Re: [onap-discuss] 答复: RE: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80

2018-01-09 Thread yuan.hu1
Addtion question, what's the inputs of the Tosca Parser in Clamp, is it a Tosca 
CSAR package?























原始邮件



发件人:袁虎10090474
收件人: ;
抄送人: ;
日 期 :2018年01月10日 10:25
主 题 :[onap-discuss] 答复: RE: [clamp] Questions about 
https://jira.onap.org/browse/CLAMP-80


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



Hi Martial,






What's the data format of a mS transmitted  between SDC and CLAMP?


What's the sequence flow between the  SDC/DCAE-DS, Parser and CLAMP? Did the 
CLAMP download the TOSCA CSAR package of the mS from SDC/DCAE-DS to local 
first, and then decode the package to obtain the properties/parameters of the 
mS?






Best Regards,


Yuan Hu



















发件人: ;
收件人:袁虎10090474; ;
抄送人: ; ;
日 期 :2018年01月09日 23:59
主 题 :RE: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80




Hello Yuan,


 


The goal of the Tosca parser in CLAMP would be to decode the transmitted 
properties of a micro-service between SDC and CLAMP.


The Tosca model would contain the description of properties/parameters of a mS 
designed in SDC/DCAE-DS ( and would be sent by DCAE-DS/SDC to CLAMP), but this  
is still to be confirmed, normally this week, with the DCAE-DS/SDC team.


 


Br,


Martial


 


From: yuan@zte.com.cn [mailto:yuan@zte.com.cn] 
 Sent: mardi 9 janvier 2018 02:44
 To: Lefevre, Catherine ; Ngueko, Gervais-Martial 

 Cc: onap-discuss@lists.onap.org
 Subject: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80


 

Hi Martial and Catherine,

 

I see there has a issue for TOSCA Model Parser in Clamp, see 
https://jira.onap.org/browse/CLAMP-80 for  details.

Did you want to integrate a TOSCA Model Parser in Clamp?

What's the usage of the TOSCA Model Parser in Clamp, can you give an example?

As far as I know, there also has private Tosca Model Parser, in the SDC project 
and the VFC project. What is the relationship between these Parser?

 

Thanks,

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


[onap-discuss] 答复: RE: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80

2018-01-09 Thread yuan.hu1
Hi Martial,






What's the data format of a mS transmitted  between SDC and CLAMP?


What's the sequence flow between the  SDC/DCAE-DS, Parser and CLAMP? Did the 
CLAMP download the TOSCA CSAR package of the mS from SDC/DCAE-DS to local 
first, and then decode the package to obtain the properties/parameters of the 
mS?






Best Regards,


Yuan Hu











原始邮件



发件人: ;
收件人:袁虎10090474; ;
抄送人: ; ;
日 期 :2018年01月09日 23:59
主 题 :RE: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80




Hello Yuan,


 


The goal of the Tosca parser in CLAMP would be to decode the transmitted 
properties of a micro-service between SDC and CLAMP.


The Tosca model would contain the description of properties/parameters of a mS 
designed in SDC/DCAE-DS ( and would be sent by DCAE-DS/SDC to CLAMP), but this  
is still to be confirmed, normally this week, with the DCAE-DS/SDC team.


 


Br,


Martial


 


From: yuan@zte.com.cn [mailto:yuan@zte.com.cn] 
 Sent: mardi 9 janvier 2018 02:44
 To: Lefevre, Catherine ; Ngueko, Gervais-Martial 

 Cc: onap-discuss@lists.onap.org
 Subject: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80


 

Hi Martial and Catherine,

 

I see there has a issue for TOSCA Model Parser in Clamp, see 
https://jira.onap.org/browse/CLAMP-80 for  details.

Did you want to integrate a TOSCA Model Parser in Clamp?

What's the usage of the TOSCA Model Parser in Clamp, can you give an example?

As far as I know, there also has private Tosca Model Parser, in the SDC project 
and the VFC project. What is the relationship between these Parser?

 

Thanks,

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


Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release testing

2018-01-09 Thread HERNANDEZ-HERRERO, JORGE
Hello, I reopened POLICY-486 as it seems to have some side effects on PAP 
initialization that have leaked into 1.1.2  amsterdam version.
Mike in our team is looking into it.
-Jorge

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ozgur
Sent: Tuesday, January 09, 2018 2:40 PM
To: Gary Wu ; Alexis de Talhouët 
Cc: onap-discuss ; FLOOD, JERRY ; 
Eric Debeau 
Subject: Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release 
testing



09.01.2018, 23:35, "Gary Wu" 
>:

How do we get the fix?  Will there be new docker images?



Hello,

I don't have idea of the docker and here the explained bug fix:

https://jira.onap.org/browse/polıcy-501




Thanks,

Gary



From: Ozgur [mailto:o...@zgur.org]
Sent: Tuesday, January 09, 2018 12:32 PM
To: Alexis de Talhouët 
>; Gary Wu 
>
Cc: Eric Debeau >; FLOOD, 
JERRY >; onap-discuss 
>
Subject: Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release 
testing







09.01.2018, 18:23, "Alexis de Talhouët" 
>:

In addition to what Marco said, Policy version has changed recently, from 
v1.1.1 to v1.1.2. See mail: 
https://lists.onap.org/pipermail/onap-discuss/2018-January/007204.html
 where I explain my errors.





@Alex,

"thread blocking" bug shouldn't happen anymore, patchset should be applied, I 
tried and bug fixed.



Ozgur



Alexis





On Jan 8, 2018, at 8:59 PM, Gary Wu 
> wrote:



Thanks Marco.



Pam, is this issue already being tracked by policy?  Or should we log a new 
Jira ticket?



Thanks,

Gary



From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, January 08, 2018 5:57 PM
To: Gary Wu >; Yunxia Chen 
>; onap-discuss 
>; 'Chengli 
Wang' >; Kang 
Xi >; Yang Xu (Yang, Fixed 
Network) >; FLOOD, JERRY 
>; Eric Debeau 
>; DRAGOSH, PAMELA L 
(PAM) >
Subject: Re: [integration] ONAP Amsterdam Maintenance release testing



Gary,



The issue with Policy is that PAP can’t connect to PDP.



echo "pushPolicy : PUT : com.MicroServicevCPE"

+ echo 'pushPolicy : PUT : com.MicroServicevCPE'

curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d 
'{

  "pdpGroup": "default",

  "policyName": "com.MicroServicevCPE",

PE300 - Data Issue: response code of the URL is 404.  This indicates a problem 
with getting the version from the PAP or the policy does not exist.pushPolicy : 
PUT : com.MicroServicevCPE

  "policyType": "MicroService"

}' 
'http://pdp:8081/pdp/api/pushPolicy'

+ curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d 
'{

  "pdpGroup": "default",

  "policyName": "com.MicroServicevCPE",

  "policyType": "MicroService"

}' 
http://pdp:8081/pdp/api/pushPolicy

* Hostname was 

Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release testing

2018-01-09 Thread Ozgur
  09.01.2018, 23:35, "Gary Wu" :How do we get the fix?  Will there be new docker images?  Hello, I don't have idea of the docker and here the explained bug fix: https://jira.onap.org/browse/polıcy-501  Thanks,Gary From: Ozgur [mailto:o...@zgur.org]Sent: Tuesday, January 09, 2018 12:32 PMTo: Alexis de Talhouët ; Gary Wu Cc: Eric Debeau ; FLOOD, JERRY ; onap-discuss Subject: Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release testing   09.01.2018, 18:23, "Alexis de Talhouët" :In addition to what Marco said, Policy version has changed recently, from v1.1.1 to v1.1.2. See mail: https://lists.onap.org/pipermail/onap-discuss/2018-January/007204.html where I explain my errors.  @Alex,"thread blocking" bug shouldn't happen anymore, patchset should be applied, I tried and bug fixed. Ozgur Alexis  On Jan 8, 2018, at 8:59 PM, Gary Wu  wrote: Thanks Marco. Pam, is this issue already being tracked by policy?  Or should we log a new Jira ticket? Thanks,Gary From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com] Sent: Monday, January 08, 2018 5:57 PMTo: Gary Wu ; Yunxia Chen ; onap-discuss ; 'Chengli Wang' ; Kang Xi ; Yang Xu (Yang, Fixed Network) ; FLOOD, JERRY ; Eric Debeau ; DRAGOSH, PAMELA L (PAM) Subject: Re: [integration] ONAP Amsterdam Maintenance release testing Gary, The issue with Policy is that PAP can’t connect to PDP. echo "pushPolicy : PUT : com.MicroServicevCPE"+ echo 'pushPolicy : PUT : com.MicroServicevCPE'curl -v --silent -X PUT --header 'Content-Type: application/json' --header 'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d '{  "pdpGroup": "default",  "policyName": "com.MicroServicevCPE",PE300 - Data Issue: response code of the URL is 404.  This indicates a problem with getting the version from the PAP or the policy does not exist.pushPolicy : PUT : com.MicroServicevCPE  "policyType": "MicroService"}' 'http://pdp:8081/pdp/api/pushPolicy' + curl -v --silent -X PUT --header 'Content-Type: application/json' --header 'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d '{  "pdpGroup": "default",  "policyName": "com.MicroServicevCPE",  "policyType": "MicroService"}' http://pdp:8081/pdp/api/pushPolicy* Hostname was NOT found in DNS cache*   Trying 172.18.0.6...* Connected to pdp (172.18.0.6) port 8081 (#0)> PUT /pdp/api/pushPolicy HTTP/1.1> User-Agent: curl/7.35.0> Host: pdp:8081> Content-Type: application/json> Accept: text/plain> ClientAuth: cHl0aG9uOnRlc3Q=> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==> Environment: TEST> Content-Length: 99> } [data not shown]* upload completely sent off: 99 out of 99 bytes< HTTP/1.1 400 Bad Request* Server Apache-Coyote/1.1 is not blacklisted< Server: Apache-Coyote/1.1< Content-Type: text/plain;charset=ISO-8859-1< Content-Length: 146< Date: Mon, 08 Jan 2018 21:30:45 GMT< Connection: close< { [data not shown]* Closing connection 0 We already faced this issue a couple of days ago while debugging OOM, not sure whether it’s being tracked somewhere. Thanks,Marco From: Gary Wu Date: Monday, January 8, 2018 at 7:17 PMTo: Yunxia Chen , onap-discuss , "PLATANIA, MARCO (MARCO)" , 'Chengli Wang' , Kang Xi , "Yang Xu (Yang, Fixed Network)" , "FLOOD, JERRY" , Eric Debeau Subject: RE: [integration] ONAP Amsterdam Maintenance release testing It’s been about 5 hours since the deployments, and none of the environments have passed health checks.  Here are the current failures: Integration-Jenkins: policy, vidIntegration-SB-03: policyIntegration-SB-04: policy, uuiIntegration-SB-05: dcae, policy It seems that policy is currently failing consistently, plus some others that fail sporadically.  Does anyone know what the issue is with policy? Thanks,Gary From: Gary Wu Sent: Monday, January 08, 2018 12:30 PMTo: Yunxia Chen ; onap-discuss ; PLATANIA, MARCO (MARCO) ; 'Chengli Wang' ; Kang Xi ; Yang Xu (Yang, Fixed Network) ; Jerry Flood ; Eric Debeau Subject: RE: [integration] ONAP Amsterdam Maintenance release testing It’s taking a while since we’re doing several simultaneous deployments.  

Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release testing

2018-01-09 Thread Gary Wu
How do we get the fix?  Will there be new docker images?

Thanks,
Gary

From: Ozgur [mailto:o...@zgur.org]
Sent: Tuesday, January 09, 2018 12:32 PM
To: Alexis de Talhouët ; Gary Wu 
Cc: Eric Debeau ; FLOOD, JERRY ; 
onap-discuss 
Subject: Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release 
testing



09.01.2018, 18:23, "Alexis de Talhouët" 
>:
In addition to what Marco said, Policy version has changed recently, from 
v1.1.1 to v1.1.2. See mail: 
https://lists.onap.org/pipermail/onap-discuss/2018-January/007204.html where I 
explain my errors.


@Alex,
"thread blocking" bug shouldn't happen anymore, patchset should be applied, I 
tried and bug fixed.

Ozgur

Alexis


On Jan 8, 2018, at 8:59 PM, Gary Wu 
> wrote:

Thanks Marco.

Pam, is this issue already being tracked by policy?  Or should we log a new 
Jira ticket?

Thanks,
Gary

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, January 08, 2018 5:57 PM
To: Gary Wu >; Yunxia Chen 
>; onap-discuss 
>; 'Chengli 
Wang' >; Kang 
Xi >; Yang Xu (Yang, Fixed 
Network) >; FLOOD, JERRY 
>; Eric Debeau 
>; DRAGOSH, PAMELA L 
(PAM) >
Subject: Re: [integration] ONAP Amsterdam Maintenance release testing

Gary,

The issue with Policy is that PAP can’t connect to PDP.

echo "pushPolicy : PUT : com.MicroServicevCPE"
+ echo 'pushPolicy : PUT : com.MicroServicevCPE'
curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d 
'{
  "pdpGroup": "default",
  "policyName": "com.MicroServicevCPE",
PE300 - Data Issue: response code of the URL is 404.  This indicates a problem 
with getting the version from the PAP or the policy does not exist.pushPolicy : 
PUT : com.MicroServicevCPE
  "policyType": "MicroService"
}' 'http://pdp:8081/pdp/api/pushPolicy'
+ curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d 
'{
  "pdpGroup": "default",
  "policyName": "com.MicroServicevCPE",
  "policyType": "MicroService"
}' http://pdp:8081/pdp/api/pushPolicy
* Hostname was NOT found in DNS cache
*   Trying 172.18.0.6...
* Connected to pdp (172.18.0.6) port 8081 (#0)
> PUT /pdp/api/pushPolicy HTTP/1.1
> User-Agent: curl/7.35.0
> Host: pdp:8081
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 99
>
} [data not shown]
* upload completely sent off: 99 out of 99 bytes
< HTTP/1.1 400 Bad Request
* Server Apache-Coyote/1.1 is not blacklisted
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 146
< Date: Mon, 08 Jan 2018 21:30:45 GMT
< Connection: close
<
{ [data not shown]
* Closing connection 0

We already faced this issue a couple of days ago while debugging OOM, not sure 
whether it’s being tracked somewhere.

Thanks,
Marco

From: Gary Wu >
Date: Monday, January 8, 2018 at 7:17 PM
To: Yunxia Chen >, 
onap-discuss >, 
"PLATANIA, MARCO (MARCO)" 
>, 'Chengli Wang' 
>, Kang Xi 
>, "Yang Xu (Yang, Fixed 
Network)" >, "FLOOD, JERRY" 
>, Eric Debeau 
>
Subject: RE: [integration] ONAP Amsterdam Maintenance release testing

It’s been about 5 hours since the deployments, and none of the environments 
have passed health checks.  Here are the current failures:

Integration-Jenkins: policy, vid
Integration-SB-03: policy
Integration-SB-04: policy, uui
Integration-SB-05: dcae, policy

It seems that policy is currently failing consistently, plus some others that 
fail sporadically.  Does anyone know what the issue is with 

Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release testing

2018-01-09 Thread Ozgur
  09.01.2018, 18:23, "Alexis de Talhouët" :In addition to what Marco said, Policy version has changed recently, from v1.1.1 to v1.1.2. See mail: https://lists.onap.org/pipermail/onap-discuss/2018-January/007204.html where I explain my errors.  @Alex,"thread blocking" bug shouldn't happen anymore, patchset should be applied, I tried and bug fixed. Ozgur Alexis  On Jan 8, 2018, at 8:59 PM, Gary Wu  wrote: Thanks Marco. Pam, is this issue already being tracked by policy?  Or should we log a new Jira ticket? Thanks,Gary From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com] Sent: Monday, January 08, 2018 5:57 PMTo: Gary Wu ; Yunxia Chen ; onap-discuss ; 'Chengli Wang' ; Kang Xi ; Yang Xu (Yang, Fixed Network) ; FLOOD, JERRY ; Eric Debeau ; DRAGOSH, PAMELA L (PAM) Subject: Re: [integration] ONAP Amsterdam Maintenance release testing Gary, The issue with Policy is that PAP can’t connect to PDP. echo "pushPolicy : PUT : com.MicroServicevCPE"+ echo 'pushPolicy : PUT : com.MicroServicevCPE'curl -v --silent -X PUT --header 'Content-Type: application/json' --header 'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d '{  "pdpGroup": "default",  "policyName": "com.MicroServicevCPE",PE300 - Data Issue: response code of the URL is 404.  This indicates a problem with getting the version from the PAP or the policy does not exist.pushPolicy : PUT : com.MicroServicevCPE  "policyType": "MicroService"}' 'http://pdp:8081/pdp/api/pushPolicy' + curl -v --silent -X PUT --header 'Content-Type: application/json' --header 'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d '{  "pdpGroup": "default",  "policyName": "com.MicroServicevCPE",  "policyType": "MicroService"}' http://pdp:8081/pdp/api/pushPolicy* Hostname was NOT found in DNS cache*   Trying 172.18.0.6...* Connected to pdp (172.18.0.6) port 8081 (#0)> PUT /pdp/api/pushPolicy HTTP/1.1> User-Agent: curl/7.35.0> Host: pdp:8081> Content-Type: application/json> Accept: text/plain> ClientAuth: cHl0aG9uOnRlc3Q=> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==> Environment: TEST> Content-Length: 99> } [data not shown]* upload completely sent off: 99 out of 99 bytes< HTTP/1.1 400 Bad Request* Server Apache-Coyote/1.1 is not blacklisted< Server: Apache-Coyote/1.1< Content-Type: text/plain;charset=ISO-8859-1< Content-Length: 146< Date: Mon, 08 Jan 2018 21:30:45 GMT< Connection: close< { [data not shown]* Closing connection 0 We already faced this issue a couple of days ago while debugging OOM, not sure whether it’s being tracked somewhere. Thanks,Marco From: Gary Wu Date: Monday, January 8, 2018 at 7:17 PMTo: Yunxia Chen , onap-discuss , "PLATANIA, MARCO (MARCO)" , 'Chengli Wang' , Kang Xi , "Yang Xu (Yang, Fixed Network)" , "FLOOD, JERRY" , Eric Debeau Subject: RE: [integration] ONAP Amsterdam Maintenance release testing It’s been about 5 hours since the deployments, and none of the environments have passed health checks.  Here are the current failures: Integration-Jenkins: policy, vidIntegration-SB-03: policyIntegration-SB-04: policy, uuiIntegration-SB-05: dcae, policy It seems that policy is currently failing consistently, plus some others that fail sporadically.  Does anyone know what the issue is with policy? Thanks,Gary From: Gary Wu Sent: Monday, January 08, 2018 12:30 PMTo: Yunxia Chen ; onap-discuss ; PLATANIA, MARCO (MARCO) ; 'Chengli Wang' ; Kang Xi ; Yang Xu (Yang, Fixed Network) ; Jerry Flood ; Eric Debeau Subject: RE: [integration] ONAP Amsterdam Maintenance release testing It’s taking a while since we’re doing several simultaneous deployments.  I’ll send out another update when the environments are up. The Jenkins URL is: http://12.234.32.117/jenkins/. Thanks,Gary From: Yunxia Chen Sent: Monday, January 08, 2018 11:30 AMTo: Gary Wu ; onap-discuss ; PLATANIA, MARCO (MARCO) ; 'Chengli Wang' ; Kang Xi ; Yang Xu (Yang, Fixed Network) ; Jerry Flood ; Eric Debeau Subject: Re: [integration] ONAP Amsterdam Maintenance release testing Thank you Gary. 

[onap-discuss] ONAP Instant Messaging Survey

2018-01-09 Thread Kenny Paul
All,

We have a number of challenges regarding an instant messaging solution for 
ONAP. Chief among these are access limitations set by companies or governments. 
 Another contributor is what is actually deployable, maintainable and scalable 
in both a technical and budgetary context.  The last challenge is everyone’s 
personal favorite solution which may or may not fit the needs of the ONAP 
community in the broader sense. 

To help identify the “best fit” Instant Messaging solution for ONAP I would 
like everyone to participate in a brief survey.  This is for information 
gathering purposes; I’ll stop short of calling this a requirements gathering 
exercise, although some of the results will help to drive requirements.  

Estimated time to complete is 4 mins. I’ll leave this up for a week or so to 
get an idea of what the landscape looks like.
https://www.surveymonkey.com/r/39CLJSS 

Please note this does not imply our ability to deploy or support all of the 
potential solutions listed on the survey.   

Thanks!
 
Best Regards, 
-kenny

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

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


Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable to bring up Portal Pod

2018-01-09 Thread Alexis de Talhouët
Hi,

Can you send the logs?

Thanks,
Alexis

> On Jan 9, 2018, at 2:37 PM, Kumar Skand Priya, Viswanath V via onap-discuss 
>  wrote:
> 
> + David +Michael
> 
> Dear OOM Team, 
> 
> Could you please help us here?
> 
> BR,
> Viswa 
> 
> 
>  
> 
> Viswanath Kumar Skand Priya
> Architect
> Verizon Network Ops & Eng
> 
>  <>
> On Tue, Jan 9, 2018 at 8:48 PM, Karthik  > wrote:
> 
> Hi Team , Good day !
> 
> I followed the Quick Installation 
> 
>  steps to install ONAP.  All pods are up and running except "Portal".I tried 
> multiple times to bring up  "Portal" pod , but  could not able to solve the 
> problem . "portalapps", "vnc-portal" are keep on hangs with 
> Waiting:PodInitializing status. I have attached the log and status images . 
> Please refer it and reply to me if you could help me in this problem. 
> Environment Details:
> Ubuntu 16, RAM 50 GB.
> 
> Thanks in Advance.
> 
> Regards,
> Karthik. 
> 
> 
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=9F3pNUkzjE-2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ=1wzEUJLKAZ5LZAneHRBQxkYxkMLXTv8JhWkMey42Hxs=U_2wA2qR_M9dVFk_k6fHcJXE3fe6-i1rUHcwwENkXAU=
>  
> 
> 
> 
> ___
> 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] [E] [oom] OOM Installation Problem | Unable to bring up Portal Pod

2018-01-09 Thread Kumar Skand Priya, Viswanath V via onap-discuss
+ David +Michael

Dear OOM Team,

Could you please help us here?

BR,
Viswa




Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng


On Tue, Jan 9, 2018 at 8:48 PM, Karthik  wrote:

>
> Hi Team , Good day !
>
> I followed the Quick Installation
> 
>  steps
> to install ONAP.  All pods are up and running except "*Portal*".I tried
> multiple times to bring up  "Portal" pod , but  could not able to solve
> the problem . "portalapps", "vnc-portal" are keep on hangs with
> *Waiting:PodInitializing* status. I have attached the log and status
> images . Please refer it and reply to me if you could help me in this
> problem.
> Environment Details:
> Ubuntu 16, RAM 50 GB.
>
> Thanks in Advance.
>
> Regards,
> Karthik.
>
>
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.
> onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=
> udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ=9F3pNUkzjE-
> 2v1eTClkRVakDRN8GH7Bm-wt1lWkxoUyyDORTqf5MxNO_GrMBs0gZ=
> 1wzEUJLKAZ5LZAneHRBQxkYxkMLXTv8JhWkMey42Hxs=U_2wA2qR_
> M9dVFk_k6fHcJXE3fe6-i1rUHcwwENkXAU=
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [**EXTERNAL**] Re: Failure to create the demo vfirewall VNF

2018-01-09 Thread Ramanarayanan, Karthick
Inline ...



From: Alexis de Talhouët 
Sent: Tuesday, January 9, 2018 10:40 AM
To: Ramanarayanan, Karthick
Cc: BRIAN D FREEMAN; onap-discuss@lists.onap.org
Subject: [**EXTERNAL**] Re: [onap-discuss] Failure to create the demo vfirewall 
VNF

Hi,

Please refer to

https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack


for setting up OOM on Kubernetes, on Racnher, in OpenStack. Please discard the 
update wrt DCAE (I said it’s merge, but not just yet).


Yes. It was using that doc, the rancher, k8s setup was brought up for onap.
I have to check back on DCAE and running it without dcae on k8s again though!


Regards,
-Karthick

And please refer to

https://wiki.onap.org/display/DW/vFWCL+instantiation%2C+testing%2C+and+debuging

for running vFWCL use case. Of course, without DCAE, you won’t have close loop.




Thanks,
Alexis


On Jan 9, 2018, at 1:36 PM, Ramanarayanan, Karthick 
> wrote:

Yes.
I checked at sdnc pods, vnf pods, mso pods.
Found nothing pertaining to the error.
A sample sdnc pod check (apart from other pods)
kubectl -n onap-sdnc -c sdnc-controller-container logs sdnc-1395102659-w48gp

Now I have to redo this test again as I am running out of memory here.
Note that this is a 14 core(28 threads for 56 total in cpuinfo),
128 gig ram. (Intel Xeon E5-2683 v3)
Before I ran the OOM, I had /proc/sys/vm/drop_caches done to just start with a 
free memory of over
120 gigs. (After clearing the kernel buffer caches for a big head start for 
ONAP :)

Then the kubernetes setup to relaunch onap/rancher,etc.

These have been up for over 3-4 days now and now my free memory is almost down 
to 30 gig
 on the caches side. Free memory minus caches is a meagre 800 megs.

Now suddenly the portals are unresponsive.

The sdc frontend has stopped responding with gateway timeouts though I am fire 
a curl sdc2/rest/version to the backend. Frontend is dead!

Its a cluster fuck now.

I will restart the onap setup again before redoing the demo vfwcl instance 
create.
(also with delete rollback set to false during vf create as Marco suggested)

Hopefully you have tested a demo instance creation on a k8s setup with OOM on 
amsterdam.
 (not with ONAP running on openstack as the demo video shows)

Thanks,
-Karthick


From: FREEMAN, BRIAN D >
Sent: Tuesday, January 9, 2018 5:41:48 AM
To: Ramanarayanan, Karthick; 
onap-discuss@lists.onap.org
Subject: [**EXTERNAL**] RE: Failure to create the demo vfirewall VNF

You need to look at SO logs for the SdncAdapter and VnfAdapter and see what 
error you are getting from SDNC or Openstack in SO.



Usually a delete implies that SO talks to SDNC correctly but then the 
interaction with Openstack fails or when SO goes to SDNC or AAI for data to 
create the Openstack heat stack create that it is failing.



Brian





From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramanarayanan, 
Karthick
Sent: Monday, January 08, 2018 6:33 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Failure to create the demo vfirewall VNF



Hi,
 I am trying to instantiate the demo vfirewall-vsink service instance based on 
the video here:



 
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4#RunningtheONAPDemos-VNFOnboarding,Instantiation,andClosed-loopOperations



 While I am able to move ahead and reach till the vf create step, the add VF 
step
 for both vfirewall and packet gen instance results in failure and moves to 
pending delete.
 (sdnc preload checkbox enabled)



 The setup I have is OOM configured for kubernetes.
 I am on amsterdam release branch for OOM.
So its not using openstack heat templates
 to instantiate ONAP. 

Re: [onap-discuss] Failure to create the demo vfirewall VNF

2018-01-09 Thread Alexis de Talhouët
Hi,

Please refer to

https://wiki.onap.org/display/DW/ONAP+on+Kubernetes+on+Rancher+in+OpenStack 


for setting up OOM on Kubernetes, on Racnher, in OpenStack. Please discard the 
update wrt DCAE (I said it’s merge, but not just yet).

And please refer to 

https://wiki.onap.org/display/DW/vFWCL+instantiation%2C+testing%2C+and+debuging 


for running vFWCL use case. Of course, without DCAE, you won’t have close loop.

Thanks,
Alexis


> On Jan 9, 2018, at 1:36 PM, Ramanarayanan, Karthick  
> wrote:
> 
> Yes. 
> I checked at sdnc pods, vnf pods, mso pods.
> Found nothing pertaining to the error.
> A sample sdnc pod check (apart from other pods)
> kubectl -n onap-sdnc -c sdnc-controller-container logs sdnc-1395102659-w48gp
> 
> Now I have to redo this test again as I am running out of memory here.
> Note that this is a 14 core(28 threads for 56 total in cpuinfo), 
> 128 gig ram. (Intel Xeon E5-2683 v3)
> Before I ran the OOM, I had /proc/sys/vm/drop_caches done to just start with 
> a free memory of over
> 120 gigs. (After clearing the kernel buffer caches for a big head start for 
> ONAP :)
> 
> Then the kubernetes setup to relaunch onap/rancher,etc. 
> 
> These have been up for over 3-4 days now and now my free memory is almost 
> down to 30 gig
>  on the caches side. Free memory minus caches is a meagre 800 megs.
> 
> Now suddenly the portals are unresponsive.
> 
> The sdc frontend has stopped responding with gateway timeouts though I am 
> fire a curl sdc2/rest/version to the backend. Frontend is dead!
> 
> Its a cluster fuck now.
> 
> I will restart the onap setup again before redoing the demo vfwcl instance 
> create.
> (also with delete rollback set to false during vf create as Marco suggested)
> 
> Hopefully you have tested a demo instance creation on a k8s setup with OOM on 
> amsterdam.
>  (not with ONAP running on openstack as the demo video shows)
> 
> Thanks,
> -Karthick
> 
> From: FREEMAN, BRIAN D 
> Sent: Tuesday, January 9, 2018 5:41:48 AM
> To: Ramanarayanan, Karthick; onap-discuss@lists.onap.org
> Subject: [**EXTERNAL**] RE: Failure to create the demo vfirewall VNF
>  
> You need to look at SO logs for the SdncAdapter and VnfAdapter and see what 
> error you are getting from SDNC or Openstack in SO.
>  
> Usually a delete implies that SO talks to SDNC correctly but then the 
> interaction with Openstack fails or when SO goes to SDNC or AAI for data to 
> create the Openstack heat stack create that it is failing.
>  
> Brian
>  
>  
> From: onap-discuss-boun...@lists.onap.org 
> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramanarayanan, 
> Karthick
> Sent: Monday, January 08, 2018 6:33 PM
> To: onap-discuss@lists.onap.org
> Subject: [onap-discuss] Failure to create the demo vfirewall VNF
>  
> Hi,
>  I am trying to instantiate the demo vfirewall-vsink service instance based 
> on the video here:
>  
>  
> https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4#RunningtheONAPDemos-VNFOnboarding,Instantiation,andClosed-loopOperations
>  
> 
>  
>  While I am able to move ahead and reach till the vf create step, the add VF 
> step 
>  for both vfirewall and packet gen instance results in failure and moves to 
> pending delete.
>  (sdnc preload checkbox enabled)
>  
>  The setup I have is OOM configured for kubernetes. 
>  I am on amsterdam release branch for OOM.
> So its not using openstack heat templates
>  to instantiate ONAP. Rather just a single node configured with k8s oneclick.
>  
>  The difference in the video pertains to running demo-k8s.sh init from 
> oom/kubernetes/robot
>  to instantiate the customer models and services after copying the demo/heat
>  to kubernetes robot /share directory for the distribute the work.
>  
>  The demo vfirewall closed loop service seems to be distributed as seen in 
> the ONAP portal.
>  ( I have also tried redistributing)
>  I am trying to instantiate the service for demo vFWCL.
>  
>  Logs indicate nothing in sdnc after the vF create failure. 
>  I don't see any requests hitting Openstack logs either.
>  
>  The VNF preload operation seems to have succeeded for the firewall closed 
> loop instances.
>  The VNF profiles are also present in sdnc.
>  
>  I get back a http success (status code 200) with the request id as expected.
>  A subsequent GET request for vnf topology information preloaded also works.
>  
>  Doing a 

Re: [onap-discuss] Failure to create the demo vfirewall VNF

2018-01-09 Thread Ramanarayanan, Karthick
Yes.

I checked at sdnc pods, vnf pods, mso pods.

Found nothing pertaining to the error.

A sample sdnc pod check (apart from other pods)

kubectl -n onap-sdnc -c sdnc-controller-container logs sdnc-1395102659-w48gp


Now I have to redo this test again as I am running out of memory here.

Note that this is a 14 core(28 threads for 56 total in cpuinfo),

128 gig ram. (Intel Xeon E5-2683 v3)

Before I ran the OOM, I had /proc/sys/vm/drop_caches done to just start with a 
free memory of over

120 gigs. (After clearing the kernel buffer caches for a big head start for 
ONAP :)


Then the kubernetes setup to relaunch onap/rancher,etc.


These have been up for over 3-4 days now and now my free memory is almost down 
to 30 gig

 on the caches side. Free memory minus caches is a meagre 800 megs.


Now suddenly the portals are unresponsive.


The sdc frontend has stopped responding with gateway timeouts though I am fire 
a curl sdc2/rest/version to the backend. Frontend is dead!


Its a cluster fuck now.


I will restart the onap setup again before redoing the demo vfwcl instance 
create.

(also with delete rollback set to false during vf create as Marco suggested)


Hopefully you have tested a demo instance creation on a k8s setup with OOM on 
amsterdam.

 (not with ONAP running on openstack as the demo video shows)


Thanks,

-Karthick



From: FREEMAN, BRIAN D 
Sent: Tuesday, January 9, 2018 5:41:48 AM
To: Ramanarayanan, Karthick; onap-discuss@lists.onap.org
Subject: [**EXTERNAL**] RE: Failure to create the demo vfirewall VNF


You need to look at SO logs for the SdncAdapter and VnfAdapter and see what 
error you are getting from SDNC or Openstack in SO.



Usually a delete implies that SO talks to SDNC correctly but then the 
interaction with Openstack fails or when SO goes to SDNC or AAI for data to 
create the Openstack heat stack create that it is failing.



Brian





From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramanarayanan, 
Karthick
Sent: Monday, January 08, 2018 6:33 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Failure to create the demo vfirewall VNF



Hi,

 I am trying to instantiate the demo vfirewall-vsink service instance based on 
the video here:



 
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4#RunningtheONAPDemos-VNFOnboarding,Instantiation,andClosed-loopOperations



 While I am able to move ahead and reach till the vf create step, the add VF 
step

 for both vfirewall and packet gen instance results in failure and moves to 
pending delete.

 (sdnc preload checkbox enabled)



 The setup I have is OOM configured for kubernetes.

 I am on amsterdam release branch for OOM.

So its not using openstack heat templates

 to instantiate ONAP. Rather just a single node configured with k8s oneclick.



 The difference in the video pertains to running demo-k8s.sh init from 
oom/kubernetes/robot

 to instantiate the customer models and services after copying the demo/heat

 to kubernetes robot /share directory for the distribute the work.



 The demo vfirewall closed loop service seems to be distributed as seen in the 
ONAP portal.

 ( I have also tried redistributing)

 I am trying to instantiate the service for demo vFWCL.



 Logs indicate nothing in sdnc after the vF create failure.

 I don't see any requests hitting Openstack logs either.



 The VNF preload operation seems to have succeeded for the firewall closed loop 
instances.

 The VNF profiles are also present in sdnc.



 I get back a http success (status code 200) with the request id as expected.

 A subsequent GET request for vnf topology information preloaded also works.



 Doing a POST using sdnc api (port 8282) works for the vnf topology preload 
step.

 But I see nothing in the logs for sdnc pods. (nothing relevant in sdc/mso pod 
either if that matters)



 Here is a snippet from curl to sdnc as well:



curl -vX POST 
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.43.172.252:8282/restconf/operations/VNF-API:preload-vnf-topology-operation
 -d @firewall.json --header "Content-Type: application/json"



Response status is http 200 as 

[onap-discuss] How to test the vFW configuration and deployment

2018-01-09 Thread bharath thiruveedula
Hi

I have followed the instructions at [1] to deploy vFW usecase in non closed 
loop environment. But I am wondering how to test configuration and 
functionality of vFW use case ?  Can anyone give some pointers where I find the 
steps to test the functionality/configuration of vFW?

[1]https://wiki.onap.org/display/DW/running+vFW+Demo+on+ONAP+Amsterdam+Release

Best Regards
Bharath T
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [clamp] Questions about https://jira.onap.org/browse/CLAMP-80

2018-01-09 Thread Ngueko, Gervais-Martial
Hello Yuan,

The goal of the Tosca parser in CLAMP would be to decode the transmitted 
properties of a micro-service between SDC and CLAMP.
The Tosca model would contain the description of properties/parameters of a mS 
designed in SDC/DCAE-DS ( and would be sent by DCAE-DS/SDC to CLAMP), but this 
is still to be confirmed, normally this week, with the DCAE-DS/SDC team.

Br,
Martial

From: yuan@zte.com.cn [mailto:yuan@zte.com.cn]
Sent: mardi 9 janvier 2018 02:44
To: Lefevre, Catherine ; Ngueko, Gervais-Martial 

Cc: onap-discuss@lists.onap.org
Subject: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80


Hi Martial and Catherine,



I see there has a issue for TOSCA Model Parser in Clamp, see 
https://jira.onap.org/browse/CLAMP-80
 for details.

Did you want to integrate a TOSCA Model Parser in Clamp?

What's the usage of the TOSCA Model Parser in Clamp, can you give an example?

As far as I know, there also has private Tosca Model Parser, in the SDC project 
and the VFC project. What is the relationship between these Parser?



Thanks,

Yuan Hu




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


Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release testing

2018-01-09 Thread Gary Wu
Hi Jorge,

Please use the Integration-SB-03 environment for your debugging.  I may 
re-deploy the others from time-to-time to test new incremental changes.

Thanks,
Gary

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 09, 2018 5:26 AM
To: Gary Wu ; PLATANIA, MARCO (MARCO) 
; Yunxia Chen ; onap-discuss 
; 'Chengli Wang' ; 
Kang Xi ; Yang Xu (Yang, Fixed Network) 
; FLOOD, JERRY ; Eric Debeau 
; HERNANDEZ-HERRERO, JORGE 
Subject: Re: [integration] ONAP Amsterdam Maintenance release testing

Gary/Marco,

+Jorge

Jorge is back from vacation, perhaps we let him take a look and see why all of 
sudden this problem is happening. We assume the environment is setup correctly, 
i.e. /etc/hosts has the right DNS information. Has the overall environment 
changed since release last November? We are assuming for Amsterdam HEAT was 
still being used as is, no changes.

If there’s a bug then Marco can go ahead and file the JIRA and work with Jorge 
on determining the fix.

Regards,

Pam


From: Gary Wu >
Date: Monday, January 8, 2018 at 8:59 PM
To: "PLATANIA, MARCO (MARCO)" 
>, Yunxia Chen 
>, onap-discuss 
>, 'Chengli 
Wang' >, Kang 
Xi >, "Yang Xu (Yang, Fixed 
Network)" >, "FLOOD, JERRY" 
>, Eric Debeau 
>, "DRAGOSH, PAMELA L 
(PAM)" >
Subject: RE: [integration] ONAP Amsterdam Maintenance release testing

Thanks Marco.

Pam, is this issue already being tracked by policy?  Or should we log a new 
Jira ticket?

Thanks,
Gary

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, January 08, 2018 5:57 PM
To: Gary Wu >; Yunxia Chen 
>; onap-discuss 
>; 'Chengli 
Wang' >; Kang 
Xi >; Yang Xu (Yang, Fixed 
Network) >; FLOOD, JERRY 
>; Eric Debeau 
>; DRAGOSH, PAMELA L 
(PAM) >
Subject: Re: [integration] ONAP Amsterdam Maintenance release testing

Gary,

The issue with Policy is that PAP can’t connect to PDP.

echo "pushPolicy : PUT : com.MicroServicevCPE"
+ echo 'pushPolicy : PUT : com.MicroServicevCPE'
curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d 
'{
  "pdpGroup": "default",
  "policyName": "com.MicroServicevCPE",
PE300 - Data Issue: response code of the URL is 404.  This indicates a problem 
with getting the version from the PAP or the policy does not exist.pushPolicy : 
PUT : com.MicroServicevCPE
  "policyType": "MicroService"
}' 'http://pdp:8081/pdp/api/pushPolicy' 

+ curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d 
'{
  "pdpGroup": "default",
  "policyName": "com.MicroServicevCPE",
  "policyType": "MicroService"
}' 
http://pdp:8081/pdp/api/pushPolicy
* Hostname was NOT found in DNS cache
*   Trying 172.18.0.6...
* Connected to pdp (172.18.0.6) port 8081 (#0)
> PUT /pdp/api/pushPolicy HTTP/1.1
> User-Agent: curl/7.35.0
> Host: pdp:8081
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> 

Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release testing

2018-01-09 Thread DRAGOSH, PAMELA L (PAM)
Gary/Marco,

+Jorge

Jorge is back from vacation, perhaps we let him take a look and see why all of 
sudden this problem is happening. We assume the environment is setup correctly, 
i.e. /etc/hosts has the right DNS information. Has the overall environment 
changed since release last November? We are assuming for Amsterdam HEAT was 
still being used as is, no changes.

If there’s a bug then Marco can go ahead and file the JIRA and work with Jorge 
on determining the fix.

Regards,

Pam


From: Gary Wu 
Date: Monday, January 8, 2018 at 8:59 PM
To: "PLATANIA, MARCO (MARCO)" , Yunxia Chen 
, onap-discuss , 'Chengli 
Wang' , Kang Xi , "Yang Xu 
(Yang, Fixed Network)" , "FLOOD, JERRY" , 
Eric Debeau , "DRAGOSH, PAMELA L (PAM)" 

Subject: RE: [integration] ONAP Amsterdam Maintenance release testing

Thanks Marco.

Pam, is this issue already being tracked by policy?  Or should we log a new 
Jira ticket?

Thanks,
Gary

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, January 08, 2018 5:57 PM
To: Gary Wu ; Yunxia Chen ; 
onap-discuss ; 'Chengli Wang' 
; Kang Xi ; Yang Xu (Yang, 
Fixed Network) ; FLOOD, JERRY ; Eric 
Debeau ; DRAGOSH, PAMELA L (PAM) 

Subject: Re: [integration] ONAP Amsterdam Maintenance release testing

Gary,

The issue with Policy is that PAP can’t connect to PDP.

echo "pushPolicy : PUT : com.MicroServicevCPE"
+ echo 'pushPolicy : PUT : com.MicroServicevCPE'
curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d 
'{
  "pdpGroup": "default",
  "policyName": "com.MicroServicevCPE",
PE300 - Data Issue: response code of the URL is 404.  This indicates a problem 
with getting the version from the PAP or the policy does not exist.pushPolicy : 
PUT : com.MicroServicevCPE
  "policyType": "MicroService"
}' 'http://pdp:8081/pdp/api/pushPolicy' 

+ curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' -d 
'{
  "pdpGroup": "default",
  "policyName": "com.MicroServicevCPE",
  "policyType": "MicroService"
}' 
http://pdp:8081/pdp/api/pushPolicy
* Hostname was NOT found in DNS cache
*   Trying 172.18.0.6...
* Connected to pdp (172.18.0.6) port 8081 (#0)
> PUT /pdp/api/pushPolicy HTTP/1.1
> User-Agent: curl/7.35.0
> Host: pdp:8081
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 99
>
} [data not shown]
* upload completely sent off: 99 out of 99 bytes
< HTTP/1.1 400 Bad Request
* Server Apache-Coyote/1.1 is not blacklisted
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 146
< Date: Mon, 08 Jan 2018 21:30:45 GMT
< Connection: close
<
{ [data not shown]
* Closing connection 0

We already faced this issue a couple of days ago while debugging OOM, not sure 
whether it’s being tracked somewhere.

Thanks,
Marco

From: Gary Wu >
Date: Monday, January 8, 2018 at 7:17 PM
To: Yunxia Chen >, 
onap-discuss >, 
"PLATANIA, MARCO (MARCO)" 
>, 'Chengli Wang' 
>, Kang Xi 
>, "Yang Xu (Yang, Fixed 
Network)" >, "FLOOD, JERRY" 
>, Eric Debeau 
>
Subject: RE: [integration] ONAP Amsterdam Maintenance release testing

It’s been about 5 hours since the deployments, and none of the environments 
have passed 

Re: [onap-discuss] [integration] ONAP Amsterdam Maintenance release testing

2018-01-09 Thread Alexis de Talhouët
In addition to what Marco said, Policy version has changed recently, from 
v1.1.1 to v1.1.2. See mail: 
https://lists.onap.org/pipermail/onap-discuss/2018-January/007204.html 
 where 
I explain my errors.

Thanks,
Alexis


> On Jan 8, 2018, at 8:59 PM, Gary Wu  wrote:
> 
> Thanks Marco.
>  
> Pam, is this issue already being tracked by policy?  Or should we log a new 
> Jira ticket?
>  
> Thanks,
> Gary
>  
> From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com] 
> Sent: Monday, January 08, 2018 5:57 PM
> To: Gary Wu ; Yunxia Chen ; 
> onap-discuss ; 'Chengli Wang' 
> ; Kang Xi ; Yang Xu (Yang, 
> Fixed Network) ; FLOOD, JERRY ; Eric 
> Debeau ; DRAGOSH, PAMELA L (PAM) 
> 
> Subject: Re: [integration] ONAP Amsterdam Maintenance release testing
>  
> Gary,
>  
> The issue with Policy is that PAP can’t connect to PDP.
>  
> echo "pushPolicy : PUT : com.MicroServicevCPE"
> + echo 'pushPolicy : PUT : com.MicroServicevCPE'
> curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
> 'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
> 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' 
> -d '{
>   "pdpGroup": "default",
>   "policyName": "com.MicroServicevCPE",
> PE300 - Data Issue: response code of the URL is 404.  This indicates a 
> problem with getting the version from the PAP or the policy does not 
> exist.pushPolicy : PUT : com.MicroServicevCPE
>   "policyType": "MicroService"
> }' 'http://pdp:8081/pdp/api/pushPolicy' 
> + curl -v --silent -X PUT --header 'Content-Type: application/json' --header 
> 'Accept: text/plain' --header 'ClientAuth: cHl0aG9uOnRlc3Q=' --header 
> 'Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==' --header 'Environment: TEST' 
> -d '{
>   "pdpGroup": "default",
>   "policyName": "com.MicroServicevCPE",
>   "policyType": "MicroService"
> }' http://pdp:8081/pdp/api/pushPolicy 
> * Hostname was NOT found in DNS cache
> *   Trying 172.18.0.6...
> * Connected to pdp (172.18.0.6) port 8081 (#0)
> > PUT /pdp/api/pushPolicy HTTP/1.1
> > User-Agent: curl/7.35.0
> > Host: pdp:8081
> > Content-Type: application/json
> > Accept: text/plain
> > ClientAuth: cHl0aG9uOnRlc3Q=
> > Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> > Environment: TEST
> > Content-Length: 99
> > 
> } [data not shown]
> * upload completely sent off: 99 out of 99 bytes
> < HTTP/1.1 400 Bad Request
> * Server Apache-Coyote/1.1 is not blacklisted
> < Server: Apache-Coyote/1.1
> < Content-Type: text/plain;charset=ISO-8859-1
> < Content-Length: 146
> < Date: Mon, 08 Jan 2018 21:30:45 GMT
> < Connection: close
> < 
> { [data not shown]
> * Closing connection 0
>  
> We already faced this issue a couple of days ago while debugging OOM, not 
> sure whether it’s being tracked somewhere.
>  
> Thanks,
> Marco
>  
> From: Gary Wu >
> Date: Monday, January 8, 2018 at 7:17 PM
> To: Yunxia Chen >, 
> onap-discuss  >, "PLATANIA, MARCO (MARCO)" 
> >, 'Chengli 
> Wang' >, 
> Kang Xi >, "Yang Xu (Yang, 
> Fixed Network)" >, "FLOOD, 
> JERRY" >, Eric Debeau 
> >
> Subject: RE: [integration] ONAP Amsterdam Maintenance release testing
>  
> It’s been about 5 hours since the deployments, and none of the environments 
> have passed health checks.  Here are the current failures:
>  
> Integration-Jenkins: policy, vid
> Integration-SB-03: policy
> Integration-SB-04: policy, uui
> Integration-SB-05: dcae, policy
>  
> It seems that policy is currently failing consistently, plus some others that 
> fail sporadically.  Does anyone know what the issue is with policy?
>  
> Thanks,
> Gary
>  
> From: Gary Wu 
> Sent: Monday, January 08, 2018 12:30 PM
> To: Yunxia Chen >; 
> onap-discuss  >; PLATANIA, MARCO (MARCO) 
> >; 'Chengli 
> Wang' >; 
> Kang Xi >; Yang Xu (Yang, 
> Fixed Network) >; Jerry 
> Flood 

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

2018-01-09 Thread Alexis de Talhouët
Ok, so by having the cloud site as follow

"RegionAlex":
{
  "region_id": "RegionAlex",
  "clli": "RegionAlex",
  "aic_version": "2.5",
  "identity_service_id": "ALEX_KEYSTONE"
}

it’s showing correctly in VID. I also created its own clli in AAI.

But I thought the region does matter for OpenStack, doesn’t it?

Alexis

