date:20170529

Hi Kedar,

I previously thought that you were looking at some Logging/Diagnostic 
Information per component (i.e. DCAE, Policy, MSO etc.) so you can track where 
the issue is in the vDNS/vLB flow.

Did you also look at the tutorial?
https://wiki.onap.org/display/DW/Installing+and+Running+the+ONAP+Demos

Best regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Tuesday, May 30, 2017 6:48 AM
To: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] closed loop in vLB doesn't seem to be working

Hi Catherine,

Thanks for reply. I looked into the wiki page you pointed but it doesn't talk 
about vLB use case. This 
README.md
 explains the use case to some extent.

But for my issue, where to look for logs ? Could anyone explain on these lines -

How to verify VES events generated by LB VM ?
How to verify VES events collected by DCAE ?
How to verify policy applied by DCAE ?


Hoe to verify MSO orchestrating spawning a new DNS VM ?

From: Lefevre, Catherine [mailto:cl6...@intl.att.com]
Sent: Monday, May 29, 2017 11:38 PM
To: Kedar Ambekar >; 
onap-discuss@lists.onap.org
Subject: RE: closed loop in vLB doesn't seem to be working

Hi Kedar,

You can find some Logging/Diagnostic Information looking at the following url:
https://wiki.onap.org/display/DW/Release+Notes+1.0.0+draft

Hope it helps

Best regards
Catherine

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Friday, May 26, 2017 2:48 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] closed loop in vLB doesn't seem to be working

Hi,

I am trying to observe closed loop scenario for vLB use case.


I confirmed with nslookup host1.dnsdemo.openecomp.org *vLoadBalancer_IP* that 
setup is ok.



I increased the traffic on packet generator of vLB  with below command.



curl -X PUT -H "Authorization: Basic YWRtaW46YWRtaW4=" -H "Content-Type: 
application/json" -H "Cache-Control: no-cache" -d '{"pg-streams":{"pg-stream": 
[{"id":"dns1", "is-enabled":"true"}, {"id":"dns2", 
"is-enabled":"true"},{"id":"dns3", "is-enabled":"true"},{"id":"dns4", 
"is-enabled":"true"},{"id":"dns5", "is-enabled":"true"}]}}' "http://localhost 
:8183/restconf/config/sample-plugin:sample-plugin/pg-streams"

After above command, I expect an instance of demovlbdns VM to get spawned under 
heat stack of vLB. I don't see that happening.

I also confirmed by installing a monitoring agent on demovlbdns that it 
actually gets more traffic.

Can anyone tell how to verify the logs of closed control loop across the 
components of ONAP ? Which logs to refer to find out the problem ?

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

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

[onap-discuss] List of Openstack services in ONAP

2017-05-29 Thread chethan m

Hi All,
I am a newbie in ONAP and need answer for a very basic question.
I was going through the wiki , while I found that HEAT is one of the
openstack services used in ONAP.
I also saw that VES collectory uses Monasca, Vitrage and Congress etc,

I did not get other services of openstack associated with ONAP for basic
things to compute, storage and network services .
Please help me understand.

Thx,
Chethan Mahadev
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] ONAP Architecture subcommittee kickoff

2017-05-29 Thread Lingli Deng

Hi Andrei,

 

You can find the information on the modeling project proposal wiki page as
follows:

 

Collaboration:

*Meeting every wed 9:00/10:00 EDT, 6:00/7:00 PDT, 15:00/16:00 CET,
9:00/10:00PM Beijing 

*IRC -
https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23onap-modeling 

 

Lingli

 

From: Andrei Kojukhov [mailto:andrei.kojuk...@amdocs.com] 
Sent: 2017年5月27日 16:01
To: Lingli Deng ; 'Christopher Donley (Chris)'
; onap-...@lists.onap.org;
onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] ONAP Architecture subcommittee kickoff

 

Hi Lingli,

 

Where can I find the info about the modelling weekly calls?

 

Tks,

 

Andrei

 

From: onap-tsc-boun...@lists.onap.org

[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Lingli Deng
Sent: Saturday, May 27, 2017 2:55 AM
To: 'Christopher Donley (Chris)'  >; onap-...@lists.onap.org
 ; onap-discuss@lists.onap.org
 
Subject: Re: [onap-tsc] ONAP Architecture subcommittee kickoff

 

Hi Chris,

 

Thanks for the arrangements. 

 

I am interested to join but found a conflict with modeling weekly calls.

Will the suggested time slot be used for subsequent routine calls or is it
only a one-time suggestion?

Since I expect several people including myself to be regularly attending
both meeting series, would you consider the possibility that we might
reschedule it to another slot?

 

Thanks again,

Lingli

 

From: onap-tsc-boun...@lists.onap.org

[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Christopher Donley
(Chris)
Sent: 2017年5月27日 7:44
To: onap-...@lists.onap.org  ;
onap-discuss@lists.onap.org  
Subject: [onap-tsc] ONAP Architecture subcommittee kickoff

 

Dear ONAP community,

 

This is a call-for-participation message for our newly created architecture
subcommittee.

 

We will have a kickoff meeting next Tuesday, May 30 at 1500 UTC.
Preliminary agenda includes:

*   Introductions
*   Discuss subcommittee goals, roles, purpose,
processes/tools/communication mechanisms, and formation next steps
*   Recurring meeting dates/times
*   Discuss the starting point and open issues
(https://wiki.onap.org/download/attachments/3245203/ONAP%20Architecture%20Ev
olution%2005022017_v7.pptx?version=1

=1493761356000=v2)
*   As time permits, continue the SO-APP-C-VF-C discussion 

 

 

For those interested in joining, here are the logistics:

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/525972941

 

Or iPhone one-tap (US Toll):  +16465588656,525972941# or
+14086380968,525972941#

 

Or Telephone:

Dial: +1 646 558 8656 (US Toll) or +1 408 638 0968 (US Toll)

Meeting ID: 525 972 941

International numbers available:
https://zoom.us/zoomconference?m=TTavi4JgYzPQg9seHf6L8GWCn-g6ehUy

 

Chris

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] Exposing a port on SDNC ODL container

2017-05-29 Thread FREEMAN, BRIAN D

The docker-compose file is under the oam repository

~[build=path]/sdnc/oam/installation/src/main/yaml/docker-compose.yml

I believe docker requires you to remove the containers and re-build them 
“docker-compose up -d” to see the new ports but I may be wrong.

You may also need to expose ports in the Dockerfile for the sdnc container 
which is under sdnc/oam/installation/sdnc/src/main/docker/Dockerfile


Brian





From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Abdelmuhaimen Seaudi
Sent: Saturday, May 27, 2017 7:49 PM
To: ROSE, DANIEL V 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Exposing a port on SDNC ODL container

Hi.

The sdnc_contoller_container has exposed port 8282 --> 8181.

How can I add another exposed port, for example 4189 --> 4189 to allow routers 
to synchronize with the ODL in the running sdnc_controller_container ?

Do I need to shutdown the sdnc_controller_container and rerun it again with 2 
exposed ports 8282:8181 and 4189:4189 ?

If yes, what is the full command to run the sdnc_controller_container ?

The sdnc_vm_init.sh script shows only "/opt/docker/docker-compose up -d", so I 
don't know what was the full command to run the sdnc_controller_container.

root@vm1-sdnc:~# docker container list
CONTAINER IDIMAGE   COMMAND 
 CREATED STATUS  PORTS NAMES
86092805e713openecomp/dgbuilder-sdnc-image:latest   "/bin/bash -c 'cd 
..."   41 hours agoUp 41 hours 0.0.0.0:3000->3100/tcp
sdnc_dgbuilder_container
4caa9aefae1dopenecomp/admportal-sdnc-image:latest   "/bin/bash -c 'cd 
..."   41 hours agoUp 41 hours 0.0.0.0:8843->8843/tcp
sdnc_portal_container
885c56b1b1d9openecomp/sdnc-image:latest 
"/opt/openecomp/sd..."   41 hours agoUp 41 hours 
0.0.0.0:8282->8181/tcpsdnc_controller_container
fdbdfc8aa306mysql/mysql-server:5.6  "/entrypoint.sh 
my..."   41 hours agoUp 41 hours 0.0.0.0:32768->3306/tcp   
sdnc_db_container

Abdelmuhaimen Seaudi, CCIE # 25265
Email: asea...@gmail.com
Skype: aseaudi
LinkedIn: 
www.linkedin.com/in/aseaudi
Telephone: +2012 84644 733


On Sun, May 28, 2017 at 12:03 AM, ROSE, DANIEL V 
> wrote:
It runs on docker so you would also need to expose the port in docker after you 
install it

On May 27, 2017, at 4:13 PM, Abdelmuhaimen Seaudi 
> wrote:
Hi.

I want to install the BGPPCEP feature on the ODL running in a container on the 
SDNC VM.

This means I need to expose the default PCEP port 4189 out of the container so 
that routers can synchronize with the PCE plugin running in ODL.

How can I do that ?

Thanks.

Abdelmuhaimen Seaudi, CCIE # 25265
Email: asea...@gmail.com
Skype: aseaudi
LinkedIn: 
www.linkedin.com/in/aseaudi
Telephone: +2012 84644 733

___
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=2wwdGZ3YcpSivQ2Kio028A=UrenvZ-0k1Sz20stfv9af-tlmNTaSvhf_gQkIPcrR2w=YEw3RtyTNDfB8VybL8nRPvxxFM5GSD363k6sQpDHkuQ=

___
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

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) 
Cc: onap-discuss@lists.onap.org; Kapil Gupta (c) ; Gaurav 
Gupta (c) ; Abhishek Saxena (c) 
; Suresh Babu Nekkalapudi ; 
Ramesh Tammana 
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)" >
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
>
Cc: "onap-discuss@lists.onap.org" 
>, "Kapil Gupta 
(c)" >, "Gaurav Gupta (c)" 
>, "Abhishek Saxena (c)" 
>, Suresh Babu 
Nekkalapudi >, Ramesh 
Tammana >
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)" 
> 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)" >
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" >, 
"PLATANIA, MARCO (MARCO)" 
>, 
"onap-discuss@lists.onap.org" 
>
Cc: "Kapil Gupta (c)" >, "Gaurav 
Gupta (c)" >, "Abhishek 
Saxena (c)" >, 
Suresh Babu Nekkalapudi 
>, Ramesh Tammana 
>
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) 
>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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) 
>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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)

Re: [onap-discuss] Getting started with SDNC/APPC

Hi Nayan,

You can find useful information can be found  

* APP-C - readme.md file
   
https://gerrit.onap.org/r/gitweb?p=appc.git;a=blob;f=README.md;h=9024ed1f4aae36a072ee1f4610920e69ac1eaef5;hb=HEAD

* SDN-C - readme.md files in gerrit under sdnc/
   Here is the one from sdnc/core
   
https://gerrit.onap.org/r/gitweb?p=sdnc/core.git;a=blob;f=README.md;h=50134aea462e07b0f1a29e3f100664b82d1b779a;hb=HEAD


And ONAP Developer Checklist
https://wiki.onap.org/display/DW/ONAP+Developer+Checklist


You could start with the following tasks APPC-4 and SDNC-8 
And/Or you can join their associated project proposals as suggested by Dan

APP-C: https://wiki.onap.org/display/DW/APPC++Project+Proposal
SDN-C: https://wiki.onap.org/display/DW/SDN-C
Common Controller Framework: 
https://wiki.onap.org/display/DW/Common+Controller+Framework

Best regards
Catherine

-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Monday, May 29, 2017 8:32 PM
To: n.deshm...@samsung.com
Cc: onap-discuss@lists.onap.org; BRADY, PATRICK D 
Subject: Re: [onap-discuss] Getting started with SDNC/APPC

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

Just because stuff is assigned in jira doesn't mean all work is done. Please 
check out the project page for sdnc appc or common controller franework for the 
roadmap for release 1. The stuff in jira is just the work that has been defined 
very tightly

> On May 28, 2017, at 9:49 PM, Nayan Deshmukh  wrote:
> 
> Hello all,
> 
> I wanted to contribute to ONAP controllers. I was able to clone and build the 
> code successfully. Most of the easiers tasks on JIRA are already assigned. 
> Can you please suggest some smaller code cleanup/refactor tasks which could 
> get me started. This is my first time working on the network stack. 
> 
> Also can you tell me about the specifics of the dev environment that you use 
> to work on the individual modules.
> 
> Thank You.
> 
> Cheers,
> Nayan Deshmukh.
> ___
> 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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=JSoGHQXbYQsIstia4P2xBKtL8MCfXMvzJxyjGF5X-8Y=RnmywnTRj_hz9fPTKXa5d1NcZMDtVSYsbVKUrmheEhg=
>  
___
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=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=kpgcKJjBG5JO6mrqxg88LnkcsZr21awWLpAUBpfN8As=tX8nx8a1XdQsPRtfSYpS6o61RkKihykXseapEKLhftc=
 
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Does ONAP support Multi-tenant Openstack deployment?

2017-05-29 Thread ROSE, DANIEL V

Onap supports multi tenant deployment as well as multisite. That is the onap
franework can be installed in one tenant or site while the vnfs are deployed on
another. We also have the ability to have regions and/or tenants for vnf
deployement. This is defined by something call lcp in mso and there is a
clouds.yaml that holds all these combinations. The heat template we put out for
the demo does not however have the full capabilities exposed as its meant to be
a simple tutorial

On May 29, 2017, at 2:19 PM, Viswa KSP
> wrote:

Hello,

I would like to know if ONAP supports multi-tenant deployment model. If yes,
please point me to configuration guide accordingly.

More details:

If you look at other ETSI compliant NFV-Os like OSM, OpenBaton, there is a
specific configuration step, where-in we will have to specify a VIM account
with tenant name, keystone URL. mgmt IP etc. This space will be used by the
orchestra tor during deployment.

While instantiating a NSD, we can dynamically at run-time specify which VIM
account to use.

While I understand that ONAP currently not multi-vim complaint ( only supported
with Openstack ), I would like to know if multi-tenant model is supported.

Assume I have 2 tenant spaces ( in 2 different openstack sites - to complicate
the problem statement further ) and I would like to instantiate service 1 in
tenant 1 and service 2 in tenant 2, how should I go about in realising this
requirement?

BR,
Viswa
___
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=2wwdGZ3YcpSivQ2Kio028A=8aOVDebX_cac4i_WaD2VI1ZaKYZWTLkLffNt5I5HUgo=MSoC0S256pAGmVajoRWmhow6Wr-4B4vNBOr0W_ffXgE=
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Getting started with SDNC/APPC

2017-05-29 Thread ROSE, DANIEL V

Just because stuff is assigned in jira doesn't mean all work is done. Please 
check out the project page for sdnc appc or common controller franework for the 
roadmap for release 1. The stuff in jira is just the work that has been defined 
very tightly

> On May 28, 2017, at 9:49 PM, Nayan Deshmukh  wrote:
> 
> Hello all,
> 
> I wanted to contribute to ONAP controllers. I was able to clone and build the 
> code successfully. Most of the easiers tasks on JIRA are already assigned. 
> Can you please suggest some smaller code cleanup/refactor tasks which could 
> get me started. This is my first time working on the network stack. 
> 
> Also can you tell me about the specifics of the dev environment that you use 
> to work on the individual modules.
> 
> Thank You.
> 
> Cheers,
> Nayan Deshmukh.
> ___
> 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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=JSoGHQXbYQsIstia4P2xBKtL8MCfXMvzJxyjGF5X-8Y=RnmywnTRj_hz9fPTKXa5d1NcZMDtVSYsbVKUrmheEhg=
>  
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Need ONAP webinar slides

2017-05-29 Thread Viswa KSP

Hello,

I would like to use the slides that was presented as part of ONOS
Introduction webinar.
Could you please provide me the link to download the same?

I assume all the materials of ONAP are open-sourced and can be utilised by
public. Please let me know if otherwise.

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

[onap-discuss] Does ONAP support Multi-tenant Openstack deployment?

2017-05-29 Thread Viswa KSP

Hello,

I would like to know if ONAP supports multi-tenant deployment model. If
yes, please point me to configuration guide accordingly.

*More details:*

If you look at other ETSI compliant NFV-Os like OSM, OpenBaton, there is a
specific configuration step, where-in we will have to specify a VIM account
with tenant name, keystone URL. mgmt IP etc. This space will be used by the
orchestra tor during deployment.

While instantiating a NSD, we can dynamically at run-time specify which VIM
account to use.

While I understand that ONAP currently not multi-vim complaint ( only
supported with Openstack ), I would like to know if multi-tenant model is
supported.

Assume I have 2 tenant spaces ( in 2 different openstack sites - to
complicate the problem statement further ) and I would like to instantiate
service 1 in tenant 1 and service 2 in tenant 2, how should I go about in
realising this requirement?

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

Re: [onap-discuss] closed loop in vLB doesn't seem to be working

Hi Kedar,

You can find some Logging/Diagnostic Information looking at the following url:
https://wiki.onap.org/display/DW/Release+Notes+1.0.0+draft

Hope it helps

Best regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kedar Ambekar
Sent: Friday, May 26, 2017 2:48 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] closed loop in vLB doesn't seem to be working

Hi,

I am trying to observe closed loop scenario for vLB use case.


I confirmed with nslookup host1.dnsdemo.openecomp.org *vLoadBalancer_IP* that 
setup is ok.



I increased the traffic on packet generator of vLB  with below command.



curl -X PUT -H "Authorization: Basic YWRtaW46YWRtaW4=" -H "Content-Type: 
application/json" -H "Cache-Control: no-cache" -d '{"pg-streams":{"pg-stream": 
[{"id":"dns1", "is-enabled":"true"}, {"id":"dns2", 
"is-enabled":"true"},{"id":"dns3", "is-enabled":"true"},{"id":"dns4", 
"is-enabled":"true"},{"id":"dns5", "is-enabled":"true"}]}}' "http://localhost 
:8183/restconf/config/sample-plugin:sample-plugin/pg-streams"

After above command, I expect an instance of demovlbdns VM to get spawned under 
heat stack of vLB. I don't see that happening.

I also confirmed by installing a monitoring agent on demovlbdns that it 
actually gets more traffic.

Can anyone tell how to verify the logs of closed control loop across the 
components of ONAP ? Which logs to refer to find out the problem ?

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

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

Re: [onap-discuss] VID VM , MariaDb docker does not remain running

2017-05-29 Thread Elhay Efrat

Please add also
Docker logs {mariadb-docker-id}


From: onap-discuss-boun...@lists.onap.org on behalf of Lefevre, Catherine
Sent: Monday, May 29, 2017 5:59:59 PM
To: Arun Arora (c); onap-discuss@lists.onap.org
Cc: Kapil Gupta (c)
Subject: Re: [onap-discuss] VID VM , MariaDb docker does not remain running

Hi Arun,

Could you please provide some logs, traces in order to better understand your 
current MariaDB issue?

Logging/Diagnostic Information
Application logs:
/opt/app/vid/logs/vid

  *   audit.log for transaction details
  *   application.log for detailed application logs and debugging
  *   debug.log for debugging output
  *   error.log for exception debugging
  *   metrics.log for metrics on transactions
Application server logs:
/usr/local/tomcat/logs/

  *   localhost_access_log.-mm-dd.txt contains access log info
  *   catalina.2017-02-28.log tomcat information
Did you also check the following discussion?
https://lists.onap.org/pipermail/onap-discuss/2017-May/000911.html

Best regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Friday, May 26, 2017 2:16 PM
To: onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
Subject: [onap-discuss] VID VM , MariaDb docker does not remain running


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





After ONAP stack deployment, Mariadb docker inside VID VM starts but is exiting 
after sometime.

Can anyone provide any pointers on why the mariadb docker stops, or is this the 
desired behavior?



Thanks & Regards,

Arun Arora
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] VID VM , MariaDb docker does not remain running

Hi Arun,

Could you please provide some logs, traces in order to better understand your 
current MariaDB issue?

Logging/Diagnostic Information
Application logs:
/opt/app/vid/logs/vid

  *   audit.log for transaction details
  *   application.log for detailed application logs and debugging
  *   debug.log for debugging output
  *   error.log for exception debugging
  *   metrics.log for metrics on transactions
Application server logs:
/usr/local/tomcat/logs/

  *   localhost_access_log.-mm-dd.txt contains access log info
  *   catalina.2017-02-28.log tomcat information
Did you also check the following discussion?
https://lists.onap.org/pipermail/onap-discuss/2017-May/000911.html

Best regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Arun Arora (c)
Sent: Friday, May 26, 2017 2:16 PM
To: onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
Subject: [onap-discuss] VID VM , MariaDb docker does not remain running


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





After ONAP stack deployment, Mariadb docker inside VID VM starts but is exiting 
after sometime.

Can anyone provide any pointers on why the mariadb docker stops, or is this the 
desired behavior?



Thanks & Regards,

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

Re: [onap-discuss] No title

Hi Nayan,



Please take a look at the readme.md file, it will give you some useful 
information about MSO and how to debug it.

https://gerrit.onap.org/r/gitweb?p=mso.git;a=blob;f=readme.md;h=3f9b4518cce67307fe01c6675bc907199b4d5d5f;hb=HEAD



Please note that MSO is interacting with several ONAP components therefore I 
would recommend that you indeed install the entire ONAP in order to trial it 
through the two available use cases i.e. vFirewall, vDNS.



[cid:image001.png@01D2D8B1.D7FD5300]





Hope it helps



Best regards

Catherine



-Original Message-
From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Thursday, May 25, 2017 6:06 PM
To: n.deshm...@samsung.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] No title



*** Security Advisory: This Message Originated Outside of AT ***.

Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.



Someone from can MSO can help you better but we usually don’t use docker in a 
local dev env.





Thanks,

Daniel Rose

ECOMP / ONAP

com.att.ecomp

732-420-7308





