Re: [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-tsc] Project Proposal: ONAP Operations Manager / ONAP onContainers

Hi, Oliver, Please see comments inline. Regards, Helen Chen From: "SPATSCHECK, OLIVER" Date: Wednesday, May 10, 2017 at 7:01 PM To: "zhao.huab...@zte.com.cn" Cc: Helen Chen 00725961 , "onap-tsc@lists.onap.org"

Re: [onap-tsc] Project Proposal: ONAP Operations Manager / ONAP onContainers

I guess where I was getting confused is who is managing the micro services themselves. E.g. DCAE uses micro services. The micro services in DCAE are managed by the DCAE controller in terms of life cycle management (turning up the micro services, monitoring the health of the micro service,

Re: [onap-tsc] Project Proposal: ONAP Operations Manager / ONAP onContainers

What Helen said is correct. During the project proposal discussion in the last week, people suggest use "Microservice Framework " instead of "Microservice Bus", that might be the reason of this confusion. "Microservice Framework" or "Microservice Bus" provides a platform to enable service

Re: [onap-tsc] Project Proposal: ONAP Operations Manager / ONAP on Containers

That’s great! Let’s getting in sync on the schedule for these two projects once they are approved by TSC. Integration project would like to leverage OAM’s capabilities for distribution, packaging and lab deployment as well. Regards, Helen Chen From: "Sauvageau, David"

Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO

I agree with Alla - an SME with detailed knowledge and well known in the target external organization is highly desirable as coordinator for ONAP. I have an excellent candidate in mind for ETSI NFV. BTW - ETSI NFV and ETSI MEC are separate bodies. Although several great people I know are

Re: [onap-tsc] Project Proposal: ONAP Operations Manager / ONAP on Containers

One more question. I am wondering what the relationship of the Microservice Framework (https://wiki.onap.org/display/DW/Microservices+Framework) and below is. Below says: >> The OOM addresses the current lack of consistent platform-wide method in >> managing software components, their

Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO

Hi all, A different way to handle this topic is to assign person responsible for each SDO/Open source coordination, same as ETSI NFV have. To me, it makes more sense, as eventually only subject expert knows which topics are discussed in the corresponding SDO/Open Source and how to handle them

Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO

Hi Phil, I agree with the approach and your interpretation. There is an optional field for coordinator follow the instruction as documented in the charter for coordination area creation request in Section 5.1.4.3. And it also references an election process for coordinators in Section

Re: [onap-tsc] Project Proposal: ONAP Operations Manager / ONAP on Containers

Hi, David, Could this manager be used for “Distribution” and “Packaging” of ONAP? Please refer to: https://wiki.onap.org/display/DW/Integration Regards, Helen Chen From: on behalf of "Sauvageau, David" Date: Wednesday, May 10, 2017

[onap-tsc] Project Proposal: ONAP Operations Manager / ONAP on Containers

Deer TSC, I would like to formally propose 2 projects to simplify the deployment and the operations of the ONAP platform and components. Project: ONAP Operations Manager (Formerly ONAP controller) - https://wiki.onap.org/display/DW/ONAP+Operations+Manager This proposal introduces the ONAP

Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO

  Mazin,   Understood.  I see that Lingli also proposed a separate open source coordinator.  Good discussion for tomorrow. Regards,Jason HuntExecutive Software Architect, IBMPhone: +1-314-749-7422Email: djh...@us.ibm.comTwitter: @DJHunt     - Original message -From: "GILBERT, MAZIN E

Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO

Hi Jason, Recall from the discussion last Thursday TSC meeting, it is suggested to have a separate coordinator for opensource communities in addition to SDOs, hence I wrote another proposal separately. I apologize not including the potential list of communities in that prposal for

Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO

Jason The coordinator we use to interact with SDO may need to be different than that for other open source projects. There are short term impacts of our first release on other open source projects like OPNFV, FD.io and Open Stack, etc. Let’s discuss tomorrow in our TSC meeting. As of now, we

[onap-tsc] Project Proposal: ONAP Operations Manager / ONAP on Containers

Dear TSC, I would like to formally propose 2 projects to simplify the deployment and the operations of the ONAP platform and components. Project: ONAP Operations Manager (Formerly ONAP controller) - https://wiki.onap.org/display/DW/ONAP+Operations+Manager This proposal introduces the ONAP

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

  Andrei,   Thank you for bringing this topic up.  It's important that we minimize overlap in projects to maximize the impact of the contributors.   In my basic understanding, VNF-SDK and ICE have substantial overlap.  Can we investigate how these two projects can merge?   As for CLAMP and Policy

Re: [onap-tsc] Creation Request for Coordination Area Standard/SDO

  Good proposal.  Would this coordinator also work with other open source projects?  I'm thinking, in particular, of OPNFV where I think we could have a tight collaboration. Regards,Jason HuntExecutive Software Architect, IBMPhone: +1-314-749-7422Email: djh...@us.ibm.comTwitter: @DJHunt     -

[onap-tsc] Creation Request for Coordination Area Standard/SDO

Coordination Area Description: Open source and standard are compliementing each other. Opensource is playing an increasing important role in SDO practice, which could help to gain industry concensus and adoption. The potential standard bodies and topics include: · IETF

[onap-tsc] Proposal for structuring Modeling projects

Dear all, Currently there are 6 draft projects in ONAP that deal with modeling, onboarding and certification. The below table summarizes the 6 initiatives and presents the feature coverage of each one of them. ONAP Project Features covered by the project VNF/Service Design VNF Guidelines

Re: [onap-tsc] [onap-discuss] [modeling] TOSCA BPMN support proposal at OASIS TOSCA WG

Huabing, I recognize the need in ONAP to support delegation in TOSCA to external workflow engines. I have said this repeatedly, and still am miss-interpreted. This has nothing to do with backward compatibility to TOSCA 1.0, it only has to do with supporting "facts on the ground/existing

Re: [onap-tsc]  [modeling] TOSCA BPMN support proposal at OASIS TOSCA WG

Hi Huabing, et. al. The need to specify imperative workflow “callous” from a TOSCA service template is pretty well understood, both from the enterprise and the telecom use case perspective. In fact, there is already a generic mechanism in TOSCA to support invocation and execution of

[onap-tsc]  [modeling] TOSCA BPMN support proposal at OASIS TOSCA WG

Hi Amir and all, Both OPEN-O and OpenECOMP have used TOSCA for service topology modelling and BPMN/BPEL for lifecycle management process modelling. After the merger, ONAP will inherit the existing codes from OPEN-O and OpenECOMP and continue to use BPMN/BPEL in SO/VF-C. However, I noticed