[onap-discuss] A Developer Environment Setup

[Thamlur Raju]

Hi,

In "createDBSchema", i am getting some errors in these logs.
I am sharing all, So Please check and give me some suggestion.


*metrics.log*
[image: Inline image 1]



*debug.log*

[image: Inline image 2]


*error.log*

[image: Inline image 3]

So Please suggest something on these errors.


Regards,

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

[onap-discuss] (no subject)

[Thamlur Raju]

Hi,

In "createDBSchema", i am getting some errors in these logs.
I am sharing all, So Please check and give me some suggestion.


*metrics.log*
[image: Inline image 1]



*debug.log*

[image: Inline image 2]


*error.log*

[image: Inline image 3]

So Please suggest something on these errors.


Regards,

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

[onap-discuss] [policy] PDP-X template

[Guo, Ruijing]

Hi, All,

From wiki, al policy templates come from policy/drools-applications:

https://wiki.onap.org/display/DW/Developing+Policy+Templates+and+Policy+Support+Code

From code, drools-applictions are PDP-D. My questions is:

Where is PDP-X template?

Thanks,

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

[onap-discuss] [SDC] Which daily build version in v1.1.0 of SDC can be setup on https://nexus3.onap.org?

[yuan.hu1]

Hi all,















I pull the latest docker images on 2017-08-15 from https://nexus3.onap.org. 



And expect to setup a SDC on my local host.


But, An error arised as follow while run the script of 'docker_run.sh'.


Can those docker images be working?


And, Who knows which version of SDC is available?






root@ubuntu:/home/sdc/docker/scripts# ./docker_run.sh


performing old dockers cleanup


docker run sdc-elasticsearch...


WARNING: Your kernel does not support swap limit capabilities or the cgroup is 
not mounted. Memory limited without swap.


0






docker run sdc-cassandra...


57e000e415b42958ed82403ff22702075a4e56a79c636d07d03a5cfe8bf73410


please wait while CS is starting...


0






docker run sdc-kibana...


WARNING: Your kernel does not support swap limit capabilities or the cgroup is 
not mounted. Memory limited without swap.


2055dd48b2333a7207e7f421cd11087555bf45ecc9e23928e10367046e97884a


docker run sdc-backend...


WARNING: Your kernel does not support swap limit capabilities or the cgroup is 
not mounted. Memory limited without swap.


8b77860a0ae78c7cb31dd876082cc546c34a293e048b785a33b592e29acb603c


please wait while BE is starting...


0






WARNING: Your kernel does not support swap limit capabilities or the cgroup is 
not mounted. Memory limited without swap.


449344feee7f8c3e1147476f705b934d179b90137eeff7087d73af9f5b81721c


Running health checks, please wait...


0






{


  "cluster_name" : "SDC-ES-Template",


  "status" : "green",


  "timed_out" : false,


  "number_of_nodes" : 1,


  "number_of_data_nodes" : 1,


  "active_primary_shards" : 0,


  "active_shards" : 0,


  "relocating_shards" : 0,


  "initializing_shards" : 0,


  "unassigned_shards" : 0,


  "delayed_unassigned_shards" : 0,


  "number_of_pending_tasks" : 0,


  "number_of_in_flight_fetch" : 0,


  "task_max_waiting_in_queue_millis" : 0,


  "active_shards_percent_as_number" : 100.0


}


BE health-Check:











Error 503 








HTTP ERROR: 503


Problem accessing /sdc2/rest/healthCheck. Reason:


Service Unavailable


http://eclipse.org/jetty;>Powered by Jetty:// 
9.3.15.v20161220
















FE health-Check:


{


  "sdcVersion": "UNKNOWN",


  "siteMode": "UNKNOWN",


  "componentsInfo": [


{


  "healthCheckComponent": "FE",


  "healthCheckStatus": "UP",


  "version": "1.1.0-SNAPSHOT",


  "description": "OK"


},


{


  "healthCheckComponent": "BE",


  "healthCheckStatus": "DOWN"


},


{


  "healthCheckComponent": "TITAN",


  "healthCheckStatus": "UNKNOWN"


},


{


  "healthCheckComponent": "CASSANDRA",


  "healthCheckStatus": "UNKNOWN"


},


{


  "healthCheckComponent": "DE",


  "healthCheckStatus": "UNKNOWN"


},


{


  "healthCheckComponent": "ON_BOARDING",


  "healthCheckStatus": "UNKNOWN"


}


  ]


}






Error [12] while user existance check


root@ubuntu:/home/sdc/docker/scripts# 







Thanks,



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

[onap-discuss] 答复: [usecaseui]: Any request for the VID team

[shentao]

Dear Catherine

 

Thanks for your kindly reminder :-)

For R1, Usecase UI is planning to support VoLTE LCM function and Monitor
(alarm and performance) display.

So I think there is no requirement which need VID to support.

Usecase UI would need dependency on SDC, SO, A, DCAE.

 

Best regards,

Tao

 

 

发件人: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] 代表 Lefevre, Catherine
发送时间: 2017年8月16日 22:53
收件人: onap-discuss@lists.onap.org
主题: [onap-discuss] [usecaseui]: Any request for the VID team

 

Good morning Use Case UI Team,

 

Have you any particular request that the VID team should consider as part of
their ONAP R1?

Thank you

 

Many thanks & regards

Catherine

 


Catherine Lefèvre

AT Network and Shared Services

D2 Platform & Systems Development

AVP Software Development & Engineering

ECOMP/ONAP/RUBY/SPP

 

 

Phone: +32 2 418 49 22

Mobile: +32 475 77 36 73

  catherine.lefe...@intl.att.com

 

TEXTING and DRIVING… It Can Wait

AT

BUROGEST OFFICE PARK SA

Avenue des Dessus-de-Lives, 2

5101 Loyers (Namur)

Belgium

 

 

NOTE: This email (or its attachments) contains information belonging to the
sender, which may be confidential. proprietary and/or legally privileged.
The information is intended only for the use of the individual(s) or
entity(ies) named above. If you are not the intended recipient, you are
hereby notified that any disclosure, distribution or taking of any action in
reliance on the content of this is strictly forbidden. If you have received
this e-mail in error please immediately notify the sender identified above

 

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

[onap-discuss] 答复: [DCAE] DCAE questions from Usecase UI

[shentao]

Dear Alla

Yes. We can support other use cases.
If we get UI requirements of additional use cases, I'd like to discuss them
with ONAPers.

Best regards,
Tao


-邮件原件-
发件人: Alla Goldner [mailto:alla.gold...@amdocs.com] 
发送时间: 2017年8月16日 20:50
收件人: shentao; 'GILBERT, MAZIN E (MAZIN E)'
抄送: onap-discuss@lists.onap.org
主题: RE: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi Tao,

So, I guess, we resolved one outstanding issue for vVoLTE support!

One question - with this design in place, I guess, it will not be difficult
to support additional use cases UI, am I right?

 Best regards, 

Alla Goldner

Open Network Division 
Amdocs Technology





-Original Message-
From: shentao [mailto:shen...@chinamobile.com] 
Sent: Wednesday, August 16, 2017 2:12 PM
To: 'GILBERT, MAZIN E (MAZIN E)' ; Alla Goldner

Cc: onap-discuss@lists.onap.org
Subject: 答复: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi, Mazin and Alla

I have discussed this issue with Lusheng and reached an agreement.
The solution is that Usecase UI will get alarm and performance data via
Dmaap and support data storage.
So it isn't difficult to display alarm and performance data by UI.
Thanks for your attention.

Best regards,
Tao


-邮件原件-
发件人: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] 代表 GILBERT, MAZIN E (MAZIN E)
发送时间: 2017年8月14日 23:02
收件人: Alla Goldner
抄送: onap-discuss@lists.onap.org
主题: Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

I would like to understand how much of the work is app specific to VoLTE. We
really should leverage any UI across all use cases especially if it is
generating custom platform work. I will wait for the PTLs to share more
info.

Thanks
Mazin 

Sent through AT's fastest network 

> On Aug 14, 2017, at 5:43 AM, Alla Goldner  wrote:
> 
>  



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] Open lab meeting now

[wangchen...@chinamobile.com]

Hi Tina,

WindRiver Developer lab has some update, you know they extend  their lab and 
setup a dedicated pod for ONAP community. As Stephen said, it will be ready by 
the end of this week.
For T-lab,It is a pity that we don't have any update from AT 


 
From: Tina Tsou
Date: 2017-08-17 03:01
To: Chengli Wang
CC: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Open lab meeting now
Dear Chengli,
 
Thank you for getting back to me.
 
Brian H. and I have some questions for Open Lab team.
What is the status on the WindRiver Dev2Dev lab and the T-lab?
Have they been fully specified?
Have these labs and their specifications/status been discussed in the OpenLab 
subcommittee?
 
If yes, would you share the URL here?
 
 
Thank you,
Tina Tsou
Enterprise Architect
Arm
tina.t...@arm.com
+1 (408)931-3833
 
From: Chengli Wang [mailto:wangchen...@chinamobile.com] 
Sent: Wednesday, August 16, 2017 8:47 AM
To: Tina Tsou 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Open lab meeting now
 
Hi Tina,
 
Open Lab meeting is proposed to cancelled this week. 
I have sent mail to notify our members and Kenny to update the invitation, not 
CC the discuss list. 
Sorry for the inconvenience.
 
And here is open lab meeting info for your reference, linked 
https://wiki.onap.org/display/DW/Open+Lab+Subcommittee
Welcome to join us next time.
 
Regards,
Chengli
NOTE: new bridge effective Aug. 9 2017
ONAP Meeting 2 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/615870381
Or iPhone one-tap (US Toll): +16465588656,,615870381# or 
+14086380968,,615870381#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 615 870 381
International numbers available: 
https://zoom.us/zoomconference?m=hGkbISp-a_TaLndBGJVpEY6LoEgVnnjE
 
 
 
在 2017年8月16日，下午11:17，Tina Tsou  写道：
 
Dear all,

Which meeting ID is valid for the Open Lab meeting now?


Thank you,
Tina
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
 
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you. 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] About ESR VIM registration API

[li.zi30]

Hi Bin,




ESR will check the status of VIM after the VIM been registered and then it will 
check every 15 minutes. But the time period will be configurable.




BR,

LiZi



















原始邮件



发件人： 
收件人：李滋00164331 
抄送人： 
日 期 ：2017年08月17日 08:28
主 题 ：RE: [onap-discuss] About ESR VIM registration API







Hi Lizi,


 


   How often does ESR check the status of VIM status? Is it a 
periodically task or just at the time of registration? Thanks


 


Best Regards,


Bin Yang,Solution Readiness Team,Wind River


Direct +86,10,84777126Mobile +86,13811391682Fax +86,10,64398189


Skype: yangbincs993


 


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of li.z...@zte.com.cn
 Sent: Wednesday, August 16, 2017 4:07 PM
 To: ethanly...@vmware.com
 Cc: onap-discuss@lists.onap.org
 Subject: Re: [onap-discuss] About ESR VIM registration API


 

 

Hi Ethan,

 

I will modify the VIM related API according to the schema in A, including 
the data structure and url. and I will remove the name/description properties.

 

FYI, I suggest we add a "status" property in cloud-region. Because ESR will 
check whether the cloud is reachable, and update the status to A How do you 
think?

 

BR,

LiZi

 

 

 


原始邮件



发件人： 



收件人：李滋00164331



抄送人： 



日 期 ：2017年08月16日 13:19



主 题 ：About ESR VIM registration API




 


Hi Li Zi,



   I just go through the wiki page about VIM registration API . 
https://wiki.onap.org/pages/viewpage.action?pageId=11930343#A:ExternalSystemRegisterAPIDefinition(draft)-VIM



   In the cloud-region schema, it doesn’t provide fields to store ‘name’ and 
‘description’ yet. Maybe we could remove them?



 



 


Best Regards,



Ethan Lynn



ethanly...@vmware.com



+86 010-59934270___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Facing issues with policy setup with Vagrant

[Guo, Ruijing]

Right. If you don’t use vagrant, there is small env diff like software version, 
IP address so that you need to modify the script.

If you use socks5 proxy instead of http-proxy, you can use script from 
following to avoid editing dockerfile:


1.  git clone http://gerrit.onap.org/gerrit/r/demo

2.  demo/vagrant/setup_proxy.sh (can setup proxy for all applications)

I just go through policy tutorial: 
https://wiki.onap.org/display/DW/Deploying+and+Debugging+the+Policy+Platform

I can update policy by followings (not in tutorial):


1.  sudo docker exec -ti pdp bash

2.  cd /tmp/policy-install/config

3.  bash ./push-policies.sh


From: viswanath.kumarskandpr...@verizon.com 
[mailto:viswanath.kumarskandpr...@verizon.com]
Sent: Wednesday, August 16, 2017 9:54 PM
To: Guo, Ruijing ; 'DRAGOSH, PAMELA L (PAM)' 
; Atul Shegokar 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Facing issues with policy setup with Vagrant


Thanks Ruijing. I had to do minor changes in your script to have it run in my 
environment..

  *   ​​ For some reason docker-compose via pip install didn't work. So used 
docker-compose binary directly ( sudo
  *   curl -o /usr/local/bin/docker-compose -L 
"https://github.com/docker/compose/releases/download/1.15.0/docker-compose-$(uname
  *   -s)-$(uname -m)")
  *   Patched settings.xml to work through corporate proxy
  *   Added switches in between script to pause & wait for my action to proceed.
  *   I had to manually edit each Dockerfile to add proxy configurations in 
/etc/apt/apt.conf as well. Simply exporting HTTP_PROXY didn't help in my case.

With above modifications, I was able to be see them running now. I had to 
manually do the stuffs in for loop to make it work in my env ( mainly due to 
corporate proxy :( ).

BTW after having all these dockers up, how am I supposed to use Policy GUI to 
create / edit / apply any policy?
Could you help me with this info?

BR,
Viswa

From: Guo, Ruijing >
Sent: Wednesday, August 16, 2017 6:14 PM
To: Kumar Skand Priya, Viswanath V; 'DRAGOSH, PAMELA L (PAM)'; Atul Shegokar
Cc: onap-discuss@lists.onap.org
Subject: [E] RE: [onap-discuss] Facing issues with policy setup with Vagrant

Hi,

Vagrant/virtualbox need virtualization support. you can setup policy from 
Ubuntu 16.04 VM/Bare Metal without vagrant/virtualbox:


1.  Setup sudo without password in Ubuntu 16.04 VM/Bare Metal

2.  Git clone 
http://gerrit.onap.org/r/policy/docker

3.  Patch from 
https://gerrit.onap.org/r/#/c/7719/
 (still in review)

4.  Change 192.168.0.10 in docker/vagrant/setup_policy.sh to interface IP 
address in your Ubuntu 16.04 VM/Bare Metal

5.  Run setup_policy.sh

I will remove hardcoded IP address. So you can just run setup_policy.sh

Thanks,
-Ruijing


From: 
viswanath.kumarskandpr...@verizon.com
 [mailto:viswanath.kumarskandpr...@verizon.com]
Sent: Wednesday, August 16, 2017 7:52 PM
To: 'DRAGOSH, PAMELA L (PAM)' 
>; Atul Shegokar 
>; Guo, Ruijing 
>
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Facing issues with policy setup with Vagrant

I’m also facing similar issue. Although, going through Google, I learnt that 
nested virtualization is not supported. Apparently, I’m running a Ubuntu VM in 
openstack and I’m trying to use vagrant to power-up V-Box inside that Ubuntu.

Is there any much simpler approach to bring up entire policy component in 
single VM? The READ.ME from 
http://gerrit.onap.org/r/policy/docker
 suggest to build individual mvn projects starting from 
“policy-common-modules”, but I couldn’t see that dir in my cloned repo.

Also, 

Re: [onap-discuss] About ESR VIM registration API

[Yang, Bin]

Hi Lizi,

   How often does ESR check the status of VIM status? Is it a 
periodically task or just at the time of registration? Thanks

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

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of li.z...@zte.com.cn
Sent: Wednesday, August 16, 2017 4:07 PM
To: ethanly...@vmware.com
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] About ESR VIM registration API




Hi Ethan,



I will modify the VIM related API according to the schema in A, including 
the data structure and url. and I will remove the name/description properties.



FYI, I suggest we add a "status" property in cloud-region. Because ESR will 
check whether the cloud is reachable, and update the status to A How do you 
think?



BR,

LiZi






原始邮件
发件人： >;
收件人：李滋00164331;
抄送人： >;
日 期 ：2017年08月16日 13:19
主 题 ：About ESR VIM registration API


Hi Li Zi,
   I just go through the wiki page about VIM registration API . 
https://wiki.onap.org/pages/viewpage.action?pageId=11930343#A:ExternalSystemRegisterAPIDefinition(draft)-VIM
   In the cloud-region schema, it doesn’t provide fields to store ‘name’ and 
‘description’ yet. Maybe we could remove them?


Best Regards,
Ethan Lynn
ethanly...@vmware.com
+86 010-59934270








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

Re: [onap-discuss] Facing issues with policy setup with Vagrant

[Morales, Victor]

Viswa,

The steps that you mention below were implemented into vagrant-onap script, so 
maybe something they can be reused

Thanks
Victor Morales

From:  on behalf of Viswanath Kumar Skand 
Priya via onap-discuss 
Reply-To: "viswanath.kumarskandpr...@verizon.com" 

Date: Wednesday, August 16, 2017 at 8:53 AM
To: "Guo, Ruijing" , "'DRAGOSH, PAMELA L (PAM)'" 
, Atul Shegokar 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Facing issues with policy setup with Vagrant


Thanks Ruijing. I had to do minor changes in your script to have it run in my 
environment..

  *   ​​ For some reason docker-compose via pip install didn't work. So used 
docker-compose binary directly ( sudo
  *   curl -o /usr/local/bin/docker-compose -L 
"https://github.com/docker/compose/releases/download/1.15.0/docker-compose-$(uname
  *   -s)-$(uname -m)")
https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib/functions#n180

  *   Patched settings.xml to work through corporate proxy
https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib/_onap_functions#n46

  *   Added switches in between script to pause & wait for my action to proceed.
  *   I had to manually edit each Dockerfile to add proxy configurations in 
/etc/apt/apt.conf as well. Simply exporting HTTP_PROXY didn't help in my case.
https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib/functions#n104

