Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

[Kedar Ambekar]

Thanks Catherine for the updated diagram, I could follow them.

Hi Daniel, Marco,

I am using Release-1.Here are my env parameters while running ONAP Heat 
template.

artifacts_version: 1.0.0
docker_version: 1.0-STAGING-latest
gerrit_branch: release-1.0.0


When I do demo.sh appc , I get 
“Dictionary does not contain key 'vpg_name_0'.”. The env file 
base_vlb_rackspace does not have this parameter. packet_gen_vlb_rackspace env 
file has this parameter though.

Here is my stack list.

[cid:image004.png@01D2D089.C881]


From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Friday, May 19, 2017 9:31 AM
To: PLATANIA, MARCO ; ROSE, DANIEL V 
; Kedar Ambekar ; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Marco, Kedar,

I have updated the wiki page with the latest pictures.

Best regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Friday, May 19, 2017 12:29 AM
To: ROSE, DANIEL V >; Kedar Ambekar 
>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

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

I’m not familiar with preloading (Dan can cover that part), but for what 
regards the vLB demo flow, APP-C is not involved. During the closed loop, 
policy gets the VNF Id from AAI and provides this Id as argument of a 
CreateVF-Module request to MSO, which actually spins up the second DNS.

The figure in the wiki is outdated and should be replaced. Honeycomb isn’t used 
on the vLB VM.

Thanks,
Marco


From: "ROSE, DANIEL V" >
Date: Thursday, May 18, 2017 at 6:09 PM
To: Kedar Ambekar >, 
"onap-discuss@lists.onap.org" 
>, "PLATANIA, 
MARCO (MARCO)" >
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

you should be calling ./demo.sh appc . What branch of onap are you using? Release1?

Marco can answer questions about the actual demo closed loop better.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Thursday, May 18, 2017 8:44 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel,

Thanks for reply !


1.   In zip file uploaded, I had base_vlb_rackspace and 
dnsscaling_rackspace files.

2.   I did demo.sh preload for 
K-demoVLB-Module.

3.   In Add VF Module, I chose base_vlb and created a VF Module with name 
K-demoVLB-Module.
 I did not do Add VF Module for dns_scaling.

4.   I created a separate heat stack for packet_gen_vlb_rackspace of name  
K-demoVLB-PackGen
 using Heat client.

5.   When I do demo.sh appc K-demoVLB-Module, I got error  Dictionary does 
not contain key 'vpg_name_0'.

6.   I tried to do demo.sh appc on 

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

[Lefevre, Catherine]

Marco, Kedar,

I have updated the wiki page with the latest pictures.

Best regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Friday, May 19, 2017 12:29 AM
To: ROSE, DANIEL V ; Kedar Ambekar ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

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

I’m not familiar with preloading (Dan can cover that part), but for what 
regards the vLB demo flow, APP-C is not involved. During the closed loop, 
policy gets the VNF Id from AAI and provides this Id as argument of a 
CreateVF-Module request to MSO, which actually spins up the second DNS.

The figure in the wiki is outdated and should be replaced. Honeycomb isn’t used 
on the vLB VM.

Thanks,
Marco


From: "ROSE, DANIEL V" >
Date: Thursday, May 18, 2017 at 6:09 PM
To: Kedar Ambekar >, 
"onap-discuss@lists.onap.org" 
>, "PLATANIA, 
MARCO (MARCO)" >
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

you should be calling ./demo.sh appc . What branch of onap are you using? Release1?

Marco can answer questions about the actual demo closed loop better.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Thursday, May 18, 2017 8:44 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel,

Thanks for reply !


1.  In zip file uploaded, I had base_vlb_rackspace and dnsscaling_rackspace 
files.

2.  I did demo.sh preload for 
K-demoVLB-Module.

3.  In Add VF Module, I chose base_vlb and created a VF Module with name 
K-demoVLB-Module.
 I did not do Add VF Module for dns_scaling.

4.  I created a separate heat stack for packet_gen_vlb_rackspace of name  
K-demoVLB-PackGen
 using Heat client.

5.  When I do demo.sh appc K-demoVLB-Module, I got error  Dictionary does 
not contain key 'vpg_name_0'.

6.  I tried to do demo.sh appc on 
K-demoVLB-PackGen
 as well. That time it gave error Dictionary does not contain key 
'vpg_private_ip_1'.


In vLB use case, the mounting of traffic generator to enable policy driven 
configuration changes (demo.sh appc) should be done on which VF-Module ? In my 
example, 
K-demoVLB-PackGen
 or K-demoVLB-Module ?

The architecture diagram on wiki for vLB 

Re: [onap-discuss] [onap-tsc] Framework for proposed projects feedback

[RICE, CHRISTOPHER]

Mazin and TSC members,

Nice job on the"rubrick" for evaluating the proposed projects.  It will make 
sure that the contributions with the most interest, support and relevance with 
the least risk make the first release.

Chris




Sent via the Samsung Galaxy S8+, an AT 4G LTE smartphone


 Original message 
From: "GILBERT, MAZIN E" 
Date: 5/18/17 8:15 PM (GMT-06:00)
To: onap-tsc , onap-discuss@lists.onap.org
Subject: [onap-tsc] Framework for proposed projects feedback

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

ONAP Team,

I want to thank you again for working so hard in proposing projects. Per our 
TSC meeting
today, I am enclosing the framework that the TSC committee developed for 
scoring and
providing feedback on each project. I expect you will get feedback from the TSC 
committee
starting next week.

Thanks
Mazin

Framework for TSC Project Feedback

1.Clarity

a. Reasonable and well defined scope

b.Identification of software modules and APIs being developed and delivered 
to ONAP and other components.

c. Following project and LF guidelines for contributors/committers

d.Identification of dependencies and assumptions on other components and 
open source.

2.Overlap

a. Intentional and unintentional overlap

b.Overlap with external open source efforts

3.Risk management

a. Sufficient development resources allocated to deliver on time

b.At least 3-4 companies involved to provide diversity

c. Availability of seed code and its maturity

4.Relevance and prioritization

a. Alignment with merger release

b.Alignment with use cases

c.Sound technical solution for solving a real need




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

[onap-discuss] Framework for proposed projects feedback

[GILBERT, MAZIN E (MAZIN E)]

ONAP Team,

I want to thank you again for working so hard in proposing projects. Per our 
TSC meeting
today, I am enclosing the framework that the TSC committee developed for 
scoring and
providing feedback on each project. I expect you will get feedback from the TSC 
committee
starting next week.

