Re: [onap-discuss] [integration][sdc] SDC images

[Catherine LEFEVRE]

Thank you so much Michael !

From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Monday, November 26, 2018 11:39 PM
To: Lando,Michael ; Jessica Wagantall 
; Yunxia Chen 
Cc: onap-discuss@lists.onap.org; Lefevre, Catherine 
; FREEMAN, BRIAN D ; Yang Xu 
(Yang, Fixed Network) 
Subject: RE: [integration][sdc] SDC images

Thanks Michael for the update. I guess you can sleep now. Jess will keep us 
posted when the images are released.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Lando,Michael [mailto:michael.la...@intl.att.com]
Sent: Monday, November 26, 2018 2:35 PM
To: Jessica Wagantall 
mailto:jwagant...@linuxfoundation.org>>; Yunxia 
Chen mailto:helen.c...@huawei.com>>
Cc: onap-discuss@lists.onap.org; Gildas 
Lanilis mailto:gildas.lani...@huawei.com>>; Lefevre, 
Catherine 
mailto:catherine.lefe...@intl.att.com>>; 
FREEMAN, BRIAN D mailto:bf1...@att.com>>; Yang Xu (Yang, Fixed 
Network) mailto:yang@huawei.com>>
Subject: RE: [integration][sdc] SDC images

Hi,

Yes I have created the dockers.
https://jenkins.onap.org/view/sdc/job/sdc-casablanca-docker-version-java-daily/17/console

and if Jessica can help me with creating the release ONAP Helpdesk #64352
they will be in your hands as soon as she is done 

> onap/sdc-kibana
>
> onap/sdc-elasticsearch
>
> onap/sdc-init-elasticsearch
>
> onap/sdc-cassandra
>
> onap/sdc-cassandra-init
>
> onap/sdc-onboard-cassandra-init
>
> onap/sdc-onboard-backend
>
> onap/sdc-backend
>
> onap/sdc-backend-init
>
> onap/sdc-frontend
>
> onap/sdc-api-tests
>
> onap/sdc-ui-tests










BR,

[Michael Lando]

AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com

From: Jessica Wagantall 
mailto:jwagant...@linuxfoundation.org>>
Sent: Monday, November 26, 2018 23:03
To: Yunxia Chen mailto:helen.c...@huawei.com>>
Cc: Lando,Michael 
mailto:michael.la...@intl.att.com>>; 
onap-discuss@lists.onap.org; Gildas Lanilis 
mailto:gildas.lani...@huawei.com>>; Lefevre, 
Catherine 
mailto:catherine.lefe...@intl.att.com>>; 
FREEMAN, BRIAN D mailto:bf1...@att.com>>; Yang Xu (Yang, Fixed 
Network) mailto:yang@huawei.com>>
Subject: Re: [integration][sdc] SDC images

I wonder if he refered to 
https://jenkins.onap.org/view/sdc-sdc-tosca/job/sdc-sdc-tosca-master-release-version-java-daily/1/console

This is the one I released this morning

thanks1
Jess

On Mon, Nov 26, 2018 at 12:59 PM Yunxia Chen 
mailto:helen.c...@huawei.com>> wrote:
Hi, Michael,

I know you have been worked so hard. But I still have to ask: have you released 
the image we talked this morning? Need it for retesting stability. If not yet, 
could we do the same thing as SO image just document it? Please let us know.

Regards,
Helen Chen

Principal Architect, Open Orchestration
Huawei US R Center
Futurewei Technologies, Inc.

2330 Central Expressway, C2-16
Santa Clara, CA 95050
Tel: (408) 330-4696
Cell: (510) 825-7348

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

View/Reply Online (#14067): https://lists.onap.org/g/onap-discuss/message/14067
Mute This Topic: https://lists.onap.org/mt/28325355/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] Update S3P for TSC

[Catherine LEFEVRE]

I am adding the Security Subcommittee to this thread who is currently reviewing 
these requests.

Envoyé de mon iPad 

Le 22 nov. 2018 à 22:35, OBRIEN, FRANK MICHAEL 
mailto:frank.obr...@amdocs.com>> a écrit :

Gildas,
   Yes, I knew about the Sonatype nexus-iq licensing terms – that single 
commercial tool is dictating how we work in public.
   There is a couple TSC issues we need to move forward on these I raised in 
the past – I’ll repost and get opinions from the other PTLs – in the case we 
proceed or keep the status quo

Discuss open source alternatives to NIST CVE search/identification – avoiding 
Sonatype
https://jira.onap.org/browse/TSC-32

Expand access to private CLM pages
https://jira.onap.org/browse/TSC-59

Expand access to nexus-iq
https://jira.onap.org/browse/TSC-49


Just an fyi – there are discrepancies between the private and public spaces – 
just checking in case this is for some criteria and this 6/8 diff means 
something.

6 projects that have no public scrubbed versions including mine – hence the 
possible confusion below
8 have a public scrubbed version but no private detailed version

Exists privately but not publicly
AAI
Logging
MSB
POMBA
SDC
SDNC

Exists publicly but not privately
DMaaP
CLAMP
DCAE
MultiVIM
MUSIC
OOF
VNFSDK
VVP

I’ll create Logging and POMBA on the public side and leave the rest to the 
other PTL’s

Thank you
/michael




From: Gildas Lanilis 
mailto:gildas.lani...@huawei.com>>
Sent: Wednesday, November 21, 2018 4:53 PM
To: Michael O'Brien mailto:frank.obr...@amdocs.com>>; 
ZWARICO, AMY mailto:az9...@att.com>>; 
onap-discuss@lists.onap.org
Cc: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; 
pawel.pawl...@orange.com; Kenny Paul 
mailto:kp...@linuxfoundation.org>>
Subject: RE: Update S3P for TSC

Hi Michael,

We has some licensing compliance with the tool we are using for the scan.
To circumvent the issue, we had to create a restricted to committers wiki space 
that embeds the “Artifact”, “Version”, and “Problem Code”. This helps committer 
to track exactly their issue.

For general audience, SECCOM team created an open to everyone, curated wiki 
page without the labeled “Artifact”, “Version”, and “Problem Code”. RN is 
ReadTheDocs will point toward the curated wiki page.

Hope this help.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Michael O'Brien [mailto:frank.obr...@amdocs.com]
Sent: Wednesday, November 21, 2018 4:48 AM
To: ZWARICO, AMY mailto:az9...@att.com>>; Gildas Lanilis 
mailto:gildas.lani...@huawei.com>>; 
onap-discuss@lists.onap.org
Cc: Stephen Terrill 
mailto:stephen.terr...@ericsson.com>>; 
pawel.pawl...@orange.com; Kenny Paul 
mailto:kp...@linuxfoundation.org>>
Subject: RE: Update S3P for TSC

Still a wip in my queue along with other work – I have almost finished details 
on the last couple ones for sdnc-context-builder – I find copying from the 
nexus-iq sections to this security page extremely tedious – figuring out each 
exploit and recommending a compensating control not in (upgrade to the latest, 
use an alternate) is going to take some time – especially with the pomba code 
and with re-integration testing - in hind sight I should have just labeled 
everything with an ignore action like some of the other teams.


I don’t understand what this issue is with the columns and links – the security 
page is not accessible to the public – hence why no one except committers can 
access the page.

  1.  Remove the columns labeled “Artifact”, “Version”, and “Problem Code”. 
This are fields that cannot be publicly accessible per the license.

I followed the existing template – there are other pages like a random pick 
below that contain these columns and links.
Are you saying that the logging page needs to be different from the rest of onap

https://wiki.onap.org/pages/viewpage.action?pageId=43387665

Re: [onap-discuss] Meaning of empty value in JIRA fixVersion?

[Catherine LEFEVRE]

Good morning Keong,



The affectedversion is a mandatory field because it determines when the 
Epic/Task/User Story/Bug/Sub-Task has been created/identified.

The fixversion is optional because it will depend on when the project team will 
plan its implementation.



Nevertheless I agree with you that any remaining "Highest/High" defect should 
have a fixversion.

I understand that our ONAP Release Manager is currently tracking any bug with 
no fix version and with a fixversion set to Amsterdam/Beijing or Casablanca 
Release.



I would recommend that each PTL review their JIRA backlog (Epic/Task/User 
Story/Bug/Sub-Task).

They should make an assessment if any Epic/Task/User Story/Bug/Sub-Task is 
still relevant in the context of the Dublin release or any future release.



Remaining Items – JIRA Query:

status != Closed AND status != Done AND project != "Sandbox Project" AND 
project != CI-Management AND project != "ONAP TSC"  ORDER BY priority DESC, 
updated DESC



Please note that we have already closed 16802 JIRA Items (Epic/Task/User 
Story/Bug/Sub-Task) since ONAP inception !



Best regards

Catherine



-Original Message-
From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Keong Lim
Sent: Friday, November 23, 2018 2:05 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Meaning of empty value in JIRA fixVersion?



Hi all,



While browsing through open cases in JIRA, it seems that for unresolved cases, 
the fixVersion is used as a forward-looking plan / prediction for when it will 
be closed and, for resolved cases, it is documentation of the actual version 
when it was closed.



But sometimes the fixVersion field is left empty. What is the meaning of 
fixVersion that is empty?



When building the JIRA query, the UI will prompt with some potential values 
which includes "Future" (apparently nothing has been defined yet for releases 
beyond "El Alto"), so is an empty value synonymous with "Future"?



Are these cases being accidentally ignored? There are over 1000 unresolved 
cases with empty fixVersion, including some Bugs that are "Highest" and "High".



Should fixVersion be a mandatory field in JIRA, i.e. not left as empty value?



The wiki 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Tracking-2BIssues-2Bwith-2BJIRA=DwIFaQ=LFYZ-o9_HUMeMTSQicvjIg=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU=ZKi9UZYxSu9ew7aKav4i41YrwmLPPoaLE1ymxqlNalM=wZLk9t5WdQ0Wem33SBmEIGDKfXcRegVBZbzsOSmK7zI=
 does not cover this case of fixVersion left empty.





Thanks,

Keong







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

View/Reply Online (#14004): https://lists.onap.org/g/onap-discuss/message/14004
Mute This Topic: https://lists.onap.org/mt/28290136/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] vFW CDS - die preload die!

[Catherine LEFEVRE]

Thank you Alexis for sharing. Great Team Effort - Well Done !

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

View/Reply Online (#13987): https://lists.onap.org/g/onap-discuss/message/13987
Mute This Topic: https://lists.onap.org/mt/28286761/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-release] Update Docker Release Images

[Catherine LEFEVRE]

Perfect - thank you
You might want to combine Manifest request from Gary?

Best regards
Catherine

From: onap-rele...@lists.onap.org [mailto:onap-rele...@lists.onap.org] On 
Behalf Of gildas.lani...@huawei.com
Sent: Thursday, November 15, 2018 9:04 PM
To: Lefevre, Catherine ; 
onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Subject: Re: [Onap-release] Update Docker Release Images

Yes I can.
I will update every day at same time as the daily bug report.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: Lefevre, Catherine [mailto:catherine.lefe...@intl.att.com]
Sent: Thursday, November 15, 2018 11:50 AM
To: onap-discuss@lists.onap.org; Gildas 
Lanilis mailto:gildas.lani...@huawei.com>>; 
onap-rele...@lists.onap.org
Subject: RE: Update Docker Release Images

Good evening Gildas,

Will you give us a daily status?

Many thanks & regards
Catherine

From: onap-discuss@lists.onap.org 
[mailto:onap-discuss@lists.onap.org] On Behalf Of 
gildas.lani...@huawei.com
Sent: Thursday, November 15, 2018 12:14 AM
To: onap-discuss@lists.onap.org; 
onap-rele...@lists.onap.org
Subject: [onap-discuss] Update Docker Release Images

Hi PTLs,

I have done an analysis on the latest Docker Images released.
The date below is the date the latest Docker image has been released (according 
to git history in 
manifest-docker.csv
 file). For the projects highlighted in red, since the release's date there are 
some "Highest" and "High" priority Jira defects that have been fixed and thus 
these projects must release a new Docker Image.

New Docker Images are due by COB on Thursday, Nov 15. For the red projects, let 
me know if you are on track to make it.

[cid:image003.jpg@01D47D2A.D01FCB30]

Thanks,
Gildas

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



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

View/Reply Online (#13771): https://lists.onap.org/g/onap-discuss/message/13771
Mute This Topic: https://lists.onap.org/mt/28151634/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] Update Docker Release Images

[Catherine LEFEVRE]

Good evening Gildas,

Will you give us a daily status?

Many thanks & regards
Catherine

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of gildas.lani...@huawei.com
Sent: Thursday, November 15, 2018 12:14 AM
To: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Subject: [onap-discuss] Update Docker Release Images

Hi PTLs,

I have done an analysis on the latest Docker Images released.
The date below is the date the latest Docker image has been released (according 
to git history in 
manifest-docker.csv
 file). For the projects highlighted in red, since the release's date there are 
some "Highest" and "High" priority Jira defects that have been fixed and thus 
these projects must release a new Docker Image.

New Docker Images are due by COB on Thursday, Nov 15. For the red projects, let 
me know if you are on track to make it.

[cid:image003.jpg@01D47D24.CAD701D0]

Thanks,
Gildas

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



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

View/Reply Online (#13769): https://lists.onap.org/g/onap-discuss/message/13769
Mute This Topic: https://lists.onap.org/mt/28140552/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] [SO][AAF] AAI request gets Unauthorized

[Catherine LEFEVRE]

Dear all,
Are you testing this on SB04?
I understand this is the only lab that is current fort the moment.
If you are testing in another lab then you will need to replicate similar SB04 
settings

Good morning Jonathan,
Can you please look at this issue with Jimmy?

Best regards
Catherine

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Guangrong Fu
Sent: Tuesday, October 30, 2018 9:59 AM
To: parou...@objectify.sk
Cc: onap-discuss@lists.onap.org; adetalhoue...@gmail.com
Subject: 答复: Re: 答复: [onap-discuss] [SO][AAF] AAI request gets Unauthorized


I'm having this issue on the instance deployed in the DCAE tenant.








原始邮件
发件人：PavelParoulek mailto:parou...@objectify.sk>>
收件人：onap-discuss 
mailto:onap-discuss@lists.onap.org>>;
抄送人："Alexis de Talhouët" 
mailto:adetalhoue...@gmail.com>>;onap-discuss 
mailto:onap-discuss@lists.onap.org>>;
日 期 ：2018年10月30日 16:25
主 题 ：Re: 答复: [onap-discuss] [SO][AAF] AAI request gets Unauthorized
Hi, on what instance/environment do you experience this problem?


 On Tue, 30 Oct 2018 09:20:53 +0100  Guangrong 
Fumailto:fu.guangr...@zte.com.cn>> wrote 


Same issue here. Could anybody help?








原始邮件
发件人：AlexisdeTalhouet mailto:adetalhoue...@gmail.com>>
收件人：onap-discuss 
mailto:onap-discuss@lists.onap.org>>;
日 期 ：2018年10月30日 04:42
主 题 ：[onap-discuss] [SO][AAF] AAI request gets Unauthorized
Team,
Are they some configuration that should be updated regarding SO to AAI 
communication since AAI integrated with AFF?

I’m facing an Unauthorized for my service request. Bellow a snippet of the BPMN 
logs:

```
18-10-29T20:23:26.705Z|6d5938d9-9f3c-4c5a-82b3-9d86c1720aec| 
o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Making GET request to: 
https://aai.onap:8443/aai/v14/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFW/service-instances?depth=2=Service_Ete_Nameedbd0170-f5ac-487f-b044-305f73045e74
 Request Headers: {Authorization=[Basic TVNPOk1TTw==], X-FromAppId=[MSO], 
X-TransactionId=[], Accept=[application/json], 
X-ONAP-RequestID=[6d5938d9-9f3c-4c5a-82b3-9d86c1720aec], 
X-ONAP-InvocationID=[1e70e4b5-7709-48e8-971b-c53ba402a0c9], 
X-ONAP-PartnerName=[SO]} 
2018-10-29T20:23:27.043Z|6d5938d9-9f3c-4c5a-82b3-9d86c1720aec| 
o.o.so.logging.jaxrs.filter.PayloadLoggingFilter - Response from GET: 
https://aai.onap:8443/aai/v14/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFW/service-instances?depth=2=Service_Ete_Nameedbd0170-f5ac-487f-b044-305f73045e74
 Response Headers: {connection=[close], Date=[Mon, 29 Oct 2018 20:23:26 GMT], 
Strict-Transport-Security=[max-age=1600; includeSubDomains; preload;], 
WWW-Authenticate=[Basic 
realm="people.osaaf.org"]}{"requestError":{"policyException":{"messageId":"POL3300","text":"Unauthorized
 (msg=%1) (ec=%2)","variables":["Unauthorized","ERR.5.1.3300"]}}}  
2018-10-29T20:23:27.154Z|6d5938d9-9f3c-4c5a-82b3-9d86c1720aec| 
o.o.s.b.i.workflow.tasks.WorkflowAction - WorkflowAction was unable to verify 
if the instance name already exist in AAI.

Thanks,
Alexis








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

View/Reply Online (#13374): https://lists.onap.org/g/onap-discuss/message/13374
Mute This Topic: https://lists.onap.org/mt/27790419/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] Problem with JIRA search results

[Catherine LEFEVRE]

Dear LF Helpdesk,

I believe the Nexus issue is now solved
Can you consider this issue as your next top priority?

Many thanks & regards
Catherine

-Original Message-
From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Jack Morgan
Sent: Friday, October 05, 2018 5:39 PM
To: onap-discuss@lists.onap.org; DRAGOSH, PAM ; 
stephen.go...@windriver.com; keong@huawei.com
Subject: Re: [onap-discuss] Problem with JIRA search results

It looks like JIRA was migrated to AWS last night per the announcement below. 
Perhaps, the database needs to be re-indexed?

https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_g_onap-2Dtsc_message_3835=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=ZglJ8LOeAfevY7wWaSximhFMAzXaMdza5QYCg-DW6SU=j7UAfwncRM_PZQ2Pj615zNpeYMxdDFIanKRPKtbIRgw=q_T9ZB-cVDZec3B3ic6sLmGOyGNukAzjs7NKIS2W7Co=

On 10/5/18 6:26 AM, Pamela Dragosh wrote:
> Its inconsistent – a lot of previously closed JIRA’s now show up on my board 
> and I can’t find ones that are currently open.
>
> Pam
>
> On 10/5/18, 8:56 AM, "onap-discuss@lists.onap.org on behalf of Gooch, 
> Stephen"  stephen.go...@windriver.com> wrote:
>
>  Jira is definably misbehaving.   I cannot find open tickets assigned to 
> my account.
>  
>  - Stephen
>  
>  -Original Message-
>  From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] 
> On Behalf Of Keong Lim
>  Sent: Friday, October 05, 2018 03:42
>  To: onap-discuss@lists.onap.org
>  Subject: [onap-discuss] Problem with JIRA search results
>  Sensitivity: Confidential
>  
>  Hi Jessica,
>  
>  Just a few minutes ago, I used this query on ONAP JIRA:
>  
> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_iss
> ues_-3Fjql-3Dissuetype-2520-253D-2520Bug-2520AND-2520priority-2520in-2
> 520-28Medium-29-2520AND-2520status-2520-253D-2520Open-2520ORDER-2520BY
> -2520createdDate-2520DESC=DwIFAg=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcE
> j6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=Uvlt9VGF1JRGYAGjb7EBSntceXuBnEMb
> SI3Qq1mWjIg=QoS4GNGozbgIKUP229K4u5iH7Y67ZYTdCYeo3zT7o6k=
>  
>  and noticed that the search results were mismatched to the JIRA issue 
> itself, e.g. 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_AAI-2D1665=DwIFAg=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=Uvlt9VGF1JRGYAGjb7EBSntceXuBnEMbSI3Qq1mWjIg=dUpIoBWLLCdav02dqWGAyPtxrlwXEWSGoU2L-ymiVps=
>  i.e. the status, resolution, updated date, resolved date are all 
> mismatched values.
>  
>  See also attached annotated screenshot.
>  
>  Could you please check if the JIRA instance needs re-indexing or some 
> other maintenance to get the search results up-to-date again?
>  
>  
>  Thanks,
>  Keong
>  
>  
>  Customer Experience and Platform Integration R Dept
>  --
>  Keong Lim, Huawei Technologies Co. Ltd (keong@huawei.com) Ground 
> Floor, Suite 1, 5 Lakeside Drive, BURWOOD EAST VIC 3151 AUSTRALIA
>  --
>"If ye love wealth better than liberty, the tranquillity of servitude 
> than the
> animating contest of freedom-go from us in peace. We ask not your 
> counsels
> or arms. Crouch down and lick the hands which feed you. May your 
> chains sit
> lightly upon you, and may posterity forget that ye were our 
> countrymen!"
>  - Samuel Adams
>  
>  
>  
>  
>  
>  
>  
>  
>  
>
>
> 
>

--
Jack Morgan





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

View/Reply Online (#12856): https://lists.onap.org/g/onap-discuss/message/12856
Mute This Topic: https://lists.onap.org/mt/26798226/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] Invalid Username or password #portal

[Catherine LEFEVRE]

Good morning/afternoon/evening All,

Are you facing this issue on a specific lab?

Many thanks & regards
Catherine

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of gaoweitao
Sent: Friday, August 17, 2018 4:57 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Invalid Username or password #portal

same issue we are facing today.
发件人：MHassan
收件人：onap-discuss@lists.onap.org,
时间：2018-08-17 20:35:25
主 题：[onap-discuss] Invalid Username or password #portal


Hi,

I faced an issue sometimes of failing to login to the portal (invalid user name 
or password).

All portal pods are running and the portal database contains all users and no 
changes regarding the passwords.

Could you help me to solve this problem?

Thanks,




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

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

Re: [onap-discuss] Jira "Resolved Date" cannot be reset

[Catherine LEFEVRE]

Thank you Keong. 
My apologies for missing your previous recommendations.

KR
Catherine

-Original Message-
From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Keong Lim
Sent: Wednesday, August 15, 2018 8:42 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Jira "Resolved Date" cannot be reset

Hi Gary and Catherine,

I noted a similar problem to Randa in the discussion about JIRA workflows: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_g_onap-2Ddiscuss_topic_24212780-2311772=DwIFaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=eOJYB_rexZjWYY73oKMD-WeB9R0Cbyzkb7NaCIyqhYg=M5yVqxeJoh6EmVRv0XNZKRcYf5mWm6u-Ph_bOQpvto8=

My suggestion there was:

> Instead of direct changes to the "Resolution" field, it should be part of the 
> workflow buttons, so that the "post transition functions" can do things like:
> - set the "Resolution" field
> - clear the "Resolved Date"
> to more appropriate values, reducing confusion

If such a "post transition function" was included in a workflow button, then it 
could be a simple matter to fix it, even without direct access to set the 
"Resolved Date" field.


Keong




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

View/Reply Online (#11886): https://lists.onap.org/g/onap-discuss/message/11886
Mute This Topic: https://lists.onap.org/mt/24528429/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] Jira "Resolved Date" cannot be reset

[Catherine LEFEVRE]

Good morning Gary,

Resolve date is not an editable field.
I believe Helpdesks ticket was opened in the Past on this topic but it has not 
been solved
We probably need to follow-up with Kenny and Jess.

Best regards
Catherine

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Gary Wu
Sent: Tuesday, August 14, 2018 9:54 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Jira "Resolved Date" cannot be reset

If a Jira issue was changed from Task to Story, this somehow sets the "Resolved 
Date" which cannot be undone.  Because the Resolved Date is set, now the issue 
ID appears with a strikethrough in the backlog lists.

Has anyone encountered this issue?  Is there a way to reset/clear the "Resolved 
Date" or otherwise remove the strikethrough?

Thanks,
Gary




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

View/Reply Online (#11884): https://lists.onap.org/g/onap-discuss/message/11884
Mute This Topic: https://lists.onap.org/mt/24528429/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] [integration] SB-01 in use?

[Catherine LEFEVRE]

Good morning Gary,

I confirm that the CLAMP, APPC teams are not using SB01.

Christopher will try to collect additional feedback before noon PST.

Best regards
Catherine

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Gary Wu
Sent: Thursday, August 09, 2018 3:14 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [integration] SB-01 in use?

Is someone actively using Wind River Integration-SB-01?  There's an OOM 
instance there about a month old and its usage is not listed on 
https://wiki.onap.org/display/DW/Integration+Test+Labs.

Please reply to me by noon Pacific today if you need this instance retained.

Thanks,
Gary




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

View/Reply Online (#11790): https://lists.onap.org/g/onap-discuss/message/11790
Mute This Topic: https://lists.onap.org/mt/24239026/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] [oom] OOM container restarts

[Catherine LEFEVRE]

Hi Yan,

No worries.

I do not know if your container restart issue is related to a timeout or not.

The CLAMP team has increased the initialDelaySeconds to 120 in the values.yaml 
file.

# probe configuration parameters
liveness:
  initialDelaySeconds: 120

Hope it helps.

Best regards
Catherine
From: Yan Yang [mailto:yangya...@chinamobile.com]
Sent: Wednesday, August 08, 2018 6:09 AM
To: onap-discuss@lists.onap.org; Lefevre, Catherine ; 
'Gary Wu' ; roger.maitl...@amdocs.com; 
onap-rele...@lists.onap.org
Subject: 答复: [onap-discuss] [oom] OOM container restarts

Hi Catherine and Gary,

Sorry for late to see this email.

VF-C team will key our eyes on this, may be need some help from OOM team.


Best Regards,
Yan
发件人: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
[mailto:onap-discuss@lists.onap.org] 代表 Catherine LEFEVRE
发送时间: 2018年8月8日 11:49
收件人: Gary Wu; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>; 
onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>
主题: Re: [onap-discuss] [oom] OOM container restarts

Thank you Gary for the additional information.
I raised previously this request because some PTLs could not find the logs from 
previous OOM containers restart.

If PTLs check at the beginning of their day then they should be able to capture 
the logs if the restart reoccurs.

I looked on the different environments yesterday (Aug 7th).
I have asked CLAMP, SDNC, DCAEGEN2, MUSIC, EXTAPI, AAF teams to investigate 
since the restart of their containers are recurrent.
I did not trigger the VFC team – I did the assumption that you were already 
working with them.
If not then let me know.

Finally, great job on the Grafana dashboard !

Best regards
Catherine

From: Gary Wu [mailto:gary.i...@huawei.com]
Sent: Tuesday, August 07, 2018 5:05 PM
To: Lefevre, Catherine mailto:cl6...@intl.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>; 
onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>
Subject: RE: [onap-discuss] [oom] OOM container restarts

Hi Cathrine,

Generally speaking, a container restart means that:

1.  The liveness probe initial delay is too low, and

2.  The liveness probe, when triggered, is returning the wrong status while 
the container is still initializing (i.e. not dead).

The default liveness probe in OOM is a TCP probe with a short (10 seconds?) 
initial delay.  This means that if the TCP port specified is not responding at 
10s after container start, then the container will be killed and restarted.

There are two ways to remedy this:

1.  Make the initial delay long enough to guarantee that by then the TCP 
port will be up, keeping in mind that ONAP might be running on arbitrarily slow 
hardware.

2.  Change the liveness probe to something else, perhaps to a shell script 
probe inside the container that can do more sophisticated checks like process 
status, etc.

I can look into the feasibility of saving the container logs.  In the meantime, 
it might actually be easier to debug the restart issues directly in the 
environments.  The deployments are done daily at midnight Pacific so anyone who 
is actively working a restart issue should have plenty of time to gather 
information and try out liveness probe changes.

Thanks,
Gary

From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Tuesday, August 07, 2018 4:48 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>; Gary Wu 
mailto:gary.i...@huawei.com>>; 
onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>
Subject: RE: [onap-discuss] [oom] OOM container restarts

Good morning Gary,

Would it be possible to save logs before a new deployment is performed so we 
can investigate what could be the reason of these restarts?

Many thanks & regards
Catherine

From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
[mailto:onap-discuss@lists.onap.org] On Behalf Of Roger Maitland
Sent: Thursday, August 02, 2018 2:32 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
gary.i...@huawei.com<mailto:gary.i...@huawei.com>; 
onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>
Subject: Re: [onap-discuss] [oom] OOM container restarts

Thanks for setting this up Gary.  Having good data will allow us to observe and 
fix these problems.

Cheers,
Roger

From: mailto:onap-discuss@lists.onap.org>> on 
behalf of Gary Wu mailto:gary.i...@huawei.com>>
Reply-To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, 
"gary.i...@huawei.com<mailto:gary.i...@huawei.com>" 
mailto:gary.i...@huawei.com>>
Date: W

Re: [onap-discuss] [oom] OOM container restarts

[Catherine LEFEVRE]

Gary, Team,

I would like to share some findings made by the CLAMP team in case of a similar 
issue is encountered by the other teams.
It seems that the problem arrives when the container takes some time to start 
(around 60s for Windriver OOM-Daily lab)

The setting of the liveness, initialDelaySeconds, must be adapted. It was 
initially set to 30s which too low, we will increase it to 120s.

Hope it helps.

Best regards
Catherine

From: Lefevre, Catherine
Sent: Wednesday, August 08, 2018 5:49 AM
To: 'Gary Wu' ; 'onap-discuss@lists.onap.org' 
; 'roger.maitl...@amdocs.com' 
; 'onap-rele...@lists.onap.org' 

Subject: RE: [onap-discuss] [oom] OOM container restarts

Thank you Gary for the additional information.
I raised previously this request because some PTLs could not find the logs from 
previous OOM containers restart.

If PTLs check at the beginning of their day then they should be able to capture 
the logs if the restart reoccurs.

I looked on the different environments yesterday (Aug 7th).
I have asked CLAMP, SDNC, DCAEGEN2, MUSIC, EXTAPI, AAF teams to investigate 
since the restart of their containers are recurrent.
I did not trigger the VFC team – I did the assumption that you were already 
working with them.
If not then let me know.

Finally, great job on the Grafana dashboard !

Best regards
Catherine

From: Gary Wu [mailto:gary.i...@huawei.com]
Sent: Tuesday, August 07, 2018 5:05 PM
To: Lefevre, Catherine mailto:cl6...@intl.att.com>>; 
onap-discuss@lists.onap.org; 
roger.maitl...@amdocs.com; 
onap-rele...@lists.onap.org
Subject: RE: [onap-discuss] [oom] OOM container restarts

Hi Cathrine,

Generally speaking, a container restart means that:

1.  The liveness probe initial delay is too low, and

2.  The liveness probe, when triggered, is returning the wrong status while 
the container is still initializing (i.e. not dead).

The default liveness probe in OOM is a TCP probe with a short (10 seconds?) 
initial delay.  This means that if the TCP port specified is not responding at 
10s after container start, then the container will be killed and restarted.

There are two ways to remedy this:

1.  Make the initial delay long enough to guarantee that by then the TCP 
port will be up, keeping in mind that ONAP might be running on arbitrarily slow 
hardware.

2.  Change the liveness probe to something else, perhaps to a shell script 
probe inside the container that can do more sophisticated checks like process 
status, etc.

I can look into the feasibility of saving the container logs.  In the meantime, 
it might actually be easier to debug the restart issues directly in the 
environments.  The deployments are done daily at midnight Pacific so anyone who 
is actively working a restart issue should have plenty of time to gather 
information and try out liveness probe changes.

Thanks,
Gary

From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Tuesday, August 07, 2018 4:48 AM
To: onap-discuss@lists.onap.org; 
roger.maitl...@amdocs.com; Gary Wu 
mailto:gary.i...@huawei.com>>; 
onap-rele...@lists.onap.org
Subject: RE: [onap-discuss] [oom] OOM container restarts

Good morning Gary,

Would it be possible to save logs before a new deployment is performed so we 
can investigate what could be the reason of these restarts?

Many thanks & regards
Catherine

From: onap-discuss@lists.onap.org 
[mailto:onap-discuss@lists.onap.org] On Behalf Of Roger Maitland
Sent: Thursday, August 02, 2018 2:32 PM
To: onap-discuss@lists.onap.org; 
gary.i...@huawei.com; 
onap-rele...@lists.onap.org
Subject: Re: [onap-discuss] [oom] OOM container restarts

Thanks for setting this up Gary.  Having good data will allow us to observe and 
fix these problems.

Cheers,
Roger

From: mailto:onap-discuss@lists.onap.org>> on 
behalf of Gary Wu mailto:gary.i...@huawei.com>>
Reply-To: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, 
"gary.i...@huawei.com" 
mailto:gary.i...@huawei.com>>
Date: Wednesday, August 1, 2018 at 6:09 PM
To: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, 
"onap-rele...@lists.onap.org" 
mailto:onap-rele...@lists.onap.org>>
Subject: [onap-discuss] [oom] OOM container restarts

Hi PTLs,

We have started to log the number of container restarts in OOM daily deployment 
tests:

Re: [onap-discuss] [oom] OOM container restarts

[Catherine LEFEVRE]

Thank you Gary for the additional information.
I raised previously this request because some PTLs could not find the logs from 
previous OOM containers restart.

If PTLs check at the beginning of their day then they should be able to capture 
the logs if the restart reoccurs.

I looked on the different environments yesterday (Aug 7th).
I have asked CLAMP, SDNC, DCAEGEN2, MUSIC, EXTAPI, AAF teams to investigate 
since the restart of their containers are recurrent.
I did not trigger the VFC team – I did the assumption that you were already 
working with them.
If not then let me know.

Finally, great job on the Grafana dashboard !

Best regards
Catherine

From: Gary Wu [mailto:gary.i...@huawei.com]
Sent: Tuesday, August 07, 2018 5:05 PM
To: Lefevre, Catherine ; onap-discuss@lists.onap.org; 
roger.maitl...@amdocs.com; onap-rele...@lists.onap.org
Subject: RE: [onap-discuss] [oom] OOM container restarts

Hi Cathrine,

Generally speaking, a container restart means that:

1.  The liveness probe initial delay is too low, and

2.  The liveness probe, when triggered, is returning the wrong status while 
the container is still initializing (i.e. not dead).

The default liveness probe in OOM is a TCP probe with a short (10 seconds?) 
initial delay.  This means that if the TCP port specified is not responding at 
10s after container start, then the container will be killed and restarted.

There are two ways to remedy this:

1.  Make the initial delay long enough to guarantee that by then the TCP 
port will be up, keeping in mind that ONAP might be running on arbitrarily slow 
hardware.

2.  Change the liveness probe to something else, perhaps to a shell script 
probe inside the container that can do more sophisticated checks like process 
status, etc.

I can look into the feasibility of saving the container logs.  In the meantime, 
it might actually be easier to debug the restart issues directly in the 
environments.  The deployments are done daily at midnight Pacific so anyone who 
is actively working a restart issue should have plenty of time to gather 
information and try out liveness probe changes.

Thanks,
Gary

From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Tuesday, August 07, 2018 4:48 AM
To: onap-discuss@lists.onap.org; 
roger.maitl...@amdocs.com; Gary Wu 
mailto:gary.i...@huawei.com>>; 
onap-rele...@lists.onap.org
Subject: RE: [onap-discuss] [oom] OOM container restarts

Good morning Gary,

Would it be possible to save logs before a new deployment is performed so we 
can investigate what could be the reason of these restarts?

Many thanks & regards
Catherine

From: onap-discuss@lists.onap.org 
[mailto:onap-discuss@lists.onap.org] On Behalf Of Roger Maitland
Sent: Thursday, August 02, 2018 2:32 PM
To: onap-discuss@lists.onap.org; 
gary.i...@huawei.com; 
onap-rele...@lists.onap.org
Subject: Re: [onap-discuss] [oom] OOM container restarts

Thanks for setting this up Gary.  Having good data will allow us to observe and 
fix these problems.

Cheers,
Roger

From: mailto:onap-discuss@lists.onap.org>> on 
behalf of Gary Wu mailto:gary.i...@huawei.com>>
Reply-To: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, 
"gary.i...@huawei.com" 
mailto:gary.i...@huawei.com>>
Date: Wednesday, August 1, 2018 at 6:09 PM
To: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>, 
"onap-rele...@lists.onap.org" 
mailto:onap-rele...@lists.onap.org>>
Subject: [onap-discuss] [oom] OOM container restarts

Hi PTLs,

We have started to log the number of container restarts in OOM daily deployment 
tests:

http://onapci.org/grafana/d/kRvfoqKmz/oom-container-restarts?orgId=1

Please review for your respective projects and see if your containers appear in 
these charts.

A restart count > 0 means that your container got killed by Kubernetes while it 
was initializing.  If your docker container has a non-zero restart count, this 
means that the liveness probe configuration for your respective helm charts 
need to be fixed so that Kubernetes doesn’t kill your containers during a slow 
startup.

Our goal for Casablanca is to have zero restarts for all ONAP containers.  If 
you don’t know what a k8s liveness probe is or what to do about it, please 
contact me or the OOM team for assistance.

Thanks,
Gary


This message and the 

Re: [onap-discuss] [Onap-release] Nexus IQ related question

[Catherine LEFEVRE]

Good morning Jess,

Have you identified any project that has generated this issue so we can have a 
deeper look?

Many thanks & regards
Catherine

From: onap-rele...@lists.onap.org [mailto:onap-rele...@lists.onap.org] On 
Behalf Of jwagant...@linuxfoundation.org
Sent: Monday, August 06, 2018 10:13 PM
To: onap-release ; onap-discuss@lists.onap.org
Subject: [Onap-release] Nexus IQ related question

Dear ONAP team,

I am helping Steve track down some of the JS failures reported by Nexus IQ tool.

I have a small question to the teams about this. Can I get a confirmation on 
the files being
included in *.war artifacts? Are these including both Java and Java Script 
related files?

Some of the bogus failures we have are related to Java Script packages found 
inside *war files
and we wan to take the right approach to minimize these.

Thanks!
Jess


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

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

Re: [onap-discuss][onap-tsc][integration] PTL Election for Integration - Self Nomination

[Catherine LEFEVRE]

+100 :)!

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Kang Xi
Sent: Thursday, July 12, 2018 5:09 PM
To: onap-discuss@lists.onap.org; Gary Wu 
Subject: Re: [onap-discuss][onap-tsc][integration] PTL Election for Integration 
- Self Nomination

+1

Regards,
Kang

From: onap-discuss@lists.onap.org 
[mailto:onap-discuss@lists.onap.org] On Behalf Of Gary Wu
Sent: Thursday, July 12, 2018 10:33
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss][onap-tsc][integration] PTL Election for Integration 
- Self Nomination

+1

From: onap-discuss@lists.onap.org 
[mailto:onap-discuss@lists.onap.org] On Behalf Of Chengli Wang
Sent: Wednesday, July 11, 2018 9:15 PM
To: onap-discuss 
mailto:onap-discuss@lists.onap.org>>; lcl7608 
mailto:lcl7...@163.com>>; ramkik 
mailto:ram...@vmware.com>>
Cc: Liu Chenglong mailto:lcl7...@163.com>>; bf1936 
mailto:bf1...@att.com>>; Yunxia Chen 
mailto:helen.c...@huawei.com>>
Subject: 回复: Re: [onap-discuss][onap-tsc][integration] PTL Election for 
Integration - Self Nomination

+1


发件人： Liu Chenglong
发送时间： 2018-07-12 09:58
收件人： onap-discuss; 
ramkik
抄送： Liu Chenglong; 
bf1...@att.com; 
helen.c...@huawei.com
主题： Re: [onap-discuss][onap-tsc][integration] PTL Election for Integration - 
Self Nomination
+1

在 2018年7月12日，07:46，ramki krishnan mailto:ram...@vmware.com>> 
写道：

+1

From: onap-discuss@lists.onap.org 
mailto:onap-discuss@lists.onap.org>> On Behalf Of 
Brian
Sent: Wednesday, July 11, 2018 12:22 PM
To: onap-discuss@lists.onap.org; 
helen.c...@huawei.com
Subject: Re: [onap-discuss][onap-tsc][integration] PTL Election for Integration 
- Self Nomination

+1 :)

From: onap-discuss@lists.onap.org 
mailto:onap-discuss@lists.onap.org>> On Behalf Of 
Helen Chen
Sent: Wednesday, July 11, 2018 3:20 PM
To: onap-discuss 
mailto:onap-discuss@lists.onap.org>>; onap-tsc 
mailto:onap-...@lists.onap.org>>
Subject: Re: [onap-discuss][onap-tsc][integration] PTL Election for Integration 
- Self Nomination

Dear ONAP Integration Committers,

I would like to nominate myself for the role of PTL of ONAP Integration project.

I was the PTL of ONAP Integration project in past one year and worked with 
Integration team delivered both Amsterdam and Beijing release. Before that, I 
also had 7+ years of experience in the open source community with projects like 
ONAP, OPEN-O, OpenDaylight, and OpenSocial.

Other qualifications:
I am a Principal Architect in the Networking Business Unit at Huawei US R, 
located at Santa Clara, California. I have years of working experience as 
software architect and leader in networking/SDN/NFV, Artificial Intelligence 
(AI) / Machine Learning (ML), cloud computing, Video / Multimedia/AR/VR/MR, 
etc. area as well as bringing new innovations from whiteboard to product 
delivery at Huawei, Cisco, Sourceforge, etc.

I had very happy and inspiring working experience collaborating with you in the 
past one year and hope to continue getting your support to bring ONAP into the 
next level.

Regards,

Helen Chen

From: onap-tsc mailto:onap-...@lists.onap.org>> on 
behalf of Helen Chen 00725961 
mailto:helen.c...@huawei.com>>
Date: Monday, July 9, 2018 at 5:32 PM
To: onap-discuss 
mailto:onap-discuss@lists.onap.org>>, onap-tsc 
mailto:onap-...@lists.onap.org>>
Subject: [onap-discuss][onap-tsc][integration] PTL Election for Integration

Dear ONAP Integration Committers,

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

If you are interested in the Integration PTL position.  Please reply to all to 
do self-nomination.

We will close the self-nomination window by 23:59 PDT July 11th, Wednesday, 
2018.  Further instructions will be sent out to the committers on the election 
procedure.  The final result will be announced on the ONAP lists before the end 
of this week.

Regards,
Helen Chen



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

View/Reply Online (#11093): https://lists.onap.org/g/onap-discuss/message/11093
Mute This Topic: https://lists.onap.org/mt/23265673/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][clamp] Inner communicator

[Catherine LEFEVRE]

Good morning Adam,

Some projects including CLAMP are on Rocket.chat
http://onap-integration.eastus.cloudapp.azure.com:3000/directory

[cid:image003.jpg@01D41452.62CF65E0]

Best regards
Catherine

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Krysiak, Adam (Nokia - PL/Wroclaw)
Sent: Thursday, July 05, 2018 9:28 AM
To: onap-discuss@lists.onap.org; Ngueko, Gervais-Martial 
Subject: [onap-discuss][clamp] Inner communicator

Hi,

I see that SDC has it's inner communicator 
(https://wiki.onap.org/display/DW/Contacts).
It would be really nice to have something like this in CLAMP.

What do you think?


Adam Krysiak
Software Engineer
MN MANO RD ONAP-UI-ML DEVOPS WRO 2 SG
Nokia
Contact number: +48691441316


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

View/Reply Online (#10851): https://lists.onap.org/g/onap-discuss/message/10851
Mute This Topic: https://lists.onap.org/mt/23163014/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 Risks Wiki page

[Catherine LEFEVRE]

Dear All,

I would like to inform you that I have created a new wiki page to track any 
Casablanca risk that each project team will identify during the ONAP Casablanca 
release: https://wiki.onap.org/display/DW/Casablanca+Risks

It already contains the risk related to JS test coverage.

Best regards
Catherine

Catherine Lefèvre
AT Labs - Network Cloud & Infrastructure
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


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

TEXTING and DRIVING... It Can Wait

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



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


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

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