[onap-tsc] Stepping down from TSC spot reserved for Bell Canada

Dear ONAP TSC, I would like to officially announce I’m stepping down as Bell Canada ONAP TSC rep, effective immediately; Olivier Phenix will be filling my position. Olivier is well versed around ONAP, as he is leading the team implementing and supporting it for Bell. I believe most of you

Re: [onap-tsc] Milestone Exception Process Timing Vote - Ends Wed., Nov 20 @ noon Pacific

> On Nov 14, 2019, at 2:30 PM, Kenny Paul wrote: > > VOTE: Does the TSC approve implementing the Milestone Exception Process > beginning with Frankfurt M2? > +1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5658):

Re: [onap-tsc] Courtesy update regarding the ONAP TSC Elections

Stephen, Thanks for all you’ve done at the TSC, you’ve been instrumental in our growth. Ciaran, welcome to TSC (nomination), looking forward working with you to continue on our journey. Regards, Alexis > On Nov 4, 2019, at 11:08 AM, Stephen Terrill via Lists.Onap.Org > wrote: > > Dear

[onap-tsc] Ali Daher will be my proxy today

Thanks team -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5257): https://lists.onap.org/g/onap-tsc/message/5257 Mute This Topic: https://lists.onap.org/mt/32515021/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe:

Re: [Onap-arc] [onap-tsc] New SDC repositories request

ONAP components are delivered in a somewhat monolith form, e.g. each container of each application have the same image tag, are never released individually, AFAIK. For instance, when there is a fix for one container, say in SDNC, it’s the all the SDNC containers that get released, same for SO,

[onap-tsc] Munir Ahmad to be my proxy until 15/07/2019

-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5163): https://lists.onap.org/g/onap-tsc/message/5163 Mute This Topic: https://lists.onap.org/mt/32230128/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe:

Re: [onap-tsc] Slack?

IIRC, it doesn’t work well in China: https://twitter.com/slackhq/status/968526959213936640 > On Jun 19, 2019, at 4:37 PM, Kenny Paul wrote: > > Can anyone please remind me again why Slack was deemed an undesirable IM > solution for

[onap-tsc] Is the meeting happening?

-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5111): https://lists.onap.org/g/onap-tsc/message/5111 Mute This Topic: https://lists.onap.org/mt/32052630/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe:

[onap-tsc] Munir will be my proxy during today's call

-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4797): https://lists.onap.org/g/onap-tsc/message/4797 Mute This Topic: https://lists.onap.org/mt/30811395/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe:

[onap-tsc] Munir will be my proxy during today's call

-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4782): https://lists.onap.org/g/onap-tsc/message/4782 Mute This Topic: https://lists.onap.org/mt/30695917/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe:

Re: [onap-tsc] [Onap-release] TSC Policy on ONAP Maintenance Release - Target Review: March 11th, 2019

I think we have a good enough proposal that we can start using. Time and experience will allow us to properly adjust the gating factor; also CD is getting better, and will certainly play a role in this. Alexis > On Mar 14, 2019, at 7:01 AM, Catherine LEFEVRE > wrote: > > Hi Stephen, > >

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

Robert Varga mailto:n...@hq.sk>>, "TIMONEY, DAN" > mailto:dt5...@att.com>> > Subject: Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities > > > > Sure Alexis - I will add this to the agenda next week. Earlier this week Anil > Belur was asking for

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

is week to have this. > > On Fri, Feb 8, 2019 at 7:06 AM Alexis de Talhouet <mailto:adetalhoue...@gmail.com>> wrote: > > >> On Feb 8, 2019, at 10:00 AM, Brian mailto:bf1...@att.com>> >> wrote: >> >> Since ONAP is Apache 2.0 and ODL is

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

> On Feb 8, 2019, at 10:00 AM, Brian wrote: > > Since ONAP is Apache 2.0 and ODL is EPL we dont think we can build a > distribution on the ONAP side that removes “ODL projects like TSDR, SXP > and similar”. It would be awesome if ONAP could build its own distro but I > dont think we know

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

22, 2019, at 4:28 PM, Alexis de Talhouet via Lists.Onap.Org > wrote: > > > >> On Jan 22, 2019, at 3:48 PM, Daniel Farrell > <mailto:dfarr...@redhat.com>> wrote: >> >> >> I have finally found the report and it's quite a few issues, so it's >&

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

> On Jan 22, 2019, at 3:48 PM, Daniel Farrell wrote: > > > I have finally found the report and it's quite a few issues, so it's > hard to break them down. > > First of all, I don't believe the list of issues flagged as coming from > OpenDaylight is accurate, as I compared the artifacts we

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

Dear ODL community, Luke, all, Could I get an update w.r.t. the vulnerabilities reported? Thanks, Alexis > On Jan 10, 2019, at 1:34 PM, Alexis de Talhouet via Lists.Onap.Org > wrote: > > Luke, all > > Following up on this. What is the current status? > > Regards,

Re: [onap-tsc] Mailing list netiquette

> On Jan 8, 2019, at 6:02 PM, Krzysztof Opasiak wrote: > > Please share your opinion about above issues. I do agree having ML practices for ONAP would be beneficial, and I’m all in favour the two mentioned points. I’m not sure how to enforce but I believe it is more a best / educational

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

o: onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org>; Daniel Farrell >> mailto:dfarr...@redhat.com>> >> Cc: Abhijit Kumbhare mailto:abhijitk...@gmail.com>>; >> mailto:t...@lists.opendaylight.org>> >> mailto:t...@lists.opendayligh

Re: [onap-tsc] [Onap-release] Release Management Update

Sad to see you changing focus; but your contribution has added tremendous value to the well being of ONAP. Thank you for all the great work, and good luck in your new endeavours. Cheers, Alexis > On Jan 2, 2019, at 3:48 PM, gildas.lani...@huawei.com wrote: > > Dear ONAP Community, > > With the

Re: [OpenDaylight TSC] [onap-tsc] CII Badging - Vulnerabilities

niel Farrell > mailto:dfarr...@redhat.com>> > Cc: Abhijit Kumbhare mailto:abhijitk...@gmail.com>>; > mailto:t...@lists.opendaylight.org>> > mailto:t...@lists.opendaylight.org>> > Subject: Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities > > > >

Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities

Awesome. Thank you for the reminder Daniel. I’ll loop in that list. Regards, Alexis > On Dec 7, 2018, at 3:56 PM, Daniel Farrell wrote: > > No, this list is exactly meant for this type of secret information. It's the > group of people the TSC has appointed as trusted to handle security

Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities

Daniel, Is the content of information provided through that mailing list publicly available? If yes, then I can’t provide the information to that list, as we don’t want to share publicly the vulnerabilities. Alexis > On Dec 7, 2018, at 3:50 PM, Daniel Farrell wrote: > > Hey Alexis, > >

Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities

Michael, Stephen, I sent you the information privately, as we should not share vulnerabilities publicly. Please only distribute internally to PTL and/or TSC. Regards, Alexis > On Dec 6, 2018, at 2:20 PM, Abhijit Kumbhare wrote: > > Thanks Alexis, Stephen and Michael. > > On Thu, Dec 6,

Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities

Michael, Stephen, Thank you for prompt response. I’ll get clarification on the vulnerabilities we have identified and will come back to you on the points you mentioned. Alexis > On Dec 6, 2018, at 1:06 PM, Stephen Kitt wrote: > > Hi Alexis, > > On Thu, 6 Dec 2018 17:57:29 +0100 > Michael

Re: [onap-tsc] CII Badging - Vulnerabilities

fix ONAP TSC mail > On Dec 6, 2018, at 11:05 AM, Alexis de Talhouët > wrote: > > Greeting ODL community, TSC, > > Within the ONAP community, we’re seeking CII badging. For that, we need to > eradicate critical vulnerabilities. > > Few ONAP projects are depending on OpenDaylight artifacts,

Re: [onap-tsc] TSC Special Election Results.

Congrats Chaker! And thank you Ramki for participation. > On Dec 3, 2018, at 3:32 PM, Brian wrote: > > Congrats Chaker ! > > From: onap-tsc@lists.onap.org > mailto:onap-tsc@lists.onap.org>> On Behalf Of Kenny > Paul > Sent: Monday, December 03, 2018 3:14 PM >

Re: [onap-tsc] URGENT: ONAP Casablanca RC2 Vote

> On Nov 27, 2018, at 12:05 PM, Kenny Paul wrote: > > Does the TSC approve the recommendations made during the Nov. 27th TSC RC2 > Review meeting that all projects pass the RC2 milestone? > +1, 0, -1 +1 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply

Re: [onap-tsc] New project proposal for Dublin and beyond...

Thank you for the link. I don’t see Alex’s project proposal, so I believe it hasn’t been submitted yet. Alexis > On Nov 27, 2018, at 8:24 AM, Lefevre, Catherine > wrote: > > Good morning Alex, Alexis, > > As requested previously, any proposed project for Dublin should be submitted > here: >

Re: [onap-tsc] Scale out use case documentation

