With StarlingX, the way to add an rpm to the platform is through a patch.

Within the StarlingX patching system it will install the rpm, and will prevent it from being removed by a reboot.

There is a video from the Open Infrastructure Foundation that shows an example of creating your own patch to allow an rpm to be installed.  It uses the patch_build.sh command

https://www.youtube.com/watch?v=vwqhxpgaxXE

For example, if I wanted to add an RPM for pyflame  my patch_build.sh   syntax would look something like this:

# Run this script from within $MY_WORKSPACE

PATH=$MY_REPO/stx/update/extras/scripts:$PATH

PATCH_ID=PYFLAME

DIR=std/rpmbuild/RPMS

PYFLAME=pyflame-1.6.6-4.el7.tis.1.x86_64.rpm

patch_build.sh \

--id ${PATCH_ID} \

--reboot-required=Y \

--summary "New pyflame rpm " \

--desc "Adds a new pyflame rpm "\

--controller ${DIR}/${PYFLAME} \

--controller-worker ${DIR}/${PYFLAME} \

--controller-worker-lowlatency ${DIR}/${PYFLAME}

Be aware that in this example,  I am ‘adding’ an rpm  rather than updating one, so I needed to include special fields

(--controller ,  --controller-worker ,  --controller-worker-lowlatency ) so that the platform knows that the rpm belongs on controller and AIO hosts (and in this example it will not install it on worker or storage nodes)

The video (and my example) assume you have a development environment setup with your variables, etc..  already defined.  If that is not the case, you may need to ensure you have the starlingx/update repo checked out and make the appropriate changes to the commands.  

Al