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.2
# note: the helm chart does not create repository credential secrets.
# If your repository requires authentication, create a docker-registry
# secret with
# 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:
releaseName: r0
components:
a1mediator:
+ xappName: robot-xapp
+ policyID: "6266268"
appmgr:
user: test
password: test
user: test
password: test
submgr:
+ o1mediator:
+ user: test
+ password: test
+ xapp:
+ name: robot-xapp
+ version: 1.0
xapp:
mcxapp:
listener:
#
# 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
# 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,