...
Analysis from CCVPN Schema Changes in Casablanca Release
See also also:
- AAI-CCVPN Schema Proposal for Casablanca Release
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI-1353
Schema Change Description | CCVPN Example | |
---|---|---|
1 | Add new top-level schema element in existing namespace
| AAI-1353-1 ("Network" and "Business" namespaces) AAI-1353-3 ("connectivity" element) AAI-1353-5 ("sp-partner" element) AAI-1353-7 ("lan-port-config" element) AAI-1353-8 ("site-resource" element) AAI-1353-10 ("network-resource" element) AAI-1353-12 ("ext-aai-networks" element as workaround) AAI-1353-13 ("sdwan-vpn" element) AAI-1353-14 ("device" element) AAI-1353-15 ("wan-port-config" element) |
2 | Add new properties to existing schema element | AAI-1353-2 ("service-instance" element) AAI-1353-4 ("vpn-binding" element) AAI-1353-6 ("allotted-resource" element) AAI-1353-9 ("complex" element) AAI-1353-11 ("p-interface" element) AAI-1353-15 ("pnf" element) |
3 | Add new sub-component schema element in existing namespace | AAI-1353-7b ("dhcp-service" element) |
4 | Add new relationships to between existing schema elements | tbc |
5 | Add new relationships between new schema element and existing schema element | tbc |
6 | Add new EdgeRules between existing schema elements | tbc |
7 | Add new EdgeRules between new schema element and existing schema element | tbc |
8 | Add new namespace | AAI-1353-12 ("ext-aai" element), see workaround "ext-aai-networks" |
9 | Add new sub-component relationship using existing top-level schema element | tbc |
10 | Add new top-level relationship using existing sub-component schema element | tbc |