date:20170801

Re: [onap-tsc] ETSI NFV API Conventions, wiki page, and more available [modeling]

2017-08-01 Thread denghui (L)

Hi Thinh

I have created  a page for recommended SPECs from SDOs.
https://wiki.onap.org/display/DW/Recommended+specs+from+SDOs

Please help to fill in the spread sheet.

If other SDOs also have such intention, please follow that page as well

Thanks a lot

DENG Hui

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Nguyenphu, Thinh (Nokia - US/Irving)
Sent: Wednesday, August 2, 2017 6:20 AM
To: onap-tsc@lists.onap.org
Subject: [onap-tsc] ETSI NFV API Conventions, wiki page, and more available

Hello,

Couple week ago, there was a discussion on this list about RESTful API Design 
Specification.  I am happy to report that the ETSI NFV SOL REST API Conventions 
document is available, 
https://nfvwiki.etsi.org/images/NFVSOL(17)50r4_ETSI_NFV_SOL_REST_API_Conventions.pdf.
 This document covers naming conventions, data and URI structures, supported 
content formats, message flows convention and tools, common error situations, 
etc.  This document really help SOL working group during our API specification 
design and development across multiple interfaces to ensure consistency design 
and implementation.

I recommending members to take a look, and development your own conventions for 
ONAP APIs across projects. The goal is to avoid any conflicting convention or 
design principle, etc.

For an overview of ETSI NFV IFA and SOL specifications (published and latest 
drafts), tutorial presentations, and webinar, please visit this wiki page, 
https://nfvwiki.etsi.org/index.php?title=NFVSolutions

For modeling, ETSI NFV has produce UML Modeling Guideline, Papyrus Guidelines, 
NFV Information Model, and IFA011 (VNFD) and IFA014 (NSD).  The links is 
available either at wiki page or attached presentation.

Finally, enclosed attachment is the presentation that presented to VNF Package 
sub-project last Friday.

To Deng Hui,
Would please create a SDO wiki page to record these above information and 
future updates. Thanks

Regards,
Thinh

Thinh Nguyenphu
Nokia Networks
thinh.nguyen...@nokia.com
+1 817-313-5189

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

Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

2017-08-01 Thread Xinhui Li

+1 All

From: Kenny Paul 
Date: Friday, 28 July 2017 at 1:08 AM
To: Xinhui Li 
Cc: onap-tsc 
Subject: Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

Hi Xinhui,
please verify that your response was intended as a "+1 All”
Thanks!

Best Regards,
-kenny

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

On Jul 24, 2017, at 1:51 AM, Xinhui Li 
> wrote:

+1

From: > 
on behalf of Dhananjay Pavgi 
>
Date: Monday, 24 July 2017 at 1:46 PM
To: Lingli Deng 
>, 'Kenny Paul' 
>, 'onap-tsc' 
>
Subject: Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

+1

thanks & regards,
Dhananjay Pavgi
Mobile : +91 98220 22264
   
www.techmahindra.com
 Platinum Member. Visit : 
http://www.onap.org

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Monday, July 24, 2017 11:07 AM
To: 'Kenny Paul' >; 
'onap-tsc' >
Subject: Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

[VOTE] +1

Lingli

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: 2017年7月23日 2:49
To: onap-tsc >
Subject: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

As mentioned we have several repository requests queued up. Gildas has reviewed 
these and feels the requestors have done their due diligence regarding the data 
needed.

Please vote for each one individually OR respond with a (+1, 0, -1)  
“ALL” to approve or reject all requests
——

VOTE to approve the AAF Project's Requests for the creation of an incremental 
repository (+1, 0 -1)
Components Name

Components Repository name

Maven Group ID

Components Description

luaplugin

aaf/luaplugin

org.onap.aaf.luaplugin

A lua plugin to integrate AAF with MSB, which provides centralized auth 
features at the API Gateway.



VOTE to approve the MSB Project's Requests for the creation of two incremental 
repositories (+1, 0 -1)
Components Name

Components Repository name

Maven Group ID

Components Description

java-sdk

msb/java-sdk

org.onap.msb.sdk

Provides a JAVA SDK for rapid microservices development, including service 
registration, service discovery, request routing, load balancing, retry, etc.

swagger-sdk

msb/swagger-sdk

org.onap.msb.swagger-sdk

Swagger sdk helps to generate swagger.json and java client sdk during the build 
time, it also helps to provide the swagger.json at the given URI in the run 
time.



VOTE to approve the A Project's Requests for the creation of two incremental 
repositories (+1, 0 -1)
Components Name

Components Repository Name

Maven Group ID

Components Discription

esr-server

aai/esr-server

org.onap.aai.esr-server

ESR backend, mainly include the function of external system reachable check and 
data pretreatment

esr-gui

aai/esr-gui

org.onap.aai.esr-gui

External system management ui


VOTE to approve the Modeling Subcommittee’s requests for the creation of an 
incremental repository within the Modeling Project’s structure (+1, 0 -1)
Components Name

Components Repository name

Maven Group ID

Components Description



 modelspec

 modeling/modelspec

 org.onap.modeling.modelspec

The repository for modeling specification
published by modeling subcommittee



Best Regards,
-kenny

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


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

Re: [onap-tsc] Leadership Diversity Language

2017-08-01 Thread Christopher Donley (Chris)

I agree that this topic would be more appropriate as a TSC policy than as text 
in the Charter.

Chris

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Tuesday, August 01, 2017 12:22 AM
To: Kenny Paul ; t...@lists.onap.org
Subject: Re: [onap-tsc] Leadership Diversity Language

Hi,

Thanks Kenny for assembling this text and to the contributors for inputing.

As a general question to all, given that these appear to read as guidelines, - 
do we want to include them in a charter; or create a TSC policy document where 
we can capture such things and others (i.e. information for decision should be 
submitted x days in advance).

The advantage of including the update in the charter is that it would be more 
consistant.  The advantage with a separate TSC policy document is that we 
separate guidelines from mechanisms.

Best Regards,

Steve.

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: 01 August 2017 03:05
To: t...@lists.onap.org
Subject: [onap-tsc] Leadership Diversity Language

TSC Members,

Please find for your discussion and review the slide contents around Leadership 
Diversity from last week’s TSC meeting. It was recommended that this may be 
better adopted as a policy, rather than as an amendment to the TSC Charter.

Leadership Diversity Intent
We as the ONAP community, should identify and train talents to help promote 
leadership diversity within projects, subcommittees, etc.
•Develop a broad base of community leaders from many backgrounds
•Instill a sense of trust and openness to multiple view points
•Ensure an adequate representation of the community
•Distribute responsibilities in a scalable fashion
•Allow exceptions where appropriate to keep both the community and project 
moving forward

Leadership Diversity Meaning
•An individual can either be in any of these leadership positions:
-the TSC Chair/Vice-Chair
-a Subcommittee Chair/Vice-Chair
-a Community Coordinator
-a PTL
•No individual should hold more than one of those roles unless the TSC deems 
there is either a high level of merit in doing so, or no reasonable alternative.
•A logical location in the TSC Charter for introducing this language would be 
in Section 1: Guiding Principles
NOTE: It was pointed out that a number of sections within the charter would 
need to be changed if Section 1 was used.

Leadership Diversity Language
1.3  Leadership Diversity
  1.3.1  Any one person should only be allowed to hold a single office at a 
time, inclusive of TSC, Subcommittee, Coordinator and PTL positions.
  1.3.2  Exceptions can be made by the TSC for someone to hold multiple 
positions if there are insufficient candidates available for a position, or in 
cases where doing so would be bring high value to the project.

Best Regards,
-kenny

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

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

Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

2017-08-01 Thread Kenny Paul

These new repositories are all still unapproved.  At least one more person 
needs to confirm that their vote it was intended to be a “+1 ALL” before these 
can be approved.

Thank you.

Best Regards, 
-kenny

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

>>  
>> From: onap-tsc-boun...@lists.onap.org 
>>  
>> [mailto:onap-tsc-boun...@lists.onap.org 
>> ] On Behalf Of Kenny Paul
>> Sent: 2017年7月23日 2:49
>> To: onap-tsc >
>> Subject: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB
>>  
>> As mentioned we have several repository requests queued up. Gildas has 
>> reviewed these and feels the requestors have done their due diligence 
>> regarding the data needed.
>>  
>> Please vote for each one individually OR respond with a (+1, 0, -1)  
>> “ALL” to approve or reject all requests
>> ——
>>  
>> VOTE to approve the AAF Project's Requests for the creation of an 
>> incremental repository (+1, 0 -1)
>> Components Name
>> Components Repository name
>> Maven Group ID
>> Components Description
>> luaplugin
>> aaf/luaplugin
>> org.onap.aaf.luaplugin
>> A lua plugin to integrate AAF with MSB, which provides centralized auth 
>> features at the API Gateway.
>>  
>>  
>> VOTE to approve the MSB Project's Requests for the creation of two 
>> incremental repositories (+1, 0 -1)
>> Components Name
>> Components Repository name
>> Maven Group ID
>> Components Description
>> java-sdk
>> msb/java-sdk
>> org.onap.msb.sdk
>> Provides a JAVA SDK for rapid microservices development, including service 
>> registration, service discovery, request routing, load balancing, retry, etc.
>> swagger-sdk
>> msb/swagger-sdk
>> org.onap.msb.swagger-sdk
>> Swagger sdk helps to generate swagger.json and java client sdk during the 
>> build time, it also helps to provide the swagger.json at the given URI in 
>> the run time.
>>  
>>  
>> VOTE to approve the A Project's Requests for the creation of two 
>> incremental repositories (+1, 0 -1)
>> Components Name
>> Components Repository Name
>> Maven Group ID
>> Components Discription
>> esr-server
>> 
>> aai/esr-server
>> 
>> org.onap.aai.esr-server
>> 
>> ESR backend, mainly include the function of external system reachable check 
>> and data pretreatment
>> 
>> esr-gui
>> 
>> aai/esr-gui
>> 
>> org.onap.aai.esr-gui
>> 
>> External system management ui
>> 
>>  
>> VOTE to approve the Modeling Subcommittee’s requests for the creation of an 
>> incremental repository within the Modeling Project’s structure (+1, 0 -1)
>> Components Name
>> Components Repository name
>> Maven Group ID
>> Components Description
>>  
>>  modelspec
>>  modeling/modelspec
>>  org.onap.modeling.modelspec
>> The repository for modeling specification
>> published by modeling subcommittee
>>  
>>  
>> Best Regards, 
>> -kenny
>> 
>> Kenny Paul,  Technical Program Manager
>> kp...@linuxfoundation.org 
>> 510.766.5945
>>  
>> 
>> 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.
>> 

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

Re: [onap-tsc] Migration to *.onap.org

2017-08-01 Thread Kenny Paul

Adding this to the Aug 3 agenda.

Best Regards, 
-kenny

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

> On Aug 1, 2017, at 5:07 AM, Lefevre, Catherine  wrote:
> 
> Dear ONAP TSC,
>  
> I fully understand the request about the seed code to be migrated to 
> *.onap.org .
> Nevertheless I want to bring to your attention that this request will require 
> significant effort (development, testing and infrastructure changes)
> ·Coordinate and update Maven dependencies and links
> ·Update namespaces as required
> ·Change the source code in order to align with *.onap.org 
>  for each impacted project
> ·Change the development scripts
> ·Review and update automated test cases
> ·Re-adjust the LF infrastructure accordingly, keeping the 
> org.openecomp version in place until the end of migration
> That way each project can control the pace of migration from org.openecomp -> 
> org.onap : especially for the projects that are already based on the previous 
> naming.  
> ·Review and re-adjust build jobs to be approved by CI-Management 
> project
> ·Create a temporary environment to perform the necessary code changes
> ·Plan the migration in order to avoid any drastic impact on the ONAP 
> community
> ·Recreate new docker images and stabilize the complete ONAP 
> Environment
> ·Etc.
>  
> Based on past experience (moving from *.att.com  to 
> *.openecomp.org ), this effort can take up to several 
> weeks until the ONAP release is completely stabilized
> If we pursue in this direction then it is a major risk for our Amsterdam 
> release to be completed on time.
> We will need to review the scope of ONAP R1 based on our resource capacity.
>  
> Or we can develop a complete migration plan as part of our ONAP R1 commitments
> And implement this migration in October as part of ONAP R2 preparation.
>  
> Is it something we can discuss during our next TSC meeting?
>  
> Thanks in advance for your consideration.
>  
> Many thanks & regards
> Catherine
>  
> Catherine Lefèvre
> AT Network and Shared Services
> D2 Platform & Systems Development
> AVP Software Development & Engineering
> ECOMP/ONAP/RUBY/SPP
>  
>  
> Phone: +32 2 418 49 22
> Mobile: +32 475 77 36 73
> catherine.lefe...@intl.att.com 
>  <> 
> TEXTING and DRIVING… It Can Wait
> AT
> BUROGEST OFFICE PARK SA
> Avenue des Dessus-de-Lives, 2
> 5101 Loyers (Namur)
> Belgium
>  
>  
> NOTE: This email (or its attachments) contains information belonging to the 
> sender, which may be confidential. proprietary and/or legally privileged. The 
> information is intended only for the use of the individual(s) or entity(ies) 
> named above. If you are not the intended recipient, you are hereby notified 
> that any disclosure, distribution or taking of any action in reliance on the 
> content of this is strictly forbidden. If you have received this e-mail in 
> error please immediately notify the sender identified above
>  
> ___
> ONAP-TSC mailing list
> 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] Migration to *.onap.org

2017-08-01 Thread SPATSCHECK, OLIVER (OLIVER)

Could we put that on the TSC agenda on Thu?

Thx

Oliver

> On Aug 1, 2017, at 8:07 AM  EDT, LEFEVRE, CATHERINE  
> wrote:
> 
> ***Security Advisory: This Message Originated Outside of AT ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
> 
> Dear ONAP TSC,
>  
> I fully understand the request about the seed code to be migrated to 
> *.onap.org.
> Nevertheless I want to bring to your attention that this request will require 
> significant effort (development, testing and infrastructure changes)
> ·Coordinate and update Maven dependencies and links
> ·Update namespaces as required
> ·Change the source code in order to align with *.onap.org for each 
> impacted project
> ·Change the development scripts
> ·Review and update automated test cases
> ·Re-adjust the LF infrastructure accordingly, keeping the 
> org.openecomp version in place until the end of migration
> That way each project can control the pace of migration from org.openecomp -> 
> org.onap : especially for the projects that are already based on the previous 
> naming.  
> ·Review and re-adjust build jobs to be approved by CI-Management 
> project
> ·Create a temporary environment to perform the necessary code changes
> ·Plan the migration in order to avoid any drastic impact on the ONAP 
> community
> ·Recreate new docker images and stabilize the complete ONAP 
> Environment
> ·Etc.
>  
> Based on past experience (moving from *.att.com to *.openecomp.org), this 
> effort can take up to several weeks until the ONAP release is completely 
> stabilized
> If we pursue in this direction then it is a major risk for our Amsterdam 
> release to be completed on time.
> We will need to review the scope of ONAP R1 based on our resource capacity.
>  
> Or we can develop a complete migration plan as part of our ONAP R1 commitments
> And implement this migration in October as part of ONAP R2 preparation.
>  
> Is it something we can discuss during our next TSC meeting?
>  
> Thanks in advance for your consideration.
>  
> Many thanks & regards
> Catherine
>  
> Catherine Lefèvre
> AT Network and Shared Services
> D2 Platform & Systems Development
> AVP Software Development & Engineering
> ECOMP/ONAP/RUBY/SPP
>  
>  
> Phone: +32 2 418 49 22
> Mobile: +32 475 77 36 73
> catherine.lefe...@intl.att.com
>  
> TEXTING and DRIVING… It Can Wait
> AT
> BUROGEST OFFICE PARK SA
> Avenue des Dessus-de-Lives, 2
> 5101 Loyers (Namur)
> Belgium
>  
>  
> NOTE: This email (or its attachments) contains information belonging to the 
> sender, which may be confidential. proprietary and/or legally privileged. The 
> information is intended only for the use of the individual(s) or entity(ies) 
> named above. If you are not the intended recipient, you are hereby notified 
> that any disclosure, distribution or taking of any action in reliance on the 
> content of this is strictly forbidden. If you have received this e-mail in 
> error please immediately notify the sender identified above
>  
> ___
> ONAP-TSC mailing list
> ONAP-TSC@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=3WBYkehchaQg0p_gO26aU_ahomnFHCk_-us7kcQebm4=3qNBXK1AEoL6zxuaVrLo3UBFVSNq0OaszyDvfaLoUQE=vK70kqm-zpxVa5UZRJs-RxEUPokb6jDG4kR-XCz9hGY=

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

[onap-tsc] ONAP VoLTE SDC call

2017-08-01 Thread denghui (L)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=denghui (L):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-disc...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc:M
 AILTO:onap-tsc@lists.onap.org
DESCRIPTION;LANGUAGE=zh-CN:Hello all\n\nThis is for discussion ONAP VoLTE S
 DC call.\n\nONAP Meeting 5 is inviting you to a scheduled Zoom meeting.\nJ
 oin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/137904496\nOr iPhone one-tap (US Toll): +1
 4086380968\,137904496# or +16465588656\,137904496#\nOr Telephone:\nDial: +
 1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll)\nMeeting ID: 137 904
  496\nInternational numbers available: https://zoom.us/zoomconference?m=mi
 -ad1sMLWlXByAKLio5vDnd9JYqUR_a\n\nThanks a lot\n\nDENG Hui\n\n
SUMMARY;LANGUAGE=zh-CN:ONAP VoLTE SDC call
DTSTART;TZID=China Standard Time:20170802T22
DTEND;TZID=China Standard Time:20170802T23
UID:04008200E00074C5B7101A82E008D0CE9D731F0BD301000
 010006833155E45E3B34AB8373F4F0AA812F3
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170801T154347Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=zh-CN:https://zoom.us/j/137904496
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1172408289
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] [SDC][MODELING][SO][VFC][SDNC][A][MULTIVIM]ONAP VoLTE SDC call on wednesday

2017-08-01 Thread denghui (L)

Please help to forward it, thanks a lot

DENG Hui
BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN
VERSION:2.0
METHOD:PUBLISH
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:China Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
CLASS:PUBLIC
CREATED:20170801T153958Z
DESCRIPTION:Hello all\n\nThis is for discussion ONAP VoLTE SDC call.\nONAP 
	Meeting 5 is inviting you to a scheduled Zoom meeting. \nJoin from PC\, Ma
	c\, Linux\, iOS or Android: https://zoom.us/j/137904496  \nOr iPhone one-tap (US Toll): +14086380968\,13
	7904496# or +16465588656\,137904496#\nOr Telephone:\nDial: +1 408 638 0968
	 (US Toll) or +1 646 558 8656 (US Toll)\nMeeting ID: 137 904 496\nInternat
	ional numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAK
	Lio5vDnd9JYqUR_a  \n\nThanks a lot\n\nDENG Hui\n
DTEND;TZID="China Standard Time":20170802T23
DTSTAMP:20170801T153958Z
DTSTART;TZID="China Standard Time":20170802T22
LAST-MODIFIED:20170801T153958Z
LOCATION:https://zoom.us/j/137904496
PRIORITY:5
SEQUENCE:0
SUMMARY;LANGUAGE=zh-cn:ONAP VoLTE SDC call
TRANSP:OPAQUE
UID:04008200E00074C5B7101A82E008D0CE9D731F0BD301000
	010006833155E45E3B34AB8373F4F0AA812F3
X-ALT-DESC;FMTTYPE=text/html:\n\n\n\n\n\n\n\n\nHello all\n\n\n\nThis is for discussion ONAP VoLTE SDC call.\n\n<
	P DIR=LTR>ONAP Meeting 5 is inviting you to a scheduled Zoom 
	meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Andro
	id: https://www.google.co
	m/url?q=https%3A%2F%2Fzoom.us%2Fj%2F137904496\;sa=D\;usd=2\;us
	g=AFQjCNHWLm-MNCNZh9JQ8TByZ7QBGA_nzQ">https://zoom.
	us/j/137904496\n\nOr
	 iPhone one-tap (US Toll): +14086380968\,137904496# or +16465588656\,13790
	4496#\n\nOr Telephone:\nDial: +1 408 638 0968 (US 
	Toll) or +1 646 558 8656 
	(US Toll)\nMeeting ID: 137 904 496\nInternational numbers availabl
	e: https://www.google.com
	/url?q=https%3A%2F%2Fzoom.us%2Fzoomconference%3Fm%3Dmi-ad1sMLWlXByAKLio5vD
	nd9JYqUR_a\;sa=D\;usd=2\;usg=AFQjCNGUpQlMWM7Hx42afMT3U-kpQiPOM
	A">https://zoom.us/zoomconference?m=mi-ad1sMLWlXByA
	KLio5vDnd9JYqUR_a\n\n\n\nThanks a lot\n\nDENG Hui\n\n\n
X-MICROSOFT-CDO-BUSYSTATUS:BUSY
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-AUTOFILLLOCATION:FALSE
X-MS-OLK-CONFTYPE:0
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] Migration to *.onap.org

2017-08-01 Thread Lefevre, Catherine

Dear ONAP TSC,

I fully understand the request about the seed code to be migrated to *.onap.org.
Nevertheless I want to bring to your attention that this request will require 
significant effort (development, testing and infrastructure changes)

·Coordinate and update Maven dependencies and links

·Update namespaces as required

·Change the source code in order to align with *.onap.org for each 
impacted project

·Change the development scripts

·Review and update automated test cases

·Re-adjust the LF infrastructure accordingly, keeping the org.openecomp 
version in place until the end of migration
That way each project can control the pace of migration from org.openecomp -> 
org.onap : especially for the projects that are already based on the previous 
naming.

·Review and re-adjust build jobs to be approved by CI-Management project

·Create a temporary environment to perform the necessary code changes

·Plan the migration in order to avoid any drastic impact on the ONAP 
community

·Recreate new docker images and stabilize the complete ONAP Environment

·Etc.

Based on past experience (moving from *.att.com to *.openecomp.org), this 
effort can take up to several weeks until the ONAP release is completely 
stabilized
If we pursue in this direction then it is a major risk for our Amsterdam 
release to be completed on time.
We will need to review the scope of ONAP R1 based on our resource capacity.

Or we can develop a complete migration plan as part of our ONAP R1 commitments
And implement this migration in October as part of ONAP R2 preparation.

Is it something we can discuss during our next TSC meeting?

Thanks in advance for your consideration.

Many thanks & regards
Catherine

Catherine Lefèvre
AT Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

Re: [onap-tsc] Leadership Diversity Language

2017-08-01 Thread Stephen Terrill

Hi,

Thanks Kenny for assembling this text and to the contributors for inputing.

As a general question to all, given that these appear to read as guidelines, - 
do we want to include them in a charter; or create a TSC policy document where 
we can capture such things and others (i.e. information for decision should be 
submitted x days in advance).

The advantage of including the update in the charter is that it would be more 
consistant.  The advantage with a separate TSC policy document is that we 
separate guidelines from mechanisms.

Best Regards,

Steve.

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: 01 August 2017 03:05
To: t...@lists.onap.org
Subject: [onap-tsc] Leadership Diversity Language

TSC Members,

Please find for your discussion and review the slide contents around Leadership 
Diversity from last week’s TSC meeting. It was recommended that this may be 
better adopted as a policy, rather than as an amendment to the TSC Charter.

Leadership Diversity Intent
We as the ONAP community, should identify and train talents to help promote 
leadership diversity within projects, subcommittees, etc.
•Develop a broad base of community leaders from many backgrounds
•Instill a sense of trust and openness to multiple view points
•Ensure an adequate representation of the community
•Distribute responsibilities in a scalable fashion
•Allow exceptions where appropriate to keep both the community and project 
moving forward


Leadership Diversity Meaning
•An individual can either be in any of these leadership positions:
-the TSC Chair/Vice-Chair
-a Subcommittee Chair/Vice-Chair
-a Community Coordinator
-a PTL
•No individual should hold more than one of those roles unless the TSC deems 
there is either a high level of merit in doing so, or no reasonable alternative.
•A logical location in the TSC Charter for introducing this language would be 
in Section 1: Guiding Principles
NOTE: It was pointed out that a number of sections within the charter would 
need to be changed if Section 1 was used.

Leadership Diversity Language
1.3  Leadership Diversity
  1.3.1  Any one person should only be allowed to hold a single office at a 
time, inclusive of TSC, Subcommittee, Coordinator and PTL positions.
  1.3.2  Exceptions can be made by the TSC for someone to hold multiple 
positions if there are insufficient candidates available for a position, or in 
cases where doing so would be bring high value to the project.



Best Regards,
-kenny

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

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

Re: [onap-tsc] [MSB][OOM]The July Virtual Developers Event Topic : OOM & MSB Interaction

2017-08-01 Thread Gildas Lanilis

Kenny, Yes this is fine with as defined in wiki.
You can go ahead and request TSC’s approval.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Kenny Paul [mailto:kp...@linuxfoundation.org]
Sent: Monday, July 31, 2017 3:37 PM
To: Gildas Lanilis 
Cc: onap-tsc@lists.onap.org; Sauvageau, David 
Subject: Re: [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction

Gildas, does this pass your review?

Best Regards,
-kenny

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

On Jul 31, 2017, at 6:42 AM, Sauvageau, David 
> wrote:

Hi Kenny, can you please create the following repo in OOM?
Thanks,

Components Name

Components Repository name

Maven Group ID

Components Description

registrator

oom/registrator

org.onap.oom.registrator

Register the service endpoints to MSB so it can be used for service request 
routing and load balancing. Registrator puts service endpoints info to MSB 
discovery module(Consul as the backend) when an ONAP component is deployed by 
OOM, and update its state along with the life cycle, such as start, stop, 
scaling, etc.

On Jul 26, 2017, at 9:37 AM, Sauvageau, David 
> wrote:

Hi Kenny
Can we please create that repo?
Thanks

Envoyé de mon iPhone

Début du message transféré :
Expéditeur: >
Date: 26 juillet 2017 à 09:16:15 UTC−4
Destinataire: >
Cc: >, 
>, 
>, 
>, 
>, 
>, 
>, 
>, 
>, 
>, 
>
Objet: Rép :⁨ [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction⁩
Hi David,

Given the current situation, MSB should take the service endpoint registration 
integration with kubernetes implementation as its priority for Amsterdam and 
integration with cloudify implementation as a stretch goal.

As we discussed in the last OOM meeting, we need a repo to accommodate the 
registrator codes for kubernetes service. Can you help to create that repo?  
Please let me know if you have any concerns or question.

Release Components Name
Components Name

Components Repository name

Maven Group ID

Components Description

registrator

oom/registrator

org.onap.oom.registrator

Register the service endpoints to MSB so it can be used for service request 
routing and load balancing. Registrator puts service endpoints info to MSB 
discovery module(Consul as the backend) when an ONAP component is deployed by 
OOM, and update its state along with the life cycle, such as start, stop, 
scaling, etc.

Resources committed to the Release

Thanks,
Huabing

Original Mail
Sender:  >;
To:  >;
CC: zhaohuabing10201488; 
>; 
>; 
>; 
>; 
>; 
>;MengZhaoXing10024238; 
>; 
>; 
>;
Date: 2017/07/26 19:39
Subject: Re: [MSB][OOM]The July Virtual Developers Event Topic :  OOM & MSB 
Interaction

Hi John

Let’s recap what was discussed and agreed as a team:
* For Amsterdam release, Kubernetes is the first OOM technical implementation 
to be created. This is the seed code available and what the team agreed to work 
on
* The cloudily implementation has not been demoed yet and no seed code 
available. It was agreed by the team that cloudily would be a stretch target.

I want to make sure we align to what the OOM team has agreed to deliver.

Comments?

On Jul 25, 2017, at 6:39 PM, NG, JOHN > 
wrote:

Huabing,
Ok, let’s focus on Consul integration for the Amsterdam release …

-  In  Day 0 OOM instantiation, Cloudify is the first OOM module to be 
created.

-  Cloudify  creates Consul as the next OOM module.   Cloudify 
registers itself in Consul.

-  Cloudify  then creates the rest of the OOM modules (Postgres, API 
Handler, Dashboard), and

Re: [onap-tsc] Use case subcommittee meeting (31/07/2017): the summary

2017-08-01 Thread Alla Goldner

Hi Mazin,

Definitely, one part of our plan is to review use cases proposals with 
Integration and Open lab tams to ensure commitment.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D30AA6.70E12AD0]

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Tuesday, August 01, 2017 9:09 AM
To: Alla Goldner 
Cc: onap-usecase...@lists.onap.org; Kenny Paul ; 
Phil Robb ; onap-tsc 
Subject: Re: Use case subcommittee meeting (31/07/2017): the summary

Thanks Alla for sharing.

One of the requirement for any new use case should be the availability of a lab 
and integration support. We need to get that vetted upfront before committing 
to any use case for a release going forward.

Regards

Mazin

Sent through AT's fastest network

On Jul 31, 2017, at 7:55 PM, Alla Goldner 
> wrote:
Hi all,

Thanks to all meeting participants!

Please see the meeting's summary below:


1.   R1 use cases: Status and actions, required from Use case subcommittee 
(vCPE: Kang Xi/Yoav Kluger, vVoLTE: Yang Xe/Chengli Wang)

We reviewed all blocking issues (presented by Yang (vVoLTE) and Kang (vCPE)) 
https://wiki.onap.org/display/DW/July+Virtual+Developers+Event+Blockers
 Today there is also vVoLTE meeting with the project teams which may resolve 
some of those issues. We agree to add column to express whether each specific 
issue is blocking for M2. This was already done by Yang, thanks a lot!!! VFC 
and SDC teams, please pay attention to your blocking issues for M2 and please 
update in case of progress achieved later today.



2.   R2 use cases proposals for presentation and review

a.   ONAP Change Management 
https://wiki.onap.org/display/DW/Use+Case%3A+ONAP+Change+Management
  - was presented as use case candidate for R2 (Emmanouil Mavrogiorgis). We 
agreed to form task force discussing this use case, led by Emmanouil. The 
objectives will be to see what is covered/planned to be covered by a different 
projects, and where gaps are, and what needs to be covered by this use case. I 
will issue separating email on this asking community to approach Emmanouil and 
start this work.


b.  5G use cases family (Disaggregated RAN deployment, E2E network slicing 
and SON) 
https://wiki.onap.org/display/DW/Release+2+Use+Cases?preview=/8230720/10783664/5G_RAN_UseCase_for_R2.docx
 - was presented as use case candidate for R2 (Vimal Begwani). We agreed to 
form task force discussing 5G potential use cases, led by Vimal. The objectives 
will be to discuss this proposal, see additional proposals, decide whether they 
all needs to be merged into a single 5G use case for R2 or proposed as a 
separate ones, and further work on proposals. I will issue separating email on 
this asking community to approach Vimal and start this work.


c.   Enterprise vCPE 
https://wiki.onap.org/pages/viewpage.action?pageId=6593376
  - to the previous ones, I would suggest to form task force discussing this 
use case and potentially extending it, as we've had several email proposals on 
how this may be extended.  I will issue separating email on this asking 
community to approach Luman and start this work.


3.   General topics

a.   Criteria for use case selection (for your information, R1 use cases 
criteria for selection are here: 
https://wiki.onap.org/display/DW/Release+1+Use+Cases
 ). We haven't had

Re: [onap-tsc] Use case subcommittee meeting (31/07/2017): the summary

2017-08-01 Thread GILBERT, MAZIN E (MAZIN E)

Thanks Alla for sharing.

One of the requirement for any new use case should be the availability of a lab 
and integration support. We need to get that vetted upfront before committing 
to any use case for a release going forward.

Regards

Mazin

Sent through AT's fastest network

On Jul 31, 2017, at 7:55 PM, Alla Goldner 
> wrote:

Hi all,

Thanks to all meeting participants!

Please see the meeting’s summary below:


1.   R1 use cases: Status and actions, required from Use case subcommittee 
(vCPE: Kang Xi/Yoav Kluger, vVoLTE: Yang Xe/Chengli Wang)

We reviewed all blocking issues (presented by Yang (vVoLTE) and Kang (vCPE)) 
https://wiki.onap.org/display/DW/July+Virtual+Developers+Event+Blockers
 Today there is also vVoLTE meeting with the project teams which may resolve 
some of those issues. We agree to add column to express whether each specific 
issue is blocking for M2. This was already done by Yang, thanks a lot!!! VFC 
and SDC teams, please pay attention to your blocking issues for M2 and please 
update in case of progress achieved later today.



2.   R2 use cases proposals for presentation and review

a.   ONAP Change Management 
https://wiki.onap.org/display/DW/Use+Case%3A+ONAP+Change+Management
  - was presented as use case candidate for R2 (Emmanouil Mavrogiorgis). We 
agreed to form task force discussing this use case, led by Emmanouil. The 
objectives will be to see what is covered/planned to be covered by a different 
projects, and where gaps are, and what needs to be covered by this use case. I 
will issue separating email on this asking community to approach Emmanouil and 
start this work.


b.  5G use cases family (Disaggregated RAN deployment, E2E network slicing 
and SON) 
https://wiki.onap.org/display/DW/Release+2+Use+Cases?preview=/8230720/10783664/5G_RAN_UseCase_for_R2.docx
 – was presented as use case candidate for R2 (Vimal Begwani). We agreed to 
form task force discussing 5G potential use cases, led by Vimal. The objectives 
will be to discuss this proposal, see additional proposals, decide whether they 
all needs to be merged into a single 5G use case for R2 or proposed as a 
separate ones, and further work on proposals. I will issue separating email on 
this asking community to approach Vimal and start this work.


c.   Enterprise vCPE 
https://wiki.onap.org/pages/viewpage.action?pageId=6593376
  - to the previous ones, I would suggest to form task force discussing this 
use case and potentially extending it, as we’ve had several email proposals on 
how this may be extended.  I will issue separating email on this asking 
community to approach Luman and start this work.


3.   General topics

a.   Criteria for use case selection (for your information, R1 use cases 
criteria for selection are here: 
https://wiki.onap.org/display/DW/Release+1+Use+Cases
 ). We haven’t had time to discuss this, please approach me in case of any 
suggestions. We will discuss this next week.

b.  Plans for alignment with Architecture subcommittee on R2 use cases 
architecture, plans on initial presentation of R2 use cases to the TSC, pre-R2 
rough milestones  - work is in progress, will report to the group.


   i


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology




From: Alla Goldner
Sent: Saturday, July 29, 2017 4:17 PM
To: onap-usecase...@lists.onap.org
Cc: GILBERT,

Re: [onap-tsc] ETSI NFV API Conventions, wiki page, and more available [modeling]

Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

Re: [onap-tsc] Leadership Diversity Language

Re: [onap-tsc] TSC VOTE on Repos for AAI, AAF, Modeling & MSB

Re: [onap-tsc] Migration to *.onap.org

Re: [onap-tsc] Migration to *.onap.org

[onap-tsc] ONAP VoLTE SDC call

[onap-tsc] [SDC][MODELING][SO][VFC][SDNC][A][MULTIVIM]ONAP VoLTE SDC call on wednesday

[onap-tsc] Migration to *.onap.org

Re: [onap-tsc] Leadership Diversity Language

Re: [onap-tsc] [MSB][OOM]The July Virtual Developers Event Topic : OOM & MSB Interaction

Re: [onap-tsc] Use case subcommittee meeting (31/07/2017): the summary

Re: [onap-tsc] Use case subcommittee meeting (31/07/2017): the summary

13 matches

Site Navigation

Mail list logo

Footer information