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 <[email protected]> wrote: > Hi David, Sylvain, > > > > The OOM-2361 > <https://protect2.fireeye.com/v1/url?k=43278791-1ef78f79-43260cde-000babff32e3-7d8fb2f90712bde7&q=1&e=f9abe687-b702-4625-8c46-95165b9f0ce5&u=https%3A%2F%2Fjira.onap.org%2Fbrowse%2FOOM-2361> > does > not apply to maintenance release (there is no reason to label it). This is > a list of all the Docker images that are present in given release of ONAP > that we extract AFTER release is announced. > > > > Regards, > > Mateusz > > > > *From:* [email protected] <[email protected]> > *Sent:* Thursday, July 16, 2020 8:56 AM > *To:* David McBride <[email protected]>; Krzysztof Opasiak < > [email protected]> > *Cc:* TIMONEY, DAN <[email protected]>; LEFEVRE, CATHERINE < > [email protected]>; LUCAS, JACK <[email protected]>; > HERNANDEZ-HERRERO, JORGE <[email protected]>; [email protected]; > [email protected]; LUNANUOVA, DOMINIC < > [email protected]>; DETERME, SEBASTIEN <[email protected]>; > PARTHASARATHY, RAMESH <[email protected]>; [email protected]; > DRAGOSH, PAM <[email protected]>; SONSINO, OFIR < > [email protected]>; MALAKOV, YURIY <[email protected]>; > [email protected]; [email protected]; DEBEAU Eric TGI/OLN < > [email protected]>; RICHOMME Morgan TGI/OLN < > [email protected]>; [email protected] > *Subject:* RE:[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 > <https://protect2.fireeye.com/v1/url?k=43278791-1ef78f79-43260cde-000babff32e3-7d8fb2f90712bde7&q=1&e=f9abe687-b702-4625-8c46-95165b9f0ce5&u=https%3A%2F%2Fjira.onap.org%2Fbrowse%2FOOM-2361>: > @Mateusz, do you have some news on this one? > > OOM-2392 > <https://protect2.fireeye.com/v1/url?k=44a9394b-197931a3-44a8b204-000babff32e3-c918e178b2d3e3d1&q=1&e=f9abe687-b702-4625-8c46-95165b9f0ce5&u=https%3A%2F%2Fjira.onap.org%2Fbrowse%2FOOM-2392>: > cause of OOM-2336 > <https://protect2.fireeye.com/v1/url?k=1be59079-46359891-1be41b36-000babff32e3-9fbd34a90b8d95a3&q=1&e=f9abe687-b702-4625-8c46-95165b9f0ce5&u=https%3A%2F%2Fjira.onap.org%2Fbrowse%2FOOM-2336> > so "matched" > > All OOM "not matched" will be obviously in Release and release note > > > > > > Frankfurt: > > OOM-2316 > <https://protect2.fireeye.com/v1/url?k=03e258b5-5e32505d-03e3d3fa-000babff32e3-cee6cfb8c4c4077f&q=1&e=f9abe687-b702-4625-8c46-95165b9f0ce5&u=https%3A%2F%2Fjira.onap.org%2Fbrowse%2FOOM-2316>: > this is a feature we rolled back because of bad behavior. *Will not* be > part of Frankfurt Maintenance Release > > > > > > By the way, I'm not allowed anymore to send emails to > [email protected] and [email protected]. Is it normal? > > > > Regards, > > Sylvain > ------------------------------ > > *De :* David McBride [[email protected]] > *Envoyé :* mercredi 15 juillet 2020 22:36 > *À :* Krzysztof Opasiak > *Cc :* TIMONEY, DAN; DESBUREAUX Sylvain TGI/OLN; LEFEVRE, CATHERINE; > LUCAS, JACK; HERNANDEZ-HERRERO, JORGE; [email protected]; > [email protected]; LUNANUOVA, DOMINIC; DETERME, > SEBASTIEN; PARTHASARATHY, RAMESH; [email protected]; DRAGOSH, PAM; > SONSINO, OFIR; MALAKOV, YURIY; [email protected]; > [email protected]; DEBEAU Eric TGI/OLN; RICHOMME Morgan TGI/OLN > *Objet :* Re: [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 two tabs: "Matched" and "Not Matched". All of the issues in Jira that > are labeled for the maintenance release are shown in the left hand column > on the "Matched" tab. In the columns to the right are where the labeled > issues in Jira match with an issue cited by one of you. > > > > The "Not Matched" tab shows issues that one of you cited, that are not > currently labeled for the maintenance release. > > > > I'm happy to take all of the "Not Matched" issues and apply the > maintenance release label to them, en masse. > > > > What I would like for you to do is to look at the issues in the left-hand > column on the "Matched" tab, that are not matched by an issue in this > email, and consider whether they should be included, or excluded. > > > > David > > > > On Wed, Jul 15, 2020 at 11:25 AM Krzysztof Opasiak <[email protected]> > wrote: > > > > On 15.07.2020 20:08, TIMONEY, DAN wrote: > > 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 have one less > cert to have to worry about maintaining. > > Well as long as it is exposed to the outside world it should be https. > So we can either: > > 1) Change its type to ClusterIP if doesn't have to be exposed. > 2) Keep it https;) > > > > > For Frankfurt, could we cherry pick that same change? If so, I'm happy > to make that a priority if you can provide some pointers on how to switch > from using a node port to ingress controller for the dgbuilder service, and > then I can make that change once the right way. > > Actually there is nothing to do from OOM perspective apart from enabling > ingress;) > > All the ingress configuration (with SSL passthrough) is already there. > The only thing that you need to do is to make sure that dgbuilder can > actually work with ingress which means that there is no hardcoded urls etc > > > Otherwise, I'm happy to install those certs in the Frankfurt branch > like Sylvain did for us for the CDS py-executor pod recently. > > That's exactly what I've been talking about:) > > > > > > > Dan > > > > -----Original Message----- > > From: Krzysztof Opasiak <[email protected]> > > Sent: Wednesday, July 15, 2020 12:25 PM > > To: TIMONEY, DAN <[email protected]>; [email protected]; > [email protected]; LEFEVRE, CATHERINE < > [email protected]> > > Cc: LUCAS, JACK <[email protected]>; [email protected]; > [email protected]; LUNANUOVA, DOMINIC < > [email protected]>; DETERME, SEBASTIEN <[email protected]>; > [email protected]; DRAGOSH, PAM <[email protected]>; > MALAKOV, YURIY <[email protected]>; [email protected]; > [email protected]; DEBEAU Eric TGI/OLN <[email protected]>; > RICHOMME Morgan TGI/OLN <[email protected]> > > Subject: Re: [ONAP][Maintenance Releases] What's onboarded from an OOM > point of view > > > > > > > > On 15.07.2020 15:04, TIMONEY, DAN wrote: > >> 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://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_issues_-3Ffilter-3D12419&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Ms-DNhR23dO4sQFfYRm4ow&m=MH705N3khZcYCab8BWZQ-KGe7F_MSPGPow7XAH0AutI&s=4Nul3p0kn2KxOXVCPL4xVGlFlrWpt3VNRgPDCAQYSII&e= > >> < > https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3D74340a1b-2D29aff678-2D74358154-2D0cc47a31cdbc-2D22b3eeadf7f1f882-26q-3D1-26u-3Dhttps-253A-252F-252Fjira.onap.org-252Fissues-252F-253Ffilter-253D12419&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Ms-DNhR23dO4sQFfYRm4ow&m=MH705N3khZcYCab8BWZQ-KGe7F_MSPGPow7XAH0AutI&s=QDGPcOWtfGOeizUdcir51R5V1Yc3oEwQPIgQOmM9ixU&e= > > > >> > >> The changes in CCSDK and SDNC for the El Alto maintenance release are > >> also marked in the ONAP Jira, with the El_Alto_Maintenance_1 tag. I > >> created a shared query for that one as well: > >> > >> > https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_issues_-3Ffilter-3D12418&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Ms-DNhR23dO4sQFfYRm4ow&m=MH705N3khZcYCab8BWZQ-KGe7F_MSPGPow7XAH0AutI&s=AbrzXZdr8B95ujLKCzkdAmOjJogP8TItzzNc80ld9tM&e= > >> < > https://urldefense.proofpoint.com/v2/url?u=https-3A__protect2.fireeye.com_url-3Fk-3Db340f9b6-2Deedb05d5-2Db34172f9-2D0cc47a31cdbc-2Dac7d3148487fbdee-26q-3D1-26u-3Dhttps-253A-252F-252Fjira.onap.org-252Fissues-252F-253Ffilter-253D12418&d=DwIDaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Ms-DNhR23dO4sQFfYRm4ow&m=MH705N3khZcYCab8BWZQ-KGe7F_MSPGPow7XAH0AutI&s=PRLrhmi-d8XFKWM7Z770hrjID117o1AXW6cuOs9WDB8&e= > > > >> > >> There are 2 new issues in that list that I added in order to address the > >> expired certificate in dgbuilder that Morgan brought to our attention > >> (thanks for that!). I’m in the process of creating a new docker to > >> address that issue and would like to include that in this maintenance > >> release if we can. > > > > El Alto - I'm fine with docker > > > > Frankfurt - would be great to have it in OOM repo instead > > > > master - use certInitializer > > > >> > >> Thanks! > >> > >> Dan > >> > >> *From: *"[email protected]> > >> *Date: *Friday, July 10, 2020 at 5:17 AM > >> *To: *"[email protected]>, > >> "LEFEVRE, CATHERINE" <[email protected]> > >> *Cc: *"LUCAS, JACK" <[email protected]>, "HERNANDEZ-HERRERO, > >> JORGE" <[email protected]>, "[email protected]" > >> <[email protected]>, "[email protected]" > >> <[email protected]>, "LUNANUOVA, DOMINIC" > >> <[email protected]>, "DETERME, SEBASTIEN" > >> <[email protected]>, "PARTHASARATHY, RAMESH" > >> <[email protected]" <[email protected]>, > >> "TIMONEY, DAN" <[email protected]>, "DRAGOSH, PAM" > >> <[email protected]>, "SONSINO, OFIR" > >> <[email protected]>, > >> "[email protected]>, > >> "[email protected]>, DEBEAU Eric TGI/OLN > >> <[email protected]>, RICHOMME Morgan TGI/OLN > >> <[email protected]> > >> *Subject: *[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 2) been applied to El Alto branch since last > >> maintenance release: > >> > >> The following commits include code change in parent repo, so digging > >> between the two release is needed in order to know > >> what changed: > >> * Update policy brmsgw to point to latest versions (POLICY-2171) > >> BRMS_DEPENDENCY_VERSION: 1.4.2 -> 1.5.3 > >> BRMS_MODELS_DEPENDENCY_VERSION: 2.0.2 -> 2.1.4 > >> * [DMaaP DR] New certs fro ElAlto images (DMAAP-1421) > >> onap/dmaap/datarouter-node: 2.1.2 -> 2.2.0 > >> onap/dmaap/datarouter-prov: 2.1.2 -> 2.2.0 > >> * Update DCAE certs for El Alto (DCAEGEN2-2206) > >> onap/org.onap.dcaegen2.deployments.tls-init-container: 1.0.3 -> > 1.0.4 > >> * Update CDS image version for elalto to 0.6.5 (OOM-2336) > >> onap/ccsdk-blueprintsprocessor: 0.6.3 -> 0.6.5 > >> onap/ccsdk-commandexecutor: 0.6.3 -> 0.6.5 > >> onap/ccsdk-sdclistener: 0.6.3 -> 0.6.5 > >> onap/ccsdk-cds-ui-server: 0.6.3 -> 0.6.5 > >> * [POLICY] new elato images (POLICY-2519) > >> onap/policy-pe: 1.5.2 -> 1.5.3 > >> onap/policy-pdpd-cl: 1.5.3 -> 1.5.4 > >> onap/policy-apex-pdp: 2.2.2 -> 2.2.3 > >> onap/policy-api: 2.1.2 -> 2.1.3 > >> onap/policy-distribution: 2.2.1 -> 2.2.2 > >> onap/policy-pap: 2.1.2 -> 2.1.3 > >> onap/policy-xacml-pdp: 2.1.2 -> 2.1.3 > >> * use new image with updated certs (DMAAP-1424) > >> onap/dmaap/dmaap-bc: 1.1.5 -> 1.1.9 > >> onap/dmaap/dbc-client: 1.0.9 -> 1.1.9 > >> * [SDC] Update sdc images for ElAlto (SDC-3199) (*** NOT YET MERGED ***) > >> onap/sdc-backend: 1.5.2 -> 1.5.3 > >> onap/sdc-backend-init: 1.5.2 -> 1.5.3 > >> onap/sdc-cassandra: 1.5.2 -> 1.5.3 > >> onap/sdc-cassandra-init: 1.5.2 -> 1.5.3 > >> onap/dcae-be: 1.3.2 -> 1.3.2-1 > >> onap/dcae-tools: 1.3.2 -> 1.3.2-1 > >> onap/dcae-dt: 1.3.2 -> 1.3.2-1 > >> onap/dcae-fe: 1.3.2 -> 1.3.2-1 > >> onap/sdc-elasticsearch: 1.5.2 -> 1.5.3 > >> onap/sdc-init-elasticsearch: 1.5.2 -> 1.5.3 > >> onap/sdc-frontend: 1.5.2 -> 1.5.3 > >> onap/sdc-kibana: 1.5.2 -> 1.5.3 > >> onap/sdc-onboard-backend: 1.5.2 -> 1.5.3 > >> onap/sdc-onboard-cassandra-init: 1.5.2 -> 1.5.3 > >> > >> These are "OOM only" (change in helm charts, no new images): > >> * Fixing missing apiVersion in etcd chart (OOM-2156) > >> * NBI to SDC: API is HTTPS with port 8443 (EXTAPI-341) > >> * VNFM-adapter health check failing (SO-2517) > >> * Fix the deployment issue (CLAMP-551) > >> * docs: Replace include directives for non existent file (OOM-2203) > >> * docs: Ensure literalinclude directive rendering (OOM-1612) > >> * Type in deployment.yaml forf cds-ui branch:elAlto (CCSDK-1953) > >> * Fix multicloud log message output issue (MULTICLOUD-966) > >> * update cert using secrets (DMAAP-1422) > >> * fix for the expiring cert (DMAAP-1438) > >> * [DMaaP] Remove "BOM" Character (OOM-2364) > >> * [GENERIC] follow elalto branches for submodules (OOM-2364) > >> * [AAI|ROBOT] track latest commits on submodules (OOM-2364) > >> * Workaround for cert expiration (DMAAP-1424) > >> * Portal certificate renewal (PORTAL-878) > >> * Fix: make all - returns multiple warnings (OOM-2412) > >> * deploy.sh does not work on Mac os x because untar directory is create… > >> (OOM-2407) > >> * [COMMON] Align Makefile with last changes (OOM-2412) > >> * AAF SMS] Override outdated certificates (AAF-1159) (*** NOT YET MERGED > >> ***) > >> > >> > >> I then believe that Policy, DMaaP, SDC and CCSDK/CDS should list commits > >> between the related releases in order to have the full > >> view of what would be OOM El Alto Maintenance Release 2 > >> > >> We have an issue on SO Api Handler today so we may have a new image > needed > >> > >> # Frankfurt > >> > >> 14 commits have (will for 2) been applied to El Alto branch since last > >> maintenance release: > >> > >> The following commits include code change in parent repo, so digging > >> between the two release is needed in order to know > >> what changed: > >> * Add new SO component so-appc-orchestrator to OOM (SO-2903) > >> new SO image: onap/so/so-appc-orchestrator:1.6.0 > >> * bump the SO version (SO-3022) > >> onap/so/bpmn-infra: 1.6.3 -> 1.6.4 > >> onap/so/catalog-db-adapter: 1.6.3 -> 1.6.4 > >> onap/so/so-monitoring: 1.6.3 -> 1.6.4 > >> onap/so/nssmf-adapter: 1.6.3 -> 1.6.4 > >> onap/so/openstack-adapter: 1.6.3 -> 1.6.4 > >> onap/so/request-db-adapter: 1.6.3 -> 1.6.4 > >> onap/so/sdc-controller: 1.6.3 -> 1.6.4 > >> onap/so/sdnc-adapter: 1.6.3 -> 1.6.4 > >> onap/so/ve-vnfm-adapter: 1.6.3 -> 1.6.4 > >> onap/so/vfc-adapter: 1.6.3 -> 1.6.4 > >> onap/so/vnfm-adapter: 1.6.3 -> 1.6.4 > >> onap/so/api-handler-infra: 1.6.3 -> 1.6.4 > >> * [CDS/SDNC] Update versions for Frankfurt mtce release (CCSDK-2519, > >> CCSDK-2399) > >> onap/ccsdk-blueprintsprocessor: 0.7.3 -> 0.7.5 > >> onap/ccsdk-commandexecutor: 0.7.3 -> 0.7.5 > >> onap/ccsdk-py-executor: 0.7.3 -> 0.7.5 > >> onap/ccsdk-sdclistener: 0.7.3 -> 0.7.5 > >> onap/ccsdk-cds-ui-server: 0.7.3 -> 0.7.5 > >> onap/sdnc-dmaap-listener-image: 1.8.3 -> 1.8.4 > >> onap/sdnc-ansible-server-image: 1.8.3 -> 1.8.4 > >> onap/admportal-sdnc-image: 1.8.3 -> 1.8.4 > >> onap/sdnc-ueb-listener-image: 1.8.3 -> 1.8.4 > >> onap/sdnc-image: 1.8.3 -> 1.8.4 > >> * [SDC] Update sdc images for Frankfurt (SDC-3189) (*** NOT YET MERGED > ***) > >> onap/sdc-backend: 1.6.6 -> 1.6.7 > >> onap/sdc-backend-init: 1.6.6 -> 1.6.7 > >> onap/sdc-cassandra: 1.6.6 -> 1.6.7 > >> onap/sdc-cassandra-init: 1.6.6 -> 1.6.7 > >> onap/sdc-frontend: 1.6.6 -> 1.6.7 > >> onap/sdc-onboard-backend: 1.6.6 -> 1.6.7 > >> onap/sdc-onboard-cassandra-init: 1.6.6 -> 1.6.7 > >> > >> > >> These are "OOM only" (change in helm charts, no new images): > >> * Add property enabling the py-executor component (CCSDK-2414) > >> * Fix SDNC DMAAP consumer properties in HELM charts (OOM-2400) > >> * Revert "[COMMON] add pre upgrade script for mariadb-galera" (INT-1633) > >> * [CLAMP] Allow to use ' in clamp mariadb passwords (CLAMP-878) > >> * [POLICY] add env passwords to api/pap/xacml/dist (POLICY-2575) > >> * point .gitreview to frankfurt branch (POLICY-2575) > >> * [SO] Sync up with the last-minute MSB certificate changes. (SO-2982) > >> * [CDS] Add hardcoded certificates to CDS (CCSDK-2410, CCSDK-2519) > >> * [COMMON] Allow to use ' in mariadb-init (OOM-2436) > >> * [AAF CertService] Increase certificates validity (AAF-1175) (*** NOT > >> YET MERGED ***) > >> > >> I then believe that SO, SDNC, SDC and CCSDK/CDS should list commits > >> between the related releases in order to have the > >> > >> full view of what would be OOM Frankfurt Maintenance Release 1. > >> > >> Regards > >> > >> Sylvain > >> > >> > _________________________________________________________________________________________________________________________ > >> > >> 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. > >> > > > > -- > Krzysztof Opasiak > Samsung R&D Institute Poland > Samsung Electronics > > > > > -- > > *David McBride* > > Release Manager > > Linux Foundation Networking (LFN) > > Mobile: +1.805.276.8018 > > Email: [email protected] > > IRC: dmcbride > > _________________________________________________________________________________________________________________________ > > > > 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. > > > > > -- *David McBride* Release Manager Linux Foundation Networking (LFN) Mobile: +1.805.276.8018 Email: [email protected] IRC: dmcbride -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#6794): https://lists.onap.org/g/onap-tsc/message/6794 Mute This Topic: https://lists.onap.org/mt/75414933/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
