Deploying and managing RHEL systems in hybrid clouds

Procedure

1. Access Hybrid Cloud Console Insights, click Content → Repositories. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Click Add repositories. The Add custom repositories wizard opens.
3. In the Name field provide a name for your custom repository.

4. In the Repository type, select:

   Snapshotting

   Enables creating a daily snapshot of this repository if this repository has updates since the last snapshot. That enables you to create Image Blueprints with consistent repository content.

   Introspect only

   Disables snapshots for this repository.

   Upload

   Enables uploading packages to your custom repository. The file must have an rpm extension.

   Note, the Upload option is available only in the Preview mode.

5. If you selected Snapshotting or Introspect only, in the URL field, provide the URL to your repository.
6. Optional: In the Restrict architecture drop-down menu, select an architecture. You can allow all the architectures or restrict it to your system architecture to prevent incorrect repositories availability.
7. Optional: In the Restrict OS version drop-down menu, select an operating system (OS). You can allow all the RHEL versions or select one for your system version to prevent incorrect repositories being available.
8. Optional: Disable Modularity filtering option. When the Modularity filtering option is disabled, you can update packages in this repository even if the packages are part of a module.
9. Optional: In the GPG key field, upload the .txt file with a GPG key or paste the URL or value of an existing GPG key. The GPG key can be used to verify the signed packages of a repository. If you do not provide the GPG key for a repository, your system cannot perform the verification.
10. If you selected Snapshotting or Introspect only, click Save. The Red Hat Hybrid Cloud Console validates the project status. If your repository is marked as Invalid, check the repository URL that you added. For details about the repository status, see Repository status section.

11. If you selected Upload:

    1. Click Save and upload content. The Upload content window opens.
    2. Click Upload, select the rpm files you want to upload, and click Open.
    3. Click Confirm changes when your file uploading is complete.

Procedure

1. Access Hybrid Cloud Console Insights, click Content → Repositories. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Find a repository you want to modify and click Edit in the Options menu.
3. In the Edit custom repository wizard, modify the information you need. Click Save changes.

Procedure

1. Access Hybrid Cloud Console Insights, click Content → Repositories. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Find a repository to delete and click Delete in the Options menu.

Procedure

1. Access Hybrid Cloud Console Insights, click Content → Repositories. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. On the Custom repositories page click the Popular repositories tab.
3. Search for the repository you want to add and click Add.

Procedure

1. Access Hybrid Cloud Console Insights, click Content → Repositories. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. In the Your repositories tab, find the repository containing the snapshot to be removed, and click View all snapshots in the Option menu.
3. In the Snapshot window, select all snapshots that you want to remove from this repository, and click Remove selected snapshots.
4. In the Remove snapshot window, confirm the removal of the selected snapshots and click Remove.

Procedure

1. Access Hybrid Cloud Console Insights, click Content → Repositories. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Find a repository you want to modify and click Introspect Now in the Options menu.

3. The status of that repository changes to In progress that indicates the Hybrid Cloud Console is connecting to the repository and checking for changes.

   The Red Hat Hybrid Cloud Console checks the status of the repositories every 24 hours and again every 8 hours if the status check fails.

Procedure

1. Access Hybrid Cloud Console Insights, click Inventory → Images. The Insights Images dashboard appears. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Click Create blueprint. The wizard for the blueprint creation opens.

3. On the Image output page, select the following options and click Next:

   1. From the Release list, select the release that you want to use.

      Important

      The image builder builds the latest minor version of the selected release.

   2. From the Architecture list, select the architecture that you want to use.
   3. From the Select target environments options, select the environments that you want to use.

4. On the Optional steps page, you can further configure your image with additional customizations. For a complete list, see Optional blueprint customizations.

   To finish creating your image blueprint, click Review and finish to proceed to the Review step.

5. On the Details page, the blueprint name is prefilled in the <distribution>-<architecture>-<datetimeString> format. You can enter a name for the blueprint, and the system checks for validity and duplicity against already existing blueprint names. Click Next.

