Re: [onap-tsc] [ONAP Helpdesk #57232] committer election results : VNFRQTS. VVP

[Gildas Lanilis via RT]

Hi Jess,

Yes Steven for VVP and Hagop for vnfrqts.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, June 18, 2018 3:06 PM
To: sw3...@att.com
Cc: Gildas Lanilis ; onap-tsc@lists.onap.org
Subject: [ONAP Helpdesk #57232] committer election results : VNFRQTS. VVP

Hi Gildas, 

>From the email you mentioned 
>"https://lists.onap.org/pipermail/onap-tsc/2018-June/004978.html;
I can only see both Steve and Hagop being requested, which is what my changes 
are reflecting. 

Did more people got approved to be added?

thanks!
Jess

On Thu Jun 14 17:44:17 2018, gildas.lani...@huawei.com wrote:
> Multiple folks asking got the same :(
> 
> Refer to attached email for details.
>  https://lists.onap.org/pipermail/onap-tsc/2018-June/004978.html
> Thanks,
> Gildas
> ONAP Release Manager
> 1 415 238 6287
> 
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap- 
> helpd...@rt.linuxfoundation.org]
> Sent: Thursday, June 14, 2018 1:03 PM
> Cc: Gildas Lanilis 
> Subject: [ONAP Helpdesk #57232] committer election results : VNFRQTS.
> VVP
> 
> Dear Steven and Gildas.
> 
> Is there a TSC like link I can use as a reference for the INFO file?
> 
> I cannot use a link to a wiki page.
> 
> Thanks!
>   Jess
> 
> On Wed Jun 13 09:38:47 2018, sw3...@att.com wrote:
> > Committer election / promotion results have been posted to the 
> > project wikis for the following projects
> >
> > VNFRQTS Hagop
> > Bozawglanian<https://wiki.onap.org/display/DW/Hagop+Bozawglanian>
> > VVP   Steve
> > Stark<https://wiki.onap.org/display/DW/Steven+Stark>
> >
> > The Resources and Repo's
> >  wiki<https://wiki.onap.org/display/DW/Resources+and+Repositories>
> > has
> > been updated accordingly.
> >
> > Please update their access in the LF systems accordingly.
> >
> > best regards
> > Steven Wright, MBA, PhD, JD.
> > [Tech Integration]
> > AT Services Inc.
> > 1057 Lenox Park Blvd NE, STE 4D28
> > Atlanta, GA 30319
> 
> 
> 




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

Re: [onap-tsc] [ONAP Helpdesk #57232] committer election results : VNFRQTS. VVP

[Gildas Lanilis]

Hi Jess,

Yes Steven for VVP and Hagop for vnfrqts.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, June 18, 2018 3:06 PM
To: sw3...@att.com
Cc: Gildas Lanilis ; onap-tsc@lists.onap.org
Subject: [ONAP Helpdesk #57232] committer election results : VNFRQTS. VVP

Hi Gildas, 

>From the email you mentioned 
>"https://lists.onap.org/pipermail/onap-tsc/2018-June/004978.html;
I can only see both Steve and Hagop being requested, which is what my changes 
are reflecting. 

Did more people got approved to be added?

thanks!
Jess

On Thu Jun 14 17:44:17 2018, gildas.lani...@huawei.com wrote:
> Multiple folks asking got the same :(
> 
> Refer to attached email for details.
>  https://lists.onap.org/pipermail/onap-tsc/2018-June/004978.html
> Thanks,
> Gildas
> ONAP Release Manager
> 1 415 238 6287
> 
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap- 
> helpd...@rt.linuxfoundation.org]
> Sent: Thursday, June 14, 2018 1:03 PM
> Cc: Gildas Lanilis 
> Subject: [ONAP Helpdesk #57232] committer election results : VNFRQTS.
> VVP
> 
> Dear Steven and Gildas.
> 
> Is there a TSC like link I can use as a reference for the INFO file?
> 
> I cannot use a link to a wiki page.
> 
> Thanks!
>   Jess
> 
> On Wed Jun 13 09:38:47 2018, sw3...@att.com wrote:
> > Committer election / promotion results have been posted to the 
> > project wikis for the following projects
> >
> > VNFRQTS Hagop
> > Bozawglanian<https://wiki.onap.org/display/DW/Hagop+Bozawglanian>
> > VVP   Steve
> > Stark<https://wiki.onap.org/display/DW/Steven+Stark>
> >
> > The Resources and Repo's
> >  wiki<https://wiki.onap.org/display/DW/Resources+and+Repositories>
> > has
> > been updated accordingly.
> >
> > Please update their access in the LF systems accordingly.
> >
> > best regards
> > Steven Wright, MBA, PhD, JD.
> > [Tech Integration]
> > AT Services Inc.
> > 1057 Lenox Park Blvd NE, STE 4D28
> > Atlanta, GA 30319
> 
> 
> 



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

Re: [onap-tsc] [ONAP Helpdesk #57232] committer election results : VNFRQTS. VVP

[Gildas Lanilis via RT]

Multiple folks asking got the same :(

Refer to attached email for details.
https://lists.onap.org/pipermail/onap-tsc/2018-June/004978.html 
Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, June 14, 2018 1:03 PM
Cc: Gildas Lanilis 
Subject: [ONAP Helpdesk #57232] committer election results : VNFRQTS. VVP

Dear Steven and Gildas. 

Is there a TSC like link I can use as a reference for the INFO file?

I cannot use a link to a wiki page.

Thanks!
Jess  

On Wed Jun 13 09:38:47 2018, sw3...@att.com wrote:
> Committer election / promotion results have been posted to the project 
> wikis for the following projects
> 
> VNFRQTS Hagop
> Bozawglanian<https://wiki.onap.org/display/DW/Hagop+Bozawglanian>
> VVP   Steve
> Stark<https://wiki.onap.org/display/DW/Steven+Stark>
> 
> The Resources and Repo's
> wiki<https://wiki.onap.org/display/DW/Resources+and+Repositories> has 
> been updated accordingly.
> 
> Please update their access in the LF systems accordingly.
> 
> best regards
> Steven Wright, MBA, PhD, JD.
> [Tech Integration]
> AT Services Inc.
> 1057 Lenox Park Blvd NE, STE 4D28
> Atlanta, GA 30319




Hi Jess,



Evidences are now available for:


VVP: Add Steve Stark LFID: ss820f


as committer at https://wiki.onap.org/display/DW/Steven+Stark





VNFRQTS: Hagop Bozawglanian LFID: hb755d


as committer https://wiki.onap.org/display/DW/Hagop+Bozawglanian



Steve also made the announcement to TSC at 
https://lists.onap.org/pipermail/onap-tsc/2018-June/004978.html



Please proceed to add them both.



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: WRIGHT, STEVEN A [mailto:sw3...@att.com]
Sent: Wednesday, June 13, 2018 6:30 AM
To: Gildas Lanilis ; 
onap-helpd...@rt.linuxfoundation.org
Subject: RE: [ONAP Helpdesk #56972] FW: [vnfrqts] CNFRQTS committer actions



Voting results fort VVP election added to the Wiki now



best regards

Steven Wright, MBA, PhD, JD.



AT Services Inc.

1057 Lenox Park Blvd NE, STE 4D28

Atlanta, GA 30319



-Original Message-

From: Gildas Lanilis 
mailto:gildas.lani...@huawei.com>>

Sent: Monday, June 11, 2018 4:31 PM

To: 
onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>;
 WRIGHT, STEVEN A mailto:sw3...@att.com>>

Subject: RE: [ONAP Helpdesk #56972] FW: [vnfrqts] CNFRQTS committer actions



Yes the removal. However for adding Hagop Bozawglanian as a new committer, I do 
NOT see in 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Hagop-2BBozawglanian=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=PVu8DKytqBISpqDc36NHSA=foSCTahIiTn8BqcAmLX3IRTK77T4qTTPr4RCFnA3v14=lw-j7vwobouZYd1Mz2mhKs61_YRyX5Z6eHiYIuCcEAw=
 the outcome of the vote from the existing VNFRQTS committers.







Same concerns for the VVP, for Steven Stark, project where there is no vote 
evidence from current VVP committers in 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Steven-2BStark=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=PVu8DKytqBISpqDc36NHSA=foSCTahIiTn8BqcAmLX3IRTK77T4qTTPr4RCFnA3v14=AR-0fqgQ7m2mQPNXFJh5Liv1KNsLvqfcsuOICEbmSl0=







Thanks,



Gildas



ONAP Release Manager



1 415 238 6287







-Original Message-



From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]



Sent: Monday, June 11, 2018 1:22 PM



Cc: Gildas Lanilis mailto:gildas.lani...@huawei.com>>



Subject: [ONAP Helpdesk #56972] FW: [vnfrqts] CNFRQTS committer actions







Dear Gildas,







This is just a small reminder.







Do you approve this removal request?







Thanks!



Jess







On Wed Jun 06 14:51:11 2018, jwagantall wrote:



> + Gildas,



>



> Sure Steven, we need Gildas to approve this request.



>



> Gildas, do you approve this?



>



> Thanks!



> Jess



>



> On Wed Jun 06 08:50:07 2018, sw3...@att.com<mailto:sw3...@att.com> wrote:



> > Hi Jessica,



> > The names below should be removed as committters for VNFRQTS under



> > section 3.2.2.3 of the ONAP technical community document. I have



> > updated the resources and repos



> > Wiki<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=PVu8DKytqBISpqDc36NHSA=foSCTahIiTn8BqcAmLX3IRTK77T4qTTPr4RCFnA3v14=GRrss6fKTtbye6ZLFA8Lg-xqwida9laaOUtI5ABd8ho=>.



> > Could you adjust their permissions accordingly



> >



> > best regards



> > Steven Wright, MBA, PhD, JD.



> > [Tech Integration]



> > AT Services Inc.



> > 1057 Lenox Park Blvd NE, STE 4D28



> > Atlanta, GA 30319



> >



> > From: WRIGHT, STEVEN A

[onap-tsc] Casablanca Requirements

[Gildas Lanilis]

Hi All,

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

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

1.   Use Cases

2.   Functional Requirements

3.   Non Functional Requirements

with an identified owner and the projects impacted.

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

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

* Adding missing owners

* Identifying impacted projects

* Adding link to complementary set of information

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

Thanks,
Gildas

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

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

Re: [onap-tsc] Beijing Lessons Learned

[Gildas Lanilis]

Hi Alla,

I fully understand there are other important meetings in parallel. As we had to 
make it this week, we have offered choices by offering 2 sessions for "Lessons 
Learned" and 2 sessions for "Process Improvements" to accommodate the largest 
audience possible.
We also suggested people to share their feedback directly within the wiki at 
https://wiki.onap.org/display/DW/ONAP+Beijing+Retrospective+and+Lesson+Learned

Hope this helps. See you next week in Beijing.

Best Regards,
Gildas
ONAP Release Manager
1 415 238 6287

From: Alla Goldner [mailto:alla.gold...@amdocs.com]
Sent: Sunday, June 10, 2018 7:41 AM
To: Gildas Lanilis ; onap-disc...@lists.onap.org; 
onap-tsc ; onap-rele...@lists.onap.org
Subject: RE: Beijing Lessons Learned

Gildas,

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

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.jpg@01D401AA.341AD9B0]


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


Dear ONAP Community,

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

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

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

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

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

Many thanks & regards
Catherine & Gildas

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



Hi there,



Gildas Lanilis is inviting you to a scheduled Zoom meeting.



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



Phone one-tap:

US: +16465588656,,2229355644# or 
+16699006833,,2229355644#



Meeting URL:

https://zoom.us/j/2229355644



Join by Telephone



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



Dial:


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



Meeting ID:

222 935 5644



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
















  << File: ATT1.txt >>

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

Re: [onap-tsc] TSC follow up: Project intent to participate in Casablanca Release

[Gildas Lanilis]

Hi Alex,

The list is for projects on their intention to pursue in Casablanca.
Looks like we have them all (except MSB and Holmes for now) and thus we should 
bring to the community the fact further work is required to complete Beijing 
work into Casablanca Release (my guess is case by case here).
Same for the S3P requirements.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Vul, Alex [mailto:alex@intel.com]
Sent: Friday, June 08, 2018 9:21 PM
To: Gildas Lanilis ; onap-tsc 

Subject: RE: [onap-tsc] TSC follow up: Project intent to participate in 
Casablanca Release

Hi Gildas,

How do we account for the functional requirement work that was started in 
Beijing and will need to continue in Casablanca? It's not part of your list.

Thank you in advance,

Alex Vul
Intel Corporation



From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Friday, June 8, 2018 07:10
To: onap-tsc mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] TSC follow up: Project intent to participate in Casablanca 
Release

Hi,

This is to follow up on an action item from the TSC meeting on June 7, 2018 
regarding Projects intent to participate into Casablanca Release.

2 dimensions:

1)  Existing Beijing Projects: have up to June 14 to formulate their 
intention. Current list is posted in 
wiki<https://wiki.onap.org/display/DW/Project+Status+in+Casablanca+Release>.

2)  Proposed Projects: current list is posted in 
wiki<https://wiki.onap.org/display/DW/Proposed+Projects>. For those who have 
not scheduled a placeholder for Architecture review, please contact Christopher 
Donley<mailto:christopher.don...@huawei.com?subject=Project%20proposal%20for%20Architecture%20Review>
 asap.

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

Thanks,
Gildas

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

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

[onap-tsc] TSC follow up: Project intent to participate in Casablanca Release

[Gildas Lanilis]

Hi,

This is to follow up on an action item from the TSC meeting on June 7, 2018 
regarding Projects intent to participate into Casablanca Release.

2 dimensions:

1)  Existing Beijing Projects: have up to June 14 to formulate their 
intention. Current list is posted in 
wiki<https://wiki.onap.org/display/DW/Project+Status+in+Casablanca+Release>.

2)  Proposed Projects: current list is posted in 
wiki<https://wiki.onap.org/display/DW/Proposed+Projects>. For those who have 
not scheduled a placeholder for Architecture review, please contact Christopher 
Donley<mailto:christopher.don...@huawei.com?subject=Project%20proposal%20for%20Architecture%20Review>
 asap.

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

Thanks,
Gildas

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

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

[onap-tsc] Casablanca Process Improvement

[Gildas Lanilis]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Gildas Lanilis:MAILTO:gildas.lani...@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
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-relea
 s...@lists.onap.org:MAILTO:onap-rele...@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Dear ONAP Community\,\n\nWe are organizing sever
 al brainstorming sessions next week in order to determine any improvement 
 plan for the ONAP Casablanca Release.\nThe first step will be to collect y
 our feedback concerning the ONAP Beijing Release from a retrospective and 
 lesson learned perspectives.\nBased on what we have learned\, we will prio
 ritize on what can be addressed as “Process Improvement” in short in l
 onger term.\n\nPlanning:\nMonday-Tuesday: Lesson Learned\nWednesday-Thursd
 ay: Process Improvement\n\nIt is important to understand that during Lesso
 n Learned session\, the goal is to collect feedback\, not to fix things.\n
 During the “Process Improvement” sessions\, we will dive on the “how
 ” to fix it.\n\nBeing realistic\, we may need more time to discuss while
  we meet at Beijing. Ideally\, we would like to get the low hanging fruits
  approved by TSC while at Beijing.\nFeel free to submit already your feedb
 ack on the ONAP wiki page:\nhttps://wiki.onap.org/display/DW/ONAP+Beijing+
 Retrospective+and+Lesson+Learned\n\nWe are suggesting to classify your inp
 uts under the following categories\n• Communication – Wiki\, Mailing L
 ists\, IRC\n• Labs & Test Environment\n• Release Management\n• JIRA 
 Management\n• Code Review\n• Development Infrastructure\n• PTL Role\
 n• Architecture\n• Open Source Values\n•   Others\n\n\n[https://
 d24cgw3uvb9a9h.cloudfront.net/static/90981/image/new/ZoomLogo_110_25.png]<
 http://zoom.us/>\n\nHi there\,\n\nGildas Lanilis is inviting you to a sche
 duled Zoom meeting.\n\nJoin Zoom Meeting\n\n
 Phone one-tap:\nUS: +16465588656\,\,2229355644# or +16699006833\,\,2229355644#\n\nMe
 eting URL:\nhttps://zoom.us/j/2229355644\n\nJoin by Telephone\n\nFor highe
 r quality\, dial a number based on your current location.\n\nDial:\n\nUS: 
 +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 87
 7 369 0926 (Toll Free)\n\nMeeting ID:\n222 935 5644\n\nInternational numbe
 rs\n\n\n\n\n\n\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:Casablanca Process Improvement
DTSTART;TZID=Pacific Standard Time:20180614T11
DTEND;TZID=Pacific Standard Time:20180614T12
UID:04008200E00074C5B7101A82E008306869FA7FFED301000
 01000B04CE697B45C3E4FA349E2F8FD5D124B
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180607T235253Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/2229355644
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:176646114
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] Beijing Lessons Learned

[Gildas Lanilis]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Gildas Lanilis:MAILTO:gildas.lani...@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
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-relea
 s...@lists.onap.org:MAILTO:onap-rele...@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Dear ONAP Community\,\n\nWe are organizing sever
 al brainstorming sessions next week in order to determine any improvement 
 plan for the ONAP Casablanca Release.\nThe first step will be to collect y
 our feedback concerning the ONAP Beijing Release from a retrospective and 
 lesson learned perspectives.\nBased on what we have learned\, we will prio
 ritize on what can be addressed as “Process Improvement” in short in l
 onger term.\n\nPlanning:\nMonday-Tuesday: Lesson Learned\nWednesday-Thursd
 ay: Process Improvement\n\nIt is important to understand that during Lesso
 n Learned session\, the goal is to collect feedback\, not to fix things.\n
 During the “Process Improvement” sessions\, we will dive on the “how
 ” to fix it.\n\nBeing realistic\, we may need more time to discuss while
  we meet at Beijing. Ideally\, we would like to get the low hanging fruits
  approved by TSC while at Beijing.\nFeel free to submit already your feedb
 ack on the ONAP wiki page:\nhttps://wiki.onap.org/display/DW/ONAP+Beijing+
 Retrospective+and+Lesson+Learned\n\nWe are suggesting to classify your inp
 uts under the following categories\n• Communication – Wiki\, Mailing L
 ists\, IRC\n• Labs & Test Environment\n• Release Management\n• JIRA 
 Management\n• Code Review\n• Development Infrastructure\n• PTL Role\
 n• Architecture\n• Open Source Values\n•   Others\n\nMany thanks
  & regards\nCatherine & Gildas\n\n[https://d24cgw3uvb9a9h.cloudfront.net/s
 tatic/90981/image/new/ZoomLogo_110_25.png]\n\nHi there\,\
 n\nGildas Lanilis is inviting you to a scheduled Zoom meeting.\n\nJoin Zoo
 m Meeting\n\nPhone one-tap:\nUS: +1646558865
 6\,\,2229355644# or +16699006833\,\,222935
 5644#\n\nMeeting URL:\nhttps://zoom.us/j/2
 229355644\n\nJoin by Telephone\n\nFor higher quality\, dial a number based
  on your current location.\n\nDial:\n\nUS: +1 646 558 8656 or +1 669 900 6
 833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)\n\nMeeti
 ng ID:\n222 935 5644\n\nInternational numbers\n\n
 \n\n\n\n\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:Beijing Lessons Learned
DTSTART;TZID=Pacific Standard Time:20180612T08
DTEND;TZID=Pacific Standard Time:20180612T09
UID:04008200E00074C5B7101A82E00870E439F57FFED301000
 0100086E2FED65B0C7244A97D0CCFB94D1CC1
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180607T235245Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/2229355644
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:176646114
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] Beijing Lessons Learned

[Gildas Lanilis]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Gildas Lanilis:MAILTO:gildas.lani...@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
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-relea
 s...@lists.onap.org:MAILTO:onap-rele...@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Dear ONAP Community\,\n\nWe are organizing sever
 al brainstorming sessions next week in order to determine any improvement 
 plan for the ONAP Casablanca Release.\nThe first step will be to collect y
 our feedback concerning the ONAP Beijing Release from a retrospective and 
 lesson learned perspectives.\nBased on what we have learned\, we will prio
 ritize on what can be addressed as “Process Improvement” in short in l
 onger term.\n\nPlanning:\nMonday-Tuesday: Lesson Learned\nWednesday-Thursd
 ay: Process Improvement\n\nIt is important to understand that during Lesso
 n Learned session\, the goal is to collect feedback\, not to fix things.\n
 During the “Process Improvement” sessions\, we will dive on the “how
 ” to fix it.\n\nBeing realistic\, we may need more time to discuss while
  we meet at Beijing. Ideally\, we would like to get the low hanging fruits
  approved by TSC while at Beijing.\nFeel free to submit already your feedb
 ack on the ONAP wiki page:\nhttps://wiki.onap.org/display/DW/ONAP+Beijing+
 Retrospective+and+Lesson+Learned\n\nWe are suggesting to classify your inp
 uts under the following categories\n• Communication – Wiki\, Mailing L
 ists\, IRC\n• Labs & Test Environment\n• Release Management\n• JIRA 
 Management\n• Code Review\n• Development Infrastructure\n• PTL Role\
 n• Architecture\n• Open Source Values\n•   Others\n\nMany thanks
  & regards\nCatherine & Gildas\n\n[https://d24cgw3uvb9a9h.cloudfront.net/s
 tatic/90981/image/new/ZoomLogo_110_25.png]\n\nHi there\,\
 n\nGildas Lanilis is inviting you to a scheduled Zoom meeting.\n\nJoin Zoo
 m Meeting\n\nPhone one-tap:\nUS: +1646558865
 6\,\,2229355644# or +16699006833\,\,222935
 5644#\n\nMeeting URL:\nhttps://zoom.us/j/2
 229355644\n\nJoin by Telephone\n\nFor higher quality\, dial a number based
  on your current location.\n\nDial:\n\nUS: +1 646 558 8656 or +1 669 900 6
 833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free)\n\nMeeti
 ng ID:\n222 935 5644\n\nInternational numbers\n\n
 \n\n\n\n\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:Beijing Lessons Learned
DTSTART;TZID=Pacific Standard Time:20180611T07
DTEND;TZID=Pacific Standard Time:20180611T08
UID:04008200E00074C5B7101A82E008005FFB6E76FED301000
 0100097C07201EBA2DC419425518F6895BD33
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180607T235224Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/2229355644
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:176646114
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] ONAP Daily Bugs report Beijing Release

[Gildas Lanilis]

Hi All,

For today, I will make the ONAP Daily Bugs report short.
For transparency, there are still 4 defects to  address. Please update defect 
status as your progress toward resolution.
[cid:image003.jpg@01D3F9F7.8E08DC20]


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

Thanks,
Gildas

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

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

Re: [onap-tsc] ONAP Daily Bugs report Beijing Release

[Gildas Lanilis]

Hi All,

For today, I will make the ONAP Daily Bugs report short.
For transparency, there are still 4 defects to  address:
[cid:image001.jpg@01D3F914.2D0AEFF0]

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

Thanks,
Gildas

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

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

Re: [onap-tsc] Federating Jira to LF Jira

[Gildas Lanilis]

Hi,

I tend to believe that in order for the TSC to approve/reject this request, LF 
IT should present a short slide deck with the benefits it would bring to the 
community.
My 2 cents.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Jessica Wagantall [mailto:jwagant...@linuxfoundation.org]
Sent: Wednesday, May 23, 2018 11:07 AM
To: onap-tsc <onap-tsc@lists.onap.org>; Gildas Lanilis 
<gildas.lani...@huawei.com>; Kenny Paul <kp...@linuxfoundation.org>; Jeremy 
Phelps <jphe...@linuxfoundation.org>
Subject: Re: [onap-tsc] Federating Jira to LF Jira

Small reminder on this.

We would like to allow LF Jira instance 
(https://jira.linuxfoundation.org<https://jira.linuxfoundation.org/>) to 
federate with the project Jira instance allowing us to cross reference Jira 
tickets between our respective Jira systems.

Can we please approve/reject this request?

Thanks!
Jess

On Thu, May 10, 2018 at 11:09 AM, Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>> wrote:
Dear Gildas and TSC members,

Can we bring up this topic with the team please?

Thanks!
Jess


-- Forwarded message --
From: Thanh Ha 
<thanh...@linuxfoundation.org<mailto:thanh...@linuxfoundation.org>>
Date: Thu, Apr 12, 2018 at 3:15 PM
Subject: [onap-tsc] Federating Jira to LF Jira
To:

Greetings TSC,

I would like to propose that we allow the LF Jira instance 
(https://jira.linuxfoundation.org<https://jira.linuxfoundation.org/>) to 
federate with the project Jira instance allowing us to cross reference Jira 
tickets between our respective Jira systems.

Is this a topic that can be brought up at the next TSC meeting agenda?

Thanks,
Thanh


___
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] [onap-discuss] [ONAP Helpdesk #55868] RE: [LF] Request new JIRA project - CD - for all continuous delivery/deployment work

[Gildas Lanilis]

Hi,

I would like to propose, we postpone the discussion and potential changes after 
Beijing Release is out of the door.
Focusing on getting the ONAP working is the urgency for now.

Thanks for your understanding,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Jessica Wagantall via 
RT
Sent: Tuesday, May 15, 2018 1:12 PM
To: frank.obr...@amdocs.com
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: [onap-discuss] [ONAP Helpdesk #55868] RE: [onap-tsc] [LF] Request new 
JIRA project - CD - for all continuous delivery/deployment work

Please let me know if I can help. 

Any new projects in Jira will also need Gildas' approval. 

thanks!
Jess

On Tue May 15 13:29:02 2018, frank.obr...@amdocs.com wrote:
> Team,
> Moved all the CD/infrastructure jiras/work around 710 into the 
> logging-analytics project for now
> Will request a scope change from the Architecture subcommittee 
> between the 29th and 5th
> /michael
> 
> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc- 
> boun...@lists.onap.org] On Behalf Of Michael O'Brien
> Sent: Thursday, May 10, 2018 9:15 PM
> To: onap-disc...@lists.onap.org; onap-tsc 
> Cc: 'helpd...@onap.org' 
> Subject: Re: [onap-tsc] [LF] Request new JIRA project - CD - for all 
> continuous delivery/deployment work
> 
> Including the Linux Foundation
> 
> From: onap-tsc-boun...@lists.onap.org boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On 
> Behalf Of Michael O'Brien
> Sent: Thursday, May 10, 2018 12:05 PM
> To: onap-disc...@lists.onap.org;
> onap-tsc >
> Subject: [onap-tsc] [LF] Request new JIRA project - CD - for all 
> continuous delivery/deployment work
> 
> Gildas,
>I would like to request a new JIRA project for CD (Continuous
> Delivery) related work.
> 
> CD
> 
> https://jira.onap.org/secure/BrowseProjects.jspa?selectedCategory=all;
> selectedProjectType=software
> 
> We don't need other artifacts at this time like a git repo, Jenkins 
> infrastructure etc this is not a full project.
> I can send out a weekly meeting schedule.
> 
> Had a talk with Roger who raised the project idea and maybe a separate 
> weekly meeting - and when he suggested this - It really makes sense 
> for the following reasons.
> We are currently talking with several teams - OPNFV, CNCF, Gitlab and 
> ONAP member CD deployments - and it would be ideal if we had a place 
> to plan all the CD work independent of any particular project 
> (currently INT and OOM and CIMAN) Currently there is a lot of CD work 
> going on across the teams - some of which are listed below.
> Gary and I work with our two teams in OOM and Integration meetings 
> very well on CD work - but a separate JIRA project would help to bring 
> in members from OPNFV for example and make the CD work (which is 
> currently essential in measuring the daily health of ONAP) its own 
> entity.
> Note: the scope of CD is to work with the existing CI system (CIMAN) 
> in only deploying and running integration testing (all automatic).  It 
> would also consolidate templates/scripts for all cloud-native 
> deployment options (openstack/aws/azure) we currently run.
> 
> As you can see I also burden the OOM project with all the CD 
> epics/stories tracking CD related work - especially the OOM-710 tasks.
> https://jira.onap.org/browse/OOM-150
> https://jira.onap.org/browse/OOM-393
> https://jira.onap.org/browse/OOM-500
> https://jira.onap.org/browse/OOM-710
> https://jira.onap.org/browse/INT-361
> https://jira.onap.org/browse/INT-300
> https://jira.onap.org/browse/INT-369
> https://jira.onap.org/browse/AAI-189
> https://jira.onap.org/browse/CIMAN-156
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement, you may 
> review at https://www.amdocs.com/about/email-disclaimer
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement, you may 
> review at https://www.amdocs.com/about/email-disclaimer
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

Re: [onap-tsc] [onap-discuss] [ONAP Helpdesk #55868] RE: [LF] Request new JIRA project - CD - for all continuous delivery/deployment work

[Gildas Lanilis via RT]

Hi,

I would like to propose, we postpone the discussion and potential changes after 
Beijing Release is out of the door.
Focusing on getting the ONAP working is the urgency for now.

Thanks for your understanding,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Jessica Wagantall via 
RT
Sent: Tuesday, May 15, 2018 1:12 PM
To: frank.obr...@amdocs.com
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: [onap-discuss] [ONAP Helpdesk #55868] RE: [onap-tsc] [LF] Request new 
JIRA project - CD - for all continuous delivery/deployment work

Please let me know if I can help. 

Any new projects in Jira will also need Gildas' approval. 

thanks!
Jess

On Tue May 15 13:29:02 2018, frank.obr...@amdocs.com wrote:
> Team,
> Moved all the CD/infrastructure jiras/work around 710 into the 
> logging-analytics project for now
> Will request a scope change from the Architecture subcommittee 
> between the 29th and 5th
> /michael
> 
> From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc- 
> boun...@lists.onap.org] On Behalf Of Michael O'Brien
> Sent: Thursday, May 10, 2018 9:15 PM
> To: onap-disc...@lists.onap.org; onap-tsc 
> Cc: 'helpd...@onap.org' 
> Subject: Re: [onap-tsc] [LF] Request new JIRA project - CD - for all 
> continuous delivery/deployment work
> 
> Including the Linux Foundation
> 
> From: onap-tsc-boun...@lists.onap.org boun...@lists.onap.org> [mailto:onap-tsc-boun...@lists.onap.org] On 
> Behalf Of Michael O'Brien
> Sent: Thursday, May 10, 2018 12:05 PM
> To: onap-disc...@lists.onap.org;
> onap-tsc >
> Subject: [onap-tsc] [LF] Request new JIRA project - CD - for all 
> continuous delivery/deployment work
> 
> Gildas,
>I would like to request a new JIRA project for CD (Continuous
> Delivery) related work.
> 
> CD
> 
> https://jira.onap.org/secure/BrowseProjects.jspa?selectedCategory=all;
> selectedProjectType=software
> 
> We don't need other artifacts at this time like a git repo, Jenkins 
> infrastructure etc this is not a full project.
> I can send out a weekly meeting schedule.
> 
> Had a talk with Roger who raised the project idea and maybe a separate 
> weekly meeting - and when he suggested this - It really makes sense 
> for the following reasons.
> We are currently talking with several teams - OPNFV, CNCF, Gitlab and 
> ONAP member CD deployments - and it would be ideal if we had a place 
> to plan all the CD work independent of any particular project 
> (currently INT and OOM and CIMAN) Currently there is a lot of CD work 
> going on across the teams - some of which are listed below.
> Gary and I work with our two teams in OOM and Integration meetings 
> very well on CD work - but a separate JIRA project would help to bring 
> in members from OPNFV for example and make the CD work (which is 
> currently essential in measuring the daily health of ONAP) its own 
> entity.
> Note: the scope of CD is to work with the existing CI system (CIMAN) 
> in only deploying and running integration testing (all automatic).  It 
> would also consolidate templates/scripts for all cloud-native 
> deployment options (openstack/aws/azure) we currently run.
> 
> As you can see I also burden the OOM project with all the CD 
> epics/stories tracking CD related work - especially the OOM-710 tasks.
> https://jira.onap.org/browse/OOM-150
> https://jira.onap.org/browse/OOM-393
> https://jira.onap.org/browse/OOM-500
> https://jira.onap.org/browse/OOM-710
> https://jira.onap.org/browse/INT-361
> https://jira.onap.org/browse/INT-300
> https://jira.onap.org/browse/INT-369
> https://jira.onap.org/browse/AAI-189
> https://jira.onap.org/browse/CIMAN-156
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement, you may 
> review at https://www.amdocs.com/about/email-disclaimer
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement, you may 
> review at https://www.amdocs.com/about/email-disclaimer
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

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

[onap-tsc] TSC Decision to postpone Beijing Release Sign-Off by 2 weeks

[Gildas Lanilis]

Hi All,

This email is to communicate the decision the TSC has taken to postpone the 
Sign-Off of Beijing Release by 2 weeks.
The new dates becomes:

  1.  RC2: Thursday, May 31, 2018
  2.  Sign-Off: Thursday, June 7, 2018
This decision will allow the community to complete the tasks related to 
Integration testing and bugs fixing on the following scope:

1.   S3P (Stability, Security, Resiliency) + vCPE + VoLTE

2.   Supporting both OOM and HEAT deployment
The Functional Requirements (HPA, CM, Manual Scaling Out) remain a stretch goal 
for Beijing Release.
The vote decision is documented in IRC 
Log<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2018/onap-meeting.2018-05-17-13.46.html>
 (Topic Integration, section am).
The Beijing Release 
Calendar<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-BeijngReleaseCalendar>
 has been updated accordingly.
Materials presented at TSC are posted in wiki 
here<https://wiki.onap.org/download/attachments/28381539/ONAP%20Beijing%20RC2%20Status%20Summary%20Version2.pdf?version=1=1526583956000=v2>
 and 
here<https://wiki.onap.org/download/thumbnails/28381539/ONAP%20Beijing%20RC2%20Project%20Status.PNG?version=1=1526583899000=v2>.
Let me know if you have any question, I will be glad to help.
Thanks,
Gildas

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

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

[onap-tsc] ONAP RC2 Release candidate 2 for Beijing Release

[Gildas Lanilis]

Hi PTLs,

RC2 is coming this Thursday, May 19. As usual, fill out the 
template<https://wiki.onap.org/display/DW/Deliverables+for+RCx+Milestone+Checklist+Template>.
 Please make it possible to join the bridge or send out a delegate. TSC may 
have questions on which we expect timely responses.

TSC will be looking status on the following:


1.   S3P

2.   vFW / vLB + vCPE + VoLTE regression use case

3.   Functional Requirements

Please update the high level project status in wiki at 
https://wiki.onap.org/display/DW/Integration+Weather+Board as well as the page 
specific to your project.

In case we still have some High and Highest priority defects, we will need to 
understand how these defects are impacting Beijing Release. Please have a close 
look at the "ONAP Daily Bugs report Beijing Release".

As we are reaching the end of the release, we need to be sensitive in not 
breaking the build and thus I am encouraging PTLs and Committers to consider 
only merging what is supporting the delivery of Beijing Release.

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

Thanks,
Gildas

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

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

[onap-tsc] [Committer Addition and removal] SO

[Gildas Lanilis]

Hi TSC Voting Members,

This is to inform you that the following person have been either promoted or 
removed as a committers on SO project.

For the record, the evidences are available in 
wiki<https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+%5BService+Orchestrator%5D+-+10th+May+2018>.

Addition: Welcome onboard SO team

1.   Marcus Williams

2.   Sanchita Pathak

Removal: Thanks for your contribution in SO project

1.   Tal Liron

2.   Heliu Zhong

3.   Yuanwei Yang


Thanks,
Gildas

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

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

[onap-tsc] ONAP RC1 Release candidate 1 for Beijing Release

[Gildas Lanilis]

Hi PTLs,

I wanted to follow up on the discussion we had at weekly PTL meeting today.

RC1 is coming this Thursday, May 3. As usual, fill out the 
template<https://wiki.onap.org/display/DW/Deliverables+for+RCx+Milestone+Checklist+Template>.
 Please make it possible to join the bridge or send out a delegate. TSC may 
have questions on which we expect timely responses.

Criteria for RC1 as discussed on TSC meeting is:



1.   Pass OOM Deployment (and heat for contingency)

2.   Pass Pair Wise testing for all projects

3.   Pass vFW / vLB + vCPE + VoLTE regression use case for projects on 
critical path

Please update the Pair Wise status in wiki from 
https://wiki.onap.org/display/DW/Integration+Weather+Board

For the vFW / vLB + vCPE + VoLTE  Use cases, Helen and Brian will confirm the 
status during RC1.

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

Thanks,
Gildas

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

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

Re: [onap-tsc] [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - add new java and python child repos

[Gildas Lanilis via RT]

Hi Michael,

Currently for logging there is 1 repo labelled "logging-analytics". This repo 
can't be renamed.
LF will need to create 2 new repo
> Logging-analytics/java
> Logging-analytics/python

And you will need to move the code appropriately, then LF will need to lock the 
" logging-analytics" repo.

In term of timing, I fear this is not the right time to do it before Beijing 
Sign-Off.

Thoughts?

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Michael O'Brien [mailto:frank.obr...@amdocs.com] 
Sent: Sunday, April 29, 2018 5:43 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: Gildas Lanilis <gildas.lani...@huawei.com>; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: RE: [ONAP Helpdesk #55393] [LOG] New repo request for 
logging-analytics - add new java and python child repos

Yes, both issues are ok
We can have just 2 top level repos - like you propose The history can be 
deleted if this makes it easier - if you can preserve it - preserve it on the 
repo where all the existing code will go - the java one.
You can put everything on one side for now - as the python folder will need to 
be moved and a new root pom.xml for it.

Anything to help out the transition - the goal is to have separate CSIT, CLM, 
Docker, Sonar jobs Thank you /michael


-Original Message-
From: Anil Belur via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Sunday, April 29, 2018 8:39 PM
To: Michael O'Brien <frank.obr...@amdocs.com>
Cc: gildas.lani...@huawei.com; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - 
add new java and python child repos

On Sun Apr 29 19:28:26 2018, frank.obr...@amdocs.com wrote:
> LF, Gildas,
>We would like to split the current logging-analytics repo into 
> python and java.  Currently the shared repo root pom.xml is causing 
> issues running both technologies both offline and with jobs running on 
> jenkins.
>I would like to formally request 2 new repos.
> 
> https://git.onap.org/logging-analytics/
> 
> Logging-analytics/java
> Logging-analytics/python
> 
> In the future we will likely add a "go" repo - but not until we have 
> some artifacts in that language.
> 
> Thank you
> /michael
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://www.amdocs.com/about/email-disclaimer>

Hello Michael 

Please clarify the following to split the code into new repositories:

1. Do you need the git histroy preserved from the original repository, split 
into both the repos?
2. Can we rename the repositories as below, instead of have the repositories 
under separate folder `logging-analytics`? Doing this would be easier to 
maintain.
   logging-analytics-java
   logging-analytics-python
 
Thanks,
Anil

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

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

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

Re: [onap-tsc] [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - add new java and python child repos

[Gildas Lanilis]

Hi Michael,

Currently for logging there is 1 repo labelled "logging-analytics". This repo 
can't be renamed.
LF will need to create 2 new repo
> Logging-analytics/java
> Logging-analytics/python

And you will need to move the code appropriately, then LF will need to lock the 
" logging-analytics" repo.

In term of timing, I fear this is not the right time to do it before Beijing 
Sign-Off.

Thoughts?

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Michael O'Brien [mailto:frank.obr...@amdocs.com] 
Sent: Sunday, April 29, 2018 5:43 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: Gildas Lanilis <gildas.lani...@huawei.com>; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: RE: [ONAP Helpdesk #55393] [LOG] New repo request for 
logging-analytics - add new java and python child repos

Yes, both issues are ok
We can have just 2 top level repos - like you propose The history can be 
deleted if this makes it easier - if you can preserve it - preserve it on the 
repo where all the existing code will go - the java one.
You can put everything on one side for now - as the python folder will need to 
be moved and a new root pom.xml for it.

Anything to help out the transition - the goal is to have separate CSIT, CLM, 
Docker, Sonar jobs Thank you /michael


-Original Message-
From: Anil Belur via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Sunday, April 29, 2018 8:39 PM
To: Michael O'Brien <frank.obr...@amdocs.com>
Cc: gildas.lani...@huawei.com; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - 
add new java and python child repos

On Sun Apr 29 19:28:26 2018, frank.obr...@amdocs.com wrote:
> LF, Gildas,
>We would like to split the current logging-analytics repo into 
> python and java.  Currently the shared repo root pom.xml is causing 
> issues running both technologies both offline and with jobs running on 
> jenkins.
>I would like to formally request 2 new repos.
> 
> https://git.onap.org/logging-analytics/
> 
> Logging-analytics/java
> Logging-analytics/python
> 
> In the future we will likely add a "go" repo - but not until we have 
> some artifacts in that language.
> 
> Thank you
> /michael
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://www.amdocs.com/about/email-disclaimer>

Hello Michael 

Please clarify the following to split the code into new repositories:

1. Do you need the git histroy preserved from the original repository, split 
into both the repos?
2. Can we rename the repositories as below, instead of have the repositories 
under separate folder `logging-analytics`? Doing this would be easier to 
maintain.
   logging-analytics-java
   logging-analytics-python
 
Thanks,
Anil

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

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

[onap-tsc] [Committer Addition] OOF- Ankit Patel

[Gildas Lanilis]

Hi TSC Voting Members,

This is to inform you that Ankit Patel has been promoted as a committer of OOF 
project to accommodate the urgent need of the team in the absence of Sastry 
Isukapalli.
For the record, the evidence are available in 
wiki<https://wiki.onap.org/display/DW/Committer+Promotion+Request+for+OOF>.

Thanks,
Gildas

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

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

Re: [onap-tsc] [Onap-lf-announce] Jenkins and Nexus downtime

[Gildas Lanilis]

Dear TSC member,

Nexus 3 is so slow that it will really help the ONAP community to have that 
work done asap.
This slowness of Nexus 3 is drastically impacting OOM and Heat deployment time. 
It will worth the 90 down time.
Not sure if Kenny is asking for a vote, but please respond asap so the work 
could be done tomorrow as planned.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-lf-announce-boun...@lists.onap.org 
[mailto:onap-lf-announce-boun...@lists.onap.org] On Behalf Of Kenny Paul
Sent: Tuesday, April 17, 2018 6:21 PM
To: onap-tsc 
Cc: onap-lf-annou...@lists.onap.org
Subject: Re: [Onap-lf-announce] Jenkins and Nexus downtime

Given where we are in the release cycle, I've asked IT to hang off on this 
pending input form the TSC. This down time has been requested as the result of 
a call this morning discussing extremely long durations to pull docker images. 
The expectation is this will improve that issue.

Basically, I'm looking for a thumbs-up from the TSC Members before proceeding 
with scheduling down time.

Best Regards,
-kenny

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


From: 
>
 on behalf of Jeremy Phelps 
>
Date: Tuesday, April 17, 2018 at 4:15 PM
To: >
Subject: Re: [Onap-lf-announce] Jenkins and Nexus downtime

Date correction in the year:
Start Date/Time:
  - 8:30 am Pacific April 18, 2018
  - 
https://www.worldtimebuddy.com/?qm=1=8,100,4641239=8=2018-4-18=8.5-10
Systems affected:
  - jenkins.onap.org
  - nexus3.onap.org
Why:
  - LF IT is migrating the nexus3 system to a new node
Expected Downtime:
  - 1.5 hours

On Tue, Apr 17, 2018 at 6:10 PM, Jeremy Phelps 
> wrote:
Start Date/Time:
  - 8:30 am Pacific April 18, 2019
  - 
https://www.worldtimebuddy.com/?qm=1=8,100,4641239=8=2018-4-18=8.5-10
Systems affected:
  - jenkins.onap.org
  - nexus3.onap.org
Why:
  - LF IT is migrating the nexus3 system to a new node
Expected Downtime:
  - 1.5 hours

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

[onap-tsc] RC0 Release candidate 0 for Beijing Release

[Gildas Lanilis]

Hi PTLs,

RC0 Release candidate 0 review for Beijing Release is coming and will be hold 
this Thursday, April 19 at 7 am PDT during the weekly TSC Meeting.
Please make it possible to join the bridge or send out a delegate. TSC may have 
questions on which we expect timely responses.


1.   As usual, please make a copy and fill out the RC0 
template<https://wiki.onap.org/display/DW/Deliverables+for+RCx+Milestone+Checklist+Template>.
 I would appreciate if you could fill it out by COB on Tuesday, April 17. Early 
is even better so we have time to clarify items (if necessary).

2.   Focus on the following items:

a.   Passing the Jenkins Health 
Check<https://jenkins.onap.org/view/External%20Labs/>

b.  Jenkins Daily Job<https://jenkins.onap.org/view/Daily-Jobs/>

c.   Jenkins CSIT<https://jenkins.onap.org/view/CSIT/>

d.  Closing any item from previous milestones

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

Thanks,
Gildas

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

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

Re: [onap-tsc] Casablanca Timeline

[Gildas Lanilis]

Hi Srini,

This is certainly a very good scope question.
As per the ONAP release milestone process, the functionalities scoped in at M1 
"Release Planning" for a  given release have to be implemented by "M4 Code 
Freeze".

Working ahead, whenever possible, is certainly a good approach if timing is an 
issue.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Addepalli, Srinivasa R [mailto:srinivasa.r.addepa...@intel.com]
Sent: Thursday, April 12, 2018 10:55 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-tsc@lists.onap.org
Cc: TALASILA, MANOOP (MANOOP) <talas...@research.att.com>; Bainbridge, David 
<dbain...@ciena.com>; Ethan Lynn <ethanly...@vmware.com>; DRAGOSH, PAMELA L 
(PAM) <pdrag...@research.att.com>; Beejal Shah <beejal.s...@amdocs.com>; 
friedel.ke...@orange.com; Lefevre, Catherine <cl6...@intl.att.com>
Subject: RE: Casablanca Timeline

Hi,

I can't make it at 7:00AM PST due to a conflict.

I have one clarification question.

As I understand TOSCA DM Model is expected to be finalized by 08/30.  This 
gives around 3 to 4 weeks' time to complete the implementation in various ONAP 
project to reach code freeze milestone.  My question : Is the expectation that 
all relevant ONAP projects implement logic to enable TOSCA based orchestration 
in Casablanca?

Thanks
Srini


-Original Appointment-
From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Thursday, April 12, 2018 10:48 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Cc: TALASILA, MANOOP (MANOOP); Bainbridge, David; Ethan Lynn; DRAGOSH, PAMELA L 
(PAM); Beejal Shah; friedel.ke...@orange.com<mailto:friedel.ke...@orange.com>; 
Lefevre, Catherine
Subject: [onap-tsc] Casablanca Timeline
When: Friday, April 13, 2018 7:00 AM-8:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/2229355644


Meeting Update: I got multiple requests to arrange this meeting 1 hour earlier 
starting at 7 am PDT. I understand this is kind of short notice and that 
everyone can't make it.
Please post your feedback in wiki at 
https://wiki.onap.org/display/DW/Release+Planning
Thanks,
Gildas
=

Hi All,

This is to follow up with TSC meeting to discuss Casablanca Timeline and the 
following items:
1.   Pair-wise testing
2.   CI-CD
3.   Offset milestone
4.   E2E Deployment code freeze (including upgrade)

In the meantime, feel free to post your comments in wiki page at 
https://wiki.onap.org/display/DW/Release+Planning

Thanks,
Gildas
[https://d24cgw3uvb9a9h.cloudfront.net/static/90733/image/new/ZoomLogo_110_25.png]<http://zoom.us/>



Hi there,



Gildas Lanilis is inviting you to a scheduled Zoom meeting.



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



Phone one-tap:

US: +16465588656,,2229355644#<tel:+16465588656,,2229355644> or 
+16699006833,,2229355644#<tel:+16699006833,,2229355644>



Meeting URL:

https://zoom.us/j/2229355644



Join by Telephone



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



Dial:


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



Meeting ID:

222 935 5644



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
















  << File: ONAPCasablancaTimelineV2.pptx >>  << File: ATT1.txt >>

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

Re: [onap-tsc] Casablanca Release Timeline draft proposal for review

[Gildas Lanilis]

Hi Alla,

I have updated the 
timeline<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-CasablancaReleasePlanning>
 to take into account your suggestion and set the "E2E release Use case 
approved" milestone for end of April beg of May (we can adjust if needed).
With the creation of the end-user advisory group, I would appreciate if you 
could provide intermediate steps to reach the "E2E release Use case approved".

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Alla Goldner [mailto:alla.gold...@amdocs.com]
Sent: Tuesday, March 27, 2018 7:10 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-tsc@lists.onap.org; 
onap-release <onap-rele...@lists.onap.org>
Subject: RE: Casablanca Release Timeline draft proposal for review

Hi Gildas,

Thanks a lot for preparing this. We really need pre-M1 milestones to be defined 
as discussed yesterday during use cases/requirements presentation.
However, I don't think it is realistic to assume middle of April as E2E release 
Use case approved - for that we would need SP input (which is missing 
currently) plus a more clear technical definition of all input requirements.
I would say end of April may work, conditionally, based on SP feedback.

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D3CDD2.7A3CAF60]

From: 
onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org> 
[mailto:onap-release-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Tuesday, March 27, 2018 2:33 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-release 
<onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>
Subject: [Onap-release] Casablanca Release Timeline draft proposal for review

Hi All,

During ONAP Break out session at ONS Los Angeles on March 26, 2018 a draft 
proposal for Casablanca Release Timeline was presented.
Find 
here<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-CasablancaRelease>
 the link toward the materials for your reviews and comments.
Please post your reviews and comments directly at the bottom of the wiki, that 
will help everyone for transparency, avoid of duplicates and make our inboxes 
lighter :).
Thanks for your honest feedback

Thanks,
Gildas

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

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

Re: [onap-tsc] Known vulnerability analysis of AAF

[Gildas Lanilis]

Hi Jonathan, All Milestones dates for Beijing are available here 
https://wiki.onap.org/display/DW/Release+Planning

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of GATHMAN, JONATHAN C
Sent: Tuesday, April 03, 2018 7:33 AM
To: Stephen Terrill 
Cc: onap-sec...@lists.onap.org; GANDHAM, SAI ; KOYA, RAMPRASAD 
; onap-tsc 
Subject: Re: [onap-tsc] Known vulnerability analysis of AAF

Hey Steve,
  When are the dates for RC0,RC1 (If you have a calendar link, I don’t have 
that)?

  My current efforts are
1)  Sonar to report AAF accurately (what is left is getting “Coverage” 
numbers… we had some improvement just this morning… nice to have headway)
2)  Getting the AAF Beijing release working in Winriver VMs.
3)  Getting the best Cassandra,J2EE and Mailer versions that 
eliminate/limit Security issues from dependent libraries.

  When those are working, I’ll be able to swing around and see what we can do 
on those other elements.

  Do you happen to know if anybody else uses Bouncey Castle, and if there are 
better versions out there without the security issues?  That might be a good 
approach.

  In terms of Vulnerability, Bouncey Castle is used exclusively to help 
facilitate Certificate Creation. (AAF Certman).  It is not in any of the 
Service, GUI, Locate, etc components.


--
Jonathan Gathman
Principled-System Architect
ATO Tech Dev/SEAT/Platform Architecture and Technology Management

AT Services, Inc.
2349 Oaker, Arnold, MO 63010
m  314-550-3312  |  
jonathan.gath...@us.att.com

From: Stephen Terrill 
>
Date: Tuesday, April 3, 2018 at 9:26 AM
To: "GATHMAN, JONATHAN C" >
Cc: "onap-sec...@lists.onap.org" 
>, onap-tsc 
>, RAMPRASAD KOYA 
>, "GANDHAM, SAI" 
>, "ZWARICO, AMY" 
>
Subject: RE: Known vulnerability analysis of AAF

Hi Jonathan,

Thanks for the reply.  It would be good to know:
-  Do you think that this will be done by RC0, RC1….?
-  If it turns out you can’t replace the version, it would be good to 
what exposure ONAP has to the vulnerability.  Sometimes it turns out ONAP is 
not exposed due to the way that ONAP uses the components.

BR,

Steve

From: GATHMAN, JONATHAN C [mailto:jg1...@att.com]
Sent: Tuesday, April 03, 2018 2:53 AM
To: Stephen Terrill 
>
Cc: onap-sec...@lists.onap.org; onap-tsc 
>; KOYA, RAMPRASAD 
>; GANDHAM, SAI 
>; ZWARICO, AMY 
>
Subject: Re: Known vulnerability analysis of AAF

Hi Steve,
  We are using “BounceyCastle” for part of the CA work.  I will have to look 
into whether I can remove easily.

  Io.netty and org.apache.httpcomponents are derived dependencies from 
Cassandra.  I’m making inquiries as to what Cassandra Versions we can use to 
get free of License issues as well as whatever flaws you have noted.

--
Jonathan Gathman
Principled-System Architect
ATO Tech Dev/SEAT/Platform Architecture and Technology Management

AT Services, Inc.
2349 Oaker, Arnold, MO 63010
m  314-550-3312  |  
jonathan.gath...@us.att.com

From: RAMPRASAD KOYA >
Date: Monday, April 2, 2018 at 5:39 PM
To: Stephen Terrill 
>, "GATHMAN, 
JONATHAN C" >, "GANDHAM, SAI" 
>
Cc: "onap-sec...@lists.onap.org" 
>, onap-tsc 
>
Subject: RE: Known vulnerability analysis of AAF

Sai, Jonathan – Any thoughts on this?

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Monday, April 02, 2018 2:59 AM
To: KOYA, RAMPRASAD >
Cc: onap-sec...@lists.onap.org; onap-tsc 
>
Subject: Known vulnerability analysis of AAF

Hi Ram,

Thanks for the review of the known vulnerabilities for AAF: 

Re: [onap-tsc] Casablanca Release Timeline draft proposal for review

[Gildas Lanilis]

Hi Vladimir,

Since I wrote this email, a bit of changes came into play (cf attached email). 
There is the introduction of end-user advisory committee who help into defining 
priorities and will feed in the usecase committee.
The "E2E Release Use Case Approval" milestone help into streamlining the work 
before we do project planning.

More to come on this during TSC meeting this Thursday.
In case you have not seen this, Casablanca goals are being defined here 
https://wiki.onap.org/display/DW/Casablanca+goals

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Vladimir Yanover (vyanover) [mailto:vyano...@cisco.com]
Sent: Tuesday, March 27, 2018 1:25 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-tsc@lists.onap.org; 
onap-release <onap-rele...@lists.onap.org>
Subject: RE: Casablanca Release Timeline draft proposal for review

Gildas,
Can you please clarify what is "E2E Release Use Case approved"?
Thanks
Vladimir

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
<onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org>> On 
Behalf Of Gildas Lanilis
Sent: Tuesday, March 27, 2018 2:33 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>; onap-release 
<onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>
Subject: [onap-tsc] Casablanca Release Timeline draft proposal for review

Hi All,

During ONAP Break out session at ONS Los Angeles on March 26, 2018 a draft 
proposal for Casablanca Release Timeline was presented.
Find 
here<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-CasablancaRelease>
 the link toward the materials for your reviews and comments.
Please post your reviews and comments directly at the bottom of the wiki, that 
will help everyone for transparency, avoid of duplicates and make our inboxes 
lighter :).
Thanks for your honest feedback

Thanks,
Gildas

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

--- Begin Message ---
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-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-usecase...@lists.onap.org<mailto:onap-usecase...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@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 pict

Re: [onap-tsc] Casablanca release goals Venn diagram

[Gildas Lanilis]

Thanks Ranny for creating the Gliffy diagram.
You deciphered properly all my handwritting:)

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Haiby, Ranny (Nokia - US/San Jose) [mailto:ranny.ha...@nokia.com]
Sent: Friday, March 30, 2018 11:20 AM
To: onap-tsc <onap-tsc@lists.onap.org>
Cc: Perala, Timo (Nokia - FI/Espoo) <timo.per...@nokia.com>; Gildas Lanilis 
<gildas.lani...@huawei.com>
Subject: Casablanca release goals Venn diagram

I had a hard time reading the handwritten diagram, so I created a Gliffy 
version on the wiki:
https://wiki.onap.org/display/DW/Casablanca+goals

I would appreciate it if the participants of the meeting where the diagram was 
created will add some details to the "Legend" section of the wiki page.

Regards,

Ranny.



[Kuva]


Sent from Nokia8

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

Re: [onap-tsc] M4 Code Freeze for Beijing Release

[Gildas Lanilis]

Hi All,

I noticed the Platform 
Maturity<https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity> 
table (Level achieved 1-4) and Functional 
Requirements<https://wiki.onap.org/display/DW/Beijing+Functional+Requirements> 
(Yes/No answer) are not systematically complete.
Please do so, that will help to understand where we collectively stand.

In case you are attending ONS, I am physically in Silver Lake A room developer 
lounge, feel free to stop by.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Thursday, March 22, 2018 3:53 PM
To: onap-release <onap-rele...@lists.onap.org>
Cc: 'Steve Winslow' <swins...@linuxfoundation.org>; Phil Robb 
<pr...@linuxfoundation.org>; 'Kenny Paul' <kp...@linuxfoundation.org>; 
onap-tsc@lists.onap.org
Subject: M4 Code Freeze for Beijing Release

Hi PTLs,

M4 Code Freeze review for Beijing Release is coming and will be hold on March 
29 at 7 am PDT during the weekly TSC Meeting.
Please make it possible to join the bridge or send out a delegate. TSC may have 
questions on which we expect timely responses.


1.   As usual, please make a copy and fill out the M4 
template<https://wiki.onap.org/display/DW/Deliverable+for+Code+Freeze+Milestone+Checklist+Template>.
 I would appreciate if you could fill it out by COB on Tuesday, March 27. Early 
is even better so we have time to clarify items (if necessary).

2.   At M1, the teams have made commitments in regards to Platform Maturity 
and Functional requirements. The commitments were all recorded in a central 
wiki page. As M4 Code freeze is coming, the community needs to understand where 
the teams stand in regards to these commitments and such the request is you 
update accordingly the column labelled "R4 result" for Platform 
Maturity<https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity> 
(Level achieved 1-4) and Functional 
Requirements<https://wiki.onap.org/display/DW/Beijing+Functional+Requirements> 
(Yes/No answer). Please answer by the intent the team had to develop these 
commitments, not by the outcome of integration testing which we have not 
performed yet.   I know we are not living in a perfect world, some defects will 
come out of the testing and collectively we will address them. The critical 
point is to create awareness in case some of these commitments would not be in 
the scope of Beijing Release.

3.   The community will be also looking at:

a.   Code Coverage for each Java and Python repo in the scope of Beijing 
Release. 50% line code coverage is the target in 
Sonar<https://sonar.onap.org/projects?sort=name>. In case you are facing 
difficulty in seeing your code coverage in Sonar, please create a LF ticket and 
CC me.

b.  CSIT testing: check that all the CSIT pass in 
Jenkins<https://jenkins.onap.org/view/CSIT/>.

c.   CLM Nexus-IQ report: All critical (level 8-9) license issues addressed 
and all critical (level 7-10) security issue either fixed or properly 
documented in wiki by using 
template<https://wiki.onap.org/pages/viewpage.action?pageId=25435956>. These 
templates will be used as a reference point from your components Release Notes.

d.  The pending commits older than 36 
hours<https://gerrit.onap.org/r/#/q/status:open+age:36h>. By pending we mean a 
commit on which no activity happened during the last 36 business hours. Back 
and forth reviews is seen as activity and does not count as pending. Skin in 
the game matter :).

e.  Keep the Risk you have identified in centralized table 
up-to-date<https://wiki.onap.org/display/DW/Beijing+Risks>. The world in 
changing fast. In case a risk will not become an issue, update its status to 
"Not occurred". In case a risk materialized and became an issue, update its 
status to "In-process".

I will be attending ONS next week and will be glad to seat with you to address 
any questions you may have. For those who cannot make it to ONS, if needed let 
me know and I will open a Zoom meeting on first come first served.
Let me know if you have any questions.

Wish us all the best in making this reality.

Thanks,
Gildas

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

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

[onap-tsc] Casablanca Release Timeline draft proposal for review

[Gildas Lanilis]

Hi All,

During ONAP Break out session at ONS Los Angeles on March 26, 2018 a draft 
proposal for Casablanca Release Timeline was presented.
Find 
here<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-CasablancaRelease>
 the link toward the materials for your reviews and comments.
Please post your reviews and comments directly at the bottom of the wiki, that 
will help everyone for transparency, avoid of duplicates and make our inboxes 
lighter :).
Thanks for your honest feedback

Thanks,
Gildas

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

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

[onap-tsc] M4 Code Freeze for Beijing Release

[Gildas Lanilis]

Hi PTLs,

M4 Code Freeze review for Beijing Release is coming and will be hold on March 
29 at 7 am PDT during the weekly TSC Meeting.
Please make it possible to join the bridge or send out a delegate. TSC may have 
questions on which we expect timely responses.


1.   As usual, please make a copy and fill out the M4 
template<https://wiki.onap.org/display/DW/Deliverable+for+Code+Freeze+Milestone+Checklist+Template>.
 I would appreciate if you could fill it out by COB on Tuesday, March 27. Early 
is even better so we have time to clarify items (if necessary).

2.   At M1, the teams have made commitments in regards to Platform Maturity 
and Functional requirements. The commitments were all recorded in a central 
wiki page. As M4 Code freeze is coming, the community needs to understand where 
the teams stand in regards to these commitments and such the request is you 
update accordingly the column labelled "R4 result" for Platform 
Maturity<https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity> 
(Level achieved 1-4) and Functional 
Requirements<https://wiki.onap.org/display/DW/Beijing+Functional+Requirements> 
(Yes/No answer). Please answer by the intent the team had to develop these 
commitments, not by the outcome of integration testing which we have not 
performed yet.   I know we are not living in a perfect world, some defects will 
come out of the testing and collectively we will address them. The critical 
point is to create awareness in case some of these commitments would not be in 
the scope of Beijing Release.

3.   The community will be also looking at:

a.   Code Coverage for each Java and Python repo in the scope of Beijing 
Release. 50% line code coverage is the target in 
Sonar<https://sonar.onap.org/projects?sort=name>. In case you are facing 
difficulty in seeing your code coverage in Sonar, please create a LF ticket and 
CC me.

b.  CSIT testing: check that all the CSIT pass in 
Jenkins<https://jenkins.onap.org/view/CSIT/>.

c.   CLM Nexus-IQ report: All critical (level 8-9) license issues addressed 
and all critical (level 7-10) security issue either fixed or properly 
documented in wiki by using 
template<https://wiki.onap.org/pages/viewpage.action?pageId=25435956>. These 
templates will be used as a reference point from your components Release Notes.

d.  The pending commits older than 36 
hours<https://gerrit.onap.org/r/#/q/status:open+age:36h>. By pending we mean a 
commit on which no activity happened during the last 36 business hours. Back 
and forth reviews is seen as activity and does not count as pending. Skin in 
the game matter :).

e.  Keep the Risk you have identified in centralized table 
up-to-date<https://wiki.onap.org/display/DW/Beijing+Risks>. The world in 
changing fast. In case a risk will not become an issue, update its status to 
"Not occurred". In case a risk materialized and became an issue, update its 
status to "In-process".

I will be attending ONS next week and will be glad to seat with you to address 
any questions you may have. For those who cannot make it to ONS, if needed let 
me know and I will open a Zoom meeting on first come first served.
Let me know if you have any questions.

Wish us all the best in making this reality.

Thanks,
Gildas

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

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

Re: [onap-tsc] Invitation: TSC Meeting (updated Mar. 8, 2018) @ Weekly from 7am to 8:30am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 (PDT) (onap-tsc@lists.onap.org)

[Gildas Lanilis]

Hi Kenny,

I thoughts you were supposed to lead a small working group on this.
Whatever we decide, having a meeting invite in my Outlook calendar is critical 
to me.

Like Alex, my outlook calendar is also pointing the weekly TSC meeting at 2 pm 
PDT ☹

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Thursday, March 22, 2018 2:11 PM
To: Vul, Alex ; onap-tsc@lists.onap.org
Cc: jphe...@linuxfoundation.org
Subject: Re: [onap-tsc] Invitation: TSC Meeting (updated Mar. 8, 2018) @ Weekly 
from 7am to 8:30am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 (PDT) 
(onap-tsc@lists.onap.org)

Hi Alex,

07:00 to 08:30 Pacific is correct.
Where g-cal is generating times such as 14:00 to 15:30 Pacific  I have not a 
clue, however it is the primary reason why I am yelling bad words at my monitor 
numerous times a day.

As a general question to the Community, are we getting sufficient value from 
the g-cal integration with the wiki to continue using it?
Would we be better off simply using the native wiki calendar?

Best Regards,
-kenny

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


On Mar 22, 2018, at 1:49 PM, Vul, Alex 
> wrote:

Kenny,

Is this a valid ONAP meeting???

Thanks,

Alex


-Original Appointment-
From: ONAP Meetings and Events 
[mailto:linuxfoundation.org_1rmtb5tpr3uc8f76fmflplo...@group.calendar.google.com]
Sent: Thursday, March 8, 2018 3:58 PM
To: ONAP Meetings and Events; 
onap-tsc@lists.onap.org; 
jwagant...@linuxfoundation.org; Andrew 
Grimberg; jphe...@linuxfoundation.org
Subject: [onap-tsc] Invitation: TSC Meeting (updated Mar. 8, 2018) @ Weekly 
from 7am to 8:30am on Thursday from Thu Mar 15 to Thu Feb 21, 2019 (PDT) 
(onap-tsc@lists.onap.org)
When: Thursday, March 22, 2018 2:00 PM-3:30 PM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://zoom.us/j/661303200


more details 
»
TSC Meeting (updated Mar. 8, 2018)
When

Weekly from 7am to 8:30am on Thursday from Thu Mar 15 to Thu Feb 21, 
2019 Pacific Time



Where

https://zoom.us/j/661303200 
(map)



Calendar

onap-tsc@lists.onap.org



Who

•

kp...@linuxfoundation.org - creator



•

onap-tsc@lists.onap.org



•

jwagant...@linuxfoundation.org



•

Andrew Grimberg



•

jphe...@linuxfoundation.org







Hi there,
ONAPmeet1 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/661303200
Or iPhone one-tap :
US: +16465588656,,661303200# or +16699006833,,661303200#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 
369 0926 (Toll Free)
Meeting ID: 661 303 200
International numbers available: 
https://zoom.us/zoomconference?m=FHWF11_wwIutwd1PAi_vsotA5bQ6kCLh




Going?   All events in this series:   
Yes
 - 
Maybe
 - 

Re: [onap-tsc] Community Announcement- PTL Self Code Merge Vote

[Gildas Lanilis]

I think we should highlight the specific circumstances that were brought up by 
PTLs during TSC meeting last Thursday.

In normal circumstances, PTLs agreed they must not merged their own code. 
However, in circumstances such as just editing one line in a pom.xml file to 
change the version on a dependency, the PTL would made the merge. In such case 
a code review is not necessary, the goal in mind is to be effective and speed 
up process of delivering. We need to trust our PTLs. As anything we all do is 
public, I would like to believe good citizenship will prevail.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of GILBERT, MAZIN E (MAZIN E)
Sent: Saturday, March 17, 2018 4:53 AM
To: Kenny Paul 
Cc: onap-tsc@lists.onap.org P 
Subject: Re: [onap-tsc] Community Announcement- PTL Self Code Merge Vote

But this will give PTLs in other companies the ability to push their own code,
or even code from their colleagues that they claim is theirs. This impacts code
quality process. I am not very comfortable letting this happen, frankly.




On Mar 15, 2018, at 6:30 PM, Kenny Paul 
> wrote:

This is to inform the community that the following item is being forwarded to 
the TSC for an email vote as per today’s TSC meeting.

The TSC approves changing the General Code Commit Rules as documented under 
Approved Operational 
Policies
 to allow PTLs merging their own commit provided there is a time critical need 
and provided that the justification for doing so is documented in the code 
review comments.


THIS IS NOT THE CALL TO VOTE!  The formal vote will occur on the onap-tsc-vote 
alias, not here.
A plus-one, minus-one, or zero here on this issue is null and void.

Best Regards,
-kenny

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

___
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=IKSC5mg8GeOiSar1dax3GQ=7zFgm0XTqg3Zx-CI5PQJjIaYUEokDvu_xPWfdYtfc1U=E69yU-W3pvKTigIC3quTyF5mmRe3_RQBnjNiohgBzeo=

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

Re: [onap-tsc] M3 Beijing Functionality Freeze is coming

[Gildas Lanilis]

Yes Srini. Please have your project on Chris'list for ARC review on Tuesday.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Addepalli, Srinivasa R [mailto:srinivasa.r.addepa...@intel.com]
Sent: Friday, March 02, 2018 5:03 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-rele...@lists.onap.org
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: RE: M3 Beijing Functionality Freeze is coming

Hi Gildas,

A question on this
"I would like to highlight the most important item is related to this question 
"Has the Project team reviewed the APIs with the Architecture Committee (ARC)?" 
"

Should this review with ARC be expected to be done before 8th?

Thanks
Srini


From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Friday, March 2, 2018 4:45 PM
To: onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>
Cc: onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: [onap-tsc] M3 Beijing Functionality Freeze is coming

Dear PTLs,

According to the Beijing Release 
Planning<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-BeijngReleaseCalendar>
 Thursday, March 8 is the Beijing M3 API 
Freeze<https://wiki.onap.org/display/DW/Release+Lifecycle#ReleaseLifecycle-ReleaseAPIFreeze>.
It is expected that PTL fills out a copy of the M3 API Freeze 
Checklist<https://wiki.onap.org/display/DW/Deliverables+for+API+Freeze+Milestone+Checklist+Template>
 in their project workspace.

I would like to highlight the most important item is related to this question 
"Has the Project team reviewed the APIs with the Architecture Committee (ARC)?"
As Chris suggested in former PTL and TSC meetings, bring your design-API 
related work to ARC meeting for review.

As you progress in this exercise, I will review the M3 artifacts and provide a 
summary to the community during TSC Meeting on Thursday, March 8. If you have 
any questions or concerns please reach out, I will be glad to help.

Thanks,
Gildas

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

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

[onap-tsc] M3 Beijing Functionality Freeze is coming

[Gildas Lanilis]

Dear PTLs,

According to the Beijing Release 
Planning<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-BeijngReleaseCalendar>
 Thursday, March 8 is the Beijing M3 API 
Freeze<https://wiki.onap.org/display/DW/Release+Lifecycle#ReleaseLifecycle-ReleaseAPIFreeze>.
It is expected that PTL fills out a copy of the M3 API Freeze 
Checklist<https://wiki.onap.org/display/DW/Deliverables+for+API+Freeze+Milestone+Checklist+Template>
 in their project workspace.

I would like to highlight the most important item is related to this question 
"Has the Project team reviewed the APIs with the Architecture Committee (ARC)?"
As Chris suggested in former PTL and TSC meetings, bring your design-API 
related work to ARC meeting for review.

As you progress in this exercise, I will review the M3 artifacts and provide a 
summary to the community during TSC Meeting on Thursday, March 8. If you have 
any questions or concerns please reach out, I will be glad to help.

Thanks,
Gildas

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

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

Re: [onap-tsc] tagging issues

[Gildas Lanilis]

Hi Eric,

To help the discussion on tagging, I would like to indicate that tagging is 
made in multiple locations.
From what I know I see:

1)  Tagging at the repository level: that was done by LF when we had the 
first release of Amsterdam on Nov 16 and then later for the maintenance release 
in January.

2)  Tagging the docker images: As Helen pointed out, we have been working 
with numerous people and LF on this. Jira Ticket is 
here.

3)  We also have the Manifest files that record the version of the Binary 
artifacts
 and Docker 
artifacts
 once they are released

4)  Not familiar with the 
file 
you have shared in the Demo repo, but I guess this file is pulling information 
from the above.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Yunxia Chen
Sent: Wednesday, February 28, 2018 10:41 AM
To: eric.deb...@orange.com; onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] tagging issues

Hi, Eric,
I agree with you: this indeed a concern.
Right now, Gildas, Ran and Gary are working with Linux foundation on this one 
and hopefully to get a solution very soon. And I also expect a stable master 
branch build, meaning we could run some basic sanity testing, more 
specifically, passing health test, running the automated vFW and vLB use case. 
And each day, we could tag what have successfully passed above testing.

Regards,

Helen Chen

From: > 
on behalf of Eric Debeau >
Date: Wednesday, February 28, 2018 at 10:09 AM
To: onap-tsc >
Subject: [onap-tsc] tagging issues

Hello

We still have some problems in the ONAP versioning/tagging.
In the Amsterdam version environment file 
(https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.env?h=amsterdam) , 
there is still one project based on master branch.

The Docker tags are not all aligned (some start with v, other with a figure) 
and all there is still missing a lot of latest tags on Docker images under the 
DockerHub repo.

As we will jump in Beijing and then Casablanca, Dublin,  we  should have a 
latest-stable release to avoid to manage various branches and the version 
namings.

Best Regards

Eric

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

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

[onap-tsc] [Committer Removal] AAI- Steven Smokowski

[Gildas Lanilis]

Hi TSC Voting Members,

This is to inform you that Steven Smokowski has decided to step down from his 
committer role on AAI.
For the record, the correspondence between Jimmy (AAI PTL) and Steven is posted 
in 
wiki<https://wiki.onap.org/display/DW/Removing+Committers+to+AAI+Project+for+Steven+Smokowski>.
Thanks Steven for your services.

Thanks,
Gildas

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

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

[onap-tsc] Jenkins Daily Jobs

[Gildas Lanilis]

Hi All,

I wanted to update the community on an issue that was raised during weekly PTL 
meeting regarding the Jenkins Daily Build and the difficulty to get that job 
executed successfully.

To provide a bit of context, Nexus-staging repo is facing some limitations and 
does not allow to repeatedly build Jenkins daily jobs. As all teams are 
currently in an intense development activities with numerous commits every days 
there is no easy way to build binaries on dependencies that are constantly 
moving.
We had a meeting with the attendees (see below) and, to circumvent this issue, 
we are proposing to not perform Jenkins daily build until we reach M4 Code 
Freeze.
For teams who need to rely on other ONAP cpts they will need to use binaries 
currently available into Nexus-Release.
This approach is a lightweight to avoid teams updating version dependencies in 
pom and manifest files.

LF has provided a way to disable Jenkins Daily Jobs. That will help in not 
consuming resources. Refer to attached email for details. Thanks Jess.

Before you ask, Sonar jobs are currently setup to run every day and this 
independently of the daily builds. Sonar can also be triggered on demand. See 
details in 
wiki<https://wiki.onap.org/display/DW/Configuring+Gerrit#ConfiguringGerrit-RunningaCommandwithinGerrit>.

We will come back with recommendations once we reach M4.

Let us know if you have any questions.

Attendees: jwagant...@linuxfoundation.org; Andrew Grimberg 
<agrimb...@linuxfoundation.org>; Kenny Paul <kp...@linuxfoundation.org>; 
'MAHER, RANDA' <rx1...@att.com>; DRAGOSH, PAMELA L (PAM) 
<pdrag...@research.att.com>; BRADY, PATRICK D <pb0...@att.com>; KAJUR, HARISH V 
<vk2...@att.com>; 'FORSYTH, JAMES' <jf2...@att.com>; Gary Wu 
<gary.i...@huawei.com>; JI, LUSHENG  (LUSHENG) <l...@research.att.com>; CHO, 
TAKAMUNE <tc0...@att.com>

Thanks,
Gildas

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

--- Begin Message ---
Dear team,



The disabled flag is now added in the daily jobs.

Please use this flag whenever you need to disable a project.

For example, if we would wanted to disable 
"policy-common-amsterdam-release-version-java-daily"

We can add the flag like this:



diff --git a/jjb/policy/policy-common.yaml b/jjb/policy/policy-common.yaml

index 779dbce..663d5de 100644

--- a/jjb/policy/policy-common.yaml

+++ b/jjb/policy/policy-common.yaml

@@ -26,7 +26,8 @@

 jobs:

   - '{project-name}-{stream}-verify-java-skip-tests'

   - '{project-name}-{stream}-merge-java'

-  - '{project-name}-{stream}-release-version-java-daily'

+  - '{project-name}-{stream}-release-version-java-daily':

+  disabled: true

   - '{project-name}-{stream}-stage-site-java':

   site-pom: 'pom.xml'

   trigger-job: '{project-name}-{stream}-release-version-java-daily'





Let me know if you have any questions

Thanks!

Jess

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

[onap-tsc] Update: M2 Beijing Functionality Freeze is coming

[Gildas Lanilis]

Dear PTLs,

Following Steve Winslow's recommendations provided at the Virtual F2F earlier 
today I wanted to bring an update on the M2 checklist regarding the Copyright 
Year format.

According to information on slide 
#44,
 from a LF perspective it is not a mandatory practice to update the year 
format. It might be that your company legal counsel may have another 
preference. In such case please conform to your company legal recommendations.

Therefore, as the practice is not mandatory for all projects, I propose you 
mark the item as NA for the question "Has the year format in copyright header 
of all source code files been updated? (Rules for new files created in 2018 and 
existing files modified in 2018 are different)".

Hope this helps. Let me know if you have any questions.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Wednesday, February 07, 2018 8:36 AM
To: onap-rele...@lists.onap.org
Cc: onap-tsc@lists.onap.org; onap-disc...@lists.onap.org
Subject: M2 Beijing Functionality Freeze is coming

Dear PTLs,

According to the Beijing Release 
Planning<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-BeijngReleaseCalendar>
 Monday, Feb 12 is the Beijing M2 Functionality 
Freeze<https://wiki.onap.org/display/DW/Release+Lifecycle#ReleaseLifecycle-ReleaseFunctionalityFreeze>.
It is expected that PTL fills out a copy of the M2 Functionality 
Checklist<https://wiki.onap.org/display/DW/Deliverables+for+Functionality+Freeze+Milestone+Checklist+Template>
 in their project workspace.

As you progress in this exercise, I will review the M2 artifacts and provide a 
summary to the community during extended PTL Meeting on Monday, Feb 12. If you 
have any questions or concerns please reach out, I will be glad to help.

Thanks,
Gildas

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

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

[onap-tsc] M2 Beijing Functionality Freeze is coming

[Gildas Lanilis]

Dear PTLs,

According to the Beijing Release 
Planning<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-BeijngReleaseCalendar>
 Monday, Feb 12 is the Beijing M2 Functionality 
Freeze<https://wiki.onap.org/display/DW/Release+Lifecycle#ReleaseLifecycle-ReleaseFunctionalityFreeze>.
It is expected that PTL fills out a copy of the M2 Functionality 
Checklist<https://wiki.onap.org/display/DW/Deliverables+for+Functionality+Freeze+Milestone+Checklist+Template>
 in their project workspace.

As you progress in this exercise, I will review the M2 artifacts and provide a 
summary to the community during extended PTL Meeting on Monday, Feb 12. If you 
have any questions or concerns please reach out, I will be glad to help.

Thanks,
Gildas

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

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

Re: [onap-tsc] [Onap-release] M2 Requirement for JUnit code coverage

[Gildas Lanilis]

Hi,



Thanks all for sharing your feedback.



I think we all recognize that providing test coverage is something that cannot 
be achieve overnight hence the reason why we have built the checklists and the 
periodic milestones. I guess none of us want to be in the same situation we 
were in M4 for Amsterdam in Paris, negotiating extra time to reach the target.



The basic idea is to start early, unit testing should not be an after thoughts 
but rather baked in. Some repos have already achieve their 50% goals. I can 
even some repos are over 80% code coverage. Excellent work.



Listening to your feedback, I would like to propose the community (the TSC will 
need to decide here) to set 50% code coverage as a stretch goal for M2 and M3 
and a mandatory goal for M4. In the M2 and M3 checklist simply provide a 
screenshot of your progress.



Regarding repos that require Python, LF told me the work is in progress. I am 
hoping to learn a firm date from LF next week during the V F2F. In the 
meantime, as we did in Amsterdam, provide a screenshot of your local code 
coverage.



Here is the link to 
Sonar<https://urldefense.proofpoint.com/v2/url?u=https-3A__sonar.onap.org_=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y=77AGr306xPmtTxr7jxu2MDoUqQZpL_kIMBlhZlnxEQg=RuNscooFGu3NF5LDhD7_jyKAUtFn_fH6k_nhPg2n0rA=>
 to visualize the status (you can sort  it out by “Overall Coverage”, by “Name” 
or by “Last Analysis” date).



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



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Thursday, February 01, 2018 6:45 AM
To: Seshu m <seshu.kuma...@huawei.com>; Gildas Lanilis 
<gildas.lani...@huawei.com>
Cc: onap-rele...@lists.onap.org
Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage



Gildas,



Same here.

Please consider moving 50% as gating requirement for M4.



Thanks,

Lusheng Ji





On 2/1/18, 6:13 AM, "onap-release-boun...@lists.onap.org on behalf of Seshu 
m<mailto:onap-release-boun...@lists.onap.org%20on%20behalf%20of%20Seshu%20m>" 
<onap-release-boun...@lists.onap.org on behalf of 
seshu.kuma...@huawei.com<mailto:onap-release-boun...@lists.onap.org%20on%20behalf%20of%20seshu.kuma...@huawei.com>>
 wrote:



Hi Gildas,







I share the same thoughts, we have the functional aspects being worked upon 
till M2 and still a lot of discussions/clarifications are required there.



So, it would be better to consider 50% code coverage for M4 and 30% for M2.











Best regards



Seshu Kumar M



Huawei Technologies India Pvt, Ltd.











本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁



止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中



的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！



This e-mail 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 herein 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 e-mail in error, please 
notify the sender by



phone or email immediately and delete it!







-Original Message-



From: 
onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org> 
[mailto:onap-release-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine



Sent: Thursday, February 01, 2018 5:40 AM



To: Shankaranarayanan P N



Cc: onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>



Subject: Re: [Onap-release] M2 Requirement for JUnit code coverage







Gildas,







I agree with the feedback provided by the PTLs







The 50% test coverage is a new Beijing requirement as part of S3P/Security 
therefore it should be treated as any other Beijing code deliverable i.e being 
gated at M4 code freeze milestone.







I am not aware that SP3 requirements are expected to be completed earlier.







30% test coverage should be gated at M2/M3 milestone.







Please also note that non-java test coverage can not yet been measured.



We really need to progress on this issue as well.







Best regards



Catherine











Le 31 janv. 2018 à 15:14, Shankaranarayanan P N 
<shankarp...@gmail.com<mailto:shankarp...@gmail.com<mailto:shankarp...@gmail.com%3cmailto:shankarp...@gmail.com>>>
 a écrit :







Hi Gildas,







I have the same concerns that Jimmy and Randa raised here. In particular, 
the seed code for OOF is being upstreamed for the first time in Beijing 
Release. While we do have unit test coverage as one of our priorities in R2, we 
had planned progressive test coverage increase to h

[onap-tsc] ONAP M1 Release Planning Pass

[Gildas Lanilis]

Hi All,

Thanks all for your participations and contributions to the ONAP M1 Release 
Milestones.
In  2 hours as a community we have been able to review and provide dispositions 
for 30 projects. 6 months ago, M1 Review took us 6 hours (and many meetings)!!!
All projects passed M1, a few with some 
conditions<https://wiki.onap.org/display/DW/Project+Status+in+Beijing+Release#ProjectStatusinBeijingRelease-Conditionsonprojects:>.
 Great achievement. Congratulations All.

I have updated the wiki with the keys outcome and deliverables.

1.   Beijing Project 
Status<https://wiki.onap.org/display/DW/Project+Status+in+Beijing+Release> is a 
centralized page with all projects status for each milestones (Pass 
Condition<https://wiki.onap.org/display/DW/Project+Status+in+Beijing+Release#ProjectStatusinBeijingRelease-Conditionsonprojects:>,
 Action 
Items<https://wiki.onap.org/display/DW/Project+Status+in+Beijing+Release#ProjectStatusinBeijingRelease-ActionItems:>).

2.   M1 Beijing Release 
findings<https://wiki.onap.org/download/attachments/16008853/ONAP%20Beijing%20M1%20Release%20PlanningV1.pdf?version=1=1516306382000=v2>
 (PDF format) is the document used to capture the findings and outcome of each 
project.

3.   M1 IRC 
notes<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2018/onap-meeting.2018-01-18-13.51.html>

4.   Beijing Platform 
Maturity<https://wiki.onap.org/display/DW/Beijing+Release+Platform+Maturity> 
summarizes the commitment in regards to Platform Maturity

5.   Beijing Functional 
Requirements<https://wiki.onap.org/display/DW/Beijing+Functional+Requirements> 
summarizes the scope committed by each team

Beside the conditions on some projects, there are 2 actions items:

1.   Performance Maturity: Benchmark-Integration (Jason Hunt -Helen Chen ) 
team to provide performance measurement definition by M2.

2.   Auto-scaling: need for Scott  Blandford and Peng Zhao to bring 
clarification on requirements.
In case there is any mistake or you have any questions please let me know, I 
will be glad to help.

Thanks,
Gildas

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

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

[onap-tsc] TSC Meeting Release Management Action Items

[Gildas Lanilis]

Hi,

This email is to follow up on action items from TSC meeting today more 
specifically on the next 2 points on preparation for M1 next week:

1)  Publish in wiki M1 Release Planning for VVP (Erik Sundelof) and Use 
Case UI (ShenTao)

2)  Fill out Platform Maturity Table:

a.   AAF (Ram)

b.  DMAAP (Ram)

c.   Log (Michael)

d.  MSB (Huabing)

e.  Modeling (Deng)

f.OOM (David)



Links:

Full meeting IRC is 
available<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2018/onap-meeting.2018-01-11-13.55.html>.

Release Management 
deck<https://wiki.onap.org/download/attachments/19202098/ONAP%20TSC%20Jan11V2.pdf?version=1=1515695612537=v2>.


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

Thanks,
Gildas

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

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

[onap-tsc] ONAP Daily Bugs report Amsterdam Maintenance

[Gildas Lanilis]

Hi All,

ONAP Daily Bugs report for Jan 04.
Data  are presented on a 15 days rolling chart.

Observation:

1.   Almost the ideal chart! 1 defect is outside the 15 days rolling 
window. I will follow up with PTL. Great Job. Thanks.

Created vs Resolved Chart:
The top chart displays the cumulative created issue (in red) versus the 
cumulated resolved issue (in green). Ultimately, on the right side of the chart 
the green line should reach the red line.
The lower chart displays in blue the difference between the red line and the 
green line. Ultimately, on the right side of the chart the blue line should 
reach zero.
[cid:image007.jpg@01D38582.7CA69150]
[cid:image008.jpg@01D38582.7CA69150]


Recently Created Chart:
This chart is a derivative from the "Created vs Resolved Chart", and displays 
in a bar chart the number of created issue. The red stack represents the number 
of unresolved issues, the green stack represents the number of resolved issues.
Same data point, just another way to look at things. Ultimately, this chart 
should all be green.
[cid:image009.jpg@01D38582.7CA69150]

Plain List of bugs:
This list represents all ONAP Highest and High priority bugs currently opened 
(status != Closed or status != Done or status != Delivered) and sorted by 
creation date. As the above charts are displaying data on a 15 days rolling 
windows, this list below may contain more bugs.
Ultimately, this list should be empty.
[cid:image010.jpg@01D38582.7CA69150]

Let me know if you have any questions.

Thanks,
Gildas

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

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

[onap-tsc] ONAP Daily Bugs report Amsterdam Maintenance

[Gildas Lanilis]

Hi All,

ONAP Daily Bugs report for Jan 03.
Data  are presented on a 15 days rolling chart.

Created vs Resolved Chart:
The top chart displays the cumulative created issue (in red) versus the 
cumulated resolved issue (in green). Ultimately, on the right side of the chart 
the green line should reach the red line.
The lower chart displays in blue the difference between the red line and the 
green line. Ultimately, on the right side of the chart the blue line should 
reach zero.
[cid:image007.jpg@01D384BC.E3D7B8C0]
[cid:image008.jpg@01D384BC.E3D7B8C0]


Recently Created Chart:
This chart is a derivative from the "Created vs Resolved Chart", and displays 
in a bar chart the number of created issue. The red stack represents the number 
of unresolved issues, the green stack represents the number of resolved issues.
Same data point, just another way to look at things. Ultimately, this chart 
should all be green.
[cid:image009.jpg@01D384BC.E3D7B8C0]

Plain List of bugs:
This list represents all ONAP Highest and High priority bugs currently opened 
(status != Closed or status != Done or status != Delivered) and sorted by 
creation date. As the above charts are displaying data on a 15 days rolling 
windows, this list below may contain more bugs.
Ultimately, this list should be empty.
[cid:image010.jpg@01D384BC.E3D7B8C0]

Let me know if you have any questions.

Thanks,
Gildas

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

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

[onap-tsc] OOO Until Jan 2

[Gildas Lanilis]

Hi All,

I will be OOO for Christmas Holidays returning on Jan 2, 2018.
Wish you all an Happy Holidays season.
In case of urgent mater, I can be reached at the number below.

Thanks,
Gildas

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

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

Re: [onap-tsc] About Image Manager Project Proposal

[Gildas Lanilis]

Hi Huabing,

Thanks for the notice.
Could you ensure the project proposal is visible into the “Proposed Project” at 
https://wiki.onap.org/display/DW/Proposed+Projects (most probably you will just 
need to use the move capability of Confluence)?

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn]
Sent: Thursday, December 07, 2017 9:03 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-tsc@lists.onap.org; onap-disc...@lists.onap.org
Subject: About Image Manager Project Proposal


Hi Gildas and all,



I have requested to defer the Image Manager Project proposal at this week's TSC 
meeting. But after that, we receive some feedback from the community that the 
requirements of Image Manager is important for operators.

So we'd like to add this project back to the F2F project proposal agenda to 
discuss with the TSC and figure out the way going forward.



Thanks,

Huabing








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

[onap-tsc] Status on TSC meeting action item on tagging and branching

[Gildas Lanilis]

Hi,

This is to follow up on the Action Item raised during 
TSC<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-12-07-13.48.html>
 meeting regarding questions brought up by Michael on tagging and branching.

Michael and I discussed and 2 things came up. Clarification were brought up. 
Nothing to worry about. We can close this action item.
Below is the summary.


1)  Tagging: to provide a bit of context, OMM is testing every day its 
latest build by taking into account all the latest Docker images available (not 
the Docker images that were Release on Nov 16 but the Docker images on which 
some teams are currently fixing defects for Amsterdam Maintenance release). 
These Dockers images are not yet released for general consumption. Goal is to 
automate as much as possible and detect as early as possible issue on Docker 
Images. Question is how the define latest? In current Nexus3.org (nexus-staging 
repo), every team is using a different name (snapshot-latest or latest or 
1.2.0-snapshot-sgtagingmmddtime,...). Decision: Michael to investigate with 
his team if there is a consistent and reliable way to determine by scripting 
what is latest. In case this is not possible by scripting, we will need to work 
with project teams to come up with a naming convention.

2)  Branching: For some reasons, OOM has multiple branches that are not all 
really necessary. Currently the team is disciplined and working on a branch 
named release-1.1.0 instead of Amsterdam. We agree with Michael that the team 
will continue working on release-1.1.0 and when we will release Amsterdam 1.0.1 
on January 18, we will work with LF to remove unnecessary branches and rename 
nicely release-1.1.0 to Amsterdam.

Also as we had some questions, just to re-iterate that the Jan 18 Amsterdam 
Maintenance Release version will be 1.0.1. The scope is bugs fix only (High and 
Highest priority). The community is using an independent versioning numbering 
for its own components. This is also further explained in 
wiki<https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-Example:1Major,1Serviceand1EnhancementReleases>.

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

Michael, keep me honest here. I have tried to summarize to key items of our 
discussion.

Thanks,
Gildas

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

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

Re: [onap-tsc] Bridges for next week.

[Gildas Lanilis]

And we won’t have weekly PTL meeting at 6:30 am PDT.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Thursday, December 07, 2017 10:26 AM
To: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: [onap-tsc] Bridges for next week.

Yes there will be dial-ins.
No, I have not set them up yet.
Yes, I will send mail when I’ve done so.

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] Project part of Wiki

[Gildas Lanilis]

Hi Steve,

I have updated the wiki accordingly to reflect this discussion.

Under the top "ONAP Project" section, there is a link toward the list of 
"Approved Projects". This list is independent of any release. Next week during 
Santa Clara F2F, as new project proposal will be approved, I will update the 
"Approved Projects".

Also, under the top "Release Planning and Management" section, there are 2 
links:

1)  "Project Status in Amsterdam Release", that provides the list of 
projects part of Amsterdam as well as their status at each milestones.

2)  "Project Status in Beijing Release", that provides the list of projects 
part of Beijing. Currently, for these project I have provided a link toward 
their Intention to participate into Beijing.

Hope this helps and brings clarity. Let me know if you have any question, I 
will be glad to help.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Wednesday, December 06, 2017 1:57 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-tsc@lists.onap.org P 
<onap-tsc@lists.onap.org>
Subject: RE: Project part of Wiki

Hi Gildas,

Keep in mind that the in the charter we "approve" projects, not "approve 
projects" for a release.  Once a project is approved, then it can indicate its 
desire to be part of a release.  Hence, "approved projects for Beijing release" 
can create confusion and should be avoided.

BR,

Steve

From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: 06 December 2017 19:34
To: Stephen Terrill 
<stephen.terr...@ericsson.com<mailto:stephen.terr...@ericsson.com>>; 
onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> P 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: RE: Project part of Wiki

Hi,

Thanks for bringing this up. Definitely, as we keep moving by adding new 
Projects and new Releases, we will need to get organized in presenting this 
properly.
See my comments inline.


Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org<mailto:onap-tsc-boun...@lists.onap.org> 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Stephen Terrill
Sent: Wednesday, December 06, 2017 2:56 AM
To: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org> P 
<onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>>
Subject: [onap-tsc] Project part of Wiki

Hi,

There is one topic that I wanted to raise for discussion.
In the ONAP Wiki, where we have the ONAP projects; we have three parts sections:
-  "Projects for Beijing Release" [Gildas] available 
here<https://wiki.onap.org/display/DW/Projects+for+Beijing+Release>. This list 
summarizes the projects that had a project proposal approved for Amsterdam 
Release and wish to participate into Beijing Release.
-  "Approved projects for Amsterdm Release". [Gildas] available 
here<https://wiki.onap.org/display/DW/Approved+Projects+for+Amsterdam+Release>. 
This list all projects that have been approved to be a part of the ONAP 
Platform. This list was created as the project proposal were approved back in 
June during Beijing F2F.
-  "deffered/depreicated" etc. [Gildas] These lists are currently empty 
and are placeholder for historic purposes. We should in the wiki the history of 
projects and which release(s) they have contributed into.

However, we have two lifecycles in ONAP.  The projects have a lifecyle; and 
then we have the release lifecycle.   This means that:
-  We have approved projects irrespective of a release.
-  Of these, projects that will contribute into the release.

For this purpose, I consider at appropropriate that we have in the same list an 
item of
"Approved projects" - Which is really the "Aproved projects for Amsterdam 
Release".  This is where we have all of the approved projects, irrespective of 
the release.
Then we can have a list of the projects in each release.  This is where we have 
the projects that will contribute to that particular release.

Thoughts? [Gildas] As we will review the 10 New Project 
Proposal<https://wiki.onap.org/display/DW/Proposed+Projects> during next week 
F2F, I will create a page "Approved projects for Beijing Release". That will 
define the project scope for Beijing.
Independently of their release contribution, we can create a list of all 
approved projects.

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

Re: [onap-tsc] Project part of Wiki

[Gildas Lanilis]

Hi,

Thanks for bringing this up. Definitely, as we keep moving by adding new 
Projects and new Releases, we will need to get organized in presenting this 
properly.
See my comments inline.


Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Wednesday, December 06, 2017 2:56 AM
To: onap-tsc@lists.onap.org P 
Subject: [onap-tsc] Project part of Wiki

Hi,

There is one topic that I wanted to raise for discussion.
In the ONAP Wiki, where we have the ONAP projects; we have three parts sections:
-  "Projects for Beijing Release" [Gildas] available 
here. This list 
summarizes the projects that had a project proposal approved for Amsterdam 
Release and wish to participate into Beijing Release.
-  "Approved projects for Amsterdm Release". [Gildas] available 
here. 
This list all projects that have been approved to be a part of the ONAP 
Platform. This list was created as the project proposal were approved back in 
June during Beijing F2F.
-  "deffered/depreicated" etc. [Gildas] These lists are currently empty 
and are placeholder for historic purposes. We should in the wiki the history of 
projects and which release(s) they have contributed into.

However, we have two lifecycles in ONAP.  The projects have a lifecyle; and 
then we have the release lifecycle.   This means that:
-  We have approved projects irrespective of a release.
-  Of these, projects that will contribute into the release.

For this purpose, I consider at appropropriate that we have in the same list an 
item of
"Approved projects" - Which is really the "Aproved projects for Amsterdam 
Release".  This is where we have all of the approved projects, irrespective of 
the release.
Then we can have a list of the projects in each release.  This is where we have 
the projects that will contribute to that particular release.

Thoughts? [Gildas] As we will review the 10 New Project 
Proposal during next week 
F2F, I will create a page "Approved projects for Beijing Release". That will 
define the project scope for Beijing.
Independently of their release contribution, we can create a list of all 
approved projects.

BR,

Steve



[Ericsson]
STEPHEN TERRILL
Technology Specialist
DUIC, Systems and Technology
Development Unit IP & Cloud
Business Unit, IT & Cloud Products

Ericsson
Ericsson R Center, via de los Poblados 13
28033, Madrid, Spain
Phone +34 339 3005
Mobile +34 609 168 515
stephen.terr...@ericsson.com
www.ericsson.com


[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

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

Re: [onap-tsc] ONAP-vAccess Project Proposal - Open Source Access Manager for Wireline Access

[Gildas Lanilis]

Hi Mounire,

Thanks for your submission.
For the community to access your materials and provide feedback, it is expected 
you fill out and post in the wiki the Project Proposal template.
The project Proposal template is available at 
https://wiki.onap.org/display/DW/Project+Proposal+Template
The place to post your submission 
https://wiki.onap.org/display/DW/Proposed+Projects
Let me know if you have any question, I will be glad to help.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of EL HOUMAIDI, MOUNIRE
Sent: Wednesday, November 29, 2017 5:50 AM
To: onap-tsc@lists.onap.org
Cc: MCDONNELL, BLAINE ; EL HOUMAIDI, MOUNIRE 
Subject: [onap-tsc] ONAP-vAccess Project Proposal - Open Source Access Manager 
for Wireline Access

Dear Team,

ONAP-vAccess Project Proposal for the Beijing release.

Regards,
Mounire El Houmaidi
Director Member Technical Staff
Technology Design & Arch.
Advanced Fixed Access Systems
e-mail:  me4...@att.com
Mobile:  404-394-2815

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

[onap-tsc] Update on TSC action Item

[Gildas Lanilis]

Hi All,

I wanted to follow up on my TSC action item related to Defect Definitions and 
thus updated the Jira defects definition in 
wiki<https://wiki.onap.org/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-JIRADefectDefinition>
 for your review. This should help to classify the defects on the attention 
they need for resolution.
Let me know if you have any questions.

The RC0 status is available in 
wiki<https://wiki.onap.org/display/DW/RCO+Status> and I will update as I learn 
from the teams.

For your convenience, I have posted the updated version of the Beijing Release 
Planning 
Proposal<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-BeigingRelease>
 that I shared with you while in Paris.

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

Thanks,
Gildas

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

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

Re: [onap-tsc] [onap-release] Problem with people creating JIRA's for unnecessary fixes

[Gildas Lanilis]

Hi Pam,

Thanks for bringing this up.

I would tend to believe there is a good intention in fixing those type of 
defects but it is definitely not the right timing. Like me, you have certainly 
seen some behaviors where people sometimes don’t realize they have to focus on 
what is important today to make the Release reality.

My suggestion to you. As you are the PTL, you are in the driver seat for your 
project and thus as a community we trust your judgment. More specifically, I 
would recommend to “Abandon” such commit and use the Jira field “fixversion” 
and assign this to “Beijing Release” . It may be good to tag them as 
“scan-report” (or whatever tag that makes sense to you and the team), so later 
when this is the right time you can come back on this defect.

Hope this helps.
My 2 cents.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Thursday, October 12, 2017 6:07 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-rele...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: [onap-tsc] [onap-release] Problem with people creating JIRA's for 
unnecessary fixes

Gildas and TSC,

Please help me. I have people that are going outside my scrum and creating 
“BUGS” for sonar major/minor fixes. None of these are critical or identified 
during integration testing. It is past code freeze and RC0 and these are 
disruptive to the process for releasing code.

I have asked them to stop over the past 2 weeks but today I have 3 new JIRA’s 
to deal with. We are trying to get our artifacts released to meet RC0 
guidelines. At this point I don’t know what to do except to bring in the 
involvement of the TSC to get this behavior stopped.

While I appreciate the help, it would have been better for this work to be done 
months ago and not post code freeze. I’m also not sure what brought on this 
sudden interest in fixing sonar major/minor issues throughout policy project. 
None of these people have spoken to myself about working on policy, much less 
added themselves as contributors to the project.

What guidance is there for this?

Thanks,

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

[onap-tsc] M4 Progress

[Gildas Lanilis]

Hi All,

This is regarding the action items 
2,f<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-10-05-13.52.html>
 on  Thursday, Oct 5 2017 TSC weekly meeting.

I have been able to upload in wiki the excel sheet that I used to monitor M4 
progress at https://wiki.onap.org/display/DW/M4+Status . It provides all the 
details on what is left to do for the teams.  Looks like I am the only one who 
can edit the file.
I also maintain the overall master Amsterdam  Release Status at 
https://wiki.onap.org/display/DW/Release+Status

Since the TSC meeting, CCSDK (Gating project) has reached the 30% code coverage 
on ccsdk-sli-northbound repo and thus made the M4 criteria.
AAF (Non-gating project) also reported the fact the team had reached to 30% 
code coverage. However, AAF did not meet the Oct 2 timeline and thus won't be 
part of Amsterdam release (refer to attached information)

Thanks,
Gildas

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

--- Begin Message ---
Dear PTLs,

On behalf of the TSC, I wanted to thank you for your leadership and drive to 
get us to the Amsterdam release on Nov 16th. You and your teams are incredible 
role models of how a community is harmonizing towards a common goal.

As we discussed at the Paris meeting, we have to make some hard decisions to 
get to the Amsterdam release on November 16th. The TSC, with feedback from 
Gildas and Helen, have decided on the following

All projects should at least pass the M4 milestone and a min of 30% unit 
coverage by next Monday EOB (PST)

Non-gating projects that do not meet this timeline will be removed from the 
formal release.
Gating projects will need to provide a date of when they expect to reach this 
milestone.

Gildas will collect all info and share with the community Monday night (PST)

thanks!
Mazin
--- End Message ---
___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

Re: [onap-tsc] Monday EOB (CA) deadline

[Gildas Lanilis]

Hi PTLs,

As agreed last week at Paris, find below the latest status on the M4 review.
The attached excel sheet provides the details on the findings. Since last 
Thursday, a lot of work has been accomplished. Congrats all, I am very happy by 
the progress.
On the attached sheet, the green cells in the column G to J represent the work 
accomplished since Thursday, the red cells mainly represent the current code 
coverage that is requiring improvement..

Most teams have reported a completion date for the remaining items on no later 
than Oct 12 for RC0. Some teams plan to deliver earlier. Only VFC and SDC have 
not yet provided an ETA.

To summarize:

1.On a total of 28 projects, 18 projects passed M4. 9 are MVP (appc, 
integration, modeling, msb, multicloud, policy, portal, sdnc, dcae), 9 are 
No-MVP projects (clamp, cli, doc, externalapi, holmes, oom, usecase ui, 
vnfrqts, vnfsdk).

2.7 MVP projects (aai, ccsdk, dmaap, sdc, so, vfc, vid) have some work 
to do to reach 30% code coverage.

3.2 no-MVP projects (aaf, vvp) did not meet the criteria to stay in the 
Amsterdam release. Both of these projects need to work on code coverage.

4.1 no-MVP project (Logging Enhancement) which is not providing code 
but documentation is on the edge of completing the ReadTheDocs tasks by Oct 3 
(documentation is currently available in 
wiki<https://wiki.onap.org/display/DW/Logging+User+Guide>).

Until we reach Release Sign-Off on Nov 16, we need to keep our focus on fixing 
bugs that have priority highest and high. I recommend Committers to pay 
attention to the criticality of defects and to "-2" those who are not relevant 
to support the Amsterdam use cases.


Thanks,
Gildas

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

From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com]
Sent: Saturday, September 30, 2017 8:33 AM
To: wangchen...@chinamobile.com; TIMONEY, DAN <dt5...@att.com>; Yunxia Chen 
<helen.c...@huawei.com>; zhao.huab...@zte.com.cn; denglin...@chinamobile.com; 
DRAGOSH, PAMELA L (PAM) <pdrag...@research.att.com>; denghu...@hotmail.com; 
TALASILA, MANOOP (MANOOP) <talas...@research.att.com>; KOYA, RAMPRASAD 
<rk5...@att.com>; Seshu m <seshu.kuma...@huawei.com>; MAYER, ANDREW J 
<am8...@att.com>; GILBERT, MAZIN E (MAZIN E) <ma...@research.att.com>; 
lxin...@vmware.com; FORSYTH, JAMES <jf2...@att.com>; 
stephen.terr...@ericsson.com; LANDO, MICHAEL <ml6...@intl.att.com>; POND, MARK 
<mp...@amdocs.com>; PUTHENPURA, SARAT (SARAT) <sa...@research.att.com>; JI, 
LUSHENG (LUSHENG) <l...@research.att.com>; GLOVER, GREG L <gg2...@att.com>; 
Kanagaraj Manickam <kanagaraj.manic...@huawei.com>; NGUEKO, GERVAIS-MARTIAL 
<gn4...@intl.att.com>; fu.guangr...@zte.com.cn; onap-tsc@lists.onap.org; 
denghui (L) <denghu...@huawei.com>; david.sauvag...@bell.ca; WRIGHT, STEVEN A 
<sw3...@att.com>; MAHER, RANDA <rx1...@att.com>; shen...@chinamobile.com; 
HEMLI, AMICHAI <ah0...@intl.att.com>; Gildas Lanilis 
<gildas.lani...@huawei.com>; SUNDELOF, ERIK <es4...@att.com>; 
kp...@linuxfoundation.org; onap-tsc-priv...@lists.onap.org; 
pr...@linuxfoundation.org; cc...@linuxfoundation.org
Subject: Monday EOB (CA) deadline

Dear PTLs,

On behalf of the TSC, I wanted to thank you for your leadership and drive to 
get us to the Amsterdam release on Nov 16th. You and your teams are incredible 
role models of how a community is harmonizing towards a common goal.

As we discussed at the Paris meeting, we have to make some hard decisions to 
get to the Amsterdam release on November 16th. The TSC, with feedback from 
Gildas and Helen, have decided on the following

All projects should at least pass the M4 milestone and a min of 30% unit 
coverage by next Monday EOB (PST)

Non-gating projects that do not meet this timeline will be removed from the 
formal release.
Gating projects will need to provide a date of when they expect to reach this 
milestone.

Gildas will collect all info and share with the community Monday night (PST)

thanks!
Mazin


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

Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

[Gildas Lanilis]

Hi,

Thanks David for sharing your analysis +1. Big chunk of code should not happen 
(whatever big mean). That is why when TSC reviewed and approved the 
“Development Best 
Practices”
 earlier in July, I had the motto “If there is 1 word to remember "Commit, 
commit, commit" multiple times a day”. During that meeting someone brought the 
issue of submitting code that is not completely done, and the practice of 
submitting “Gerrit Draft 
Features”
 was introduced. This “Gerrit Draft Features” practice provides a way for the 
community to see “code in progress”, to provide early feedback and not commit 
yet in Master (until the feature is really complete).
The unfortunate David’s description of “we’ll build it internally and then 
upstream the code” demonstrates a lack transparency, working in a silo mode, 
that a trustfulness open source community must avoid.

I agree with Oliver and Lushen that the singularity we are currently 
experiencing is about bringing in seed code, onetime event. In case of multiple 
occurrences of such behavior in a single repo, as a community we should  simply 
-2 the code while doing code reviews.

Thanks to Steve, who pointed out the CI guidance we have in place in wiki. At 
the end of the day, in Open Source what matter is working code. And CI 
disciplines helps.

Not sure we should spend energy in tooling to control or limit such behavior. I 
think we have bigger fish to catch now. I would be in favor of educating people 
and making them realize everything they do is PUBLIC (thinking about their 
online resume). That should help the community to self-regulate. Also, read the 
lines story I bring each time we meet on the coder who commit code at 5:30 pm 
on a Friday (fourth 
bullet))

Some good reading in CI by Jez Humble and David 
Fairley
 (but that requires much more time)

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
Sent: Friday, August 04, 2017 3:01 AM
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

Thanks for sharing your perspective Lusheng, I think its important to get the 
perspectives of the projects into these discussions.  BR, Steve.

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of JI, LUSHENG (LUSHENG)
Sent: 04 August 2017 07:43
To: onap-tsc@lists.onap.org
Subject: Re: [onap-tsc] Enforcing an "Upstream first" approach to ONAP

Dear TSC and ONAP community,

As I am reading through this thread, I can certainly appreciate David’s good 
intention behind the suggestion.  Perhaps this is a minority opinion here, but 
as a PTL and committer I have to say I am also concerned about “enforcing” 
things such as hard limit on submission LOC.


  1.  Contributions come in the shapes that they are in.  Some large some 
small.  Putting a submission size limit will not change that, but it would 
impact the integrity of large contributions though.  Say someone wants to 
contribute a new complex function but LOC too large, it is not like he would be 
able to break this one large contribution into several smaller contributions.  
The more likely outcome is that he will simply break the contribution into 
several smaller commits, each smaller than the LOC limit but only fragment of 
the original contribution file tree.  This would make committer’s job much 
harder because he now must review ALL of these commits together, equal amount 
of LOC, and spread in multiple submissions.  Individual commits like these 
cannot be reviewed individually effectively because it is difficult to assess 
its value to the whole project, without mentioning that individual submission 
may even break the CICD and testing of the project.
  2.  The “commit small commit often” practice of devops really relies on the 
rich support of features and branches of git.  We essentially have ONLY ONE 
branch, the master.  This is the key reason for why I am not sure we should 
follow the devops manual to a tee here.  None of those sophisticated branching 
workflows is applicable here.  ONAP gerrit is not best suited for being used as 
dev repo.  With this limitation, I would much prefer to have the head of master 
branch relatively clean and stable, only advanced by good quality, tested, and 
self-contained contributions, not by work-in-progress fragments.
  3.  Large submission does not necessarily equal to behind-door development.  
Gitlab is 

Re: [onap-tsc] M2 Amsterdam Functionality Freeze is coming

[Gildas Lanilis]

Dear PTLs,

As a kindly reminder, it is expected you fill out in the project space with the 
M2 Functionality Freeze Checklist.
We will review the artifacts during TSC meeting on Thursday, August 3.

Let me know if you have any questions.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Monday, July 31, 2017 8:43 AM
To: 'onap-rele...@lists.onap.org' <onap-rele...@lists.onap.org>
Cc: 'onap-tsc@lists.onap.org' <onap-tsc@lists.onap.org>
Subject: RE: M2 Amsterdam Functionality Freeze is coming

Hi,

FYI, I add an item related to project blocker there were identified last week 
during V F2F.
The question is "If applicable to your project, has your team been able to 
clear the project' 
blockers<https://wiki.onap.org/display/DW/July+Virtual+Developers+Event+Blockers>?
 If not provide status on the plan to close the blocker(s).

For the PTL who already made a copy of the template, I updated directly your 
project checklist.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Thursday, July 27, 2017 8:04 AM
To: 'onap-rele...@lists.onap.org' 
<onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>
Cc: onap-tsc@lists.onap.org<mailto:onap-tsc@lists.onap.org>
Subject: M2 Amsterdam Functionality Freeze is coming

Dear PTLs,

Thank you very much for those of you who could make it at the Virtual F2F 
meeting where I presented on Release Status, Process and Scum Board.
For those who could make it, don't worry, the presentation 
<https://wiki.onap.org/download/attachments/8231717/ONAP%20Release%20Status%20Process%20and%20Scrum%20Board.pdf?version=1=1501009344000=v2>
 and the recording 
