Robot Pod Refactoring

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

Robot Tag	Test	Executable from outside the cluster	Blocking points	Comments
health-aai	core small medium full
health-dmaap	core small medium full
health-portal	core small medium full
health-sdc	core small medium full
health-sdc	core small medium full
health-so	core small medium full
healtmr	core small medium full
health-aaf	small medium full
health-appc	small medium full
health-msb	small medium full
health-portal	small medium full
health-vid	small medium full
multicloud	small medium full
health-cds	medium full
health-clamp	medium full
health-dcaegen2	medium full
health-policy	medium full
health-oof	medium full
health-uui	medium full
external-api	medium full
datarouter	full
health-modeling	full
health-vfc	full
health-vnfsdk	full
healthdist	healthdist

Robot Tag	Test	Executable from outside	Blocking points	Comments
hvves	hvves			https://git.onap.org/testsuite/tree/robot/testsuites/hvves-ci.robot
5gbulkpm	5gbulkpm			https://git.onap.org/testsuite/tree/robot/testsuites/usecases/5gbulkpm.robot
pnf-registrate	pnf-registrate			https://git.onap.org/testsuite/tree/robot/testsuites/pnf-registration.robot