RA-1, RI-1 and RC-1 Traceability and Gap Analysis

1

RM 4.2.1.1

RM 4.2.4

Predefined Flavors

Catalog of Predefined Flavor Geometries

RA-1 "4.2.2.5. Compute Nodes"

3.2 VNF Category

Yes

Armada Charts

Please see the manifests

Functional

2

RM 4.2.2

Flavor Networking

Network Interface Specifications

RA-1 "4.2.2.9 Compute node configurations for Profiles and Flavors"

3.2 VNF Category

Yes

Armada Charts

Functional

3

RM 4.2.3

Flavor Storage Extensions

Flavor Storage Extensions

RA-1 "4.4.1. Support for Profiles and T-shirt instance types"

3.2 VNF Category

Yes

Armada Charts

Functional

4

RM 4.2.5

Also  RM 5.2.1

Profile Capabilities

Profile Capabilities includes specifications for capabilities such as CPU Pinning, NUMA support, SR-IOV, FPGA, etc.

RA-1 "4.4.1. Support for Profiles and T-shirt instance types"

3.3 NFVI SW Profile

Yes

Armada Charts

Functional

5

RM 5.2.3

Virtual (Overlay) Networking

Virtual (Overlay) Networking including vNIC interfaces, Protocols (VXLAN, Geneve, ...), NAT, Security Groups, HW Offload, crypto acceleration

RA-1 "4.2.3. Network Fabric"

3.3 NFVI SW Profile

Yes

Armada Charts

Functional

6

RM 5.4

HW Profiles

Hardware Profiles including configurations for compute, storage, networking, PCIe

RA-1 "4.2.2. Compute"

3.4 NFVI HW Profile

Yes

Armada Charts

Functional

1

req.gen.ost.01

Open source

The Architecture must use OpenStack APIs.

RA-1 5.3. Consolidated Set of APIs

Yes

Armada Chart

Manifests

with Airship 2.0 will replace with helm operator

Functional

2

req.gen.ost.02

Open source

The Architecture must support dynamic request and configuration of virtual resources (compute, network, storage) through OpenStack APIs.

RA-1 5.3. Consolidated Set of APIs

Yes

NA

Once OpenStack installed this is intrinsic capability

Functional

3

req.gen.rsl.01

Resiliency

The Architecture must support resilient OpenStack components that are required for the continued availability of running workloads.

RA-1 3.3.1. VIM Core services

Yes

NA

Once k8s installed this is intrinsic capability

OSTK components resiliency

missing

@Al Morton There are several HA tests conducted as part of OVP 1.0, are they sufficient?

Yardstick TC025 and/or TC045

supported through redundancy; redundancy and recoverability can be managed through k8s

4

req.gen.avl.01

Availability

The Architecture must provide High Availability for OpenStack components.

RA-1 4.2 Underlying Resources

Yes

NA

Once k8s installed this is intrinsic capability

OSTK Components High Availability

missing

@Al Morton There are several HA tests conducted as part of OVP 1.0, are they sufficient?

supported through redundancy; redundancy and recoverability can be managed through k8s

1

req.inf.com.01

Compute

The Architecture must provide compute resources for VM instances.

RA-1 3.3.1.4 "Cloud Workload Services"

Yes

Armada Chart

Functional

Functest

2

req.inf.com.04

Compute

The Architecture must be able to support multiple CPU SKU options to support various infrastructure profiles (Base, and Network Intensive).

RA-1 4.4.1. "Support for Profiles and T-shirt instance types"

Yes

Armada Chart

Post processing

Functional

missing

needs to be confirmed (same as RM requirements)

3

req.inf.com.05

Compute

The Architecture must support Hardware Platforms with NUMA capabilities.

RA-1 4.4.1. "Support for Profiles and T-shirt instance types"

Yes

Armada Chart

Functional

Functest

Functest supports tuning a few inputs such flavor extra specs (e.g. hugepages). All tests can be executed multiple times (basic then network intensive) 

comment acknowledged, no action required

