Skip to end of metadata
Go to start of metadata


Context Aggregator


Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploy context aggregator Micro ServiceVerify context aggregator MS starts up without errorPASS

LOG-519 - Getting issue details... STATUS


Consume audit event from “event bus” (message router)Verify audit event is consumed by POMBA-CA and is processed successfully
PASS

LOG-519 - Getting issue details... STATUS


Retrieve model data for all underlying context builders

Verify POMBA-CA is able to retrieve model data if all of the .properties files for all of the context builders exist in config/builders directory

Verify all of the underlying context builders receive a ‘Get context” request from POMBA-CA


Verify a response is received at POMBA-CA from all under lying context builders

PASS

LOG-519 - Getting issue details... STATUS


Unable to retrieve model data | Malformed .properties file for at least one of the underlying context buildersVerify POMBA-CA is unable to retrieve model data if one of the .properties files for a context builder (e.g. aai.properties) is misconfiguredPASS

LOG-519 - Getting issue details... STATUS


Unable to retrieve model data | Missing .properties file for a context builderVerify POMBA-CA is unable to retrieve model data if one of the .properties files for a context builder (e.g. aai.properties) is missing from config/builders directoryPASS

LOG-519 - Getting issue details... STATUS


Context Aggregator - OOM

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploy Context Aggregator in OOMVerify that the Context Aggregator can be deployed in a Kubernetes environmentPASS

LOG-422 - Getting issue details... STATUS


Login to the Context Aggregator pod and ensure it is runningVerify that the Context Aggregator pod is reachable and Context Aggregator is runningPASS
LOG-422 - Getting issue details... STATUS
Delete the deployed Context Aggregator from OOMVerify that the Context Aggregator pod can be deleted by using the standard OOM deletion instructionPASS

LOG-422 - Getting issue details... STATUS



Context Aggregator - Latest POMBA API

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Ensure the response from the Network Discovery Context Builder align with Common Model v.1

Verify the response from Network Discovery Context Builder is using Common Model v.1


Verify all of the underlying context builders receive a ‘Get context” request from POMBA-CA with the following 3 parameters: ServiceInstanceIdmodelVersionId, and modelInvariantId

PASS

LOG-439 - Getting issue details... STATUS


Ensure the response from the Network Discovery Context Builder align with Common Model v.1Verify the response from Network Discovery Context Builder is using Common Model v.1PASS

LOG-439 - Getting issue details... STATUS


Ensure the response from the Network Discovery Context Builder align with Common Model v.1

Verify the response from Network Discovery Context Builder is using Common Model v.1

PASS

LOG-439 - Getting issue details... STATUS


Verify XFromAppId is needed in the Event
  • Verify POMBA-CA is able to retrieve model data from Network Discovery context builder
  • Verify the Network Discovery context builder receives a ‘Get context” request from POMBA-CA
  • Verify a response is received at POMBA-CA from Network Discovery context builder
PASS

LOG-439 - Getting issue details... STATUS


Verify xTransactionId is needed in the Event
  • Verify POMBA-CA is able to retrieve model data from Network Discovery context builder
  • Verify the Network Discovery context builder receives a ‘Get context” request from POMBA-CA
  • Verify a response is received at POMBA-CA from Network Discovery context builder
PASS

LOG-439 - Getting issue details... STATUS


Verify customerId is not a mandatory attributes in the Even
  • Verify POMBA-CA is able to retrieve model data from Network Discovery context builder
  • Verify the Network Discovery context builder receives a ‘Get context” request from POMBA-CA
  • Verify a response is received at POMBA-CA from Network Discovery context builder
PASS

LOG-439 - Getting issue details... STATUS


Verify serviceType is not a mandatory attributes in the Even
  • Verify POMBA-CA is able to retrieve model data from Network Discovery context builder
  • Verify the Network Discovery context builder receives a ‘Get context” request from POMBA-CA
  • Verify a response is received at POMBA-CA from Network Discovery context builder
PASS

LOG-439 - Getting issue details... STATUS


Retrieve model data for Network Discovery context builder
  • Verify POMBA-CA is able to retrieve model data from Network Discovery context builder
  • Verify the Network Discovery context builder receives a ‘Get context” request from POMBA-CA
  • Verify a response is received at POMBA-CA from Network Discovery context builder
PASS

LOG-439 - Getting issue details... STATUS



Context Builder: AAI

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploy MSVerify AAI Context Builder MS starts up without errorPASSDavid Stangl

LOG-521 - Getting issue details... STATUS


success pathVerify that the AAI Context Builder service is able to process an incoming context request.PASS

LOG-521 - Getting issue details... STATUS


bad credentialsVerify that the AAI Context Builder service fails to process a context request from a sender that cannot be authenticated. An error response should be returned to the Context Aggregator.PASS

LOG-521 - Getting issue details... STATUS


sonar reportVerify that the AAI Context Builder service Sonar report does not include any critical level issues that need to be resolved.PASS

LOG-521 - Getting issue details... STATUS


wiki updateVerify that the ONAP developer wiki has been updated to include pertinent information for the development and usage of the AAI Context Builder.PASS

LOG-521 - Getting issue details... STATUS


Context Builder: AAI - OOM

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploy AAI Context Builder in OOMVerify that the AAI Context Builder can be deployed in a Kubernetes environmentPASS

LOG-425 - Getting issue details... STATUS


Login to the AAI Context Builder pod and ensure it is runningVerify that the AAI Context Builder pod is reachable and SDC Context Builder is runningPASS

LOG-425 - Getting issue details... STATUS


Delete the deployed AAi Context Builder from OOMVerify that the AAI Context Builder pod can be deleted by using the standard OOM deletion instructionPASS

LOG-425 - Getting issue details... STATUS



Context Builder: AAI - APIv1 Update

Test CaseDescriptionStatusOwnerDateJIRA linkComment
aai-context-builder | service | context | successVerify that the AAI Context Builder is capable of receiving a context request that includes only the serviceInstanceId parameter.PASS
LOG-461 - Getting issue details... STATUS



aai-context-builder | service | v1 | contextVerify that the AAI Context Builder is able to accept context requests that explicitly specify v1 of the API.PASS

LOG-461 - Getting issue details... STATUS


aai-context-builder | swagger | index.htmlVerify that the AAI Context Builder provides swagger documentation for the latest API (v1).FAIL

LOG-461 - Getting issue details... STATUS

Bug entered:

LOG-687 - Getting issue details... STATUS

aai-context-builder | service | context | missing serviceInstanceIdVerify that the AAI Context Builder service will fail to process a context request that does not provide a service-Instance-Id. An error response should be returned to the Context Aggregator.PASS

LOG-461 - Getting issue details... STATUS


aai-context-builder | service | context | header | missing application idVerify that the AAI Context Builder service will fail to process a context request that does not provide an AppId in the header. An error response should be returned to the Context Aggregator.PASS

LOG-461 - Getting issue details... STATUS


aai-context-builder | service | context | service not in AAIVerify that the AAI Context Builder service returns a suitable response when the service for which context is requested cannot be found in the A&AI database.

LOG-461 - Getting issue details... STATUS



Context Builder: SDC

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploying SDC context builder serviceVerify that SDC context builder can be deployed (manually)PASS

LOG-522 - Getting issue details... STATUS


Send API request to SDC context builderVerify that an API request can be sent to SDC context builderPASS

LOG-522 - Getting issue details... STATUS


Send API request to SDC context builder with error in modelVersionIdVerify that an error occurs when the null value or missing modelVersionIdPASS
LOG-522 - Getting issue details... STATUS
Send API request to SDC context builder - missing AppId from the headerVerify that missing parameter returns proper error code in responsePASS
LOG-522 - Getting issue details... STATUS
Send API request to SDC context builder - missing basic auth from the headerVerify that missing parameter returns proper error code in responsePASS
LOG-522 - Getting issue details... STATUS
Check sonar reportVerify that no critical sonar issuesPASS
LOG-522 - Getting issue details... STATUS
Review wiki pageVerify that the ONAP developer wiki has been updated with information regarding the SDC Builder.PASS

LOG-522 - Getting issue details... STATUS


Context Builder: SDC - OOM

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploy SDC Context Builder in OOMVerify that the SDC Context Builder can be deployed in a Kubernetes environmentPASS