<https://wiki.onap.org/display/DW/July+24-26+Virtual+Developers+Event?preview=/8231717/10782076/JulyVF2F-Day1-20170724.mp4>
 are available in wiki.

To provide visibility on the development activities within the community, it is 
expected that every team use the Scrum Board and do create and start 
Sprints<https://wiki.onap.org/display/DW/Create+a+Sprint>.
>From a Release Management perspective, I look at this Master Release 
>management page<https://wiki.onap.org/display/DW/Amsterdam+Release+Status> 
>which provides visibility, transparency and a sense of achievements. Each 
>child page provides a more granular view on each project. I see a large number 
>of teams have created their Scrum Board, thanks to them, it helps a lot.

Also, next Thursday (1 week from now) according to the Amsterdam Release 
Planning<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-ONAPRelease1ReleasePlanningDraftProposal>,
 August 3 is the Amsterdam M2 Functionality 
Freeze<https://wiki.onap.org/display/DW/Release+Lifecycle#ReleaseLifecycle-ReleaseFunctionalityFreeze>.
It is expected that each PTL works with each team and fill out a copy of the M2 
Functionality 
Checklist<https://wiki.onap.org/display/DW/Deliverables+for+Functionality+Freeze+Milestone+Checklist+Template>
 in their project workspace.

As you progress in this exercise, I will review the M2 artifacts and provide a 
summary to the community during TSC Meeting on August the 3. I am confident you 
and your team will pass. If you have any questions or concerns please reach 
out, I will be glad to help out.

Thanks,
Gildas

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

___
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

[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 <gildas.lani...@huawei.com>
Cc: onap-tsc@lists.onap.org; Sauvageau, David <david.sauvag...@bell.ca>
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<mailto:kp...@linuxfoundation.org>
510.766.5945

On Jul 31, 2017, at 6:42 AM, Sauvageau, David 
<david.sauvag...@bell.ca<mailto:david.sauvag...@bell.ca>> 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 
<david.sauvag...@bell.ca<mailto:david.sauvag...@bell.ca>> wrote:

Hi Kenny
Can we please create that repo?
Thanks

Envoyé de mon iPhone

Début du message transféré :
Expéditeur: <zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>>
Date: 26 juillet 2017 à 09:16:15 UTC−4
Destinataire: <david.sauvag...@bell.ca<mailto:david.sauvag...@bell.ca>>
Cc: <jn1...@att.com<mailto:jn1...@att.com>>, 
<jflu...@research.att.com<mailto:jflu...@research.att.com>>, 
<jh2...@att.com<mailto:jh2...@att.com>>, 
<rb2...@att.com<mailto:rb2...@att.com>>, 
<ht1...@att.com<mailto:ht1...@att.com>>, 
<roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>>, 
<j...@research.att.com<mailto:j...@research.att.com>>, 
<meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>>, 
<c...@research.att.com<mailto:c...@research.att.com>>, 
<ag1...@att.com<mailto:ag1...@att.com>>, 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>
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:  <david.sauvag...@bell.ca<mailto:david.sauvag...@bell.ca>>;
To:  <jn1...@att.com<mailto:jn1...@att.com>>;
CC: zhaohuabing10201488; 
<jflu...@research.att.com<mailto:jflu...@research.att.com>>; 
<jh2...@att.com<mailto:jh2...@att.com>>; 
<rb2...@att.com<mailto:rb2...@att.com>>; 
<ht1...@att.com<mailto:ht1...@att.com>>; 
<roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>>; 
<j...@research.att.com<mailto:j...@research.att.com>>;MengZhaoXing10024238; 
<c...@research.att.com<mailto:c...@research.att.com>>; 
<ag1...@att.com<mailto:ag1...@att.com>>; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>;
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 <jn1...@att.com<mailto:jn1...@att.com>> 
wrote:

Huabing,

Re: [onap-tsc] M2 Amsterdam Functionality Freeze is coming

[Gildas Lanilis]

Hi,

FYI, I add an item related to project blocker there were identified last week 
during V F2F.
The question is "If applicable to your project, has your team been able to 
clear the project' 
blockers<https://wiki.onap.org/display/DW/July+Virtual+Developers+Event+Blockers>?
 If not provide status on the plan to close the blocker(s).

For the PTL who already made a copy of the template, I updated directly your 
project checklist.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Thursday, July 27, 2017 8:04 AM
To: 'onap-rele...@lists.onap.org' <onap-rele...@lists.onap.org>
Cc: onap-tsc@lists.onap.org
Subject: M2 Amsterdam Functionality Freeze is coming

Dear PTLs,

Thank you very much for those of you who could make it at the Virtual F2F 
meeting where I presented on Release Status, Process and Scum Board.
For those who could make it, don't worry, the presentation 
<https://wiki.onap.org/download/attachments/8231717/ONAP%20Release%20Status%20Process%20and%20Scrum%20Board.pdf?version=1=1501009344000=v2>
 and the recording 
<https://wiki.onap.org/display/DW/July+24-26+Virtual+Developers+Event?preview=/8231717/10782076/JulyVF2F-Day1-20170724.mp4>
 are available in wiki.

To provide visibility on the development activities within the community, it is 
expected that every team use the Scrum Board and do create and start 
Sprints<https://wiki.onap.org/display/DW/Create+a+Sprint>.
>From a Release Management perspective, I look at this Master Release 
>management page<https://wiki.onap.org/display/DW/Amsterdam+Release+Status> 
>which provides visibility, transparency and a sense of achievements. Each 
>child page provides a more granular view on each project. I see a large number 
>of teams have created their Scrum Board, thanks to them, it helps a lot.

Also, next Thursday (1 week from now) according to the Amsterdam Release 
Planning<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-ONAPRelease1ReleasePlanningDraftProposal>,
 August 3 is the Amsterdam M2 Functionality 
Freeze<https://wiki.onap.org/display/DW/Release+Lifecycle#ReleaseLifecycle-ReleaseFunctionalityFreeze>.
It is expected that each PTL works with each team and fill out a copy of the M2 
Functionality 
Checklist<https://wiki.onap.org/display/DW/Deliverables+for+Functionality+Freeze+Milestone+Checklist+Template>
 in their project workspace.

As you progress in this exercise, I will review the M2 artifacts and provide a 
summary to the community during TSC Meeting on August the 3. I am confident you 
and your team will pass. If you have any questions or concerns please reach 
out, I will be glad to help out.

Thanks,
Gildas

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

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

[onap-tsc] M2 Amsterdam Functionality Freeze is coming

[Gildas Lanilis]

Dear PTLs,

Thank you very much for those of you who could make it at the Virtual F2F 
meeting where I presented on Release Status, Process and Scum Board.
For those who could make it, don't worry, the presentation 
<https://wiki.onap.org/download/attachments/8231717/ONAP%20Release%20Status%20Process%20and%20Scrum%20Board.pdf?version=1=1501009344000=v2>
 and the recording 
<https://wiki.onap.org/display/DW/July+24-26+Virtual+Developers+Event?preview=/8231717/10782076/JulyVF2F-Day1-20170724.mp4>
 are available in wiki.

To provide visibility on the development activities within the community, it is 
expected that every team use the Scrum Board and do create and start 
Sprints<https://wiki.onap.org/display/DW/Create+a+Sprint>.
>From a Release Management perspective, I look at this Master Release 
>management page<https://wiki.onap.org/display/DW/Amsterdam+Release+Status> 
>which provides visibility, transparency and a sense of achievements. Each 
>child page provides a more granular view on each project. I see a large number 
>of teams have created their Scrum Board, thanks to them, it helps a lot.

Also, next Thursday (1 week from now) according to the Amsterdam Release 
Planning<https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-ONAPRelease1ReleasePlanningDraftProposal>,
 August 3 is the Amsterdam M2 Functionality 
Freeze<https://wiki.onap.org/display/DW/Release+Lifecycle#ReleaseLifecycle-ReleaseFunctionalityFreeze>.
It is expected that each PTL works with each team and fill out a copy of the M2 
Functionality 
Checklist<https://wiki.onap.org/display/DW/Deliverables+for+Functionality+Freeze+Milestone+Checklist+Template>
 in their project workspace.

As you progress in this exercise, I will review the M2 artifacts and provide a 
summary to the community during TSC Meeting on August the 3. I am confident you 
and your team will pass. If you have any questions or concerns please reach 
out, I will be glad to help out.

Thanks,
Gildas

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

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

Re: [onap-tsc] [ptls] proposed topic for the next week's PTL meeting

[Gildas Lanilis]

Hi,

As the TSC were reviewing every project for the M1 Release Planning, I created 
a dependency graph based on the data provided (API Incoming dependencies).
This Graphiz graph is currently available in wiki at 
https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-APIDependencies
 .
My plan is to upload in Gerrit the source code that helped creating the graph.

Hope this helps.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Kanagaraj Manickam
Sent: Friday, July 07, 2017 6:00 AM
To: 赵化冰; onap-tsc@lists.onap.org; Phil Robb; Kenny Paul; 
wangchen...@chinamobile.com; dtimo...@att.com; Yunxia Chen; 
zhao.huab...@zte.com.cn; denglin...@chinamobile.com; pdrag...@research.att.com; 
denghu...@hotmail.com; talas...@research.att.com; Ram Koya; Seshu m; 
am8...@att.com; Casey Cain; lxin...@vmware.com; jf2...@att.com; 
stephen.terr...@ericsson.com; ml6...@intl.att.com; mp...@amdocs.com; 
sa...@research.att.com; l...@research.att.com; gg2...@att.com; 
gn4...@intl.att.com; fu.guangr...@zte.com.cn; denghui (L); 
david.sauvag...@bell.ca; sw3...@att.com; rx1...@att.com; 
shen...@chinamobile.com; ah0...@intl.att.com; Gildas Lanilis; es4...@att.com
Cc: Eman Gil
Subject: RE: [onap-tsc][ptls] proposed topic for the next week's PTL meeting

One more topic:
As part of M1 review, every project has listed the dependencies and I feel it 
will be very helpful if we could bring them together into one wiki and and draw 
a dependency graph and get it reviewed/accepted by all of us.
Shall we have this topic as part of PTL meeting on Monday (10th) ?

Thanks
Kanagaraj M


***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
This e-mail 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 herein 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 e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

From: 赵化冰 [mailto:zhaohuab...@gmail.com]
Sent: Friday, July 07, 2017 12:32 PM
To: onap-tsc@lists.onap.org; Phil Robb; Kenny Paul; 
wangchen...@chinamobile.com; dtimo...@att.com; Yunxia Chen; 
zhao.huab...@zte.com.cn; denglin...@chinamobile.com; pdrag...@research.att.com; 
denghu...@hotmail.com; talas...@research.att.com; Ram Koya; Seshu m; 
am8...@att.com; Casey Cain; lxin...@vmware.com; jf2...@att.com; 
stephen.terr...@ericsson.com; ml6...@intl.att.com; mp...@amdocs.com; 
sa...@research.att.com; l...@research.att.com; gg2...@att.com; Kanagaraj 
Manickam; gn4...@intl.att.com; fu.guangr...@zte.com.cn; denghui (L); 
david.sauvag...@bell.ca; sw3...@att.com; rx1...@att.com; 
shen...@chinamobile.com; ah0...@intl.att.com; Gildas Lanilis; es4...@att.com
Cc: Eman Gil
Subject: [onap-tsc][ptls] proposed topic for the next week's PTL meeting

Dear PTLs,

Maybe we could discuss this topic at the next week's PTL meeting. It's 
important and covers almost all the projects which will produce APIs.

https://wiki.onap.org/display/DW/RESTful+API+Design+Specification+for+ONAP

Thanks,
Huabing
-- Forwarded message -
Cc: <onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>


Hi  Pam,

After taking a look at the other best practices on this page. I realized that 
this is more like a specification than best practices because we'd like to 
enforce them to all the ONAP components. I moved this page to 
https://wiki.onap.org/display/DW/RESTful+API+Design+Specification+for+ONAP



Agree that some of the projects may not redesign the existing API for 
back-compatible reason, We can maintain the old version while designing the new 
version in parallel. It's possible that both the old and new version can be 
provided to the ONAP clients.



Thanks,

Huabing
Original Mail
Sender:  <pdrag...@research.att.com<mailto:pdrag...@research.att.com>>;
To: zhaohuabing10201488; 
<onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>>;
Date: 2017/06/22 20:09
Subject: Re: [onap-discuss] RESTful API Design Best Practices for 
ONAPMicroservices


Huabing,

Thanks, I agree and feel this is very valuable. There is no formal best 
practices for RESTful API, albeit a few websites that do a fairly good job at 
making suggestions.

I think this detailed information should probably be in the section located 
here:

https://wiki.onap.org/display/DW/Developer+Best+Practices

Gildas has

[onap-tsc] YOUR ACTION IS REQUIRED: A Project needs new repos for microservices

[Gildas Lanilis]

Dear TSC Voting Members,

AAI team needs the 3 following repos to be added in Gerrit. The PTL (Jimmy 
Forsyth) has provided the rational down below.
At this point the request and all associated artifacts are properly  documented 
in 
wiki<https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-ActiveandAvailableInventory>
 and are summarized in the screenshot below.
[cid:image002.jpg@01D2F66C.49734E40]

To expedite the approval, your approval by replying a +1, 0, -1 by email will 
be deemed sufficient by LF to move forward in repos creation.
The AA team thank you in advance for your prompt response.

Best Regards,
Gildas Lanilis
ONAP Release Manager
1 415 238 6287

From: FORSYTH, JAMES [mailto:jf2...@att.com]
Sent: Thursday, July 06, 2017 7:06 AM
To: Gildas Lanilis
Subject: FW: [onap-tsc] A Project needs new repos for microservices

Hi, Gildas,

I have made the update to the Resources and Repositories 
Page.<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DActiveandAvailableInventory=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=Oej6QUk5p2KdqNEWySpOHA=N0nd4_E6pXRddwrKlctvqfy2p7bRUuVh6P7FHpHYRAw=dqPvJ8JIEgW8zblQnYuXulM6smJETtxvHtDUuiYS7V0=>

Can you help with A’s request to get new repos added?

Thank you!

-jimmy

From: Kenny Paul [mailto:kp...@linuxfoundation.org]
Sent: Thursday, July 06, 2017 7:48 AM
To: FORSYTH, JAMES <jf2...@att.com>
Cc: onap-tsc@lists.onap.org; PAQUETTE, FRANCIS <francis.paque...@amdocs.com>; 
WEATHERLY, STEPHEN <sweat...@amdocs.com>; BYLSMA, SUSAN 
<susan.byl...@amdocs.com>; DENING, EDWARD <ed.den...@amdocs.com>; BLIMKIE, 
STEVEN <steven.blim...@amdocs.com>; AGGARWAL, MANISHA <amani...@att.com>; 
Gildas Lanilis <gildas.lani...@huawei.com>
Subject: Re: [onap-tsc] A Project needs new repos for microservices

Hi James,
Please ensure that all of the necessary information for these have been 
provided on the Resources and Repositories 
Page.<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Resources-2Band-2BRepositories-23ResourcesandRepositories-2DActiveandAvailableInventory=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=Oej6QUk5p2KdqNEWySpOHA=N0nd4_E6pXRddwrKlctvqfy2p7bRUuVh6P7FHpHYRAw=dqPvJ8JIEgW8zblQnYuXulM6smJETtxvHtDUuiYS7V0=>
At first glance it appears that babel is missing.

Once that information is complete, please let Gildas know and he will help 
shepherd this request.

Best Regards,
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>
510.766.5945

On Jul 5, 2017, at 9:27 AM, FORSYTH, JAMES 
<jf2...@att.com<mailto:jf2...@att.com>> wrote:

Dear ONAP TSC Members,

The A team would like to request permission to add 3 new repositories for 2 
new microservices and a new graph database abstraction library for the 
Amsterdam release.

The repos will be called:

aai/champ
aai/gizmo
aai/babel

A’s rationale for creating these separate repos as opposed to using a 
subdirectory under an existing repo is as follows: it is the convention to 
create a separate git repository for each microservice and library as is 
demonstrated by the microservices currently part of the AAI project. The 
advantages of separate repos (as opposed a single repo containing multiple 
microservices) is the ability to manage access rights for each microservice. 
Otherwise a user with write permissions to the “common” microservice repo could 
accidentally (or intentionally) make change to another microservice.

Please let me know if further clarification is needed.

Thank you for your attention,
Jimmy Forsyth
A PTL


___
ONAP-TSC mailing list
ONAP-TSC@lists.onap.org<mailto:ONAP-TSC@lists.onap.org>
https://lists.onap.org/mailman/listinfo/onap-tsc<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=Oej6QUk5p2KdqNEWySpOHA=N0nd4_E6pXRddwrKlctvqfy2p7bRUuVh6P7FHpHYRAw=nrf_db78BJ5q9lzkRyPA5FpPsbbhwcDONwdjE4yoU18=>

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

[onap-tsc] ONAP Amsterdam M1 Release Planning Reviews second review

[Gildas Lanilis]

Dear TSC Voting Members, Recently appointed PTLs and Primary Project Contacts,

This email is regarding the ONAP M1 Release Planning Review (second round).
As we discussed at TSC meeting, we are conducting the second review for M1 
Release Planning on Friday July 7.
For the recently approved projects or those who can't make it on Friday, we 
will organize separate reviews (most probable during TSC weekly meeting).

More specifically for the review on Friday, July 7 the agenda is posted in 
wiki<https://wiki.onap.org/display/DW/Amsterdam+Release+Planning%3A+M1+Project+Review#AmsterdamReleasePlanning:M1ProjectReview-ReviewFriday,July7>.
 The PTL attendance is required as well as TSC Voting Members. In case you 
can't attend please designate a substitute.

As we have very limited time, I will run the review by displaying the Release 
Artifacts and focusing our attention on the following criteria:

1.   Scope of the functionalities committed for Amsterdam Release

2.   Project dependencies within ONAP (API)

3.   Timeline

4.   Resources
I will give opportunity for questions to PTLs to answer and request TSC their 
disposition (pass, conditional, no pass).

Once we are done with the M1 review of the 12 projects, we will review the 
action items from last week M1 review and finalize the Project Proposal review 
for Network Function Change 
Management<https://wiki.onap.org/pages/viewpage.action?pageId=4719331>
Zoom information to join the conference are documented in 
wiki<https://wiki.onap.org/display/DW/TSC+Meeting+Resources>.

Let me know if you have any questions. Talk to you tomorrow.

Thanks,
Gildas

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

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

[onap-tsc] ONAP Amsterdam M1 Release Planning Reviews

[Gildas Lanilis]

Dear TSC Voting Members, Recently appointed PTLs and Primary Project Contacts,

This email is regarding the ONAP M1 Release Planning Review.
As we discussed at TSC meeting, we are going to conduct 2 main reviews on 
Friday, June 30 and Friday July 7 for the projects that have been approved 
before June 23.
For the recently approved projects or those who can't make it on Friday, we 
will organize separate reviews.

More specifically for the review on Friday, June 30 the agenda is posted in 
wiki<https://wiki.onap.org/display/DW/Amsterdam+Release+Planning%3A+M1+Project+Review>.
 The PTL attendance is required as well as TSC Voting Members. In case you 
can't attend please designate a substitute.

As we have very limited time, I will run the review by displaying the Release 
Artifacts and focusing our attention on the following criteria:

1.   Scope of the functionalities committed for Amsterdam Release

2.   Project dependencies within ONAP (API)

3.   Timeline

4.   Resources
I will give opportunity for questions to PTLs to answer and request TSC their 
disposition (pass, conditional, no pass).

Let me know if you have any questions. Talk to you tomorrow.

Thanks,
Gildas

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

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

Re: [onap-tsc] [onap-cli] M1 deliverable review

[Gildas Lanilis]

Hi Kanagaraj,

Thanks for the update. Let me review the artifacts, I will come back to you 
shortly if there is anything preventing to move forward.
A slot freed up for presenting M1 Release artifacts this Friday 30, so I 
propose we review CLI this Friday. As it will be late for you, I did my best to 
have CLI on the top of the list.
Let me know if you have any concerns.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Kanagaraj Manickam
Sent: Wednesday, June 28, 2017 5:09 AM
To: Gildas Lanilis
Cc: 'onap-tsc@lists.onap.org'
Subject: [onap-cli] M1 deliverable review

Dear Gildas,

I have updated the M1 release plan and check list for ONAP CLI project under 
https://wiki.onap.org/display/DW/Command+Line+Interface+Project
Kindly review it and let me know if any updates required.

Thank you.

Regards
Kanagaraj M

***
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**

***
This e-mail 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 herein 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 e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

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

Re: [onap-tsc] MSB Amsterdam Release Planning

[Gildas Lanilis]

Hi Huabing,

Thanks for volunteering for the MSB project review this Friday, June 30. I have 
updated the calendar accordingly.
I am reviewing the Release artifacts and will let you know shortly if there is 
anything preventing to move forward.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn]
Sent: Wednesday, June 28, 2017 8:17 AM
To: Gildas Lanilis
Cc: onap-tsc@lists.onap.org
Subject: MSB Amsterdam Release Planning

Hi Gildas,

I have updated MSB Amsterdam Release Planning in the wiki. Could you please 
review and let me know if anything missing or needed to be modified? I would 
appreciate it if MSB could get a time slot at this Friday's TSC review meeting.

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

Re: [onap-tsc] TSC Meetings

[Gildas Lanilis]

Hi,
The agreement we had at Beijing was to make it the week of September 24th.
The week of Sept 17 is Jewish New Year (Rosh  Hashana) and the week of Oct 1 is 
China National Holiday.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Sunday, June 25, 2017 7:10 AM
To: GILBERT, MAZIN E (MAZIN E); t...@lists.onap.org
Subject: Re: [onap-tsc] TSC Meetings

Hi Mazin,

Regarding TSC f2f meeting in September, 4th week of September was discussed, I 
believe (the week starting from September 25). The previous (3rd) week is 
Jewish New Year (Rosh haShana).

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2EE6E.2224B550]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of GILBERT, MAZIN E (MAZIN E)
Sent: Sunday, June 25, 2017 5:02 PM
To: t...@lists.onap.org
Subject: [onap-tsc] TSC Meetings

ONAP Community

Please mark your calendars for July 24 and 25 for the next TSC virtual meeting.
The goal of the meeting is to review progress with the Amsterdam release. We
will share more info on the agenda and working hours shortly. We realize it 
will be a challenge
to operate across all timezones.

We will also be having a F2F TSC meeting on the third week of September. We
hope to have it in Europe. We have a proposal in France but we are still open to
other proposals. The meeting will be focused on both update to the Amsterdam 
release
and planning for the Beijing Release.

Phil, I would appreciate creating a wiki for both of these meetings.

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

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

[Gildas Lanilis]

Thanks Andrei for putting the deck together. It helps to move forward.
It was my intention to build a similar table based on the dependencies 
input
 for each and every project.
I posted your table as a reference on wiki at 
https://wiki.onap.org/display/DW/Release+Planning#ReleasePlanning-ReleaseDependencies
 and started to build directly into the wiki the same table (so far with only 
approved projects). That should help into avoiding the question “what is the 
latest version?”.

A couple of questions:


1)  I was wondering how to read the dependency table. In other words who is 
the API provider and who is the API consumer? In the Release Planning 
Template,
 I called it “API Incoming Dependencies” (provider) and “API Outgoing 
Dependencies” (consumer). Your clarification would help (my guess is that the 
projects in the column have dependencies on the projects in the row). Thanks to 
confirm.

2)  Would you mind clarifying the blue boxes “Interact but no direct 
interface”? To some extend everything interact through a different level of 
connection in ONAP.

3)  For the red boxes “Likely but not mentioned”. Would you mind explaining 
where it is not mentioned?  May be we should wait until all projects have 
created their release plan.

4)  Not sure what are the “Change Man”, “Ext Sys Reg” projects. To my 
knowledge, none have not been approved so far, and I do not see them in the 
list of “proposed project”. 
May be it is just a wording issue. It would help if you could provide a link.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Andrei Kojukhov
Sent: Monday, June 19, 2017 6:17 AM
To: Alla Goldner; Phil Robb; Arul Nambi
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: Re: [onap-discuss] [onap-tsc] Tentative July ONAP Developers 
Face-to-Face Meeting

Alla, Phil,

Please take an updated slide (attached) – I sent you an email twice by mistake.

BR

Andrei

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Alla Goldner
Sent: Monday, June 19, 2017 4:06 PM
To: Phil Robb ; Arul Nambi 
Cc: Elhay Efrat ; onap-disc...@lists.onap.org; 
onap-tsc 
Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers 
Face-to-Face Meeting

Hi Phil, all,

Given the huge number of approved projects and their complexity, from one side, 
and lack of well-defined interactions and interfaces between those 
projects/modules representing the projects, from the other side, I would say we 
may need a meeting to define those, to synchronize on those, to see if all 
needed interfaces are indeed defined etc.

We’ve been trying to access the complexity internally and came up with the list 
of all potential interactions which will have to be developed, attached. The 
list may not be fully correct, I will be happy to upload it (just needs to know 
what would be the ideal placement for it) and invite the community to respond 
and introduce all required modifications. The list will have to be extended 
once we approve more projects.
(Please note that Integration and Documentation interfaces with all projects, 
but there is no need to build interface, just to coordinate.)

My development experience tells me such a mission can’t be achieved by project 
calls only, or even project-to-project calls, but requires a dedicated meeting, 
the sooner the better.

My 2 cents ☺

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2E914.228CB470]

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Monday, June 19, 2017 11:47 AM
To: Arul Nambi >
Cc: Elhay Efrat >; 
onap-disc...@lists.onap.org; onap-tsc 
>
Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers 
Face-to-Face Meeting

Hi Arul:

The problem with doing "both" is that if not enough people get in the room 
together physically, then for those that took the time, expense, and effort to 
get there they will not get much value from it.  If there is critical mass that 
get together in the room, then those remote, and on the phone *never* get 
nearly as much out of it as those in the room.

I would like to better understand what we would do at a group gathering, 
virtual or physical in late July.  Can folks propose propose 

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

[Gildas Lanilis]

Hi Phil,

I see 2 benefits in holding a real physical face 2 face developer event:

1)  Technical: it gives the project teams who have technical dependencies 
to seat together and speak on white board functional diagrams, sequence flaw 
diagrams ( good and error cases), finalize the API interface. This can be 
organized in parallel sessions (may be 3-4 sessions depending on the need).

2)  Community: Most developers in our community never had the opportunity 
to meet each other. We all know Human aspect is critical, and the relation 
between people is completely different after they meet. It creates trust and 
speed up the whole community. As we are at the inception of the ONAP, the 
sooner we do it, the better for the whole community.

A 2-3 days gathering would help. One more point regarding both approach 
(physical and virtual). We should recognize it is extremely difficult for 
remote people on the phone to understand and see (on the white board) what is 
gong on. Furthermore, I feel bad asking people who are 15 hours ahead or behind 
the wake up at 2 or 3 am to attend a meeting.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alla Goldner
Sent: Monday, June 19, 2017 6:06 AM
To: Phil Robb; Arul Nambi
Cc: onap-disc...@lists.onap.org; onap-tsc
Subject: Re: [onap-discuss] [onap-tsc] Tentative July ONAP Developers 
Face-to-Face Meeting

Hi Phil, all,

Given the huge number of approved projects and their complexity, from one side, 
and lack of well-defined interactions and interfaces between those 
projects/modules representing the projects, from the other side, I would say we 
may need a meeting to define those, to synchronize on those, to see if all 
needed interfaces are indeed defined etc.

We’ve been trying to access the complexity internally and came up with the list 
of all potential interactions which will have to be developed, attached. The 
list may not be fully correct, I will be happy to upload it (just needs to know 
what would be the ideal placement for it) and invite the community to respond 
and introduce all required modifications. The list will have to be extended 
once we approve more projects.
(Please note that Integration and Documentation interfaces with all projects, 
but there is no need to build interface, just to coordinate.)

My development experience tells me such a mission can’t be achieved by project 
calls only, or even project-to-project calls, but requires a dedicated meeting, 
the sooner the better.

My 2 cents ☺

Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D2E911.4CCD6250]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Phil Robb
Sent: Monday, June 19, 2017 11:47 AM
To: Arul Nambi 
Cc: Elhay Efrat ; onap-disc...@lists.onap.org; 
onap-tsc 
Subject: Re: [onap-tsc] [onap-discuss] Tentative July ONAP Developers 
Face-to-Face Meeting

Hi Arul:

The problem with doing "both" is that if not enough people get in the room 
together physically, then for those that took the time, expense, and effort to 
get there they will not get much value from it.  If there is critical mass that 
get together in the room, then those remote, and on the phone *never* get 
nearly as much out of it as those in the room.

I would like to better understand what we would do at a group gathering, 
virtual or physical in late July.  Can folks propose propose agenda topics so 
we can see what we would want to accomplish, and from that we can figure out 
the best format it?

Thanks,

Phil.

On Wed, Jun 14, 2017 at 9:28 PM, Arul Nambi 
> wrote:
+1 why can we not have both?

From: Elhay Efrat
Sent: Wednesday, June 14, 2017 5:31 AM
To: jamil.cha...@orange.com; Arul Nambi 
>
Cc: Dhananjay Pavgi 
>; Gadiyar, 
Rajesh >; GILBERT, 
MAZIN E (MAZIN E) >; 
Kenny Paul >; 
onap-disc...@lists.onap.org; onap-tsc 
>
Subject: RE: [onap-tsc] [onap-discuss] Tentative July ONAP Developers 
Face-to-Face Meeting

Why not always add vitrual ☺ ?

From: jamil.cha...@orange.com 
[mailto:jamil.cha...@orange.com]
Sent: Wednesday, June 14, 2017 10:00 AM
To: Arul Nambi >
Cc: Elhay Efrat >; 
Dhananjay Pavgi 

Re: [onap-tsc] Face to Face meeting agreements

[Gildas Lanilis]

One note regarding the Use Case.
During the F2F only the VoLTE use case was approved.
The vCPE use case was discussed but as no consensus was closed to be made the 
TSC asked the vCPE Use Case Team to refine the proposal. The vCPE Use Case Team 
has to formalize its new proposal by June 15.

Thanks,
Gildas
1 415 238 6287

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Kenny Paul
Sent: Monday, June 12, 2017 1:32 PM
To: Brian Hedstrom
Cc: onap-tsc
Subject: Re: [onap-tsc] Face to Face meeting agreements

Hello Brian,

I certainly understand your frustration and I’d like to apologize for the 
absence of sufficiently detailed information being captured in the IRC.  There 
were a number of technical, logistical issues across the board and on my part 
specifically, some basic “ramping-up” challenges that impacted the quality note 
taking at thus event.

The recordings of the event along with the timestamps for specific topics can 
be found here: https://wiki.onap.org/display/DW/Presentations

The list of approved projects can be found here:
https://wiki.onap.org/display/DW/Approved+Projects

As far as you list of projects below, ESR and Network Function Change Mgmt were 
discussed and deferred. To the best of my knowledge, the others did not make it 
onto the agenda.

I will be doing some work on the wiki this week as it relates to project data 
that should help out.

All of the use cases were approved.

Please let me know if you have any additional questions.
Thanks for your patience.


Best Regards,
-kenny.

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

On Jun 9, 2017, at 12:06 PM, Brian Hedstrom 
> 
wrote:

In looking at the F2F Day 1 Meeting 
Notes,
 and reviewing the IRC channel for Day 
2
 (it appears the meeting wasn't closed with #endmeeting and a meeting minute 
link wasn't generated), I'm finding it difficult to see what motions were voted 
on and approved versus voted down. There is missing/incomplete information in 
those notes.

Will there be a report or wiki page created that captures what motions passed 
at the F2F meeting?

I could not find any details on whether these projects were voted on:

  *   Authentication and Authorization Framework
  *   DMaaP
  *   External System Register
  *   Network Function Change Management
  *   ONAP Extensibility
  *   ONAP University
  *   Open Lab
  *   SNIRO Optimization Framework
  *   VNF Validation Program (ONAP ICE)
  *   Common Frameworks
Also, I only found that VoLTE Use Case was approved, were the other use cases 
approved?


Thanks,

--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oamtechnologyconsulting.com
brian.hedst...@oamtechnologies.com
720-470-7091
___
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

[onap-tsc] ONAP F2F TSC meeting minutes April 6

[Gildas Lanilis]

Meeting Minutes update:
During our ONAP F2F meeting, Ning So (Ning.So at ril.com<mailto:Ning.So at 
ril.com>) representing Reliance Jio was present (he arrived just after the TSC 
Members roll call) .

Thanks,
Gildas
Gildas Lanilis
OPEN-O Release Manager
gildas.lanilis at huawei.com
Mobile: 1 415 238 6287


From: Gildas Lanilis
Sent: Thursday, April 06, 2017 9:54 PM
To: 'onap-tsc at lists.onap.org'
Subject: ONAP F2F TSC meeting minutes April 6

Hi All,

Please find below the IRC link toward the ONAP F2F TSC meeting minutes that 
took place at Santa Clara Convention Center on Thursday, April 6, 2017 from 
3:30 pm PDT to 6:30 pm PDT.
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-04-06-22.42.html

For those who are interested to access the email archives on all ONAP-TSC 
threads use this link<https://lists.onap.org/pipermail/onap-tsc/>.

Once available, the link toward the Zoom recording will be shared.

Participants:
AMDOCS Alla Goldner
AT Mazin Gilbert
Bell Canada David Sauvageau
China Mobile Lingli Deng
China Telecom  Mr. Xiaojun XIE Absent
Cisco  Ed Warnicke
EricssonStephen Terrill
Gigaspaces Amir Levy
Huawei Chris Donley
IBMJason Hunt
Intel   Rajesh Gadiyar
NokiaRanny Haiby
Orange Roberto Kung
Reliance Jio Absent
Tech Mahindra  Anit Lohtia
VMWare  Xinhui Li
ZTE Meng Zhaoxing 
proxied by Huabing Zhao

Let me know if you have any questions.

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
OPEN-O Release Manager
gildas.lanilis at huawei.com
Mobile: 1 415 238 6287

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/4f8260e0/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2975 bytes
Desc: image001.png
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/4f8260e0/attachment.png>

[onap-tsc] ONAP F2F TSC meeting minutes April 6

[Gildas Lanilis]

Meeting Minutes update:
During our ONAP F2F meeting, it was Dhananjay Pavgi (DP00476350 at 
TechMahindra.com) representing Tech Mahindra not Anit Lohtia as indicated below.

Thanks,
Gildas
Gildas Lanilis
OPEN-O Release Manager
gildas.lanilis at huawei.com
Mobile: 1 415 238 6287


From: Gildas Lanilis
Sent: Thursday, April 06, 2017 9:54 PM
To: 'onap-tsc at lists.onap.org'
Subject: ONAP F2F TSC meeting minutes April 6

Hi All,

Please find below the IRC link toward the ONAP F2F TSC meeting minutes that 
took place at Santa Clara Convention Center on Thursday, April 6, 2017 from 
3:30 pm PDT to 6:30 pm PDT.
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-04-06-22.42.html

For those who are interested to access the email archives on all ONAP-TSC 
threads use this link<https://lists.onap.org/pipermail/onap-tsc/>.

Once available, the link toward the Zoom recording will be shared.

Participants:
AMDOCS Alla Goldner
AT Mazin Gilbert
Bell Canada David Sauvageau
China Mobile Lingli Deng
China Telecom  Mr. Xiaojun XIE Absent
Cisco  Ed Warnicke
EricssonStephen Terrill
Gigaspaces Amir Levy
Huawei Chris Donley
IBMJason Hunt
Intel   Rajesh Gadiyar
NokiaRanny Haiby
Orange Roberto Kung
Reliance Jio Absent
Tech Mahindra  Anit Lohtia
VMWare  Xinhui Li
ZTE Meng Zhaoxing 
proxied by Huabing Zhao

Let me know if you have any questions.

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
OPEN-O Release Manager
gildas.lanilis at huawei.com
Mobile: 1 415 238 6287

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/1f59ea0e/attachment-0001.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2975 bytes
Desc: image001.png
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170410/1f59ea0e/attachment-0001.png>

[onap-tsc] ONAP F2F TSC meeting minutes April 6

[Gildas Lanilis]

Hi All,

Please find below the IRC link toward the ONAP F2F TSC meeting minutes that 
took place at Santa Clara Convention Center on Thursday, April 6, 2017 from 
3:30 pm PDT to 6:30 pm PDT.
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-04-06-22.42.html

For those who are interested to access the email archives on all ONAP-TSC 
threads use this link<https://lists.onap.org/pipermail/onap-tsc/>.

Once available, the link toward the Zoom recording will be shared.

Participants:
AMDOCS Alla Goldner
AT Mazin Gilbert
Bell Canada David Sauvageau
China Mobile Lingli Deng
China Telecom  Mr. Xiaojun XIE Absent
Cisco  Ed Warnicke
EricssonStephen Terrill
Gigaspaces Amir Levy
Huawei Chris Donley
IBMJason Hunt
Intel   Rajesh Gadiyar
NokiaRanny Haiby
Orange Roberto Kung
Reliance Jio Absent
Tech Mahindra  Anit Lohtia
VMWare  Xinhui Li
ZTE Meng Zhaoxing 
proxied by Huabing Zhao

Let me know if you have any questions.

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
OPEN-O Release Manager
gildas.lanilis at huawei.com
Mobile: 1 415 238 6287

-- next part --
An HTML attachment was scrubbed...
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170407/e18f11d8/attachment.html>
-- next part --
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2975 bytes
Desc: image001.png
URL: 
<http://lists.onap.org/pipermail/onap-tsc/attachments/20170407/e18f11d8/attachment.png>