Open Stack

I wonder if cloud-init() is widely used. I don't use userdata feature in my
setting. However I plan to use cloud-init to fix host table for fixed IP
lookups.

I agree with your comment on separating fqdn for internal and external IPs.

Murali Balcha


On Mon, Apr 28, 2014 at 10:17 PM, gustavo panizzo <gfa> <gfa at zumbi.com.ar>wrote:

> On 04/28/2014 07:52 PM, Muralidhar Balcha wrote:
> > Thanks Dennis. Neutron and Nova are two different databases. Either
> > Neutron need to query the hostname using nova client or nova should pass
> > in the hostname to neutron agent.  It is doable if not impossible to get
> > the hostname associated with vif/port pair. It needs to be part of the
> > code. There are pending blue prints describing this feature. Hopefully
> > it makes it to Juno.
>
> if you use cloud-init and setup the metadata network you should get the
> hostname of the vm setup. for the dns resolution you should use
> something external, probably designate or a custom solution
>
> >
> > Floating IPs are another way to get around this issue, but VMs that are
> > closely related such as hadoop nodes should resolve fixed IP addresses
> > and be able to communicate over its private network.
>
> i wouldn't use the same fqdn for internal ip and floating ip. most of
> the time i provision hostname for floating ip in advance
>
> example:
>
> app.example.com --> floating ip1
>
> then i attach floating ip1 to any vm i want or a LB
>
> --
> 1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
>



-- 
Muralidhar Balcha
508 494 5007
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20140429/37852717/attachment.html>