LOG-424 - Getting issue details... STATUS


Login to the SDC Context Builder pod and ensure it is runningVerify that the SDC Context Builder pod is reachable and SDC Context Builder is runningPASS

LOG-424 - Getting issue details... STATUS


Delete the deployed SDC Context Builder from OOMVerify that the SDC Context Builder pod can be deleted by using the standard OOM deletion instructionPASS

LOG-424 - Getting issue details... STATUS



Context Builder: SDC - APIv1 Update

Test CaseDescriptionStatusOwnerDateJIRA linkComment
Deploy SDC Context Builder in OOMVerify that the SDC Context Builder can be deployed in a Kubernetes environmentPass
LOG-448 - Getting issue details... STATUS



SDC-context-builder | service | context | successVerify that the SDC Context Builder is capable of receiving a context request that includes only the modelVersionId parameter.Pass

LOG-448 - Getting issue details... STATUS


api v1 - SDC-context-builder | service |context

ignores extra parameters

Verify that the SDC Context Builder is able to accept context requests that explicitly specify v1 of the API.

API contains parameters extra parameters like serviceType and customerId.

  • That required ones are:modelVersionId, modelInvariantId,serviceInstanceId,XFromApId,xTransactionId
Pass

LOG-448 - Getting issue details... STATUS


api v1 - SDC-context-builder | service | context

do not include serviceType

Verify that the SDC Context Builder is able to accept context requests that explicitly specify v1 of the API.

Absence of serviceType should not cause problem.

Pass

LOG-448 - Getting issue details... STATUS


api v1 - SDC-context-builder | service | context

do not include customerId

Verify that the SDC Context Builder is able to accept context requests that explicitly specify v1 of the API.

Absence of customerId should not cause problem.

Pass

LOG-448 - Getting issue details... STATUS


SDC-context-builder | swagger | index.htmlVerify that the SDC Context Builder provides swagger documentation for the latest API (v1).FAIL

LOG-448 - Getting issue details... STATUS

Defect entered:

LOG-699 - Getting issue details... STATUS


SDC-context-builder | service | context | missing modelVersionIdVerify that the SDC Context Builder service will fail to process a context request that does not provide a service-Instance-Id. An error response should be returned to the Context Aggregator.Pass

LOG-448 - Getting issue details... STATUS


SDC-context-builder | service | context | model version id not in SDCVerify that the SDC Context Builder service returns a suitable response when the service for which context is requested cannot be found in SDC.Pass

LOG-448 - Getting issue details... STATUS


Context Builder: Network Discovery

Test CaseDescriptionStatusOwnerDateJIRA linkComment
api | network-discovery-context-builder | service | context | decomposition requestVerify that the Network Discovery Context Builder generates a service instance decomposition action when it is sent a POMBA request from the Context Aggregator. The decomposition request should utilize the proper credentials.PASS

LOG-401 - Getting issue details... STATUS


api v1 | network-discovery-context-builder | service | context | decomposition request

Verify that the Network Discovery Context Builder generates a service instance decomposition action when it is sent a POMBA request from the Context Aggregator. The decomposition request should utilize the proper credentials.

The request includes new API v2 headers.

PASS

LOG-401 - Getting issue details... STATUS


api v1 | network-discovery-context-builder | service | context | ignores extra parametersVerify that the Network Discovery Context Builder accepts a request that contains more query parameters than required (context-aggregator may send other parameters like modelVersionId and modelInvariantId).PASS

LOG-401 - Getting issue details... STATUS


api v1 | network-discovery-context-builder | service | context | no X-ONAP-PartnerNameVerify that the Network Discovery Context Builder returns an error to the Context Aggregator when its request does not include a PartnerName header.PASS

LOG-401 - Getting issue details... STATUS


api v1 | network-discovery-context-builder | service | context | using X-FromAppIdVerify that the Network Discovery Context Builder accepts X-FromAppId in lieu of X-ONAP-PartnerNamePASS

LOG-401 - Getting issue details... STATUS


api v1 | network-discovery-context-builder | service | context | using X-TransactionIdVerify that the Network Discovery Context Builder accepts X-TransactionId in lieu of X-ONAP-RequestIDPASS

LOG-401 - Getting issue details... STATUS


