Versions Compared

Key

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

Table of Contents
maxLevel2

POMBA Data Router

HTTPS Support

Test CaseDescriptionStatusOwnerDateJIRA linkCommentdata-router | deployment | httpsVerify that the POMBA data-router can be deployed using HTTPS as a configurable parameter.PASS Jira LegacyserverSystem Jiracolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

Validation passes, this particular attribute only exists in AAI, so no other builders to compare with

however you can still see the data in kibana as part of other violation payload



Table of Contents
maxLevel2

POMBA Data Router

HTTPS Support

Test CaseDescriptionStatusOwnerDateJIRA linkComment
data-router | deployment | httpsVerify that the POMBA data-router can be deployed using HTTPS as a configurable parameter.PASS

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-559


data-router | orchestration-initiation | httpsVerify that an orchestration-event can be published to the data-router over HTTPSPASS

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-559


data-router | orchestration-initiation | httpsVerify that the data-router rejects the orchestration-event if sent via HTTPPASS

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-559


data-router | server-side certificates | httpsThe purpose of the test is to validate that the orchestration-event to data-router can only be successful with server-side certificatesPASS

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-559


data-router | server-side certificatesThe purpose of the test is to validate that the orchestration-event to data-router will be rejected if the server-side certificates are not loadedPASS

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-559



Context Builder: SDNC

OOM

Test CaseDescriptionStatusOwnerDateJIRA linkComment
oom deploymentVerify that the SDNC Context Builder is capable of being deployed through OOM.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-426


oom deletion Verify that the SDNC Context Builder is capable of being deleted form a POMBA deployment.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-426


SDNC Seed Code w/ Generic Resources API

Test CaseDescriptionStatusOwnerDateJIRA linkComment
context aggregator | builders | properties | sdnc.propertiesVerify that the Context Aggregator config/builders/ directory contains an sdnc.properties file upon deployment so that the builder can be utilized in audits.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-520


sdnccontextbuilder | service | context | basic authVerify that the SDNC Context Builder can successfully process an incoming context request using basic authentication.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-520


sdnccontextbuilder | service | context | basic auth | bad credentialsVerify that the SDNC Context Builder rejects requests that do not provide the correct credentials.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-520


context aggregator -> sdnc context builderVerify that the Context Aggregator is capable of interoperating with the SDNC Context Builder.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-520


sdnc context builder -> sdncVerify that the SDNC Context Builder is capable of interoperating with an SDNC.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-520


POMBA APIv1

Test CaseDescriptionStatusOwnerDateJIRA linkComment
sdnccontextbuilder | v1 | service | contextVerify that the SDNC Context Builder context API can be called while explicitly referencing the version (v1).PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | service | contextVerify that when the API version for the SDNC Context Builder is not explicitly specified, the latest version (APIv1) will be invoked.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | v1 | service | context | vservers fieldsVerify that the SDNC Context Builder can return the full list of required attributes associated with one or more vservers associated with a service instance. The attribute values should be obtained from the correct source attributes.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | v1 | service | context | l3-networks fieldsVerify that the SDNC Context Builder can return the full list of required attributes associated with one or more l3-networks associated with a service instance. The attribute values should be obtained from the correct source attributes.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | v1 | service | context | serviceInstanceId missingVerify that the SDNC Context Builder returns a 400 error when the required serviceInstanceID parameter is missing.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | v1 | service | context | X-TransactionId missingVerify that the SDNC Context Builder is capable of processing a context request that omits the X-TransactionId header.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | v1 | service | context | X-FromAppId missingVerify that the SDNC Context Builder reutrns a 400 error processing a context request that omits the X-FromAppId header.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | v1 | service | context | SDNC not availableVerify that the SDNC Context Builder returns a 500 error when the SDNC from which data is to be obtained is not available.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | v1 | service | context | service not foundVerify that the SDNC Context Builder returns a 404 error when the service instance for which context is requested cannot be located in the SDNC.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


sdnccontextbuilder | logging | successVerify that the SDNC Context Builder provides sufficient logging when a context request is successfully processed.

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462