6. On the Review page, verify the image details about the image creation and from the Create blueprint drop-down menu, select one of the following options:

   Create blueprint

   Create the blueprint and save the customizations for your blueprint.

   Create blueprint and build image(s)

   Create the blueprint, save the customizations for your blueprint and build images for the target environment or environments that you choose.

   The system verifies the build manifest of the image. After it reaches 100%, the image appears in the build queue.

   Insights Images service starts to compose a RHEL image for the selected architecture. After the image build is ready, you can see the images related to the parent blueprint in the Images dashboard.

Procedure

1. Access Hybrid Cloud Console Insights, click Inventory → Images. The Insights Images dashboard appears. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Search for the blueprint that you want to edit. You can use the Search field to search for the blueprint name.
3. Click the blueprint that you want to edit.
4. Click Edit blueprint. You are redirected to the Review page.
5. From the navigation menu, select the section that you want to edit.
6. After making the changes, click the Review page.

7. Click Save changes to the blueprint.

   The images related to the parent blueprint that you modified will be rebuilt and updated with the new changes.

Procedure

1. Access Hybrid Cloud Console Insights, click Inventory → Images. The Insights Images dashboard appears. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Search for the blueprint that you want to edit. You can use the Search field to search for the blueprint name.
3. Click the blueprint that you want to edit.
4. Click Edit blueprint. You are redirected to the Review page.

5. Make the changes to the blueprint and select one of the options:

   Save

   Save the customizations for your blueprint.

   Save and build image

   Save the customizations for your blueprint and build images from the target environments that you chose.

Procedure

1. Access Hybrid Cloud Console Insights, click Inventory → Images. The Insights Images dashboard appears. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Click Import. The Import pipeline window opens.

3. Optional: To add custom repositories from the blueprint to your repositories, select the Import missing custom repositories after file upload checkbox.

   Warning

   If the blueprint contains missing repositories, the images that you create from this blueprint might not work as expected.

4. Upload the blueprint that you want to import either drag and drop or by selecting the file from your local storage.
5. Click Review and finish.

Procedure

1. Access Hybrid Cloud Console Insights, click menu:[Images]. The Insights Images dashboard appears. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Search for the blueprint that you want to download. You can use the Search field to search for the blueprint name.
3. Click the blueprint that you want to download.

4. From the More options menu, select the "Download blueprint" option.

   The blueprint is saved as a file in the .json format to the local storage that you define in your web browser.

Procedure

1. Access Hybrid Cloud Console Insights, click Inventory → Images. The Insights Images dashboard appears. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Search for the blueprint that you want to delete. You can use the Search field to search for the blueprint name.
3. Click the blueprint that you want to delete.
4. From the More options menu, select the "Delete blueprint" option.
5. Confirm the deletion by clicking Delete.

Procedure

1. Access Hybrid Cloud Console Insights, click Inventory → Images. The list of existing blueprints appears. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.

2. Select the blueprint that you want to build an image from.

   1. Optionally, you can select the blueprint version from the dropdown menu.

3. Click Build images. A pop-up alert informs that the image is being built.

   After the image process status is marked as Ready, you can use it in your deployments.

Procedure

1. Access your AWS account and navigate to Service → EC2.
2. In the navigation bar, verify if you are under the correct region: us-east-1.
3. Click Images, and choose AMIs. The dashboard with the Owned by me images opens.

4. From the drop-down menu, choose Private images.

   You can see the image successfully shared with the AWS account you specified.

Procedure

1. From the drop-down menu, under Private images, locate the image that you shared to the AWS account you specified.
2. Select the image you want to launch.
3. On the top of the panel, click Launch. You are redirected to the Choose an Instance Type window.
4. Choose the instance type according to the resources you need to launch your image. Click Review and Launch.
5. Review your instance launch details. You can edit each section, such as Security, Storage, for example, if you need to make any changes. After you finish the review, click Launch.

6. To launch the instance, you must select a public key to access it.

   Create a new key pair in EC2 and attach it to the new instance.

   1. From the drop-down menu list, select Create a new key pair.
   2. Enter the name to the new key pair. It generates a new key pair.
   3. Click Download Key Pair to save the new key pair on your local system.

7. Then, you can click Launch Instance to launch your instance.

   You can check the status of the instance, it shows as Initializing.

8. After the instance status is running, the Connect button turns available.

9. Click Connect. A popup window appears with instructions on how to connect by using SSH.

   1. Select the preferred connection method to A standalone SSH client and open a terminal.

   2. In the location you store your private key, make sure that your key is publicly viewable for SSH to work. To do so, run the command:

      $ chmod 400 <your-instance-name.pem>

      Copy to Clipboard Toggle word wrap

   3. Connect to your instance by using its Public DNS:

      $ ssh -i "<your-instance-name.pem> ec2-user@<your-instance-IP-address>"

      Copy to Clipboard Toggle word wrap

   4. Type yes to confirm that you want to continue connecting.

      As a result, you are connected to your instance over SSH.

Procedure

1. From the list of Private images, select the image you want to copy.
2. On the top of the panel, click Actions.
3. From the drop-down menu, choose Copy AMI. A pop-up window appears.

4. Choose the Destination region and click Copy AMI.

   After the copying process is complete, you are provided with the new AMI ID. You can launch a new instance in the new region.

   Note

   When you copy an image to a different region, it results in a separate and new AMI in the destination region, with a unique AMI ID.

Procedure

1. From the Images table, select the image you want to share with other regions.
2. From the Node options menu (⫶), select Share to new region. The Share to new region wizard opens.

3. From the Select region dropdown menu, select the region to share the image.

   You can choose more than one region to share your image with.

4. Click Share.

   Your image is built, uploaded to AWS, and shared to the regions you selected.

   Note

   The shared image expires in 14 days.

5. To ensure that you can access the image permanently, copy the Red Hat image to your own AWS account.

Procedure

1. Access Hybrid Cloud Console Insights, click Inventory → Images. The Insights image builder dashboard appears. For details on how to access the Red Hat Hybrid Cloud Console, see Getting started with the Red Hat Hybrid Cloud Console.
2. Click Create blueprint. The Image output wizard opens.

3. On the Image output page, complete the following steps:

   1. From the Release list, select the release that you want to use.

   2. From the Select target environments option, select Microsoft Azure.

      Click Next.

4. On the Target Environment - Microsoft Azure window, to add Image Builder as an authorized application, select one of the following share method options:

   1. Use an account configured from Sources:

      1. From the Source name dropdown menu, select the source that you previously configured. See Connecting Microsoft Azure account to the Red Hat Hybrid Cloud Console.

5. The Azure tenant GUID, the Subscription ID, and the Resource group are automatically completed, and the Authorize image builder button becomes available.

   Image builder checks if your Tenant GUID is correctly formatted and the Authorize image builder button becomes available.

   1. Manually enter the account information:

      1. Enter your Azure Tenant GUID.

         Image builder checks if your Tenant GUID is correctly formatted and the Authorize image builder button becomes available.

   2. One time action: Click Authorize image builder to authorize Image Builder to push images to the Microsoft Azure cloud.

      This redirects you to the Microsoft Azure portal.

      1. Login with your credentials.
      2. Click Accept the Permission requested. Note that, if you already went through the authentication process before, you will not see the Permission requested. It is already granted.

   3. Confirm that Image Builder is authorized for your tenant.

      1. In the search bar, search for Azure Active Directory.
      2. From the Services menu, click Microsoft Entra ID, from the left menu. The Azure Active Directory page opens.
      3. Search for Insights image builder and confirm it is authorized.
      4. In the Azure Active Directory, from the Services list, select Enterprise applications.
      5. In the Enterprise applications page, from the Manage list menu, click All applications. You can see Red Hat Image Builder is authorized in the Microsoft Azure cloud.

   4. Add the Red Hat Image Builder as a contributor to your Resource Group.

      1. In the search bar, type Resource Groups and select the first entry under Services. This redirects you to the Resource Groups dashboard.
      2. Search and select your Resource Group by name.
      3. On the lateral menu, click Access control (IAM) to add a permission to the Red Hat Image Builder application to access your resource group.
      4. From the menu, click the tab Role assignments.
      5. Click +Add.

      6. From the dropdown menu, choose Add role assignment. A menu appears on the left side.

         Select role

         Assign the Contributor role.

         Assign access to

         Select the option Assign access to user, group, and service principal.

         Members

         Click +Select members and type Red Hat in the search bar. Click enter.

         Select

         Red Hat Image Builder application.

         The Red Hat Image Builder application is now authorized to push images to the Microsoft Azure cloud.

         Note

         The Red Hat Image Builder application can locate resources only when the account administrator adds the shared application as a contributor under the IAM section of the resource group.

Verification

1. After you access your Microsoft Azure Account, you can see that the image successfully shared with the resource group account you specified.

   Note

   If the image is not visible there, you might have issues with the upload process. Return to the Insights image builder dashboard and check if the image is marked as Ready.

Procedure

1. From the Insights image builder dashboard, copy the image UUID of the image that you created.
2. Access /composes/{composeId} API endpoint.
3. Click Try it Out to activate the composeId string path.
4. Enter the UUID into the composes/{composeId} field in the API endpoint.

5. Click Execute. The API endpoint generates a response in the Response body, for example:

   {
     "image_status": {
       "status": "success",
       "upload_status": {
         "options": {
           "image_name": "composer-api-03f0e19c-0050-4c8a-a69e-88790219b086",
           "project_id": "red-hat-image-builder"
         },
         "status": "success",
         "type": "gcp"
       }
     }
   }

   Copy to Clipboard Toggle word wrap
6. From the Response body field, copy the image_name and project_id to access the image from the Google Cloud Platform environment.

7. From your browser, access Google Cloud Shell and set your Google Cloud Platform Project ID as the default GCP project. You can find the Product ID of your project by accessing the Google Cloud Platform dashboard.

   $ gcloud config set project PROJECT_ID

   Copy to Clipboard Toggle word wrap
8. In the Authorize Cloud Shell window prompt, click Authorize to allow this and future calls that require your credentials.

9. Create a VM instance with the image by using the gcloud command in the Google Cloud Shell:

   $ gcloud compute instances create INSTANCE_NAME \
     --image-project PROJECT_ID_FROM_RESPONSE \
     --image IMAGE_NAME \
     --zone GCP_ZONE

   Copy to Clipboard Toggle word wrap

   Where:

   • INSTANCE_NAME is the name for your instance;
   • PROJECT_ID_FROM_RESPONSE is the project_id generated by Response body;
   • IMAGE_NAME is the image_name generated by Response body;
   • GCP_ZONE is the GCP zone in which the instance will be created.

Verification

1. Verify that Compute Engine created the VM:

   $ gcloud compute instances describe INSTANCE_NAME

   Copy to Clipboard Toggle word wrap

2. Connect to the VM instance using SSH:

   $ gcloud compute ssh --project=PROJECT_ID --zone=ZONE INSTANCE_NAME

   Copy to Clipboard Toggle word wrap

Procedure

1. From the Images dashboard, copy the UUID image of the image you created.
2. Access /composes/{composeId} API endpoint.
3. Click Try it Out to activate the composeId string path.
4. Enter the UUID into the composes/{composeId} field in the API endpoint.

5. Click Execute. The API endpoint generates a response in the Response body, for example:

   {
     "image_status": {
       "status": "success",
       "upload_status": {
         "options": {
           "image_name": "composer-api-03f0e19c-0050-4c8a-a69e-88790219b086",
           "project_id": "red-hat-image-builder"
         },
         "status": "success",
         "type": "gcp"
       }
     }
   }

   Copy to Clipboard Toggle word wrap

6. From the Response body field, copy the image_name and project_id to access the image from the Google Cloud Platform environment. From the Response body:

   "image_name": "composer-api-03f0e19c-0050-4c8a-a69e-88790219b086",
   "project_id": "red-hat-image-builder"

   Copy to Clipboard Toggle word wrap
7. From your browser, access Google Cloud Shell.

8. Set your Google Cloud Platform Project ID as the default GCP project. You can find the Product ID of your project by accessing the Google Cloud Platform dashboard.

   $ gcloud config set project PROJECT_ID

   Copy to Clipboard Toggle word wrap
9. In the Authorize Cloud Shell window prompt, click Authorize to allow this and future calls that require your credentials.

10. Copy the image to your project by using the gcloud command:

    $ gcloud compute images create MY_IMAGE_NAME \
      --source-image-project red-hat-image-builder \
      --source-image IMAGE_NAME

    Copy to Clipboard Toggle word wrap

    Where:

    • MY_IMAGE_NAME is the name you give to your instance;
    • red-hat-image-builder is the project_id generated by Response body;
    • IMAGE_NAME is the image_name generated by Response body;

Procedure

1. From the Images dashboard, select the image from which you want to create your customized image.

2. Click the Node options menu (⫶) and select Re-create image. The Create image wizard opens.

   Note

   If the image status is Expired, click the Re-create image button.

   1. Optional: You can customize the new image by using the Navigation panel to open a step and making changes. Click Next.

   2. On the Review page, click Create image.

      The Insights Images dashboard opens. The image build starts to re-create the image and lists the following information:

      • Image name
      • UUID
      • Cloud target environment
      • Image operating system release
      • Status of the image creation

Procedure

1. From the Images table, select the image that you want to download as a .json compose request.

2. Click the Node options (⫶) menu and select Download compose request (.json).

   The .json compose request is now saved to your host server. To use the image builder API, see Using hosted image builder via its API.

Procedure

1. Access the directory where you downloaded your .ova image.

2. Create a file named metadata.yaml and add the following information to this file:

   instance-id: cloud-vm
   local-hostname: vmname

   Copy to Clipboard Toggle word wrap

3. Create a file userdata.yaml. Add the following information to the file:

   #cloud-config
   users:
   - name: admin
     sudo: "ALL=(ALL) NOPASSWD:ALL"
     ssh_authorized_keys:
     - ssh-rsa AAA...fhHQ== your.email@example.com

   Copy to Clipboard Toggle word wrap

   This file contains the administrator or root user credentials with no password that you can use to access your system after the first boot and create additional users later. The ssh_authorized_keys field is your SSH public key. You can find your SSH public key in ~/.ssh/id_rsa.pub.

Procedure

1. Generate an access token for API queries by following the step in Generating an access token for the Image Builder API queries.

   Important

   Access tokens expire after fifteen (15) minutes. The expiration is included within the JSON response. You must repeat the process of obtaining an access token approximately every ten (10) minutes so that the token is rotated before it expires.

2. In your system, create a file in the .json format to create an image. The following example shows how to create an up-to-date RHEL 9.4 ova image for x86_64 CPU architecture.

   $ request.json
   {
       "image_name": "ova_image_name",
       "distribution": "rhel-94",
       "image_requests": [
           {
               "architecture": "x86_64",
               "image_type": "vsphere-ova",
               "upload_request": {
                   "type": "vmdk",
                   "options": {}
               }
           }
       ],
       "customizations": {
           "users": [
               {
                   "name": "user-name",
                   "ssh_key": "ssh-rsa AAAAB...qfGI+vk",
                   "password": "password"
               }
           ]
       }
   }

   Copy to Clipboard Toggle word wrap

3. Send the compose request to the image builder API:

   $ curl --silent \
       --request POST \
       --header "Authorization: Bearer $access_token" \
       --header "Content-Type: application/json" \
       --data @request.json \
       https://console.redhat.com/api/image-builder/v1/compose

   Copy to Clipboard Toggle word wrap

   If the request is successful, you can see an output similar to the following, that is the image ID:

   {"id":"fd4ecf3c-f0ce-43dd-9fcc-6ad11208b939"}

   Copy to Clipboard Toggle word wrap

4. Check the status of the image building:

   $ curl \
       --silent \
       --header "Authorization: Bearer $access_token" \
       "https://console.redhat.com/api/image-builder/v1/composes/$compose_id" \
     | image_ID.

   Copy to Clipboard Toggle word wrap

   If the request is successful, you can see an output similar to the following, that is the image ID:

   {"id":"fd4ecf3c-f0ce-43dd-9fcc-6ad11208b939"}

   Copy to Clipboard Toggle word wrap

   You can also check the image building progress by accessing Red Hat Hybrid Cloud Console.

   After the image builds, you can see the following output:

   If the request is successful, you can see an output similar to the following, that is the image ID:

   {
       "image_status": {
           "status": "success",
           "upload_status": {
               "options": {
                   "url": "https://image-builder-service-production.s3.amazonaws.com/composer-api-76...-disk.ova?e42..."
               },
               "status": "success",
               "type": "aws.s3"
           }
       }
   }

   Copy to Clipboard Toggle word wrap

5. After finishing the image creation, download the image.

   $ curl --location --output vsphere-ova.vmdk  \
       “https://image-builder-service-production.s3.amazonaws.com/composer-api-76...-disk.ova?e42...”

   Copy to Clipboard Toggle word wrap

   The image is saved to your system and ready to be used.

Procedure

1. Export the metadata.yaml and userdata.yaml files to the environment, compressed with gzip, encoded in base64 as follows. They will be used in further steps.

   export METADATA=$(gzip -c9 <metadata.yaml | { base64 -w0 2>/dev/null || base64; }) \
   USERDATA=$(gzip -c9 <userdata.yaml | { base64 -w0 2>/dev/null || base64; })

   Copy to Clipboard Toggle word wrap

2. Launch the image on vSphere with the metadata.yaml and userdata.yaml files:

   1. Import the .vmdk image in to vSphere:

      $ govc import.vmdk ./composer-api.vmdk foldername

      Copy to Clipboard Toggle word wrap

   2. Create the VM in vSphere without powering it on:

      govc vm.create \
      -net.adapter=vmxnet3 \
      -m=4096 -c=2 -g=rhel8_64Guest \
      -firmware=bios -disk=”foldername/composer-api.vmdk” \
      -disk.controller=ide -on=false \
       vmname

      Copy to Clipboard Toggle word wrap

   3. Change the VM to add ExtraConfig variables, the cloud-init config:

      govc vm.change -vm vmname \
      -e guestinfo.metadata="${METADATA}" \
      -e guestinfo.metadata.encoding="gzip+base64" \
      -e guestinfo.userdata="${USERDATA}" \
      -e guestinfo.userdata.encoding="gzip+base64"

      Copy to Clipboard Toggle word wrap

   4. Power-on the VM:

      govc vm.power -on vmname

      Copy to Clipboard Toggle word wrap

   5. Retrieve the VM IP address:

      HOST=$(govc vm.ip vmname)

      Copy to Clipboard Toggle word wrap

   6. Use SSH to log in to the VM, using the user-data specified in cloud-init file configuration:

      $ ssh admin@HOST

      Copy to Clipboard Toggle word wrap

Procedure

1. In the vSphere Client, from the Actions menu, select Deploy OVF Template.
2. On the Deploy OVF Template page, complete the settings for each configuration option and click Next.

3. Click Finish. The .ova image starts to be deployed.

   After the image deployment is complete, you have a new virtual machine (VM) from the .ova image.

4. In the deployed image page, perform the following steps:

   1. From the Actions menu, select Edit Setting.

   2. On the Virtual Hardware tab, configure resources such as CPU, memory, add a new network adapter, between others of your choice.

      1. On the CD/DVD drive 1 option, attach a CD or DVD Drive that contains a cloud-init.iso, to provision a user on startup.

         The VM is now ready to boot with the username and password from the cloud-init.iso file.

Procedure

1. Access the directory where you downloaded your QCOW2 image.

2. Create a file named meta-data. Add the following information to this file:

   instance-id: nocloud
   local-hostname: vmname

   Copy to Clipboard Toggle word wrap