api | network-discovery-context-builder | service | context | bad usernameVerify that the Network Discovery Context Builder API disallows requests when the provided username is not correct.PASS

LOG-401 - Getting issue details... STATUS


api | network-discovery-context-builder | service | context | bad passwordVerify that the Network Discovery Context Builder API disallows requests when the provided password is not correct.PASS

LOG-401 - Getting issue details... STATUS


api | network-discovery-context-builder | service | context | no serviceInstanceIdVerify that the Network Discovery Context Builder returns an error to the Context Aggregator when its request does not include a service instance ID.PASS

LOG-401 - Getting issue details... STATUS


api | network-discovery-context-builder | service | context | service decomposer downVerify that the Network Discovery Context Builder returns an error to the Context Aggregator when an audit request cannot be carried out due to an unresponsive Service Decomposer.PASS

LOG-401 - Getting issue details... STATUS


api | network-discovery-context-builder | service | context | service not in aaiVerify that the Network Discovery Context Builder returns an error to the Context Aggregator when an audit request cannot be carried out due to the specified service not being available in the A&AI database.PASS

LOG-401 - Getting issue details... STATUS


api v2 | network-discovery-context-builder | service | context | X-ONAP-TransactionIdVerify that the Network Discovery Context Builder returns an error to the Context Aggregator when its request does not include a service instance ID.PASS

LOG-401 - Getting issue details... STATUS


logging | network-discovery-context-builder | audit requestVerify that the Network Discovery Context Builder logs appropriate information upon reception of an audit request.PASS

LOG-401 - Getting issue details... STATUS


logging | network-discovery-context-builder | audit request | missing parameterVerify that the Network Discovery Context Builder logs appropriate information upon reception of an audit request that is missing the required service instance ID.PASS

LOG-401 - Getting issue details... STATUS


api | network-discovery-context-builder | service | context | swagger documentationVerify that the micro service API provides a swagger description of the API parameters, versions, etc.PASS

LOG-401 - Getting issue details... STATUS


wiki | developer documentationVerify that the ONAP developer wiki has been updated with information regarding the Network Discovery Context Builder.PASS

LOG-401 - Getting issue details... STATUS


properties file | default resource types
PASS

LOG-401 - Getting issue details... STATUS


properties file | no resource types
PASS

LOG-401 - Getting issue details... STATUS


properties file | unknown resource type
PASS

LOG-401 - Getting issue details... STATUS


properties file | missing resource type
PASS

LOG-401 - Getting issue details... STATUS


Network-discovery-context-builder sends request | To Network Discovery for each resource typeVerify that the Network Discovery Context Builder sends one Network Discovery request for each resource found in the response from the Service Decomposition service.PASS

LOG-401 - Getting issue details... STATUS


Network-discovery-context-builder disallows|unsupported resource typesVerify that the Network Discovery Context Builder is able to produce a final audit report when one (or more) of the resource discovery requests was rejected due to the resource type not being supported. The final report should include error messaging for the unsupported resource types.PASS

LOG-401 - Getting issue details... STATUS


Network-discovery-context-builder | timeout is configurableVerify that the Network Discovery Context Builder timeout is configurable and resource discovery responses will be timeout based on the configured timePASS

LOG-401 - Getting issue details... STATUS


Network-discovery-context-builder disallows| malformed requestVerify that the Network Discovery Context Builder disallows the resource discovery requests and gets rejected due to malformed requestPASS

LOG-401 - Getting issue details... STATUS


Network-discovery-context-builder disallows| missing parameter| ServiceInstanceId and ONAP-PartnerNameVerify that the Network Discovery Context Builder disallows the resource discovery requests and gets rejected due missing ServiceInstanceId and ONAP-ParameterName. The final report should include  proper error codePASS

LOG-401 - Getting issue details... STATUS


Network-discovery-context-builder| Not able to discover resource typeVerify that the Network Discovery Context Builder is able to generate a response back to context aggregator without any  resource type informationPASS

LOG-401 - Getting issue details... STATUS


Network Discovery Context Builder returns failure| Network-Discovery is downVerify that the Network Discovery Context Builder returns a failure response to the Context Aggregator if resource discovery cannot be performed due to the unavailability of the Network Discovery service.The Network Discovery Context Builder disallows to accept a discovery request from the Network Discovery micro service
  • Response back should be 400 missing parameters
PASS

LOG-401 - Getting issue details... STATUS


Network-discovery-context-builder disallows request | when network-discovery credentials incorrect or missingVerify that the Network Discovery Context Builder returns an error when network-discovery credentials are incorrectPASS

LOG-401 - Getting issue details... STATUS


logging | network-discovery-context-builder | audit requestVerify that the Network Discovery Context Builder logs appropriate information when receiving the service decomposition response and generating resource discovery requests.PASS

LOG-401 - Getting issue details... STATUS


logging | network-discovery-context-builder | audit requestVerify that the Network Discovery Context Builder logs appropriate information when receiving resource discovery results.PASS

LOG-401 - Getting issue details... STATUS


wiki | developer documentationVerify that the ONAP developer wiki has been updated with information regarding the "discovery" part of the Network Discovery Context Builder.PASS

LOG-401 - Getting issue details... STATUS


Context Builder: Network Discovery - OOM

Test CaseDescriptionStatusOwnerDateJIRA linkComment
oom | install | network discovery context builderVerify that the Network Discovery Context Builder can be deployed using OOM.PASSDavid Stangl



OOM-1320 - Getting issue details... STATUS



Service Decomposition


Test CaseDescriptionStatusOwnerDateJIRA linkComment
GET A&AI service instance details - success scenarioVerify that A&AI data is populated  correctlyPASS

LOG-397 - Getting issue details... STATUS


GET A&AI service instance details - missing parameter(AppId)Verify that missing parameter returns proper error code in responsePASS

LOG-397 - Getting issue details... STATUS


GET A&AI service instance details - missing parameter(serviceInstanceId)Verify that missing parameter returns empty json responsePASS
LOG-397 - Getting issue details... STATUS

GET A&AI service instance details - invalid parameter(serviceInstanceId)Verify that missing parameter returns proper error code in responsePASS
LOG-397 - Getting issue details... STATUS

Malformed GET Request to fetch the dataVerify that malformed GET request returns proper error code in responsePASS
LOG-397 - Getting issue details... STATUS

service-decomposition | service includes VNFsVerify that VNF resources that comprise a services can be returned by the service decomposition micro service.PASS
LOG-397 - Getting issue details... STATUS

service-decomposition | service includes VNFCsVerify that VNFC resources that comprise a services can be returned by the service decomposition micro service.PASS
LOG-397 - Getting issue details... STATUS

service-decomposition | service includes VFModulesVerify that VFModule resources that comprise a services can be returned by the service decomposition micro service.PASS
LOG-397 - Getting issue details... STATUS

service-decomposition | service includes VServersVerify that VServer resources that comprise a services can be returned by the service decomposition micro service.PASS
LOG-397 - Getting issue details... STATUS

service-decomposition | service includes L3 networkVerify that L3 network resources that comprise a services can be returned by the service decomposition micro service.PASS
LOG-397 - Getting issue details... STATUS

GET Generic VNF output for supported resources with different combinations of the dataVerify that all supported resource types should be populated in correct hierarchyPASS
LOG-397 - Getting issue details... STATUS

service-decomposition | interrelated resources don't result in redundancy or unrelated service resourcesVerify that the service decomposition micro service returns only components directly related to the service and does not return duplicate components when the components are related to each other recursively.PASS
LOG-397 - Getting issue details... STATUS

service-decomposition | service not foundVerify that the service decomposition micro service returns an error code and message when the service that is requested cannot be located.PASS
LOG-397 - Getting issue details... STATUS

service-decomposition | X-ONAP-RequestID not specifiedVerify that the service decomposition micro service generates a unique transaction ID when one had not been specified in the request.FAIL

LOG-397 - Getting issue details... STATUS

X-ONAP-RequestID not generated by microservice. Not so much an issue because the only caller currently passes in an ID.

Tracking this issue outside of story.

service-decomposition | X-ONAP-RequestID specifiedVerify that the service decomposition micro service response uses the same unique transaction ID as was specified in the request.FAIL

LOG-397 - Getting issue details... STATUS

X-ONAP-RequestID not returned in response to caller.