4

req.inf.com.06

Compute

The Architecture must support CPU Pinning of the vCPUs of VM instance.

RA-1 4.4.1. "Support for Profiles and T-shirt instance types"

Yes

Armada Chart

Functional

Functest

Functest supports tuning a few inputs such flavor extra specs (e.g. hugepages). All tests can be executed multiple times (basic then network intensive) 

comment acknowledged, no action required

5

req.inf.com.07

Compute

The Architecture must support different hardware configurations to support various infrastructure profiles (Base, and Network Intensive).

RA-1 3.3.3. "Host aggregates providing resource pooling"

Yes

Armada chart

Functional

Functest

Functest supports tuning a few inputs such flavor extra specs (e.g. hugepages). All tests can be executed multiple times (basic then network intensive) 

comment acknowledged, no action required

6

req.inf.com.08

Compute

The Architecture must support allocating certain number of host cores/threads to non-tenant workloads such as for OpenStack services.

Dedicating host core/sibling threads to certain workloads (e.g., OpenStack services. Please see example, "Configuring libvirt compute nodes for CPU pinning"

Yes

Armada chart

Functional

7

req.inf.com.09

Compute

The Architecture must ensure that the host cores/threads assigned to a workload are thread-sibling aware: that is, that a core and its associated SMT threads are either all assigned to non-tenant workloads or all assigned to tenant workloads.

Achieved through configuring the "cpu_dedicated_set" and "cpu_shared_set" parameters in nova.conf correctly.

Yes

Armada chart

Functional

@Al Morton Possibly verified with VSPERF testing (Cross-NUMA Test Results). Also ETSI NFV TST009, clause 12.4 and Annex D.

8

req.inf.stg.01

Storage

The Architecture must provide remote (not directly attached to the host) Block storage for VM Instances.

RA-1 3.4.2.3. "Storage"

Yes

Armada chart

Functional

Functest

too generic and should mention the ref to the mandatory capabilities and the status expected.

130 single tests about volumes amongst tempest_cinder, tempest_full, tempest_scenario and tempest_slow ( +indirect testing in case of tempest_heat)

addressed in req.int.api.03 below

(PR #1622 merged)

9

req.inf.stg.02

Storage

The Architecture must provide Object storage for VM Instances. Operators may choose not to implement Object Storage but must be cognizant of the risk of "Compliant VNFs" failing in their environment.

OpenStack Swift Service (RA-1 4.3.1.4 "Swift")

Yes

Armada chart

Functional

Functest

too generic and should mention the ref to the mandatory capabilities and the status expected.

140 single tests about object storage amongst tempest_full, tempest_scenario and tempest_slow ( +indirect testing in case of tempest_heat)

addressed in req.int.api.04 below

(PR #1622 merged)

10

req.inf.stg.03

move to Recommendations

Storage

The Architecture may provide a file system service (file system storage solution) for VM Instances.

RA-1 4.2.4. "Storage Backend"

Yes

Armada chart

Functional

Out of CNTT RC (may)

+ an API proposing this feature should be proposed in CNTT first

The tempest plugin could be added in Functest if it makes sens (IaaS verification). Useless on CNTT side right now

Bug here!

11

req.inf.stg.04

move to Recommendations

Storage

The Architecture may support Software Defined Storage (SDS) that seamlessly supports shared block storage, object storage and flat files.

RA-1 4.2.4.1. "Ceph Storage Cluster"

Yes

Armada chart

Functional

Out of CNTT RC (may)

As far as I understand It's out of CNTT (implementation design) 

Ceph is tested thought the mandatory service API by Functest

12

req.inf.stg.06

move to Recommendations

Storage

The Architecture should make the immutable images available via location independent means.

RA-1 4.3.1.2. "Glance"

Yes

Armada chart

Functional

Functest

It's a must requirement according RA1 Chapter5

Bug here !

Glance is required but not necessarily immutable images – some operators make changes to install needed tools such anti-virus etc.

13

req.inf.stg.07