Hi All,
Just need some clarification and would like to get you guys feedback on
managing VMs using OpenNebula in your environment.
Our current practice as below (using OpenNebula 4.2):
1. New VM request
- Clone existing image (master image) to a new image. All the images
are persistent.
- Clone existing template (master template) to a new template.
- Update the new template - set cpu/vcpu, memory, image (point to
newly created image), ip address, etc
- Instantiate the template
2. Update the spec of the VM
- Shutdown / delete the running VM
- Update the template belongs to that particular VM - e.g set the new
memory size
- Instantiate the template
Note: a) In our setup, every VM will have their own template as per done in #1
b) Reason being update the template & re-instantiate instead of
just update the memory in VM is because of #3 below
3. Repair the VM
- In some cases the VM's filesystem will have some errors (eg: due to
force shutdown / nfs issues) therefore require to run fsck using live CD.
- Image type CDROM cannot be attached thru VM list page (click on the
VM -> storage tab)
- Update the VM's template - add disk and choose the ISO image, choose
boot = cdrom
- Instantiate the template and fix the errors using the live CD
- Shutdown / delete the running VM
- Update the VM's template - remove the ISO image and choose boot = hd
- Instantiate the template
>From the above scenario, anything that we are doing inefficiently? Im still
>new to this OpenNebula so appreciate you guys feedback / suggestion
Testing environment (OpenNebula 4.8)
To further understand on this OpenNebula, I have setup ONE 4.8 and testing the
Cloud View and see how I can improve my operation / VM administration.
The way user can create VM in Cloud View is the one I need - user define the VM
name, choose the template (OS), set the memory & CPU and launch it. Very
simple. But unfortunately this only works with non-persistent image type. In my
case, I cannot use non-persistent image because of the reason stated in #2 and
#3 above.
So what I think Cloud View can be improved is:
- Based on config parameter (oned.conf -> ONE_DEPLOY=Persistent),
when user create a VM, a template should be created and the image should be
cloned as persistent image. This is kinda same behavior as "Save" VM with only
different is the image persistent yes/no and template spec
- Able to attach / detach CDROM
Feel free to comment on this and provide some feedback.
--
Regards,
Anandharaj
________________________________
DISCLAIMER:
This e-mail (including any attachments) is for the addressee(s) only and may be
confidential, especially as regards personal data. If you are not the intended
recipient, please note that any dealing, review, distribution, printing,
copying or use of this e-mail is strictly prohibited. If you have received this
email in error, please notify the sender immediately and delete the original
message (including any attachments).
MIMOS Berhad is a research and development institution under the purview of the
Malaysian Ministry of Science, Technology and Innovation. Opinions, conclusions
and other information in this e-mail that do not relate to the official
business of MIMOS Berhad and/or its subsidiaries shall be understood as neither
given nor endorsed by MIMOS Berhad and/or its subsidiaries and neither MIMOS
Berhad nor its subsidiaries accepts responsibility for the same. All liability
arising from or in connection with computer viruses and/or corrupted e-mails is
excluded to the fullest extent permitted by law.
_______________________________________________
Users mailing list
[email protected]
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
