Hello,

In an effort to add greater customizability and offer better debugging support, some changes have been made to remote clients.

Until now, remote clients were built weekly by the CENGN build and a tarball provided at [1]. This tarball had the location of the docker images embedded inside them; while users could open the file that contained the links  to these docker images and edit them, no official support was provided for this.

With the latest changes that just merged, you can override the pulled images when you configure the clients. The review that added the changes is at [2].

The commit added two new optional parameters: "-p" and "-a". As stated, they are optional and if don't use them the used images will be the default ones mentioned  in the tarball.

The "-p" parameter is used to override the platformclients image and "-a" is used to override the openstack application image.

Examples of usage:
  1. ./configure_client.sh (without any parameters given, the defaults will be used)
  2. ./configure_client.sh -p docker.io/randomrepo/randomimage:latest (this will use the docker image given as parameter for platform client operations)
  3. ./configure_client.sh -a docker.io/anotherrepo/anotherimage:tag(this will use the docker image given as parameter for openstack clients operations)
  4. ./configure_client  -p docker.io/randomrepo/randomimage:latest -a docker.io/anotherrepo/anotherimage:tag (it will override both)
For full instruction about how to configure and use remote clients for StarlingX, you can read the full readme at [3]


[1]: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_docker_image_build/outputs/remote-cli/
[2]: https://review.opendev.org/#/c/714897/
[3]: https://opendev.org/starlingx/clients/src/branch/master/remote_cli/README