Re: [onap-discuss] Portal VM failed to brought up widget-ms docker container

[GILBERT, MAZIN E (MAZIN E)]

Lokesh, 

Who do you work for? We would like to keep a list of contributing companies.
mazin




> On Aug 11, 2017, at 7:44 AM, lokesh r  wrote:
> 
> Hi,
> 
> I brought all the onap modules through heat orchestration in openstack newton.
> In portal VM widget-ms docker container failed to run, its exiting attached 
> the screenshot of docker error logs for widget-ms.
> 
> docker logs for widget-ms container - widget-msdockererrorlogs.png
> portal.sh stdout and stderr log file - portal.log
> 
> Kindly help us in resolving the issue.
> 
> Thanks,
> Lokesh.
> ___
> 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=IKSC5mg8GeOiSar1dax3GQ=jN679uu5gA4hHpofCro05AHSUWnh4OBl8UfoUyNB5W8=X2a6IPDFEBorbQiVyBguPZPJ60vsttrtTjOZYnUHkRA=
>  

___
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

[GILBERT, MAZIN E (MAZIN E)]

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

___
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=IKSC5mg8GeOiSar1dax3GQ=j5Joirsx9DTraFhodiUPAmT5WtlmQuhQMQ6ikZlV0TE=Vzxr-EAzE8erKKMRIxz-OHjPYmu4fdXjt9ea5dWgM6o=
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Draft of TSC Charter Section 5.4.1 Changes

[GILBERT, MAZIN E (MAZIN E)]

Thank you Kenny,

I encourage the ONAP community to review the proposed changes below and provide 
feedback.
We want to finalize this in one week. The TSC will then review and vote.

Mazin



On Jul 24, 2017, at 5:53 PM, Kenny Paul 
> wrote:

The proposed changes to Section 5.4.1 have been posted to the TSC wiki page
 
https://wiki.onap.org/pages/viewpage.action?pageId=4719160

Sorry for the delay but I did not have an editable version of Charter v.7.1 
available to me to redlined and I got that this morning.

What is reflected in the v7.2.1 draft are:
- numbering changes to facilitate a line-by-line vote as was recommended by Ed 
Warnicke
- a page break for the sake of readability
- the text discussed at the July 20th TSC meeting below:

5.4.1.2 Each subcommittee may elect a Chair or Vice-Chair who is responsible 
for leading meetings and representing the subcommittee to the TSC.

5.4.1.3 The Chair or Vice-Chair will be elected by members of the subcommittee 
as of the date the nomination process starts for the election.

5.4.1.4 Voting for a Chair or Vice-Chair not limited to member companies 
however only 1 Subcommittee member from each company, or group of related 
companies (as defined in section 7.4 of the ONAP Project Charter) may vote in 
the election.


Not reflected in this draft is language around from Rajesh Gadiyar, Susana 
Sabater and Bob Monkman around the diversity of participation in leadership 
positions.
I did not include this as A) the language had been inadvertently omitted from 
the discussion and B) the intended scope of those provisions extends beyond the 
specific changes to the topic of Steering Committee elections to also include 
PTL and Community Coordinator roles.  I will with Susana, Bob and Rajesh on the 
specific language around that to be presented at the August 3rd TSC meeting.

Please let me know if you have any questions.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
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=IKSC5mg8GeOiSar1dax3GQ=UNKen1fs4ejCf862AlleVo3HNxfdUuBM8SAbP3PFpe4=LRP_uTu46KNtzOcv6P8g10MJ2bJjK5l1E3ilxUYG4AM=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] #PTL

[GILBERT, MAZIN E (MAZIN E)]

PTL Team, 

Some projects have made an outstanding job on reducing and cleaning-up the 
committers' list.
Please review committers in your project and approach them to ensure their 
commitment
and appropriate role in your project. Let’s stick to up-to 2 committers per 
company.

Phil and I will review where we are in the TSC meeting Thursday.

Thank you!
Mazin
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] sdc committers

[GILBERT, MAZIN E (MAZIN E)]

Yuan Yue,

I have not examined this particular project, but the TSC and I have requested 
last week during the review phase of projects for R1,
that the PTLs clean up the list of committers to 3-5, as some are more 
qualified to be contributors than committers.
We have projects with 16-20 committers and 2-3 contributors. PTLs should work 
with their project team to clean-up
the list to a core set of committers but should do it in total transparency and 
openness. If the TSC needs to provide clearer guidelines then we
can discuss today in our TSC Meeting.

thanks
Mazin


On Jul 6, 2017, at 4:42 AM, yuan@zte.com.cn 
wrote:


Hi Michael and Phil,


I wish this is just an unintentional mistake during synchronizing information 
between "approved SDC proposal page" to "Resources and Repositories" in the 
wiki page. Otherwise I would be greately confused on the pratice of removing 
committer from an approved project acording to the procedure we have defined on 
TSC Charter:


A Committer for a project who is disruptive, or has been inactive on that 
project for an extended period (e.g., six or more months) may have his or her 
Committer status revoked by the project’s Project Technical Leader (PTL) or by 
super-majority vote of the project’s committers.

The Project Technical Leader is responsible for informing the Technical 
Steering Committee (TSC) of any committers who are removed or resign.


Is there any explanation on the issue Zhaoxing mentioned in his mail?


Best Regards,

Yuan Yue



原始邮件
发件人：孟照星10024238
收件人： >;
抄送人： >; 
>;
日 期 ：2017年07月06日 14:45
主 题 ：[onap-tsc] sdc committers


Hi Michael,

I noticed that some of the committers have been removed from Resources and 
Repositories
 even though they're listed as committer in the approved SDC proposal 
page
 .
There is a guideline from TSC about project participants, for community 
diversity, a project is encouraged to have at least three companies involved, 
Currently only 2 in SDC. Given that ZTE has seed codes for SDC listed in the 
approved proposal page for Catalog, workflow designer and VNF designer, I think 
the committers from ZTE should also be listed at the Resources and Repositories 
page.

Thanks and Regards,
Zhaoxing






___
ONAP-TSC mailing list
onap-...@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=zagCM6lrm4jcHVIcirLmNorTBnCLgbojm4GVc3NWGnA=WzM6PSwQz7jZ2SxUp_oMzcrP2JB3z4oWonomCFpPfPg=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [onap-tsc] Modelling discussion on Friday May 5th

[GILBERT, MAZIN E (MAZIN E)]

Rittwik, Deng,

This is great. Thank you  for taking the lead.

I realize the focus is on TOSCA and parsers. Wonderful!
I want to take you one level higher to start by discussing
what the framework look like for the information model. Perhaps  invite folks 
who have
operational experience. Then start describing the differernt
data models and how TOSCA plays a role in driving service chaining and micro 
services
(like analytics, data collections, etc).

It would be great if the outcome of this mini session to
be a recommendation position/paper or a proposal for a project.

Mazin



On Apr 20, 2017, at 4:34 AM, denghui (L) mailto:denghui12 at huawei.com>> wrote:

Hello all

We are happy to let you know that we are hosting a modeling session on Friday, 
May 5th, AT Lab.
9:00-10:30 Shitao moderate: TOSCA NFV Profile
10:30-12:00 Rittwik moderate: AT Parser
13:30-16:00 DengHui moderate: Modelling & Opendeployment

Please kindly help to let us know if you are interested in joining us, so that 
we can book a proper meeting room for our discussion

Best regards,

Rittwik & DENG Hui
___
ONAP-TSC mailing list
ONAP-TSC at lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y=HRoKLiOZCWLzl3Z-00DLQIUCwCAWqQL50mUFHtfYXYA=731fuCUnXbuPSOGHEcVf4U29cHpOGPKmwevRHGAoeiY=

-- next part --
An HTML attachment was scrubbed...
URL: 

Re: [onap-discuss] [onap-tsc] Proposal for structuring Modeling projects

[GILBERT, MAZIN E (MAZIN E)]

Jason

The VNF-SDK and ICE teams are in discussion of a merger and a consolidated plan 
with co-leadership.At least that is my expectation and hope.
CLAMP is for control loop automation. The development and design of templates 
that drive control loops can be part of SDC, including initial orchestration of 
the loop and policy definitions.
However, you need a runtime configuration environment (portal) that enable 
configuration and updates of policies, etc.

Let’s make sure we are not mixing design from run-time.

Mazin







On May 10, 2017, at 1:38 PM, Jason Hunt 
> wrote:


Andrei,

Thank you for bringing this topic up.  It's important that we minimize overlap 
in projects to maximize the impact of the contributors.

In my basic understanding, VNF-SDK and ICE have substantial overlap.  Can we 
investigate how these two projects can merge?

As for CLAMP and Policy Framework, it seems that they both would contribute 
design tools into SDC.  As I understand it, SDC should be able to support the 
design of all the elements that make up a VNF package (including workflows, 
analytics microservices, directed graphs for controllers, policies, etc.)  I 
would expect that each project that requires a design element would create that 
design element themselves and plug that into SDC... rather than the SDC project 
trying to design everything. For example, today directed graphs in the 
controllers are built directly in the Node-RED tooling in the controller, but 
this should in the future be accessible via SDC.  Is that your understanding?

I welcome others' input on this.

Thanks!

Regards,
Jason Hunt
Executive Software Architect, IBM

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


- Original message -
From: Andrei Kojukhov 
>
Sent by: onap-tsc-boun...@lists.onap.org
To: onap-discuss 
>, 
"onap-...@lists.onap.org" 
>
Cc:
Subject: [onap-tsc] Proposal for structuring Modeling projects
Date: Wed, May 10, 2017 9:46 AM


Dear all,



Currently there are 6 draft projects in ONAP that deal with modeling, 
onboarding and certification. The below table summarizes the 6 initiatives and 
presents the feature coverage of each one of them.





ONAP Project


Features covered by the project


VNF/Service Design


VNF Guidelines


VNF Certification


VNFD/VNF package onboard


Modeling – overall modeling issues


V











Incubation and Certification Entity (ICE)





V


V


V


Service Design and Create (SDC)


v


V


V


V


VNF-SDK


V


V


V


CLAMP


V











Policy Framework


V















Besides an overlap in content and resources allocation of contributors, my 
expectation is that there will be issues with synchronization of requirements 
such as VNF guidelines and requirements derived from Use cases as well as 
maintaining open source.

Therefore, I’m proposing to consider structuring the above described ONAP 
projects. One of possible umbrella projects may be SDC covering most if not all 
the design and onboarding related features.



The Service Design and Create can be seen as one candidate as unified platform 
for

· Validation and verification of VNF guidelines,

· VNF/Service Design studio

· Standard VNFD/VNF package onboarding platform based on ETSI NFV 
SOL001, SOL004 specifications leveraging TOSCA YAML modeling and CSAR packaging

· Multilayered VNF Certification including VNF package integrity and 
authenticity validation, VNF deployment and running VNF tests verifying 
non-functional VNF KPI’s that are currently specified in ETSI NFV EVE011 work,

There may be different options of structuring all or part of the ONAP 
initiatives as shown in the following pictures.



Option 1: SDC umbrella







Option 2: “Design Automation” umbrella including on-boarding and certification







Option 3: “Design Automation” umbrella excluding on-boarding and certification







I would like to invite ONAP community members to provide their view on possible 
structuring.





BR,



Andrei







Andrei Kojukhov, PhD



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 

Re: [onap-discuss] [onap-tsc] Project Proposal: External SystemRegister

[GILBERT, MAZIN E (MAZIN E)]

LiZi,

Thanks for putting the proposal together. The TSC will be continuing a review 
cycle over the next 2 weeks.
I realize the difference and the need of having a system register for external 
communications,
but the question is whether this should be a separate project that may cause 
further dilution.
If the technology and the algorithms used for supporting ESR are similar to 
others like those
used in A, but the type of data is different then I don’t see the need for 
separate systems.

I can see many situations like life cycle management of VNFs using closed loop 
automation where
doing post health checks are critical after repairing a failure. So having both 
platform and external system
data available in one place are key.

In general, the TSC will look very closely on projects that need merger to help 
unify the community
and strengthen the developer ecosystem. You are getting good feedback from the 
community and
I suggest you look closer.

Regards,
Mazin




On May 17, 2017, at 5:31 AM, li.z...@zte.com.cn 
wrote:

Hi Avi,

ESR will not only store and manage configuration of VIM, but also the 
configuration of VNFM/SDNC/EMS. It provides a service to centralized management 
of the information of different kinds of external systems. And it will be used 
by SO/SDC/VF-C etc.
When comes to multi-vim, we suggest that multi-vim using ESR as a dependency 
component, obtaining the connect information and status of VIM from ESR. For 
this point, we can have a further discussion.


Best regards,

LiZi




原始邮件
发件人： ＜avi.chap...@amdocs.com＞;
收件人： ＜dr6...@att.com＞;李滋00164331; 
＜jpianigi...@juniper.net＞;
抄送人： ＜onap-discuss@lists.onap.org＞; 
＜onap-...@lists.onap.org＞;
日 期 ：2017年05月17日 00:31
主 题 ：RE: [onap-tsc] [onap-discuss] Project Proposal: External SystemRegister

Hi,

Reading the project scope it seems to me a real time configuration repository 
for external system location and credential specifically for VIM.
Probably this should be part of the multi-vim project which should own and 
manage this configuration.

I assume that  the component which is used for  storing/managing this 
configuration can be shared across different projects and/or might offered to  
be a service  which any component can use.

Avi,


From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Tuesday, May 16, 2017 6:51 PM
To: li.z...@zte.com.cn; 
jpianigi...@juniper.net
Cc: onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] Project Proposal: External System 
Register

I have to agree with Jacopo and Steve, that’s not business logic that’s basic 
endpoint health checking.

So to clarify on my and their inputs, it still seems like to me that the entire 
scope of this project is covered by some combination of A, ONAP OM or MSB 
depending  on who you ask / how you look at it.

ONAP Operations manager in particular mentions (Which seems to cover most of 
your stuff.)

•  Platform Monitoring & healing: Monitor platform state, Platform health 
checks, fault tolerance and self-healing

Can you please work with someone like David Sauvageau on that project to be 
sure you have no overlap?

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
li.z...@zte.com.cn
Sent: Tuesday, May 16, 2017 12:49 AM
To: jpianigi...@juniper.net
Cc: onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Project Proposal: External System 
Register


Hi Jacopo,



Thanks for your quick response. The business logic can be information 
verification before store the data to A, and heartbeat detection of the 
system state.

For example, a user sent the authentic url, tenant, username and password of 
VIM to ESR. ESR try to connect the VIM with these information. After authentic 
succeed, ESR store these VIM information to A, do heartbeat detection for 
VIM status and present  the system status to user.



Best regards,

LiZi






原始邮件
发件人： ＜jpianigi...@juniper.net＞;
收件人：李滋00164331;
抄送人： ＜stephen.terr...@ericsson.com＞; 
＜onap-...@lists.onap.org＞; 
＜onap-discuss@lists.onap.org＞;
日 期 ：2017年05月16日 11:32
主 题 ：Re: [onap-tsc] Project Proposal: External System Register


Not clear what the 

Re: [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting

[GILBERT, MAZIN E (MAZIN E)]

I was not present for this discussion. We need to have a meeting around the 3rd 
week of
July to go through project by project progress. Phil and I discussed a virtual 
meeting
since folks will be too busy to travel, and some may not be able to.

Would like to get a sense from the TSC community if this is appropriate and more
convenient while voting for dates.

thanks
Mazin

On Jun 12, 2017, at 1:08 PM, Kenny Paul 
> wrote:

Please respond to the doodle poll below no later than:
Thurs. 01:00 PM UTC
Thurs. 09:00 PM China
Thurs: 09:00 AM Eastern
Thurs: 06:00 AM Pacific

https://doodle.com/poll/7zufivqebtnvrhdt

Thank You.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

___
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=IKSC5mg8GeOiSar1dax3GQ=7n6f3RBF3LtkjuBpPhqrMbVfiHC_wqVOfDz5z3uutjM=8D2aZuG-pN820woJDvlHxyXQnkAsRt0bFjokAPWgc1E=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Framework for proposed projects feedback

[GILBERT, MAZIN E (MAZIN E)]

ONAP Team,

I want to thank you again for working so hard in proposing projects. Per our 
TSC meeting
today, I am enclosing the framework that the TSC committee developed for 
scoring and
providing feedback on each project. I expect you will get feedback from the TSC 
committee
starting next week.

Thanks
Mazin

Framework for TSC Project Feedback

1.Clarity

a. Reasonable and well defined scope

b.Identification of software modules and APIs being developed and delivered 
to ONAP and other components.

c. Following project and LF guidelines for contributors/committers

d.Identification of dependencies and assumptions on other components and 
open source.

2.Overlap

a. Intentional and unintentional overlap

b.Overlap with external open source efforts

3.Risk management

a. Sufficient development resources allocated to deliver on time

b.At least 3-4 companies involved to provide diversity

c. Availability of seed code and its maturity

4.Relevance and prioritization

a. Alignment with merger release

b.Alignment with use cases

c.Sound technical solution for solving a real need




___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Projects

[GILBERT, MAZIN E (MAZIN E)]

Team, 

First, thank you for spending a week in NJ brainstorming, planning and 
architecting our next 4Q17 release.
Our next step is to have the smaller community teams flush out their project 
proposals, fill in gaps, and communicate
with other teams to consolidate proposals in the case of overlaps. Please 
notify us if your proposal is ready to be 
reviewed for feedback. I expect the majority of proposals will be in that stage 
before our Thursday TSC meeting
on May 11th.

Have a wonderful weekend.
mazin


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] TSC F2F meeting in Paris

[GILBERT, MAZIN E (MAZIN E)]

ONAP Community,

We are really excited about our next face to face meeting in Paris, hosted by 
Nokia.
This is a critical meeting as we will review our Amsterdam release and make
key decisions about the Beijing release.

There are limited spots, so please register at your earliest convenience.
The place has limited seats.

Here is the link for info and registration.

https://wiki.onap.org/display/DW/ONAP+Developer+Event+September+25-28%2C+2017%2C+Paris-Saclay%2C+France

Look forward to seeing you all.
Mazin

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Rewarding committers and coders

[GILBERT, MAZIN E (MAZIN E)]

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







___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ~

[GILBERT, MAZIN E (MAZIN E)]

Srini,

So that the ONAP community can better support you and the user community, it 
would help
to know the company each individual works for. This will help the Linux 
Foundation to better
report their statistics on progress.

thanks
Mazin



On Aug 24, 2017, at 3:06 PM, Srinivasa Goda 
> wrote:

Hi,

I've some trouble installing ONAP on OpenStack. I'm not sure if this is right 
group. If not, would someone help me with right group to post questions on 
ONAP. And thanks in advance and sorry if this is wrong group.

My question is,

I'm installing ONAP using 'openstack stack create -t ONAP_OPENSTACK.YAML -e 
ONAP_OPENSTACK.env '.

My installation is failing with insufficient resources. But I've 128GB RAM and 
~2 TB hard disk. Every time I run install command, complete disk, 2 TB of it, 
is written and host freezes.

Any clue what could be happening here.

Thanks,
Regards,
Srini

[Beta Tester Badge 3]
___
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=IKSC5mg8GeOiSar1dax3GQ=Pnk1HGSP2UKtYHpWij61QvBU7MSIOvHFgv3SQUH065A=MlHi0cy3c7JoUbfjcvL__QgGonwuWGetvd6DdBafxvE=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] So pass M4

[GILBERT, MAZIN E (MAZIN E)]

Congratulations to the SO team. Well done.
Mazin



On Oct 9, 2017, at 1:47 AM, Seshu m 
> wrote:

Thanks Gildas...



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!
 
*

From: Gildas Lanilis
Sent: Monday, October 09, 2017 10:57 AM
To: Seshu m
Subject: So pass M4

Hi Seshu,

I see SO reached 30.3% code coverage, so SO has passed M4.
I have updated status accordingly in wiki.


Thanks,
Gildas


Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
gildas.lani...@huawei.com
Mobile: 1 415 238 6287

___
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=IKSC5mg8GeOiSar1dax3GQ=N4XtT1OLOpEyr0EY95oGnZJqGHIq5OyjgXJbwHAV6gc=Ynq6skp9TbPXbM3hVUtPS8_mGcZjTY_m7mswKDvW8Co=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] newbee question

[GILBERT, MAZIN E (MAZIN E)]

AS
Please identify which company or institute you are part of so we track 
contributors and inquirers.
AT ECOMP and LF ONAP are aligned.

Mazin





On Nov 15, 2017, at 3:22 PM, Andrey Selivanov via onap-discuss 
> wrote:

Hi!

How  ONAP official release (e.g. Amsterdam) corresponds to ECOMP software code 
base currently in production at AT (about 2 years I've heard)?
Is it 2 completely different software projects from AT point of view? Do they 
collide in future?
Sorry for stupidity).

wbr,
AS





.
___
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=IKSC5mg8GeOiSar1dax3GQ=DbhlkUFNHq6CyB96LwdRKz3dc9YvFxqskS7bCwPKRT8=oa81UchgBgBIyTKMjX6gGAGke5fwJFAge3AFEhWLNc0=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] ONAP Meeting in Santa Clara

[GILBERT, MAZIN E (MAZIN E)]

Colleagues and Friends,

On behalf of the TSC and the LF,  I want to congratulate every one of you for 
your outstanding collaboration in delivering
Amsterdam. The goal and timeline were far reaching, but yet this community 
delivered the
impossible. I am truly honored and excited about what we delivered and what 
Chapter 2
looks like for our the Beijing release.

We will celebrate in style at the Santa Clara meeting, hosted by Intel. I do 
want to encourage you  to
attend the meeting. Agenda will go out by Monday or Tuesday. If you are 
attending, it is
vital that you register asap. The link is at

https://wiki.onap.org/display/DW/ONAP+Beijing+Release+Developer+Forum%2C+Dec.+11-13%2C+2017%2C+Santa+Clara%2C+CA+US

Congratulations, and see you in Santa Clara.

Mazin

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Modeling

[GILBERT, MAZIN E (MAZIN E)]

Deng Hui,

Thanks for your presentation today, and I really appreciate the modeling 
committee working together. Lots has been accomplished since R1.

I just wanted to articulate the conversation main points.

1. Modeling approaches for ONAP releases should be approved by the TSC. This 
should be documented and approved no later than M2.

2. If the modeling committee is unable to interlock on a common approach for 
offline, documentation or runtime, then different options should be brought to 
the TSC for review and making a decision.

Modeling directly impacts deployability. Disagreements impacting R3 should be 
documented and brought to the TSC over the next 2 weeks.

Thanks!
Mazin
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [modeling] Help on ONAP R2 Data Modeling verification

[GILBERT, MAZIN E (MAZIN E)]

Thanks Deng
That is surprising. Can each company with strong interest in this offer one 
coder please.  This is a key activity and can’t be coded by 2 coders. This will 
impact our Casablanca release.

Thank you all!!

Mazin

Sent through AT's fastest network

On May 2, 2018, at 6:08 AM, denghui (L) 
> wrote:

Hello all

We have more than 10-20 companies regularly to talk about ONAP modeling , but 
unfortunately we have only 2 coders contributing ONAP R2 modeling code 
contribution.
Victor has worked on this more than 1 week, and felt that he can’t do such huge 
work just by himself, so he has create below jira to invite more contributors

I create JIRA tickets to track the status for R2 DM 
Verification：

1.  
https://jira.onap.org/browse/SDC-1291

2.  
https://jira.onap.org/browse/SDC-1290

3.  
https://jira.onap.org/browse/SDC-1289

4.  
https://jira.onap.org/browse/SDC-1288
  Owner: Dejan from ericsson

5.  
https://jira.onap.org/browse/SDC-1287
  Owner: Dejan from ericsson

6.  
https://jira.onap.org/browse/SDC-1286
  Owner: Victor Gao

If you could help, please come and help on first 3 bullets.
Many thanks for your help

Best regards,

DENG Hui
___
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=IKSC5mg8GeOiSar1dax3GQ=7osx5auWQIBPX6fsZAYS6n7rKCLzv2nUaoahw5ZGS40=TOh2rQvHE5Kdn2xb2WMuTVnLoZK2KOA5MsIoGB1O-zw=
___
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

[GILBERT, MAZIN E (MAZIN E)]

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

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
___
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=IKSC5mg8GeOiSar1dax3GQ=7VBK7vn4mMMbbTBo_UbIrby0L3gd_KvI_MskXwqLW-k=Y63nXwhDh5uYEaYn9pj-mMgdhOa5KZzTbaZj3NWvzgg=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] MUSIC Proposal for Beijing

[GILBERT, MAZIN E (MAZIN E)]

TSC Members,

I met this afternoon with members of the OOM project and MUSIC team.
I confirmed the following

Although on the key common area among both projects is resiliency,
OOM’s scope is life cycle management of the ONAP platform itself.
Scope is the following
https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project

MUSIC, on the other hand, is focusing on database resiliency/scalability across 
sites.
MUSIC and OOM are complimentary, and MUSIC is optional and is relevant to only
few projects. Per authors, the scope is the following

MUSIC is a shared service with recipes that individual ONAP components and 
micro-service
can use for state replication, consistency management and state ownership 
across geo-distributed sites.
MUSIC will make sure that the right service data is available at the right 
place, and at the right time
to enable federated active-active operation of ONAP.

The OOM team recommended that MUSIC should be an independent project.
My criteria are for architecture input which has been vetted already. OOM
to provide recommendation which they have, and finally, the TSC to vote.

Kenny will shortly send out a vote for MUSIC. Please go ahead and vote
as +1, 0, -1. If you have not been part of the discussions and have questions,
then please follow up directly with the OOM and MUSIC teams.

Thanks, and appreciate everyone for doing their due diligence.

Mazin




___
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]

[GILBERT, MAZIN E (MAZIN E)]

+1

Please add the candidate’s company plus existing committers.


On Jan 11, 2018, at 6:57 PM, MAHER, RANDA 
> 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

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
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y=NXGqSa5NxTHo7zyxUrPP49eLYsmXzI4yh64s3B4oM5A=Evsqbp4rRCVLOh5p5fjHYs14lo95L06AtvAB_oZldfM=

___
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

[GILBERT, MAZIN E (MAZIN E)]

Phil,

On behalf of the ONAP community and its members, I want to thank you and the LF 
for making this happen.

I expect and hope this will encourage significant participation.

Mazin

Sent through AT's fastest network

On Jan 27, 2018, at 12:47 AM, Phil Robb 
> wrote:

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
 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
___
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=IKSC5mg8GeOiSar1dax3GQ=qxdWttB_80KqwMJc2HNyUCZIJiRUEWTpCOlouDvl-i4=b6q0zaCIKOp4hRspauDHlUUXLT7hqhPugMvuwaemROM=
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] CLAMP meaning?

[GILBERT, MAZIN E (MAZIN E)]

Control Loop Automation Management Platform




On Feb 12, 2018, at 5:49 AM, Thovalai, Sundar 
> wrote:

Hi Lars

The ONAP documentation says Closed Loop Automation Management Platform, so I 
guess that is the official interpretation of what CLAMP means?

http://onap.readthedocs.io/en/latest/submodules/clamp.git/docs/#

Sundar

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lars-Erik Helander
Sent: Monday, February 12, 2018 10:37 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] CLAMP meaning?

What is the official interpretation of the CLAMP abbreviation?
In descriptions I have seen both "Control Loop" as well as "Closed Loop" being 
mentioned as the meaning for CL in CLAMP.

As I understand the intention of CLAMP is to support both closed loop and open 
loop control, the "Control Loop" interpretation seems most appropriate.

Anyone that can clarify?

/Lars

-
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
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=IKSC5mg8GeOiSar1dax3GQ=8l4wAXpQdZvao8J06Gvxl4Q8XArL9k2cp7D-NulErzc=JTBh5Ir4t0t-_DLH2085QwR1iEFR2a5Qw1PhhTeB3pk=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

[GILBERT, MAZIN E (MAZIN E)]

This was the goal of the software architect subcommittee or system engineering 
subcommittee.
We agreed that we would have a coordinator instead who would work under the
architecture committee and with all PTLs to exercise the S3P criteria and other
Beijing requirements. We also agreed last month that each PTL will get back to 
the TSC to
tell us what they level they can meet and how.

Kenny
Let’s please add this to the TSC meeting tomorrow.
Mazin





On Jan 3, 2018, at 12:02 AM, Alla Goldner 
> wrote:

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




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 >
Cc: onap-...@lists.onap.org; onap-discuss 
>; 
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 >
Date: Tuesday, January 2, 2018 at 2:58 PM
To: Helen Chen 00725961 >
Cc: "onap-...@lists.onap.org" 
>, onap-discuss 
>, 
"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
Twitter: @DJHunt




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

Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release

[GILBERT, MAZIN E (MAZIN E)]

Thanks Roger.

Have there been other groups who have managed to bring up Amsterdam with OOM 
(with and without DCAE)?
Can you point me to any so I can understand their experience.

mazin


On Jan 3, 2018, at 11:15 AM, Roger Maitland 
> wrote:

Hi Helen,

David is on vacation so I’ll answer - OOM is ready.

The OOM team has been working with the Integration team and the entire ONAP 
community to create the 
amsterdam
 release of OOM which is now available.  There is a continuous delivery system 
that deploys the master branch of all of the ONAP components with OOM – 
here
 is the dashboard.  As this system is effectively continuously evaluating ONAP 
health this should be very useful for the Integration team to quickly identify 
component submissions that result in a degradation.

The initial version of DCAE support is under final testing.  This version 
brings up the DCAE controller which then brings up the rest of the DCAE VMs.  
There is a discussion scheduled for tomorrow between the OOM and DCAE team on a 
more fully containerized solution.  The OOM team is also working on deploying 
OpenStack DNS Designate to simply the deployment of OpenStack infrastructure 
required for DCAE.  We’ll let the community know when this is ready.

Cheers,
Roger

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yunxia Chen
Sent: Tuesday, January 2, 2018 5:25 PM
To: onap-discuss 
>; Sauvageau, 
David >
Subject: [onap-discuss] [integration][oom] OOM readiness for Beijing release

Hi, David,

Happy new year and it was very nice to talk with you at Santa Clara. Is OOM 
ready for Integration team to take over to test the Beijing release, maybe 
start with Amsterdam project first? From last meeting, it seems have a little 
bit issue on DCAE, has it resolved yet?

Regards,
Helen Chen
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-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=IKSC5mg8GeOiSar1dax3GQ=_dlaJi5cUYGfdQpkrTvOLmwKf9nHldPQl5dmZYtz2iQ=j7WSvxdz-fKgmH76NuG-x2cW3E_oZL4nU8OuXiW1ylM=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Modeling

[GILBERT, MAZIN E (MAZIN E)]

Thanks you. Also please share with the TSC what requirements your subcommittee 
generated so the TSC can assess the different views.

Mazin
On Jun 20, 2018, at 12:08 PM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Hi Mazin

We will try to summarize the major disagreements and bring it to TSC in next 2 
weeks.

Thanks a lot

DENG Hui



From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Wednesday, June 20, 2018 11:33 AM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-tsc 
mailto:onap-...@lists.onap.org>>
Subject: Modeling

Deng Hui,

Thanks for your presentation today, and I really appreciate the modeling 
committee working together. Lots has been accomplished since R1.

I just wanted to articulate the conversation main points.

1. Modeling approaches for ONAP releases should be approved by the TSC. This 
should be documented and approved no later than M2.

2. If the modeling committee is unable to interlock on a common approach for 
offline, documentation or runtime, then different options should be brought to 
the TSC for review and making a decision.

Modeling directly impacts deployability. Disagreements impacting R3 should be 
documented and brought to the TSC over the next 2 weeks.

Thanks!
Mazin

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

View/Reply Online (#10492): https://lists.onap.org/g/onap-discuss/message/10492
Mute This Topic: https://lists.onap.org/mt/22460897/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] PTL Election announcement for ONAP modeling project

[GILBERT, MAZIN E (MAZIN E)]

Deng,

I appreciate you holding an election for the PTL.

For the modeling project PTL election, we need each Chair to ensure they have 
vetted all
active committers before any election is taking place. Can you share the list of
active committers.

As outlined in the website the issue is different for the subcommittee modeling 
Chair.

It seems that you are initiating a PTL election and not a subcommittee modeling 
Chair election.
Please confirm, and share the list of active Committers who will be voting for 
the new PTL.

thanks
mazin








On Jul 4, 2018, at 2:14 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Dear ONAP Community and ONAP TSC,

As mandated by ONAP process, PTL elections must be held at least once a year.
You can read more details here: 
https://wiki.onap.org/display/DW/Annual+Community+Elections

if you are interested in this position, I invite you to submit your 
self-nomination for ONAP modeling project.

Important dates:
---
You have 2 days to submit your self-nomination from receipt of this email. (End 
by July 6th 2018 10:00 IST)

Election duration: July 6th 2018 12:00 IST -  July 11th 2018 12:00 IST
(from CVIS system, private email will be sent to all committers email id 
mentioned 
athttps://wiki.onap.org/display/DW/Resources+and+Repositories
 )

Election result: July 11th 2018 (will be announced in onap-discuss and onap-tsc 
mailing lists)



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

View/Reply Online (#10854): https://lists.onap.org/g/onap-discuss/message/10854
Mute This Topic: https://lists.onap.org/mt/23036778/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] PTL Election announcement for ONAP modeling project

[GILBERT, MAZIN E (MAZIN E)]

Thanks. I am assuming the project is based on the repo that is supporting the 
Tosca Parsers,
and you are tracking active committers.

Are you holding an election at the same time for the Chair subcommittee?

Mazin


On Jul 5, 2018, at 8:21 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Mazin

Yes it is modeling project PTL election other than modeling subcommittee.

You may have missed below email which does have the link to repositories
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-Modeling<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DModeling=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=h336thy4AQC9X1JMXCsyYKGnG9RZQiRvWQY-u54zaMI=ffAQ4YaMD5X0xX09fOLdQR9a4020jv33Vw3hzajOwBA=>
the committers in modeling project are:
Hui Deng
Shitao Li
Rittwik Jana
Bruce Thompson
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Arthur Berezin
Sandeep Shah
Ling Li
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

I did send email to helpdesk to remove 3 of them from the list before based on 
the confirmation of project:
Bruce Thompson
Arthur Berezin
Ling Li

It seems that they are still here, I will send again to helpdesk
So the final qualified committers are:
Hui Deng
Shitao Li
Rittwik Jana
Maopeng Zhang
Zhaoxing Meng
Amir Levy
Sandeep Shah
Liuhe Zhong
Yannan Han
Hu Dong
Serban Jora
Lingli Deng

Thanks for your checking
Best regards,

DENG Hui


From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Thursday, July 5, 2018 7:35 PM
To: denghui (L) mailto:denghu...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org>
Subject: Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP 
modeling project

Deng,

I appreciate you holding an election for the PTL.

For the modeling project PTL election, we need each Chair to ensure they have 
vetted all
active committers before any election is taking place. Can you share the list of
active committers.

As outlined in the website the issue is different for the subcommittee modeling 
Chair.

It seems that you are initiating a PTL election and not a subcommittee modeling 
Chair election.
Please confirm, and share the list of active Committers who will be voting for 
the new PTL.

thanks
mazin







On Jul 4, 2018, at 2:14 AM, denghui (L) 
mailto:denghu...@huawei.com>> wrote:

Dear ONAP Community and ONAP TSC,

As mandated by ONAP process, PTL elections must be held at least once a year.
You can read more details here: 
https://wiki.onap.org/display/DW/Annual+Community+Elections<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Annual-2BCommunity-2BElections=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=Oej6QUk5p2KdqNEWySpOHA=aqtE2C1ZdfxIEpvFpsi-ywKvepAjMEEvXvpyXwKvr7o=1VOSZREkf7OvEcmx6COn9S0Mz80ACCfrmsVXjmhZwZs=>

if you are interested in this position, I invite you to submit your 
self-nomination for ONAP modeling project.

Important dates:
---
You have 2 days to submit your self-nomination from receipt of this email. (End 
by July 6th 2018 10:00 IST)

Election duration: July 6th 2018 12:00 IST -  July 11th 2018 12:00 IST
(from CVIS system, private email will be sent to all committers email id 
mentioned 
athttps://wiki.onap.org/display/DW/Resources+and+Repositories<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=XBYNhzlk2jx6nSVGWpJjJUhpTLxHynkr7bh6Vp5VOXU=odKqVMZCdJUsygPKUpW7Gk3KS-ALAv3Pe3CO5I_82Ls=>
 )

Election result: July 11th 2018 (will be announced in onap-discuss and onap-tsc 
mailing lists)




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

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

[onap-discuss] ONAP subcommittees - reminder.

[GILBERT, MAZIN E (MAZIN E)]

Team, 

The TSC has approved a number of subcommittees in the past. I would like to 
encourage each 
subcommittee chair to share updates with the TSC on a regular basis - either 
through email or
at the TSC Thursday meetings. It is important that the TSC is knowledgable and 
agree of the workplan of the 
subcommittees. Each subcommittee should plan to provide a readout about once a 
month to the TSC.

thanks
mazin


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Action Plan towards Casablanca

[GILBERT, MAZIN E (MAZIN E)]

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 
> 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 
requirements/functionalities.

For that, we need to get your revised high level proposals per (2) and (3) by 
our April 9th meeting. Please talk to me in case of any questions.

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
___
onap-discuss mailing list

Re: [onap-discuss] [onap-tsc] Action Plan towards Casablanca

[GILBERT, MAZIN E (MAZIN E)]

Chris

As Phil mentioned, this is a subcommittee of the LFN end-user advisory 
committee and does not need the approval, scope or charter
of our TSC. Phil can share status and plan.

Nevertheless, I agree that it is important for our TSC to review but we will 
not slow down the process.
thanks
Mazin

On Mar 30, 2018, at 10:45 PM, Christopher Donley (Chris) 
<christopher.don...@huawei.com<mailto:christopher.don...@huawei.com>> wrote:

Mazin,

As we discussed, please make sure that we follow the charter in proposing the 
end-user advisory committee (I.e, formal documentation of the purpose, scope, 
membership, etc) so that the TSC can review and vote on it. I think it’s a good 
idea, but I want to see the details and make sure we follow our documented 
procedure.

Thanks,
Chris


From: GILBERT, MAZIN E (MAZIN E)
To: Alla Goldner;
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@lists.onap.org> P;
Subject: Re: [onap-tsc] [onap-discuss] Action Plan towards Casablanca
Time: 2018-03-30 17:57:00


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