Hi,<div><br></div><div>I'd like to add some comments on this:</div><div><br></div><div>On Fri, Dec 30, 2011 at 8:52 AM, Chris Picton <span dir="ltr"><<a href="mailto:chris@ecntelecoms.com">chris@ecntelecoms.com</a>></span> wrote:</div>
<div><br><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Ok - so for this type of VM, I should:<br>
* Keep my vm definition templates in a known location<br> * Use persistent disks for them.<br> * Hardcode the MAC and VLAN/etc in the files<br> * If I need to make a change, I would shutdown the machine, edit<br>
the file and create a new VM, bypassing the opennebula template<br> files.</blockquote><div><br></div><div>The modification of VMs during their execution is in our mid-term roadmap. Meanwhile, you don't really need to bypass the OpenNebula template pool. You can register your templates using 'onetemplate create', and edit existing ones with the 'onetemplate update' command. New VM instances will be created with the new attributes.</div>
<div><br></div><div>Regarding the MAC and VLAN, why do you need to hardcode them? If it is because you want to make sure the VM gets the same IP/MAC every time is is instantiated, you can still use an OpenNebula VNet and request a specific IP from that network in the template, e.g.:</div>
<div><br></div><div> NIC = [ NETWORK_ID = 7, IP = 192.168.2.3 ]</div><div><br></div><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I just found OpenNebula Service Manager:<br><a href="http://opennebula.org/software:ecosystem:oneservice" target="_blank">http://opennebula.org/software:ecosystem:oneservice</a> which seems to do<br>exactly what I need<br>
<br></blockquote><div><br></div>Please note that OpenNebula Service Manager is an ecosystem project developed for OpenNebula 2.0. I'm not familiar with the code, and I can't really tell if it is incompatible with the 3.x series... I'm guessing that the interaction with OpenNebula is limited to basic VM operations such as deploy and shutdown, so it may be worth to give it a try.</div>
<div><br></div><div>Best regards,</div><div>Carlos</div><div><br></div><div><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px">--<br>Carlos Martín, MSc<br>Project Engineer<br>
OpenNebula - The Open Source Toolkit for Data Center Virtualization<br><a href="http://www.OpenNebula.org" target="_blank">www.OpenNebula.org</a> | <a href="mailto:cmartin@opennebula.org" target="_blank">cmartin@opennebula.org</a> | <a href="http://twitter.com/opennebula" target="_blank">@OpenNebula</a></span><span style="border-collapse:collapse;color:rgb(136,136,136);font-family:arial,sans-serif;font-size:13px"><a href="mailto:cmartin@opennebula.org" style="color:rgb(42,93,176)" target="_blank"></a></span><br>
<br><br><div class="gmail_quote">On Fri, Dec 30, 2011 at 8:52 AM, Chris Picton <span dir="ltr"><<a href="mailto:chris@ecntelecoms.com">chris@ecntelecoms.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, 2011-12-29 at 15:21 +0100, richard -rw- weinberger wrote:<br>
> On Thu, Dec 29, 2011 at 10:20 AM, Chris Picton <<a href="mailto:chris@ecntelecoms.com">chris@ecntelecoms.com</a>> wrote:<br>
> > 1. Create a machine which will be long-lived, setting the hostname and<br>
> > specific parameters of this VM. Machines of this sort will probably<br>
> > last the lifetime of the opennebula installation.<br>
><br>
> OpenNebula manages only them.<br>
> If you don't need OpenNebula in future you can still manage your VMs<br>
> using virsh.<br>
><br>
> > 2. Edit an existing vm: Add more memory. Attach a new disk or disks.<br>
> > Create a new network adapter in the VM.<br>
><br>
> Delete the VM, edit the template and start it again.<br>
> Sadly there is currently no way to do this while the VM is running. :(<br>
<br>
<br>
</div>Ok - so for this type of VM, I should:<br>
* Keep my vm definition templates in a known location<br>
* Use persistent disks for them.<br>
* Hardcode the MAC and VLAN/etc in the files<br>
* If I need to make a change, I would shutdown the machine, edit<br>
the file and create a new VM, bypassing the opennebula template<br>
files.<br>
<div class="im"><br>
><br>
> > 3. Create a cluster of machines which should start and stop in a<br>
> > particular order, but run together.<br>
><br>
> Needs some scripting, but is definitely doable.<br>
</div>I just found OpenNebula Service Manager:<br>
<a href="http://opennebula.org/software:ecosystem:oneservice" target="_blank">http://opennebula.org/software:ecosystem:oneservice</a> which seems to do<br>
exactly what I need<br>
<br>
Thanks for the help<br>
<span class="HOEnZb"><font color="#888888"><br>
Chris<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opennebula.org">Users@lists.opennebula.org</a><br>
<a href="http://lists.opennebula.org/listinfo.cgi/users-opennebula.org" target="_blank">http://lists.opennebula.org/listinfo.cgi/users-opennebula.org</a><br>
</div></div></blockquote></div><br></div>