#5883 New Cloud Images Process
Closed: Fixed None Opened 5 years ago by red.

The cloud kickstart file has been moved to the spin-kickstarts Git by rel-eng. When this happened, it seems there was no discussion regarding the future process to create cloud images and the Spins Process doesn't seem appropriate.

Therefore, the Cloud SIG would like to know what the intended process should look like to give new contributors access to the cloud image kickstart files and how to make sure new images (i.e. products) are created from new kickstart files if necessary.

For now, mattdm (probably already has) and I need access from the Cloud SIG but more will follow soon as we get ready to work on new products.


Nearly two weeks have passed and I haven't heard anything in this regard. Maybe you're ignoring old milestones, so I'm changing it to F21 Alpha instead, but would like to make clear that F21 Alpha is way too late for this.

Nearly two weeks have passed and I haven't heard anything in this regard. Maybe you're ignoring old milestones, so I'm changing it to F21 Alpha instead, but would like to make clear that F21 Alpha is way too late for this.

I really am not at all sure what it is you're asking. spins-kickstarts is the central repository for all fedora kickstarts, how they are added and updated, follows the spins process. if you want to add new cloud variants then they need to be proposed, reviewed and added. as to updates they are done by the spin owners. cloud is just another spin in a different wrapper to the live iso format. just as the arm images are the same thing but wrapped in a format easily consumed by arm systems. There really is nothing special or wildly different here.

I really am not at all sure what it is you're asking. spins-kickstarts is the central repository for all fedora kickstarts, how they are added and updated, follows the spins process. if you want to add new cloud variants then they need to be proposed, reviewed and added. as to updates they are done by the spin owners. cloud is just another spin in a different wrapper to the live iso format. just as the arm images are the same thing but wrapped in a format easily consumed by arm systems. There really is nothing special or wildly different here.

Hm, okay, I didn't think the spins stuff was intended with such a general meaning and purpose. I'll have it discussed in the Cloud WG whether that works for us, but would guess so.

Still, so far the Cloud Image (which will be renamed to something like Cloud Base Image for F21) was not following said process AFAIK (it's not on the F20 or F21 spin release page, for sure). So are you suggesting we follow the process retrospectively or is the Cloud Base Image good? If the latter, how can we add additional owners (i.e. let more people have git access)?

Hm, okay, I didn't think the spins stuff was intended with such a general meaning and purpose. I'll have it discussed in the Cloud WG whether that works for us, but would guess so.

Still, so far the Cloud Image (which will be renamed to something like Cloud Base Image for F21) was not following said process AFAIK (it's not on the F20 or F21 spin release page, for sure). So are you suggesting we follow the process retrospectively or is the Cloud Base Image good? If the latter, how can we add additional owners (i.e. let more people have git access)?

There was no opposition to this in the Cloud WG/SIG, so I figure we'll move forward with this. Still hoping for an answer to my questions, though. We'd really like to be able to get started here, as F21 is coming nearer (even if slowly) with every day.

There was no opposition to this in the Cloud WG/SIG, so I figure we'll move forward with this. Still hoping for an answer to my questions, though. We'd really like to be able to get started here, as F21 is coming nearer (even if slowly) with every day.

Not sure whats being asked here fully.

IMHO:

The cloud sig should determine the process they want to use to review/vet new cloud images and then when something passes that they are added.

Does that make sense? or can you clarify the remaining questions here?

Not sure whats being asked here fully.

IMHO:

The cloud sig should determine the process they want to use to review/vet new cloud images and then when something passes that they are added.

Does that make sense? or can you clarify the remaining questions here?

Metadata Update from @red:
- Issue set to the milestone: Fedora 21 Alpha

2 years ago

Login to comment on this ticket.

Metadata