I actually would wish for influxDB (and NFS) to be optional parts of the RIC platform. Right now it is just added into ric-dep’s

 bin/install

COMPONENTS=${LIST_OF_COMPONENTS:-"infrastructure dbaas xapp-onboarder appmgr rtmgr e2mgr e2term a1mediator submgr vespamgr jaegeradapter o1mediator alarmmanager influxdb"}

I think a better solution is to add influxdb as extra parameter, in addition to the existing -f, -c and -o. In the install script I would also encourage a check that the storage class exists in the underlying k8s platform.

A new parameter:

   -C LIST_OF_ADDITIONAL_COMPONENTS

This is added to the default list. I.e., for installation you’d invoke

   bin/install -f <recipe>   ####without influx

   bin/install -f <recipe> -C influxdb  ### with influx

which is simpler than having to modify the long list

   bin/install -f <recipe> -c "infrastructure dbaas xapp-onboarder appmgr rtmgr e2mgr e2term a1mediator submgr vespamgr jaegeradapter o1mediator alarmmanager influxdb"

I wouldn’t even mind a special parameter “-o” with the semantics of installing “additional optional components”

The other optional component would be “jaegeradapter” which we can make optional at the same time.

In terms of printing we could even have the install script print this:

Deploying RIC infra components [infrastructure dbaas xapp-onboarder appmgr rtmgr e2mgr e2term a1mediator submgr vespamgr o1mediator alarmmanager]

Note that the following optional components are NOT being deployed: influxdb, jaegeradapter. To deploy them add them with -C to the default component list of the install command.

Note that bin/uninstall needs to eb modified as well.