update #9

doc/naas/lcm_intro.md

@@ -82,19 +82,23 @@ In this phase the Service Designer can define several aspects.  **Be aware that
 ### High level example: Enhanced Mobile Broadband (eMBB) Service Lifecycle
 
 1. **Preparation:**
+
    - Define eMBB service requirements for high bandwidth and low latency.
    - Create an eMBB service specification template specifying related services and resources to Kubernetes Operators, VNFs for content delivery and traffic management.
    - Expose to catalog
 
 2. **Instantiation:**
+
    - Instantiate other services and allocate resources such as edge computing nodes and high-capacity links.
    - Configure the service to prioritize video streaming traffic.
 
 3. **Operation:**
+
    - Monitor the service to ensure it meets high-bandwidth requirements.
    - Scale up resources during peak usage periods, such as live sports events.
 
 4. **Decommissioning:**
+
    - Notify users about service termination.
    - Decommission the network service, reclaiming resources for other services.
 

doc/naas/so_servicespec_to_services_nfv.md

+# From Service Specification to NFV based services
+
+After a Service Order completion, active services with their additional characteristics are found:
+
+* From the Order Items of a selected Service order
+* from the menu of Service inventory and then selecting details of each service
+* through the Service Inventory API (TMF 638 - Service Inventory Management ) 
+
+
+Openslice creates a Service for the requested CFS. Customers make Service Orders and Openslice instantiates the requested Service Specifications for each Service Order Item of a Service Order. Running Services instantiated by Openslice, reside in Openslice Service Inventory. The following picture displays how Service Specifications are related to Running Services and how Running Services relate with instantiated running Network Services. 
+
+
+[![Openslice  Service Specification instantiation](./so/service_specification_instantiation.png)](./so/service_specification_instantiation.png)
+
+
+There is a hierarchy of services. Usually an Instantiated CFS has Supporting Services some Instantiated RFSs. Then an Instantiated RFS is related to some running NS managed by NFVO
+
+
+## Interacting with an Active Service (Day 2 config)
+
+In some cases, if the underlying service is configured with actions (for example in OSM Day 2 primitive actions), there are characteristics that can be modified.  Usually they are named like : <servicename>::Primitive::<action>
+
+The user can edit the characteristic with a new value. The value is propagated through the OSOM and NFVO down to the related VNF.
+
+## Terminating/Inactivating a service
+
+You can terminate the service with one of the following processes:
+
+* Select the related Service Order and terminate the Order Item. This will delete all the underlying related active services. The Order goes to ACKNOWLEDGED->INPROGRESS->COMPLETE
+* To terminate or inactivate a service, select the specific service from the inventory, press Edit and set the State either to Inactive or Terminated
+
+<b>Warning: if you terminate or inactivate a service the action cannot be undone.</b>   
+
+
+## uml: sequence diagram
+Here I will embed PlantUML markup to generate a sequence diagram.
+
+I can include as many plantuml segments as I want in my Markdown, and the diagrams can be of any type supported by PlantUML.
+

doc/catalogs.md → doc/service_design/catalogs.md

@@ -96,35 +96,6 @@ Openslice offers the GST in a format that is machine readable and aligned with t
 Providers can clone a GST as e NEST directly in Openslice Web portal and the adjust the default attributes to their Service Specification
 
 
-### 5G-VINNI Service Blueprint
-(Offered only as a design for now. THere is no direct implementation to NFV)
-5G-VINNI Service Blueprint is a special Service Specification defined by teh 5G-VINNI project. Many details can be found in document <https://zenodo.org/record/3345612>
-
-5G-VINNI Service Blueprint is a reusable self-contained specification of required network slice service (instances). As described in GST mapping VINNI-SB is also machine readable. 
-
-Here is a tentative approach in JSON : <https://github.com/openslice/org.etsi.osl.tmf.api/tree/master/src/main/resources/vinnisb>
-
-5G-VINNI SB has many commonalities with GST as well as it offers Testing as a Service attributes.
-
- Next figure presents the high-level object model of a 5G-VINNI service blueprint.
- 
-The 5G-VINNI SB as a first prototype approach is conceived as a CFS of a ‘bundle’ of services. It has some characteristics, like name, description, service type (eMBB, etc) and others. The constituent services are:
-
-- A “Service Topology” Service Specification which is related to a Network Service Resource topology (a Logical Resource Spec). It is considered at this stage as an RFS but is subject to change in future
-- A “VINNI SB Service Requirements” Service Specification which is related to Service requirements. This is very similar to GST. It is considered at this stage a CFS.
-- A “VINNI SB Service Exposure Level 1” Service Specification which contains characteristics for service exposure on level 1 ( see D3.1 for details). It is considered at this stage a CFS.
-- A “VINNI SB Service Exposure Level 2” Service Specification which contains characteristics for service exposure on level 2. It is considered at this stage a CFS.
-- A “VINNI SB Service Exposure Level 3” Service Specification which contains characteristics for service exposure on level 3. It is considered at this stage a CFS.
-- A “VINNI SB Service Exposure Level 4” Service Specification which contains characteristics for service exposure on level 4. It is considered at this stage a CFS.
-- A “VINNI SB Service 3rd part VNF” Service Specification which contains characteristics for support 3rd party VNFs to be included in the service. It is considered at this stage as an RFS but is subject to change in future
-- A “VINNI SB Service 3rd part NSD” Service Specification which contains characteristics for support 3rd party NSDs to be included in the service. It is considered at this stage as an RFS but is subject to change in future
-- A “VINNI SB Service Monitoring” Service Specification which contains characteristics for offering Monitoring capabilities on the requested Service. It is considered at this stage a CFS.
-- A “VINNI SB Service Testing” Service Specification which contains characteristics for offering Testing capabilities on the requested Service. It is considered at this stage a CFS.
-
-
-[![VINNI SB Template Model diagram](../images/vinni_sb_model_diagram.png)](../images/vinni_sb_model_diagram.png)
-
-
 ## Manage a Service Specification
 
 You can manage them though the Web UI
@@ -142,6 +113,6 @@ Delete it from the category
 
 ## Consume and expose Service Specifications from other Service Catalogues 
 
-See more on [Consuming Services From External Partner Organizations](./architecture/consumingServicesFromExternalPartners.md)
+See more on [Consuming Services From External Partner Organizations]( ../architecture/consumingServicesFromExternalPartners.md )