openstack team mailing list archive

[Mark McClain <mark.mcclain@xxxxxxxxxxxxx>]

Thomas-

You are not missing anything.  The DHCP hostname is auto generated because Nova does not currently provide this information to Quantum when creating the port and Quantum does not have the ability to query the Nova API.  Quantum and Nova should not directly access the other component's database, so changes would be needed in API interaction between Nova and Quantum to make this work.

mark

On Jan 3, 2013, at 4:52 AM, Thomas Kärgel <kaergel@xxxxxxxxxxxxx> wrote:

> Hello,
> 
> i noticed that Quantum DHCP agent does not put the instance-name in
> dnsmasq configuration files.
> This was working fine under Essex using Quantum/Nova-network.
> 
> I found the lines of source which generate the "-"-separated hostname in
> quantum/agent/linux/dhcp.py, but i'm not sure why it is generated this way.
> Is there any concern about accessing the database from
> quantum/agent/linux/dhcp.py to retrieve the correct instance-name?
> 
> Or am I missing some configuration details?
> 
> Kind regards
> thomas
> 
> 
> -- 
> Thomas Kärgel
> Linux Consultant
> Mail: kaergel@xxxxxxxxxxxxx
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp