[onap-discuss] [ONAP Helpdesk #57926] RE: [LOG][AAI][SDNC] for [POMBA] Request for 10 additional Repos - CIMAN-169

[Gildas Lanilis via RT]

Hi Michael,

I have updated the wiki at 
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-LoggingEnhancements
 to update the "Maven Group ID" field.
Please review and confirm this is what you intended and we will take it from 
there for Log project.
As you mentioned, we will wait request from other PTLs impacted by this 
initiative to create their repos.

I see you added 2 extra columns labelled "Maven Artifact ID" and "Java package 
name". I am not sure what is the purpose of these 2 extra columns. This won't 
be used by LF. Could you explain?

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Michael O'Brien [mailto:frank.obr...@amdocs.com]
Sent: Monday, July 02, 2018 6:28 AM
To: onap-discuss ; 'helpd...@onap.org' 

Cc: Gildas Lanilis 
Subject: [LOG][AAI][SDNC] for [POMBA] Request for 10 additional Repos - 
CIMAN-169

LF, Jessica, Gildas,
   Hi, I am putting in a formal request for some additional repos, (git, 
gerrit, nexus, nexus3, sonar, Jenkins infrastructure).

   There are 10 repos requested for the POMBA sub-project these are distributed 
across logging-analtyics, SDNC and AA  I understand the PTLs (Tim and Jimmy) 
of sdnc and aai are aware of their requests - I have included all information 
across the projects to help collaboration and consolidation of work for the 
Linux Foundation.  This includes Sharon and Prudence of the POMBA sub-project.
   I am including Seshu from SO because I understand new repos are coming in 
there soon as well - since we are all helping each other out - I would ask any 
other project to join the conversation on any new repos they require so we can 
compare notes..
   The repos are of the AA model - where we have 1 repo per microservice.

DevOps jira only for logging-analytics so far has all these details and links 
to the following 3 tracking jiras.
https://jira.onap.org/browse/CIMAN-169

https://jira.onap.org/browse/LOG-193

*   logging-analytics/pomba-context-aggregator

*   logging-analytics/pomba-aai-context-builder

*   logging-analytics/pomba-sdc-context-builder

*   logging-analytics/pomba-sdnc-context-builder

*   logging-analytics/pomba-network-discovery-context-builder

*   logging-analytics/pomba-audit-common

The 2 requests below - are for info only right now - I am deferring to the AAI 
and SDNC projects to finalize these new repo requests - adding here for 
completeness from the POMBA perspective
https://jira.onap.org/browse/AAI-1348
TBD
*   aai/pomba/validation or aai/validation ?

https://jira.onap.org/browse/SDNC-358
TBD
* sdnc/service-decomposition
* sdnc/network-discovery
* sdnc/network-discovery-api

We need to also review the proposed maven groupId, artifactId, version 
(currently 1.1.2-SNAPSHOT) and java package name (org.onap.pomba in the sdnc 
and aai repos for example) and update the API section of the M1 page for Monday 
in all 3 projects.
https://wiki.onap.org/display/DW/Resources+and+Repositories
https://wiki.onap.org/display/DW/Logging+Casablanca+M1+Release+Planning
https://wiki.onap.org/display/DW/SDNC+%3A+Casablanca++%3A+Release+Planning+Template
https://wiki.onap.org/display/DW/AAI+R3+M1+Release+Planning

/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


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

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

Re: [onap-discuss] [ONAP Helpdesk #57926] [linuxfoundation.org #57926] RE: [LOG][AAI][SDNC] for [POMBA] Request for 10 additional Repos - CIMAN-169

[Gildas Lanilis via RT]

Hi Tian,

Please work with AAI PTL Jimmy to get the request documented in AAI first in 
wiki at 
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-ActiveandAvailableInventory
 
Once this is done, I will review and request LF creation accordingly.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Tian Lee via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, July 02, 2018 6:43 AM
To: frank.obr...@amdocs.com
Cc: Gildas Lanilis ; onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #57926] [linuxfoundation.org #57926] RE: 
[LOG][AAI][SDNC] for [POMBA] Request for 10 additional Repos - CIMAN-169

Hi,

On this specific point:

TBD
*   aai/pomba/validation or aai/validation ?

I would be inclined to go with aai/validation, since the Validation service is 
designed to be used in a variety of AAI flows (AAI data pre/post validation, 
validation of DMaaP events etc), therefore is not specific to pomba.

Regards,
Tian Lee
Software Design Expert
ONAP AAI project committer
Amdocs Technology

+44 (0)1225 32 7522

[amdocs-a]

Read the latest on Amdocs.com<http://www.amdocs.com/> and the Amdocs blog 
network<http://blogs.amdocs.com/> - and follow us on 
Facebook<http://www.facebook.com/Amdocs>, Twitter<http://twitter.com/Amdocs>, 
LinkedIn<http://www.linkedin.com/company/amdocs> and 
YouTube<http://www.youtube.com/amdocs>.



From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Michael O'Brien
Sent: 02 July 2018 14:28
To: onap-discuss ; 'helpd...@onap.org' 

Cc: gildas.lani...@huawei.com
Subject: [onap-discuss] [LOG][AAI][SDNC] for [POMBA] Request for 10 additional 
Repos - CIMAN-169

LF, Jessica, Gildas,
   Hi, I am putting in a formal request for some additional repos, (git, 
gerrit, nexus, nexus3, sonar, Jenkins infrastructure).

   There are 10 repos requested for the POMBA sub-project these are distributed 
across logging-analtyics, SDNC and AA  I understand the PTLs (Tim and Jimmy) 
of sdnc and aai are aware of their requests - I have included all information 
across the projects to help collaboration and consolidation of work for the 
Linux Foundation.  This includes Sharon and Prudence of the POMBA sub-project.
   I am including Seshu from SO because I understand new repos are coming in 
there soon as well - since we are all helping each other out - I would ask any 
other project to join the conversation on any new repos they require so we can 
compare notes..
   The repos are of the AA model - where we have 1 repo per microservice.

DevOps jira only for logging-analytics so far has all these details and links 
to the following 3 tracking jiras.
https://jira.onap.org/browse/CIMAN-169

https://jira.onap.org/browse/LOG-193

*   logging-analytics/pomba-context-aggregator

*   logging-analytics/pomba-aai-context-builder

*   logging-analytics/pomba-sdc-context-builder

*   logging-analytics/pomba-sdnc-context-builder

*   logging-analytics/pomba-network-discovery-context-builder

*   logging-analytics/pomba-audit-common

The 2 requests below - are for info only right now - I am deferring to the AAI 
and SDNC projects to finalize these new repo requests - adding here for 
completeness from the POMBA perspective
https://jira.onap.org/browse/AAI-1348
TBD
*   aai/pomba/validation or aai/validation ?

https://jira.onap.org/browse/SDNC-358
TBD
* sdnc/service-decomposition
* sdnc/network-discovery
* sdnc/network-discovery-api

We need to also review the proposed maven groupId, artifactId, version 
(currently 1.1.2-SNAPSHOT) and java package name (org.onap.pomba in the sdnc 
and aai repos for example) and update the API section of the M1 page for Monday 
in all 3 projects.
https://wiki.onap.org/display/DW/Resources+and+Repositories
https://wiki.onap.org/display/DW/Logging+Casablanca+M1+Release+Planning
https://wiki.onap.org/display/DW/SDNC+%3A+Casablanca++%3A+Release+Planning+Template
https://wiki.onap.org/display/DW/AAI+R3+M1+Release+Planning

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



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

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

[onap-discuss] 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 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-discuss@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-discuss@lists.onap.org<mailto:onap-discuss@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 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-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc:M
 AILTO:onap-...@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:20180613T08
DTEND;TZID=Pacific Standard Time:20180613T09
UID:04008200E00074C5B7101A82E00800E523F87FFED301000
 01000A84CD087B7545E4F98F55816F2974700
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180607T235250Z
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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 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-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc:M
 AILTO:onap-...@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #57038] beijing repo branching

[Gildas Lanilis]

Hi Jess,



Here u go.



- Are the teams ok branching from the latest tip of master? (This will make it 
easier on my script) [Gildas] For the repos on which there is either a Docker 
Release or a Java Released artifact, we should branch from that latest point. 
For other repos we should branch from the tip of master

- Do the teams want me to tag the tip of the beijing branch with "2.0.0-ONAP" 
tag? [Gildas] yes exactly, as documented here 
https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-BranchingandMerginginONAP
 (and beijing in lower case)



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 07, 2018 12:28 PM
To: Gildas Lanilis 
Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Subject: [ONAP Helpdesk #57038] beijing repo branching



Thanks so much for gathering this information Gildas!

This is a great list!



I have few questions:



- Are the teams ok branching from the latest tip of master? (This will make it 
easier on my script)

- Do the teams want me to tag the tip of the beijing branch with "2.0.0-ONAP" 
tag?



Thanks!

Jess



On Thu Jun 07 15:23:43 2018, 
gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com> wrote:

> Hi Helpdesk,

>

> Following TSC discussion on June 7, find in attachment the status of

> all ONAP repo and their need for a "beijing" branch.

> You will see that a lot has already been done.

>

> 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #57038] beijing repo branching

[Gildas Lanilis via RT]

Hi Jess,



Here u go.



- Are the teams ok branching from the latest tip of master? (This will make it 
easier on my script) [Gildas] For the repos on which there is either a Docker 
Release or a Java Released artifact, we should branch from that latest point. 
For other repos we should branch from the tip of master

- Do the teams want me to tag the tip of the beijing branch with "2.0.0-ONAP" 
tag? [Gildas] yes exactly, as documented here 
https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-BranchingandMerginginONAP
 (and beijing in lower case)



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 07, 2018 12:28 PM
To: Gildas Lanilis 
Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Subject: [ONAP Helpdesk #57038] beijing repo branching



Thanks so much for gathering this information Gildas!

This is a great list!



I have few questions:



- Are the teams ok branching from the latest tip of master? (This will make it 
easier on my script)

- Do the teams want me to tag the tip of the beijing branch with "2.0.0-ONAP" 
tag?



Thanks!

Jess



On Thu Jun 07 15:23:43 2018, 
gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com> wrote:

> Hi Helpdesk,

>

> Following TSC discussion on June 7, find in attachment the status of

> all ONAP repo and their need for a "beijing" branch.

> You will see that a lot has already been done.

>

> 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] beijing repo branching

[Gildas Lanilis]

Hi Helpdesk,

Following TSC discussion on June 7, find in attachment the status of all ONAP 
repo and their need for a "beijing" branch.
You will see that a lot has already been done.

Thanks,
Gildas

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



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

[onap-discuss] Beijing Branching

[Gildas Lanilis]

Hi PTLs,

Following today TSC's meeting and the Pas of Beijing Release, LF is going to 
create Beijing Branch on all repos that have not currently been branched.

In case you have some repos dedicated for Casablanca development and do not 
need Beijing Branch, please let me know asap.

@All committers, in the meantime, while LF creates the branches today (June 7), 
please refrain from merging code.


Thanks,
Gildas

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

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

[onap-discuss] Beijing Release: Last Mile

[Gildas Lanilis]

Hi PTLs,

This email is to summarize on the latest activities to reach Beijing Release 
Sign-Off this Thursday, June 7, 2018.

1.   Docker image: All projects that need to Release a new Docker Image 
(and thus update accordingly the Docker manifest file) must email LF Helpdesk 
by 2 pm PDT on Tuesday, June 5 including a link to the proper specific Jenkins 
build job that generated the selected candidate build (e.g. 
https://jenkins.onap.org/view/oparent/job/oparent-master-release-version-java-daily/124/).
 Ultimately, the Docker manifest 
file<https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv?h=beijing>
 (In Beijing Branch) should not contain words such as "latest", "SNAPSHOT" or 
"STAGING" but only version number. If necessary, also update the Java manifest 
file. All the release process is documented in 
wiki<https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process>.

2.   Release Notes: I have updated for most projects the "Security Notes" 
within each Release Notes. Thanks to review and merge its content (feel free to 
amend to fix typo, if any). Also, it is not necessary to list in the Release 
Notes all issues fixed into Beijing Release, but only the main one that were 
visible in Amsterdam externally to users. Same approach for "New Features", it 
is not necessary to list all Jira Stories implemented in Beijing, but rather 
focus on describing the 3-4 main features of your project. Last, Release Notes 
are cumulative (all release notes go in a single file); information for Beijing 
Release goes on the top of the file.

3.   Release Sign-Off Template: The Release Sign-Off template is available 
in 
wiki<https://wiki.onap.org/display/DW/Deliverables+for+Release+Sign-Off+Milestone+Checklist+Template>.
 Please fill it out and keep me posted on its availability so I can review.
Let me know if you have 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #56611] [linuxfoundation.org #56611] RE: Missing docker images

[Gildas Lanilis via RT]

Hi Helpdesk,

Could we have LF attention on this issue today?
As you can see this is blocking ONAP deployment and we have RC2 tomorrow on May 
31.
A similar ticket 55813 was raised a couple of week ago, but the issue still 
persists.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: aroraa...@vmware.com via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, May 30, 2018 12:45 AM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #56611] [linuxfoundation.org #56611] RE: Missing docker 
images

Missing image is blocking ONAP R2 deployment. Please generate/ recover the 
image.


Best Regards,
Arun Arora


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: 30 May 2018 05:16
To: helpd...@onap.org; onap-discuss@lists.onap.org
Subject: [onap-discuss] Missing docker images

Hi all,

The following images are currently missing from nexus3:

16:03:49 [ERROR] onap/dmaap/dmaap-mr:1.1.4 not found
16:04:14 [ERROR] onap/org.onap.dcaegen2.deployments.bootstrap:1.1.2 not found

Can whoever is able to generate or recover them please help?  This is blocking 
teams from making manifest changes.

Thanks,
Gary




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

Re: [onap-discuss] [ONAP Helpdesk #56611] [linuxfoundation.org #56611] RE: Missing docker images

[Gildas Lanilis]

Hi Helpdesk,

Could we have LF attention on this issue today?
As you can see this is blocking ONAP deployment and we have RC2 tomorrow on May 
31.
A similar ticket 55813 was raised a couple of week ago, but the issue still 
persists.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: aroraa...@vmware.com via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, May 30, 2018 12:45 AM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #56611] [linuxfoundation.org #56611] RE: Missing docker 
images

Missing image is blocking ONAP R2 deployment. Please generate/ recover the 
image.


Best Regards,
Arun Arora


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: 30 May 2018 05:16
To: helpd...@onap.org; onap-discuss@lists.onap.org
Subject: [onap-discuss] Missing docker images

Hi all,

The following images are currently missing from nexus3:

16:03:49 [ERROR] onap/dmaap/dmaap-mr:1.1.4 not found
16:04:14 [ERROR] onap/org.onap.dcaegen2.deployments.bootstrap:1.1.2 not found

Can whoever is able to generate or recover them please help?  This is blocking 
teams from making manifest changes.

Thanks,
Gary



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

[onap-discuss] Info for RC2 on Thursday

[Gildas Lanilis]

Hi PTLs,

This  email is to get the focus on what is expected by Thursday, May 31 for RC2.


1.   Defects: The list of Highest and High priority 
defects<https://jira.onap.org/issues/?filter=10703> must be Zero. I will send a 
status on the remaining later tonight.

2.   Integration Weather 
Board<https://wiki.onap.org/display/DW/Integration+Weather+Board>: update the 
page with the color coding for both the "Pair Wise Testing" and the "Maturity". 
The whole page is expected to be green.

3.   Pair Wise Testing: update your project page with the latest 
information.

4.   For the functional Requirements, work on with the following person to 
provide update

a.   
HPA<https://wiki.onap.org/display/DW/Hardware+Platform+Enablement+In+ONAP> 
(main contact Alexander Vul<https://wiki.onap.org/display/~avul>)

b.  Change 
Management<https://wiki.onap.org/pages/viewpage.action?pageId=4719331> (Main 
contact Ajay Mahimkar<https://wiki.onap.org/display/~ajaymahimkar>)

c.   Scaling<https://wiki.onap.org/display/DW/Auto+and+Manual+Scaling>  
(main contact Scott Blandford<https://wiki.onap.org/display/~csbford>)

5.   CSIT: The CSIT jobs<https://jenkins.onap.org/view/CSIT/> must pass. 
There are some jobs failing.

6.   Daily Build: Ensure the build targeted for Beijing Release are 
passing. I can see some RED job 
here<https://jenkins.onap.org/view/Daily-Jobs/>. Be sure the RED are not 
relevant for Beijing Release.

7.   Release Notes:

a.   I am in the process of updating the security section of the RN for 
your review and merge before the end of this week.

b.  Keep in mind that Release Notes are cumulative (all release notes go in 
a single file). Release Notes information for Beijing Release goes on the top 
of the file.  As a consequence, Release Notes editing takes place into Master 
branch.

c.   It is not necessary to list in the Release Notes all issues fixed into 
Beijing Release, but only the main one that were visible externally to users.

d.  Once the Release Notes has been merged, have a look on the rendering 
into ReadTheDocs. The formatting is not always what you may expect.

Let me know if I have missed anything and we will take it from there.

Thanks,
Gildas

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

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

Re: [onap-discuss] [ONAP Helpdesk #55868] RE: [onap-tsc] [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-discuss@lists.onap.org; onap-...@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-discuss@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-discuss@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-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

Re: [onap-discuss] [ONAP Helpdesk #55868] RE: [onap-tsc] [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-discuss@lists.onap.org; onap-...@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-discuss@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-discuss@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-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Fixing invalid YAML in read only git repos

[Gildas Lanilis]

Hi Michael,

Aai-config repo is no longer used by AAI Team, and thus the repo has been 
locked.
You can use this link to see status of the repo in Gerrit: 
https://gerrit.onap.org/r/#/admin/projects/?filter=aai

[cid:image001.jpg@01D3EE97.AD1B0D60]

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 Michael Still
Sent: Wednesday, May 16, 2018 6:01 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Fixing invalid YAML in read only git repos

Hi,

the INFO.yaml file in aai/aai-config is syntactically invalid, as are several 
others. I figured I'd just fix this, but my review was rejected because the 
repo is marked as read only:


$ git review

Could not connect to gerrit.

Enter your gerrit username: mikal

Trying again with 
ssh://mi...@gerrit.onap.org:29418/aai/aai-config.git

Creating a git remote called "gerrit" that maps to:

   
ssh://mi...@gerrit.onap.org:29418/aai/aai-config.git



This repository is now set up for use with git-review. You can set the

default username for future repositories with:

  git config --global --add gitreview.username "mikal"



Your change was committed before the commit hook was installed.

Amending the commit to add a gerrit change id.

remote: Processing changes: refs: 1, done

To 
ssh://mi...@gerrit.onap.org:29418/aai/aai-config.git

 ! [remote rejected] HEAD -> refs/publish/master (project is read only)

error: failed to push some refs to 
'ssh://mi...@gerrit.onap.org:29418/aai/aai-config.git'

Having valid YAML in these info files would be useful to me as I starting to 
write simple scripts that try to use this information. Is there any path to 
getting these files fixed?

Thanks,
Michael

--
Did this email leave you hoping to cause me pain? Good news!
Sponsor me in city2surf 2018 and I promise to suffer greatly.
http://www.madebymikal.com/city2surf-2018/
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Gerrit is down

[Gildas Lanilis]

Wiki is down too.

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 Gary Wu
Sent: Friday, May 04, 2018 11:13 AM
To: helpd...@onap.org; onap-discuss 
Subject: [onap-discuss] Gerrit is down

Hi Helpdesk,

gerrit.onap.org is down.  Can you take a look?

Thanks,
Gary


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

Re: [onap-discuss] [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-discuss@lists.onap.org; 
onap-...@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-discuss@lists.onap.org; 
onap-...@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [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-discuss@lists.onap.org; 
onap-...@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-discuss@lists.onap.org; 
onap-...@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Error accessing wiki.onap.org

[Gildas Lanilis]

Wiki is back.

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 Ramki Krishnan
Sent: Saturday, April 28, 2018 7:15 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Error accessing wiki.onap.org

I get the following error accessing wiki.onap.org. Are others facing the same 
issue?
Thanks,
Ramki
Confluence
You cannot access Confluence at present. Look at the table below to identify 
the reasons.
Type

Description

Exception

Level

Time

cluster

Non Clustered Confluence: Database is being updated by another Confluence 
instance. Please see http://confluence.atlassian.com/x/mwiyCg for more details.

Your server id is: BXAM-PB5R-RTXP-3EVE

fatal

2018-04-28 04:17:58

This page will automatically update every 60 seconds.

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

Re: [onap-discuss] Nexus3 docker.public configuration changed.

[Gildas Lanilis]

Hi PTLs,

This means that you might have some Released Docker images with dependencies on 
images in docker.snapshots and docker.staging who may be failing now.
If that is the case, you will need to request LF to release these images in 
docker.snapshots or docker.staging

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Jessica Wagantall [mailto:jwagant...@linuxfoundation.org]
Sent: Friday, April 27, 2018 3:04 PM
To: onap-discuss@lists.onap.org; onap-release <onap-rele...@lists.onap.org>; 
Jeremy Phelps <jphe...@linuxfoundation.org>; Andrew Grimberg 
<agrimb...@linuxfoundation.org>; Gildas Lanilis <gildas.lani...@huawei.com>
Subject: Re: Nexus3 docker.public configuration changed.

One more small reminder.

Releases to Nexus2 and Nexus3 should be requested:
- Via RT ticket (please skip direct emails to make sure anyone in my team can 
help out if I am not around)
- With PTL approval ( People in the committers group can also request releases, 
but preferably they should come from the PTL directly )
- Requests coming from the contributors (not in committers group) will always 
need the PTL approval.
- Jenkins job link that produced the binaries selected as candidate. ( Please 
make sure this link is from the actual build number and not
  just the build name that generates the images. For example:  
https://jenkins.onap.org/view/usecase-ui/job/usecase-ui-server-master-docker-java-daily/259)

Having this information ready for the release requests will help me and my team 
release faster.

Thanks!
Jess

On Fri, Apr 27, 2018 at 1:50 PM, Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>> wrote:
Dear ONAP team,

Today morning we had some issues with our docker.io<http://docker.io> proxy for 
which some teams were not able
to pull some needed libraries. This problem has been corrected this morning.

However, while debugging this issue, we realized our docker.public (10001) had 
a configuration
error.

docker.public should only be a group for docker.releases and 
docker.io<http://docker.io> (in that order) so that any dependencies are first 
looked for in docker.releases and, if not found, it would be looked for in
docker.io<http://docker.io>.

Our configuration was erroneously including docker.snapshots and docker.staging 
in the group too.
This configuration has been adjusted and some teams might see some dependency 
issues which
need to be corrected by the teams making a release of their binaries so that 
they become available
in the docker.public group.

Basically, we are following this rule that we are already following in Nexus2:
https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-ONAPVersioningStrategy

I am here to help making any releases if the team needs and of course with PTL 
approval and
via RT ticket.

Please let me know if you guys have any questions.
Thanks a ton!
Jess

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

Re: [onap-discuss] Casablanca Testing Process Improvement

[Gildas Lanilis]

Hi Helen,

Usually I like to strike while the iron when is hot, but I will follow the 
community guidance. I understand we all have our plate full.
I will cancel for tomorrow and unless I hear some push back I will reschedule 
for after Beijing Sign-Off (end of May).

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Yunxia Chen
Sent: Wednesday, April 18, 2018 11:52 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>; Gary Wu <gary.i...@huawei.com>; 
plata...@research.att.com; FREEMAN, BRIAN D <bf1...@att.com>; 
frank.obr...@amdocs.com; Mike Elliott <mike.elli...@amdocs.com>; Lando,Michael 
<ml6...@intl.att.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: Casablanca Testing Process Improvement

Hi, Gildas,

Thanks for following up with it. Is it possible to postpone to after Beijing 
release? We’ll have more experience to share by then and more time.

Regards,

Helen Chen

From: Gildas Lanilis 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Date: Wednesday, April 18, 2018 at 11:02 AM
To: Helen Chen 00725961 <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>, 
Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>, "PLATANIA, MARCO 
(MARCO)" <plata...@research.att.com<mailto:plata...@research.att.com>>, 
"FREEMAN, BRIAN D" <bf1...@att.com<mailto:bf1...@att.com>>, 
"frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>" 
<frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>, Mike Elliott 
<mike.elli...@amdocs.com<mailto:mike.elli...@amdocs.com>>, "Lando,Michael" 
<ml6...@intl.att.com<mailto:ml6...@intl.att.com>>
Cc: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Casablanca Testing Process Improvement

Hi All,

This is to follow up on the discussion we had last Monday during PTL meeting to 
overall improve our approach to testing (pair wise, healthcheck,…) with the 
goal to remove the burden on Integration team after M4.

These improvements are expected to take place in Casablanca release timeframe, 
not Beijing.

In attachment are the slides presented during PTLs meeting. I just removed the 
Caablanca timeline.

I don’t have much visibility on your timeline. Let me know if that works for 
you.

I have cc’ed the open-discuss mailing for transparency. I expect people in the 
To: to join the discussion but everyone is welcome.

Thanks all for your support,
Gildas


[https://d24cgw3uvb9a9h.cloudfront.net/static/90752/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>











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

[onap-discuss] Centralized Risks Beijing Release.

[Gildas Lanilis]

Hi PTLs,

Following up with PTLs meeting, a centralized wiki page to summarize Beijing 
Risks is now available for anyone who need to communicate his project' risks.
This is available at https://wiki.onap.org/display/DW/Beijing+Risks

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 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-discuss@lists.onap.org; onap-...@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-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-...@lists.onap.org<mailto:onap-...@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 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-...@lists.onap.org; onap-discuss@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Guidance Needed for Nexus IQ Issues

[Gildas Lanilis]

Hi Guangrong,

Thanks for reaching out.
Let me propose this.
During the Virtual F2F this week Steve Winslow from Linux Foundation is 
providing a talk on Copyrights and Licenses on Thursday. (See 
Agenda<https://wiki.onap.org/display/DW/VF2F+Feb.+5-8%2C+2017>).

I am sure Steve’s presentation will help a lot of teams. In case you still have 
issue, Steve and I will be glad to help you.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: fu.guangr...@zte.com.cn [mailto:fu.guangr...@zte.com.cn]
Sent: Sunday, February 04, 2018 7:44 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: zheng.nieco...@zte.com.cn; peng.congc...@zte.com.cn; li.yi...@zte.com.cn; 
onap-discuss@lists.onap.org
Subject: Guidance Needed for Nexus IQ Issues


Hi Gildas & all,



Holmes team members have been working on the policy violations found by Nexus 
IQ. But we are quite lost at how to handle those issues.



[cid:image001.png@01D39E54.CEFA2DA0]



What's the meaning of the violations on the screenshot? How could we eliminate 
the threats?



Thanks a ton.

Guangrong








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

Re: [onap-discuss] [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-discuss] High number of old pending commits

[Gildas Lanilis]

Hi All,

As discussed during the PTL meeting this am, there is currently a high volume 
of commits that have been pending for months.
The list is available here<https://gerrit.onap.org/r/#/q/status:open>.

I think that by respect to those who have made a contribution to the ONAP code, 
we should provide them some feedback, either by reviewing and commenting the 
work, abandon the work (It may very well not be useful anymore) or by merging 
the code into Master.
I understand there are some commits for which the discussion goes back and 
forth. That is a good sign of maturity, however this should not take months.

Thanks all for your support in spending a bit of time to review this list.

Thanks,
Gildas

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

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

Re: [onap-discuss] Triggering CLM jobs

[Gildas Lanilis]

Looping in security committee for their guidance.

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 DRAGOSH, PAMELA L 
(PAM)
Sent: Tuesday, January 23, 2018 10:32 AM
To: Jessica Wagantall ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Triggering CLM jobs

Jessica,

Thanks. I have a question on resolving security issues. Sometimes it is an easy 
fix to upgrade to a newer version of a dependency. However, other times there 
was no fix but a work around was in place. Or, it doesn’t apply because the 
method actually isn’t being used by our project. How do we resolve the CLM 
security issue? Do PTL’s have the right to do this (similar to sonar)?

Thanks,

Pam

From: 
>
 on behalf of Jessica Wagantall 
>
Date: Monday, January 22, 2018 at 5:58 PM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] Triggering CLM jobs

Dear ONAP team,

Just to let you know, the CLM jobs can now be triggered on demand after posting
the comment "run-clm" in your Gerrit change.

The CLM jobs are still scheduled to run every Saturday but I hope this feature 
can be
useful for debugging on demand.

Just as a reminder, commenting "run-clm" in a gerrit that is not merged, will 
not trigger
the CLM job based on that revision but will trigger the job based on the tip of 
the branch.
This job is designed to always run on the latest tip of the branch to avoid 
inconsistencies on
the reports.

Please let me know for any questions
Thanks a ton!
Jess.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] M2 Checklist Question

[Gildas Lanilis]

Hi Steve,

Following the discussion in PTL's call today, I will had the following question:
"Does your project team expect any feature content change from the current 
release scope to impact VNF requirements?"

Let me know your thoughts on the wording and I will add it asap in M2 checklist.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: WRIGHT, STEVEN A [mailto:sw3...@att.com]
Sent: Friday, January 05, 2018 7:41 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: M2 Checklist Question

Hi Gildas,

As ONAP  evolves, I'd like to have something in place to help keep the platform 
code evolution and VNF requirements in sync.  Could we  please add a question 
to the M2 checklist for the PTLS to identify if they expect any on the  feature 
content from the current release of their project to impact VNF requirements?


best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

sw3...@att.com<mailto:sw3...@att.com>
www.linkedin.com/in/drstevenawright/<http://www.linkedin.com/in/drstevenawright/>

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

[onap-discuss] 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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Confluence is down

[Gildas Lanilis]

Hi Helpdesk,


Could you help? Confluence is down
[cid:image001.png@01D38FC9.09813EE0]


Thanks,
Gildas

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

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

[onap-discuss] Beijing Release Functional requirements Commitment

[Gildas Lanilis]

Hi PTLs,

This is to follow up on the discussion we had earlier today at PTL weekly 
meeting regarding Beijing Functional Requirements.

I summarized in a single table the functional 
requirements<https://wiki.onap.org/display/DW/Beijing+Functional+Requirements> 
the PTLs are committing for Beijing Release.

So far, I had the chance to discuss with some of you to review the table.
For those I have not discussed yet with (sorry, it is a matter of geographical 
location), feel free to edit the table or contact me for any questions you may 
have. A 5-10 minutes zoom meeting<https://zoom.us/j/2229355644> worth the time.
Use the comment column to clearly state why a requirement is "NA" or "No". Feel 
to free to re-use current statements like "Not enough resource", "Requirement 
not clear", "Not priority", "Requirement owner did not reach out",...

It is critical we communicate clearly ahead on Beijing Release functional 
Requirement scope. During M1 review on Thursday, the clock will be ticking and 
we will not have time to discuss the details.

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] M2 Checklist Question

[Gildas Lanilis]

Hi Steven,

Thanks for reaching out with your question.
I will be glad to do so, but I would like to hear PTL's thoughts on this.
In any case, I will bring this question to our weekly PTL meeting.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: WRIGHT, STEVEN A [mailto:sw3...@att.com]
Sent: Friday, January 05, 2018 7:41 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: M2 Checklist Question

Hi Gildas,

As ONAP  evolves, I'd like to have something in place to help keep the platform 
code evolution and VNF requirements in sync.  Could we  please add a question 
to the M2 checklist for the PTLS to identify if they expect any on the  feature 
content from the current release of their project to impact VNF requirements?


best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

sw3...@att.com<mailto:sw3...@att.com>
www.linkedin.com/in/drstevenawright/<http://www.linkedin.com/in/drstevenawright/>

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

Re: [onap-discuss] [ONAP Helpdesk] Can NOT create jira issues

[Gildas Lanilis]

LF has now fixed the Jira issue. New rules are in place.
https://lists.onap.org/pipermail/onap-discuss/2018-January/007210.html

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Michael O'Brien [mailto:frank.obr...@amdocs.com]
Sent: Friday, January 05, 2018 7:47 AM
To: Lu, Lianhao <lianhao...@intel.com>; onap-discuss@lists.onap.org
Cc: Gildas Lanilis <gildas.lani...@huawei.com>
Subject: RE: [ONAP Helpdesk] Can NOT create jira issues

Lianhao
Started yesterday after making that field mandatory after the TSC proposal 
was implemented - looks like the change in the template may have been done 
without a crud test (create/update a jira)
In the queue - they are in PST so it is 7:45 AM there - likely this will 
get fixed in the next hour or so :)
   ONAP Helpdesk #50702

https://lists.onap.org/pipermail/onap-discuss/2018-January/007189.html
https://lists.onap.org/pipermail/onap-discuss/2018-January/007196.html

Thank you
/michael






-Original Message-
From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien
Sent: Friday, January 5, 2018 08:17
To: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; 
helpd...@onap.org<mailto:helpd...@onap.org>
Subject: [onap-discuss] CRITICAL: FW: [ONAP Helpdesk #50702] AutoReply: Unable 
to create new JIRA on mandatory "Affects Version" introduced today



Jessica,

Hi, JIRA currently is broken on the new validation field - we are not able 
to add any new issues - could we get this addressed ASAP, either temporarily 
reverse the change and retest it before reintroducing it or temporarily 
auto-populating it



 Thank you

 /michael



-Original Message-

From: ONAP Helpdesk via RT [mailto:onap-helpd...@rt.linuxfoundation.org]

Sent: Friday, January 5, 2018 00:44

To: Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>>

Subject: [ONAP Helpdesk #50702] AutoReply: Unable to create new JIRA on 
mandatory "Affects Version" introduced today



Greetings,



Your support ticket regarding:

  "Unable to create new JIRA on mandatory "Affects Version" 
introduced today", has been entered in our ticket tracker.  A summary of your 
ticket appears below.



If you have any follow-up related to this issue, please reply to this email.



You may also follow up on your open tickets by visiting 
https://rt.linuxfoundation.org/ -- if you have not logged into RT before, you 
will need to follow the "Forgot your password" link to set an RT password.



--

The Linux Foundation Support Team





-

LF,

  Hi, I totally agree with the new mandatory field "affects version"  - however 
I have tried adjusting the "configure fields" section and an unable to raise 
any Epic or Story anymore because of the blocking error on this field - which 
does not show on the create issue screen.

   Setting the "Fix Version/s" field does not help.

   Can you adjust the "Create Issue" screen so we can fill in this mandatory 
field





[cid:image002.jpg@01D385BE.48F088C0]

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>



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



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

___

onap-discuss mailing list

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

https://lists.onap.org/mailman/listinfo/onap-discuss


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lu, Lianhao
Sent: Friday, January 5, 2018 10:14
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] [ONAP Helpdesk] Can NOT create jira issues

Hi ONAP Helpdesk,

I just found that from today, I can NOT create new jira story. When I click 
"Create" in the jira web page, it says "Affects Version/s is required." But I 
can't find the corresponding input field of "Affects Version/s" on the creating 
page. How to deal with that?

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

[onap-discuss] Change in Jira

[Gildas Lanilis]

Hi All,

Following discussion and agreement we had during TSC 
meeting<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2018/onap-meeting.2018-01-04-13.47.html>
 (topic 5, Info z) regarding Jira usage, the following 2 changes are now 
effective within Jira.


1.   For Jira issue of type Bug, the field "Affects Version/s" is mandatory 
at the creation of the issue.

2.   For Jira issue of type Bug, the field "Fix Version/s" is mandatory 
during the transition from "Open" to "In Progress".

These new rules are applicable for all ONAP Jira projects and will help us to 
understand on which Release the bug was found and into which Release the Team 
plans to fix it.

Let me know if you have any question.

Thanks,
Gildas

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

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

[onap-discuss] F2F Santa Clara Presentation

[Gildas Lanilis]

Hi,

As a lot people have asked here is the link toward the presentation I made at 
Santa Clara F2F.
https://wiki.onap.org/display/DW/ONAP+Dec+2017+F2F+in+Santa+Clara


Thanks,
Gildas

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

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

Re: [onap-discuss] 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-...@lists.onap.org; onap-discuss@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [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-discuss@lists.onap.org; onap-...@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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

[Gildas Lanilis]

Thanks Dan for your prompt feedback.
Good point. I would suggest you add this point as a comment and we will take it 
from there.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Wednesday, November 29, 2017 1:56 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-release 
<onap-rele...@lists.onap.org>
Cc: onap-discuss <onap-discuss@lists.onap.org>; FREEMAN, BRIAN D 
<bf1...@att.com>
Subject: Re: [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

Gildas,

This is an excellent topic – thanks for starting this discussion!

One suggestion – we might want to separate out the HA/Geo Redundancy columns 
into 2 sets : one set for local HA only, and a second set for Geo Redundancy.

Just by way of example, in the case of SDN-C, we’d need 1 VM for no redundancy, 
8 for local HA, and 16 for geo redundancy.

I know that our target is geo redundancy, but it might be good to have a view 
of resources for local HA only as well.  That way, if we find we can’t afford 
the VMs for full geo redundancy, we’ll know the minimal set for local HA as 
well.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki<https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From: 
<onap-release-boun...@lists.onap.org<mailto:onap-release-boun...@lists.onap.org>>
 on behalf of Gildas Lanilis 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Date: Wednesday, November 29, 2017 at 3:31 PM
To: onap-release 
<onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>
Cc: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, "FREEMAN, 
BRIAN D" <bf1...@att.com<mailto:bf1...@att.com>>
Subject: [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

Hi PTLs,

We need your help.
We are working with Catherine, Helen and Brian on estimating the needs in term 
of Integration Lab resources for Beijing Release. This is important as it will 
most certainly impact $ budget and thus may require TSC and GB approval.
The details have been posted in the wiki at 
https://wiki.onap.org/display/DW/Integration+labs+need+for+Beijing<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Integration-2Blabs-2Bneed-2Bfor-2BBeijing=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=CaUG4r_Cugx2h70vsTNpSuic88WvQvOkdEn6HN4L51g=PkQYN-ujTSkhOXsPBggjxW5UrwxxkAhonWZo1SoY9rE=>
 and we need every team to fill out the table.

Please let my Catherine, Helen, Brian and Brian know if you have any questions.

It will be greatly appreciated if the table could be filled out by Monday, Dec 
4.

Thanks,
Gildas

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

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

[onap-discuss] ACTION REQUIRED: Estimating LAB resource needs

[Gildas Lanilis]

Hi PTLs,

We need your help.
We are working with Catherine, Helen and Brian on estimating the needs in term 
of Integration Lab resources for Beijing Release. This is important as it will 
most certainly impact $ budget and thus may require TSC and GB approval.
The details have been posted in the wiki at 
https://wiki.onap.org/display/DW/Integration+labs+need+for+Beijing and we need 
every team to fill out the table.

Please let my Catherine, Helen, Brian and Brian know if you have any questions.

It will be greatly appreciated if the table could be filled out by Monday, Dec 
4.

Thanks,
Gildas

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

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

Re: [onap-discuss] [integration]Enforce the second person for code review

[Gildas Lanilis]

Hi Helen,

I think here we are asking LF toll chain to re-enforce the statement on slide 
#4, bullet 2 “You cannot merge your own commit; someone else has to 
review/merge it after R1 RC0 and forward.”
I have created LF Ticket #47501.
Keep you posted as I heard back.


Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Yunxia Chen
Sent: Tuesday, October 24, 2017 11:50 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-discuss 
<onap-discuss@lists.onap.org>
Subject: Re: [integration]Enforce the second person for code review

Here’s the link:
https://wiki.onap.org/display/DW/TSC+2017-08-10?preview=%2F11929820%2F11929874%2FONAP-Upstream+Discussion+v2.0.pdf

Regards,

Helen Chen

From: Helen Chen 00725961 <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>
Date: Tuesday, October 24, 2017 at 11:36 AM
To: Gildas Lanilis 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>, onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [integration]Enforce the second person for code review

Hi, Gildas,
As TSC has approved that after RC0, code has to be reviewed by the second 
person. Could you please submit a help desk ticket to enforce it?
https://jira.onap.org/browse/INT-106

Regards,
Helen Chen

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

[onap-discuss] Practices on the usage of Jira-ID in the commit

[Gildas Lanilis]

Dear Community Members,

It came to my knowledge that some Jira IDs are, in some case, not been used 
properly when committing code.

To overcome this issue, please consider these cases:

1. If you commit some code in project A, ensure the Jira ID is 
reflecting the same project A.

2. Each issue is unique, and do not re-use the same Jira ID within the 
same project (unless it is a bug this is difficult to fix and requires multiple 
commits).

As we are entering in the integration phase, it is becoming more and more 
critical that we have a clear view on what goes into the release, I kindly 
request you abide to these practices.


Thanks,
Gildas

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

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

Re: [onap-discuss] M4 checklist finished about Usecase UI

[Gildas Lanilis]

Hi Tao,

Just for full transparency, I see in wiki Resource and 
Repositories<https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-UsecaseUI>
 there are 2 repos defined for “UseCase UI”, however in Sonar I see reports for 
“usecase-ui-server<https://sonar.onap.org/dashboard/index/73879>” (refer 
screenshot below)
[cid:image001.png@01D33B00.70F01F60]

Please keep me honest, am I missing anything? I thought I would see Sonar 
Coverage for “org.onap.usecase-ui” repo.


Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: shentao [mailto:shen...@chinamobile.com]
Sent: Sunday, October 01, 2017 5:07 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: M4 checklist finished about Usecase UI

Hi, Gildas

Usecase UI team has finished M4 checklist all requirements.
Could you help me to report TSC and confirm if we have anything else issues.

Best regards,
Tao

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

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

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

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

[onap-discuss] Agenda for M4 Code Review on Sept 28

[Gildas Lanilis]

Hi PTLs,

This message is regarding the M4 Code Freeze for Sept 28.
We had to breakdown the M4 review in 2 meetings: 1 meeting from 10 am to 12 pm 
(for people in China, and those who need to take-off in the afternoon) and a 
second from 1 pm to 3 pm (for people in the US and those who have extra time in 
the afternoon).
Time is Paris time zone.

If you cannot make it, please send your delegate.

The agenda is available in wiki at 
https://wiki.onap.org/display/DW/Agenda+for+M4+Review

Let me know if you have any question.

Thanks,
Gildas

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

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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis via RT]

Thanks Jess.



See my comments inline



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287



-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Tuesday, September 26, 2017 1:45 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



Sorry that the more I dig, the more issues I find. [Gildas] yes not a surprise. 
Thanks for your attention on this. That will place ONAP in a cleaner place.

Here is some work I did today:



- DMaaP Bus Controller UI (parent) - the jobs have been removed 
(https://gerrit.onap.org/r/#/c/15607/), shall we remove this entry? [Gildas] Yes

- Ecomp Portal SDK Project (parent) - Project has transitioned to portal/sdk 
which is fixed. Remove? [Gildas] yes

- modeling/toscaparsers/nfvparser - Working with the dev 
https://gerrit.onap.org/r/#/c/13247/  [Gildas] The repo modeling/toscaparsers 
contains some Java and Python files. As python is not covered by LF I think for 
know we can name it modeling-toscaparsers

- org/onap/vfc/nfvo/driver/ems/ems - https://gerrit.onap.org/r/#/c/15689/ 
[Gildas] merge it

- vfc/nfvo/wfengine/activiti-extension and vfc/nfvo/wfengine/wfenginemgrservice 
- https://gerrit.onap.org/r/#/c/15677/1 [Gildas] merge it

- SDC Distribution Client - https://gerrit.onap.org/r/#/c/15695/, 
https://gerrit.onap.org/r/#/c/15699/, https://gerrit.onap.org/r/#/c/15703/ 
[Gildas] merge them

- SDNC Plugins - https://gerrit.onap.org/r/#/c/15711/ and 
https://gerrit.onap.org/r/#/c/15713/ [Gildas] merge them.



Can you please help me pushing these merges please?

Thanks!

Jess



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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis]

Thanks Jess.



See my comments inline



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287



-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Tuesday, September 26, 2017 1:45 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



Sorry that the more I dig, the more issues I find. [Gildas] yes not a surprise. 
Thanks for your attention on this. That will place ONAP in a cleaner place.

Here is some work I did today:



- DMaaP Bus Controller UI (parent) - the jobs have been removed 
(https://gerrit.onap.org/r/#/c/15607/), shall we remove this entry? [Gildas] Yes

- Ecomp Portal SDK Project (parent) - Project has transitioned to portal/sdk 
which is fixed. Remove? [Gildas] yes

- modeling/toscaparsers/nfvparser - Working with the dev 
https://gerrit.onap.org/r/#/c/13247/  [Gildas] The repo modeling/toscaparsers 
contains some Java and Python files. As python is not covered by LF I think for 
know we can name it modeling-toscaparsers

- org/onap/vfc/nfvo/driver/ems/ems - https://gerrit.onap.org/r/#/c/15689/ 
[Gildas] merge it

- vfc/nfvo/wfengine/activiti-extension and vfc/nfvo/wfengine/wfenginemgrservice 
- https://gerrit.onap.org/r/#/c/15677/1 [Gildas] merge it

- SDC Distribution Client - https://gerrit.onap.org/r/#/c/15695/, 
https://gerrit.onap.org/r/#/c/15699/, https://gerrit.onap.org/r/#/c/15703/ 
[Gildas] merge them

- SDNC Plugins - https://gerrit.onap.org/r/#/c/15711/ and 
https://gerrit.onap.org/r/#/c/15713/ [Gildas] merge them.



Can you please help me pushing these merges please?

Thanks!

Jess


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

Re: [onap-discuss] [DMAAP][AAF] Release Management Status

[Gildas Lanilis]

I fear confusion. There is not nee to have a Jenkins Job for the Release Branch.
I would recommend you have a discussion with LF helpdesk.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: GUDISENA, VARUNESHWAR [mailto:vg4...@att.com]
Sent: Monday, September 25, 2017 8:29 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: 'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com>; GANDHAM, SAI <sg4...@att.com>; 'Jessica 
Wagantall' <jwagant...@linuxfoundation.org>
Subject: RE: [DMAAP][AAF] Release Management Status

Also, wanted  to inform that some of the Jenkins jobs which are failing in 
DMAAP are release jobs. These release jobs are failing because there is no 
release branch.


From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Monday, September 25, 2017 10:26 PM
To: GUDISENA, VARUNESHWAR <vg4...@att.com<mailto:vg4...@att.com>>
Cc: 'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; 'Jessica Wagantall' 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: RE: [DMAAP][AAF] Release Management Status

Hi Varun,

As DMAAP is a Gating project (AAF is not), that is where we should focus on.

The number of Red and Grey jobs in 
Jenkins<https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_dmaap_=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=S2qOaens2S1X5nqU95xJeA=8fag03sNhXMgh0FyBv18COOCYxQIvL62wQPc8sRsCg4=KzZoBRW6CBgT4gQ-aNCeMyLAWTenKraAGDMVpYZ-Ik8=>
 is quite impressive. If there is no plan to use them for Amsterdam, let remove 
them for Jenkins. That will declutter the place and help to see the what is 
really important.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: GUDISENA, VARUNESHWAR [mailto:vg4...@att.com]
Sent: Monday, September 25, 2017 9:52 AM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: 'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; 'Jessica Wagantall' 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: RE: [DMAAP][AAF] Release Management Status

Update on AAF:
Even though no other project is using AAF for Release 1, we are still targeting 
to release AAF in Amsterdam Release.



From: GUDISENA, VARUNESHWAR
Sent: Thursday, September 21, 2017 6:26 PM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: RE: [DMAAP][AAF] Release Management Status

Some of the message router stage sites are failing too. I will investigate.


From: GUDISENA, VARUNESHWAR
Sent: Thursday, September 21, 2017 6:21 PM
To: 'Gildas Lanilis' 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: [DMAAP][AAF] Release Management Status

Gildas,
I reviewed M2-M3 TSC Update excel.
For AAF, there are lot of Jenkins issues -> We are working on it. We are 
deferring AAF project for Release 2. No other ONAP project is using AAF in 
Release 1.
For DMaaP , there are lot Jenkins issues -> DMaaP has 3 components viz Message 
Router, Data Router and Bus Controller. We are deferring Data Router and Bus 
Controller
To Release 1. For Message Router, release jobs are failing. Stage site jobs 
never started . Jessica told since release branch is not available, release 
jobs are failing. I will
contact helpdesk on why stage site jobs were not started. CSIT tasks are also 
pending for M2 and M3. I have committed the code today. DMaaP CSIT code in
integration repo is merged. Jenkins CSIT config is in code review.

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

Re: [onap-discuss] [DMAAP][AAF] Release Management Status

[Gildas Lanilis]

I would recommend you remove the jobs by editing the JJB files in ci-management 
folder. Andy and Jess (LF Release Eng) will review your change.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: GUDISENA, VARUNESHWAR [mailto:vg4...@att.com]
Sent: Monday, September 25, 2017 8:27 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: 'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com>; GANDHAM, SAI <sg4...@att.com>; 'Jessica 
Wagantall' <jwagant...@linuxfoundation.org>
Subject: RE: [DMAAP][AAF] Release Management Status

I will send the list of Jenkins jobs to be removed to helpdesk.


From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Monday, September 25, 2017 10:26 PM
To: GUDISENA, VARUNESHWAR <vg4...@att.com<mailto:vg4...@att.com>>
Cc: 'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; 'Jessica Wagantall' 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: RE: [DMAAP][AAF] Release Management Status

Hi Varun,

As DMAAP is a Gating project (AAF is not), that is where we should focus on.

The number of Red and Grey jobs in 
Jenkins<https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_dmaap_=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=S2qOaens2S1X5nqU95xJeA=8fag03sNhXMgh0FyBv18COOCYxQIvL62wQPc8sRsCg4=KzZoBRW6CBgT4gQ-aNCeMyLAWTenKraAGDMVpYZ-Ik8=>
 is quite impressive. If there is no plan to use them for Amsterdam, let remove 
them for Jenkins. That will declutter the place and help to see the what is 
really important.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: GUDISENA, VARUNESHWAR [mailto:vg4...@att.com]
Sent: Monday, September 25, 2017 9:52 AM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: 'onap-discuss@lists.onap.org' 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; 'Jessica Wagantall' 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: RE: [DMAAP][AAF] Release Management Status

Update on AAF:
Even though no other project is using AAF for Release 1, we are still targeting 
to release AAF in Amsterdam Release.



From: GUDISENA, VARUNESHWAR
Sent: Thursday, September 21, 2017 6:26 PM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: RE: [DMAAP][AAF] Release Management Status

Some of the message router stage sites are failing too. I will investigate.


From: GUDISENA, VARUNESHWAR
Sent: Thursday, September 21, 2017 6:21 PM
To: 'Gildas Lanilis' 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: [DMAAP][AAF] Release Management Status

Gildas,
I reviewed M2-M3 TSC Update excel.
For AAF, there are lot of Jenkins issues -> We are working on it. We are 
deferring AAF project for Release 2. No other ONAP project is using AAF in 
Release 1.
For DMaaP , there are lot Jenkins issues -> DMaaP has 3 components viz Message 
Router, Data Router and Bus Controller. We are deferring Data Router and Bus 
Controller
To Release 1. For Message Router, release jobs are failing. Stage site jobs 
never started . Jessica told since release branch is not available, release 
jobs are failing. I will
contact helpdesk on why stage site jobs were not started. CSIT tasks are also 
pending for M2 and M3. I have committed the code today. DMaaP CSIT code in
integration repo is merged. Jenkins CSIT config is in code review.

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

Re: [onap-discuss] [DMAAP][AAF] Release Management Status

[Gildas Lanilis]

Hi Varun,

As DMAAP is a Gating project (AAF is not), that is where we should focus on.

The number of Red and Grey jobs in 
Jenkins<https://jenkins.onap.org/view/dmaap/> is quite impressive. If there is 
no plan to use them for Amsterdam, let remove them for Jenkins. That will 
declutter the place and help to see the what is really important.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: GUDISENA, VARUNESHWAR [mailto:vg4...@att.com]
Sent: Monday, September 25, 2017 9:52 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: 'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com>; GANDHAM, SAI <sg4...@att.com>; 'Jessica 
Wagantall' <jwagant...@linuxfoundation.org>
Subject: RE: [DMAAP][AAF] Release Management Status

Update on AAF:
Even though no other project is using AAF for Release 1, we are still targeting 
to release AAF in Amsterdam Release.



From: GUDISENA, VARUNESHWAR
Sent: Thursday, September 21, 2017 6:26 PM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: RE: [DMAAP][AAF] Release Management Status

Some of the message router stage sites are failing too. I will investigate.


From: GUDISENA, VARUNESHWAR
Sent: Thursday, September 21, 2017 6:21 PM
To: 'Gildas Lanilis' 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; DOMETRIUS, 
ALEXANDER C <ad0...@att.com<mailto:ad0...@att.com>>; GANDHAM, SAI 
<sg4...@att.com<mailto:sg4...@att.com>>; Jessica Wagantall 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: [DMAAP][AAF] Release Management Status

Gildas,
I reviewed M2-M3 TSC Update excel.
For AAF, there are lot of Jenkins issues -> We are working on it. We are 
deferring AAF project for Release 2. No other ONAP project is using AAF in 
Release 1.
For DMaaP , there are lot Jenkins issues -> DMaaP has 3 components viz Message 
Router, Data Router and Bus Controller. We are deferring Data Router and Bus 
Controller
To Release 1. For Message Router, release jobs are failing. Stage site jobs 
never started . Jessica told since release branch is not available, release 
jobs are failing. I will
contact helpdesk on why stage site jobs were not started. CSIT tasks are also 
pending for M2 and M3. I have committed the code today. DMaaP CSIT code in
integration repo is merged. Jenkins CSIT config is in code review.

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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis via RT]

Thanks Jess for the update. Glad to hear the news. I trust you , we are all 
getting a clean house here +1. :)

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, September 20, 2017 4:26 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention

Dear Gildas, 

I am noticing that most of these leftovers are due to the fact that we have to 
also change the names in the pom files for the release branches that can be 
causing these ugly names. 

I am almost done uploading all the changes and giving you a new update.. Will 
send it very shortly..
Just wanted to let you know that the delay is due to extra work actually needed.

Thanks!
Jess

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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis]

Thanks Jess for the update. Glad to hear the news. I trust you , we are all 
getting a clean house here +1. :)

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, September 20, 2017 4:26 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention

Dear Gildas, 

I am noticing that most of these leftovers are due to the fact that we have to 
also change the names in the pom files for the release branches that can be 
causing these ugly names. 

I am almost done uploading all the changes and giving you a new update.. Will 
send it very shortly..
Just wanted to let you know that the delay is due to extra work actually needed.

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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis]

Hi Deng,

If I look into Gerrit 
<https://gerrit.onap.org/r/#/q/project:modeling/toscaparsers> to the content of 
modeling/toscaparsers repo, I see some python and java files.

For Python flies, LF do not provide yet code coverage tool so, I agree, Sonar 
is not necessary but for Java files Sonar is in place.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: denghui (L)
Sent: Tuesday, September 19, 2017 5:56 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>; 
onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org; meng.zhaoxi...@zte.com.cn
Subject: RE: [ONAP Helpdesk #45515] Sonar naming convention

Gildas,


6. 
modeling/toscaparsers/nfvparser<https://sonar.onap.org/dashboard/index/53315>
These codes are all based on python, do they still need SONAR work?

Thanks a  lot

DENG Hui

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Wednesday, September 20, 2017 6:53 AM
To: 
onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention


Thanks Jess for the effort. Let's continue our journey. I found other entries 
that requires work.



1. Common Logging Library<https://sonar.onap.org/dashboard/index/2433>. 
Looks like this is related to commit for aai/logging-service at 
https://gerrit.onap.org/r/#/c/11289/ Not sure why this is still in Sonar. The 
Daily Jenkins Jobs has passed 
https://jenkins.onap.org/view/aai/job/aai-logging-service-master-release-version-java-daily/
 Ideas?

All the entries below are not correct and required your help.

2. Distribution<https://sonar.onap.org/dashboard/index/40657>

3. DMaaP Bus Controller UI 
(parent)<https://sonar.onap.org/dashboard/index/61735>

4. Ecomp Portal SDK Project 
(parent)<https://sonar.onap.org/dashboard/index/56961>

5. ECOMP Portal SDK Project 
(parent)<https://sonar.onap.org/dashboard/index/57947>

6. 
modeling/toscaparsers/nfvparser<https://sonar.onap.org/dashboard/index/53315>

7. inventory-api<https://sonar.onap.org/dashboard/index/66771> should 
be under dcaegen2/platform

8. MSO main project<https://sonar.onap.org/dashboard/index/61887> 
should be removed

9. OpenStack Java SDK<https://sonar.onap.org/dashboard/index/66901>

10. Parent POMs<https://sonar.onap.org/dashboard/index/33585>

11. SDN-C Adaptors<https://sonar.onap.org/dashboard/index/10345>

12. SDN-C Core Components<https://sonar.onap.org/dashboard/index/10057>

13. SDN-C Core Components - 
rootpom<https://sonar.onap.org/dashboard/index/42279>

14. SDN-C Java Plugins<https://sonar.onap.org/dashboard/index/11185>

15. SDN-C Northbound APIs<https://sonar.onap.org/dashboard/index/63769>

16. SDN-C OAM<https://sonar.onap.org/dashboard/index/63755>

17. VID Parent Project<https://sonar.onap.org/dashboard/index/9373>



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Tuesday, September 19, 2017 2:45 PM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



Here are more updates from my side:

- Removed "blueprints"

- Demo-aggregator removed, template to use no-sonar needs merge in gerrit: 
http://gerrit.onap.org/r/13601

- "model-loader" belongs to aai-model-loader. This was pre-onap rename when we 
were using openecomp. Removed it.

- "ncomp" removed

- "ONAP Operations Manager" removed

- "oparent" removed, template to use no-sonar needs merge in gerrit: 
http://gerrit.onap.org/r/13603

- Will try to reply soon to these 2 broken jobs since the tech teams have not 
reported them, but I contact them with what I see they have wrong in their pom 
files:

  - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-master-release-version-java-daily/

  - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-parent-master-release-version-java-daily/

- "dcae" removed

- "Portal (parent)" removed

- Items in your #7 are part of the items that I thought I fix but they are not 
updating. I have a possible cause and was able to fix 1 of them, will upload 
the same fix for the rest.





Thanks!

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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis via RT]

Hi Deng,

If I look into Gerrit 
<https://gerrit.onap.org/r/#/q/project:modeling/toscaparsers> to the content of 
modeling/toscaparsers repo, I see some python and java files.

For Python flies, LF do not provide yet code coverage tool so, I agree, Sonar 
is not necessary but for Java files Sonar is in place.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: denghui (L)
Sent: Tuesday, September 19, 2017 5:56 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>; 
onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org; meng.zhaoxi...@zte.com.cn
Subject: RE: [ONAP Helpdesk #45515] Sonar naming convention

Gildas,


6. 
modeling/toscaparsers/nfvparser<https://sonar.onap.org/dashboard/index/53315>
These codes are all based on python, do they still need SONAR work?

Thanks a  lot

DENG Hui

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gildas Lanilis
Sent: Wednesday, September 20, 2017 6:53 AM
To: 
onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention


Thanks Jess for the effort. Let's continue our journey. I found other entries 
that requires work.



1. Common Logging Library<https://sonar.onap.org/dashboard/index/2433>. 
Looks like this is related to commit for aai/logging-service at 
https://gerrit.onap.org/r/#/c/11289/ Not sure why this is still in Sonar. The 
Daily Jenkins Jobs has passed 
https://jenkins.onap.org/view/aai/job/aai-logging-service-master-release-version-java-daily/
 Ideas?

All the entries below are not correct and required your help.

2. Distribution<https://sonar.onap.org/dashboard/index/40657>

3. DMaaP Bus Controller UI 
(parent)<https://sonar.onap.org/dashboard/index/61735>

4. Ecomp Portal SDK Project 
(parent)<https://sonar.onap.org/dashboard/index/56961>

5. ECOMP Portal SDK Project 
(parent)<https://sonar.onap.org/dashboard/index/57947>

6. 
modeling/toscaparsers/nfvparser<https://sonar.onap.org/dashboard/index/53315>

7. inventory-api<https://sonar.onap.org/dashboard/index/66771> should 
be under dcaegen2/platform

8. MSO main project<https://sonar.onap.org/dashboard/index/61887> 
should be removed

9. OpenStack Java SDK<https://sonar.onap.org/dashboard/index/66901>

10. Parent POMs<https://sonar.onap.org/dashboard/index/33585>

11. SDN-C Adaptors<https://sonar.onap.org/dashboard/index/10345>

12. SDN-C Core Components<https://sonar.onap.org/dashboard/index/10057>

13. SDN-C Core Components - 
rootpom<https://sonar.onap.org/dashboard/index/42279>

14. SDN-C Java Plugins<https://sonar.onap.org/dashboard/index/11185>

15. SDN-C Northbound APIs<https://sonar.onap.org/dashboard/index/63769>

16. SDN-C OAM<https://sonar.onap.org/dashboard/index/63755>

17. VID Parent Project<https://sonar.onap.org/dashboard/index/9373>



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Tuesday, September 19, 2017 2:45 PM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



Here are more updates from my side:

- Removed "blueprints"

- Demo-aggregator removed, template to use no-sonar needs merge in gerrit: 
http://gerrit.onap.org/r/13601

- "model-loader" belongs to aai-model-loader. This was pre-onap rename when we 
were using openecomp. Removed it.

- "ncomp" removed

- "ONAP Operations Manager" removed

- "oparent" removed, template to use no-sonar needs merge in gerrit: 
http://gerrit.onap.org/r/13603

- Will try to reply soon to these 2 broken jobs since the tech teams have not 
reported them, but I contact them with what I see they have wrong in their pom 
files:

  - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-master-release-version-java-daily/

  - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-parent-master-release-version-java-daily/

- "dcae" removed

- "Portal (parent)" removed

- Items in your #7 are part of the items that I thought I fix but they are not 
updating. I have a possible cause and was able to fix 1 of them, will upload 
the same fix for the rest.





Thanks!

Jess

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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis via RT]

Thanks Jess for the effort. Let's continue our journey. I found other entries 
that requires work.



1. Common Logging Library<https://sonar.onap.org/dashboard/index/2433>. 
Looks like this is related to commit for aai/logging-service at 
https://gerrit.onap.org/r/#/c/11289/ Not sure why this is still in Sonar. The 
Daily Jenkins Jobs has passed 
https://jenkins.onap.org/view/aai/job/aai-logging-service-master-release-version-java-daily/
 Ideas?

All the entries below are not correct and required your help.

2. Distribution<https://sonar.onap.org/dashboard/index/40657>

3. DMaaP Bus Controller UI 
(parent)<https://sonar.onap.org/dashboard/index/61735>

4. Ecomp Portal SDK Project 
(parent)<https://sonar.onap.org/dashboard/index/56961>

5. ECOMP Portal SDK Project 
(parent)<https://sonar.onap.org/dashboard/index/57947>

6. 
modeling/toscaparsers/nfvparser<https://sonar.onap.org/dashboard/index/53315>

7. inventory-api<https://sonar.onap.org/dashboard/index/66771> should 
be under dcaegen2/platform

8. MSO main project<https://sonar.onap.org/dashboard/index/61887> 
should be removed

9. OpenStack Java SDK<https://sonar.onap.org/dashboard/index/66901>

10. Parent POMs<https://sonar.onap.org/dashboard/index/33585>

11. SDN-C Adaptors<https://sonar.onap.org/dashboard/index/10345>

12. SDN-C Core Components<https://sonar.onap.org/dashboard/index/10057>

13. SDN-C Core Components - 
rootpom<https://sonar.onap.org/dashboard/index/42279>

14. SDN-C Java Plugins<https://sonar.onap.org/dashboard/index/11185>

15. SDN-C Northbound APIs<https://sonar.onap.org/dashboard/index/63769>

16. SDN-C OAM<https://sonar.onap.org/dashboard/index/63755>

17. VID Parent Project<https://sonar.onap.org/dashboard/index/9373>



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Tuesday, September 19, 2017 2:45 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



Here are more updates from my side:

- Removed "blueprints"

- Demo-aggregator removed, template to use no-sonar needs merge in gerrit: 
http://gerrit.onap.org/r/13601

- "model-loader" belongs to aai-model-loader. This was pre-onap rename when we 
were using openecomp. Removed it.

- "ncomp" removed

- "ONAP Operations Manager" removed

- "oparent" removed, template to use no-sonar needs merge in gerrit: 
http://gerrit.onap.org/r/13603

- Will try to reply soon to these 2 broken jobs since the tech teams have not 
reported them, but I contact them with what I see they have wrong in their pom 
files:

  - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-master-release-version-java-daily/

  - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-parent-master-release-version-java-daily/

- "dcae" removed

- "Portal (parent)" removed

- Items in your #7 are part of the items that I thought I fix but they are not 
updating. I have a possible cause and was able to fix 1 of them, will upload 
the same fix for the rest.





Thanks!

Jess

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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis via RT]

Updating my notes with proper naming (instead of screenshots)

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Tuesday, September 19, 2017 9:50 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention

Moving Gildas notes back into this ticket for better logging... 


Hi Jess,
 
Thanks for your feedback. We are making progress. See my comments inline, I 
marked them as [Gildas-2]. And a few other points to consider just below.
 
Other points:
 
1)   I see in Sonar something named “blueprints”. However, in his Helpdesk 
request Lusheng mentioned Bluepribnt as “non code”. We can delete this 
blueprints from Sonar.
2)   Demo-aggregator: despite some confusion in Marco -1 at 
https://gerrit.onap.org/r/#/c/11201/ this item must be considered as “non-code” 
by using the skip-sonar.
3)   I see a model-loader. Quite strange. There is also an aai-model-loader 
but that one is perfectly good. Not sure to understand where that come from L
4)   All the ncomp-xxx must be removed. Ncomp repos have been locked by 
Lusheng request to helpdesk.
5)   ONAP Operations Manager Dashboard project this is completely weird to 
me. There is no controller, nor dashbard nor ecd project. We can delete this.
6)   oparent. There is really no code that will be shipped here. This is 
mainly used by Gary. We should consider this as skip.
7)   I see these guys (I meant Sonar entries below) that should not be 
here. All VFC jobs have recently passed their daily builds.
org/onap/vfc/nfvo/driver/ems/ems
org/onap/vfc/nfvo/driver/ems/ems
vfc/nfvo/drivers/vnfm/svnfm/huawei/vnfmadapter
vfc/nfvo/wfengine/activiti-extension
vfc/nfvo/wfengine/wfenginemgrservice
 
Thanks,
Gildas
ONAP Release Manager
1 415 238 6287
 
From: Jessica Wagantall [mailto:jwagant...@linuxfoundation.org] 
Sent: Monday, September 18, 2017 4:08 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: Andrew Grimberg <agrimb...@linuxfoundation.org>
Subject: Re: Sonar notes
 
Dear Gildas, 
 
here is one more update on this task:
 
- All the repos that you helped me confirmed that can be removed have been just 
now been removed. [Gildas-2]. Great. Smelling fresh air now.
 
- Broken jobs are still broken. I can start looking into them, but I am giving 
priority to other teams who did reported some Jenkins issues on their own jobs. 
[Gildas-2] Yes priority on ONAP Jenkins job that are failing. Once these jobs 
passed, we may be in better position to get Sonar fixed. 
  After that, I can totally help these 2:
  Distribution - job broken - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-master-release-version-java-daily/
  [Gildas-2] I see you have defined properly the distribution in 
https://gerrit.onap.org/r/#/c/11315/ . Instead of seeing the name Distribution 
we should see ccsdk-distribution
  Parent POMs - broken 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-parent-master-release-version-java-daily/
 [Gildas-2] I see you have defined properly the parent  in 
https://gerrit.onap.org/r/#/c/11415/ Instead of seeing the name Parent POMs we 
should see ccsdk-parent
 
- (No idea yet items) Looking in parallel with other activities. I need to test 
if this would be a possible cause, so trying it out with one of the repos 
(Listed change in the end of the email)
  
- Do you want me to remove all the fixed "dcae" entries? I think that's what I 
understood, but I just needed a confirmation. [Gildas-2] yes please all dcae 
need to be removed. You have locked the repos last week. 
 
 
Portal (parent) - not sure if its repeated from 
https://sonar.onap.org/overview?id=org.openecomp.portal%3Aecompportal-parent-project
 [Gildas] The Portal (parent) is version 1.0.0 so this old ecomp.
1 question here: Portal project has 2 repos: portal and portal/sdk. However, I 
see only a “clean up commit” for portal 
https://gerrit.onap.org/r/#/q/topic:sonar-name-cleanup+projects:portal reasons? 
Or it is me being missing glasses? - Missed this change, listed it in the end 
of this email... [Gildas-2] yes I see you have created a portal-sdk 
https://gerrit.onap.org/r/#/c/13249/ . Excellent. The above Portal (parent) can 
now be removed.
 
- Need these new changes merged: [Gildas-2] OK I will follow up with PTLs.



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

Re: [onap-discuss] [ONAP Helpdesk #45515] Sonar naming convention

[Gildas Lanilis]

Updating my notes with proper naming (instead of screenshots)

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Tuesday, September 19, 2017 9:50 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention

Moving Gildas notes back into this ticket for better logging... 


Hi Jess,
 
Thanks for your feedback. We are making progress. See my comments inline, I 
marked them as [Gildas-2]. And a few other points to consider just below.
 
Other points:
 
1)   I see in Sonar something named “blueprints”. However, in his Helpdesk 
request Lusheng mentioned Bluepribnt as “non code”. We can delete this 
blueprints from Sonar.
2)   Demo-aggregator: despite some confusion in Marco -1 at 
https://gerrit.onap.org/r/#/c/11201/ this item must be considered as “non-code” 
by using the skip-sonar.
3)   I see a model-loader. Quite strange. There is also an aai-model-loader 
but that one is perfectly good. Not sure to understand where that come from L
4)   All the ncomp-xxx must be removed. Ncomp repos have been locked by 
Lusheng request to helpdesk.
5)   ONAP Operations Manager Dashboard project this is completely weird to 
me. There is no controller, nor dashbard nor ecd project. We can delete this.
6)   oparent. There is really no code that will be shipped here. This is 
mainly used by Gary. We should consider this as skip.
7)   I see these guys (I meant Sonar entries below) that should not be 
here. All VFC jobs have recently passed their daily builds.
org/onap/vfc/nfvo/driver/ems/ems
org/onap/vfc/nfvo/driver/ems/ems
vfc/nfvo/drivers/vnfm/svnfm/huawei/vnfmadapter
vfc/nfvo/wfengine/activiti-extension
vfc/nfvo/wfengine/wfenginemgrservice
 
Thanks,
Gildas
ONAP Release Manager
1 415 238 6287
 
From: Jessica Wagantall [mailto:jwagant...@linuxfoundation.org] 
Sent: Monday, September 18, 2017 4:08 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: Andrew Grimberg <agrimb...@linuxfoundation.org>
Subject: Re: Sonar notes
 
Dear Gildas, 
 
here is one more update on this task:
 
- All the repos that you helped me confirmed that can be removed have been just 
now been removed. [Gildas-2]. Great. Smelling fresh air now.
 
- Broken jobs are still broken. I can start looking into them, but I am giving 
priority to other teams who did reported some Jenkins issues on their own jobs. 
[Gildas-2] Yes priority on ONAP Jenkins job that are failing. Once these jobs 
passed, we may be in better position to get Sonar fixed. 
  After that, I can totally help these 2:
  Distribution - job broken - 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-master-release-version-java-daily/
  [Gildas-2] I see you have defined properly the distribution in 
https://gerrit.onap.org/r/#/c/11315/ . Instead of seeing the name Distribution 
we should see ccsdk-distribution
  Parent POMs - broken 
https://jenkins.onap.org/view/ccsdk/job/ccsdk-parent-master-release-version-java-daily/
 [Gildas-2] I see you have defined properly the parent  in 
https://gerrit.onap.org/r/#/c/11415/ Instead of seeing the name Parent POMs we 
should see ccsdk-parent
 
- (No idea yet items) Looking in parallel with other activities. I need to test 
if this would be a possible cause, so trying it out with one of the repos 
(Listed change in the end of the email)
  
- Do you want me to remove all the fixed "dcae" entries? I think that's what I 
understood, but I just needed a confirmation. [Gildas-2] yes please all dcae 
need to be removed. You have locked the repos last week. 
 
 
Portal (parent) - not sure if its repeated from 
https://sonar.onap.org/overview?id=org.openecomp.portal%3Aecompportal-parent-project
 [Gildas] The Portal (parent) is version 1.0.0 so this old ecomp.
1 question here: Portal project has 2 repos: portal and portal/sdk. However, I 
see only a “clean up commit” for portal 
https://gerrit.onap.org/r/#/q/topic:sonar-name-cleanup+projects:portal reasons? 
Or it is me being missing glasses? - Missed this change, listed it in the end 
of this email... [Gildas-2] yes I see you have created a portal-sdk 
https://gerrit.onap.org/r/#/c/13249/ . Excellent. The above Portal (parent) can 
now be removed.
 
- Need these new changes merged: [Gildas-2] OK I will follow up with PTLs.


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

Re: [onap-discuss] [ptls][integration]Gating Project

[Gildas Lanilis]

Ah ah ☺ You have asked for the list, you got the list.
No Helen, this list has not been formally approved by TSC.

To clarify.
The list was done with the intention to de-risk as much as possible Amsterdam 
release.
The Gating projects are the projects that MUST be in Amsterdam.
The Non Gating projects are the projects that can be removed from Amsterdam in 
the case they would miss the coming milestones. We do not want these “Non 
Gating projects” to jeopardize the Amsterdam Release.
Now, in case the “Non Gating Projects” are ready for Amsterdam that is 
fantastic, they will be IN.

Hope this helps.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Yunxia Chen
Sent: Monday, September 18, 2017 4:02 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-discuss 
<onap-discuss@lists.onap.org>
Cc: GILBERT, MAZIN E (MAZIN E) <ma...@research.att.com>
Subject: Re: [ptls][integration]Gating Project

I knew that list. My question is: does that list approved by TSC as final?

Regards,

Helen Chen

From: Gildas Lanilis 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Date: Monday, September 18, 2017 at 12:35 PM
To: Helen Chen 00725961 <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>, 
onap-discuss <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: "GILBERT, MAZIN E (MAZIN E)" 
<ma...@research.att.com<mailto:ma...@research.att.com>>
Subject: RE: [ptls][integration]Gating Project

Hi Helen,

List of Gating vs Non-Gating that was presented on TSC weekly meeting on 
Thrusday, August 31.
That list was made on Monday, August 28 by PTLs who attended the meeting “TSC 
ONLY Amsterdam Recommendations”

Info in on Slide #5: 
https://wiki.onap.org/display/DW/TSC+2017-09-07?preview=%2F15994964%2F15994960%2FONAP+Recommendations+Amsterdam+ReleaseVersion2.pdf

Hope this helps.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yunxia Chen
Sent: Monday, September 18, 2017 8:13 AM
To: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: GILBERT, MAZIN E (MAZIN E) 
<ma...@research.att.com<mailto:ma...@research.att.com>>
Subject: [onap-discuss] [ptls][integration]Gating Project

While in today’s  “PTL & Coordinators Meeting”, someone mentioned “Gating 
Project”, where could I find the list? Since those projects might influence our 
E2E integration test flow, I would like to know it as soon as possible.

Regards,
Helen Chen

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

Re: [onap-discuss] "permission denied" for accessing referenced documents by Document project demo

[Gildas Lanilis]

There was a typo in the link provided in M4 template (an s was missing at 
guide). I fix it now.

The proper link is:
http://onap.readthedocs.io/en/latest/guides/onap-developer/how-to-use-docs/include-documentation.html

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 JI, LUSHENG (LUSHENG)
Sent: Friday, September 15, 2017 6:30 AM
To: DRAGOSH, PAMELA L (PAM) ; GLOVER, GREG L 

Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] "permission denied" for accessing referenced 
documents by Document project demo

Pam,

Later last night I found a way around it.
Basically, the direct links into content items will all give you “Permission 
Denied” error.  But the front page  http://onap.readthedocs.io/en/latest/ is 
okay.  Then you can navigate into the item of interest from there.

Hope this helps.
Lusheng

From: "DRAGOSH, PAMELA L (PAM)" 
>
Date: Friday, September 15, 2017 at 9:09 AM
To: "JI, LUSHENG (LUSHENG)" 
>, "GLOVER, GREG L" 
>
Cc: "onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-discuss] "permission denied" for accessing referenced 
documents by Document project demo

All,

Yes I have the same issue. Should folks create an account and then be given 
permission?

Thanks,

Pam

From: 
>
 on behalf of "JI, LUSHENG (LUSHENG)" 
>
Date: Thursday, September 14, 2017 at 8:56 PM
To: "GLOVER, GREG L" >
Cc: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] "permission denied" for accessing referenced documents 
by Document project demo

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

Sorry I could not attend your demo due to schedule conflict.  And today I 
finally got the chance to view the video.  Thanks for the effort.

When I was trying to access the pages referenced from your project wiki page, 
M4 template, and recorded demo.  But I get “Permission Denied You don't have 
the proper permissions to view this page. Please contact the owner of this 
project to request permission.” on ALL of them.  I registered an account on 
readdocs, that did not help either.

Any suggestions on how to actually see these documents?

Thanks,
Lusheng Ji
DCAE PTL



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

Re: [onap-discuss] Release Update Information

[Gildas Lanilis]

Hi PTLs,

To avoid last minutes "surprises" while filling out the M4 template, I would 
like to bring your attention on 2 particular items:

1)   Documentation Practice Area: By M4, every ONAP is expected to go 
through this "Has the team created a documentation Template in 
ReadTheDocs<http://onap.readthedocs.io/>?" These are instructions on how to 
create the 
environment<http://onap.readthedocs.io/en/latest/guides/onap-developer/how-to-use-docs/include-documentation.html>
 (just the shell for M4) within the Doc repo and at least within one of your 
project repos.  Greg and Rich are currently evangelizing the process within the 
community and recording will be available.

2)   Development Practice Area: By M4, it is expected that each team 
understands the ONAP versioning and Release process and thus the questions:  Do 
you have a clear plan to implement the Independent Versioning and Release 
Process<https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process>
 by RC0? I would recommend you have a discussion within your team on this to 
understand the process. In case you have questions, I would recommend to use 
the comment section of the wiki 
page<https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process>.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Thursday, September 14, 2017 3:50 PM
To: onap-rele...@lists.onap.org
Cc: onap-discuss@lists.onap.org; Phil Robb <pr...@linuxfoundation.org>
Subject: Release Update Information

Hi PTLs,

Following up on TSC meeting today.

2 important points to highlight:

1. MSSQL database: this was a lingering question. Phil Robb clarified 
the point that we CANNOT embed MSSQL database within ONAP. (see meeting minutes 
point 
#4<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-09-14-13.43.html>).
 Alternatives such as MariaDB and Postgres SLQ are acceptable.

2. M4 Code Freeze: the checklist has been recently updated and is 
available in 
wiki<https://wiki.onap.org/display/DW/Deliverable+for+Code+Freeze+Milestone+Checklist+Template>.
 For the teams who copied earlier the template, I would strongly recommend to 
take the latest. We will review the deliverables while meeting in Paris on Sept 
28.


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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] M4 Code Freeze Milestone Review

[Gildas Lanilis]

Hi Yoav,

I will be glad to see them attending this important milestone.
If PTLs can't make it, they should send out a delegate.

See you there.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Yoav Kluger [mailto:yoav.klu...@amdocs.com]
Sent: Friday, September 15, 2017 8:38 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>; onap-discuss@lists.onap.org
Subject: M4 Code Freeze Milestone Review

Hi Gildas,

Noticed you have scheduled this review for Thursday - do we know that people 
will be staying for Thursday to attend this review?

Thanks,
Yoav Kluger
Amdocs Technology
+1(201)912-7294
+972-54-4850278
[amdocs-a]

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

[onap-discuss] Release Update Information

[Gildas Lanilis]

Hi PTLs,

Following up on TSC meeting today.

2 important points to highlight:

1. MSSQL database: this was a lingering question. Phil Robb clarified 
the point that we CANNOT embed MSSQL database within ONAP. (see meeting minutes 
point 
#4<http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2017/onap-meeting.2017-09-14-13.43.html>).
 Alternatives such as MariaDB and Postgres SLQ are acceptable.

2. M4 Code Freeze: the checklist has been recently updated and is 
available in 
wiki<https://wiki.onap.org/display/DW/Deliverable+for+Code+Freeze+Milestone+Checklist+Template>.
 For the teams who copied earlier the template, I would strongly recommend to 
take the latest. We will review the deliverables while meeting in Paris on Sept 
28.


Let me know if you have any questions

Thanks,
Gildas

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

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

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

[Gildas Lanilis]

Hi,

I would recommend looking at:

1. Number of code contribution (Git commits)

2. Mailing list activities

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

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

Dear All,

Couple of other measures that could be considered:


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

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

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

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

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

Dear ONAP Community,

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

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

thanks!
Mazin





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

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

Re: [onap-discuss] YOUR ACTION IS REQUIRED: Sonar naming convention

[Gildas Lanilis]

Almost there. 9 more commits to review !!! and we will have a clean Sonar 
Dashboard.


Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Monday, September 11, 2017 4:50 PM
To: 'onap-discuss@lists.onap.org' <onap-discuss@lists.onap.org>; 
'onap-rele...@lists.onap.org' <onap-rele...@lists.onap.org>
Cc: 'Jessica Wagantall'' <jwagant...@linuxfoundation.org>
Subject: RE: YOUR ACTION IS REQUIRED: Sonar naming convention

There are still 27 commits pending on this!!! You do not want to be the last 
one. Isn’t it ☺
Click that link now: 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup
Please review and provide your disposition.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Friday, September 08, 2017 3:57 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>
Cc: Jessica Wagantall' 
<jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>>
Subject: YOUR ACTION IS REQUIRED: Sonar naming convention
Importance: High


Thanks Jess for your contributions.



To All ONAP Code Reviewers, Committers and PTLs,



LF has been helping us in housekeeping Sonar<https://sonar.onap.org/>. 
Currently, all names are upsides down. Once your action is performed, we should 
be able to quickly find relevant data info.



Please review the changes at 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup , provide 
your -1, +1,0,-2, +2 and merge the changes.



As Jess says below, once this is done, LF will help removing old entries.



Let’s see how fast we can get this done ☺…and then forget about it.



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Friday, September 08, 2017 3:18 PM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



As discussed, for step #1 I have pushed into gerrit all corrections needed to 
all projects for their root pom files. The "" parameter has been set to 
match the name in gerrit (separated by dashes).



These are the changes: 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup



Would you please help me communicating to the teams about the importance of 
getting these changes approved and merged? I now depend on them accepting my 
changes and any "-1" situations we can address them as it comes.



These changes will generate new entries in Sonar, after that we can work on 
removing old entries.



Thanks a ton in advance for your help!

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

[onap-discuss] Binaries in Gerrit

[Gildas Lanilis]

Hi PTLs,

I wanted to bring your attention on the presence of binaries files within your 
Gerrit repositories.
As you know, git and gerrit are exclusively for Software Configuration 
Management (meaning dealing with merging, branching, versioning source code) 
and not for storing jar, war, tar or other types of binaries.
Among other things, presence of binary in your repos make them heavier to clone 
and pull and may on the long term rebut potential developers.

This item was part of the M2 checklist and again in the coming M4 checklist. I 
strongly encourage your team to be proactive and take the measure to get rid of 
these binaries. See the list of files in attachment.
If those binaries are necessary for the execution of your project, you should 
consider alternatives such as retrieving them from Nexus or embed them within 
your Docker image.

Let me know if you have questions.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287
/onap/aaf/authz/authz-service/src/main/resources/docker-compose/old/dme2-3.1.200.jar
/onap/aai/sparky-be/src/main/resources/extApps/aai.war
/onap/aai/sparky-fe/webstormSettings/settings.jar
/onap/ccsdk/distribution/dgbuilder/tools/printYangToProp.jar
/onap/ccsdk/storage/pgaas/cdf/src/cdf-prop-value/buildjars/gnu_getopt.jar
/onap/dcae/demo/startup/message-router/docker_files/state-20170301.tar.gz
/onap/dcae/pgaas/cdf/src/cdf-prop-value/buildjars/gnu_getopt.jar
/onap/dcae/pgaas/cdf/src/cdf-prop-value/cdf-prop-value/src/main/java/cdf-prop-value.jar
/onap/dcae/pgaas/cdf/src/cdf-prop-value/cdf-util/src/main/java/cdf-util.jar
/onap/dmaap/datarouter/datarouter-prov/src/main/resources/authz.jar
/onap/dmaap/datarouter/datarouter-prov/src/main/resources/subscriber.jar
/onap/oom/kubernetes/config/docker/init/src/config/dcae/common-event/config/dcae-config.tar
/onap/policy/engine/POLICY-SDK-APP/src/main/webapp/app/policyApp/libs/bower_components/angular/angular.min.js.gzip
/onap/sdnc/oam/admportal/lib/antlr4-4.5.1.jar
/onap/sdnc/oam/admportal/lib/antlr4-runtime-4.5.1.jar
/onap/sdnc/oam/admportal/lib/GLCookieDecryption.jar
/onap/sdnc/oam/admportal/lib/java-concurrent-hash-trie-map-0.2.23.jar
/onap/sdnc/oam/admportal/lib/jsr305-2.0.3.jar
/onap/sdnc/oam/admportal/lib/object-cache-api-0.6.3-Helium-SR1.jar
/onap/sdnc/oam/admportal/lib/org.abego.treelayout.core-1.0.1.jar
/onap/sdnc/oam/admportal/lib/org.eclipse.osgi-3.8.1.v20120830-144521.jar
/onap/sdnc/oam/admportal/lib/ST4-4.0.8.jar
/onap/sdnc/oam/admportal/lib/util-0.6.3-Helium-SR1.jar
/onap/sdnc/oam/admportal/lib/yang-binding-0.6.3-Helium-SR1.jar
/onap/sdnc/oam/admportal/lib/yang-common-0.6.3-Helium-SR1.jar
/onap/sdnc/oam/dgbuilder/tools/printYangToProp.jar
/onap/vfc/nfvo/driver/ems/ems/boco/data/PM-ENB-EUTRANCELLNB-test.csv.gz
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] YOUR ACTION IS REQUIRED: Sonar naming convention

[Gildas Lanilis]

There are still 27 commits pending on this!!! You do not want to be the last 
one. Isn’t it ☺
Click that link now: 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup
Please review and provide your disposition.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Gildas Lanilis
Sent: Friday, September 08, 2017 3:57 PM
To: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Cc: Jessica Wagantall' <jwagant...@linuxfoundation.org>
Subject: YOUR ACTION IS REQUIRED: Sonar naming convention
Importance: High


Thanks Jess for your contributions.



To All ONAP Code Reviewers, Committers and PTLs,



LF has been helping us in housekeeping Sonar<https://sonar.onap.org/>. 
Currently, all names are upsides down. Once your action is performed, we should 
be able to quickly find relevant data info.



Please review the changes at 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup , provide 
your -1, +1,0,-2, +2 and merge the changes.



As Jess says below, once this is done, LF will help removing old entries.



Let’s see how fast we can get this done ☺…and then forget about it.



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Friday, September 08, 2017 3:18 PM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



As discussed, for step #1 I have pushed into gerrit all corrections needed to 
all projects for their root pom files. The "" parameter has been set to 
match the name in gerrit (separated by dashes).



These are the changes: 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup



Would you please help me communicating to the teams about the importance of 
getting these changes approved and merged? I now depend on them accepting my 
changes and any "-1" situations we can address them as it comes.



These changes will generate new entries in Sonar, after that we can work on 
removing old entries.



Thanks a ton in advance for your help!

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

[onap-discuss] YOUR ACTION IS REQUIRED: Sonar naming convention

[Gildas Lanilis]

Thanks Jess for your contributions.



To All ONAP Code Reviewers, Committers and PTLs,



LF has been helping us in housekeeping Sonar<https://sonar.onap.org/>. 
Currently, all names are upsides down. Once your action is performed, we should 
be able to quickly find relevant data info.



Please review the changes at 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup , provide 
your -1, +1,0,-2, +2 and merge the changes.



As Jess says below, once this is done, LF will help removing old entries.



Let’s see how fast we can get this done ☺…and then forget about it.



Thanks,

Gildas

ONAP Release Manager

1 415 238 6287





-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Friday, September 08, 2017 3:18 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45515] Sonar naming convention



Dear Gildas,



As discussed, for step #1 I have pushed into gerrit all corrections needed to 
all projects for their root pom files. The "" parameter has been set to 
match the name in gerrit (separated by dashes).



These are the changes: 
https://gerrit.onap.org/r/#/q/status:open+topic:sonar-name-cleanup



Would you please help me communicating to the teams about the importance of 
getting these changes approved and merged? I now depend on them accepting my 
changes and any "-1" situations we can address them as it comes.



These changes will generate new entries in Sonar, after that we can work on 
removing old entries.



Thanks a ton in advance for your help!

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

[onap-discuss] Sonar naming convention

[Gildas Lanilis]

Hi Helpdesk,

The way ONAP projects are currently named in Sonar are actually messy and not 
consistent at https://sonar.onap.org/.

Do you have any recommendation to make this more user friendly. I would like to 
see them grouped by ONAP project.
I kind of like what VFC has done as it provides the full path in its name.

Thoughts?


Thanks,
Gildas

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

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

Re: [onap-discuss] which version to use for new project

[Gildas Lanilis]

Hi Kanagaraj,

Multiple persons (Oliver S, Helen C, Gary W, Christophe C, Anael C, Andy G, 
myself, and certainly other (sory if I miss their name)) within the ONAP 
community have been scratching their head on the versioning issue.

The main line of thinking has been captured in wiki at 
https://wiki.onap.org/display/DW/Release+Versioning+Strategy Please read this 
as it provides some background information on why we have chosen this approach.
Gary is also documenting the “How To” to make it concrete within your project 
at https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process

I would encourage you to consider these 2 pages.
For now, definitely every component has the freedom to come up with their own 
version.

Hope this helps.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Kanagaraj Manickam
Sent: Sunday, September 03, 2017 9:44 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: RE: which version to use for new project

Dear Gildas,

I think for deployment projects both HEAT template (demo) and OOM, it would 
make it easier if every component in Amsterdam release would follow the same 
versioning , 1.1.
Otherwise, deployment services needs to keep track of the version of each 
component, which would complicate it.

have observed this scenario, when we are making the required changes for CLI in 
deployment projects (demo and OOM). So we are setting the CLI version to 1.1 to 
make it very simple.
Please let us know if you see any issue. Thanks.

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

From: Gildas Lanilis
Sent: Monday, August 28, 2017 8:09 PM
To: Kanagaraj Manickam
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: RE: which version to use for new project

Hi Kanagaraj,

Among other thing, ONAP Is adopting Sementic Versionning, so it can’t be 1.0 or 
1.1.

Each project can define its version. Read this post for more info 
https://wiki.onap.org/display/DW/Release+Versioning+Strategy

Let me know if you have further questions.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Kanagaraj Manickam
Sent: Monday, August 28, 2017 12:12 AM
To: Gildas Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: which version to use for new project

Dear Gildas,

For new project approved in this release, which version to use , 1.0 or 1.1?
Pls help.

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

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

Re: [onap-discuss] ONAP Deployment Strategy for R1: OOM vs Heat Template

[Gildas Lanilis]

The meeting has been cancelled.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Friday, September 01, 2017 7:10 AM
To: Yunxia Chen <helen.c...@huawei.com>; Sauvageau, David 
(david.sauvag...@bell.ca) <david.sauvag...@bell.ca>; Gildas Lanilis 
<gildas.lani...@huawei.com>; Roger Maitland <roger.maitl...@amdocs.com>; Seshu 
m <seshu.kuma...@huawei.com>; HEMLI, AMICHAI <ah0...@intl.att.com>; TIMONEY, 
DAN <dt5...@att.com>; KOYA, RAMPRASAD <rk5...@att.com>; TALASILA, MANOOP 
(MANOOP) <talas...@research.att.com>; yangya...@chinamobile.com; Xinhui Li 
<lxin...@vmware.com>; DRAGOSH, PAMELA L (PAM) <pdrag...@research.att.com>; 
FORSYTH, JAMES <jf2...@att.com>; onap-discuss <onap-discuss@lists.onap.org>
Subject: Re: ONAP Deployment Strategy for R1: OOM vs Heat Template

Is this meeting still happening?

Marco

From: helen.c...@huawei.com<mailto:helen.c...@huawei.com>
When: 10:00 AM - 11:00 AM September 1, 2017
Subject: ONAP Deployment Strategy for R1: OOM vs Heat Template
Location: https://zoom.us/j/44


When: Friday, September 01, 2017 7:00 AM-8:00 AM. (UTC-08:00) Pacific Time (US 
& Canada)
Where: 
https://zoom.us/j/44<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_44=DwQFoQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=7pg4aAIMaSv23OCm6jmP8aiF1ZlSk0pM-jkmKaWTd_s=9VP517BgUPNHsHA9ZhdCndu6RQw2m5kLGvy7vFYzkB0=>

*~*~*~*~*~*~*~*~*~*
Hi, David, Marco and PTLs on this list,

Let’s use this time to decide which way we should go. If necessary, we report 
to TSC for approval.

For people who are not aware of the context, please refer to Marco’s initial 
emails (attached).

For PTLs on this list, from my information (may not up to date), OOM has not 
integrated with your project:
AAI
VID
SO
SDNC
DCAE
Portal
VFC
Multi-VIM
MSBhjn
Policy
CCF

If you or your proxy cannot make this meeting, please go to the following wiki 
page to add comments related to your project and cc us as well before 9/1/2017 
7:00am PDT :
https://wiki.onap.org/display/DW/ONAP+Installation+Strategy+for+Release+A<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BInstallation-2BStrategy-2Bfor-2BRelease-2BA=DwMFoQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=7pg4aAIMaSv23OCm6jmP8aiF1ZlSk0pM-jkmKaWTd_s=sbbhlLklWKNRAI3XCLwMKCxOT-8xT9V-Lz2lvGD_7aE=>

If you’d like to use OOM, please work with David to give us a solid date for 
when it could be done. Since Integration team is doing daily testing, we need 
to identify one tool to deploy ONAP for R1 before the end of this week.

Thank you,
Helen Chen


ONAP Deployment Strategy for R1: OOM vs Heat Template

(Non LF Zoom Licence)
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/44<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F44-26sa-3DD-26usd-3D2-26usg-3DAFQjCNGOukyk-2DyviNF7xE6h-2DW-5Fr5G1RgPA=DwMFoQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=7pg4aAIMaSv23OCm6jmP8aiF1ZlSk0pM-jkmKaWTd_s=TEOx4_UIEToExQuXWH85_HExpPO68Y5sIbrAQnVfffo=>
Or iPhone one-tap (US Toll): +16465588656,44# or 
+14086380968,44#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 44  8
International numbers available: 
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fzoomconference-253Fm-253DCqsAwHx4CSyRanCfPHKBvf6Vslgcsn86-26sa-3DD-26usd-3D2-26usg-3DAFQjCNHmeO65V-5FncgXTJyNNL6g4uKzSNyg=DwMFoQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=7pg4aAIMaSv23OCm6jmP8aiF1ZlSk0pM-jkmKaWTd_s=v7vsZ8tueuJMQOP9WxU8f9voYdllBX9qiBVS1p7DoCc=>

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

Re: [onap-discuss] which version to use for new project

[Gildas Lanilis]

Hi Kanagaraj,

Among other thing, ONAP Is adopting Sementic Versionning, so it can’t be 1.0 or 
1.1.

Each project can define its version. Read this post for more info 
https://wiki.onap.org/display/DW/Release+Versioning+Strategy

Let me know if you have further questions.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Kanagaraj Manickam
Sent: Monday, August 28, 2017 12:12 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: which version to use for new project

Dear Gildas,

For new project approved in this release, which version to use , 1.0 or 1.1?
Pls help.

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

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

[onap-discuss] LF ticket number

[Gildas Lanilis]

Hi,

I heard some of you complaining that when submitting a ticket to 
helpd...@onap.org<mailto:helpd...@onap.org> they would not receive a LF ticket 
number back.
I observed similar issue earlier this week, and by chance it starts working 
again this morning. I submitted a ticket for that issue, but LF has no evidence 
of the problem.

I also noticed there is a way to consult and submit LF tickets online by 
connecting to https://rt.linuxfoundation.org/ (the username is the email 
address related to your LFID). For the PWD, you will need to use the "Forgot 
your password" link.

There is one limitation: you can only see the ticket you have submitted. It 
would be great if we could see the ticket submitted within the ONAP community.
It works for me and thoughts it would bring value to you as well.


