About CloudForms Lab

About CloudForms Lab

1. Set Up Lab Environment

1.1. Provision Lab Environment

 Use FireFox when running these labs. All other browsers, including Chrome, may have compatibility issues.

Before you can run these labs, you need to provision the lab environment with CloudForms and Red Hat Virtualization.

1. Access the OPENTLC lab provisioning system, which is built on top of CloudForms, athttps://labs.opentlc.com.

2. Use your credentials to log in.

    If you do not remember your username or password, go to https://www.opentlc.com/account to reset your password or obtain a username reminder.

3. After you log in, navigate to Services → Catalogs → All Services → OPENTLC Cloud Infrastructure Labs.

4. On the left side of the screen, locate CloudForms 4.1 Implementation Lab and clickOrder, which appears on the right.

5. On the next screen, on the lower right side, click Submit to order your CloudForms environment.

6. Check your email for a message from Red Hat describing how to connect to the environment.

1.2. Review Lab Environment

1. Wait about 20 minutes to allow the environment to build.

2. Verify that your environment includes the following entities:

   • Student Workstation

   • CloudForms Management Engine

   • Red Hat Virtualization Manager

   • Red Hat Enterprise Linux + KVM-Host

   • VMware vSphere + 2 ESXi hosts

   • IdM/IPA Identity Management host

   • Red Hat OpenStack Platform (all-in-one installation)

   • Red Hat Satellite

   • Red Hat OpenShift

   • Ansible Tower

 The lab environment is cloud-based, so you can access it over the WAN from anywhere. However, do not expect its performance to match a bare-metal environment.

2. Access Lab Environment

2.1. Set Up SSH

To access your workstation system via SSH, use your personal OPENTLC SSO username and public SSH key.

 Unless otherwise noted, you cannot use SSH to connect directly asroot.

If you have not already done so, you must provide a public SSH key.

1. Go to https://www.opentlc.com/update and log in.

2. Paste your public key in the appropriate field.

 For more information on generating an SSH key, see: https://www.opentlc.com/ssh.html.

2.2. Access Environment With SSH

1. Use SSH to remotely connect to the lab workstation. Use your private SSH key and your OPENTLC SSO login:

   $ ssh -i path-to-your-ssh-key [e-mail]

    When entering commands, replace GUID with your personal GUID, which is provided at the top of the lab provisioning email you received from Red Hat.
    To avoid problems, always use the FQDN hostname andnot the IP or Ravello DNS entry when using SSH to connect to your OPENTLC lab hosts.

2. Become root on the lab workstation:

   $ sudo -i#

2.3. Using Kerberos Authentication Instead of SSH Keys (Advanced)

If you have problems using SSH keys, use Kerberos authentication instead. To do this you must be running on a UNIX/Linux or Mac OS X host.

 Windows hosts can support Kerberos, but it is beyond the scope of this class to provide instructions for implementing it.

1. Make sure you have the following settings in /etc/krb5.conf on your host (not in the lab environment):

   dns_lookup_realm = truedns_lookup_kdc = true

2. Use the following command to obtain a Kerberos ticket:

   $ kinit [e-mail]<enter your OPENTLC SSO password>

    Capitalize all letters of OPENTLC.COM, as shown.

3. Use SSH to remotely connect to your host without specifying the -i flag:

   $ ssh [e-mail]

3. Troubleshoot Lab Environment

3.1. Unable to Access a Server

1. Go to https://labs.opentlc.com.

2. In Services → My Services → All Services, select your lab environment (OTLC-RH-<login>-redhat.com-CFI_v4.1_Implementation-GUID).

3. At the top of the screen, select App Control → Stop, wait for the environment to stop, then selectApp Control → Start.

4. If you configured cloud and infrastructure providers, you need to make CloudForms check its authentication statuses again:

   1. Go to Compute → Infrastructure/Couds → Providers.

   2. Select the provider that has an erratic status:

   3. Select Authentication → Re-Check Authentication Status: