Re: [onap-tsc] ONAP University Project Proposal

2017-05-11 Thread Don Clarke 
Nermin/Mazin,

This is a very good initiative. Can I suggest that there is a plan to include 
module(s) that describe how ONAP relates to the standards bodies that are also 
playing an important role in the NFV ecosystem.

I see mention of "ecosystem" and "upstream projects". I don't see explicit 
mention of standards.

ONAP adoption is in part dependent on those relationships being productive to 
avoid fragmentation and to be compatible with corporate mandates around 
telecommunications standards.

There is a list of relevant bodies being developed as part of the TSC Standards 
and Open Source coordinator discussion. The needed educational material could 
be coordinated through that effort.

For example an extensive body of tutorial material already exists for ETSI NFV. 
I'm sure similar collateral exists amongst the other bodies.

Best regards,
Don Clarke.

On May 11, 2017, at 14:08, Nermin Mohamed 
mailto:nermin.moha...@huawei.com>> wrote:

Hello,

ONAP University Project proposal is ready for review by ONAP TSC.

ONAP University
Contact: Mazin Gilbert (AT&T) and Nermin Mohamed (Huawei)
Description:
Provide overview of the ONAP University training courses for users, developers 
and any other interested parties of member and non-member companies.
This is to help SPs, vendors and suppliers to build up their team’s ONAP 
expertise to increase the success of adopting ONAP.
A variety of delivery options:

· Video Training

· Online Training

· Classroom training

· Hands-on training

· ONAP Certification

· Online tutorials and guides

· ONAP Blog

· Webinar

· Online nanodegrees
Training can be customized based on end user’s needs


Please see attached document for details. Please advise if you need any further 
detail.


BR//Nermin

Nermin Mohamed
Vice President, Solutions and Marketing
Huawei Technologies USA, Inc.
5700 Tennyson Parkway, Suite 500,
Plano, Texas 75024
Office: 214-919-6123
Mobile: 214-537-7985
Fax: 214-919-6597
email: nermin.moha...@huawei.com<mailto:nermin.moha...@huawei.com>
www.huawei.cpm/us<http://www.huawei.cpm/us>



<http://www.twitter.com/Huawei><http://www.facebook.com/Huawei><http://www.youtube.com/Huawei><http://www.linkedin.com/company/huawei><http://www.google.com/+Huawei>


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO

2017-05-10 Thread Don Clarke 
I agree with Alla - an SME with detailed knowledge and well known in the target 
external organization is highly desirable as coordinator for ONAP. I have an 
excellent candidate in mind for ETSI NFV.

BTW - ETSI NFV and ETSI MEC are separate bodies. Although several great people 
I know are involved in both.

Regards,
Don Clarke.

On May 10, 2017, at 15:05, Alla Goldner 
mailto:alla.gold...@amdocs.com>> wrote:

Hi all,

A different way to handle this topic is to assign person responsible for each 
SDO/Open source coordination, same as ETSI NFV have.
To me, it makes more sense, as eventually only subject expert knows which 
topics are discussed in the corresponding SDO/Open Source and how to handle 
them in the best possible way, and not a single coordinator assigned per all 
SDO and/or Open Source projects.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Jason Hunt
Sent: Wednesday, May 10, 2017 10:07 PM
To: ma...@research.att.com<mailto:ma...@research.att.com>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO


Mazin,

Understood.  I see that Lingli also proposed a separate open source 
coordinator.  Good discussion for tomorrow.


Regards,
Jason Hunt
Executive Software Architect, IBM

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


- Original message -
From: "GILBERT, MAZIN E (MAZIN E)" 
mailto:ma...@research.att.com>>
To: Jason Hunt mailto:djh...@us.ibm.com>>
Cc: "denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>" 
mailto:denglin...@chinamobile.com>>, 
"onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>" 
mailto:onap-tsc@lists.onap.org>>
Subject: Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO
Date: Wed, May 10, 2017 1:58 PM

Jason

The coordinator we use to interact with SDO may need to be different than that 
for other
open source projects. There are short term impacts of our first release on 
other open source projects
like OPNFV, FD.io<http://FD.io> and Open Stack, etc.

Let’s discuss tomorrow in our TSC meeting. As of now, we have not approved any 
coordinators except security.
I also need to check with the governance board whether we need any direction 
when interacting
with SDO.

Mazin




On May 10, 2017, at 1:00 PM, Jason Hunt 
mailto:djh...@us.ibm.com>> wrote:


Good proposal.  Would this coordinator also work with other open source 
projects?  I'm thinking, in particular, of OPNFV where I think we could have a 
tight collaboration.


Regards,
Jason Hunt
Executive Software Architect, IBM

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


- Original message -
From: 邓灵莉 mailto:denglin...@chinamobile.com>>
Sent by: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Cc:
Subject: [onap-tsc] Creation Request for Coordination Area Standard/SDO
Date: Wed, May 10, 2017 10:18 AM

Coordination Area Description:


Open source and standard are compliementing each other. Opensource is playing 
an increasing important role in SDO practice, which could help to gain industry 
concensus and adoption.


The potential standard bodies and topics include:

• IETF YANG/NETMOD/NFVRG

• TMF OSS/API/ZOOM

• MEF LSO

• ETSI NFV/MEC

• OASIS TOSCA

• 3GPP

• BBF


Coordinator Responsibilities Description:

• External Responsibilities:

•  Identify members of the ONAP community with existing relationships to 
external SDOs, and work with them to identify and follow the overlap in 
interest or practice from standard bodies related to ONAP’s implementation and 
report to TSC regularly or on demand.

•  Develop ONAP collaboration strategy with, coordinate ONAP presence, 
delegation and participation to identified SDO practices and report to TSC 
regularly or on demand.

• Internal Responsibilities:

  •  Work with individual projects in soliciting and identification of 
related SDO practices.

•  Coordinate between implementation project in ONAP and identified SDO 
practice and report to TSC regularly or on demand.

•  Coordinate among multiple implementation projects in ONAP which fall into 
scope of a given SDO spec and report to TSC regularly or on demand.


Report Cadence:

• Regularly each TSC F2F meeting.

• On-demand report based on urgency of the event.


Area Coordinator:

Hui Deng denghu...@huawei.com<mailto:denghu...@huawei.com>

Lingli/邓灵莉

中国移动通信研究院

denglin...@chinamobile.com<mailto:denglin...@chinamobile.com>

Re: [onap-tsc] [ONAP Security] - support

2017-05-04 Thread Don Clarke 
Steve,

As per my previous question to the ONAP community on this topic, I very much 
welcome this initiative.

I'll look at what resources CableLabs might be able to contribute, at least to 
help ONAP put in place a strategy.
CableLabs Igor Faynberg was present for some of your NJ meeting, I'll consult 
with Igor and the CableLabs security team and get back with you.

Best regards,
Don Clarke.

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Thursday, May 04, 2017 3:22 PM
To: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: [onap-tsc] [ONAP Security] - support

Hi All,

I'm to support looking into what we need to do to support the security of ONAP 
within the ONAP project.  To do this, I want to start by reaching out to 
identify who would be interested in supporting this activity, and also starting 
to get a list of what we think needs to happen.  My thinking was to first 
identify what needs to be done so that could be worked into a proposal.

If you do want to support the security of onap, in particular if you either 
have a good understanding of security and/or a broad understanding of the seed 
code bases please reply directly to me to express your interesting in 
supporting; and if you have a view of what actions we need to take, sharing 
that would also be great input.

BR,

Steve


[Ericsson]<http://www.ericsson.com/>
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R&D Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>
www.ericsson.com<http://www.ericsson.com>


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

Legal entity: Ericsson España S.A, compay registration number ESA288568603. 
This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at 
www.ericsson.com/email_disclaimer<http://www.ericsson.com/email_disclaimer>

___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Draft Agenda for May ONAP Project Developer Event

2017-04-26 Thread Don Clarke 
This is a great idea. Recorded sessions can also be used as tutorials for 
future new participants, especially if some kind of descriptive indexing is 
included to facilitate topic search.

On Apr 26, 2017, at 08:48, "Ning.So at ril.com" 
mailto:Ning.So at ril.com>> wrote:

Will there be video for each session available for remote attendees, either in 
real-time streaming, or through recording (hopefully both)? Since ONAP is a 
global project, attending every meeting in person will be challenging for a lot 
of people who want to contribute.  We should consider video streaming/recording 
a general requirement for future technical meetings.

Ning So

From: onap-tsc-bounces at lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of BENNETT, 
RICH
Sent: Wednesday, April 26, 2017 12:47 AM
To: onap-tsc at lists.onap.org
Cc: onap-discuss at lists.onap.org
Subject: [onap-tsc] Draft Agenda for May ONAP Project Developer Event

Hi All,

A "Draft Agenda" for the May ONAP Project Developer Event has been posted here 
https://wiki.onap.org/display/DW/ONAP+Project+Developer+Event%3A+May+2+-+5%2C+2017
 for the TSC to review and approve at this week's meeting.

Thank you

Rich

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s), are confidential and may be 
privileged. If you are not the intended recipient, you are hereby notified that 
any review, re-transmission, conversion to hard copy, copying, circulation or 
other use of this message and any attachments is strictly prohibited. If you 
are not the intended recipient, please notify the sender immediately by return 
email and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. The company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachment."

___
ONAP-TSC mailing list
ONAP-TSC at lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc
-- next part --
An HTML attachment was scrubbed...
URL:

[onap-tsc] Updated TSC Charter

2017-04-20 Thread Don Clarke 
Chris,

Regulators are concerned about the impact of virtualization on the resilience 
of critical national infrastructures (they have turned-up at ETSI NFV meetings).

Will there be a formalized ONAP process to minimize security vulnerabilities 
and/or undertake risk analysis in relation to critical components of the 
platform?

I don't see anything in the charter, would these aspects fall under (e.g.) the 
TSC Responsibility for "defining release quality standards"?

I don't think this should be left to individual project teams to figure out.

Thanks,
Don.


From: onap-tsc-bounces at lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley (Chris)
Sent: Wednesday, April 19, 2017 9:45 AM
To: onap-tsc at lists.onap.org
Cc: Ed Warnicke
Subject: [onap-tsc] Updated TSC Charter

Dear TSC,

On behalf of the Charter drafting team, please find attached an updated version 
of the TSC Charter incorporating your suggestions and feedback from the last 
review.  We have attempted to highlight the open issues that need a decision 
from the TSC.  We are sending this draft with the intention that you review it 
in preparation for discussion and voting during our next TSC meeting.

Chris, Steve, Ed, Lingli, Alla, and Phil
-- next part --
An HTML attachment was scrubbed...
URL:

[onap-tsc] ONAP - Referencing and Providing Feedback to the ETSI NFV Work

2017-04-19 Thread Don Clarke 
Dear ONAP Colleagues,

Further to my message, ETSI NFV WG Chair Thinh Nguyenphu (Nokia) will be 
attending the upcoming ONAP session in New Jersey and has kindly offered to 
provide a tutorial overview of the ETSI NFV work.

It can be crafted to fit whatever time slot might be available.

Let me know if this would be of interest.

Best regards,
Don Clarke.

On Apr 18, 2017, at 11:28, Don Clarke mailto:D.Clarke at cablelabs.com>> wrote:

Dear ONAP TSC,

I realise everyone is busy standing up this new community but I would like to 
lodge in people?s minds early that the ETSI NFV Industry Specification 
Group<http://www.etsi.org/technologies-clusters/technologies/nfv> (ETSI NFV) 
has been working very hard over the past 4 years to create a body of converged 
requirements and specifications for NFV systems that are being referenced 
globally, including by Open Source communities such as OSM who have provided 
extensive feedback on the utility of the ETSI NFV specifications based on their 
implementation insights.

Noting that members of the OPEN-O community were actively involved in ETSI NFV, 
and the ECOMP white paper referenced the ETSI NFV Architectural Framework, it 
would be useful (at some point) to initiate a discussion in ONAP on the 
importance of referencing the ETSI NFV work as input, and to encourage feedback 
to ETSI NFV on the insights coming from the ONAP implementation so that the 
specs can be improved.

ETSI NFV is providing a common foundation for the global NFV industry to avoid 
fragmentation and encourage interoperability.

I would be very happy to arrange a tutorial webinar (i.e. given by the ETSI NFV 
experts) if the ONAP community would find this useful.

FYI - there will be an ETSI NFV Tutorial session at NFV World 
Congress<https://www.layer123.com/nfv-agenda-workshop/#Forum-2> in San Jose in 
a couple of weeks. It clashes with the ONAP meeting in New Jersey but may be 
useful for some and the materials will be freely available after the event.

Best regards,
Don Clarke.

CableLabs (Chair ETSI NFV Network Operator Council).



___
ONAP-TSC mailing list
ONAP-TSC at lists.onap.org<mailto:ONAP-TSC at lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170419/f5f3ca0e/attachment.html>

[onap-tsc] ONAP - Referencing and Providing Feedback to the ETSI NFV Work

2017-04-18 Thread Don Clarke 
Dear ONAP TSC,

I realise everyone is busy standing up this new community but I would like to 
lodge in people's minds early that the ETSI NFV Industry Specification 
Group<http://www.etsi.org/technologies-clusters/technologies/nfv> (ETSI NFV) 
has been working very hard over the past 4 years to create a body of converged 
requirements and specifications for NFV systems that are being referenced 
globally, including by Open Source communities such as OSM who have provided 
extensive feedback on the utility of the ETSI NFV specifications based on their 
implementation insights.

Noting that members of the OPEN-O community were actively involved in ETSI NFV, 
and the ECOMP white paper referenced the ETSI NFV Architectural Framework, it 
would be useful (at some point) to initiate a discussion in ONAP on the 
importance of referencing the ETSI NFV work as input, and to encourage feedback 
to ETSI NFV on the insights coming from the ONAP implementation so that the 
specs can be improved.

ETSI NFV is providing a common foundation for the global NFV industry to avoid 
fragmentation and encourage interoperability.

I would be very happy to arrange a tutorial webinar (i.e. given by the ETSI NFV 
experts) if the ONAP community would find this useful.

FYI - there will be an ETSI NFV Tutorial session at NFV World 
Congress<https://www.layer123.com/nfv-agenda-workshop/#Forum-2> in San Jose in 
a couple of weeks. It clashes with the ONAP meeting in New Jersey but may be 
useful for some and the materials will be freely available after the event.

Best regards,
Don Clarke.

CableLabs (Chair ETSI NFV Network Operator Council).



-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170418/ab051af0/attachment.html>