Re: [onap-discuss] [onap-tsc] Clarifying the plan for developer gathering at ONS

[Alla Goldner]

Hi Phil,

Thanks a lot for this information!

As we know, ONS attendants have to pay registration fees.
What is arrangement for those coming to attend ONAP meeting?


Best regards,

Alla Goldner

Open Network Division
Amdocs Technology


[cid:image001.png@01D394EC.DBC882A0]

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Phil Robb
Sent: Tuesday, January 23, 2018 8:50 PM
To: onap-tsc ; onap-discuss@lists.onap.org; Raymond 
Paik 
Subject: [onap-tsc] Clarifying the plan for developer gathering at ONS

Hello ONAP developers and TSC members:

I wanted to provide some clarity on the activities and timeframe we have to 
gather during ONS.

The developer event during ONS week will be from 8:00am to 6:00pm on Monday, 
March 26th, and 8:00am to 12:00 noon on Tuesday, March 27th.  From requests we 
have received we had also been investigating the possibility to extend the 
event into the proceeding Sunday, but we've determined that such an extension 
is not going to be possible.  That said, we still have the Monday/Tuesday time 
for formal presentations, as well as break out rooms and a developer lounge for 
continued meetings, discussions, and hacking at ONS during the rest of the week.

As we've mentioned before, we would like to take advantage of the fact that the 
communities from the different projects will be in the same place at the same 
time.  As such, we encourage you to propose sessions that can further 
cross-collaboration among the LFN projects.  We also recognize that there are 
plenty of project-specific topics that need to be discussed.  Please also 
propose those sessions for this event.

With the LFN formally announced today, we are working to get the LFN wiki site 
up and running as quickly as possible.  One of the first uses for this site 
will be the location for submitting your proposed talks and presentations for 
the developer event at ONS.  We apologize that it is not up quite yet but it 
will be up within the next 2 or 3 days.

Once the site is up, Ray Paik (cc-ed) will send out an email to all communities 
on where to find it along with a call-for-presentations for you to post your 
discussion and presentation topics.  Between February 9th and February 15th, we 
will convene the TAC representatives from the LFN projects to review the 
submissions and to form an outline/framework for the developer event, giving 
time for cross-project discussions, project-specific sessions, and a TAC 
meeting.  From there, we will work with each project TSC to prioritize 
project-specific sessions during the event.

I am looking forward to this first-of-its-kind event and the breadth and depth 
of discussions we will have during this week.  Please be preparing your topics 
over the coming days and submit them to the LFN wiki once it is live.

Best regards,

Phil.
--
Phil Robb
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
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] [sdc] What are the relationships between Distribution Engine, uebServers and Dmaap?

[yuan.hu1]

Hi Michael and David,




What are the relationships between Distribution Engine, uebServers and Dmaap?

Does the uebServers play a message brocker(agent) when the Distribution Engine 
send a message to the Dmaap?

And how to deploy a uebServers?




Thanks,

Yuan Hu  











原始邮件



发件人：袁虎10090474
收件人： ;
抄送人： ;
日 期 ：2018年01月19日 11:32
主 题 ：[sdc] What are the relationships between Distribution Engine, uebServers 
and Dmaap?




Hi Michael,







What are the relationships between Distribution Engine, uebServers and Dmaap?


Does the uebServers play a message brocker(agent) when the Distribution Engine 
send a message to the Dmaap?


And how to deploy a uebServers?






Thanks,


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

Re: [onap-discuss] [OOM] DCAE config in windriver

[Gary Wu]

Incidentally I’m also getting this error from entrypoint.sh; not sure if it’s 
related to this set of changes:

sed: can’t read /opt/robot/vm_properties.py: No such file or directory

Thanks,
Gary

From: Gary Wu
Sent: Tuesday, January 23, 2018 4:41 PM
To: 'Alexis de Talhouët' 
Cc: BRIAN D FREEMAN ; PLATANIA, MARCO (MARCO) 
; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM] DCAE config in windriver

Hi Alexis,

Despite having DNS_PROXY_ENABLE turned on, I’m observing the following:

dcaegen2/heat/entrypoint.sh repeatedly tries to configure Designate directly 
via “openstack recordset” commands and failing with authentication errors.  Is 
this supposed to be happening?  The multicloud proxy endpoint seems to be 
properly configured in onap_dcae.env, but this endpoint doesn’t seem to be used 
by entrypoint.sh so I’m not sure how the DNS record requests are supposed to 
get into the proxy.

Because of the DNS record creation issue above, the dcae-bootstrap VM is still 
stuck due to inability to resolve “vm1.aai.simpledemo.onap.org”.

Thanks,
Gary


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 9:34 AM
To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: BRIAN D FREEMAN mailto:bf1...@att.com>>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE config in windriver

Right, as I said, expect this to be merged in a couple of hours.

Thanks,
Alexis

On Jan 23, 2018, at 12:29 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

The first patch depends on the second, but the second has not yet been merged 
yet?  I guess I should wait for the second one to merged first?

Thanks,
Gary

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 8:53 AM
To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: BRIAN D FREEMAN mailto:bf1...@att.com>>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE config in windriver

Gary,

This patch fixes the OOM to enable proxy DNS designate setup: 
https://gerrit.onap.org/r/#/c/28933/

I’ve tested in my environment, it’s working.

Please try again when you have some time. Note, the onap-parameters.yaml have 
changed a little bit to enable this. See https://gerrit.onap.org/r/#/c/28591/

Expect this to be merge in a couple of hours.

Thanks,
Alexis


On Jan 22, 2018, at 3:57 PM, Alexis de Talhouët 
mailto:adetalhoue...@gmail.com>> wrote:

Gary,

OOM doesn’t yet support the proxied solution. This is being worked on; until 
this is not fix, you cannot use Wind-River lab to deploy OOM with DCAENGEN2.
Expect the fix to be submit in the next couple of days.

Thanks,
Alexis


On Jan 22, 2018, at 3:17 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

Hi Alexis,

Yes, I’m able to deploy DCAEGEN2 on a (non-Wind River) system with Designate 
installed.  My question is specifically on the Wind River lab.  Can we use 
Designate there?  So far what I see is “public endpoint for dns service in 
RegionOne region not found”, so it seems like we cannot.  Or is there a special 
Designate endpoint/config available?

Has anyone successfully deployed OOM with DCAEGEN2 in the Wind River lab, with 
or without the proxy solution?

Thanks,
Gary


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Monday, January 22, 2018 11:58 AM
To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: BRIAN D FREEMAN mailto:bf1...@att.com>>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE config in windriver

Hi Gary,

I noticed the proxy solution that DCAEGEN2 offers is not fully working yet with 
OOM. What is working is having DCAE on the same OpenStack as DNS Designate. I’m 
currently in the process of addressing this.

Regarding your question about how 
"vm1.aai.simpledemo.onap.org gets 
resolves, we create a zone in Designate for 
simpledemo.onap.org, see 
https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/entrypoint.sh;h=85c5ee2b131458f7f25cab3c8efc4071b22775f5;hb=refs/heads/amsterdam
And we added a reverse proxy so the lookup returns the IP of the K8S host 
running the reverse-proxy, and the service port are opened.

See bellow design implemented:




Thanks,
Alexis



On Jan 22, 2018, at 2:00 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

Hi Alexis and Brian,

How should we currently spin up DCAEGEN2 using OOM in Wind River lab?

I assume we're supposed to set DNSAAS_PROXY_ENABLE to "true".  However, when 
this is done, my dcae-dcae-boostrap VM gets stuck on wait_for_aai_ready() since 
it's unable to resolve the hostname 
"vm1.aai.simpledemo.onap.org

Re: [onap-discuss] Triggering CLM jobs

[Gildas Lanilis]

Looping in security committee for their guidance.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DRAGOSH, PAMELA L 
(PAM)
Sent: Tuesday, January 23, 2018 10:32 AM
To: Jessica Wagantall ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Triggering CLM jobs

Jessica,

Thanks. I have a question on resolving security issues. Sometimes it is an easy 
fix to upgrade to a newer version of a dependency. However, other times there 
was no fix but a work around was in place. Or, it doesn’t apply because the 
method actually isn’t being used by our project. How do we resolve the CLM 
security issue? Do PTL’s have the right to do this (similar to sonar)?

Thanks,

Pam

From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Jessica Wagantall 
mailto:jwagant...@linuxfoundation.org>>
Date: Monday, January 22, 2018 at 5:58 PM
To: "onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] Triggering CLM jobs

Dear ONAP team,

Just to let you know, the CLM jobs can now be triggered on demand after posting
the comment "run-clm" in your Gerrit change.

The CLM jobs are still scheduled to run every Saturday but I hope this feature 
can be
useful for debugging on demand.

Just as a reminder, commenting "run-clm" in a gerrit that is not merged, will 
not trigger
the CLM job based on that revision but will trigger the job based on the tip of 
the branch.
This job is designed to always run on the latest tip of the branch to avoid 
inconsistencies on
the reports.

Please let me know for any questions
Thanks a ton!
Jess.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration]ONAP Maturity Benchmark / KPI discussion

[Yunxia Chen]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Yunxia Chen:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chen Yan:M
 AILTO:chenyan@chinatelecom.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 ss:MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:When: Wednesday\, January 24\, 2018 5:00 PM-6:00
  PM. (UTC-08:00) Pacific Time (US & Canada)\nWhere: https://zoom.us/j/4466
 66\n\n*~*~*~*~*~*~*~*~*~*\n\nLet’s go through the requirement from C
 hina Telecom.\n
SUMMARY;LANGUAGE=en-US:[integration]ONAP Maturity Benchmark / KPI discussio
 n
DTSTART;TZID=Pacific Standard Time:20180124T17
DTEND;TZID=Pacific Standard Time:20180124T18
UID:0A41E29F-07AF-44EE-A9D8-1606D32AEDA0
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20180124T011250Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/44
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2116140392
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] DCAE config in windriver

[Gary Wu]

Hi Alexis,

Despite having DNS_PROXY_ENABLE turned on, I’m observing the following:

dcaegen2/heat/entrypoint.sh repeatedly tries to configure Designate directly 
via “openstack recordset” commands and failing with authentication errors.  Is 
this supposed to be happening?  The multicloud proxy endpoint seems to be 
properly configured in onap_dcae.env, but this endpoint doesn’t seem to be used 
by entrypoint.sh so I’m not sure how the DNS record requests are supposed to 
get into the proxy.

Because of the DNS record creation issue above, the dcae-bootstrap VM is still 
stuck due to inability to resolve “vm1.aai.simpledemo.onap.org”.

Thanks,
Gary


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 9:34 AM
To: Gary Wu 
Cc: BRIAN D FREEMAN ; PLATANIA, MARCO (MARCO) 
; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE config in windriver

Right, as I said, expect this to be merged in a couple of hours.

Thanks,
Alexis


On Jan 23, 2018, at 12:29 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

The first patch depends on the second, but the second has not yet been merged 
yet?  I guess I should wait for the second one to merged first?

Thanks,
Gary

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 8:53 AM
To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: BRIAN D FREEMAN mailto:bf1...@att.com>>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE config in windriver

Gary,

This patch fixes the OOM to enable proxy DNS designate setup: 
https://gerrit.onap.org/r/#/c/28933/

I’ve tested in my environment, it’s working.

Please try again when you have some time. Note, the onap-parameters.yaml have 
changed a little bit to enable this. See https://gerrit.onap.org/r/#/c/28591/

Expect this to be merge in a couple of hours.

Thanks,
Alexis



On Jan 22, 2018, at 3:57 PM, Alexis de Talhouët 
mailto:adetalhoue...@gmail.com>> wrote:

Gary,

OOM doesn’t yet support the proxied solution. This is being worked on; until 
this is not fix, you cannot use Wind-River lab to deploy OOM with DCAENGEN2.
Expect the fix to be submit in the next couple of days.

Thanks,
Alexis



On Jan 22, 2018, at 3:17 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

Hi Alexis,

Yes, I’m able to deploy DCAEGEN2 on a (non-Wind River) system with Designate 
installed.  My question is specifically on the Wind River lab.  Can we use 
Designate there?  So far what I see is “public endpoint for dns service in 
RegionOne region not found”, so it seems like we cannot.  Or is there a special 
Designate endpoint/config available?

Has anyone successfully deployed OOM with DCAEGEN2 in the Wind River lab, with 
or without the proxy solution?

Thanks,
Gary


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Monday, January 22, 2018 11:58 AM
To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: BRIAN D FREEMAN mailto:bf1...@att.com>>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE config in windriver

Hi Gary,

I noticed the proxy solution that DCAEGEN2 offers is not fully working yet with 
OOM. What is working is having DCAE on the same OpenStack as DNS Designate. I’m 
currently in the process of addressing this.

Regarding your question about how 
"vm1.aai.simpledemo.onap.org gets 
resolves, we create a zone in Designate for 
simpledemo.onap.org, see 
https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/entrypoint.sh;h=85c5ee2b131458f7f25cab3c8efc4071b22775f5;hb=refs/heads/amsterdam
And we added a reverse proxy so the lookup returns the IP of the K8S host 
running the reverse-proxy, and the service port are opened.

See bellow design implemented:




Thanks,
Alexis




On Jan 22, 2018, at 2:00 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

Hi Alexis and Brian,

How should we currently spin up DCAEGEN2 using OOM in Wind River lab?

I assume we're supposed to set DNSAAS_PROXY_ENABLE to "true".  However, when 
this is done, my dcae-dcae-boostrap VM gets stuck on wait_for_aai_ready() since 
it's unable to resolve the hostname 
"vm1.aai.simpledemo.onap.org", and none of 
the DNSAAS-related code in dcae_vm_init.sh gets triggered since they only occur 
after wait_for_aai_ready().

Is there additional config/init that we're supposed to do to get 
vm1.aai.simpledemo.onap.org to resolve in 
this VM?

Thanks,
Gary

-Original Message-
From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Monday, January 22, 2018 6:48 AM
To: 

Re: [onap-discuss] [AAI][SO] How to add another LCP Region

[FREEMAN, BRIAN D]

I think this issue was the format of onap_parameters.yaml changed.


I re-edited the onap_parameters_sample.yaml and used that and it at least got 
past the k8 init phase.


Brian


From: FREEMAN, BRIAN D
Sent: Tuesday, January 23, 2018 3:56 PM
To: Alexis de Talhouët 
Cc: onap-discuss 
Subject: RE: [onap-discuss] [AAI][SO] How to add another LCP Region

That’s Michael’s continuouse deployment script.

It was working fine now I seem to have broken it.

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 3:54 PM
To: FREEMAN, BRIAN D mailto:bf1...@att.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region

Brian,

I’m not familiar with the cd.sh script.

Alexis

On Jan 23, 2018, at 12:53 PM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:

OK – I’ll try later. For some reason cd.sh got stuck “waiting for config pod to 
complete” ?

Do I need to update my version of cd.sh ?

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 11:48 AM
To: FREEMAN, BRIAN D mailto:bf1...@att.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region

Brian, no it’s not merged yet.

It has been Code-Review +2 and Verified +1, but not submitted yet. It’s 
dependent on some other patch I was testing. I just found my missing piece. 
Expect this to be merge by 1pm.

Thanks for testing, though :)

Thanks,
Alexis


On Jan 23, 2018, at 11:37 AM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:

I think it was merged today (in parallel with your email I suspect).

Trying an cd.sh install now on -b amsterdam to see.

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 11:28 AM
To: FREEMAN, BRIAN D mailto:bf1...@att.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region





On Jan 10, 2018, at 5:56 PM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:


  1.  Robot did not work – trying to patch/work around to use it and it 
partially succeed – could be amsterdam vs master issue

 *   Tried to run robot distribute and the heat templates were missing
 *   Used the following:
   i.  Cd 
/dockerdata-nfs/onap/
 ii.  Git clone 
http://gerrit.onap.org/r/demo
   iii.  Cd demo
   iv.  cp -rf heat 
../robot/eteshare
 v.  this put 
the heat/vFW etc into the heat directory.

 *   After this distribute seems to work partially
   i.  ROBOT 
fails after partially distributing looking for 6 thing and getting 5 – not sure 
what that error is but the models do seem to be distributed to AAI and SO from 
the SDC GUI perspective


Brian, the fix for this is now out: 
https://gerrit.onap.org/r/#/c/28935/

Expect it to be merged in the next few days.

Thanks,
Alexis

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

Re: [onap-discuss] [AAI][SO] How to add another LCP Region

[FREEMAN, BRIAN D]

That’s Michael’s continuouse deployment script.

It was working fine now I seem to have broken it.

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 3:54 PM
To: FREEMAN, BRIAN D 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region

Brian,

I’m not familiar with the cd.sh script.

Alexis


On Jan 23, 2018, at 12:53 PM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:

OK – I’ll try later. For some reason cd.sh got stuck “waiting for config pod to 
complete” ?

Do I need to update my version of cd.sh ?

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 11:48 AM
To: FREEMAN, BRIAN D mailto:bf1...@att.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region

Brian, no it’s not merged yet.

It has been Code-Review +2 and Verified +1, but not submitted yet. It’s 
dependent on some other patch I was testing. I just found my missing piece. 
Expect this to be merge by 1pm.

Thanks for testing, though :)

Thanks,
Alexis



On Jan 23, 2018, at 11:37 AM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:

I think it was merged today (in parallel with your email I suspect).

Trying an cd.sh install now on -b amsterdam to see.

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 11:28 AM
To: FREEMAN, BRIAN D mailto:bf1...@att.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region






On Jan 10, 2018, at 5:56 PM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:


  1.  Robot did not work – trying to patch/work around to use it and it 
partially succeed – could be amsterdam vs master issue

 *   Tried to run robot distribute and the heat templates were missing
 *   Used the following:
   i.  Cd 
/dockerdata-nfs/onap/
 ii.  Git clone 
http://gerrit.onap.org/r/demo
   iii.  Cd demo
   iv.  cp -rf heat 
../robot/eteshare
 v.  this put 
the heat/vFW etc into the heat directory.

 *   After this distribute seems to work partially
   i.  ROBOT 
fails after partially distributing looking for 6 thing and getting 5 – not sure 
what that error is but the models do seem to be distributed to AAI and SO from 
the SDC GUI perspective


Brian, the fix for this is now out: 
https://gerrit.onap.org/r/#/c/28935/

Expect it to be merged in the next few days.

Thanks,
Alexis

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

Re: [onap-discuss] [AAI][SO] How to add another LCP Region

[Alexis de Talhouët]

Brian,

I’m not familiar with the cd.sh script.

Alexis

> On Jan 23, 2018, at 12:53 PM, FREEMAN, BRIAN D  wrote:
> 
> OK – I’ll try later. For some reason cd.sh got stuck “waiting for config pod 
> to complete” ?
>  
> Do I need to update my version of cd.sh ?
>  
> Brian
>  
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
> Sent: Tuesday, January 23, 2018 11:48 AM
> To: FREEMAN, BRIAN D 
> Cc: onap-discuss 
> Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region
>  
> Brian, no it’s not merged yet.
>  
> It has been Code-Review +2 and Verified +1, but not submitted yet. It’s 
> dependent on some other patch I was testing. I just found my missing piece. 
> Expect this to be merge by 1pm.
>  
> Thanks for testing, though :)
>  
> Thanks, 
> Alexis
> 
> 
> On Jan 23, 2018, at 11:37 AM, FREEMAN, BRIAN D  > wrote:
>  
> I think it was merged today (in parallel with your email I suspect).
>  
> Trying an cd.sh install now on -b amsterdam to see.
>  
> Brian
>  
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com 
> ] 
> Sent: Tuesday, January 23, 2018 11:28 AM
> To: FREEMAN, BRIAN D mailto:bf1...@att.com>>
> Cc: onap-discuss  >
> Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region
>  
>  
> 
> 
> 
> On Jan 10, 2018, at 5:56 PM, FREEMAN, BRIAN D  > wrote:
>  
> Robot did not work – trying to patch/work around to use it and it partially 
> succeed – could be amsterdam vs master issue
> Tried to run robot distribute and the heat templates were missing
> Used the following:
>i.  Cd 
> /dockerdata-nfs/onap/
>  ii.  Git 
> clone http://gerrit.onap.org/r/demo 
> 
>iii.  Cd demo
>iv.  cp -rf 
> heat ../robot/eteshare
>  v.  this put 
> the heat/vFW etc into the heat directory.
> After this distribute seems to work partially
>i.  ROBOT 
> fails after partially distributing looking for 6 thing and getting 5 – not 
> sure what that error is but the models do seem to be distributed to AAI and 
> SO from the SDC GUI perspective
>  
>  
> Brian, the fix for this is now out: https://gerrit.onap.org/r/#/c/28935/ 
> 
>  
> Expect it to be merged in the next few days.
>  
> Thanks,
> Alexis

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

Re: [onap-discuss] ONAP continuous tagging and deployment discussion - full CI/CD

[Alexis de Talhouët]

Some thoughts:

- Continuous System Integration Test (CSIT) per project, current level is low: 
https://jenkins.onap.org/view/CSIT/ We should encourage project as part as 
their milestones to have a certain level of coverage through CSIT. Maybe create 
a reward, like the project that has the best test coverage (we’ve done this for 
a few releases in ODL)
- REST API layer
- E2E functionality within the project itself (using simulators, …)

- CSIT for overall ONAP, e.g run close-loop use cases

- A better way to customize ONAP deployment in OOM. Currently everything is 
coming from an onap-parameters.yaml file, which was done initially but isn’t a 
good solution. Team is currently working on moving the configuration under each 
helm chart (per project), so configuration can be derived from the helm chart 
itself. Once done, we can create a common helm chart that will centralize the 
ONAP parameters to be passed to any projects helm chart, it will basically sit 
on top of the other, as illustrated bellow:
——— 
 common chart
——— 
 projects chart
——— 
That way, projects chart can be configured to retrieved the value from the 
common chart, or to use their own values (using Go Templating, e.g. {{ 
Values.common.appcversion | default v1.1.1 }} ). So basically we keep the 
ability to deploy one chart at the time.
Finally, Helm provides the ability to overwrite the values.yaml properties when 
deploying a chart, hence the common values.yaml file can be overwritten to 
provide specific environment details.

- Create a CI process for OOM in ONAP’s Jenkins. As OOM is using helm chart for 
each application, OOM should produce helm chart, and at release time, should 
release helm chart, so consumer (GOCD, Cloudify, …) can consume them. This 
currently doesn’t exist in ONAP, moreover, we need ONAP to be able to host helm 
chart. Nexus doesn’t offer this capability yet. I know Bintray does, and it’s 
on the way for Artifcatory. But we need support from the LF on this to find the 
appropriate solution. Note, it could also be a simple HTTP server on which we 
can have two folders, snapshot and release, and manipulate helm chart from 
there.

- Create a CD process for OOM in ONAP’s Jenkins: Today we have Michael’s script 
that does the job. But we should have something that provides more auditing, 
better logging, better traceability, etc Internally we’ve been using GOCD 
for that, and we’re currently looking at how to properly upstream what we’ve 
done. GOCD allows to create pipeline, similar to Jenkins pipeline, but geared 
mainly for CD and not CI. This will give the ability to deploy ONAP on 
multiple/different environments. Also, this could be triggered by an upstream 
Jenkins Job, like a merge job, or a keyword comment on a gerrit patch. An 
alternative to GOCD, being currently developed in OOM, is Cloudify. So both 
options will sit on top of OOM, consuming helm chart build by OOM.

- Ability to upgrade a component. Today, OOM only offers the ability to create 
or delete component, which is underusing the advantage of Kubernetes that 
support upgrade for any deployment.
With the upgradability feature provided by OOM, we will be able to re-deploy 
only components that have changed, based on docker image version. So no need to 
re-deploy the whole ONAP. And the best part is, it will rollback is the upgrade 
has failed. So we can keep and “stable” like kind of environment where to 
periodically run the CSIT covering the close-loop use cases.

Regarding how the process should work in Gerrit:
- I tend to think we shouldn’t have to wait for an hour or so to have a 
Verified +1 from Jenkins, this is too long, and this will impact development 
cycles badly. Ideally, the Jenkins verified job shouldn’t take more than 30 mn 
if we want to be efficient. 
The addition of a Gerrit trigger keyword to run it the full CSIT close-loops 
suites will allow committer/developers to run more in-depth verification on 
patches that they feel requires it.


Alexis

> On Jan 23, 2018, at 2:37 PM, Michael O'Brien  wrote:
> 
> Team,
> Hi, the Integration(Ran, Marco, Gary, Helen, Brian), OOM(Alexis, Mike O, 
> Mike E, Yuri), the Linux Foundation(Jessica) and members of the TSC (Gildas) 
> have been discussing build tagging and continuous deployment as a way of 
> validating the runtime integrity of each component merge – a fully jenkins 
> triggered automated CI/CD system that does more than healthcheck.
> At the last Integration meet and a couple before that we discussed moving 
> away from blind tagging and more towards continuous build validation – this 
> meeting is in response.
> One of the major goals of this meeting is getting a clean set of tasks we 
> will present to the Linux Foundation and the PTLs on any 
> addition/modification of the current Jenkins/nexus3 build structure.
>  
> We will be holding weekly meetings so everyone can contribute and be 

[onap-discuss] ONAP continuous tagging and deployment discussion - full CI/CD

[Michael O'Brien]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Michael O'Brien:MAILTO:frank.obr...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jessica Wa
 gantall:MAILTO:jwagant...@linuxfoundation.org
ATTACH:CID:37CAC50216F4B046B628986FE8432E97@amdocs.com
ATTACH:CID:75223DBADFC13F4EBCEE400C8EC2@amdocs.com
DESCRIPTION;LANGUAGE=en-US:Team\,\nHi\, the Integration(Ran\, Marco\, G
 ary\, Helen\, Brian)\, OOM(Alexis\, Mike O\, Mike E\, Yuri)\, the Linux Fo
 undation(Jessica) and members of the TSC (Gildas) have been discussing bui
 ld tagging and continuous deployment as a way of validating the runtime in
 tegrity of each component merge – a fully jenkins triggered automated CI
 /CD system that does more than healthcheck.\nAt the last Integration m
 eet and a couple before that we discussed moving away from blind tagging a
 nd more towards continuous build validation – this meeting is in respons
 e.\nOne of the major goals of this meeting is getting a clean set of t
 asks we will present to the Linux Foundation and the PTLs on any addition/
 modification of the current Jenkins/nexus3 build structure.\n\nWe will
  be holding weekly meetings so everyone can contribute and be aware of wor
 k items and changes to the way we build\, deploy\, test and mark each comm
 it in onap.  Currently the JobBuilder does CI compilation/test marking a -
 1/+1.  We will be coming up with a set of proposals to drive CD with the g
 oal of creating/consuming a manifest per commit and marking a merge as +1/
 -1 using an additional “CDBuilder”.\n Please come to the meeting t
 o help us align/fix anything out of order and sort out the work items.\n\n
 https://zoom.us/j/7939937123\nTentatively 1130 EST (GMT-5) on Thu – 30 m
 in after the TSC meeting – we can move it\n\n There is a JIRA being 
 worked out that describes the tasks needed to transition a live POC using 
 what is running now.  There is also work being done in OOM-460 that will a
 lign any CD system to helm based config packaging.  This meeting is to wor
 k out tasks mostly around what will impact the LF and PTLs as we bring in 
 continuous deployment and align CI/CD with what is master right now.\n\n  
 Agenda items\nReview https://jira.onap.org/browse/OOM-500\nDiscuss ali
 gning the nexus3 docker tag timestamp format –
  LF task and PTL oversight\nDiscuss building tagged docker images per comm
 it – more granular than daily – LF task\nDiscuss how to validate 
 a tagset containing the specific commit under test – the CD deployment server/job – this is where we pull/p
 ush the docker tagset manifest under test.\n\nDiscussion start (from OOM-5
 00)\n\n  existing flow (actual)\n•   gerrit review commits - partial
 -CI runs - JobBuilder marks -1 (compile failure\, sonar failure)\n• 
   gerrit review commits - partial-CI runs - JobBuilder marks +1\, committe
 r +2 merges to master\, (later daily docker merge build tagged docker blin
 dly)\n•   no way to know whether that commit degraded ONAP\n\n  prop
 osed flow (expected) - two phase JobBuilder +1 process\n•   gerrit r
 eview commits - partial-CI runs - JobBuilder marks -1 (compile failure\, s
 onar failure)\n•   gerrit review commits - partial-CI runs - JobBuil
 der marks +1\, (what we add below)\nkick in docker merge immediately\, we 
 tag the docker image\, we adjust the manifest for this review\nrun extra C
 DBuilder that runs CD deploy of OOM using above tagset manifest\, healthch
 eck\, vFW\nreport failure - marks gerrit review as -1 - no tag set publish
 ed for this failed commit\nor report pass - marks gerrit review as +1\njen
 kins now retags "latest" to the the docker built above for the review (do 
 not blindly tag "latest" to the last docker build whether it passes/fails 
 CD)\nTagset for that build becomes the latest stable master build of ONAP 
 (as in an OOM deploy will run not from master tip but from a tagged set th
 at omits the last breaking change)\n•   committer +2 merges to maste
 r\, (docker merge and tagging should not be required as long as master has
  not moved during the 1 hour CD build)\n\n\n Thank you\n /michael\
 n\n\n\n\n\n
SUMMARY;LANGUAGE=en-US:ONAP continuous tagging and deployment discussion - 
 full CI/CD
DTSTART;TZID=Eastern Standard Time:20180125T113000
DTEND;TZID=Eastern Standard Time:20180125

[onap-discuss] Clarifying the plan for developer gathering at ONS

[Phil Robb]

Hello ONAP developers and TSC members:

I wanted to provide some clarity on the activities and timeframe we have to
gather during ONS.

The developer event during ONS week will be from 8:00am to 6:00pm on
Monday, March 26th, and 8:00am to 12:00 noon on Tuesday, March 27th.  From
requests we have received we had also been investigating the possibility to
extend the event into the proceeding Sunday, but we've determined that such
an extension is not going to be possible.  That said, we still have the
Monday/Tuesday time for formal presentations, as well as break out rooms
and a developer lounge for continued meetings, discussions, and hacking at
ONS during the rest of the week.

As we've mentioned before, we would like to take advantage of the fact that
the communities from the different projects will be in the same place at
the same time.  As such, we encourage you to propose sessions that can
further cross-collaboration among the LFN projects.  We also recognize that
there are plenty of project-specific topics that need to be discussed.
Please also propose those sessions for this event.

With the LFN formally announced today, we are working to get the LFN wiki
site up and running as quickly as possible.  One of the first uses for this
site will be the location for submitting your proposed talks and
presentations for the developer event at ONS.  We apologize that it is not
up quite yet but it will be up within the next 2 or 3 days.

Once the site is up, Ray Paik (cc-ed) will send out an email to all
communities on where to find it along with a call-for-presentations for you
to post your discussion and presentation topics.  Between February 9th and
February 15th, we will convene the TAC representatives from the LFN
projects to review the submissions and to form an outline/framework for the
developer event, giving time for cross-project discussions,
project-specific sessions, and a TAC meeting.  From there, we will work
with each project TSC to prioritize project-specific sessions during the
event.

I am looking forward to this first-of-its-kind event and the breadth and
depth of discussions we will have during this week.  Please be preparing
your topics over the coming days and submit them to the LFN wiki once it is
live.

Best regards,

Phil.
-- 
Phil Robb
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Triggering CLM jobs

[DRAGOSH, PAMELA L (PAM)]

Jessica,

Thanks. I have a question on resolving security issues. Sometimes it is an easy 
fix to upgrade to a newer version of a dependency. However, other times there 
was no fix but a work around was in place. Or, it doesn’t apply because the 
method actually isn’t being used by our project. How do we resolve the CLM 
security issue? Do PTL’s have the right to do this (similar to sonar)?

Thanks,

Pam

From:  on behalf of Jessica Wagantall 

Date: Monday, January 22, 2018 at 5:58 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Triggering CLM jobs

Dear ONAP team,

Just to let you know, the CLM jobs can now be triggered on demand after posting
the comment "run-clm" in your Gerrit change.

The CLM jobs are still scheduled to run every Saturday but I hope this feature 
can be
useful for debugging on demand.

Just as a reminder, commenting "run-clm" in a gerrit that is not merged, will 
not trigger
the CLM job based on that revision but will trigger the job based on the tip of 
the branch.
This job is designed to always run on the latest tip of the branch to avoid 
inconsistencies on
the reports.

Please let me know for any questions
Thanks a ton!
Jess.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Bitergia Data Changes

[Kenny Paul]

Actually ci-management needs a bit of a clarifier. I’ll write something up more 
formally for community comment and TSC approval but until then, here is the 
background.

As everyone is aware the scrutiny being applied to proposals last June with 30 
projects going through simultaneously focused more on project fit than 
operational details. This is one of those areas where real-world utilization 
differs from what the TSC approved last year in China. It has just been sitting 
dormant until now.

Technically ci-management is not an integration repo. Instead it belongs to the 
LF Rel-Ops team and not to the community. To date no one outside of the LF team 
has been granted commit approval privs. The fact that the ci-management repo 
was listed as a repo on Integration’s original project proposal was because 
they do indeed need it to do their work. The fact it was approved "as is” is 
just another of the many oversights from the initial batch of project approvals 
that needs to be corrected.  

Such are the growing pains of a new open-source community. :-)

As I said I’ll write something more formal up for comment and approval.


Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

> On Jan 22, 2018, at 3:42 PM, Kenny Paul  wrote:
> 
> None other than I didn’t move them down when I was editing the json file :-)
> I’ll fix it and send another pull request, but I’ll wait for a bit to see if 
> anyone else sees changes that need to be made.
>  
> Best Regards, 
> -kenny
> 
> Kenny Paul,  Technical Program Manager
> kp...@linuxfoundation.org 
> 510.766.5945
> 
>> On Jan 22, 2018, at 2:51 PM, Gildas Lanilis > > wrote:
>> 
>> Hi Kenny,
>>  
>> According to Repositories and Resources Wiki page repos such as   
>> ci-management, demo, oparent belong into Integration project 
>> 
>> According to Bitergia (cf screenshot below), these 3 repos belong to 
>> “ONAP-General” which does not really relates to an ONAP project.
>> 
>> Any reasons? I think these 3 repos should belong to Integration, and we 
>> should get rid of “ONAP-General”.
>>  
>> Thanks,
>> Gildas
>> ONAP Release Manager
>> 1 415 238 6287
>>  
> 

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

Re: [onap-discuss] [AAI][SO] How to add another LCP Region

[FREEMAN, BRIAN D]

OK – I’ll try later. For some reason cd.sh got stuck “waiting for config pod to 
complete” ?

Do I need to update my version of cd.sh ?

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 11:48 AM
To: FREEMAN, BRIAN D 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region

Brian, no it’s not merged yet.

It has been Code-Review +2 and Verified +1, but not submitted yet. It’s 
dependent on some other patch I was testing. I just found my missing piece. 
Expect this to be merge by 1pm.

Thanks for testing, though :)

Thanks,
Alexis


On Jan 23, 2018, at 11:37 AM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:

I think it was merged today (in parallel with your email I suspect).

Trying an cd.sh install now on -b amsterdam to see.

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 11:28 AM
To: FREEMAN, BRIAN D mailto:bf1...@att.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region





On Jan 10, 2018, at 5:56 PM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:


  1.  Robot did not work – trying to patch/work around to use it and it 
partially succeed – could be amsterdam vs master issue

 *   Tried to run robot distribute and the heat templates were missing
 *   Used the following:
   i.  Cd 
/dockerdata-nfs/onap/
 ii.  Git clone 
http://gerrit.onap.org/r/demo
   iii.  Cd demo
   iv.  cp -rf heat 
../robot/eteshare
 v.  this put 
the heat/vFW etc into the heat directory.

 *   After this distribute seems to work partially
   i.  ROBOT 
fails after partially distributing looking for 6 thing and getting 5 – not sure 
what that error is but the models do seem to be distributed to AAI and SO from 
the SDC GUI perspective


Brian, the fix for this is now out: 
https://gerrit.onap.org/r/#/c/28935/

Expect it to be merged in the next few days.

Thanks,
Alexis

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

Re: [onap-discuss] [OOM] DCAE config in windriver

[Alexis de Talhouët]

Right, as I said, expect this to be merged in a couple of hours.

Thanks,
Alexis

> On Jan 23, 2018, at 12:29 PM, Gary Wu  wrote:
> 
> The first patch depends on the second, but the second has not yet been merged 
> yet?  I guess I should wait for the second one to merged first?
>  
> Thanks,
> Gary
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
> Sent: Tuesday, January 23, 2018 8:53 AM
> To: Gary Wu 
> Cc: BRIAN D FREEMAN ; PLATANIA, MARCO (MARCO) 
> ; onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] [OOM] DCAE config in windriver
>  
> Gary,
>  
> This patch fixes the OOM to enable proxy DNS designate setup: 
> https://gerrit.onap.org/r/#/c/28933/ 
>  
> I’ve tested in my environment, it’s working.
>  
> Please try again when you have some time. Note, the onap-parameters.yaml have 
> changed a little bit to enable this. See https://gerrit.onap.org/r/#/c/28591/ 
> 
>  
> Expect this to be merge in a couple of hours.
>  
> Thanks,
> Alexis
> 
> 
> On Jan 22, 2018, at 3:57 PM, Alexis de Talhouët  > wrote:
>  
> Gary,
>  
> OOM doesn’t yet support the proxied solution. This is being worked on; until 
> this is not fix, you cannot use Wind-River lab to deploy OOM with DCAENGEN2.
> Expect the fix to be submit in the next couple of days.
>  
> Thanks,
> Alexis
> 
> 
> On Jan 22, 2018, at 3:17 PM, Gary Wu  > wrote:
>  
> Hi Alexis,
>  
> Yes, I’m able to deploy DCAEGEN2 on a (non-Wind River) system with Designate 
> installed.  My question is specifically on the Wind River lab.  Can we use 
> Designate there?  So far what I see is “public endpoint for dns service in 
> RegionOne region not found”, so it seems like we cannot.  Or is there a 
> special Designate endpoint/config available?
>  
> Has anyone successfully deployed OOM with DCAEGEN2 in the Wind River lab, 
> with or without the proxy solution?
>  
> Thanks,
> Gary
>  
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com 
> ] 
> Sent: Monday, January 22, 2018 11:58 AM
> To: Gary Wu mailto:gary.i...@huawei.com>>
> Cc: BRIAN D FREEMAN mailto:bf1...@att.com>>; PLATANIA, MARCO 
> (MARCO) mailto:plata...@research.att.com>>; 
> onap-discuss@lists.onap.org 
> Subject: Re: [onap-discuss] [OOM] DCAE config in windriver
>  
> Hi Gary,
>  
> I noticed the proxy solution that DCAEGEN2 offers is not fully working yet 
> with OOM. What is working is having DCAE on the same OpenStack as DNS 
> Designate. I’m currently in the process of addressing this.
>  
> Regarding your question about how "vm1.aai.simpledemo.onap.org 
>  gets resolves, we create a zone in 
> Designate for simpledemo.onap.org , see 
> https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/entrypoint.sh;h=85c5ee2b131458f7f25cab3c8efc4071b22775f5;hb=refs/heads/amsterdam
>  
> 
> And we added a reverse proxy so the lookup returns the IP of the K8S host 
> running the reverse-proxy, and the service port are opened.
>  
> See bellow design implemented:
>  
> 
>  
>  
> Thanks,
> Alexis
> 
> 
> 
> On Jan 22, 2018, at 2:00 PM, Gary Wu  > wrote:
>  
> Hi Alexis and Brian,
> 
> How should we currently spin up DCAEGEN2 using OOM in Wind River lab?
> 
> I assume we're supposed to set DNSAAS_PROXY_ENABLE to "true".  However, when 
> this is done, my dcae-dcae-boostrap VM gets stuck on wait_for_aai_ready() 
> since it's unable to resolve the hostname "vm1.aai.simpledemo.onap.org 
> ", and none of the DNSAAS-related code 
> in dcae_vm_init.sh gets triggered since they only occur after 
> wait_for_aai_ready().
> 
> Is there additional config/init that we're supposed to do to get 
> vm1.aai.simpledemo.onap.org  to resolve 
> in this VM?
> 
> Thanks,
> Gary
> 
> -Original Message-
> From: onap-discuss-boun...@lists.onap.org 
>  
> [mailto:onap-discuss-boun...@lists.onap.org 
> ] On Behalf Of Alexis de Talhouët
> Sent: Monday, January 22, 2018 6:48 AM
> To: BRIAN D FREEMAN mailto:bf1...@att.com>>
> Cc: onap-discuss@lists.onap.org 
> Subject: Re: [onap-discuss] [OOM] DCAE status in non-openstack clouds ?
> 
> Brian,
> 
> DCAE deployment in Amsterdam is coupled to OpenStack cloud, and we’re not in 
> the process of supporting other cloud for now.
> This could be an enhancement for Beijing, if DCAE still runs in VMs. And if 
> we do such implementatio

Re: [onap-discuss] [OOM] DCAE config in windriver

[Gary Wu]

The first patch depends on the second, but the second has not yet been merged 
yet?  I guess I should wait for the second one to merged first?

Thanks,
Gary

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 8:53 AM
To: Gary Wu 
Cc: BRIAN D FREEMAN ; PLATANIA, MARCO (MARCO) 
; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE config in windriver

Gary,

This patch fixes the OOM to enable proxy DNS designate setup: 
https://gerrit.onap.org/r/#/c/28933/

I’ve tested in my environment, it’s working.

Please try again when you have some time. Note, the onap-parameters.yaml have 
changed a little bit to enable this. See https://gerrit.onap.org/r/#/c/28591/

Expect this to be merge in a couple of hours.

Thanks,
Alexis


On Jan 22, 2018, at 3:57 PM, Alexis de Talhouët 
mailto:adetalhoue...@gmail.com>> wrote:

Gary,

OOM doesn’t yet support the proxied solution. This is being worked on; until 
this is not fix, you cannot use Wind-River lab to deploy OOM with DCAENGEN2.
Expect the fix to be submit in the next couple of days.

Thanks,
Alexis


On Jan 22, 2018, at 3:17 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

Hi Alexis,

Yes, I’m able to deploy DCAEGEN2 on a (non-Wind River) system with Designate 
installed.  My question is specifically on the Wind River lab.  Can we use 
Designate there?  So far what I see is “public endpoint for dns service in 
RegionOne region not found”, so it seems like we cannot.  Or is there a special 
Designate endpoint/config available?

Has anyone successfully deployed OOM with DCAEGEN2 in the Wind River lab, with 
or without the proxy solution?

Thanks,
Gary


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Monday, January 22, 2018 11:58 AM
To: Gary Wu mailto:gary.i...@huawei.com>>
Cc: BRIAN D FREEMAN mailto:bf1...@att.com>>; PLATANIA, MARCO 
(MARCO) mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE config in windriver

Hi Gary,

I noticed the proxy solution that DCAEGEN2 offers is not fully working yet with 
OOM. What is working is having DCAE on the same OpenStack as DNS Designate. I’m 
currently in the process of addressing this.

Regarding your question about how 
"vm1.aai.simpledemo.onap.org gets 
resolves, we create a zone in Designate for 
simpledemo.onap.org, see 
https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/entrypoint.sh;h=85c5ee2b131458f7f25cab3c8efc4071b22775f5;hb=refs/heads/amsterdam
And we added a reverse proxy so the lookup returns the IP of the K8S host 
running the reverse-proxy, and the service port are opened.

See bellow design implemented:




Thanks,
Alexis



On Jan 22, 2018, at 2:00 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

Hi Alexis and Brian,

How should we currently spin up DCAEGEN2 using OOM in Wind River lab?

I assume we're supposed to set DNSAAS_PROXY_ENABLE to "true".  However, when 
this is done, my dcae-dcae-boostrap VM gets stuck on wait_for_aai_ready() since 
it's unable to resolve the hostname 
"vm1.aai.simpledemo.onap.org", and none of 
the DNSAAS-related code in dcae_vm_init.sh gets triggered since they only occur 
after wait_for_aai_ready().

Is there additional config/init that we're supposed to do to get 
vm1.aai.simpledemo.onap.org to resolve in 
this VM?

Thanks,
Gary

-Original Message-
From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Monday, January 22, 2018 6:48 AM
To: BRIAN D FREEMAN mailto:bf1...@att.com>>
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE status in non-openstack clouds ?

Brian,

DCAE deployment in Amsterdam is coupled to OpenStack cloud, and we’re not in 
the process of supporting other cloud for now.
This could be an enhancement for Beijing, if DCAE still runs in VMs. And if we 
do such implementation, we should leverage Multicloud interfaces to do so.

Prior to this, we should flush out the requirement of DCAE deployment on 
different type of cloud, what are the implications and so on.

Alexis



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

Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod lab

[Alexis de Talhouët]

# #
# OpenStack Config on which DCAE will be deployed #
# #

# --- 
# Either v2.0 or v3
DCAE_OS_API_VERSION: "v2.0"
DCAE_OS_KEYSTONE_URL: "http://10.1.1.5:5000";
DCAE_OS_USERNAME: "nso"
DCAE_OS_PASSWORD: "Password"
DCAE_OS_TENANT_NAME: "nso-rancher"
DCAE_OS_TENANT_ID: "21ca0f4c2239475fb1b4b499399163e"
DCAE_OS_REGION: "RegionOne"
# — 

That section let you provide the information for the OpenStack on which to 
deploy DCAE. If that OpenStack instance has Designate, then 
# Proxy DNS Designate. This means DCAE will run in an instance not support 
Designate, and Designate will be provided by another instance.
# Set to true if you wish to use it
DNSAAS_PROXY_ENABLE: “true"

Will be set to false, and that OpenStack will be used for DNS Designate support.

Hope this clarifies things,
Alexis

> On Jan 23, 2018, at 12:00 PM, Kranthi Guttikonda 
>  wrote:
> 
> Hi Alexis,
>  
> I have couple of questions. Pardon me.
>  
> # Whether or not to deploy DCAE
> # If set to false, all the parameters bellow can be left empty or removed
> # If set to false, update ../dcaegen2/values.yaml disableDcae value to true, 
> //Is it possible to elaborate this???
> # this is to avoid deploying the DCAE deployments and services.
> DEPLOY_DCAE: "true"
>  
> # In the HEAT setup, it's meant to be a DNS list, as the HEAT setup deploys a 
> DNS Server VM in addition to DNS Designate
> # and this DNS Server is setup to forward request to the DNS Designate 
> backend when it cannot resolve, hence the
> # DNS_FORWARDER config here. The DCAE Boostrap requires both inputs, even 
> though they are now similar, we have to pass
> # them.
> # -
> # ATTENTION: Assumption is made the DNS Designate backend is configure to 
> forward request to a public DNS (e.g. 8.8.8.8)
> # -
> # Put the IP of the DNS Designate backend (e.g. the OpenStack IP supporting 
> DNS Designate)
> DNS_LIST : "10.1.1.16"
> DNS_FORWARDER: "10.1.1.16"
>  
> If DNS designate is available (not using proxy) then can’t we directly give 
> the DNS designate URL to DCAE instead querying that from keystone/openstack 
> services? I mean we can pass the direct API url to DCAE scripts. Just 
> wondering.
>  
> Thanks,
> Kranthi
>  
> From:  > on behalf of Alexis de Talhouët 
> mailto:adetalhoue...@gmail.com>>
> Date: Tuesday, January 23, 2018 at 11:09 AM
> To: Gary Wu mailto:gary.i...@huawei.com>>
> Cc: onap-discuss  >
> Subject: Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod lab
>  
> Hello guys,  <>
>  
> Could you provide feedback on this updated version of onap-parameters.yaml? 
> https://gerrit.onap.org/r/#/c/28591/5/kubernetes/config/onap-parameters-sample.yaml
>  
> 
>  
> It’s under review, and I’d love a little but a feedback. I added a lot of 
> comments explaining what are the param to give. Please let me know if it 
> helps and does answer your questions.
>  
> Thanks,
> Alexis
> 
> 
> On Jan 18, 2018, at 12:59 PM, Alexis de Talhouët  > wrote:
>  
> Gary, 
>  
> For now Amsterdam branch has been highly tested. I’m starting the work on the 
> master branch.
> So please use Amsterdam branch for now.
>  
> Regarding the issue you faced with the init container, this should be fix 
> now.You could try to re-pull the config-init:2.0.0-SNAPSHOT image (for master)
>  
> The config container does provision directory, and it does also a bunch of 
> sed command to inject parameters, Those sed commands is what is taking most 
> of the time, because we loop blindly over all the directories, instead of 
> targeting the sed more precisely. I’m currently working on improving this for 
> Amsterdam, and will cherry-pick on master once ready.
>  
> Thanks,
> Alexis
> 
> 
> On Jan 18, 2018, at 12:49 PM, Gary Wu  > wrote:
>  
> Are we mainly testing against OOM amsterdam branch, or master?
>  
> In the master branch, the config container complains about other parameters 
> missing like NEXUS_REPO or something.  Is the OOM master branch stable enough 
> for us to try now?  If so, can you share your sample parameters file for the 
> master branch?
>  
> As an aside, does anyone know why the config container takes 2 to 3 minutes 
> to complete?  Seems to be a long time for creating shared config directories, 
> or maybe my environment is not set up right somehow.
> 
> Thanks,
> Gary
>  
> From: onap-discuss-boun...@lists.onap.org 
>  
> [mailto:onap-discuss-boun...@lists.onap.org 
> ] On Behalf Of Alexis de Talhouët
> Sent: Thursday, January 18, 2018 9:14 AM
> To: PLATANIA, MARCO (MARCO)  >
> Cc: onap-discuss  >

Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod lab

[Kranthi Guttikonda]

Hi Alexis,

I have couple of questions. Pardon me.

# Whether or not to deploy DCAE
# If set to false, all the parameters bellow can be left empty or removed
# If set to false, update ../dcaegen2/values.yaml disableDcae value to true, 
//Is it possible to elaborate this???
# this is to avoid deploying the DCAE deployments and services.
DEPLOY_DCAE: "true"

# In the HEAT setup, it's meant to be a DNS list, as the HEAT setup deploys a 
DNS Server VM in addition to DNS Designate
# and this DNS Server is setup to forward request to the DNS Designate backend 
when it cannot resolve, hence the
# DNS_FORWARDER config here. The DCAE Boostrap requires both inputs, even 
though they are now similar, we have to pass
# them.
# -
# ATTENTION: Assumption is made the DNS Designate backend is configure to 
forward request to a public DNS (e.g. 8.8.8.8)
# -
# Put the IP of the DNS Designate backend (e.g. the OpenStack IP supporting DNS 
Designate)
DNS_LIST : "10.1.1.16"
DNS_FORWARDER: "10.1.1.16"

If DNS designate is available (not using proxy) then can’t we directly give the 
DNS designate URL to DCAE instead querying that from keystone/openstack 
services? I mean we can pass the direct API url to DCAE scripts. Just wondering.

Thanks,
Kranthi

From:  on behalf of Alexis de Talhouët 

Date: Tuesday, January 23, 2018 at 11:09 AM
To: Gary Wu 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod lab

Hello guys,

Could you provide feedback on this updated version of onap-parameters.yaml? 
https://gerrit.onap.org/r/#/c/28591/5/kubernetes/config/onap-parameters-sample.yaml

It’s under review, and I’d love a little but a feedback. I added a lot of 
comments explaining what are the param to give. Please let me know if it helps 
and does answer your questions.

Thanks,
Alexis


On Jan 18, 2018, at 12:59 PM, Alexis de Talhouët 
mailto:adetalhoue...@gmail.com>> wrote:

Gary,

For now Amsterdam branch has been highly tested. I’m starting the work on the 
master branch.
So please use Amsterdam branch for now.

Regarding the issue you faced with the init container, this should be fix 
now.You could try to re-pull the config-init:2.0.0-SNAPSHOT image (for master)

The config container does provision directory, and it does also a bunch of sed 
command to inject parameters, Those sed commands is what is taking most of the 
time, because we loop blindly over all the directories, instead of targeting 
the sed more precisely. I’m currently working on improving this for Amsterdam, 
and will cherry-pick on master once ready.

Thanks,
Alexis


On Jan 18, 2018, at 12:49 PM, Gary Wu 
mailto:gary.i...@huawei.com>> wrote:

Are we mainly testing against OOM amsterdam branch, or master?

In the master branch, the config container complains about other parameters 
missing like NEXUS_REPO or something.  Is the OOM master branch stable enough 
for us to try now?  If so, can you share your sample parameters file for the 
master branch?

As an aside, does anyone know why the config container takes 2 to 3 minutes to 
complete?  Seems to be a long time for creating shared config directories, or 
maybe my environment is not set up right somehow.

Thanks,
Gary

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Thursday, January 18, 2018 9:14 AM
To: PLATANIA, MARCO (MARCO) 
mailto:plata...@research.att.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod lab

Marco,

Well that’s the thing I’m currently looking at. I know Robot needs them for 
whatever reason.

I’m currently about to test a deployment without those parameters, because as 
you pointed out, they don’t necessarily make sense for OOM.

I have to validate this, but I’m validating other thing at the same time. 
Because with the introduction of DCAE, we potentially can configure tree 
different OpenStack:

- 1 where to deploy VNF
- 1 where to deploy DCAE
- 1 where DNS Designate is supported

So I’m re-doing the onap-parameters.yaml to take this in consideration. Note, 
it could also be the same OpenStack instance for all of them, but as the 
flexibility is giving to us
by DCAE, let’s leverage this.

Moreover, this separation is useful when going in prod.

Alexis



On Jan 18, 2018, at 12:06 PM, PLATANIA, MARCO (MARCO) 
mailto:plata...@research.att.com>> wrote:

Alexis,

What are these parameters used for in OOM?

OPENSTACK_UBUNTU_14_IMAGE: "ubuntu-14-04-cloud-amd64"
OPENSTACK_PUBLIC_NET_ID: "971040b2-7059-49dc-b220-4fab50cb2ad4"
OPENSTACK_OAM_NETWORK_ID: "31b5d82c-bfd3-44bf-a830-4bc0b628013f"
OPENSTACK_OAM_SUBNET_ID: "658d0e1b-8e2c-45c3-94e3-e7a1df1ed475"
OPENSTACK_OAM_NETWORK_CIDR: "10.10.2.0/24"

We had them for Heat, to tell the Orchestrator what image and network to use 
when creating ONAP VMs. For vFW/vLB use cases, those parameters are passed as 
SDNC pre

[onap-discuss] [OOM][Amsterdam] It's getting stable - HEAT feature parity

[Alexis de Talhouët]

Hi OOM team,

I think we have all the outstanding bugs for Amsterdam being addressed here: 
https://gerrit.onap.org/r/#/q/status:open+project:oom+branch:amsterdam

We support both DCAEGEN2 deployment solution: the standalone one, and the 
proxied one.

There is still one to be done, OOM-604, that is update the docker version to 
latest Amsterdam Maintenance Release.

Once done, I’ll make sure to back-port all those fixes in master.

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

Re: [onap-discuss] [**EXTERNAL**] Service distribution error on latest ONAP/OOM

[Alexis de Talhouët]

Karthick,

The fix is out: https://gerrit.onap.org/r/#/c/28591/ and has been tested.
Expect this to be merge on a couple of hours.

Please re-test and confirm it does fix your issue when you have time.

Regards,
Alexis

> On Jan 22, 2018, at 11:57 AM, Ramanarayanan, Karthick  
> wrote:
> 
> That's great Alexis.
> Thanks.
> (also don't be surprised if backend doesn't come up sometimes with no 
> indicator in the log pods.
>  Just restart cassandra, elastic search and kibana pod before restarting 
> backend pod and it would load the user profiles in the sdc-be logs :)
> 
> Regards,
> -Karthick
> From: Alexis de Talhouët 
> Sent: Monday, January 22, 2018 5:10:26 AM
> To: Ramanarayanan, Karthick
> Cc: onap-discuss@lists.onap.org; Bainbridge, David
> Subject: Re: [**EXTERNAL**] [onap-discuss] Service distribution error on 
> latest ONAP/OOM
>  
> Hi Karthick,
> 
> Yes, I’m aware of this since you mentioned it last week. I reproduced the 
> issue.
> Currently implementing a fix for it. Sorry for the regression introduced.
> 
> See https://jira.onap.org/browse/OOM-608 
> 
>  for more details.
> 
> Thanks,
> Alexis
> 
>> On Jan 19, 2018, at 4:21 PM, Ramanarayanan, Karthick > > wrote:
>> 
>> Hi Alexis,
>>  I reverted the oom commit from head to:
>> 
>> git checkout cb02aa241edd97acb6c5ca744de84313f53e8a5a
>> 
>> Author: yuryn mailto:yury.novit...@amdocs.com>>
>> Date:   Thu Dec 21 14:31:21 2017 +0200
>> 
>> Fix firefox tab crashes in VNC
>> 
>> Change-Id: Ie295257d98ddf32693309535e15c6ad9529f10fc
>> Issue-ID: OOM-531
>> 
>> 
>> Everything works with service creation, vnf and vf creates! 
>> Please note that I am running with dcae disabled.
>> Something is broken with dcae disabled in the latest.
>> 100% reproducible with service distribution step through operator taking a 
>> policy exception mailed earlier.
>> Have a nice weekend.
>> 
>> Regards,
>> -Karthick
>> 
>> 
>> 
>>   
>> From: Ramanarayanan, Karthick
>> Sent: Friday, January 19, 2018 8:48:23 AM
>> To: Alexis de Talhouët
>> Cc: onap-discuss@lists.onap.org 
>> Subject: Re: [**EXTERNAL**] Re: [onap-discuss] Service distribution error on 
>> latest ONAP/OOM
>>  
>> Hi Alexis,
>>  I did check the policy pod logs before sending the mail. 
>>  I didn't see anything suspicious.
>>  I initially suspected aai-service dns not getting resolved but you seem to 
>> have fixed it
>>  and it was accessible from policy pod.
>>  Nothing suspicious from any log anywhere.
>>  I did see that the health check on sdc pods returned all UP except: DE 
>> component whose health check was down. 
>>  Not sure if its anyway related. Could be benign.
>> 
>> curl http://127.0.0.1:30206/sdc1/rest/healthCheck 
>> 
>> {
>>  "sdcVersion": "1.1.0",
>>  "siteMode": "unknown",
>>  "componentsInfo": [
>>{
>>  "healthCheckComponent": "BE",
>>  "healthCheckStatus": "UP",
>>  "version": "1.1.0",
>>  "description": "OK"
>>},
>>{
>>  "healthCheckComponent": "TITAN",
>>  "healthCheckStatus": "UP",
>>  "description": "OK"
>>},
>>{
>>  "healthCheckComponent": "DE",
>>  "healthCheckStatus": "DOWN",
>>  "description": "U-EB cluster is not available"
>>},
>>{
>>  "healthCheckComponent": "CASSANDRA",
>>  "healthCheckStatus": "UP",
>>  "description": "OK"
>>},
>>{
>>  "healthCheckComponent": "ON_BOARDING",
>>  "healthCheckStatus": "UP",
>>  "version": "1.1.0",
>>  "description": "OK",
>>  "componentsInfo": [
>>{
>>  "healthCheckComponent": "ZU",
>>  "healthCheckStatus": "UP",
>>  "version": "0.2.0",
>>  "description": "OK"
>>},
>>{
>>  "healthCheckComponent": "BE",
>>  "healthCheckStatus": "UP",
>>  "version": "1.1.0",
>>  "description": "OK"
>>},
>>{
>>  "healthCheckComponent": "CAS",
>>  "healthCheckStatus": "UP",
>>  "version": "2.1.17",
>>  "description": "OK"
>>},
>>{
>>  "healthCheckComponent": "FE",
>>  "healthCheckStatus": "UP",
>>  "version": "1.1.0",
>>  "description": "OK"
>>}
>>  ]
>>},
>>{
>>  "healthCheckComponent": "FE",
>>  "healthCheckStatus": "UP",
>>  "version": "1.1.0",
>>  "description": "OK"
>>}
>>  ]
>> 
>> 
>> On some occasions backend doesn't come up even though po

Re: [onap-discuss] [OOM] DCAE config in windriver

[Alexis de Talhouët]

Gary,

This patch fixes the OOM to enable proxy DNS designate setup: 
https://gerrit.onap.org/r/#/c/28933/

I’ve tested in my environment, it’s working.

Please try again when you have some time. Note, the onap-parameters.yaml have 
changed a little bit to enable this. See https://gerrit.onap.org/r/#/c/28591/

Expect this to be merge in a couple of hours.

Thanks,
Alexis

> On Jan 22, 2018, at 3:57 PM, Alexis de Talhouët  
> wrote:
> 
> Gary,
> 
> OOM doesn’t yet support the proxied solution. This is being worked on; until 
> this is not fix, you cannot use Wind-River lab to deploy OOM with DCAENGEN2.
> Expect the fix to be submit in the next couple of days.
> 
> Thanks,
> Alexis
> 
>> On Jan 22, 2018, at 3:17 PM, Gary Wu > > wrote:
>> 
>> Hi Alexis,
>>  
>> Yes, I’m able to deploy DCAEGEN2 on a (non-Wind River) system with Designate 
>> installed.  My question is specifically on the Wind River lab.  Can we use 
>> Designate there?  So far what I see is “public endpoint for dns service in 
>> RegionOne region not found”, so it seems like we cannot.  Or is there a 
>> special Designate endpoint/config available?
>>  
>> Has anyone successfully deployed OOM with DCAEGEN2 in the Wind River lab, 
>> with or without the proxy solution?
>>  
>> Thanks,
>> Gary
>>  
>>  
>> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com 
>> ] 
>> Sent: Monday, January 22, 2018 11:58 AM
>> To: Gary Wu mailto:gary.i...@huawei.com>>
>> Cc: BRIAN D FREEMAN mailto:bf1...@att.com>>; PLATANIA, 
>> MARCO (MARCO) > >; onap-discuss@lists.onap.org 
>> 
>> Subject: Re: [onap-discuss] [OOM] DCAE config in windriver
>>  
>> Hi Gary,
>>  
>> I noticed the proxy solution that DCAEGEN2 offers is not fully working yet 
>> with OOM. What is working is having DCAE on the same OpenStack as DNS 
>> Designate. I’m currently in the process of addressing this.
>>  
>> Regarding your question about how "vm1.aai.simpledemo.onap.org 
>>  gets resolves, we create a zone in 
>> Designate for simpledemo.onap.org , see 
>> https://gerrit.onap.org/r/gitweb?p=oom.git;a=blob;f=kubernetes/config/docker/init/src/config/dcaegen2/heat/entrypoint.sh;h=85c5ee2b131458f7f25cab3c8efc4071b22775f5;hb=refs/heads/amsterdam
>>  
>> 
>> And we added a reverse proxy so the lookup returns the IP of the K8S host 
>> running the reverse-proxy, and the service port are opened.
>>  
>> See bellow design implemented:
>>  
>> 
>>  
>>  
>> Thanks,
>> Alexis
>> 
>> 
>> On Jan 22, 2018, at 2:00 PM, Gary Wu > > wrote:
>>  
>> Hi Alexis and Brian,
>> 
>> How should we currently spin up DCAEGEN2 using OOM in Wind River lab?
>> 
>> I assume we're supposed to set DNSAAS_PROXY_ENABLE to "true".  However, when 
>> this is done, my dcae-dcae-boostrap VM gets stuck on wait_for_aai_ready() 
>> since it's unable to resolve the hostname "vm1.aai.simpledemo.onap.org 
>> ", and none of the DNSAAS-related code 
>> in dcae_vm_init.sh gets triggered since they only occur after 
>> wait_for_aai_ready().
>> 
>> Is there additional config/init that we're supposed to do to get 
>> vm1.aai.simpledemo.onap.org  to resolve 
>> in this VM?
>> 
>> Thanks,
>> Gary
>> 
>> -Original Message-
>> From: onap-discuss-boun...@lists.onap.org 
>>  
>> [mailto:onap-discuss-boun...@lists.onap.org 
>> ] On Behalf Of Alexis de Talhouët
>> Sent: Monday, January 22, 2018 6:48 AM
>> To: BRIAN D FREEMAN mailto:bf1...@att.com>>
>> Cc: onap-discuss@lists.onap.org 
>> Subject: Re: [onap-discuss] [OOM] DCAE status in non-openstack clouds ?
>> 
>> Brian,
>> 
>> DCAE deployment in Amsterdam is coupled to OpenStack cloud, and we’re not in 
>> the process of supporting other cloud for now.
>> This could be an enhancement for Beijing, if DCAE still runs in VMs. And if 
>> we do such implementation, we should leverage Multicloud interfaces to do so.
>> 
>> Prior to this, we should flush out the requirement of DCAE deployment on 
>> different type of cloud, what are the implications and so on.
>> 
>> Alexis
>> 
>>  
> 

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

Re: [onap-discuss] [AAI][SO] How to add another LCP Region

[Alexis de Talhouët]

Brian, no it’s not merged yet.

It has been Code-Review +2 and Verified +1, but not submitted yet. It’s 
dependent on some other patch I was testing. I just found my missing piece. 
Expect this to be merge by 1pm.

Thanks for testing, though :)

Thanks,
Alexis

> On Jan 23, 2018, at 11:37 AM, FREEMAN, BRIAN D  wrote:
> 
> I think it was merged today (in parallel with your email I suspect).
>  
> Trying an cd.sh install now on -b amsterdam to see.
>  
> Brian
>  
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
> Sent: Tuesday, January 23, 2018 11:28 AM
> To: FREEMAN, BRIAN D 
> Cc: onap-discuss 
> Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region
>  
>  
> 
> 
> On Jan 10, 2018, at 5:56 PM, FREEMAN, BRIAN D  > wrote:
>  
> Robot did not work – trying to patch/work around to use it and it partially 
> succeed – could be amsterdam vs master issue
> Tried to run robot distribute and the heat templates were missing
> Used the following:
>i.  Cd 
> /dockerdata-nfs/onap/
>  ii.  Git 
> clone http://gerrit.onap.org/r/demo 
> 
>iii.  Cd demo
>iv.  cp -rf 
> heat ../robot/eteshare
>  v.  this put 
> the heat/vFW etc into the heat directory.
> After this distribute seems to work partially
>i.  ROBOT 
> fails after partially distributing looking for 6 thing and getting 5 – not 
> sure what that error is but the models do seem to be distributed to AAI and 
> SO from the SDC GUI perspective
>  
>  
> Brian, the fix for this is now out: https://gerrit.onap.org/r/#/c/28935/ 
> 
>  
> Expect it to be merged in the next few days.
>  
> Thanks,
> Alexis

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

Re: [onap-discuss] [AAI][SO] How to add another LCP Region

[FREEMAN, BRIAN D]

I think it was merged today (in parallel with your email I suspect).

Trying an cd.sh install now on -b amsterdam to see.

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 23, 2018 11:28 AM
To: FREEMAN, BRIAN D 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [AAI][SO] How to add another LCP Region




On Jan 10, 2018, at 5:56 PM, FREEMAN, BRIAN D 
mailto:bf1...@att.com>> wrote:


  1.  Robot did not work – trying to patch/work around to use it and it 
partially succeed – could be amsterdam vs master issue

 *   Tried to run robot distribute and the heat templates were missing
 *   Used the following:
   i.  Cd 
/dockerdata-nfs/onap/
 ii.  Git clone 
http://gerrit.onap.org/r/demo
   iii.  Cd demo
   iv.  cp -rf heat 
../robot/eteshare
 v.  this put 
the heat/vFW etc into the heat directory.

 *   After this distribute seems to work partially
   i.  ROBOT 
fails after partially distributing looking for 6 thing and getting 5 – not sure 
what that error is but the models do seem to be distributed to AAI and SO from 
the SDC GUI perspective


Brian, the fix for this is now out: 
https://gerrit.onap.org/r/#/c/28935/

Expect it to be merged in the next few days.

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

Re: [onap-discuss] [AAI][SO] How to add another LCP Region

[Alexis de Talhouët]

> On Jan 10, 2018, at 5:56 PM, FREEMAN, BRIAN D  wrote:
> 
> Robot did not work – trying to patch/work around to use it and it partially 
> succeed – could be amsterdam vs master issue
> Tried to run robot distribute and the heat templates were missing
> Used the following:
>i.  Cd 
> /dockerdata-nfs/onap/
>  ii.  Git 
> clone http://gerrit.onap.org/r/demo 
>iii.  Cd demo
>iv.  cp -rf 
> heat ../robot/eteshare
>  v.  this put 
> the heat/vFW etc into the heat directory.
> After this distribute seems to work partially
>i.  ROBOT 
> fails after partially distributing looking for 6 thing and getting 5 – not 
> sure what that error is but the models do seem to be distributed to AAI and 
> SO from the SDC GUI perspective


Brian, the fix for this is now out: https://gerrit.onap.org/r/#/c/28935/

Expect it to be merged in the next few days.

Thanks,
Alexis___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfrqts] Beijing Release Sprint planning

[WRIGHT, STEVEN A]

I've made a first pass of allocating the current set of tasks across the 
sprints remaining for the current release. Please review and email me any 
comments or bring to the next weekly project team meeting. I'm particularly 
interested to break down some of the user stories into more manageable tasks 
that we can knock out in the early sprints. We have a significant amount of 
work to do and I'd prefer to avoid last minute rearrangements  as we get 
towards the end of the release where we will also need to pick up the planning 
activities for the Casablanca release.


best regards
Steven Wright, MBA, PhD, JD.
[Tech Integration]
AT&T Services Inc.
1057 Lenox Park Blvd NE, STE 4D28
Atlanta, GA 30319
P: 470.415.3156

sw3...@att.com
www.linkedin.com/in/drstevenawright/

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

Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod lab

[Alexis de Talhouët]

Hello guys,

Could you provide feedback on this updated version of onap-parameters.yaml? 
https://gerrit.onap.org/r/#/c/28591/5/kubernetes/config/onap-parameters-sample.yaml

It’s under review, and I’d love a little but a feedback. I added a lot of 
comments explaining what are the param to give. Please let me know if it helps 
and does answer your questions.

Thanks,
Alexis

> On Jan 18, 2018, at 12:59 PM, Alexis de Talhouët  
> wrote:
> 
> Gary,
> 
> For now Amsterdam branch has been highly tested. I’m starting the work on the 
> master branch.
> So please use Amsterdam branch for now.
> 
> Regarding the issue you faced with the init container, this should be fix 
> now.You could try to re-pull the config-init:2.0.0-SNAPSHOT image (for master)
> 
> The config container does provision directory, and it does also a bunch of 
> sed command to inject parameters, Those sed commands is what is taking most 
> of the time, because we loop blindly over all the directories, instead of 
> targeting the sed more precisely. I’m currently working on improving this for 
> Amsterdam, and will cherry-pick on master once ready.
> 
> Thanks,
> Alexis
> 
>> On Jan 18, 2018, at 12:49 PM, Gary Wu > > wrote:
>> 
>> Are we mainly testing against OOM amsterdam branch, or master?
>>  
>> In the master branch, the config container complains about other parameters 
>> missing like NEXUS_REPO or something.  Is the OOM master branch stable 
>> enough for us to try now?  If so, can you share your sample parameters file 
>> for the master branch?
>>  
>> As an aside, does anyone know why the config container takes 2 to 3 minutes 
>> to complete?  Seems to be a long time for creating shared config 
>> directories, or maybe my environment is not set up right somehow.
>> 
>> Thanks,
>> Gary
>>  
>> From: onap-discuss-boun...@lists.onap.org 
>>  
>> [mailto:onap-discuss-boun...@lists.onap.org 
>> ] On Behalf Of Alexis de Talhouët
>> Sent: Thursday, January 18, 2018 9:14 AM
>> To: PLATANIA, MARCO (MARCO) > >
>> Cc: onap-discuss > >
>> Subject: Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod 
>> lab
>>  
>> Marco,
>>  
>> Well that’s the thing I’m currently looking at. I know Robot needs them for 
>> whatever reason.
>>  
>> I’m currently about to test a deployment without those parameters, because 
>> as you pointed out, they don’t necessarily make sense for OOM.
>>  
>> I have to validate this, but I’m validating other thing at the same time. 
>> Because with the introduction of DCAE, we potentially can configure tree 
>> different OpenStack:
>>  
>> - 1 where to deploy VNF
>> - 1 where to deploy DCAE
>> - 1 where DNS Designate is supported
>>  
>> So I’m re-doing the onap-parameters.yaml to take this in consideration. 
>> Note, it could also be the same OpenStack instance for all of them, but as 
>> the flexibility is giving to us
>> by DCAE, let’s leverage this.
>>  
>> Moreover, this separation is useful when going in prod.
>>  
>> Alexis
>> 
>> 
>> On Jan 18, 2018, at 12:06 PM, PLATANIA, MARCO (MARCO) 
>> mailto:plata...@research.att.com>> wrote:
>>  
>> Alexis,
>>  
>> What are these parameters used for in OOM?
>>  
>> OPENSTACK_UBUNTU_14_IMAGE: "ubuntu-14-04-cloud-amd64"
>> OPENSTACK_PUBLIC_NET_ID: "971040b2-7059-49dc-b220-4fab50cb2ad4"
>> OPENSTACK_OAM_NETWORK_ID: "31b5d82c-bfd3-44bf-a830-4bc0b628013f"
>> OPENSTACK_OAM_SUBNET_ID: "658d0e1b-8e2c-45c3-94e3-e7a1df1ed475"
>> OPENSTACK_OAM_NETWORK_CIDR: "10.10.2.0/24"
>>  
>> We had them for Heat, to tell the Orchestrator what image and network to use 
>> when creating ONAP VMs. For vFW/vLB use cases, those parameters are passed 
>> as SDNC preload.
>>  
>> Marco
>>  
>> From: > > on behalf of Alexis de 
>> Talhouët mailto:adetalhoue...@gmail.com>>
>> Date: Thursday, January 18, 2018 at 11:47 AM
>> To: Pavel Paroulek mailto:parou...@objectify.sk>>
>> Cc: onap-discuss > >
>> Subject: Re: [onap-discuss] [**EXTERNAL**] oom openstack config in the pod 
>> lab
>>  
>> Hi,
>>  
>> I don’t know which tenant you’re using, but for the OOM tenant, here is my 
>> onap-parameters.yaml file.
>>  
>> Note: this was my parameters two months ago, I do not guarantee the values 
>> are still accurate.
>>  
>> # Look at the images
>> OPENSTACK_UBUNTU_14_IMAGE: "ubuntu-14-04-cloud-amd64"
>> # Look at the networks
>> OPENSTACK_PUBLIC_NET_ID: "971040b2-7059-49dc-b220-4fab50cb2ad4"
>> OPENSTACK_OAM_NETWORK_ID: "31b5d82c-bfd3-44bf-a830-4bc0b628013f"
>> OPENSTACK_OAM_SUBNET_ID: "658d0e1b-8e2c-45c3-94e3-e7a1df1ed475"
>> OPENSTACK_OAM_NETWORK_CIDR: "10.10.2.0/24"
>> # your credentials
>> OPENSTACK_USERNAME: “YOUR_USER"
>> OPENSTACK_API_KEY: “YOUR_PASSWORD"
>> # the tenant to use, the name and id
>> OPENSTACK_TENANT_NAME: "OOM"
>> OPEN

Re: [onap-discuss] Bitergia Data Changes

[Kenny Paul]

Followed up with LiZi on this in a different thread. Reposting here for 
onap-discuss benefit.
Either this was a filter issue or it took 24 hrs for all of the data to be 
populated because I see commits going back to Aug 6 (pacific time) in git view 
if I look at the past 6 months of data.


Best Regards, 
-kenny

Kenny Paul,  Technical Program Manager
kp...@linuxfoundation.org
510.766.5945

> On Jan 22, 2018, at 5:23 PM,   wrote:
> 
> Dear Kenny,
> 
> 
> 
> After reviewed the https://onap.biterg.io  . I found 
> that the statistic data about aai/esr-server and aai/esr-gui repository is 
> from Jan 9, 2018. Actually, the statistic data should be start from Aug 
> 7,2017 and ESR has been released in Amsterdam Release and make a success. The 
> code submit history see 
> https://gerrit.onap.org/r/gitweb?p=aai%2Fesr-server.git;a=summary 
>   and 
> https://gerrit.onap.org/r/gitweb?p=aai%2Fesr-gui.git;a=summary 
>  .
> 
> I think the data about ESR in biterg is incorrect. Could you be kindly fix 
> that?
> 
> 
> 
> Thanks,
> 
> LiZi
> 
> 
> 
> 
> 
> 原始邮件
> 发件人： ;
> 收件人： ;
> 日 期 ：2018年01月23日 06:36
> 主 题 ：[onap-discuss] Bitergia Data Changes
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss
> 
> 
> As mentioned on the PTL call this morning I had a pull request into Bitergia 
> to update the information to align to specific projects. 
> The config has now been updated. 
> 
> 
> 
> A couple of key changes:
> - Each ONAP project now has its own line item , under which the associated 
> repos are aligned.
> - Previously missing repos have been added
> - Locked repos associated with the original open-o or ecomp seedcode are no 
> longer reported on
> 
> PTLs please take a look at your repos listed using either the git or gerrit 
> views and please open a helpdesk ticket if something is missing.
> 
> https://onap.biterg.io 
> 
>   
> Best Regards, 
> -kenny
> 
> Kenny Paul,  Technical Program Manager
> kp...@linuxfoundation.org
> 510.766.5945
> 
> 
> As mentioned on the PTL call this morning I had a pull request into Bitergia 
> to update the information to align to specific projects. 
> The config has now been updated. 
> 
> 
> 
> A couple of key changes:
> - Each ONAP project now has its own line item , under which the associated 
> repos are aligned.
> - Previously missing repos have been added
> - Locked repos associated with the original open-o or ecomp seedcode are no 
> longer reported on
> 
> PTLs please take a look at your repos listed using either the git or gerrit 
> views and please open a helpdesk ticket if something is missing.
> 
> https://onap.biterg.io 
>   
> Best Regards, 
> -kenny
> 
> Kenny Paul,  Technical Program Manager
> kp...@linuxfoundation.org 
> 510.766.5945
> 
> 
> 

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

Re: [onap-discuss] [OOM] DCAE status in non-openstack clouds ?

[FREEMAN, BRIAN D]

Michael,

WRT ARM. I've looked at it before and its not funcationally equivalent to HEAT. 
There is no ARM stack ID that allows changes or even delete's. Its really just 
a macro for the create/instantiate api calls and not a real resource in Azure. 
I think the plan will be to use a cloudify/Aria pluging to convert a TOSCA 
tempalte into the non-openstack cloud API calls.
I dont know if CloudFoundation is more like HEAT but I think doing 
non-openstack clouds via the cloudify/aria tosca template makes the most sense.

AT&T should be contributing some code we put together for this but there is 
alot of work left to do.

Brina


-Original Message-
From: OBRIEN, FRANK MICHAEL 
Sent: Tuesday, January 23, 2018 9:22 AM
To: Alexis de Talhouët ; FREEMAN, BRIAN D 

Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [OOM] DCAE status in non-openstack clouds ?

Brian,

   Good question.  I have started going to the multivim meetings on Mondays.

   I am interested in work to start bringing in southbound plugins to bring up 
VNFs on Azure and AWS.  I understand the Azure work is in the queue.  The AWS 
work has not started yet.

   In the far future we will also look at containerized VNFs but for now we 
should be able to plugin ARM and CloudFormation templates alongside the current 
HEAT ones - don't know if this work will make it in Beijing.



   Btw, thank you for the Azure push a month ago - we started getting things 
rolling around the 20th of Dec and should receive our Azure subscription within 
the week.  For now I occasionally run some personal account tests on azure to 
prep.

   /michael



-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët

Sent: Monday, January 22, 2018 09:48

To: BRIAN D FREEMAN 

Cc: onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] [OOM] DCAE status in non-openstack clouds ?



Brian,



DCAE deployment in Amsterdam is coupled to OpenStack cloud, and we’re not in 
the process of supporting other cloud for now.

This could be an enhancement for Beijing, if DCAE still runs in VMs. And if we 
do such implementation, we should leverage Multicloud interfaces to do so.



Prior to this, we should flush out the requirement of DCAE deployment on 
different type of cloud, what are the implications and so on.



Alexis



> On Jan 22, 2018, at 9:34 AM, FREEMAN, BRIAN D  wrote:

> 

> Michale, Alexis,

> 

> What is the current status of bring DCAE up on non-openstack clouds via OOM ? 
> I have gotten all components but DCAE to pass healthcheck but not sure 
> dcaegen2 pod is even starting in my Azure test environment.

> 

> Brian

> 

> -Original Message-

> From: onap-discuss-boun...@lists.onap.org 

> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael 

> O'Brien via RT

> Sent: Friday, January 05, 2018 2:46 PM

> Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org

> Subject: Re: [onap-discuss] [ONAP Helpdesk #50702] Unable to create 

> new JIRA on mandatory "Affects Version" introduced today

> 

> Jessica,

>   Fixed - thank you

>   Verified task and bug creation

> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_bro

> wse_INT-2D376&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2F

> zw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=tKrU0djaLFNMunPe64U

> L71aFWuRZOtZNphgsL0_tZww&e= 

> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_bro

> wse_INT-2D377&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2F

> zw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=lmgLUdA1wy4X-hgZh5s

> G7g92G3dUW8ZBiQIzON1dVIg&e=

> 

>   /michael

> 

> -Original Message-

> From: Jessica Wagantall via RT 

> [mailto:onap-helpd...@rt.linuxfoundation.org]

> Sent: Friday, January 5, 2018 13:38

> To: Michael O'Brien 

> Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org

> Subject: [ONAP Helpdesk #50702] Unable to create new JIRA on mandatory 

> "Affects Version" introduced today

> 

> Dear Michael ,

> 

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

> 

> Please try and let me know. 

> 

> Thanks and sorry for the trouble

> Jess

> 

> On Fri Jan 05 13:33:22 2018, jwagantall wrote:

>> Working on this now.. 

>> 

>> thanks!

>> Jess

>> 

>> On Fri Jan 05 08:17:31 2018, frank.obr...@amdocs.com wrote:

>>> Jessica,

>>>   Hi, JIRA currently is broken on the new validation field - we are 

>>> not able to add any new issues - could we get this addressed ASAP, 

>>> either temporarily reverse the change and retest it before 

>>> reintroducing it or temporarily auto-populating it

>>> 

>>> Thank you

>>> /michael

>>> 

>>> -Original Message-

>>> From: ONAP Helpdesk via RT [mailto:onap- 

>>> helpd...@rt.linuxfoundation.org]

>>> Sent: Friday

Re: [onap-discuss] [OOM] DCAE status in non-openstack clouds ?

[Michael O'Brien]

Brian,
   Good question.  I have started going to the multivim meetings on Mondays.
   I am interested in work to start bringing in southbound plugins to bring up 
VNFs on Azure and AWS.  I understand the Azure work is in the queue.  The AWS 
work has not started yet.
   In the far future we will also look at containerized VNFs but for now we 
should be able to plugin ARM and CloudFormation templates alongside the current 
HEAT ones - don't know if this work will make it in Beijing.

   Btw, thank you for the Azure push a month ago - we started getting things 
rolling around the 20th of Dec and should receive our Azure subscription within 
the week.  For now I occasionally run some personal account tests on azure to 
prep.
   /michael

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Monday, January 22, 2018 09:48
To: BRIAN D FREEMAN 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [OOM] DCAE status in non-openstack clouds ?

Brian,

DCAE deployment in Amsterdam is coupled to OpenStack cloud, and we’re not in 
the process of supporting other cloud for now.
This could be an enhancement for Beijing, if DCAE still runs in VMs. And if we 
do such implementation, we should leverage Multicloud interfaces to do so.

Prior to this, we should flush out the requirement of DCAE deployment on 
different type of cloud, what are the implications and so on.

Alexis

> On Jan 22, 2018, at 9:34 AM, FREEMAN, BRIAN D  wrote:
> 
> Michale, Alexis,
> 
> What is the current status of bring DCAE up on non-openstack clouds via OOM ? 
> I have gotten all components but DCAE to pass healthcheck but not sure 
> dcaegen2 pod is even starting in my Azure test environment.
> 
> Brian
> 
> -Original Message-
> From: onap-discuss-boun...@lists.onap.org 
> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Michael 
> O'Brien via RT
> Sent: Friday, January 05, 2018 2:46 PM
> Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org
> Subject: Re: [onap-discuss] [ONAP Helpdesk #50702] Unable to create 
> new JIRA on mandatory "Affects Version" introduced today
> 
> Jessica,
>   Fixed - thank you
>   Verified task and bug creation
> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_bro
> wse_INT-2D376&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2F
> zw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=tKrU0djaLFNMunPe64U
> L71aFWuRZOtZNphgsL0_tZww&e= 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_bro
> wse_INT-2D377&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2F
> zw&m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=lmgLUdA1wy4X-hgZh5s
> G7g92G3dUW8ZBiQIzON1dVIg&e=
> 
>   /michael
> 
> -Original Message-
> From: Jessica Wagantall via RT 
> [mailto:onap-helpd...@rt.linuxfoundation.org]
> Sent: Friday, January 5, 2018 13:38
> To: Michael O'Brien 
> Cc: onap-discuss@lists.onap.org; onap-...@lists.onap.org
> Subject: [ONAP Helpdesk #50702] Unable to create new JIRA on mandatory 
> "Affects Version" introduced today
> 
> Dear Michael ,
> 
> Can you please try again. This mandatory field has now been isolated to only 
> Bug type issues on its own. Epic and Story can now be created without the 
> need of an Affected Version. 
> 
> Please try and let me know. 
> 
> Thanks and sorry for the trouble
> Jess
> 
> On Fri Jan 05 13:33:22 2018, jwagantall wrote:
>> Working on this now.. 
>> 
>> thanks!
>> Jess
>> 
>> On Fri Jan 05 08:17:31 2018, frank.obr...@amdocs.com wrote:
>>> Jessica,
>>>   Hi, JIRA currently is broken on the new validation field - we are 
>>> not able to add any new issues - could we get this addressed ASAP, 
>>> either temporarily reverse the change and retest it before 
>>> reintroducing it or temporarily auto-populating it
>>> 
>>> Thank you
>>> /michael
>>> 
>>> -Original Message-
>>> From: ONAP Helpdesk via RT [mailto:onap- 
>>> helpd...@rt.linuxfoundation.org]
>>> Sent: Friday, January 5, 2018 00:44
>>> To: Michael O'Brien 
>>> Subject: [ONAP Helpdesk #50702] AutoReply: Unable to create new JIRA 
>>> on mandatory "Affects Version" introduced today
>>> 
>>> Greetings,
>>> 
>>> Your support ticket regarding:
>>>"Unable to create new JIRA on mandatory "Affects Version"
>>> introduced today", has been entered in our ticket tracker.  A 
>>> summary of your ticket appears below.
>>> 
>>> If you have any follow-up related to this issue, please reply to 
>>> this email.
>>> 
>>> You may also follow up on your open tickets by visiting 
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__rt.linuxfoundat
>>> ion.org_&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=e3d1ehx3DI5AoMgDmi2Fzw&
>>> m=X0h7lcMZUU83N2cuK_RLHtm5rKHLh_QVh7IVqQwuWl8&s=FXckY0PVLNJI-0IyLaAM6k6lmgsRtC5iXouWEJ8SEcU&e=
>>>   -- if you have not logged into RT before, you will need to follow the 
>>> "Forgot your password" link to set an RT password.
>>> 
>>> --
>>> The Linux 

[onap-discuss] [so] vFW Demo: SO Heat Orchestration Timeout

[Manoj K Nair]

Hi SO Team,

I tried to bring up the vFW demo and while adding the VF module for vFW got an 
error (timeout) in SO and the state changed to "pending delete".  I noticed in  
SO VNFAdapter/auditmso.log following error

"2018-01-23T09:40:04.642Z|2018-01-23T09:48:48.523Z|f0741791-a210-4a51-8f41-9b17900
c8be44|2838a2e5-d665-4f2e-8d97-948a463ef41d|Thread-298||CreateVfModule|BPELClienn
t|ERROR|505|Create VF Module: Query vFW_SINC_Module5 in 
RegionOne/d4cdcb2d594a455
51b6fd1576ce5bc2f6: org.openecomp.mso.openstack.exceptions.MsoIOException: 
Connee
ct to 172.116.0.196:8004 [/172.116.0.196] failed: Connection timed out 
(Connectii
on timed 
out)|356b3660-d381-4a62-954e-efb9be4b8992|INFO|0|172.18.0.3|523881|mso..
mso.testlab.openecomp.org|172.18.0.3"

As per my understanding this is some issue with connecting to the keystone 
service. I verified in my Openstack controller above IP/Port for Orchestration 
API and I am also able to ping controller node from MSO docker container. My 
MSO cloud_region.json is targeting to OpenStack Ocata and I slightly modified 
this to rectify an SSL error .


2018-01-23T07:51:14.109Z|2018-01-23T07:51:29.356Z|9fc35ff3-ff2c-4ac5-bcaa-bb2cdee
3467da|789f273b-1044-4b6b-a9b8-5e5b74f92542|Thread-278||CreateVfModule|BPELClienn
t|ERROR|505|Create VF Module: Query vFW_SINC_Module1 in 
RegionOne/d4cdcb2d594a455
51b6fd1576ce5bc2f6: org.openecomp.mso.openstack.exceptions.MsoIOException: 
Unrecc
ognized SSL message, plaintext 
connection?|356b3660-d381-4a62-954e-efb9be4b8992||
INFO|0|172.18.0.3|15247|mso.mso.testlab.openecomp.org|172.18.0.3

I changed the identity_url from https to http as below .  After this change I 
started getting the heat orchestration timeout error . Appreciate if you can 
clarify


1)  Does MSO support Keystone v3 ?

2)  Can I just add the v3 URL as http://192.168.1.196:5000/v3";  for 
identity_url ?

3)  Do I need to also mention  "identity_api_version"="v3"?

4)  Any other configuration missing in SO which might trigger the timeout ? 
(I have configured cloud region in AAI and also preloaded VNF data in SDNC as 
per wiki page)


MSO cloud_config.json is given below.


{
  "cloud_config":
  {
"identity_services":
{
"DEFAULT_KEYSTONE":
{
  "identity_url": "http://192.168.1.196:5000/v2.0";,
  "mso_id": "onap",
  "mso_pass": "91ceda8da6526c3e71d75b01cf159e61",
  "admin_tenant": "service",
  "member_role": "admin",
  "tenant_metadata": true,
  "identity_server_type": "KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD"
}
},
"cloud_sites":
{
"RegionOne":
{
  "region_id": "RegionOne",
  "clli": "RegionOne",
  "aic_version": "2.5",
  "identity_service_id": "DEFAULT_KEYSTONE"
}
}
  }
}




The information transmitted herein is intended only for the person or entity to 
which it is addressed and may contain confidential, proprietary and/or 
privileged material. Any review, retransmission, dissemination or other use of, 
or taking of any action in reliance upon, this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error, please contact the sender and delete the material from any computer.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Did You Know?

[Tzvika Avni]

[cid:image001.png@01D39052.EEF5F1D0]

Did You Know?
OOM automatically registers all components to MSB

ONAP services need to be registered to MSB to leverage its service 
discovery/routing/LB capabilities.

OOM uses the KUBE2MSB registrator (another ONAP component) to register services 
automatically when deploying the ONAP components.

The registrator gets notified by the POD event, updates the service info and 
registers service endpoint in the MSB.

*MSB uses these service info to route service requests.

MSB portal shows all registered NAP services:

http://${Node_IP}:30082/msb



If you'd like to learn more about MSB, check out the MSB wiki 
page.
If you'd like to learn more about OOM, check out the OOM 
wiki or 
concepts to find out more about 
Kubernetes.


Tzvika Avni
[amdocs-a]
Amdocs a Platinum member of 
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 

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