Re: [onap-discuss] [integration]Please help us on Integration Lab

[Gooch, Stephen]

Hello All,

Lab access has been restored.

Br,
-Stephen

From: Michael O'Brien [mailto:frank.obr...@amdocs.com]
Sent: Monday, January 15, 2018 20:56
To: Yunxia Chen; Gooch, Stephen; Raineri, Eddy; Yang, Bin
Cc: onap-discuss
Subject: RE: [integration]Please help us on Integration Lab

Fyi,
   I raised the issue on the VPN 36 hours ago after the Thu retrofit – service 
has been excellent and prompt – I would expect tomorrow we should be good.
   https://jira.onap.org/browse/OPENLABS-153
https://lists.onap.org/pipermail/onap-discuss/2018-January/007390.html

   For now you can consult the CD poc on AWS that is pending migration to the 
LF under (OOM-500) to at least get 
healthcheck hourly for master
http://jenkins.onap.info/job/oom-cd/

http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-7d,mode:quick,to:now))&_a=(description:'',filters:!(),options:(darkTheme:!f),panels:!((col:1,id:AWAts77k3NTXK5mX2kuM,panelIndex:1,row:1,size_x:8,size_y:3,type:visualization),(col:9,id:AWAtuTVI3NTXK5mX2kuP,panelIndex:2,row:1,size_x:4,size_y:3,type:visualization),(col:1,id:AWAtuBTY3NTXK5mX2kuO,panelIndex:3,row:7,size_x:6,size_y:3,type:visualization),(col:1,id:AWAttmqB3NTXK5mX2kuN,panelIndex:4,row:4,size_x:6,size_y:3,type:visualization),(col:7,id:AWAtvHtY3NTXK5mX2kuR,panelIndex:6,row:4,size_x:6,size_y:6,type:visualization)),query:(match_all:()),timeRestore:!f,title:'CD%20Health%20Check',uiState:(),viewMode:view)

Notice that the MSB fix has fixed the 8 failing heathcheck from the 13th – 3 
hours ago
https://gerrit.onap.org/r/#/c/27943/

   thanks Stephen,
   /michael


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yunxia Chen
Sent: Monday, January 15, 2018 10:15
To: Gooch, Stephen 
mailto:stephen.go...@windriver.com>>; Raineri, 
Eddy mailto:eddy.rain...@windriver.com>>; Yang, Bin 
mailto:bin.y...@windriver.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [integration]Please help us on Integration Lab

Thank you Stephen.
Since the team is doing MR testing, if possible, please help to get it up asap.

Regards,

Helen Chen

From: "Gooch, Stephen" 
mailto:stephen.go...@windriver.com>>
Date: Monday, January 15, 2018 at 7:10 AM
To: Helen Chen 00725961 mailto:helen.c...@huawei.com>>, 
"Raineri, Eddy" 
mailto:eddy.rain...@windriver.com>>, "Yang, Bin" 
mailto:bin.y...@windriver.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: RE: [integration]Please help us on Integration Lab

Hi Helen,

The issue is in the building, external to the ONAP lab.   See attached.

Br,
- Stephen

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Monday, January 15, 2018 16:08
To: Gooch, Stephen; Raineri, Eddy; Yang, Bin
Cc: onap-discuss
Subject: [integration]Please help us on Integration Lab

Hi, Stephen, Eddy & Bin,

We cannot access Integration lab this morning, could you please help take a 
look?

Regards,
Helen Chen


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

[onap-discuss] Reg. vDNS registration and policies

[ESWAR RAO]

Hi All,

I have setup ONAP Amsterdam release and registered a VIM (ocata version
openstack) through AAI.


Now I wanted to see how I can do vDNS and achieve CLAMP.

I was following:

https://github.com/mikalstill/onap-demos

https://wiki.onap.org/display/DW/vFWCL+instantiation,+testing,+and+debuging

Can some one please provide pointers of how I can perform instantiation
from E2E.

Anywhere I can get some pointers where* Policies are defined for vDNS *just
like in below:

http://onap.readthedocs.io/en/latest/submodules/vnfsdk/model.git/docs/files/VNF%20SDK%20blueprints.html



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

Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL

[Yang, Bin]

Hi Brian,

Have you been able to get policy issue fixed?  I observed the same issue, and 
the branches are correct for my ONAP template file. Does anyone could help on 
this issue? Thanks.
   policy_repohttp://gerrit.onap.org/r/policy/docker.git
   policy_dockerv1.1.2
policy_branchamsterdam
policy_repohttp://gerrit.onap.org/r/policy/docker.git


$ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh 
policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 
./onap_dev.pem


Removing the vFW Policy from PDP..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> DELETE /pdp/api/deletePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 133
>
* upload completely sent off: 133 out of 133 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 91
< Date: Tue, 16 Jan 2018 09:32:08 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 310812b5-858f-4ee7-82a7-0b6723466a19 --The policy was 
successfully deleted.


Updating vFW Operational Policy ..

*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/updatePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 1309
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 149
< Date: Tue, 16 Jan 2018 09:32:29 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 8ea2a93d-9e9a-4d30-b944-c6d169cc2eb5 --Policy with the name 
com.Config_BRMS_Param_BRMSParamvFirewall.2.xml was successfully updated.

Pushing the vFW Policy ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/pushPolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 99
>
* upload completely sent off: 99 out of 99 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 162
< Date: Tue, 16 Jan 2018 09:32:35 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 9ad6377c-6a4c-4a8c-870f-df9fa69a5003 --Policy 
'com.Config_BRMS_Param_BRMSParamvFirewall.2.xml' was successfully pushed to the 
PDP group 'default'.

Restarting PDP-D ..


The authenticity of host 'policy.api.simpledemo.onap.org (10.12.9.121)' can't 
be established.
ECDSA key fingerprint is SHA256:PzUojk3RJNW5LsjcrMA80lyIV3opeekfg7fbbOqsqE8.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'policy.api.simpledemo.onap.org,10.12.9.121' (ECDSA) 
to the list of known hosts.
[drools-pdp-controllers]
L []: Stopping Policy Management... Policy Management (pid=5503) is stopping... 
Policy Management has stopped.
[drools-pdp-controllers]
L []: Policy Management (pid 5762) is running


PDP-D amsterdam maven coordinates ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 9696 (#0)
* Server auth using Basic with user '@1b3rt'
> GET /policy/pdp/engine/controllers/amsterdam/drools HTTP/1.1
> Host: policy.api.simpledemo.onap.org:9696
> Authorization: Basic QDFiM3J0OjMxbnN0MzFu
> User-Agent: curl/7.50.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Tue, 16 Jan 2018 09:33:44 GMT
< Content-Type: application/json
< Content-Length: 31
< Server: Jetty(9.3.14.v20161028)
<
{ [31 bytes data]
* Connection #0 to host policy.api.simpledemo.onap.org left intact
{
"error": "amsterdam not found"
}


PDP-D control loop updated ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 9696 (#0)
* Server auth using Basic with user '@1b3rt'
> GET 
> /policy/pdp/engine/controllers/amsterdam/drools/facts/closedloop-amsterdam/org.onap.policy.controlloop.Params
>  HTTP/1.1
> Host: policy.api.simpledemo.onap.org:9696
> Authorization: Basic QDFiM3J0OjMxbnN0MzFu
> User-Agent: curl/7.50.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Tue, 16 Jan 2018 09:33:44 GMT
< Content-Type: application/json
< Content-Length: 87
< Server: Jetty(9.3.14.v20161028)
<
{ [87 bytes data]
* Connection #0 to host policy.api.simpledemo.onap.org left intact
{
"error": "amsterdam:closedloop-amsterdam:org.o

Re: [onap-discuss] [SDC] ASDC reports status 500 for health check

[ESWAR RAO]

After using docker_version as 1.1-STAGING-latest instead of 1.1.0, the
health of SDC was fine.

Thanks
Eswar



On Tue, Jan 16, 2018 at 10:38 AM, ESWAR RAO  wrote:

>
> Hi All,
>
> Can you please help me in resolving below:
>
>
> I executed robot test case to verify sanity out of which 2 components are
> failing.
>
> root@onap-robot:/home/ubuntu# docker exec -it openecompete_container
> /var/opt/OpenECOMP_ETE/runTags.sh -i health h -d ./html
> -V /share/config/integration_robot_properties.py  -V
> /share/config/integration_preload_parameters.py -V
> /share/config/vm_properties.py
>
> *Basic DCAE Health Chec*k   |
> *FAIL *|
> [  | cdap |  |  |  |  | cdap_broker | config_binding_service |
> deployment_handler | inventory | 
> a35a7b6a9379424386475302c113c3d5_cdap_app_cdap_app_tca
> | platform_doc
> kerhost |  | b982f9652d8c4f3d95dd806b20f31909_dcaegen2-collectors-ves |
> component_dockerhost |
> | cloudify_manager ] does not contain match for pattern
> 'service-change-handler'.
>
> *Basic ASDC Health Check*   |
> *FAIL *|
> 500 != 200
>
> 
> 
> ###
>
> root@onap-sdc:/opt# docker images
> REPOSITORY  TAG
>  IMAGE IDCREATED SIZE
> nexus3.onap.org:10001/openecomp/sdc-cassandra   v1.1.0
> 119363b4876b2 months ago874MB
> nexus3.onap.org:10001/openecomp/sdc-kibana  v1.1.0
> 5a60bc32b5412 months ago487MB
> nexus3.onap.org:10001/openecomp/sdc-elasticsearch   v1.1.0
> 9c94734127942 months ago541MB
> nexus3.onap.org:10001/openecomp/sdc-frontendv1.1.0
> 72064d647e902 months ago824MB
> nexus3.onap.org:10001/openecomp/sdc-backend v1.1.0
> bd2289ba829d2 months ago1.39GB
>
> root@onap-sdc:/opt# docker ps
> CONTAINER IDIMAGE
> COMMAND  CREATED STATUS  PORTS
>NAMES
> cc42b59a1da1nexus3.onap.org:10001/openecomp/sdc-frontend:v1.1.0
>   "/root/startup.sh"   4 days ago  Up 4 days
>  0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp
>   sdc-FE
> 69634c4c666bnexus3.onap.org:10001/openecomp/sdc-backend:v1.1.0
>  "/root/startup.sh"   4 days ago  Up 4 days
>  0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcp
>   sdc-BE
> 2827bb3ad057nexus3.onap.org:10001/openecomp/sdc-kibana:v1.1.0
>   "/root/startup.sh"   4 days ago  Up 4 days
>  0.0.0.0:5601->5601/tcp
>   sdc-kbn
> f0792a125861nexus3.onap.org:10001/openecomp/sdc-cassandra:v1.1.0
>  "/root/startup.sh"   4 days ago  Up 4 days
>  7000-7001/tcp, 0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp
>  sdc-cs
> 5e4e73a7fdccnexus3.onap.org:10001/openecomp/sdc-elasticsearch:
> v1.1.0   "/root/startup.sh"   4 days ago  Up 4 days
>  0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp
>   sdc-es
> root@onap-sdc:/opt#
>
> root@onap-sdc:/opt# curl http://10.0.3.1:8181/sdc1/rest/healthCheck
> {
>   "sdcVersion": "UNKNOWN",
>   "siteMode": "UNKNOWN",
>   "componentsInfo": [
> {
>   "healthCheckComponent": "FE",
>   "healthCheckStatus": "UP",
>   "version": "1.1.0",
>   "description": "OK"
> },
> {
>   "healthCheckComponent": "BE",
>   "healthCheckStatus": "DOWN"
> },
> {
>   "healthCheckComponent": "TITAN",
>   "healthCheckStatus": "UNKNOWN"
> },
> {
>   "healthCheckComponent": "CASSANDRA",
>   "healthCheckStatus": "UNKNOWN"
> },
> {
>   "healthCheckComponent": "DE",
>   "healthCheckStatus": "UNKNOWN"
> },
> {
>   "healthCheckComponent": "ON_BOARDING",
>   "healthCheckStatus": "UNKNOWN"
> }
>   ]
> }root@onap-sdc:/opt#
>
> 
> 
> ###
>
>
> Thanks
> Eswar Rao
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Promote Liang ke to Committer of Multi VIM/Cloud

[Xinhui Li]

Hi Jessica,

TSC have approved Liang ke as a committer of Multi VIM/Cloud. Please help to 
promote him or let me know I need submit some ticket for this.

Please refer to this link for more info: 
https://wiki.onap.org/pages/viewpage.action?pageId=22249517

Thanks,

Xinhui Li
PTL of Multi VIM/Cloud
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [multicloud] synergy between APPC and Multi-cloud in R2

[Xinhui Li]

Hi Randa,

In R2 Release, Multi VIM/Cloud targets to support event/notification federation 
between external Clouds and ONAP. This will bring obvious benefits to S3p 
improvement, e.g. instead of looped polling to know if VM is properly 
powered-off, a corresponding event will be thrown to DMAAP and help to achieve 
an efficient closed loop with existing use cases.  It will be nice if we can 
have some sync up meeting to discuss about this.

Xinhui Li
PTL of Multi VIM/Cloud
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [DCAE] [Holmes] Problem with holmes-rules docker

[ESWAR RAO]

Hi All,


I was able to install ONAP amsterdam release.

But when I run robot test-cases DCAE is failing for holmes-rules docker.

==
OpenECOMP ETE.Robot.Testsuites.Health-Check :: Testing ecomp components
are...
==
Basic DCAE Health Check   |
FAIL |
[  | cdap |  |  |  |  | cdap_broker | config_binding_service |
deployment_handler | inventory | service-change-handler |
a35a7b6a9379424386475302c113c3d5_cdap_app_cdap_app_tca |
platform_dockerhost |  |
b982f9652d8c4f3d95dd806b20f31909_dcaegen2-collectors-ves |
component_dockerhost |
| cloudify_manager ] does not contain match for pattern
'regexp=.*dcae-analytics-holmes-rule-management'

root@dcaedoks00:/home/ubuntu# docker ps
CONTAINER IDIMAGE
   COMMAND  CREATED
 STATUS  PORTSNAMES
608c1b8dc822nexus3.onap.org:10001/onap/holmes/rule-management:v1.0.0
"/bin/sh -c /home/..."   15 minutes ago  Up 15
minutes   0.0.0.0:9101->9101/tcp
*cf95931412c3489c875e81fc36001804_dcae-analytics-holmes-rule-management*

9a70288c1b4f
nexus3.onap.org:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector:v1.1.0
 "/opt/app/docker-e..."   22 hours agoUp 22 hours
 0.0.0.0:8080->8080/tcp
 b982f9652d8c4f3d95dd806b20f31909_dcaegen2-collectors-ves
04d026c06920onapdcae/registrator:v7
   "/bin/sh -c '/bin/..."   29 hours agoUp
29 hours  registrator
root@dcaedoks00:/home/ubuntu#
root@dcaedoks00:/home/ubuntu#

root@dcaedoks00:/home/ubuntu# docker exec 608c1b8dc822 env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/lib/jvm/java-8-openjdk-amd64/jre/bin:/usr/lib/jvm/java-8-openjdk-amd64/bin
HOSTNAME=cf95931412c3489c875e81fc36001804_dcae-analytics-holmes-rule-management
SERVICE_CHECK_HTTP=/api/holmes-rule-mgmt/v1/healthcheck
CONSUL_HOST=192.168.21.224
SERVICE_NAME=cf95931412c3489c875e81fc36001804_dcae-analytics-holmes-rule-management
CONFIG_BINDING_SERVICE=config_binding_service
MSB_ADDR=10.0.14.1
URL_JDBC=dcae-pgvm-write.fKHc.dcaeg2.onap.org
JDBC_USERNAME=holmes_admin
SERVICE_TAGS=hrules
SERVICE_CHECK_TIMEOUT=1s
SERVICE_CHECK_INTERVAL=15s
JDBC_PASSWORD=19e471deae0168dff1d1bfee3a726062
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64
CLASSPATH=.:/usr/lib/jvm/java-8-openjdk-amd64/lib:/lib
JRE_HOME=/usr/lib/jvm/java-8-openjdk-amd64/jre
HOME=/root
root@dcaedoks00:/home/ubuntu#


root@dcaedoks00:/home/ubuntu# docker logs 608c1b8dc822

2018-01-16 12:08:56 692 INFO
[org.onap.holmes.common.config.MicroServiceConfig][pool-1-thread-1] - The
config_binding_service address is http://192.168.21.228:1
2018-01-16 12:08:56 698 WARN
[org.eclipse.jetty.util.component.AbstractLifeCycle][main] - FAILED
io.dropwizard.db.ManagedPooledDataSource@3f9270ed{ConnectionPool[defaultAutoCommit=null;
defaultReadOnly=null; defaultTransactionIsolation=-1; defaultCatalog=null;
driverClassName=org.postgresql.Driver; maxActive=100; maxIdle=100;
minIdle=8; initialSize=10; maxWait=1000; testOnBorrow=false;
testOnReturn=false; timeBetweenEvictionRunsMillis=1;
numTestsPerEvictionRun=0; minEvictableIdleTimeMillis=1000;
testWhileIdle=false; testOnConnect=true; password=;
url=jdbc:postgresql://dcae-pgvm-write.fKHc.dcaeg2.onap.org/holmes;
username=holmes_admin; validationQuery=/* MyService Health Check */ SELECT
1; validationQueryTimeout=-1; validatorClassName=null;
validationInterval=3; accessToUnderlyingConnectionAllowed=true;
removeAbandoned=false; removeAbandonedTimeout=60; logAbandoned=false;
connectionProperties=null; initSQL=null; jdbcInterceptors=null;
jmxEnabled=true; fairQueue=true; useEquals=true;
abandonWhenPercentageFull=0; maxAge=0; useLock=false; dataSource=null;
dataSourceJNDI=null; suspectTimeout=0; alternateUsernameAllowed=false;
commitOnReturn=false; rollbackOnReturn=false;
useDisposableConnectionFacade=true; logValidationErrors=false;
propagateInterruptState=false; ignoreExceptionOnPreLoad=false; }:
org.postgresql.util.PSQLException: The connection attempt failed.
org.postgresql.util.PSQLException: The connection attempt failed.


Can you please let me know where does the
dcae-analytics-holmes-rule-management try to connect ??

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

Re: [onap-discuss] [DCAE] problems with dcae bootstrap VM

[ESWAR RAO]

Thanks Lusheng.

After going through jira bugs and changing docker image version of SDC
containers, I was able to succeed

--
Basic ASDC Health Check   |
PASS |
--

Thanks
Eswar Rao



On Tue, Jan 16, 2018 at 6:34 AM, JI, LUSHENG (LUSHENG)  wrote:

> Eswar,
>
> Good to hear the progress you have made.
>
> Service Change Handler has dependency on (A)SDC because it is expecting
> the latter to distribute close loop models.  So if SDC is not healthy,
> Service Change Handler will bail.
>
> For debugging (A)SDC, you may want to check with the SDC team.  You might
> want to start with looking into SDC's docker log just like how you checked
> the DCAE boot container.
>
>
> Lusheng
>
> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
>
>
>  Original message 
> From: ESWAR RAO 
> Date: 1/15/18 7:47 PM (GMT-05:00)
> To: Josef Reisinger 
> Cc: "JI, LUSHENG (LUSHENG)" ,
> onap-discuss@lists.onap.org, onap-discuss-boun...@lists.onap.org
> Subject: Re: [onap-discuss] [DCAE] problems with dcae bootstrap VM
>
> Hi Josef and Lusheng,
>
> Thanks for the response.
>
> I made the boot container to run without exiting and i deleted all
> deployments/cancelledexecutions individually and installed them manually
> using the install script.
>
> All 29 VM's are UP.
>
> While installation of deployment "PlatformServicesInventory" I faced
> problem with "service-change-handler" start.
>
> I executed robot test case to verify sanity out of which 2 components are
> failing.
>
> root@onap-robot:/home/ubuntu# docker exec -it openecompete_container
> /var/opt/OpenECOMP_ETE/runTags.sh -i health h -d ./html
> -V /share/config/integration_robot_properties.py  -V
> /share/config/integration_preload_parameters.py -V
> /share/config/vm_properties.py
>
> *Basic DCAE Health Chec*k   | 
> *FAIL
> *|
> [  | cdap |  |  |  |  | cdap_broker | config_binding_service |
> deployment_handler | inventory | 
> a35a7b6a9379424386475302c113c3d5_cdap_app_cdap_app_tca
> | platform_doc
> kerhost |  | b982f9652d8c4f3d95dd806b20f31909_dcaegen2-collectors-ves |
> component_dockerhost |
> | cloudify_manager ] does not contain match for pattern
> 'service-change-handler'.
>
> *Basic ASDC Health Check*   | 
> *FAIL
> *|
> 500 != 200
>
>
> (1) Please let me know where I can debug for Basic ASDC Health Check
> failure ??
>
> (2) Please help to start 'service-change-handler' docker.
>
>  # cfy install -p ./blueprints/inv/inventory.yaml -b
> PlatformServicesInventory -d PlatformServicesInventory
>  -i "location_id=fKHc" -i ./config/invinputs.yaml  -vv
>
> 2018-01-15T10:36:44 CFY 
> [inventory_ec24a.start] Task succeeded 'dockerplugin.create_and_
> start_container_for_platforms'
> 2018-01-15T10:36:45 CFY 
> [service-change-handler_8060a] Creating node
> 2018-01-15T10:41:50 CFY 
> [service-change-handler_8060a.start] Task failed 
> 'dockerplugin.create_and_start_container_for_platforms'
> -> Container never became healthy
> Traceback (most recent call last):
>   File "/tmp/pip-build-P7Jcnx/cloudify-plugins-common/cloudify/dispatch.py",
> line 596, in main
>   File "/tmp/pip-build-P7Jcnx/cloudify-plugins-common/cloudify/dispatch.py",
> line 366, in handle
>   File "/opt/mgmtworker/env/plugins/dockerplugin-2.4.0/lib/
> python2.7/site-packages/dockerplugin/decorators.py", line 57, in wrapper
> raise NonRecoverableError(e)
> NonRecoverableError: Container never became healthy
>
> 2018-01-15T10:41:51 CFY  'install' workflow
> execution failed: RuntimeError: Workflow failed: Task failed
> 'dockerplugin.create_and_start_container_for_platforms' -> Container
> never became healthy
>
> *Image is downloaded to dokp ; but process is not running*
>
> ubuntu@dcaedokp00:~$ sudo docker images
> REPOSITORY
> TAG IMAGE IDCREATED SIZE
> nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.configbinding
> 
>  v1.2.0  001c94f2d7992 months ago714 MB
> nexus3.onap.org:10001/onap/org.onap.dcaegen2.platform.inventory-api
> 
>  v1.2.0  7237fbbd35cb2 months ago557 MB
> *nexus3.onap.org:1000

[onap-discuss] [policy] Thank you to Ericsson!!

[DRAGOSH, PAMELA L (PAM)]

And particular Liam Fallon for help in pulling the policy/drools-applications 
repo back into Green status.

We are already <1% away from meeting Beijing code coverage requirements for 
that repository!!

Pam Dragosh
ONAP Policy PTL
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] - restart pod behavoir with SDNC data

[Alexis de Talhouët]

Hi Brian,

Resiliency is part of this epic: OOM-346  
and it has not being done yet.

I tend to think ODL data is not being persisted in the SDNC-163 
 so we will have to address this, 
whether it’s for master or amsterdam.
Also, I’m not sure we should persist to whole ODL deployment 
(/opt/opendaylight/current), but instead have a mechanism that creates 
regularly snapshots and backup those upon restart (like 
cluster-admin:backup-datastore 

 or daexim 
, 
that I’m sure you already know)

Alexis

> On Jan 15, 2018, at 5:46 PM, FREEMAN, BRIAN D  wrote:
> 
> Michael, Alexis,
>  
> I did a test where I created an OOM environment, sent preload into SDNC and 
> then deleted the SDNC Pod.
> K8 restarted the POD but the data saved to SDNC wasnt there.
> This was Amsterdam.
>  
> Do we need to have the /opt/opendaylight/current/ directory persisted (or 
> current/journal) ?
>  
> I think the clustering team may have addressed this as well but cold recovery 
> of an SDNC cluster created by OOM requires something stored on the hard disk.
>  
> Brian
>  
> ___
> 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] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL

[DRAGOSH, PAMELA L (PAM)]

Bin,

Sorry I missed this the other day. Let’s have our team take a look as it looks 
like the Drools PDP is missing the Amsterdam controller. That should never have 
been deleted.

Which lab are you in? If you can give access to Jorge, he can take a quick look.

Regards,

Pam

From:  on behalf of "Yang, Bin" 

Date: Tuesday, January 16, 2018 at 4:50 AM
To: "Matt, Brian" , "onap-discuss@lists.onap.org" 

Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Brian,

Have you been able to get policy issue fixed?  I observed the same issue, and 
the branches are correct for my ONAP template file. Does anyone could help on 
this issue? Thanks.
   policy_repo
http://gerrit.onap.org/r/policy/docker.git
   policy_dockerv1.1.2
policy_branchamsterdam
policy_repo
http://gerrit.onap.org/r/policy/docker.git


$ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh 
policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 
./onap_dev.pem


Removing the vFW Policy from PDP..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> DELETE /pdp/api/deletePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 133
>
* upload completely sent off: 133 out of 133 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 91
< Date: Tue, 16 Jan 2018 09:32:08 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 310812b5-858f-4ee7-82a7-0b6723466a19 --The policy was 
successfully deleted.


Updating vFW Operational Policy ..

*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/updatePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 1309
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 149
< Date: Tue, 16 Jan 2018 09:32:29 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 8ea2a93d-9e9a-4d30-b944-c6d169cc2eb5 --Policy with the name 
com.Config_BRMS_Param_BRMSParamvFirewall.2.xml was successfully updated.

Pushing the vFW Policy ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/pushPolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 99
>
* upload completely sent off: 99 out of 99 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 162
< Date: Tue, 16 Jan 2018 09:32:35 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 9ad6377c-6a4c-4a8c-870f-df9fa69a5003 --Policy 
'com.Config_BRMS_Param_BRMSParamvFirewall.2.xml' was successfully pushed to the 
PDP group 'default'.

Restarting PDP-D ..


The authenticity of host 'policy.api.simpledemo.onap.org (10.12.9.121)' can't 
be established.
ECDSA key fingerprint is SHA256:PzUojk3RJNW5LsjcrMA80lyIV3opeekfg7fbbOqsqE8.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'policy.api.simpledemo.onap.org,10.12.9.121' (ECDSA) 
to the list of known hosts.
[drools-pdp-controllers]
L []: Stopping Policy Management... Policy Management (pid=5503) is stopping... 
Policy Management has stopped.
[drools-pdp-controllers]
L []: Policy Management (pid 5762) is running


PDP-D amsterdam maven coordinates ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 9696 (#0)
* Server auth using Basic with user '@1b3rt'
> GET /policy/pdp/engine/controllers/amsterdam/drools HTTP/1.1
> Host: policy.api.simpledemo.onap.org:9696
> Authorization: Basic QDFiM3J0OjMxbnN0MzFu
> User-Agent: curl/7

Re: [onap-discuss] [SO][SDC]Distribution Client Register Failed.

[Alexis de Talhouët]

Hi,

How do you know it’s picking the asdc-contoller1 config to connect?
What I’ve noticed is SO comes with two pre-configured asdc-controllers, but the 
thing is, one is a dummy one (asdc-controller2), but the asdc code in SO will 
try to establish the connection to all the controllers provided in the 
asdc-connections list, hence the issue you’re facing. You probably are seeing 
the logs of the second one, and the first one has successfully connect.
Try removing the dummy asdc-controller entry, and restart SO. I tend to think 
the stacktrace you mentioned will disappear.

Alexis

> On Jan 15, 2018, at 9:29 PM, Chenchuanyu  wrote:
> 
> Hi SDC Team,
>I found that Distribution Client of SO cannot registered successful to SDC.
> Below is the errormso.log and the SDC configuration , asdc-controller1 is 
> used to register the distribution client. The response message from SDC is 
> CONF_INVALID_ASDC_FQDN.
> Because of this SO cannot get the template information designed in SDC, can 
> anyone help on this?
>  
> 2017-12-02T23:25:30.003Z|trace-#|EJB default - 
> 9|InitASDC||ASDC||WARN|BusinessProcesssError|ASDCControllerException in 
> checkInStoppedState|Exception raised: 
> org.openecomp.mso.asdc.client.exceptions.ASDCControllerException: 
> Initialization of the ASDC Controller failed with reason: configuration is 
> invalid: CONF_INVALID_ASDC_FQDN -   at 
> org.openecomp.mso.asdc.client.ASDCController.initASDC(ASDCController.java:237)
>  -   at 
> org.openecomp.mso.asdc.client.ASDCGlobalController.checkInStoppedState(ASDCGlobalController.java:130)
>  -  at 
> org.openecomp.mso.asdc.ASDCControllerSingleton.periodicControllerTask(ASDCControllerSingleton.java:63)
>  -  at sun.reflect.GeneratedMethodAccessor367.invoke(Unknown Source) -
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  -at java.lang.reflect.Method.invoke(Method.java:498) -at 
> org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
>  -   at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) 
> -  at 
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:57)
>  - at 
> org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)
>  - at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) 
> -  at 
> org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
>  - at 
> org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82)
>  -at 
> org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:95)
>  -   at 
> org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)
>  - at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) 
> -  at 
> org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:57)
>  - at 
> org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)
>  - at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) 
> -  at 
> org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
>  -  at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) 
> -  at 
> org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
>  - at 
> org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
>  -   at 
> org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
>  -  at 
> org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) 
> -  at 
>  
> {
> "asdc-connections":{
> "asdc-controller1":{
> "user":"mso",
> "consumerGroup":"sdc-OpenSource-Env1-mso-dockero",
> "consumerId":"sdc-COpenSource-Env11-mso-dockero",
> "environmentName":"SDC-OpenSource-Env1",
> "asdcAddress":"c2.vm1.sdc.simpledemo.openecomp.org:8443 
> ",
> 
> "password":"613AF3483E695524F9857643B697FA51C7A9A0951094F53791485BF3458F9EADA37DBACCCEBD0CB242B85B4062745247",
> "pollingInterval":"60",
> "pollingTimeout":"60",
> "relevantArtifactTypes":"HEAT,HEAT_ENV,HEAT_VOL",
> "activateServerTLSAuth":"false",
> "keyStorePassword":"",
> "keyStorePath":""
> },
> "asdc-controller2":{
> "user":"user",
>

Re: [onap-discuss] Reg. vDNS registration and policies

[Alexis de Talhouët]

Hi,

I’m planing on doing a step by step for vDNS as I’ve done for vFWCL, but 
haven’t got the time to do it yet.
That being said, you could follow the video that was done by Marco here 
https://wiki.onap.org/display/DW/Running+the+ONAP+Demos?preview=/1015891/16010234/vLB_closed_loop.mp4
 


Regarding policy for vDNS, I believe they are pushed at the startup of the 
policy containers, checkout the logs of pap. If you go in the ONAP portal as 
the demo/demo123456! user, you should be able to go in the Policy UI, browse 
the policy through the policy editor, and right click on it to see its content.

Alexis 

> On Jan 16, 2018, at 4:06 AM, ESWAR RAO  wrote:
> 
> Hi All,
> 
> I have setup ONAP Amsterdam release and registered a VIM (ocata version 
> openstack) through AAI.
> 
> 
> Now I wanted to see how I can do vDNS and achieve CLAMP.
> 
> I was following:
> 
> https://github.com/mikalstill/onap-demos 
> 
> 
> https://wiki.onap.org/display/DW/vFWCL+instantiation,+testing,+and+debuging 
> 
> 
> Can some one please provide pointers of how I can perform instantiation from 
> E2E.
> 
> Anywhere I can get some pointers where Policies are defined for vDNS just 
> like in below:
> 
> http://onap.readthedocs.io/en/latest/submodules/vnfsdk/model.git/docs/files/VNF%20SDK%20blueprints.html
>  
> 
> 
> 
> 
> Thanks
> Eswar Rao
> 
> ___
> 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] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL

[Matt, Brian]

Bin,

I'm in the process of updating our deployment with the suggested 
versions/branches to see if it will make a difference. I should be able to test 
later today, I'll let you know.


Brian


From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Tuesday, January 16, 2018 4:51 AM
To: Matt, Brian ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Brian,

Have you been able to get policy issue fixed?  I observed the same issue, and 
the branches are correct for my ONAP template file. Does anyone could help on 
this issue? Thanks.
   policy_repohttp://gerrit.onap.org/r/policy/docker.git
   policy_dockerv1.1.2
policy_branchamsterdam
policy_repohttp://gerrit.onap.org/r/policy/docker.git


$ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh 
policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 
./onap_dev.pem


Removing the vFW Policy from PDP..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> DELETE /pdp/api/deletePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 133
>
* upload completely sent off: 133 out of 133 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 91
< Date: Tue, 16 Jan 2018 09:32:08 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 310812b5-858f-4ee7-82a7-0b6723466a19 --The policy was 
successfully deleted.


Updating vFW Operational Policy ..

*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/updatePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 1309
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 149
< Date: Tue, 16 Jan 2018 09:32:29 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 8ea2a93d-9e9a-4d30-b944-c6d169cc2eb5 --Policy with the name 
com.Config_BRMS_Param_BRMSParamvFirewall.2.xml was successfully updated.

Pushing the vFW Policy ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/pushPolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 99
>
* upload completely sent off: 99 out of 99 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 162
< Date: Tue, 16 Jan 2018 09:32:35 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 9ad6377c-6a4c-4a8c-870f-df9fa69a5003 --Policy 
'com.Config_BRMS_Param_BRMSParamvFirewall.2.xml' was successfully pushed to the 
PDP group 'default'.

Restarting PDP-D ..


The authenticity of host 'policy.api.simpledemo.onap.org (10.12.9.121)' can't 
be established.
ECDSA key fingerprint is SHA256:PzUojk3RJNW5LsjcrMA80lyIV3opeekfg7fbbOqsqE8.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'policy.api.simpledemo.onap.org,10.12.9.121' (ECDSA) 
to the list of known hosts.
[drools-pdp-controllers]
L []: Stopping Policy Management... Policy Management (pid=5503) is stopping... 
Policy Management has stopped.
[drools-pdp-controllers]
L []: Policy Management (pid 5762) is running


PDP-D amsterdam maven coordinates ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 9696 (#0)
* Server auth using Basic with user '@1b3rt'
> GET /policy/pdp/engine/controllers/amsterdam/drools HTTP/1.1
> Host: policy.api.simpledemo.onap.org:9696
> Authorization: Basic QDFiM3J0OjMxbnN0MzFu
> User-Agent: curl/7.50.1
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Tue, 16 Jan 2018 09:33:44 GMT
< Content-Type: application/json
< Content-Length: 31
< Server: Jetty(9.3.14.v20161028)
<
{ [31 bytes data]
* Connection #0 to host policy.api.simpledemo.onap.org left intact
{
"error": "amsterdam not found"
}


PDP-D control loop updated ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 9696 (#0)
* Server auth using Basic with user '@1b3rt'
> GET 
> /policy/pdp/engine/controllers/amsterdam/drools/facts/closedloop-amsterdam/org.onap.policy.controlloop.Params
>  HTTP/1.1

Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL

[Yang, Bin]

Hi Pam,

   Appreciate your quick response, I am using the ONAP lab but in 
my newly created tenant. Please let me know the username of your team members 
who will working on this this issue, so I can add him/her to be member of my 
tenant.

   Thanks.

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

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 16, 2018 9:40 PM
To: Yang, Bin; Matt, Brian; onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Bin,

Sorry I missed this the other day. Let’s have our team take a look as it looks 
like the Drools PDP is missing the Amsterdam controller. That should never have 
been deleted.

Which lab are you in? If you can give access to Jorge, he can take a quick look.

Regards,

Pam

From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Yang, Bin" 
mailto:bin.y...@windriver.com>>
Date: Tuesday, January 16, 2018 at 4:50 AM
To: "Matt, Brian" 
mailto:brian.m...@windstream.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Brian,

Have you been able to get policy issue fixed?  I observed the same issue, and 
the branches are correct for my ONAP template file. Does anyone could help on 
this issue? Thanks.
   policy_repo
http://gerrit.onap.org/r/policy/docker.git
   policy_dockerv1.1.2
policy_branchamsterdam
policy_repo
http://gerrit.onap.org/r/policy/docker.git


$ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh 
policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 
./onap_dev.pem


Removing the vFW Policy from PDP..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> DELETE /pdp/api/deletePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 133
>
* upload completely sent off: 133 out of 133 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 91
< Date: Tue, 16 Jan 2018 09:32:08 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 310812b5-858f-4ee7-82a7-0b6723466a19 --The policy was 
successfully deleted.


Updating vFW Operational Policy ..

*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/updatePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 1309
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 149
< Date: Tue, 16 Jan 2018 09:32:29 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 8ea2a93d-9e9a-4d30-b944-c6d169cc2eb5 --Policy with the name 
com.Config_BRMS_Param_BRMSParamvFirewall.2.xml was successfully updated.

Pushing the vFW Policy ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/pushPolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 99
>
* upload completely sent off: 99 out of 99 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 162
< Date: Tue, 16 Jan 2018 09:32:35 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 9ad6377c-6a4c-4a8c-870f-df9fa69a5003 --Policy 
'com.Config_BRMS_Param_BRMSParamvFirewall.2.xml' was successfully pushed to the 
PDP group 'default'.

Restarting PDP-D ..


Th

Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL

[DRAGOSH, PAMELA L (PAM)]

Sure – please add Jorge. Not sure what his username is, he can provide that.

Thanks,

Pam

From: "Yang, Bin" 
Date: Tuesday, January 16, 2018 at 9:20 AM
To: "DRAGOSH, PAMELA L (PAM)" , "Matt, Brian" 
, "onap-discuss@lists.onap.org" 

Cc: "HERNANDEZ-HERRERO, JORGE" 
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Pam,

   Appreciate your quick response, I am using the ONAP lab but in 
my newly created tenant. Please let me know the username of your team members 
who will working on this this issue, so I can add him/her to be member of my 
tenant.

   Thanks.

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

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 16, 2018 9:40 PM
To: Yang, Bin; Matt, Brian; onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Bin,

Sorry I missed this the other day. Let’s have our team take a look as it looks 
like the Drools PDP is missing the Amsterdam controller. That should never have 
been deleted.

Which lab are you in? If you can give access to Jorge, he can take a quick look.

Regards,

Pam

From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Yang, Bin" 
mailto:bin.y...@windriver.com>>
Date: Tuesday, January 16, 2018 at 4:50 AM
To: "Matt, Brian" 
mailto:brian.m...@windstream.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Brian,

Have you been able to get policy issue fixed?  I observed the same issue, and 
the branches are correct for my ONAP template file. Does anyone could help on 
this issue? Thanks.
   policy_repo
http://gerrit.onap.org/r/policy/docker.git
   policy_dockerv1.1.2
policy_branchamsterdam
policy_repo
http://gerrit.onap.org/r/policy/docker.git


$ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh 
policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 
./onap_dev.pem


Removing the vFW Policy from PDP..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> DELETE /pdp/api/deletePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 133
>
* upload completely sent off: 133 out of 133 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 91
< Date: Tue, 16 Jan 2018 09:32:08 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 310812b5-858f-4ee7-82a7-0b6723466a19 --The policy was 
successfully deleted.


Updating vFW Operational Policy ..

*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/updatePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 1309
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 149
< Date: Tue, 16 Jan 2018 09:32:29 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 8ea2a93d-9e9a-4d30-b944-c6d169cc2eb5 --Policy with the name 
com.Config_BRMS_Param_BRMSParamvFirewall.2.xml was successfully updated.

Pushing the vFW Policy ..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/pushPolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 99
>
* upload completely sent off: 99 out of 99 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Cont

Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL

[Yang, Bin]

I just added Jorge as a member of tenant ‘demonstrable’ , please go with this 
tenant.

Thanks.

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

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 16, 2018 10:23 PM
To: Yang, Bin; Matt, Brian; onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Sure – please add Jorge. Not sure what his username is, he can provide that.

Thanks,

Pam

From: "Yang, Bin" mailto:bin.y...@windriver.com>>
Date: Tuesday, January 16, 2018 at 9:20 AM
To: "DRAGOSH, PAMELA L (PAM)" 
mailto:pdrag...@research.att.com>>, "Matt, Brian" 
mailto:brian.m...@windstream.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Cc: "HERNANDEZ-HERRERO, JORGE" mailto:jh1...@att.com>>
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Pam,

   Appreciate your quick response, I am using the ONAP lab but in 
my newly created tenant. Please let me know the username of your team members 
who will working on this this issue, so I can add him/her to be member of my 
tenant.

   Thanks.

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

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 16, 2018 9:40 PM
To: Yang, Bin; Matt, Brian; 
onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Bin,

Sorry I missed this the other day. Let’s have our team take a look as it looks 
like the Drools PDP is missing the Amsterdam controller. That should never have 
been deleted.

Which lab are you in? If you can give access to Jorge, he can take a quick look.

Regards,

Pam

From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Yang, Bin" 
mailto:bin.y...@windriver.com>>
Date: Tuesday, January 16, 2018 at 4:50 AM
To: "Matt, Brian" 
mailto:brian.m...@windstream.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Brian,

Have you been able to get policy issue fixed?  I observed the same issue, and 
the branches are correct for my ONAP template file. Does anyone could help on 
this issue? Thanks.
   policy_repo
http://gerrit.onap.org/r/policy/docker.git
   policy_dockerv1.1.2
policy_branchamsterdam
policy_repo
http://gerrit.onap.org/r/policy/docker.git


$ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh 
policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 
./onap_dev.pem


Removing the vFW Policy from PDP..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> DELETE /pdp/api/deletePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 133
>
* upload completely sent off: 133 out of 133 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 91
< Date: Tue, 16 Jan 2018 09:32:08 GMT
<
* Connection #0 to host policy.api.simpledemo.onap.org left intact
Transaction ID: 310812b5-858f-4ee7-82a7-0b6723466a19 --The policy was 
successfully deleted.


Updating vFW Operational Policy ..

*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> PUT /pdp/api/updatePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 1309
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-Length: 1

Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL

[HERNANDEZ-HERRERO, JORGE]

Hi Bin,

I looked at your 10.12.9.121 vm.   Can you do the following to use the latest 
amsterdam version?


1.   /opt/config/docker_version.txt – change to v1.1.3 (relates to 
POLICY-486)

2.   mv /opt/policy /opt/policy.old

3.   git clone -b $(cat /opt/config/gerrit_branch.txt)--single-branch $(cat 
/opt/config/remote_repo.txt) /opt/policy

4.   policy_vm_init.sh

There was some issue discussed in POLICY-486 that I think you may have hit and 
should be solved now.

Let me know how it goes.

Jorge

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Tuesday, January 16, 2018 8:41 AM
To: DRAGOSH, PAM ; Matt, Brian 
; onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE 
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

I just added Jorge as a member of tenant ‘demonstrable’ , please go with this 
tenant.

Thanks.

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

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 16, 2018 10:23 PM
To: Yang, Bin; Matt, Brian; 
onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Sure – please add Jorge. Not sure what his username is, he can provide that.

Thanks,

Pam

From: "Yang, Bin" mailto:bin.y...@windriver.com>>
Date: Tuesday, January 16, 2018 at 9:20 AM
To: "DRAGOSH, PAMELA L (PAM)" 
mailto:pdrag...@research.att.com>>, "Matt, Brian" 
mailto:brian.m...@windstream.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Cc: "HERNANDEZ-HERRERO, JORGE" mailto:jh1...@att.com>>
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Pam,

   Appreciate your quick response, I am using the ONAP lab but in 
my newly created tenant. Please let me know the username of your team members 
who will working on this this issue, so I can add him/her to be member of my 
tenant.

   Thanks.

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

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 16, 2018 9:40 PM
To: Yang, Bin; Matt, Brian; 
onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Bin,

Sorry I missed this the other day. Let’s have our team take a look as it looks 
like the Drools PDP is missing the Amsterdam controller. That should never have 
been deleted.

Which lab are you in? If you can give access to Jorge, he can take a quick look.

Regards,

Pam

From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Yang, Bin" 
mailto:bin.y...@windriver.com>>
Date: Tuesday, January 16, 2018 at 4:50 AM
To: "Matt, Brian" 
mailto:brian.m...@windstream.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Brian,

Have you been able to get policy issue fixed?  I observed the same issue, and 
the branches are correct for my ONAP template file. Does anyone could help on 
this issue? Thanks.
   policy_repo
http://gerrit.onap.org/r/policy/docker.git
   policy_dockerv1.1.2
policy_branchamsterdam
policy_repo
http://gerrit.onap.org/r/policy/docker.git


$ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh 
policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 
./onap_dev.pem


Removing the vFW Policy from PDP..


*   Trying 10.12.9.121...
* Connected to policy.api.simpledemo.onap.org (10.12.9.121) port 8081 (#0)
> DELETE /pdp/api/deletePolicy HTTP/1.1
> Host: policy.api.simpledemo.onap.org:8081
> User-Agent: curl/7.50.1
> Content-Type: application/json
> Accept: text/plain
> ClientAuth: cHl0aG9uOnRlc3Q=
> Authorization: Basic dGVzdHBkcDphbHBoYTEyMw==
> Environment: TEST
> Content-Length: 133
>
* upload completely sent off: 133 out of 133 bytes
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Content-Type: text/plain;charset=ISO-8859-1
< Content-

[onap-discuss] [ONAP Helpdesk #51163] Promote Liang ke to Committer of Multi VIM/Cloud

[Kenny Paul via RT]

Approval- #3 item
http://ircbot.wl.linuxfoundation.org/meetings/onap-meeting/2018/onap-meeting.2018-01-04-13.47.html

-kenny

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

[onap-discuss] [ONAP Helpdesk #51163] Promote Liang ke to Committer of Multi VIM/Cloud

[Jessica Wagantall via RT]

Dear Xinhui, 

Do you have a TSC approval link for this request? I was not able to find it in 
the link you provided me. 

thanks a ton
Jess

On Tue Jan 16 07:15:02 2018, lxin...@vmware.com wrote:
> Hi Jessica,
> 
> TSC have approved Liang ke as a committer of Multi VIM/Cloud. Please
> help to promote him or let me know I need submit some ticket for this.
> 
> Please refer to this link for more info:
> https://wiki.onap.org/pages/viewpage.action?pageId=22249517
> 
> Thanks,
> 
> Xinhui Li
> PTL of Multi VIM/Cloud



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

[onap-discuss] [ONAP Helpdesk #51163] Promote Liang ke to Committer of Multi VIM/Cloud

[Jessica Wagantall via RT]

Thanks so much Kenny, 

This request has been completed now

Thanks!
Jess

On Tue Jan 16 12:13:33 2018, jwagantall wrote:
> Dear Xinhui,
> 
> Do you have a TSC approval link for this request? I was not able to
> find it in the link you provided me.
> 
> thanks a ton
> Jess
> 
> On Tue Jan 16 07:15:02 2018, lxin...@vmware.com wrote:
> > Hi Jessica,
> >
> > TSC have approved Liang ke as a committer of Multi VIM/Cloud. Please
> > help to promote him or let me know I need submit some ticket for
> > this.
> >
> > Please refer to this link for more info:
> > https://wiki.onap.org/pages/viewpage.action?pageId=22249517
> >
> > Thanks,
> >
> > Xinhui Li
> > PTL of Multi VIM/Cloud



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

Re: [onap-discuss] [integration]Please help us on Integration Lab

[Michael O'Brien]

Stephen,
   Hi, thank you – saw the return to service this morning – very nice!.
   I am still having SSH issues due to the network refactor over the holidays – 
we used to be able to get to 10.12.5.0/24 nodes directly – but some of those 
externally facing networks are gone.
   Currently using the jump box/bastion box instead – I still have ssh issues 
to vms
   I will test password-only access instead of ssh – is there a new procedure 
on which network to attach to our vm so we can get into it
   Thank you

From the jira

still having an issue with ssh between nodes – either directly or fron the jump 
box

michael_o_brien@pod-onap-01-vjhost:~$ ssh -i openlab_oom_key.pem 
ubuntu@10.12.5.14

ssh: connect to host 10.12.5.14 port 22: Protocol not available
oom-jenkins

(not found)

appc-multicloud-integration * 10.10.5.14

m1.xlarge

openlab_oom_key

Active

nova

None

Running

6 days, 13 hours

Create 
Snapshot



oom-obrien-64

(not found)

external * 10.12.5.10

m1.xxlarge

openlab_oom_key

Active

nova

None

Running

1 week, 4 days

Create 
Snapshot



oom-obrien-64-1

(not found)

oam_onap_6Gve * 10.0.0.29

m1.xxlarge

openlab_oom_key

Active

nova

None

Running

1 week, 4 days

Create 
Snapshot

·Comment


From: Gooch, Stephen [mailto:stephen.go...@windriver.com]
Sent: Tuesday, January 16, 2018 04:05
To: Michael O'Brien ; Yunxia Chen 
; Raineri, Eddy ; Yang, Bin 

Cc: onap-discuss 
Subject: RE: [integration]Please help us on Integration Lab

Hello All,

Lab access has been restored.

Br,
-Stephen

From: Michael O'Brien [mailto:frank.obr...@amdocs.com]
Sent: Monday, January 15, 2018 20:56
To: Yunxia Chen; Gooch, Stephen; Raineri, Eddy; Yang, Bin
Cc: onap-discuss
Subject: RE: [integration]Please help us on Integration Lab

Fyi,
   I raised the issue on the VPN 36 hours ago after the Thu retrofit – service 
has been excellent and prompt – I would expect tomorrow we should be good.
   https://jira.onap.org/browse/OPENLABS-153
https://lists.onap.org/pipermail/onap-discuss/2018-January/007390.html

   For now you can consult the CD poc on AWS that is pending migration to the 
LF under (OOM-500) to at least get 
healthcheck hourly for master
http://jenkins.onap.info/job/oom-cd/

http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS?_g=(refreshInterval:(display:Off,pause:!f,value:0),time:(from:now-7d,mode:quick,to:now))&_a=(description:'',filters:!(),options:(darkTheme:!f),panels:!((col:1,id:AWAts77k3NTXK5mX2kuM,panelIndex:1,row:1,size_x:8,size_y:3,type:visualization),(col:9,id:AWAtuTVI3NTXK5mX2kuP,panelIndex:2,row:1,size_x:4,size_y:3,type:visualization),(col:1,id:AWAtuBTY3NTXK5mX2kuO,panelIndex:3,row:7,size_x:6,size_y:3,type:visualization),(col:1,id:AWAttmqB3NTXK5mX2kuN,panelIndex:4,row:4,size_x:6,size_y:3,type:visualization),(col:7,id:AWAtvHtY3NTXK5mX2kuR,panelIndex:6,row:4,size_x:6,size_y:6,type:visualization)),query:(match_all:()),timeRestore:!f,title:'CD%20Health%20Check',uiState:(),viewMode:view)

Notice that the MSB fix has fixed the 8 failing heathcheck from the 13th – 3 
hours ago
https://gerrit.onap.org/r/#/c/27943/

   thanks Stephen,
   /michael


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yunxia Chen
Sent: Monday, January 15, 2018 10:15
To: Gooch, Stephen 
mailto:stephen.go...@windriver.com>>; Raineri, 
Eddy mailto:eddy.rain...@windriver.com>>; Yang, Bin 
mailto:bin.y...@windriver.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [integration]Please help us on Integration Lab

Thank you Stephen.
Since the team is doing MR testing, if possible, please help to get it up asap.

Regards,

Helen Chen

From: "Gooch, Stephen" 
mailto:stephen.go...@windriver.com>>
Date: Monday, January 15, 2018 at 7:10 AM
To: Helen Chen 00725961 mailto:helen.c...@huawei.com>>, 
"Raineri, Eddy" 
mailto:eddy.rain...@windriver.com>>, "Yang, Bin" 
mailto:bin.y...@windriver.com>>
Cc: onap-discuss 
mailto:onap-discuss@lists.onap.org>>
Subject: RE: [integration]Please help us on Integration Lab

Hi Helen,

The issue is in the building, external to the ONAP lab.   See attached.

Br,
- Stephen

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Monday, January 15, 2018 16:08
To: Gooch, Stephen; 

Re: [onap-discuss] [Onap-arc] [ONAP container] ONAP event follow up: next steps and logistics(doodle poll)

[Xinhui Li]

Isaku,

The list is under draft which need more work and discussion. The team also have 
some questions for this proposal.  I will allocate time for this topic in the 
coming weekly (PST 5:00 to 6:00PM every Monday). Please attend.

Thanks,

Xinhui 

On 1/12/18, 6:12 AM, "Isaku Yamahata"  wrote:

Hello Xinhui. Just heads up.

Although I know that k8s is on the list of Beijing planning [1],
let us coordinate on k8s related stuff at multicloud weekly meetings.

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D22250779&d=DwIBAg&c=uilaK90D4TOVoH58JNXRgQ&r=14DWHoQdlEcTDc7RcGLzzkS0IMYLAIocLc5dNQRKqgk&m=arPqk4jdHjenOKeqVt7p4M4HAftEP151NWWHzm3D4yg&s=aJ8syRLsTPez_LAO3qSHsqzzKCpXTBFC1l1YE9h0BCw&e=

Thanks,

On Thu, Jan 11, 2018 at 10:56:45AM -0800,
Isaku Yamahata  wrote:

> Now the feedback from ARC subcommittee is to start as subproject under the
> unbrella of multicloud project.
> Anyway let's start weekly meeting in order to discuss our own details.
> Given the availability of major contributors, I chosen the following 
timeslot.
> 
>   - China(Wed)2:00am/UTC(Wed) 18:00PM/ET(Tue) 13:00pm-/PT(Tue) 10:00am
> 
> Also we should attend multicloud project weekly meeting for coordination 
with them.
> 
> 
> Thanks,
> 
> 
> On Mon, Jan 08, 2018 at 10:35:43AM -0800,
> Isaku Yamahata  wrote:
> 
> > Hello. Sorry for late reply.
> > Unfortunately we can't find good timeslot for all the attendees and key 
contributor.
> > As Isaku is going to present 2nd review at tomorrow(Jan 9, 2019) ARC 
subcommittee,
> > let's postpone one week to see the outcome.
> > 
> > So far timezone candidate (according to voting).
> > - CST Wed 2:00am/UTC Tue 18:00pm/EST Tue 13:00pm/PST TUE 10:00 AM 11:00 
AM
> > - CST Wed 13:00pm/UTC Wed 05:00am/EST Tue 12:00 midnight/PST Tue 21:00pm
> > 
> > I'm wondering if timeslot rotation bi-weekly.
> > I'd like to include Bin and Munish, though. no such time slots.
> > 
> > Thanks,
> > 
> > On Thu, Dec 21, 2017 at 01:18:34PM -0800,
> > Isaku Yamahata  wrote:
> > 
> > > Hello.
> > > Looking at doodle poll, it looks difficult to arrange one time slot.
> > > 
> > > According to the poll, the following time slots
> > > (China(Tue)7:00am/UTC(Mon) 11:00PM/PST(Mon) 3:00PM or
> > > China(Wed)7:00am/UTC 11:00PM/PST 3:00PM) are candidates,
> > > but key contributors will be missing.
> > > What does timeslot candidate work for you in addition to the poll?
> > > 
> > > Thanks,
> > > 
> > > On Thu, Dec 14, 2017 at 02:54:07PM -0800,
> > > Isaku Yamahata  wrote:
> > > 
> > > > Hello ONAP kubernetes folks.
> > > > This week we had good discussions and got feedback from TSC.
> > > > In order to follow to the feedback and make the next step,
> > > > I'd like to arrange weekly zoom meeting.
> > > > 
> > > > 
> > > > * doodle poll for timeslot for zoom meeting
> > > > I've created a doodle poll for meeting. Please vote for timeslot.
> > > > 
https://urldefense.proofpoint.com/v2/url?u=https-3A__doodle.com_poll_hkas87yba5bcyfs9&d=DwIBAg&c=uilaK90D4TOVoH58JNXRgQ&r=14DWHoQdlEcTDc7RcGLzzkS0IMYLAIocLc5dNQRKqgk&m=arPqk4jdHjenOKeqVt7p4M4HAftEP151NWWHzm3D4yg&s=zLcLNtvzGgsNKEsoltQFHDKF_CAJhp81Oje6RAc3jxQ&e=
> > > > We can start meeting from the week of Jan 1 or 8, 2018.
> > > > If we're agressive, we can also have a meeting on the week of Dec 
18, 2017.
> > > > 
> > > > 
> > > > * wiki page
> > > > 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D16007890&d=DwIBAg&c=uilaK90D4TOVoH58JNXRgQ&r=14DWHoQdlEcTDc7RcGLzzkS0IMYLAIocLc5dNQRKqgk&m=arPqk4jdHjenOKeqVt7p4M4HAftEP151NWWHzm3D4yg&s=zqvAWkcrO0lO4tI6vfJRn5aV02rHrlJgzBmc6_CnoNw&e=
> > > > I've created this wiki page to collect/accumulate information.
> > > > 
> > > > Bin, Can you please up load your presentations and create link?
> > > > Frank, Can you please please create your proposal and upload it?
> > > > Hopefully your proposal can on the table for discussion.
> > > > 
> > > > 
> > > > There are several discussion points.
> > > > - how to deploy VNF
> > > >   So far we have two proposals. Bin's proposal and Munish 
proposal(3 options).
> > > >   - use ARIA or not
> > > >   - use Helm or not
> > > >   - relationship to TOSCA
> > > > 
> > > > - Life Cycle Management(LCM)
> > > >   There are several aspects of LCM and the how to architect
> > > >   generic VNF controller in the contest of k8s.
> > > >   - configuration
> > > >   - auto scaling
> > > >   - rolling upgrade
> > > > 
> > > > - relationship to other ONAP component
> > > >   especially multicloud, SO, OOF and modeling would have a deep 
relat

Re: [onap-discuss] [Onap-arc] [ONAP container] ONAP event follow up: next steps and logistics(doodle poll)

[Mohamed El-Serngawy]

Hi Isaku,

Would you send the (Container based network) tomorrow meeting details, I
couldn't find the zoom link.

Thanks

On Thu, Jan 11, 2018 at 5:12 PM, Isaku Yamahata <
yamah...@private.email.ne.jp> wrote:

> Hello Xinhui. Just heads up.
>
> Although I know that k8s is on the list of Beijing planning [1],
> let us coordinate on k8s related stuff at multicloud weekly meetings.
>
> [1] https://wiki.onap.org/pages/viewpage.action?pageId=22250779
>
> Thanks,
>
> On Thu, Jan 11, 2018 at 10:56:45AM -0800,
> Isaku Yamahata  wrote:
>
> > Now the feedback from ARC subcommittee is to start as subproject under
> the
> > unbrella of multicloud project.
> > Anyway let's start weekly meeting in order to discuss our own details.
> > Given the availability of major contributors, I chosen the following
> timeslot.
> >
> >   - China(Wed)2:00am/UTC(Wed) 18:00PM/ET(Tue) 13:00pm-/PT(Tue) 10:00am
> >
> > Also we should attend multicloud project weekly meeting for coordination
> with them.
> >
> >
> > Thanks,
> >
> >
> > On Mon, Jan 08, 2018 at 10:35:43AM -0800,
> > Isaku Yamahata  wrote:
> >
> > > Hello. Sorry for late reply.
> > > Unfortunately we can't find good timeslot for all the attendees and
> key contributor.
> > > As Isaku is going to present 2nd review at tomorrow(Jan 9, 2019) ARC
> subcommittee,
> > > let's postpone one week to see the outcome.
> > >
> > > So far timezone candidate (according to voting).
> > > - CST Wed 2:00am/UTC Tue 18:00pm/EST Tue 13:00pm/PST TUE 10:00 AM
> 11:00 AM
> > > - CST Wed 13:00pm/UTC Wed 05:00am/EST Tue 12:00 midnight/PST Tue
> 21:00pm
> > >
> > > I'm wondering if timeslot rotation bi-weekly.
> > > I'd like to include Bin and Munish, though. no such time slots.
> > >
> > > Thanks,
> > >
> > > On Thu, Dec 21, 2017 at 01:18:34PM -0800,
> > > Isaku Yamahata  wrote:
> > >
> > > > Hello.
> > > > Looking at doodle poll, it looks difficult to arrange one time slot.
> > > >
> > > > According to the poll, the following time slots
> > > > (China(Tue)7:00am/UTC(Mon) 11:00PM/PST(Mon) 3:00PM or
> > > > China(Wed)7:00am/UTC 11:00PM/PST 3:00PM) are candidates,
> > > > but key contributors will be missing.
> > > > What does timeslot candidate work for you in addition to the poll?
> > > >
> > > > Thanks,
> > > >
> > > > On Thu, Dec 14, 2017 at 02:54:07PM -0800,
> > > > Isaku Yamahata  wrote:
> > > >
> > > > > Hello ONAP kubernetes folks.
> > > > > This week we had good discussions and got feedback from TSC.
> > > > > In order to follow to the feedback and make the next step,
> > > > > I'd like to arrange weekly zoom meeting.
> > > > >
> > > > >
> > > > > * doodle poll for timeslot for zoom meeting
> > > > > I've created a doodle poll for meeting. Please vote for timeslot.
> > > > > https://doodle.com/poll/hkas87yba5bcyfs9
> > > > > We can start meeting from the week of Jan 1 or 8, 2018.
> > > > > If we're agressive, we can also have a meeting on the week of Dec
> 18, 2017.
> > > > >
> > > > >
> > > > > * wiki page
> > > > > https://wiki.onap.org/pages/viewpage.action?pageId=16007890
> > > > > I've created this wiki page to collect/accumulate information.
> > > > >
> > > > > Bin, Can you please up load your presentations and create link?
> > > > > Frank, Can you please please create your proposal and upload it?
> > > > > Hopefully your proposal can on the table for discussion.
> > > > >
> > > > >
> > > > > There are several discussion points.
> > > > > - how to deploy VNF
> > > > >   So far we have two proposals. Bin's proposal and Munish
> proposal(3 options).
> > > > >   - use ARIA or not
> > > > >   - use Helm or not
> > > > >   - relationship to TOSCA
> > > > >
> > > > > - Life Cycle Management(LCM)
> > > > >   There are several aspects of LCM and the how to architect
> > > > >   generic VNF controller in the contest of k8s.
> > > > >   - configuration
> > > > >   - auto scaling
> > > > >   - rolling upgrade
> > > > >
> > > > > - relationship to other ONAP component
> > > > >   especially multicloud, SO, OOF and modeling would have a deep
> relationship.
> > > > >
> > > > >
> > > > > - any other discussion points?
> > > > >
> > > > > Thanks,
> > > > > --
> > > > > Isaku Yamahata 
> > > > > ___
> > > > > onap-discuss mailing list
> > > > > onap-discuss@lists.onap.org
> > > > > https://lists.onap.org/mailman/listinfo/onap-discuss
> > > > >
> > > >
> > > > --
> > > > Isaku Yamahata 
> > > > ___
> > > > onap-discuss mailing list
> > > > onap-discuss@lists.onap.org
> > > > https://lists.onap.org/mailman/listinfo/onap-discuss
> > > >
> > >
> > > --
> > > Isaku Yamahata 
> > > ___
> > > Onap-arc mailing list
> > > onap-...@lists.onap.org
> > > https://lists.onap.org/mailman/listinfo/onap-arc
> > >
> >
> > --
> > Isaku Yamahata 
> >
>
> --
> Isaku Yamahata 
> ___
> Onap-arc mailing list
> onap-...@lists.onap.org
> https://lists.onap.

[onap-discuss] [integration]Topics for this week's Integration Meeting

[Yunxia Chen]

Hi,

The following is the agenda for tomorrow’s meeting so far, please let me know 
if you have anything to add:

1/16/2018

  1.  Amsterdam Maintenance release testing status
 *   vFWCL (Marco / Gary)
 *   vDNS (Marco / Gary)
 *   vCPE (Kang)
 *   VoLTE (Chengli / Yang)
  2.  Integration Lab:
 *   Intel / Windriver Lab: (Stephen)
 *   TLAB (Rich)
  3.  Beijing release related topics:
 *   Integration R2 Release 
Planning
 *   Benchmark: (Yan Chen)

Regards,
Helen Chen
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-arc] [ONAP container] ONAP event follow up: next steps and logistics(doodle poll)

[Isaku Yamahata]

https://wiki.onap.org/pages/viewpage.action?pageId=16009184

[coe] Team ONAP5, China(Wed)2:00am / UTC(Wed) 18:00PM / ET(Tue) 13:00pm / 
PT(Tue) 10:00am
> Meeting Information:
>  ONAP Meeting 5 is inviting you to a scheduled Zoom meeting.
>  Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/961993336


On Mon, Jan 15, 2018 at 12:59:06PM -0500,
Mohamed El-Serngawy  wrote:

> Hi Isaku,
> 
> Would you send the (Container based network) tomorrow meeting details, I
> couldn't find the zoom link.
> 
> Thanks
> 
> On Thu, Jan 11, 2018 at 5:12 PM, Isaku Yamahata <
> yamah...@private.email.ne.jp> wrote:
> 
> > Hello Xinhui. Just heads up.
> >
> > Although I know that k8s is on the list of Beijing planning [1],
> > let us coordinate on k8s related stuff at multicloud weekly meetings.
> >
> > [1] https://wiki.onap.org/pages/viewpage.action?pageId=22250779
> >
> > Thanks,
> >
> > On Thu, Jan 11, 2018 at 10:56:45AM -0800,
> > Isaku Yamahata  wrote:
> >
> > > Now the feedback from ARC subcommittee is to start as subproject under
> > the
> > > unbrella of multicloud project.
> > > Anyway let's start weekly meeting in order to discuss our own details.
> > > Given the availability of major contributors, I chosen the following
> > timeslot.
> > >
> > >   - China(Wed)2:00am/UTC(Wed) 18:00PM/ET(Tue) 13:00pm-/PT(Tue) 10:00am
> > >
> > > Also we should attend multicloud project weekly meeting for coordination
> > with them.
> > >
> > >
> > > Thanks,
> > >
> > >
> > > On Mon, Jan 08, 2018 at 10:35:43AM -0800,
> > > Isaku Yamahata  wrote:
> > >
> > > > Hello. Sorry for late reply.
> > > > Unfortunately we can't find good timeslot for all the attendees and
> > key contributor.
> > > > As Isaku is going to present 2nd review at tomorrow(Jan 9, 2019) ARC
> > subcommittee,
> > > > let's postpone one week to see the outcome.
> > > >
> > > > So far timezone candidate (according to voting).
> > > > - CST Wed 2:00am/UTC Tue 18:00pm/EST Tue 13:00pm/PST TUE 10:00 AM
> > 11:00 AM
> > > > - CST Wed 13:00pm/UTC Wed 05:00am/EST Tue 12:00 midnight/PST Tue
> > 21:00pm
> > > >
> > > > I'm wondering if timeslot rotation bi-weekly.
> > > > I'd like to include Bin and Munish, though. no such time slots.
> > > >
> > > > Thanks,
> > > >
> > > > On Thu, Dec 21, 2017 at 01:18:34PM -0800,
> > > > Isaku Yamahata  wrote:
> > > >
> > > > > Hello.
> > > > > Looking at doodle poll, it looks difficult to arrange one time slot.
> > > > >
> > > > > According to the poll, the following time slots
> > > > > (China(Tue)7:00am/UTC(Mon) 11:00PM/PST(Mon) 3:00PM or
> > > > > China(Wed)7:00am/UTC 11:00PM/PST 3:00PM) are candidates,
> > > > > but key contributors will be missing.
> > > > > What does timeslot candidate work for you in addition to the poll?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > On Thu, Dec 14, 2017 at 02:54:07PM -0800,
> > > > > Isaku Yamahata  wrote:
> > > > >
> > > > > > Hello ONAP kubernetes folks.
> > > > > > This week we had good discussions and got feedback from TSC.
> > > > > > In order to follow to the feedback and make the next step,
> > > > > > I'd like to arrange weekly zoom meeting.
> > > > > >
> > > > > >
> > > > > > * doodle poll for timeslot for zoom meeting
> > > > > > I've created a doodle poll for meeting. Please vote for timeslot.
> > > > > > https://doodle.com/poll/hkas87yba5bcyfs9
> > > > > > We can start meeting from the week of Jan 1 or 8, 2018.
> > > > > > If we're agressive, we can also have a meeting on the week of Dec
> > 18, 2017.
> > > > > >
> > > > > >
> > > > > > * wiki page
> > > > > > https://wiki.onap.org/pages/viewpage.action?pageId=16007890
> > > > > > I've created this wiki page to collect/accumulate information.
> > > > > >
> > > > > > Bin, Can you please up load your presentations and create link?
> > > > > > Frank, Can you please please create your proposal and upload it?
> > > > > > Hopefully your proposal can on the table for discussion.
> > > > > >
> > > > > >
> > > > > > There are several discussion points.
> > > > > > - how to deploy VNF
> > > > > >   So far we have two proposals. Bin's proposal and Munish
> > proposal(3 options).
> > > > > >   - use ARIA or not
> > > > > >   - use Helm or not
> > > > > >   - relationship to TOSCA
> > > > > >
> > > > > > - Life Cycle Management(LCM)
> > > > > >   There are several aspects of LCM and the how to architect
> > > > > >   generic VNF controller in the contest of k8s.
> > > > > >   - configuration
> > > > > >   - auto scaling
> > > > > >   - rolling upgrade
> > > > > >
> > > > > > - relationship to other ONAP component
> > > > > >   especially multicloud, SO, OOF and modeling would have a deep
> > relationship.
> > > > > >
> > > > > >
> > > > > > - any other discussion points?
> > > > > >
> > > > > > Thanks,
> > > > > > --
> > > > > > Isaku Yamahata 
> > > > > > ___
> > > > > > onap-discuss mailing list
> > > > > > onap-discuss@lists.onap.org
> > > > > > https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Beijing Release Functional requirements Commitment

[Gildas Lanilis]

Hi PTLs,

This is to follow up on the discussion we had earlier today at PTL weekly 
meeting regarding Beijing Functional Requirements.

I summarized in a single table the functional 
requirements 
the PTLs are committing for Beijing Release.

So far, I had the chance to discuss with some of you to review the table.
For those I have not discussed yet with (sorry, it is a matter of geographical 
location), feel free to edit the table or contact me for any questions you may 
have. A 5-10 minutes zoom meeting worth the time.
Use the comment column to clearly state why a requirement is "NA" or "No". Feel 
to free to re-use current statements like "Not enough resource", "Requirement 
not clear", "Not priority", "Requirement owner did not reach out",...

It is critical we communicate clearly ahead on Beijing Release functional 
Requirement scope. During M1 review on Thursday, the clock will be ticking and 
we will not have time to discuss the details.

Let me know if you have any questions, I will be glad to help.

Thanks,
Gildas

[HuaweiLogowithName]
Gildas Lanilis
ONAP Release Manager
Santa Clara CA, USA
gildas.lani...@huawei.com
Mobile: 1 415 238 6287

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

[onap-discuss] Need Feedback: VES Additional Info structure

[GUPTA, ALOK]

DCAE ONAP TEAM Members:

We have a request for updating VES additonalInformation Structure in each 
Domain to  get rid of repeating name and value in the additional name. 
Following is an example of current implementation:
  "chronicThresholdCount": "3",
 "faultFields": {
"eventSourceType": "interface",
"alarmAdditionalInformation": [{
  "name": "DIR",
  "value": "tx"
}, {
  "name": "LOC",
  "value": "NEND"
}, {
  "name": "TYPE",
  "value": "communication"
}, {
  "name": "CKTID",
  "value": ""
}, {
  "name": "agingThreshold",
  "value": "300"
}, {
  "name": "objType",
  "value": "interface"
}, {
  "name": "alarmEntityOid",
  "value": "ORLDFLPC-0101050934 interface-eth-1/0/C1/1"
}],
"specificProblem": "lossOfSignal",
"alarmInterfaceA": "eth-1/0/C1/1",
"alarmCondition": "lossOfSignal",
"eventSeverity": "CRITICAL",
"faultFieldsVersion": 1,
"vfStatus": "Active"
 },
 "chronicInterval": "2"
  },

The modified structure would look like:
"chronicThresholdCount": "3",
 "faultFields": {
"eventSourceType": "interface",
"alarmAdditionalInformation": {
   "DIR":"tx",
   "LOC": "NEND",
   "TYPE": "communication",
   "CKTID": "",
   "agingThreshold": "300",
   "objType": "interface",
   "alarmEntityOid": "ORLDFLPC-0101050934 
interface-eth-1/0/C1/1"
},
"specificProblem": "lossOfSignal",
"alarmInterfaceA": "eth-1/0/C1/1",
"alarmCondition": "lossOfSignal",
"eventSeverity": "CRITICAL",
"faultFieldsVersion": 1,
"vfStatus": "Active"
 },
 "chronicInterval": "2"
  },

The rationale other than this being compact and reduces event processing time, 
for recommended changes are:


  1.  It inflates the message size by 16 bytes per name/value pair.  (So, 64 
entries in a message yields 1KB of waste.)


  1.  It forces message readers to iterate through an array doing string 
comparisons at O(n) rather than a typical hash lookup of O(log n). If a message 
writer drops 100 entries into that array, my high-speed event processing has to 
do 100 operations instead of 6. That's a 16x slowdown!  This matters quite a 
bit when dealing with 1000s of events per second.


  1.  We have event processing tools throughout our infrastructure that know 
how to pull named values from arbitrary JSON. For example, we have syntax like: 
${event.faultFields.alarmAdditionalInformation.alarmEntityOid}. Unfortunately, 
these tools are useless when data is in this 
array-of-objects-with-name-and-value-keys format. Our tools would have to be 
upgraded to support a name/value search like: 
${event.faultFields.alarmAdditionalInformation[name=alarmEntityOid].value}. 
This hardly seems worth doing - it'd be a bit difficult to implement and graft 
into our current syntax and in maybe 8 years of using JSON across a lot of 
services, I've never seen this construct.

We have two choices:


1.  We could replace the old name/value structure with new one, or

2.  We could support second structure in addition to first one to allow 
both for backward compatibility.

My personal preference is to replace and let collector convert 4.x and 5.x to 
the new structure. This impacts current downstream DCAE systems and I would 
like to get feedback on the change from ONAP team.

I would be discussing the issue during regularly scheduled DCAE team meeting.

Please advise.

Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com

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

[onap-discuss] [ONAP Helpdesk #51075] JIRA Beijing release in Affects/Fix Version missing?

[Jessica Wagantall via RT]

Dear Michael, 

I went through the projects and added the "Beijing Release" in 2 projects that 
were missing it. 

Can you please double check your project and let me know if you see it now?

Thanks a ton!
Jess

On Sat Jan 13 19:22:11 2018, frank.obr...@amdocs.com wrote:
> Team,
>Hi, noticed when raising/editing jiras today that the Beijing
> release is missing - we only have Amsterdam, Casablanca Release,
> Dublin Release.
>The Beijing release was last there yesterday (Friday 20180112)
>When we find issues in master/Beijing we are unable to set the
> Affects or Fix field for that release.
>Thank you
>/michael
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

Re: [onap-discuss] Need Feedback: VES Additional Info structure

[FREEMAN, BRIAN D]

The name/value pair array is usually used to allow for adding new parameters 
without a change to the model.

Is that not a concern with VES additionaInformationStructures ?

Brian


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of GUPTA, ALOK
Sent: Tuesday, January 16, 2018 1:58 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] Need Feedback: VES Additional Info structure
Importance: High

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
DCAE ONAP TEAM Members:

We have a request for updating VES additonalInformation Structure in each 
Domain to  get rid of repeating name and value in the additional name. 
Following is an example of current implementation:
  "chronicThresholdCount": "3",
 "faultFields": {
"eventSourceType": "interface",
"alarmAdditionalInformation": [{
  "name": "DIR",
  "value": "tx"
}, {
  "name": "LOC",
  "value": "NEND"
}, {
  "name": "TYPE",
  "value": "communication"
}, {
  "name": "CKTID",
  "value": ""
}, {
  "name": "agingThreshold",
  "value": "300"
}, {
  "name": "objType",
  "value": "interface"
}, {
  "name": "alarmEntityOid",
  "value": "ORLDFLPC-0101050934 interface-eth-1/0/C1/1"
}],
"specificProblem": "lossOfSignal",
"alarmInterfaceA": "eth-1/0/C1/1",
"alarmCondition": "lossOfSignal",
"eventSeverity": "CRITICAL",
"faultFieldsVersion": 1,
"vfStatus": "Active"
 },
 "chronicInterval": "2"
  },

The modified structure would look like:
"chronicThresholdCount": "3",
 "faultFields": {
"eventSourceType": "interface",
"alarmAdditionalInformation": {
   "DIR":"tx",
   "LOC": "NEND",
   "TYPE": "communication",
   "CKTID": "",
   "agingThreshold": "300",
   "objType": "interface",
   "alarmEntityOid": "ORLDFLPC-0101050934 
interface-eth-1/0/C1/1"
},
"specificProblem": "lossOfSignal",
"alarmInterfaceA": "eth-1/0/C1/1",
"alarmCondition": "lossOfSignal",
"eventSeverity": "CRITICAL",
"faultFieldsVersion": 1,
"vfStatus": "Active"
 },
 "chronicInterval": "2"
  },

The rationale other than this being compact and reduces event processing time, 
for recommended changes are:


  1.  It inflates the message size by 16 bytes per name/value pair.  (So, 64 
entries in a message yields 1KB of waste.)


  1.  It forces message readers to iterate through an array doing string 
comparisons at O(n) rather than a typical hash lookup of O(log n). If a message 
writer drops 100 entries into that array, my high-speed event processing has to 
do 100 operations instead of 6. That's a 16x slowdown!  This matters quite a 
bit when dealing with 1000s of events per second.


  1.  We have event processing tools throughout our infrastructure that know 
how to pull named values from arbitrary JSON. For example, we have syntax like: 
${event.faultFields.alarmAdditionalInformation.alarmEntityOid}. Unfortunately, 
these tools are useless when data is in this 
array-of-objects-with-name-and-value-keys format. Our tools would have to be 
upgraded to support a name/value search like: 
${event.faultFields.alarmAdditionalInformation[name=alarmEntityOid].value}. 
This hardly seems worth doing - it'd be a bit difficult to implement and graft 
into our current syntax and in maybe 8 years of using JSON across a lot of 
services, I've never seen this construct.

We have two choices:


  1.  We could replace the old name/value structure with new one, or
  2.  We could support second structure in addition to first one to allow both 
for backward compatibility.

My personal preference is to replace and let collector convert 4.x and 5.x to 
the new structure. This impacts current downstream DCAE systems and I would 
like to get feedback on the change from ONAP team.

I would be discussing the issue during regularly scheduled DCAE team meeting.

Please advise.

Regards,

Alok Gupta
732-420-7007
MT B2 3D30
ag1...@att.com

[onap-discuss] [ONAP Helpdesk #51095] Add logging-analytics repo to Jenkins JobBuilder and Sonar

[Jessica Wagantall via RT]

Dear Michael, 

I have double checked that Jenkins (Maven settings file), Nexus2 and Nexus3 
bits for this new project are present. 

I have also created the new Jenkins tab in preparation for the JJB jobs. Sonar 
will appear once the daily job runs and it will automatically generate an entry 
for your project there. 

Here is an initial change for your JJB templates:
https://gerrit.onap.org/r/#/c/28345/

Can you please review this change and let me know for any changes you need 
(depending on your project's needs)

Thanks a ton!
Jess

On Sun Jan 14 22:59:47 2018, frank.obr...@amdocs.com wrote:
> Linux Foundation, TSC,
>Could you add the logging-analytics project to Jenkins,
> nexus/nexus3 and Sonar.
>We have started development work on the Logging RI and AOP library
> and would like the standard Java Jenkins build to kick in along with
> sonar tracking.
>Currently we need the JobBuilder -1/+1 process to run on git
> commits to the logging-analytics repo.
>I have submitted a functioning minimal project structure that
> builds a template rest war as the initial framework.  The docker
> container that will run this microservice is next in the list.
>See
> https://gerrit.onap.org/r/#/c/28129/
>tested under
> http://logging.us-east-1.elasticbeanstalk.com/rest/read/test
>for
> https://jira.onap.org/browse/LOG-120
>for the R2 epic
> https://jira.onap.org/browse/LOG-95
>We will need a new folder under https://jenkins.onap.org/
>Thank you
>/michael
> 
> 
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> 
> you may review at https://www.amdocs.com/about/email-disclaimer
> 



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

[onap-discuss] Invitation: ONAP Parser As A Service Discussion @ Thu Jan 18, 2018 4am - 6am (PST) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180118T12Z
DTEND:20180118T14Z
DTSTAMP:20180116T210512Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:r2dptb3qckdp84m1kf7l5hb...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=atul.puroh...@vodafone.com;X-NUM-GUESTS=0:mailto:atul.purohit1@voda
 fone.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
CREATED:20180116T210342Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 7 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/696936829\n\nOr iPhone one-tap :\nUS: +16699006833\,\,696936829#  o
 r +16465588656\,\,696936829# \nOr Telephone:\nDial(for higher quality\,
  dial a number based on your current location): \nUS: +1 669 900 68
 33  or +1 646 558 8656  or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (
 Toll Free)\nMeeting ID: 696 936 829\nInternational numbers availabl
 e: https://zoom.us/zoomconference?m=-ZE637X3vpkoIcSXJlJUV8VKH1rcc2dQ\n\n\n\
 n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~::~:~::-\nPlease do not edit this section of the description.\n\nView 
 your event at https://www.google.com/calendar/event?action=VIEW&eid=cjJkcHR
 iM3Fja2RwODRtMWtmN2w1aGJicGcgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn&tok=NzIjb
 GludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxl
 bmRhci5nb29nbGUuY29tMzI5OTBlZjQyYjhmZTgwMGRmNDI3YmQ4Mzc3MjFjNDM5OTAwZTdlNA&
 ctz=America/Los_Angeles&hl=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180116T210511Z
LOCATION:https://zoom.us/j/696936829
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:ONAP Parser As A Service Discussion
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H10M0S
END:VALARM
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

[onap-discuss] Invitation: ONAP Parser As A Service Discussion @ Mon Jan 22, 2018 4am - 6am (PST) (onap-discuss@lists.onap.org)

[kpaul]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180122T12Z
DTEND:20180122T14Z
DTSTAMP:20180116T211353Z
ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3
 uc8f76fmflplo...@group.calendar.google.com
UID:a93d1fqugatdmr509jo9v39...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=onap-discuss@lists.onap.org;X-NUM-GUESTS=0:mailto:onap-discuss@list
 s.onap.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=atul.puroh...@vodafone.com;X-NUM-GUESTS=0:mailto:atul.purohit1@voda
 fone.com
CREATED:20180116T211258Z
DESCRIPTION:Hi there\, \n\nONAP Meeting 7 is inviting you to a scheduled Zo
 om meeting. \n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.u
 s/j/582922554\n\nOr iPhone one-tap :\nUS: +16465588656\,\,582922554#  o
 r +16699006833\,\,582922554# \nOr Telephone:\nDial(for higher quality\,
  dial a number based on your current location): \nUS: +1 646 558 86
 56  or +1 669 900 6833  or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (
 Toll Free)\nMeeting ID: 582 922 554\nInternational numbers availabl
 e: https://zoom.us/zoomconference?m=fHZb2kA17cjJNycOQuG1Xi2mrjjwalqx\n\n\n\
 n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~::~:~::-\nPlease do not edit this section of the description.\n\nView 
 your event at https://www.google.com/calendar/event?action=VIEW&eid=YTkzZDF
 mcXVnYXRkbXI1MDlqbzl2Mzlicmcgb25hcC1kaXNjdXNzQGxpc3RzLm9uYXAub3Jn&tok=NzIjb
 GludXhmb3VuZGF0aW9uLm9yZ18xcm10YjV0cHIzdWM4Zjc2Zm1mbHBsb2k4OEBncm91cC5jYWxl
 bmRhci5nb29nbGUuY29tYjdkOWUyOTRlYWJmNWNiMThhZTFmMmQzNmU5NmVhODk3ZmJlYjkwNw&
 ctz=America/Los_Angeles&hl=en.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180116T211353Z
LOCATION:https://zoom.us/j/582922554
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:ONAP Parser As A Service Discussion
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H10M0S
END:VALARM
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] ONAP Instant Messaging Survey

[Kenny Paul]

Please don’t forget to fill out the IM survey and also PLEASE do not select 
more than one “My Top Prioriy” to question 1.
https://www.surveymonkey.com/r/39CLJSS 

Thanks!

Best Regards, 
-kenny

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

> On Jan 9, 2018, at 12:28 PM, Kenny Paul  wrote:
> 
> 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] VIM registration for Multi-VIM

[Bisht, Suraj (Nokia - US/Irving)]

Hi Bin, Liz,

After adding new VIM we are still getting MSO  error in VF-Module deployment

We added new cloud-sites in MSO as well but same result. Is there any formal 
procedure to push new VIM info to MSO

Kindly clarify following

a)   After adding VIM details into ESR what are the subsequent steps i.e. 
adding to MSO

b)  Can MSO cloud site have same region_id twice? our both VIMs using same 
region name

c)   How MSO know which Cloud site to use

d)  What is mso_pass and how to provide a valid value while adding a new 
site or modifying current one with new VIM

MSO error

Received vfModuleException from VnfAdapter: category='INTERNAL' 
message='org.openecomp.mso.openstack.exceptions.MsoAdapterException: 
Authentication Failure: 
tenant=4fc3ee7632934653a3abccca190215e8,cloud=DEFAULT_KEYSTONE' 
rolledBack='true'


|b5579593-eb59-4bb0-a505-0fd40d9a4ad1|INFO|0|172.18.0.3|0|mso.mso.testlab.openecomp.org|172.18.0.3
2018-01-16T21:09:00.360Z|2018-01-16T21:09:00.360Z|f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|N/A|default
 task-47||MSO.CVFMI|BPMNClient|COMPLETE|0|FH_request_id: 
f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|b5579593-eb59-4bb0-a505-0fd40d9a4ad1|INFO|0|172.18.0.3|0|mso.mso.testlab.openecomp.org|172.18.0.3
2018-01-16T21:09:00.362Z|2018-01-16T21:09:00.362Z|f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|N/A|default
 task-47||MSO.CVFMI|BPMNClient|COMPLETE|0|FH_ErrorCode: 
7020|b5579593-eb59-4bb0-a505-0fd40d9a4ad1|INFO|0|172.18.0.3|0|mso.mso.testlab.openecomp.org|172.18.0.3
2018-01-16T21:09:00.365Z|2018-01-16T21:09:00.365Z|f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|N/A|default
 task-47||MSO.FH|BPMNClient|COMPLETE|0|updateRequestInfraPayload:
http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:req="http://org.openecomp.mso/requestsdb";>




f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2

BPEL
Received 
vfModuleException from VnfAdapter: category='INTERNAL' 
message='org.openecomp.mso.openstack.exceptions.MsoAdapterException: 
Authentication Failure: 
tenant=4fc3ee7632934653a3abccca190215e8,cloud=DEFAULT_KEYSTONE' 
rolledBack='true'

FAILED
100




|b5579593-eb59-4bb0-a505-0fd40d9a4ad1|INFO|0|172.18.0.3|0|mso.mso.testlab.openecomp.org|172.18.0.3
2018-01-16T21:09:00.477Z|2018-01-16T21:09:00.477Z|f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|N/A|default
 task-47||MSO.FH|BPMNClient|COMPLETE|0|FalloutHandler Response: 
http://org.openecomp/mso/workflow/schema/v1";>

MSO config
/opt/test_lab/volumes/mso/chef-config/mso-docker.json

"mso-po-adapter-config": {
  "checkrequiredparameters": "true",
  "cloud_sites": [
{
  "aic_version": "2.5",
  "id": "regionOne",
  "identity_service_id": "DEFAULT_KEYSTONE",
  "lcp_clli": "regionOne",
  "region_id": "regionOne"
},
{
  "aic_version": "2.5",
  "id": "Nokia_WDS",
  "identity_service_id": "WDS_KEYSTONE",
  "lcp_clli": "Nokia_WDS",
  "region_id": "regionOne"
}
  ],
  "identity_services": [
{
  "admin_tenant": "service",
  "dcp_clli": "DEFAULT_KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD",
  "identity_server_type": "KEYSTONE",
  "identity_url": "http://x.x.x.x:5000/v2.0";,
  "member_role": "admin",
  "mso_id": "onap",
  "mso_pass": "3478e94a26cee89518c9fca110d875ea",
  "tenant_metadata": "true"
},
{
  "admin_tenant": "service",
  "dcp_clli": "WDS_KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD",
  "identity_server_type": "KEYSTONE",
  "identity_url": "http://x.x.x.x:5000/v2.0";,
  "member_role": "admin",
  "mso_id": "admin",
  "mso_pass": "3478e94a26cee89518c9fca110d875ea",
  "tenant_metadata": "true"
}
  ],

Thanks,
Suraj

From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Monday, January 15, 2018 9:39 PM
To: li.z...@zte.com.cn; Bisht, Suraj (Nokia - US/Irving) 
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] VIM registration for Multi-VIM

