In Guilin, the testsuite/oom helm chart must be sent back to OOM.

It is the opportunity to refactor heavily this pod.

Daniel Rose already initiated the work and suggested a new architecture, more microservices oriented.

The robot pod is now popular in ONAP, as a consequences the change must be transparent to the end user

OOM best practice shall be taken into account in order to introduce non cloud native stuff (storage, certificate management,..).

When possible the robot tests shall be executed as end user, it means out of the ONAP cluster.

At least tests taht are executable from outside the cluster shall be known and referenced with a specific tag.

Work has been initiated by Lucjan Bryndza for ingress.

Robot test tables

note for all the robot tests I run the xtesting docker as follow from the control node

docker run -it -v /tmp/robot_properties.py:/share/config/robot_properties.py -v /tmp/results:/var/lib/xtesting/results nexus3.onap.org:10001/onap/xtesting-healthcheck bash

I adapted the robot_properties I retrieved from the robot-eteshare configmap to reference the nodeports

Healthcheck

Healthcheck

https://git.onap.org/testsuite/tree/robot/testsuites/health-check.robot

NB:

FAIL (1/5): it means that this robot test includes 5 tests, 1 is PASS, the remaining 4 are FAIL

PASS (2/2): as it is PASS it shall be always the same number N/N, it is mentioned to indicate the number of tests of the use case.


Robot TagTestExecutable from outside the clusterBlocking pointsComments
health-aai
  • core
  • small
  • medium
  • full
PASS (1/1)

health-dmaap
  • core
  • small
  • medium
  • full
FAIL (1/3)Basic DMAAP Message Router and Message Router PubSub => Call internal dmaap port (3904)
health-portal
  • core
  • small
  • medium
  • full
PASS (1/1)

health-sdc
  • core
  • small
  • medium
  • full
PASS (1/1)

health-sdnc
  • core
  • small
  • medium
  • full
PASS (1/1)

health-so
  • core
  • small
  • medium
  • full
FAIL (0/1)Basic SO HC )> Call SO internal port (8085)
health-aaf
  • small
  • medium
  • full
FAIL (0/2)

Basic AAF HC FAIL => Call AAF internal port (8100) not exposed

Basic AAF SMS HC FAIL => Call AAF-SMS internal port 10443


health-appc
  • small
  • medium
  • full
PASS (1/1)

health-msb
  • small
  • medium
  • full
PASS (1/1)

health-vid
  • small
  • medium
  • full
PASS (1/1)

multicloud
  • small
  • medium
  • full
FAIL (0/7)502!=200
health-cds
  • medium
  • full
FAIL (0/1)Basc CDS HC => call the cds internal port 8080
health-clamp
  • medium
  • full
PASS (1/1)

health-dcaegen2
  • medium
  • full
FAIl (0/1)Basic DCAE HC => call the internal DCAE HC port (80)
health-policy
  • medium
  • full
FAIL (0/2)Both policy tests => call the internal Policy port (6969)
health-oof
  • medium
  • full
FAIl (2/3)

Basic OOF-Homing OK

but OOF-CMSO calls internal 8080


health-uui
  • medium
  • full
FAIl (0/1)502!=200
external-api
  • medium
  • full
PASS (1/1)

datarouter

full

FAIL (0/1)Datarouter HC call internal 8443 port
health-modeling

full

FAIL (0/1)502!= 200
health-vfc

full

FAIL (0/14)502!=200
health-vnfsdk

full

PASS (1/1)

healthdisthealthdistFAIl (0/1)call to internal SDC port (8445)

Postinstall

https://git.onap.org/testsuite/tree/robot/testsuites/post-install-tests.robot

Robot TagTestExecutable from outsideBlocking pointsComments
aaimodelspostinstallPASS

dmaapaclpostinstallFAILCall to dmaap internal port (3904)

Smoke tests


docker run -v /tmp/robot_properties.py:/share/config/robot_properties.py -v /home/debian/.kube/config::/root/.kube/config -v /tmp/results:/var/lib/xtesting/results nexus3.onap.org:10001/onap/xtesting-smoke-usecases-robot


Robot TagTestExecutable from outsideBlocking pointsComments
hvveshvvesFAIL (0/1)Call to internal DCAE port (consul  on 8500)https://git.onap.org/testsuite/tree/robot/testsuites/hvves-ci.robot
5gbulkpm5gbulkpmFAIL (1/9)Call to internal DCAE inventory port (8080) internal dmaap (3904) + hardocded criteria for DR PM Mapper Subscriber Chec (look for https://dcae-pm-mapper:8443/delivery)https://git.onap.org/testsuite/tree/robot/testsuites/usecases/5gbulkpm.robot
pnf-registratepnf-registrateFAIL (0/3)Call to internal SC port (8445= and internal dmaap port (3904)https://git.onap.org/testsuite/tree/robot/testsuites/pnf-registration.robot
  • No labels