[openstack-dev] [openstack-ansible][neutron][designate] Failure trying to set dns_domain from command line
Lawrence J. Albinson
lawrence at ljalbinson.com
Tue Jun 27 22:53:59 UTC 2017
As ever, many thanks for clarifying that. And I shall put in a feature
request as you suggest.
In the meantime, presumably the missing pieces that I need are those
'Configuring OpenStack Networking for integration with an external
external_dns_driver = designate
url = .... etc ....
Kind regards, Lawrence
On 27/06/17 16:57, Graham Hayes wrote:
> On 27/06/17 16:36, Lawrence J. Albinson wrote:
>> Hi Graham,
>> Many thanks for the pointer. I hadn't added dns to the plugin list.
>> I did, however, set the following:
>> neutron_designate_enabled: True
> Ah - unfortunately there is two ways of integrating Neutron + Designate
> The external DNS plug, which allows you to use "--dns-domain" on a per
> network basis, and "designate-sink"
> designate-sink was written before Designate was an official project, and
> uses notifications. It is very powerful, but requires deployers to
> write custom plugins for it to work well.
> What OSA is missing is "neutron external DNS integration" - which is the
> code that we use for "--dns-domain"
> If you file a request here it will go on to the to do list:
> - Graham
>> I'm wondering if the two together will fix things. I shall know by the morning.
>> Again, many thanks.
>> Kind regards, Lawrence
>> From: Graham Hayes
>> Sent: 27 June 2017 16:14
>> To: openstack-dev at lists.openstack.org
>> Subject: Re: [openstack-dev] [openstack-ansible][neutron][designate] Failure trying to set dns_domain from command line
>> On 27/06/17 15:01, Lawrence J. Albinson wrote:
>>> Hello Colleagues,
>>> I am trying to enable dynamic updating of DNSaaS when a port or VM is
>>> I have DNSaaS working with Bind9 as the back-end and I am able to
>>> manually create/update/delete entries with the openstack client and/or
>>> the designate client and see Bind9 reflect those changes.
>>> However, I am unable to set a dns_domain name for a network from the
>>> openstack CLI and/or the neutron CLI.
>>> I have tried the following:
>>> neutron net-update --dns-domain example.com
>>> neutron net-update --dns-domain example.com public
>>> neutron net-update --dns-domain example.com.
>>> neutron net-update --dns-domain example.com. public
>>> The response is always the same, namely:
>>> Unrecognized attribute(s) 'dns_domain'
>>> Neutron server returns request_ids:
>>> Before I go searching through the Neutron source, does anyone know if
>>> this is a 'hole' in the Neutron API and, if so, has it been fixed after
>>> the commit point being used by openstack-ansible tag 15.1.3.
>>> Kind regards, Lawrence
>> Hi Lawrence,
>> Did you enable the DNS plugin in neutron?
>> Adding "dns" to the list here  should enable the --dns-domain
>> 0 -
>> However, it does not look like OpenStack Ansible code supports Neutron
>> calling Designate to update DNS Recordsets yet.
>> It looks like a missing feature - I am not sure how OSA deals with
>> feature requests, but if you are on IRC they use #openstack-ansible
>> - Graham
>>> Lawrence J Albinson
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev