FIX: move some end-to-end test configs to values.yaml for nanobot

A few of the configurations for the ete testsuite were baked into
the testsuite file.  This change moves those configs to
the global properties file and allows them to be configured out of
the nanobot values.yaml.  This change only affects the nanobot
version of those files.

The change also makes a minor update to elminate the requirement
for a host path for logging; that is now optional.

signed-off-by: dave kormann <dk3239@att.com>
Change-Id: I02be793f3a5a6f7f51a7ec081ad372aead1f66f9
4 files changed
tree: ea78f87df95cdd8ec40753809ef2b74f0bbc6abb
  1. ons_2019_demo/
  2. ric_robot_suite/
  3. simulators/
  4. test_scripts/
  5. .gitreview
  6. LICENSES.txt
  7. README.md
README.md

RIC end-to-end (E2E) deployment and testing

  1. Clone the it_dep and it_test folders on your VM
  2. Install kubernetes using the script in it_dep_kubernetes/setup-1node-k8s.sh
  3. Install the RIC using the script in it_dep_ricplt/ric_install.sh
  4. Copy robot_install.sh from it_test_ric_robot_suite_helm_ into it_dep_ricplt/
  5. cd into it_dep_ricplt and run robot_install.sh. It will create a softlink to the it_test_ric_robot_suite helm director and do the helm install of rig-robot from it_dep_ricplt
  6. The command “kubectl -n ricplatform get pods” will show the additional pod for ric-robot.
  7. cd into it_test_ric_robot_suite_helm_ric-robot and run ./ete.sh health to verify that the RIC is ready and deployed.