from:"Eric Debeau"

Re: [onap-tsc] Weekly ONAP Release Status - May 25, 2022 #weeklyupdate

2022-05-31 Thread Eric Debeau via lists.onap.org

Thanks


We will use some material for the release note


Best Regards


Eric


De : onap-tsc@lists.onap.org  de la part de Haiby, 
Ranny 
Envoyé : mercredi 1 juin 2022 01:43:23
À : Kenny Paul
Cc : Lefevre, Catherine; David McBride; onap-release; onap-tsc; Jagiełło, Michał
Objet : Re: [onap-tsc] Weekly ONAP Release Status - May 25, 2022 #weeklyupdate

Hi Catherine,

Brandon and I were working on this:
https://docs.google.com/document/d/1QuLEh6O5xGiGolbozRXWFZTyjNlVCib0zb1tNz4Lmqw/edit?usp=sharing
Not exactly the release notes, but messaging for the release.

Regards,

Ranny.


On Tue, May 31, 2022 at 3:50 PM 
mailto:kp...@linuxfoundation.org>> wrote:
Hi Catherine,

We established previously that LF Marketing will no longer be delivering a 
general release note and that the community will be responsible for writing a 
general release note if appropriate.

Thanks!
-kenny

From: Lefevre, Catherine 
mailto:catherine.lefe...@intl.att.com>>
Sent: Monday, May 30, 2022 6:06 PM
To: David McBride 
mailto:dmcbr...@linuxfoundation.org>>; 
onap-release mailto:onap-rele...@lists.onap.org>>; 
onap-tsc mailto:onap-tsc@lists.onap.org>>; Jagiełło, 
Michał mailto:michal.jagie...@t-mobile.pl>>; Ranny 
Haiby mailto:rha...@linuxfoundation.org>>
Cc: Kenny Paul mailto:kp...@linuxfoundation.org>>
Subject: RE: Weekly ONAP Release Status - May 25, 2022 #weeklyupdate

Good morning David, Ranny,

Did the Marketing team finalize the draft document based on what has been 
provided by the ONAP Community?
We will need it for our release note.

Many thanks & regards,
Catherine

From: David McBride 
mailto:dmcbr...@linuxfoundation.org>>
Sent: Wednesday, May 25, 2022 5:10 PM
To: onap-release 
mailto:onap-rele...@lists.onap.org>>; onap-tsc 
mailto:onap-tsc@lists.onap.org>>; Jagiełło, Michał 
mailto:michal.jagie...@t-mobile.pl>>
Cc: Lefevre, Catherine 
mailto:catherine.lefe...@intl.att.com>>; Kenny 
Paul mailto:kp...@linuxfoundation.org>>
Subject: Weekly ONAP Release Status - May 25, 2022 #weeklyupdate

Jakarta release
• 
Schedule
• Milestone 
Status
o RC
• The TSC approved the RC milestone on May 12
o Sign Off - scheduled for June 2
• Release management tasks have been published
• 
Projects
• Requirement 
owners

*   New license scan results

   *   
https://lists.onap.org/g/onap-ptl/message/335
   *   
https://lists.onap.org/g/onap-ptl/message/332
   *   A new RM task has been added for Sign Off to review license scan 
results and make any necessary changes
• Open issue status and 
trend
• Xtesting Results 
(master)
o @Jagiełło, Michał said on Monday that we 
should have Xtesting daily test results for the Jakarta branch this week
• Integration
o Integration Test 
Status
o Blocking 
Points
Kohn Release
• 
Schedule
o See the following messages regarding recent changes to the schedule:
• 
https://lists.onap.org/g/onap-ptl/message/329

Re: [onap-tsc] [Network Slicing] - EXT-API repo re-activation

2022-04-21 Thread Eric Debeau via lists.onap.org

Hello


I think that it is not as simple as the project is no more maintained...


I am not sure that we will create a Jakarta branch...


Upate OOM is simple, but we need the new image


To be discussed.


Best Regards


Eric


De : onap-tsc@lists.onap.org  de la part de Catherine 
LEFEVRE 
Envoyé : jeudi 21 avril 2022 14:21:35
À : Ahila Pandaram - (iDEAS-ER&D); onap-tsc@lists.onap.org
Cc : David McBride; MAYER, ANDREW J; DEBEAU Eric INNOV/NET; MAYER, ANDREW J; 
D'Alessandro Alessandro Gerardo; N.K. Shankaranarayanan; Saravanan A 
(iDEAS-ER&D); Deepika S (iDEAS-ER&D); Malinconico Aniello Paolo (Guest); MAYER, 
ANDREW J
Objet : Re: [onap-tsc] [Network Slicing] - EXT-API repo re-activation


Thank you Ahila.

I have added this request to today’s ONAP TSC Agenda (4/21)

We are nearly there 😊



Best regards,

Catherine



From: Ahila Pandaram - (iDEAS-ER&D) 
Sent: Thursday, April 21, 2022 2:12 PM
To: Lefevre, Catherine ; onap-tsc@lists.onap.org
Cc: David McBride ; MAYER, ANDREW J 
; DEBEAU Eric TGI/OLN ; MAYER, ANDREW J 
; D'Alessandro Alessandro Gerardo 
; N.K. Shankaranarayanan 
; Saravanan A (iDEAS-ER&D) ; 
Deepika S (iDEAS-ER&D) ; Malinconico Aniello Paolo 
(Guest) ; MAYER, ANDREW J 

Subject: RE: [onap-tsc] [Network Slicing] - EXT-API repo re-activation



Thank you Catherine for checking with us.



Below are the pending items to be done. We need support from Andy Mayer/Eric 
Debeau.



  1.  The bug fix is currently available in the master branch and it needs to 
be aligned with the ONAP release. It requires the release version of the image 
to get pushed to nexus
  2.  release image version update in the OOM charts



Thanks & Regards,

Ahila P.



From: Lefevre, Catherine 
mailto:catherine.lefe...@intl.att.com>>
Sent: 21 April 2022 17:29
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; Ahila Pandaram - 
(iDEAS-ER&D) mailto:ahila.panda...@wipro.com>>; 
MAYER, ANDREW J mailto:am8...@att.com>>
Cc: David McBride 
mailto:dmcbr...@linuxfoundation.org>>; MAYER, 
ANDREW J mailto:am8...@att.com>>; DEBEAU Eric TGI/OLN 
mailto:eric.deb...@orange.com>>; D'Alessandro 
Alessandro Gerardo 
mailto:alessandro.dalessan...@telecomitalia.it>>;
 N.K. Shankaranarayanan mailto:nk.shan...@stl.tech>>; 
Saravanan A (iDEAS-ER&D) 
mailto:saravanan@wipro.com>>; Deepika S 
(iDEAS-ER&D) mailto:deepika@wipro.com>>; Malinconico 
Aniello Paolo (Guest) 
mailto:aniellopaolo.malincon...@guest.telecomitalia.it>>
Subject: RE: [onap-tsc] [Network Slicing] - EXT-API repo re-activation



CAUTION:This email is received from an external domain. Open the hyperlink(s) & 
attachment(s) with caution.
.


Good morning /afternoon Kevin and Ahila,



My apologies for the delayed response.



The code was reviewed and merged by Andy on April 18th.

Have you all what you need to proceed?



Best regards

Catherine



From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Kevin 
Tang via lists.onap.org
Sent: Monday, April 18, 2022 7:08 PM
To: Ahila Pandaram - (iDEAS-ER&D) 
mailto:ahila.panda...@wipro.com>>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; David McBride 
mailto:dmcbr...@linuxfoundation.org>>; MAYER, 
ANDREW J mailto:am8...@att.com>>; DEBEAU Eric TGI/OLN 
mailto:eric.deb...@orange.com>>; D'Alessandro 
Alessandro Gerardo 
mailto:alessandro.dalessan...@telecomitalia.it>>;
 N.K. Shankaranarayanan mailto:nk.shan...@stl.tech>>; 
Saravanan A (iDEAS-ER&D) 
mailto:saravanan@wipro.com>>; Deepika S 
(iDEAS-ER&D) mailto:deepika@wipro.com>>; Malinconico 
Aniello Paolo (Guest) 
mailto:aniellopaolo.malincon...@guest.telecomitalia.it>>
Subject: Re: [onap-tsc] [Network Slicing] - EXT-API repo re-activation



Hi All,



Just a friendly reminder, code-review is needed for this fix 
https://gerrit.onap.org/r/c/externalapi/nbi/+/128384<https://urldefense.com/v3/__https:/apc01.safelinks.protection.outlook.com/?url=https*3A*2F*2Furldefense.com*2Fv3*2F__https*3A*2Fprotect2.fireeye.com*2Fv1*2Furl*3Fk*3D31323334-501d2dca-31317ecd-454455534531-38d6987983223d4c*26q*3D1*26e*3Dbc9814e2-b8cf-41a7-97d3-56eda9a2a4fb*26u*3Dhttps*3A*2F*2Fgerrit.onap.org*2Fr*2Fc*2Fexternalapi*2Fnbi*2F*2B*2F128384__*3BJSUlJSUlJSUlJQ!!BhdT!nIZTznujgJqJuDhcZ7Y-c0xy1M_sVJOs1J1W-BdxXnnBOCfI9evdXUP1dLmxMKPwwgHteOqXrJb939vqHbjL2QGgt8kzNIsCDrERmA*24&data=05*7C01*7Cahila.pandaram*40wipro.com*7Ceed7ccc500104a93a3bc08da238e6b34*7C258ac4e4146a411e9dc879a9e12fd6da*7C1*7C0*7C637861391880600586*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C3000*7C*7C*7C&sdata=ZaYZp47siUTWLmBZvJ*2FdOxmwLhTv7T9sb9*2BseSb*2BTVY*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUqKioqKioqKioqJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!BhdT

Re: [onap-tsc] [OOM] Ready to move to gitlab

2021-12-16 Thread Eric Debeau via lists.onap.org

Hello


Congrats Sylvain and OOM team.


I think that it is a good solution to start next year.


Best Regards


Eric


De : onap-rele...@lists.onap.org  de la part de 
Sylvain Desbureaux via lists.onap.org 

Envoyé : jeudi 16 décembre 2021 17:36:01
À : onap-tsc@lists.onap.org
Cc : onap-rele...@lists.onap.org; Bengt Thuree; David McBride; Kenny Paul; 
jwagant...@linuxfoundation.org; k.opas...@samsung.com
Objet : [Onap-release] [OOM] Ready to move to gitlab

Hello,

Today we have merged the different files allowing us to move to gitlab.
We still have a few things not working:

  *   Pushing tests charts into onap-helm-testing repository
  *   Pushing released charts into onap-helm-release (well, it also doesn’t 
work on Jenkins today, a ticket is opened: 
https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23362)

But I guess we can start without them.

I then propose to make the change (gitlab the “official”, gerrit the “mirror”) 
first week of next year if no one is opposed.

Regards,

Sylvain

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.




_

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

[onap-tsc] Orange proxy for next TSC meeting

2021-10-22 Thread Eric Debeau via lists.onap.org

Hello


Sylvain will be Orange proxy for next TSC (November, 4th).


Best Regards


Eric

_

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

Re: [onap-tsc] [Onap-release] Weekly ONAP Release Status - Sept 29, 2021 #weeklyupdate

2021-09-29 Thread Eric Debeau via lists.onap.org

Hello

"A documentation build issue has been blocking the maintenance release.

  *   A solution has been submitted.
  *   Unclear at this time whether the solution was successful."

=> the documentation build issue impacted all the projects and not only the 
maintenance release
=> the pb is corrected in lfdocs-conf and the global maintenance release note 
has been published thanks to Andreas. Still waiting for some projects to 
publish their Honolulu Maintenance Release


Best Regards

Eric


De : onap-rele...@lists.onap.org [onap-rele...@lists.onap.org] de la part de 
David McBride [dmcbr...@linuxfoundation.org]
Envoyé : mercredi 29 septembre 2021 21:57
À : onap-release; onap-tsc
Cc : Kenny Paul
Objet : [Onap-release] Weekly ONAP Release Status - Sept 29, 2021 #weeklyupdate

Istanbul release

  *   Schedule
 *   M4
*   On Sept 16, the TSC approved M4 on 
the condition that
   *   the remaining milestone tasks be resolved by Sept 30
   *   the status of BP/GR requirements is understood by Sept 23
*   The conditions have now been satisfied
 *   RC
*   Scheduled for Oct 14
  *   Jira
 *   153 open 
issues
 (-134 change from previous update)
 *   Note: this 
dashboard shows 
> 2000 issues that are unassigned to a release.  This means that we do not have 
an accurate accounting of the actual workload for the current release.
  *   SECCOM High Priority Jira
 *   Resolved
  *   Integration blocking issues

Honolulu maintenance release

  *   Jira
 *   2 open 
issues
 (0 change from previous update)
  *   INT team indicated that daily test results are acceptable
  *   A documentation build issue has been blocking the maintenance release.
 *   A solution has been submitted.
 *   Unclear at this time whether the solution was successful.

Jakarta release

  *   A schedule proposal  will be voted on by 
the TSC on Sept 30.

--
David McBride (pronounce)
Senior Technical Community Architect
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email: dmcbr...@linuxfoundation.org


_

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

Re: [onap-tsc] ONAP TSC SELF-NOMINATIONS OPEN - Ends Sept 21, 2021

2021-09-21 Thread Eric Debeau via lists.onap.org

Dear ONAP community,


I would like to nominate myself as a TSC member of the ONAP project 
representing Orange.


I have been involved in SDN/NFV activities for more than 7 years, leading a 
team focusing in open source communities (ONAP, OPNFV, Acumos). I jumped into 
ONAP from day1 and always promoted ONAP in various events (SDN World Congress 
2017, OSN Days Paris 2018, ONS 2018&2019, ONES2020, ONS Europe 2018&2019),  
interviews (Telecoms TV) and LinkedIn.


Currently TSC member representing Orange, I am also the Orange coordinator for 
all ONAP activities. Orange had PTL responsibility on various projects 
(External API and Integration project), and is now leading the OOM project. 
Orange is also contributing to many projects and various tasks forces (CNCF) or 
sub-committees (security). Orange has introduced the gating process by managing 
various platforms and providing resources to perform daily tests.


I contributed to various ONAP projects (documentation, integration, 
externalAPI…) and I am strongly involved to improve documentation, end to end 
automation, platform footprint and also CI/CD. I also conducted many PoC with 
many vendors and service providers establishing strong relationship with the 
eco-system. I am convinced that collaboration within open source project is the 
best approach to drive the industry to deliver de facto standard solutions. 
ONAP has established an amazing community and I very proud to be part of it.


ONAP is a major project for service providers in their network automation 
journey and I will focus my energy to make ONAP a success. Acting as a TSC 
member, I would focus on key topics (usability, CI/CD, security) to ease ONAP 
usage in production.


Best Regards


Eric


De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Kenny Paul 
[kp...@linuxfoundation.org]
Envoyé : mardi 7 septembre 2021 17:11
À : 'onap-tsc'
Objet : [onap-tsc] ONAP TSC SELF-NOMINATIONS OPEN - Ends Sept 21, 2021

Dear ONAP Community,
If you are interested in running for a seat on the TSC, please read all of this 
information carefully
Nominations for seats on the ONAP TSC are officially open. Up to 25 seats on 
the TSC are now available.
Who is eligible to Run:

  *   Any Active Community Members as measured 
at 14:00 UTC, Tuesday, September 7, 2021.   The ONAP Technical Community 
Documents defines an Active Community Member as 
anyone from the ONAP community with twenty (20) or more measurable 
contributions during the previous 12-month period, inclusive of code merged, 
code reviews performed, wiki page edits, (creation, modification, comments or 
attachments) or JIRA activities (creation, modification, comment or closure).

  *   There are no restrictions to the number of people from a company or group 
of companies that may run for an available seat.
Self-Nomination Phase

  *   Interested individuals MUST REPLY-ALL TO THIS ORIGINAL EMAIL with your 
intention to run no later than 23:59 UTC, September 21, 2021

  *   It is recommended that candidates include a small head-shot, a short 
biography and statement of intent on why you would be a good person to hold a 
seat on the TSC.

  *   Please also fill in the 2021 TSC Election Candidates wiki 
page with that same information.
Election Phase

  *   Any Active Community Members as of 14:00 UTC, Tuesday, September 7, 2021 
is eligible to vote.

  *   A Condorcet election will be held using the OpaVote 
system (due to recent changes to CIVS). The election 
shall consist of a single stack ranked vote of all candidates.

  *   Active Community Members will receive an invitation to vote from OpaVote.

  *   The election phase will begin with the distribution of the poll via email 
from the application

  *   The election phase will end two (2) weeks later in the same time zone the 
poll was initiated from

  *   Only the top ranked candidates from any single company or group of 
related companies will be elected; if the top 5 vote getters are all from the 
same company, only the person with the highest number of votes out of all 5 
will be elected from that company.

  *   The LF will update the Voting Results 
History  page with their name, date, and link to 
the publicly viewable results and send an email to the onap-tsc distribution 
list.

Thanks!
-kenny



_

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

Re: [onap-tsc] Follow up to TSC 2.0 Number of seats discussion

2021-04-15 Thread Eric Debeau via lists.onap.org

Thanks Kenny !

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Kenny Paul 
[kp...@linuxfoundation.org]
Envoyé : jeudi 15 avril 2021 21:22
À : onap-tsc@lists.onap.org
Objet : [onap-tsc] Follow up to TSC 2.0 Number of seats discussion

As currently defined and “Active Community Member” is:  Anyone from the ONAP 
community with twenty (20) or more measurable contributions during the previous 
12-month period, inclusive of code merged, code reviews performed, wiki page 
edits, or JIRA activities

Given this criteria in good faith I’m using the following columns from the 
community leaderboard in LFX Insights when “All” is selected.  These are the 
same values as I’ve always used throughout the history of ONAP:

  *   Code commits & LOC numbers – NOT USED – Not part of the criteria
  *   Gerrit: Approvals – The act of issuing a +1, -1, +2 or -2 for someone’s 
code submission – implies a code review
  *   Gerrit: Active Changesets – NOT USED - Not part of the criteria
  *   Gerrit: Merged Changesets – Merged Code
  *   Gerrit: Review Comments – the act of adding a comment to a review – 
implies a code review
  *   Jira: Comments – the act of adding a comment to a Jira ticket
  *   Jira: Issues Assigned – Jiras assigned to an individual
  *   Jira: Issues Created – Jiras created by an individual
  *   Jira: Issues Closed - NOT USED – Yes, technically someone can close an 
issue that was not assigned to them. Doing so should always include adding a 
comment which the person would then get credit for.
  *   Jira: Issues Avg Days in Open – NOT USED - Not part of the criteria
  *   Confluence: Comments – the act of adding comments to a page – implies an 
edit
  *   Confluence: Posts – blog posts - No one ever uses this functionality in 
ONAP, but it would still be valid if they did
  *   Confluence: Pages Created – exactly what it says – implies an edit
  *   Confluence: Pages Edited – exactly what it says
  *   Confluence: Attachments – the act of uploading an attachment to a page– 
implies an edit
  *   Confluence: Last Update & Days Since Last – NOT USED - Not part of the 
criteria

For the past year there are 420 unique “Active Community Members” based upon 
the above.
Dupe company names were then removed after doing some quick reconciliation 
(such as  Ericsson & EST as one example) and tossing anyone not affiliated into 
a single bucket.
This produced 48 unique company names. I then broke things down further into 
companies by # of Active Community Members for the following:
# from a company

>= 3 people

>= 5 people

>= 6 people

>= 10 people

# of companies

22

20

17

14


Hope this helps in the decision making process for what a reasonable number of 
seats for the TSC.


Thanks!
-kenny



_

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

Re: [onap-tsc] RC0 formal validation

2021-04-02 Thread Eric Debeau via lists.onap.org

Thanks Kenny

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Kenny Paul 
[kp...@linuxfoundation.org]
Envoyé : vendredi 2 avril 2021 18:10
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] RC0 formal validation

I just put it out there. https://lists.onap.org/g/onap-tsc-vote/message/1941


From: onap-tsc@lists.onap.org  On Behalf Of Eric 
Debeau via lists.onap.org
Sent: Friday, April 2, 2021 6:28 AM
To: onap-tsc 
Subject: [onap-tsc] RC0 formal validation

Hello

I have not yet seen a formal agreement for RC0 milestone while it seems that it 
should be ok.

@Kenny, @David Can we formalize it via a vote?

Best Regards

Eric

_



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.


_

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

[onap-tsc] RC0 formal validation

2021-04-02 Thread Eric Debeau via lists.onap.org

Hello

I have not yet seen a formal agreement for RC0 milestone while it seems that it 
should be ok.

@Kenny, @David Can we formalize it via a vote?

Best Regards

Eric

_

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

Re: [onap-tsc] [ONAP] integration committer promotion Illia Halych

2021-04-02 Thread Eric Debeau via lists.onap.org

+1

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Morgan 
Richomme via lists.onap.org [morgan.richomme=orange@lists.onap.org]
Envoyé : vendredi 2 avril 2021 11:29
À : onap-tsc
Objet : [onap-tsc] [ONAP] integration committer promotion Illia Halych

Dear TSC,

I would like to request review/approval for Illia Halych committer promotion 
for Integration project.
All committers voted in favor (11 yes/0 no on 13 committers)

see 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+Integration+Illia+Halych
 for details

Eli worked on the pythonsdk, the simu wrapper for the pythonsdk, he attends the 
weekly meeting and will help us on the resiliency/backup & restore for Istambul.

I will update the several info.yaml  upon approval.

/Morgan
Integration PTL


_

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.




_

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

[onap-tsc] Proxy Orange for TSC

2021-02-11 Thread Eric Debeau via lists.onap.org

Hello

Morgan will be the Orange proxy for the TSC today.

Best Regards

Eric

_

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 (#7514): https://lists.onap.org/g/onap-tsc/message/7514
Mute This Topic: https://lists.onap.org/mt/80556092/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] vote to remove POMBA in OOM Helm charts

2020-12-07 Thread Eric Debeau via lists.onap.org

Thank you Catherine

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Catherine 
LEFEVRE [catherine.lefe...@intl.att.com]
Envoyé : lundi 7 décembre 2020 15:43
À : onap-tsc@lists.onap.org; Kenny Paul
Objet : Re: [onap-tsc] vote to remove POMBA in OOM Helm charts

Good morning Eric,

The vote has been kicked off with the TSC.

Best regards
Catherine

From: onap-tsc@lists.onap.org  On Behalf Of Eric 
Debeau via lists.onap.org
Sent: Saturday, December 5, 2020 9:06 AM
To: Kenny Paul ; onap-tsc@lists.onap.org
Subject: [onap-tsc] vote to remove POMBA in OOM Helm charts

Hi Kenny

As  decided in the last TSC, can you launch the vote to remove POMBA from OOM 
Helm charts ?

Best Regards

Eric

_



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.


_

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 (#7351): https://lists.onap.org/g/onap-tsc/message/7351
Mute This Topic: https://lists.onap.org/mt/78730054/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] vote to remove POMBA in OOM Helm charts

2020-12-05 Thread Eric Debeau via lists.onap.org

Hi Kenny

As  decided in the last TSC, can you launch the vote to remove POMBA from OOM 
Helm charts ?

Best Regards

Eric

_

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 (#7348): https://lists.onap.org/g/onap-tsc/message/7348
Mute This Topic: https://lists.onap.org/mt/78730054/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-release] [onap-tsc] ONAP Dockerhub Update

2020-11-26 Thread Eric Debeau via lists.onap.org

Perfect !

Many thanks Kenny

Best Regards

Eric



De : onap-rele...@lists.onap.org [onap-rele...@lists.onap.org] de la part de 
Kenny Paul [kp...@linuxfoundation.org]
Envoyé : jeudi 26 novembre 2020 16:25
À : DESBUREAUX Sylvain TGI/OLN; onap-tsc@lists.onap.org; 
onap-rele...@lists.onap.org
Objet : Re: [Onap-release] [onap-tsc] ONAP Dockerhub Update

OK Morgan, onapintegration should be good to go on Dockerhub.
-kenny

From: sylvain.desbure...@orange.com 
Sent: Thursday, November 26, 2020 6:49 AM
To: kp...@linuxfoundation.org; onap-tsc@lists.onap.org; 
onap-rele...@lists.onap.org
Subject: RE:[onap-tsc] ONAP Dockerhub Update

I've created it this morning europe time so I believe it wasn't :)

thanks again and good thanksgiving!

De : kp...@linuxfoundation.org 
[kp...@linuxfoundation.org]
Envoyé : jeudi 26 novembre 2020 15:34
À : onap-tsc@lists.onap.org; 
onap-rele...@lists.onap.org
Cc : DESBUREAUX Sylvain TGI/OLN
Objet : RE: [onap-tsc] ONAP Dockerhub Update
I think that "onapintegration" was one of the accounts already included, but 
I’ll check.

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Morgan 
Richomme via lists.onap.org
Sent: Thursday, November 26, 2020 12:54 AM
To: onap-tsc@lists.onap.org; 
onap-rele...@lists.onap.org
Cc: DESBUREAUX Sylvain TGI/OLN 
mailto:sylvain.desbure...@orange.com>>
Subject: Re: [onap-tsc] ONAP Dockerhub Update

Thanks Kenny

As discussed in rocket chat yesterday, could you declare the dockerhub user 
"onapintegration" as the 5th seat.
This user will be used for ONAP integration daily/weekly CI chains

Thanks

Morgan


De : onap-tsc@lists.onap.org 
[onap-tsc@lists.onap.org] de la part de Kenny Paul [kp...@linuxfoundation.org]
Envoyé : mercredi 25 novembre 2020 00:40
À : onap-tsc@lists.onap.org; 
onap-rele...@lists.onap.org
Objet : [onap-tsc] ONAP Dockerhub Update
Dear TSC,

Jess just finished working with LF Finance to upgrade the ONAP Dockerhub 
account.  Originally we applied for a free OSS account, but I decided that we 
were better off just getting a paid account to get back on track ASAP.  Once I 
found out that the cost was only $300 USD annually I gave the authorization to 
proceed, so this is one of those, “Ask for forgiveness rather than permission” 
scenarios on my part.

This plan has 5 seats associated with it, 4 of which are currently in use for 
automation/management purposes.  There is one seat available and that is being 
held in reserve for now. Should it also be needed to serve the community at 
large, let’s make sure that we understand why and establish if there are any 
others that are also necessary. If so we can add then to our account 
incrementally.

This should get us past our current bottleneck.

Thanks!
-kenny


_



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.

_



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 del

Re: [onap-tsc] ONAP Dockerhub Update

2020-11-26 Thread Eric Debeau via lists.onap.org

Thanks Kenny for your efforts

I also approve the Morgan's proposal. It is very important for the CI chains.

Best Regards

Eri

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Morgan 
Richomme via lists.onap.org [morgan.richomme=orange@lists.onap.org]
Envoyé : jeudi 26 novembre 2020 09:53
À : onap-tsc@lists.onap.org; onap-rele...@lists.onap.org
Cc : DESBUREAUX Sylvain TGI/OLN
Objet : Re: [onap-tsc] ONAP Dockerhub Update

Thanks Kenny

As discussed in rocket chat yesterday, could you declare the dockerhub user 
"onapintegration" as the 5th seat.
This user will be used for ONAP integration daily/weekly CI chains

Thanks

Morgan


De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Kenny Paul 
[kp...@linuxfoundation.org]
Envoyé : mercredi 25 novembre 2020 00:40
À : onap-tsc@lists.onap.org; onap-rele...@lists.onap.org
Objet : [onap-tsc] ONAP Dockerhub Update

Dear TSC,

Jess just finished working with LF Finance to upgrade the ONAP Dockerhub 
account.  Originally we applied for a free OSS account, but I decided that we 
were better off just getting a paid account to get back on track ASAP.  Once I 
found out that the cost was only $300 USD annually I gave the authorization to 
proceed, so this is one of those, “Ask for forgiveness rather than permission” 
scenarios on my part.

This plan has 5 seats associated with it, 4 of which are currently in use for 
automation/management purposes.  There is one seat available and that is being 
held in reserve for now. Should it also be needed to serve the community at 
large, let’s make sure that we understand why and establish if there are any 
others that are also necessary. If so we can add then to our account 
incrementally.

This should get us past our current bottleneck.

Thanks!
-kenny


_

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.




_

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 (#7310): https://lists.onap.org/g/onap-tsc/message/7310
Mute This Topic: https://lists.onap.org/mt/78489750/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] Promotion of Ramesh as SO committer

2020-11-20 Thread Eric Debeau via lists.onap.org

Hello

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de seshu
kumar m via lists.onap.org [seshu.kumar.m=huawei@lists.onap.org]
Envoyé : vendredi 20 novembre 2020 17:27
À : Seshu m; onap-tsc
Objet : Re: [onap-tsc] Promotion of Ramesh as SO committer

Dear TSC,

I would like to provide the promotion of Ramesh Parthasarathy as SO project
committer.

Detailed report on the candidature can be found in the wiki link :

https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+11.04.2020

We received 5/6 votes as +1 from the existing commiters of SO collected through
email.

will be updating the info.yaml file once TSC approves the promotion.

--
Thanks and Regards,
M Seshu Kumar
Lead Architect,
P&S, Cloud Network OSDT,
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
___
This e-mail and its attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed above.
Any use of the information contained herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by
persons other than the intended recipient(s) is prohibited. If you receive this
e-mail in error, please notify the sender by phone or email immediately and
delete it!
---

From:Seshu m
To:SMOKOWSKI, STEVEN ;BENJAMIN, MAX
;byung-woo.jun ;Muszkieta, Lukasz
(Nokia - PL/Wroclaw) ;Chenchuanyu
;Seshu m
Date:2020-11-18 18:14:16
Subject:Promotion of Ramesh as SO committer

Dear SO Committers

This is in regards to the promotion of Ramesh Parthasarathy as committer in SO.

You can find the details of his contributions to SO and its integration with
oom.

https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+11.04.2020

Ramesh has been consistent with his contributions to SO and has made
significant contributions for the project to meet the milestones.

Request to kindly provide your feedback with one of the below options before
20th November 2020 EOB:

+1 if you agree

0 if you have no opinion

-1 if you don't agree

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

Re: [onap-tsc] [ONAP] [Integration] committer promotion for Lasse Kaihlavirta

2020-11-17 Thread Eric Debeau via lists.onap.org

Hello

Ok for me

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Catherine 
LEFEVRE [catherine.lefe...@intl.att.com]
Envoyé : mardi 17 novembre 2020 15:37
À : onap-tsc@lists.onap.org
Cc : Lasse Kaihlavirta
Objet : Re: [onap-tsc] [ONAP] [Integration] committer promotion for Lasse 
Kaihlavirta

Dear ONAP TSC (or proxies),

I am an Integration committer therefore may I ask one of you to review this 
request?

Many thanks & regards
Catherine

From: onap-tsc@lists.onap.org  On Behalf Of Morgan 
Richomme via lists.onap.org
Sent: Friday, November 13, 2020 11:23 AM
To: onap-tsc@lists.onap.org
Cc: Lasse Kaihlavirta 
Subject: [onap-tsc] [ONAP] [Integration] committer promotion for Lasse 
Kaihlavirta

Dear TSC,
I’d like to promote the Lasse Kaihlavirta as Integration project committer:
Lasse is involved in Integration for a long time.
He is now working on the CSIT improvement and recently detailed his roadmap 
during the last PTL meeting.

See 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+Integration+Lasse+Kaihlavirta
 to get all the details on his activities.
As indicated in this wiki page, he got only +1 vote from the voting committers 
(8/8)

Once formerly approved by TSC, I will update the different INFO.yaml

Regards

/Morgan
ONAP Integration - PTL

_



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.


_

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 (#7272): https://lists.onap.org/g/onap-tsc/message/7272
Mute This Topic: https://lists.onap.org/mt/78226743/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] Call for Functest and CNTT RC2 contributions

2020-09-18 Thread Eric Debeau via lists.onap.org

Bravo

J'ai retwitté...

Un beau FM !

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de
cedric.ollivier via lists.onap.org [cedric.ollivier=orange@lists.onap.org]
Envoyé : vendredi 18 septembre 2020 09:23
À : opnfv-tech-discuss (opnfv-tech-disc...@lists.opnfv.org);
onap-tsc@lists.onap.org; onap-disc...@lists.onap.org; TSC OPNFV
(opnfv-...@lists.opnfv.org)
Objet : [onap-tsc] Call for Functest and CNTT RC2 contributions

Hi,

I share a couple of Functest and CNTT RC2 proposals which should help any new
comers to contribute to the CNTT implementation part, key to our success.
https://www.linkedin.com/pulse/call-functest-cntt-rc2-contributions-c%C3%A9dric-ollivier/

Kubernetes Conformance aims to provide an high level of common functionality as
opposed to CNTT which defines its reference architecture.
The related test case picks about 300 out of 5000 single tests offered by e2e
tests [1].
The next requirement traceability could help reaching the OpenStack ratio where
more than 80 % of the tests are selected for the CNTT conformance.
Please see Select all e2e tests applicable to RA2 for details [2].

CNTT RC2 runs the automated Center of Internet Security (CIS) benchmarks for
information and fails if the highest vulnerabilities are detected.
I hope we will set as mandatory a couple of CIS benchmark checks once our
security requirements are clearer.
Please see Implement from RA2 to RC2 security traceability for details [3].
It's worth mentioning that they are many security tools like docker-bench which
could complete kube-hunter and kube-bench in RC2.

I'm hoping to see cnf-conformance [4] which enables interoperability of Cloud
native Network Functions (CNFs) in RC2.
A first test case running the default CNF was integrated in Functest Kubernetes
a couple of weeks ago and it's already in good shape.

Be free to suggest and to contribute any other ideas. Any feedback about CNTT
RC2 is also welcome!
It should be noted that the test case list, now mandatory in CNTT RC2, is
already in an ongoing Orange RFP.

Cédric

[1]
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests.md

[2] https://github.com/cntt-n/CNTT/issues/2025

[3] https://github.com/cntt-n/CNTT/issues/1984

[4] https://github.com/cncf/cnf-conformance

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7079): https://lists.onap.org/g/onap-tsc/message/7079
Mute This Topic: https://lists.onap.org/mt/76926448/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] List of approved licenses in ONAP dockers

2020-09-09 Thread Eric Debeau via lists.onap.org

Hello

To keep track of this discussion, please find the TSC decisions wiki page
https://wiki.onap.org/display/DW/2020+TSC+Decisions

During TSC 8/6/2020, "TSC agreed that only GPL v3 should be removed from the 
containers for the Guilin Release, distributed by the ONAP Community"

Best Regards

Eric

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

View/Reply Online (#7054): https://lists.onap.org/g/onap-tsc/message/7054
Mute This Topic: https://lists.onap.org/mt/75333278/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][EXTAPI] ptl election result

2020-09-09 Thread Eric Debeau via lists.onap.org

Congrats Adrian !

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Adrian 
Osullivan via lists.onap.org [adrian.osullivan=huawei@lists.onap.org]
Envoyé : mercredi 9 septembre 2020 11:19
À : onap-tsc@lists.onap.org
Objet : [onap-tsc][EXTAPI] ptl election result

Dear TSC,

I have been re-elected as EXTAPI PTL

Here are the voting results: 
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_d29b86969bbb2873

Voting Results Wiki has been updated: 
https://wiki.onap.org/display/DW/Voting+Results+History

Best Regards,

Adrian


Adrian O’Sullivan, Open Source EcoSystem Development  | Europe Standardization 
& Industry Development Dept (Corporate Strategy Dept) | Tel : +353 87 9590250 | 
Email:  adrian.osulli...@huawei.com  |
 Post Addr.:Huawei Ireland Research Centre (Cork), The Capitol 14-23 Grand 
Parade, Cork City, T12 F894, Ireland.

[Huawei LOGO]




_

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 (#7052): https://lists.onap.org/g/onap-tsc/message/7052
Mute This Topic: https://lists.onap.org/mt/76728805/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] M4 CLI-312 INFO.YAML Clean up

2020-09-02 Thread Eric Debeau via lists.onap.org

Hello Kanagaraj

OK to approve your proposal

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Kanagaraj 
Manickam via lists.onap.org [kanagaraj.manickam=huawei@lists.onap.org]
Envoyé : mardi 1 septembre 2020 13:53
À : onap-tsc
Cc : talas...@research.att.com; Ukponmwan, Itohan
Objet : [onap-tsc] M4 CLI-312 INFO.YAML Clean up

Hi,

I have observed that following contributors are inactive for more than year and 
as part of M4, and to fix this issue, Can you pls approve for the same.

- name: 'Subhash Kumar'
  email: 'subhash.kumar.si...@huawei.com' 
https://gerrit.onap.org/r/q/projects:cli+owner:subhash.kumar.singh%2540huawei.com
 (User does not exists)
  company: 'Huawei'
  id: 'subhash_singh'
 timezone: 'India/Bangalore'
- name: 'Manoop Talasila'
  email: 'talas...@research.att.com' 
https://gerrit.onap.org/r/q/projects:cli+owner:talasila%2540research.att.com 
(NO CONTRIBUTION)
  company: 'ATT'
  id: 'talasila'
  timezone: 'America/New York'
- name: 'Itohan Ukponmwan'
  email: 'itohan.ukponm...@intel.com'
[cid:image001.png@01D68084.A10FBD50]
  company: 'Intel'
  id: 'itohan'
  timezone: 'America/Pacific'

Kanagaraj Manickam
Lead Architect
Cloudfiy Networking OSDT
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka
Tel: + 91-80-49160700 ext 72410 Mob: 9945602938
[Company_logo]


This e-mail and its attachments contain confidential information from HUAWEI, 
which
is intended only for the person or entity whose address is listed above. Any 
use of the
information contained herein in any way (including, but not limited to, total 
or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify 
the sender by
phone or email immediately and delete it!



_

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 (#7039): https://lists.onap.org/g/onap-tsc/message/7039
Mute This Topic: https://lists.onap.org/mt/76554103/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] Committer updates for DCAE

2020-09-01 Thread Eric Debeau via lists.onap.org

Hi Vijay

No objections from TSC members, TSC approves this promotion. Congrats to 
Kornel, Remigiusz and Pawel.

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Vijay VK 
[vv7...@att.com]
Envoyé : lundi 31 août 2020 16:41
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] Committer updates for DCAE

Yes, indeed. All existing committers have voted in favor (approval link is 
provided on the wiki pages).

Thanks,
Vijay

From: onap-tsc@lists.onap.org  On Behalf Of Eric 
Debeau via lists.onap.org
Sent: Monday, August 31, 2020 10:34 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Committer updates for DCAE

Hello Vijay

Kornel, Remigiusz and Pawel have strongly contributed to DCAE (code + JIRA)

Best regards

Eric

De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[onap-tsc@lists.onap.org] de la part de Vijay VK [vv7...@att.com]
Envoyé : lundi 31 août 2020 16:11
À : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Objet : [onap-tsc] Committer updates for DCAE
Hi TSC,
Kindly request to  review & approve following committer promotions.

New committers/extensions

  *   Kornel Janiak 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5Ball+DCAE%5D%3A+Kornel+Janiak<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Committer-2BPromotion-2BRequest-2Bfor-2B-255Ball-2BDCAE-255D-253A-2BKornel-2BJaniak&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6WYcUG7NY-ZxfqWx5MmzVQ&m=WbILVF7YazR1Afsa3YG2O6vi3JhcyTI271Odv5q0r9c&s=llf0jhid1pXS3ZriqqZ094uzyq8E07PuN6HEmcuodwU&e=>
  *   Remigiusz Janeczek : 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5Ball+DCAE%5D%3A+Remigiusz+Janeczek<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Committer-2BPromotion-2BRequest-2Bfor-2B-255Ball-2BDCAE-255D-253A-2BRemigiusz-2BJaneczek&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6WYcUG7NY-ZxfqWx5MmzVQ&m=WbILVF7YazR1Afsa3YG2O6vi3JhcyTI271Odv5q0r9c&s=ipta2XotUKbOVcDL4uARYS8N_vHNZgUspVTNa6is_sU&e=>
  *   Pawel Kasperkiewicz : 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BDCAE%3Avescollector%5D%3A+Pawel+Kasperkiewicz<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Committer-2BPromotion-2BRequest-2Bfor-2B-255BDCAE-253Avescollector-255D-253A-2BPawel-2BKasperkiewicz&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=6WYcUG7NY-ZxfqWx5MmzVQ&m=WbILVF7YazR1Afsa3YG2O6vi3JhcyTI271Odv5q0r9c&s=QX_xOShJlKD0AUyufrre-Fmj8a26TSz1qU7g1zmALlQ&e=>
 (only dcaegen2/collector/ves repository)

Also want to notify below committers have moved out of ONAP project and/or left 
company - I will proceed revoking their committer privilege.

  *   Lusheng Ji (AT&T)
  *   Henrik Anderson (Ericsson)

Regards,
Vijay



_



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.


_

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:

Re: [onap-tsc] Committer updates for DCAE

2020-08-31 Thread Eric Debeau via lists.onap.org

Hello Vijay

Kornel, Remigiusz and Pawel have strongly contributed to DCAE (code + JIRA)

Best regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Vijay VK 
[vv7...@att.com]
Envoyé : lundi 31 août 2020 16:11
À : onap-tsc@lists.onap.org
Objet : [onap-tsc] Committer updates for DCAE

Hi TSC,
Kindly request to  review & approve following committer promotions.

New committers/extensions

  *   Kornel Janiak 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5Ball+DCAE%5D%3A+Kornel+Janiak
  *   Remigiusz Janeczek : 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5Ball+DCAE%5D%3A+Remigiusz+Janeczek
  *   Pawel Kasperkiewicz : 
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BDCAE%3Avescollector%5D%3A+Pawel+Kasperkiewicz
 (only dcaegen2/collector/ves repository)

Also want to notify below committers have moved out of ONAP project and/or left 
company - I will proceed revoking their committer privilege.

  *   Lusheng Ji (AT&T)
  *   Henrik Anderson (Ericsson)

Regards,
Vijay




_

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 (#7028): https://lists.onap.org/g/onap-tsc/message/7028
Mute This Topic: https://lists.onap.org/mt/76534453/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] [OOM] PTL election results

2020-07-21 Thread Eric Debeau via lists.onap.org

Congrats to Sylvain

Best regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Sylvain 
Desbureaux via lists.onap.org [sylvain.desbureaux=orange@lists.onap.org]
Envoyé : mardi 21 juillet 2020 15:56
À : onap-tsc@lists.onap.org
Cc : onap-rele...@lists.onap.org; Borislav Glozman; Mike Elliott; Krzysztof 
Opasiak
Objet : [onap-tsc] [OOM] PTL election results

Dear TSC members,

All committers of OOM project have voted 
(https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_3584830cbf9b0f18).

I've been elected as PTL.

Thanks OOM committers for their confidence.

Best regards,
Sylvain Desbureaux

_

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.




_

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 (#6830): https://lists.onap.org/g/onap-tsc/message/6830
Mute This Topic: https://lists.onap.org/mt/75703864/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] Project Lifecycle Reviews - TSC Action Required

2020-07-08 Thread Eric Debeau via lists.onap.org

Hi Jason

I am interested to review the comments

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Jason Hunt 
[djh...@us.ibm.com]
Envoyé : mardi 7 juillet 2020 22:09
À : onap-tsc@lists.onap.org
Objet : [onap-tsc] Project Lifecycle Reviews - TSC Action Required


Thank you to all the projects that have complete review templates for moving to 
the mature phase (see list below).

TSC Members:  Here's my suggested process for handling reviews...

In order to expedite the review process, I'd ask each of you to find time to 
read through each of the submissions and provide your comments directly in the 
wiki page.  For those projects that have already submitted, please complete by 
FRIDAY JULY 17.

I will then schedule a couple calls for July 20th and 21st for a working team 
to review the comments and make a recommendation to the TSC. (please let me 
know if you are interested)

The TSC will then review and vote during the meeting on July 23rd.

Completed templates can be found here:  
https://wiki.onap.org/display/DW/Project+Maturity+Reviews

Projects that have sent emails to the TSC requesting review (let me know if I 
missed anyone):

SDC
CLAMP
MultiCloud
CLI
VNFSDK

Thanks!


Regards,
Jason Hunt
Distinguished Engineer, IBM

Phone: +1-314-749-7422
Email: djh...@us.ibm.com
Twitter: @DJHunt



_

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 (#6707): https://lists.onap.org/g/onap-tsc/message/6707
Mute This Topic: https://lists.onap.org/mt/75363187/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] Guilin milestone status / M1 scheduled July 9 #guilin

2020-07-01 Thread Eric Debeau via lists.onap.org

Hi David

1. Yes and DOC
2. The Documentation project is also producing some own documentation and the 
overall documentation (eg user guides) and is responsible to publish (release 
note, architecture, overview...).

Best Regards

Eric

De : David McBride [dmcbr...@linuxfoundation.org]
Envoyé : jeudi 2 juillet 2020 00:48
À : onap-tsc; DEBEAU Eric TGI/OLN
Cc : onap-...@lists.onap.org; Kenny Paul
Objet : Re: [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

Thanks, Eric.

  1.  How about the project planning template? Would this apply to INT and OOM?
  2.  The document tracking table tracks individual project documentation. 
AFAIK - the DOC project manages production and publication of the overall 
documentation, but doesn't produce their own documentation.  Am I missing 
something?

David

On Wed, Jul 1, 2020 at 1:35 PM Eric Debeau via 
lists.onap.org<http://lists.onap.org> 
mailto:orange@lists.onap.org>> wrote:
Hello David

I understand and it is good to optimize the management tasks for OOM, INT and 
DOC ;-)

However, I believe that

  *
Update the FOSS wiki page applies for OOM, INT and DOC
  *
Add documents to document tracking table applies for OOM, INT and DOC
  *
Communicate API changes to other projects => may apply to OOM if we change K8S 
version

Best Regards

Eric

De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>] de la part de David 
McBride [dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>]
Envoyé : mercredi 1 juillet 2020 16:58
À : onap-tsc
Cc : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; Kenny Paul
Objet : Re: [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

Hi Eric,

I received feedback during the Frankfurt release that many of the "standard" 
release management tasks are not applicable to OOM and INT.  I'm trying to do a 
limited amount of customization of the tasks to ensure that the tasks are 
meaningful to the projects that they are assigned to.  If you could review the 
M1 tasks and let me know which you believe are applicable to OOM and INT, I 
would be happy to generate the issues and track status.  Thanks.

David

On Tue, Jun 30, 2020 at 11:40 PM Eric Debeau via 
lists.onap.org<http://lists.onap.org> 
mailto:orange@lists.onap.org>> wrote:
Hi David

I notice that some projects are not tracked (Documentation, Integration, OOM) 
while other are still there (Logging)

We should also consider CDS as a separate project.

Best Regards

Eric

De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>] de la part de David 
McBride [dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>]
Envoyé : mercredi 1 juillet 2020 01:25
À : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Cc : onap-tsc; Kenny Paul
Objet : [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

Team,

In reviewing the Guilin Milestone Status<https://wiki.onap.org/x/FboLBQ>, I was 
startled to see that 18/26 projects tracked still have 7+ of their 8 milestone 
tasks still in the Open state (see attachment), with just 9 days to go until M1!

Please get started with your project milestone tasks ASAP.  Remember that the 
Guilin release has a short schedule of just 4 months.  We need to hit our 
milestone dates in order to stay on track.

If you are blocked for some reason, or need help, please let me or Catherine 
know.

Thanks

David

--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
IRC: dmcbride

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.



--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile

Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

2020-07-01 Thread Eric Debeau via lists.onap.org

Hello

CDS has not a good visibility. CDS is not described in the Architecture figure 
as an example.
We believe that CDS will take a more important role in the coming releases. 
There is more and more PoD deployed for CDS and we should have more Health 
Check dedicated to CDS for example.

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de TIMONEY, 
DAN [dtimo...@att.com]
Envoyé : mercredi 1 juillet 2020 18:14
À : onap-...@lists.onap.org; dmcbr...@linuxfoundation.org; onap-tsc
Cc : Kenny Paul
Objet : Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 9 
#guilin

Eric,

I’m not sure I understand your ask to track CDS as a separate project.  As you 
know, CDS is part of CCSDK.   Can you please say a little more about what you 
had in mind?

Dan



From:  on behalf of David McBride 

Reply-To: "onap-...@lists.onap.org" , 
"dmcbr...@linuxfoundation.org" 
Date: Wednesday, July 1, 2020 at 10:59 AM
To: onap-tsc 
Cc: "onap-...@lists.onap.org" , Kenny Paul 

Subject: Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 
9 #guilin

Hi Eric,

I received feedback during the Frankfurt release that many of the "standard" 
release management tasks are not applicable to OOM and INT.  I'm trying to do a 
limited amount of customization of the tasks to ensure that the tasks are 
meaningful to the projects that they are assigned to.  If you could review the 
M1 tasks and let me know which you believe are applicable to OOM and INT, I 
would be happy to generate the issues and track status.  Thanks.

David

On Tue, Jun 30, 2020 at 11:40 PM Eric Debeau via 
lists.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.onap.org&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=3iMe5LrAmPH95HS6qeK7GKQsUa5Ej6kQ8oB3mAFSn_M&s=u21xDaekPZG17IEAFXe5xtzy6r7BBgWSruCk8b39zbc&e=>
 mailto:orange@lists.onap.org>> 
wrote:
Hi David

I notice that some projects are not tracked (Documentation, Integration, OOM) 
while other are still there (Logging)

We should also consider CDS as a separate project.

Best Regards

Eric

De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>] de la part de David 
McBride [dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>]
Envoyé : mercredi 1 juillet 2020 01:25
À : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Cc : onap-tsc; Kenny Paul
Objet : [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin
Team,

In reviewing the Guilin Milestone 
Status<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_x_FboLBQ&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=3iMe5LrAmPH95HS6qeK7GKQsUa5Ej6kQ8oB3mAFSn_M&s=lNfC_payfzzA1Hv_sN-msT7FUtnSqB6nJv5X9mYUQUc&e=>,
 I was startled to see that 18/26 projects tracked still have 7+ of their 8 
milestone tasks still in the Open state (see attachment), with just 9 days to 
go until M1!

Please get started with your project milestone tasks ASAP.  Remember that the 
Guilin release has a short schedule of just 4 months.  We need to hit our 
milestone dates in order to stay on track.

If you are blocked for some reason, or need help, please let me or Catherine 
know.

Thanks

David

--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
IRC: dmcbride

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.


--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
IRC: dmcbride


__

Re: [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

2020-07-01 Thread Eric Debeau via lists.onap.org

Hello David

I understand and it is good to optimize the management tasks for OOM, INT and 
DOC ;-)

However, I believe that

  *
Update the FOSS wiki page applies for OOM, INT and DOC
  *
Add documents to document tracking table applies for OOM, INT and DOC
  *
Communicate API changes to other projects => may apply to OOM if we change K8S 
version

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de David 
McBride [dmcbr...@linuxfoundation.org]
Envoyé : mercredi 1 juillet 2020 16:58
À : onap-tsc
Cc : onap-...@lists.onap.org; Kenny Paul
Objet : Re: [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

Hi Eric,

I received feedback during the Frankfurt release that many of the "standard" 
release management tasks are not applicable to OOM and INT.  I'm trying to do a 
limited amount of customization of the tasks to ensure that the tasks are 
meaningful to the projects that they are assigned to.  If you could review the 
M1 tasks and let me know which you believe are applicable to OOM and INT, I 
would be happy to generate the issues and track status.  Thanks.

David

On Tue, Jun 30, 2020 at 11:40 PM Eric Debeau via 
lists.onap.org<http://lists.onap.org> 
mailto:orange@lists.onap.org>> wrote:
Hi David

I notice that some projects are not tracked (Documentation, Integration, OOM) 
while other are still there (Logging)

We should also consider CDS as a separate project.

Best Regards

Eric

De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>] de la part de David 
McBride [dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>]
Envoyé : mercredi 1 juillet 2020 01:25
À : onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Cc : onap-tsc; Kenny Paul
Objet : [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

Team,

In reviewing the Guilin Milestone Status<https://wiki.onap.org/x/FboLBQ>, I was 
startled to see that 18/26 projects tracked still have 7+ of their 8 milestone 
tasks still in the Open state (see attachment), with just 9 days to go until M1!

Please get started with your project milestone tasks ASAP.  Remember that the 
Guilin release has a short schedule of just 4 months.  We need to hit our 
milestone dates in order to stay on track.

If you are blocked for some reason, or need help, please let me or Catherine 
know.

Thanks

David

--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
IRC: dmcbride

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.



--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
IRC: dmcbride


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You

Re: [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

2020-06-30 Thread Eric Debeau via lists.onap.org

Hi David

I notice that some projects are not tracked (Documentation, Integration, OOM) 
while other are still there (Logging)

We should also consider CDS as a separate project.

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de David 
McBride [dmcbr...@linuxfoundation.org]
Envoyé : mercredi 1 juillet 2020 01:25
À : onap-...@lists.onap.org
Cc : onap-tsc; Kenny Paul
Objet : [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

Team,

In reviewing the Guilin Milestone Status, I was 
startled to see that 18/26 projects tracked still have 7+ of their 8 milestone 
tasks still in the Open state (see attachment), with just 9 days to go until M1!

Please get started with your project milestone tasks ASAP.  Remember that the 
Guilin release has a short schedule of just 4 months.  We need to hit our 
milestone dates in order to stay on track.

If you are blocked for some reason, or need help, please let me or Catherine 
know.

Thanks

David

--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
IRC: dmcbride


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


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

View/Reply Online (#6632): https://lists.onap.org/g/onap-tsc/message/6632
Mute This Topic: https://lists.onap.org/mt/75225170/21656
Mute #guilin: https://lists.onap.org/g/onap+onap-tsc/mutehashtag/guilin
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] Docs submodule deprecation

2020-06-25 Thread Eric Debeau via lists.onap.org

Thanks Jessica (and Aric) for your efforts

Best Regards

Eric

De : onap-rele...@lists.onap.org [onap-rele...@lists.onap.org] de la part de 
jwagant...@linuxfoundation.org [jwagant...@linuxfoundation.org]
Envoyé : mercredi 24 juin 2020 23:17
À : onap-disc...@lists.onap.org; onap-release; onap-tsc
Objet : [Onap-release] Docs submodule deprecation

Dear teams,

As we agreed previously in the TSC calls and today's Docs virtual event,
we are proceeding with the deprecation of docs submodules:
https://gerrit.onap.org/r/c/doc/+/106771

Going forward we are not going to run both submodules and intersphinx linking
in parallel to avoid confusions among teams.

Please let us know if you have any questions.
For any docs specific issues please continue to report them in the tracker and
we will address them:
https://wiki.onap.org/display/DW/Docs+migration+tracker

Thanks a ton for your support!
Jess




_

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 (#6598): https://lists.onap.org/g/onap-tsc/message/6598
Mute This Topic: https://lists.onap.org/mt/75098379/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][Integration] new repository for integration team testsuite/robot-utils

2020-06-10 Thread Eric Debeau via lists.onap.org

Thanks Catherine

Best REgards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Catherine 
LEFEVRE [catherine.lefe...@intl.att.com]
Envoyé : mercredi 10 juin 2020 20:17
À : onap-tsc@lists.onap.org; infrastructure-coordina...@onap.org
Cc : Szwałkiewicz, Marek
Objet : Re: [onap-tsc] [ONAP][Integration] new repository for integration team 
testsuite/robot-utils

Good evening Morgan,

I understand our Infrastructure coordinator is on leave.
Therefore, on behalf of the ONAP TSC, I have reviewed your request and I 
approve it.

Best regards
Catherine
From: onap-tsc@lists.onap.org  On Behalf Of Morgan 
Richomme via lists.onap.org
Sent: Wednesday, June 10, 2020 5:49 PM
To: infrastructure-coordina...@onap.org
Cc: onap-tsc@lists.onap.org; Szwałkiewicz, Marek 

Subject: [onap-tsc] [ONAP][Integration] new repository for integration team 
testsuite/robot-utils

Hi

I would like to ask for the creation of a new repository testsuite/robot-utils.
This repository will host the code of a wrapper to offer onap-pythonsdk 
functions to robot test developers.
It will be a small repo include python, robot and configuration files.

I updated the page 
https://wiki.onap.org/display/DW/Resources+and+Repositories.

Thanks and regards

Morgan



_



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.


_

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 (#6525): https://lists.onap.org/g/onap-tsc/message/6525
Mute This Topic: https://lists.onap.org/mt/74799536/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 Project Lifecycle: recommended actions

2020-06-05 Thread Eric Debeau via lists.onap.org

Hello

I believe that we need more formal proof of maturity checked by tools to avoid 
any dispute.

›Successful participation in releases: The project demonstrates stable output 
(code base, documents) within its history of releases in accordance with the 
release policy.

=> How to check that a document is stable ?

›Architecture has been reviewed by the Architecture Committee => It do not see 
a proof a maturity. Every project should pass the Architecture Review and can 
claim to become mature. We should state the project passed the Architecture 
Committe

›Project is active and contributes to ONAP: The project demonstrates a stable 
or increasing number of contributions across recent releases. Contributions are 
commits which got merged to a repository of an ONAP project or a related 
upstream project. Commits can for example be patches to update the requirements 
document of a project, code addition to an ONAP or upstream project repository, 
new test cases and so forth.

=> OK. It is easy to check with bitergia

›Mature artifacts produced: The project demonstrates that the artifacts 
produced by the project are deployable (where applicable) and have been 
successfully deployed, configured and used by end users (typically, service 
providers).

=> Any project can claim that if they are in the release !
=> We need more technical proofs : eg code quality, test coverage...

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Jason Hunt 
[djh...@us.ibm.com]
Envoyé : vendredi 5 juin 2020 21:45
À : onap-tsc@lists.onap.org
Cc : az9...@att.com; k.opas...@samsung.com; onap-rele...@lists.onap.org; 
onap-tsc@lists.onap.org; p.paw...@f5.com
Objet : Re: [onap-tsc] ONAP Project Lifecycle: recommended actions

I don't think we'd want to codify that list of criteria into the technical 
community document, so what we might want to do is amend the document to 
require a Security Subcommittee review prior to a project moving to the mature 
or core phases.  This would need to be voted on by the TSC.  Should we cover it 
in the next TSC meeting?

Regards,
Jason Hunt
Distinguished Engineer, IBM

Phone: +1-314-749-7422
Email: djh...@us.ibm.com
Twitter: @DJHunt

- Original message -
From: "Sylvain Desbureaux via lists.onap.org" 

Sent by: onap-tsc@lists.onap.org
To: Krzysztof Opasiak , "onap-tsc@lists.onap.org" 

Cc: "az9...@att.com" , "onap-rele...@lists.onap.org" 
, "p.paw...@f5.com" 
Subject: [EXTERNAL] Re: [onap-tsc] ONAP Project Lifecycle: recommended actions
Date: Fri, Jun 5, 2020 10:08 AM

+1
and one day we may need to be able to add new criterias for the ops
(I'm thinking opentracing compatibility, prometheus endpoints, ...)

De : Krzysztof Opasiak [k.opas...@samsung.com]
Envoyé : vendredi 5 juin 2020 16:53
À : onap-tsc@lists.onap.org
Cc : az9...@att.com; onap-rele...@lists.onap.org; p.paw...@f5.com; DESBUREAUX 
Sylvain TGI/OLN
Objet : Re: [onap-tsc] ONAP Project Lifecycle: recommended actions

... and correct Pawel Pawlak email;)

On 05.06.2020 16:53, Krzysztof Opasiak wrote:
> Hi Jason,
>
> On 05.06.2020 16:27, Jason Hunt wrote:
>>Krzysztof,
>> Great point.  There are two options to address it:
>> 1. The TSC votes to amend the Technical Community Document to include
>> security in the criteria for the mature state
>> 2.  We modify the template for the maturity reviews to allow for
>> security information to be included under the "mature artifacts"
>> criteria.  The TSC would then include that in its decision whether a
>> project has met the "mature artifacts" portion of the criteria.
>
> I'll deffer this to Pawel & Amy to decide which way to go.
>
>> I would prefer the latter and am happy to make the update.  Please let
>> me know if there is suggested input you would like to see from projects
>> so that we can update the template accordingly.
>
> I'd definitely would like to make sure that before any project is called
> mature it:
>
> 1) Does not hardcode any credentials in the container & OOM helm charts
> 2) Its docker containers are free of any hardcoded certificates
> 3) It doesn't use static TLS certificates but obtains them at runtime
> 4) It has no open OJSI tickets
> 5) It has no known vulnerabilities in its direct dependencies
> 6) It uses base image that is free of license violation and
> vulnerabilities (aka recommended by seccom)
> 7) Does not run as a root
> 8) Does not access any DB as root from the application container (unless
> there is a valid reason for that which has been presented & approved by
> SECCOM)
> 9) Does not access any DB that is owned by other service
> 10) Uses only well-known, open source libraries for handling crypto
> 11) Does not contain its own user store
> 12) Can be access & used via ingress controller
> 13) Has no runtime Internet dependencies
> 14) Use secure communication to access anything that is outside of
> kubernetes cluster
> 15) Has no un

[onap-tsc] Orange proxy today

2020-05-26 Thread Eric Debeau via lists.onap.org

Hello

Morgan Richomme will be the Orange proxy for the TSC today

Best regards

Eric

_

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 (#6426): https://lists.onap.org/g/onap-tsc/message/6426
Mute This Topic: https://lists.onap.org/mt/74476074/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] Morgan will be Orange proxy today

2020-05-14 Thread Eric Debeau via lists.onap.org

Hello

Morgan Richomme will be the Orange proxy for the TSC meeting today

Best Regards

Eric

_

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 (#6363): https://lists.onap.org/g/onap-tsc/message/6363
Mute This Topic: https://lists.onap.org/mt/74203242/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-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing development work

2020-04-30 Thread Eric Debeau via lists.onap.org

Hi Srini

Any news from COE team ?

Best Regards

Eric

De : onap-cnf-taskfo...@lists.onap.org [onap-cnf-taskfo...@lists.onap.org] de 
la part de Srini [srinivasa.r.addepa...@intel.com]
Envoyé : jeudi 23 avril 2020 15:16
À : onap-cnf-taskfo...@lists.onap.org; DEBEAU Eric TGI/OLN; 
k.opas...@samsung.com; ranny.ha...@samsung.com; catherine.lefe...@intl.att.com; 
onap-tsc@lists.onap.org
Cc : DESBUREAUX Sylvain TGI/OLN
Objet : Re: [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing 
development work

Hi Eric,

Thank you for pointer to select micro-services in each project. We will propose 
it to ONAP COE team tomorrow.

On the profiles:  It is my view that if set of projects/micro-services from 
ONAP are taken to do Application/NF life cycle management across multiple 
sites, then I thought it qualifies.  For example, using ONAP4K8s profile, one 
can do following

  *   On-board complex applications (Consisting of multiple applications with 
each application consisting of multiple micro-services – CNAs & CNFs)
  *   Defining complex application profiles
  *   Defining deployment intents (Placement intents and action intents)
  *   One-Click deployment of complex application – Which deploys 
micro-services of applications of complex applications based on placement 
intents across multiple Edge/Cloud K8s clusters.
  *   One-Click termination of complex application deployment.
  *   Modify existing deployment or upgrade existing deployment – Roadmap
  *   Auto-Creation of Edge/Cloud cluster specific service mesh, load balancer 
rules, firewall rules, NAT rules to enable connectivity among the 
micro-services deployed in various clusters – Roadmap
  *   Platform aware placement – Roadmap
  *   Uses many CNCF projects (Prometheus for metrics, Jaeger for tracing, 
fluentD for logging,  ISTIO+Envoy+AuthService for IAM+Mutual-TLS etc..) for 
basic functionality.

That said, I am personally okay to remove ONAP4K8s profile documentation & 
pages from ONAP wiki and move it elsewhere.  Will discuss with COE team and 
take next steps.

Thanks
Srini

-Original Message-
From: onap-cnf-taskfo...@lists.onap.org  On 
Behalf Of Eric Debeau via lists.onap.org
Sent: Wednesday, April 22, 2020 11:27 PM
To: onap-cnf-taskfo...@lists.onap.org; k.opas...@samsung.com; Addepalli, 
Srinivasa R ; ranny.ha...@samsung.com; 
catherine.lefe...@intl.att.com; onap-tsc@lists.onap.org
Cc: DESBUREAUX Sylvain TGI/OLN 
Subject: Re: [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and 
existing development work

Hi Srini

I have 2 concerns:
- We are using ONAP term while using only one component from one project. If we 
generalize that position, it means that I can just use VES collector with my 
solution and states my solution is ONAP based. Why not, but we should agree at 
ONAP community.
- We are using dedicated thread for the installation and it is not tested in 
the ONAP process as it is. As a result, it is difficult to validate it as ONAP 
technical recipe

On technical topic, It is possible to select sub-components in OOM to only 
deploy relevant components.

A&AI and DMAAP projects have started this effort and I belive that Sylvain 
would like to extend it for Guilin for other core projects.
https://git.onap.org/aai/oom/tree/components
https://git.onap.org/oom/tree/kubernetes/dmaap/components

As a result, you can only select the components required for your needs.

I only raise concerns that I would like to share with TSC, but we should decide 
as a community.

Best Regards

Eric

De : 
onap-cnf-taskfo...@lists.onap.org<mailto:onap-cnf-taskfo...@lists.onap.org> 
[onap-cnf-taskfo...@lists.onap.org] de la part de Krzysztof Opasiak via 
lists.onap.org [k.opasiak=samsung@lists.onap.org]
Envoyé : mercredi 22 avril 2020 23:26
À : 
onap-cnf-taskfo...@lists.onap.org<mailto:onap-cnf-taskfo...@lists.onap.org>; 
srinivasa.r.addepa...@intel.com<mailto:srinivasa.r.addepa...@intel.com>; DEBEAU 
Eric TGI/OLN; ranny.ha...@samsung.com<mailto:ranny.ha...@samsung.com>; 
catherine.lefe...@intl.att.com<mailto:catherine.lefe...@intl.att.com>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> Objet : Re: 
[onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing development 
work

On 22.04.2020 23:14, Srini wrote:
> Hi Eric,
>
> Just to be on the same page:
>
>  1. Application life cycle management on K8s Clusters is taken care by
> following micro-services
>  1. K8s Plugin Service in Multi Cloud project (new development)
>  2. Mongo DB & etcd (Non-ONAP open source)
>  3. SDC Client in Multi-Cloud (New development)
>  4. SDC modifications
>  5. SO modification
>  6. Multi-Cloud broker modifications.
>  2. ONAP4K8s is one recipe and useful for greenfield (e.g Enterprises
> and Industry 4.0) deployments. It has f

Re: [onap-tsc] FW: Committer Promotion Request for VNFSDK

2020-04-23 Thread Eric Debeau via lists.onap.org

Hello

OK to remove mickael.jezeq...@orange.com as he is no longer 
an ONAP committer for this project

Best regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Catherine 
LEFEVRE [catherine.lefe...@intl.att.com]
Envoyé : jeudi 23 avril 2020 14:16
À : onap-tsc@lists.onap.org
Cc : infrastructure-coordina...@onap.org
Objet : Re: [onap-tsc] FW: Committer Promotion Request for VNFSDK

Good morning Xinhui,

My apologies for the delayed response.
I do not see any vote from the following committers:

Moshe Hoadley

@mickael.jezeq...@orange.com

wenyao guan

Are these people still active?
If not then I suggest to remove them from the committers list.
Can we clarify this before promoting Bogumil? Thank you


Best regards
Catherine


_

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 (#6199): https://lists.onap.org/g/onap-tsc/message/6199
Mute This Topic: https://lists.onap.org/mt/73055676/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-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing development work

2020-04-22 Thread Eric Debeau via lists.onap.org

Hi Srini

I have 2 concerns:
- We are using ONAP term while using only one component from one project. If we 
generalize that position, it means that I can just use VES collector with my 
solution and states my solution is ONAP based. Why not, but we should agree at 
ONAP community.
- We are using dedicated thread for the installation and it is not tested in 
the ONAP process as it is. As a result, it is difficult to validate it as ONAP 
technical recipe

On technical topic, It is possible to select sub-components in OOM to only 
deploy relevant components.

A&AI and DMAAP projects have started this effort and I belive that Sylvain 
would like to extend it for Guilin for other core projects.
https://git.onap.org/aai/oom/tree/components
https://git.onap.org/oom/tree/kubernetes/dmaap/components

As a result, you can only select the components required for your needs. 

I only raise concerns that I would like to share with TSC, but we should decide 
as a community.

Best Regards

Eric

De : onap-cnf-taskfo...@lists.onap.org [onap-cnf-taskfo...@lists.onap.org] de 
la part de Krzysztof Opasiak via lists.onap.org 
[k.opasiak=samsung@lists.onap.org]
Envoyé : mercredi 22 avril 2020 23:26
À : onap-cnf-taskfo...@lists.onap.org; srinivasa.r.addepa...@intel.com; DEBEAU 
Eric TGI/OLN; ranny.ha...@samsung.com; catherine.lefe...@intl.att.com; 
onap-tsc@lists.onap.org
Objet : Re: [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing 
development work

On 22.04.2020 23:14, Srini wrote:
> Hi Eric,
>
> Just to be on the same page:
>
>  1. Application life cycle management on K8s Clusters is taken care by
> following micro-services
>  1. K8s Plugin Service in Multi Cloud project (new development)
>  2. Mongo DB & etcd (Non-ONAP open source)
>  3. SDC Client in Multi-Cloud (New development)
>  4. SDC modifications
>  5. SO modification
>  6. Multi-Cloud broker modifications.
>  2. ONAP4K8s is one recipe and useful for greenfield (e.g Enterprises
> and Industry 4.0) deployments. It has following
>  1. K8s Plugin Service in Multi Cloud project
>  2. Security Micro-services (SMS, Vault, TPM related)
>  3. Mongo DB & etcd (Non-ONAP open source)
>
>  From the beginning, we wanted to make sure that everything we do is
> modular and can be deployed standalone fashion,  keeping micro-service
> architecture principles in mind.
>
> ONAP4K8s recipe need not be used if the intention is to use along with
> rest of ONAP (SDC, SO, AAF, OOF etc…). We have both models supported
> (standalone or integrated).
>
> ONAP4K8s is mainly for greenfield scenarios.
>
> If the term ‘ONAP’ in ONAP4K8s is confusing, we can rename this recipe
> as something else.  I think based on another email on similar subject,
> you seem to be implying that if people are not using some components
> such as SDC, SO, AAF are not used, then it should not be called as ONAP.
> If this is the concern,  we don’t mind removing ONAP4K8s page altogether
> and put it in places (such as Akraino/ICN) where it is being used.  Let
> us know.
>
> Is the concern/confusion that we are not using OOM for this profile? If
> this is the concern, we do have plans to ensure that OOM is leveraged
> for creating the profile with above services as in (2).  But at this
> time, OOM granularity is selection of projects, but not micro-services
> in each project. Hence, we created something to move forward.

Such a feature is more than welcome in OOM so instead of creating this
from scratch you can just submit a patch to OOM:)

Patches are always welcomed

>
> Thanks
>
> Srini
>
> *From:* onap-cnf-taskfo...@lists.onap.org
>  *On Behalf Of *Eric Debeau via
> lists.onap.org
> *Sent:* Wednesday, April 22, 2020 11:51 AM
> *To:* onap-cnf-taskfo...@lists.onap.org; ranny.ha...@samsung.com;
> catherine.lefe...@intl.att.com; onap-tsc@lists.onap.org
> *Subject:* Re: [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC
> and existing development work
>
> Hi
>
> I participated this afternoon to the various sessions around CNF where
> there is a lot of activities for this long journey towards managing CNF.
>
> However, I am still confused about the communication about ONAP4K8S and
> the statement that we should rely on ONAP4K8S to manage CNF in ONAP.
>
> We can not state that ONAP4K8 is an ONAP profile. Based on the code
> available on the ONAP repo
> https://git.onap.org/multicloud/k8s/tree/deployments/helm/onap4k8s,
> <https://protect2.fireeye.com/url?k=b34b8f34-ee9f335c-b34a047b-0cc47a3356b2-306c885440378ef9&q=1&u=https%3A%2F%2Fgit.onap.org%2Fmulticloud%2Fk8s%2Ftree%2Fdeployments%2Fhelm%2Fonap4k8s%2C>
> we can see that ONAP4K8S is not using existing ONAP project. There is a
&g

Re: [onap-tsc] [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing development work

2020-04-22 Thread Eric Debeau via lists.onap.org

Hi

I participated this afternoon to the various sessions around CNF where there is 
a lot of activities for this long journey towards managing CNF.

However, I am still confused about the communication about ONAP4K8S and the 
statement that we should rely on ONAP4K8S to manage CNF in ONAP.

We can not state that ONAP4K8 is an ONAP profile. Based on the code available 
on the ONAP repo 
https://git.onap.org/multicloud/k8s/tree/deployments/helm/onap4k8s, we can see 
that ONAP4K8S is not using existing ONAP project. There is a dedicated chart 
for the deployment not reusing existing ONAP ones (managed by OOM project):
https://git.onap.org/multicloud/k8s/tree/deployments/helm/onap4k8s. It is only 
based on one Docker from multicoud project (multicloud-ks), mongodb, etcd and 
other common components with no reference to existing official ONAP charts 
defined in OOM repo.

I have no problem if we consider it clearly as a PoC, but we can not claim that 
is an ONAP profile and the way we communicate on ONAP4K8S is not clear an is 
very confusing.

As an example of "ONAP profile", we can find one for 5G slicing use-case where 
the use-case team has defined an optimized subset of ONAP components for their 
slicing use-case: 
https://git.onap.org/oom/tree/kubernetes/onap/resources/overrides/onap-5g-network-slicing.yaml

We really need to clarify this topic.

Best Regards

Eric

De : onap-cnf-taskfo...@lists.onap.org [onap-cnf-taskfo...@lists.onap.org] de 
la part de Ranny Haiby (Samsung) via lists.onap.org 
[ranny.haiby=samsung@lists.onap.org]
Envoyé : mardi 21 avril 2020 01:56
À : onap-cnf-taskfo...@lists.onap.org; catherine.lefe...@intl.att.com
Objet : Re: [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and existing 
development work

Hi Catherine,

Thanks for defining the scope of WS7. I admit it was not clear to me before, 
and now it makes much sense.

One thing If I may suggest – the phrasing of “Initial experimentations with 
basic CNF(s)…” sounds a bit non-committal, as if we are not sure if and when we 
want to support CNFs. How about “Incremental improvements to accommodate for 
CNF(s) in order to validate…”

Regards,

Ranny.


From:  on behalf of Catherine LEFEVRE 

Reply-To: "onap-cnf-taskfo...@lists.onap.org" 
, "catherine.lefe...@intl.att.com" 

Date: Monday, April 20, 2020 at 12:16 PM
To: "onap-cnf-taskfo...@lists.onap.org" 
Subject: Re: [onap-cnf-taskforce] OVP 2.0 - Workstream 7 - ONAP POC and 
existing development work
Resent-From: 

Team,

I have tried to define the scope of WS07 track as follows:
WS07 Scope: ONAP POCs & Existing Development Work to support CNFs

  *   Initial experimentations with basic CNF(s) in order to validate 
onboarding, instantiation of multiple CNFs, monitoring, etc. processes
  *   Implement what you learn from ETSI-based CNF support
  *   Pursue our Cloud Native Security journey by leveraging the benefits of a 
Service Mesh
https://wiki.lfnetworking.org/display/LN/OVP+2.0+Workstreams


I have also updated the following wiki - 
https://wiki.lfnetworking.org/pages/viewpage.action?pageId=34603941
I have merged #1 and #5 together.
Under item #1 – I have also added the CDS work developed in Frankfurt as 
suggested by Lucasz

Shall I also merge #3 SO with the new #1 cFW POC ?
If yes then I can rename #1 as “Initial experimentations with basic CNF(s) in 
order to validate onboarding, instantiation of multiple CNFs, monitoring 
processes”
So it gives us more time to evaluate the two paths – SO & Multi-Cloud.

The OVP Cloud Native session is on day3 so it would be great if we can finalize 
our WS07 section before that
I have also added a note ‘draft version’ so it gives us an opportunity to 
refine our mind.

Thanks in advance for your support.

Best regards
Catherine


_

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 an

Re: [onap-tsc] [onap-ptl] [ONAP] Daily master (pre-Frankfurt) CI follow-up

2020-04-01 Thread Eric Debeau via lists.onap.org

Hello David

38% is the average value for the 4 test families

  *   infrastructure-healthcheck: 100%
  *   healthcheck: 50%
  *   smoke usecases: 0%
  *   security: 0%

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de David 
McBride [dmcbr...@linuxfoundation.org]
Envoyé : mercredi 1 avril 2020 17:48
À : onap-...@lists.onap.org; RICHOMME Morgan TGI/OLN
Cc : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] [onap-ptl] [ONAP] Daily master (pre-Frankfurt) CI 
follow-up

Thanks, Morgan.

Is the value at the top (38%) an aggregate of the values below (infra HC, HC, 
smoke, security)?

David

On Tue, Mar 31, 2020 at 3:04 AM Morgan Richomme via 
Lists.Onap.Org 
mailto:orange@lists.onap.org>> 
wrote:
Hi

as discussed yesterday during the PTL meeting, please find hereafter some links 
to track the daily master test results (pre-Frankfurt).

I already started exchanging with the PTLs to confirm that the versions are the 
correct ones based on the "Verify Readiness dashboard".

We tried to simplify the access to the daily Master release page.
We already hosted the gating results (until they are merged).
We just added the Master daily (executed in Orange DC)

All the results can be found here:
https://gating-results.onap.eu/results/

the daily Master results will be pushed daily (if the pipeline succeeds) under 
onap_daily_pod4_master--

today it is under 
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/

You should see a page providing a summary of the CI tests
Click on Full Results to get the list of tests per category
e.g. infrastructure-healthcheck => 2 tests: onap-helm and onap-k8s
then click on the test to get results/logs corresponding to the test

If you want to get the onap-k8s status => click on onap-k8s
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/infrastructure-healthcheck/k8s/index.html
from this page you can have the snapshot of all the versions used for the 
installation.
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/infrastructure-healthcheck/k8s/versions.html

the robot healthcheck results can be found here: 
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/healthcheck/full/full/report.html
at the moment we have 2 tests failing: CLI and NBI (both are addressed through 
a JIRA/gerrit in progress)

Regarding the security tests
for Frankfurt we will focus on
- root_pods
- http_public_endpoints
- jdpw_ports

click on the link to see the status
today
- root pods => 47 pods remaining (wait for new dockers, most of them should 
disappear within the next days...)
- http_public_endpoints: still 4 ports (as discussed yesterday - the 4 issues 
are tracked)
- jdpw_ports: 1 port still open, fix announced for several weeks but no docker 
released and submited in OOM Master yet

For the End to End tests
- basic VM onboarding/distribution/instantiation using VNF API),  SDC 
onboarding/distribution seems OK but we can see an error on instantiation on 
module creation ('requestState': 'FAILED', 'statusMessage': 'STATUS: Received 
error from SDN-C: Error processing request to SDNC. Connection refused 
(Connection refused))
see 
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/smoke-usecases/basic_vm/xtesting.debug.log
-freeradius_nbi: error occurs earlier (onboarding/distribution still fine) but 
error on service creation at instantiation, could be linked to issue on NBI to 
be troublesshoted (no service instance retrieved from NBI)


/Morgan




_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.



--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
IRC: dmcbride


_

Re: [onap-tsc] [ONAP] Daily master (pre-Frankfurt) CI follow-up

2020-03-31 Thread Eric Debeau via Lists.Onap.Org

Thanks Morgan

It gives a very detailed view about the ONAP status and it is easy to browse.

Confrats to Integration and OOM teams for this wonderful effort.

We can also see very good progress on the security.

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Morgan 
Richomme via Lists.Onap.Org [morgan.richomme=orange@lists.onap.org]
Envoyé : mardi 31 mars 2020 12:04
À : onap-...@lists.onap.org
Cc : onap-tsc@lists.onap.org
Objet : [onap-tsc] [ONAP] Daily master (pre-Frankfurt) CI follow-up

Hi

as discussed yesterday during the PTL meeting, please find hereafter some links 
to track the daily master test results (pre-Frankfurt).

I already started exchanging with the PTLs to confirm that the versions are the 
correct ones based on the "Verify Readiness dashboard".


We tried to simplify the access to the daily Master release page.
We already hosted the gating results (until they are merged).
We just added the Master daily (executed in Orange DC)

All the results can be found here: 
https://gating-results.onap.eu/results/

the daily Master results will be pushed daily (if the pipeline succeeds) under 
onap_daily_pod4_master--

today it is under 
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/

You should see a page providing a summary of the CI tests
Click on Full Results to get the list of tests per category
e.g. infrastructure-healthcheck => 2 tests: onap-helm and onap-k8s
then click on the test to get results/logs corresponding to the test

If you want to get the onap-k8s status => click on onap-k8s
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/infrastructure-healthcheck/k8s/index.html
from this page you can have the snapshot of all the versions used for the 
installation.
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/infrastructure-healthcheck/k8s/versions.html

the robot healthcheck results can be found here: 
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/healthcheck/full/full/report.html
at the moment we have 2 tests failing: CLI and NBI (both are addressed through 
a JIRA/gerrit in progress)

Regarding the security tests
for Frankfurt we will focus on
- root_pods
- http_public_endpoints
- jdpw_ports

click on the link to see the status
today
- root pods => 47 pods remaining (wait for new dockers, most of them should 
disappear within the next days...)
- http_public_endpoints: still 4 ports (as discussed yesterday - the 4 issues 
are tracked)
- jdpw_ports: 1 port still open, fix announced for several weeks but no docker 
released and submited in OOM Master yet

For the End to End tests
- basic VM onboarding/distribution/instantiation using VNF API),  SDC 
onboarding/distribution seems OK but we can see an error on instantiation on 
module creation ('requestState': 'FAILED', 'statusMessage': 'STATUS: Received 
error from SDN-C: Error processing request to SDNC. Connection refused 
(Connection refused))
see 
https://gating-results.onap.eu/results/onap_daily_pod4_master-492114891-03-31-2020_09-03/smoke-usecases/basic_vm/xtesting.debug.log
-freeradius_nbi: error occurs earlier (onboarding/distribution still fine) but 
error on service creation at instantiation, could be linked to issue on NBI to 
be troublesshoted (no service instance retrieved from NBI)


/Morgan




_

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.




_

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

Re: [onap-tsc] [lfn-TAC] 回复: [opnfv-tsc] LFN Committer Representative to the Board Election Results

2020-03-26 Thread Eric Debeau via Lists.Onap.Org

Congrats to Cédric, our LFN hero !

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Catherine 
LEFEVRE [catherine.lefe...@intl.att.com]
Envoyé : jeudi 26 mars 2020 14:30
À : lfn-...@lists.lfnetworking.org; Casey Cain; TF TSC; TSC; 
t...@lists.pnda.io; onap-tsc; opnfv-...@lists.opnfv.org; t...@lists.fd.io; 
t...@lists.snas.io; t...@lists.openswitch.net; OLLIVIER Cédric TGI/OLN
Objet : Re: [onap-tsc] [lfn-TAC] 回复: [opnfv-tsc] LFN Committer Representative 
to the Board Election Results

Way to Go Cedric !

We would like to invite you to our next ONAP TSC Call organized on April 2nd, 
2020 to understand how our committers and contributors can interact with you.

Many thanks & regards
Catherine

From: lfn-...@lists.lfnetworking.org  On Behalf 
Of fuqiao
Sent: Tuesday, March 24, 2020 1:58 AM
To: Casey Cain ; TF TSC ; 
TSC ; t...@lists.pnda.io; onap-tsc 
; opnfv-...@lists.opnfv.org; t...@lists.fd.io; TAC 
; t...@lists.snas.io; t...@lists.openswitch.net
Subject: [lfn-TAC] 回复: [opnfv-tsc] LFN Committer Representative to the Board 
Election Results

Congratulations to Cedric

发送自 Windows 10 
版邮件应用

发件人: Casey Cain
发送时间: 2020年3月23日 22:30
收件人: TF TSC; 
TSC; 
t...@lists.pnda.io; 
onap-tsc; 
opnfv-...@lists.opnfv.org; 
t...@lists.fd.io; 
TAC; 
t...@lists.snas.io; 
t...@lists.openswitch.net
主题: [opnfv-tsc] LFN Committer Representative to the Board Election Results

Hello, everyone.

Please join me in congratulating Cédric Ollivier as the new LFN Committer 
Representative to the Board.  Cédric will be representing the committers and 
contributors to LFN projects at the LFN Governing Board.

Thank you to everyone who participated in the Election!

Best,
Casey Cain
Technical Program Manager / Community Architect
Linux Foundation
_
IRC - CaseyLF
WeChat - okaru6
Book a Meeting w/ 
Casey



_

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 (#6083): https://lists.onap.org/g/onap-tsc/message/6083
Mute This Topic: https://lists.onap.org/mt/72563427/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] Integration minutes

2020-03-25 Thread Eric Debeau via Lists.Onap.Org

Hello

I would like to get your attention on results from Integration team:
https://wiki.onap.org/display/DW/Integration+Meeting+Minutes


Some progress on security, but still some issues on some projects...

  1.  Frankfurt

 *
*   still some security issues but we are not far from the end

   *   last daily master

  *   nb public http port < 10 
https://gating-results.onap.eu/results/onap_daily_pod4_master-482446694/security/http_public_endpoints/http_public_endpoints.log

  *   still 1 jdpw port, fix but wait for the docker for more than 
2 weeks: 
https://gating-results.onap.eu/results/onap_daily_pod4_master-482446694/security/jdpw_ports/jdpw_ports.log

  *   nb of rooted pod decreasing (still a xfail list to be added 
for the upstream dockers) but several patch in progress: 
https://gating-results.onap.eu/results/onap_daily_pod4_master-482446694/security/root_pods/root_pods.log

*   There are several hot topics and still blocking errors for the 
M4

   *   
SO:
 not compiling for a while, work on the side effect on unrooting the pod 
(included certificates)

*
   *   SDC new version looks better

  *   even the E2E tests were ok for onboarding (manual tests) now 
problem with the SO

   *   SDNC candidate version committed in OOM but some regression 
detected

   *   Issue on dmaap-dr but I think we start figuring out the 
difference between Nokia lab and azure/Orange lab

You can also find results on the daily master here:
https://gating-results.onap.eu/results/onap_daily_pod4_master-482446694/ with 
100% ok for healthcheck


Best Regards

Eric

_

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 (#6072): https://lists.onap.org/g/onap-tsc/message/6072
Mute This Topic: https://lists.onap.org/mt/72550594/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-vote] [onap-tsc] ONAP Intern Project Review

2020-03-15 Thread Eric Debeau via Lists.Onap.Org

+1 for both

De : onap-tsc-v...@lists.onap.org [onap-tsc-v...@lists.onap.org] de la part de 
Kenny Paul [kp...@linuxfoundation.org]
Envoyé : vendredi 13 mars 2020 20:20
À : onap-tsc-v...@lists.onap.org
Cc : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc-vote] [onap-tsc] ONAP Intern Project Review

(bcc’d to onap-tsc for visibility)

Dear TSC Members,
These two intern projects were approved by the TSC yesterday:

  *   ETSI NFV APIs conformance test for OVP 
https://wiki.lfnetworking.org/x/DwH_AQ
  *   Modeling/etsicatalog  https://wiki.lfnetworking.org/x/CQH_AQ
 *   Approved with the provisions:  change spec from 2.5.1 to 2.7.1 and add 
“Alignment with the CNF task force where applicable”   (I’ve made the required 
changes to the proposal)

The following two projects were reviewed by the TSC during the meeting, edited 
and are now up for approval - Voting ends 5pm pacific, March 17th

  *   ONAP Automation Testing - Portal/SDC 
https://wiki.lfnetworking.org/x/uwAQAg
  *   ONAP Security Requirements – SDC https://wiki.lfnetworking.org/x/uQAQAg

#VOTE Does the TSC approve the “ONAP Automation Testing - Portal/SDC” and the 
“ONAP Security Requirements – SDC” projects to be part of the 2020 Mentorship 
Program?
Please respond with:
   +1  “Both”or +1 by project name
0“Both”or  0 by project name
-1  “Both”or -1  by project name


From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul 
via Lists.Onap.Org
Sent: Tuesday, March 10, 2020 6:02 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ONAP Intern Project Review

Hi TSC Members,

There have been 2 project proposals submitted by ONAP for the 2020 Mentorship 
Program.

In addition I have just been made aware of 2 additional intern projects that 
are desired which will be submitted tonight my time.
The good news is that after conferring with the Mentorship Program Manager, we 
should still be able to get all 4 ONAP projects funded, ---PROVIDED---  that 
the ONAP TSC reviews and approves all of them no later than 5pm pacific, March 
17th.

Of critical importance here is that the scope for all of our intern projects is 
clear and concise.

  *   If projects are too broad or vaguely defined, a perspective intern is 
unlikely to understand what the project is about, which will deter students 
from applying.
  *   If the proposal is overly optimistic about what an intern can effectively 
achieve in a short couple of months, it sets unrealistic expectations for them 
during the application phase.

The net results of either of those scenarios is a “fail” on the part of the TSC 
as it relates to the Mentorship Program that could adversely impact both our 
funding and participation in the program the following year.  We need to make 
sure that y’all are clear about these and in agreement on the expectations.

I am adding a proposal review to this week’s TSC call, but knowing that we 
still have a lot of M4 work we may not got to reviewing them.
PLEASE take a look at the  two proposals listed above (which have been posted 
for a couple of weeks now) and note any concerns as comments on the respective 
page, either in-line or at the bottom.

Thanks!
-kenny



_

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 (#6028): https://lists.onap.org/g/onap-tsc/message/6028
Mute This Topic: https://lists.onap.org/mt/71978642/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] Orange Proxy

2020-03-12 Thread Eric Debeau via Lists.Onap.Org

Hello

Morgan will be the Orange proxy this afternoon

Best Regards

Eric

_

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 (#6019): https://lists.onap.org/g/onap-tsc/message/6019
Mute This Topic: https://lists.onap.org/mt/71901456/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] Please join the ONAP PTL meeting NOW!

2020-03-09 Thread Eric Debeau via Lists.Onap.Org

Hi David

As defined by the TSC, the meeting calendar should be aligned with UTC time to 
avoid confusion

https://lists.onap.org/g/onap-tsc-vote/topic/onap_calendar_standardization/30315212?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,80,30315212

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de David 
McBride [dmcbr...@linuxfoundation.org]
Envoyé : lundi 9 mars 2020 14:11
À : onap-tsc
Objet : [onap-tsc] Please join the ONAP PTL meeting NOW!

Team,

Sorry for the confusion.  The calendar currently lists the PTL meeting starting 
at 7 a.m. Pacific, in approximately 55 minutes.  That is NOT correct.  The 
meeting has started now.  If you are available, please join the call.  We will 
try to get the calendar fixed this week.

David

--
David McBride
Release Manager
Linux Foundation Networking (LFN)
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org
IRC: dmcbride


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.


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

View/Reply Online (#6001): https://lists.onap.org/g/onap-tsc/message/6001
Mute This Topic: https://lists.onap.org/mt/71834092/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] Confirmation of Dong Wang for China Telecom's reserved TSC seat

2020-03-04 Thread Eric Debeau via Lists.Onap.Org

+1

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Kenny Paul 
[kp...@linuxfoundation.org]
Envoyé : mercredi 4 mars 2020 16:08
À : onap-tsc-v...@lists.onap.org
Cc : wdongne...@sina.com
Objet : [onap-tsc] Confirmation of Dong Wang for China Telecom's reserved TSC 
seat

(bcc’d to onap-tsc for visibility – please respond to onap-tsc-vote)

Dear TSC members,
I have received an email from Sun Qiong, the LFN Governing Board for China 
Telecom, stating that Dong Wang is now representing ONAP development for their 
organization.

Does the TSC confirm Dong Wang as the replacement for the reserved seat 
currently held by Zhonghe Huang?
Vote:  +1 approve, 0 abstain, -1 do not approve

Thanks!
-kenny



_

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 (#5989): https://lists.onap.org/g/onap-tsc/message/5989
Mute This Topic: https://lists.onap.org/mt/71728173/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] proxy Orange

2020-02-18 Thread Eric Debeau via Lists.Onap.Org

Hello

Sylvain will represent Orange for the next TSC meeting

Best Regards

Eric

_

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 (#5939): https://lists.onap.org/g/onap-tsc/message/5939
Mute This Topic: https://lists.onap.org/mt/71375191/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] Committer Promotion Request for OOM

2020-01-29 Thread Eric Debeau via Lists.Onap.Org

Hi Mike

+2

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Mike 
Elliott [mike.elli...@amdocs.com]
Envoyé : mercredi 29 janvier 2020 15:34
À : onap-tsc@lists.onap.org
Cc : Lefevre, Catherine; David McBride; Kenny Paul
Objet : [onap-tsc] Committer Promotion Request for OOM

Dear TSC,

I would like to kindly request a Committer Promotion of Krzysztof Opasiak for 
the OOM Team.

All information can be found in the follow link:
https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BOOM%5D+-+Krzysztof+Opasiak

Thanks,
Mike

This email and the information contained herein is proprietary and confidential 
and subject to the Amdocs Email Terms of Service, which you may review at 
https://www.amdocs.com/about/email-terms-of-service


_

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 (#5883): https://lists.onap.org/g/onap-tsc/message/5883
Mute This Topic: https://lists.onap.org/mt/70242499/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] [CI][Integration] security tests integration in ONAP CI chains

2020-01-27 Thread Eric Debeau via Lists.Onap.Org

Congrats to Morgan, Integration and seccom teams.

A very good collaborative work within the community

Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Amy 
Zwarico [amy.zwar...@att.com]
Envoyé : lundi 27 janvier 2020 14:17
À : RICHOMME Morgan TGI/OLN; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Cc : ROUZAUT Fabian TGI/OLN; p.wieczor...@samsung.com
Objet : Re: [onap-tsc] [ONAP] [CI][Integration] security tests integration in 
ONAP CI chains

Great news!

From: morgan.richo...@orange.com 
Sent: Monday, January 27, 2020 4:44 AM
To: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Cc: ROUZAUT Fabian TGI/OLN ; 
p.wieczor...@samsung.com; ZWARICO, AMY 
Subject: [ONAP] [CI][Integration] security tests integration in ONAP CI chains

Hi

I am happy to announce that a new xtesting security docker has been integrated 
end of last week.

This new docker includes 3 new tests dealing with security:
- root_pods: we check that the pods are not run as root
- unlimitted_pods: we check that limits have been set for each pod
- cis_kubernetes: we perform the CIS security suite implemented by aquasecurity 
based on CIS requirements and defined as a Security requirement by Seccom for 
Frankfurt 
(https://jira.onap.org/browse/REQ-243)
root_pods and unlimitted_pods have been provided by F.Rouzaut involved in 
Seccom.
Additional tests (port scan) are already available 
(https://git.onap.org/integration/tree/test/security)
 and will be added very soon in the docker to complete the test suite.

All the security tests have been declared under the security project in the 
test DB: 
http://testresults.opnfv.org/onap/api/v1/projects/security/cases

The good news is that the tests are now integrated and are run in the CI chains
- Daily El Alto
- Daily Master (future Frankfurt): e.g. 
https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/jobs/415571519
- Gating: e.g. 
https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/jobs/415455149
For the moment these chains are running on Orange labs (Daily + gating) + Azure 
(gating). But any lab can add this docker as part of its chains.

The bad new is that there are all failing for the moment.. 
(https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/jobs/415571519/artifacts/download)
- regarding root_pods (135 on 240 pods launched as root) and unlimitted_pods, 
it is up to the project to fix the issues by modifying their docker build chain 
(not using root user) and/or fix limit in their helm charts.
- regarding cis tests, 34 assertions are fail .
It is not directly linked to ONAP but has to be fixed at k8s installation 
whatever the installer (rke, kubespray)

Note port scannings to be added show also some open ports.

We may add a topic for the PTL meeting on these new tests and also a topic to 
remind best practices on Gating

/Morgan



_



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 suscept

Re: [onap-tsc] Kind Reminder - Special TSC Call Now

2020-01-21 Thread Eric Debeau via Lists.Onap.Org

Hello

I can not attend

Morgan will be the Orange Proxy

Best Regards

Eric

De : onap-tsc@lists.onap.org [onap-tsc@lists.onap.org] de la part de Catherine 
LEFEVRE [catherine.lefe...@intl.att.com]
Envoyé : mardi 21 janvier 2020 15:07
À : onap-tsc@lists.onap.org
Objet : [onap-tsc] Kind Reminder - Special TSC Call Now

Dear all,

We are about to start the review of Frankfurt Release (M2/M3).
Please join the call – thank you
When:
Tuesday, 21 January 2020
2:00pm to 3:00pm
(UTC+00:00) UTC
Where:
https://zoom.us/j/661303200
Organizer: Kenny Paul 
kp...@linuxfoundation.org
 5107665945
Description:

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/661303200
Or iPhone one-tap (US Toll): +14086380968,661303200# or +16465588656,661303200#
Or Telephone:
Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)
Meeting ID: 661 303 200
International numbers available: 
https://zoom.us/zoomconference?m=FHWF11_wwIutwd1PAi_vsotA5bQ6kCLh
Best regards
Catherine


Catherine Lefèvre
AVP Software Development & Engineering

AT&T Labs – Network Cloud and SDN Platform Integration
SDN Platform & Systems
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&T
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.



_

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 (#5852): https://lists.onap.org/g/onap-tsc/message/5852
Mute This Topic: https://lists.onap.org/mt/69957071/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 TSC Chair Nominations 2019

2019-12-10 Thread Eric Debeau via Lists.Onap.Org

Congrats Catherine !

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Davide Cherubini
Envoyé : mardi 10 décembre 2019 13:41
À : onap-tsc@lists.onap.org; Catherine LEFEVRE
Objet : Re: [onap-tsc] ONAP TSC Chair Nominations 2019

Congratulations @Catherine LEFEVRE!

Davide

From:  on behalf of Kenny Paul 

Reply to: "onap-tsc@lists.onap.org" 
Date: Friday, 6 December 2019 at 20:44
To: "onap-tsc@lists.onap.org" 
Subject: Re: [onap-tsc] ONAP TSC Chair Nominations 2019

Congratulations to Catherine on being reelected as our ONAP TSC Chair!
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_4356f527d488649e
I will be setting up the Vice-Chair elections shortly.

-kenny

From: onap-tsc@lists.onap.org  On Behalf Of Kenny Paul 
via Lists.Onap.Org
Sent: Monday, December 2, 2019 12:29 PM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] ONAP TSC Chair Nominations 2019

There is only one candidate for the ONAP TSC Chair election: Catherine LeFevre 
(AT&T).

Ballots have been distributed to TSC members.  Voting ends 12:30 pacific 
Friday, Dec. 6

Thanks!
-kenny


_

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 (#5760): https://lists.onap.org/g/onap-tsc/message/5760
Mute This Topic: https://lists.onap.org/mt/61193921/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] Prague co-meeting with CNTT

2019-12-06 Thread Eric Debeau via Lists.Onap.Org

Hello

It would be great also to discuss on-going on OpenLab WindRiver & Orange 
verifications. It seems very close to the current target of compliance required 
by Service Providers and discuss the path from the commercial product 
interoperability testing to CNTT NFVI compliance and how to complete it towards 
VNF onboarding and testing.

+ Cedric, deeply involved in that topic (CNTT/OPNV/ONAP) and Morgan

Best regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Rabi, Abdel, Vodafone Group
Envoyé : jeudi 5 décembre 2019 21:51
À : Lefevre, Catherine; onap-tsc@lists.onap.org; TENNANT, RICK
Cc : Lincoln Lavoie; COTTRELL, MARK; BELTRAN, JONATHAN
Objet : Re: [onap-tsc] Prague co-meeting with CNTT

Sounds good. Thanks Catherine.

Jim/Rick, May I suggest pencilling a 90 minutes session for the joint session 
to cover the topics mentioned?

Topics so far:

  *   CNTT Requirements:  consideration in 2020, especially for 
VVP/VNFSDK/VTP/SDC etc.
  *   Leverage OVP Framework to NFVi Testing
  *   VNF Security

Yours,
Rabi


From: "Lefevre, Catherine" 
Date: Thursday, 5 December 2019 at 20:41
To: "Rabi, Abdel, Vodafone Group" , 
"onap-tsc@lists.onap.org" 
Cc: Lincoln Lavoie , "COTTRELL, MARK" , 
"BELTRAN, JONATHAN" , "TENNANT, RICK" 
Subject: RE: [onap-tsc] Prague co-meeting with CNTT

Thanks Rabi.

I would like to share additional items for consideration for our joint 
CNTT/ONAP session.

These topics were brought today during our ONAP TSC Call:

  *   Leverage OVP Framework to NFVi Testing
  *   VNF Security

Best regards
Catherine

From: Rabi, Abdel, Vodafone Group 
Sent: Thursday, December 5, 2019 9:37 PM
To: Lefevre, Catherine ; onap-tsc@lists.onap.org
Cc: Lincoln Lavoie ; COTTRELL, MARK ; 
BELTRAN, JONATHAN ; TENNANT, RICK 
Subject: Re: [onap-tsc] Prague co-meeting with CNTT

Yes indeed a great and an important topic to discuss jointly. Thanks Catherine.

Yours,
Rabi

From: "Lefevre, Catherine" 
mailto:catherine.lefe...@intl.att.com>>
Date: Thursday, 5 December 2019 at 14:04
To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Cc: Lincoln Lavoie mailto:lylav...@iol.unh.edu>>, "Rabi, 
Abdel, Vodafone Group" 
mailto:abdel.r...@vodafone.com>>, "COTTRELL, MARK" 
mailto:mc2...@att.com>>, "BELTRAN, JONATHAN" 
mailto:jb7...@att.com>>, "TENNANT, RICK" 
mailto:rt0...@att.com>>
Subject: RE: [onap-tsc] Prague co-meeting with CNTT

Good morning Jim,

My apologies for the delayed response.

I believe another area of discussion would be about the VNF Testing (VNF 
Instantiation, etc)
We have received two requirements as part of the Frankfurt release.
It would be great to understand what other requirements which should consider 
in 2020, especially for VVP/VNFSDK/VTP/SDC etc.

Dear TSC Members – I have also added this topic as part of our today’s TSC call 
in case of you have any other suggestion.

Best regards
Catherine

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill via Lists.Onap.Org
Sent: Thursday, November 21, 2019 8:53 PM
To: onap-tsc@lists.onap.org
Cc: Lincoln Lavoie mailto:lylav...@iol.unh.edu>>; Rabi, 
Abdel, Vodafone Group 
mailto:abdel.r...@vodafone.com>>; COTTRELL, MARK 
mailto:mc2...@att.com>>; BELTRAN, JONATHAN 
mailto:jb7...@att.com>>; TENNANT, RICK 
mailto:rt0...@att.com>>
Subject: Re: [onap-tsc] Prague co-meeting with CNTT

Hi Jim,

It would be helpful if you could elaborate on what you saw as the most 
significant intersecting topics  as the term “solution deployment” is quite a 
large scope -  Actually – it would be great if there were suggestions from CNTT 
on the questions that have where ONAP could help – orchestration is clear – but 
beyond that it wasn’t obvious from the last joint meeting nor in the meeting 
planning , then I think the time allocation can be considered.

BR,

Steve



From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Jim 
Baker via Lists.Onap.Org
Sent: Thursday, 21 November 2019 20:29
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Cc: Lincoln Lavoie mailto:lylav...@iol.unh.edu>>; Rabi, 
Abdel, Vodafone Group 
mailto:abdel.r...@vodafone.com>>; COTTRELL, MARK 
mailto:mc2...@att.com>>; BELTRAN, JONATHAN 
mailto:jb7...@att.com>>; TENNANT, RICK 
mailto:rt0...@att.com>>
Subject: [onap-tsc] Prague co-meeting with CNTT

Greetings!
With the Prague f2f meeting looming, I wanted to reach out to the ONAP 
community and plan the CNTT interactions in Prague. We can allocate 2-3 hours 
of time to this collaboration if we can come up with an appropriate agenda. 
While CNTT is chartered to specify the Common NFVI, the CNTT community is 
concerned about the time to solution deployment - which includes VNFs and 
orchestrators. Since ONAP contributes to both VNF validation and orchestration, 
it would make sense to focus our attentions there...

Please res

Re: [onap-tsc] 2019 ONAP TSC Elections - Call for nominations

2019-10-31 Thread Eric Debeau via Lists.Onap.Org

Dear ONAP community,

I would like to nominate myself as a TSC member of the ONAP project 
representing Orange.

I have been involved in SDN/NFV activities for more than 5 years, leading a 
team focusing in open source communities (ONAP, OPNFV, Acumos).
I jumped into ONAP from day1 and always promoted ONAP in various events (SDN 
World Congress 2017, OSN Days Paris 2018, ONS 2018&2019, ONS Europe 2018&2019) 
and interviews (Telecoms TV).

Currently TSC member representing Orange, I am also the Orange coordinator for 
all ONAP activities (cf Orange stats on bitergia: 
https://onap.biterg.io/goto/2154018f4e022a09c433a6a04ca8b27d).
Orange had PTL responsibility on External API and is now leading Integration 
project, security sub-committee and the CNCF coordination. Orange is also very 
active to promote ONAP by offering an OpenLab Platform for the community and 
resources to perform daily tests.
I contributed to various ONAP projects (documentation, integration, 
externalAPI…) and I am strongly involved to improve documentation, end to end  
automation, platform footprint and also CI/CD. I also conducted many PoC with 
many vendors and service providers establishing strong relationship with the 
eco-system.

I am convinced that collaboration within open source project is the best 
approach to drive the industry to deliver de facto standard solutions.
ONAP has established an amazing community and I very proud to be part of it.

ONAP is a major project for service providers in their network automation 
journey and I will focus my energy to make ONAP a success.

Acting as a TSC member, I would focus on key topics (usability, CI/CD, 
security) to ease ONAP usage in production.

My bitergia stats: https://onap.biterg.io/goto/5e8f7d40088f42db52a56b36312b9412

Best Regards

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

View/Reply Online (#5554): https://lists.onap.org/g/onap-tsc/message/5554
Mute This Topic: https://lists.onap.org/mt/36335561/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 El Alto license exceptions - Slides and backup for TSC

2019-10-22 Thread Eric Debeau via Lists.Onap.Org

Hello

I notice that a huge number of files (41k out of 91k) still does not have
license. I believe that it is normal for many files (eg .gitignore, INFO.yaml
files…), but we should correct other files such as js or go files.

We should improve the process and probably include some verification when
patching some code to verify that all files include some licenses.

I also strongly advice to get rid of all “Proprietary / restricted” notices.

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de Jim
Baker
Envoyé : jeudi 17 octobre 2019 23:49
À : onap-tsc
Objet : [onap-tsc] ONAP El Alto license exceptions - Slides and backup for TSC

Steve Winslow provided the below information as followup to today's TSC
meeting. Please review and we will need the TSC decision (aka vote) on whether
to adopt the license waivers as recommended herein. This vote will need to
close before sign-off. I will work with Catherine to request a vote. Please
review and express any concerns before 2019-10-22 EOD.
Thanks, Jim

In anticipation of the upcoming El Alto release, attached please find the
following materials:

* summary slide deck regarding the license scan report and analysis; and
* .zip file containing the backup data and materials used to produce the
slides.
Under the ONAP technical charter [1] ONAP uses the Apache-2.0 license for its
source code and CC-BY-4.0 for documentation. The TSC can approve exceptions to
this policy by a vote of at least 2/3 of the full TSC. As with prior ONAP
releases, this approval vote is taken shortly prior to the release.

The attached slides are intended to assist with this, by documenting the
various licenses that were found in the ONAP codebases and in certain of the
third party dependencies that are included at build- or install-time.

These slides have been shared with the ONAP Legal Subcommittee and were
discussed on a call with subcommittee members on October 17. Unfortunately
there was not a sufficient quorum for the Legal Subcommittee to make a formal
recommendation to the TSC. However, the attached slides reflect the
recommendation of the participants who attended the call.

In a very few instances that are noted in the report, license exceptions were
not recommended, and for those items we have been working with the participants
to address the findings prior to the release.

Otherwise, the participants who attended the Legal Subcommittee call recommend
that the TSC adopt exceptions for the license findings documented in the
report. Slide 34 includes proposed resolution text in case the TSC would like
to use this as a formal resolution.

[1]
https://www.onap.org/wp-content/uploads/sites/20/2018/01/ONAP-Project-a-Series-of-LF-Projects-LLC-Technical-Charter-12-22-2017-FINAL.pdf,
section 7

--
Steve Winslow
Director of Strategic Programs
The Linux Foundation
swins...@linuxfoundation.org

--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007

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

View/Reply Online (#5507): https://lists.onap.org/g/onap-tsc/message/5507
Mute This Topic: https://lists.onap.org/mt/34914574/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] Integration PTL Election Results

2019-10-16 Thread Eric Debeau via Lists.Onap.Org

Congrats Morgan !

Thanks Brian for acting as a TPTL ;-)

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Brian Freeman
Envoyé : mercredi 16 octobre 2019 14:29
À : 'onap-tsc@lists.onap.org'; Jim Baker; 'David McBride'
Cc : RICHOMME Morgan TGI/OLN; LEFEVRE, CATHERINE
Objet : [onap-tsc] Integration PTL Election Results


Dear ONAP TSC,

Please find the ONAP Integration  project's PTL election details below:

Election result:
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_5ab5a1fc695d987b


Morgan Richomme is the new Integration PTL.

Congratulations Morgan !

Brian Freeman
(Temporary Integration PTL)




_

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 (#5479): https://lists.onap.org/g/onap-tsc/message/5479
Mute This Topic: https://lists.onap.org/mt/34559623/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] Frankfurt Release Requirements - Target: Oct 15th, EOD !!!

2019-10-14 Thread Eric Debeau via Lists.Onap.Org

Hello

There is still a lot of requirements. How do we intend to prioritize all the 
requirements ?

In addition, I believe that some requirements are overlapping:

Eg for network slicing, I can find the following requirements and it is 
difficult to commit for such requirements

· Modeling: Enhanced Nested and Shared Service Information Model - 5G / 
E2E Network Slicing modeling

· Modeling: 5G / ORAN & 3GPP Standards Harmonization

· 5G / 5G Service Modeling: Modeling (exploratory) work for creating a 
5G Service

· Vertical Industry Oriented On-demand 5G Slice Service

· Network Slicing

We also have various levels of description:

-  Some requirements are very atomic

-  Some requirements are more global (eg Network Slicing)

I also noticed that some requirements and use-cases are not listed in the right 
table

· End to End Layer 1 Service Management. Modeling the Optical Service 
should be a use -case

· Service Resolver should be a feature and not a use-case

If the requirements only impact one project (and Integration), it should be 
managed at the project level (eg Portal, DCAE/Acumos integration, ...

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Catherine LEFEVRE
Envoyé : vendredi 11 octobre 2019 20:58
À : onap-tsc@lists.onap.org
Objet : [onap-tsc] Frankfurt Release Requirements - Target: Oct 15th, EOD !!!
Importance : Haute

Dear Frankfurt « Owners »,

Thank you for submitting your use cases and your requirements for the Frankfurt 
release.
We are really excited to kick-off our Frankfurt as soon as possible
https://wiki.onap.org/display/DW/Frankfurt+Release+Requirements

The TSC is currently performing some prioritizations based on your inputs and 
EUAG inputs.

It is essential that we collect your additional inputs not later than Oct 15th, 
2019 end of your day
If we do not get them on time then we will postpone your use case/requirements 
to the Guilin Release.


*Use Case / requirements should be reviewed by the Architecture Team 
ASAP

*As you know, we are currently under capacity concerning our Testing 
activities
Therefore a new column has been added "Integration Lead" to identify per use 
case, per requirement.
The Integration Lead will have the following responsibilities:

o   Identify the testers

o   Define the Integration Test Plan for the use case or requirement

o   Develop with his/her testers the automated tests

o   Provide Test Results to the Integration Team



*Provide project's impact for your use case/requirement. Example: SDC 
(C); SO (C) , AAI(TO)

C= Code Change, TO= Test Only


[cid:image003.jpg@01D5829B.CD7BC4C0]


*Provide the list of Dev committed to impacted PTL per use case, per 
requirement a.k.a these columns should be filled up


[cid:image004.jpg@01D5829B.CD7BC4C0]

   Examples

   SDC committed by Ericsson

   SO partially committed by Nokia

   SO will only support REQ-xxx



*Provide T-Shirt Size - is it a multiple release requirement or not?

*Provide Company Engagement

If you look at the TSC minutes (Oct. 10th), you will find the list of missing 
items per use case, per requirement.
https://wiki.onap.org/display/DW/TSC+2019-10-10

If your use case/requirement is not listed in the table then the architecture 
did not approve it or have not yet finalized the review.

Please let us know if you have any question concerning our requests.

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT&T Labs - Network Cloud and SDN Platform Integration
SDN Platform & Systems
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
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



_

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

[onap-tsc] test

2019-10-14 Thread Eric Debeau via Lists.Onap.Org

Test to validate the mailing list.

_

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 (#5470): https://lists.onap.org/g/onap-tsc/message/5470
Mute This Topic: https://lists.onap.org/mt/34532174/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] Orange proxy

2019-07-19 Thread Eric Debeau via Lists.Onap.Org

Hello

Pawel Pawlak will be my proxy for the next 3 weeks.

Best regards

Eric

_

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 (#5267): https://lists.onap.org/g/onap-tsc/message/5267
Mute This Topic: https://lists.onap.org/mt/32525995/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 Meeting Updates - MoM/Action Items (July 11th) and Agenda (July 18th) #tsc

2019-07-16 Thread Eric Debeau via Lists.Onap.Org

Hi Catherine

I believe that we must also discuss some technical problems that we should 
solve as soon as possible

-  Not all repos are mirrored to github

-  Not all projects have Dublin branch => potential impact on 
documentation

-  Better clarification to explain how to synchronize Doc project with 
Project repos for documentation

-  Verified use-cases for El Alto should be fully automated to be 
retested

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Catherine LEFEVRE
Envoyé : mardi 16 juillet 2019 19:33
À : onap-tsc@lists.onap.org
Objet : [onap-tsc] TSC Meeting Updates - MoM/Action Items (July 11th) and 
Agenda (July 18th) #tsc

Dear ONAP Community,

Key Highlights
· Congratulations to our new OOM Committers Sylvain Desbureaux, 
Bartlomiej Grzybowski & Milan Verespej; our new SDC Committers Inna Manzon, 
Tomasz Golabek, Piotr Darosz and Ojas Dubey;
Brinda Santh Muthuramalingam (CCSDK) and Yuanhong Deng (Modeling) !
· TSC approved the The TSC approves a $50K expenditure against the 
budget for lab improvements (Testing & ToolChain)
· TSC approves the Supercommitter proposal Super 
Committers
· LFN Code of Conduct will replace ONAP Code of Conduct (CII Badging)
· Migration to Global-jbb is in progress (21 out 29 projects complete) 
– Certificate will expire on 7/19/2019 - 
https://wiki.onap.org/display/DW/global-jjb+Migration+Tracker
· Vote for Dublin Demo/Tutorials is in progress until July 31st, 2019 – 
https://wiki.onap.org/display/DW/DEMOS+-+R4+Dublin+Demos
· Vote for POC definition will be kicked-off soon

Here are the Urgent Tasks to be completed within the next 2-3 weeks:
· Finalize Dublin Retrospective – Task Lead: Jim Baker
· Finalize El-Alto Content with PTLs – Task Lead: Jim Baker
· Finalize global-jjb migration– Task Lead: Jessica Wagantall
· Finalize Hardware Plan (Lab & Toolchain infrastructure) – Task Leads: 
Xinhui Li (Infrastructure TCC), Yan Yang (OpenLab), Yang Xu (Integration), 
Morgan Richomme (CI/CD)
· Finalize ONAP Internship Program proposal (TSC-117)– Task Lead: Kenny 
Paul

Our latest TSC Meeting Notes have been posted - 
https://wiki.onap.org/display/DW/TSC+2019-07-11

Next TSC Call
The next TSC agenda will be reviewed on Wednesday, July 17th, 2019 - 
https://wiki.onap.org/display/DW/TSC+2019-07-18
The review of El Alto content will be the primary topic.
TSC Calendar: https://lists.onap.org/g/onap-tsc/calendar

2019 TSC Decisions
https://wiki.onap.org/display/DW/2019+TSC+Decisions

TSC Dashboard:
https://jira.onap.org/secure/RapidBoard.jspa?projectKey=TSC&rapidView=163

TSC Chat
https://lists.onap.org/g/onap-tsc/chats

Upcoming Event(s):
· ONAP Joint SubC Meetings Europe (September, Belgium) – Sept 26th & 
Sept 27th
· New DDF dates under approval by TSC - Dec 2nd-5th
Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT&T Labs – Network Cloud & Infrastructure
SDN Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING… It Can Wait

AT&T
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium




_

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 
modifi

Re: [onap-tsc] SSH/HTTPS from Gerrit? #lf

2019-07-15 Thread Eric Debeau via Lists.Onap.Org

Hi Catherine

We detected thanks to Cedric Ollivier that all the repos are not synchronized 
with github. I will send a mail with a list of repos not currently mirrored.

Best Regards

Eric

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

View/Reply Online (#5232): https://lists.onap.org/g/onap-tsc/message/5232
Mute This Topic: https://lists.onap.org/mt/32441215/21656
Mute #lf: https://lists.onap.org/mk?hashtag=lf&subid=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] Dublin Release note

2019-06-27 Thread Eric Debeau via Lists.Onap.Org

Oups.. I sent on the wrong TSC list...

De : onap-rele...@lists.onap.org [mailto:onap-rele...@lists.onap.org] De la
part de Eric Debeau via Lists.Onap.Org
Envoyé : jeudi 27 juin 2019 17:35
À : onap-tsc-v...@lists.onap.org; onap-rele...@lists.onap.org
Cc : onap-rele...@lists.onap.org
Objet : [Onap-release] [onap-tsc] Dublin Release note

Hello

As discussed in the TSC, I proposed the following global release note for
Dublin including the main new features classified according to the
classification defined by Architecture subcommittee:
https://gerrit.onap.org/r/#/c/doc/+/90600/

Output is available here:
https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/doc-dublin-verify-rtd/208/html/release/index.html#dublinrelease-notes

Please provide feedbacks as soon as possible in the gerrit if possible.

Best Regards

Eric

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 (#5165): https://lists.onap.org/g/onap-tsc/message/5165
Mute This Topic: https://lists.onap.org/mt/32232416/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 Dublin - Remaining Activities

2019-06-26 Thread Eric Debeau via Lists.Onap.Org

Hi Huabing

Thanks for the update.

It is ok :
https://docs.onap.org/en/dublin/submodules/msb/apigateway.git/docs/release-notes.html

But  there are still some editorial errors.

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Huabing Zhao
Envoyé : mercredi 26 juin 2019 04:31
À : onap-tsc
Cc : onap-rele...@lists.onap.org
Objet : Re: [onap-tsc] URGENT - ONAP Dublin - Remaining Activities

Hi Catherine,

I have submitted the release note yesterday, but it doesn't show on the onap 
readthedocs site yet. I guess I may need to wait for a few more hours. I would 
appreciate it if someone form docs team could help on that.

Here is the gerrit submit: https://gerrit.onap.org/r/c/msb/apigateway/+/89468

Thanks,
Huabing

On Tue, Jun 25, 2019, 5:02 PM Catherine LEFEVRE 
mailto:catherine.lefe...@intl.att.com>> wrote:
Good morning All,

In order to finalize the ONAP Dublin release, we still need to fix the 
following items :
[cid:image001.jpg@01D52B45.776C1F10]

Can I ask the assignees to fix these documentations issues today (Tuesday June 
25th) so we can ask the TSC to sign-off the release?

Many thanks & regards
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT&T Labs – Network Cloud & Infrastructure
D2 Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair


Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING… It Can Wait

AT&T
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



_

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 (#5151): https://lists.onap.org/g/onap-tsc/message/5151
Mute This Topic: https://lists.onap.org/mt/32201527/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] Is the meeting happening?

2019-06-13 Thread Eric Debeau via Lists.Onap.Org

Not yet...

-Message d'origine-
De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Alexis de Talhouet
Envoyé : jeudi 13 juin 2019 16:06
À : onap-tsc
Objet : [onap-tsc] Is the meeting happening?






_

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 (#5112): https://lists.onap.org/g/onap-tsc/message/5112
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] CERT Project in JIRA

2019-05-29 Thread Eric Debeau via Lists.Onap.Org

Hello

I discovered a new CERT project under the ONAP JIRA: 
https://jira.onap.org/projects/CERT/issues/CERT-17?filter=allopenissues

I do not remember that we validate this new project at TSC level and I can not 
find any decision about it under 
https://wiki.onap.org/display/DW/2019+TSC+Decisions and I do not remember such 
discussion.

Can anyone clarify ?

Best Regards

Eric

_

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 (#5057): https://lists.onap.org/g/onap-tsc/message/5057
Mute This Topic: https://lists.onap.org/mt/31834550/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] CCVPN merge proposal

2019-05-22 Thread Eric Debeau

Hi Catherine

The code is merged

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Catherine LEFEVRE
Envoyé : mercredi 22 mai 2019 14:32
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] CCVPN merge proposal

Dear all,

It is unclear how we have moved forward with this proposition.
Let's review on the TSC call on May 23rd, 2019

Best regards
Catherine

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Sonsino, Ofir
Sent: Friday, May 03, 2019 1:15 PM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] CCVPN merge proposal

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Dear TSC, CCVPN Use Case Owners, impacted PTLs,

Please find below the proposal related to the SDC merge requests i.e. new TOSCA 
parser

*
https://gerrit.onap.org/r/#/c/84769/

*
https://gerrit.onap.org/r/#/c/84786/

*
https://gerrit.onap.org/r/#/c/84788/

As a pre-requisite, these commits should

*Include test coverage i.e. 55% test coverage

*Consider any review comments provided by the SDC reviewers

*Not include any new Security/Vulnerability

*Not include any new license issue

In order to give an opportunity to progress on CCVPN while we are stabilizing 
the code of the Dublin Release,
We would like to suggest:

#0 Identify any impacted component by the new parser and created associated 
JIRA Tickets
#1 Create a branch for all the impacted components identified during step #0 +  
SDC i.e. Dublin Release
#2 Merge the code on the SDC Master
#3 Ask LF to accelerate changes to the CI/CD Toolchain to work on Dublin branch 
and Master at the same time including Jenkins jobs, Sonar and Nexus IQ for all 
the impacted components
#4 CCVPN team will perform any validation, pair-wise testing using the SDC 
containers built from the Master (STAGING -?)
  It will include any regression test including vFW, vDNS reference use 
cases
  Certification of the new parser with  SDNC, DCAE, Policy, ExtAPI, A&AI, 
SO, CLAMP to confirm no interface break
#5 Provide test results by June 16th so PTLs, Integration, TSC can re-assess if 
a cherry-pick on Dublin branch is possible or not
#6 If not possibility to cherry pick due to quality issues or lack of testing 
then consider this requirement as Dublin Maintenance Candidate


Thanks & regards,

Ofir Sonsino
Project Technical Lead, SDC
AT&T Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451417
Mobile: +972 (52) 4377782
E-mail: ofir.sons...@intl.att.com



_

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 (#4998): https://lists.onap.org/g/onap-tsc/message/4998
Mute This Topic: https://lists.onap.org/mt/31482505/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] [linuxfoundation.org #74980] DockerHub Migration

2019-05-03 Thread Eric Debeau

Hello

There is a LFN Infra WG. You can find information on the LFN wiki:
https://wiki.lfnetworking.org/display/LN/Infrastructure+Working+Group+Summary+Report


Best Regards

Eric

-Message d'origine-
De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Kenny Paul
Envoyé : vendredi 3 mai 2019 21:14
À : tina.t...@arm.com
Cc : paul.vad...@enea.com; agrimb...@linuxfoundation.org; 
brian.hedst...@oamtechnologies.com; jwagant...@linuxfoundation.org; 
martin.klo...@tieto.com
Objet : Re: [onap-tsc] [linuxfoundation.org #74980] DockerHub Migration

(removed helpdesk, moved TAC & TSC lists to Bcc)

Hi Tina,

There is not an LFEdge infrastructure or an LFNetworking infrastructure.  The 
infrastructure implementations are independent for each project and not shared. 
The LF- IT team is a common organization with resources allocated based upon 
the individual project budgets. 
The service offerings from LF-IT are a set "menu" of support options that are 
offered to the community. Implementations are not shared across projects. 

The individual TACs for each umbrella review and make recommendations around 
shared common technical interests to the TSCs in that umbrella.  Each project 
can decide whether they want to follow the TAC's recommendations or not.

All discussions around infrastructure, code, process or technology changes must 
be community driven and should start with the individual project TSCs that 
would be impacted by any change.

Hope that helps to clarify.

Thanks!
-Kenny

Kenny Paul,  ONAP Technical Program Manager 
kp...@linuxfoundation.org
510.766.5945 Pacific time zone



-Original Message-
From: Tina Tsou via RT  
Sent: Friday, May 3, 2019 10:09 AM
Cc: paul.vad...@enea.com; agrimb...@linuxfoundation.org; 
brian.hedst...@oamtechnologies.com; jwagant...@linuxfoundation.org; 
kp...@linuxfoundation.org; martin.klo...@tieto.com; t...@lists.lfedge.org; 
t...@lists.lfnetworking.org
Subject: RE: [linuxfoundation.org #74980] DockerHub Migration

Dear @Kenny Paul et al,



Is this LF infrastructure common to LF Edge (Akraino, EdgeX, EVE, EdgeHome, 
etc.) and LFN (ONAP, FD.io, OPNFV, OpenDayLight, etc.)? Or is it specific to 
ONAP only?





Thank you,

Tina Tsou

Enterprise Architect

Arm

tina.t...@arm.com

+1 (408)931-3833



-Original Message-
From: Kenny Paul via RT 
Sent: Friday, May 3, 2019 9:50 AM
To: Tina Tsou 
Cc: paul.vad...@enea.com; agrimb...@linuxfoundation.org; 
brian.hedst...@oamtechnologies.com; jwagant...@linuxfoundation.org; 
martin.klo...@tieto.com; t...@lists.lfedge.org; t...@lists.lfnetworking.org
Subject: [linuxfoundation.org #74980] DockerHub Migration



No further action can be taken by the LF until clear direction and support is 
being driven by the ONAP TSC. At that point the appropriate jira(s) will be 
opened for the projects to perform the necessary tasks.

-Kenny



IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.






_

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 (#4927): https://lists.onap.org/g/onap-tsc/message/4927
Mute This Topic: https://lists.onap.org/mt/31487126/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] Updated ONAP Dublin Architecture

2019-05-03 Thread Eric Debeau

ss squashed-looking…

Biggest change:  moved diagram down in page in that OSS/BSS box is not overly 
emphasized.

Cheers,
Kevin


From: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> 
[mailto:onap-...@lists.onap.org] On Behalf Of Eric Debeau
Sent: Thursday 2 May 2019 10:06
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Subject: Re: [Onap-arc] [onap-tsc] Updated ONAP Dublin Architecture

Hello

A few minor comments ;-)

Use-Case UI is not in the picture. I added it.
I removed all the ONAP (eg ONAP Portal => Portal, …) for Interfaces.
For VID, I proposed Deployer, but it is not the best wording…Anyway, VID means 
nothing for a newbie…We must find a word

I extended DMaaP with Message&Data Routers (DMaaP)
I increased the policy font for ESR
I increased the blocks for the controllers

Best Regards

Eric

De : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
[mailto:onap-tsc@lists.onap.org] De la part de Stephen Terrill
Envoyé : mercredi 1 mai 2019 15:56
À : onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Objet : Re: [onap-tsc] Updated ONAP Dublin Architecture

Hi,

It was pointed out to me that in the re-arraging of the vigure, VID was 
dropped.  As there was no discussion to remove VID, I am treating that as an 
oversight and re-including.

BR,

Steve

From: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill via 
Lists.Onap.Org<https://urldefense.proofpoint.com/v2/url?u=http-3A__Lists.Onap.Org&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8wMhuHHyFmHOjgdacmshCXZ4Rv5xr-X76AahjvgT87dlemLt9pdAZrU2L_fxtwIz&m=Pka_-VBX9V1SNhN8xO80o8GFb73_Skvda6KldXcQisk&s=BedzIsMa_lQOPFc7Maoh89Bpc4SM3zYw93d_aehfMJg&e=>
Sent: Tuesday 30 April 2019 18:28
To: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] Updated ONAP Dublin Architecture

Hi,

Please find attatched the updated Dublin Architecture slides after the 
architecture subcommittee today.

Best Regards,

Steve.

[http://www.ericsson.com]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8wMhuHHyFmHOjgdacmshCXZ4Rv5xr-X76AahjvgT87dlemLt9pdAZrU2L_fxtwIz&m=Pka_-VBX9V1SNhN8xO80o8GFb73_Skvda6KldXcQisk&s=hD7F8oQO7EMKDj13zt33N9m4f6E8N89sHYOIGtJnUQA&e=>

Stephen Terrill
Senior Expert, Automation and Management

TECHNOLOGY SPECIALIST
BDGS RDP Architecture & Technology
Phone: +34913393005
Mobile: +34609168515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>

Ericsson
C/ Via de los Poblados 13. B
28033,Madrid, Madrid
Spain
ericsson.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8wMhuHHyFmHOjgdacmshCXZ4Rv5xr-X76AahjvgT87dlemLt9pdAZrU2L_fxtwIz&m=Pka_-VBX9V1SNhN8xO80o8GFb73_Skvda6KldXcQisk&s=hD7F8oQO7EMKDj13zt33N9m4f6E8N89sHYOIGtJnUQA&e=>

[http://www.ericsson.com/current_campaign]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_current-5Fcampaign&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8wMhuHHyFmHOjgdacmshCXZ4Rv5xr-X76AahjvgT87dlemLt9pdAZrU2L_fxtwIz&m=Pka_-VBX9V1SNhN8xO80o8GFb73_Skvda6KldXcQisk&s=keouAO6b0MppdTU6b2dCdUW5jMjXs6RtRNiAC2ih5wA&e=>

Our commitment to Technology for 
Good<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_thecompany_sustainability-2Dcorporateresponsibility&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8wMhuHHyFmHOjgdacmshCXZ4Rv5xr-X76AahjvgT87dlemLt9pdAZrU2L_fxtwIz&m=Pka_-VBX9V1SNhN8xO80o8GFb73_Skvda6KldXcQisk&s=PiANcFGZHxwC4Qy8spR2n9qXqm-qBOe2-PvHLBoCNEE&e=>
 and Diversity and 
Inclusion<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ericsson.com_thecompany_diversity-2Dinclusion&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8wMhuHHyFmHOjgdacmshCXZ4Rv5xr-X76AahjvgT87dlemLt9pdAZrU2L_fxtwIz&m=Pka_-VBX9V1SNhN8xO80o8GFb73_Skvda6KldXcQisk&s=dSDFXdOTHCvnUJpiH4PYWSNXdxlpvXD8J7WPa6WZmT4&e=>
 contributes to positive change.
Follow us on: 
Facebook<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_ericsson&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8wMhuHHyFmHOjgdacmshCXZ4Rv5xr-X76AahjvgT87dlemLt9pdAZrU2L_fxtwIz&m=Pka_-VBX9V1SNhN8xO80o8GFb73_Skvda6KldXcQisk&s=KEuqIsO0HsoCtWYNgqxAsHwUvyheEZFnZwYpGtRHHe4&e=>
 
LinkedIn<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_ericsson&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=8wMhuHHyFmHOjgdacmshCXZ4Rv5xr-X76AahjvgT87dlemLt9pdAZrU2L_fxtwIz&m=Pka_-VBX9V1SNhN8xO80o8GFb73_Skvda6KldXcQisk&s=ZQbO3bNZfTFDfN_Au_oiJTKTYvbaAvnTk_mhIydW9v

Re: [onap-tsc] ONAP deployment baseline

2019-04-18 Thread Eric Debeau

Hello Jim

« Ease of Deployment » is important and OOM team (with the community) is 
working hard to ease the deployment.

The first OVP Program step is only to validate the VNF package/descriptor. 
There is no need to deploy full ONAP for that.
VNF Vendor just need to run VVP or VNFSDK to check their package/descriptor. It 
is an easy task.
We have developed a portal for VVP and DT also proposed their portal to help 
any vendor to test their VNF using Heat descriptor.

To fully test VNF within ONAP and to check the full onboarding, deployment, 
configuration and closed-loop, they need to deploy a full ONAP.
I believe that all ‘main’ vendors have deployed ONAP in their labs.

I agree that we must help ‘small’ VNF vendors with ONAP community solutions to 
avoid them to deploy a full ONAP or we must provide more adapted ONAP 
deployment to test their VNF managed by ONAP. That is why I advocated from Day0 
to get a small footprint for ONAP. Within OOM project, we defined an override 
file to only deploy a subset of ONAP components to enable on-boarding and 
deployment.

In addition, Orange OpenLab welcomes different VNF vendor that can test their 
VNF.

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de Jim 
Baker
Envoyé : jeudi 18 avril 2019 20:04
À : onap-tsc
Objet : [onap-tsc] ONAP deployment baseline

Greeting ONAP TSC,
One of my areas of contribution within LFN is on the OVP program. As the OVP 
program seeks to attract a marketplace of verified VNFs, the developers of the 
VNFs have the task of completing testing using ONAP. Before they can begin the 
self-testing work required by the OVP, they need to have deployed ONAP and 
OpenStack before 
that...

My question is: Is "ease of install" a system attribute that we have baselined 
AND improve upon?

My desired outcome from raising this question is to accurately state for VNF 
developers an estimation of the process time required currently to deploy ONAP 
AND to understand the interest in the community of investing in "ease of 
deployment"  to improve the end-user experience.

Thanks for sharing your thoughts!

--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007


_

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 (#4872): https://lists.onap.org/g/onap-tsc/message/4872
Mute This Topic: https://lists.onap.org/mt/31234067/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] Proposed Dublin Architecture Slides

2019-04-16 Thread Eric Debeau

Hi Stephen,

I believe that we should explain what POMBA and MUSIC are.

For color code, why Holmes is not as the same color as  DCAE ?

I would propose that we use the same color code in ONAP project for 
documentation and any other material

Blue for Design Time
Green for Run Time

-  Dark Green for controller

-  Light Green for Common Services

Exact color code should be based on the one used for the PPT template.

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Stephen Terrill
Envoyé : mercredi 17 avril 2019 08:31
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi,

Please find an update incorporating updated text on the DCAE definition from 
Vijay.

Best Regards,

Steve

From: onap-tsc@lists.onap.org  On Behalf Of Stephen 
Terrill
Sent: Tuesday 16 April 2019 23:39
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi All,

I missed a comment from Amy, please look at this version instead.

BR,

Steve

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Tuesday 16 April 2019 23:23
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Proposed Dublin Architecture Slides

Hi All,

Thanks for the feedback, the good catches and comments are appreciated.

@Dan, I have added the note
@Ofir, @Seshu, apologies for the omission I have added entries for SO and SDC.

The update is attatched.

Best Regards,

Steve.

From: onap-tsc@lists.onap.org 
mailto:onap-tsc@lists.onap.org>> On Behalf Of Stephen 
Terrill
Sent: Monday 15 April 2019 13:35
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] Proposed Dublin Architecture Slides

Hi,

Please find attatched the proposed Dublin architecture slides.  This is a 
reduced slide set compared to the previous release due to that we are working 
to capture the functional component descriptions and it was thought that the 
effort was better focussed on that.

Best Regards,

Steve

[http://www.ericsson.com]

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

[http://www.ericsson.com/current_campaign]

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


_

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 (#4847): https://lists.onap.org/g/onap-tsc/message/4847
Mute This Topic: https://lists.onap.org/mt/31187054/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] Hackathon announcement - the 17rh

2019-04-16 Thread Eric Debeau

Hi Jim

Just published and I proposed some topics.

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de Jim 
Baker
Envoyé : lundi 15 avril 2019 02:22
À : onap-tsc
Objet : [onap-tsc] Hackathon announcement - the 17rh

Yo ONAP folks,
Please take advantage of this chance to have 1:1  access to the docs team
From Sofia:
Please see updated event page 
here
FYI – still waiting the rest of the doc team to add their planned time slot and 
time zone.

--
Jim Baker
Linux Foundation Networking - Technical Program Manager
mobile: +1 970 227 6007


_

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 (#4837): https://lists.onap.org/g/onap-tsc/message/4837
Mute This Topic: https://lists.onap.org/mt/31135938/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 Policy on ONAP Maintenance Release - Target Review: March 11th, 2019

2019-03-09 Thread Eric Debeau

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 feedback then please provide final feedback about v5
before March 11th EOD.

Many thanks & regards,
Catherine

Catherine Lefèvre
AVP Software Development & Engineering

AT&T Labs - Network Cloud & Infrastructure
D2 Platform & Systems Development
ECOMP/RUBY/SPP-NEAM-Appl. Servers/SIA
ONAP TSC Chair

Phone: +32 81 84 09 08
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT&T
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 (#4719): https://lists.onap.org/g/onap-tsc/message/4719
Mute This Topic: https://lists.onap.org/mt/30318760/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 DDF + OPNFV Plugfest Now Complete

2019-03-08 Thread Eric Debeau

Thanks Brandon and Amar’s team for this good report

Is the report stored on the wiki ?

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Brandon Wick
Envoyé : vendredi 8 mars 2019 09:55
Objet : [onap-tsc] ONAP DDF + OPNFV Plugfest Now Complete

ONAP Community,

Here's the report from the the recent ONAP DDF + OPNFV Plugfest in France. 
Kudos to Amar and his team and everyone who helped make this happen. Please 
share it in your communities and help spread the word about the good work 
happening at our technical events. If you have any feedback on the report, 
please contact me directly. Thanks!

Best,

Brandon Wick
Senior Integrated Marketing Manager
The Linux Foundation
bw...@linuxfoundation.org
+1.917.282.0960



_

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 (#4710): https://lists.onap.org/g/onap-tsc/message/4710
Mute This Topic: https://lists.onap.org/mt/30306948/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] ONAP Container optimization effort

2019-02-28 Thread Eric Debeau

Hello

Following the TSC call, please find some information about the current 
situation on the existing Docker images on the wiki:
https://wiki.onap.org/display/DW/Reduction+effort+between+Casablanca+and+Dublin 
(thanks to Sylvain)

Best Regards

Eric

_

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 (#4686): https://lists.onap.org/g/onap-tsc/message/4686
Mute This Topic: https://lists.onap.org/mt/30165925/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 Meeting Updates - MoM/Action Items (Dec 6th) and Agenda (Dec 13th) #tsc

2018-12-10 Thread Eric Debeau

Hello Catherine, TSC

We made some progress on Pair-Wise Testing, but we still need to consolidate. I 
can present some results during  TSC, Dec 20th.

For  E2E Process Automation (TSC-53), I propose a slot during  TSC Dec 20th and 
to the Architecture sub-committee.
Please also attend the tomorrow session on ONAP usability to illustrate what we 
can expect by true automation on simple examples.

For container optimization, we have a presentation tomorrow during the VF2F 
with Mike and Adolfo.

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Catherine LEFEVRE
Envoyé : lundi 10 décembre 2018 19:58
À : onap-tsc@lists.onap.org
Objet : [onap-tsc] TSC Meeting Updates - MoM/Action Items (Dec 6th) and Agenda 
(Dec 13th) #tsc

Dear ONAP Community,

TSC Vice Chair Self-Nomination is opened till December 12th Noon PST

Our Dec 6th TSC Meeting Notes have been posted.
https://wiki.onap.org/display/DW/TSC+2018-12-06

Here are the Urgent Tasks to be completed within the next 2-3 weeks:

.Finalize the ONAP Release Maintenance Proposal (TSC-34) - Task Lead: 
Stephen Terrill/Alexis de Talhouet  - Target: Dec 13th

.Dublin Pair-Wise Activities Proposal (TSC-42) - Task Lead: Eric Debeau 
- Target: Dec 13th

·Kick-off Casablanca Award Nomination (TSC-74) - Task Lead: Kenny Paul


Several meetings have been organized with the ONAP TSC in order to discuss 
about Dublin TSC prioritization criteria (TSC-45)
As a result of these sessions, the following Task Forces have been created- 
Target: Virtual Event - Dec 10th-12th:
- Security By Design (TSC-52) - Task Lead: Stephen Terrill
- E2E Process Automation (TSC-53) - Task Lead: Eric Debeau
- Documentation (TSC-54) - Task Lead: Myself
- Continuous Integration Approach (TSC-55) - Task Lead: Srini
- Container Optimization (TSC-62) - Task Lead: Eric Debeau

TSC Dashboard:
https://jira.onap.org/secure/RapidBoard.jspa?projectKey=TSC&rapidView=163<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_secure_RapidBoard.jspa-3FprojectKey-3DTSC-26rapidView-3D163&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=vXTu3-NYLaHEwQ7b-gN2nGNSucn5VsrfQF5ZCmnx3po&s=-lZEU9jB5pxxsmL2U357M-2ZM7cYEnAwAg1orJqEmhU&e=>

TSC Decisions
https://wiki.onap.org/display/DW/2018+TSC+Decisions<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_2018-2BTSC-2BDecisions&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=vXTu3-NYLaHEwQ7b-gN2nGNSucn5VsrfQF5ZCmnx3po&s=TfSLgiXSrgrrPMVX2O1kdG_HE4MfZN3NcU1G6CKLcu8&e=>

Next TSC Call(s)
No TSC Call on December 27th, 2018
The next TSC agenda will be reviewed on Wednesday (Dec 12th).

Here is the wiki link:
https://wiki.onap.org/display/DW/TSC+2018-12-13+Meeting+Agenda

Upcoming Events

* Dec 10th-Dec 12th (Virtual):  Virtual Dublin Developer Forum: 
https://wiki.onap.org/pages/viewpage.action?pageId=45293323<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D45293323&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=vXTu3-NYLaHEwQ7b-gN2nGNSucn5VsrfQF5ZCmnx3po&s=oTb9vRH37Yr9kdUAy0aytA4HF2wUVlsz35jl0hBBBnE&e=>

* Jan 8-11 - Dublin Release F2F Developer Design Forum (France): 
https://wiki.lfnetworking.org/pages/viewpage.action?pageId=8257579<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.lfnetworking.org_pages_viewpage.action-3FpageId-3D8257579&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=vXTu3-NYLaHEwQ7b-gN2nGNSucn5VsrfQF5ZCmnx3po&s=1EiQmPmb4rzU56vSfu1EWxMyGiT_dW6JeQLMcIFKesc&e=>
 Feel free to request your VISA: 
http://events.linuxfoundation.org/visa-request<https://urldefense.proofpoint.com/v2/url?u=http-3A__events.linuxfoundation.org_visa-2Drequest&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=vXTu3-NYLaHEwQ7b-gN2nGNSucn5VsrfQF5ZCmnx3po&s=j5AMx0X3ZGgE3BF74gfoaf8XPVpEhYdVsAV4nB9k7B0&e=>
 Submit your proposal: 
https://wiki.lfnetworking.org/display/LN/OPNFV-ONAP+January+2019+Session+Proposals<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.lfnetworking.org_display_LN_OPNFV-2DONAP-2BJanuary-2B2019-2BSession-2BProposals&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=vXTu3-NYLaHEwQ7b-gN2nGNSucn5VsrfQF5ZCmnx3po&s=s1QLf2mwtuokO_v0lTEpr9v6-fxWWk--qpHyp7swkoQ&e=>

TSC Chat
https://lists.onap.org/g/onap-tsc/chats<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_g_onap-2Dtsc_chats&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU&m=vXTu3-NYLaHEwQ7b-gN2nGNSucn5VsrfQF5ZCmnx3po&s=HGH0js5kdNpmqVJPyb4bvgdTb2CmXc4D71nSE5ujAEE&

Re: [onap-tsc][integration] The ONAP Integration Project PTL Election Result

2018-12-10 Thread Eric Debeau

Congrats Yang

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Adolfo Perez-Duran
Envoyé : lundi 10 décembre 2018 19:34
À : onap-tsc@lists.onap.org
Cc : onap-disc...@lists.onap.org
Objet : Re: [onap-tsc][integration] The ONAP Integration Project PTL Election 
Result

Congratulations Yang Xu!

Look forward to collaborating with you.

Adolfo

On Mon, Dec 10, 2018 at 11:16 AM Yang Xu 
mailto:yang@huawei.com>> wrote:
Thanks Helen and the whole Integration team for the incredible work, and the 
trust on me.

Regards,
-Yang
From: onap-tsc@lists.onap.org 
[mailto:onap-tsc@lists.onap.org] On Behalf Of 
Helen Chen
Sent: Monday, December 10, 2018 12:01 AM
To: onap-tsc mailto:onap-tsc@lists.onap.org>>; 
onap-discuss mailto:onap-disc...@lists.onap.org>>
Subject: [onap-tsc][integration] The ONAP Integration Project PTL Election 
Result

Dear ONAP TSC and the Integration team,

Below is the Integration Project PTL election result:
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_45faf0d0cf9a320a

Congratulations Yang Xu !!

Regards,
Helen Chen

Principal Architect, Open Orchestration
Huawei US R&D Center
Futurewei Technologies, Inc.

2330 Central Expressway, C2-16
Santa Clara, CA 95050
Tel: (408) 330-4696
Cell: (510) 825-7348


_

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 (#4310): https://lists.onap.org/g/onap-tsc/message/4310
Mute This Topic: https://lists.onap.org/mt/28706326/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] VF2F Bridge Issues

2018-12-10 Thread Eric Debeau

Thanks Kenny

Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Kenny Paul
Envoyé : lundi 10 décembre 2018 17:28
À : onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] VF2F Bridge Issues

Just received confirmation that the ONAP1 Bridge has been set to 500 attendees.
Should not have any problems tomorrow.

Thanks!
-kenny


From:  on behalf of Kenny Paul 

Reply-To: 
Date: Monday, December 10, 2018 at 6:09 AM
To: 
Subject: Re: [onap-tsc] VF2F Bridge Issues

Yes, the meeting is being recorded.

From:  on behalf of Kenny Paul 

Reply-To: 
Date: Monday, December 10, 2018 at 5:54 AM
To: "onap-tsc@lists.onap.org Calendar" 
Subject: [onap-tsc] VF2F Bridge Issues

For some reason the ONAP1 Bridge was renewed w/ only a 100 participant limit 
rather than the 500 participant upgrade. I will work with IT to get that 
corrected for tomorrow.


Best Regards,
-kenny

Kenny Paul, Technical Program Manager, The Linux Foundation
kp...@linuxfoundation.org, 510.766.5945
San Francisco Bay Area, Pacific Time Zone




_

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 (#4304): https://lists.onap.org/g/onap-tsc/message/4304
Mute This Topic: https://lists.onap.org/mt/28708993/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-discuss] Location for usecase specific files modules/scripts/artifacts

2018-11-29 Thread Eric Debeau

Hello Srini

That is a good point you raised

I think that we should clarify where to put the various use-case artifacts in 
ONAP.

We have some artifacts in demo (eg Heat &TOSCA  for VNF to be used in various 
use-cases: vFW, vCPE and some specific code for VNF)
We have some specific DG in SNDC project (eg CC-VPN)
A place to put global use-case information in doc project (only vFW)
…

And a lot, lot, lot  of material in the wiki

Yet another topic to solve at TSC level.

Best Regards

Eric


De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Srini
Envoyé : jeudi 29 novembre 2018 20:53
À : PLATANIA, MARCO (MARCO); onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Objet : Re: [onap-tsc] [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Thanks Marco.

Srini

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 11:46 AM
To: Addepalli, Srinivasa R ; 
onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Same standard procedure as every other repository. It’s managed by the 
Integration Team, so committers are myself, Gary Wu, Helen, Yang Xu and others 
I suppose.

Marco

From: "Addepalli, Srinivasa R" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 1:24 PM
To: "PLATANIA, MARCO (MARCO)" 
mailto:plata...@research.att.com>>, 
"onap-disc...@lists.onap.org" 
mailto:onap-disc...@lists.onap.org>>, 
"onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>
Subject: RE: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Thanks Marco.

Yes, intention is not to add any ONAP component related code/patches in usecase 
directory.

Demo repository:  Does it go through same merging process? If so, who are 
committers and reviewers for this?

Thanks
Srini


From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, November 29, 2018 10:10 AM
To: onap-disc...@lists.onap.org; Addepalli, 
Srinivasa R 
mailto:srinivasa.r.addepa...@intel.com>>; 
onap-tsc@lists.onap.org
Subject: Re: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi Srini,

A few use cases use the Demo repository to store Heat templates, scripts, and 
VNF-specific code, as you noticed. The same repo could be used by your use case 
too. Note that Demo doesn’t host any ONAP component code. For that, other repos 
are used.

Not sure what CCVPN and VoLTE do.

Marco

From: mailto:onap-disc...@lists.onap.org>> on 
behalf of Srini 
mailto:srinivasa.r.addepa...@intel.com>>
Reply-To: "onap-disc...@lists.onap.org" 
mailto:onap-disc...@lists.onap.org>>, 
"srinivasa.r.addepa...@intel.com" 
mailto:srinivasa.r.addepa...@intel.com>>
Date: Thursday, November 29, 2018 at 12:57 PM
To: "onap-tsc@lists.onap.org" 
mailto:onap-tsc@lists.onap.org>>, 
"onap-disc...@lists.onap.org" 
mailto:onap-disc...@lists.onap.org>>
Subject: [onap-discuss] Location for usecase specific files 
modules/scripts/artifacts

Hi,


For “K8S based Cloud-region support” work, we intend to prove  with three use 
cases


-Deploying EdgeXFoundry

-Deploying vFirewall using K8S

-Deploying Service assurance framework and apps.

These requires creation of artifacts, some scripts and even possibly some 
usecase specific modules.
Where do usecase specific files put in ONAP?
Main intention is that anybody in community can run these usecases and hence 
want to put all usecase specific files in ONAP for them to easily access them.

I see demo repository for vCPE, vFW and vDNS.
Is this the right place for all other usecases?
BTW, I don’t see any files related to CCVPN, VoLTE usecase. Are they placed 
elsewhere?

Any guidance from the TSC/community is appreciated.

Thanks
Srini






_

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

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

2018-11-27 Thread Eric Debeau

Thanks Ofir

It could be cool to upload the associated Swagger in th OfferedAPI section ;-)

Best Regards

Eric

De : Sonsino, Ofir [mailto:ofir.sons...@intl.att.com]
Envoyé : mardi 27 novembre 2018 09:38
À : onap-disc...@lists.onap.org; PLATANIA, MARCO; DEBEAU Eric TGI/OLN; 
onap-tsc@lists.onap.org
Cc : Roger Maitland
Objet : RE: [onap-discuss] [onap-tsc] Scale out use case documentation

Hi Eric,

Please note this API is also documented in VID readthedocs:
https://onap.readthedocs.io/en/latest/submodules/vid.git/docs/administration.html

Thanks,
Ofir

From: onap-disc...@lists.onap.org [mailto:onap-disc...@lists.onap.org] On 
Behalf Of PLATANIA, MARCO
Sent: Tuesday, November 27, 2018 3:34 AM
To: onap-disc...@lists.onap.org; eric.deb...@orange.com; onap-tsc@lists.onap.org
Cc: Roger Maitland 
Subject: Re: [onap-discuss] [onap-tsc] Scale out use case documentation

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hi Eric,

Thanks for pointing that out. I just updated the wiki page with the call to the 
VID API that enables scale out for a given VNF.

Marco

From: mailto:onap-disc...@lists.onap.org>> on 
behalf of Eric Debeau mailto:eric.deb...@orange.com>>
Reply-To: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, 
"eric.deb...@orange.com<mailto:eric.deb...@orange.com>" 
mailto:eric.deb...@orange.com>>
Date: Monday, November 26, 2018 at 4:53 PM
To: "onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Cc: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 
mailto:onap-disc...@lists.onap.org>>, Roger 
Maitland mailto:roger.maitl...@amdocs.com>>
Subject: Re: [onap-discuss] [onap-tsc] Scale out use case documentation

https://wiki.onap.org/display/DW/2018/10/10/Casablanca+Highlights<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_2018_10_10_Casablanca-2BHighlights&d=DwQFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=R_GD3len05VHHFEJvp5VDqk78RpfvnBkMkZCDZ9-lmM&s=W71bMdZSNYF26lxYSXEGi-Y7zTfO3E57chH-Z-MMeSE&e=>


_

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 (#4156): https://lists.onap.org/g/onap-tsc/message/4156
Mute This Topic: https://lists.onap.org/mt/28359037/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

2018-11-26 Thread Eric Debeau

Thanks Marco

To be updated in the Casablanca Highlights:
https://wiki.onap.org/display/DW/2018/10/10/Casablanca+Highlights


Can you just add in the wiki  the request used for the VID:
vid/change-management/vnf_workflow_relation (I am afraid such API is not yet 
defined in the readthedocs)


Best Regards

Eric

De : onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] De la part de 
Alexis de Talhouet
Envoyé : lundi 26 novembre 2018 22:01
À : onap-tsc@lists.onap.org
Cc : onap-disc...@lists.onap.org
Objet : Re: [onap-tsc] Scale out use case documentation

Thanks for sharing Marco! Very insightful.

Alexis


On Nov 26, 2018, at 3:31 PM, Marco Platania 
mailto:plata...@research.att.com>> 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




_

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 (#4152): https://lists.onap.org/g/onap-tsc/message/4152
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]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] #architecture #modeling summary from Montreal

2018-11-19 Thread Eric Debeau

Hi Stephen, Hui and Andy

Can you share the presentation you did during the last TSC meeting about the 
Montreal event ?

Thanks

Best Regards

Eric

_

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 (#4131): https://lists.onap.org/g/onap-tsc/message/4131
Mute This Topic: https://lists.onap.org/mt/28241703/21656
Mute #architecture: https://lists.onap.org/mk?hashtag=architecture&subid=2743226
Mute #modeling: https://lists.onap.org/mk?hashtag=modeling&subid=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]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] ONAP implementations by service providers

2018-11-07 Thread Eric Debeau

Hello

I noticed that we created a page to list ONAP implementations by Service 
Providers:
https://wiki.onap.org/display/DW/ONAP+Implementations+by+SP

It is still empty;-( I think that we should fill this table. That could help 
also to prioritize the various ONAP requirements for Dublin.

Best Regards

Eric

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

View/Reply Online (#4069): https://lists.onap.org/g/onap-tsc/message/4069
Mute This Topic: https://lists.onap.org/mt/28029691/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] Dublin Prioritization Criteria - Session 1 (APAC/EMEA)

2018-11-07 Thread Eric Debeau

Hello Catherine & Alla

When is scheduled this meeting ?

Best Regards

Eric

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

View/Reply Online (#4067): https://lists.onap.org/g/onap-tsc/message/4067
Mute This Topic: https://lists.onap.org/mt/28021529/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: [E] Re: [onap-tsc] SP priorities for Dublin

2018-10-24 Thread Eric Debeau

Hi Viswanath

Yes, you can ;-)
You may define different priorities.

BR

Eric

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

View/Reply Online (#3975): https://lists.onap.org/g/onap-tsc/message/3975
Mute This Topic: https://lists.onap.org/mt/27622425/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] SP priorities for Dublin

2018-10-24 Thread Eric Debeau

Hi Service Provider TSC members

Please fill the table to provide your requirements: 
https://wiki.onap.org/display/DW/SP+priorities+for+Dublin ( 
https://wiki.onap.org/display/DW/SP+priorities+for+Dublin )

Best Regards

Eric

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

View/Reply Online (#3969): https://lists.onap.org/g/onap-tsc/message/3969
Mute This Topic: https://lists.onap.org/mt/27486689/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-discuss] [doc] DOC Project PTL Election - Self-Nomination Phase Open

2018-09-11 Thread Eric Debeau

Hello

As a DOC committer, I fully support the Sofia candidature. She has very good 
experience in open source communities and demonstrated her leadership in OPNFV 
as DOC PTL.

Best Regards

Eric

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

View/Reply Online (#3690): https://lists.onap.org/g/ONAP-TSC/message/3690
Mute This Topic: https://lists.onap.org/mt/25505447/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] Use case documentation in readthedocs #documentation #usecase #end2end

2018-08-10 Thread Eric Debeau

Hello

As discussed in the TSC yesterday,

The current use-case definition in readthedocs is here:

* Global use-case definition under the Architecture section: 
https://onap.readthedocs.io/en/beijing/guides/onap-developer/architecture/onap-architecture.html#onap-use-cases

* Use-cases description and call flows: 
https://onap.readthedocs.io/en/beijing/guides/onap-developer/use-cases/index.html

The repo to describe the use-cases is here:
https://gerrit.onap.org/r/gitweb?p=doc.git;a=tree;f=docs/use-cases;hb=HEAD

Please feel free to contact Rich, the Documentation PTL.

Please feel free to provide feedbacks on the best way to provide end to end 
documentation to help anyone to better understand ONAP. I will provide some 
guidelines in the next TSC to improve such documentation.

PS: I am using some tags ;-)

Best Regards

Eric

_

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 (#3605): https://lists.onap.org/g/ONAP-TSC/message/3605
Mute This Topic: https://lists.onap.org/mt/24249116/21656
Mute #end2end: https://lists.onap.org/mk?hashtag=end2end&subid=2743226
Mute #documentation: 
https://lists.onap.org/mk?hashtag=documentation&subid=2743226
Mute #usecase: https://lists.onap.org/mk?hashtag=usecase&subid=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] REMINDER: TSC Election Self-Nominations close 5pm Pacific, Tuesday, Aug. 7.

2018-08-08 Thread Eric Debeau

Hello Kenny

Can we get an update on the number of validated candidates ?

Best regards

Eric

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

View/Reply Online (#3594): https://lists.onap.org/g/ONAP-TSC/message/3594
Mute This Topic: https://lists.onap.org/mt/24215962/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] F2F Meeting(s) @ ONS-EU

2018-08-08 Thread Eric Debeau

Hello

I can check if we can get some rooms in Sophia-Antipolis.

Best regards

Eric

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

View/Reply Online (#3593): https://lists.onap.org/g/ONAP-TSC/message/3593
Mute This Topic: https://lists.onap.org/mt/24222619/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] CALL FOR NOMINATIONS: ONAP TSC ELECTION

2018-07-28 Thread Eric Debeau

Dear ONAP community members,

I would like to nominate myself as a TSC member of the ONAP project 
representing Orange (seat as Platinum Service Provider).

I have been involved in SDN/NFV activities for 5 years, leading a team focusing 
in open source communities (ONAP, OPNFV, Acumos). I contributed in various ONAP 
projects (Documentation, Integration, ExternalAPI…) and sub-committees 
(architecture, use-case…) and I am the current Orange TSC member. I also 
promoted ONAP in various events (OSN Days, ONS Summit, SDN World Congress…).

ONAP is a key project for service providers and I will focus my energy to make 
ONAP a success. Acting as a TSC member, I would like to accelerate the ONAP 
deployment in production focusing on the key requirements and to bring more 
technical topics within the TSC.

My ONAP stats: https://onap.biterg.io/goto/6a4383ca05cf22196ac3c13df6382a86 ( 
https://onap.biterg.io/goto/6a4383ca05cf22196ac3c13df6382a86 )

My short bio:

Eric Debeau has a solid 20 years experience in the telecommunications area with 
a particular focus to adopt IT techniques in networks and OSS domains. Through 
his broad experience as network architect (SDH, VoIP, IMS), he is recognized as 
an Orange expert in future network domain. He is currently leading a team 
working on the core network evolution leveraging IT techniques mainly covering 
NFV and network data analytics. His team is very open-source focused with 
strong involvement in OPNFV and now in ONAP. Eric Debeau is very involved in 
various open-source communities (ONAP TSC member) and he is responsible to 
coordinate the Orange contributions to ONAP project. He contributed in various 
open-source community summits, published various technical papers and holds 
several patents.

My head-shot:

Best Regards

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

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

[onap-tsc] [onap-discuss] [extAPI] External API PTL Election - Results

2018-07-18 Thread Eric Debeau

Hello

Congrats to Matthieu !

Many thanks for Andy and his strong involvement as PTL for the first 2 ONAP 
releases and to manage the handover with Matthieu.

Best Regards

Eric

_

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 (#3422): https://lists.onap.org/g/ONAP-TSC/message/3422
Mute This Topic: https://lists.onap.org/mt/23672084/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] [onap-discuss] [extAPI] External API PTL Election - Nominations open

2018-07-09 Thread Eric Debeau

Hello

Orange team submit and support Matthieu Geerebaert application as ONAP/ExtAPI 
PTL. Matthieu will be OoO till august 6th that why I fill this application on 
his behalf.

Matthieu is a talented coder for a long time in Orange and he leaded Orange 
development team for NBI component. He is already an ONAP committer and he 
shows his strong commitment during Beijing development to solve all project 
issues and roadblock. From his journey within Orange, Matthieu has a long 
experience in API development and in project development.

Thanks


Eric on behalf of Matthieu

_

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 (#3327): https://lists.onap.org/g/ONAP-TSC/message/3327
Mute This Topic: https://lists.onap.org/mt/23199910/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] Modeling Options Agenda Item Discussed Today at TSC Meeting

2018-07-06 Thread Eric Debeau

Hello

Where can we get the slides ?

I want to remind that we are in an open-source project to produce some code to 
answer service provider requirements.

I also want to raise some operational concerns about  the question: "Do we 
agree that we don't want the vendors to have to create ONAP-specific 
descriptors that conflict with standards? "
What are the standards ? Heat Orchestration Template is the de facto-standard 
for VNF to be deployed on OpenStack, Helm Chart is the de facto standard to 
deploy VNF to be deployed on K8S.
Using various VNF descriptors will require to get the associated tooling to:
- test VNF deployment on infra (eg it is easy to test VNF deployment on 
OpenStack using Heat template)
- validate VNF descriptor (VNF SDK & VVP tool must be adapted to test these 
various VNF descriptor flavors)

Best Regards

Eric

_

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 (#3313): https://lists.onap.org/g/ONAP-TSC/message/3313
Mute This Topic: https://lists.onap.org/mt/23175452/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-tsc] TSC Attendance requirements - discussion

2018-06-28 Thread Eric Debeau

Hello

I agree with the proposal

If we want to include the email vote, I would propose to replace" two (2) 
consecutive meetings" by  2 consecutive events (TSC meetings and email vote)."

We can get an observation period for the next 3 months to detect is there is a 
problem for the quorum and solve it if necessary. Do  not solve problems that 
does not (yet) exist.

However, I also believe that the motivation is not only about voting. It is 
also to be involved technically in the project.
I think that we should force all TSC member to get a minimum technical 
background about ONAP (ie minimal is to follow the ONAP course...).

Best Regards

Eric

_

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 (#3231): https://lists.onap.org/g/ONAP-TSC/message/3231
Mute This Topic: https://lists.onap.org/mt/22883027/21656
Group Owner: onap-tsc+ow...@lists.onap.org
Unsubscribe: https://lists.onap.org/g/ONAP-TSC/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

93 matches

Mail list logo