Thanks for sharing Marco! Very insightful. Alexis > On Nov 26, 2018, at 3:31 PM, Marco Platania wrote: > > Dear ONAP Community, > > For Casablanca we deliver a new, improved scale out use case. These are some > of the major improvements/contributions: > > A design phase in which users define

Re: [onap-tsc] New project proposal for Dublin and beyond...

Alex, Do you have a link to the project proposal so we can start looking at it before TSC meeting? Thanks, Alexis > On Nov 26, 2018, at 3:21 PM, Alex Vul wrote: > > Hi Catherine, > > I have a Dublin project proposal for support of Composable Disaggregated > Infrastructure in ONAP. I would

Re: [onap-tsc] TSC Escalation - AAI/ESR Committer issue.

Hi, When it comes to define new committers for a given project, what I’ve seen happening before, and it worked fairly well, is to have the PTL of the project start a committer election of a week or two.. Contributors to the project can self-nominate themselves, and once nomination period is

Re: [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change waiver between SO and SDNC

mp; regards > Catherine > > From: onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org> > [mailto:onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org>] On Behalf > Of Alexis de Talhouet > Sent: Friday, October 12, 2018 4:59 AM > To: onap-tsc; onap-discuss &

Re: [onap-tsc] [TSC] Request API change waiver between SO and SDNC

)? >This question would help me understand if there is interaction > between SDNC and underlying VIM/Cloud instance > > Thanks > > Best Regards, > Bin Yang,Solution Engineering Team,Wind River > ONAP Multi-VIM/Cloud PTL > Direct +86,10,84777126 M

[onap-tsc] [TSC] Request API change waiver between SO and SDNC

Hello TSC, As discussed during today’s meeting, an issue has been identified in the new SO building block, introducing a regression in term of functionality from previous release. PTLs from both projects acknowledge and agree with the required changes. Expected behaviour: Have the cloud owner

Re: [onap-tsc] [Onap-lf-announce] [it-infrastructure-alerts] JIRA unavailable Thursday 6:00pm to 7:00pm PT time

FYI, if JIRA is not available, we can’t push any patch, as the commit hook to validate the Issue-ID within the patch is failing. Example: remote: Resolving deltas: 100% (26/26) remote: Processing changes: refs: 1, done remote: Non-existing issue ids referenced in commit message remote: The

Re: [onap-tsc] Agenda Preparation for the next TSC Call (Oct 4th, 2018)

Catherine, Thanks you for sharing the link. I added two items that I hope we will be able to discuss. Regards, Alexis > On Oct 1, 2018, at 10:50 AM, Catherine LEFEVRE > wrote: > > Dear ONAP Community, > > We would like to invite you to share any agenda item, that you would like to >

Re: [onap-tsc] Feed-back about features priority for Dublin

Here are a few other topics that I forget to mentioned that we would love to see prioritized in Dublin: - support for the applications to be deployed in a geo-redundant fashion (either active active/ active passive, ...) - support and integration of PNDA within DCAE/CLAMP - support for database

[onap-tsc] Feed-back about features priority for Dublin

Hello Alla, As discussed yesterday, a critical feature we’ve been looking for is the ability to enable self service of ONAP by our operational teams. With this in mind, during the Casablanca timeframe, Controller Design Studio has emerged . It’s goal is to create a common platform to all

Re: [onap-tsc] Join us at the ONS party and let's brainstorm about Dublin #ons europe 2018

Count me in as well. Alexis > On Sep 23, 2018, at 5:18 PM, Helen Chen wrote: > > Please count me in. It is fine for me to do at or after the reception. > > Regards, > > Helen Chen > > From: onap-tsc mailto:ONAP-TSC@lists.onap.org>> on > behalf of "LEFEVRE, CATHERINE"

Re: [onap-tsc] TSC Seat Vanacy

What happened in such scenario within the OpenDaylight community was to have the next runner appointed as the new TSC member, given previous election was very recent. Anyhow, I echo Frank’s point that it’s important current TSC come up with a way to handle such case, and that the TSC amends the

Re: [onap-tsc] 2018 TSC Election Results

Congrats to the new elected TSC! Alexis > On Aug 31, 2018, at 8:51 AM, Marisa Viveros wrote: > > +1 > > > Regards, > Marisa S. Viveros > IBM > > > From:"Alla Goldner" > > To:"ONAP-TSC@lists.onap.org " >

Re: [onap-discuss][onap-tsc][OOM] PTL Election for OOM

+1 > On Jul 18, 2018, at 1:52 PM, Mike Elliott wrote: > > Dear ONAP OOM Committers, > > I would like to nominate myself as Project Technical Lead (PTL) for the ONAP > Operations Manager (OOM) project. > > I have been a very active member of the OOM project since its inception. > Active in