[onap-discuss] [dcae][dcaegen2][holmes] A Question on Auto Scailing of DCAE Microservices

[fu.guangrong]

Lusheng,






The Holmes team is currently working on the auto scaling plans for Holmes. We 
need to confirm something with you.






To my understanding, the microservice should only focus on how to maintain and 
balance its data flow rather than how the docker containers/vms are scaled by 
their controller. As a DCAE application, I think it's DCAE controller's 
responsiblity to determine when and how to scale in or scale out Holmes 
instances. Is that correct?






If what my understanding is correct, does DCAE have any specific requirements 
regarding collecting the status and metrics of its microservices?






Regards,


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

[onap-discuss] [AAI] [optfra] [multicloud] Persistence of HPA related information in A

[Ranganathan, Dileep]

Hello Jimmy,

I would like to discuss about the Persistence of HPA related information in 
A in the weekly meeting call.
I would like to discuss my proposal to capture the HPA capabilities in a 
generic way in A as
represented here --> 
https://wiki.onap.org/display/DW/Persistence+of+HPA+related+information+in+AAI
I would appreciate if we could include this in tomorrow's meeting.

Thanks,
Dileep Ranganathan

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

[onap-discuss] 答复: RE: [OOM][MSB] Kube2MSB RBAC security issues

[zhao.huabing]

Hi Nicolas,


Thanks for looking into this issue and solve it!


It looks to me that the second is more elegant.


BR,


Huabing



原始邮件



发件人： ;
收件人： ; ;赵化冰10201488;
日 期 ：2018年02月02日 03:01
主 题 ：RE: [OOM][MSB] Kube2MSB RBAC security issues




Hi Michael , Huabing


 


Here is the reason why Kube2MSB failed in RBAC enabled cluster.


 


The kube2MSB  will use the token from service account kube-system:default. This 
service account doesn’t have the admin privileges.


 


To fix that issue there are 2 ways


 


1.   Create a clusterrolebinding assign admin privileges to that service 
account


 


Just run following command:


kubectl create clusterrolebinding kube-system-default-admin-binding 
--clusterrole=cluster-admin --serviceaccount=kube-system:default


 


This command should execute once. Should we put it in 
createConfig.sh  ?


 


2.   Instead of using token from service account kube-system:default,  
kube2msb can use the token form service account onap-kube2msb:default .


In createAll.bash  the ClusterRoleBinding is created for onap-kube2msb:default. 
So that account already get the admin privileges.


 


Change the kube-system to $1-$2


 


   87   # assign default auth token


   88   if [[ -z $ONAP_DEFAULT_AUTH_TOKEN ]]; then


   89 DEFAULT_SECRET=`kubectl get secrets -n kube-system | grep 
default-token |  awk '{ print $1}'`


   90 ONAP_DEFAULT_AUTH_TOKEN=`kubectl get secrets $DEFAULT_SECRET -n 
kube-system -o yaml | grep  'token:'  | awk '{ print $2}' | base64 --decode`


   91   fi


   92 


  93cmd=`echo helm install $LOCATION/$2/ --name $1-$2 --namespace $1 --set 
nsPrefix=$1,nodePortPrefix=$3,kubeMasterAuthToken=$ONAP_DEFAULT_AUTH_TOKEN 
${HELM_VALUES_ADDITION}`


   94   eval ${cmd}


   95   check_return_code $cmd


 


Thanks,


Nicolas


 


[centos@server-186-kubernetes-master-host-8z2tnf robot]$ kubectl get 
ClusterRoleBinding onap-kube2msb-admin-binding -o yaml


apiVersion: rbac.authorization.k8s.io/v1


kind: ClusterRoleBinding


metadata:


  creationTimestamp: 2018-01-30T20:18:49Z


  name: onap-kube2msb-admin-binding


  resourceVersion: "159146"


  selfLink: 
/apis/rbac.authorization.k8s.io/v1/clusterrolebindings/onap-kube2msb-admin-binding


  uid: c838ff8d-05fa-11e8-bad9-fa163efe5022


roleRef:


  apiGroup: rbac.authorization.k8s.io


  kind: ClusterRole


  name: cluster-admin


subjects:


- kind: ServiceAccount


  name: default


  namespace: onap-kube2msb


 


 



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HU, JUN NICOLAS
 Sent: Wednesday, January 31, 2018 12:06 PM
 To: OBRIEN, FRANK MICHAEL ; 
onap-discuss@lists.onap.org
 Subject: [onap-discuss] [OOM][MSB] Kube2MSB RBAC security issues




 


***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.


Hi,


 


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


 


The Kube2MSB cannot access the apis of pods and services.


 


Thanks,


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

[onap-discuss] 答复: Re: VIM registration failure

[zhao.huabing]

Hi Kiruthiga,


Could you please get log of MSB internal api gateway using "sudo docker logs "? 
 It may help to investigate this issue.






Thanks,


Huabing











原始邮件



发件人： ;
收件人：李滋00164331;
抄送人： ;
日 期 ：2018年02月01日 19:45
主 题 ：Re: [onap-discuss] VIM registration failure


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

 

Hi LiZi,


 


Both AAI and Multicloud services are registered in MSB. But still we are 
getting the same error mentioned in the below mail.


 


All the request to MSB API is resulting in “Bad Gateway error”.  The external 
port of MSB-IAG server is either in CLOSE_WAIT or TIME_WAIT status while 
triggering  MSB API calls. If you could see in the error screenshot, during VIM 
registration request is sent to MSB-IAG server and it gives “Bad Gateway 
error”. Please help in fixing this issue.


 


Regards,


Kiruthiga



 



From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn] 
 Sent: Thursday, February 1, 2018 4:36 PM
 To: Kiruthiga R 
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] VIM registration failure




 



This message was identified as a phishing scam.



Feedback

Hi Kiruthiga,

Before you register VIM with ESR GUI, you need register the AAI's service to 
MSB. Also, you need register Multi-Cloud to MSB. You may check the registration 
result with MSB GUI (http://MSB_SERVER_IP/iui/microservices/default.html).  If 
they are not registered, please register with the following command.

 

curl -X POST \

-H "Content-Type: application/json" \

-d '{"serviceName": "aai-cloudInfrastructure", "version": "v11", "url": 
"/aai/v11/cloud-infrastructure","protocol": "REST", "enable_ssl":"true", 
"visualRange":"1", "nodes": [ {"ip": "ESR_SERVER_IP","port": "8443"}]}' \

http://MSB_SERVER_IP:10081/api/microservices/v1/services 

 

curl -X POST -H “Content-Type: application/json” -d ‘{“serviceName”: 
“multicloud”, “version”: “v0”, “url”: “/api/multicloud/v0”,”protocol”: “REST”, 
“nodes”: [ {“ip”: “’$MultiCloud_IP’”,”port”: “9001”}]}’ 
“http://$MSB_SERVER_IP:10081/api/microservices/v1/services“ 

 

Thanks,

LiZi

 

 


原始邮件



发件人： ;



收件人： ;



日 期 ：2018年02月01日 17:55



主 题 ：[onap-discuss]  VIM registration failure




___
onap-discuss mailing list
 onap-discuss@lists.onap.org
 
https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.onap.org%2fmailman%2flistinfo%2fonap%2ddiscuss=CAD20441-6424-9305-A7AC-9253E32E6B5F=f63efd9aed1e0a367f4bd39381444e47841a5725-599b5ddaa682f840307a6cbf4482e982d884cbe8
 
 


Hi Team,


 


We have installed Amsterdam release of ONAP. We were successfully able to 
demonstrate vFW heat template based instantiation. We are currently working on 
TOSCA based E2E service  instantiation. We have a customer vCER CSAR file with 
which  we were able to create and distribute network and E2E service. We were 
able to onboard vnf and ns packages using usecase-UI. While trying to do VIM 
registration through ESR GUI, we are facing ExtsysException: PUT cloud region 
to AAI failed. When we tried to debug, all request to MSB-IAG is resulting “Bad 
Gateway”.


 



 
 
 


The external port getting exposed to msb-iag is in CLOSE_WAIT state. Please 
help in resolving the port issue and to proceed VIM registration.


 


Regards,


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

Re: [onap-discuss] VIM registration failure

[li.zi30]

Hi Kiruthiga,





Could you please try to call the orginal API of AAI with 
https://{{}AAI1_PUB_IP}}:8443/aai/v11/cloud-infrastructure/cloud-region/{cloud-owner}/{cloud-region-id}
 and make sure the AAI is start normally. 

 



Thanks,


LiZi











原始邮件



发件人： ;
收件人：李滋00164331;
抄送人： ;
日 期 ：2018年02月01日 19:45
主 题 ：RE: [onap-discuss]  VIM registration failure




Hi LiZi,


 


Both AAI and Multicloud services are registered in MSB. But still we are 
getting the same error mentioned in the below mail.


 


All the request to MSB API is resulting in “Bad Gateway error”.  The external 
port of MSB-IAG server is either in CLOSE_WAIT or TIME_WAIT status while 
triggering  MSB API calls. If you could see in the error screenshot, during VIM 
registration request is sent to MSB-IAG server and it gives “Bad Gateway 
error”. Please help in fixing this issue.


 


Regards,


Kiruthiga



 



From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn] 
 Sent: Thursday, February 1, 2018 4:36 PM
 To: Kiruthiga R 
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] VIM registration failure




 



This message was identified as a phishing scam.



Feedback

Hi Kiruthiga,

Before you register VIM with ESR GUI, you need register the AAI's service to 
MSB. Also, you need register Multi-Cloud to MSB. You may check the registration 
result with MSB GUI (http://MSB_SERVER_IP/iui/microservices/default.html).  If 
they are not registered, please register with the following command.

 

curl -X POST \

-H "Content-Type: application/json" \

-d '{"serviceName": "aai-cloudInfrastructure", "version": "v11", "url": 
"/aai/v11/cloud-infrastructure","protocol": "REST", "enable_ssl":"true", 
"visualRange":"1", "nodes": [ {"ip": "ESR_SERVER_IP","port": "8443"}]}' \

http://MSB_SERVER_IP:10081/api/microservices/v1/services 

 

curl -X POST -H “Content-Type: application/json” -d ‘{“serviceName”: 
“multicloud”, “version”: “v0”, “url”: “/api/multicloud/v0”,”protocol”: “REST”, 
“nodes”: [ {“ip”: “’$MultiCloud_IP’”,”port”: “9001”}]}’ 
“http://$MSB_SERVER_IP:10081/api/microservices/v1/services“ 

 

Thanks,

LiZi

 

 


原始邮件



发件人： ;



收件人： ;



日 期 ：2018年02月01日 17:55



主 题 ：[onap-discuss]  VIM registration failure




___
 onap-discuss mailing list
 onap-discuss@lists.onap.org
 
https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.onap.org%2fmailman%2flistinfo%2fonap%2ddiscuss=CAD20441-6424-9305-A7AC-9253E32E6B5F=f63efd9aed1e0a367f4bd39381444e47841a5725-599b5ddaa682f840307a6cbf4482e982d884cbe8
 
  


Hi Team,


 


We have installed Amsterdam release of ONAP. We were successfully able to 
demonstrate vFW heat template based instantiation. We are currently working on 
TOSCA based E2E service  instantiation. We have a customer vCER CSAR file with 
which  we were able to create and distribute network and E2E service. We were 
able to onboard vnf and ns packages using usecase-UI. While trying to do VIM 
registration through ESR GUI, we are facing ExtsysException: PUT cloud region 
to AAI failed. When we tried to debug, all request to MSB-IAG is resulting “Bad 
Gateway”.


 



 
 
 


The external port getting exposed to msb-iag is in CLOSE_WAIT state. Please 
help in resolving the port issue and to proceed VIM registration.


 


Regards,


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

Re: [onap-discuss] Global JJB Sonar jobs are now in production.

[Jessica Wagantall]

+ ONAP release

Dear ONAP team,

Following up with this task, I have made sure all Sonar jobs ran at least
once.
I fixed few infra issues and here are the latest issues we got:

*Compilation/Dependency error:*
https://jenkins.onap.org/view/01-all-sonar/job/aai-aai-servi
ce-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/aai-rest-clie
nt-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/clamp-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/policy-engine-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/vvp-jenkins-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/ccsdk-distrib
ution-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/vnfsdk-
compliance-sonar/2/console
https://jenkins.onap.org/view/01-all-sonar/job/usecase-ui-sonar/2/

*Need plugin version changes:*
https://jenkins.onap.org/view/01-all-sonar/job/aai-sparky-fe-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/ccsdk-platfor
m-plugins-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/ccsdk-storage
-pgaas-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/dcaegen2-plat
form-configbinding-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/oom-registrat
or-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/oparent-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/ui-dmaapbc-sonar/2/console

*Test failures:*
https://jenkins.onap.org/view/01-all-sonar/job/aai-traversal-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/policy-common-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/policy-drools
-pdp-sonar/1/console
https://jenkins.onap.org/view/01-all-sonar/job/appc-sonar/1/console


I am looking into the plugin version job failures and should be a matter or
making the updates in
the pom files for some of them.

Please look into your job's compilations/test failures and let me know for
any questions

Thanks a ton!
Jess


On Thu, Feb 1, 2018 at 1:00 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> wrote:

> Dear ONAP team,
>
> As few of you pointed out, after creating our amsterdam branch, we started
> seeing some issues
> in Sonar after the scans were trying to get processed for this branch as
> well as master. As you might
> know, Sonar does not have a concept of branching and hence we decided to
> focus our scans to just
> the master branch.
>
> Our gerrit-maven-sonar job from global-jjb takes care of handling this
> properly. This is why, we have
> now switched from using our internal Sonar task (from
> release_version_java_daily jobs) to use the
> one LF team developed in global-jjb.
>
> This is the reference change if you want to take a look at it:
> https://gerrit.onap.org/r/#/c/29561/
>
> All Sonar jobs are now located in the following view:
> https://jenkins.onap.org/view/01-all-sonar/
> These jobs are scheduled to run every Saturday but anyone can run it in
> demand after posting a
> comment "run-sonar" in your Gerrit change.
>
> I am running all of them once and detecting any failures to make sure we
> are on track.
>
> Please let me know for any questions!
> Thanks!
> Jess
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [vnfsdk] VNF SDK Meeting Agenda for 2/2/18

[Brian Hedstrom]

Team,

Agenda for tomorrow's VNF SDK Meeting is posted at:

https://wiki.onap.org/display/DW/VNF+SDK+02-02-2018+Meeting


Thanks

-- 
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oam.technology
brian.hedst...@oamtechnologies.com
720-470-7091
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration] ONAP S3P Testing Tools

[Yunxia Chen]

Hi, team,

I have created 4 stories related to S3P tools investigation:
INT-408: JMeter
INT-409: Locust
INT-410: JProfile
INT-411: Chaos Monkey

I know Ran is working JProfile, therefore I have assign INT-410 to him. And 
assigned Locust to Gary. Could anyone pick up JMeter and Chaos Monkey?

You could find the tasks description inside the story.

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

[onap-discuss] Global JJB Sonar jobs are now in production.

[Jessica Wagantall]

Dear ONAP team,

As few of you pointed out, after creating our amsterdam branch, we started
seeing some issues
in Sonar after the scans were trying to get processed for this branch as
well as master. As you might
know, Sonar does not have a concept of branching and hence we decided to
focus our scans to just
the master branch.

Our gerrit-maven-sonar job from global-jjb takes care of handling this
properly. This is why, we have
now switched from using our internal Sonar task (from
release_version_java_daily jobs) to use the
one LF team developed in global-jjb.

This is the reference change if you want to take a look at it:
https://gerrit.onap.org/r/#/c/29561/

All Sonar jobs are now located in the following view:
https://jenkins.onap.org/view/01-all-sonar/
These jobs are scheduled to run every Saturday but anyone can run it in
demand after posting a
comment "run-sonar" in your Gerrit change.

I am running all of them once and detecting any failures to make sure we
are on track.

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

[onap-discuss] Inaugural Meetup 02/09/2018 - Open Source Networking Bay Area User Group

[HU, BIN]

Hello communities of LFN,

We are very excited to announce our Open Source Networking Bay Area User 
Group's Inaugural Meetup of the 2018 New Year, which will be held on Friday, 
02/09/2018 and hosted by Lumina Networks.

-  Date/Time: 12:30pm-4:00pm, Friday February 9th.

-  Venue: Lumina Networks, 2055 Gateway Place, 1st Floor Training Room, 
San Jose, CA.

We will start with a special guest presentation, in which you will receive 
insights from Verizon, who recently joined ONAP, on building a programmable 
network infrastructure using open source SDN technology. We will also talk 
about OpenDaylight (ODL) and its new offerings on Oxygen and upcoming Flourine 
release, how ONAP can orchestrate workloads into multiple clouds, container 
networking for Kubernetes (K8s), and learn about a new tool from OPNFV 
Lab-as-a-Service.

For more details, please visit and RSVP at 
https://www.meetup.com/Open-Source-Networking-User-Group-Bay-Area/events/246581633/.

Come. Connect. Enjoy. FREE FOOD AND DRINKS.

Thank you

Bin Hu
Co-Organizer, Open Source Networking Bay Area User Group

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

Re: [onap-discuss] [integration] Problem with install ONAP on vagrant

[Morales, Victor]

+Michael

Can you help us to solve this issue, apparently the error is located in the way 
OOM is installing these services[1], I’m not sure if we change it to don’t 
iterate over every service

Regards
Victor Morales

[1] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib/oom#n194


From: yanghc 
Date: Thursday, February 1, 2018 at 2:45 AM
To: Victor Morales , "onap-discuss@lists.onap.org" 

Subject: RE: [onap-discuss] [integration] Problem with install ONAP on vagrant

Hi Victor,

After changing the value of the parameter  in etc/settings.yaml file as you 
recommended and re-installing oom, the  Rancher and Kubernetes Dashboards can 
be accessed now.

It looks like the installation try to install  these onap apps : “consul msb 
mso message-router sdnc vid robot portal policy appc aai sdc dcaegen2 log cli 
multicloud clamp vnfsdk uui aaf vfc kube2msb”.
But some apps (like port, appc, clamp…) didn’t installed. Please see the 
attached for more detail.

Could you please help me to solve it ?

$ grep Error vagrant_libvirt-3.out
oom: Error: error installing: an error on the server ("Service 
unavailable") has prevented the request from succeeding (post 
deployments.extensions)
oom: Error: image onap/vfc/ztevnfmdriver:v1.0.2 not found
oom: Error parsing reference: "2.0.0-SNAPSHOT:latest" is not a valid 
repository/tag
oom: Error parsing reference: "Always:latest" is not a valid repository/tag
oom: Error: image onap/org.onap.dcaegen2.deployments.bootstrap:latest not 
found
oom: Error: image library/v1.1.0:latest not found
oom: Error parsing reference: "Always:latest" is not a valid repository/tag
oom: Error: image onap/refrepo:latest not found
oom: Error: image library/latest:latest not found
oom: Error: image onap/data-router:latest not found
oom: Error: image onap/search-data-service:latest not found
oom: Error: image onap/sparky-be:latest not found
oom: Error: parse error in "mso/templates/db-deployment-configmap.yaml": 
template: mso/templates/db-deployment-configmap.yaml:8: function "tpl" not 
defined
oom: Error: parse error in "sdnc/templates/sdnc-log-configmap.yaml": 
template: sdnc/templates/sdnc-log-configmap.yaml:8: function "tpl" not defined
oom: Error: parse error in "portal/templates/portal-logs-configmap.yaml": 
template: portal/templates/portal-logs-configmap.yaml:8: function "tpl" not 
defined
oom: Error: parse error in 
"policy/templates/policy-deployment-secret.yaml": template: 
policy/templates/policy-deployment-secret.yaml:9: function "tpl" not defined
oom: Error: parse error in "appc/templates/appc-conf-configmap.yaml": 
template: appc/templates/appc-conf-configmap.yaml:8: function "tpl" not defined
oom: Error: parse error in "clamp/templates/clamp-mariadb-configmap.yaml": 
template: clamp/templates/clamp-mariadb-configmap.yaml:8: function "tpl" not 
defined


Best regards,
慧卿

From: Morales, Victor [mailto:victor.mora...@intel.com]
Sent: Tuesday, January 30, 2018 6:09 AM
To: yanghc ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [integration] Problem with install ONAP on vagrant

Hey Yang,

Regarding the first error, usually I get the same error when I have leftovers 
from previous executions and most of the times they are solved when $ vagrant 
destroy command is executed [1]. The second execution printed a message about 
building ONAP Docker images from source code and this building process has not 
implemented yet [2], we have collected most of the build instructions in 
separated files and it’s necessary to call all these get_*_images functions 
from there. Anyway, there is a way to control the workflow of the vagrant-onap 
tool thru persistent configuration values or parameters [3], Shashank made a 
great job explaining these concepts with examples [4].  So, for OOM you have to 
choose the following values in etc/settings.yaml file:

build_image: "False"
skip_install: "False"

At this point you should be able to access to the Rancher and Kubernetes 
Dashboards using their port forwarded ports[5], but nothing has been deployed 
there yet given the default configuration values.

Regards/Saludos
Victor Morales

PS: You can also control the verbosity level of the execution thru the “debug” 
value in the settings file.

[1] 
https://git.onap.org/integration/tree/bootstrap/vagrant-onap/tools/run.sh#n99
[2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib/oom#n166
[3] 
http://onap.readthedocs.io/en/latest/submodules/integration.git/bootstrap/vagrant-onap/doc/source/features/configure_execution.html
[4] 
http://onap.readthedocs.io/en/latest/submodules/integration.git/bootstrap/vagrant-onap/doc/source/features/example_usage.html
[5] 
https://git.onap.org/integration/tree/bootstrap/vagrant-onap/Vagrantfile#n162


From: yanghc >
Date: Monday, 

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

[HU, JUN NICOLAS]

Hi Michael , Huabing

Here is the reason why Kube2MSB failed in RBAC enabled cluster.

The kube2MSB  will use the token from service account kube-system:default. This 
service account doesn't have the admin privileges.

To fix that issue there are 2 ways


1.   Create a clusterrolebinding assign admin privileges to that service 
account



Just run following command:
kubectl create clusterrolebinding kube-system-default-admin-binding 
--clusterrole=cluster-admin --serviceaccount=kube-system:default

This command should execute once. Should we put it in 
createConfig.sh
 ?


2.   Instead of using token from service account kube-system:default,  
kube2msb can use the token form service account onap-kube2msb:default .

In 
createAll.bash
  the ClusterRoleBinding is created for onap-kube2msb:default. So that account 
already get the admin privileges.



Change the kube-system to $1-$2


  
87
   # assign default auth token
  
88
   if [[ -z $ONAP_DEFAULT_AUTH_TOKEN ]]; then
  
89
 DEFAULT_SECRET=`kubectl get secrets -n kube-system | grep default-token |  
awk '{ print $1}'`
  
90
 ONAP_DEFAULT_AUTH_TOKEN=`kubectl get secrets $DEFAULT_SECRET -n 
kube-system -o yaml | grep  'token:'  | awk '{ print $2}' | base64 --decode`
  
91
   fi
  
92
  
93
   cmd=`echo helm install $LOCATION/$2/ --name $1-$2 --namespace $1 --set 
nsPrefix=$1,nodePortPrefix=$3,kubeMasterAuthToken=$ONAP_DEFAULT_AUTH_TOKEN 
${HELM_VALUES_ADDITION}`
  
94
   eval ${cmd}
  
95
   check_return_code $cmd

Thanks,
Nicolas


[centos@server-186-kubernetes-master-host-8z2tnf robot]$ kubectl get 
ClusterRoleBinding onap-kube2msb-admin-binding -o yaml
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  creationTimestamp: 2018-01-30T20:18:49Z
  name: onap-kube2msb-admin-binding
  resourceVersion: "159146"
  selfLink: 
/apis/rbac.authorization.k8s.io/v1/clusterrolebindings/onap-kube2msb-admin-binding
  uid: c838ff8d-05fa-11e8-bad9-fa163efe5022
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: default
  namespace: onap-kube2msb


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of HU, JUN NICOLAS
Sent: Wednesday, January 31, 2018 12:06 PM
To: OBRIEN, FRANK MICHAEL ; onap-discuss@lists.onap.org
Subject: [onap-discuss] [OOM][MSB] Kube2MSB RBAC security issues

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hi,

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

The Kube2MSB cannot access the apis of pods and services.

Thanks,
Nicolas

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

Re: [onap-discuss] [multicloud][container] container API design document for R2 (was Re: [multicloud] kick off design discussions for R2)

[Isaku Yamahata]

I uploaded spec at
https://gerrit.onap.org/r/#/c/30027/

For now I'm borrowing other JIRA item because JIRA item isn't created.
Once it's created I'll update issue id.

Thanks,

On Thu, Feb 01, 2018 at 09:28:13AM -0800,
Isaku Yamahata  wrote:

> BTW, is it better to submit it as spec for multicloud repo?
> 
> Thanks,
> 
> On Thu, Feb 01, 2018 at 09:13:34AM -0800,
> Isaku Yamahata  wrote:
> 
> > Hello.
> > 
> > I uploaded API design document for container at 
> > https://wiki.onap.org/display/DW/Multicloud+API+design+for+K8s+for+Beijing%3A+work-in-progress
> > So that we can discuss its API design. feedback/comments please.
> > NOTE: This is draft/work-in-progress so that it's open to discussion.
> > 
> > Thanks,
> > 
> > On Mon, Jan 22, 2018 at 05:58:48AM +,
> > Xinhui Li  wrote:
> > 
> > > Hi,
> > > 
> > > Thanks for your contribution to Multi Cloud along the time. We will 
> > > trigger a series of review/discussion meetings on MVP features and 
> > > stretch goals. I need the help from the owners of all features/stories 
> > > (assigned with Jira tickets) to prepare accordingly. Please draft a spec 
> > > document under the repo path: framework/docs/specs/
> > > 
> > > Please refer to this link for more details,  
> > > https://gerrit.onap.org/r/#/c/28755/1/docs/specs/README.rst
> > > 
> > > 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
> > 
> > 
> > -- 
> > Isaku Yamahata 
> 
> -- 
> Isaku Yamahata 
> 

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

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

[Elie Dit Cosaque, David (Nokia - US/Irving)]

Hi Seb, Yury,

We finally have found a working openssl command:

openssl aes-128-ecb -K aa3871669d893c7fb8abbcda31b88b4f   -e -in in.txt -out 
out_ecb.txt

in.txt: contains the data to encrypt, in our case 
Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U

The encrypted output (out_ecb.txt) is in binary format so I used the bless hex 
editor to copy the value. 

After changing the encrypted password, we see no authentication error and can 
get the list of services from SDC. 

I was expecting CLAMP GUI to somehow retrieve the clamp policies from the 
policy VM and present them in the CLAMP designer with an option to start/stop. 
Do we need to create a template and model ? Do you know about a procedure on 
how to do this for the vFWCL demo.

Thanks,
David.
 

-Original Message-
From: Elie Dit Cosaque, David (Nokia - US/Irving) 
Sent: Wednesday, January 31, 2018 3:27 PM
To: 'Determe, Sebastien' ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

Thanks Seb and Yuri

Could you please share the complete openssl command line to generate the 
encrypted password. Our SDC password is Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=
So base64 decoded:
vid:Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U

How can we get the encrypted hex from 
Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U? I always end up with padding error 
when I try (I have done many tries ☹).

Thanks,
David.

-Original Message-
From: Determe, Sebastien [mailto:sd3...@intl.att.com]
Sent: Wednesday, January 31, 2018 2:17 PM
To: Elie Dit Cosaque, David (Nokia - US/Irving) 
; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [sdc][integration][clamp] Clamp error connecting to 
SDC

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



Sent from my Samsung Galaxy smartphone.


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

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

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

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

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

Seb

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

Hi Sebastien,

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

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

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

Thanks,
David.

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

==> /opt/clamp/log/CLAMP/debug.log <==
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|DEBUG|c.a.a.c.logging.PerformanceTracking|In...:logTracker
2018-01-31T15:42:28,557Z||7a-8810-6ae7247a9c74|INFO|c.a.a.c.logging.PerformanceTracking|Performance
 Log:

Re: [onap-discuss] [multicloud][container] container API design document for R2 (was Re: [multicloud] kick off design discussions for R2)

[Isaku Yamahata]

BTW, is it better to submit it as spec for multicloud repo?

Thanks,

On Thu, Feb 01, 2018 at 09:13:34AM -0800,
Isaku Yamahata  wrote:

> Hello.
> 
> I uploaded API design document for container at 
> https://wiki.onap.org/display/DW/Multicloud+API+design+for+K8s+for+Beijing%3A+work-in-progress
> So that we can discuss its API design. feedback/comments please.
> NOTE: This is draft/work-in-progress so that it's open to discussion.
> 
> Thanks,
> 
> On Mon, Jan 22, 2018 at 05:58:48AM +,
> Xinhui Li  wrote:
> 
> > Hi,
> > 
> > Thanks for your contribution to Multi Cloud along the time. We will trigger 
> > a series of review/discussion meetings on MVP features and stretch goals. I 
> > need the help from the owners of all features/stories (assigned with Jira 
> > tickets) to prepare accordingly. Please draft a spec document under the 
> > repo path: framework/docs/specs/
> > 
> > Please refer to this link for more details,  
> > https://gerrit.onap.org/r/#/c/28755/1/docs/specs/README.rst
> > 
> > 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
> 
> 
> -- 
> Isaku Yamahata 

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

[onap-discuss] [multicloud][container] container API design document for R2 (was Re: [multicloud] kick off design discussions for R2)

[Isaku Yamahata]

Hello.

I uploaded API design document for container at 
https://wiki.onap.org/display/DW/Multicloud+API+design+for+K8s+for+Beijing%3A+work-in-progress
So that we can discuss its API design. feedback/comments please.
NOTE: This is draft/work-in-progress so that it's open to discussion.

Thanks,

On Mon, Jan 22, 2018 at 05:58:48AM +,
Xinhui Li  wrote:

> Hi,
> 
> Thanks for your contribution to Multi Cloud along the time. We will trigger a 
> series of review/discussion meetings on MVP features and stretch goals. I 
> need the help from the owners of all features/stories (assigned with Jira 
> tickets) to prepare accordingly. Please draft a spec document under the repo 
> path: framework/docs/specs/
> 
> Please refer to this link for more details,  
> https://gerrit.onap.org/r/#/c/28755/1/docs/specs/README.rst
> 
> 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


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

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

[morgan.richomme]

OK let's use this slot

I am not sure to undertand the time table, shall we understand that the meeting 
is planned on Tuesday the 6th 2 PM - 3 PM UTC ? with lots of // meetings? and 
conflict with the integration weekly meeting?

/Morgan

Le mercredi 31 janvier 2018 à 17:11 +0800, Chengli Wang a écrit :
Hi All,

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

Chengli


在 2018年1月31日，上午2:13，Yunxia Chen 
> 写道：

Hi, Morgan,
That’s the great news. What does Orange lab plan to offer to the community?  
Could you please call a 30 minutes working session to sort this out with the 
following people?
• Chengli Wang
• Rich Bennett
• Gary Wu
• Gildas Lanilis
• Stephen Gooch

They all on the “To” list as well. Let’s not duplicate the content. I am fine 
with either way you guys come out.

Regards,

Helen Chen

From: "morgan.richo...@orange.com" 
>
Date: Tuesday, January 30, 2018 at 8:34 AM
To: "bin.y...@windriver.com" 
>, Kang Xi 
>, Helen Chen 00725961 
>, 
"wangchen...@chinamobile.com" 
>, 
"ran.pol...@amdocs.com" 
>, 
"lxin...@vmware.com" 
>, "ROSE, DANIEL V" 
>, Gary Wu 
>, "Yang Xu (Yang, Fixed 
Network)" >, "PLATANIA, MARCO 
(MARCO)" >, yangyi 
>, 
"spondon...@att.com" 
>
Cc: Eric Debeau >, 
BLAISONNEAU David IMT/OLN 
>, 
onap-discuss >
Subject: [onap-discuss] [integration][OpenLab] Orange Open labs + integration 
repos


Hi Helen



regarding my action point

#AP 4: morgan_orange check with Eric on the Orange Open Lab schedule (when 
could we communicate at teh community level)



I am pleased to announce that the Orange Open Lab will be open on the 14th of 
February after some internal tests currently in progress.



I was wondering if if would make sense to create new repos to manage that

- integration/installation to host heat related activities

- integration/tests to host testing

- integration/infrastructure to manage the different labs

- integration/tooling



Note for the testing part I would even suggest to split it into

integration/functestional_tests (or functest :))

integration/benchmark



having only 1 repo will be misleading

If so my colleague David could push the code we are currently using to automate 
the creation of accounts for remote access (ansible roles) to an ONAP rebound.

And I assume it will be also the right place for Tlab owner to share stuff.



is it also up to the integration project to manage the federation of labs, as 
far as I understand there is also a comittee dealing with that?

if so I would suggest to reference somewhere (in integration/infrastructure for 
example) the IPs of the different labs

in order to easily tune the FW rules and let ONAP open lab discuss one with the 
others.

May I add a topic on this for next week?



/Morgan

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this 

Re: [onap-discuss] Delete a VF module , if two VF modules have been created!

[Shubhra Garg]

Hi Team,


Basically, I am looking for a cleaned delete of VF module from the main ONAP 
component.

Rather than an unfinished delete ( VF module got deleted from one component, 
still the data is present with another module ).

Kindly help!

Best Regards,
Shubhra


From: Shubhra Garg
Sent: Thursday, February 1, 2018 9:11 PM
To: onap-discuss@lists.onap.org; onap-...@lists.onap.org
Subject: Delete a VF module , if two VF modules have been created!


Hi Team,

I was trying to create a VF module after performing SDNC preload operation 
operation for SINK.

But, I entered the wrong vnf ID and performed the preload operation for SINK 
again and tried to create another/second vf module.

On onap wiki, I somewhere read that only one VF module is supported as of now.

I ran a curl query to check in MSO, it shows both the VF modules and the 
respective errors for the same.

But, now If I have to delete one VF module , then should I delete it from AAI 
or MSO or VID or all three?

Could you please help in picking the right component ( MSO, AAI , VID , SDC ) 
and the right DELETE curl query for the same.


I am not sure what I should put for resource path.

Trying to formulate a curl query for deleting a VF module:

GET 
/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}

GET 
/network/generic-vnfs/generic-vnf/46aa2fcb-bddd-442c-a4a7-b2b843e8161b/vf-modules/vf-module/a219c5fb-bf1f-4874-8876-30a16cb17122



DELETE 
/network/generic-vnfs/generic-vnf/46aa2fcb-bddd-442c-a4a7-b2b843e8161b/vf-modules/vf-module/a219c5fb-bf1f-4874-8876-30a16cb17122


serverRoot = https://{FQDN}:{Port}/ecomp/mso/infra/{resourcePath}


DELETE 
https://{FQDN}:{Port}/ecomp/mso/infra/{resourcePath}/serviceInstances/v2/{serviceInstanceId}/vnfs/{vnfInstanceId}/vfModules/{vfmoduleinstance-id}


Curl query to MSO ( shows two VF modules):
root@ubuntu:/home/infy_user/curl_queries_json# curl -X GET 
http://127.0.0.1:30223/ecomp/mso/infra/orchestrationRequests/v2/ -H 'Accept: 
application/json' -H 'Authorization: Basic 
SW5mcmFQb3J0YWxDbGllbnQ6cGFzc3dvcmQxJA==' -H 'Content-Type: application/json' 
-H 'X-FromAppId: Postman' | python -m json.tool
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  78560  78560 0  68323  0 --:--:-- --:--:-- --:--:-- 68912
{
"requestList": [
{
"request": {
"instanceReferences": {
"requestorId": "demo",
"serviceInstanceId": "955f5d8a-0e6d-4605-8efc-19c4dac1c921",
"serviceInstanceName": "vFW-vSINK-service-instance1"
},
"requestDetails": {
"modelInfo": {
"modelInvariantId": 
"fc742f77-955d-4ebb-bb02-3322929eaa17",
"modelName": "vFW-vSINK-service",
"modelType": "service",
"modelVersion": "1.0",
"modelVersionId": "df599415-6ed3-480b-b48c-6f5b83ddaf7b"
},
"requestInfo": {
"instanceName": "vFW-vSINK-service-instance1",
"requestorId": "demo",
"source": "VID",
"suppressRollback": false
},
"requestParameters": {
"aLaCarte": true,
"autoBuildVfModules": false,
"cascadeDelete": false,
"rebuildVolumeGroups": false,
"subscriptionServiceType": "vFWCL",
"usePreload": true
},
"subscriberInfo": {
"globalSubscriberId": "Demonstration"
}
},
"requestId": "6d11958f-27da-44e1-8390-53ea04a1bde5",
"requestScope": "service",
"requestStatus": {
"finishTime": "Thu, 01 Feb 2018 13:01:00 GMT",
"percentProgress": 100,
"requestState": "COMPLETE",
"statusMessage": "Service Instance was created 
successfully."
},
"requestType": "createInstance",
"startTime": "Thu, 01 Feb 2018 13:00:35 GMT"
}
},
{
"request": {
"instanceReferences": {
"requestorId": "demo",
"serviceInstanceId": "955f5d8a-0e6d-4605-8efc-19c4dac1c921",
"vnfInstanceId": "46aa2fcb-bddd-442c-a4a7-b2b843e8161b",
"vnfInstanceName": "vFW-vSINK-VNF-instance"
},
"requestDetails": {
"cloudConfiguration": {
"lcpCloudRegionId": "RegionOne",
   

[onap-discuss] Delete a VF module , if two VF modules have been created!

[Shubhra Garg]

Hi Team,

I was trying to create a VF module after performing SDNC preload operation 
operation for SINK.

But, I entered the wrong vnf ID and performed the preload operation for SINK 
again and tried to create another/second vf module.

On onap wiki, I somewhere read that only one VF module is supported as of now.

I ran a curl query to check in MSO, it shows both the VF modules and the 
respective errors for the same.

But, now If I have to delete one VF module , then should I delete it from AAI 
or MSO or VID or all three?

Could you please help in picking the right component ( MSO, AAI , VID , SDC ) 
and the right DELETE curl query for the same.


I am not sure what I should put for resource path.

Trying to formulate a curl query for deleting a VF module:

GET 
/network/generic-vnfs/generic-vnf/{vnf-id}/vf-modules/vf-module/{vf-module-id}

GET 
/network/generic-vnfs/generic-vnf/46aa2fcb-bddd-442c-a4a7-b2b843e8161b/vf-modules/vf-module/a219c5fb-bf1f-4874-8876-30a16cb17122



DELETE 
/network/generic-vnfs/generic-vnf/46aa2fcb-bddd-442c-a4a7-b2b843e8161b/vf-modules/vf-module/a219c5fb-bf1f-4874-8876-30a16cb17122


serverRoot = https://{FQDN}:{Port}/ecomp/mso/infra/{resourcePath}


DELETE 
https://{FQDN}:{Port}/ecomp/mso/infra/{resourcePath}/serviceInstances/v2/{serviceInstanceId}/vnfs/{vnfInstanceId}/vfModules/{vfmoduleinstance-id}


Curl query to MSO ( shows two VF modules):
root@ubuntu:/home/infy_user/curl_queries_json# curl -X GET 
http://127.0.0.1:30223/ecomp/mso/infra/orchestrationRequests/v2/ -H 'Accept: 
application/json' -H 'Authorization: Basic 
SW5mcmFQb3J0YWxDbGllbnQ6cGFzc3dvcmQxJA==' -H 'Content-Type: application/json' 
-H 'X-FromAppId: Postman' | python -m json.tool
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  78560  78560 0  68323  0 --:--:-- --:--:-- --:--:-- 68912
{
"requestList": [
{
"request": {
"instanceReferences": {
"requestorId": "demo",
"serviceInstanceId": "955f5d8a-0e6d-4605-8efc-19c4dac1c921",
"serviceInstanceName": "vFW-vSINK-service-instance1"
},
"requestDetails": {
"modelInfo": {
"modelInvariantId": 
"fc742f77-955d-4ebb-bb02-3322929eaa17",
"modelName": "vFW-vSINK-service",
"modelType": "service",
"modelVersion": "1.0",
"modelVersionId": "df599415-6ed3-480b-b48c-6f5b83ddaf7b"
},
"requestInfo": {
"instanceName": "vFW-vSINK-service-instance1",
"requestorId": "demo",
"source": "VID",
"suppressRollback": false
},
"requestParameters": {
"aLaCarte": true,
"autoBuildVfModules": false,
"cascadeDelete": false,
"rebuildVolumeGroups": false,
"subscriptionServiceType": "vFWCL",
"usePreload": true
},
"subscriberInfo": {
"globalSubscriberId": "Demonstration"
}
},
"requestId": "6d11958f-27da-44e1-8390-53ea04a1bde5",
"requestScope": "service",
"requestStatus": {
"finishTime": "Thu, 01 Feb 2018 13:01:00 GMT",
"percentProgress": 100,
"requestState": "COMPLETE",
"statusMessage": "Service Instance was created 
successfully."
},
"requestType": "createInstance",
"startTime": "Thu, 01 Feb 2018 13:00:35 GMT"
}
},
{
"request": {
"instanceReferences": {
"requestorId": "demo",
"serviceInstanceId": "955f5d8a-0e6d-4605-8efc-19c4dac1c921",
"vnfInstanceId": "46aa2fcb-bddd-442c-a4a7-b2b843e8161b",
"vnfInstanceName": "vFW-vSINK-VNF-instance"
},
"requestDetails": {
"cloudConfiguration": {
"lcpCloudRegionId": "RegionOne",
"tenantId": "d626273afd214d0b85ba991ef7131768"
},
"modelInfo": {
"modelCustomizationId": 
"f93ad831-6215-4a3b-ac55-42928fa2d573",
"modelCustomizationName": "vFW-vSINK 0",
"modelInvariantId": 
"e8417b7a-4913-43af-923e-eb6881a76451",
"modelName": "vFW-vSINK",
"modelType": "vnf",
"modelVersion": 

[onap-discuss] [DCAEGEN2][Integration]DCAEGEN2 Manual Installation Status and issues

[Thiruveedula, Bharath via onap-discuss]

Greetings


I am trying to setup DCAEGGEN2 using manual installation approach. The
environment I am using is behind the proxy. So for installing DCAEGEN2 I
have to do lot of workarounds to make it work(though I haven't reached that
state). Here are the steps I took just to make centos VM  up.



1.  As Designate service is not running in my ONAP installed openstack, we
are supposed to  create one surrogate openstack and add those details in
dnsaas_*.txt in dcae_bootstrap VM



2. We have to make sure that "tenant name" and "region name" of both
openstack should be same.



3. If you are using keystone v3 for any of the openstack make sure the
domain name should match the domain name in AAI payload while registering
pod25 and pod25dns . If you are using "*Default*" domain name, then all is
well :)



4. If you are behind proxy, we should pass proxy variables while running
boot container. Please find my docker run command below:


*docker run -d  --name boot -v /opt/app/config:/opt/app/installer/config -v
/etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt -e
"CLOUDIFY_SSL_TRUST_ALL=true"  -e "no_proxy=127.0.0.1," -e
"http_proxy=:80" -e
REQUESTS_CA_BUNDLE="/etc/ssl/certs/ca-certificates.crt" -e "https_proxy= *
*** :80"  -e "PYTHONHTTPSVERIFY=0 "   -e "LOCATION=MYGL"
"nexus3.onap.org:10001/onap/org.onap.dcaegen2.deployments.bootstrap:v1.1.1.3
"
/opt/app/installer/installer*



*5.  *For all SSL based errors refer
https://jira.onap.org/browse/DCAEGEN2-218. Thanks Elena



6. And if you are using v3 for main openstack and it is baed on SSL, you
have to tweak the multicloud code. Find the tweak below.

   - *Login to multi service VM and login to  **multicloud-windriver
   container*
   - *Open  /opt/windriver/lib/newton/newton/requests/views/util.py*
   - *Change  "return session.Session(auth=auth)" to "return
   session.Session(auth=auth, verify=Fals)*"

7. If you make it through to launch "centos_vm" that's the first relief.
But make sure your centos_vm should have "centos" user, if not present then
it won't proceed. The approach I used is to change "SSHUSER" in
*installer *file
in boot container and commit the image with new version and update
dcae2_vm_init.sh file with updated docker image name



8. The next blocker is the following line


"*PVTIP=$(ssh $SSHOPTS -i "$PVTKEY" "$SSHUSER"@"$PUBIP" 'echo PVTIP=`curl
--silent http://169.254.169.254/2009-04-04/meta-data/local-ipv4`
' | grep PVTIP |
sed 's/PVTIP=//')*"


If you are using proxy, set no_proxy for  "*169.254.169.254" *for example:


"*PVTIP=$(ssh $SSHOPTS -i "$PVTKEY" "$SSHUSER"@"$PUBIP" ' **export
no_proxy=$no_proxy,169.254.169.254;**echo PVTIP=`curl --silent
http://169.254.169.254/2009-04-04/meta-data/local-ipv4`
' | grep PVTIP |
sed 's/PVTIP=//')*"


9. boot container launches centos_vm with some cloud-init. Now if you want
to have successful installation of cloudinit scripts I need to add proxy
details. It seems like a rabbit hole for me. Currently I block here with
the following logs:



2018-02-01 12:42:27 CFY  [elasticsearch_1eb63.creation] Sending
task 'fabric_plugin.tasks.run_script'

2018-02-01 12:42:27 CFY  [amqp_influx_895ee.creation] Task started
'fabric_plugin.tasks.run_script'

2018-02-01 12:42:27 LOG  [amqp_influx_895ee.creation] INFO:
Preparing fabric environment...

2018-02-01 12:42:27 LOG  [amqp_influx_895ee.creation] INFO:
Environment prepared successfully

[floating_ip] out: Traceback (most recent call last):

[floating_ip] out:   File "/tmp/cloudify-ctx/ctx", line 139, in 

[floating_ip] out: main()

[floating_ip] out:   File "/tmp/cloudify-ctx/ctx", line 128, in main

[floating_ip] out: args.timeout)

[floating_ip] out:   File "/tmp/cloudify-ctx/ctx", line 84, in client_req

[floating_ip] out: response = request_method(socket_url, request,
timeout)

[floating_ip] out:   File "/tmp/cloudify-ctx/ctx", line 65, in
http_client_req

[floating_ip] out: timeout=timeout)

[floating_ip] out:   File "/usr/lib64/python2.7/urllib2.py", line 127, in
urlopen

[floating_ip] out: return _opener.open(url, data, timeout)

[floating_ip] out:   File "/usr/lib64/python2.7/urllib2.py", line 410, in
open

[floating_ip] out: response = meth(req, response)

[floating_ip] out:   File "/usr/lib64/python2.7/urllib2.py", line 523, in
http_response

[floating_ip] out: 'http', request, response, code, msg, hdrs)

[floating_ip] out:   File "/usr/lib64/python2.7/urllib2.py", line 448, in
error

[floating_ip] out: return self._call_chain(*args)

[floating_ip] out:   File "/usr/lib64/python2.7/urllib2.py", line 382, in
_call_chain

[floating_ip] out: result = func(*args)

[floating_ip] out:   File "/usr/lib64/python2.7/urllib2.py", line 531, in
http_error_default

[floating_ip] out: raise 

[onap-discuss] [modeling] ONAP IM discussion call Feb. 1st meeting notes

[yangxu (H)]

Hi,

Thank you all for joining the call!

Here’s the meeting notes:
1) Focus on the word document for now:
- Identify the parts that could be stable before M2 and try to reach consensus
- Word doc format: IFA011(ETSI) like format
- Process: reach consensus in meeting calls, and then move the consensus part 
to the wiki (IM clean version page)

2) Working on papyrus after M2 milestone:
- Need to agree on the guidelines first
- Candidate: IISOMI papyrus guideline
- Suggest everyone to review the guideline, invite Nigel to have a presentation 
on the modeling subcommittee call

3) Task calls for IM discussion:
- Agree on two time slots to have IM discussion calls to accelerate the process
- Slot 1: 8 am US eastern (9 pm Beijing) Mon.
- Slot 2: 8 am US eastern (9 pm Beijing) Wed.
- Zoom id: 9117271979
- May use one or both slots according to the working process

4) Plan for the next call:
- Feb. 7 (Slot 2 above)
- Scope: try to agree on the VNFD top level and VDU models
- To do:
   - Kevin will help update the doc and wiki regarding the above parts
   - Lingli will help provide more feedback

Hope all interested people could join the following calls and help building the 
ONAP information model!

Best regards,
Xu Yang
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] VIM registration failure

[Kiruthiga R]

Hi LiZi,

Both AAI and Multicloud services are registered in MSB. But still we are 
getting the same error mentioned in the below mail.

All the request to MSB API is resulting in “Bad Gateway error”.  The external 
port of MSB-IAG server is either in CLOSE_WAIT or TIME_WAIT status while 
triggering MSB API calls. If you could see in the error screenshot, during VIM 
registration request is sent to MSB-IAG server and it gives “Bad Gateway 
error”. Please help in fixing this issue.

Regards,
Kiruthiga

From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn]
Sent: Thursday, February 1, 2018 4:36 PM
To: Kiruthiga R 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] VIM registration failure


This message was identified as a phishing 
scam.

Feedback


Hi Kiruthiga,

Before you register VIM with ESR GUI, you need register the AAI's service to 
MSB. Also, you need register Multi-Cloud to MSB. You may check the registration 
result with MSB GUI (http://MSB_SERVER_IP/iui/microservices/default.html). If 
they are not registered, please register with the following command.



curl -X POST \

-H "Content-Type: application/json" \

-d '{"serviceName": "aai-cloudInfrastructure", "version": "v11", "url": 
"/aai/v11/cloud-infrastructure","protocol": "REST", "enable_ssl":"true", 
"visualRange":"1", "nodes": [ {"ip": "ESR_SERVER_IP","port": "8443"}]}' \

http://MSB_SERVER_IP:10081/api/microservices/v1/services



curl -X POST -H “Content-Type: application/json” -d ‘{“serviceName”: 
“multicloud”, “version”: “v0”, “url”: “/api/multicloud/v0”,”protocol”: “REST”, 
“nodes”: [ {“ip”: “’$MultiCloud_IP’”,”port”: “9001”}]}’ 
“http://$MSB_SERVER_IP:10081/api/microservices/v1/services“



Thanks,

LiZi




原始邮件
发件人： >;
收件人： >;
日 期 ：2018年02月01日 17:55
主 题 ：[onap-discuss]  VIM registration failure
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://imsva91-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2flists.onap.org%2fmailman%2flistinfo%2fonap%2ddiscuss=CAD20441-6424-9305-A7AC-9253E32E6B5F=f63efd9aed1e0a367f4bd39381444e47841a5725-599b5ddaa682f840307a6cbf4482e982d884cbe8