Thanks
Mazin

Framework for TSC Project Feedback

1.Clarity

a. Reasonable and well defined scope

b.Identification of software modules and APIs being developed and delivered 
to ONAP and other components.

c. Following project and LF guidelines for contributors/committers

d.Identification of dependencies and assumptions on other components and 
open source.

2.Overlap

a. Intentional and unintentional overlap

b.Overlap with external open source efforts

3.Risk management

a. Sufficient development resources allocated to deliver on time

b.At least 3-4 companies involved to provide diversity

c. Availability of seed code and its maturity

4.Relevance and prioritization

a. Alignment with merger release

b.Alignment with use cases

c.Sound technical solution for solving a real need




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

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

[PLATANIA, MARCO (MARCO)]

Hi Kedar,

I’m not familiar with preloading (Dan can cover that part), but for what 
regards the vLB demo flow, APP-C is not involved. During the closed loop, 
policy gets the VNF Id from AAI and provides this Id as argument of a 
CreateVF-Module request to MSO, which actually spins up the second DNS.

The figure in the wiki is outdated and should be replaced. Honeycomb isn’t used 
on the vLB VM.

Thanks,
Marco


From: "ROSE, DANIEL V" 
Date: Thursday, May 18, 2017 at 6:09 PM
To: Kedar Ambekar , "onap-discuss@lists.onap.org" 
, "PLATANIA, MARCO (MARCO)" 

Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

you should be calling ./demo.sh appc . What branch of onap are you using? Release1?

Marco can answer questions about the actual demo closed loop better.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Thursday, May 18, 2017 8:44 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel,

Thanks for reply !


1.   In zip file uploaded, I had base_vlb_rackspace and 
dnsscaling_rackspace files.

2.   I did demo.sh preload for 
K-demoVLB-Module.

3.   In Add VF Module, I chose base_vlb and created a VF Module with name 
K-demoVLB-Module.
 I did not do Add VF Module for dns_scaling.

4.   I created a separate heat stack for packet_gen_vlb_rackspace of name  
K-demoVLB-PackGen
 using Heat client.

5.   When I do demo.sh appc K-demoVLB-Module, I got error  Dictionary does 
not contain key 'vpg_name_0'.

6.   I tried to do demo.sh appc on 
K-demoVLB-PackGen
 as well. That time it gave error Dictionary does not contain key 
'vpg_private_ip_1'.


In vLB use case, the mounting of traffic generator to enable policy driven 
configuration changes (demo.sh appc) should be done on which VF-Module ? In my 
example, 
K-demoVLB-PackGen
 or K-demoVLB-Module ?

The architecture diagram on wiki for vLB 
(https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos)
 does not show APPC involved and directing packet generator using NETCONF. Is 
it expected ? If yes, how DNS VM scale up-down is demonstrated in that case ?

In same diagram, what is the use of honeycomb on vLB VM ?

KeDar Ambekar | Network Services | Tech Mahindra
• Desk: +91 20 66018100 x 2879   Mobile: +91 95616 50414

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Thursday, May 18, 2017 12:09 AM
To: Kedar Ambekar >; 
onap-discuss@lists.onap.org
Subject: RE: Re:RE: Query on vlb_ipaddr parameter of vLB usecase

They may both be there, but you wont have to do the 

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

[ROSE, DANIEL V]

you should be calling ./demo.sh appc . What branch of onap are you using? Release1?

Marco can answer questions about the actual demo closed loop better.

Thanks,
Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Thursday, May 18, 2017 8:44 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel,

Thanks for reply !


1.   In zip file uploaded, I had base_vlb_rackspace and 
dnsscaling_rackspace files.

2.   I did demo.sh preload for 
K-demoVLB-Module.

3.   In Add VF Module, I chose base_vlb and created a VF Module with name 
K-demoVLB-Module.
 I did not do Add VF Module for dns_scaling.

4.   I created a separate heat stack for packet_gen_vlb_rackspace of name  
K-demoVLB-PackGen
 using Heat client.

5.   When I do demo.sh appc K-demoVLB-Module, I got error  Dictionary does 
not contain key 'vpg_name_0'.

6.   I tried to do demo.sh appc on 
K-demoVLB-PackGen
 as well. That time it gave error Dictionary does not contain key 
'vpg_private_ip_1'.


In vLB use case, the mounting of traffic generator to enable policy driven 
configuration changes (demo.sh appc) should be done on which VF-Module ? In my 
example, 
K-demoVLB-PackGen
 or K-demoVLB-Module ?

The architecture diagram on wiki for vLB 
(https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos)
 does not show APPC involved and directing packet generator using NETCONF. Is 
it expected ? If yes, how DNS VM scale up-down is demonstrated in that case ?

In same diagram, what is the use of honeycomb on vLB VM ?

KeDar Ambekar | Network Services | Tech Mahindra
• Desk: +91 20 66018100 x 2879   Mobile: +91 95616 50414

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Thursday, May 18, 2017 12:09 AM
To: Kedar Ambekar >; 
onap-discuss@lists.onap.org
Subject: RE: Re:RE: Query on vlb_ipaddr parameter of vLB usecase

They may both be there, but you wont have to do the second one through VID. 
Policy will do it for you


Thanks,

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: Kedar Ambekar [mailto:ake...@techmahindra.com]
Sent: Wednesday, May 17, 2017 2:38 PM
To: onap-discuss@lists.onap.org; Kedar 
Ambekar >; ROSE, DANIEL 
V >
Subject: Re:RE: Query on vlb_ipaddr parameter of vLB usecase

In my case, I think VID has loaded. both as I get 2 options to create VF module.



Sent from my Mi phone
On "ROSE, DANIEL V" >, May 17, 2017 11:00 
PM wrote:
Hi Kedar

you should just have to run it on the one vid loads.
Before 

Re: [onap-discuss] SDC portal is not accessible with 502 error

[ROSE, DANIEL V]

Aayush,

There is kind of a story already for this 
https://jira.onap.org/browse/COMMON-12?filter=-2
if you want to track that or add some details

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of EMPOROPULO, VITALIY
Sent: Thursday, May 18, 2017 11:10 AM
To: aayush.bhatna...@ril.com; ajay.priyadar...@ril.com; EFRAT, ELHAY 
; onap-discuss@lists.onap.org; ning...@ril.com; 
robert.pipp...@ril.com
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Aayush,

It is obviously not a good way to use containers, and is definitely going to 
change.

To my understanding, running all of the SDC containers in a single VM was a 
quick and easy solution for automating SDC deployment in ONAP. From that point 
it will evolve to proper (Micro)services, with independent scaling-out of 
components, load balancing and service lookup as a means of HA and fault 
tolerance, etc.

Regards,
Vitaliy

From: aayush.bhatna...@ril.com 
[mailto:aayush.bhatna...@ril.com]
Sent: Thursday, May 18, 2017 17:38
To: Vitaliy Emporopulo 
>; 
ajay.priyadar...@ril.com; Elhay Efrat 
>; 
onap-discuss@lists.onap.org; 
ning...@ril.com; 
robert.pipp...@ril.com
Subject: RE: SDC portal is not accessible with 502 error

Thanks for the update Vitaliy.

The requirement of running on the same host is something which has been done by 
design, or will it change in the future.

Why I ask this question is the fact that once we try to execute HA and Fault 
Tolerant scenarios for individual ONAP components (inclusive of the SDC), the 
hosts may change.

Regards

Aayush


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vitaliy Emporopulo
Sent: 18 May 2017 18:41
To: Ajay Priyadarshi; Elhay Efrat; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Ajay,

Currently a SDC setup expects all of its containers to run on the same host 
(virtual or physical), and access each other via the host's IP address or 
hostname visible inside the containers. This is possible using 
container-to-host port binding.

Apparently, a SDC container cannot reach the others via 172.16.74.83. On the 
other hand, it looks like the BE identifies itself as 10.0.3.1 (see the log), 
which is your private_ip. This also makes perfect sense - the containers should 
talk to each other on the private network, while the public one is exposed for 
external access. Normally that would be the front-end server.

I guess you won't see a 172.16.74.x address if you run ifconfig inside a 
container, except on FE.

To sum up, the configuration of your containers should point to the private 
network IPs for container-to-container communication (FE-to-BE, 
BE-to-Cassandra, etc).

Regards,
Vitaliy

From: ajay.priyadar...@ril.com 
[mailto:ajay.priyadar...@ril.com]
Sent: Thursday, May 18, 2017 15:00
To: Vitaliy Emporopulo 
>; Elhay 
Efrat >; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Hi Vitaliy,

All SDC Docker containers are on single VM.

docker container list
CONTAINER IDIMAGE   
   COMMAND  CREATED STATUS  PORTS   
  NAMES
58421a971a63
nexus3.onap.org:10001/openecomp/sdc-frontend:1.0-STAGING-latest
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp  sdc-FE
35cdccf1abb5
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest 
"/root/startup.sh"   3 hours ago Up 42 minutes   
0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcpsdc-BE
139f5a712d37
nexus3.onap.org:10001/openecomp/sdc-kibana:1.0-STAGING-latest  
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:5601->5601/tcp
sdc-kbn
9b60d4f6fd20
nexus3.onap.org:10001/openecomp/sdc-cassandra:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  7000-7001/tcp, 
0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp   sdc-cs
85b83dec8442

Re: [onap-discuss] SDNC project build issue

[Tapan Majhi]

Thanks Brian.


From: FREEMAN, BRIAN D [mailto:bf1...@att.com]
Sent: Thursday, May 18, 2017 7:51 PM
To: Tapan Majhi ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] SDNC project build issue

Have to add bin to the assembly section. The upgraded maven-assembly 
plugin is enforcing a new constraint that the 2.2.x version didnt have. I think 
Dan is updating the files since some of the assemble_*.xml’s in the other 
repo’s have already been updated with the id.

Brian

Northbound:
  modified:   asdcApi/installer/src/assembly/assemble_installer_zip.xml
modified:   asdcApi/installer/src/assembly/assemble_mvnrepo_zip.xml
modified:   dataChange/installer/src/assembly/assemble_installer_zip.xml
modified:   dataChange/installer/src/assembly/assemble_mvnrepo_zip.xml
modified:   dmaap-listener/src/assembly/assemble_zip.xml
modified:   ueb-listener/src/assembly/assemble_zip.xml
modified:   vnfapi/installer/src/assembly/assemble_installer_zip.xml
modified:   vnfapi/installer/src/assembly/assemble_mvnrepo_zip.xml
modified:   vnftools/installer/src/assembly/assemble_installer_zip.xml
modified:   vnftools/installer/src/assembly/assemble_mvnrepo_zip.xml


http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;

xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
 
http://maven.apache.org/xsd/assembly-1.1.0.xsd">
bin


From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of MAJHI, TAPAN
Sent: Thursday, May 18, 2017 9:20 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] SDNC project build issue

I am trying to build sdnc/northbound project taking the latest code.

Earlier its was working fine but now with the latest code I am getting below 
error.

[INFO] SDN-C Northbound APIs .. SUCCESS [  5.603 s]
[INFO] asdcApi  SUCCESS [  0.217 s]
[INFO] asdcApi-model .. SUCCESS [ 19.336 s]
[INFO] asdcApi-provider ... SUCCESS [ 24.822 s]
[INFO] asdcApi-features ... SUCCESS [  2.391 s]
[INFO] asdcApi  - Karaf  Installer  FAILURE [  0.757 s]
[INFO] dataChange . SKIPPED
[INFO] dataChange-model ... SKIPPED
[INFO] dataChange-provider  SKIPPED
[INFO] dataChange-features  SKIPPED
[INFO] dataChange  - Karaf  Installer . SKIPPED
[INFO] DMAAP Listener . SKIPPED
[INFO] UEB Listener ... SKIPPED
[INFO] vnfapi . SKIPPED
[INFO] vnfapi-model ... SKIPPED
[INFO] vnfapi-provider  SKIPPED
[INFO] vnfapi-features  SKIPPED
[INFO] VNF API  - Karaf  Installer  SKIPPED
[INFO] VNF Tools Plugin ... SKIPPED
[INFO] VNF Tools Plugin - Provider  SKIPPED
[INFO] VNF tools Plugin - Features  SKIPPED
[INFO] VNF Tools Plugin  - Karaf  Installer ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 57.250 s
[INFO] Finished at: 2017-05-18T09:12:01-04:00
[INFO] Final Memory: 106M/254M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.4.1:single (maven-repo-zip) on 
project asdcApi-installer: Assembly is incorrectly configured: null: Assembly 
is incorrectly configured: null:
[ERROR] Assembly: null is not configured correctly: Assembly ID must be present 
and non-empty.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.4.1:single (maven-repo-zip) on 
project asdcApi-installer: Assembly is incorrectly configured: null
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 

Re: [onap-discuss] question on SDC

[Ramu n]

Thanks Daniel Rose for the reply..

Please clarify my second question.

Regards,
Ramu N

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

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Thursday, May 18, 2017 8:02 PM
To: Ramu n; onap-discuss@lists.onap.org
Cc: Aruna kumar padhi
Subject: RE: [onap-discuss] question on SDC

You can have sensible defaults in SDC that would apply to basic use cases, but 
properties can be replaced when they are used so someone reusing the service 
can decide if the defaults make sense for them. Or like Tal said, just leave 
them blank and force them to be filled in by the service designer or at runtime.

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n
Sent: Thursday, May 18, 2017 10:27 AM
To: onap-discuss@lists.onap.org
Cc: Aruna kumar padhi >
Subject: Re: [onap-discuss] question on SDC

Hi Tal Halfon,

Thanks for the reply..

i agree with you that during Design-time user can set HEAT env files with 
actual cloud infrastructure details.

But as SDC catalog maintain the Resources(VFC/VNF), Services(VF), products as a 
re-usable building blocks. so i am trying understand how re-suability of these 
building blocks is achieved.
i can think Resources(VNFs) can be reused during Service Design-time(by 
updating the VNFs HEAT env parameters)..
and Service(VF) can be reused during deployment(Run-time) through VID for 
different tenants, so Run-time may be need to modify HEAT env parameters based 
on the tenant.

Please correct me if I am missing something.

Regards,
Ramu N

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

From: Halfon Tal [mailto:halfon@amdocs.com]
Sent: Thursday, May 18, 2017 5:35 PM
To: Ramu n; onap-discuss@lists.onap.org
Cc: Aruna kumar padhi
Subject: RE: [onap-discuss] question on SDC

Hi Ramu

Let me clarify my answer below

- ENV file set default values, so in some case user would want to set values 
that in normal flow will be run time just for making testing/certification 
easier.
Saying the above, ONAP do recommend that for production, HEAT env file will 
include only pseudo constant values (design time parameters) and not run time


Best regards
Tal Halfon

Development Manager @ Amdocs

P. +972 54 2213763

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Halfon Tal
Sent: Thursday, May 18, 2017 2:39 PM
To: Ramu n >; 
onap-discuss@lists.onap.org
Cc: Aruna kumar padhi >
Subject: Re: [onap-discuss] question on SDC

Hi Ramu

Regarding the first Q, The env file in the heat is used as default value, in 
run time different values can be provided.



Best regards
Tal Halfon

Development Manager @ Amdocs

P. +972 54 2213763

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n
Sent: Thursday, May 18, 2017 1:44 PM
To: onap-discuss@lists.onap.org
Cc: Aruna kumar padhi >
Subject: [onap-discuss] question on SDC

Dear All,

1)
as mentioned in 
https://wiki.onap.org/display/DW/Pre-Onboarding
 link, create a tenant and note tenant ID
and in 

Re: [onap-discuss] SDC portal is not accessible with 502 error

[Aayush.Bhatnagar]

Thanks for the update Vitaliy.

The requirement of running on the same host is something which has been done by 
design, or will it change in the future.

Why I ask this question is the fact that once we try to execute HA and Fault 
Tolerant scenarios for individual ONAP components (inclusive of the SDC), the 
hosts may change.

Regards

Aayush


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vitaliy Emporopulo
Sent: 18 May 2017 18:41
To: Ajay Priyadarshi; Elhay Efrat; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Hi Ajay,

Currently a SDC setup expects all of its containers to run on the same host 
(virtual or physical), and access each other via the host's IP address or 
hostname visible inside the containers. This is possible using 
container-to-host port binding.

Apparently, a SDC container cannot reach the others via 172.16.74.83. On the 
other hand, it looks like the BE identifies itself as 10.0.3.1 (see the log), 
which is your private_ip. This also makes perfect sense - the containers should 
talk to each other on the private network, while the public one is exposed for 
external access. Normally that would be the front-end server.

I guess you won't see a 172.16.74.x address if you run ifconfig inside a 
container, except on FE.

To sum up, the configuration of your containers should point to the private 
network IPs for container-to-container communication (FE-to-BE, 
BE-to-Cassandra, etc).

Regards,
Vitaliy

From: ajay.priyadar...@ril.com 
[mailto:ajay.priyadar...@ril.com]
Sent: Thursday, May 18, 2017 15:00
To: Vitaliy Emporopulo 
>; Elhay 
Efrat >; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Hi Vitaliy,

All SDC Docker containers are on single VM.

docker container list
CONTAINER IDIMAGE   
   COMMAND  CREATED STATUS  PORTS   
  NAMES
58421a971a63
nexus3.onap.org:10001/openecomp/sdc-frontend:1.0-STAGING-latest
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp  sdc-FE
35cdccf1abb5
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest 
"/root/startup.sh"   3 hours ago Up 42 minutes   
0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcpsdc-BE
139f5a712d37
nexus3.onap.org:10001/openecomp/sdc-kibana:1.0-STAGING-latest  
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:5601->5601/tcp
sdc-kbn
9b60d4f6fd20
nexus3.onap.org:10001/openecomp/sdc-cassandra:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  7000-7001/tcp, 
0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp   sdc-cs
85b83dec8442
nexus3.onap.org:10001/openecomp/sdc-elasticsearch:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcpsdc-es

<> have correct Ip_address.

Vm1_sdc public_ip:172.16.64.83
Vm1_sdc private_ip: 10.0.3.1

Cassandra sever are running and UP.

BE stderr.log

Last shared stderr logs. I am getting following highlighted

May 18, 2017 11:07:19 AM org.springframework.web.context.ContextLoader 
initWebApplicationContext
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'vendorLicenseManager' defined in ServletContext resource 
[/WEB-INF/beans-services.xml]: Instantiation of bean failed; nested exception 
is java.lang.ExceptionInInitializerError
.
Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All 
host(s) tried for query failed (tried: /172.16.74.83:9042 
(com.datastax.driver.core.TransportException: [/172.16.74.83:9042] Cannot 
connect))
at 
com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:240)
  ...

BE error.log

2017-05-18T11:40:31.762Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:34.763Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:37.762Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:40.763Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=

Re: [onap-discuss] question on SDC

[ROSE, DANIEL V]

You can have sensible defaults in SDC that would apply to basic use cases, but 
properties can be replaced when they are used so someone reusing the service 
can decide if the defaults make sense for them. Or like Tal said, just leave 
them blank and force them to be filled in by the service designer or at runtime.

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n
Sent: Thursday, May 18, 2017 10:27 AM
To: onap-discuss@lists.onap.org
Cc: Aruna kumar padhi 
Subject: Re: [onap-discuss] question on SDC

Hi Tal Halfon,

Thanks for the reply..

i agree with you that during Design-time user can set HEAT env files with 
actual cloud infrastructure details.

But as SDC catalog maintain the Resources(VFC/VNF), Services(VF), products as a 
re-usable building blocks. so i am trying understand how re-suability of these 
building blocks is achieved.
i can think Resources(VNFs) can be reused during Service Design-time(by 
updating the VNFs HEAT env parameters)..
and Service(VF) can be reused during deployment(Run-time) through VID for 
different tenants, so Run-time may be need to modify HEAT env parameters based 
on the tenant.

Please correct me if I am missing something.

Regards,
Ramu N

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

From: Halfon Tal [mailto:halfon@amdocs.com]
Sent: Thursday, May 18, 2017 5:35 PM
To: Ramu n; onap-discuss@lists.onap.org
Cc: Aruna kumar padhi
Subject: RE: [onap-discuss] question on SDC

Hi Ramu

Let me clarify my answer below

- ENV file set default values, so in some case user would want to set values 
that in normal flow will be run time just for making testing/certification 
easier.
Saying the above, ONAP do recommend that for production, HEAT env file will 
include only pseudo constant values (design time parameters) and not run time


Best regards
Tal Halfon

Development Manager @ Amdocs

P. +972 54 2213763

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Halfon Tal
Sent: Thursday, May 18, 2017 2:39 PM
To: Ramu n >; 
onap-discuss@lists.onap.org
Cc: Aruna kumar padhi >
Subject: Re: [onap-discuss] question on SDC

Hi Ramu

Regarding the first Q, The env file in the heat is used as default value, in 
run time different values can be provided.



Best regards
Tal Halfon

Development Manager @ Amdocs

P. +972 54 2213763

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n
Sent: Thursday, May 18, 2017 1:44 PM
To: onap-discuss@lists.onap.org
Cc: Aruna kumar padhi >
Subject: [onap-discuss] question on SDC

Dear All,

1)
as mentioned in 
https://wiki.onap.org/display/DW/Pre-Onboarding
 link, create a tenant and note tenant ID
and in 
https://wiki.onap.org/display/DW/Resource+Onboarding#ResourceOnboarding-CVSPCreateaVendorSoftwareProduct
 link, attach Heat.zip package to the Vendor Software Product which contain 
Heat template & env files.
As the Heat env contains the environment parameters (like Tenant, Network 
details) which are Service provider's cloud infrastructure details.
why these environment parameters need to be provided during 
Design-time(On-boarding), because i think these are required only during 
Run-time(Instantiation).

2)
>From the below diagram, as per my understanding Stage-1(VNF Provider) is out 
>of scope of ONAP, i.e. it is done in VNF Providers development environment.

Re: [onap-discuss] question on SDC

[Ramu n]

Hi Tal Halfon,

Thanks for the reply..

i agree with you that during Design-time user can set HEAT env files with 
actual cloud infrastructure details.

But as SDC catalog maintain the Resources(VFC/VNF), Services(VF), products as a 
re-usable building blocks. so i am trying understand how re-suability of these 
building blocks is achieved.
i can think Resources(VNFs) can be reused during Service Design-time(by 
updating the VNFs HEAT env parameters)..
and Service(VF) can be reused during deployment(Run-time) through VID for 
different tenants, so Run-time may be need to modify HEAT env parameters based 
on the tenant.

Please correct me if I am missing something.

Regards,
Ramu N

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

From: Halfon Tal [mailto:halfon@amdocs.com]
Sent: Thursday, May 18, 2017 5:35 PM
To: Ramu n; onap-discuss@lists.onap.org
Cc: Aruna kumar padhi
Subject: RE: [onap-discuss] question on SDC

Hi Ramu

Let me clarify my answer below

- ENV file set default values, so in some case user would want to set values 
that in normal flow will be run time just for making testing/certification 
easier.
Saying the above, ONAP do recommend that for production, HEAT env file will 
include only pseudo constant values (design time parameters) and not run time


Best regards
Tal Halfon

Development Manager @ Amdocs

P. +972 54 2213763

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Halfon Tal
Sent: Thursday, May 18, 2017 2:39 PM
To: Ramu n >; 
onap-discuss@lists.onap.org
Cc: Aruna kumar padhi >
Subject: Re: [onap-discuss] question on SDC

Hi Ramu

Regarding the first Q, The env file in the heat is used as default value, in 
run time different values can be provided.



Best regards
Tal Halfon

Development Manager @ Amdocs

P. +972 54 2213763

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n
Sent: Thursday, May 18, 2017 1:44 PM
To: onap-discuss@lists.onap.org
Cc: Aruna kumar padhi >
Subject: [onap-discuss] question on SDC

Dear All,

1)
as mentioned in https://wiki.onap.org/display/DW/Pre-Onboarding link, create a 
tenant and note tenant ID
and in 
https://wiki.onap.org/display/DW/Resource+Onboarding#ResourceOnboarding-CVSPCreateaVendorSoftwareProduct
 link, attach Heat.zip package to the Vendor Software Product which contain 
Heat template & env files.
As the Heat env contains the environment parameters (like Tenant, Network 
details) which are Service provider's cloud infrastructure details.
why these environment parameters need to be provided during 
Design-time(On-boarding), because i think these are required only during 
Run-time(Instantiation).

2)
>From the below diagram, as per my understanding Stage-1(VNF Provider) is out 
>of scope of ONAP, i.e. it is done in VNF Providers development environment.
[cid:image001.png@01D2D00F.BF207D30]

Please anyone clarify if my understanding is correct.

Regards,
Ramu N

***
 This e-mail and 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!

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
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

Re: [onap-discuss] [onap-tsc] [ONAP EXTERNAL OPEN SOURCE COMMUNITY COORDINATOR] Election Kickoff

[jamil.chawki]

Hello Team
I would like to nominate myself for the election of ONAP Open Source and SDO 
Coordinator.
In order to accelerate the adoption of ONAP as an industry standard, a strong 
collaboration between ONAP project and major SDOs and open source projects is 
needed. As I am leading cloud computing, NFV and SDN standards and open source 
activities at Orange, I have a solid experience to serve this role. I have 
contributed to the creation of OPNFV with an objective to deliver a 
carrier-grade platform for NFV. I am also involved in the development of ETSI 
NFV specifications as well as the publication of several standards on cloud 
computing, SDN and Big Data in ITU-T and ISO/IEC.
Here after my short bio:

·  Since 2012, Coordinating Orange delegates active in different 
standard organisations like ETSI NFV, IETF, ITU-T SG 13, DMTF, ISO /IEC, 3GPP.

·  Since 2016, OPNFV Board director representing Service Provider 
Silver members.

·  Since 2015, OpenDaylight Advisory group member representing Orange.

·  2012-2016 Chairman of the cloud computing Working Party, in ITU-T 
Study Group 13 ‘Future Networks, SDN and Cloud’

·  2012-2014 Co-convener of the joint Collaborative Team (CT) between 
ITU-T SG13 and ISO IEC/ JTC1 SC38 on Cloud Computing Overview & Vocabulary (ISO 
17788) and Cloud Computing architecture (ISO 17789).

https://www.linkedin.com/in/jamil-chawki-a57a5a3/
https://twitter.com/jchawki

Regards
Jamil Chawki
Orange Labs

De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de Phil Robb
Envoyé : vendredi 12 mai 2017 03:56
À : onap-tsc; onap-discuss@lists.onap.org
Objet : [onap-tsc] [ONAP EXTERNAL OPEN SOURCE COMMUNITY COORDINATOR] Election 
Kickoff

Hello ONAP Community Members:

Please consider this email as the kickoff of the ONAP External Open Source 
Community Coordinator Election process.  A description of the role can be found 
on the ONAP Technical Community Coordinator's page here:  
https://wiki.onap.org/display/DW/Technical+Community+Coordinators

Please recall, as stated in section 5.2.2.2 of the ONAP TSC Charter, any member 
of the technical community is eligible to run for this position.  It is not 
exclusively reserved for TSC Members.  However, only TSC members are eligible 
to vote when choosing among the potential candidates.  This position serves at 
the pleasure of the TSC and TSC Chairperson.

There are two phases to the election process.  The first is the Nomination 
Phase where community members may nominate themselves for the position of "ONAP 
External Open Source Community Coordinator".  Once the Nomination Phase has 
concluded, we will enter the Election Phase, where all ONAP TSC Members are 
invited and encouraged to vote on the candidates whom have been nominated.

Timing:
§  Nominations open May 11th, 2017.
§  Nominations close May 17th at 9:00pm Pacific Time
§  Voting begins May 18th, 2017
§  Voting Ends May 24th, 2017 at 9:00pm Pacific Time

If you wish to nominate yourself for the position of "ONAP External Open Source 
Community Coordinator", please respond-all to this email with your picture 
(headshot), biography, and statement of interest on why you would wish to hold 
the position.  I wlll post this information to the wiki prior to the start of 
the election so that everyone in the technical community is able to become 
familiar with the candidates.

If you have any questions, please do not hesitate to contact me.

Best,

Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

Re: [onap-discuss] [onap-tsc] [ONAP EXTERNAL OPEN SOURCE COMMUNITY COORDINATOR] Election Kickoff

[jamil.chawki]

Hello
I would like to confirm my self-nomination for SDO coordinator
Regards
jamil
De : onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
De la part de jamil.cha...@orange.com
Envoyé : jeudi 18 mai 2017 00:46
À : Phil Robb; onap-tsc; onap-discuss@lists.onap.org
Objet : Re: [onap-tsc] [ONAP EXTERNAL OPEN SOURCE COMMUNITY COORDINATOR] 
Election Kickoff

Hello Team
I would like to nominate myself for the election of ONAP Open Source and SDO 
Coordinator.
In order to accelerate the adoption of ONAP as an industry standard, a strong 
collaboration between ONAP project and major SDOs and open source projects is 
needed. As I am leading cloud computing, NFV and SDN standards and open source 
activities at Orange, I have a solid experience to serve this role. I have 
contributed to the creation of OPNFV with an objective to deliver a 
carrier-grade platform for NFV. I am also involved in the development of ETSI 
NFV specifications as well as the publication of several standards on cloud 
computing, SDN and Big Data in ITU-T and ISO/IEC.
Here after my short bio:

· Since 2012, Coordinating Orange delegates active in different 
standard organisations like ETSI NFV, IETF, ITU-T SG 13, DMTF, ISO /IEC, 3GPP.

·  Since 2016, OPNFV Board director representing Service Provider 
Silver members.

· Since 2015, OpenDaylight Advisory group member representing Orange.

·  2012-2016 Chairman of the cloud computing Working Party, in ITU-T 
Study Group 13 ‘Future Networks, SDN and Cloud’

· 2012-2014 Co-convener of the joint Collaborative Team (CT) between 
ITU-T SG13 and ISO IEC/ JTC1 SC38 on Cloud Computing Overview & Vocabulary (ISO 
17788) and Cloud Computing architecture (ISO 17789).

https://www.linkedin.com/in/jamil-chawki-a57a5a3/
https://twitter.com/jchawki

Regards
Jamil Chawki
Orange Labs

De : onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] De la part de Phil Robb
Envoyé : vendredi 12 mai 2017 03:56
À : onap-tsc; onap-discuss@lists.onap.org
Objet : [onap-tsc] [ONAP EXTERNAL OPEN SOURCE COMMUNITY COORDINATOR] Election 
Kickoff

Hello ONAP Community Members:

Please consider this email as the kickoff of the ONAP External Open Source 
Community Coordinator Election process.  A description of the role can be found 
on the ONAP Technical Community Coordinator's page here:  
https://wiki.onap.org/display/DW/Technical+Community+Coordinators

Please recall, as stated in section 5.2.2.2 of the ONAP TSC Charter, any member 
of the technical community is eligible to run for this position.  It is not 
exclusively reserved for TSC Members.  However, only TSC members are eligible 
to vote when choosing among the potential candidates.  This position serves at 
the pleasure of the TSC and TSC Chairperson.

There are two phases to the election process.  The first is the Nomination 
Phase where community members may nominate themselves for the position of "ONAP 
External Open Source Community Coordinator".  Once the Nomination Phase has 
concluded, we will enter the Election Phase, where all ONAP TSC Members are 
invited and encouraged to vote on the candidates whom have been nominated.

Timing:
§  Nominations open May 11th, 2017.
§  Nominations close May 17th at 9:00pm Pacific Time
§  Voting begins May 18th, 2017
§  Voting Ends May 24th, 2017 at 9:00pm Pacific Time

If you wish to nominate yourself for the position of "ONAP External Open Source 
Community Coordinator", please respond-all to this email with your picture 
(headshot), biography, and statement of interest on why you would wish to hold 
the position.  I wlll post this information to the wiki prior to the start of 
the election so that everyone in the technical community is able to become 
familiar with the candidates.

If you have any questions, please do not hesitate to contact me.

Best,

Phil.
--
Phil Robb
Executive Director, OpenDaylight Project
VP Operations - Networking & Orchestration, The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb

_



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

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

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

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



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

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

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

[onap-discuss] SDNC project build issue

[Tapan Majhi]

I am trying to build sdnc/northbound project taking the latest code.

Earlier its was working fine but now with the latest code I am getting below 
error.

[INFO] SDN-C Northbound APIs .. SUCCESS [  5.603 s]
[INFO] asdcApi  SUCCESS [  0.217 s]
[INFO] asdcApi-model .. SUCCESS [ 19.336 s]
[INFO] asdcApi-provider ... SUCCESS [ 24.822 s]
[INFO] asdcApi-features ... SUCCESS [  2.391 s]
[INFO] asdcApi  - Karaf  Installer  FAILURE [  0.757 s]
[INFO] dataChange . SKIPPED
[INFO] dataChange-model ... SKIPPED
[INFO] dataChange-provider  SKIPPED
[INFO] dataChange-features  SKIPPED
[INFO] dataChange  - Karaf  Installer . SKIPPED
[INFO] DMAAP Listener . SKIPPED
[INFO] UEB Listener ... SKIPPED
[INFO] vnfapi . SKIPPED
[INFO] vnfapi-model ... SKIPPED
[INFO] vnfapi-provider  SKIPPED
[INFO] vnfapi-features  SKIPPED
[INFO] VNF API  - Karaf  Installer  SKIPPED
[INFO] VNF Tools Plugin ... SKIPPED
[INFO] VNF Tools Plugin - Provider  SKIPPED
[INFO] VNF tools Plugin - Features  SKIPPED
[INFO] VNF Tools Plugin  - Karaf  Installer ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 57.250 s
[INFO] Finished at: 2017-05-18T09:12:01-04:00
[INFO] Final Memory: 106M/254M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.4.1:single (maven-repo-zip) on 
project asdcApi-installer: Assembly is incorrectly configured: null: Assembly 
is incorrectly configured: null:
[ERROR] Assembly: null is not configured correctly: Assembly ID must be present 
and non-empty.
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.4.1:single (maven-repo-zip) on 
project asdcApi-installer: Assembly is incorrectly configured: null
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoFailureException: Assembly is 
incorrectly configured: null
at 
org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:479)
at 
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
[ERROR]

Anyone facing similar issue? Or any clue how to 

Re: [onap-discuss] SDC portal is not accessible with 502 error

[Vitaliy Emporopulo]

Hi Ajay,

Currently a SDC setup expects all of its containers to run on the same host 
(virtual or physical), and access each other via the host's IP address or 
hostname visible inside the containers. This is possible using 
container-to-host port binding.

Apparently, a SDC container cannot reach the others via 172.16.74.83. On the 
other hand, it looks like the BE identifies itself as 10.0.3.1 (see the log), 
which is your private_ip. This also makes perfect sense - the containers should 
talk to each other on the private network, while the public one is exposed for 
external access. Normally that would be the front-end server.

I guess you won't see a 172.16.74.x address if you run ifconfig inside a 
container, except on FE.

To sum up, the configuration of your containers should point to the private 
network IPs for container-to-container communication (FE-to-BE, 
BE-to-Cassandra, etc).

Regards,
Vitaliy

From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Thursday, May 18, 2017 15:00
To: Vitaliy Emporopulo ; Elhay Efrat 
; onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Hi Vitaliy,

All SDC Docker containers are on single VM.

docker container list
CONTAINER IDIMAGE   
   COMMAND  CREATED STATUS  PORTS   
  NAMES
58421a971a63
nexus3.onap.org:10001/openecomp/sdc-frontend:1.0-STAGING-latest
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:8181->8181/tcp, 8080/tcp, 0.0.0.0:9443->9443/tcp  sdc-FE
35cdccf1abb5
nexus3.onap.org:10001/openecomp/sdc-backend:1.0-STAGING-latest 
"/root/startup.sh"   3 hours ago Up 42 minutes   
0.0.0.0:8080->8080/tcp, 0.0.0.0:8443->8443/tcpsdc-BE
139f5a712d37
nexus3.onap.org:10001/openecomp/sdc-kibana:1.0-STAGING-latest  
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:5601->5601/tcp
sdc-kbn
9b60d4f6fd20
nexus3.onap.org:10001/openecomp/sdc-cassandra:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  7000-7001/tcp, 
0.0.0.0:9042->9042/tcp, 7199/tcp, 0.0.0.0:9160->9160/tcp   sdc-cs
85b83dec8442
nexus3.onap.org:10001/openecomp/sdc-elasticsearch:1.0-STAGING-latest   
"/root/startup.sh"   3 hours ago Up 3 hours  
0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcpsdc-es

<> have correct Ip_address.

Vm1_sdc public_ip:172.16.64.83
Vm1_sdc private_ip: 10.0.3.1

Cassandra sever are running and UP.

BE stderr.log

Last shared stderr logs. I am getting following highlighted

May 18, 2017 11:07:19 AM org.springframework.web.context.ContextLoader 
initWebApplicationContext
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'vendorLicenseManager' defined in ServletContext resource 
[/WEB-INF/beans-services.xml]: Instantiation of bean failed; nested exception 
is java.lang.ExceptionInInitializerError
.
Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All 
host(s) tried for query failed (tried: /172.16.74.83:9042 
(com.datastax.driver.core.TransportException: [/172.16.74.83:9042] Cannot 
connect))
at 
com.datastax.driver.core.ControlConnection.reconnectInternal(ControlConnection.java:240)
  ...

BE error.log

2017-05-18T11:40:31.762Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:34.763Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:37.762Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:40.763Z|||ES-Health-Check-Thread||ASDC-BE||ERROR|||10.0.3.1||o.o.sdc.be.dao.impl.ESCatalogDAO||ActivityType=,
 Desc=
2017-05-18T11:40:41.437Z|||Titan-Reconnect-Task||ASDC-BE||INFO|||10.0.3.1||o.o.s.be.dao.titan.TitanGraphClient||ActivityType=,
 Desc=
2017-05-18T11:40:41.437Z|||Titan-Reconnect-Task||ASDC-BE||INFO|||10.0.3.1||o.o.s.be.dao.titan.TitanGraphClient||ActivityType=,
 Desc=<** createGraph with /var/lib/jetty/config/catalog-be/titan.properties 
and initializeGraph=true started>
2017-05-18T11:40:41.437Z|||Titan-Reconnect-Task||ASDC-BE||INFO|||10.0.3.1||o.o.s.be.dao.titan.TitanGraphClient||ActivityType=,
 Desc=
2017-05-18T11:40:41.439Z|||Titan-Reconnect-Task||ASDC-BE||INFO|||10.0.3.1||c.n.a.c.i.CountingConnectionPoolMonitor||ActivityType=,
 Desc=
2017-05-18T11:40:41.783Z|||UEBConsumerThread||ASDC-BE||INFO|||10.0.3.1||c.att.nsa.apiClient.http.HttpClient||ActivityType=,
 Desc=<   --> HTTP/1.1 200 

Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

[Kedar Ambekar]

Hi Daniel,

Thanks for reply !


1.   In zip file uploaded, I had base_vlb_rackspace and 
dnsscaling_rackspace files.

2.   I did demo.sh preload for 
K-demoVLB-Module.

3.   In Add VF Module, I chose base_vlb and created a VF Module with name 
K-demoVLB-Module.
 I did not do Add VF Module for dns_scaling.

4.   I created a separate heat stack for packet_gen_vlb_rackspace of name  
K-demoVLB-PackGen
 using Heat client.

5.   When I do demo.sh appc K-demoVLB-Module, I got error  Dictionary does 
not contain key 'vpg_name_0'.

6.   I tried to do demo.sh appc on 
K-demoVLB-PackGen
 as well. That time it gave error Dictionary does not contain key 
'vpg_private_ip_1'.


In vLB use case, the mounting of traffic generator to enable policy driven 
configuration changes (demo.sh appc) should be done on which VF-Module ? In my 
example, 
K-demoVLB-PackGen
 or K-demoVLB-Module ?

The architecture diagram on wiki for vLB 
(https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos) does 
not show APPC involved and directing packet generator using NETCONF. Is it 
expected ? If yes, how DNS VM scale up-down is demonstrated in that case ?

In same diagram, what is the use of honeycomb on vLB VM ?

KeDar Ambekar | Network Services | Tech Mahindra
• Desk: +91 20 66018100 x 2879   Mobile: +91 95616 50414

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Thursday, May 18, 2017 12:09 AM
To: Kedar Ambekar ; onap-discuss@lists.onap.org
Subject: RE: Re:RE: Query on vlb_ipaddr parameter of vLB usecase

They may both be there, but you wont have to do the second one through VID. 
Policy will do it for you


Thanks,

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: Kedar Ambekar [mailto:ake...@techmahindra.com]
Sent: Wednesday, May 17, 2017 2:38 PM
To: onap-discuss@lists.onap.org; Kedar 
Ambekar >; ROSE, DANIEL 
V >
Subject: Re:RE: Query on vlb_ipaddr parameter of vLB usecase

In my case, I think VID has loaded. both as I get 2 options to create VF module.



Sent from my Mi phone
On "ROSE, DANIEL V" >, May 17, 2017 11:00 
PM wrote:
Hi Kedar

you should just have to run it on the one vid loads.
Before running the closed loop you will have to run demo.sh appc command though

Thanks,

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Wednesday, May 17, 2017 9:25 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel,

As a VSP for vLB, I have uploaded zip containing dnsscaling_rackspace and 
base_vlb_rackspace yaml & env files. In Add VF-Module menu, I get 2 options, 
one for base_vlb and other for dns_scaling.

For both, am I supposed to run steps demo.sh preload,  add VF-Modules,  demo.sh 
appc ?

I have manually created manifest file (attached) as I am not sure which 
generate-manifest.py to use. Is this file ok ?

Regards,
KeDar

From: ROSE, DANIEL V [mailto:dr6...@att.com]
Sent: Monday, May 15, 2017 10:44 PM
To: Kedar Ambekar >; 
onap-discuss@lists.onap.org
Subject: RE: Query on vlb_ipaddr parameter of vLB usecase

Yeah, that’s how testing does it.

Daniel Rose
ECOMP / ONAP
com.att.ecomp
732-420-7308

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Monday, May 15, 2017 12:57 PM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel,

Ok. So zip file containing dnsscaling_rackspace and base_vlb_rackspace should 
be on-boarded in SDC ?

And then packet generator heat template could be installed with some heat 
client separately.

Regards,
KeDar
From: 

Re: [onap-discuss] question on SDC

[Halfon Tal]

Hi Ramu

Regarding the first Q, The env file in the heat is used as default value, in 
run time different values can be provided.



Best regards
Tal Halfon

Development Manager @ Amdocs

P. +972 54 2213763

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ramu n
Sent: Thursday, May 18, 2017 1:44 PM
To: onap-discuss@lists.onap.org
Cc: Aruna kumar padhi 
Subject: [onap-discuss] question on SDC

Dear All,

1)
as mentioned in https://wiki.onap.org/display/DW/Pre-Onboarding link, create a 
tenant and note tenant ID
and in 
https://wiki.onap.org/display/DW/Resource+Onboarding#ResourceOnboarding-CVSPCreateaVendorSoftwareProduct
 link, attach Heat.zip package to the Vendor Software Product which contain 
Heat template & env files.
As the Heat env contains the environment parameters (like Tenant, Network 
details) which are Service provider's cloud infrastructure details.
why these environment parameters need to be provided during 
Design-time(On-boarding), because i think these are required only during 
Run-time(Instantiation).

2)
>From the below diagram, as per my understanding Stage-1(VNF Provider) is out 
>of scope of ONAP, i.e. it is done in VNF Providers development environment.
[cid:image001.png@01D2CFE4.42DA46A0]

Please anyone clarify if my understanding is correct.

Regards,
Ramu N

***
 This e-mail and 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!

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