Tracking ticket for building support for the Azure Image uploads
Metadata Update from @davdunc: - Issue marked as depending on: #355 - Issue tagged with: Azure, meeting
@dustymabe reports that work on a PoC required X.Y.Z versioning to be used. and in FCOS we have a X.Y.Z.A
We are looking for a way to coordinate the requirements.
X.Y.Z versioning should be easy for us, since Fedora Cloud already does this (version.n.datestamp)
Opened a pull request for pungi here: https://pagure.io/pungi-fedora/pull-request/1161
Metadata Update from @davdunc: - Issue assigned to davdunc
Pungi pull request is merged. Working on the uploader.
I'm still getting a handle on the state of things, but is there anything here I can do to help?
Metadata Update from @davdunc: - Issue assigned to jcline (was: davdunc)
This is now done. Images are uploaded using https://pagure.io/cloud-image-uploader/ to an Community Azure Compute Gallery. The public gallery id is Fedora-5e266ba4-2250-406d-adad-5d73860d958f - users can query for existing images via the CLI with something like az sig image-definition list-community --public-gallery-name Fedora-5e266ba4-2250-406d-adad-5d73860d958f ....
Fedora-5e266ba4-2250-406d-adad-5d73860d958f
az sig image-definition list-community --public-gallery-name Fedora-5e266ba4-2250-406d-adad-5d73860d958f ...
At the moment, the nightly builds are uploaded nightly, but won't be used by users booting the "latest" image. Every other week I'm manually promoting an image after some smoke testing, but I'm looking to automate that testing and promotion in the near future.
Metadata Update from @jcline: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.