Update on this issue.
n-c-c is configuring the hosts keys for each node for the following entries:
* private-address of the compute node on the cloud-compute relation, which in our env is the internal space
* hostname on cloud-compute relation data (which is the hostname w/o domain)
* reverse lookup entry of the private-address that in maas environments return the fqdn with the interface name at the beginning:
``` >>> import charmhelpers.contrib.openstack.utils as ch_utils >>> print(ch_utils.get_hostname("192.168.52.50")) bond0.123.my-host.maas ```
The correct entry is only returned for reverse lookup on the oam space which is the boot interface
Update on this issue.
n-c-c is configuring the hosts keys for each node for the following entries:
* private-address of the compute node on the cloud-compute relation, which in our env is the internal space
* hostname on cloud-compute relation data (which is the hostname w/o domain)
* reverse lookup entry of the private-address that in maas environments return the fqdn with the interface name at the beginning:
``` contrib. openstack. utils as ch_utils utils.get_ hostname( "192.168. 52.50") ) 123.my- host.maas
>>> import charmhelpers.
>>> print(ch_
bond0.
```
The correct entry is only returned for reverse lookup on the oam space which is the boot interface