Manuel J. Parra Royón (manuelparra@decsai.ugr.es) & José. M. Benítez Sánchez (j.m.benitez@decsai.ugr.es)
- Starting with OpenNebula
OpenNebula enable two ways of interaction:
- Command line applications
- Web Application
Firstly try to access to the docker ugr server:
ssh manuparra@docker....
Change manuparra with your user login:
ssh mccXXXXXXX@docker....
Use your previously changed password, when asked.
The first action when login is the next:
oneuser login mccXXXXXXX —-ssh —-force
This command is very important, due to, it creates the session with OpenNebula and it allows to use all commands on OpenNebula.
OpenNebula commands:
onemarket onevm oneacct onedatastore
onegroup onetemplate onevnet oneacl
onedb onehost oneuser onezone
onecluster oneimage onevcenter ...
It allows to list the images of Operating systems, data, etc. that we can import to add to our cloud available from a MarketPlace
List of OSs available to run:
onemarket list
It allows to list the images that are in the system ready to be used for a display of virtual machines
List of imported images available to work:
oneimage list
Allows you to manage the virtual networks that have been created.
List of virtual networks created:
onevnet show <ID>
It allows to manage templates of generation of virtual machines, so that we can create templates that have certain attributes of memory, capacity, etc. etc.
List of available templates
onetemplate list
onetemplate show <ID>
It is normal to appear empty since we have not yet made any template. We will create it later.
It allows to manage the virtual machines launched, to know the state, to modify the state, to know the IP / Network, resources, etc., etc.
List of virtual machines available:
onevm list
It is normal to appear empty since we have not yet launched any virtual machine. We will create it later.
Allows you to manage the hosts and resources of the cloud created with OpenNebula
List of hosts of the system and its state:
onehost list
It appears empty since HOSTS are managed from a privileged user profile.
Access to the docker ugr server:
ssh manuparra@docker....
This is the first step before working with OpenNebula:
oneuser login <youruserlogin> --ssh --force
for example:
oneuser login manuparra --ssh --force
or in your case:
oneuser login mccXXXXXX --ssh --force
If this command works fine, you are allow to use and connect with OpenNebula.
oneimage list
It will show:
ID USER GROUP NAME DATASTORE SIZE TYPE PER STAT RVMS
8 oneadmin users CentOS-6.5-one- default 10G OS No used 1
9 oneadmin users CentOS-7 default 10G OS No rdy 0
10 oneadmin users Ubuntu-14.04 default 10G OS No rdy 0
11 oneadmin users Hadoop 1.2 Mast default 1.3G OS No rdy 0
12 oneadmin users Hadoop 1.2 Slav default 1.3G OS No rdy 0
...
Images are referenced by "ID" or "NAME". You can use those IDENTIFIERS to reference list elements.
If we want to use CENTOS7, we need the ID => 9 o NAME => "CentOS-7".
Now we have to verify that we have created our Virtual Network to be able to launch the machines within a correct IP address space:
onevnet list
and look forward for your Virtual Network
ID USER GROUP NAME CLUSTER BRIDGE LEASES
0 oneadmin oneadmin private_vnet - br0 0
1 usertest users private1_vnet - br0 0
2 openstack users openstack_vnet - br0 0
3 datavisuali users datavisuali_vnet - br0 0
...
Remember your Virtual Network ID or Virtual Network NAME.
Schema:
We use onetemplate with this syntax:
onetemplate create --name <nametemplate> --cpu <numcpu> --vcpu <numvcpu> --memory <mem> --arch x86_64 --disk <imageid> --nic <idvnet> --vnc --ssh --net_context
for example:
onetemplate create --name "Plantilla_CentOS" --cpu 1 --vcpu 1 --memory 512 --arch x86_64 --disk 9 --nic "manuelparra_vnet" --vnc --ssh --net_context
Those are the parameters explained:
- --name : Name of the template to indentify on OpenNebula
- --cpu : Number of CPUs. Integer. - --vcpu : Number of Virtual CPUs: can be 0.5, 1, 1.5 .... etc.
- --memory : RAM in MB, GB
- --arch: Architecture: x86_64, x86, … It should be the same than the image.
- --disk: ID of the DISK. This ID can be searched from oneimage list command.
- --nic : Name or ID of the VirtualNetwork
- --ssh: Access from SSH.
- --net_context: Network Context
To verify if the template was created:
onetemplate list
If we want to delete the template, first get the selected ID or NAME and then:
onetemplate delete <ID>
First, list your Virtual Machines list:
onevm list
and check again the list of my templates:
onetemplate list
And now, we create a new instance of a Virtual Machine:
onetemplate instantiate <IDtemplate>
for example:
onetemplate instantiate 63
It will returns an ID of the created Virtual Machine.
Because the start of the virtual machine takes time, we will see the state at each moment, so check list of your Virtual Machines:
onevm list
It will show:
ID USER GROUP NAME STAT UCPU UMEM HOST TIME
5 manuelpa users Plantilla_CentO runn 0 512M noded07 0d 01h13
In the STAT column we have the current state. RUNNING = RUN And information about Memory, HOST, etc.
Check the ID of your Virtual Machine:
onevm list
and get your Virtual Machine ID:
onevm show <ID>
onevm show 60
It will returns all information about your Virtual Machine.
The part that interests us of the details is to know that IP has been assigned to this machine created:
CONTEXT=[
DISK_ID="1",
ETH0_DNS="150.214.191.10",
ETH0_GATEWAY="192.168.10.1",
ETH0_IP="192.168.12.148",
ETH0_MAC="02:00:c0:a8:0c:94",
NETWORK=“YES",
....
So, our Virtual Machine IP to connect with SSH is: 192.168.10.148
We try to connect to the Virtual Machine:
ssh root@192.168.12.148
NOTE: It doesn't need password. WHY ?
Verify if you are connected to Internet:
ping -c2 google.com
The life-cycle of a Virtual Machine within OpenNebula includes the following stages/steps:
pend Pending By default a VM starts in the pending state, waiting for a resource to run on. It will stay in this state until the scheduler decides to deploy it, or the user deploys it using the onevm deploy command.
hold Hold The owner has held the VM and it will not be scheduled until it is released. It can be, however, deployed manually.
clon Cloning The VM is waiting for one or more disk images to finish the initial copy to the repository (image state still in lock)
prol Prolog The system is transferring the VM files (disk images and the recovery file) to the host in which the virtual machine will be running.
boot Boot OpenNebula is waiting for the hypervisor to create the VM.
runn Running The VM is running (note that this stage includes the internal virtualized machine booting and shutting down phases). In this state, the virtualization driver will periodically monitor it.
migr Migrate The VM is migrating from one resource to another. This can be a life migration or cold migration (the VM is saved and VM files are transferred to the new resource).
hotp Hotplug A disk attach/detach, nic attach/detach operation is in process.
snap Snapshot A system snapshot is being taken.
save Save The system is saving the VM files after a migration, stop or suspend operation.
epil Epilog In this phase the system cleans up the Host used to virtualize the VM, and additionally disk images to be saved are copied back to the system datastore.
shut Shutdown OpenNebula has sent the VM the shutdown ACPI signal, and is waiting for it to complete the shutdown process. If after a timeout period the VM does not disappear, OpenNebula will assume that the guest OS ignored the ACPI signal and the VM state will be changed to running, instead of done.
stop Stopped The VM is stopped. VM state has been saved and it has been transferred back along with the disk images to the system datastore.
susp Suspended Same as stopped, but the files are left in the host to later resume the VM there (i.e. there is no need to re-schedule the VM).
poff PowerOff
Same as suspended, but no checkpoint file is generated. Note that the files are left in the host to later boot the VM there.
Picture of stages:
You can terminate an instance with the onevm terminate command, from any state. It will shutdown (if needed) and delete the VM. This operation will free the resources (images, networks, etc) used by the VM.
There are two different ways to temporarily stop the execution of a VM: short and long term pauses. A short term pause keeps all the VM resources allocated to the hosts so its resume its operation in the same hosts quickly. Use the following onevm commands or Sunstone actions:
- suspend: the VM state is saved in the running Host. When a suspended VM is resumed, it is immediately deployed in the same Host by restoring its saved state.
- poweroff: Gracefully powers off a running VM by sending the ACPI signal. It is similar to suspend but without saving the VM state. When the VM is resumed it will boot immediately in the same Host.
- poweroff --hard: Same as above but the VM is immediately powered off. Use this action when the VM doesn’t have ACPI support.
- stop: Same as undeploy but also the VM state is saved to later resume it.
When the VM is successfully paused you can resume its execution with:
- resume: Resumes the execution of VMs in the stopped, suspended, undeployed and poweroff states.
Use the following commands to reboot a VM:
- reboot: Reboots a running VM, sending the ACPI signal.
- reboot --hard: Performs a ‘hard’ reboot.
Go to: http://docker.ugr.es:9869/ and follow the next steps:
- Connect to docker server ugr:
ssh manuparra@..... - Authenticate using:
oneuser login mdatXXXXXXXX --ssh --force - Execute:
cat .one/one_authit will show your SunStone credentials in this format:<user>:<password>, for example:manuparra:7374j31g74hd7234 - Copy the corresponding part of password and paste http://docker.ugr.es:9869/ login and password.