X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=ric_robot_suite%2Fhelm%2Fnanobot%2Fvalues.yaml;h=c433c177687e68f8c0120b295737249ab9b77761;hb=refs%2Fchanges%2F70%2F4170%2F1;hp=0abfda056345735de87fb19531706b323594fcde;hpb=ce3094f1ef4f3197d730cc38a152811919347c17;p=it%2Ftest.git

diff --git a/ric_robot_suite/helm/nanobot/values.yaml b/ric_robot_suite/helm/nanobot/values.yaml
index 0abfda0..c433c17 100644
--- a/ric_robot_suite/helm/nanobot/values.yaml
+++ b/ric_robot_suite/helm/nanobot/values.yaml
@@ -25,11 +25,11 @@ images:
    job:
     init:
      name: alpine
-     # tag: latest
-    run:
-     repository: snapshot.docker.ranco-dev-tools.eastus.cloudapp.azure.com:10001
-     name: test/nanobot
      tag: latest
+    run:
+     repository: nexus3.o-ran-sc.org:10004
+     name: o-ran-sc/it-test-nanobot
+     tag: 0.0.2
      # note: the helm chart does not create repository credential secrets.
      # If your repository requires authentication, create a docker-registry 
      # secret with
@@ -39,7 +39,7 @@ images:
      # and fill in secret-name below.  Only one secret should be created per
      # registry. The chart will take care of producing a unique  list of
      # imagePullSecrets.
-     repositoryCred: azure-secret
+     repositoryCred: o-ran-registry-secret
 ric:
  cluster:
   # The kubernetes cluster name.  To find this, do:
@@ -48,32 +48,62 @@ ric:
   # the DNS domain for k8s services, typically "cluster.local"
   domain: cluster.local
  platform:
-  # RIC installation details.  The values
-  # for these can typically be found in
-  # the ricplt/ric_env.sh file from the ric
-  # platform source tree
+  # RIC installation details.  These values mostly cover things
+  # the robot needs to know, but which aren't configured by the
+  # RIC recipe.
   releaseName: r0
   components:
+   a1mediator:
+    xappName: robot-xapp
+    policyID: "6266268"
    appmgr:
     user: test
     password: test
+   dbaas:
+    controller:
+     # the type of k8s controller for this entity
+     # (ie, statefulset, daemonset, deployment..)
+     # if unspecified, the default is "deployment".
+     type: statefulset
+     # the suffix, if any, to append to the name
+     # of the controller entity.  The chart will
+     # prepend a hyphen to this string.
+     suffix: server
+   e2mgr:
+    user: test
+    password: test
+   e2term:
+    controller:
+     suffix: alpha
    rtmgr:
     user: test
     password: test
-   e2mgr:
+   submgr:
+   o1mediator:
     user: test
     password: test
-   e2term:
-   a1mediator:
+    xapp:
+     name: robot-xapp
+     version: 1.0
  xapp:
-  anr:
-   servicename: anr
+  mcxapp:
+   listener:
+    containername: mc-xapp-listener
+   writer:
+    containername: mcxapp
+    # statistics sent to ves by the writer.  the tests
+    # will check that these are actually being sent
+    statistics:
+    - mc_connected_cnt
+    - throughput_gnb
+    - throughput_rollup
+    - throughput_ue
  robot:
   release: r1
   #
   # If specified, a host filesystem
   # path where robot output will be stored 
-  # log: /opt/ric/robot/log
+  log: /opt/ric/robot/log
   #
   # Active testsuites can be chosen by
   # tag, testuite names, or both.  leaving
@@ -96,7 +126,7 @@ ric:
    # set this to a true value to cause
    # the job to fail (and, typically, be resubmitted)
    # when tests fail
-   failOnTestFail: false
+   failOnTestFail: true
    serviceAccount:
     # by default, the job will create
     # a temporary serviceaccount and
@@ -114,7 +144,7 @@ ric:
     # This should be an xapp which is "onboarded" to
     # the appmgr but not deployed at the time the test
     # is initiated.
-    xapp: xapp-std
+    xapp: robot-xapp
     gNodeB:
      # the details of a test gNodeB, for [E/X]2 tests.
      # This can be either a real gnodeb or a simulator,
@@ -123,3 +153,6 @@ ric:
      name: AAAA456789
      address: 10.0.0.3
      port: 36421
+    dashboard:
+     address: 10.1.0.1
+     port: 31080
\ No newline at end of file