Chapter 16. Provisioning cloud instances on Google Compute Engine

Procedure

1. In GCE, generate a service account key in JSON format. For more information, see Create and manage service account keys in the GCE documentation.
2. In the Satellite web UI, navigate to Infrastructure > Compute Resources and click Create Compute Resource.
3. In the Name field, enter a name for the compute resource.
4. From the Provider list, select Google.
5. Optional: In the Description field, enter a description for the resource.
6. In the JSON key field, click Choose File and locate your service account key for upload from your local machine.
7. Click Load Zones to populate the list of zones from your GCE environment.
8. From the Zone list, select the GCE zone to use.
9. Click Submit.

Procedure

1. In GCE, generate a service account key in JSON format. For more information, see Create and manage service account keys in the GCE documentation.

2. Use the hammer compute-resource create command to add a GCE compute resource to Satellite:

   # hammer compute-resource create \
   --key-path "My_GCE_Key.json" \
   --name "My_GCE_Compute_Resource" \
   --provider "gce" \
   --zone "My_Zone"

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources.
2. Click the name of the Google Compute Engine connection.
3. Click Create Image.
4. In the Name field, enter a name for the image.
5. From the Operating System list, select the base operating system of the image.
6. From the Architecture list, select the operating system architecture.
7. 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.
8. From the Image list, select an image from the Google Compute Engine compute resource.
9. Optional: Select the User Data checkbox if the image supports user data input, such as cloud-init data.
10. Click Submit to save the image details.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles.
2. In the Compute Profiles window, click the name of an existing compute profile, or click Create Compute Profile, enter a Name, and click Submit.
3. Click the name of the GCE compute resource.
4. From the Machine Type list, select the machine type to use for provisioning.
5. From the Image list, select the image to use for provisioning.
6. From the Network list, select the GCE network to use for provisioning.
7. 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 GCE and attach it to the host.
8. In the Size (GB) field, enter the size of the storage to create on the host.
9. Click Submit to save the compute profile.

Procedure

1. Create a compute profile to use with the GCE compute resource:

   $ hammer compute-profile create --name My_GCE_Compute_Profile

2. Add GCE details to the 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"

Procedure

1. In the Satellite web UI, navigate to Hosts > Create Host.
2. In the Name field, enter a name for the host.
3. Optional: Click the Organization tab and change the organization context to match your requirement.
4. Optional: Click the Location tab and change the location context to match your requirement.
5. From the Host Group list, select a host group that you want to assign your host to. That host group will populate the form.
6. From the Deploy on list, select the Google Compute Engine connection.
7. From the Compute Profile list, select a profile to use to automatically populate virtual machine settings.
8. From the Lifecycle Environment list, select the environment.
9. Click the Interfaces tab, and on the interface of the host, click Edit.

10. Verify that the fields are populated with values. Note in particular:

    • Satellite automatically assigns an IP address for the new host.
    • Ensure that the MAC address field is blank. Google Compute Engine assigns a MAC address to the host during provisioning.
    • The Name from the Host tab becomes the DNS name.
    • The Domain field is populated with the required domain.
    • Ensure that Satellite automatically selects the Managed, Primary, and Provision options for the first interface on the host. If not, select them.

11. Click OK to save. To add another interface, click Add Interface. You can select only one interface for Provision and Primary.

    For more information about network interfaces, see Configuring network interfaces in Managing hosts.

12. Click the Operating System tab, and confirm that all fields automatically contain values.
13. Click Resolve in Provisioning templates to check the new host can identify the right provisioning templates to use.
14. 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.
15. On the Parameters tab, click Add parameter. Add a parameter named kt_activation_keys, select the string type, and enter the name of the activation key as the value. The activation key has to belong to the same organization as your host. You can also enter a comma-separated list of multiple activation keys.
16. Click Submit to save the host entry.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources.
2. Select your Google Compute Engine provider.
3. On the Virtual Machines tab, click Delete from the Actions menu. This deletes the virtual machine from the Google Compute Engine 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.