Re: [onap-discuss] ONAP Java 8 -> 11 upgrade exception process

[Closset, Christophe]

Hello Amy,

I've created the exception for SDC and AAI (issue with JanusGraph)

https://wiki.onap.org/display/DW/Guilin+Exception+Request+for+REQ-351

Regards
Christophe

From: onap-discuss@lists.onap.org  On Behalf Of 
ZWARICO, AMY
Sent: Friday, August 21, 2020 2:25 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] ONAP Java 8 -> 11 upgrade exception process

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
If you need an exception for upgrading to Java 11 
(REQ-351)
 because of a technical dependency, please request an exception using the 
Guilin exception process 
(https://wiki.onap.org/display/DW/Guilin+Milestone+and+Requirements+Exception+Requests).
Several projects have been given approval through Jira comments. It would be 
very helpful and simplify tracking if you could request a formal exception.
Best regards,
Amy Zwarico, LMTS
Chief Security Office / Platform Security
AT&T Services
(205) 613-1667



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

View/Reply Online (#21953): https://lists.onap.org/g/onap-discuss/message/21953
Mute This Topic: https://lists.onap.org/mt/76327765/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] Nominations for SDC PTL are open

[Closset, Christophe]

Dear all,

I'd like to nominate myself for the PTL role of SDC.



Short Summary
I've been part of the ONAP community since its inception in 2017 and I've been 
involved in many aspects of it :
I'm a committer on CLAMP, integration and have been contributing changes to 
CLAMP, SO, SDC, portal, AAF, Doc, integration and a few on OOM.
I've been working in SDN for a long time (at least for the last 5years+), 
supporting AT&T teams in the open sourcing of ECOMP and I've been recently 
engaged in SDC and would be honored to push the work further.



Objective

As PTL, I want to work with the SDC team and make SDC a success for the whole 
ONAP community.


Regards
Christophe

From: onap-...@lists.onap.org  On Behalf Of Sonsino, 
Ofir
Sent: Tuesday, July 21, 2020 10:23 AM
To: onap-...@lists.onap.org; onap-...@lists.onap.org; 
onap-discuss@lists.onap.org
Subject: [onap-sdc] Nominations for SDC PTL are open

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

Nominations for the PTL position for SDC project are open, according to the 
process described at:
https://wiki.onap.org/display/DW/Annual+Community+Elections+-+Process#AnnualCommunityElectionsProcess-PTLElections

Individuals interested in running for the PTL position should reply-all 
indicating their intention to run.
Nominations are due by 12PM UTC, July 23th.

Br,

Ofir Sonsino
Project Technical Lead, SDC
AT&T Network Application Development * NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
***
Office: +972 (3) 5451417
Mobile: +972 (52) 4377782
E-mail: ofir.sons...@intl.att.com



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

View/Reply Online (#21741): https://lists.onap.org/g/onap-discuss/message/21741
Mute This Topic: https://lists.onap.org/mt/75699643/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] Enabling JS in SonarCloud

[Closset, Christophe]

Done

From: DRAGOSH, PAM 
Sent: Tuesday, January 28, 2020 3:12 PM
To: onap-discuss@lists.onap.org; Closset, Christophe 

Subject: Re: [onap-discuss] Enabling JS in SonarCloud

Christophe,

Thank you for sharing, there is a wiki page for guidelines on implementing code 
coverage. Could you update that page when you get a chance?

https://wiki.onap.org/display/DW/Implementing+Code+Coverage

I just recently updated it for Java sonar configuration changes but the 
Javascript isn’t there.

Thanks!

Pam

From: mailto:onap-discuss@lists.onap.org>> on 
behalf of "CLOSSET, CHRISTOPHE" 
mailto:christophe.clos...@intl.att.com>>
Reply-To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>, "CLOSSET, 
CHRISTOPHE" 
mailto:christophe.clos...@intl.att.com>>
Date: Tuesday, January 28, 2020 at 9:06 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] Enabling JS in SonarCloud

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

All,

We’ve been tweaking around with SonarCloud over the past few days to try and 
understand why our JS was no more analyzed VS what we had in SonarQube,
Looking at SonarCloud ONAP projects, none were reporting JS 
https://sonarcloud.io/organizations/onap/projects<https://urldefense.proofpoint.com/v2/url?u=https-3A__sonarcloud.io_organizations_onap_projects&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=I1y448-FS1iwJi2aLL8gZLfiYr5jEvUZgg1ArYYIRzs&s=FpFWEZCkv1_7wVu7F8MTk9RB51TNa5SK9ssCIMbGupw&e=>,
 so we suspected that there was something different.
It seems that the SonarCloud Analyzer requires to have access to the executable 
of node.js on the build node to allow for the analysis to be run, not sure if 
this was the case before (apparently new since SQ 7.8).
We have fixed it by pointing sonar to our own instance of node.js that we 
provide in our build (this way, we control the node.js version that we want).

You can take a look at the CLAMP 
pom.xml<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dclamp.git-3Ba-3Dblob-3Bf-3Dpom.xml&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=I1y448-FS1iwJi2aLL8gZLfiYr5jEvUZgg1ArYYIRzs&s=9uAa0Hc1K-57ACowjbcToAAn67VcGnvhsA_NOs6RsB4&e=>
 file if you want to see how we’ve enabled it, also excluding test.js sources 
to properly report coverage.

Hope it helps

Regards
Christophe



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

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

[onap-discuss] Enabling JS in SonarCloud

[Closset, Christophe]

All,

We've been tweaking around with SonarCloud over the past few days to try and 
understand why our JS was no more analyzed VS what we had in SonarQube,
Looking at SonarCloud ONAP projects, none were reporting JS 
https://sonarcloud.io/organizations/onap/projects, so we suspected that there 
was something different.
It seems that the SonarCloud Analyzer requires to have access to the executable 
of node.js on the build node to allow for the analysis to be run, not sure if 
this was the case before (apparently new since SQ 7.8).
We have fixed it by pointing sonar to our own instance of node.js that we 
provide in our build (this way, we control the node.js version that we want).

You can take a look at the CLAMP 
pom.xml file if 
you want to see how we've enabled it, also excluding test.js sources to 
properly report coverage.

Hope it helps

Regards
Christophe


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

View/Reply Online (#19848): https://lists.onap.org/g/onap-discuss/message/19848
Mute This Topic: https://lists.onap.org/mt/70218540/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] login into CLAMP UI

[Closset, Christophe]

Hello Vidya,

Is AAF running ok on your system ?
Can you detail how you’ve added the certificate to your browser ?
We’ve noticed that some browsers require you to :

Open browser -> remove old certificate -> close browser
Open browser -> add the new certificate -> close browser
Open browser -> access clamp UI

Hope it helps

Regards
Christophe

From: onap-discuss@lists.onap.org  On Behalf Of 
Vidyashree Rama
Sent: Wednesday, May 15, 2019 12:06 PM
To: Ngueko, Gervais-Martial ; 
onap-discuss@lists.onap.org
Cc: Gaurav agrawal ; Rama SubbaReddy 

Subject: [onap-discuss][CLAMP] login into CLAMP UI

Hi Martial,

I am not able to login to CLAMP UI(dublin) using credentials  (admin/password 
and cs0008/password).  I have added certificate given in this wiki 
(https://wiki.onap.org/display/DW/Control+Loop+Flows+and+Models+for+Casablanca#ControlLoopFlowsandModelsforCasablanca-Configure).

Kindly help to resolve this issue

Thanks,
Vidya


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

View/Reply Online (#17036): https://lists.onap.org/g/onap-discuss/message/17036
Mute This Topic: https://lists.onap.org/mt/31628132/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 GUI #casablanca #clamp

[Closset, Christophe]

Also,

Please make sure that you remove the old certificate, close the browser, re 
open the browser, import the new one, close the browser then open it again.
Firefox/Chrome may be touchy when it comes to loading/unloading certificates 
that match the same entry

Regards
Christophe

From: Closset, Christophe
Sent: Monday, May 06, 2019 11:03 AM
To: onap-discuss@lists.onap.org; jkzcristi...@gmail.com
Subject: RE: [onap-discuss] CLAMP GUI #casablanca #clamp

Hello Xoan,

Yes the certificate was updated as part of Dublin (as it was expired) and the 
wiki link was not.

I’ve changed the link to point to the latest in master (instead of keeping a 
hard copy in the wiki), this should ensure that whatever the time you pick the 
certificate, it will be valid.

Please retry with this certificate (your import method seems ok to me).

Regards
Christophe

From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
mailto:onap-discuss@lists.onap.org>> On Behalf Of 
jkzcristiano
Sent: Friday, May 03, 2019 7:55 PM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] CLAMP GUI #casablanca #clamp

Dear all,

for some reason now I cannot login to CLAMP GUI. I am using Windows 10 and 
Chrome. I am using the certificate in this 
wiki<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Control-2BLoop-2BFlows-2Band-2BModels-2Bfor-2BCasablanca&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=SQpdQt3svDPUj1o1HQcSHxetwinoEswRDTTr2ztvY7Y&m=ykSLinXKeoFOieUkOCROXcfvXxVKKGLcZbFjzrkxnuU&s=vy9xOe4ElD2apzndS7gyJQTBfzXAjnObgN6_c004RXA&e=>.
 Not sure if I am importing this certificate in the right manner to chrome.

When I try to access CLAMP GUI via chrome, I can see the certificate route:

[cid:image001.png@01D503FC.326ACE40]

However, the certificate I download from the wiki seems to be 
"intermediateCA_1".

Hope some help here.

Alternatively, is there a simple way to "workaround" this? I am using oom 
casablanca.

Thank you in advance!
Xoan


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

View/Reply Online (#16901): https://lists.onap.org/g/onap-discuss/message/16901
Mute This Topic: https://lists.onap.org/mt/31486343/21656
Mute #clamp: https://lists.onap.org/mk?hashtag=clamp&subid=2740164
Mute #casablanca: https://lists.onap.org/mk?hashtag=casablanca&subid=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] CLAMP GUI #casablanca #clamp

[Closset, Christophe]

Hello Xoan,

Yes the certificate was updated as part of Dublin (as it was expired) and the 
wiki link was not.

I’ve changed the link to point to the latest in master (instead of keeping a 
hard copy in the wiki), this should ensure that whatever the time you pick the 
certificate, it will be valid.

Please retry with this certificate (your import method seems ok to me).

Regards
Christophe

From: onap-discuss@lists.onap.org  On Behalf Of 
jkzcristiano
Sent: Friday, May 03, 2019 7:55 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] CLAMP GUI #casablanca #clamp

Dear all,

for some reason now I cannot login to CLAMP GUI. I am using Windows 10 and 
Chrome. I am using the certificate in this 
wiki.
 Not sure if I am importing this certificate in the right manner to chrome.

When I try to access CLAMP GUI via chrome, I can see the certificate route:

[cid:image001.png@01D503FA.B8706A60]

However, the certificate I download from the wiki seems to be 
"intermediateCA_1".

Hope some help here.

Alternatively, is there a simple way to "workaround" this? I am using oom 
casablanca.

Thank you in advance!
Xoan


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

View/Reply Online (#16900): https://lists.onap.org/g/onap-discuss/message/16900
Mute This Topic: https://lists.onap.org/mt/31486343/21656
Mute #clamp: https://lists.onap.org/mk?hashtag=clamp&subid=2740164
Mute #casablanca: https://lists.onap.org/mk?hashtag=casablanca&subid=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] [clamp]:Casablanca-Logs are not generated in Clamp

[Closset, Christophe]

Note that you can overcome the issue by redefining the config of the clamp 
container in the clamp pod (config map)

You can add a parameter to override the default configuration and map the log 
location to /var/log/onap :

[cid:image002.jpg@01D4923F.8E189E40]

From: onap-discuss@lists.onap.org  On Behalf Of 
jkzcristiano
Sent: Wednesday, December 12, 2018 4:59 PM
To: Determe, Sebastien ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [clamp]:Casablanca-Logs are not generated in Clamp

On Wed, Dec 12, 2018 at 07:12 AM, sebdet wrote:
/var/log/ONAP
Great!! Thank you all!

Xoan


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

View/Reply Online (#14454): https://lists.onap.org/g/onap-discuss/message/14454
Mute This Topic: https://lists.onap.org/mt/28720227/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] Issue in designing a template

[Closset, Christophe]

Hi Nathan,

The version you are using is not yet released and has gone through several 
changes, one of which is that the
design of templates is no more part of CLAMP in Beijing and has been moved to 
SDC-DCAE D (where all the design activities happens) see 
https://wiki.onap.org/display/DW/CLAMP+Beijing+Updates

If you want, you can use the Amsterdam version of CLAMP which still has the 
template design

We are in the process of updating documentation to line up with the Beijing 
changes

Regards
Christophe

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Nathan Saraiva
Sent: Tuesday, March 27, 2018 5:27 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [CLAMP] Issue in designing a template

Hi Everybody,

I am Ph.D. student and in this moment I am studying some orchestration 
platforms, such as ONAP. I installed the CLAMP component towards understanding 
better. I follwed the steps in  
https://github.com/onap/clamp.
 However, the Template Menu didn't show in the Closed Loop Modeler (figure 
below). I already changed the user permissions, but the issue keeps. Any 
suggestions?

[cid:part1.08551FDD.1BFE8BE0@dca.fee.unicamp.br]

Regards,

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

Re: [onap-discuss] [onap][CLAMP] CLAMP GUI - Template tab not found

[Closset, Christophe]

Hello Karthik,

Thanks for looking into Clamp, you are right the admin user can do anything but
this is a change related to the Beijing release, the Templates are now going to 
be designed in SDC using DCAE Designer
Please refer to  :
https://wiki.onap.org/display/DW/CLAMP+Beijing+Updates


If you want to use the one seen in the demo, you can use the Amsterdam release

Once Beijing changes are completed, we will also update the video to avoid 
further confusion

Regards
Christophe


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Dhandapani, 
Karthikeyan via onap-discuss
Sent: Thursday, March 08, 2018 9:35 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [onap][CLAMP] CLAMP GUI - Template tab not found

Hi Team, Myself  Karthik from Verizon.

I am exploring CLAMP Application. I cloned the master branch and build is 
success with Docker.
In CLAMP GUI -> I could not find the Template tab to create the template.

I logged in as Admin , and password is password. I got the error that Admin 
user cannot have privilege to get templates. But I see, all your demo videos 
logged in as Admin.

Should I login as different user ?  or  Admin will work ?.
I am going through the code to check the possibility to enable the permission 
to Admin user.

Could you Please suggest/help me in this issue ?



Thanks for your time.



Regards,
Karthik.

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

Re: [onap-discuss] docker:clamp

[Closset, Christophe]

Hello aijanwen,

Sorry for the late reply,

Can you give more details on your build environment ? Did you successfully 
build the project before (are you running on a VM that is running Ubuntu?)
It seems the docker plugin was unable to download the OS updates for the base 
image (this step is done to ensure you have an up to date image in the docker 
build),

Wondering if this is an instance of 
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1577926


Regards
Christophe

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of aijianwen
Sent: Monday, November 13, 2017 3:44 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] docker:clamp

Hi,team:
I want to produce the dockers of clamp.
I download the code of clamp project,then using the shell script:
#!/bin/bash
source /etc/profile


W: GPG error: 
http://security.ubuntu.com/ubuntu
 xenial-security InRelease: Could not execute 'apt-key' to verify signature (is 
gnupg installed?)

W: The repository 
'http://security.ubuntu.com/ubuntu
 xenial-security InRelease' is not signed.

W: GPG error: 
http://archive.ubuntu.com/ubuntu
 xenial InRelease: Could not execute 'apt-key' to verify signature (is gnupg 
installed?)

W: The repository 
'http://archive.ubuntu.com/ubuntu
 xenial InRelease' is not signed.

W: GPG error: 
http://archive.ubuntu.com/ubuntu
 xenial-updates InRelease: Could not execute 'apt-key' to verify signature (is 
gnupg installed?)

W: The repository 
'http://archive.ubuntu.com/ubuntu
 xenial-updates InRelease' is not signed.

W: GPG error: 
http://archive.ubuntu.com/ubuntu
 xenial-backports InRelease: Could not execute 'apt-key' to verify signature 
(is gnupg installed?)

W: The repository 
'http://archive.ubuntu.com/ubuntu
 xenial-backports InRelease' is not signed.

[ERROR] Failed to execute goal com.spotify:docker-maven-plugin:1.0.0:build 
(build-image) on project clds: Exception caught: The command '/bin/sh -c test 
-n "$http_proxy" && echo "Acquire::Proxy 
\"http://$http_proxy\";"
 > /etc/apt/apt.conf.d/02proxy || true &&  apt-get update &&  apt-get 
-y dist-upgrade &&  apt-get install -y openjdk-8-jre-headless' returned a 
non-zero code: 100 -> [Help 1]



How to solve it?

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

Re: [onap-discuss] pls close https://gerrit.onap.org/r/#/c/5009/

[Closset, Christophe]

+Rob

The MSO project is deprecated and is locked as read only, so this change cannot 
be merged as is
Please resubmit to the SO project if it is still meaningful.

[cid:image001.jpg@01D31BF3.0E768E90]

Note that I’m no more a committer on MSO  ( and SO) so please contact the PTL 
of this project or committers to get the change approved and merged

https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-ServiceOrchestrator

Regards
Christophe

From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Wednesday, August 23, 2017 9:16 AM
To: Closset, Christophe 
Cc: Gildas Lanilis ; Seshu m 
; 'onap-discuss@lists.onap.org' 

Subject: pls close https://gerrit.onap.org/r/#/c/5009/

Dear Christophe Closset

Kindly help to close this git commit  
https://gerrit.onap.org/r/#/c/5009/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_5009_&d=DwMFbw&c=LFYZ-o9_HUMeMTSQicvjIg&r=dnnJbZr4ZyquG9ib2bthXCpy6mcsShHseeENa-AmKrM&m=ZRsRSrsuGRfEr80uNERHMPEF0AxWfMLxjogd0dt399M&s=ImOFl_jQAgV74W15kwOpkbnmjhYeVV0pfVTDL_i2UvU&e=>
 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!
***

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

Re: [onap-discuss] Regarding docker baseline tag

[Closset, Christophe]

1.0-STAGING-latest is built out of the release 1.0.0 branch for each component.

This branch is the one that was used for the initial seed code of ONAP, and is 
pretty much stable now (all new work happens on master)
Even though the containers are rebuilt every day, since the code is not moving 
on that branch it means these won't be different

Note that this branch may be renamed in the future (since we will create an 
official R1 with the Amsterdam release) but I would still recommend using that 
docker tag as a stable build for now.

Regards
Chrisotphe

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Tuesday, June 27, 2017 9:55 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Regarding docker baseline tag

Hi All,

My understanding is that everyday's build is tagged as "latest" as well. So 
while installing ONAP, if I use docker_version: 1.0-STAGING-latest as an 
environment parameter, I will be getting previous day build. That means I will 
get different functionality in every install.

If I want to use some baseline functionality, which may not be latest but have 
highest success probability, which tag I should be using for docker ? Also what 
should be corresponding artifact version and gerrit version ?

Thank you.




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] Integration project PTL Election

[Closset, Christophe]

+1

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Thursday, June 22, 2017 9:31 PM
To: onap-discuss@lists.onap.org
Cc: Yunxia Chen ; wangchen...@chinamobile.com; ROSE, 
DANIEL V ; PLATANIA, MARCO ; 
Closset, Christophe ; Closson, Anael 
; DEY, SPONDON ; ANAPAN-LAVALLE, HECTOR A 
; xiaolong.k...@orange.com; francois.desp...@orange.com; 
yangyi@chinatelecom.cn; wanglm@chinatelecom.cn; Gary Wu 
; Kang Xi ; Yang Xu (Yang, Fixed 
Network) ; xingxiaocheng ; 
aijianwen ; Liuyuliang (Yuliang, SSA) 
; dandrus...@mirantis.com; lxin...@vmware.com; 
bin.y...@windriver.com; alon.strikov...@amdocs.com
Subject: [onap-discuss] Integration project PTL Election

Dear Integration committers,

Upon close our self-nomination period, we only have one candidate: Helen Chen.  
According to LF rules, we still need to run the election (cannot use that poll 
system, it requires two choices).   I’d like to start the vote through email, 
and close the vote at this Friday, June 23rd , 11:59 PM, PDT.

Committers, if you support Helen Chen for PTL, would you please respond to this 
message with “+1”.  If you don’t, please respond with “-1”, and if you are 
neutral, please respond with “0”.

Regards,

Helen Chen

Committers list upon Integration project approval date 06/08/2017 for your 
reference:
Helen Chen



helen.c...@huawei.com<mailto:helen.c...@huawei.com>





Chengli Wang



wangchen...@chinamobile.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_mailto-3A&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=dnnJbZr4ZyquG9ib2bthXCpy6mcsShHseeENa-AmKrM&m=EYdyFyzXviUtykt0V7zBi3iIycbUbsPSwNC9o5kAIUw&s=jYg_GabgryyKk80Z6heJ7m9zV3HjVmjlXB_1twP2tKY&e=>





Daniel Rose



dr6...@att.com<mailto:dr6...@att.com>





Marco Platania



plata...@research.att.com<mailto:plata...@research.att.com>





Christophe Closset



cc6...@intl.att.com<mailto:cc6...@intl.att.com>





Anael Closson



ac2...@intl.att.com<mailto:ac2...@intl.att.com>





Spondon Dey



 spondon...@att.com<mailto:spondon...@att.com>





Hector Anapan-Lavalle



ha0...@att.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_mailto-3A&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=dnnJbZr4ZyquG9ib2bthXCpy6mcsShHseeENa-AmKrM&m=EYdyFyzXviUtykt0V7zBi3iIycbUbsPSwNC9o5kAIUw&s=jYg_GabgryyKk80Z6heJ7m9zV3HjVmjlXB_1twP2tKY&e=>





Xiaolong Kong



xiaolong.k...@orange.com<mailto:yangyi@chinatelecom.cn>





François Despres



francois.desp...@orange.com<mailto:francois.desp...@orange.com>





Yi Yang



yangyi@chinatelecom.cn<mailto:yangyi@chinatelecom.cn>





Luman Wang



wanglm@chinatelecom.cn<mailto:wanglm@chinatelecom.cn>





Gary Wu



gary.i...@huawei.com<mailto:gary.i...@huawei.com>





Kang Xi



kang...@huawei.com<mailto:kang...@huawei.com>





Yang Xu



yang@huawei.com<mailto:yang@huawei.com>





Xiaocheng Xing



xingxiaoch...@huawei.com<mailto:xingxiaoch...@huawei.com>





Jianwen Ai



aijian...@huawei.com<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_mailto-3A&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=dnnJbZr4ZyquG9ib2bthXCpy6mcsShHseeENa-AmKrM&m=EYdyFyzXviUtykt0V7zBi3iIycbUbsPSwNC9o5kAIUw&s=jYg_GabgryyKk80Z6heJ7m9zV3HjVmjlXB_1twP2tKY&e=>





Yuliang Liu



liuyulia...@huawei.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__huawei.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=dnnJbZr4ZyquG9ib2bthXCpy6mcsShHseeENa-AmKrM&m=EYdyFyzXviUtykt0V7zBi3iIycbUbsPSwNC9o5kAIUw&s=T7vwalHivIZk4VvOVFm58vHI6t-4u78O9qlGfwj-bWU&e=>





Dmitriy Andrushko



dandrus...@mirantis.com<mailto:dandrus...@mirantis.com>





Xinhui Li



lxin...@vmware.com<mailto:lxin...@vmware.com>





Bin Yang



bin.y...@windriver.com<mailto:bin.y...@windriver.com>





Alon Strikovsky



alon.strikov...@amdocs.com<mailto:alon.strikov...@amdocs.com>








From: Helen Chen 00725961 mailto:helen.c...@huawei.com>>
Date: Wednesday, June 21, 2017 at 7:44 PM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] Integration project PTL nomination solicitation

Dear Integration committers,

I would like to inform you that the voting poll has been set up for vote 
collection.
The voting poll will be closed by Friday, June 23rd , 11:59 PM, PDT.

Regards,

Helen Chen

From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Helen Chen 00725961 
mailto:helen.c...@huawei.com>>
Date: Friday, June 16, 2017 at 4:37 PM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] Integration project PTL nomination solicitation

Dear Integration committers,

The Integration project is solicitin

Re: [onap-discuss] aai docker images are missing !

[Closset, Christophe]

I was able to pull mso 1.0-STAGING-latest today, which image name do you still 
have issues with ?

From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Thursday, June 15, 2017 10:03 AM
To: Closset, Christophe ; bharath thiruveedula 
; Kanagaraj Manickam ; 
onap-discuss@lists.onap.org; Subhash Kumar Singh 

Subject: RE: [onap-discuss] aai docker images are missing !

we are using 1.1-STAGING-latest as 1.0-STAGING-latest is missing still. Is it 
ok?
Thanks.

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

***
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: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Closset, Christophe
Sent: Wednesday, June 14, 2017 5:38 PM
To: bharath thiruveedula; Kanagaraj Manickam; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Subhash Kumar 
Singh
Subject: Re: [onap-discuss] aai docker images are missing !

It seems the Nexus hosting the docker images has some troubles,

I’ll raise a support ticket

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of bharath thiruveedula
Sent: Wednesday, June 14, 2017 9:29 AM
To: Kanagaraj Manickam mailto:mkr1...@gmail.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Subhash Kumar 
Singh mailto:subhash.kumar.si...@huawei.com>>
Subject: Re: [onap-discuss] aai docker images are missing !

Hi Kanagaraj,
I am also facing similar issue for mso. Does it have any issue in nexus repo?
Regards
Bharath T

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Subhash Kumar Singh 
mailto:subhash.kumar.si...@huawei.com>>
Sent: Wednesday, June 14, 2017 12:38:23 PM
To: Kanagaraj Manickam; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] aai docker images are missing !

Hello,

The 1.0-STAGING-latest  tag is also missing, which is used in deploy script for 
AAI-1.

--
Regards,
Subhash Kumar Singh

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[onap-discuss-boun...@lists.onap.org] on behalf of Kanagaraj Manickam 
[mkr1...@gmail.com]
Sent: Wednesday, June 14, 2017 11:28
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] aai docker images are missing !
Hi,

While installing  AAI VM aai_vm1 it reports following error:
It seems the required images are not available in the docker repository.
Kindly help.

root@onap-aai-inst1:/opt/test-config# ./deploy_vm1.sh
Login Succeeded
Pulling repository 
nexus3.onap.org:10001/openecomp/aai-resources<https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus3.onap.org-3A10001_openecomp_aai-2Dresources&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=dnnJbZr4ZyquG9ib2bthXCpy6mcsShHseeENa-AmKrM&m=zreqI4cLtfLgGSYcqx4lOC81rEJRBVBQbHTLnnCn2VI&s=GkUAXpycL7Ja7gcEGt9st2yEg0qVezU3sMgSX52S1bU&e=>
Error: image openecomp/aai-resources:1.1-STAGING-latest not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/openecomp/aai-resources:1.1-STAGING-latest<https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus3.onap.org-3A10001_openecomp_aai-2Dresources-3A1.1-2DSTAGING-2Dlatest&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=dnnJbZr4ZyquG9ib2bthXCpy6mcsShHseeENa-AmKrM&m=zreqI4cLtfLgGSYcqx4lOC81rEJRBVBQbHTLnnCn2VI&s=FHwMiklQiyj0ESEAfgQnCfpJ_f_s2NFAk4-Nm32yPco&e=>
Pulling repository 
nexus3.onap.org:10001/openecomp/aai-traversal<https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus3.onap.org-3A10001_openecomp_aai-2Dtraversal&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=dnnJbZr4ZyquG9ib2bthXCpy6mcsShHseeENa-AmKrM&m=zreqI4cLtfLgGSYcqx4lOC81rEJRBVBQbHTLnnCn2VI&s=8esM9RcNnj0TeR1hil2tW0Ec6IBhtRHH37dlf8yKlkM&e=>
Error: image opene

