[Openstack-operators] [openstack-dev] [Neutron] Allowing DNS suffix to be set per subnet (at least per tenant)
blak111 at gmail.com
Thu Sep 3 21:21:43 UTC 2015
Support for that blueprint already merged so it's a little late to
change it to per-subnet. If that is too fine-grained for your use-case, I
would file an RFE bug to allow it to be set at the subnet level.
On Thu, Sep 3, 2015 at 1:07 PM, Maish Saidel-Keesing <maishsk at maishsk.com>
> On 09/03/15 20:51, Gal Sagie wrote:
> I am not sure if this address what you need specifically, but it would be
> worth checking these
> two approved liberty specs:
> Thanks Gal,
> So I see that from the bp  the fqdn will be configurable for each and
> every port ?
> I think that this does open up a number of interesting possibilities, but
> I would also think that it would be sufficient to do this on a subnet level?
> We do already have the option of setting nameservers per subnet - I assume
> the data model is already implemented - which is interesting - because I
> don't see that as part of the information that is sent by dnsmasq so it
> must be coming from neutron somewhere.
> The domain suffix - definitely is handled by dnsmasq.
> On Thu, Sep 3, 2015 at 8:37 PM, Steve Wormley <openstack at wormley.com>
>> As far as I am aware it is not presently built-in to Openstack. You'll
>> need to add a dnsmasq_config_file option to your dhcp agent configurations
>> and then populate the file with:
>> domain=DOMAIN_NAME,CIDR for each network
>> On Thu, Sep 3, 2015 at 1:04 AM, Maish Saidel-Keesing <
>> <maishsk at maishsk.com>maishsk at maishsk.com> wrote:
>>> Hello all (cross-posting to openstack-operators as well)
>>> Today the setting of the dns suffix that is provided to the instance is
>>> passed through dhcp_agent.
>>> There is the option of setting different DNS servers per subnet (and and
>>> therefore tenant) but the domain suffix is something that stays the same
>>> throughout the whole system is the domain suffix.
>>> I see that this is not a current neutron feature.
>>> Is this on the roadmap? Are there ways to achieve this today? If so I
>>> would be very interested in hearing how.
>>> Best Regards,
>>> Maish Saidel-Keesing
>>> OpenStack Development Mailing List (not for usage questions)
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Best Regards ,
> The G.
> Best Regards,
> Maish Saidel-Keesing
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-operators