Revision as of 20:47, 19 April 2023

Fedora Images on Azure

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Azure is a massive public cloud and offering an official Fedora Cloud image there would expand Fedora's user base there. It also gives Fedora Cloud users more options when selecting public clouds.

Owner

Name: Major Hayden David Duncan
Email: major@redhat.com

Current status

Targeted release: Fedora Linux 39
Last updated: 2023-04-19
FESCo issue: <will be assigned by the Wrangler>
Tracker bug: <will be assigned by the Wrangler>
Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

We want to:

Get Azure images built via the existing Pungi processes
Publish Azure images via Azure's image gallery
Test these images during regularly scheduled Fedora Cloud test days before final

 release

Ensure that the Azure URN is linked on the Fedora website in the cloud downloads

 section (similar to how AWS images are listed today)

Feedback

Another alternative would be to offer a VHD download option from a mirror, but that would require users to download the image and upload it to Azure on their own. This could be challenging for users without technical skills to complete these steps or for users with slow network connectivity.

Benefit to Fedora

Expands Fedora's official image public cloud footprint to Azure (currently just AWS)
Allows Azure customers to launch official Fedora images which were tested before launch
Raises awareness around Fedora Cloud images

Scope

Proposal owners: Isolated change that does not affect the OS itself but does improve

 its availability in public clouds.

Other developers: Does not affect other developers or features in Fedora.

Release engineering: #Releng issue number

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with Community Initiatives: N/A

Upgrade/compatibility impact

This is a net new offering in a cloud where Fedora was not previously offered.

How To Test

Verify that the Fedora image appears in Azure's image gallery
Launch an Azure VM with the new Fedora image
Complete the usual verification that is done on other clouds during test days

User Experience

Customers on Azure will notice that a new Fedora official images is available to them. Users of other platforms, such as workstation and server, will not see a change. Customers of other clouds, such as AWS, will not see a change either.

Dependencies

All dependencies are already packaged and tested. One of the biggest is the Azure Linux agent (walagent), but it has been packaged in Fedora for multiple releases and is verified to work on Azure.

Contingency Plan

Contingency mechanism: N/A (not a System Wide Change)
Contingency deadline: N/A (not a System Wide Change)
Blocks release? No

Documentation

N/A (not a System Wide Change)

Release Notes

Fedora images are now available for use in Azure VMs.

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
+= Fedora Images on Azure =
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
-{{admon/tip | Report issues | To report an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-= Change Proposal Name <!-- The name of your change proposal --> =
 {{Change_Proposal_Banner}}
 == Summary ==
-<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
+Azure is a massive public cloud and offering an official Fedora Cloud image there would
+expand Fedora's user base there. It also gives Fedora Cloud users more options when
+selecting public clouds.
 == Owner ==
-<!--
+* Name: [[User:mhayden| Major Hayden]] [[User:davdunc| David Duncan]]
-For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
+* Email: major@redhat.com
-This should link to your home wiki page so we know who you are.
--->
-* Name: [[User:FASAcountName| Your Name]]
-<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
-* Email: <your email address so we can contact you, invite you to meetings, etc. Please provide your Bugzilla email address if it is different from your email in FAS>
-<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
-* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
--->
@@ Line 34: / Line 21: @@
 <!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
-<!-- Select proper category, default is Self Contained Change -->
 [[Category:SelfContainedChange]]
-<!-- [[Category:SystemWideChange]] -->
-* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f<VERSION>/ Fedora Linux <VERSION>]
+* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f39/ Fedora Linux 39]
 * Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
@@ Line 52: / Line 37: @@
 == Detailed Description ==
 <!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+We want to:
+* Get Azure images built via the existing Pungi processes
+* Publish Azure images via Azure's image gallery
+* Test these images during regularly scheduled Fedora Cloud test days before final
+  release
+* Ensure that the Azure URN is linked on the Fedora website in the cloud downloads
+  section (similar to how AWS images are listed today)
 == Feedback ==
 <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
+Another alternative would be to offer a VHD download option from a mirror, but that
+would require users to download the image and upload it to Azure on their own. This
+could be challenging for users without technical skills to complete these steps or for
+users with slow network connectivity.
 == Benefit to Fedora ==
@@ Line 84: / Line 83: @@
       https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
 -->
+* Expands Fedora's official image public cloud footprint to Azure (currently just AWS)
+* Allows Azure customers to launch official Fedora images which were tested before launch
+* Raises awareness around Fedora Cloud images
 == Scope ==
-* Proposal owners:
+* Proposal owners: Isolated change that does not affect the OS itself but does improve
+  its availability in public clouds.
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Other developers: Does not affect other developers or features in Fedora.<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
@@ Line 102: / Line 106: @@
 <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
-* Alignment with Community Initiatives:
+* Alignment with Community Initiatives: N/A
 <!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->
@@ Line 108: / Line 112: @@
 <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+This is a net new offering in a cloud where Fedora was not previously offered.
@@ Line 126: / Line 130: @@
 -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Verify that the Fedora image appears in Azure's image gallery
+* Launch an Azure VM with the new Fedora image
+* Complete the usual verification that is done on other clouds during [https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230418.n.1_Cloud test days]
@@ Line 140: / Line 146: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
+Customers on Azure will notice that a new Fedora official images is available to them.
+Users of other platforms, such as workstation and server, will not see a change.
+Customers of other clouds, such as AWS, will not see a change either.
 == Dependencies ==
 <!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+All dependencies are already packaged and tested. One of the biggest is the Azure Linux
+agent (walagent), but it has been packaged in Fedora for multiple releases and is
+verified to work on Azure.
@@ Line 150: / Line 162: @@
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency mechanism: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
 * Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 169: / Line 181: @@
 Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
 -->
+Fedora images are now available for use in Azure VMs.

Search

Changes/Fedora Images On Azure: Difference between revisions