> On Jan 9, 2018, at 9:37 AM, FREEMAN, BRIAN D  wrote:
> 
> You need to name one RegionTwo or something,
>  
> From: onap-discuss-boun...@lists.onap.org 
> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
> Sent: Tuesday, January 09, 2018 9:34 AM
> To: onap-discuss 
> Subject: [onap-discuss] [AAI][SO] How to add another LCP Region
>  
> Hello AAI, SO expert,
>  
> I’m trying to add another LCP Region to be able to deploy VNF in another 
> OpenStack instance.
>  
> To do so, I have done the following:
>  
> In MSO:
> - Add a Cloud Site
>  
> "RegionAlex":
> {
>   "region_id": "RegionOne",
>   "clli": "RegionOne",
>   "aic_version": "2.5",
>   "identity_service_id": "ALEX_KEYSTONE"
> }
>  
> - Add it’s associated Cloud Identity Services
>  
>"ALEX_KEYSTONE":
> {
>   "identity_url": "http://10.195.194.215:5000/v2.0 
> ",
>   "mso_id": "nso",
>   "mso_pass": "86b74198e8ccb959eaaadefevsd2a8a2",
>   "admin_tenant": "service",
>   "member_role": "admin",
>   "tenant_metadata": true,
>   "identity_server_type": "KEYSTONE",
>   "identity_authentication_type": "USERNAME_PASSWORD"
> }
>  
> In AAI:
> - Create a cloud region
>  
> {
> "cloud-owner": "CloudOwner",
> "cloud-region-id": "RegionAlex",
> "cloud-type": "SharedNode",
> "owner-defined-type": "OwnerType",
> "cloud-region-version": "v1",
> "cloud-zone": "CloudZone",
> "sriov-automation": false,
> "resource-version": "1515506147118",
> "relationship-list": {
> "relationship": [
> {
> "related-to": "complex",
> "related-link": 
> "/aai/v11/cloud-infrastructure/complexes/complex/clli1",
> "relationship-data": [
> {
> "relationship-key": 
> "complex.physical-location-id",
> "relationship-value": "clli1"
> }
> ]
> }
> ]
> }
> }
>  
>  
> - Create the tenant in the region for the 4 different services with the right 
> tenant id:
>  
> {
> "tenant-id": "21ca0f4c2239475fbf1b4b499399163e",
> "tenant-name": "nso-rancher",
> "relationship-list": {
> "relationship": [
> {
> "related-to": "service-subscription",
> "related-link": 
> "/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vLB",
> "relationship-data": [
> {
> "relationship-key": "customer.global-customer-id",
> "relationship-value": "Demonstration"
> },
> {
> "relationship-key": 
> "service-subscription.service-type",
> "relationship-value": "vLB"
> }
> ]
> },
> {
> "related-to": "service-subscription",
> "related-link": 
> "/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vIMS",
> "relationship-data": [
> {
> "relationship-key": "customer.global-customer-id",
> "relationship-value": "Demonstration"
> },
> {
> "relationship-key": 
> "service-subscription.service-type",
> "relationship-value": "vIMS"
> }
> ]
> },
> {
> "related-to": "service-subscription",
> "related-link": 
> "/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFWCL",
> "relationship-data": [
> {
> "relationship-key": "customer.global-customer-id",
> "relationship-value": "Demonstration"
> },
> {
>  

Re: [onap-discuss] [ONAP Helpdesk #50852] RE: maven artifacts

2018-01-09 Thread Gary Wu via RT
Thanks Andy, I didn't realize that 1.1.0 was already released.

Victor, given that 1.1.0 is already released, you need to change your build 
dependencies to refer to the released 1.1.0 version instead of 1.1.0-SNAPSHOT, 
and also bump your current build version number to something newer like 
1.1.1-SNAPSHOT or 1.2.0-SNAPSHOT.

Thanks,
Gary

-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Tuesday, January 09, 2018 7:07 AM
To: Gary Wu 
Cc: bin.y...@windriver.com; onap-discuss@lists.onap.org; ruijing@intel.com; 
victor.mora...@intel.com
Subject: Re: [ONAP Helpdesk #50852] RE: [onap-discuss] maven artifacts

On 01/09/2018 06:34 AM, Gary Wu via RT wrote:
> 
> Tue Jan 09 09:34:10 2018: Request 50852 was acted upon.
>  Transaction: Ticket created by gary.i...@huawei.com
>Queue: ONAP Helpdesk
>  Subject: RE: [onap-discuss] maven artifacts
>Owner: Nobody
>   Requestors: gary.i...@huawei.com
>   Status: new
>  Ticket  https://rt.linuxfoundation.org/Ticket/Display.html?id=50852 >
> 
> 
> I’m not sure why the 1.1.0-SNAPSHOT versions disappeared again.  I wonder if 
> something is wrong with Nexus.
>
> Helpdesk, can you help?  1.1.0-SNAPSHOT used to exist here, but it has 
> since disappeared: 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicl
> oud/openstack/multicloud-openstack-newton/
> 
> Also, there are occasions where the merge job seems to have created 
> 1.1.0-SNAPSHOT but then it’s nowhere to be found:
> https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-mast
> er-newton-merge-java/57/console
> 
> Thanks,
> Gary

Nothing is wrong with Nexus. There is a 1.1.0 release of this artifact in the 
system [0] Nexus auto-purges SNAPSHOT copies of released artifacts as any 
further development _must_ end up on a new version since you can't release new 
copies of the same version. There is a grace period of 14 days that a SNAPSHOT 
version will continue to exist at the same time that there is a release 
version. But in this case we're way, way, way past that window since the 
release version of this happened in the middle of November (November 16, 2017 
to be specific).

If you end up generating a new SNAPSHOT artifact at a version in this state it 
will exist for a very, very short amount of time until the Nexus artifact 
reaper comes through which happens once a day.

-Andy-

[0]
https://nexus.onap.org/content/repositories/releases/org/onap/multicloud/openstack/multicloud-openstack-newton/1.1.0/

> 
> From: Morales, Victor [mailto:victor.mora...@intel.com]
> Sent: Monday, January 08, 2018 9:43 AM
> To: Gary Wu ; Yang, Bin (Wind River) 
> ; Guo, Ruijing ; 
> onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] maven artifacts
> 
> Hey Gary,
> 
> We’re still having issues to deploy the 1.1.0-SNAPSHOT version for 
> multicloud-openstack-newton artifact [1].  The –merge-java job looks 
> like was successfully executed [2] when the version was bumped [3] but 
> there is no artifact placed for that specific version, as consequence 
> other jobs are failing [4].  I’m not sure if the deployment process 
> needs to be done separately (per subproject) [5] given that the parent 
> pom.xml contains the reference of every subproject[6]
> 
> Regards/Saludos
> Victor Morales
> 
> [1] 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicl
> oud/openstack/multicloud-openstack-newton/
> [2] 
> https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/multicloud-op
> enstack-master-newton-merge-java/55/console.log.gz
> [3] https://gerrit.onap.org/r/#/c/24617/
> [4] 
> https://jenkins.onap.org/job/multicloud-openstack-master-ocata-verify-
> java/65/ [5] 
> https://git.onap.org/ci-management/tree/jjb/multicloud/multicloud-open
> stack.yaml [6] 
> https://git.onap.org/multicloud/openstack/tree/pom.xml#n37
> 
> From: 
>  .onap.org>> on behalf of Gary Wu 
> >
> Date: Thursday, December 21, 2017 at 9:58 AM
> To: "Yang, Bin (Wind River)" 
> >, "Guo, 
> Ruijing" >, 
> "onap-discuss@lists.onap.org" 
> >
> Subject: Re: [onap-discuss] maven artifacts
> 
> I’m not sure why it didn’t work before, but I just re-ran that job and now 
> the artifact is there.
> 
> Thanks,
> Gary
> 
> From: Yang, Bin [mailto:bin.y...@windriver.com]
> Sent: Wednesday, December 20, 2017 6:51 PM
> To: Gary Wu >; GUO, 
> RUIJING >; 
> onap-discuss@lists.onap.org
> Subject: RE: 

Re: [onap-discuss] [ONAP Helpdesk #50852] RE: maven artifacts

2018-01-09 Thread Gary Wu
Thanks Andy, I didn't realize that 1.1.0 was already released.

Victor, given that 1.1.0 is already released, you need to change your build 
dependencies to refer to the released 1.1.0 version instead of 1.1.0-SNAPSHOT, 
and also bump your current build version number to something newer like 
1.1.1-SNAPSHOT or 1.2.0-SNAPSHOT.

Thanks,
Gary

-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Tuesday, January 09, 2018 7:07 AM
To: Gary Wu 
Cc: bin.y...@windriver.com; onap-discuss@lists.onap.org; ruijing@intel.com; 
victor.mora...@intel.com
Subject: Re: [ONAP Helpdesk #50852] RE: [onap-discuss] maven artifacts

On 01/09/2018 06:34 AM, Gary Wu via RT wrote:
> 
> Tue Jan 09 09:34:10 2018: Request 50852 was acted upon.
>  Transaction: Ticket created by gary.i...@huawei.com
>Queue: ONAP Helpdesk
>  Subject: RE: [onap-discuss] maven artifacts
>Owner: Nobody
>   Requestors: gary.i...@huawei.com
>   Status: new
>  Ticket  https://rt.linuxfoundation.org/Ticket/Display.html?id=50852 >
> 
> 
> I’m not sure why the 1.1.0-SNAPSHOT versions disappeared again.  I wonder if 
> something is wrong with Nexus.
>
> Helpdesk, can you help?  1.1.0-SNAPSHOT used to exist here, but it has 
> since disappeared: 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicl
> oud/openstack/multicloud-openstack-newton/
> 
> Also, there are occasions where the merge job seems to have created 
> 1.1.0-SNAPSHOT but then it’s nowhere to be found:
> https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-mast
> er-newton-merge-java/57/console
> 
> Thanks,
> Gary

Nothing is wrong with Nexus. There is a 1.1.0 release of this artifact in the 
system [0] Nexus auto-purges SNAPSHOT copies of released artifacts as any 
further development _must_ end up on a new version since you can't release new 
copies of the same version. There is a grace period of 14 days that a SNAPSHOT 
version will continue to exist at the same time that there is a release 
version. But in this case we're way, way, way past that window since the 
release version of this happened in the middle of November (November 16, 2017 
to be specific).

If you end up generating a new SNAPSHOT artifact at a version in this state it 
will exist for a very, very short amount of time until the Nexus artifact 
reaper comes through which happens once a day.

-Andy-

[0]
https://nexus.onap.org/content/repositories/releases/org/onap/multicloud/openstack/multicloud-openstack-newton/1.1.0/

> 
> From: Morales, Victor [mailto:victor.mora...@intel.com]
> Sent: Monday, January 08, 2018 9:43 AM
> To: Gary Wu ; Yang, Bin (Wind River) 
> ; Guo, Ruijing ; 
> onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] maven artifacts
> 
> Hey Gary,
> 
> We’re still having issues to deploy the 1.1.0-SNAPSHOT version for 
> multicloud-openstack-newton artifact [1].  The –merge-java job looks 
> like was successfully executed [2] when the version was bumped [3] but 
> there is no artifact placed for that specific version, as consequence 
> other jobs are failing [4].  I’m not sure if the deployment process 
> needs to be done separately (per subproject) [5] given that the parent 
> pom.xml contains the reference of every subproject[6]
> 
> Regards/Saludos
> Victor Morales
> 
> [1] 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicl
> oud/openstack/multicloud-openstack-newton/
> [2] 
> https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/multicloud-op
> enstack-master-newton-merge-java/55/console.log.gz
> [3] https://gerrit.onap.org/r/#/c/24617/
> [4] 
> https://jenkins.onap.org/job/multicloud-openstack-master-ocata-verify-
> java/65/ [5] 
> https://git.onap.org/ci-management/tree/jjb/multicloud/multicloud-open
> stack.yaml [6] 
> https://git.onap.org/multicloud/openstack/tree/pom.xml#n37
> 
> From: 
>  .onap.org>> on behalf of Gary Wu 
> >
> Date: Thursday, December 21, 2017 at 9:58 AM
> To: "Yang, Bin (Wind River)" 
> >, "Guo, 
> Ruijing" >, 
> "onap-discuss@lists.onap.org" 
> >
> Subject: Re: [onap-discuss] maven artifacts
> 
> I’m not sure why it didn’t work before, but I just re-ran that job and now 
> the artifact is there.
> 
> Thanks,
> Gary
> 
> From: Yang, Bin [mailto:bin.y...@windriver.com]
> Sent: Wednesday, December 20, 2017 6:51 PM
> To: Gary Wu >; GUO, 
> RUIJING >; 
> onap-discuss@lists.onap.org
> Subject: RE: 

Re: [onap-discuss] [ONAP Helpdesk #50852] RE: maven artifacts

2018-01-09 Thread Andrew Grimberg via RT
On 01/09/2018 06:34 AM, Gary Wu via RT wrote:
> 
> Tue Jan 09 09:34:10 2018: Request 50852 was acted upon.
>  Transaction: Ticket created by gary.i...@huawei.com
>Queue: ONAP Helpdesk
>  Subject: RE: [onap-discuss] maven artifacts
>Owner: Nobody
>   Requestors: gary.i...@huawei.com
>   Status: new
>  Ticket https://rt.linuxfoundation.org/Ticket/Display.html?id=50852 >
> 
> 
> I’m not sure why the 1.1.0-SNAPSHOT versions disappeared again.  I wonder if 
> something is wrong with Nexus.
>
> Helpdesk, can you help?  1.1.0-SNAPSHOT used to exist here, but it has since 
> disappeared: 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicloud/openstack/multicloud-openstack-newton/
> 
> Also, there are occasions where the merge job seems to have created 
> 1.1.0-SNAPSHOT but then it’s nowhere to be found:
> https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-newton-merge-java/57/console
> 
> Thanks,
> Gary

Nothing is wrong with Nexus. There is a 1.1.0 release of this artifact
in the system [0] Nexus auto-purges SNAPSHOT copies of released
artifacts as any further development _must_ end up on a new version
since you can't release new copies of the same version. There is a grace
period of 14 days that a SNAPSHOT version will continue to exist at the
same time that there is a release version. But in this case we're way,
way, way past that window since the release version of this happened in
the middle of November (November 16, 2017 to be specific).

If you end up generating a new SNAPSHOT artifact at a version in this
state it will exist for a very, very short amount of time until the
Nexus artifact reaper comes through which happens once a day.

-Andy-

[0]
https://nexus.onap.org/content/repositories/releases/org/onap/multicloud/openstack/multicloud-openstack-newton/1.1.0/

> 
> From: Morales, Victor [mailto:victor.mora...@intel.com]
> Sent: Monday, January 08, 2018 9:43 AM
> To: Gary Wu ; Yang, Bin (Wind River) 
> ; Guo, Ruijing ; 
> onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] maven artifacts
> 
> Hey Gary,
> 
> We’re still having issues to deploy the 1.1.0-SNAPSHOT version for 
> multicloud-openstack-newton artifact [1].  The –merge-java job looks like was 
> successfully executed [2] when the version was bumped [3] but there is no 
> artifact placed for that specific version, as consequence other jobs are 
> failing [4].  I’m not sure if the deployment process needs to be done 
> separately (per subproject) [5] given that the parent pom.xml contains the 
> reference of every subproject[6]
> 
> Regards/Saludos
> Victor Morales
> 
> [1] 
> https://nexus.onap.org/content/repositories/snapshots/org/onap/multicloud/openstack/multicloud-openstack-newton/
> [2] 
> https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/multicloud-openstack-master-newton-merge-java/55/console.log.gz
> [3] https://gerrit.onap.org/r/#/c/24617/
> [4] 
> https://jenkins.onap.org/job/multicloud-openstack-master-ocata-verify-java/65/
> [5] 
> https://git.onap.org/ci-management/tree/jjb/multicloud/multicloud-openstack.yaml
> [6] https://git.onap.org/multicloud/openstack/tree/pom.xml#n37
> 
> From: 
> >
>  on behalf of Gary Wu >
> Date: Thursday, December 21, 2017 at 9:58 AM
> To: "Yang, Bin (Wind River)" 
> >, "Guo, Ruijing" 
> >, 
> "onap-discuss@lists.onap.org" 
> >
> Subject: Re: [onap-discuss] maven artifacts
> 
> I’m not sure why it didn’t work before, but I just re-ran that job and now 
> the artifact is there.
> 
> Thanks,
> Gary
> 
> From: Yang, Bin [mailto:bin.y...@windriver.com]
> Sent: Wednesday, December 20, 2017 6:51 PM
> To: Gary Wu >; GUO, RUIJING 
> >; 
> onap-discuss@lists.onap.org
> Subject: RE: [onap-discuss] maven artifacts
> 
> Hi Gary,
> 
>The -merge-java job seems working well, but the snaphot 
> artifacts is nowhere to find on nexus.onap.org. Could you help look into this 
> log to find out any clue ?
> 
> https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-newton-merge-java/lastBuild/console
> 
> Thanks.
> 
> Best Regards,
> Bin Yang,Solution Readiness Team,Wind River
> Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
> Skype: yangbincs993
> 
> From: Gary Wu [mailto:gary.i...@huawei.com]
> Sent: Wednesday, December 20, 2017 3:40 PM
> To: GUO, RUIJING; 
> onap-discuss@lists.onap.org
> Cc: Yang, Bin
> 

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

2018-01-09 Thread FREEMAN, BRIAN D
You need to name one RegionTwo or something,

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët
Sent: Tuesday, January 09, 2018 9:34 AM
To: onap-discuss 
Subject: [onap-discuss] [AAI][SO] How to add another LCP Region

Hello AAI, SO expert,

I’m trying to add another LCP Region to be able to deploy VNF in another 
OpenStack instance.

To do so, I have done the following:

In MSO:
- Add a Cloud Site

"RegionAlex":
{
  "region_id": "RegionOne",
  "clli": "RegionOne",
  "aic_version": "2.5",
  "identity_service_id": "ALEX_KEYSTONE"
}

- Add it’s associated Cloud Identity Services

   "ALEX_KEYSTONE":
{
  "identity_url": 
"http://10.195.194.215:5000/v2.0",
  "mso_id": "nso",
  "mso_pass": "86b74198e8ccb959eaaadefevsd2a8a2",
  "admin_tenant": "service",
  "member_role": "admin",
  "tenant_metadata": true,
  "identity_server_type": "KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD"
}

In AAI:
- Create a cloud region

{
"cloud-owner": "CloudOwner",
"cloud-region-id": "RegionAlex",
"cloud-type": "SharedNode",
"owner-defined-type": "OwnerType",
"cloud-region-version": "v1",
"cloud-zone": "CloudZone",
"sriov-automation": false,
"resource-version": "1515506147118",
"relationship-list": {
"relationship": [
{
"related-to": "complex",
"related-link": 
"/aai/v11/cloud-infrastructure/complexes/complex/clli1",
"relationship-data": [
{
"relationship-key": 
"complex.physical-location-id",
"relationship-value": "clli1"
}
]
}
]
}
}


- Create the tenant in the region for the 4 different services with the right 
tenant id:

{
"tenant-id": "21ca0f4c2239475fbf1b4b499399163e",
"tenant-name": "nso-rancher",
"relationship-list": {
"relationship": [
{
"related-to": "service-subscription",
"related-link": 
"/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vLB",
"relationship-data": [
{
"relationship-key": "customer.global-customer-id",
"relationship-value": "Demonstration"
},
{
"relationship-key": "service-subscription.service-type",
"relationship-value": "vLB"
}
]
},
{
"related-to": "service-subscription",
"related-link": 
"/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vIMS",
"relationship-data": [
{
"relationship-key": "customer.global-customer-id",
"relationship-value": "Demonstration"
},
{
"relationship-key": "service-subscription.service-type",
"relationship-value": "vIMS"
}
]
},
{
"related-to": "service-subscription",
"related-link": 
"/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFWCL",
"relationship-data": [
{
"relationship-key": "customer.global-customer-id",
"relationship-value": "Demonstration"
},
{
"relationship-key": "service-subscription.service-type",
"relationship-value": "vFWCL"
}
]
},
{
"related-to": "service-subscription",
"related-link": 
"/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vCPE",
"relationship-data": [
{
"relationship-key": "customer.global-customer-id",
"relationship-value": "Demonstration"
},
{
"relationship-key": 

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

2018-01-09 Thread Alexis de Talhouët
Hello AAI, SO expert,

I’m trying to add another LCP Region to be able to deploy VNF in another 
OpenStack instance.

To do so, I have done the following:

In MSO:
- Add a Cloud Site

"RegionAlex":
{
  "region_id": "RegionOne",
  "clli": "RegionOne",
  "aic_version": "2.5",
  "identity_service_id": "ALEX_KEYSTONE"
}

- Add it’s associated Cloud Identity Services

   "ALEX_KEYSTONE":
{
  "identity_url": "http://10.195.194.215:5000/v2.0;,
  "mso_id": "nso",
  "mso_pass": "86b74198e8ccb959eaaadefevsd2a8a2",
  "admin_tenant": "service",
  "member_role": "admin",
  "tenant_metadata": true,
  "identity_server_type": "KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD"
}

In AAI:
- Create a cloud region

{
"cloud-owner": "CloudOwner",
"cloud-region-id": "RegionAlex",
"cloud-type": "SharedNode",
"owner-defined-type": "OwnerType",
"cloud-region-version": "v1",
"cloud-zone": "CloudZone",
"sriov-automation": false,
"resource-version": "1515506147118",
"relationship-list": {
"relationship": [
{
"related-to": "complex",
"related-link": 
"/aai/v11/cloud-infrastructure/complexes/complex/clli1",
"relationship-data": [
{
"relationship-key": 
"complex.physical-location-id",
"relationship-value": "clli1"
}
]
}
]
}
}


- Create the tenant in the region for the 4 different services with the right 
tenant id:

{
"tenant-id": "21ca0f4c2239475fbf1b4b499399163e",
"tenant-name": "nso-rancher",
"relationship-list": {
"relationship": [
{
"related-to": "service-subscription",
"related-link": 
"/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vLB",
"relationship-data": [
{
"relationship-key": "customer.global-customer-id",
"relationship-value": "Demonstration"
},
{
"relationship-key": "service-subscription.service-type",
"relationship-value": "vLB"
}
]
},
{
"related-to": "service-subscription",
"related-link": 
"/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vIMS",
"relationship-data": [
{
"relationship-key": "customer.global-customer-id",
"relationship-value": "Demonstration"
},
{
"relationship-key": "service-subscription.service-type",
"relationship-value": "vIMS"
}
]
},
{
"related-to": "service-subscription",
"related-link": 
"/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vFWCL",
"relationship-data": [
{
"relationship-key": "customer.global-customer-id",
"relationship-value": "Demonstration"
},
{
"relationship-key": "service-subscription.service-type",
"relationship-value": "vFWCL"
}
]
},
{
"related-to": "service-subscription",
"related-link": 
"/aai/v11/business/customers/customer/Demonstration/service-subscriptions/service-subscription/vCPE",
"relationship-data": [
{
"relationship-key": "customer.global-customer-id",
"relationship-value": "Demonstration"
},
{
"relationship-key": "service-subscription.service-type",
"relationship-value": "vCPE"
}
]
}
]
}
}

So my expectation is to have VID displaying the two LCP Region so I can pick 
the one where I want to deploy.

The thing is, VID is showing only one “RegionOne” option. But in the console I 
can see it’s retrieving two.

cloudRegionTenantList=  creationService.js:909:3
[
{
"cloudRegionId": "",
"tenantName": "Please choose a region",
"tenantId": ""
},
{

Re: [onap-discuss] maven artifacts

2018-01-09 Thread Gary Wu
I’m not sure why the 1.1.0-SNAPSHOT versions disappeared again.  I wonder if 
something is wrong with Nexus.

Helpdesk, can you help?  1.1.0-SNAPSHOT used to exist here, but it has since 
disappeared: 
https://nexus.onap.org/content/repositories/snapshots/org/onap/multicloud/openstack/multicloud-openstack-newton/

Also, there are occasions where the merge job seems to have created 
1.1.0-SNAPSHOT but then it’s nowhere to be found:
https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-newton-merge-java/57/console

Thanks,
Gary

From: Morales, Victor [mailto:victor.mora...@intel.com]
Sent: Monday, January 08, 2018 9:43 AM
To: Gary Wu ; Yang, Bin (Wind River) 
; Guo, Ruijing ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] maven artifacts

Hey Gary,

We’re still having issues to deploy the 1.1.0-SNAPSHOT version for 
multicloud-openstack-newton artifact [1].  The –merge-java job looks like was 
successfully executed [2] when the version was bumped [3] but there is no 
artifact placed for that specific version, as consequence other jobs are 
failing [4].  I’m not sure if the deployment process needs to be done 
separately (per subproject) [5] given that the parent pom.xml contains the 
reference of every subproject[6]

Regards/Saludos
Victor Morales

[1] 
https://nexus.onap.org/content/repositories/snapshots/org/onap/multicloud/openstack/multicloud-openstack-newton/
[2] 
https://logs.onap.org/production/vex-yul-ecomp-jenkins-1/multicloud-openstack-master-newton-merge-java/55/console.log.gz
[3] https://gerrit.onap.org/r/#/c/24617/
[4] 
https://jenkins.onap.org/job/multicloud-openstack-master-ocata-verify-java/65/
[5] 
https://git.onap.org/ci-management/tree/jjb/multicloud/multicloud-openstack.yaml
[6] https://git.onap.org/multicloud/openstack/tree/pom.xml#n37

From: 
>
 on behalf of Gary Wu >
Date: Thursday, December 21, 2017 at 9:58 AM
To: "Yang, Bin (Wind River)" 
>, "Guo, Ruijing" 
>, 
"onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-discuss] maven artifacts

I’m not sure why it didn’t work before, but I just re-ran that job and now the 
artifact is there.

Thanks,
Gary

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Wednesday, December 20, 2017 6:51 PM
To: Gary Wu >; GUO, RUIJING 
>; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] maven artifacts

Hi Gary,

   The -merge-java job seems working well, but the snaphot 
artifacts is nowhere to find on nexus.onap.org. Could you help look into this 
log to find out any clue ?

https://jenkins.onap.org/view/multicloud/job/multicloud-openstack-master-newton-merge-java/lastBuild/console

Thanks.

Best Regards,
Bin Yang,Solution Readiness Team,Wind River
Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
Skype: yangbincs993

From: Gary Wu [mailto:gary.i...@huawei.com]
Sent: Wednesday, December 20, 2017 3:40 PM
To: GUO, RUIJING; 
onap-discuss@lists.onap.org
Cc: Yang, Bin
Subject: RE: [onap-discuss] maven artifacts

Hi Ruijing,

SNAPSHOT artifacts are deployed to nexus by Jenkins using the -merge-java jobs 
that you define.

Thanks,
Gary

From: Guo, Ruijing [mailto:ruijing@intel.com]
Sent: Tuesday, December 19, 2017 11:23 PM
To: onap-discuss@lists.onap.org
Cc: Yang, Bin (Wind River) 
>; Gary Wu 
>
Subject: [onap-discuss] maven artifacts

Hi,

Who can deploy maven artifacts to nexus.onap.org? Integration team?

multicloud-openstack-newton: 1.0.0-SNAPSHOT

https://nexus.onap.org/content/repositories/snapshots/org/onap/multicloud/openstack/multicloud-openstack-newton/1.0.0-SNAPSHOT/

I expect multicloud-openstack-newton: 1.1.0-SNAPSHOT is deployed in nexus.

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


Re: [onap-discuss] ONAP on Vanilla OpenStack

2018-01-09 Thread PLATANIA, MARCO (MARCO)
Harry,

A couple of things. First of all, the env file is not updated. You are using 
the docker released for Amsterdam but the Gerrit master branches, which contain 
work for Beijing release. Please look at the latest one in the Gerrit demo 
repo: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=24b09b92a97a4069289cb7ca94c6884b06f23dd4;hb=refs/heads/amsterdam

Please change sdc_branch to amsterdam. This param hasn’t been updated yet, I’ll 
do it soon.

The other thing is that you need the FQDN of the Portal component, not its IP: 
portal.api.simpledemo.onap.org:8989/ONAPPORTAL/login.htm

Hope this helps!

Marco


From:  on behalf of huangxiangyu 

Date: Monday, January 8, 2018 at 10:47 PM
To: "onap-discuss@lists.onap.org" , 
"onap-...@lists.onap.org" 
Subject: [onap-discuss] ONAP on Vanilla OpenStack

Hi

I have a vanilla openstack environment (with Designate) and I’m using attached 
template to launch ONAP. There are 15 VMs running after onap stack is created. 
However I find 
http://:8989/ONAPPORTAL/login.html
 returns 404. I’ve looked into onap_portal vm and there are four dockers 
running. I think catalina.out inside onap/portal-app has some information which 
contains ERROR below:
ERROR in catalina.out: ERROR in 
ch.qos.logback.core.joran.spi.Interpreter@114:21 - no applicable action for 
[totalSizeCap], current ElementPath  is 
[[configuration][appender][rollingPolicy][totalSizeCa

BTW, I can see tomcat’s welcome page on 
http://:8989.
 Can somebody please tell me where I got wrong or show me how to debug this 
problem ? Any help is appreciated.

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


Re: [onap-discuss] Failure to create the demo vfirewall VNF

2018-01-09 Thread FREEMAN, BRIAN D
You need to look at SO logs for the SdncAdapter and VnfAdapter and see what 
error you are getting from SDNC or Openstack in SO.

Usually a delete implies that SO talks to SDNC correctly but then the 
interaction with Openstack fails or when SO goes to SDNC or AAI for data to 
create the Openstack heat stack create that it is failing.

Brian


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramanarayanan, 
Karthick
Sent: Monday, January 08, 2018 6:33 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Failure to create the demo vfirewall VNF


Hi,

 I am trying to instantiate the demo vfirewall-vsink service instance based on 
the video here:



 
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010290/vFW_closed_loop.mp4#RunningtheONAPDemos-VNFOnboarding,Instantiation,andClosed-loopOperations



 While I am able to move ahead and reach till the vf create step, the add VF 
step

 for both vfirewall and packet gen instance results in failure and moves to 
pending delete.

 (sdnc preload checkbox enabled)



 The setup I have is OOM configured for kubernetes.

 I am on amsterdam release branch for OOM.

So its not using openstack heat templates

 to instantiate ONAP. Rather just a single node configured with k8s oneclick.



 The difference in the video pertains to running demo-k8s.sh init from 
oom/kubernetes/robot

 to instantiate the customer models and services after copying the demo/heat

 to kubernetes robot /share directory for the distribute the work.



 The demo vfirewall closed loop service seems to be distributed as seen in the 
ONAP portal.

 ( I have also tried redistributing)

 I am trying to instantiate the service for demo vFWCL.



 Logs indicate nothing in sdnc after the vF create failure.

 I don't see any requests hitting Openstack logs either.



 The VNF preload operation seems to have succeeded for the firewall closed loop 
instances.

 The VNF profiles are also present in sdnc.



 I get back a http success (status code 200) with the request id as expected.

 A subsequent GET request for vnf topology information preloaded also works.



 Doing a POST using sdnc api (port 8282) works for the vnf topology preload 
step.

 But I see nothing in the logs for sdnc pods. (nothing relevant in sdc/mso pod 
either if that matters)



 Here is a snippet from curl to sdnc as well:



curl -vX POST 
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.43.172.252:8282/restconf/operations/VNF-API:preload-vnf-topology-operation
 -d @firewall.json --header "Content-Type: application/json"



Response status is http 200 as expected.
{
 "output": {
   "svc-request-id": "robot12",
   "response-code": "200",
   "ack-final-indicator": "Y"
 }
}


Trying to do a get request for the vnf topology preload information POST 
request above also returns expected information:


curl -sSL 
http://admin:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U@10.43.172.252:8282/restconf/config/VNF-API:preload-vnfs/vnf-preload-list/vfirewall-1/3d6f8762Fea8453fBd9a..base_vfw..module-0/preload-data/vnf-topology-information/vnf-topology-identifier
 | jq .

{
 "vnf-topology-identifier": {
   "vnf-name": "vfirewall-1",
   "generic-vnf-type": "3d6f8762-fea8-453f-bd9a 0",
   "generic-vnf-name": "firewall-vnf",
   "vnf-type": "3d6f8762Fea8453fBd9a..base_vfw..module-0",
   "service-type": "5b5c134c-662e-407e-bc4c-4200b4b5cb02"
 }
}


I am also attaching the firewall.json POST request for vnf toplogy preload to 
sdnc portal.

The VNF profiles have all been added to sdnc portal for the 2 vfs.



But still VF create request (for both vfirewall sink and packetgen) results in 
failure and moves transaction to pending delete.

No api request traces in Openstack as well and neither do I 

Re: [onap-discuss] [portal]ONAP on Vanilla OpenStack

2018-01-09 Thread Kanagaraj Manickam
Hi Manoop,

It would be very helpful and very easy for users if you could make portal to 
open the login page, just pointing the 
http://> and default to 80.
Kindly help. Thank you.

Regards
Kanagaraj M
-
Be transparent! Win together !!

本邮件及其附件含有华为公司的保密信息,仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用(包括但不限于全部或部分地泄露、复制、或散发)本邮件中的信息。如果您错收了本邮件,请您立即电话或邮件通知发件人并删除本邮件!
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whose address is listed above. 
Any use of the information contained herein in any way (including, but not   
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is  prohibited. If you receive 
this e-mail in error, please notify the sender by phone or email immediately 
and delete it!


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Abhishek Shekhar
Sent: Tuesday, January 09, 2018 1:56 PM
To: huangxiangyu; onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: Re: [onap-discuss] ONAP on Vanilla OpenStack

Hi,

It is login.htm not login.html (HTM not HTML)

Please try using 
http://:8989/ONAPPORTAL/login.htm

Hope it helps.

Thanks
Abhishek Shekhar

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of huangxiangyu
Sent: Tuesday, January 9, 2018 9:18 AM
To: onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: [onap-discuss] ONAP on Vanilla OpenStack

Hi

I have a vanilla openstack environment (with Designate) and I’m using attached 
template to launch ONAP. There are 15 VMs running after onap stack is created. 
However I find 
http://:8989/ONAPPORTAL/login.html
 returns 404. I’ve looked into onap_portal vm and there are four dockers 
running. I think catalina.out inside onap/portal-app has some information which 
contains ERROR below:
ERROR in catalina.out: ERROR in 
ch.qos.logback.core.joran.spi.Interpreter@114:21
 - no applicable action for [totalSizeCap], current ElementPath  is 
[[configuration][appender][rollingPolicy][totalSizeCa

BTW, I can see tomcat’s welcome page on 
http://:8989. Can somebody 
please tell me where I got wrong or show me how to debug this problem ? Any 
help is appreciated.

Thanks and Regards
Harry
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] ONAP on Vanilla OpenStack

2018-01-09 Thread Abhishek Shekhar
Hi,

It is login.htm not login.html (HTM not HTML)

Please try using 
http://:8989/ONAPPORTAL/login.htm

Hope it helps.

Thanks
Abhishek Shekhar

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of huangxiangyu
Sent: Tuesday, January 9, 2018 9:18 AM
To: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: [onap-discuss] ONAP on Vanilla OpenStack

Hi

I have a vanilla openstack environment (with Designate) and I'm using attached 
template to launch ONAP. There are 15 VMs running after onap stack is created. 
However I find 
http://:8989/ONAPPORTAL/login.html
 returns 404. I've looked into onap_portal vm and there are four dockers 
running. I think catalina.out inside onap/portal-app has some information which 
contains ERROR below:
ERROR in catalina.out: ERROR in 
ch.qos.logback.core.joran.spi.Interpreter@114:21
 - no applicable action for [totalSizeCap], current ElementPath  is 
[[configuration][appender][rollingPolicy][totalSizeCa

BTW, I can see tomcat's welcome page on 
http://:8989. Can somebody 
please tell me where I got wrong or show me how to debug this problem ? Any 
help is appreciated.

Thanks and Regards
Harry
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

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