-Original Message-

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ?? 

Sent: Thursday, May 25, 2017 4:37 AM

To: onap-discuss@lists.onap.org

Subject: [onap-discuss] No title





Hi all,











I am a newbie to ONAP. I am trying to contribute to mso. I was able to clone 
and build the mso module, though some tests are failing but the code is 
building fine.











I also tried to use the docker-config to run the docker containers on my 
machine. But I am getting the following error when I run deploy.sh





ERROR: Network "dockerconfig_default" needs to be recreated - options have 
changed













Also can you please tell me about the development environment that you use to 
work on MSO. Do I need to setup entire onap to work on mso?













Thank You.













Cheers,





Nayan Deshmukh

___

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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=2wwdGZ3YcpSivQ2Kio028A=rFy1sMuE5PiLhgAtJmGWaa-hpTZus-R3V22CV_zo7PQ=qJdKzydhnP3ueJ4GUNCSJGQ_vnX0PzWuRezjju3NnbM=

___

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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=FIaVZuAgpklv_OAILZz0N1C3Uq_uzwAQFRpzYiVJv54=QP2pzpLcKijGjB6PgT94fmMNoSzA0PC-WuulF1RGbWI=
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-discssus] Tooling for call flow

Hi Eric,

It could be an interesting if people have not the Visio license (or any similar 
tool).
I will try it.

Best regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Friday, May 26, 2017 9:39 PM
To: eric.deb...@orange.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] [onap-discssus] Tooling for call flow

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Ah totally different then what I thought! I cant help much there :)

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

From: eric.deb...@orange.com 
[mailto:eric.deb...@orange.com]
Sent: Friday, May 26, 2017 3:31 PM
To: ROSE, DANIEL V >; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discssus] Tooling for call flow

Hello

I am talking about call flow for use-case description (eg call flow for VoLTE: 
https://wiki.onap.org/download/attachments/3246140/image2017-5-17_18-34-39.png?version=1=149501728=v2
) or for any documentation.

Eric

De : ROSE, DANIEL V [mailto:dr6...@att.com]
Envoyé : mercredi 24 mai 2017 19:58
À : DEBEAU Eric IMT/OLN; 
onap-discuss@lists.onap.org
Objet : RE: [onap-discssus] Tooling for call flow

Hi Eric,

Are you talking about call flows in the model 
(https://wiki.onap.org/display/DW/Service+Design#ServiceDesign-CNCF
 )?

Or are you talking about DGs in sdnc?

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 
eric.deb...@orange.com
Sent: Wednesday, May 24, 2017 3:17 AM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [onap-discssus] Tooling for call flow

Hello

To be able to work on call flow in a collaborative way, I believe that we 
should use a tool based on a description language rather using images.

Is there any guideline within the Linux Foundation for such tooling ?

Within Orange, we developed a cool tool:
https://github.com/Orange-OpenSource/EtherPlant

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.

_



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

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)" 
Date: Monday, May 29, 2017 at 12:27 PM
To: "PLATANIA, MARCO (MARCO)" 
Cc: "onap-discuss@lists.onap.org" , "Kapil Gupta 
(c)" , "Gaurav Gupta (c)" , 
"Abhishek Saxena (c)" , Suresh Babu Nekkalapudi 
, Ramesh Tammana 
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)" 
> 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)" 
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" , "PLATANIA, MARCO (MARCO)" 
, "onap-discuss@lists.onap.org" 

Cc: "Kapil Gupta (c)" , "Gaurav Gupta (c)" 
, "Abhishek Saxena (c)" , 
Suresh Babu Nekkalapudi , Ramesh Tammana 

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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) 
>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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) >; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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: 
>
 on behalf of "Arun Arora (c)" 
>
Date: Friday, May 26, 2017 at 8:15 AM
To: "onap-discuss@lists.onap.org"

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)" 
> 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)" 
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" , "PLATANIA, MARCO (MARCO)" 
, "onap-discuss@lists.onap.org" 

Cc: "Kapil Gupta (c)" , "Gaurav Gupta (c)" 
, "Abhishek Saxena (c)" , 
Suresh Babu Nekkalapudi , Ramesh Tammana 

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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) 
>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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) >; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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: 
>
 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:

Re: [onap-discuss] A certificate issuer

2017-05-29 Thread Ahmad, Munir

Thanks Catherine for the follow-up,

We have resolved this issue by re-pulling changes for A

From: "Lefevre, Catherine" 
Date: Monday, May 29, 2017 at 11:08 AM
To: "Ahmad, Munir" , "onap-discuss@lists.onap.org" 

Subject: RE: [onap-discuss] A certificate issuer


Hi Munir,



I do not know if you have got any feedback regarding your query.

I would like to suggest to take a look at the readme.md file in the 
aai/resources repo

https://gerrit.onap.org/r/gitweb?p=aai/resources.git;a=blob;f=readme.md;h=367867f9542f3a0e1013d5541c9396dacbb85165;hb=HEAD



It gives you some sample about accessing AAI APIs etc


if it does not answer to your query then feel free to post a question on the 
following wiki - http://wiki.onap.org/questions/



Best regards

Catherine



-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ahmad, Munir

Sent: Tuesday, May 02, 2017 5:53 PM

To: onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] A certificate issuer



Hello All,







The robot script /opt/demo.sh init is making a call to A url 
https://urldefense.proofpoint.com/v2/url?u=https-3A__aai.api.simpledemo.openecomp.org-3A8443_aai_v8_cloud-2Dinfrastructure_cloud-2Dregions_cloud-2Dregion_Rackspace_RegionOne=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=IFApZ3Bvh6NXo2hwVBqt4EqsE2oGJA_mH24TQifApzw=







Which results in A throwing an internal error 500 and based on the stack 
trace and wget of the url we need to add the issuer certificate as trusted







Based on my understanding this cert can not be obtained from 
aai.api.simpledemo.openecomp.org. Is the issuer cert available somewhere we can 
download?











Stack trace from A…







Getting the resource...: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__aai.api.simpledemo.openecomp.org-3A8443_aai_v8_cloud-2Dinfrastructure_cloud-2Dregions_cloud-2Dregion_Rackspace_RegionOne=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=IFApZ3Bvh6NXo2hwVBqt4EqsE2oGJA_mH24TQifApzw=



Getting the Resource failed: 500:







org.openecomp.aai.exceptions.AAIException: AAI_7402



   at 
org.openecomp.aai.util.GetResource.getNode(GetResource.java:154)



   at org.openecomp.aai.util.GetResource.main(GetResource.java:89)











output of wget…







wget 
https://urldefense.proofpoint.com/v2/url?u=https-3A__aai.api.simpledemo.openecomp.org-3A8443_aai_v8_cloud-2Dinfrastructure_cloud-2Dregions_cloud-2Dregion_Rackspace_RegionOne=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=IFApZ3Bvh6NXo2hwVBqt4EqsE2oGJA_mH24TQifApzw=



--2017-05-02 15:26:38--  
https://urldefense.proofpoint.com/v2/url?u=https-3A__aai.api.simpledemo.openecomp.org-3A8443_aai_v8_cloud-2Dinfrastructure_cloud-2Dregions_cloud-2Dregion_Rackspace_RegionOne=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=IFApZ3Bvh6NXo2hwVBqt4EqsE2oGJA_mH24TQifApzw=



Resolving aai.api.simpledemo.openecomp.org 
(aai.api.simpledemo.openecomp.org)... 10.0.1.1



