[onap-discuss] Plan towards agreeing on Dublin scope

[Alla Goldner]

Hi all,

During today's TSC meeting we discussed Dublin's Roadmap and agreed on the 
following:


1.   Nov 1st - is the last day for Service Providers requirements for 
Dublin https://wiki.onap.org/display/DW/SP+priorities+for+Dublin

I will consolidate all information already provided by additional SP into this 
page (beginning of the next week)

2.   Nov 15th  - is the last day for providing use case/functional 
requirements as a candidates for Dublin

3.   Nov 29th  - is the last day for getting all of the requirements 
(architecture, security, projects, S3P etc.) and getting a single consolidated 
list so all of the projects have full picture of what is required from them. By 
this date, all use cases/functional requirements need to be discussed with a 
different projects, and demanded scope of development should be clear to the 
projects

4.   Vf2f in December - making a decision of what is indeed included in 
Dublin, based on Service providers priorities and projects' commitments


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D46C90.8E2E81D0]

“Amdocs’ email platform is based on a third-party, worldwide, cloud-based 
system. Any emails sent to Amdocs will be processed and stored using such 
system and are accessible by third party providers of such system on a limited 
basis. Your sending of emails to Amdocs evidences your consent to the use of 
such system and such processing, storing and access”.

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

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

Re: [onap-discuss] Non-functional requirement proposal for Dublin: Adopting ONAP Normative Base Images

[Alla Goldner]

Hi,

I think it belongs to S3P – I would describe them as new S3P requirements for 
Dublin.
Gildas, I would not add them under Casablanca non-functional requirements.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D46B6E.F2496D60]

From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Wednesday, October 24, 2018 1:30 AM
To: Adolfo Perez-Duran ; Alla Goldner 
; Jason Hunt ; 
onap-discuss@lists.onap.org
Cc: Tina Tsou ; Brian Hedstrom 
; Bob Monkman ; Yunxia 
Chen 
Subject: RE: Non-functional requirement proposal for Dublin: Adopting ONAP 
Normative Base Images

Hi,

I see 2 approaches:

1)  Make it part of one of the S3P dimension

2)  Or include it in the Non-functional requirement list (example: as we 
did in Casablanca at 
https://wiki.onap.org/display/DW/Casablanca+Release+Requirements#CasablancaReleaseRequirements-NonFunctionalRequirements
 )

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Adolfo Perez-Duran [mailto:adolfo.perez-du...@oamtechnologies.com]
Sent: Tuesday, October 23, 2018 11:39 AM
To: alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>; Gildas Lanilis 
mailto:gildas.lani...@huawei.com>>; Jason Hunt 
mailto:djh...@us.ibm.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Tina Tsou mailto:tina.t...@arm.com>>; Brian Hedstrom 
mailto:brian.hedst...@oamtechnologies.com>>;
 Bob Monkman mailto:bob.monk...@arm.com>>; Yunxia Chen 
mailto:helen.c...@huawei.com>>
Subject: Non-functional requirement proposal for Dublin: Adopting ONAP 
Normative Base Images

Alla, Gildas, Jason

Could you advise on the process we should follow to introduce this 
non-functional requirement to the Dublin release?

Requirement: Use ONAP Normative Base Images to Improve deployability and reduce 
footprint and resource consumption

Rationale:
Both operators looking to experiment with ONAP and developers producing ONAP 
containers report long build times and high resource consumption. The OOM team 
also reports long deployment times and high resource consumption.

Furthermore, small, efficient images also address the issue some operators have 
reported when they have attempted to deploy ONAP to "kick the tires."

Proposed solution and benefits:
ONAP's CIA project has identified a set of container base images that, if 
adopted,  would alleviate the problems of resource consumption and long build 
times ONAP projects are experiencing.

Experiments conducted with the proposed base images have produced container 
images that were up to two orders of magnitude smaller. Smaller images 
translate into smaller build and deploy times as well as smaller footprint.

Community support:
The idea of using these normative base images was presented to the PTL 
community on October 8th, 2018. There is consensus and  support for the 
adoption of these base images and for the introduction of a non-functional 
requirement for Dublin.

It was suggested that also cover the requirement under S3P, Jason Hunt has been 
made aware of the requirement.

Timeline:
We propose that the requirement be met by M3.

Thanks,

Adolfo
“Amdocs’ email platform is based on a third-party, worldwide, cloud-based 
system. Any emails sent to Amdocs will be processed and stored using such 
system and are accessible by third party providers of such system on a limited 
basis. Your sending of emails to Amdocs evidences your consent to the use of 
such system and such processing, storing and access”.

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

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

[onap-discuss] Happy Jewish New Year to all those celebrating it!!!

[Alla Goldner]

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D44857.6D310230]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

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

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

[onap-discuss] Sep 3 and Sep 10 meetings will be cancelled as discussed today on the call

[Alla Goldner]

Sep 3 - Labor day in the US
Sep 10 - New Year (Rosh HaShana) in Israel

Have a Great Holidays

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D43E4C.74D13010]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

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

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

Re: [onap-discuss] Joint meeting with CL subcommittee

[Alla Goldner]

Hi all,

Today we had join meeting with CL subcommittee.
Thanks to all meeting's attendants!

Here is the meeting summary:


1.   All Beijing Release functional requirements leads (HPA (Alex), Change 
Management (Emmanuel), Scaling (Scott)) are asked to list all their functional 
requirements "shortcuts" which were made in Beijing Release and what is planned 
to be accomplished out of this list for Casablanca Release. I have created the 
following wiki page for this: 
https://wiki.onap.org/display/DW/Beijing+release+functional+requirements+shortcuts



2.   We must further discuss how we handle and prioritize requirements and 
use cases  (with EUAG involvement) prior to each release. I will raise this 
point at one of the upcoming TSC meetings



3.   We reviewed CL requirements 
https://wiki.onap.org/display/DW/Control+Loop+Sub+Committee+Release+Planning 
and our recommendation is:



a.   vFirewall enhancements - discuss with vFirewall team firstly

b.  Ease of creating analytic components and on-boarding DCAE micro 
services  - discuss with DCAE team firstly

c.   Event based Common API for Control Loop Operations and Defining and 
Modeling Control Loop for LCM Operations - discuss with ARC subcommittee

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D42DCD.A8B66BA0]

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Alla Goldner
Sent: Thursday, August 02, 2018 9:13 AM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc ; onap-discuss@lists.onap.org; DRAGOSH, 
PAMELA L (PAM) ; GILBERT, MAZIN E (MAZIN E) 

Subject: [onap-discuss] Joint meeting with CL subcommittee

Hi all,

As we discussed, next week's Usecase subcommittee meeting will be joined by 
Closed Loop subcommittee. I am working with Kenny on extending the meeting time 
to 2 hours.

Please prepare functional requirements you could think of as generic closed 
loop requirements for the future releases for our joint discussion.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D42DCD.A8B66BA0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

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

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

Re: [onap-discuss] [Onap-usecasesub] ZTE sign up for CCVPN use case vender

[Alla Goldner]

Great, Zhuoyao!

Please let Lin know what exact tasks you plan to contribute on.
We will review this use case and its test case definitions during our upcoming 
meeting on Monday.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D420F0.AB23FF90]

From: onap-usecase...@lists.onap.org [mailto:onap-usecase...@lists.onap.org] On 
Behalf Of huang.zhuo...@zte.com.cn
Sent: Saturday, July 21, 2018 10:38 AM
To: menglin...@chinamobile.comv; Alla Goldner 
Cc: onap-discuss@lists.onap.org; onap-usecase...@lists.onap.org; 
bo.kai...@zte.com.cn
Subject: [Onap-usecasesub] ZTE sign up for CCVPN use case vender




Hi, Lin MENG and Alla,



ZTE volunteers to sign up as a CCVPN use case vender and take part in 
the development and test activities including equipment support.



Best Regards!









黄卓垚huangzhuoyao



职位position
承载网管开发部/有线研究院/有线产品经营部Strategy & IT-IT Dept.


[cid:image002.gif@01D420F0.AB23FF90]

[cid:image003.gif@01D420F0.AB23FF90]
深圳市南山区科技南路55号中兴通讯研发大楼33楼
33/F, R Building, ZTE Corporation Hi-tech Road South,
Hi-tech Industrial Park Nanshan District, Shenzhen, P..R.China, 518057
T: +86 755    F: +86 755 
M: +86 xxx
E: huang.zhuo...@zte.com.cn<mailto:huang.zhuo...@zte.com.cn>
www.zte.com.cn<http://www.zte.com.cn/>



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

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

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

Re: [onap-discuss] [onap-tsc] TSC meetings: length, topics etc.

[Alla Goldner]

+1 on all points below.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D41166.EE28E1A0]

From: onap-...@lists.onap.org [mailto:onap-...@lists.onap.org] On Behalf Of 
Stephen Terrill
Sent: Sunday, July 01, 2018 6:09 PM
To: Arash Hekmat ; onap-tsc ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-tsc] TSC meetings: length, topics etc.

Hi Arash, All,

Thank-you for the suggestion - I think that this is a topic worthy of debate 
and bringing forward.  It would be beneficial to create clear expectations on 
the decision process and the ability to be efficient in this, and allow 
sufficient time between when the proposal for decision is requested and the 
decision meeting itself.  Afterall, a "surprise" request for decision is often 
meet with pushback as there is often a need to reflect and discuss with others.

I agree that all requests for a decision should be posted in advance to give 
time for reflection, debate and collecting input.  An exception due to time 
constraints maybe the milestone decisions.
-  I support that all decisions requests are posted in advance.  1 week 
maybe too long though, how about on the prior Monday?
-  It can be that decisions required two meeting cycles - the first one 
can often be for information before the decision if it is complex or 
controversial.

It may make sense to capture a policy around this; I think also that this is 
independent of the TS composition as it is also clarity for the community 
irrespective of the decided TSC composition.

BR,

Steve.

From: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> 
mailto:onap-...@lists.onap.org>> On Behalf Of Arash 
Hekmat
Sent: Friday, June 29, 2018 7:31 PM
To: onap-tsc mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-tsc] TSC meetings: length, topics etc.

ONAP TSC,

This is a process proposal for the ONAP TSC meetings. This is independent of 
the decision on the length and timing of the TSC meetings.

To help shorten the TSC meetings, it may be helpful to have a process where all 
TSC members views on the topics on the agenda are known before the meeting. 
This gives time to all the companies to know other companies views and to 
formulate their responses and votes before the meeting. This may help reduce 
surprises and lengthy discussions during the meeting.

One way to do this is to use the TSC Meeting Agendas wiki page: 
https://wiki.onap.org/display/DW/Upcoming+Agendas

The Linux Foundation (Kenny) could add a structure template to the TSC Meeting 
Agenda page and for each meeting:

  1.  Each presenter is asked to list (or upload) their discussion points on 
the Meeting Agenda page (at least a week prior to the meeting)
  2.  Each voting TSC member is asked to add their responses or views for each 
discussion point (at least 24 or 48 hours prior to the meeting)
  3.  During the TSC meeting, Kenny presents the Meeting Agenda page including 
all agenda points and the added responses and views
  4.  For every contentious point, where a vote may be needed, a vote is held 
during the TSC meeting to make a decision.

It should be clarified that:

  *   The TSC Meeting Agenda wiki page should not be used for back and forth 
discussions and arguments
  *   Adding responses or views to the TSC Meeting Agenda wiki page is not a 
substitute for attending the TSC meeting.

Arash Hekmat (Amdocs)

From: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> 
mailto:onap-...@lists.onap.org>> On Behalf Of Alla 
Goldner
Sent: Friday, June 29, 2018 1:22 AM
To: onap-tsc mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-tsc] TSC meetings: length, topics etc.

Hi all,

Following my AI from yesterday's TSC meeting, I am sending this email out.

We would want to make life easier for those in Asia who attend our (very late 
for them)TSC meetings on Thursday.
Having said that, we should keep in mind that the only timeframe during which 
we can have our meetings without getting into 12 am-6 am night hours for any of 
the regions is these timeframe.


  1.  One of the proposals raised by community was:

*   TSC meeting time should be shorten to 1 hour - so people in China 
suffer less due to late evening hours. We should clearly define what are topics 
on agenda for TSC meetings, and then also:
-  what can be discussed by some form of active chat (yet to be defined)
-  What may be discussed in bi or 3 - weekly meetings, which are also 
scheduled in advance


  1.  The other suggestion brought by Phill during our f2f meeting last week 
was to have separate meetings for a different regions.

In any case, further work on the proposals is needed (in case there is a 
support for any of these), or, alternatively, a new proposal can be brought to 
the table.

Please let us 

[onap-discuss] TSC meetings: length, topics etc.

[Alla Goldner]

Hi all,

Following my AI from yesterday's TSC meeting, I am sending this email out.

We would want to make life easier for those in Asia who attend our (very late 
for them)TSC meetings on Thursday.
Having said that, we should keep in mind that the only timeframe during which 
we can have our meetings without getting into 12 am-6 am night hours for any of 
the regions is these timeframe.


1.  One of the proposals raised by community was:


*   TSC meeting time should be shorten to 1 hour - so people in China 
suffer less due to late evening hours. We should clearly define what are topics 
on agenda for TSC meetings, and then also:

-  what can be discussed by some form of active chat (yet to be defined)

-  What may be discussed in bi or 3 - weekly meetings, which are also 
scheduled in advance


2.  The other suggestion brought by Phill during our f2f meeting last week 
was to have separate meetings for a different regions.

In any case, further work on the proposals is needed (in case there is a 
support for any of these), or, alternatively, a new proposal can be brought to 
the table.

Please let us know what you think about 2 proposals above and bring your own 
suggestions, if you have some.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D40F7E.4C5A76C0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

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

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

[onap-discuss] Usecase sucommittee meeting on 02/07/2018 - the agenda

[Alla Goldner]

Hi all,

Here is the agenda for the upcoming Usecase subcommittee meeting:


1.   We will discuss Casablanca f2f Forum.

a.   Ben Cheung will present his summary of the event (Thanks  a lot to Ben 
for preparing it!)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D40F7D.2825C6C0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

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

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

[onap-discuss] Usecase subcommittee meeting on 25/6/2018 will be cancelled

[Alla Goldner]

All use cases/functional requirements task forces are concentrating on M1 next 
week.
Bridge can be used for some discussions with relevant PTLs, if needed.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D4088B.99FDA400]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Casablanca Requirements

[Alla Goldner]

Gildas,

All endorsed use cases and requirements are included now.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image002.png@01D404CC.3DE22FA0]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Gildas Lanilis
Sent: Friday, June 15, 2018 12:04 AM
To: onap-tsc ; onap-discuss@lists.onap.org; 
onap-rele...@lists.onap.org
Subject: [onap-tsc] Casablanca Requirements
Importance: High

Hi All,

This is to follow up on June 14, TSC Meeting regarding gathering the 
Requirements for Casablanca Release.

To meet that goal, I have created a wiki page 
listing<https://wiki.onap.org/display/DW/Casablanca+Release+Requirements> in 3 
big categories:

1.   Use Cases

2.   Functional Requirements

3.   Non Functional Requirements

with an identified owner and the projects impacted.

Note this is NOT the Casablanca Release Scope, but the gathering of all 
requirements we have to consider and prioritize while we meet at Beijing.

I have done the first cut (some have already added complementary info, +1), 
however there are some empty cells and the community would be grateful if you 
could fill out the missing part by:

* Adding missing owners

* Identifying impacted projects

* Adding link to complementary set of information

Let me know if you have any questions, I will be glad to help.

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>
Mobile: 1 415 238 6287

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] From Casablanca Forum Program Committee

[Alla Goldner]

Hi all,

On behalf of Casablanca Forum Program Committee:

We almost finished to schedule, some adjustments still have to be made, we will 
complete asap.

In the mean time, please do the following:


  1.  Go to the page 
https://wiki.onap.org/display/DW/China+Telecom+Meeting+Rooms  and check to make 
sure your requested session is included
  2.  In case you have late sessions requests - please put them here 
https://wiki.onap.org/display/DW/Late+sessions%27+requests by Wednesday 
midnight PST the latest (also those already approached some of us by emails)

Also, we would also like to announce that meetings will be finished on Friday 
by 11 am, to make it easier for those leaving on that day.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D4027F.66909300]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Usecase subcommittee meeting on 11/06/2018: the summary

[Alla Goldner]

Hi,

Thanks to all meeting's participants!


1.   We endorsed CCVPN and Change Management use cases/requirements

2.   Please upload your presentations for the next week meeting (once page 
becomes available for editing, under our 2-hours session) and please inform me 
in advance who is going to present your use case/requirement there next week


See you in Beijing!

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D401B1.D96374C0]

From: Alla Goldner
Sent: Friday, June 08, 2018 9:03 PM
To: 'onap-usecase...@lists.onap.org' 
Cc: 'onap-tsc' ; 'onap-discuss@lists.onap.org' 

Subject: Usecase subcommittee meeting on 11/06/2018: the agenda

Hi all,

Here is agenda for the upcoming meeting:


1.   Check whether all comments provided for CCVPN and Change management 
(incl. alignment with PNF support) were addressed ; in this case, endorse these 
use cases/functional requirements for Casablanca

1.   Preparation for f2f meeting in Beijing:

a.   We will review your presentations - each one should take apprx. 10 
minutes, the same one used for Casablanca's endorsement can be used (or 
modified to fit into time slot/to include most recent added details). Please 
put it under  
https://wiki.onap.org/display/DW/Casablanca+Release+Developers+Forum+Session+Proposals
 , Usecase subcommittee session


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D401B1.D96374C0]
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Beijing Lessons Learned

[Alla Goldner]

Gildas,

This is scheduled in parallel to Usecase subcommittee meeting. Many of the 
people attending Usecase subcommittee are also interested in this topic.

 Best regards,

Alla Goldner

Open Network Division
Amdocs Technology





-Original Appointment-
From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Friday, June 08, 2018 2:52 AM
To: Gildas Lanilis; onap-discuss@lists.onap.org; onap-tsc; 
onap-rele...@lists.onap.org
Subject: [Onap-release] Beijing Lessons Learned
When: Monday, June 11, 2018 7:00 AM-8:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/2229355644


Dear ONAP Community,

We are organizing several brainstorming sessions next week in order to 
determine any improvement plan for the ONAP Casablanca Release.
The first step will be to collect your feedback concerning the ONAP Beijing 
Release from a retrospective and lesson learned perspectives.
Based on what we have learned, we will prioritize on what can be addressed as 
"Process Improvement" in short in longer term.

Planning:
Monday-Tuesday: Lesson Learned
Wednesday-Thursday: Process Improvement

It is important to understand that during Lesson Learned session, the goal is 
to collect feedback, not to fix things.
During the "Process Improvement" sessions, we will dive on the "how" to fix it.

Being realistic, we may need more time to discuss while we meet at Beijing. 
Ideally, we would like to get the low hanging fruits approved by TSC while at 
Beijing.
Feel free to submit already your feedback on the ONAP wiki page:
https://wiki.onap.org/display/DW/ONAP+Beijing+Retrospective+and+Lesson+Learned

We are suggesting to classify your inputs under the following categories
* Communication - Wiki, Mailing Lists, IRC
* Labs & Test Environment
* Release Management
* JIRA Management
* Code Review
* Development Infrastructure
* PTL Role
* Architecture
* Open Source Values
*   Others

Many thanks & regards
Catherine & Gildas

[https://d24cgw3uvb9a9h.cloudfront.net/static/90981/image/new/ZoomLogo_110_25.png]<http://zoom.us/>

Hi there,

Gildas Lanilis is inviting you to a scheduled Zoom meeting.

Join Zoom Meeting<https://zoom.us/j/2229355644>

Phone one-tap:
US: +16465588656,,2229355644# or 
+16699006833,,2229355644#

Meeting URL:
https://zoom.us/j/2229355644

Join by Telephone

For higher quality, dial a number based on your current location.

Dial:

US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 
369 0926 (Toll Free)

Meeting ID:
222 935 5644

International numbers<https://zoom.us/u/TU2f6>









  << File: ATT1.txt >>

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] new study in 3GPP SA5 on integration of ONAP and 3GPP configuration management services for 5G networks has been approved recently

[Alla Goldner]

I uploaded it to https://wiki.onap.org/pages/editpage.action?pageId=25434340

The objective is to:

  *   Study how the ONAP architecture can be supported in 3GPP.
  *   Study how the ONAP configuration management mechanisms (e.g. APP-C and 
VF-C) can be supported in 3GPP.
  *   Study ONAP protocol technology that may be used in 3GPP.
  *   Make recommendations on potential adaptations in 3GPP specifications to 
allow ONAP to be supported in 3GPP.
  *   Find mismatches and propose solutions.
  *   Identify potential feedback to ONAP to be 3GPP compliant for easier 
alignment.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3FCF1.D3CE0AD0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Community feedback on raised issues

[Alla Goldner]

Hi all,

As a reminder, we will have a discussion with a concrete improvement proposals 
during our f2f meeting in Beijing.
Please look on https://wiki.onap.org/display/DW/Community+Feedback and see if 
you have any additional constructive proposals for our work process improvement.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3FCC4.84FAE0E0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee meeting on 04/06/2018: the summary

[Alla Goldner]

Hi all,

Thanks to all meeting's participants! Here is the meeting's summary


1.   Lin Meng presented progress achieved on definition of CCVPN 
https://wiki.onap.org/display/DW/CCVPN%28Cross+Domain+and+Cross+Layer+VPN%29+USE+CASE

2.   Ajay Mahimkar presented progress achieved on Change Management 
definition for Casablanca

3.   Thinh Nguyenphu, ETSI SOL Vice-Chair, presented ETSI NFV scaling 
concept and detailed TOSCA model to support scaling

Action Items:


1.   Lin and Ajay will work offline with involved parties to resolve 
remaining, rather minor, comments till next Monday. If there are no outstanding 
comments by the next Monday, we will endorse these use cases/functional 
requirements

2.   Ajay will work offline with PNF support team to correlate proposals 
(Change Management also includes proposal for RAN PNF software upgrades)

3.   Thinh will upload his presentation to wiki (Thinh, thanks again for 
your courtesy to provide it!) and send link to it

4.   Requirements' terminology applicable to all activities running in ONAP 
(e.g. "should", "shall", "may" etc.) will be discussed during our f2f meeting

5.   Wiki centralized placement of the documentation will be discussed 
during f2f meeting

6.   All use cases/requirements authors:

a.   Please make sure to review your proposal with Architecture 
subcommittee to make sure it is aligned with Casablanca architecture plans. 
Chris has available time slots for the next week to do that

b.  Please prepare short 120 minutes presentation of your use 
case/requirement for Casablanca meeting. It cvan be based on your presentation 
used for endorsement, please let me know. We will review status next Monday

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3FCB6.B0EF0C20]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Thursday, May 31, 2018 10:48 AM
To: onap-usecase...@lists.onap.org
Cc: onap-tsc 
Subject: [onap-tsc] Agenda for Usecase subcommittee meeting on 04/06/2018

Hi all,

Here is agenda for the next week's Usecase subcommittee meeting:


1.   Lin Meng will present progress achieved on definition of CCVPN 
https://wiki.onap.org/display/DW/CCVPN%28Cross+Domain+and+Cross+Layer+VPN%29+USE+CASE

2.   Ajay Mahimkar will present progress achieved on Change Management 
definition for Casablanca

3.   Thinh Nguyenphu, ETSI SOL Vice-Chair, will present ETSI NFV scaling 
concept and detailed TOSCA model to support scaling

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3FCB6.B0EF0C20]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Casablanca Release Developers Forum - submission deadline

[Alla Goldner]

Hi all,

The deadline for topic submission is defined for the next Wednesday, June 6th, 
midnight PST.
After the deadline, your submissions will be marked as late and introduced into 
agenda only if scheduling allows.

The Program Committee (Alla, Lingli, Parviz, Alex, Ramki, Nermin).






Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3F846.75FADB90]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] CCVPN Usecase Update and Welcome Comments

[Alla Goldner]

Thanks a lot, Lin!!!

All, we will review it next Monday. Please, if possible, review it in advance 
of the meeting and provide your comments to Lin.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3F743.12F8C880]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of LinMeng
Sent: Tuesday, May 29, 2018 4:59 AM
To: onap-usecase...@lists.onap.org; onap-discuss@lists.onap.org
Subject: [onap-discuss] CCVPN Usecase Update and Welcome Comments

Hi everyone,
We’ve already updated more details about CCVPN use case on wiki page:
https://wiki.onap.org/display/DW/CCVPN%28Cross+Domain+and+Cross+Layer+VPN%29+USE+CASE

This use case centers on OTN, but scenarios are not only limited to OTN. Other 
physical networks such as SDH and PTN can also be applied as long as it can be 
formalized and comprised into services according to the specification.

We sincerely welcome other companies to join us.
Please feel free to leave a comment on the wiki page or send me an email.

Thanks!

---
孟琳
人工智能和智慧运营研发中心
中国移动通信有限公司研究院
中国北京市西城区宣武门西大街32号（100053）

Meng Lin
Center of AI and Intelligent Operation R
China Mobile Research Institute
No.32 Xuanwumen west street, Xicheng District, Beijing 100053, China

Mobile: +86 13810012241
Email: menglin...@chinamobile.com<mailto:menglin...@chinamobile.com>
-



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee is on the bridge https://zoom.us/j/180524208

[Alla Goldner]

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3F1EF.B4DDAA20]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Kenny, please move Usecase subcommittee meeting from MOnday to Tuesday next week, the same timeslot

[Alla Goldner]

Kenny,

I sent 5 requests since last Tuesday to reschedule this meeting next week. As 
you've mentioned there are no guaranteed slots on Wednesday, I suggested to 
reschedule for Tuesday next week 4 pm CET, as Architecture subcommittee meeting 
is cancelled, and use their bridge.

Please reschedule. Lack of rescheduling creates a LOT of confusion and people 
approach me asking if/when this meeting will happen next week.

TEAM - as discussed this week, we will cover remaining functional requirements 
(Change Management and HPA) proposals for Casablanca as well as go back to 
controversial issues related to 5G and review progress made for Cross Domain 
and Cross layer VPN service.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EE7D.03451CA0]

From: Alla Goldner
Sent: Thursday, May 17, 2018 5:15 PM
To: 'Kenny Paul' <kp...@linuxfoundation.org>
Cc: onap-usecase...@lists.onap.org
Subject: Kenny, please move Usecase subcommittee meeting from MOnday to Tuesday 
next week, the same timeslot

We can use arch subcommittee bridge, their meeting is cancelled next week

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EE7D.03451CA0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-usecasesub] [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

[Alla Goldner]

Vladimir,

if I understood Steve's comment correctly, it is not about any particular name, 
but more about recognition of yet additional standalone controller, while we 
don't have it as a part of our architecture.
This is why the proposal is to contain it under SDN-C (as, also according to 
our architecture, this is SDN-C's sub-module/sub-project), but explain 
explicitly what this module's functionality is.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDBE.84CB1FF0]

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Thursday, May 17, 2018 8:53 AM
To: Alla Goldner <alla.gold...@amdocs.com>; Dhananjay Pavgi 
<dp00476...@techmahindra.com>; SHANKARANARAYANAN, N K (N K) 
<shan...@research.att.com>; onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Subject: RE: [Onap-usecasesub] [onap-tsc] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

SDN-R is ONF project based on the Microwave Information Model TR-532, which is 
quite distant from what is needed for cellular RAN.
So what we knew as SDN-R in fact never was SDN Radio controller :)
Therefore we are free to keep the name SDN-R or find another good looking name. 
After all, it's just trademark.
I propose SADRAN= SoftwAre Defined RAN.
Thanks
Vladimir




From: 
onap-usecasesub-boun...@lists.onap.org<mailto:onap-usecasesub-boun...@lists.onap.org>
 
<onap-usecasesub-boun...@lists.onap.org<mailto:onap-usecasesub-boun...@lists.onap.org>>
 On Behalf Of Alla Goldner
Sent: Wednesday, May 16, 2018 10:28 PM
To: Dhananjay Pavgi 
<dp00476...@techmahindra.com<mailto:dp00476...@techmahindra.com>>; 
SHANKARANARAYANAN, N K (N K) 
<shan...@research.att.com<mailto:shan...@research.att.com>>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: Re: [Onap-usecasesub] [onap-tsc] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Guys,

All proponents of SDN-R terminology - when I asked during the meeting are there 
any concerns regarding the compromise proposal of saying "SDN-C" and then 
explicitly describing the functionality of this sub-module, there were no 
concerns about it.

One additional sub-compromise :) - can we agree on calling it "SDN-R (SDN-C 
sub-module)"?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDBE.84CB1FF0]

From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com]
Sent: Thursday, May 17, 2018 7:07 AM
To: SHANKARANARAYANAN, N K (N K) 
<shan...@research.att.com<mailto:shan...@research.att.com>>; Alla Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: RE: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Concur with views below from Shankar. Why confuse by changing it to SDN-C when 
we know it's functionality quite "Radio" and wireless domain specific.

thanks & regards,
Dhananjay Pavgi
+91 98220 22264

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
<onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> On 
Behalf Of SHANKARANARAYANAN, N K (N K)
Sent: Thursday, May 17, 2018 8:39 AM
To: Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Alla,

I don't understand the decision to change the SDN-R term after the several 
discussions in the 5G and SDN-R groups
using this term to describe the single ONAP OA controller persona (derived 
from CC-SDK) for mobility and wireless PNF/VNFs.
The reasons were articulated in the discussions. There has been momentum in 
using the SDN-R term, and changing it to SDN-C now causes confusion.

Regards,

Shankar


From: 
onap-usecasesub-boun...@lists.onap.org<mailto:onap-usecasesub-boun...@lists.onap.org>
 [onap-usecasesub-boun...@lists.onap.org] on behalf of All

Re: [onap-discuss] [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

[Alla Goldner]

Guys,

All proponents of SDN-R terminology - when I asked during the meeting are there 
any concerns regarding the compromise proposal of saying "SDN-C" and then 
explicitly describing the functionality of this sub-module, there were no 
concerns about it.

One additional sub-compromise :) - can we agree on calling it "SDN-R (SDN-C 
sub-module)"?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB8.E8F74180]

From: Dhananjay Pavgi [mailto:dp00476...@techmahindra.com]
Sent: Thursday, May 17, 2018 7:07 AM
To: SHANKARANARAYANAN, N K (N K) <shan...@research.att.com>; Alla Goldner 
<alla.gold...@amdocs.com>; onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Subject: RE: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Concur with views below from Shankar. Why confuse by changing it to SDN-C when 
we know it's functionality quite "Radio" and wireless domain specific.

thanks & regards,
Dhananjay Pavgi
+91 98220 22264

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
<onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> On 
Behalf Of SHANKARANARAYANAN, N K (N K)
Sent: Thursday, May 17, 2018 8:39 AM
To: Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: Re: [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee 
meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Alla,

I don't understand the decision to change the SDN-R term after the several 
discussions in the 5G and SDN-R groups
using this term to describe the single ONAP OA controller persona (derived 
from CC-SDK) for mobility and wireless PNF/VNFs.
The reasons were articulated in the discussions. There has been momentum in 
using the SDN-R term, and changing it to SDN-C now causes confusion.

Regards,

Shankar


From: 
onap-usecasesub-boun...@lists.onap.org<mailto:onap-usecasesub-boun...@lists.onap.org>
 [onap-usecasesub-boun...@lists.onap.org] on behalf of Alla Goldner 
[alla.gold...@amdocs.com]
Sent: Tuesday, May 15, 2018 4:21 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc
Subject: [Onap-usecasesub] The summary of Usecase subcommittee meeting 
14/05/2017 - Casablanca use cases/functional requirements endorsement
Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


1.   We have fully endorsed the following use cases/functional requirements:

a.   OSAM

b.  Auto Scaling out

c.   Consistent representation and identification of a cloud region in ONAP

d.  Edge Automation through ONAP



2.   5G group of functional requirements is endorsed, with the following 
exceptions:

a.   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements

b.  SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



3.   Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Casablanca-2Buse-2Bcases-2Bproposals-2Bfor-2Bendorsement=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=3F6B_OfdEFaZplwZX72F9ItZySDTzOU-cPey8nzXnHA=0xTbqUdLR-851l7UAd83zDbYq3UV0fmlrYmnbjQLwow=f2cGhvhTgxPybLCBOP_WT5ljK9FymPHnXzRnM6kRavI=>.
 We will discuss them next Monday



4.   Cross Domain and Cross Layer VPN Service was presented for the first 
time yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB8.E8F74180]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs p

Re: [onap-discuss] [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

[Alla Goldner]

Hi Steve,

Sorry for omitting this from the summary, I will add it to the summary posted 
on wiki now.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB7.91CD3820]

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Thursday, May 17, 2018 12:34 AM
To: Alla Goldner <alla.gold...@amdocs.com>; onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Subject: RE: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 
- Casablanca use cases/functional requirements endorsement

Hi Alla,

Thanks for the notes.

One clarification in the 5G group of functions - I recall correctly that SDN-R 
is to be replaced by SDN-C; and to extend that comment I also asked about the 
role of APPC (as that handles the higher layer VNFs) and the response was that 
is also a controller created from CCSDK (correct) and the split will be worked 
out in the architecture sub-committee.

BR,

Steve

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Tuesday, May 15, 2018 10:22 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: [onap-tsc] The summary of Usecase subcommittee meeting 14/05/2017 - 
Casablanca use cases/functional requirements endorsement

Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


  1.  We have fully endorsed the following use cases/functional requirements:
 *   OSAM
 *   Auto Scaling out
 *   Consistent representation and identification of a cloud region in ONAP
 *   Edge Automation through ONAP



  1.  5G group of functional requirements is endorsed, with the following 
exceptions:
 *   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements
 *   SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



  1.  Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



  1.  Cross Domain and Cross Layer VPN Service was presented for the first time 
yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EDB7.91CD3820]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee meeting next week

[Alla Goldner]

Hi all,

As I will be travelling on Monday next week, I will ask to move our meeting to 
Wednesday (only for the next week), same time slot.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EC4F.2C1595E0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

[Alla Goldner]

Hi all,

Here is the summary of our yesterday's meeting.
Thanks to all meeting participants!


1.   We have fully endorsed the following use cases/functional requirements:

a.   OSAM

b.  Auto Scaling out

c.   Consistent representation and identification of a cloud region in ONAP

d.  Edge Automation through ONAP



2.   5G group of functional requirements is endorsed, with the following 
exceptions:

a.   Terminology of SDN-R will be replaced by SDN-C, while it will be 
clarified what is the functionality of the SDN-C sub-module (used to be called 
SDN-R) to cover necessary enhancements

b.  SON and slice optimization topics will be re-discussed till next 
Monday's Usecase subcommittee meeting by all interested parties. There are 
concerns expressed by Cisco (Vladimir Yanover) which require additional 
discussions. We will monitor their progress and see if consensus is achieved or 
this issue needs to be raised and decided by the TSC



3.   Casablanca's HPA and Change Management authors - please upload your 
proposals under 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+endorsement.
 We will discuss them next Monday



4.   Cross Domain and Cross Layer VPN Service was presented for the first 
time yesterday. Some comments were received. Team will update according to the 
comments received and we will continue our discussion next Monday as well. 
Also, the team has asked for additional volunteering companies to participate 
in this development (please approach Lingli and Lin in case of interest)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EC3B.04166B00]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Requirements extracted from SP lists of priorities for Casablanca

[Alla Goldner]

Hi all,

I extracted common requirements received from a different Service Providers for 
Casablanca Release so far and put them under: 
https://wiki.onap.org/display/DW/Requirements+extracted+from+SP+lists+of+priorities+for+Casablanca

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA99.9885AE70]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] e2e use cases for approval by the TSC

[Alla Goldner]

Thanks, Vladimir,

5G task force: the following requests were received:


1.   SON support

2.   Network slicing support

3.   Controllers architecture

I attach them to this email.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA24.90EEFCE0]

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Saturday, May 12, 2018 6:17 PM
To: Alla Goldner <alla.gold...@amdocs.com>; onap-usecase...@lists.onap.org; 
onap-tsc <onap-...@lists.onap.org>; onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] e2e use cases for approval by the TSC

Hi, Alla,

Thanks for sending this. To my deep regret, there is a problem. Cisco several 
times expressed opposition to having SON in this release. The reason is that 
the architecture for SON was never properly analyzed.
Therefore I request removal of the following items

1.   SON - problem formulation

2.   SON - problem solving

3.   Slice optimization problem formulation

4.   Slice optimization problem solving
For all four, the concern is about splitting of the SON procedure(s) into two 
independent pieces.
For #3 and #4, in addition to that, there is no consistent definition yet (in 
3GPP) of slice level performance measurements. With no performance 
measurements, what kind of optimization can be arranged?

Thanks
Vladimir


From: Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>
Sent: Friday, May 11, 2018 11:34 AM
To: Vladimir Yanover (vyanover) 
<vyano...@cisco.com<mailto:vyano...@cisco.com>>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-tsc] e2e use cases for approval by the TSC

Hi Vladimir,

The implementation proposals for 5G use cases in Casablanca was also discussed 
during several Usecase subcommittee meetings and presentation is uploaded for 
yesterday's TSC meting 
https://wiki.onap.org/pages/editpage.action?pageId=28381537

I also attach it.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA24.90EEFCE0]

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Friday, May 11, 2018 11:24 AM
To: Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-tsc] e2e use cases for approval by the TSC

Alla,
Can you please clarify what exactly you received from 5G group?
Unless I am missing something, there was no 5G call to finally decide which use 
cases are going to the use case subcommittee. There were several proposals 
presented, most of them good, but even for those I have difficulty to 
understand which of them (and which versions) have been ever endorsed by the 5G 
group.
Thanks
Vladimir

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
<onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> On 
Behalf Of Alla Goldner
Sent: Friday, May 11, 2018 7:58 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-tsc] e2e use cases for approval by the TSC

Hi all,

As we didn't have any time left for use case discussion and approval during 
yesterday's TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors - please make sure you distributed your 
presentations for approval. So far, we've received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA24.90EEFCE0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/ab

Re: [onap-discuss] [onap-tsc] e2e use cases for approval by the TSC

[Alla Goldner]

Hi Bin,
Yes, of course, Centralized Representation and Consistent Identification of 
Cloud Regions In ONAP was presented and discussed and can be brought for 
approval by the TSC. In this case, this is already generalized functional 
requirement, and, indeed, in a very good shape requirements and status wise, 
btw, also highly demanded by the Service Providers provided their opinions on 
priorities.

Please upload short description to 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval as 
soon as possible.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA09.B0B1E490]

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Saturday, May 12, 2018 3:32 PM
To: Alla Goldner <alla.gold...@amdocs.com>
Cc: onap-usecase...@lists.onap.org; onap-tsc <onap-...@lists.onap.org>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Alla,


   My proposal is “Centralized Representation and Consistent 
Identification of Cloud Regions In 
ONAP<https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP>”,
 I presented during ONS usecase subcommittee session and I double check with 
all related PTLs after that, and got positive feedback to support that. I put 
the proposal at : 
https://wiki.onap.org/display/DW/Centralized+Representation+and+Consistent+Identification+of+Cloud+Regions+In+ONAP

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Alla Goldner [mailto:alla.gold...@amdocs.com]
Sent: Saturday, May 12, 2018 6:56 PM
To: Yang, Bin
Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Bin,

What is functional requirement you are talking about? Can you share more 
details?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3EA09.B0B1E490]

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Saturday, May 12, 2018 1:54 PM
To: Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>
Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Alla,

What about functional requirement proposal?  Should we do the same for 
approval or having another session ?  Thanks

Bin

在 2018年5月12日，02:43，Alla Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> 写道：
Hi all,

Link to the use case proposals is here: 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval.



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, May 11, 2018 7:58 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] e2e use cases for approval by the TSC

Hi all,

As we didn’t have any time left for use case discussion and approval during 
yesterday’s TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors - please make sure you distributed your 
presentations for approval. So far, we’ve received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
ONAP-TSC mailing list
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc
This message and the information contained herein is proprietary 

Re: [onap-discuss] [onap-tsc] e2e use cases for approval by the TSC

[Alla Goldner]

Hi Bin,

What is functional requirement you are talking about? Can you share more 
details?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E9F8.F02E8C60]

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Saturday, May 12, 2018 1:54 PM
To: Alla Goldner <alla.gold...@amdocs.com>
Cc: onap-usecase...@lists.onap.org; onap-tsc <onap-...@lists.onap.org>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] e2e use cases for approval by the TSC

Hi Alla,

What about functional requirement proposal?  Should we do the same for 
approval or having another session ?  Thanks

Bin

在 2018年5月12日，02:43，Alla Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> 写道：
Hi all,

Link to the use case proposals is here: 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval.



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, May 11, 2018 7:58 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] e2e use cases for approval by the TSC

Hi all,

As we didn’t have any time left for use case discussion and approval during 
yesterday’s TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors - please make sure you distributed your 
presentations for approval. So far, we’ve received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
ONAP-TSC mailing list
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] e2e use cases for approval by the TSC

[Alla Goldner]

Hi all,

Link to the use case proposals is here: 
https://wiki.onap.org/display/DW/Casablanca+use+cases+proposals+for+approval.



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E970.FB50ECB0]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, May 11, 2018 7:58 AM
To: onap-usecase...@lists.onap.org; onap-tsc <onap-...@lists.onap.org>; 
onap-discuss@lists.onap.org
Subject: [onap-discuss] e2e use cases for approval by the TSC

Hi all,

As we didn't have any time left for use case discussion and approval during 
yesterday's TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors - please make sure you distributed your 
presentations for approval. So far, we've received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E970.FB50ECB0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] e2e use cases for approval by the TSC

[Alla Goldner]

Hi all,

As we didn't have any time left for use case discussion and approval during 
yesterday's TSC meeting and likely will not have till the launch of Beijing due 
to urgent Beijing related discussions, the meeting decision was that we will 
host e2e use case approval discussions during Usecase subcommittee meetings on 
Monday, 4 pm CET.


1.   All use case authors - please make sure you distributed your 
presentations for approval. So far, we've received 5G group, Edge Automation 
and auto Scaling out

2.   Kenny, as agreed, please make sure all PTLs aware the discussion will 
take place during Use case subcommittee meeting

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E8FB.A240FE00]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Feedback on Casablanca priorities

[Alla Goldner]

Hi all,

We received a lot of feedback on Casablanca suggested priorities and missing 
requirements from SP forming End User Advisory Group.
I distributed the received feedback earlier and it is reflected on wiki.

The question is how we make sure this feedback is reflected, for balance 
between platform quality and enrichment, for the specific demanded use cases 
and for the functional/architecture gaps we are requested to fulfill. What 
would be the appropriate process to reflect it in our Casablanca plans?

Your feedback is appreciated!

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E3DA.88963F40]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] more feedback on Casablanca priorities received from Turk Telecom

[Alla Goldner]

https://wiki.onap.org/display/DW/Casablanca+goals

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E3D9.F6004EA0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] more feedback on Casablanca priorities received from Swisscom

[Alla Goldner]

https://wiki.onap.org/display/DW/Casablanca+goals

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E3AF.B12DD830]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee meeting on May 7th - the agenda

[Alla Goldner]

Hi all,

Here is agenda for Usecase subcommittee meeting next week:


1.   As agreed with Helen, we will dedicate 30 minutes to PNF support and 
scaling out (Beijing) use cases status of integration work - 
Scott/Zhao/Ben/Vimal



2.   Short reviews of Casablanca use cases proposals status - as we have to 
bring them for approval by the TSC next Thursday - all Casablanca use cases 
task forces leads

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E3A4.2C3D4170]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Community feedback

[Alla Goldner]

Hi,

Following discussions we had at ONS, and during one of the TSC meetings and 
also during the dedicated meeting we set, the following list of issues was 
consolidated:

https://wiki.onap.org/display/DW/Community+Feedback

All - please check if there are additional concerns/proposals you would like to 
add.

I put request for a session during our Beijing meeting to discuss and agree on 
constructive proposals for issues' resolution 
https://wiki.onap.org/display/DW/Casablanca+Release+Developers+Forum+Session+Proposals
 .

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E2C2.4779BE10]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Usecase subcommittee meeting of 30/4/2018 - the summary

[Alla Goldner]

Feedback for Casablanca priorities from China Mobile was received and added 
under

https://wiki.onap.org/display/DW/Casablanca+goals

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E1FE.20144B20]

From: Alla Goldner
Sent: Tuesday, May 01, 2018 4:46 PM
To: onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org; 
onap-...@lists.onap.org
Subject: Usecase subcommittee meeting of 30/4/2018 - the summary

Hi all,

Thanks to all meeting attendants!

Here is the summary:

1. We reviewed Edge automation presentation by Ramki and, specifically, what is 
planned for Casablanca
2. We reviewed EUAG feedback (Vodafone, Verizon, AT, Bell, Orange) regarding 
their priorities for Casablanca. I put those requirements under 
https://wiki.onap.org/display/DW/Casablanca+goals . The bottom line is that 
platform quality seem to be significantly more important that functional 
enrichment of the platform at this point, still.
a. This information, along with E2E use cases proposals will serve as input for 
TSC decision on the E2E use cases approval (May 10th)

Our next meeting will be dedicated to review of E2E use cases before bringing 
them for TSC approval next week.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E1FE.20144B20]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee meeting of 30/4/2018 - the summary

[Alla Goldner]

Hi all,

Thanks to all meeting attendants!

Here is the summary:

1. We reviewed Edge automation presentation by Ramki and, specifically, what is 
planned for Casablanca
2. We reviewed EUAG feedback (Vodafone, Verizon, AT, Bell, Orange) regarding 
their priorities for Casablanca. I put those requirements under 
https://wiki.onap.org/display/DW/Casablanca+goals . The bottom line is that 
platform quality seem to be significantly more important that functional 
enrichment of the platform at this point, still.
a. This information, along with E2E use cases proposals will serve as input for 
TSC decision on the E2E use cases approval (May 10th)

Our next meeting will be dedicated to review of E2E use cases before bringing 
them for TSC approval next week.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E16B.E45C7090]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Casablanca use cases: Feedback received from EUAG (Service Providers) so far

[Alla Goldner]

 ONAP components and 
their features to work reliably.
  *   For service providers, this is a major undertaking - so slightly less of 
a short-term, immediate need.

5. 5G Use case Items

  *   PNF support primarily from our point of view, although ONAP partially 
supports this - it should definitely be improved.
  *   5G is less of an immediate need than the other use cases, given ONAP 
could benefit from several improvements to existing functionality.

Additional input from Bell:

We should focus on completing the existing feature set rather than starting 
something new like 5g - making the features work for real so that more 
operators can actually start using the platform. Then 5g or other are just use 
cases.

We should put a very little percentage in adding use cases, especially if we 
are hard coding policies and other parameters just so that he use case is 
working at the end of a release. Fix vFW, fix vCPE, fix VoLTE, do not add. The 
ultimate goal is to have a platform on which any use case can be deployed.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3E06B.3B567280]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Meeting agenda for 30/4/2018

[Alla Goldner]

Hi all,

Here is agenda for the next week's meeting:


1.   Edge Automation requirements for Casablanca

2.   End User Advisory Group priority of requirements for Casablanca

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3DE5E.B2D06410]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee meeting 23/04/2018: the summary

[Alla Goldner]

Hi,

Thanks to all meeting attendants!

During Usecase subcommittee meeting today, we hosted Service Providers 
representing End User Advisory Group.
We presented 5G use cases : PNF, network slicing, Optimization; Edge Automation 
and OSAM.

AI 1: OSAM team to check dependency on PNF support i.e. whether PNF support 
provided in Beijing is sufficient or enhancements are needed.

AI 2: All task forces: provide link to the most updated high level requirements 
in wiki by tomorrow, I will then provide them to EUAG.

AI 3: platform requirements and what is needed for ONAP platform deployability. 
All - please provide your questions to EUAG.

AI 4: Upon receiving the links, EUAG members will consider use cases and 
provide us with their feedback by the next week.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3DB3E.DF3A1FA0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] FW: Our meeting next Monday 23/4/2018: the agenda

[Alla Goldner]

Hi all,

For your information, the upcoming Usecase subcommittee meeting will be 
dedicated to Casablanca priorities discussions with Service Providers' 
representatives.

You all are invited!

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3D8A7.FD685E90]

From: onap-usecasesub-boun...@lists.onap.org 
[mailto:onap-usecasesub-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, April 20, 2018 1:03 PM
To: onap-usecase...@lists.onap.org
Subject: [Onap-usecasesub] Our meeting next Monday 23/4/2018: the agenda

Hi all,

Our meeting next week will be dedicated to discussion with SP representatives 
who will serve on End User Advisory Committee, once officially set up.
We will discuss their view on priorities for Casablanca and, on the other side, 
what is currently on our table in the preparation phase.

Use cases leaders - please be ready with your presentations.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3D8A7.FD685E90]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Usecase subcommittee meeting 09/04/2018: the summary

[Alla Goldner]

Thanks, Ramki,

Thus, discussions upcoming Monday will be limited to :

 a. PNF support (whatever is not covered in Beijing)
  b. Optimization and OOF
  c. Network slicing


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3D166.E87864F0]

From: Ramki Krishnan [mailto:ram...@vmware.com]
Sent: Wednesday, April 11, 2018 1:36 AM
To: Alla Goldner <alla.gold...@amdocs.com>; onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: RE: Usecase subcommittee meeting 09/04/2018: the summary

Hi Alla,

Thanks for including the Edge Automation work in the next week's agenda. Based 
on the last meeting, the consensus was to update the use case subcommittee in 
the week on April 30th. Our work is progressing well 
(https://wiki.onap.org/display/DW/Edge+Automation+through+ONAP) and looking 
forward to community participation.

--
Thanks,
Ramki

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Tuesday, April 10, 2018 7:19 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Subject: [onap-discuss] Usecase subcommittee meeting 09/04/2018: the summary

Hi all,

Thanks to all meeting's attendants!

Here is the meeting's summary:


  1.  Agreed that we have time till end of April to discuss E2E use case 
candidates for Casablanca, which will be followed by formal approval
 *   All approvals will be conditional pending final functional 
requirements extraction and generalization, and agreements on 
functionality/assigned resources with each one of involved projects
 *   Approvals will also be based on input received from a group of ONAP 
Service Providers regarding their deployment requirements
  2.  Use case description should be as full as possible e.g. not only "5G" but 
"5G Network slicing" with initial flows, potential involved companies, business 
need description etc.
 *   The target is to have eventually all generalized functional 
requirements defined by the same template as created and used for HPA: 
https://wiki.onap.org/display/DW/Hardware+Platform+Enablement+In+ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Hardware-2BPlatform-2BEnablement-2BIn-2BONAP=DwMFAg=uilaK90D4TOVoH58JNXRgQ=bCmYL3bSEMwtZqPWSHINtvRWIlUeuM66MeOgvaAueQU=DDbZm_YJUFm-XgXwT7yuSx4zZVXNvX0iG_D0_G-MuGI=BP8c7HhVa3yZk7g1sQc1uztamoXDb930V5KCIPQoTKg=>
  3.  Next week's meeting will be dedicated to 5G related use cases discussions 
and what can realistically go into Casablanca scope, specifically
 a. PNF support (whatever is not covered in Beijing)
  b. Optimization and OOF
  c. Network slicing
  d. Edge Automation




Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3D166.E87864F0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwMFAg=uilaK90D4TOVoH58JNXRgQ=bCmYL3bSEMwtZqPWSHINtvRWIlUeuM66MeOgvaAueQU=DDbZm_YJUFm-XgXwT7yuSx4zZVXNvX0iG_D0_G-MuGI=NoFnr7GEQyahcIlsti4fW6i1ar8cC_yCQ6J6enJJwgk=>
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] distribution lists

[Alla Goldner]

Hi all,

As I already sent several emails last week in this regard, it is important to 
emphasize that:


1.   We should try to avoid using of private email list distributions, 
while discussing use cases/functional requirements. This way we will allow 
anyone interested to participate in those discussions and support transparency 
of those discussions

2.   As a result, we should use a single list of members onap-usecasesub 
for communicating any information related to all use cases/functional 
requirements discussions

a.   This would also prevent the situations e.g. one we are facing starting 
from the last week, related to Edge Automation requirements, when all emails 
got blocked due to a very long distribution lists plus onap-usecasesub list, 
and I had/have to release those on a permanent basis

3.   All people interested in use cases/functional requirements discussions 
- please subscribe to onap-usecasesub 
https://lists.onap.org/mailman/listinfo/onap-usecasesub

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3CE5B.C40F01E0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Action Plan towards Casablanca

[Alla Goldner]

Thanks, Mazin,

We will definitely not slow down as time issue is becoming critical and try to 
come up with our proposal of realistic scope per defined prioritized areas.

We also need to define what percentage of work in Casablanca would be dedicated 
by the projects to leftovers from Beijing and to extension of S3P work.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3C8F9.A7BB05A0]

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Saturday, March 31, 2018 3:56 AM
To: Alla Goldner <alla.gold...@amdocs.com>
Cc: onap-usecase...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-...@lists.onap.org P <onap-...@lists.onap.org>
Subject: Re: [onap-discuss] Action Plan towards Casablanca
Importance: High

Thanks Alla for the summary.

Here is what we agreed to at the TSC meeting.
There are three work plans for Casablanca. The theme is increase deployability 
of ONAP.

1. Functional requirements and use cases. We agreed to establish an end-user 
advisory committee that will be driven by the equivalent of product managers 
across operators who will help to set priorties that can accelerate 
deployability of ONAP. The work of your committee on use cases and 5G 
solutioning will help to provide options for the end-user advisory committee.

2. Platform Evolution. This includes some of your list items
a. S3P new target (including code coverage)
b. Backward compatibility
c. Improve modularity and simplicity of using ONAP.

3. Broader learning and education of ONAP.
The Education committee will develop a proposal for weekly Webinars.

I am working to assemble 1. My hope is to have 3-4 operators signed up next 
week so they can meet with your team and get the work started.
Phil will make that committee official as a subgroup under LFN end-user 
advisory committee. Until then, let’s not slow down.

We also discussed what we want to accomplish prior to the Beijing meeting in 
June. We will discuss that further at the TSC meeting this week,
and also vote on the release planning for Casablanca.

Great progress by the team on Beijing. Most projects hit M4 already. Momentum 
is amazing.

Mazin


On Mar 30, 2018, at 5:03 AM, Alla Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> wrote:

Hi all,

I re-attach the picture which describes high level priorities as discussed 
during the meeting called by me on Wednesday evening. I understand this was 
discussed in details also during the TSC meeting.

What we had on the table was:

1.   Leftovers from Beijing remained from :
a.   Functional requirements (PNF, Scaling, Change Management, HPA)
b.  Leftovers from S3P support
2.   New S3P requirements
3.   All new use cases and requirements coming to Casablanca (you could see 
the variety during our meeting on Monday)
4.   A different projects proposed extensions
5.   Possibly, new projects potentially proposed for Casablanca
6.   Architecture evolution related modifications

Clearly, this whole scope will not be accomplished in a single Release, this is 
why we needed to see what would be areas of priorities.
Clearly, we may get additional input from the Service Providers, as discussed, 
but in the mean time, in order to make progress, let’s assume these are the 
priorities.

Now, in order to do constructive work and move forward towards Casablanca 
Release, specifically for Usecase subcommittee, we need to see what ongoing 
work matches the Deployability goal as defined and, additionally, extract 
generic functional requirements from the use cases brought to the table/see if 
some requirements brought to the table can be generalized.

I identify the following areas for our activities out of proposed prioritized 
areas:

1.   Leftovers of functional requirements from Beijing – as scope is pretty 
clear, I would say that at this point the required actions are:
a.   Have a detailed list of functionality proposed to move to Casablanca
b.  Negotiate with involved projects on this functionality and resources 
assigned to these activities

2.   All 5G related requirements:
a.   A realistic plan of what can be implemented in Casablanca (a subset of 
functionality discussed so far), based on available/emulated VNFs/PNFs, 3GPP 
standards’ availability etc. with flows, needed resources, affected modules

3.   All external controllers related activities – this work should be 
generalized and common principle should be developed on what we bring to 
Casablanca in such a way that it can be utilized by several use cases. Some 
initial work on this was also done in Beijing.
a.   A concrete proposal on what we bring to Casablanca should be worked on 
and brought

I suggested end of April as a deadline for the conditional approval of the 
scope as discussed above. (Conditional is because some more detailed 
discussions with the projects after this may rule out/or add some of the 
requ

Re: [onap-discuss] [Onap-usecasesub] Kickstart Change Management discussion for Casablanca

[Alla Goldner]

Yuan's comment on Change management extracted from his email:


Change management: To me, it is a quite clear requirement of "live upgrading", 
change management is too general to be understood. Most of teleco legacy 
equipments have thier own live upgrading capability and correspondent approach 
based on thier own software and hardware architecture. From my own developing 
experience, live upgrading is the most complicated part in teleco software. 
Different data storage policy and synchronization mechanism need different 
preparation during live upgrading. I believe virtualized infrastructure might 
provide some possibility to reduce the complicity of live upgrading but it is 
still complex when we think about data of the software which is deeply coupled 
with VNF internal approach.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3C106.06636C60]

From: onap-usecasesub-boun...@lists.onap.org 
[mailto:onap-usecasesub-boun...@lists.onap.org] On Behalf Of MAHIMKAR, AJAY 
(AJAY)
Sent: Wednesday, March 21, 2018 11:12 AM
To: onap-usecase...@lists.onap.org; onap-discuss@lists.onap.org
Subject: [Onap-usecasesub] Kickstart Change Management discussion for Casablanca

Hi all:

Here is an email thread to kick-start discussion on Change Management for ONAP 
Casablanca.

Thanks,

-  Ajay
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Schedule Update for ONS

[Alla Goldner]

Kenny,

As for the TSC meeting: as Passover holidays start on Friday, Israeli 
participants will leave on Thursday morning (this is the latest we can do to be 
at home by the time the holiday starts, though without appropriate holidays 
preparations due to ONS :().
Is here any possibility to move TSC meeting to Wednesday?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3B77A.9BE3FF60]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: Friday, March 09, 2018 1:35 AM
To: onap-discuss <onap-discuss@lists.onap.org>
Subject: [onap-discuss] Schedule Update for ONS

Just a quick update about the LFN Developer Forum schedule at ONS-

The plenary sessions have been chosen and the Events team is currently 
notifying speakers.  The Developer Forum schedule should be published on the 
LFN wiki by tomorrow. LFN Developer Forum Plenary Session 
Proposals<https://wiki.lfnetworking.org/display/LN/LFN+Developer+Forum+Plenary+Session+Proposals?src=contextnavpagetreemode>

If you submitted a proposal what was not selected for the plenary sessions that 
you believe would be an equally good topic for an ONAP specific breakout 
session, please add it to the ONAP Breakout Page  as soon as possible so the 
that Program Committee can work on the scheduling. ONAP Project Specific 
Breakouts<https://wiki.lfnetworking.org/display/LN/ONAP+Project+Specific+Breakouts>

The TSC meeting itself will still occur on Thursday morning as usual. Please 
add TSC meeting topics to the upcoming agenda page just the same as always. TSC 
2018-03-29 Meeting Agenda 
(ONS)<https://wiki.onap.org/pages/viewpage.action?pageId=25439855>



Best Regards,
-kenny

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

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee - agenda for 26/2/2018

[Alla Goldner]

Hi all,

Here is agenda for the upcoming meeting:


1.   Status of Beijing functional requirements development

2.   Showcasing of Beijing requirements: discussion with Integration.

3.   Discussion - how we make sure in the future (in Casablanca) that 
requirements are clear, closed and proceed for M1/M2 etc. Any suggestion is 
welcomed

4.   Casablanca requirements - so far, we've reviewed OSAM. Any additional 
initial requirements are welcome for discussion. Also, let's start discussion 
on Casablanca's focus and direction


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3AC23.A1ECA630]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Invitation: [usecase] Subcommittee (updated Jan. 30, 2018) @ Weekly from 7am to 8am on Monday from Mon Feb 12 to Mon Jan 21, 2019 (PST) (alla.gold...@amdocs.com)

[Alla Goldner]

Hi all,

I will ask to cancel the next week’s Usecase subcommittee meeting due to Spring 
Festival Golden Week Holidays in China.

Those celebrating – have a GREAT HOLIDAYS WEEK!!!

 Best regards,

Alla Goldner

Open Network Division
Amdocs Technology





-Original Appointment-
From: ONAP Meetings and Events 
[mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com]
Sent: Wednesday, January 31, 2018 3:12 AM
To: ONAP Meetings and Events; Alla Goldner; onap-discuss@lists.onap.org
Subject: Invitation: [usecase] Subcommittee (updated Jan. 30, 2018) @ Weekly 
from 7am to 8am on Monday from Mon Feb 12 to Mon Jan 21, 2019 (PST) 
(alla.gold...@amdocs.com)
When: Monday, February 19, 2018 7:00 AM-8:00 AM America/Los_Angeles.
Where: https://zoom.us/j/655429955


more details 
»<https://www.google.com/calendar/event?action=VIEW=NWJiaXZ1MTgxNjltZHMxa3QyZzhra2x0M2MgYWxsYS5nb2xkbmVyQGFtZG9jcy5jb20=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzBkMmMyY2I4MjVlZWE5OWYyN2M3NjVmYWYxZDgxOTBmYmZjMTQzYw=America/Los_Angeles=en>

[usecase] Subcommittee (updated Jan. 30, 2018)
When
Weekly from 7am to 8am on Monday from Mon Feb 12 to Mon Jan 21, 2019 
Pacific Time

Where
https://zoom.us/j/655429955 
(map<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F655429955=D=2=AFQjCNHDg145xh6q3mt294pIjwPzvH_vDA>)

Calendar
alla.gold...@amdocs.com

Who
•
kp...@linuxfoundation.org - creator

•
alla.gold...@amdocs.com

•
onap-discuss@lists.onap.org



Hi there,

ONAP Meeting 2 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/655429955<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F655429955=D=2=AFQjCNHDg145xh6q3mt294pIjwPzvH_vDA>
Or iPhone one-tap :
US: +16699006833,,655429955# or +16465588656,,655429955#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 
880 1246 (Toll Free)
Meeting ID: 655 429 955
International numbers available: 
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3DCqsAwHx4CSyRanCfPHKBvf6Vslgcsn86=D=2=AFQjCNHmeO65V_ncgXTJyNNL6g4uKzSNyg>




Going?   All events in this series:   
Yes<https://www.google.com/calendar/event?action=RESPOND=NWJiaXZ1MTgxNjltZHMxa3QyZzhra2x0M2MgYWxsYS5nb2xkbmVyQGFtZG9jcy5jb20=1=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzBkMmMyY2I4MjVlZWE5OWYyN2M3NjVmYWYxZDgxOTBmYmZjMTQzYw=America/Los_Angeles=en>
 - 
Maybe<https://www.google.com/calendar/event?action=RESPOND=NWJiaXZ1MTgxNjltZHMxa3QyZzhra2x0M2MgYWxsYS5nb2xkbmVyQGFtZG9jcy5jb20=3=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzBkMmMyY2I4MjVlZWE5OWYyN2M3NjVmYWYxZDgxOTBmYmZjMTQzYw=America/Los_Angeles=en>
 - 
No<https://www.google.com/calendar/event?action=RESPOND=NWJiaXZ1MTgxNjltZHMxa3QyZzhra2x0M2MgYWxsYS5nb2xkbmVyQGFtZG9jcy5jb20=2=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzBkMmMyY2I4MjVlZWE5OWYyN2M3NjVmYWYxZDgxOTBmYmZjMTQzYw=America/Los_Angeles=en>
more options 
»<https://www.google.com/calendar/event?action=VIEW=NWJiaXZ1MTgxNjltZHMxa3QyZzhra2x0M2MgYWxsYS5nb2xkbmVyQGFtZG9jcy5jb20=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tMzBkMmMyY2I4MjVlZWE5OWYyN2M3NjVmYWYxZDgxOTBmYmZjMTQzYw=America/Los_Angeles=en>
Invitation from Google Calendar<https://www.google.com/calendar/>

You are receiving this courtesy email at the account alla.gold...@amdocs.com 
because you are an attendee of this event.
To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings for 
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn 
More<https://support.google.com/calendar/answer/37135#forwarding>.
 << File: invite.ics >>

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ONS Registration Discount for active developers and leadership

[Alla Goldner]

Phil,

Thanks a lot for this extra-effort!


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D39786.304F1FA0]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Saturday, January 27, 2018 7:48 AM
To: onap-tsc <onap-...@lists.onap.org>; onap-discuss@lists.onap.org
Subject: [onap-discuss] ONS Registration Discount for active developers and 
leadership

Hello ONAP community:

Active developers and project leadership are strongly encouraged to participate 
in the ONS event.  Monday and Tuesday will be exceptionally valuable and the 
rest of the week can be used to either learn about something new going on in 
the industry and/or continue the discussions and work that are started on 
Monday and Tuesday.

To facilitate as much developer participation as possible, we have arranged for 
a 50% (ie $600 for the early-bird registration) discount to individuals meeting 
any one of the following criteria:

- You are an active contributor to ONAP with a gerrit ID and have submitted a 
patch within the last 6 months...and prior to receiving this email.

- You are an active committer and have reviewed a code contribution within the 
past 6 months and prior to receiving this email.

- You are a current TSC member

- You are a current PTL

- You are a Subcommittee Chairperson

- You are the ONAP Release Manager.

If you satisfy one of the criteria above, please do the following to register 
for ONS

  *   Please click 
here<https://www.regonline.com/registration/checkin.aspx?EventId=2087601=0==1>
 to register for the conference
  *   Select "Attendee Registration"
  *   Enter the discount code: ONSDVE18
My team will be reviewing everyone that uses this code, so please don't use it 
if you don't qualify.  We will void any registration made that does not meet 
the criteria.

Best regards and I look forward to seeing everyone at ONS,

Phil.
--
Phil Robb
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Clarifying the plan for developer gathering at ONS

[Alla Goldner]

Hi Phil,

Thanks a lot for this information!

As we know, ONS attendants have to pay registration fees.
What is arrangement for those coming to attend ONAP meeting?


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D394EC.DBC882A0]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Phil Robb
Sent: Tuesday, January 23, 2018 8:50 PM
To: onap-tsc <onap-...@lists.onap.org>; onap-discuss@lists.onap.org; Raymond 
Paik <rp...@linuxfoundation.org>
Subject: [onap-tsc] Clarifying the plan for developer gathering at ONS

Hello ONAP developers and TSC members:

I wanted to provide some clarity on the activities and timeframe we have to 
gather during ONS.

The developer event during ONS week will be from 8:00am to 6:00pm on Monday, 
March 26th, and 8:00am to 12:00 noon on Tuesday, March 27th.  From requests we 
have received we had also been investigating the possibility to extend the 
event into the proceeding Sunday, but we've determined that such an extension 
is not going to be possible.  That said, we still have the Monday/Tuesday time 
for formal presentations, as well as break out rooms and a developer lounge for 
continued meetings, discussions, and hacking at ONS during the rest of the week.

As we've mentioned before, we would like to take advantage of the fact that the 
communities from the different projects will be in the same place at the same 
time.  As such, we encourage you to propose sessions that can further 
cross-collaboration among the LFN projects.  We also recognize that there are 
plenty of project-specific topics that need to be discussed.  Please also 
propose those sessions for this event.

With the LFN formally announced today, we are working to get the LFN wiki site 
up and running as quickly as possible.  One of the first uses for this site 
will be the location for submitting your proposed talks and presentations for 
the developer event at ONS.  We apologize that it is not up quite yet but it 
will be up within the next 2 or 3 days.

Once the site is up, Ray Paik (cc-ed) will send out an email to all communities 
on where to find it along with a call-for-presentations for you to post your 
discussion and presentation topics.  Between February 9th and February 15th, we 
will convene the TAC representatives from the LFN projects to review the 
submissions and to form an outline/framework for the developer event, giving 
time for cross-project discussions, project-specific sessions, and a TAC 
meeting.  From there, we will work with each project TSC to prioritize 
project-specific sessions during the event.

I am looking forward to this first-of-its-kind event and the breadth and depth 
of discussions we will have during this week.  Please be preparing your topics 
over the coming days and submit them to the LFN wiki once it is live.

Best regards,

Phil.
--
Phil Robb
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Beijing M1: Status of functional requirements

[Alla Goldner]

Hi Mazin,

Sure, we will add this information to the description.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D392EC.566F2CA0]

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Sunday, January 21, 2018 3:15 PM
To: Alla Goldner <alla.gold...@amdocs.com>
Cc: onap-...@lists.onap.org P <onap-...@lists.onap.org>; 
onap-...@lists.onap.org; onap-discuss@lists.onap.org; 
onap-usecase...@lists.onap.org
Subject: Re: [onap-discuss] Beijing M1: Status of functional requirements

Thanks Alla. That is great progress, and appreciate the hard work by everyone.
Have the software architectures worked on the detailed designs of those 
requirements
with the PTLs to ensure nothing is lost in translation?

Can you add to the website the services that will be tested to evaluate 
completions of those requirements.

Mazin




On Jan 18, 2018, at 1:08 PM, Alla Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> wrote:

Hi all,

As per today’s M1 dedicated TSC meeting and outcomes of the work done by 
Usecase subcommittee along with relevant PTLs,

Here is the most updated status of the functional requirements: 
https://wiki.onap.org/display/DW/Beijing+Functional+Requirements<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Beijing-2BFunctional-2BRequirements=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=7VBK7vn4mMMbbTBo_UbIrby0L3gd_KvI_MskXwqLW-k=oTidhLg49Z6O_9zviXx3fusoAmFtnvgaAJ1TYwIbm3I=>

1.   Thus, we assume, the following functional requirements are part of 
Beijing Release scope:

a.   HPA
b.  Change Management
c.   Manual scaling
d.  PNF support

All, please indicate if you see any issues with that.

2.   Auto scaling status: APPC, CLAMP and Policy could not commit due to 
lack of resources.

All, please indicate in case some additional resources can be dedicated from 
your side to help the above mentioned projects with Auto scaling requirement 
support.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=7VBK7vn4mMMbbTBo_UbIrby0L3gd_KvI_MskXwqLW-k=IayIFfpFwRaM2wxAHs8JbwKxe9_7ufbotiJ9jkkxtrE=>
___
onap-discuss mailing list
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=7VBK7vn4mMMbbTBo_UbIrby0L3gd_KvI_MskXwqLW-k=Y63nXwhDh5uYEaYn9pj-mMgdhOa5KZzTbaZj3NWvzgg=

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Beijing M1: Status of functional requirements

[Alla Goldner]

Hi all,

As per today's M1 dedicated TSC meeting and outcomes of the work done by 
Usecase subcommittee along with relevant PTLs,

Here is the most updated status of the functional requirements: 
https://wiki.onap.org/display/DW/Beijing+Functional+Requirements


1.   Thus, we assume, the following functional requirements are part of 
Beijing Release scope:


a.   HPA

b.  Change Management

c.   Manual scaling

d.  PNF support

All, please indicate if you see any issues with that.


2.   Auto scaling status: APPC, CLAMP and Policy could not commit due to 
lack of resources.

All, please indicate in case some additional resources can be dedicated from 
your side to help the above mentioned projects with Auto scaling requirement 
support.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D39097.AC5F6230]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

[Alla Goldner]

+1

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D38B8F.A54F05C0]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E 
(MAZIN E)
Sent: Friday, January 12, 2018 5:16 AM
To: MAHER, RANDA <rx1...@att.com>
Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

+1

Please add the candidate’s company plus existing committers.



On Jan 11, 2018, at 6:57 PM, MAHER, RANDA 
<rx1...@att.com<mailto:rx1...@att.com>> wrote:

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

Dear TSC,

Please consider request below for Committer Promotion for APPC project.

https://wiki.onap.org/pages/viewpage.action?pageId=22251669<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D22251669=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y=NXGqSa5NxTHo7zyxUrPP49eLYsmXzI4yh64s3B4oM5A=8xeTPTAsHN34YGfDkmGCT1Kx-ZYfUGIVlWqjAYXGrLM=>

One of our existing committers has indicated that he will  step down from 
Committer to Contributor role.
Existing Committers have all voted +1 on Taka Cho promotion to Committer.

Thanks, Randa
APPC PTL
___
ONAP-TSC mailing list
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y=NXGqSa5NxTHo7zyxUrPP49eLYsmXzI4yh64s3B4oM5A=Evsqbp4rRCVLOh5p5fjHYs14lo95L06AtvAB_oZldfM=

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-usecasesub] seem to be the old known issue (when we reschedule our meetings ) "Host has another meeting in progress"

[Alla Goldner]

It works now, all - please connect.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D384BA.67EA05D0]

From: onap-usecasesub-boun...@lists.onap.org 
[mailto:onap-usecasesub-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Wednesday, January 03, 2018 5:31 PM
To: onap-usecase...@lists.onap.org; Kenny Paul <kp...@linuxfoundation.org>
Subject: [Onap-usecasesub] seem to be the old known issue (when we reschedule 
our meetings ) "Host has another meeting in progress"

Kenny, any way to assist?

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D384BA.67EA05D0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Invitation: [usecase] Sub-Committee (one-off bridge number) @ Wed Jan 3, 2018 7:30am - 8:30am (PST) (onap-discuss@lists.onap.org)

[Alla Goldner]

Kenny is trying to see what can be done, on a call with him now

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D384B9.75A6ACB0]

From: Vul, Alex [mailto:alex@intel.com]
Sent: Wednesday, January 03, 2018 5:36 PM
To: kp...@linuxfoundation.org; Alla Goldner <alla.gold...@amdocs.com>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Invitation: [usecase] Sub-Committee (one-off bridge 
number) @ Wed Jan 3, 2018 7:30am - 8:30am (PST) (onap-discuss@lists.onap.org)

Can’t get into the meeting… Help!!!

-Original Appointment-
From: ONAP Meetings and Events 
[mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com]
Sent: Thursday, December 21, 2017 9:00 AM
To: ONAP Meetings and Events; 
alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] Invitation: [usecase] Sub-Committee (one-off bridge 
number) @ Wed Jan 3, 2018 7:30am - 8:30am (PST) 
(onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>)
When: Wednesday, January 3, 2018 7:30 AM-8:30 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/781963645


more details 
»<https://www.google.com/calendar/event?action=VIEW=MGlwZWNlb2JtdjZldG1oZDNsczJobHZobjAgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZDFhZTA5NjkxYTY3YTFiM2IwYmJlNmE2MGM3OTI0YTM2NWE2NTVkYw=America/Los_Angeles=en>
[usecase] Sub-Committee (one-off bridge number)
When

Wed Jan 3, 2018 7:30am – 8:30am Pacific Time



Where

https://zoom.us/j/781963645 
(map<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F781963645=D=2=AFQjCNH8MSryx68Awcb_e1vFdvQcQW_1Yg>)



Calendar

onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>



Who

•

kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org> - creator



•

alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>



•

onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>







Note bridge/host change for this meeting.

ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/781963645<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fj%2F781963645=D=2=AFQjCNH8MSryx68Awcb_e1vFdvQcQW_1Yg>
Or iPhone one-tap :
US: +16699006833,,781963645# or +16465588656,,781963645#
Or Telephone:
Dial(for higher quality, dial a number based on your current location)：
US: +1 669 900 6833 or +1 646 558 8656 or +1 877 369 0926 (Toll Free) or +1 855 
880 1246 (Toll Free)
Meeting ID: 781 963 645
International numbers available: 
https://zoom.us/zoomconference?m=v72irFBsz1OedLM5BciLHglq1CBwjFCD<https://www.google.com/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3Dv72irFBsz1OedLM5BciLHglq1CBwjFCD=D=2=AFQjCNEsgQWbGomUskbk5Wt1EKVwrckZTg>



Going?   
Yes<https://www.google.com/calendar/event?action=RESPOND=MGlwZWNlb2JtdjZldG1oZDNsczJobHZobjAgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=1=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZDFhZTA5NjkxYTY3YTFiM2IwYmJlNmE2MGM3OTI0YTM2NWE2NTVkYw=America/Los_Angeles=en>
 - 
Maybe<https://www.google.com/calendar/event?action=RESPOND=MGlwZWNlb2JtdjZldG1oZDNsczJobHZobjAgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=3=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZDFhZTA5NjkxYTY3YTFiM2IwYmJlNmE2MGM3OTI0YTM2NWE2NTVkYw=America/Los_Angeles=en>
 - 
No<https://www.google.com/calendar/event?action=RESPOND=MGlwZWNlb2JtdjZldG1oZDNsczJobHZobjAgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=2=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZDFhZTA5NjkxYTY3YTFiM2IwYmJlNmE2MGM3OTI0YTM2NWE2NTVkYw=America/Los_Angeles=en>
more options 
»<https://www.google.com/calendar/event?action=VIEW=MGlwZWNlb2JtdjZldG1oZDNsczJobHZobjAgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn=NzIjbGludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxlbmRhci5nb29nbGUuY29tZDFhZTA5NjkxYTY3YTFiM2IwYmJlNmE2MGM3OTI0YTM2NWE2NTVkYw=America/Los_Angeles=en>

Invitation from Google Calendar<https://www.google.com/calendar/>
You are receiving this courtesy email at the account 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> because you are 
an attendee of this event.
To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings for 
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn 
More<https://support.google.com/calendar/answer/37135#forwarding>.

<< File: invite.ics 

Re: [onap-discuss] [Onap-usecasesub] [integration] ONAP S3P definition and matrix

[Alla Goldner]

Hi Jason, Helen,

I fully agree with Helen and her proposal of having a smaller group to guide 
S3P requirements introduction into Beijing ,

If we count only on projects from now on to define their functionality aligned 
with S3P per agreed goals, we may end up with each project understanding (and 
implementing) those requirements differently, thus we may not have Beijing 
Release aligned with those requirements as a whole.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D38460.D0756E00]

From: onap-usecasesub-boun...@lists.onap.org 
[mailto:onap-usecasesub-boun...@lists.onap.org] On Behalf Of Yunxia Chen
Sent: Wednesday, January 03, 2018 1:21 AM
To: Jason Hunt <djh...@us.ibm.com>
Cc: onap-...@lists.onap.org; onap-discuss <onap-discuss@lists.onap.org>; 
onap-usecase...@lists.onap.org
Subject: Re: [Onap-usecasesub] [onap-discuss] [integration] ONAP S3P definition 
and matrix

Hi, Jason,
I agree with you that each project should have their own criteria. But after 
talking with some projects, I am not sure they have a clear idea how those high 
level “definition” could be reflected into their projects, (they need more help 
on those); and some S3P doesn’t make too much sense for them at this point, for 
example, (let’s also use A), does it make sense to request A to use 
metric for updating events if the bottleneck is at infrastructure level, 
querying the cloud?

For the security requirement, are we really want ALL calls are “role-based 
access control and authorization”? I am not sure all project PTLs have realized 
the impact of this one for them. ☺

