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

Hi Daniel, Just as you said what ONAP Operations manager care is " Platform Monitoring & healing: Monitor platform state, Platform health checks, fault tolerance and self-healing". It is about the ONAP system. And the ONAP Operations manager will not only check the state of platform, but al

Re: [onap-tsc] Release Naming

I could not agree more! To use "famous cities around world" instead of "famous cities belonging to platinum members" would bring two benifits: 1. avoid non-continuous naming which may confuse user why we jump from Release E to Release H and where is Release F? 2. use real famous cities to avo

Re: [onap-tsc] Release Naming

Hi Mazin, I prefer #1. Because the city name can be recognized by broader community members and outside users of ONAP compared to the other options. ZTE City would like to change Tianjin to Chengdu, giant panda hometown. Thanks, Zhaoxing 原始邮件 发件人： ＜ma...@

Re: [onap-tsc] Thoughts on next steps.

"For MSB: I agree this should be part of CCF. It could be used by DCAE and OOM." Huabing： MSB and CCF are different and their scope are not overlapping. From the project description of CCF, it will provide "a common set of reusable code that can be used across multiple controllers", it

[onap-tsc] 答复: Re: Thoughts on next steps.

We understand the DCAE provide the framework and Holmes can be a sub-project as one DCAE special application project. We can image there will be more and more DCAE applications in more areas in the further. In this case, we wish DCAE project as framework and the 'Holmes' as a application proje

Re: [onap-tsc] Release Naming

Thanks, Mazin, for sharing this innovation with us. Option 1 is preferred. Xinhui From: on behalf of "GILBERT, MAZIN E (MAZIN E)" Date: Wednesday, 17 May 2017 at 1:23 AM To: onap-tsc Subject: [onap-tsc] Release Naming Team, I have two proposals for release naming. One from Rueben Klein an

Re: [onap-tsc] Project Proposal: VF-C

Sorry for the confusion. Correction on the proposal page: https://wiki.onap.org/display/DW/VF-C%3A+Virtual+Function+Controller From: Lingli Deng [mailto:denglin...@chinamobile.com] Sent: 2017年5月17日 9:43 To: 'onap-tsc@lists.onap.org' Subject: [onap-tsc] Project Proposal: VF-C Dear ONAP T

Re: [onap-tsc] Proposal: Architecture Subcommittee

Hi guys, It seems people do want to place to group architecture discussion, but have different opinions on what to cover, how to conduct and what would be the output. My take from open source community is that whoever contributes speaks louder and the TSC committee or its sub-committees

Re: [onap-tsc] 答复: Release Naming

Hi All, I am not a TSC member, but just want to share a thought. I think you should modify first option "famous cities belonging to platinum members" to "famous cities around the world", because platinum members are not permanent and can change in future. Thanks Anil On Tue, May 16, 2017 at 6:37

[onap-tsc] Project Proposal: VF-C

Dear ONAP TSC, We would like to formally propose the VF-C project for ONAP. The proposal wiki page, which includes details of the project description, project scope, and proposed repo names, can be found at: VF-C: Virtual Function Controller https://wiki.onap.org/display/DW/VF-C The

[onap-tsc] 答复: Release Naming

hi MAZINE, I’m not a TSC member but I prefer Option 1 Chengdu is one of the major ZTE RD locations, which is also a beautiful travel city and can be recommanded as the location. Best Regards Maopeng 原始邮件 发件人： ＜ma...@research.att.com＞ 收件人： ＜onap-tsc@lists.onap.org＞ 日 期 ：2017年05

[onap-tsc] 答复: Re: 答复: Service Orchestrator project proposal

Hi DeWayne, Do you mean that this project proposal should support option 1 and option 2( integrated with VF-C)? If it is ture, the project proposal should be changed. Best Regards Maopeng 原始邮件 发件人： ＜dewa...@gigaspaces.com＞ 收件人：张茂鹏10030173 抄送人： ＜onap-tsc@lists.onap.org＞ 日 期 ：2

Re: [onap-tsc] 答复: Service Orchestrator project proposal

