settingsLogin | Registersettings

[Openstack] domain name resets to novalocal (ignoring designate DNS zone)

0 votes

Dear Openstack community,

I am testing a big data cluster application that needs DNS service across the cluster (at the moment the cluster is running on vms for testing) so I decided to give designate a go.

Because my deployment is based on kolla-ansible so I decided to follow this document http://egonzalez.org/deploy-openstack-designate-with-kolla-ansible/ which has helped me a lot to get designate up and running.

The installation was successful and I could create a DNS zone and assign it to my private network.

The problem I am having is that the instance domain changes from what I have in designate (garvan.openstack.org.) to nova (novalocal) when the instance reboots.

For instance:

I create a new vm and the FQDN (hostname -f) is myvm.garvan.orpenstack.org but after reboot it changes to myvn.novalocal.

This is what I can see from journal

[centos@myvm ~]$ journalctl | grep novalocal
...
Jun 01 11:52:13 myvm cloud-init[822]: [CLOUDINIT] ccsethostname.py[DEBUG]: Setting the hostname to myvm.novalocal (myvm)
...

My questions is, why is this happening and why is cloud-init or nova not following the setup from designate? Is this an issue with nova, neutron or designate and how can I fix it?

I am running ocata and my environment is quite standard so I assume this issue may be affecting many people.

Thank you very much

Manuel Sopena Ballesteros | Big data Engineer
Garvan Institute of Medical Research
The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010
T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: manuel.sb@garvan.org.aumanuel.sb@garvan.org.au

NOTICE
Please consider the environment before printing this email. This message and any attachments are intended for the addressee named and may contain legally privileged/confidential/copyright information. If you are not the intended recipient, you should not read, use, disclose, copy or distribute this communication. If you have received this message in error please notify us at once by return email and then delete both messages. We accept no liability for the distribution of viruses or similar in electronic communications. This notice should not be removed.


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
asked Jun 1, 2017 in openstack by Manuel_Sopena_Balles (600 points)   1 3 6

1 Response

0 votes

On 01/06/17 13:03, Manuel Sopena Ballesteros wrote:
Dear Openstack community,

I am testing a big data cluster application that needs DNS service
across the cluster (at the moment the cluster is running on vms for
testing) so I decided to give designate a go.

Because my deployment is based on kolla-ansible so I decided to follow
this document
http://egonzalez.org/deploy-openstack-designate-with-kolla-ansible/
which has helped me a lot to get designate up and running.

The installation was successful and I could create a DNS zone and assign
it to my private network.

The problem I am having is that the instance domain changes from what I
have in designate (garvan.openstack.org.) to nova (novalocal) when the
instance reboots.

For instance:

I create a new vm and the FQDN (hostname -f) is
myvm.garvan.orpenstack.org but after reboot it changes to myvn.novalocal.

This is what I can see from journal

[centos@myvm ~]$ journalctl | grep novalocal

Jun 01 11:52:13 myvm cloud-init[822]: [CLOUDINIT]
ccsethostname.py[DEBUG]: Setting the hostname to myvm.novalocal (myvm)

My questions is, why is this happening and why is cloud-init or nova not
following the setup from designate? Is this an issue with nova, neutron
or designate and how can I fix it?

I think the issue is with neutron - did you set up the neutron dns
extension?

There is good guide for that here:
https://docs.openstack.org/mitaka/networking-guide/config-dns-int.html

This allows the domain used by the network to be set as a custom one.

Thanks,

Graham

I am running ocata and my environment is quite standard so I assume this
issue may be affecting many people.

Thank you very much

Manuel Sopena Ballesteros *| Big data Engineer
*Garvan Institute of Medical Research *
The Kinghorn Cancer Centre,
370 Victoria Street, Darlinghurst, NSW 2010
*T:
+ 61 (0)2 9355 5760 | F: +61 (0)2 9295
8507 | E: manuel.sb@garvan.org.au manuel.sb@garvan.org.au

NOTICE
Please consider the environment before printing this email. This message
and any attachments are intended for the addressee named and may contain
legally privileged/confidential/copyright information. If you are not
the intended recipient, you should not read, use, disclose, copy or
distribute this communication. If you have received this message in
error please notify us at once by return email and then delete both
messages. We accept no liability for the distribution of viruses or
similar in electronic communications. This notice should not be removed.


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

responded Jun 1, 2017 by Graham_Hayes (1,060 points)  
...