Re: [onap-discuss] aai docker images are missing !

[Closset, Christophe]

It seems the Nexus hosting the docker images has some troubles,

I'll raise a support ticket

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of bharath thiruveedula
Sent: Wednesday, June 14, 2017 9:29 AM
To: Kanagaraj Manickam ; onap-discuss@lists.onap.org; 
Subhash Kumar Singh 
Subject: Re: [onap-discuss] aai docker images are missing !

Hi Kanagaraj,
I am also facing similar issue for mso. Does it have any issue in nexus repo?
Regards
Bharath T

From: 
onap-discuss-boun...@lists.onap.org 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Subhash Kumar Singh 
mailto:subhash.kumar.si...@huawei.com>>
Sent: Wednesday, June 14, 2017 12:38:23 PM
To: Kanagaraj Manickam; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] aai docker images are missing !

Hello,

The 1.0-STAGING-latest  tag is also missing, which is used in deploy script for 
AAI-1.

--
Regards,
Subhash Kumar Singh

From: 
onap-discuss-boun...@lists.onap.org 
[onap-discuss-boun...@lists.onap.org] on behalf of Kanagaraj Manickam 
[mkr1...@gmail.com]
Sent: Wednesday, June 14, 2017 11:28
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] aai docker images are missing !
Hi,

While installing  AAI VM aai_vm1 it reports following error:
It seems the required images are not available in the docker repository.
Kindly help.

root@onap-aai-inst1:/opt/test-config# ./deploy_vm1.sh
Login Succeeded
Pulling repository 
nexus3.onap.org:10001/openecomp/aai-resources
Error: image openecomp/aai-resources:1.1-STAGING-latest not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/openecomp/aai-resources:1.1-STAGING-latest
Pulling repository 
nexus3.onap.org:10001/openecomp/aai-traversal
Error: image openecomp/aai-traversal:1.1-STAGING-latest not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/openecomp/aai-traversal:1.1-STAGING-latest
Pulling repository 
nexus3.onap.org:10001/openecomp/search-data-service
Error: image openecomp/search-data-service:1.1-STAGING-latest not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/openecomp/search-data-service:1.1-STAGING-latest
Pulling repository 
nexus3.onap.org:10001/openecomp/datarouter-service
Error: image openecomp/datarouter-service:1.1-STAGING-latest not found
Error response from daemon: No such image: 
nexus3.onap.org:10001/openecomp/datarouter-service:1.1-STAGING-latest

Re: [onap-discuss] Staging repo in settings.xml

[Closset, Christophe]

I’ll set up a call to discuss this further.

I think we need to have a TSC decision on :

