summaryrefslogtreecommitdiffstats
path: root/mcp/reclass/classes/cluster/mcp-pike-odl-ha/openstack/compute_pdf.yml.j2
AgeCommit message (Collapse)AuthorFilesLines
2018-05-22[xdf] Fix parsing of non-range private vlan(s)Alexandru Avadanii1-1/+1
Private (tenant) vlan range support introduced a regression in parsing PDF/IDF with a single vlan (no range) due to the value being interpreted as an int instead of string. Change-Id: Id5d67c4c516a9bb807ffa5e111ead5cbcee7e2ca Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit 0bc600fd4d269a17ebcf28700b46e199d66c25db)
2018-04-23[ha] Fix tenant NIC OS config for VLAN rangesAlexandru Avadanii1-2/+3
Previous commits added support for tenant VLAN range parametrization, yet failed to accomodate the new VLAN range representation ('M:N') in existing `linux.network.interfaces` reclass configuration. This lead to the silent removal of <nic_private>.<vlan_private> from interfaces file and for `br-mesh` to try to use <nic_private> instead of <nic_private>.<vlan_private>, conflicting with `br-floating`. Stick to using the first VLAN in the tenant range. JIRA: FUEL-365 Change-Id: I88f7263159f1742dba3b6e36649c9344f2932c5f Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com> (cherry picked from commit cfc5988be48d1317244e71fd7919480db18745d4)
2018-03-03[j2 parsing] Adopt new generate_config featuresAlexandru Avadanii1-2/+2
- bump Pharos git submodule for j2 'do' extension + batch mode; - adopt j2 'do' in our templates; - use int filter for 'native' vlan check; - lib.sh: adopt `-i` to remove `ln` hack for net_map.j2; - lib.sh: adopt `-b` to speedup template parsing; NOTE: Bumping Pharos will also bring in the latest changes in pod_config.yml.j2, which include massive IP shifts and updates. JIRA: FUEL-335 Change-Id: I7d3a997b3d8659d5f09f867870fb3a148c1ec6df Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-02-05[baremetal] Rename all to drop baremetal prefixAlexandru Avadanii1-0/+48
A few things differ between baremetal and virtual nodes: - provisioning method; - network setup; Since now we support completely dynamic network config based on PDF + IDF, as well as dynamic provisioning of VMs on jumpserver (as virtual cluster nodes), respectively MaaS-driven baremetal provisioning, let's drop the 'baremetal-' prefix from cluster model names and prepare for unified scenarios. Note that some limitations still apply, e.g. virtual nodes are spawned only on jumpserver (localhost) for now. JIRA: FUEL-310 Change-Id: If20077ac37c6f15961468abc58db7e16f2c29260 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>