POMBA Data Router
HTTPS Support
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| data-router | deployment | https | Verify that the POMBA data-router can be deployed using HTTPS as a configurable parameter. | PASS | LOG-559 - Getting issue details... STATUS | |||
| data-router | orchestration-initiation | https | Verify that an orchestration-event can be published to the data-router over HTTPS | PASS | LOG-559 - Getting issue details... STATUS | |||
| data-router | orchestration-initiation | https | Verify that the data-router rejects the orchestration-event if sent via HTTP | PASS | LOG-559 - Getting issue details... STATUS | |||
| data-router | server-side certificates | https | The purpose of the test is to validate that the orchestration-event to data-router can only be successful with server-side certificates | PASS | LOG-559 - Getting issue details... STATUS | |||
| data-router | server-side certificates | The 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 | PASS | LOG-559 - Getting issue details... STATUS |
Context Builder: SDNC
OOM
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| oom deployment | Verify that the SDNC Context Builder is capable of being deployed through OOM. | PASS | LOG-426 - Getting issue details... STATUS | |||
| oom deletion | Verify that the SDNC Context Builder is capable of being deleted form a POMBA deployment. | PASS | LOG-426 - Getting issue details... STATUS |
SDNC Seed Code w/ Generic Resources API
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| context aggregator | builders | properties | sdnc.properties | Verify that the Context Aggregator config/builders/ directory contains an sdnc.properties file upon deployment so that the builder can be utilized in audits. | PASS | LOG-520 - Getting issue details... STATUS | |||
| sdnccontextbuilder | service | context | basic auth | Verify that the SDNC Context Builder can successfully process an incoming context request using basic authentication. | PASS | LOG-520 - Getting issue details... STATUS | |||
| sdnccontextbuilder | service | context | basic auth | bad credentials | Verify that the SDNC Context Builder rejects requests that do not provide the correct credentials. | PASS | LOG-520 - Getting issue details... STATUS | |||
| context aggregator -> sdnc context builder | Verify that the Context Aggregator is capable of interoperating with the SDNC Context Builder. | PASS | LOG-520 - Getting issue details... STATUS | |||
| sdnc context builder -> sdnc | Verify that the SDNC Context Builder is capable of interoperating with an SDNC. | PASS | LOG-520 - Getting issue details... STATUS |
POMBA APIv1
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| sdnccontextbuilder | v1 | service | context | Verify that the SDNC Context Builder context API can be called while explicitly referencing the version (v1). | PASS | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | service | context | Verify that when the API version for the SDNC Context Builder is not explicitly specified, the latest version (APIv1) will be invoked. | PASS | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | v1 | service | context | vservers fields | Verify 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 | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | v1 | service | context | l3-networks fields | Verify 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 | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | v1 | service | context | serviceInstanceId missing | Verify that the SDNC Context Builder returns a 400 error when the required serviceInstanceID parameter is missing. | PASS | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | v1 | service | context | X-TransactionId missing | Verify that the SDNC Context Builder is capable of processing a context request that omits the X-TransactionId header. | PASS | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | v1 | service | context | X-FromAppId missing | Verify that the SDNC Context Builder reutrns a 400 error processing a context request that omits the X-FromAppId header. | PASS | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | v1 | service | context | SDNC not available | Verify that the SDNC Context Builder returns a 500 error when the SDNC from which data is to be obtained is not available. | PASS | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | v1 | service | context | service not found | Verify 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 | LOG-462 - Getting issue details... STATUS | |||
| sdnccontextbuilder | logging | success | Verify that the SDNC Context Builder provides sufficient logging when a context request is successfully processed. | LOG-462 - Getting issue details... STATUS | Logging for the sdncctxbuilder will be tested on the next phase of the epic | |||
| sdnccontextbuilder | logging | failure | bad request | Verify that the SDNC Context Builder provides sufficient logging when a context request is unsuccessfully processed due to a missing parameter. | LOG-462 - Getting issue details... STATUS | Logging for the sdncctxbuilder will be tested on the next phase of the epic | |||
| sdnccontextbuilder | v1 | swagger | Verify that the SDNC Context Builder provides swagger documentation for v1 of the Context Builder API. | PASS | LOG-462 - Getting issue details... STATUS | |||
| wiki | Verify that the wiki documentation provides a suitable description of the SDNC Context Builder APIv1. | PASS | LOG-462 - Getting issue details... STATUS |
API Mapper w/ VNF API
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| default config | context request | service type | vFW | Verify 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 | LOG-421 - Getting issue details... STATUS | |||
| default config | context request | service type | vDNS | Verify 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 | LOG-421 - Getting issue details... STATUS | |||
| default config | context request | service type | non-vFW/vDNS | Verify 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 | LOG-421 - Getting issue details... STATUS | |||
| generic-resource-api | common model support | vserver | Verify 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 | LOG-421 - Getting issue details... STATUS | |||
| generic-resource-api | common model support | l3-network | Verify 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 | LOG-421 - Getting issue details... STATUS | |||
| rules modification | Verify that the rules used to select which API should be used to gather service data can be changed. | PASS | LOG-421 - Getting issue details... STATUS | |||
| context request | aai unavailable | Verify that an error is returned when the SDNC Context Builder is unable to contact the AAI and cannot, therefore, determine ServiceType for rules mapping | PASS | LOG-421 - Getting issue details... STATUS | |||
| developer wiki | Verify 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 rules | PASS | LOG-421 - Getting issue details... STATUS |
L2 Fabric Retrieval - network
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| network | sdnc| SDNCctxbuilder | Generic-API | Verify that the latest sdncctxbuilder can query SDNC and return the required attributes | PASS | LOG-768 - Getting issue details... STATUS | |||
| network | sdnc| SDNCctxbuilder | VNF-API | Verify that the latest sdncctxbuilder can query SDNC and return the required attributes | FAIL | LOG-768 - Getting issue details... STATUS | LOG-968 - Getting issue details... STATUS |
L2 Fabric Retrieval - pnf
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
network | sdnc| SDNCctxbuilder| Generic-API | Verify that the latest sdncctxbuilder can query SDNC and return the required attributes | PASS | J. Ram Balasubramanian | LOG-778 - Getting issue details... STATUS |
POMBA Reporting
https support for Kibana
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| oom deployment | Verify that the pomba-kibana dashboard can be deployed via an allowed HTTPS only configuration | PASS | J. Ram Balasubramanian | LOG-517 - Getting issue details... STATUS | ||
oom deployment | Generate new self signed certificate and verify HTTPS connection after deployment | PASS | J. Ram Balasubramanian | LOG-517 - Getting issue details... STATUS | ||
| kibana dashboard access | Verify that the kibana dashboard can only be accessed via HTTPS when configured | PASS | J. Ram Balasubramanian | LOG-517 - Getting issue details... STATUS | ||
| kibana dashboard access | Verify that pomba reports are posted and are view-able by Kibana | PASS | J. Ram Balasubramanian | LOG-517 - Getting issue details... STATUS |
A&AI Context Builder
L2 Fabric Retrieval - PNF
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| pnf | aai | aaictxbuilder | Verify that the latest aaictxbuilder can query AAI and return the required attributes | PASS | J. Ram Balasubramanian | LOG-764 - Getting issue details... STATUS | ||
pnf | aai | aaictxbuilder | Verify that the latest aaictxbuilder can query AAI and return the required attributes | PASS | J. Ram Balasubramanian | LOG-764 - Getting issue details... STATUS |
pserver retrieval from A&AI Context Builder
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| pserver | aai | aaictxbuilder | Verify that the latest aaictxbuilder can query AAI and return the required attributes | PASS | LOG-762 - Getting issue details... STATUS | |||
| pserver | aai | aaictxbuilder | Verify that the latest aaictxbuilder can query AAI and return the required attributes and shown in Kibana | PASS | J. Ram Balasubramanian | LOG-762 - Getting issue details... STATUS |
L2 Fabric Retrieval - p-interface
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| p-interface | aai | aaictxbuilder | Verify that the latest aaictxbuilder can query AAI and return the required attributes | PASS | J. Ram Balasubramanian | LOG-765 - Getting issue details... STATUS |
L2 Fabric Retrieval - network
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
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 | LOG-763 - Getting issue details... STATUS | |||
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 | LOG-763 - Getting issue details... STATUS | |||
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 | LOG-763 - Getting issue details... STATUS |
POMBA: Cheap and cheerful : continue after error from context builder
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| builders | aai | fail to reach aai-ctxBuilder | verify that the Context Aggregator can respond to an audit request if aai-ctxBuildercannot be reached | PASS | J. Ram Balasubramanian | LOG-937 - Getting issue details... STATUS | ||
| builders | sdnc | fail to reach sdnc-ctxBuilder | verify that the Context Aggregator can respond to an audit request if sdnc-ctxBuildercannot be reached | PASS | J. Ram Balasubramanian | LOG-937 - Getting issue details... STATUS | ||
| builders | ndcb | fail to reach ndcb-ctxBuilder | verify that the Context Aggregator can respond to an audit request if nd-ctxBuildercannot be reached | PASS | J. Ram Balasubramanian | LOG-937 - Getting issue details... STATUS | ||
| builders | ndcb | fail to reach sdc-ctxBuilder | verify that the Context Aggregator can respond to an audit request if sdc-ctxBuildercannot be reached | PASS | LOG-937 - Getting issue details... STATUS | |||
| builders | aai | fail to reach aai | verify that the aaictxbuilder can respond to a request with no data if aai cannot be reached | PASS | LOG-937 - Getting issue details... STATUS | |||
| builders | sdnc | fail to reach sdnc | verify that the sdncctxbuilder can respond to a request with no data if sdnc cannot be reached | PASS | LOG-937 - Getting issue details... STATUS | |||
| builders | ndcb | fail to reach service-decompostion | verify that the ndcb can respond to a request with no data if service-decomp cannot be reached | PASS | LOG-937 - Getting issue details... STATUS | |||
| builders | ndcb | fail to reach nd | verify that the ndcb can respond to a request with no data if nd cannot be reached | PASS | LOG-937 - Getting issue details... STATUS |
Network Discovery Context Builder
Network Discovery - network
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| 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. | PASS | J. Ram Balasubramanian | SDNC-475 - Getting issue details... STATUS | ||
| ndcb | network retrieval failure | Verify that a failure is returned if the network-id is not found in Openstack | PASS | J. Ram Balasubramanian | SDNC-475 - Getting issue details... STATUS |
Port/P-interface; network
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| ndcb | nd | p-interface | Verify that the ndcb is able to retrieve p-interface information from nd | PASS | LOG-977 - Getting issue details... STATUS | |||
| ndcb | nd | p-interface | Verify that the p-interface information retrieved from nd is normalized as per the common model | PASS | LOG-977 - Getting issue details... STATUS | |||
| ndcb | nd | p-interface | Verify that the results as posted to validation contain all the relevant attribute pairs as indicated in common model | PASS | LOG-977 - Getting issue details... STATUS | |||
| ndcb | nd | p-interface | Verify that the audit with the new p-interface can run an e-2-e flow. Note: rules are not in yet for this story | PASS | LOG-977 - Getting issue details... STATUS |
Attribute Comparisons
PNF
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| pnf | attribute comparison | same name | Verify that the validation can process attribute rule comparison between AAI and SDNC | PASS | LOG-958 - Getting issue details... STATUS | |||
| pnf | attribute comparison | different name | Verify that the validation can process attribute rule comparison between AAI and SDNC | PASS | LOG-958 - Getting issue details... STATUS | |||
| pnf | aai | attribute comparison | missing pnf-name | Verify that the validation can process attribute rule comparison between AAI and SDNC | PASS | LOG-958 - Getting issue details... STATUS |
Network
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| network | aai | sdnc | Verify that the network data returned by the aggregators are compared | PASS | LOG-957 - Getting issue details... STATUS | |||
| network | aai | nd | Verify that the network data returned by the aggregators are compared | PASS | LOG-957 - Getting issue details... STATUS | |||
| network | nd | sdnc | Verify that the network data returned by the aggregators are compared | PASS | LOG-957 - Getting issue details... STATUS | |||
| network | aai | sdnc | nd | Verify that all network information is audited and compared using different resources. Note, this is all 3 builders | PASS | LOG-957 - Getting issue details... STATUS | |||
| network | aai | sdnc | nd | Verify that all network information is audited and compared using different resources. Note, this is all 3 builders | PASS | LOG-957 - Getting issue details... STATUS | |||
| network | aai | sdnc | nd | Verify that all network information is audited and compared using different resources. Note, this is all 3 builders | FAIL | LOG-957 - Getting issue details... STATUS | |||
| network | aai | sdnc | nd | Verify that all network information is audited and compared using different resources. Note, this is all 3 builders, multi-level (service,vnf,vfmodule) | FAIL | LOG-957 - Getting issue details... STATUS | |||
| network | aai | sdnc | nd | Verify that all network information is audited and compared using different resources. Note, this is all 3 builders, multi-level (service,vnf,vfmodule) | FAIL | LOG-957 - Getting issue details... STATUS |
Transaction Tracing
POMBA: Transaction tracing through requestId and partnerName
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| Logging | X-ONAP-PartnerName | Present | Verify that when the PartnerName is present in the post, its preserved through the entire flow (i.e with all builders and ms) | PASS | LOG-551 - Getting issue details... STATUS | |||
| Logging | X-ONAP-PartnerName | Not Present | Verify that when the PartnerName is missing in the post, the call is rejected | PASS | LOG-551 - Getting issue details... STATUS | |||
| Logging | X-ONAP-RequestID | Present | Verify that when the RequestId is present in the post, the same ID is maintained throughout the flow (i.e all builders and ms) | PASS | LOG-551 - Getting issue details... STATUS | |||
| Logging | X-ONAP-RequestID | Not Present | Verify that when the RequestId is not present it the post, a new one is generated, and maintained through the flow | PASS | LOG-551 - Getting issue details... STATUS | |||
| Logging | X-ONAP-PartnerName | Kibana | Verify that the PartnerName is visible in KIbana | PASS | LOG-551 - Getting issue details... STATUS | |||
| Logging | X-ONAP-RequestID | Kibana | Verify that the RequestID is visible in Kibana | PASS | LOG-551 - Getting issue details... STATUS |
Post Orchestration Audit
Reporting - dataQuality
| Test Case | Description | Status | Owner | Date | JIRA link | Comment |
|---|---|---|---|---|---|---|
| dataQualitySummary | aaiCtxBuilder | Verify that when the audit process cannot reach the aaictxbuilder, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULTindicating fault at the aaiCtxBuilder | PASS | J. Ram Balasubramanian | LOG-665 - Getting issue details... STATUS | ||
| dataQualitySummary| aai | Verify that when the audit process cannot reach the aai, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the aaiCtxBuilder | PASS | LOG-665 - Getting issue details... STATUS | |||
| dataQualitySummary| sdncCtxBuilder | Verify that when the audit process cannot reach the sdncctxbuilder, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULTindicating fault at the sdncctxbuilder | PASS | LOG-665 - Getting issue details... STATUS | |||
| dataQualitySummary| sdnc | Verify that when the audit process cannot reach the sdnc, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the sdncctxbuilder | PASS | LOG-665 - Getting issue details... STATUS | |||
| dataQualitySummary| ndCtxBuilder | Verify that when the audit process cannot reach the ndctxbuilder, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the ndCtxBuilder | PASS | LOG-665 - Getting issue details... STATUS | |||
| dataQualitySummary| nd | Verify that when the audit process cannot reach the nd, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the ndCtxBuilder | PASS | LOG-665 - Getting issue details... STATUS | |||
| dataQualitySummary| OpenStack | Verify that when the audit process cannot reach the Openstack, dataQuality=error is reported in Dmaap topic POA-AUDIT-RESULT indicating fault at the ndCtxBuilder | PASS | LOG-665 - Getting issue details... STATUS | |||
| dataQualitySummary| all OK | Verify that when all data is returned by all builders, then dataQuality=OK is reported on Dmaap topic POA-AUDIT-RESULT | PASS | LOG-665 - Getting issue details... STATUS | |||
| dataQualitySummary| | Verify that even if audit compare(s) fail for any reason, dataQuality shall still report OK as long as all builders returned data | PASS | LOG-665 - Getting issue details... STATUS |