Logging for the sdncctxbuilder will be tested on the next phase of the epic
sdnccontextbuilder | logging | failure | bad requestVerify that the SDNC Context Builder provides sufficient logging when a context request is unsuccessfully processed due to a missing parameter.

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462

Logging for the sdncctxbuilder will be tested on the next phase of the epic
sdnccontextbuilder | v1 | swaggerVerify that the SDNC Context Builder provides swagger documentation for v1 of the Context Builder API.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


wikiVerify that the wiki documentation provides a suitable description of the SDNC Context Builder APIv1.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-462


API Mapper w/ VNF API

Test CaseDescriptionStatusOwnerDateJIRA linkComment
default config | context request | service type | vFWVerify that, using the default configuration, the VNF API is utilized when the SDNC Context Builder detects that the service instance is of type "vFW".PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421


default config | context request | service type | vDNSVerify that, using the default configuration, the VNF API is utilized when the SDNC Context Builder detects that the service instance is of type "vDNS".PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421


default config | context request | service type | non-vFW/vDNSVerify that, using the default configuration, the GENERIC-RESOURCE-API is utilized when the SDNC Context Builder detects that the service instance isn't of the type vFW or vDNS.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421


generic-resource-api | common model support | vserverVerify that when the SDNC Context Builder utilizes the Generic Resource API to gather service data, the output is able to pass along all of the mandatory vserver attributes.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421


generic-resource-api | common model support | l3-networkVerify that when the SDNC Context Builder utilizes the Generic Resource API to gather service data, the output is able to pass along all of the mandatory l3-network attributes.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421


rules modificationVerify that the rules used to select which API should be used to gather service data can be changed.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421


context request | aai unavailableVerify that an error is returned when the SDNC Context Builder is unable to contact the AAI and cannot, therefore, determine ServiceType for rules mappingPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421


developer wikiVerify that the developer wiki has been updated to include information about the API mapping feature in SDNC Context Builder, including how to modify the mapping rulesPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421


L2 Fabric Retrieval - network


Test CaseDescriptionStatusOwnerDateJIRA linkComment
network | sdnc| SDNCctxbuilder | Generic-APIVerify that the latest sdncctxbuilder can query SDNC and return the required attributesPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-768


network | sdnc| SDNCctxbuilder | VNF-APIVerify that the latest sdncctxbuilder can query SDNC and return the required attributes FAIL

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-768

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-968

L2 Fabric Retrieval - pnf

Test CaseDescriptionStatusOwnerDateJIRA linkComment

network | sdnc| SDNCctxbuilder| Generic-API

Verify that the latest sdncctxbuilder can query SDNC and return the required attributesPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-778



POMBA Reporting

https support for Kibana

Test CaseDescriptionStatusOwnerDateJIRA linkComment
oom deploymentVerify that the pomba-kibana dashboard can be deployed via an allowed HTTPS only configurationPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-517


oom deployment

Generate new self signed certificate and verify HTTPS connection after deploymentPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-517


kibana dashboard accessVerify that the kibana dashboard can only be accessed via HTTPS when configuredPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-517


kibana dashboard accessVerify that pomba reports are posted and are view-able by KibanaPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-517


A&AI Context Builder

L2 Fabric Retrieval - PNF

Test CaseDescriptionStatusOwnerDateJIRA linkComment
pnf | aai | aaictxbuilderVerify that the latest aaictxbuilder can query AAI and return the required attributesPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-764


pnf | aai | aaictxbuilder
Verify that the latest aaictxbuilder can query AAI and return the required attributesPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-764


pserver retrieval from A&AI Context Builder


Test CaseDescriptionStatusOwnerDateJIRA linkComment
pserver | aai | aaictxbuilder Verify that the latest aaictxbuilder can query AAI and return the required attributes PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-762


pserver | aai | aaictxbuilderVerify that the latest aaictxbuilder can query AAI and return the required attributes and shown in KibanaPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-762


L2 Fabric Retrieval - p-interface


Test CaseDescriptionStatusOwnerDateJIRA linkComment
p-interface | aai | aaictxbuilderVerify that the latest aaictxbuilder can query AAI and return the required attributesPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-765