Hi guys, Please correct me if I am wrong. But I do not think we have a hard deadline for amendments to project proposal, until it is formal approval. Lingli From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of DeWayne Filppi Sent: 2017年5月1

Re: [onap-tsc] Release Naming

Prefer #1 Xiaojun From: Lingli Date: 2017-05-17 05:28 To: GILBERT, MAZIN E (MAZIN E) CC: onap-tsc Subject: Re: [onap-tsc] Release Naming Hi Mazin, I prefer the first option. As famous conductors are not as famous as the cities, and easily to pronounce and remember to Asian people. Thanks,

Re: [onap-tsc] Release Naming

Suggest option 2. We are dealing with the domain of Orchestration :) and actually, much beyond. thanks & regards, Dhananjay Pavgi Mobile : +91 98220 22264 [cid:image002.png@01CE7323.F2727500] [ONAP_logo_Sig] www.techmahindra.com Platinum

Re: [onap-tsc] Thoughts on next steps.

+1. I like this approach given our focus to get a good release out in Nov. From: on behalf of "Haiby, Ranny (Nokia - US/San Jose USA)" Date: Tuesday, May 16, 2017 at 2:10 PM To: "RATH, CHRISTOPHER A (CHRISTOPHER A)" , "SPATSCHECK, OLIVER (OLIVER)" , onap-tsc Subject: Re: [onap-tsc] Thoughts

Re: [onap-tsc] Release Naming

Team,  I have two  proposals for release naming. One from Rueben Klein and the other from Gildas Lanilis. The first is famous cities belonging to platinum members, and the other is famous conductors in  the domain of orchestrating:-) Both follow the alphabet style. Please review and share com

Re: [onap-tsc] Thoughts on next steps.

@Oliver - I share your concern about having 32 projects and gating the release with deliverables from each one. What I would like to propose is categorization of "core" and "non-core" (or a less derogatory name) projects. Core projects are those that provide the minimum viable product functiona

Re: [onap-tsc] Proposal: Architecture Subcommittee

Hi, My view is that architecture alignment is needed and in particular during this formative phase. I think that during this phase, the architecture output will be listened to irrespective of the organizational approach we have. I would like, however, that the projects have freedom within the

Re: [onap-tsc] Thoughts on next steps.

For the areas in which I have contributions to consider, here are some clarifications. First, the Common Controller Framework should have overlap as far as scope with a lot of projects. That is the point of that project, to find overlapping functionality, develop it in a single project, and re

[onap-tsc] Thoughts on next steps.

I just went through the proposals and noticed that quite a few of them have not clearly defined boundaries between them which makes me wonder if they overlap (see table below). From experience overlapping project definitions rarely lead to good outcomes (duplicate work gets done and people are

[onap-tsc] ONAP Extensibility Project Proposal

Dear ONAP TSC Members, We would like to formally propose the ONAP extensibility project. This project will describe and define requirements, guidelines and tools for extending ONAP. As you know, one of the major problem we encounter with large open source projects like ONAP, is the – sometime i

Re: [onap-tsc] Release Naming

Option 2 From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of Gadiyar, Rajesh Sent: Tuesday, May 16, 2017 11:23 AM To: Alla Goldner ; GILBERT, MAZIN E (MAZIN E) ; onap-tsc Subject: Re: [onap-tsc] Release Naming Option 2 (Famous Conductors) is my choice as

Re: [onap-tsc] Release Naming

Option 2 (Famous Conductors) is my choice as well. BTW, just as an FYI, Irvine is not a major Intel site ☺ If you decide to go the option 1 route: Hillsboro, Chandler, Santa Clara, Haifa are better options. From: on behalf of Alla Goldner Date: Tuesday, May 16, 2017 at 10:58 AM To: "GILBERT,

Re: [onap-tsc] Release Naming

Second option, in my view. Best regards, Alla Goldner Open Network Division Amdocs Technology [cid:image001.png@01D2CE87.19BB2E50] From: onap-tsc-boun...@lists.onap.org [mailto:onap-tsc-boun...@lists.onap.org] On Behalf Of GILBERT, MAZIN E (MAZIN E) Sent: Tuesday, May 16, 2017 8:23 PM To: on

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

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 fo

Re: [onap-tsc] Release Naming

Hello I prefer option 2 Best Jamil Le 16 mai 2017 à 19:23, GILBERT, MAZIN E (MAZIN E) mailto:ma...@research.att.com>> a écrit : Team, I have two proposals for release naming. One from Rueben Klein and the other from Gildas Lanilis. The first is famous cities belonging to platinum members, and

Re: [onap-tsc] Release Naming

I’m not a TSC member but I prefer Option 2 (Also, for Bell Canada, I think it should reflect Montreal, not Ottawa.) > On May 16, 2017, at 1:23 PM, GILBERT, MAZIN E (MAZIN E) > wrote: > > Team, > > I have two proposals for release naming. One from Rueben Klein and the other > from Gildas Lan

[onap-tsc] Release Naming

Team, I have two proposals for release naming. One from Rueben Klein and the other from Gildas Lanilis. The first is famous cities belonging to platinum members, and the other is famous conductors in the domain of orchestrating:-) Both follow the alphabet style. Please review and share comments

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

Re: [onap-tsc] 答复: Service Orchestrator project proposal

Maopeng, The rationale behind option 1 vs option 2 was based on participant input at the time. As far as I know, the time has passed for new project proposals. I suppose it is conceivable with enough committers that both options could be pursued in parallel. The proposal is submitted however.

[onap-tsc] ONAP Proposed Project - Authentication and Authorization Framework

Team, Please review the proposed ONAP project. * Name: Authentication and Authorization Framework * https://wiki.onap.org/display/DW/Authentication+and+Authorization+Framework Thanks, Ram _

[onap-tsc] ONAP Proposed Project - DMaaP – Data movement as a platform

Team, Please review the proposed ONAP project. · Name: DMaaP – Data movement as a platform · https://wiki.onap.org/pages/viewpage.action?pageId=3247130 Thanks, Ram ___ ONAP-TSC mailing list ONAP-TSC@lists.onap.org https://lists.onap.org/mailm

Re: [onap-tsc] Proposal: Architecture Subcommittee

Hi Steve, That is the point, project perspective brings more of authorative in nature, to support different projects align as directed by arch. committee. And I tried to suggest the project repo here, helps to store the artifacts, which are approved the project’s committers. Also it keeps track

Re: [onap-tsc] [onap-discuss] How to best populate Contributors and Committers in newly formed ONAP projects

My 2 cents… It is preferable to have at least 2 Committers show approval (with a +1) for a contribution before it is accepted into the repository. It is also a best practice to never have a Committer review and/or approve their own contribution into the repository. -

Re: [onap-tsc] Policy Framework Project Proposal

Sven, We have submitted the proposal already to the tsc as of 5/11 – Phil Robb marked it with that date. We hope to hear from the TSC within the next week or so to determine if it is accepted. Since we are not officially accepted yet, let’s keep our comments on the wiki page itself right now.

Re: [onap-tsc] Policy Framework Project Proposal

Thanks a lot Pam! I have added Ericsson contributors. We are currently discussion committers as well (hopefully finalising that in the next few days). Two questions: * When do you plan to submit the proposal? * What is your preferred method of commenting/contributing to your

[onap-tsc] Project Proposal: DMaaP

Dear ONAP TSC, We would like to formally propose the DMaaP project for ONAP. The proposal wiki page, which includes details of the project description, project scope, and proposed repo names, can be found at: DMaaP - Data Movement as a Platform https://wiki.onap.org/pages/viewpage.action?pageId=

[onap-tsc] Project Proposal: AAF

Dear ONAP TSC, We would like to formally propose the AAF project for ONAP. The proposal wiki page, which includes details of the project description, project scope, and proposed repo names, can be found at: AAF-Authentication and Authorization Framework https://wiki.onap.org/display/DW/Authentic

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

Hi Daniel, I think they're different. What MSB care about is providing a registration/discovery mechanism to facilitate the communication of Microservices, in particular, the Registration/discovery of MSB focus on the access end points of service providers. What ESR provides is the central re