Hi Bin, When we first created OPNFV, we set out to resolve the gaps we needed for the NFVI, which we saw as missing in the various open sourced projects. It was focused on NFV, not upon being the best installer of OpenStack or some other component that we said could be leveraged, but which was still deemed as not meeting our needs. I don't feel we ever completed this task before moving on to orchestration, because it became the next shiny thing. But what are we orchestrating if things are not instrumented to be orchestrated in a highly efficient manner. Recently, I met with an operator who said that our SDN controllers were simply too slow to meet their objectives. This statement is not intended as a slam of any of the controller projects. It's just meant as a point of reference that there's a need to implement a feature that is consumable for the intended recipient.
Your task and the task of the TSC is not an easy one. And I really love how our CI/CD and DevOps folks have matured over these years. But I think this cannot be the major mission for OPNFV. I think we are still missing that E2E reference architecture and stack that be easily leveraged. With that said, I do NOT propose we throw the baby out with the bathwater. I'd like to propose a solution for attracting more developers to our community and still develop features and components that are missing, but which resolve the gaps identified years ago. What we're doing is some really good stuff. But I would still like to see a smaller group drive a tightly coupled framework that can be easily leveraged by the consumers with a top level API, and which can figure out how to best implement certain features/component projects within OPNFV into this framework, and can also develop whatever new features might be missing. At the end of the day, I have shortened my list of projects I am participating in. I truly believe that OPNFV is very relevant and needed, but struggles too much trying to be like other projects out there. I'd love for us to get back to why we formed in the first place. But whatever you and the other TSC members decide, I'll support. We have already made provisions in our charter for what I am asking for. But I do not wish to be the tail wagging the dog. I see the need for these other things we're doing too. And I certainly see the challenge that you're now wrestling with. I am looking forward to an amazing year. Best, Ash On Tue, Nov 20, 2018 at 9:23 AM HU, BIN <bh5...@att.com> wrote: > Hello community, > > > > Thank you for the input and discussion of OPNFV Strategy and Plan > <https://wiki.opnfv.org/download/attachments/2925933/OPNFV%20Strategy%20and%20Plan%20v0.6.pptx?version=1&modificationDate=1542680159000&api=v2> > in the past 3 weeks, including in TSC discussion and Weekly Technical > Discussions. > > > > One critical role of TSC is to set up the direction and vision. So please > continue your input and discussion in the mailing list in order to further > mature the vision and strategy for the future. We target for TSC to approve > the strategy and vision next week Nov 27 as the 1st milestone, if we can > mature the discussion. Then we can continue to work on next steps for > details of deliverables that fit our resource availability and capability. > > > > Thank you and I am looking forward to more inputs and discussions. > > > > Bin > > > > *From:* HU, BIN > *Sent:* Tuesday, October 30, 2018 10:16 PM > *To:* opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org > *Subject:* Discussion of OPNFV Strategic Plan > > > > Hello community, > > > > At the 1st meeting of our new TSC today, we kicked off a discussion of OPNFV > Strategic Plan > <https://wiki.opnfv.org/download/attachments/2925933/OPNFV%20Strategy%20and%20Plan%20v0.5.pptx?version=1&modificationDate=1540961098489&api=v2>. > The outline of the OPNFV Strategic Plan > <https://wiki.opnfv.org/download/attachments/2925933/OPNFV%20Strategy%20and%20Plan%20v0.5.pptx?version=1&modificationDate=1540961098489&api=v2> > includes: > > - First 3 agenda items outline the current status of OPNFV (slide > #3-#8), which is a Problem Statement > - Slide #7 is a summary of input from new TSC members. > - Then it talks about key objectives of evolving OPNFV (slide #10), > focusing on > - Stakeholder-oriented business opportunity > - Technology excellence > - Community growth > - Slide #11-#13 talks about stakeholder-oriented business opportunity, > including > - Why should we evolve to DevOps platform > - A user story > - OPNFV new strategy, including addressing key roadblocks of other > communities including ONAP, OpenStack and Acumos > - Slide #14 talks about technology excellence, such as cloud-native > and microservices, edge, and a long-term vision of cloud-services based > toolchain > - Slide #15 talks about community growth > - Slide #16 talks about the next step to develop a detailed work plan > > > > We would like community involvement in discussing OPNFV strategic plan, > and shaping OPNFV’s future. So we plan to discuss it in the Weekly > Technical Discussion on Nov 8. > > > > Meanwhile, please feel free to give any feedback via email so that the > discussion on Nov. 8 will be more effective and productive. > > > > Thank you and look forward to everyone’s involvement and feedback. > > > > Bin > > > -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#4834): > https://lists.opnfv.org/g/opnfv-tsc/message/4834 > Mute This Topic: https://lists.opnfv.org/mt/27802341/675449 > Group Owner: opnfv-tsc+ow...@lists.opnfv.org > Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub [a...@cachengo.com] > -=-=-=-=-=-=-=-=-=-=-=- >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22419): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22419 Mute This Topic: https://lists.opnfv.org/mt/28277855/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