Tracking this issue outside of story: LOG-237 - Getting issue details... STATUS

service-decomposition | X-ONAP-PartnerNameVerify that the service decomposition micro service response uses the same unique ONAP partner name as was specified in the request.FAIL

LOG-397 - Getting issue details... STATUS

X-ONAP-PartnerNAme not returned in response to caller.

Tracking this issue outside of story.

service-decomposition | A&AI connection severedVerify that the service decomposition micro service response includes an error code and error message when a lookup fails due to no connection to A&AI.PASS
LOG-397 - Getting issue details... STATUS

service-decomposition | mini-soakVerify that the service decomposition micro service can handle multiple and sometimes concurrent requests for decomposition without causing issue with the process (memory leaks, etc.) or providing callers with bad information (mixing up response content, etc.)PASS

LOG-397 - Getting issue details... STATUS


service-decompoistion | swagger API documentationVerify that the API documentation for the service decomposition micro service is available.PASS

LOG-397 - Getting issue details... STATUS




POMBA Validation Service

Test CaseDescriptionStatusOwnerDateJIRA linkComment
OOM | deploymentVerify that the Validation Service can be deployed in a POMBA environment with all the appropriate configuration, etc.PASS

LOG-427 - Getting issue details... STATUS


OOM | removalVerify that the Validation Service can be undeployed from a POMBA environment.PASS

LOG-427 - Getting issue details... STATUS


pomba-validation-service | RULES-VALIDATION | successVerify that the Validation Service can successfully consume a RULES-VALIDATION event, employ validation rules and return a validation report to the POA-AUDIT-RESULT queue in DMaaP.PASS

LOG-427 - Getting issue details... STATUS


pomba-validation-service | topic creation | POA-AUDIT-RESULTVerify that the Validation Service is able to create the POA-AUDIT-RESULT queue in DMaaP for the purposes of publishing the results of evaluations. This should be done at the time of the very first outgoing DMaaP event.FAIL

LOG-427 - Getting issue details... STATUS

General issue with components writing to DMaaP without an existing topic. Topic is created but message dropped. Subsequent messages are written correctly. Will be dealt with outside of this story.

LOG-659 - Getting issue details... STATUS

sonar reportVerify that the Validation Service Sonar report does not include any critical level issues that need to be resolved.PASS

LOG-427 - Getting issue details... STATUS


POMBA Validation Service - Rules: AAI vs. ND attribute comparison

Test CaseDescriptionStatusOwnerDateJIRA linkComment
aai vs. nd | all attributes | matchVerify that there are no violations reported when the attributes reported by both the AAI Context Builder and Network Discovery Context Builder have the same values.PASS

LOG-434 - Getting issue details... STATUS


aai vs. nd | vm.uuid comparision | mismatchVerify that there is a MAJOR violation reported when the vm.uuid values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.FAIL

LOG-434 - Getting issue details... STATUS

Report is generated but there are some issues:

LOG-682 - Getting issue details... STATUS

aai vs. nd | vm.name comparision | mismatchVerify that there is a MAJOR violation reported when the vm.name values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.FAIL
LOG-434 - Getting issue details... STATUS

Report is generated but there are some issues:

LOG-682 - Getting issue details... STATUS

aai vs. nd | vm.lockedBoolean comparison | mismatchVerify that there is a MAJOR violation reported when the vm.lockedBoolean values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.FAIL
LOG-434 - Getting issue details... STATUS

Report is generated but there are some issues:

LOG-682 - Getting issue details... STATUS

aai vs. nd | vm.hostName comparison | mismatchVerify that there is a MAJOR violation reported when the vm.hostName values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.FAIL
LOG-434 - Getting issue details... STATUS

Report is generated but there are some issues:

LOG-682 - Getting issue details... STATUS

aai vs. nd | vm.imageId comparison | mismatchVerify that there is a MAJOR violation reported when the vm.imageId values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.FAIL
LOG-434 - Getting issue details... STATUS

Report is generated but there are some issues:

LOG-682 - Getting issue details... STATUS

aai vs. nd | vm.name comparision | mismatch | case sensitivityVerify that a mismatch is detected when the value for an attribute is the same but just not expressed in the same case. (e.g. "123fred" vs. "123Fred")FAIL
LOG-434 - Getting issue details... STATUS

