yahoo-eng-team team mailing list archive

[Joe Gordon <1198767@xxxxxxxxxxxxxxxxxx>]

Grizzly has been 'end of life'ed is this bug still valid?

** Changed in: nova
       Status: New => Invalid

** Changed in: nova
       Status: Invalid => New

** Changed in: nova
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1198767

Title:
  Nova does not pick up on dhcp_domain from Quantum

Status in OpenStack Compute (Nova):
  Incomplete

Bug description:
  I'm using Grizzly with the RedHat RDO packages.

  I am using Quantum networking with the following in /etc/quantum/dhcp_agent.ini:
  dhcp_domain=mydomain.com

  This works properly and sets the correct domain for new Nova instances
  which obtain their hostname and domain via dhcp. However, if you ask
  the Metadata service for the hostname it returns with 'novalocal'.

  curl http://169.254.169.254/openstack/2012-08-10/meta_data.json

  {"uuid": "12345long_string", "availability_zone": "nova", "hostname":
  "smov0001.novalocal", "launch_index": 0, "public_keys": {"mykey":
  "ssh-rsa longkeygoeshere root@xxxxxxxxx\n"}, "name": "smov0001"}

  I looked into why that might be happening, and it seems that in Nova's
  network/manager.py it has the following stanza:

      cfg.StrOpt('dhcp_domain',
                 default='novalocal',
                 help='domain to use for building the hostnames'),

  So, essentially if you only place your custom dhcp_domain setting in
  Quantum's dhcp_agent.ini file it won't be picked up by Nova. If you
  ALSO place dhcp_domain=mydomain.com in nova.conf, the metadata service
  will return with the correct mydomain.com setting.

  This was non-obvious to me and created issues with cloud-init and
  orchestration. I'm not sure of the best way to address this but at the
  very least it's a documentation bug. Ideally Nova should be smart
  enough to know I am using Quantum networking and pick up the setting
  from there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1198767/+subscriptions