Scenarios
See also scenario status pages:
These links appear to be changing, the can be reached here: http://testresults.opnfv.org/reporting/
- Apex: http://testresults.opnfv.org/reporting/functest/release/master/index-status-apex.html
- Compass: http://testresults.opnfv.org/reporting/functest/release/master/index-status-compass.html
- Fuel: http://testresults.opnfv.org/reporting/functest/release/master/index-status-fuel.html
- Joid: http://testresults.opnfv.org/reporting/functest/release/master/index-status-joid.html
Testing:
- Test Release Criteria (include the appropriate scenario references)
Status legend:
- Active (running as part of a Jenkins job) -> include link to jenkins for details
- Inactive (jenkins job defined - but not active)
- Planning (not yet in JJB but planned)
- Not planned
- <empty field> - not defined for now (plans unknown)
| Scenario Name | VIM | SDN | Features | HA | Apex (Owner) (Status) | Compass | Fuel | Joid | Hardware dependencies (Pharos and CI bare-metal and virtual requirements) | Software dependencies (features, components) | Tests for scenario validation (Smoke) + ... |
|---|---|---|---|---|---|---|---|---|---|---|---|
os-nosdn-nofeature-ha | OS | - | - | HA | Tim Rozet (inactive) | Weidong (active) | Fedor Zhadaev (active) | Artur Tyloch (active) | |||
| os-nosdn-nofeature-noha | OS | - | - | - | Fedor Zhadaev (inactive) | Artur Tyloch (active) | |||||
| os-nosdn-kvm-ha | OS | - | KVM | HA | Raghu Reddy (active) | ||||||
| os-nosdn-kvm_ovs-ha | OS | - | SFQM | HA | Raghu Reddy (inactive) | ||||||
| os-nosdn-kvm-noha | OS | - | KVM | - | Raghu Reddy (inactive) | ||||||
| os-nosdn-kvm_ovs-noha | OS | - | KVM OVSNFV | - | Raghu Reddy (inactive) | ||||||
| os-nosdn-ovs-ha | OS | - | SFQM | HA | Tom Herbert | Mark Gray (active) | |||||
| os-nosdn-ovs-noha | OS | - | OVSNFV SFQM | - | Tom Herbert | Mark Gray (inactive) | |||||
| os-nosdn-vlan-ha | OS | - | HA | Fedor Zhadaev (inactive) | |||||||
| os-odl_l2-nofeature-ha | OS | ODL Layer2 | - | HA | Tim Rozet (active) | Weidong | Fedor Zhadaev (active) | Artur Tyloch (active) |
| ||
| os-odl_l2-sfc-noha | OS | ODL Layer2 | SFC | - | Brady Johnson (inactive) | Brady Johnson (inactive) | Tacker | ||||
| os-odl_l2-sfc-ha | OS | ODL Layer2 | SFC | HA | Brady Johnson (active) | Tacker | |||||
| os-odl_l2-bgpvpn-ha | OS | ODL Layer2 | BGPVPN | HA | Tim Irnich (active) | Tim Irnich (active) | |||||
| os-odl_l2-bgpvpn-noha | OS | ODL Layer2 | BGPVPN | - | Tim Irnich (active) | ||||||
| os-nosdn-fdio-noha | OS | VPP/FDS | - | Frank Brockners (planning) |
ref vpp page
| ||||||
| os-odl_l2-fdio-noha | OS | ODL Layer2 | VPP/FDS | - | Frank Brockners (planning) |
ref vpp page
| |||||
| os-odl_l2-fdio-ha | OS | ODL Layer2 | VPP/FDS | HA | Frank Brockners (planning) |
ref vpp page
| |||||
| os-odl_l3-fdio-noha | OS | ODL Layer3 | VPP/FDS | - | Frank Brockners (planning) |
ref vpp page
| |||||
| os-odl_l3-fdio-ha | OS | ODL Layer3 | VPP/FDS | HA | Frank Brockners (planning) |
ref vpp page
| |||||
| os-odl_l3-nofeature-ha | OS | ODL Layer3 | - | HA | Tim Rozet | Weidong (inactive) | Fedor Zhadaev | ||||
| os-odl_l3-nofeature-noha | OS | ODL Layer3 | - | - | Fedor Zhadaev (inactive) | ||||||
| os-odl_l3-vpp-ha | OS | ODL Layer3 | VPP/FDS | HA | Frank Brockners (planning) |
ref vpp page
| |||||
| os-ocl-nofeature-ha | OS | OpenContrail | - | HA | Stuart Mackie (inactive) | Stuart Mackie (active) | Stuart Mackie (active) | ||||
| os-ocl-nofeature-noha | OS | OpenContrail | - | - | Stuart Mackie (inactive) | ||||||
| os-onos-nofeature-ha | OS | ONOS | - | HA | Wei Su (active) | Wei Su (active) | Wei Su (active) | Wei Su (active) | |||
| os-onos-sfc-ha | OS | ONOS | SFC | HA | Wei Su (inactive) | Wei Su (Inactive) | Wei Su (inactive) | Wei Su (active) | VNFFG | ||
| os-nosdn-lxd-noha | OS | - | LXD | - | Artur Tyloch (active) | ||||||
| os-nosdn-lxd-ha | OS | - | LXD | HA | Artur Tyloch (active) |
Feature Project Dependencies on Scenarios and other Features
- Scenario Compatibility: Scenarios in which the Feature should be usable
- Note: presumes that the Feature project will ensure that the Feature is installed as part of the Scenario deploy, or is installable and usable/testable post-deploy
- Dependency upon Scenarios: what Scenario context the Feature depends upon, or constraints it has
- Scenario Base Testing
- Yes (to be tested as part of the base Scenario deploy/test stage) or a list of Scenarios for which "Yes" applies
- No: only in supplemental (post-CI/CD) testing
- Dependency upon Features: what the Feature requires from other Features (or specific aspect/test of the Feature)
- Note: it's assumed that the dependency is partial, i.e. Features are not wholly dependent upon other Features unless specified e.g. as ("Full: <Feature>")
- Note: it's assumed that the dependency is partial, i.e. Features are not wholly dependent upon other Features unless specified e.g. as ("Full: <Feature>")
Please keep the points below in mind while completing the last two right-hand columns of below table.
- Indicate Pharos Specification Compatibility against baseline
- Projects must clearly state the specification of the resource needs that will be used for CI purposes.
- Based on this information, validation/compatibility check against the Pharos Specification must be done by the projects with the support from Infra WG in order to identify whether the project needs comply or not with the Pharos Specification.
- If the needs comply with Pharos Specification and if the resources are not secured, project should request resources from Pharos Project by writing a ticket on JIRA and adding the link of the issue on corresponding row in the table. Please follow the process documented on the page Generic Lab Request Process.
- Is Pharos Change Process Complete and CI Resources Available
- If the "Pharos Specification Compatibility" column entry is "Standard Pharos POD", then this column should be blank.
- If the "Pharos Specification Compatibility" column entry is anything other than "Standard Pharos POD", then this column must be completed.
- If requested resources are not Pharos compliant, a change request must be submitted by following the process documented on Pharos Architecture Change Request Process.
- The requesting project must then follow up with the Infra WG to get the change approved, applied and requested resources provided. Link to the JIRA issue should be added on corresponding row in the table.
- Notes
- Please list CI resources only and not development resources as specified on column headings.
- Example resources are
- Standard Pharos POD (5+1) -> this is essentially getting integrated to an installer with no special additions
- 1 standalone machine capable of deploying OpenStack HA virtually -> these resources must be connected to Jenkins and running jobs on Jenkins automatically
- 2 standalone machines capable of deploying OpenStack HA virtually -> these resources must be connected to Jenkins and running jobs on Jenkins automatically
- Pharos POD with 2NICs in each compute node -> this requires CR process and might require installers to support additional NIC
- Please list CI resources only and not development resources as specified on column headings.
| Project | Current (Brahmaputra) Scenario Compatibility | New (Colorado) Scenario Compatibility | Dependency upon Scenarios | Scenario Base Testing | Dependency upon Features | Indicate Pharos Specification Compatibility (against baseline) for CI/Production | Is Pharos change process complete and CI resources available |
|---|---|---|---|---|---|---|---|
| Armband | FUEL-os-nosdn-nofeature-ha FUEL-os-nosdn-nofeature-noha FUEL-os-odl_l2-nofeature-ha FUEL-os-odl_l2-nofeature-noha | APEX-os-nosdn-nofeature-ha FUEL-os-nosdn-nofeature-ha FUEL-os-nosdn-nofeature-noha JOID-os-nosdn-nofeature-ha JOID-os-nosdn-nofeature-noha APEX-os-odl_l2-nofeature-ha FUEL-os-odl_l2-nofeature-ha FUEL-os-odl_l2-nofeature-noha JOID-os-odl_l2-nofeature-ha JOID-os-odl_l2-nofeature-noha | Standard Pharos POD | A full arm64-based HA pod is allocated within the Enea Pharos Lab for the Colorado project and has been integrated with CI. | |||
| Copper | JOID-* | Apex-* | Non-HA | Yes | Congress | Standard Pharos POD | No changes needed |
| Doctor | Apex-* | Fuel-*, JOID-*, Compass-* | Yes | Congress, Vitrage and Aodh/Celiometer | Standard Pharos POD | (We planned to have doctor dedicated test job which will be run every patch upload. If we have such job, we might use pods in ZTE and OOL. But, it's not mandatory for Colorado) | |
| Domino | os-nosdn-nofeature-ha, os-nosdn-nofeature-noha | Non-HA or HA | N/A | Standard Pharos POD |
| ||
| FastDataStacks | n/a | APEX-os-odl2-vpp-noha APEX-os-odl3-vpp-noha | noha or ha | Yes | ODL Boron latest, VPP | Standard Pharos POD | No changes needed |
| HA | N/A | N/A | N/A | N/A | N/A | N/A | N/A |
| Ipv6 | APEX-os-nosdn-nofeature-ha COMPASS-os-nosdn-nofeature-ha FUEL-os-nosdn-nofeature-ha FUEL-os-nosdn-nofeature-noha JOID-os-nosdn-nofeature-ha JOID-os-nosdn-nofeature-noha APEX-os-odl_l2-nofeature-ha COMPASS-os-odl_l2-nofeature-ha FUEL-os-odl_l2-nofeature-ha FUEL-os-odl_l2-nofeature-noha JOID-os-odl_l2-nofeature-ha JOID-os-odl_l2-nofeature-noha | APEX-os-nosdn-nofeature-ha COMPASS-os-nosdn-nofeature-ha FUEL-os-nosdn-nofeature-ha FUEL-os-nosdn-nofeature-noha JOID-os-nosdn-nofeature-ha JOID-os-nosdn-nofeature-noha APEX-os-odl_l2-nofeature-ha COMPASS-os-odl_l2-nofeature-ha FUEL-os-odl_l2-nofeature-ha FUEL-os-odl_l2-nofeature-noha JOID-os-odl_l2-nofeature-ha JOID-os-odl_l2-nofeature-noha | os-nosdn-nofeature os-odl_l2-nofeature HA or NOHA | Yes | N/A | Yes, standard Pharos environment without special needs | 2 blades are allocated and work in progress. |
| Models | N/A | All | None | yes | None | Standard Pharos POD | No changes needed |
| Movie | N/A | os-odl_l2-nofeature-ha os-onos-nofeature-ha | Non-HA or HA | yes | requires Karaf cli to run tests over both odl/onos for use case testing | Standard Pharos POD | Need a standard OPNFV ODL POD for Movie add-on testing |
| Multisite | N/A | All | Non-HA or HA
| Yes | Requires two OpenStack sites with shared KeyStone | 2 standalone machines | Two blades have been allocated |
| NFV for KVM | os-nosdn-kvm-ha | os-nosdn-kvm-ha os-nosdn-kvm_ovs-ha | yes | Depends on Fuel's NFV4KVM support | Standard Pharos POD; Use VM environment for it. | No changes needed | |
| ONOSFW | os-onos-nofeature-ha | os-onos-nofeature-ha APEX-os-onos-sfc-ha COMPASS-os-onos-sfc-ha FUEL-os-onos-sfc-ha JOID-os-onos-sfc-ha | HA or Non-HA | Yes | Mitaka networking-sfc, onos goldeneye and ovs with nsh support | Standard Pharos Pod | No changes needed |
| Open vSwitch for NFV | Fuel - nosdn-ovs-ha | Fuel-nosdn-ovs-ha/noha Apex-nosdn-ovs-ha/noha | Yes | only supports Neutron vlan tenant networks | Standard Pharos Pod | ||
| OVNO | apex-os-ocl-nofeature-ha joid-os-ocl-nofeature-nonha/ha compass-os-ocl-nofeature-ha | HA | Yes | None | Standard Pharos Pod | ||
| Parser | APEX-os-nosdn-nofeature-noha COMPASS-os-nosdn-nofeature-noha FUEL-os-nosdn-nofeature-noha JOID-os-nosdn-nofeature-noha
| APEX-os-nosdn-nofeature-noha COMPASS-os-nosdn-nofeature-noha FUEL-os-nosdn-nofeature-noha JOID-os-nosdn-nofeature-noha | OpenStack tosca-parser and heat-translator, which both are part of Heat release. | Standard Pharos POD; Use VM environment | No Changes Needed | ||
| Prediction | Requirements Project | no CI integration | |||||
| Promise | Fuel-*, JOID-* | no new scenarios | No | Yes | None | Standard Pharos POD | No Changes Needed |
| SDNVPN | FUEL-os-odl_l2-bgpvpn-ha, FUEL-os-odl_l2-bgpvpn-noha, APEX-os-odl_l2-bgpvpn-noha, APEX-os-odl_l2-bgpvpn-ha | planned to rename scenarios to: os-odl_vpnservice-sdnvpn-{ha|noha} Planned to create a new scenario that uses the ODL VPN Service as Neutron backend without BGPVPN: os-odl_vpnservice-{ha|noha} | None | Yes | Standard Pharos POD | ||
| Service Function Chaining (SFC) | os-odl_l2-sfc-ha, os-odl_l2-sfc-noha | os-odl_l2-sfc-ha, os-odl_l2-sfc-noha | HA or Non-HA | Yes, Yardstick | Apex, Fuel, Tacker, Yardstick | Standard Pharos POD | No changes needed |
| SFC ONOS | Standard Pharos POD | Depends on Lab resources avilability for os-nos-sfc-ha | |||||
| SFQM | Fuel-nosdn-ovs-ha/noha apex-nosdn-ovs-ha? | Not Yet | We depend on OVS4NFV being installed on the platform with a version of DPDK >= 16.04 | Standard Pharos POD | |||
| VNFFG | os-onos-nofeature-ha | os-onos-sfc-ha | HA or Non-HA | Yes | Mitaka networking-sfc, onos goldeneye and/or ovs with nsh suport | Standard Pharos Pod | |