Add script to upload the image to different cloud provider

[praveenkumar]

We should have a script which takes bundle and cloud provider as input and then create the image which is uploaded to respective cloud provider.

[tsebastiani]

will push a draft script that I made for AWS as starting point

[lmilbaum]

We should have a script which takes bundle and cloud provider as input and then create the image which is uploaded to respective cloud provider.

What bundle stands for?

[adrianriobo]

Would prefer to keep this out of this project I started to make a draft based on packer but there are some caveats I found with it...like only post processor allowing import for gcp and aws... azure, openstack or any other should be done with ad hoc bash code...

Code for packer can be checked at:

adrianriobo/crc-cloud-builder#1

[adrianriobo]

At least this should be reusable

[adrianriobo]

What bundle stands for?

This is the compressed asset holding the qcow2 image which needs to be imported on the providers. This is an example

[lmilbaum]

Thanks @adrianriobo. If I understand you correctly, the artifacts of such a script would be something like AWS AMIs. Those are used by crc-cloud to spin the environment. If that is the case then maybe those artifacts should be generated in a different git repo. Does that make sense?

[praveenkumar]

I was thinking of end to end enablement for the user who doesn't have the required image on the cloud from his account (as of now assume these images are not public) so the user first need to create the cloud image and this tool/script provide that functionality using the version user should have the image as part of his cloud account and then next step can be taken like provision the VM and configure to run crc.

If it is just a single script then we can keep it in the same repo in different folder like image-builder and have a entry on README how to consume it.

[lmilbaum]

I was thinking of end to end enablement for the user who doesn't have the required image on the cloud from his account (as of now assume these images are not public) so the user first need to create the cloud image and this tool/script provide that functionality using the version user should have the image as part of his cloud account and then next step can be taken like provision the VM and configure to run crc.

If it is just a single script then we can keep it in the same repo in different folder like image-builder and have a entry on README how to consume it.

Ah. OK. Valid point.