Hi Bin, Perhaps 'integrated' is a better word here than 'supported'. A lot of the work in OPNFV involves integrating many of these upstream components which in turn exposes bugs, or creates features that enable an NFV use case.
I'm quite terrible with examples, but I'm sure others from the community have time. Regards, Trevor Bramwell On Tue, Nov 27, 2018 at 12:26:33AM +0000, HU, BIN wrote: > Trevor, > > Thank you for your question. > > Can you give more details and examples of "doing what we're best at, which is > getting NFV supported by upstream projects."? > > Thank you > Bin > > -----Original Message----- > From: Trevor Bramwell <tbramw...@linuxfoundation.org> > Sent: Monday, November 26, 2018 4:17 PM > To: HU, BIN <bh5...@att.com> > Cc: Tim Irnich <tim.irn...@suse.com>; AshYoung <a...@cachengo.com>; Georg > Kunz <georg.k...@ericsson.com>; Manuel Buil <mb...@suse.com>; > opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org > Subject: Re: [opnfv-tsc] Discussion of OPNFV Strategic Plan > > Hi Bin, > > I'm still unclear on the first point: "Enabling and automating stakeholders’ > business transformation into DevOps organization" > > From what I've read it seems like the suggestion is to package up everything > that makes up OPNFV (Platform, CI/CD piplines, testing / verification / > certification tools, etc.) and turn that into something that can be deployed > by a company internally. > > Is that what is being suggested here, or something else? And if so I'd be > concerned that we'd actually be reducing companies incentive to be involved, > or more of our time would be spent trying to support people using the tool > then doing what we're best at, which is getting NFV supported by upstream > projects. > > Regards, > Trevor Bramwell > > On Mon, Nov 26, 2018 at 09:04:57PM +0000, HU, BIN wrote: > > Tim, > > > > Not sure if you get a chance to follow the most recent discussion. > > > > The ask is merely to agree on a strategy (i.e. the vision and direction) > > outlined on Slide #13, supported by the steps of actions summarized on > > slide #16. See attached the most recent update v0.8. > > > > Please let me know if there is anything unclear here. > > > > Thanks > > Bin > > > > -----Original Message----- > > From: opnfv-...@lists.opnfv.org <opnfv-...@lists.opnfv.org> On Behalf > > Of Tim Irnich > > Sent: Monday, November 26, 2018 12:57 PM > > To: HU, BIN <bh5...@att.com>; AshYoung <a...@cachengo.com>; Georg Kunz > > <georg.k...@ericsson.com>; Manuel Buil <mb...@suse.com> > > Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org > > Subject: Re: [opnfv-tsc] Discussion of OPNFV Strategic Plan > > > > On 11/26/18 4:40 PM, HU, BIN wrote: > > > > > > If I understand correctly, Point #1 and #3 are actually the same > > > question, i.e. what will we do in the next step? > > > > No, I'm rather suggesting to make sure our understanding is complete before > > we proceed. We clearly do not yet sufficiently understand what exactly the > > decision is you're asking us to take, so we cannot proceed. > > Let's continue to work on this until we have the required clarity, and then > > decide. > > > > Regards, Tim > > > > > > -=-=-=-=-=-=-=-=-=-=-=- > > Links: You receive all messages sent to this group. > > > > View/Reply Online (#4856): > > https://lists.opnfv.org/g/opnfv-tsc/message/4856 > > Mute This Topic: https://lists.opnfv.org/mt/27802341/557206 > > Group Owner: opnfv-tsc+ow...@lists.opnfv.org > > Unsubscribe: https://lists.opnfv.org/g/opnfv-tsc/unsub > > [tbramw...@linuxfoundation.org] > > -=-=-=-=-=-=-=-=-=-=-=- >
signature.asc
Description: PGP signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22443): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22443 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] -=-=-=-=-=-=-=-=-=-=-=-
