Commit f50bffff authored by Kostis Trantzas's avatar Kostis Trantzas
Browse files

fix for #2

parent 82e5c05c
Loading
Loading
Loading
Loading
Loading
+1 −0
Original line number Diff line number Diff line
Docker Compose WIP
 No newline at end of file

doc/deploymentK8s.md

0 → 100644
+1 −0
Original line number Diff line number Diff line
Kubernetes WIP
 No newline at end of file
+7 −5
Original line number Diff line number Diff line
@@ -10,11 +10,13 @@ Configuration of your target(s) NFVOs/MANO services with Openslice is performed

3. Navigate to Admin > Manage MANO providers > Add New MANO Provider and enter its details:

* Name and description of your choice. The selected name will supplement the NFV artifacts of this provider.
* One of the already defined MANO platforms
* API URL Endpoint, eg: https://10.10.10.10:9999 (This is the SOL005 NBI endpoint - *Note the port 9999*)
* Username, Password and Project of your OSM tenant.
    - Name and description of your choice. The selected name will supplement the NFV artifacts of this provider.
    - One of the already defined MANO platformssynchronization
    - API URL Endpoint, eg: https://10.10.10.10:9999 (This is the SOL005 NBI endpoint - *Note the port 9999*)
    - Username, Password and Project of your OSM tenant.

Check EnabledForONBOARDING, if you want VNF/NS packages uploaded through the UI by the user, to also be automatically ONBOARDED to this MANO (1 step process). If left unchecked, the onboarding process must be performed manually after the VNF/NS package is uploaded to the portal, by the designated UI (2 step process).

Check EnabledForSYNC, if you want to support the automatic synchronization of this MANO with OpenSlice. When enabled, the existing VNF/NS packages and VIMs (and any updates on them) of the registered MANO are also reflected to the portal to the respective UIs (Registered VNFs/NSDs and Manage Infrastructures). The synchronization is a continuous process that will confirm that the artifacts are still present in the MANO, updating the status field of the respective artifacts to `OSM_PRESENT`. If during this process, an artifact is deleted from the MANO, the respective status field will be updated to `OSM_MISSING`.
 No newline at end of file
Check EnabledForSYNC, if you want to support the automatic synchronization of this MANO with OpenSlice. When enabled, the existing VNF/NS packages and VIMs (and any updates on them) of the registered MANO are also reflected to the portal to the respective UIs (Registered VNFs/NSDs and Manage Infrastructures). 

The synchronization is a continuous process that will confirm that the artifacts are still present in the MANO, updating the status field of the respective artifacts to `OSM_PRESENT`. If during this process, an artifact is deleted from the MANO, the respective status field will be updated to `OSM_MISSING`.
 No newline at end of file
+4 −1
Original line number Diff line number Diff line
@@ -72,7 +72,10 @@ nav:
  - Overview:
      - Introduction: index.md
  - Getting Started:
      - Deployment/Installation: deployment.md
      - Deployment/Installation: 
          - deployment.md
          - Docker Compose: deploymentCompose.md
          - Kubernetes: deploymentK8s.md
      - NFV Orchestrator Configuration: nfvoconfig.md
      - Service Catalogs: catalogs.md
      - NFV Catalogs: nfvcatalogs.md