1. OPEN-O Sun Release Lab Deployment & Assembly

2. Agenda
OPEN-O Sun Release Deployment Options
OPEN-O Assembly & Distribution Directory Structure Suggestion

3. OPEN-O Deployment Option 1-Residential use case
Deploy one NFV-O for the Edge and other for the Core.
SDN-O can be deployed with the GS-O or as a separate system.
GS-O
NFV-O1
SDN-O
NFV-O2
VIM1
G-VNFM1
S-VNFM1
WAN controller
S-VNFM2
VIM2 OS
vNAT OS
vFW OS
vLB
pCPE
OLT
vCPE OS
vBRAS(CP)
SPTN
pBRAS(DP) GW
Residence
Building
TIC-Edge
Metro Core
TIC-Core

4. OPEN-O Deployment Option 1-Gaps
Catalog & Inventory should support multiple instances
Catalog & Inventory should support data synchronizing between GS-O an NFV-O systems
GS-O should login before it can access the NFV-O services
NFV-O or NFV-O might have their own GUI Portals
Note: SDN-O can be deployed with the GS-O or as a separated system.
GS-O
Internal API Gateway
External API Gateway ……
Catalog
Inventory
SDN-O
GS-O
Auth
Portal
NFV-O 1(2)
Internal API Gateway
External API Gateway ……
Catalog
Inventory
NFV-O
Auth
Portal

5. OPEN-O Deployment Option 2-Residential use case
Deploy OPEN-O as a whole, one NFVO to manage both the edge an the core cloud.
Recommend this option for release 1.
Internal API Gateway
External API Gateway ……
Catalog
Inventory
NFV-O
SDN-O
GS-O
Auth
Portal
VIM1
G-VNFM1
S-VNFM1
WAN controller
S-VNFM2
VIM2 OS
vNAT OS
vFW OS
vLB
pCPE
OLT
vCPE OS
vBRAS(CP)
SPTN
pBRAS(DP) GW
Residence
Building
TIC-Edge
Metro Core
TIC-Core

6. OPEN-O Deployment Option 2.1-Residential use case
Deploy OPEN-O as a whole, one NFVO to manage both the edge an the core cloud.
Recommend this option for release 1.
Internal API Gateway
External API Gateway ……
Catalog
Inventory
NFV-O
SDN-O
GS-O
Auth
Portal
VIM1
G-VNFM1
S-VNFM1
WAN controller
S-VNFM2
VIM2 DC
controller 1 DC
controller 2 OS
vNAT OS
vFW OS
vLB
pCPE
OLT
vCPE OS
vBRAS(CP)
SPTN
pBRAS(DP) GW
Residence
Building
TIC-Edge
Metro Core
TIC-Core

7. OPEN-O Deployment Option 2-Domain Tag
ESR adds a domain tag for the VNFM & VIM when registration (e.g., Edge, Core, PoP, Tenant Cloud).
GSO chooses a domain tag when decomposing the E2E NS based on policy(The policy might just be a user input on the portal right now).
GSO sends the NS creation request to NFVO along with the domain tag.
NFVO talks with ESR, ESR choose an appropriate VNFM/VIM according to the domain tag and return the chosen VNFM/VIM to NFVO.
NFVO sends the request to the VNFM/VIM.

8. OPEN-O Release Assembly
Service-name
- bin …
-initialize.sh
-run.sh
-stop.sh
-works
OPEN-O Release Assembly
Microservice Assemblies
Microservice Assemblies
OPEN-O Release Assembly
Deploy and Test
Sub-project Merge Job
OPEN-O Release Assembly Job
Integration Test Job
Source codes
Third-Party Libs
Maven POM for Microservices Assembly
Scripts
Maven pom for OPEN-O Release Assembly
Assembly sub-Project Git Repository
Test case
Microservice sub-Project Git Repository

9. Tool Infrastructure People will download VM from Nexus Server
Code / Unit Test
Repository
(Git/Gerrit)
System Test
Repository
(Git/Gerrit)
People will download VM from Nexus Server
Artifact
Repository
(Nexus)
Build / Unit Test
(Jenkins, Maven)
System Test
(Robot Framework)
Contribution Activity Reports
(Bitergia or Spectrometer)
API Documentation
(Swagger)
Unit Test
Code Coverage Reports
(SonarQube)
System / Performance Test Reports
(Robot, JMeter)
MSB API Portal

10. CI-Management (Jenkins)
Per Patch
Periodic (Daily)
Patch Submission
Patch Merge
All Projects Build From Source
Deploy to Nexus
Single Project Build /
Core Unit Tests
Single Project Build /
Core Unit Tests
All Unit Tests
All Projects Build From Artifacts
Check
Cross-Project Dependencies
Deploy to Swagger
Deploy to SonarQube
Project-Dependent System Tests
All System Tests

11. OPEN-O Distribution Directory Structure Suggestions
Each service has two sub-directories
bin : service binary, immutable
works : runtime configuration & temp files
Each service has there shell scripts in the bin directory
initialize.sh (Optional)
Intialize.sh are supposed to be run only once, if the service has specific dependency on the OS, it can use this script to set it up, for example, install some python packages.
run.sh (Mandatory) start the service
stop.sh (Mandatory) shutdown the service
There are there shell scripts in the root directory.
init.sh
traversal all the directories and call the initialize.sh of each service
startup.sh
traversal all the directories and call the run.sh of each service
shutdown.sh
traversal all the directories and call the stop.sh of each service
Note: Each service should has no dependency on the other services and can be started at a random order
openo-distribution
gso-lifecycle-nbi
bin …
initialize.sh
run.sh
stop.sh
works
gso-lifecycle-nbi-works
gso-portal
nfvo-dac
nfvo-umc
sdno-l2vpn ……
init.sh
shutdown.sh
startup.sh

12. Thank You