Page tree
Skip to end of metadata
Go to start of metadata

Scenarios

See also scenario status pages:

These links appear to be changing, the can be reached here: http://testresults.opnfv.org/reporting/

Testing:

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 NameVIMSDNFeaturesHAApex
(Owner)
(Status) 
CompassFuelJoid

Hardware dependencies

(Pharos and CI bare-metal

and virtual requirements)

Software dependencies

(features, components)

Tests for scenario validation

(Smoke) + ...

os-nosdn-nofeature-ha

OS--HATim Rozet
(inactive) 
Weidong
(active
Fedor Zhadaev
(active
Artur Tyloch
(active
  
os-nosdn-nofeature-nohaOS---  Fedor Zhadaev
(inactive) 
Artur Tyloch
(active) 
  
os-nosdn-kvm-haOS-KVMHA  Raghu Reddy 
(active)
   
os-nosdn-kvm_ovs-haOS-

KVM
OVSNFV

SFQM

HA  Raghu Reddy
(inactive)
   
os-nosdn-kvm-nohaOS-KVM-  Raghu Reddy
(inactive)
   
os-nosdn-kvm_ovs-nohaOS-KVM
OVSNFV 
-  Raghu Reddy
(inactive)
   
os-nosdn-ovs-haOS-

OVSNFV

SFQM

HATom Herbert Mark Gray
(active)
   
os-nosdn-ovs-nohaOS-OVSNFV
SFQM 
-Tom Herbert Mark Gray
(inactive)
   
os-nosdn-vlan-haOS- HA  Fedor Zhadaev
(inactive)
   
os-odl_l2-nofeature-haOSODL Layer2-HATim Rozet
(active

Weidong
(active

Fedor Zhadaev
(active)
Artur Tyloch
(active
 
  • promise
  • doctor
  • movie
os-odl_l2-sfc-nohaOSODL Layer2SFC-

Brady Johnson

(inactive)

 

Brady Johnson

(inactive)

  Tacker
os-odl_l2-sfc-haOSODL Layer2SFC  HA  Brady Johnson
(active)
  Tacker
os-odl_l2-bgpvpn-haOSODL Layer2BGPVPN  HATim Irnich
(active
 Tim Irnich
(active)
   
os-odl_l2-bgpvpn-nohaOSODL Layer2BGPVPN  -  Tim Irnich
(active)
   
os-nosdn-fdio-nohaOS VPP/FDS-Frank Brockners
(planning)
     

ref vpp page

os-odl_l2-fdio-nohaOSODL Layer2VPP/FDS-Frank Brockners
(planning)
     

ref vpp page

os-odl_l2-fdio-haOSODL Layer2VPP/FDSHAFrank Brockners
(planning)
     

ref vpp page

os-odl_l3-fdio-nohaOSODL Layer3VPP/FDS-Frank Brockners
(planning)
     

ref vpp page

os-odl_l3-fdio-haOSODL Layer3VPP/FDSHAFrank Brockners
(planning)
     

ref vpp page

os-odl_l3-nofeature-haOSODL Layer3-HA

Tim Rozet
(active)

Weidong
(inactive) 

Fedor Zhadaev
(active)

   
os-odl_l3-nofeature-nohaOSODL Layer3--  Fedor Zhadaev
(inactive)
   
os-odl_l3-vpp-haOSODL Layer3VPP/FDSHAFrank Brockners
(planning) 
     

ref vpp page 

os-ocl-nofeature-haOSOpenContrail-HAStuart Mackie
(inactive)
Stuart Mackie
(active
 Stuart Mackie
(active
  
os-ocl-nofeature-nohaOSOpenContrail--   Stuart Mackie
(inactive
  
os-onos-nofeature-haOSONOS-HAWei Su
(active
Wei Su
(active)
Wei Su
(active)
Wei Su
(active)
  
os-onos-sfc-haOSONOSSFCHAWei Su (inactive)  Wei Su (Inactive)Wei Su
(inactive)
Wei Su
(active)
  VNFFG
os-nosdn-lxd-nohaOS-LXD-   Artur Tyloch
(active
  
os-nosdn-lxd-haOS-LXDHA   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>")

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
ProjectCurrent (Brahmaputra) Scenario CompatibilityNew (Colorado) Scenario CompatibilityDependency upon ScenariosScenario Base TestingDependency upon FeaturesIndicate 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.
CopperJOID-*Apex-*Non-HAYesCongressStandard Pharos PODNo changes needed
DoctorApex-*Fuel-*, JOID-*, Compass-* YesCongress, Vitrage and Aodh/CeliometerStandard 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-odl2-vpp-ha

APEX-os-odl3-vpp-noha
APEX-os-odl3-vpp-ha 

noha or haYesODL Boron latest,
VPP  
Standard Pharos PODNo changes needed
HAN/AN/AN/AN/AN/AN/AN/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

YesN/A

Yes, standard Pharos environment without special needs

PHAROS-181

2 blades are allocated and work in progress.

ModelsN/AAllNoneyesNoneStandard Pharos PODNo changes needed
MovieN/A

os-odl_l2-nofeature-ha

os-onos-nofeature-ha

 Non-HA or HAyesrequires Karaf cli to run tests over both odl/onos for use case testingStandard Pharos PODNeed a standard OPNFV ODL POD for Movie add-on testing
MultisiteN/AAll

Non-HA or HA

 

YesRequires two OpenStack sites with shared KeyStone

2 standalone machines

Two blades have been allocated
NFV for KVMos-nosdn-kvm-ha

os-nosdn-kvm-ha

os-nosdn-kvm_ovs-ha

  yesDepends on Fuel's NFV4KVM support

Standard Pharos POD;  Use VM environment for it.  

No changes needed
ONOSFWos-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-HAYesMitaka networking-sfc, onos goldeneye and ovs with nsh supportStandard Pharos PodNo changes needed
Open vSwitch for NFVFuel - nosdn-ovs-ha

Fuel-nosdn-ovs-ha/noha

Apex-nosdn-ovs-ha/noha 

 Yesonly 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

HAYesNone

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 Projectno CI integration
PromiseFuel-*, JOID-*no new scenariosNoYesNoneStandard Pharos PODNo Changes Needed
SDNVPNFUEL-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}

NoneYes Standard Pharos POD 
Service Function Chaining (SFC)os-odl_l2-sfc-ha, os-odl_l2-sfc-nohaos-odl_l2-sfc-ha, os-odl_l2-sfc-nohaHA or Non-HAYes, YardstickApex, Fuel, Tacker, YardstickStandard Pharos PODNo changes needed
SFC ONOS     Standard Pharos PODDepends on Lab resources avilability for os-nos-sfc-ha
SFQM Fuel-nosdn-ovs-ha/noha
apex-nosdn-ovs-ha?


 Not YetWe depend on OVS4NFV being installed on the platform with a version of DPDK >= 16.04

Standard Pharos POD 

 
VNFFGos-onos-nofeature-haos-onos-sfc-haHA or Non-HAYesMitaka networking-sfc, onos goldeneye and/or ovs with nsh suportStandard Pharos Pod