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

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



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

__

Re: [onap-tsc] TSC Prioritization - Latest Updates

[hlfight_]

Dear Catherine,




Thank you for info update. :)




About VNF validation, we've discussed with PTL, the conclusion is that our 
requirements will only do enhancement in VNFSDK.




Best Regards,

Lei






Normal   07.8 磅   0   2  false   false   false  
EN-US   ZH-CN   X-NONE  
   MicrosoftInternetExplorer4   





  

---  

黄蕾  

人工智能和智慧运营研发中心  

中国移动通信有限公司研究院  

中国北京市西城区宣武门西大街32号（100053）  

   

Huang Lei  

Center of AI and Intelligent Operation R&D  

China Mobile Research Institute  

No.32 Xuanwumen west street, Xicheng District, Beijing 100053, China  

   

Mobile: +86 18800156155  

Email: huanglei...@chinamobile.com  

-  

   

 


 



发件人: Catherine LEFEVRE

时间: 2020/07/01(星期三)20:14

收件人: 黄蕾;

抄送人: onap-tsc;onap-release;morgan.richomme;杨艳;Kanagaraj Manickam;

主题: Re: [onap-tsc] TSC Prioritization - Latest Updates 

 

Thank you Lei for the updates. 

You might want to discuss with the VVP and VFSDK who are already performing 
some VNF validation. 

  

In the meanwhile I will finalize the review with the ONAP TSC based on your 
constructive discussions with Morgan. 

Thank you again ! 

  

Best regards 

Catherine 

 

 

From: 黄蕾  
 Sent: Wednesday, July 1, 2020 1:14 PM
 To: Lefevre, Catherine 
 Cc: onap-tsc ; onap-release 
; morgan.richomme ; 杨艳 
; Kanagaraj Manickam 
 Subject: Re: [onap-tsc] TSC Prioritization - Latest Updates   

  

 

 

Dear Catherine,  

 

   

 

 

After today's detailed discussion with Morgan, we both agree on pushing forward 
these four testing automatic requirements, the testing objects, target and 
method  are different from each other.

 

   

 

Thanks again to Morgan for preparing today's call for us discuss fully about 
our two project. :)

 

   

 

Best Regards,  

 

Lei   

 



 

   

 

 

发件人: Catherine LEFEVRE  

 

时间: 2020/07/01(星期三)19:10  

 

收件人: onap-tsc;onap-release;  

 

主题: [onap-tsc] TSC Prioritization - Latest Updates

Good morning/afternoon Requirement Owners, PTLs, 

  

I want to inform you that the following requirements have been reviewed and 
prioritized by the ONAP TSC as follows  REQ-339 - Container Network Function 
Test Platform (CNTP): OVP 2.0 support and Enable Network Service testing (RANK 
#3 PTL GO/NO GO)REQ-385 - IPv4/IPv6 dual stack support in ONAP (RANK #3 PTL 
GO/NO GO) 

  

We are waiting for the final discussions between Morgan and Lei regarding 
REQ-335 to REQ-338 -  https://lists.onap.org/g/onap-tsc/message/6613 

  

TSC Vote in progress for the following requirements:  REQ-329: Guilin-R7 - 
Support for Intent-based NetworkREQ-345: 5G OOF SON use case requirements for 
Guilin releaseREQ-386: Apply common Swagger style and documentation generation 
tools to create robust ONAP API documentation 

  

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. 

  

 

  


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

View/Reply Online (#6650): https://lists.onap.org/g/onap-tsc/message/6650
Mute This Topic: https://lists.onap.org/mt/75232350/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

[David McBride]

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  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 [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
>  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 [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.
>>
>>
>
> --
> *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

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

[TIMONEY, DAN]

Eric,

Thanks for that feedback!

Let me discuss with your concerns with the CDS team and come back with a plan 
to make sure we’re being as transparent as possible.

Thanks!

Dan

From:  on behalf of "Eric Debeau via lists.onap.org" 

Reply-To: "onap-tsc@lists.onap.org" 
Date: Wednesday, July 1, 2020 at 4:40 PM
To: "onap-tsc@lists.onap.org" , 
"onap-...@lists.onap.org" , 
"dmcbr...@linuxfoundation.org" 
Cc: Kenny Paul 
Subject: Re: [onap-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 
9 #guilin

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
 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 
[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 t

Re: [onap-tsc] [onap-discuss] Jenkins, Nexus, Nexus3 downtime maintenance - July 1st 12:00 - 14:00 PT

[Jessica Wagantall]

Hi Team..

we should be back and stable now..

Thanks so much!
Jess

On Wed, Jul 1, 2020 at 1:57 PM Jessica Wagantall via lists.onap.org
 wrote:

> Small update...
>
> Our team is still working through this migration.
> We need to extend 30 more minutes to complete.
>
> Thanks so much for your patience
> Jess
>
> On Wed, Jul 1, 2020 at 10:16 AM Jessica Wagantall via lists.onap.org
>  wrote:
>
>> Dear team.
>>
>>
>> This is a small reminder of this downtime happening in aprox 2 hours.
>> Please be advised that *Jenkins, Nexus and Nexus3 will be unavailable
>> for 2 hrs. *
>>
>> Thanks!
>> Jess
>>
>> On Tue, Jun 30, 2020 at 1:55 PM Jessica Wagantall via lists.onap.org
>>  wrote:
>>
>>> Dear ONAP team,
>>>
>>> Jenkins, Nexus and Nexus3 will be under maintenance
>>> July 1st 12:00 - 14:00 PT (14:00 - 16:00 Central) for
>>> auth0 support.
>>>
>>> These services will not be accessible during this time and Jenkins jobs
>>> will be paused.
>>>
>>> Please let us know for any issues and we can always plan for a
>>> better timing.
>>>
>>> Thanks so much!
>>> Jess
>>>
>>> 
>
>

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

View/Reply Online (#6647): https://lists.onap.org/g/onap-tsc/message/6647
Mute This Topic: https://lists.onap.org/mt/75240581/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] Jenkins, Nexus, Nexus3 downtime maintenance - July 1st 12:00 - 14:00 PT

[Jessica Wagantall]

Small update...

Our team is still working through this migration.
We need to extend 30 more minutes to complete.

Thanks so much for your patience
Jess

On Wed, Jul 1, 2020 at 10:16 AM Jessica Wagantall via lists.onap.org
 wrote:

> Dear team.
>
>
> This is a small reminder of this downtime happening in aprox 2 hours.
> Please be advised that *Jenkins, Nexus and Nexus3 will be unavailable for
> 2 hrs. *
>
> Thanks!
> Jess
>
> On Tue, Jun 30, 2020 at 1:55 PM Jessica Wagantall via lists.onap.org
>  wrote:
>
>> Dear ONAP team,
>>
>> Jenkins, Nexus and Nexus3 will be under maintenance
>> July 1st 12:00 - 14:00 PT (14:00 - 16:00 Central) for
>> auth0 support.
>>
>> These services will not be accessible during this time and Jenkins jobs
>> will be paused.
>>
>> Please let us know for any issues and we can always plan for a
>> better timing.
>>
>> Thanks so much!
>> Jess
>>
>> 
>
>

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

View/Reply Online (#6646): https://lists.onap.org/g/onap-tsc/message/6646
Mute This Topic: https://lists.onap.org/mt/75240581/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-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

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


--
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,

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

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



--
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 (#6644): https://lists.onap.org/g

Re: [onap-tsc] Guilin M1 release management Jira Issues published #guilin

[David McBride]

Team,

I just realized that I inadvertently left the project planning template off
of the list of tasks for M1.  This has now been corrected.  My apologies
for the oversight.

David

On Fri, Jun 19, 2020 at 6:41 PM David McBride 
wrote:

> Team,
>
> The Guilin M1 release management Jira issues have been published. A couple
> of changes from Frankfurt:
>
>- Reworded many of the issues to be more concise.
>- Did not publish issues for INT, OOM, or VNFRQTS
>
> Note that the TSC has reviewed a schedule proposal that has *M1 on July
> 9.* So, you're advised to *get started on these as soon as possible*.
>
> Find your project's M1 epic from the list below:
>
> AAF-1163
> AAI-2945
> DCAEGEN2-2299
> CCSDK-2462
> APPC-1890
> CLI-274
> HOLMES-317
> DMAAP-1445
> LOG-1219
> OPTFRA-778
> PORTAL-922
> MUSIC-597
> SDNC-1248
> USECASEUI-446
> SDC-3134
> SO-2993
> VNFSDK-598
> VVP-424
> MULTICLOUD-1083
> VID-841
> MSB-481
> VFC-1677
> MODELING-373
> POLICY-2659
> EXTAPI-454
> CLAMP-869
>
> Let me know if you have any questions.
>
> David
>
> --
> *David McBride*
> Release Manager
> Linux Foundation Networking (LFN)
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> IRC: dmcbride
>


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

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

View/Reply Online (#6643): https://lists.onap.org/g/onap-tsc/message/6643
Mute This Topic: https://lists.onap.org/mt/74995473/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] Call for support from CCPVN/BBS Usecase for DCAE mS (RESTConf and VESAdapter)

[Vijay VK]

Seshu - Sure, let me know when. Btw, you can find the outstanding jira list for 
RESTConf collector here - 
https://jira.onap.org/browse/DCAEGEN2-2293?jql=labels%20%3D%20dcae-restconf. 
From Guilin standpoint,  would prioritize on following as these are mandatory 
TSC requirements.

  1.  Java11 support
  2.  Vulnerability removal
  3.  Switching to onap recommended base image (java) (DCAE jira to be created)

And David - Thank you for response/confirmation from BBS usecase perspective.

Regards,
Vijay.
From: onap-tsc@lists.onap.org  On Behalf Of seshu 
kumar m via lists.onap.org
Sent: Wednesday, July 01, 2020 12:26 PM
To: onap-tsc ; onap-usecasesub 
; onap-discuss ; 
FREEMAN, BRIAN D 
Cc: onap-tsc ; onap-arc 
Subject: Re: [onap-tsc] Call for support from CCPVN/BBS Usecase for DCAE mS 
(RESTConf and VESAdapter)


Hi Vijay,



I'm checking to see how can we help on the Restconf collector part of the code.

Can we catch up to discuss the details on what is required to resolve in Guilin.

--
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:Vijay VK mailto:vv7...@att.com>>
To:onap-usecasesub 
mailto:onap-usecase...@lists.onap.org>>;onap-discuss
 
mailto:onap-disc...@lists.onap.org,bf1...@att.com>>
Cc:onap-tsc mailto:onap-tsc@lists.onap.org>>;onap-arc 
mailto:onap-...@lists.onap.org>>
Date:2020-06-30 22:35:50
Subject:[onap-tsc] Call for support from CCPVN/BBS Usecase for DCAE mS 
(RESTConf and VESAdapter)

CCPVN/BBS Usecase team,
The following MS were introduced in DCAE during R3/R4 release in support of 
your usecase.


  *   VES Adapter/Mapper  (original contribution from TechM)
  *   RESTConf collector (original contribution from Huawei)

However for both El-Alto and Frankfurt releases, there has been no active 
development/support offered.  In-addition to backlog, these components are due 
for security updates (vulnerabilities fixes, java11 upgrade etc.) that are 
mandated by TSC for Guilin.

Please confirm if you are still requiring these microservices to be continued, 
if so I do expect usecase teams to provide resources for support (if any 
question on work entailed/jira's - pls reach out to me).
In the absence of volunteer or confirmation of these services being required - 
there is risk of deprecating this components for Guilin.  Would appreciate your 
response soon as Guilin/M1 is due next week.

Regards,
Vijay
(DCAE PTL)


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

View/Reply Online (#6642): https://lists.onap.org/g/onap-tsc/message/6642
Mute This Topic: https://lists.onap.org/mt/75218062/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] Jenkins, Nexus, Nexus3 downtime maintenance - July 1st 12:00 - 14:00 PT

[Jessica Wagantall]

Dear team.


This is a small reminder of this downtime happening in aprox 2 hours.
Please be advised that *Jenkins, Nexus and Nexus3 will be unavailable for 2
hrs. *

Thanks!
Jess

On Tue, Jun 30, 2020 at 1:55 PM Jessica Wagantall via lists.onap.org
 wrote:

> Dear ONAP team,
>
> Jenkins, Nexus and Nexus3 will be under maintenance
> July 1st 12:00 - 14:00 PT (14:00 - 16:00 Central) for
> auth0 support.
>
> These services will not be accessible during this time and Jenkins jobs
> will be paused.
>
> Please let us know for any issues and we can always plan for a
> better timing.
>
> Thanks so much!
> Jess
> 
>
>

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

View/Reply Online (#6641): https://lists.onap.org/g/onap-tsc/message/6641
Mute This Topic: https://lists.onap.org/mt/75240581/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 support from CCPVN/BBS Usecase for DCAE mS (RESTConf and VESAdapter)

[seshu kumar m via lists.onap.org]

Hi Vijay,


I'm checking to see how can we help on the Restconf collector part of the code.

Can we catch up to discuss the details on what is required to resolve in Guilin.

--
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:Vijay VK 
To:onap-usecasesub ;onap-discuss 

Cc:onap-tsc ;onap-arc 
Date:2020-06-30 22:35:50
Subject:[onap-tsc] Call for support from CCPVN/BBS Usecase for DCAE mS 
(RESTConf and VESAdapter)

CCPVN/BBS Usecase team,
The following MS were introduced in DCAE during R3/R4 release in support of 
your usecase.


  *   VES Adapter/Mapper  (original contribution from TechM)
  *   RESTConf collector (original contribution from Huawei)

However for both El-Alto and Frankfurt releases, there has been no active 
development/support offered.  In-addition to backlog, these components are due 
for security updates (vulnerabilities fixes, java11 upgrade etc.) that are 
mandated by TSC for Guilin.

Please confirm if you are still requiring these microservices to be continued, 
if so I do expect usecase teams to provide resources for support (if any 
question on work entailed/jira’s – pls reach out to me).
In the absence of volunteer or confirmation of these services being required – 
there is risk of deprecating this components for Guilin.  Would appreciate your 
response soon as Guilin/M1 is due next week.

Regards,
Vijay
(DCAE PTL)


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

View/Reply Online (#6640): https://lists.onap.org/g/onap-tsc/message/6640
Mute This Topic: https://lists.onap.org/mt/75218062/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-ptl] [onap-tsc] Guilin milestone status / M1 scheduled July 9 #guilin

[TIMONEY, DAN]

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


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


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

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

[David McBride]

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

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

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

View/Reply Online (#6638): https://lists.onap.org/g/onap-tsc/message/6638
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-usecasesub] Call for support from CCPVN/BBS Usecase for DCAE mS (RESTConf and VESAdapter)

[David Perez Caparros]

Hi Vijay,

from the BBS team side, RCC and VES mapper are not strictly necessary. They are 
only needed if the vendor equipment requires RESTCONF.
At the moment, we cannot guarantee resources to implement the maintenance tasks 
required in Guilin, so it’s fine for us to deprecate them.
In case we get additional support before Guilin/M1, I will let you know.

Regards,
David

On 30 Jun 2020, at 19:05, Vijay VK mailto:vv7...@att.com>> 
wrote:

CCPVN/BBS Usecase team,
The following MS were introduced in DCAE during R3/R4 release in support of 
your usecase.


  *   VES Adapter/Mapper  (original contribution from TechM)
  *   RESTConf collector (original contribution from Huawei)


However for both El-Alto and Frankfurt releases, there has been no active 
development/support offered.  In-addition to backlog, these components are due 
for security updates (vulnerabilities fixes, java11 upgrade etc.) that are 
mandated by TSC for Guilin.

Please confirm if you are still requiring these microservices to be continued, 
if so I do expect usecase teams to provide resources for support (if any 
question on work entailed/jira’s – pls reach out to me).
In the absence of volunteer or confirmation of these services being required – 
there is risk of deprecating this components for Guilin.  Would appreciate your 
response soon as Guilin/M1 is due next week.

Regards,
Vijay
(DCAE PTL)



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

View/Reply Online (#6637): https://lists.onap.org/g/onap-tsc/message/6637
Mute This Topic: https://lists.onap.org/mt/75234865/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 Prioritization - Latest Updates

[Catherine LEFEVRE]

Thank you Lei for the updates.
You might want to discuss with the VVP and VFSDK who are already performing 
some VNF validation.

In the meanwhile I will finalize the review with the ONAP TSC based on your 
constructive discussions with Morgan.
Thank you again !

Best regards
Catherine
From: 黄蕾 
Sent: Wednesday, July 1, 2020 1:14 PM
To: Lefevre, Catherine 
Cc: onap-tsc ; onap-release 
; morgan.richomme ; 杨艳 
; Kanagaraj Manickam 
Subject: Re: [onap-tsc] TSC Prioritization - Latest Updates

Dear Catherine,

After today's detailed discussion with Morgan, we both agree on pushing forward 
these four testing automatic requirements, the testing objects, target and 
method are different from each other.

Thanks again to Morgan for preparing today's call for us discuss fully about 
our two project. :)

Best Regards,
Lei


发件人: Catherine LEFEVRE
时间: 2020/07/01(星期三)19:10
收件人: 
onap-tsc;onap-release;
主题: [onap-tsc] TSC Prioritization - Latest Updates
Good morning/afternoon Requirement Owners, PTLs,

I want to inform you that the following requirements have been reviewed and 
prioritized by the ONAP TSC as follows

  1.  REQ-339 - Container Network Function Test Platform (CNTP): OVP 2.0 
support and Enable Network Service testing (RANK #3 PTL GO/NO GO)
  2.  REQ-385 - IPv4/IPv6 dual stack support in ONAP (RANK #3 PTL GO/NO GO)

We are waiting for the final discussions between Morgan and Lei regarding 
REQ-335 to REQ-338 - 
https://lists.onap.org/g/onap-tsc/message/6613

TSC Vote in progress for the following requirements:

  1.  REQ-329: Guilin-R7 - Support for Intent-based Network
  2.  REQ-345: 5G OOF SON use case requirements for Guilin release
  3.  REQ-386: Apply common Swagger style and documentation generation tools to 
create robust ONAP API documentation

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

[cid:image001.png@01D64FAD.F4089CF0][cid:image002.png@01D64FAD.F4089CF0]

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.



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

View/Reply Online (#6636): https://lists.onap.org/g/onap-tsc/message/6636
Mute This Topic: https://lists.onap.org/mt/75232350/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 Prioritization - Latest Updates

[hlfight_]

Dear Catherine,






After today's detailed discussion with Morgan, we both agree on pushing forward 
these four testing automatic requirements, the testing objects, target and 
method are different from each other.  




Thanks again to Morgan for preparing today's call for us discuss fully about 
our two project. :) 




Best Regards,

Lei








 



发件人: Catherine LEFEVRE

时间: 2020/07/01(星期三)19:10

收件人: onap-tsc;onap-release;

主题: [onap-tsc] TSC Prioritization - Latest Updates 

 

Good morning/afternoon Requirement Owners, PTLs, 

  

I want to inform you that the following requirements have been reviewed and 
prioritized by the ONAP TSC as follows  REQ-339 - Container Network Function 
Test Platform (CNTP): OVP 2.0 support and Enable Network Service testing (RANK 
#3 PTL GO/NO GO)REQ-385 - IPv4/IPv6 dual stack support in ONAP (RANK #3 PTL 
GO/NO GO) 

  

We are waiting for the final discussions between Morgan and Lei regarding 
REQ-335 to REQ-338 - https://lists.onap.org/g/onap-tsc/message/6613 

  

TSC Vote in progress for the following requirements:  REQ-329: Guilin-R7 - 
Support for Intent-based NetworkREQ-345: 5G OOF SON use case requirements for 
Guilin releaseREQ-386: Apply common Swagger style and documentation generation 
tools to create robust ONAP API documentation 

  

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. 

  


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

View/Reply Online (#6635): https://lists.onap.org/g/onap-tsc/message/6635
Mute This Topic: https://lists.onap.org/mt/75232350/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] TSC Prioritization - Latest Updates

[Catherine LEFEVRE]

Good morning/afternoon Requirement Owners, PTLs,

I want to inform you that the following requirements have been reviewed and 
prioritized by the ONAP TSC as follows

  *   REQ-339 - Container Network Function Test Platform (CNTP): OVP 2.0 
support and Enable Network Service testing (RANK #3 PTL GO/NO GO)
  *   REQ-385 - IPv4/IPv6 dual stack support in ONAP (RANK #3 PTL GO/NO GO)

We are waiting for the final discussions between Morgan and Lei regarding 
REQ-335 to REQ-338 - https://lists.onap.org/g/onap-tsc/message/6613

TSC Vote in progress for the following requirements:

  *   REQ-329: Guilin-R7 - Support for Intent-based Network
  *   REQ-345: 5G OOF SON use case requirements for Guilin release
  *   REQ-386: Apply common Swagger style and documentation generation tools to 
create robust ONAP API documentation

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

[cid:image001.png@01D64FA7.BD38FE50][cid:image003.png@01D64FA8.F9F2FE80]

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.


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

View/Reply Online (#6634): https://lists.onap.org/g/onap-tsc/message/6634
Mute This Topic: https://lists.onap.org/mt/75232350/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 Release: REQ-335 to REQ-338

[hlfight_]

Dear Catherine,






After today's detailed discussion with Morgan, we both agree on pushing forward 
these four testing automatic requirements, the testing objects, target and 
method are different from each other.  




Thanks again to Morgan for preparing today's call for us discuss fully about 
our two project. :) 




Best Regards,

Lei








 



发件人: Lefevre, Catherine

时间: 2020/07/01(星期三)05:51

收件人: morgan.richomme;黄蕾;

抄送人: onap-tsc;yangyanyj;

主题: RE: [onap-tsc] Guilin Release: REQ-335 to REQ-338 

 

Thank you Morgan, Lei for your feedback. 

  

Lei – you should not be worried about the TSC deadline. 

You have been really active, replying to all of our queries. 

  

Many thanks & regards 

Catherine 

 

 

From: morgan.richo...@orange.com  
 Sent: Tuesday, June 30, 2020 4:01 PM
 To: 黄蕾 ; Lefevre, Catherine 

 Cc: onap-tsc ; yangyanyj 
 Subject: RE:[onap-tsc] Guilin Release: REQ-335 to REQ-338   

  

 

 

Hi  

 

   

 

I will hopefully have a better view tomorrow :)  

 

   

 

 

I remember I saw a presentation in Prag on this topic. @Lei do not hesitate to 
correct me if I am wrong.  

 

   

 

The title of the requirements is maybe a bit misleading, Certification shall be 
indicated.  

 

   

 

As far as I remember automation testing here deals only with VNF automation 
testing from SDC interface.  

 

The goal is not to test ONAP to validate ONAP but to certify VNF vendors that 
their VNF can be deployed from ONAP.  

 

It requires some work on SDC (but resources are provisionned)+ use/update of 
CLI + glue (if VNF needs network resources)  

 

  

 

There is probably some tooling overlaps with what has been done in Integration 
regarding VNF automation.  

In frankfurt I tried to integrate the VNF_Tosca use case in CI. I think we were 
not far.  

 

This use case is already leveraging the tools used for Certification automation 
(CLI, oclip,..)  

 

Integration is using alternatives to CLI (Robot, postman, onap_tests, soon 
python_onapsdk,..) to interact with ONAP  

 

that is why vCPE_Tosca was interesting because it was following another logic  

 

It could have been the opportunity to sue and test CLI and components that are 
no very tested (MSB, ESR) 

 

Unfortunately I was able to finalize the integration, I created a Jira in order 
to enhance the use case for Guilin.

 

   

 

As a conclusion, If I understood well, goals are different.   

 

There requirements deal with VNF testing automation within Certification 
context.  

 

   

 

/Morgan  

 

   

 

   

 

De : 黄蕾 [huanglei...@chinamobile.com]
 Envoyé : mardi 30 juin 2020 15:10
 À : Catherine LEFEVRE; RICHOMME Morgan TGI/OLN
 Cc : onap-tsc; yangyanyj
 Objet : Re: [onap-tsc] Guilin Release: REQ-335 to REQ-338  

 

 

Dear Catherine, Morgan  

 

   

 

 Considering TSC Guilin prioritization decision meeting is approaching, but the 
nearest integration weekly call is held on tomorrow (July 1st), time is very  
limited, we worry about over the deadline of TSC process. After preliminary 
discussion with Morgan offline, we both agree on establishing this automatic 
testing platform , so I suggest push milestone process forward first, I think 
both me and Morgan agree  on this point. And then I'll help share the detail of 
our automatic testing idea with integration team tomorrow in weekly call, talk 
about possible coorperation in future. :)  

 

   

 

Best Regards,  

 

Lei  

 

--- 

黄蕾 

人工智能和智慧运营研发中心 

中国移动通信有限公司研究院 

中国北京市西城区宣武门西大街32号（100053） 

  

Huang Lei 

Center of AI and Intelligent Operation R&D 

China Mobile Research Institute 

No.32 Xuanwumen west street, Xicheng District, Beijing 100053, China 

  

Mobile: +86 18800156155 

Email: huanglei...@chinamobile.com 

- 

  

 

 

 

   

 

 

发件人: Catherine LEFEVRE  

 

时间: 2020/06/30(星期二)19:59  

 

收件人: RICHOMME Morgan TGI/OLN;onap-tsc;  

 

主题: [onap-tsc] Guilin Release: REQ-335 to REQ-338

 

Good evening/afternoon Lei Huang, Morgan, 


 Please share the conclusions, after your today’s discussions, concerning 
“REQ-335 to REQ-338”. 

It will help a lot the ONAP TSC to finalize their Guilin prioritization 
concerning these requirements. 

  

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 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 p