diff --git a/doc/images/catalogs/execute_mano_primitives.png b/doc/images/catalogs/execute_mano_primitives.png new file mode 100644 index 0000000000000000000000000000000000000000..e8b6713dcad1b2ec1bdddcbcadfb3252558944c3 Binary files /dev/null and b/doc/images/catalogs/execute_mano_primitives.png differ diff --git a/doc/images/catalogs/mano_nslcm.png b/doc/images/catalogs/mano_nslcm.png new file mode 100644 index 0000000000000000000000000000000000000000..28f3e3ad5d8a92fca70462d989dad2e5924644af Binary files /dev/null and b/doc/images/catalogs/mano_nslcm.png differ diff --git a/doc/images/catalogs/mano_primitives_list.png b/doc/images/catalogs/mano_primitives_list.png new file mode 100644 index 0000000000000000000000000000000000000000..e93ef0ed468fab41472cca076a5737e121944f93 Binary files /dev/null and b/doc/images/catalogs/mano_primitives_list.png differ diff --git a/doc/service_design/catalogs.md b/doc/service_design/catalogs.md index ebaf24fc0d524ce6729038ae6dadfca2d02752c0..41fbe1ad54c15dfb0dc99e5b6a3da696d3458bd4 100644 --- a/doc/service_design/catalogs.md +++ b/doc/service_design/catalogs.md @@ -35,18 +35,40 @@ or a more complex example (beautify it first if you want to view it, but in the You can leave the Alias and Unit of Measure as is. Check also the is Default. +### OSM NS LCM Status +When a Service is deployed, OpenSlice provides the ability to see the status messages from the NFVO. This status can be regarding NS instantiation, primitive execution, etc. + +Going to `ResourceFacingService (RFS)` -> `Contextual Features` -> `MANO NSLCM`, you will be able to see a beautified view of the status messages retrieved by OSM. + +MANO NSLCM Section ### Day 2 Primitive Actions -NFVOs like OSM allow to perform actions while a service is running, for example change attributes or make actions on a specific VNF. To design this do something similar to the following example: +NFVOs like OSM allow to perform actions while a service is running, for example change attributes or make actions on a specific VNF. +OpenSlice supports the invocation of day 2 primitives using Open Source MANO (OSM). This feature allows users to perform various actions while a service is running, such as changing attributes or executing specific actions on a Network Service's (NSD) Virtual Network Function (VNF). This capability enhances the flexibility and control over network services, making it easier to manage them in real-time. + +#### Invoking Primitives in OpenSlice + +To design and invoke primitives in OpenSlice, do the following steps: + +1. When a service is instantiated, go to its `ResourceFacingService (RFS)` -> `Contextual Features` -> `MANO Primitives List`; + MANO Primitives List Section + +2. There, you will find that VNF available primitives; +3. Click on the `Execute Primitive` button of the chosen VNF; +4. On the `Execute MANO Primitives` window: + 1. Select the desired primitive on the `Primitive Parameter Name`; + 2. Provide the `Primitive Parameter Value`; + + Execute MANO Primitives Window + +5. Click on the `Submit` button. -- Go to the RFS related to the NSD that contains VNFs with primitives -- create a characteristic named Primitive:: , e.g. Primitive::touch -- select Value Type: ARRAY -- add Service Characteristic Value: i) alias=primitive, value= (e.g. touch), ii) alias=member_vnf_index, value= (e.g. 1), iii) add the params that the user will change in alias the name of param and in value an initial value (e.g. alias=filename, value=myfile.txt) +After the previous steps, after a while, you should be able to see the status of the primitive execution above on the same page, on the `MANO NSLCM` section. -In the above example, when the service is running and the user goes to service inventory to MODIFY it, changes the value of the alias=filename, value=myfile.txt, to value =secondfile.txt. Then inside the VNF a file will be created called secondfile.txt +> ***IMPORTANT NOTE:*** +As of now, OpenSlice still only supports the invoking of VNF-level primitives. We expect to have VDU-level primitives in the future.