Connecting to aai.api.simpledemo.openecomp.org 
(aai.api.simpledemo.openecomp.org)|10.0.1.1|:8443... connected.



ERROR: cannot verify aai.api.simpledemo.openecomp.org's certificate, issued by 
‘/C=US/ST=NJ/L=Bedminster/O=OpenECOMP/OU=simpledemo/CN=OpenECOMP simpledemo 
Server CA X1/emailAddress=simpled...@openecomp.org’:



  Unable to locally verify the issuer's authority.



To connect to aai.api.simpledemo.openecomp.org insecurely, use 
`--no-check-certificate'.













___

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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=s7aYc4p8X2fRiLJMwr6QE0ppboMTAklKR41vyG_VbXc=
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] onap-discuss Digest, Vol 3, Issue 7

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

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)" 
Date: Monday, May 29, 2017 at 6:38 AM
To: "Arun Arora (c)" , "PLATANIA, MARCO (MARCO)" 
, "onap-discuss@lists.onap.org" 

Cc: "Kapil Gupta (c)" , "Gaurav Gupta (c)" 
, "Abhishek Saxena (c)" , 
Suresh Babu Nekkalapudi , Ramesh Tammana 

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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) 
>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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) >; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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: 
>
 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:

Re: [onap-discuss] SDC , MSO and Robot VM were inaccessible via ssh/ping post ONAP stack creation

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)" 
Date: Monday, May 29, 2017 at 5:44 AM
To: "PLATANIA, MARCO (MARCO)" , 
"onap-discuss@lists.onap.org" 
Cc: "Kapil Gupta (c)" 
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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) >; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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: 
>
 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"

Re: [onap-discuss] A certificate issuer

Hi Munir,



I do not know if you have got any feedback regarding your query.

I would like to suggest to take a look at the readme.md file in the 
aai/resources repo

https://gerrit.onap.org/r/gitweb?p=aai/resources.git;a=blob;f=readme.md;h=367867f9542f3a0e1013d5541c9396dacbb85165;hb=HEAD



It gives you some sample about accessing AAI APIs etc


if it does not answer to your query then feel free to post a question on the 
following wiki - http://wiki.onap.org/questions/



Best regards

Catherine



-Original Message-

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Ahmad, Munir

Sent: Tuesday, May 02, 2017 5:53 PM

To: onap-discuss@lists.onap.org

Subject: Re: [onap-discuss] A certificate issuer



Hello All,







The robot script /opt/demo.sh init is making a call to A url 
https://urldefense.proofpoint.com/v2/url?u=https-3A__aai.api.simpledemo.openecomp.org-3A8443_aai_v8_cloud-2Dinfrastructure_cloud-2Dregions_cloud-2Dregion_Rackspace_RegionOne=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=IFApZ3Bvh6NXo2hwVBqt4EqsE2oGJA_mH24TQifApzw=







Which results in A throwing an internal error 500 and based on the stack 
trace and wget of the url we need to add the issuer certificate as trusted







Based on my understanding this cert can not be obtained from 
aai.api.simpledemo.openecomp.org. Is the issuer cert available somewhere we can 
download?











Stack trace from A…







Getting the resource...: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__aai.api.simpledemo.openecomp.org-3A8443_aai_v8_cloud-2Dinfrastructure_cloud-2Dregions_cloud-2Dregion_Rackspace_RegionOne=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=IFApZ3Bvh6NXo2hwVBqt4EqsE2oGJA_mH24TQifApzw=



Getting the Resource failed: 500:







org.openecomp.aai.exceptions.AAIException: AAI_7402



   at 
org.openecomp.aai.util.GetResource.getNode(GetResource.java:154)



   at org.openecomp.aai.util.GetResource.main(GetResource.java:89)











output of wget…







wget 
https://urldefense.proofpoint.com/v2/url?u=https-3A__aai.api.simpledemo.openecomp.org-3A8443_aai_v8_cloud-2Dinfrastructure_cloud-2Dregions_cloud-2Dregion_Rackspace_RegionOne=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=IFApZ3Bvh6NXo2hwVBqt4EqsE2oGJA_mH24TQifApzw=



--2017-05-02 15:26:38--  
https://urldefense.proofpoint.com/v2/url?u=https-3A__aai.api.simpledemo.openecomp.org-3A8443_aai_v8_cloud-2Dinfrastructure_cloud-2Dregions_cloud-2Dregion_Rackspace_RegionOne=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=IFApZ3Bvh6NXo2hwVBqt4EqsE2oGJA_mH24TQifApzw=



Resolving aai.api.simpledemo.openecomp.org 
(aai.api.simpledemo.openecomp.org)... 10.0.1.1



Connecting to aai.api.simpledemo.openecomp.org 
(aai.api.simpledemo.openecomp.org)|10.0.1.1|:8443... connected.



ERROR: cannot verify aai.api.simpledemo.openecomp.org's certificate, issued by 
‘/C=US/ST=NJ/L=Bedminster/O=OpenECOMP/OU=simpledemo/CN=OpenECOMP simpledemo 
Server CA X1/emailAddress=simpled...@openecomp.org’:



  Unable to locally verify the issuer's authority.



To connect to aai.api.simpledemo.openecomp.org insecurely, use 
`--no-check-certificate'.













___

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=DwIGaQ=LFYZ-o9_HUMeMTSQicvjIg=66ObImPAUA0o2f1hTGknnnv5ScXvX8EnREJCPHHBY5M=0DgjQptYT68hMdoIknmWty95Hsb0UY77OiSYI0q1Fsk=s7aYc4p8X2fRiLJMwr6QE0ppboMTAklKR41vyG_VbXc=
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] ONAP Demo Instance

Hi Sankar,

Have you also looked at the readme.md located in the project repo?
Each development team has put some information about their component in this 
file.

There is also information on the wiki (wiki.onap.org)
https://wiki.onap.org/display/DW/Developing+ONAP

if you have any additional question then feel free to raise it through the 
following wiki so the ONAP community can start to address it - 
http://wiki.onap.org/questions/

Many thanks & regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Shankar, Shashank 
Kumar
Sent: Monday, May 08, 2017 6:09 PM
To: ROSE, DANIEL V ; Joe Falconer ; 
Morales, Victor ; onap-discuss@lists.onap.org; 
BENNETT, RICH ; UNO, LARRY 
Subject: Re: [onap-discuss] ONAP Demo Instance

Hi Daniel,

Any update from the development teams on the development setup/workflow?

Thanks,
Shashank

From: "ROSE, DANIEL V" >
Date: Friday, May 5, 2017 at 10:15 AM
To: Shashank Kumar Shankar 
>, 
Joe Falconer >, 
"Morales, Victor" >, 
"onap-discuss@lists.onap.org" 
>, "BENNETT, 
RICH" >, "UNO, LARRY" 
>
Subject: RE: [onap-discuss] ONAP Demo Instance

Larry can we ring this up with our development teams Monday?

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

From: Shankar, Shashank Kumar [mailto:shashank.kumar.shan...@intel.com]
Sent: Friday, May 05, 2017 10:37 AM
To: ROSE, DANIEL V >; Joe Falconer 
>; Morales, Victor 
>; 
onap-discuss@lists.onap.org; BENNETT, RICH 
>
Subject: Re: [onap-discuss] ONAP Demo Instance

Hi Daneil,