L2 Fabric Retrieval - network


Test CaseDescriptionStatusOwnerDateJIRA linkComment

L3-Network | aai | aaictxbuilder

(Service Level)

Verify that the latest aaictxbuilder can query AAI and return the required attributes (uuid,name, attr=networkType, attr=networkRole, attr=networkTechnology). L3-Network data is extracted from AAI data in Service Level.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-763


L3-Network | aai | aaictxbuilder

(VNF Level)

Verify that the latest aaictxbuilder can query AAI and return the required attributes (uuid,name, attr=networkType, attr=networkRole, attr=networkTechnology).L3-Network data is extracted from AAI data in VNF Level.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-763


L3-Network | aai | aaictxbuilder

(V-Module level)

Verify that the latest aaictxbuilder can query AAI and return the required attributes (uuid,name, attr=networkType, attr=networkRole, attr=networkTechnology).L3-Network data is extracted from AAI data in V-Module Level.PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-763


L2 Fabric Retrieval - L-Interface

Test CaseDescriptionStatusOwnerDateJIRA linkComment
aai | l-interface

Verify that the aaictxbuilder can retrieve the following attributes from aai

  • interface-id
  • interface-name
  • interface-role
  • is-port-mirrored
  • prov-status
  • macaddr
  • in-maint
PASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-766

Validation passes, this particular attribute only exists in AAI, so no other builders to compare with

however you can still see the data in kibana as part of other violation payload

aai | l-interface | ctxaggVerify that the ctxAggregator converts the new data and posts to valition based on Common ModelPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-766


Test CaseDescriptionStatusOwnerDateJIRA linkComment
aai | l-interface

Verify that the aaictxbuilder can retrieve the following attributes from aai

PASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-767


aai | l-interface | ctxaggVerify that the ctxAggregator converts the new data and posts to valition based on Common ModelPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-767



POMBA: Cheap and cheerful : continue after error from context builder

Test CaseDescriptionStatusOwnerDateJIRA linkComment
builders | aai | fail to reach aai-ctxBuilderverify that the Context Aggregator can respond to an audit request if aai-ctxBuildercannot be reachedPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-937


builders | sdnc | fail to reach sdnc-ctxBuilderverify that the Context Aggregator can respond to an audit request if sdnc-ctxBuildercannot be reachedPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-937


builders | ndcb | fail to reach ndcb-ctxBuilderverify that the Context Aggregator can respond to an audit request if nd-ctxBuildercannot be reachedPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-937


builders | ndcb | fail to reach sdc-ctxBuilderverify that the Context Aggregator can respond to an audit request if sdc-ctxBuildercannot be reachedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-937


builders | aai | fail to reach aaiverify that the aaictxbuilder can respond to a request with no data if aai cannot be reachedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-937


builders | sdnc | fail to reach sdncverify that the sdncctxbuilder can respond to a request with no data if sdnc cannot be reachedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-937


builders | ndcb | fail to reach service-decompostionverify that the ndcb can respond to a request with no data if service-decomp cannot be reachedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-937


builders | ndcb | fail to reach ndverify that the ndcb can respond to a request with no data if nd cannot be reachedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-937



Network Discovery Context Builder 

Network Discovery - network 


Test CaseDescriptionStatusOwnerDateJIRA linkComment
ndcb | network retrieval

Verify that the network attributes are returned. See https://lf-onap.atlassian.net/wiki/pages/viewpage.action?pageId=16338765 for a list of expected attributes.

Verfify that network lists exist at the service, vfModule and vnf level.

PASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-475


ndcb | network retrieval failureVerify that a failure is returned if the network-id is not found in OpenstackPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keySDNC-475


Port/P-interface; network 

Test CaseDescriptionStatusOwnerDateJIRA linkComment
ndcb | nd | p-interfaceVerify that the ndcb is able to retrieve p-interface information from ndPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-977


ndcb | nd | p-interfaceVerify that the p-interface information retrieved from nd is normalized as per the common modelPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-977


ndcb | nd | p-interfaceVerify that the results as posted to validation contain all the relevant attribute pairs as indicated in common modelPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-977


ndcb | nd | p-interfaceVerify that the audit with the new p-interface can run an e-2-e flow. Note: rules are not in yet for this storyPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-977



Attribute Comparisons

PNF

Test CaseDescriptionStatusOwnerDateJIRA linkComment
pnf | attribute comparison | same nameVerify that the validation can process attribute rule comparison between AAI and SDNCPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-958


pnf | attribute comparison | different nameVerify that the validation can process attribute rule comparison between AAI and SDNCPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-958


pnf | aai | attribute comparison | missing pnf-nameVerify that the validation can process attribute rule comparison between AAI and SDNCPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-958


Network

Test CaseDescriptionStatusOwnerDateJIRA linkComment
network | aai | sdncVerify that the network data returned by the aggregators are comparedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

559

957

data-router | orchestration-initiation | https

network | aai | ndVerify that
an orchestration-event can be published to the data-router over HTTPSPASSDavid Stangl
the network data returned by the aggregators are comparedPASS

Jira Legacy
serverSystem Jira

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

559

957

data-router | orchestration-initiation | https

network | nd | sdncVerify that the network data
-router rejects the orchestration-event if sent via HTTP
returned by the aggregators are comparedPASS
David Stangl

Jira Legacy
serverSystem Jira

columns

key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

559data-router | server-side certificates | httpsThe purpose of the test is to validate that the orchestration-event to data-router can only be successful with server-side certificatesPASSDavid Stangl

957


network | aai | sdnc | ndVerify that all network information is audited and compared using different resources. Note, this is all 3 buildersPASS

Jira Legacy
serverSystem Jira

columns

key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

559data-router | server-side certificatesThe purpose of the test is to validate that the orchestration-event to data-router will be rejected if the server-side certificates are not loadedPASSDavid Stangl

957


network | aai | sdnc | ndVerify that all network information is audited and compared using different resources. Note, this is all 3 buildersPASS

Jira Legacy
serverSystem Jira

columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution

serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

559

Context Builder: SDNC

OOM

Test CaseDescriptionStatusOwnerDateJIRA linkCommentoom deploymentVerify that the SDNC Context Builder is capable of being deployed through OOM.PASSDavid Stangl

957


network | aai | sdnc | ndVerify that all network information is audited and compared using different resources. Note, this is all 3 buildersFAIL

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

426oom deletion Verify that the SDNC Context Builder is capable of being deleted form a POMBA deployment.PASS

957

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

426

SDNC Seed Code w/ Generic Resources API

Test CaseDescriptionStatusOwnerDateJIRA linkCommentcontext aggregator | builders | properties | sdnc.propertiesVerify that the Context Aggregator config/builders/ directory contains an sdnc.properties file upon deployment so that the builder can be utilized in audits.PASSDavid Stangl

1016
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-1017

network | aai | sdnc | ndVerify that all network information is audited and compared using different resources. Note, this is all 3 builders, multi-level (service,vnf,vfmodule)FAIL

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

520sdnccontextbuilder | service | context | basic authVerify that the SDNC Context Builder can successfully process an incoming context request using basic authentication.PASSDavid Stangl

957

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-1016
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

520

1017

sdnccontextbuilder
network |
service
aai |
context | basic auth | bad credentialsVerify that the SDNC Context Builder rejects requests that do not provide the correct credentials.PASSDavid Stangl
sdnc | ndVerify that all network information is audited and compared using different resources. Note, this is all 3 builders, multi-level (service,vnf,vfmodule)FAIL

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

520context aggregator -> sdnc context builderVerify that the Context Aggregator is capable of interoperating with the SDNC Context Builder.PASS

957

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

520sdnc context builder -> sdncVerify that the SDNC Context Builder is capable of interoperating with an SDNC.PASSDavid Stangl

1016
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

520
POMBA APIv1

1017

P-Interface

Test CaseDescriptionStatusOwnerDateJIRA linkComment
sdnccontextbuilder
p-interface |
v1
aai |
service
nd |
context
uuidVerify that the
SDNC Context Builder context API can be called while explicitly referencing the version (v1).PASSDavid Stangl
value returned by aai (equip-identifier) and nd (port id) when same, do not raise a violationPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-959


