get_started:get_started_project_proposal
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
get_started:get_started_project_proposal [2014/12/08 17:27] Frank Brockners |
get_started:get_started_project_proposal [2015/09/11 17:05] (current) Ashlee Young [Committers and Contributors] |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| * //Proposed name for the project:// Bootstrap/Get-started (BGS) | * //Proposed name for the project:// Bootstrap/Get-started (BGS) | ||
| - | * //Proposed name for the repository:// bootstrap | + | * //Proposed name for the repository:// genesis |
| * //Project Categories:// Integration & Testing | * //Project Categories:// Integration & Testing | ||
| ==== Project description ==== | ==== Project description ==== | ||
| - | Project “Bootstrap/Get started” assembles and tests a base set of infrastructure components for OPNFV to run a few example VNFs. It puts together a single deployment type that can both be used by developers and run in continuous integration. The goals of the GetStarted Project is to stand up quickly one or more stacks of components, learn from their differences and commonality of deployment experience, and feed that back into producing a more flexible framework. Initially the project will focus on a single combination of components. The project will be complete, and hand off to the wider scope “Octopus” project, when CI demonstrably runs and the project can be seen to perform the tasks required of a basic VIM layer. | + | Project “Bootstrap/Get started” assembles and tests a base set of infrastructure components for OPNFV to run a few example VNFs like LBs, FWs. It puts together a single deployment type that can both be used by developers and run in continuous integration. The goals of the GetStarted Project is to stand up quickly one or more stacks of components, learn from their differences and commonality of deployment experience, and feed that back into producing a more flexible framework. Initially the project will focus on a single combination of components. The project will be complete, and hand off to the wider scope “Octopus” project, when CI demonstrably runs and the project can be seen to perform the tasks required of a basic VIM layer. |
| - | The project targets an installation on a virtual environment based on Linux/Centos 7 as base operating system and distribution. “Bootstrap/Get started” provides a solution to automatically install and configure the required components using existing installer and configuration tools and perform a set of basic system level tests (i.e. test whether OpenStack, OpenDaylight, OVS components are operational, tests whether a set of VNFs can be deployed/removed on the Compute Node). The project is intended to serve as both an initial development framework and a framework for CI. We feel it is important that developers work on realistic deployments rather than have separate development-centric deployments (‘it works on devstack’) and future projects will work on development tooling. | + | The project targets an installation on a virtual environment based on Linux Ubuntu 14.04/Centos 7 as base operating system and distribution. “Bootstrap/Get started” provides a solution to automatically install and configure the required components using existing installer and configuration tools and perform a set of basic system level tests (i.e. test whether OpenStack, OpenDaylight/SDN Controler, OVS components are operational, tests whether a set of VNFs can be deployed/removed on the Compute Node). The project is intended to serve as both an initial development framework and a framework for CI. It is important that developers work on realistic deployments which (‘works on devstack &/or packstack" as Compute Node VNFs) and future projects will work on development tooling. |
| The picture outlines the main setup of “bootstrap/get started”. | The picture outlines the main setup of “bootstrap/get started”. | ||
| Line 23: | Line 23: | ||
| * running OpenStack | * running OpenStack | ||
| * with a standard, lightly tuned configuration that suits NFV applications | * with a standard, lightly tuned configuration that suits NFV applications | ||
| - | * On Linux/Centos 7 | + | * On Linux Centos 7 |
| * with redundant control nodes (Openstack HA) | * with redundant control nodes (Openstack HA) | ||
| - | * running OpenDaylight Controller (ODL) | + | * running OpenDaylight Controller (ODL) / SDN Controller |
| * one or more compute nodes | * one or more compute nodes | ||
| * hosting a set of example VNFs to allow for system level testing of the infrastructure | * hosting a set of example VNFs to allow for system level testing of the infrastructure | ||
| * with deployment to VMs for on-laptop testing | * with deployment to VMs for on-laptop testing | ||
| * with deployment to bare metal for physical environment testing | * with deployment to bare metal for physical environment testing | ||
| - | * with a set of integration tests to demonstrate correct OpenStack/ODL base operation | + | * with a set of integration tests to demonstrate correct OpenStack/ODL/SDN Controller base operation |
| - | * with a set of system tests to demonstrate correct operation of the smple VNFs | + | * with a set of system tests to demonstrate correct operation of the sample VNFs like LBs, FWs |
| * designed for easy substitution of components | * designed for easy substitution of components | ||
| * using KVM as hypervisor | * using KVM as hypervisor | ||
| Line 50: | Line 50: | ||
| Targeted test cases (automated via Robot/Jenkins): | Targeted test cases (automated via Robot/Jenkins): | ||
| - | * Automated test of installation completeness and component health check: Ensure that all required components are installed and are healthy (OpenStack, OpenDaylight Controller, OVS, Example VNFs (OpenWRT, Snort, End-system/host VMs). This includes: | + | * Automated test of installation completeness and component health check: Ensure that all required components are installed and are healthy (OpenStack, OpenDaylight Controller/SDN Controller, OVS, Example VNFs (OpenWRT, Snort, End-system/host VMs). This includes: |
| * OpenStack health check (Verify Nova, Neutron, Keystone, Horizon, MySQL, Rabbit MQ, etc.. services are up and running) | * OpenStack health check (Verify Nova, Neutron, Keystone, Horizon, MySQL, Rabbit MQ, etc.. services are up and running) | ||
| - | * OpenDaylight health check (Verify MDSAL, RESTCONF, OVSDB, SFC, etc. services are up and running) | + | * OpenDaylight/SDN Controller health check (Verify MDSAL, RESTCONF, OVSDB, SFC, etc. services are up and running) |
| * Automated system-level testing: bring up / tear down multiple instances of VNFs (OpenWRT, Snort), check idempotent system behavior. | * Automated system-level testing: bring up / tear down multiple instances of VNFs (OpenWRT, Snort), check idempotent system behavior. | ||
| * Automated system service-level testing (bonus effort - in case there is time available): Bring up instances of OpenWRT and Snort, configure a service chain, test whether the service chain is functioning (e.g. two hosts can communicate via the service chain - and the configured packet processing behavior is in place). | * Automated system service-level testing (bonus effort - in case there is time available): Bring up instances of OpenWRT and Snort, configure a service chain, test whether the service chain is functioning (e.g. two hosts can communicate via the service chain - and the configured packet processing behavior is in place). | ||
| Line 67: | Line 67: | ||
| * OpenWRT (as example VNF - for routing, firewall, NAT) | * OpenWRT (as example VNF - for routing, firewall, NAT) | ||
| * Snort (as example VNF - for IDS) | * Snort (as example VNF - for IDS) | ||
| - | * Linux/Centos 7 distribution | + | * Linux Centos 7 distribution |
| ==== Committers and Contributors ==== | ==== Committers and Contributors ==== | ||
| Line 79: | Line 79: | ||
| * M R (Chengappa cm-r@hp.com) | * M R (Chengappa cm-r@hp.com) | ||
| * Palani Chinnakannan (pals@cisco.com) | * Palani Chinnakannan (pals@cisco.com) | ||
| + | * Peter Hladky (peter.hladky@pantheon.sk) | ||
| * Reinaldo Penno (rapenno@gmail.com) | * Reinaldo Penno (rapenno@gmail.com) | ||
| * Stefan Berg K (stefan.k.berg@ericsson.com) | * Stefan Berg K (stefan.k.berg@ericsson.com) | ||
| - | * Prakash Ramchandran (p.ramchandran@huawei.com) | + | * Prakash Ramchandran (prakash.ramchandran@huawei.com) |
| * Wes Hayutin (whayutin@redhat.com) | * Wes Hayutin (whayutin@redhat.com) | ||
| * Xiong Zhang (zhangxiong7@huawei.com ) | * Xiong Zhang (zhangxiong7@huawei.com ) | ||
| Line 98: | Line 99: | ||
| * Markus Berglund (markus.berglund@nsn.com) | * Markus Berglund (markus.berglund@nsn.com) | ||
| * Palani Chinnakannan (pals@cisco.com) | * Palani Chinnakannan (pals@cisco.com) | ||
| - | * Paul Quinn (paulq@cisco.com) | + | * Paul Quinn (paulq@cisco.com) |
| - | * Prakash Ramchandran (p.ramchandran@huawei.com) | + | * Peter Hladky (peter.hladky@pantheon.sk) |
| + | * Ashlee Young (ashlee@onosfw.com) | ||
| * Qiqi Hu (huqiqi@huawei.com) | * Qiqi Hu (huqiqi@huawei.com) | ||
| * Reinaldo Penno (rapenno@gmail.com) | * Reinaldo Penno (rapenno@gmail.com) | ||
| Line 111: | Line 113: | ||
| * Dongren Zhao (zhaodongren@huawei.com ) | * Dongren Zhao (zhaodongren@huawei.com ) | ||
| * Yu Zhang (zhangyu11@huawei.com ) | * Yu Zhang (zhangyu11@huawei.com ) | ||
| + | * Julien (zhang.jun3g@zte.com.cn) | ||
| + | * Jiang zhifeng(jiang.zhifeng@zte.com.cn) | ||
| + | * Vagish Shanmukh (vagishs@gmail.com) | ||
| ==== Planned deliverables ==== | ==== Planned deliverables ==== | ||
| Project deliverables: | Project deliverables: | ||
| * “Bootstrap/Get started” install scripts for automated deployment of the test setup to a virtual environment and bare metal environment | * “Bootstrap/Get started” install scripts for automated deployment of the test setup to a virtual environment and bare metal environment | ||
| - | * Test scripts to allow for automated system level testing (Component health check (OpenStack, OVS, OpenDaylight, lifecycle manage VNFs, create services using example VNFs). | + | * Test scripts to allow for automated system level testing (Component health check (OpenStack, OVS, OpenDaylight / SDN Controller, lifecycle manage VNFs, create services using example VNFs). |
| * Comprehensive source-to-tested-deployment script for running the entire system start to end for either use in development (deployed system is interesting), performance testing (performance results are interesting) or CI (test passes and failures are interesting). | * Comprehensive source-to-tested-deployment script for running the entire system start to end for either use in development (deployed system is interesting), performance testing (performance results are interesting) or CI (test passes and failures are interesting). | ||
get_started/get_started_project_proposal.1418059629.txt.gz · Last modified: 2014/12/08 17:27 by Frank Brockners
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
