Management – OSBC Instructor PODs Lab

For the instructors, there are now 4 users:
admin1 — Brad
admin2 — John
admin3 — Karim
admin4 — Marc

password: !onecloud123

from there you can log into a pair of systems, separate from the rest of the labs:

admin1: aio221 compute231
admin2: aio222 compute232
admin3: aio223 compute233
admin4: aio224 compute234

ssh in the admin user accout is set to log in as centos user to the aio and compute nodes, , and you already have a ssh key for all of the system (they were all deployed with the same cloud key)
but just in case: the user is centos, the password is centos
the image is a standard CentOS Cloud image (Centos 7.1)

As with the student environments, I recommend that at least the first ssh session (or with tunnel setup in putty, first putty session) be run as:

ssh -L 8080:10.1.64.221:80 -L 6080:10.1.64.221:6080 admin1@lab.onecloudinc.com

{clearly this is for user admin1 and user aio221}

this allows you to eventually point your browser to http://localhost:8080 on your local laptop, and get to horizon when taht’s set up.

Also if you run:

nova get-vnc-console vm-name novnc

You’ll get a URL of the form:

http://10.1.64.221:6080/…….

If you take that URL, and again, drop it into your local browser (but you’ll need to change 10.1.64.221 to localhost before hitting “enter”) you will eventually be able to access your deployed VMs via webVNC.

Now the trick to all of the above is that if you need to help a student fix an issue that they have with their VMs….

Well, instead of logging in to your AIO node (and instead of setting the pointers to about to 10.1.64.221):

ssh -L 8080:10.1.64.11:80 -L 6008:10..164.11:6080 admin1@lab.onecloudinc.com

ssh admin@centos-1
source ~/keystonerc_admin
nova get-vnc-console {trouble_VM_name} novnc

and as above, take the http URL, paste it into your _local_ browser, change the 10.1… address with localhost, and voi la, KVM access to the troubled VM.

Since these are centos machines, the user is centos, password is centos.

 

————————————————————————————————————————-

Added Details on Access to Student Systems

Clearly getting access to tenants VMs when they break something (perhaps network wise) is one of the tricks that needs to be dealt with.  I’ve created a script to help a bit on the jumpbox (66.220.11.249):

# vnc aio111
If you set up your tunnels as described in the Instructor lab docs, then you should just be able to copy/paste that into a browser and have access to the tenants vm.
In order to simply this process:
1) there are now nova and neutron command line tools on the jumpbox for talking to the “under cloud”
2) the root user (and the localadmin user) on the jumpbox have a keystonerc_admin file pointing to the jumpbox.
I  recommend that for putty users (how many of us are on windows in the instructor core?):  Create a profile with the 8080:centos-1:80 and 6080:centos-1:6080 Local redirects.
For Mac users copy and paste the following in a terminal:
cat >> ~/.ssh/config <<EOF
Host lab
  User localadmin
  LocalForward 8080 centos-1:80
  LocalForward 6080 centos-1:6080
#  IdentityFile ~/lab_localadmin.key
EOF
For Mac users, I also recommend editing your local hosts file:
sudo cat >> /etc/hosts <<EOF
66.220.11.249 lab
EOF
then you should be able to:
ssh lab
vnc aioXXX
copy paste, and you’re on the VM.
and for those that don’t have the localadmin password for the jumpbox, it’s !onecloud132