drpfeature-test-drpe-ansible-blender

Intent
Add blender render node via ansible-playbook.
Success
RackN-Portal setup that uses inventory.py to run ansible all -i inventory.py -m ping

Manual Steps

  1. Assuming a drpfeature-test-network with drpfeature-test-vbox running the drpfeature-test-drpe setup.

  2. Assuming the drp3-Clone-post4machineHPEpxeboot vm configuration.

  3. Assuming drpfeature-test-drpe-ansible setup

  4. Start drpe vm ( see drpfeature-test-drpe )

  5. ssh drpops@192.168.88.3 ( good4installs# )

    1. Start drp-provision on drpe:

      [drpops@drpe ~]$ cd drpisolated/
[drpops@drpe drpisolated]$ sudo ./dr-provision --static-ip=192.168.88.3 --base-root=/home/drpops/drpisolated/drp-data --local-content="" --default-content=""
  6. Open RackN-Portal Content Packages We need to load something ansible to test
    1. Click “Browse For More Content”
    2. Find kubespray and click the + icon to add this content to endpoint
    3. View your drpfeature-test-drpe Endpoint (hamburger -> Endpoint..)
    4. Click Content Packages again you should see kubespray
    5. Verify kubespray is in your endpoint, if not “Transfer” it so that it displays in the Endpoint Content column
  7. Navigate to Profiles
    1. The following locked Profiles should have been added
      1. etcd
      2. k8s-cluster
      3. k8s-deploy
      4. kube-master
      5. kube-node
    2. Clone the k8s-deploy Profile in Profiles
    3. Rename and Edit the Profile for mycluster
    4. Save (Click Add button) and Verify Profile mycluster in Profiles
    5. In Profiles click Ansible button (on top)
    6. Select the mycluster Profile for Ansible Inventory Grid
      1. Select the server nodes you want in mycluster
      2. add etcd and kube master to a machine
      3. add kube node to others
  8. Fire up four bare metal machines on drpfeature-test-hpeC7000
    1. Browse to drpfeature-test-hpeC7000
    2. Login with drpops ( good4installs# )
    3. Should see 4 blades (or how ever many are in at the time)
    4. Click the blade image and it takes you to the blade View
    5. Click Boot Options (confirm it is booting from local disk)
    6. Click Virtual Devices (to control power / boot)
  9. Reference the drp-kubespray-document and follow the commands step 24.1.4
    1. ssh drpops@192.168.88.3 ( good4installs# )
    2. SKIP THIS - Git Clone kubespray-github (SKIP… we are just testing the inventory.py file)
    3. Create directory mkdir testansible and cd testansible
    4. Pull in inventory.py from drp-inventory.py-source-file (rob shows link)
    5. Make executable chmod +x inventory.py
    6. Verify local environment endpoint is set.
    7. Look at what endpoint we are pointed to ./drpcli info get
    8. Set endpoint export RS_ENDPOINT=https://192.168.88.3:8092
    9. Set profile export RS_PROFILE=mycluster
    10. Test ./inventory.py | jq command
    11. Test Ansible via ping ansible all -i inventory.py -m ping

Video Track

  1. tc Make Video and Show stuff at some point

Video

No Video Yet

Setup for testing drp endpoint

drpfeature-test setup uses the drpfeature-test-network and drpfeature-test-vbox running on a drpfeature-test-macosx with drp-provision running on the drpfeature-test-drpe endpoint for pxe boot of Proliant Blade servers in drpfeature-test-hpeC7000 configuration which then are assessable via drpfeature-test-drpe-ansible and can use drpfeature-test-drpe-ansible-blender to install a blender render grid worker node.