-Do we want to freeze artifacts from seed code release 1.0.0 (the 
stable one) and/or 1.1.0 (the enhanced and catch up code)  or not ?

o   A mitigated action could be to just go and bless the Docker containers from 
the stable build that we have – which is what people are trialing against and 
rename the stable branch to something more meaningful (just keep it for 
historical purpose and as an easy way for people to see the code they are 
running their trial on), then for the current master we can probably move away 
from staging and go to snapshots as suggested below.

-Do we formally remove artifact version numbering from ONAP release 
numbering ?

o   If we do, then we could question the whole staging approach.

Few things to note when moving away from staging:

-I don’t think there is a formal list of which artifacts are coming 
from staging, now disabling the staging repo will quickly highlight them. This 
will need attention from all teams to fix their builds with proper snapshots.

We’ve noticed that the build nodes do not start from an empty .m2 repository so 
it might obfuscate issues.

-We will need to setup daily snapshot builds (right now we have daily 
release against staging build) to keep up building our daily docker images, 
sonar scans etc… - we will need to adapt the docker images tag to reflect that 
situation

-We will need each team to adapt their jjb jobs and templates to have a 
way to re-enable staging easily

Just to say that it’s not straightforward and will most probably take a few 
days before we get all components buildable again on master

Regards
Christophe

From: SPATSCHECK, OLIVER
Sent: Friday, May 26, 2017 2:19 PM
To: Andrew Grimberg 
Cc: Gary Wu ; Coquelin, Sebastien 
; Closset, Christophe ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Staging repo in settings.xml


Would have to talk to all the teams to get the details but I think most 
artifacts need to be locked down. Please remember that since we created the 
1.0.0 branch we have been contributing code based on two additional internal 
releases into the seed repos. This new code base has not been fully tested yet 
(we took some shortcuts)to catch up. So if we remove the 1.0.0 branch we don’t 
have a working system right now.

I also think that artifact versioning shouldn’t match the ONAP release 
versioning. I think trying to keep that all in sync with the number of 
artifacts we have is a nightmare. E.g. will you be rolling the artifact version 
number on the Open-O artifacts back to 1.0.0? I would just leave them where 
they are. Otherwise you will have people with incorrect artifacts in there 
maven caches.  This seems to be just generating additional work/confusion with 
little practical value.

Oliver

On May 25, 2017, at 5:55 PM, Andrew Grimberg 
mailto:agrimb...@linuxfoundation.org>> wrote:

On 05/25/2017 02:36 PM, Gary Wu wrote:

That makes sense given that staging artifacts were supposed to exist
only long enough to decide whether they're good to release or not;
they were not meant to be used as long-lived build dependencies.

I think the right thing to do is to move away from this "build
against staging" approach relatively soon.  Given that our formal 1st
release is November, and assuming that the release artifact version
will be "1.0.0", I see two options:

1. Do not release any thing from staging right now.  Change all
artifact versions to 1.0.0-SNAPSHOT.

2.  For the subset of artifacts that need to be "locked down",
actually release the staging candidates right now as 1.0.0-RC0 or
some such.  Then change all artifact versions to 1.0.0-SNAPSHOT,
except explicit dependencies on the released 1.0.0-RC0 artifacts
where desired.

Any other ideas?

Do we have a full list of the artifacts that explicitly need to be
served up from staging repos right now?  I'm hoping this list is
relatively short.

Not something I can answer. I would hope that the seed projects can
answer that.

-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

Re: [onap-discuss] Staging repo in settings.xml

[Closset, Christophe]

Hi Gary, Andy,

As for the OpenECOMP history, the whole original idea was also to align 
everyone's release number and date to a common one for the launch (the current 
release-1.0.0 branch). 
Concerns were raised in the dev teams (as you pointed below) that everyone's 
pace would be different eventually and that we should have a way of releasing 
components independently even though we have serious inter dependencies within 
ONAP. So instead of a MEGA build - all components have their independent 
release jobs building on staging. This hybrid approach somehow suited us 
nicely, now we did not go through the blessing process to move all these to 
proper release artifacts and kept moving with this in the master branch as Andy 
explained.