With above modifications, I was able to be see them running now. I had to 
manually do the stuffs in for loop to make it work in my env ( mainly due to 
corporate proxy :( ).

BTW after having all these dockers up, how am I supposed to use Policy GUI to 
create / edit / apply any policy?
Could you help me with this info?

BR,
Viswa

From: Guo, Ruijing 
Sent: Wednesday, August 16, 2017 6:14 PM
To: Kumar Skand Priya, Viswanath V; 'DRAGOSH, PAMELA L (PAM)'; Atul Shegokar
Cc: onap-discuss@lists.onap.org
Subject: [E] RE: [onap-discuss] Facing issues with policy setup with Vagrant

Hi,

Vagrant/virtualbox need virtualization support. you can setup policy from 
Ubuntu 16.04 VM/Bare Metal without vagrant/virtualbox:


1.  Setup sudo without password in Ubuntu 16.04 VM/Bare Metal

2.  Git clone 
http://gerrit.onap.org/r/policy/docker

3.  Patch from 
https://gerrit.onap.org/r/#/c/7719/
 (still in review)

4.  Change 192.168.0.10 in docker/vagrant/setup_policy.sh to interface IP 
address in your Ubuntu 16.04 VM/Bare Metal

5.  Run setup_policy.sh

I will remove hardcoded IP address. So you can just run setup_policy.sh

Thanks,
-Ruijing


From: viswanath.kumarskandpr...@verizon.com 
[mailto:viswanath.kumarskandpr...@verizon.com]
Sent: Wednesday, August 16, 2017 7:52 PM
To: 'DRAGOSH, PAMELA L (PAM)' ; Atul Shegokar 
; Guo, Ruijing 
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Facing issues with policy setup with Vagrant

I’m also facing similar issue. Although, going through Google, I learnt that 
nested virtualization is not supported. Apparently, I’m running a Ubuntu VM in 
openstack and I’m trying to use vagrant to power-up V-Box inside that Ubuntu.

Is there any much simpler approach to bring up entire policy component in 
single VM? The READ.ME from 
http://gerrit.onap.org/r/policy/docker
 suggest to build individual mvn projects starting from 
“policy-common-modules”, but I couldn’t see that dir in my cloned repo.

Also, 
https://wiki.onap.org/pages/viewpage.action?pageId=11929334
 page explains about 

Re: [onap-discuss] Facing issues with policy setup with Vagrant

[Morales, Victor]

Hey there,

Apparently, the error message is saying that virtualization feature is 
disabled, you can verify it running in the host machine running

$ egrep ‘(vmx|svm)’ /proc/cpuinfo

In the other hand, if that computer was provisioned by OpenStack, the Compute 
node where that instance is hosted has to support nested virtualization which 
can be enabled the proper kernel module.


· 
https://docs.openstack.org/devstack/latest/guides/devstack-with-nested-kvm.html

I haven’t tried to use the scripts isolated (there are plans to document and 
test that in the future) but maybe this can work

$ git clone https://git.onap.org/integration
$ mv integration/bootstrap/vagrant-onap/lib /var/onap
$ source /var/onap/policy
$ init_policy

Regards,
Victor Morales

From:  on behalf of Viswanath Kumar Skand 
Priya via onap-discuss 
Reply-To: "viswanath.kumarskandpr...@verizon.com" 

Date: Wednesday, August 16, 2017 at 6:51 AM
To: "'DRAGOSH, PAMELA L (PAM)'" , Atul Shegokar 
, "Guo, Ruijing" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Facing issues with policy setup with Vagrant

I’m also facing similar issue. Although, going through Google, I learnt that 
nested virtualization is not supported. Apparently, I’m running a Ubuntu VM in 
openstack and I’m trying to use vagrant to power-up V-Box inside that Ubuntu.

Is there any much simpler approach to bring up entire policy component in 
single VM? The READ.ME from http://gerrit.onap.org/r/policy/docker suggest to 
build individual mvn projects starting from “policy-common-modules”, but I 
couldn’t see that dir in my cloned repo.

Also, https://wiki.onap.org/pages/viewpage.action?pageId=11929334 page explains 
about building PDP but not entire policy component.

Could you somebody from policy team shed some light on development env setup?

BR,
Viswa

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DRAGOSH, PAMELA L 
(PAM)
Sent: Wednesday, August 16, 2017 5:13 PM
To: Atul Shegokar ; ruijing@intel.com
Cc: onap-discuss@lists.onap.org
Subject: [E] Re: [onap-discuss] Facing issues with policy setup with Vagrant

Atul,

Sorry that you are having issues. I don’t know what those errors are or where 
they come from. Perhaps Ruijing could help you, he setup the vagrant for Policy.

Not sure if you saw this wiki or if it would help:

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


Regards,

Pam

From: 
>
 on behalf of Atul Shegokar 
>
Date: Wednesday, August 16, 2017 at 4:31 AM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] Facing issues with policy setup with Vagrant

HI team,

I am trying to make setup for policy using vagrant. When I try to use vagrant 
up command, it gives an error saying VT-x is not available (VERR_VMX_NO_VMX).

I have already made below checks –

1)   VT-x AMD-V rea active in VM.

2)   VT-x is enabled in BIOS.

3)   Hyper-V is disabled and system rebooted (it was checked earlier).

Please guide help, if there are any other possible reasons which are affecting 
vagrant up command working.



Thanks & Regards,
Atul Shegokar













Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at 
http://www.techmahindra.com/Disclaimer.html
 externally 
http://tim.techmahindra.com/tim/disclaimer.html
 internally within TechMahindra.

[onap-discuss] CSIT Test Case Review for M3

[Yunxia Chen]

Hi, Gildas,

From M3 checklist, I saw this item:
Have you reviewed all the Test Case with Integration Team?

yes

Schedule a meeting with Integration Team to review the deliverable.


Currently, Integration team is helping each project on their CSIT setup, we 
have wiki and video for how to do it:
https://wiki.onap.org/display/DW/Creating+a+CSIT+Test

But since we will be very busy on implementing some cross projects / pair 
projects CSITs and E2E Lab implementation, I am afraid that Integration team 
will become the bottleneck for M3. Could we remove this item, instead, we 
depend on PTLs to decide whether they have their core functionalities covered 
in their CSIT or not?

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

Re: [onap-discuss] [ONAP Helpdesk #44125] Independent project artifact release process

[Gary Wu via RT]

Hi Andy,

Thanks for your feedback.  I would like to do a trial run of this process with 
oparent and document the instructions.

To confirm, is the preferred way to do a staging build via the 
"-release-version-java-daily" jobs?  Do we currently have any documentation on 
how to setup/use the staging build jobs?  For example, I think it requires a 
version.properties file to be defined in the repo; not sure if there are other 
requirements.

For the GPG signed tag, do we have any recommended instructions for the project 
committers/PTLs to do so themselves, or should we assume that LFRE will take 
care of this for the time being?

Thanks,
Gary


-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, August 16, 2017 11:59 AM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: Re: [ONAP Helpdesk #44125] Independent project artifact release process

Greetings Gary,

On 08/16/2017 11:34 AM, Gary Wu via RT wrote:

> Resending since I didn't get a ticket number back for some reason last time.

Not certain why you didn't. The original ticket, which I've merged this into is 
44125

> From: Gary Wu
> Sent: Wednesday, August 09, 2017 12:37 PM
> To: 'helpd...@onap.org' 
> Cc: onap-discuss@lists.onap.org
> Subject: [integration] Independent project artifact release process
> 
> Hi helpdesk,
> 
> ONAP is moving toward a model where each project/repo will be 
> releasing its own artifacts and versions, and cross-repo dependencies 
> are on release artifacts only (i.e. no SNAPSHOT/staging dependencies).
> Integration will be piloting this with oparent and clamp repos to work 
> out all the kinks.
> 
> To that end, we will need a clear process for individual projects to 
> version bump and release their own artifacts.
> 
> ONAP currently has Jenkins job definitions that will deploy release 
> artifact candidates to staging. What seems to be missing is a way for 
> a project to pick a candidate from staging and formally release it 
> into the Releases repo. Does this process exist? If so, can you point 
> me to some documentation on how this process works? If not, can you 
> share your thoughts on how we can best implement this last step?

The closest we currently have is the process that OpenDaylight has been 
operating with for their odlparent project which as of the current release 
cycle has broken off to doing independent releases of it's one.
In fact during the Nitrogen cycle it's already had at least 4 releases that I'm 
aware of!

The current process that has been in use in ODL by odlparent is detailed in the 
lead mail in this [0] mailing list thread.

LF is working on ways that the we can grant more of the process control to the 
projects themselves but we don't currently have everything needed for it just 
yet.

To get the heart of your request the current way for an ONAP project to 
formally do a release at present would be as follows:

1) A staging build has happened. In the job logs there will be a notice as to 
what the staging repository that was created is. This needs to be captured by a 
project committer / PTL that will be requesting a release

2) Any testing that needs to be performed against the artifacts is performed.

3) A helpdesk ticket is opened requesting that LF Release Engineering perform a 
signing and release operation on the target staging repository

4) LFRE will pull the artifacts, GPG sign them, push a secondary staging 
repository with the signatures and then perform a release operation inside 
nexus which will cause it to transition both the requested staging repository 
and the signature repository to copy into the releases repository and then 
delete the staging repositories.

5) A GPG signed tag needs to be placed on the commit by either LFRE or 
preferably the PTL or a committer of the project with the release version

For docker images, we don't currently have as much automated tooling in place 
but the basic flow is:

1) Identify the STAGING docker slice that is to be released

2) Open a ticket with LF to release the specific docker

3) LFRE will pull the docker image and retag it into the nexus docker releases 
repository and push

4) The image should also then be pushed to dockerhub

Eventually, this will all get fully automated in some fashion with the correct 
checks and balances in place for restricting who can do what.
Once we have a good automation flow in place then it will probably be a matter 
of an authorized party submitting a gerrit change to a special repository / 
specially formatted comment to trigger Jenkins to perform operations on behalf 
of folks.

-Andy-

[0] https://lists.opendaylight.org/pipermail/dev/2017-August/003990.html

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation



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

Re: [onap-discuss] [ONAP Helpdesk #44125] Independent project artifact release process

[Gary Wu]

Hi Andy,

Thanks for your feedback.  I would like to do a trial run of this process with 
oparent and document the instructions.

To confirm, is the preferred way to do a staging build via the 
"-release-version-java-daily" jobs?  Do we currently have any documentation on 
how to setup/use the staging build jobs?  For example, I think it requires a 
version.properties file to be defined in the repo; not sure if there are other 
requirements.

For the GPG signed tag, do we have any recommended instructions for the project 
committers/PTLs to do so themselves, or should we assume that LFRE will take 
care of this for the time being?

Thanks,
Gary


-Original Message-
From: Andrew Grimberg via RT [mailto:onap-helpd...@rt.linuxfoundation.org] 
Sent: Wednesday, August 16, 2017 11:59 AM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: Re: [ONAP Helpdesk #44125] Independent project artifact release process

Greetings Gary,

On 08/16/2017 11:34 AM, Gary Wu via RT wrote:

> Resending since I didn't get a ticket number back for some reason last time.

Not certain why you didn't. The original ticket, which I've merged this into is 
44125

> From: Gary Wu
> Sent: Wednesday, August 09, 2017 12:37 PM
> To: 'helpd...@onap.org' 
> Cc: onap-discuss@lists.onap.org
> Subject: [integration] Independent project artifact release process
> 
> Hi helpdesk,
> 
> ONAP is moving toward a model where each project/repo will be 
> releasing its own artifacts and versions, and cross-repo dependencies 
> are on release artifacts only (i.e. no SNAPSHOT/staging dependencies).
> Integration will be piloting this with oparent and clamp repos to work 
> out all the kinks.
> 
> To that end, we will need a clear process for individual projects to 
> version bump and release their own artifacts.
> 
> ONAP currently has Jenkins job definitions that will deploy release 
> artifact candidates to staging. What seems to be missing is a way for 
> a project to pick a candidate from staging and formally release it 
> into the Releases repo. Does this process exist? If so, can you point 
> me to some documentation on how this process works? If not, can you 
> share your thoughts on how we can best implement this last step?

The closest we currently have is the process that OpenDaylight has been 
operating with for their odlparent project which as of the current release 
cycle has broken off to doing independent releases of it's one.
In fact during the Nitrogen cycle it's already had at least 4 releases that I'm 
aware of!

The current process that has been in use in ODL by odlparent is detailed in the 
lead mail in this [0] mailing list thread.

LF is working on ways that the we can grant more of the process control to the 
projects themselves but we don't currently have everything needed for it just 
yet.

To get the heart of your request the current way for an ONAP project to 
formally do a release at present would be as follows:

1) A staging build has happened. In the job logs there will be a notice as to 
what the staging repository that was created is. This needs to be captured by a 
project committer / PTL that will be requesting a release

2) Any testing that needs to be performed against the artifacts is performed.

