summaryrefslogtreecommitdiffstats
path: root/docs/templates/release/configguide/feature.configuration.rst
diff options
context:
space:
mode:
authorMarkos Chandras <mchandras@suse.de>2018-04-03 09:33:17 +0000
committerGerrit Code Review <gerrit@opnfv.org>2018-04-03 09:33:17 +0000
commita7222a155895e8459cb06287153d8577b00702bc (patch)
treece31d921a3668a72f64692c40635409cf72d8cdc /docs/templates/release/configguide/feature.configuration.rst
parente8b7a664081b4f13837cee5f81024f887d51e3e8 (diff)
Update git submodules
* Update docs/submodules/releng-xci from branch 'master' - Merge changes from topic 'misc-simplifications-osa' * changes: xci: bootstrap-host: Make active network interface consistent xci: osa: Simplify tasks for copying OSA configuration files xci: Use proper Ansible modules to manage SSH keys - xci: bootstrap-host: Make active network interface consistent When we run XCI for the first time, Ansible picks the first active interface as the default one. However, after we configure all the XCI bridges etc, and we try to run this role again, Ansible may have changed its mind about what interface is active and it could default to one of the bridges. This forces the role to redo the network configuration but this time the bridges are being attached to bridges so everything goes terribly wrong after that. The way to solve this would be to add a local fact about what interface should be considered as the 'real' default one so subsequent calls to this role to not destroy the network. This also drops the task which removed the network configuration files on SUSE platforms since Ansible is smart enough to not touch them if they are configured properly. Change-Id: Ic0525e934b1934a40d69e6cf977615ab9b3dac6d Signed-off-by: Markos Chandras <mchandras@suse.de> - xci: osa: Simplify tasks for copying OSA configuration files We can use a loop to copy all these files instead of multiple tasks. This simplifies the playbook quite a bit. Change-Id: I5f0d387ac090d81fc577b5ebeaeb6131e75cffa1 Signed-off-by: Markos Chandras <mchandras@suse.de> - xci: Use proper Ansible modules to manage SSH keys We can use the 'user', 'slurp' and 'authorized_key' modules to manage the various SSH configurations across the hosts instead of using command line tools. Change-Id: I2dde4d584fc336e267868607d5a58f5ee2c1feed Signed-off-by: Markos Chandras <mchandras@suse.de>
Diffstat (limited to 'docs/templates/release/configguide/feature.configuration.rst')
0 files changed, 0 insertions, 0 deletions