I will talk to Benchmark team to see what they could do for Beijing release.

Regards,

Helen Chen

From: Jason Hunt <djh...@us.ibm.com<mailto:djh...@us.ibm.com>>
Date: Tuesday, January 2, 2018 at 2:58 PM
To: Helen Chen 00725961 <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>
Cc: "onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>" 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>, onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, 
"onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>" 
<onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>>
Subject: Re: [onap-discuss] [integration] ONAP S3P definition and matrix

Hi Helen,

Those details have not been defined.  The thought was for many of the criteria 
that the individual projects are in the best position to identify criteria 
appropriate to their project.

So, for performance, as an example, maybe SO would identify and measure a 
criteria around request handling time, whereas AAI might use a metric around 
events received per second.  (These are just examples).

For stability, each project should identify & create the appropriate test 
transactions that would exercise 80% of their code.  Then those tests would be 
run over a 72 hour period & monitored for any component failures.

My hope is that the Benchmark team will be able to assist the project teams 
with the performance and stability testing.

For resiliency, the level 2 criteria just says that there has to be automated 
failure detection and rerouting with no other qualifications on how 
"gracefully" that occurs.  For that level, the teams should just gather how 
many requests are lost when failure happens under load (for stateless 
components), and gather what sort of data loss occurs when failure happens 
under load (for stateful components).


Regards,
Jason Hunt
Executive Software Architect, IBM

Phone: 314-749-7422
Email: djh...@us.ibm.com<mailto:djh...@us.ibm.com>
Twitter: @DJHunt




From:Yunxia Chen <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>
To:Jason Hunt <djh...@us.ibm.com<mailto:djh...@us.ibm.com>>
Cc:"onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>" 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>, onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, 
"onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>" 
<onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>>
Date:01/02/2018 04:45 PM
Subject:Re: [onap-discuss] [integration] ONAP S3P definition and matrix




Hi, Jason,

Thanks for the fast turnaround. I am looking for something more concrete and 
specific, for example,
Performance: What exactly the criteria identified?
• Speed of service provisioning?
• How many particular operations can be processed in a second?
• How many concurrent operations can be run in parallel without 
degradation?
Stability:
• Longevity tests? 72 hours? … What does 72 hour platform level soak 
w/random transactions mean here?
•

[onap-discuss] Usecase subcommittee meeting during f2f meeting

[Alla Goldner]

Hi all,

The Usecase subcommittee meeting will take place 1:15 to 3:15 in the room 175.

Sorry for all confusion caused by project reviews taking longer than expected.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D37460.3C1ECBD0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Request to consider reschedule the weekly callsfor DST time changes

[Alla Goldner]

+1

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3644D.502B7100]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Thursday, November 23, 2017 10:51 AM
To: meng.zhaoxi...@zte.com.cn; zhao.huab...@zte.com.cn
Cc: ma...@research.att.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Request to consider reschedule the weekly callsfor 
DST time changes

+1
As I have been staying over mid-nights consecutively this week, and I feel the 
pain deeply.

Lingli

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>
Sent: 2017年11月23日 16:34
To: zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
Cc: ma...@research.att.com<mailto:ma...@research.att.com>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Request to consider reschedule the weekly callsfor 
DST time changes


+1


Original Mail
Sender: zhaohuabing10201488
To:  <ma...@research.att.com<mailto:ma...@research.att.com>>;
CC:  <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;
Date: 2017/11/21 15:11
Subject: Re: [onap-discuss]Request to consider reschedule the weekly callsfor 
DST time changes

Hi Mazin, Lingli and all,



May I suggest applying this principle to all the community meetings? I noticed 
that there are a couple of other meetings that have the same problem.



Thanks,

Huabing




Sender:  <ma...@research.att.com<mailto:ma...@research.att.com>>;
To:  <denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>>;
CC:  <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;
Date: 2017/11/21 10:38
Subject: Re: [onap-discuss] Request to consider reschedule the weekly callsfor 
DST time changes
I am very supportive. We agreed to avoid 12 mid night to 6am.

Kenny, please advise of when we can make the change. TSC meetings
should go back to 1 hour.

Mazin



On Nov 20, 2017, at 8:45 PM, Lingli Deng 
<denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>> wrote:

Hi Kenny and Mazin,

As a result of the DST time change, the current time slot for ONAP calls are 
technically one-hour later for regions that does not follow the practice in 
winter, like China.
Hence a lot of them, including TSC weekly call, are now spanning after 
mid-night.
As we requested last week on the TSC call, would it be possible to reschedule 
the weekly calls 30 minutes earlier, so that people could share the burden of 
accommodating the change?

Thanks,
Lingli



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee 20/11/2017 meeting - the summary

[Alla Goldner]

Hi all,

Thanks to all meeting's participants!

Here is the summary:


1.   Alla thanked all Usecase subcommittee members and Integration team 
members greatly contributed to the success of Amsterdam Release!!!

 2.   R2 requirements
a.E-vCPE requirements were presented by Luman. This will follow by 
email discussion which Luman will initiate ASAP, describing the problem the 
requirements are resolving, and high level description, in addition to the 
presentation.

b.Centralized Parsers Distribution requirements were presented by  
Atul. Some questions were raised. The next step is to include the requirements 
into merged requirements table, including all needed information and also 
present it to Architecture subcommittee

c. General: What is currently missing in the requirements 
definition. Yuan has expressed his view that VNFs/PNFs source/description is 
missing from the use case as well as expressed concern of lacking of 5G 
standard to start with 5G related requirements. We decided that:


i.Each requirements group/task force leader (5G, Change 
Management, VoLTE remaining requirements, E-vCPE, VNF Scaling;  Centralized 
Parser Distribution and External Controller, once ready) will issue separate 
email to the whole list describing what has already been defined in a different 
places related to his/her use case/requirements with the corresponding links

ii.  Community members will provide comments what is missing 
(if something is missing), target date is next Monday, 27/11/2017

d.VNF Scaling - next level of details - this task force 
representatives didn't attend the call. Steve/team - please also issue email as 
described above for the VNF scaling related requirements to see if ONAP 
community is satisfied with the level of definition

e.External Controller - status of the discussions (Ramesh). There 
was no progress on the related discussions. Ramesh will update us next week on 
the progress achieved by then


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D362BB.0306CCA0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] A Big Thanks to all your efforts !!! ONAP SO is sucessfully delivered for Amsterdam

[Alla Goldner]

+1
Great achievement by all involved people

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D35FCF.7A3A33A0]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Seshu m
Sent: Friday, November 17, 2017 3:26 PM
To: DAUGHERTY, ROBERT E <rd4...@att.com>; FAZAL, ABBAS 
<afa...@research.att.com>; cl6...@att.com; Byung-Woo Jun 
<byung-woo@ericsson.com>; Chenchuanyu <chenchua...@huawei.com>; DeWayne 
Filppi <dewa...@gigaspaces.com>; Ethan Lynn <ethanly...@vmware.com>; Jinxin 
(Saw) <saw@huawei.com>; sylvain.desbure...@orange.com; alex@intel.com; 
denghui (L) <denghu...@huawei.com>; Zhoujun (ONAP) <zhouj...@huawei.com>; 
jh7...@att.com; BULLARD, GIL <wb5...@att.com>; MARTELLA, ARTHUR W (ARTHUR) 
<amart...@research.att.com>; BORALE, SHAILENDRA S <sb8...@att.com>; 
lxin...@vmware.com; Michael O'Brien <frank.obr...@amdocs.com>; Kevin McDonnell 
<kevin.mcdonn...@huawei.com>; huang.zhuo...@zte.com.cn; Kang Xi 
<kang...@huawei.com>; Yang Xu (Yang, Fixed Network) <yang@huawei.com>; 
FREEMAN, BRIAN D <bf1...@att.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] A Big Thanks to all your efforts !!! ONAP SO is 
sucessfully delivered for Amsterdam

Dear All,

Thanks to all your efforts, ONAP SO is sucessfully delivered for Amsterdam.
It was definitely not a cake-walk but a roller-coaster ride that we had to pass 
through.
But, the results are here and this is a stepping stone for us to move on to 
Beijing.
Lets togther achieve more such successful milestones and make ONAP a global 
success.

Best Regards,
Seshu
**
 This email 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 here 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 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Usecase subcommittee meeting 23/10/2017 (wide discussion of Network Slicing)

[Alla Goldner]

Hi all,

Here is agenda for Monday’s meeting.

1.  Short overview of R1 vVoLTE and R-vCPE status and needs

2.  Beijing Release, 5G and network slicing – the next level of details. We 
invite architecture and modelling subcommittees representatives along with a 
different projects representatives to participate and provide their view and 
comments

 Best regards,

Alla Goldner

Open Network Division
Amdocs Technology





This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] First ONAP Hackathon

[Alla Goldner]

Hi,



This is to inform you that we have held the first ONAP 
Hackathon<https://wiki.onap.org/display/DW/ONAP+Hackathon%2C+16+October+Israel> 
in Israel on Monday, 16th of October hosted by Amdocs, AT and Cloudify.

We had 70 participants from 12 companies out of which 7 were VNF vendors 
(Amdocs, AT, Cloudify, ECI, RADCOM, Allot, Huwawei, Vasona Networks, Teoco, 
Microsoft, AudioCodes, Atrinet).

We have delivered set of presentations and demonstrations followed by Hackathon 
session in which vendors who came with their own VNFs got ONAP environments and 
professional support for validating and onboarding their VNFs, and others got 
the vFW demo scenario to play with and onboard.



RADCOM, Allot and Audiocodes managed pretty quickly to validate, onboard and 
create service of their own VNFs - kudos!!!


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D34813.EFA1C050]


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Layer123 presentation

[Alla Goldner]

Hi,

My slides from L123 event are here: 
https://wiki.onap.org/display/DW/Residential+vCPE+use+case

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D34730.97F8BEA0]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of eric.deb...@orange.com
Sent: Monday, October 16, 2017 10:51 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Layer123 presentation

Hello

Please find the slides presented during the Layer123 event
https://wiki.onap.org/download/attachments/16001688/SNDWC-ONAP-MiniSummit-VNF-Onboarding.pdf?api=v2

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.
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] R2 preparations: functional and non-functional requirements candidates

[Alla Goldner]

Hi all,

Recently, the list of R2 functional requirements candidates was extended by 
Kang (inputs from the Integration tem) and by Zhao (inputs from vVoLTE team).
https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates.

During the next week’s meeting we will continue requirements grouping and 
prioritization for R2.

Requirements authors - please check your requirements to see if definitions 
should be extended/further harmonization and grouping proposals can be made.

While working on prioritization, we will take into account the following inputs:


1.   https://wiki.onap.org/display/DW/Use+case+goals+and+selection+criteria

2.   
https://wiki.onap.org/display/DW/Architecture+Requirements+for+R2+use+cases

3.   Mostly important - goals of R2, as communicated before and will also 
be discussed during the meeting


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D33437.523E5A20]

From: Alla Goldner
Sent: Wednesday, September 20, 2017 12:40 PM
To: onap-...@lists.onap.org P <onap-...@lists.onap.org>; 
onap-discuss@lists.onap.org
Subject: R2 preparations: functional and non-functional requirements candidates

Hi all,

Here is the status of functional and non-functional requirements candidates for 
Beijing Release:


1.   Table with merged functional requirements candidates: 
https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates

2.   Non-functional requirements candidates 
https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements





And…Chag Sameach and Shana Tova to all our Jewish colleagues!



[#ShanaTova from #Jewish Treats! #RoshHashana #Judaism]

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D33437.523E5A20]

From: Alla Goldner
Sent: Tuesday, September 19, 2017 5:21 PM
To: 'onap-usecase...@lists.onap.org' 
<onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>>
Cc: 'Kenny Paul' <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>; 
'GILBERT, MAZIN E (MAZIN E)' 
<ma...@research.att.com<mailto:ma...@research.att.com>>; Yoav Kluger 
<yoav.klu...@amdocs.com<mailto:yoav.klu...@amdocs.com>>; Andrei Kojukhov 
<andrei.kojuk...@amdocs.com<mailto:andrei.kojuk...@amdocs.com>>; 
'onap-...@lists.onap.org' 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: RE: Usecase subcommittee meeting 18/09/2017 - the summary

Hi all,

Please see table with merged requirements here: 
https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates


1.   I marked all pages previously used for gathering of R2 functional 
requirements as OBSOLETE, as we want to have a single source now and update it 
accordingly
Note: Non-functional requirement proposals for R2 remain untouched 
https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements


2.   We (Alla, Yoav, Andrei) gathered all requirements into a single table 
with the information previously provided by the requirements authors, while 
adding on top of it:

a.   Agreed priority for R2 - this is something to be agreed by the whole 
group (empty for now)

b.  Proposed grouping/harmonization - this is our initial proposal of how 
those requirements may be grouped and this may be used for further requirements 
harmonization

c.   Proposed ownership - would be beneficial if each group/requirement 
gets under responsibility of a project (if it is a single project related) or 
person (i.e. proceeding with that group in the same way as was done with the 
specific use cases in R1) (empty for now)

The AI are:


1.   Requirements authors - please double check all initial information is 
present

2.   Requirements authors - please introduce summary/link to some detail 
requirement description in case it is missing. This is needed

3.   All - please review and provide your comments and suggestions for 
modifications/next step of our discussions, concentrating mostly on 
requirements harmonization/importance/relevancy for R2 goal of making ONAP 
Platform more stable

4.   Luman - please extend this table with E-vCPE additional requirements 
as discussed yesterday


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D33437.523E5A20]

From: Alla Goldner
Sent: Monday, September 18, 2017 10:22 PM
To: 'onap-usecase...@lists.onap.org' 
<onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>>
Cc: 'Kenny Paul' <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>; 
'GILBERT, MAZIN E (MAZIN E)' 
<ma...@research.att.com<mailto:ma...@research.att.com>>
Subject: Usecase subcommittee meeting 18/09/2017 - the summary

Hi all,

Thanks to all meeting’s attendants!
Here is the summary:


1.   All R2 use case

[onap-discuss] VNF Onboarding – ONAP Hackathon Invitation

[Alla Goldner]

Please forward to your Israeli colleagues – we would like to see them all 
attending this ONAP event!


[http://solutions.amdocs.com/rs/647-OJR-802/images/ONAP-Network-Hackathon650_WithTextx.jpg]


Hello ,

We would like to invite you to participate in the first VNF Onboarding 
Hackathon, hosted by Amdocs, AT and Cloudify, October 16 on the Amdocs 
Ra’anana campus.

This team based, collaborative event is all about innovation and education, 
giving you the opportunity to learn about ONAP, the industry’s leading 
automation and orchestration platform, and try your hand at onboarding and 
designing innovative new services.

Hear from the experts – Speakers from Amdocs, AT and Cloudify will share 
their experiences of working with ONAP and the advancements happening in this 
open source platform.

Gain hands-on experience – Bring your own VNF application to experiment with 
onboarding it to a live ONAP environment. We’ll provide help and support to 
keep you on track.

Don’t have a VNF to bring? Not a problem, just come to learn!

Showcase your work - The 3 top performing teams will have the opportunity to 
showcase their work at the Linux Foundation Roadshow on October 19th in front 
of influential local executives from network operators and VNF vendors.

The event is free of charge.
Register now<http://go1.amdocs.com/tIR0200oO00qa00wJcw>




[Amdocs]<http://go1.amdocs.com/hq0cg0J00OIow020RU0>



Send to a 
Friend<http://solutions.amdocs.com/index.php/email/emailWebview?ftf=true_tok=eyJpIjoiTURka05XUTBNRFU0Tm1KaiIsInQiOiJNZFpPdlYvUURNVS9VaGRWMVdnbS9CR3N2eFZJTFJEMmozdGVadHRJUlVZZ01jRFZ5MFBuL0Z0OE9CQ3NPQ0VSVnpxQjNkZGpRdk80RzhUTXFycy9OZz09In0%3D>
Unsubscribe<http://secure-web.cisco.com/1jQck1MSmf5ALUnJnFplYqYjqMXCcyGG_422smDlYOq9xeFcQHT-FTcTD1lBL19CBl8bUDdfOctbiXX7QQTPjin7dL4rx3E_fHMVYsxcHz6g0AuaLy07PpJAX7ugu_lckN0Y7hNP-vkZ3Wvn5hGKW8nIDK57R0qHUXUmhrTugTjoupMSrCrhBLG-8ab0H66F9Bw6YI6Cz6WfMrMYu8GkmI8yvdU7Dubuc_k2CiU9dcEuMBmbBzP7pxlVkkO2fMElVQduQKmsMt1adnlgR2GEotWA2idgvxdG8kORi0S06kdx-oc37FRibR6Huz43TFwdi7qzspCck3LtbUH7uk-N3OgrOQfhfF1m637r49nXPw7sXKkqq9d8BOPI1qm1u8cNFVhrsCF9HGDutLpi8Ji-G3lxkjwis1hEasSdn3fwqEYmJ_Ev2rgH-H1WbJ7hK9lQYlPTVnYriqZrZXQJjsp2Uwc4mprHJRogjzMwuygiw0dc/l237%3Ahttp%3A%2F%2Fsolutions.amdocs.com%2FUnsubscribePage.html%3Fmkt_unsubscribe%3D1%26mkt_tok%3DeyJpIjoiTURka05XUTBNRFU0Tm1KaiIsInQiOiJNZFpPdlYvUURNVS9VaGRWMVdnbS9CR3N2eFZJTFJEMmozdGVadHRJUlVZZ01jRFZ5MFBuL0Z0OE9CQ3NPQ0VSVnpxQjNkZGpRdk80RzhUTXFycy9OZz09In0%253De>




[Twitter]<http://go1.amdocs.com/Bc00VO2Rw0oJ00hq00I>


[LinkedIn]<http://go1.amdocs.com/Ao0W00OJ20wIcq0i00R>


[Facebook]<http://go1.amdocs.com/j0XJ0c2qO00wRIj0o00>


[YouTube]<http://go1.amdocs.com/ZJw000cYI000k20qROo>


[Blog]<http://go1.amdocs.com/pO0cZR000lwJIq000o2>



Amdocs
1390 Timberlake Manor Parkway, Chesterfield, MO 63017 US

View this 
online<http://solutions.amdocs.com/index.php/email/emailWebview?mkt_tok=eyJpIjoiTURka05XUTBNRFU0Tm1KaiIsInQiOiJNZFpPdlYvUURNVS9VaGRWMVdnbS9CR3N2eFZJTFJEMmozdGVadHRJUlVZZ01jRFZ5MFBuL0Z0OE9CQ3NPQ0VSVnpxQjNkZGpRdk80RzhUTXFycy9OZz09In0%3D>







Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D332DB.D1829920]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] R2 preparations: functional and non-functional requirements candidates

[Alla Goldner]

Hi all,

Here is the status of functional and non-functional requirements candidates for 
Beijing Release:


1.   Table with merged functional requirements candidates: 
https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates

2.   Non-functional requirements candidates 
https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements





And…Chag Sameach and Shana Tova to all our Jewish colleagues!



[#ShanaTova from #Jewish Treats! #RoshHashana #Judaism]

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D33168.22665D10]

From: Alla Goldner
Sent: Tuesday, September 19, 2017 5:21 PM
To: 'onap-usecase...@lists.onap.org' <onap-usecase...@lists.onap.org>
Cc: 'Kenny Paul' <kp...@linuxfoundation.org>; 'GILBERT, MAZIN E (MAZIN E)' 
<ma...@research.att.com>; Yoav Kluger <yoav.klu...@amdocs.com>; Andrei Kojukhov 
<andrei.kojuk...@amdocs.com>; 'onap-...@lists.onap.org' 
<onap-...@lists.onap.org>
Subject: RE: Usecase subcommittee meeting 18/09/2017 - the summary

Hi all,

Please see table with merged requirements here: 
https://wiki.onap.org/display/DW/Merged+list+of+R2+functional+requirement+candidates


