Documentation housekeeping

doc/OpenSlice_deployment_examples.md

@@ -2,11 +2,11 @@
 
 Here are some examples from past and current efforts that use OpenSlice in various cases.
 
-## 5GinFIRE EU project(2018)
+## 5GinFIRE EU project (2018)
 
 * MultiVIM approach
 * 9 Testbeds
-* Automotive, Smart City, eHeath, PPDR, Media, SDR, Cloud
+* Automotive, Smart City, eHeath, PPDR, Media, SDR, Cloud
 * 22 Experiment proposals from Verticals
 * 100+ Users
 * VxF catalog: 
@@ -19,7 +19,7 @@ Here are some examples from past and current efforts that use OpenSlice in vario
   * 500+ Deployment requests (orchestrations) performed
 
 
-[![OpenSlice  usage](./images/deployment_example/Slide1.PNG)
+![OpenSlice  usage](./images/deployment_example/Slide1.PNG)
 
 ## 5G-VINNI  EU project (2020)
 
@@ -27,7 +27,7 @@ Here are some examples from past and current efforts that use OpenSlice in vario
 * 5G services on multiple sites
 * Introduction of TMFORUM models and APIs 
 
-[![OpenSlice  usage](./images/deployment_example/Slide2.PNG)
+![OpenSlice  usage](./images/deployment_example/Slide2.PNG)
 
 ## 5GASP  EU project (2021-2024)
 
@@ -36,14 +36,14 @@ Here are some examples from past and current efforts that use OpenSlice in vario
 * Introducing Service Test models
 * Introducing the Product models for a network application marketplace
 
-[![OpenSlice  usage](./images/deployment_example/Slide3.PNG)
+![OpenSlice  usage](./images/deployment_example/Slide3.PNG)
 
 ## FIDAL EU project (2023-)
 
 * Support multi-site automated testing
 * Multiple testbeds/ different APIs
 
-[![OpenSlice  usage](./images/deployment_example/Slide4.PNG)
+![OpenSlice  usage](./images/deployment_example/Slide4.PNG)
 
 ## ACROSS EU project (2023-)
 
@@ -52,13 +52,13 @@ Here are some examples from past and current efforts that use OpenSlice in vario
 * Support Zero-touch provisioning concepts
 
 
-[![OpenSlice  usage](./images/deployment_example/Slide5.PNG)
+![OpenSlice  usage](./images/deployment_example/Slide5.PNG)
 
 ## INCODE EU project (2023-)
 
 * Support the provisioning of end-to-end domain services
 
-[![OpenSlice  usage](./images/deployment_example/Slide6.PNG)
+![OpenSlice  usage](./images/deployment_example/Slide6.PNG)
 
 
 ## IMAGINEB5G EU project (2023-)
@@ -68,6 +68,7 @@ Here are some examples from past and current efforts that use OpenSlice in vario
 ## ETSI ZSM PoC #2
 
 * Automated Network Slice Scaling in Multi-Site Environments
+* [See more](https://zsmwiki.etsi.org/index.php?title=PoC_2_Automated_Network_Slice_Scaling_in_Multi-Site_Environments)
 
 
-[![OpenSlice  usage](./images/deployment_example/Slide7.PNG)
+![OpenSlice  usage](./images/deployment_example/Slide7.PNG)

doc/etsi_osl.md

-# The ETSi SDG OSL
+# The ETSI SDG OSL
 
-OpenSlice is developed by the OSL ETSI Software Development Group [see more info](https://osl.etsi.org/)
+OpenSlice is developed by the OSL ETSI Software Development Group [see more info](https://osl.etsi.org/).
\ No newline at end of file

doc/history.md

-## History
+# History
 
 * The NFV portal part of OpenSlice was initially developed in H2020 European Research project [5GinFIRE](https://5ginfire.eu) by University of Patras, Greece
 * OpenSlice core services, APIs was further developed and maintained in H2020 European project [5G-VINNI](https://5g-vinni.eu/) by University of Patras, Greece
@@ -11,7 +11,6 @@
 Please cite our [![paper]](https://arxiv.org/abs/2102.03290) if you use OpenSlice in your research
 
 ```
-
 @misc{tranoris2021openslice,
       title={Openslice: An opensource OSS for Delivering Network Slice as a Service}, 
       author={Christos Tranoris},
@@ -20,6 +19,4 @@ Please cite our [![paper]](https://arxiv.org/abs/2102.03290) if you use OpenSlic
       archivePrefix={arXiv},
       primaryClass={cs.NI}
 }
-
-
 ```
\ No newline at end of file

doc/index.md

@@ -70,17 +70,18 @@ There are various portals offering UI friendly access to users acting as Service
 
 Check a live demo of OpenSlice in the following pages:
 
-(username=admin, password=openslice <br> or <br>username=admin, password=changeme)
-
 * OpenSlice demo: <http://portal.openslice.io/>
 * OpenSlice Service Catalogs and ordering: <http://portal.openslice.io/services/>
 * OpenSlice NFV Services onboarding: <http://portal.openslice.io/nfvportal>
->
-> 
+
+Login credentials:
+
+* username=admin, password=openslice 
+* username=admin, password=changeme
 
 # Probe further
 
 * Installing OpenSlice. See the [Deployment](deployment.md) of OpenSlice
-* Learn more on [how OpenSlice supports Network as a Service(NaaS)](./naas/introduction
+* Learn more on [how OpenSlice supports Network as a Service(NaaS)](./naas/introduction)
 * Who is implementing OpenSlice? See [OSL ETSI SDG](https://osl.etsi.org/)
 * How OpenSlice works? See the [Architecture](./architecture/architecture.md) of OpenSlice

doc/naas/introduction.md

@@ -11,7 +11,7 @@ This section describes some core concepts for Delivering Network as a Service in
 In general Network as a Service (NaaS) is a  service model that allows users to consume network infrastructure and services , similar to how they would consume other cloud services like Software as a Service (SaaS) or Infrastructure as a Service (IaaS). NaaS abstracts the complexity of managing physical network infrastructure, providing users with virtualized network resources that can be dynamically allocated and managed through software.
 
 
-# OpenSlice and NaaS
+## OpenSlice and NaaS
 
 OpenSlice makes extensive use of TMFORUM's models and APIs. Therefore if one is familiar with TMF APIs the terminology and ideas are the same.
 

doc/naas/nfv/intro.md

+_This section is WIP._
\ No newline at end of file

doc/naas/nfv/nfvcatalogs.md

+_This section is WIP._
\ No newline at end of file

doc/naas/nfv/nfvservices.md

 # NFV Services 
 
-NFV Services are managed through a dedicate UI the NFV portal (eg http://portal.openslice.io/nfvportal)
+NFV Services are managed through a dedicated UI, i.e. the NFV portal (eg., [http://portal.openslice.io/nfvportal](http://portal.openslice.io/nfvportal)).
 
-Users are able through this portal to manage their NFV artifacts towards the NFVO, ( for example onboard VNFs and NSDs to a target OSM)
+Users are able through this portal to manage their NFV artifacts towards the NFVO (for example onboard VNFs and NSDs to a target OSM).
 
 
-Openslice NFV Services target to accommodate the following envisaged user roles. All users are assumed to be Authenticated:
+OpenSlice NFV Services target to accommodate the following envisaged user roles. All users are assumed to be Authenticated:
 
-* NFV developer: This role is responsible to upload VNF and NSD Descriptors in the Openslice services towards NFVO like OSM
-* Services administrator: This role represents the user that are responsible for maintenance of the Openslice services
+* NFV developer: This role is responsible to upload VNF and NSD Descriptors in the OpenSlice services towards NFVO, like OSM
+* Services administrator: This role represents the user that are responsible for maintenance of the OpenSlice services
 
-(obsolete: )
+(obsolete:)
 
 * Testbed provider: This role represents users that are responsible for testbed administration, configuration, integration, adaptation, support, etc
 * Experimenter: This role represents the user that will utilize our services and tools to deploy an experiment. That is the experiment description in terms of e.g.: NSD (Network Service Descriptor) or TOSCA Specification (in future versions)
@@ -21,12 +21,12 @@ Finally an anonymous user role exists who has some really simple usage scenarios
 
 During the onboarding process the following occurs:
 
-• A NFV developer submits a NFV archive (VNF or NSD) (he can later manage if needed some metadata)
-• The administrator can manage the NFV artifact (e.g. edit it)
-• The administrator On-Boards the NFV artifact to the target MANO
-• The administrator can optionally mark the NFV:
-o As public in order to be publicly visible by all portal users
-o As Certified which means this is certified by a certain entity
+- A NFV developer submits a NFV archive (VNF or NSD) (he can later manage if needed some metadata)
+- The administrator can manage the NFV artifact (e.g. edit it)
+- The administrator On-Boards the NFV artifact to the target MANO
+- The administrator can optionally mark the NFV:
+- As public in order to be publicly visible by all portal users
+- As Certified which means this is certified by a certain entity
 
 
 ## Request a new NSD deployment (this is different in comparison to Services)

doc/naas/resource_catalog.md

@@ -3,4 +3,6 @@
 #OpenSlice Resource Catalog:
 
     * Resource Specifications: Defines the underlying resources required to deliver services, such as network components, servers, and software.
-    * Resource Availability: Tracks the availability and status of resources to ensure efficient service delivery.
+    * Resource Availability: Tracks the availability and status of resources to ensure efficient service delivery.
\ No newline at end of file
+
+_This section is WIP._
\ No newline at end of file

doc/naas/resource_inventory.md

+_This section is WIP._
\ No newline at end of file

doc/naas/resource_spec.md

+_This section is WIP._
\ No newline at end of file

doc/naas/service_inventory.md

 # Service Inventory
 
-Service Inventory contains refences to running services that realize a Service Order
+Service Inventory contains references to running services that realize a Service Order.
 
 ## Intended Audience: Service Designers, OpenSlice administrators, Users
 
@@ -9,7 +9,7 @@ The Service Inventory is a repository that maintains detailed records of all act
 
 This inventory enables real-time visibility into the status, configuration, and dependencies of each service, facilitating effective management, troubleshooting, and optimization. 
 
-By providing a view of the active services, the Service Inventory includes services/resource allocation, and ensures that services are delivered in alignment with the inital requst. 
+By providing a view of the active services, the Service Inventory includes services/resource allocation, and ensures that services are delivered in alignment with the initial request. 
 
 
 ## UI management

doc/naas/so_intro.md

 # Service Orchestration
 
-- Service Orchestration: The orchestration engine evaluates the request, determines the necessary resources, and initiates the automated workflows.It interacts with underlying controller components (e.g. 5G Core, Radios, Containerized controllers, NFV, SDN controllers ) to provision and configure the required network functions and connectivity.
+Definition: The orchestration engine evaluates the request, determines the necessary resources, and initiates the automated workflows.It interacts with underlying controller components (e.g. 5G Core, Radios, Containerized controllers, NFV, SDN controllers) to provision and configure the required network functions and connectivity.
 
 ## Intended Audience: Service Designers
 
 OpenSlice end-to-end (E2E) service orchestration framework is designed to manage and automate the entire lifecycle of services across multiple domains and technologies. For delivering, Network as a Service (NaaS) OpenSlice automates and manages the entire lifecycle of network services, from provisioning to monitoring and decommissioning, while ensuring seamless integration, operation, and delivery of services from the initial request to the final delivery, spanning all involved components and layers.
 
-As next image depicts, service orchestrators follow some predefined workflows. OpenSlice end-to-end (E2E) service orchestrator follows some predefined workflows to manage a service lifecycle (They are described in BPMN language and included in our orchestration engine)
+As next image depicts, service orchestrators follow some predefined workflows. OpenSlice end-to-end (E2E) service orchestrator follows some predefined workflows to manage a service lifecycle (They are described in BPMN language and included in our orchestration engine).
 
 [![SO](./so/img01.png)](./so/img01.png)
 

doc/naas/so_servicespec_to_services_kubernetes.md

+_This section is WIP._
\ No newline at end of file

doc/portals_intro.md

 # OpenSlice Portals
 
-Openslice comprises of a web landing page [See Demo](http://portal.openslice.io/) that navigates to the respective Portal:
+OpenSlice comprises of a web landing page [(See Demo)](http://portal.openslice.io/) that navigates to the respective Portals:
 
-- Services Portal [See Demo](http://portal.openslice.io/services)
-- NFV Portal [See Demo](http://portal.openslice.io/nfvportal)
-- Products Portal [See Demo](http://portal.openslice.io/products)
-- Testing Portal [See Demo](http://portal.openslice.io/testing)
-- Resources Portal [See Demo](http://portal.openslice.io/resources)
+- Services Portal [(See Demo)](http://portal.openslice.io/services)
+- NFV Portal [(See Demo)](http://portal.openslice.io/nfvportal)
+- Products Portal [(See Demo)](http://portal.openslice.io/products)
+- Testing Portal [(See Demo)](http://portal.openslice.io/testing)
+- Resources Portal [(See Demo)](http://portal.openslice.io/resources)
 
 
-Following you may find the scope each portal focuses on and the main TMF APIs it supports.
+Following you may find the scope each portal focuses on and the main TMF APIs it supports:
 
 **Services Portal** is a designated portal for the:
 - Service Designer - To design Customer Facing Services as bundles of Resource Facing Services that map to specific Resourses (e.g. NFV, Testing, General Resources). Then, it is charged with the designed Services' exposure to public Service Catalogs.
@@ -44,4 +44,4 @@ More information can be found at [NFV Services](./naas/nfv/nfvservices.md).
 |**Testing Portal**   |        |x       |        |        |        |        |        |        |        |x       |        |
 |**Resources Portal** |        |x       |        |x       |        |x       |        |        |        |        |x       |
 
-The NFV Portal uses a proprietary API
+The NFV Portal uses a proprietary API.
\ No newline at end of file