project-name
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
project-name [2014/12/01 05:40] 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 12: | Line 12: | ||
| The scope of the project is captured in the table shown below. As the table indicates all the features and functionality are part of the first release of the OPNFV. Nearly all these features have been tested and integrated within the OpenContrail, an open source platform under the Apache 2.0 license. Various POCs and pre-production version of the OpenContrail have been demonstrated in numerous lab and production systems. | The scope of the project is captured in the table shown below. As the table indicates all the features and functionality are part of the first release of the OPNFV. Nearly all these features have been tested and integrated within the OpenContrail, an open source platform under the Apache 2.0 license. Various POCs and pre-production version of the OpenContrail have been demonstrated in numerous lab and production systems. | ||
| - | ====== Table start ====== | + | ^ Technology Area ^ Technology Sub-area ^ Technology Proposed ^ |
| - | . | + | | **Virtual Infrastructure Orchestration** | Compute Orchestration | OpenStack, Juno or later | |
| - | . | + | | | Storage Orchestration | OpenStack, Juno or later - Ceph based distributed storage | = |
| - | . | + | | | Network Orchestration | OpenStack, Juno or later - OpenContrail SDN Controller | = |
| - | ====== Table end ====== | + | | **Server OS ** | | Ubuntu, Trusty | |
| + | | **Server Hypervisor ** | | KVM - Qemu | | ||
| + | | ** Virtual Network Device on Server ** | | OpenContrail - vRouter | | ||
| + | | ** 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 | | ||
| + | | |SDN Controller Availability | High Availability with Active-Active-Active mechanism | | ||
| + | |** Physical Infrastructure Design ** |Server-Network Connectivity| Reference Cluster Design with connectivity specification | | ||
| + | | |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 35: | Line 63: | ||
| * 3rd Party VNFs | * 3rd Party VNFs | ||
| - | Testability: ''(optional, Project Categories: Integration & Testing)'' | + | ====== Testability: ''(optional, Project Categories: Integration & Testing)'' ====== |
| Information regarding testing and integration including interoperability, scalability, high availability are provided in the above table. Any additional information for quality assurance and test resources will be available if necessary. | Information regarding testing and integration including interoperability, scalability, high availability are provided in the above table. Any additional information for quality assurance and test resources will be available if necessary. | ||
| - | Documentation: ''(optional, Project Categories: Documentation)'' | ||
| - | All API-related documents will be available in a timely manner. Detailed description of the Functional Architecture (building blocks, reference points, interfaces and protocols, work flow diagrams, etc.) will be provided during the development, integration and testing processes. | ||
| - | Dependencies: | + | ====== Documentation: ''(optional, Project Categories: Documentation)'' ====== |
| - | The OSCAR project relies on the following open source projects: | + | |
| - | o OpenStack Juno release: various components including Nova, Neutron, Ceilometer, Heat, etc., | + | |
| - | o OpenContrail: vRouter and other components, | + | |
| - | o Installer: Cobbler, | + | |
| - | o Configuration & Management: Puppet, | + | |
| - | o QEMU/KVM, | + | |
| - | o Linux/Ubuntu distribution. | + | |
| + | All API-related documents will be available in a timely manner. Detailed description of the Functional Architecture (building blocks, reference points, interfaces and protocols, work flow diagrams, etc.) will be provided during the development, integration and testing processes. | ||
| + | ====== Dependencies: ====== | ||
| + | The OSCAR project relies on the following open source projects: | ||
| + | * OpenStack Juno release: various components including Nova, Neutron, Ceilometer, Heat, etc., | ||
| + | * OpenContrail: vRouter and other components, | ||
| + | * Installer: Cobbler, | ||
| + | * Configuration & Management: Puppet, | ||
| + | * QEMU/KVM, | ||
| + | * Linux/Ubuntu distribution. | ||
| - | 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. |
| - | Planned deliverables | + | |
| + | ====== Planned Deliverables ====== | ||
| Project Oscar: | Project Oscar: | ||
| - | Installs scripts for automated deployment of the test setup to a bare metal environment, | + | * Installs scripts for automated deployment of the test setup to a bare metal environment, |
| - | Test scripts to allow for automated system level testing and component health check of all network functions, software components, etc in both virtual and physical environments, | + | * Test scripts to allow for automated system level testing and component health check of all network functions, software components, etc in both virtual and physical environments, |
| - | Heat-based orchestration template for delivered sample VNFs as well as other vendors’ VNFs. | + | * Heat-based orchestration template for delivered sample VNFs as well as other vendors’ VNFs. |
| - | Proposed Release Schedule: | + | |
| - | The first release is targeted for March 2015. | + | ====== Proposed Release Schedule: ====== |
| - | The project aligns with the current release cadence. | + | * The first release is targeted for March 2015. |
| + | * 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.1417412444.txt.gz · Last modified: 2014/12/01 05:40 by Parviz Yegani
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
