DM: improve names used in generated configuration
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Won't Fix
|
Low
|
Suresh Balineni | |||
R3.0 |
Won't Fix
|
Low
|
Suresh Balineni | |||
R3.1 |
Won't Fix
|
Low
|
Suresh Balineni | |||
Trunk |
Fix Committed
|
Low
|
Suresh Balineni |
Bug Description
Following changes should be implemented:
1. Consistently use __contrail__ as prefix not just anywhere in the name.
For example sv-__contrail_
2. The dynamic-tunnels name should be changed from __contrail__ to
__contrail-
cluster.
3. Similar to 2 above, the __contrail__ and __contrail_
should also contain the global ASN.
4. Community names should have __contrail__ prefix to valid conflicts with
manually configured communities.
5. The RI and policy names should have the name before the uuid so that
it becomes easier to find them using JUNOS CLI - auto-completion will
work better if the name is before the uuid string.
6. After JUNOS limitation with service-set and rule names is fixed, we
should use the BMS IP and FIP in the snat and dnat rule name instead
of just using a number. That will minimize name changes (and reduce
chances of data plane churn) when a FIP is added/removed from BMS.
The dots in address can be replaced with underscores.
7. Filter names for redirect to nat RIs should
8. Filter name redirect_
__contrail_
9. Consistently use hyphen (-) as separator in generated names. We
currently use a mix of hypen and underscore arbitrarily. As a convention,
the only place we should use underscore is for the __contrail__ prefix.
10. Filter name used to direct traffic to nat should contain the vn name.
Change redirect_
___contrail_
description: | updated |
description: | updated |
description: | updated |
description: | updated |
bug update...