#324 Setup Hyperscale tags for c9s
Closed: Fixed 8 months ago by arrfab. Opened a year ago by ngompa.

Please setup build tags for the Hyperscale SIG with:

$sig = hyperscale
$version = 9s
$project = packages, spin
$version = main, experimental, spin, hotfixes, facebook

leading to:

  • hyperscale9s-packages-{main,experimental,spin,hotfixes,facebook}-{candidate,testing,release}
  • hyperscale9s-spin-{main,experimental}-{candidate,testing,release}

which would then publish to:

/centos/9-stream/hyperscale/$arch/packages-main
/centos/9-stream/hyperscale/$arch/packages-experimental
/centos/9-stream/hyperscale/$arch/packages-spin
/centos/9-stream/hyperscale/$arch/packages-hotfixes
/centos/9-stream/hyperscale/$arch/packages-facebook
/centos/9-stream/hyperscale/$arch/spin-main
/centos/9-stream/hyperscale/$arch/spin-experimental

We need the following macros set for all of the tags:

%dist .hs.el9
%centos_hs 1

For the facebook tags, we need the following macros set instead:

%dist .hs+fb.el9
%facebook 1
%centos_hs 1

For the experimental tags, we need the %dist macro to use hsx instead of hs where appropriate.

For the hyperscale9s-spin-main-* tags, all hyperscale9s-packages-* tags should be set up as packages in its buildroot except the -experimental ones. For the hyperscale9s-spin-experimental-* tags, the hyperscale9s-packages-experimental-* tags should be added to it too.

For $arch, we want x86_64 and aarch64.

Thanks!


One interesting point that was raised during CentOS Stream office hours is that we do not have signed content yet for cs9.

I see few steps, we can do on koji-dev first :
- add cs9 repos (do we care about signed content?)
- modify tooling to support cs9
- create a tag
- profit

Metadata Update from @arrfab:
- Issue marked as depending on: #313
- Issue priority set to: Waiting on External (was: Needs Review)
- Issue tagged with: cbs, centos-build-pipeline, feature-request, groomed

a year ago

Per discussion in #313 , @bstinson asked for all 9s requests to wait for proper 9 Stream to really exist.
So tagged this request as "groomed"

Metadata Update from @arrfab:
- Issue marked as blocking: #336

9 months ago

I've added a centos9s-buildroot externalrepo in to CBS:https://cbs.centos.org/koji/externalrepoinfo?extrepoID=42 , we can proceed with these hyperscale tags

@bstinson well, it points to external mirror (really external) which we don't allow (per koji policy) so except if we now add a specific route, why not doing like for epel : internal mirror in the DC/subnet/vlan where CBS hosts are hosted ?

sure, we can mirror this content

It needs to be a mirror b/c https://kojihub.stream.centos.org/kojifiles/repos/c9s-build/latest/ could change under the feet of CBS builds - it's auto-regenerated after a new build is tagged into c9s-build tag hierarchy.

@apevec correct, so let me sync up with @bstinson to see how we can easily mirror cs9 content internally (different DC/subnet/env) and so have it available for cbs kojid builders

I've updated the ticket to sync it with what we have for c8s now, and to include AArch64, since we're going to start supporting that too.

Metadata Update from @arrfab:
- Issue marked as depending on: #425

8 months ago

