1. OPEN-O GS-O Planning Mercury Release
Jinxin / Brendan Hassett

2. Issues Faced During Sun Release
Issue Faced
Priority
Problem Statement
Dead Lock Issue of the Workflow Engine
High
Current Workflow Engine is single instance based and hence leads to an issue of the deadlock.
We got a temp fix done for the sun release in the tiger team activity.
Security issue with the GS-O GUI
Medium
The below are the security issues and gaps found in sun release:
Browser interaction with DB
A lot of decision making is happening in client.
Current portal has business logic implementation.
User privileges provision for future releases. Data validation for the input from CLIENT (GUI & CLI).
Unified Look and feel for the GUI Pages
Currently there is no standard followed by the UI pages from different partners of OPEN-O.
No information on the current status to the user
Low
There is no info on the progress on the current operation.
The User does not get any information if the operation is completed.
The reporter can be the assignee.

3. Requirement List of Mercury Release
Priority
Description
Accommodate more complex service lifecycles (e.g. activate, deactivate, scaling, update)
High
GS-O should prepare for the service lifecycle operation framework which is fit for more complex service lifecycle (e.g. activate, deactivate, scaling, update)for the further releases.
The below are the tasks we need to do:
Define the interface fields of the NS(network service) in the GS-O TOSCA template.
Have the capability of decompose the GS-O TOSCA template(Depends on the Parser component).
Generate the relationships of the NS.
According to the type of operation , select the workflow file, transmit the parameters ,start the workflow engine.
Enhance the Service Gateway micro service
We want the Service GW as the entry point for all the client requests.
So, we plan on moving the business login from portal to Service Gateway.
Thus reducing the security issues we pose currently in the code.
It depends on GS-O and CLIENT (both GUI and CLI) cooperation.
Improve retrieving the status of service from inventory
Medium
Add the status of service, it depends on capability of Holmes ,Policy ,Inventory, SDNO and NFVO Project.
The reporter can be the assignee.

4. Requirement List of Mercury Release
Priority
Description
Unified look and feel for the GUI Pages
Medium
Currently there is no standard followed by the UI pages from different partners of OPEN-O.
It is already proposed as UI project requirement in the mercury release.
Display the progress and status when execute the GS-O operations
User should be intimated of the current status of the operation.
So we need to provide more information as a percent progress bar.
It depends on GS-O and UI cooperation (This is already discussed and agreed).
Poll SDN-O and NFV-O for service execution result
Low
User needs an exact operation report to resolve the issue when the operation has failed. Currently user doesn’t know the detailed reasons except “Operation Failed” .It is not enough for user to correct the error.
So we need to improve this in mercury release.
Depends on in SDN-O and NFV-O response messaging.
Split SBI driver into SDN-O driver and NFV-O driver
In sun release, GS-O has only one south bound driver.
For better scalability, we need split it into different kinds of driver(SDN-O driver and NFV-O driver).
Internal to GS-O, no dependencies on other projects
The reporter can be the assignee.

5. Expected GS-O Activity Timeline
Mercury Release Timeline
Enhance the Service Gateway micro service
Expected GS-O Activity Timeline
Accommodate more complex service lifecycles
Integration
Phase
Jan 19, 2017
Feb 16, 2017
Display the operation progress and status
March 2, 2017
M 2
M 3
M 4 IP
Improve retrieving the status of service from inventory
Sun Bug fixes
Demo ready
Complex ,need design
Poll SDN-O and NFV-O for service execution result
Agreed upon (between GS-O and CLIENT alone in R2)
Split SBI driver into SDN-O driver and NFV-O driver
Mercury Release Bug fixes
Require discussion and cooperation with other sub-projects
Internal to GS-O

6. Feel Free to join OPEN-O GS-O Thanks