Hi All,

These changes were just merged.  The wiki was updated too.

Generate the stx-openstack application tarball[edit]

The stx-openstack application tarballs are generated with each build on the CENGN mirror.

Alternatively, in a development environment, run the following command to construct the application tarballs.

$MY_REPO_ROOT_DIR/cgcs-root/build-tools/build-helm-charts.sh

· The resulting tarballs can be found under $MY_WORKSPACE/std/build-helm/stx.

· By default, the latest stable starlingx docker images are used in armada manifest. You can build the application tarball with different image versions by specifying the image record files/urls which contain the images you would like to use via option --image-record (The starlingx image build records can be found on the CENGN mirror)

· To construct a new name of stx-openstack tarball, specify a label with --label option. The name of the stx-openstack application tarball is stx-openstack-<stx-openstack-helm rpm version>(-<label>).tgz

· If the build-helm-charts.sh command is unable to find the charts, run "build-pkgs" to build the chart rpms and re-run the build-helm-charts.sh command.

Stage application for deployment[edit]

Transfer the stx-openstack application tarball onto your active controller.

Use sysinv to upload the application tarball.

source /etc/platform/openrc

system application-upload stx-openstack-1.0-11.tgz

system application-list

· stx-openstack application tarball has a metadata.yaml file which contains the app name and version. The app name and version will be extracted from the metadata.yaml when uploading. For the application tarballs that do not have app name and version included in metadata.yaml, they need to be specified via --app-name and --app-version.

Thanks,

-Angie

From: Wang, Jing (Angie)
Sent: May-01-19 12:12 AM
To: starlingx-discuss@lists.starlingx.io
Subject: Automation script needs to be updated because the coming changes for build-helm-charts.sh and system application-upload CLI

Hi All,

Please aware that there are two commits may be merged soon that will impact automated testing.

The gerrit reviews:

- The changes for build-helm-charts.sh: https://review.opendev.org/#/c/655494/

- The changes for system application-upload CLI: https://review.opendev.org/#/c/655497/

Once they are merged,

- A metadata.yaml file will be built into stx-openstack application tarball which contains application name and version.

        The name of the application tarball will be changed to <application-name>-<application-rpm-version>(-<label>).tgz

        (Ie… stx-openstack app tarball will be renamed from “helm-charts-manifest(-<label>).tgz” to “stx-openstack-1.0-11(-<label>).tgz”)

        But to allow people to adapt their scripts and transition, we create a symbolic link that pointing to the new tarball with the old name. We will drop the symbolic link in two weeks.

- The usage of system application-upload CLI will be

usage: system application-upload [-n <app name>] [-v <app version>] <tar file>

Optional arguments:

  -n <app name>, --app-name <app name>

                        Name of the application

  -v <app version>, --app-version <app version>

                        Version of the application

App name is an optional parameter now, it can be supplied by ‘--app-name’ or ‘-n’.

To upload stx-openstack application,  it doesn’t need to specify app name and app version, they will be extracted from metadata.yaml file.  Note: the app name/version in metadata.yaml has higher priority.

Ie. system application-upload stx-openstack-1.0-11.tgz

To upload other custom apps that may not have metadata.yaml file or may not have app information included in the metadata.yaml, user has to pass app name and version.

Ie. system application-upload custom-app.tgz  -n xxx –v xxx

The wiki will be updated regarding to these changes too.

If you have any concerns or questions, free feel to ask me.

Thanks,

-Angie