3) A helpdesk ticket is opened requesting that LF Release Engineering perform a 
signing and release operation on the target staging repository

4) LFRE will pull the artifacts, GPG sign them, push a secondary staging 
repository with the signatures and then perform a release operation inside 
nexus which will cause it to transition both the requested staging repository 
and the signature repository to copy into the releases repository and then 
delete the staging repositories.

5) A GPG signed tag needs to be placed on the commit by either LFRE or 
preferably the PTL or a committer of the project with the release version

For docker images, we don't currently have as much automated tooling in place 
but the basic flow is:

1) Identify the STAGING docker slice that is to be released

2) Open a ticket with LF to release the specific docker

3) LFRE will pull the docker image and retag it into the nexus docker releases 
repository and push

4) The image should also then be pushed to dockerhub

Eventually, this will all get fully automated in some fashion with the correct 
checks and balances in place for restricting who can do what.
Once we have a good automation flow in place then it will probably be a matter 
of an authorized party submitting a gerrit change to a special repository / 
specially formatted comment to trigger Jenkins to perform operations on behalf 
of folks.

-Andy-

[0] https://lists.opendaylight.org/pipermail/dev/2017-August/003990.html

--
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation


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

Re: [onap-discuss] [integration][holmes] How to Get Dependencies like MySQL during the Building of the Dockers?

[Gary Wu]

Hi Guangrong,

The LF Jenkins slave VMs are freshly allocated for each job, and the VM images 
are not pre-loaded with any docker images; all the docker images are freshly 
pulled when they are needed.  The MySQL docker image is pretty small, so this 
shouldn’t be taking that long, but if needed probably the right thing to do is 
to get the mysql docker image cached in the ONAP nexus3 proxy.

If you feel that this is necessary, can you send a request to ONAP helpdesk for 
that?

Thanks,
Gary

From: fu.guangr...@zte.com.cn [mailto:fu.guangr...@zte.com.cn]
Sent: Tuesday, August 15, 2017 5:57 PM
To: Gary Wu 
Cc: onap-discuss@lists.onap.org
Subject: 答复: RE: RE: [onap-discuss] 答复: [integration][holmes] How to Get 
Dependencies like MySQL during the Building of the Dockers?


Gary,



Is there an existing MySQL docker image on the server which is used to perform 
the CSIT task? If no, would you please help to pull it to the server first? 
Otherwise we have to do it every time before we carry out our CSIT task, which 
is quite time-consuming.



I'm sorry that I can not check it by myself because I don't know how to connect 
to the CSIT server ( and I don't think I have the privilege to access it).



Thanks in advance.



Regards,

Guangrong








原始邮件
发件人： >;
收件人：付光荣10144542;
抄送人： >;
日 期 ：2017年08月16日 01:10
主 题 ：RE: RE: [onap-discuss] 答复: [integration][holmes] How to Get Dependencies 
like MySQL during the Building of the Dockers?


Hi Guangrong,

For CSIT, I would suggest that you start up the MySQL docker container in your 
setup.sh and pass its IP address to your microservice docker container via an 
environment  variable.

Thanks,
Gary

From: fu.guangr...@zte.com.cn 
[mailto:fu.guangr...@zte.com.cn]
Sent: Tuesday, August 15, 2017 2:14 AM
To: Gary Wu >
Cc: onap-discuss@lists.onap.org
Subject: 答复: RE: [onap-discuss] 答复: [integration][holmes] How to Get 
Dependencies like MySQL during the Building of the Dockers?


Thanks for your suggetion, Gary.



I have sent an email to the DCAE team to discuss about that. But the solution 
you suggested is specifically for the production environment. For development, 
especially for the CSIT purpose, we need the support  of MySQL to accomplish 
the FT tasks. Could the integration team help to find a way to achieve that?



Looking forward to your reply.



Best Regards,

Guangrong








原始邮件
发件人： >;
收件人：付光荣10144542;
抄送人： >;
日 期 ：2017年08月15日 01:09
主 题 ：RE: [onap-discuss] 答复: [integration][holmes] How to Get Dependencies like 
MySQL during the Building of the Dockers?


Hi Guangrong,

It depends on what your MySQL dependency looks like.

If your dependency is to store data in a running MySQL instance, it is 
recommended that you run a separate  MySQL container independently from the 
container for  your own microservice, and configure your microservice to 
communicate with that MySQL instance.  For this, you can use the docker 
container provided directly by MySQL: 
https://hub.docker.com/r/mysql/mysql-server/.  You should not run a MySQL 
instance directly within your own microservice docker container.

If you have dependencies on MySQL libraries in your code, then it’s recommended 
that you set that up  manually in your Dockerfile configuration scripts.

Thanks,
Gary



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
fu.guangr...@zte.com.cn
Sent: Sunday, August 13, 2017 5:51 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] 答复: [integration][holmes] How to Get Dependencies like 
MySQL during the Building of the Dockers?


Hi,



I have not heard any response so far. Could anybody please help to answer the 
question or give me any suggestion?



Thanks.



Guangrong








原始邮件
发件人：付光荣10144542
收件人： >;
日 期 ：2017年08月10日 22:09
主 题 ：[integration][holmes] How to Get Dependencies like MySQL during the 
Building of the Dockers?



Hi all,



While making dockers, we want to integrate MySQL as a part of our components. 
Do we have to pull it directly from the internet or is it stored in some place 
of ONAP so that we could fetch it from within?



Thanks.



Guangrong




















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

Re: [onap-discuss] Open lab meeting now

[Tina Tsou]

Dear Chengli,

Thank you for getting back to me.

Brian H. and I have some questions for Open Lab team.
What is the status on the WindRiver Dev2Dev lab and the T-lab?
Have they been fully specified?
Have these labs and their specifications/status been discussed in the OpenLab 
subcommittee?

If yes, would you share the URL here?


Thank you,
Tina Tsou
Enterprise Architect
Arm
tina.t...@arm.com
+1 (408)931-3833

From: Chengli Wang [mailto:wangchen...@chinamobile.com]
Sent: Wednesday, August 16, 2017 8:47 AM
To: Tina Tsou 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Open lab meeting now

Hi Tina,

Open Lab meeting is proposed to cancelled this week.
I have sent mail to notify our members and Kenny to update the invitation, not 
CC the discuss list.
Sorry for the inconvenience.

And here is open lab meeting info for your reference, linked 
https://wiki.onap.org/display/DW/Open+Lab+Subcommittee
Welcome to join us next time.

Regards,
Chengli
NOTE: new bridge effective Aug. 9 2017
ONAP Meeting 2 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/615870381
Or iPhone one-tap (US Toll): +16465588656,,615870381# or 
+14086380968,,615870381#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 615 870 381
International numbers available: 
https://zoom.us/zoomconference?m=hGkbISp-a_TaLndBGJVpEY6LoEgVnnjE



在 2017年8月16日，下午11:17，Tina Tsou > 写道：

Dear all,

Which meeting ID is valid for the Open Lab meeting now?


Thank you,
Tina
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [ONAP Helpdesk #44125] Independent project artifact release process

[Andrew Grimberg via RT]

Greetings Gary,

On 08/16/2017 11:34 AM, Gary Wu via RT wrote:

> Resending since I didn't get a ticket number back for some reason last time.

Not certain why you didn't. The original ticket, which I've merged this
into is 44125

> From: Gary Wu
> Sent: Wednesday, August 09, 2017 12:37 PM
> To: 'helpd...@onap.org' 
> Cc: onap-discuss@lists.onap.org
> Subject: [integration] Independent project artifact release process
> 
> Hi helpdesk,
> 
> ONAP is moving toward a model where each project/repo will be
> releasing its own artifacts and versions, and cross-repo dependencies
> are on release artifacts only (i.e. no SNAPSHOT/staging dependencies).
> Integration will be piloting this with oparent and clamp repos to work
> out all the kinks.
> 
> To that end, we will need a clear process for individual projects to
> version bump and release their own artifacts.
> 
> ONAP currently has Jenkins job definitions that will deploy release
> artifact candidates to staging. What seems to be missing is a way for a
> project to pick a candidate from staging and formally release it into
> the Releases repo. Does this process exist? If so, can you point me to
> some documentation on how this process works? If not, can you share your
> thoughts on how we can best implement this last step?

The closest we currently have is the process that OpenDaylight has been
operating with for their odlparent project which as of the current
release cycle has broken off to doing independent releases of it's one.
In fact during the Nitrogen cycle it's already had at least 4 releases
that I'm aware of!

The current process that has been in use in ODL by odlparent is detailed
in the lead mail in this [0] mailing list thread.

LF is working on ways that the we can grant more of the process control
to the projects themselves but we don't currently have everything needed
for it just yet.

To get the heart of your request the current way for an ONAP project to
formally do a release at present would be as follows:

1) A staging build has happened. In the job logs there will be a notice
as to what the staging repository that was created is. This needs to be
captured by a project committer / PTL that will be requesting a release

2) Any testing that needs to be performed against the artifacts is
performed.

3) A helpdesk ticket is opened requesting that LF Release Engineering
perform a signing and release operation on the target staging repository

4) LFRE will pull the artifacts, GPG sign them, push a secondary staging
repository with the signatures and then perform a release operation
inside nexus which will cause it to transition both the requested
staging repository and the signature repository to copy into the
releases repository and then delete the staging repositories.

5) A GPG signed tag needs to be placed on the commit by either LFRE or
preferably the PTL or a committer of the project with the release version

For docker images, we don't currently have as much automated tooling in
place but the basic flow is:

1) Identify the STAGING docker slice that is to be released

2) Open a ticket with LF to release the specific docker

3) LFRE will pull the docker image and retag it into the nexus docker
releases repository and push

4) The image should also then be pushed to dockerhub

Eventually, this will all get fully automated in some fashion with the
correct checks and balances in place for restricting who can do what.
Once we have a good automation flow in place then it will probably be a
matter of an authorized party submitting a gerrit change to a special
repository / specially formatted comment to trigger Jenkins to perform
operations on behalf of folks.

-Andy-

[0] https://lists.opendaylight.org/pipermail/dev/2017-August/003990.html

-- 
Andrew J Grimberg
Lead, IT Release Engineering
The Linux Foundation




binrzPHcH0pRW.bin
Description: application/rt-original-message
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Joint Architecture/Use Case meeting

