# 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:
# for these can typically be found in
# the ricplt/ric_env.sh file from the ric
# platform source tree
- namespace: ricplt
releaseName: r0
components:
appmgr:
rtmgr:
user: test
password: test
- dbaas:
- port: "6379"
e2mgr:
user: test
password: test
e2term:
+ a1mediator:
xapp:
- namespace: ricxapp
+ anr:
+ servicename: anr
robot:
+ release: r1
#
- # host filesystem path where robot
- # output will be stored
- log: /opt/ric/robot/log
+ # 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
# - 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
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: xapp-std
+ 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