Re: [onap-discuss] [ONAP Helpdesk #61706] nexus and nexus3 bottleneck

[Gary Wu]

Hi Jess,

Looks like nexus/nexus3 are again bogged down today.  Can you take a look?  
This is a showstopper.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Tuesday, October 02, 2018 4:05 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #61706] nexus and nexus3 bottleneck

Looks like there might be a noisy neighbor using up a bunch of bandwidth which 
Ryan was able to detect. 

We are escalating this to our provider now. 

thanks!
Jess

On Tue Oct 02 18:46:46 2018, jwagantall wrote:
> Thanks for reporting this Gary.
> 
> I am looking into it with Ryan.
> I also noticed little bit slower since I was running a release of 8 
> binaries at once..
> 
> I will let you know for any updates from our findings.
> 
> thanks!
> Jess
> 
> On Tue Oct 02 17:57:04 2018, gary.i...@huawei.com wrote:
> > Hi helpdesk,
> >
> > nexus and nexus3 have been exceedingly slow all day, which is 
> > causing many jobs to either take a long time or time-out outright.  
> > Can you take a look?
> >
> > Thanks,
> > Gary




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

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

[onap-discuss] Anyone using ONAP-vCPE tenant?

[Gary Wu]

Is anyone actively using the ONAP-vCPE tenant in Wind River lab?

Thanks,
Gary



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

View/Reply Online (#12791): https://lists.onap.org/g/onap-discuss/message/12791
Mute This Topic: https://lists.onap.org/mt/26660217/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] Release procedure for repos with a pom hierarchy that includes multiple war/jars per repo #logging #pomba #release

[Gary Wu]

The ONAP way of doing releases is probably different from what you'd expect.  
This is how it's typically done right now:


1.   We don't commit a change of the pom version to remove the "-SNAPSHOT" 
version; the "-SNAPSHOT" is left as-is in source control.

2.A separate daily job usually with "-version-" in the name runs a "mvn 
versions:set" to strip the "-SNAPSHOT" version at job build time, resulting in 
artifacts that are release-versioned and pushed to the nexus staging repo.

3.   The "mvn versions:set" command is typically run against the root pom, 
and is smart enough to recursively make the same change through all its 
children/subtree poms, IF the children/subtree poms are set up correctly to 
have their versions inherited from the root pom.

4.   Given the above, it is fine for the "-version-" job to do a staging 
build of multiple simultaneous artifacts from an entire tree.

This should work if all your artifact versions can be the same.  I don't know 
the specifics of your docker job, but if the above works for you on the 
Java/Maven side then maybe what you need is to run the "mvn versions:set" 
command within the docker job to strip the "-SNAPSHOT" from the poms like how 
it's done for the Java builds.

Thanks,
Gary

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Michael O'Brien
Sent: Tuesday, October 02, 2018 12:46 PM
To: onap-discuss@lists.onap.org
Cc: Prudence Au ; Jessica Wagantall 

Subject: [onap-discuss] Release procedure for repos with a pom hierarchy that 
includes multiple war/jars per repo #logging #pomba #release

Team,
 Bringing this up to the community because we have a couple general 
questions around how to release projects with many artifacts per repo.
 Running into an issue where I need to 1 artifact at a time but the jobs 
and my pom structure is set for a single global build.
 Prudence, Jessica and I are looking into this - adding community - if 
there are any others with my same issue.
 Either I need to flatten and disassociate my pom tree or find a way to 
build specifically at folder level - not from the root pom.xml of the repo.
Release a specific jar
https://git.onap.org/logging-analytics/tree/reference/logging-slf4j/pom.xml
instead of the default root which builds 5 jars and 1 war (leaving out the 
non-java pom projects for python, kubernetes and docker
https://git.onap.org/logging-analytics/tree/pom.xml

 We are working very closely with Jessica right now and in the past on our 
repos and now on our release of the 2 projects logging and pomba - but running 
into issues with the release job failing because I have one release job for all 
my artifacts.
https://gerrit.onap.org/r/#/c/69618/

 This is the first release of either project (pomba is new, logging has a 
deep pom structure in Casablanca)
 We are having an issue with a conflict between the release job expecting a 
single root pom.xml
Pom structure
logging-analytics (root) (pom)
+ logging-reference (pom)
+  logging-demo
+  logging-docker-root
+  logging-kubernetes
+  logging-library
+  logging-mock-service
+  logging-slf4j
+ logging-sl4fj-demo

+ logging-pylog (pom)

Jar/war dependencies

+  logging-demo

+  logging-library (can be removed)

+  logging-mock-service

+ logging-library

+ logging-slf4j

+ logging-sl4fj-demo

+ logging-sl4j

  The issue is how do we deal with projects that have multiple artifacts 
per repo (1:m)?  I may have created a special case where I use 1 repo to create 
a war and several dependent jars - where I should have requested more repos to 
keep it (1:1)
  In pomba there are several repos each with one pom and one artifact - 
this is good.
  In logging because there is only one repo - there is a tree of folders 
each with their own pom with pom, war and jar artifacts like the following

  The logging project follows a similar but different structure to 
ccsdk/slk and sdnc/oam for example - except that my root pom's parent is 
oparent.
  Ccsdk and sdnc all reference their parents to odlparent-* whether 1 or 2 
levels deep in the project.
  So I am also wondering if there are any other projects out there 
following a pom.xml structure where there is a single root with multiple levels 
of subchild poms where each level references the level above - not the same 
root level 0

  Others:
  Root
  +  child-level1 - references root
   + child-level2 - references root

   Mine:
  Root
  +  child-level1 - references root
   + child-level2 - references "child-level1"

  It is also significant whether the child/subfolder poms are pom 
artifacts or war/jar artifacts.
  I tried
-Adjusting the version (1.2.2-SNAPSHOT to 1.2.2) from the root down - this 

Re: [onap-discuss] Anyone using ONAP-vCPE tenant?

[Gary Wu]

Yes, that would be great.  Thanks!

-Gary

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Multanen, Eric W
Sent: Tuesday, October 02, 2018 10:49 AM
To: onap-discuss@lists.onap.org; Gary Wu 
Subject: Re: [onap-discuss] Anyone using ONAP-vCPE tenant?

I don't believe any of us are at the moment.  I can delete a bunch of the 
stacks (I assume you're looking to free up resources).

Eric

From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
[mailto:onap-discuss@lists.onap.org] On Behalf Of Gary Wu
Sent: Tuesday, October 2, 2018 9:59 AM
To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] Anyone using ONAP-vCPE tenant?

Is anyone actively using the ONAP-vCPE tenant in Wind River lab?

Thanks,
Gary




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

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

Re: [onap-discuss] [ONAP Helpdesk #61676] gerrit down

[Gary Wu]

It seems like nexus and nexus3 are suffering severe congestion right now, so 
the jobs are spending a long time trying to download artifacts.

Maybe we should consider migrating those systems to AWS as well?

Thanks,
Gary

-Original Message-
From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Pamela Dragosh
Sent: Tuesday, October 02, 2018 10:12 AM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [ONAP Helpdesk #61676] gerrit down

This just started this morning. Seems to have been resolved as folks can now 
submit changes. 

Nobody hard codes any IP address, their environments haven’t changed in months. 
These were separate firewalls.

But jenkins is really, really slow today and failing to finish verify and merge 
jobs.

Pam

On 10/2/18, 11:49 AM, "Andrew Grimberg via RT" 
 wrote:

On 10/02/2018 06:56 AM, pdrag...@research.att.com via RT wrote:
> 
> It seems that multiple folks on my team across the US cannot submit a
> gerrit review. It either hangs or gives a connection refused.
> 

Greetings Pam,

Is this a problem that people have been having (and are still having)
since the maintenance of Gerrit on Friday?

If so, it sounds like there's possibly corporate firewalls blocking
access then as the ONAP Gerrit system is working just fine for me and
I've seen no alarms from our monitoring.

The new system is now behind an Amazon ELB and does not have hard and
firm IP addresses. My experience with these sorts of systems is that the
addresses will change with no notice and no control on our part but as
Amazon remanages the addresses in their own system.

The _current_ IP addresses are: 35.166.47.83 and 35.164.144.118

-Andy-

-- 
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation








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

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

[onap-discuss] [dcae] vescollector:1.3.1 docker image missing

[Gary Wu]

Hi DCAE team,

The vescollector:1.3.1 docker image as specified on the staging manifest is 
missing from nexus3.onap.org.  Can you help rebuild that image if that tag is 
still correct, or update the staging manifest if not?

Thanks,
Gary



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

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

[onap-discuss] nexus and nexus3 bottleneck

[Gary Wu]

Hi helpdesk,

nexus and nexus3 have been exceedingly slow all day, which is causing many jobs 
to either take a long time or time-out outright.  Can you take a look?

Thanks,
Gary



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

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

[onap-discuss] [integration] Who is using SB-01?

[Gary Wu]

Hi all,

Who is using the Integration-SB-01 tenant in Wind River?  If you need an 
Integration tenant to run ONAP, please check with the Integration team first, 
and then put your name against your assigned tenant here: 
https://wiki.onap.org/display/DW/Integration+Test+Labs so that we know whom to 
contact.

Thanks,
Gary



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

View/Reply Online (#12922): https://lists.onap.org/g/onap-discuss/message/12922
Mute This Topic: https://lists.onap.org/mt/27158071/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] Who is using SB-01?

[Gary Wu]

Since no one responded, we will be shutting down the SB-01 instance in a couple 
of hours.

Thanks,
Gary

_
From: Gary Wu
Sent: Wednesday, October 10, 2018 8:26 AM
To: onap-discuss@lists.onap.org
Subject: [integration] Who is using SB-01?


Hi all,

Who is using the Integration-SB-01 tenant in Wind River?  If you need an 
Integration tenant to run ONAP, please check with the Integration team first, 
and then put your name against your assigned tenant here: 
https://wiki.onap.org/display/DW/Integration+Test+Labs so that we know whom to 
contact.

Thanks,
Gary



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

View/Reply Online (#12955): https://lists.onap.org/g/onap-discuss/message/12955
Mute This Topic: https://lists.onap.org/mt/27158071/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] Scheduling of Daily Jobs

[Gary Wu]

Hi Victor,

Gerrit was migrated to AWS on Friday.  I’m guessing that git.onap.org might not 
have been updated accordingly to reflect that change.  Please log a ticket with 
LF helpdesk.

Thanks,
Gary

From: Morales, Victor [mailto:victor.mora...@intel.com]
Sent: Monday, October 01, 2018 8:14 AM
To: onap-discuss@lists.onap.org; Gary Wu 
Subject: Re: [onap-discuss] Scheduling of Daily Jobs

Hey Gary,

I have some patchsets [1] that their changes are not merged into its 
repository.  They have merged status in Gerrit and Jenkins are not showing any 
building or merging error[2] but they’re not reflected in git.onap.org[3]. Do 
you know how can I fix this? Or retry again? I’ve tried with “please release” 
and “recheck” Gerrit comments but they’re in same status.

Thanks
Victor Morales

[1] 
https://gerrit.onap.org/r/#/q/owner:victor.morales%2540intel.com+status:merged+after:2018-09-28
[2] 
https://jenkins.onap.org/view/multicloud/job/multicloud-k8s-master-merge-golang/
[3] https://git.onap.org/multicloud/k8s/


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 Wu 
mailto:gary.i...@huawei.com>>
Date: Friday, September 28, 2018 at 10:29 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] Scheduling of Daily Jobs

Hi PTLs,

Currently all of the Daily Jenkins jobs (Java/Docker release jobs) are 
scheduled for around noon UTC (8 AM Eastern), which imposes severe resource 
contention on nexus and nexus3 for the next several hours and causing some of 
them to fail due to timeouts.

To fix this, I will be submitting a change to spread the load throughout the 
day instead of having them all run at the same time.  Please let me know if you 
have any concerns.

Thanks,
Gary




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

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

[onap-discuss] [integration] integration/csit has been branched

[Gary Wu]

Hi all,

The integration/csit repo has been branched.  Please feel free to start working 
on post-casablanca CSIT test changes there.

Thanks,
Gary



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

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

Re: [onap-discuss] [ONAP Helpdesk #61676] gerrit down

[Gary Wu]

The use of http on port 80 seems to be defined in the distributionManagement 
block in CCSDK here: 
https://git.onap.org/ccsdk/parent/tree/odlparent/odlparent-lite/pom.xml?id=c3dde295948318a40bd1a78319e197299b47e153

Thanks,
Gary

-Original Message-
From: TIMONEY, DAN [mailto:dt5...@att.com] 
Sent: Wednesday, October 03, 2018 12:06 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: Gildas Lanilis ; agrimb...@linuxfoundation.org; 
FREEMAN, BRIAN D ; Gary Wu ; LEFEVRE, 
CATHERINE ; onap-discuss@lists.onap.org
Subject: Re: [ONAP Helpdesk #61676] gerrit down

Jess,

I took a closer look at that error below.  Not only is the staging plugin using 
port 80, but it's using http, not https.  I checked my configuration and 
verified that I'm using https://nexus.onap.org   not http://nexus.onap.org.  I 
have no clue where that's coming from, unless our settings.xml in Jenkins is 
somehow messed up (I can't see that directly)

Dan

-- 
Dan Timoney
SDN-CP Development
ONAP Project Technical Lead : CCSDK and SDNC 
 
Please go to  D2 ECOMP Release Planning Wiki 
<https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 
ECOMP Project In-take, 2016 Release Planning, Change Management, and find key 
Release Planning Contact Information.
 

On 10/3/18, 11:26 AM, "TIMONEY, DAN"  wrote:

Jess,

I'm still seeing this problem this morning.

You ask an excellent question about port 80.  I checked my configuration 
and verified that we're using https://nexus.onap.org with no port specified - 
so it should be port 443, not 80.  This error is happening within the staging 
plugin, which I personally have been railing against for over a year now ... 
this is just the latest in a series of problems with that wonderful plugin, the 
others being:

1) It occasionally loses track of which is the latest version of a jar 
file (which I think Andrew created a workaround for last year).
2) For zip files (which we use as installation bundles), if you try to 
pull a specific version from the staging repository, you'll consistently get 
the very first copy ever pushed, not the latest.  You can see that actually if 
you look at the artifacts in the nexus web page  - for jar files, you'll see a 
list of autogenerated repos but for zip files you'll only see the first.

So, it looks like yet another issue in the staging plugin  if you don't 
explicitly provide a port, it defaults to 80 even for https, which is just 
plain wrong.

I'll try seeing if I can get around this by explicitly setting the port to 
443 in the staging url, but if that's the problem ,we should really get 
Sonatype to fix it.  

Dan
-- 
Dan Timoney
SDN-CP Development
ONAP Project Technical Lead : CCSDK and SDNC 
 
Please go to  D2 ECOMP Release Planning Wiki 
<https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 
ECOMP Project In-take, 2016 Release Planning, Change Management, and find key 
Release Planning Contact Information.
 

On 10/2/18, 6:49 PM, "Jessica Wagantall via RT" 
 wrote:

Hi Dan, 

Looking into this issue. 

Why are we using port 80? : 

https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus.onap.org-3A80=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=Ms-DNhR23dO4sQFfYRm4ow=9BsdxCi7UWgNWFeVZnwuitt1LsK6wdh0bsG3J-s2mTE=8qfiU_gE41IyWoPbuFI1liIVFnxglXe9ybT4xnDI4Vo=:

Nothing changed for Nexus servers on Friday. The only migration that 
happened was for Gerrit. 

thanks a ton!
Jess

On Tue Oct 02 15:03:09 2018, dt5...@att.com wrote:
> All,
> 
> FYI - I hoped to work around this issue by commenting out a module
> that isn't critical from our build, hoping to reduce load.  Didn't
> help - just moved the problem to someplace else.
> 
> Here's the error I'm getting:
> 
> 18:43:05 [INFO] Installing /w/workspace/sdnc-oam-master-merge-
> java/pom.xml to /w/workspace/sdnc-oam-master-merge-
> java/admportal/target/nexus-staging/deferred/org/onap/sdnc/oam/sdnc-
> oam/1.4.0-SNAPSHOT/sdnc-oam-1.4.0-SNAPSHOT.pom
> 18:43:05 [INFO] Deploying remotely...
>  18:43:05 [INFO] Bulk deploying locally gathered artifacts from
> directory:
> 18:43:05 [INFO]  * Bulk deploying locally gathered snapshot artifacts
> 18:45:14 Oct 02, 2018 6:45:14 PM
> 
org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> 18:45:14 INFO: I/O exception (java.net.SocketException) caught when
> processing request to 
{}->https://urldefense.proofpoint.com/v2/url?u=http-3A__nexus.onap.org-3A80=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=Ms-DNhR23dO4sQFfYRm4ow=9BsdxCi7U

Re: [onap-discuss] oparent 1.2.1 released

[Gary Wu]

Hi Yan,

It’s recommended to upgrade oparent to 1.2.1; not a must.

The settings.xml should be placed in your local ~/.m2/ directory, where you 
should already have one; the change is just to add the additional property 
definitions.  LF has already taken care of doing this in the Maven build 
environments in Jenkins.

Thanks,
Gary

From: Yan Yang [mailto:yangya...@chinamobile.com]
Sent: Thursday, September 20, 2018 6:17 PM
To: onap-discuss@lists.onap.org; Gary Wu 
Subject: 答复: [onap-discuss] oparent 1.2.1 released

Hi Gary,

I would like to know :

1.   If all components must upgrade oparent to 1.2.1 and add the 
settings.xml file

2.   Where does the setting.xml file need to be placed? Thanks.


Best Regards,
Yan
发件人: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> 
[mailto:onap-discuss@lists.onap.org] 代表 Gary Wu
发送时间: 2018年9月19日 2:00
收件人: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
主题: [onap-discuss] oparent 1.2.1 released

Hi all,

oparent 1.2.1 has been released.

Notable changes:

・ Additional standard 3rd party library versions courtesy of the PTL 
taskforce: https://git.onap.org/oparent/tree/dependencies/pom.xml
・ Nexus URL definitions have been refactored out of the oparent pom and 
are now expected in your build environment settings.xml.  This helps facilitate 
folks who need to do builds in a non-internet environment without having to 
recompile oparent.  For a sample ONAP settings.xml with the required 
properties, see https://git.onap.org/oparent/tree/settings.xml
・ JaCoCo bumped to version 0.8.2.

Please upgrade at your earliest convenience.

Thanks,
Gary




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

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

[onap-discuss] Jenkins not working

[Gary Wu]

Hi helpdesk,

Jenkins has a huge backlog and minions are spawning.  Can you take a look?

Thanks,
Gary



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

View/Reply Online (#12660): https://lists.onap.org/g/onap-discuss/message/12660
Mute This Topic: https://lists.onap.org/mt/26231356/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] [ci-management][integration] Jenkins Job Failure

[Gary Wu]

Hi Guangrong,

Yes, you need to formally release the holmes-actions 1.2.0 artifact by emailing 
LF helpdesk.  After they’re done with the release process, then the artifact 
will become available in the releases repo.

Thanks,
Gary

From: Guangrong Fu [mailto:steven20...@gmail.com]
Sent: Tuesday, September 25, 2018 6:44 PM
To: Gary Wu 
Cc: onap-discuss ; fu.guangr...@zte.com.cn
Subject: Re: [ci-management][integration] Jenkins Job Failure

Hi Gary,

Yes, I was talking about maven builds.

Although I've changed the version to 1.2.0, the artifact seemed to be pushed 
into the staging repo rather than the releases repo. That's how the error came 
into being.

You could find the following verify jobs are still failing due to the missing 
of holmes-actions:1.2.0 from the release repo.

https://gerrit.onap.org/r/#/c/68791/
https://gerrit.onap.org/r/#/c/68793/
https://gerrit.onap.org/r/#/c/68789/

Do I have to inform the help desk to move the maven artifact into the releases 
repo as well as what we usually do to the docker artifacts?

Regards,
Guangrong

Gary Wu mailto:gary.i...@huawei.com>>于2018年9月26日周三 
上午9:18写道：
Hi Guangrong,

Sorry, I thought you were talking about docker builds, but looks like you’re 
talking about maven builds?

For maven build release jobs, it is correct that SNAPSHOT dependencies from 
outside the repo are not allowed.  So, as an example, for 
https://jenkins.onap.org/view/holmes/job/holmes-dsa-master-release-version-java-daily/
 to pass you must depend on a release version of the holmes-actions artifact.

Thanks,
Gary


From: Guangrong Fu [mailto:steven20...@gmail.com<mailto:steven20...@gmail.com>]
Sent: Tuesday, September 25, 2018 5:35 PM

To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>; 
fu.guangr...@zte.com.cn<mailto:fu.guangr...@zte.com.cn>
Subject: Re: [ci-management][integration] Jenkins Job Failure

Gary,

It'll be better for us to retrieve the artifact using its SNAPSHOT version. 
Some use cases are still being tested at the moment. Bugs could rise at any 
time. So changes for holmes-actions are inevitable.

But when I tried to compile other modules using holmes-actions 1.2.0-SNAPSHOT, 
the compiler complains that we are banned from using dependencies versioned as 
'SNAPSHOT'.

If I still want to use the snapshot version of some dependencies, what kind of 
changes shall I make in our Jenkins jobs?

Thanks,
Guangrong

Gary Wu mailto:gary.i...@huawei.com>>于2018年9月26日周三 
上午12:16写道：
Hi Guangrong,

It depends on what you are trying to do.

If you are ready to release holmes-actions 1.2.0, you need to email LF helpdesk 
to ask that they release that artifact.  Once that’s done, the 1.2.0 artifact 
will become available in the releases repo.

If you’re trying to do some testing with holmes-actions 1.2.0 as a staging 
artifact, then you need to update your job to retrieve that artifact from the 
staging repo.

If you’re actually trying do something using holmes-actions 1.2.0-SNAPSHOT, 
then you need to update your job to retrieve that artifact from the staging 
repo.

Thanks,
Gary

From: Guangrong Fu [mailto:steven20...@gmail.com<mailto:steven20...@gmail.com>]
Sent: Tuesday, September 25, 2018 3:45 AM
To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>; 
fu.guangr...@zte.com.cn<mailto:fu.guangr...@zte.com.cn>

Subject: [ci-management][integration] Jenkins Job Failure

Hi Gary,

The daily release jobs for Holmes have been failing for a long time.

Initially, it was because they depended on the snapshot version of the 
'holmes-actions' module. But after I changed the version of the dependency to 
'1.2.0', the compilation failure went on occurring. It seems that the artifact 
'org.onap.holmes.common:holmes-actions:1.2.0' is stored in the staging repo 
rather than the release one.

You could find the artifact at 
https://nexus.onap.org/content/groups/staging/org/onap/holmes/common/holmes-actions/.

The error of the Jenkins job is


Any thoughts about this? What am I supposed to do now?

Thanks a ton in advance.

BR,
Guangrong


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

View/Reply Online (#12648): https://lists.onap.org/g/onap-discuss/message/12648
Mute This Topic: https://lists.onap.org/mt/26221836/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] [ci-management][integration] Jenkins Job Failure

[Gary Wu]

Hi Guangrong,

Sorry, I thought you were talking about docker builds, but looks like you’re 
talking about maven builds?

For maven build release jobs, it is correct that SNAPSHOT dependencies from 
outside the repo are not allowed.  So, as an example, for 
https://jenkins.onap.org/view/holmes/job/holmes-dsa-master-release-version-java-daily/
 to pass you must depend on a release version of the holmes-actions artifact.

Thanks,
Gary


From: Guangrong Fu [mailto:steven20...@gmail.com]
Sent: Tuesday, September 25, 2018 5:35 PM
To: Gary Wu 
Cc: onap-discuss ; fu.guangr...@zte.com.cn
Subject: Re: [ci-management][integration] Jenkins Job Failure

Gary,

It'll be better for us to retrieve the artifact using its SNAPSHOT version. 
Some use cases are still being tested at the moment. Bugs could rise at any 
time. So changes for holmes-actions are inevitable.

But when I tried to compile other modules using holmes-actions 1.2.0-SNAPSHOT, 
the compiler complains that we are banned from using dependencies versioned as 
'SNAPSHOT'.

If I still want to use the snapshot version of some dependencies, what kind of 
changes shall I make in our Jenkins jobs?

Thanks,
Guangrong

Gary Wu mailto:gary.i...@huawei.com>>于2018年9月26日周三 
上午12:16写道：
Hi Guangrong,

It depends on what you are trying to do.

If you are ready to release holmes-actions 1.2.0, you need to email LF helpdesk 
to ask that they release that artifact.  Once that’s done, the 1.2.0 artifact 
will become available in the releases repo.

If you’re trying to do some testing with holmes-actions 1.2.0 as a staging 
artifact, then you need to update your job to retrieve that artifact from the 
staging repo.

If you’re actually trying do something using holmes-actions 1.2.0-SNAPSHOT, 
then you need to update your job to retrieve that artifact from the staging 
repo.

Thanks,
Gary

From: Guangrong Fu [mailto:steven20...@gmail.com<mailto:steven20...@gmail.com>]
Sent: Tuesday, September 25, 2018 3:45 AM
To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>; 
fu.guangr...@zte.com.cn<mailto:fu.guangr...@zte.com.cn>

Subject: [ci-management][integration] Jenkins Job Failure

Hi Gary,

The daily release jobs for Holmes have been failing for a long time.

Initially, it was because they depended on the snapshot version of the 
'holmes-actions' module. But after I changed the version of the dependency to 
'1.2.0', the compilation failure went on occurring. It seems that the artifact 
'org.onap.holmes.common:holmes-actions:1.2.0' is stored in the staging repo 
rather than the release one.

You could find the artifact at 
https://nexus.onap.org/content/groups/staging/org/onap/holmes/common/holmes-actions/.

The error of the Jenkins job is
[image.png]

Any thoughts about this? What am I supposed to do now?

Thanks a ton in advance.

BR,
Guangrong


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

View/Reply Online (#12647): https://lists.onap.org/g/onap-discuss/message/12647
Mute This Topic: https://lists.onap.org/mt/26221836/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] [ci-management][integration] Jenkins Job Failure

[Gary Wu]

Hi Guangrong,

It depends on what you are trying to do.

If you are ready to release holmes-actions 1.2.0, you need to email LF helpdesk 
to ask that they release that artifact.  Once that’s done, the 1.2.0 artifact 
will become available in the releases repo.

If you’re trying to do some testing with holmes-actions 1.2.0 as a staging 
artifact, then you need to update your job to retrieve that artifact from the 
staging repo.

If you’re actually trying do something using holmes-actions 1.2.0-SNAPSHOT, 
then you need to update your job to retrieve that artifact from the staging 
repo.

Thanks,
Gary

From: Guangrong Fu [mailto:steven20...@gmail.com]
Sent: Tuesday, September 25, 2018 3:45 AM
To: Gary Wu 
Cc: onap-discuss ; fu.guangr...@zte.com.cn
Subject: [ci-management][integration] Jenkins Job Failure

Hi Gary,

The daily release jobs for Holmes have been failing for a long time.

Initially, it was because they depended on the snapshot version of the 
'holmes-actions' module. But after I changed the version of the dependency to 
'1.2.0', the compilation failure went on occurring. It seems that the artifact 
'org.onap.holmes.common:holmes-actions:1.2.0' is stored in the staging repo 
rather than the release one.

You could find the artifact at 
https://nexus.onap.org/content/groups/staging/org/onap/holmes/common/holmes-actions/.

The error of the Jenkins job is
[image.png]

Any thoughts about this? What am I supposed to do now?

Thanks a ton in advance.

BR,
Guangrong


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

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

[onap-discuss] Remove unused Beijing Jenkins jobs

[Gary Wu]

Hi PTLs,

There are still a large number of Jenkins jobs building beijing artifacts 
daily.  If you no longer need them, please remove the unused beijing jobs from 
Jenkins so we can lighten the load.

Thanks,
Gary



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

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

[onap-discuss] Scheduling of Daily Jobs

[Gary Wu]

Hi PTLs,

Currently all of the Daily Jenkins jobs (Java/Docker release jobs) are 
scheduled for around noon UTC (8 AM Eastern), which imposes severe resource 
contention on nexus and nexus3 for the next several hours and causing some of 
them to fail due to timeouts.

To fix this, I will be submitting a change to spread the load throughout the 
day instead of having them all run at the same time.  Please let me know if you 
have any concerns.

Thanks,
Gary



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

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

[onap-discuss] onapci.org maintenance

[Gary Wu]

Hi all,

onapci.org will be undergoing maintenance and upgrades this week.  During this 
time, onapci.org Jenkins will be placed into read-only mode, and Grafana will 
be unavailable.  This also means that the daily deployment tests will be 
suspended for the rest of the week.

I hope to have everything up and running again before Monday.

Thanks,
Gary



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

View/Reply Online (#14290): https://lists.onap.org/g/onap-discuss/message/14290
Mute This Topic: https://lists.onap.org/mt/28613126/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] Images Missing in Release Manifest

[Gary Wu]

Hi all,

As of now the following images are still NOT accounted for, i.e. neither 
released nor declared to be unused for Casablanca:

onap/dcae-tools,1.3-STAGING-latest
onap/network-discovery,latest
onap/service-decomposition,latest
onap/spike,1.0-STAGING-latest

Would the owners please respond with your dispositions on these images above?

Thanks,
Gary

_
From: Gary Wu
Sent: Wednesday, November 14, 2018 2:59 PM
To: onap-discuss@lists.onap.org Group ; 
onap-rele...@lists.onap.org
Subject: Images Missing in Release Manifest


Hi all,

The following images are used in the OOM helm charts but do not have a 
corresponding entry in the release manifest.  Can you please add the 
appropriate release images to the release manifest?

onap/aaf/aaf_cass,2.1.7
onap/ccsdk-controllerblueprints,latest
onap/dcae-be,1.3-STAGING-latest
onap/dcae-dt,1.2-STAGING-latest
onap/dcae-fe,1.3-STAGING-latest
onap/dcae-tools,1.3-STAGING-latest
onap/dcae-tosca-app,1.3-STAGING-latest
onap/fproxy,2.1-STAGING-latest
onap/music/cassandra_music,3.0.0
onap/music/prom,1.0.5-latest
onap/network-discovery,latest
onap/org.onap.dcaegen2.deployments.pnda-bootstrap-container,5.0.0
onap/org.onap.dcaegen2.deployments.pnda-mirror-container,5.0.0
onap/rproxy,2.1-STAGING-latest
onap/service-decomposition,latest
onap/spike,1.0-STAGING-latest
onap/tproxy-config,2.1-STAGING-latest

Thanks,
Gary




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

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

[onap-discuss] Anyone still using SB02, SB04, SB06?

[Gary Wu]

Hi all,

Is anyone still using the following Wind River environments?

Integration-SB-02
Integration-SB-04
Integration-SB-06

If not, we'd like to shut them down to reduce the load in the lab.

Thanks,
Gary



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

View/Reply Online (#14106): https://lists.onap.org/g/onap-discuss/message/14106
Mute This Topic: https://lists.onap.org/mt/28375067/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][sdc] SDC images

[Gary Wu]

I’ve submitted the manifest change.

Thanks,
Gary

From: Gildas Lanilis
Sent: Monday, November 26, 2018 4:34 PM
To: Jessica Wagantall ; Yunxia Chen 
; Gary Wu 
Cc: michael.la...@intl.att.com; onap-discuss@lists.onap.org; 
catherine.lefe...@intl.att.com; BRIAN D FREEMAN ; Yang Xu 
(Yang, Fixed Network) 
Subject: RE: [integration][sdc] SDC images

Helen, Gary,

The docker-manifect for SDC is not updated yet.
According the commit https://gerrit.onap.org/r/#/c/73302/ that generated the 
build and the docker image, the new version is 1.3.5.

Could we do something to move forward?

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

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

Thanks for this Michael. I have now released all the SDC dockers

Let me know if I can help on anything else

Jess

On Mon, Nov 26, 2018 at 2:47 PM Yunxia Chen 
mailto:helen.c...@huawei.com>> wrote:
Thank you Michael !

Please also submit the manifest change request and we will merge it once the 
release image is available.

Regards,

Helen Chen

From: "Lando,Michael" 
mailto:michael.la...@intl.att.com>>
Date: Monday, November 26, 2018 at 2:35 PM
To: Jessica Wagantall 
mailto:jwagant...@linuxfoundation.org>>, Helen 
Chen 00725961 mailto:helen.c...@huawei.com>>
Cc: onap-discuss 
mailto: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,

[ichael 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<mailto: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<mailto: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<https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_sdc-2Dsdc-2Dtosca_job_sdc-2Dsdc-2Dtosca-2Dmaster-2Drelease-2Dversion-2Djava-2Ddaily_1_console=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=FYvXSElfSmWIXOeZxWIxQysejuz9-TXmaL6uftBh8MY=0uk-SRcBkaUFRKi5XZ3hEBU3FDxMqBLvNkGns6T5gSY=_PNFhzN5Q8nK5tQKamZ8NDITFe7fluxKYys7PUXWZfQ=>

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 (#14073): https://lists.onap.org/g/onap-discuss/message/14073
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]
-=-=-=-=-=-=-=-=-=-=-=-

[onap-discuss] Wind River daily deployment tests suspended

[Gary Wu]

Hi all,

Due to Wind River lab infrastructure issues, we need to suspend the daily 
Release and Staging deployment tests until further notice.

Thanks,
Gary



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

View/Reply Online (#13824): https://lists.onap.org/g/onap-discuss/message/13824
Mute This Topic: https://lists.onap.org/mt/28194688/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] Wind River daily deployment tests suspended

[Gary Wu]

Hi all,

The Wind River daily Release and Staging deployment tests have been restored.

Thanks,
Gary

From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On 
Behalf Of Gary Wu
Sent: Saturday, November 17, 2018 8:31 AM
To: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Subject: [onap-discuss] Wind River daily deployment tests suspended

Hi all,

Due to Wind River lab infrastructure issues, we need to suspend the daily 
Release and Staging deployment tests until further notice.

Thanks,
Gary




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

View/Reply Online (#13836): https://lists.onap.org/g/onap-discuss/message/13836
Mute This Topic: https://lists.onap.org/mt/28194688/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 ] EXTAPI-122

[Gary Wu]

Hi Matthieu,

We deploy OOM once a day.  This chart shows, for each OOM deployment, the 
number of times your container got killed and restarted by Kubernetes.  It has 
nothing to do with gerrit.

If your container is getting killed/restarted by Kubernetes, it means that your 
liveness probe is configured incorrectly in your OOM helm chart.  The target is 
to fix the liveness probe configuration so that there are zero restarts even if 
the deployment environment is arbitrarily slow or congested on any particular 
day.

Thanks,
Gary

From: matthieu.geereba...@orange.com [mailto:matthieu.geereba...@orange.com]
Sent: Monday, September 17, 2018 2:15 AM
To: Gary Wu 
Cc: NGUYEN Quoc Nghia IMT/OLS ; DEBEAU Eric 
IMT/OLN 
Subject: [ ONAP ] EXTAPI-122

Hi Gary,

About this ticket, I do not understand graph, externalapi compare to the other 
modules. Reboot seem to occures a lot some days while some other it's only 
few.. What should be the reasonable limit for nbi 3.0.0 latest ? ( 
externalapi/nbi :3.0.0-latest )

https://jira.onap.org/browse/EXTAPI-122

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

Do you think we are facing an app instability ? is it relative to the use of 
some magic world we can use in gerrit or is it independant ?
Thank you for your advice



[logo Orange]<http://www.orange.com/>

Matthieu Geerebaert
Software architect
Product Owner API Designer
ORANGE/IMT/OLS/ARSEC/API

fixe :  +33 5 56 53 09 47 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%204%2037%2044%2050%2049%20>
mobile :  +33 6 79 16 83 23 
<https://monsi.sso.francetelecom.fr/index.asp?target=http%3A%2F%2Fclicvoice.sso.francetelecom.fr%2FClicvoiceV2%2FToolBar.do%3Faction%3Ddefault%26rootservice%3DSIGNATURE%26to%3D+33%206%2089%2075%2086%2014%20>
matthieu.geereba...@orange.com<mailto:matthieu.geereba...@orange.com>


_



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

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

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

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



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

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

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

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

Thank you.

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

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

[onap-discuss] oparent 1.2.1 released

[Gary Wu]

Hi all,

oparent 1.2.1 has been released.

Notable changes:

*   Additional standard 3rd party library versions courtesy of the PTL 
taskforce: https://git.onap.org/oparent/tree/dependencies/pom.xml
*   Nexus URL definitions have been refactored out of the oparent pom and 
are now expected in your build environment settings.xml.  This helps facilitate 
folks who need to do builds in a non-internet environment without having to 
recompile oparent.  For a sample ONAP settings.xml with the required 
properties, see https://git.onap.org/oparent/tree/settings.xml
*   JaCoCo bumped to version 0.8.2.

Please upgrade at your earliest convenience.

Thanks,
Gary



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

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

Re: [onap-discuss] [ONAP Helpdesk #44073] [integration] IOException during gerrit submission

[Gary Wu via RT]

I think it may have something to do with whatever Andy fixed this morning.  
I've copied the email thread below.

Thanks,
Gary


-

Greetings folks,

I saw an error this morning related to this. It should now be resolved.

-Andy-

On 08/14/2017 07:31 AM, WONNELL, SKIP wrote:
> Yes, I see the same issue in APPC using ssh.
> 
>  
> 
> Skip
> 
>  
> 
> *From:* onap-discuss-boun...@lists.onap.org
> [mailto:onap-discuss-boun...@lists.onap.org] *On Behalf Of *EFRAT, 
> ELHAY
> *Sent:* Monday, August 14, 2017 12:05 AM
> *To:* zhao.huab...@zte.com.cn; onap-discuss@lists.onap.org
> *Subject:* Re: [onap-discuss] Can't push code to ONAP Gerrit today
> 
>  
> 
> Same happens with ssh ? **
> 
> * *
> 
> --
> --
> 
> *From:*onap-discuss-boun...@lists.onap.org
> <mailto:onap-discuss-boun...@lists.onap.org> on behalf of 
> zhao.huab...@zte.com.cn <mailto:zhao.huab...@zte.com.cn>
> *Sent:* Monday, August 14, 2017 4:56:45 AM
> *To:* onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org>
> *Subject:* [onap-discuss] Can't push code to ONAP Gerrit today
> 
> Hi,
> 
>  
> 
> I run into this when trying to push code to ONAP Gerrit:
> 
>  
> 
> remote: java.io.IOException:
> RestClientException{statusCode=Optional.of(403), errorCollections=[]}
> 
> To http://huabingz...@gerrit.onap.org/r/a/msb/apigateway
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__HuabingZhao-40ger
> rit.onap.org_r_a_msb_apigateway=DwQFAg=LFYZ-o9_HUMeMTSQicvjIg=T2
> g18byrjQaNP_c0GkWdpA=oSgoQYMfM5e6eOzh6dWt30j99aSDy_hPoQT4AA1qAww=w
> pWC-DZZ4Do3r40uL1hvJ1Jhtwco0Q0G96Qq4eSp76o=>
> 
>  ! [remote rejected] HEAD -> refs/for/master (Failed to check whether 
> or not issue MSB-19 exists)
> 
>  
> 
> (MSB-19 does exist in ONAP jira https://jira.onap.org/browse/MSB-19
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_br
> owse_MSB-2D19=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=T2g18byrjQaNP_c0GkWd
> pA=oSgoQYMfM5e6eOzh6dWt30j99aSDy_hPoQT4AA1qAww=V-0C0KrDwl3ceIg_lPY
> p4yhSzZzJUP_PbuByo58642s=>)
> 
>  
> 
> Some of my colleagues have the same  problems. 
> 
> Is it an issue of ONAP Gerrit or something is not correct when I push 
> the commit?
> 
>  
> 
> Does anyone have any idea?
> 
>  
> 
> Thanks for your help.
> 
>  
> 
> Huabing
> 
>  
> 
>  
> 
>  
> 
>  
> 
> This message and the information contained herein is proprietary and 
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_a
> bout_email-2Ddisclaimer=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=T2g18byrjQ
> aNP_c0GkWdpA=oSgoQYMfM5e6eOzh6dWt30j99aSDy_hPoQT4AA1qAww=ocU2sKJGI
> eba4o6iK65liGgCJ7x8Co8AA-vXqIJfywM=>
> 
> 
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
> 

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


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 14, 2017 1:54 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #44073] [integration] IOException during gerrit 
submission

Awesome Gary! 

Were you able to notice what made the difference? 

Thanks!
Jess.. 

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

Re: [onap-discuss] [ONAP Helpdesk #44073] [integration] IOException during gerrit submission

[Gary Wu via RT]

Hi Jessica,

It seems to be working now.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 14, 2017 1:20 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #44073] [integration] IOException during gerrit 
submission

Dear Gary, 

are you still seeing these issues?
Can you please show me the commit message as well as the error you are getting?

Thanks!
Jess

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

[onap-discuss] [linuxfoundation.org #44094] RE: [linuxfoundation.org #44094] Re: [linuxfoundation.org #44094] RE: [ONAP Helpdesk #44094] 答复: Re: 答复: [integration] RE: About CI job Script for python pr

[Gary Wu via RT]

Andrew/Jess, since we don't have direct access to these environments, can you 
help check them to see if redis is running?

Thanks,
Gary

-Original Message-
From: fu.jin...@zte.com.cn via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, August 10, 2017 5:52 PM
To: zhang.maope...@zte.com.cn
Cc: Gary Wu <gary.i...@huawei.com>; onap-discuss@lists.onap.org
Subject: 答复: [linuxfoundation.org #44094] Re: [linuxfoundation.org #44094] RE: 
[ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About CI job 
Script for python project in ONAP

Hi Andrew,Jess and Gary:

Thanks for your help, I can see the node for redis in Jenkins now.

But unit test for vfc-nfvo-lcm still can not passed, from the log in jenkins, I 
think redis is not started in the redis node, can you help me to check it?

Thanks,

Jinhua










原始邮件



发件人： <onap-helpd...@rt.linuxfoundation.org>
收件人：张茂鹏10030173
抄送人：傅锦华10108953 <gary.i...@huawei.com> <onap-discuss@lists.onap.org>
日 期 ：2017年08月11日 02:09
主 题 ：[linuxfoundation.org #44094] Re: [linuxfoundation.org #44094] RE: [ONAP 
Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About CI job 
Script for python project in ONAP





Gary's changes have been merged in and the redis image has been built.
I've added a new minion template to allow the image to come online.

-Andy-

On 08/10/2017 09:55 AM, Gary Wu via RT wrote:
> 
> Sorry about that.  I’ve submitted a fix into ci-management: 
> https://gerrit.onap.org/r/#/c/7229/
> 
> Thanks,
> Gary
> 
> From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn]
> Sent: Wednesday, August 09, 2017 5:54 PM
> To: onap-helpd...@rt.linuxfoundation.org
> Cc: zhang.maope...@zte.com.cn Gary Wu <gary.i...@huawei.com> 
> onap-discuss@lists.onap.org
> Subject: 答复: [ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] 
> RE: About CI job Script for python project in ONAP
> 
> 
> Hi Jess,
> 
> I think Gary's script has some mistakes, you can see the following log
> 
> 18:13:06 openstack: mv: cannot stat '/tmp/redis-4.0.1/redis-server': No 
> such file or directory
> 
> Gary's Scripts(Path of redis-server and redis.conf are wrong)
> 
># 2. set conf file and init script
> 
> mv /tmp/redis-4.0.1/redis-server /etc/init.d/redis-server
> 
> chmod +x /etc/init.d/redis-server
> 
> mv /tmp/redis-4.0.1/redis.conf /etc/redis.conf
> 
> 
> 
> Thanks,
> 
> Jinhua
> 
> 
> 
> 
> 
> 
> 原始邮件
> 发件人： 
> <onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>>
> 收件人：张茂鹏10030173
> 抄送人：傅锦华10108953 <gary.i...@huawei.com<mailto:gary.i...@huawei.com>> 
> <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
> 日 期 ：2017年08月10日 07:01
> 主 题 ：[ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About 
> CI job Script for python project in ONAP
> 
> 
> Dear Maopeng,
> 
> I am currently working on this.
> Looking at the current failures found here:
> https://jenkins.onap.org/job/ci-management-merge-packer-ubuntu-16.04-redis/1/console
> 
> Will let you know once I get this resolved
> 
> Thanks!
> Jess
> 
> 
> 
> 
> 

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

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

[onap-discuss] [linuxfoundation.org #44094] RE: [ONAP Helpdesk #44094] 答复: Re: 答复: [integration] RE: About CI job Script for python project in ONAP

[Gary Wu via RT]

Sorry about that.  I’ve submitted a fix into ci-management: 
https://gerrit.onap.org/r/#/c/7229/

Thanks,
Gary

From: fu.jin...@zte.com.cn [mailto:fu.jin...@zte.com.cn]
Sent: Wednesday, August 09, 2017 5:54 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: zhang.maope...@zte.com.cn; Gary Wu <gary.i...@huawei.com>; 
onap-discuss@lists.onap.org
Subject: 答复: [ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: 
About CI job Script for python project in ONAP


Hi Jess,

I think Gary's script has some mistakes, you can see the following log

18:13:06 openstack: mv: cannot stat '/tmp/redis-4.0.1/redis-server': No 
such file or directory

Gary's Scripts(Path of redis-server and redis.conf are wrong)

   # 2. set conf file and init script

mv /tmp/redis-4.0.1/redis-server /etc/init.d/redis-server

chmod +x /etc/init.d/redis-server

mv /tmp/redis-4.0.1/redis.conf /etc/redis.conf



Thanks,

Jinhua






原始邮件
发件人： 
<onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>>;
收件人：张茂鹏10030173;
抄送人：傅锦华10108953; <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>; 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;
日 期 ：2017年08月10日 07:01
主 题 ：[ONAP Helpdesk #44094] 答复: Re: [onap-discuss]答复: [integration] RE: About 
CI job Script for python project in ONAP


Dear Maopeng,

I am currently working on this.
Looking at the current failures found here:
https://jenkins.onap.org/job/ci-management-merge-packer-ubuntu-16.04-redis/1/console

Will let you know once I get this resolved

Thanks!
Jess





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

Re: [onap-discuss] [ONAP Helpdesk #43030] [integration] Jenkins jobs not updating Gerrit

[Gary Wu via RT]

Hi Jess,

Seems it is working again now.  If you look at e.g. 
https://gerrit.onap.org/r/#/c/5789/ you can see that the first couple of jobs 
that got triggered did not update Gerrit, but the final "recheck" did.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, July 13, 2017 4:48 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #43030] [integration] Jenkins jobs not updating Gerrit

Dear Gary, 

Can you please let me know which job are you wanting to see updates from? 

Thansk a ton
Jess. 

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

Re: [onap-discuss] [ONAP Helpdesk #43359] Jenkins is down

[Gary Wu via RT]

Looks like it's working now.  Thanks!
-Gary

-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Friday, July 21, 2017 11:02 AM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #43359] Jenkins is down

On Fri Jul 21 13:21:36 2017, agrimberg wrote:
> On 07/21/2017 10:11 AM, Gary Wu via RT wrote:
> 
> > Hi helpdesk,
> > 
> > http://jenkins.onap.org/ is not responding.  Can you take a look?
> > 
> > Thanks,
> > Gary
> 
> Greetings Gary,
> 
> It looks like we are, or were having some issues getting to the 
> provider [0]. I suggest you subscribe to our master status page [1]. 
> At some point ONAP will likely get it's own dedicated page, but right 
> now this is the best option.
> 
> -Andy-
> 
> [0] https://status.linuxfoundation.org/incidents/b1sv4m6zb7tr
> [1] https://status.linuxfoundation.org/

As of 20 minutes ago this issue should be fully resolved.

-Andy-

--
Andrew Grimberg
The Linux Foundation

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

[onap-discuss] [linuxfoundation.org #43994] RE: [ONAP Helpdesk #43994] RE: 答复：[integration] Jenkins Merge Failure

[Gary Wu via RT]

Hi Jessica,

Am I supposed to be able to access that link?  If not yet, can I be granted 
read access?

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 07, 2017 1:57 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: fu.guangr...@zte.com.cn; onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #43994] RE: 答复：[integration] Jenkins Merge Failure

Duplicate of https://rt-sso.linuxfoundation.org/Ticket/Display.html?id=43995

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

Re: [onap-discuss] [ONAP Helpdesk #44125] Independent project artifact release process

[Gary Wu via RT]

Hi Andy,

Thanks for your feedback.  I would like to do a trial run of this process with 
oparent and document the instructions.

To confirm, is the preferred way to do a staging build via the 
"-release-version-java-daily" jobs?  Do we currently have any documentation on 
how to setup/use the staging build jobs?  For example, I think it requires a 
version.properties file to be defined in the repo; not sure if there are other 
requirements.

For the GPG signed tag, do we have any recommended instructions for the project 
committers/PTLs to do so themselves, or should we assume that LFRE will take 
care of this for the time being?

Thanks,
Gary


-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, August 16, 2017 11:59 AM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [ONAP Helpdesk #44125] Independent project artifact release process

Greetings Gary,

On 08/16/2017 11:34 AM, Gary Wu via RT wrote:

> Resending since I didn't get a ticket number back for some reason last time.

Not certain why you didn't. The original ticket, which I've merged this into is 
44125

> From: Gary Wu
> Sent: Wednesday, August 09, 2017 12:37 PM
> To: 'helpd...@onap.org' <helpd...@onap.org>
> Cc: onap-discuss@lists.onap.org
> Subject: [integration] Independent project artifact release process
> 
> Hi helpdesk,
> 
> ONAP is moving toward a model where each project/repo will be 
> releasing its own artifacts and versions, and cross-repo dependencies 
> are on release artifacts only (i.e. no SNAPSHOT/staging dependencies).
> Integration will be piloting this with oparent and clamp repos to work 
> out all the kinks.
> 
> To that end, we will need a clear process for individual projects to 
> version bump and release their own artifacts.
> 
> ONAP currently has Jenkins job definitions that will deploy release 
> artifact candidates to staging. What seems to be missing is a way for 
> a project to pick a candidate from staging and formally release it 
> into the Releases repo. Does this process exist? If so, can you point 
> me to some documentation on how this process works? If not, can you 
> share your thoughts on how we can best implement this last step?

The closest we currently have is the process that OpenDaylight has been 
operating with for their odlparent project which as of the current release 
cycle has broken off to doing independent releases of it's one.
In fact during the Nitrogen cycle it's already had at least 4 releases that I'm 
aware of!

The current process that has been in use in ODL by odlparent is detailed in the 
lead mail in this [0] mailing list thread.

LF is working on ways that the we can grant more of the process control to the 
projects themselves but we don't currently have everything needed for it just 
yet.

To get the heart of your request the current way for an ONAP project to 
formally do a release at present would be as follows:

1) A staging build has happened. In the job logs there will be a notice as to 
what the staging repository that was created is. This needs to be captured by a 
project committer / PTL that will be requesting a release

2) Any testing that needs to be performed against the artifacts is performed.

3) A helpdesk ticket is opened requesting that LF Release Engineering perform a 
signing and release operation on the target staging repository

4) LFRE will pull the artifacts, GPG sign them, push a secondary staging 
repository with the signatures and then perform a release operation inside 
nexus which will cause it to transition both the requested staging repository 
and the signature repository to copy into the releases repository and then 
delete the staging repositories.

5) A GPG signed tag needs to be placed on the commit by either LFRE or 
preferably the PTL or a committer of the project with the release version

For docker images, we don't currently have as much automated tooling in place 
but the basic flow is:

1) Identify the STAGING docker slice that is to be released

2) Open a ticket with LF to release the specific docker

3) LFRE will pull the docker image and retag it into the nexus docker releases 
repository and push

4) The image should also then be pushed to dockerhub

Eventually, this will all get fully automated in some fashion with the correct 
checks and balances in place for restricting who can do what.
Once we have a good automation flow in place then it will probably be a matter 
of an authorized party submitting a gerrit change to a special repository / 
specially formatted comment to trigger Jenkins to perform operations on behalf 
of folks.

-Andy-

[0] https://lists.opendaylight.org/pipermail/dev/2017-August/003990.html

--
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] [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

[Gary Wu via RT]

Actually I think the key step is the next one where "clean deploy" is being 
done, but it doesn't hurt to have them all configured to have Releases be the 
top priority.

Also this should really be done for all Maven jobs including merge and verify, 
not just release-version.

The right long term solution is to remove the need to build against Staging at 
all, which will be addressed by the Independent Versioning process, but it 
probably will take some time for the whole of ONAP to transition to that 
process.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, September 06, 2017 1:52 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

Sure Gary, 

It seems that this should be a property of this step:
versions:set versions:update-child-modules versions:commit -B

Let me investigate how to do that in this case and get back to you 

Thanks!
Jess

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

Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

[Gary Wu via RT]

I just noticed the issue today, but I suspect it's been happening for a long 
time.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, September 06, 2017 2:10 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

Hey Gary, quick question.. did you saw this happening the time we released 
oparent 0.1.0?

Thanks!
Jess

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

Re: [onap-discuss] [ONAP Helpdesk #46299] RE: [integration] RE: Change in integration[master]: Add chrome drive installation and chrome download

[Gary Wu via RT]

Hi Kishore,

I tried to to run your test suite in my local machine, and it also failed.

The error is:


02:10:35 ++ mkdir -p /PROJECT/OpenSource/UbuntuEP/etc
02:10:35 mkdir: cannot create directory ‘/PROJECT’: Permission denied

The same error was also observed on the LF CSIT environment.

I don’t know if this is related to the selenium errors, but please make sure 
that you’re able to use run-csit.sh to run the tests successfully in your local 
environment without root privileges before submitting to gerrit.

Thanks,
Gary

From: KOYA, KISHORE [mailto:kk7...@att.com]
Sent: Wednesday, September 27, 2017 8:36 AM
To: onap-helpd...@rt.linuxfoundation.org; Gary Wu <gary.i...@huawei.com>
Cc: HOTZE, BECKY L <bk2...@att.com>; RAJU, CHINNAPPA <cr7...@att.com>; FLOOD, 
JERRY <jf9...@att.com>; onap-discuss@lists.onap.org; TALASILA, MANOOP 
<talas...@research.att.com>
Subject: RE: [ONAP Helpdesk #46299] RE: [integration] RE: Change in 
integration[master]: Add chrome drive installation and chrome download


Hi Gary,



Any updates on below issue?



Thanks ,

Kishore Koya

ECOMP Open Source

Call Me @ 469-831-7289

Email : kk7...@att.com<mailto:kk7...@att.com> | Q me @



-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Tuesday, September 26, 2017 9:25 PM
To: gary.i...@huawei.com<mailto:gary.i...@huawei.com>
Cc: HOTZE, BECKY L <bk2...@att.com<mailto:bk2...@att.com>>; RAJU, CHINNAPPA 
<cr7...@att.com<mailto:cr7...@att.com>>; FLOOD, JERRY 
<jf9...@att.com<mailto:jf9...@att.com>>; KOYA, KISHORE 
<kk7...@att.com<mailto:kk7...@att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; TALASILA, 
MANOOP <talas...@research.att.com<mailto:talas...@research.att.com>>
Subject: [ONAP Helpdesk #46299] RE: [integration] RE: Change in 
integration[master]: Add chrome drive installation and chrome download



Dear Gary,



Since we are using an ubuntu machine, I have built a new ubuntu image which you 
can check here:

https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_view_packer_job_ci-2Dmanagement-2Dpacker-2Dmerge-2Dubuntu-2D16.04-2Ddocker_7_console=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=t6xw3To2DNA95dIV83mG2w=dgQXqWWQ9f0bMvWwbAVknLkj-jfL315qdaEJRpNNP3A=qFqD96MUzIZZZko9GY2sN76I-5wtOFcLzeCoWm6FeQE=

google-chrome-stable seems to be getting properly installed.



Although, I am still facing the same issue in the job:

https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_job_portal-2Dmaster-2Dverify-2Dcsit-2Dtestsuite_31_console=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=t6xw3To2DNA95dIV83mG2w=dgQXqWWQ9f0bMvWwbAVknLkj-jfL315qdaEJRpNNP3A=vEd-VpEXUu4Np8CAndEzbpQRM46Y9ktxVBNZMeFsm40=



Could there be something else missing?



Thanks!

Jess

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

Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

[Gary Wu via RT]

Hi Huabing,

I suspect the issue is that the site ID in your distributionManagement tags is 
“onap-site”.  I believe the expected value is “ecomp-site”.

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
zhao.huab...@zte.com.cn
Sent: Tuesday, August 22, 2017 6:53 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins 
job issue


Hi Gary, Jessica,



This job has similar issue:

msb-apigateway-master-stage-site-java

https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/msb-apigateway-master-stage-site-java/3/console.log.gz



[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.6:stage-deploy (default-cli) on 
project msb-apigateway-parent: Error uploading site: Failed to transfer file: 
https://nexus.onap.org/content/sites/site/org/onap/msb/apigateway/1.0.0/staging/./dependencies.html<https://nexus.onap.org/content/sites/site/org/onap/msb/apigateway/1.0.0/staging/dependencies.html>.
 Return code is: 401 -> [Help 1]



Could you please help me with that?



Thanks,

Huabing
Original Mail
Sender:  
<onap-helpd...@rt.linuxfoundation.org<mailto:onap-helpd...@rt.linuxfoundation.org>>;
To:
CC:  
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;zhaohuabing10201488;
Date: 2017/08/22 06:39
Subject: [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue


Hi Huabing,

I've incorporated the staging plugin config below into oparent, and it looks 
like the MSB release-version jobs are completing successfully now.

Thanks,
Gary


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
Subject: [ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Sure, of course.

Basically the pom.xml needs to be containing the repositories, distribution 
management and staging plugin blocks.
Let's take the vid pom.xml as an example of the information your pom is missing.

Basically, the staging plugin definition needs to look like this:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging




You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/https://oss.sonatype.org/service/local/repositories/releases/content/%3c/url>>



Notice that the serverIDs are prefixed like "ecomp-" and not "onap-". This is a 
rename that still hasn't changed, but we are discussing about the impact on 
doing so.

Lastly, you will also need to update the distribution management:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Re

Re: [onap-discuss] [ONAP Helpdesk #44584] RE: Need Help on cli ci issues

[Gary Wu via RT]

Hi Kanagaraj,

I've submitted a change to CLI that should fix the issue.  Please review/merge.

https://gerrit.onap.org/r/#/c/8507/

Thanks,
Gary


-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Jessica Wagantall via 
RT
Sent: Wednesday, August 23, 2017 12:34 PM
To: Kanagaraj Manickam 
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [ONAP Helpdesk #44584] RE: Need Help on cli ci issues

for https://jenkins.onap.org/view/cli/job/cli-master-stage-site-java/4/console
We need to add the site information in the distribution management:

ecomp-site
dav:${nexusproxy}${sitePath}


Let me know if this helps. Otherwise, please let me know which other issues are 
you facing. 

Thanks!
Jess

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

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

[onap-discuss] [ONAP Helpdesk #44584] [linuxfoundation.org #44584] RE: ONAP JIRA CIMAN-23

[Gary Wu via RT]

Hi Kanagaraj,

There are unfortunately two different docker-maven-plugins in use in ONAP: one 
from io.fabric8, one from com.spotify.

The one that you’re using is from spotify, which needs a different JJB template 
for the docker job.
I’ve submitted a change to your CLI JJB file which changes it to use the 
correct docker job template for the spotify plugin.

https://gerrit.onap.org/r/#/c/8509/

Thanks,
Gary

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kanagaraj Manickam
Sent: Tuesday, August 22, 2017 11:53 PM
To: 'onap-helpd...@rt.linuxfoundation.org' 

Cc: 'onap-discuss@lists.onap.org' 
Subject: [onap-discuss] ONAP JIRA CIMAN-23
Importance: High



Dear LF team,

I have been blocked on ONAP JIRA issue CIMAN-23 and could you please help to 
fix it on or before M3 (24th Aug)

Thanks
Kanagaraj M

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

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!
***

From: Kanagaraj Manickam
Sent: 21 August 2017 19:35
To: 
onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org; Gildas 
Lanilis
Subject: RE: Need Help on cli ci issues

+cc’ed Gildas.

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

***
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: Kanagaraj Manickam
Sent: Monday, August 21, 2017 7:31 PM
To: 'onap-helpd...@rt.linuxfoundation.org'
Cc: onap-discuss@lists.onap.org
Subject: Need Help on cli ci issues

Hi LF team,

We are having issues on daily build of docker and release for CLI project and 
filed the issues CIMAN-22 and CIMAN-23 for the same.
Could you please help to fix them?  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

[onap-discuss] [ONAP Helpdesk #44643] [linuxfoundation.org #44643] RE: [VNFSDK -refrepo] Sonar build is failing with below error -Please help

[Gary Wu via RT]

Hi Murali,

The latest run of that job has completed successfully now, I think because of 
your fix in https://gerrit.onap.org/r/#/c/8271/.

Thanks,
Gary

From: Murali p
Sent: Tuesday, August 22, 2017 4:51 AM
To: onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org; Gary Wu <gary.i...@huawei.com>
Subject: [VNFSDK -refrepo] Sonar build is failing with below error -Please help

Hi,


https://jenkins.onap.org/view/vnfsdk/job/vnfsdk-refrepo-master-release-version-java-daily/lastBuild/console

The Build is successful but triggering sonar build is throwing error. Please 
help.



11:21:49 [vnfsdk-refrepo-master-release-version-java-daily] $ 
/w/tools/hudson.tasks.Maven_MavenInstallation/mvn33/bin/mvn -s 
/tmp/settings1508208698336776093.xml -gs 
/tmp/global-settings1081172466262618554.xml -DGERRIT_BRANCH=master 
-DPROJECT=vnfsdk/refrepo 
-DMVN=/w/tools/hudson.tasks.Maven_MavenInstallation/mvn33/bin/mvn 
-DGERRIT_REFSPEC=refs/heads/master "-DARCHIVE_ARTIFACTS= 
**/target/surefire-reports/*-output.txt" -DGERRIT_PROJECT=vnfsdk/refrepo 
-DSTACK_NAME=$JOB_NAME-$BUILD_NUMBER -DNone= clean deploy sonar:sonar 
-Dsonar.host.url=https://sonar.onap.org<https://sonar.onap.org/> -B 
-Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn

11:21:51 [INFO] Scanning for projects...

11:21:59 [ERROR] [ERROR] Some problems were encountered while processing the 
POMs:

11:21:59 [WARNING] 'parent.relativePath' of POM 
org.onap.vnfsdk.refrepo:vnfmarket-deployment:1.0.0 
(/w/workspace/vnfsdk-refrepo-master-release-version-java-daily/vnfmarket-be/deployment/pom.xml)
 points at org.onap.vnfsdk.refrepo:vnf-sdk-marketplace-core-parent instead of 
org.onap.vnfsdk.refrepo:vnfmarket, please verify your project structure @ line 
23, column 13

11:21:59 [FATAL] Non-resolvable parent POM for 
org.onap.vnfsdk.refrepo:vnfmarket-deployment:1.0.0: Could not find artifact 
org.onap.vnfsdk.refrepo:vnfmarket:pom:1.0.0 in staging 
(https://nexus.onap.org/content/repositories/staging/) and 
'parent.relativePath' points at wrong local POM @ line 23, column 13

11:21:59  @

11:21:59 [ERROR] The build could not read 1 project -> [Help 1]

11:21:59 [ERROR]

11:21:59 [ERROR]   The project 
org.onap.vnfsdk.refrepo:vnfmarket-deployment:1.0.0 
(/w/workspace/vnfsdk-refrepo-master-release-version-java-daily/vnfmarket-be/deployment/pom.xml)
 has 1 error

11:21:59 [ERROR] Non-resolvable parent POM for 
org.onap.vnfsdk.refrepo:vnfmarket-deployment:1.0.0: Could not find artifact 
org.onap.vnfsdk.refrepo:vnfmarket:pom:1.0.0 in staging 
(https://nexus.onap.org/content/repositories/staging/) and 
'parent.relativePath' points at wrong local POM @ line 23, column 13 -> [Help 2]

11:21:59 [ERROR]

11:21:59 [ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.

11:21:59 [ERROR] Re-run Maven using the -X switch to enable full debug logging.

11:21:59 [ERROR]

11:21:59 [ERROR] For more information about the errors and possible solutions, 
please read the following articles:

11:21:59 [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException

11:21:59 [ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

11:21:59 Build step 'Invoke top-level Maven targets' marked build as failure

11:21:59 $ ssh-agent -k


With regards,
Murali

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

[onap-discuss] [integration][ONAP Helpdesk #44285] RE: MSB Jenkins job issue

[Gary Wu via RT]

Hi Huabing,

I've incorporated the staging plugin config below into oparent, and it looks 
like the MSB release-version jobs are completing successfully now.  

Thanks,
Gary


-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, August 21, 2017 3:20 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org; zhao.huab...@zte.com.cn
Subject: [ONAP Helpdesk #44285] RE: MSB Jenkins job issue

Sure, of course. 

Basically the pom.xml needs to be containing the repositories, distribution 
management and staging plugin blocks.
Let's take the vid pom.xml as an example of the information your pom is 
missing. 

Basically, the staging plugin definition needs to look like this:

org.sonatype.plugins

nexus-staging-maven-plugin
1.6.7
true

${nexusproxy}

176c31dfe190a
ecomp-staging

 


You will also need the definition for the repositories, which looks like this:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}


ecomp-staging
VID Staging Repository

${nexusproxy}/${stagingNexusPath}



oss-snapshots
oss Central - Snapshots

https://oss.sonatype.org/service/local/repositories/releases/content/



Notice that the serverIDs are prefixed like "ecomp-" and not "onap-". This is a 
rename that still hasn't changed, but we are discussing about the impact on 
doing so. 

Lastly, you will also need to update the distribution management:


ecomp-releases
VID Release Repository

${nexusproxy}/${releaseNexusPath}


ecomp-snapshots
VID Snapshot Repository

${nexusproxy}/${snapshotNexusPath}



ecomp-site
dav:${nexusproxy}${sitePath}





Please feel free to add me as reviewer to your pom.xml changes and I can help 
further. 

I hope this information helps
Thanks!
Jess

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

Re: [onap-discuss] [ONAP Helpdesk #44584] RE: Need Help on cli ci issues

[Gary Wu via RT]

Looks like the docker image now builds fine on LF infrastructure, but the job 
is failing because the existing "docker push" script is hardcoded to assume 
"openecomp/" as the image name prefix instead of "onap/".

We'll probably need some refactoring for a more generic docker build job 
template for the spotify plugin.  Stay tuned.  

Thanks,
Gary

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Jessica Wagantall via 
RT
Sent: Wednesday, August 23, 2017 3:10 PM
To: Kanagaraj Manickam 
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [ONAP Helpdesk #44584] RE: Need Help on cli ci issues

https://gerrit.onap.org/r/#/c/8509/ is now reviewed and merged

https://gerrit.onap.org/r/#/c/8507/ looks good and just needs to be merged 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

Re: [onap-discuss] [ONAP Helpdesk #47175] No binaries in ONAP stagging repo

[Gary Wu via RT]

As of now I still don't see any of the older autorelease directories here:  
https://nexus.onap.org/content/repositories/, not sure if this is expected.

Can you send another message out once the restore is fully completed?

Thanks,
Gary

-Original Message-
From: Jeremy Phelps via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, October 18, 2017 10:00 AM
To: zhao.huab...@zte.com.cn
Cc: Gary Wu <gary.i...@huawei.com>; jwagant...@linuxfoundation.org; 
onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #47175] No binaries in ONAP stagging repo

Hi all,
We should be good now, restore of the older artifacts is currently in progress 
and I have kicked off a build of:
msb-java-sdk-master-release-version-java-daily

Please let me know if this resolves for you.
Jeremy

On Wed Oct 18 11:27:20 2017, talas...@research.att.com wrote:
> Yes, The Portal team realized the same issue today, we too had opened 
> below ticket to LF, earlier to this email.
> 
> “[linuxfoundation.org #46449] Portal/SDK jars missing from nexus maven 
> staging repository”
> 
> Manoop
> 
> 
> On 10/18/17, 11:15 AM, "onap-discuss-boun...@lists.onap.org on behalf 
> of Gary Wu via RT" <onap-discuss-boun...@lists.onap.org on behalf of 
> onap-helpd...@rt.linuxfoundation.org> wrote:
> 
> Hold on… it looks like all autorelease directories older than last 
> Friday got removed, which is a big issue for multiple teams.
> Catherine will be escalating for a restore.
> 
> Thanks,
> Gary
> 
> From: Gary Wu
> Sent: Wednesday, October 18, 2017 8:05 AM
> To: 'zhao.huab...@zte.com.cn' <zhao.huab...@zte.com.cn>; 
> jwagant...@linuxfoundation.org; helpd...@onap.org
> Cc: onap-discuss@lists.onap.org
> Subject: RE: No binaries in ONAP stagging repo
> 
> The directory autorelease-18453 doesn’t seem to exist on nexus right 
> now.  Maybe the autorelease directories get removed after a certain 
> time?
> 
> You’ll need to re-run the staging (-release-version-*) jobs to build 
> to staging/autorelease again.  After that, if the result is good, 
> please email LF to have them formally released into the Releases repo.
> 
> Thanks,
> Gary
> 
> From: zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>
> [mailto:zhao.huab...@zte.com.cn]
> Sent: Tuesday, October 17, 2017 11:40 PM
> To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>;
> jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>;
> helpd...@onap.org<mailto:helpd...@onap.org>
> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
> Subject: No binaries in ONAP stagging repo
> 
> 
> Hi Jess, Gary,
> 
> I found that the binary of msb java sdk has not been pushed to ONAP 
> stagging repository today.
> 
> Because of that, the wfengine jenkins job failed.
> 
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__jenkins.onap.org_view_vfc_job_vfc-2Dnfvo-2Dwfengine-2Dmaster-
> 2Dengine-2Dactiviti-2Dextension-2Dverify-2Djava_=DwIGaQ=LFYZ-
> o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-
> q_w=0LmhWnkxvOPOium09mgc1rMdFYVDBpbW0cdM-
> 2cR2nc=jmYekt5vUdIJWxrvV5A-zBm4ebFMpHWXPYD2Iw5ri64=
> 
> 
> 
> The msb-java-sdk-1.0.0 does exist at
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__nexus.onap.org=DwIGaQ=LFYZ-
> o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-
> q_w=0LmhWnkxvOPOium09mgc1rMdFYVDBpbW0cdM-
> 2cR2nc=jEy3cAEf5jesxDTdRj2pmAHa_wFxEA55PMPl1DMpEK4=
> <https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__nexus.onap.org=DwIGaQ=LFYZ-
> o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-
> q_w=0LmhWnkxvOPOium09mgc1rMdFYVDBpbW0cdM-
> 2cR2nc=jEy3cAEf5jesxDTdRj2pmAHa_wFxEA55PMPl1DMpEK4= ,> in 
> repository autorelease-18453 (staging:
> closed)<https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__nexus.onap.org_index.html-23view-2Drepositories-3Bautorelease-
> 2D18453-7Ebrowsestorage-7E_org_onap_msb_java-2Dsdk_msb-2Djava-
> 2Dsdk_1.0.0_msb-2Djava-2Dsdk-2D1.0.0.jar=DwIGaQ=LFYZ-
> o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-
> q_w=0LmhWnkxvOPOium09mgc1rMdFYVDBpbW0cdM-
> 2cR2nc=hzXt2qA7FifQDwL2DW00rMhA8eOjs-m54o_2UT36Nkk= >, but not in 
> stagging repo.
> 
> 
> 
> Is there anything I am supposed to do to fix this?
> 
> 
> 
> Thanks a lot,
> 
> Huabing
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
>  https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwIGaQ=LFYZ-
> o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-
> q_w=0LmhWnkxvOPOium09mgc1rMdFYVDBpbW0cdM-
> 2cR2nc=YQu8pJCVcUAP2S3O3DNVNh-4W0Tzm7ISSB8gXAhYz-U=
> 
> 




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

[onap-discuss] [ONAP Helpdesk #47175] [linuxfoundation.org #47175] RE: No binaries in ONAP stagging repo

[Gary Wu via RT]

Hold on… it looks like all autorelease directories older than last Friday got 
removed, which is a big issue for multiple teams.  Catherine will be escalating 
for a restore.

Thanks,
Gary

From: Gary Wu
Sent: Wednesday, October 18, 2017 8:05 AM
To: 'zhao.huab...@zte.com.cn' <zhao.huab...@zte.com.cn>; 
jwagant...@linuxfoundation.org; helpd...@onap.org
Cc: onap-discuss@lists.onap.org
Subject: RE: No binaries in ONAP stagging repo

The directory autorelease-18453 doesn’t seem to exist on nexus right now.  
Maybe the autorelease directories get removed after a certain time?

You’ll need to re-run the staging (-release-version-*) jobs to build to 
staging/autorelease again.  After that, if the result is good, please email LF 
to have them formally released into the Releases repo.

Thanks,
Gary

From: zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn> 
[mailto:zhao.huab...@zte.com.cn]
Sent: Tuesday, October 17, 2017 11:40 PM
To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>; 
jwagant...@linuxfoundation.org<mailto:jwagant...@linuxfoundation.org>; 
helpd...@onap.org<mailto:helpd...@onap.org>
Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: No binaries in ONAP stagging repo


Hi Jess, Gary,

I found that the binary of msb java sdk has not been pushed to ONAP stagging 
repository today.

Because of that, the wfengine jenkins job failed.

https://jenkins.onap.org/view/vfc/job/vfc-nfvo-wfengine-master-engine-activiti-extension-verify-java/



The msb-java-sdk-1.0.0 does exist at 
https://nexus.onap.org<https://nexus.onap.org,> in repository autorelease-18453 
(staging: 
closed)<https://nexus.onap.org/index.html#view-repositories;autorelease-18453~browsestorage~/org/onap/msb/java-sdk/msb-java-sdk/1.0.0/msb-java-sdk-1.0.0.jar>,
 but not in stagging repo.



Is there anything I am supposed to do to fix this?



Thanks a lot,

Huabing









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

[onap-discuss] [ONAP Helpdesk #47175] [linuxfoundation.org #47175] RE: No binaries in ONAP stagging repo

[Gary Wu via RT]

The directory autorelease-18453 doesn’t seem to exist on nexus right now.  
Maybe the autorelease directories get removed after a certain time?

You’ll need to re-run the staging (-release-version-*) jobs to build to 
staging/autorelease again.  After that, if the result is good, please email LF 
to have them formally released into the Releases repo.

Thanks,
Gary

From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn]
Sent: Tuesday, October 17, 2017 11:40 PM
To: Gary Wu <gary.i...@huawei.com>; jwagant...@linuxfoundation.org; 
helpd...@onap.org
Cc: onap-discuss@lists.onap.org
Subject: No binaries in ONAP stagging repo


Hi Jess, Gary,

I found that the binary of msb java sdk has not been pushed to ONAP stagging 
repository today.

Because of that, the wfengine jenkins job failed.

https://jenkins.onap.org/view/vfc/job/vfc-nfvo-wfengine-master-engine-activiti-extension-verify-java/



The msb-java-sdk-1.0.0 does exist at 
https://nexus.onap.org<https://nexus.onap.org,> in repository autorelease-18453 
(staging: 
closed)<https://nexus.onap.org/index.html#view-repositories;autorelease-18453~browsestorage~/org/onap/msb/java-sdk/msb-java-sdk/1.0.0/msb-java-sdk-1.0.0.jar>,
 but not in stagging repo.



Is there anything I am supposed to do to fix this?



Thanks a lot,

Huabing









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

Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

[Gary Wu via RT]

This issue is still occurring and still needs LF resolution.
 
Thanks,
Gary

-Original Message-
From: Kenny Paul via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Sunday, October 22, 2017 7:43 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

I’m reviewing all of the tickets in the LF IT queue that are open.
Is this still an issue that needs support from IT or can this ticket be closed?

Thanks!
-kenny

On Wed Sep 06 17:18:23 2017, gary.i...@huawei.com wrote:
> I just noticed the issue today, but I suspect it's been happening for 
> a long time.
> 
> Thanks,
> Gary
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap- 
> helpd...@rt.linuxfoundation.org]
> Sent: Wednesday, September 06, 2017 2:10 PM
> To: Gary Wu <gary.i...@huawei.com>
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence 
> issue
> 
> Hey Gary, quick question.. did you saw this happening the time we 
> released oparent 0.1.0?
> 
> Thanks!
> Jess




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

Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

[Gary Wu via RT]

Hi Pam,

The move away from building against staging dependencies has been planned and 
announced for Amsterdam since early September, and teams should have started 
making the transition since RC0.  We understand that the transition would take 
time, which is why we waited as long as possible to turn on the enforcement.  
Given that the release is only one week away, we needed to turn the enforcement 
on now in order for teams to have adequate time to formally release their 
artifacts.

On the implementation specifics:  You should not need to change or remove your 
build jobs; instead, for each dependency that you had coming from staging, 
those upstream teams need to formally release their artifacts.  After that's 
done, your builds should complete successfully by retrieving those same 
artifact versions from the Releases repo.

Also, this only affects Java/Maven artifacts.  You should still be able to 
produce and use STAGING docker images, but the Java/Maven artifacts contained 
within those docker images should be the released versions.

Thanks,
Gary

-Original Message-
From: pdrag...@research.att.com via RT 
[mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Friday, November 10, 2017 8:48 AM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo 
precedence issue

Gary,

This breaks current projects whose release jobs on the master branch are 
producing Staging artifacts. I will now have to remove those jobs.

I understand for a formal release process you don’t want staging in the mix. 
But unfortunately perhaps this could have been done post Amsterdam release.

Pam

On 11/9/17, 3:12 PM, "onap-discuss-boun...@lists.onap.org on behalf of Gary Wu 
via RT" <onap-discuss-boun...@lists.onap.org on behalf of 
onap-helpd...@rt.linuxfoundation.org> wrote:

Thanks Jess.

All teams:  Please make sure that you are no longer building against 
staging artifacts.  If you still have dependencies on staging artifacts, please 
contact the upstream teams to make sure that they formally release those 
artifacts.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT 
[mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, November 09, 2017 11:51 AM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

Dear Gary, 

We have now removed the staging as an active profile from 
global-settings.xml now and the dependencies should now be downloaded from 
releases. 

Thanks!
Jess

On Mon Nov 06 13:43:31 2017, gary.i...@huawei.com wrote:
> Hi Jessica,
> 
> Thanks for the investigation.  At this point in the release cycle, I 
> think the better solution now is to just completely remove staging 
> from settings.xml.  All teams should be formally releasing their 
> artifacts by now, and we should no longer be having any build 
> dependencies on staging artifacts.  This would completely eliminate 
> the precedence issue.
> 
> Thanks,
> Gary
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap- 
> helpd...@rt.linuxfoundation.org]
> Sent: Friday, November 03, 2017 6:21 PM
> To: Gary Wu <gary.i...@huawei.com>
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence 
> issue
> 
> Dear Gary,
> 
> I was briefly talking with Andy about this ticket.
> 
> I made a test in the sandbox in where I am changing the values that 
> global-settings have as the active profiles. Basically, this file has 
> the releases, staging, snapshot active profiles described in that 
> order. This file controls the precedence of the repos where is going 
> to do the downloads.
> 
> Here is a run on the job with that described global settings:
> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__jenkins.onap.org_sandbox_job_integration-2Dmaster-2Dversion-2D=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=Ddx1EMIdNutEneZ6mWVntIrLKGz6DW56oB0qCeUGoC8=e_2kEzSAMTHe5p59EWQMOzpqK0vycI1I2UhrTxCznc8=
 
> manifest-release-version-java-daily/2/console
> This job downloaded the release version of oparent: 00:53:19 [INFO]
> Downloaded:
> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_content_repositories_releases_org_onap_oparent_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=Ddx1EMIdNutEneZ6mWVntIrLKGz6DW56oB0qCeUGoC8=KIlzTtoSbQMpwWEBZs6FPh-6jOZ1SMl6m1Iza2pwLmc=
 
> oparent/0.1.1/oparent-
> 0.1.1.pom (21 KB at 43

Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

[Gary Wu via RT]

Hi Jessica,

Thanks for the investigation.  At this point in the release cycle, I think the 
better solution now is to just completely remove staging from settings.xml.  
All teams should be formally releasing their artifacts by now, and we should no 
longer be having any build dependencies on staging artifacts.  This would 
completely eliminate the precedence issue.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Friday, November 03, 2017 6:21 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

Dear Gary, 

I was briefly talking with Andy about this ticket. 

I made a test in the sandbox in where I am changing the values that 
global-settings have as the active profiles. Basically, this file has the 
releases, staging, snapshot active profiles described in that order. This file 
controls the precedence of the repos where is going to do the downloads.

Here is a run on the job with that described global settings: 
https://jenkins.onap.org/sandbox/job/integration-master-version-manifest-release-version-java-daily/2/console
This job downloaded the release version of oparent: 00:53:19 [INFO] Downloaded: 
https://nexus.onap.org/content/repositories/releases/org/onap/oparent/oparent/0.1.1/oparent-0.1.1.pom
 (21 KB at 430.4 KB/sec)

I did a small test in which I removed the releases profile and the download 
happened from the public repo: 
https://jenkins.onap.org/sandbox/job/integration-master-version-manifest-release-version-java-daily/6/console

Another thing that Andy mentioned, is that whenever this download fails, the 
log will report the last place where it looked for the binaries. For example, 
if we ask the job to look into releases and then staging, if it fails it will 
report the failure while looking into staging making the log look like it 
didn't looked in releases even though it actually did. It just happens that 
maven will report the failure making reference to the last profile it looked 
into. 

Let me know if you would like to make more tests with my setup, I can place the 
jobs in the Sandbox for us to experiment more. 

Thanks!
Jess

On Tue Oct 24 00:29:23 2017, gary.i...@huawei.com wrote:
> This issue is still occurring and still needs LF resolution.
> 
> Thanks,
> Gary
> 
> -Original Message-
>  From: Kenny Paul via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
> Sent: Sunday, October 22, 2017 7:43 PM
> To: Gary Wu <gary.i...@huawei.com>
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence 
> issue
> 
> I’m reviewing all of the tickets in the LF IT queue that are open.
> Is this still an issue that needs support from IT or can this ticket 
> be closed?
> 
> Thanks!
> -kenny
> 
> On Wed Sep 06 17:18:23 2017, gary.i...@huawei.com wrote:
> > I just noticed the issue today, but I suspect it's been happening 
> > for a long time.
> >
> > Thanks,
> > Gary
> >
> > -Original Message-
> >   From: Jessica Wagantall via RT [mailto:onap- 
> > helpd...@rt.linuxfoundation.org]
> > Sent: Wednesday, September 06, 2017 2:10 PM
> > To: Gary Wu <gary.i...@huawei.com>
> > Cc: onap-discuss@lists.onap.org
> >  Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence 
> > issue
> >
> > Hey Gary, quick question.. did you saw this happening the time we 
> > released oparent 0.1.0?
> >
> > Thanks!
> > Jess
> 
> 
> 




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

Re: [onap-discuss] [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

[Gary Wu via RT]

Thanks Jess.

All teams:  Please make sure that you are no longer building against staging 
artifacts.  If you still have dependencies on staging artifacts, please contact 
the upstream teams to make sure that they formally release those artifacts.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, November 09, 2017 11:51 AM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence issue

Dear Gary, 

We have now removed the staging as an active profile from global-settings.xml 
now and the dependencies should now be downloaded from releases. 

Thanks!
Jess

On Mon Nov 06 13:43:31 2017, gary.i...@huawei.com wrote:
> Hi Jessica,
> 
> Thanks for the investigation.  At this point in the release cycle, I 
> think the better solution now is to just completely remove staging 
> from settings.xml.  All teams should be formally releasing their 
> artifacts by now, and we should no longer be having any build 
> dependencies on staging artifacts.  This would completely eliminate 
> the precedence issue.
> 
> Thanks,
> Gary
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap- 
> helpd...@rt.linuxfoundation.org]
> Sent: Friday, November 03, 2017 6:21 PM
> To: Gary Wu <gary.i...@huawei.com>
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence 
> issue
> 
> Dear Gary,
> 
> I was briefly talking with Andy about this ticket.
> 
> I made a test in the sandbox in where I am changing the values that 
> global-settings have as the active profiles. Basically, this file has 
> the releases, staging, snapshot active profiles described in that 
> order. This file controls the precedence of the repos where is going 
> to do the downloads.
> 
> Here is a run on the job with that described global settings:
> https://jenkins.onap.org/sandbox/job/integration-master-version-
> manifest-release-version-java-daily/2/console
> This job downloaded the release version of oparent: 00:53:19 [INFO]
> Downloaded:
> https://nexus.onap.org/content/repositories/releases/org/onap/oparent/
> oparent/0.1.1/oparent-
> 0.1.1.pom (21 KB at 430.4 KB/sec)
> 
> I did a small test in which I removed the releases profile and the 
> download happened from the public repo:
> https://jenkins.onap.org/sandbox/job/integration-master-version-
> manifest-release-version-java-daily/6/console
> 
> Another thing that Andy mentioned, is that whenever this download 
> fails, the log will report the last place where it looked for the 
> binaries. For example, if we ask the job to look into releases and 
> then staging, if it fails it will report the failure while looking 
> into staging making the log look like it didn't looked in releases 
> even though it actually did. It just happens that maven will report 
> the failure making reference to the last profile it looked into.
> 
> Let me know if you would like to make more tests with my setup, I can 
> place the jobs in the Sandbox for us to experiment more.
> 
> Thanks!
> Jess
> 
> On Tue Oct 24 00:29:23 2017, gary.i...@huawei.com wrote:
> > This issue is still occurring and still needs LF resolution.
> >
> > Thanks,
> > Gary
> >
> > -Original Message-
> >  From: Kenny Paul via RT [mailto:onap- 
> > helpd...@rt.linuxfoundation.org]
> > Sent: Sunday, October 22, 2017 7:43 PM
> > To: Gary Wu <gary.i...@huawei.com>
> > Cc: onap-discuss@lists.onap.org
> >  Subject: [ONAP Helpdesk #45447] [integration] Maven repo precedence 
> > issue
> >
> > I’m reviewing all of the tickets in the LF IT queue that are open.
> >  Is this still an issue that needs support from IT or can this 
> > ticket be closed?
> >
> > Thanks!
> > -kenny
> >
> > On Wed Sep 06 17:18:23 2017, gary.i...@huawei.com wrote:
> > > I just noticed the issue today, but I suspect it's been happening 
> > > for a long time.
> > >
> > > Thanks,
> > > Gary
> > >
> > > -Original Message-
> > >From: Jessica Wagantall via RT [mailto:onap- 
> > > helpd...@rt.linuxfoundation.org]
> > > Sent: Wednesday, September 06, 2017 2:10 PM
> > > To: Gary Wu <gary.i...@huawei.com>
> > > Cc: onap-discuss@lists.onap.org
> > >   Subject: [ONAP Helpdesk #45447] [integration] Maven repo 
> > > precedence issue
> > >
> > > Hey Gary, quick question.. did you saw this happening the time we 
> > > released oparent 0.1.0?
> > >
> > > Thanks!
> > > Jess
> >
> >
> >
> 
> 
> 




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

Re: [onap-discuss] [ONAP Helpdesk #47614] Issue with SO daily build due to appc client kit jar

[Gary Wu via RT]

Hi Seshu,

The issue on so-master-docker-version-java-daily is due to SNAPSHOT 
dependencies which are no longer allowed for staging/release builds.  Please 
update your pom files to replace your SNAPSHOT dependencies with Release 
dependencies per the 
https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process.

A Jira issue has been logged to track this:  https://jira.onap.org/browse/SO-286

Thanks,
Gary

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
seshu.kuma...@huawei.com via RT
Sent: Monday, October 30, 2017 7:12 AM
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [ONAP Helpdesk #47614] Issue with SO daily build due to 
appc client kit jar

On Mon Oct 30 05:59:44 2017, seshu.kuma...@huawei.com wrote:
> Dear LF
> 
> We are facing the issue of the SO verify build failure due to the appc 
> client -kit jar.
> This issue was reported 2 weeks earlier and was resolved, but has come 
> back again.
> Request to kinldy look into this at the earliest as this is blcoking 
> the progress.
> 
https://jenkins.onap.org/view/so/job/so-master-verify-profile-java/lastBuild/console

There is other problem that looks to be with the staging issue and is blocking 
our progress.
https://jenkins.onap.org/view/so/job/so-master-docker-version-java-daily/lastBuild/console

12:35:46 [WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireReleaseDeps 
failed with message:
12:35:46 Found Banned Dependency: 
org.openecomp.so.libs.openstack-java-sdk.client-connectors:http-connector:jar:1.1.0-SNAPSHOT
12:35:46 Found Banned Dependency: 
org.openecomp.so.libs.openstack-java-sdk:quantum-client:jar:1.1.0-SNAPSHOT
12:35:46 Found Banned Dependency: 
org.openecomp.so.libs.openstack-java-sdk:heat-model:jar:1.1.0-SNAPSHOT
12:35:46 Found Banned Dependency: 
org.openecomp.so.libs.openstack-java-sdk:heat-client:jar:1.1.0-SNAPSHOT
12:35:46 Found Banned Dependency: 
org.openecomp.so.libs.openstack-java-sdk:keystone-client:jar:1.1.0-SNAPSHOT
12:35:46 Found Banned Dependency: 
org.openecomp.so.libs.openstack-java-sdk:openstack-client:jar:1.1.0-SNAPSHOT
12:35:46 Found Banned Dependency: 
org.openecomp.so.libs.openstack-java-sdk:quantum-model:jar:1.1.0-SNAPSHOT
12:35:46 Found Banned Dependency: 
org.openecomp.so.libs.openstack-java-sdk:keystone-model:jar:1.1.0-SNAPSHOT
12:35:46 Use 'mvn dependency:tree' to locate the source of the banned 
dependencies.




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



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

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

Re: [onap-discuss] [Onap-release] [ONAP Helpdesk #55152] [linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Gary Wu via RT]

I've just added a script that will update the OOM helm charts using the 
versions from the docker-manifest.csv.  Going forward, teams should only need 
to update the manifest as the "single source of truth", and we'll sync the OOM 
and HEAT docker image versions from there.

Thanks,
Gary

-Original Message-
From: onap-release-boun...@lists.onap.org 
[mailto:onap-release-boun...@lists.onap.org] On Behalf Of dt5...@att.com via RT
Sent: Monday, May 07, 2018 11:10 AM
To: frank.obr...@amdocs.com
Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
Subject: Re: [Onap-release] [onap-discuss] [ONAP Helpdesk #55152] 
[linuxfoundation.org #55152] RE: [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

Michael,

I believe the Heat environment is using the version manifests.  So I think we 
only have 2 places to update now - which is still one too many, but such is 
life.   The good news is there's no changes between 0.2.1-SNAPSHOT and 
0.2.2-SNAPSHOT of dgbuilder, so you're not missing any bug fixes but I'll 
certainly get that updated in OOM.


Dan

-- 
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO
 
Please go to  D2 ECOMP Release Planning Wiki 
 for D2 
ECOMP Project In-take, 2016 Release Planning, Change Management, and find key 
Release Planning Contact Information.
 
On 5/7/18, 1:58 PM, "onap-discuss-boun...@lists.onap.org on behalf of Michael 
O'Brien via RT"  wrote:

Dan,
   Hi, I am using ONAP out of the box – no changes.
   The image changes anyone makes to HEAT, OOM need to also be made to the 
other side in order for both ONAP deployment options to be in sync.
   The image tag for OOM for SDNC and APPC were not updated in sync with 
the HEAT and manifest change.
   A note for all PTS’s: any change to any of the 3 configuration places 
(until we have automated yaml generation) – must be done in sync in all three 
places
  The manifest
  HEAT
  OOM

   CCSDK and any other common charts are a bit of a special case – as 
either PTL needs to make the change for the other project – when using cross 
project charts like common/dgbuilder.


https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_46423_=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=g5iDyAsou22Nfxj8QZL5EBVYg1eUmhCNIR0X6t6IZFY=7y2q8-lYULDtlC81W7JOw4S1piwQSK_0uJQlMuvAKEs=
 
The above change is being tested on a live deployment – ETA 90 min before 
it can be merged.


The secondary on this is – this issue only came up because the LF deleted 
the older image – without the LF’s periodic purge – SDNC and APPC would have 
continued working with the old images for a while

Thank you
/michael

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Monday, May 7, 2018 9:32 AM
To: Michael O'Brien ; 
'onap-rele...@lists.onap.org' ; 
'onap-discuss@lists.onap.org' 
Cc: 'helpd...@onap.org' 
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

All,

You shouldn’t really be using snapshot versions of the CCSDK docker images. 
 You should be using version 0.2-STAGING-latest for CCSDK (and 
1.3-STAGING-latest for SDN-C)

I noticed last week that the docker version manifest incorrectly specified 
snapshot versions for the CCSDK docker images, so I fixed that.   Sorry if that 
caused any confusion.

Dan

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

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From: 
>
 on behalf of "OBRIEN, FRANK MICHAEL" 
>
Date: Monday, May 7, 2018 at 7:52 AM
To: "'onap-rele...@lists.onap.org'" 
>, onap-discuss 
>
Cc: "'helpd...@onap.org'" >
Subject: Re: [onap-discuss] [CCSDK] ccsdk-dgbuilder-image had no 
0.2.1-SNAPSHOT until 20 April

Team,
   The image was deleted again – looks like as James M. has mentioned – the 
rule for nexus3 deletion should be “delete 2 week old images – unless there has 
been no build in the past 2 weeks” – to keep at least 1 snapshot around

Re: [onap-discuss] [ONAP Helpdesk #55813] [integration][aaf] AAF docker images missing

[Gary Wu via RT]

I see that those images have re-appeared now.  Not sure what happened.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, May 09, 2018 2:16 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #55813] [integration][aaf] AAF docker images missing

I wonder if you might have came across a mini downtime in Nexus. 

I was able to re-run this job now:
https://jenkins.onap.org/view/integration/job/integration-master-version-manifest-release-version-java-daily/212/

Thanks!
Jess

On Wed May 09 17:14:43 2018, jwagantall wrote:
> Hi Gary,
> 
> checking on this now.. I am able to pull the first image for example:
> docker pull nexus3.onap.org:10003/onap/aaf/aaf_cm:2.1.0-SNAPSHOT
> 
> Checking more.. 
> 
> Thanks!
> Jess
> 
> 
> On Wed May 09 13:44:52 2018, gary.i...@huawei.com wrote:
> > Hi AAF team and helpdesk,
> > 
> > The following AAF docker images have disappeared from nexus3:
> > 
> > 11:53:57 [INFO] --- exec-maven-plugin:1.6.0:exec 
> > (check-docker-images-
> > exist) @ version-manifest ---
> > 11:53:57 [ERROR] onap/aaf/aaf_cm:2.1.0-SNAPSHOT not found
> > 11:53:57
> > 11:53:58 [ERROR] onap/aaf/aaf_fs:2.1.0-SNAPSHOT not found
> > 11:53:58
> > 11:53:58 [ERROR] onap/aaf/aaf_gui:2.1.0-SNAPSHOT not found
> > 11:53:58
> > 11:53:58 [ERROR] onap/aaf/aaf_hello:2.1.0-SNAPSHOT not found
> > 11:53:58
> > 11:53:59 [ERROR] onap/aaf/aaf_locate:2.1.0-SNAPSHOT not found
> > 11:53:59
> > 11:53:59 [ERROR] onap/aaf/aaf_oauth:2.1.0-SNAPSHOT not found
> > 11:53:59
> > 11:53:59 [ERROR] onap/aaf/aaf_service:2.1.0-SNAPSHOT not found
> > 11:53:59
> > 11:54:26 [ERROR] Command execution failed.
> > 
> > https://jenkins.onap.org/view/integration/job/integration-master-
> > version-manifest-release-version-java-daily/211/
> > 
> > Were these purposely removed or renamed?  Or did something happen to 
> > nexus3?
> > 
> > Thanks,
> > Gary
> 
> 




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

Re: [onap-discuss] [ONAP Helpdesk #56451] [portal] Missing Portal docker images

[Gary Wu via RT]

I think some teams managed to produce "release-like" tags and put them into the 
docker.snapshots repo, but they were not really released via LF.

You can look up the past errors by browsing the build history for 
http://12.234.32.117/jenkins/job/nexus3-docker-image-check/. 

Some of the past ones that have disappeared:

[ERROR] onap/multicloud/vio:1.1.2-STAGING not found
[ERROR] onap/multicloud/vio-vesagent:1.0.0 not found
[ERROR] onap/multicloud/framework:1.1.2-STAGING not found
[ERROR] openecomp/mso:1.2.1 not found
[ERROR] onap/multicloud/openstack-ocata:1.1.2-SNAPSHOT not found

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Thursday, May 24, 2018 9:28 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #56451] [portal] Missing Portal docker images

I am confused by the tag, these are supposed to be found in snapshots repo?
Why do they have a release tag?

Also, quick question Gary, on these disappearing images issue, does it seems 
like the only images that disappear have the release tag format? Do you recall 
any disappeared images under the SNAPSHOT or STAGING tag? I don't 

Thansk!
Jess


On Fri May 25 00:23:48 2018, jwagantall wrote:
> Investigating this issue.. 
> 
> Thanks!
> Jess
> 
> On Fri May 25 00:15:54 2018, gary.i...@huawei.com wrote:
> > Hi helpdesk and/or Portal team,
> > 
> > The following images have disappeared from nexus3:
> > 
> > 19:04:55 [ERROR] onap/portal-app:v2.2.0 not found
> > 19:04:56 [ERROR] onap/portal-db:v2.2.0 not found
> > 19:04:57 [ERROR] onap/portal-sdk:v2.2.0 not found
> > 19:04:57 [ERROR] onap/portal-wms:v2.2.0 not found
> > 
> > http://12.234.32.117/jenkins/job/nexus3-docker-image-check/321/conso
> > le
> > 
> > Please help.
> > 
> > Thanks,
> > Gary
> > 
> > 
> 
> 




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

[onap-discuss] [ONAP Helpdesk #56152] [linuxfoundation.org #56152] RE: [so] mso:1.2.1 image missing

[Gary Wu via RT]

Hi Seshu,

Thanks for taking care of this.  I hope LF can figure out why these docker 
images keep disappearing.

Thanks,
Gary

From: Seshu m
Sent: Friday, May 18, 2018 12:23 AM
To: Gary Wu <gary.i...@huawei.com>; helpd...@onap.org; 
onap-discuss@lists.onap.org
Subject: RE: [so] mso:1.2.1 image missing

Hi Gary

This is strange why things go missing,
I triggered a new build and I can see the Docker back
https://nexus3.onap.org/#browse/search=keyword%3Dmso:7f6379d32f8dd78fd8e42923c8ff348e:88bfafa960bab52124a30fecfc044940
[cid:image001.png@01D3EE75.FDBB4810]

http://12.234.32.117/jenkins/job/nexus3-docker-image-check/157/
is success..

Thanks and Regards,
M Seshu Kumar
Senior System Architect
Single OSS India Branch Department. S/W BU.
Huawei Technologies India Pvt. Ltd.
Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield
Bengaluru-560066, Karnataka.
Tel: + 91-80-49160700 , Mob: 9845355488
[Company_logo]
___
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 Gary Wu
Sent: Friday, May 18, 2018 1:28 PM
To: helpd...@onap.org<mailto:helpd...@onap.org>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: [onap-discuss] [so] mso:1.2.1 image missing

Hi helpdesk and/or the SO team,

Currently the mso image is missing:

22:05:48 [ERROR] openecomp/mso:1.2.1 not found
http://12.234.32.117/jenkins/job/nexus3-docker-image-check/155/console

Can we figure out what happened?  This will likely cause problems for upcoming 
deployments.

Thanks,
Gary



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

Re: [onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

[Gary Wu via RT]

This job runs hourly, and checks the image tags in the docker manifest: 
https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Friday, May 18, 2018 3:39 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

Gary, 

How often is this job triggered?
Does it checks all possible "missing" images?

Thanks!
Jess

On Fri May 18 18:31:50 2018, jwagantall wrote:
> I have been investigating all the examples we have.
> 
> This has to be something coming from Jenkins.
> 
> So far, I have not seen this issue in the docker.releases repo which 
> is the only repo where we do not use automation to push, but rather on 
> demand pushes.
> 
> Another separate issue, why are we using this tag in the snapshots 
> repo?
> 
> Let me continue working on this cases.
> 
> Thanks!
> Jess
> 
> On Fri May 18 10:00:42 2018, gary.i...@huawei.com wrote:
> > Hi Seshu,
> >
> > Thanks for taking care of this.  I hope LF can figure out why these 
> > docker images keep disappearing.
> >
> > Thanks,
> > Gary
> >
> > From: Seshu m
> > Sent: Friday, May 18, 2018 12:23 AM
> > To: Gary Wu <gary.i...@huawei.com>; helpd...@onap.org; onap- 
> > disc...@lists.onap.org
> > Subject: RE: [so] mso:1.2.1 image missing
> >
> > Hi Gary
> >
> > This is strange why things go missing, I triggered a new build and I 
> > can see the Docker back
> > https://nexus3.onap.org/#browse/search=keyword%3Dmso:7f6379d32f8dd78
> > fd8e42923c8ff348e:88bfafa960bab52124a30fecfc044940
> > [cid:image001.png@01D3EE75.FDBB4810]
> >
> > http://12.234.32.117/jenkins/job/nexus3-docker-image-check/157/
> > is success..
> >
> > Thanks and Regards,
> > M Seshu Kumar
> > Senior System Architect
> > Single OSS India Branch Department. S/W BU.
> > Huawei Technologies India Pvt. Ltd.
> > Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield 
> > Bengaluru-560066, Karnataka.
> > Tel: + 91-80-49160700 , Mob: 9845355488 [Company_logo] 
> > 
> > ___ 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 Gary Wu
> > Sent: Friday, May 18, 2018 1:28 PM
> > To: helpd...@onap.org<mailto:helpd...@onap.org>; onap- 
> > disc...@lists.onap.org<mailto:onap-discuss@lists.onap.org>
> > Subject: [onap-discuss] [so] mso:1.2.1 image missing
> >
> > Hi helpdesk and/or the SO team,
> >
> > Currently the mso image is missing:
> >
> > 22:05:48 [ERROR] openecomp/mso:1.2.1 not found
> > http://12.234.32.117/jenkins/job/nexus3-docker-image-
> > check/155/console
> >
> > Can we figure out what happened?  This will likely cause problems 
> > for upcoming deployments.
> >
> > Thanks,
> > Gary




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

Re: [onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

[Gary Wu via RT]

Not that I'm aware of, because virtually none of the images in the manifest are 
release versions yet.

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Friday, May 18, 2018 4:07 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

Thanks!

Can you confirm something with me please?

No occurrences have happened in docker.releases right?

This will help me narrow down the cause which could be Jenkins jobs if my 
assumption is correct. 

If this also happens in docker.releases then I would suggest an upgrade to the 
newest Nexus3 version. 

Thanks!
Jess

On Fri May 18 18:50:22 2018, gary.i...@huawei.com wrote:
> This job runs hourly, and checks the image tags in the docker
> manifest: https://git.onap.org/integration/tree/version-
> manifest/src/main/resources/docker-manifest.csv
> 
> Thanks,
> Gary
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap- 
> helpd...@rt.linuxfoundation.org]
> Sent: Friday, May 18, 2018 3:39 PM
> To: Gary Wu <gary.i...@huawei.com>
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing
> 
> Gary,
> 
> How often is this job triggered?
> Does it checks all possible "missing" images?
> 
> Thanks!
> Jess
> 
> On Fri May 18 18:31:50 2018, jwagantall wrote:
> > I have been investigating all the examples we have.
> >
> > This has to be something coming from Jenkins.
> >
> > So far, I have not seen this issue in the docker.releases repo which 
> > is the only repo where we do not use automation to push, but rather 
> > on demand pushes.
> >
> > Another separate issue, why are we using this tag in the snapshots 
> > repo?
> >
> > Let me continue working on this cases.
> >
> > Thanks!
> > Jess
> >
> > On Fri May 18 10:00:42 2018, gary.i...@huawei.com wrote:
> > > Hi Seshu,
> > >
> > > Thanks for taking care of this.  I hope LF can figure out why 
> > > these docker images keep disappearing.
> > >
> > > Thanks,
> > > Gary
> > >
> > > From: Seshu m
> > > Sent: Friday, May 18, 2018 12:23 AM
> > >  To: Gary Wu <gary.i...@huawei.com>; helpd...@onap.org; onap- 
> > > disc...@lists.onap.org
> > > Subject: RE: [so] mso:1.2.1 image missing
> > >
> > > Hi Gary
> > >
> > > This is strange why things go missing, I triggered a new build and 
> > > I can see the Docker back
> > > https://nexus3.onap.org/#browse/search=keyword%3Dmso:7f6379d32f8dd
> > > 78
> > > fd8e42923c8ff348e:88bfafa960bab52124a30fecfc044940
> > > [cid:image001.png@01D3EE75.FDBB4810]
> > >
> > > http://12.234.32.117/jenkins/job/nexus3-docker-image-check/157/
> > > is success..
> > >
> > > Thanks and Regards,
> > > M Seshu Kumar
> > > Senior System Architect
> > > Single OSS India Branch Department. S/W BU.
> > > Huawei Technologies India Pvt. Ltd.
> > >  Survey No. 37, Next to EPIP Area, Kundalahalli, Whitefield 
> > > Bengaluru-560066, Karnataka.
> > >  Tel: + 91-80-49160700 , Mob: 9845355488 [Company_logo] 
> > > __
> > > __ ___ 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 Gary Wu
> > > Sent: Friday, May 18, 2018 1:28 PM
> > >  To: helpd...@onap.org<mailto:helpd...@onap.org>; onap- 
> > > disc...@lists.onap.org<mailto:onap-discuss@lists.onap.org>
> > > Subject: [onap-discuss] [so] mso:1.2.1 image missing
> > >
> > > Hi helpdesk and/or the SO team,
> > >
> > > Currently the mso image is missing:
> > >
> > > 22:05:48 [ERROR] openecomp/mso:1.2.1 not found
> > > http://12.234.32.117/jenkins/job/nexus3-docker-image-
> > > check/155/console
> > >
> > > Can we figure out what happened?  This will likely cause problems 
> > > for upcoming deployments.
> > >
> > > Thanks,
> > > Gary
> 
> 
> 




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

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

[Gary Wu via RT]

Thanks Sunil.

Can someone from DCAE help with the other missing image?

16:04:14 [ERROR] onap/org.onap.dcaegen2.deployments.bootstrap:1.1.2 not found

Thanks,
Gary


-Original Message-
From: UNNAVA, SUNIL [mailto:su6...@att.com] 
Sent: Wednesday, May 30, 2018 10:45 AM
To: onap-helpd...@rt.linuxfoundation.org; Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [ONAP Helpdesk #56611] [linuxfoundation.org #56611] 
RE: Missing docker images

Docker image onap/dmaap/dmaap-mr:1.1.4 is available now in Nexus.

Thanks,
Sunil

-Original Message-
From: onap-discuss-boun...@lists.onap.org  
On Behalf Of aroraa...@vmware.com via RT
Sent: Wednesday, May 30, 2018 3:45 AM
To: gary.i...@huawei.com
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [ONAP Helpdesk #56611] [linuxfoundation.org #56611] RE: 
Missing docker images

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


Best Regards,
Arun Arora


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

Hi all,

The following images are currently missing from nexus3:

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

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

Thanks,
Gary



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=t27CRRmn7U12dnOvcSPfcQ=qrBhC0Fe8YsNUG497qcS4GayL8A38EcStQS8Hm9suMs=PCEVAImKxPrhCzH4XD4QUuLhY5PFrkyFNT1sWqkEtR4=

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

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

[Gary Wu via RT]

Hi Lusheng,

I currently see a 1.1.3 in docker.snapshot repo.  Ok to bump the docker 
manifest to 1.1.3?

Thanks,
Gary

-Original Message-
From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com] 
Sent: Wednesday, May 30, 2018 11:21 AM
To: Gary Wu ; UNNAVA, SUNIL ; 
onap-helpd...@rt.linuxfoundation.org
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [ONAP Helpdesk #56611] [linuxfoundation.org #56611] 
RE: Missing docker images

Gary,

onap/org.onap.dcaegen2.deployments.bootstrap:1.1.2 a snapshot tag.  
We submitted helpdesk ticket 56632 for releasing 
onap/org.onap.dcaegen2.deployments.bootstrap:1.1.3.  Jess is working on that.

Lusheng


On 5/30/18, 1:53 PM, "Gary Wu"  wrote:

Thanks Sunil.

Can someone from DCAE help with the other missing image?

16:04:14 [ERROR] onap/org.onap.dcaegen2.deployments.bootstrap:1.1.2 not 
found

Thanks,
Gary


-Original Message-
From: UNNAVA, SUNIL [mailto:su6...@att.com] 
Sent: Wednesday, May 30, 2018 10:45 AM
To: onap-helpd...@rt.linuxfoundation.org; Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [ONAP Helpdesk #56611] [linuxfoundation.org 
#56611] RE: Missing docker images

Docker image onap/dmaap/dmaap-mr:1.1.4 is available now in Nexus.

Thanks,
Sunil

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
 On Behalf Of aroraa...@vmware.com via RT
Sent: Wednesday, May 30, 2018 3:45 AM
To: gary.i...@huawei.com
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [ONAP Helpdesk #56611] [linuxfoundation.org #56611] 
RE: Missing docker images

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


Best Regards,
Arun Arora


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

Hi all,

The following images are currently missing from nexus3:

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

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

Thanks,
Gary



___
onap-discuss mailing list
onap-discuss@lists.onap.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=t27CRRmn7U12dnOvcSPfcQ=qrBhC0Fe8YsNUG497qcS4GayL8A38EcStQS8Hm9suMs=PCEVAImKxPrhCzH4XD4QUuLhY5PFrkyFNT1sWqkEtR4=



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

Re: [onap-discuss] [ONAP Helpdesk #45257] [integration] Issue-ID check

[Gary Wu via RT]

I thought that this in fact had already been implemented (the 
capitalization-sensitive check for "Issue-ID").

Thanks,
Gary

-Original Message-
From: Kenny Paul via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Sunday, October 22, 2017 7:51 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #45257] [integration] Issue-ID check

Gary, looking for conformation that this is in fact something that you want to 
put on hold until after the release.

Thanks!
-kenny



On Thu Oct 12 15:53:22 2017, jwagantall wrote:
> Dear Team,
> 
> just a small update on this. After discussing with Gildas, we thought 
> that this enforcement will create a little bit of obstacles for 
> developers since we are so close to our release goals.
> 
> We are planning to merge this change after Nov 16 when we have more 
> flexibility.
> 
> Thanks!
> Jess
> 
> On Thu Sep 21 16:21:38 2017, agrimberg wrote:
> > On Sat Sep 02 11:19:32 2017, frank.obr...@amdocs.com wrote:
> > > Gary,
> > >Good point, the pre-commit script is cAP agnostic but the links 
> > > are not.
> > >I have also noticed that periodically some jiras will not show 
> > > their gerrit reviews - even though they were previously linked.
> > >The linking between confluence and jira is also currently 
> > > broken in the jira-to-confluence direction but not the reverse 
> > > since April.
> >
> > Greetings folks,
> >
> > If you see that JIRA is not showing you any changes that you know 
> > exist try doing the following when looking at the JIRA issue:
> >
> > --[cut]--
> > Select the down arrow next to the Gerrit Reviews Make sure that 
> > 'Show All Reviews' is selected If it is, switch it to 'Show Open 
> > Reviews' and then back
> > --[cut]--
> >
> > What happens is that sometimes the Gerrit plugin disconnects from 
> > the Gerrit server and toggling those settings generally forces it to 
> > reconnect and refresh any caches that it has.
> >
> > > Sent this to the group on the 18th
> > >Watch your commit message case for JIRA links - the "Issue-ID"
> > > is
> > > case sensitive
> > >Only a "Issue-ID:" prefix will link gerrit reviews to jira - 
> > > cases like "issue-id, Issue-Id" will fail to link until the LF 
> > > makes their pre-commit check case-insensitive
> > >
> > > https://wiki.onap.org/display/DW/Commit+Messages#CommitMessages-
> > > CommitStructure
> >
> > I now have a change in for review, which will require a Gerrit 
> > restart to take effect when it's rolled out, which will enforce the 
> > following regex for the JIRA check:
> >
> > ^Issue-ID: ([A-Z][A-Z0-9]{1-9}-\d+)
> >
> > This means that it will _enforce_ that JIRA issues start with 
> > 'Issue-
> > ID: ', yes a _single_ space will be required. NOTE: we tell folks 
> > that this needs to be in the footer, but technically it can be 
> > anywhere and pass as we have no ability to the check to only operate 
> > on the footer, but honestly, it looks tacky if it isn't properly in 
> > the footer ;)
> >
> > When this change rolls out, another comment linking change will also 
> > roll out which will enable Gerrit change IDs to be relinked back 
> > into Gerrit meaning that people will be able to leave notes in the 
> > comments such as:
> >
> > --[cut]--
> > This change requires I4937bfdbecc4aec2363497aba12b9c0389cf2c90 from 
> > repo foo to work correctly.
> > --[cut]--
> >
> > And the I4937bfdbecc4aec2363497aba12b9c0389cf2c90 would be properly 
> > linked to the other change. This makes those sorts of comments more 
> > bullet proof to change should we have to do rebuilds of the Gerrit 
> > system or migrate repositories to a different one in the future 
> > where the short change number would end up changing.
> >
> > -Andy-




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

Re: [onap-discuss] [ONAP Helpdesk #50852] RE: maven artifacts

[Gary Wu via RT]

Thanks Andy, I didn't realize that 1.1.0 was already released.

Victor, given that 1.1.0 is already released, you need to change your build 
dependencies to refer to the released 1.1.0 version instead of 1.1.0-SNAPSHOT, 
and also bump your current build version number to something newer like 
1.1.1-SNAPSHOT or 1.2.0-SNAPSHOT.

Thanks,
Gary

-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Tuesday, January 09, 2018 7:07 AM
To: Gary Wu <gary.i...@huawei.com>
Cc: bin.y...@windriver.com; onap-discuss@lists.onap.org; ruijing@intel.com; 
victor.mora...@intel.com
Subject: Re: [ONAP Helpdesk #50852] RE: [onap-discuss] maven artifacts

On 01/09/2018 06:34 AM, Gary Wu via RT wrote:
> 
> Tue Jan 09 09:34:10 2018: Request 50852 was acted upon.
>  Transaction: Ticket created by gary.i...@huawei.com
>Queue: ONAP Helpdesk
>  Subject: RE: [onap-discuss] maven artifacts
>Owner: Nobody
>   Requestors: gary.i...@huawei.com
>   Status: new
>  Ticket  https://rt.linuxfoundation.org/Ticket/Display.html?id=50852 >
> 
> 
> I’m not sure why the 1.1.0-SNAPSHOT versions disappeared again.  I wonder if 
> something is wrong with Nexus.
>
> Helpdesk, can you help?  1.1.0-SNAPSHOT used to exist here, but it has 
> since disappeared: 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicl
> oud/openstack/multicloud-openstack-newton/
> 
> Also, there are occasions where the merge job seems to have created 
> 1.1.0-SNAPSHOT but then it’s nowhere to be found:
> https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-mast
> er-newton-merge-java/57/console
> 
> Thanks,
> Gary

Nothing is wrong with Nexus. There is a 1.1.0 release of this artifact in the 
system [0] Nexus auto-purges SNAPSHOT copies of released artifacts as any 
further development _must_ end up on a new version since you can't release new 
copies of the same version. There is a grace period of 14 days that a SNAPSHOT 
version will continue to exist at the same time that there is a release 
version. But in this case we're way, way, way past that window since the 
release version of this happened in the middle of November (November 16, 2017 
to be specific).

If you end up generating a new SNAPSHOT artifact at a version in this state it 
will exist for a very, very short amount of time until the Nexus artifact 
reaper comes through which happens once a day.

-Andy-

[0]
https://nexus.onap.org/content/repositories/releases/org/onap/multicloud/openstack/multicloud-openstack-newton/1.1.0/

> 
> From: Morales, Victor [mailto:victor.mora...@intel.com]
> Sent: Monday, January 08, 2018 9:43 AM
> To: Gary Wu <gary.i...@huawei.com>; Yang, Bin (Wind River) 
> <bin.y...@windriver.com>; Guo, Ruijing <ruijing@intel.com>; 
> onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] maven artifacts
> 
> Hey Gary,
> 
> We’re still having issues to deploy the 1.1.0-SNAPSHOT version for 
> multicloud-openstack-newton artifact [1].  The –merge-java job looks 
> like was successfully executed [2] when the version was bumped [3] but 
> there is no artifact placed for that specific version, as consequence 
> other jobs are failing [4].  I’m not sure if the deployment process 
> needs to be done separately (per subproject) [5] given that the parent 
> pom.xml contains the reference of every subproject[6]
> 
> Regards/Saludos
> Victor Morales
> 
> [1] 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicl
> oud/openstack/multicloud-openstack-newton/
> [2] 
> https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/multicloud-op
> enstack-master-newton-merge-java/55/console.log.gz
> [3] https://gerrit.onap.org/r/#/c/24617/
> [4] 
> https://jenkins.onap.org/job/multicloud-openstack-master-ocata-verify-
> java/65/ [5] 
> https://git.onap.org/ci-management/tree/jjb/multicloud/multicloud-open
> stack.yaml [6] 
> https://git.onap.org/multicloud/openstack/tree/pom.xml#n37
> 
> From: 
> <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-bounces@lists
> .onap.org>> on behalf of Gary Wu 
> <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>
> Date: Thursday, December 21, 2017 at 9:58 AM
> To: "Yang, Bin (Wind River)" 
> <bin.y...@windriver.com<mailto:bin.y...@windriver.com>>, "Guo, 
> Ruijing" <ruijing@intel.com<mailto:ruijing@intel.com>>, 
> "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
> <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
> Subject: Re: [onap-discuss] maven artifacts
> 
> I’m not sure why it didn’t work before, but I just re-ran that job and now 
> the artifac

Re: [onap-discuss] [ONAP Helpdesk #53333] [integration] Jenkins stuck

[Gary Wu via RT]

Just curious, did you identify what the problem was?

Thanks,
Gary

-Original Message-
From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, March 07, 2018 7:38 PM
To: Gary Wu <gary.i...@huawei.com>
Cc: onap-discuss@lists.onap.org
Subject: [ONAP Helpdesk #5] [integration] Jenkins stuck

Fixed and the queue is now in good state. 


On Wed Mar 07 14:01:47 2018, jwagantall wrote:
> Dear Gary,
> 
> I am still looking into these issues. 
> Sorry for the delays. 
> 
> Thanks!
> Jess
> 
> 
> On Wed Mar 07 12:14:48 2018, gary.i...@huawei.com wrote:
> > Hi helpdesk,
> > 
> > Jenkins has a huge backlog and is not running any jobs.  Can you 
> > take a look?
> > 
> > Thanks,
> > Gary
> 
> 




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