Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

    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-*, Fuel-*, Compass-*Non-HA (TBV)YesCongress  
doctorApex-*Fuel-*, JOID-*, Compass-*  Congress, Vitrage and Aodh/Celiometer  
Domino  Apex, Fuel, Compass, JoidNon-HA or HA Requires two OpenStack installation with distinct Heat enginesYes, standard Pharos environment without special needs

PHAROS-181 (refer to comments for Domino)

2 blades are allocated and work in progress. will add along with test to IPv6 Domino functional tests.

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/AYes, standard Pharos environment without special needs

PHAROS-181

2 blades are allocated and work in progress.

ModelsN/A      
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 testing  
multisite Fuel, Compass

Non-HA or HA

 

 Requires two OpenStack sites with shared KeyStone Two blades allocated
NFV for KVMos-nosdn-kvm-ha

os-nosdn-kvm-ha

os-nosdn-kvm_ovs-ha

  yesDepends on Fuel's NFV4KVM support Use VM environment for it. 
ONOSFW       
Open vSwitch for NFVFuel - nosdn-ovs-ha

Fuel-nosdn-ovs-ha/noha

Apex-nosdn-ovs-ha/noha 

 Yesonly supports Neutron vlan tenant networksWill require 2 NICs on each compute node. One for management traffic under kernel control and one for tenant traffic under DPDK control.

Standard Pharos Pod

(with 2 network ports)

 
OVNO       
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.  
policytest       
prediction       
promiseFuel-*, JOID-*no new scenariosNo    
rsN/A      
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 The scenario should deploy on a standard Pharos environment without any special needs. 
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, Yardstick  
SFC ONOSos-onos-nofeature-haos-onos-sfc-haHA or Non-HAYesMitaka networking-sfc, onos goldeneye and/or ovs with nsh suportPharos compatibility  not evaluated for new scenarioDepends on Lab resources avilability for os-nos-sfc-ha
SFQM Fuel-nosdn-ovs-ha/noha

 Not YetWe depend on OVS4NFV being installed on the platform with a version of DPDK >= 16.04Will require 2 NICs on each compute node. One for management traffic under kernel control and one for tenant traffic under DPDK control. 
VNFFGos-onos-nofeature-haos-onos-sfc-haHA or Non-HAYesMitaka networking-sfc, onos goldeneye and/or ovs with nsh suportPharos compatibility  not evaluated for new scenarioDepends on Lab resources avilability for os-nos-sfc-ha