/
Airship RI-1 Gap Analysis

Anuket Project

Airship RI-1 Gap Analysis

Feb 26, 2021

  • L2 Only

    • Airship 1.8 reference type added support for OVS-DPDK but is currently L2(provider network) only for performance improvement and avoiding Neutron L3+DPDK complexities/issues.

    • Airship and FuncTest have already worked together to address a large number of tempest and ci cases to remove/skip dependency on Neutron L3 tenant work, router, floating ip etc.. Here are the list of remaining tempest test cases still failing: 

    • Add L2 only VNF workload in FuncTest. Currently used VNF workload for testing are L3 dependent and have to be skipped. (Note: Cedric has mentioned HeatIMS as a potential candidate). 

    • For the long run, we need to add L3 support as an option in RI-1. (Capture lack of L3 in chapter 9 as a gap, section 9.4 

      (https://github.com/cntt-n/CNTT/blob/master/doc/ref_impl/cntt-ri/chapters/chapter09.md)

  • OpenStack

    • Train release (tie RI-1 conformance to Baldy)

    • Nova live migration. (add in Gap)

    • Tempest test failures:

  • Community lab

    • POD 17 is used for Airship development and running the master (Post Jerma). It is significantly under-spec (RAM and disk). Node 4 has hardware issues. Ticket open.

    • POD 15 is for RC gate. It is out of commission because Node 1 has issue with BMC console and couldn't install OS. Ticket open.  When the hardware issue is addressed, it needs to bring up to Airship 1.8 (Jerma) for the RC gate and community reference/shared use.