Report is generated but there are some issues:

LOG-682 - Getting issue details... STATUS

aai vs. nd | vm.hostName comparison | dataQuality error from nd builderVerify that there is no violation reported when the vm.hostName reported by the Network Discovery Context Builder has an associated dataQuality of "error".PASS
LOG-434 - Getting issue details... STATUS

aai vs. nd | vm.imageIdcomparison | attribute missing from nd builderVerify that there is no violation reported when the Network Discovery Context Builder fails to include a vm.imageId attribute while the AAI Context Builder does.PASS
LOG-434 - Getting issue details... STATUS

aai vs. nd | network.uuid comparison | mismatchVerify that there is a MAJOR violation reported when the network.uuid values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.PASS
LOG-434 - Getting issue details... STATUS

aai vs. nd | network.name comparison | mismatchVerify that there is a MAJOR violation reported when the network.namevalues reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.PASS
LOG-434 - Getting issue details... STATUS

aai vs. nd | network.adminState comparison | mismatchVerify that there is a MAJOR violation reported when the network.adminStatevalues reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.PASS

LOG-434 - Getting issue details... STATUS


aai vs. nd | network.sharedNetworkBoolean comparison | mismatchVerify that there is a MAJOR violation reported when the network.sharedNetworkBoolean values reported by the AAI Context Builder and the Network Discovery Context Builder do not have the same value.PASS

LOG-434 - Getting issue details... STATUS


aai vs. nd | multiple violationsVerify that multiple attribute comparison violations can be reported.PASS

LOG-434 - Getting issue details... STATUS


POMBA Validation Service - Rules: AAI vs. SDC VNF comparison

Test CaseDescriptionStatusOwnerDateJIRA linkComment
SDC and AAI output matchesVerify that the Validation Service does not detect any issues when the SDC and AAI context builders provide the same number of VNFCs, the vnfc-type and vf-module-type for each VNFC match and the AAI provides a nfc-naming-code for each VNFC.PASS

LOG-571 - Getting issue details... STATUS


vnfc-type | mismatchVerify that the Validation Service is able to detect that the vnfc-type for a VNFC as reported by the SDC and AAI context builders does not match. An ERROR level violation should be reported.PASS

LOG-571 - Getting issue details... STATUS


vnfc-count | SDC reports more than AAIVerify that the Validation Service is able to detect when the number of VNFCs reported by the SDC Context Builder is greater than the number of VNFCs reported by the AAI Context Builder. A WARN level violation should be reported.PASS

LOG-571 - Getting issue details... STATUS


vnfc-count | SDC reports fewer than AAIVerify that the Validation Service does not detect a violation when the SDC Context Builder reports fewer VNFCs than the AAI Context Builder.PASS

LOG-571 - Getting issue details... STATUS



POMBA Data Router

Test CaseDescriptionStatusOwnerDateJIRA linkComment
data-router | orchestration-event-service | orchestration-event | success | no transaction IDVerify that the Data Router can successfully process an incoming request and produce a DMaaP event with the information.PASS


LOG-572 - Getting issue details... STATUS


data-router | orchestration-event-service | orchestration-event | success | transaction ID providedVerify that the Data Router can successfully process an incoming request that includes a transaction ID to use.PASS

LOG-572 - Getting issue details... STATUS


data-router | orchestration-event-service | orchestration-event | success | multiple servicesVerifythat the Data Router can successfully process an incoming request and producePASS

LOG-572 - Getting issue details... STATUS


data-router | POA-AUDIT-RESULT | successVerify that the Data Router monitors the DMaaP POA-AUDIT-RESULT queue and is able to process events tat are found, resulting in a request to the SDS.PASS

LOG-572 - Getting issue details... STATUS


data-router | orchestration-event-service | orchestration-event | missing service instance IDVerify that the Data Router rejects an incoming request that does not specify a service instance ID.PASS

LOG-572 - Getting issue details... STATUS


data-router | orchestration-event-service | orchestration-event | missing model version IDVerify that the Data Router rejects an incoming request that does not specify a service instance ID.PASS

LOG-572 - Getting issue details... STATUS