1.   I marked all pages previously used for gathering of R2 functional 
requirements as OBSOLETE, as we want to have a single source now and update it 
accordingly
Note: Non-functional requirement proposals for R2 remain untouched 
https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements


2.   We (Alla, Yoav, Andrei) gathered all requirements into a single table 
with the information previously provided by the requirements authors, while 
adding on top of it:

a.   Agreed priority for R2 - this is something to be agreed by the whole 
group (empty for now)

b.  Proposed grouping/harmonization - this is our initial proposal of how 
those requirements may be grouped and this may be used for further requirements 
harmonization

c.   Proposed ownership - would be beneficial if each group/requirement 
gets under responsibility of a project (if it is a single project related) or 
person (i.e. proceeding with that group in the same way as was done with the 
specific use cases in R1) (empty for now)

The AI are:


1.   Requirements authors - please double check all initial information is 
present

2.   Requirements authors - please introduce summary/link to some detail 
requirement description in case it is missing. This is needed

3.   All - please review and provide your comments and suggestions for 
modifications/next step of our discussions, concentrating mostly on 
requirements harmonization/importance/relevancy for R2 goal of making ONAP 
Platform more stable

4.   Luman - please extend this table with E-vCPE additional requirements 
as discussed yesterday


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D33168.22665D10]

From: Alla Goldner
Sent: Monday, September 18, 2017 10:22 PM
To: 'onap-usecase...@lists.onap.org' 
<onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>>
Cc: 'Kenny Paul' <kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>>; 
'GILBERT, MAZIN E (MAZIN E)' 
<ma...@research.att.com<mailto:ma...@research.att.com>>
Subject: Usecase subcommittee meeting 18/09/2017 - the summary

Hi all,

Thanks to all meeting’s attendants!
Here is the summary:


1.   All R2 use cases were updated with the list of their corresponding 
functional requirements - thanks a lot to the authors!!! Some of the 
requirements still need more explanation to be added though

2.   Alla will merge all functional requirements into a single table by 
19/09/2017, then we will work with it for:

a.   Removal of the same requirement appearing multiple times/extension of 
one requirement by functional modifications coming from another one

b.  Making a requirements generic

   i.  We must 
target generic platform requirements (e.g. E-vCPE service onboarding, SDWAN 
service onboarding requirements transform to some generic onboarding functional 
requirement which is not supported by R1)

c.   Prioritization proposal of a different requirements for R2

3.   Then, Luman will also add additional E-vCPE requirements discussed 
during the call to this table

4.   Alla will check whether zoom connection is possible during next week 
meeting

5.   Alex will check with Chris whether R2 architecture requirements will 
be included to guide us while prioritizing those functional requirements 
https://wiki.onap.org/display/DW/Architecture+Requirements+for+R2+use+cases

6.   One of the action items to discuss during the next week joint meeting 
with the Architecture subcommittee is NAI/PCE coming from E-vCPE use case (in 
case Luman will be able to connect by zoom)

7. 

Re: [onap-discuss] ONAP TSC measures of success

[Alla Goldner]

Hi all,

I agree with the defined below, perhaps we should introduce additional 
contribution measures, on top of number of Git commits e.g. number of 
affected/new files, number of code lines etc.

Just my 2 cents :)

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image003.png@01D32DF7.58233230]

From: onap-tsc-private-boun...@lists.onap.org 
[mailto:onap-tsc-private-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Thursday, September 14, 2017 11:56 PM
To: GILBERT, MAZIN E <ma...@research.att.com>; onap-discuss@lists.onap.org; 
onap-tsc-priv...@lists.onap.org
Subject: Re: [onap-tsc-private] ONAP TSC measures of success

Hi,

I would recommend looking at:

1. Number of code contribution (Git commits)

2. Mailing list activities

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Dhananjay Pavgi
Sent: Thursday, September 14, 2017 3:43 AM
To: GILBERT, MAZIN E (MAZIN E) 
<ma...@research.att.com<mailto:ma...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> P 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: Re: [onap-tsc] ONAP TSC measures of success

Dear All,

Couple of other measures that could be considered:


1.   JUNit test coverage across LOC : Indicator of Code Quality (i.e. being 
unit tested)

2.   Number of VNFs successfully on boarded and tested : Indicator of VNF 
adoption rate for ONAP

3.   Number of Integration Test cases covered : Indicator of platform 
maturity for E-2-E use.

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
[cid:image002.png@01CE7323.F2727500]   [ONAP_logo_Sig]
www.techmahindra.com<http://www.techmahindra.com/> Platinum 
Member. Visit : http://www.onap.org<http://www.onap.org/>

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E (MAZIN E)
Sent: Wednesday, September 13, 2017 10:26 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> P 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: [onap-tsc] ONAP TSC measures of success

Dear ONAP Community,

I want to start an email dialog which we will follow up in our Paris meeting on 
technical measures of success of the ONAP platform.
What measures we should track and make publicly visible in PR events? I know 
LOC has been used already. This seems like one
of 2-3 other measures we should be tracking.

Those measures should be agnostic to any particular release and publicly 
recognized. Please share your thoughts and ideas.

thanks!
Mazin





Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html externally 
http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra.

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] R2 non-functional requirements

[Alla Goldner]

Hi all,

As a result of discussions we had in Usecase subcommittee and during our joint 
meeting with Architecture subcommittee today, the following wiki page was 
created 
https://wiki.onap.org/display/DW/R2+proposals+for+Non-functional+requirements .

This would list all non-functional requirements (i.e. not coming directly from 
a different use cases e.g. credentials usage, performance, resiliency, testing 
requirements etc.). These non-functional requirements are playing key role in 
building a stable, "Enterprise grade" ONAP platform.

Members of Architecture and Usecase subcommittees, the whole ONAP community - 
please fill in requirements' candidates for R2, we will then review and 
prioritize.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3281F.7EDCC090]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Rewarding committers and coders

[Alla Goldner]

Hi Mazin, all,

I believe we should reward when Release finishes, and this would be "the most 
contributing developer" category, while each project will have a possibility to 
announce its winner. Each project will have to determine what is measured, and 
it would be, I guess, a combination of (but, of course, not limited to):


1.   Code commits

2.   Email discussion participation

3.   Meetings' attendance

4.   Willingness to assist others

5.   Level of cooperation with other projects, subcommittees etc.

If same person is rewarded, let's say, 2 (or 3 ) times, we can think of a more 
significant reward.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image007.png@01D31BDE.ED20]


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E 
(MAZIN E)
Sent: Sunday, August 20, 2017 8:02 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> P
Subject: [onap-discuss] Rewarding committers and coders

ONAP Community,

I hope you are enjoying what remains of the summer.

I wanted to kick off a discussion on ideas for rewarding top committers and 
coders.
How often we should do this, type of rewards, ideas on promoting diversity,
bases for the rewards (lines, commits, etc). Should we introduce badges?

We will complete this discussion at the F2F meeting in France and start
executing your ideas.

Thanks!
Mazin






This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

[Alla Goldner]

Hi Tao,

So, I guess, we resolved one outstanding issue for vVoLTE support!

One question - with this design in place, I guess, it will not be difficult to 
support additional use cases UI, am I right?

 Best regards, 

Alla Goldner

Open Network Division 
Amdocs Technology





-Original Message-
From: shentao [mailto:shen...@chinamobile.com] 
Sent: Wednesday, August 16, 2017 2:12 PM
To: 'GILBERT, MAZIN E (MAZIN E)' <ma...@research.att.com>; Alla Goldner 
<alla.gold...@amdocs.com>
Cc: onap-discuss@lists.onap.org
Subject: 答复: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi, Mazin and Alla

I have discussed this issue with Lusheng and reached an agreement.
The solution is that Usecase UI will get alarm and performance data via Dmaap 
and support data storage.
So it isn't difficult to display alarm and performance data by UI.
Thanks for your attention.

Best regards,
Tao


-邮件原件-
发件人: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] 代表 GILBERT, MAZIN E (MAZIN E)
发送时间: 2017年8月14日 23:02
收件人: Alla Goldner
抄送: onap-discuss@lists.onap.org
主题: Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

I would like to understand how much of the work is app specific to VoLTE. We 
really should leverage any UI across all use cases especially if it is 
generating custom platform work. I will wait for the PTLs to share more info.

Thanks
Mazin 

Sent through AT's fastest network 

> On Aug 14, 2017, at 5:43 AM, Alla Goldner <alla.gold...@amdocs.com> wrote:
> 
>  



This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

[Alla Goldner]

Hi Mazin, Lingli,

Usecase UI project covers only vVoLTE specific requirements in R1: 
https://wiki.onap.org/display/DW/Usecase+UI+Release+Planning.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D31503.54989F90]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lingli
Sent: Monday, August 14, 2017 1:24 PM
To: GILBERT, MAZIN E (MAZIN E) <ma...@research.att.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi Mazin,

I do not believe it is new requirement. It was documented and communicated via 
the list before.

As a platform ONAP should provide FCAPS data to the UI for monitory purpose, 
which is use case independent.

Part of the API requirement is shared with Holmes, for alarm reporting.

We are connecting with DCAE PTL again for further clarification.

Thanks,
Lingli



China Mobile Research Institute
On 08/14/2017 17:19, GILBERT, MAZIN E (MAZIN E)<mailto:ma...@research.att.com> 
wrote:
Lingli

Is this UI use case specific or general for the platform (to be used for VOLTE, 
vCPE and others). Can you point me to the new platform requirements needed for 
it?

Thanks
Mazin
Sent through AT's fastest network

On Aug 13, 2017, at 7:04 PM, Lingli 
<denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>> wrote:
Hi Tao and Lusheng,

If I understand it correctly this issue is affecting M2 functional freeze for 
Usecase UI and VoLTE use case, and therefore needs immediate attention.
Would you both help further clarify the situation and expectations for R1 over 
the two APIs?

Thanks and Regards,
Lingli


China Mobile Research Institute
On 08/11/2017 13:30, shentao<mailto:shen...@chinamobile.com> wrote:
Hi, Lusheng

Usecase UI is going to provide alarm and performance show functions.
I just want to confirm if DCAE will support alarm and performance data query 
via Usecase UI.

Best regards,
Tao

-
沈涛
中国移动通信有限公司研究院网络技术研究所
中国北京市西城区宣武门西大街32号（100053）

Shen Tao
China Mobile Research Institute
No.32 Xuanwumen west street,Xicheng District, Beijing 100053, China

Tel: +86 15801696688-34070
Mobile: +86 13521591389
Email:  shen...@chinamobile.com<mailto:shen...@chinamobile.com>
-

___
onap-discuss mailing list
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=j5Joirsx9DTraFhodiUPAmT5WtlmQuhQMQ6ikZlV0TE=Vzxr-EAzE8erKKMRIxz-OHjPYmu4fdXjt9ea5dWgM6o=
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] R2 use cases planning

[Alla Goldner]

Hi Vladimir,

Yes, we discuss all R2 use cases submitted so far, under R2 (you can see the 
whole list on the left side of the page, I will add links in the explicit way).

In parallel, we are discussing ONAP Platform Capabilities missing in R1 and 
asking TSC for guidance for R2 direction as expressed in the presentation I've 
shared.



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D31422.E5D59620]

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Sunday, August 13, 2017 10:49 AM
To: Alla Goldner <alla.gold...@amdocs.com>; onap-...@lists.onap.org; 
'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org>
Cc: onap-usecase...@lists.onap.org
Subject: RE: R2 use cases planning

Hi, Alla
Let me ask for clarification. The link in the presentation "ONAP R2 use cases 
discussion r1"
https://wiki.onap.org/display/DW/Release+2+Use+Cases
points to the page (A) with a list of use cases proposed by Dhananjay Pavgi. 
There is no indication of existence of other use cases.
There are however other proposals in the Wiki, in particular at the page (B) 
titled "Use case: 5G- RAN deployment, E2E Slicing, SON"
https://wiki.onap.org/display/DW/Use+case%3A+5G-+RAN+deployment%2C+E2E+Slicing%2C+SON
The page (B) contains links to several others

* 5G RAN and Slicing Use Case for ONAP Release 
2<https://wiki.onap.org/download/attachments/8230720/5G_RAN_UseCase_for_R2.docx?version=1=1501518268000=v2>

* 
5G_RAN_UseCase_for_R2_v3<https://wiki.onap.org/download/attachments/10784151/5G_RAN_UseCase_for_R2_v3.docx?version=1=1502385472000=v2>

* 5G_RAN_UseCase_for_R2_V3 -- AT 
Comments<https://wiki.onap.org/download/attachments/10784151/5G_RAN_UseCase_for_R2_v4.docx?version=1=1502385736000=v2>

* 5G_RAN_UseCase_v3 -- Ericsson Comments & Action 
Items<https://wiki.onap.org/download/attachments/10784151/5G_RAN_UseCase_for_R2_v3-reflections-v3.docx?version=1=1502385521000=v2>
Let me ask whether the list in (B) will also be a part of the discussion on the 
call.
Thanks
Vladimir

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Thursday, August 10, 2017 8:21 PM
To: onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>; 
'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Subject: [onap-tsc] R2 use cases planning

Hi all,

Unfortunately, we didn't have time during the TSC meeting to cover R2 use cases 
topic.

I would like to ask you to review the attached presentation, covering status of 
Usecase subcommittee discussions and asking TSC for guidelines on directions we 
should take going forward (Extending ONAP Platform capabilities or introducing 
new functional use cases).
Also, some initial proposal for R2 timelines is part of this input material, 
with emphasize given to pre-R2 milestones related to use cases approval.

It is part of the next meeting agenda, 
https://wiki.onap.org/display/DW/2017-08-17+Meeting+Agenda .
It would be great if we can start the related discussion by emails and get your 
feedback prior to TSC meeting next week.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D31422.E5D59620]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Usecase/Arch subcommittees joint meeting on Wednesday

[Alla Goldner]

Hi all,

Please find here the updated agenda with preliminary questions received from 
Architecture subcommittee (thanks, Chris!):

1.Usecase subcommittee will present R1 use cases (Yoav/Kang - vCPE, 
Chengli/Yang - vVoLTE) and provide brief overview of R2 discussions, including 
emphasizing ONAP Platform Capabilities

2.Architecture subcommittee will present and highlight differences 
between R1 and R2 foreseen architecture, so Usecase subcommittee 
representatives can ask on that and its potential impact on use cases 
implementation, and also raise relevant issues.

3.Architecture subcommittee will ask their use case related 
questions:
-  would the use case(s) require multi-site support?
-  multi-region/multi-domain/federation?
-  Multi-national?
-  Do we need to consider enhanced networking features (e.g., 
underlays)?
-  Can individual use cases be built from same components? (common 
APIs/models)
-  What are the challenges from the first set of use cases?
-  What technical debt have you identified?
-  Clarify business drivers and capabilities of the use cases
-  What are the functional commonalities between the use cases? Are 
there generic elements where we should focus?

Usecase subcommittee members, please try to come to the meeting prepared with 
responses, as our meeting time is limited; would also be good to start 
communicating some of the responses by emails sent both to Usecase and to 
Architecture subcommittee.

This is start of our dialogue which will continue towards R2, as we move on 
with use cases definition and architecture definition. We will also discuss 
format and frequency of our join meetings going forward.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D31084.6CE06890]

From: Alla Goldner
Sent: Monday, August 07, 2017 10:35 PM
To: onap-usecase...@lists.onap.org; Yoav Kluger <yoav.klu...@amdocs.com>; 'Kang 
Xi' <kang...@huawei.com>; 'Chengli Wang' <wangchen...@chinamobile.com>; 'Yang 
Xu (Yang, Fixed Network)' <yang@huawei.com>; 'Yunxia Chen' 
<helen.c...@huawei.com>
Cc: GILBERT, MAZIN E (MAZIN E) <ma...@research.att.com>; Phil Robb 
<pr...@linuxfoundation.org>; 'Kenny Paul' <kp...@linuxfoundation.org>; 
onap-...@lists.onap.org
Subject: Usecase/Arch subcommittees joint meeting on Wednesday

Hi all,

After speaking with Chris, here is our proposal for the joint meeting on 
Wednesday:


1.   Usecase subcommittee will present R1 use cases (Yoav/Kang - vCPE, 
Chengli/Yang - vVoLTE), mostly concentrated on ONAP Platform capabilities



2.   Usecase subcommittee members are encouraged to ask questions/provide 
demands on potential functionality to be supported for the next releases


3.   Architecture subcommittee will present and highlight differences 
between R1 and R2 foreseen architecture, so Usecase subcommittee 
representatives can ask on that and its potential impact on use cases 
implementation, and also raise relevant issues.



4.   Architecture subcommittee will ask their use case related questions


5.   Both Usecase and Architecture subcommittee members are encouraged to 
send out their questions in advance, in order to make our discussions more 
effective.


This is start of our dialogue which will continue towards R2, as we move on 
with use cases definition and architecture definition. We will also discuss 
format and frequency of our join meetings going forward.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D31084.6CE06890]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] short slot during the upcoming TSC meeting to discuss use cases scope/milestones for R2

[Alla Goldner]

Hi, Mazin, Phil, Kenny,

During today's Usecase subcommittee meeting, we discussed whether we should 
concentrate on introducing new functional use cases for R2 or concentrate on 
extending/adding ONAP Platform capabilities for the existing use cases.
Also, we stated to discuss R2 milestones for use cases scope approval.

It would be good, if you can dedicate 10 min during the upcoming TSC meeting 
for this discussion. We may not be able to decide during the meeting, but 
simply open the topic, so we can continue discussing it by emails and come to 
conclusion next week.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D30FC4.A4D05640]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] vCPE use case review at virtual developer event

[Alla Goldner]

Thanks a lot, Kang,

If needed, we will also use some of Usecase subcommittee meeting time on Wed to 
close on remaining issues.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D304D0.1C0A92C0]

From: Kang Xi [mailto:kang...@huawei.com]
Sent: Monday, July 24, 2017 10:23 PM
To: 'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org>
Cc: SHACHAM, RON (RON) <rshac...@research.att.com>; NGUEKO, GERVAIS-MARTIAL 
<gn4...@intl.att.com>; DRAGOSH, PAMELA L (PAM) <pdrag...@research.att.com>; 
Pawłowski Michał 1 - Korpo <michal.pawlows...@orange.com>; Jon Fannar Karlsson 
Taylor <jon.tay...@amdocs.com>; Alla Goldner <alla.gold...@amdocs.com>; Yunxia 
Chen <helen.c...@huawei.com>; Yang Xu (Yang, Fixed Network) 
<yang@huawei.com>; Yoav Kluger <yoav.klu...@amdocs.com>; Seshu m 
<seshu.kuma...@huawei.com>; denghui (L) <denghu...@huawei.com>; Zhou, Danny 
<danny.z...@intel.com>; FREEMAN, BRIAN D <bf1...@att.com>; SPATSCHECK, OLIVER 
<spat...@research.att.com>; Lefevre, Catherine <cl6...@intl.att.com>; Chong Li 
<chong...@huawei.com>; Mengqiang <oscar.mengqi...@huawei.com>; ROSE, DANIEL V 
<dr6...@att.com>; TIMONEY, DAN <dt5...@att.com>; GUPTA, ALOK <ag1...@att.com>; 
KLEIN, REUBEN <rk1...@att.com>; MAHER, RANDA <rx1...@att.com>
Subject: RE: vCPE use case review at virtual developer event

Hi All,

In tomorrow's virtual develop event vCPE session, I plan to give a quick 
presentation of the architecture on the wiki, the service model and flows from 
Gil's slides, and closed loop design from Ron's slides. Given that we only have 
50min, I'll keep the presentation short and give more time for open 
discussions. Most likely we won't have enough time to completely answer all 
possible questions but I'll write them down to help continue the discussions 
offline. If you have any questions/comments that you want to share in advance, 
please feel free to reply this email before the meeting.

Useful materials:

-  Use case wiki page: 
https://wiki.onap.org/pages/viewpage.action?pageId=3246168

-  Important questions: 
https://wiki.onap.org/display/DW/Use+Case+Related+Important+Questions+and+Answers

Regards,
Kang

From: Kang Xi
Sent: Thursday, July 20, 2017 15:40
To: 'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: 'SHACHAM, RON (RON)' 
<rshac...@research.att.com<mailto:rshac...@research.att.com>>; NGUEKO, 
GERVAIS-MARTIAL <gn4...@intl.att.com<mailto:gn4...@intl.att.com>>; DRAGOSH, 
PAMELA L (PAM) <pdrag...@research.att.com<mailto:pdrag...@research.att.com>>; 
Pawłowski Michał 1 - Korpo 
<michal.pawlows...@orange.com<mailto:michal.pawlows...@orange.com>>; TAYLOR, 
JON <jon.tay...@amdocs.com<mailto:jon.tay...@amdocs.com>>; Alla Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>; Yunxia Chen 
<helen.c...@huawei.com<mailto:helen.c...@huawei.com>>; Yang Xu (Yang, Fixed 
Network) <yang@huawei.com<mailto:yang@huawei.com>>; KLUGER, YOAV 
<yoav.klu...@amdocs.com<mailto:yoav.klu...@amdocs.com>>; Seshu m 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>; denghui (L) 
<denghu...@huawei.com<mailto:denghu...@huawei.com>>; Zhou, Danny 
<danny.z...@intel.com<mailto:danny.z...@intel.com>>; 'FREEMAN, BRIAN D' 
<bf1...@att.com<mailto:bf1...@att.com>>; SPATSCHECK, OLIVER 
<spat...@research.att.com<mailto:spat...@research.att.com>>; Lefevre, Catherine 
<cl6...@intl.att.com<mailto:cl6...@intl.att.com>>; Chong Li 
<chong...@huawei.com<mailto:chong...@huawei.com>>; Mengqiang 
<oscar.mengqi...@huawei.com<mailto:oscar.mengqi...@huawei.com>>; ROSE, DANIEL V 
<dr6...@att.com<mailto:dr6...@att.com>>; TIMONEY, DAN 
<dt5...@att.com<mailto:dt5...@att.com>>; 'GUPTA, ALOK' 
<ag1...@att.com<mailto:ag1...@att.com>>; KLEIN, REUBEN 
<rk1...@att.com<mailto:rk1...@att.com>>; MAHER, RANDA 
<rx1...@att.com<mailto:rx1...@att.com>>
Subject: vCPE use case review at virtual developer event

Hi All,

We will have a vCPE use case review in next week's virtual developer event. 
Please sign up at the following link if you are interested. Thanks.
https://wiki.onap.org/pages/viewpage.action?pageId=8232264


Regards,
Kang

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Architecture Progress

[Alla Goldner]

Dear Hui,

First of all, let's assume that all people participating in the discussions do 
understand what they are talking about. I strongly believe such a respectful 
behavior will help to reach consensus, which is our common goal.

Secondly, let's look on the presentation provided by Vimal. There is a key 
difference between the slide 2 (current R2+ view) and the slide 3 (Desired 
Integrated view). This difference is in having an integrated "Standard & sVNFM 
Adaption Layer" on slide 3. I believe our discussion should be concentrated on 
this and other differences, their pros and cons, and overall involved modules' 
functionalities, depending on those architecture alternatives.
I suggest we continue these discussions during next week's virtual meeting.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D302F9.1840D290]

From: denghui (L) [mailto:denghu...@huawei.com]
Sent: Saturday, July 22, 2017 1:52 PM
To: Alla Goldner <alla.gold...@amdocs.com>; Pasi Vaananen 
<pvaan...@redhat.com>; onap-discuss@lists.onap.org
Cc: onap-tsc <onap-...@lists.onap.org>
Subject: RE: [onap-discuss] Architecture Progress

Hi all

I guess that people are confusing about the interface of VNF  with ONAP 
architecture,
Interface between VNF and ONAP is quite simple : Heat(ECOMP) or TOSCA(OPEN-O), 
it has nothing with architecture discussion.

I agree with Chris's suggestion here, either you need to understand the 
implementation or join architecture call.

Best regards,

DENG Hui

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Saturday, July 22, 2017 1:56 PM
To: Pasi Vaananen <pvaan...@redhat.com<mailto:pvaan...@redhat.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: onap-tsc <onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: Re: [onap-discuss] Architecture Progress

Hi Pasi, Jamil, Chris, all,

I fully agree with Pasi's view.
When we started this work ,the assumption was that whatever our merged 
architecture will look like internally, we should deliver a single set of 
interfaces between the VNFs and ONAP.
And this is not what we are having right now with R1 proposed architecture.
Also, indeed, if we allow interfaces' divergence for R1, it is going to be hard 
to reverse later. One possible outcome is that some of VNF vendors would want 
to wait until the divergences are resolved. The other possible outcome is that 
we continue proceeding with 2 different tracks within ONAP - one coming from 
Open-O and the other one coming from ecomp, and each one of VNF vendors making 
a decision which track they want/need to support, in some cases having a need 
to support both thus doubling the effort. The latter is clearly not the optimal 
way forward, and not what we want to achieve with ONAP, we should try to see 
how we avoid it at least in a longer term, in my view. The former may be 
significantly improved and timelines may be shortened, if we manage to work on 
it effectively now and provide the shortest path to get there from the current 
state - and Vimal's proposal of target merged architecture looks like a great 
step towards it, preserving all functionality coming from APPC and VF-C, but 
making a single set of external interfaces. I think we should give a very high 
priority to those discussions and handle them now, in parallel to R1 work.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D302F9.1840D290]

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pasi Vaananen
Sent: Friday, July 21, 2017 11:15 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Architecture Progress


Hi Jamil,

In ONAP F2F in New Jersey, there was what I thought was "agreement" that there 
is to be only one set of VNFDs / interfaces for ONAP. If that is strictly 
enforced (like I think it should be, as these collectively form the "interface" 
between the VNF vendors and ONAP - if the overlap would be e.g. on NS level 
descriptors, it would not be as bad, as those could be considered to be system 
internal and therefore not as much of inter-operability problem), then having 
two parallel implementations means that they would need to do exactly the same 
things, and be essentially "indistinguishable" from each other even on their 
behaviors associated with these descriptors and interfaces.

Obviously, strict enforcement of this would imply about 100% overlap on the 
associated development, testing, etc. activities (minus any sharing of code 
between the teams). And, in addition, coordination between the two teams to 
accomplish the required level of agreeme

Re: [onap-discuss] Architecture Progress

[Alla Goldner]

Hi Pasi, Jamil, Chris, all,

I fully agree with Pasi's view.
When we started this work ,the assumption was that whatever our merged 
architecture will look like internally, we should deliver a single set of 
interfaces between the VNFs and ONAP.
And this is not what we are having right now with R1 proposed architecture.
Also, indeed, if we allow interfaces' divergence for R1, it is going to be hard 
to reverse later. One possible outcome is that some of VNF vendors would want 
to wait until the divergences are resolved. The other possible outcome is that 
we continue proceeding with 2 different tracks within ONAP - one coming from 
Open-O and the other one coming from ecomp, and each one of VNF vendors making 
a decision which track they want/need to support, in some cases having a need 
to support both thus doubling the effort. The latter is clearly not the optimal 
way forward, and not what we want to achieve with ONAP, we should try to see 
how we avoid it at least in a longer term, in my view. The former may be 
significantly improved and timelines may be shortened, if we manage to work on 
it effectively now and provide the shortest path to get there from the current 
state - and Vimal's proposal of target merged architecture looks like a great 
step towards it, preserving all functionality coming from APPC and VF-C, but 
making a single set of external interfaces. I think we should give a very high 
priority to those discussions and handle them now, in parallel to R1 work.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D302C5.88CFF7E0]

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Pasi Vaananen
Sent: Friday, July 21, 2017 11:15 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Architecture Progress


Hi Jamil,

In ONAP F2F in New Jersey, there was what I thought was "agreement" that there 
is to be only one set of VNFDs / interfaces for ONAP. If that is strictly 
enforced (like I think it should be, as these collectively form the "interface" 
between the VNF vendors and ONAP - if the overlap would be e.g. on NS level 
descriptors, it would not be as bad, as those could be considered to be system 
internal and therefore not as much of inter-operability problem), then having 
two parallel implementations means that they would need to do exactly the same 
things, and be essentially "indistinguishable" from each other even on their 
behaviors associated with these descriptors and interfaces.

Obviously, strict enforcement of this would imply about 100% overlap on the 
associated development, testing, etc. activities (minus any sharing of code 
between the teams). And, in addition, coordination between the two teams to 
accomplish the required level of agreement in absence of the independent / 
detailed specification that is to be implemented, which would further slow 
things down.

If ONAP community chooses to allow divergence here for r1, it is going to be 
hard to reverse later (assuming that someone would pick sides and actually 
deploy the result - more likely outcome is that VNF vendors would want to wait 
until the divergences are resolved, i.e. R2 at the earliest per current 
"plan"). It is also going to be difficult to "push back" on e.g. ETSI and OASIS 
on descriptors etc. if ONAP community itself cant get into one opinion on what 
to push.

I like Vimal's "Target Merged Architecture" slide #3 at high level - what is 
the shortest path to get there from the current state ?

Regards,

Pasi

On 07/21/2017 03:09 PM, jamil.cha...@orange.com<mailto:jamil.cha...@orange.com> 
wrote:
Hi Chris
I have participated partially to the last 2 meetings, my position was 
represented by Vimal. We need time to analyse the output before to take a 
position and as you know the subcommittee is consultative and we need to 
discuss the output in the TSC.
I think we have clearly Identified overlap between 2 approches and there is a 
high risk to not have a useful Rel-1 as we have many changes  on the technical 
components in addition to 2 different VNF guidelines.

Regards
Jamil



Cordialement
Jamil
Le 21 juil. 2017 à 20:17, Christopher Donley (Chris) 
<christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>> a écrit :
Dear Jamil,

I'd like to invite you to participate in our ARC calls.  We generally meet 
Tuesdays from 1400-1600 UTC (but we'll have to adjust next week due to the 
developer meeting).  We have considered multiple presentations over the last 
four weeks (including the one you referenced), and after careful discussion, we 
aligned on the release 1 and release 2 functional architecture I shared.  I 
held consensus checks on each of the last two calls and did not hear dissenting 
opinions from the high level approach. The version of the diagram that I shared 
represents the community consensus from Tues

Re: [onap-discuss] Use case subcommittee - meeting summary 10/07/2017

[Alla Goldner]

Hi Steve,

According to the discussions we had, I believe that those existing Use cases 
flows include sufficient level of information, but:


1.   Detailed functionality is up to projects to define, and there are 
questions raised from the projects side

2.   There may be missing/ or additional demanded call flows

3.   There are some clarifications requested to be added to the call flows. 
Some of them mentioned in my summary, some were requested during the meetings 
with the PTLs

In overall, I believe, we are tracking all gaps along with the progress made, 
and all remaining Open Issues are handled as we communicate. Both use cases 
leaders and long with the Integration team reported that it is feasible to 
close all remaining Open Issues till the next week and we are working with 
projects on that.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2FADE.A2624A80]

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Wednesday, July 12, 2017 1:54 AM
To: Alla Goldner <alla.gold...@amdocs.com>
Cc: onap-usecase...@lists.onap.org; onap-discuss@lists.onap.org; onap-tsc 
<onap-...@lists.onap.org>
Subject: Re: [onap-discuss] Use case subcommittee - meeting summary 10/07/2017

Hi Alla,

Do you have a feel for how much guidance is required for R1, I believe we said 
the call flows should be high level, though I can understand that there are 
questions from ptls that we need to answer.

BR, steve

Sent from my Phone, please forgive typos

On 11 Jul 2017, at 09:03, Alla Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> wrote:
Hi all,

Thanks a lot to meeting’s attendants.

Here is the meeting’s summary. As there are also action items to all PTLs, I 
distribute it to the whole TSC list. I encourage PTLs and all potentially 
involved people to register to dedicated usecasesub list.


1.   Doodle poll is created (and email is sent by Kenny) to see preference 
for Use case subcommittee meetings’ occurrence – weekly or bi-weekly. All 
interested parties are encouraged to vote.



2.   The highest priority now is to compete R1 use cases discussion. In 
parallel we should start working on R2 use cases. Thus, please start including 
your R2 use case description proposals under this created link:
https://wiki.onap.org/display/DW/Release+2+Use+Cases . We can then start email 
discussions in parallel to our meetings.



3.   vCPE and vVOLTE use cases leaders have meetings with a different 
projects. The objective is to complete all use cases description with all flows 
and involved modules functionality by next week. Use cases leaders are 
requested to upload and distribute all meetings notes. The work is done and 
organized in a very close cooperation with Integration project. In case of a 
need, we may schedule dedicated meeting to review remaining points with 
projects this week

a.   vCPE:


   i.  Still under discussion:

1.   DCAE/Intel discussion to close packets’ format (please involve Alok 
Gupta per his request)

2.   Interactions with SDC will be further clarified

3.   SDN-C functional extension will be discussed with SDN-C team

4.   Onboarding of vCPE VNFs scenario - DCAE Telemetry issue will be 
clarified



b.  vVoLTE


   i.  There is need to check legal process of commercial VNFs 
approval. Perhaps this is not needed as commitment is only for integration 
testing. In any case, we will ask Phil to help validating this issue


 ii.  There is need to involve VNF requirements project to double check 
whether documentation of Open-O is merged with ecomp documentation to create a 
single set of guidelines


iii.  There is request to include model which drives the use case in 
the vVolTE use case description


   iv.  A question on whether vIMS+vEPC is enforced as a single request 
coming from SO (i.e. as a single network service or not). It was clarified that 
it is up to implementation, as VF-C can support it both ways. The corresponding 
clarification should be included in the use case description


 v.  Still under discussion:

1.   SDC for design time functionality

2.   SDN-C interaction with 3rd party controller

3.   For overlay – whether Openstack or hardware will be used – discussions 
with Brian Freeman are initiated



4.   PTL of projects with specific issues related to use cases 
implementation are requested to provide th

[onap-discuss] Use case subcommittee - meeting summary 10/07/2017

[Alla Goldner]

Hi all,

Thanks a lot to meeting's attendants.

Here is the meeting's summary. As there are also action items to all PTLs, I 
distribute it to the whole TSC list. I encourage PTLs and all potentially 
involved people to register to dedicated usecasesub list.


1.   Doodle poll is created (and email is sent by Kenny) to see preference 
for Use case subcommittee meetings' occurrence - weekly or bi-weekly. All 
interested parties are encouraged to vote.



2.   The highest priority now is to compete R1 use cases discussion. In 
parallel we should start working on R2 use cases. Thus, please start including 
your R2 use case description proposals under this created link:
https://wiki.onap.org/display/DW/Release+2+Use+Cases . We can then start email 
discussions in parallel to our meetings.



3.   vCPE and vVOLTE use cases leaders have meetings with a different 
projects. The objective is to complete all use cases description with all flows 
and involved modules functionality by next week. Use cases leaders are 
requested to upload and distribute all meetings notes. The work is done and 
organized in a very close cooperation with Integration project. In case of a 
need, we may schedule dedicated meeting to review remaining points with 
projects this week

a.   vCPE:

   i.  Still 
under discussion:

1.   DCAE/Intel discussion to close packets' format (please involve Alok 
Gupta per his request)

2.   Interactions with SDC will be further clarified

3.   SDN-C functional extension will be discussed with SDN-C team

4.   Onboarding of vCPE VNFs scenario - DCAE Telemetry issue will be 
clarified



b.  vVoLTE

   i.  There is 
need to check legal process of commercial VNFs approval. Perhaps this is not 
needed as commitment is only for integration testing. In any case, we will ask 
Phil to help validating this issue

 ii.  There is 
need to involve VNF requirements project to double check whether documentation 
of Open-O is merged with ecomp documentation to create a single set of 
guidelines

iii.  There is 
request to include model which drives the use case in the vVolTE use case 
description

   iv.  A question 
on whether vIMS+vEPC is enforced as a single request coming from SO (i.e. as a 
single network service or not). It was clarified that it is up to 
implementation, as VF-C can support it both ways. The corresponding 
clarification should be included in the use case description

 v.  Still 
under discussion:

1.   SDC for design time functionality

2.   SDN-C interaction with 3rd party controller

3.   For overlay - whether Openstack or hardware will be used - discussions 
with Brian Freeman are initiated



4.   PTL of projects with specific issues related to use cases 
implementation are requested to provide their questions in advance and also to 
attend Use case subcommittee meetings in such a cases. PTLs who has no clear 
information on what their project should implement per R1 use cases (and those 
projects are not mentioned under point 3 above) are requested to approach me 
ASAP.



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2FA28.AC916010]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-usecasesub] [onap-tsc] Use case subcommittee - agenda for the upcoming meeting this Monday

[Alla Goldner]

Hi, Evgeniy,

Sure, I will add this to agenda.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F9C7.2194BE50]

From: Ievgen Zhukov [mailto:evgeniy.zhu...@netcracker.com]
Sent: Monday, July 10, 2017 9:16 PM
To: Alla Goldner <alla.gold...@amdocs.com>; onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Subject: RE: [Onap-usecasesub] [onap-tsc] Use case subcommittee - agenda for 
the upcoming meeting this Monday

Hi, Alla

Can we put into Agenda SD-WAN and SD-LAN for Release 2?
This Use Cases will be able to demonstrate ONAP Orchestration capability for 
VNFs hosted on CPE device (SD-WAN Case) and beyond it (SD-LAN Case).

And, if meeting time will be enough, can we take MEC Use Case for consideration?
This Use Case might have significant impact for Architecture and other Use 
Cases.

Thank you,
---

Evgeniy Zhukov, Business Analysis
Netcracker Technology

+38 (044) 238-8727 | ext. 26927| office
+38 (093) 210-4266 | mobile

We are Netcracker, and we are focused forward



[https://www.netcracker.com/assets/img/netcracker-social-final.png]ƕ
From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, July 7, 2017 9:37 AM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi all,

Here is agenda for the upcoming meeting.
In case of any additional topics, or concrete use cases proposals for 
discussion, I kindly ask to let me know in advance, so meeting’s time can be 
managed accordingly.



  1.  Review of suggested Use case subcommittee flow of operation as documented 
here https://wiki.onap.org/display/DW/Usecase+subcommittee , “Use case 
subcommittee flow”
  2.  R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions
  3.  R2 use cases: the initial proposals
 *   Network Function Change Management?
 *   Enterprise vCPE?
 *   More?
  4.  AOB




Note: The previous meeting minutes can be found under 
https://wiki.onap.org/display/DW/Usecase+Subcommittee+Meeting+Minutes

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F9C7.2194BE50]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer




The information transmitted herein is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary and/or 
privileged material. Any review, retransmission, dissemination or other use of, 
or taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer.
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Use case subcommittee - agenda for the upcoming meeting this Monday

[Alla Goldner]

Hi Lingli,

Thanks a lot for your feedback.
I fully agree with you that R1 discussions should be prioritized.
You can see that this item (R1 use cases (vCPE and vVoLTE): Status, Open 
issues, required actions) appears before the R2 use cases discussions.
However, we should limit this discussion to Status, Open issues and required 
actions, as mentioned, during Use case subcommittee meeting, for the following 
reasons:


1.   As agreed for R1 (there were quite a few discussions and emails shared 
by a different people in this regard), we have R1 expedited process, by which, 
upon use cases approval, responsibility on use cases coordination moved to 
Integration project. This results in a different meetings between use cases 
leaders and the respective involved projects. BTW, the feedback I am getting so 
far as that this work has been very productive, for both approved use cases.



2.   In order to analyse different projects dependencies and affected 
functionalities, technical issues should be discussed with people working on a 
different projects. The reason is that projects’ expertise is within a project, 
not within Use case subcommittee. We can’t force all projects’ ALL 
representatives to attend Use case subcommittee, while, only if all people 
working on specific project participate in discussion, we can have full 
functional coverage and appropriate split of responsibilities.



3.   We do need start talking about R2 use cases, in order to have our 
proposal ready for TSC review in advance before R2 starts, in order to align 
correctly and on time with R2  goals.


2 weeks ago I raised question on whether we should move to weekly use case 
subcommittee meetings. No response was received. I will raise it again today 
during the meeting, as, in my understanding, such a move is needed in order to 
allow a comprehensive coverage.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F96A.D2752D70]

From: Lingli Deng [mailto:denglin...@chinamobile.com]
Sent: Monday, July 10, 2017 9:41 AM
To: Alla Goldner <alla.gold...@amdocs.com>; 'BEGWANI, VIMAL' <vb1...@att.com>; 
onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; 'onap-tsc' <onap-...@lists.onap.org>
Subject: RE: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi Alla,

I wonder if we should prioritize the R1 usecase discussion in this time slot.

Currently, there are ad hoc meetings arranged respectively for VoLTE and CPE 
usecases, which makes people rather frustrating and not efficient because it is 
really hard to allocate a common time slot for cross project discussion, which 
I believe would be improved much if we host such discussion in this 
subcommittee, which to my understanding is the top priority.

Thanks,
Lingli

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: 2017年7月8日 0:59
To: BEGWANI, VIMAL <vb1...@att.com<mailto:vb1...@att.com>>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: Re: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi, Vimal,

Yes, of course, happy to do that.

Here is the updated agenda:


  1.  Review of suggested Use case subcommittee flow of operation as documented 
here 
https://wiki.onap.org/display/DW/Usecase+subcommittee<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Usecase-2Bsubcommittee=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=YQZaNPLN15xk3BWcVl7k8w=fJeFF2gsoUxIvMSd7LwlFJm195aQf6PCsGoLcOOJcVs=_gs9OYnZ5I93MA1QgqXnFJ9luEVCYalLple1Iynub1w=>
 , “Use case subcommittee flow”
  2.  R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions
  3.  R2 use cases: the initial proposals
 *   Network Function Change Management?
 *   Enterprise vCPE?
 *   5G
   i.  RAN 
deployment
 ii.  E2E 
Network Slicing

 *   More?
  1.  AOB


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F989.346CD870]

From: BEGWANI, VIMAL [mailto:vb1...@att.com]
Sent: Friday, July 07, 2017 7:53 PM
To: Alla Goldner <alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: RE: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Alla,
  We are still in an initial discussion, but I would like to ad

Re: [onap-discuss] [onap-tsc] Use case subcommittee - agenda for the upcoming meeting this Monday

[Alla Goldner]

Hi, Vimal,

Yes, of course, happy to do that.

Here is the updated agenda:


  1.  Review of suggested Use case subcommittee flow of operation as documented 
here 
https://wiki.onap.org/display/DW/Usecase+subcommittee<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Usecase-2Bsubcommittee=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=YQZaNPLN15xk3BWcVl7k8w=fJeFF2gsoUxIvMSd7LwlFJm195aQf6PCsGoLcOOJcVs=_gs9OYnZ5I93MA1QgqXnFJ9luEVCYalLple1Iynub1w=>
 , "Use case subcommittee flow"
  2.  R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions
  3.  R2 use cases: the initial proposals
 *   Network Function Change Management?
 *   Enterprise vCPE?
 *   5G
   i.  RAN 
deployment
 ii.  E2E 
Network Slicing

 *   More?
  1.  AOB


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F75B.78E565B0]

From: BEGWANI, VIMAL [mailto:vb1...@att.com]
Sent: Friday, July 07, 2017 7:53 PM
To: Alla Goldner <alla.gold...@amdocs.com>; onap-usecase...@lists.onap.org
Cc: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Subject: RE: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Alla,
  We are still in an initial discussion, but I would like to add 5G RAN 
deployment and E2E Network Slicing support for 5G network.  Can we add it as a 
place holder?
Regards,
Vimal

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Friday, July 07, 2017 12:37 PM
To: onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
<onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>>
Subject: [onap-tsc] Use case subcommittee - agenda for the upcoming meeting 
this Monday

Hi all,

Here is agenda for the upcoming meeting.
In case of any additional topics, or concrete use cases proposals for 
discussion, I kindly ask to let me know in advance, so meeting's time can be 
managed accordingly.



  1.  Review of suggested Use case subcommittee flow of operation as documented 
here 
https://wiki.onap.org/display/DW/Usecase+subcommittee<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Usecase-2Bsubcommittee=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=YQZaNPLN15xk3BWcVl7k8w=fJeFF2gsoUxIvMSd7LwlFJm195aQf6PCsGoLcOOJcVs=_gs9OYnZ5I93MA1QgqXnFJ9luEVCYalLple1Iynub1w=>
 , "Use case subcommittee flow"
  2.  R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions
  3.  R2 use cases: the initial proposals
 *   Network Function Change Management?
 *   Enterprise vCPE?
 *   More?
  4.  AOB




Note: The previous meeting minutes can be found under 
https://wiki.onap.org/display/DW/Usecase+Subcommittee+Meeting+Minutes<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Usecase-2BSubcommittee-2BMeeting-2BMinutes=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=YQZaNPLN15xk3BWcVl7k8w=fJeFF2gsoUxIvMSd7LwlFJm195aQf6PCsGoLcOOJcVs=Ge_R73iwTJpZgq5qdnsov29qxNgMl0rG5yOlYTp1bVk=>

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F75B.78E565B0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=YQZaNPLN15xk3BWcVl7k8w=fJeFF2gsoUxIvMSd7LwlFJm195aQf6PCsGoLcOOJcVs=OXNNDyrj75gn-js0w0ShMMbQLpdKTcZMb2D7w9X1i5E=>
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [openlab] OpenLab Kickoff Meeting Schedule

[Alla Goldner]

Thanks a lot, Chengli, for your kind consideration!!!
Let's see if this newly suggested slot is acceptable by others.

Best regards, Alla


 Original Message 
Subject: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule
From: Chengli Wang <wangchen...@chinamobile.com>
Date: Jul 7, 2017, 2:08 PM
To: Alla Goldner <alla.gold...@amdocs.com>
Hi,

Sorry for that.
My consider is that almost every nights(China)/mornings(US) are occupied by 
other community meetings. We can change to 8 next Tuesday evening if it's ok 
for the West Coast folks in US.

Regards,
Chengli

在 2017年7月7日，下午6:24，Alla Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>> 写道：

Hi all,

As Elhay had mentioned, it is middle of night in Israel. If this call is 
scheduled for the suggested time slot, our assigned people will not have any 
possibility to participate. Please kindly consider this.

Best regards, Alla


 Original Message 
Subject: Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule
From: "Yang Xu (Yang, Fixed Network)" 
<yang@huawei.com<mailto:yang@huawei.com>>
Date: Jul 7, 2017, 1:20 PM
To: 
wangchen...@chinamobile.com<mailto:wangchen...@chinamobile.com>,stephen.go...@windriver.com<mailto:stephen.go...@windriver.com>,spat...@research.att.com<mailto:spat...@research.att.com>,vanbra...@att.com<mailto:vanbra...@att.com>,yangyi@chinatelecom.cn<mailto:yangyi@chinatelecom.cn>,Yunxia
 Chen 
<helen.c...@huawei.com<mailto:helen.c...@huawei.com>>,zhang.maope...@zte.com.cn<mailto:zhang.maope...@zte.com.cn>,Alon
 Strikovsky 
<alon.strikov...@amdocs.com<mailto:alon.strikov...@amdocs.com>>,Elhay Efrat 
<elhay.efr...@amdocs.com<mailto:elhay.efr...@amdocs.com>>,bin.y...@windriver.com<mailto:bin.y...@windriver.com>,ma...@research.att.com<mailto:ma...@research.att.com>,Alla
 Goldner 
<alla.gold...@amdocs.com<mailto:alla.gold...@amdocs.com>>,denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>
Good for me!

Sent from HUAWEI AnyOffice
From:Chengli Wang
To:Chengli Wang,Yang Xu (Yang, Fixed 
Network),stephen.go...@windriver.com<mailto:stephen.go...@windriver.com>,spat...@research.att.com<mailto:spat...@research.att.com>,vanbra...@att.com<mailto:vanbra...@att.com>,yangyi@chinatelecom.cn<mailto:yangyi@chinatelecom.cn>,Yunxia
 
Chen,zhang.maopeng1,alon.strikov...@amdocs.com<mailto:alon.strikov...@amdocs.com>,elhay.efr...@amdocs.com<mailto:elhay.efr...@amdocs.com>,bin.y...@windriver.com<mailto:bin.y...@windriver.com>,Mazin
 E Gilbert,Alla Goldner,Lingli Deng
Cc:onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Date:2017-07-07 04:04:53
Subject:Re: [onap-discuss][openlab] OpenLab Kickoff Meeting Schedule

Hi,

If the time slot works for majority folks, I will send invite and logistic next 
Monday.

Thanks,
Chengli

在 2017年7月7日，下午4:00，Chengli Wang 
<wangchen...@chinamobile.com<mailto:wangchen...@chinamobile.com>> 写道：

Hi Subcommittees,

I would like to invite you to attend open lab subcommittee  kickoff meeting. As 
so many meetings scheduled in each week it hard to find more suitable time slot 
for everyone located in different time zone.
I propose our first meeting time is 8:30 am July 12,2017 Beijing time, 8:30 pm 
July 11, 2017, EDT, Is it work for you?

On the Kickoff meeting, I proposed agenda below,

1. Proposed lab specification and guidelines (refer to OPNFV Pharos), linked 
here(Specification, https://wiki.onap.org/display/DW/ONAP+Lab+Specification 
Guide https://wiki.onap.org/display/DW/ONAP+Lab+Guide), Welcome review and 
comments in advance.
2. Discussion on collaboration with Integration team on CI/CD and E2E 
integration test.
3. Solicit Interest of Usecases Integration Testing from Lab Donators

Hope you can join us and feedback.

Thanks and Regards,
Chengli


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Use case subcommittee - agenda for the upcoming meeting this Monday

[Alla Goldner]

Hi all,

Here is agenda for the upcoming meeting.
In case of any additional topics, or concrete use cases proposals for 
discussion, I kindly ask to let me know in advance, so meeting's time can be 
managed accordingly.



1.   Review of suggested Use case subcommittee flow of operation as 
documented here https://wiki.onap.org/display/DW/Usecase+subcommittee , "Use 
case subcommittee flow"

2.   R1 use cases (vCPE and vVoLTE): Status, Open issues, required actions

3.   R2 use cases: the initial proposals

a.   Network Function Change Management?

b.  Enterprise vCPE?

c.   More?

4.   AOB




Note: The previous meeting minutes can be found under 
https://wiki.onap.org/display/DW/Usecase+Subcommittee+Meeting+Minutes

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2F756.96374B60]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Nomination Open for Usecase Subcommittee

[Alla Goldner]

Dear Usecase subcommittee members,

I'd like to self-nominate for Usecase subcommittee chairperson position.
You can see my short resume below.  I am fully committed to this work and 
confident we can achieve great results by collaborative work in the community 
and preparing our inputs in advance for the TSC review and approval.

I am looking forward to work with all of you.

Best regards, Alla


Alla is a Director of Technology, Strategy and Standardization at Amdocs. She 
has over 20 years of varied experience in Telecommunication Standards 
development lead, in Technology Strategy and in System Architecture from 
Alcatel, Motorola, Intel, Marvell and Allot Communications. Alla has wide 
experience of leading standardization work in 3GPP, IETF, ETSI NFV, BBF, ETSI 
MEC, being a Rapporteur and a leading contributor of numerous work items in the 
areas of 5G, Policy Control and Charging, NFV, SDN, Service function chaining, 
Control-User Plane split and Congestion management. She has served on the 
Program Committees of several conferences (e.g. IEEE ICC and IEEE CSCN), 
published at top research venues and holds multiple patents. Her current 
interest is related to network evolution domain with focus on NFV and SDN areas 
both in Standardization and Open Source domains. Alla holds a BSc in 
Mathematics and Computer Science from Tel Aviv University and MSc in Technology 
Management from New York University.


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2EF2B.12773480]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Tuesday, June 27, 2017 7:38 AM
To: onap-discuss@lists.onap.org; onap-tsc <onap-...@lists.onap.org>
Cc: onap-usecase...@lists.onap.org
Subject: [onap-tsc] [onap-discuss] Nomination Open for Usecase Subcommittee

Dear Usecase subcommitters:

The Usecase Subcommittee has been formally approved. I would like to solicit 
self-nominations for the coordinator/chairperson of Usecase Subcommittee.
Any member of the Open Lab Subcommittee may run for this position.  Please 
note, to indicate that you are a member of the Usecase Subcommittee you must 
put your name and email address on the Usecase Subcommittee 
https://wiki.onap.org/display/DW/Usecase+subcommittee

The nomination period will end  4:00 AM UTC, Thursday, June 29.

To nominate, please respond to this email with your intention to run.
After the nomination period is closed, a voting poll will be set up for vote 
collection.

Best regards,



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2EF2B.12773480]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [onap-tsc] Nomination Open for Usecase Subcommittee

[Alla Goldner]

Dear Usecase subcommitters:

The Usecase Subcommittee has been formally approved. I would like to solicit 
self-nominations for the coordinator/chairperson of Usecase Subcommittee.
Any member of the Open Lab Subcommittee may run for this position.  Please 
note, to indicate that you are a member of the Usecase Subcommittee you must 
put your name and email address on the Usecase Subcommittee 
https://wiki.onap.org/display/DW/Usecase+subcommittee

The nomination period will end  4:00 AM UTC, Thursday, June 29.

To nominate, please respond to this email with your intention to run.
After the nomination period is closed, a voting poll will be set up for vote 
collection.

Best regards,



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2EF18.3D1E86B0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] First Use case subcommittee meeting - the summary

[Alla Goldner]

Hi,

Yesterday we had the first Use case subcommittee meeting. Thanks to all 
participants! Here is the call summary:


1.   We had general discussion of what should be Use case subcommittee 
responsibility and the proposed flow/tasks division between a different 
subcommitees/projects/Release management. We have a separate email thread 
handling that discussion. Right now, the flow proposal is following:

1.   Use case subcommittee discuses new use cases

2.   Use case subcommittee produces use case flow diagrams, provides its 
view on the foreseen modules introductions/modifications and suggests potential 
PNFs / VNFs

3.   Use case subcommittee gets feedback from the potentially effected 
projects including integration team on feasibility

4.   Iterate back to 2.

5.   TSC approves the use case

6.   In case new modules or new API introduction is foreseen, architecture 
subcommittee defines the new/modified ONAP flows and the interfaces principles, 
based on the approved use cases

7.   Projects define their extended functionality and their external APIs, 
following those principles.

8.   Detailed per-component flows are defined and projects write their user 
stories / implement them; Integration team continuously works with Use case 
subcommittee to accompany the use case development, review epics/user stories, 
answer questions, etc. Use case subcommittee behaves as system engineers for 
the use case through test start date

9.   Integration team defines the gating use case based on step 8 and 
finalizes the PNFs / VNFs selection, with the help of use case subcommittee, 
architecture subcommittee, PTLs of a different ONAP projects

10.   TSC approves the gating use case

11.   Integration project leads (coordinates) effort to get the gating use case 
tested, repaired, and verified, and the results are documented.



2.   There were no questions or proposals for the existing R1 use cases

3.   Yan Chen has presented Enterprise vCPE Use Case targeting ONAP R2. The 
received comments were to add justification part to the use case description, 
to consider equipment extensions e.g. VNFs, open sourced or commercial, and to 
add flows

4.   As we will have to decide which R1 use cases extension/R2 new use 
cases are beneficial, it is proposed to have justification section per each 
brought use case.

5.   We agreed there are 2 use cases categories: those purely based on new 
models/new configuration and those required components extension/new components 
introduction. The former may not require interactions with projects etc. per 
phases defined in (1), while the latter does. In case of former, we may decide 
to recommend it for inclusion in the present release, and it will be up to 
Integration team to decide whether the task id feasible.

6.   For the R1, we reached step 6 from the Italic list above. Thus, we 
need to get architecture subcommittee feedback urgently. This feedback should 
include:

a.   What architecture subcommittee plans to define for R1 and when

b.  Which decisions should be taken by the projects themselves

7.   Also, a direct communication should be established between the 
Integration team/PTLs of the other projects and the use cases teams to speed up 
the process, per Helen's request. This would follow (6) above i.e. whether 
input is expected from Architecture subcommittee or direct work with use case 
teams can be established. Yoav and Jon from Amdocs (they are cc'ed) are 
contacts for vCPE use case. I asked for the contacts names for VoLTE use case - 
will communicate once I get those.

8.   It was clarified that we should provide our R2 use cases proposal by 
September meeting. This would include steps 1-4 from the Italic list above. For 
that, all interested companies are required to start bringing their R1 use case 
extensions/new R2 use cases proposals ASAP. It would be beneficial to get those 
in advance before each meeting in order to have constructive discussion.

A general point - right now, bi-weekly calls are scheduled. Subject to load and 
responsibilities split, we may decide to move it to weekly meetings. Let's 
discuss it next meeting.

Also, a dedicated use case subcommittee email list was created - please 
subscribe. I plan to move all related email exchanges over there in a week from 
now.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2E9A5.9FCFD840]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Use Case Subcommittee Flow

[Alla Goldner]

Hi Tom,

My understanding is that it is not directly related to our ONAP work. 
This may be taken as an optional part of VNF validation process, per specific 
operator requirements. 

 Best regards, 

Alla Goldner

Open Network Division 
Amdocs Technology





-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TOFIGH, TOM
Sent: Monday, June 19, 2017 5:43 PM
To: SPATSCHECK, OLIVER <spat...@research.att.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Use Case Subcommittee Flow

Are we considering Application Benchmarking as part of the use case efforts?

Certain measurements may be essential to make sure SLAs can be met 
under various conditions.
Thxs
Tom Tofigh 

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of SPATSCHECK, OLIVER
Sent: Monday, June 19, 2017 7:31 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Use Case Subcommittee Flow

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


Based on the discussion in the subcommittee meeting my understanding on how use 
cases get worked from the beginning to the end is like follow:

1. Use case subcommittee discuses new use cases 2. Use case subcommittee gets 
feedback from community including integration team on feasibility 3. Iterate 
back to 1.
4. TSC approval
5. Integration project leads (coordinates) effort to get detailed flows with 
the help of the other projects and the release manager 6. Detailed flows are 
defined and projects write there user stories/implement them 7. Integration 
team tests flows and use case

Did I capture this correctly? Does that make sense to everybody?

Thx

Oliver
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=UY_ZNE-YO2kndJN0BSg2tg=dXwp18p1vFoEvGovHQKaL1Gj-c25cbEFIn_KR7WpyPc=ZUvffeIGYtXNF9Q83mF40QRaizTeLldnVsoWo99SeaY=
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Use case Subcommittee - agenda for tomorrow's meeting

[Alla Goldner]

Hi all,

We are starting Use case subcommittee meetings tomorrow! Here is agenda for Use 
case subcommittee kick off meeting:


1.   General - introduction, charter

2.   R1 use cases - status, questions, connection with projects, tracking

3.   R2 use cases discussion kick off:

a.   Timeframes for proposals

b.  Possible use cases:

   i.  
Potential R1 use cases' extensions in R2

 ii.  New R2 
use cases

The general description about Use case subcommittee: 
https://wiki.onap.org/display/DW/Usecase+subcommittee . Please add your name, 
if you want to become Use case subcommittee member, the membership is open.

The meetings information is here: 
https://wiki.onap.org/display/DW/Use+Case+Subcommittee+Bi-Weekly



Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2E836.AAEBE4F0]

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 
<https://www.amdocs.com/about/email-disclaimer>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss