Page History

...

• Uninstall running component and delete deployment

  Code Block
  language bash theme Midnight title Uninstall component linenumbers true
  cfy uninstall bbs-ep

  
  

• Delete blueprint

  Code Block
  language bash theme Midnight title Delete blueprint linenumbers true
  cfy blueprints delete bbs-ep

Initial Validation

After deployment, we can check if BBS-ep POD is running correctly

Deployment steps for VES-Mapper

• VES-Mapper blueprint is available @
  https://gerrit.onap.org/r/gitweb?p=dcaegen2/services/mapper.git;a=blob_plain;f=UniversalVesAdapter/dpo/blueprints/k8s-vesmapper.yaml-template.yaml
• Transfer blueprint file in DCAE bootstrap POD under /blueprints directory
• Log-in to the DCAE bootstrap POD's main container
• To deploy::
  1.  Validate blueprint
     cfy blueprints validate /blueprints/k8s-vesmapper.yaml-template.yaml
  2. Upload validated blueprint
     cfy blueprints upload -b ves-mapper /blueprints/k8s-vesmapper.yaml-template.yaml
  3. Create Cloudify Deployment
     cfy deployments create -b ves-mapper ves-mapper
  4. Deploy component
     cfy executions start -d ves-mapper install
• To un-deploy::
  1. Uninstall component
     cfy uninstall ves-mapper
  2. Delete blueprint
     cfy blueprints delete ves-mapper

Initial Validation

After deployment, we can check if BBS-ep POD is running correctly

root@cluster-admin:~# kubectl -n onap get pods | grep -i bbs
dep-bbs-event-processor-6b6df75d94-g7jw8                          

root@cluster-admin:~# kubectl -n onap get pods | grep -i bbs
dep-bbs-event-processor-6b6df75d94-g7jw8                          2/2       Running            0          1d

And then check the logs to see if it can connect to DMaaP, polling for events. Even in the absence of events, we can at least verify that there is nothing to consume for both PNF re-registration messages and CPE authentication messages.

kubectl -n onap logs dep-bbs-event-processor-6b6df75d94-g7jw8 -c bbs-event-processor


2019-04-10 09:37:58.151  INFO 1 --- [pipeline-thrd-4] o.o.b.e.p.p.ReRegistrationPipeline       : Process next Re-Registration events
2019-04-10 09:37:58.152  INFO 1 --- [pipeline-thrd-1] o.o.b.e.p.p.CpeAuthenticationPipeline    : Process next CPE Authentication events
2019-04-10 09:38:07.680  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.CpeAuthenticationPipeline    : Nothing to consume from DMaaP
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.CpeAuthenticationPipeline    : CPE Authentication processing pipeline has been completed
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.ReRegistrationPipeline       : Nothing to consume from DMaaP
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.ReRegistrationPipeline       : PNF Re-Registration processing pipeline has been completed
2019-04-10 09:38:28.151  INFO 1 --- [pipeline-thrd-4] o.o.b.e.p.p.ReRegistrationPipeline       : Process next Re-Registration events

Feed test data

To perform functional tests for BBS-ep, we must first populate test data to A&AI. This can be done by running the following Postman collection along with the required input file.

...

...

Initial Validation for VES-Mapper

After Cloudify deployment,

1. Check that VES-Mapper POD is created and it is in running state
   
   kubectl get pods -n onap | grep mapper
   dep-s36f1a2fadd614a42872bd680516e271a-dcaegen2-svc-mapper-l2cms 1/1 Running 0 1d

2. Check the logs. Here are some important log statements that could be looked for.

   kubectl logs -n onap dep-s36f1a2fadd614a42872bd680516e271a-dcaegen2-svc-mapper-l2cms | more
   
   11:10:12.078 [main] INFO debugLogger - Triggering controller's start url
   11:10:12.078 [main] INFO debugLogger - Running curl command for url:http://localhost:8085/start
   11:10:12.186 [http-nio-8085-exec-1] INFO o.a.c.c.C.[Tomcat].[localhost].[/] - Initializing Spring DispatcherServlet 'dispatcherServlet'
   11:10:12.186 [http-nio-8085-exec-1] INFO o.s.web.servlet.DispatcherServlet - Initializing Servlet 'dispatcherServlet'
   11:10:12.200 [http-nio-8085-exec-1] INFO o.s.web.servlet.DispatcherServlet - Completed initialization in 14 ms
   11:10:12.243 [http-nio-8085-exec-1] INFO metricsLogger - UniversalVesAdapter Application starting...
   11:10:12.243 [http-nio-8085-exec-1] INFO debugLogger - Creating Subcriber and Publisher with creator.............
   ...
   ...
   ...
   11:10:13.219 [http-nio-8085-exec-1] INFO debugLogger - Created scriber topic:unauthenticated.DCAE_RCC_OUTPUTpublisher topic:unauthenticated.VES_PNFREG_OUTPUT
   11:10:13.230 [rcc-notification] INFO metricsLogger - fetch and publish from and to Dmaap started:rcc-notification
   ...
   ...
   ...
   11:10:13.322 [http-nio-8085-exec-1] INFO debugLogger - Created scriber topic:unauthenticated.ONAP-COLLECTOR-SNMPTRAPpublisher topic:unauthenticated.SEC_FAULT_OUTPUT
   11:10:13.326 [snmp-notification] INFO metricsLogger - fetch and publish from and to Dmaap started:snmp-notification
   ...
   ...
   ...
   11:13:11.873 [snmp-notification] DEBUG debugLogger - number of messages to be converted :0
   11:13:13.044 [rcc-notification] DEBUG debugLogger - number of messages to be converted :0

Feed test data

To perform functional tests for BBS-ep, we must first populate test data to A&AI. This can be done by running the following Postman collection along with the required input file.

Import the Collection JSON file into Postman and then execute it via the Runner utility after changing appropriately the external test-data input (for example give the appropriate A&AI IP address)

...

[
"{\"closedLoopEventClient\":\"DCAE.BBS_event_processor_mSInstance\",\"policyVersion\":\"1.0.0.5\",\"policyName\":\"CPE_Authentication\",\"policyScope\":\"policyScope\",\"target_type\":\"VM\",\"AAI\":{\"cpe.old-authentication-state\":\"outOfService\",\"cpe.new-authentication-state\":\"inService\",\"cpe.swVersion\":\"1.2.3\",\"service-information.hsia-cfs-service-instance-id\":\"1923eaa8-8ab7-49ef-b4c2-e185efbbe832\"},\"closedLoopAlarmStart\":1556102531,\"closedLoopEventStatus\":\"ONSET\",\"closedLoopControlName\":\"controlName\",\"version\":\"1.0.2\",\"target\":\"vserver.vserver-name\",\"requestID\":\"205f5550-37a0-4be7-be63-effefe181b37\",\"from\":\"DCAE-bbs-event-processor\"}"
]\"from\":\"DCAE-bbs-event-processor\"}"
]

Functional testing of VES-Mapper individually

1. Send a PNF registration notification on behalf of RestConf Collector by calling DMaaP API
   1. curl -v -k -H 'Content-Type:application/json' -POST http://message-router.onap.svc.cluster.local:3904/events/unauthenticated.DCAE_RCC_OUTPUT -d @rcc_noti.json
2. Invoke DMaaP API to fetch message on the topic unauthenticated.VES_PNFREG_OUTPUT . VES-Mapper should have published converted VES event on this topic.

curl -X GET 'http://message-router.onap.svc.cluster.local:3904/events/unauthenticated.VES_PNFREG_OUTPUT/grp2/con2?timeout=1600'