Versions Compared

Key

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

Table of Contents
maxLevel2

POMBA Data Router

HTTPS Support



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
data-router | deployment | httpsoom deploymentVerify that the POMBA data-router can be deployed using HTTPS as a configurable parameterSDNC Context Builder is capable of being deployed through OOM.PASS

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

data-router | orchestration-initiation | https

426


oom deletion Verify that an orchestration-event can be published to the data-router over HTTPSthe SDNC Context Builder is capable of being deleted form a POMBA deployment.PASS

Jira Legacy
serverSystem Jiracolumnskey,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 HTTP

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 Jiracolumnskey,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 certificates

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 Jiracolumnskey,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 loaded

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 Jiracolumnskey,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 deployment

520


context aggregator -> sdnc context builderVerify that the SDNC Context Builder Aggregator is capable of being deployed through OOMinteroperating with the SDNC Context Builder.PASS

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

oom deletion 

520


sdnc context builder -> sdncVerify that the SDNC Context Builder is capable of being deleted form a POMBA deploymentinteroperating with an SDNC.PASS

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

SDNC Seed Code w/ Generic Resources API

520


POMBA APIv1

sdnccontextbuilder | service | context | basic auth
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.PASS

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

OwnerDateJIRA linkComment
sdnccontextbuilder | v1 | service | contextVerify that the SDNC Context Builder can successfully process an incoming context request using basic authenticationcontext API can be called while explicitly referencing the version (v1).PASS

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


sdnccontextbuilder | service | context | basic auth | bad credentialsVerify that when the API version for the SDNC Context Builder rejects requests that do not provide the correct credentialsis not explicitly specified, the latest version (APIv1) will be invoked.PASS

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

context aggregator -> sdnc context builder

462


sdnccontextbuilder | v1 | service | context | vservers fieldsVerify that the Context Aggregator is capable of interoperating with the SDNC Context BuilderSDNC 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-520

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

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-520

POMBA APIv1

Comment v1 | service | context | X-TransactionId missing is capable of processing that omits the X-TransactionId headerLOG-462 v1 service | context | X-FromAppId missing reutrns a 400 error processing that omits the X-FromAppId header.
Test CaseDescriptionStatusOwnerDateJIRA link

462


sdnccontextbuilder | v1 | service | context | serviceInstanceId missingVerify that the SDNC Context Builder context API can be called while explicitly referencing the version (v1)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 when the API version for the SDNC Context Builder is not explicitly specified, the latest version (APIv1) will be invokedcapable 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 | vservers fieldsX-FromAppId missingVerify 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 attributesreutrns 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 | l3-networks fieldsSDNC not availableVerify 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 attributesreturns 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 | serviceInstanceId missingservice not foundVerify that the SDNC Context Builder returns a 400 404 error when the required serviceInstanceID parameter is missingservice 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.PASS

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

LOG-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 PASSis 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 | service | context | SDNC not availableswaggerVerify that the SDNC Context Builder returns a 500 error when the SDNC from which data is to be obtained is not availableprovides swagger documentation for v1 of the Context Builder API.PASS

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


sdnccontextbuilder | v1 | service | context | service not foundwikiVerify that the wiki documentation provides a suitable description of the SDNC Context Builder returns a 404 error when the service instance for which context is requested cannot be located in the SDNCAPIv1.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.


API Mapper w/ VNF API

462462
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-

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

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-

Logging 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

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-462

wiki

421


generic-resource-api | common model support | vserverVerify that the wiki documentation provides a suitable description of the SDNC Context Builder APIv1when 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-462

API Mapper w/ VNF API

David Stangl
Test CaseDescriptionStatusOwnerDateJIRA linkComment
default config | context request | service type | vFWVerify that, using the default configuration, the VNF API is utilized

421


generic-resource-api | common model support | l3-networkVerify that when the SDNC Context Builder detects that the service instance is of type "vFW"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


default config | context request | service type | vDNSrules modificationVerify that , using the default configuration, the VNF API is utilized when the SDNC Context Builder detects that the service instance is of type "vDNS"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


default config | context request | service type | non-vFW/vDNS| aai unavailableVerify that , using the default configuration, the GENERIC-RESOURCE-API is utilized an error is returned when the SDNC Context Builder detects that the service instance isn't of the type vFW or vDNS.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


generic-resource-api | common model support | vserverdeveloper wikiVerify that when the the developer wiki has been updated to include information about the API mapping feature in 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., including how to modify the mapping rulesPASS

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

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-

421rules modification

768


network | sdnc| SDNCctxbuilder | VNF-APIVerify that the
rules used to select which API should be used to gather service data can be changed.PASSDavid Stangl
latest sdncctxbuilder can query SDNC and return the required attributes FAIL

Jira Legacy
serverSystem Jira
serverId

4733707d-2057-3a0f-ae5e-4fd8aff50176keyLOG-421context 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 mappingPASSDavid Stangl

4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-768

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 rulesPASSDavid Stangl

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-

421
L2 Fabric Retrieval - network

778



POMBA Reporting

https support for Kibana

Test CaseDescriptionStatusOwnerDateJIRA linkComment
network | sdnc| SDNCctxbuilder | Generic-API
oom deploymentVerify that the
latest sdncctxbuilder can query SDNC and return the required attributes
pomba-kibana dashboard can be deployed via an allowed HTTPS only configurationPASSJ. Ram Balasubramanian

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

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

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-

768

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-

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 attributes

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-

778

POMBA Reporting

https support for Kibana

517


A&AI Context Builder

L2 Fabric Retrieval - PNF

Test CaseDescriptionStatusOwnerDateJIRA linkComment
oom deployment
pnf | aai | aaictxbuilderVerify that the
pomba-kibana dashboard can be deployed via an allowed HTTPS only configuration
latest aaictxbuilder can query AAI and return the required attributesPASSJ. 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 deployment

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-

517kibana dashboard access

764


pserver retrieval from A&AI Context Builder


Test CaseDescriptionStatusOwnerDateJIRA linkComment
pserver | aai | aaictxbuilder Verify that the
kibana dashboard can only be accessed via HTTPS when configured
latest aaictxbuilder can query AAI and return the required attributes PASS

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

517kibana dashboard accessVerify that pomba reports are posted and are view-able by

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-

517
A&AI Context Builder

762


L2 Fabric Retrieval - p-

PNF

interface


Test CaseDescriptionStatusOwnerDateJIRA linkComment
pnf
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

-764
pnf | aai | aaictxbuilder
Verify that the latest aaictxbuilder can query AAI and return the required attributes

-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-

764

pserver retrieval from A&AI Context Builder

Test CaseDescriptionStatusOwnerDateJIRA linkCommentpserver

763


L3-Network | aai | aaictxbuilder

(VNF Level)

Verify that the latest aaictxbuilder can query
AAI and return the required attributes
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-

762

763

pserver

L3-Network | aai | aaictxbuilder

(V-Module level)

Verify that the latest aaictxbuilder can query AAI and return the required attributes
and shown in Kibana
(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-

762L2 Fabric Retrieval - p-interface

763



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

Test CaseDescriptionStatusOwnerDateJIRA linkComment
p-interface
builders | aai |
aaictxbuilderVerify that the latest aaictxbuilder can query AAI and return the required attributes
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-

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.

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-

763

937

L3-Network

builders |
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.
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-

763

937

L3-Network

builders |
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.
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-

763

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

Test CaseDescriptionStatusOwnerDateJIRA linkComment

937


builders | aai | fail to reach aai-ctxBuilderverify that the Context Aggregator aaictxbuilder can respond to an audit a request with no data if aai -ctxBuilder cannot be reachedPASS

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


builders | sdnc | fail to reach sdnc-ctxBuilderverify that the Context Aggregator can the sdncctxbuilder can respond to an audit a request with no data if sdnc -ctxBuildercannot cannot be reachedPASS

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


builders | ndcb | fail to reach ndcbservice-ctxBuilderdecompostionverify that the Context Aggregator the ndcb can respond to an audit request if nd-ctxBuildera 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 sdc-ctxBuilderndverify that the Context Aggregator the ndcb can respond to an audit a request if sdc-ctxBuilderwith no data if nd cannot be reachedPASS
verify that the aaictxbuilder can respond to a request with no data if aai cannot be reached

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

builders | aai | fail to reach aai

-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://wiki.onap.org/pages/viewpage.action?pageId=48534037 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
keyLOGSDNC-937475


builders | sdnc | fail to reach sdncverify that the sdncctxbuilder can respond to a request with no data if sdnc cannot be reachedndcb | network retrieval failureVerify that a failure is returned if the network-id is not found in OpenstackPASSJ. Ram Balasubramanian
verify that the ndcb can respond to a request with no data if service-decomp cannot be reached

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

builders | ndcb | fail to reach service-decompostion

SDNC-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-

937

977

builders |

ndcb |
fail to reach ndverify that the ndcb can respond to a request with no data if nd cannot be reached
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-

937

Network Discovery Context Builder 

Network Discovery - network 

Test CaseDescriptionStatusOwnerDateJIRA linkCommentndcb | network retrieval

Verify that the network attributes are returned. See https://wiki.onap.org/pages/viewpage.action?pageId=48534037 for a list of expected attributes.

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

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
key

SDNC

LOG-

475

977


ndcb
| network retrieval failure
| nd | p-interfaceVerify that
a failure is returned if the network-id is not found in Openstack
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
key

SDNC

LOG-

475

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-957


network | aai | ndVerify that the network data returned by the aggregators are comparedPASS

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


network | nd | sdncVerify that the network data returned by the aggregators are comparedPASS

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-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
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-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-957

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-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-957

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyLOG-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-957

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