R5.0-micro-services provisioning fails when hosts of cluster has different interface names

[Sudheendra Rao]

R5.0 micro-services provision fails when hosts in a cluster has different interface names.
Need to have host specific parameters to take care of this scenario.

openstack/contrail controller nodes have interface as enp1s0f1 but computes interface name is eno2.
Below error is seen during provisioning.

TASK [common : Copying over fluentd input config files] **********************************************************************************************************************************
ok: [192.168.192.2] => (item=00-global)
ok: [192.168.192.3] => (item=00-global)
failed: [192.168.192.2] (item=01-syslog) => {"changed": false, "item": "01-syslog", "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute u'ansible_enp1s0f1'"}
failed: [192.168.192.3] (item=01-syslog) => {"changed": false, "item": "01-syslog", "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute u'ansible_enp1s0f1'"}
ok: [192.168.192.3] => (item=02-mariadb)
ok: [192.168.192.2] => (item=02-mariadb)

Copying the snapshot of the email exchange about this problem:

the contrail containers support global and per instance.role configuration.
I will add per instance configuration (applied to all roles within an instance). We will then have global, instance and role level.
Ram will do the same for the kolla containers.

Regards,
Michael

Am 05.03.2018 um 21:40 schrieb Ramprakash Ram Mohan <email address hidden>:

Hi Sudhee,

Looks like there is no way to do this now. Please raise a bug and assign it to me. Shall work on this on priority.
Previously, we were able to do this because we had a static inventory file where we can plug in host specific parameters along with the host line. Now the inventory is dynamically calculated (no inventory file is used. The inventory file generated is just for reference). So all host specific parameters have to be generated as well.

Thanks,
Ram

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/40369
Submitter: Ramprakash R (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/40369
Committed: http://github.com/Juniper/contrail-ansible-deployer/commit/9f88202bc7bad360f15f391aecfc5ed945a097ac
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 9f88202bc7bad360f15f391aecfc5ed945a097ac
Author: Ramprakash Ram Mohan <email address hidden>
Date: Tue Mar 6 23:43:41 2018 -0800

Support host-level params for kolla

Host-level kolla parameters can be specified at host level (per role) like below:

instances:
bms1:
provider: bms
ip: 192.168.1.51
roles:
openstack:
network_interface: eth0
kolla_external_vip_interface: eth1
bms2:
provider: bms
ip: 192.168.1.52
roles:
openstack:
network_interface: eno1
kolla_external_vip_interface: eno2
bms3:
provider: bms
ip: 192.168.1.53
roles:
openstack_compute:
network_interface: bond1
kolla_external_vip_interface: bond0
vrouter:
PHYSICAL_INTERFACE: bond1

Change-Id: If91ce97113bc8095b73aff4af348a50d058acc8b
Closes-Bug: #1753642