[Christopher Donley (Chris)]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Christopher Donley (Chris):MAILTO:christopher.don...@huawei.co
 m
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alla Goldn
 er:MAILTO:alla.gold...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-arc@l
 ists.onap.org:MAILTO:onap-...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-useca
 se...@lists.onap.org:MAILTO:onap-usecase...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-tsc@l
 ists.onap.org:MAILTO:onap-...@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='onap-disc
 u...@lists.onap.org':MAILTO:onap-discuss@lists.onap.org
DESCRIPTION;LANGUAGE=en-US:Dear Architecture and Use Case subcommittees\,\n
 \nAlla and I would like to continue our joint ARC/Use Case meetings on Sep
 tember 7 at 1300 UTC. Please see the Zoom invitation below.\n\nChris & All
 a\n\n---\n\nHi there\,\n\n
 Chris Donley & Alla Goldner are inviting you to a scheduled Zoom meeting.\
 n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/43748053
 5\n\nOr iPhone one-tap (US Toll):  +16465588656\,\,437480535# or +16468769
 923\,\,437480535#\n\nOr Telephone:\nDial: +1 646 558 8656 (US Toll) or
  +1 646 876 9923 (US Toll)\nMeeting ID: 437 480 535\nInternational
  numbers available: https://zoom.us/zoomconference?m=mnKk1YCEnSSOS9SnLxFy2
 Tnd9JYqUR_a\n\n\n\n
SUMMARY;LANGUAGE=en-US:Joint Architecture/Use Case meeting
DTSTART;TZID=Pacific Standard Time:20170907T06
DTEND;TZID=Pacific Standard Time:20170907T07
UID:04008200E00074C5B7101A82E00810F4D9887B16D301000
 010003133856474F68041B8DB4146A73975DD
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170816T173635Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/437480535
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1871742945
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [OOM] Kubernetes version to be used as reference

[Doucerain, Jerome]

Hi,


as we are using kubernetes to run ONAP containers, we are developing kubernetes 
manifests to describe the resources required by the ONAP components and the 
environment where we are running them on.


Some kubernetes resources we are referring to in the manifests are valid only 
in some kubernetes versions or the way to refer to those resources is specific 
to particular versions, taking into account the evolution as the kubernetes API.


So to keep the valuable material the community is bringing valid as long as 
possible, and as we are at the beginning of the ONAP on kubernetes story, my 
proposal would be to try to start with the most recent stable version of 
kubernetes (i.e. 1.7) and base the kubernetes manifests on the version 1.7 API 
reference.



It will also allow us to use the latest features of kubernetes to operate ONAP.


Could you please give some feedback on that.


Thanks


Jerome


Jerome Doucerain
Sr Consultant - System Architecture
Bell Business Markets
671, LaGauchetière Ouest, 5e
Montréal (Québec) H3B 2M8
Office : 514 870-6392
jerome.doucer...@bell.ca
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [VNFRQTS] Requirements format - VNFRQTS-23

[WRIGHT, STEVEN A]

Per the discussion on yesterday's call, I've created a daughter page for this 
discussion at : 
https://wiki.onap.org/display/DW/VNFRQTS+Requirement+Format+discussion

Please add your comments or update the page as appropriate.


To help move this along, I have put this as an agenda item for next week's call 
:
https://wiki.onap.org/pages/viewpage.action?pageId=10783589

it would be good to nail some of this down next week so we can tee up the 
consequential (and more substantive)  editing tasks for Sprint-3


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

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

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

[onap-discuss] aai-core package

[aditya g]

Hi All,

I don't find the package org.openecomp.aai.domain.yang. There is any references 
to this package in aa-core.

Regards
Aditya

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

Re: [onap-discuss] Open lab meeting now

[Chengli Wang]

Hi Tina,

Open Lab meeting is proposed to cancelled this week. 
I have sent mail to notify our members and Kenny to update the invitation, not 
CC the discuss list. 
Sorry for the inconvenience.

And here is open lab meeting info for your reference, linked 
https://wiki.onap.org/display/DW/Open+Lab+Subcommittee 

Welcome to join us next time.

Regards,
Chengli
NOTE: new bridge effective Aug. 9 2017
ONAP Meeting 2 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/615870381 

Or iPhone one-tap (US Toll): +16465588656,,615870381# or 
+14086380968,,615870381#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
+1 855 880 1246 (US Toll Free)
+1 877 369 0926 (US Toll Free)
Meeting ID: 615 870 381
International numbers available: 
https://zoom.us/zoomconference?m=hGkbISp-a_TaLndBGJVpEY6LoEgVnnjE 




> 在 2017年8月16日，下午11:17，Tina Tsou  写道：
> 
> Dear all,
> 
> Which meeting ID is valid for the Open Lab meeting now?
> 
> 
> Thank you,
> Tina
> IMPORTANT NOTICE: The contents of this email and any attachments are 
> confidential and may also be privileged. If you are not the intended 
> recipient, please notify the sender immediately and do not disclose the 
> contents to any other person, use it for any purpose, or store or copy the 
> information in any medium. Thank you.
> ___
> 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] [so] Weekly Meeting

[Manoj K Nair]

Hi Seshu,

In today’s SO meeting you mentioned about the bifurcation to Imperative BPMN 
flow and Existing MSO BPMN flow . Can you please clarify how this bifurcation 
is carried out. I just checked the implementation of API handler – 
ServiceInstances.java and found that - String requestJSON, Action action, 
HashMap instanceIdMap, String version parameters are passed for 
Service instantiation . Further  getServiceInstanceOrchestrationURI is used to 
look up the Recipe from Catalog DB.

Can you please confirm if the BPMN URL is selected based on 
msoRequest.getModelInfo().getModelType() ?  Can you please clarify what logic 
is applied for selection of BPMN flow and delegation.

Additionally , is this going to change, because 
here
 there is a proposal to have a generic workflow engine with Camunda and WSO2 
plugins.

Thanks

Manoj

[https://www.netcracker.com/assets/img/netcracker-social-final.png] ƕ
From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Seshu m
Sent: Wednesday, August 09, 2017 1:40 PM
To: onap-discuss@lists.onap.org
Cc: onap-...@lists.onap.org
Subject: [onap-tsc] [so] Weekly Meeting


[so] Weekly Meeting
https://zoom.us/j/309416964
Hi there,
ONAP Meeting 6 is inviting you to a scheduled Zoom meeting.
Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/309416964 Or iPhone 
one-tap (US Toll): +14086380968,,309416964# or +16465588656,,309416964# Or 
Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) +1 855 
880 1246 (US Toll Free) +1 877 369 0926 (US Toll Free) Meeting ID: 309 416 964 
International numbers available: 
https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT
2:00 PM - 3:00 PM

Best Regards,
Seshu
**
 This email and its attachments contain confidential information from HUAWEI, 
which is intended only for the person or entity whose address is listed above. 
Any use of the information contained here in any way (including, but not 
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s) is prohibited. If you receive this 
email in error, please notify the sender by phone or email immediately and 
delete it!
 
*






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

[onap-discuss] Open lab meeting now

[Tina Tsou]

Dear all,

Which meeting ID is valid for the Open Lab meeting now?


Thank you,
Tina
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [OOM] Proposed topic for today's OOM call

[赵化冰]

Hi Team,

The idea is to use the annotation of kubernetes configuration file to put
the information what MSB need for service registration. After the service
is spun up by kubernetes, registrator can get this information by watching
the POD event and register the service to MSB using this piece of
information.

This diagram is for the deployment of MSB OOM integration which I still
have some questions in it. I hope we can discuss in the team.
* Deploy there PODs for MSB: External API Gateway(EAG), Internal API
Gateway(IAG) and Discovery
* Deploy DNS POD and Service
* Deploy Registrator POD (How can Registrator get the kubernets master IP
to watch the POD event? )
* Service consumer use DNS or Cluster IP to get the MSB IAG and Discovery
Service (How can the Cluster IP be passed to other ONAP services if using
the Cluster IP solution?)
* External systems use an the External IP of the MSB EAG to send requests
to ONAP system

[image: image.png]

Thanks,
Huabing


On Wed, Aug 16, 2017 at 8:24 PM 赵化冰  wrote:

> Hi David,
>
> May I suggest we discuss the below topics at today's call ?
>
>
>- Draft of the YAML configuration contract
>- Kubernetes Deployment for MSB OOM Integration
>
>
> Thanks,
> Huabing
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Facing issues with policy setup with Vagrant

[Viswanath Kumar Skand Priya via onap-discuss]

+ onap-discuss


Another note : In ~/docker/policy-db/Dockerfile, if you are behind proxy ( like 
me.. ), then you will have to teak apt-key command like below, to have them 
working...


apt-key adv --keyserver-options http-proxy= --recv-keys 
--keyserver hkp://keyserver.ubuntu.com:80 0xcbcb082a1bb943db && \


Sorry to spam... let me compile all changes and put them in wiki from now on.


BR,

Viswa


From: Kumar Skand Priya, Viswanath V
Sent: Wednesday, August 16, 2017 8:15 PM
To: Guo, Ruijing; 'DRAGOSH, PAMELA L (PAM)'; Atul Shegokar
Subject: RE: [onap-discuss] Facing issues with policy setup with Vagrant

OK I got this working by..


· Switching to 16.04 base

· Switching to “apt-get install default-jdk” . This step eliminates 
setting ppa repository .

Incase of Ubuntu 14.04 default JDK is v7 and incase of Ubuntu 16.04 default JDK 
is v8.

May be you can add these to your scripts…

BR,
Viswa

From: Kumar Skand Priya, Viswanath V
Sent: Wednesday, August 16, 2017 8:04 PM
To: Guo, Ruijing ; 'DRAGOSH, PAMELA L (PAM)' 
; Atul Shegokar ; Kumar 
Skand Priya, Viswanath V 
Subject: Re: [onap-discuss] Facing issues with policy setup with Vagrant


Ruijing,



I cannot get past the building Dockers through DockerFile and I'm stuck in 
openJDK 8 installation step.


Cannot add PPA: 'ppa:webupd8team/java'.
Please check that the PPA name or format is correct.

Tried adding "apt-get install -y --reinstall ca-certificates​" to the build 
step, switched openJDK with Oracle JDK etc.. Still no luck...

Could you let me know what am I missing here?

BR,
Viswa






From: 
onap-discuss-boun...@lists.onap.org 
>
 on behalf of Viswanath Kumar Skand Priya via onap-discuss 
