Thanks Brian and Gary for the clarification

I think we should document it somewhere in the wiki.

Best Regards

Eric

De : Gary Wu [mailto:[email protected]]
Envoyé : vendredi 17 août 2018 18:33
À : [email protected]; [email protected]; DEBEAU Eric IMT/OLN
Objet : RE: [onap-discuss] Docker images tagging rules for Casablanca 
#integration #oom #heat #docker

There are two docker manifests: one for released images, one for staging 
images.  Each day, we use them to do two sets of deployments: release and 
staging, respectively.

The way it works for OOM is that we take the helm charts from oom repo master 
branch, and apply the docker image versions from the respective manifests above 
for the two sets of deployments.  So, the docker image versions actually 
checked-in to OOM are overridden during the deployment process.  This means 
that teams must keep the release and staging manifests up-to-date to ensure 
that the desired images are used for the daily deployment tests.

Likewise for HEAT.

The actual scripts used by the daily deployments to apply manifest versions 
into OOM/HEAT are 
https://git.onap.org/integration/tree/version-manifest/src/main/scripts/update-oom-image-versions.sh
 and
https://git.onap.org/integration/tree/version-manifest/src/main/scripts/update-heat-image-versions.sh
 respectively.  As we get close to the Casablanca release, I will also use 
these same scripts manually to sync-up the docker images versions in the OOM 
and HEAT templates vs. what’s specified in the release manifest.

Thanks,
Gary

From: [email protected] [mailto:[email protected]] On 
Behalf Of Brian
Sent: Friday, August 17, 2018 6:20 AM
To: '[email protected]' <[email protected]>; 
'[email protected]' <[email protected]>
Subject: Re: [onap-discuss] Docker images tagging rules for Casablanca 
#integration #oom #heat #docker

Gary would know for sure but I think this script updates helm chart images with 
manifest.csv values but not sure if its in use.

https://git.onap.org/integration/tree/version-manifest/src/main/scripts/update-oom-image-versions.sh

Brian


From: FREEMAN, BRIAN D
Sent: Friday, August 17, 2018 9:19 AM
To: [email protected]<mailto:[email protected]>; 
[email protected]<mailto:[email protected]>
Subject: RE: [onap-discuss] Docker images tagging rules for Casablanca 
#integration #oom #heat #docker

Eric,

This is a good discussion.

The link you referenced was for the “release” version – at this point its 
Beijing.
The current development is the “staging” version
https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest-staging.csv

This has the latest tags.

I will point out that some projects bury their tags in their deploy.sh scripts 
in HEAT (I found this in AAI) and we need to change that practice.

I thought we had an override script for OOM deployments that would set the 
image versions but I’m not as familiar with this part of the integration 
environment build process.

https://git.onap.org/integration/tree/version-manifest/src/main/scripts/add-images-from-oom.sh


Brian

From: [email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>> On Behalf Of 
Eric Debeau
Sent: Friday, August 17, 2018 9:09 AM
To: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] Docker images tagging rules for Casablanca #integration 
#oom #heat #docker

Hello

The docker-manifest file is the placeholder to store the Docker images version 
associated with each release.
https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_integration_tree_version-2Dmanifest_src_main_resources_docker-2Dmanifest.csv&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&m=XB-9JPXMzWxGy0EcCrC4BihcVl9VckdJw6phzn2juE8&s=qf5aww_ly89MWt74gASFhn3itXG9AFl_of29O3ceea4&e=>

Today, a script developed by Integration team is populating the Heat env file 
for the Heat based installation.
For OOM, I believe that each project is managing the values in their Chart Helm 
file, but as far as I know, there is no formal alignment between those values 
and the docker-manifest file.

I also noticed that there is no "latest" tags in the docker-manifest file

I would like to know the strategy for Docker images tagging for the master 
branch.

Thanks

Best Regards


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11929): https://lists.onap.org/g/onap-discuss/message/11929
Mute This Topic: https://lists.onap.org/mt/24612018/21656
Mute #integration: https://lists.onap.org/mk?hashtag=integration&subid=2740164
Mute #oom: https://lists.onap.org/mk?hashtag=oom&subid=2740164
Mute #heat: https://lists.onap.org/mk?hashtag=heat&subid=2740164
Mute #docker: https://lists.onap.org/mk?hashtag=docker&subid=2740164
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to