[one-users] Virtual machine hostname contextualization

[Jean-Philippe Garcia Ballester]

  Hi,
  Yes, it seems to me it was broken in c483e7bba0800373f3a79e6a07bb4cbe31fe2e64 when replace_template_attribute("NAME", name); was removed.
  Thanks !

On Tuesday 16 April 2013 11:13:35 Carlos Martín Sánchez wrote:
> Hi,
> 
> We changed a bit the VM template for 4.0 and it looks like we broke this.
> The fix is simple, so it will be included in the final release [1].
> 
> Thanks for testing the beta!
> 
> [1] http://dev.opennebula.org/issues/1915
> 
> --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - The Open-source Solution for Data Center Virtualization
> www.OpenNebula.org | cmartin at opennebula.org |
> @OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>
> 
> 
> On Tue, Apr 16, 2013 at 10:33 AM, Jean-Philippe Garcia Ballester <
> giga at le-pec.org> wrote:
> 
> >   Hi,
> >   Thank you for your reply and your patience. Unfortunately it does not
> > work. I am using OpenNebula 4.0 beta (3.9.80). Maybe it is a regression ?
> >   Regards,
> >
> > On Monday 15 April 2013 12:47:29 Campbell, Bill wrote:
> > > Sorry, that was a misunderstanding of the question.  I misread in how we
> > define HOSTNAME=<some random name here> in the contextualization script.
> > >
> > > If you want to use the hostname, then add this as your context variable:
> > >
> > > HOSTNAME=$NAME
> > >
> > > That should do it.
> > >
> > > ----- Original Message -----
> > > From: "Jean-Philippe Garcia Ballester" <giga at le-pec.org>
> > > To: "Bill Campbell" <bcampbell at axcess-financial.com>
> > > Sent: Monday, April 15, 2013 9:22:57 AM
> > > Subject: Re: [one-users] Virtual machine hostname contextualization
> > >
> > >    Hi,
> > >    I have not seen anything in the 3.8 contextualization package that
> > > would use a variable named HOSTNAME, nor anything that would actually
> > > change the hostname.
> > >    Also, I have not found how to automatically fill a contextualization
> > > variable with the actual name of the VM.
> > >    For example
> > > CONTEXT=[
> > >    TEST="$VMID" ]
> > >    in the vm template will be correctly replaced by
> > > TEST="55"
> > >    in the generated context.sh for the instantiated VM. But
> > > CONTEXT=[
> > >    TEST="$HOSTNAME" ]
> > >    will not result in anything in context.sh.
> > >    Regards,
> > >
> > > On 15/04/2013 14:57, Campbell, Bill wrote:
> > > > Should just be the HOSTNAME variable.  So long as your VM template
> > > > has the contextualization packages installed it should take that
> > > > variable and apply the appropriate hostname on boot.
> > > >
> > > > ----- Original Message -----
> > > > From: "Jean-Philippe Garcia Ballester" <giga at le-pec.org>
> > > > To: users at lists.opennebula.org
> > > > Sent: Monday, April 15, 2013 4:23:58 AM
> > > > Subject: [one-users] Virtual machine hostname contextualization
> > > >
> > > >   Hi,
> > > >   I am currently experimenting on opennebula 4.0 beta to satisfy my
> > > > personal curiosity. I was thinking of creating a non-persistent image
> > > > with a basic Debian installation, a chef-client, and just enough
> > > > contextualization to let the VM connect to the chef server and
> > > > configure itself.
> > > >   However, I did not find any contexualization variable for the
> > > > template that would be replaced by the name of the instantiated VM.
> > > > Is
> > > > there such a variable ?
> > > >   Regards,
> > >
> > >
> > --
> > Jean-Philippe Garcia Ballester
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >
> >
-- 
Jean-Philippe Garcia Ballester
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20130416/00aa293c/attachment-0002.pgp>