Hi Team,

We have installed Amsterdam release of ONAP. We were successfully able to 
demonstrate vFW heat template based instantiation. We are currently working on 
TOSCA based E2E service instantiation. We have a customer vCER CSAR file with 
which  we were able to create and distribute network and E2E service. We were 
able to onboard vnf and ns packages using usecase-UI. While trying to do VIM 
registration through ESR GUI, we are facing ExtsysException: PUT cloud region 
to AAI failed. When we tried to debug, all request to MSB-IAG is resulting “Bad 
Gateway”.

[cid:image001.jpg@01D39B7F.F7C08EA0]


The external port getting exposed to msb-iag is in CLOSE_WAIT state. Please 
help in resolving the port issue and to proceed VIM registration.

Regards,
Kiruthiga


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

Re: [onap-discuss] VIM registration failure

[li.zi30]

Hi Kiruthiga,


Before you register VIM with ESR GUI, you need register the AAI's service to 
MSB. Also, you need register Multi-Cloud to MSB. You may check the registration 
result with MSB GUI (http://MSB_SERVER_IP/iui/microservices/default.html). If 
they are not registered, please register with the following command.




curl -X POST \

-H "Content-Type: application/json" \

-d '{"serviceName": "aai-cloudInfrastructure", "version": "v11", "url": 
"/aai/v11/cloud-infrastructure","protocol": "REST", "enable_ssl":"true", 
"visualRange":"1", "nodes": [ {"ip": "ESR_SERVER_IP","port": "8443"}]}' \

http://MSB_SERVER_IP:10081/api/microservices/v1/services 




curl -X POST -H “Content-Type: application/json” -d ‘{“serviceName”: 
“multicloud”, “version”: “v0”, “url”: “/api/multicloud/v0”,”protocol”: “REST”, 
“nodes”: [ {“ip”: “’$MultiCloud_IP’”,”port”: “9001”}]}’ 
“http://$MSB_SERVER_IP:10081/api/microservices/v1/services“ 




Thanks,


LiZi











原始邮件



发件人： ;
收件人： ;
日 期 ：2018年02月01日 17:55
主 题 ：[onap-discuss]  VIM registration failure


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

  

Hi Team,


 


We have installed Amsterdam release of ONAP. We were successfully able to 
demonstrate vFW heat template based instantiation. We are currently working on 
TOSCA based E2E service instantiation. We have a customer vCER CSAR file with 
which  we were able to create and distribute network and E2E service. We were 
able to onboard vnf and ns packages using usecase-UI. While trying to do VIM 
registration through ESR GUI, we are facing ExtsysException: PUT cloud region 
to AAI failed. When we tried to debug, all request to MSB-IAG is resulting “Bad 
Gateway”.


 



 
 


The external port getting exposed to msb-iag is in CLOSE_WAIT state. Please 
help in resolving the port issue and to proceed VIM registration.


 


Regards,


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

[onap-discuss] VIM registration failure

[Kiruthiga R]

Hi Team,

We have installed Amsterdam release of ONAP. We were successfully able to 
demonstrate vFW heat template based instantiation. We are currently working on 
TOSCA based E2E service instantiation. We have a customer vCER CSAR file with 
which we were able to create and distribute network and E2E service. We were 
able to onboard vnf and ns packages using usecase-UI. While trying to do VIM 
registration through ESR GUI, we are facing ExtsysException: PUT cloud region 
to AAI failed. When we tried to debug, all request to MSB-IAG is resulting "Bad 
Gateway".

[cid:image002.jpg@01D39B70.C64CCA00]

The external port getting exposed to msb-iag is in CLOSE_WAIT state. Please 
help in resolving the port issue and to proceed VIM registration.

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