[onap-discuss] [ONAP Helpdesk #57978] JIRA - serious performance/rendering issues this morning again

[Jessica Wagantall via RT]

Spoke to our INFRA team. 

We are looking closely into this and saving reports of CPU, I/O, network 
statistics for this few days to detect any inconsistencies. 

Thanks!
Jess

On Tue Jul 03 11:53:15 2018, jwagantall wrote:
> Dear Michael,
> 
> I have reported this to Ryan now.
> 2 weeks ago (or so) Pam reported issues too during a very specific
> window of time which
> turned out to be the backup tasks running, we disabled those.
> 
> Ryan is looking at what else could this be.
> 
> During the rest of the day, we notice JIRA 90% idle.
> 
> thanks!
> Jess
> 
> On Tue Jul 03 10:33:18 2018, frank.obr...@amdocs.com wrote:
> > LF Hi,
> >Jira is experiencing a lot of slowdown and rendering issues this
> > morning again - on 3 different machines and 2 different networks - to
> > be sure.
> >This has been happening periodically for a couple weeks - can we
> > get a RCA on this issue
> >Thank you
> >/michael
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > 




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

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

[onap-discuss] [ONAP Helpdesk #57742] jira.onap.org hangs and timeouts consistently during early morning EST

[Jessica Wagantall via RT]

Replied to another ticket created by Michael, 

I have spoken with the INFRA team and we are monitoring CPU,I/O and network
operations for this following days with the hope of spotting any 
inconsistencies 

I will let you know as soon as I get an update from them. 

Thanks!
Jess

On Wed Jun 27 20:29:19 2018, rx1...@att.com wrote:
> This has always been my experience- I cannot access ONAP wiki or Jira
> before 8:30 AM. I just assumed you were running some sort of
> maintenance at this time. Rands
> 
> Randa
> 
> Sent from my iPhone
> 
> > On Jun 27, 2018, at 5:51 PM, Jessica Wagantall via RT  > helpd...@rt.linuxfoundation.org> wrote:
> >
> > Dear Pam,
> >
> > I have brought this issue up with Ryan from our infra team.
> > Looking at the jira logs, there is nothing that seems suspicious, but
> > Ryan has
> > disabled a backup that is set to run 10:00UTC 6:00am.
> >
> > Can you please let me know in case you see this issue again, we need
> > to see if the backup
> >  maybe was causing issues.
> >
> > During the day, Jira is 90% idle
> >
> > thanks!
> > Jess
> >
> >> On Wed Jun 27 08:21:12 2018, pdrag...@research.att.com wrote:
> >> Hi LF,
> >>
> >> Every day between approximately 7:30am and 8:30am EST I try to
> >> access
> >> jira.onap.org, and every day I consistently get time outs and
> >> hanging.
> >> It doesn’t matter if I refresh my browser, re-login or what network
> >> I
> >> am on. This is consistent pretty much every day. At some point it
> >> seems to recover and behave better during the day.
> >>
> >> Can someone please look into the logs and see what the problem is? I
> >> realize it just got upgraded, but the problem has been happening for
> >> many months now.
> >>
> >> It is extremely inconvenient and frustrating as I am trying to
> >> assess
> >> the work that was done overnight and what to prepare for during the
> >> day.
> >>
> >> Thanks,
> >>
> >> Pam
> >
> >
> >
> >
> > 
> >




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

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

[onap-discuss] [ONAP Helpdesk #57978] JIRA - serious performance/rendering issues this morning again

[Jessica Wagantall via RT]

Dear Michael, 

I have reported this to Ryan now. 
2 weeks ago (or so) Pam reported issues too during a very specific window of 
time which
turned out to be the backup tasks running, we disabled those. 

Ryan is looking at what else could this be. 

During the rest of the day, we notice JIRA 90% idle. 

thanks!
Jess

On Tue Jul 03 10:33:18 2018, frank.obr...@amdocs.com wrote:
> LF Hi,
>Jira is experiencing a lot of slowdown and rendering issues this
> morning again - on 3 different machines and 2 different networks - to
> be sure.
>This has been happening periodically for a couple weeks - can we
> get a RCA on this issue
>Thank you
>/michael
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 




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

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

[onap-discuss] [ONAP Helpdesk #57818] Cannot access wiki or jira

[Jessica Wagantall via RT]

There was no maintenance scheduled. 

Looks like the services are stable. 

Thanks!
Jess

On Thu Jun 28 22:20:50 2018, rx1...@att.com wrote:
> Hello LF,
> 
> Are you doing maintenance ?
> Cannot access wiki or jira again!
> 
> Regards,
> 
> Randa
> 




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

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

[ONAP Helpdesk #57746] RE: [onap-discuss] nexus3.onap.org stopped proxy of docker.io images

[Jessica Wagantall via RT]

This is working again locally in 2 of my machines. 

Looks like a server restart helped. 

Can you please re-try. Please let me know in case you still have any issues. 

Thanks!
Jess

On Wed Jun 27 12:59:14 2018, borislav.gloz...@amdocs.com wrote:
> This was for few days, for several images.
> 
> Looks like proxy mode was / is not working.
> 
> Thanks,
> Borislav Glozman
> O:+972.9.776.1988
> M:+972.52.2835726
> ________
> From: Jessica Wagantall via RT 
> Sent: Wednesday, June 27, 2018 19:55
> To: Borislav Glozman
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #57746] RE: [onap-discuss] nexus3.onap.org
> stopped proxy of docker.io images
> 
> This seemed to have happened for other teams as well.
> 
> I have just ran the command and was able to download it:
> 
> docker pull nexus3.onap.org:10001/library/cassandra:3.11
> 3.11: Pulling from library/cassandra
> f2aa67a397c4: Already exists
> 7883c8e950c9: Pull complete
> 17fef4315177: Pull complete
> de8642533b1e: Pull complete
> fc91ae190319: Pull complete
> c8de95d40c25: Pull complete
> d66bea82a2da: Pull complete
> 6e85c3794992: Pull complete
> 7e67c1874abb: Pull complete
> 901a929c2fa8: Pull complete
> Digest:
> sha256:7155cb41dd1a508c5ea67b1750e98381d495873637aea6dcb9a5b13e3b2fb133
> Status: Downloaded newer image for
> nexus3.onap.org:10001/library/cassandra:3.11
> 
> 
> Can you please try again? I am wondering if this was a small glitch
> issue.
> 
> Thanks!
> Jess
> 
> On Wed Jun 27 10:10:46 2018, borislav.gloz...@amdocs.com wrote:
> > Resending with helpdesk.
> >
> > Thanks,
> > Borislav Glozman
> > O:+972.9.776.1988
> > M:+972.52.2835726
> > [amdocs-a]
> > Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-
> > network/nfv-powered-by-onap>
> >
> > From: onap-discuss@lists.onap.org [mailto:onap-
> > disc...@lists.onap.org]
> > On Behalf Of Borislav Glozman
> > Sent: Tuesday, June 26, 2018 6:11 PM
> > To: onap-discuss@lists.onap.org
> > Cc: Jessica Wagantall 
> > Subject: [onap-discuss] nexus3.onap.org stopped proxy of docker.io
> > images
> >
> > Hi,
> >
> > I noticed when deploying ONAP deployment on K8S that images that come
> > from docker.io are not downloaded via nexus3.onap.org
> > For example: nexus3.onap.org:10001/ library/cassandra:3.11
> > I am getting error from nexus3:
> > https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11
> > {"errors":[{"code":"UNAUTHORIZED","message":"authentication
> > required","detail":[{"Type":"repository","Class":"","Name":"library/cassandra","Action":"pull"}]}]}
> >
> > Path
> >
> > v2/library/cassandra/manifests/3.11<https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11>
> >
> > Content type
> >
> > application/vnd.docker.distribution.manifest.v2+json
> >
> > File size
> >
> > 2.4 KB
> >
> > Blob created
> >
> > Wed Apr 25 2018 09:35:44 GMT+0300 (Israel Daylight Time)
> >
> > Blob updated
> >
> > Mon Apr 30 2018 13:27:29 GMT+0300 (Israel Daylight Time)
> >
> > Last 30 days
> >
> > 0 downloads
> >
> > Last downloaded
> >
> > Tue Jun 26 2018 18:05:21 GMT+0300 (Israel Daylight Time)
> >
> > Locally cached
> >
> > true
> >
> > Blob reference
> >
> > default@BE552485-1ACD19AD-4F5AA0F6-50E80C8B-4ADDA1F1:e52b1b31-05f6-
> > 4d93-bff9-0219fb055389
> >
> > Containing repo
> >
> > docker.io
> >
> > Uploader
> >
> > docker
> >
> > Uploader's IP Address
> >
> > 66.46.199.130
> >
> >
> > Could you please fix this?
> >
> > Thanks,
> > Borislav Glozman
> > O:+972.9.776.1988
> > M:+972.52.2835726
> > [amdocs-a]
> > Amdocs a Platinum member of ONAP<https://www.amdocs.com/open-
> > network/nfv-powered-by-onap>
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > 
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > <https://www.amdocs.com/about/email-disclaimer>
> 
> 
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://www.amdocs.com/about/email-disclaimer>




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

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

[onap-discuss] [ONAP Helpdesk #57742] jira.onap.org hangs and timeouts consistently during early morning EST

[Jessica Wagantall via RT]

Dear Pam,

I have brought this issue up with Ryan from our infra team. 
Looking at the jira logs, there is nothing that seems suspicious, but Ryan has 
disabled a backup that is set to run 10:00UTC 6:00am. 

Can you please let me know in case you see this issue again, we need to see if 
the backup
maybe was causing issues. 

During the day, Jira is 90% idle

thanks!
Jess

On Wed Jun 27 08:21:12 2018, pdrag...@research.att.com wrote:
> Hi LF,
> 
> Every day between approximately 7:30am and 8:30am EST I try to access
> jira.onap.org, and every day I consistently get time outs and hanging.
> It doesn’t matter if I refresh my browser, re-login or what network I
> am on. This is consistent pretty much every day. At some point it
> seems to recover and behave better during the day.
> 
> Can someone please look into the logs and see what the problem is? I
> realize it just got upgraded, but the problem has been happening for
> many months now.
> 
> It is extremely inconvenient and frustrating as I am trying to assess
> the work that was done overnight and what to prepare for during the
> day.
> 
> Thanks,
> 
> Pam




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

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

[ONAP Helpdesk #57746] RE: [onap-discuss] nexus3.onap.org stopped proxy of docker.io images

[Jessica Wagantall via RT]

This seemed to have happened for other teams as well. 

I have just ran the command and was able to download it:

docker pull nexus3.onap.org:10001/library/cassandra:3.11
3.11: Pulling from library/cassandra
f2aa67a397c4: Already exists 
7883c8e950c9: Pull complete 
17fef4315177: Pull complete 
de8642533b1e: Pull complete 
fc91ae190319: Pull complete 
c8de95d40c25: Pull complete 
d66bea82a2da: Pull complete 
6e85c3794992: Pull complete 
7e67c1874abb: Pull complete 
901a929c2fa8: Pull complete 
Digest: sha256:7155cb41dd1a508c5ea67b1750e98381d495873637aea6dcb9a5b13e3b2fb133
Status: Downloaded newer image for nexus3.onap.org:10001/library/cassandra:3.11


Can you please try again? I am wondering if this was a small glitch issue. 

Thanks!
Jess

On Wed Jun 27 10:10:46 2018, borislav.gloz...@amdocs.com wrote:
> Resending with helpdesk.
> 
> Thanks,
> Borislav Glozman
> O:+972.9.776.1988
> M:+972.52.2835726
> [amdocs-a]
> Amdocs a Platinum member of ONAP network/nfv-powered-by-onap>
> 
> From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org]
> On Behalf Of Borislav Glozman
> Sent: Tuesday, June 26, 2018 6:11 PM
> To: onap-discuss@lists.onap.org
> Cc: Jessica Wagantall 
> Subject: [onap-discuss] nexus3.onap.org stopped proxy of docker.io
> images
> 
> Hi,
> 
> I noticed when deploying ONAP deployment on K8S that images that come
> from docker.io are not downloaded via nexus3.onap.org
> For example: nexus3.onap.org:10001/ library/cassandra:3.11
> I am getting error from nexus3:
> https://nexus3.onap.org/repository/docker.io/v2/library/cassandra/manifests/3.11
> {"errors":[{"code":"UNAUTHORIZED","message":"authentication
> required","detail":[{"Type":"repository","Class":"","Name":"library/cassandra","Action":"pull"}]}]}
> 
> Path
> 
> v2/library/cassandra/manifests/3.11
> 
> Content type
> 
> application/vnd.docker.distribution.manifest.v2+json
> 
> File size
> 
> 2.4 KB
> 
> Blob created
> 
> Wed Apr 25 2018 09:35:44 GMT+0300 (Israel Daylight Time)
> 
> Blob updated
> 
> Mon Apr 30 2018 13:27:29 GMT+0300 (Israel Daylight Time)
> 
> Last 30 days
> 
> 0 downloads
> 
> Last downloaded
> 
> Tue Jun 26 2018 18:05:21 GMT+0300 (Israel Daylight Time)
> 
> Locally cached
> 
> true
> 
> Blob reference
> 
> default@BE552485-1ACD19AD-4F5AA0F6-50E80C8B-4ADDA1F1:e52b1b31-05f6-
> 4d93-bff9-0219fb055389
> 
> Containing repo
> 
> docker.io
> 
> Uploader
> 
> docker
> 
> Uploader's IP Address
> 
> 66.46.199.130
> 
> 
> Could you please fix this?
> 
> Thanks,
> Borislav Glozman
> O:+972.9.776.1988
> M:+972.52.2835726
> [amdocs-a]
> Amdocs a Platinum member of ONAP network/nfv-powered-by-onap>
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 




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

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

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

[Jessica Wagantall via RT]

Reviving this request. 

Do we need more discussion about this?
Is this requests still applicable?

Thanks!
Jess

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

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

[Jessica Wagantall via RT]

Reviving this request. 

Do we need more discussion about this?
Is this requests still applicable?

Thanks!
Jess

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

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

[Jessica Wagantall via RT]

Closing this thread for now to keep the RT queue cleaned and being able to 
focus on other issues. 

This issue is being monitored constantly however and I am keeping an eye on it 
after having
increased the snapshot rule for removing old images from 15 to 25 days. 

Thanks!
Jess


On Fri May 18 19:15:54 2018, gary.i...@huawei.com wrote:
> 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 
> 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 
> > 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 ; 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
> >

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

[Jessica Wagantall via RT]

Closing this thread for now to keep the RT queue cleaned and being able to 
focus on other issues. 

This issue is being monitored constantly however and I am keeping an eye on it 
after having
increased the snapshot rule for removing old images from 15 to 25 days. 

Thanks!
Jess


On Wed May 09 17:24:01 2018, gary.i...@huawei.com wrote:
> 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 
> 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

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

[Jessica Wagantall via RT]

Closing this thread for now to keep the RT queue cleaned and being able to 
focus on other issues. 

This issue is being monitored constantly however and I am keeping an eye on it 
after having
increased the snapshot rule for removing old images from 15 to 25 days. 

Thanks!
Jess

On Tue May 29 12:50:35 2018, gary.i...@huawei.com wrote:
> Hi Jess,
> 
> The image checking job just verifies that all the images listed in the
> manifest (the versions we use for deployment testing) are available.
> It doesn't know anything about when it was last deployed to nexus3.
> 
> Thanks,
> Gary
> 
> -Original Message-----
>  From: Jessica Wagantall via RT [mailto:onap-
> helpd...@rt.linuxfoundation.org]
> Sent: Thursday, May 24, 2018 11:01 PM
> To: Gary Wu 
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #56451] [portal] Missing Portal docker images
> 
> Gary,
> 
> Does this job takes in consideration that images from Snapshot will
> disappear after 16 days?
>  We still have this task in place that cleans up old images.
> 
> thanks!
> Jess
> 
> On Fri May 25 00:28:11 2018, jwagantall wrote:
> > 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/console
> > > >
> > > > 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 #56955] RE: Beijing Release: Last Mile

[Jessica Wagantall via RT]

This was completed

Thanks!
Jess

On Wed Jun 06 02:04:59 2018, denghu...@huawei.com wrote:
> Dear Jessica,
> 
> Sorry for late,
> 
> https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers-
> javatoscachecker-master-javatoscachecker-release-version-java-
> daily/209/
> https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers-
> nfvparser-master-nfvparser-release-version-java-daily/127/
> 
> thanks
> 
> DENG Hui
> 
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap-
> helpd...@rt.linuxfoundation.org]
> Sent: Wednesday, June 6, 2018 1:00 PM
> To: denghui (L) 
> Cc: Gildas Lanilis ; j...@research.att.com;
> onap-discuss@lists.onap.org; onap-rele...@lists.onap.org;
> rittwik.j...@gmail.com; shang.xiaod...@zte.com.cn;
> yangya...@chinamobile.com
> Subject: [ONAP Helpdesk #56955] RE: [onap-discuss] Beijing Release:
> Last Mile
> 
> Dear Deng,
> 
> Thanks, but I need you to give me the links to the Jenkins jobs that
> generated these please.
> 
> I cannot perform a release without them.
> 
> Thanks!
> Jess
> 
> On Tue Jun 05 22:48:45 2018, denghu...@huawei.com wrote:
> > Hi Jess,
> >
> > This is for modeling part, thanks a lot:
> >
> > Javatoscachecker:  /org/onap/modeling/toscaparsers/Checker/1.2.0-
> > SNAPSHOT/Checker-1.2.0-20180605.124309-
> > 60.jar<https://nexus.onap.org/service/local/repositories/snapshots/con
> > tent/org/onap/modeling/toscaparsers/Checker/1.2.0-
> > SNAPSHOT/Checker-1.2.0-20180605.124309-60.jar>
> > NFVParser:  /org/onap/modeling/toscaparsers/nfvparser/modeling-
> > toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-
> > nfvparser-
> > 1.1.0-20180329.050338-
> > 7.zip<https://nexus.onap.org/service/local/repositories/snapshots/cont
> > ent/org/onap/modeling/toscaparsers/nfvparser/modeling-
> > toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-
> > nfvparser-
> > 1.1.0-20180329.050338-7.zip>
> >
> > Deng Hui
> >
> > From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-
> > boun...@lists.onap.org] On Behalf Of Jessica Wagantall
> > Sent: Wednesday, June 6, 2018 6:16 AM
> > To: Gildas Lanilis 
> > Cc: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
> > Subject: Re: [onap-discuss] Beijing Release: Last Mile
> >
> > No request received yet also from the modeling team.
> >
> > Thanks!
> > Jess
> >
> > On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall
> > mailto:jwagant...@linuxfoundation.org>
> > >
> > wrote:
> > Dear Gildas,
> >
> > Here is an update on the pending items:
> >
> > *** MUSIC *** New release version 2.5.5 needed ***
> >
> > - Working with Tom on this now. We should be releasing soon.
> > Reference: #56927: Music Jar Release 2.5.5
> >
> > *** VID *** New clarification from the team ***
> >
> > - The request was placed to make a docker release but I noticed
> >their maven artifacts haven't been released for the specific
> > version
> > used
> >   to build their docker images. Do we approve a release of those too?
> > Reference: #56922: VID docker release
> >
> > *** AAF *** Pending Ram's Approval ***
> >
> > - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> > - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> > 8.jar<https://nexus.onap.org/index.html#view-
> > repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> > client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> > Reference: #56662: Artifacts for Release
> >
> > No release request yet from multicloud or usecase-ui teams!
> >
> > Thanks!
> > Jess
> >
> > On Mon, Jun 4, 2018 at 12:27 PM, Jessica Wagantall
> > mailto:jwagant...@linuxfoundation.org>
> > >
> > wrote:
> > Thanks a lot for this Gildas,
> >
> > Due to the importance of these releases, I will help posting here the
> > blockers we encounter in the RT tickets.
> >
> > Here are some blockers:
> >
> > *** AAF *** Pending Ram's Approval ***
> >
> > - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> > - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> > 8.jar<https://nexus.onap.org/index.html#view-
> > repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> > client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> > Reference: #56662: Artifacts for Release
> >
> > *** DMAAP *** Pending Ram's Approval

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

[Jessica Wagantall via RT]

Dear Lianhao, 

vnfsdk-pkgtools has been re-branched and re-tagged now

Thanks!
Jess

On Thu Jun 07 19:53:22 2018, lianhao...@intel.com wrote:
> Hi Jessica,
> 
> For vnfsdk-pkgtools, I think the 'beijing' tag should be applied to
> the current master tip version. The 'release/mercury' came from pre
> Amsterdam release, it came from Open-O.
> 
> Best Regards,
> -Lianhao
> 
> -Original Message-
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-
> boun...@lists.onap.org] On Behalf Of Jessica Wagantall via RT
> Sent: Friday, June 8, 2018 7:10 AM
> To: gildas.lani...@huawei.com
> Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org
> Subject: [onap-discuss] [ONAP Helpdesk #57038] beijing repo branching
> 
> Dear Gildas
> 
> All branches needed to be renamed from "Beijing" to "beijing" are now
> renamed.
> 
> All "beijing" branches have been created and tagged for all repos
> which my script detected no tag at all. These have been branched of
> from the tip of master. (See attached list "all-no-tags")
> 
> All "beijing" branches have been created for the repos which had
> release tags. The branching point was the latest tag available which
> should match the last version released. (See attached list "all-tags")
> From this particular list, I want to mention few important cases which
> my script detected:
> 
> 
> --has an 2.0.0-ONAP tag already (probably applied by the tech
> team). Couldn't move this tag to the tip of the beijing branch
> 
> dcaegen2-collectors-ves
> 
> --very old last release (Nov). beijing branch is as old as the
> amsterdam branch. I can help FF if the team wants
> 
> holmes-common
> holmes-dsa
> holmes-engine-management
> holmes-rule-management
> 
> --very old tag detected "release/mercury". beijing branch is as
> old as the amsterdam branch. I can help FF if the team wants
> 
> vnfsdk-lctest
> vnfsdk-pkgtools
> 
> 
> Please let me know for your comments.
> 
> Thanks!
> Jess
> 
> 
> On Thu Jun 07 19:02:38 2018, jwagantall wrote:
> > Dear Mike..
> >
> > Sorry i noticed this message a little bit late. I had created the
> > beijing branch for oom from the latest tag available. But I can
> > always
> > remove it and re-create it from whichever point you need.
> >
> > Just let me know if I should proceed removing it.
> >
> > Thanks!
> >  Jess
> >
> > > On Thu Jun 07 16:33:01 2018, mike.elli...@amdocs.com wrote:
> > > > Hey Jessica,
> > > >
> > > > We have a bit of a glitch in releasing and tagging all at once.
> > > > There
> > > >  is patch https://gerrit.onap.org/r/#/c/50937/ which needs to be
> > > > on
> > > >  the OOM Beijing branch, but can only be tested and merged once
> > > >  beijing branches are created for the repos referenced within
> > > > this
> > > > patch.
> > > > Is it possible to do this in two stages so we can make this
> > > > happen?
> > > >
> > > > Thanks,
> > > > Mike.
> > > >
> > > > On 6/7/18, 3:28 PM, "onap-discuss-boun...@lists.onap.org on
> > > > behalf
> > > > of Jessica Wagantall via RT"  > > > on behalf of onap-helpd...@rt.linuxfoundation.org> wrote:
> > > >
> > > > Thanks so much for gathering this information Gildas!
> > > > This is a great list!
> > > >
> > > > I have few questions:
> > > >
> > > > - Are the teams ok branching from the latest tip of master? (This
> > > > will make it easier on my script)
> > > > - Do the teams want me to tag the tip of the beijing branch with
> > > > "2.0.0-ONAP" tag?
> > > >
> > > > Thanks!
> > > > Jess
> > > >
> > > > On Thu Jun 07 15:23:43 2018, gildas.lani...@huawei.com wrote:
> > > > > Hi Helpdesk,
> > > > >
> > > > > Following TSC discussion on June 7, find in attachment the
> > > > > status of all ONAP repo and their need for a "beijing" branch.
> > > > > You will see that a lot has already been done.
> > > > >
> > > > > Thanks,
> > > > > Gildas
> > > > >
> > > > > [HuaweiLogowithName]
> > > > > Gildas Lanilis
> > > > > ONAP Release Manager
> > > > > Santa Clara CA, USA
> > > > > gildas.lani...@huawei.com
> > > > > Mobile: 1 415 238 6287
> > > >
> > > >
> > > >
> > > > ___
> > > > onap-discuss mailing list
> > > > onap-discuss@lists.onap.org
> > > > https://lists.onap.org/mailman/listinfo/onap-discuss
> > > >
> > > >
> > > > This message and the information contained herein is proprietary
> > > > and confidential and subject to the Amdocs policy statement,
> > > >
> > > > you may review at https://www.amdocs.com/about/email-disclaimer
> > > > <https://www.amdocs.com/about/email-disclaimer>
> 
> 
> 



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

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

[Jessica Wagantall via RT]

Dear Gildas

All branches needed to be renamed from "Beijing" to "beijing" are now renamed.

All "beijing" branches have been created and tagged for all repos which my 
script detected no
tag at all. These have been branched of from the tip of master. (See attached 
list "all-no-tags")

All "beijing" branches have been created for the repos which had release tags. 
The branching point
was the latest tag available which should match the last version released. (See 
attached list "all-tags")
>From this particular list, I want to mention few important cases which my 
>script detected:


--has an 2.0.0-ONAP tag already (probably applied by the tech team). 
Couldn't move this tag to the tip of the beijing branch

dcaegen2-collectors-ves

--very old last release (Nov). beijing branch is as old as the amsterdam 
branch. I can help FF if the team wants

holmes-common
holmes-dsa
holmes-engine-management
holmes-rule-management

--very old tag detected "release/mercury". beijing branch is as old as the 
amsterdam branch. I can help FF if the team wants

vnfsdk-lctest
vnfsdk-pkgtools


Please let me know for your comments. 

Thanks!
Jess


On Thu Jun 07 19:02:38 2018, jwagantall wrote:
> Dear Mike..
> 
> Sorry i noticed this message a little bit late. I had created the
> beijing branch for oom from the latest
> tag available. But I can always remove it and re-create it from
> whichever point you need.
> 
> Just let me know if I should proceed removing it.
> 
> Thanks!
>  Jess
> 
> > On Thu Jun 07 16:33:01 2018, mike.elli...@amdocs.com wrote:
> > > Hey Jessica,
> > >
> > > We have a bit of a glitch in releasing and tagging all at once.
> > > There
> > > is patch https://gerrit.onap.org/r/#/c/50937/ which needs to be on
> > > the
> > > OOM Beijing branch, but can only be tested and merged once beijing
> > > branches are created for the repos referenced within this patch.
> > > Is it possible to do this in two stages so we can make this happen?
> > >
> > > Thanks,
> > > Mike.
> > >
> > > On 6/7/18, 3:28 PM, "onap-discuss-boun...@lists.onap.org on behalf
> > > of
> > > Jessica Wagantall via RT"  > > behalf of onap-helpd...@rt.linuxfoundation.org> wrote:
> > >
> > > Thanks so much for gathering this information Gildas!
> > > This is a great list!
> > >
> > > I have few questions:
> > >
> > > - Are the teams ok branching from the latest tip of master? (This
> > > will
> > > make it easier on my script)
> > > - Do the teams want me to tag the tip of the beijing branch with
> > > "2.0.0-ONAP" tag?
> > >
> > > Thanks!
> > > Jess
> > >
> > > On Thu Jun 07 15:23:43 2018, gildas.lani...@huawei.com wrote:
> > > > Hi Helpdesk,
> > > >
> > > > Following TSC discussion on June 7, find in attachment the status
> > > > of
> > > > all ONAP repo and their need for a "beijing" branch.
> > > > You will see that a lot has already been done.
> > > >
> > > > Thanks,
> > > > Gildas
> > > >
> > > > [HuaweiLogowithName]
> > > > Gildas Lanilis
> > > > ONAP Release Manager
> > > > Santa Clara CA, USA
> > > > gildas.lani...@huawei.com
> > > > Mobile: 1 415 238 6287
> > >
> > >
> > >
> > > ___
> > > onap-discuss mailing list
> > > onap-discuss@lists.onap.org
> > > https://lists.onap.org/mailman/listinfo/onap-discuss
> > >
> > >
> > > This message and the information contained herein is proprietary
> > > and
> > > confidential and subject to the Amdocs policy statement,
> > >
> > > you may review at https://www.amdocs.com/about/email-disclaimer
> > > <https://www.amdocs.com/about/email-disclaimer>





all-no-tags
Description: Binary data


all-tags
Description: Binary data
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

[Jessica Wagantall via RT]

Dear Gildas

All branches needed to be renamed from "Beijing" to "beijing" are now renamed.

All "beijing" branches have been created and tagged for all repos which my 
script detected no
tag at all. These have been branched of from the tip of master. (See attached 
list "all-no-tags")

All "beijing" branches have been created for the repos which had release tags. 
The branching point
was the latest tag available which should match the last version released. (See 
attached list "all-tags")
>From this particular list, I want to mention few important cases which my 
>script detected:


--has an 2.0.0-ONAP tag already (probably applied by the tech team). 
Couldn't move this tag to the tip of the beijing branch

dcaegen2-collectors-ves

--very old last release (Nov). beijing branch is as old as the amsterdam 
branch. I can help FF if the team wants

holmes-common
holmes-dsa
holmes-engine-management
holmes-rule-management

--very old tag detected "release/mercury". beijing branch is as old as the 
amsterdam branch. I can help FF if the team wants

vnfsdk-lctest
vnfsdk-pkgtools


Please let me know for your comments. 

Thanks!
Jess


On Thu Jun 07 19:02:38 2018, jwagantall wrote:
> Dear Mike..
> 
> Sorry i noticed this message a little bit late. I had created the
> beijing branch for oom from the latest
> tag available. But I can always remove it and re-create it from
> whichever point you need.
> 
> Just let me know if I should proceed removing it.
> 
> Thanks!
>  Jess
> 
> > On Thu Jun 07 16:33:01 2018, mike.elli...@amdocs.com wrote:
> > > Hey Jessica,
> > >
> > > We have a bit of a glitch in releasing and tagging all at once.
> > > There
> > > is patch https://gerrit.onap.org/r/#/c/50937/ which needs to be on
> > > the
> > > OOM Beijing branch, but can only be tested and merged once beijing
> > > branches are created for the repos referenced within this patch.
> > > Is it possible to do this in two stages so we can make this happen?
> > >
> > > Thanks,
> > > Mike.
> > >
> > > On 6/7/18, 3:28 PM, "onap-discuss-boun...@lists.onap.org on behalf
> > > of
> > > Jessica Wagantall via RT"  > > behalf of onap-helpd...@rt.linuxfoundation.org> wrote:
> > >
> > > Thanks so much for gathering this information Gildas!
> > > This is a great list!
> > >
> > > I have few questions:
> > >
> > > - Are the teams ok branching from the latest tip of master? (This
> > > will
> > > make it easier on my script)
> > > - Do the teams want me to tag the tip of the beijing branch with
> > > "2.0.0-ONAP" tag?
> > >
> > > Thanks!
> > > Jess
> > >
> > > On Thu Jun 07 15:23:43 2018, gildas.lani...@huawei.com wrote:
> > > > Hi Helpdesk,
> > > >
> > > > Following TSC discussion on June 7, find in attachment the status
> > > > of
> > > > all ONAP repo and their need for a "beijing" branch.
> > > > You will see that a lot has already been done.
> > > >
> > > > Thanks,
> > > > Gildas
> > > >
> > > > [HuaweiLogowithName]
> > > > Gildas Lanilis
> > > > ONAP Release Manager
> > > > Santa Clara CA, USA
> > > > gildas.lani...@huawei.com
> > > > Mobile: 1 415 238 6287
> > >
> > >
> > >
> > > ___
> > > onap-discuss mailing list
> > > onap-discuss@lists.onap.org
> > > https://lists.onap.org/mailman/listinfo/onap-discuss
> > >
> > >
> > > This message and the information contained herein is proprietary
> > > and
> > > confidential and subject to the Amdocs policy statement,
> > >
> > > you may review at https://www.amdocs.com/about/email-disclaimer
> > > <https://www.amdocs.com/about/email-disclaimer>





all-no-tags
Description: Binary data


all-tags
Description: Binary data
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

[Jessica Wagantall via RT]

Dear Mike.. 

Sorry i noticed this message a little bit late. I had created the beijing 
branch for oom from the latest 
tag available. But I can always remove it and re-create it from whichever point 
you need.

Just let me know if I should proceed removing it.

Thanks!
Jess 

> On Thu Jun 07 16:33:01 2018, mike.elli...@amdocs.com wrote:
> > Hey Jessica,
> >
> > We have a bit of a glitch in releasing and tagging all at once. There
> > is patch https://gerrit.onap.org/r/#/c/50937/ which needs to be on
> > the
> > OOM Beijing branch, but can only be tested and merged once beijing
> > branches are created for the repos referenced within this patch.
> > Is it possible to do this in two stages so we can make this happen?
> >
> > Thanks,
> > Mike.
> >
> > On 6/7/18, 3:28 PM, "onap-discuss-boun...@lists.onap.org on behalf of
> > Jessica Wagantall via RT"  > behalf of onap-helpd...@rt.linuxfoundation.org> wrote:
> >
> > Thanks so much for gathering this information Gildas!
> > This is a great list!
> >
> > I have few questions:
> >
> > - Are the teams ok branching from the latest tip of master? (This
> > will
> > make it easier on my script)
> > - Do the teams want me to tag the tip of the beijing branch with
> > "2.0.0-ONAP" tag?
> >
> > Thanks!
> > Jess
> >
> > On Thu Jun 07 15:23:43 2018, gildas.lani...@huawei.com wrote:
> > > Hi Helpdesk,
> > >
> > > Following TSC discussion on June 7, find in attachment the status
> > > of
> > > all ONAP repo and their need for a "beijing" branch.
> > > You will see that a lot has already been done.
> > >
> > > Thanks,
> > > Gildas
> > >
> > > [HuaweiLogowithName]
> > > Gildas Lanilis
> > > ONAP Release Manager
> > > Santa Clara CA, USA
> > > gildas.lani...@huawei.com
> > > Mobile: 1 415 238 6287
> >
> >
> >
> > ___
> > onap-discuss mailing list
> > onap-discuss@lists.onap.org
> > https://lists.onap.org/mailman/listinfo/onap-discuss
> >
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > <https://www.amdocs.com/about/email-disclaimer>



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

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

[Jessica Wagantall via RT]

Dear Mike.. 

Sorry i noticed this message a little bit late. I had created the beijing 
branch for oom from the latest 
tag available. But I can always remove it and re-create it from whichever point 
you need.

Just let me know if I should proceed removing it.

Thanks!
Jess 

> On Thu Jun 07 16:33:01 2018, mike.elli...@amdocs.com wrote:
> > Hey Jessica,
> >
> > We have a bit of a glitch in releasing and tagging all at once. There
> > is patch https://gerrit.onap.org/r/#/c/50937/ which needs to be on
> > the
> > OOM Beijing branch, but can only be tested and merged once beijing
> > branches are created for the repos referenced within this patch.
> > Is it possible to do this in two stages so we can make this happen?
> >
> > Thanks,
> > Mike.
> >
> > On 6/7/18, 3:28 PM, "onap-discuss-boun...@lists.onap.org on behalf of
> > Jessica Wagantall via RT"  > behalf of onap-helpd...@rt.linuxfoundation.org> wrote:
> >
> > Thanks so much for gathering this information Gildas!
> > This is a great list!
> >
> > I have few questions:
> >
> > - Are the teams ok branching from the latest tip of master? (This
> > will
> > make it easier on my script)
> > - Do the teams want me to tag the tip of the beijing branch with
> > "2.0.0-ONAP" tag?
> >
> > Thanks!
> > Jess
> >
> > On Thu Jun 07 15:23:43 2018, gildas.lani...@huawei.com wrote:
> > > Hi Helpdesk,
> > >
> > > Following TSC discussion on June 7, find in attachment the status
> > > of
> > > all ONAP repo and their need for a "beijing" branch.
> > > You will see that a lot has already been done.
> > >
> > > Thanks,
> > > Gildas
> > >
> > > [HuaweiLogowithName]
> > > Gildas Lanilis
> > > ONAP Release Manager
> > > Santa Clara CA, USA
> > > gildas.lani...@huawei.com
> > > Mobile: 1 415 238 6287
> >
> >
> >
> > ___
> > onap-discuss mailing list
> > onap-discuss@lists.onap.org
> > https://lists.onap.org/mailman/listinfo/onap-discuss
> >
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > <https://www.amdocs.com/about/email-disclaimer>



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

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

[Jessica Wagantall via RT]

Dear Mike.. 

Sorry i noticed this message a little bit late. I had created the beijing 
branch for oom from the latest 
tag available. But I can always remove it and re-create it from whichever point 
you need.

Just let me know if I should proceed removing it.

Thanks!
Jess 

On Thu Jun 07 16:33:01 2018, mike.elli...@amdocs.com wrote:
> Hey Jessica,
> 
> We have a bit of a glitch in releasing and tagging all at once. There
> is patch https://gerrit.onap.org/r/#/c/50937/ which needs to be on the
> OOM Beijing branch, but can only be tested and merged once beijing
> branches are created for the repos referenced within this patch.
> Is it possible to do this in two stages so we can make this happen?
> 
> Thanks,
> Mike.
> 
> On 6/7/18, 3:28 PM, "onap-discuss-boun...@lists.onap.org on behalf of
> Jessica Wagantall via RT"  behalf of onap-helpd...@rt.linuxfoundation.org> wrote:
> 
> Thanks so much for gathering this information Gildas!
> This is a great list!
> 
> I have few questions:
> 
> - Are the teams ok branching from the latest tip of master? (This will
> make it easier on my script)
> - Do the teams want me to tag the tip of the beijing branch with
> "2.0.0-ONAP" tag?
> 
> Thanks!
> Jess
> 
> On Thu Jun 07 15:23:43 2018, gildas.lani...@huawei.com wrote:
> > Hi Helpdesk,
> >
> > Following TSC discussion on June 7, find in attachment the status of
> > all ONAP repo and their need for a "beijing" branch.
> > You will see that a lot has already been done.
> >
> > Thanks,
> > Gildas
> >
> > [HuaweiLogowithName]
> > Gildas Lanilis
> > ONAP Release Manager
> > Santa Clara CA, USA
> > gildas.lani...@huawei.com
> > Mobile: 1 415 238 6287
> 
> 
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
> 
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://www.amdocs.com/about/email-disclaimer>



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

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

[Jessica Wagantall via RT]

Thanks so much for gathering this information Gildas!
This is a great list!

I have few questions:

- Are the teams ok branching from the latest tip of master? (This will make it 
easier on my script)
- Do the teams want me to tag the tip of the beijing branch with "2.0.0-ONAP" 
tag?

Thanks!
Jess

On Thu Jun 07 15:23:43 2018, gildas.lani...@huawei.com wrote:
> Hi Helpdesk,
> 
> Following TSC discussion on June 7, find in attachment the status of
> all ONAP repo and their need for a "beijing" branch.
> You will see that a lot has already been done.
> 
> Thanks,
> Gildas
> 
> [HuaweiLogowithName]
> Gildas Lanilis
> ONAP Release Manager
> Santa Clara CA, USA
> gildas.lani...@huawei.com
> Mobile: 1 415 238 6287



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

[onap-discuss] [ONAP Helpdesk #56955] RE: Beijing Release: Last Mile

[Jessica Wagantall via RT]

Dear Deng, 

Thanks, but I need you to give me the links to the Jenkins jobs that generated 
these please. 

I cannot perform a release without them.

Thanks!
Jess
 
On Tue Jun 05 22:48:45 2018, denghu...@huawei.com wrote:
> Hi Jess,
> 
> This is for modeling part, thanks a lot:
> 
> Javatoscachecker:  /org/onap/modeling/toscaparsers/Checker/1.2.0-
> SNAPSHOT/Checker-1.2.0-20180605.124309-
> 60.jar SNAPSHOT/Checker-1.2.0-20180605.124309-60.jar>
> NFVParser:  /org/onap/modeling/toscaparsers/nfvparser/modeling-
> toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-
> 7.zip toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-7.zip>
> 
> Deng Hui
> 
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-
> boun...@lists.onap.org] On Behalf Of Jessica Wagantall
> Sent: Wednesday, June 6, 2018 6:16 AM
> To: Gildas Lanilis 
> Cc: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] Beijing Release: Last Mile
> 
> No request received yet also from the modeling team.
> 
> Thanks!
> Jess
> 
> On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall
> mailto:jwagant...@linuxfoundation.org>>
> wrote:
> Dear Gildas,
> 
> Here is an update on the pending items:
> 
> *** MUSIC *** New release version 2.5.5 needed ***
> 
> - Working with Tom on this now. We should be releasing soon.
> Reference: #56927: Music Jar Release 2.5.5
> 
> *** VID *** New clarification from the team ***
> 
> - The request was placed to make a docker release but I noticed
>   their maven artifacts haven't been released for the specific version
> used
>   to build their docker images. Do we approve a release of those too?
> Reference: #56922: VID docker release
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> No release request yet from multicloud or usecase-ui teams!
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 12:27 PM, Jessica Wagantall
> mailto:jwagant...@linuxfoundation.org>>
> wrote:
> Thanks a lot for this Gildas,
> 
> Due to the importance of these releases, I will help posting here the
> blockers we encounter in the RT tickets.
> 
> Here are some blockers:
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> *** DMAAP *** Pending Ram's Approval ***
> 
> - Docker release for onap/dmaap/dmaap-mr:1.1.4
> Reference: #56857: Move docker image to release repository
> 
> *** VFC *** Yan to clarify ***
> 
> - Email sent for 8 maven artifacts to be released, but email mentions
> also docker images needed and no link to docker images jobs
> - Do we just need to release the maven artifacts? if docker images
> need release, please update request with corresponding docker links
> from Jenkins
> Reference: #56821: Please help to release VF-C R2 artifacts to
> releases repo
> 
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 7:33 AM, Gildas Lanilis
> mailto:gildas.lani...@huawei.com>> wrote:
> Hi PTLs,
> 
> This email is to summarize on the latest activities to reach Beijing
> Release Sign-Off this Thursday, June 7, 2018.
> 
> 1.   Docker image: All projects that need to Release a new Docker
> Image (and thus update accordingly the Docker manifest file) must
> email LF Helpdesk by 2 pm PDT on Tuesday, June 5 including a link to
> the proper specific Jenkins build job that generated the selected
> candidate build (e.g.
> https://jenkins.onap.org/view/oparent/job/oparent-master-release-
> version-java-daily/124/). Ultimately, the Docker manifest
> file manifest/src/main/resources/docker-manifest.csv?h=beijing> (In Beijing
> Branch) should not contain words such as “latest”, “SNAPSHOT” or
> “STAGING” but only version number. If necessary, also update the Java
> manifest file. All the release process is documented in
> wiki.
> 
> 2.   Release Notes: I have updated for most projects the “Security
> Notes” within each Release Notes. Thanks to review and merge its
> 

[onap-discuss] [ONAP Helpdesk #56955] RE: Beijing Release: Last Mile

[Jessica Wagantall via RT]

Dear Deng, 

Thanks, but I need you to give me the links to the Jenkins jobs that generated 
these please. 

I cannot perform a release without them.

Thanks!
Jess
 
On Tue Jun 05 22:48:45 2018, denghu...@huawei.com wrote:
> Hi Jess,
> 
> This is for modeling part, thanks a lot:
> 
> Javatoscachecker:  /org/onap/modeling/toscaparsers/Checker/1.2.0-
> SNAPSHOT/Checker-1.2.0-20180605.124309-
> 60.jar SNAPSHOT/Checker-1.2.0-20180605.124309-60.jar>
> NFVParser:  /org/onap/modeling/toscaparsers/nfvparser/modeling-
> toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-
> 7.zip toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers-nfvparser-
> 1.1.0-20180329.050338-7.zip>
> 
> Deng Hui
> 
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-
> boun...@lists.onap.org] On Behalf Of Jessica Wagantall
> Sent: Wednesday, June 6, 2018 6:16 AM
> To: Gildas Lanilis 
> Cc: onap-rele...@lists.onap.org; onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] Beijing Release: Last Mile
> 
> No request received yet also from the modeling team.
> 
> Thanks!
> Jess
> 
> On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall
> mailto:jwagant...@linuxfoundation.org>>
> wrote:
> Dear Gildas,
> 
> Here is an update on the pending items:
> 
> *** MUSIC *** New release version 2.5.5 needed ***
> 
> - Working with Tom on this now. We should be releasing soon.
> Reference: #56927: Music Jar Release 2.5.5
> 
> *** VID *** New clarification from the team ***
> 
> - The request was placed to make a docker release but I noticed
>   their maven artifacts haven't been released for the specific version
> used
>   to build their docker images. Do we approve a release of those too?
> Reference: #56922: VID docker release
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> No release request yet from multicloud or usecase-ui teams!
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 12:27 PM, Jessica Wagantall
> mailto:jwagant...@linuxfoundation.org>>
> wrote:
> Thanks a lot for this Gildas,
> 
> Due to the importance of these releases, I will help posting here the
> blockers we encounter in the RT tickets.
> 
> Here are some blockers:
> 
> *** AAF *** Pending Ram's Approval ***
> 
> - Docker release for  onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0
> - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-
> 8.jar repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms-
> client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar>
> Reference: #56662: Artifacts for Release
> 
> *** DMAAP *** Pending Ram's Approval ***
> 
> - Docker release for onap/dmaap/dmaap-mr:1.1.4
> Reference: #56857: Move docker image to release repository
> 
> *** VFC *** Yan to clarify ***
> 
> - Email sent for 8 maven artifacts to be released, but email mentions
> also docker images needed and no link to docker images jobs
> - Do we just need to release the maven artifacts? if docker images
> need release, please update request with corresponding docker links
> from Jenkins
> Reference: #56821: Please help to release VF-C R2 artifacts to
> releases repo
> 
> 
> Thanks!
> Jess
> 
> On Mon, Jun 4, 2018 at 7:33 AM, Gildas Lanilis
> mailto:gildas.lani...@huawei.com>> wrote:
> Hi PTLs,
> 
> This email is to summarize on the latest activities to reach Beijing
> Release Sign-Off this Thursday, June 7, 2018.
> 
> 1.   Docker image: All projects that need to Release a new Docker
> Image (and thus update accordingly the Docker manifest file) must
> email LF Helpdesk by 2 pm PDT on Tuesday, June 5 including a link to
> the proper specific Jenkins build job that generated the selected
> candidate build (e.g.
> https://jenkins.onap.org/view/oparent/job/oparent-master-release-
> version-java-daily/124/). Ultimately, the Docker manifest
> file manifest/src/main/resources/docker-manifest.csv?h=beijing> (In Beijing
> Branch) should not contain words such as “latest”, “SNAPSHOT” or
> “STAGING” but only version number. If necessary, also update the Java
> manifest file. All the release process is documented in
> wiki.
> 
> 2.   Release Notes: I have updated for most projects the “Security
> Notes” within each Release Notes. Thanks to review and merge its
> 

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

[Jessica Wagantall via RT]

Rejecting for now. 

Please create a new request once the information/planning is ready. 

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

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

[Jessica Wagantall via RT]

Thanks a ton Manoop 

Why are we using release tags for the snapshots repo? :(

Thanks!
Jess

On Fri May 25 14:04:24 2018, talas...@research.att.com wrote:
> I posted the “please release” and the portal dockers are now
> regenerated.
> 
> From: "TALASILA, MANOOP (MANOOP)" <talas...@research.att.com>
> Date: Friday, May 25, 2018 at 6:06 AM
> To: "gary.i...@huawei.com" <gary.i...@huawei.com>, "onap-
> helpd...@rt.linuxfoundation.org"  helpd...@rt.linuxfoundation.org>
> Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
> Subject: Re: [onap-discuss] [ONAP Helpdesk #56451] [portal] Missing
> Portal docker images
> 
> Should I post "please release" on this last commit to generate the
> dockers again?
> https://gerrit.onap.org/r/#/c/47453/
> Manoop
> 
> 
> 
> On Fri, May 25, 2018 at 2:00 AM -0400, "Jessica Wagantall via RT"
> <onap-helpd...@rt.linuxfoundation.org<mailto:onap-
> helpd...@rt.linuxfoundation.org>> wrote:
> 
> Gary,
> 
> 
> 
> Does this job takes in consideration that images from Snapshot will
> disappear after 16 days?
> 
> We still have this task in place that cleans up old images.
> 
> 
> 
> thanks!
> 
> Jess
> 
> 
> 
> On Fri May 25 00:28:11 2018, jwagantall wrote:
> 
> > 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
> 
> > > >
> 
> > > > https://urldefense.proofpoint.com/v2/url?u=http-
> > > > 3A__12.234.32.117_jenkins_job_nexus3-2Ddocker-2Dimage-
> > > > 2D=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-
> > > > U2OvGp0SXnE4nO3a-LJ-
> > > > q_w=WkgzEHl_Yg2WhBHmINkZ9K6Ba3O8XPDeRPmjFyfYpk4=ftzVNBIMAa9lmgnKGdEFIImEnWghpHlr9vVw8-
> > > > q9Jl8=
> 
> > > > check/321/console
> 
> > > >
> 
> > > > Please help.
> 
> > > >
> 
> > > > 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=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-
> q_w=WkgzEHl_Yg2WhBHmINkZ9K6Ba3O8XPDeRPmjFyfYpk4=UmM42pkfj1SWM8jSIau6goEJgv0_RDVH16rzm2qBX9k=



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

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

[Jessica Wagantall via RT]

Gary, 

Does this job takes in consideration that images from Snapshot will disappear 
after 16 days?
We still have this task in place that cleans up old images. 

thanks!
Jess

On Fri May 25 00:28:11 2018, jwagantall wrote:
> 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/console
> > >
> > > 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 #56451] [portal] Missing Portal docker images

[Jessica Wagantall via RT]

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/console
> > 
> > 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 #56451] [portal] Missing Portal docker images

[Jessica Wagantall via RT]

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/console
> 
> 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] [so] mso:1.2.1 image missing

[Jessica Wagantall via RT]

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

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

[Jessica Wagantall via RT]

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 ; 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: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 > 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; onap-
> > disc...@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

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

[Jessica Wagantall via RT]

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 ; 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: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 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; onap-
> disc...@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

[onap-discuss] [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at least 10x slower at 1MB/sec

[Jessica Wagantall via RT]

Thank you Michael!

Let's sync up on this after the weekend. 

Thanks!
Jess

On Fri May 18 14:58:32 2018, frank.obr...@amdocs.com wrote:
> Jessica,
>   On my public systems I have not seen any issues - but I have not run
> a bmon lately.
>   I'll do one over the weekend and was also planning on adding a
> Jenkins job
>   Looks good so far.
>   /michael
> 
> -Original Message-
>  From: Jessica Wagantall via RT [mailto:onap-
> helpd...@rt.linuxfoundation.org]
> Sent: Friday, May 18, 2018 2:38 PM
> To: Michael O'Brien <frank.obr...@amdocs.com>
> Cc: gildas.lani...@huawei.com; onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at
> least 10x slower at 1MB/sec
> 
> Hi Michael,
> 
> I just wanted to check in.
> 
> How are things going in Nexus3? are you seeing an improvement since
> the last time we met for this?
> 
> thanks!
> Jess
> 
> On Tue May 01 13:00:45 2018, jwagantall wrote:
> > Actually, I think this is the latest ticket on this issue,
> >
> > I will leave this opened and continue our investigation here and
> > close
> > other instances  of the same issue.
> >
> > Thanks!
> > Jess
> >
> > On Tue May 01 12:59:52 2018, jwagantall wrote:
> > > Dear Michael and Gildas,
> > >
> > > After our meeting yesterday with Mo, I spoke yesterday to Ryan and
> > > asked him if he could please  be able to look into the GC task that
> > > seems to be causing some of these issues and to also look at the
> > > heap and memory sizes to make sure we are able to use the
> > > resources
> > > we have more efficiently.
> > >
> > > I will close this ticket for now since there are many instances of
> > > the same problem and just  leave the latest topic opened so that we
> > > can put all our comments there.
> > >
> > > Thanks!
> > > Jess
> > >
> > > On Mon Apr 16 14:02:53 2018, frank.obr...@amdocs.com wrote:
> > > > LF,
> > > >Hi, there seems to be an issue since last Thursday where
> > > > nexus3.onap.org:10001 is severely throttled.
> > > > On my azure/aws instances I am getting around 1 MB/sec where
> > > >  previously I could download at least 10 streams at about 10+
> > > > MB/sec before wed.
> > > >
> > > > https://git.onap.org/oom/tree/kubernetes/config/prepull_docker.sh
> > > >
> > > > To reproduce run the above script on an oom deployment.
> > > > Tracking this issue in OOM-942 and its' linked jiras
> > > > https://jira.onap.org/browse/OOM-942
> > > > These stats for example ( a byproduct of how the script runs) are
> > > > 10
> > > > sec apart and show the actual speed for a single remaining pull.
> > > >
> > > > a244880be6ed: Downloading [>
> > > > ] 2.639 MB/160.9 MB
> > > > a244880be6ed: Downloading [=>
> > > > ] 3.688 MB/160.9 MB
> > > > a244880be6ed: Downloading [=>
> > > > ] 5.796 MB/160.9 MB
> > > > a244880be6ed: Downloading [==>
> > > > ] 7.908 MB/160.9 MB
> > > > a244880be6ed: Downloading [==>
> > > > ] 9.487 MB/160.9 MB
> > > > a244880be6ed: Downloading [===>
> > > > ] 11.07 MB/160.9 MB
> > > > a244880be6ed: Downloading [>
> > > > ] 13.71 MB/160.9 MB
> > > > a244880be6ed: Downloading [=>
> > > > ] 16.34 MB/160.9 MB
> > > > a244880be6ed: Downloading [=>
> > > > ] 18.45 MB/160.9 MB
> > > > a244880be6ed: Downloading [==> ] 20.56 MB/160.9 MB
> > > > a244880be6ed: Downloading [==> ] 21.61 MB/160.9 MB
> > > > a244880be6ed: Downloading [> ] 26.36 MB/160.9 MB
> > > > a244880be6ed: Downloading [> ] 27.94 MB/160.9 MB
> > > > a244880be6ed: Downloading [=> ] 31.63 MB/160.9 MB
> > > > a244880be6ed: Downloading [==> ]  34.8 MB/160.9 MB
> > > >  a244880be6ed: Downloading [===> ] 35.85 MB/160.9 MB
> > > > waiting for last pull
> > > >
> > > >
> > > >
> > > > Michael O'Brien
> > > > Amdocs Technology
> > > > 16135955268
> > > > 55268
> > > > [amdocs-a]
> > > >
> > > > This message and the information contained herein is proprietary
> > > > and confidential and subject to the Amdocs policy statement,
> > > >
> > > > you may review at https://www.amdocs.com/about/email-disclaimer
> > > > <https://www.amdocs.com/about/email-disclaimer>
> 
> 
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://www.amdocs.com/about/email-disclaimer>



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

[onap-discuss] [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at least 10x slower at 1MB/sec

[Jessica Wagantall via RT]

Hi Michael, 

I just wanted to check in. 

How are things going in Nexus3? are you seeing an improvement since the last 
time we met for this?

thanks!
Jess

On Tue May 01 13:00:45 2018, jwagantall wrote:
> Actually, I think this is the latest ticket on this issue,
> 
> I will leave this opened and continue our investigation here and close
> other instances
>  of the same issue.
> 
> Thanks!
> Jess
> 
> On Tue May 01 12:59:52 2018, jwagantall wrote:
> > Dear Michael and Gildas,
> >
> > After our meeting yesterday with Mo, I spoke yesterday to Ryan and
> > asked him if he could please
> >  be able to look into the GC task that seems to be causing some of
> > these issues and
> > to also look at the heap and memory sizes to make sure we are able to
> > use the
> >  resources we have more efficiently.
> >
> > I will close this ticket for now since there are many instances of
> > the
> > same problem and just
> >  leave the latest topic opened so that we can put all our comments
> > there.
> >
> > Thanks!
> > Jess
> >
> > On Mon Apr 16 14:02:53 2018, frank.obr...@amdocs.com wrote:
> > > LF,
> > >Hi, there seems to be an issue since last Thursday where
> > > nexus3.onap.org:10001 is severely throttled.
> > >On my azure/aws instances I am getting around 1 MB/sec where
> > > previously I could download at least 10 streams at about 10+ MB/sec
> > > before wed.
> > >https://git.onap.org/oom/tree/kubernetes/config/prepull_docker.sh
> > >
> > > To reproduce run the above script on an oom deployment.
> > > Tracking this issue in OOM-942 and its' linked jiras
> > > https://jira.onap.org/browse/OOM-942
> > > These stats for example ( a byproduct of how the script runs) are
> > > 10
> > > sec apart and show the actual speed for a single remaining pull.
> > >
> > > a244880be6ed: Downloading [>
> > > ] 2.639 MB/160.9 MB
> > > a244880be6ed: Downloading [=>
> > > ] 3.688 MB/160.9 MB
> > > a244880be6ed: Downloading [=>
> > > ] 5.796 MB/160.9 MB
> > > a244880be6ed: Downloading [==>
> > > ] 7.908 MB/160.9 MB
> > > a244880be6ed: Downloading [==>
> > > ] 9.487 MB/160.9 MB
> > > a244880be6ed: Downloading [===>
> > > ] 11.07 MB/160.9 MB
> > > a244880be6ed: Downloading [>
> > > ] 13.71 MB/160.9 MB
> > > a244880be6ed: Downloading [=>
> > > ] 16.34 MB/160.9 MB
> > > a244880be6ed: Downloading [=>
> > > ] 18.45 MB/160.9 MB
> > > a244880be6ed: Downloading [==>
> > > ] 20.56 MB/160.9 MB
> > > a244880be6ed: Downloading [==>
> > > ] 21.61 MB/160.9 MB
> > > a244880be6ed: Downloading [>
> > > ] 26.36 MB/160.9 MB
> > > a244880be6ed: Downloading [>
> > > ] 27.94 MB/160.9 MB
> > > a244880be6ed: Downloading [=>
> > > ] 31.63 MB/160.9 MB
> > > a244880be6ed: Downloading [==>
> > > ]  34.8 MB/160.9 MB
> > > a244880be6ed: Downloading [===>
> > > ] 35.85 MB/160.9 MB
> > > waiting for last pull
> > >
> > >
> > >
> > > Michael O'Brien
> > > Amdocs Technology
> > > 16135955268
> > > 55268
> > > [amdocs-a]
> > >
> > > This message and the information contained herein is proprietary
> > > and
> > > confidential and subject to the Amdocs policy statement,
> > >
> > > you may review at https://www.amdocs.com/about/email-disclaimer
> > > 



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

[onap-discuss] [ONAP Helpdesk #55854] RE: [integration] Problem with integration CSIT tests not being able to execute docker-compose

[Jessica Wagantall via RT]

Are you guys still seeing docker-compose issues?

Please let me know and I can look 

thanks!
Jess

On Fri May 11 14:57:22 2018, pdrag...@research.att.com wrote:
> Unfortunately, now the problem has reappeared again:
> 
> 18:51:22 /w/workspace/policy-master-csit-
> health/test/csit/scripts/policy/script1.sh: line 97:
> /usr/local/bin/docker-compose: Permission denied
> 18:51:22 +++ '[' '!' 126 -eq 0 ']'
> 18:51:22 +++ echo 'Docker compose failed'
> 18:51:22 Docker compose failed
> 
> 
> https://jenkins.onap.org/view/policy/job/policy-master-csit-
> health/883/
> 
> Can the LF team take a look at this?
> 
> Thanks,
> 
> Pam
> 
> 
> From: "TALASILA, MANOOP (MANOOP)" 
> Date: Thursday, May 10, 2018 at 11:00 AM
> To: "DRAGOSH, PAMELA L (PAM)" , Gary Wu
> , "onap-discuss@lists.onap.org"  disc...@lists.onap.org>, "helpd...@onap.org" 
> Subject: Re: [onap-discuss] [integration] Problem with integration
> CSIT tests not being able to execute docker-compose
> 
> Yes, seems like it is fixed now (however, did not hear anything from
> the filed ticket though).
> 
> Manoop
> 
> From:  on behalf of "DRAGOSH,
> PAMELA L (PAM)" 
> Date: Thursday, May 10, 2018 at 10:49 AM
> To: Gary Wu , "onap-discuss@lists.onap.org"
> , "helpd...@onap.org" 
> Subject: Re: [onap-discuss] [integration] Problem with integration
> CSIT tests not being able to execute docker-compose
> 
> ***Security Advisory: This Message Originated Outside of AT ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more
> information.
> 
> 
> 
> It seems to have magically fixed itself.
> 
> The portal team saw the problem also and had filed a ticket, so
> perhaps it got fixed.
> 
> Pam
> 
> From: Gary Wu 
> Date: Thursday, May 10, 2018 at 10:45 AM
> To: "DRAGOSH, PAMELA L (PAM)" , "onap-
> disc...@lists.onap.org" ,
> "helpd...@onap.org" 
> Subject: RE: [onap-discuss] [integration] Problem with integration
> CSIT tests not being able to execute docker-compose
> 
> Not sure if LF has changed the installation process of docker-compose
> recently.
> 
> Helpdesk, can you help?
> 
> Thanks,
> Gary
> 
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-
> boun...@lists.onap.org] On Behalf Of DRAGOSH, PAMELA L (PAM)
> Sent: Thursday, May 10, 2018 6:00 AM
> To: onap-discuss@lists.onap.org
> Subject: [onap-discuss] [integration] Problem with integration CSIT
> tests not being able to execute docker-compose
> 
> Gary et all,
> 
> It seems that a Policy CSIT failed because the docker-compose binary
> has permission denied:
> 
> https://jenkins.onap.org/view/policy/job/policy-master-csit-
> health/875/console 3A__jenkins.onap.org_view_policy_job_policy-2Dmaster-2Dcsit-
> 2Dhealth_875_console=DwMGaQ=LFYZ-
> o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=dshN1ybPtn9OBMkI2URT6_HjNz58JJoX_WsxIj7WH7g=o1iyTT807dywlh6332xO9aafzAlPJZEefVKbyNYCIsI=>
> 
> /w/workspace/policy-master-csit-
> health/test/csit/scripts/policy/script1.sh: line 99:
> /usr/local/bin/docker-compose: Permission denied
> 22:44:25 +++ '[' '!' 126 -eq 0 ']'
> 
> Did something change in the integration repo or the base Jenkins Job
> for this to occur?
> 
> Thanks,
> 
> Pam Dragosh
> ONAP Policy PTL
> 
> 



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

[onap-discuss] [ONAP Helpdesk #56089] [LF] Gerrit review fails to push on jetty 404 looking for /tools/hooks/commit-msg

[Jessica Wagantall via RT]

urs) Changes to be
> committed:
>   (use "git reset HEAD ..." to unstage)
> 
> modified:   deploy/cd.sh
> 
> obrienbiometrics:logging-analytics michaelobrien$ git commit --amend
> [master 6f718d2] cd.sh oom deployment script
>  Date: Mon May 14 20:25:45 2018 -0400
>  1 file changed, 365 insertions(+)
>  create mode 100755 deploy/cd.sh
> obrienbiometrics:logging-analytics michaelobrien$ git review -R
> Warning: Permanently added
> '[gerrit.onap.org]:29418,[198.145.29.92]:29418' (RSA) to the list of
> known hosts.
> remote: Processing changes: updated: 1, refs: 1, done
>  remote:
> remote: Updated Changes:
> remote:   https://gerrit.onap.org/r/47503 cd.sh oom deployment
> script
>  remote:
> To ssh://gerrit.onap.org:29418/logging-analytics
>  * [new branch]  HEAD -> refs/publish/master
> 
> 
> -Original Message-
> From: Jessica Wagantall via RT [mailto:onap-
> helpd...@rt.linuxfoundation.org]
> Sent: Wednesday, May 16, 2018 7:17 PM
> To: Michael O'Brien <frank.obr...@amdocs.com>
> Cc: onap-discuss@lists.onap.org
> Subject: [ONAP Helpdesk #56089] [LF] Gerrit review fails to push on
> jetty 404 looking for /tools/hooks/commit-msg
> 
> Michael,
> 
> Are you able to push the code using git push?
> 
> Thanks!
> Jess
> 
> 
> On Wed May 16 19:02:37 2018, frank.obr...@amdocs.com wrote:
> > Team,
> > Hi, having a new issue pushing code to gerrit - getting a 404 -
> >  where previously if there was a commit message format issue it would
> > notify you of the cause - getting a 404 now.
> >Pushing reviews a couple days ago had no issues.
> >Is anyone else having issues pushing a new gerrit review
> > Will amend "git review -R" and existing review to see if it is
> > just
> > for new commits
> >
> > Details on
> > https://jira.onap.org/browse/LOG-376
> >
> >
> > obrienbiometrics:log-376b michaelobrien$ cd oom
> >
> > obrienbiometrics:oom michaelobrien$ git status
> >
> > On branch master
> >
> > Your branch is up-to-date with 'origin/master'.
> >
> > Changes to be committed:
> >
> > (use "git reset HEAD ..." to unstage)
> >
> >
> >
> > modified:   kubernetes/log/charts/log-logstash/values.yaml
> >
> >
> >
> > obrienbiometrics:oom michaelobrien$ git commit -am "log logstash
> > replicaset to 3"
> >
> > [master 8324970] log logstash replicaset to 3
> >
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > obrienbiometrics:oom michaelobrien$ git commit -s --amend
> >
> > [master 05509fc] log logstash replicaset to 3
> >
> > Date: Wed May 16 18:55:11 2018 -0400
> >
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > obrienbiometrics:oom michaelobrien$ git review
> >
> > Problems encountered installing commit-msg hook
> >
> > The following command failed with exit code 104
> >
> > "GET https://michaelobr...@gerrit.onap.org/tools/hooks/commit-msg;
> >
> > ---
> >
> > 
> >
> > 
> >
> > 
> >
> > Error 404 
> >
> > 
> >
> > 
> >
> > HTTP ERROR: 404
> >
> > Problem accessing /tools/hooks/commit-msg. Reason:
> >
> > Not Found
> >
> > Powered by Jetty://
> >
> > 
> >
> > 
> >
> >
> >
> > ---
> > *
> > Co<https://jira.onap.org/secure/AddComment!default.jspa?id=22902>
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > <https://www.amdocs.com/about/email-disclaimer>
> 
> 
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://www.amdocs.com/about/email-disclaimer>
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> <https://www.amdocs.com/about/email-disclaimer>



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

[onap-discuss] [ONAP Helpdesk #56089] [LF] Gerrit review fails to push on jetty 404 looking for /tools/hooks/commit-msg

[Jessica Wagantall via RT]

Michael, 

Are you able to push the code using git push?

Thanks!
Jess


On Wed May 16 19:02:37 2018, frank.obr...@amdocs.com wrote:
> Team,
>Hi, having a new issue pushing code to gerrit - getting a 404 -
> where previously if there was a commit message format issue it would
> notify you of the cause - getting a 404 now.
>Pushing reviews a couple days ago had no issues.
>Is anyone else having issues pushing a new gerrit review
>Will amend "git review -R" and existing review to see if it is just
> for new commits
> 
> Details on
> https://jira.onap.org/browse/LOG-376
> 
> 
> obrienbiometrics:log-376b michaelobrien$ cd oom
> 
> obrienbiometrics:oom michaelobrien$ git status
> 
> On branch master
> 
> Your branch is up-to-date with 'origin/master'.
> 
> Changes to be committed:
> 
> (use "git reset HEAD ..." to unstage)
> 
> 
> 
> modified:   kubernetes/log/charts/log-logstash/values.yaml
> 
> 
> 
> obrienbiometrics:oom michaelobrien$ git commit -am "log logstash
> replicaset to 3"
> 
> [master 8324970] log logstash replicaset to 3
> 
> 1 file changed, 2 insertions(+), 1 deletion(-)
> 
> obrienbiometrics:oom michaelobrien$ git commit -s --amend
> 
> [master 05509fc] log logstash replicaset to 3
> 
> Date: Wed May 16 18:55:11 2018 -0400
> 
> 1 file changed, 2 insertions(+), 1 deletion(-)
> 
> obrienbiometrics:oom michaelobrien$ git review
> 
> Problems encountered installing commit-msg hook
> 
> The following command failed with exit code 104
> 
> "GET https://michaelobr...@gerrit.onap.org/tools/hooks/commit-msg;
> 
> ---
> 
> 
> 
> 
> 
> 
> 
> Error 404 
> 
> 
> 
> 
> 
> HTTP ERROR: 404
> 
> Problem accessing /tools/hooks/commit-msg. Reason:
> 
> Not Found
> 
> Powered by Jetty://
> 
> 
> 
> 
> 
> 
> 
> ---
> *
> Co
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

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

[Jessica Wagantall via RT]

Please let me know if I can help. 

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

thanks!
Jess

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



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

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

[Jessica Wagantall via RT]

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

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

[Jessica Wagantall via RT]

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

[onap-discuss] [ONAP Helpdesk #55626] Gerrit is down

[Jessica Wagantall via RT]

Dear team, 

we are back on track now.. 

Everything is working .

thanks!
Jess

On Fri May 04 14:22:29 2018, jconway wrote:
> Hello,
> We are experiencing an issue with our edge firewalls, you can follow
> the incident here
> 
> https://status.linuxfoundation.org/incidents/zjkddd9wt0yt
> 
> Sorry for any inconvenience.
> 
> Best regards,
> Jordan Conway



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

[onap-discuss] [ONAP Helpdesk #54730] Adjust for Healthcheck timeouts when running HC before the system is ready when docker pulls timeout

[Jessica Wagantall via RT]

After our meeting yesterday with Mo, I spoke yesterday to Ryan and asked him if 
he could please
be able to look into the GC task that seems to be causing some of these issues 
and 
to also look at the heap and memory sizes to make sure we are able to use the
resources we have more efficiently. 

I will close this ticket for now since there are many instances of the same 
problem and just
leave the latest topic opened so that we can put all our comments there. 

Thanks!
Jess

On Thu Apr 12 21:52:38 2018, frank.obr...@amdocs.com wrote:
> Team,
> Since 9 AM EDT GME-5 there has been slowdown issues with nexus3
> docker downloads
> 
> The effect of this has been that it takes longer for the system to
> come up - an increase from 35-45 to 60+ min.
> A secondary effect of this slowdown is that robot healthcheck will
> experience multiple timeouts on unhealthly containers - which will in
> some cases run to a total of 14 min.
> Therefore I am adjusting both the time to wait for a system to come up
> to 80 min and reduce the number of warming healthcheck runs from 3 to
> 2. So we can continue to fit in a 2 hour timeslot.
>  With the new helm root values.yaml we can swap out the docker repo
> for a local one - we are also testing this as a workaround.
> 
> Currently there are issues with 7 containers causing 13 others to pend
> in the init state.
> There is one image pull issue with smsdb-0 that is a wrong image tag
> and not related to the nexus3 slowdown - See OOM-902
> 
> Some days nexus3.onap.info works fine and pulls take around 30 min
> Other days like today pulls take over 90 min.
> Perhaps we can institute a network throughput page on nexus3 to help
> track it
> 
> Thank you
> /michael
> 
> Michael O'Brien
> Amdocs Technology
> 16135955268
> 55268
> [amdocs-a]
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #55415] nexus3 slowdown (burst/pause) behavior - propose 2nd LF meeting

[Jessica Wagantall via RT]

Closing this ticket and replying on RT54849

Ryan is helping us adjusting the GC tasks so that they wont slow down our 
performance
as well as adjusting the heap sizes. 

Thanks!
Jess

On Mon Apr 30 14:17:17 2018, jwagantall wrote:
> + Mo
> 
> Dear Michael,
> 
> I did noticed once last week a pull that failed for me immediately for
> no reason and had to restart.
> 
> Mo, do you think you can join us for a quick debugging session some
> time today please?
> 
> Thanks a ton!
> Jess
> 
> 
> 
> On Mon Apr 30 11:56:28 2018, frank.obr...@amdocs.com wrote:
> > LF,
> >Hi, we have been seeing burst behavior for the last week. This
> > morning in the integration lab session we see this on multiple
> > machines.
> >Downloads are fast when they are running - but completely stall
> > every min or so for 30-60 sec.
> >
> > For example pulling the dmaap container manually - a single pull took
> > 3 min on one system - 18 on antoher and had sections where the job
> > ran
> > about 1 to 5 with bursts to 25 Mb/sec (max is usually 10Mb/sec per
> > stream - up to 5 in parallel - I have seen 25) - but there were times
> > 30-60 sec where the image download completely paused at 0Mb/sec.
> >
> > This behavior is different or is in combination with the traditional
> > slowdown we used to see  - very slow pulls - this issue is new in
> > that
> > it works fine during the burst - but has sections where all pulls
> > pause.  To be frank - I did see this pause behavior briefly for a
> > couple seconds back even in Dec.
> >
> >
> > I propose we meet again to test downloads again and get some
> > volumetrics.
> > Some details on this and previous issues in
> >
> > https://jira.onap.org/browse/OOM-933
> >
> > Time 1130 EST 20180430
> >
> > see slowdown again after our last meeting - a burst behaviour
> > (burst/hold in 30-60 sec intervals)
> >
> > This in an azure system (clean) running a manual docker download -
> > see
> > attachment on OOM-716
> >
> > root@obrienondemand20180430:/var/lib/waagent/custom-
> > script/download/0#
> > history
> >
> > 1  cd /var/lib/waagent/custom-script/download/0/
> >
> > 2  ls
> >
> > 3  tail -f stdout
> >
> > 4  wget
> > https://jira.onap.org/secure/attachment/11444/prepull_docker_master.sh
> >
> > 6  sudo chmod 777 prepull_docker_master.sh
> >
> > 7  vi prepull_docker_master.sh
> >
> > 8  docker login -u docker -p docker nexus3.onap.org:10001
> >
> > 9  docker pull nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> >
> > 10  vi prepull_docker_master.sh
> >
> > 11  docker pull nexus3.onap.org:10001/onap/vid:1.2.1
> >
> > 12  docker pull nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> >
> >
> >
> >
> >
> > root@obrienondemand20180430:/var/lib/waagent/custom-
> > script/download/0#
> > docker pull nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> >
> > 1.1.4: Pulling from onap/dmaap/dmaap-mr
> >
> > 0c5a750448f5: Pull complete
> >
> > e2356a247318: Pull complete
> >
> > 12f105c650c3: Pull complete
> >
> > 46d4cec7ab72: Pull complete
> >
> > f5b0369aa7fc: Pull complete
> >
> > a93519a09c8b: Pull complete
> >
> > 73ffcbe01622: Waiting
> >
> > 071f37eca411: Waiting
> >
> > dc33933d1e9b: Waiting
> >
> > cc3a1fce1c35: Waiting
> >
> > ab292f5d0d16: Waiting
> >
> > 9cd00aac030f: Waiting
> >
> >
> >
> >
> >
> > 3 min
> >
> > root@obrienondemand20180430:/var/lib/waagent/custom-
> > script/download/0#
> > docker pull nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> >
> > 1.1.4: Pulling from onap/dmaap/dmaap-mr
> >
> > 0c5a750448f5: Pull complete
> >
> > e2356a247318: Pull complete
> >
> > 12f105c650c3: Pull complete
> >
> > 46d4cec7ab72: Pull complete
> >
> > f5b0369aa7fc: Pull complete
> >
> > a93519a09c8b: Pull complete
> >
> > 73ffcbe01622: Pull complete
> >
> > 071f37eca411: Pull complete
> >
> > dc33933d1e9b: Pull complete
> >
> > cc3a1fce1c35: Pull complete
> >
> > ab292f5d0d16: Pull complete
> >
> > 9cd00aac030f: Pull complete
> >
> > Digest:
> > sha256:8dff567ab978965f545fc1cadc8060cd34a2599ba586e786795469b32fc670ff
> >
> > Status: Downloaded newer image for
> > nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> >
> > testing full predeploy - started 1148
> >
> > 1149
> >
> > ubuntu@obrienondemand20180430:~$ sudo ps -ef | grep docker | grep
> > pull
> > | wc -l
> >
> > 77
> >
> > 10 sec below
> >
> > 32eda82f66ec: Downloading [>
> > ] 96.86 MB/298.4 MB
> >
> > 32eda82f66ec: Downloading [>
> > ]   124 MB/298.4 MB
> >
> > 1153
> >
> > ubuntu@obrienondemand20180430:~$ sudo ps -ef | grep docker | grep
> > pull
> > | wc -l
> >
> > 75
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > 



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

[onap-discuss] [ONAP Helpdesk #54020] [LF] JIRA rendering issues, nexus3 slowdown

[Jessica Wagantall via RT]

Closing this ticket and replying on RT54849

Ryan is helping us adjusting the GC tasks so that they wont slow down our 
performance
as well as adjusting the heap sizes. 

Thanks!
Jess

On Fri Mar 23 13:24:44 2018, frank.obr...@amdocs.com wrote:
> LF.
>Hi, the usual slowdown in nexus (we are bringing in a local nexus3
> cache as a workaround)
>Talking with Microsoft this morning - they reminded me of burst
> instances.
>I use T2 instances for some of my personal VM's - these get credits
> equal to about 1 hour/day of full CPU capability then run slower other
> times.  Are you using instances that have a sliding performance scale.
> Just a question as I don't know your clustering setup for nexus3
> 
> Another issue, Jira has been having problems rendering today - mobile
> mode works fine, but desktop mode on 2 different browsers and a phone
> took 10 min to render around 1300 EDT today
> 
> Fixed now
> 
> Michael O'Brien
> Amdocs Technology
> 16135955268
> 55268
> [amdocs-a]
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at least 10x slower at 1MB/sec

[Jessica Wagantall via RT]

Actually, I think this is the latest ticket on this issue, 

I will leave this opened and continue our investigation here and close other 
instances
of the same issue. 

Thanks!
Jess

On Tue May 01 12:59:52 2018, jwagantall wrote:
> Dear Michael and Gildas,
> 
> After our meeting yesterday with Mo, I spoke yesterday to Ryan and
> asked him if he could please
>  be able to look into the GC task that seems to be causing some of
> these issues and
> to also look at the heap and memory sizes to make sure we are able to
> use the
>  resources we have more efficiently.
> 
> I will close this ticket for now since there are many instances of the
> same problem and just
>  leave the latest topic opened so that we can put all our comments
> there.
> 
> Thanks!
> Jess
> 
> On Mon Apr 16 14:02:53 2018, frank.obr...@amdocs.com wrote:
> > LF,
> >Hi, there seems to be an issue since last Thursday where
> > nexus3.onap.org:10001 is severely throttled.
> >On my azure/aws instances I am getting around 1 MB/sec where
> > previously I could download at least 10 streams at about 10+ MB/sec
> > before wed.
> >https://git.onap.org/oom/tree/kubernetes/config/prepull_docker.sh
> >
> > To reproduce run the above script on an oom deployment.
> > Tracking this issue in OOM-942 and its' linked jiras
> > https://jira.onap.org/browse/OOM-942
> > These stats for example ( a byproduct of how the script runs) are 10
> > sec apart and show the actual speed for a single remaining pull.
> >
> > a244880be6ed: Downloading [>
> > ] 2.639 MB/160.9 MB
> > a244880be6ed: Downloading [=>
> > ] 3.688 MB/160.9 MB
> > a244880be6ed: Downloading [=>
> > ] 5.796 MB/160.9 MB
> > a244880be6ed: Downloading [==>
> > ] 7.908 MB/160.9 MB
> > a244880be6ed: Downloading [==>
> > ] 9.487 MB/160.9 MB
> > a244880be6ed: Downloading [===>
> > ] 11.07 MB/160.9 MB
> > a244880be6ed: Downloading [>
> > ] 13.71 MB/160.9 MB
> > a244880be6ed: Downloading [=>
> > ] 16.34 MB/160.9 MB
> > a244880be6ed: Downloading [=>
> > ] 18.45 MB/160.9 MB
> > a244880be6ed: Downloading [==>
> > ] 20.56 MB/160.9 MB
> > a244880be6ed: Downloading [==>
> > ] 21.61 MB/160.9 MB
> > a244880be6ed: Downloading [>
> > ] 26.36 MB/160.9 MB
> > a244880be6ed: Downloading [>
> > ] 27.94 MB/160.9 MB
> > a244880be6ed: Downloading [=>
> > ] 31.63 MB/160.9 MB
> > a244880be6ed: Downloading [==>
> > ]  34.8 MB/160.9 MB
> > a244880be6ed: Downloading [===>
> > ] 35.85 MB/160.9 MB
> > waiting for last pull
> >
> >
> >
> > Michael O'Brien
> > Amdocs Technology
> > 16135955268
> > 55268
> > [amdocs-a]
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > 



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

[onap-discuss] [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at least 10x slower at 1MB/sec

[Jessica Wagantall via RT]

Dear Michael and Gildas, 

After our meeting yesterday with Mo, I spoke yesterday to Ryan and asked him if 
he could please
be able to look into the GC task that seems to be causing some of these issues 
and 
to also look at the heap and memory sizes to make sure we are able to use the
resources we have more efficiently. 

I will close this ticket for now since there are many instances of the same 
problem and just
leave the latest topic opened so that we can put all our comments there. 

Thanks!
Jess

On Mon Apr 16 14:02:53 2018, frank.obr...@amdocs.com wrote:
> LF,
>Hi, there seems to be an issue since last Thursday where
> nexus3.onap.org:10001 is severely throttled.
>On my azure/aws instances I am getting around 1 MB/sec where
> previously I could download at least 10 streams at about 10+ MB/sec
> before wed.
>https://git.onap.org/oom/tree/kubernetes/config/prepull_docker.sh
> 
> To reproduce run the above script on an oom deployment.
> Tracking this issue in OOM-942 and its' linked jiras
> https://jira.onap.org/browse/OOM-942
> These stats for example ( a byproduct of how the script runs) are 10
> sec apart and show the actual speed for a single remaining pull.
> 
> a244880be6ed: Downloading [>
> ] 2.639 MB/160.9 MB
> a244880be6ed: Downloading [=>
> ] 3.688 MB/160.9 MB
> a244880be6ed: Downloading [=>
> ] 5.796 MB/160.9 MB
> a244880be6ed: Downloading [==>
> ] 7.908 MB/160.9 MB
> a244880be6ed: Downloading [==>
> ] 9.487 MB/160.9 MB
> a244880be6ed: Downloading [===>
> ] 11.07 MB/160.9 MB
> a244880be6ed: Downloading [>
> ] 13.71 MB/160.9 MB
> a244880be6ed: Downloading [=>
> ] 16.34 MB/160.9 MB
> a244880be6ed: Downloading [=>
> ] 18.45 MB/160.9 MB
> a244880be6ed: Downloading [==>
> ] 20.56 MB/160.9 MB
> a244880be6ed: Downloading [==>
> ] 21.61 MB/160.9 MB
> a244880be6ed: Downloading [>
> ] 26.36 MB/160.9 MB
> a244880be6ed: Downloading [>
> ] 27.94 MB/160.9 MB
> a244880be6ed: Downloading [=>
> ] 31.63 MB/160.9 MB
> a244880be6ed: Downloading [==>
> ]  34.8 MB/160.9 MB
> a244880be6ed: Downloading [===>
> ] 35.85 MB/160.9 MB
> waiting for last pull
> 
> 
> 
> Michael O'Brien
> Amdocs Technology
> 16135955268
> 55268
> [amdocs-a]
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #55415] nexus3 slowdown (burst/pause) behavior - propose 2nd LF meeting

[Jessica Wagantall via RT]

+ Mo

Dear Michael, 

I did noticed once last week a pull that failed for me immediately for no 
reason and had to restart.

Mo, do you think you can join us for a quick debugging session some time today 
please?

Thanks a ton!
Jess



On Mon Apr 30 11:56:28 2018, frank.obr...@amdocs.com wrote:
> LF,
>Hi, we have been seeing burst behavior for the last week. This
> morning in the integration lab session we see this on multiple
> machines.
>Downloads are fast when they are running - but completely stall
> every min or so for 30-60 sec.
> 
> For example pulling the dmaap container manually - a single pull took
> 3 min on one system - 18 on antoher and had sections where the job ran
> about 1 to 5 with bursts to 25 Mb/sec (max is usually 10Mb/sec per
> stream - up to 5 in parallel - I have seen 25) - but there were times
> 30-60 sec where the image download completely paused at 0Mb/sec.
> 
> This behavior is different or is in combination with the traditional
> slowdown we used to see  - very slow pulls - this issue is new in that
> it works fine during the burst - but has sections where all pulls
> pause.  To be frank - I did see this pause behavior briefly for a
> couple seconds back even in Dec.
> 
> 
> I propose we meet again to test downloads again and get some
> volumetrics.
> Some details on this and previous issues in
> 
> https://jira.onap.org/browse/OOM-933
> 
> Time 1130 EST 20180430
> 
> see slowdown again after our last meeting - a burst behaviour
> (burst/hold in 30-60 sec intervals)
> 
> This in an azure system (clean) running a manual docker download - see
> attachment on OOM-716
> 
> root@obrienondemand20180430:/var/lib/waagent/custom-script/download/0#
> history
> 
> 1  cd /var/lib/waagent/custom-script/download/0/
> 
> 2  ls
> 
> 3  tail -f stdout
> 
> 4  wget
> https://jira.onap.org/secure/attachment/11444/prepull_docker_master.sh
> 
> 6  sudo chmod 777 prepull_docker_master.sh
> 
> 7  vi prepull_docker_master.sh
> 
> 8  docker login -u docker -p docker nexus3.onap.org:10001
> 
> 9  docker pull nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> 
> 10  vi prepull_docker_master.sh
> 
> 11  docker pull nexus3.onap.org:10001/onap/vid:1.2.1
> 
> 12  docker pull nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> 
> 
> 
> 
> 
> root@obrienondemand20180430:/var/lib/waagent/custom-script/download/0#
> docker pull nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> 
> 1.1.4: Pulling from onap/dmaap/dmaap-mr
> 
> 0c5a750448f5: Pull complete
> 
> e2356a247318: Pull complete
> 
> 12f105c650c3: Pull complete
> 
> 46d4cec7ab72: Pull complete
> 
> f5b0369aa7fc: Pull complete
> 
> a93519a09c8b: Pull complete
> 
> 73ffcbe01622: Waiting
> 
> 071f37eca411: Waiting
> 
> dc33933d1e9b: Waiting
> 
> cc3a1fce1c35: Waiting
> 
> ab292f5d0d16: Waiting
> 
> 9cd00aac030f: Waiting
> 
> 
> 
> 
> 
> 3 min
> 
> root@obrienondemand20180430:/var/lib/waagent/custom-script/download/0#
> docker pull nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> 
> 1.1.4: Pulling from onap/dmaap/dmaap-mr
> 
> 0c5a750448f5: Pull complete
> 
> e2356a247318: Pull complete
> 
> 12f105c650c3: Pull complete
> 
> 46d4cec7ab72: Pull complete
> 
> f5b0369aa7fc: Pull complete
> 
> a93519a09c8b: Pull complete
> 
> 73ffcbe01622: Pull complete
> 
> 071f37eca411: Pull complete
> 
> dc33933d1e9b: Pull complete
> 
> cc3a1fce1c35: Pull complete
> 
> ab292f5d0d16: Pull complete
> 
> 9cd00aac030f: Pull complete
> 
> Digest:
> sha256:8dff567ab978965f545fc1cadc8060cd34a2599ba586e786795469b32fc670ff
> 
> Status: Downloaded newer image for
> nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4
> 
> testing full predeploy - started 1148
> 
> 1149
> 
> ubuntu@obrienondemand20180430:~$ sudo ps -ef | grep docker | grep pull
> | wc -l
> 
> 77
> 
> 10 sec below
> 
> 32eda82f66ec: Downloading [>
> ] 96.86 MB/298.4 MB
> 
> 32eda82f66ec: Downloading [>
> ]   124 MB/298.4 MB
> 
> 1153
> 
> ubuntu@obrienondemand20180430:~$ sudo ps -ef | grep docker | grep pull
> | wc -l
> 
> 75
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #55374] [critical] Nexus3 config change breaks CD builds until 30+ snapshot are released by PTLs

[Jessica Wagantall via RT]

xus3.onap.org:10001/onap/sdc-elasticsearch:1.2-STAGING-latest"
> Normal   Pulling 32m (x13 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/sdc-cassandra:1.2-STAGING-latest"
> Normal   Pulling 26m (x12 over 6h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/testsuite:1.2-STAGING-latest"
> Normal   Pulling 6m (x14 over 7h)  kubelet, ip-10-0-0-206.us-east-
> 2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/refrepo/postgres:latest"
> Normal   Pulling 15m (x14 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/portal-db:2.1-STAGING-latest"
> Normal   Pulling 21m (x14 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/music/cassandra_music:latest"
> Normal   Pulling 3m (x12 over 6h)  kubelet, ip-10-0-0-206.us-east-
> 2.compute.internal  pulling image "nexus3.onap.org:10001/onap/policy-
> pe:1.2-STAGING-latest"
> Normal   Pulling 9m (x13 over 7h)   kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/multicloud/openstack-windriver:latest"
> Normal   Pulling 10m (x13 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/multicloud/vio:latest"
> Normal   Pulling 17m (x13 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/multicloud/openstack-ocata:latest"
> Normal   Pulling 20m (x13 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/multicloud/framework:latest"
> Normal   Pulling 13m (x12 over 6h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/msb/msb_discovery:1.1.0-SNAPSHOT-latest"
> Normal   Pulling 14m (x12 over 6h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/policy-drools:1.2-STAGING-latest"
> Normal   Pulling 6m (x10 over 5h)  kubelet, ip-10-0-0-206.us-east-
> 2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.1.4"
> Normal   Pulling 20m (x14 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/org.onap.dcaegen2.deployments.redis-
> cluster-container:1.0.0"
> Normal   Pulling 22m (x14 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/org.onap.dcaegen2.deployments.healthcheck-
> container:1.0.0"
> Normal   Pulling 1m (x14 over 7h)  kubelet, ip-10-0-0-206.us-east-
> 2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/org.onap.dcaegen2.deployments.cm-
> container:1.3.0"
> Normal   Pulling 14m (x14 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/consul:1.0.6"
> Normal   Pulling 18m (x14 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/consul:1.0.0"
> Normal   Pulling 10m (x13 over 6h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/clamp"
> dev-appc-dgbuilder-67579b8578-mmqfk - duplicate of sdnc
> Normal   Pulling 12m (x14 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/appc-cdt-image:1.3.0-SNAPSHOT-latest"
> Normal   Pulling 21m (x9 over 5h)  kubelet, ip-10-0-0-206.us-east-
> 2.compute.internal  pulling image "nexus3.onap.org:10001/onap/appc-
> image:1.3.0-SNAPSHOT-latest"
> Normal   Pulling 27m (x13 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/search-data-service:1.2-STAGING-latest"
> Normal   Pulling 31m (x12 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/aai-resources:1.2-STAGING-latest"
> Normal   Pulling 29m (x13 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/model-loader:1.2-STAGING-latest"
> Normal   Pulling 22m (x13 over 7h)  kubelet, ip-10-0-0-206.us-
> east-2.compute.internal  pulling image
> "nexus3.onap.org:10001/onap/gizmo:1.1-STAGING-latest"
> Normal   Pulling 35m (x13 over 7h)  kubelet, ip-10-0-0-206.us-
> east-

[onap-discuss] [ONAP Helpdesk #55359] RE: Nexus3 docker.public configuration changed.

[Jessica Wagantall via RT]

+ Gildas. 

On Fri Apr 27 22:59:55 2018, jwagantall wrote:
> Dear Michael,
> 
> This is going to be an effect for jobs using the dependencies.
> We need to make sure SDC makes a release of their binaries so we can
> move our dependencies
> to the released version of them.
> 
> The image you are trying to fetch just exists in Snapshot and we need
> SDC team to request a release
> (which will be released as onap/sdc/sdc-workflow-designer:1.1.0)
> for it: https://nexus3.onap.org/#browse/search=keyword%3Dsdc-workflow-
> designer:c60bc6b9612f47d36fd6ad66a8830cf2
> 
> Also, btw, fixing this tag too to match
> https://jira.onap.org/browse/CIMAN-132.
> 
> Please let me know if this helps explaining.
> Thanks!
> Jess
> 
> On Fri Apr 27 20:51:37 2018, frank.obr...@amdocs.com wrote:
> > Team, LF,
> >Seeing issues as of 1400EDT where a major portion (about 35-50 of
> > the 107 total) of the docker container images are failing to resolve
> > Started around midday 20180427 after the slowdown that was occurring
> > earlier in the day.
> > 35 on both AWS systems as of a couple hours ago
> > 50 on a slower internal system
> > http://jenkins.onap.info/job/oom-cd-master2-aws/27/console
> > http://jenkins.onap.info/job/oom-cd-master/2789/console
> > ubuntu@ip-10-0-0-144:~$ kubectl get pods --all-namespaces | grep
> > Image
> > onap  dev-aaf-84dbb784f-62xrj0/1
> > ImagePullBackOff0  41m
> > onap  dev-aai-babel-79d9cc58fb-98blr 0/1
> > ImagePullBackOff0  41m
> > onap  dev-aai-data-router-cb4cf6b79-rr5sn0/1
> > ImagePullBackOff0  41m
> > onap  dev-aai-gizmo-657cb8556c-blbcc 1/2
> > ErrImagePull0  41m
> > onap  dev-aai-search-data-8686bbd58c-tx84s   1/2
> > ErrImagePull0  41m
> > onap  dev-appc-cdt-747fb47876-dffnw  0/1
> > ImagePullBackOff0  41m
> > onap  dev-clamp-9dbb4686d-jwvcz  0/1
> > ImagePullBackOff0  41m
> > onap  dev-consul-b5d9d5564-c72jq 0/1
> > ImagePullBackOff0  40m
> > onap  dev-consul-server-8f8f8767-hwfgk   0/1
> > ImagePullBackOff0  40m
> > onap  dev-dcae-cloudify-manager-d8748c658-gt7xd  0/1
> > ImagePullBackOff0  40m
> > onap  dev-dcae-healthcheck-67f5dfc95-qf5sx   0/1
> > ImagePullBackOff0  40m
> > onap  dev-dcae-redis-0   0/1
> > ImagePullBackOff0  41m
> > onap  dev-multicloud-5d4648c6c5-lmgrm1/2
> > ErrImagePull0  40m
> > onap  dev-multicloud-ocata-6465ddf889-dsnw6  1/2
> > ErrImagePull0  40m
> > onap  dev-multicloud-windriver-8579976b7c-r6qgz  1/2
> > ErrImagePull0  40m
> > onap  dev-portal-cassandra-5f477975d4-h6rbt  0/1
> > ErrImagePull0  40m
> > onap  dev-portal-db-745747866f-jh7gn 0/1
> > ImagePullBackOff0  40m
> > onap  dev-postgres-config-44fxk  0/1
> > ErrImagePull0  41m
> > onap  dev-robot-5fc4c7846b-b52g4 0/1
> > ImagePullBackOff0  40m
> > onap  dev-sdc-cs-64f45d77dc-85rhg0/1
> > ImagePullBackOff0  40m
> > onap  dev-sdc-es-5d7789-27b4b0/1
> > ErrImagePull0  40m
> > onap  dev-sdc-wfd-5b5d4f58f6-4xg86   0/1
> > ImagePullBackOff0  40m
> > onap  dev-sms-857f6dbd87-9g87d   0/1
> > ErrImagePull0  41m
> > onap  dev-smsdb-00/2
> > ErrImagePull0  41m
> > onap  dev-vfc-catalog-7d89bc8b9d-5rdx2   1/2
> > ErrImagePull0  40m
> > onap  dev-vfc-ems-driver-864685477c-fnthh0/1
> > ImagePullBackOff0  40m
> > onap  dev-vfc-multivim-proxy-767757dfd8-ntzkb0/1
> > ImagePullBackOff0  40m
> > onap  dev-vfc-nokia-v2vnfm-driver-7fbc7dd6d6-vrf85   0/1
> > ErrImagePull0  40m
> > onap  dev-vfc-nokia-vnfm-driver-5f9c777fd8-k22hq 1/2
> > ErrImagePull0  40m
> > onap  dev-vfc-nslcm-76fd6648cc-gk64s 1/2
> > ErrImagePull0  40m
> > onap  dev-vfc-workflow-78f6466f9d-th8zf  0/1
> > ImagePullBackOff0  40m
> > onap  dev-vfc-workflow-engine-79769874c7-5q5df   0/1
> > ImagePullBackOff0  40m
> > onap  dev-vfc-zte-sdnc-driver-5b6c7cbd6b-2wnj8   0/1
> > ImagePullBackOff0  40m
> > onap  sniro-emulator-7fc8658bcb-zst6d0/1
> > ImagePullBackOff0  

[onap-discuss] [ONAP Helpdesk #55359] RE: Nexus3 docker.public configuration changed.

[Jessica Wagantall via RT]

Dear Michael, 

This is going to be an effect for jobs using the dependencies. 
We need to make sure SDC makes a release of their binaries so we can move our 
dependencies 
to the released version of them. 

The image you are trying to fetch just exists in Snapshot and we need SDC team 
to request a release 
(which will be released as onap/sdc/sdc-workflow-designer:1.1.0)
for it: 
https://nexus3.onap.org/#browse/search=keyword%3Dsdc-workflow-designer:c60bc6b9612f47d36fd6ad66a8830cf2

Also, btw, fixing this tag too to match https://jira.onap.org/browse/CIMAN-132. 

Please let me know if this helps explaining.
Thanks!
Jess

On Fri Apr 27 20:51:37 2018, frank.obr...@amdocs.com wrote:
> Team, LF,
>Seeing issues as of 1400EDT where a major portion (about 35-50 of
> the 107 total) of the docker container images are failing to resolve
> Started around midday 20180427 after the slowdown that was occurring
> earlier in the day.
> 35 on both AWS systems as of a couple hours ago
> 50 on a slower internal system
> http://jenkins.onap.info/job/oom-cd-master2-aws/27/console
> http://jenkins.onap.info/job/oom-cd-master/2789/console
> ubuntu@ip-10-0-0-144:~$ kubectl get pods --all-namespaces | grep Image
> onap  dev-aaf-84dbb784f-62xrj0/1
> ImagePullBackOff0  41m
> onap  dev-aai-babel-79d9cc58fb-98blr 0/1
> ImagePullBackOff0  41m
> onap  dev-aai-data-router-cb4cf6b79-rr5sn0/1
> ImagePullBackOff0  41m
> onap  dev-aai-gizmo-657cb8556c-blbcc 1/2
> ErrImagePull0  41m
> onap  dev-aai-search-data-8686bbd58c-tx84s   1/2
> ErrImagePull0  41m
> onap  dev-appc-cdt-747fb47876-dffnw  0/1
> ImagePullBackOff0  41m
> onap  dev-clamp-9dbb4686d-jwvcz  0/1
> ImagePullBackOff0  41m
> onap  dev-consul-b5d9d5564-c72jq 0/1
> ImagePullBackOff0  40m
> onap  dev-consul-server-8f8f8767-hwfgk   0/1
> ImagePullBackOff0  40m
> onap  dev-dcae-cloudify-manager-d8748c658-gt7xd  0/1
> ImagePullBackOff0  40m
> onap  dev-dcae-healthcheck-67f5dfc95-qf5sx   0/1
> ImagePullBackOff0  40m
> onap  dev-dcae-redis-0   0/1
> ImagePullBackOff0  41m
> onap  dev-multicloud-5d4648c6c5-lmgrm1/2
> ErrImagePull0  40m
> onap  dev-multicloud-ocata-6465ddf889-dsnw6  1/2
> ErrImagePull0  40m
> onap  dev-multicloud-windriver-8579976b7c-r6qgz  1/2
> ErrImagePull0  40m
> onap  dev-portal-cassandra-5f477975d4-h6rbt  0/1
> ErrImagePull0  40m
> onap  dev-portal-db-745747866f-jh7gn 0/1
> ImagePullBackOff0  40m
> onap  dev-postgres-config-44fxk  0/1
> ErrImagePull0  41m
> onap  dev-robot-5fc4c7846b-b52g4 0/1
> ImagePullBackOff0  40m
> onap  dev-sdc-cs-64f45d77dc-85rhg0/1
> ImagePullBackOff0  40m
> onap  dev-sdc-es-5d7789-27b4b0/1
> ErrImagePull0  40m
> onap  dev-sdc-wfd-5b5d4f58f6-4xg86   0/1
> ImagePullBackOff0  40m
> onap  dev-sms-857f6dbd87-9g87d   0/1
> ErrImagePull0  41m
> onap  dev-smsdb-00/2
> ErrImagePull0  41m
> onap  dev-vfc-catalog-7d89bc8b9d-5rdx2   1/2
> ErrImagePull0  40m
> onap  dev-vfc-ems-driver-864685477c-fnthh0/1
> ImagePullBackOff0  40m
> onap  dev-vfc-multivim-proxy-767757dfd8-ntzkb0/1
> ImagePullBackOff0  40m
> onap  dev-vfc-nokia-v2vnfm-driver-7fbc7dd6d6-vrf85   0/1
> ErrImagePull0  40m
> onap  dev-vfc-nokia-vnfm-driver-5f9c777fd8-k22hq 1/2
> ErrImagePull0  40m
> onap  dev-vfc-nslcm-76fd6648cc-gk64s 1/2
> ErrImagePull0  40m
> onap  dev-vfc-workflow-78f6466f9d-th8zf  0/1
> ImagePullBackOff0  40m
> onap  dev-vfc-workflow-engine-79769874c7-5q5df   0/1
> ImagePullBackOff0  40m
> onap  dev-vfc-zte-sdnc-driver-5b6c7cbd6b-2wnj8   0/1
> ImagePullBackOff0  40m
> onap  sniro-emulator-7fc8658bcb-zst6d0/1
> ImagePullBackOff0  40m
> 
> 
> Warning  Failed  24s (x11 over 5h)  kubelet, beijing-oom  Failed
> to pull image "nexus3.onap.org:10001/onap/sdc/sdc-workflow-
> designer:1.1.0-SNAPSHOT-STAGING-latest": rpc error: code = Unknown
> desc = Error: image 

[onap-discuss] [ONAP Helpdesk #55152] [CCSDK] ccsdk-dgbuilder-image had no 0.2.1-SNAPSHOT until 20 April

[Jessica Wagantall via RT]

Dear Michael,

I wonder if this was a case of an old Snapshot that got removed by our
cleanup tasks. 
We have a daily task that cleans up any old Snapshots older than 16 days. 

This is the job that re-created this binary:
https://jenkins.onap.org/view/ccsdk/job/ccsdk-distribution-master-docker-java-daily/308/console

Do you think this was the case?

Thanks!
Jess

On Tue Apr 24 17:18:52 2018, frank.obr...@amdocs.com wrote:
> LF,
>   Just would like to understand what happened to this image that broke
> SDNC and APPC for a couple days
> 
> https://jira.onap.org/browse/SDNC-285
> https://jira.onap.org/browse/APPC-856
> 
> From the logs it looks like the SNAPSHOT image was returned 4 days ago
> - before the 20th of April the dockers failed to pull.
> https://nexus3.onap.org/#browse/browse:docker.snapshot:v2%2Fonap%2Fccsdk-
> dgbuilder-image%2Fmanifests%2F0.2.1-SNAPSHOT
> 
> Blob created
> 
> Fri Apr 20 2018 09:11:26 GMT-0400 (Eastern Daylight Time)
> 
> Blob updated
> 
> Tue Apr 24 2018 09:27:11 GMT-0400 (Eastern Daylight Time)
> 
> 
> When these images disappear for a while - the pods fail to come up.
> 
> 
> 
> Thank you
> /michael
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #54954] Jenkins Job queue is stuck

[Jessica Wagantall via RT]

Things look stable now. 

We will continue monitoring the state of these nodes to prevent builds being 
stuck. 

thanks!
Jess

On Thu Apr 19 09:30:17 2018, jeremyphelps wrote:
> Hi All,
> I am looking into this now, I suspect we have some orphaned VMs that
> are clogging things up.  I'm going to pause the Jenkins while I
> investigate.
> Jeremy
> 
> On Thu Apr 19 09:27:18 2018, bf1...@att.com wrote:
> > 246 in the build Queue ?
> >
> > Brian
> >
> >
> > From: onap-discuss-boun...@lists.onap.org  > boun...@lists.onap.org> On Behalf Of DRAGOSH, PAM
> > Sent: Thursday, April 19, 2018 8:16 AM
> > To: Jessica Wagantall via RT <onap-helpd...@rt.linuxfoundation.org>
> > Cc: onap-discuss@lists.onap.org
> > Subject: [onap-discuss] Jenkins Job queue is stuck
> >
> > ***Security Advisory: This Message Originated Outside of AT ***
> > Reference http://cso.att.com/EmailSecurity/IDSP.html for more
> > information.
> > Can someone look into it?
> >
> > Thanks,
> >
> > Pam



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

[onap-discuss] [ONAP Helpdesk #54972] [integration] Increase number of Jenkins minions

[Jessica Wagantall via RT]

Dear Gary, 

Jeremy has increased the number now. 
We are checking why is it taking so long for the node to be terminated after a 
build finishes.

Looking into those issues now
Thanks!
Jess

On Thu Apr 19 12:08:56 2018, gary.i...@huawei.com wrote:
> Hi Helpdesk,
> 
> Can we bump up the number of Jenkins minions?  Currently the demand
> seems to be outstripping the supply; we've been having 100+ backlog
> jobs for a while.
> 
> Thanks,
> Gary



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

[onap-discuss] [ONAP Helpdesk #54973] Issue with the build process

[Jessica Wagantall via RT]

Dear Seshu, 

Jeremy has increased the number of nodes now and hopefully it will help 
unclogging
jobs faster. 

Thanks a ton!
Jess 

On Thu Apr 19 12:20:39 2018, seshu.kuma...@huawei.com wrote:
> Dear LF
> 
> The current jenkins capacity seems insufficient to handle the build
> jobs.
> Could we please increase this to make it more productive.
> 
> 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] [ONAP Helpdesk #54694] Jira down - confluence up - EOM

[Jessica Wagantall via RT]

Possibly a network glitch. 

Looks stable now

Thanks!
Jess

On Thu Apr 12 08:21:18 2018, frank.obr...@amdocs.com wrote:
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #53498] Nexus3 throttled today around noon - 3 hour pull on Azure eastus/westus2 instead of 20-40 min

[Jessica Wagantall via RT]

Dear Michael, 

I wonder if these slow downs are related to the amount of activity on a Monday 
compared to the weekend. 

Let me keep an eye on these slow times for now. 

Thanks a ton
Jess

On Mon Mar 12 13:44:27 2018, frank.obr...@amdocs.com wrote:
> LF,
>   Hi, I am testing oneclick installs of ONAP about 15 times a day -
> yesterday nexus3 was operating normally - 20-40 min for all 95 docker
> images.  Today around noon for a couple hours nexus slowed to a crawl
> where a single image pull took over 15 min.
>   I just switched to westus2 and thought it might be their gateway -
> but I see this on the faster/verified eastus.
> 
> Upping the timeout on the prepull script from 3000 sec to 8000
> 
> https://jira.onap.org/browse/OOM-328
> e8e2e3cc: Retrying in 3 seconds
> e8e2e3cc: Retrying in 2 seconds
> 0eb1db346111: Pull complete
> e8e2e3cc: Retrying in 1 second
> waiting for last pull - 81 left
> e8e2e3cc: Retrying in 10 seconds
> e8e2e3cc: Retrying in 9 seconds
> e8e2e3cc: Retrying in 8 seconds
> e8e2e3cc: Retrying in 7 seconds
> e8e2e3cc: Retrying in 6 seconds
> e8e2e3cc: Retrying in 5 seconds
> e8e2e3cc: Retrying in 4 seconds
> 
> two different azure DCs westus2, eastus experiencing the issue
> 
> Michael O'Brien
> Amdocs Technology
> 16135955268
> 55268
> [amdocs-a]
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

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

[Jessica Wagantall via RT]

This seemed to be a possible issue with network throttling.

For some reason the nodes where not getting properly assigned and removed once 
the 
Jenkins job was completed. 

Andy was helping us adding the node instances slowly back into Jenkins in 
smaller increments and
monitoring that they were acting properly. 

Thanks!
Jess

On Thu Mar 08 12:47:50 2018, gary.i...@huawei.com wrote:
> 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

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

[Jessica Wagantall via RT]

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

[onap-discuss] [ONAP Helpdesk #53326] Jenkins slaves offline

[Jessica Wagantall via RT]

Fixed and the queue is now in good state. 


On Wed Mar 07 14:03:31 2018, jwagantall wrote:
> Dear Denes, 
> 
> I am still looking into these issues. 
> Sorry for the delays. 
> 
> Thanks!
> Jess
> 
> 
> On Wed Mar 07 09:20:48 2018, denes.nem...@nokia.com wrote:
> > Hi
> > 
> > Most of the Jenkins slaves went offline. Does anyone know what to do?
> > 
> > D.
> 
> 



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

[onap-discuss] [ONAP Helpdesk #53326] Jenkins slaves offline

[Jessica Wagantall via RT]

Dear Denes, 

I am still looking into these issues. 
Sorry for the delays. 

Thanks!
Jess


On Wed Mar 07 09:20:48 2018, denes.nem...@nokia.com wrote:
> Hi
> 
> Most of the Jenkins slaves went offline. Does anyone know what to do?
> 
> D.



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

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

[Jessica Wagantall via RT]

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

[onap-discuss] [ONAP Helpdesk #52451] [integration] Jenkins backlog

[Jessica Wagantall via RT]

Thanks for pointing it out Gary, I noticed that too actually

I am not sure what caused this but it took Jenkins quite a few minutes to start 
picking builds. 

Looks like it is ramping up now. 

Thanks!
Jess

On Wed Feb 14 14:45:48 2018, gary.i...@huawei.com wrote:
> Hi helpdesk,
> 
> ONAP Jenkins has a huge backlog but very few jobs are getting
> executed.  Can you take a look?
> 
> Thanks,
> Gary



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

[onap-discuss] [ONAP Helpdesk #52163] RE: ONAP-HELPDESK - so-libs-master-stage-site-java jenkins job is failing

[Jessica Wagantall via RT]

Hi, 

I was only able to release 
https://jenkins.onap.org/view/cli/job/cli-master-merge-java/329/ for now. 

For https://jenkins.onap.org/view/cli/job/cli-amsterdam-merge-java/1/, this is 
an artifact from Dec8th, which is no longer in existence in Nexus. Staging 
repositories only are kept for 14 days. Do we have a better candidate?

Also, for the swagger releases, I need a confirmation from the PTL of the 
project. 

Thanks a ton
Jess

On Wed Feb 14 06:49:33 2018, kanagaraj.manic...@huawei.com wrote:
> Dear Jess,
> Pls use following links:
> 
> CLI:
> https://jenkins.onap.org/view/cli/job/cli-amsterdam-merge-java/1/
> https://jenkins.onap.org/view/cli/job/cli-master-merge-java/329/
> 
> Swagger-SDK:
> 
> https://jenkins.onap.org/view/msb/job/msb-swagger-sdk-master-merge-
> java/12/
> https://jenkins.onap.org/view/msb/job/msb-swagger-sdk-amsterdam-merge-
> java/1/
> 
> 
> 
> Regards
> Kanagaraj M
> -
> Be transparent! Win together !!
> 
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> This e-mail and its attachments contain confidential information from
> HUAWEI, which is intended only for the person  or entity whose address
> is listed above. Any use of the information contained herein in any
> way (including, but not   limited to, total or partial disclosure,
> reproduction, or dissemination) by persons other than the intended
> recipient(s) is  prohibited. If you receive this e-mail in error,
> please notify the sender by phone or email immediately and delete it!
> 
> 
> 
> -Original Message-
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-
> boun...@lists.onap.org] On Behalf Of Jessica Wagantall via RT
> Sent: Wednesday, February 14, 2018 1:34 PM
> To: Subhash Kumar Singh
> Cc: onap-discuss@lists.onap.org
> Subject: [onap-discuss] [ONAP Helpdesk #52163] RE: ONAP-HELPDESK - so-
> libs-master-stage-site-java jenkins job is failing
> 
> Dear Kanagaraj,
> 
> Sure, I can help moving binaries into the release repository,
> 
> Although, just for confirmation purposes, I will need you to provide
> me with the link of the Jenkins job you need me to release.
> 
> Can you please select a candidate?
> 
> Thanks!
> Jess
> 
> On Tue Feb 13 00:18:49 2018, kanagaraj.manic...@huawei.com wrote:
> > Dear LF,
> >
> > Could you please help to fix the site jobs for CLI, which is failing
> > for a quite a while.
> >
> > in order to fix this issue , Pls release CLI jars from latest commit
> > in both Amsterdam and master branch, if LF is not planning to run the
> > site jobs from the snapshot.
> >
> > Thank you.
> >
> > Regards
> > Kanagaraj M
> > -
> > Be transparent! Win together !!
> >
> > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复
> > 制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> >  This e-mail and its attachments contain confidential information
> > from
> >  HUAWEI, which is intended only for the person  or entity whose
> > address
> >  is listed above. Any use of the information contained herein in any
> >  way (including, but not   limited to, total or partial disclosure,
> > reproduction, or dissemination) by persons other than the intended
> >  recipient(s) is  prohibited. If you receive this e-mail in error,
> > please notify the sender by phone or email immediately and delete it!
> >
> >
> >
> > -Original Message-
> >  From: Kanagaraj Manickam
> > Sent: Monday, February 12, 2018 2:16 PM
> > To: onap-helpd...@rt.linuxfoundation.org
> > Cc: Gildas Lanilis
> >  Subject: RE: [onap-discuss] [ONAP Helpdesk #52163] snapshot vs
> > release
> > repo
> >
> > Dear LF team,
> >
> > Could you please help to find the resolution for the below mentioned
> > issue. Thank you.
> >
> >
> > Regards
> > Kanagaraj M
> > -
> > Be transparent! Win together !!
> >
> > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复
> > 制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> >  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  prohibit

[onap-discuss] [ONAP Helpdesk #52163] RE: ONAP-HELPDESK - so-libs-master-stage-site-java jenkins job is failing

[Jessica Wagantall via RT]

Win together !!
> 
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> This e-mail and its attachments contain confidential information from
> HUAWEI, which is intended only for the person  or entity whose address
> is listed above. Any use of the information contained herein in any
> way (including, but not   limited to, total or partial disclosure,
> reproduction, or dissemination) by persons other than the intended
> recipient(s) is  prohibited. If you receive this e-mail in error,
> please notify the sender by phone or email immediately and delete it!
> 
> 
> 
> -Original Message-
> From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-
> boun...@lists.onap.org] On Behalf Of Jessica Wagantall via RT
> Sent: Friday, February 09, 2018 1:40 AM
> To: Subhash Kumar Singh
> Cc: onap-discuss@lists.onap.org
> Subject: [onap-discuss] [ONAP Helpdesk #52163] RE: ONAP-HELPDESK - so-
> libs-master-stage-site-java jenkins job is failing
> 
> Dear Subhash,
> 
> The current released version of this artifact is 1.1.0:
> https://nexus.onap.org/content/repositories/releases/org/openecomp/so/libs/openstack-
> java-sdk/
> 
> Your pom file has the dependency on 1.2.0-SNAPSHOT which should not be
> there.
> We are avoiding dependencies on staging/snapshot artifacts since we
> made already our official release into Nexus. The best way to resolve
> this issue is to make an un-official release of the artifacts that you
> need (like other projects do) and make your dependencies against those
> new released artifacts.
> Please make sure any release requests are requested by the PTL of the
> project.
> 
> More information on this workflow can be found here:
> https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-
> IssueofdependencyonSnapshot
> 
> Thanks!
> Jess
> 
> On Thu Feb 08 06:07:13 2018, subhash.kumar.si...@huawei.com wrote:
> > + onap-helpdesk
> >
> > --
> > Regards,
> > Subhash Kumar Singh
> >
> > **
> > *
> > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复
> > 制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！*
> > *
> >
> > **
> > * This e-mail and its attachments contain
> > confidential
> > information from HUAWEI, which is intended only for the person  or
> > entity whoseaddress 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, pleasenotify the sender by phone or email immediately and
> > delete it!
> > **
> > *
> >
> > From: Subhash Kumar Singh
> > Sent: Thursday, February 08, 2018 4:17 PM
> > To: onap-discuss@lists.onap.org
> >  Cc: Seshu m <seshu.kuma...@huawei.com>; Gildas Lanilis
> > <gildas.lani...@huawei.com>
> >  Subject: ONAP-HELPDESK - so-libs-master-stage-site-java jenkins job
> > is
> > failing
> >
> > Hello ONAP helpdesk,
> >
> > We are facing issue with so-libs-master-stage-site-java Jenkins
> > job[1], which is continually failing.
> > I observed that job is trying to fetch artifact v1.2.0[2] which is
> > not
> > available in release repository[3].
> >
> > In other projects (like CLI[4]), I observed that  *-master-stage-java
> > job is failing.
> >
> > Please help us to resolve this issue.
> >
> > [1] https://jenkins.onap.org/view/so/job/so-libs-master-stage-site-
> > java/
> > [2] https://jenkins.onap.org/view/so/job/so-libs-master-stage-site-
> > java/173/console
> > [3]
> > https://nexus.onap.org/content/repositories/releases/org/openecomp/so/
> > libs/openstack-
> > java-sdk/openstack-client/
> > [4] https://jenkins.onap.org/view/cli/job/cli-master-stage-site-java/
> > --
> > Regards,
> > Subhash Kumar Singh
> >
> > **
> > *
> > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复
> > 制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！*
> > ***

[onap-discuss] [ONAP Helpdesk #52001] [ONAP] need a VM for integration reporting aggregation

[Jessica Wagantall via RT]

Dear Morgan, 

I was talking today with Aric about this (since he has seen this working in 
opnfv).
I know from him that this system is not easily adaptable to other projects. 

Are you familiar with how this system is developed?

Do you know who can help us rewriting this so that easily adaptable to other 
projects?

Thanks!
Jess

On Mon Feb 05 03:17:16 2018, morgan.richo...@orange.com wrote:
> Hi,
> 
> would it be possible to get IT resources to host ONAP integration
> results.
> The idea is to collect test results from the different CI chains and
> provide an aggregated view of the results (referencing jenkins runs on
> different labs with different installers, on different versions
> (Amsterdam, Master (Beijing),..).
> It is an adaptation of what is currently done in OPNFV
> (http://testresults.opnfv.org/).
> The most straight forward way would be
> - duplication of the testresults.opnfv.org VM managed by Linux
> Foundation (nginx, docker APi, docker reporting, mongo DB, git, would
> be preinstalled)
> - configuration of testresults subdomain for onap main domain to point
> testresults.onap.org to the IP of this duplicated VM
> 
> I would make some cleaning on the duplicated VM
> - clean several accounts used in OPNFV and not needed for ONAP
> - dump of the OPNFV DB
> - creation of ONAP DB (installers: OOM, Heat; test cases: Functional
> test cases (robot, vFW, vLB,), benchmark ..)
> 
> We should also re-use the existing jenkins Jobs in order to sync the
> deployement of the dockers, backup the DB from ONAP main CI
> 
> If it is not possible to duplicate the VM, is it possible to get a
> fresh VM
> - 2 vCPU
> - 80 Go disk
> - 8 Go Ram
> We could even start smaller if needed, but that is the current sizing
> on OPNFV side and we had to increase it once (initial sizing was too
> small)
> 
> I gave a try on my local POD and took some screenshots (attached file)
> Please note that Functest here means all the functional testing (no
> bijection with the OPNFV functest project) and would leverage the
> robot healtcheck as well as automated functional testcases.
> Benchmark corresponds to the new benchmark project
> 
> I think it is a good example of Xcommunity synergies..
> 
> Thanks
> 
> Morgan
> 
> _
> 
> Ce message et ses pieces jointes peuvent contenir des informations
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les
> messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere,
> deforme ou falsifie. Merci.
> 
> This message and its attachments may contain confidential or
> privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have
> been modified, changed or falsified.
> Thank you.



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

[onap-discuss] [ONAP Helpdesk #52163] RE: ONAP-HELPDESK - so-libs-master-stage-site-java jenkins job is failing

[Jessica Wagantall via RT]

Dear Subhash, 

The current released version of this artifact is 1.1.0: 
https://nexus.onap.org/content/repositories/releases/org/openecomp/so/libs/openstack-java-sdk/

Your pom file has the dependency on 1.2.0-SNAPSHOT which should not be there. 
We are avoiding dependencies on staging/snapshot artifacts since we made 
already our official
release into Nexus. The best way to resolve this issue is to make an 
un-official release of the
artifacts that you need (like other projects do) and make your dependencies 
against those new
released artifacts.
Please make sure any release requests are requested by the PTL of the project. 

More information on this workflow can be found here: 
https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-IssueofdependencyonSnapshot

Thanks!
Jess

On Thu Feb 08 06:07:13 2018, subhash.kumar.si...@huawei.com wrote:
> + onap-helpdesk
> 
> --
> Regards,
> Subhash Kumar Singh
> 
> ***
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
> 
> ***
> This e-mail and its attachments contain confidential information from
> HUAWEI, which is intended only for the person  or entity whoseaddress
> 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, pleasenotify the sender by phone or email immediately and
> delete it!
> ***
> 
> From: Subhash Kumar Singh
> Sent: Thursday, February 08, 2018 4:17 PM
> To: onap-discuss@lists.onap.org
> Cc: Seshu m ; Gildas Lanilis
> 
> Subject: ONAP-HELPDESK - so-libs-master-stage-site-java jenkins job is
> failing
> 
> Hello ONAP helpdesk,
> 
> We are facing issue with so-libs-master-stage-site-java Jenkins
> job[1], which is continually failing.
> I observed that job is trying to fetch artifact v1.2.0[2] which is not
> available in release repository[3].
> 
> In other projects (like CLI[4]), I observed that  *-master-stage-java
> job is failing.
> 
> Please help us to resolve this issue.
> 
> [1] https://jenkins.onap.org/view/so/job/so-libs-master-stage-site-
> java/
> [2] https://jenkins.onap.org/view/so/job/so-libs-master-stage-site-
> java/173/console
> [3]
> https://nexus.onap.org/content/repositories/releases/org/openecomp/so/libs/openstack-
> java-sdk/openstack-client/
> [4] https://jenkins.onap.org/view/cli/job/cli-master-stage-site-java/
> --
> Regards,
> Subhash Kumar Singh
> 
> ***
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
> 
> ***
> This e-mail and its attachments contain confidential information from
> HUAWEI, which is intended only for the person  or entity whoseaddress
> 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, pleasenotify 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 #52070] ONAP Jira system is down

[Jessica Wagantall via RT]

Sorry for the inconvenience. 

I have confirm all the services are stable now. 

Thanks!
Jess

On Tue Feb 06 07:17:22 2018, seshu.kuma...@huawei.com wrote:
> Dear LF
> 
> ONAP Jira is throwing a timeout error when tried to access any
> specific content.
> Request to kindly look into the issue asap.
> 
> 
> Best regards
> Seshu Kumar M
> Huawei Technologies India Pvt, Ltd.
> 
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
> 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
> 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> This e-mail and its attachments contain confidential information from
> HUAWEI, which
> is intended only for the person or entity whose address is listed
> above. Any use of the
> information contained herein in any way (including, but not limited
> to, total or partial
> disclosure, reproduction, or dissemination) by persons other than the
> intended
> recipient(s) is prohibited. If you receive this e-mail in error,
> please notify the sender by
> phone or email immediately and delete it!
> 



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

[onap-discuss] [ONAP Helpdesk #52024] Gerrit, jira down 20180205:1215 GMT-5

[Jessica Wagantall via RT]

Dear Michael, 

Looks like this was more of a network glitch. 
All the services are now confirmed to be up. 

Sorry for the inconvenience. 

Thanks!
Jess

On Mon Feb 05 12:23:57 2018, frank.obr...@amdocs.com wrote:
> Team,
>Gerrit and jira just went down for a couple min - is this the heap
> issue.
>/michael
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #51622] Release job not uploading Sonar changes

[Jessica Wagantall via RT]

Dear Pam, 

This is now fixed after a server restart
https://sonar.onap.org/overview?id=27681

Sorry for the inconvenience. 

thanks!
Jess

On Mon Jan 29 13:09:26 2018, jwagantall wrote:
> Dear Pam,
> 
> I have seen this issue before.
> This is caused by a backlog on Sonar tasks and hence the reports are
> delayed.
> Take a look at the screen attached.
> 
> 
> 
> I am looking into what is causing this delay now
> 
> thanks!
> Jess
> 
> On Fri Jan 26 09:38:36 2018, pdrag...@research.att.com wrote:
> > LF Helpdesk and ONAP Community,
> >
> > For our repository policy/drools-applications. We have had some code
> > submissions to fix technical debt and add Junit tests. Despite
> > several
> > successful daily release job runs, sonar has not had an upload since
> > January 18th. There are no errors in the logs, and the logs are very
> > similar both before and after January 18th.
> >
> > Has anyone else have this problem before? Can anyone suggest
> > something
> > to look at?
> >
> > This is the latest successful job that DID upload sonar data:
> >
> > https://jenkins.onap.org/view/policy/job/policy-drools-applications-
> > master-release-version-java-daily/408/
> >
> > This is the next successful job where a changes was made after 408
> > that did NOT upload any sonar data:
> >
> > https://jenkins.onap.org/view/policy/job/policy-drools-applications-
> > master-release-version-java-daily/414/
> >
> > Even if there wasn’t a commit, there should have been an upload but
> > sonar reports the last analysis was Jan 18.
> >
> > [cid:image001.png@01D39689.56562B10]
> >
> > Any help or suggestions are appreciated,
> >
> > Pam
> > ONAP Policy PTL
> >



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

[onap-discuss] [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot repository setting?)

[Jessica Wagantall via RT]

Closing this for now since the jobs have been removed in 
https://gerrit.onap.org/r/#/c/28373/

On Fri Jan 12 22:30:45 2018, zhao.huab...@zte.com.cn wrote:
> Hi Jess,
> 
> 
> 
> This failed project doesn't depend on any snapshot artifact of other
> projects.
> 
> 
> 
> 
> 
> For example, the failed job "msb-discovery-master-stage-site-java"
> says it can't find "org.onap.msb.discovery.sdclient:discovery-
> service:jar:1.1.0" which is an artifact generated by this maven
> project itself.
> 
> 
> 
> 
> I can find this artifact in the stagging and snapshot repo.
> 
> 
> 
> 
> 
> 
> 
> https://jenkins.onap.org/view/msb/job/msb-discovery-master-stage-site-
> java/
> 
> Build failed to find artifact
> org.onap.msb.discovery.sdclient:discovery-service:jar:1.1.0 needed for
> sub-project org.onap.msb.discovery.sdclient:discovery-
> standalone:pom:1.1.0. Check correct groupId, artifactId and version.
> This may also indicate a problem with nexus. Another possibility is
> that this is a -SNAPSHOT version and it has expired from nexus -- in
> that case check with the project which provides the artifact.
> 
> 
> 
> 
> Thanks,
> 
> 
> Huabing
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Original Mail
> 
> 
> 
> Sender:  ;
> To: zhaohuabing10201488;
> CC:  ;
> Date: 2018/01/04 09:15
> Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot
> repository setting?)
> 
> 
> Although that can sound like the fastest way to fix it, is is best to
> move away from Snapshot dependencies as per these strategies:
> 
> https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-
> Whatarethe2bigissuestoaddress?
> 
> Thanks!
> Jess
> 
> On Tue Jan 02 22:01:53 2018, zhao.huab...@zte.com.cn wrote:
> > I mean, could we just use the snapshot artifacts for these Jenkins
> > jobs?
> >
> >
> > Before the release of 1.0.0, all jenkins jobs ran very well. Should I
> > modify these jobs or pom.xml to use snapshot instead of release?
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Original Mail
> >
> >
> >
> > Sender:  ;
> > To: zhaohuabing10201488;
> > CC:  ;
> > Date: 2018/01/03 10:04
> > Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot
> > repository setting?)
> >
> >
> > We could point to an older released version of these artifacts.
> >
> > Also, if we decide to release this newer version 1.1.0 we won't be
> > putting it under any particular official name like "amserdam" or
> > "beijing" if this is your concern.
> >
> > Thanks
> > Jess
> >
> > On Tue Jan 02 03:04:23 2018, zhao.huab...@zte.com.cn wrote:
> > > Hi Jess,
> > >
> > >
> > > 1.1.0 is just a snapshot version right now, so it should not be
> > > released at this point. Do we have a workaround for this issue?
> > >
> > >
> > > Thanks,
> > >
> > >
> > > Huabing
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > Original Mail
> > >
> > >
> > >
> > > Sender:  ;
> > > To: zhaohuabing10201488;
> > > CC:  ;
> > > Date: 2017/12/30 02:12
> > > Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to
> > > snapshot
> > > repository setting?)
> > >
> > >
> > > Dear Huabing,
> > >
> > > This is the last released version we had for these binaries:
> > > https://nexus.onap.org/content/repositories/releases/org/onap/msb/apigateway/apiroute/apiroute-
> > > standalone/
> > >
> > > Looks like we need to make a release for version 1.1.0. Do you have
> > > a
> > > candidate for this version that we can release?
> > >
> > > Thanks!
> > >   Jess.
> > >
> > > On Tue Dec 26 04:17:29 2017, zhao.huab...@zte.com.cn wrote:
> > > > Dear ONAP helpdesk,
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > I noticed that some of the jenkins jobs are continually failing,
> > > > it
> > > > seems that the snapshot repository is missing in the ONAP maven
> > > > setting.
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > One failed Jenkins job:
> > > > https://jenkins.onap.org/view/msb/job/msb-
> > > > apigateway-master-stage-site-java/
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-
> > > > site-
> > > > plugin:3.6:site (default-cli) on project msb-apigateway-parent:
> > > > failed
> > > > to get report for org.apache.maven.plugins:maven-javadoc-plugin:
> > > > Failed to execute goal on project apiroute-standalone: Could not
> > > > resolve dependencies for project
> > > > org.onap.msb.apigateway.apiroute:apiroute-standalone:pom:1.1.0:
> > > > Could
> > > > not find artifact org.onap.msb.apigateway.apiroute:apiroute-
> > > > service:jar:1.1.0 in releases
> > > > (https://nexus.onap.org/content/repositories/releases/) -> [Help
> > > > 1]13:15:21 [ERROR]
> > > >
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > >
> > > > Huabing

[onap-discuss] [ONAP Helpdesk #51095] Add logging-analytics repo to Jenkins JobBuilder and Sonar

[Jessica Wagantall via RT]

Dear Michael, 

I have double checked that Jenkins (Maven settings file), Nexus2 and Nexus3 
bits for this new project are present. 

I have also created the new Jenkins tab in preparation for the JJB jobs. Sonar 
will appear once the daily job runs and it will automatically generate an entry 
for your project there. 

Here is an initial change for your JJB templates:
https://gerrit.onap.org/r/#/c/28345/

Can you please review this change and let me know for any changes you need 
(depending on your project's needs)

Thanks a ton!
Jess

On Sun Jan 14 22:59:47 2018, frank.obr...@amdocs.com wrote:
> Linux Foundation, TSC,
>Could you add the logging-analytics project to Jenkins,
> nexus/nexus3 and Sonar.
>We have started development work on the Logging RI and AOP library
> and would like the standard Java Jenkins build to kick in along with
> sonar tracking.
>Currently we need the JobBuilder -1/+1 process to run on git
> commits to the logging-analytics repo.
>I have submitted a functioning minimal project structure that
> builds a template rest war as the initial framework.  The docker
> container that will run this microservice is next in the list.
>See
> https://gerrit.onap.org/r/#/c/28129/
>tested under
> http://logging.us-east-1.elasticbeanstalk.com/rest/read/test
>for
> https://jira.onap.org/browse/LOG-120
>for the R2 epic
> https://jira.onap.org/browse/LOG-95
>We will need a new folder under https://jenkins.onap.org/
>Thank you
>/michael
> 
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #51075] JIRA Beijing release in Affects/Fix Version missing?

[Jessica Wagantall via RT]

Dear Michael, 

I went through the projects and added the "Beijing Release" in 2 projects that 
were missing it. 

Can you please double check your project and let me know if you see it now?

Thanks a ton!
Jess

On Sat Jan 13 19:22:11 2018, frank.obr...@amdocs.com wrote:
> Team,
>Hi, noticed when raising/editing jiras today that the Beijing
> release is missing - we only have Amsterdam, Casablanca Release,
> Dublin Release.
>The Beijing release was last there yesterday (Friday 20180112)
>When we find issues in master/Beijing we are unable to set the
> Affects or Fix field for that release.
>Thank you
>/michael
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #51163] Promote Liang ke to Committer of Multi VIM/Cloud

[Jessica Wagantall via RT]

Thanks so much Kenny, 

This request has been completed now

Thanks!
Jess

On Tue Jan 16 12:13:33 2018, jwagantall wrote:
> Dear Xinhui,
> 
> Do you have a TSC approval link for this request? I was not able to
> find it in the link you provided me.
> 
> thanks a ton
> Jess
> 
> On Tue Jan 16 07:15:02 2018, lxin...@vmware.com wrote:
> > Hi Jessica,
> >
> > TSC have approved Liang ke as a committer of Multi VIM/Cloud. Please
> > help to promote him or let me know I need submit some ticket for
> > this.
> >
> > Please refer to this link for more info:
> > https://wiki.onap.org/pages/viewpage.action?pageId=22249517
> >
> > Thanks,
> >
> > Xinhui Li
> > PTL of Multi VIM/Cloud



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

[onap-discuss] [ONAP Helpdesk #51163] Promote Liang ke to Committer of Multi VIM/Cloud

[Jessica Wagantall via RT]

Dear Xinhui, 

Do you have a TSC approval link for this request? I was not able to find it in 
the link you provided me. 

thanks a ton
Jess

On Tue Jan 16 07:15:02 2018, lxin...@vmware.com wrote:
> Hi Jessica,
> 
> TSC have approved Liang ke as a committer of Multi VIM/Cloud. Please
> help to promote him or let me know I need submit some ticket for this.
> 
> Please refer to this link for more info:
> https://wiki.onap.org/pages/viewpage.action?pageId=22249517
> 
> Thanks,
> 
> Xinhui Li
> PTL of Multi VIM/Cloud



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

[onap-discuss] [ONAP Helpdesk #51126] [integration] nexus.onap.org is down

[Jessica Wagantall via RT]

Should be back now

Thanks!

On Mon Jan 15 14:08:01 2018, jwagantall wrote:
> Our team is looking into it now.
> 
> thanks a ton and sorry for the inconvenience
> Jess
> 
> On Mon Jan 15 13:14:35 2018, gary.i...@huawei.com wrote:
> > Hi helpdesk,
> >
> > Nexus.onap.org is currently returning 502 Bad Gateway.  Can you take
> > a look?
> >
> > Thanks,
> > Gary
> >
> >



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

[onap-discuss] [ONAP Helpdesk #51126] [integration] nexus.onap.org is down

[Jessica Wagantall via RT]

Our team is looking into it now. 

thanks a ton and sorry for the inconvenience
Jess

On Mon Jan 15 13:14:35 2018, gary.i...@huawei.com wrote:
> Hi helpdesk,
> 
> Nexus.onap.org is currently returning 502 Bad Gateway.  Can you take a look?
> 
> Thanks,
> Gary
> 
> 



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

[onap-discuss] [ONAP Helpdesk #50939] Infra is down

[Jessica Wagantall via RT]

Everything is back now.. 

This was caused due to a quick maintenance update. 

Thanks
Jess

On Wed Jan 10 17:20:28 2018, jwagantall wrote:
> Dear Alexis
> 
> Our team is now restoring the services. 
> 
> Thanks!
> Jess
> 
> On Wed Jan 10 17:11:12 2018, adetalhoue...@gmail.com wrote:
> > Greetings,
> > 
> > Looks like the infra is down? Gerrit, Jira, Confluence
> > 
> > Can someone help please?
> > 
> > Thanks,
> > Alexis
> 
> 



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

[onap-discuss] [ONAP Helpdesk #50939] Infra is down

[Jessica Wagantall via RT]

Dear Alexis

Our team is now restoring the services. 

Thanks!
Jess

On Wed Jan 10 17:11:12 2018, adetalhoue...@gmail.com wrote:
> Greetings,
> 
> Looks like the infra is down? Gerrit, Jira, Confluence
> 
> Can someone help please?
> 
> Thanks,
> Alexis



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

[onap-discuss] [ONAP Helpdesk #50702] Unable to create new JIRA on mandatory "Affects Version" introduced today

[Jessica Wagantall via RT]

Dear Michael , 

Can you please try again. This mandatory field has now been isolated to only 
Bug type issues on its own. Epic and Story can now be created without the need 
of an Affected Version. 

Please try and let me know. 

Thanks and sorry for the trouble
Jess

On Fri Jan 05 13:33:22 2018, jwagantall wrote:
> Working on this now.. 
> 
> thanks!
> Jess
> 
> On Fri Jan 05 08:17:31 2018, frank.obr...@amdocs.com wrote:
> > Jessica,
> >Hi, JIRA currently is broken on the new validation field - we are
> > not able to add any new issues - could we get this addressed ASAP,
> > either temporarily reverse the change and retest it before
> > reintroducing it or temporarily auto-populating it
> > 
> > Thank you
> > /michael
> > 
> > -Original Message-
> >  From: ONAP Helpdesk via RT [mailto:onap-
> > helpd...@rt.linuxfoundation.org]
> > Sent: Friday, January 5, 2018 00:44
> > To: Michael O'Brien 
> > Subject: [ONAP Helpdesk #50702] AutoReply: Unable to create new JIRA
> > on mandatory "Affects Version" introduced today
> > 
> > Greetings,
> > 
> > Your support ticket regarding:
> > "Unable to create new JIRA on mandatory "Affects Version"
> > introduced today", has been entered in our ticket tracker.  A summary
> > of your ticket appears below.
> > 
> > If you have any follow-up related to this issue, please reply to this
> > email.
> > 
> > You may also follow up on your open tickets by visiting
> > https://rt.linuxfoundation.org/ -- if you have not logged into RT
> > before, you will need to follow the "Forgot your password" link to set
> > an RT password.
> > 
> > --
> > The Linux Foundation Support Team
> > 
> > 
> > -
> > LF,
> >   Hi, I totally agree with the new mandatory field "affects version"
> > - however I have tried adjusting the "configure fields" section and an
> > unable to raise any Epic or Story anymore because of the blocking
> > error on this field - which does not show on the create issue screen.
> >Setting the "Fix Version/s" field does not help.
> >Can you adjust the "Create Issue" screen so we can fill in this
> > mandatory field
> > 
> > 
> > [cid:image002.jpg@01D385BE.48F088C0]
> > thank you
> >/Michael
> > 
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> > 
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > 
> > 
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> > 
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > 
> 
> 



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

[onap-discuss] [ONAP Helpdesk #50702] Unable to create new JIRA on mandatory "Affects Version" introduced today

[Jessica Wagantall via RT]

Working on this now.. 

thanks!
Jess

On Fri Jan 05 08:17:31 2018, frank.obr...@amdocs.com wrote:
> Jessica,
>Hi, JIRA currently is broken on the new validation field - we are
> not able to add any new issues - could we get this addressed ASAP,
> either temporarily reverse the change and retest it before
> reintroducing it or temporarily auto-populating it
> 
> Thank you
> /michael
> 
> -Original Message-
>  From: ONAP Helpdesk via RT [mailto:onap-
> helpd...@rt.linuxfoundation.org]
> Sent: Friday, January 5, 2018 00:44
> To: Michael O'Brien 
> Subject: [ONAP Helpdesk #50702] AutoReply: Unable to create new JIRA
> on mandatory "Affects Version" introduced today
> 
> Greetings,
> 
> Your support ticket regarding:
> "Unable to create new JIRA on mandatory "Affects Version"
> introduced today", has been entered in our ticket tracker.  A summary
> of your ticket appears below.
> 
> If you have any follow-up related to this issue, please reply to this
> email.
> 
> You may also follow up on your open tickets by visiting
> https://rt.linuxfoundation.org/ -- if you have not logged into RT
> before, you will need to follow the "Forgot your password" link to set
> an RT password.
> 
> --
> The Linux Foundation Support Team
> 
> 
> -
> LF,
>   Hi, I totally agree with the new mandatory field "affects version"
> - however I have tried adjusting the "configure fields" section and an
> unable to raise any Epic or Story anymore because of the blocking
> error on this field - which does not show on the create issue screen.
>Setting the "Fix Version/s" field does not help.
>Can you adjust the "Create Issue" screen so we can fill in this
> mandatory field
> 
> 
> [cid:image002.jpg@01D385BE.48F088C0]
> thank you
>/Michael
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot repository setting?)

[Jessica Wagantall via RT]

Although that can sound like the fastest way to fix it, is is best to move away 
from Snapshot dependencies as per these strategies:

https://wiki.onap.org/display/DW/Release+Versioning+Strategy#ReleaseVersioningStrategy-Whatarethe2bigissuestoaddress?

Thanks!
Jess

On Tue Jan 02 22:01:53 2018, zhao.huab...@zte.com.cn wrote:
> I mean, could we just use the snapshot artifacts for these Jenkins
> jobs?
> 
> 
> Before the release of 1.0.0, all jenkins jobs ran very well. Should I
> modify these jobs or pom.xml to use snapshot instead of release?
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Original Mail
> 
> 
> 
> Sender:  ;
> To: zhaohuabing10201488;
> CC:  ;
> Date: 2018/01/03 10:04
> Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot
> repository setting?)
> 
> 
> We could point to an older released version of these artifacts.
> 
> Also, if we decide to release this newer version 1.1.0 we won't be
> putting it under any particular official name like "amserdam" or
> "beijing" if this is your concern.
> 
> Thanks
> Jess
> 
> On Tue Jan 02 03:04:23 2018, zhao.huab...@zte.com.cn wrote:
> > Hi Jess,
> >
> >
> > 1.1.0 is just a snapshot version right now, so it should not be
> > released at this point. Do we have a workaround for this issue?
> >
> >
> > Thanks,
> >
> >
> > Huabing
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Original Mail
> >
> >
> >
> > Sender:  ;
> > To: zhaohuabing10201488;
> > CC:  ;
> > Date: 2017/12/30 02:12
> > Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot
> > repository setting?)
> >
> >
> > Dear Huabing,
> >
> > This is the last released version we had for these binaries:
> > https://nexus.onap.org/content/repositories/releases/org/onap/msb/apigateway/apiroute/apiroute-
> > standalone/
> >
> > Looks like we need to make a release for version 1.1.0. Do you have a
> > candidate for this version that we can release?
> >
> > Thanks!
> >   Jess.
> >
> > On Tue Dec 26 04:17:29 2017, zhao.huab...@zte.com.cn wrote:
> > > Dear ONAP helpdesk,
> > >
> > >
> > >
> > >
> > >
> > >
> > > I noticed that some of the jenkins jobs are continually failing, it
> > > seems that the snapshot repository is missing in the ONAP maven
> > > setting.
> > >
> > >
> > >
> > >
> > >
> > >
> > > One failed Jenkins job: https://jenkins.onap.org/view/msb/job/msb-
> > > apigateway-master-stage-site-java/
> > >
> > >
> > >
> > >
> > >
> > > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-
> > > plugin:3.6:site (default-cli) on project msb-apigateway-parent:
> > > failed
> > > to get report for org.apache.maven.plugins:maven-javadoc-plugin:
> > > Failed to execute goal on project apiroute-standalone: Could not
> > > resolve dependencies for project
> > > org.onap.msb.apigateway.apiroute:apiroute-standalone:pom:1.1.0:
> > > Could
> > > not find artifact org.onap.msb.apigateway.apiroute:apiroute-
> > > service:jar:1.1.0 in releases
> > > (https://nexus.onap.org/content/repositories/releases/) -> [Help
> > > 1]13:15:21 [ERROR]
> > >
> > >
> > >
> > >
> > > Thanks,
> > >
> > >
> > > Huabing



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

[onap-discuss] [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot repository setting?)

[Jessica Wagantall via RT]

We could point to an older released version of these artifacts. 

Also, if we decide to release this newer version 1.1.0 we won't be putting it 
under any particular official name like "amserdam" or "beijing" if this is your 
concern. 

Thanks
Jess

On Tue Jan 02 03:04:23 2018, zhao.huab...@zte.com.cn wrote:
> Hi Jess,
> 
> 
> 1.1.0 is just a snapshot version right now, so it should not be
> released at this point. Do we have a workaround for this issue?
> 
> 
> Thanks,
> 
> 
> Huabing
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Original Mail
> 
> 
> 
> Sender:  ;
> To: zhaohuabing10201488;
> CC:  ;
> Date: 2017/12/30 02:12
> Subject: [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot
> repository setting?)
> 
> 
> Dear Huabing,
> 
> This is the last released version we had for these binaries:
> https://nexus.onap.org/content/repositories/releases/org/onap/msb/apigateway/apiroute/apiroute-
> standalone/
> 
> Looks like we need to make a release for version 1.1.0. Do you have a
> candidate for this version that we can release?
> 
> Thanks!
>   Jess.
> 
> On Tue Dec 26 04:17:29 2017, zhao.huab...@zte.com.cn wrote:
> > Dear ONAP helpdesk,
> >
> >
> >
> >
> >
> >
> > I noticed that some of the jenkins jobs are continually failing, it
> > seems that the snapshot repository is missing in the ONAP maven
> > setting.
> >
> >
> >
> >
> >
> >
> > One failed Jenkins job: https://jenkins.onap.org/view/msb/job/msb-
> > apigateway-master-stage-site-java/
> >
> >
> >
> >
> >
> > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-
> > plugin:3.6:site (default-cli) on project msb-apigateway-parent:
> > failed
> > to get report for org.apache.maven.plugins:maven-javadoc-plugin:
> > Failed to execute goal on project apiroute-standalone: Could not
> > resolve dependencies for project
> > org.onap.msb.apigateway.apiroute:apiroute-standalone:pom:1.1.0: Could
> > not find artifact org.onap.msb.apigateway.apiroute:apiroute-
> > service:jar:1.1.0 in releases
> > (https://nexus.onap.org/content/repositories/releases/) -> [Help
> > 1]13:15:21 [ERROR]
> >
> >
> >
> >
> > Thanks,
> >
> >
> > Huabing



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

[onap-discuss] [ONAP Helpdesk #50378] Jenkins jobs failed (due to snapshot repository setting?)

[Jessica Wagantall via RT]

Dear Huabing,

This is the last released version we had for these binaries:
https://nexus.onap.org/content/repositories/releases/org/onap/msb/apigateway/apiroute/apiroute-standalone/

Looks like we need to make a release for version 1.1.0. Do you have a candidate 
for this version that we can release?

Thanks!
Jess.  

On Tue Dec 26 04:17:29 2017, zhao.huab...@zte.com.cn wrote:
> Dear ONAP helpdesk,
> 
> 
> 
> 
> 
> 
> I noticed that some of the jenkins jobs are continually failing, it
> seems that the snapshot repository is missing in the ONAP maven
> setting.
> 
> 
> 
> 
> 
> 
> One failed Jenkins job: https://jenkins.onap.org/view/msb/job/msb-
> apigateway-master-stage-site-java/
> 
> 
> 
> 
> 
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-
> plugin:3.6:site (default-cli) on project msb-apigateway-parent: failed
> to get report for org.apache.maven.plugins:maven-javadoc-plugin:
> Failed to execute goal on project apiroute-standalone: Could not
> resolve dependencies for project
> org.onap.msb.apigateway.apiroute:apiroute-standalone:pom:1.1.0: Could
> not find artifact org.onap.msb.apigateway.apiroute:apiroute-
> service:jar:1.1.0 in releases
> (https://nexus.onap.org/content/repositories/releases/) -> [Help
> 1]13:15:21 [ERROR]
> 
> 
> 
> 
> Thanks,
> 
> 
> Huabing



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

[onap-discuss] [ONAP Helpdesk #49130] Branch creation permissions

[Jessica Wagantall via RT]

Rejecting... 

Please re-open this request if it becomes needed again.

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

[onap-discuss] [ONAP Helpdesk #49557] JIRA server not responding 20171107:1600 EDT

[Jessica Wagantall via RT]

Must have been a small glitch. 

The server is back up

Thanks!
Jess

On Thu Dec 07 16:08:06 2017, frank.obr...@amdocs.com wrote:
> Multiple internet connections tested
> Was up 5 min ago
> 
> Michael O'Brien
> Amdocs Technology
> 16135955268
> 55268
> [amdocs-a]
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] [ONAP Helpdesk #49130] Branch creation permissions

[Jessica Wagantall via RT]

Dear Michael, 

Do you still need these permissions? Were you able to get TSC approval?

Thanks!
Jess

On Fri Dec 01 14:13:22 2017, jwagantall wrote:
> Dear Michael,
> 
> I see you listed as a contributor but not as a committer:
> https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-
> LoggingEnhancements
> 
> You will need a TSC request to get approved to be a committer for this
> project.
> 
> In the meantime, please let me know the branch name that you need and
> the branching point and I will help
> 
> thanks!
> Jess
> 
> On Thu Nov 30 00:19:48 2017, frank.obr...@amdocs.com wrote:
> > Gildas, Kenny,
> >Hi, I would like to create a branch in the logging-analytics repo
> > -
> > for https://jira.onap.org/browse/LOG-108
> > https://gerrit.onap.org/r/#/admin/projects/logging-analytics,branches
> >I raised a ticket on this before - could you check my branch
> > creation permissions.
> >
> > User michaelobrien
> >
> > Thank you
> > /michael
> >
> > Michael O'Brien
> > Amdocs Technology
> > 16135955268
> > 55268
> > [amdocs-a]
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> >
> > you may review at https://www.amdocs.com/about/email-disclaimer
> > 



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

[onap-discuss] [ONAP Helpdesk #49350] [ONAP Helpdesk]No vfc-nfvo-lcm related jenkins jobs for Amsterdam branch

[Jessica Wagantall via RT]

My apologies, 

I think I had missed that project. 
The amsterdam branch stream is set now. 

Thanks!
Jess

On Mon Dec 04 02:53:31 2017, ying.yunl...@zte.com.cn wrote:
> Dear Jess，
> 
> 
> 
> 
> I found that there are still no vfc-nfvo-lcm related jenkins jobs for
> Amsterdam branch. So amsterdam vfc-nfvo-lcm related bugs could not be
> merged. Can you help to add these jenkins jobs.
> 
> 
> 
> 
> Thanks!
> 
> Yunlong



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

[onap-discuss] [ONAP Helpdesk #49130] Branch creation permissions

[Jessica Wagantall via RT]

Dear Michael, 

I see you listed as a contributor but not as a committer:
https://wiki.onap.org/display/DW/Resources+and+Repositories#ResourcesandRepositories-LoggingEnhancements

You will need a TSC request to get approved to be a committer for this project. 

In the meantime, please let me know the branch name that you need and the 
branching point and I will help

thanks!
Jess

On Thu Nov 30 00:19:48 2017, frank.obr...@amdocs.com wrote:
> Gildas, Kenny,
>Hi, I would like to create a branch in the logging-analytics repo -
> for https://jira.onap.org/browse/LOG-108
> https://gerrit.onap.org/r/#/admin/projects/logging-analytics,branches
>I raised a ticket on this before - could you check my branch
> creation permissions.
> 
> User michaelobrien
> 
> Thank you
> /michael
> 
> Michael O'Brien
> Amdocs Technology
> 16135955268
> 55268
> [amdocs-a]
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

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

[Jessica Wagantall via RT]

This is now in place. 

thanks!
Jess

On Tue Nov 21 13:22:26 2017, jwagantall wrote:
> This change is scheduled to be merged today at 2:00pm PDT
> 
> Thanks!
> Jess
> 
> On Mon Oct 23 19:37:02 2017, jwagantall wrote:
> > We were trying to implement it quite few time ago, but it conflicted
> > with the peak of the time in which the devs were doing their changes
> > before the code freeze at a very rapid flow.
> > 
> > I synced with Gildas and he suggested we move this improvement to Nov
> > 16 and for now to start educating the devs about this restriction by
> > adding comments in their gerrit changes.
> > 
> > I agree with Gildas that this enforcement could have caused quite a
> > bit of frustration to developers during this time, but this could be
> > welcomed after Nov 16.
> > 
> > On Mon Oct 23 11:07:04 2017, gary.i...@huawei.com wrote:
> > > 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 
> > > 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 

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

[Jessica Wagantall via RT]

This change is scheduled to be merged today at 2:00pm PDT

Thanks!
Jess

On Mon Oct 23 19:37:02 2017, jwagantall wrote:
> We were trying to implement it quite few time ago, but it conflicted
> with the peak of the time in which the devs were doing their changes
> before the code freeze at a very rapid flow.
> 
> I synced with Gildas and he suggested we move this improvement to Nov
> 16 and for now to start educating the devs about this restriction by
> adding comments in their gerrit changes.
> 
> I agree with Gildas that this enforcement could have caused quite a
> bit of frustration to developers during this time, but this could be
> welcomed after Nov 16.
> 
> On Mon Oct 23 11:07:04 2017, gary.i...@huawei.com wrote:
> > 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 
> > 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.
> > > >

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

[Jessica Wagantall via RT]

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

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

[Jessica Wagantall via RT]

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

[onap-discuss] [ONAP Helpdesk #47527] [DOC] Documentation RTD Build Reaching the Default Time/Memory Quota

[Jessica Wagantall via RT]

Closing this issue for now

Dear Rich, please send a new request if you get to have more errors in the 
future. 

Thanks 
Jess

On Tue Oct 31 17:05:11 2017, jwagantall wrote:
> Dear Rich, 
> 
> do you still have issues with these docs?
> Can you please send us a screenshot or any more info please?
> 
> Thanks!
> Jess
> 
> On Sat Oct 28 20:37:56 2017, KennyPaul wrote:
> > Can you provide some screenshots or some other debug info?
> > Not sure what the issue is here but ODL ran into something like this
> > once and it was caused by inefficient scripting .
> > 
> > On Thu Oct 26 10:23:10 2017, rb2...@att.com wrote:
> > > With recent additions of documentation source we are reaching the
> > > default time/memory quota at Readthedocs.
> > >
> > > There are some things we are doing that will reduce our requirements
> > > but increasing the quota at the Readthedocs would improve turnaround
> > > time as we finalize the Amsterdam Release.
> > >
> > > Does the LF release engineering team have a contact with readthedocs
> > > to request a change in quota?
> > >
> > > Thank you
> > >
> > > Rich
> 
> 



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

[onap-discuss] [ONAP Helpdesk #47650] [cli][lf] Create branch release 1.1.0 for onap/cli

[Jessica Wagantall via RT]

Dear Kanagaraj

Please let me know if you still have any questions and if you were able to use 
my instructions

Thanks a ton
Jess

On Tue Oct 31 12:32:43 2017, jwagantall wrote:
> Dear Kanagaraj,
> 
> you should be able to create the branch from the UI in gerrit.
> Try adding the branch here and let me know if this works for you:
> https://gerrit.onap.org/r/#/admin/projects/cli,branches
> 
> For enabling the Jenkins jobs, you should add the new branch as part
> of the stream list in the yaml template:
> /ci-management/jjb/cli/cli.yaml
> 
> Let me know if you have any questions and if you would like me to
> review your gerrit.
> 
> Thanks!
> Jess
> 
> On Tue Oct 31 03:28:21 2017, kanagaraj.manic...@huawei.com wrote:
> > Hi,
> >
> > To enabled release artifact for Amsterdam release, I would like to
> > create new git branch release-1.1.0 for CLI (onap/cli) project and
> > enable new jenkins jobs under this branch to build following binaries
> > and mark them as Amsterdam release candidate.
> > (I assume that existing Jenkins jobs will not get affected and will
> > continuous produce these artifacts from master branch, and let me
> > know
> > otherwise).
> >
> >
> > 1.   NEXUS artifact zip:  org.onap.cli :: cli-zip :: 1.1.0
> >
> > 2.   Docker container image:  onap/cli (tag: 1.1.0)
> >
> > 3.   Document
> >
> > 4.   Sonar
> >
> > 5.   CSIT
> >
> > Could you please help ? Thank you.
> >
> > Regards
> > Kanagaraj M
> > ONAP-CLI-PTL
> >
> > ***
> > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
> >
> > ***
> > 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 #47527] [DOC] Documentation RTD Build Reaching the Default Time/Memory Quota

[Jessica Wagantall via RT]

Dear Rich, 

do you still have issues with these docs?
Can you please send us a screenshot or any more info please?

Thanks!
Jess

On Sat Oct 28 20:37:56 2017, KennyPaul wrote:
> Can you provide some screenshots or some other debug info?
> Not sure what the issue is here but ODL ran into something like this
> once and it was caused by inefficient scripting .
> 
> On Thu Oct 26 10:23:10 2017, rb2...@att.com wrote:
> > With recent additions of documentation source we are reaching the
> > default time/memory quota at Readthedocs.
> >
> > There are some things we are doing that will reduce our requirements
> > but increasing the quota at the Readthedocs would improve turnaround
> > time as we finalize the Amsterdam Release.
> >
> > Does the LF release engineering team have a contact with readthedocs
> > to request a change in quota?
> >
> > Thank you
> >
> > Rich



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

[onap-discuss] [ONAP Helpdesk #47650] [cli][lf] Create branch release 1.1.0 for onap/cli

[Jessica Wagantall via RT]

Dear Kanagaraj, 

you should be able to create the branch from the UI in gerrit. 
Try adding the branch here and let me know if this works for you:
https://gerrit.onap.org/r/#/admin/projects/cli,branches

For enabling the Jenkins jobs, you should add the new branch as part of the 
stream list in the yaml template:
/ci-management/jjb/cli/cli.yaml

Let me know if you have any questions and if you would like me to review your 
gerrit. 

Thanks!
Jess

On Tue Oct 31 03:28:21 2017, kanagaraj.manic...@huawei.com wrote:
> Hi,
> 
> To enabled release artifact for Amsterdam release, I would like to
> create new git branch release-1.1.0 for CLI (onap/cli) project and
> enable new jenkins jobs under this branch to build following binaries
> and mark them as Amsterdam release candidate.
> (I assume that existing Jenkins jobs will not get affected and will
> continuous produce these artifacts from master branch, and let me know
> otherwise).
> 
> 
> 1.   NEXUS artifact zip:  org.onap.cli :: cli-zip :: 1.1.0
> 
> 2.   Docker container image:  onap/cli (tag: 1.1.0)
> 
> 3.   Document
> 
> 4.   Sonar
> 
> 5.   CSIT
> 
> Could you please help ? Thank you.
> 
> Regards
> Kanagaraj M
> ONAP-CLI-PTL
> 
> ***
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！**
> 
> ***
> 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 #47175] No binaries in ONAP stagging repo

[Jessica Wagantall via RT]

Closing this case now. 

These issues have been resolved and the jobs look stable

Thanks!
Jess

On Thu Oct 19 00:36:43 2017, jwagantall wrote:
> Dear Gary,
> 
> The restore is completed. It looks like for older autoreleases there
> was a problem with Nexus trying to recognize these repos properly.
> Even with some manual work to attempt to bring them back, there would
> not be possible to release them.
> 
> Is it possible to move our dependencies to a newer autorelease? This
> would be the safer option for now.
> 
> Thanks!
> Jess
> 
> On Wed Oct 18 13:16:23 2017, gary.i...@huawei.com wrote:
> > 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 ; 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"  > > 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' ;
> > > 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]
> > > Sent: Tuesday, October 17, 2017 11:40 PM
> > > To: Gary Wu >;
> > > 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://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=
> > >  > > 3A__nexus.onap.org=DwIGaQ=LFYZ-
> > > o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-
> > > q_w=0LmhWnkxvOPOium09mgc1rMdFYVDBpbW0cdM-
> > >  2cR2nc=jEy3cAEf5jesxDTdRj2pmAHa_wFxEA55PMPl1DMpEK4= ,> in
> > > repository autorelease-18453 (staging:
> > > closed) > > 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-
> > > 

[onap-discuss] [ONAP Helpdesk #47177] SO build failing due to no appc client jars in the staging repo

[Jessica Wagantall via RT]

Closing this case now. 

These issues have been resolved and the jobs look stable

Thanks!
Jess

On Wed Oct 18 12:42:08 2017, jwagantall wrote:
> Dear Seshu,
> 
> We are investigating the cause of these problems. For now, It looks
> like there are recent builds that are passing now due to a new appc
> daily job run that just happened this morning.
> 
> Sorry for the inconvenience.
> 
> Will re-trigger the latest so builds to make sure we are ok now that
> the appc binaries are back
> 
> Thanks!
> Jess
> 
> On Wed Oct 18 02:51:07 2017, seshu.kuma...@huawei.com wrote:
> > Dear LF
> >
> > We are facing SO build failures due to appc client jar missing in the
> > nexus staging repo.
> >
> > [ERROR] Failed to execute goal on project MSOCommonBPMN: Could not
> > resolve dependencies for project
> > org.openecomp.so:MSOCommonBPMN:war:1.1.0-SNAPSHOT: The following
> > artifacts could not be resolved: org.openecomp.appc.client:client-
> > kit:jar:1.1.0, org.openecomp.appc.client:client-lib:jar:1.1.0: Could
> > not find artifact org.openecomp.appc.client:client-kit:jar:1.1.0 in
> > staging
> > https://nexus.onap.org/content/repositories/staging/
> >
> >
> > https://jenkins.onap.org/job/so-master-verify-profile-
> > java/479/console
> > https://jenkins.onap.org/job/so-master-verify-profile-
> > java/480/console
> >
> > I inspected the recent code merges made on and after 17 Oct and dint
> > find any code merge that would ideally effect this.
> > Please help us resolve this issue as this asap as this is blocking
> > the
> > entire ONAP integration test progress.
> >
> > 
> > Best regards
> > Seshu Kumar M
> > Huawei Technologies India Pvt, Ltd.
> > 
> > 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
> > 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
> > 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> > This e-mail and its attachments contain confidential information from
> > HUAWEI, which
> > is intended only for the person or entity whose address is listed
> > above. Any use of the
> > information contained herein in any way (including, but not limited
> > to, total or partial
> > disclosure, reproduction, or dissemination) by persons other than the
> > intended
> > recipient(s) is prohibited. If you receive this e-mail in error,
> > please notify the sender by
> > phone or email immediately and delete it!
> >



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

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

[Jessica Wagantall via RT]

We were trying to implement it quite few time ago, but it conflicted with the 
peak of the time in which the devs were doing their changes before the code 
freeze at a very rapid flow. 

I synced with Gildas and he suggested we move this improvement to Nov 16 and 
for now to start educating the devs about this restriction by adding comments 
in their gerrit changes. 

I agree with Gildas that this enforcement could have caused quite a bit of 
frustration to developers during this time, but this could be welcomed after 
Nov 16. 

On Mon Oct 23 11:07:04 2017, gary.i...@huawei.com wrote:
> 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 
> 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

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

[Jessica Wagantall via RT]

Dear Gary, 

The restore is completed. It looks like for older autoreleases there was a 
problem with Nexus trying to recognize these repos properly. Even with some 
manual work to attempt to bring them back, there would not be possible to 
release them. 

Is it possible to move our dependencies to a newer autorelease? This would be 
the safer option for now.

Thanks!
Jess

On Wed Oct 18 13:16:23 2017, gary.i...@huawei.com wrote:
> 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 ; 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-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' ;
> > 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]
> > Sent: Tuesday, October 17, 2017 11:40 PM
> > To: Gary Wu >;
> > 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://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=
> >  > 3A__nexus.onap.org=DwIGaQ=LFYZ-
> > o9_HUMeMTSQicvjIg=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-
> > q_w=0LmhWnkxvOPOium09mgc1rMdFYVDBpbW0cdM-
> >  2cR2nc=jEy3cAEf5jesxDTdRj2pmAHa_wFxEA55PMPl1DMpEK4= ,> in
> > repository autorelease-18453 (staging:
> > closed) > 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 

[onap-discuss] [ONAP Helpdesk #47177] SO build failing due to no appc client jars in the staging repo

[Jessica Wagantall via RT]

Dear Seshu, 

We are investigating the cause of these problems. For now, It looks like there 
are recent builds that are passing now due to a new appc daily job run that 
just happened this morning. 

Sorry for the inconvenience. 

Will re-trigger the latest so builds to make sure we are ok now that the appc 
binaries are back

Thanks!
Jess

On Wed Oct 18 02:51:07 2017, seshu.kuma...@huawei.com wrote:
> Dear LF
> 
> We are facing SO build failures due to appc client jar missing in the
> nexus staging repo.
> 
> [ERROR] Failed to execute goal on project MSOCommonBPMN: Could not
> resolve dependencies for project
> org.openecomp.so:MSOCommonBPMN:war:1.1.0-SNAPSHOT: The following
> artifacts could not be resolved: org.openecomp.appc.client:client-
> kit:jar:1.1.0, org.openecomp.appc.client:client-lib:jar:1.1.0: Could
> not find artifact org.openecomp.appc.client:client-kit:jar:1.1.0 in
> staging
> https://nexus.onap.org/content/repositories/staging/
> 
> 
> https://jenkins.onap.org/job/so-master-verify-profile-java/479/console
> https://jenkins.onap.org/job/so-master-verify-profile-java/480/console
> 
> I inspected the recent code merges made on and after 17 Oct and dint
> find any code merge that would ideally effect this.
> Please help us resolve this issue as this asap as this is blocking the
> entire ONAP integration test progress.
> 
> 
> Best regards
> Seshu Kumar M
> Huawei Technologies India Pvt, Ltd.
> 
> 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁
> 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中
> 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！
> This e-mail and its attachments contain confidential information from
> HUAWEI, which
> is intended only for the person or entity whose address is listed
> above. Any use of the
> information contained herein in any way (including, but not limited
> to, total or partial
> disclosure, reproduction, or dissemination) by persons other than the
> intended
> recipient(s) is prohibited. If you receive this e-mail in error,
> please notify the sender by
> phone or email immediately and delete it!
> 



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

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

[Jessica Wagantall via RT]

I have updated 2 more changes from repos that just got their sonar report in 
the server:

https://gerrit.onap.org/r/#/c/18845/
https://gerrit.onap.org/r/#/c/18847/

Can we please expedite their approval?

Thansk!
Jess

On Fri Oct 13 18:16:25 2017, jwagantall wrote:
> Taking care of 2 more
> 
> vfc/nfvo/driver/vnfm/svnfm/huawei and a new one that came just
> recently  oparent/odlparent-carbon
> 
> On Thu Oct 12 15:55:59 2017, jwagantall wrote:
> > Dear Gildas,
> >
> > I am going to close this ticket for now as it seems that we are
> > finally looking decent in Sonar.
> > If you still have any individual requests on any repos, please feel
> > free to let me know.
> >
> > Thanks!
> > Jess
> >
> > On Tue Sep 26 18:25:14 2017, gildas.lani...@huawei.com wrote:
> > > Thanks Jess.
> > >
> > >
> > >
> > > See my comments inline
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Gildas
> > >
> > > ONAP Release Manager
> > >
> > > 1 415 238 6287
> > >
> > >
> > >
> > > -Original Message-
> > > From: Jessica Wagantall via RT [mailto:onap-
> > > helpd...@rt.linuxfoundation.org]
> > > Sent: Tuesday, September 26, 2017 1:45 PM
> > > To: Gildas Lanilis <gildas.lani...@huawei.com>
> > > Cc: onap-discuss@lists.onap.org
> > > Subject: [ONAP Helpdesk #45515] Sonar naming convention
> > >
> > >
> > >
> > > Dear Gildas,
> > >
> > >
> > >
> > > Sorry that the more I dig, the more issues I find. [Gildas] yes not
> > > a
> > > surprise. Thanks for your attention on this. That will place ONAP
> > > in
> > > a
> > > cleaner place.
> > >
> > > Here is some work I did today:
> > >
> > >
> > >
> > > - DMaaP Bus Controller UI (parent) - the jobs have been removed
> > > (https://gerrit.onap.org/r/#/c/15607/), shall we remove this entry?
> > > [Gildas] Yes
> > >
> > > - Ecomp Portal SDK Project (parent) - Project has transitioned to
> > > portal/sdk which is fixed. Remove? [Gildas] yes
> > >
> > > - modeling/toscaparsers/nfvparser - Working with the dev
> > > https://gerrit.onap.org/r/#/c/13247/  [Gildas] The repo
> > > modeling/toscaparsers contains some Java and Python files. As
> > > python
> > > is not covered by LF I think for know we can name it modeling-
> > > toscaparsers
> > >
> > > - org/onap/vfc/nfvo/driver/ems/ems -
> > > https://gerrit.onap.org/r/#/c/15689/ [Gildas] merge it
> > >
> > > - vfc/nfvo/wfengine/activiti-extension and
> > > vfc/nfvo/wfengine/wfenginemgrservice -
> > > https://gerrit.onap.org/r/#/c/15677/1 [Gildas] merge it
> > >
> > > - SDC Distribution Client - https://gerrit.onap.org/r/#/c/15695/,
> > > https://gerrit.onap.org/r/#/c/15699/,
> > > https://gerrit.onap.org/r/#/c/15703/ [Gildas] merge them
> > >
> > > - SDNC Plugins - https://gerrit.onap.org/r/#/c/15711/ and
> > > https://gerrit.onap.org/r/#/c/15713/ [Gildas] merge them.
> > >
> > >
> > >
> > > Can you please help me pushing these merges please?
> > >
> > > Thanks!
> > >
> > > Jess
> > >
> > >



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