#9 RFC: Hyperscale Cloud Images
Opened 3 years ago by ignatenkobrain. Modified 3 months ago

Given that there are some ideas like #3 and #7, I guess it would make sense to build our own cloud images (aka ami/qcow2) since it would be very inconvenient to deploy machines and having to reboot them.

Should we ask Cloud SIG to support us with this (so that on top of what images they build, they would also build another one or few images with packages from hyperscale SIG) or would we build our own images or we don't care?


Yeah, I think this could be useful. Assuming the Cloud SIG already has tooling in place to build cloud images, I'd lean towards leveraging that. Whether we end up hosting the builds ourselves or they do, I have no strong preference on.

Are we able to also do Azure images?

Also, we certainly should work in partnership with the Cloud SIG on this.

There are Azure images for c7 on https://cloud.centos.org/ but I don't see any for c8 / c8s.

Hmm, maybe @jperrin can help us and Cloud SIG get Azure images in place...

I'm not sure where the c7 images came from or how they were built. I am working on a way to publish official azure images though. I'll report back when I've got more info.

Metadata Update from @dcavalca:
- Issue tagged with: meeting

3 years ago

Metadata Update from @salimma:
- Issue assigned to salimma

3 years ago

I'll check with the Cloud SIG and look at getting some images built. Do we have any priority preference for image types? Cloud currently produces the following: https://alt.fedoraproject.org/cloud/

  • raw
  • qcow2 for OpenStack
  • vagrant (vbox, kvm)
  • gcp
  • aws (x86_64, aarch64)

I'm interested in OpenStack and AWS images ATM.

+1 for AWS as we have an internal customer for it.

I need OpenStack, AWS, and Azure images, so it'd be great if we could get those...

Metadata Update from @dcavalca:
- Issue untagged with: meeting
- Issue assigned to ngompa (was: salimma)

2 years ago

Login to comment on this ticket.

Metadata