User Tools

Site Tools


oscar:project_proposal

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
oscar:project_proposal [2015/01/09 17:23]
Stuart Mackie
oscar:project_proposal [2015/04/03 15:53] (current)
Stuart Mackie [Table]
Line 1: Line 1:
-====== Project: OSCAR ======+====== Project: ​System Configuration And Reporting (OSCAR======
  
   * //Proposed name for the project:// **OSCAR** (OPNFV System Configuration And Reporting)   * //Proposed name for the project:// **OSCAR** (OPNFV System Configuration And Reporting)
-  *            //Proposed name for the repository:// ​repo-oscar+  *            //Proposed name for the repository://​ oscar
   *            //Project Categories://​ Collaborative Development   *            //Project Categories://​ Collaborative Development
    
 ====== Project Description ====== ====== Project Description ======
-Project “OSCAR” provides a deployment platform for automatically installing and configuring the software components of OPNFV systems. ​ It is intended to be used by operators who are deploying OPNFV in integration labs and in production networks, and is intended to be part of, and integrated with, the OSS environment. The input to OSCAR will be the set of images and packages (with associated metadata) created by the Octopus CI environment as shown in the diagram below.+Project “OSCAR” provides a deployment platform for automatically installing and configuring the software components of OPNFV systems. ​ It is intended to be used by operators who are deploying OPNFV in integration labs and in production networks, and is intended to be part of, and integrated with, the OSS environment. The input to OSCAR will be the set of images and packages (with associated metadata) created by the Octopus CI environment ​(or other sources) ​as shown in the diagram below.
  
-{{ :​oscar:​oscar_in_opnfv.png?​nolink |}}+{{ :​oscar:​oscar_in_opnfv ​v2.png?nolink |}}
  
 A primary goal of OSCAR is to support the installation of a variety of OPNFV software stacks that are based upon on different underlying components, since each operator may have their own preferences based on their own unique business and technical requirements. These variations could, for example, leverage different SDN controllers or approaches to compute infrastructure (e.g. hypervisor vs container). A primary goal of OSCAR is to support the installation of a variety of OPNFV software stacks that are based upon on different underlying components, since each operator may have their own preferences based on their own unique business and technical requirements. These variations could, for example, leverage different SDN controllers or approaches to compute infrastructure (e.g. hypervisor vs container).
Line 16: Line 16:
 In Release 1 of OSCAR, it is proposed to support two OPNFV stacks, in order to demonstrate operation with multiple stacks. The stacks are described in the following table: In Release 1 of OSCAR, it is proposed to support two OPNFV stacks, in order to demonstrate operation with multiple stacks. The stacks are described in the following table:
  
-      ​OPNFV Component ​             ^Stack1 ​                 ^Stack2 ​             + OPNFV Component ​                     ^ Stack1 ​                 ^ Stack2 ​               
-|Virtual Infrastructure Manager (VIM)|OpenStack (Juno) ​       |OpenStack (Juno) ​   +| Virtual Infrastructure Manager (VIM)  | OpenStack (Juno) ​       | OpenStack (Juno) ​     
-|Network Controller ​                 |OpenDaylight ​           |OpenContrail ​       +| Network Controller ​                   | OpenDaylight ​           | OpenContrail ​         
-|Compute OS                          |Ubuntu, Debian, Fedora ​ |Centos, Ubuntu ​     +| Compute OS                            | Ubuntu, Debian, Fedora ​ | Centos, Ubuntu ​       
-|Virtualization ​                     |KVM/​QEMU ​               |KVM/QEMU, Docker ​   +| Virtualization ​                       | KVM/​QEMU ​               | KVM/QEMU, Docker ​     
-|Virtual Networking ​                 |Open vSwitch ​           |OpenContrail vRouter| +| Virtual Networking ​                   | Open vSwitch ​           | OpenContrail vRouter ​ 
-|Preloaded VNFs                      |As per BSG + TBD        |As per BSG + TBD    |+| Preloaded VNFs                        | As per BSG + TBD        | As per BSG + TBD      | 
 +| Installation and Orchestration ​       | TBD                     | TBD                   | 
 + 
  
  
Line 68: Line 71:
   * OpenDaylight:​ Open vSwitch and controller   * OpenDaylight:​ Open vSwitch and controller
   * OpenContrail:​ vRouter and controller   * OpenContrail:​ vRouter and controller
-  * Installer: Cobbler +  * Installer: ​Juju, Cobbler 
-  * Configuration & Management: Puppet+  * Configuration & Management: ​Juju, Puppet
   * Virtualization:​ QEMU/KVM   * Virtualization:​ QEMU/KVM
   * Containers: Docker   * Containers: Docker
   * OS: Linux Ubuntu/​Centos/​Debian/​Fedora distributions   * OS: Linux Ubuntu/​Centos/​Debian/​Fedora distributions
 +
 +===== Key Project Facts =====
 +
 +** Project Creation Date: ** \\
 +** Project Category: ** Integration & Testing\\
 +** Lifecycle State: ** \\
 +** Primary Contact: **  \\
 +** Project Lead: **  \\
 +** Jira Project Name: ** OPNFV System Configuration And Reporting \\
 +** Jira Project Prefix: ** OSCAR \\
 +** Mailing list tag ** [oscar] \\
 +
  
 ====== Committers: ====== ====== Committers: ======
Line 79: Line 94:
   * Peter Lee ([[plee@clearpathnet.com]]),​ CLEARPATH NETWORKS   * Peter Lee ([[plee@clearpathnet.com]]),​ CLEARPATH NETWORKS
   * Konstantin Babenko ([[kbabenko@ngnware.com]]),​ ngnWare   * Konstantin Babenko ([[kbabenko@ngnware.com]]),​ ngnWare
 +  * Prakash Ramchandran ([[prakash.ramchandran@huawei.com]]),​ Huawei 
 +  * Narinder Gupta ([[narinder.gupta@canonical.com]]),​ Canonical
 ====== Contributors:​ ====== ====== Contributors:​ ======
   * Parantap Lahiri ([[plahiri@juniper.net]]),​ JUNIPER NETWORKS   * Parantap Lahiri ([[plahiri@juniper.net]]),​ JUNIPER NETWORKS
Line 95: Line 111:
   * Konstantin Babenko ([[kbabenko@ngnware.com]]),​ ngnWare   * Konstantin Babenko ([[kbabenko@ngnware.com]]),​ ngnWare
   * Nabeel Asim ([[nasim@ngnware.com]]),​ ngnWare   * Nabeel Asim ([[nasim@ngnware.com]]),​ ngnWare
 +  * Ivan Zorrati ([[ivan.zorati@canonical.com]]),​ Canonical
 ====== Planned Deliverables ====== ====== Planned Deliverables ======
   * OSCAR configuration server package   * OSCAR configuration server package
Line 106: Line 122:
  
 ====== Proposed Release Schedule: ====== ====== Proposed Release Schedule: ======
-  * The first release is targeted ​for March 2015.+  * The first OSCAR release is targeted ​to align to OPNFV 2nd release. Interim downloads may be available ahead of formal release.
   * The project aligns with the current release cadence.   * The project aligns with the current release cadence.
oscar/project_proposal.1420824206.txt.gz · Last modified: 2015/01/09 17:23 by Stuart Mackie