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

[Alexis de Talhouet]

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 already know Olivier, and this is more a formality than a 
news.

It was a pleasure being part of this team, we achieved so much already! Keep up 
the great work.

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

View/Reply Online (#5973): https://lists.onap.org/g/onap-tsc/message/5973
Mute This Topic: https://lists.onap.org/mt/71608592/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

> 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): https://lists.onap.org/g/onap-tsc/message/5658
Mute This Topic: https://lists.onap.org/mt/58039315/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 All,
>
> I wanted to take a few moments to share a few words.  As you know I have been 
> involved with the ONAP journey from the TSC perspective (architecture and 
> SECCOM  as well) from its inception and have seen the creation and growth of 
> this community which has been an amazing journey.  We see that as part of 
> this journey, ONAP is now moving to a phase with ever increasing relevance 
> for product development, and as such we want to adjust our contribution to 
> the community (TSC) steering accordingly.For this purpose I am very happy 
> that Ciaran has stepped up to self nominate as I have been working with him 
> for quite some time and I am sure, if elected, he will do a great job - and 
> indeed he has also been my stand-in a number of times.  I wanted to add – 
> this is not an exit but a transformation - my intention to remain involved, 
> but from another supporting perspective as time allows.
>
> Best Regards,
>
> Steve
>
>  
>
> Stephen Terrill
> Senior Expert, Automation and Management
>
> TECHNOLOGY SPECIALIST
> BDGS RDP Architecture & Technology
> Phone: +34913393005
> Mobile: +34609168515
> stephen.terr...@ericsson.com 
>
> Ericsson
> C/ Via de los Poblados 13. B
> 28033,Madrid, Madrid
> Spain
> ericsson.com 
>
>  
>
> Our commitment to Technology for Good 
>  
> and Diversity and Inclusion 
>  contributes to 
> positive change.
> Follow us on: Facebook  LinkedIn 
>  Twitter 
> 
> 
> Legal entity:ERICSSON AB registration number 556056-6258, registered office 
> in Stockholm.
> This communication is confidential. Our email terms: 
> www.ericsson.com/en/legal/privacy/email-disclaimer 
> 
> 


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

View/Reply Online (#5576): https://lists.onap.org/g/onap-tsc/message/5576
Mute This Topic: https://lists.onap.org/mt/41267004/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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, AAI, etc...

Right now repo structure is somewhat free for all, making thing hard to grasp 
for new comers, to maintain for PTL, to debug/dev/search for developer, and to 
release for RelEng.

I agree having one repo per container can be ideal in some cases, but reality 
is currently different. With the number of containers in ONAP, I’m not 
convinced this is the best path forward. Having one repo per project with CI/CD 
based on sub-folders of the repo could be also a good answer to address the 
need (note: SO is *not* an example of that, having one module building all the 
images, rather than each module building their own).

I believe this is a very good discussion for TSC to have, in order to come up 
with best practices and then having them reflected across projects.

> On Jul 8, 2019, at 4:43 AM, Sylvain Desbureaux via Lists.Onap.Org 
>  wrote:
> 
> Hello Krzysztof,
> 
> That exactly was the " we should have a __clear__  (automated) policy on how 
> to upgrade the upstream components" so we're absolutely inline (. 
> 
> ---
> Sylvain Desbureaux 
> 
> Le 08/07/2019 10:42, « onap-tsc@lists.onap.org au nom de Krzysztof Opasiak 
> via Lists.Onap.Org »  k.opasiak=samsung@lists.onap.org> a écrit :
> 
> 
> 
>>On 08.07.2019 10:20, Sylvain Desbureaux via Lists.Onap.Org wrote:
>> Hello Kenny,
>> 
>> If I may I think that “micro” repos are a better way to handle code in a 
>> CI/CD world. Let’s take two examples:
>> 
>>  * SO: SO has (roughly) one project into ONAP git but delivers 13
>>containers. That means that 1 code change that should affect only
>>one of the containers will rebuild the 13 containers so it’s
>>__hard__ to debug at the end.
>>  * SDC: SDC has 21 repos (if I’m not mistaken) and delivers 13
>>containers also. That mean that 1 code change that should affect
>>only one of the containers __should__ rebuild 1 containers. I assume
>>that some repos could be merged together but not that much IMHO.
>> 
>> So for me a good practice is:
>> 
>>  * This “folder” / code produce 1 container àit should be a project
>>into gerrit
>>  * This “folder” / code is a common foundation for several containers
>>àit should be a project into gerrit and we should have a __clear__
>>(automated) policy on how to upgrade the upstream components.
> 
>I strongly agree with your point but I'd like to also add that in order 
>to fully benefit from multiple repo workflow we should start using 
>proper tags in gerrit (Depends-On:) if we are doing changes that affect 
>other repos and learn our CI/CD system to properly interpret that to 
>avoid fake failures in number of reviews...
> 
>Best regards,
>-- 
>Krzysztof Opasiak
>Samsung R Institute Poland
>Samsung Electronics
> 
> 
> 
> 
> 
> 
> _
> 
> 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 (#5193): https://lists.onap.org/g/onap-tsc/message/5193
Mute This Topic: https://lists.onap.org/mt/32389899/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

-=-=-=-=-=-=-=-=-=-=-=-
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: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] Slack?

[Alexis de Talhouet]

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?
>
> Thanks!
> -kenny
>
> 


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

View/Reply Online (#5120): https://lists.onap.org/g/onap-tsc/message/5120
Mute This Topic: https://lists.onap.org/mt/32131148/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Is the meeting happening?

[Alexis de Talhouet]

-=-=-=-=-=-=-=-=-=-=-=-
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: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

-=-=-=-=-=-=-=-=-=-=-=-
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: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

-=-=-=-=-=-=-=-=-=-=-=-
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: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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,
>
> Sorry for short add-ons
>
> I have got the following feedback
> Do we really need approval from TSC to deliver a patch ?
>This sounds like a step too far, a minor patch should always 
> be kept stable – can we have a limited impact assessment done prior to 
> executing the fix ?
>
> Timelines and support model looks good otherwise
>
> Best regards
> Catherine
>
> From: onap-tsc@lists.onap.org  
> [mailto:onap-tsc@lists.onap.org ] On Behalf 
> Of Stephen Terrill
> Sent: Tuesday, March 12, 2019 9:35 PM
> To: onap-tsc@lists.onap.org ; 
> 'onap-rele...@lists.onap.org ' 
> mailto:onap-rele...@lists.onap.org>>
> Subject: Re: [onap-tsc] [Onap-release] TSC Policy on ONAP Maintenance Release 
> - Target Review: March 11th, 2019
>
> Hi All,
>
> I was wondering whether there was more input regarding the what we should do 
> in the case of an individual project release vs a full ONAP release.
>
> BR,
>
> Steve.
>
> From: onap-rele...@lists.onap.org  
> mailto:onap-rele...@lists.onap.org>> On Behalf 
> Of Stephen Terrill
> Sent: Saturday 9 March 2019 15:22
> To: Eric Debeau mailto:eric.deb...@orange.com>>; 
> onap-tsc@lists.onap.org ; 
> 'onap-rele...@lists.onap.org ' 
> mailto:onap-rele...@lists.onap.org>>
> Subject: Re: [Onap-release] TSC Policy on ONAP Maintenance Release - Target 
> Review: March 11th, 2019
>
> Hi,
>
> As we couldn’t agree on an overall validation, some suggestions were to have 
> more validation, some less, so now that has to be part of the proposal for 
> that release.
>
> Regarding the integration of an individual project release in OOM, is that 
> really necessary – what would then be the different between an individual 
> project release and an overall ONAP release with just one project updated.  
> The idea, I thought, was to have an easy way for the projects to release bug 
> and security fix updates with as little overhead as possible.
>
> BR,
>
> Steve
>
> From: onap-rele...@lists.onap.org  
> mailto:onap-rele...@lists.onap.org>> On Behalf 
> Of Eric Debeau
> Sent: Saturday 9 March 2019 09:53
> To: onap-tsc@lists.onap.org ; 
> 'onap-rele...@lists.onap.org ' 
> mailto:onap-rele...@lists.onap.org>>
> Subject: Re: [Onap-release] TSC Policy on ONAP Maintenance Release - Target 
> Review: March 11th, 2019
>
> Hello
>
> Thanks for the material. It is clear we need a clear TSC Policy on ONAP 
> Maintenance Release. But, we also must improve our rules and tools (cf pbs 
> with Casablanca Maintenance Release). I believe that the proposal is missing 
> some technical points. For a patch release, we get a new Docker image for the 
> project. How is it reflected with OOM ? Who validates this new image: the 
> project, integration, OOM ?
>
> Slide 13: we should apply these tests for any patch and we need to improve 
> our gating process. I agree we may have different tests depending on the 
> projects (some of them are core components and their evolution may have huge 
> impact, while other peripherical components may have less impact).
> To be defined with Integration, OOM and CI/CD teams.
>
> Best Regards
>
> Eric
>
> De : onap-tsc@lists.onap.org  
> [mailto:onap-tsc@lists.onap.org ] De la part 
> de Catherine LEFEVRE
> Envoyé : samedi 9 mars 2019 00:14
> À : onap-tsc@lists.onap.org ; 
> 'onap-rele...@lists.onap.org '
> Objet : [onap-tsc] TSC Policy on ONAP Maintenance Release - Target Review: 
> March 11th, 2019
>
> Dear all,
>
> Stephen has enhanced the “TSC Policy on ONAP Maintenance Release” with your 
> feedback.
> The main issue last time was the individual release criteria.  Should there 
> be required health testing, pair wise testing, regression testing.
> For now it is left it as a decision to decide when the TSC makes the decision.
>
> https://jira.onap.org/secure/attachment/13434/Prosal%20for%20a%20TSC%20Policy%20on%20ONAP%20Release%20Maintenance-pa5.pptx
>  
> 
>
> If you have any additional 

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

[Alexis de Talhouet]

Abhijit,

Can we postpone to next Thursday TSC meeting, key resource aren’t available 
this week to
have this discussion.
People for this topic will be, Dan, Taka, Pawel and myself.

Thanks,
Alexis

> On Feb 11, 2019, at 3:02 PM, Abhijit Kumbhare  wrote:
> 
> For some reason, OpenDaylight TSC got dropped off this thread - added it 
> back. Looking forward to talking with you guys Alexis and folks.
> 
> On Fri, Feb 8, 2019 at 11:38 AM TIMONEY, DAN  <mailto:dt5...@att.com>> wrote:
> All,
> 
>
> 
> One clarification I wanted to make, re: Robert’s question about the list we’d 
> provided.
> 
>
> 
> The Nexus IQ server also reports on third party libraries that are embedded 
> within other jars.  For example, ODL Oxygen doesn’t ship netty 4.0.30, but 
> the jar for narayana-osgi-jta contains that version of netty.  I can tell 
> that because when I look at “Occurrences” of that library in the Nexus IQ 
> Server report, I see this:
> 
>
> 
> netty-all-4.0.30.Final.jar located at 
> opendaylight/oxygen/target/docker-stage/karaf-0.8.3.tar.gz/karaf-0.8.3/system/org/jboss/narayana/osgi/narayana-osgi-jta/5.5.2.Final/narayana-osgi-jta-5.5.2.Final.jar
> 
>
> 
>
> 
> I really wish we could just share the report, but unfortunately Sonatype told 
> us in no uncertain terms that sort of thing is a violation of their software 
> license terms.
> 
>
> 
> I just wanted to reassure you  all that I really did do my best to be careful 
> about separating out the vulnerabilities we’re inheriting from ODL from any 
> that we’re introducing ourselves.
> 
>
> 
> Dan
> 
> -- 
> 
> Dan Timoney
> 
> SDN-CP Development
> 
> ONAP Project Technical Lead : CCSDK and SDNC
> 
>
> 
> 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: Abhijit Kumbhare mailto:abhijitk...@gmail.com>>
> Date: Friday, February 8, 2019 at 11:06 AM
> To: "onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org>" 
> mailto:onap-tsc@lists.onap.org>>
> Cc: 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 the same to be on the agenda - but there was no time 
> this 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 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 how to do that without tainting.
> 
>
> 
> I tend to think we can. This is one of the things I want to discuss during 
> ODL TSC when it is the good time.
> 
>
> 
> 


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

View/Reply Online (#4616): https://lists.onap.org/g/onap-tsc/message/4616
Mute This Topic: https://lists.onap.org/mt/28708638/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

Thank you Abhijit. So we’ll be there on the 14th.
Alexis

> On Feb 8, 2019, at 11:05 AM, Abhijit Kumbhare  wrote:
> 
> Sure Alexis - I will add this to the agenda next week. Earlier this week Anil 
> Belur was asking for the same to be on the agenda - but there was no time 
> this 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 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 how to do that without tainting.
> 
> I tend to think we can. This is one of the things I want to discuss during 
> ODL TSC when it is the good time.
> 
> 
> 
> 


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

View/Reply Online (#4599): https://lists.onap.org/g/onap-tsc/message/4599
Mute This Topic: https://lists.onap.org/mt/28708638/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

> 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 how to do that without tainting.

I tend to think we can. This is one of the things I want to discuss during ODL 
TSC when it is the good time.


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

View/Reply Online (#4591): https://lists.onap.org/g/onap-tsc/message/4591
Mute This Topic: https://lists.onap.org/mt/28708638/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

Greeting ODL TSC,

I would like to add an item to next TSC agenda, to have a discussion 
following-up this mail-thread,
to see how we can move forward. Kindly let me know when would be a good time so 
we can have
the right persons from ONAP community to attend.

Thank you,
Alexis

> On Jan 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
>> 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 are shipped in
>> karaf-0.8.3.
>> 
>> We also did not ship netty-4.0.30, we shipped 4.1.22.
>> 
>> We did not ship the following artifacts at all:
>> commons-fileupload
>> artemis-commons
>> faces-impl
>> sendgrid-java
>> netty-4.0.30 -- we are shipped 4.1.22.Final
>> 
>> I could not find a public repository for the SONATYPE advisories -- does
>> anyone have a pointer? Without that I cannot evaluate them...
>> 
>> We have upgraded org.bouncycastle in Oxygen SR4, so at least those two
>> CVEs have been fixed.
>> 
>> Finally, it seems that quite a few issues are affecting
>> ccsdk/distribution, which are coming from ODL projects like TSDR, SXP
>> and similar. I am not sure whether ONAP really uses them, so it may be
>> worthwhile to take a look at how the distribution is assembled.
> 
> 
> Thanks Daniel for copying. Thanks Robert for the answer.
> 
> Brian, yes, Robert did reply with some preliminary answers. We should ingest 
> them
> and start triaging our list.
> Also, we should look into how we could build a custom distro out of ODL 
> released artifacts
> specific for ONAP, as as pointed by Robert, we might not need everything. I 
> actually think
> we mostly need NETCONF, that I’m aware of.
> 
> I’ll follow-up w/ Dan Timoney and that.
> 
> Regards,
> Alexis
> 


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

View/Reply Online (#4589): https://lists.onap.org/g/onap-tsc/message/4589
Mute This Topic: https://lists.onap.org/mt/28708638/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

> 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 are shipped in
> karaf-0.8.3.
> 
> We also did not ship netty-4.0.30, we shipped 4.1.22.
> 
> We did not ship the following artifacts at all:
> commons-fileupload
> artemis-commons
> faces-impl
> sendgrid-java
> netty-4.0.30 -- we are shipped 4.1.22.Final
> 
> I could not find a public repository for the SONATYPE advisories -- does
> anyone have a pointer? Without that I cannot evaluate them...
> 
> We have upgraded org.bouncycastle in Oxygen SR4, so at least those two
> CVEs have been fixed.
> 
> Finally, it seems that quite a few issues are affecting
> ccsdk/distribution, which are coming from ODL projects like TSDR, SXP
> and similar. I am not sure whether ONAP really uses them, so it may be
> worthwhile to take a look at how the distribution is assembled.


Thanks Daniel for copying. Thanks Robert for the answer.

Brian, yes, Robert did reply with some preliminary answers. We should ingest 
them
and start triaging our list.
Also, we should look into how we could build a custom distro out of ODL 
released artifacts
specific for ONAP, as as pointed by Robert, we might not need everything. I 
actually think
we mostly need NETCONF, that I’m aware of.

I’ll follow-up w/ Dan Timoney and that.

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

View/Reply Online (#4508): https://lists.onap.org/g/onap-tsc/message/4508
Mute This Topic: https://lists.onap.org/mt/28708638/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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,
> Alexis
> 
>> On Dec 10, 2018, at 8:13 AM, Luke Hinds > <mailto:lhi...@redhat.com>> wrote:
>> 
>> Hi Alexis,
>> 
>> We can see your email and you will see replies as your email will be in the 
>> reply all list , a reply is till pending, but its on our desk so to speak.
>> 
>> I discussed this with Stephen this morning and a reply will follow. initial 
>> analysis shows that a good number of false positives are reported.
>> 
>> Regards,
>> 
>> Luke
>> 
>> On Mon, Dec 10, 2018 at 1:10 PM Alexis de Talhouët > <mailto:adetalhoue...@gmail.com>> wrote:
>> Everyone, Daniel,
>> 
>> So I did send the mail to ODL security list, but message is getting held 
>> waiting for “moderator approval” 
>> 
>>> Your mail to 'security' with the subject
>>> 
>>>CII Badging - Vulnerabilities
>>> 
>>> Is being held until the list moderator can review it for approval.
>>> 
>>> The reason it is being held:
>>> 
>>>Post by non-member to a members-only list
>> 
>> 
>> I don’t know if this is intended or not, but as there is no way to register 
>> to such list I’m wondering if I missed something..
>> 
>> Stephen T, in this case, I’m following ODL process are I’m reporting 
>> vulnerabilities to their project; vulnerabilities we have identified within 
>> ONAP as part of the CII Badging requirement.
>> 
>> Regards,
>> Alexis
>> 
>> 
>>> On Dec 10, 2018, at 6:44 AM, Michael Vorburger >> <mailto:vorbur...@redhat.com>> wrote:
>>> 
>>> Hello everyone,
>>> 
>>> It's great to see that we do have a working formal security vulnerability 
>>> disclosure process in place in ODL.
>>> 
>>> I'll therefore let the members of that strucuture deal with this. If I can 
>>> be of any help for anything specific, please reach out to me.
>>> 
>>> Tx,
>>> M.
>>> --
>>> Michael Vorburger, Red Hat
>>> vorbur...@redhat.com <mailto:vorbur...@redhat.com> | IRC: vorburger 
>>> @freenode | ~ = http://vorburger.ch <http://vorburger.ch/>
>>> 
>>> On Sun, Dec 9, 2018 at 2:52 AM Stephen Terrill 
>>> mailto:stephen.terr...@ericsson.com>> wrote:
>>> Hi,
>>> 
>>>
>>> 
>>> Thanks. This maybe a good opportunity to point to this wiki for this 
>>> process.  https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management 
>>> <https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management>
>>>
>>> 
>>> This will be a good opportunity to test it out.
>>> 
>>>
>>> 
>>> BR,
>>> 
>>>
>>> 
>>> Steve
>>> 
>>>
>>> 
>>> From: onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org> 
>>> mailto:onap-tsc@lists.onap.org>> On Behalf Of 
>>> Kenny Paul
>>> Sent: Friday 7 December 2018 22:15
>>> To: 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.opendaylight.org>>
>>> Subject: Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities
>>> 
>>>
>>> 
>>> Perfect! Thanks Daniel!
>>> 
>>>
>>> 
>>> Thanks!
>>> 
>>> -kenny
>>> 
>>>
>>> 
>>>
>>> 
>>> From: mailto:onap-tsc@lists.onap.org>> on behalf 
>>> of Alexis de Talhouet >> <mailto:adetalhoue...@gmail.com>>
>>> Reply-To: mailto:onap-tsc@lists.onap.org>>
>>> Date: Friday, December 7, 2018 at 12:58 PM
>>> To: Daniel Farrell mailto:dfarr...@redhat.com>>
>>> Cc: Abhijit Kumbhare >> <mailto:abhijitk...@gmail.com>>, ">> <mailto:t...@lists.opendaylight.org>>" >> <mailto:t...@lists.opendaylight.org>>, >> <mailto:ONAP-TSC@lists.onap.org>>
>>> Subject: Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities
>>> 
>>

Re: [onap-tsc] Mailing list netiquette

[Alexis de Talhouet]

> 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 practices.

> If you would like to have some discussion about that or to present to 
> the broader audience on this topic I'm available during current event.


I believe it worth having a discussion about this; could be a 15mn item during
TSC meeting.

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

View/Reply Online (#4462): https://lists.onap.org/g/onap-tsc/message/4462
Mute This Topic: https://lists.onap.org/mt/29073941/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

Luke, all

Following up on this. What is the current status?

Regards,
Alexis

> On Dec 10, 2018, at 8:13 AM, Luke Hinds  wrote:
> 
> Hi Alexis,
> 
> We can see your email and you will see replies as your email will be in the 
> reply all list , a reply is till pending, but its on our desk so to speak.
> 
> I discussed this with Stephen this morning and a reply will follow. initial 
> analysis shows that a good number of false positives are reported.
> 
> Regards,
> 
> Luke
> 
> On Mon, Dec 10, 2018 at 1:10 PM Alexis de Talhouët  <mailto:adetalhoue...@gmail.com>> wrote:
> Everyone, Daniel,
> 
> So I did send the mail to ODL security list, but message is getting held 
> waiting for “moderator approval” 
> 
>> Your mail to 'security' with the subject
>> 
>>CII Badging - Vulnerabilities
>> 
>> Is being held until the list moderator can review it for approval.
>> 
>> The reason it is being held:
>> 
>>Post by non-member to a members-only list
> 
> 
> I don’t know if this is intended or not, but as there is no way to register 
> to such list I’m wondering if I missed something..
> 
> Stephen T, in this case, I’m following ODL process are I’m reporting 
> vulnerabilities to their project; vulnerabilities we have identified within 
> ONAP as part of the CII Badging requirement.
> 
> Regards,
> Alexis
> 
> 
>> On Dec 10, 2018, at 6:44 AM, Michael Vorburger > <mailto:vorbur...@redhat.com>> wrote:
>> 
>> Hello everyone,
>> 
>> It's great to see that we do have a working formal security vulnerability 
>> disclosure process in place in ODL.
>> 
>> I'll therefore let the members of that strucuture deal with this. If I can 
>> be of any help for anything specific, please reach out to me.
>> 
>> Tx,
>> M.
>> --
>> Michael Vorburger, Red Hat
>> vorbur...@redhat.com <mailto:vorbur...@redhat.com> | IRC: vorburger 
>> @freenode | ~ = http://vorburger.ch <http://vorburger.ch/>
>> 
>> On Sun, Dec 9, 2018 at 2:52 AM Stephen Terrill > <mailto:stephen.terr...@ericsson.com>> wrote:
>> Hi,
>> 
>>
>> 
>> Thanks. This maybe a good opportunity to point to this wiki for this 
>> process.  https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management 
>> <https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management>
>>
>> 
>> This will be a good opportunity to test it out.
>> 
>>
>> 
>> BR,
>> 
>>
>> 
>> Steve
>> 
>>
>> 
>> From: onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org> 
>> mailto:onap-tsc@lists.onap.org>> On Behalf Of 
>> Kenny Paul
>> Sent: Friday 7 December 2018 22:15
>> To: 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.opendaylight.org>>
>> Subject: Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities
>> 
>>
>> 
>> Perfect! Thanks Daniel!
>> 
>>
>> 
>> Thanks!
>> 
>> -kenny
>> 
>>
>> 
>>
>> 
>> From: mailto:onap-tsc@lists.onap.org>> on behalf 
>> of Alexis de Talhouet > <mailto:adetalhoue...@gmail.com>>
>> Reply-To: mailto:onap-tsc@lists.onap.org>>
>> Date: Friday, December 7, 2018 at 12:58 PM
>> To: Daniel Farrell mailto:dfarr...@redhat.com>>
>> Cc: Abhijit Kumbhare mailto:abhijitk...@gmail.com>>, 
>> "mailto:t...@lists.opendaylight.org>>" 
>> mailto:t...@lists.opendaylight.org>>, 
>> mailto:ONAP-TSC@lists.onap.org>>
>> Subject: 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 > <mailto:dfarr...@redhat.com>> 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 issues. 
>> They will follow all the normal security embargo best practices.
>> 
>>
>> 
>> Thanks,
>> 
>> Daniel
>> 
>> On Fri, Dec 7, 2018 at 9:52 PM Alexis de Talhouët > <mailto:adetalhoue...@gmail.com>> wrote:
>> 
>

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

[Alexis de Talhouet]

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 new year, comes the time for new resolutions and changes.
> The first one is easy to articulate as I wish you all and the ones around you 
> Happy New 2019 year.
> For the second, it is with deep regrets and a broken heart to announce that I 
> will no longer have the privilege to be the ONAP Release Manager. This was 
> announced to the Community back in September 2018 and becomes effective today.
> In the meantime, Catherine will be covering on Release Management and Release 
> Coordinator duties until further notice.
> I will be attending the ONAP-OPNFV developers conference in Paris next week 
> for new endeavors with Huawei and transfer any information the community 
> needs.
> It has been an honor to help the community and working with you all.
> I wish ONAP great success and a lot of deployments.
>
> Thanks,
> Gildas
> 
> Gildas Lanilis
> Santa Clara CA, USA
> gildas.lani...@huawei.com 
> Mobile: 1 415 238 6287 
>
> 


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

View/Reply Online (#4382): https://lists.onap.org/g/onap-tsc/message/4382
Mute This Topic: https://lists.onap.org/mt/28917621/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

Everyone, Daniel,

So I did send the mail to ODL security list, but message is getting held 
waiting for “moderator approval” 

> Your mail to 'security' with the subject
> 
>CII Badging - Vulnerabilities
> 
> Is being held until the list moderator can review it for approval.
> 
> The reason it is being held:
> 
>Post by non-member to a members-only list


I don’t know if this is intended or not, but as there is no way to register to 
such list I’m wondering if I missed something..

Stephen T, in this case, I’m following ODL process are I’m reporting 
vulnerabilities to their project; vulnerabilities we have identified within 
ONAP as part of the CII Badging requirement.

Regards,
Alexis


> On Dec 10, 2018, at 6:44 AM, Michael Vorburger  wrote:
> 
> Hello everyone,
> 
> It's great to see that we do have a working formal security vulnerability 
> disclosure process in place in ODL.
> 
> I'll therefore let the members of that strucuture deal with this. If I can be 
> of any help for anything specific, please reach out to me.
> 
> Tx,
> M.
> --
> Michael Vorburger, Red Hat
> vorbur...@redhat.com <mailto:vorbur...@redhat.com> | IRC: vorburger @freenode 
> | ~ = http://vorburger.ch <http://vorburger.ch/>
> 
> On Sun, Dec 9, 2018 at 2:52 AM Stephen Terrill  <mailto:stephen.terr...@ericsson.com>> wrote:
> Hi,
> 
>
> 
> Thanks. This maybe a good opportunity to point to this wiki for this process. 
>  https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management 
> <https://wiki.onap.org/display/DW/ONAP+Vulnerability+Management>
>
> 
> This will be a good opportunity to test it out.
> 
>
> 
> BR,
> 
>
> 
> Steve
> 
>
> 
> From: onap-tsc@lists.onap.org <mailto:onap-tsc@lists.onap.org> 
> mailto:onap-tsc@lists.onap.org>> On Behalf Of Kenny 
> Paul
> Sent: Friday 7 December 2018 22:15
> To: 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.opendaylight.org>>
> Subject: Re: [onap-tsc] [OpenDaylight TSC] CII Badging - Vulnerabilities
> 
>
> 
> Perfect! Thanks Daniel!
> 
>
> 
> Thanks!
> 
> -kenny
> 
>
> 
>
> 
> From: mailto:onap-tsc@lists.onap.org>> on behalf of 
> Alexis de Talhouet mailto:adetalhoue...@gmail.com>>
> Reply-To: mailto:onap-tsc@lists.onap.org>>
> Date: Friday, December 7, 2018 at 12:58 PM
> To: Daniel Farrell mailto:dfarr...@redhat.com>>
> Cc: Abhijit Kumbhare mailto:abhijitk...@gmail.com>>, 
> "mailto:t...@lists.opendaylight.org>>" 
> mailto:t...@lists.opendaylight.org>>, 
> mailto:ONAP-TSC@lists.onap.org>>
> Subject: 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  <mailto:dfarr...@redhat.com>> 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 issues. 
> They will follow all the normal security embargo best practices.
> 
>
> 
> Thanks,
> 
> Daniel
> 
> On Fri, Dec 7, 2018 at 9:52 PM Alexis de Talhouët  <mailto:adetalhoue...@gmail.com>> wrote:
> 
> 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  <mailto:dfarr...@redhat.com>> wrote:
> 
>
> 
> Hey Alexis,
> 
>
> 
> Reminder that we have a security response team that's meant to handle these 
> types of things. Stephen is on the security response team, but you might 
> still be better off sharing with that group vs Stephen and Michael directly. 
> We asked for these details to be sent to that list months ago when ONAP folks 
> first mentioned these scanning issues, but last time I talked to Stephen 
> about it they still hadn't been sent.
> 
>
> 
> secur...@lists.opendaylight.org <mailto:secur...@lists.opendaylight.org>
>
> 
> We appreciate ONAP working with us to make sure we're the best upstream we 
> can be. Looking forward to benefiting both projects by working together more 
> closely.
> 
> 
> Daniel
> 
>
&g

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

[Alexis de Talhouet]

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 issues. 
> They will follow all the normal security embargo best practices.
> 
> Thanks,
> Daniel
> 
> On Fri, Dec 7, 2018 at 9:52 PM Alexis de Talhouët  > wrote:
> 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,
>> 
>> Reminder that we have a security response team that's meant to handle these 
>> types of things. Stephen is on the security response team, but you might 
>> still be better off sharing with that group vs Stephen and Michael directly. 
>> We asked for these details to be sent to that list months ago when ONAP 
>> folks first mentioned these scanning issues, but last time I talked to 
>> Stephen about it they still hadn't been sent.
>> 
>> secur...@lists.opendaylight.org 
>> 
>> We appreciate ONAP working with us to make sure we're the best upstream we 
>> can be. Looking forward to benefiting both projects by working together more 
>> closely.
>> 
>> Daniel
>> 
>> On Fri, Dec 7, 2018 at 8:16 PM Alexis de Talhouët > > wrote:
>> 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, 2018 at 10:16 AM Alexis de Talhouët >> > wrote:
>>> 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 Vorburger mailto:vorbur...@redhat.com>> 
>>> > wrote:
>>> >>> On Dec 6, 2018, at 11:05 AM, Alexis de Talhouët
>>> >>> mailto:adetalhoue...@gmail.com>> 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, such as
>>> >>> CCSDK, and we’re seeing a fair amount of vulnerabilities coming
>>> >>> from OpenDaylight; precisely, 130 vulnerabilities in our CCSDK CLM
>>> >>> reports that were found in the ODL Oxygen SR3 distribution,
>>> >>> documented here
>>> >>> https://wiki.onap.org/pages/viewpage.action?pageId=45300857 
>>> >>> . The
>>> >>> document is high level information providing only the groupId of
>>> >>> the maven artifact. I don’t have permission to see ODL projects in
>>> >>> LF Nexus-ID: https://nexus-iq.wl.linuxfoundation.org 
>>> >>> , so I can't
>>> >>> link directly reports here.
>>> >>> 
>>> >>> Point is, we would like to know where ODL stands with regards to CII
>>> >>> Badging; is that something you’re seeking?
>>> > 
>>> > Not actively, but we do care about fixing vulnerabilities.
>>> > 
>>> >>> Regardless, we would like to know if ODL is willing to address
>>> >>> critical vulnerabilities impacting ONAP?
>>> > 
>>> > Yes, we are.
>>> > 
>>> >> I just had a (quick) look at wiki.onap.org , and 
>>> >> was wondering if you
>>> >> guys would be willing to help us help you more, by:
>>> >> 
>>> >> - clarifying details about the vulnerability, like a link to a CVE
>>> > 
>>> > +1
>>> > 
>>> >> - first check out Fluorine or even better already Neon; at least some
>>> >> of the Karaf related ones likely are already solved
>>> > 
>>> > At least, check Oxygen SR4 when it’s available. I’m also not entirely
>>> > sure how the analysis matches up with Oxygen SR3; for example, the
>>> > version of Guava in SR3 is 23.6.1, which fixes the known
>>> > vulnerabilities. CLM also flags a number of false positives, e.g.
>>> > commons-fileupload (1.3.3 in SR3) which is fixed AFAIK.
>>> > 
>>> >> - clarify where you found the artifact... there are (to me) some
>>> >> surprises in your list; e.g. sendgrid or angular I wouldn't know
>>> >> where that is used by what project in ODL
>>> > 
>>> > +1
>>> > 
>>> >> - dedupe your list - it looks a lot longer than it 

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

[Alexis de Talhouet]

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,
> 
> Reminder that we have a security response team that's meant to handle these 
> types of things. Stephen is on the security response team, but you might 
> still be better off sharing with that group vs Stephen and Michael directly. 
> We asked for these details to be sent to that list months ago when ONAP folks 
> first mentioned these scanning issues, but last time I talked to Stephen 
> about it they still hadn't been sent.
> 
> secur...@lists.opendaylight.org 
> 
> We appreciate ONAP working with us to make sure we're the best upstream we 
> can be. Looking forward to benefiting both projects by working together more 
> closely.
> 
> Daniel
> 
> On Fri, Dec 7, 2018 at 8:16 PM Alexis de Talhouët  > wrote:
> 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, 2018 at 10:16 AM Alexis de Talhouët > > wrote:
>> 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 Vorburger mailto:vorbur...@redhat.com>> 
>> > wrote:
>> >>> On Dec 6, 2018, at 11:05 AM, Alexis de Talhouët
>> >>> mailto:adetalhoue...@gmail.com>> 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, such as
>> >>> CCSDK, and we’re seeing a fair amount of vulnerabilities coming
>> >>> from OpenDaylight; precisely, 130 vulnerabilities in our CCSDK CLM
>> >>> reports that were found in the ODL Oxygen SR3 distribution,
>> >>> documented here
>> >>> https://wiki.onap.org/pages/viewpage.action?pageId=45300857 
>> >>> . The
>> >>> document is high level information providing only the groupId of
>> >>> the maven artifact. I don’t have permission to see ODL projects in
>> >>> LF Nexus-ID: https://nexus-iq.wl.linuxfoundation.org 
>> >>> , so I can't
>> >>> link directly reports here.
>> >>> 
>> >>> Point is, we would like to know where ODL stands with regards to CII
>> >>> Badging; is that something you’re seeking?
>> > 
>> > Not actively, but we do care about fixing vulnerabilities.
>> > 
>> >>> Regardless, we would like to know if ODL is willing to address
>> >>> critical vulnerabilities impacting ONAP?
>> > 
>> > Yes, we are.
>> > 
>> >> I just had a (quick) look at wiki.onap.org , and 
>> >> was wondering if you
>> >> guys would be willing to help us help you more, by:
>> >> 
>> >> - clarifying details about the vulnerability, like a link to a CVE
>> > 
>> > +1
>> > 
>> >> - first check out Fluorine or even better already Neon; at least some
>> >> of the Karaf related ones likely are already solved
>> > 
>> > At least, check Oxygen SR4 when it’s available. I’m also not entirely
>> > sure how the analysis matches up with Oxygen SR3; for example, the
>> > version of Guava in SR3 is 23.6.1, which fixes the known
>> > vulnerabilities. CLM also flags a number of false positives, e.g.
>> > commons-fileupload (1.3.3 in SR3) which is fixed AFAIK.
>> > 
>> >> - clarify where you found the artifact... there are (to me) some
>> >> surprises in your list; e.g. sendgrid or angular I wouldn't know
>> >> where that is used by what project in ODL
>> > 
>> > +1
>> > 
>> >> - dedupe your list - it looks a lot longer than it really is, many
>> >> dupes ;)
>> > 
>> > I think this is because the artifacts aren’t fully described: we need
>> > the artifactId as well as the groupId, and ideally the version.
>> > 
>> > Regards,
>> > 
>> > Stephen
>> 
>> ___
>> TSC mailing list
>> t...@lists.opendaylight.org 
>> https://lists.opendaylight.org/mailman/listinfo/tsc 
>> 
> 
> ___
> TSC mailing list
> t...@lists.opendaylight.org 
> 

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

[Alexis de Talhouet]

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, 2018 at 10:16 AM Alexis de Talhouët  > wrote:
> 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 Vorburger mailto:vorbur...@redhat.com>> 
> > wrote:
> >>> On Dec 6, 2018, at 11:05 AM, Alexis de Talhouët
> >>> mailto:adetalhoue...@gmail.com>> 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, such as
> >>> CCSDK, and we’re seeing a fair amount of vulnerabilities coming
> >>> from OpenDaylight; precisely, 130 vulnerabilities in our CCSDK CLM
> >>> reports that were found in the ODL Oxygen SR3 distribution,
> >>> documented here
> >>> https://wiki.onap.org/pages/viewpage.action?pageId=45300857 
> >>> . The
> >>> document is high level information providing only the groupId of
> >>> the maven artifact. I don’t have permission to see ODL projects in
> >>> LF Nexus-ID: https://nexus-iq.wl.linuxfoundation.org 
> >>> , so I can't
> >>> link directly reports here.
> >>> 
> >>> Point is, we would like to know where ODL stands with regards to CII
> >>> Badging; is that something you’re seeking?
> > 
> > Not actively, but we do care about fixing vulnerabilities.
> > 
> >>> Regardless, we would like to know if ODL is willing to address
> >>> critical vulnerabilities impacting ONAP?
> > 
> > Yes, we are.
> > 
> >> I just had a (quick) look at wiki.onap.org , and 
> >> was wondering if you
> >> guys would be willing to help us help you more, by:
> >> 
> >> - clarifying details about the vulnerability, like a link to a CVE
> > 
> > +1
> > 
> >> - first check out Fluorine or even better already Neon; at least some
> >> of the Karaf related ones likely are already solved
> > 
> > At least, check Oxygen SR4 when it’s available. I’m also not entirely
> > sure how the analysis matches up with Oxygen SR3; for example, the
> > version of Guava in SR3 is 23.6.1, which fixes the known
> > vulnerabilities. CLM also flags a number of false positives, e.g.
> > commons-fileupload (1.3.3 in SR3) which is fixed AFAIK.
> > 
> >> - clarify where you found the artifact... there are (to me) some
> >> surprises in your list; e.g. sendgrid or angular I wouldn't know
> >> where that is used by what project in ODL
> > 
> > +1
> > 
> >> - dedupe your list - it looks a lot longer than it really is, many
> >> dupes ;)
> > 
> > I think this is because the artifacts aren’t fully described: we need
> > the artifactId as well as the groupId, and ideally the version.
> > 
> > Regards,
> > 
> > Stephen
> 
> ___
> TSC mailing list
> t...@lists.opendaylight.org 
> https://lists.opendaylight.org/mailman/listinfo/tsc 
> 


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

View/Reply Online (#4277): https://lists.onap.org/g/onap-tsc/message/4277
Mute This Topic: https://lists.onap.org/mt/28628360/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 Vorburger  wrote:
>>> 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, such as
>>> CCSDK, and we’re seeing a fair amount of vulnerabilities coming
>>> from OpenDaylight; precisely, 130 vulnerabilities in our CCSDK CLM
>>> reports that were found in the ODL Oxygen SR3 distribution,
>>> documented here
>>> https://wiki.onap.org/pages/viewpage.action?pageId=45300857. The
>>> document is high level information providing only the groupId of
>>> the maven artifact. I don’t have permission to see ODL projects in
>>> LF Nexus-ID: https://nexus-iq.wl.linuxfoundation.org, so I can't
>>> link directly reports here.
>>> 
>>> Point is, we would like to know where ODL stands with regards to CII
>>> Badging; is that something you’re seeking?
> 
> Not actively, but we do care about fixing vulnerabilities.
> 
>>> Regardless, we would like to know if ODL is willing to address
>>> critical vulnerabilities impacting ONAP?
> 
> Yes, we are.
> 
>> I just had a (quick) look at wiki.onap.org, and was wondering if you
>> guys would be willing to help us help you more, by:
>> 
>> - clarifying details about the vulnerability, like a link to a CVE
> 
> +1
> 
>> - first check out Fluorine or even better already Neon; at least some
>> of the Karaf related ones likely are already solved
> 
> At least, check Oxygen SR4 when it’s available. I’m also not entirely
> sure how the analysis matches up with Oxygen SR3; for example, the
> version of Guava in SR3 is 23.6.1, which fixes the known
> vulnerabilities. CLM also flags a number of false positives, e.g.
> commons-fileupload (1.3.3 in SR3) which is fixed AFAIK.
> 
>> - clarify where you found the artifact... there are (to me) some
>> surprises in your list; e.g. sendgrid or angular I wouldn't know
>> where that is used by what project in ODL
> 
> +1
> 
>> - dedupe your list - it looks a lot longer than it really is, many
>> dupes ;)
> 
> I think this is because the artifacts aren’t fully described: we need
> the artifactId as well as the groupId, and ideally the version.
> 
> Regards,
> 
> Stephen


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

View/Reply Online (#4272): https://lists.onap.org/g/onap-tsc/message/4272
Mute This Topic: https://lists.onap.org/mt/28628360/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] CII Badging - Vulnerabilities

[Alexis de Talhouet]

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, such as CCSDK, and 
> we’re seeing a fair amount of vulnerabilities coming from OpenDaylight; 
> precisely, 130 vulnerabilities in our CCSDK CLM reports that were found in 
> the ODL Oxygen SR3 distribution, documented here 
> https://wiki.onap.org/pages/viewpage.action?pageId=45300857 
> . The document 
> is high level information providing only the groupId of the maven artifact. I 
> don’t have permission to see ODL projects in LF Nexus-ID: 
> https://nexus-iq.wl.linuxfoundation.org 
> , so I can't link directly reports 
> here.
> 
> Point is, we would like to know where ODL stands with regards to CII Badging; 
> is that something you’re seeking?
> 
> Regardless, we would like to know if ODL is willing to address critical 
> vulnerabilities impacting ONAP?
> 
> Regards,
> Alexis


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

View/Reply Online (#4271): https://lists.onap.org/g/onap-tsc/message/4271
Mute This Topic: https://lists.onap.org/mt/28627055/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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
> To: onap-tsc@lists.onap.org 
> Subject: [onap-tsc] TSC Special Election Results.
>
> Congrats to Chaker for being elected to the TSC.
> https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_234d1ee32f8790a8 
> 
>
>
> Best Regards, 
> -kenny
> 
> Kenny Paul, Technical Program Manager, The Linux Foundation
> kp...@linuxfoundation.org , 510.766.5945 
> 
> San Francisco Bay Area, Pacific Time Zone
>
>
> 


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

View/Reply Online (#4233): https://lists.onap.org/g/onap-tsc/message/4233
Mute This Topic: https://lists.onap.org/mt/28575409/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

> 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 Online (#4181): https://lists.onap.org/g/onap-tsc/message/4181
Mute This Topic: https://lists.onap.org/mt/28372693/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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:
> https://wiki.onap.org/display/DW/Proposed+Projects+for+Dublin+Release 
> 
>
> Please note that any new project should be reviewed by the Architecture 
> Subcommittee prior any ONAP TSC review/decision.
>
> Additional information:
> https://lists.onap.org/g/onap-tsc/topic/proposed_projects_for_dublin/28021671?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,40,28021671
>  
> 
>
> Many thanks and regards
> Catherine
>
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
> Sent: Monday, November 26, 2018 9:54 PM
> To: onap-tsc@lists.onap.org
> Cc: Lefevre, Catherine 
> Subject: 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 like to review this proposal with the TSC. Is 
> there an opportunity to do so this Thursday’s meeting on November 29th?
>
> Thanks in advance, 
>
> Alex Vul
> Intel Corporation
>
> 


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

View/Reply Online (#4158): https://lists.onap.org/g/onap-tsc/message/4158
Mute This Topic: https://lists.onap.org/mt/28324908/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 and deploy policies and closed-loops 
> from CLAMP;
> Closed-loop- and Policy-based automation;
> Guard policies that allow/deny scale out operations based on frequency limits 
> or max number of instances already scaled;
> New and improved workflow that leverages SO ability to compose building 
> blocks on the fly;
> Use of Generic Resource APIs for VNF instantiation and lifecycle management 
> (as opposed to the old VNF APIs);
> VNF health check;
> Support for multiple VNF types;
> Support for multiple VNF controllers, i.e. APPC (officially supported) and 
> SDNC (experimental);
> Ability to define lifecycle management configuration from CLAMP (automated 
> trigger) or VID (manual trigger).
> Scale out has been tested against the latest released docker images (RC2). I 
> just created a wiki page that describes how to run the use case: 
> https://wiki.onap.org/display/DW/Running+Scale+Out+Use+Case+for+Casablanca 
>   
> It includes videos and material that has been used for the demonstration.
>
> Please let me know if you have any issues when visualizing the page or videos.
>
> Thanks,
> Marco
>
> 


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

View/Reply Online (#4151): https://lists.onap.org/g/onap-tsc/message/4151
Mute This Topic: https://lists.onap.org/mt/28325064/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 like to review this proposal with the TSC. Is 
> there an opportunity to do so this Thursday’s meeting on November 29th?
>
> Thanks in advance, 
>
> Alex Vul
> Intel Corporation
>
> 


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

View/Reply Online (#4150): https://lists.onap.org/g/onap-tsc/message/4150
Mute This Topic: https://lists.onap.org/mt/28324908/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 over, committers vote 
whether each nominee can become committer by assessing their involvement in the 
project (e.g. meritocracy).
It is generally good to perform such committer election at the beginning of 
each release, as it allows to make sure we don’t have an un-healthy project 
with not enough committers, and also to recognize work that has been done 
during previous release. It is also good practice to refresh project’s 
committer list by making sure all committers are *active*.

In this case, I would suggest to run a committer election within the project. 
That way, who ever feels then can take on the committer role can candidate.
In the case no one show up, then it’s a different discussion. In the case ppl 
showing up don’t have any contribution to that specific project is up to the 
actual committers to decide what to do.
Once new committers have been elected within the project, PTL sends a mail to 
TSC asking to vote on whether new committers can be approved or not. Knowing 
the background / history of the project, TSC should be able to judge the 
candidate accordingly, making sure the project can be in a healthy state.

I don’t know who is aai/esr-* PTL, but committer election should be held. Lv Bo 
should step up (maybe some other will), the aai/esr-* committers vote, e.g. Li 
Zi and Sun QI vote, then PTL present to TSC with new potential committer(s), 
being, among other, Lv Bo. And we can have that as an TSC agenda item to 
discuss briefly whether we agree to have Lv Bo committer knowing the history.

Regards,
Alexis

> On Oct 16, 2018, at 10:03 PM, Kenny Paul  wrote:
> 
> Jimmy tried to pursue the correct channels to resolve the following issue but 
> he is stuck, so I'm formally escalating it to the TSC.
>
> Li Zi, (li.z...@zte.com.cn ) has been the primary 
> code contributor and Committer to the ESR sub project of AAI. She is no 
> longer participating in the ONAP project and security fixes are required for 
> the Casablanca Release.
> · Li Zi requested that Lv Bo (lv.bo...@zte.com.cn 
> ) be assigned as her replacement. This is not 
> allowed as it violates sections 3.1.1   Contributor 
> 
>  & 3.1.2   Committer 
> 
>  of the ONAP Technical Community document:
> Committers cannot be appointed, they must be meritocracy elected from the 
> pool of active Contributors to that project's repositories
> There is no record of Lv Bo ever making a contribution to the aai/esr-* 
> repositories.
> ( There have been numerous code contributions to a different ONAP project:  
> msb/service-mesh )
>
> The only Committers on the aai/esr-* repos are Li Zi, (li.z...@zte.com.cn 
> ) and Sun Qi (sun.qi...@zte.com.cn 
> ). Both were the only individuals listed on the 
> original project submission form 
> https://wiki.onap.org/pages/viewpage.action?pageId=5734948 
> 
>
> In terms of Committer responsibilities, Sun Qi has made +2 all of Li Zi's 
> contributions to aai/esr-*. Exclusively. There are no records of code reviews 
> being performed for any contributor other than Li Zi.  There is no record of 
> any code contributions being made by Sun Qi.
>
> Based upon the fact that self merges are not permitted, nothing can be done.
>
> The guidance the TSC needs to provide here is:
> Recommend that Jimmy work with Sun Qi to nominate one of the individuals 
> below to Committer status
> 
> Recommend that Jimmy pursue an exception to section 3.2.2.1 Adding 
> Committers 
> 
>  by filling out a Committer Promotion Request for Lv Bo, backed by 
> contributions made outside of the AAI project
> 
> Decide to take action based upon section 3.2.2.2 Adding Committers to 
> moribund projects 
> 
>  to appoint a Committer from the list below.
>
> Contributors to the aai/esr-* repos over the past 6 months:
> Submitter
> 
> Repository
> 
> Status
> 
> created
> 
> Summary
> 
> Bin Yang
> 
> aai/esr-server
> 
> NEW
> 
> 2018-09-03
> 
> Refactor cloud region registration logic
> 
> Gary Wu
> 
> aai/esr-server
> 
> NEW
> 
> 2018-08-24
> 
> Use managed guava version
> 

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

[Alexis de Talhouet]

+1 from me, obviously :)  - Proxy for David Sauvageau

> On Oct 12, 2018, at 8:34 AM, Ning So  wrote:
> 
> ＋1.
> 
> Ning So
> 
> 
>  Original Message 
> Subject: [External]Re: [onap-tsc-vote] [onap-tsc] [TSC] Request API change 
> waiver between SO and SDNC
> From: Catherine LEFEVRE  <mailto:catherine.lefe...@intl.att.com>>
> Date: Oct 12, 2018, 5:43 AM
> To: onap-tsc@lists.onap.org 
> <mailto:onap-tsc@lists.onap.org>,onap-tsc-v...@lists.onap.org 
> <mailto:onap-tsc-v...@lists.onap.org>
> The e-mail below is from an external source. Please do not open attachments 
> or click links from an unknown or suspicious origin.
> 
> 
> Good morning Alexis,
>
> Thank you for your leadership supporting the teams to progress quickly on 
> this issue.
> I am adding the TSC vote distro list in order to increase the visibility of 
> this request.
>
> TSC Members (or proxy)
> Please vote (+1 waiver approved, 0-neutral, -1 waiver not approved) no later 
> than Oct 13th End of your Day.
> ·Andreas Geissler (DT)
> ·Ranny Haiby, Nokia
> ·David Sauvageau, Bell Canada
> ·Chaker Al-Hakim, Huawei
> ·+1  Catherine Lefevre, AT   
> ·Eric Debeau, Orange
> ·Jason Hunt, IBM
> ·Srinivasa Addepalli, Intel
> ·Murat Turpcu,turk telekom
> ·Ning So, Reliance Jio
> ·Lingli Deng, CMCC
> ·Alla Goldner, Amdocs
> ·Bin Yang, Wind River
> ·Milind Jalwadi,, TechMahindra
> ·Stephen Terrill, Ericsson
> ·Susana Sabater, Vodafone
> ·Viswa, Verizon
> ·Yan Chen, China Telecom
> Many thanks & 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
> Cc: Seshu m; TIMONEY, DAN
> Subject: [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 / cloud region being retrievable from static 
> configuration file.
>
> Current behaviour:
> Cloud owner is hardcoded in the code, with no way to change it using config 
> file.
>
> API change requested:
> SDN-C: GENERIC-RESOURCE-API.yang
>
> Impact:
> This API change will allow SO to resolve the cloud owner from the config file 
> (similar to what we had in previous release), and to be able to use it with 
> the GR-API.
>
> Patches:
> SO:
> 1.  Use a property instead of hard coded value. (TBD)
> 2.  Push the changeset to allow it to be set on the north-bound 
> api.  (TBD)
> SDNC: 
> 1 Add cloud-owner definition: 
> .https://gerrit.onap.org/r/#/c/67413/ 
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_67413_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=c31OYuaPawMl_ySS_voXJQ=IRnORADhsIQatMiCFmpWYSg2RJ98PK3OBna5p6LFn8w=MlFEjJ27qgrsAF2_ZjsQRU5IFM7F9Z2E57BCD-A25FM=>
>
> Regards,
> Alexis
> 
> "Confidentiality Warning: This message and any attachments are intended only 
> for the use of the intended recipient(s), are confidential and may be 
> privileged. If you are not the intended recipient, you are hereby notified 
> that any review, re-transmission, conversion to hard copy, copying, 
> circulation or other use of this message and any attachments is strictly 
> prohibited. If you are not the intended recipient, please notify the sender 
> immediately by return email and delete this message and any attachments from 
> your system.
> 
> Virus Warning: Although the company has taken reasonable precautions to 
> ensure no viruses are present in this email. The company cannot accept 
> responsibility for any loss or damage arising from the use of this email or 
> attachment."
> 
> 


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

View/Reply Online (#3894): https://lists.onap.org/g/onap-tsc/message/3894
Mute This Topic: https://lists.onap.org/mt/27269787/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

We re not trying to fulfill this requirement; although we are very aware of it. 
It is planned for Dublin, and won’t get in Casablanca; this is not the 
intention.
We’re not either changing any of the existing behaviour.
I’m not proposing any solution here, simply asking for an API waiver as we need 
to add a field in GR-API yang to get rid of the hard coded cloud owner in the 
new SO BB. The solution has been there before, it’s just lack of time before 
API freeze, and in this matter, introducing a regression.

Background:
SO and SDNC added respectively new Building Blocks and support for GR-API, in 
order to avoir having to perform the manual preload step. With these new flows, 
at assignment stage, all the required ressources would get resolved by SDNC and 
stored in SDNC GR-API, so at creation stage, all SO has to do is query SDNC to 
gets the resources to use, and proceed with creation.
What was uncover late is SO new BBs are using a hard coded cloud owner. The 
change is simply to allow having that cloud owner configurable. It is a 
small/quick fix in order to provide somewhat of a feature parity between former 
SO flow and new SO flows.

I’m asking the TSC for an API waiver as we're pass API freeze and this is an 
API change, in some ways.  If you want to discuss more in detail that 
functionality, I’ll be happy to explain over a meeting.
My intention is to have a quick turnaround on the API change waiver request. I 
hope TSC will be able to see the urgency in that matter, given RC0, so we don’t 
debate too much on a requirement, as as stated before, we’re not trying to 
fulfil any; simply to fix a regression.

Thanks,
Alexis

> On Oct 11, 2018, at 9:04 PM, Yang Bin  wrote:
> 
> Hi Alexis, Dan,
>
>I am not sure if you are aware the ONAP functional requirement 
> about the “Centralized Representation and Consistent Identification of Cloud 
> Regions In ONAP” 
> https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP
>
>The functional requirement consists of 2 important changes:
> 1, remove any hardcoded/redundant representation of a single cloud region, 
> the hard-coded cloud-sites in SO configuration file is exactly what is  
> targeting to be refactored. Now this part is on track of pairwise testing 
> between SO/MultiCloud .
> 2, apply the usage of ID of a cloud region in a consistent way , the 
> agreement is that the composite keys: {cloud-owner}/{cloud-region-id} will be 
> applied whenever ONAP component wants to refer to a cloud region. This part 
> requires the API changes between VID/SO/SDNC and other related projects. It 
> is  a stretch goal in Casablanca, perhaps we can get it done in Dublin 
> Release.
>
>I do believe both of 2 changes above might be related to your 
> proposal. I would like to discuss a little bit about the issue and your 
> proposal so that maybe we can come up with more comprehensive/consistent 
> solution to get things (API changes) done at one time.
>
>If you don’t mind, we can start with several questions:
>1, why should the Cloud-Owner be provisioned to SDNC with 
> REST-API?
> I guess your proposal is to provision the “Cloud Owner” instead of having it 
> being hard-coded . I agree with you that it should not be hard-coded, but why 
> should the Cloud-Owner be provisioned to SDNC with REST-API?
> IMHO, “Cloud-Owner” (and the cloud-region-id ) should be selected either by 
> user via VID portal or by OOF according to policy. In that case, the ID  of 
> the selected cloud region ({cloud-owner}/{cloud-region-id} ) should be passed 
> to SO/SDNC/etc. through rest API.
>
> 2, Will SDNC use the ID  of the selected cloud region to retrieve information 
> from AAI?
>This question is to help me understand what the interactions 
> are between SDNC and AAI
>
> 3, Will SDNC use the ID  of the selected cloud region to retrieve information 
> from underlying VIM/Cloud instance (e.g. OpenStack instance)?
>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    Mobile +86,13811391682Fax +86,10,64398189
> Skype: yangbincs993
>
> From: 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
> Cc: Seshu m; TIMONEY, DAN
> Subject: [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, introdu

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

[Alexis de Talhouet]

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 / cloud region being retrievable from static configuration 
file.

Current behaviour:
Cloud owner is hardcoded in the code, with no way to change it using config 
file.

API change requested:
SDN-C: GENERIC-RESOURCE-API.yang

Impact:
This API change will allow SO to resolve the cloud owner from the config file 
(similar to what we had in previous release), and to be able to use it with the 
GR-API.

Patches:
SO:
1.  Use a property instead of hard coded value. (TBD)
2.  Push the changeset to allow it to be set on the north-bound api.  
(TBD)
SDNC: 
1 Add cloud-owner definition: .https://gerrit.onap.org/r/#/c/67413/ 


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

View/Reply Online (#3878): https://lists.onap.org/g/onap-tsc/message/3878
Mute This Topic: https://lists.onap.org/mt/27260030/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 issue-ids
remote: * SDNC-471
remote: are referenced in the commit message of
remote: db13f4ddbd4a66ab9d66b1820279514137543eff,
remote: but do not exist in its-jira Issue-Tracker

So, Gerrit is impacted as well, in the sense that new patch can’t be submitted.

Alexis

> On Oct 4, 2018, at 5:20 PM, jwagant...@linuxfoundation.org wrote:
> 
> What: The Linux Foundation will be performing a JIRA migration to AWS
> 
> When: Thursday Oct 04 at 6:00pm Pacific
> 
> Why: To improve the performance of JIRA and helping generating reports faster.
> 
> Impact: only JIRA will be unavailable during this time
> 
> Thanks so much!
> Jess
> 


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

View/Reply Online (#3837): https://lists.onap.org/g/onap-tsc/message/3837
Mute This Topic: https://lists.onap.org/mt/26796413/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 
> discuss this week with the ONAP TSC, no later than Tuesday (Oct. 2nd) 11.59pm 
> PST.
> The TSC agenda items will therefore be reviewed and confirmed on Wednesday 
> (Oct 3rd).
>
> Here is the wiki link where you can post your agenda item(s):
> https://wiki.onap.org/display/DW/TSC+2018-10-04+Meeting+Agenda 
> 
>
> Many thanks & regards
> Catherine
>
> Catherine Lefèvre
> AVP Software Development & Engineering
>
> AT Labs – Network Cloud & Infrastructure
> D2 Platform & Systems Development
> ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
> ONAP TSC Chair
>
>
> Phone: +32 2 418 49 22
> Mobile: +32 475 77 36 73
> catherine.lefe...@intl.att.com 
>  <> 
> TEXTING and DRIVING… It Can Wait
> AT
> BUROGEST OFFICE PARK SA
> Avenue des Dessus-de-Lives, 2
> 5101 Loyers (Namur)
> Belgium
>
>
> NOTE: This email (or its attachments) contains information belonging to the 
> sender, which may be confidential. proprietary and/or legally privileged. The 
> information is intended only for the use of the individual(s) or entity(ies) 
> named above. If you are not the intended recipient, you are hereby notified 
> that any disclosure, distribution or taking of any action in reliance on the 
> content of this is strictly forbidden. If you have received this e-mail in 
> error please immediately notify the sender identified above
>
> 


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

View/Reply Online (#3804): https://lists.onap.org/g/onap-tsc/message/3804
Mute This Topic: https://lists.onap.org/mt/26442215/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 as a service. A lot of applications are using SQL or 
Postgres, maybe we could harmonized and have one cluster of each where 
application could own their dB.
- implementation of a proper CI system providing daily feedback using the full 
robot suite (e.g. run distribution and instantiation) on the state of all our 
branches, whether release branches or master. Example of such CI has been 
implemented at various place, but would be good to see that integrated within 
ONAP CI system. This will allow to catch régression way earlier in the 
development cycle.

Regards,
Alexis


> On Sep 26, 2018, at 9:09 AM, Alexis de Talhouët  
> wrote:
> 
> 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 controller 
> providing design capability to define controller blueprint, e.g. the WHAT, 
> and data dictionaries, e.g. the HOW. The blueprint is using a JSON TOSCA 
> based representation.
> it’s leaving under CCSDK, and will be harmonize with APPC CDT. This 
> initiative is well documented here 
> https://wiki.onap.org/plugins/servlet/mobile?contentId=35523521#content/view/35523521
> 
> In order to used the self serve framework, a few new microservices has arised 
> in the Casablanca timeframe. Our deliveries in Casablanca is to augment 
> current vFW assignent orchestration use case to enable name generation at VNF 
> and VF-MODULE level using policy based definition, and to enable 
> auto-assignment of ip addresses within defined pools in an ipam system (we 
> use netbox).
> 
> The enablement of this feature in Casablanca is permitted thanks to new SO 
> building block, and SDNC generic-resource-api DGs.
> 
> There is still a lot of work to do in Dublin and sub-sequent release to 
> properly integrate this within CCSDK and SDC and to be more feature complete. 
> The work items are being listed here: 
> https://wiki.onap.org/pages/viewpage.action?pageId=41422551
> 
> Finally, for those interested, we had a few deep dive sessions in all the 
> components comprising this new feature, the recording can be find here: 
> https://wiki.onap.org/display/DW/ONAP+Controller+Design+Studio+Working+Session
> 
> Another feature that will be valuable for us would be to have TOSCA based 
> orchestration at the SO layer.
> 
> Regards,
> Alexis

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

View/Reply Online (#3777): https://lists.onap.org/g/ONAP-TSC/message/3777
Mute This Topic: https://lists.onap.org/mt/26228330/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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 controller 
providing design capability to define controller blueprint, e.g. the WHAT, and 
data dictionaries, e.g. the HOW. The blueprint is using a JSON TOSCA based 
representation.
it’s leaving under CCSDK, and will be harmonize with APPC CDT. This initiative 
is well documented here 
https://wiki.onap.org/plugins/servlet/mobile?contentId=35523521#content/view/35523521

In order to used the self serve framework, a few new microservices has arised 
in the Casablanca timeframe. Our deliveries in Casablanca is to augment current 
vFW assignent orchestration use case to enable name generation at VNF and 
VF-MODULE level using policy based definition, and to enable auto-assignment of 
ip addresses within defined pools in an ipam system (we use netbox).

The enablement of this feature in Casablanca is permitted thanks to new SO 
building block, and SDNC generic-resource-api DGs.

There is still a lot of work to do in Dublin and sub-sequent release to 
properly integrate this within CCSDK and SDC and to be more feature complete. 
The work items are being listed here: 
https://wiki.onap.org/pages/viewpage.action?pageId=41422551

Finally, for those interested, we had a few deep dive sessions in all the 
components comprising this new feature, the recording can be find here: 
https://wiki.onap.org/display/DW/ONAP+Controller+Design+Studio+Working+Session

Another feature that will be valuable for us would be to have TOSCA based 
orchestration at the SO layer.

Regards,
Alexis

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

View/Reply Online (#3775): https://lists.onap.org/g/ONAP-TSC/message/3775
Mute This Topic: https://lists.onap.org/mt/26228330/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

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"  >
> Reply-To: onap-tsc mailto:ONAP-TSC@lists.onap.org>>
> Date: Sunday, September 23, 2018 at 11:14 PM
> To: onap-tsc mailto:ONAP-TSC@lists.onap.org>>, 
> onap-discuss  >
> Subject: [onap-tsc] Join us at the ONS party and let's brainstorm about 
> Dublin #ons europe 2018
>
> Good evening/morning/afternoon ONAP TSC and Community Members,
>
> As you know there is not yet any formal ONAP Dublin Release Developers Forum 
> being setup.
> Therefore we would like to take the opportunity to meet you at the ONS Europe 
> event this week to collect your initial thoughts about the ONAP Dublin 
> release/use cases.
>
> The ‘Onsite reception’ is planned on Wednesday 26, 17:30–19:00. Location: 
> Auditorium.
> Please let us know if you are interested to meet during the reception (or 
> after the reception) to brainstorm together.
> 
> 
> Many thanks & regards
> Alla/Catherine
>
> Catherine Lefèvre
> AVP Software Development & Engineering
>
> AT Labs – Network Cloud & Infrastructure
> D2 Platform & Systems Development
> ECOMP/ONAP/RUBY/SPP-NEAM-Appl. Servers/SIA
>
>
> Phone: +32 2 418 49 22
> Mobile: +32 475 77 36 73
> catherine.lefe...@intl.att.com 
>  <> 
> TEXTING and DRIVING… It Can Wait
> AT
> BUROGEST OFFICE PARK SA
> Avenue des Dessus-de-Lives, 2
> 5101 Loyers (Namur)
> Belgium
>
>
> NOTE: This email (or its attachments) contains information belonging to the 
> sender, which may be confidential. proprietary and/or legally privileged. The 
> information is intended only for the use of the individual(s) or entity(ies) 
> named above. If you are not the intended recipient, you are hereby notified 
> that any disclosure, distribution or taking of any action in reliance on the 
> content of this is strictly forbidden. If you have received this e-mail in 
> error please immediately notify the sender identified above
>
> 


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

View/Reply Online (#3748): https://lists.onap.org/g/ONAP-TSC/message/3748
Mute This Topic: https://lists.onap.org/mt/26155760/21656
Mute #ons: https://lists.onap.org/mk?hashtag=ons=2743226
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-tsc] TSC Seat Vanacy

[Alexis de Talhouet]

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 charter.

Regards,
Alexis

> On Sep 23, 2018, at 1:24 PM, Alla Goldner  wrote:
> 
> +1
> 
> Sent from Nine
> From: "Frank Brockners via Lists.Onap.Org " 
> mailto:fbrockne=cisco@lists.onap.org>>
> Sent: Sunday, 23 September 2018 19:19
> To: ONAP-TSC@lists.onap.org 
> Subject: Re: [onap-tsc] TSC Seat Vanacy
> 
> Hi Kenny, 
>
> Thanks for the summary. As a community member, I’d prefer if the TSC would 
> quickly amend the current charter to cover the case of TSC members stepping 
> down from their role. Any other approach would be a shot from the hip – and 
> might be in conflict to the ultimate policy that the TSC would come up with. 
> The amendment should cover the considerations that you list below, especially 
> the fact that the TSC now consists of elected members and not representatives 
> of parties, companies, etc. In that, a TSC differs from most of the 
> parliaments, where members often represent parties, so that successors are 
> automatically picked from a list.
>
> Regards,
> Frank
>
> From: ONAP-TSC@lists.onap.org  
> mailto:ONAP-TSC@lists.onap.org>> On Behalf Of Kenny 
> Paul
> Sent: Sonntag, 23. September 2018 18:43
> To: onap-tsc@lists.onap.org 
> Subject: [onap-tsc] TSC Seat Vanacy
>
> I wanted to follow up on the discussion regarding a special election due to 
> Chris taking a new job.  One of the first questions asked was, "What does the 
> Charter say?"  Neither the Charter or Community Document says anything about 
> a vacancy. In the absence of any specific language, the default should be to 
> honor what language there is.  Currently the Community Document says:
> 4.1.1.2   Size and Structure
> The TSC shall consist of eighteen (18) seats 
> Nine (9) seats on the TSC are to be reserved for Operators
> Only one (1) person from any company, or group of related companies (as 
> defined in section 4.4.4.1) may be a member at any given time.
>
> As such, my guidance to the TSC is to immediately authorize a special 
> election using the criteria currently defined in the Community Document, 
> plain and simple.
>
> There were a several alternatives to a special election which have been 
> suggested. While it is well within the TSC's right to pursue any of these 
> alternatives, all must be thoroughly scrutinized through the lens of 
> fairness, trust, and responsibility to the community.
>
> Leaving the seat vacant until the next election cycle
> It took 6 months to debate and vote on membership criteria, and another full 
> month to run an election. Leaving the seat vacant until the next scheduled 
> election implies that after all that work the TSC doesn't care about being 
> fully functional.  This would be a huge hit to the community's trust of the 
> TSC.
>
> Delay any decision on an election until the TSC amends the Community Document 
> to address how to handle a vacancy
> This is marginally better than leaving the seat vacant, because who knows how 
> long amending the Community Document might take. I would encourage the TSC to 
> take up amending the Community Document to cover one or more of the 
> operational and governance gaps that exist, however it is unfair to the ONAP 
> community to hold the recently vacated seat hostage to those discussions.
>
> Have Chris appoint his replacement
> When the TSC was comprised of only appointed individuals doing this would 
> have been fine course of action. In fact, there were a couple instances back 
> in March where this occurred. Now that we have moved from an appointed TSC to 
> an elected TSC, such an appointment by a member is completely inappropriate.
>
> Make the next runner up in the August election the new TSC member
> While true the seat does not belong to Huawei, it would be exceeding unfair 
> to them, especially as the 2nd largest contributor to the Project, to 
> suddenly be out in the cold with absolutely no chance to even compete for a 
> seat they once held.
>
> I don't like creating work for myself and a TCS election is indeed a great 
> deal of work. The thought of having to run a new election is mind-numbing but 
> I welcome it gladly because it is absolutely the right thing to do.
>
> I recommend a one week nomination period, and a one week voting period. (The 
> prior election was lengthened to two + two specifically to accommodate summer 
> vacations).  I am at ONS-Europe this week and out the first week of October 
> on family business. The earliest I can commit to kicking off the process 
> (after revalidating qualified Active Community Members) would be Oct. 11th, 
> putting the close of 

Re: [onap-tsc] 2018 TSC Election Results

[Alexis de Talhouet]

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 " 
> mailto:ONAP-TSC@lists.onap.org>>, 
> "onap-tsc@lists.onap.org " 
> mailto:ONAP-TSC@lists.onap.org>>
> Date:08/31/2018 12:54 AM
> Subject:Re: [onap-tsc] 2018 TSC Election Results
> Sent by:ONAP-TSC@lists.onap.org 
> 
> 
> 
> Congratulationsto the winners and welcome to the new TSC members!!!
> 
> Sent from Nine
> 
> 
> From: Kenny Paul 
> Sent: Thursday, 30 August 2018 23:00
> To: onap-tsc@lists.onap.org
> Subject: [onap-tsc] 2018 TSC Election Results
> 
> Congrats to the winners!
>
> Actual votes cast: 238
> Reserved seats in BOLD 
> New Representatives in Green
>
>  1. Catherine Lefevre (AT) 
>   2. Alla Goldner (Amdocs)
>   3. Stephen Terrill (Ericsson)
>   4. Chris Donley (Huawei)
>   5. Srini Addepalli (Intel)
>   6. Jason Hunt (IBM)
>   7. Eric Debeau (Orange)
>   8. Andreas Geissler (Deutsche Telekom)
>   9. Ranny Haiby (Nokia)
> 10. David Sauvageau (Bell Canada) 
> 11. Viswanath Kumar Skand Priya (Verizon)
> 12. Susana Sabater (Vodafone)
> 13. Lingli Deng (China Mobile)
> 14. Bin Yang (Wind River)
> 15. Murat Turpcu (Turk Telekom) 
> 16. Milind Jalwadi (Tech Mahindra)
> 17. Chen Yan (China Telecom)
> 18. Ning So (Reliance Jio)
>
> Results  https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_709f2aa112974a02 
> 
>
> Best Regards, 
> -kenny
> 
> Kenny Paul, Technical Program Manager, The Linux Foundation
> kp...@linuxfoundation.org , 510.766.5945
> San Francisco Bay Area, Pacific Time Zone
>
>
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement, 
> you may review at https://www.amdocs.com/about/email-disclaimer 
> 
> 
> 
> 
> 


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

View/Reply Online (#3678): https://lists.onap.org/g/ONAP-TSC/message/3678
Mute This Topic: https://lists.onap.org/mt/25133733/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/leave/2743226/1412191262/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

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

[Alexis de Talhouet]

+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 both its architecture and as a top committer on the project. Over 
> the last year, I standardized the Helm chart template for the ONAP community 
> and delivered many of the Helm charts on behalf of the project teams. I also 
> held a number of workshops, education and debugging sessions with the project 
> teams and worked very closely with the integration team to help ensure the 
> successful delivery of ONAP on OOM in the Beijing release.
>
> We have a fantastic team and a great community, with a lot of smart, 
> experienced and dedicated people. I’m really looking forward to working with 
> this team to deliver on Casablanca and beyond!  And I would very much like to 
> do that as your PTL.
>
> Thanks very much for your consideration,
> Mike Elliott
>
>
> From: mailto:ONAP-TSC@lists.onap.org>> on behalf of 
> David Sauvageau mailto:david.sauvag...@bell.ca>>
> Date: Tuesday, July 10, 2018 at 1:45 PM
> To: "onap-disc...@lists.onap.org " 
> mailto:onap-disc...@lists.onap.org>>, 
> "ONAP-TSC@lists.onap.org " 
> mailto:ONAP-TSC@lists.onap.org>>
> Subject: [onap-discuss][onap-tsc][OOM] PTL Election for OOM
>
> Dear ONAP OOM Committers,
>   
> As mandated by ONAP process, PTL elections must be held at least once a year. 
>   You can read more details here: 
> https://wiki.onap.org/display/DW/Annual+Community+Elections 
> 
>
> If you are interested in the Integration PTL position.  Please reply to all 
> to do self-nomination. 
>
> We will close the self-nomination window by 23:59 PDT July 18th, Wednesday, 
> 2018.  Further instructions will be sent out to the committers on the 
> election procedure.  The final result will be announced on the ONAP lists 
> before the end of this week.
>
> Regards,
> David Sauvageau
>
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer 
> 
> 


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

View/Reply Online (#3429): https://lists.onap.org/g/ONAP-TSC/message/3429
Mute This Topic: https://lists.onap.org/mt/23219123/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-