Re: [onap-discuss] Some thoughts about ONAP MicroserviceArchitecture for Casablanca and beyond: Service Mesh,Centralized Authentication and unified API standards

Hi Tal, Good points. You're right, Istio is still not production ready while service mesh approach is very promising, We're trying to set up a demo with ONAP to demonstrate its benefits. I agree that most of the APIs we have now are not "REST", actually sometimes it's difficult to make

Re: [onap-discuss] Some thoughts about ONAP Microservice Architecture for Casablanca and beyond: Service Mesh, Centralized Authentication and unified API standards

Hi Huabing, 1. We have some good experience with Itsio and would love to be part of the conversation. It's one of the things we're looking at, too, in terms of improving ONAP's currently basic containerization. We are starting by looking at OOM but hope to find best practices that could work for

Re: [onap-discuss] Some thoughts about ONAP MicroserviceArchitecture for Casablanca and beyond: Service Mesh, Centralized Authentication and unified API standards

Sounds good! I will edit it and try to be succinct. On Wed, Mar 14, 2018 at 3:26 AM, wrote: > Hi Tal, > > Good points. > >1. > >You're right, Istio is still not production ready while service mesh >approach is very promising, We're trying to set up a demo

Re: [onap-discuss] How to use the internal login, instead of external login in Portal SDK

Hi Manoop, We replaced the URL in the onboarding URLs like below URL = http://1.2.3.4:8080/epsdk-apps-os/welcome.htm REST URL = Blank User = demo Password = demo Then, we replaced the following lines in the WEB-INF/classes/portal.properties file: portal.api.impl.class =

Re: [onap-discuss] [ONAP Helpdesk #53486] [DCAE] requesting DCAE weekly meeting time change

Yes. Thank you very much Kenny! Lusheng Sent via the Samsung Galaxy S7, an AT 4G LTE smartphone Original message From: Kenny Paul via RT Date: 3/13/18 8:37 PM (GMT-05:00) To: "JI, LUSHENG (LUSHENG)" Cc:

Re: [onap-discuss] [ONAP Helpdesk #53486] [DCAE] requesting DCAE weekly meeting time change

Yes. Thank you very much Kenny! Lusheng Sent via the Samsung Galaxy S7, an AT 4G LTE smartphone Original message From: Kenny Paul via RT Date: 3/13/18 8:37 PM (GMT-05:00) To: "JI, LUSHENG (LUSHENG)" Cc:

Re: [onap-discuss] Invitation: 5G Use Case Team Meeting @ Weekly from 8am to 9am on Thursday from Thu Jan 4 to Thu Dec 13 (PST) (onap-discuss@lists.onap.org)

All, Based in the discussions and action items from Use Case Subcommittee call, we need to focus on gathering high level requirements for Casablanca. Here is the proposed agenda for tomorrow’s call. Feel free to suggest changes. Agenda for March 15, 2018 5G Requirements for Casablanca - All

[onap-discuss] [sdc][integration]PNF onboarding and service design

Hi Michael, As we plan for R2 PNF integration test, could you provide us an PNFD sample and show us SDC process of onboarding an PNF and creating service with the PNF? Regards, -Yang ___ onap-discuss mailing list onap-discuss@lists.onap.org

Re: [onap-discuss] oparent 1.1.0 released

Hi Pam, Most of the changes are local to oparent itself and shouldn’t affect downstream projects. The only changes that may affect downstream projects are: · SNAPSHOT dependencies are disallowed in release artifacts (used be warnings only) · sonar-maven-plugin version

Re: [onap-discuss] oparent 1.1.0 released

Hi all, To clarify, please use the release version of oparent "1.1.0", not "1.1.0-SNAPSHOT". In general you should always use only release versions of dependencies that are coming from outside your repo. Thanks, Gary _ From: Gary Wu Sent: Monday,

[onap-discuss] Invitation: [aai] - one-off meeting @ Fri Mar 16, 2018 6am - 7am (PDT) (onap-discuss@lists.onap.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20180316T13Z DTEND:20180316T14Z DTSTAMP:20180314T225936Z ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3

Re: [onap-discuss] [sdc][integration]PNF onboarding and service design

Hi, In SDC we do not have a concept of onboarding for PNF, PNF's are modeled in SDC similar to the VNF. I think we should have a talk with the people responsible for the PNF functionality to create an example with them. BR, [Michael Lando] Michael Lando Software Architect AT Network

[onap-discuss] Unable to get DNS response from vLB

Hi I am setting up vDNS usecase. I have deployed the 3 VMs. I can check the functionality of DNS. But when I am trying to run the command "nslookup hos1.dnsdemo.onap.org 192.168.9.111" from pktgen VM, I couldn't get any response. Even with "nslookup host1.dnsdemo.onap.org 192.168.10.211". I

Re: [onap-discuss] info on vCPE scaling

Eric, Hi, forwarding this one to onap-discuss - I have not seen the vCPE use case in action yet From: eric.dm...@wipro.com [mailto:eric.dm...@wipro.com] Sent: Wednesday, March 14, 2018 14:17 To: Michael O'Brien Subject: info I know you are very busy, if you get a

[onap-discuss] [INT] Robot INIT and Robot InstantiateVFW after Healthcheck ?

Gary, In working with OOM over the last few week it seem like the best way to detect problems is to run the demo-k8s.sh init and then to check via op0001 if SO, AAI and SDNC picked up the models. Usually on a fresh OOM they do not. The repair is to delete the AAI model-loader POD, the SO POD

Re: [onap-discuss] oparent 1.1.0 released

Gary, Were there major changes to oparent that were made? In the past moving to an oparent seemed to cause problems in projects. Thanks, Pam From: on behalf of Gary Wu Date: Monday, March 12, 2018 at 4:46 PM To:

Re: [onap-discuss] [INT] Robot INIT and Robot InstantiateVFW after Healthcheck ?

Gary, My apologies - I will re-calibrate to use "ETE" :) I think OOM is working the dependency issue but not sure of the status/delivery time frame. I suspect we dont need all healthchecks to run for init to work. We might need a new test template to call "Model Distribution From ASDC" which

Re: [onap-discuss] Some thoughts about ONAP MicroserviceArchitecture for Casablanca and beyond: Service Mesh, Centralized Authentication and unified API standards

Hi Huabing, I agree with you service mesh technologies are best as it takes away majority of housekeeping work away from the ONAP service developers – Authenticating peers, Authorization of peers requests, Secure communication (Mutual TLS), visibility and more. Great that you intend to show

Re: [onap-discuss] oparent 1.1.0 released

Hi Dileep, It’s also 1.1.0. Thanks, Gary From: Ranganathan, Dileep [mailto:dileep.ranganat...@intel.com] Sent: Wednesday, March 14, 2018 12:02 PM To: Gary Wu ; DRAGOSH, PAMELA L (PAM) ; onap-discuss@lists.onap.org Subject: RE: [onap-discuss]

Re: [onap-discuss] oparent 1.1.0 released

Hi Gary, What is the version to be used for python projects which inherit from oparent-python? Thanks, Dileep From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Gary Wu Sent: Wednesday, March 14, 2018 10:26 AM To: DRAGOSH, PAMELA L (PAM)

Re: [onap-discuss] [multicloud] Last Call for Feedback of MultiVIM Metrics for VES Requirement

ALOK, Bin and Multi-VIM team; In addition to what is listed in your table, Should the domain be expanded to include collecting matrices from mobility and Transport infrastructure? For example ; Radio, ONUs, SSDs, GPUs, Roadms, Amplifiers, Transponders In addition can " Collector" be also its

[onap-discuss] [aai] AAI weekly meeting for this week

Dear ONAP AAI Team, In order to accommodate the most community members, the team took a vote and decided on Wednesdays at 13:00 UTC (9 AM EDT). This week we will still have our weekly meeting on Friday, 2018-03-16 @ 13:00 UTC (9 AM EDT). I have requested the single session meeting from the LF

Re: [onap-discuss] [aai] AAI weekly meeting for this week

Sounds good –thanks for the heads up Jimmy I would like to goto the first hour of the architecture meet at 9 And the policy meet at 9 (alternate weeks) /michael From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of FORSYTH, JAMES Sent: Wednesday,