User Tools

Site Tools


project-name

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
project-name [2014/12/01 06:48]
Parviz Yegani
project-name [2015/02/23 06:07] (current)
Iben Rodriguez added some section for questions
Line 1: Line 1:
-====== Project ​Name ====== +====== Project: OSCAR ======
- +
-             * Proposed name for the project: **OSCAR** (Open Source Carrier grade ARchitecture) +
-  *            Proposed name for the repository: repo-oscar +
-  *            Project Categories: (Integration & Testing, Collaborative Development)+
  
 +             * //Proposed name for the project:// **OSCAR** (Open Source Carrier grade ARchitecture)
 +  *            //Proposed name for the repository://​ repo-oscar
 +  *            //Project Categories://​ Integration & Testing, Collaborative Development
 + 
 ====== Project Description ====== ====== Project Description ======
 Project “OSCAR” provides a platform that can be used to assemble and test a base set of infrastructure components for the OPNFV. A few example VNFs will be provided to validate the integrity and the overall functionality of the OPNFV implementation platform. The goals of the Oscar Project is closely aligned with what the OPNFV technical steering committee (TSC) is envisioning for the first release. This is fast track the integration of the core open source network components, learn from their differences and commonality of deployment experience, and feed that back into producing a more flexible implementation framework. ​ Project “OSCAR” provides a platform that can be used to assemble and test a base set of infrastructure components for the OPNFV. A few example VNFs will be provided to validate the integrity and the overall functionality of the OPNFV implementation platform. The goals of the Oscar Project is closely aligned with what the OPNFV technical steering committee (TSC) is envisioning for the first release. This is fast track the integration of the core open source network components, learn from their differences and commonality of deployment experience, and feed that back into producing a more flexible implementation framework. ​
Line 21: Line 21:
 | ** Support for Physical Appliance/​Baremetal Server ** | | VTEP termination on ToR switch using OVSDB | | ** Support for Physical Appliance/​Baremetal Server ** | | VTEP termination on ToR switch using OVSDB |
 | ** Virtual Infrastructure Availability ** |Orchestration Controller Availability | High Availability with Active-Active-Active mechanism | | ** Virtual Infrastructure Availability ** |Orchestration Controller Availability | High Availability with Active-Active-Active mechanism |
 +| |SDN Controller Availability | High Availability with Active-Active-Active mechanism |
 |** Physical Infrastructure Design ** |Server-Network Connectivity| Reference Cluster Design with connectivity specification | |** Physical Infrastructure Design ** |Server-Network Connectivity| Reference Cluster Design with connectivity specification |
 | |Network Gateway | Network Gateway interface to Internet and L3VPN | | |Network Gateway | Network Gateway interface to Internet and L3VPN |
 +|** Physical Infrastructure Configuration/​Imaging ** |Server Imaging/​Configuration | Cobbler based imaging; Puppet based configuration |
 +| |Network Device Imaging/​Configuration| Netconf based device configuration management|
 +|** Service Orchestration ** |VNF Initiation | Heat Template based Virtual Network and Service Chain creation|
 +| |VNF Configuration | Individual EMS based VNF configuration|
 +|** Service Scaling ** |Horizontal Scaling of Service | API based horizontal scaling of services |
 +| |Vertical Scaling of Service | On-demand resource augmentation of VNF |
 +|** Traffic Steering ** |Traffic steering through transparent Services | API based creation of transparent (bump-in-the-wire) Service Chain between two networks|
 +| |Traffic steering through Services with L3 processing | API based creation of L3 processed Service Chain between two networks |
 +| |Traffic steering through multiple virtual services| API based creation of multiple virtualized services between two networks |
 +| |Traffic steering through virtual and physical services| API and Netconf based traffic steering through Virtualized and Physical Appliance |
 +|** User Interface ** |Creation of Service Chains | GUI or API based orchestration of Service Chains |
 +| |Operation and Management of Cluster | GUI or API based Operation and Management of Cluster |
 +| |CLI Interface | Standard CLI based Operations |
 +|** Operability ** |Infrastructure Resources Monitoring | CPU, Mem, NIC, vCPU, vMem, vNIC, Virtual Network Traffic, Environment Variables, events|
 +| |Service Monitoring | Service Status Monitoring |
 +| |Diagnostic | Endpoint reachability testing|
 +|** Data Collection & Analytics ** |Log Collection | Service Logs & Syslogs |
 +| |Flow Record | 1:1 flow record collection |
 +| |Packet Capture | API driven on-demand full packet capture of any flow |
 +| |Flow Path | Correlate overlay and underlay data to trace flow path |
 +
  
 ====== Targeted Test Cases ====== ====== Targeted Test Cases ======
Line 59: Line 81:
  
 ====== Committers and Contributors:​ ====== ====== Committers and Contributors:​ ======
-  * Parantap Lahiri (plahiri@juniper.net) +  * Parantap Lahiri ([[plahiri@juniper.net]]
-  * Parviz Yegani (pyegani@juniper.net) +  * Parviz Yegani ([[pyegani@juniper.net]]
-  * Raghavendra Mallya (rmallya@juniper.net) +  * Raghavendra Mallya ([[rmallya@juniper.net]]
-  * Kalyanjeet Gogoi (kjgogoi@juniper.net)+  * Kalyanjeet Gogoi ([[kjgogoi@juniper.net]])
   * More committers and contributors will be added later.   * More committers and contributors will be added later.
  
Line 75: Line 97:
   * The project aligns with the current release cadence.   * The project aligns with the current release cadence.
  
 +====== Questions ======
 +  - is this project approved by TSC already?
 +  - is there a lab where this project is being worked on?
 +  - if so is there public access to the lab?
 +  - is there any repo setup for the code and scripts being generated by this project?
 +  - can others outside juniper participate in this project?
project-name.1417416485.txt.gz · Last modified: 2014/12/01 06:48 by Parviz Yegani