If the Dev team themselves can let us know their environment setup and their 
development work flow for individual components, it would be really helpful 
since we cannot have the complete setup locally and Devs would like to develop 
individual components standalone.

Thanks,
Shashank

From: 
>
 on behalf of "ROSE, DANIEL V" >
Date: Thursday, May 4, 2017 at 9:32 PM
To: Joe Falconer >, 
"Morales, Victor" >, 
"onap-discuss@lists.onap.org" 
>, "BENNETT, 
RICH" >
Subject: Re: [onap-discuss] ONAP Demo Instance

Hello, each component today generally has its own process for setting up an 
environment. I think dcae has one here 
https://wiki.onap.org/display/DW/DCAE+Controller+Development+Guide
 but there is some room for improvement on most of them. I think we can put out 
a request for someone like rich bennett to ask for that from the dev teams.

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 Joe Falconer
Sent: Thursday, May 04, 2017 7:13 PM
To: Morales, Victor 
>; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] ONAP Demo Instance

Hi Victor, Shankar & Daniel

Any learning you can share round this would be most welcome.

Getting a development environment operating with some subset of modules that 
can be deployed locally with limited resources is key to building knowledge of 
the code base.

I know its early in the game but the developers tutorial material is a pretty 
sparse on the wiki.

I'd have thought an early focus on this is key to attracting developers from 
the wider open source community.

Joe

On Fri, May 5, 2017 at 4:00 AM Morales, Victor 
> wrote:
Howdy,

I recently started exploring ONAP source code and I don’t have access to cloud 
resources to deploy it yet, so I decided to split heat template into a Vagrant

Re: [onap-discuss] demo.sh failing with ssl error

Good morning Vikram,

There have been several threads regarding the demo.sh failing.
I would like to check with you if your problem has been solved or if you are 
still facing an issue?

Many thanks & regards
Catherine

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Vikram Mukundamgari
Sent: Tuesday, April 25, 2017 6:34 PM
To: ROSE, DANIEL V ; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] demo.sh failing with ssl error

Hi,

Even after changing the verify =False , I am still getting the same error .

Attached is the log.html file.

Thanks,
Vikram



From: "ROSE, DANIEL V" >
Date: Monday, April 24, 2017 at 2:25 PM
To: Vikram Mukundamgari 
>, 
"onap-discuss@lists.onap.org" 
>
Subject: RE: demo.sh failing with ssl error

https://gerrit.onap.org/r/gitweb?p=testsuite.git;a=blob;f=robot/resources/openstack/keystone_interface.robot;h=6c48e12086ef0bd04aaa05f486b7aae4ae9aff7a;hb=refs/heads/release-1.0.0#l23

I believe verify has to be set to False and then you can rerun the test again 
and it will get past it.


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 Vikram Mukundamgari
Sent: Monday, April 24, 2017 5:07 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] demo.sh failing with ssl error

Hi ,

Running ./demo.sh init in robot vm is failing with ssl error shown below


SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed 
(_ssl.c:590)

Traceback (most recent call last): File 
"/var/opt/OpenECOMP_ETE/robot/library/RequestsLibrary/RequestsKeywords.py", 
line 421, in post_request timeout) File 
"/var/opt/OpenECOMP_ETE/robot/library/RequestsLibrary/RequestsKeywords.py", 
line 871, in _body_request cookies=self.cookies) File 
"/var/opt/OpenECOMP_ETE/robot/library/requests/sessions.py", line 535, in post 
return self.request('POST', url, data=data, json=json, **kwargs) File 
"/var/opt/OpenECOMP_ETE/robot/library/requests/sessions.py", line 488, in 
request resp = self.send(prep, **send_kwargs) File 
"/var/opt/OpenECOMP_ETE/robot/library/requests/sessions.py", line 609, in send 
r = adapter.send(request, **kwargs) File 
"/var/opt/OpenECOMP_ETE/robot/library/requests/adapters.py", line 497, in send 
raise SSLError(e, request=request)

Is there any workaround to bypass the verification or pass the path to 
certificate.

Also attached the log.html

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

[onap-discuss] Info needed about acceptance criteria or checking the sanity of the ONAP Environment

2017-05-29 Thread Gaurav Gupta (c)

Hello There


We have created ONAP stack on  Openstack Mitaka ( Centos7 ) , We are looking 
for some info about the ways to do the sanity check for the ONAP Environment .



There are 2 ways that are present .


using the

a- ete.sh with healthcheck as parameter from robot vm  .

b-

Log into the vm1-robot VM (get  from cloud provider)
-   In the shell run: docker exec openecompete_container 
/var/opt/OpenECOMP_ETE/runTags.sh -i health


Any suggestion whether the above 2 are sufficient  or there are additional 
testing means to check if the ONAP environment is good .


Thanks

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

Re: [onap-discuss] Staging repo in settings.xml

2017-05-29 Thread Closset, Christophe

I’ll set up a call to discuss this further.

I think we need to have a TSC decision on :

-Do we want to freeze artifacts from seed code release 1.0.0 (the 
stable one) and/or 1.1.0 (the enhanced and catch up code)  or not ?

o   A mitigated action could be to just go and bless the Docker containers from 
the stable build that we have – which is what people are trialing against and 
rename the stable branch to something more meaningful (just keep it for 
historical purpose and as an easy way for people to see the code they are 
running their trial on), then for the current master we can probably move away 
from staging and go to snapshots as suggested below.

-Do we formally remove artifact version numbering from ONAP release 
numbering ?

o   If we do, then we could question the whole staging approach.

Few things to note when moving away from staging:

-I don’t think there is a formal list of which artifacts are coming 
from staging, now disabling the staging repo will quickly highlight them. This 
will need attention from all teams to fix their builds with proper snapshots.

We’ve noticed that the build nodes do not start from an empty .m2 repository so 
it might obfuscate issues.

-We will need to setup daily snapshot builds (right now we have daily 
release against staging build) to keep up building our daily docker images, 
sonar scans etc… - we will need to adapt the docker images tag to reflect that 
situation

-We will need each team to adapt their jjb jobs and templates to have a 
way to re-enable staging easily

Just to say that it’s not straightforward and will most probably take a few 
days before we get all components buildable again on master

Regards
Christophe

From: SPATSCHECK, OLIVER
Sent: Friday, May 26, 2017 2:19 PM
To: Andrew Grimberg 
Cc: Gary Wu ; Coquelin, Sebastien 
; Closset, Christophe ; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] Staging repo in settings.xml


Would have to talk to all the teams to get the details but I think most 
artifacts need to be locked down. Please remember that since we created the 
1.0.0 branch we have been contributing code based on two additional internal 
releases into the seed repos. This new code base has not been fully tested yet 
(we took some shortcuts)to catch up. So if we remove the 1.0.0 branch we don’t 
have a working system right now.

I also think that artifact versioning shouldn’t match the ONAP release 
versioning. I think trying to keep that all in sync with the number of 
artifacts we have is a nightmare. E.g. will you be rolling the artifact version 
number on the Open-O artifacts back to 1.0.0? I would just leave them where 
they are. Otherwise you will have people with incorrect artifacts in there 
maven caches.  This seems to be just generating additional work/confusion with 
little practical value.

Oliver

On May 25, 2017, at 5:55 PM, Andrew Grimberg 
> wrote:

On 05/25/2017 02:36 PM, Gary Wu wrote:

That makes sense given that staging artifacts were supposed to exist
only long enough to decide whether they're good to release or not;
they were not meant to be used as long-lived build dependencies.

I think the right thing to do is to move away from this "build
against staging" approach relatively soon.  Given that our formal 1st
release is November, and assuming that the release artifact version
will be "1.0.0", I see two options:

1. Do not release any thing from staging right now.  Change all
artifact versions to 1.0.0-SNAPSHOT.

2.  For the subset of artifacts that need to be "locked down",
actually release the staging candidates right now as 1.0.0-RC0 or
some such.  Then change all artifact versions to 1.0.0-SNAPSHOT,
except explicit dependencies on the released 1.0.0-RC0 artifacts
where desired.

Any other ideas?

Do we have a full list of the artifacts that explicitly need to be
served up from staging repos right now?  I'm hoping this list is
relatively short.

Not something I can answer. I would hope that the seed projects can
answer that.

-Andy-

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

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

Re: [onap-discuss] 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) ; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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) 
>; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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) >; 
onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) >
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: 
>
 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

Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal failed to launch

Hi Subhash,



For me the option was there when I logged into portal. I have the following 
options (I am redeploying ONAP, so list below is what I remember)

1)  Policy

2)  SDC

3)  VID

4)  DMaar

5)  xDemp_App



Initially on clicking SDC I got ‘connection timeout’ as in my setup SDC VM gets 
unreachable. However, I did a work-around after which I can see the ‘bad 
gateway 502’ error, but the SDC page loads.

BTW for the work-around I have another discussion open: 
https://lists.onap.org/pipermail/onap-discuss/2017-May/001030.html



Thanks,

Arun



From: Subhash Kumar Singh [mailto:subhash.kumar.si...@huawei.com]
Sent: Monday, May 29, 2017 2:05 PM
To: Arun Arora (c) ; Kanagaraj Manickam 
; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch



Hi Arun,



Could you please let us know how did you get the option for SDC on portal, 
because after log in to the portal using "demo" username we are seeing empty 
list for applications.



I think we should get the SDC in applications section as documented in wiki [1].



[1] 
https://wiki.onap.org/display/DW/Creating+a+Licensing+Model#CreatingaLicensingModel-RolesintheOnboardingandDistributionWorkflow





--

Regards,

Subhash Kumar Singh





From: Arun Arora (c) [aroraa...@vmware.com]
Sent: Monday, May 29, 2017 12:47
To: Kanagaraj Manickam; 
onap-discuss@lists.onap.org
Cc: Subhash Kumar Singh
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch

Hi Kanagaraj,



I have not checked this yet.



Also when I click on SDC on portal I get “Bad Gateway 502” error. Currently I 
am working to fix this and some other errors before trying things on SDC.

For me, currently, 1 docker each is not up in VID and AAI VMs. And the reason 
for it is HealthCheck of SDC dockers is currently failing. I am working on this 
first.



In the meantime, if you fix the issue you have, can you pls put the details 
here as I suspect that I may also get this problem. Also, I will post here if I 
find any solution for the problem.



Thanks,

Arun





From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Monday, May 29, 2017 12:38 PM
To: Arun Arora (c) >; 
onap-discuss@lists.onap.org
Cc: Subhash Kumar Singh 
>
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch



thanks arun for helping. Now we are trying the tutorial given in wiki and 
facing the following issue:



we wanted to login as 'designer' using cs0008 as mentioned [1] but portal says 
'invalid username or password'. Try to check the portal mysql table 'fn_user', 
it was listing only 'demo' user. so we tried to create the sample user 'user1' 
and 'cs0008' using the portal 'Users'-> Add User. with same password mentioned 
in the wiki. Again portal reports 'invalid username or password' when we try to 
login using 'user1' & 'cs0008'.



MariaDB [portal]> select login_id from fn_user;

+--+

| login_id |

+--+

| cs0008   |

| demo |

| user1|

+--+

3 rows in set (0.03 sec)



MariaDB [portal]>



[1] 
https://wiki.onap.org/display/DW/Creating+a+Licensing+Model



Kindly help.



Regards

Kanagaraj M



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

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

Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal failed to launch

2017-05-29 Thread Subhash Kumar Singh

Hi Arun,

Could you please let us know how did you get the option for SDC on portal, 
because after log in to the portal using "demo" username we are seeing empty 
list for applications.

I think we should get the SDC in applications section as documented in wiki [1].

[1] 
https://wiki.onap.org/display/DW/Creating+a+Licensing+Model#CreatingaLicensingModel-RolesintheOnboardingandDistributionWorkflow


--
Regards,
Subhash Kumar Singh


From: Arun Arora (c) [aroraa...@vmware.com]
Sent: Monday, May 29, 2017 12:47
To: Kanagaraj Manickam; onap-discuss@lists.onap.org
Cc: Subhash Kumar Singh
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch


Hi Kanagaraj,



I have not checked this yet.



Also when I click on SDC on portal I get “Bad Gateway 502” error. Currently I 
am working to fix this and some other errors before trying things on SDC.

For me, currently, 1 docker each is not up in VID and AAI VMs. And the reason 
for it is HealthCheck of SDC dockers is currently failing. I am working on this 
first.



In the meantime, if you fix the issue you have, can you pls put the details 
here as I suspect that I may also get this problem. Also, I will post here if I 
find any solution for the problem.



Thanks,

Arun





From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Monday, May 29, 2017 12:38 PM
To: Arun Arora (c) ; onap-discuss@lists.onap.org
Cc: Subhash Kumar Singh 
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch



thanks arun for helping. Now we are trying the tutorial given in wiki and 
facing the following issue:



we wanted to login as 'designer' using cs0008 as mentioned [1] but portal says 
'invalid username or password'. Try to check the portal mysql table 'fn_user', 
it was listing only 'demo' user. so we tried to create the sample user 'user1' 
and 'cs0008' using the portal 'Users'-> Add User. with same password mentioned 
in the wiki. Again portal reports 'invalid username or password' when we try to 
login using 'user1' & 'cs0008'.



MariaDB [portal]> select login_id from fn_user;

+--+

| login_id |

+--+

| cs0008   |

| demo |

| user1|

+--+

3 rows in set (0.03 sec)



MariaDB [portal]>



[1] https://wiki.onap.org/display/DW/Creating+a+Licensing+Model



Kindly help.



Regards

Kanagaraj M



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

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



From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Monday, May 29, 2017 11:47 AM
To: Subhash Kumar Singh
Cc: onap-discuss@lists.onap.org; Kanagaraj 
Manickam
Subject: Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch



Glad it worked  



Regards,

Arun



From: Subhash Kumar Singh 
>
Sent: Monday, May 29, 2017 11:30:26 AM
To: Arun Arora (c)
Cc: onap-discuss@lists.onap.org; Kanagaraj 
Manickam
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch



Hi Arun,



Thank you for the suggestions.



We are now able to access the portal by following your another post [1]. After 
adding the hosts entry in the portal docker instance, portal dashboard is 
accessible.



[1] 
https://lists.onap.org/pipermail/onap-discuss/2017-May/001032.html



--

Thanks and Regards,

Subhash Kumar Singh





From: Arun Arora (c) [aroraa...@vmware.com]
Sent: Friday, May 26, 2017 20:16
To: Subhash Kumar Singh
Cc: onap-discuss@lists.onap.org; Kanagaraj 
Manickam

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) ; onap-discuss@lists.onap.org
Cc: Kapil Gupta (c) 
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: 
>
 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


sdc.grub.cfg
Description: sdc.grub.cfg


sdc.grub.cfg.modified
Description: sdc.grub.cfg.modified


mso.grub.cfg
Description: mso.grub.cfg


mso.grub.cfg.modified
Description: mso.grub.cfg.modified


robot.grub.cfg
Description: robot.grub.cfg


robot.grub.cfg.modified
Description: robot.grub.cfg.modified
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal failed to launch

Hi Kanagaraj,

I have not checked this yet.

Also when I click on SDC on portal I get “Bad Gateway 502” error. Currently I 
am working to fix this and some other errors before trying things on SDC.

For me, currently, 1 docker each is not up in VID and AAI VMs. And the reason 
for it is HealthCheck of SDC dockers is currently failing. I am working on this 
first.

In the meantime, if you fix the issue you have, can you pls put the details 
here as I suspect that I may also get this problem. Also, I will post here if I 
find any solution for the problem.

Thanks,

Arun

From: Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com]
Sent: Monday, May 29, 2017 12:38 PM
To: Arun Arora (c) ; onap-discuss@lists.onap.org
Cc: Subhash Kumar Singh 
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch

thanks arun for helping. Now we are trying the tutorial given in wiki and 
facing the following issue:

we wanted to login as 'designer' using cs0008 as mentioned [1] but portal says 
'invalid username or password'. Try to check the portal mysql table 'fn_user', 
it was listing only 'demo' user. so we tried to create the sample user 'user1' 
and 'cs0008' using the portal 'Users'-> Add User. with same password mentioned 
in the wiki. Again portal reports 'invalid username or password' when we try to 
login using 'user1' & 'cs0008'.

MariaDB [portal]> select login_id from fn_user;

+--+

| login_id |

+--+

| cs0008   |

| demo |

| user1|

+--+

3 rows in set (0.03 sec)

MariaDB [portal]>

[1] https://wiki.onap.org/display/DW/Creating+a+Licensing+Model

Kindly help.

Regards

Kanagaraj M

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

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

From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Monday, May 29, 2017 11:47 AM
To: Subhash Kumar Singh
Cc: onap-discuss@lists.onap.org; Kanagaraj 
Manickam
Subject: Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch

Glad it worked  

Regards,

Arun

From: Subhash Kumar Singh 
>
Sent: Monday, May 29, 2017 11:30:26 AM
To: Arun Arora (c)
Cc: onap-discuss@lists.onap.org; Kanagaraj 
Manickam
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch

Hi Arun,

Thank you for the suggestions.

We are now able to access the portal by following your another post [1]. After 
adding the hosts entry in the portal docker instance, portal dashboard is 
accessible.

[1] 
https://lists.onap.org/pipermail/onap-discuss/2017-May/001032.html

--

Thanks and Regards,

Subhash Kumar Singh

From: Arun Arora (c) [aroraa...@vmware.com]
Sent: Friday, May 26, 2017 20:16
To: Subhash Kumar Singh
Cc: onap-discuss@lists.onap.org; Kanagaraj 
Manickam
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch

Hi Subhash,

First pls establish that you are able to ping the portal VM's Floating IP from 
inside the VM and inside the docker.

If ping does not work then its likely a security group issue.

I faced a similar issue so I am thinking in that terms.

Also can you share the snapshot of ur default security group rules.

Thanks

Arun

On May 26, 2017, at 7:16 PM, Subhash Kumar Singh 
> wrote:

Hello Arun,

Thanks for the suggestions.

I think, this issue is not related to floating IP or security group because we 
are able to access the vm

[onap-discuss] AAF & DMaaP - Any partnership?

Good morning all,

We are looking for any potential partnership with other companies to 
participate to the following projects:


·Authentication and Authorization 
Framework

·Data Movement as a 
Platform

Feel free to contact Ram Koya or myself if you have any interest.
Thank you.

Many thanks & regards
Catherine

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


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

TEXTING and DRIVING... It Can Wait

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



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

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

Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal failed to launch

2017-05-29 Thread Kanagaraj Manickam

thanks arun for helping. Now we are trying the tutorial given in wiki and 
facing the following issue:

we wanted to login as 'designer' using cs0008 as mentioned [1] but portal says 
'invalid username or password'. Try to check the portal mysql table 'fn_user', 
it was listing only 'demo' user. so we tried to create the sample user 'user1' 
and 'cs0008' using the portal 'Users'-> Add User. with same password mentioned 
in the wiki. Again portal reports 'invalid username or password' when we try to 
login using 'user1' & 'cs0008'.

MariaDB [portal]> select login_id from fn_user;
+--+
| login_id |
+--+
| cs0008   |
| demo |
| user1|
+--+
3 rows in set (0.03 sec)

MariaDB [portal]>

[1] https://wiki.onap.org/display/DW/Creating+a+Licensing+Model

Kindly help.

Regards
Kanagaraj M

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

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

From: Arun Arora (c) [mailto:aroraa...@vmware.com]
Sent: Monday, May 29, 2017 11:47 AM
To: Subhash Kumar Singh
Cc: onap-discuss@lists.onap.org; Kanagaraj Manickam
Subject: Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch

Glad it worked  

Regards,

Arun

From: Subhash Kumar Singh 
>
Sent: Monday, May 29, 2017 11:30:26 AM
To: Arun Arora (c)
Cc: onap-discuss@lists.onap.org; Kanagaraj 
Manickam
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch

Hi Arun,

Thank you for the suggestions.

We are now able to access the portal by following your another post [1]. After 
adding the hosts entry in the portal docker instance, portal dashboard is 
accessible.

[1] 
https://lists.onap.org/pipermail/onap-discuss/2017-May/001032.html

--
Thanks and Regards,
Subhash Kumar Singh

From: Arun Arora (c) [aroraa...@vmware.com]
Sent: Friday, May 26, 2017 20:16
To: Subhash Kumar Singh
Cc: onap-discuss@lists.onap.org; Kanagaraj 
Manickam
Subject: RE: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal 
failed to launch
Hi Subhash,
First pls establish that you are able to ping the portal VM's Floating IP from 
inside the VM and inside the docker.
If ping does not work then its likely a security group issue.
I faced a similar issue so I am thinking in that terms.
Also can you share the snapshot of ur default security group rules.
Thanks
Arun
On May 26, 2017, at 7:16 PM, Subhash Kumar Singh 
> wrote:
Hello Arun,

Thanks for the suggestions.

I think, this issue is not related to floating IP or security group because we 
are able to access the vm (onap-portal) using the assigned private key.

I've checked the /opt/cofig/public_ip.txt file, it is correctly configured with 
floating IP and security group allows all the TCP traffic (0-65535) 
egress/ingress .

Please let me know for your suggestion.

--
Regards,
Subhash Kumar Singh

From: Arun Arora (c) [aroraa...@vmware.com]
Sent: Friday, May 26, 2017 18:38
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.

[onap-discuss] Authentication and Authorization Framework & Data Movement as a Platform - Any partnership?

Good morning all,

We are looking for any potential partnership with other companies to 
participate to the following projects:


·Authentication and Authorization 
Framework

·Data Movement as a 
Platform

Feel free to contact Ram Koya or myself if you have any interest.
Thank you.

Many thanks & regards
Catherine

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


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

TEXTING and DRIVING... It Can Wait

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



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

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

Re: [onap-discuss] demo/OpenECOMP heat stack successful ! ONAP portal failed to launch