Yeah. Actually, I mean sanity testing is using stable-versioned. Sorry, I typed wrongly.
L
From: Penney, Don
Sent: May-02-19 9:44 PM
To: Hernandez Gonzalez, Fernando; Wang, Jing (Angie); starlingx-discuss@lists.starlingx.io
Subject: RE: Automation script needs to be updated because the coming changes for build-helm-charts.sh and system application-upload CLI
In my opinion, PV and sanity testing should be done with stable-versioned, ensuring version-specific images are used corresponding to the load (as opposed to ¡°latest¡± label). In addition, this would help for
debugging, as designers would be able to easily verify which images are being used.
Cheers,
Don.
From: Hernandez Gonzalez, Fernando [mailto:fernando.hernandez.gonzalez@intel.com]
Sent: Thursday, May 02, 2019 7:05 PM
To: Wang, Jing (Angie); starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Automation script needs to be updated because the coming changes for build-helm-charts.sh and system application-upload CLI
Thanks a lot Angie, I will use stable-latest
J
Maybe we should consider in put a small description under BUILD_INFO.txt about helm chart information for the community.
Regards,
Fernando Hernandez Gonzalez
Cloud Software Engineer
Avenida del Bosque #1001 Col, El Baj¨ªo
Zapopan, Jalisco MX, 45019
____________________________________
Office: +52.33.16.45.01.34 inet 86450134
From: Wang, Jing (Angie) [mailto:Angie.Wang@windriver.com]
Sent: Thursday, May 2, 2019 5:48 PM
To: Hernandez Gonzalez, Fernando <fernando.hernandez.gonzalez@intel.com>; starlingx-discuss@lists.starlingx.io
Subject: RE: Automation script needs to be updated because the coming changes for build-helm-charts.sh and system application-upload CLI
Hi Fernando,
The ¡°stx-openstack-xxx¡± is the new name of the stx-openstack app tarball. The ¡°helm-charts-manifest-xxx¡± is the old name.
The helm-charts-manifest tarballs are the symbolic links to the stx-openstack tarballs.
helm-charts-manifest-centos-dev-latest.tgz
->
stx-openstack-1.0-11-centos-dev-latest.tgz
helm-charts-manifest-centos-dev-versioned.tgz
->
stx-openstack-1.0-11-centos-dev-versioned.tgz
helm-charts-manifest-centos-stable-latest.tgz
->
stx-openstack-1.0-11-centos-stable-latest.tgz
helm-charts-manifest-centos-stable-versioned.tgz
->
stx-openstack-1.0-11-centos-stable-versioned.tgz
dev-latest/dev-versioned/stable-latest/stable-versioned represents which starlingx docker images are being used to install charts.
In sanity test, I think we are using stable-latest.
Thanks,
-Angie
From: Hernandez Gonzalez, Fernando [mailto:fernando.hernandez.gonzalez@intel.com]
Sent: May-02-19 6:26 PM
To: Wang, Jing (Angie);
starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Automation script needs to be updated because the coming changes for build-helm-charts.sh and system application-upload CLI
Hi Angie, seems the build succeed, Could you please help me out and tell me what is the appropriate helm char to use?
http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/latest_build/outputs/helm-charts/
|
../ |
|
- |
Directory |
|
2019-May-02 17:08:34 |
1.0M |
application/x-gtar-compressed |
|
|
2019-May-02 17:08:34 |
1.0M |
application/x-gtar-compressed |
|
|
2019-May-02 17:08:34 |
1.0M |
application/x-gtar-compressed |
|
|
2019-May-02 17:08:34 |
1.0M |
application/x-gtar-compressed |
|
|
2019-May-02 17:08:34 |
1.0M |
application/x-gtar-compressed |
|
|
2019-May-02 17:08:34 |
1.0M |
application/x-gtar-compressed |
|
|
2019-May-02 17:08:34 |
1.0M |
application/x-gtar-compressed |
|
|
2019-May-02 17:08:34 |
1.0M |
application/x-gtar-compressed |
Thanks!
Fernando Hernandez Gonzalez
Cloud Software Engineer
Avenida del Bosque #1001 Col, El Baj¨ªo
Zapopan, Jalisco MX, 45019
____________________________________
Office: +52.33.16.45.01.34 inet 86450134
From: Wang, Jing (Angie) [mailto:Angie.Wang@windriver.com]
Sent: Wednesday, May 1, 2019 4:55 PM
To: starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] Automation script needs to be updated because the coming changes for build-helm-charts.sh and system application-upload CLI
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 ?Cv 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