Options
Red Hat EX280 OpenShift Enterprise Exam Resources
darkerosxx
Banned Posts: 1,343
I studied for this exam for a few weeks, using a trial version of the software only to find out the actual exam is 2 major versions behind what's linked to on the exam page. The exam is currently on version 1.2, while their pages link to a trial for version 2.1. Their training team reimbursed my exam voucher and said their updated exam on version 2.1 should be out soon, at the latest they're hoping for Q1 2015. So, having said all of that... here are my notes using the CURRENT exam objectives on version 2.1 of OpenShift Enterprise
My notes on EX280 Openshift exam, following listed objectives
_________________________
*** - Install and configure Red Hat OpenShift Enterprise broker hosts, Install and configure Red Hat OpenShift Enterprise node hosts, Install and configure the Red Hat OpenShift web console
-Ensure broker and node attached to yum repo for generic RHEL6 server (NOT OPENSHIFT REPO), then run yum update -y, reboot
-Generate an ssh key
--ssh-keygen -t rsa -b 2048
--use defaults, no password
-Copy the ssh key to broker and nodes, then test it works without password
--ssh-copy-id $hostname
--ssh $hostname
-run the oo-install-ose script, which asks you for the following information:
--Broker hostname FQDN/IP
--Node hostname FQDN/IP
--username to SSH to broker/node (it will test if can ssh without password)
--it will log in to each broker/node, get the IP on it, and ask if that's what you want to use for inter-broker/node communication
--domain name for apps
--domain name for OpenShift hosts (if different)
--available gear sizes system-wide (default small, can be multiple)
--user default gear sizes (can be multiple)
--app default gear size
--default node district name
-then it asks you to confirm above info
-then it asks you to tell it how to get packages
--package repository options are "none" if you manually set up yum repos, yum will ask for repo info, rhsm for RED HAT SUBSCRIPTION MANAGER
-confirm that info, add any one-time install options if you have any
-want to use specific usernames/passwords? if not, will spit out users and passwords it created
-should start install at that point, run a tail -f /tmp/openshift-deploy.log to follow install on both broker and node
-my installs ALWAYS end with it restarting services on both the broker and the node, but after restarting the node services, the install script stalls. If you ctl-c the script, it says it finished the install and I've found the install does work, but the district isn't installed, so I install a district manually, covered in later steps
____________________________
*** - Configure Red Hat OpenShift Enterprise broker hosts to use basic authentication
-by default, uses htpasswd authentication for Apache
--htpasswd file is /etc/openshift/htpasswd
-to add a user, generate a username:hashed password combo to put in the file
--run htpasswd -nb $username $password, copy/paste output and place as new line in htpasswd file
-log in as user to console at http://$hostname/console and it will create user in openshift with default settings
____________________________
*** - Limit gear resources
-edit gear resources on node
--vi /etc/openshift/resource_limits.conf
--/etc/init.d/ruby192-mcollective restart
-add new gear sizes to nodes
--define new gear profile on node
---vi /etc/openshift/resource_limits.conf
---modify the node_profile parameter to set new name for gear profile
---/etc/init.d/ruby192-mcollective restart
--update list of gear sizes on broker
---vi /etc/openshift/broker.conf
---modify valid_gear_sizes to include the new profile, comma-separated
---if new default size for users, edit default_gear_capabilities
---/etc/init.d/openshift-broker restart
--create a district so users can use the new gear size
---oo-admin-ctl-district -c create -n newdistrict -p large
--add the node to that district (remove the node from the old district if necessary)
---oo-admin-ctl-district -c add-node --name newdistrict -i nodename
--grant users access to new gear sizes
---oo-admin-ctl-user -l username --addgearsize large
-edit gear resources on broker
--vi /etc/openshift/broker.conf
---valid_gear_sizes
---default_max_gears
---default_gear_size
---default_gear_capabilities
-edit user settings for gears
--oo-admin-ctl-user -l user --option like setmaxgears
____________________________
*** - Configure districts
-create a district
--oo-admin-ctl-district -c create -n district_medium -p medium
-add a node to the district
--oo-admin-ctl-district -c add-node -n district_medium -i node.example.com
-remove node from district
--oo-admin-ctl-district -c deactivate-node -n small_district -i node2.example.com
--oo-admin-ctl-district -c remove-node -n small_district -i node2.example.com
-delete the district
--oo-admin-ctl-district -c destroy -n district_name
-list of nodes
--oo-admin-ctl-district
____________________________
*** - Manage Red Hat OpenShift Enterprise applications from the command line
-find what applications a user is using
--oo-ctl-admin-domain -l user
-app mgmt from user
--login to user cli
---su -u user
---rhc setup
-create an app under a user
--rhc app create appname cartridgename
-stop and destroy an app under a user
--oo-admin-ctl-app -l username -a appname -c stop (or force-stop)
--oo-admin-ctl-app -l username -a appname -c destroy (or force-destroy)
____________________________
*** - Deploy cartridges
ON BROKER:
-list cartridges
--oo-admin-ctl-cartridge -c list
-deactivate cartridge
--oo-admin-ctl-cartridge -c deactivate -n name
-clean out deactivated cartridges
--oo-admin-ctl-cartridge -c clean
-import cartridges from node
--oo-admin-ctl-cartridge -c import-node --activate --obsolete -i node.example.com
-add cartridges from url
--oo-admin-ctl-cartridge -c import --url URL_to_Cartridge_Manifest --activate
ON NODE:
-add cartridges from yum on node
--yum search cartridge
--yum install $package
-add cartridge from file on node
--oo-admin-cartridge --action install --source /path/to/cartridge/
-remove cartridge from node
--oo-admin-cartridge --action erase --name Cart_Name
____________________________
OTHER NOTES
-when having issues with anything, try running diagnostics first to see if it can find the issue
-it will usually tell you how to fix a problem
--oo-diagnostics
-remove a user
--oo-admin-ctl-domain -l username -c delete
My notes on EX280 Openshift exam, following listed objectives
_________________________
*** - Install and configure Red Hat OpenShift Enterprise broker hosts, Install and configure Red Hat OpenShift Enterprise node hosts, Install and configure the Red Hat OpenShift web console
-Ensure broker and node attached to yum repo for generic RHEL6 server (NOT OPENSHIFT REPO), then run yum update -y, reboot
-Generate an ssh key
--ssh-keygen -t rsa -b 2048
--use defaults, no password
-Copy the ssh key to broker and nodes, then test it works without password
--ssh-copy-id $hostname
--ssh $hostname
-run the oo-install-ose script, which asks you for the following information:
--Broker hostname FQDN/IP
--Node hostname FQDN/IP
--username to SSH to broker/node (it will test if can ssh without password)
--it will log in to each broker/node, get the IP on it, and ask if that's what you want to use for inter-broker/node communication
--domain name for apps
--domain name for OpenShift hosts (if different)
--available gear sizes system-wide (default small, can be multiple)
--user default gear sizes (can be multiple)
--app default gear size
--default node district name
-then it asks you to confirm above info
-then it asks you to tell it how to get packages
--package repository options are "none" if you manually set up yum repos, yum will ask for repo info, rhsm for RED HAT SUBSCRIPTION MANAGER
-confirm that info, add any one-time install options if you have any
-want to use specific usernames/passwords? if not, will spit out users and passwords it created
-should start install at that point, run a tail -f /tmp/openshift-deploy.log to follow install on both broker and node
-my installs ALWAYS end with it restarting services on both the broker and the node, but after restarting the node services, the install script stalls. If you ctl-c the script, it says it finished the install and I've found the install does work, but the district isn't installed, so I install a district manually, covered in later steps
____________________________
*** - Configure Red Hat OpenShift Enterprise broker hosts to use basic authentication
-by default, uses htpasswd authentication for Apache
--htpasswd file is /etc/openshift/htpasswd
-to add a user, generate a username:hashed password combo to put in the file
--run htpasswd -nb $username $password, copy/paste output and place as new line in htpasswd file
-log in as user to console at http://$hostname/console and it will create user in openshift with default settings
____________________________
*** - Limit gear resources
-edit gear resources on node
--vi /etc/openshift/resource_limits.conf
--/etc/init.d/ruby192-mcollective restart
-add new gear sizes to nodes
--define new gear profile on node
---vi /etc/openshift/resource_limits.conf
---modify the node_profile parameter to set new name for gear profile
---/etc/init.d/ruby192-mcollective restart
--update list of gear sizes on broker
---vi /etc/openshift/broker.conf
---modify valid_gear_sizes to include the new profile, comma-separated
---if new default size for users, edit default_gear_capabilities
---/etc/init.d/openshift-broker restart
--create a district so users can use the new gear size
---oo-admin-ctl-district -c create -n newdistrict -p large
--add the node to that district (remove the node from the old district if necessary)
---oo-admin-ctl-district -c add-node --name newdistrict -i nodename
--grant users access to new gear sizes
---oo-admin-ctl-user -l username --addgearsize large
-edit gear resources on broker
--vi /etc/openshift/broker.conf
---valid_gear_sizes
---default_max_gears
---default_gear_size
---default_gear_capabilities
-edit user settings for gears
--oo-admin-ctl-user -l user --option like setmaxgears
____________________________
*** - Configure districts
-create a district
--oo-admin-ctl-district -c create -n district_medium -p medium
-add a node to the district
--oo-admin-ctl-district -c add-node -n district_medium -i node.example.com
-remove node from district
--oo-admin-ctl-district -c deactivate-node -n small_district -i node2.example.com
--oo-admin-ctl-district -c remove-node -n small_district -i node2.example.com
-delete the district
--oo-admin-ctl-district -c destroy -n district_name
-list of nodes
--oo-admin-ctl-district
____________________________
*** - Manage Red Hat OpenShift Enterprise applications from the command line
-find what applications a user is using
--oo-ctl-admin-domain -l user
-app mgmt from user
--login to user cli
---su -u user
---rhc setup
-create an app under a user
--rhc app create appname cartridgename
-stop and destroy an app under a user
--oo-admin-ctl-app -l username -a appname -c stop (or force-stop)
--oo-admin-ctl-app -l username -a appname -c destroy (or force-destroy)
____________________________
*** - Deploy cartridges
ON BROKER:
-list cartridges
--oo-admin-ctl-cartridge -c list
-deactivate cartridge
--oo-admin-ctl-cartridge -c deactivate -n name
-clean out deactivated cartridges
--oo-admin-ctl-cartridge -c clean
-import cartridges from node
--oo-admin-ctl-cartridge -c import-node --activate --obsolete -i node.example.com
-add cartridges from url
--oo-admin-ctl-cartridge -c import --url URL_to_Cartridge_Manifest --activate
ON NODE:
-add cartridges from yum on node
--yum search cartridge
--yum install $package
-add cartridge from file on node
--oo-admin-cartridge --action install --source /path/to/cartridge/
-remove cartridge from node
--oo-admin-cartridge --action erase --name Cart_Name
____________________________
OTHER NOTES
-when having issues with anything, try running diagnostics first to see if it can find the issue
-it will usually tell you how to fix a problem
--oo-diagnostics
-remove a user
--oo-admin-ctl-domain -l username -c delete
Comments
-
Options
asummers
Member Posts: 157
Hello - did you ever get round to doing this exam? I am in two minds about Openshift -
Options
vampug
Member Posts: 11 ■□□□□□□□□□
I got some free ROL training due to a snafu with one of my other exams and chose the CL280.
I had the same problem with the installation not completing and logged a call with RH, however, with it being a weekend sI finally figured out what the problem was (DFU issue on my part).
Every time I did the install I would open a terminal session within the GUI and do the install (I ended up with an installtion that did not complete - cartridges not being added etc), however the course notes said (not so clearly I might add), do CTRL ALT F2 (new console - ie not running console within GUI).
The installation works perfectly if you run it from a non GUI TTY.
Thanks for the notes and info that you have prepared.
Hope this helps and good luck, I have my exam in a couple of weeks - fingers crossed (3 down, 2 to go)