Re: [onap-discuss] [onap-tsc] [ONAP STANDARDS/SDO COORDINATOR ELECTION] Kickoff of the ONAP Standards/SDO Coordinator Election

2017-05-17 Thread Lingli Deng
Hi Tony,

 

Sorry for the mistake.

Please kindly ignore the previous message.

 

Lingli

 

From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Lingli
Sent: 2017年5月18日 8:42
To: HANSEN, TONY L 
Cc: onap-discuss@lists.onap.org; onap-tsc 
Subject: Re: [onap-tsc] [onap-discuss] [ONAP STANDARDS/SDO COORDINATOR 
ELECTION] Kickoff of the ONAP Standards/SDO Coordinator Election

 

你认识么?

 

 

China Mobile Research Institute 

On 05/18/2017 07:10,   HANSEN, TONY L wrote: 

I am interested in the ONAP Standards / SDO Coordinator position. I feel that 
my involvement in the standards world for the past 25 years puts me in an 
excellent position to support ONAP in this role.

 

Tony Hansen

 

Standards work:

 

I have been involved in the Internet Engineering Task Force (IETF) for 25 
years, attending a majority of the meetings for the past 20 years. Most of my 
efforts there have been involved in the Applications and Real Time area, the 
Security area, and the General area (layer 5 on up). I have 20 published 
Requests for Comment (RFCs), including full internet standards and best current 
practices. I have been a Working Group (WG) chair four times, for the Open 
Pluggable Edge Platform WG (OPES, 2005-2007), the Yet Another Mail WG (YAM, 
2009-2011), the File Transfer Protocol Extensions (FTPext, 2010-2012), and the 
Javascript Object Signing and Encryption WG (JOSE, 2011-2012). I have been a 
member of the RFC Series Oversight Committee (an Internet Architecture Board 
[IAB] appointed position) for the past four years.

 

I have also been an adjunct liaison to the C++ Standards Committee since 1991.

 

RFCS:

RFC3798 Message Disposition Notification. T. Hansen, Ed., G. Vaudreuil, Ed.. 
May 2004. (draft standard) (DOI: 10.17487/RFC3798)

 

RFC3885 SMTP Service Extension for Message Tracking. E. Allman, T. Hansen. 
September 2004. (Proposed Standard) (DOI: 10.17487/RFC3885)

 

RFC3887 Message Tracking Query Protocol. T. Hansen. September 2004. (Proposed 
Standard) (DOI: 10.17487/RFC3887)

 

RFC3888 Message Tracking Model and Requirements. T. Hansen. September 2004. 
(Informational) (DOI: 10.17487/RFC3888)

 

RFC3938 Video-Message Message-Context. T. Hansen. October 2004. (Proposed 
Standard) (DOI: 10.17487/RFC3938)

 

RFC4395 / BCP35 Guidelines and Registration Procedures for New URI Schemes. T. 
Hansen, T. Hardie, L. Masinter. February 2006. (Best Current Practice) (DOI: 
10.17487/RFC4395)

 

RFC4634 US Secure Hash Algorithms (SHA and HMAC-SHA). D. Eastlake 3rd, T. 
Hansen. July 2006. (Informational) (DOI: 10.17487/RFC4634)

 

RFC5248 / BCP138 A Registry for SMTP Enhanced Mail System Status Codes. T. 
Hansen, J. Klensin. June 2008. (Best Current Practice) (DOI: 10.17487/RFC5248)

 

RFC5585 DomainKeys Identified Mail (DKIM) Service Overview. T. Hansen, D. 
Crocker, P. Hallam-Baker. July 2009. (Informational) (DOI: 10.17487/RFC5585)

 

RFC5703 Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, 
Replacement, and Enclosure. T. Hansen, C. Daboo. October 2009. (Proposed 
Standard) (DOI: 10.17487/RFC5703)

 

RFC5863 DomainKeys Identified Mail (DKIM) Development, Deployment, and 
Operations. T. Hansen, E. Siegel, P. Hallam-Baker, D. Crocker. May 2010. 
(Informational) (DOI: 10.17487/RFC5863)

 

RFC6234 US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF). D. 
Eastlake 3rd, T. Hansen. May 2011. (Informational) (DOI: 10.17487/RFC6234)

 

RFC6376 / STD76 DomainKeys Identified Mail (DKIM) Signatures. D. Crocker, Ed., 
T. Hansen, Ed., M. Kucherawy, Ed.. September 2011. (Internet Standard) (DOI: 
10.17487/RFC6376)

 

RFC6533 Internationalized Delivery Status and Disposition Notifications. T. 
Hansen, Ed., C. Newman, A. Melnikov. February 2012. (Proposed Standard) (DOI: 
10.17487/RFC6533)

 

RFC6838 / BCP13 Media Type Specifications and Registration Procedures. N. 
Freed, J. Klensin, T. Hansen. January 2013. (Best Current Practice) (DOI: 
10.17487/RFC6838)

 

RFC6839 Additional Media Type Structured Syntax Suffixes. T. Hansen, A. 
Melnikov. January 2013. (Informational) (DOI: 10.17487/RFC6839)

 

RFC7595 / BCP35 Guidelines and Registration Procedures for URI Schemes. D. 
Thaler, Ed., T. Hansen, T. Hardie. June 2015. (Best Current Practice) (DOI: 
10.17487/RFC7595)

 

RFC7677 SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security 
Layer (SASL) Mechanisms. T. Hansen. November 2015. (Proposed Standard) (DOI: 
10.17487/RFC7677)

 

RFC7995 PDF Format for RFCs. T. Hansen, Ed., L. Masinter, M. Hardy. December 
2016. (Informational) (DOI: 10.17487/RFC7995)

 

RFC8098 / STD85 Message Disposition Notification. T. Hansen, Ed., A. Melnikov, 
Ed.. February 2017. (Internet Standard) (DOI: 10.17487/RFC8098)

 

Open Source work:

 

I was an early adopter of open source 35 years ago. I have contributed to the 
IETF Open source tools for the past 10 years. I have contributed code to 
various other small op

Re: [onap-discuss] [ONAP STANDARDS/SDO COORDINATOR ELECTION] Kickoff of the ONAP Standards/SDO Coordinator Election

2017-05-17 Thread Lingli



I am interested in the ONAP Standards / SDO Coordinator position. I feel that my involvement in the standards world for the past 25 years puts me in an excellent position to support ONAP
 in this role.
 
    Tony Hansen
 
Standards work:
 
I have been involved in the Internet Engineering Task Force (IETF) for 25 years, attending a majority of the meetings for the past 20 years. Most of my efforts
 there have been involved in the Applications and Real Time area, the Security area, and the General area (layer 5 on up). I have 20 published Requests for Comment (RFCs), including full internet standards and best current practices. I have been a Working Group
 (WG) chair four times, for the Open Pluggable Edge Platform WG (OPES, 2005-2007), the Yet Another Mail WG (YAM, 2009-2011), the File Transfer Protocol Extensions (FTPext, 2010-2012), and the _javascript_ Object Signing and Encryption WG (JOSE, 2011-2012). I
 have been a member of the RFC Series Oversight Committee (an Internet Architecture Board [IAB] appointed position) for the past four years.
 
