Change Naming of Charms in OSM
Proposers
- David Garcia (Canonical)
- Guillermo Calviño (Canonical)
- Gulsum Atici (Canonical)
- Mark Beierl (Canonical)
Description
OSM creates the juju models identified with the Network service ID. As the time being, it entitles the charm application with a combination of vnf-id, vdu_id, vdu_count and a random suffix. However, the current charm application naming is not descriptive enough to obtain the correct charm belonging to a certain VDU/KDU. This feature covers necessary changes to use new charm application naming structure. Hence, the relevant charm of VDU/KDU in the VNFD descriptor becomes clearly visible.
Demo or definition of done
The following tasks should be completed:
- Onboard new network services which includes NS level, VNF level and VDU level charms
- Check the "application" value in the list of nsrs["_admin"]["deployed"]["VCA"] whether they are matching the proposed naming structure within this feature.
NS level: <charm-name>-ns
Example: simple-ns
VNF level: <ee-name>-z<vnf-ordinal-scale-number>-<vnf-profile-id>-vnf
Example: vnf-policy-ee-z0-vnf1-vnf
VDU level: <ee-name>-z<ordinal-scale-number>-<vnf-profile-id>-<vdu-profile-id>-z<vdu-ordinal-scale-number>-vdu
Example: vnf-policy-ee-z0-vnf1-policyVM-z0-vdu-
Scale/heal the VNFs which belongs to NS which uses new application naming and check that scaled and healed VNFs uses the new application naming.
-
Scale/heal the VNFs which belongs to NS which uses old application naming and check that scaled and healed VNFs uses the old application naming.
This work is considered done when all the implementations, tests and documentation is contributed to use explicit charm application naming. Implementation Details