Thanks,
Gildas

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

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

Re: [onap-discuss] CSIT Test Case Review for M3

[Gildas Lanilis]

Hi Helen,

The purpose of this item was to ensure consistency across projects and have the 
confidence that we were testing the right things.
As Integration Team is helping each team with their CSIT, we should be good. I 
have removed this checkpoint for this release. We can revisit this item and 
decide if we need to add it for later releases.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Yunxia Chen
Sent: Wednesday, August 16, 2017 2:37 PM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Cc: SPATSCHECK, OLIVER <spat...@research.att.com>; LEFEVRE, CATHERINE 
<cl6...@intl.att.com>; ROSE, DANIEL V <dr6...@att.com>; Gary Wu 
<gary.i...@huawei.com>; onap-discuss <onap-discuss@lists.onap.org>
Subject: CSIT Test Case Review for M3

Hi, Gildas,

From M3 checklist, I saw this item:
Have you reviewed all the Test Case with Integration Team?

yes

Schedule a meeting with Integration Team to review the deliverable.


Currently, Integration team is helping each project on their CSIT setup, we 
have wiki and video for how to do it:
https://wiki.onap.org/display/DW/Creating+a+CSIT+Test

But since we will be very busy on implementing some cross projects / pair 
projects CSITs and E2E Lab implementation, I am afraid that Integration team 
will become the bottleneck for M3. Could we remove this item, instead, we 
depend on PTLs to decide whether they have their core functionalities covered 
in their CSIT or not?

Regards,
Helen Chen
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Versioning for Amsterdam

[Gildas Lanilis]

>

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

> Subject: Re: [onap-discuss] Versioning for Amsterdam

>

>

> I agree that we should do 3.) independent of 1.) and 2.) ( Again I don’t 
> think there has been a final decision but I din’t hear any opposition to 3. 
> so far).

>

> As for:

>

> " AAI version 2.0.3, AAF version 1.0.8, Clamp version 0.9.0.”

>

> I think that’s actually a good thing.

>

> First we are using 3rd party software of different versions anyway. All those 
> components depend on often hundreds of jar files which have all kind of 
> version numbers and version number schemes. So if we are going with 2.) we 
> are treating other components not differently as we would treat external 
> components from a build perspective.

>

> Also above would more honestly represent maturity. E.g. if we are introducing 
> a new component and ONAP itself is in release 10.X.X should the “beta” 
> version of that new component have a 10.X.X release number of a 0.X.X release 
> number. Giving it a 10.X.X release number as the first release is very 
> misleading… . Also easier for CICD if we ever decided to go that route.

>

> As for the question if there would be one version per project or repo I would 
> really leave this up to the projects to work out. If we can handle one per 
> project the build infrastructure will also be able to handle one per repo.

>

> I like Pam’s suggestion. Let’s set up some time to close on this next week at 
> the virtual dev meeting.

>

> Gildas can you set up the discussion as part of the release planing?

>

> Thx

>

> Oliver

>

>> On Jul 19, 2017, at 7:27 PM  EDT, Yunxia Chen 
>> <helen.c...@huawei.com<mailto:helen.c...@huawei.com>> wrote:

>>

>> Option 3 is an alternative as option 1. I +1 for option 1 or option 3 from 
>> Integration point of view and end user point of view.

>>

>> I understand that the “freedom” on each project with its own versioning. As 
>> stated in Gildas’s email, currently we have 20+ projects which will 
>> participate the Arsterdam simultaneous release, it will be very hard for us 
>> to test all those combinations and maintain that mapping.

>>

>> Regards,

>>

>> Helen Chen

>>

>> From: 
>> <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
>>  on behalf of Gildas

>> Lanilis <gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>

>> Date: Wednesday, July 19, 2017 at 1:58 PM

>> To: "HANSEN, TONY L" <t...@att.com<mailto:t...@att.com>>, 
>> "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>"

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

>> Subject: Re: [onap-discuss] Versioning for Amsterdam

>>

>> To my knowledge, no decision was made on versioning.

>>

>> If we go with option #2:

>>

>> Questions:

>> 1)  Who is maintaining the version dependency? Or ideally how to 
>> generate automatically that dependency graph?

>> 2)  When we will deliver Amsterdam later in November, we are going to 
>> say: We are delivering Amsterdam Release 1.0.0 that embeds the following 
>> components: AAI version 2.0.3, AAF version 1.0.8, Clamp version 0.9.0. and 
>> so on. Are we comfortable with that approach?

>>

>> 3)  Independently of option #1 or #2, do we agree to adopt Semantic 
>> Versionning?

>>

>> 

>>

>> Thanks,

>> Gildas

>> ONAP Release Manager

>> 1 415 238 6287

>>

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

>> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HANSEN,

>> TONY L

>> Sent: Wednesday, July 19, 2017 1:24 PM

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

>> Subject: Re: [onap-discuss] Versioning for Amsterdam

>>

>> Here’s my +1 as well for option 2. I also like Randa’s addition, but make 
>> sure you also add in “Prototype” or “PreRelease” or something along those 
>> lines for issues filed against the current pre-Amsterdam code base.

>>

>> Tony

>>

>> From: 
>> <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
>>  on behalf of "MAHER,

>> RANDA" <rx1...@att.com<mailto:rx1...@att.com>>

>> Date: Wednesday, July 19, 2017 at 3:43 PM

>> To: "TALASILA, MANOOP" 
>> <talas...@research.att.com<mailto:talas...@re

Re: [onap-discuss] Versioning for Amsterdam

[Gildas Lanilis]

To my knowledge, no decision was made on versioning.

If we go with option #2:

Questions:

1)   Who is maintaining the version dependency? Or ideally how to generate 
automatically that dependency graph?

2)   When we will deliver Amsterdam later in November, we are going to say: 
We are delivering Amsterdam Release 1.0.0 that embeds the following components: 
AAI version 2.0.3, AAF version 1.0.8, Clamp version 0.9.0. and so on. Are we 
comfortable with that approach?



3)   Independently of option #1 or #2, do we agree to adopt Semantic 
Versionning?


[cid:image003.jpg@01D30097.08B57DD0]

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 HANSEN, TONY L
Sent: Wednesday, July 19, 2017 1:24 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Versioning for Amsterdam

Here’s my +1 as well for option 2. I also like Randa’s addition, but make sure 
you also add in “Prototype” or “PreRelease” or something along those lines for 
issues filed against the current pre-Amsterdam code base.

Tony

From: 
>
 on behalf of "MAHER, RANDA" >
Date: Wednesday, July 19, 2017 at 3:43 PM
To: "TALASILA, MANOOP" 
>, 
"onap-discuss@lists.onap.org" 
>, "SPATSCHECK, 
OLIVER" >
Subject: Re: [onap-discuss] Versioning for Amsterdam

I would further propose an enhancement for Option 2:

All Jira project be updated to include a new field called Release Name and 
entries for that field be from a pull down menu that would include Amsterdam, 
Beijing, and any future release added when the name is determined. Further, 
that Affects Version and Fix Version be used to identify the version number in 
which an issue is found in and/or submitted in.

Having a separate Release Name Attribute in Jira will allow to easily build  
query to collect all the items being submitted for Amsterdam and we don’t have 
to worry about different version numbers being used across different projects 
for the same major release.

Randa

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of TALASILA, MANOOP
Sent: Wednesday, July 19, 2017 2:51 PM
To: onap-discuss@lists.onap.org; 
SPATSCHECK, OLIVER >
Subject: Re: [onap-discuss] Versioning for Amsterdam

+1 for option 2 (from Portal team)
Manoop

On Wed, Jul 19, 2017 at 11:06 AM -0400, "SPATSCHECK, OLIVER (OLIVER)" 
> wrote:

*** Security Advisory: This Message Originated Outside of AT ***.

Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.







On the OOM call the question of versioning came up and as this is a larger 
issue across projects David and I decided to bring it up with the larger 
community. I know we have discussed this before but I am not sure we made a 
final decision for Amsterdam (sorry if there was a decision I missed but nobody 
on the call was aware of any decision…).







The question is how to handle the fact that the seed code is tagged with 
different version numbers > 1 already.







There are really two options to fix that.







1. We try to keep the version numbers all in sync and in sync with the release 
number which will require “down versioning” some of the code with all the 
problems that will cause with dependencies and artifact caching. It will also 
be difficult to maintain as we are applying patches after the Amsterdam release 
is out (a patch to one component would trigger a version update to all other 
components).







2. We allow each repo to manage there own version number and then the Amsterdam 
release is just really a collection of artifacts with different version numbers 
properly tagged/referenced.







I think most people I talked to prefer 2.







Do we have consensus on this?







Does the TSC have to officially bless this?







Thx







Oliver


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

Re: [onap-discuss] Getting Release Engineering support

[Gildas Lanilis]

Hi Andy,

You have a very legitimate request.
I think it would help the community, if we could have a web interface to submit 
ticket. That will help the community to see what has already been submitted 
(and avoid duplicates) and track progress on resolution. 

Thanks,
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 Andrew Grimberg
Sent: Wednesday, July 19, 2017 7:57 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Getting Release Engineering support

Greetings folks,

I've been seeing a large uptick in unicast support requests directly to myself 
or myself and other LF Release Engineers.

As an reminder, the LF Release Engineering team does not work on support 
requests that are directed to our personal / corporate email. Support requests 
_must_ be directed at our helpdesk ticketing system by sending them to 
helpd...@onap.org

If we feel that the request / issue doesn't warrant being in a ticket we'll 
pull the discussion offline from the ticketing system, but that is where you 
should be starting for most things.

-Andy-

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation

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

[onap-discuss] [Release] Adoption of Commit Process Practices

[Gildas Lanilis]

Hi All,

During TSC Meeting on July 13 
TSC<https://wiki.onap.org/display/DW/TSC+July+13%2C+2017>, the TSC has approved 
a set of Development Best 
Practices<https://wiki.onap.org/download/attachments/3245207/ONAP-DevelopmentBestPractices.pdf?version=1=1499893335000=v2>.

One of them is in regards to the Commit Process which is defined in wiki at 
https://wiki.onap.org/display/DW/Commit+Messages

Key Points (among others) for you to keep in your radar:

1. It is now mandatory to establish a link from the Commit Message BODY 
to a Jira Issue ID. Linux Foundation is setting up a plugin to enforce this.

2. Do NOT have Jira Issue ID in the header

3. Header is 50 char max. Linux Foundation is setting up a plugin to 
enforce this

4. Body is 72 char max. Linux Foundation is setting up a plugin to 
enforce this
5.  Self-commits are NOT allowed. In other word, a committer cannot approve 
its own work
6.  NEVER embed jar, war, tar, gz, gzip, zip in Gerrit. This is a bad 
practice. In case your repo already contains such files, please take actions to 
remove them asap
7.  There are other practices describing the why and other do and don't, 
that I strongly encourage to 
read<https://wiki.onap.org/display/DW/Commit+Messages>.
These practices cannot all be enforced by a tool. In the quest of looking good 
and acting as a good citizens, it is expected the community will self-check and 
auto-regulate.

Wish you all the best commits for the Amsterdam Release.

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [coding guidelines] Python

[Gildas Lanilis]

Hi Seshu,

Thanks for reaching out.
Correct I have not provided any specific guidelines for Python.
However in wiki<https://google.github.io/styleguide/>,  Catherine and Tony have 
kindly provided recommendations on the Google Style guide at 
https://google.github.io/styleguide/
Using these guidelines for 
Python<https://google.github.io/styleguide/pyguide.html> is a certainly a good 
way to start with.

Hope this helps

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Seshu m
Sent: Monday, July 17, 2017 8:08 AM
To: onap-discuss@lists.onap.org; Gildas Lanilis <gildas.lani...@huawei.com>
Subject: [coding guidelines] Python

Hi Gildas,

Could you please help us understand if there are any speciifc coding 
guidelines/styles defined in ONAP for Python for R1.
We would be using Python in the SO for ARIA and required to get this clarified.

Best Regards,
Seshu
**
 This email and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained here in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #43020] ONAP wiki down

[Gildas Lanilis]

Systems are back operational.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Gildas Lanilis 
Sent: Thursday, July 13, 2017 11:31 AM
To: onap-discuss@lists.onap.org
Subject: FW: [ONAP Helpdesk #43020] ONAP wiki down

Hi,

FYI, ONAP Wiki, Jira and Gerrit are currently down.
Refer to ticket msg from LF below.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Thursday, July 13, 2017 11:18 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Subject: Re: [ONAP Helpdesk #43020] ONAP wiki down

On 07/13/2017 11:13 AM, Andrew Grimberg wrote:
> On 07/13/2017 11:09 AM, Gildas Lanilis via RT wrote:
> 
>> Hi,
>>
>> Looks like onap wiki is down:
>> [cid:image001.png@01D2FBC8.6D54A320]
> 
> Greetings Gildas,
> 
> The site is definitely not responding for me either. We haven't gotten 
> any alarms though which is a bit troubling.
> 
> I'm poking into it now.

Greetings Gildas,

Just an update. Our systems administration team updated our general Linux 
Foundation status page [0] with the following information just a few minutes 
ago.

--[cut]--
Investigating - We are investigating what we believe to be an issue with 
network/switching equipment in the PDX datacenter. Atmosera is currently 
"performing maintenance on the power systems at DC3, our downtown Portland 
datacenter" which was not supposed to affect any running systems. We are 
investigating and will update as soon as we learn more.

This affects any sites and infrastructure which are hosted at, or depend on 
services hosted in PDX. Primarily gerrit, git, wiki and jira systems.
--[/cut]--

So, the issue is with our DC provider.

[0] https://status.linuxfoundation.org/

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation


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

[onap-discuss] FW: [ONAP Helpdesk #43020] ONAP wiki down

[Gildas Lanilis]

Hi,

FYI, ONAP Wiki, Jira and Gerrit are currently down.
Refer to ticket msg from LF below.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, July 13, 2017 11:18 AM
To: Gildas Lanilis <gildas.lani...@huawei.com>
Subject: Re: [ONAP Helpdesk #43020] ONAP wiki down

On 07/13/2017 11:13 AM, Andrew Grimberg wrote:
> On 07/13/2017 11:09 AM, Gildas Lanilis via RT wrote:
> 
>> Hi,
>>
>> Looks like onap wiki is down:
>> [cid:image001.png@01D2FBC8.6D54A320]
> 
> Greetings Gildas,
> 
> The site is definitely not responding for me either. We haven't gotten 
> any alarms though which is a bit troubling.
> 
> I'm poking into it now.

Greetings Gildas,

Just an update. Our systems administration team updated our general Linux 
Foundation status page [0] with the following information just a few minutes 
ago.

--[cut]--
Investigating - We are investigating what we believe to be an issue with 
network/switching equipment in the PDX datacenter. Atmosera is currently 
"performing maintenance on the power systems at DC3, our downtown Portland 
datacenter" which was not supposed to affect any running systems. We are 
investigating and will update as soon as we learn more.

This affects any sites and infrastructure which are hosted at, or depend on 
services hosted in PDX. Primarily gerrit, git, wiki and jira systems.
--[/cut]--

So, the issue is with our DC provider.

[0] https://status.linuxfoundation.org/

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation




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

[onap-discuss] [Release] Release Management Update on reaching M1.

[Gildas Lanilis]

rces+and+Repositories>" wiki 
page.

For you convenience, here is the 
link<https://wiki.onap.org/display/DW/Presentations?preview=/3246513/6593134/ONAP-ReleasePlanningTraining.pdf>
 toward the training materials and the 
recording<https://wiki.onap.org/download/attachments/3246513/Release_Planning_Training.mp4?version=1=1497632945000=v2>
 I made last week to reach M1.

Last but not least, if you have any questions or concerns feel free to reach 
out (phone, email, irc, hangout, wechat, snapchat, skype, viber,...) I will be 
glad to help.


Thanks,
Gildas

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

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

Re: [onap-discuss] Invitation: Release Planning Requirements @ Thu Jun 15, 2017 6pm - 7pm (PDT) (onap-discuss at lists.onap.org)

[Gildas Lanilis]

Hi DeWayne,

Here you go https://wiki.onap.org/display/DW/Presentations
Training is labeled Release Management Training

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

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 DeWayne Filppi
Sent: Tuesday, June 20, 2017 2:56 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Invitation: Release Planning Requirements @ Thu Jun 
15, 2017 6pm - 7pm (PDT) (onap-discuss at lists.onap.org)

This session was going to be recorded and a link placed in the wiki.  I 
couldn't find it.  Was it done?

DeWayne

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

Re: [onap-discuss] [onap-tsc] 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-discuss@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-discuss@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-discuss@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-discuss] List of ONAP Docker Images

[Gildas Lanilis]

Hi,

I just discussed this with Andy at LF.
As we speak Nexus is supporting both org.openecomp and org.onap. So there is no 
urgency to make the shift.
As we have so many other things to do, we may wait until M2 to make it happen.

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 ROSE, DANIEL V
Sent: Friday, June 16, 2017 1:53 PM
To: Gary Wu; Viswa KSP
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] List of ONAP Docker Images

It is on everyone’s radar and was discussed at the may F2F but I don’t think 
there was a timeline yet because it will be disruptive for a bit. Timeline will 
probably have to come from the TSC due to all the cross project impacts. Maybe 
bring it up in the tsc list if you think its important Viswa.

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

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: Friday, June 16, 2017 11:20 AM
To: Viswa KSP 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] List of ONAP Docker Images

My understanding is that all the docker image names will be changed to onap.  
In addition, all the Java artifacts will have groupIds and package names 
changed to org.onap as well.  I’m not sure what the timeline is on either of 
these items.

Thanks,
Gary

From: Viswa KSP [mailto:kspviswa.git...@gmail.com]
Sent: Friday, June 16, 2017 2:31 AM
To: Gary Wu >
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] List of ONAP Docker Images

