date:20180131

Re: [onap-discuss] Any consensus on the two IMs proposed

2018-01-31 Thread yangxu (H)

Hi Jason,

As agreed by the group, we'll produce Papyrus files as the final spec.
A meeting has been arranged to discuss about Papyrus and try to reach consensus 
on the models.
If you are interested, please join the call.

Zoom id: 9117271979
Time: 8:00 am us eastern time, 9:00 pm Beijing time, Thursday (Feb 1)

Best regards,
Xu
发件人：domineering skycloud
收件人：onap-discuss@lists.onap.org,
时间：2018-01-30 23:20:21
主 题：[onap-discuss] Any consensus on the two IMs proposed

Hi guys,

Regarding ONAP modeling, I’ve noticed that there are two documents to
propose the IM 
specifications(https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions),
namely, one from Huawei (ONAP VNFD IM - based on IFA011 v231.docx) and another 
(ONAP Class Model 2017-01-02 V3.docx)
from AT So I am wondering which one we should follow to develop and whether 
we reach a consensus in terms of which IM specification we should choose, 
Huawei’s or ATT’s?

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

[onap-discuss] [modeling] Whether How and when we should move to Github for modeling spec update process

2018-01-31 Thread denghui (L)

Hello modeling subcommittee,

Many Thanks to Jessie's kind presentation on GitHub for Papyrus model.
https://wiki.onap.org/display/DW/Modeling+sub-committee+Contributions
https://wiki.onap.org/download/attachments/16003450/GitHub%20for%20Papyrus%20Model.pptx?api=v2

Due to time limitation, we would like to discussion in the list together with 
the communities whether, how and when we should move to Github to manage the 
modeling spec update process.

Thanks a lot for your advice
Best regards,

DENG Hui
___
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

2018-01-31 Thread Ramanarayanan, Karthick

Yes.

I am running in k8s cluster.

I haven't moved to the latest.

I have got the closed loop demo (without dcae of course!) working fine on Dec 
21st setup now.

Regards,

-Karthick


From: Alexis de Talhouët 
Sent: Wednesday, January 31, 2018 5:18:42 AM
To: Ramanarayanan, Karthick
Cc: BRIAN D FREEMAN; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM

Hello Karthick, Brian

I think, thanks to Marco, we have identified one piece of the problem.
I guess you guys are running a K8S cluster. The way UEB is configured in SDC is 
using the K8S hosts IPs, so DCAE service (when deployed), can reach it when 
retrieving the config using the following request (replace 
K8S_HOST with one of your 
host ip):

curl -X GET \
  
http://K8S_HOST:30205/sdc/v1/distributionUebCluster
 \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'X-ECOMP-InstanceID: mso' \
  -H 'authorization: Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=‘

I guess, if you try this request on the setup where it was failing before, 
you’ll get the list where the first elements look ok, but the second one is 
wrong, See https://jira.onap.org/browse/OOM-638 for more details.
This has now been fix.

That said, it seems this is not it, and there is still something breaking SDC 
UEB registration.

Can you confirm you’re running in a K8S cluster?  I’m looking into this.

Alexis

On Jan 26, 2018, at 1:22 PM, Ramanarayanan, Karthick 
> wrote:

The sdc-backend was always a suspect in my setup (56 core) and I invariably 
used to restart the backend pods to get the backend health checks to succeed:
curl http://127.0.0.1:30205/sdc2/rest/healthCheck

This returns "Service unavailable" when backend doesn't come up. If you restart 
the cassandra/es/kibana pods and then restart the backend, it would come up.

In my single node k8s host (k8s directly on the host as in my earlier runs),
I see health check component DE for backend failing. (distribution engine)

Everything else is up.

curl http://127.0.0.1:30205/sdc2/rest/healthCheck


 {
  "healthCheckComponent": "DE",
  "healthCheckStatus": "DOWN",
  "description": "U-EB cluster is not available"
},


This probably implies that in my setup, the UebServers list fetched in the 
backend catalog code before running the DistributionHealthCheck servers fetched 
from the distributionEngine configuration is not proper. (when running without 
dcae vm or dcae disabled)

This is probably the reason why distribution for service fails with policy 
exception.
Its not able to find the ueb server list perhaps when dcae is disabled.
Alexis would know best.

Regards,
-Karthick

From: FREEMAN, BRIAN D >
Sent: Friday, January 26, 2018 9:52:24 AM
To: Alexis de Talhouët; Ramanarayanan, Karthick
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM

Alexi,



I cant get OOM install to work today (it was working yesterday) - seems to fail 
on sdc - doesnt pass healthcheck due to sdc-be as best I can tell .



I use cd.sh should i use the 4 step process below instead ?



Brian





-Original Message-

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

Sent: Friday, January 26, 2018 8:50 AM

To: Ramanarayanan, Karthick >

Cc: onap-discuss@lists.onap.org

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



Karthick,



I’ve just re-tested on latest Amsterdam, and distribute does work fine.



I don’t know if you have redeploy the whole ONAP or not, but understand that 
the issue you had with distribution not working was an issue

impacting so aai and sdc.

The reason is, sdc is configured with the ueb cluster ip address (dmaap, the 
message bus basically), and the way ueb is configured in sdc is using

external access to dmaap, using the k8s node ip instead of the internal 
networking of k8s (e.g. dmaap.onap-message-router).

This change was done recently to accommodate DCAEGEN2 service-change-handler 
micro-service that has to connect to dmaap.

sdc has an api so one can retrieve the ueb cluster ips, 
/sdc/v1/distributionUebCluster, and all the consumer of sdc distribute are 
using the sdc-distribution-client application,

provided by sdc, that retrieves the ueb cluster ips using the api mentioned 
before. Hence when the DCAE micro service was retrieving the ips of the ueb 
cluster, and

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

2018-01-31 Thread Determe, Sebastien

Yes that is the key, for the encryption mecanism check the cryptoutils class 
header. You can encrypt using openssl command.
Seb



Sent from my Samsung Galaxy smartphone.


 Original message 
From: "Elie Dit Cosaque, David (Nokia - US/Irving)" 

Date: 1/31/18 18:50 (GMT+01:00)
To: "Determe, Sebastien" , onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

I have not encrypted the password so this must be the issue. Is there tool that 
I can use to do that? Can I retrieve the SDC password from the Authorization 
header such as:  Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=

Is the CLAMP key aa3871669d893c7fb8abbcda31b88b4f ?
Thanks,
David.
From: Determe, Sebastien [mailto:sd3...@intl.att.com]
Sent: Wednesday, January 31, 2018 11:00 AM
To: Elie Dit Cosaque, David (Nokia - US/Irving) 
; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

OK so it indicates that the password you have set for SDC has not been 
decrypted properly.
Did you encrypt it with AES-CBC-128 ?

Seb

From: Elie Dit Cosaque, David (Nokia - US/Irving) 
[mailto:david.elie_dit_cosa...@nokia.com]
Sent: Wednesday, January 31, 2018 5:57 PM
To: Determe, Sebastien >; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Hi Sebastien,

For the first error, I was able to find a java stack trace but for the second, 
I see only the error below at he following URL:

http://{{CLAMP_IP}}:8080/restservices/clds/v1/clds/sdc/services

[
{
"code": 500,
"message": "Given final block not properly padded"
}
]

Thanks,
David.

These are all the logs captured during the designer page refresh:
==

==> /opt/clamp/log/CLAMP/debug.log <==
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|DEBUG|c.a.a.c.logging.PerformanceTracking|In...:logTracker
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|INFO|c.a.a.c.logging.PerformanceTracking|Performance
 Log:
restservices.clds.v1.clds.properties#AJSC-CSI#ajsc:ajsc6camundademo-1.1.0-TEST-944a55e8bf56-N/A#ajscUser~CNG-CSI~fc4e11f9-b137-4f7a-8810-6ae7247a9c74#2018-01-31T15:42:28.517Z#ajscUser#[e0716f48-3783-410f-bf12-1ae646a8fda3]|Main#I#1517413348517#restservices.clds.v1.clds.properties|Main#C#1517413348556#restservices.clds.v1.clds.properties|RecordSizes#ReqMsgSize=#RespMsgSize=1631#ClientDME2Lookup=#ClientSentTime=null#Cluster=N/A#Vtier=944a55e8bf56#ClientApp=ajsc-csi-restful~ajsc6camundademo#Mode=#InstanceName=ajsc:ajsc6camundademo-1.1.0-TEST-944a55e8bf56-N/A#HostIPAddress=172.18.0.3#HostName=944a55e8bf56#ResponseCode=0#ResponseDescription=Success

==> /opt/clamp/log/CLAMP/error.log <==
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|||Both 
org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|||Both 
org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results

==> /opt/clamp/log/CLAMP/security.log <==
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||User logged into the CLDS 
system=admin
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-cl|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-cl|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-cl|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-cl|dev|update

Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

2018-01-31 Thread bharath thiruveedula

Hi Lusheng,

Sure. Thanks for the confirmation.

>>By the way, there is a deployment of ONAP w DCAE by Heat template in the 
>>Pod25 Integration lab, in the DCAE tenant.  If you have access to the 
>>Integration lab, you can access this instance to see an example of those 
>>values.

I will get more details about Pod25 integration lab and I will check the values.

Best Regards
Bharath T

From: onap-discuss-boun...@lists.onap.org  
on behalf of JI, LUSHENG (LUSHENG) 
Sent: Wednesday, January 31, 2018 11:03 PM
To: Thiruveedula, Bharath; Alexis de Talhouët
Cc: onap-discuss; Talari Nehemiah Vara, Vara (Nokia - US/Irving)
Subject: Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with 
Multicloud Titanium

Bharath,

The dnsaas_* parameters are all related to the proxy-ed Designate.  In the 
current proxy implementation, the “surrogate” tenant needs to have the same 
values for both the region and tenant name as the actual deployment tenant 
(despite that there are separate sets of configuration parameters, which was 
because there was a plan to make things less restrictive to permit different 
names, which was not done in R1).

By the way, there is a deployment of ONAP w DCAE by Heat template in the Pod25 
Integration lab, in the DCAE tenant.  If you have access to the Integration 
lab, you can access this instance to see an example of those values.

Thanks,

Lusheng

From:  on behalf of "Thiruveedula, Bharath 
via onap-discuss" 
Reply-To: "Thiruveedula, Bharath" 
Date: Wednesday, January 31, 2018 at 11:26 AM
To: Alexis de Talhouët 
Cc: onap-discuss , "Talari Nehemiah Vara, Vara 
(Nokia - US/Irving)" 
Subject: Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with 
Multicloud Titanium

Hi Alexis,

That's the document that helped me to start. But the region name issue is not 
mentioned in that document. Anyways I will update the document.

Thanks Alexis

Best Regards

Bharath T

On Wed, Jan 31, 2018 at 9:02 PM, Alexis de Talhouët 
> wrote:

Hi,

Please refer to this page where all the parameters are explained: 
http://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/installation_heat.html

Thanks,

Alexis

On Jan 31, 2018, at 9:46 AM, Kumar Skand Priya, Viswanath V 
>
 wrote:

Probably due to the assumption that, DCAE's openstack happens to be the same as 
Designate's openstack in a typical setup. Since we introduced proxy designate, 
this assumption is now invalidated. Good Catch Bharath!

BR,

Viswa

[mage removed by 
sender.]

Viswanath Kumar Skand Priya

Architect

Verizon India ( VDSI )

On Wed, Jan 31, 2018 at 8:05 PM, Thiruveedula, Bharath 
> 
wrote:

Hi ,

As per the code in "dnsdesig/dns_plugin.py" in  boot container, it expects the 
"dns"  service in endpoints with the same region name as DCAE_REGION. So the 
region name and tenant name of both the openstack should be same. It worked for 
me.

Best Regards

Bharath T

On Wed, Jan 31, 2018 at 5:33 PM, Thiruveedula, Bharath 
> 
wrote:

Hi Alexis,

(Sorry Ramu for hijacking the mail)

I am also facing the same error.

The parameter you are referring "dcae_keystone_url" is the value in 
/opt/config/keystone_url.txt?

First of all, let me clear you that I am trying t install DCAEGEN2 using heat 
way not the OOM approach. Though the

Re: [onap-discuss] [modeling] ONAP IM discussion meeting

2018-01-31 Thread SCAGGS, KEVIN

All,

I will try to join.

I just completed an XMI export of the ONAP model, sending it to Michela for 
another attempt for conversion.   Previously, I only sent one domain (Service).

If this goes well, I would think we will be well positioned to either make a 
move from Sparx to Papyrus or better yet, to move things back and forth between 
the two tools.

Regards,
Kevin

From: MAYER, ANDREW J
Sent: Wednesday, January 31, 2018 10:58 AM
To: yangxu (H) ; SCAGGS, KEVIN ; 
August-Wilhelm Jagau ; Michela Bevilacqua 

Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [modeling] ONAP IM discussion meeting

Xu Yang,

Yes, let’s plan on a call to discuss at 8:00am eastern US on Thursday (1 Feb) 
to discuss Papyrus, using Zoom ID: 9117271979

Best Regards,
Andy

Andy Mayer, Ph.D. | PMTS, D2.0 Integration | AT Labs | Phone: +1 (732) 
420-9945 | am8...@att.com

From: yangxu (H) [mailto:yang...@huawei.com]
Sent: Wednesday, January 31, 2018 7:03 AM
To: SCAGGS, KEVIN >; MAYER, ANDREW J 
>
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [modeling] ONAP IM discussion meeting

Hi Kevin & Andy,

I think it’s time to discuss how to start the Papyrus work and make a concrete 
agreement/specification for R2’s information model.
Are you available at 8:00 a.m. US eastern time (9:00 p.m. Beijing time) on 
Thursday or Friday? Let’s have one hour discussion on this and try to address 
the comments on the current model.

We can use zoom id: 9117271979 for this call. Please tell me your preferred 
time, thanks in advance.
And anyone who is interested in this work is welcomed to join.

Best regards,
Xu Yang

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

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

2018-01-31 Thread Yury Novitsky

The basic authentication header is base64 encoded.
You can use any base64 decoder to get user:password from the string after Basic.

Best regards,
Yury.

-Original Message-
From: Elie Dit Cosaque, David (Nokia - US/Irving) 
[david.elie_dit_cosa...@nokia.com]
Received: Wednesday, 31 Jan 2018, 19:51
To: Determe, Sebastien [sd3...@intl.att.com]; onap-discuss@lists.onap.org 
[onap-discuss@lists.onap.org]
Subject: Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

I have not encrypted the password so this must be the issue. Is there tool that 
I can use to do that? Can I retrieve the SDC password from the Authorization 
header such as:  Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=

Is the CLAMP key aa3871669d893c7fb8abbcda31b88b4f ?
Thanks,
David.
From: Determe, Sebastien [mailto:sd3...@intl.att.com]
Sent: Wednesday, January 31, 2018 11:00 AM
To: Elie Dit Cosaque, David (Nokia - US/Irving) 
; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

OK so it indicates that the password you have set for SDC has not been 
decrypted properly.
Did you encrypt it with AES-CBC-128 ?

Seb

From: Elie Dit Cosaque, David (Nokia - US/Irving) 
[mailto:david.elie_dit_cosa...@nokia.com]
Sent: Wednesday, January 31, 2018 5:57 PM
To: Determe, Sebastien >; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Hi Sebastien,

For the first error, I was able to find a java stack trace but for the second, 
I see only the error below at he following URL:

http://{{CLAMP_IP}}:8080/restservices/clds/v1/clds/sdc/services

[
{
"code": 500,
"message": "Given final block not properly padded"
}
]

Thanks,
David.

These are all the logs captured during the designer page refresh:
==

==> /opt/clamp/log/CLAMP/debug.log <==
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|DEBUG|c.a.a.c.logging.PerformanceTracking|In...:logTracker
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|INFO|c.a.a.c.logging.PerformanceTracking|Performance
 Log:
restservices.clds.v1.clds.properties#AJSC-CSI#ajsc:ajsc6camundademo-1.1.0-TEST-944a55e8bf56-N/A#ajscUser~CNG-CSI~fc4e11f9-b137-4f7a-8810-6ae7247a9c74#2018-01-31T15:42:28.517Z#ajscUser#[e0716f48-3783-410f-bf12-1ae646a8fda3]|Main#I#1517413348517#restservices.clds.v1.clds.properties|Main#C#1517413348556#restservices.clds.v1.clds.properties|RecordSizes#ReqMsgSize=#RespMsgSize=1631#ClientDME2Lookup=#ClientSentTime=null#Cluster=N/A#Vtier=944a55e8bf56#ClientApp=ajsc-csi-restful~ajsc6camundademo#Mode=#InstanceName=ajsc:ajsc6camundademo-1.1.0-TEST-944a55e8bf56-N/A#HostIPAddress=172.18.0.3#HostName=944a55e8bf56#ResponseCode=0#ResponseDescription=Success

==> /opt/clamp/log/CLAMP/error.log <==
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|||Both 
org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|||Both 
org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results

==> /opt/clamp/log/CLAMP/security.log <==
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||User logged into the CLDS 
system=admin
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-cl|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-cl|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-cl|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-cl|dev|update

Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

2018-01-31 Thread JI, LUSHENG (LUSHENG)

Bharath,

The dnsaas_* parameters are all related to the proxy-ed Designate.  In the 
current proxy implementation, the “surrogate” tenant needs to have the same 
values for both the region and tenant name as the actual deployment tenant 
(despite that there are separate sets of configuration parameters, which was 
because there was a plan to make things less restrictive to permit different 
names, which was not done in R1).

By the way, there is a deployment of ONAP w DCAE by Heat template in the Pod25 
Integration lab, in the DCAE tenant.  If you have access to the Integration 
lab, you can access this instance to see an example of those values.

Thanks,
Lusheng

From:  on behalf of "Thiruveedula, Bharath 
via onap-discuss" 
Reply-To: "Thiruveedula, Bharath" 
Date: Wednesday, January 31, 2018 at 11:26 AM
To: Alexis de Talhouët 
Cc: onap-discuss , "Talari Nehemiah Vara, Vara 
(Nokia - US/Irving)" 
Subject: Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with 
Multicloud Titanium

Hi Alexis,

That's the document that helped me to start. But the region name issue is not 
mentioned in that document. Anyways I will update the document.

Thanks Alexis

Best Regards
Bharath T

On Wed, Jan 31, 2018 at 9:02 PM, Alexis de Talhouët 
> wrote:
Hi,

Please refer to this page where all the parameters are explained: 
http://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/installation_heat.html

Thanks,
Alexis

On Jan 31, 2018, at 9:46 AM, Kumar Skand Priya, Viswanath V 
>
 wrote:

Probably due to the assumption that, DCAE's openstack happens to be the same as 
Designate's openstack in a typical setup. Since we introduced proxy designate, 
this assumption is now invalidated. Good Catch Bharath!

BR,
Viswa

[mage removed by 
sender.]

Viswanath Kumar Skand Priya
Architect
Verizon India ( VDSI )

On Wed, Jan 31, 2018 at 8:05 PM, Thiruveedula, Bharath 
> 
wrote:
Hi ,

As per the code in "dnsdesig/dns_plugin.py" in  boot container, it expects the 
"dns"  service in endpoints with the same region name as DCAE_REGION. So the 
region name and tenant name of both the openstack should be same. It worked for 
me.

Best Regards
Bharath T

On Wed, Jan 31, 2018 at 5:33 PM, Thiruveedula, Bharath 
> 
wrote:
Hi Alexis,

(Sorry Ramu for hijacking the mail)

I am also facing the same error.

The parameter you are referring "dcae_keystone_url" is the value in 
/opt/config/keystone_url.txt?

First of all, let me clear you that I am trying t install DCAEGEN2 using heat 
way not the OOM approach. Though the approach for installing DCAE in heat or 
OOM is the same, but the parameter is sligtly different it seems.

In the heat way of installation, we have three files pointing to  keystone:
1) /opt/config/keystone_url.txt -> 
"http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0"
2) /opt/config/openstack_keystone_url.txt -> 
"http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0"
3) /opt/config/dnsaas_keystone_url.txt -> 
"http://10.0.0.8/identity"

And below is

[onap-discuss] [OOM][MSB] Kube2MSB RBAC security issues

2018-01-31 Thread HU, JUN NICOLAS

Hi,

I created https://jira.onap.org/browse/OOM-645.

The Kube2MSB cannot access the apis of pods and services.

Thanks,
Nicolas

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

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

2018-01-31 Thread Determe, Sebastien

OK so it indicates that the password you have set for SDC has not been 
decrypted properly.
Did you encrypt it with AES-CBC-128 ?

Seb

From: Elie Dit Cosaque, David (Nokia - US/Irving) 
[mailto:david.elie_dit_cosa...@nokia.com]
Sent: Wednesday, January 31, 2018 5:57 PM
To: Determe, Sebastien ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Hi Sebastien,

For the first error, I was able to find a java stack trace but for the second, 
I see only the error below at he following URL:

http://{{CLAMP_IP}}:8080/restservices/clds/v1/clds/sdc/services

[
{
"code": 500,
"message": "Given final block not properly padded"
}
]

Thanks,
David.

These are all the logs captured during the designer page refresh:
==

==> /opt/clamp/log/CLAMP/debug.log <==
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|DEBUG|c.a.a.c.logging.PerformanceTracking|In...:logTracker
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|INFO|c.a.a.c.logging.PerformanceTracking|Performance
 Log:
restservices.clds.v1.clds.properties#AJSC-CSI#ajsc:ajsc6camundademo-1.1.0-TEST-944a55e8bf56-N/A#ajscUser~CNG-CSI~fc4e11f9-b137-4f7a-8810-6ae7247a9c74#2018-01-31T15:42:28.517Z#ajscUser#[e0716f48-3783-410f-bf12-1ae646a8fda3]|Main#I#1517413348517#restservices.clds.v1.clds.properties|Main#C#1517413348556#restservices.clds.v1.clds.properties|RecordSizes#ReqMsgSize=#RespMsgSize=1631#ClientDME2Lookup=#ClientSentTime=null#Cluster=N/A#Vtier=944a55e8bf56#ClientApp=ajsc-csi-restful~ajsc6camundademo#Mode=#InstanceName=ajsc:ajsc6camundademo-1.1.0-TEST-944a55e8bf56-N/A#HostIPAddress=172.18.0.3#HostName=944a55e8bf56#ResponseCode=0#ResponseDescription=Success

==> /opt/clamp/log/CLAMP/error.log <==
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|||Both 
org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|||Both 
org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results

==> /opt/clamp/log/CLAMP/security.log <==
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||User logged into the CLDS 
system=admin
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-cl|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-cl|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-cl|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-cl|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-template|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-template|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-template|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-template|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|COMPLETE|0|Get cldsInfo 
success||INFO|||30|||org.onap.clamp.clds.service.CldsService|||GET cldsInfo 
completed

==> /opt/clamp/log/CLAMP/debug.log <==

Re: [onap-discuss] [modeling] ONAP IM discussion meeting

2018-01-31 Thread MAYER, ANDREW J

Xu Yang,

Yes, let’s plan on a call to discuss at 8:00am eastern US on Thursday (1 Feb) 
to discuss Papyrus, using Zoom ID: 9117271979

Best Regards,
Andy

Andy Mayer, Ph.D. | PMTS, D2.0 Integration | AT Labs | Phone: +1 (732) 
420-9945 | am8...@att.com

From: yangxu (H) [mailto:yang...@huawei.com]
Sent: Wednesday, January 31, 2018 7:03 AM
To: SCAGGS, KEVIN ; MAYER, ANDREW J 
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] [modeling] ONAP IM discussion meeting

Hi Kevin & Andy,

I think it’s time to discuss how to start the Papyrus work and make a concrete 
agreement/specification for R2’s information model.
Are you available at 8:00 a.m. US eastern time (9:00 p.m. Beijing time) on 
Thursday or Friday? Let’s have one hour discussion on this and try to address 
the comments on the current model.

We can use zoom id: 9117271979 for this call. Please tell me your preferred 
time, thanks in advance.
And anyone who is interested in this work is welcomed to join.

Best regards,
Xu Yang

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

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

2018-01-31 Thread Elie Dit Cosaque, David (Nokia - US/Irving)

Hi Sebastien,

For the first error, I was able to find a java stack trace but for the second, 
I see only the error below at he following URL:

http://{{CLAMP_IP}}:8080/restservices/clds/v1/clds/sdc/services

[
{
"code": 500,
"message": "Given final block not properly padded"
}
]

Thanks,
David.

These are all the logs captured during the designer page refresh:
==

==> /opt/clamp/log/CLAMP/debug.log <==
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|DEBUG|c.a.a.c.logging.PerformanceTracking|In...:logTracker
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|INFO|c.a.a.c.logging.PerformanceTracking|Performance
 Log:
restservices.clds.v1.clds.properties#AJSC-CSI#ajsc:ajsc6camundademo-1.1.0-TEST-944a55e8bf56-N/A#ajscUser~CNG-CSI~fc4e11f9-b137-4f7a-8810-6ae7247a9c74#2018-01-31T15:42:28.517Z#ajscUser#[e0716f48-3783-410f-bf12-1ae646a8fda3]|Main#I#1517413348517#restservices.clds.v1.clds.properties|Main#C#1517413348556#restservices.clds.v1.clds.properties|RecordSizes#ReqMsgSize=#RespMsgSize=1631#ClientDME2Lookup=#ClientSentTime=null#Cluster=N/A#Vtier=944a55e8bf56#ClientApp=ajsc-csi-restful~ajsc6camundademo#Mode=#InstanceName=ajsc:ajsc6camundademo-1.1.0-TEST-944a55e8bf56-N/A#HostIPAddress=172.18.0.3#HostName=944a55e8bf56#ResponseCode=0#ResponseDescription=Success

==> /opt/clamp/log/CLAMP/error.log <==
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|||Both 
org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|||Both 
org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results

==> /opt/clamp/log/CLAMP/security.log <==
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||User logged into the CLDS 
system=admin
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-cl|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-cl|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-cl|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-cl|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-template|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-template|dev|read
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|DEBUG|||0||checking if admin has permission: 
permission-type-template|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|INFO|||0||admin authorized for permission: 
permission-type-template|dev|update
2018-01-31T15:42:29Z|2018-01-31T15:42:29Z|e4e75980-b2f2-4137-88b8-862687863722||22-bf5e-8dc96a3cba6c||CldsService:
 GET cldsInfo|admin|COMPLETE|0|Get cldsInfo 
success||INFO|||30|||org.onap.clamp.clds.service.CldsService|||GET cldsInfo 
completed

==> /opt/clamp/log/CLAMP/debug.log <==
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|o.apache.cxf.jaxrs.utils.JAXRSUtils|Both
 org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results
2018-01-31T15:42:29,721Z||68-ba78-7b0b5f274192|WARN|o.apache.cxf.jaxrs.utils.JAXRSUtils|Both
 org.onap.clamp.clds.service.UserServiceImpl#getUser and 
org.onap.clamp.clds.service.UserServiceImpl#getUser are equal candidates for 
handling the current request which can lead to unpredictable results

[onap-discuss] [dcaegen2] DCAE weekly meeting tomorrow to be extended by 30 minutes

2018-01-31 Thread JI, LUSHENG (LUSHENG)

Greetings.

Please note that to accommodate the planned agenda items, the DCAE weekly 
meeting tomorrow (Thursday) will be extended by 30 additional minutes from its 
normal duration.  This meeting will run from 10:30-12:00AM Eastern time (or 
7:30 -9:00 AM Pacific time; 11:30-1AM Beijing time, etc).

We will cover MSB demo and integration (Huabing from the MSB team) and S3P KPI 
testing (Helen from the Integration team).

Thanks,
Lusheng Ji
DCAE PTL
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Canceled event: [vvp] Weekly Meeting (starting Dec. 5, /2017) @ Weekly from 6am to 7am on Tuesday (PST) (onap-discuss@lists.onap.org)

2018-01-31 Thread kpaul

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:CANCEL
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20171205T06
DTEND;TZID=America/Los_Angeles:20171205T07
RRULE:FREQ=WEEKLY;BYDAY=TU
DTSTAMP:20180131T160823Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:75m4t11cb4fq5bq69pocfph...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=eb
 5...@intl.att.com;X-NUM-GUESTS=0:mailto:eb5...@intl.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;CN=on
 ap-disc...@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@lists.onap.org
CREATED:20171128T181057Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 4 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/242271647\n\nOr iPhone one-tap :\nUS: +16699006833\,\,242271647#  o
 r +16465588656\,\,242271647# \nOr Telephone:\nDial(for higher quality\,
  dial a number based on your current location)：\nUS: +1 669 900 683
 3  or +1 646 558 8656  or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (T
 oll Free)\nMeeting ID: 242 271 647\nInternational numbers available
 : https://zoom.us/zoomconference?m=SKT0njBqw_2Xfg9vmabn5Kt13V5cLneM\n\n
LAST-MODIFIED:20180131T160823Z
LOCATION:https://zoom.us/j/242271647
SEQUENCE:1
STATUS:CANCELLED
SUMMARY:[vvp] Weekly Meeting (starting Dec. 5\, /2017)
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [E] Re: [oom] ONAP R1 | Unable to distribute models to AAI in OOM deployment

2018-01-31 Thread Alexis de Talhouët

Bharath,
Thanks, I think this is good for expert to help you, unfortunately, this is not 
something I can help with.
Seems to be something off with the files being ingested by SDC that AAI tries 
to import.
Alexis


> On Jan 31, 2018, at 9:56 AM, Thiruveedula, Bharath 
>  wrote:
> 
> Hi Alexis,
> 
> I have attached the logs of AAI-ML. while distributing I can see one error 
> highlighted below:
> "
> ERROR   org.onap.aai.modelloader.entity.model.ModelArtifact
> RequestId=c8e05f3d-f43f-4c75-920a-d24ccaefa191 ServiceName=ModelLoader
> ServiceInstanceId= StartTime=2018-01-31T14:43:12.710Z ClientAddress= 
> PartnerName=Event-Bus  ServerFQDN=model-loader-service-1965047489-7dkw0   
> MDLSVC2002E|MDLSVC2002E Distribution event error: Ingestion failed for MODEL 
> 1c8299f2-de1b-4217-a77c-0be9522acc0d|4d199989-3de7-430c-9e07-16da50935ab7. 
> Rolling back distribution.|
> 
> Best Regards
> Bharath T
> 
> On Wed, Jan 31, 2018 at 6:40 PM, Alexis de Talhouët  > wrote:
> Hi,
> 
> Can you look at the logs of the model-loader component of AAI?
> 
> Thanks,
> Alexis
> 
>> On Jan 31, 2018, at 3:03 AM, Kumar Skand Priya, Viswanath V via onap-discuss 
>> > wrote:
>> 
>> Dear OOM Team,
>> 
>> We are powering ONAP R1 using OOM. While the installation is successful, we 
>> are facing issues while distributing a network service from SDC to AAI. 
>> 
>> PS : 
>> There are no issues with R1 standalone ONAP deployment ( via HOT files ).
>> Restarting AAI and/or redeploying PODs doesn't help.
>> 
>> Details about Error :
>> 
>> In OOM setup, after distributing the SDC model, we are getting  "deploy 
>> error" in AAI, which blocks the deployment of network service. Below are the 
>> screenshots:
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Log from AAI-datarouter
>> 
>> 2018-01-30T07:44:53.722Z||main|DataRouter||org.onap.aai.datarouter.policy.EntityEventPolicy||ERROR|EEP012E|EEP012E
>>  Failed to create Search index topography-search-index due to: Error during 
>> GET operation to AAI with message = java.net.UnknownHostException: 
>> aai.searchservice.simpledemo.openecomp.org 
>> 
>>|
>> 2018-01-30T07:44:53.722Z||main|DataRouter||org.onap.aai.datarouter.policy.EntityEventPolicy||INFO|EEP0007I|EEP0007I
>>  Entity Event Policy component started.|
>> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.impl.converter.DefaultTypeConverter||WARN|Overriding
>>  type converter from: StaticMethodTypeConverter: public static 
>> java.io.InputStream 
>> org.apache.camel.component.http.HttpConverter.toInputStream(javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange)
>>  throws java.io.IOException to: StaticMethodTypeConverter: public static 
>> java.io.InputStream 
>> org.apache.camel.component.http4.HttpConverter.toInputStream(javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange)
>>  throws java.io.IOException
>> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.impl.converter.DefaultTypeConverter||WARN|Overriding
>>  type converter from: StaticMethodTypeConverter: public static 
>> javax.servlet.http.HttpServletResponse 
>> org.apache.camel.component.http.HttpConverter.toServletResponse(org.apache.camel.Message)
>>  to: StaticMethodTypeConverter: public static 
>> javax.servlet.http.HttpServletResponse 
>> org.apache.camel.component.http4.HttpConverter.toServletResponse(org.apache.camel.Message)
>> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.impl.converter.DefaultTypeConverter||WARN|Overriding
>>  type converter from: StaticMethodTypeConverter: public static 
>> javax.servlet.http.HttpServletRequest 
>> org.apache.camel.component.http.HttpConverter.toServletRequest(org.apache.camel.Message)
>>  to: StaticMethodTypeConverter: public static 
>> javax.servlet.http.HttpServletRequest 
>> org.apache.camel.component.http4.HttpConverter.toServletRequest(org.apache.camel.Message)
>> 2018-01-30T07:44:55.047Z||main|DataRouter||ajsc.ComputeService||ERROR|NMBS-COMPUTESVC-0042:
>>  addRoute for data-router:entity-event:v1 failed  - EXCEPTION: null
>> CAUSED BY: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 109; 
>> Element type "from" must be followed by either attribute specifications, ">" 
>> or "/>".
>> STACKTRACE: at 
>> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl(createUnmarshalException:578)
>> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl(unmarshal0:264)
>> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl(unmarshal:229)
>> at ajsc.ComputeService(getRouteDefinition:793)
>> at

Re: [onap-discuss] [integration][OpenLab] Orange Open labs +integration repos

2018-01-31 Thread Chengli Wang

Hi All,

We will have a special LAB topic during next week virtual F2F meeting, would 
you mind use this session to kick off the related discussion?
The event topic linked here, 
https://wiki.onap.org/display/DW/VF2F+Feb.+5-8%2C+2017 
  we can reserve 60 
minutes if needed.

Chengli 


> 在 2018年1月31日，上午2:13，Yunxia Chen  写道：
> 
> Hi, Morgan,
> That’s the great news. What does Orange lab plan to offer to the community?  
> Could you please call a 30 minutes working session to sort this out with the 
> following people?
> · Chengli Wang
> · Rich Bennett
> · Gary Wu
> · Gildas Lanilis 
> · Stephen Gooch
>  
> They all on the “To” list as well. Let’s not duplicate the content. I am fine 
> with either way you guys come out.
>  
> Regards,
>  
> Helen Chen
>  
> From: "morgan.richo...@orange.com" 
> Date: Tuesday, January 30, 2018 at 8:34 AM
> To: "bin.y...@windriver.com" , Kang Xi 
> , Helen Chen 00725961 , 
> "wangchen...@chinamobile.com" , 
> "ran.pol...@amdocs.com" , "lxin...@vmware.com" 
> , "ROSE, DANIEL V" , Gary Wu 
> , "Yang Xu (Yang, Fixed Network)" 
> , "PLATANIA, MARCO (MARCO)" , 
> yangyi , "spondon...@att.com" 
> Cc: Eric Debeau , BLAISONNEAU David IMT/OLN 
> , onap-discuss 
> Subject: [onap-discuss] [integration][OpenLab] Orange Open labs + integration 
> repos
>  
> Hi Helen
>  
> regarding my action point 
> #AP 4: morgan_orange check with Eric on the Orange Open Lab schedule (when 
> could we communicate at teh community level)
>  
> I am pleased to announce that the Orange Open Lab will be open on the 14th of 
> February after some internal tests currently in progress.
>  
> I was wondering if if would make sense to create new repos to manage that
> - integration/installation to host heat related activities
> - integration/tests to host testing
> - integration/infrastructure to manage the different labs
> - integration/tooling
>  
> Note for the testing part I would even suggest to split it into
> integration/functestional_tests (or functest :))
> integration/benchmark 
>  
> having only 1 repo will be misleading
> If so my colleague David could push the code we are currently using to 
> automate the creation of accounts for remote access (ansible roles) to an 
> ONAP rebound.
> And I assume it will be also the right place for Tlab owner to share stuff.
>  
> is it also up to the integration project to manage the federation of labs, as 
> far as I understand there is also a comittee dealing with that?
> if so I would suggest to reference somewhere (in integration/infrastructure 
> for example) the IPs of the different labs 
> in order to easily tune the FW rules and let ONAP open lab discuss one with 
> the others.
> May I add a topic on this for next week?
>  
> /Morgan
> _
>  
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>  
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.

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

Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

2018-01-31 Thread Alexis de Talhouët

Hi,

Please refer to this page where all the parameters are explained: 
http://onap.readthedocs.io/en/latest/submodules/dcaegen2.git/docs/sections/installation_heat.html
 


Thanks,
Alexis

> On Jan 31, 2018, at 9:46 AM, Kumar Skand Priya, Viswanath V 
>  wrote:
> 
> Probably due to the assumption that, DCAE's openstack happens to be the same 
> as Designate's openstack in a typical setup. Since we introduced proxy 
> designate, this assumption is now invalidated. Good Catch Bharath!
> 
> BR,
> Viswa
> 
> 
>  
> 
> Viswanath Kumar Skand Priya
> Architect
> Verizon India ( VDSI )
> 
>  <>
> On Wed, Jan 31, 2018 at 8:05 PM, Thiruveedula, Bharath 
> > 
> wrote:
> Hi ,
> 
> As per the code in "dnsdesig/dns_plugin.py" in  boot container, it expects 
> the "dns"  service in endpoints with the same region name as DCAE_REGION. So 
> the region name and tenant name of both the openstack should be same. It 
> worked for me.
> 
> Best Regards
> Bharath T
> 
> On Wed, Jan 31, 2018 at 5:33 PM, Thiruveedula, Bharath 
> > 
> wrote:
> Hi Alexis,
> 
> (Sorry Ramu for hijacking the mail)
> 
> I am also facing the same error. 
> 
> The parameter you are referring "dcae_keystone_url" is the value in 
> /opt/config/keystone_url.txt?
> 
> First of all, let me clear you that I am trying t install DCAEGEN2 using heat 
> way not the OOM approach. Though the approach for installing DCAE in heat or 
> OOM is the same, but the parameter is sligtly different it seems.
> 
> In the heat way of installation, we have three files pointing to  keystone:
> 1) /opt/config/keystone_url.txt -> 
> "http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
>  
> "
> 2) /opt/config/openstack_keystone_url.txt   -> 
> "http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
>  
> "
> 3) /opt/config/dnsaas_keystone_url.txt -> "http://10.0.0.8/identity 
> "
> 
> And below is the contents of /tmp/local_inputs.yaml
> 
> ubuntu1604image_id: 'ubuntu-16.04-x86_64-v1-core'
> centos7image_id: 'centos-7-x86_64-v4-core'
> flavor_id: 'm1.xlarge'
> security_group: 'onap_sg_MYGL'
> public_net: 'provider-core-cmn-v4'
> private_net: 'oam_onap_MYGL'
> openstack:
>   username: 'admin'
>   password: 'admin_pw'
>   tenant_name: 'ONAP_Manual_Installation'
>   auth_url: 
> 'http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
>  
> '
>   region: 'regionOne'
> keypair: 'onap_key_MYGL'
> key_filename: ./key600
> location_prefix: 'dcae'
> location_domain: 'MYGL.USWIN'
> codesource_url: 
> 'https://nexus.onap.org/service/local/repositories/raw/content 
> '
> codesource_version: 'org.onap.dcaegen2.deployments/releases'
> 
> I tried to see the request logs  from multicloud
> 
> [31/Jan/2018 11:31:22] "POST 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v3/auth/tokens 
> HTTP/1.1" 201 5135
> [31/Jan/2018 11:31:24] "GET 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN.
>  HTTP/1.1" 200 635
> [31/Jan/2018 11:31:24] "GET 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones 
> HTTP/1.1" 200 618
> [31/Jan/2018 11:31:35] "GET 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN.
>  HTTP/1.1" 200 635
> [31/Jan/2018 11:32:30] "POST 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens 
> HTTP/1.1" 200 4481
> [31/Jan/2018 11:32:31] "GET 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=oam_onap_MYGL
>  HTTP/1.1" 200 631
> [31/Jan/2018 11:32:31] "GET 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0 HTTP/1.1" 200 
> 185
> [31/Jan/2018 11:32:31] "POST 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens 
> HTTP/1.1" 200 4481
> [31/Jan/2018 11:32:32] "GET 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/compute/v2.1/os-keypairs 
> HTTP/1.1" 200 5152
> [31/Jan/2018 11:32:32] "POST 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens 
> HTTP/1.1" 200 4481
> [31/Jan/2018 11:32:33] "GET 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=provider-core-cmn-v4
>  HTTP/1.1" 200 654
> [31/Jan/2018 11:32:33] "POST 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/floatingips.json
>  HTTP/1.1" 201 434
> [31/Jan/2018

Re: [onap-discuss] [E] Re: [oom] ONAP R1 | Unable to distribute models to AAI in OOM deployment

2018-01-31 Thread Thiruveedula, Bharath via onap-discuss

Hi Alexis,

I have attached the logs of AAI-ML. while distributing I can see one error
highlighted below:
"

*ERROR   org.onap.aai.modelloader.entity.model.ModelArtifact
RequestId=c8e05f3d-f43f-4c75-920a-d24ccaefa191 ServiceName=ModelLoader
   ServiceInstanceId= StartTime=2018-01-31T14:43:12.710Z
ClientAddress= PartnerName=Event-Bus
ServerFQDN=model-loader-service-1965047489-7dkw0
MDLSVC2002E|MDLSVC2002E Distribution event error: Ingestion failed for
MODEL 1c8299f2-de1b-4217-a77c-0be9522acc0d|4d199989-3de7-430c-9e07-16da50935ab7.
Rolling back distribution.|*


Best Regards

Bharath T


On Wed, Jan 31, 2018 at 6:40 PM, Alexis de Talhouët  wrote:

> Hi,
>
> Can you look at the logs of the model-loader component of AAI?
>
> Thanks,
> Alexis
>
> On Jan 31, 2018, at 3:03 AM, Kumar Skand Priya, Viswanath V via
> onap-discuss  wrote:
>
> Dear OOM Team,
>
> We are powering ONAP R1 using OOM. While the installation is successful,
> we are facing issues while distributing a network service from SDC to AAI.
>
> PS :
>
>- There are no issues with R1 standalone ONAP deployment ( via HOT
>files ).
>- Restarting AAI and/or redeploying PODs doesn't help.
>
>
> *Details about Error :*
>
> In OOM setup, after distributing the SDC model, we are getting  *"deploy
> error" *in AAI, which blocks the deployment of network service. Below are
> the screenshots:
>
> 
>
>
> 
>
>
> *Log from AAI-datarouter*
>
> 2018-01-30T07:44:53.722Z||main|DataRouter||org.onap.aai.data
> router.policy.EntityEventPolicy||ERROR|EEP012E|EEP012E Failed to create
> Search index topography-search-index due to: Error during GET operation to
> AAI with message = java.net.UnknownHostException:
> aai.searchservice.simpledemo.openecomp.org
> 
>  |
> 2018-01-30T07:44:53.722Z||main|DataRouter||org.onap.aai.data
> router.policy.EntityEventPolicy||INFO|EEP0007I|EEP0007I Entity Event
> Policy component started.|
> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.
> impl.converter.DefaultTypeConverter||WARN|Overriding type converter from:
> StaticMethodTypeConverter: public static java.io.InputStream
> org.apache.camel.component.http.HttpConverter.toInputStream(
> javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange) throws
> java.io.IOException to: StaticMethodTypeConverter: public static
> java.io.InputStream org.apache.camel.component.htt
> p4.HttpConverter.toInputStream(javax.servlet.http.
> HttpServletRequest,org.apache.camel.Exchange) throws java.io.IOException
> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.
> impl.converter.DefaultTypeConverter||WARN|Overriding type converter from:
> StaticMethodTypeConverter: public static 
> javax.servlet.http.HttpServletResponse
> org.apache.camel.component.http.HttpConverter.toServletResponse(org.apache.camel.Message)
> to: StaticMethodTypeConverter: public static 
> javax.servlet.http.HttpServletResponse
> org.apache.camel.component.http4.HttpConverter.toServletResp
> onse(org.apache.camel.Message)
> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.
> impl.converter.DefaultTypeConverter||WARN|Overriding type converter from:
> StaticMethodTypeConverter: public static javax.servlet.http.HttpServletRequest
> org.apache.camel.component.http.HttpConverter.toServletRequest(org.apache.camel.Message)
> to: StaticMethodTypeConverter: public static 
> javax.servlet.http.HttpServletRequest
> org.apache.camel.component.http4.HttpConverter.toServletRequ
> est(org.apache.camel.Message)
> 2018-01-30T07:44:55.047Z||main|DataRouter||ajsc.ComputeServi
> ce||ERROR|NMBS-COMPUTESVC-0042: addRoute for data-router:entity-event:v1
> failed  - EXCEPTION: null
> CAUSED BY: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber:
> 109; Element type "from" must be followed by either attribute
> specifications, ">" or "/>".
> STACKTRACE: at com.sun.xml.bind.v2.runtime.un
> marshaller.UnmarshallerImpl(createUnmarshalException:578)
> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl(un
> marshal0:264)
> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl(un
> marshal:229)
> at ajsc.ComputeService(getRouteDefinition:793)
> at ajsc.ComputeService$getRouteDefinition$3(callCurrent:-1)
> at ajsc.ComputeService(addRoute:820)
> at ajsc.ComputeService$_init_closure15(doCall:970)
> at ajsc.ComputeService(init:970)
> at ajsc.ComputeService$init(call:-1)
> at ajsc.RouteMgmtService(init:148)
> at ajsc.RouteMgmtService$init$0(call:-1)
> at ajsc.ContextMgr(onApplicationEvent:19)
> at org.springframework.context.event.SimpleApplicationEventMult
> icaster(invokeListener:163)
> at org.springframework.context.event.SimpleApplicationEventMult
>

Re: [onap-discuss] [E] Re: [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

2018-01-31 Thread Kumar Skand Priya, Viswanath V via onap-discuss

Probably due to the assumption that, DCAE's openstack happens to be the
same as Designate's openstack in a typical setup. Since we introduced proxy
designate, this assumption is now invalidated. Good Catch Bharath!

BR,
Viswa




Viswanath Kumar Skand Priya
Architect
Verizon India ( VDSI )


On Wed, Jan 31, 2018 at 8:05 PM, Thiruveedula, Bharath <
bharath.thiruveed...@verizon.com> wrote:

> Hi ,
>
> As per the code in "dnsdesig/dns_plugin.py" in  boot container, it expects
> the "dns"  service in endpoints with the same region name as DCAE_REGION.
> So the region name and tenant name of both the openstack should be same. It
> worked for me.
>
> Best Regards
> Bharath T
>
> On Wed, Jan 31, 2018 at 5:33 PM, Thiruveedula, Bharath <
> bharath.thiruveed...@verizon.com> wrote:
>
>> Hi Alexis,
>>
>> (Sorry Ramu for hijacking the mail)
>>
>> I am also facing the same error.
>>
>> The parameter you are referring "dcae_keystone_url" is the value in*
>> /opt/config/keystone_url.txt*?
>>
>> First of all, let me clear you that I am trying t install DCAEGEN2 using
>> heat way not the OOM approach. Though the approach for installing DCAE in
>> heat or OOM is the same, but the parameter is sligtly different it seems.
>>
>> In the heat way of installation, we have three files pointing to
>> keystone:
>> 1) */opt/config/keystone_url.txt* -> 
>> "*http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
>> *
>> "
>> 2) */opt/config/**openstack_keystone_url.txt* -> 
>> "*http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
>> *
>> "
>> 3) */opt/config/dnsaas_keystone_url.txt* -> "*http://10.0.0.8/identity
>> *"
>>
>> And below is the contents of /tmp/local_inputs.yaml
>>
>> ubuntu1604image_id: 'ubuntu-16.04-x86_64-v1-core'
>> centos7image_id: 'centos-7-x86_64-v4-core'
>> flavor_id: 'm1.xlarge'
>> security_group: 'onap_sg_MYGL'
>> public_net: 'provider-core-cmn-v4'
>> private_net: 'oam_onap_MYGL'
>> openstack:
>>   username: 'admin'
>>   password: 'admin_pw'
>>   tenant_name: 'ONAP_Manual_Installation'
>>   auth_url: 'http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_reg
>> ionOne/identity/v2.0'
>>   region: 'regionOne'
>> keypair: 'onap_key_MYGL'
>> key_filename: ./key600
>> location_prefix: 'dcae'
>> location_domain: 'MYGL.USWIN'
>> codesource_url: 'https://nexus.onap.org/servic
>> e/local/repositories/raw/content'
>> codesource_version: 'org.onap.dcaegen2.deployments/releases'
>>
>> I tried to see the request logs from multicloud
>>
>> [31/Jan/2018 11:31:22] "POST /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/identity/v3/auth/tokens HTTP/1.1" 201 5135
>> [31/Jan/2018 11:31:24] "GET /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN. HTTP/1.1" 200
>> 635 [31/Jan/2018 11:31:24] "GET /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/dns-delegate/v2/zones HTTP/1.1" 200 618 [31/Jan/2018
>> 11:31:35] "GET /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN. HTTP/1.1" 200
>> 635 [31/Jan/2018 11:32:30] "POST /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 [31/Jan/2018
>> 11:32:31] "GET /api/multicloud-titanium_cloud/v0/pod25_regionOne/network/
>> v2.0/networks.json?name=oam_onap_MYGL HTTP/1.1" 200 631 [31/Jan/2018
>> 11:32:31] "GET /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/identity/v2.0 HTTP/1.1" 200 185 [31/Jan/2018
>> 11:32:31] "POST /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 [31/Jan/2018
>> 11:32:32] "GET 
>> /api/multicloud-titanium_cloud/v0/pod25_regionOne/compute/v2.1/os-keypairs
>> HTTP/1.1" 200 5152 [31/Jan/2018 11:32:32] "POST
>> /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
>> HTTP/1.1" 200 4481 [31/Jan/2018 11:32:33] "GET
>> /api/multicloud-titanium_cloud/v0/pod25_regionOne/network/
>> v2.0/networks.json?name=provider-core-cmn-v4 HTTP/1.1" 200 654
>> [31/Jan/2018 11:32:33] "POST /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/network/v2.0/floatingips.json HTTP/1.1" 201 434
>> [31/Jan/2018 11:32:34] "POST /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 [31/Jan/2018
>> 11:32:34] "GET /api/multicloud-titanium_cloud/v0/pod25_regionOne/network/
>> v2.0/security-groups.json?name=onap_sg_MYGL HTTP/1.1" 200 2628
>> [31/Jan/2018 11:32:36] "POST /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481 [31/Jan/2018
>> 11:32:37] "POST /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/network/v2.0/ports.json HTTP/1.1" 201 760
>> [31/Jan/2018 11:32:38] "POST /api/multicloud-titanium_cloud
>> /v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481

Re: [onap-discuss] [E] Re: [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

2018-01-31 Thread Akula, Ramanjaneyul Reddy (Nokia - US/Irving)

Bharath,
Good point. I have noticed the issue with the tenant name and changed my 
deployment to use admin tenant. But region looks new to me.
I have different region names between designate and the native cloud.
I’ll change my designate to use the samename.
By the way in your env file what is the keystone url you have used for the 
param “dcae_keystone_url”?

Thanks in advance

best regards,
Ramu


From: Thiruveedula, Bharath [mailto:bharath.thiruveed...@verizon.com]
Sent: Wednesday, January 31, 2018 8:35 AM
To: Alexis de Talhouët 
Cc: Akula, Ramanjaneyul Reddy (Nokia - US/Irving) 
; onap-discuss 
; Talari Nehemiah Vara, Vara (Nokia - US/Irving) 
; Kumar Skand Priya, Viswanath V 
; VENKATESH KUMAR, VIJAY 
Subject: Re: [E] Re: [onap-discuss] [DCAGEN2] Proxied DNS Designate only with 
Multicloud Titanium

Hi ,

As per the code in "dnsdesig/dns_plugin.py" in  boot container, it expects the 
"dns"  service in endpoints with the same region name as DCAE_REGION. So the 
region name and tenant name of both the openstack should be same. It worked for 
me.

Best Regards
Bharath T

On Wed, Jan 31, 2018 at 5:33 PM, Thiruveedula, Bharath 
> 
wrote:
Hi Alexis,

(Sorry Ramu for hijacking the mail)

I am also facing the same error.

The parameter you are referring "dcae_keystone_url" is the value in 
/opt/config/keystone_url.txt?

First of all, let me clear you that I am trying t install DCAEGEN2 using heat 
way not the OOM approach. Though the approach for installing DCAE in heat or 
OOM is the same, but the parameter is sligtly different it seems.

In the heat way of installation, we have three files pointing to  keystone:
1) /opt/config/keystone_url.txt -> 
"http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0;
2) /opt/config/openstack_keystone_url.txt -> 
"http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0;
3) /opt/config/dnsaas_keystone_url.txt -> "http://10.0.0.8/identity;

And below is the contents of /tmp/local_inputs.yaml

ubuntu1604image_id: 'ubuntu-16.04-x86_64-v1-core'
centos7image_id: 'centos-7-x86_64-v4-core'
flavor_id: 'm1.xlarge'
security_group: 'onap_sg_MYGL'
public_net: 'provider-core-cmn-v4'
private_net: 'oam_onap_MYGL'
openstack:
  username: 'admin'
  password: 'admin_pw'
  tenant_name: 'ONAP_Manual_Installation'
  auth_url: 
'http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0'
  region: 'regionOne'
keypair: 'onap_key_MYGL'
key_filename: ./key600
location_prefix: 'dcae'
location_domain: 'MYGL.USWIN'
codesource_url: 'https://nexus.onap.org/service/local/repositories/raw/content'
codesource_version: 'org.onap.dcaegen2.deployments/releases'

I tried to see the request logs from multicloud

[31/Jan/2018 11:31:22] "POST 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v3/auth/tokens 
HTTP/1.1" 201 5135 [31/Jan/2018 11:31:24] "GET 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN.
 HTTP/1.1" 200 635 [31/Jan/2018 11:31:24] "GET 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones 
HTTP/1.1" 200 618 [31/Jan/2018 11:31:35] "GET 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN.
 HTTP/1.1" 200 635 [31/Jan/2018 11:32:30] "POST 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens 
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:31] "GET 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=oam_onap_MYGL
 HTTP/1.1" 200 631 [31/Jan/2018 11:32:31] "GET 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0 HTTP/1.1" 200 
185 [31/Jan/2018 11:32:31] "POST 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens 
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:32] "GET 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/compute/v2.1/os-keypairs 
HTTP/1.1" 200 5152 [31/Jan/2018 11:32:32] "POST 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens 
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:33] "GET 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=provider-core-cmn-v4
 HTTP/1.1" 200 654 [31/Jan/2018 11:32:33] "POST 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/floatingips.json 
HTTP/1.1" 201 434 [31/Jan/2018 11:32:34] "POST 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens 
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:34] "GET 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/security-groups.json?name=onap_sg_MYGL
 HTTP/1.1" 200 2628 [31/Jan/2018 11:32:36] "POST 
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens 
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:37] "POST

Re: [onap-discuss] [E] Re: [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

2018-01-31 Thread Thiruveedula, Bharath via onap-discuss

Hi ,

As per the code in "dnsdesig/dns_plugin.py" in  boot container, it expects
the "dns"  service in endpoints with the same region name as DCAE_REGION.
So the region name and tenant name of both the openstack should be same. It
worked for me.

Best Regards
Bharath T

On Wed, Jan 31, 2018 at 5:33 PM, Thiruveedula, Bharath <
bharath.thiruveed...@verizon.com> wrote:

> Hi Alexis,
>
> (Sorry Ramu for hijacking the mail)
>
> I am also facing the same error.
>
> The parameter you are referring "dcae_keystone_url" is the value in*
> /opt/config/keystone_url.txt*?
>
> First of all, let me clear you that I am trying t install DCAEGEN2 using
> heat way not the OOM approach. Though the approach for installing DCAE in
> heat or OOM is the same, but the parameter is sligtly different it seems.
>
> In the heat way of installation, we have three files pointing to  keystone:
> 1) */opt/config/keystone_url.txt* -> 
> "*http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
> *
> "
> 2) */opt/config/**openstack_keystone_url.txt* -> 
> "*http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
> *
> "
> 3) */opt/config/dnsaas_keystone_url.txt* -> "*http://10.0.0.8/identity
> *"
>
> And below is the contents of /tmp/local_inputs.yaml
>
> ubuntu1604image_id: 'ubuntu-16.04-x86_64-v1-core'
> centos7image_id: 'centos-7-x86_64-v4-core'
> flavor_id: 'm1.xlarge'
> security_group: 'onap_sg_MYGL'
> public_net: 'provider-core-cmn-v4'
> private_net: 'oam_onap_MYGL'
> openstack:
>   username: 'admin'
>   password: 'admin_pw'
>   tenant_name: 'ONAP_Manual_Installation'
>   auth_url: 'http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_
> regionOne/identity/v2.0'
>   region: 'regionOne'
> keypair: 'onap_key_MYGL'
> key_filename: ./key600
> location_prefix: 'dcae'
> location_domain: 'MYGL.USWIN'
> codesource_url: 'https://nexus.onap.org/service/local/repositories/raw/
> content'
> codesource_version: 'org.onap.dcaegen2.deployments/releases'
>
> I tried to see the request logs from multicloud
>
> [31/Jan/2018 11:31:22] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v3/auth/tokens HTTP/1.1" 201 5135
> [31/Jan/2018 11:31:24] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN. HTTP/1.1"
> 200 635 [31/Jan/2018 11:31:24] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/dns-delegate/v2/zones HTTP/1.1" 200 618
> [31/Jan/2018 11:31:35] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN. HTTP/1.1"
> 200 635 [31/Jan/2018 11:32:30] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481
> [31/Jan/2018 11:32:31] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=oam_onap_MYGL
> HTTP/1.1" 200 631 [31/Jan/2018 11:32:31] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0 HTTP/1.1" 200 185 [31/Jan/2018
> 11:32:31] "POST 
> /api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
> HTTP/1.1" 200 4481 [31/Jan/2018 11:32:32] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/compute/v2.1/os-keypairs HTTP/1.1" 200 5152
> [31/Jan/2018 11:32:32] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481
> [31/Jan/2018 11:32:33] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=provider-core-cmn-v4
> HTTP/1.1" 200 654 [31/Jan/2018 11:32:33] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/network/v2.0/floatingips.json HTTP/1.1" 201 434
> [31/Jan/2018 11:32:34] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481
> [31/Jan/2018 11:32:34] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/network/v2.0/security-groups.json?name=onap_sg_MYGL
> HTTP/1.1" 200 2628 [31/Jan/2018 11:32:36] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481
> [31/Jan/2018 11:32:37] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/network/v2.0/ports.json HTTP/1.1" 201 760
> [31/Jan/2018 11:32:38] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481
> [31/Jan/2018 11:32:38] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481
> [31/Jan/2018 11:35:55] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481
> [31/Jan/2018 11:35:55] "GET /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=oam_onap_MYGL
> HTTP/1.1" 200 631 [31/Jan/2018 11:35:56] "POST /api/multicloud-titanium_
> cloud/v0/pod25_regionOne/identity/v2.0/tokens HTTP/1.1" 200 4481
>

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

2018-01-31 Thread Alexis de Talhouët

Marco,

Yes, that’s because you need to update manually the /etc/hosts of the 
vnc-portal to point to the new clusterIP of the SDC services.
This has been made dynamic in master, but not in amsterdam.

Thanks,
Alexis

> On Jan 31, 2018, at 9:09 AM, PLATANIA, MARCO (MARCO) 
>  wrote:
> 
> Alexis,
>  
> Another issue that I see after rebuilding SDC is that Portal cannot access 
> it. I received connection timeout when it tries to resolve 
> sdc.api.simpledemo.org . This SDC is healthy 
> and using dmaap.onap-message-router as UEB endpoint.
>  
> Marco
>  
> From:  on behalf of Alexis de Talhouët 
> 
> Date: Wednesday, January 31, 2018 at 8:18 AM
> To: "Ramanarayanan, Karthick" 
> Cc: "onap-discuss@lists.onap.org" 
> Subject: Re: [onap-discuss] [**EXTERNAL**] Service distribution error on 
> latest ONAP/OOM
>  
> Hello Karthick, Brian 
>  
> I think, thanks to Marco, we have identified one piece of the problem.
> I guess you guys are running a K8S cluster. The way UEB is configured in SDC 
> is using the K8S hosts IPs, so DCAE service (when deployed), can reach it 
> when retrieving the config using the following request (replace K8S_HOST 
> 
>  with one of your host ip):
>  
> curl -X GET \
>   http://K8S_HOST:30205/sdc/v1/distributionUebCluster 
> 
>  \
>   -H 'Accept: application/json' \
>   -H 'Content-Type: application/json' \
>   -H 'X-ECOMP-InstanceID: mso' \
>   -H 'authorization: Basic 
> dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=‘
>  
> I guess, if you try this request on the setup where it was failing before, 
> you’ll get the list where the first elements look ok, but the second one is 
> wrong, See https://jira.onap.org/browse/OOM-638 
> 
>  for more details.
> This has now been fix.
>  
> That said, it seems this is not it, and there is still something breaking SDC 
> UEB registration. 
>  
> Can you confirm you’re running in a K8S cluster?  I’m looking into this.
>  
> Alexis
> 
> 
>> On Jan 26, 2018, at 1:22 PM, Ramanarayanan, Karthick > > wrote:
>>  
>> The sdc-backend was always a suspect in my setup (56 core) and I invariably 
>> used to restart the backend pods to get the backend health checks to succeed:
>> curl http://127.0.0.1:30205/sdc2/rest/healthCheck 
>> 
>>  
>> This returns "Service unavailable" when backend doesn't come up. If you 
>> restart the cassandra/es/kibana pods and then restart the backend, it would 
>> come up.
>>  
>> In my single node k8s host (k8s directly on the host as in my earlier runs),
>> I see health check component DE for backend failing. (distribution engine)
>>  
>> Everything else is up.
>>  
>> curl http://127.0.0.1:30205/sdc2/rest/healthCheck 
>> 
>>  
>>  {
>>   "healthCheckComponent": "DE",
>>   "healthCheckStatus": "DOWN",
>>   "description": "U-EB cluster is not available"
>> },
>>  
>> This probably implies that in my setup, the UebServers list fetched in the 
>> backend catalog code before running the DistributionHealthCheck servers 
>> fetched from the distributionEngine configuration is not proper. (when 
>> running without dcae vm or dcae disabled)
>>  
>> This is probably the reason why distribution for service fails with policy 
>> exception.
>> Its not able to find the ueb server list perhaps when dcae is disabled.
>> Alexis would know best.
>>  
>> Regards,
>> -Karthick
>> From: FREEMAN, BRIAN D >
>> Sent: Friday, January 26, 2018 9:52:24 AM
>> To: Alexis de Talhouët; Ramanarayanan, Karthick
>> Cc: onap-discuss@lists.onap.org 
>> Subject: RE: [onap-discuss] [**EXTERNAL**] Service distribution error on 
>> latest ONAP/OOM
>>  
>> Alexi,
>> 
>> 
>> 
>> I cant get OOM install to work today (it was working yesterday) - seems to 
>> fail on sdc - doesnt pass healthcheck due to sdc-be as best I can tell .
>> 
>> 
>> 
>> I use cd.sh should i use the 4 step process

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

2018-01-31 Thread PLATANIA, MARCO (MARCO)

Alexis,

Another issue that I see after rebuilding SDC is that Portal cannot access it. 
I received connection timeout when it tries to resolve sdc.api.simpledemo.org. 
This SDC is healthy and using dmaap.onap-message-router as UEB endpoint.

Marco

From:  on behalf of Alexis de Talhouët 

Date: Wednesday, January 31, 2018 at 8:18 AM
To: "Ramanarayanan, Karthick" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM

Hello Karthick, Brian

I think, thanks to Marco, we have identified one piece of the problem.
I guess you guys are running a K8S cluster. The way UEB is configured in SDC is 
using the K8S hosts IPs, so DCAE service (when deployed), can reach it when 
retrieving the config using the following request (replace 
K8S_HOST
 with one of your host ip):

curl -X GET \
  
http://K8S_HOST:30205/sdc/v1/distributionUebCluster
 \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'X-ECOMP-InstanceID: mso' \
  -H 'authorization: Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=‘

I guess, if you try this request on the setup where it was failing before, 
you’ll get the list where the first elements look ok, but the second one is 
wrong, See 
https://jira.onap.org/browse/OOM-638
 for more details.
This has now been fix.

That said, it seems this is not it, and there is still something breaking SDC 
UEB registration.

Can you confirm you’re running in a K8S cluster?  I’m looking into this.

Alexis


On Jan 26, 2018, at 1:22 PM, Ramanarayanan, Karthick 
> wrote:

The sdc-backend was always a suspect in my setup (56 core) and I invariably 
used to restart the backend pods to get the backend health checks to succeed:
curl http://127.0.0.1:30205/sdc2/rest/healthCheck

This returns "Service unavailable" when backend doesn't come up. If you restart 
the cassandra/es/kibana pods and then restart the backend, it would come up.

In my single node k8s host (k8s directly on the host as in my earlier runs),
I see health check component DE for backend failing. (distribution engine)

Everything else is up.

curl http://127.0.0.1:30205/sdc2/rest/healthCheck

 {
  "healthCheckComponent": "DE",
  "healthCheckStatus": "DOWN",
  "description": "U-EB cluster is not available"
},

This probably implies that in my setup, the UebServers list fetched in the 
backend catalog code before running the DistributionHealthCheck servers fetched 
from the distributionEngine configuration is not proper. (when running without 
dcae vm or dcae disabled)

This is probably the reason why distribution for service fails with policy 
exception.
Its not able to find the ueb server list perhaps when dcae is disabled.
Alexis would know best.

Regards,
-Karthick

From: FREEMAN, BRIAN D >
Sent: Friday, January 26, 2018 9:52:24 AM
To: Alexis de Talhouët; Ramanarayanan, Karthick
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM

Alexi,



I cant get OOM install to work today (it was working yesterday) - seems to fail 
on sdc - doesnt pass healthcheck due to sdc-be as best I can tell .



I use cd.sh should i use the 4 step process below instead ?



Brian





-Original Message-

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

Sent: Friday, January 26, 2018 8:50 AM

To: Ramanarayanan, Karthick >

Cc: onap-discuss@lists.onap.org

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



Karthick,



I’ve just re-tested on latest Amsterdam, and distribute does work fine.



I don’t know if you have redeploy the whole ONAP or not, but understand that 
the issue you had with distribution not

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

2018-01-31 Thread Alexis de Talhouët

Ok, single instance should work fine now. It has been tested and is constantly 
being tested in the OpenLab.
Alexis

> On Jan 31, 2018, at 8:54 AM, FREEMAN, BRIAN D  wrote:
> 
> Alexis,
> I am out of town but when I was trying the install on Friday last week it was 
> failing on a non-clustered instance. A single 64 GB VM. It was working before 
> Friday but cant say if it broke on thur or wed.
>  
> Brian
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
> Sent: Wednesday, January 31, 2018 8:19 AM
> To: Ramanarayanan, Karthick 
> Cc: FREEMAN, BRIAN D ; onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] [**EXTERNAL**] Service distribution error on 
> latest ONAP/OOM
>  
> Hello Karthick, Brian
>  
> I think, thanks to Marco, we have identified one piece of the problem.
> I guess you guys are running a K8S cluster. The way UEB is configured in SDC 
> is using the K8S hosts IPs, so DCAE service (when deployed), can reach it 
> when retrieving the config using the following request (replace K8S_HOST 
> 
>  with one of your host ip):
>  
> curl -X GET \
>   http://K8S_HOST:30205/sdc/v1/distributionUebCluster 
> 
>  \
>   -H 'Accept: application/json' \
>   -H 'Content-Type: application/json' \
>   -H 'X-ECOMP-InstanceID: mso' \
>   -H 'authorization: Basic 
> dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=‘
>  
> I guess, if you try this request on the setup where it was failing before, 
> you’ll get the list where the first elements look ok, but the second one is 
> wrong, See https://jira.onap.org/browse/OOM-638 
> 
>  for more details.
> This has now been fix.
>  
> That said, it seems this is not it, and there is still something breaking SDC 
> UEB registration. 
>  
> Can you confirm you’re running in a K8S cluster?  I’m looking into this.
>  
> Alexis
> 
> 
> On Jan 26, 2018, at 1:22 PM, Ramanarayanan, Karthick  > wrote:
>  
> The sdc-backend was always a suspect in my setup (56 core) and I invariably 
> used to restart the backend pods to get the backend health checks to succeed:
> curl http://127.0.0.1:30205/sdc2/rest/healthCheck 
> 
>  
> This returns "Service unavailable" when backend doesn't come up. If you 
> restart the cassandra/es/kibana pods and then restart the backend, it would 
> come up.
>  
> In my single node k8s host (k8s directly on the host as in my earlier runs),
> I see health check component DE for backend failing. (distribution engine)
>  
> Everything else is up.
>  
> curl http://127.0.0.1:30205/sdc2/rest/healthCheck 
> 
>  
>  {
>   "healthCheckComponent": "DE",
>   "healthCheckStatus": "DOWN",
>   "description": "U-EB cluster is not available"
> },
>  
> This probably implies that in my setup, the UebServers list fetched in the 
> backend catalog code before running the DistributionHealthCheck servers 
> fetched from the distributionEngine configuration is not proper. (when 
> running without dcae vm or dcae disabled)
>  
> This is probably the reason why distribution for service fails with policy 
> exception.
> Its not able to find the ueb server list perhaps when dcae is disabled.
> Alexis would know best.
>  
> Regards,
> -Karthick
> From: FREEMAN, BRIAN D >
> Sent: Friday, January 26, 2018 9:52:24 AM
> To: Alexis de Talhouët; Ramanarayanan, Karthick
> Cc: onap-discuss@lists.onap.org 
> Subject: RE: [onap-discuss] [**EXTERNAL**] Service distribution error on 
> latest ONAP/OOM
>  
> Alexi,
> 
> 
> 
> I cant get OOM install to work today (it was working yesterday) - seems to 
> fail on sdc - doesnt pass healthcheck due to sdc-be as best I can tell .
> 
> 
> 
> I use cd.sh should i use the 4 step process below instead ?
> 
> 
> 
> Brian
> 
> 
> 
> 
> 
> -Original Message-
> 
> From: onap-discuss-boun...@lists.onap.org 
>  
> [mailto:onap-discuss-boun...@lists.onap.org 
> ] On Behalf Of Alexis de Talhouët
> 
> Sent: Friday, January 26, 2018 8:50 AM
> 
> To:

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

2018-01-31 Thread FREEMAN, BRIAN D

Alexis,
I am out of town but when I was trying the install on Friday last week it was 
failing on a non-clustered instance. A single 64 GB VM. It was working before 
Friday but cant say if it broke on thur or wed.

Brian

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Wednesday, January 31, 2018 8:19 AM
To: Ramanarayanan, Karthick 
Cc: FREEMAN, BRIAN D ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM

Hello Karthick, Brian

I think, thanks to Marco, we have identified one piece of the problem.
I guess you guys are running a K8S cluster. The way UEB is configured in SDC is 
using the K8S hosts IPs, so DCAE service (when deployed), can reach it when 
retrieving the config using the following request (replace 
K8S_HOST
 with one of your host ip):

curl -X GET \

http://K8S_HOST:30205/sdc/v1/distributionUebCluster
 \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'X-ECOMP-InstanceID: mso' \
  -H 'authorization: Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=‘

I guess, if you try this request on the setup where it was failing before, 
you’ll get the list where the first elements look ok, but the second one is 
wrong, See 
https://jira.onap.org/browse/OOM-638
 for more details.
This has now been fix.

That said, it seems this is not it, and there is still something breaking SDC 
UEB registration.

Can you confirm you’re running in a K8S cluster?  I’m looking into this.

Alexis

On Jan 26, 2018, at 1:22 PM, Ramanarayanan, Karthick 
> wrote:

The sdc-backend was always a suspect in my setup (56 core) and I invariably 
used to restart the backend pods to get the backend health checks to succeed:
curl http://127.0.0.1:30205/sdc2/rest/healthCheck

This returns "Service unavailable" when backend doesn't come up. If you restart 
the cassandra/es/kibana pods and then restart the backend, it would come up.

In my single node k8s host (k8s directly on the host as in my earlier runs),
I see health check component DE for backend failing. (distribution engine)

Everything else is up.

curl http://127.0.0.1:30205/sdc2/rest/healthCheck

 {
  "healthCheckComponent": "DE",
  "healthCheckStatus": "DOWN",
  "description": "U-EB cluster is not available"
},

This probably implies that in my setup, the UebServers list fetched in the 
backend catalog code before running the DistributionHealthCheck servers fetched 
from the distributionEngine configuration is not proper. (when running without 
dcae vm or dcae disabled)

This is probably the reason why distribution for service fails with policy 
exception.
Its not able to find the ueb server list perhaps when dcae is disabled.
Alexis would know best.

Regards,
-Karthick

From: FREEMAN, BRIAN D >
Sent: Friday, January 26, 2018 9:52:24 AM
To: Alexis de Talhouët; Ramanarayanan, Karthick
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM

Alexi,

I cant get OOM install to work today (it was working yesterday) - seems to fail 
on sdc - doesnt pass healthcheck due to sdc-be as best I can tell .

I use cd.sh should i use the 4 step process below instead ?

Brian

-Original Message-

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

Sent: Friday, January 26, 2018 8:50 AM

To: Ramanarayanan, Karthick >

Cc: onap-discuss@lists.onap.org

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

Karthick,

I’ve just re-tested on latest Amsterdam, and distribute does work fine.

I don’t know if you have redeploy the whole ONAP or not, but understand that 
the issue you had with distribution not working was an issue

impacting so aai and sdc.

The reason is, sdc is configured with the ueb cluster ip address (dmaap, the 
message bus

Re: [onap-discuss] [oom] Question on DCAE deployment using OOM

2018-01-31 Thread Alexis de Talhouët

Hi,

Let’s clarify one thing, OOM is the medium to deploy ONAP. DCAE doesn’t provide 
a way to be deployed in Kubernetes for now, hence OOM is not able to do this.

What OOM does is create the HEAT stack in OpenStack, HEAT stack that will 
create a VM running the dcae-boostrap container, which will then deploy the 
whole DCAE. OOM has created a wrapper on top of this so one can seamlessly 
deploy ONAP using OOM, as it’s done with HEAT. Please see the attachment here: 
https://jira.onap.org/browse/OOM-508  
explaining the implementation.

DCAE team and OOM team are working together to see how we can migrate DCAE 
components into Kubernetes deployment/services.  That work is still in 
progress, and I don’t have a clear view of the timeline for completion. Until 
this is done, ONAP will still requires a VIM to deploy DCAE.

Thanks,
Alexis

> On Jan 31, 2018, at 2:17 AM, Kumar Skand Priya, Viswanath V via onap-discuss 
>  wrote:
> 
> Dear OOM Team,
> 
> We found that, even-though OOM deploys DCAE bootstrap container inside a POD, 
> the bootstrap container in-turn deploys other DCAE components as VMs in 
> underlying VIM ( openstack ).
> 
> Would like to know, why doesn't entire DCAE run under kubern8s mode? and also 
> what's the story of DCAE's LCM with OOM, since some parts of DCAE are still 
> in VM mode ?
> 
> BR,
> Viswa
> 
>  
> 
> Viswanath Kumar Skand Priya
> Architect
> Verizon India ( VDSI )
> 
>  <>___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss

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

Re: [onap-discuss] [oom] ONAP R1 | Unable to distribute models to AAI in OOM deployment

2018-01-31 Thread Alexis de Talhouët

Hi,

Can you look at the logs of the model-loader component of AAI?

Thanks,
Alexis

> On Jan 31, 2018, at 3:03 AM, Kumar Skand Priya, Viswanath V via onap-discuss 
>  wrote:
> 
> Dear OOM Team,
> 
> We are powering ONAP R1 using OOM. While the installation is successful, we 
> are facing issues while distributing a network service from SDC to AAI. 
> 
> PS : 
> There are no issues with R1 standalone ONAP deployment ( via HOT files ).
> Restarting AAI and/or redeploying PODs doesn't help.
> 
> Details about Error :
> 
> In OOM setup, after distributing the SDC model, we are getting  "deploy 
> error" in AAI, which blocks the deployment of network service. Below are the 
> screenshots:
> 
> 
> 
> 
> 
> 
> 
> Log from AAI-datarouter
> 
> 2018-01-30T07:44:53.722Z||main|DataRouter||org.onap.aai.datarouter.policy.EntityEventPolicy||ERROR|EEP012E|EEP012E
>  Failed to create Search index topography-search-index due to: Error during 
> GET operation to AAI with message = java.net.UnknownHostException: 
> aai.searchservice.simpledemo.openecomp.org 
>    |
> 2018-01-30T07:44:53.722Z||main|DataRouter||org.onap.aai.datarouter.policy.EntityEventPolicy||INFO|EEP0007I|EEP0007I
>  Entity Event Policy component started.|
> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.impl.converter.DefaultTypeConverter||WARN|Overriding
>  type converter from: StaticMethodTypeConverter: public static 
> java.io.InputStream 
> org.apache.camel.component.http.HttpConverter.toInputStream(javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange)
>  throws java.io.IOException to: StaticMethodTypeConverter: public static 
> java.io.InputStream 
> org.apache.camel.component.http4.HttpConverter.toInputStream(javax.servlet.http.HttpServletRequest,org.apache.camel.Exchange)
>  throws java.io.IOException
> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.impl.converter.DefaultTypeConverter||WARN|Overriding
>  type converter from: StaticMethodTypeConverter: public static 
> javax.servlet.http.HttpServletResponse 
> org.apache.camel.component.http.HttpConverter.toServletResponse(org.apache.camel.Message)
>  to: StaticMethodTypeConverter: public static 
> javax.servlet.http.HttpServletResponse 
> org.apache.camel.component.http4.HttpConverter.toServletResponse(org.apache.camel.Message)
> 2018-01-30T07:44:53.865Z||main|DataRouter||org.apache.camel.impl.converter.DefaultTypeConverter||WARN|Overriding
>  type converter from: StaticMethodTypeConverter: public static 
> javax.servlet.http.HttpServletRequest 
> org.apache.camel.component.http.HttpConverter.toServletRequest(org.apache.camel.Message)
>  to: StaticMethodTypeConverter: public static 
> javax.servlet.http.HttpServletRequest 
> org.apache.camel.component.http4.HttpConverter.toServletRequest(org.apache.camel.Message)
> 2018-01-30T07:44:55.047Z||main|DataRouter||ajsc.ComputeService||ERROR|NMBS-COMPUTESVC-0042:
>  addRoute for data-router:entity-event:v1 failed  - EXCEPTION: null
> CAUSED BY: org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 109; 
> Element type "from" must be followed by either attribute specifications, ">" 
> or "/>".
> STACKTRACE: at 
> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl(createUnmarshalException:578)
> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl(unmarshal0:264)
> at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl(unmarshal:229)
> at ajsc.ComputeService(getRouteDefinition:793)
> at ajsc.ComputeService$getRouteDefinition$3(callCurrent:-1)
> at ajsc.ComputeService(addRoute:820)
> at ajsc.ComputeService$_init_closure15(doCall:970)
> at ajsc.ComputeService(init:970)
> at ajsc.ComputeService$init(call:-1)
> at ajsc.RouteMgmtService(init:148)
> at ajsc.RouteMgmtService$init$0(call:-1)
> at ajsc.ContextMgr(onApplicationEvent:19)
> at 
> org.springframework.context.event.SimpleApplicationEventMulticaster(invokeListener:163)
> at 
> org.springframework.context.event.SimpleApplicationEventMulticaster(multicastEvent:136)
> at 
> org.springframework.context.support.AbstractApplicationContext(publishEvent:381)
> at 
> org.springframework.context.support.AbstractApplicationContext(publishEvent:335)
> at 
> org.springframework.context.support.AbstractApplicationContext(finishRefresh:855)
> at org.springframework.context.support.AbstractApplicationContext(refresh:541)
> at 
> org.springframework.web.context.ContextLoader(configureAndRefreshWebApplicationContext:444)
> at org.eclipse.jetty.server.handler.ContextHandler(startContext:791)
> at org.eclipse.jetty.servlet.ServletContextHandler(startContext:294)
> at org.eclipse.jetty.webapp.WebAppContext(startWebapp:1349)
> at org.eclipse.jetty.webapp.WebAppContext(startContext:1342)
> at org.eclipse.jetty.server.handler.ContextHandler(doStart:741)
> at org.eclipse.jetty.webapp.WebAppContext(doStart:505)
> at org.eclipse.jetty.util.component.AbstractLifeCycle(start:68)
> at

Re: [onap-discuss] [E] Re: [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

2018-01-31 Thread Thiruveedula, Bharath via onap-discuss

Hi Alexis,

(Sorry Ramu for hijacking the mail)

I am also facing the same error.

The parameter you are referring "dcae_keystone_url" is the value in*
/opt/config/keystone_url.txt*?

First of all, let me clear you that I am trying t install DCAEGEN2 using
heat way not the OOM approach. Though the approach for installing DCAE in
heat or OOM is the same, but the parameter is sligtly different it seems.

In the heat way of installation, we have three files pointing to  keystone:
1) */opt/config/keystone_url.txt* ->
"*http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
*
"
2) */opt/config/**openstack_keystone_url.txt* ->
"*http://10.0.14.1/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0
*
"
3) */opt/config/dnsaas_keystone_url.txt* -> "*http://10.0.0.8/identity
*"

And below is the contents of /tmp/local_inputs.yaml

ubuntu1604image_id: 'ubuntu-16.04-x86_64-v1-core'
centos7image_id: 'centos-7-x86_64-v4-core'
flavor_id: 'm1.xlarge'
security_group: 'onap_sg_MYGL'
public_net: 'provider-core-cmn-v4'
private_net: 'oam_onap_MYGL'
openstack:
  username: 'admin'
  password: 'admin_pw'
  tenant_name: 'ONAP_Manual_Installation'
  auth_url: 'http://10.0.14.1/api/multicloud-titanium_cloud/v0/
pod25_regionOne/identity/v2.0'
  region: 'regionOne'
keypair: 'onap_key_MYGL'
key_filename: ./key600
location_prefix: 'dcae'
location_domain: 'MYGL.USWIN'
codesource_url: 'https://nexus.onap.org/service/local/repositories/
raw/content'
codesource_version: 'org.onap.dcaegen2.deployments/releases'

I tried to see the request logs from multicloud

[31/Jan/2018 11:31:22] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v3/auth/tokens
HTTP/1.1" 201 5135 [31/Jan/2018 11:31:24] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN.
HTTP/1.1" 200 635 [31/Jan/2018 11:31:24] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones
HTTP/1.1" 200 618 [31/Jan/2018 11:31:35] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/dns-delegate/v2/zones?name=MYGL.USWIN.
HTTP/1.1" 200 635 [31/Jan/2018 11:32:30] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:31] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=oam_onap_MYGL
HTTP/1.1" 200 631 [31/Jan/2018 11:32:31] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0 HTTP/1.1"
200 185 [31/Jan/2018 11:32:31] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:32] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/compute/v2.1/os-keypairs
HTTP/1.1" 200 5152 [31/Jan/2018 11:32:32] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:33] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=provider-core-cmn-v4
HTTP/1.1" 200 654 [31/Jan/2018 11:32:33] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/floatingips.json
HTTP/1.1" 201 434 [31/Jan/2018 11:32:34] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:34] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/security-groups.json?name=onap_sg_MYGL
HTTP/1.1" 200 2628 [31/Jan/2018 11:32:36] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:37] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/ports.json
HTTP/1.1" 201 760 [31/Jan/2018 11:32:38] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:32:38] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:35:55] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:35:55] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=oam_onap_MYGL
HTTP/1.1" 200 631 [31/Jan/2018 11:35:56] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:35:56] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/security-groups.json?name=onap_sg_MYGL
HTTP/1.1" 200 2628 [31/Jan/2018 11:35:57] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/identity/v2.0/tokens
HTTP/1.1" 200 4481 [31/Jan/2018 11:35:57] "GET
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/networks.json?name=provider-core-cmn-v4
HTTP/1.1" 200 654 [31/Jan/2018 11:35:58] "POST
/api/multicloud-titanium_cloud/v0/pod25_regionOne/network/v2.0/floatingips.json
HTTP/1.1" 201 434 [31/Jan/2018 11:35:58] "GET

[onap-discuss] [modeling] ONAP IM discussion meeting

2018-01-31 Thread yangxu (H)

Hi Kevin & Andy,

I think it’s time to discuss how to start the Papyrus work and make a concrete 
agreement/specification for R2’s information model.
Are you available at 8:00 a.m. US eastern time (9:00 p.m. Beijing time) on 
Thursday or Friday? Let’s have one hour discussion on this and try to address 
the comments on the current model.

We can use zoom id: 9117271979 for this call. Please tell me your preferred 
time, thanks in advance.
And anyone who is interested in this work is welcomed to join.

Best regards,
Xu Yang

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

Re: [onap-discuss] 答复: Using VF-C

2018-01-31 Thread Lars-Erik Helander

Thank you Yan.
The "onboarding" page mentions VFs and VFCs, where can I find more
information about the definition of the term "VFC" ?

/Lars

2018-01-30 8:21 GMT+01:00 Yan Yang :

> Hi Lars,
>
>
>
> Thanks for your question.
>
> Please see my response below in your email.
>
>
>
>
>
> Best Regards,
>
> Yan
>
> *发件人:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org] *代表 *Lars-Erik Helander
> *发送时间:* 2018年1月29日 18:11
> *收件人:* onap-discuss@lists.onap.org
> *主题:* [onap-discuss] Using VF-C
>
>
>
> I would like to try out the VF-C part ONAP and have a few questions:
>
>
>
> 1)  are there any ready made packages with TOSCA based descriptors
> available somewhere
>
> https://wiki.onap.org/display/DW/VOLTE+test+case+input+
> collection+for+tracking
>
> 2)  do you have to create the required packages using SDC or could you
> use externally created packages
>
> Vendor provides the csar packages and imports into SDC
>
> 3) if the answer to 2) is YES => what is the onboarding procedure for
> externally created packages?
>
> https://wiki.onap.org/display/DW/Resource+Onboarding
>
>
>
>
>
>
>
> I have deployed ONAP using OOM.
>
>
>
> /Lars
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

2018-01-31 Thread Determe, Sebastien

Hi,
Do you have the java stack trace associated to that issue please ?
Thank you,
Seb

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elie Dit Cosaque, 
David (Nokia - US/Irving)
Sent: Tuesday, January 30, 2018 4:59 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

Hello All,

We changed the authorization password based on the changes in CLAMP-74 in 
app.jar. Now the initial error is gone but we are facing another one.

The following request fails with error 500:

GET /restservices/clds/v1/clds/sdc/services/ HTTP/1.1
Host: :8080
HTTP/1.1 500

Has anyone faced the same issue in ONAP Amsterdam (Heat deployment)? Are we 
missing something ? Any help is appreciated!
Thanks,
David.

From: Elie Dit Cosaque, David (Nokia - US/Irving)
Sent: Monday, January 29, 2018 10:56 AM
To: onap-discuss@lists.onap.org
Subject: Clamp error connecting to SDC

Hello All,

We are trying to run the vFW demo with close loop. However when accessing the 
CLAMP designer, we see a forbidden error when CLAMP is trying to connect to SDC 
(to get the templates?). After some investigations it appears that CLAMP might 
be using an invalid authorization. Clamp is using “Basic dGVzdDoxMjM0NTY=” 
which leads to a forbidden (403) error for URL: 
http://sdc.api.simpledemo.onap.org:8080/sdc/v1/catalog/services.
 Using “Basic dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=” 
in postman is successful.
Has anyone seen this error? How can we correct it?

Log below:
23:05:37.546 [ajscUser~CNG-CSI~5c1cff6d-ce81-47f5-a35b-07028c153dd9] ERROR 
org.onap.clamp.clds.client.SdcCatalogServices - Exception when attempting to 
open SDC error stream
java.io.IOException: Server returned HTTP response code: 403 for URL: 
http://sdc.api.simpledemo.onap.org:8080/sdc/v1/catalog/services
at 
sun.net.https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=www.protocol.http.HttpURLConnection.getInputStream0%28HttpURLConnection.java%3a1876=682b9b49-43d5-4f61-a39d-a2a56819bf0c=6c7ce660e3fe5aefe98c2ff6c0868b94f1fd96da-5871e854d4391bd085ffcdf18c63e40333935f62
at 
sun.net.https://smex12-5-en-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=www.protocol.http.HttpURLConnection.getInputStream%28HttpURLConnection.java%3a1474=682b9b49-43d5-4f61-a39d-a2a56819bf0c=6c7ce660e3fe5aefe98c2ff6c0868b94f1fd96da-762a77c7a3f694d9ce4cb07c6a213e3e99c7
at 
org.onap.clamp.clds.client.SdcCatalogServices.getInputStream(SdcCatalogServices.java:409)
at 
org.onap.clamp.clds.client.SdcCatalogServices.getResponse(SdcCatalogServices.java:386)
at 
org.onap.clamp.clds.client.SdcCatalogServices.getSdcServicesInformation(SdcCatalogServices.java:113)
at 
org.onap.clamp.clds.service.CldsService.getSdcServices(CldsService.java:571)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:180)
at 
org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:189)
at org.apache.cxf.jaxrs.JAXRSInvoker.invoke(JAXRSInvoker.java:99)
at 
org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
at 
org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:96)
at 
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
at 
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
at 
org.apache.camel.component.cxf.cxfbean.CxfBeanDestination.process(CxfBeanDestination.java:83)
at 
org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:103)
at 
org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)
at 
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)
at

Re: [onap-discuss] Any consensus on the two IMs proposed

[onap-discuss] [modeling] Whether How and when we should move to Github for modeling spec update process

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

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

Re: [onap-discuss] [modeling] ONAP IM discussion meeting

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

[onap-discuss] [OOM][MSB] Kube2MSB RBAC security issues

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

Re: [onap-discuss] [modeling] ONAP IM discussion meeting

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

[onap-discuss] [dcaegen2] DCAE weekly meeting tomorrow to be extended by 30 minutes

[onap-discuss] Canceled event: [vvp] Weekly Meeting (starting Dec. 5, /2017) @ Weekly from 6am to 7am on Tuesday (PST) (onap-discuss@lists.onap.org)

Re: [onap-discuss] [E] Re: [oom] ONAP R1 | Unable to distribute models to AAI in OOM deployment

Re: [onap-discuss] [integration][OpenLab] Orange Open labs +integration repos

Re: [onap-discuss] [E] [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

Re: [onap-discuss] [E] Re: [oom] ONAP R1 | Unable to distribute models to AAI in OOM deployment

Re: [onap-discuss] [E] Re: [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

Re: [onap-discuss] [E] Re: [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

Re: [onap-discuss] [E] Re: [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

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

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

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

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

Re: [onap-discuss] [oom] Question on DCAE deployment using OOM

Re: [onap-discuss] [oom] ONAP R1 | Unable to distribute models to AAI in OOM deployment

Re: [onap-discuss] [E] Re: [DCAGEN2] Proxied DNS Designate only with Multicloud Titanium

[onap-discuss] [modeling] ONAP IM discussion meeting

Re: [onap-discuss] 答复: Using VF-C

Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to SDC

31 matches

Site Navigation

Mail list logo

Footer information