From 79985af449bf8de301bd47eb336117baeded9e58 Mon Sep 17 00:00:00 2001 From: Bala Konda Reddy M Date: Nov 03 2025 18:47:07 +0000 Subject: [PATCH 1/5] Add docs for fedora on Microsoft Azure Signed-off-by: Bala Konda Reddy M --- diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc index 0cefa03..e9e500d 100644 --- a/modules/ROOT/nav.adoc +++ b/modules/ROOT/nav.adoc @@ -1,2 +1,3 @@ -* xref:faq.adoc[FAQ] -* xref:wsl.adoc[Windows Subsystem for Linux] \ No newline at end of file +* xref:wsl.adoc[Windows Subsystem for Linux] +* xref:azure.adoc[Fedora on Microsoft Azure] +* xref:faq.adoc[FAQ] \ No newline at end of file diff --git a/modules/ROOT/pages/azure.adoc b/modules/ROOT/pages/azure.adoc new file mode 100644 index 0000000..1a8f4c6 --- /dev/null +++ b/modules/ROOT/pages/azure.adoc @@ -0,0 +1,243 @@ += Fedora on Microsoft Azure + + +Microsoft Azure is one of the major cloud platforms where Fedora Cloud images are officially supported and regularly updated by the Fedora Cloud SIG. + +Fedora images are directly accessible through Azure's Community Gallery, providing a seamless deployment experience without requiring manual image uploads. + +Azure provides a https://azure.microsoft.com/en-us/free/[free tier offering] for new customers, which includes $200 in credits valid for the first 30 days, plus access to popular services free for 12 months. + + +== Prerequisites + +Before deploying Fedora on Microsoft Azure, ensure you have an active Azure account with a valid subscription that includes sufficient quota for virtual machine creation. + +Azure uses resource groups as organizational units for related cloud resources. Resource groups function as containers that group Azure resources such as virtual machines, storage accounts, and network components. This structure allows for consolidated management, billing, and cleanup operations. + +For secure access to your Fedora virtual machines, SSH key pairs are required. Azure can generate these automatically during VM creation, or you can provide your own existing keys. + +Additionally, install the Azure CLI on your local machine to manage deployments and configure resources programmatically from the command line. + +[source,bash] +---- +sudo dnf install azure-cli +az login # Authenticate your account +---- + +NOTE: The login process will open your browser and may take a few moments to complete. + +If you prefer using the web interface, navigate to https://portal.azure.com[Azure Portal] to deploy VMs through the browser. + +== Deploy Fedora VMs + +There are two primary methods to deploy Fedora virtual machines on Azure: + +1. **Web Portal**: Using either the Fedora Project's cloud launch page or Azure's Community Gallery +2. **Azure CLI**: Command-line deployment + +== Method 1: Web Portal Deployment + +Ensure you are authenticated to portal.azure.com before proceeding. + +=== Option A: Using Fedora Project Cloud Launch + +This method provides the quickest deployment path. The Fedora Project website integrates directly with Azure, automatically selecting the appropriate image for your chosen region. + +1. Navigate to https://fedoraproject.org/cloud/download#cloud_launch[Fedora Cloud Launch] +2. Choose your preferred Azure region from the available options +3. The system will redirect you directly to Azure's VM creation interface + +NOTE: Toggle "Show Beta downloads" on the page to access the latest beta images for deployment. + +=== Option B: Using Azure Community Gallery + +For more control over the deployment process, manually navigate through Azure's Community Gallery to select Fedora images. + +==== Finding Fedora Images + +1. Access the https://portal.azure.com/#view/Microsoft_Azure_ComputeHub/ComputeHubMenuBlade/~/communityImagesBrowse[Community images service] in Azure Portal +2. Apply a filter for "Public gallery name" and locate Fedora's gallery: `Fedora-5e266ba4-2250-406d-adad-5d73860d958f` +3. Select the Fedora image that matches your requirements (version and architecture) +4. Choose a region geographically close to your location for better performance +5. Click "Create VM" to begin the configuration process + +==== Virtual Machine Configuration + +Configure the following parameters during VM setup: + +*Resource Organization:* Create a new resource group or select an existing one. Resource groups organize and manage related Azure components as a single unit. + +*VM Identity:* Assign a name to your virtual machine. This name becomes both the hostname and the resource identifier within Azure. + +*Instance Size:* Select an appropriate VM size based on your workload requirements. For general-purpose workloads, consider the Standard_B2ats_v2 size, which provides balanced compute resources. + +*Authentication:* Configure SSH key authentication for secure access. Azure can generate a new key pair automatically, which you'll download for later use. + +==== Post-Deployment Access + +Once deployment completes (typically takes 2-3 minutes), Azure displays your VM details including the assigned public IP address. To connect to your Fedora instance: + +1. Download your SSH private key when prompted +2. Set appropriate file permissions for security +3. Connect using SSH with the default `azureuser` account + +[source,bash] +---- +chmod 600 ~/Downloads/your-key-name.pem +ssh -i ~/Downloads/your-key-name.pem azureuser@YOUR-PUBLIC-IP +---- + +==== Resource Cleanup + +When the VM is no longer needed, delete the entire resource group to remove all associated resources efficiently. This removes the VM, storage, networking components, and all other related resources. Confirm your intent before proceeding with deletion. + + +== Method 2: Azure CLI Deployment + +The Azure Command Line Interface provides a powerful alternative for users who prefer programmatic deployment or need to automate VM creation processes. While the CLI requires more specific knowledge of Azure parameters, it offers greater speed and automation capabilities. + +=== Authentication and Setup + +Ensure you have properly authenticated with Azure and have the necessary permissions to create resources: + +[source,bash] +---- +az login +az account show # Verify correct subscription +---- + +=== Discovering Available Images + +Fedora maintains multiple image definitions within Azure's Community Gallery, covering different releases and hardware architectures. Each image definition contains various versions, with new versions added regularly for security updates and improvements. + +To list all available Fedora image definitions: + +[source,bash] +---- +az sig image-definition list-community \ + --public-gallery-name Fedora-5e266ba4-2250-406d-adad-5d73860d958f \ + --location eastus \ + --query '[].name' +---- + +For viewing specific versions of an image definition: + +[source,bash] +---- +az sig image-version list-community \ + --public-gallery-name Fedora-5e266ba4-2250-406d-adad-5d73860d958f \ + --gallery-image-definition "Fedora-Cloud-42-x64" \ + --location eastus \ + --query '[?!excludeFromLatest].uniqueId' +---- + +=== Creating Virtual Machines + +Begin by establishing a resource group to contain your VM and associated resources: + +[source,bash] +---- +az group create \ + --location eastus \ + --resource-group fedora-deployment +---- + +The command returns confirmation of the created resource group: + +[source,json] +---- +{ + "id": "/subscriptions/[SUBSCRIPTION-ID]/resourceGroups/fedora-deployment", + "location": "eastus", + "managedBy": null, + "name": "fedora-deployment", + "properties": { + "provisioningState": "Succeeded" + }, + "tags": null, + "type": "Microsoft.Resources/resourceGroups" +} +---- + +Deploy the virtual machine using the discovered image ID: + +[source,bash] +---- +az vm create \ + --location eastus \ + --name fedora_latest \ + --resource-group fedora-deployment \ + --image /CommunityGalleries/Fedora-5e266ba4-2250-406d-adad-5d73860d958f/Images/Fedora-Cloud-42-x64/Versions/latest \ + --size Standard_B2ats_v2 \ + --security-type TrustedLaunch \ + --generate-ssh-keys +---- + +During deployment, Azure will prompt for license agreement acceptance: + +---- +To create the VM/VMSS from community gallery image, you must accept the license agreement and privacy statement: https://docs.fedoraproject.org/en-US/legal/. (If you want to accept the legal terms by default, please use the option '--accept-term' when creating VM/VMSS) (Y/n): y +---- + +Upon successful deployment, the command returns VM details: + +[source,json] +---- +{ + "fqdns": "", + "id": "/subscriptions/[SUBSCRIPTION-ID]/resourceGroups/fedora-deployment/providers/Microsoft.Compute/virtualMachines/fedora_latest", + "location": "eastus", + "powerState": "VM running", + "privateIpAddress": "[PRIVATE-IP]", + "publicIpAddress": "[PUBLIC-IP]", + "resourceGroup": "fedora-deployment", + "zones": "" +} +---- + +This command creates a VM and automatically generates SSH keys for authentication. + +To connect to your deployed VM, use the generated SSH key: + +[source,bash] +---- +chmod 600 ~/.ssh/fedora-azure.pem # Set proper permissions for the SSH key +ssh -i ~/.ssh/fedora-azure.pem azureuser@YOUR-PUBLIC-IP +---- + +=== Resource Management + +To remove all created resources when they're no longer needed: + +[source,bash] +---- +az group delete --name fedora-deployment --yes +---- + +The `--yes` flag automatically confirms the deletion without prompting for user input. This command removes the resource group and all contained resources, providing a clean and complete cleanup process. + +== Post-Deployment Configuration + +After successfully deploying your Fedora VM, several configuration steps will help optimize your environment for production use. + +=== Initial System Updates + +Connect to your VM and ensure the system has the latest security updates: + +[source,bash] +---- +sudo dnf update -y +---- + +=== User Management + +The default user account `azureuser` comes with sudo privileges. You may want to create additional users or configure specific access controls based on your security requirements. + +=== Network Security + +Review and configure Network Security Groups (NSGs) to control inbound and outbound traffic. By default, only SSH access (port 22) is enabled. Add rules for any additional services you plan to run. + +== Additional Resources + +For comprehensive information about Azure virtual machine features and advanced configurations, consult the official Azure virtual machine documentation. The https://learn.microsoft.com/en-us/cli/azure/?view=azure-cli-latest[Azure CLI reference guide] provides detailed information about all available commands and parameters for deployments. + From 416829d73053f8a9796a05a527dd65b0dc8ff101 Mon Sep 17 00:00:00 2001 From: Bala Konda Reddy M Date: Nov 03 2025 18:47:07 +0000 Subject: [PATCH 2/5] Add docs for fedora on Microsoft Azure Signed-off-by: Bala Konda Reddy M --- diff --git a/modules/ROOT/pages/azure.adoc b/modules/ROOT/pages/azure.adoc index 1a8f4c6..483c645 100644 --- a/modules/ROOT/pages/azure.adoc +++ b/modules/ROOT/pages/azure.adoc @@ -16,17 +16,6 @@ Azure uses resource groups as organizational units for related cloud resources. For secure access to your Fedora virtual machines, SSH key pairs are required. Azure can generate these automatically during VM creation, or you can provide your own existing keys. -Additionally, install the Azure CLI on your local machine to manage deployments and configure resources programmatically from the command line. - -[source,bash] ----- -sudo dnf install azure-cli -az login # Authenticate your account ----- - -NOTE: The login process will open your browser and may take a few moments to complete. - -If you prefer using the web interface, navigate to https://portal.azure.com[Azure Portal] to deploy VMs through the browser. == Deploy Fedora VMs @@ -37,17 +26,19 @@ There are two primary methods to deploy Fedora virtual machines on Azure: == Method 1: Web Portal Deployment -Ensure you are authenticated to portal.azure.com before proceeding. +Ensure you are authenticated to https://portal.azure.com/[Azure Portal] before proceeding. === Option A: Using Fedora Project Cloud Launch This method provides the quickest deployment path. The Fedora Project website integrates directly with Azure, automatically selecting the appropriate image for your chosen region. -1. Navigate to https://fedoraproject.org/cloud/download#cloud_launch[Fedora Cloud Launch] +NOTE: Toggle "Show Beta downloads" on the Cloud launch page to access the latest beta images for deployment. + + +1. Navigate to https://fedoraproject.org/cloud/download#cloud_launch[Fedora Cloud Launch] page. 2. Choose your preferred Azure region from the available options 3. The system will redirect you directly to Azure's VM creation interface -NOTE: Toggle "Show Beta downloads" on the page to access the latest beta images for deployment. === Option B: Using Azure Community Gallery @@ -58,20 +49,7 @@ For more control over the deployment process, manually navigate through Azure's 1. Access the https://portal.azure.com/#view/Microsoft_Azure_ComputeHub/ComputeHubMenuBlade/~/communityImagesBrowse[Community images service] in Azure Portal 2. Apply a filter for "Public gallery name" and locate Fedora's gallery: `Fedora-5e266ba4-2250-406d-adad-5d73860d958f` 3. Select the Fedora image that matches your requirements (version and architecture) -4. Choose a region geographically close to your location for better performance -5. Click "Create VM" to begin the configuration process - -==== Virtual Machine Configuration - -Configure the following parameters during VM setup: - -*Resource Organization:* Create a new resource group or select an existing one. Resource groups organize and manage related Azure components as a single unit. - -*VM Identity:* Assign a name to your virtual machine. This name becomes both the hostname and the resource identifier within Azure. - -*Instance Size:* Select an appropriate VM size based on your workload requirements. For general-purpose workloads, consider the Standard_B2ats_v2 size, which provides balanced compute resources. - -*Authentication:* Configure SSH key authentication for secure access. Azure can generate a new key pair automatically, which you'll download for later use. +4. Use https://learn.microsoft.com/en-us/azure/virtual-machines/linux/quick-create-portal[Azure Quick Create] Documentation for the vm configuration. ==== Post-Deployment Access @@ -87,25 +65,23 @@ chmod 600 ~/Downloads/your-key-name.pem ssh -i ~/Downloads/your-key-name.pem azureuser@YOUR-PUBLIC-IP ---- -==== Resource Cleanup - -When the VM is no longer needed, delete the entire resource group to remove all associated resources efficiently. This removes the VM, storage, networking components, and all other related resources. Confirm your intent before proceeding with deletion. - == Method 2: Azure CLI Deployment The Azure Command Line Interface provides a powerful alternative for users who prefer programmatic deployment or need to automate VM creation processes. While the CLI requires more specific knowledge of Azure parameters, it offers greater speed and automation capabilities. -=== Authentication and Setup - -Ensure you have properly authenticated with Azure and have the necessary permissions to create resources: +Install the Azure CLI on your local machine to manage deployments and configure resources. [source,bash] ---- -az login -az account show # Verify correct subscription +sudo dnf install azure-cli +az login # Authenticate your account +az account show # Verify correct subscription ---- +NOTE: The login process will open your browser and may take a few moments to complete. + + === Discovering Available Images Fedora maintains multiple image definitions within Azure's Community Gallery, covering different releases and hardware architectures. Each image definition contains various versions, with new versions added regularly for security updates and improvements. @@ -119,7 +95,7 @@ az sig image-definition list-community \ --location eastus \ --query '[].name' ---- - +Creating For viewing specific versions of an image definition: [source,bash] @@ -133,69 +109,10 @@ az sig image-version list-community \ === Creating Virtual Machines -Begin by establishing a resource group to contain your VM and associated resources: - -[source,bash] ----- -az group create \ - --location eastus \ - --resource-group fedora-deployment ----- - -The command returns confirmation of the created resource group: - -[source,json] ----- -{ - "id": "/subscriptions/[SUBSCRIPTION-ID]/resourceGroups/fedora-deployment", - "location": "eastus", - "managedBy": null, - "name": "fedora-deployment", - "properties": { - "provisioningState": "Succeeded" - }, - "tags": null, - "type": "Microsoft.Resources/resourceGroups" -} ----- - -Deploy the virtual machine using the discovered image ID: - -[source,bash] ----- -az vm create \ - --location eastus \ - --name fedora_latest \ - --resource-group fedora-deployment \ - --image /CommunityGalleries/Fedora-5e266ba4-2250-406d-adad-5d73860d958f/Images/Fedora-Cloud-42-x64/Versions/latest \ - --size Standard_B2ats_v2 \ - --security-type TrustedLaunch \ - --generate-ssh-keys ----- - -During deployment, Azure will prompt for license agreement acceptance: - ----- -To create the VM/VMSS from community gallery image, you must accept the license agreement and privacy statement: https://docs.fedoraproject.org/en-US/legal/. (If you want to accept the legal terms by default, please use the option '--accept-term' when creating VM/VMSS) (Y/n): y ----- - -Upon successful deployment, the command returns VM details: +Please follow this https://learn.microsoft.com/en-us/azure/virtual-machines/linux/tutorial-manage-vm[Virtual Machine Creation] guide from the Azure documentation using Azure CLI -[source,json] ----- -{ - "fqdns": "", - "id": "/subscriptions/[SUBSCRIPTION-ID]/resourceGroups/fedora-deployment/providers/Microsoft.Compute/virtualMachines/fedora_latest", - "location": "eastus", - "powerState": "VM running", - "privateIpAddress": "[PRIVATE-IP]", - "publicIpAddress": "[PUBLIC-IP]", - "resourceGroup": "fedora-deployment", - "zones": "" -} ----- +NOTE: Use --image option with specific fedora version /CommunityGalleries/Fedora-5e266ba4-2250-406d-adad-5d73860d958f/Images/// during vm creation. -This command creates a VM and automatically generates SSH keys for authentication. To connect to your deployed VM, use the generated SSH key: @@ -204,40 +121,3 @@ To connect to your deployed VM, use the generated SSH key: chmod 600 ~/.ssh/fedora-azure.pem # Set proper permissions for the SSH key ssh -i ~/.ssh/fedora-azure.pem azureuser@YOUR-PUBLIC-IP ---- - -=== Resource Management - -To remove all created resources when they're no longer needed: - -[source,bash] ----- -az group delete --name fedora-deployment --yes ----- - -The `--yes` flag automatically confirms the deletion without prompting for user input. This command removes the resource group and all contained resources, providing a clean and complete cleanup process. - -== Post-Deployment Configuration - -After successfully deploying your Fedora VM, several configuration steps will help optimize your environment for production use. - -=== Initial System Updates - -Connect to your VM and ensure the system has the latest security updates: - -[source,bash] ----- -sudo dnf update -y ----- - -=== User Management - -The default user account `azureuser` comes with sudo privileges. You may want to create additional users or configure specific access controls based on your security requirements. - -=== Network Security - -Review and configure Network Security Groups (NSGs) to control inbound and outbound traffic. By default, only SSH access (port 22) is enabled. Add rules for any additional services you plan to run. - -== Additional Resources - -For comprehensive information about Azure virtual machine features and advanced configurations, consult the official Azure virtual machine documentation. The https://learn.microsoft.com/en-us/cli/azure/?view=azure-cli-latest[Azure CLI reference guide] provides detailed information about all available commands and parameters for deployments. - From 76f11ec9bb76c5a89566ea5405ed9a65d7324744 Mon Sep 17 00:00:00 2001 From: Bala Konda Reddy M Date: Nov 03 2025 18:47:07 +0000 Subject: [PATCH 3/5] Add docs for fedora on Microsoft Azure Signed-off-by: Bala Konda Reddy M --- diff --git a/modules/ROOT/pages/azure.adoc b/modules/ROOT/pages/azure.adoc index 483c645..8dbaeae 100644 --- a/modules/ROOT/pages/azure.adoc +++ b/modules/ROOT/pages/azure.adoc @@ -5,15 +5,9 @@ Microsoft Azure is one of the major cloud platforms where Fedora Cloud images ar Fedora images are directly accessible through Azure's Community Gallery, providing a seamless deployment experience without requiring manual image uploads. -Azure provides a https://azure.microsoft.com/en-us/free/[free tier offering] for new customers, which includes $200 in credits valid for the first 30 days, plus access to popular services free for 12 months. - == Prerequisites -Before deploying Fedora on Microsoft Azure, ensure you have an active Azure account with a valid subscription that includes sufficient quota for virtual machine creation. - -Azure uses resource groups as organizational units for related cloud resources. Resource groups function as containers that group Azure resources such as virtual machines, storage accounts, and network components. This structure allows for consolidated management, billing, and cleanup operations. - For secure access to your Fedora virtual machines, SSH key pairs are required. Azure can generate these automatically during VM creation, or you can provide your own existing keys. @@ -56,12 +50,10 @@ For more control over the deployment process, manually navigate through Azure's Once deployment completes (typically takes 2-3 minutes), Azure displays your VM details including the assigned public IP address. To connect to your Fedora instance: 1. Download your SSH private key when prompted -2. Set appropriate file permissions for security -3. Connect using SSH with the default `azureuser` account +2. Connect to Virtual Machine with default user `azureuser`. [source,bash] ---- -chmod 600 ~/Downloads/your-key-name.pem ssh -i ~/Downloads/your-key-name.pem azureuser@YOUR-PUBLIC-IP ---- @@ -114,10 +106,9 @@ Please follow this https://learn.microsoft.com/en-us/azure/virtual-machines/linu NOTE: Use --image option with specific fedora version /CommunityGalleries/Fedora-5e266ba4-2250-406d-adad-5d73860d958f/Images/// during vm creation. -To connect to your deployed VM, use the generated SSH key: +To connect to your deployed VM, use SSH keys with default user `azureuser`. [source,bash] ---- -chmod 600 ~/.ssh/fedora-azure.pem # Set proper permissions for the SSH key -ssh -i ~/.ssh/fedora-azure.pem azureuser@YOUR-PUBLIC-IP +ssh -i ~/Downloads/your-key-name.pem azureuser@YOUR-PUBLIC-IP ---- From 36d41653a299fbf2b428428f21cecdfab391a47f Mon Sep 17 00:00:00 2001 From: Bala Konda Reddy M Date: Nov 03 2025 18:47:07 +0000 Subject: [PATCH 4/5] Add docs for fedora on Microsoft Azure Signed-off-by: Bala Konda Reddy M --- diff --git a/modules/ROOT/pages/azure.adoc b/modules/ROOT/pages/azure.adoc index 8dbaeae..08ac86d 100644 --- a/modules/ROOT/pages/azure.adoc +++ b/modules/ROOT/pages/azure.adoc @@ -106,9 +106,12 @@ Please follow this https://learn.microsoft.com/en-us/azure/virtual-machines/linu NOTE: Use --image option with specific fedora version /CommunityGalleries/Fedora-5e266ba4-2250-406d-adad-5d73860d958f/Images/// during vm creation. +<<<<<<< HEAD To connect to your deployed VM, use SSH keys with default user `azureuser`. [source,bash] ---- ssh -i ~/Downloads/your-key-name.pem azureuser@YOUR-PUBLIC-IP ---- +======= +>>>>>>> 3999aa1 (Add docs for fedora on Microsoft Azure) From cc91a844b395328d93a15871e7b53866e2a662e2 Mon Sep 17 00:00:00 2001 From: Bala Konda Reddy M Date: Nov 03 2025 18:47:07 +0000 Subject: [PATCH 5/5] Add docs for fedora on Microsoft Azure Signed-off-by: Bala Konda Reddy M --- diff --git a/modules/ROOT/pages/azure.adoc b/modules/ROOT/pages/azure.adoc index 08ac86d..cf194f7 100644 --- a/modules/ROOT/pages/azure.adoc +++ b/modules/ROOT/pages/azure.adoc @@ -104,14 +104,3 @@ az sig image-version list-community \ Please follow this https://learn.microsoft.com/en-us/azure/virtual-machines/linux/tutorial-manage-vm[Virtual Machine Creation] guide from the Azure documentation using Azure CLI NOTE: Use --image option with specific fedora version /CommunityGalleries/Fedora-5e266ba4-2250-406d-adad-5d73860d958f/Images/// during vm creation. - - -<<<<<<< HEAD -To connect to your deployed VM, use SSH keys with default user `azureuser`. - -[source,bash] ----- -ssh -i ~/Downloads/your-key-name.pem azureuser@YOUR-PUBLIC-IP ----- -======= ->>>>>>> 3999aa1 (Add docs for fedora on Microsoft Azure)