OPEN-O GS-O Planning Mercury Release

Slides:



Advertisements
Similar presentations
ECHO Test Track Pro User’s Guide
Advertisements

Lectures on File Management
TDPS Wireless v Enhancements E1 - Multi load E2 - Driver time scheduler.
Software Engineering CSE470: Process 15 Software Engineering Phases Definition: What? Development: How? Maintenance: Managing change Umbrella Activities:
The Developer Perspective Michelle Osmond. Design – Requirements Gathering Sales & Research projects –Prototypes/Demos User group meetings Usability workshops.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Project Execution & Termination Life Cycle Execution Presented by: Basker George.
CVSQL 2 The Design. System Overview System Components CVSQL Server –Three network interfaces –Modular data source provider framework –Decoupled SQL parsing.
Client/Server Architectures
CSCI ClearQuest 1 Rational ClearQuest Michel Izygon - Jim Helm.
Dillon: CSE470: SE, Process1 Software Engineering Phases l Definition: What? l Development: How? l Maintenance: Managing change l Umbrella Activities:
Software Testing Life Cycle
Lecture 7 Interaction. Topics Implementing data flows An internet solution Transactions in MySQL 4-tier systems – business rule/presentation separation.
Eric Westfall – Indiana University Jeremy Hanson – Iowa State University Building Applications with the KNS.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Software Life Cycle Requirements and problem analysis. –What exactly is this system supposed to do? Design –How will the system solve the problem? Coding.
ISYS 562 Microcomputer Business Applications David Chao.
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
Accomplishments: Implementation Login form Dictionary Inputs Calculations(Partially Completed) Output(Partially Completed) Made a test database.
JavaServer Faces: Sample App + Life Cycle Compiled from Sun TechDays workshops (JSF Basics, Web-Tier Codecamp: JavaServer Faces, Java Studio Creator)
© ABB Group November 12, 2015 | Slide 1 ICV Implementation in Region ERP- Status update March 2011 & Plan for Go-Live REMSC, 2011.
T Iteration Demo Team 13 I1 Iteration
Workforce Scheduling Release 5.0 for Windows Implementation Overview OWS Development Team.
Worldwide Protein Data Bank Common D&A Project Sequence Processing Modular Demo May 6, 2010 Project Deliverable.
Web-based Front End for Kraken Jing Ai Jingfei Kong Yinghua Hu.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
EGI-InSPIRE RI EGI-InSPIRE EGI-InSPIRE RI Requirements Status EGI.eu UCB
/16 Final Project Report By Facializer Team Final Project Report Eagle, Leo, Bessie, Five, Evan Dan, Kyle, Ben, Caleb.
 Project Team: Suzana Vaserman David Fleish Moran Zafir Tzvika Stein  Academic adviser: Dr. Mayer Goldberg  Technical adviser: Mr. Guy Wiener.
Version 0.6 Draft – For Review Huabing Zhao
OPEN-O Approach 1, 2, 3 and 1.5 Discussion in Beijing.
Open-O GS-O Project Proposal
SDN-O LCM for Mercury Release Key Points and Overview
Open-O SFC.Mgr Proposal
Microservice Powered Orchestration
Architecture Review 10/11/2004
OPEN-O VNF-SDK Planning Release 2
Avoiding Redundancy in the Management of Technical Documentation and Models: Requirements Analysis and Prototypical Implementation for Enterprise Architecture.
Bringing Dynamism to OPNFV
Open-O Client Project Proposal
OPEN-O CLIENT Planning Mercury Release
Orchestration and Controller Alignment for ONAP Release 1
Introduction to .NET Florin Olariu
Open-O Client Project Proposal
OPEN-O Project Proposal Training
Component and Deployment Diagrams
OPEN-O Sun Release Lab Deployment & Assembly
A&AI Component Diagram
OPEN-O Multiple VIM Driver Project Use Cases
OPEN-O Modeling Directions (DRAFT 0)
ONAP SDC TOSCA Import Gap Analysis
NFV Updates Deepanshu Gautam.
Open-O CLI One Command to command whole Open-O v1.0
Wizard Templates.
T Project Review Group: pdm I2 Iteration
ONAP Run-time Catalog Project
Open-O Client Project Proposal
Agenda Where we are (Amsterdam Architecture)
Setting Up and Supporting Clients Using Employee Development in ADP Workforce Now [Developer: Use this slide if you are not using audio. You can add.
Top Reasons to Choose Angular. Angular is well known for developing robust and adaptable Single Page Applications (SPA). The Application structure is.
Documenting ONAP components (functional)
Engineering Processes
Data, Databases, and DBMSs
Software Engineering Lecture #14.
Design Components are Code Components
Exploring the Power of EPDM Tasks Working with and Developing Tasks in SolidWorks Enterprise PDM (EPDM) By: Marc Young xLM Solutions
SOFTWARE DEVELOPMENT LIFE CYCLE
Framework Anil
Presentation transcript:

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

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.

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.

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.

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

Feel Free to join OPEN-O GS-O Thanks