You may find alternate way of registering VIM thru ONAP CLI.
Vim-register command would help here. 
http://onap.readthedocs.io/en/latest/submodules/cli.git/docs/cmd_help.html#vim-register

Regards
Kanagaraj M
-
Be transparent! Win tog

Re: [onap-discuss] [vnfsdk] repo plan

[Christopher Donley (Chris)]

Good point.  So far, SDC hasn't committed to delivering the code in the Beijing 
release, so let's hold off on that for now.

Also FYI, I updated Jira stories associated with each of our epics and made a 
first pass at prioritization.  Please take a look and feel free to update.

Chris

From: Lu, Lianhao [mailto:lianhao...@intel.com]
Sent: Monday, January 15, 2018 6:36 PM
To: Christopher Donley (Chris) ; 
onap-discuss@lists.onap.org
Subject: RE: [vnfsdk] repo plan

Do we need new repos for those tools coming from SDC? i.e. license tools and 
heat-tosca translater?

Best Refgards,
-Lianhao

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Christopher Donley 
(Chris)
Sent: Tuesday, January 16, 2018 2:14 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [vnfsdk] repo plan

Team,

As we discussed on Friday, we'll need some new repos for vnfsdk.  Since we need 
to ask for TSC approval for new repos, I want to make sure we have everything 
we expect to need for Beijing before I ask.  I'm planning to request the 
following:

*Dovetail-integration for integration with the OPNFV Dovetail tool

*Ice for ICE tools
I also propose that we rename "compliance" to "ves-agent", since that's what 
we're using it for.

Comments/feedback? Anything missing?  Please let me know by Weds so that I can 
ask the TSC to approve our new repos.

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

[onap-discuss] 答复: [SO][SDC]Distribution Client Register Failed.

[Chenchuanyu]

Hi Alexis,
Thanks a lot , I got it . I will remove the asdc-controller2 and try again.

Chuanyu Chen.

发件人: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
发送时间: 2018年1月16日 21:43
收件人: Chenchuanyu
抄送: onap-discuss
主题: Re: [onap-discuss] [SO][SDC]Distribution Client Register Failed.

Hi,

How do you know it’s picking the asdc-contoller1 config to connect?
What I’ve noticed is SO comes with two pre-configured asdc-controllers, but the 
thing is, one is a dummy one (asdc-controller2), but the asdc code in SO will 
try to establish the connection to all the controllers provided in the 
asdc-connections list, hence the issue you’re facing. You probably are seeing 
the logs of the second one, and the first one has successfully connect.
Try removing the dummy asdc-controller entry, and restart SO. I tend to think 
the stacktrace you mentioned will disappear.

Alexis


On Jan 15, 2018, at 9:29 PM, Chenchuanyu 
mailto:chenchua...@huawei.com>> wrote:

Hi SDC Team,
   I found that Distribution Client of SO cannot registered successful to SDC.
Below is the errormso.log and the SDC configuration , asdc-controller1 is used 
to register the distribution client. The response message from SDC is 
CONF_INVALID_ASDC_FQDN.
Because of this SO cannot get the template information designed in SDC, can 
anyone help on this?

2017-12-02T23:25:30.003Z|trace-#|EJB default - 
9|InitASDC||ASDC||WARN|BusinessProcesssError|ASDCControllerException in 
checkInStoppedState|Exception raised: 
org.openecomp.mso.asdc.client.exceptions.ASDCControllerException: 
Initialization of the ASDC Controller failed with reason: configuration is 
invalid: CONF_INVALID_ASDC_FQDN -   at 
org.openecomp.mso.asdc.client.ASDCController.initASDC(ASDCController.java:237) 
-   at 
org.openecomp.mso.asdc.client.ASDCGlobalController.checkInStoppedState(ASDCGlobalController.java:130)
 -  at 
org.openecomp.mso.asdc.ASDCControllerSingleton.periodicControllerTask(ASDCControllerSingleton.java:63)
 -  at sun.reflect.GeneratedMethodAccessor367.invoke(Unknown Source) -  
  at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 -at java.lang.reflect.Method.invoke(Method.java:498) -at 
org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)
 -   at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) -  
at 
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:57)
 - at 
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)
 - at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) -  
at 
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
 - at 
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82)
 -at 
org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:95)
 -   at 
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)
 - at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) -  
at 
org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:57)
 - at 
org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:61)
 - at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) -  
at 
org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)
 -  at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) -  
at 
org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)
 - at 
org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)
 -   at 
org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)
 -  at 
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) -  
at