>
Sent: Wednesday, August 16, 2017 7:23 PM
To: Guo, Ruijing; 'DRAGOSH, PAMELA L (PAM)'; Atul Shegokar
Cc: onap-discuss@lists.onap.org
Subject: [E] Re: [onap-discuss] Facing issues with policy setup with Vagrant


Thanks Ruijing. I had to do minor changes in your script to have it run in my 
environment..

  *   ​​ For some reason docker-compose via pip install didn't work. So used 
docker-compose binary directly ( sudo curl -o /usr/local/bin/docker-compose
  *   -L 
"https://github.com/docker/compose/releases/download/1.15.0/docker-compose-$(uname
  *   -s)-$(uname -m)")
  *   Patched settings.xml to work through corporate proxy
  *   Added switches in between script to pause & wait for my action to proceed.
  *   I had to manually edit each Dockerfile to add proxy configurations in 
/etc/apt/apt.conf as well. Simply exporting HTTP_PROXY didn't help in my case.

With above modifications, I was able to be see them running now. I had to 
manually do the stuffs in for loop to make it work in my env ( mainly due to 
corporate proxy :( ).

BTW after having all these dockers up, how am I supposed to use Policy GUI to 
create / edit / apply any policy?
Could you help me with this info?

BR,
Viswa

From: Guo, Ruijing >
Sent: Wednesday, August 16, 2017 6:14 PM
To: Kumar Skand Priya, Viswanath V; 'DRAGOSH, PAMELA L (PAM)'; Atul Shegokar
Cc: onap-discuss@lists.onap.org
Subject: [E] RE: [onap-discuss] Facing issues with policy setup with Vagrant

Hi,

Vagrant/virtualbox need virtualization support. you can setup policy from 
Ubuntu 16.04 VM/Bare Metal without vagrant/virtualbox:


1.  Setup sudo without password in Ubuntu 16.04 VM/Bare Metal

2.  Git clone 
http://gerrit.onap.org/r/policy/docker

3.  Patch from 
https://gerrit.onap.org/r/#/c/7719/
 (still in review)

4.  Change 192.168.0.10 in docker/vagrant/setup_policy.sh to interface IP 
address 

[onap-discuss] [usecaseui]: Any request for the VID team

[Lefevre, Catherine]

Good morning Use Case UI Team,

Have you any particular request that the VID team should consider as part of 
their ONAP R1?
Thank you

Many thanks & regards
Catherine

Catherine Lefèvre
AT Network and Shared Services
D2 Platform & Systems Development
AVP Software Development & Engineering
ECOMP/ONAP/RUBY/SPP


Phone: +32 2 418 49 22
Mobile: +32 475 77 36 73
catherine.lefe...@intl.att.com

TEXTING and DRIVING... It Can Wait

AT
BUROGEST OFFICE PARK SA
Avenue des Dessus-de-Lives, 2
5101 Loyers (Namur)
Belgium



NOTE: This email (or its attachments) contains information belonging to the 
sender, which may be confidential. proprietary and/or legally privileged. The 
information is intended only for the use of the individual(s) or entity(ies) 
named above. If you are not the intended recipient, you are hereby notified 
that any disclosure, distribution or taking of any action in reliance on the 
content of this is strictly forbidden. If you have received this e-mail in 
error please immediately notify the sender identified above

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

Re: [onap-discuss] Facing issues with policy setup with Vagrant

[DRAGOSH, PAMELA L (PAM)]

Viswa,

Thanks! Maybe we can update the wiki to reflect how to get it to run in your 
environment?

For the Policy GUI, I believe you will need the Portal framework to be running 
in order to access the GUI.

I’ve added Tarun to the email thread in hopes that he can help with 
instructions on getting that running.

Thanks,

Pam

From: "viswanath.kumarskandpr...@verizon.com" 

Date: Wednesday, August 16, 2017 at 9:53 AM
To: "Guo, Ruijing" , "DRAGOSH, PAMELA L (PAM)" 
, Atul Shegokar 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Facing issues with policy setup with Vagrant


Thanks Ruijing. I had to do minor changes in your script to have it run in my 
environment..

  *   ​​ For some reason docker-compose via pip install didn't work. So used 
docker-compose binary directly ( sudo
  *   curl -o /usr/local/bin/docker-compose -L 
"https://github.com/docker/compose/releases/download/1.15.0/docker-compose-$(uname
  *   -s)-$(uname -m)")
  *   Patched settings.xml to work through corporate proxy
  *   Added switches in between script to pause & wait for my action to proceed.
  *   I had to manually edit each Dockerfile to add proxy configurations in 
/etc/apt/apt.conf as well. Simply exporting HTTP_PROXY didn't help in my case.

With above modifications, I was able to be see them running now. I had to 
manually do the stuffs in for loop to make it work in my env ( mainly due to 
corporate proxy :( ).

BTW after having all these dockers up, how am I supposed to use Policy GUI to 
create / edit / apply any policy?
Could you help me with this info?

BR,
Viswa

From: Guo, Ruijing 
Sent: Wednesday, August 16, 2017 6:14 PM
To: Kumar Skand Priya, Viswanath V; 'DRAGOSH, PAMELA L (PAM)'; Atul Shegokar
Cc: onap-discuss@lists.onap.org
Subject: [E] RE: [onap-discuss] Facing issues with policy setup with Vagrant

Hi,

Vagrant/virtualbox need virtualization support. you can setup policy from 
Ubuntu 16.04 VM/Bare Metal without vagrant/virtualbox:


1.  Setup sudo without password in Ubuntu 16.04 VM/Bare Metal

2.  Git clone 
http://gerrit.onap.org/r/policy/docker

3.  Patch from 
https://gerrit.onap.org/r/#/c/7719/
 (still in review)

4.  Change 192.168.0.10 in docker/vagrant/setup_policy.sh to interface IP 
address in your Ubuntu 16.04 VM/Bare Metal

5.  Run setup_policy.sh

I will remove hardcoded IP address. So you can just run setup_policy.sh

Thanks,
-Ruijing


From: viswanath.kumarskandpr...@verizon.com 
[mailto:viswanath.kumarskandpr...@verizon.com]
Sent: Wednesday, August 16, 2017 7:52 PM
To: 'DRAGOSH, PAMELA L (PAM)' ; Atul Shegokar 
; Guo, Ruijing 
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Facing issues with policy setup with Vagrant

I’m also facing similar issue. Although, going through Google, I learnt that 
nested virtualization is not supported. Apparently, I’m running a Ubuntu VM in 
openstack and I’m trying to use vagrant to power-up V-Box inside that Ubuntu.

Is there any much simpler approach to bring up entire policy component in 
single VM? The READ.ME from 
http://gerrit.onap.org/r/policy/docker
 suggest to build individual mvn projects starting from 
“policy-common-modules”, but I couldn’t see that dir in my cloned repo.

Also, 

Re: [onap-discuss] Facing issues with policy setup with Vagrant

[Guo, Ruijing]

Hi,

Vagrant/virtualbox need virtualization support. you can setup policy from 
Ubuntu 16.04 VM/Bare Metal without vagrant/virtualbox:


1.  Setup sudo without password in Ubuntu 16.04 VM/Bare Metal

2.  Git clone http://gerrit.onap.org/r/policy/docker

3.  Patch from https://gerrit.onap.org/r/#/c/7719/ (still in review)

4.  Change 192.168.0.10 in docker/vagrant/setup_policy.sh to interface IP 
address in your Ubuntu 16.04 VM/Bare Metal

5.  Run setup_policy.sh

I will remove hardcoded IP address. So you can just run setup_policy.sh

Thanks,
-Ruijing


From: viswanath.kumarskandpr...@verizon.com 
[mailto:viswanath.kumarskandpr...@verizon.com]
Sent: Wednesday, August 16, 2017 7:52 PM
To: 'DRAGOSH, PAMELA L (PAM)' ; Atul Shegokar 
; Guo, Ruijing 
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Facing issues with policy setup with Vagrant

I’m also facing similar issue. Although, going through Google, I learnt that 
nested virtualization is not supported. Apparently, I’m running a Ubuntu VM in 
openstack and I’m trying to use vagrant to power-up V-Box inside that Ubuntu.

Is there any much simpler approach to bring up entire policy component in 
single VM? The READ.ME from http://gerrit.onap.org/r/policy/docker suggest to 
build individual mvn projects starting from “policy-common-modules”, but I 
couldn’t see that dir in my cloned repo.

Also, https://wiki.onap.org/pages/viewpage.action?pageId=11929334 page explains 
about building PDP but not entire policy component.

Could you somebody from policy team shed some light on development env setup?

BR,
Viswa

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DRAGOSH, PAMELA L 
(PAM)
Sent: Wednesday, August 16, 2017 5:13 PM
To: Atul Shegokar 
>; 
ruijing@intel.com
Cc: onap-discuss@lists.onap.org
Subject: [E] Re: [onap-discuss] Facing issues with policy setup with Vagrant

Atul,

Sorry that you are having issues. I don’t know what those errors are or where 
they come from. Perhaps Ruijing could help you, he setup the vagrant for Policy.

Not sure if you saw this wiki or if it would help:

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


Regards,

Pam

From: 
>
 on behalf of Atul Shegokar 
>
Date: Wednesday, August 16, 2017 at 4:31 AM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] Facing issues with policy setup with Vagrant

HI team,

I am trying to make setup for policy using vagrant. When I try to use vagrant 
up command, it gives an error saying VT-x is not available (VERR_VMX_NO_VMX).

I have already made below checks –

1)  VT-x AMD-V rea active in VM.

2)  VT-x is enabled in BIOS.

3)  Hyper-V is disabled and system rebooted (it was checked earlier).

Please guide help, if there are any other possible reasons which are affecting 
vagrant up command working.



Thanks & Regards,
Atul Shegokar













Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at 
http://www.techmahindra.com/Disclaimer.html
 externally 
http://tim.techmahindra.com/tim/disclaimer.html
 internally within TechMahindra.

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

[onap-discuss] 邀请：ONAP Holmes Weekly Meeting @ 2017-08-17 (周四) 20:00 - 21:00 (CST) (onap-discuss@lists.onap.org)

[Guangrong Fu]

BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Shanghai
X-LIC-LOCATION:Asia/Shanghai
BEGIN:STANDARD
TZOFFSETFROM:+0800
TZOFFSETTO:+0800
TZNAME:CST
DTSTART:19700101T00
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=Asia/Shanghai:20170817T20
DTEND;TZID=Asia/Shanghai:20170817T21
DTSTAMP:20170816T125447Z
ORGANIZER;CN=Guangrong Fu:mailto:steven20...@gmail.com
UID:4b62j73lq9s0d9m0skkum0a...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jh2...@att.com;X-NUM-GUESTS=0:mailto:jh2...@att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=du.jiaqi...@zte.com.cn;X-NUM-GUESTS=0:mailto:du.jiaqi...@zte.com.cn
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=ramesh.a.nagara...@accenture.com;X-NUM-GUESTS=0:mailto:ramesh.a.nag
 ara...@accenture.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=david.sauvag...@bell.ca;X-NUM-GUESTS=0:mailto:david.sauvageau@bell.
 ca
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=liuyuan...@chinamobile.com;X-NUM-GUESTS=0:mailto:liuyuanyjy@chinamo
 bile.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=zhao.huab...@zte.com.cn;X-NUM-GUESTS=0:mailto:zhao.huab...@zte.com.
 cn
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=l...@research.att.com;X-NUM-GUESTS=0:mailto:l...@research.att.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=joh...@att.com;X-NUM-GUESTS=0:mailto:joh...@att.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=ACCEPTED;RSVP=TRUE
 ;CN=Guangrong Fu;X-NUM-GUESTS=0:mailto:steven20...@gmail.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=fu.guangr...@zte.com.cn;X-NUM-GUESTS=0:mailto:fu.guangr...@zte.com.
 cn
RECURRENCE-ID;TZID=Asia/Shanghai:20170817T20
CREATED:20170720T102725Z
DESCRIPTION:Hi there\, \n\nGuangrong Fu is inviting you to a scheduled Zoom
  meeting. \n\nIn the meeting\, we are going to continue with the topic abou
 t the integration of DCAE and MSB. I have discussed with Huabing offline ab
 out this and proposed a way to accomplish this for R1. We want to check wit
 h DCAE and OOM whether it's feasible or not. If time permits\, we may have 
 more discussion on how to achieve the goal in a more elegant way as a stret
 ch goal.\n\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/j/
 66\n\nOr iPhone one-tap (US Toll):  +14086380968\,\,66# or 
 +16465588656\,\,66#\n\nOr Telephone:\nDial: +1 408 638 0968 (US
  Toll) or +1 646 558 8656 (US Toll)\nMeeting ID: 699 996 \nInte
 rnational numbers available: https://zoom.us/zoomconference?m=_5QAuX9O-wb43
 xJqoNQjTlyYurEIrnWK\n\n\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\n请勿修改说明中的这部分内容。\n\n在 https://www.go
 ogle.com/calendar/event?action=VIEW=NGI2Mmo3M2xxOXMwZDltMHNra3VtMGE3ZmN
 fMjAxNzA4MTdUMTIwMDAwWiBvbmFwLWRpc2N1c3NAbGlzdHMub25hcC5vcmc=MjEjc3Rldm
 VuMjAwMjdAZ21haWwuY29tNjliYjYwNTM1MzY4NmY5ZWJmZDczYzU0NjYzZDAyM2MyNzFmMjBkY
 Q=Asia/Shanghai=zh_CN 查看您的活动。\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20170816T125447Z
LOCATION:https://zoom.us/j/66
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:ONAP Holmes Weekly Meeting
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR


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

[onap-discuss] FW: SO weekly meeting

[Seshu m]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:India Standard Time
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+0530
TZOFFSETTO:+0530
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN=Seshu m:MAILTO:seshu.kuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Xinhui Li:
 MAILTO:lxin...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Danny Lin:
 MAILTO:l...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Jinxin (Sa
 w):MAILTO:saw@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Zengjiangu
 o (OSS Design):MAILTO:zengjian...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Andrew Phi
 lip:MAILTO:aphi...@microsoft.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang, Bin":
 MAILTO:bin.y...@windriver.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhanganbin
 g...@chinamobile.com:MAILTO:zhanganb...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Ethan Lynn
 :MAILTO:ethanly...@vmware.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="CHOMA, JOH
 N S":MAILTO:jc1...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=DeWayne Fi
 lppi:MAILTO:dewa...@gigaspaces.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Byung-Woo 
 Jun:MAILTO:byung-woo@ericsson.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wangchengl
 i...@chinamobile.com:MAILTO:wangchen...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhongheliu
 @boco.com.cn:MAILTO:zhonghe...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=zhang.zhou
 1...@zte.com.cn:MAILTO:zhang.zh...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Chenchuany
 u:MAILTO:chenchua...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyanyjy
 @chinamobile.com:MAILTO:yangyan...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DAUGHERTY,
  ROBERT E":MAILTO:rd4...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Lingli Den
 g:MAILTO:denglin...@chinamobile.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=wu.liang@z
 te.com.cn:MAILTO:wu.li...@zte.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yangyuanwe
 i...@boco.com.cn:MAILTO:yangyuan...@boco.com.cn
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=denghui (L
 ):MAILTO:denghu...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Christophe
 r Donley (Chris):MAILTO:christopher.don...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=alex.vul@i
 ntel.com:MAILTO:alex@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Vijaykumar
  S:MAILTO:vijaykuma...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=onap-discu
 s...@lists.onap.org:MAILTO:onap-discuss@lists.onap.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Praveen Kr
 ishnamurthy P:MAILTO:kprav...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="SOMASUNDAR
 AM, PRABHURAM":MAILTO:ps7...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="BULLARD, G
 IL":MAILTO:wb5...@att.com
DESCRIPTION;LANGUAGE=en-US:When: Occurs every Wednesday effective 8/16/2017
  from 7:00 PM to 8:00 PM (UTC+05:30) Chennai\, Kolkata\, Mumbai\, New Delh
 i.\n\nNote: The GMT offset above does not reflect daylight saving time adj
 ustments.\n\n*~*~*~*~*~*~*~*~*~*\n\n [so] Weekly Meeting\nhttps://zoom.us/
 j/309416964\n\nHi there\, ONAP Meeting 8 is inviting you to a scheduled Zo
 om meeting.\nJoin from PC\, Mac\, Linux\, iOS or Android: https://zoom.us/
 j/309416964\nOr\niPhone one-tap (US Toll): +14086380968\,\,309416964# or +
 16465588656\,\,309416964#\nOr\nTelephone: Dial: +1 408 638 0968 (US Toll) 
 or +1 646 558 8656 (US Toll) +1 855 880 1246 (US Toll Free) +1 877 369 092
 6 (US Toll Free)\nMeeting ID: 309 416 964\nInternational numbers available
 : https://zoom.us/zoomconference?m=30xXqK2sdCwPiwKQZLwqW5yEWuwQ7QHT\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=WE;WKST=SU
SUMMARY;LANGUAGE=en-US:FW: SO weekly meeting
DTSTART;TZID=India Standard Time:20170816T19
DTEND;TZID=India Standard Time:20170816T20
UID:04008200E00074C5B7101A82E008C07578307216D301000
 010005F0D2FDC0A38A040B56B13ACF1DF6DE1
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170816T040235Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:1737525217
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE

Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

[Alla Goldner]

Hi Tao,

So, I guess, we resolved one outstanding issue for vVoLTE support!

One question - with this design in place, I guess, it will not be difficult to 
support additional use cases UI, am I right?

 Best regards, 

Alla Goldner

Open Network Division 
Amdocs Technology





-Original Message-
From: shentao [mailto:shen...@chinamobile.com] 
Sent: Wednesday, August 16, 2017 2:12 PM
To: 'GILBERT, MAZIN E (MAZIN E)' ; Alla Goldner 

Cc: onap-discuss@lists.onap.org
Subject: 答复: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Hi, Mazin and Alla

I have discussed this issue with Lusheng and reached an agreement.
The solution is that Usecase UI will get alarm and performance data via Dmaap 
and support data storage.
So it isn't difficult to display alarm and performance data by UI.
Thanks for your attention.

Best regards,
Tao


-邮件原件-
发件人: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] 代表 GILBERT, MAZIN E (MAZIN E)
发送时间: 2017年8月14日 23:02
收件人: Alla Goldner
抄送: onap-discuss@lists.onap.org
主题: Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

I would like to understand how much of the work is app specific to VoLTE. We 
really should leverage any UI across all use cases especially if it is 
generating custom platform work. I will wait for the PTLs to share more info.

Thanks
Mazin 

Sent through AT's fastest network 

> On Aug 14, 2017, at 5:43 AM, Alla Goldner  wrote:
> 
>  



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] [OOM] Proposed topic for today's OOM call

[赵化冰]

Hi David,

May I suggest we discuss the below topics at today's call ?


   - Draft of the YAML configuration contract
   - Kubernetes Deployment for MSB OOM Integration


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

Re: [onap-discuss] Facing issues with policy setup with Vagrant

[Viswanath Kumar Skand Priya via onap-discuss]

I’m also facing similar issue. Although, going through Google, I learnt that 
nested virtualization is not supported. Apparently, I’m running a Ubuntu VM in 
openstack and I’m trying to use vagrant to power-up V-Box inside that Ubuntu.

Is there any much simpler approach to bring up entire policy component in 
single VM? The READ.ME from http://gerrit.onap.org/r/policy/docker suggest to 
build individual mvn projects starting from “policy-common-modules”, but I 
couldn’t see that dir in my cloned repo.

Also, https://wiki.onap.org/pages/viewpage.action?pageId=11929334 page explains 
about building PDP but not entire policy component.

Could you somebody from policy team shed some light on development env setup?

BR,
Viswa

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DRAGOSH, PAMELA L 
(PAM)
Sent: Wednesday, August 16, 2017 5:13 PM
To: Atul Shegokar ; ruijing@intel.com
Cc: onap-discuss@lists.onap.org
Subject: [E] Re: [onap-discuss] Facing issues with policy setup with Vagrant

Atul,

Sorry that you are having issues. I don’t know what those errors are or where 
they come from. Perhaps Ruijing could help you, he setup the vagrant for Policy.

Not sure if you saw this wiki or if it would help:

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


Regards,

Pam

From: 
>
 on behalf of Atul Shegokar 
>
Date: Wednesday, August 16, 2017 at 4:31 AM
To: "onap-discuss@lists.onap.org" 
>
Subject: [onap-discuss] Facing issues with policy setup with Vagrant

HI team,

I am trying to make setup for policy using vagrant. When I try to use vagrant 
up command, it gives an error saying VT-x is not available (VERR_VMX_NO_VMX).

I have already made below checks –

1)  VT-x AMD-V rea active in VM.

2)  VT-x is enabled in BIOS.

3)  Hyper-V is disabled and system rebooted (it was checked earlier).

Please guide help, if there are any other possible reasons which are affecting 
vagrant up command working.



Thanks & Regards,
Atul Shegokar













Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at 
http://www.techmahindra.com/Disclaimer.html
 externally 
http://tim.techmahindra.com/tim/disclaimer.html
 internally within TechMahindra.

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

[onap-discuss] 答复: [DCAE] DCAE questions from Usecase UI

[shentao]

Hi, Mazin and Alla

I have discussed this issue with Lusheng and reached an agreement.
The solution is that Usecase UI will get alarm and performance data via
Dmaap and support data storage.
So it isn't difficult to display alarm and performance data by UI.
Thanks for your attention.

Best regards,
Tao


-邮件原件-
发件人: onap-discuss-boun...@lists.onap.org
[mailto:onap-discuss-boun...@lists.onap.org] 代表 GILBERT, MAZIN E (MAZIN E)
发送时间: 2017年8月14日 23:02
收件人: Alla Goldner
抄送: onap-discuss@lists.onap.org
主题: Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

I would like to understand how much of the work is app specific to VoLTE. We
really should leverage any UI across all use cases especially if it is
generating custom platform work. I will wait for the PTLs to share more
info.

Thanks
Mazin 

Sent through AT's fastest network 

> On Aug 14, 2017, at 5:43 AM, Alla Goldner  wrote:
> 
>  



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

[onap-discuss] External System Register API and VNFM/SDNC/EMS schema in A

[li.zi30]

Hi Jimmy and All,




I updated the External System Register API after referenced 
https://wiki.onap.org/display/DW/AAI+API . To visit the new API please visit 
https://wiki.onap.org/pages/viewpage.action?pageId=11930343 . In this page also 
include the schema definition of each external system.




@Jimmy  When comes to the schema of VNFM/SDNC/EMS, I think they are totally new 
data to the original A repository. So shall I add them to A at the same 
level of cloud-infrastructure? Or can you give me any suggestions? 




Thank you,


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

Re: [onap-discuss] Welcome to the "onap-discuss" mailing list

[Neeraj Benjwal]

My Email ID : neeraj.benj...@lnttechservices.com

Thanks,
[ Neeraj Benjwal ]

-Original Message-
From: onap-discuss-bounces+neeraj.benjwal=lnttechservices@lists.onap.org 
[mailto:onap-discuss-bounces+neeraj.benjwal=lnttechservices@lists.onap.org] 
On Behalf Of onap-discuss-requ...@lists.onap.org
Sent: 16 August 2017 14:37
To: Neeraj Benjwal
Subject: Welcome to the "onap-discuss" mailing list

Welcome to the onap-discuss@lists.onap.org mailing list!

To post to this list, send your email to:

  onap-discuss@lists.onap.org

General information about the mailing list is at:

  https://lists.onap.org/mailman/listinfo/onap-discuss

If you ever want to unsubscribe or change your options (eg, switch to or from 
digest mode, change your password, etc.), visit your subscription page at:

  
https://lists.onap.org/mailman/options/onap-discuss/neeraj.benjwal%40lnttechservices.com


You can also make such adjustments via email by sending a message to:

  onap-discuss-requ...@lists.onap.org

with the word `help' in the subject or body (don't include the quotes), and you 
will get back a message with instructions.

You must know your password to change your options (including changing the 
password, itself) or to unsubscribe.  It is:

  Onap#4321

Normally, Mailman will remind you of your lists.onap.org mailing list passwords 
once every month, although you can disable this if you prefer.  This reminder 
will also include instructions on how to unsubscribe or change your account 
options.  There is also a button on your options page that will email your 
current password to you.
L Technology Services Ltd

www.LntTechservices.com

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [ONAP Helpdesk #43995] [linuxfoundation.org #43995] 转发: 答复: RE: 答复：[integration] Jenkins Merge Failure

[victor....@huawei.com via RT]

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

Hi  Helpdesk,

I also faced this problem.  But  it doesn't works even I 
already change the groupid according the wiki definition.

Here is the console output of Jenkins job: 
https://jenkins.onap.org/view/vfc/job/vfc-nfvo-resmanagement-master-merge-java/3/console
[cid:image001.png@01D316B2.217D0EB0]
Resource and Repositories definition:
[cid:image002.png@01D316B2.87AD2EE0]


I also have another question:
[cid:image003.png@01D316B2.87AD2EE0]

Here is the console output link: 
https://jenkins.onap.org/view/vfc/job/vfc-nfvo-driver-svnfm-master-drv-vnfm-huawei-verify-java/2/console
Should I change the corresponding jjb script?
[cid:image004.png@01D316B3.146F6C80]
Script link: 
https://gerrit.onap.org/r/gitweb?p=ci-management.git;a=blob;f=jjb/vfc/vfc-nfvo-driver-svnfm-huawei.yaml;h=77e16f973bd005ab4de8aab2b678cc9c03f066eb;hb=refs/heads/master

Because when I check the Jenkins job configuration, only can find the 
vfc-nfvo-driver-svnfm mvn setting file.

Cloud you help check with it?
BR
Victor
*
本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使
用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通
知发件人并删除本邮件！
*

*
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person
or entity whose address is listed above. Any use of the information contained 
herein in any way (including, but not
limited to, total or partial disclosure, reproduction, or dissemination) by 
persons other than the intended recipient(s)
is prohibited. If you receive this e-mail in error, please notify the sender by 
phone or email immediately and delete it!
*

发件人: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] 代表 fu.guangr...@zte.com.cn
发送时间: 2017年8月7日 9:32
收件人: Gary Wu 
抄送: onap-discuss@lists.onap.org; helpd...@onap.org
主题: [onap-discuss] 答复: RE: 答复：[integration] Jenkins Merge Failure


Hi Gary,



Thanks for your hint. The problem is caused by the inconsistency of the 
groupids between what's defined on the wiki page and the actual one used in the 
pom. Now they are in accordance with each other and have been successfully 
merged.



Thank you very much.



Best Regards,

Guangrong








原始邮件
发件人： >;
收件人： >;
抄送人： 
>;付光荣10144542;
日 期 ：2017年08月07日 06:45
主 题 ：RE: 答复：[integration] Jenkins Merge Failure


Hi helpdesk,

Can you help on this?  I’m guessing that the Nexus deployment is failing due to 
a mismatch with the artifact groupId, but it’s not possible to tell from the 
logs  whether it’s a misconfiguration of Nexus, or there’s something wrong with 
the groupIds on the artifacts themselves.

Thanks,
Gary


From: fu.guangr...@zte.com.cn 
[mailto:fu.guangr...@zte.com.cn]
Sent: Friday, August 04, 2017 6:04 PM
To: Gary Wu >
Cc: onap-discuss@lists.onap.org
Subject: 答复：[integration] Jenkins Merge Failure

Gary,

Any idea on this?

Thanks.

Guangrong
原始邮件
发件人:付光荣10144542
收件人:gary.i...@huawei.com;
抄送人:onap-discuss@lists.onap.org;
日期:2017-08-04 14:57:41
主题:[integration] Jenkins Merge Failure


Hi Gary,



When jenkins tried to merge codes into gerrit, an error below occurred.



[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on 
project holmes-actions-parent: Failed to deploy artifacts: Could not transfer 
artifact 
org.onap.holmes.actions:holmes-actions-parent:pom:1.0.0-20170804.064650-1  
from/to ecomp-snapshots 
(https://nexus.onap.org/content/repositories/snapshots): Access denied to: 
https://nexus.onap.org/content/repositories/snapshots/org/onap/holmes/actions/holmes-actions-parent/1.0.0-SNAPSHOT/holmes-actions-parent-1.0.0-20170804.064650-1.pom,
 ReasonPhrase: Forbidden. -> [Help 1]

06:46:50 [ERROR]

06:46:50 [ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.

06:46:50 [ERROR] Re-run Maven using the -X switch to enable full debug logging.

06:46:50 [ERROR]

06:46:50 [ERROR] For more information about the errors and possible solutions, 
please read the following articles:

06:46:50 [ERROR] [Help 1] 

[onap-discuss] Facing issues with policy setup with Vagrant

[Atul Shegokar]

HI team,

I am trying to make setup for policy using vagrant. When I try to use vagrant 
up command, it gives an error saying VT-x is not available (VERR_VMX_NO_VMX).

I have already made below checks -

1)  VT-x AMD-V rea active in VM.

2)  VT-x is enabled in BIOS.

3)  Hyper-V is disabled and system rebooted (it was checked earlier).

Please guide help, if there are any other possible reasons which are affecting 
vagrant up command working.



Thanks & Regards,
Atul Shegokar














Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.


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

Re: [onap-discuss] About ESR VIM registration API

[li.zi30]

Hi Ethan,




I will modify the VIM related API according to the schema in A, including 
the data structure and url. and I will remove the name/description properties.




FYI, I suggest we add a "status" property in cloud-region. Because ESR will 
check whether the cloud is reachable, and update the status to A How do you 
think?




BR,

LiZi
















原始邮件



发件人： 
收件人：李滋00164331
抄送人： 
日 期 ：2017年08月16日 13:19
主 题 ：About ESR VIM registration API






Hi Li Zi,

   I just go through the wiki page about VIM registration API . 
https://wiki.onap.org/pages/viewpage.action?pageId=11930343#A:ExternalSystemRegisterAPIDefinition(draft)-VIM

   In the cloud-region schema, it doesn’t provide fields to store ‘name’ and 
‘description’ yet. Maybe we could remove them?

 
 

Best Regards,

Ethan Lynn

ethanly...@vmware.com

+86 010-59934270___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [multicloud] Get start with multi VIM/cloud

[Yang, Bin]

Hi Dave,

   I think it is not ready yet. Will let you know when it is ready 
for test.

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

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Chen, Wei D
Sent: Tuesday, August 15, 2017 4:30 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [multicloud] Get start with multi VIM/cloud

Hi Dear Developers,

Anyone could point me to any guide on how to set up the multicloud environment, 
run the service, any options available to run the service?



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

Re: [onap-discuss] A Developer Environment Setup - ISSUE

[Thamlur Raju]

Hi Vamshi,

In "createDBSchema", i am getting some errors in three logs.
I am sharing all, So Please check it and give me some IDEA.


*metrics.log*

[image: Inline image 1]



*debug.log*

[image: Inline image 2]


*error.log*

[image: Inline image 3]




Regards,

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