From 1652342a4ef2ff810332170c2fc40d36f4807f12 Mon Sep 17 00:00:00 2001 From: aticig Date: Thu, 25 Aug 2022 16:50:17 +0300 Subject: [PATCH] Feature 10944 Adding charm application naming details Signed-off-by: aticig --- 05-osm-usage.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/05-osm-usage.md b/05-osm-usage.md index 4bdba90..282f3bb 100644 --- a/05-osm-usage.md +++ b/05-osm-usage.md @@ -522,6 +522,20 @@ These charms can run with three scopes: - VNF: running globally for the VNF, for the management VDU that represents it. - NS: running for the whole NS, after VNFs have been configured, to handle interactions between them. +Depending on the scope of charms, the charm application naming differs: + +- **The VNF level** charm application name is prepared by combining the relevant execution environment name and vnf-profile-id. +- **The VDU level** charm application name includes vdu-profile-id as an identifier together with the relevant execution environment name and vnf-profile-id that it belongs. +- **The NS level** charm application name is identified with the charm name. + +The structure of charm application name makes the charm more apparent. Besides, it makes the VDU/KDU more visible by looking through the related charm. The structure of charm application names which are limited with 50 characters, are described below according to scope of charms: + +```bash +NS level: -ns +VNF level: -z--vnf +VDU level: -z---z-vdu +``` + For detailed instructions on how to add cloud-init or charms to your VNF, visit the following references: - [VNF Onboarding Guidelines, Day-0](https://osm.etsi.org/docs/vnf-onboarding-guidelines/02-day0.html) -- GitLab