Age | Commit message (Collapse) | Author | Files | Lines |
|
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)
|
|
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)
|
|
- dummy copy of os-nosdn-nofeature-ha masquerading as
os-ovn-nofeature-ha scenario placeholder;
JIRA: FUEL-329
Change-Id: Ic5e6d65cf057289bb13ce2fa157b6ba53d7dab80
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|