Activity log for bug #1843218

Date Who What changed Old value New value Message
2019-09-09 04:44:09 Gregoire Mahe bug added bug
2019-09-10 05:08:40 Gregoire Mahe 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) 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) -- USECASE -- We want to allow default DNS when a user creates instance without specifying dns domain / dns name. Like S3 with AWS, when you creates a bucket, you have a default dns. (I don't know if this is the same with EC2, but I think so.
2019-09-11 08:53:00 Dr. Jens Harbott bug added subscriber Dr. Jens Harbott
2019-09-11 12:32:37 Arnaud Morin bug added subscriber Arnaud Morin
2019-09-13 00:30:31 Miguel Lavalle tags rfe
2019-09-13 00:57:48 Miguel Lavalle neutron: importance Undecided Wishlist
2019-09-18 10:38:20 Gregoire Mahe neutron: assignee Gregoire Mahe (gregoiremahe)
2019-09-18 10:38:31 Gregoire Mahe neutron: status New In Progress
2019-09-19 23:19:16 Miguel Lavalle neutron: status In Progress Triaged
2019-09-26 23:28:49 Miguel Lavalle tags rfe rfe-confirmed
2019-09-27 09:47:38 Slawek Kaplonski tags rfe-confirmed rfe-triaged
2019-10-04 16:51:36 Slawek Kaplonski tags rfe-triaged rfe-approved
2019-11-19 10:58:45 Slawek Kaplonski neutron: milestone ussuri-1
2019-11-20 13:37:44 Slawek Kaplonski neutron: milestone ussuri-1
2020-09-01 15:33:04 Zoltan Arnold Nagy bug added subscriber Zoltan Arnold Nagy
2021-01-06 14:39:29 Andrew Bogott bug added subscriber Andrew Bogott