I just announced CentOS Stream 9 for cbs (https://lists.centos.org/pipermail/centos-devel/2021-September/077320.html) , so let's start with one tag and if that seems to work for you (after some feedback), I'll create all the other ones (quite a bunch)

I have so started with the packages-main one :

* Checking distribution el9s configuration...
 -> Checking hyperscale config...
Using default options for hyperscale/packages
Creating tag  : hyperscale9s-packages-main-candidate
Creating tag  : hyperscale9s-packages-main-testing
Creating tag  : hyperscale9s-packages-main-release
 -> creating hyperscale9s-packages-main-el9s
Added external repo centos9s-baseos to tag hyperscale9s-packages-main-el9s-build (priority 5)
Added external repo centos9s-appstream to tag hyperscale9s-packages-main-el9s-build (priority 10)
Added external repo centos9s-crb to tag hyperscale9s-packages-main-el9s-build (priority 15)

# taginfo
Tag: hyperscale9s-packages-main-el9s-build [2379]
Arches: x86_64 aarch64
Groups: build, srpm-build
Tag options:
  mock.new_chroot : 0
  mock.package_manager : 'dnf'
  mock.yum.module_hotfixes : 1
  rpm.macro.centos_hs : 1
  rpm.macro.dist : '.hs.el9'
This tag is a buildroot for one or more targets
Current repo: repo#854586: 2021-09-03 13:04:22.549874+00:00
Targets that build from this tag:
  hyperscale9s-packages-main-el9s
External repos:
    5 centos9s-baseos (http://mirror.stream.centos.org/9-stream/BaseOS/$arch/os/, merge mode: bare), arches: inherited from tag
   10 centos9s-appstream (http://mirror.stream.centos.org/9-stream/AppStream/$arch/os/, merge mode: bare), arches: inherited from tag
   15 centos9s-crb (http://mirror.stream.centos.org/9-stream/CRB/$arch/os/, merge mode: bare), arches: inherited from tag
Inheritance:
  5    .... buildsys9s-release [2363]
  10   .... hyperscale9s-packages-main-candidate [2376]

Can you give it a try and give us feedback ? If that works for you, I'll create the other ones.
PS: as stated in the mail sent to -devel list, -release tag[s] is/are locked for now

Metadata Update from @arrfab:
- Issue assigned to arrfab

8 months ago

Metadata Update from @arrfab:
- Issue untagged with: groomed
- Issue priority set to: Waiting on Reporter (was: Waiting on External)
- Issue tagged with: centos-stream, high-gain, medium-trouble

8 months ago

Could you create the -spin tags? Because nothing we have for main is likely to carry over to c9s right now, but all the packages we have for spin will need to be built...

Basically, I have no packages to test with for packages-main, but I have plenty for packages-spin.

Added too :

* Checking distribution el9s configuration...
 -> Checking hyperscale config...
Using default options for hyperscale/packages
Creating tag  : hyperscale9s-packages-spin-candidate
Creating tag  : hyperscale9s-packages-spin-testing
Creating tag  : hyperscale9s-packages-spin-release
 -> creating hyperscale9s-packages-spin-el9s
Added external repo centos9s-baseos to tag hyperscale9s-packages-spin-el9s-build (priority 5)
Added external repo centos9s-appstream to tag hyperscale9s-packages-spin-el9s-build (priority 10)
Added external repo centos9s-crb to tag hyperscale9s-packages-spin-el9s-build (priority 15)

# taginfo
Tag: hyperscale9s-packages-spin-el9s-build [2383]
Arches: x86_64 aarch64
Groups: build, srpm-build
Tag options:
  mock.new_chroot : 0
  mock.package_manager : 'dnf'
  mock.yum.module_hotfixes : 1
  rpm.macro.centos_hs : 1
  rpm.macro.dist : '.hs.el9'
This tag is a buildroot for one or more targets
Current repo: no active repo
Targets that build from this tag:
  hyperscale9s-packages-spin-el9s
External repos:
    5 centos9s-baseos (http://mirror.stream.centos.org/9-stream/BaseOS/$arch/os/, merge mode: bare), arches: inherited from tag
   10 centos9s-appstream (http://mirror.stream.centos.org/9-stream/AppStream/$arch/os/, merge mode: bare), arches: inherited from tag
   15 centos9s-crb (http://mirror.stream.centos.org/9-stream/CRB/$arch/os/, merge mode: bare), arches: inherited from tag
Inheritance:
  5    .... buildsys9s-release [2363]
  10   .... hyperscale9s-packages-spin-candidate [2380]

thanks for the feedback .. so do you want me to add the other ones ?
The part about For the hyperscale9s-spin-main-* tags, all hyperscale9s-packages-* tags should be set up as packages in its buildroot is a little bit confusing though, so if you can elaborate and/or (preferred) comes with a list of inheritances between your tags, I'll be able to proceed

@arrfab Basically, kickstarts that run through hyperscale9s-spin-* tags should be able to source packages from the hyperscale9s-packages-* tags.

Specifically, -spin-main should be able to source from -packages-main, and -spin-experimental from -packages-experimental and -packages-main

@ngompa actually, do you want hotfixes as well for the spin tags?

Yes, I want hotfixes too.

Let's divide this request into multiple ones.
I created all the other hyperscale9s-packages-{main,experimental,spin,hotfixes,facebook} tags, normally with proper macros.
So let me close this ticket as the hyperscale9s-spin* ones seems more related to iso/tree which is something that has never been asked for and in fact still WIP for 8s (see your ticket #388)

Once ticket #388 is working and that there is a clear path about spins, you'll be able to create a new ticket for 9s too

Metadata Update from @arrfab:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

8 months ago

Login to comment on this ticket.

Boards 1
CBS Status: Backlog