X-Git-Url: https://gerrit.o-ran-sc.org/r/gitweb?a=blobdiff_plain;f=ric_robot_suite%2Fhelm%2Fnanobot%2Fvalues.yaml;h=5785c7e26fcc16caf7280d1b341cab6a34235330;hb=6948ee0b6b98e048e9cbea56abd76bc4dfe9ee0a;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..5785c7e 100644 --- a/ric_robot_suite/helm/nanobot/values.yaml +++ b/ric_robot_suite/helm/nanobot/values.yaml @@ -1,6 +1,6 @@ # Copyright (c) 2019 AT&T Intellectual Property. # Copyright (c) 2019 Nokia. -# +# Copyright (c) 2020 HCL Technologies Limited. # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at @@ -13,19 +13,26 @@ # 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: 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.3 + # note: the helm chart does not create repository credential secrets. - # If your repository requires authentication, create a docker-registry + # If your repository requires authentication, create a docker-registry # secret with # # kubectl create secret docker-registry --namespace ... @@ -33,7 +40,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: @@ -42,48 +49,108 @@ 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 - namespace: ricplt + # 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 - rtmgr: - user: test - password: test dbaas: - port: "6379" + controller: + type: statefulset + suffix: server + # 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 + submgr: + user: test + password: test + port: 8080 + o1mediator: + user: test + password: test + xapp: + name: robot-xapp + version: 1.0 xapp: - namespace: ricxapp + 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 + rbac: + # If true, create & use RBAC resources + # + create: true + clusterAdminRole: true + rules: + cluster: + - apiGroups: + - "" + resources: + - ["pods", "pods/log", "pods/exec", "services"] + verbs: + - get + - list + - watch + - patch + - update 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 # tag, testuite names, or both. leaving # either unspecified will cause all to run. testsuites: - # - ricdeployment - # - healthcheck + - ricdeployment + - health-check + - ete 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 +161,29 @@ 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: bouncer-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. + # added deployment name and deployment namespace, + # for Ran elements. + name: AAAA456789 + address: 10.0.0.3 + port: 36421 + ran_deployment: e2sim + ran_namespace: test + plmnid: 373437 + gnbid: gnb_734_733_b5c67788 + dashboard: + address: 10.1.0.1 + port: 31080 +