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

2018-05-15 Thread Michael O'Brien via RT 
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-disc...@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] On Behalf Of Michael O'Brien
Sent: Thursday, May 10, 2018 12:05 PM
To: onap-disc...@lists.onap.org; onap-tsc 
mailto:onap-tsc@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 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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

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

2018-04-30 Thread Michael O'Brien via RT 
I was ok with moving code between the repos

Sounds good, Having a hard time with the mixed python and java code from the 
single root pom.xml that is picked up by Jenkins jobs - It may not have been a 
good idea to mix the 2 technologies in a single repo.
I'll work through the issues as I try to get code coverage working.
Worst case I will just remove all the java code - store it until after the 
release and concentrate on the python code.
/michael

-Original Message-
From: Gildas Lanilis via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Monday, April 30, 2018 6:20 PM
To: Michael O'Brien 
Cc: onap-disc...@lists.onap.org; onap-tsc@lists.onap.org
Subject: RE: [ONAP Helpdesk #55393] [LOG] New repo request for 
logging-analytics - add new java and python child repos

Hi Michael,

Currently for logging there is 1 repo labelled "logging-analytics". This repo 
can't be renamed.
LF will need to create 2 new repo
> Logging-analytics/java
> Logging-analytics/python

And you will need to move the code appropriately, then LF will need to lock the 
" logging-analytics" repo.

In term of timing, I fear this is not the right time to do it before Beijing 
Sign-Off.

Thoughts?

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287


-Original Message-
From: Michael O'Brien [mailto:frank.obr...@amdocs.com]
Sent: Sunday, April 29, 2018 5:43 PM
To: onap-helpd...@rt.linuxfoundation.org
Cc: Gildas Lanilis ; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: RE: [ONAP Helpdesk #55393] [LOG] New repo request for 
logging-analytics - add new java and python child repos

Yes, both issues are ok
We can have just 2 top level repos - like you propose The history can be 
deleted if this makes it easier - if you can preserve it - preserve it on the 
repo where all the existing code will go - the java one.
You can put everything on one side for now - as the python folder will need to 
be moved and a new root pom.xml for it.

Anything to help out the transition - the goal is to have separate CSIT, CLM, 
Docker, Sonar jobs Thank you /michael


-Original Message-
From: Anil Belur via RT [mailto:onap-helpd...@rt.linuxfoundation.org]
Sent: Sunday, April 29, 2018 8:39 PM
To: Michael O'Brien 
Cc: gildas.lani...@huawei.com; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - 
add new java and python child repos

On Sun Apr 29 19:28:26 2018, frank.obr...@amdocs.com wrote:
> LF, Gildas,
>We would like to split the current logging-analytics repo into 
> python and java.  Currently the shared repo root pom.xml is causing 
> issues running both technologies both offline and with jobs running on 
> jenkins.
>I would like to formally request 2 new repos.
> 
> https://git.onap.org/logging-analytics/
> 
> Logging-analytics/java
> Logging-analytics/python
> 
> In the future we will likely add a "go" repo - but not until we have 
> some artifacts in that language.
> 
> 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
> 

Hello Michael 

Please clarify the following to split the code into new repositories:

1. Do you need the git histroy preserved from the original repository, split 
into both the repos?
2. Can we rename the repositories as below, instead of have the repositories 
under separate folder `logging-analytics`? Doing this would be easier to 
maintain.
   logging-analytics-java
   logging-analytics-python
 
Thanks,
Anil

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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

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

2018-04-29 Thread Michael O'Brien via RT 
Yes, both issues are ok
We can have just 2 top level repos - like you propose
The history can be deleted if this makes it easier - if you can preserve it - 
preserve it on the repo where all the existing code will go - the java one.
You can put everything on one side for now - as the python folder will need to 
be moved and a new root pom.xml for it.

Anything to help out the transition - the goal is to have separate CSIT, CLM, 
Docker, Sonar jobs
Thank you
/michael


-Original Message-
From: Anil Belur via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Sunday, April 29, 2018 8:39 PM
To: Michael O'Brien 
Cc: gildas.lani...@huawei.com; onap-disc...@lists.onap.org; 
onap-tsc@lists.onap.org
Subject: [ONAP Helpdesk #55393] [LOG] New repo request for logging-analytics - 
add new java and python child repos

On Sun Apr 29 19:28:26 2018, frank.obr...@amdocs.com wrote:
> LF, Gildas,
>We would like to split the current logging-analytics repo into 
> python and java.  Currently the shared repo root pom.xml is causing 
> issues running both technologies both offline and with jobs running on 
> jenkins.
>I would like to formally request 2 new repos.
> 
> https://git.onap.org/logging-analytics/
> 
> Logging-analytics/java
> Logging-analytics/python
> 
> In the future we will likely add a "go" repo - but not until we have 
> some artifacts in that language.
> 
> 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
> 

Hello Michael 

Please clarify the following to split the code into new repositories:

1. Do you need the git histroy preserved from the original repository, split 
into both the repos?
2. Can we rename the repositories as below, instead of have the repositories 
under separate folder `logging-analytics`? Doing this would be easier to 
maintain.
   logging-analytics-java
   logging-analytics-python
 
Thanks,
Anil

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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

[onap-tsc] [ONAP Helpdesk #55375] [linuxfoundation.org #55375] RE: [Onap-release] [VID][VFC][SO][AAF][AAI][APPC][CCSDK][DCAE][DMAAP][CLAMP][SDNC][SDC][INT][PORTAL][POLICY][MUSIC][MULTICLOUD][MSB] Nexu

2018-04-29 Thread Michael O'Brien via RT 
Dan,
   Totally agree, I have CC’d Gildas on this. And the TSC – I would expect that 
this is our highest blocking issue Monday morning.
   Also, I am just the messenger – I was assisting a training session on 
installing onap for several developers on Friday when this phenomenon appeared 
– checked my CD systems and they also were busted.
   Trying to get this to the attention of everyone so we can lead a way out of 
this scenario.
   Bottom line is that a change was unilaterally made

   You bring up a good point – not just a fix but is this new process advisable.
   There is a refactor of how we build docker images so that they are on-demand 
instead of daily – if we are in a window of slower merge cycles until this is 
finished then we need to go over it Monday.
I recommend that the LF just fix all the 50 containers immediately as the 
build is currently completely broken.
It should not be up to individual PTL’s to get something going that was 
working OK Friday morning.

Usually I recommend we meet with the LF on these issues.  We can devote the 
PTL meeting to this and get feedback from everyone.
Ideally breaking changes like this are put up to the PTLs first, we try to 
do some prototype/impact and then schedule the change.

Thank you
/michael


From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Saturday, April 28, 2018 8:55 PM
To: Michael O'Brien ; onap-disc...@lists.onap.org; 
onap-release ; onap-tsc ; 
helpd...@onap.org
Subject: Re: [Onap-release] 
[VID][VFC][SO][AAF][AAI][APPC][CCSDK][DCAE][DMAAP][CLAMP][SDNC][SDC][INT][PORTAL][POLICY][MUSIC][MULTICLOUD][MSB]
 Nexus3 Fix breaks deployment - PTLs please reply to the LF email to release 
your snapshot dockers to return the build t...

Michael

Please see the comment I just added to this ticket.  This is a much bigger 
issue than just releasing the existing docker containers.  If we can’t use 
snapshot or staging versions of Dockers any longer in integration, you are 
probably going to be looking at an average turnaround for fixes of no better 
than 24 hours (since each and every one will need 2 releases done : first of 
Maven artifact, then a rebuild Docker based on updated Maven, and then finally 
released version of Docker).

Also, if we do as requested and request release builds for our docker 
containers, there is a possibility for discrepancies between our released Maven 
artifacts and released Docker containers.

Due to this potential discrepancy, I think we need to discuss this at our PTL 
call on Monday.  We need to make the TSC aware of this potential discrepancy 
and to go on record accepting that risk.

Dan


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

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

From: 
mailto:onap-release-boun...@lists.onap.org>>
 on behalf of "OBRIEN, FRANK MICHAEL" 
mailto:frank.obr...@amdocs.com>>
Date: Saturday, April 28, 2018 at 5:39 PM
To: onap-discuss 
mailto:onap-disc...@lists.onap.org>>, onap-release 
mailto:onap-rele...@lists.onap.org>>, onap-tsc 
mailto:onap-tsc@lists.onap.org>>, 
"helpd...@onap.org" 
mailto:helpd...@onap.org>>
Subject: [Onap-release] 
[VID][VFC][SO][AAF][AAI][APPC][CCSDK][DCAE][DMAAP][CLAMP][SDNC][SDC][INT][PORTAL][POLICY][MUSIC][MULTICLOUD][MSB]
 Nexus3 Fix breaks deployment - PTLs please reply to the LF email to release 
your snapshot dockers to return the build to de...


Team,

   Please assist the LF and Gildas to get the snapshot docker images released 
so we can pull again for Beijing deployments

   The list of containers failing because of images unable to pull are listed 
below and in the jira



See JIRA

https://jira.onap.org/browse/CIMAN-157



Check the projects below and reply to the mail below to fix your images

https://lists.onap.org/pipermail/onap-discuss/2018-April/009317.html

PTL?

sniro

common - postgres

smsdb

vault

consul



PTLs verified

vid

vfc

so

aaf

aai

appc

ccsdk

dcae

dmaap

clamp

sdnc

sdc

integration

portal

music

policy

multicloud

msb




(+) proposal - dont wait for PTL approval - we already were running with these 
50 images - just reenable them



All CD deployments fail except those with a proxy

http://jenkins.onap.info/job/oom-cd-master/

[onap-tsc] [ONAP Helpdesk #51247] [linuxfoundation.org #51247] RE: [onap-discuss] wiki down: 502 bad gateway on wiki.onap.org at 1708 EST GMT-5

2018-01-17 Thread Michael O'Brien via RT 
Back up - only a 600 second outage - thanks for the quick turnaround
/michael

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael O'Brien
Sent: Wednesday, January 17, 2018 17:12
To: onap-discuss ; onap-tsc@lists.onap.org; 
helpd...@onap.org
Subject: [onap-discuss] wiki down: 502 bad gateway on wiki.onap.org at 1708 EST 
GMT-5

LF,
  Hi, the system went down 1 min ago on 3 systems (corp laptop, personal 
laptop, cell phone)
  Dig to dev.onap.org: 198.145.29.92

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
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-TSC mailing list
ONAP-TSC@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc