Not sure what the process is exactly. I thought I added it to the 10/19 schedule to be discussed then. I didn’t think that the TSC would vote on it that day but would at least put a stamp of approval that yes we need a subcommittee for this. Then perhaps the process starts???
I didn’t really pick up a lot of interest off the TSC mailing list. Perhaps the onap-discuss would be better?? Seems everyone is real busy right now with Amsterdam release. Recommendations? Pam From: Phil Robb <[email protected]> Date: Tuesday, October 17, 2017 at 7:47 AM To: "DRAGOSH, PAMELA L (PAM)" <[email protected]> Cc: onap-tsc <[email protected]>, Kenny Paul <[email protected]> Subject: Re: [onap-tsc] Control Loop Subcommittee Proposal Hi Pam: When did you want this to be discussed/voted-on during a TSC meeting? Assuming the two week socialization period, would you like us to add it to the 10/26 meeting, or did you want to wait and have us schedule it for a meeting after the Amsterdam release? Thanks, Phil. On Wed, Oct 11, 2017 at 9:56 AM, DRAGOSH, PAMELA L (PAM) <[email protected]<mailto:[email protected]>> wrote: Dear TSC, I would like some guidance on the proposal for a Control Loop SubCommittee. This was discussed in Paris F2F at the Control Loop E2E Meeting. We identified a need for a subcommittee to help coordinate the efforts of supporting Control Loops across all the multitude of projects that are involved. Coordination between the project teams proved difficult to manage amongst themselves. Each Use Case for Amsterdam also had slightly different requirements for their respective Control Loops. There needs to be an overarching subcommittee that can manage this effort. This is what I am proposing: Name: Control Loop Subcommittee Purpose: Coordinate the projects involved in implementation of Control Loop for the use cases in each release. Expected Deliverables: • Wiki – One-stop wiki page that can organize all the architectural and flow diagrams expected for the Use Cases targeted for a Release. • Architectural Diagram – Work with Architecture Sub Committee to provide architecture diagrams for Control Loop Design, Instantiation and Runtime Execution. • Flow Diagrams – Work with the relevant project teams to provide Flow Diagrams for creating Control Loops during Design Time Service Design and Flow Diagrams for Control Loop Runtime Instantiation and Execution. • Model definition (In coordination with Modeling, VNFSDK, VNF Requirements Sub Committees) – Coordinate the models for VNF Vendor Recommendations for Control Loops, Models for DCAE Microservices, Models for Policy Configuration/Operational Control Loop Policies, etc. • Project Requirements – Work with required Project teams to ensure commitments and deliverables for Control Loop Use Cases for a release. The Core teams are DCAE/CLAMP/Policy, but ultimately most projects are involved (APPC/VFC/SO/Dmaap/SDC/AAI to name a few). • Integration Testing Requirements – Work with the integration test team to build E2E Testing Scripts for Control Loop Design, Instantiation and Runtime Execution • Documentation Requirements – Work with the documentation team to build documentation on how the community can build, design and test Control Loops. Starting Participants: Pamela Dragosh – AT&T Liam Fallon – Ericsson Gervais-Martial Ngueko – AT&T Guangrong Fu – ZTE Grzegorz Tysczka – Orange Patrick Liu - Huawei Regards, Pamela Dragosh ONAP Policy PTL _______________________________________________ ONAP-TSC mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-tsc<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=jwTiArcEj6aUX0HjV0M3dT12gUtk7rC07xpgpVZkS_4&m=AHw4lOC0U1P7DeVWyexUwLHw7ctxnEABJEaE5ovgxoY&s=O9EaZjCpyg3VFzExekcRyipFZhzY9pacHlO3z8OHglw&e=> -- Phil Robb Executive Director, OpenDaylight Project VP Operations - Networking & Orchestration, The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
