MetaCloud testbed - workflow example
THIS PART OF WIKI IS OUTDATED AND UNDER CONSTRUCTION. PLEASE BE PATIENT.
(Czech version) For better understanding of how to work with cloud, we prepared a simple use case for you, where we will illustrate the basic functionality of MetaCloud.
Web interface usage example
The easiest way is to use one of the templates and images we prepared for you. You can find their lists in the Virtual Resources section in the left menu within the section Templates and Images. Choose the template you want to start and click on the Initiate button in the top right menu.Now, you can connect via ssh to your virtual machine which address you can find in column VM's IP(s). All our virtual machines' images are non-persistent. That means all data stored on the virtual machine are lost after its shutdown. If you need a virtual machine which keep data aftre its shutdown you have to upload your own image to MetaCloud [[upload image or copy one of our images. You can do that in images section by clicking on the Clone button in the top right menu. Now you can set your image to persistent in Persistent column. Don't forget that your new image has different ID (ID column) so you have to support it with right template. You can create a new one or you can copy and modify one of our prepared templates. Again you can choose the template from the list and click on Clone button in the top right menu. Click on the Update properties button and you will be shown a dialogue with templates properties. Find the row IMAGE_ID and set to the ID of your new image. Now when you start the virtual machine with your peristent image all chages and data will be stored aftre the machine shutdown. You can start only one virtual machine with persistent image. If you need more virtual machines with this modified image, change the image back to non-persistent and than you can run more of them.
Command line usage example
We suppose you have correctly configured and functioning environment with OpenNebula client tools. The easiest way is to use one of the templates and images we prepared for you.
$ oneimage list ID USER GROUP NAME DATASTORE SIZE TYPE PER STAT RVMS 8 oneadmin users debian6 default 8G OS No rdy 0 41 oneadmin users scilinux5 default 10G OS No rdy 0 42 oneadmin users scilinux6 default 10G OS No rdy 0
$ onetemplate list ID USER GROUP NAME REGTIME 5 oneadmin users debianvm 02/15 18:27:09 55 oneadmin users scilinux5vm 04/24 13:04:17 56 oneadmin users scilinux6vm 04/24 13:05:04
Now you can start a virtual machine.
$ onetemplate instantiate 5 VM ID: 1977
When the machine is running you can establish a connection via ssh.
$ onevm show 1977 VIRTUAL MACHINE 1977 INFORMATION ----------------------------- ... NIC=[ BRIDGE=xenbr0, CLUSTER_ID="100", IP=<IP_ADRESA_VM>, # address for SSH connction with VM MAC=02:00:c0:a8:fe:03, NETWORK=public, NETWORK_ID="1", VLAN="NO", WHITE_PORTS_TCP="22", WHITE_PORTS_UDP="67,68" ] ...
All our virtual machines' images are non-persistent. That means all data stored on the virtual machine are lost after its shutdown. If you need a virtual machine keep data aftre its shutdown you have to upload your own image to MetaCloud [[upload image or copy one of our images.
$ oneimage clone debian6 MyImage ID: 371
Now you can set image persistence.
$ oneimage persistent 371
Don't forget that your new image has different ID (ID column) so you have to support it with right template. You can create a new one or you can copy and modify one of our prepared templates.
$ onetemplate clone debianvm MyTemplate ID: 584 $ onetemplate update 584
Find the row IMAGE_ID and set to the ID of your new image. Now when you start the virtual machine with your peristent image all chages and data will be stored aftre the machine shutdown. You can start only one virtual machine with persistent image. If you need more virtual machines with this modified image, change the image back to non-persistent and than you can run more of them.