Re: [onap-discuss] [Onap-release] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April
I've just added a script that will update the OOM helm charts using the versions from the docker-manifest.csv. Going forward, teams should only need to update the manifest as the "single source of truth", and we'll sync the OOM and HEAT docker image versions from there. Thanks, Gary -Original Message- From: onap-release-boun...@lists.onap.org [mailto:onap-release-boun...@lists.onap.org] On Behalf Of dt5...@att.com via RT Sent: Monday, May 07, 2018 11:10 AM To: frank.obr...@amdocs.com Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org Subject: Re: [Onap-release] [onap-discuss] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April Michael, I believe the Heat environment is using the version manifests. So I think we only have 2 places to update now - which is still one too many, but such is life. The good news is there's no changes between 0.2.1-SNAPSHOT and 0.2.2-SNAPSHOT of dgbuilder, so you're not missing any bug fixes but I'll certainly get that updated in OOM. Dan -- Dan Timoney SDN-CP / OpenECOMP SDN-C SSO Please go to D2 ECOMP Release Planning Wiki <https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find key Release Planning Contact Information. On 5/7/18, 1:58 PM, "onap-discuss-boun...@lists.onap.org on behalf of Michael O'Brien via RT" <onap-discuss-boun...@lists.onap.org on behalf of onap-helpd...@rt.linuxfoundation.org> wrote: Dan, Hi, I am using ONAP out of the box – no changes. The image changes anyone makes to HEAT, OOM need to also be made to the other side in order for both ONAP deployment options to be in sync. The image tag for OOM for SDNC and APPC were not updated in sync with the HEAT and manifest change. A note for all PTS’s: any change to any of the 3 configuration places (until we have automated yaml generation) – must be done in sync in all three places The manifest HEAT OOM CCSDK and any other common charts are a bit of a special case – as either PTL needs to make the change for the other project – when using cross project charts like common/dgbuilder. https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_46423_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=g5iDyAsou22Nfxj8QZL5EBVYg1eUmhCNIR0X6t6IZFY=7y2q8-lYULDtlC81W7JOw4S1piwQSK_0uJQlMuvAKEs= The above change is being tested on a live deployment – ETA 90 min before it can be merged. The secondary on this is – this issue only came up because the LF deleted the older image – without the LF’s periodic purge – SDNC and APPC would have continued working with the old images for a while Thank you /michael From: TIMONEY, DAN [mailto:dt5...@att.com] Sent: Monday, May 7, 2018 9:32 AM To: Michael O'Brien <frank.obr...@amdocs.com>; 'onap-rele...@lists.onap.org' <onap-rele...@lists.onap.org>; 'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org> Cc: 'helpd...@onap.org' <helpd...@onap.org> Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April All, You shouldn’t really be using snapshot versions of the CCSDK docker images. You should be using version 0.2-STAGING-latest for CCSDK (and 1.3-STAGING-latest for SDN-C) I noticed last week that the docker version manifest incorrectly specified snapshot versions for the CCSDK docker images, so I fixed that. Sorry if that caused any confusion. Dan -- Dan Timoney SDN-CP / OpenECOMP SDN-C SSO Please go to D2 ECOMP Release Planning Wiki<https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find key Release Planning Contact Information. From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of "OBRIEN, FRANK MICHAEL" <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>> Date: Monday, May 7, 2018 at 7:52 AM To: "'onap-rele...@lists.onap.org'" <onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>, onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Cc: "'helpd...@onap.org'" <helpd...@onap.org<mailto:helpd...@onap.org>> Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April Team, The image was deleted again – looks like as James M. has mentioned – the rule for nexus3 deletion should be “delete 2 week old images – unless there has been no build in the past 2 weeks”
Re: [onap-discuss] [Onap-release] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April
I've just added a script that will update the OOM helm charts using the versions from the docker-manifest.csv. Going forward, teams should only need to update the manifest as the "single source of truth", and we'll sync the OOM and HEAT docker image versions from there. Thanks, Gary -Original Message- From: onap-release-boun...@lists.onap.org [mailto:onap-release-boun...@lists.onap.org] On Behalf Of dt5...@att.com via RT Sent: Monday, May 07, 2018 11:10 AM To: frank.obr...@amdocs.com Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org Subject: Re: [Onap-release] [onap-discuss] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April Michael, I believe the Heat environment is using the version manifests. So I think we only have 2 places to update now - which is still one too many, but such is life. The good news is there's no changes between 0.2.1-SNAPSHOT and 0.2.2-SNAPSHOT of dgbuilder, so you're not missing any bug fixes but I'll certainly get that updated in OOM. Dan -- Dan Timoney SDN-CP / OpenECOMP SDN-C SSO Please go to D2 ECOMP Release Planning Wiki <https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find key Release Planning Contact Information. On 5/7/18, 1:58 PM, "onap-discuss-boun...@lists.onap.org on behalf of Michael O'Brien via RT" <onap-discuss-boun...@lists.onap.org on behalf of onap-helpd...@rt.linuxfoundation.org> wrote: Dan, Hi, I am using ONAP out of the box – no changes. The image changes anyone makes to HEAT, OOM need to also be made to the other side in order for both ONAP deployment options to be in sync. The image tag for OOM for SDNC and APPC were not updated in sync with the HEAT and manifest change. A note for all PTS’s: any change to any of the 3 configuration places (until we have automated yaml generation) – must be done in sync in all three places The manifest HEAT OOM CCSDK and any other common charts are a bit of a special case – as either PTL needs to make the change for the other project – when using cross project charts like common/dgbuilder. https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_46423_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=g5iDyAsou22Nfxj8QZL5EBVYg1eUmhCNIR0X6t6IZFY=7y2q8-lYULDtlC81W7JOw4S1piwQSK_0uJQlMuvAKEs= The above change is being tested on a live deployment – ETA 90 min before it can be merged. The secondary on this is – this issue only came up because the LF deleted the older image – without the LF’s periodic purge – SDNC and APPC would have continued working with the old images for a while Thank you /michael From: TIMONEY, DAN [mailto:dt5...@att.com] Sent: Monday, May 7, 2018 9:32 AM To: Michael O'Brien <frank.obr...@amdocs.com>; 'onap-rele...@lists.onap.org' <onap-rele...@lists.onap.org>; 'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org> Cc: 'helpd...@onap.org' <helpd...@onap.org> Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April All, You shouldn’t really be using snapshot versions of the CCSDK docker images. You should be using version 0.2-STAGING-latest for CCSDK (and 1.3-STAGING-latest for SDN-C) I noticed last week that the docker version manifest incorrectly specified snapshot versions for the CCSDK docker images, so I fixed that. Sorry if that caused any confusion. Dan -- Dan Timoney SDN-CP / OpenECOMP SDN-C SSO Please go to D2 ECOMP Release Planning Wiki<https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find key Release Planning Contact Information. From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of "OBRIEN, FRANK MICHAEL" <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>> Date: Monday, May 7, 2018 at 7:52 AM To: "'onap-rele...@lists.onap.org'" <onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>, onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Cc: "'helpd...@onap.org'" <helpd...@onap.org<mailto:helpd...@onap.org>> Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April Team, The image was deleted again – looks like as James M. has mentioned – the rule for nexus3 deletion should be “delete 2 week old images – unless there has been no build in the past 2 weeks”
