X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=ric_robot_suite%2Fhelm%2Fnanobot%2Fvalues.yaml;h=c2a224c8db8e484a7721e256376ae2a9895cf11d;hb=cc685917b28444e6e9fc70f1a96b14e073d8cec7;hp=256f17ceca5b78a6d467a3b215a06ebd943205d8;hpb=c5fa07bcd8cbd614bcd813cac698385b789bcfcb;p=it%2Ftest.git diff --git a/ric_robot_suite/helm/nanobot/values.yaml b/ric_robot_suite/helm/nanobot/values.yaml index 256f17c..c2a224c 100644 --- a/ric_robot_suite/helm/nanobot/values.yaml +++ b/ric_robot_suite/helm/nanobot/values.yaml @@ -13,6 +13,12 @@ # See the License for the specific language governing permissions and # limitations under the License. +# +# configuration for this chart is split between this file and the "recipe" +# used by the ric-common chart. For the most part, platform configuration +# is defined by that recipe, and robot configuration is here. +# + images: ric: robot: @@ -21,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.2 # note: the helm chart does not create repository credential secrets. # If your repository requires authentication, create a docker-registry # secret with @@ -33,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: @@ -46,27 +52,52 @@ ric: # for these can typically be found in # the ricplt/ric_env.sh file from the ric # platform source tree - namespace: ricplt releaseName: r0 components: + a1mediator: + xappName: robot-xapp + policyID: "6266268" appmgr: user: test password: test - rtmgr: - user: test - password: test dbaas: - port: "6379" e2mgr: user: test password: test e2term: + rtmgr: + user: test + password: test + submgr: + o1mediator: + user: test + password: test + xapp: + name: robot-xapp + version: 1.0 xapp: - namespace: ricxapp + mcxapp: + listener: + containername: mc-xapp-listener + writer: + containername: mc-xapp-writer + # statistics sent to ves by the writer. the tests + # will check that these are actually being sent + statistics: + - mc_connected_cnt + - mc_connection_stats + - mc_connects_cnt + - mc_disconnects_cnt + - mc_unique_ue_cnt + - rrcx_pdf_serv_cell + - rrcx_pdf_serv_gnb + - rrcx_stats_serv_cell + - rrcx_stats_serv_gnb robot: + release: r1 # - # host filesystem path where robot - # output will be stored + # If specified, a host filesystem + # path where robot output will be stored log: /opt/ric/robot/log # # Active testsuites can be chosen by @@ -76,14 +107,21 @@ ric: # - ricdeployment # - healthcheck tags: - # - etetests - # - k8stests + enabled: + # - etetests + # - k8stests + disabled: + # - intrusive + # - artificialdata + - UpdateWebPage + - e2setup_dash + - x2setup_dash # job: # 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 @@ -94,4 +132,22 @@ ric: create: true # ... and specify the serviceaccount here: # name: nanobot - \ No newline at end of file + # + environment: + # the name of a test xapp; the appmgr testsuite + # will attempt to deploy and undeploy this app; + # This should be an xapp which is "onboarded" to + # the appmgr but not deployed at the time the test + # is initiated. + 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, + # but in either case should exist prior to test + # initiation. + name: AAAA456789 + address: 10.0.0.3 + port: 36421 + dashboard: + address: 10.1.0.1 + port: 31080 \ No newline at end of file