I have also been an adjunct liaison to the C++ Standards Committee since 1991.
 
RFCS:
RFC3798 Message Disposition Notification. T. Hansen, Ed., G. Vaudreuil, Ed.. May 2004. (draft standard) (DOI: 10.17487/RFC3798)
 
RFC3885 SMTP Service Extension for Message Tracking. E. Allman, T. Hansen. September 2004. (Proposed Standard) (DOI: 10.17487/RFC3885)
 
RFC3887 Message Tracking Query Protocol. T. Hansen. September 2004. (Proposed Standard) (DOI: 10.17487/RFC3887)
 
RFC3888 Message Tracking Model and Requirements. T. Hansen. September 2004. (Informational) (DOI: 10.17487/RFC3888)
 
RFC3938 Video-Message Message-Context. T. Hansen. October 2004. (Proposed Standard) (DOI: 10.17487/RFC3938)
 
RFC4395 / BCP35 Guidelines and Registration Procedures for New URI Schemes. T. Hansen, T. Hardie, L. Masinter. February 2006. (Best Current Practice) (DOI: 10.17487/RFC4395)
 
RFC4634 US Secure Hash Algorithms (SHA and HMAC-SHA). D. Eastlake 3rd, T. Hansen. July 2006. (Informational) (DOI: 10.17487/RFC4634)
 
RFC5248 / BCP138 A Registry for SMTP Enhanced Mail System Status Codes. T. Hansen, J. Klensin. June 2008. (Best Current Practice) (DOI: 10.17487/RFC5248)
 
RFC5585 DomainKeys Identified Mail (DKIM) Service Overview. T. Hansen, D. Crocker, P. Hallam-Baker. July 2009. (Informational) (DOI: 10.17487/RFC5585)
 
RFC5703 Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure. T. Hansen, C. Daboo. October 2009. (Proposed Standard) (DOI:
 10.17487/RFC5703)
 
RFC5863 DomainKeys Identified Mail (DKIM) Development, Deployment, and Operations. T. Hansen, E. Siegel, P. Hallam-Baker, D. Crocker. May 2010. (Informational)
 (DOI: 10.17487/RFC5863)
 
RFC6234 US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF). D. Eastlake 3rd, T. Hansen. May 2011. (Informational) (DOI: 10.17487/RFC6234)
 
RFC6376 / STD76 DomainKeys Identified Mail (DKIM) Signatures. D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed.. September 2011. (Internet Standard) (DOI: 10.17487/RFC6376)
 
RFC6533 Internationalized Delivery Status and Disposition Notifications. T. Hansen, Ed., C. Newman, A. Melnikov. February 2012. (Proposed Standard) (DOI: 10.17487/RFC6533)
 
RFC6838 / BCP13 Media Type Specifications and Registration Procedures. N. Freed, J. Klensin, T. Hansen. January 2013. (Best Current Practice) (DOI: 10.17487/RFC6838)
 
RFC6839 Additional Media Type Structured Syntax Suffixes. T. Hansen, A. Melnikov. January 2013. (Informational) (DOI: 10.17487/RFC6839)
 
RFC7595 / BCP35 Guidelines and Registration Procedures for URI Schemes. D. Thaler, Ed., T. Hansen, T. Hardie. June 2015. (Best Current Practice) (DOI: 10.17487/RFC7595)
 
RFC7677 SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security Layer (SASL) Mechanisms. T. Hansen. November 2015. (Proposed Standard) (DOI: 10.17487/RFC7677)
 
RFC7995 PDF Format for RFCs. T. Hansen, Ed., L. Masinter, M. Hardy. December 2016. (Informational) (DOI: 10.17487/RFC7995)
 
RFC8098 / STD85 Message Disposition Notification. T. Hansen, Ed., A. Melnikov, Ed.. February 2017. (Internet Standard) (DOI: 10.17487/RFC8098)
 
Open Source work:
 
I was an early adopter of open source 35 years ago. I have contributed to the IETF Open source tools for the past 10 years. I have contributed code to various other
 small open source projects. I have been working on OpenECOMP & now ONAP for the past two years.
 
Other major publications:
 
The C++ Answer Book, 1989
 
Professional Experience:
 
   Bell Laboratories / AT&T 1980 – present
Member of Technical Staff, Distinguished Member of Technical Staff, Technology Consultant, Lead Member Technical Staff
 
Education:
 
Masters Computer Science / Computer Engineering, Stanford University, 1981
Bachelor of Science Electrical Engineering, SDSU, 1980
Bachelor of Arts Mathematics, SDSU, 1980
 


 

 

From: 
 on behalf of Phil Robb 

Re: [onap-discuss] [ONAP STANDARDS/SDO COORDINATOR ELECTION] Kickoff of the ONAP Standards/SDO Coordinator Election

2017-05-17 Thread HANSEN, TONY L
I am interested in the ONAP Standards / SDO Coordinator position. I feel that 
my involvement in the standards world for the past 25 years puts me in an 
excellent position to support ONAP in this role.

Tony Hansen

Standards work:

I have been involved in the Internet Engineering Task Force (IETF) for 25 
years, attending a majority of the meetings for the past 20 years. Most of my 
efforts there have been involved in the Applications and Real Time area, the 
Security area, and the General area (layer 5 on up). I have 20 published 
Requests for Comment (RFCs), including full internet standards and best current 
practices. I have been a Working Group (WG) chair four times, for the Open 
Pluggable Edge Platform WG (OPES, 2005-2007), the Yet Another Mail WG (YAM, 
2009-2011), the File Transfer Protocol Extensions (FTPext, 2010-2012), and the 
Javascript Object Signing and Encryption WG (JOSE, 2011-2012). I have been a 
member of the RFC Series Oversight Committee (an Internet Architecture Board 
[IAB] appointed position) for the past four years.

I have also been an adjunct liaison to the C++ Standards Committee since 1991.

RFCS:
RFC3798 Message Disposition Notification. T. Hansen, Ed., G. Vaudreuil, Ed.. 
May 2004. (draft standard) (DOI: 10.17487/RFC3798)

RFC3885 SMTP Service Extension for Message Tracking. E. Allman, T. Hansen. 
September 2004. (Proposed Standard) (DOI: 10.17487/RFC3885)

RFC3887 Message Tracking Query Protocol. T. Hansen. September 2004. (Proposed 
Standard) (DOI: 10.17487/RFC3887)

RFC3888 Message Tracking Model and Requirements. T. Hansen. September 2004. 
(Informational) (DOI: 10.17487/RFC3888)

RFC3938 Video-Message Message-Context. T. Hansen. October 2004. (Proposed 
Standard) (DOI: 10.17487/RFC3938)

RFC4395 / BCP35 Guidelines and Registration Procedures for New URI Schemes. T. 
Hansen, T. Hardie, L. Masinter. February 2006. (Best Current Practice) (DOI: 
10.17487/RFC4395)

RFC4634 US Secure Hash Algorithms (SHA and HMAC-SHA). D. Eastlake 3rd, T. 
Hansen. July 2006. (Informational) (DOI: 10.17487/RFC4634)

RFC5248 / BCP138 A Registry for SMTP Enhanced Mail System Status Codes. T. 
Hansen, J. Klensin. June 2008. (Best Current Practice) (DOI: 10.17487/RFC5248)

RFC5585 DomainKeys Identified Mail (DKIM) Service Overview. T. Hansen, D. 
Crocker, P. Hallam-Baker. July 2009. (Informational) (DOI: 10.17487/RFC5585)

RFC5703 Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, 
Replacement, and Enclosure. T. Hansen, C. Daboo. October 2009. (Proposed 
Standard) (DOI: 10.17487/RFC5703)

RFC5863 DomainKeys Identified Mail (DKIM) Development, Deployment, and 
Operations. T. Hansen, E. Siegel, P. Hallam-Baker, D. Crocker. May 2010. 
(Informational) (DOI: 10.17487/RFC5863)

RFC6234 US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF). D. 
Eastlake 3rd, T. Hansen. May 2011. (Informational) (DOI: 10.17487/RFC6234)

RFC6376 / STD76 DomainKeys Identified Mail (DKIM) Signatures. D. Crocker, Ed., 
T. Hansen, Ed., M. Kucherawy, Ed.. September 2011. (Internet Standard) (DOI: 
10.17487/RFC6376)

RFC6533 Internationalized Delivery Status and Disposition Notifications. T. 
Hansen, Ed., C. Newman, A. Melnikov. February 2012. (Proposed Standard) (DOI: 
10.17487/RFC6533)

RFC6838 / BCP13 Media Type Specifications and Registration Procedures. N. 
Freed, J. Klensin, T. Hansen. January 2013. (Best Current Practice) (DOI: 
10.17487/RFC6838)

RFC6839 Additional Media Type Structured Syntax Suffixes. T. Hansen, A. 
Melnikov. January 2013. (Informational) (DOI: 10.17487/RFC6839)

RFC7595 / BCP35 Guidelines and Registration Procedures for URI Schemes. D. 
Thaler, Ed., T. Hansen, T. Hardie. June 2015. (Best Current Practice) (DOI: 
10.17487/RFC7595)

RFC7677 SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security 
Layer (SASL) Mechanisms. T. Hansen. November 2015. (Proposed Standard) (DOI: 
10.17487/RFC7677)

RFC7995 PDF Format for RFCs. T. Hansen, Ed., L. Masinter, M. Hardy. December 
2016. (Informational) (DOI: 10.17487/RFC7995)

RFC8098 / STD85 Message Disposition Notification. T. Hansen, Ed., A. Melnikov, 
Ed.. February 2017. (Internet Standard) (DOI: 10.17487/RFC8098)

Open Source work:

I was an early adopter of open source 35 years ago. I have contributed to the 
IETF Open source tools for the past 10 years. I have contributed code to 
various other small open source projects. I have been working on OpenECOMP & 
now ONAP for the past two years.

Other major publications:

The C++ Answer Book, 1989

Professional Experience:

   Bell Laboratories / AT&T 1980 – present
Member of Technical Staff, Distinguished Member of Technical Staff, Technology 
Consultant, Lead Member Technical Staff

Education:

Masters Computer Science / Computer Engineering, Stanford University, 1981
Bachelor of Science Electrical Engineering, SDSU, 1980
Bachelor of Arts Mathematics, SDSU, 1980

[cid:image001.png@01D2CF41.1835AB40] [cid:image002.png@01D2CF41.1835AB40]


From: 
ma

Re: [onap-discuss] [ONAP STANDARDS/SDO COORDINATOR ELECTION] Kickoff of the ONAP Standards/SDO Coordinator Election - Intel Uri Elzur candidacy

2017-05-17 Thread Elzur, Uri
Resend as I have not seen it come through

Thx

Uri (“Oo-Ree”)
C: 949-378-7568

From: Elzur, Uri
Sent: Tuesday, May 16, 2017 11:17 PM
To: Phil Robb ; onap-tsc ; 
onap-discuss@lists.onap.org
Cc: Elzur, Uri (uri.el...@intel.com) 
Subject: RE: [onap-discuss] [ONAP STANDARDS/SDO COORDINATOR ELECTION] Kickoff 
of the ONAP Standards/SDO Coordinator Election - Intel Uri Elzur candidacy

Hi All

Working in open source communities and standard organizations for multiple 
years now and specifically in all layers pertinent to ONAP, is in my humble 
opinion, the background needed to be successful in this important role for the 
ONAP community. I’ve gathered lots of experience serving as the OPEN-O TSC Vice 
chair and Architecture chair. I’m proud of the initiatives I’ve led in that 
community including the initiation of the VNF SDK project that was adopted by 
the ONAP community too! The VNF SDK was the first open source proposed project 
to fully include VNFs in a MANO community!

The VNF SDK project is designed to address the painful on-boarding issue and it 
emphasized the importance of getting VNFs that are in tune with the MANO 
orchestration as part of the initial design vs. an afterthought. Specifically 
related to this standards and SDO coordinator position, I’ve also proposed the 
adoption of a unified, industry-agreed Data Models to enable higher levels of 
MANO automation and reduction of the VNF vendor’s labor. This has been done in 
collaboration with all community vendor and considering and integrating the 
opinions and inputs of multiple VNF vendors.

Positions on level of automation and cloud readiness, are  one of the topics 
that may separate different candidates for this position. We firmly believe 
that working with relevant standard organizations to promote highest level of 
automation and agility, are essential to enable Telco to best compete with best 
cloud efficiencies, for long term NFV success. However, my unequivocal commit 
is to represent the TSC position whatever it may be!

The time left before the vote is short. So I hope this write up provides some 
idea of the motivation, proven capabilities and proposed directions


Additional relevant background

· OPEN-O - multiple contributions to the Membership agreement that was 
used to guide the ONAP’s membership agreement. Active participant in data 
modeling and standard  interactions.

· ODL – serve on the board and was on the TSC in last 2 years. 
intitiated and drove the Multi Writer work to respolve the issue of multiple 
projects simultaneously intercting with a vSwitch.  Inititiator of the S3P 
(Stability, Security, Scalabilitya and Perfomance) as a mesure of “readiness” 
for an open Source project – adopted by ONAP as well

· SFC – working with many of the industry and the community to look for 
a broad industry agreement for top to bottom SFC

· VNF Data Model – created the initiative for Data Model convergence 
and industry agreement including multi party  public efforts  open to all where 
interoprability and use of the VNF SDK tools created for OPEN-O was 
demonstrated  (e.g. public demo at MWC and recently at L123 NFV World Congress)

· DMTF board member 2008-2010

· IETF – co editor of the NSH (SFC related) draft

· At Intel I lead the stack architrcture MANO through OpenStack, ODL, 
vSwitches and the server platform. This provides an opportunity


Beyond experience, have demonstraed an un biased handling of technical issues! 
It is important to note that, we at Intel, do not ship products competing with 
the key vendors in the ONAP community, we are positioned to handle any 
potential disagreement in an even handed way!

Short bio is found below.


Uri Elzur Bio
DNSG Chief Technologist

Uri Elzur is the CTO for the Data Center Network Solution Group (DNSG) of 
Intel’s Data Center Group. In this role, he is responsible for creating SDN/NFV 
technical strategy, open source top-to-bottom stack architectures (including 
MANO, OpenStack, ODL, vSwitch) and influence the server platforms.

Uri is a networking specialist with more than 25 years of industry experience 
and a proven track record of creating innovative product architectures, 
strategies and in Networking, Virtualization, Security etc. Currently represent 
Intel at ODL, Open-O (as a VC Architecture) and IETF.

Previously, Uri has held a position of a Sr. Director at Broadcom, managing a 
networking/NIC architecture team. In that role Uri led multiple innovations in 
the areas of Virtualization, TCP offload, RDMA, iSER, iSCSI/FCoE.

Uri holds many patents and BSc and MSc EE/CS from the Technion, Haifa, Israel


Thx

Uri (“Oo-Ree”)
C: 949-378-7568

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Phil Robb
Sent: Thursday, May 11, 2017 6:51 PM
To: onap-tsc mailto:onap-...@lists.onap.org>>; 
onap-discuss@lists.onap.org

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

2017-05-17 Thread ROSE, DANIEL V
They may both be there, but you wont have to do the second one through VID. 
Policy will do it for you


Thanks,

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

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

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



Sent from my Mi phone
On "ROSE, DANIEL V" mailto:dr6...@att.com>>, May 17, 2017 11:00 
PM wrote:
Hi Kedar

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

Thanks,

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

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

Hi Daniel,

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

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

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

Regards,
KeDar

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

Yeah, that’s how testing does it.

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

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

Hi Daniel,

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

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

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

We did thinks a bit bifferent for vlb vs vfw, here robot treats the packet gen 
as a tool to test the use case. This is actually closer to being how real vnfs 
would be tested as most real vnfs would not have a packet gen included in their 
base heat template.


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

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

Hi ,

packet_gen_vlb_rackspace.env file of vLB use case has this parameter.

vlb_ipaddr: INSERT THE PUBLIC ADDRESS OF THE vLB HERE

To fill this, the vLB VM needs to be instantiated first.

What all Heat templates should be part of the zip file to be uploaded while 
defining a new Vendor Software Product in case of vLB ? Only 
dnsscaling_rackspace and base_vlb_rackspace first and then separately 
packet_gen_vlb_rackspace ? If this understanding is correct, then there will be 
2 Heat stacks for vLB  usecase ?

Regards,
KeDar



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.

___

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

2017-05-17 Thread Kedar Ambekar
In my case, I think VID has loaded. both as I get 2 options to create VF module.



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

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

Thanks,

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

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

Hi Daniel,

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

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

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

Regards,
KeDar

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

Yeah, that’s how testing does it.

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

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

Hi Daniel,

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

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

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

We did thinks a bit bifferent for vlb vs vfw, here robot treats the packet gen 
as a tool to test the use case. This is actually closer to being how real vnfs 
would be tested as most real vnfs would not have a packet gen included in their 
base heat template.


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

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

Hi ,

packet_gen_vlb_rackspace.env file of vLB use case has this parameter.

vlb_ipaddr: INSERT THE PUBLIC ADDRESS OF THE vLB HERE

To fill this, the vLB VM needs to be instantiated first.

What all Heat templates should be part of the zip file to be uploaded while 
defining a new Vendor Software Product in case of vLB ? Only 
dnsscaling_rackspace and base_vlb_rackspace first and then separately 
packet_gen_vlb_rackspace ? If this understanding is correct, then there will be 
2 Heat stacks for vLB  usecase ?

Regards,
KeDar



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] SDC portal is not accessible with 502 error

2017-05-17 Thread Vitaliy Emporopulo
It's configuration.yaml - not configuration.yml.

Sorry my bad

From: Vitaliy Emporopulo
Sent: Wednesday, May 17, 2017 21:20
To: Elhay Efrat ; ajay.priyadar...@ril.com; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Hi Ajay,

It looks like SDC fails to connect to the Cassandra cluster. Are all of your 
SDC Docker containers running in a single VM?

To begin with, I would check the connectivity from BE to Cassandra and whether 
the Cassandra cluster IP has been configured correctly. Open a shell session in 
the BE container and look for configuration.yml, cassandraConfig section.

Regards,
Vitaliy

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Wednesday, May 17, 2017 17:12
To: ajay.priyadar...@ril.com; 
onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Could we share hangout elhayef...@gmail.com ?

From: ajay.priyadar...@ril.com 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 5:08 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi

 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat mailto:elhay.efr...@amdocs.com>>
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi 
mailto:ajay.priyadar...@ril.com>>,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-

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

2017-05-17 Thread Vitaliy Emporopulo
Hi Ajay,

It looks like SDC fails to connect to the Cassandra cluster. Are all of your 
SDC Docker containers running in a single VM?

To begin with, I would check the connectivity from BE to Cassandra and whether 
the Cassandra cluster IP has been configured correctly. Open a shell session in 
the BE container and look for configuration.yml, cassandraConfig section.

Regards,
Vitaliy

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Elhay Efrat
Sent: Wednesday, May 17, 2017 17:12
To: ajay.priyadar...@ril.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC portal is not accessible with 502 error

Could we share hangout elhayef...@gmail.com ?

From: ajay.priyadar...@ril.com 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 5:08 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi

 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat mailto:elhay.efr...@amdocs.com>>
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi 
mailto:ajay.priyadar...@ril.com>>,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

201

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

2017-05-17 Thread ROSE, DANIEL V
Hi Kedar

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

Thanks,

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

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

Hi Daniel,

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

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

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

Regards,
KeDar

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

Yeah, that's how testing does it.

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

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

Hi Daniel,

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

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

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

We did thinks a bit bifferent for vlb vs vfw, here robot treats the packet gen 
as a tool to test the use case. This is actually closer to being how real vnfs 
would be tested as most real vnfs would not have a packet gen included in their 
base heat template.


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

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

Hi ,

packet_gen_vlb_rackspace.env file of vLB use case has this parameter.

vlb_ipaddr: INSERT THE PUBLIC ADDRESS OF THE vLB HERE

To fill this, the vLB VM needs to be instantiated first.

What all Heat templates should be part of the zip file to be uploaded while 
defining a new Vendor Software Product in case of vLB ? Only 
dnsscaling_rackspace and base_vlb_rackspace first and then separately 
packet_gen_vlb_rackspace ? If this understanding is correct, then there will be 
2 Heat stacks for vLB  usecase ?

Regards,
KeDar



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] SDC portal is not accessible with 502 error

2017-05-17 Thread Elhay Efrat
Could we share hangout elhayef...@gmail.com ?

From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 5:08 PM
To: Elhay Efrat ; onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

Yes, all docker containers are up.

Regards,
Ajay Priyadarshi

 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat mailto:elhay.efr...@amdocs.com>>
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi 
mailto:ajay.priyadar...@ril.com>>,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com 
[mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat mailto:elhay.efr...@amdocs.com>>; 
onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

2017-05-17 10:23:54.033:INFO:oejs.SetUIDListener:main: Setting umask=02
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:9443}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:54.053:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:54.055:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:54.070:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:54.383:INFO:oeja.Ann

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

2017-05-17 Thread Ajay.Priyadarshi
Yes, all docker containers are up.

Regards,
Ajay Priyadarshi


 Original Message 
Subject: RE: SDC portal is not accessible with 502 error
From: Elhay Efrat 
Date: 17 May 2017, 19:33
To: Ajay Priyadarshi ,onap-discuss@lists.onap.org
Could you please check you Cassandra Docker if it’s up or down

From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat ; onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

2017-05-17 10:23:54.033:INFO:oejs.SetUIDListener:main: Setting umask=02
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:9443}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:54.053:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:54.055:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:54.070:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:54.383:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=67ms
2017-05-17 10:23:54.699:INFO:oejsh.ContextHandler:main: Started 
o.e.j.w.WebAppContext@52a86356{/onboarding,file:///var/lib/jetty/temp/jetty-0.0.0.0-8181-onboarding-fe-1.0.0.war-_onboarding-fe-1.0.0-any-3940833158422955661.dir/webapp/,AVAILABLE}{/onboarding-fe-1.0.0.war}

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

2017-05-17 Thread Elhay Efrat
Could you please check you Cassandra Docker if it's up or down

From: ajay.priyadar...@ril.com [mailto:ajay.priyadar...@ril.com]
Sent: Wednesday, May 17, 2017 4:58 PM
To: Elhay Efrat ; onap-discuss@lists.onap.org
Subject: RE: SDC portal is not accessible with 502 error

These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

2017-05-17 10:23:54.033:INFO:oejs.SetUIDListener:main: Setting umask=02
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:9443}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:54.053:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:54.055:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:54.070:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:54.383:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=67ms
2017-05-17 10:23:54.699:INFO:oejsh.ContextHandler:main: Started 
o.e.j.w.WebAppContext@52a86356{/onboarding,file:///var/lib/jetty/temp/jetty-0.0.0.0-8181-onboarding-fe-1.0.0.war-_onboarding-fe-1.0.0-any-3940833158422955661.dir/webapp/,AVAILABLE}{/onboarding-fe-1.0.0.war}
2017-05-17 10:23:57.821:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=2254ms
2017-05-17 10:23:59.533:INFO:oejsh.ContextHandler:main: S

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

2017-05-17 Thread Ajay.Priyadarshi
These are stderr logs. If needed more logs I can attach error logs as well.

BE log:

2017-05-17 10:23:05.852:INFO:oejs.SetUIDListener:main: Setting 
umask=02
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
2017-05-17 10:23:05.888:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:8443}
2017-05-17 10:23:05.889:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:05.890:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:05.892:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:05.908:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:14.027:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=5987ms
2017-05-17 10:23:15.089:INFO:c0.0:main: No Spring WebApplicationInitializer 
types detected on classpath
2017-05-17 10:23:16.275:INFO:c0.0:main: Initializing Spring root 
WebApplicationContext
10:23:17,387  INFO plugins:149 - [371d43040623] loaded [shield], sites []
10:23:17,622  INFO transport:80 - [371d43040623] Using 
[org.elasticsearch.shield.transport.ShieldClientTransportService] as transport 
service, overridden by [shield]
10:23:17,623  INFO transport:96 - [371d43040623] Using 
[org.elasticsearch.shield.transport.netty.ShieldNettyTransport] as transport, 
overridden by [shield]
2017-05-17 10:24:18.085:WARN:oejw.WebAppContext:main: Failed startup of context 
o.e.j.w.WebAppContext@52a86356{/,file:///var/lib/jetty/temp/jetty-0.0.0.0-8080-catalog-be-1.0.0.war-_catalog-be-1.0.0-any-771472197387554835.dir/webapp/,UNAVAILABLE}{/catalog-be-1.0.0.war}
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'product-operation': Unsatisfied dependency expressed 
through field 'componentInstanceOperation'; nested exception is 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'component-instance-operation': Unsatisfied dependency 
expressed through field 'resourceOperation'; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'resource-operation': Injection of resource dependencies failed; 
nested exception is org.springframework.beans.factory.BeanCreationException: 
Error creating bean with name 'component-cache': Injection of resource 
dependencies failed; nested exception is 
org.springframework.beans.factory.BeanCreationException: Error creating bean 
with name 'component-cassandra-dao': Invocation of init method failed; nested 
exception is java.lang.RuntimeException: Artifact keyspace [sdccomponent] 
failed to connect with error : KEYSPACE_NOT_CONNECTED
at 
org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor$AutowiredFieldElement.inject(AutowiredAnnotationBeanPostProcessor.java:592)


FE log:

2017-05-17 10:23:54.033:INFO:oejs.SetUIDListener:main: Setting umask=02
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Opened 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.0.0:9443}
2017-05-17 10:23:54.052:INFO:oejs.SetUIDListener:main: Setting GID=999
2017-05-17 10:23:54.053:INFO:oejs.SetUIDListener:main: Setting UID=999
2017-05-17 10:23:54.055:INFO:oejs.Server:main: jetty-9.3.15.v20161220
2017-05-17 10:23:54.070:INFO:oejdp.ScanningAppProvider:main: Deployment monitor 
[file:///var/lib/jetty/webapps/] at interval 1
2017-05-17 10:23:54.383:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=67ms
2017-05-17 10:23:54.699:INFO:oejsh.ContextHandler:main: Started 
o.e.j.w.WebAppContext@52a86356{/onboarding,file:///var/lib/jetty/temp/jetty-0.0.0.0-8181-onboarding-fe-1.0.0.war-_onboarding-fe-1.0.0-any-3940833158422955661.dir/webapp/,AVAILABLE}{/onboarding-fe-1.0.0.war}
2017-05-17 10:23:57.821:INFO:oeja.AnnotationConfiguration:main: Scanning 
elapsed time=2254ms
2017-05-17 10:23:59.533:INFO:oejsh.ContextHandler:main: Started 
o.e.j.w.WebAppContext@35ef1869{/sdc1,file:///var/lib/jetty/temp/jetty-0.0.0.0-8181-catalog-fe-1.0.0.war-_catalog-fe-1.0.0-any-4644672237465305283.dir/webapp/,AVAILABLE}{/catalog-fe-1.0.0.war}
2017-05-17 10:23:59.540:INFO:oejs.AbstractConnector:main: Started 
ServerConnector@643b1d11{HTTP/1.1,[http/1.1]}{0.0.0.0:8181}
2017-05-17 10:23:59.544:INFO:oejus.SslContextFactory:main: 
x509=X509@6ecab872(jetty,h=[jetty.eclipse.org],w=[]) for 
SslContextFactory@48eb9836(file:///var/lib/jetty/etc/keystore,file:///var/lib/jetty/etc/keystore)
2017-05-17 10:23:59.552:INFO:oejus.SslContextFactory:main: 
x509=X509@6c518474(mykey,h=[],w=[]) for 
SslContextFactory@48eb9836(file:///var/lib/jetty/etc/keystore,file:///var/lib/jetty/etc/keystore)
2017-05-17 10:23:59.563:INFO:oejs.AbstractConnector:main: Started 
ServerConnector@2ef5e5e3{SSL,[ssl, http/1.1]}{0.0.

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

2017-05-17 Thread Elhay Efrat
Could you please share BE and FE log ?


From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of 
ajay.priyadar...@ril.com
Sent: Wednesday, May 17, 2017 4:20 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] SDC portal is not accessible with 502 error

Hello team,

We are installing ONAP on Red Hat OSP-10 .

My portal is accessible while trying to access the SDC, I am getting 502 bad 
gateway (attached image). What are the possible reasons of this error.
I tried to access the page directly and getting same response.

[cid:image001.jpg@01D2CF2C.592C93D0]


Regards,
Ajay Kr. Priyadarshi
SDM QA Team
Reliance Jio Infocomm Limited
Mobile: +91-9958880174
Direct : 1246625832
VOIP : 11832


"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s), are confidential and may be 
privileged. If you are not the intended recipient, you are hereby notified that 
any review, re-transmission, conversion to hard copy, copying, circulation or 
other use of this message and any attachments is strictly prohibited. If you 
are not the intended recipient, please notify the sender immediately by return 
email and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. The company cannot accept responsibility 
for any loss or damage arising from the use of this email or attachment."
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] Query on vlb_ipaddr parameter of vLB usecase

2017-05-17 Thread Kedar Ambekar
Hi Daniel,

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

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

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

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

Yeah, that's how testing does it.

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

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

Hi Daniel,

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

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

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

We did thinks a bit bifferent for vlb vs vfw, here robot treats the packet gen 
as a tool to test the use case. This is actually closer to being how real vnfs 
would be tested as most real vnfs would not have a packet gen included in their 
base heat template.


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

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

Hi ,

packet_gen_vlb_rackspace.env file of vLB use case has this parameter.

vlb_ipaddr: INSERT THE PUBLIC ADDRESS OF THE vLB HERE

To fill this, the vLB VM needs to be instantiated first.

What all Heat templates should be part of the zip file to be uploaded while 
defining a new Vendor Software Product in case of vLB ? Only 
dnsscaling_rackspace and base_vlb_rackspace first and then separately 
packet_gen_vlb_rackspace ? If this understanding is correct, then there will be 
2 Heat stacks for vLB  usecase ?

Regards,
KeDar



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.



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


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

2017-05-17 Thread Ajay.Priyadarshi
Hello team,

We are installing ONAP on Red Hat OSP-10 .

My portal is accessible while trying to access the SDC, I am getting 502 bad 
gateway (attached image). What are the possible reasons of this error.
I tried to access the page directly and getting same response.

[cid:image001.jpg@01D2CF3E.5B48DEF0]


Regards,
Ajay Kr. Priyadarshi
SDM QA Team
Reliance Jio Infocomm Limited
Mobile: +91-9958880174
Direct : 1246625832
VOIP : 11832

"Confidentiality Warning: This message and any attachments are intended only 
for the use of the intended recipient(s). 
are confidential and may be privileged. If you are not the intended recipient. 
you are hereby notified that any 
review. re-transmission. conversion to hard copy. copying. circulation or other 
use of this message and any attachments is 
strictly prohibited. If you are not the intended recipient. please notify the 
sender immediately by return email. 
and delete this message and any attachments from your system.

Virus Warning: Although the company has taken reasonable precautions to ensure 
no viruses are present in this email. 
The company cannot accept responsibility for any loss or damage arising from 
the use of this email or attachment."
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss


Re: [onap-discuss] [onap-tsc] Project Proposal: External SystemRegister

2017-05-17 Thread GILBERT, MAZIN E (MAZIN E)
LiZi,

Thanks for putting the proposal together. The TSC will be continuing a review 
cycle over the next 2 weeks.
I realize the difference and the need of having a system register for external 
communications,
but the question is whether this should be a separate project that may cause 
further dilution.
If the technology and the algorithms used for supporting ESR are similar to 
others like those
used in A&AI, but the type of data is different then I don’t see the need for 
separate systems.

I can see many situations like life cycle management of VNFs using closed loop 
automation where
doing post health checks are critical after repairing a failure. So having both 
platform and external system
data available in one place are key.

In general, the TSC will look very closely on projects that need merger to help 
unify the community
and strengthen the developer ecosystem. You are getting good feedback from the 
community and
I suggest you look closer.

Regards,
Mazin




On May 17, 2017, at 5:31 AM, li.z...@zte.com.cn 
wrote:

Hi Avi,

ESR will not only store and manage configuration of VIM, but also the 
configuration of VNFM/SDNC/EMS. It provides a service to centralized management 
of the information of different kinds of external systems. And it will be used 
by SO/SDC/VF-C etc.
When comes to multi-vim, we suggest that multi-vim using ESR as a dependency 
component, obtaining the connect information and status of VIM from ESR. For 
this point, we can have a further discussion.


Best regards,

LiZi




原始邮件
发件人: <avi.chap...@amdocs.com>;
收件人: <dr6...@att.com>;李滋00164331; 
<jpianigi...@juniper.net>;
抄送人: <onap-discuss@lists.onap.org>; 
<onap-...@lists.onap.org>;
日 期 :2017年05月17日 00:31
主 题 :RE: [onap-tsc] [onap-discuss] Project Proposal: External SystemRegister

Hi,

Reading the project scope it seems to me a real time configuration repository 
for external system location and credential specifically for VIM.
Probably this should be part of the multi-vim project which should own and 
manage this configuration.

I assume that  the component which is used for  storing/managing this 
configuration can be shared across different projects and/or might offered to  
be a service  which any component can use.

Avi,


From: onap-tsc-boun...@lists.onap.org 
[mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of ROSE, DANIEL V
Sent: Tuesday, May 16, 2017 6:51 PM
To: li.z...@zte.com.cn; 
jpianigi...@juniper.net
Cc: onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-tsc] [onap-discuss] Project Proposal: External System 
Register

I have to agree with Jacopo and Steve, that’s not business logic that’s basic 
endpoint health checking.

So to clarify on my and their inputs, it still seems like to me that the entire 
scope of this project is covered by some combination of A&AI, ONAP OM or MSB 
depending  on who you ask / how you look at it.

ONAP Operations manager in particular mentions (Which seems to cover most of 
your stuff.)

•  Platform Monitoring & healing: Monitor platform state, Platform health 
checks, fault tolerance and self-healing

Can you please work with someone like David Sauvageau on that project to be 
sure you have no overlap?

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 
li.z...@zte.com.cn
Sent: Tuesday, May 16, 2017 12:49 AM
To: jpianigi...@juniper.net
Cc: onap-discuss@lists.onap.org; 
onap-...@lists.onap.org
Subject: Re: [onap-discuss] [onap-tsc] Project Proposal: External System 
Register


Hi Jacopo,



Thanks for your quick response. The business logic can be information 
verification before store the data to A&AI, and heartbeat detection of the 
system state.

For example, a user sent the authentic url, tenant, username and password of 
VIM to ESR. ESR try to connect the VIM with these information. After authentic 
succeed, ESR store these VIM information to A&AI, do heartbeat detection for 
VIM status and present  the system status to user.



Best regards,

LiZi






原始邮件
发件人: <jpianigi...@juniper.net>;
收件人:李滋00164331;
抄送人: <stephen.terr...@ericsson.com>; 
<onap-...@lists.onap.org>; 
<onap-discuss@lists.onap.org>;
日 期 :2017年05月16日 11:32
主 题 :Re: [onap-tsc] Project Proposal: External System Register


Not clea

Re: [onap-discuss] ONAP deployment with latest images/docker/code - VID issue

2017-05-17 Thread Andrew Fenner
Update:
Based on some feedback this is seen not to be an e2e tested setup so I 
continued to investigate.

I managed to get the authentication_mechanism = BOTH set and the war rebuild so 
I got past that problem. How I am considently asked for my login details and 
when I put them in I get a 404 error.

There is an exception
...
Caused by: java.io.FileNotFoundException: 
http://vid.api.simpledemo.openecomp.org:8080/vid/api/sessionTimeOuts
...

It looks like a v2 is missing on the url but this is more and more looking like 
there is a significant incompatible change between VID and Portal.

So I think this might be part of the cause. Any thoughts of where this should 
come from would be welcome.

I also updated the docker start of the vid with "-e VID_UEB_APP_KEY=ueb_key -e 
VID_UEB_APP_SECRET=ueb_secret" so that it matched up with what was installed in 
the portal (this removed an exception but didn't seem to be important).

I also had to add vm1-message-router to the hosts file of the portal docker 
container

Thanks

/Andrew



From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Andrew Fenner
Sent: 16 May 2017 13:42
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] ONAP deployment with latest images/docker/code - VID 
issue

Hi,

I had deployed previous deployed ONAP based on the branches suggested and got 
the demo working. Then I tried to move to a "latest" software, so I know I 
might be in uncharted waters but I wondered is this the place to get help, 
please point me to other forum if its more apprioriate.

I have the branches etc set as follows
ubuntu@vm1-vid:/opt$ cat /opt/config/artifacts_version.txt 
/opt/config/docker_version.txt /opt/config/gerrit_branch.txt
1.1.0-SNAPSHOT
1.1-STAGING-latest
master

The docker containers download and after one change to the vid_vm_init.sh the 
server seems to be up.
The change
docker run -e VID_MYSQL_DBNAME=vid_openecomp -e 
VID_MYSQL_PASS=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U --name vid-server -p 
8080:8080 --link vid-mariadb:vid-mariadb-docker-instance -d 
$NEXUS_DOCKER_REPO/openecomp/vid:$DOCKER_IMAGE_VERSION
to
docker run -e VID_MYSQL_DBNAME=vid_openecomp_epsdk -e 
VID_MYSQL_PASS=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U --name vid-server -p 
8080:8080 --link vid-mariadb:vid-mariadb-docker-instance -d 
$NEXUS_DOCKER_REPO/openecomp/vid:$DOCKER_IMAGE_VERSION


However once I try to launch the VID from the portal I get the error
2017-05-16 
12:22:50,901|39d38c21-06e7-4bf6-a244-dc1f56e4dab9||http-apr-8080-exec-6||/single_signon.htm|292b461a-2954-4b63-a3f9-f916c7ad3bc0|WARN|INFORMATIONAL|172.17.0.3|9e55538716e8
 Handler execution resulted in exception: required key 
[authentication_mechanism] not found

This seems to be related the lack on an attribute
authentication_mechanism = BOTH
in the 
/opt/vid/epsdk-app-onap/src/main/webapp/WEB-INF/fusion/conf/fusion.properties

I also got the error
2017-05-16 
12:08:53,961|||localhost-startStop-1ERROR|INFORMATIONAL|172.17.0.3|9e55538716e8||org.openecomp.portalsdk.core.util.SystemProperties||
 getProperty: environment is null, should never happen!
Which is a bit worrying.

It looks like I'm not getting a consistent set of downloads and I was looking 
for any advice on how to proceed

SDC seems to be working and I got a Service distributed to A&AI so a lot of the 
latest seems to have worked so that is why I was hoping to get past this issue 
with VID.

Thanks

/Andrew


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


Re: [onap-discuss] [onap-tsc] Project Proposal: External SystemRegister

2017-05-17 Thread li.zi30
Hi Avi,





ESR will not only store and manage configuration of VIM, but also the 
configuration of VNFM/SDNC/EMS. It provides a service to centralized management 
of the information of different kinds of external systems. And it will be used 
by SO/SDC/VF-C etc.


When comes to multi-vim, we suggest that multi-vim using ESR as a dependency 
component, obtaining the connect information and status of VIM from ESR. For 
this point, we can have a further discussion.




Best regards,

LiZi














原始邮件



发件人: <avi.chap...@amdocs.com>
收件人: <dr6...@att.com>李滋00164331 <jpianigi...@juniper.net>
抄送人: <onap-discuss@lists.onap.org> <onap-...@lists.onap.org>
日 期 :2017年05月17日 00:31
主 题 :RE: [onap-tsc] [onap-discuss]   Project Proposal: External 
SystemRegister







Hi,


 


Reading the project scope it seems to me a real time configuration repository 
for external system location and credential specifically for VIM.


Probably this should be part of the multi-vim project which should own and 
manage this configuration.


 


I assume that  the component which is used for  storing/managing this 
configuration can be shared across different projects and/or might offered to  
be a service  which any component can use.


 


Avi,


 


 



From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of ROSE, DANIEL V
 Sent: Tuesday, May 16, 2017 6:51 PM
 To: li.z...@zte.com.cn jpianigi...@juniper.net
 Cc: onap-discuss@lists.onap.org onap-...@lists.onap.org
 Subject: Re: [onap-tsc] [onap-discuss] Project Proposal: External System 
Register




 


I have to agree with Jacopo and Steve, that’s not business logic that’s basic 
endpoint health checking.


 


So to clarify on my and their inputs, it still seems like to me that the entire 
scope of this project is covered by some combination of A&AI, ONAP OM or MSB 
depending  on who you ask / how you look at it.


 


ONAP Operations manager in particular mentions (Which seems to cover most of 
your stuff.)


 


·  Platform Monitoring & healing: Monitor platform state, Platform health 
checks, fault tolerance and self-healing


 


Can you please work with someone like David Sauvageau on that project to be 
sure you have no overlap?


 


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 li.z...@zte.com.cn
 Sent: Tuesday, May 16, 2017 12:49 AM
 To: jpianigi...@juniper.net
 Cc: onap-discuss@lists.onap.org onap-...@lists.onap.org
 Subject: Re: [onap-discuss] [onap-tsc] Project Proposal: External System 
Register


 

Hi Jacopo,

 

Thanks for your quick response. The business logic can be information 
verification before store the data to A&AI, and heartbeat detection of the 
system state. 

For example, a user sent the authentic url, tenant, username and password of 
VIM to ESR. ESR try to connect the VIM with these information. After authentic 
succeed, ESR store these VIM information to A&AI, do heartbeat detection for 
VIM status and present  the system status to user. 

 

Best regards,

LiZi

 

 

 


原始邮件



发件人: <jpianigi...@juniper.net>



收件人:李滋00164331



抄送人: <stephen.terr...@ericsson.com> <onap-...@lists.onap.org> 
<onap-discuss@lists.onap.org>



日 期 :2017年05月16日 11:32



主 题 :Re: [onap-tsc] Project Proposal: External System Register




 


Not clear what the business logic is.
 
 Sent from my iPhone




 On May 15, 2017, at 8:21 PM, "li.z...@zte.com.cn" <li.z...@zte.com.cn> wrote:


Hi Jacopo, Steve:

 

Actually, ESR has some business logic to deal with about external system, such 
as information verification,  which is out the scope of A&AI. When comes to the 
realization, ESR will be realized relying on A&AI (store the external system 
data in A&AI). 

 

Thanks,

LiZi

 

 

 

 

 




 



发件人: <jpianigi...@juniper.net>



收件人: <stephen.terr...@ericsson.com>李滋00164331   <onap-...@lists.onap.org> 
<onap-discuss@lists.onap.org>



日 期 :2017年05月16日 01:19



主 题 :RE: [onap-tsc] Project Proposal: External System Register




 


Hi,


I would agree with Steve about the need to limit overlap between subprojects


Jacopo  



From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] 
On Behalf Of Stephen Terrill
 Sent: Monday, May 15, 2017 10:10 AM
 To: li.z...@zte.com.cn onap-...@lists.onap.org onap-discuss@lists.onap.org
 Subject: Re: [onap-tsc] Project Proposal: External System Register




 


Hi,


 


While I agree with the need of the external elements to be registered, is there 
a reason for why we need a separate  register in addition to A&AI? (note: I saw 
that Catherine   had a comment with a similar lines).  It may also relate to 
catalogue - LiZi, have you had a chance to chat with the A&AI Project 
(https://wiki.onap.org/pages/viewpage.action?pageId=3246952).


 


Best Regards,


 


Steve.


 


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

Re: [onap-discuss] ONAP deployment with latest images/docker/code - VID issue

2017-05-17 Thread Andrew Fenner
Update:
Based on some feedback this is seen not to be an e2e tested setup so I 
continued to investigate.

I managed to get the authentication_mechanism = BOTH set and the war rebuild so 
I got past that problem. How I am considently asked for my login details and 
when I put them in I get a 404 error.

There is an exception
...
Caused by: java.io.FileNotFoundException: 
http://vid.api.simpledemo.openecomp.org:8080/vid/api/sessionTimeOuts
...

So I think this might be part of the cause. Any thoughts of where this should 
come from would be welcome.

I also updated the docker start of the vid with "-e VID_UEB_APP_KEY=ueb_key -e 
VID_UEB_APP_SECRET=ueb_secret" so that it matched up with what was installed in 
the portal (this removed an exception but didn't seem to be important).

I also had to add vm1-message-router to the hosts file of the portal docker 
container

Thanks

/Andrew



From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Andrew Fenner
Sent: 16 May 2017 13:42
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] ONAP deployment with latest images/docker/code - VID 
issue

Hi,

I had deployed previous deployed ONAP based on the branches suggested and got 
the demo working. Then I tried to move to a "latest" software, so I know I 
might be in uncharted waters but I wondered is this the place to get help, 
please point me to other forum if its more apprioriate.

I have the branches etc set as follows
ubuntu@vm1-vid:/opt$ cat /opt/config/artifacts_version.txt 
/opt/config/docker_version.txt /opt/config/gerrit_branch.txt
1.1.0-SNAPSHOT
1.1-STAGING-latest
master

The docker containers download and after one change to the vid_vm_init.sh the 
server seems to be up.
The change
docker run -e VID_MYSQL_DBNAME=vid_openecomp -e 
VID_MYSQL_PASS=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U --name vid-server -p 
8080:8080 --link vid-mariadb:vid-mariadb-docker-instance -d 
$NEXUS_DOCKER_REPO/openecomp/vid:$DOCKER_IMAGE_VERSION
to
docker run -e VID_MYSQL_DBNAME=vid_openecomp_epsdk -e 
VID_MYSQL_PASS=Kp8bJ4SXszM0WXlhak3eHlcse2gAw84vaoGGmJvUy2U --name vid-server -p 
8080:8080 --link vid-mariadb:vid-mariadb-docker-instance -d 
$NEXUS_DOCKER_REPO/openecomp/vid:$DOCKER_IMAGE_VERSION


However once I try to launch the VID from the portal I get the error
2017-05-16 
12:22:50,901|39d38c21-06e7-4bf6-a244-dc1f56e4dab9||http-apr-8080-exec-6||/single_signon.htm|292b461a-2954-4b63-a3f9-f916c7ad3bc0|WARN|INFORMATIONAL|172.17.0.3|9e55538716e8
 Handler execution resulted in exception: required key 
[authentication_mechanism] not found

This seems to be related the lack on an attribute
authentication_mechanism = BOTH
in the 
/opt/vid/epsdk-app-onap/src/main/webapp/WEB-INF/fusion/conf/fusion.properties

I also got the error
2017-05-16 
12:08:53,961|||localhost-startStop-1ERROR|INFORMATIONAL|172.17.0.3|9e55538716e8||org.openecomp.portalsdk.core.util.SystemProperties||
 getProperty: environment is null, should never happen!
Which is a bit worrying.

It looks like I'm not getting a consistent set of downloads and I was looking 
for any advice on how to proceed

SDC seems to be working and I got a Service distributed to A&AI so a lot of the 
latest seems to have worked so that is why I was hoping to get past this issue 
with VID.

Thanks

/Andrew


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