Hi Cristopher,

 

I’d recommend the test teams use the helm-charts-manifest-centos-stable-versioned.tgz file, which uses specific image versions in the manifest, as opposed to “latest”. This would allow for better accuracy in issue reporting, as well as reproducibility, and should ensure you’re testing with images corresponding to the load you’re testing.

 

We’ll try to do a better job of communicating such changes in the future.

 

Cheers,

Don.

 

 

From: Lemus Contreras, Cristopher J [mailto:cristopher.j.lemus.contreras@intel.com]
Sent: Thursday, April 11, 2019 2:03 PM
To: starlingx-discuss@lists.starlingx.io
Subject: [Starlingx-discuss] [helm-charts] Name of auto-generated helm-charts

 

Hello,

 

Today we found that the usual helm-chat-manifest.tgz file was not generated and, instead, 4 new helm charts are available: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190411T140142Z/outputs/helm-charts/

 

 

helm-charts-manifest-centos-dev-latest.tgz

helm-charts-manifest-centos-dev-versioned.tgz

helm-charts-manifest-centos-stable-latest.tgz

helm-charts-manifest-centos-stable-versioned.tgz

 

So, a couple of questions:

 

  1. Which file should be used to do the sanity tests? I assume that we should use: helm-charts-manifest-centos-stable-latest.tgz , kindly confirm.
  2. Is it possible to notify these changes beforehand to the whole comunity? This change breaks the automation that we have in place and could also affect anybody that has automated the download.  It might be a minor change, but it can be easily avoided with a quick notification.

 

Thanks in advance!

 

Cristopher Lemus