Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Thanks, Mateusz. I removed the label from the issue and removed the issue from the spreadsheet. David On Thu, Jul 16, 2020 at 2:01 AM wrote: > Hi David, Sylvain, > > > > The OOM-2361 >

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Hi David, Sylvain, The OOM-2361 does not apply to maintenance release (there is no reason to label it). This

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

On 16.07.2020 11:54, Krzysztof Opasiak wrote: s/CC/TO/ Mateusz Pilat Just to make sure that he notices this email;) sic! Your better than me:D I should have read the whole thread before responding;) On 16.07.2020 08:56, sylvain.desbure...@orange.com wrote: Hello David, Here's my take

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Hello David, Here's my take on the two spreadsheet for OOM: El Alto: OOM-2361: @Mateusz, do you have some news on this one? OOM-2392: cause of OOM-2336 so "matched" All OOM "not

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Hello, If Ingress is also accepted as default deployment (it's for now in "PTL GO/NO GO" state), we (OOM team) can also create a template that would push the certificate on the ingress instead of pusing it on the component. Work to do that is not big although there's some. That's an approach

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Dan, In particular, there are about 24 CCSDK issues that are planned for the El Alto maintenance release that I didn't see in Sylvain's list (see Matched tab). Please let me know whether those should be included, or not. David On Wed, Jul 15, 2020 at 1:36 PM David McBride wrote: > Thanks for

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Thanks for starting this thread. I'd like to use this discussion to reconcile the different views on the content of the maintenance releases. I took all of the Jira issues referenced in this thread and put them into two spreadsheets; one for El Alto, and one for Frankfurt. Each spreadsheet has

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Krzysztof, For Guilin, instead of certInitializer, how about if we change dgbuilder to use http instead of https and use it as a trial for using an ingress controller instead of a node port? Since dgbuilder is a design time tool primarily, it's pretty isolated and low risk- and then we'll

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

David, Sylvain, Catherine: The changes in CCSDK and SDNC for the Frankfurt maintenance release are marked in the ONAP jira with the frankfurt_maintenance_release_1 tag. I created a shared query for (hopefully) easy reference: https://jira.onap.org/issues/?filter=12419 The changes in CCSDK

Re: [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

att.com; pdrag...@research.att.com; ofir.sons...@intl.att.com; yuriy.mala...@att.com; onap-...@lists.onap.org; onap-tsc@lists.onap.org; DEBEAU Eric TGI/OLN; RICHOMME Morgan TGI/OLN; Krzysztof Opasiak Objet : [onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of

[onap-tsc] [ONAP][Maintenance Releases] What's onboarded from an OOM point of view

Hi David and Catherine, Following yesterday's call, here's what I see from OOM code point of view on our maintenance releases. It's my view as of today, we may see new merge request coming, especially for the (not announced) Frankfurt Maintenance Release. # El Alto 24 commits have (will for