X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=ric_robot_suite%2Fhelm%2Fnanobot%2Fvalues.yaml;h=78f622e869ac410174ef18aff4645b5c90dfa7c9;hb=14eff645eb8db8f5d9fdc7d47bb081c505790509;hp=16ac5a61689cb78bd665ce2b81bc1c7d9b5b310e;hpb=3d053f85cc9c42c57850780a18afb0eef425303c;p=it%2Ftest.git

diff --git a/ric_robot_suite/helm/nanobot/values.yaml b/ric_robot_suite/helm/nanobot/values.yaml
index 16ac5a6..78f622e 100644
--- a/ric_robot_suite/helm/nanobot/values.yaml
+++ b/ric_robot_suite/helm/nanobot/values.yaml
@@ -27,9 +27,9 @@ images:
      name: alpine
      # tag: latest
     run:
-     repository: snapshot.docker.ranco-dev-tools.eastus.cloudapp.azure.com:10001
-     name: test/nanobot
-     tag: latest
+     repository: nexus3.o-ran-sc.org:10004
+     name: o-ran-sc/it-test-nanobot
+     tag: 0.0.1
      # 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:
@@ -55,6 +55,8 @@ ric:
   releaseName: r0
   components:
    a1mediator:
+    xappName: robot-xapp
+    policyID: "6266268"
    appmgr:
     user: test
     password: test
@@ -131,7 +133,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,