p-interface | aai | nd | uuidVerify that the value returned by aai (equip-identifier) and nd (port id) when not the same, a violation is raisedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462sdnccontextbuilder | service | context

959


p-interface | aai | nd | nameVerify that
when the API version for the SDNC Context Builder is not explicitly specified, the latest version (APIv1) will be invoked.PASSDavid Stangl
the value returned by aai (interface-name) and nd (name) when same, do not raise a violationPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462

959

sdnccontextbuilder

p-interface |
v1
aai |
service | context | vservers fields
nd | nameVerify that the
SDNC Context Builder can return the full list of required attributes associated with one or more vservers associated with a service instance. The attribute values should be obtained from the correct source attributes.PASSDavid Stangl
value returned by aai (interface-name) and nd (name) when not the same, violation is raisedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462

959

sdnccontextbuilder

p-interface |
v1
aai |
service | context | l3-networks fields
nd | portDescriptionVerify that the
SDNC Context Builder can return the full list of required attributes associated with one or more l3-networks associated with a service instance. The attribute values should be obtained from the correct source attributes.PASSDavid Stangl
value returned by aai (port-description) and nd (description) when same, do not raise a violationPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462sdnccontextbuilder | v1 | service | context | serviceInstanceId missingVerify that the SDNC Context Builder returns a 400 error when the required serviceInstanceID parameter is missing.PASSDavid Stangl

959


p-interface | aai | nd | portDescriptionVerify that the value returned by aai (port-description) and nd (description) when not same, violation is raisedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462

959

sdnccontextbuilder

p-interface |
v1
aai |
service | context | X-TransactionId missing
nd | lockedBooleanVerify that the
SDNC Context Builder is capable of processing a context request that omits the X-TransactionId header.PASSDavid Stangl
value returned by aai (in-maint) and nd (adminStateUp) when same, do not raise a violationFAIL

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462sdnccontextbuilder | v1 | service | context | X-FromAppId missingVerify that the SDNC Context Builder reutrns a 400 error processing a context request that omits the X-FromAppId header.PASS

959

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462

1017

sdnccontextbuilder
p-interface |
v1
aai |
service | context | SDNC not available
nd | lockedBooleanVerify that the
SDNC Context Builder returns a 500 error when the SDNC from which data is to be obtained is not available.PASSDavid Stangl
value returned by aai (in-maint) and nd (adminStateUp) when not same, violation is raisedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462

959

sdnccontextbuilder

p-interface |
v1 | service | context | service not found
aai | ndVerify that the
SDNC Context Builder returns a 404 error when the service instance for which context is requested cannot be located in the SDNC.PASSDavid Stangl
attributes are sent to validation for audit are all present and conform to the correct formatPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462sdnccontextbuilder | logging | success

959



Transaction Tracing

POMBA: Transaction tracing through requestId and partnerName


Test CaseDescriptionStatusOwnerDateJIRA linkComment
Logging | X-ONAP-PartnerName | PresentVerify that
the SDNC Context Builder provides sufficient logging when a context request is successfully processed.David Stangl
when the PartnerName is present in the post, its preserved through the entire flow (i.e with all builders and ms)PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462

551


Logging
for the sdncctxbuilder will be tested on the next phase of the epicsdnccontextbuilder | logging | failure | bad request
X-ONAP-PartnerName | Not PresentVerify that
the SDNC Context Builder provides sufficient logging when a context request is unsuccessfully processed due to a missing parameter.
when the PartnerName is missing in the post, the call is rejectedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462Logging for the sdncctxbuilder will be tested on the next phase of the epicsdnccontextbuilder | v1 | swaggerVerify that the SDNC Context Builder provides swagger documentation for v1 of the Context Builder API.PASSDavid Stangl

551


Logging | X-ONAP-RequestID | PresentVerify that when the RequestId is present in the post, the same ID is maintained throughout the flow (i.e all builders and ms)PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462wiki

551


