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

[Yang Bin]

+1

Best Regards,
Bin Yang,Solution Engineering Team,Wind River
ONAP Multi-VIM/Cloud PTL
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of 
Kenny Paul
Sent: Friday, November 15, 2019 3:30 AM
To: onap-tsc-v...@lists.onap.org
Subject: [onap-tsc] Milestone Exception Process Timing Vote - Ends Wed., Nov 20 
@ noon Pacific

(bcc' to onap-tsc for visibility)

As evidenced by today's call the Milestone Exception Process ( 
https://lists.onap.org/g/onap-tsc-vote/topic/40467217#1262 ) approved by the 
TSC last week (https://lists.onap.org/g/onap-tsc/message/5592) is certainly 
needed. My recommendation to the TSC when the process was approved was to make 
it effective beginning with Frankfurt M2. I didn't see any follow-ups to that 
suggestion, so I am initiating a vote:

VOTE: Does the TSC approve implementing the Milestone Exception Process 
beginning with Frankfurt M2?
+1, 0, -1

Thanks!
-kenny



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

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

[onap-tsc] DCAE Committer promotion requests : Joseph O'Leary

[Vijay VK]

Hi TSC/Infrastructure-Coordinator,
I would like to promote Joseph O'Leary as a committer for DCAE project; please 
find below the supporting documentation for this request.

https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BDCAE%5D%3A+Joseph+O%27Leary

I would greatly appreciate your approval on this regard.

Thanks,
Vijay.


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

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

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

[Alexis de Talhouet]

> On Nov 14, 2019, at 2:30 PM, Kenny Paul  wrote:
> 
> VOTE: Does the TSC approve implementing the Milestone Exception Process 
> beginning with Frankfurt M2? 
> 


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

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

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

[Davide Cherubini]

+1


[signature_1705304268]

Davide Cherubini
Principal Engineer
Lead Software, Open Source and Labs
Strategy & Innovation
Cloud & Automation CoE

Babbage House, The Connection, Newbury, Berkshire RG14 2FN
+44 7770 700172

davide.cherub...@vodafone.com
vodafone.com

The future is exciting.
Ready?




From:  on behalf of Kenny Paul 

Reply to: "onap-tsc@lists.onap.org" 
Date: Thursday, 14 November 2019 at 19:30
To: "onap-tsc-v...@lists.onap.org" 
Subject: [onap-tsc] Milestone Exception Process Timing Vote - Ends Wed., Nov 20 
@ noon Pacific

(bcc’ to onap-tsc for visibility)

As evidenced by today’s call the Milestone Exception Process ( 
https://lists.onap.org/g/onap-tsc-vote/topic/40467217#1262 ) approved by the 
TSC last week (https://lists.onap.org/g/onap-tsc/message/5592) is certainly 
needed. My recommendation to the TSC when the process was approved was to make 
it effective beginning with Frankfurt M2. I didn’t see any follow-ups to that 
suggestion, so I am initiating a vote:

VOTE: Does the TSC approve implementing the Milestone Exception Process 
beginning with Frankfurt M2?
+1, 0, -1

Thanks!
-kenny



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

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

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

[Andreas Geissler]

+1

Von: onap-tsc@lists.onap.org  Im Auftrag von Kenny Paul
Gesendet: Donnerstag, 14. November 2019 20:30
An: onap-tsc-v...@lists.onap.org
Betreff: [onap-tsc] Milestone Exception Process Timing Vote - Ends Wed., Nov 20 
@ noon Pacific

(bcc' to onap-tsc for visibility)

As evidenced by today's call the Milestone Exception Process ( 
https://lists.onap.org/g/onap-tsc-vote/topic/40467217#1262 ) approved by the 
TSC last week (https://lists.onap.org/g/onap-tsc/message/5592) is certainly 
needed. My recommendation to the TSC when the process was approved was to make 
it effective beginning with Frankfurt M2. I didn't see any follow-ups to that 
suggestion, so I am initiating a vote:

VOTE: Does the TSC approve implementing the Milestone Exception Process 
beginning with Frankfurt M2?
+1, 0, -1

Thanks!
-kenny



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

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

答复: [onap-tsc] URGENT - ONAP Frankfurt - CALL FOR SUPPORT - WE NEED YOU

[Shen Tao]

Hi Catherine,

Could you please tell me why network slicing use case couldn’t be included
into U-UI scope?

 

The network slicing team has already devoted enough resources in U-UI, they
already confirmed with me and created the Jira task before M1. According to
my knowledge, the LLD and API documentation of their enhancement in U-UI has
been finished about 80% by their team following the instruction given by
U-UI team. They definitely can catch API Freeze and Code Freeze. I didn’t
see any risks to include network slicing use case into U-UI scope.

 

I add network slicing use case into U-UI scope before M1. Also, U-UI doesn’
t have any architectural impacts as this module is used for providing the
Use interface for use cases. I noticed that Lin’s email to TSC list
clarifying this use case also gave the evidence on that.

 

I kindly request you to add network slicing use case into U-UI scope, which
will be an important functional enhancement in U-UI and will help us to
fulfill other “TSC Must Have” items for Frankfurt.

 

BR,

Tao

---

 

 

发件人: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] 代表
Catherine LEFEVRE
发送时间: 2019年11月15日 18:29
收件人: onap-tsc@lists.onap.org
主题: Re: [onap-tsc] URGENT - ONAP Frankfurt - CALL FOR SUPPORT - WE NEED
YOU

 

Good morning Tao,

 

I confirm that the UUI project is now green based on the feedback you have
provided last night -
https://wiki.onap.org/display/DW/Frankfurt+Milestone+Status

 

Please note that the UUI is not impacted by the Network Slicing requirement
for the Frankfurt release.

Only ExtAPI and SO are impacted by this requirement -
https://wiki.onap.org/display/DW/Frankfurt+Release+Requirements

 

Best regards

Catherine

 

From: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] On Behalf Of
Shen Tao
Sent: Friday, November 15, 2019 4:38 AM
To: onap-tsc@lists.onap.org
Cc: TALASILA, MANOOP 
Subject: 答复: [onap-tsc] URGENT - ONAP Frankfurt - CALL FOR SUPPORT - WE
NEED YOU

 

Dear Catherine, 

 

Thank you a lot for helping UUI in Frankfurt release planning.

Sorry that I didn’t realize that I should write “TSC MUST HAVE” into
release planning and used old M1 template.

I have updated UUI release planning and created 4 jira tickets for “TSC
MUST HAVE” to solve the M1 pending issues.

And added jira links to the release planning of UUI use case which is going
to support in Frankfurt release.

I believe that we have had an in-depth discussion on 5G slicing use case and
have prepared enough resources to develop this feature.

 

Best regards,

Tao

 

 

发件人: onap-tsc@lists.onap.org [mailto:onap-tsc@lists.onap.org] 代表
Catherine LEFEVRE
发送时间: 2019年11月15日 0:07
收件人: onap-tsc@lists.onap.org
抄送: TALASILA, MANOOP
主题: [onap-tsc] URGENT - ONAP Frankfurt - CALL FOR SUPPORT - WE NEED YOU
重要性: 高

 

Dear ONAP Community,

 

We are looking for developers/testers to support the following projects:
UUI, PORTAL and OOF for the Frankfurt release.

These components did not find enough developers/testers to help them to meet
All the Frankfurt “TSC MUST HAVE”.

https://wiki.onap.org/display/DW/Frankfurt+Code+Impact+View+per+Component
 

 

If you are interested to help them then please urgently contact the
respective PTLs no later than November 18th EOD.

UUI: shen...@chinamobile.com

OOF:   shankarp...@gmail.com

Portal: talas...@research.att.com

 

If we do not identify the additional resource then the use
cases/requirements that depend on these components will be reviewed and
likely descoped.

 

In addition we have not yet found a PTL to support the Logging project.

Please contact Prudence (prudence...@amdocs.com) if you are interested to
take this role.

 

Thanks in advance for your support.

 

Many thanks & regards

Catherine

 

 


Catherine Lefèvre

AVP Software Development & Engineering

 

AT Labs �C 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

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