{
"asdc-connections":{
"asdc-controller1":{
"user":"mso",
"consumerGroup":"sdc-OpenSource-Env1-mso-dockero",
"consumerId":"sdc-COpenSource-Env11-mso-dockero",
"environmentName":"SDC-OpenSource-Env1",

"asdcAddress":"c2.vm1.sdc.simpledemo.openecomp.org:8443",

"password":"613AF3483E695524F9857643B697FA51C7A9A0951094F53791485BF3458F9EADA37DBACCCEBD0CB242B85B4062745247",
"pollingInterval":"60",
"pollingTimeout":"60",
"relevantArtifactTypes":"HEAT,HEAT_ENV,HEAT_VOL",
"activateServerTLSAuth":"false

Re: [onap-discuss] [ONAP Helpdesk #51163] Promote Liang ke to Committer of Multi VIM/Cloud

[lxin...@vmware.com via RT]

Thanks, Kenny and Jess!

On 17/01/2018, 1:17 AM, "Jessica Wagantall via RT" 
 wrote:

Thanks so much Kenny, 

This request has been completed now

Thanks!
Jess

On Tue Jan 16 12:13:33 2018, jwagantall wrote:
> Dear Xinhui,
> 
> Do you have a TSC approval link for this request? I was not able to
> find it in the link you provided me.
> 
> thanks a ton
> Jess
> 
> On Tue Jan 16 07:15:02 2018, lxin...@vmware.com wrote:
> > Hi Jessica,
> >
> > TSC have approved Liang ke as a committer of Multi VIM/Cloud. Please
> > help to promote him or let me know I need submit some ticket for
> > this.
> >
> > Please refer to this link for more info:
> > 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D22249517&d=DwIDaQ&c=uilaK90D4TOVoH58JNXRgQ&r=14DWHoQdlEcTDc7RcGLzzkS0IMYLAIocLc5dNQRKqgk&m=PrY67PMoFzFCYKFoQTMMWnd_B1_-m8VBJyz1TWbylw4&s=EP5LXiOiJHgwu4iivge5TM9JQJc61UsX41uYQeg79Mc&e=
> >
> > Thanks,
> >
> > Xinhui Li
> > PTL of Multi VIM/Cloud






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

Re: [onap-discuss] [ONAP Helpdesk #51163] Promote Liang ke to Committer of Multi VIM/Cloud

[Xinhui Li]

Thanks, Kenny and Jess!

On 17/01/2018, 1:17 AM, "Jessica Wagantall via RT" 
 wrote:

Thanks so much Kenny, 

This request has been completed now

Thanks!
Jess

On Tue Jan 16 12:13:33 2018, jwagantall wrote:
> Dear Xinhui,
> 
> Do you have a TSC approval link for this request? I was not able to
> find it in the link you provided me.
> 
> thanks a ton
> Jess
> 
> On Tue Jan 16 07:15:02 2018, lxin...@vmware.com wrote:
> > Hi Jessica,
> >
> > TSC have approved Liang ke as a committer of Multi VIM/Cloud. Please
> > help to promote him or let me know I need submit some ticket for
> > this.
> >
> > Please refer to this link for more info:
> > 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D22249517&d=DwIDaQ&c=uilaK90D4TOVoH58JNXRgQ&r=14DWHoQdlEcTDc7RcGLzzkS0IMYLAIocLc5dNQRKqgk&m=PrY67PMoFzFCYKFoQTMMWnd_B1_-m8VBJyz1TWbylw4&s=EP5LXiOiJHgwu4iivge5TM9JQJc61UsX41uYQeg79Mc&e=
> >
> > Thanks,
> >
> > Xinhui Li
> > PTL of Multi VIM/Cloud





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

Re: [onap-discuss] [modeling] Papyrus version

[yangxu (H)]

Hi Nigel,

Thanks for the advice and effort for updating the tutorial video!
Would you mind uploading the video to the wiki once you finish the update?

Regarding the chapter vs full video, personally I prefer to have the video in 
chapters, it’s easier to navigate.

Best regards,
Xu

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Davis, Nigel
Sent: Friday, January 12, 2018 11:55 PM
To: denghui (L) ; am8...@att.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [modeling] Papyrus version

Hi,

I propose we use 3.2.0 RC4 which is the latest stable release and then we stick 
with that (until we find features in a new version of Papyrus that we need).  I 
will need to do a small update to the video to provide instructions on how to 
load that. That will take me a couple of days. I have the original video in a 
number of chapters. It may be worth me providing those as that will mean that 
people can home in on the relevant one without having to wade through the whole 
video to try to find the relevant part. We can discuss this off line.

I will aim to get ONF, MEF etc to settle on 3.2.0 RC4 as well (although clearly 
I may not be able to achieve this).

Nigel

From: denghui (L) [mailto:denghu...@huawei.com]
Sent: 10 January 2018 19:25
To: Davis, Nigel mailto:nda...@ciena.com>>; 
am8...@att.com
Cc: onap-discuss@lists.onap.org
Subject: [**EXTERNAL**] [modeling] Papyrus version

Hi Nigel

Could you kindly help to advice what’s final version for papyrus for modeling 
team? Thanks a lot for your kind help.

Hi Andy,

Have you recorded Nigel’s training about Papyrus last Friday? Thanks a lot for 
your kind help

Best regards,

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

Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with vFWCL

[Yang, Bin]

Hi Jorge,

   It works. Appreciate your great help.

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

From: HERNANDEZ-HERRERO, JORGE [mailto:jh1...@att.com]
Sent: Wednesday, January 17, 2018 1:04 AM
To: Yang, Bin; DRAGOSH, PAM; Matt, Brian; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Bin,

I looked at your 10.12.9.121 vm.   Can you do the following to use the latest 
amsterdam version?


1.   /opt/config/docker_version.txt – change to v1.1.3 (relates to 
POLICY-486)

2.   mv /opt/policy /opt/policy.old

3.   git clone -b $(cat /opt/config/gerrit_branch.txt)--single-branch $(cat 
/opt/config/remote_repo.txt) /opt/policy

4.   policy_vm_init.sh

There was some issue discussed in POLICY-486 that I think you may have hit and 
should be solved now.

Let me know how it goes.

Jorge

From: Yang, Bin [mailto:bin.y...@windriver.com]
Sent: Tuesday, January 16, 2018 8:41 AM
To: DRAGOSH, PAM ; Matt, Brian 
; onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE 
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

I just added Jorge as a member of tenant ‘demonstrable’ , please go with this 
tenant.

Thanks.

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

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 16, 2018 10:23 PM
To: Yang, Bin; Matt, Brian; 
onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Sure – please add Jorge. Not sure what his username is, he can provide that.

Thanks,

Pam

From: "Yang, Bin" mailto:bin.y...@windriver.com>>
Date: Tuesday, January 16, 2018 at 9:20 AM
To: "DRAGOSH, PAMELA L (PAM)" 
mailto:pdrag...@research.att.com>>, "Matt, Brian" 
mailto:brian.m...@windstream.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Cc: "HERNANDEZ-HERRERO, JORGE" mailto:jh1...@att.com>>
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Pam,

   Appreciate your quick response, I am using the ONAP lab but in 
my newly created tenant. Please let me know the username of your team members 
who will working on this this issue, so I can add him/her to be member of my 
tenant.

   Thanks.

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

From: DRAGOSH, PAMELA L (PAM) [mailto:pdrag...@research.att.com]
Sent: Tuesday, January 16, 2018 9:40 PM
To: Yang, Bin; Matt, Brian; 
onap-discuss@lists.onap.org
Cc: HERNANDEZ-HERRERO, JORGE
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Bin,

Sorry I missed this the other day. Let’s have our team take a look as it looks 
like the Drools PDP is missing the Amsterdam controller. That should never have 
been deleted.

Which lab are you in? If you can give access to Jorge, he can take a quick look.

Regards,

Pam

From: 
mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Yang, Bin" 
mailto:bin.y...@windriver.com>>
Date: Tuesday, January 16, 2018 at 4:50 AM
To: "Matt, Brian" 
mailto:brian.m...@windstream.com>>, 
"onap-discuss@lists.onap.org" 
mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Hi Brian,

Have you been able to get policy issue fixed?  I observed the same issue, and 
the branches are correct for my ONAP template file. Does anyone could help on 
this issue? Thanks.
   policy_repo
http://gerrit.onap.org/r/policy/docker.git
   policy_dockerv1.1.2
policy_branchamsterdam
policy_repo
http://gerrit.onap.org/r/policy/docker.git


$ ./demo/vnfs/vFW/scripts/update-vfw-op-policy.sh 
policy.api.simpledemo.onap.org 7fe331bc-f46e-4cb3-aaa3-639024381f86 
./onap_dev.pem


Removing the vFW Policy from PDP..


*   Trying 10.12.9.121...
* Connected to policy.api.simple

Re: [onap-discuss] VIM registration for Multi-VIM

[li.zi30]

Hi Suraj,






Applies inline.






Regards,


LiZi











原始邮件



发件人： ;
收件人：李滋00164331; ;
抄送人： ; ;
日 期 ：2018年01月17日 07:14
主 题 ：RE: [onap-discuss] VIM registration for Multi-VIM




Hi Bin, Liz,


 


After adding new VIM we are still getting MSO  error in VF-Module deployment


 


We added new cloud-sites in MSO as well but same result. Is there any formal 
procedure to push new VIM info to MSO


 


Kindly clarify following


a)   After adding VIM details into ESR what are the subsequent steps i.e. 
adding to MSO


   LiZi: "adding VIM details into ESR", actually, ESR will put the basic 
VIM information to AAI, and inform Multi-VIM to put more detail about the VIM 
to AAI. Then MSO can get the VIM details from AAI.


b)  Can MSO cloud site have same region_id twice? our both VIMs using same 
region name


   LiZi: We use cloud-owner + cloud-region-id to locate an unique VIM.


c)   How MSO know which Cloud site to use


   LiZi: I think MSO team or Multi-VIM team may knows more.


d)  What is mso_pass and how to provide a valid value while adding a new 
site or modifying current one with new VIM


 


MSO error


 


Received vfModuleException from VnfAdapter: category='INTERNAL' 
message='org.openecomp.mso.openstack.exceptions.MsoAdapterException: 
Authentication Failure: 
tenant=4fc3ee7632934653a3abccca190215e8,cloud=DEFAULT_KEYSTONE'  
rolledBack='true'


 


 


|b5579593-eb59-4bb0-a505-0fd40d9a4ad1|INFO|0|172.18.0.3|0|mso.mso.testlab.openecomp.org|172.18.0.3


2018-01-16T21:09:00.360Z|2018-01-16T21:09:00.360Z|f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|N/A|default
 task-47||MSO.CVFMI|BPMNClient|COMPLETE|0|FH_request_id: 
f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|b5579593-eb59-4bb0-a505-0fd40d9a4ad1|INFO|0|172.18.0.3|0|mso.mso.testlab.openecomp.org|172.18.0.3


2018-01-16T21:09:00.362Z|2018-01-16T21:09:00.362Z|f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|N/A|default
 task-47||MSO.CVFMI|BPMNClient|COMPLETE|0|FH_ErrorCode: 
7020|b5579593-eb59-4bb0-a505-0fd40d9a4ad1|INFO|0|172.18.0.3|0|mso.mso.testlab.openecomp.org|172.18.0.3


2018-01-16T21:09:00.365Z|2018-01-16T21:09:00.365Z|f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|N/A|default
 task-47||MSO.FH|BPMNClient|COMPLETE|0|updateRequestInfraPayload:


http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:req="http://org.openecomp.mso/requestsdb";>












f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2



BPEL


Received 
vfModuleException from VnfAdapter:  category='INTERNAL' 
message='org.openecomp.mso.openstack.exceptions.MsoAdapterException: 
Authentication Failure: 
tenant=4fc3ee7632934653a3abccca190215e8,cloud=DEFAULT_KEYSTONE' 
rolledBack='true'



FAILED


100












|b5579593-eb59-4bb0-a505-0fd40d9a4ad1|INFO|0|172.18.0.3|0|mso.mso.testlab.openecomp.org|172.18.0.3


2018-01-16T21:09:00.477Z|2018-01-16T21:09:00.477Z|f9a67d1d-2e4a-4c4d-a3f2-2b101d3be8a2|N/A|default
 task-47||MSO.FH|BPMNClient|COMPLETE|0|FalloutHandler Response:  
http://org.openecomp/mso/workflow/schema/v1";>


 


MSO config


/opt/test_lab/volumes/mso/chef-config/mso-docker.json


 


"mso-po-adapter-config": {


  "checkrequiredparameters": "true",


  "cloud_sites": [


{


  "aic_version": "2.5",


  "id": "regionOne",


  "identity_service_id": "DEFAULT_KEYSTONE",


  "lcp_clli": "regionOne",


  "region_id": "regionOne"


},


{


  "aic_version": "2.5",


  "id": "Nokia_WDS",


  "identity_service_id": "WDS_KEYSTONE",


  "lcp_clli": "Nokia_WDS",


  "region_id": "regionOne"


}


  ],


  "identity_services": [


{


  "admin_tenant": "service",


  "dcp_clli": "DEFAULT_KEYSTONE",


  "identity_authentication_type": "USERNAME_PASSWORD",


  "identity_server_type": "KEYSTONE",


  "identity_url": "http://x.x.x.x:5000/v2.0";,


  "member_role": "admin",


  "mso_id": "onap",


  "mso_pass": "3478e94a26cee89518c9fca110d875ea",


  "tenant_metadata": "true"


},


{


  "admin_tenant": "service",


  "dcp_clli": "WDS_KEYSTONE",


  "identity_authentication_type": "USERNAME_PASSWORD",


  "identity_server_type": "KEYSTONE",


  "identity_url": "http://x.x.x.x:5000/v2.0";,


  "memb

[onap-discuss] [multicloud] Planned use of repo "multicloud/azure"

[HU, BIN]

Hello community,

MultiVIM/Cloud R2 (Beijing) Release will include support of Azure as a stretch 
goal. Thus we are planning to develop Azure Plugin in the repo 
"multicloud/azure".

This is a courtesy notice to the community regarding the planned use of repo 
"multicloud/azure", which is currently empty. If there is any concern or other 
plan from the community regarding this planned usage, please share your 
thoughts, concerns and/or other plans.

Thank you
Bin

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

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

[MAHER, RANDA]

Hello TSC, Kenny:

Any chance we can get this committer promotion approved over email?
I have put this on the agenda for this week's TSC meeting, but with M1 review, 
not sure we will get to it.

I have recorded five +1 thus far


1.   Dhananjay Pavgi

2.   Mazin Gilbert

3.   Jamil Chawki

4.   Alla Goldner

5.   Stephen Terrill

Thanks, Randa

From: Stephen Terrill [mailto:stephen.terr...@ericsson.com]
Sent: Friday, January 12, 2018 4:28 AM
To: MAHER, RANDA ; onap-...@lists.onap.org
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] Committer Promotion Request for [appc]

+1

From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of MAHER, RANDA
Sent: 12 January 2018 00:58
To: onap-...@lists.onap.org
Cc: onap-discuss@lists.onap.org
Subject: [onap-tsc] Committer Promotion Request for [appc]

Dear TSC,

Please consider request below for Committer Promotion for APPC project.

https://wiki.onap.org/pages/viewpage.action?pageId=22251669

One of our existing committers has indicated that he will  step down from 
Committer to Contributor role.
Existing Committers have all voted +1 on Taka Cho promotion to Committer.

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

Re: [onap-discuss] [Multicloud] Heat not getting listed in swagger url

[ESWAR RAO]

Thanks Bin for all the help.
Now its working for us !!!


Thanks
Eswar Rao



On Tue, Jan 16, 2018 at 8:56 AM, Yang, Bin  wrote:

> Hi Eswar,
>
>
>
>I don’t know exactly how you performed those actions, but I
> can put my test here:
>
>
>
> ubuntu@vm0-robot:~$ *export
> MULTICLOUD_PLUGIN_ENDPOINT=http://10.0.14.1:80/api/multicloud-titanium_cloud/v0/pod25_RegionOne
> *
>
>
>
> ubuntu@vm0-robot:~$ *curl -v -s -H "Content-Type: application/json" -X
> POST -d '{"auth": {"tenantName": "xxx", "passwordCredentials": {"username":
> "yyy", "password": "zzz"}}}'
> $MULTICLOUD_PLUGIN_ENDPOINT/identity/v2.0/tokens*
>
> *   Trying 10.0.14.1...
>
> * Connected to 10.0.14.1 (10.0.14.1) port 80 (#0)
>
> > POST /api/multicloud-titanium_cloud/v0/pod25_RegionOne/identity/v2.0/tokens
> HTTP/1.1
>
> > Host: 10.0.14.1
>
> > User-Agent: curl/7.47.0
>
> > Accept: */*
>
> > Content-Type: application/json
>
> > Content-Length: 119
>
> >
>
> * upload completely sent off: 119 out of 119 bytes
>
> < HTTP/1.1 200 OK
>
> < Server: openresty
>
> < Date: Tue, 16 Jan 2018 03:22:25 GMT
>
> < Content-Type: application/json
>
> < Transfer-Encoding: chunked
>
> < Connection: keep-alive
>
> < Vary: Cookie
>
> < X-Frame-Options: SAMEORIGIN
>
> < Allow: GET, POST, HEAD, OPTIONS
>
> <
>
> {"access":{"token":{"issued_at":"2018-01-16T03:22:26.
> 00Z","expires":"2018-01-16T04:22:26.00Z","id":"
> 7c463130b2ad403ea14c85352243c495","tenant":
>
>
>
>
>
> ubuntu@vm0-robot:~$ *export TOKEN=7c463130b2ad403ea14c85352243c495*
>
>
>
>
>
> ubuntu@vm0-robot:~$ *curl -v -s  -H "Content-Type: application/json"  -H
> "X-Auth-Token: $TOKEN" -X GET
> $MULTICLOUD_PLUGIN_ENDPOINT/orchestration/v1/c7738ddc4c414303b8960048a16b7fc6/stacks*
>
> *   Trying 10.0.14.1...
>
> * Connected to 10.0.14.1 (10.0.14.1) port 80 (#0)
>
> > GET /api/multicloud-titanium_cloud/v0/pod25_RegionOne/orchestration/v1/
> c7738ddc4c414303b8960048a16b7fc6/stacks HTTP/1.1
>
> > Host: 10.0.14.1
>
> > User-Agent: curl/7.47.0
>
> > Accept: */*
>
> > Content-Type: application/json
>
> > X-Auth-Token: 7c463130b2ad403ea14c85352243c495
>
> >
>
> < HTTP/1.1 200 OK
>
> < Server: openresty
>
> < Date: Tue, 16 Jan 2018 03:23:30 GMT
>
> < Content-Type: application/json
>
> < Transfer-Encoding: chunked
>
> < Connection: keep-alive
>
> < X-Subject-Token: 7c463130b2ad403ea14c85352243c495
>
> < Vary: Cookie
>
> < X-Frame-Options: SAMEORIGIN
>
> < Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
>
> <
>
> * Connection #0 to host 10.0.14.1 left intact
>
> {"stacks":[{"description":"","parent":null,"deletion_time":
> null,"stack_name":"onap.d","stack_user_project_id":"
> 92d4d1230d254a8185f989a15b459aad","stack_status_reason":"Stack CREATE
> completed successfully","creation_time":"2018-01-16T02:27:25Z","links"
> :[{"href":"http://10.0.14.1:80/api/multicloud-titanium_
> cloud/v0/pod25_RegionOne/orchestration/v1/c7738ddc4c414303b8960048a16b7f
> c6/stacks/onap.d/8e50c023-8caf-4c7e-9601-f4821a3fe7d0","
> rel":"self"}],"updated_time":"2018-01-16T02:27:25Z","stack_
> owner":null,"stack_status":"CREATE_COMPLETE","id":"
> 8e50c023-8caf-4c7e-9601-f4821a3fe7d0","tags":null}]}
>
>
>
>
>
> Best Regards,
>
> Bin Yang,Solution Readiness Team,*Wind River*
>
> Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189
>
> Skype: yangbincs993
>
>
>
> *From:* ESWAR RAO [mailto:eswar7...@gmail.com]
> *Sent:* Tuesday, January 16, 2018 8:26 AM
> *To:* Yang, Bin
> *Cc:* onap-discuss@lists.onap.org
> *Subject:* Re: [onap-discuss] [Multicloud] Heat not getting listed in
> swagger url
>
>
>
>
>
> Hi Bin,
>
>
>
> Thanks for the help.
>
>
>
> I have tried with keystone v2.0 token and issued the below call,
>
>
>
> curl -v -s  -H "Content-Type: application/json"  -H "X-Auth-Token:$TOKEN"
> -X GET http://192.168.21.212:80/api/multicloud/v0/radisys_mec/
> orchestration/v1/323b4f23d58143d29a81cd4adb6ade3b/stacks
>
>
>
> it gives,
>
> * About to connect() to 192.168.21.212 port 80 (#0)
>
> *   Trying 192.168.21.212...
>
> * Connected to 192.168.21.212 (192.168.21.212) port 80 (#0)
>
> > GET /api/multicloud/v0/radisys_mec/orchestration/v1/
> 323b4f23d58143d29a81cd4adb6ade3b/stacks HTTP/1.1
>
> User-Agent: curl/7.29.0
>
> Host: 192.168.21.212
>
> Accept: */*
>
> Content-Type: application/json
>
> X-Auth-Token:gABaXKre8_O5Y4TuTLMYxIzr6w9u9VAEX2i8G8WMs_zwQLvQ4_
> 1cYaKUFjBxMuq23DKB0Ps40bmnkqGoi0_QaQJ_bJyksCqJRmw0O6AAiF6okezB9teYZL
> yt08iscEqMZnbhOv88OZVFnGODf7wfIkHwFN-t7Dwa88KEvGBuSaIoK1WVWA0
>
>
>
> HTTP/1.1 403 Unknown Status Code
>
> Server: openresty
>
> Date: Mon, 15 Jan 2018 13:30:12 GMT
>
> Content-Type: application/json
>
> Content-Length: 58
>
> Connection: keep-alive
>
> status: 403
>
> Vary: Cookie
>
> content-encoding: gzip
>
> Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
>
> x-frame-options: SAMEORIGIN
>
> * Connection #0 to host 192.168.21.212 left intact
>
> *{"detail":"Authentication credentials were not pr