summaryrefslogtreecommitdiffstats
path: root/docs/submodules/fuel
diff options
context:
space:
mode:
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>2018-08-08 11:03:17 +0000
committerGerrit Code Review <gerrit@opnfv.org>2018-08-08 11:03:17 +0000
commit4398d9bff0d1672e6eee07ceb6b2d01f3a14a659 (patch)
treeb58bf3038660e2fe7af342532b9935f35642f2a6 /docs/submodules/fuel
parent6a3654e5a7140602a9247417946ed7fae3f2c2d7 (diff)
Update git submodules
* Update docs/submodules/fuel from branch 'master' - Merge changes from topic 'baremetal-noha' * changes: [states] baremetal_init: Parameterize kvm hosts [scenarios] Differentiate virtual node roles - [states] baremetal_init: Parameterize kvm hosts Instead of hardcoding the 'kvm' hostnames, use new targeting mechanism based on scenario-specific node names, preparing for baremetal noha scenario integration. JIRA: FUEL-382 Change-Id: If336aa1ac130749e4df7bffaf27a55513dd4f267 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> - [scenarios] Differentiate virtual node roles Split scenario yaml definitions for virtual.nodes based on node role ('infra', 'control' or 'compute'), to be leveraged later to contruct node lists based on said role. This moves the responsability of filtering node names in scenario files (based on 'virtual' or 'baremetal' type) to xdf_data.sh.j2, simplifying scenario templates. By keeping all nodes (both virtual and baremetal) in scenario files, we can later determine the role (and implicitly the hostname) for a MaaS-managed node based on its index in the virtual.nodes.control structure. JIRA: FUEL-382 Change-Id: I1f83a307631f4166ee1c57ef598c44876b962f97 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
Diffstat (limited to 'docs/submodules/fuel')
m---------docs/submodules/fuel0
1 files changed, 0 insertions, 0 deletions
diff --git a/docs/submodules/fuel b/docs/submodules/fuel
-Subproject 143bf770cf104daaf8d457a3de294d6acb33f9c
+Subproject 6a3bbf95c70207a146c5b2c82d8518cf02e5c26