Re: [onap-discuss] Portal VM failed to brought up widget-ms docker container

Lokesh, Who do you work for? We would like to keep a list of contributing companies. mazin > On Aug 11, 2017, at 7:44 AM, lokesh r wrote: > > Hi, > > I brought all the onap modules through heat orchestration in openstack newton. > In portal VM widget-ms

Re: [onap-discuss] [DCAE] DCAE questions from Usecase UI

Lingli Is this UI use case specific or general for the platform (to be used for VOLTE, vCPE and others). Can you point me to the new platform requirements needed for it? Thanks Mazin Sent through AT's fastest network On Aug 13, 2017, at 7:04 PM, Lingli

Re: [onap-discuss] Draft of TSC Charter Section 5.4.1 Changes

Thank you Kenny, I encourage the ONAP community to review the proposed changes below and provide feedback. We want to finalize this in one week. The TSC will then review and vote. Mazin On Jul 24, 2017, at 5:53 PM, Kenny Paul >

[onap-discuss] #PTL

PTL Team, Some projects have made an outstanding job on reducing and cleaning-up the committers' list. Please review committers in your project and approach them to ensure their commitment and appropriate role in your project. Let’s stick to up-to 2 committers per company. Phil and I will

Re: [onap-discuss] [onap-tsc] sdc committers

Yuan Yue, I have not examined this particular project, but the TSC and I have requested last week during the review phase of projects for R1, that the PTLs clean up the list of committers to 3-5, as some are more qualified to be contributors than committers. We have projects with 16-20

[onap-discuss] [onap-tsc] Modelling discussion on Friday May 5th

Rittwik, Deng, This is great. Thank you for taking the lead. I realize the focus is on TOSCA and parsers. Wonderful! I want to take you one level higher to start by discussing what the framework look like for the information model. Perhaps invite folks who have operational experience. Then

Re: [onap-discuss] [onap-tsc] Proposal for structuring Modeling projects

Jason The VNF-SDK and ICE teams are in discussion of a merger and a consolidated plan with co-leadership.At least that is my expectation and hope. CLAMP is for control loop automation. The development and design of templates that drive control loops can be part of SDC, including initial

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

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

Re: [onap-discuss] Tentative July ONAP Developers Face-to-Face Meeting

I was not present for this discussion. We need to have a meeting around the 3rd week of July to go through project by project progress. Phil and I discussed a virtual meeting since folks will be too busy to travel, and some may not be able to. Would like to get a sense from the TSC community if

[onap-discuss] Framework for proposed projects feedback

ONAP Team, I want to thank you again for working so hard in proposing projects. Per our TSC meeting today, I am enclosing the framework that the TSC committee developed for scoring and providing feedback on each project. I expect you will get feedback from the TSC committee starting next week.

[onap-discuss] Projects

Team, First, thank you for spending a week in NJ brainstorming, planning and architecting our next 4Q17 release. Our next step is to have the smaller community teams flush out their project proposals, fill in gaps, and communicate with other teams to consolidate proposals in the case of

[onap-discuss] TSC F2F meeting in Paris

ONAP Community, We are really excited about our next face to face meeting in Paris, hosted by Nokia. This is a critical meeting as we will review our Amsterdam release and make key decisions about the Beijing release. There are limited spots, so please register at your earliest convenience. The

[onap-discuss] Rewarding committers and coders

ONAP Community, I hope you are enjoying what remains of the summer. I wanted to kick off a discussion on ideas for rewarding top committers and coders. How often we should do this, type of rewards, ideas on promoting diversity, bases for the rewards (lines, commits, etc). Should we introduce

Re: [onap-discuss] ~

Srini, So that the ONAP community can better support you and the user community, it would help to know the company each individual works for. This will help the Linux Foundation to better report their statistics on progress. thanks Mazin On Aug 24, 2017, at 3:06 PM, Srinivasa Goda

Re: [onap-discuss] So pass M4

Congratulations to the SO team. Well done. Mazin On Oct 9, 2017, at 1:47 AM, Seshu m > wrote: Thanks Gildas... Best Regards, Seshu ** This

Re: [onap-discuss] newbee question

AS Please identify which company or institute you are part of so we track contributors and inquirers. AT ECOMP and LF ONAP are aligned. Mazin On Nov 15, 2017, at 3:22 PM, Andrey Selivanov via onap-discuss > wrote: Hi! How

[onap-discuss] ONAP Meeting in Santa Clara

Colleagues and Friends, On behalf of the TSC and the LF, I want to congratulate every one of you for your outstanding collaboration in delivering Amsterdam. The goal and timeline were far reaching, but yet this community delivered the impossible. I am truly honored and excited about what we

[onap-discuss] Modeling

Deng Hui, Thanks for your presentation today, and I really appreciate the modeling committee working together. Lots has been accomplished since R1. I just wanted to articulate the conversation main points. 1. Modeling approaches for ONAP releases should be approved by the TSC. This should be

Re: [onap-discuss] [modeling] Help on ONAP R2 Data Modeling verification

Thanks Deng That is surprising. Can each company with strong interest in this offer one coder please. This is a key activity and can’t be coded by 2 coders. This will impact our Casablanca release. Thank you all!! Mazin Sent through AT's fastest network On May 2, 2018, at 6:08 AM, denghui

Re: [onap-discuss] Beijing M1: Status of functional requirements

Thanks Alla. That is great progress, and appreciate the hard work by everyone. Have the software architectures worked on the detailed designs of those requirements with the PTLs to ensure nothing is lost in translation? Can you add to the website the services that will be tested to evaluate

[onap-discuss] MUSIC Proposal for Beijing

TSC Members, I met this afternoon with members of the OOM project and MUSIC team. I confirmed the following Although on the key common area among both projects is resiliency, OOM’s scope is life cycle management of the ONAP platform itself. Scope is the following

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

+1 Please add the candidate’s company plus existing committers. On Jan 11, 2018, at 6:57 PM, MAHER, RANDA > wrote: ***Security Advisory: This Message Originated Outside of AT *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Re: [onap-discuss] ONS Registration Discount for active developers and leadership

Phil, On behalf of the ONAP community and its members, I want to thank you and the LF for making this happen. I expect and hope this will encourage significant participation. Mazin Sent through AT's fastest network On Jan 27, 2018, at 12:47 AM, Phil Robb

Re: [onap-discuss] CLAMP meaning?

Control Loop Automation Management Platform On Feb 12, 2018, at 5:49 AM, Thovalai, Sundar > wrote: Hi Lars The ONAP documentation says Closed Loop Automation Management Platform, so I guess that is the official interpretation of

Re: [onap-discuss] [Onap-usecasesub] [integration] ONAP S3P definition and matrix

This was the goal of the software architect subcommittee or system engineering subcommittee. We agreed that we would have a coordinator instead who would work under the architecture committee and with all PTLs to exercise the S3P criteria and other Beijing requirements. We also agreed last month

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

Thanks Roger. Have there been other groups who have managed to bring up Amsterdam with OOM (with and without DCAE)? Can you point me to any so I can understand their experience. mazin On Jan 3, 2018, at 11:15 AM, Roger Maitland >

Re: [onap-discuss] Modeling

bring it to TSC in next 2 weeks. Thanks a lot DENG Hui From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com] Sent: Wednesday, June 20, 2018 11:33 AM To: denghui (L) mailto:denghu...@huawei.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; ona

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

Deng, I appreciate you holding an election for the PTL. For the modeling project PTL election, we need each Chair to ensure they have vetted all active committers before any election is taking place. Can you share the list of active committers. As outlined in the website the issue is different

Re: [onap-discuss] [onap-tsc] PTL Election announcement for ONAP modeling project

G Hui From: GILBERT, MAZIN E (MAZIN E) [mailto:ma...@research.att.com] Sent: Thursday, July 5, 2018 7:35 PM To: denghui (L) mailto:denghu...@huawei.com>> Cc: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-...@lists.onap.org<mailto:onap-...@lists.onap.org&

[onap-discuss] ONAP subcommittees - reminder.

Team, The TSC has approved a number of subcommittees in the past. I would like to encourage each subcommittee chair to share updates with the TSC on a regular basis - either through email or at the TSC Thursday meetings. It is important that the TSC is knowledgable and agree of the workplan

Re: [onap-discuss] Action Plan towards Casablanca

Thanks Alla for the summary. Here is what we agreed to at the TSC meeting. There are three work plans for Casablanca. The theme is increase deployability of ONAP. 1. Functional requirements and use cases. We agreed to establish an end-user advisory committee that will be driven by the

Re: [onap-discuss] [onap-tsc] Action Plan towards Casablanca

the purpose, scope, membership, etc) so that the TSC can review and vote on it. I think it’s a good idea, but I want to see the details and make sure we follow our documented procedure. Thanks, Chris From: GILBERT, MAZIN E (MAZIN E) To: Alla Goldner; Cc: onap-discuss@lists.onap.org<mail