====== Project: System Configuration And Reporting (OSCAR) ====== * //Proposed name for the project:// **OSCAR** (OPNFV System Configuration And Reporting) * //Proposed name for the repository:// oscar * //Project Categories:// Collaborative Development ====== 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 (or other sources) as shown in the diagram below. {{ :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). The OSCAR project is described in detail in this presentation: {{:oscar:oscar_overview_v8.pptx|}} 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 ^ | Virtual Infrastructure Manager (VIM) | OpenStack (Juno) | OpenStack (Juno) | | Network Controller | OpenDaylight | OpenContrail | | Compute OS | Ubuntu, Debian, Fedora | Centos, Ubuntu | | Virtualization | KVM/QEMU | KVM/QEMU, Docker | | Virtual Networking | Open vSwitch | OpenContrail vRouter | | Preloaded VNFs | As per BSG + TBD | As per BSG + TBD | | Installation and Orchestration | TBD | TBD | OSCAR will validate each installation once it is completed, and reports will be available to show the configuration and status of each installation under OSCAR’s control. Later releases of OSCAR will implement the OPNFV platform lifecycle for each installation under management, including component upgrades, scaling and site migration. Images and packages from Collaborative Development projects will be included in OPNFV stacks managed by OSCAR as they become released through Octopus. Additionally, it will be desirable to support configuration of network infrastructure to provide connectivity from physical networks to the virtual infrastructure supporting the VNFs. OSCAR will be based on a set of open source management tools, selected according to best-fit for specific tasks. Available tools include: Cobbler, Puppet, Chef, Ansible and several others. The overall workflow for deployment is likely to be based on TOSCA. Documentation will be provided to enable users to edit the components of an OPNFV stack or to create new stacks. This will include specification of component images and packages, scaling rules, high availability configurations, and health check metrics and methods. ====== Scope ====== The primary focus of OSCAR is managing pre-production and production deployments in operator labs and networks. The intent is to develop a system which provides “recipes” or templates that can be used to create OPNFV stacks whose configurations match desired levels of scalability and availability as required by individual operators and for each specific deployment. **Related Projects** * **Octopus** provides an environment in which OPNFV components (platform builds based upon various combinations of components from upstream projects) can be maintained in sync with the upstream projects, and built from those source components into a cohesive set of images and packages, with associated metadata, that form the input artifacts for test and deployment projects, e.g. OSCAR and the test/integration project (Pharos). Since OSCAR is itself an OPNFV component, it will ultimately have its own lifecycle within Octopus. * **Get-started** will provide a capability to quickly deploy a base configuration of components of OPNFV in order to support developer testing of OPNFV stacks and to aid Octopus CI development. OSCAR will use the BGS stack as one of its initially supported stacks in order to exercise the ability to deploy at scale and on multiple sites. * OSCAR will follow the release cadencing of the **Simultaneous Release** project, once it is in place. ====== Test Cases ====== OSCAR will provide automated tools for installation of various components as well as health check for individual components. Testing will include: **Release 1** * Deploy specified OPNFV stack onto designated bare metal or virtual servers (inc. preload VNF images and Heat templates) * Validate deployment * Report on configuration and status (health check) of specified deployments **Release 2+** * Life cycle management for OPNFV stack (scale, upgrade, migrate) * Management of preloaded VNFs * Test configuration of physical network for connectivity to VNFs * Edit stacks and create new stacks ====== Documentation ====== Documentation will be provided that describes the OSCAR architecture, components, supported stacks, installation procedure, user interface, APIs, and configuration files. ====== Dependencies: ====== The OSCAR project relies on the following open source projects: * OpenStack Juno release: various components including Nova, Neutron, Ceilometer, Heat, etc. * OpenDaylight: Open vSwitch and controller * OpenContrail: vRouter and controller * Installer: Juju, Cobbler * Configuration & Management: Juju, Puppet * Virtualization: QEMU/KVM * Containers: Docker * 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: ====== * Parviz Yegani ([[pyegani@juniper.net]]), JUNIPER NETWORKS * Stuart Mackie ([[wsmackie@juniper.net]]), JUNIPER NETWORKS * Peter Lee ([[plee@clearpathnet.com]]), CLEARPATH NETWORKS * Konstantin Babenko ([[kbabenko@ngnware.com]]), ngnWare * Prakash Ramchandran ([[prakash.ramchandran@huawei.com]]), Huawei * Narinder Gupta ([[narinder.gupta@canonical.com]]), Canonical ====== Contributors: ====== * Parantap Lahiri ([[plahiri@juniper.net]]), JUNIPER NETWORKS * Parviz Yegani ([[pyegani@juniper.net]]), JUNIPER NETWORKS * Raghavendra Mallya ([[rmallya@juniper.net]]), JUNIPER NETWORKS * Kalyanjeet Gogoi ([[kjgogoi@juniper.net]]), JUNIPER NETWORKS * Stuart Mackie ([[wsmackie@juniper.net]]), JUNIPER NETWORKS * Margaret Chiosi ([[mc3124@att.com]]), AT&T * BIN HU ([[bh526r@att.com]]), AT&T * Qiao Fu ([[fuqiao@chinamobile.com]]), China Mobile * Peter Lee ([[plee@clearpathnet.com]]), CLEARPATH NETWORKS * Mark Medina ([[mmedina@clearpathnet.com]]), CLEARPATH NETWORKS * Ravi Chunduru ([[rchunduru@clearpathnet.com]]), CLEARPATH NETWORKS * Sivaprasath Busa ([[sbusa@clearpathnet.com]]), CLEARPATH NETWORKS * Konstantin Babenko ([[kbabenko@ngnware.com]]), ngnWare * Nabeel Asim ([[nasim@ngnware.com]]), ngnWare * Ivan Zorrati ([[ivan.zorati@canonical.com]]), Canonical ====== Planned Deliverables ====== * OSCAR configuration server package * Installation procedure and scripts for OSCAR onto bare metal or virtual servers * Configuration files for supported OPNFV stacks * Images and packages for supported OPNFV stacks * Inventory and system configuration reports for deployed OPNFV stacks * Documentation describing how to support OPNFV stack lifecycle, and how to configure OSCAR to support new solution components and VNFs ====== Proposed Release Schedule: ====== * 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.