[one-users] Recommended usage patterns

[Carlos Martín Sánchez]

Hi,

I'd like to add some comments on this:

On Fri, Dec 30, 2011 at 8:52 AM, Chris Picton <chris at ecntelecoms.com> wrote:

Ok - so for this type of VM, I should:
>      * Keep my vm definition templates in a known location
>      * Use persistent disks for them.
>      * Hardcode the MAC and VLAN/etc in the files
>      * If I need to make a change, I would shutdown the machine, edit
>        the file and create a new VM, bypassing the opennebula template
>        files.


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.

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.:

  NIC = [ NETWORK_ID = 7, IP = 192.168.2.3 ]

I just found OpenNebula Service Manager:
> http://opennebula.org/software:ecosystem:oneservice which seems to do
> exactly what I need
>
>
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.

Best regards,
Carlos

--
Carlos Martín, MSc
Project Engineer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | cmartin at opennebula.org |
@OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>


On Fri, Dec 30, 2011 at 8:52 AM, Chris Picton <chris at ecntelecoms.com> wrote:

> On Thu, 2011-12-29 at 15:21 +0100, richard -rw- weinberger wrote:
> > On Thu, Dec 29, 2011 at 10:20 AM, Chris Picton <chris at ecntelecoms.com>
> wrote:
> > > 1. Create a machine which will be long-lived, setting the hostname and
> > > specific parameters of this VM. Machines of this sort will probably
> > > last the lifetime of the opennebula installation.
> >
> > OpenNebula manages only them.
> > If you don't need OpenNebula in future you can still manage your VMs
> > using virsh.
> >
> > > 2. Edit an existing vm: Add more memory. Attach a new disk or disks.
> > > Create a new network adapter in the VM.
> >
> > Delete the VM, edit the template and start it again.
> > Sadly there is currently no way to do this while the VM is running. :(
>
>
> Ok - so for this type of VM, I should:
>      * Keep my vm definition templates in a known location
>      * Use persistent disks for them.
>      * Hardcode the MAC and VLAN/etc in the files
>      * If I need to make a change, I would shutdown the machine, edit
>        the file and create a new VM, bypassing the opennebula template
>        files.
>
> >
> > > 3. Create a cluster of machines which should start and stop in a
> > > particular order, but run together.
> >
> > Needs some scripting, but is definitely doable.
> I just found OpenNebula Service Manager:
> http://opennebula.org/software:ecosystem:oneservice which seems to do
> exactly what I need
>
> Thanks for the help
>
> Chris
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120102/00b6d1c4/attachment-0002.htm>