|
| 1 | +--- |
| 2 | +title: Red Hat Enterprise Linux bring-your-own-susbcription images |
| 3 | +description: Learn about bring-your-own-subscription images for Red Hat Enterprise Linux on Azure |
| 4 | +services: virtual-machines-linux |
| 5 | +documentationcenter: '' |
| 6 | +author: asinn826 |
| 7 | +manager: BorisB2015 |
| 8 | +editor: '' |
| 9 | + |
| 10 | +ms.assetid: f495f1b4-ae24-46b9-8d26-c617ce3daf3a |
| 11 | +ms.service: virtual-machines-linux |
| 12 | +ms.devlang: na |
| 13 | +ms.topic: article |
| 14 | +ms.tgt_pltfrm: vm-linux |
| 15 | +ms.workload: infrastructure-services |
| 16 | +ms.date: 6/6/2019 |
| 17 | +ms.author: alsin |
| 18 | + |
| 19 | +--- |
| 20 | + |
| 21 | +# Red Hat Enterprise Linux bring-your-own-subscription images in Azure |
| 22 | +Red Hat Enterprise Linux (RHEL) images are available in Azure via a pay-as-you-go (PAYG) or bring-your-own-subscription (BYOS) model. This document provides an overview of the BYOS images in Azure. |
| 23 | + |
| 24 | +## Important points to consider |
| 25 | + |
| 26 | +- The RHEL BYOS images provided in this program are production-ready RHEL images similar the RHEL PAYG images in the Azure Gallery/Marketplace. The registration process to obtain the images is in preview. |
| 27 | + |
| 28 | +- The images follow our current policies described in [Red Hat Enterprise Linux images on Azure](./redhat-images.md) |
| 29 | + |
| 30 | +- Standard support policies apply to VMs created from these images |
| 31 | + |
| 32 | +- The VMs provisioned from RHEL BYOS images do not carry RHEL fees associated with RHEL PAYG images |
| 33 | + |
| 34 | +- The images are unentitled, so you must use subscription-manager to register and subscribe the VMs to get updates from Red Hat directly |
| 35 | + |
| 36 | +- It is currently not possible to dynamically switch between BYOS and PAYG billing models for Linux images. Redeploying the VM from the respective image is required to switch the billing model |
| 37 | + |
| 38 | +- Azure Disk Encryption (ADE) is supported on these RHEL BYOS images. ADE support is currently in preview. You must register with Red Hat using subscription-manager before configuring ADE. Once registered, to configure ADE refer to: [Enable Azure Disk Encryption for Linux IaaS VMs](https://docs.microsoft.com/azure/virtual-machines/linux/disk-encryption-overview) |
| 39 | + |
| 40 | +- While the images won’t change (beyond standard updates and patches), the registration process is in preview and the flow will be further improved to streamline the process |
| 41 | + |
| 42 | +- You have full control of the VMs already provisioned from these images or its snapshots regardless of the final implementation |
| 43 | + |
| 44 | +## Requirements and conditions to access the RHEL BYOS images |
| 45 | + |
| 46 | +1. Get familiar with the [Red Hat Cloud Access program](https://www.redhat.com/en/technologies/cloud-computing/cloud-access) terms and register at [Red Hat's Cloud Access registration page](https://access.redhat.com/cloude/manager/image_imports/new). |
| 47 | + |
| 48 | +1. Complete the [RHEL BYOS access request form](https://aka.ms/rhel-byos). You will need to have on hand your Red Hat account number as well as your Azure subscription(s) that you with to access the RHEL BYOS images with. |
| 49 | + |
| 50 | +1. Upon review and approval by both Red Hat and Microsoft, your Azure subscription(s) will be enabled for image access. |
| 51 | + |
| 52 | +### Expected time for image access |
| 53 | + |
| 54 | +Upon completing the RHEL BYOS form and accepting terms, Red Hat will validate your eligibility for the BYOS images within three business days and, if valid, you will receive access to the BYOS images within one business day afterward. |
| 55 | + |
| 56 | +## Use the RHEL BYOS images from the Azure Portal |
| 57 | + |
| 58 | +1. After your subscription is enabled for RHEL BYOS images, you can locate it in the [Azure portal](https://portal.azure.com) by navigating to **Create a Resource** and then **See all**. |
| 59 | + |
| 60 | +1. At the top of the page, you will see that you have private offers. |
| 61 | + |
| 62 | +  |
| 63 | + |
| 64 | +1. You can click on the purple link or scroll down to the bottom of the page to see your private offers. |
| 65 | + |
| 66 | +1. The rest of provisioning in the UI will be no different to any other existing Red Hat image. Choose your RHEL version and follow the prompts to provision your VM. This process will also let you accept the terms of the image at the final step. |
| 67 | + |
| 68 | +>[!NOTE] |
| 69 | +>These steps so far will not enable your RHEL BYOS image for programmatic deployment – an additional step will be required as described in the “Additional Information” section below. |
| 70 | +
|
| 71 | +The rest of this document focuses on the CLI method to provision and accept terms on the image. The UI and CLI are fully interchangeable as far as the final result (a provisioned RHEL BYOS VM) is concerned. |
| 72 | + |
| 73 | +## Use the RHEL BYOS images from the Azure CLI |
| 74 | +The following set of instructions will walk you through the initial deployment process for a RHEL VM using the Azure CLI. These instructions assume that you have the [Azure CLI installed](https://docs.microsoft.com/cli/azure/install-azure-cli). |
| 75 | + |
| 76 | +>[!IMPORTANT] |
| 77 | +>Make sure you use all lowercase letters in the publisher, offer, plan, and image references for all the following commands |
| 78 | +
|
| 79 | +1. Check that you are in your desired subscription: |
| 80 | + ```azurecli |
| 81 | + az account show -o=json |
| 82 | + ``` |
| 83 | +
|
| 84 | +1. Create a resource group for your RHEL BYOS VM: |
| 85 | + ```azurecli |
| 86 | + az group create --name <name> --location <location> |
| 87 | + ``` |
| 88 | +
|
| 89 | +1. Accept the image terms: |
| 90 | + ```azurecli |
| 91 | + az vm image terms accept --publisher redhat --offer rhel-byos --plan <SKU value here> -o=jsonc |
| 92 | +
|
| 93 | + # Example: |
| 94 | + az vm image terms accept --publisher redhat --offer rhel-byos --plan rhel-lvm75 -o=jsonc |
| 95 | +
|
| 96 | + OR |
| 97 | +
|
| 98 | + az vm image terms accept --urn RedHat:rhel-byos:rhel-lvm8:8.0.20190620 |
| 99 | + ``` |
| 100 | + >[!NOTE] |
| 101 | + >These terms need to be accepted *once per Azure subscription, per image SKU*. |
| 102 | +
|
| 103 | +1. (Optional) Validate your VM deployment with the following command : |
| 104 | + ```azurecli |
| 105 | + az vm create -n <VM name> -g <resource group name> --image <image urn> --validate |
| 106 | +
|
| 107 | + # Example: |
| 108 | + az vm create -n rhel-byos-vm -g rhel-byos-group --image RedHat:rhel-byos:rhel-lvm75:7.5.20190620 |
| 109 | + ``` |
| 110 | +
|
| 111 | +1. Provision your VM by running the same command as above without the `--validate` argument: |
| 112 | + ```azurecli |
| 113 | + az vm create -n <VM name> -g <resource group name> --image <image urn> --validate |
| 114 | + ``` |
| 115 | +
|
| 116 | +1. SSH into your VM and verify that you have an unentitled image. TO do this, run `sudo yum repolist`. The output will ask you to use subscription-manager to register the VM with Red Hat. |
| 117 | +
|
| 118 | +## Additional information |
| 119 | +- If you attempt to provision a VM on a subscription that is not enabled for this offer, you will get the following error and you should contact Microsoft or Red Hat to enable your subscription. |
| 120 | + ``` |
| 121 | + "Offer with PublisherId: redhat, OfferId: rhel-byos, PlanId: rhel-lvm75 is private and can not be purchased by subscriptionId: GUID" |
| 122 | + ``` |
| 123 | +
|
| 124 | +- If you create a snapshot from the RHEL BYOS image AND publish the image in [Shared Image Gallery](https://docs.microsoft.com/azure/virtual-machines/linux/shared-image-galleries), you will need to provide plan information that matches the original source of the snapshot. For example, the command might look like (note the plan parameters in the final line): |
| 125 | + ```azurecli |
| 126 | + az vm create –image \ |
| 127 | + "/subscriptions/GUID/resourceGroups/GroupName/providers/Microsoft.Compute/galleries/GalleryName/images/ImageName/versions/1.0.0" \ |
| 128 | + -g AnotherGroupName --location EastUS2 -n VMName \ |
| 129 | + --plan-publisher redhat --plan-product rhel-byos --plan-name rhel-lvm75 |
| 130 | + ``` |
| 131 | +
|
| 132 | +- If you are using automation to provision VMs from the RHEL BYOS images, you will need to provide plan parameters similar to what was shown above. For example, if you are using Terraform, you would provide the plan information in a [plan block](https://www.terraform.io/docs/providers/azurerm/r/virtual_machine.html#plan). |
| 133 | +
|
| 134 | +## Next steps |
| 135 | +* Learn more about the [Azure Red Hat Update Infrastructure](./redhat-rhui.md). |
| 136 | +* To learn more about the Red Hat images in Azure, go to the [documentation page](./redhat-images.md). |
| 137 | +* Information on Red Hat support policies for all versions of RHEL can be found on the [Red Hat Enterprise Linux Life Cycle](https://access.redhat.com/support/policy/updates/errata) page. |
0 commit comments