I agree that it's confusing and not ideal right now (the concept of not really 
released 'release artifacts' is puzzling at first but we got used to it).
If (and that's probably a TSC decision to make) we want to move to a fully 
decoupled model - which with the number of repositories growing is probably a 
good idea - then we should also remove the joint numbering somewhat (TSC) so 
that components can truly release independently. This indeed brings the issue 
of managing dependencies in a non-intuitive manner (I'm building ONAP release X 
and I see dependencies with strange numbers, potentially from previous ONAP 
releases )and would need to be adopted by the community as well.

One benefit of the staging approach is that it allows to limit version variance 
during a stabilization period. Staging should be limited in time, probably for 
a period at the end of the official release cycle when everyone's artifact are 
mostly ready. The Release Candidate approach is another way of achieving this I 
believe.

Regards
Christophe

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu
Sent: Friday, May 12, 2017 12:29 AM
To: Andrew Grimberg ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Staging repo in settings.xml

Hi Andy, thanks for the explanation.

It sounds like this will require a larger discussion on the overall versioning 
and release strategy across ONAP projects and artifacts.

For everyone's reference, in OPEN-O we decided to keep all artifact versions in 
sync across projects in order to minimize the management and support burden.  
Under this assumption, the autorelease "mega-build" that builds everything 
together was a way to enforce synchronized version labels and to detect 
cross-project compilation issues since everyone was building against SNAPSHOT 
dependencies that can change at any time.

If we don't want to build against SNAPSHOT dependencies across projects, then 
it means that different projects may have different release cycles, and we may 
end up with a mix of different artifact versions for the official "ONAP Version 
1" distribution.  This has the benefit of breaking up the autorelease 
"mega-build", at the cost of having to manage and support a mix of artifact 
versions and differing release schedules.

Can someone from ECOMP pipe in to add some historical perspective and/or the 
current assumptions on artifact versioning?

Regarding the issue at hand (Staging in settings.xml), a better approach may be 
to release the upstream artifact using a version label like "1.0.0-RC0" as an 
intermediate Release (i.e. no longer changing) artifact.  This will allow 
downstream projects to build against an artifact version that is truly 
locked-down (and not from Staging), while allowing the upstream team some 
flexibility to make tweaks before releasing the final "1.0.0" version.

If anyone has thoughts on this topic, please jump in.

Thanks,
Gary


-Original Message-
From: Andrew Grimberg [mailto:agrimb...@linuxfoundation.org]
Sent: Thursday, May 11, 2017 1:17 PM
To: Gary Wu ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Staging repo in settings.xml

On 05/10/2017 02:05 PM, Gary Wu wrote:
> What's the rationale behind including Staging in the global 
> settings.xml?  This seems unorthodox.
> 
> I have now observed instances (e.g. sdnc/core, mso) where a clean 
> build in a local environment will fail unless Staging is included in 
> local settings.xml.  This is because there are snapshot artifacts in 
> Nexus that have been built with a dependency on a "release versioned"
> artifact which has only been staged but not yet released.  This 
> doesn't seem right.

You're correct that it's rather unorthodox. The rational was supposed to be 
temporary as the original intent was that each of the base projects would be 
doing _independent_ releases (that whole Continuous Delivery concept). The 
thing is that no actual release happened before ONAP started as I was being led 
to believe was going to happen.

As downstream of the core projects wanted to only depend on a release version 
so that they weren't tied to the SNAPSHOTS except for when a new feature th

[onap-discuss] [sonar]

[Closset, Christophe]

SDN-C projects are there now as well as others that were missing

Regards
Christophe

From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Lefevre, Catherine
Sent: Monday, April 24, 2017 8:49 PM
To: Jing Wang ; onap-discuss at lists.onap.org
Subject: Re: [onap-discuss] [sonar]

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

I just had a quick look and we are indeed missing a couple of them.
Let me follow-up with the Linux Foundation support team (Andrew Grimberg) on 
this topic

Best regards
Catherine

From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Jing 
Wang
Sent: Monday, April 24, 2017 8:41 PM
To: onap-discuss at lists.onap.org
Subject: [onap-discuss] [sonar]

Hi all,

I had a look at 
http://sonar.onap.org.
 It only shows 26 projects in the dashboard. I wonder if those are all the 
sonar projects we have now. Or they are only a subset.

I'm interested in the sdnc projects. Looks like they are not included.

Thanks!

Jing
-- next part --
An HTML attachment was scrubbed...
URL: 

[onap-discuss] Queries about MSO image & source code

[Closset, Christophe]

Hi,

1.It is embedded in the container, try the following URL : 
http://:8080/camunda

2. a. it is currently using a wsdl to generate stubs (implementation) during 
build, see pom.xml of that module
b. Not sure what you mean, compile works fine : 
https://jenkins.onap.org/view/mso/job/mso-master-verify-profile-java/

Regards
Christophe

From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Jian Jiang
Sent: Monday, April 24, 2017 3:18 AM
To: onap-discuss at lists.onap.org
Subject: [onap-discuss] Queries about MSO image & source code

Hi


1.  After download and run  those MSO containers, everything seems ok, but 
we cannot visit cockpit console with the URL mentioned in Readme 
'http://:8080/cockpit', not sure whether Camunda Engine not 
included in the MSO docker image or needs some special configuration?
BTW: JBOSS console is ok.

2.  MSO source code issue:

a.  'mso-network-adapter-async-client' package is incomplete on git, there 
only have test code without any implementation code.

b.  Compile MSO component will fail, please help to check.

BR
Jian




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
-- next part --
An HTML attachment was scrubbed...
URL: 

[onap-discuss] [installation] New Heat templates available in Gerrit/Nexus

[Closset, Christophe]

It should all be back now

Regards
Christophe

From: onap-discuss-bounces at lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yang, Bin
Sent: Friday, April 21, 2017 11:31 AM
To: Lefevre, Catherine ; PLATANIA, MARCO ; onap-discuss at lists.onap.org
Subject: Re: [onap-discuss] [installation] New Heat templates available in 
Gerrit/Nexus

Hi Catherine,

   Noted and thanks!

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Friday, April 21, 2017 5:09 PM
To: Yang, Bin; PLATANIA, MARCO; onap-discuss at 
lists.onap.org
Subject: RE: [onap-discuss] [installation] New Heat templates available in 
Gerrit/Nexus

Good morning Bin,

Christophe has opened a ticket to the LF helpdesk this morning
We have noticed that the following environments are currently down

https://jenkins.onap.org/
https://logs.onap.org/
https://nexus3.onap.org/
https://nexus.onap.org/

Best regards
Catherine

From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yang, 
Bin
Sent: Friday, April 21, 2017 11:02 AM
To: PLATANIA, MARCO mailto:platania at 
research.att.com>>; onap-discuss at lists.onap.org
Subject: Re: [onap-discuss] [installation] New Heat templates available in 
Gerrit/Nexus

Hi Marco,

   The links seem to be broken , I cannot download those files, 
would you help fix that? Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: onap-discuss-bounces at lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
PLATANIA, MARCO (MARCO)
Sent: Friday, April 21, 2017 4:11 AM
To: onap-discuss at lists.onap.org
Subject: Re: [onap-discuss] [installation] New Heat templates available in 
Gerrit/Nexus

Apologies for the broken link. Here are the correct ones:

https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/OpenECOMP/1.1.0-SNAPSHOT/onap_openstack_RC.yaml
https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/OpenECOMP/1.1.0-SNAPSHOT/onap_openstack_RC.env

Marco

From: mailto:onap-discuss-bounces at 
lists.onap.org>> on behalf of "PLATANIA, MARCO (MARCO)" mailto:plata...@research.att.com>>
Date: Thursday, April 20, 2017 at 4:00 PM
To: "onap-discuss at lists.onap.org" 
mailto:onap-discuss at lists.onap.org>>
Subject: [onap-discuss] [installation] New Heat templates available in 
Gerrit/Nexus

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Dear ONAP community members,

We made some major changes to the Heat templates for Rackspace and vanilla 
OpenStack. Please see below the list of changes:


1.  Removed all the post-instantiation scripts from the template and 
created a new, equivalent script in Gerrit/Nexus for each component, named 
component_install

[onap-discuss] Failed to pull docker image

[Closset, Christophe]

Hi,

I just tried and I was able to pull the image successfully :

cclo at ubuntu:~$ sudo docker login nexus3.onap.org:10001
Username: docker
Password:
Login Succeeded

Then

cclo at ubuntu:~$ sudo docker pull 
nexus3.onap.org:10001/openecomp/mso:1.0-STAGING-latest
1.0-STAGING-latest: Pulling from openecomp/mso
c62795f78da9: Pull complete
d4fceeeb758e: Pull complete
5c9125a401ae: Pull complete
0062f774e994: Pull complete
6b33fd031fac: Pull complete
e2dd741ef955: Pull complete
c1242259760e: Pull complete

just tried and I was able to pull the image successfully, did you see any error 
at the login step ?


-- next part --
An HTML attachment was scrubbed...
URL: