[Starlingx-discuss] Docker image list

[Bailey, Henry Albert (Al)]

I don't think all of those images are downloaded during the application-apply, due to overrides selecting a more recent version.

The three phases are where images are downloaded are:

- Initial phase (ansible)
- Platform-integ-apps (after unlock)
- Stx-openstack (after application-apply)

Would authoring and maintaining a document with these images and versions be a decent way to manage this. (probably in starlingx/config)
Or is running scripts the preferred approach?

The readme.rst for  starlingx/config is light on contents at the moment
https://opendev.org/starlingx/config/src/branch/master/README.rst

Al


-----Original Message-----
From: Dean Troyer [mailto:dtroyer at gmail.com] 
Sent: Monday, June 24, 2019 10:50 AM
To: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Docker image list

On Mon, Jun 24, 2019 at 8:59 AM Cordoba Malibran, Erich
<erich.cordoba.malibran at intel.com> wrote:
> docker.io/openstackhelm/magnum:ocata
> docker.io/kolla/ubuntu-source-aodh-evaluator:ocata
> docker.io/openstackhelm/heat:newton
> docker.io/kolla/ubuntu-source-ceilometer-api:ocata
> docker.io/openstackhelm/horizon:ocata
[...]

Why are these showing up with 'ocata' and 'newton' in the names/tags?
Presumably we are not using Ocata or Newton releases.  Is this an
artifact of how OpenStack-Helm works?

dt

-- 
Dean Troyer
dtroyer at gmail.com

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss