from:"Jessica Wagantall"

Team,

Services should be available now

Thanks!
Jess

On Tue, Nov 6, 2018 at 9:58 PM Lu, Lianhao  wrote:

> Hi Guys,
>
>
>
> Is https://nexus.onap.org/ down now? Because mvn can NOT download
> anything successfully during ‘mvn install’ now. I’m wondering if it’s a
> nexus.onap.org issue or my local network issue?
>
>
>
> Best Regards,
>
> -Lianhao
>

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

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

Re: [onap-discuss] Jenkins not reachable

Team,

seems like the services are coming back.
I am still keeping an eye on them

Thanks!
Jess

On Tue, Nov 6, 2018 at 9:08 PM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear ONAP team.
>
> Seems like there is an outage right now with our provider:
> https://status.linuxfoundation.org/incidents/5d50wx4t5v0v
>
> Please hold on for updates on this meanwhile this is under investigation
>
> Sorry for the inconvenience.
>
> Thanks!
> Jess
>

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

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

Re: [onap-discuss] ONAP nexus down?

Yes. Unfortunately some services are down
https://status.linuxfoundation.org/incidents/5d50wx4t5v0v

Our provider is looking into it.

thanks!
Jess

On Tue, Nov 6, 2018 at 10:00 PM Syed Atif Husain 
wrote:

> https://nexus3.onap.org is also down
>
>
>
> Regards,
>
> Atif
>
>
>
> *From:* onap-discuss@lists.onap.org  *On
> Behalf Of *Lianhao Lu
> *Sent:* Wednesday, November 7, 2018 11:28 AM
> *To:* onap-discuss@lists.onap.org
> *Cc:* jwagant...@linuxfoundation.org
> *Subject:* [onap-discuss] ONAP nexus down?
>
>
>
> Hi Guys,
>
>
>
> Is https://nexus.onap.org/
> 
> down now? Because mvn can NOT download anything successfully during ‘mvn
> install’ now. I’m wondering if it’s a nexus.onap.org issue or my local
> network issue?
>
>
>
> Best Regards,
>
> -Lianhao
>
> 
>

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

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

[onap-discuss] Jenkins not reachable

Dear ONAP team.

Seems like there is an outage right now with our provider:
https://status.linuxfoundation.org/incidents/5d50wx4t5v0v

Please hold on for updates on this meanwhile this is under investigation

Sorry for the inconvenience.

Thanks!
Jess

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

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

[onap-discuss] Debugging Gerrit reported downtimes

2018-10-25 Thread Jessica Wagantall

Dear ONAP team.

We noticed some slow downs today while trying to clone from gerrit.onap.org.
Our infra team was helping us debugging these and noticed a large amount of
fetches a day over https done from IP  71.205.221.97 (400k fetches a day).
This seems to be a Comcast IP.

I wanted to check around and see if anyone can help me locate the source of
these
requests that seem to be causing some slow downs.

If these tasks are really needed, we can always work something out like
allowing
for more parallel requests which I would need to check with the infra team
if this is something
we could possibly do. Also, we can see if these pulls can rather be done
using some
local cache rather.

Thanks so much for your help!
Jess

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

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

Re: [onap-discuss] Unstable Jenkins jobs

Looks like we are back to normal..

I am just re-running more jobs

Thanks!
Jess

On Mon, Oct 22, 2018 at 7:03 PM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear team
>
> I just wanted to let you know that I am still working on this..
>
> Sorry for the delays.
>
> Thanks!
> Jess
>
> On Mon, Oct 22, 2018 at 6:00 PM Jessica Wagantall <
> jwagant...@linuxfoundation.org> wrote:
>
>> Sorry for the delay.. Getting issues fetching the latest lftools.
>>
>> Looking for help from my team too..
>>
>> Thanks!
>> JEss
>>
>> On Mon, Oct 22, 2018 at 5:34 PM Jessica Wagantall <
>> jwagant...@linuxfoundation.org> wrote:
>>
>>> Change is up now..
>>>
>>> I am just quick checking it and will get someone to approve it for me
>>> https://gerrit.onap.org/r/#/c/71015/
>>>
>>> Thanks!
>>> Jess
>>>
>>> On Mon, Oct 22, 2018 at 4:53 PM Gary Wu  wrote:
>>>
>>>> Hi helpdesk,
>>>>
>>>> All the Jenkins jobs keep returning Unstable status.  Can you take a
>>>> look?
>>>>
>>>> Thanks,
>>>> Gary
>>>>
>>>>
>>>>
>>> 
>

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

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

Re: [onap-discuss] Unstable Jenkins jobs

Dear team

I just wanted to let you know that I am still working on this..

Sorry for the delays.

Thanks!
Jess

On Mon, Oct 22, 2018 at 6:00 PM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Sorry for the delay.. Getting issues fetching the latest lftools.
>
> Looking for help from my team too..
>
> Thanks!
> JEss
>
> On Mon, Oct 22, 2018 at 5:34 PM Jessica Wagantall <
> jwagant...@linuxfoundation.org> wrote:
>
>> Change is up now..
>>
>> I am just quick checking it and will get someone to approve it for me
>> https://gerrit.onap.org/r/#/c/71015/
>>
>> Thanks!
>> Jess
>>
>> On Mon, Oct 22, 2018 at 4:53 PM Gary Wu  wrote:
>>
>>> Hi helpdesk,
>>>
>>> All the Jenkins jobs keep returning Unstable status.  Can you take a
>>> look?
>>>
>>> Thanks,
>>> Gary
>>>
>>>
>>>
>> 
>

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

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

Re: [onap-discuss] Unstable Jenkins jobs

Sorry for the delay.. Getting issues fetching the latest lftools.

Looking for help from my team too..

Thanks!
JEss

On Mon, Oct 22, 2018 at 5:34 PM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Change is up now..
>
> I am just quick checking it and will get someone to approve it for me
> https://gerrit.onap.org/r/#/c/71015/
>
> Thanks!
> Jess
>
> On Mon, Oct 22, 2018 at 4:53 PM Gary Wu  wrote:
>
>> Hi helpdesk,
>>
>> All the Jenkins jobs keep returning Unstable status.  Can you take a look?
>>
>> Thanks,
>> Gary
>>
>>
>> 
>>
>

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

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

Re: [onap-discuss] Unstable Jenkins jobs

Change is up now..

I am just quick checking it and will get someone to approve it for me
https://gerrit.onap.org/r/#/c/71015/

Thanks!
Jess

On Mon, Oct 22, 2018 at 4:53 PM Gary Wu  wrote:

> Hi helpdesk,
>
> All the Jenkins jobs keep returning Unstable status.  Can you take a look?
>
> Thanks,
> Gary
>
>
> 
>

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

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

[onap-discuss] CLM job block refactoring

Dear ONAP team,

I have been working on re-writing out CLM job definitions under
ci-management/jjb/*

The idea is to isolate the CLM portion of the job similar to how we have it
for the
Sonar one. This is in preparation for two things:
- The new changes that we will be working in global-jjb to allow teams to
define an
  application name for each job so that the entry in IQ looks like
"onap-aai-aai-common"
  for example. As you know, The same IQ server is shared with many projects
so adding
  this prefix will help in cases where 2 projects have the same repo name.
This change will
  be easier to apply on an isolated job block.
- CLM works best when running in master. We have had cases where adding
several
  branches in CLM causes the reports to be overwritten since we do not have
control of
  which branch runs first, so the prevailing report will be from the last
branch that was ran on.
  If teams really desire to switch branches, they can still do so in the
CLM block but let's
  keep it running for just 1 branch at a time to avoid confusions with the
resulting reports.

You can find my work here:
https://gerrit.onap.org/r/#/q/topic:clm-project-refactor

I will be adding the PTLs to these changes and review them once more.
Please help me
reviewing and +1 the change if you agree with it.

Thank you AAI for having this all in place already :)

Thanks so much!
Jess

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

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

[onap-discuss] AWS JIRA rest environment available now

2018-09-28 Thread Jessica Wagantall

Dear ONAP team,

Ryan has helped us creating https://jira-new.onap.org/ which is a copy of
our JIRA but in an
AWS server. I will be working on testing this instance during the times
that most failures to generate reports occurred.

Could I please ask the teams to also give it a shot if you find
jira.onap.org having issues?

Please notice that this is a test environment for now and any changes into
jira-new.onap.org
will not be propagated into jira.onap.org.

Once we gather some examples of this test environment working better than
the production one,
we can do the switch to AWS.

Thanks a ton for your help as always!
Jess

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

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

Re: [onap-discuss] CSIT error

2018-09-27 Thread Jessica Wagantall

Thanks for your reply Jorge!

What could be the cause of docker-compose starting and stopping? Is this
being controlled via script? I wonder if we can make sure docker-compose is
running before executing these
tasks

Thanks!
Jess

On Thu, Sep 27, 2018 at 9:07 AM UNNAVA, SUNIL  wrote:

> Hi Jorge,
>
>
>
> Thanks for sharing your thoughts.  IP address of the Kafka and Zookeeper
> address are not changed from the first time( Otherwise MR container will
> not start), I can’t identify the IP address of the MR based on the log. We
> don’t see any issue in local and it is working with out any issues earlier.
>
>
>
>
>
> Jessica,
>
>
>
> Please let me know, when we can connect and debug the issue.
>
>
>
> Thanks,
>
> Sunil
>
>
>
> *From:* HERNANDEZ-HERRERO, JORGE
> *Sent:* Thursday, September 27, 2018 11:05 AM
> *To:* onap-discuss@lists.onap.org; UNNAVA, SUNIL 
> *Cc:* Gildas Lanilis ;
> jwagant...@linuxfoundation.org
> *Subject:* RE: CSIT error
>
>
>
> Hello Sunil,
>
>
>
> Giving it a shot ..  Errno 101 has to do with network  connectivity.   By
> looking at from looking at the logs  in
> https://jenkins.onap.org/view/dmaap/job/dmaap-master-csit-mrpubsub/405/console
> , I wonder since the logs show going through a couple docker-compose up
> and docker-compose down, the DMAAP_MR_IP is staled from the first time.
> See below .. Just an idea, in case it helps:
>
>
>
> *19:35:08* DMaaP Service Running
>
> *19:35:08* ++ break
>
> *19:35:08* +++ docker inspect '--format={{range
> .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' dockercompose_dmaap_1
>
> *19:35:09* ++ DMAAP_MR_IP=172.17.0.4
>
> *19:35:09* +++ docker inspect '--format={{range
> .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' dockercompose_kafka_1
>
> *19:35:09* ++ KAFKA_IP=172.17.0.3
>
> *19:35:09* +++ docker inspect '--format={{range
> .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' dockercompose_zookeeper_1
>
> *19:35:09* ++ ZOOKEEPER_IP=172.17.0.2
>
> *19:35:09* ++ echo DMAAP_MR_IP=172.17.0.4
>
> *19:35:09* DMAAP_MR_IP=172.17.0.4
>
> *19:35:09* ++ echo KAFKA_IP=172.17.0.3
>
> *19:35:09* KAFKA_IP=172.17.0.3
>
> *19:35:09* ++ echo ZOOKEEPER_IP=172.17.0.2
>
> *19:35:09* ZOOKEEPER_IP=172.17.0.2
>
> *19:35:09* ++ docker-compose down
>
> *19:35:10* [33mWARNING:[0m Dependency conflict: an older version of the
> 'docker-py' package may be polluting the namespace. If you're experiencing
> crashes, run the following command to remedy the issue:
>
> *19:35:10* pip uninstall docker-py; pip uninstall docker; pip install
> docker
>
> *19:35:10* Stopping dockercompose_dmaap_1 ...
>
> *19:35:10* Stopping dockercompose_kafka_1 ...
>
> *19:35:10* Stopping dockercompose_zookeeper_1 ...
>
>
>
>
>
> ..  The DMAAP_MR_IP may change .. 20 seconds later, I don’t see the
> variable updated in the logs, so may be stale, and explain the 101 errno ..
>
>
>
> *19:35:38* Creating network "dockercompose_default" with the default
> driver
>
> *19:35:38* Creating dockercompose_zookeeper_1 ...
>
> *19:35:38* Creating dockercompose_zookeeper_1
>
> *19:35:39* [1A[2K
>
> Creating dockercompose_zookeeper_1 ... [32mdone[0m
>
> [1BCreating dockercompose_kafka_1 ...
>
> *19:35:39* Creating dockercompose_kafka_1
>
> *19:35:39* [1A[2K
>
> Creating dockercompose_kafka_1 ... [32mdone[0m
>
> [1BCreating dockercompose_dmaap_1 ...
>
> *19:35:39* Creating dockercompose_dmaap_1
>
> *19:35:40* [1A[2K
>
> Creating dockercompose_dmaap_1 ... [32mdone[0m
>
> [1B++ for i in '{1..50}'
>
> *19:35:40* +++ docker inspect --format '{{ .State.Running }}'
> dockercompose_dmaap_1
>
> *19:35:40* ++ '[' true ']'
>
> *19:35:40* +++ docker inspect --format '{{ .State.Running }}'
> dockercompose_zookeeper_1
>
> *19:35:40* ++ '[' true ']'
>
> *19:35:40* +++ docker inspect --format '{{ .State.Running }}'
> dockercompose_dmaap_1
>
> *19:35:41* ++ '[' true ']'
>
> *19:35:41* ++ echo 'DMaaP Service Running'
>
> *19:35:41* DMaaP Service Running
>
> *19:35:41* ++ break
>
> *19:35:41* ++ for i in '{1..50}'
>
> *19:35:41* ++ curl -sS -m 1 172.17.0.4:3904/events/TestTopic
>
> *19:35:41* curl: (7) Failed to connect to 172.17.0.4 port 3904: Network
> is unreachable
>
> *19:35:41* ++ echo sleep 1
>
> *19:35:41* sleep 1
>
>
>
> Jorge
>
>
>
> *From:* onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org
> ] *On Behalf Of *UNNAVA, SUNIL
> *Sent:* Thursday, September 27, 2018 9:43 AM
> *To:* onap-discuss@lists.onap.org
> *Cc:* Gildas Lanilis ;
> jwagant...@linuxfoundation.org
> *Subject:* [onap-discuss] CSIT error
>
>
>
> Security Advisory:* This Message Originated Outside of AT ***
> Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
>
> Hi,
>
>
>
> We are facing some issues while running the CSIT job.  CSIT job is failing
> all of sudden with the following error. Is any one faced this issue before
> or any thoughts on the error.
>
>
>
> *19:57:39* Evaluating expression 
> 'requests.post('http://172.17.0.4:3904/events/TestTopic1 
>

[onap-discuss] [it-infrastructure-alerts] Gerrit and Jenkins unavailable Friday 1:00pm to 3:00pm PT time

2018-09-27 Thread Jessica Wagantall

What: The Linux Foundation will be performing a migration of Gerrit to AWS

When: Friday Sep 28 at 1:00pm Pacific

Why: Gerrit needs to be migrated to AWS. Moving to aws will improve
reliability and
scalability of gerrit system

Impact: Gerrit will be unavailable and Jenkins will need to be set to quiet
mode for 2:00 hrs

Thanks so much!
Jess

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

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

Re: [onap-discuss] Jenkins not processing builds

2018-09-26 Thread Jessica Wagantall

The queue is moving now..

This was caused by nodes which didn't got terminated properly and ended up
in zombie state.

Thanks!
Jess

On Wed, Sep 26, 2018 at 8:40 AM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear team,
>
> I am taking care of this now.
>
> Sorry for the inconvenience
>
> Thanks!
> Jess
>

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

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

[onap-discuss] Jenkins not processing builds

2018-09-26 Thread Jessica Wagantall

Dear team,

I am taking care of this now.

Sorry for the inconvenience

Thanks!
Jess

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

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

Re: [onap-discuss] Jenkins access issues being investigated

2018-09-21 Thread Jessica Wagantall

Should be all good now.

Thanks!
Jess

On Fri, Sep 21, 2018 at 10:36 AM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear team,
>
> If you are facing issues login into Jenkins servers, our infra team is
> already looking into this and should be resolved soon
>
> Thanks!
> Jess
>

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

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

[onap-discuss] Jenkins access issues being investigated

2018-09-21 Thread Jessica Wagantall

Dear team,

If you are facing issues login into Jenkins servers, our infra team is
already looking into this and should be resolved soon

Thanks!
Jess

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

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

[onap-discuss] mvn35 is available in Jenkins

2018-09-19 Thread Jessica Wagantall

Dear ONAP team,

This is just to let you know that Maven 3.5.4 is available in Jenkins and
teams
can move into this version if they do not want to use mvn33.

Here is an example on how to input this change into your project's yaml
file in ci-management:
https://github.com/onap/ci-management/blob/master/jjb/sdc/sdc.yaml

By default, all jobs assume mvn33 unless this variable is overwritten like
in the example.

Thanks a ton!
Jess

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

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

[onap-discuss] Regarding tag in the project's pom.xml

2018-09-05 Thread Jessica Wagantall

Dear ONAP teams,

This is a small reminder that the  tag in the pom.xml for your
projects needs
to match the name of the repo. This tag helps writing the correct name in
the Sonar report.

Changing this name multiple times will cause Sonar to have old entries in
the reports and
we have to manually remove them.

Let's please make sure these are matching the names. For example:
https://gerrit.onap.org/r/#/c/64887/

Thanks so much!
Jess

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

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

Re: [onap-discuss] License issues with Nexus IQ

2018-08-22 Thread Jessica Wagantall

Dear team,

Just to let you know that Andy, Thanh and myself are still in communication
and working with Sonatype
on this to get to a resolution.

Thanks so much for your patience.

Thanks!
Jess

On Mon, Aug 20, 2018 at 3:54 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear ONAP team,
>
> I know few of you have reported license issues in Nexus IQ like this one:
>
> https://jira.onap.org/secure/attachment/12154/Screenshot%202
> 018-08-20%2010.36.53.png
>
> I have contacted Sonatype Support to verify our product license since this
> seems to
> be related directly to it. Currently I am still in email exchanges with
> them waiting to help me
> out with a resolution.
>
> Will let you know once I get an update from them.
>
> Thanks a lot for your patience.
> Jess
>

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

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

[onap-discuss] License issues with Nexus IQ

2018-08-20 Thread Jessica Wagantall

Dear ONAP team,

I know few of you have reported license issues in Nexus IQ like this one:

https://jira.onap.org/secure/attachment/12154/Screenshot%202
018-08-20%2010.36.53.png

I have contacted Sonatype Support to verify our product license since this
seems to
be related directly to it. Currently I am still in email exchanges with
them waiting to help me
out with a resolution.

Will let you know once I get an update from them.

Thanks a lot for your patience.
Jess

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

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

[onap-discuss] Nexus IQ related question

2018-08-06 Thread Jessica Wagantall

Dear ONAP team,

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

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

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

Thanks!
Jess

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

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

Re: [onap-discuss] [ONAP Helpdesk #58617] CLM jobs missing Nexus IQ configuration

2018-08-06 Thread Jessica Wagantall

Hi Pam,

We are not making any changes to the credentials as far as any work done to
upgrade this plugin.

Can you please show me which link is giving you the login failure? Are you
able to login and see no
content, or are you not able to login at all?

I need to check if this plugin upgrade touched anything related to
permissions.

Are you able to see the report by clicking on the Jenkins link "Latest
Application Composition Report"?

Thanks!
Jess

On Fri, Aug 3, 2018 at 8:47 AM, Pamela Dragosh 
wrote:

> Thanks Jess,
>
> I was able to re-run them. Yesterday and this morning I was able to login
> and view the reports.
>
> But now for some reason LDAP authentication is failing. Can someone check
> to see what is going on? Maybe you guys are making changes still??
>
> Thanks,
>
> Pam
>
>
> On 8/1/18, 8:27 PM, "Jessica Wagantall via RT"  linuxfoundation.org> wrote:
>
> These CLM templates are now running again!
>
> Please feel free to try your jobs using the "run-clm" comment in
> Gerrit.
>
> Thanks!
> Jess
>
>
> On Mon Jul 23 14:28:37 2018, jwagantall wrote:
> > Dear Pam,
> >
> > I sent an email about this last week.
> > Unfortunately these plugins are deprecated and we are working on the
> > configuring the new ones for
> > JJB and re-code our CLM job:
> >
> > This is my email I sent:
> >
> > 
> >
> > I wanted to inform you that after upgrading Jenkins due to a high
> > priority security patch, some
> > plugins became deprecated. Including IQ and CLM Nexus plugins.
> >
> > This is due to one of the security patches closing off an API that
> > those plugins were depending on:
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__
> jenkins.io_blog_2018_03_15_jep-2D200-2Dlts_=DwIDaQ=
> LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7r
> C07xpgpVZkS_4=96Bc1k_3iM0oj6iIg3pHPLg7zV1VFjiM9y5IwOAqVWE=
> CVoNLkzJtZNh4I9xpHeeyK8iwsIM_xxzGstuP5rD42w=
> >
> > On the other hand according to Sonatype's download page for the
> > plugins they are both deprecated plugins and they no longer recommend
> > installing it:
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__help.
> sonatype.com_iqserver_download-2Dand-2Dcompatibility=DwIDaQ=
> LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7r
> C07xpgpVZkS_4=96Bc1k_3iM0oj6iIg3pHPLg7zV1VFjiM9y5IwOAqVWE=
> 26d8T531m1w2Zyb8LwiRNuo0s4yEliJQcsZ53TovA7E=
> >
> > We are working on installing Nexus Platform plugin 3.x but it seems
> > that there is no way to migrate
> > our CLM jobs into the new plugin. We are working on changing global-
> > jjb to adapt to this new
> > configuration, but we need to update also upstream JJB to add the
> > support.
> >
> > I will let you know more details on this work and hopefully get us
> > going soon.
> >
> > The reports are still available via https://urldefense.proofpoint.
> com/v2/url?u=https-3A__nexus-2D=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=
> jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=96Bc1k_
> 3iM0oj6iIg3pHPLg7zV1VFjiM9y5IwOAqVWE=xxbxiUJ_
> p9h83EE8i7hjBozLqB8QameiNgbsB3p2TDs=
> > iq.wl.linuxfoundation.org/assets/index.html#/reports/violations
> >
> > --
> >
> > Thanks!
> > Jess
> > On Mon Jul 23 08:03:59 2018, pdrag...@research.att.com wrote:
> > > Hi,
> > >
> > > All of the ONAP CLM jobs failed over the weekend due to nexus IQ
> > > server address has not been configured:
> > >
> > > 08:42:25 [INFO] BUILD SUCCESS
> > > 08:42:25 [INFO]
> > > 
> 
> > > 08:42:25 [INFO] Total time: 12:47 min
> > > 08:42:25 [INFO] Finished at: 2018-07-21T08:42:25Z
> > > 08:42:25 [INFO]
> > > 
> 
> > > 08:42:31 [policy-engine-maven-clm-master] $ /bin/bash
> > > /tmp/jenkins8728067635506742314.sh
> > > 08:42:41 [policy-engine-maven-clm-master] $ /bin/sh -xe
> > > /tmp/jenkins7691417530010630761.sh
> > > 08:42:41 + find . -regex .*karaf/target
> > > 08:42:41 + xargs rm -rf
> > > 08:42:43 ERROR: Build step failed with exception
> > > 08:42:43 java.lang.IllegalArgumentException: Nexus IQ Server
&g

Re: [onap-discuss] Jenkins not processing builds

2018-07-23 Thread Jessica Wagantall

Working still with our provider.

Seems like some instances are not able to be removed and we are checking
with them now.

Thanks!
Jess

On Mon, Jul 23, 2018 at 11:12 AM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear Team,
>
> Just to let you know I am still working on this.
>
> Some executors seemed to be stuck but I am working through those.
>
> thanks!
> Jess
>

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

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

[onap-discuss] Jenkins not processing builds

2018-07-23 Thread Jessica Wagantall

Dear Team,

Just to let you know I am still working on this.

Some executors seemed to be stuck but I am working through those.

thanks!
Jess

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

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

[onap-discuss] Jenkins builds stuck

2018-07-12 Thread Jessica Wagantall

Dear ONAP team,

We noticed some jobs are getting stuck in the Jenkins queue.
This is getting fixed as we speak by upgrading to the last version of
global-jjb

Thanks a ton for your patience.

Thanks!
Jess

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

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

Re: [onap-discuss] Jenkins having trigger issues

2018-07-11 Thread Jessica Wagantall

This looks to be better now

Thanks!
Jess

On Wed, Jul 11, 2018 at 5:58 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Performing a quick restart now.
>
> Looks like Jenkins triggers are not responding.
>
> Thanks for your patience
>
> Thanks!
> Jess
>

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

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

[onap-discuss] Jenkins having trigger issues

2018-07-11 Thread Jessica Wagantall

Performing a quick restart now.

Looks like Jenkins triggers are not responding.

Thanks for your patience

Thanks!
Jess

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

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

2018-07-05 Thread 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

2018-07-05 Thread 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

2018-07-03 Thread 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]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] Jenkins being restarted today 9:00 am PT

2018-07-02 Thread Jessica Wagantall

This is now completed and working better.

Thanks!
Jess

On Mon, Jul 2, 2018 at 7:48 AM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> What: The Linux Foundation will be performing a Jenkins restart. Jenkins
> will be set to QuietDown
> mode previous to this time.
>
> When: Monday July 02 at 9am Pacific
>
> Why: Need to upgrade OpenStack Cloud plugin to fetch security issues.
> Previously v2.36 had a bug
>  where no new builds were processed. v2.37 has just been released.
>
> Impact: Jenkins will be set to QuietDown mode before this time. The
> restart should take couple of
>  minutes
>
>

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

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

[onap-discuss] Jenkins being restarted today 9:00 am PT

2018-07-02 Thread Jessica Wagantall

What: The Linux Foundation will be performing a Jenkins restart. Jenkins
will be set to QuietDown
mode previous to this time.

When: Monday July 02 at 9am Pacific

Why: Need to upgrade OpenStack Cloud plugin to fetch security issues.
Previously v2.36 had a bug
 where no new builds were processed. v2.37 has just been released.

Impact: Jenkins will be set to QuietDown mode before this time. The restart
should take couple of
 minutes

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

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

2018-06-29 Thread 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

2018-06-27 Thread 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]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] Issues pulling images from docker.io through our Nexus3 proxy.

2018-06-27 Thread Jessica Wagantall

Team,

Can we please give it a shot now again to your images?

>From my tests 5 out of 5 pulls succeeded. Not like before when I had to
re-try up to 3 times.

I will go through the RTs and tackle them individually.

Please expect my reply on them.

Thanks!
Jess

On Wed, Jun 27, 2018 at 2:59 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear team,
>
> I wanted to let you know that I am still investigating these issues.
>
> In my case (in my local machine) running the same pull requests sometimes
> succeeds
> and sometimes it fails to find the proper manifest.
>
> Nothing in our environment has changed, but I am looking through the logs
> to see if I can catch
> something happening.
>
> Sorry for the inconvenience, I'll continue working on this.
>
> Thanks!
> Jess
> 
>
>

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

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

[onap-discuss] Issues pulling images from docker.io through our Nexus3 proxy.

2018-06-27 Thread Jessica Wagantall

Dear team,

I wanted to let you know that I am still investigating these issues.

In my case (in my local machine) running the same pull requests sometimes
succeeds
and sometimes it fails to find the proper manifest.

Nothing in our environment has changed, but I am looking through the logs
to see if I can catch
something happening.

Sorry for the inconvenience, I'll continue working on this.

Thanks!
Jess

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

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

2018-06-27 Thread 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

2018-06-27 Thread 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<https://www.amdocs.com/open-
> 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<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>




-=-=-=-=-=-=-=-=-=-=-=-
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]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [onap-discuss] [it-infrastructure-alerts] Brief Jenkins restart

2018-06-25 Thread Jessica Wagantall

This is now completed

Thanks!
Jess

On Mon, Jun 25, 2018 at 2:21 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear ONAP team,
>
> We are going to perform a brief Jenkins restart now that the workload is
> not heavy.
>
> This is to install the newest OpenStack Cloud Plugin in Jenkins to fetch a
> new security patch.
>
> Thanks so much!
> Jess
>

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

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

[onap-discuss] [it-infrastructure-alerts] Brief Jenkins restart

2018-06-25 Thread Jessica Wagantall

Dear ONAP team,

We are going to perform a brief Jenkins restart now that the workload is
not heavy.

This is to install the newest OpenStack Cloud Plugin in Jenkins to fetch a
new security patch.

Thanks so much!
Jess

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

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

Re: [onap-discuss] [it-infrastructure-alerts] JIRA security maintainance. Saturday June 16 at 8am Pacific (3pm UTC)

2018-06-16 Thread Jessica Wagantall

This is now completed

Thanks
Jess

On Sat, Jun 16, 2018, 7:51 AM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear team
>
> This maintainance is about to start
>
> Thanks
> Jess
>
> On Fri, Jun 15, 2018, 12:39 PM Jessica Wagantall <
> jwagant...@linuxfoundation.org> wrote:
>
>> Dear team,
>>
>> This is just a small reminder of this upcoming maintenance.
>>
>> Thanks!
>> Jess
>>
>> On Wed, Jun 13, 2018 at 2:42 PM, Jessica Wagantall <
>> jwagant...@linuxfoundation.org> wrote:
>>
>>> What: The Linux Foundation will be performing a JIRA security upgrade
>>>
>>> When: Saturday June 16 at 8am Pacific (3pm UTC)
>>>
>>> Why:The bundled Atlassian OAuth plugin allows arbitrary HTTP requests to
>>> be proxied
>>> CVE-2017-9506 (https://jira.atlassian.com/browse/JRASERVER-65862)
>>>
>>> Impact: Jira will be unavailable for 1 hour
>>>
>>> Notices will be posted to the mailing lists at the start and end of the
>>> maintenance.
>>>
>>
>>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [it-infrastructure-alerts] JIRA security maintainance. Saturday June 16 at 8am Pacific (3pm UTC)

2018-06-16 Thread Jessica Wagantall

Dear team

This maintainance is about to start

Thanks
Jess

On Fri, Jun 15, 2018, 12:39 PM Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear team,
>
> This is just a small reminder of this upcoming maintenance.
>
> Thanks!
> Jess
>
> On Wed, Jun 13, 2018 at 2:42 PM, Jessica Wagantall <
> jwagant...@linuxfoundation.org> wrote:
>
>> What: The Linux Foundation will be performing a JIRA security upgrade
>>
>> When: Saturday June 16 at 8am Pacific (3pm UTC)
>>
>> Why:The bundled Atlassian OAuth plugin allows arbitrary HTTP requests to
>> be proxied
>> CVE-2017-9506 (https://jira.atlassian.com/browse/JRASERVER-65862)
>>
>> Impact: Jira will be unavailable for 1 hour
>>
>> Notices will be posted to the mailing lists at the start and end of the
>> maintenance.
>>
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [it-infrastructure-alerts] JIRA security maintainance. Saturday June 16 at 8am Pacific (3pm UTC)

2018-06-15 Thread Jessica Wagantall

Dear team,

This is just a small reminder of this upcoming maintenance.

Thanks!
Jess

On Wed, Jun 13, 2018 at 2:42 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> What: The Linux Foundation will be performing a JIRA security upgrade
>
> When: Saturday June 16 at 8am Pacific (3pm UTC)
>
> Why:The bundled Atlassian OAuth plugin allows arbitrary HTTP requests to
> be proxied
> CVE-2017-9506 (https://jira.atlassian.com/browse/JRASERVER-65862)
>
> Impact: Jira will be unavailable for 1 hour
>
> Notices will be posted to the mailing lists at the start and end of the
> maintenance.
>
___
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

2018-06-14 Thread 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

2018-06-14 Thread 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] Re-applying "Non-Author-Code-Review" rule in Gerrit

2018-06-14 Thread Jessica Wagantall

Dear ONAP team.

As agreed on the TSC meeting 05/24, I am re-applying
the "Non-Author-Code-Review" Gerrit rule
now.

For more information on this discussion, please refer to the TSC minutes
here:
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2018/onap-meeting.2018-05-24-13.52.html

If you would like more details on this rule's implementation, please refer
to:
https://git.eclipse.org/r/Documentation/prolog-cookbook.html#NonAuthorCodeReview

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

[onap-discuss] [it-infrastructure-alerts] JIRA security maintainance. Saturday June 16 at 8am Pacific (3pm UTC)

2018-06-13 Thread Jessica Wagantall

What: The Linux Foundation will be performing a JIRA security upgrade

When: Saturday June 16 at 8am Pacific (3pm UTC)

Why:The bundled Atlassian OAuth plugin allows arbitrary HTTP requests to be
proxied
CVE-2017-9506 (https://jira.atlassian.com/browse/JRASERVER-65862)

Impact: Jira will be unavailable for 1 hour

Notices will be posted to the mailing lists at the start and end of the
maintenance.
___
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

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

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

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

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

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] Jira Federation being implemented

2018-06-08 Thread Jessica Wagantall

Dear ONAP team,

As discussed on May 24th TSC meeting (
https://wiki.onap.org/display/DW/TSC+2018-05-24), we
will go ahead and implement the cross JIRA capabilities for jira.onap.org.

Please let me know if there are any concerns about this.
Thanks so much!
Jess
___
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

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

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

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

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

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

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

2018-06-05 Thread 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<https://nexus.onap.org/service/local/repositories/snapshots/content/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/content/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 ***
> 
> - 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<https://git.onap.org/integration/tree/version-
> manifest/src/main/resources/docker-manifest.csv?h=beijing> (In Beijing
> Branch) should not c

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

2018-06-05 Thread 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<https://nexus.onap.org/service/local/repositories/snapshots/content/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/content/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 ***
> 
> - 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<https://git.onap.org/integration/tree/version-
> manifest/src/main/resources/docker-manifest.csv?h=beijing> (In Beijing
> Branch) should not c

Re: [onap-discuss] Beijing Release: Last Mile

2018-06-05 Thread Jessica Wagantall

*No request received yet also from the modeling team.*

Thanks!
Jess

On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall <
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 <
> 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 
>>
>> - 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 > > 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/
>>> <https://jenkins.onap.org/view/oparent/job/oparent-master-release-version-java-daily/124/>*).
>>> Ultimately, the Docker manifest file
>>> <https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv?h=beijing>
>>> (In Beijing Branch) should not contain words such as “latest”, “SNAPSHOT”
>>> or “STAGING” but only version number. If necessary, also update the Java
>>> manifest file. All the release process is documented in wiki
>>> <https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process>
>>> .
>>>
>>> 2.   *Release Notes*: I have updated for most projects the
>>> “Security Notes” within each Release Notes. Thanks to review and merge its
>>> content (feel free to amend to fix typo, if any). Also, it is not necessary
>>> to list in the Release Notes all issues fixed into Beijing Release, but
>>> only the main one that were visible in Amsterdam externally to users. Same
>>> approach for “New Features”, it is not necessary to list all Jira Stories
>>> implemented in Beijing, but rather focus on describing the 3-4 main
>>> features of your project. Last, Release Notes are cumulative (all release
>>> notes go in a single file); information for Beiji

Re: [onap-discuss] Beijing Release: Last Mile

2018-06-05 Thread Jessica Wagantall

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 <
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 
>
> - 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 
> 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/
>> <https://jenkins.onap.org/view/oparent/job/oparent-master-release-version-java-daily/124/>*).
>> Ultimately, the Docker manifest file
>> <https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv?h=beijing>
>> (In Beijing Branch) should not contain words such as “latest”, “SNAPSHOT”
>> or “STAGING” but only version number. If necessary, also update the Java
>> manifest file. All the release process is documented in wiki
>> <https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process>
>> .
>>
>> 2.   *Release Notes*: I have updated for most projects the “Security
>> Notes” within each Release Notes. Thanks to review and merge its content
>> (feel free to amend to fix typo, if any). Also, it is not necessary to list
>> in the Release Notes all issues fixed into Beijing Release, but only the
>> main one that were visible in Amsterdam externally to users. Same approach
>> for “New Features”, it is not necessary to list all Jira Stories
>> implemented in Beijing, but rather focus on describing the 3-4 main
>> features of your project. Last, Release Notes are cumulative (all release
>> notes go in a single file); information for Beijing Release goes on the top
>> of the file.
>>
>> 3.   *Release Sign-Off Template*: The Release Sign-Off template is
>> available in wiki
>> <https://wiki.onap.org/display/DW/Deliverables+for+Release+Sign-Off+Milestone+Checklist+Template>.
>> Please fill it out and keep me posted on its availability so I can review.
>>
>> Let me know if you have question, I will be glad to help.
>>
>> Thanks,
>>
>> Gildas
>>
>>
>>
>> *[image: HuaweiLogowithName]*
>>
>> *Gildas Lanilis*
>>
>> *ONAP Release Manager*
>>
>> *Santa Clara CA, USA*
>>
>> *gildas.lani...@huawei.com *
>>
>> *Mobile: 1 415 238 6287*
>>
>>
>>
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Beijing Release: Last Mile

2018-06-04 Thread Jessica Wagantall

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

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 
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
> 
> (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 content
> (feel free to amend to fix typo, if any). Also, it is not necessary to list
> in the Release Notes all issues fixed into Beijing Release, but only the
> main one that were visible in Amsterdam externally to users. Same approach
> for “New Features”, it is not necessary to list all Jira Stories
> implemented in Beijing, but rather focus on describing the 3-4 main
> features of your project. Last, Release Notes are cumulative (all release
> notes go in a single file); information for Beijing Release goes on the top
> of the file.
>
> 3.   *Release Sign-Off Template*: The Release Sign-Off template is
> available in wiki
> .
> Please fill it out and keep me posted on its availability so I can review.
>
> Let me know if you have question, I will be glad to help.
>
> Thanks,
>
> Gildas
>
>
>
> *[image: 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 #55393] [LOG] New repo request for logging-analytics - add new java and python child repos

2018-05-31 Thread 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

2018-05-25 Thread 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

2018-05-25 Thread 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

2018-05-24 Thread 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

2018-05-24 Thread 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

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

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

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

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

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

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

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

2018-05-16 Thread 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] Sonar issues with Maven 35 resolved

2018-05-15 Thread Jessica Wagantall

Dear team,

I got few reports of sonar jobs failing recently.

The cause was the new maven 35 installation was missing in Jenkins
which has now been added in the Global Tool configuration.

Please feel free to trigger your sonar jobs using "run-sonar" comment
in Gerrit. This job should be back in good shape again.

Thanks a ton!
Jess
___
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

2018-05-15 Thread 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

Re: [onap-discuss] Nexus 3 images "disappearing" from the server

Gary,

Can I get your opinion on this?
Looking at dmaap, it seems that this project is using 2 daily templates at
the same time:
[image: Success] [image: 100%]
<https://jenkins.onap.org/view/dmaap/job/dmaap-messagerouter-docker-master-docker-java-daily/lastBuild>
dmaap-messagerouter-docker-master-docker-java-daily
<https://jenkins.onap.org/view/dmaap/job/dmaap-messagerouter-docker-master-docker-java-daily/>
12
hr - #266
<https://jenkins.onap.org/view/dmaap/job/dmaap-messagerouter-docker-master-docker-java-daily/lastSuccessfulBuild/>
N/A 8 min 34 sec
[image: Success] [image: 100%]
<https://jenkins.onap.org/view/dmaap/job/dmaap-messagerouter-docker-master-docker-version-java-daily/lastBuild>
dmaap-messagerouter-docker-master-docker-version-java-daily
<https://jenkins.onap.org/view/dmaap/job/dmaap-messagerouter-docker-master-docker-version-java-daily/>
12
hr - #267
<https://jenkins.onap.org/view/dmaap/job/dmaap-messagerouter-docker-master-docker-version-java-daily/lastSuccessfulBuild/>
N/A 9 min 48 sec

Both seemed to update a latest tag. I am not saying this is the cause, but
it is definitely not right thing to do. Right?

thanks!
Jess

On Fri, May 11, 2018 at 5:49 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Hi Gary,
>
> Just a small observation,
> onap/cli: 2.0.0-SNAPSHOT-20180425T130053Z
> seems like it will be removed in 45 mins.
>
> We have a task that runs every day at 6:30 PT that removes old SNAPSHOTS
> older than 16 days.
>
> I am looking further into your particular case.
>
> Thanks!
> Jess
>
> On Fri, May 11, 2018 at 5:43 PM, Jessica Wagantall <
> jwagant...@linuxfoundation.org> wrote:
>
>> Dear Michal,
>>
>> In your case, which is the Jenkins job that needs these versions:
>> policy_handler: nexus3.onap.org:10001/onap/org.onap.dcaegen2
>> .platform.policy-handler:2.4.1
>> service_change_handler: nexus3.onap.org:10001/onap/org.onap.
>> dcaegen2.platform.servicechange-handler:1.1.3
>>
>> I think in your particular case this could be a need for these versions
>> to be released and that just hasn't been requested.
>>
>> I can see these binary versions tagged as "...SNAPSHOT.." but they
>> haven't been pushed into the releases
>> repository because no one have requested them
>>
>> Let me know if my info is helpful
>>
>> thanks!
>> Jess
>>
>> On Fri, May 11, 2018 at 2:11 PM, Jessica Wagantall <
>> jwagant...@linuxfoundation.org> wrote:
>>
>>> Thanks Gary,
>>>
>>> I have updated it since a bit ago and been using it without an issue.
>>>
>>> Gildas, can we propose to the TSC this upgrade please?
>>>
>>> It is something we can easily try with about 1 min of downtime while the
>>> server restarts with the new version.
>>>
>>> Thanks!
>>> Jess
>>>
>>> On Fri, May 11, 2018 at 1:37 PM, Gary Wu <gary.i...@huawei.com> wrote:
>>>
>>>> Sounds reasonable, except that I’m no longer actively using nexus3ap,
>>>> and may not be able to give much feedback on how well it’s working.
>>>>
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Gary
>>>>
>>>>
>>>>
>>>> *From:* Jessica Wagantall [mailto:jwagant...@linuxfoundation.org]
>>>> *Sent:* Friday, May 11, 2018 1:27 PM
>>>> *To:* m.pta...@partner.samsung.com
>>>> *Cc:* Gary Wu <gary.i...@huawei.com>; onap-discuss@lists.onap.org;
>>>> onap-release <onap-rele...@lists.onap.org>; Gildas Lanilis <
>>>> gildas.lani...@huawei.com>; Jeremy Phelps <jphe...@linuxfoundation.org>;
>>>> Kenny Paul <kp...@linuxfoundation.org>; Anil Belur <
>>>> abe...@linuxfoundation.org>
>>>> *Subject:* Re: Re: [onap-discuss] Nexus 3 images "disappearing" from
>>>> the server
>>>>
>>>>
>>>>
>>>> Thanks for your inputs Michael and Gary,
>>>>
>>>>
>>>>
>>>> Gary, the case you mention makes me wonder if this is a tag problem or
>>>> the way binaries are being tagged every day.
>>>>
>>>> I was chatting with Andy and he mentioned to me that in general Nexus3
>>>> reports so many docker issues.
>>>>
>>>>
>>>>
>>>> We confirmed this is not relates to a disk capacity issues since we
>>>> have still about 3TB of free space.
>>>>
>>>>
>>>>
>>>> I am trying something now which

Re: [onap-discuss] Nexus 3 images "disappearing" from the server

Hi Gary,

Just a small observation,
onap/cli: 2.0.0-SNAPSHOT-20180425T130053Z
seems like it will be removed in 45 mins.

We have a task that runs every day at 6:30 PT that removes old SNAPSHOTS
older than 16 days.

I am looking further into your particular case.

Thanks!
Jess

On Fri, May 11, 2018 at 5:43 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear Michal,
>
> In your case, which is the Jenkins job that needs these versions:
> policy_handler: nexus3.onap.org:10001/onap/org.onap.
> dcaegen2.platform.policy-handler:2.4.1
> service_change_handler: nexus3.onap.org:10001/onap/org.onap.
> dcaegen2.platform.servicechange-handler:1.1.3
>
> I think in your particular case this could be a need for these versions to
> be released and that just hasn't been requested.
>
> I can see these binary versions tagged as "...SNAPSHOT.." but they haven't
> been pushed into the releases
> repository because no one have requested them
>
> Let me know if my info is helpful
>
> thanks!
> Jess
>
> On Fri, May 11, 2018 at 2:11 PM, Jessica Wagantall <
> jwagant...@linuxfoundation.org> wrote:
>
>> Thanks Gary,
>>
>> I have updated it since a bit ago and been using it without an issue.
>>
>> Gildas, can we propose to the TSC this upgrade please?
>>
>> It is something we can easily try with about 1 min of downtime while the
>> server restarts with the new version.
>>
>> Thanks!
>> Jess
>>
>> On Fri, May 11, 2018 at 1:37 PM, Gary Wu <gary.i...@huawei.com> wrote:
>>
>>> Sounds reasonable, except that I’m no longer actively using nexus3ap,
>>> and may not be able to give much feedback on how well it’s working.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Gary
>>>
>>>
>>>
>>> *From:* Jessica Wagantall [mailto:jwagant...@linuxfoundation.org]
>>> *Sent:* Friday, May 11, 2018 1:27 PM
>>> *To:* m.pta...@partner.samsung.com
>>> *Cc:* Gary Wu <gary.i...@huawei.com>; onap-discuss@lists.onap.org;
>>> onap-release <onap-rele...@lists.onap.org>; Gildas Lanilis <
>>> gildas.lani...@huawei.com>; Jeremy Phelps <jphe...@linuxfoundation.org>;
>>> Kenny Paul <kp...@linuxfoundation.org>; Anil Belur <
>>> abe...@linuxfoundation.org>
>>> *Subject:* Re: Re: [onap-discuss] Nexus 3 images "disappearing" from
>>> the server
>>>
>>>
>>>
>>> Thanks for your inputs Michael and Gary,
>>>
>>>
>>>
>>> Gary, the case you mention makes me wonder if this is a tag problem or
>>> the way binaries are being tagged every day.
>>>
>>> I was chatting with Andy and he mentioned to me that in general Nexus3
>>> reports so many docker issues.
>>>
>>>
>>>
>>> We confirmed this is not relates to a disk capacity issues since we have
>>> still about 3TB of free space.
>>>
>>>
>>>
>>> I am trying something now which I don't guarantee might fix our issue,
>>> but we could give it a shot at least.
>>>
>>> I have upgraded https://nexus3ap.onap.org/ to version 3.11.0 and see
>>> how it behaves.
>>>
>>> If everything goes fine and that version is stable, we should upgrade
>>> nexus3.onap.org too so that we are at least
>>>
>>> on the latest version.
>>>
>>>
>>>
>>> Can I get your thoughts on this?
>>>
>>>
>>>
>>> Thanks!
>>>
>>> Jess
>>>
>>>
>>>
>>> On Thu, May 10, 2018 at 11:44 PM, Michal Ptacek <
>>> m.pta...@partner.samsung.com> wrote:
>>>
>>> Hi,
>>>
>>>
>>>
>>> not sure if it relates but OOM currently needs for dcae2gen following
>>> images
>>>
>>>
>>>
>>> policy_handler: nexus3.onap.org:10001/onap/org
>>> .onap.dcaegen2.platform.policy-handler:2.4.1
>>> service_change_handler: nexus3.onap.org:10001/onap/org
>>> .onap.dcaegen2.platform.servicechange-handler:1.1.3
>>>
>>>
>>>
>>> both of them are currently NOT available on nexus, the question is
>>> whether it relates to this problem
>>>
>>>
>>>
>>> Should we just simply start using newer images (fix in OOM ?)
>>>
>>> I don't know if I can propose that as I am not from DCAE team ...
>>>
>>>
>>>
>>> thanks,
>>>
>>> Michal
>>&

Re: [onap-discuss] Nexus 3 images "disappearing" from the server

Dear Michal,

In your case, which is the Jenkins job that needs these versions:
policy_handler: nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.
policy-handler:2.4.1
service_change_handler: nexus3.onap.org:10001/onap/
org.onap.dcaegen2.platform.servicechange-handler:1.1.3

I think in your particular case this could be a need for these versions to
be released and that just hasn't been requested.

I can see these binary versions tagged as "...SNAPSHOT.." but they haven't
been pushed into the releases
repository because no one have requested them

Let me know if my info is helpful

thanks!
Jess

On Fri, May 11, 2018 at 2:11 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Thanks Gary,
>
> I have updated it since a bit ago and been using it without an issue.
>
> Gildas, can we propose to the TSC this upgrade please?
>
> It is something we can easily try with about 1 min of downtime while the
> server restarts with the new version.
>
> Thanks!
> Jess
>
> On Fri, May 11, 2018 at 1:37 PM, Gary Wu <gary.i...@huawei.com> wrote:
>
>> Sounds reasonable, except that I’m no longer actively using nexus3ap, and
>> may not be able to give much feedback on how well it’s working.
>>
>>
>>
>> Thanks,
>>
>> Gary
>>
>>
>>
>> *From:* Jessica Wagantall [mailto:jwagant...@linuxfoundation.org]
>> *Sent:* Friday, May 11, 2018 1:27 PM
>> *To:* m.pta...@partner.samsung.com
>> *Cc:* Gary Wu <gary.i...@huawei.com>; onap-discuss@lists.onap.org;
>> onap-release <onap-rele...@lists.onap.org>; Gildas Lanilis <
>> gildas.lani...@huawei.com>; Jeremy Phelps <jphe...@linuxfoundation.org>;
>> Kenny Paul <kp...@linuxfoundation.org>; Anil Belur <
>> abe...@linuxfoundation.org>
>> *Subject:* Re: Re: [onap-discuss] Nexus 3 images "disappearing" from the
>> server
>>
>>
>>
>> Thanks for your inputs Michael and Gary,
>>
>>
>>
>> Gary, the case you mention makes me wonder if this is a tag problem or
>> the way binaries are being tagged every day.
>>
>> I was chatting with Andy and he mentioned to me that in general Nexus3
>> reports so many docker issues.
>>
>>
>>
>> We confirmed this is not relates to a disk capacity issues since we have
>> still about 3TB of free space.
>>
>>
>>
>> I am trying something now which I don't guarantee might fix our issue,
>> but we could give it a shot at least.
>>
>> I have upgraded https://nexus3ap.onap.org/ to version 3.11.0 and see how
>> it behaves.
>>
>> If everything goes fine and that version is stable, we should upgrade
>> nexus3.onap.org too so that we are at least
>>
>> on the latest version.
>>
>>
>>
>> Can I get your thoughts on this?
>>
>>
>>
>> Thanks!
>>
>> Jess
>>
>>
>>
>> On Thu, May 10, 2018 at 11:44 PM, Michal Ptacek <
>> m.pta...@partner.samsung.com> wrote:
>>
>> Hi,
>>
>>
>>
>> not sure if it relates but OOM currently needs for dcae2gen following
>> images
>>
>>
>>
>> policy_handler: nexus3.onap.org:10001/onap/org
>> .onap.dcaegen2.platform.policy-handler:2.4.1
>> service_change_handler: nexus3.onap.org:10001/onap/org
>> .onap.dcaegen2.platform.servicechange-handler:1.1.3
>>
>>
>>
>> both of them are currently NOT available on nexus, the question is
>> whether it relates to this problem
>>
>>
>>
>> Should we just simply start using newer images (fix in OOM ?)
>>
>> I don't know if I can propose that as I am not from DCAE team ...
>>
>>
>>
>> thanks,
>>
>> Michal
>>
>>
>>
>> - *Original Message* -
>>
>> *Sender* : Gary Wu <gary.i...@huawei.com>
>>
>> *Date* : 2018-05-11 07:39 (GMT+1)
>>
>> *Title* : Re: [onap-discuss] Nexus 3 images "disappearing" from the
>> server
>>
>> *To : *null<jwagant...@linuxfoundation.org>, null<
>> onap-discuss@lists.onap.org>, null<onap-rele...@lists.onap.org>, null<
>> gildas.lani...@huawei.com>, null<jphe...@linuxfoundation.org>, null<
>> kp...@linuxfoundation.org>, null<abe...@linuxfoundation.org>
>>
>>
>>
>> Hi Jess,
>>
>>
>>
>> It’s not clear that the “Purge unused docker manifests and images” task
>> is the culprit.  If I understand the doc correctly, it’s only supposed to
>> delete images that are no longer associated with any t

Re: [onap-discuss] Nexus 3 images "disappearing" from the server

Thanks Gary,

I have updated it since a bit ago and been using it without an issue.

Gildas, can we propose to the TSC this upgrade please?

It is something we can easily try with about 1 min of downtime while the
server restarts with the new version.

Thanks!
Jess

On Fri, May 11, 2018 at 1:37 PM, Gary Wu <gary.i...@huawei.com> wrote:

> Sounds reasonable, except that I’m no longer actively using nexus3ap, and
> may not be able to give much feedback on how well it’s working.
>
>
>
> Thanks,
>
> Gary
>
>
>
> *From:* Jessica Wagantall [mailto:jwagant...@linuxfoundation.org]
> *Sent:* Friday, May 11, 2018 1:27 PM
> *To:* m.pta...@partner.samsung.com
> *Cc:* Gary Wu <gary.i...@huawei.com>; onap-discuss@lists.onap.org;
> onap-release <onap-rele...@lists.onap.org>; Gildas Lanilis <
> gildas.lani...@huawei.com>; Jeremy Phelps <jphe...@linuxfoundation.org>;
> Kenny Paul <kp...@linuxfoundation.org>; Anil Belur <
> abe...@linuxfoundation.org>
> *Subject:* Re: Re: [onap-discuss] Nexus 3 images "disappearing" from the
> server
>
>
>
> Thanks for your inputs Michael and Gary,
>
>
>
> Gary, the case you mention makes me wonder if this is a tag problem or the
> way binaries are being tagged every day.
>
> I was chatting with Andy and he mentioned to me that in general Nexus3
> reports so many docker issues.
>
>
>
> We confirmed this is not relates to a disk capacity issues since we have
> still about 3TB of free space.
>
>
>
> I am trying something now which I don't guarantee might fix our issue, but
> we could give it a shot at least.
>
> I have upgraded https://nexus3ap.onap.org/ to version 3.11.0 and see how
> it behaves.
>
> If everything goes fine and that version is stable, we should upgrade
> nexus3.onap.org too so that we are at least
>
> on the latest version.
>
>
>
> Can I get your thoughts on this?
>
>
>
> Thanks!
>
> Jess
>
>
>
> On Thu, May 10, 2018 at 11:44 PM, Michal Ptacek <
> m.pta...@partner.samsung.com> wrote:
>
> Hi,
>
>
>
> not sure if it relates but OOM currently needs for dcae2gen following
> images
>
>
>
> policy_handler: nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.
> policy-handler:2.4.1
> service_change_handler: nexus3.onap.org:10001/onap/
> org.onap.dcaegen2.platform.servicechange-handler:1.1.3
>
>
>
> both of them are currently NOT available on nexus, the question is whether
> it relates to this problem
>
>
>
> Should we just simply start using newer images (fix in OOM ?)
>
> I don't know if I can propose that as I am not from DCAE team ...
>
>
>
> thanks,
>
> Michal
>
>
>
> - *Original Message* -
>
> *Sender* : Gary Wu <gary.i...@huawei.com>
>
> *Date* : 2018-05-11 07:39 (GMT+1)
>
> *Title* : Re: [onap-discuss] Nexus 3 images "disappearing" from the server
>
> *To : *null<jwagant...@linuxfoundation.org>, null<onap-disc...@lists.onap.
> org>, null<onap-rele...@lists.onap.org>, null<gildas.lani...@huawei.com>,
> null<jphe...@linuxfoundation.org>, null<kp...@linuxfoundation.org>, null<
> abe...@linuxfoundation.org>
>
>
>
> Hi Jess,
>
>
>
> It’s not clear that the “Purge unused docker manifests and images” task is
> the culprit.  If I understand the doc correctly, it’s only supposed to
> delete images that are no longer associated with any tags.  I still see
> tons of time-stamped SNAPSHOT docker images from a couple of weeks ago
> still around (e.g. onap/cli: 2.0.0-SNAPSHOT-20180425T130053Z).
>
>
>
> As of this past couple of hours, onap/dmaap/dmaap-mr:1.1.4 has
> disappeared.  See https://jenkins.onap.org/job/integration-master-version-
> manifest-verify-java/182/.  This broke the deployments that were running
> around that time.
>
>
>
> Fortunately, I had a local docker cache where I could pull a copy of
> onap/dmaap/dmaap-mr:1.1.4, and I found that this image has the same sha256
> hash as the onap/dmaap/dmaap-mr:latest image currently on nexus3.  So the
> image is still there, but just the tag is missing.  Maybe this is another
> clue to help narrow down the cause.
>
>
>
> Thanks,
>
> Gary
>
>
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *On Behalf Of *Jessica Wagantall
>  *Sent:* Thursday, May 10, 2018 2:55 PM
>  *To:* onap-discuss@lists.onap.org; onap-release <
> onap-rele...@lists.onap.org>; Gildas Lanilis <gildas.lani...@huawei.com>;
> Jeremy Phelps <jphe...@linuxfoundation.org>; Kenny Paul <
> kp...@linuxfound

Re: [onap-discuss] Nexus 3 images "disappearing" from the server

Thanks for your inputs Michael and Gary,

Gary, the case you mention makes me wonder if this is a tag problem or the
way binaries are being tagged every day.
I was chatting with Andy and he mentioned to me that in general Nexus3
reports so many docker issues.

We confirmed this is not relates to a disk capacity issues since we have
still about 3TB of free space.

I am trying something now which I don't guarantee might fix our issue, but
we could give it a shot at least.
I have upgraded https://nexus3ap.onap.org/ to version 3.11.0 and see how it
behaves.
If everything goes fine and that version is stable, we should upgrade
nexus3.onap.org too so that we are at least
on the latest version.

Can I get your thoughts on this?

Thanks!
Jess

On Thu, May 10, 2018 at 11:44 PM, Michal Ptacek <
m.pta...@partner.samsung.com> wrote:

> Hi,
>
>
>
> not sure if it relates but OOM currently needs for dcae2gen following
> images
>
>
>
> policy_handler: nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.
> policy-handler:2.4.1
> service_change_handler: nexus3.onap.org:10001/onap/
> org.onap.dcaegen2.platform.servicechange-handler:1.1.3
>
>
>
> both of them are currently NOT available on nexus, the question is whether
> it relates to this problem
>
>
>
> Should we just simply start using newer images (fix in OOM ?)
>
> I don't know if I can propose that as I am not from DCAE team ...
>
>
>
> thanks,
>
> Michal
>
>
>
> - *Original Message* -
>
> *Sender* : Gary Wu <gary.i...@huawei.com>
>
> *Date* : 2018-05-11 07:39 (GMT+1)
>
> *Title* : Re: [onap-discuss] Nexus 3 images "disappearing" from the server
>
> *To : *null<jwagant...@linuxfoundation.org>, null<onap-disc...@lists.onap.
> org>, null<onap-rele...@lists.onap.org>, null<gildas.lani...@huawei.com>,
> null<jphe...@linuxfoundation.org>, null<kp...@linuxfoundation.org>, null<
> abe...@linuxfoundation.org>
>
>
>
> Hi Jess,
>
>
>
> It’s not clear that the “Purge unused docker manifests and images” task is
> the culprit.  If I understand the doc correctly, it’s only supposed to
> delete images that are no longer associated with any tags.  I still see
> tons of time-stamped SNAPSHOT docker images from a couple of weeks ago
> still around (e.g. onap/cli: 2.0.0-SNAPSHOT-20180425T130053Z).
>
>
>
> As of this past couple of hours, onap/dmaap/dmaap-mr:1.1.4 has
> disappeared.  See https://jenkins.onap.org/job/integration-master-version-
> manifest-verify-java/182/.  This broke the deployments that were running
> around that time.
>
>
>
> Fortunately, I had a local docker cache where I could pull a copy of
> onap/dmaap/dmaap-mr:1.1.4, and I found that this image has the same sha256
> hash as the onap/dmaap/dmaap-mr:latest image currently on nexus3.  So the
> image is still there, but just the tag is missing.  Maybe this is another
> clue to help narrow down the cause.
>
>
>
> Thanks,
>
> Gary
>
>
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *On Behalf Of *Jessica Wagantall
>  *Sent:* Thursday, May 10, 2018 2:55 PM
>  *To:* onap-discuss@lists.onap.org; onap-release <
> onap-rele...@lists.onap.org>; Gildas Lanilis <gildas.lani...@huawei.com>;
> Jeremy Phelps <jphe...@linuxfoundation.org>; Kenny Paul <
> kp...@linuxfoundation.org>; Anil Belur <abe...@linuxfoundation.org>
>  *Subject:* [onap-discuss] Nexus 3 images "disappearing" from the server
>
>
>
> Dear ONAP team,
>
>
>
> As mentioned today by Helen on the TSC call, it seems that we have
> experienced
>
> an issue with Nexus3 where the dependency images "disappear" for some
> moment and
>
> come back.
>
>
>
> I was investigating this issue a little bit closer, let me try to explain
> what I think is happening
>
> with Gary's example.
>
>
>
> In his case, onap/aaf/aaf_cm/manifests/2.1.0-SNAPSHOT
> <https://nexus3.onap.org/repository/docker.snapshot/v2/onap/aaf/aaf_cm/manifests/2.1.0-SNAPSHOT>
>  (among other AFF images) disappeared
>
> on the 9th of may and re-appeared the same day after few hours.
>
> Looking at the job that pushed this image https://jenkins.onap.
> org/view/aaf/job/aaf-authz-master-docker-java-shell-daily/,
>
> seems like AAF bins were successfully pushed on the 7th and on the 9th but
> failed on the 8th.
>
>
>
> At the same time, I believe this rule kicked in:
>
>
>
> This rule seems to be scanning for dependencies and will remove any
> snapshot not being referenced by anyone every day.
>
> https://help.sonatype.com/re

[onap-discuss] Nexus 3 images "disappearing" from the server

2018-05-10 Thread Jessica Wagantall

Dear ONAP team,

As mentioned today by Helen on the TSC call, it seems that we have
experienced
an issue with Nexus3 where the dependency images "disappear" for some
moment and
come back.

I was investigating this issue a little bit closer, let me try to explain
what I think is happening
with Gary's example.

In his case, onap/aaf/aaf_cm/manifests/2.1.0-SNAPSHOT

(among
other AFF images) disappeared
on the 9th of may and re-appeared the same day after few hours.
Looking at the job that pushed this image
https://jenkins.onap.org/view/aaf/job/aaf-authz-master-docker-java-shell-daily/
,
seems like AAF bins were successfully pushed on the 7th and on the 9th but
failed on the 8th.

At the same time, I believe this rule kicked in:

This rule seems to be scanning for dependencies and will remove any
snapshot not being referenced by anyone every day.
https://help.sonatype.com/repomanager3/configuration/system-configuration#SystemConfiguration-TypesofTasksandWhentoUseThem
There is not much configuration on this rule to be able to explain what is
actually looking for, but I believe this is the cause.

This rule might have removed the AAF image pushed on the 7th and, since the
AAF jenkins job failed to push a new image on the 8th,
the rule might have remove it for some time. Then the job that kicked in on
the 9th brought it back.

So, here is my suggestions:
- We need to make sure our daily jobs are healthy and address any failures
on a daily basis to avoid this issue in future
- Keeping this rule in place is helping us keep stability on disk space. If
we were to remove it we will have grater issues to address.
- I have confirmed with Andy and we prefer keeping this known configuration
in place to avoid disk usage issues.

Let me know if I was clear on my explanation and we can see if keeping an
eye on the dailies helps us reducing this occurrences.
Thanks a ton!
Jess
___
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

2018-05-09 Thread 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

2018-05-09 Thread 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

2018-05-04 Thread 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

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

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

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

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