Chapter 15. Provisioning Cloud Instances on Google Compute Engine Red Hat Satellite can interact with Google Compute Engine (GCE), including creating new virtual machines and controlling their power management states. You can only use golden images supported by Red Hat with Satellite for creating GCE hosts. Prerequisites You can use synchronized content repositories for Red Hat Enterprise Linux. For more information, see Syncing Repositories in the Content Management Guide . Provide an activation key for host registration. For more information, see Creating An Activation Key in the Content Management guide. In your GCE project, configure a service account with the necessary IAM Compute role. For more information, see Compute Engine IAM roles in the GCE documentation. In your GCE project-wise metadata, set the enable-oslogin to FALSE . For more information, see Enabling or disabling OS Login in the GCE documentation. Optional: If you want to use Puppet with GCE hosts, navigate to Administer > Settings > Puppet and enable the Use UUID for certificates setting to configure Puppet to use consistent Puppet certificate IDs. Based on your needs, associate a finish or user_data provisioning template with the operating system you want to use. For more information about provisioning templates, see Provisioning Templates in Provisioning Hosts . 15.1. Installing Google GCE Plugin Install the Google GCE plugin to attach an GCE compute resource provider to Satellite. This allows you to manage and deploy hosts to GCE. Procedure Install the Google GCE compute resource provider on your Satellite Server: Optional: In the Satellite web UI, navigate to Administer > About and select the Compute Resources tab to verify the installation of the Google GCE plugin. 15.2. Adding a Google GCE Connection to Satellite Server Use this procedure to add Google Compute Engine (GCE) as a compute resource in Satellite. To use the CLI instead of the Satellite web UI, see the CLI procedure . Procedure In Google GCE, generate a service account key in JSON format. Copy the file from your local machine to Satellite Server: On Satellite Server, change the owner for your service account key to the foreman user: On Satellite Server, configure permissions for your service account key to ensure that the file is readable: On Satellite Server, restore SELinux context for your service account key: In the Satellite web UI, navigate to Infrastructure > Compute Resources and click Create Compute Resource . In the Name field, enter a name for the compute resource. From the Provider list, select Google . Optional: In the Description field, enter a description for the resource. In the Google Project ID field, enter the project ID. In the Client Email field, enter the client email. In the Certificate Path field, enter the path to the service account key. For example, /usr/share/foreman/ gce_key .json . Click Load Zones to populate the list of zones from your GCE environment. From the Zone list, select the GCE zone to use. Click Submit . CLI procedure In Google GCE, generate a service account key in JSON format. Copy the file from your local machine to Satellite Server: On Satellite Server, change the owner for your service account key to the foreman user: On Satellite Server, configure permissions for your service account key to ensure that the file is readable: On Satellite Server, restore SELinux context for your service account key: Use the hammer compute-resource create command to add a GCE compute resource to Satellite: 15.3. Adding Google Compute Engine Images to Satellite Server To create hosts using image-based provisioning, you must add information about the image, such as access details and the image location, to your Satellite Server. To use the CLI instead of the Satellite web UI, see the CLI procedure . Procedure In the Satellite web UI, navigate to Infrastructure > Compute Resources and click the name of the Google Compute Engine connection. Click Create Image . In the Name field, enter a name for the image. From the Operating System list, select the base operating system of the image. From the Architecture list, select the operating system architecture. In the Username field, enter the SSH user name for image access. Specify a user other than root , because the root user cannot connect to a GCE instance using SSH keys. The username must begin with a letter and consist of lowercase letters and numbers. From the Image list, select an image from the Google Compute Engine compute resource. Optional: Select the User Data checkbox if the image supports user data input, such as cloud-init data. Click Submit to save the image details. CLI procedure Create the image with the hammer compute-resource image create command. With the --username option, specify a user other than root , because the root user cannot connect to a GCE instance using SSH keys. The username must begin with a letter and consist of lowercase letters and numbers. 15.4. Adding Google GCE Details to a Compute Profile Use this procedure to add Google GCE hardware settings to a compute profile. When you create a host on Google GCE using this compute profile, these settings are automatically populated. To use the CLI instead of the Satellite web UI, see the CLI procedure . Procedure In the Satellite web UI, navigate to Infrastructure > Compute Profiles . In the Compute Profiles window, click the name of an existing compute profile, or click Create Compute Profile , enter a Name , and click Submit . Click the name of the GCE compute resource. From the Machine Type list, select the machine type to use for provisioning. From the Image list, select the image to use for provisioning. From the Network list, select the Google GCE network to use for provisioning. Optional: Select the Associate Ephemeral External IP checkbox to assign a dynamic ephemeral IP address that Satellite uses to communicate with the host. This public IP address changes when you reboot the host. If you need a permanent IP address, reserve a static public IP address on Google GCE and attach it to the host. In the Size (GB) field, enter the size of the storage to create on the host. Click Submit to save the compute profile. CLI procedure Create a compute profile to use with the Google GCE compute resource: Add GCE details to the compute profile: 15.5. Creating Image-based Hosts on Google Compute Engine In Satellite, you can use Google Compute Engine provisioning to create hosts from an existing image. The new host entry triggers the Google Compute Engine server to create the instance using the pre-existing image as a basis for the new volume. To use the CLI instead of the Satellite web UI, see the CLI procedure . Procedure In the Satellite web UI, navigate to Hosts > Create Host . In the Name field, enter a name for the host. Click the Organization and Location tabs to ensure that the provisioning context is automatically set to the current context. From the Host Group list, select the host group that you want to use to populate the form. From the Deploy on list, select the Google Compute Engine connection. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings. From the Lifecycle Environment list, select the environment. Click the Interfaces tab and click Edit on the host's interface. Verify that the fields are automatically populated, particularly the following items: The Name from the Host tab becomes the DNS name . The MAC address field is blank. Google Compute Engine assigns a MAC address to the host during provisioning. Satellite Server automatically assigns an IP address for the new host. The Domain field is populated with the required domain. The Managed , Primary , and Provision options are automatically selected for the first interface on the host. If not, select them. Click the Operating System tab, and confirm that all fields automatically contain values. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use. Click the Virtual Machine tab and confirm that these settings are populated with details from the host group and compute profile. Modify these settings to suit your needs. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key. Click Submit to save the host entry. CLI procedure Create the host with the hammer host create command and include --provision-method image . Replace the values in the following example with the appropriate values for your environment. For more information about additional host creation parameters for this compute resource, enter the hammer host create --help command. 15.6. Deleting a VM on Google GCE You can delete VMs running on Google GCE on your Satellite Server. Procedure In the Satellite web UI, navigate to Infrastructure > Compute Resources . Select your Google GCE provider. On the Virtual Machines tab, click Delete from the Actions menu. This deletes the virtual machine from the Google GCE compute resource while retaining any associated hosts within Satellite. If you want to delete the orphaned host, navigate to Hosts > All Hosts and delete the host manually. 15.7. Uninstalling Google GCE Plugin If you have previously installed the Google GCE plugin but don't use it anymore to manage and deploy hosts to GCE, you can uninstall it from your Satellite Server. Procedure Uninstall the GCE compute resource provider from your Satellite Server: Optional: In the Satellite web UI, navigate to Administer > About and select the Available Providers tab to verify the removal of the Google GCE plugin.

Commands:
satellite-installer --enable-foreman-compute-gce
scp gce_key.json root@satellite.example.com:/usr/share/foreman/gce_key.json
chown foreman /usr/share/foreman/ gce_key .json
chmod 0600 /usr/share/foreman/ gce_key .json
restorecon -vv /usr/share/foreman/ gce_key .json
scp gce_key.json root@satellite.example.com:/usr/share/foreman/gce_key.json
chown foreman /usr/share/foreman/ gce_key .json
chmod 0600 /usr/share/foreman/ gce_key .json
restorecon -vv /usr/share/foreman/ gce_key .json
hammer compute-resource create --email " My_GCE_Email " --key-path " Path_To_My_GCE_Key.json " --name " My_GCE_Compute_Resource " --project " My_GCE_Project_ID " --provider "gce" --zone " My_Zone "
hammer compute-resource image create --name ' gce_image_name ' --compute-resource ' gce_cr ' --operatingsystem-id 1 --architecture-id 1 --uuid ' 3780108136525169178 ' --username ' admin '
hammer compute-profile create --name My_GCE_Compute_Profile
hammer compute-profile values create --compute-attributes "machine_type=f1-micro,associate_external_ip=true,network=default" --compute-profile " My_GCE_Compute_Profile " --compute-resource " My_GCE_Compute_Resource " --volume " size_gb=20 "
hammer host create --architecture x86_64 --compute-profile " gce_profile_name " --compute-resource " My_GCE_Compute_Resource " --image " My_GCE_Image " --interface "type=interface,domain_id=1,managed=true,primary=true,provision=true" --location " My_Location " --name " GCE_VM " --operatingsystem " My_Operating_System " --organization " My_Organization " --provision-method 'image' --puppet-ca-proxy-id 1 --puppet-environment-id 1 --puppet-proxy-id 1 --root-password " My_Root_Password "
yum remove -y foreman-gce satellite-installer --no-enable-foreman-compute-gce