from:"PLATANIA, MARCO $MARCO$"

Re: [onap-discuss] vFWCL instantiation problem (not allowed to create an int on ext net)

2018-05-05 Thread PLATANIA, MARCO (MARCO)

The issue is that your openstack platform is not configured to allow VMs to be 
directly attached to the external or provider network. I don’t know how to 
change this configuration in openstack but I’m pretty positive that that is the 
issue.

Marco




On Sat, May 5, 2018 at 11:21 AM -0400, "Badr Eddine Aouled Yahia" 
> 
wrote:

Hello,

I am playing the vFWCL use-case on Amsterdam release and i am now on the step 
of the creation of the VF modules, i have done all the previous steps 
successfully and now i am facing this problem:
when creating the vf modules, i get number of attemps exceeded, but thes 
problems is exactly the creation of an external interface for the VMs to access 
the public net.
I watched the VMs on openstack created successefully but when it comes to 
attribute ips, it rolls back

on the mso container in var/log/ecomp/MSO/VnfAdapter/
 logs, i fount this exception "It is not allowed to create an interface on 
external network"

I doubt that there is a problem in the heat templates because i have deployed a 
simple service with a single vnf (freeRadius) with well configured resources 
and parameters (router interface, floating ip ...) in the heat templates.
In the vFW heat templates, this kid of parameters and resources is not 
specified but all the tutorials in ONAP does not add any resources or 
parameters to the vFWCL heat so i am a little bit confused.

Does anyone have an idea how to solve this problem without the need to modify 
the heats for the vFWCL with hardcoded things?
or even to what this problem could be related?

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

Re: [onap-discuss] SDC deployment on heat and OOM

2018-05-03 Thread PLATANIA, MARCO (MARCO)

Michael,

The issue with the Heat deployment is that connection to Gerrit timed out, so 
the SDC repo hasn’t been cloned:

fatal: unable to access 'http://gerrit.onap.org/r/sdc.git/': Failed to connect 
to gerrit.onap.org port 80: Connection timed out

As a consequence, sdc_vm_init.sh couldn’t find deploy.sh. I just cloned it 
manually and redeployed SDC. Yesterday, we experienced network instability. 
Consider that the clone operation this morning succeeded after a few failed 
attempts. I’m not sure whether the network has healed completely.

Marco

From: "LANDO, MICHAEL" <ml6...@intl.att.com>
Date: Thursday, May 3, 2018 at 5:55 AM
To: 'Yunxia Chen' <helen.c...@huawei.com>, Gary Wu <gary.i...@huawei.com>, 
"OBRIEN, FRANK MICHAEL" <frank.obr...@amdocs.com>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>, Mike Elliott <mike.elli...@amdocs.com>, 'Roger 
Maitland' <roger.maitl...@amdocs.com>
Cc: BRIAN FREEMAN <bf1...@att.com>, "NACHMIAS, LIOR" <ln6...@intl.att.com>, 
"'onap-discuss@lists.onap.org'" <onap-discuss@lists.onap.org>, "RATZ, YAKI" 
<yr9...@intl.att.com>, "FUSS, ARELI" <af7...@intl.att.com>
Subject: SDC deployment on heat and OOM

Hi,

After Gary explained to me how I can login into the external labs I started 
checking our deployment there.

Heat:

It looks like on the last heat deployment execution 
https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-heat-deploy/259/consoleFull

The SDC was not even started I logged into the VM that was assigned to SDC 
10.12.5.83 and our docker startup script was not even executed as far as I can 
see since :
root@onap-sdc:~# docker ps -a
CONTAINER IDIMAGE   COMMAND CREATED 
STATUS  PORTS   NAMES
root@onap-sdc:~#

as a result our health check is shown as failing which is not the case.
What is the cause? What failed?

OOM:

https://jenkins.onap.org/view/External%20Labs/job/lab-windriver-beijing-oom-deploy/339/console

from what I see the job and the health check was completed at 8:30 utc when I 
logged into the Machin I can see that it took SDC started successful with no 
intervention (Thank you OOM team) and that last docker came up at 09:14:09 utc.
As a result our health check is marked as failed which is not the case since I 
was able to log into the sdc fe docker and validate the health check is passing.

How can this be addressed can we prolong the job execution or the number of 
retries for the health check? I am more than sure the SDC is not the only 
application that fails because of this.

Side note:
I tried executing the health check from out side the docker but probably I am 
missing something in connection to the K8 networking since I was unable to 
connect.
I tried curl http://sdc-fe.onap:8181/sdc1/rest/healthCheck as the health check 
does.













BR,

[ichael Lando]

AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: michael.la...@intl.att.com<mailto:michael.la...@intl.att.com>

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

Re: [onap-discuss] [integration] Problem with integration repo

2018-04-05 Thread PLATANIA, MARCO (MARCO)

We modified ONAP install scripts but I don’t think they impact that file, 
considering that install scripts run in the VMs after they are created and have 
no relationships with other files in Gerrit. I’m not sure whether the manifest 
file in the Integration repo may create that issue, perhaps Gary can chime in, 
but I don’t think so.

Marco

From: Yunxia Chen <helen.c...@huawei.com>
Date: Thursday, April 5, 2018 at 11:21 AM
To: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, "PLATANIA, MARCO 
(MARCO)" <plata...@research.att.com>, Gary Wu <gary.i...@huawei.com>
Subject: Re: [onap-discuss] [integration] Problem with integration repo

Hi, Marco & Gary,
Does this have anything to do with those scripts you created?

Regards,

Helen Chen

From: <onap-discuss-boun...@lists.onap.org> on behalf of "DRAGOSH, PAMELA L 
(PAM)" <pdrag...@research.att.com>
Date: Thursday, April 5, 2018 at 8:03 AM
To: onap-discuss <onap-discuss@lists.onap.org>
Subject: [onap-discuss] [integration] Problem with integration repo

Hi Integration team,

I am trying to update the integration version manifest, but I am having 
difficulty with a particular file that seems to automatically get modified 
every time I do a clean clone or checkout:

test/csit/plans/vfc-nfvo-wfengine/sanity-check/testplan.txt

Even when I start from scratch with a brand new clone this file is modified on 
a fresh clone. When I try to stash it I get this issue:

warning: CRLF will be replaced by LF in 
test/csit/plans/vfc-nfvo-wfengine/sanity-check/testplan.txt.
The file will have its original line endings in your working directory.
Saved working directory and index state WIP on master: b5529a6 Changes to match 
OOM refactoring
HEAD is now at b5529a6 Changes to match OOM refactoring

But git still thinks I have modified it, while I have not. Is the CRLF work 
around for this?

I am working on MacOS.

Thanks,

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

Re: [onap-discuss] vFWCL and vLB demo files in Nexus

2018-03-20 Thread PLATANIA, MARCO (MARCO)

Bharath, David,

We noticed the issue and are currently talking to Jess from LF to find a 
solution. The VES5 files and vLB/vFW VES clients have been all updated, but the 
latter doesn’t show up in the staging repo. As workaround, please set the VNF 
Heat env files as follows:
  repo_url_artifacts: 
https://nexus.onap.org/content/repositories/autorelease-43645
  demo_artifacts_version: 1.2.0
  install_script_version: 1.2.0-SNAPSHOT

This should work for Amsterdam and master. Please let me know if you have 
problems.

Thanks,
Marco

From:  on behalf of Cipher Cipher 

Date: Tuesday, March 20, 2018 at 1:57 PM
To: "david.perezcapar...@swisscom.com" , 
"onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] vFWCL and vLB demo files in Nexus

Hi

I am also waiting this change to reflect in tar.  But the change in gerrit is 
merged to master. I am wondering whether to cherry pick to amsterdam ?

Can anyone explain how these versions like 1.2.0 is mapped to git branches amd 
how these versions are generated

Best Regards
Bharath T

On Tue, 20 Mar 2018 at 11:05 PM, 
> 
wrote:
Hi all,

vpp_measurement_reporter.c in the vFWCL and vLB demos was recently updated 
(https://jira.onap.org/browse/CERT-12).
Tar files under 
https://nexus.onap.org/content/groups/staging/org/onap/demo/vnf/ves5/
  should also be updated to incorporate the latest version of it so that 
cloud-init scripts exit correctly during demo VMs provisioning.

David

--
David Pérez Caparrós
Senior Innovation Engineer
Swisscom (Switzerland)
david.perezcapar...@swisscom.com

___
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] FW: vPacketGen

2018-02-21 Thread PLATANIA, MARCO (MARCO)

Yes, all the demo VNFs for vFW and vLB/vDNS use cases can be considered L4.

Marco

From:  on behalf of Michael O'Brien 

Date: Wednesday, February 21, 2018 at 12:30 PM
To: "onap-discuss@lists.onap.org" 
Cc: "eric.dm...@wipro.com" 
Subject: [onap-discuss] FW: vPacketGen

I would expect yes layer 4 VM (no L3 router level here).
Adding community
/michael

From: eric.dm...@wipro.com [mailto:eric.dm...@wipro.com]
Sent: Wednesday, February 21, 2018 12:27
To: Michael O'Brien 
Cc: joe.kid...@5thlayer.com
Subject: vPacketGen

Hello, will a vPacketgen server that generate traffic be classified as a L4+ 
device?

Eric Maye

470-274-4670
The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. 
www.wipro.com
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] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

2018-02-20 Thread PLATANIA, MARCO (MARCO)

All the components in Heat already have ping-utils, vim and nslookup. Not sure 
about the Centos VMs for DCAE, need to check with Lusheng.

Marco

From: Kang Xi <kang...@huawei.com>
Date: Tuesday, February 20, 2018 at 11:02 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, BRIAN FREEMAN 
<bf1...@att.com>
Cc: onap-discuss <onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [integration] INT-261: Add standard utilities to 
all dockers (vim, ping, nslookup)

Hi Marco,

I agree with you. Actually I did check the size and found the total is less 
than 5MB. Is there also an easy solution for heat?

Regards,
Kang

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Tuesday, February 20, 2018 10:58
To: Kang Xi <kang...@huawei.com>; FREEMAN, BRIAN D <bf1...@att.com>
Cc: onap-discuss <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [integration] INT-261: Add standard utilities to 
all dockers (vim, ping, nslookup)

Hi Kang,

Those tools don’t really require too much space in a docker image, so size 
shouldn’t be a problem. I don’t think we need to modify the docker images, we 
could create init containers in kubernetes that install those tools for the 
ONAP components that need them.

Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Kang Xi <kang...@huawei.com<mailto:kang...@huawei.com>>
Date: Tuesday, February 20, 2018 at 10:38 AM
To: BRIAN FREEMAN <bf1...@att.com<mailto:bf1...@att.com>>
Cc: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [integration] INT-261: Add standard utilities to all 
dockers (vim, ping, nslookup)

Hi Brian, All,

We have a backlog jira ticket asking to install standard utilities to all 
dockers.
https://jira.onap.org/browse/INT-261<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_INT-2D261=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=SIDtjRhzdznWsLmsHqy4fafBi8RZUWe4XJlUYPMbWbI=tRBXDFUKW30iWCNKP3P9x_6jg-HN8_AH4Pdspuq8FOo=>

This issue was discussed at today’s Integration weekly meeting. Some concerns 
were raised that it would inflate the size and increate maintenance work for 
the production version as how to turn on/off installing those packages. Another 
question is that it might not be needed for all the dockers.

There is no doubt that having those tools will make debug and test more 
productive. Do you think it is possible to add the tools to a few most 
demanding dockers? If yes, please specify a list and I’ll follow up on this. 
Immediately I have the controller dockers in SDNC/APPC and mso docker in SO.

Regards,
Kang

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

Re: [onap-discuss] [integration] INT-261: Add standard utilities to all dockers (vim, ping, nslookup)

2018-02-20 Thread PLATANIA, MARCO (MARCO)

Hi Kang,

Those tools don’t really require too much space in a docker image, so size 
shouldn’t be a problem. I don’t think we need to modify the docker images, we 
could create init containers in kubernetes that install those tools for the 
ONAP components that need them.

Marco

From:  on behalf of Kang Xi 

Date: Tuesday, February 20, 2018 at 10:38 AM
To: BRIAN FREEMAN 
Cc: onap-discuss 
Subject: [onap-discuss] [integration] INT-261: Add standard utilities to all 
dockers (vim, ping, nslookup)

Hi Brian, All,

We have a backlog jira ticket asking to install standard utilities to all 
dockers.
https://jira.onap.org/browse/INT-261

This issue was discussed at today’s Integration weekly meeting. Some concerns 
were raised that it would inflate the size and increate maintenance work for 
the production version as how to turn on/off installing those packages. Another 
question is that it might not be needed for all the dockers.

There is no doubt that having those tools will make debug and test more 
productive. Do you think it is possible to add the tools to a few most 
demanding dockers? If yes, please specify a list and I’ll follow up on this. 
Immediately I have the controller dockers in SDNC/APPC and mso docker in SO.

Regards,
Kang

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

Re: [onap-discuss] http://:667 Site Can't Be Reached - Debug

2018-02-15 Thread PLATANIA, MARCO (MARCO)

Hi Stephen,

What kind of response do you get when you try to access that port? We don’t 
have a specific way to debug that service. We noticed that sometimes cloud-init 
doesn’t run as expected. In these cases we just reboot the affected VM.

Marco

From:  on behalf of "Gooch, Stephen" 

Date: Thursday, February 15, 2018 at 3:17 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] http://:667 Site Can't Be Reached 
- Debug

Hello,

After deploying the vFWCL demo, all three VMs are active and respond to a ping 
from external network.  However when attempting to look at the SNK VM’s graph 
on port :667, nothing is displayed.

Is there a procedure for debugging the lack of html service on port 667?

Br,
- Stephen

Stephen Gooch | Senior Member of Technical Staff | Wind River
+1.510.965.7909 , Skype ID: Stephen.gooch

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

Re: [onap-discuss] vFW Closed Loop: Canot capture all the packets in the Graph

2018-02-15 Thread PLATANIA, MARCO (MARCO)

Hi Bharath,

For your records, the error below is not really an error:

./v_firewall_init.sh: line 67: /var/lib/honeycomb/persist/context/data.json: No 
such file or directory
./v_firewall_init.sh: line 68: /var/lib/honeycomb/persist/config/data.json: No 
such file or directory

It tries to delete any Honeycomb pre-existing state before starting it.

Marco

From: "Thiruveedula, Bharath" <bharath.thiruveed...@verizon.com>
Date: Thursday, February 15, 2018 at 4:26 AM
To: onap-discuss <onap-discuss@lists.onap.org>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>
Cc: Kranthi Guttikonda <kranthi.guttiko...@b-yond.com>, "VENKATESH KUMAR, 
VIJAY" <vv7...@att.com>
Subject: Re: vFW Closed Loop: Canot capture all the packets in the Graph

Hi.

The issue was solved by just rebooting sink VM.

Best Regards
Bharath T

On Wed, Feb 14, 2018 at 8:18 PM, Thiruveedula, Bharath 
<bharath.thiruveed...@verizon.com<mailto:bharath.thiruveed...@verizon.com>> 
wrote:
Hi team,

I am trying to setup closed loop using vFWCL package. I launched both vfwsnk 
and vpg. But I couldn't see the packet flows in the sink graph. The below is 
the screenshot from the sink portal

[nline image 1]

If you see, the packets are being captured(3,417 captured), but only showing 10 
packets.

I logged into Sink VM, and ran tcpdump on eth1 and eth2 interface: Please find 
the logs below:

root@zdfw1fwl01snk01:~# tcpdump -i eth2
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2, link-type EN10MB (Ethernet), capture size 262144 bytes
14:37:15.612245 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, bad 
length 120 > 1
14:37:15.618444 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, bad 
length 120 > 1
14:37:15.632497 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, bad 
length 120 > 1
14:37:15.633028 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, bad 
length 120 > 1
14:37:15.633882 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, bad 
length 120 > 1
14:37:15.637333 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, bad 
length 120 > 1
14:37:15.641411 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, bad 
length 120 > 1



root@zdfw1fwl01snk01:~# tcpdump -i eth1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes
14:39:48.313554 ARP, Request who-has 192.168.20.250 tell 
is008820.domain.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__is008820.domain.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=N1H36VucH4ndPKEt_Ruk_aKGzEEUHsPMs1Kc93wlgcQ=lVLzbwd2lq5qeZgOfyJOBSzf7g-Qstd0nThmNTixo0k=>,
 length 46
14:39:48.319791 ARP, Request who-has 192.168.20.250 tell 
is008820.domain.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__is008820.domain.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=N1H36VucH4ndPKEt_Ruk_aKGzEEUHsPMs1Kc93wlgcQ=lVLzbwd2lq5qeZgOfyJOBSzf7g-Qstd0nThmNTixo0k=>,
 length 46
14:39:48.333847 ARP, Request who-has 192.168.20.250 tell 
is008820.domain.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__is008820.domain.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=N1H36VucH4ndPKEt_Ruk_aKGzEEUHsPMs1Kc93wlgcQ=lVLzbwd2lq5qeZgOfyJOBSzf7g-Qstd0nThmNTixo0k=>,
 length 46
14:39:48.335237 ARP, Request who-has 192.168.20.250 tell 
is008820.domain.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__is008820.domain.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=N1H36VucH4ndPKEt_Ruk_aKGzEEUHsPMs1Kc93wlgcQ=lVLzbwd2lq5qeZgOfyJOBSzf7g-Qstd0nThmNTixo0k=>,
 length 46
14:39:48.338654 ARP, Request who-has 192.168.20.250 tell 
is008820.domain.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__is008820.domain.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=N1H36VucH4ndPKEt_Ruk_aKGzEEUHsPMs1Kc93wlgcQ=lVLzbwd2lq5qeZgOfyJOBSzf7g-Qstd0nThmNTixo0k=>,
 length 46
14:39:48.342786 ARP, Request who-has 192.168.20.250 tell 
is008820.domain.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__is008820.domain.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=N1H36VucH4ndPKEt_Ruk_aKGzEEUHsPMs1Kc93wlgcQ=lVLzbwd2lq5qeZgOfyJOBSzf7g-Qstd0nThmNTixo0k=>,
 length 46


And the route table has the following route too:
192.168.10.0192.168.20.100  255.255.255.0   UG0  00 eth0

I couldn't get  the issue of why it is not showing up in the graphs. In the 
cloud init script I got the only error in firewall and packetgen

./v_firewall_init.sh: line 67: /var/lib/honeycomb/persist/context/data.json: No 
such file or directory
./v_firewall_init.sh: line 68: /var/lib/honeycomb/persist/config/data.json: No 
such file or directory


Plea

[onap-discuss] SO issues with keystone

2018-02-02 Thread PLATANIA, MARCO (MARCO)

All,

I’m instantiating VNFs in a remote OpenStack lab called RegionTwo. I modified 
mso-docker.config appropriately. See below:

"mso-po-adapter-config":
{
  "identity_services":
  [
{
  "dcp_clli": "DEFAULT_KEYSTONE",
  "identity_url": "http://135.197.225.10:35357/v2.0;,
  "mso_id": "admin",
  "mso_pass": "a83e2b8446193c5ac450d84f0f1dc711",
  "admin_tenant": "service",
  "member_role": "admin",
  "tenant_metadata": "true",
  "identity_server_type": "KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD"
},
{
  "dcp_clli": "DEFAULT_KEYSTONE2",
  "identity_url": "http:// 135.197.220.71:5000/v3",
  "mso_id": "marco",
  "mso_pass": "f461eb3230f0b4b7b1ce8ed018da155f",
  "admin_tenant": "service",
  "member_role": "admin",
  "tenant_metadata": "true",
  "identity_server_type": "KEYSTONE",
  "identity_authentication_type": "USERNAME_PASSWORD"
}
  ],

  "cloud_sites":
  [
{
  "id": "RegionOne",
  "aic_version": "2.5",
  "lcp_clli": "RegionOne",
  "region_id": "RegionOne",
  "identity_service_id": "DEFAULT_KEYSTONE"
},
{
  "id": "RegionTwo",
  "aic_version": "2.5",
  "lcp_clli": "RegionTwo",
  "region_id": "RegionTwo",
  "identity_service_id": "DEFAULT_KEYSTONE2"
}
  ],

When I try to install a VNF, I receive the following error from SO:

2018-02-02T18:21:48.847Z|0d1b96a0-9fbe-4d1a-a197-4eebd4041c5f|Thread-282|CreateVfModule|BPELClient|Openstack||ERROR|DataError|Openstack
 Keystone Error on TokenAuth|MSO-RA-9202E Exception communicating with 
Openstack Keystone Error on TokenAuth: Error [code=404, title=Not Found, 
message=The resource could not be found.]: {1}

2018-02-02T18:21:48.848Z|0d1b96a0-9fbe-4d1a-a197-4eebd4041c5f|Thread-282|CreateVfModule|BPELClient|Openstack||ERROR|AvailabilityError|Connection
 Exception|MSO-RA-9202E Exception communicating with OpenStack: Openstack 
Exception on Token request: 404 Not Found: The resource could not be found.

2018-02-02T18:21:48.849Z|0d1b96a0-9fbe-4d1a-a197-4eebd4041c5f|Thread-282|CreateVfModule|BPELClient|OpenStack|queryStack|ERROR|DataError|Exception
 - queryStack|MSO-RA-9227E Exception while query VNF:Vfmodule_vLB-0201 in 
RegionTwo/c236140a3dff4911bb4c7c86940616cc

2018-02-02T18:21:48.850Z|0d1b96a0-9fbe-4d1a-a197-4eebd4041c5f|Thread-282|CreateVfModule|BPELClient|OpenStack|queryStack|ERROR|DataError|Exception
 - queryStack|MSO-RA-9200E Exception: 404 Not Found: The resource could not be 
found. - at 
org.openecomp.mso.openstack.utils.MsoCommonUtils.keystoneErrorToMsoException(MsoCommonUtils.java:173)
 - at 
org.openecomp.mso.openstack.utils.MsoHeatUtils.getHeatClient(MsoHeatUtils.java:996)
 - at 
org.openecomp.mso.openstack.utils.MsoHeatUtils.queryStack(MsoHeatUtils.java:646)
 - at 
org.openecomp.mso.adapters.vnf.MsoVnfAdapterImpl.createVfModule(MsoVnfAdapterImpl.java:788)
 - at 
org.openecomp.mso.adapters.vnf.VnfAdapterRest$CreateVfModuleTask.run(VnfAdapterRest.java:388)
 - at java.lang.Thread.run(Thread.java:748) -

Does someone know when this error happens in SO? It seems resource not found 
when talking to keystone, but the OpenStack lab has all the endpoints 
configured correctly and also RegionTwo/c236140a3dff4911bb4c7c86940616cc 
exists. CLI operations against OpenStack work as expected. Note that this 
OpenStack lab uses Keystone v3. Is that supported in SO?

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

Re: [onap-discuss] [EXTERNAL] Service distribution error on latest ONAP/OOM

2018-01-31 Thread PLATANIA, MARCO (MARCO)

Alexis,

Another issue that I see after rebuilding SDC is that Portal cannot access it. 
I received connection timeout when it tries to resolve sdc.api.simpledemo.org. 
This SDC is healthy and using dmaap.onap-message-router as UEB endpoint.

Marco

From:  on behalf of Alexis de Talhouët 

Date: Wednesday, January 31, 2018 at 8:18 AM
To: "Ramanarayanan, Karthick" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM

Hello Karthick, Brian

I think, thanks to Marco, we have identified one piece of the problem.
I guess you guys are running a K8S cluster. The way UEB is configured in SDC is 
using the K8S hosts IPs, so DCAE service (when deployed), can reach it when 
retrieving the config using the following request (replace 
K8S_HOST
 with one of your host ip):

curl -X GET \
  
http://K8S_HOST:30205/sdc/v1/distributionUebCluster
 \
  -H 'Accept: application/json' \
  -H 'Content-Type: application/json' \
  -H 'X-ECOMP-InstanceID: mso' \
  -H 'authorization: Basic 
dmlkOktwOGJKNFNYc3pNMFdYbGhhazNlSGxjc2UyZ0F3ODR2YW9HR21KdlV5MlU=‘

I guess, if you try this request on the setup where it was failing before, 
you’ll get the list where the first elements look ok, but the second one is 
wrong, See 
https://jira.onap.org/browse/OOM-638
 for more details.
This has now been fix.

That said, it seems this is not it, and there is still something breaking SDC 
UEB registration.

Can you confirm you’re running in a K8S cluster?  I’m looking into this.

Alexis


On Jan 26, 2018, at 1:22 PM, Ramanarayanan, Karthick 
> wrote:

The sdc-backend was always a suspect in my setup (56 core) and I invariably 
used to restart the backend pods to get the backend health checks to succeed:
curl http://127.0.0.1:30205/sdc2/rest/healthCheck

This returns "Service unavailable" when backend doesn't come up. If you restart 
the cassandra/es/kibana pods and then restart the backend, it would come up.

In my single node k8s host (k8s directly on the host as in my earlier runs),
I see health check component DE for backend failing. (distribution engine)

Everything else is up.

curl http://127.0.0.1:30205/sdc2/rest/healthCheck

 {
  "healthCheckComponent": "DE",
  "healthCheckStatus": "DOWN",
  "description": "U-EB cluster is not available"
},

This probably implies that in my setup, the UebServers list fetched in the 
backend catalog code before running the DistributionHealthCheck servers fetched 
from the distributionEngine configuration is not proper. (when running without 
dcae vm or dcae disabled)

This is probably the reason why distribution for service fails with policy 
exception.
Its not able to find the ueb server list perhaps when dcae is disabled.
Alexis would know best.

Regards,
-Karthick

From: FREEMAN, BRIAN D >
Sent: Friday, January 26, 2018 9:52:24 AM
To: Alexis de Talhouët; Ramanarayanan, Karthick
Cc: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM

Alexi,



I cant get OOM install to work today (it was working yesterday) - seems to fail 
on sdc - doesnt pass healthcheck due to sdc-be as best I can tell .



I use cd.sh should i use the 4 step process below instead ?



Brian





-Original Message-

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët

Sent: Friday, January 26, 2018 8:50 AM

To: Ramanarayanan, Karthick >

Cc: onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] [**EXTERNAL**] Service distribution error on latest 
ONAP/OOM



Karthick,



I’ve just re-tested on latest Amsterdam, and distribute does work fine.



I don’t know if you have redeploy the whole ONAP or not, but understand that 
the issue you had with distribution not

Re: [onap-discuss] [integration]Committers promotion for Integration Project: Morgan Richomme

2018-01-26 Thread PLATANIA, MARCO (MARCO)

+1 to Eric and Morgan.

As I understand, Jack will be a contributor, not committer. Is that right?

Marco

From: Yunxia Chen <helen.c...@huawei.com>
Date: Friday, January 26, 2018 at 3:12 AM
To: "wangchen...@chinamobile.com" <wangchen...@chinamobile.com>, "ROSE, DANIEL 
V" <dr6...@att.com>, "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"DEY, SPONDON" <sd4...@att.com>, "yangyi@chinatelecom.cn" 
<yangyi@chinatelecom.cn>, Gary Wu <gary.i...@huawei.com>, Kang Xi 
<kang...@huawei.com>, "Yang Xu (Yang, Fixed Network)" <yang@huawei.com>, 
"lxin...@vmware.com" <lxin...@vmware.com>, "bin.y...@windriver.com" 
<bin.y...@windriver.com>, "ran.pol...@amdocs.com" <ran.pol...@amdocs.com>
Cc: "morgan.richo...@orange.com" <morgan.richo...@orange.com>, Gildas Lanilis 
<gildas.lani...@huawei.com>, onap-discuss <onap-discuss@lists.onap.org>
Subject: Re: [integration]Committers promotion for Integration Project: Morgan 
Richomme

Dear Integration Committers,

I would like to propose to promote: Morgan Richomme as the committer for 
Integration project.

Morgan has been an active contributor for OPNFV testing related project. Before 
Amsterdam release, he was focused on the ONAP integration testing in Orange 
open lab and contributed the results back to ONAP community.

Git Commits: 29
Gerrit changesets: 17
Mailing Lists: 6
Jira: 13
(The above data is from ONAP Bitergia)

For Beijing release, he is actively working on:

1.  ONAP Maturity testing

2.  Leading and working on ONAP testing results related work

3.  Continue his integration testing at Orange open lab

4.  Integration / Benchmark

Before I get the approval from ONAP TSC / infrastructure coordinator, I would 
like to do an internal vote among all current Integration committers, which are 
on the “To” list:

1.  If you agree to promote Morgan as committer of Integration project, 
please reply “+1”

2.  If you have no opinion, please reply “0”

3.  If you disagree to promote Morgan as committer of Integration project 
and just keep him as contributor, please reply “-1”

Please response before 6:00PM PST, 1/29/2018 (next Monday).

Regards,
Helen Chen

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

Re: [onap-discuss] Demo update-vfw policy script when running without closed loop

2018-01-25 Thread PLATANIA, MARCO (MARCO)

Karthick,

Please look for BRMS_DEPENDENCY_VERSION at the end of 
${OOM_HOME}/kubernetes/config/docker/init/src/config/policy/opt/policy/config/pe/brmsgw.conf.

That parameter should be the same as the Policy container version number. For 
Amsterdam, it has to be either 1.1.1 or 1.1.3, depending on the Policy version 
that you are using (Amsterdam v1.1.1 or Amsterdam Maintenance v1.1.3).

Also, 
${OOM_HOME}/kubernetes/config/docker/init/src/config/policy/opt/policy/config/pe/push-policies.sh,
 line 11 should be:

wget -O cl-amsterdam-template.drl 
https://git.onap.org/policy/drools-applications/plain/controlloop/templates/archetype-cl-amsterdam/src/main/resources/archetype-resources/src/main/resources/__closedLoopControlName__.drl?h=amsterdam

instead of wget -O cl-amsterdam-template.drl 
https://git.onap.org/policy/drools-applications/plain/controlloop/templates/archetype-cl-amsterdam/src/main/resources/archetype-resources/src/main/resources/__closedLoopControlName__.drl

(note ?h=amsterdam at the end of the correct call).

You can make these changes in your OOM local repo, as described above, or 
directly in the ONAP configuration folder in your NFS share (or local disk if 
you have a single-host K8S cluster), in 
/dockerdata-nfs/onap/policy/opt/policy/config/pe/push-policies.sh (and the same 
path for brmsgw.conf). The former approach requires to rebuild ONAP, while the 
latter requires to rebuild only Policy.

Marco



From:  on behalf of "Ramanarayanan, 
Karthick" 
Date: Thursday, January 25, 2018 at 1:32 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Demo update-vfw policy script when running without 
closed loop


Hi,

 In my kubernetes setup minus dcae (just vFW without closed loop),

 I am trying to mount the appc packetgen interface but I am unable to see the 
mounts in appc mounts list.

 The policy that was pushed used the kubernetes update-vfw-op-policy.sh script 
which seems to be applicable for closed loop.



 Though the policy script runs and applies the policy and restarts the policy 
pods, the get on controlloop.Params fails at the end.



 curl -v --silent --user @1b3rt:31nst31n -X GET 
http://${K8S_HOST}:${POLICY_DROOLS_PORT}/policy/pdp/engine/controllers/amsterdam/drools/facts/closedloop-amsterdam/org.onap.policy.controlloop.Params
  | python -m json.tool


{
"error": "amsterdam:closedloop-amsterdam:org.onap.policy.controlloop.Params 
not found"
}




Moving ahead, I configure the packet gen interface with an appc put to network 
topology for the packetgen vnf/ip.

Put succeeds but appc mounts doesn't show up.

Wondering if the policy script needs to be changed when executing without 
closed loop?

What am I missing?



Thanks,

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

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

2018-01-12 Thread PLATANIA, MARCO (MARCO)

Yes, all of them should be “amsterdam”, only mr_branch should be master.

Marco

From: "Matt, Brian" <brian.m...@windstream.com>
Date: Friday, January 12, 2018 at 2:50 PM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Marco,

Thanks, looking through my heat environment file, it appears most match these 
versions I’ll update the ones that appear to have newer versions.

I’m using the template from 
https://git.onap.org/demo/plain/heat/ONAP/onap_openstack.env<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_demo_plain_heat_ONAP_onap-5Fopenstack.env=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=WwC7M8e0GTumlTd-m66bMTSV1Czkiq5FbtxOvt0sjQw=T-LdM3tff1wAkUtddUYX03EItMnuIdVEDp1Z8K_GeMw=>
 to deploy; these are linked from Amsterdam 1.0.0 installation and download. 
I’d imagine we’d want these updated if they are wrong?

For the gerrit branches, I assume you are referencing:

  aai_branch: master
  appc_branch: master
  so_branch: master
  mr_branch: master
  policy_branch: master
  portal_branch: master
  robot_branch: master
  sdc_branch: master
  sdnc_branch: master
  vid_branch: master
  clamp_branch: master
  vnfsdk_branch: master

All of these should be Amsterdam except mr_branch? I can give this a shot and 
see if it helps.

Brian

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Friday, January 12, 2018 2:29 PM
To: Matt, Brian <brian.m...@windstream.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam 
with vFWCL

Brian,

It seems to me that you are using old docker images and/or that the Gerrit 
branch is not in sync with the dockers. Please modify the heat environment file 
with the latest docker image version numbers that you can find here: 
https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=version-manifest/src/main/resources/docker-manifest.csv;h=37cc982c096617932bb8558ab5f7d3230b809369;hb=refs/heads/amsterdam<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dintegration.git-3Ba-3Dblob-3Bf-3Dversion-2Dmanifest_src_main_resources_docker-2Dmanifest.csv-3Bh-3D37cc982c096617932bb8558ab5f7d3230b809369-3Bhb-3Drefs_heads_amsterdam=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=WwC7M8e0GTumlTd-m66bMTSV1Czkiq5FbtxOvt0sjQw=J8NzU-YatKdwWqmVZChQqaHNjBSyxMYy-imka0IUrJ4=>

Robot should use 1.1-STAGING-latest instead.

Also, all the gerrit branches should be “amsterdam” except for message router, 
which uses master.

Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Matt, Brian" 
<brian.m...@windstream.com<mailto:brian.m...@windstream.com>>
Date: Friday, January 12, 2018 at 1:29 PM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with 
vFWCL

We’ve been working through the vFW demo with Amsterdam and have the VM 
deployed. However, the APPC mounting and Drools policy deployment are not 
working completely. We’ve got through the heatbridge setup and are having 
issues with the policy steps and the APPC steps.

For APPC we found that the image being delivered by the heat templates for 
1.0.0 appear to have a /opt/sdnc directory where the deployment is expecting an 
/opt/appc directory. We renamed these to get the container running and it 
appears to work fine that way, but it may be contributing to the issue?

When attempting to do the APPC mount we are getting the following error.

protocol
malformed-message
Error parsing input: Unknown child(ren) node(s) 
detected, identified by: (urn:opendaylight:netconf-node-topology)host, in: list 
node

Below are the details of our call.

URL: 
http://{{appc_ip}}:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/8d1df789-bf7f-4c6a-9515-8f4b7583febd<https://urldefense.proofpoint.com/v2/url?u=http-3A__-257b-257bappc-5Fip-257d-257d-3A8282_restconf_config_network-2Dtopology-3Anetwork-2Dtopology_topology_topology-2Dnetconf_node_8d1df789-2Dbf7f-2D4c6a-2D9515-2D8f4b7583febd=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=oVE0_bi4x1uhhdY5Jk5jf39U9qtqDNsqNp4xnW0eJzA=7NmftQD4gMZrSdkN4kaQb7mW8dv-eJM75awVzV3xqYo=>
Headers:
Authorization: Basic 
YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==
Content-Type: text/xml
Accept: application/xml
Content:

   8d1df789-bf7f-4c6a-9515-8f4b7583febd
   10.0.80.2
   2831
   admin

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

2018-01-12 Thread PLATANIA, MARCO (MARCO)

Brian,

It seems to me that you are using old docker images and/or that the Gerrit 
branch is not in sync with the dockers. Please modify the heat environment file 
with the latest docker image version numbers that you can find here: 
https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=version-manifest/src/main/resources/docker-manifest.csv;h=37cc982c096617932bb8558ab5f7d3230b809369;hb=refs/heads/amsterdam

Robot should use 1.1-STAGING-latest instead.

Also, all the gerrit branches should be “amsterdam” except for message router, 
which uses master.

Marco

From:  on behalf of "Matt, Brian" 

Date: Friday, January 12, 2018 at 1:29 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [APPC][POLICY] Drools and APPC issues in Amsterdam with 
vFWCL

We’ve been working through the vFW demo with Amsterdam and have the VM 
deployed. However, the APPC mounting and Drools policy deployment are not 
working completely. We’ve got through the heatbridge setup and are having 
issues with the policy steps and the APPC steps.

For APPC we found that the image being delivered by the heat templates for 
1.0.0 appear to have a /opt/sdnc directory where the deployment is expecting an 
/opt/appc directory. We renamed these to get the container running and it 
appears to work fine that way, but it may be contributing to the issue?

When attempting to do the APPC mount we are getting the following error.



protocol
malformed-message
Error parsing input: Unknown child(ren) node(s) 
detected, identified by: (urn:opendaylight:netconf-node-topology)host, in: list 
node



Below are the details of our call.

URL: 
http://{{appc_ip}}:8282/restconf/config/network-topology:network-topology/topology/topology-netconf/node/8d1df789-bf7f-4c6a-9515-8f4b7583febd
Headers:
Authorization: Basic 
YWRtaW46S3A4Yko0U1hzek0wV1hsaGFrM2VIbGNzZTJnQXc4NHZhb0dHbUp2VXkyVQ==
Content-Type: text/xml
Accept: application/xml
Content:


   8d1df789-bf7f-4c6a-9515-8f4b7583febd
   10.0.80.2
   2831
   admin
   admin
   false



For Drools we are able to delete the policy from PDP, Update the policy in PDP, 
and push the policy in PDP. When we get past that point, after restarting 
policy on the drools container, we are getting an error that the Amsterdam 
controller does not exist.

{
"error": "amsterdam not found"
}

This is coming back from 
http://policy.api.simpledemo.onap.org:9696/policy/pdp/engine/controllers/amsterdam/drools.
 If we back it up a bit to 
http://policy.api.simpledemo.onap.org:9696/policy/pdp/engine/controllers
 we get a response of an empty list, we assume this means there are no 
controllers created?

I looked around the wiki and searched through the discuss conversations but 
couldn’t find references to these specific errors.


Brian
This email message and any attachments are for the sole use of the intended 
recipient(s). Any unauthorized review, use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please contact the sender by 
reply email and destroy all copies of the original message and any attachments.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ONAP on Vanilla OpenStack

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

Harry,

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

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

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

Hope this helps!

Marco


From:  on behalf of huangxiangyu 

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

Hi

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

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

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

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

2018-01-08 Thread PLATANIA, MARCO (MARCO)

Karthick,

Make sure you set “delete on rollback” to false in vid. The exceeded number of 
polls error is benign but it still deletes the VF module if the delete option 
is set to true.

Marco

On Mon, Jan 8, 2018 at 9:36 PM -0500, "Ramanarayanan, Karthick" 
> wrote:

Hi Marco,

Thanks for the response.

Comments inline.

I have retried now with the changes to demo versions but doesn't change the 
equation.

Same status as before.

More inline ...

>What error are you getting precisely?

I get maximum poll attempts exceeded.

I thought that's a benign error for the GUI waiting to refresh on request

 status.

But after that, refreshing the service instance list, moves the VF to pending 
delete.

(also unable to delete once in this state as mentioned earlier. No hint in 
sdnc/mso/vid portal logs whatsoever)

Here's a snapshot for your perusal:

https://www.dropbox.com/s/z6b69aq40k6hw61/Screenshot%202018-01-08%2018.25.06.png?dl=

> How did you set onap-parameters.yaml in OOM? The OpenStack parameters are 
> used by SO to instantiate the VNFs.

Yes. I am aware about that. As without that, model init through demo-k8s robot 
would have failed anyway.

Here's the onap-parameters.yaml for our k8s environment under 
oom/kubernetes/config:

#cat onap-parameters.yaml
--

OPENSTACK_UBUNTU_14_IMAGE: "Ubuntu_14.04.5_LTS"
OPENSTACK_PUBLIC_NET_ID: "aff52391-359f-4264-9768-1948c83021bc"
OPENSTACK_OAM_NETWORK_ID: "abd45e55-bbac-4ec4-84cf-38479b1cf075"
OPENSTACK_OAM_SUBNET_ID: "28222064-0f44-4758-94c5-72eaaf726837"
OPENSTACK_OAM_NETWORK_CIDR: "10.0.0.0/26"
OPENSTACK_USERNAME: "onap"
OPENSTACK_API_KEY: "secret"
OPENSTACK_TENANT_NAME: "onap"
OPENSTACK_TENANT_ID: "45947f2541a34498b340eb93b56b5c24"
OPENSTACK_REGION: "RegionOne"
OPENSTACK_KEYSTONE_URL: 
"http://192.168.42.240/identity;
OPENSTACK_FLAVOUR_MEDIUM: "m1.small"
OPENSTACK_SERVICE_TENANT_NAME: "service"
DMAAP_TOPIC: "AUTO"
DEMO_ARTIFACTS_VERSION: "1.1.0-SNAPSHOT"

Maybe the DEMO artifacts version above needs to be 1.1.1 as I haven't changed 
that yet.

Can try with that if you think that's the issue.

>Also, note that for Amsterdam release, the following parameters should be used:

Done. Posted the vnf preload topology operation with demo artifacts 1.1.1 and 
install 1.1.1.

Confirmed with a GET as well to see the new posted data for the vnfs.

Same error as mentioned above.

 Regards,

-Karthick

From:  on behalf of "Ramanarayanan, 
Karthick" 
Date: Monday, January 8, 2018 at 6:32 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Failure to create the demo vfirewall VNF

{

"vnf-parameter-name": "demo_artifacts_version",

"vnf-parameter-value": "1.1.0"

},

{

"vnf-parameter-name": "install_script_version",

"vnf-parameter-value": "1.1.0-SNAPSHOT"
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

2018-01-08 Thread PLATANIA, MARCO (MARCO)

Karthick,

What error are you getting precisely? How did you set onap-parameters.yaml in 
OOM? The OpenStack parameters are used by SO to instantiate the VNFs. Also, 
note that for Amsterdam release, the following parameters should be used:

{
"vnf-parameter-name": "demo_artifacts_version",
"vnf-parameter-value": "1.1.1"
},
{
"vnf-parameter-name": "install_script_version",
"vnf-parameter-value": "1.1.1"
}

When I shoot the video, the release wasn’t cut yet, so I had to use 1.1.0 and 
1.1.0-SNAPSHOT respectively.

Marco

From:  on behalf of "Ramanarayanan, 
Karthick" 
Date: Monday, January 8, 2018 at 6:32 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Failure to create the demo vfirewall VNF

{
"vnf-parameter-name": "demo_artifacts_version",
"vnf-parameter-value": "1.1.0"
},
{
"vnf-parameter-name": "install_script_version",
"vnf-parameter-value": "1.1.0-SNAPSHOT"
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

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

2018-01-08 Thread PLATANIA, MARCO (MARCO)

Gary,

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

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

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

Thanks,
Marco

From: Gary Wu <gary.i...@huawei.com>
Date: Monday, January 8, 2018 at 7:17 PM
To: Yunxia Chen <helen.c...@huawei.com>, onap-discuss 
<onap-discuss@lists.onap.org>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>, 'Chengli Wang' <wangchen...@chinamobile.com>, Kang 
Xi <kang...@huawei.com>, "Yang Xu (Yang, Fixed Network)" <yang@huawei.com>, 
"FLOOD, JERRY" <jf9...@att.com>, Eric Debeau <eric.deb...@orange.com>
Subject: RE: [integration] ONAP Amsterdam Maintenance release testing

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

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

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

Thanks,
Gary

From: Gary Wu
Sent: Monday, January 08, 2018 12:30 PM
To: Yunxia Chen <helen.c...@huawei.com>; onap-discuss 
<onap-discuss@lists.onap.org>; PLATANIA, MARCO (MARCO) 
<plata...@research.att.com>; 'Chengli Wang' <wangchen...@chinamobile.com>; Kang 
Xi <kang...@huawei.com>; Yang Xu (Yang, Fixed Network) <yang@huawei.com>; 
Jerry Flood <jf9...@att.com>; Eric Debeau <eric.deb...@orange.com>
Subject: RE: [integration] ONAP Amsterdam Maintenance release testing

It’s taking a while since we’re doing several simultaneous deployments.  I’ll 
send out another update when the environments are up.

The Jenkins URL is: 
http://12.234.32.117/jenkins/<https://urldefense.proofpoint.com/v2/url?u=http-3A__12.234.32.117_jenkins_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=icRkVA3EVTeZx-b9_7_68tqory4UWCQJi5I3XDMU4LM=EiVctmRFdVOHojySDyggzV4iSt4hLLoEEDsufxO14oE=>.

Thanks,
Gary

From: Yunxia Chen
Sent: Monday, January 08, 2018 11:30 AM
To: Gary Wu <gary.i...@huawei.com<mailto:gary.i...@huawei.com>>; onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; PLATANIA, 
MARCO (MARCO) <plata...@research.att.com<mailto:plata...@research.att.com>>; 
'Chengli Wang' 
<wangchen...@chinamobile.com<mailto:wangchen...@chinamobile.com>>; Kang Xi 
<kang...@huawei.com<mailto:kang...@huawei.com>>; Yang Xu (Yang, Fixed Network) 
<yang@huawei.com<mailto:yang@huawei.com>>; Jerry Flood 
<jf9...@att.com<mailto:jf9...@att.com>>; Eric Debeau 
<eric.deb...@orange.com<mailto:eric.deb...@orange.com>>
Subject: Re: [integration] ONAP Amsterdam Maintenance release testing

Thank you Gary. Please let us know once it passed all health check.

At the same time, could you please include vFWCL test case

Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release

2018-01-04 Thread PLATANIA, MARCO (MARCO)

eploy in about 10 minutes (excluding DCAE).

First impressions:

  *   The system is highly dependent in using exact versions of everything: 
docker, kubernetes, helm, rancher, etc.  If anything is slightly off, things 
would break, and it would not be obvious exactly what was wrong.  As a result, 
it makes the system feel fragile.
  *   The SDC intermittent issue above makes the OOM deployments feel not fully 
stable/repeatable yet.
  *   The OOM “how-to” documentation has almost too much information, covering 
multiple options/paths that sometimes overlap (e.g. where to install Rancher 
server vs agent, whether to use the cd.sh or manually perform individual 
steps).  This made it hard for a newcomer to discern which steps need to be run 
next given which other choices were made earlier, and it was also hard to 
figure out if any mistakes were made performing some prior steps.

I was not able to find any information on how to deploy DCAE via OOM; the most 
I got so far was that the DCAE controller container was able to bring up about 
half of the expected DCAE VMs, but not enough to be able to pass the DCAE 
health check.

Thanks,
Gary


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Wednesday, January 03, 2018 9:15 AM
To: Alexis de Talhouët 
<adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>; GILBERT, MAZIN E 
(MAZIN E) <ma...@research.att.com<mailto:ma...@research.att.com>>
Cc: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release

I’ve been playing around with the OOM solution for a while and I was able to 
instantiate the vFW, vLB/vDNS, plus another dummy generic VNF that I created. I 
installed a minimal version of DCAE (only the collector and one CDAP container 
with the Threshold-crossing microservices) to run closed loop, waiting for the 
whole DCAE platform to be ready. I wasn’t able to run closed loop yet, perhaps 
due to out-of-sync configuration in my environment. I’m trying to fix this and 
see how far I can go with closed loop.

Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Alexis de Talhouët 
<adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>>
Date: Wednesday, January 3, 2018 at 11:36 AM
To: "GILBERT, MAZIN E (MAZIN E)" 
<ma...@research.att.com<mailto:ma...@research.att.com>>
Cc: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release

Mazin,

So far, that I’m aware of, a few ppl from various company have tried OOM 
Amsterdam, and have successfully deployed vFWCL.
If you want names and email, I guess I can find them for you.

We’re currently testing vFWCL close loop with DCAE being deployed by OOM; I’d 
say it’s 80% done.

Thanks,
Alexis

On Jan 3, 2018, at 11:21 AM, GILBERT, MAZIN E (MAZIN E) 
<ma...@research.att.com<mailto:ma...@research.att.com>> wrote:

Thanks Roger.

Have there been other groups who have managed to bring up Amsterdam with OOM 
(with and without DCAE)?
Can you point me to any so I can understand their experience.

mazin


On Jan 3, 2018, at 11:15 AM, Roger Maitland 
<roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>> wrote:

Hi Helen,

David is on vacation so I’ll answer - OOM is ready.

The OOM team has been working with the Integration team and the entire ONAP 
community to create the 
amsterdam<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Doom.git-3Ba-3Dshortlog-3Bh-3Drefs_heads_amsterdam=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=_dlaJi5cUYGfdQpkrTvOLmwKf9nHldPQl5dmZYtz2iQ=uYM-V22L0V1EhonUacGlX4_i-MF4XdWNLtYWzReGYA4=>
 release of OOM which is now available.  There is a continuous delivery system 
that deploys the master branch of all of the ONAP components with OOM – 
here<https://urldefense.proofpoint.com/v2/url?u=http-3A__kibana.onap.info-3A5601_app_kibana-23_dashboard_AWAtvpS63NTXK5mX2kuS-3F-5Fg-3D-28refreshInterval-3A-28display-3AOff-2Cpause-3A-21f-2Cvalue-3A0-29-2Ctime-3A-28from-3Anow-2D24h-2Cmode-3Aquick-2Cto-3Anow-29-29-26-5Fa-3D-28description-3A-2527-2527-2Cfilters-3A-21-28-29-2Coptions-3A-28darkTheme-3A-21f-29-2Cpanels-3A-21-28-28col-3A1-2Cid-3AAWAts77k3NTXK5mX2kuM-2CpanelIndex-3A1-2Crow-3A1-2Csize-5Fx-3A8-2Csize-5Fy-3A=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=TEGneiYu3X69Tbakkf-0jbhukaSEN5O-Dj-rwTm4eXY=HXzlpENhYHSnNMtU61IUybmlPUBxj2VxcRYHbRcCRJw=>
 is the dashboard.  As this system is effectively continuously evaluating ONAP 
health this should be very useful for the Integration team to quickly identify 
component submissions that result in a degra

Re: [onap-discuss] vFW VES event fail to send

2018-01-04 Thread PLATANIA, MARCO (MARCO)

127.0.0.1 is definitely not correct. In the Heat-based deployment, a VM called 
dcaedoks00 is created. That VM contains the VES collector, so the IP address of 
that VM is used. In K8S you need to look for 
nexus.onap.org<http://nexus.onap.org/>:10001/onap/org.onap.dcaegen2.collectors.ves.vescollector
 docker container. I think you should use it’s IP address.

Marco

From: Kranthi Guttikonda <kranthi.guttiko...@b-yond.com>
Date: Thursday, January 4, 2018 at 10:19 AM
To: "FREEMAN, BRIAN D" <bf1...@att.com>, "de Talhouet, Alexis" 
<alexis.de_talho...@bell.ca>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>, onap-discuss <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] vFW VES event fail to send

I remember Marco’s video shows to use dcaedoks00 VM public ip address.



Thanks,

Kranthi



On 1/4/18, 10:14 AM, 
"onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
 on behalf of FREEMAN, BRIAN D" 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>
 on behalf of bf1...@att.com<mailto:bf1...@att.com>> wrote:



It should be the IP of the DCAE VES collector I thought ? I dont think 
127.0.0.1 is correct.



Brian





-Original Message-

From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of de Talhouet, Alexis

Sent: Thursday, January 04, 2018 9:46 AM

To: PLATANIA, MARCO 
<plata...@research.att.com<mailto:plata...@research.att.com>>; onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>

Subject: [onap-discuss] vFW VES event fail to send



Hi Marco, experts,







I was wondering if you could help me understand something with regards to 
VES collector on the vfw sinc vnf.







I see in the syslog it’s failing to send the events, see logs bellow:







Jan  4 14:42:58 vfw-sinc-vnf EVEL[17281]: | | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | ERROR: Failed to transfer an event to Vendor 
Event Listener! Error code=7 (Failed to connect to 127.0.0.1 port 8080: 
Connection refused)



Jan  4 14:42:58 vfw-sinc-vnf EVEL[17281]: | | | | | | | | | | | | | | | | | 
| | | | | | | | | | | | | | | ERROR: Dropped event: {"event": 
{"commonEventHeader": {"domain": "measurementsForVfScaling", "eventId": 
"TrafficStats_1.2.3.4", "eventName": "vFirewallBroadcastPackets", 
"lastEpochMicrosec": 1515076978028524, "priority": "Normal", 
"reportingEntityName": "fwll", "sequence": 124625, "sourceName": 
"vFW_SINC_VNF", "startEpochMicrosec": 1515076967821239, "version": 1.2, 
"eventType": "HTTP request rate", "reportingEntityId": "No UUID available", 
"sourceId": "44629bac-c241-4087-afb5-febef78bdb72", "nfcNamingCode": "vVNF", 
"nfNamingCode": "vVNF"}, "measurementsForVfScalingFields": 
{"measurementInterval": 10, "cpuUsageArray": [{"cpuIdentifier": "cpu1", 
"cpuIdle": 66.70, "cpuUsageSystem": 33.30, "cpuUsageUser": 0.00, 
"percentUsage": 0.00}], "requestRate": 5099, "vNicUsageArray": 
[{"receivedOctetsDelta": 43860.00, "receivedTotalPacketsDelta": 
1020.00, "transmittedOctetsDelta": 0.00, 
"transmittedTotalPacketsDelta": 0.00, "valuesAreSuspect": "true", 
"vNicIdentifier": "eth0"}], "measurementsForVfScalingVersion": 2.1}}}







It cannot connect to 127.0.0.1 port 8080, which is configured in the sdnc 
preload config.







My question is, should this always be 127.0.0.1? Or should it be the IP of 
the VM in which the VES collector is running? (I know it can sound like an 
obvious question, but in Marco’s video, I haven’t seen him changed this in the 
sdnc preload step).







Thanks,



Alexis







___

onap-discuss mailing list

onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>


https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=nXDFucLC_nuN5o0oXltp9kR1k9K0qbrJbaSqynmBzaY=tcKrKhIh-bFt3RzWtpGkZdDVF1BiTwVDnJr_FrdKLlY=

___

onap-discuss mailing list

onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>


https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=O70NXVqpfNjNBeZACn6p4L9zZwCxVZpy0zDOIVjUUrw=EZJeJctIdgC6ShGb-Ne8LBQn2E_TwRI3g6W7yr46P8Y=






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

Re: [onap-discuss] Attempting the FW demo

2018-01-04 Thread PLATANIA, MARCO (MARCO)

Hi David,

Yes, this video is still valid and it targets developers that want to recreate 
all the steps to run closed loop operations. I agree there are a lot of manual 
steps to execute, but the purpose of the video is to educate people about all 
the details of ONAP operations. In the meantime, we are working on automating 
most of those steps, so people can run operations faster.

Thanks,
Marco

From:  on behalf of "Bainbridge, David" 

Date: Wednesday, January 3, 2018 at 5:28 PM
To: onap-discuss 
Subject: [onap-discuss] Attempting the FW demo

Is the following video still valid?

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

For a system that is meant to automate VNF deployment there seems to be an 
inordinate number of manual steps and cut and pasting.

Am I missing something?

Avèk respè,
/david
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release

2018-01-03 Thread PLATANIA, MARCO (MARCO)

I’ve been playing around with the OOM solution for a while and I was able to 
instantiate the vFW, vLB/vDNS, plus another dummy generic VNF that I created. I 
installed a minimal version of DCAE (only the collector and one CDAP container 
with the Threshold-crossing microservices) to run closed loop, waiting for the 
whole DCAE platform to be ready. I wasn’t able to run closed loop yet, perhaps 
due to out-of-sync configuration in my environment. I’m trying to fix this and 
see how far I can go with closed loop.

Marco

From:  on behalf of Alexis de Talhouët 

Date: Wednesday, January 3, 2018 at 11:36 AM
To: "GILBERT, MAZIN E (MAZIN E)" 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [integration][oom] OOM readiness for Beijing release

Mazin,

So far, that I’m aware of, a few ppl from various company have tried OOM 
Amsterdam, and have successfully deployed vFWCL.
If you want names and email, I guess I can find them for you.

We’re currently testing vFWCL close loop with DCAE being deployed by OOM; I’d 
say it’s 80% done.

Thanks,
Alexis

On Jan 3, 2018, at 11:21 AM, GILBERT, MAZIN E (MAZIN E) 
> wrote:

Thanks Roger.

Have there been other groups who have managed to bring up Amsterdam with OOM 
(with and without DCAE)?
Can you point me to any so I can understand their experience.

mazin

On Jan 3, 2018, at 11:15 AM, Roger Maitland 
> wrote:

Hi Helen,

David is on vacation so I’ll answer - OOM is ready.

The OOM team has been working with the Integration team and the entire ONAP 
community to create the 
amsterdam
 release of OOM which is now available.  There is a continuous delivery system 
that deploys the master branch of all of the ONAP components with OOM – 
here
 is the dashboard.  As this system is effectively continuously evaluating ONAP 
health this should be very useful for the Integration team to quickly identify 
component submissions that result in a degradation.

The initial version of DCAE support is under final testing.  This version 
brings up the DCAE controller which then brings up the rest of the DCAE VMs.  
There is a discussion scheduled for tomorrow between the OOM and DCAE team on a 
more fully containerized solution.  The OOM team is also working on deploying 
OpenStack DNS Designate to simply the deployment of OpenStack infrastructure 
required for DCAE.  We’ll let the community know when this is ready.

Cheers,
Roger

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Yunxia Chen
Sent: Tuesday, January 2, 2018 5:25 PM
To: onap-discuss 
>; Sauvageau, 
David >
Subject: [onap-discuss] [integration][oom] OOM readiness for Beijing release

Hi, David,

Happy new year and it was very nice to talk with you at Santa Clara. Is OOM 
ready for Integration team to take over to test the Beijing release, maybe 
start with Amsterdam project first? From last meeting, it seems have a little 
bit issue on DCAE, has it resolved yet?

Regards,
Helen Chen
This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=IKSC5mg8GeOiSar1dax3GQ=_dlaJi5cUYGfdQpkrTvOLmwKf9nHldPQl5dmZYtz2iQ=j7WSvxdz-fKgmH76NuG-x2cW3E_oZL4nU8OuXiW1ylM=

___
onap-discuss mailing list
onap-discuss@lists.onap.org

Re: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack

2017-12-14 Thread PLATANIA, MARCO (MARCO)

Hello Pavithra,

Make sure you are populating oom/kubernetes/config/onap-parameters.yaml 
correctly. Those parameters should reflect your OpenStack environment and are 
used by SO during VNF instantiation.

“Maximun number of poll attempts exceeded” indicates a timeout expiration. SO 
is trying to contact OpenStack but something fails. Also, deleting VF module 
manually is not currently supported.

Perhaps SO people can add more on how to get past the timeout expiration.

Thanks,
Marco

From:  on behalf of Pavithra R13 

Date: Thursday, December 14, 2017 at 7:27 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Issue in vFW instantiation E2E - OOM with OpenStack


Hi All,

I am using OOM 1.1.0 release and following the steps/videos posted in 
wiki(“https://wiki.onap.org/display/DW/vFW+instantiation+E2E+-+OOM+with+OpenStack”).
 At step 10g  (create VF-Module for vFW_SINC) I am facing the error “Maximun 
number of poll attempts exceeded.”

And VF module on the VID page shows orchestration status as “pending delete”. 
Also the stack doesn’t get created in my OpenStack environment. I could not 
manually delete the VF module also. It shows “System failure” when trying to 
delete . How do I get past this? Any suggestions on what could be 
failing/missing. I tried two times and it’s failing with same error “Maximun 
number of poll attempts exceeded.”

Kindly suggest solutions to solve the issue and successfully create VF module.

Regards,

Pavithra R






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

Re: [onap-discuss] [Amsterdam][OOM] vFW close-loop testing

2017-12-07 Thread PLATANIA, MARCO (MARCO)

Yes, make sure that Policy configuration is taken from the Amsterdam branch, 
not master. Not sure how this is done in OOM, but I get this failure when I use 
policy containers released for Amsterdam and configuration data taken from 
Gerrit master branch (as opposed to Amsterdam branch).

Marco

From: Alexis de Talhouët <adetalhoue...@gmail.com>
Date: Thursday, December 7, 2017 at 2:27 PM
To: "HERNANDEZ-HERRERO, JORGE" <jh1...@att.com>
Cc: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com>, "PLATANIA, MARCO 
(MARCO)" <plata...@research.att.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [Amsterdam][OOM] vFW close-loop testing

Now that everything is up-to-date in my setup, I’m facing the following.
Does this ring a bell to someone?

Thanks,
Alexis

PDP-D amsterdam maven coordinates ..

*   Trying 10.195.197.141...
* TCP_NODELAY set
* Connected to 10.195.197.141 (10.195.197.141) port 30221 (#0)
* Server auth using Basic with user '@1b3rt'
> GET /policy/pdp/engine/controllers/amsterdam/drools HTTP/1.1
> Host: 10.195.197.141:30221
> Authorization: Basic QDFiM3J0OjMxbnN0MzFu
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Thu, 07 Dec 2017 19:08:51 GMT
< Content-Type: application/json
< Content-Length: 31
< Server: Jetty(9.3.14.v20161028)
<
{ [31 bytes data]
* Connection #0 to host 10.195.197.141 left intact
{
"error": "amsterdam not found"
}

PDP-D control loop updated ..

*   Trying 10.195.197.141...
* TCP_NODELAY set
* Connected to 10.195.197.141 (10.195.197.141) port 30221 (#0)
* Server auth using Basic with user '@1b3rt'
> GET 
> /policy/pdp/engine/controllers/amsterdam/drools/facts/closedloop-amsterdam/org.onap.policy.controlloop.Params
>  HTTP/1.1
> Host: 10.195.197.141:30221
> Authorization: Basic QDFiM3J0OjMxbnN0MzFu
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 404 Not Found
< Date: Thu, 07 Dec 2017 19:08:51 GMT
< Content-Type: application/json
< Content-Length: 87
< Server: Jetty(9.3.14.v20161028)
<
{ [87 bytes data]
* Connection #0 to host 10.195.197.141 left intact
{
"error": "amsterdam:closedloop-amsterdam:org.onap.policy.controlloop.Params 
not found"
}

On Dec 7, 2017, at 1:38 PM, Alexis de Talhouët 
<adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>> wrote:

Jorge,

keep in mind I’m working on the OOM setup, not the HEAT setup. In the OOM 
world, some of the config is being forked to be able to properly adjust to the 
kubernetes context. This is why there is a version mis-match. Actually it’s a 
config mis-match. Due to the fact I took the config from the policy/docker 
repo, amsterdam branch. As said in my previous message, I believe this branch 
should be updated to reflect expected config for amsterdam.

Thanks again for the assistance.
Alexis

On Dec 7, 2017, at 1:35 PM, Alexis de Talhouët 
<adetalhoue...@gmail.com<mailto:adetalhoue...@gmail.com>> wrote:

I see, I followed the docker checked-in the policy/docker repository, for the 
amsterdam branch: 
https://gerrit.onap.org/r/gitweb?p=policy/docker.git;a=blob;f=config/pe/brmsgw.conf;h=70d8bbb69d3398ab10ee1da78b3c5ed1a52c2bb0;hb=refs/heads/amsterdam<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dpolicy_docker.git-3Ba-3Dblob-3Bf-3Dconfig_pe_brmsgw.conf-3Bh-3D70d8bbb69d3398ab10ee1da78b3c5ed1a52c2bb0-3Bhb-3Drefs_heads_amsterdam=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=7BLQK8I0TiROpyCKxApn_BFi83SQ6zwst3_ClaeDfIY=7caTIw1iPZzr_vwXBms2GZ6NBxcsT_2Spx8H4wDa3fs=>

So I guess it should be updated to reflect the proper config.

Thanks for the valuable help Jorge. I will update my config as per as the 
config coming from my HEAT deployment.

Alexis
On Dec 7, 2017, at 1:12 PM, HERNANDEZ-HERRERO, JORGE 
<jh1...@att.com<mailto:jh1...@att.com>> wrote:

There is an issue on the brmsgw generating rules jar files while fetching 
dependencies:

[ERROR] Failed to execute goal on project policy-amsterdam-rules: Could not 
resolve dependencies for project 
org.onap.policy-engine.drools.amsterdam:policy-amsterdam-rules:jar:0.1.0: 
Failure to find com.att.research.xacml:xacml-pdp:jar:1.1.1 in 
https://nexus.onap.org/content/repositories/releases/<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_content_repositories_releases_=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=AOclne09odx6cmeimzFUhQ=0Ecw5ceyIx6TGXxpswy_BZP3oGe9Y5glraVxH-eVx68=8-WWVNjmujKCNMrM6skuvlaUQz8qU6K0SJ6d2qsDrlE=>
 was cached in the local repository, resolution will

xacml-pdp jar should be pointing to 1.0.0.   This dependency version comes from 
this file.

docker exec -t -u policy brmsgw bash -c "cat 
/opt/app/policy/servers/brmsgw/dependency.json"

See entry for xacml-p

Re: [onap-discuss] [OpenLab] OOM tenant VMs have been wiped

2017-12-07 Thread PLATANIA, MARCO (MARCO)

Alexis,

Stephen has sent an email last week about lab upgrade. I don’t know if the 
things are connected though. See the original email below.

Marco


Hello,

On Sunday, Dec 3rd ~5 PM PST, the ONAP Developed Pod will receive an additional 
1TB of RAM.   An upgrade such as this should happen without service 
interruption.  However, since the POD’s memory usage is greater than 90% of the 
current capacity, there is not enough RAM to fully migrate all VMs off any 
given server.   Thus, we are requesting that older stacks and VMs that are not 
currently in use are shut down to facilitate a live upgrade (by Sunday 
afternoon PST).

Br,
- Stephen


From:  on behalf of Alexis de Talhouët 

Date: Thursday, December 7, 2017 at 10:40 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [OpenLab] OOM tenant VMs have been wiped

Hi,

All the VMs under the OOM tenant in the OpenLab are gone.
Have they been removed intentionally? Have I missed a mail noticed?

Thanks,
Alexis
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=b-RozLqo_1pErQAEo3KNU3-5yc2dLgmc7zynb8KpvPE=jEz_saSsjIlI0bgwLQAIDgBWemvoMyhLWsGm2-eppcc=

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

Re: [onap-discuss] Multiservices, Robot VMs come up without config directory and install script. Problem with AAI1 init

2017-12-01 Thread PLATANIA, MARCO (MARCO)

Yes, robot still uses 1.1-STAGING-latest or something similar (the one you have 
in the Heat template is correct).

Marco

From: "Arun Arora (c)" <aroraa...@vmware.com>
Date: Friday, December 1, 2017 at 11:15 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] Multiservices, Robot VMs come up without config 
directory and install script. Problem with AAI1 init

Hi Marco,

I re-deployed the stack with Amsterdam branch. Also the docker versions 
mentioned for all VMs in the env file seem latest except robot VM. I compared 
and didn’t see version difference apart from the robot VM of which there was no 
docker entry in the docker-manifest.csv file. Should it be fine?
I will update as things move ahead.

Thanks,
Arun

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: 01 December 2017 19:56
To: Arun Arora (c) <aroraa...@vmware.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Multiservices, Robot VMs come up without config 
directory and install script. Problem with AAI1 init

Hi Arun,

No, they aren’t known issues. However, I suggest you to use the templates here: 
https://nexus.onap.org/content/sites/raw/org.onap.demo/heat/ONAP/1.1.1/<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_content_sites_raw_org.onap.demo_heat_ONAP_1.1.1_=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ=jb5ycBf4M5z4CaqUuBmKXuHXR24In-b-euUEvW9sg9U=fiSWL1Na5NSn2X0BVaqbm1-ycbIh_0mznWfumAjiyLU=>
 or in Gerrit (demo repo – Amsterdam branch). The template you are using has 
docker images released for Amsterdam but use the master branch that is for 
Beijing. That worked soon after the release, but some teams have already made 
new contributions to master that may not be necessarily in sync with the docker 
released for Amsterdam.

Also, please get the latest docker version numbers from the Manifest file in 
the Integration repo: 
https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=version-manifest/src/main/resources/docker-manifest.csv;h=35e992adc0678ccd98328d33c9a5ffc88dbb4dfa;hb=refs/heads/amsterdam<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Dintegration.git-3Ba-3Dblob-3Bf-3Dversion-2Dmanifest_src_main_resources_docker-2Dmanifest.csv-3Bh-3D35e992adc0678ccd98328d33c9a5ffc88dbb4dfa-3Bhb-3Drefs_heads_amsterdam=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ=jb5ycBf4M5z4CaqUuBmKXuHXR24In-b-euUEvW9sg9U=BNZ7o1M3JbXrR2lx_Xs1tpToY4nZ9R213fPj7Hkt18M=>

Thanks,
Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
<aroraa...@vmware.com<mailto:aroraa...@vmware.com>>
Date: Friday, December 1, 2017 at 8:45 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] Multiservices, Robot VMs come up without config 
directory and install script. Problem with AAI1 init

https://nexus.onap.org/content/sites/raw/org.onap.demo/heat/ONAP/1.1.0-SNAPSHOT<https://urldefense.proofpoint.com/v2/url?u=https-3A__nexus.onap.org_content_sites_raw_org.onap.demo_heat_ONAP_1.1.0-2DSNAPSHOT_onap-5Fopenstack.env=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=67N3o5f_muT_-94kKWrlvj7SGZJ66qGzL6WQ8OJfb0E=6ik7bdy_9Q2ctbhKfNvTC1WerHrjoNFCdJULxXGmu7U=>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Multiservices, Robot VMs come up without config directory and install script. Problem with AAI1 init

2017-12-01 Thread PLATANIA, MARCO (MARCO)

Hi Arun,

No, they aren’t known issues. However, I suggest you to use the templates here: 
https://nexus.onap.org/content/sites/raw/org.onap.demo/heat/ONAP/1.1.1/ or in 
Gerrit (demo repo – Amsterdam branch). The template you are using has docker 
images released for Amsterdam but use the master branch that is for Beijing. 
That worked soon after the release, but some teams have already made new 
contributions to master that may not be necessarily in sync with the docker 
released for Amsterdam.

Also, please get the latest docker version numbers from the Manifest file in 
the Integration repo: 
https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=version-manifest/src/main/resources/docker-manifest.csv;h=35e992adc0678ccd98328d33c9a5ffc88dbb4dfa;hb=refs/heads/amsterdam

Thanks,
Marco

From:  on behalf of "Arun Arora (c)" 

Date: Friday, December 1, 2017 at 8:45 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Multiservices, Robot VMs come up without config 
directory and install script. Problem with AAI1 init

https://nexus.onap.org/content/sites/raw/org.onap.demo/heat/ONAP/1.1.0-SNAPSHOT
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

2017-11-30 Thread PLATANIA, MARCO (MARCO)

Bin,

Are you talking about the k8s cluster? If so, please look at these best 
practices: 
https://kubernetes.io/docs/tasks/administer-cluster/highly-available-master/

Marco

From: "HU, BIN" <bh5...@att.com>
Date: Thursday, November 30, 2017 at 12:54 PM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"eric.deb...@orange.com" <eric.deb...@orange.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

Is there a typical cluster configuration documented somewhere? such as:

-  Recommended number of master nodes for HA?

-  Recommended number of worker nodes?

-  Recommended capacity of each master node (CPUs, RAM and storage)?

-  Recommended capacity of each worker node (CPUs, RAM and storage)?

Thanks
Bin

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Thursday, November 30, 2017 8:55 AM
To: eric.deb...@orange.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

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

You are right saying that full HA deployment will require a lot of resources, 
but that is true for the Heat approach only. If we use K8s, instead of 7 VMs 
for SDNC (SDNC here is just an example, based on numbers that Dan provided) we 
have 3 times (still based on Dan’s numbers) the number of containers that SDNC 
runs in a non-replicated environment.

Then, we need to adjust the size of the cluster accordingly. As I said in a 
previous email, the resource required by each single container depend on what 
that container does. I don’t have number to share, except that, based on OOM 
Team’s experience, 64 GB worked well for non-replicated ONAP (excluding DCAE). 
I expected that number going up when we use HA, but still reasonably, not even 
close to what Heat would require.

Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "eric.deb...@orange.com<mailto:eric.deb...@orange.com>" 
<eric.deb...@orange.com<mailto:eric.deb...@orange.com>>
Date: Thursday, November 30, 2017 at 11:38 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource 
needs

Hello

We first need to define what we want to test on the labs.

We need various platforms to test at least a minimal installation on various 
environments to validate that the installation works fine in different 
environments (ie 3 different platforms) in a daily basis.
I believe that we need around 100~150 GB RAM memory for that (we are working to 
optimize a minimal installation).
We can offer our lab for that.

Each project should test their various modules in standalone and cluster mode 
and that should not require such many resources on a project basis.

Now, do we need to test a full HA mode for all the components ?
If yes, It may require a huge amount of resources according to first answers 
(eg SDNC) running on different platforms.
We need to estimate that.

Best Regards

Eric

_

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-release] ACTION REQUIRED: Estimating LAB resource needs

2017-11-30 Thread PLATANIA, MARCO (MARCO)

Eric,

You are right saying that full HA deployment will require a lot of resources, 
but that is true for the Heat approach only. If we use K8s, instead of 7 VMs 
for SDNC (SDNC here is just an example, based on numbers that Dan provided) we 
have 3 times (still based on Dan’s numbers) the number of containers that SDNC 
runs in a non-replicated environment.

Then, we need to adjust the size of the cluster accordingly. As I said in a 
previous email, the resource required by each single container depend on what 
that container does. I don’t have number to share, except that, based on OOM 
Team’s experience, 64 GB worked well for non-replicated ONAP (excluding DCAE). 
I expected that number going up when we use HA, but still reasonably, not even 
close to what Heat would require.

Marco

From:  on behalf of 
"eric.deb...@orange.com" 
Date: Thursday, November 30, 2017 at 11:38 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource 
needs

Hello

We first need to define what we want to test on the labs.

We need various platforms to test at least a minimal installation on various 
environments to validate that the installation works fine in different 
environments (ie 3 different platforms) in a daily basis.
I believe that we need around 100~150 GB RAM memory for that (we are working to 
optimize a minimal installation).
We can offer our lab for that.

Each project should test their various modules in standalone and cluster mode 
and that should not require such many resources on a project basis.

Now, do we need to test a full HA mode for all the components ?
If yes, It may require a huge amount of resources according to first answers 
(eg SDNC) running on different platforms.
We need to estimate that.

Best Regards

Eric

_



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-release] ACTION REQUIRED: Estimating LAB resource needs

2017-11-30 Thread PLATANIA, MARCO (MARCO)

I don’t think there is a real relationship between number of containers and 
resource needed, it mainly depends on what kind of computation you are doing. I 
leave the answer to the experts (OOM team) but a while ago I was told that on 
average you roughly need 2 GB per container, but I don’t know how accurate this 
is.

Today’s OOM cluster is 64 GB (without DCAE). That seems OK for non-replicated 
ONAP.

Marco

From: "FREEMAN, BRIAN D" <bf1...@att.com>
Date: Thursday, November 30, 2017 at 9:46 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, Gildas Lanilis 
<gildas.lani...@huawei.com>, "TIMONEY, DAN" <dt5...@att.com>, onap-release 
<onap-rele...@lists.onap.org>
Cc: onap-discuss <onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

That does make sense – perhaps another set of columns or separate table for 
container data.

How do you measure/estimate the memory needed for a container ?

Brian



From: PLATANIA, MARCO
Sent: Thursday, November 30, 2017 9:41 AM
To: FREEMAN, BRIAN D <bf1...@att.com>; Gildas Lanilis 
<gildas.lani...@huawei.com>; TIMONEY, DAN <dt5...@att.com>; onap-release 
<onap-rele...@lists.onap.org>
Cc: onap-discuss <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

Brian,

Thanks for the clarification, I was also confused. Resource assessment is 
important for HEAT, which needs to know #CPUs, memory, etc. of each specific VM.

If we use OOM for Beijing (as I understand), in my opinion the right way to 
think about it is container-level, rather than VM-level. This means that PTLs 
should tell how many instances of their component they need (or, put in another 
way, how many replicas of their containers they need). Resource sizing is then 
made at cluster level. Depending on how many containers we’ll need to support, 
the OOM cluster size will be adjusted.

Does it make sense?

Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "FREEMAN, BRIAN D" <bf1...@att.com<mailto:bf1...@att.com>>
Date: Thursday, November 30, 2017 at 9:07 AM
To: Gildas Lanilis 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>, "TIMONEY, DAN" 
<dt5...@att.com<mailto:dt5...@att.com>>, onap-release 
<onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>
Cc: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

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


Folks,

Just some clarity based on responses so far.

The goal is to estimate the cloud resources we will need for testing and to 
help guide the testing strategy since likely will not have enough main memory 
for all the instances we had in Amsterdam with HA and Geo.

We are assuming OOM to minimize the footprint so the VM numbers are less 
relevant.

Today in HEAT a full Amsterdam is about 300 GB of main memory (SB01) – DCAE is 
already clustered

If we go with HA/Clustering that becomes “roughly”  600 GB (assuming DCAE is 
bulk of current memory utilization)  for one site and 1.2 TB for two sites but 
not all components need to scale the same way and there is  efficiency with OOM.

To the extent you can assess the memory you need in OOM with clustering that 
would be really helpful.

Brian



From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Wednesday, November 29, 2017 5:31 PM
To: TIMONEY, DAN <dt5...@att.com<mailto:dt5...@att.com>>; onap-release 
<onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>
Cc: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; FREEMAN, 
BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>
Subject: RE: [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

Thanks Dan for your prompt feedback.
Good point. I would suggest you add this point as a comment and we will take it 
from there.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Wednesday, November 29, 2017 1:56 PM
To: Gildas Lanilis 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>; onap-release 
<onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>
Cc: onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>; FREEMAN, 
BRIAN D <bf1...@att.com<mailto:bf1...@att.com>>
Subject: Re: [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

Gildas,

This is an excellent topic – thanks for starting this discussi

Re: [onap-discuss] VFW/vLB External Network Connect fails

2017-11-30 Thread PLATANIA, MARCO (MARCO)

I was pretty sure the private key was mismatching the public key used during 
the installation, but this doesn’t seem to be the case. Security group can be 
an issue, even though he’s able to access the VMs via the private network.

Is the path to the private key correct when you try to access them via the 
public IP? I can’t think of other possible causes.

Marco

From:  on behalf of "FREEMAN, BRIAN D" 

Date: Thursday, November 30, 2017 at 9:38 AM
To: "Arun Arora (c)" , "onap-discuss@lists.onap.org" 

Subject: Re: [onap-discuss] VFW/vLB External Network Connect fails

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


Hmm – cant help – dont know if your environment is doing security groups that 
blocks by default. Perhaps Marco has run into this problem before.

Brian


From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Thursday, November 30, 2017 9:33 AM
To: onap-discuss@lists.onap.org; FREEMAN, BRIAN D 
Subject: RE: VFW/vLB External Network Connect fails

No, the keypair is fine. Also I am using the keypair I created and not the one 
which comes as default in demo's env file.
I am able to ssh on VM on its ONAP network interface in any scenario but not on 
external network interface when the VM had interfaces for both networks created 
by Demo Stack.
Thanks
Arun


From: FREEMAN, BRIAN D
Sent: Thursday, November 30, 7:58 PM
Subject: RE: VFW/vLB External Network Connect fails
To: Arun Arora (c), 
onap-discuss@lists.onap.org


We usually only log in via the external IP for testing – seems strange that 
behavoir would change by detaching interfaces but we it is a VPP application so 
the protected/unprotected vNICs shouldn’t really be setup for login.

Is the problem that the public key used in preload doesnt match the private.key 
you are using ?

Brian






From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Thursday, November 30, 2017 9:14 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] VFW/vLB External Network Connect fails

Hi All,

While trying to create vFW and vLB/ vDNS demos I am facing the following issue 
in both demos:
For both demos able to create the stack which creates 3 VMs and their 
associated networks In vFW demo, vFirewall application VM has both ‘protected’ 
and ‘unprotected’ networks configured on its interfacesIn vLB/ vDNS demo, 
Load-Balance VM has both ‘lb01_private’ and ‘pktget01_private’ networks 
configured on its interfaces Issue: SSH on both VMs (“vFirewall application VM” 
and “Load-Balance VM”) fails when its done using their External Interface IP or 
the IPs from the networks created with the demo stacks (i.e.  ‘protected’, 
‘unprotected’, ‘lb01_private’ or ‘pktget01_private’)I can only SSH then through 
the IP assigned by ONAP networkFurther to this, if any interface on ‘protected’ 
and ‘unprotected’ is detached from vFirewall application VM, and VM is 
restarted then SSH using external interface works!! Same happens for 
Load-Balance VM!

Is this issue seen by anyone? Any pointers to resolve this?

Thanks,
Arun


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

Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

2017-11-30 Thread PLATANIA, MARCO (MARCO)

Brian,

Thanks for the clarification, I was also confused. Resource assessment is 
important for HEAT, which needs to know #CPUs, memory, etc. of each specific VM.

If we use OOM for Beijing (as I understand), in my opinion the right way to 
think about it is container-level, rather than VM-level. This means that PTLs 
should tell how many instances of their component they need (or, put in another 
way, how many replicas of their containers they need). Resource sizing is then 
made at cluster level. Depending on how many containers we’ll need to support, 
the OOM cluster size will be adjusted.

Does it make sense?

Marco

From:  on behalf of "FREEMAN, BRIAN D" 

Date: Thursday, November 30, 2017 at 9:07 AM
To: Gildas Lanilis , "TIMONEY, DAN" 
, onap-release 
Cc: onap-discuss 
Subject: Re: [onap-discuss] [Onap-release] ACTION REQUIRED: Estimating LAB 
resource needs

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


Folks,

Just some clarity based on responses so far.

The goal is to estimate the cloud resources we will need for testing and to 
help guide the testing strategy since likely will not have enough main memory 
for all the instances we had in Amsterdam with HA and Geo.

We are assuming OOM to minimize the footprint so the VM numbers are less 
relevant.

Today in HEAT a full Amsterdam is about 300 GB of main memory (SB01) – DCAE is 
already clustered

If we go with HA/Clustering that becomes “roughly”  600 GB (assuming DCAE is 
bulk of current memory utilization)  for one site and 1.2 TB for two sites but 
not all components need to scale the same way and there is  efficiency with OOM.

To the extent you can assess the memory you need in OOM with clustering that 
would be really helpful.

Brian



From: Gildas Lanilis [mailto:gildas.lani...@huawei.com]
Sent: Wednesday, November 29, 2017 5:31 PM
To: TIMONEY, DAN ; onap-release 
Cc: onap-discuss ; FREEMAN, BRIAN D 

Subject: RE: [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

Thanks Dan for your prompt feedback.
Good point. I would suggest you add this point as a comment and we will take it 
from there.

Thanks,
Gildas
ONAP Release Manager
1 415 238 6287

From: TIMONEY, DAN [mailto:dt5...@att.com]
Sent: Wednesday, November 29, 2017 1:56 PM
To: Gildas Lanilis 
>; onap-release 
>
Cc: onap-discuss 
>; FREEMAN, 
BRIAN D >
Subject: Re: [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

Gildas,

This is an excellent topic – thanks for starting this discussion!

One suggestion – we might want to separate out the HA/Geo Redundancy columns 
into 2 sets : one set for local HA only, and a second set for Geo Redundancy.

Just by way of example, in the case of SDN-C, we’d need 1 VM for no redundancy, 
8 for local HA, and 16 for geo redundancy.

I know that our target is geo redundancy, but it might be good to have a view 
of resources for local HA only as well.  That way, if we find we can’t afford 
the VMs for full geo redundancy, we’ll know the minimal set for local HA as 
well.

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.


From: 
>
 on behalf of Gildas Lanilis 
>
Date: Wednesday, November 29, 2017 at 3:31 PM
To: onap-release 
>
Cc: onap-discuss 
>, "FREEMAN, 
BRIAN D" >
Subject: [Onap-release] ACTION REQUIRED: Estimating LAB resource needs

Hi PTLs,

We need your help.
We are working with Catherine, Helen and Brian on estimating the needs in term 
of Integration Lab resources for Beijing Release. This is important as it will 
most certainly impact $ budget and thus may require TSC and GB approval.
The details have been posted in the wiki at

[onap-discuss] videos about VNF creation, vFW and vLB/vDNS closed loops

2017-11-28 Thread PLATANIA, MARCO (MARCO)

Team,

I created a new table named “VNF Onboarding, Instantiation, and Closed-loop 
Operations” on the wiki: https://wiki.onap.org/display/DW/Running+the+ONAP+Demos

I created and uploaded three new videos:

· VNF onboarding and service creation: it shows how to onboard VNFs and 
create services with ONAP. It focuses on the vFW, but the same procedure can be 
used to onboard many other VNFs

· vFW closed-loop

· vLB/vDNS closed-loop

The vFW and vLB/vDNS closed-loop videos show how to run closed-loop operations 
step by step. I also uploaded the VNF topology data used to preload SDNC (for 
both vFW and vLB/vDNS) and the APPC mount point for the vFW closed loop.

Hope this helps.

Marco

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

Re: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No valid host was found. There are not enough hosts available., Code: 500""

2017-11-27 Thread PLATANIA, MARCO (MARCO)

Michael, All,


1.   Please use vFWCL, which supports closed loop for Amsterdam Release. We 
split vFW and vPacketGen for closed loop, perhaps we will have a single 
template for Beijing, but for the moment please go ahead with vFWCL.

2.   No

3.   No

4.   Yes

Regarding the private/public key pair, this doesn’t get overridden by SDC or 
redistribution. The key that you set in the Heat template stays. The only way 
to override it is in the SDNC preload, but this is not necessary if you already 
set the key in the Heat template.

In general, the 3 VMs get external IP addresses and you should be able to ping 
and ssh them as root. However, IP issues were observed in the past. Nothing 
related to ONAP, Heat, or the vFW per se, just lack of external IPs or some 
misconfiguration in the OpenStack settings.

Marco

From:  on behalf of Michael O'Brien 

Date: Monday, November 27, 2017 at 9:06 AM
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No 
valid host was found. There are not enough hosts available., Code: 500""

Going through this issue this morning with some of you - it looks like we have 
a couple questions that we will get answers for in the noon meeting


1)   Do we use the older vFW template or the new split vFWCL template with 
the PORTAL-409 fix from the 4th nov – or both

2)   Does the ssh key in the older vFW still get overridden by any sdc 
distribute override

3)   Does the ssh key we manually add at design time to the vFWCL env(2) 
files get overridden by any override in SDC distribute as well

4)   I would expect any default key in the env to work out of the box 
otherwise



Observation: the vFW sink on Integration SB-00 on 10.12.6.60 works (no closed 
loop yet via (dcae/policy/appc) and generates the :667 graph in a curl/browser 
– so we have a good target

I tried getting into this one with the default key but I don’t know whether it 
was generated by 1 or 2 or SDC overridden



In cases where the private and assigned IPs are still not accessible – even 
from robot – attach a 3rd floating ip – as the vFW has its own subnet.



These questions are on top of the other ones we will verify (preload via 
robot/post or both, appc mount via robot/post or both)

Basically, we should have some documentation on these today/this week as we 
finish with the distribute step



See you later at 1200EDT.

https://wiki.onap.org/display/DW/Vetted+vFirewall+Demo+-+Full+draft+how-to+for+F2F+and+ReadTheDocs

/michael



From: FREEMAN, BRIAN D [mailto:bf1...@att.com]
Sent: Monday, November 27, 2017 08:52
To: Arun Arora (c) ; onap-discuss@lists.onap.org; 
PLATANIA, MARCO 
Cc: Ramki Krishnan ; Ramesh Tammana ; 
Gaurav Gupta (c) ; Michael O'Brien 

Subject: RE: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No 
valid host was found. There are not enough hosts available., Code: 500""

Arun,

I dont know what problem you are getting into. Assigning the floating IP’s 
after the fact seems strange but theres nothing that would be different for the 
3 VM’s that I know of that would work for one and not the other 2 wrt logging 
in.

Perhaps using the concole port to see if the VM cloud-init log has any 
indications.

Without an external IP I’m not sure the applications can do their install so I 
think you need to get the external network configuration working.

Brian

From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Friday, November 24, 2017 9:38 AM
To: onap-discuss@lists.onap.org; FREEMAN, 
BRIAN D >; PLATANIA, MARCO 
>
Cc: Ramki Krishnan >; Ramesh 
Tammana >; Gaurav Gupta (c) 
>; OBRIEN, FRANK MICHAEL 
>
Subject: RE: [onap-discuss] vFW Demo Stack Create Fails with ""Message: No 
valid host was found. There are not enough hosts available., Code: 500""

Hi All, Brian, Marco,

Out of the 3 VMs for vFW demo, I am able to login to only Traffic Generator VM. 
The floating IPs of rest 2 VMs are not pingable and I am not able to ssh in 
them as well.
FYI, all three VMs have same key pair and for all floating IP was assigned 
manually as

Re: [onap-discuss] R1 Blitz: Intermittent AAI-vm1 container startup failures in HEAT - manual /opt/aai_install.sh fails but installs docker and pulls images

2017-11-26 Thread PLATANIA, MARCO (MARCO)

Michael,

We saw similar intermittent failures in cloud init. This is not related to heat 
in particular, but I agree that a component installation is incomplete if cloud 
init fails. We had to re-run the install script to bring up an affected 
component.

Marco

From:  on behalf of Michael O'Brien 

Date: Sunday, November 26, 2017 at 1:13 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] R1 Blitz: Intermittent AAI-vm1 container startup 
failures in HEAT - manual /opt/aai_install.sh fails but installs docker and 
pulls images

Team,
   I am experiencing the aai-vm1 startup errors we previously saw last week in 
HEAT.  I deployed the latest yaml to open-lab and am having an issue manually 
bringing up the 6 containers in aai1 – specifically the resources one again.  I 
understand there may be a set of scripts developed to work around the 
intermittent issue where vm1 is deployed before vm2.
   After 1 hour aai1 had not even pulled docker images until I manually started 
the install scripts off the /opt dir – shouldn’t these normally be bootstrapped?
   Aai-vm2’s hbase and es are up fine.

   It is an intermittent issue because I have seen deployments from last week 
where AAI fully works. The current workaround is to delete/recreate the entire 
HEAT stack.
   Let us know if there is another workaround.

https://jira.onap.org/browse/AAI-513



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

Re: [onap-discuss] ONAP installation on vanilla openstack

2017-11-22 Thread PLATANIA, MARCO (MARCO)

Hello Muhammad,

Please use the latest templates in Gerrit (yaml and env files): 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=77a6ce1f507981e0c4f0515a5fcc5fbd6db84660;hb=refs/heads/master

The template you are using is pretty old.

Thanks,
Marco

From:  on behalf of Muhammad Ali 

Date: Wednesday, November 22, 2017 at 8:52 AM
To: "onap-discuss@lists.onap.org" 
Cc: Abhi Thorat 
Subject: [onap-discuss] ONAP installation on vanilla openstack

Hi,

I’ve started deploying ONAP using the following Heat template.

https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/OpenECOMP/1.1.0-SNAPSHOT/onap_openstack.yaml

Stack creation was successful in Openstack. VMs and networks are up running.

However, Portal VM was not configured correctly, below is the output of “docker 
ps -a” from portal VM.

root@vm1-portal:/opt# docker ps -a
CONTAINER IDIMAGE   COMMAND  CREATED
 STATUS  PORTS   NAMES
a07f1099790dmariadb "docker-entrypoint..."   2 hours ago
 Created data_vol_portal

Is this the correct output? I’m wondering if there should be more active 
containers of ecomp portal and its components.

Below are my findings, when manually executed the portal_install.sh file.

<…>
docker stop/waiting
docker start/running, process 20839
Cloning into 'portal'...
remote: Finding sources: 100% (6754/6754)
remote: Total 6754 (delta 2747), reused 6754 (delta 2747)
Receiving objects: 100% (6754/6754), 16.28 MiB | 3.46 MiB/s, done.
Resolving deltas: 100% (2747/2747), done.
Checking connectivity... done.
Already up-to-date.
chmod: cannot access ‘portal/deliveries/new_start.sh’: No such file or directory
chmod: cannot access ‘portal/deliveries/new_stop.sh’: No such file or directory
chmod: cannot access ‘portal/deliveries/dbstart.sh’: No such file or directory
unzip:  cannot find or open portal/deliveries/etc.zip, 
portal/deliveries/etc.zip.
Login Succeeded
1.1-STAGING-latest: Pulling from openecomp/portaldb
4a441ce0e165: Pull complete
a1ddcbe73394: Pull complete
<…snipped…>
Status: Downloaded newer image for mariadb:latest
a07f1099790d8b19db7906b7bd337459d4b0676c08b9515fe6d0d3ba7872ff19
Error response from daemon: No such container: ecompdb_portal
Error response from daemon: No such container: 1610-1
Error response from daemon: No such container: widget-ms:latest
./portal_vm_init.sh: line 35: ./dbstart.sh: No such file or directory
./portal_vm_init.sh: line 36: ./new_start.sh: No such file or directory
./portal_vm_init.sh: line 37: ./widget_ms_start.sh: No such file or directory

And script hangs there.

Below is my heat env file.

 nexus_repo: 
https://nexus.onap.org/content/sites/raw
  nexus_docker_repo: nexus3.onap.org:10001
  nexus_username: docker
  nexus_password: docker
  dmaap_topic: AUTO
 artifacts_version: 1.1.0-SNAPSHOT
  docker_version: 1.1-STAGING-latest
  gerrit_branch: master
  openstack_tenant_id: admin
  openstack_username: admin
  cloud_env: openstack

Seems like, it is missing some *start.sh scripts from the repo.

Can you please point me to the correct upstream repo? Also, kindly review the 
my env config, if there is something that I need to modify/update.

Any help will be appreciated in this regard.

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

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread PLATANIA, MARCO (MARCO)

Yes, this is what I suggested in a separate email.

Marco

From: "TIMONEY, DAN" <dt5...@att.com>
Date: Wednesday, November 15, 2017 at 4:32 PM
To: "BARSKY, GEORA" <geo...@amdocs.com>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>, Arun Arora <arun_ar...@outlook.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, 
"sylvain.desbure...@orange.com" <sylvain.desbure...@orange.com>, "OBRIEN, FRANK 
MICHAEL" <frank.obr...@amdocs.com>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Geora,

The release-1.1.0 branch is pre-Amsterdam seed code.   You want to be using the 
master branch, which should be working fine.

The sdnc_install.sh script sets GERRIT_BRANCH (which is where it does the pull) 
to the contents of /opt/config/gerrit_branch.txt.  I’m not sure how that’s set 
(Marco would know that better than me), but it sounds like that’s set to 
release-1.1.0 instead of master.

Marco – can they just update that file and re-run sdnc-install.sh?

Dan

--
Dan Timoney
SDN-CP / OpenECOMP SDN-C SSO

Please go to  D2 ECOMP Release Planning 
Wiki<https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for 
D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find 
key Release Planning Contact Information.

From: <onap-discuss-boun...@lists.onap.org> on behalf of "BARSKY, GEORA" 
<geo...@amdocs.com>
Date: Wednesday, November 15, 2017 at 4:16 PM
To: "PLATANIA, MARCO" <plata...@research.att.com>, Arun Arora 
<arun_ar...@outlook.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>, "sylvain.desbure...@orange.com" 
<sylvain.desbure...@orange.com>, "OBRIEN, FRANK MICHAEL" 
<frank.obr...@amdocs.com>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest

During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}

Thanks

Geora Barsky
Amdocs Technology
647-688-1039

[docs-a]

Follow us on 
Facebook<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_amdocs_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo=Dw1-UGXnb-wT2UsV7miTa839sklh6NZYqmUybN7T-I8=>,

Twitter<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_amdocs=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo=Ra-vPiL3TdS6TfrtkPQ_O1F5PbHahT2Vc9jpjyu_qko=>,

LinkedIn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_amdocs=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo=Zv9_KYcaWy--k2eplJHg4kAoqGucbhYjLZtDytwMcLs=>,

YouTube<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_amdocsinc=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo=qwDjnw3jv6tlX0LOZw0iKpGndJAuj-oamu0gmPRcbQo=>,

Google+<https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_105657940751678445194=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo=vsM7wmSd0b4KGyO5Y-BGORyohptG77YsMAsUr6Sfwag=>
 and the Amdocs blog 
network<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.amdocs.com_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=qLcfee4a2vOwYSub0bljcQ=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo=QbJpaKW_Y-MRqu2gvVqMjPhxUbf6hLR7od8KAlcxTdU=>.

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Wednesday, November 15, 2017 1:27 PM
To: Arun Arora <arun_ar...@outlook.com>; onap-discuss@lists.onap.org; 
sylvain.desbure...@orange.com; Michael O'Brien <frank.obr...@amdocs.com>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue 
with MSB though, because the docker version in Heat is wrong. It is v1.0.0, 
while it should be 1.0.0 (without v). I’m going to submit a change soon, please 
update your local Heat env.

Arun,

If you are using an old heat template, please switch to the latest one: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master<https://urldefens

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread PLATANIA, MARCO (MARCO)

Geora,

Please change /opt/config/gerrit_branch.txt from release-1.1.0 to master and 
retry.

Thanks,
Marco

From: Geora Barsky <geo...@amdocs.com>
Date: Wednesday, November 15, 2017 at 4:16 PM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, Arun Arora 
<arun_ar...@outlook.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>, "sylvain.desbure...@orange.com" 
<sylvain.desbure...@orange.com>, Michael O'Brien <frank.obr...@amdocs.com>
Subject: RE: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco,

In addition to below , I also noticed that there is an issue with 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml .

It points to openecomp/images instead of onap

sdnc:
image: openecomp/sdnc-image:latest

During the installation it seems like this code is  pulled from release-1.1.0 
branch :

As a result we fail :

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest
Pulling sdnc (openecomp/sdnc-image:latest)...
ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or 
no pull access"}

Thanks

Geora Barsky
Amdocs Technology
647-688-1039

[mdocs-a]

Follow us on 
Facebook<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_amdocs_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=mfb9tikoBGuYOfSUY6Hz1mQwJ12tKO1VplOTaiLODPQ=adFGO6Es2dMOFT-tbX1t3ozqOVwTNUGsWt8uRQd4A-k=>,

Twitter<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_amdocs=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=mfb9tikoBGuYOfSUY6Hz1mQwJ12tKO1VplOTaiLODPQ=7oe_0fYInhakcmiYLVo3IF7QqIlyvicTRlfLuCK9ZTI=>,

LinkedIn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_amdocs=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=mfb9tikoBGuYOfSUY6Hz1mQwJ12tKO1VplOTaiLODPQ=5-xaX1dW3XAV_21S66UW2Uzgm80Lysco2uq1j_5QWUA=>,

YouTube<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_amdocsinc=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=mfb9tikoBGuYOfSUY6Hz1mQwJ12tKO1VplOTaiLODPQ=3M81JGCLnBxpqbgmctZnP8XPYhowuWL80pNP05Ct6YE=>,

Google+<https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_105657940751678445194=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=mfb9tikoBGuYOfSUY6Hz1mQwJ12tKO1VplOTaiLODPQ=TR8u11wKC0NvqGrQzeNYwMA5nfE-_lR0uVX1LXl9-gs=>
 and the Amdocs blog 
network<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.amdocs.com_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=mfb9tikoBGuYOfSUY6Hz1mQwJ12tKO1VplOTaiLODPQ=I3WnwvoSZOB1xtnVRO0SDwTfPx63HxIInvPuZ6l5vgg=>.

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Wednesday, November 15, 2017 1:27 PM
To: Arun Arora <arun_ar...@outlook.com>; onap-discuss@lists.onap.org; 
sylvain.desbure...@orange.com; Michael O'Brien <frank.obr...@amdocs.com>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue 
with MSB though, because the docker version in Heat is wrong. It is v1.0.0, 
while it should be 1.0.0 (without v). I’m going to submit a change soon, please 
update your local Heat env.

Arun,

If you are using an old heat template, please switch to the latest one: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dtree-3Bf-3Dheat_ONAP-3Bh-3Df948399f5fcbe2300f0d7b8417792aea4682425d-3Bhb-3Drefs_heads_master=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=mfb9tikoBGuYOfSUY6Hz1mQwJ12tKO1VplOTaiLODPQ=d1zlIhzKqUUtyqGxD9rmKAarbVQ8EaVNUPNG4zLNCMc=>

/opt/config/nexus_docker_repo.txt in the SDNC VM is used by the vm_init script 
to point to the Nexus repository. Make sure you have port 10001 instead of 
10003 in that file.

Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Arun Arora <arun_ar...@outlook.com<mailto:arun_ar...@outlook.com>>
Date: Wednesday, November 15, 2017 at 12:23 PM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Following JIRA Ticket: 
https://jira.onap.org/browse/SDNC-102<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDNC-2D102=DwMFAg=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=jJs8089honCN-dSntDLJk

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

2017-11-15 Thread PLATANIA, MARCO (MARCO)

Arun, Sylvain, Michael,

I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue 
with MSB though, because the docker version in Heat is wrong. It is v1.0.0, 
while it should be 1.0.0 (without v). I’m going to submit a change soon, please 
update your local Heat env.


Arun,

If you are using an old heat template, please switch to the latest one: 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master

/opt/config/nexus_docker_repo.txt in the SDNC VM is used by the vm_init script 
to point to the Nexus repository. Make sure you have port 10001 instead of 
10003 in that file.

Marco

From:  on behalf of Arun Arora 

Date: Wednesday, November 15, 2017 at 12:23 PM
To: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails


Following JIRA Ticket: 
https://jira.onap.org/browse/SDNC-102



was created for this issue and marked as Resolved and Closed. However, the 
issue still seems to be present.



In comments it was mentioned to change the port from 10003 to 10001 in 
docker-compose.yml.

But I didn't find any such port in 
/opt/sdnc/installation/src/main/yaml/docker-compose.yml.



Can someone provide me a working hack..



Thanks,

Arun Arora




[SDNC-102] SDNC Failed Robot Health Check - 
ONAP
jira.onap.org
No reviews matched the request. Check your Options in the drop-down menu of 
this sections header.



From: onap-discuss-boun...@lists.onap.org  
on behalf of Arun Arora 
Sent: Wednesday, November 15, 2017 10:37:33 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [SDNC] sdnc_vm_init.sh fails




ERROR: {"message":"repository onap/sdnc-image not found: does not exist or no 
pull access"}



Hi All,



I am seeing this error since yesterday. I tried to re-pull SDNC dockers afresh. 
For that I deleted all dockers along with all the files/ directories downloaded 
in /opt when sdnc_install.sh runs.



I tried this many times but the I receive the same error above in each trial.



What may be the reason of this error? I doubt it is some local setup issue as I 
re-pulled other VMs as well along with SDNC but didn't see any such error.



Is this seen by someone else? Any possible solutions?



Thanks,

Arun Arora




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

Re: [onap-discuss] 答复: RE: question about sdc_vm_init

2017-11-14 Thread PLATANIA, MARCO (MARCO)

If this is not strictly required for Amsterdam, please wait till we cut the 
release on Thursday.

Marco

From: "FREEMAN, BRIAN D" <bf1...@att.com>
Date: Monday, November 13, 2017 at 9:37 PM
To: "lv.bo...@zte.com.cn" <lv.bo...@zte.com.cn>, "LANDO, MICHAEL" 
<ml6...@intl.att.com>, "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] 答复: RE: question about sdc_vm_init

Sometimes the repo to clone is the start script that is the last line in the 
vm_init.sh script.

But for sdc it looks like it is supposed to be in the vm_install.sh but I dont 
have  fresh environment.
On an old environment the remote url for orign is shown below.

root@vm1-sdc:/opt/sdc# git remote get-url --all  origin
http://gerrit.onap.org/r/sdc.git

I;ve never seen the work flow designer so not sure of the repo to use.

Did you simply check gerrit.onap.org under project list filter for sdc

Brian

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of lv.bo...@zte.com.cn
Sent: Monday, November 13, 2017 8:31 PM
To: LANDO, MICHAEL <ml6...@intl.att.com>; PLATANIA, MARCO 
<plata...@research.att.com>
Cc: onap-discuss@lists.onap.org
Subject: [onap-discuss] 答复: RE: question about sdc_vm_init

Marco and Michael,

I checked the sdc_vm_init.sh file and did not found where to set the parameters 
of what repo to clone.

Then, I thought the sdc_workflow_designer repo already existed. I just need to 
pull the new version.

But Marco said there is no sdc_workflow_designer repo under opt/ in sdc vm.

So again, how should I get the repo on sdc vm ?

原始邮件
发件人： <ml6...@intl.att.com<mailto:ml6...@intl.att.com>>;
收件人：吕波10185543; <plata...@research.att.com<mailto:plata...@research.att.com>>;
抄送人：赵化冰10201488; 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;
日 期 ：2017年11月05日 20:42
主 题 ：RE: question about sdc_vm_init
As far as I think.
You should have clone of your repo as part of the init.
The init hase paremeters to define from what repo to clone.
Once cloned the run script should be part of it.

BR,

Michael Lando
Opensource TL , SDC
AT Network Application Development · NetCom
Tel Aviv | Tampa | Atlanta | New Jersey |Chicago
···
Office: +972 (3) 5451487
Mobile: +972 (54) 7833603
e-mail: ml6...@intl.att.com<mailto:ml6...@intl.att.com>

From: lv.bo...@zte.com.cn<mailto:lv.bo...@zte.com.cn> 
[mailto:lv.bo...@zte.com.cn]
Sent: Thursday, November 02, 2017 4:34 AM
To: Lando,Michael <ml6...@intl.att.com<mailto:ml6...@intl.att.com>>; PLATANIA, 
MARCO <plata...@research.att.com<mailto:plata...@research.att.com>>
Cc: zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: question about sdc_vm_init

Hi,

I'm writing a docker_run.sh scipt for workflow designer which should be invoked 
when sdc vm init.

I checked the script in sdc_vm_init.sh(under demo/boot). I found there is a 
local repo of sdc. The docker_run.sh comes from the local repo  which will pull 
the latest sdc code.

My question is:  How shold the sdc vm get the latest version of workflow 
designer's docker_run.sh? Is that the same as the one in sdc? Is there a local 
repo of sdc-workflow-designer too?  Should I clone the sdc-workflow-designer 
repo to sdc vm myself?

Regards.

Lv Bo

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

Re: [onap-discuss] AAI-inst1 dockers not starting

2017-10-26 Thread PLATANIA, MARCO (MARCO)

Kapil,

I answered in a separate email thread, please refer to that email for details. 
One thing to note is that if you are using OpenStack on VMware, we never tested 
it, so there may be some environment-specific issue that we are not aware of. 
I’ve never seen the error that you report below.

Also, please onap_openstack.yaml/env.

Thanks,
Marco

From: "Kapil Gupta (c)" <gka...@vmware.com>
Date: Thursday, October 26, 2017 at 2:58 AM
To: "Kapil Gupta (c)" <gka...@vmware.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>, "onap-discuss-boun...@lists.onap.org" 
<onap-discuss-boun...@lists.onap.org>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>
Subject: RE: [onap-discuss] AAI-inst1 dockers not starting

Hi Marco,

I am able to fix this issue by doing some manual steps with docker-compose.

Thanks
Kapil
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kapil Gupta (c)
Sent: 26 October 2017 10:09
To: onap-discuss@lists.onap.org; onap-discuss-boun...@lists.onap.org; 
plata...@research.att.com
Subject: [onap-discuss] AAI-inst1 dockers not starting

Hi Marco,


We are deploying ONAP 1.1 with onap_openstack_float.env and 
onap_openstack_float.yaml.
15 VM’s were created and 3 robot health check  passed.

Some of  VM’s docker not starting and failing with error “Cannot open self 
/opt/docker/docker-compose or archive /opt/docker/docker-compose.pkg “

Please suggest the way forward.

Following is  AAi-inst1 logs

root@vm1-aai-inst1:/opt# docker images
REPOSITORYTAG  
IMAGE IDCREATED SIZE
nexus3.onap.org:10001/openecomp/aai-resources 1.1-STAGING-latest   
f8d70ac27c5116 hours ago680MB
nexus3.onap.org:10001/openecomp/aai-resources latest   
f8d70ac27c5116 hours ago680MB
nexus3.onap.org:10001/openecomp/aai-traversal 1.1-STAGING-latest   
030bded4f87916 hours ago680MB
nexus3.onap.org:10001/openecomp/aai-traversal latest   
030bded4f87916 hours ago680MB
nexus3.onap.org:10001/openecomp/sparky-be 1.1-STAGING-latest   
4fc6f17981304 weeks ago 601MB
nexus3.onap.org:10001/openecomp/sparky-be latest   
4fc6f17981304 weeks ago 601MB
nexus3.onap.org:10001/openecomp/search-data-service   1.1-STAGING-latest   
bbf847c9afc84 weeks ago 612MB
nexus3.onap.org:10001/openecomp/search-data-service   latest   
bbf847c9afc84 weeks ago 612MB
nexus3.onap.org:10001/openecomp/model-loader  1.1-STAGING-latest   
5bc33ca4db8a4 weeks ago 603MB
nexus3.onap.org:10001/openecomp/model-loader  latest   
5bc33ca4db8a4 weeks ago 603MB
nexus3.onap.org:10001/openecomp/data-router   1.1-STAGING-latest   
264e141534c15 weeks ago 603MB
nexus3.onap.org:10001/openecomp/data-router   latest   
264e141534c15 weeks ago 603MB

root@vm1-aai-inst1:/opt# docker ps -a
CONTAINER IDIMAGE   COMMAND CREATED 
STATUS  PORTS   NAMES

./aai_vm_init.sh failed with below error.
1.1-STAGING-latest: Pulling from openecomp/sparky-be
Digest: sha256:84ca3d38c6a61aab18ba11f060564e5d45a98da046fa98d521bf9846c3c5aaa0
Status: Image is up to date for 
nexus3.onap.org:10001/openecomp/sparky-be:1.1-STAGING-latest
Cannot open self /opt/docker/docker-compose or archive 
/opt/docker/docker-compose.pkg
Cannot open self /opt/docker/docker-compose or archive 
/opt/docker/docker-compose.pkg
Cannot open self /opt/docker/docker-compose or archive 
/opt/docker/docker-compose.pkg
Cannot open self /opt/docker/docker-compose or archive 
/opt/docker/docker-compose.pkg
Cannot open self /opt/docker/docker-compose or archive 
/opt/docker/docker-compose.pkg
A Microservices are successfully started

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

Re: [onap-discuss] ONAP 1.1 and HealthCheck pass requirement for attempting vFW/vDNS

2017-10-25 Thread PLATANIA, MARCO (MARCO)

Hello Gaurav,

vFW and vLB/vDNS use cases require Portal, SDC, AAI, SO, VID, SDNC, Policy, and 
DCAE to be healthy to run closed loop. If you want to test only the onboarding, 
distribution and instantiation, you don’t need Policy and DCAE.

Also, the Robot component is needed for preload data into AAI and SDNC.

Marco

From:  on behalf of "Gaurav Gupta (c)" 

Date: Wednesday, October 25, 2017 at 11:28 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] ONAP 1.1 and HealthCheck pass requirement for 
attempting vFW/vDNS


Hi There



in ONAP 1.1 we see that Number of health test  have been increased to 23 . what 
is the minimum number of health test and which healthtest be passed before vFW 
/vDNS Demo can be attempted . For example in ONAP 1.0 we can attempt the Demo 
only if the 9 out of 10 health test cases passed .





thanks

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

[onap-discuss] Integration Test Labs wikipage

2017-10-18 Thread PLATANIA, MARCO (MARCO)

Hi Team,

We created a new wiki page under the Integration Project that lists all the 
OpenStack labs that the Integration Team is currently supporting for testing 
activities. Here is the link: 
https://wiki.onap.org/display/DW/Integration+Test+Labs

This is a convenient way to keep track of ONAP labs and retrieve the IP 
addresses of the ONAP VMs in case you need/want to access a specific VM, e.g. 
for debugging purposes. SSH access requires a private key. The PTLs already 
received the key in a separate email. If you need the private key, please ask 
your PTL or the Integration Team.

Please visit this page often to learn which ONAP instances are currently up and 
what they are being used for. This page will be updated every time a new ONAP 
instance is created, such that you can get the latest IP addresses.

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

Re: [onap-discuss] [Integration] ESR deploy issue in Intel lab withdemo script

2017-10-12 Thread PLATANIA, MARCO (MARCO)

Hi LiZi,

I manually fixed also the other ONAP instance that is running in the 
Integration lab (Integration project in OpenStack). ESR containers are now 
available.

Marco

From: "li.z...@zte.com.cn" <li.z...@zte.com.cn>
Date: Thursday, October 12, 2017 at 2:06 AM
To: "helen.c...@huawei.com" <helen.c...@huawei.com>
Cc: "kang...@huawei.com" <kang...@huawei.com>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [Integration] ESR deploy issue in Intel lab 
withdemo script

Thanks Helen. I do have access to a integration test space, I just don't know 
the space name of the one I used. :)

Regards,

LiZi

原始邮件
发件人： <helen.c...@huawei.com>;
收件人： <kang...@huawei.com>;李滋00164331; <plata...@research.att.com>;
抄送人： <onap-discuss@lists.onap.org>;
日 期 ：2017年10月12日 12:07
主 题 ：Re: [onap-discuss] [Integration] ESR deploy issue in Intel lab withdemo 
script

Hi, Lizi,
If you haven’t got access to Integrtion-SB-01 yet, I am sure you have your own 
space and also Integration space available as well. Stephen is working on to 
give everyone access to all integration’s  testing space.

Regards,

Helen Chen

From: <onap-discuss-boun...@lists.onap.org> on behalf of Kang Xi 
<kang...@huawei.com>
Date: Wednesday, October 11, 2017 at 9:03 PM
To: "li.z...@zte.com.cn" <li.z...@zte.com.cn>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>
Cc: onap-discuss <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [Integration] ESR deploy issue in Intel lab with 
demo script

LiZi,

We are all using the same lab and the portal is the same. The lab is virtually 
divided into multiple work spaces. Integration-SB01 is one of the work space. 
Usually one person get access to  one or just a few work spaces. If you need 
access to other work spaces you will need to request from Stephen Gooch.

Regards,
Kang

From: li.z...@zte.com.cn [mailto:li.z...@zte.com.cn]
Sent: Wednesday, October 11, 2017 23:54
To: plata...@research.att.com
Cc: Kang Xi <kang...@huawei.com>; onap-discuss@lists.onap.org
Subject: Re: [Integration] ESR deploy issue in Intel lab with demo script

Hi Marco,

Thank you very much.  Which Integration-SB01 lab is? Can we folks have an 
access with it ?  I ususally test ESR in 
http://10.12.25.2/project/instances/<https://urldefense.proofpoint.com/v2/url?u=http-3A__10.12.25.2_project_instances_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=1_dm874GUnEct4EkN7R8lzTztEHpdYrI5SoAOiOXm44=sSn76MGRnRwA-tteq8GKtS7xPUUjHV_miv0N8Aer2H0=>
 which  provided by Stepthen and YangBin.  I know we have several labs for 
ONAP, but I am dizzy about the labs name or No.

Thanks

LiZi

原始邮件
发件人： <plata...@research.att.com<mailto:plata...@research.att.com>>;
收件人：李滋00164331; <kang...@huawei.com<mailto:kang...@huawei.com>>;
抄送人： <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>;
日 期 ：2017年10月12日 11:28
主 题 ：Re: [Integration] ESR deploy issue in Intel lab with demo script

Hi LiZi,

ESR didn’t get deployed because your contribution was merged after ONAP was 
build. I fixed this manually in the ONAP instance  in the Integration-SB01 lab. 
The containers are now running.

Marco

From: "li.z...@zte.com.cn<mailto:li.z...@zte.com.cn>" 
<li.z...@zte.com.cn<mailto:li.z...@zte.com.cn>>
Date: Wednesday, October 11, 2017 at 10:03 PM
To: "kang...@huawei.com<mailto:kang...@huawei.com>" 
<kang...@huawei.com<mailto:kang...@huawei.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, "PLATANIA, 
MARCO (MARCO)" <plata...@research.att.com<mailto:plata...@research.att.com>>
Subject: [Integration] ESR deploy issue in Intel lab with demo script

Hi Kang,

I add the script in demo repo, and hope it could deploy esr-server and esr-gui 
in openo vm in Intel lab automatically. But it seems that the ESR did not 
deployed succeed. Do you know who could help me have   a look at what happend 
while deploy ESR with the scripts?

Thanks,

LiZi

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

Re: [onap-discuss] [Integration] ESR deploy issue in Intel lab with demo script

2017-10-11 Thread PLATANIA, MARCO (MARCO)

Hi LiZi,

ESR didn’t get deployed because your contribution was merged after ONAP was 
build. I fixed this manually in the ONAP instance in the Integration-SB01 lab. 
The containers are now running.

Marco

From: "li.z...@zte.com.cn" <li.z...@zte.com.cn>
Date: Wednesday, October 11, 2017 at 10:03 PM
To: "kang...@huawei.com" <kang...@huawei.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, "PLATANIA, 
MARCO (MARCO)" <plata...@research.att.com>
Subject: [Integration] ESR deploy issue in Intel lab with demo script

Hi Kang,

I add the script in demo repo, and hope it could deploy esr-server and esr-gui 
in openo vm in Intel lab automatically. But it seems that the ESR did not 
deployed succeed. Do you know who could help me have a look at what happend 
while deploy ESR with the scripts?

Thanks,

LiZi

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

Re: [onap-discuss] Dev testing and Integration testing in Windriver lab

2017-10-05 Thread PLATANIA, MARCO (MARCO)

Hi Helen,

I get this. Manoop and team are here in Bedminster, I can help.


Manoop,

I’ll touch base with you as soon as I can.

Marco

From: Yunxia Chen <helen.c...@huawei.com>
Date: Thursday, October 5, 2017 at 2:15 PM
To: "TALASILA, MANOOP (MANOOP)" <talas...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, Kranthi Guttikonda 
<kranthi.guttiko...@b-yond.com>, "Yang Xu (Yang, Fixed Network)" 
<yang@huawei.com>
Cc: "LOTT, CHRISTOPHER M (CHRISTOPHER)" <cl...@research.att.com>, "PLATANIA, 
MARCO (MARCO)" <plata...@research.att.com>
Subject: Re: Dev testing and Integration testing in Windriver lab

Hi, Marco, Yang & Kang,
Could any of you help them for your earliest convenience? (You are all at EST). 
If Portal team could test those part, it could help our next test as well.
Regards,

Helen Chen

From: "TALASILA, MANOOP (MANOOP)" <talas...@research.att.com>
Date: Thursday, October 5, 2017 at 11:07 AM
To: Helen Chen 00725961 <helen.c...@huawei.com>, onap-discuss 
<onap-discuss@lists.onap.org>, Kranthi Guttikonda 
<kranthi.guttiko...@b-yond.com>, "Yang Xu (Yang, Fixed Network)" 
<yang@huawei.com>
Cc: "LOTT, CHRISTOPHER M (CHRISTOPHER)" <cl...@research.att.com>, "PLATANIA, 
MARCO (MARCO)" <plata...@research.att.com>
Subject: Re: Dev testing and Integration testing in Windriver lab

Thanks for the quick reply. All our team is in EST timezone.

Our preferred time is 2 – 4PM EST timeframe, please see if you have anyone that 
can help around that time. If not, please let me know, we can work out some 
best time.

Manoop

From: Yunxia Chen <helen.c...@huawei.com>
Date: Thursday, October 5, 2017 at 1:30 PM
To: "TALASILA, MANOOP (MANOOP)" <talas...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, Kranthi Guttikonda 
<kranthi.guttiko...@b-yond.com>, "Yang Xu (Yang, Fixed Network)" 
<yang@huawei.com>
Cc: "Marco Platania (Confluence)" <nore...@onap.org>, "LOTT, CHRISTOPHER M 
(CHRISTOPHER)" <cl...@research.att.com>
Subject: Re: Dev testing and Integration testing in Windriver lab

Hi, Manoop,
Please see comments inline.

Regards,

Helen Chen

From: "TALASILA, MANOOP (MANOOP)" <talas...@research.att.com>
Date: Thursday, October 5, 2017 at 8:30 AM
To: Helen Chen 00725961 <helen.c...@huawei.com>, onap-discuss 
<onap-discuss@lists.onap.org>
Cc: "Marco Platania (Confluence)" <nore...@onap.org>, "LOTT, CHRISTOPHER M 
(CHRISTOPHER)" <cl...@research.att.com>
Subject: Dev testing and Integration testing in Windriver lab

Hi Helen,

The Portal team have few questions about windriver lab usage. Please see, if 
your team can help us answer them.

The Portal team got access to windriver lab, but we were not completely sure 
about the process or things that we can do and things that we should not be 
doing in the windriver lab environment. Please refer us to the right wiki 
sources, if this is already documented.

Here is what we are looking for:

1.  Regarding Developer testing: After accessing windriver lab, we see that 
we can create our own VM and use it to deploy our project’s docker images to 
perform dev testing. Is that OK? Do we need to coordinate with anyone before 
creating VMs?
[HELEN] Yes, you could do it yourself. No, you don’t need to. However, we 
recommend that you leverage the whole instance from Integration space, you 
could see it as well in your projects list. Please contact us if you need any 
help from us, the more testing, the better.

2.  Regarding Integration testing: Are the Portal Docker artifacts deployed 
in the integration environment along with entire ONAP components, by anyone? If 
so, how can we access and test in that environment? so that we can verify if 
Policy, SDC, VID, CLI etc.. applications are accessible from the Portal 
platform.

[HELEN] Marco, Kranthi and Yang jointly own that. It is easier to reschedule a 
quick meeting with them. What’s your preferred time? We haven’t tested Policy, 
CLI yet, but I know we will get some issues. If you could test it before hand, 
that would be very helpful for us.

Please forgive, if some of these topics are already discussed and if we missed 
them in the emails. So far, we were using the Rackspace env for above testing, 
but now we are ready to try in the windriver lab env.

Thanks in advance for your help.

Regards
Manoop


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

Re: [onap-discuss] ONAP 1.1 flavor_xxlarge?

2017-10-05 Thread PLATANIA, MARCO (MARCO)

Michael and Michael,

Not sure I fully understand the original question, however, the DCAE GEN 2 VM 
in the Heat stack is Ubuntu 16.04. It runs a single docker container that is 
meant to spin up the entire DCAE platform via Cloudify.

DCAE GEN 2 supports Centos 7. The Cloudify container uses the Centos image name 
to create VMs for DCAE. Being containerized, the Cloudify code can run on any 
OS, so we picked Ubuntu to be consistent with the other VMs.

Marco

From:  on behalf of Michael O'Brien 

Date: Thursday, October 5, 2017 at 9:35 AM
To: Michael Ryan , onap-discuss 

Subject: Re: [onap-discuss] ONAP 1.1 flavor_xxlarge?

Michael,
Good questions.  The DCAEGEN2 and Integration (heat work) teams should 
verify this - I currently use OOM/Kubernetes to deploy ONAP, I also deploy on 
Rackspace as a secondary Openstack reference.
Short answers: use 32g vm, and yes Centos is used by DCAE cloudify and other 
new components.

Long--
For your xxLarge flavor question – using Rackspace and AWS EC2 flavors as a 
reference - 
https://aws.amazon.com/ec2/instance-types/
 an “xx” or 2x” instance for general purpose (non mem/storage/compute 
optimized) – usually means 32g ram
If you also correlate the existing AAI1 VM which is 1x or xlarge at 16g – 
then 32g is the standard “xx”
I asked about this in the DCAE meet this morning about 
(onap_openstack_float.yaml)– there is no previous use of xx in DCAEGEN1 (use 
onap_rackspace.yaml as dcae1 reference)– they will get back to use – but I 
would go with 32g – remember this is a runtime requirement (as in high 
throughput production ready) – for development with a single use case you 
should be OK with 16g – as a lot of the 32g VM will be unused.

I would recommend
| memory1-30  | 30 GB Memory v1   | 30720 | 0   
 | 0 |  | 4 | 1250.0  | N/A   |


 For the 2nd question on VM OS’s – Traditionally we ran pure Ubuntu16/14, OOM 
recommendation is 16.04, in 1.1/R1/Amsterdam we run a mix of apt/yum OSs.  I 
understand so far that the cloudify image requires CENTOS in R1.
My understanding is that the DCAEGEN1 controller is replaced by Cloudify – 
which requires Centos.
A quick search of the code in IntelliJ shows centos 7 references in DCAE CDAP 
cluster, ccsdk, vnfsdk, vfc/nfvo , ci-management, vvp/devkitdocker images

We need to update the R1 deployment diagram at 
https://wiki.onap.org/display/DW/Overall+Deployment+Architecture#OverallDeploymentArchitecture-Version1.1.0/R1

Thank you
/michael

From: Michael Ryan
Sent: Wednesday, October 4, 2017 22:15
To: Michael O'Brien 
Subject: RE: ONAP 1.1 flavor_xxlarge?

Hi Again

The Gen2 DCAE controller in the heat template specifies the Ubuntu 1604 image 
for its server, however there are configuration references to the 
centos_7_image parameter. Do you know how this image is used by the DCAE 
controller?

  dcae_c_vm:
type: OS::Nova::Server
properties:
  image: { get_param: ubuntu_1604_image }
…

  user_data:
str_replace:
  params:
…
__centos_7_image__: { get_param: centos_7_image }

…

  template: |

…
echo "__centos_7_image__" > /opt/config/centos_7_image.txt

Thanks
Michael

From: Michael Ryan
Sent: Wednesday, October 04, 2017 10:06 PM
To: Michael O'Brien >
Subject: ONAP 1.1 flavor_xxlarge?

Hi Michael

In the latest ONAP 1.1 heat template there are new requirements for openo and 
2nd gen DCAE controller.

For openo, the template calls for flavor_xxlarge. Which flavor do you recommend 
I map this parameter to? Here is a list of flavors in RS:

root@server-cli:~# nova flavor-list
+-+---+---+--+---+--+---+-+---+
| ID  | Name  | Memory_MB | 
Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+-+---+---+--+---+--+---+-+---+
| 2   | 512MB Standard Instance   | 512   | 20  
 | 0 | 512  | 1 | 80.0|

Re: [onap-discuss] [integration] Integration testing results for 10/3/2017

2017-10-04 Thread PLATANIA, MARCO (MARCO)

Hi Ofir,

Do you know why the deploy button in the VID portal is greyed out? Is there 
some information missing in VID?

We are in the integration zoom room right now, in case you can join: 
https://zoom.us/j/44

Thanks,
Marco


From:  on behalf of Kranthi Guttikonda 

Date: Wednesday, October 4, 2017 at 7:49 AM
To: "SONSINO, OFIR" , Yunxia Chen , 
onap-discuss , "HEMLI, AMICHAI" 

Subject: Re: [onap-discuss] [integration] Integration testing results for 
10/3/2017

Thanks, Ofir. Now able to see the SDC service model in VID but the deploy 
button is grayed out. Attached the screenshot.

~ Kranthi

From:  on behalf of "Sonsino, Ofir" 

Date: Wednesday, October 4, 2017 at 6:19 AM
To: Yunxia Chen , onap-discuss 
, "Hemli, Amichai" 
Subject: Re: [onap-discuss] [integration] Integration testing results for 
10/3/2017

Hi Helen,

I’ve just delivered a fix for VID-74.

Thanks,
Ofir

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Wednesday, October 04, 2017 2:25 AM
To: onap-discuss ; Sonsino, Ofir 
; Hemli, Amichai 
Subject: [integration] Integration testing results for 10/3/2017


1.  Installed the latest docker images from master branch today, (Will do 
daily update in the future starting at 6:00AM EDT)

2.  Passed all existing health check except DCAE (known issue, and have 
solution for it), still miss health check for the following MVP project (VFC, 
MSB, Multi-VIM). And jira tickets (INT-242 and its subtasks) have been created. 
Thanks for the help from SO, DCAE and A team!

3.  Finished onboarding vFW testing.

4.  Tried to instantiate the service today, not done.


Identified the following issues:

1.  
https://jira.onap.org/browse/AAI-411:
 the dependency between two AAI vms cause imtimiite issues.

2.  
https://jira.onap.org/browse/VID-74:
 this is a block issue for Integration team tomorrow’s testing.  (Amichai Hemli 
/ Ofir Sonsino)

Regards,
Helen Chen

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

[onap-discuss] [installation] Docker image name and version number

2017-10-02 Thread PLATANIA, MARCO (MARCO)

Hello ONAP Team,

Per the Independent Versioning and Release Process, we’re asking individual 
project teams to document the “right version of docker image to use” for each 
of their respective docker images in the Docker Version Manifest CSV here: 
https://gerrit.onap.org/r/gitweb?p=integration.git;a=blob;f=version-manifest/src/main/resources/docker-manifest.csv;h=dba9132913e1d6b9fd88dae0738c4eae9f1c5849;hb=refs/heads/master

An example of the Manifest file is the following:

onap/policy/policy-nexus,1.1-STAGING-latest
onap/policy/policy-drools,1.1-STAGING-latest
onap/policy/policy-pe,1.1-STAGING-latest
…

The heat template used for ONAP deployment will pick up the right docker image 
versions from that same manifest. As such, please keep the manifest updated 
AND/OR let me (plata...@research.att.com) and 
Gary Wu (gary.i...@huawei.com) know about changes.

Integration team will kick off testing very soon. This is the list of docker 
image tags per component, based on what your team has used so far:

  aai_docker: 1.1-STAGING-latest
  appc_docker: 1.1-STAGING-latest
  so_docker: 1.1-STAGING-latest
  mr_docker: 1.1-STAGING-latest
  dcae_docker: 1.1-latest
  policy_docker: 1.1-STAGING-latest
  portal_docker: 1.3-STAGING-latest
  robot_docker: 1.1-STAGING-latest
  sdc_docker: 1.1-STAGING-latest
  sdnc_docker: 1.2-STAGING-latest
  vid_docker: 1.1-STAGING-latest
  clamp_docker: 1.1-STAGING-latest
  msb_docker: latest
  mvim_docker: latest
  vfc_docker: latest
  uui_docker: latest
  dgbuilder_docker: 0.1-STAGING-latest
  cli_docker: 1.1-STAGING-latest

The integration team will use these tags to build the first ONAP instance. 
Please let us know of any change.

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

Re: [onap-discuss] Authentication error

2017-10-02 Thread PLATANIA, MARCO (MARCO)

Hi Arul,

I’m aware of some issue when downloading SDNC via nexus3.onap.org:10003. Could 
you change 10003 to 10001 and try again?

Marco

From:  on behalf of "NAMBI, ARUL" 

Date: Monday, October 2, 2017 at 10:07 AM
To: "ayush.ga...@wipro.com" , "onap-s...@lists.onap.org" 
, "onap-discuss@lists.onap.org" 

Subject: Re: [onap-discuss] Authentication error

Hi Ayush,
What is the nexus docker credentials that you are using?
Regards
Arul

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ayush.ga...@wipro.com
Sent: Monday, October 2, 2017 4:13 AM
To: onap-s...@lists.onap.org; onap-discuss@lists.onap.org
Subject: [onap-discuss] Authentication error

Hi,

I am manually setting up the sdnc when I ran

./sdnc_vm_init.sh all the docker images were pulled but at docker-compose up-d

I got the authentication error.

Following is the error log

Already up-to-date.

Login Succeeded

1.2-STAGING-latest: Pulling from onap/sdnc-image

Digest: sha256:a6a7df7d42b5eb27bb586884e9b3e83c681895643cdde546a1eae0236806afc9

Status: Image is up to date for 
nexus3.onap.org:10001/onap/sdnc-image:1.2-STAGING-latest

1.2-STAGING-latest: Pulling from onap/admportal-sdnc-image

Digest: sha256:1118f3439fdd451eceadae97aaddd8d31b8459d6e165e6909d359d2683aaff87

Status: Image is up to date for 
nexus3.onap.org:10001/onap/admportal-sdnc-image:1.2-STAGING-latest

0.1-STAGING-latest: Pulling from onap/ccsdk-dgbuilder-image

Digest: sha256:dd9af38b03923fed45794ac5dc7886f988d8cc7b5bf5faa36665770e595b08ab

Status: Image is up to date for 
nexus3.onap.org:10001/onap/ccsdk-dgbuilder-image:0.1-STAGING-latest

Pulling sdnc (nexus3.onap.org:10003/onap/sdnc-image:latest)...

Pulling repository nexus3.onap.org:10003/onap/sdnc-image

ERROR: unauthorized: authentication required

Where is the error can anybody point out. I am not behind any proxy.

Thanks

Ayush Garg
The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. WARNING: Computer viruses can be transmitted via email. The 
recipient should check this email and any attachments for the presence of 
viruses. The company accepts no liability for any damage caused by any virus 
transmitted by this email. 
www.wipro.com
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit 
http://www.symanteccloud.com
__
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] INT-235: Rackspace 20170928 HEAT deployment fails on nexus3:10003 authentication failure on several VM's during docker image pulls in cloud init

2017-09-28 Thread PLATANIA, MARCO (MARCO)

Hi Michael,

The init scripts are set to use port 10001, unless some team is using custom 
scripts that point to 10003.

Marco




On Thu, Sep 28, 2017 at 6:50 PM -0400, "Michael O'Brien" 
> wrote:

Team,
   Was running a refreshed Rackspace as a verification of issues in mso, policy 
etc…as part of ongoing determination if ONAP 1.1 is sane – until CI tagging of 
good builds is in.
   Rackspace and likely openstack deployment is currently having nexus3 auth 
issues affecting multiple VM’s (SDNC, DCAE,….), for example robot,clamp are 
fine because they just use nexus3:10001.
   I understand there may be workarounds in pre-authenticating docker against 
the repo – but this should be added to the deployment scripts directly as 
currently the HEAT deployments are in regression.

   The issue is during the *_init.sh script specifically for port 10003 (note: 
10001 is OK)

https://jira.onap.org/browse/INT-235


root@vm1-sdnc:/var/log# cat cloud-init-output.log

OK

Status: Downloaded newer image for 
nexus3.onap.org:10001/onap/admportal-sdnc-image:1.2-STAGING-latest

0.1-STAGING-latest: Pulling from onap/ccsdk-dgbuilder-image

50513f4bae65: Already exists



BUSTED

Status: Downloaded newer image for mysql/mysql-server:5.6

Pulling sdnc (nexus3.onap.org:10003/onap/sdnc-image:latest)...

Pulling repository nexus3.onap.org:10003/onap/sdnc-image

unauthorized: authentication required

/michael


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

[onap-discuss] meeting recordings

2017-09-26 Thread PLATANIA, MARCO (MARCO)

Hello Kenny,

Are the recordings of morning meetings available for those that couldn’t attend 
in person?

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

Re: [onap-discuss] Service registration with MSB //Re: [integration] ONAP installation via Heat

2017-09-20 Thread PLATANIA, MARCO (MARCO)

Hi Huabing,

Your assumption is correct. How do you want us to pass these variables to the 
container? As part of the docker run instruction?

Also, which container should have access to them?

Thanks,
Marco




On Wed, Sep 20, 2017 at 8:57 PM -0400, "zhao.huab...@zte.com.cn" 
<zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>> wrote:


Hi Marco,


So I assume these environment variables can be accessed in the MSB VM?


That should work.


Thanks,

Huabing


Original Mail
Sender:  <plata...@research.att.com>;
To: zhaohuabing10201488; <helen.c...@huawei.com>;
CC:  <onap-discuss@lists.onap.org>;
Date: 2017/09/20 21:14
Subject: Re: Service registration with MSB //Re: [onap-discuss] [integration] 
ONAP installation via Heat

Hi Huabing,

Yes, that’s possible. We’ll create a file with all the components and their IP 
addresses. I was thinking about something like this:

export AAI_IP_ADDRESS=10.0.1.1
export DCAE_IP_ADDRESS=10.0.4.1
export POLICY_IP_ADDRESS=10.0.7.1
etc.

What do you think?

Thanks,
Marco

From: "zhao.huab...@zte.com.cn" <zhao.huab...@zte.com.cn>
Date: Wednesday, September 20, 2017 at 4:43 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"helen.c...@huawei.com" <helen.c...@huawei.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Service registration with MSB //Re: [onap-discuss] [integration] ONAP 
installation via Heat


Hi Marco,



As we discussed in the meeting, MSB needs to know the VM IP addresses of all 
the onap components so MSB can register the services for them.

Can we pass that information to MSB VM as environment variables?



@Helen,

According to what I heard in this meeting, VFC, Multi-VIM, MSB, UUI will be 
deployed inside one VM? If that's true, MSB will assume these components' IP 
address is the same as MSB itself when registering the  services.



Thanks,

Huabing
Original Mail
Sender:  <helen.c...@huawei.com>;
To:  <plata...@research.att.com>; <onap-discuss@lists.onap.org>;
Date: 2017/09/20 07:24
Subject: Re: [onap-discuss] [integration] ONAP installation via Heat


Did. :)

Regards,

Helen Chen

From: <onap-discuss-boun...@lists.onap.org> on behalf of "PLATANIA, MARCO 
(MARCO)" <plata...@research.att.com>
Date: Tuesday, September 19, 2017 at 3:21 PM
To: onap-discuss <onap-discuss@lists.onap.org>
Subject: [onap-discuss] [integration] ONAP installation via Heat

All,

To support ONAP teams whose components aren’t in Heat yet, I created a wiki 
page that explains how to add new components to the Heat template and  what 
ONAP teams should do to help us during this process: 
https://wiki.onap.org/display/DW/How+to+add+a+new+ONAP+component+to+Heat<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_How-2Bto-2Badd-2Ba-2Bnew-2BONAP-2Bcomponent-2Bto-2BHeat=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=iMoFdkTRdWMvIGzYyH47YNZGFwEw5Uvy54aHZTNRRC0=ag46XEF7tegu9d8k0jMZDfQnCoNC7fVvxHRjGBjv0WM=>

I know Helen will schedule a meeting with interested teams soon.

Thanks,
Marco






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

[onap-discuss] [integration] ONAP installation via Heat - status update

2017-09-20 Thread PLATANIA, MARCO (MARCO)

ONAP Team,

This is a status update about adding MSB, VNF-SDK, Multi-VIM, UUI, and VF-C to
the Heat template for ONAP installation.

In the Heat template, I created a new VM object that contains install scripts
and configuration data to run the docker containers. I tested it in a private
OpenStack lab. Some containers are up, but there is still work to do. Please
see below.

MSB

· What is working

oThe msb_init_script.sh that Huabing provided works (the three MSB
containers spin up)

oThe config file with IP addresses is ready (/opt/config/onap_ips.txt)

· TODO

oHuabing, please let me know how we can pass these IPs to MSB. Is it OK to
pass them in the docker run command, e.g.

§ docker run … -e AAI_IP=$AAI_IP_ADDR –e APPC_IP=$APPC_IP_ADDR etc.

oIf so, which container should receive these values (msb_consul,
msb_discovery, or msb_apigateway)?

VNFSDK

· What is working

oThe two containers are up

· TODO

oNothing for the moment

Multi-VIM

* What is working
* The two containers are up
* TODO
* Nothing for the moment

UUI

· What is working

oNo instruction provided yet

· TODO

oI created a skeleton of the uui_vm_init.sh script for you. Please fill it
up with docker pull and docker run instructions. I cannot find your containers
in Nexus3. Please help!

VF-C

* What is working
* No instruction provided yet
* TODO
* I created a skeleton of the vfc_vm_init.sh script for you. Please fill
it up with docker run instructions. I already put instructions to pull the
containers. Please help us complete the script.

UUI and VF-C teams, uui_vm_init.sh and vfc_vm_init.sh skeletons are in Gerrit:
https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=boot;h=a8ec8377dec772334915d7ad3c79c9195e983d78;hb=refs/heads/master

Tomorrow (EST time) I will set up a VM in the developer lab and give access to
MSB, VNFSDK, Multi-VIM, UUI, and VF-C teams to check whether their containers
are running correctly.

Thanks,
Marco

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

[onap-discuss] [integration] ONAP installation via Heat

2017-09-19 Thread PLATANIA, MARCO (MARCO)

All,

To support ONAP teams whose components aren’t in Heat yet, I created a wiki 
page that explains how to add new components to the Heat template and what ONAP 
teams should do to help us during this process: 
https://wiki.onap.org/display/DW/How+to+add+a+new+ONAP+component+to+Heat

I know Helen will schedule a meeting with interested teams soon.

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

[onap-discuss] [integration] ONAP installation via Heat

2017-09-19 Thread PLATANIA, MARCO (MARCO)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="PLATANIA, MARCO  (MARCO)":MAILTO:plata...@research.att.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=Mike Ellio
 tt:MAILTO:mike.elli...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Yunxia Che
 n:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang Xu (Y
 ang, Fixed Network)":MAILTO:yang@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="THORPE, HE
 NRY E":MAILTO:ht1...@att.com
DESCRIPTION;LANGUAGE=en-US:When: Tuesday\, September 19\, 2017 3:00 PM-4:00
  PM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://zoom.us/j/4466
 66\n\n*~*~*~*~*~*~*~*~*~*\n\nApologies for the sudden change\, I need 
 to move this meeting to 3PM due to a conflict that just came up.\n\nThanks
 \,\nMarco\n\n---\n\nONAP Team\,\n\nThe integration team is sch
 eduling this meeting to discuss the details of ONAP installation via Heat\
 , especially for those components that are currently not in Heat.\n\nPleas
 e join if you can to discuss how we can work together and move forward.\n\
 nThanks\,\nMarco\n\n\nJoin from PC\, Mac\, Linux\, iOS or Android: https:/
 /zoom.us/j/44<https://urldefense.proofpoint.com/v2/url?u=https-3A_
 _www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fj-252F44
 -26sa-3DD-26usd-3D2-26usg-3DAFQjCNGOukyk-2DyviNF7xE6h-2DW-5Fr5G1RgPA=DwM
 FoQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0
 =U2a6dCV2iyenA80PqyBXaYNu3nAIx6NImGJN7RboRmE=6vUAt4ekaqLmLhgAGdnGBAOka
 3SphxHnhkJWS5wfrIw=>\nOr iPhone one-tap (US Toll): +16465588656\,448
 888# or +14086380968\,44#\nOr Telephone:\nDial: +1 646 558 8656 (U
 S Toll) or +1 408 638 0968 (US Toll)\nMeeting ID: 44  8\nInternati
 onal numbers available: https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfP
 HKBvf6Vslgcsn86<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.g
 oogle.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fzoomconference-253Fm-2
 53DCqsAwHx4CSyRanCfPHKBvf6Vslgcsn86-26sa-3DD-26usd-3D2-26usg-3DAFQjCNHmeO6
 5V-5FncgXTJyNNL6g4uKzSNyg=DwMFoQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0
 gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=U2a6dCV2iyenA80PqyBXaYNu3nAIx6NImGJN7Rbo
 RmE=Rd0Fiax8E2XUBYciL45mI5c23nxGTlAFd9U_MvgCkSo=>\n\n
SUMMARY;LANGUAGE=en-US:[integration] ONAP installation via Heat
DTSTART;TZID=Eastern Standard Time:20170919T15
DTEND;TZID=Eastern Standard Time:20170919T16
UID:861FF417-81FD-4EAA-8AD3-6DF4EBADDA77
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170919T161825Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://zoom.us/j/44
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:2115607733
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:TRUE
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] [integration] ONAP installation via Heat

2017-09-19 Thread PLATANIA, MARCO (MARCO)

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="PLATANIA, MARCO  (MARCO)":MAILTO:plata...@research.att.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=Mike Ellio
 tt:MAILTO:mike.elli...@amdocs.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Yunxia Che
 n:MAILTO:helen.c...@huawei.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Yang Xu (Y
 ang, Fixed Network)":MAILTO:yang@huawei.com
DESCRIPTION;LANGUAGE=en-US:When: Tuesday\, September 19\, 2017 2:00 PM-3:00
  PM. (UTC-05:00) Eastern Time (US & Canada)\nWhere: https://zoom.us/j/4466
 66\n\n*~*~*~*~*~*~*~*~*~*\n\nONAP Team\,\n\n\n\nThe integration team i
 s scheduling this meeting to discuss the details of ONAP installation via 
 Heat\, especially for those components that are currently not in Heat.\n\n
 \n\nPlease join if you can to discuss how we can work together and move fo
 rward.\n\n\n\nThanks\,\n\nMarco\n\n\n\n\n\nJoin from PC\, Mac\, Linux\, iO
 S or Android: https://zoom.us/j/44<https://urldefense.proofpoint.c
 om/v2/url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us
 -252Fj-252F44-26sa-3DD-26usd-3D2-26usg-3DAFQjCNGOukyk-2DyviNF7xE6h
 -2DW-5Fr5G1RgPA=DwMFoQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8e
 C3w16GC3sKgWIcs4iIee0=U2a6dCV2iyenA80PqyBXaYNu3nAIx6NImGJN7RboRmE=6vUA
 t4ekaqLmLhgAGdnGBAOka3SphxHnhkJWS5wfrIw=>\nOr iPhone one-tap (US Toll): 
 +16465588656\,44# or +14086380968\,44#\nOr Telephone:\nDia
 l: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)\nMeeting ID: 44 
  8\nInternational numbers available: https://zoom.us/zoomconferenc
 e?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86<https://urldefense.proofpoint.com/v2/
 url?u=https-3A__www.google.com_url-3Fq-3Dhttps-253A-252F-252Fzoom.us-252Fz
 oomconference-253Fm-253DCqsAwHx4CSyRanCfPHKBvf6Vslgcsn86-26sa-3DD-26usd-3D
 2-26usg-3DAFQjCNHmeO65V-5FncgXTJyNNL6g4uKzSNyg=DwMFoQ=LFYZ-o9_HUMeMTSQ
 icvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=U2a6dCV2iyenA80PqyB
 XaYNu3nAIx6NImGJN7RboRmE=Rd0Fiax8E2XUBYciL45mI5c23nxGTlAFd9U_MvgCkSo=>
 \n\n\n
SUMMARY;LANGUAGE=en-US:[integration] ONAP installation via Heat
DTSTART;TZID=Eastern Standard Time:20170919T14
DTEND;TZID=Eastern Standard Time:20170919T15
UID:861FF417-81FD-4EAA-8AD3-6DF4EBADDA77
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170919T161025Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://zoom.us/j/44
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:2115607733
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:TRUE
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

Re: [onap-discuss] [integration] vCPE workflow discussions

2017-09-14 Thread PLATANIA, MARCO (MARCO)

Brian,

When you say “I put the networks (CPE_PUBLIC and CPE_SIGNAL) into the same 
service with the VNF”, do you mean into the same Heat template? Or did you 
create a new service that uses the VNF component Heat templates plus an 
existing network service?

Thanks,
Marco

From: "FREEMAN, BRIAN D" <bf1...@att.com>
Date: Wednesday, September 13, 2017 at 3:35 PM
To: Kang Xi <kang...@huawei.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>, "LEFEVRE, CATHERINE" <cl6...@intl.att.com>
Cc: "KLUGER, YOAV" <yoav.klu...@amdocs.com>, "DAUGHERTY, ROBERT E" 
<rd4...@att.com>, "BULLARD, GIL" <wb5...@att.com>, "CHOMA, JOHN S" 
<jc1...@att.com>, "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"MARTELLA, ARTHUR W (ARTHUR)" <amart...@research.att.com>, "ZINNIKAS, MICHAEL 
J" <mz2...@att.com>, "SHAH, SARYU D" <ss3...@att.com>, "BOSLET, CORY" 
<cb6...@att.com>, Seshu m <seshu.kuma...@huawei.com>, 
"'simer.si...@us.fujitsu.com'" <simer.si...@us.fujitsu.com>, "'Gadiyar, 
Rajesh'" <rajesh.gadi...@intel.com>, 'Geora Barsky' <geo...@amdocs.com>, 'Karin 
Arnold' <karin.arn...@de.ibm.com>, "SILVERTHORN, DANIEL" 
<daniel.silverth...@amdocs.com>, "'Alex Daltrini (adaltrin)'" 
<adalt...@cisco.com>, "Casem Majd (Cas Majd)" <cas.m...@huawei.com>, "ROSE, 
DANIEL V" <dr6...@att.com>, "GUPTA, ALOK" <ag1...@att.com>, "HAHN III, JIM" 
<jh7...@att.com>, "Vul, Alex" <alex@intel.com>, Xinhui Li 
<lxin...@vmware.com>, Jaco Fourie <jaco.fou...@ericsson.com>, "Eli Williams 
(eliwill)" <eliw...@cisco.com>, "Pujar, Rashmi" <rashmi.pu...@bell.ca>, Tomer 
Oster <tomer.os...@amdocs.com>
Subject: RE: [integration] vCPE workflow discussions

Just a quick update.

I put the networks (CPE_PUBLIC and CPE_SIGNAL)  into the same service with the 
VNF and distributed via SDN.

On VID , after service instantiate there were appropriately 2 buttons . One for 
“Add Network” (drop downs for CPE_PUBLIC and CPE_SIGNAL) and an “Add VN”F 
Module. This would be the reminder to create network before VF since you cant 
add a VF until the Add VNF is done. Again VNF-API was triggered on Add Network 
(applied integration work around  for the mso-sdnc-properties to point sdncurl6 
for VNF-API)  but didnt succeed (actually due to a problem on SDNC with 1.1.2 
vs 1.1.2-SNAPSHOT dependencies).

Brian




-Original Appointment-
From: Kang Xi [mailto:kang...@huawei.com]
Sent: Tuesday, September 12, 2017 8:20 PM
To: Kang Xi; onap-discuss@lists.onap.org; LEFEVRE, CATHERINE
Cc: KLUGER, YOAV; DAUGHERTY, ROBERT E; BULLARD, GIL; CHOMA, JOHN S; FREEMAN, 
BRIAN D; PLATANIA, MARCO; MARTELLA, ARTHUR; ZINNIKAS, MICHAEL J; SHAH, SARYU D; 
BOSLET, CORY; Seshu m; 'simer.si...@us.fujitsu.com'; 'Gadiyar, Rajesh'; 'Geora 
Barsky'; 'Karin Arnold'; SILVERTHORN, DANIEL; 'Alex Daltrini (adaltrin)'; Casem 
Majd (Cas Majd); ROSE, DANIEL V; GUPTA, ALOK; HAHN III, JIM; Vul, Alex; Xinhui 
Li; Jaco Fourie; Eli Williams (eliwill); Pujar, Rashmi; Tomer Oster
Subject: [integration] vCPE workflow discussions
When: Wednesday, September 13, 2017 11:00 AM-12:00 PM (UTC-05:00) Eastern Time 
(US & Canada).
Where: https://zoom.us/j/44



· Generic workflows:
· Update on code contribution to the community (Arthur)
· Test plan and who will be leading this
· Custom workflows:
· Update on design and test (Saryu)
· Training demo/doc (Rob)


Kang Xi is inviting you to a scheduled Zoom meeting.

Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/44<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_j_44=DwMFbw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=nixHf0Up2ho5-cdwgpv6r-gycSlul7vjppzvBgMB-yA=KriEdVRnwpWofxyWQDAOHv_H6g9P1QoinzZpWjltD1o=>

Or iPhone one-tap :
US: +14086380968,,44#  or +16468769923,,44#
Or Telephone：
Dial(for higher quality, dial a number based on your current location)：
US: +1 408 638 0968  or +1 646 876 9923  or +1 669 900 6833
Meeting ID: 446 666 
International numbers available: 
https://zoom.us/zoomconference?m=YilmmLfh2QJZSirC9kA-eyHblCgJwR_-<https://urldefense.proofpoint.com/v2/url?u=https-3A__zoom.us_zoomconference-3Fm-3DYilmmLfh2QJZSirC9kA-2DeyHblCgJwR-5F-2D=DwMFbw=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=nixHf0Up2ho5-cdwgpv6r-gycSlul7vjppzvBgMB-yA=2LcT3LHbU69OcZGSaDTktX7UopK615NKAgTtVAHPf7U=>


  << File: ATT1.txt >>

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

Re: [onap-discuss] ONAP Deployment Strategy for R1: OOM vs Heat Template

2017-09-05 Thread PLATANIA, MARCO (MARCO)

Hello Mike,

Thanks for installing OOM and ONAP in the WindRiver lab!

I got access via the link that you sent. How can I see the list of running 
containers? The usual “docker ps” doesn’t seem to work. How can we access 
single containers, e.g. Robot, to run health check? Also, could you please 
explain the content of /etc/hosts? I thought all the containers ran in a single 
VM, but I see different IP addresses.

I can access the portal GUI, but I can’t access SDC: the IP isn’t resolved 
correctly.

Thanks for the support.

Marco

From: Mike Elliott <mike.elli...@amdocs.com>
Date: Tuesday, September 5, 2017 at 4:12 PM
To: Yunxia Chen <helen.c...@huawei.com>
Cc: Gildas Lanilis <gildas.lani...@huawei.com>, "Sauvageau, David 
(david.sauvag...@bell.ca)" <david.sauvag...@bell.ca>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>, Roger Maitland <roger.maitl...@amdocs.com>, Seshu 
m <seshu.kuma...@huawei.com>, "HEMLI, AMICHAI" <ah0...@intl.att.com>, "TIMONEY, 
DAN" <dt5...@att.com>, "KOYA, RAMPRASAD" <rk5...@att.com>, "TALASILA, MANOOP 
(MANOOP)" <talas...@research.att.com>, "yangya...@chinamobile.com" 
<yangya...@chinamobile.com>, Xinhui Li <lxin...@vmware.com>, "DRAGOSH, PAMELA L 
(PAM)" <pdrag...@research.att.com>, "FORSYTH, JAMES" <jf2...@att.com>, 
onap-discuss <onap-discuss@lists.onap.org>, "TIMONEY, DAN" <dt5...@att.com>
Subject: Re: ONAP Deployment Strategy for R1: OOM vs Heat Template

Hi Helen,

There is an OOM deployment now running in the integration lab. It is running on 
2 VMs running in the WindRiver OpenStack Environment. The ‘OOM’ VM is hosting 
Rancher and the ‘ONAP-1’ VM is hosting ONAP, current as of 10:00am EST.

If you have have access to the lab (ie. VPN account), you can login to the VNC 
session using the following URL (credential to login is ‘password’)
http://172.21.5.77:30211/vnc.html?autoconnect=1=0=3<https://urldefense.proofpoint.com/v2/url?u=http-3A__172.21.5.77-3A30211_vnc.html-3Fautoconnect-3D1-26autoscale-3D0-26quality-3D3=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=MHxT3OtzZQc7VUaLM2vaFGP74oAi3BLSOELbh2KhAiQ=P9NvKFkWJR9-pzbllE4Gy4JUQvfOC6yCIlKbharOeLo=>

Note that this is a single instance of ONAP and as such the VNC session would 
be shared if multiple people login at the same time.


Currently running ONAP containers:


Please let me know if you have any questions, comments or concerns,
Mike.


On Sep 1, 2017, at 10:03 AM, Yunxia Chen 
<helen.c...@huawei.com<mailto:helen.c...@huawei.com>> wrote:

We lean to OOM, but need to try it out since we have tried Heat template in the 
Developer Lab.

Regards,

Helen Chen

From: Gildas Lanilis 
<gildas.lani...@huawei.com<mailto:gildas.lani...@huawei.com>>
Date: Friday, September 1, 2017 at 7:00 AM
To: Helen Chen 00725961 <helen.c...@huawei.com<mailto:helen.c...@huawei.com>>, 
"Sauvageau, David (david.sauvag...@bell.ca<mailto:david.sauvag...@bell.ca>)" 
<david.sauvag...@bell.ca<mailto:david.sauvag...@bell.ca>>, "PLATANIA, MARCO 
(MARCO)" <plata...@research.att.com<mailto:plata...@research.att.com>>, Roger 
Maitland <roger.maitl...@amdocs.com<mailto:roger.maitl...@amdocs.com>>, Seshu m 
<seshu.kuma...@huawei.com<mailto:seshu.kuma...@huawei.com>>, 
"ah0...@intl.att.com<mailto:ah0...@intl.att.com>" 
<ah0...@intl.att.com<mailto:ah0...@intl.att.com>>, 
"dtimo...@att.com<mailto:dtimo...@att.com>" 
<dtimo...@att.com<mailto:dtimo...@att.com>>, 
"rk5...@att.com<mailto:rk5...@att.com>" 
<rk5...@att.com<mailto:rk5...@att.com>>, 
"talas...@research.att.com<mailto:talas...@research.att.com>" 
<talas...@research.att.com<mailto:talas...@research.att.com>>, 
"yangya...@chinamobile.com<mailto:yangya...@chinamobile.com>" 
<yangya...@chinamobile.com<mailto:yangya...@chinamobile.com>>, Xinhui Li 
<lxin...@vmware.com<mailto:lxin...@vmware.com>>, 
"pdrag...@research.att.com<mailto:pdrag...@research.att.com>" 
<pdrag...@research.att.com<mailto:pdrag...@research.att.com>>, 
"jf2...@att.com<mailto:jf2...@att.com>" 
<jf2...@att.com<mailto:jf2...@att.com>>, onap-discuss 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: Mike Elliott <mike.elli...@amdocs.com<mailto:mike.elli...@amdocs.com>>, 
"TIMONEY, DAN" <dt5...@att.com<mailto:dt5...@att.com>>
Subject: RE: ONAP Deployment Strategy for R1: OOM vs Heat Template

Hi Helen,

What is the conclusion?
Is Amsterdam Release using OOM or Heat Template?


Thanks,
Gildas
ONAP Release Manager
1 415 238

Re: [onap-discuss] ONAP Deployment Strategy for R1: OOM vs Heat Template

2017-09-01 Thread PLATANIA, MARCO (MARCO)

Is this meeting still happening?

Marco

From: helen.c...@huawei.com
When: 10:00 AM - 11:00 AM September 1, 2017
Subject: ONAP Deployment Strategy for R1: OOM vs Heat Template
Location: https://zoom.us/j/44


When: Friday, September 01, 2017 7:00 AM-8:00 AM. (UTC-08:00) Pacific Time (US 
& Canada)
Where: 
https://zoom.us/j/44

*~*~*~*~*~*~*~*~*~*
Hi, David, Marco and PTLs on this list,

Let’s use this time to decide which way we should go. If necessary, we report 
to TSC for approval.

For people who are not aware of the context, please refer to Marco’s initial 
emails (attached).

For PTLs on this list, from my information (may not up to date), OOM has not 
integrated with your project:
AAI
VID
SO
SDNC
DCAE
Portal
VFC
Multi-VIM
MSBhjn
Policy
CCF

If you or your proxy cannot make this meeting, please go to the following wiki 
page to add comments related to your project and cc us as well before 9/1/2017 
7:00am PDT :
https://wiki.onap.org/display/DW/ONAP+Installation+Strategy+for+Release+A

If you’d like to use OOM, please work with David to give us a solid date for 
when it could be done. Since Integration team is doing daily testing, we need 
to identify one tool to deploy ONAP for R1 before the end of this week.

Thank you,
Helen Chen


ONAP Deployment Strategy for R1: OOM vs Heat Template

(Non LF Zoom Licence)
Join from PC, Mac, Linux, iOS or Android: 
https://zoom.us/j/44
Or iPhone one-tap (US Toll): +16465588656,44# or 
+14086380968,44#
Or Telephone:
Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)
Meeting ID: 44  8
International numbers available: 
https://zoom.us/zoomconference?m=CqsAwHx4CSyRanCfPHKBvf6Vslgcsn86

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

Re: [onap-discuss] [E] vLB/vDNS Queries

2017-08-25 Thread PLATANIA, MARCO (MARCO)

Kumar, Bharath,

VPP is the vLB. VPP has many plugins, so you can configure it to play different 
roles. In the vLB/vDNS use case, we use VPP as packet generator (VM1) and vLB 
(VM2). In the vFW use case, we use it as packet generator (VM1) and vFW (VM2). 
For the vLB scenario, nslookups directed to the vLB are captured by VPP and 
sent over to one of the existing vDNSs.

Regarding the discovery service that vLB and vDNS use, I’m not aware of any VPP 
discovery service, so we implemented our own.

Lately, we found that the vLB use case used in release-1.0.0 didn’t work in 
some OpenStack labs, due to VPP config issues (use cases for release-1.0.0 
supported Rackspace only). We are now using the latest VPP (1707). The vLB use 
case architecture changed a little: while for release-1.0.0 we only had vLB and 
vDNS, the current release adds a packet generator VM as part of the VNF. Please 
use this one because is more stable.

To test it, you can log into the packet generator VM and run nslookups like:

nslookup host1.dnsdemo.onap.org vLB_IP_ADDRESS

The vLB_IP_ADDRESS is the IP address towards the private network that connects 
vLB and packet generator. If you are using the latest template in Gerrit 
(https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/vLB;h=e69c2fadce8452da7840b3177c7e2ad694bf1959;hb=refs/heads/master
 ), that address is set to 192.168.9.111.

Thanks,
Marco

From: "Kumar Skand Priya, Viswanath V" <viswanath.kumarskandpr...@verizon.com>
Date: Friday, August 25, 2017 at 4:27 AM
To: bharath thiruveedula <bharath_...@hotmail.com>
Cc: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, Josef Reisinger 
<josef.reisin...@de.ibm.com>
Subject: Re: [E] [onap-discuss] vLB/vDNS Queries

Hi Marco,

I would like to rephrase one of Bharath’s question :

Assuming vLB and vDNS are in same private network, why do we need VPP in 
middle? Can clients directly contact vLB inorder to reach vDNS, which then gets 
scaled based on policy?

BR,
Viswa

On Friday, August 25, 2017, bharath thiruveedula 
<bharath_...@hotmail.com<mailto:bharath_...@hotmail.com>> wrote:
> Hi Marco,
>
> Marco, thanks a lot for your reply!
>
> 1)   You are right, the vFW/vLB VNFs have multiple vNICs, one of these 
> attached to the public network. We tested them successfully in 3-4 different 
> vanilla OpenStack environments (Liberty and Mitaka versions) plus Rackspace. 
> It may be that your OpenStack configuration doesn’t
>
> allow you to attach vNICs directly to public networks, but this feature can 
> be enabled (although I can’t help here, sorry for that)
>
> Oh, but I think it is not recommended by openstack  to directly attach the 
> interface to external network. I am aware that  using floating-ip is not 
> valid in SDC, so that's why we took this approach. Not sure why SDC team 
> invalidates using floating ip in heat template.
> 2)   The v_lb_init.sh script allows VPP to take over eth0 and eth1 in the 
> vLB VM. This doesn’t mean that you can’t reach the VM. It’s true that PING 
> and SSH don’t work, but VPP will accept nslookup requests on eth0 from an 
> external VM and use eth1 to forward those requests to one or more vDNS. We 
> didn’t test the vLB with floating IPs though. I remember that the 
> configuration currently in place couldn’t work straight away with floating 
> IPs, so for the moment we abandoned that path. As for the vDNS not connected 
> to the vLB, try to see if Java is downloaded and installed correctly, and if 
> dnsmembership.sh and dns_client.sh in vLB and vDNS VMs, respectively, are 
> running. These scripts launch a service that vLB and vDNS use to discover 
> each other via the ONAP OAM network.
>
> Yeah floating IP approach is not working, I have tested vDNS using nslookup 
> directly to DNS IP, it works. Bu
> t through vLB is not redirecting. I will test nslookup from the external VM 
> in the same network of vLB. Can you give information on dnsmembership.sh and 
> dns_client.sh, as why we need discovery here, does VPP take care of that?
> Best Regards
> Bharath T
> 
> From: PLATANIA, MARCO (MARCO) 
> <plata...@research.att.com<mailto:plata...@research.att.com>>
> Sent: Thursday, August 24, 2017 10:03 PM
> To: bharath thiruveedula; 
> onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Josef 
> Reisinger
> Subject: Re: [onap-discuss] vLB/vDNS Queries
>
>
> Bharath,
>
>
>
> 1)   You are right, the vFW/vLB VNFs have multiple vNICs, one of these 
> attached to the public network. We tested them successfully in 3-4 different 
> vanilla OpenStack environments (Liberty and Mitaka versions) plus Rackspace. 
> It may be that your OpenStack

Re: [onap-discuss] vLB/vDNS Queries

2017-08-24 Thread PLATANIA, MARCO (MARCO)

Bharath,


1)   You are right, the vFW/vLB VNFs have multiple vNICs, one of these 
attached to the public network. We tested them successfully in 3-4 different 
vanilla OpenStack environments (Liberty and Mitaka versions) plus Rackspace. It 
may be that your OpenStack configuration doesn’t allow you to attach vNICs 
directly to public networks, but this feature can be enabled (although I can’t 
help here, sorry for that)

2)   The v_lb_init.sh script allows VPP to take over eth0 and eth1 in the 
vLB VM. This doesn’t mean that you can’t reach the VM. It’s true that PING and 
SSH don’t work, but VPP will accept nslookup requests on eth0 from an external 
VM and use eth1 to forward those requests to one or more vDNS. We didn’t test 
the vLB with floating IPs though. I remember that the configuration currently 
in place couldn’t work straight away with floating IPs, so for the moment we 
abandoned that path. As for the vDNS not connected to the vLB, try to see if 
Java is downloaded and installed correctly, and if dnsmembership.sh and 
dns_client.sh in vLB and vDNS VMs, respectively, are running. These scripts 
launch a service that vLB and vDNS use to discover each other via the ONAP OAM 
network.

3)   The vFW/vLB demos work in ONAP release 1.0.0, in Rackspace. The ONAP 
code currently in the master branch is supposed to support vFW/vLB demos in 
vanilla OpenStack, although the code is being tested right now. Some issue is 
preventing the closed loop to work correctly. If you want to test the closed 
loop in OpenStack, you may consider to install ONAP 1.0.0 plus DCAE 1.1.0 and 
MSO 1.1.0 in OpenStack. This will require some manual tinkering to Heat 
templates and environment files. Josef succeeded in this. Here’s a summary of 
his effort

  artifacts_version: 1.1.0-SNAPSHOT
  docker_version: 1.0-STAGING-latest
  gerrit_branch: master
.
.
.
 ###
 # #
 # Parameters used by DCAE #
 # #
 ###
  dcae_base_environment: 1-NIC-FLOATING-IPS
  dcae_zone: ZONE
  dcae_state: STATE
  nexus_repo_root: 
https://nexus.onap.org
  nexus_url_snapshot: 
https://nexus.onap.org/content/repositories/snapshots
  gitlab_branch: master
  dcae_code_version: 1.1.0

and I changed a line in the heat template for the dcae controller vm to use 
docker version 1.1
echo "__docker_version__" > /opt/config/docker_version.txt
echo "1.1-STAGING-latest" > /opt/config/docker_version.txt

Thanks,
Marco

From:  on behalf of bharath thiruveedula 

Date: Thursday, August 24, 2017 at 12:05 PM
To: "onap-discuss@lists.onap.org" , Josef 
Reisinger 
Subject: [onap-discuss] vLB/vDNS Queries


Hi.



I am trying to setup vLB demo using 1.0.0 heat 
template(https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/vLB/base_vlb.yaml;h=c292f2957d97bd7839d7fa7fcf55e04c1e9718ba;hb=refs/heads/release-1.0.0).



But I have few queries/issue with the demo:

1) LB and DNS VMs has one network interface attached to public network, which 
in most of the openstack environments won't assign the IP address. This issue 
also faced in vFW also.



So in this case, I attached to another private network and launched the VMs



2) According to the 
v_lb_init.sh
 script, it brings down both eth0 and eth1 interfaces and attach to them to 
corresponding bridges along with the tap interfaces. In this case, I observed 
it lost the connectivity to those interfaces. So I can't send the DNS queries 
using Loadbalancer public IP(I assigned floating IP). I am not completely aware 
of VPP and

Re: [onap-discuss] Dockers are not present in the VMs

2017-08-23 Thread PLATANIA, MARCO (MARCO)

Hello Parvez,

As I just replied to another email, please use the latest heat templates in 
Gerrit.

You are using an old version, which doesn’t include Gerrit repo 
parametrization, as described here: https://jira.onap.org/browse/UCA-33

Thanks,
Marco


From:  on behalf of Ran Pollak 

Date: Wednesday, August 23, 2017 at 10:25 AM
To: "onap-discuss@lists.onap.org" , Parvez Basha 
Shaik 
Subject: Re: [onap-discuss] Dockers are not present in the VMs

Hi Parvez,

The issue is a missing text file inside /opt/config, the expected text file is 
“remote_repo.txt”, it’s supposed to be generated from the heat, for example 
“echo "__external_dns__" > /opt/config/external_dns.txt”.

For Clarification this is the issue: we need to add a similar line into the 
heat so that the portal_vm_init.sh(in this example we using the portal) will 
not fail.

PSB the reason:

CODE_REPO=$(cat /opt/config/remote_repo.txt)  --> this file is missing so the 
parameter CODE_REPO doesn’t get any value
git clone -b $GERRIT_BRANCH --single-branch $CODE_REPO --> This line fails 
because it is missing COD_REPO

This line is translated to “git clone -b master --single-branch  ” and that’s 
why the git clone is failing.


From: Parvez Basha Shaik
Sent: Wednesday, August 23, 2017 4:36 PM
To: onap-discuss@lists.onap.org
Cc: Manoj Kapre >; Tomer Oster 
>; Jayant Madavi 
>; Netaji Surve 
>; Kaish Alam 
>; Nikita Chouhan 
>; Ran Pollak 
>; Stella Gorenshtein 
>; Tariq Gharra 
>; David Swisa 
>; Borislav Glozman 
>; Eyal Holzman 
>
Subject: Dockers are not present in the VMs
Importance: High

Hi Community,

We were trying to deploy 1.1 community version of ONAP and I see that the 
environment is deployed without any errors and stack was created. But, to our 
surprise I could not see a single docker dropping into the VMs. This is very 
basic issue and we tried to validate the error and it seems like it is not able 
to reach the docker repo from VM through VM_init.sh scripts.
Is it because the repo is not up? Or is it just our teams/network who is facing 
this issue (Amdocs India and Israel) or did we migrate to new repo or is it 
because of the init file permissions?

1.   I have raised a ONAP JIRA bug for the same. 
CIMAN-32
 I found CI project as appropriate place for this to log. Please feel free to 
assign to the right team if its wrongly assigned.
2.

Thanks,
Parvez
Ph: +91 9985300392

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] Issues we found during the Deployment of ONAP 1.1

2017-08-23 Thread PLATANIA, MARCO (MARCO)

Hello Ran,

Please use the latest heat templates in Gerrit.

You are using an old version, which doesn’t include Gerrit repo 
parametrization, as described here: https://jira.onap.org/browse/UCA-33

Thanks,
Marco

From:  on behalf of Ran Pollak 

Date: Wednesday, August 23, 2017 at 10:50 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Issues we found during the Deployment of ONAP 1.1

Hello ONAP Community Members,

PSB the issues we found on ONAP-deployment 1.1, please add info if you also saw 
those issues mention below(also update if there is defect number):

vm1-dcae-controller:
root@vm1-dcae-controller:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory
root@vm1-dcae-controller:/opt# MR_REPO=$(cat /opt/config/mr_repo.txt)
cat: /opt/config/mr_repo.txt: No such file or directory
root@vm1-dcae-controller:/opt#


vm1-portal:
root@vm1-portal:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory


vm1-mso:
root@vm1-mso:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory

vm1-appc:
root@vm1-appc:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory

vm1-sdc:
root@vm1-sdc:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory

vm1-policy:
root@vm1-policy:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory


vm1-message-router:
root@vm1-message-router:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory


vm1-vid:
root@vm1-vid:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory

vm1-robot:
root@vm1-robot:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory


vm1-sdnc:
root@vm1-sdnc:/opt# CODE_REPO=$(cat /opt/config/remote_repo.txt)
cat: /opt/config/remote_repo.txt: No such file or directory

BR,
Ran Pollak

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] [E] Re: Closed Loop Question

2017-08-22 Thread PLATANIA, MARCO (MARCO)

That’s the right assumption. DCAE 1.1.0 works in Vanilla OpenStack but not DCAE 
1.0.0. If you want to try the closed loop, you can install ONAP 1.0.0 with MSO 
and DCAE 1.1.0 (with a bit of manual work on the Heat template). I know 
somebody in the community did it, probably Josef (in CC).

Marco

From: "Kumar Skand Priya, Viswanath V" <viswanath.kumarskandpr...@verizon.com>
Date: Tuesday, August 22, 2017 at 11:29 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>
Cc: "DRAGOSH, PAMELA L (PAM)" <pdrag...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [E] Re: Closed Loop Question

Thanks Marco. We have powered up ONAP ( - dcae ) on Vanila openstack ( after 
bit of a struggle ).

We also learnt that dcae 1.1.0 will work on vanilla openstack. So can we assume 
we cannot demo vLB in 1.0.0 + Vanilla openstack ?

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.verizon.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=2FKsQ3Tf-q5n_AP6ac4LGoV-MIsxEcdvR2yDl8KIOeg=ajGTVouIQY87gsZVYlg4AOQb2OTZBJC2w4zY3ZDRluU=>

Viswanath Kumar Skand Priya
Architect
SDN, Cloud Services & Orchestration

On Tue, Aug 22, 2017 at 8:52 PM, PLATANIA, MARCO (MARCO) 
<plata...@research.att.com<mailto:plata...@research.att.com>> wrote:
Hi Viswa,

Not really. The onboarding process (SDC + demo.sh in the robot VM) populates 
ONAP components with metadata about the VNF that you want to run. Those steps 
are required for the closed loop to work correctly.

Also, regarding the vLB, we are testing it for ONAP 1.1.0 but we still have 
some issue with the DNS scaling scenario. So, for the scaling use case you may 
want to see what we did for ONAP 1.0.0.

Thanks,
Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Kumar Skand Priya, Viswanath V via onap-discuss" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Reply-To: "Kumar Skand Priya, Viswanath V" 
<viswanath.kumarskandpr...@verizon.com<mailto:viswanath.kumarskandpr...@verizon.com>>
Date: Tuesday, August 22, 2017 at 11:03 AM
To: "DRAGOSH, PAMELA L (PAM)" 
<pdrag...@research.att.com<mailto:pdrag...@research.att.com>>

Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [E] Re: Closed Loop Question

Thanks Pam. I shall try vDNS as suggested.

BTW Is there a way we can skip the SDC on-boarding steps and directly start 
with deployment + scaling ??

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.verizon.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=TYE6HdAJosx0j0ckbJqHiItzrnuMkRAUm07SzHz8D2I=LpqXsu4ntmHCIYVij_-YymkSfIcd5cFARh8byEN2GhE=>

Viswanath Kumar Skand Priya
Architect
SDN, Cloud Services & Orchestration

On Tue, Aug 22, 2017 at 8:26 PM, DRAGOSH, PAMELA L (PAM) 
<pdrag...@research.att.com<mailto:pdrag...@research.att.com>> wrote:
Viswa,

The vDNS (also call vLB) use case does VNF scaling. It is very basic. ☺

Regards,

Pam

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Kumar Skand Priya, Viswanath V via onap-discuss" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Reply-To: "Kumar Skand Priya, Viswanath V" 
<viswanath.kumarskandpr...@verizon.com<mailto:viswanath.kumarskandpr...@verizon.com>>
Date: Tuesday, August 22, 2017 at 10:45 AM
To: Josef Reisinger 
<josef.reisin...@de.ibm.com<mailto:josef.reisin...@de.ibm.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: Re: [onap-discuss] [E] Re: Closed Loop Question

Hi Josef,

Thanks for the note. Does this mean that, currently we cannot use ONAP to 
perform scaling / healing of VNFs ?

Could you let me know if there are any other demo available today, which takes 
use through closed loop?

Can the CLAMP project be leveraged to demonstrate closed loop?

PS : Bharath works with me on ONAP exploration!

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.verizon.com=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4=qWoY_xw3Vs-N_sofCThrKlfCYjsUSL8K4gQOA9zK_Ls=_r9QB-B4NklThucc4VpdnK8UStN6nHFgoPD6JgKAioI=>

Viswanath Kumar Skand Priya
Architect
SDN, Clou

Re: [onap-discuss] [E] Re: Closed Loop Question

2017-08-22 Thread PLATANIA, MARCO (MARCO)

Hi Viswa,

Not really. The onboarding process (SDC + demo.sh in the robot VM) populates 
ONAP components with metadata about the VNF that you want to run. Those steps 
are required for the closed loop to work correctly.

Also, regarding the vLB, we are testing it for ONAP 1.1.0 but we still have 
some issue with the DNS scaling scenario. So, for the scaling use case you may 
want to see what we did for ONAP 1.0.0.

Thanks,
Marco

From:  on behalf of "Kumar Skand Priya, 
Viswanath V via onap-discuss" 
Reply-To: "Kumar Skand Priya, Viswanath V" 

Date: Tuesday, August 22, 2017 at 11:03 AM
To: "DRAGOSH, PAMELA L (PAM)" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [E] Re: Closed Loop Question

Thanks Pam. I shall try vDNS as suggested.

BTW Is there a way we can skip the SDC on-boarding steps and directly start 
with deployment + scaling ??

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Architect
SDN, Cloud Services & Orchestration

On Tue, Aug 22, 2017 at 8:26 PM, DRAGOSH, PAMELA L (PAM) 
> wrote:
Viswa,

The vDNS (also call vLB) use case does VNF scaling. It is very basic. ☺

Regards,

Pam

From: 
>
 on behalf of "Kumar Skand Priya, Viswanath V via onap-discuss" 
>
Reply-To: "Kumar Skand Priya, Viswanath V" 
>
Date: Tuesday, August 22, 2017 at 10:45 AM
To: Josef Reisinger 
>
Cc: "onap-discuss@lists.onap.org" 
>
Subject: Re: [onap-discuss] [E] Re: Closed Loop Question

Hi Josef,

Thanks for the note. Does this mean that, currently we cannot use ONAP to 
perform scaling / healing of VNFs ?

Could you let me know if there are any other demo available today, which takes 
use through closed loop?

Can the CLAMP project be leveraged to demonstrate closed loop?

PS : Bharath works with me on ONAP exploration!

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Architect
SDN, Cloud Services & Orchestration

On Tue, Aug 22, 2017 at 2:15 PM, Josef Reisinger 
> wrote:
I run the basic vFW demo right now and this does not include scaling of the 
VMs. It includes changing the package rate of the package generator (keeping it 
constant). To change the packet rate, there is a REST API.
Not sure I got your Q'#2 right, the closes "loop" consists of the vFW as the 
source of measurements, DCAE to process the measurements and CDAP to run an APP 
die determine whether the packet rate it too high, Policy & APPC to close the 
loop (roughly, see more details here: 
https://wiki.onap.org/display/DW/Tutorial%3A+Verifying+and+Observing+a+deployed+Service+Instance)

The vFW VMs have different # of network interfaces, three for the sink & pgn 
nodes, 4 for the firewall node. Running vFW demo on another openstack instance 
can become a bit tricky maybe, I am not sure the the entire comms runs via the 
"public" network. If you run into issues, you should keep that as a probable 
cause of issues in mind.

Mit freundlichen Grüßen / Kind regards
Josef Reisinger

From:bharath thiruveedula 
>
To:Josef Reisinger 
>
Date:22.08.2017 10:23
Subject:Closed Loop Question

Hi Josef,

I think you played well with DCAE part :)

I am currently looking to make closed loop work with vFW. I have few questions 
on this:
1)Can we scale up/down the

Re: [onap-discuss] ONAP installation: Unable to launch Portal

2017-08-08 Thread PLATANIA, MARCO (MARCO)

Subhash, Arvind,

Can you post some Portal logs or give more information about the issue your 
experiencing? Adding Manoop from Portal to the email…

Thanks,
Marco

From:  on behalf of Subhash Kumar Singh 

Date: Tuesday, August 8, 2017 at 4:52 AM
To: "onap-discuss@lists.onap.org" 
Cc: "bharti.kaus...@tcs.com" , Arvind1 Sharma 
, "onap-discuss-requ...@lists.onap.org" 

Subject: Re: [onap-discuss] ONAP installation: Unable to launch Portal

Hello Everyone,

We are also facing similar issue with portal, because ecompdb_portal docker 
instance is exiting with error.
Which I’ve already reported [1].

[1]  
https://lists.onap.org/pipermail/onap-discuss/2017-August/003078.html
--
Regards,
Subhash Kumar Singh

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

***
This e-mail and its attachments contain confidential information from HUAWEI, 
which is intended only for the person  or entity whoseaddress 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, pleasenotify the sender by phone or email immediately and 
delete it!
***

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arvind1 Sharma
Sent: Tuesday, August 08, 2017 11:30 AM
To: onap-discuss@lists.onap.org
Cc: bharti.kaus...@tcs.com; onap-discuss-requ...@lists.onap.org
Subject: [onap-discuss] ONAP installation: Unable to launch Portal

Hi,

I'm trying to install ONAP. While opening the dashboard, I'm getting error 
"Unable to connect". Pls help.

Also, Is it possible to activate a VNF through CLI without portal.


Best Regards
Arvind Kumar Sharma
Tata Consultancy Services
Cell:- +91-99-7170-1428
Mailto: arvind1.sha...@tcs.com
Website: 
http://www.tcs.com

Experience certainty. IT Services
Business Solutions
Consulting


=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [integration][so][sdc] vCPE network-related issues

2017-08-03 Thread PLATANIA, MARCO (MARCO)

All,

This is the list of IP addresses currently used in ONAP for the OAM network.

 oam_network_cidr: 10.0.0.0/8
  aai1_ip_addr: 10.0.1.1
  aai2_ip_addr: 10.0.1.2
  appc_ip_addr: 10.0.2.1
  dcae_ip_addr: 10.0.4.1
  dcae_coll_ip_addr: 10.0.4.102
  dcae_db_ip_addr: 10.0.4.101
  dcae_hdp1_ip_addr: 10.0.4.103
  dcae_hdp2_ip_addr: 10.0.4.104
  dcae_hdp3_ip_addr: 10.0.4.105
  dns_ip_addr: 10.0.100.1
  mso_ip_addr: 10.0.5.1
  mr_ip_addr: 10.0.11.1
  policy_ip_addr: 10.0.6.1
  portal_ip_addr: 10.0.9.1
  robot_ip_addr: 10.0.10.1
  sdc_ip_addr: 10.0.3.1
  sdnc_ip_addr: 10.0.7.1
  vid_ip_addr: 10.0.8.1

These of course can be changed, but many installation are already using the 
10.X addresses. In our private lab we are using 10.0.0.0/16 instead of /8.

Thanks,
Marco

From: kang...@huawei.com
When: 9:00 AM - 10:00 AM August 3, 2017
Subject: [integration][so][sdc] vCPE network-related issues
Location: https://zoom.us/j/44


Hi All,

We will cover all the network-related items for vCPE:
· Network between vBRG and vBNG
· Network between vBNG and vGMUX
· Network between vGMUX and vG
· Network between vG and “public Internet hosting the web server”

Marco and Danny,

Would you please investigate how to create/config the above and lead the 
discussions?

Thanks,
Kang


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

Re: [onap-discuss] [DCAE] DCAE 1.0.0

2017-07-25 Thread PLATANIA, MARCO (MARCO)

Hi Shankar,

Yes, you can modify the heat template to install ONAP seed code release-1.0.0 
with DCAE 1.1.0. We never tested this option, so I don’t know the outcome, but 
it seems that Josef is using this approach.

For what regards the dependency from the underlying platform, Rackspace and 
vanilla OpenStack use different image names, flavors, network IDs, etc. So, the 
configuration used for Rackspace (coded in DCAE) doesn’t work in plain 
OpenStack.

Marco

From: Cipher Cipher <cipher.for.programm...@gmail.com>
Date: Tuesday, July 25, 2017 at 3:28 AM
To: Michael O'Brien <frank.obr...@amdocs.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, "PLATANIA, 
MARCO (MARCO)" <plata...@research.att.com>
Subject: RE: [onap-discuss] [DCAE] DCAE 1.0.0

Hi Michael/Marco,

Thanks for the input. Can you throw some light why DCAE functionality depends 
up on underlying cloud(racks pace or vanilla openstack)? And can we just 
replace DCAE-1.0.0 with the latest and keeping rest of the components as it is? 
Will there be any api endpoint mismatch if we use above approach?

Cheers
Shankar

On 25-Jul-2017 3:55 AM, "Michael O'Brien" 
<frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>> wrote:
Shankar,
   Hi, as Marco mentions in a 1.0.0 ONAP environment DCAE only works in 
Rackspace so far, in 1.1 it works in both.
   We had a similar question on the 18th from Serkant.  I checked the page 
below in anticipation of editing it but I will leave the clause as-is

DCAE-VERSION

1.1.0

Note only 1.1.0 version is working outside of Rackspace


   There is a video of closed-loop (requires DCAE) for 1.0.0 on Rackspace at
https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Installing-2Band-2BRunning-2Bthe-2BONAP-2BDemos=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=0c94DuMw40KaHf-_5LU5QAqvGkV0vsBrN1yvOHoUT_A=0Duc17E8SGKtXDMhCXMMMZtu7p0PW67yldK6voi99Cc=>
Closed loop partial details
https://wiki.onap.org/display/DW/Tutorial%3A+Verifying+and+Observing+a+deployed+Service+Instance<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Tutorial-253A-2BVerifying-2Band-2BObserving-2Ba-2Bdeployed-2BService-2BInstance=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=0c94DuMw40KaHf-_5LU5QAqvGkV0vsBrN1yvOHoUT_A=WBH_1k3uO0O3raw1FFzSbDloCjCzXoi16VTOdvIJm0g=>
   thank you
   /michael


From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>]
 On Behalf Of PLATANIA, MARCO (MARCO)
Sent: Monday, July 24, 2017 16:02
To: Cipher Cipher 
<cipher.for.programm...@gmail.com<mailto:cipher.for.programm...@gmail.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] [DCAE] DCAE 1.0.0

Hello Shankar,

You are right. DCAE (and MSO) have been modified to work in vanilla OpenStack 
since seed code 1.1.0 (current master branch). Seed code release 1.0.0 supports 
Rackspace only.

Please refer to the wiki page below for information about ONAP installation in 
vanilla OpenStack: 
https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BInstallation-2Bin-2BVanilla-2BOpenStack=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=0c94DuMw40KaHf-_5LU5QAqvGkV0vsBrN1yvOHoUT_A=_WdJmuBVExk20vaaihMr5scm2mR0oSSg64Uj1a0Nhpg=>

Thanks,
Marco


From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Cipher Cipher 
<cipher.for.programm...@gmail.com<mailto:cipher.for.programm...@gmail.com>>
Date: Monday, July 24, 2017 at 3:08 PM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] [DCAE] DCAE 1.0.0

Hey,

According to the DCAE controller 
guide(https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_DCAE-2BController-2BDevelopment-2BGuide=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=cpf7fEpKw4eGoxszA_SApKcgwdf-r3IUdTWJKDLVaTI=92wpqMU1NYxeq7qqkzMvxyRFAxsAjtakdGuDHCSjwkI=>),
 it doesn't work in release-1.0.0. But I have already ONAP release-1.0.0 up and 
running, so to make DCAE working, we have to replace ONAP with new version? or 
is there any alternatives?

Cheers
Shankar
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<https:

Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

2017-07-19 Thread PLATANIA, MARCO (MARCO)

Arun,

You can modify the yaml file manually. Then you have to run “make down” to 
shutdown the entire environment and then “bash init.sh” and “make up” to 
startup again. Those files are in /opt/dcae-startup-vm-controller.

No need to rebuild ONAP.

Thanks,
Marco


From:  on behalf of "Arun Arora (c)" 

Date: Wednesday, July 19, 2017 at 2:00 PM
To: "LUND, CARSTEN (CARSTEN)" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] DCAE controller-startup.sh fails and throws error

Okay, thanks for pointing that out. I think redeploying ONAP stack is not 
necessary? Will it be fine if I just change the Zone in config.yaml in DCAE and 
rerun 
dcae_install.sh
 manually?
Also, do you think this is causing the problem of missing files and directories?
Thanks,
Arun
On Jul 19, 2017, at 11:06 PM, "LUND, CARSTEN (CARSTEN)" 
> wrote:
I noticed this from the log


+ export 'ZONE=NorthIndia '
+ ZONE='NorthIndia '


Note the space after NorthIndia.


Please remove from config.yaml and redeploy.


Carsten


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Wednesday, July 19, 2017 9:29 AM
To: MAJHI, TAPAN ; Josef Reisinger 
; FREEMAN, BRIAN D ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] DCAE controller-startup.sh fails and throws error



Hi All,



Regarding the issue I am facing for DCAE VMs deployment, the immediate blocker 
for me is required files and directories are not found (like cdap-instances, 
docker-instances, docker-instances). I am suspecting these directories are 
created in run-time as I searched them in the DCAA VM, Container and DCAE Demo 
Gittree but couldn’t find them.

Attaching the execution logs for your reference. All errors for missing files, 
directories are mentioned as exceptions in the attached execution log.



1)  I tried with rel-1.0 and rel-1.1 but both gave same errors

2)  Also tried with both 2-NIC and 1-NIC-FLOATING-IPS. No luck in this as 
well

3)  Currently using 1-NIC-FLOATING-IPS

4)  Verified config.yaml parameters with all configurations and 
modifications in 
https://jira.onap.org/browse/DCAEGEN2-69
 and 
https://jira.onap.org/browse/DCAEGEN2-7

5)  Found some more config issues in the config.yaml and fixed

6)  Finally, made sure the execution is going as per the sequence mentioned 
in 
https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide



The problem happens with the following command execution done as part of ‘make 
gen-config sync restart’

java -cp 'lib/*' 
org.openecomp.dcae.controller.operation.utils.GenControllerConfiguration $ZONE 
. GITLINK OPENECOMP-DEMO



I am not able to find the directories/ files listed in the errors.



Any pointers from anyone who have fixed these issues?

@Tapan, @Joseph, @Brian, special mention to you for any pointers to resolve 
this issue, as you have finished the deployment (Congrats BTW ☺ )





Thanks & Regards,

Arun Arora



PS: Wanted to mention again, I am deploying on VIO (VMware Integrated OpenStack)









From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Tuesday, July 18, 2017 8:29 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org
Subject: RE: DCAE controller-startup.sh fails and throws error



We also faced this issue and created an JIRA ID: DCAEGEN2-69



And  we tried to provided required conf and logs. Please let us know if 
additional details required.



Thanks.



Regards

Kanagaraj M



***

Re: [onap-discuss] [DCAE] DCAE Rackspace deployment

2017-07-18 Thread PLATANIA, MARCO (MARCO)

Hello Serkant,

DCAE spins up in Rackspace and vanilla openstack. Please see the wiki page 
about ONAP installation in openstack for further information.

If you want to spin up DCAE in Rackspace, you can use the Rackspace template 
instead.

Thanks,
Marco




On Tue, Jul 18, 2017 at 4:15 AM -0400, "Serkant Uluderya" 
> wrote:

Hello,

Installing and Running the ONAP 
Demos
 wiki page states that DCAE does not support 1.0.0 and Vanilla Openstack Heat 
template is required to deploy DCAE. Does it simply mean that I can't deploy 
DCAE, if I use rackspace template?

Kind regards,
Serkant
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-installation] DCAE installation now supported by all Heat templates

2017-07-17 Thread PLATANIA, MARCO (MARCO)

Hello Subhash,

The env file seems correct.

Can you try to rebuild? It may be a transient issue. Are the containers 
downloaded correctly in those VMs?

Did you see anything in the logs of the DCAE docker container?

Marco

_
From: Subhash Kumar Singh 
<subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>>
Sent: Monday, July 17, 2017 11:39 AM
Subject: RE: [onap-discuss] [onap-installation] DCAE installation now supported 
by all Heat templates
To: PLATANIA, MARCO (MARCO) 
<plata...@research.att.com<mailto:plata...@research.att.com>>, 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: Kanagaraj Manickam 
<kanagaraj.manic...@huawei.com<mailto:kanagaraj.manic...@huawei.com>>


Hello Marco,

We tried to stack ONAP with following properties as specified in environment 
file[1] (demo:origin/master):

artifacts_version: 1.1.0-SNAPSHOT
docker_version: 1.1-STAGING-latest
gerrit_branch: master
artifacts_version: 1.1.0-SNAPSHOT
docker_version: 1.1-STAGING-latest
gerrit_branch: master

We observed that SDC, VID and DCAE components are not coming up. I tried to 
re-initialize the docker but it didn’t help. I didn’t see any error message in 
docker logs but portal tabs for SDC and VID showing error message (VID : HTTP 
Status 404 and SDC: HTTP ERROR 305).

In case of 1.0-STAGING, we can see portal working with these components. Please 
let us know if we are missing anything for ONAP stacking.

[1] [1] 
https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.env;h=6446e3d5ff1b9993c2513fb8ddc98c812b8d4ff4;hb=HEAD

--
Regards,
Subhash Kumar Singh

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org]On Behalf Of PLATANIA, MARCO (MARCO)
Sent: Saturday, July 15, 2017 2:40 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [onap-installation] DCAE installation now supported by 
all Heat templates

ONAP Community,

All the Heat templates that we built to install ONAP in vanilla OpenStack now 
support the DCAE data collection and analytics platform installation.

Please refer to the updated wiki pages for detailed info about ONAP 
installationhttps://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BInstallation-2Bin-2BVanilla-2BOpenStack=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=w8m9w_NofWdY8dHz5w1dKY-vAnaTHul3CKHQ7Q9RIWs=qjIOet3JNBZ_EZJdXpZAheWiMTDKy4zdld22F8IBgRs=>
 and DCAE development 
guidehttps://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_DCAE-2BController-2BDevelopment-2BGuide=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=w8m9w_NofWdY8dHz5w1dKY-vAnaTHul3CKHQ7Q9RIWs=gAFEk4CK4939IIhyOq-elYOvXCvqYAa-tbLrS45cojE=>

Gerrit contains the latest Heat templates. Note 
thatonap_openstack.yaml<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack.yaml-3Bh-3Da17a0eeb7ca712ef29c0dde3cd09800ad8e28d16-3Bhb-3Drefs_heads_master=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=w8m9w_NofWdY8dHz5w1dKY-vAnaTHul3CKHQ7Q9RIWs=iWsJIKKo3SsPj3lToB519aeD02aep76vE_xkUJN_ZrY=>
 has been recently updated to work with DCAE.

Tests have been conducted in OpenStack Liberty. Please let us know if you have 
any questions and share your experience if you are going to use these templates 
in a different OpenStack release.

Note that the integration team used one of these templates to install ONAP in 
the OpenStack lab kindly offered by Windriver.

Thanks,
Marco



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

[onap-discuss] [onap-installation] DCAE installation now supported by all Heat templates

2017-07-14 Thread PLATANIA, MARCO (MARCO)

ONAP Community,

All the Heat templates that we built to install ONAP in vanilla OpenStack now 
support the DCAE data collection and analytics platform installation.

Please refer to the updated wiki pages for detailed info about ONAP 
installation 
https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack and 
DCAE development guide 
https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide

Gerrit contains the latest Heat templates. Note that 
onap_openstack.yaml
 has been recently updated to work with DCAE.

Tests have been conducted in OpenStack Liberty. Please let us know if you have 
any questions and share your experience if you are going to use these templates 
in a different OpenStack release.

Note that the integration team used one of these templates to install ONAP in 
the OpenStack lab kindly offered by Windriver.

Thanks,
Marco

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

Re: [onap-discuss] [DOC] Documentation for running demo on Openstack Mitaka

2017-07-06 Thread PLATANIA, MARCO (MARCO)

Josef, Tapan,

Documenting your progress is a good idea! The heat templates for vLB and vFW 
that are currently in Gerrit work with OpenStack Liberty.

Tapan,

What changes did you make for Mitaka?

Thanks,
Marco

From:  on behalf of Josef Reisinger 

Date: Thursday, July 6, 2017 at 9:11 AM
To: "MAJHI, TAPAN" 
Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] [DOC] Documentation for running demo on Openstack 
Mitaka

Hi Tapan,

I started a similar activity with pages under 
https://wiki.onap.org/display/DW/Tutorial%3A+Creating+a+Service+Instance+from+a+Design+Model...
 for Openstack Ocata - while I don't see any Ocata vs. Mitaka issues. You may 
want to check for duplicates

Mit freundlichen Grüßen / Kind regards
Josef Reisinger
When wisdom comes to call, there's nobody listening at all - Pendragon / Man Of 
Nomadic Traits

IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius

IBM Deutschland
Godesberger Allee 127
53175 Bonn Beuel

Phone:+49 151 1426 4559
Mobile:  +49-(0) 151 1426 4559
E-Mail:  josef.reisin...@de.ibm.com


IBM Deutschland GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Martina Koederitz (Vorsitzende), Nicole Reimer, Norbert 
Janzen, Dr. Christian Keller, Ivo Koerner, Stefan Lutz
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart, HRB 
14562 / WEEE-Reg.-Nr. DE 99369940






From:Tapan Majhi 
To:"onap-discuss@lists.onap.org" 
Date:06.07.2017 15:00
Subject:[onap-discuss] [DOC] Documentation for running demo on 
Openstack Mitaka
Sent by:onap-discuss-boun...@lists.onap.org




Hi All,

We managed to run the vFw and vLB demo on Mitaka version of Openstack.
Some modification in the robot script/Python libraries and the heat files of 
vFW and vLB is done to run the demo successfully.
We are thinking of creating a page in the wiki to list down all the changes .

Let me know if this will be helpful for others or not. If yes where should I 
create the page?
Possible options I can think of is  
https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos

Please suggest

Regards
Tapan M

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
Amdocs Development Centre India Private Limited having CIN: 
U72200PN2004PTC0188320 converted into Amdocs Development Centre India LLP (A 
limited liability partnership withLLP Identification Number: AAI-6901 
effective 28th Feb 2017)___
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] DCAE Health-Check is failing

2017-06-30 Thread PLATANIA, MARCO (MARCO)

Subhash,

After the DCAE VM is created, dcae_install.sh and dcae_vm_init.sh set up, 
download and install software dependencies, plus dcae_vm_init.sh calls the 
Makefile script in /opt/dcae-startup-vm-controller. If you look at 
dcae_vm_init.sh, you’ll see a “make up” instruction.

When you want to rebuild DCAE, please run make down (from 
/opt/dcae-startup-vm-controller), such that the controller tears down the 5 VMs 
that it spins up and updates its internal state. Running dcae_vm_init.sh may 
compromise the DCAE controller state because it will try to create VMs that 
possibly already exist.

That being said, from the attached logs I see that you are having connectivity 
issues:
http error: java.net.NoRouteToHostException: No route to host (Host unreachable)

Finally, version 1.0.0 (in release-1.0.0 branch) is not supported. Please use 
these parameters:
artifacts_version: 1.1.0-SNAPSHOT
docker_version: 1.1-STAGING-latest
gerrit_branch: master
dcae_base_environment: 1-NIC-FLOATING-IPS
gitlab_branch: master
dcae_code_version: 1.1.0

The environment files in Gerrit have been updated accordingly.

For further details about DCAE, please refer to the wiki page: 
https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide

Thanks,
Marco

From: Subhash Kumar Singh <subhash.kumar.si...@huawei.com>
Date: Friday, June 30, 2017 at 8:56 AM
To: "LUND, CARSTEN (CARSTEN)" <l...@research.att.com>, "PLATANIA, MARCO 
(MARCO)" <plata...@research.att.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>
Cc: Kanagaraj Manickam <kanagaraj.manic...@huawei.com>
Subject: RE: [onap-discuss] DCAE Health-Check is failing

Hello Marco and Carsten,

I’ve updated the configuration file (/opt/app/dcae-controller/config.yaml) in 
DCAE VM as you have suggested and again tried to execute `dcae_vm_init.sh` .
This time I can see following three VMs got created (but floating IP is not 
associated to VMs):

$ openstack server list
+--+--++--++
| ID   | Name | Status | 
Networks | Image Name   
  |
+--+--++--++
| ececf3ce-d518-457a-83d6-9bfb463d7d89 | zldcZONESTATEcdap00  | ACTIVE | 
oam_ecomp_v1rl=10.3.0.8 | 
trusty-server-cloudimg-amd64-disk1.img |
| c459eeff-8f9d-4625-b1b3-b70a6b7f583f | zldcZONESTATEpstg00  | ACTIVE | 
oam_ecomp_v1rl=10.3.0.6  | 
xenial-server-cloudimg-amd64-disk1.img |
| 8b486bcc-77a0-49f3-b1c7-ac46257cce99 | zldcZONESTATEcoll00  | ACTIVE | 
oam_ecomp_v1rl=10.3.0.11 | 
trusty-server-cloudimg-amd64-disk1.img |


Still, I can’t see other 2 VMs (cdap01, cdap02) even after waiting for 60 
minutes, sharing docker logs [1].
Could you please explain the flow of creation of VMs (heat and required 
scripts) in DCAE and their communication so that we can debug this issue.

As part of this issue, I’ve identified that heat environment file was 
configured with wrong values, which I’ve corrected and pushed [2].
At the same time, I observed that we have hardcoded tag in “Makefile” and  
“docker-compose.yml” and it is referring to image version 1.0.0 (I am using 
latest tag).

In our setup, Network 192.168.x.y is externally reachable for us and floating 
IPs are not in the use.

Please let us know your thoughts.

[1] 
http://paste.openstack.org/show/614170/<https://urldefense.proofpoint.com/v2/url?u=http-3A__paste.openstack.org_show_614170_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=DMpAS97s97V1pt6He27TEIsfGaTLFwxHuHRWjatPPBg=vGUSOxPhHDjYY7jhfpDGUnhNF-sJvnzL11A992w5Sk0=>
[2] 
https://gerrit.onap.org/r/#/c/5617/<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_5617_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=DMpAS97s97V1pt6He27TEIsfGaTLFwxHuHRWjatPPBg=DpW_ZO3SPTypEeOsa7pKjOMJjArp3W--kQ3Mu61nyXs=>

--
Regards,
Subhash Kumar Singh


From: LUND, CARSTEN (CARSTEN) [mailto:l...@research.att.com]
Sent: Thursday, June 29, 2017 8:03 PM
To: PLATANIA, MARCO (MARCO) <plata...@research.att.com>; Subhash Kumar Singh 
<subhash.kumar.si...@huawei.com>; onap-discuss@lists.onap.org
Cc: Kanagaraj Manickam <kanagaraj.manic...@huawei.com>
Subject: RE: [onap-discuss] DCAE Health-Check is failing

Make sure the floating IPs (whatever they are) have been associated with the 
tenant and not in use.

Trying to keep everything documented on 
https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_DCAE-2BController-2B

Re: [onap-discuss] DCAE Health-Check is failing

2017-06-29 Thread PLATANIA, MARCO (MARCO)

Hello Subhash,

There are a few errors in the ONAP stack deployment for what regards the 
parameters you set.

The Heat env file should contain:

  artifacts_version: 1.1.0-SNAPSHOT
  docker_version: 1.1-STAGING-latest
  gerrit_branch: master
  cloud_env: openstack
  dcae_base_environment: 1-NIC-FLOATING-IPS
  gitlab_branch: master
  dcae_code_version: 1.1.0

You are trying to install DCAE release-1.0.0, which doesn’t work in vanilla 
OpenStack. The configuration above will install DCAE 1.1.0

Also, I’m not sure whether 192.168.X.Y works as floating IP set. Those should 
be externally reachable.

Marco


From: Subhash Kumar Singh <subhash.kumar.si...@huawei.com>
Date: Thursday, June 29, 2017 at 10:15 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Cc: Kanagaraj Manickam <kanagaraj.manic...@huawei.com>, "LUND, CARSTEN 
(CARSTEN)" <l...@research.att.com>
Subject: RE: [onap-discuss] DCAE Health-Check is failing

Hello Marco,

Please check the config file :
http://paste.openstack.org/show/614068/<https://urldefense.proofpoint.com/v2/url?u=http-3A__paste.openstack.org_show_614068_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=y8hhUzPBsDA6YCsF228o-roNXtVgs4-idc_BgSDrPIg=xkp0a9uKD7SbfTZRETSXpVp-6QEVGmDGRBGTyM9Apsw=>

--
Regards,
Subhash Kumar Singh

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Thursday, June 29, 2017 7:01 PM
To: Subhash Kumar Singh <subhash.kumar.si...@huawei.com>; 
onap-discuss@lists.onap.org
Cc: Kanagaraj Manickam <kanagaraj.manic...@huawei.com>; LUND, CARSTEN (CARSTEN) 
<l...@research.att.com>
Subject: Re: [onap-discuss] DCAE Health-Check is failing

Hello Subhash,

Could you please paste the content of /opt/app/dcae-controller/config.yaml ?

Adding Carsten who knows DCAE best.

Marco


From: Subhash Kumar Singh 
<subhash.kumar.si...@huawei.com<mailto:subhash.kumar.si...@huawei.com>>
Date: Thursday, June 29, 2017 at 9:09 AM
To: "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com<mailto:plata...@research.att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: Kanagaraj Manickam 
<kanagaraj.manic...@huawei.com<mailto:kanagaraj.manic...@huawei.com>>
Subject: RE: [onap-discuss] DCAE Health-Check is failing

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

Re: [onap-discuss] Is there a way to confirm correct spin-up of vFW stack

2017-06-29 Thread PLATANIA, MARCO (MARCO)

Hi Josef,

I replied to your comment. Please see below.

Please make sure that your OpenStack security group has the ports open like this
Ingress

IPv4

TCP

1 - 65535

0.0.0.0/0

-

Delete Rule


Ingress

IPv4

TCP

22 (SSH)

0.0.0.0/0

-

Delete Rule


Ingress

IPv4

UDP

1 - 65535

0.0.0.0/0

-

Delete Rule


Ingress

IPv4

UDP

53

0.0.0.0/0

-

Also, could you run these commands:
in the packet generator: tcpdump -i eth1
in the firewall: tcpdump -i eth2
You should see traffic flowing through:
14:16:11.384577 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, length 
120
14:16:11.484337 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, length 
120
14:16:11.584315 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, length 
120
14:16:11.684496 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, length 
120
14:16:11.784383 IP 192.168.10.200.15320 > 192.168.20.250.http-alt: UDP, length 
120

Please let us know.

Marco

From:  on behalf of Josef Reisinger 

Date: Thursday, June 29, 2017 at 9:47 AM
To: onap-discuss 
Subject: [onap-discuss] Is there a way to confirm correct spin-up of vFW stack

I asked the following uestion below under 
https://wiki.onap.org/questions/8227972/is-there-a-way-to-confirm-correct-spin-up-of-vfw-stack.

I have spun up a stack in Openstack Ocata containing the three VMs for the 
firewall demo. I am able to connect to http://:667/ and can see some 
graphics. But there is no traffic at all. I can see in pgn & fwl that there is 
some VPN setup with vpp.. but I cannot see any real traffic on 
(un)protected_network.

I used

curl -X PUT -H "Authorization: Basic YWRtaW46YWRtaW4=" -H "Content-Type: 
application/json" -H "Cache-Control: no-cache" -H "Postman-Token: 
9005870c-900b-2e2e-0902-ef2009bb0ff7" -d '{"pg-streams":{"pg-stream": 
[{"id":"fw_udp1", "is-enabled":"true"},{"id":"fw_udp2", 
"is-enabled":"true"},{"id":"fw_udp3", "is-enabled":"true"},{"id":"fw_udp4", 
"is-enabled":"true"},{"id":"fw_udp5", "is-enabled":"true"},{"id":"fw_udp6", 
"is-enabled":"true"},{"id":"fw_udp7", "is-enabled":"true"},{"id":"fw_udp8", 
"is-enabled":"true"},{"id":"fw_udp9", "is-enabled":"true"},{"id":"fw_udp10", 
"is-enabled":"true"}]}}' 
"http://localhost:8183/restconf/config/sample-plugin:sample-plugin/pg-streams"

to trigger some messages ... with no success. Is there any documentation 
available which helps to understand what the vFW stack does?

Mit freundlichen Grüßen / Kind regards
Josef Reisinger
When wisdom comes to call, there's nobody listening at all - Pendragon / Man Of 
Nomadic Traits

IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius

IBM Deutschland
Godesberger Allee 127
53175 Bonn Beuel

Phone:+49 151 1426 4559
Mobile:  +49-(0) 151 1426 4559
E-Mail:  josef.reisin...@de.ibm.com





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

Re: [onap-discuss] DCAE Health-Check is failing

2017-06-29 Thread PLATANIA, MARCO (MARCO)

Hello Subhash,

Could you please paste the content of /opt/app/dcae-controller/config.yaml ?

Adding Carsten who knows DCAE best.

Marco


From: Subhash Kumar Singh <subhash.kumar.si...@huawei.com>
Date: Thursday, June 29, 2017 at 9:09 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Cc: Kanagaraj Manickam <kanagaraj.manic...@huawei.com>
Subject: RE: [onap-discuss] DCAE Health-Check is failing

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

Re: [onap-discuss] DCAE Health-Check is failing

2017-06-28 Thread PLATANIA, MARCO (MARCO)

Subash,

DCAE takes longer to install. The DCAE controller spins up 5 additional VMs off 
the Heat template. This takes about 25 minutes, plus configuration time. 
Overall, please allow about one hour before running health checks. The VMs may 
be ready but still getting configured (the Hadoop/CDAP cluster takes the 
longest).

Regarding point 3) that you mention, those floating IPs will be used by the 5 
additional VMs that DCAE controller spins up. If they are not in use, it’s 
likely that those VMs haven’t been created yet.

Thanks,
Marco

From:  on behalf of Subhash Kumar Singh 

Date: Wednesday, June 28, 2017 at 10:50 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] DCAE Health-Check is failing

Hello Everyone,

We are trying run the robot test case (ete.sh) to test the health status of 
DCAE service but it is failing:

# ./ete.sh health
Starting Xvfb on display :88 with res 1280x1024x24
Executing robot tests at log level TRACE
==
OpenECOMP ETE
==
OpenECOMP ETE.Robot
==
OpenECOMP ETE.Robot.Testsuites
==
OpenECOMP ETE.Robot.Testsuites.Health-Check :: Testing ecomp components are...
==
Basic DCAE Health Check   | FAIL |
Value of dictionary key 'healthTestStatus' does not match: YELLOW != GREEN
--

So, following are the questions that we would like to ask:

1] We observed that in created docker instance 
(dcaestartupvmcontroller_dcae-controller_1) hosts file is not reflecting 
correct hostname and IP mapping as provided in the heat template.

/etc/hosts :

172.18.0.2  c52bfc0fba28
10.0.4.1   zldcZONESTATEcont00.dcae.simpledemo.openecomp.org cont00 
zldcZONESTATEcont00
10.0.4.101 zldcZONESTATEpstg00.dcae.simpledemo.openecomp.org pstg00 
zldcZONESTATEpstg00
10.0.4.102 zldcZONESTATEcoll00.dcae.simpledemo.openecomp.org coll00 
zldcZONESTATEcoll00 dcae-coll-ZONE.dcae.simpledemo.openecomp.org
10.0.103 zldcZONESTATEcdap00.dcae.simpledemo.openecomp.org cdap00 
zldcZONESTATEcdap00
10.0.4.104 zldcZONESTATEcdap01.dcae.simpledemo.openecomp.org cdap01 
zldcZONESTATEcdap01
10.0.4.105 zldcZONESTATEcdap02.dcae.simpledemo.openecomp.org cdap02 
zldcZONESTATEcdap02
10.0.6.1   policy.api.simpledemo.openecomp.org


2] In the hosts file we are observing one more host entry :

172.18.0.2  c52bfc0fba28

could you please let us know which host/service it is referring, as we are 
seeing the error message around this IP:

/opt/app/dcae-controller-platform-server/logs# tailf error.log
06/28-14:06:17.615|ac864c39-a759-411f-a232-2325b89ade5e|??|databus 
polling|DATABUS_POLLING||WARN|1|172.18.0.2|c52bfc0fba28|||DCAE-CONTROLLER-DATABUS-POLLING-FAILED-5001W
 java.lang.RuntimeException: http error: java.net.SocketTimeoutException: 
connect timed out


3] Could you please let us know the use of five extra assigned IP's to the 
DCAE, because we are not seeing any process/ docker consuming it.

Kindly help us.

--
Regards,
Subhash Kumar Singh


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

Re: [onap-discuss] DCAE HealthCheck failing while running ete.sh from Robot VM on ONAP Environment using Vanila Openstack Mitaka

2017-06-09 Thread PLATANIA, MARCO (MARCO)

Hi Arun,

Sorry for missing this point. Master branch has the latest developments, so 
that’s the right place.

Thanks,
Marco

From: "Arun Arora (c)" <aroraa...@vmware.com>
Date: Friday, June 9, 2017 at 11:07 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, "Gaurav Gupta (c)" 
<guptagau...@vmware.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>
Subject: RE: [onap-discuss] DCAE HealthCheck failing while running ete.sh from 
Robot VM on ONAP Environment using Vanila Openstack Mitaka

Hi Marco,

One question, from which repo we need to pull the latest template files? For 
now we took it from master repo but it was some time back.

Thanks,

Arun

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO 
(MARCO)
Sent: Friday, June 09, 2017 6:26 PM
To: Gaurav Gupta (c) <guptagau...@vmware.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] DCAE HealthCheck failing while running ete.sh from 
Robot VM on ONAP Environment using Vanila Openstack Mitaka

Hello Gurav,

The health check fails because the data collection and analytics platform that 
DCAE controller spins up off the Heat template is not there. Please pull the 
latest templates from Gerrit (onap_openstack_float.* is the right one).

In order for DCAE to work correctly, at this time, you need to manually assign 
5 floating IPs to your OpenStack project. This 5 IPs need to be associated to:

  dcae_coll_float_ip

  dcae_db_float_ip

  dcae_hdp1_float_ip

  dcae_hdp2_float_ip

  dcae_hdp3_float_ip

in whatever order you want. At run time, the DCAE controller will fetch those 
IPs from the underlying OpenStack platform and assign to the VMs defined above. 
To assign floating IPs to your project, from the OpenStack horizon dashboard, 
click on Compute -> Access & Security -> Floating IPs. Then click “Allocate IP 
To Project” 5 times. OpenStack will assign 5 IPs to you.

I will update the wiki page soon 
https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_ONAP-2BInstallation-2Bin-2BVanilla-2BOpenStack=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ=_WFXpPJ_JwkkWhI-YZmod5GQhpcLWs34pvmrcmuXlzU=G8YSzU3JJh2WAnZJldwwfAi5gL9wAmWei5FM4GeJ0-4=>
 and send an email when done. Note, however, that DCAE team is still working on 
a DNS issue within the DCAE collector docker container. The issue is tracked in 
this Jira: 
https://jira.onap.org/browse/DCAE-7<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_DCAE-2D7=DwMGaQ=uilaK90D4TOVoH58JNXRgQ=fJSaCk5Dtn2KbIeqRCU_Kzr_L_vL-XtXjh29c6PfRGQ=_WFXpPJ_JwkkWhI-YZmod5GQhpcLWs34pvmrcmuXlzU=2yWa5tD95oV8lApfRWNckjUUF-LBDeoXvgYSTyfVdYU=>

Thanks,

Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Gaurav Gupta (c)" 
<guptagau...@vmware.com<mailto:guptagau...@vmware.com>>
Date: Friday, June 9, 2017 at 6:02 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Subject: [onap-discuss] DCAE HealthCheck failing while running ete.sh from 
Robot VM on ONAP Environment using Vanila Openstack Mitaka

Hello there

We are running into the DCAE Health check issue while running the ete.sh health

The ONAP Environment is created using below yaml and env files .

https://gerrit.onap.org/r/gitweb?=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3F-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack-5Ffloat.yaml-3Bh-3D659f94c93b9c5dfae02031ddcae82161ce927318-3Bhb-3Drefs_heads_master=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=O2DDMhNO_94DlSebx9F530e1ha93SaRNyjxvnisBHWg=gcRIgwkOXK3wP7gs8VnaBYBYIrDRBL1MMTVmaSLmMhU=>

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack-5Ffloat.yaml-3Bh-3D659f94c93b9c5dfae02031ddcae82161ce927318-3Bhb-3Drefs_heads_master=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=O2DDMhNO_94DlSebx9F530e1ha93SaRNyjxvnisBHWg=I0cC8ZVMk4ZeQnaJXvx0jNf8cXqShdQEMDetYflCJNU=>

Lab Environment

Openstack Mitaka on Centos7

ONAP 12 VM’s are deployed .

For DCAE VM’s – we see 1 docker pull request and 1 docker being pulled and 
docker is up as seen inside the DCAE VM using docker ps –a command .

[cid

[onap-discuss] [installation] Heat template and instructions to run DCAE in vanilla OpenStack

2017-06-09 Thread PLATANIA, MARCO (MARCO)

All,

I updated the wiki page about ONAP installation in vanilla OpenStack: 
https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack

There’s a new paragraph (in blue) that highlights the necessary steps to run 
DCAE in OpenStack. Please use the following templates for installation: 
onap_openstack_float.yaml
 and 
onap_openstack_float.env

Note, however, that DCAE team is still working on a DNS issue within the DCAE 
collector docker container. The issue is tracked in this Jira: 
https://jira.onap.org/browse/DCAE-7

Finally, the Heat templates linked above include the new A configurations. 
A now has 2 VMs: one has the docker containers that run the A logic and 
one has databases and third-party software dependencies.

Thanks,
Marco

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

Re: [onap-discuss] DCAE HealthCheck failing while running ete.sh from Robot VM on ONAP Environment using Vanila Openstack Mitaka

2017-06-09 Thread PLATANIA, MARCO (MARCO)

Hello Gurav,

The health check fails because the data collection and analytics platform that 
DCAE controller spins up off the Heat template is not there. Please pull the 
latest templates from Gerrit (onap_openstack_float.* is the right one).

In order for DCAE to work correctly, at this time, you need to manually assign 
5 floating IPs to your OpenStack project. This 5 IPs need to be associated to:
  dcae_coll_float_ip
  dcae_db_float_ip
  dcae_hdp1_float_ip
  dcae_hdp2_float_ip
  dcae_hdp3_float_ip

in whatever order you want. At run time, the DCAE controller will fetch those 
IPs from the underlying OpenStack platform and assign to the VMs defined above. 
To assign floating IPs to your project, from the OpenStack horizon dashboard, 
click on Compute -> Access & Security -> Floating IPs. Then click “Allocate IP 
To Project” 5 times. OpenStack will assign 5 IPs to you.

I will update the wiki page soon 
https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack and 
send an email when done. Note, however, that DCAE team is still working on a 
DNS issue within the DCAE collector docker container. The issue is tracked in 
this Jira: https://jira.onap.org/browse/DCAE-7

Thanks,
Marco

From:  on behalf of "Gaurav Gupta (c)" 

Date: Friday, June 9, 2017 at 6:02 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] DCAE HealthCheck failing while running ete.sh from 
Robot VM on ONAP Environment using Vanila Openstack Mitaka


Hello there



We are running into the DCAE Health check issue while running the ete.sh health



The ONAP Environment is created using below yaml and env files .


https://gerrit.onap.org/r/gitweb?=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master



https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master

Lab Environment
Openstack Mitaka on Centos7
ONAP 12 VM’s are deployed .
For DCAE VM’s – we see 1 docker pull request and 1 docker being pulled and 
docker is up as seen inside the DCAE VM using docker ps –a command .
[cid:image001.png@01D2E0FE.28D2E2F0]
But while running the healthCheck it seems it is looking for additional docker 
on DCAE VM .
Error Message from healthCheck results is pasted below highlighted in red .

KEYWORD dcae_interface . Check DCAE Results ${resp.json()}
Documentation:


Parse DCAE JSON response and make sure all rows have healthTestStatus=GREEN

Start / End / Elapsed:

20170606 18:45:15.912 / 20170606 18:45:15.957 / 00:00:00.045


18:45:15.956

TRACE

Arguments: [ {'healthTestMessageCode': 'Cluster not deployed', 
'healthTestStatus': 'YELLOW', 'instance': 'NorthIndia', 'service': 
'cdap-helloworld', 'status': 'UNDEPLOYED'} | 'healthTestStatus' | 'GREEN' ]


18:45:15.956

FAIL

Value of dictionary key 'healthTestStatus' does not match: YELLOW != GREEN


with best regards
gaurav
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Is it ok to replace the value of vm_base_name "vm1" to "vm2" in the ONAP HEAT template?

2017-06-07 Thread PLATANIA, MARCO (MARCO)

Hello Josef,

vm_base_name is to avoid confusion. You can have multiple vm1_component_name, 
because OpenStack uses UUID not VM names, but you will be confused. 
vm_base_name is independent from DNS configuration. The DNS configuration 
doesn’t require any change, it’s just a FQDM-IP address mapping, but the FQDN 
doesn’t need to necessarily match the VM name (indeed, despite some similarity, 
it doesn’t).

Hope this helps.

Thanks,
Marco

From:  on behalf of Josef Reisinger 

Date: Wednesday, June 7, 2017 at 8:55 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Is it ok to replace the value of vm_base_name "vm1" to 
"vm2" in the ONAP HEAT template?

Folks,

I am running currently two independent ONAP environments. To avoid to be too 
confused, I changed the value of parameter  vm_base_name from "vm1" to "vm2", I 
am not sure that this is consistently configured throughout the environment as 
I see a log of entries with "vm1" in the name in the dns server config. 
Liekwise I assume this is is true for the VMs which use host names to connect 
to each other.
Should I better revert to "vm1" for both environments for the next stack 
creation?

Mit freundlichen Grüßen / Kind regards
Josef Reisinger

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

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-30 Thread PLATANIA, MARCO (MARCO)

You can add sed -i "s/ens[0-9]*/eth0/g" 
/etc/udev/rules.d/70-persistent-net.rules to mso/robot/asdc_install.sh, in the 
block of code in which the interface name is changed.

Then, you can commit the changes, I’ll review them and merge.

If you prefer, I can make those changes by myself.

Marco

From: "Arun Arora (c)" <aroraa...@vmware.com>
Date: Monday, May 29, 2017 at 3:57 PM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, "Kapil Gupta 
(c)" <gka...@vmware.com>, "Gaurav Gupta (c)" <guptagau...@vmware.com>, 
"Abhishek Saxena (c)" <abhisheksax...@vmware.com>, Suresh Babu Nekkalapudi 
<snekkalap...@vmware.com>, Ramesh Tammana <rame...@vmware.com>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation


Pls let me know the procedure to commit patch.



Thanks,

Arun





From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Monday, May 29, 2017 10:12 PM
To: Arun Arora (c) <aroraa...@vmware.com>
Cc: onap-discuss@lists.onap.org; Kapil Gupta (c) <gka...@vmware.com>; Gaurav 
Gupta (c) <guptagau...@vmware.com>; Abhishek Saxena (c) 
<abhisheksax...@vmware.com>; Suresh Babu Nekkalapudi <snekkalap...@vmware.com>; 
Ramesh Tammana <rame...@vmware.com>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



I think so…



Marco



From: "Arun Arora (c)" <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com<mailto:plata...@research.att.com>>
Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, "Kapil Gupta 
(c)" <gka...@vmware.com<mailto:gka...@vmware.com>>, "Gaurav Gupta (c)" 
<guptagau...@vmware.com<mailto:guptagau...@vmware.com>>, "Abhishek Saxena (c)" 
<abhisheksax...@vmware.com<mailto:abhisheksax...@vmware.com>>, Suresh Babu 
Nekkalapudi <snekkalap...@vmware.com<mailto:snekkalap...@vmware.com>>, Ramesh 
Tammana <rame...@vmware.com<mailto:rame...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?

Regards

Arun

On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com<mailto:plata...@research.att.com>> wrote:

OK thanks Arun and apologies for missing the latest email. I was starting my 
email stack from the bottom ☺



I’m glad you were able to reboot the VMs correctly.



Marco



From: "Arun Arora (c)" <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>, 
"PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com<mailto:plata...@research.att.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" <gka...@vmware.com<mailto:gka...@vmware.com>>, "Gaurav 
Gupta (c)" <guptagau...@vmware.com<mailto:guptagau...@vmware.com>>, "Abhishek 
Saxena (c)" <abhisheksax...@vmware.com<mailto:abhisheksax...@vmware.com>>, 
Suresh Babu Nekkalapudi 
<snekkalap...@vmware.com<mailto:snekkalap...@vmware.com>>, Ramesh Tammana 
<rame...@vmware.com<mailto:rame...@vmware.com>>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Hi Marco,



I figured that change in /etc/default/grub should be OK. However, change in 
interface name is also required in /etc/udev/rules.d/70-persistent-net.rules. 
This file also has the interface name which remain ensX after reboot which 
causes network interface configuration failure.



If following is executed then after reboot VM is reachable, interface name is 
changes to eth0 and network works fine.

sed -i "s/ens[0-9]*/eth0/g" /etc/udev/rules.d/70-persistent-net.rules





Thanks,

Arun



From: 
onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Monday, May 29, 2017 3:15 PM
To: PLATANIA, MARCO (MARCO) 
<plata...@research.att.com<mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.on

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread PLATANIA, MARCO (MARCO)

I think so…

Marco

From: "Arun Arora (c)" <aroraa...@vmware.com>
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, "Kapil Gupta 
(c)" <gka...@vmware.com>, "Gaurav Gupta (c)" <guptagau...@vmware.com>, 
"Abhishek Saxena (c)" <abhisheksax...@vmware.com>, Suresh Babu Nekkalapudi 
<snekkalap...@vmware.com>, Ramesh Tammana <rame...@vmware.com>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Thanks Marco. So can we add this in the install scripts for SDC, Robot and MSO?
Regards
Arun
On May 29, 2017, at 9:02 PM, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com<mailto:plata...@research.att.com>> wrote:
OK thanks Arun and apologies for missing the latest email. I was starting my 
email stack from the bottom ☺

I’m glad you were able to reboot the VMs correctly.

Marco

From: "Arun Arora (c)" <aroraa...@vmware.com>
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" <aroraa...@vmware.com>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>
Cc: "Kapil Gupta (c)" <gka...@vmware.com>, "Gaurav Gupta (c)" 
<guptagau...@vmware.com>, "Abhishek Saxena (c)" <abhisheksax...@vmware.com>, 
Suresh Babu Nekkalapudi <snekkalap...@vmware.com>, Ramesh Tammana 
<rame...@vmware.com>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Hi Marco,

I figured that change in /etc/default/grub should be OK. However, change in 
interface name is also required in /etc/udev/rules.d/70-persistent-net.rules. 
This file also has the interface name which remain ensX after reboot which 
causes network interface configuration failure.

If following is executed then after reboot VM is reachable, interface name is 
changes to eth0 and network works fine.

sed -i "s/ens[0-9]*/eth0/g" /etc/udev/rules.d/70-persistent-net.rules

Thanks,

Arun

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Monday, May 29, 2017 3:15 PM
To: PLATANIA, MARCO (MARCO) <plata...@research.att.com>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) <gka...@vmware.com>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Hi Marco,

I realized you were referring to /etc/default/grub but in my previous email I 
attached grub.conf files for all VM.

I am attaching /etc/default/grub of each VM now.

Pls note as all three VMs use Ubuntu 16.04 as image I am assuming that the 
original grub is same for all. So, I created a VM with Ubuntu 16.04 and took 
grub file from it. Pls let me know if this is incorrect procedure to get 
unmodified /etc/default/grub.

Thanks,

Arun

From: Arun Arora (c)
Sent: Monday, May 29, 2017 12:55 PM
To: PLATANIA, MARCO (MARCO) 
<plata...@research.att.com<mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Hi Marco,

I am attaching the Original and modified grub.cfg file for all VMs. Pls let me 
know of any possible fix.

Also, In my understanding whatever fix is done should happen automatically when 
creating ONAP stack via HEAT. We can try the fix and then can think of how to 
automate it.

With Regards,

Arun

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Friday, May 26, 2017 6:51 PM
To: Arun Arora (c) <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Hello Arun,

Some components need to know their public IP address. This is retrieved in 
_vm_init.sh (i.e. policy, sdc). We use this command:

ifconfig eth0 | grep "inet addr" | tr -s ' ' | cut -d' ' -f3 | cut -d':' -f2

Because Ubuntu 16.04 VMs have a different vNIC name, as you said ensX, we 
changed the interface name in those VMs to reflect the usual case. We didn’t 
see any problem after rebooting the VMs. Thank you for letting us know.

I think the problem is not in the vNIC per se, but in the grub file that gets 
modified. That prevents correct start up. Could you please attach the original 
grub file?

Th

Re: [onap-discuss] onap-discuss Digest, Vol 3, Issue 7

2017-05-29 Thread PLATANIA, MARCO (MARCO)

Hello Shaheen,

Apologies for the late reply. Is this still causing issues to you?

As far as I see from the config file below, you modified some ONAP addresses, 
which is fine, but you need to check if the address assignment is coherent with 
the oam_network_cidr parameter in the heat environment file and the DNS VM 
config, which doesn’t seem to have the correct private address if it is 
resolving them incorrectly.

What template are you using? 

resolv.conf seems correct to me. Also, make sure your OpenStack installation 
isn’t preventing you from resolving DNS queries (unfortunately I’m not an 
expert on this, so I can provide little help.)

Thanks,
Marco


On 5/5/17, 1:28 PM, "onap-discuss-boun...@lists.onap.org on behalf of Ali, 
Shaheen"  wrote:

Hello ONAP-discussers,

More information.  Might have a DNS problem.  The resolv.conf file on all 
the instances look like this:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by 
resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.10.1.13
nameserver xxx.xxx.xxx.xxx
search openstacklocal


This is the correct instance named vm1-dns-server.  However, that domain is 
wrong: openstacklocal causes errors according to the messages in the DNS server.

May  5 17:04:42 vm1-dns-server named[1179]: client 10.10.1.17#43895 
(vm1-message-router.openstacklocal): query (cache) 
'vm1-message-router.openstacklocal/A/IN' denied
May  5 17:04:42 vm1-dns-server named[1179]: client 10.10.1.17#37936 
(vm1-message-router): query (cache) 'vm1-message-router/A/IN' denied

In fact, in this particular example, the portal (10.10.1.17) is trying to 
reach the host named vm1-message-router.  Problem is that the heat template set 
up a zone named simpledemo.openecomp.org in file 
/etc/bind/zones/db.simpledemo.openecomp.org which has an entry like so:
...
vm1.mr.simpledemo.openecomp.org.IN  A   10.10.1.15
...
;Message Router
;mr.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
ueb.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
mr.api.simpledemo.openecomp.org.IN  A   10.10.1
collector.api.simpledemo.openecomp.org. IN  A   10.10.1
;dbc.api.simpledemo.openecomp.org.  IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
;drprov.api.simpledemo.openecomp.org.   IN  CNAME   
vm1.mr.simpledemo.openecomp.org.
...
So, the A records that point to 10.10.1 look wrong.  The A record for 
vm1.mr.simpledemo.openecomp.org looks correct except that the portal logs in 
the container are throwing exceptions because the web service is trying to 
reach a host named vm1-message-router...

Any clues?

Shaheen


--

Message: 1
Date: Fri, 5 May 2017 13:23:47 +
From: "Ali, Shaheen" 
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Problem with tutorial
Message-ID:
<21aad91308992140820380d7bf70793fa87...@podcwmbxex505.ctl.intranet>
Content-Type: text/plain; charset="iso-8859-1"

I have set up ONAP on our own Newton OpenStack instance.  I cannot add a 
License Key Group.  Where should I begin to debug?  I have poked around the 
logs of vm-vid, vm-sdc and vm-message-router, but nothing stands out.

Shaheen


**


This communication is the property of CenturyLink and may contain 
confidential or privileged information. Unauthorized use of this communication 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please immediately notify the sender by reply e-mail 
and destroy all copies of the communication and any attachments.


___
onap-discuss mailing list
onap-discuss@lists.onap.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=4ApVTf-048h2sFMm8kA-ET1VUqm9vnfAQhSqv9gxi0g=O2C55Z1TwG8AuavqCnMgqww8R34H-t19kJiTE_oS8SM=
 


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

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread PLATANIA, MARCO (MARCO)

OK thanks Arun and apologies for missing the latest email. I was starting my 
email stack from the bottom ☺

I’m glad you were able to reboot the VMs correctly.

Marco

From: "Arun Arora (c)" <aroraa...@vmware.com>
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" <aroraa...@vmware.com>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>
Cc: "Kapil Gupta (c)" <gka...@vmware.com>, "Gaurav Gupta (c)" 
<guptagau...@vmware.com>, "Abhishek Saxena (c)" <abhisheksax...@vmware.com>, 
Suresh Babu Nekkalapudi <snekkalap...@vmware.com>, Ramesh Tammana 
<rame...@vmware.com>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Hi Marco,

I figured that change in /etc/default/grub should be OK. However, change in 
interface name is also required in /etc/udev/rules.d/70-persistent-net.rules. 
This file also has the interface name which remain ensX after reboot which 
causes network interface configuration failure.

If following is executed then after reboot VM is reachable, interface name is 
changes to eth0 and network works fine.

sed -i "s/ens[0-9]*/eth0/g" /etc/udev/rules.d/70-persistent-net.rules

Thanks,

Arun

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Monday, May 29, 2017 3:15 PM
To: PLATANIA, MARCO (MARCO) <plata...@research.att.com>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) <gka...@vmware.com>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Hi Marco,

I realized you were referring to /etc/default/grub but in my previous email I 
attached grub.conf files for all VM.

I am attaching /etc/default/grub of each VM now.

Pls note as all three VMs use Ubuntu 16.04 as image I am assuming that the 
original grub is same for all. So, I created a VM with Ubuntu 16.04 and took 
grub file from it. Pls let me know if this is incorrect procedure to get 
unmodified /etc/default/grub.

Thanks,

Arun

From: Arun Arora (c)
Sent: Monday, May 29, 2017 12:55 PM
To: PLATANIA, MARCO (MARCO) 
<plata...@research.att.com<mailto:plata...@research.att.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Hi Marco,

I am attaching the Original and modified grub.cfg file for all VMs. Pls let me 
know of any possible fix.

Also, In my understanding whatever fix is done should happen automatically when 
creating ONAP stack via HEAT. We can try the fix and then can think of how to 
automate it.

With Regards,

Arun

From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Friday, May 26, 2017 6:51 PM
To: Arun Arora (c) <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation

Hello Arun,

Some components need to know their public IP address. This is retrieved in 
_vm_init.sh (i.e. policy, sdc). We use this command:

ifconfig eth0 | grep "inet addr" | tr -s ' ' | cut -d' ' -f3 | cut -d':' -f2

Because Ubuntu 16.04 VMs have a different vNIC name, as you said ensX, we 
changed the interface name in those VMs to reflect the usual case. We didn’t 
see any problem after rebooting the VMs. Thank you for letting us know.

I think the problem is not in the vNIC per se, but in the grub file that gets 
modified. That prevents correct start up. Could you please attach the original 
grub file?

Thanks,

Marco

From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
<aroraa...@vmware.com<mailto:aroraa...@vmware.com>>
Date: Friday, May 26, 2017 at 8:15 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" <gka...@vmware.com<mailto:gka...@vmware.com>>
Subject: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping 
post ONAP stack creation

Hi All,

We have deployed ONAP on Vanilla OpenStack Mitaka (On top of CentOS 7). Using 
the following YAML and env files:

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master<https://urld

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-29 Thread PLATANIA, MARCO (MARCO)

Even these seems correct.

Can you verify these instructions instead?

sed -i "s/ens[0-9]*/eth0/g" /etc/network/interfaces.d/*.cfg
echo 'network: {config: disabled}' >> 
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg

Please check if those files exist and if changes are applied correctly.

Thanks,
Marco

From: "Arun Arora (c)" <aroraa...@vmware.com>
Date: Monday, May 29, 2017 at 5:44 AM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Cc: "Kapil Gupta (c)" <gka...@vmware.com>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation


Hi Marco,



I realized you were referring to /etc/default/grub but in my previous email I 
attached grub.conf files for all VM.

I am attaching /etc/default/grub of each VM now.

Pls note as all three VMs use Ubuntu 16.04 as image I am assuming that the 
original grub is same for all. So, I created a VM with Ubuntu 16.04 and took 
grub file from it. Pls let me know if this is incorrect procedure to get 
unmodified /etc/default/grub.



Thanks,

Arun



From: Arun Arora (c)
Sent: Monday, May 29, 2017 12:55 PM
To: PLATANIA, MARCO (MARCO) <plata...@research.att.com>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) <gka...@vmware.com>
Subject: RE: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Hi Marco,



I am attaching the Original and modified grub.cfg file for all VMs. Pls let me 
know of any possible fix.

Also, In my understanding whatever fix is done should happen automatically when 
creating ONAP stack via HEAT. We can try the fix and then can think of how to 
automate it.



With Regards,

Arun



From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Friday, May 26, 2017 6:51 PM
To: Arun Arora (c) <aroraa...@vmware.com<mailto:aroraa...@vmware.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Cc: Kapil Gupta (c) <gka...@vmware.com<mailto:gka...@vmware.com>>
Subject: Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via 
ssh/ping post ONAP stack creation



Hello Arun,



Some components need to know their public IP address. This is retrieved in 
_vm_init.sh (i.e. policy, sdc). We use this command:

ifconfig eth0 | grep "inet addr" | tr -s ' ' | cut -d' ' -f3 | cut -d':' -f2



Because Ubuntu 16.04 VMs have a different vNIC name, as you said ensX, we 
changed the interface name in those VMs to reflect the usual case. We didn’t 
see any problem after rebooting the VMs. Thank you for letting us know.



I think the problem is not in the vNIC per se, but in the grub file that gets 
modified. That prevents correct start up. Could you please attach the original 
grub file?



Thanks,

Marco



From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of "Arun Arora (c)" 
<aroraa...@vmware.com<mailto:aroraa...@vmware.com>>
Date: Friday, May 26, 2017 at 8:15 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>
Cc: "Kapil Gupta (c)" <gka...@vmware.com<mailto:gka...@vmware.com>>
Subject: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping 
post ONAP stack creation



Hi All,



We have deployed ONAP on Vanilla OpenStack Mitaka (On top of CentOS 7). Using 
the following YAML and env files:

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack-5Ffloat.yaml-3Bh-3D659f94c93b9c5dfae02031ddcae82161ce927318-3Bhb-3Drefs_heads_master=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=0W0Iqz1u4tpxjq-popdh_Dub7VDg8oFWFEzedDoFcQU=-c1dDfM35o9Ih-STMgfXqEGBxtvMeaBGaskuy9V2bAQ=>

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dblob-3Bf-3Dheat_OpenECOMP_onap-5Fopenstack-5Ffloat.yaml-3Bh-3D659f94c93b9c5dfae02031ddcae82161ce927318-3Bhb-3Drefs_heads_master=DwMF-g=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=0W0Iqz1u4tpxjq-popdh_Dub7VDg8oFWFEzedDoFcQU=-c1dDfM35o9Ih-STMgfXqEGBxtvMeaBGaskuy9V2bAQ=>



Once ONAP stack is created, the SDC, MSO and Robot VMs remain accessible till 
they reboot as part of their respective install script execution. The install 
script for each VM is:

1)  SDC - /opt/asdc_install.sh

Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal failed to launch

2017-05-26 Thread PLATANIA, MARCO (MARCO)

Hello Subhash,

The dns_vm is used to resolve FQDN that ONAP components use to talk to each 
other. This is different from the 8.8.8.8 DNS that you specified, which is 
necessary for external routing.

Thanks,
Marco

From:  on behalf of "Arun Arora (c)" 

Date: Friday, May 26, 2017 at 9:08 AM
To: Subhash Kumar Singh , 
"onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch


Hi Subhash,



Pls check of you have /opt/config/public_ip.txt file with floating IP in it.

Also try enabling Ingress in the Security Group for all Ports and CIDR 0.0.0.0/0



The sql insertion is done from portal_vm_init.sh which requires Floating IP and 
it should be accessible from inside the VM. You can also try giving your 
Private IP as well. But it will wipe out the next time you create ONAP stack 
via HEAT.



Thanks,

Arun



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Subhash Kumar Singh
Sent: Friday, May 26, 2017 5:45 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch



Hi,



We are trying to bring up the ONAP setup on the vanilla Openstack (5-node) 
using provided HEAT template [1]. We would like to request for the 
clarification for the following issues :



1.  OpenECOMP HEAT template is having resource named dns_vm. what is the 
purpose of this vm?

As part of heat stack creation, we have used 8.8.8.8 as dns server in the 
heat environment file for dns_list & external_dns.

And we noted that some specific dns entries are specified in the wiki [2].  
 if we are accessing the resources using the IP address , are these DNS entries 
are required?



2.  After successful stack creation, We are not able to access the portal ( 
http://https://urldefense.proofpoint.com/v2/url?u=http-3A__-253cportal-5Fvm-3A8989_EcompPORTAL_login.html=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=95EagLLrI_2KeETmgmJD_o0J3siJHxzRpujsoGhJ98Q=ODxQFdVn82qb2ow40Op4ACoe9NbTItqJFRGh1q8a6QQ=>).
 It is throwing exception [3] related to mysql connection.

We have checked the docker instance in the onap-portal both the dockers are 
up but mysql is not accessible from the outside of docker.



$ sudo docker ps

CONTAINER IDIMAGE   COMMAND  CREATED
 STATUS  PORTS  
  NAMES

0db86c4be8c2ep:1610-1   "/PROJECT/OpenSour..."   2 hours ago
 Up 2 hours  0.0.0.0:8006->8005/tcp, 0.0.0.0:8010->8009/tcp, 
0.0.0.0:8989->8080/tcp   1610-1

591c9e998306ecompdb:portal  "docker-entrypoint..."   2 hours ago
 Up 2 hours 
  ecompdb_portal



So it seems like the portal is not accessible because mysql is not accessible.





Kindly help to fix these issues, to test the sample VNF using ONAP.





[1]  
https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=024dd2f90a2f36b09497a5d93dda52ae58294dc9;hb=refs/heads/master



[2] 
https://wiki.onap.org/display/DW/Tutorial%3A+Accessing+the+ONAP+Portal



[3] 
http://paste.openstack.org/show/610720/



--

Thanks and Regards,

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

Re: [onap-discuss] Login Credentials for portal vm

2017-05-26 Thread PLATANIA, MARCO (MARCO)

You have root access: ssh –i  private_key root@IP_ADDRESS

From:  on behalf of "EFRAT, ELHAY" 

Date: Friday, May 26, 2017 at 1:22 AM
To: Viswa KSP , lokesh r 

Cc: "onap-discuss@lists.onap.org" 
Subject: Re: [onap-discuss] Login Credentials for portal vm

SSH -i keyfromopenstack cloud@ip

From: onap-discuss-boun...@lists.onap.org on behalf of Viswa KSP
Sent: Friday, May 26, 2017 5:17:30 AM
To: lokesh r
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Login Credentials for portal vm
It depends on the cloud image that you had chosen for Ubuntu 14/16 as per your 
environment. Default login for Ubuntu clould image is via ssh keypair only.

You can also login via keypair that you had given in your HEAT / env file .

BR,
Viswa

On May 26, 2017 10:26 AM, "lokesh r" 
> wrote:
Hi,

 What is default login credentials to login portal vm ?

[nline image 1]

Thanks,
Lokesh.

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

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] Login Credentials for portal vm

2017-05-26 Thread PLATANIA, MARCO (MARCO)

Hi Lokesh,

Login is possible via public/private key. Please, use the terminal instead of 
the OpenStack console and use the private key associated to the public key that 
you set in the heat template for ONAP installation.

Thanks,
Marco

From:  on behalf of lokesh r 

Date: Friday, May 26, 2017 at 12:56 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Login Credentials for portal vm

Hi,

 What is default login credentials to login portal vm ?

[nline image 1]

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

Re: [onap-discuss] Portal VM: Nameserver entry appends in /etc/resolv.conf on each execution of portal_install.sh

2017-05-26 Thread PLATANIA, MARCO (MARCO)

Hello Arun,

That instruction is in portal_install.sh, which runs only once when the VM is 
created. If you reboot the VMs multiple times, only portal_vm_init.sh will run, 
which is not supposed to update resolv.conf.

Thanks,
Marco

From:  on behalf of "Arun Arora (c)" 

Date: Friday, May 26, 2017 at 8:16 AM
To: "onap-discuss@lists.onap.org" 
Cc: "Kapil Gupta (c)" 
Subject: [onap-discuss] Portal VM: Nameserver entry appends in /etc/resolv.conf 
on each execution of portal_install.sh


Hi All,



We have deployed ONAP on Vanilla OpenStack Mitaka (On top of CentOS 7). Using 
the following YAML and env files:

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master





When troubleshooting in Portal VM, we see that there were multiple nameserver 
entries with same IP address (DNS VM) present in /etc/resolv.conf . This entry 
is appended in /etc/resolv.conf on each execution of /opt/portal_install.sh 
which contains the following code:

echo "nameserver "$DNS_IP_ADDR >> /etc/resolvconf/resolv.conf.d/head



After executing the script 6-7 times the traffic to Internet timeouts due to 
multiple nameserver entries for DNS VM. FYI, We verified recursion: yes in DNS 
VM.



If this is an issue how can I contribute a patch for the fix.



Thanks & Regards,

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

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

2017-05-26 Thread PLATANIA, MARCO (MARCO)

Hello Arun,

Some components need to know their public IP address. This is retrieved in 
_vm_init.sh (i.e. policy, sdc). We use this command:
ifconfig eth0 | grep "inet addr" | tr -s ' ' | cut -d' ' -f3 | cut -d':' -f2

Because Ubuntu 16.04 VMs have a different vNIC name, as you said ensX, we 
changed the interface name in those VMs to reflect the usual case. We didn’t 
see any problem after rebooting the VMs. Thank you for letting us know.

I think the problem is not in the vNIC per se, but in the grub file that gets 
modified. That prevents correct start up. Could you please attach the original 
grub file?

Thanks,
Marco

From:  on behalf of "Arun Arora (c)" 

Date: Friday, May 26, 2017 at 8:15 AM
To: "onap-discuss@lists.onap.org" 
Cc: "Kapil Gupta (c)" 
Subject: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping 
post ONAP stack creation


Hi All,



We have deployed ONAP on Vanilla OpenStack Mitaka (On top of CentOS 7). Using 
the following YAML and env files:

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master

https://gerrit.onap.org/r/gitweb?p=demo.git;a=blob;f=heat/OpenECOMP/onap_openstack_float.yaml;h=659f94c93b9c5dfae02031ddcae82161ce927318;hb=refs/heads/master



Once ONAP stack is created, the SDC, MSO and Robot VMs remain accessible till 
they reboot as part of their respective install script execution. The install 
script for each VM is:

1)  SDC - /opt/asdc_install.sh

2)  MSO - /opt/mso_install.sh

3)  Robot - /opt/robot_install.sh



We found that in each script the following line is written which changes the 
NIC interface name from ens[x] to eth0

sed -i "s/ens[0-9]*/eth0/g" /etc/network/interfaces.d/*.cfg



Due to this after reboot each VM becomes inaccessible. If the above line is 
commented, the issue does not happen.



We want to know the reason for changing the Interface name.

We searched and found some discussions that the Ubuntu-16.04 does not work well 
with NIC name as ensX however, we didn’t see any such problem.





With Regards,

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

Re: [onap-discuss] Versions to use for ONAP

2017-05-24 Thread PLATANIA, MARCO (MARCO)

Josef,

Please use the following parameters in the heat template:

artifacts_version: 1.1.0-SNAPSHOT
docker_version: 1.0-STAGING-latest
gerrit_branch: release-1.0.0
dcae_code_version: 1.0.0

Thanks,
Marco

From:  on behalf of Josef Reisinger 

Date: Wednesday, May 24, 2017 at 9:09 AM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] Versions to use for ONAP

Folks,

I am in the process to re-create the ONAP stack and wonder which version of 
artifacts/docker/gerrit-branchto use.

I know that there is an 1.1-STAGING-latest version of the docker images, which 
works better in case of VID. Should I stick with 1.0-STAGING-latest in the 
environment file or is it safe/advised to use 1.1-STATING-latest?

Mit freundlichen Grüßen / Kind regards
Josef Reisinger
When wisdom comes to call, there's nobody listening at all - Pendragon / Man Of 
Nomadic Traits

IBM Sales & Distribution, Communications Sector
Certified IT-Architect Telecommunications
IBM Certified Telecommunications Industry ITA
Lehrbeauftragter an der Hochschule Fresenius

IBM Deutschland
Godesberger Allee 127
53175 Bonn Beuel

Phone:+49 151 1426 4559
Mobile:  +49-(0) 151 1426 4559
E-Mail:  josef.reisin...@de.ibm.com






___
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

2017-05-22 Thread PLATANIA, MARCO (MARCO)

Hello Kedar,

At start up, the packet generator VM runs run_traffic_fw_demo.sh, which 
periodically generates traffic of different loads. Typically, it starts with an 
amount of traffic that is in between the acceptable low-water/high-water marks 
(although this line of code is currently commented out for testing purposes). 
Then, periodically the traffic is adjusted so as to violate pre-defined 
thresholds and trigger the closed-loop operations.

The policies we set are:

· High-water mark: 700 packets/10 secs

· Low-water mark: 300 packets/10 secs

The command that APP-C executes against the packet generator when the traffic 
crosses the thresholds is set up in the policy itself, and it simply tells the 
traffic generator to produce 500 packets/10 secs.

The reporting activity is via VES, as you said, and no DMaaP is involved.

Pam, Hector, Lusheng, could you please clarify/confirm that the topics 
mentioned below represent the actual closed-loop message-exchange configuration?

Thanks,
Marco

From: <onap-discuss-boun...@lists.onap.org> on behalf of Kedar Ambekar 
<ake...@techmahindra.com>
Date: Monday, May 22, 2017 at 5:46 AM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Marco,

Thanks for arranging information from policy team, much appreciated ! Using 
kafka-console-consumer.sh, I could receive messages on topic POLICY-CL-MGT.

I am looking for sequence of messages being exchanged between ONAP components 
to demonstrate closed control loop scenario to adjust the traffic generated by 
packet generator. Here is what I have tried to describe the vFW flow by 
referring to a call flow on wiki.


  1.  Packet generator starts with default load which may be on lower side than 
policy configured threshold.
With what rate it starts, what is low threshold , what is high threshold ?


  1.  vFirewall VM has VES client which reports traffic received to DCAE. 
DCAE’s collector collects this information.
I believe this communication happens by VES client invoking REST API on VES 
collector and DMaap is not involved in it. Is it right understanding?


  1.  DCAE publishes ‘low load’ event on DMaap bus which is received on Policy 
Engine.
I believe this message is on topic DCAE-CL-EVENT.


  1.  Policy engine takes action based on defined rules & publishes ‘increase 
load’ event on the bus which is received by APP-C.
I believe this message is on topic POLICY-CL-MGT.


  1.  APP-C talks to honeycomb agent on packet generator and instructs it to 
increase load.
Where to see these NETCONF / RESTCONF commands ? What is APPC-CL topic for ?


  1.  Eventually, once the threshold is reached, DCAE publishes ‘high load’ 
event on DMaap bus. This event is received by Policy Engine.
I believe this message is on topic DCAE-CL-EVENT.


  1.  Policy Engine takes action based on defined rules & publishes ‘decrease 
load’ event on bus. This event is received by APP-C.
I believe this message is on topic POLICY-CL-MGT.


  1.  APP-C talks to honeycomb agent on packet generator and tells to decrease 
the load.

Where to see these NETCONF / RESTCONF commands ?

So the flow is VES events -- DCAE-CL-EVENT -- POLICY-CL-MGT – NETCONF -- VES 
events -- DCAE-CL-EVENT -- POLICY-CL-MGT – NETCONF -- VES events ….  ?
From: PLATANIA, MARCO (MARCO) [mailto:plata...@research.att.com]
Sent: Friday, May 19, 2017 8:15 PM
To: Kedar Ambekar <ake...@techmahindra.com>; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hello Kedar,

This is what I received from Policy team about communication monitoring:

“The best way to monitor Policy during Closed Loop is to subscribe to our 
POLICY-CL-MGT topic (may have another name that is configurable).”

“With regards to the logs in the drools container, see 
$POLICY_HOME/logs/network.log.   I think that will capture all FW messages 
interaction, For the LB case, the REST interactions with AAI/MSO REST will go 
to the .out file, they are not captured yet in the network.log (it will at some 
point).”

If you need further assistance, please feel free to reach out to Policy team 
directly (some contacts here: 
https://wiki.onap.org/pages/viewpage.action?pageId=3246903<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D3246903=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0=B4eZeKD7opLm3-XhQqqHOfSSoaFKGsCXtbQ75g0gpwg=c9ca-OoFmxU1bVuVb34aaq56E1UCpxPKO9URYPwQ1RQ=>
 ).

Thanks,
Marco


From: 
<onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>>
 on behalf of Kedar Ambekar 
<ake...@techmahindra.com<mailto:ake...@techmahindra.com>>
Date: Friday, May 19, 2017 at 8:37 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@lists.onap.org<

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

2017-05-19 Thread PLATANIA, MARCO (MARCO)

Hello Kedar,

This is what I received from Policy team about communication monitoring:

“The best way to monitor Policy during Closed Loop is to subscribe to our 
POLICY-CL-MGT topic (may have another name that is configurable).”

“With regards to the logs in the drools container, see 
$POLICY_HOME/logs/network.log.   I think that will capture all FW messages 
interaction, For the LB case, the REST interactions with AAI/MSO REST will go 
to the .out file, they are not captured yet in the network.log (it will at some 
point).”

If you need further assistance, please feel free to reach out to Policy team 
directly (some contacts here: 
https://wiki.onap.org/pages/viewpage.action?pageId=3246903 ).

Thanks,
Marco


From: <onap-discuss-boun...@lists.onap.org> on behalf of Kedar Ambekar 
<ake...@techmahindra.com>
Date: Friday, May 19, 2017 at 8:37 AM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

Hi Daniel, Marco,

It appears that the robot script run for demo.sh appc is more specific for vFW.

In case if vLB, as packetGenerator VM is part of different Heat stack, the 
robot script can’t find key vpg_name_0 in the dictionary. Also, I believe it 
will fail further for vpg_private_ip_1.

I gave a try by making below small changes (as APPC is not involved in vLB 
demo)  in demo_preload.robot as below.

Original :
${vpg_name_0}=Get From Dictionary${stack_info}vpg_name_0
${vpg_public_ip}=Get Server Ip${server_list}${stack_info}   
vpg_name_0network_name=public
${vpg_oam_ip}=Get From Dictionary${stack_info}vpg_private_ip_1
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_oam_ip}

Changed:
Declared a variable vpg_name_0 with the name of my packet generator VM from 
different stack.
Declared a variable vpg_public_ip with public IP of my packet generator VM from 
different stack.
${appc}=Create Mount Point In APPC${vpg_name_0}${vpg_public_ip}

With that, though I am not sure the impact of above change yet,  I could make 
the demo.sh appc step pass.

Now, can I know how to verify the closed control loop ? How to see messages 
exchanged on Message Bus for both the use cases ?

Appreciate some write-up on verification of both the cases !!

From: Kedar Ambekar
Sent: Friday, May 19, 2017 10:22 AM
To: onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] Query on vlb_ipaddr parameter of vLB usecase

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.

[id:image002.png@01D2D0CA.C66625C0]


From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Friday, May 19, 2017 9:31 AM
To: PLATANIA, MARCO 
<plata...@research.att.com<mailto:plata...@research.att.com>>; ROSE, DANIEL V 
<dr6...@att.com<mailto:dr6...@att.com>>; Kedar Ambekar 
<ake...@techmahindra.com<mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org<mailto: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> 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO
Sent: Friday, May 19, 2017 12:29 AM
To: ROSE, DANIEL V <dr6...@att.com<mailto:dr6...@att.com>>; Kedar Ambekar 
<ake...@techmahindra.com<mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org<mailto: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" <dr6...@att.com<mailto:dr6...@att.com>>
Date: Thursday, May 18, 2017 at 6:09 PM
To: Kedar Ambekar <ake...@techmahindra.com<mailto:ake...@techmahindra.com>>, 
"onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
<onap-discuss@l

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

2017-05-18 Thread 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" <dr6...@att.com>
Date: Thursday, May 18, 2017 at 6:09 PM
To: Kedar Ambekar <ake...@techmahindra.com>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>, "PLATANIA, MARCO (MARCO)" 
<plata...@research.att.com>
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<https://urldefense.proofpoint.com/v2/url?u=https-3A__mycloud.rackspace.com_cloud_1033910_servers-23stacks_orchestration-252CcloudOrchestration-252CIAD_K-2DdemoVLB-2DModule-252F2f720d88-2D287a-2D4628-2D9c7e-2D2bb5df5ba99c_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=UDVCsf_QNH-oQ7ZWHrwg3LxeKoHYbq84kMssY3SUTWw=CVMZ8bDOY7cdXCVesdhK1x37QEfbth06co2E0yU7ug4=>.

3.   In Add VF Module, I chose base_vlb and created a VF Module with name 
K-demoVLB-Module<https://urldefense.proofpoint.com/v2/url?u=https-3A__mycloud.rackspace.com_cloud_1033910_servers-23stacks_orchestration-252CcloudOrchestration-252CIAD_K-2DdemoVLB-2DModule-252F2f720d88-2D287a-2D4628-2D9c7e-2D2bb5df5ba99c_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=UDVCsf_QNH-oQ7ZWHrwg3LxeKoHYbq84kMssY3SUTWw=CVMZ8bDOY7cdXCVesdhK1x37QEfbth06co2E0yU7ug4=>.
 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__mycloud.rackspace.com_cloud_1033910_servers-23stacks_orchestration-252CcloudOrchestration-252CIAD_K-2DdemoVLB-2DPackGen-252F5ab12078-2Dcd09-2D4a29-2Db08a-2D0c65368cc728_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=UDVCsf_QNH-oQ7ZWHrwg3LxeKoHYbq84kMssY3SUTWw=MFlNerNQgTp5cuAjAbvjc5Z_qWjn5_WwjjBDjXBQEjc=>
 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__mycloud.rackspace.com_cloud_1033910_servers-23stacks_orchestration-252CcloudOrchestration-252CIAD_K-2DdemoVLB-2DPackGen-252F5ab12078-2Dcd09-2D4a29-2Db08a-2D0c65368cc728_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=UDVCsf_QNH-oQ7ZWHrwg3LxeKoHYbq84kMssY3SUTWw=MFlNerNQgTp5cuAjAbvjc5Z_qWjn5_WwjjBDjXBQEjc=>
 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<https://urldefense.proofpoint.com/v2/url?u=https-3A__mycloud.rackspace.com_cloud_1033910_servers-23stacks_orchestration-252CcloudOrchestration-252CIAD_K-2DdemoVLB-2DPackGen-252F5ab12078-2Dcd09-2D4a29-2Db08a-2D0c65368cc728_=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=UDVCsf_QNH-oQ7ZWHrwg3LxeKoHYbq84kMssY3SUTWw=MFlNerNQgTp5cuAjAbvjc5Z_qWjn5_WwjjBDjXBQEjc=>
 or K-demoVLB-Module ?

The architecture diagram on wiki for vLB 
(https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Installing-2Band-2BRunning-2Bthe-2BONAP-2BDemos=DwMGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=UDVCsf_QNH-oQ7ZWHrwg3LxeKoHYbq84kMssY3SUTWw=9Z9zuJ2IgC7GfFVwLRL6Qce_I0ra8ZFR7FIKL4VXMZw=>)
 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 <ake...@techmahindra.com<mailto:ake...@techmahindra.com>>; 
onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>
Subje

Re: [onap-discuss] DCAE controller fails to find flavor even when it exists

2017-05-16 Thread PLATANIA, MARCO (MARCO)

Hello Rashmi,

The configuration you are using refers to the stable release 1.0.0, which is 
fully tested and supported in Rackspace. DCAE release-1.0.0 doesn’t work in 
OpenStack. DCAE 1.1.0 does, still with some caveat as explained before. 
However, ONAP version 1.1.0 hasn’t been fully tested yet, so it may still 
present some issues.

As such, I would suggest to install the stable release (1.0.0). Note, however, 
that some parameters in your environment file don’t seem set up correctly.

For release 1.0.0 (stable), if you are using the heat template in the 
release-1.0.0 branch:

· artifacts_version: 1.0.0

· docker_version: 1.0-STAGING-latest

· gerrit_branch: release-1.0.0

· gitlab_branch: master

Otherwise, if you want to use the new heat template in the Gerrit master 
branch, still with release-1.0.0 docker images, please set:

  *   artifacts_version: 1.1.0-SNAPSHOT
  *   docker_version: 1.0-STAGING-latest
  *   gerrit_branch: release-1.0.0
  *   gitlab_branch: master
  *   dcae_code_version: 1.0.0

Finally, if you want to try the code that is currently in the Gerrit master 
branch (unstable release), please use the new Heat template and set the 
parameters in the environment file as follows:

  *   artifacts_version: 1.1.0-SNAPSHOT
  *   docker_version: 1.1-STAGING-latest
  *   gerrit_branch: master
  *   gitlab_branch: master
  *   dcae_code_version: 1.1.0

For a description of the new Heat templates and the differences among them, 
please refer to the wiki: 
https://wiki.onap.org/display/DW/ONAP+Installation+in+Vanilla+OpenStack

One more thing: there is “gerrit_branch” which refers to ONAP as a whole (it 
can be “release-1.0.0” or “master”, depends on what environment you want to 
build), and “gitlab_branch” which is internally used by DCAE and should always 
be set to “master” (it refers to some other Snapshot repo).

Thanks,
Marco


From: "Pujar, Rashmi" <rashmi.pu...@bell.ca>
Date: Tuesday, May 16, 2017 at 1:03 PM
To: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>, 
"onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] DCAE controller fails to find flavor even when it 
exists

Hello Marco,

Yes, I am deploying the release-1.0.0 code with the Openstack heat templates 
and env files.

-  Docker-version: 1.0-STAGING-latest

-  DCAE-VERSION: 1.0.0

-  Git_branch version to clone the dcae/demo project in the cloud_init 
file: release-1.0.0
Do I have to upgrade to 1.1.0 to get past the issue I am seeing? What is the 
recommended version of ONAP to get a deployment running and validate it?

Thanks,
Rashmi

From: "PLATANIA, MARCO (MARCO)" <plata...@research.att.com>
Date: Tuesday, May 16, 2017 at 12:36 PM
To: "Pujar, Rashmi" <rashmi.pu...@bell.ca>, "onap-discuss@lists.onap.org" 
<onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] DCAE controller fails to find flavor even when it 
exists

Hello Rashmi,

DCAE controller (in Gerrit master branch) requires onap_openstack_nofloat.yaml 
Heat template to correctly start up in vanilla OpenStack. While porting DCAE to 
vanilla OpenStack is still a work in progress, we were able to create the 
expected analytics platform with the controller defined in the DCAE section of 
that template.

From the error below, it seems to me that the parameters you are using refer to 
the Rackspace configuration (VM image names, flavors, …). In the env file, 
please set:

· artifacts_version: 1.1.0-SNAPSHOT

· docker_version: 1.1-STAGING-latest

· gerrit_branch: master

· cloud_env: openstack_nofloat

· dcae_base_environment: 2-NIC

· dcae_code_version: 1.1.0

I anticipate that the creation of the analytics platform (that DCAE does off 
the Heat template) is pretty slow at this time (it may take a couple of hours 
for the entire stack to come up – sorry for the inconvenience).

Thanks,
Marco

From: <onap-discuss-boun...@lists.onap.org> on behalf of "Pujar, Rashmi" 
<rashmi.pu...@bell.ca>
Date: Tuesday, May 16, 2017 at 12:06 PM
To: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: [onap-discuss] DCAE controller fails to find flavor even when it exists

Hello Devs!

I am trying to get DCAE controller running and have it spin up the rest of the 
VMs in my Openstack setup. So far I have been successful in getting the DCAE 
controller instance communicating fine with Openstack (gets the token, 
endpoints and the compute/glance/network resources and updates the Jetty server 
endpoints). The flavors and the images needed by the DCAE VMs have been created 
in OS. However, DCAE controller fails to deploy the VM citing missing flavor as 
the reason for failure.

What is the DCAE controller endpoint where it queries for the flavor name? I am 
looking at: http://localhost:9998/resour

Re: [onap-discuss] DCAE controller fails to find flavor even when it exists

2017-05-16 Thread PLATANIA, MARCO (MARCO)

Hello Rashmi,

DCAE controller (in Gerrit master branch) requires onap_openstack_nofloat.yaml 
Heat template to correctly start up in vanilla OpenStack. While porting DCAE to 
vanilla OpenStack is still a work in progress, we were able to create the 
expected analytics platform with the controller defined in the DCAE section of 
that template.

From the error below, it seems to me that the parameters you are using refer to 
the Rackspace configuration (VM image names, flavors, …). In the env file, 
please set:

· artifacts_version: 1.1.0-SNAPSHOT

· docker_version: 1.1-STAGING-latest

· gerrit_branch: master

· cloud_env: openstack_nofloat

· dcae_base_environment: 2-NIC

· dcae_code_version: 1.1.0

I anticipate that the creation of the analytics platform (that DCAE does off 
the Heat template) is pretty slow at this time (it may take a couple of hours 
for the entire stack to come up – sorry for the inconvenience).

Thanks,
Marco

From:  on behalf of "Pujar, Rashmi" 

Date: Tuesday, May 16, 2017 at 12:06 PM
To: "onap-discuss@lists.onap.org" 
Subject: [onap-discuss] DCAE controller fails to find flavor even when it exists

Hello Devs!

I am trying to get DCAE controller running and have it spin up the rest of the 
VMs in my Openstack setup. So far I have been successful in getting the DCAE 
controller instance communicating fine with Openstack (gets the token, 
endpoints and the compute/glance/network resources and updates the Jetty server 
endpoints). The flavors and the images needed by the DCAE VMs have been created 
in OS. However, DCAE controller fails to deploy the VM citing missing flavor as 
the reason for failure.

What is the DCAE controller endpoint where it queries for the flavor name? I am 
looking at: http://localhost:9998/resources/openstack/locations/${ZONE}/flavors 
and it has the entry. Is there any other endpoint to verify?
Any insights to debug this would be helpful.

org.openecomp.ncomp.sirius.manager.Jetty8ClientException: HTTP Request Failed: 
URL: http://localhost:9998/resources/services/vm-docker-host-1 code:500 
msg:operation failed: deploy {   "exception": "java.lang.RuntimeException: No 
flavor with name '8 GB Performance'",   "directory": 
"/opt/app/dcae-controller-platform-server",   "user": "root",   "hostname": 
"7493a368c7ff",   "port": "9998",   "class": "DcaePlatformController",   
"action": "deploy",   "request": {"instanceName": "z1"},   "context": { 
"remoteIp": "127.0.0.1", "user": "console", "parameters": {}, 
"path": "/resources/services/vm-docker-host-1", "requestId": 
"1494949479518:29"   } } 


Error 500 operation failed: deploy
{
  "exception": "java.lang.RuntimeException: No flavor with name '8 GB 
Performance'",
  "directory": "/opt/app/dcae-controller-platform-server",
  "user": "root",
  "hostname": "7493a368c7ff",
  "port": "9998",
  "class": "DcaePlatformController",
  "action": "deploy",
  "request": {"instanceName": "z1"},
  "context": {
"remoteIp": "127.0.0.1",
"user": "console",
"parameters": {},
"path": "/resources/services/vm-docker-host-1",
"requestId": "1494949479518:29"
  }
}


The DCAE controller Jetty8 server endpoint for the locations lists the flavor 
as below:

root@7493a368c7ff:/# curl -X GET -H "Authorization: Basic 
Y29uc29sZTpaakprWWpsbE1qbGpNVEkyTTJJeg==" -H "Content-Type: application/json" 
-H "Accept: application/json" -H "Host: localhost:9998" -H "Cache-Control: 
no-cache" -H "Postman-Token: 654d54f7-78ed-080b-7432-b9721cf3a5b0" 
"http://localhost:9998/resources/openstack/locations/z1;
{
  "lastChanged": "2017-05-16T15:49:28.728+",
  "ceilometerAvailableCapabilites": [],
  "ceilometerUnavailableCapabilites": [],
  "version": "Juno",
  "remoteLocation": "false",
  "remoteLocationName": "z1",
  "allowCreateFlavor": "false",
  "keystoneUrl": "http://x.x.x.x:5000/v2.0;,
  "flavorId": "2",
  "supportsSecurityGroups": "false",
  "supportsFloatingIps": "false",
  "projects": {"onap": .

  "flavors": {

"8 GB Performance": {
  "id": "5",
  "ram": "16384",
  "disk": "160",
  "vcpus": "8",
  "swap": "",
  "rxtx_factor": "1.0",
  "OS_FLV_EXT_DATA_ephemeral": "0",
  "OS_FLV_DISABLED_disabled": "false",
  "os_flavor_access_is_public": "true",
  "links": [
"0",
"1"
  ]
}
  },
  "hypervisors": {}
}
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

1 2 >

1 - 100 of 124 matches

Mail list logo