← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1843218] [NEW] [RFE] allow to create record on default zone from tenants

 

Public bug reported:

Neutron has, in DEFAULT section in neutron.conf file, a key dns_domain
which is a domain fallback.

Basically, if we create port with neutron, the default dns assigment
will be myport.defaultzone.com.

Currently, Designate Integration will create DNS record
myport.defaultzone.com. A portIP

The problem is, defaultzone.com. can be created only inside one and only
one tenant. So this feature works only for one tenant, because the
others has not access to this zone.

One of the solution I propose, is to integrate tenantid variable into default zone. So basically, create <tenantid>.defaultzone.com.
on each tenants, to allow users to have their DNS record myport.<tenantid>.defaultzone.com. inside their own tenant.

To sumarize,

When the user do openstack port create --network public --dns-name
myport port, a default record will be created at
myport.<tenantid>.defaultzone.com.

So, when a user creates an instance with nova, or port with neutron, we
want to create automatically dns record
myport.<tenantid>.defaultzone.com. inside his own tenant. (A and AAAA
fields)

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1843218

Title:
  [RFE] allow to create record on default zone from tenants

Status in neutron:
  New

Bug description:
  Neutron has, in DEFAULT section in neutron.conf file, a key dns_domain
  which is a domain fallback.

  Basically, if we create port with neutron, the default dns assigment
  will be myport.defaultzone.com.

  Currently, Designate Integration will create DNS record
  myport.defaultzone.com. A portIP

  The problem is, defaultzone.com. can be created only inside one and
  only one tenant. So this feature works only for one tenant, because
  the others has not access to this zone.

  One of the solution I propose, is to integrate tenantid variable into default zone. So basically, create <tenantid>.defaultzone.com.
  on each tenants, to allow users to have their DNS record myport.<tenantid>.defaultzone.com. inside their own tenant.

  To sumarize,

  When the user do openstack port create --network public --dns-name
  myport port, a default record will be created at
  myport.<tenantid>.defaultzone.com.

  So, when a user creates an instance with nova, or port with neutron,
  we want to create automatically dns record
  myport.<tenantid>.defaultzone.com. inside his own tenant. (A and AAAA
  fields)

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