Re: [onap-discuss] CSAR from SDC

Hi Michael, Could we discuss these questions at today's meeting? Thanks, Huabing Original Mail Sender: To: zhaohuabing10201488 CC: MengZhaoXing10024238YuanHu10090474 Date: 2017/07/17 18:08 Subject: Re:CSAR from SDC +Eden,Zahi Please assit Original Message -

Re: [onap-discuss] [onap-tsc] [ptls][cli][msb][aaf] Review ONAPfunctionalites to support from CLI

Hi Kanagaraj, Sure. Currently, we're mainly using the AAF weekly meeting to discuss the integration between AAF and MSB. The conclusion of the last meeting is that AAF will add a Lua plugin which can provide centralized auth at the MSB external API gateway. I will add you in the loop

[onap-discuss] MSB Integration Guide Slies //Re: Invitation: [msb] Weekly Meeting @ Weekly from8:30pm to 9:30pm on Monday (CST) (onap-discuss@lists.onap.org)

Hi, The slides of this meeting can be downloaded here: https://wiki.onap.org/pages/editpage.action?pageId=8232336 BR, Huabing Original Mail Sender: To: lizi00164331 Date: 2017/07/14 10:05 Subject: [onap-discuss] Invitation: [msb] Weekly Meeting @ Weekly from8:30pm to 9:30

[onap-discuss] Invitation: [openlab] Bi-Weekly Meeting @ Every 2 weeks from 8am to 9am on Wednesday (PDT) (onap-discuss@lists.onap.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02 RRULE:FREQ=YEARLY;BYMONTH

[onap-discuss] Updated Invitation: Use Case Subcommittee Bi-Weekly Meeting @ Every 2 weeks from 7am to 8am on Monday from Mon Jun 19 to Sun Jul 30 (PDT) (onap-discuss@lists.onap.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02 RRULE:FREQ=YEARLY;BYMONTH

[onap-discuss] Updated Invitation: Use Case Subcommittee Bi-Weekly Meeting @ Weekly from 7am to 8am on Monday (PDT) (onap-discuss@lists.onap.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02 RRULE:FREQ=YEARLY;BYMONTH

[onap-discuss] Invitation: [vnfsdk] Weekly Meeting @ Weekly from 6am to 7am on Friday (PDT) (onap-discuss@lists.onap.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02 RRULE:FREQ=YEARLY;BYMONTH

[onap-discuss] What Do You Need From The July Developers Event?

The July Virtual Developers Event is next week and your contributions are what will drive all of these sessions. As Phil Robb mentioned at the close of the PTL call this morning, we are looking to the community to suggest topics for discussion which we will use to build the agenda from. Ideall

Re: [onap-discuss] FW: [onap-tsc] [aai] YOUR ACTION IS REQUIRED: A&AI Project needs new repos for microservices

Hi, CT – Thanks for your feedback – it seems to me that making the process of getting new repos is made difficult by design in order to prevent an explosion of repositories for the LF to manage. There are currently 30 approved projects with several still in proposed state; A&AI alone already h

Re: [onap-discuss] [coding guidelines] Python

Hi Seshu, Thanks for reaching out. Correct I have not provided any specific guidelines for Python. However in wiki, Catherine and Tony have kindly provided recommendations on the Google Style guide at https://google.github.io/styleguide/ Using these guideli

Re: [onap-discuss] [onap-installation] DCAE installation now supported by all Heat templates

Hello Subhash, The env file seems correct. Can you try to rebuild? It may be a transient issue. Are the containers downloaded correctly in those VMs? Did you see anything in the logs of the DCAE docker container? Marco _ From: Subhash Kumar Singh mailto:subhash.ku

Re: [onap-discuss] [onap-installation] DCAE installation now supported by all Heat templates

Hello Marco, We tried to stack ONAP with following properties as specified in environment file[1] (demo:origin/master): artifacts_version: 1.1.0-SNAPSHOT docker_version: 1.1-STAGING-latest gerrit_branch: master artifacts_version: 1.1.0-SNAPSHOT docker_version: 1.1-STAGING-latest gerrit_branch: m

[onap-discuss] [coding guidelines] Python

Hi Gildas, Could you please help us understand if there are any speciifc coding guidelines/styles defined in ONAP for Python for R1. We would be using Python in the SO for ARIA and required to get this clarified. Best Regards, Seshu ***

Re: [onap-discuss] [oom] TOSCA Model Driven Orchestration across Containers and Non-Container Deployment Options

Hi John, I believe one of the action item from the last meeting was to schedule a followup demo of the cloudify implementation. When is the earliest this demo can happen? Would you suggest we do the demo at our weekly meeting? If we want to include such an implementation for the Amsterdam relea

Re: [onap-discuss] [onap-tsc] [ptls][cli][msb][aaf] Review ONAP functionalites to support from CLI

Dear Huabing, CLI project would depends on the MSB for service discovery and AAF for AA. So I have gone thru the MSB release planning from wiki and found that your are planning to integrate AAF as one of the Auth service provider in MSB. IMO, It’s an right integration and as CLI also would get

Re: [onap-discuss] 答复: [Modeling][vfc] TOSCA Parser API Requirements

Hi Yan, My feedback: * Most of the ONAP components, some of them already consume our TOSCA parser (MSO, SDN-C, VID, SDN-GC), are Java-based hence require Java language invoke. * The common use-case we found is that components would like to consume the parser in-process, i.e. get it as