Skip to content

Latest commit

 

History

History
64 lines (48 loc) · 2.35 KB

Deploying-Generic-Services-in-RHPDS.adoc

File metadata and controls

64 lines (48 loc) · 2.35 KB

Deploying Generic Services in RHPDS

  1. Check out the git repo at https://github.com/rut31337/order_svc

  2. Order your services using order_svc.sh

    1. Flag -c is the catalog in RHPDS

    2. Flag -i is the catalog item name from the above catalog

      Note
      Catalog and catalog item names should be in " if there are spaces in the name. You should specify the catalog and catalog item names exactly as they show up in the CloudForms GUI.
    3. Flag -u is your RHPDS generic login

      Important
      Do not use your personal RHPDS login for this purpose or the quota will stop you.
    4. Flag -w is the cloudforms URL (RHPDS in this example)

    5. Flag -t specifies the number of instances to deploy

    6. Flag -d allows you to set values that control the service deployment:

      1. Setting autostart=t will start the environments immediately upon creation and autostart=f will create environments but not start them (useful for staging a day ahead)

      2. Setting noemail=t is recommended as you do not want to send an email for every environment created (see obtaining GUIDs below)

./order_svc.sh -c "Workshops" -i "CloudForms 4.5 Workshop" \
 -u <generic_login> -w "https://rhpds.redhat.com" \
 -t 2 -d "autostart=t;noemail=t"
Note
More detailed documentation for order_svc and get_svcs is available in the above GIT repo.

Retrieving Lab GUIDs

  1. Obtain your GUIDs using this (flags are similar to order_svc, see above):

    ./get_svcs.sh -c "Workshops" -i "CloudForms 4.5 Workshop" \
     -u <generic_login> -w "https://rhpds.redhat.com" \
     -o services.txt
    cat services.txt |cut -f5 -d- > guids.txt

Working With Generic Environments

Once you have your GUIDs, you can share one GUID per student/group of students. The lab instructions should be generic where each VM in the lab has a hostname of something-$GUID.rhpds.opentlc.com. The student need only replace $GUID with their assigned GUID.

Retiring Generic Services in RHPDS

You have two options to retire services in RHPDS:

  • Allow them to self retire

    Note
    If you choose this option, at least power all the services down in Ravello to save money.

or

  • Use the standard service retirement in the RHPDS CloudForms interface.

    1. Services → My Services

    2. Select All

    3. Lifecycle → Retire

Important
Please do not delete the services in Ravello directly. You can power on and power off directly in Ravello if you want however.