This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
get_started:get_started_work_items [2014/11/28 08:11] Frank Brockners [System performance benchmark and scale numbers] |
get_started:get_started_work_items [2015/01/16 18:39] Joseph Gasparakis |
||
---|---|---|---|
Line 1: | Line 1: | ||
======= Bootstrap/Get started - Candidate work items ======= | ======= Bootstrap/Get started - Candidate work items ======= | ||
+ | |||
+ | ===== Task management ===== | ||
+ | |||
+ | Complementary to this wiki, we'll use [[https://etherpad.opnfv.org/p/bgs]] to track activity. | ||
+ | |||
===== System definition ===== | ===== System definition ===== | ||
Line 18: | Line 23: | ||
* Tempest, Rally (for testing) | * Tempest, Rally (for testing) | ||
* //OpenDaylight Helium Release// | * //OpenDaylight Helium Release// | ||
- | * MDSAL, Clustering, Restconf, OVSDB, OpenFlow, SFC, GBP, ML2-plugin, Netconf | + | * MDSAL, Clustering, Restconf, OVSDB, OpenFlow, SFC, GBP, ML2-plugin, Netconf (Details see table below) |
* //Hypervisor:// | * //Hypervisor:// | ||
* KVM, QEMU | * KVM, QEMU | ||
Line 32: | Line 37: | ||
* Robot | * Robot | ||
* Jenkins | * Jenkins | ||
+ | |||
+ | // Baseline for OpenDaylight components //: | ||
+ | |||
+ | ^ Name ^ Version ^ Repository ^ Description ^ | ||
+ | |odl-dlux-all | 0.1.1-Helium-SR1.1 | odl-dlux-0.1.1-Helium-SR1.1 | | | ||
+ | |odl-config-persister-all | 0.2.6-Helium-SR1.1 | odl-config-persister-0.2.6-Helium-SR1.1 | OpenDaylight :: Config Persister:: All | | ||
+ | |odl-aaa-all | 0.1.1-Helium-SR1.1 | odl-aaa-0.1.1-Helium-SR1.1 | OpenDaylight :: AAA :: Authentication :: All Featu | | ||
+ | |odl-ovsdb-all | 1.0.1-Helium-SR1.1 | ovsdb-1.0.1-Helium-SR1.1 | OpenDaylight :: OVSDB :: all | | ||
+ | |odl-ttp-all | 0.0.2-Helium-SR1.1 | odl-ttp-0.0.2-Helium-SR1.1 | OpenDaylight :: ttp :: All| | ||
+ | |odl-openflowplugin-all | 0.0.4-Helium-SR1.1 | openflowplugin-0.0.4-Helium-SR1.1 | OpenDaylight :: Openflow Plugin :: All| | ||
+ | |odl-adsal-compatibility-all | 1.4.3-Helium-SR1.1 | odl-adsal-compatibility-0.8.2-Helium-SR1.1 | OpenDaylight :: controller :: All| | ||
+ | |odl-tcpmd5-all | 1.0.1-Helium-SR1.1 | odl-tcpmd5-1.0.1-Helium-SR1.1 | | ||
+ | |odl-adsal-all | 0.8.2-Helium-SR1.1 | adsal-0.8.2-Helium-SR1.1 | OpenDaylight AD-SAL All Features| | ||
+ | |odl-config-all | 0.2.6-Helium-SR1.1 | odl-config-0.2.6-Helium-SR1.1 | OpenDaylight :: Config :: All| | ||
+ | |odl-netconf-all | 0.2.6-Helium-SR1.1 | odl-netconf-0.2.6-Helium-SR1.1 | OpenDaylight :: Netconf :: All| | ||
+ | |odl-base-all | 1.4.3-Helium-SR1.1 | odl-base-1.4.3-Helium-SR1.1 | OpenDaylight Controller| | ||
+ | |odl-mdsal-all | 1.1.1-Helium-SR1.1 | odl-mdsal-1.1.1-Helium-SR1.1 | OpenDaylight :: MDSAL :: All| | ||
+ | |odl-yangtools-all | 0.6.3-Helium-SR1.1 | odl-yangtools-0.6.3-Helium-SR1.1 | OpenDaylight Yangtools All| | ||
+ | |odl-restconf-all | 1.1.1-Helium-SR1.1 | odl-controller-1.1.1-Helium-SR1.1 | OpenDaylight :: Restconf :: All| | ||
+ | |odl-integration-compatible-with-all | 0.2.1-Helium-SR1.1 | odl-integration-0.2.1-Helium-SR1.1 | | ||
+ | |odl-netconf-connector-all | 1.1.1-Helium-SR1.1 | odl-controller-1.1.1-Helium-SR1.1 | OpenDaylight :: Netconf Connector :: All| | ||
+ | |odl-akka-all | 1.4.3-Helium-SR1.1 | odl-controller-1.4.3-Helium-SR1.1 | OpenDaylight :: Akka :: All| | ||
+ | |||
+ | |||
---- | ---- | ||
===== Use cases for system level test (initial focus) ===== | ===== Use cases for system level test (initial focus) ===== | ||
+ | |||
+ | The following set of use-cases will guide the testing performed as part of Bootstrap/Get-started. The project does not intent to provide a comprehensive coverage of the particular use-cases and all associated testing scenarios. We just need a few VNFs that we can run on the environment Bootstrap/Get-started provides. Having a few example VNFs (rather than only one) is to ensure that test scenarios are kept generic wherever possible. Use-case specific test projects are expected to provide proper and full coverage for specific use-cases. | ||
^ Use-Case ^ Description ^ Interested contributors ^ | ^ Use-Case ^ Description ^ Interested contributors ^ | ||
- | | Simple VNF: vRouter | Bring up one or multiple instances of a simple virtual router. OpenWRT will be used as virtual router. | | | + | | Simple VNF: vRouter | Bring up one or multiple instances of a simple virtual router. OpenWRT will be used as virtual router. | Joseph Gasparakis | |
- | | Simple VNF: vIDS | Bring up one or multiple instances of a service appliance. Snort/IDS will be used as service appliance. | | | + | | Simple VNF: vIDS | Bring up one or multiple instances of a service appliance. Snort/IDS will be used as service appliance. | Joseph Gasparakis | |
| SFC | Service chaining using open source components: Firewall and IDS (OpenWRT as simple firewall, Snort as IDS) | | | | SFC | Service chaining using open source components: Firewall and IDS (OpenWRT as simple firewall, Snort as IDS) | | | ||
Line 46: | Line 77: | ||
===== Candidate work items ===== | ===== Candidate work items ===== | ||
+ | This section lists tasks and test cases which Bootstrap/Get-started aspires to perform. It is expected that the scenario tests fold into more specific test projects (e.g. for system level functionality testing, specific VNF use-case tests, performance tests etc.) - which are in the process of being defined. | ||
==== System setup ==== | ==== System setup ==== | ||
Line 57: | Line 89: | ||
^ Test/Task ^ Description ^ Interested contributors ^ | ^ Test/Task ^ Description ^ Interested contributors ^ | ||
- | | Components function test: OpenStack | Ensure OpenStack components are installed correctly and functioning. Leverage [[http://docs.openstack.org/developer/tempest/index.html|OpenStack Tempest]] and [[https://wiki.openstack.org/wiki/Rally|OpenStack Rally]]. Includes smoke, baremetal, compute, data_processing, identity, image, network, object_storage, orchestration, telemetry, and volume testing. See [[http://logs.openstack.org/78/134978/1/check/check-tempest-dsvm-neutron-full/7ebce20/logs/testr_results.html.gz|example]] for the result of a tempest run. | | | + | | Components function test: OpenStack | Ensure OpenStack components are installed correctly and functioning. Leverage [[http://docs.openstack.org/developer/tempest/index.html|OpenStack Tempest]] and [[https://wiki.openstack.org/wiki/Rally|OpenStack Rally]]. Includes smoke, baremetal, compute, data_processing, identity, image, network, object_storage, orchestration, telemetry, and volume testing ([[https://github.com/openstack/tempest/tree/master/tempest/scenario|current list]] of tempest scenario tests available). See [[http://logs.openstack.org/78/134978/1/check/check-tempest-dsvm-neutron-full/7ebce20/logs/testr_results.html.gz|example]] for the result of a tempest run. | | |
| Components function test: OpenDaylight/Networking | Ensure OpenDaylight components are installed correctly and functioning. Check whether relevant Karaf modules are loaded and functioning correctly. | | | | Components function test: OpenDaylight/Networking | Ensure OpenDaylight components are installed correctly and functioning. Check whether relevant Karaf modules are loaded and functioning correctly. | | | ||
| Scenario testing: Basic system testing | Basic system testing leverages Tempest Scenario testing with Openstack deployment configured to use Neutron/ML2 managed networking supplied by OpenDaylight.\\ * Basic network ops: Test network connectivity to a VM via a tenant network, a public network, or both. \\ * Advanced server networking: Test VM connectivity after some advanced instance operations executed: start/stop instance, reboot instance, migrate instance, etc. Tests prioritised by relevance to NFV workloads. \\ * Install and removal of ODL Karaf features on running instance. \\ * Security groups: Verify cross tenant connectivity - basic as well as after resizing an instance etc. | | | | Scenario testing: Basic system testing | Basic system testing leverages Tempest Scenario testing with Openstack deployment configured to use Neutron/ML2 managed networking supplied by OpenDaylight.\\ * Basic network ops: Test network connectivity to a VM via a tenant network, a public network, or both. \\ * Advanced server networking: Test VM connectivity after some advanced instance operations executed: start/stop instance, reboot instance, migrate instance, etc. Tests prioritised by relevance to NFV workloads. \\ * Install and removal of ODL Karaf features on running instance. \\ * Security groups: Verify cross tenant connectivity - basic as well as after resizing an instance etc. | | | ||
Line 65: | Line 97: | ||
==== System VNF-management operations testing ==== | ==== System VNF-management operations testing ==== | ||
- | ^ Test/Task ^ Description ^ Interested contributors ^ | + | ^ Test/Task ^ Description ^ Interested contributors ^ |
- | | Simple VNF creation | Create VM images for vRouter (from OpenWRT) and vIDS (from Snort) for testing purposes | | | + | | Simple VNF creation | Create VM images for vRouter (from OpenWRT) and vIDS (from Snort) for testing purposes | Frank | |
- | | Simple VNF hosting: base | Scenario test using Tempest to create and configure a simple VNF: Create 3 VMs: 2 hosts and one instance of a vRouter (OpenWRT) with basic configuration. Test whether vRouter is reachable (within its domain) from the host and can pass packets between the hosts. | | | + | | Simple VNF hosting: base | Scenario test using Tempest to create and configure a simple VNF: Create 3 VMs: 2 hosts and one instance of a vRouter (OpenWRT) with basic configuration. Test whether vRouter is reachable (within its domain) from the host and can pass packets between the hosts. | | |
- | | Simple VNF hosting: Scale/Idempotence testing | Scenario test using Tempest to create/remove n-instances of a vRouter. (Test requires a simple VNFM which in this case will be provided by a script) | | | + | | Simple VNF hosting: Scale/Idempotence testing | Scenario test using Tempest to create/remove n-instances of a vRouter. (Test requires a simple VNFM which in this case will be provided by a script) | | |
- | | Simple VNF hosting: Sequencing | Scenario test using Tempest to investigate system behavior in case components are not triggered/loaded in the correct sequence (i.e. VNFM would behave wrongly) | | | + | | Simple VNF hosting: Sequencing | Scenario test using Tempest to investigate system behavior in case components are not triggered/loaded in the correct sequence (i.e. VNFM would behave wrongly) | | |
- | | Simple VNF hosting: Resource control | Scenario test using Tempest to deploy n instances of vRouter and check for allocated vCPUs, check vCPU pinning. | | | + | | Simple VNF hosting: Resource control | Scenario test using Tempest to deploy n instances of vRouter and check for allocated vCPUs, check vCPU pinning. | | |
- | | Simple VNF hosting: Fault management | Scenario test using Tempest to test detection of VNF failure (vRouter) | | | + | | Simple VNF hosting: Fault management | Scenario test using Tempest to test detection of VNF failure (vRouter) | | |
- | | Simple VNF hosting: Service upgrade | Scenario test using Tempest to replace an existing VNF (vRouter) with a new revision | | | + | | Simple VNF hosting: Service upgrade | Scenario test using Tempest to replace an existing VNF (vRouter) with a new revision | | |
- | | SFC: base | Scenario test using Tempest to create a service chain from a set of open-source VNFs: Firewall and IDS: OpenWRT and Snort. Basic functionality test of the service chain. | | | + | | SFC: base | Scenario test using Tempest to create a service chain from a set of open-source VNFs: Firewall and IDS: OpenWRT and Snort. Basic functionality test of the service chain. | | |
- | | Eventing/Statistics | Scenario tests to test capturing events and statistics from different system components (VNFs, ODL, OpenStack) | | | + | | Eventing/Statistics | Scenario tests to test capturing events and statistics from different system components (VNFs, ODL, OpenStack) | | |