Chapter 14. Provisioning cloud instances in Amazon EC2

Procedure

1. Install the EC2 compute resource provider on your Satellite Server:

   # satellite-installer --enable-foreman-compute-ec2

2. Optional: In the Satellite web UI, navigate to Administer > About and select the compute resources tab to verify the installation of the Amazon EC2 plugin.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and in the Compute Resources window, click Create Compute Resource.
2. In the Name field, enter a name to identify the Amazon EC2 compute resource.
3. From the Provider list, select EC2.
4. In the Description field, enter information that helps distinguish the resource for future use.
5. Optional: From the HTTP proxy list, select an HTTP proxy to connect to external API services. You must add HTTP proxies to Satellite before you can select a proxy from this list. For more information, see Section 14.4, “Using an HTTP proxy with compute resources”.
6. In the Access Key and Secret Key fields, enter the access keys for your Amazon EC2 account. For more information, see Managing Access Keys for your AWS Account on the Amazon documentation website.
7. Optional: Click Load Regions to populate the Regions list.
8. From the Region list, select the Amazon EC2 region or data center to use.
9. Click the Locations tab and ensure that the location you want to use is selected, or add a different location.
10. Click the Organizations tab and ensure that the organization you want to use is selected, or add a different organization.
11. Click Submit to save the Amazon EC2 connection.
12. Select the new compute resource and then click the SSH keys tab, and click Download to save a copy of the SSH keys to use for SSH authentication. Until BZ1793138 is resolved, you can download a copy of the SSH keys only immediately after creating the Amazon EC2 compute resource. If you require SSH keys at a later stage, follow the procedure in Section 14.9, “Connecting to an Amazon EC2 instance using SSH”.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > HTTP Proxies, and select New HTTP Proxy.
2. In the Name field, enter a name for the HTTP proxy.
3. In the URL field, enter the URL for the HTTP proxy, including the port number.
4. Optional: Enter a username and password to authenticate to the HTTP proxy, if your HTTP proxy requires authentication.
5. Click Test Connection to ensure that you can connect to the HTTP proxy from Satellite.
6. Click the Locations tab and add a location.
7. Click the Organization tab and add an organization.
8. Click Submit.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources.
2. Select your Amazon EC2 provider.

3. Click Create Image.

   • In the Name field, enter a meaningful and unique name for your EC2 image.
   • From the Operating System list, select an operating system to associate with the image.
   • From the Architecture list, select an architecture to associate with the image.
   • In the Username field, enter the username needed to SSH into the machine.
   • In the Image ID field, enter the image ID provided by Amazon or an operating system vendor.
   • Optional: Select the User Data check box to enable support for user data input.
   • Optional: Set an Iam Role for Fog to use when creating this image.
   • Click Submit to save your changes to Satellite.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources and select an Amazon EC2 connection.
2. Click the Images tab, and then click Create Image.
3. In the Name field, enter a name to identify the image for future use.
4. From the Operating System list, select the operating system that corresponds with the image you want to add.
5. From the Architecture list, select the operating system’s architecture.
6. In the Username field, enter the SSH user name for image access. This is normally the root user.
7. In the Password field, enter the SSH password for image access.
8. In the Image ID field, enter the Amazon Machine Image (AMI) ID for the image. This is usually in the following format: ami-xxxxxxxx.
9. Optional: Select the User Data checkbox if the images support user data input, such as cloud-init data. If you enable user data, the Finish scripts are automatically disabled. This also applies in reverse: if you enable the Finish scripts, this disables user data.
10. Optional: In the IAM role field, enter the Amazon security role used for creating the image.
11. Click Submit to save the image details.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Profiles and click the name of your profile, then click an EC2 connection.
2. From the Flavor list, select the hardware profile on EC2 to use for the host.
3. From the Image list, select the image to use for image-based provisioning.
4. From the Availability zone list, select the target cluster to use within the chosen EC2 region.
5. From the Subnet list, add the subnet for the EC2 instance. If you have a VPC for provisioning new hosts, use its subnet.
6. From the Security Groups list, select the cloud-based access rules for ports and IP addresses to apply to the host.
7. From the Managed IP list, select either a Public IP or a Private IP.
8. Click Submit to save the compute profile.

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 EC2 connection.
7. From the Compute Profile list, select a profile to use to automatically populate virtual machine-based settings.
8. Click the Interfaces tab, and on the interface of the host, click Edit.

9. 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. EC2 assigns a MAC address to the host during provisioning.
   • The Name from the Host tab becomes the DNS name.
   • Ensure that Satellite automatically selects the Managed, Primary, and Provision options for the first interface on the host. If not, select them.
10. Click OK to save. To add another interface, click Add Interface. You can select only one interface for Provision and Primary.
11. Click the Operating System tab and confirm that all fields are populated with values.
12. Click the Virtual Machine tab and confirm that all fields are populated with values.
13. Click the Parameters tab, and ensure that a parameter exists that provides an activation key. If not, add an activation key.
14. Click Submit to save your changes.

Procedure

1. To locate the compute resource list, on your Satellite Server base system, enter the following command, and note the ID of the compute resource that you want to use:

   # hammer compute-resource list

2. Switch user to the postgres user:

   # su - postgres

3. Initiate the postgres shell:

   $ psql

4. Connect to the Foreman database as the user postgres:

   # postgres=# \c foreman

5. Select the secret from key_pairs where compute_resource_id = 3:

   # select secret from key_pairs where compute_resource_id = 3; secret

6. Copy the key from after -----BEGIN RSA PRIVATE KEY----- until -----END RSA PRIVATE KEY-----.

7. Create a .pem file and paste your key into the file:

   # vim Keyname.pem

8. Ensure that you restrict access to the .pem file:

   # chmod 600 Keyname.pem

9. To connect to the Amazon EC2 instance, enter the following command:

   ssh -i Keyname.pem   ec2-user@example.aws.com

Procedure

1. In the Satellite web UI, navigate to Hosts > Templates > Provisioning Templates.
2. In the Provisioning Templates page, enter Kickstart default finish into the search field and click Search.
3. On the Kickstart default finish template, select Clone.
4. In the Name field, enter a unique name for the template.

5. In the template, prefix each command that requires root privileges with sudo, except for subscription-manager register and yum commands, or add the following line to run the entire template as the sudo user:

   sudo -s << EOS
   _Template_ _Body_
   EOS

6. Click the Association tab, and associate the template with a Red Hat Enterprise Linux operating system that you want to use.
7. Click the Locations tab, and add the the location where the host resides.
8. Click the Organizations tab, and add the organization that the host belongs to.
9. Make any additional customizations or changes that you require, then click Submit to save your template.
10. In the Satellite web UI, navigate to Hosts > Operating systems and select the operating system that you want for your host.
11. Click the Templates tab, and from the Finish Template list, select your finish template.
12. In the Satellite web UI, navigate to Hosts > Create Host.
13. In the Name field, enter a name for the host.
14. Optional: Click the Organization tab and change the organization context to match your requirement.
15. Optional: Click the Location tab and change the location context to match your requirement.
16. From the Host Group list, select a host group that you want to assign your host to. That host group will populate the form.
17. Click the Parameters tab and navigate to Host parameters.

18. In Host parameters, click Add Parameter two times to add two new parameter fields. Add the following parameters:

    1. In the Name field, enter activation_keys. In the corresponding Value field, enter your activation key.
    2. In the Name field, enter remote_execution_ssh_user. In the corresponding Value field, enter ec2-user.
19. Click Submit to save the changes.

Procedure

1. In the Satellite web UI, navigate to Infrastructure > Compute Resources.
2. Select your Amazon EC2 provider.
3. On the Virtual Machines tab, click Delete from the Actions menu. This deletes the virtual machine from the Amazon EC2 compute resource while retaining any associated hosts within Satellite. If you want to delete an orphaned host, navigate to Hosts > All Hosts and delete the host manually.

Procedure

1. Uninstall the EC2 compute resource provider from your Satellite Server:

   # satellite-maintain packages remove foreman-ec2
   # satellite-installer --no-enable-foreman-compute-ec2

2. Optional: In the Satellite web UI, navigate to Administer > About and select the Available Providers tab to verify the removal of the Amazon EC2 plugin.