Logging | X-ONAP-RequestID | Not PresentVerify that
the wiki documentation provides a suitable description of the SDNC Context Builder APIv1.PASSDavid Stangl
when the RequestId is not present it the post, a new one is generated, and maintained through the flowPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

462

API Mapper w/ VNF API

Test CaseDescriptionStatusOwnerDateJIRA linkCommentdefault config | context request | service type | vFWVerify that, using the default configuration, the VNF API is utilized when the SDNC Context Builder detects that the service instance is of type "vFW".PASSDavid Stangl

551


Logging | X-ONAP-PartnerName | KibanaVerify that the PartnerName is visible in KIbanaPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

421

551

default config | context request | service type | vDNS

Logging | X-ONAP-RequestID | KibanaVerify that
, using the default configuration, the VNF API is utilized when the SDNC Context Builder detects that the service instance is of type "vDNS".PASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-421

default config | context request | service type | non-vFW/vDNSVerify that, using the default configuration, the GENERIC-RESOURCE-API is utilized when the SDNC Context Builder detects that the service instance isn't of the type vFW or vDNS.PASSDavid Stangl
the RequestID is visible in KibanaPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-551


Post Orchestration Audit

Reporting - dataQuality


Test CaseDescriptionStatusOwnerDateJIRA linkComment
dataQualitySummary | aaiCtxBuilderVerify that when the audit process cannot reach the aaictxbuilder, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULTindicating fault at the aaiCtxBuilderPASSJ. Ram Balasubramanian

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

421generic-resource-api | common model support | vserverVerify that when the SDNC Context Builder utilizes the Generic Resource API to gather service data, the output is able to pass along all of the mandatory vserver attributes.PASS

665

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-1003
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG

-421generic-resource-api | common model support | l3-network

-1000

dataQualitySummary| aaiVerify that when the
SDNC Context Builder utilizes the Generic Resource API to gather service data, the output is able to pass along all of the mandatory l3-network attributes.PASSDavid Stangl
audit process cannot reach the aai, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the aaiCtxBuilderPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

421rules modificationVerify that the rules used to select which API should be used to gather service data can be changed.PASSDavid Stangl

665


dataQualitySummary| sdncCtxBuilderVerify that when the audit process cannot reach the sdncctxbuilder, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULTindicating fault at the sdncctxbuilderPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

421

665

context request

dataQualitySummary|
aai unavailable
sdncVerify that
an error is returned when the SDNC Context Builder is unable to contact the AAI and cannot, therefore, determine ServiceType for rules mappingPASS
when the audit process cannot reach the sdnc, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the sdncctxbuilderPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-
421developer wikiVerify that the developer wiki has been updated to include information about the API mapping feature in SDNC Context Builder, including how to modify the mapping rulesPASS
665

dataQualitySummary| ndCtxBuilderVerify that when the audit process cannot reach the ndctxbuilder, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the ndCtxBuilderPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

421

POMBA Reporting

https support for Kibana

Test CaseDescriptionStatusOwnerDateJIRA linkCommentoom deploymentVerify that the pomba-kibana dashboard can be deployed via an allowed HTTPS only configurationPASSJ. Ram Balasubramanian

665


dataQualitySummary| ndVerify that when the audit process cannot reach the nd, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the ndCtxBuilderPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

517

oom deployment

Generate new self signed certificate and verify HTTPS connection after deploymentPASSJ. Ram Balasubramanian

665


dataQualitySummary| OpenStackVerify that when the audit process cannot reach the Openstack, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the ndCtxBuilderPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

517kibana dashboard access

665


dataQualitySummary| all OKVerify that
the kibana dashboard can only be accessed via HTTPS when configuredPASSJ. Ram Balasubramanian
when all data is returned by all builders, then dataQuality=OK is reported on Dmaap topic POA-AUDIT-RESULTPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

517kibana dashboard accessVerify that pomba reports are posted and are view-able by KibanaPASSJ. Ram Balasubramanian

665


dataQualitySummary|Verify that even if audit compare(s) fail for any reason, dataQuality shall still report OK as long as all builders returned dataPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-

517

665