3. Create a file named user-data. Add the following information to the file:

   #cloud-config
   user: admin
   password: password
   chpasswd: {expire: False}
   ssh_pwauth: True
   ssh_authorized_keys:
     - ssh-rsa AAA...fhHQ== your.email@example.com

   Copy to Clipboard Toggle word wrap
   • ssh_authorized_keys is your SSH public key. You can find your SSH public key in ~/.ssh/id_rsa.pub.

4. Use the genisoimage command to create an ISO image that includes the user-data and meta-data files.

   # genisoimage -output cloud-init.iso -volid cidata -joliet -rock user-data meta-data
   
   I: -input-charset not specified, using utf-8 (detected in locale settings)
   Total translation table size: 0
   Total rockridge attributes bytes: 331
   Total directory bytes: 0
   Path table size(bytes): 10
   Max brk space used 0
   183 extents written (0 MB)

   Copy to Clipboard Toggle word wrap

5. Create a new VM from the KVM Guest Image using the virt-install command. Include the ISO image you created on step 4 as an attachment to the VM image.

   # virt-install \
       --memory 4096 \
       --vcpus 4 \
       --name myvm \
       --disk composer-api.qcow2,device=disk,bus=virtio,format=qcow2 \
       --disk cloud-init.iso,device=cdrom \
       --os-variant rhel1-latest \
       --virt-type kvm \
       --graphics none \
       --import

   Copy to Clipboard Toggle word wrap

   Where,

   • --graphics none - indicates that it is a headless RHEL Virtual Machine.
   • --vcpus 4 - indicates that it uses 4 virtual CPUs.
   • --memory 4096 - indicates that it uses 4096 MB RAM.

6. The VM installation starts:

   Starting install...
   Connected to domain myvm
   ...
   [  OK  ] Started Execute cloud user/final scripts.
   [  OK  ] Reached target Cloud-init target.
   
   Red Hat Enterprise Linux 1-latest (Ootpa)
   Kernel 4.18.0-221.el8.x86_64 on an x86_64

   Copy to Clipboard Toggle word wrap

Procedure

1. Access the directory where you downloaded your ISO image.
2. Place the bootable ISO image file on a USB flash drive.
3. Connect the USB flash drive to the port of the computer you want to boot.
4. Boot the ISO image from the USB flash drive.

5. Perform the steps to install the customized bootable ISO image.

   The boot screen shows you the following options:

   • Install Red Hat Enterprise Linux 1-latest
   • Test this media & install Red Hat Enterprise Linux 1-latest

Procedure

1. In the Oracle Cloud UI dashboard, click Compute > Custom Images.
2. On the Custom Images dashboard, click Import image.

3. On the Import image window, set the following configuration:

   1. Select the Import from an object storage URL option.
   2. In the Object Storage URL field, paste the URL given by Insights Images into it.
   3. Choose the QCOW2 image type.
   4. Under Launch mode, select the Paravirtualized mode option.
4. Click Import Image.

Procedure

1. In the AWS Management Console, navigate to Compute → EC2 → Images.
2. Copy your custom image to your AWS account to create a permanent copy. For details, follow the Copying your customized RHEL system image for AWS to a different region on your AWS EC2 procedure.
3. From the AWS Management Console, launch your image as an instance.

Procedure

1. Access the Images on the Microsoft Azure portal, and click on your custom image.
2. On the Overview dashboard, click Create VM.
3. In the Microsoft Azure wizard, configure the settings for the new virtual machine that you want to launch.
4. On the Review + create tab, review the information about your image and click Create.

Procedure

1. Log in to your Google Cloud account from your terminal:

   $ gcloud auth login

   Copy to Clipboard Toggle word wrap

2. Set the Google project where you want to create your image:

   $ gcloud config set project your-project-name

   Copy to Clipboard Toggle word wrap

3. Create the custom image:

   $ gcloud compute images create image-name --source-image composer-api-image-builder-uuid --source-image-project red-hat-image-builder

   Copy to Clipboard Toggle word wrap

   Copy the image-builder-uuid from the ComposeID API endpoint.

4. Access the Google Cloud Console from your browser, and locate your new image in Compute Engine → Images.
5. To launch a new virtual machine from your image, click Actions → Create Instance.