wrote:
>
>>
>> I don’t think there is a formal exit inside OpenStack to do this. You
>> may have to make a small patch to Nova.
>>
>> It would be an interesting feature to define a plug-in architecture for
>> this which would have several other uses.
>&g
to:cecca...@fnal.gov>]
> Sent: 14 September 2013 20:40
> To: Tim Bell
> Cc: openstack@lists.openstack.org
<mailto:openstack@lists.openstack.org>
> Subject: Re: [Openstack] openstack meta-data
>
> Hello,
> thanks for the help! I hadn't seen t
ginal Message-
> > From: Francesco Ceccarelli [mailto:cecca...@fnal.gov]
> > Sent: 14 September 2013 20:40
> > To: Tim Bell
> > Cc: openstack@lists.openstack.org
> > Subject: Re: [Openstack] openstack meta-data
> >
> > Hello,
> > thanks for the help! I hadn
arelli [mailto:cecca...@fnal.gov]
> Sent: 14 September 2013 20:40
> To: Tim Bell
> Cc: openstack@lists.openstack.org
> Subject: Re: [Openstack] openstack meta-data
>
> Hello,
> thanks for the help! I hadn't seen the command in the documentation, this can
> be helpful.
>
Hello,
thanks for the help! I hadn't seen the command in the documentation,
this can be helpful.
BTW my problem is to update metadata every time a machine is launched.
For example let's talk about the hostname. Every time I launch a
machine, I would like to have well-configured metadata, with the
p
You can update the metadata associated with an instance using the 'nova meta'
command. However, this only updates the metadata (i.e.
key value pairs) rather than the other attributes.
Changing the server name would not alter the hostname of the VM, it would only
alter the description in Nova.
