uyuni-project / uyuni

Source code for Uyuni
https://www.uyuni-project.org/
GNU General Public License v2.0
428 stars 177 forks source link

Add deployment support for all our support clients in sumaform #2719

Open srbarrios opened 3 years ago

srbarrios commented 3 years ago

Contribute in Sumaform to support more clients

Thanks to sumaform, we are available to build an environment using libvirt or AWS, including systems for the most important supported clients. For that, we make use of official images.

But we still missing a lot of officially supported clients.

Here the full list of supported clients:

Sumaform link to the list of images: https://github.com/uyuni-project/sumaform/blob/master/backend_modules/libvirt/base/main.tf

srbarrios commented 3 years ago

@paususe please prioritize this card inside a squad different than QA Squad. We need all of them in sumaform, but we can only commit to use them, not to add support for them.

paususe commented 3 years ago

Oracle Linux images can be built with https://github.com/oracle/ol-sample-scripts/tree/master/oracle-linux-image-tools

moio commented 3 years ago

Ha, Packer again. Not straightforward, but it can be done if no openstack images (or equivalent) can be found

paususe commented 3 years ago

I found a better solution for Oracle Linux: we can download the Vagrant boxes, uncompress them, and inside we find a qcow2 image file: http://yum.oracle.com/boxes/

It may require some enablement in sumaform, though.

moio commented 3 years ago

That's a nice idea worth exploring :+1:

One possibility is to create an OBS project which uses the .box file as the "source archive" and the "building" becomes "decompressing it" - thereby publishing the .qcow2 inside.

srbarrios commented 3 years ago

I found a better solution for Oracle Linux: we can download the Vagrant boxes, uncompress them, and inside we find a qcow2 image file: http://yum.oracle.com/boxes/

It may require some enablement in sumaform, though.

Yup, I guess it might need the cloud-init part.

In any case, for this card goal, I would not worry too much about having "offical images" or having them "as a Continurous Delivery way", but I would like to at least have contributions in sumaform with any qcow2 image that succeded deploying the supported clients, tweaking whatever is need on cloud-init or salt states.

paususe commented 3 years ago

One possibility is to create an OBS project which uses the .box file as the "source archive" and the "building" becomes "decompressing it" - thereby publishing the .qcow2 inside.

Would it be possible to run some kind of pre-script to download the Vagrant box, uncompress it and run virt-customize -a box.img --root-password password:MYNEWPASSWORD?

That way we avoid the need for an OBS project.

moio commented 3 years ago

Problem I see is that would add virt-customize and some scripting language as dependencies of sumaform, while currently it only has Terraform. Maintenance wise I do not see a huge difference with an OBS project, so I would be inclined to go down that path.

Shirocco88 commented 3 years ago

Is Ubuntu 16.04 LTS (JeOS image: ubuntu1604o) really neccessary ? IMHO it is EOL;

moio commented 3 years ago

I would not invest any fresh development time in supporting that OS version at this point in time, but if possible I'd keep the image around in sumaform a little longer, just in case someone comes back with a user case that, despite the EOL, is still something we can help with.

Typically we try to be nice and help out users in case they have difficulties migrating out of EOL'd OSs, for example.

I think the image can actually be dropped completely let's say some months from now.