OpenNebula4 Quick User Guide¶
- Table of contents
- OpenNebula4 Quick User Guide
- Quick User Guide
Quick User Guide¶
- If you did not yet, please take a look at the OpenNebula4 New User Quick Start Tutorial first.
- In order to use FermiCloud you need to go to http://fermicloud.fnal.gov or ssh $USER@fcluigpvm01.fnal.gov (as your own user)*
- fermicloud.fnal.gov is an alias pointing to fclheadgpvm01.fnal.gov. Users cannot log into this machine
- fermicloudui.fnal.gov is an RRDNS pair that points to fcluigpvm01.fnal.gov and fcluigpvm02.fnal.gov both of which users can log into individually.
- Do not source the user.sh script, it is already sourced for you.
- You can see your running VMs by running one_check-pingVMs.sh. This command will ping all your VMs and list them, just like onevm list but also attaching it's actual hostname.
- In order to start a VM you can use the the onetemplate instantiate "$VirtualMachineInstanceType" command. See more details on the Virtual Machine Instance Type list below.
- Please customize the name of your VMs with the --name 'My vm name'flag, see 'onetemplate help' output for more information.
FermiCloud Standard Virtual Machine Instance Types¶
All standard FermiCloud VMs have the following Hardware properties:
- 2GB of RAM
- 1 CPU (Intel E5640 or newer) - not dedicated
- 16GB / partition (in a +200GB disk) - not dedicated
If you need something different than the default templates offer, please contact FermiCloud through http://fermi.service-now.com/. If you don't find anything that fit your needs under 'Scientific Computing' just submit a 'General Request'.
These are the standard Non-persistent VM Templates that FermiCloud offers on the OpenNebula4 server:
- CLI_DynamicIP_SLF6Vanilla - Scientific Linux Fermi 6.
- CLI_DynamicIP_SLF6_HOME - Scientific Linux Fermi 6 with NIS and automount enabled (NFS shared home area), SSH login enabled from any network.
- CLI_POOL_IPV6_SLF6Vanilla - Scientific Linux Fermi 6 with IPV6 support
- CLI_POOL_IPV6_SLF6_HOME - Scientific Linux Fermi 6 with IPV6 support and NIS and automount enabled (NFS shared home area), SSH login enabled from any network.
- CLI_DynamicIP_SLF6_32bit - Scientific Linux Fermi 6 32-bit
- SLF7Vanilla_Dynamic_IP - Scientific Linux 7.2 64-bit
- SLF7V_DynIP_Home - Scientific Linux 7.2 64-bit with home directories and NIS.
You can always list them from fermicloudui.fnal.gov:
-bash-4.1$ onetemplate list | grep -v timm | grep -v dwd | grep -v EC2 ID USER GROUP NAME REGTIME 2 oneadmin oneadmin CLI_PRIV_SLF6_PRVM_GWMS 12/31 09:05:10 4 oneadmin oneadmin CLI_PRIV_SLF6Vanilla 01/02 12:10:55 5 oneadmin oneadmin CLI_DynamicIP_SLF6Vanilla 02/13 11:27:05 7 oneadmin oneadmin CLI_POOL_IPV6_SLF6Vanilla 02/20 10:53:18 73 oneadmin oneadmin CLI_POOL_IPV6_SLF6_HOME 03/17 20:36:49 75 oneadmin oneadmin CLI_DynamicIP_SLF6_HOME 03/22 21:46:50 199 oneadmin oneadmin SLF7Vanilla_DynamicIP 02/09 10:16:17 202 oneadmin oneadmin SLF7V_DynIP_Home 02/16 15:07:23
Note that all template's minor version may be updated without prior notice (ie: today your now VM can be SLF6.4 and tomorrow SLF6.5).
You can refer to template by the number rather than the name but the number is subject to change without notice.
Adding new users to my VM k5login persistently¶
By default all FermiCloud VMs regenerate /root/.k5login file throught the 'contextualization scripts' on each boot.
In order to get an entry in root's .k5login persistently you have to add the new lines you want in the /root/k5login_local file. Any user added in this files will be granted root in the VM, the format of k5login files is (note uppercase FNAL.GOV), for instance if I want to add 'gerard1' user as root in a fermicloud VM I will run the following in the VM (as root):
user=gerard1 echo "$user@FNAL.GOV" >> /root/.k5login echo "$user@FNAL.GOV" >> /root/k5login_local
If you are running a NIS enabled VM, any user with access in FermiCloud can access, as a user, to the VM. To know if NIS is enabled in your VM you can run 'ypwhich':
# ypwhich fermicloudnis2.fnal.gov # echo $? 0
# ypwhich ypwhich: Can't communicate with ypbind #
How to create N VMs just like the one you like (save and relaunch a VM)¶
It is possible to save the status of a non-persistent VM so that many copies of that VM can be launched thereafter.
In OpenNebula 4 this does not take admin privileges anymore.
To save a copy of your VM as a snapshot
onevm disk-snapshot <vmid> 0 <snapshotname> onevm shutdown <vmid> onetemplate clone 5 my_new_template
where 5 is tne number of the standard template that people normally use.
The onetemplate clone command will return a template number when it is executed.
export EDITOR=/usr/bin/vim onetemplate update <templateid>
The DISK section of the template looks like this
DISK=[ CACHE="default", IMAGE="SLF6Vanilla", IMAGE_UNAME="oneadmin", TARGET="vda"
Modify it so that IMAGE has the value of the new image name you picked <snapshotname> and
IMAGE_UNAME is your user name rather than oneadmin.
Once this change is made you can instantiate the new template
onetemplate instantiate <templateid> --name=<your_name_here>
For assistance you can contact FermiCloud support via the Service Desk http://servicedesk.fnal.gov/.