data-router | orchestration-event-service | orchestration-event | DMaaP not availableVerify that the Data Router responds with an error code when the DMaaP service is not accessible when a request is being processed.PASS

LOG-572 - Getting issue details... STATUS


data-router | POA-AUDIT-RESULT | malformed eventVerify that the Data Router fails gracefully when a POA-AUDIT-RESULT event is being processed but the content of the event prevents proper processing.PASS

LOG-572 - Getting issue details... STATUS


data-router | POA-AUDIT-RESULT | SDS not availableVerify that the Data Router fails gracefully when a POA-AUDIT-RESULT event is being processed and the SDS is not available to receive requests.PASS

LOG-572 - Getting issue details... STATUS


data-router | orchestration-event-service | orchestration-event | bad certificateVerify that the Data Router rejects connections from clients that do not utilize the correct certificate (or the certificate is bad).PASS

LOG-572 - Getting issue details... STATUS


data-router | orchestration-event-service | orchestration-event | missing certificateVerify that the Data Router rejects connections from clients that do not utilize the correct keystore password.PASS

LOG-572 - Getting issue details... STATUS



POMBA Data Router - OOM

Test CaseDescriptionStatusOwnerDateJIRA linkComment
OOM | deploymentVerify that the Data Router can be deployed in a POMBA environment with all the appropriate configuration, etc.PASS

LOG-572 - Getting issue details... STATUS


OOM | removalVerify that the Data Router can be undeployed from a POMBA environment.PASS

LOG-572 - Getting issue details... STATUS



POMBA Data Router - APIv1 Update


Test CaseDescriptionStatusOwnerDateJIRA linkComment
data-router | v1 | orchestration-event-service | orchestration-eventVerify that the orchestration-event API operation only needs to be provided the serviceInstanceId, modelVersionId and modelInvariantId parametersPASS

LOG-428 - Getting issue details... STATUS


data-router | orchestration-event-service | orchestration-eventVerify that the latest version (v1) of the orchestration-event operation is invoked when the API version is not explicitly specified.FAIL

LOG-428 - Getting issue details... STATUS

Bug entered:

LOG-676 - Getting issue details... STATUS

data-router | orchestration-event-service | orchestration-eventVerify that if the v1 API is used to send an orchestration-event operation and the two deprecated parameters – customerId and serviceType – are included, either a POA-AUDIT-INIT message is written without the offending parameters or the request is entirely rejected.PASS

LOG-428 - Getting issue details... STATUS


POA-AUDIT-RESULT | processingVerify that the Data Router remains capable of consuming and processing POA-AUDIT-RESULT events.PASS

LOG-428 - Getting issue details... STATUS



POMBA Data Router - Audit Report Additional Fields

Test CaseDescriptionStatusOwnerDateJIRA linkComment
orchestration-event-service | orchestration-event | X-TransactionIdVerify that the POA-AUDIT-RESULT messages produced by the Validation Service include the X-TransactionId value that was originally sent in the post-orchestration audit request so that this information can appear in the final audit report.PASS

LOG-454 - Getting issue details... STATUS


orchestration-event-service | orchestration-event | missing X-TransactionIdVerify that the POA-AUDIT-RESULT messages produced by the Validation Service includes an X-TransactionId value generated by the Data Router in the case where the original orchestration event did not include one.PASS

LOG-454 - Getting issue details... STATUS


orchestration-event-service | orchestration-event | X-FromAppIdVerify that the POA-AUDIT-RESULT messages produced by the Validation Service include an X-FromAppId attribute that indicates the application that initiated the audit. (i.e. The client that sent the orchestration-event)FAIL

LOG-454 - Getting issue details... STATUS

Big entered:

LOG-697 - Getting issue details... STATUS



POMBA Search Data Service

Test CaseDescriptionStatusOwnerDateJIRA linkComment
POA-AUDIT-REPORT eventVerify that the Search Data Service is able to accept POMBA messaging from the Data Router.PASS

LOG-612 - Getting issue details... STATUS


POMBA Search Data Service - OOM

Test CaseDescriptionStatusOwnerDateJIRA linkComment
oom | search-data-service | installVerify that the Search Data Service can be deployed in a POMBA environment using OOM.PASS


LOG-612 - Getting issue details... STATUS