Is there a proposal to standardize docker parent repo to just onap ? ( Cos I 
can see bunch of docker parents such as onap, openecomp, dcae, aai etc ).

BR,
Viswa

On Fri, Jun 16, 2017 at 4:14 AM, Gary Wu 
> wrote:
Hi PTLs,

I am compiling a list of all the ONAP Docker images in a spreadsheet (CSV):

https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=packaging/docker/docker-images.csv;h=9bac826b024ed76fb991ea3694ca39a669f53bbe;hb=refs/heads/master

Please take a look and see if there is anything missing or incorrect for your 
respective projects.  In particular, please let me know if there are any 
planned changes for Release 1.

Please feel free to submit any changes directly via Gerrit, or you may email me 
and I’ll change it for you.

Thanks,
Gary



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

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

[onap-discuss] [releng] Next steps to Reach M1

[Gildas Lanilis]

Hi All,

This message is to the attention of all Project Primary Contacts or future PTLs 
(to be elected shortly) and related to the next steps to reach M1 Release 
Planning milestone (planned for June 29).

Earlier this week, Chris Donley made a presentation on "ONAP Project Roles and 
Responsibilities<https://wiki.onap.org/display/DW/Presentations?preview=/3246513/6592765/ONAP-Project%20Roles%20v1.pdf>"
 and myself presented "Getting to M1 Release 
Planning<https://wiki.onap.org/display/DW/Presentations?preview=/3246513/6593134/ONAP-ReleasePlanningTraining.pdf>".

The "Getting to M1 Release Planning" explains what is expected from you (the 
primary Contact or future PTL) to reach M1.
In a nutshell you have to:
1.   Fill out the "Release Planning Template"
2.   Fill out The "Release Planning Checklist"
3.   AND MOST critical NOW review and complete the "Resources & 
Repositories<https://wiki.onap.org/display/DW/Resources+and+Repositories>" wiki 
page.

The "Resources & Repositories" page is the central place used to document all 
repos (with repos name, maven ID and repo description) pertaining to ONAP.
Please review the data. When populating the table from the Projects proposal, I 
noticed that for some repos the description is missing, other repo are not 
clearly defined and still have some "?".
Also complete the committers list by adding the missing information such as 
LFID and location.

Let me know if you have any questions.
Furthermore, let myself and Kenny Paul know when you are done with the 
"Resources & Repositories" work. Kenny can further assist you to finalize the 
creation of the repos and Jira projects.

Thanks,
Gildas

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

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

Re: [onap-discuss] [onap-tsc] ONAP Release Naming Framework Election Has Concluded - Global Cities Wins

[Gildas Lanilis]

Hi Lisa,

I understand the concerns you brought up. However, we need your immediate 
recommendations regarding the naming of our first release “Anchorage” or 
“Amsterdam”.
This is critical as we are using these names while discussing Release plan and 
in our tool chain.

[cid:image001.jpg@01D2E370.AA134E80]

Thanks,
Gildas

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

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Lisa Caywood
Sent: Wednesday, June 07, 2017 10:20 AM
To: Phil Robb
Cc: onap-discuss@lists.onap.org; onap-tsc
Subject: Re: [onap-tsc] ONAP Release Naming Framework Election Has Concluded - 
Global Cities Wins

For the record, Marketing had two concerns with Cities:

1) OpenStack also uses some cities, so we would need to ensure that our names 
do not overlap with theirs.

2) Visual elements (for launch banners and other branding assets) - many cities 
look like other big cities. We would want to ensure that each city picked has a 
widely recognized landmark to anchor on.

Obviously both of these are very manageable, just things to be aware of.

Regards, Lisa

On Wed, Jun 7, 2017 at 3:17 AM, Phil Robb 
<pr...@linuxfoundation.org<mailto:pr...@linuxfoundation.org>> wrote:
Hello All:

The Release Naming Framework election has concluded and the winner is "Global 
Cities".
Result detailsHide details




1

2

3

4

5

1. Global Cities



-

106

117

130

147

2. Scientists



99

-

111

131

132

3. Music Composers



87

82

-

108

131

4. Philosophers



74

51

81

-

116

5. Zodiac Signs



55

62

63

73

-


Before we make it official, we need to run the idea by the Marketing Folks to 
make sure they have no issues with it.

I'll keep you posted.

Thanks to all of those folks that voted.  We had 210 votes all told.

Best,

Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949<tel:(970)%20229-5949>
(M) 970-420-4292<tel:(970)%20420-4292>
Skype: Phil.Robb

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



--
Lisa Caywood
Director of Ecosystem Development | OpenDaylight Project | 
lcayw...@opendaylight.org<mailto:lcayw...@opendaylight.org> | +1 408 857 3642
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP RELEASE MANAGER ELECTION] Call For Nominations

[Gildas Lanilis]

Dear ONAP TSC,

I am motivated to serve as ONAP’s Release Manager to support the on-time 
delivery of our releases. In this role, I will focus my energy on developing a 
Release framework (templates, tools, processes) so the ONAP community can 
deliver on time.

Over the past year, I served as OPEN-O’s Release Manager, where we delivered 
two on-time releases.  I understand what is necessary to support open source 
simultaneous releases.  I can dedicate 100% of my time to serve as the Release 
Manager and work hand in hand, transparently and openly, with the TSC’s 
members, the PTL’s and all the community with the only objective for all of us 
to be successful. I will help to remove roadblocks and report status to the 
community. I have also been working on LF cross-project harmonization efforts, 
and if elected, will continue to work with the respective communities on a 
common CI/CD toolchain.

I have over 20 years of industry experience, including 7 years as a developer, 
in delivering great software that helps people in their life. I am a strong 
supporter of Lean and Agile practices that have helped me as:

· OPEN-O Release Manager, delivering as planned, on time 2 Open Source 
OPEN-O releases

· Enterprise Software Release Manager,  adopting a 4 months release 
cycle to launch multiple releases to key customers

· Director Development Best Practices, leading a R and Product 
Management department adopting Agile practices and resulting to a CMMI Level 3 
certification

Thanks you for your trust and support.
Gildas

Bio:

Gildas joined Huawei in 2016 as the OPEN-O Release Manager and is based in 
Santa Clara, CA, USA. In his role Gildas is running the delicate art of getting 
things done without formal authority.

Gildas is  coming from Virtual Hold Technology, where he served as Director of 
Release Management and DevOps Manager for Cloud Applications.

Gildas is a vivid Agile supporter and served at Genesys to lead the 
introduction of modern development practices and inspired R teams to deliver 
great software.

When he is not running, Gildas enjoys life with his family and cheers up his 
kids on the San Francisco Bay Area soccer fields or on the sideline of a 
swimming event. And when comes time to celebrate, nothing better than 
Champagne, French of course.

[Gildas.png]

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
Release Management
gildas.lani...@huawei.com
Mobile: 1 415 238 6287

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Wednesday, May 31, 2017 2:48 PM
To: onap-tsc; onap-discuss@lists.onap.org
Subject: [onap-discuss] [ONAP RELEASE MANAGER ELECTION] Call For Nominations

Hello ONAP Community Members:

Please consider this email as the kickoff of the ONAP Release Manager Election 
process.  A description of the role can be found on the ONAP Release Manager 
Election (2017) page here: 
https://wiki.onap.org/pages/viewpage.action?pageId=6589452

Any member of the technical community is eligible to run for this position.  It 
is not exclusively reserved for TSC Members.  However, only TSC members are 
eligible to vote when choosing among the potential candidates.  This position 
serves at the pleasure of the TSC.

There are two phases to the election process.  The first is the Nomination 
Phase where community members may nominate themselves for the position of "ONAP 
Release Manager".  Once the Nomination Phase has concluded, we will enter the 
Election Phase, where all ONAP TSC Members are invited and encouraged to vote 
on the candidates whom have been nominated.

Timing:
•   Nominations open May 31st, 2017.
•   Nominations close June 7th at 9:00pm Pacific Time
•   Voting begins June 8th, 2017
•   Voting Ends June 15th, 2017 at 9:00pm Pacific Time

If you wish to nominate yourself for the position of "ONAP Release Manager", 
please respond-all to this email indicating your interest to stand for election.

All nominees are invited to provide their Picture, Biography, and Statement of 
Intent on the election wiki page so that members of the TSC, and the community, 
can learn more about the candidate and their intentions for the role of Release 
Manager. The nominee ordering on the election wiki page will be in ascending 
alphabetical order by last name.

If you have any questions, please do not hesitate to contact me.

Best,

Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Technical Deep Dive on Tuesday May 2nd

[Gildas Lanilis]

Hi Eric,

I guess you are referring to the Wednesday Deep Dive session.
I see a lot of Materials published in wiki at 
https://wiki.onap.org/display/DW/Parallel+Session+Completed+Templates

Hope it helps.

Thanks,
Gildas

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of eric.deb...@orange.com
Sent: Tuesday, May 09, 2017 5:51 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Technical Deep Dive on Tuesday May 2nd

Hello

I would like to know where we can find the cool slide sets presented last week 
during the ONAP Project Developer Event and especially for the Tuesday deep 
dive session (APP-C, SDC, AAI).

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-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Proposal for list split of onap-discuss

[Gildas Lanilis]

Let me share my experience with mailing list per project:
Even though developers requested for specific mailing list, they hate it. Why:

1.   They had to register in all the mailing lists. Too cumbersome.  So 
most of them did not register

2.   As they did not register in mailing list, other folks took the habit 
to add them separately in To or Cc. And then the Moderator?s misery started.

3.   The list of folks added separately to the mailing list grew quickly 
and hit the max allowed by Linux Foundation (10 recipients). Thus requiring the 
Moderator to review and accept the message. Impact: delay on the responses.

4.   As the folks were not systematically in the mailing list but still 
used it (by pressing Reply All), by policy (to avoid spam) Linux Foundation 
requested the Moderator to again review and accept the message. Impact: delay 
on the responses.

I start liking the Topic. It requires a bit of discipline but it makes things 
working better for all who can enjoy the art of filtering.

Thanks,
Gildas

From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of SULLIVAN, BRYAN L
Sent: Thursday, April 20, 2017 11:38 AM
To: Ed Warnicke; Andrew Grimberg
Cc: onap-discuss
Subject: Re: [onap-discuss] Proposal for list split of onap-discuss

The flip side (just to be considered in the supporting infra) is that it?s not 
hard for projects to become disconnected when segregated. Needing/managing many 
project email list subscriptions inhibits the ability to easily keep an 
overview of how things are progressing across projects. Of course at some 
point, the firehose becomes unmanageable and the demands of focus require 
segregation.

But some infra support can address the limitations of project-specific lists:

-  Mail subscription system (e.g. http://lists.onap.org) support for a 
?auto-subscribe to all? option for those who want it.

-  Mail archive system that supports an effective search, e.g. the W3C 
system: https://www.w3.org/Search/Mail/Public/

o   Mailman is woefully inadequate for this. Some services exist that could 
possibly be used for this, e.g. http://openstack.markmail.org/search/?q= works 
well for me, for OpenStack in general.

o   Note that you can also just subscribe using some email service ala Gmail or 
Hotmail, that provides a search feature that works for you. That can completely 
solve your corporate inbox issue, given that you?re allowed to use 
non-corporate email services for open source work.

If we want to create project-specific lists, I recommend that the LF work on 
the two supporting infra capabilities above, or include workarounds such as 
above in developer intros/FAQs.

Thanks,
Bryan Sullivan | AT

From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ed Warnicke
Sent: Thursday, April 20, 2017 10:46 AM
To: Andrew Grimberg 
Cc: onap-discuss 
Subject: Re: [onap-discuss] Proposal for list split of onap-discuss

I hit a situation just yesterday where there was literally no reasonable way to 
address a sub-community of openstack because they have
a giant monster mailer, and thus there was no reasonable way to address the 
interested subcommunity.

Monster mega lists suppress conversation.  Give each project their own space 
for their community to talk.

Ed

On Thu, Apr 20, 2017 at 10:34 AM, Andrew Grimberg mailto:agrimberg at linuxfoundation.org>> wrote:
On 04/20/2017 09:46 AM, Ed Warnicke wrote:
> Josef,
>
> I couldn't agree more.  Typically 'discuss' in most communities is for
> 'cross project' discussion.  Project specific converstions tend to happen on
> ${project}-dev mailers (think dcae-dev, sdnc-dev, etc).   For this to
> work, one needs projects.  Projects *need* their own space to hold
> publicly visible conversations.
>
> I would strongly recommend *against* a single list in the long term.  It
> becomes overwhelming, and it strongly discourages folks sending email
> because the room is so big.

Our largest communities have major cross-posting problems along with new
people regularly informing us that they don't know where to send things
because of having too many lists. As such, I can't express how strongly
I recommend only breaking out a specific topic to a separate list _iff_
it proves to cause too much traffic on the general list.

As Aimee pointed out OpenStack, which is a community larger than our
largest community, doesn't do what you're talking about. They use topics
on their lists precisely to get around the mailing list explosion of a
list per project that you're suggesting.

-Andy-

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation

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

[onap-discuss] Support ONAP on multiple OS/Openstacks?

[Gildas Lanilis]

Thanks Catherine for bringing this up.

+1 for defining upfront OSs and their versions.
For Openstack, I would like to suggest as clearly name upfront the series ONAP 
has to support. That will avoid confusion and potential waste of effort.
For instance, Newton is planned to EOL [0] on 2017-10-11. Shall we Yes/No 
Support it?

[0] https://releases.openstack.org/

Thanks,
Gildas

From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine
Sent: Thursday, April 20, 2017 1:41 AM
To: onap-discuss at lists.onap.org
Subject: [onap-discuss] Support ONAP on multiple OS/Openstacks?

Good morning all,

I would like to start a new thread in order to understand if there is a need to 
certify ONAP on multiple OS/Openstacks.

OS
Currently ONAP is running on Ubuntu 14.04 (target to move to Ubuntu 16.04).
Open-O is running on CentOS but I understand from Helen Yunxia (Huawei) that it 
should not be an issue to run it on Ubuntu.
Redhat was not considered from a certification perspective due to license cost.

>From an architecture perspective, it is important that ONAP remains OS agnostic
The only constraint on the OS is that it should support an Openstack version

OpenStack
I have noticed that people are trying to deploy ONAP using different OpenStack 
release series (i.e. Icehouse, Mitaka, Ocata, Kilo, etc)
Although I would like to recommend that we only focus on the release series 
that are not EOL or will be soon EOL as an Openstack baseline for ONAP,
We should collect what has already been validated by the ONAP community and 
what they agree to support

Any additional thoughts?

Best regards
Catherine

Catherine Lef?vre
AT Software Development & Engineering
D2 Platform & Systems Development
AVP - ECOMP/ONAP/RUBY/SPP


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

TEXTING and DRIVING... It Can Wait

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



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

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