[opnfv-tech-discuss] FW: Yardstick weekly meeting - Nov 27th
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:UTC BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+ TZOFFSETTO:+ END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+ TZOFFSETTO:+ END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN="Foley, Emma L";SENT-BY="MAILTO:limingji...@huawei.com":MAILTO:emm a.l.fo...@intel.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org DESCRIPTION;LANGUAGE=zh-CN:Today’s Agenda - 2018 27/11 (09:30 UTC)\n • Action point follow-up 5'\n• Hunter Release Planning Rev iew\n• AoB 5'\n\nMeeting Logistics\n• Tuesdays UTC 09h 30 - 10h00 (Asia and Europe Slot)\n• zoom: https://zoom.us/j/5014 627785\n• IRC channel: #opnfv-yardstick\n• chair by Rex Le e\n• See Yardstick Meetings for details and minu tes of meeting\n\n\n SUMMARY;LANGUAGE=zh-CN:FW: Yardstick weekly meeting - Nov 27th DTSTART;TZID=UTC:20181127T093000 DTEND;TZID=UTC:20181127T10 UID:04008200E00074C5B7101A82E008D03E734479C7D301000 01000A360706B3A279C468F9FD0EADE57E8C7 RECURRENCE-ID;TZID=UTC:20181127T083000 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20180329T235413Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION;LANGUAGE=zh-CN:https://zoom.us/j/5014627785 X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-OWNERAPPTID:-757254174 X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:3 X-MICROSOFT-DISALLOW-COUNTER:FALSE END:VEVENT END:VCALENDAR -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22447): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22447 Mute This Topic: https://lists.opnfv.org/mt/28368800/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[opnfv-tech-discuss] Invitation: [OVN4NFV] Weekly Meeting - Tuesday - 2018 November 27 @ Tue Nov 27, 2018 9pm - 10pm (IST) (opnfv-tech-discuss@lists.opnfv.org)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20181127T153000Z DTEND:20181127T163000Z DTSTAMP:20181127T071745Z ORGANIZER;CN=trinaths@gmail.com:mailto:trinaths@gmail.com UID:4mc9j6o46hn1ehroj9cmm71...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=opnfv-tech-discuss@lists.opnfv.org;X-NUM-GUESTS=0:mailto:opnfv-tech -disc...@lists.opnfv.org CREATED:20181127T071745Z DESCRIPTION:Hi OVN4NFV team-\n\nPlease find the agenda for Tuesday's\, IRC based weekly meeting -\nhttps://wiki.opnfv.org/display/OV/Meeting+Agenda \n \nTuesday (Weekly) meetings\n\nMeeting Time: 1530 to 1630 UTC \n\nEST/ET: 1 030 to 1130 HRS\n\nPST/PT: 0730 to 0830 HRS\n\nIST: 2100 to 2200 HRS \n\n(P lease co-relate with Day light saving (if any) with India Standard Time)\n\ n\n/Trinath\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~: ~:~:~:~:~:~:~:~:~:~::~:~::-\nPlease do not edit this section of the descrip tion.\n\nView your event at https://www.google.com/calendar/event?action=VI EW=NG1jOWo2bzQ2aG4xZWhyb2o5Y21tNzFhNDMgb3BuZnYtdGVjaC1kaXNjdXNzQGxpc3Rz Lm9wbmZ2Lm9yZw=MjIjdHJpbmF0aHMuZGV2QGdtYWlsLmNvbWM4YWFjNDY0NTRlY2M5ZmE0 MDYwMTA2Y2E3Yjk5YWI1MTJmMjg5YzY=Asia%2FCalcutta=en=1.\n-::~:~::~: ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~: :- LAST-MODIFIED:20181127T071745Z LOCATION:#ovn4nfv-meeting (IRC Channel) SEQUENCE:0 STATUS:CONFIRMED SUMMARY:[OVN4NFV] Weekly Meeting - Tuesday - 2018 November 27 TRANSP:OPAQUE BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:This is an event reminder TRIGGER:-P0DT0H15M0S END:VALARM END:VEVENT END:VCALENDAR invite.ics Description: application/ics -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22446): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22446 Mute This Topic: https://lists.opnfv.org/mt/28368774/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [edge cloud] bi-weekly meeting reminder
Hello Edge Cloud Team, We are going to have our first edge cloud meeting after the OpenStack summit this Wednesday, Nov. 28, at 13:00 UTC. Look forward to see you then. Best, Qihui China Mobile Research Institute (+86) 13810659120 From: qihuiz Date: 2018-11-21 20:22 To: fuqiao; beth.cohen; adrian.peret; julienjut; haojingbo; gergely.csatari; ildiko; paul-andre.raymond; trevor.cooper; cristina.pauna; xiaohua.zhang; Bob.Monkman; deepak.s; asayeed; Tina.Tsou; klaus.mehler; periyasamy.palanisamy; hu.jie; kliu; wanglu; pvaanane; fanyamei; glenn.seiler; huang.shuquan; adrien.lebre; pierre.lynch; pj; valentin.boucher; kan.hong; claudio_serra; acm; viktor.tikkanen; simple_hlw; kailun.qin; mark.beierl; manuelbuil87 CC: opnfv-tech-discuss; opnfv-tsc; edge-computing Subject: [opnfv-tech-discuss] [edge cloud] H release plan Hello Edge Cloud Team, I've updated the edge cloud Hunter release plan. Please go to check if it's proprate. And we will discuss about the plan during our next meeting on Wednesday, Nov. 28. https://wiki.opnfv.org/display/EC/H+release+plan https://wiki.opnfv.org/display/SWREL/Edge+Cloud+Release+Plan+for+OPNFV+Hunter Best, Qihui China Mobile Research Institute (+86) 13810659120 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22445): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22445 Mute This Topic: https://lists.opnfv.org/mt/28367793/21656 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
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 +, 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 > Sent: Monday, November 26, 2018 4:17 PM > To: HU, BIN > Cc: Tim Irnich ; AshYoung ; Georg > Kunz ; Manuel Buil ; > 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 +, 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 On Behalf > > Of Tim Irnich > > Sent: Monday, November 26, 2018 12:57 PM > > To: HU, BIN ; AshYoung ; Georg Kunz > > ; Manuel Buil > > 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] -=-=-=-=-=-=-=-=-=-=-=-
[opnfv-tech-discuss] OPNFV Release meeting Nov 27 #release
Team, Due to the need to have an extended TSC meeting, our release meeting on Nov 27 will start 30 minutes later than usual (7:30 PST) and will be reduced to 30 minutes. David Title: OPNFV Release meeting David McBride is inviting you to a scheduled Zoom meeting. Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/515704540 Or iPhone one-tap : US: +16465588656,,515704540# or +16699006833,,515704540# Or Telephone: Dial(for higher quality, dial a number based on your current location): US: +1 646 558 8656 or +1 669 900 6833 or +1 855 880 1246 (Toll Free) or +1 877 369 0926 (Toll Free) Meeting ID: 515 704 540 International numbers available: https://zoom.us/zoomconference?m=dbo2cjcGmyrQfkTYGMcvQu5OWVA9bBru When: Tue Nov 27, 2018 7:30am – 8am Pacific Time - Los Angeles Who: * dmcbr...@linuxfoundation.org - organizer * opnfv-tech-discuss@lists.opnfv.org * opnfv-...@lists.opnfv.org -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22442): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22442 Mute This Topic: https://lists.opnfv.org/mt/28357954/21656 Mute #release: https://lists.opnfv.org/mk?hashtag=release=2783016 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
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 Sent: Monday, November 26, 2018 4:17 PM To: HU, BIN Cc: Tim Irnich ; AshYoung ; Georg Kunz ; Manuel Buil ; 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 +, 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 On Behalf > Of Tim Irnich > Sent: Monday, November 26, 2018 12:57 PM > To: HU, BIN ; AshYoung ; Georg Kunz > ; Manuel Buil > 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] > -=-=-=-=-=-=-=-=-=-=-=- -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22441): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22441 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] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [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 +, 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 On Behalf Of Tim > Irnich > Sent: Monday, November 26, 2018 12:57 PM > To: HU, BIN ; AshYoung ; Georg Kunz > ; Manuel Buil > 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 (#22440): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22440 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] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [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 (#22438): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22438 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] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
Hi Bin, In slide 3, you have this: –Addressing key roadblock of other open source communities (e.g. ONAP, OpenStack, Acumos etc.) It would be good if you can add K8S too as an example. Like this: –Addressing key roadblock of other open source communities (e.g. ONAP, OpenStack, Acumos, K8S etc.) On Mon, Nov 26, 2018 at 9:24 AM HU, BIN wrote: > Srini, > > Thank you for input. > > The details of K8S and how it should work with NFV need to be addressed at > a more tactical level, because K8S is one of the technologies in CN > paradigm. E.g: > - Step 2+: when defining how a CN-based platform is composed of, how > packaged CN-based testing tool is composed of > - and how a vertical will use CN-based solution, e.g. at Edge Cloud > project, or OVN4NFV project etc. > > You are very welcome to contribute to all of the details of technology, > including but not limited to K8S. > > Thank you > Bin > > -Original Message- > From: Addepalli, Srinivasa R > Sent: Monday, November 26, 2018 8:39 AM > To: HU, BIN ; Tim Irnich ; AshYoung < > a...@cachengo.com>; Georg Kunz ; Manuel Buil < > mb...@suse.com> > Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org > Subject: RE: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV > Strategic Plan > > Hi Bin, > > My 2 cents from strategy perspective. > > I see that Cloud native and micro services mentioned in your presentation. > But I did not see any Kubernetes term used anywhere. Hence, I thought I > would bring this up. > > So far, majority of the OPNFV focus seems to be supporting openstack based > sites. Many edge deployments are talking about using K8S. That leads to > supporting VNFs and CNFs using K8S. I feel that OPNFV community can lead > this effort on "K8S for NFV" - from CNI requirements perspective, > supporting various workloads (VM, container and Functions) and installation > perspective. > > In summary, strategy perspective, "K8S for NFV" need to be considered, in > my view. > > Some details: > > On CNI: OVN4NFV project started to develop OVN4NFV to work in K8S > environment. But, there may be other CNIs that OPNFV community may be > interested in such Nokia DANM and NSM (Network Service Mesh). Hence, I feel > it is important for OPNFV community to list down requirements on CNIs for > Network functions. > > On workloads: Docker is well known for bringing up containers. For VMs, > there are multiple options - Virtlet and Kubevirt for example. It is good > if OPNFV community discusses on how these can be supported. > > On software provisioning/installations: There are many installation in K8S > world - Kubespray and others. I feel that it is important to study and > consider new installers that are popular in K8S world and enhance them to > use for NFV. > > Thanks > Srini > > > -Original Message- > From: opnfv-tech-discuss@lists.opnfv.org [mailto: > opnfv-tech-discuss@lists.opnfv.org] On Behalf Of HU, BIN > Sent: Monday, November 26, 2018 7:40 AM > To: Tim Irnich ; AshYoung ; Georg > Kunz ; Manuel Buil > Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org > Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV > Strategic Plan > > Tim, > > Thank you for jumping in and offering your opinion. That's very helpful > and valuable. > > If I understand correctly, Point #1 and #3 are actually the same question, > i.e. what will we do in the next step? > - As I clarified in the email > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g_opnfv-2Dtsc_message_4844=DwIFAw=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=1h2UtM6XU8AenrGJ-Q8amy3LevJHiHk6H-e9Acwbe68=oMmmb5REJiKea-CVQ9n5qXl9oSrcGyhH6UxDZ93GNcU= > and earlier in this thread > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g_opnfv-2Dtsc_message_4845=DwIFAw=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=1h2UtM6XU8AenrGJ-Q8amy3LevJHiHk6H-e9Acwbe68=D7kWljFPFP2Ktnqa4r-a7LnuLvdTfBcgbUbm2lS_XII=, > this is our 1st milestone or Step #1 to have a strategic plan. This > milestone triggers the action of Step #2 and other following steps. Those > steps (or actions) are outlined on slide #16. > - Once we agree on the strategic plan, the action is the Step #2, i.e. to > define the details of the portfolio of what we can offer. The example of > details was illustrated in > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g_opnfv-2Dtsc_message_4845=DwIFAw=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=1h2UtM6XU8AenrGJ-Q8amy3LevJHiHk6H-e9Acwbe68=D7kWljFPFP2Ktnqa4r-a7LnuLvdTfBcgbUbm2lS_XII= > . > - You can see the example of portfolio in > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g_opnfv-2Dtsc_message_4845=DwIFAw=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=1h2UtM6XU8AenrGJ-Q8amy3LevJHiHk6H-e9Acwbe68=D7kWljFPFP2Ktnqa4r-a7LnuLvdTfBcgbUbm2lS_XII= > is getting the balance of equal importance of tools and reference stacks, > and maximizes the value of what we can offer. > - I changed the
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
Srini, Thank you for input. The details of K8S and how it should work with NFV need to be addressed at a more tactical level, because K8S is one of the technologies in CN paradigm. E.g: - Step 2+: when defining how a CN-based platform is composed of, how packaged CN-based testing tool is composed of - and how a vertical will use CN-based solution, e.g. at Edge Cloud project, or OVN4NFV project etc. You are very welcome to contribute to all of the details of technology, including but not limited to K8S. Thank you Bin -Original Message- From: Addepalli, Srinivasa R Sent: Monday, November 26, 2018 8:39 AM To: HU, BIN ; Tim Irnich ; AshYoung ; Georg Kunz ; Manuel Buil Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org Subject: RE: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan Hi Bin, My 2 cents from strategy perspective. I see that Cloud native and micro services mentioned in your presentation. But I did not see any Kubernetes term used anywhere. Hence, I thought I would bring this up. So far, majority of the OPNFV focus seems to be supporting openstack based sites. Many edge deployments are talking about using K8S. That leads to supporting VNFs and CNFs using K8S. I feel that OPNFV community can lead this effort on "K8S for NFV" - from CNI requirements perspective, supporting various workloads (VM, container and Functions) and installation perspective. In summary, strategy perspective, "K8S for NFV" need to be considered, in my view. Some details: On CNI: OVN4NFV project started to develop OVN4NFV to work in K8S environment. But, there may be other CNIs that OPNFV community may be interested in such Nokia DANM and NSM (Network Service Mesh). Hence, I feel it is important for OPNFV community to list down requirements on CNIs for Network functions. On workloads: Docker is well known for bringing up containers. For VMs, there are multiple options - Virtlet and Kubevirt for example. It is good if OPNFV community discusses on how these can be supported. On software provisioning/installations: There are many installation in K8S world - Kubespray and others. I feel that it is important to study and consider new installers that are popular in K8S world and enhance them to use for NFV. Thanks Srini -Original Message- From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of HU, BIN Sent: Monday, November 26, 2018 7:40 AM To: Tim Irnich ; AshYoung ; Georg Kunz ; Manuel Buil Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan Tim, Thank you for jumping in and offering your opinion. That's very helpful and valuable. If I understand correctly, Point #1 and #3 are actually the same question, i.e. what will we do in the next step? - As I clarified in the email https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g_opnfv-2Dtsc_message_4844=DwIFAw=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=1h2UtM6XU8AenrGJ-Q8amy3LevJHiHk6H-e9Acwbe68=oMmmb5REJiKea-CVQ9n5qXl9oSrcGyhH6UxDZ93GNcU= and earlier in this thread https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g_opnfv-2Dtsc_message_4845=DwIFAw=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=1h2UtM6XU8AenrGJ-Q8amy3LevJHiHk6H-e9Acwbe68=D7kWljFPFP2Ktnqa4r-a7LnuLvdTfBcgbUbm2lS_XII=, this is our 1st milestone or Step #1 to have a strategic plan. This milestone triggers the action of Step #2 and other following steps. Those steps (or actions) are outlined on slide #16. - Once we agree on the strategic plan, the action is the Step #2, i.e. to define the details of the portfolio of what we can offer. The example of details was illustrated in https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g_opnfv-2Dtsc_message_4845=DwIFAw=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=1h2UtM6XU8AenrGJ-Q8amy3LevJHiHk6H-e9Acwbe68=D7kWljFPFP2Ktnqa4r-a7LnuLvdTfBcgbUbm2lS_XII=. - You can see the example of portfolio in https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g_opnfv-2Dtsc_message_4845=DwIFAw=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=1h2UtM6XU8AenrGJ-Q8amy3LevJHiHk6H-e9Acwbe68=D7kWljFPFP2Ktnqa4r-a7LnuLvdTfBcgbUbm2lS_XII= is getting the balance of equal importance of tools and reference stacks, and maximizes the value of what we can offer. - I changed the wording of 1st bullet point on slide #16 to reflect your point of #1 and #3. This is the Step #2, the immediate action point triggered by the strategic plan. - I also changed wording on other bullets on slide #16 to reflect some more details in my prior messages. - See attached deck v0.7. Regarding your point #4, it is actually one of the following actions, i.e. to develop a marketing message to reflect our strategy. This is captured on the last bullet point on slide #16. Certainly, this is another action point we
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
Manuel, Thank you for your great question. I would say that slide #13 provides the strategy and vision at a high level, and slide #16 provides more clarity of steps to execute towards the strategy and vision. The others are background and supporting material. I think our discussion is more about how to achieve it in a more balanced way without losing existing products, and considering the nature of a roadmap. So you are right. The voting is for the strategy (the ultimate vision and direction) (slide #13), with the supporting steps of execution to achieve the vision in a gradual and balanced way in order to maximize the value of OPNFV (slide #16). Hope that I clarify it, and please let me know if you have any more concern on the strategy and its execution steps. Thanks Bin -Original Message- From: opnfv-tech-discuss@lists.opnfv.org On Behalf Of Manuel Buil Sent: Monday, November 26, 2018 8:51 AM To: HU, BIN ; Tim Irnich ; AshYoung ; Georg Kunz Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan Hi Bin, Reading all your answers (thanks for that!), I think I was confused because your slides contain much more content that what you really want us to approve, right? If I understand correctly, basically tomorrow you would like the TSC to *only* vote on your proposed "strategy (vision and direction) based on potential addressable market and potential customer needs, and our expertise and strength". That means, checking your slides, you want us to vote on slide 13. The rest, is just information to corroborate your reasoning of why we need a new strategy and why that strategy in particular (up until slide 13), or just a peek into potential actions we could take once the strategy is approved (after slide 13). In conclusion, correct if I am wrong, the question you want us to vote tomorrow would be something like: Do you think OPNFV strategy should be based on?: * Enabling and automating stakeholders’ business transformation into DevOps organization * Addressing key roadblock of other open source communities Is my reasoning correct? or... how wrong am I? :) Thanks, Manuel On Mon, 2018-11-26 at 15:39 +, HU, BIN wrote: > Tim, > > Thank you for jumping in and offering your opinion. That's very > helpful and valuable. > > If I understand correctly, Point #1 and #3 are actually the same > question, i.e. what will we do in the next step? > - As I clarified in the email > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g > _opnfv-2Dtsc_mes=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6Y > IIHhw=ZtjwNafmJ7onuz-clvmP33vkECvLJVDEmIXUPRC5aOY=I8sAXwxhIGvELdRc > qU20v59F880QmUcSb8j0Q2lv0zg= > sage/4844 and earlier in this thread > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g > _opnfv-2D=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw > =ZtjwNafmJ7onuz-clvmP33vkECvLJVDEmIXUPRC5aOY=7hI7uXkaHnQCxB_UlmxYUHb > 4j2SBRylY_yyU1g0I0Ss= tsc/message/4845, this is our 1st milestone or > Step #1 to have a strategic plan. This milestone triggers the action > of Step #2 and other following steps. Those steps (or actions) are > outlined on slide #16. > - Once we agree on the strategic plan, the action is the Step #2, i.e. > to define the details of the portfolio of what we can offer. The > example of details was illustrated in > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g > _opnfv=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=Zt > jwNafmJ7onuz-clvmP33vkECvLJVDEmIXUPRC5aOY=kfwLgIBByerbykno_ZjrMWFwfT > dKZnH1ptJE5FYONy4= > -tsc/message/4845. > - You can see the example of portfolio in > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.opnfv.org_g > _o=DwIDaQ=LFYZ-o9_HUMeMTSQicvjIg=6qPcDOqMgwf1K_r6YIIHhw=ZtjwNa > fmJ7onuz-clvmP33vkECvLJVDEmIXUPRC5aOY=MXWrAS6751y_7YZJNt_Wtgw6iUMFDB > s69zV5z0o3O54= > pnfv-tsc/message/4845 is getting the balance of equal importance of > tools and reference stacks, and maximizes the value of what we can > offer. > - I changed the wording of 1st bullet point on slide #16 to reflect > your point of #1 and #3. This is the Step #2, the immediate action > point triggered by the strategic plan. > - I also changed wording on other bullets on slide #16 to reflect some > more details in my prior messages. > - See attached deck v0.7. > > Regarding your point #4, it is actually one of the following actions, > i.e. to develop a marketing message to reflect our strategy. This is > captured on the last bullet point on slide #16. Certainly, this is > another action point we need to take after we agree on the strategy. > > Regarding your point #2, yes, we need all TSC members to contribute to > those actions, including: > - defining the portfolio > - defining the implementation and roadmap > - working with MWG to define marketing message. > > I also would expect that
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
Hi Bin, Reading all your answers (thanks for that!), I think I was confused because your slides contain much more content that what you really want us to approve, right? If I understand correctly, basically tomorrow you would like the TSC to *only* vote on your proposed "strategy (vision and direction) based on potential addressable market and potential customer needs, and our expertise and strength". That means, checking your slides, you want us to vote on slide 13. The rest, is just information to corroborate your reasoning of why we need a new strategy and why that strategy in particular (up until slide 13), or just a peek into potential actions we could take once the strategy is approved (after slide 13). In conclusion, correct if I am wrong, the question you want us to vote tomorrow would be something like: Do you think OPNFV strategy should be based on?: * Enabling and automating stakeholders’ business transformation into DevOps organization * Addressing key roadblock of other open source communities Is my reasoning correct? or... how wrong am I? :) Thanks, Manuel On Mon, 2018-11-26 at 15:39 +, HU, BIN wrote: > Tim, > > Thank you for jumping in and offering your opinion. That's very > helpful and valuable. > > If I understand correctly, Point #1 and #3 are actually the same > question, i.e. what will we do in the next step? > - As I clarified in the email https://lists.opnfv.org/g/opnfv-tsc/mes > sage/4844 and earlier in this thread https://lists.opnfv.org/g/opnfv- > tsc/message/4845, this is our 1st milestone or Step #1 to have a > strategic plan. This milestone triggers the action of Step #2 and > other following steps. Those steps (or actions) are outlined on slide > #16. > - Once we agree on the strategic plan, the action is the Step #2, > i.e. to define the details of the portfolio of what we can offer. The > example of details was illustrated in https://lists.opnfv.org/g/opnfv > -tsc/message/4845. > - You can see the example of portfolio in https://lists.opnfv.org/g/o > pnfv-tsc/message/4845 is getting the balance of equal importance of > tools and reference stacks, and maximizes the value of what we can > offer. > - I changed the wording of 1st bullet point on slide #16 to reflect > your point of #1 and #3. This is the Step #2, the immediate action > point triggered by the strategic plan. > - I also changed wording on other bullets on slide #16 to reflect > some more details in my prior messages. > - See attached deck v0.7. > > Regarding your point #4, it is actually one of the following actions, > i.e. to develop a marketing message to reflect our strategy. This is > captured on the last bullet point on slide #16. Certainly, this is > another action point we need to take after we agree on the strategy. > > Regarding your point #2, yes, we need all TSC members to contribute > to those actions, including: > - defining the portfolio > - defining the implementation and roadmap > - working with MWG to define marketing message. > > I also would expect that yourself will be able to help drive one of > those actions, for example, working with MWG on marketing message to > make sure that it gets known externally. > > With those changes on slide #16 (in attached v0.7), hopefully it gets > the level of clarity you expected, and we can move forward. > > I am looking forward to your further contribution in executing this > strategy, especially e.g. in working with MWG for our marketing > message to get it known externally. > > Thank you again > Bin > > -Original Message- > From: Tim Irnich > Sent: Monday, November 26, 2018 6:37 AM > To: HU, BIN ; AshYoung ; Georg Kunz > ; Manuel Buil > Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org > Subject: Re: [opnfv-tsc] Discussion of OPNFV Strategic Plan > > Hi all, > > having read the entire thread again this morning, I'd like to offer > the following thoughts to hopefully help us make progress: > > - We need to make sure the decision we take triggers action and > change (since I think we all agree that we need to change something > in OPNFV). > To achieve this, we need to more clarity on the choices that are in > front of us and their consequences. The current material does not do > this clearly enough. It sort of says "we keep doing everything we > already do and add a few things." IMHO it would be better is we > described the change we want to achieve (i.e. in the form of "instead > of [...] we want [...]"). > > - The fraction of TSC members that have actively participated in the > discussion so far is way too low. I'd like to urge all TSC members to > get engaged. Remember, we are elected by the OPNFV community, and > this obliges us to do this type of work. We should not wait for > clarity to be provided, we should actively contribute to obtaining > it. > > - The discussion so far seems to revolve around a priority question: > are we primarily doing (consumable) tools for CI/CD and testing, and >
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
Hi Bin, My 2 cents from strategy perspective. I see that Cloud native and micro services mentioned in your presentation. But I did not see any Kubernetes term used anywhere. Hence, I thought I would bring this up. So far, majority of the OPNFV focus seems to be supporting openstack based sites. Many edge deployments are talking about using K8S. That leads to supporting VNFs and CNFs using K8S. I feel that OPNFV community can lead this effort on "K8S for NFV" - from CNI requirements perspective, supporting various workloads (VM, container and Functions) and installation perspective. In summary, strategy perspective, "K8S for NFV" need to be considered, in my view. Some details: On CNI: OVN4NFV project started to develop OVN4NFV to work in K8S environment. But, there may be other CNIs that OPNFV community may be interested in such Nokia DANM and NSM (Network Service Mesh). Hence, I feel it is important for OPNFV community to list down requirements on CNIs for Network functions. On workloads: Docker is well known for bringing up containers. For VMs, there are multiple options - Virtlet and Kubevirt for example. It is good if OPNFV community discusses on how these can be supported. On software provisioning/installations: There are many installation in K8S world - Kubespray and others. I feel that it is important to study and consider new installers that are popular in K8S world and enhance them to use for NFV. Thanks Srini -Original Message- From: opnfv-tech-discuss@lists.opnfv.org [mailto:opnfv-tech-discuss@lists.opnfv.org] On Behalf Of HU, BIN Sent: Monday, November 26, 2018 7:40 AM To: Tim Irnich ; AshYoung ; Georg Kunz ; Manuel Buil Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan Tim, Thank you for jumping in and offering your opinion. That's very helpful and valuable. If I understand correctly, Point #1 and #3 are actually the same question, i.e. what will we do in the next step? - As I clarified in the email https://lists.opnfv.org/g/opnfv-tsc/message/4844 and earlier in this thread https://lists.opnfv.org/g/opnfv-tsc/message/4845, this is our 1st milestone or Step #1 to have a strategic plan. This milestone triggers the action of Step #2 and other following steps. Those steps (or actions) are outlined on slide #16. - Once we agree on the strategic plan, the action is the Step #2, i.e. to define the details of the portfolio of what we can offer. The example of details was illustrated in https://lists.opnfv.org/g/opnfv-tsc/message/4845. - You can see the example of portfolio in https://lists.opnfv.org/g/opnfv-tsc/message/4845 is getting the balance of equal importance of tools and reference stacks, and maximizes the value of what we can offer. - I changed the wording of 1st bullet point on slide #16 to reflect your point of #1 and #3. This is the Step #2, the immediate action point triggered by the strategic plan. - I also changed wording on other bullets on slide #16 to reflect some more details in my prior messages. - See attached deck v0.7. Regarding your point #4, it is actually one of the following actions, i.e. to develop a marketing message to reflect our strategy. This is captured on the last bullet point on slide #16. Certainly, this is another action point we need to take after we agree on the strategy. Regarding your point #2, yes, we need all TSC members to contribute to those actions, including: - defining the portfolio - defining the implementation and roadmap - working with MWG to define marketing message. I also would expect that yourself will be able to help drive one of those actions, for example, working with MWG on marketing message to make sure that it gets known externally. With those changes on slide #16 (in attached v0.7), hopefully it gets the level of clarity you expected, and we can move forward. I am looking forward to your further contribution in executing this strategy, especially e.g. in working with MWG for our marketing message to get it known externally. Thank you again Bin -Original Message- From: Tim Irnich Sent: Monday, November 26, 2018 6:37 AM To: HU, BIN ; AshYoung ; Georg Kunz ; Manuel Buil Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org Subject: Re: [opnfv-tsc] Discussion of OPNFV Strategic Plan Hi all, having read the entire thread again this morning, I'd like to offer the following thoughts to hopefully help us make progress: - We need to make sure the decision we take triggers action and change (since I think we all agree that we need to change something in OPNFV). To achieve this, we need to more clarity on the choices that are in front of us and their consequences. The current material does not do this clearly enough. It sort of says "we keep doing everything we already do and add a few things." IMHO it would be better is we described the change
Re: [opnfv-tech-discuss] Infra Working Group Meeting #infra #releng #pharos #security
Hi all, I'll be 10-15 minutes late today. Sorry for the inconvenience. Regards, Trevor Bramwell -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#22431): https://lists.opnfv.org/g/opnfv-tech-discuss/message/22431 Mute This Topic: https://lists.opnfv.org/mt/26875261/21656 Mute #infra: https://lists.opnfv.org/mk?hashtag=infra=2783016 Mute #releng: https://lists.opnfv.org/mk?hashtag=releng=2783016 Mute #pharos: https://lists.opnfv.org/mk?hashtag=pharos=2783016 Mute #security: https://lists.opnfv.org/mk?hashtag=security=2783016 Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
-Original Message- From: Tim Irnich Sent: Monday, November 26, 2018 8:37 AM To: HU, BIN ; AshYoung ; Georg Kunz ; Manuel Buil Cc: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org Subject: Re: [opnfv-tsc] Discussion of OPNFV Strategic Plan Hi all, having read the entire thread again this morning, I'd like to offer the following thoughts to hopefully help us make progress: - We need to make sure the decision we take triggers action and change (since I think we all agree that we need to change something in OPNFV). To achieve this, we need to more clarity on the choices that are in front of us and their consequences. The current material does not do this clearly enough. It sort of says "we keep doing everything we already do and add a few things." IMHO it would be better is we described the change we want to achieve (i.e. in the form of "instead of [...] we want [...]"). - The fraction of TSC members that have actively participated in the discussion so far is way too low. I'd like to urge all TSC members to get engaged. Remember, we are elected by the OPNFV community, and this obliges us to do this type of work. We should not wait for clarity to be provided, we should actively contribute to obtaining it. [ay] I just thought the whole world was celebrating Thanksgiving with us [/ay] - The discussion so far seems to revolve around a priority question: are we primarily doing (consumable) tools for CI/CD and testing, and merely produce reference stacks to have something to validate those tools against, or are the reference stacks the priority and the tools are a by-product? Or are both equally important? IMHO both depend on each other and OPNFV needs to maximize the value it provides in both domains. [ay] That's the major point I was trying to highlight. Thank you for doing a better job of saying it. [/ay] - In addition to doing things better or differently, we need to find better ways of _explaining_ what we do, since lack of clarity (or an outdated view) on OPNFV's mission & value proposition seems to be the key reason for declining investment. Let's remember that there's no other entity than the TSC left to do this work. Once we have renewed our value proposition, the most important next step is to make sure it gets known externally. [ay] I share the same concern. Not sure people feel NFV is still relevant. I happen to believe it is, or I wouldn't be responding to this. [/ay] Regards, Tim On 11/22/18 8:44 PM, HU, BIN wrote: > Manuel, > > > > Thank you for sharing your more thoughts here. I really appreciate > your time and thinking. > > > > I am not sure if Georg or Ash really meant that we never finished > anything completely. (Correct me if I am wrong). Here is the status: > > * We have integrated platform as our main product (through > installers). We have gone through 7 releases. The stable release > process is quite mature. And we are working on maturing XCI process. > * OVP / Dovetail is also quite stable and becomes mature recently. > * The underlying CI/CD pipeline, and related test framework and test > cases are able to support successful stable release and OVP/Dovetail. > > > > Of course, nothing is perfect, and there is room for further improving > Integrated Platform and OVP/Dovetail, including add-on features of > platform and test case coverage in Dovetail. This is more like > maintaining and evolving existing product. The potential is limited > IMHO. The reality is that despite we have those 2 flagship products > which are very successful and can be maintained and evolved further, > we are still losing investment significantly as you indicated in your > 3^rd concern. > > > > My take of what Georg and Ash really meant is that we need to be > carefully handling our existing products (i.e. Integrated Platform and > OVP/Dovetail), and we don’t lose track of platform capabilities and > related test coverage when we look for new strategy. The strategy and > direction should evolve based on what we have and what we are good at. > From that viewpoint, I completely agree with them. So the strategy of > DevOps Platform, which includes the potential portfolio that includes > existing products, is the evolution based on what we have and what we > are good at, and opens potential for new market segment: > > * Expanded market segments: > o Existing 2 products are targeted to operators in terms of NFVI > (current segment) > o Potential portfolio expand the segment to all stakeholders and > other communities in terms of DevOps pipeline (new segment) > o Current segment is a vertical of new segment in this picture. So > those 2 segments are orthogonal. New market segment has little > cannibalization effect on current segment > o Thus we expand our addressable market with this new segment, > which potentially will support unlimited
Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan
Hi all, having read the entire thread again this morning, I'd like to offer the following thoughts to hopefully help us make progress: - We need to make sure the decision we take triggers action and change (since I think we all agree that we need to change something in OPNFV). To achieve this, we need to more clarity on the choices that are in front of us and their consequences. The current material does not do this clearly enough. It sort of says "we keep doing everything we already do and add a few things." IMHO it would be better is we described the change we want to achieve (i.e. in the form of "instead of [...] we want [...]"). - The fraction of TSC members that have actively participated in the discussion so far is way too low. I'd like to urge all TSC members to get engaged. Remember, we are elected by the OPNFV community, and this obliges us to do this type of work. We should not wait for clarity to be provided, we should actively contribute to obtaining it. - The discussion so far seems to revolve around a priority question: are we primarily doing (consumable) tools for CI/CD and testing, and merely produce reference stacks to have something to validate those tools against, or are the reference stacks the priority and the tools are a by-product? Or are both equally important? IMHO both depend on each other and OPNFV needs to maximize the value it provides in both domains. - In addition to doing things better or differently, we need to find better ways of _explaining_ what we do, since lack of clarity (or an outdated view) on OPNFV's mission & value proposition seems to be the key reason for declining investment. Let's remember that there's no other entity than the TSC left to do this work. Once we have renewed our value proposition, the most important next step is to make sure it gets known externally. Regards, Tim On 11/22/18 8:44 PM, HU, BIN wrote: > Manuel, > > > > Thank you for sharing your more thoughts here. I really appreciate your > time and thinking. > > > > I am not sure if Georg or Ash really meant that we never finished > anything completely. (Correct me if I am wrong). Here is the status: > > * We have integrated platform as our main product (through > installers). We have gone through 7 releases. The stable release > process is quite mature. And we are working on maturing XCI process. > * OVP / Dovetail is also quite stable and becomes mature recently. > * The underlying CI/CD pipeline, and related test framework and test > cases are able to support successful stable release and OVP/Dovetail. > > > > Of course, nothing is perfect, and there is room for further improving > Integrated Platform and OVP/Dovetail, including add-on features of > platform and test case coverage in Dovetail. This is more like > maintaining and evolving existing product. The potential is limited > IMHO. The reality is that despite we have those 2 flagship products > which are very successful and can be maintained and evolved further, we > are still losing investment significantly as you indicated in your 3^rd > concern. > > > > My take of what Georg and Ash really meant is that we need to be > carefully handling our existing products (i.e. Integrated Platform and > OVP/Dovetail), and we don’t lose track of platform capabilities and > related test coverage when we look for new strategy. The strategy and > direction should evolve based on what we have and what we are good at. > From that viewpoint, I completely agree with them. So the strategy of > DevOps Platform, which includes the potential portfolio that includes > existing products, is the evolution based on what we have and what we > are good at, and opens potential for new market segment: > > * Expanded market segments: > o Existing 2 products are targeted to operators in terms of NFVI > (current segment) > o Potential portfolio expand the segment to all stakeholders and > other communities in terms of DevOps pipeline (new segment) > o Current segment is a vertical of new segment in this picture. So > those 2 segments are orthogonal. New market segment has little > cannibalization effect on current segment > o Thus we expand our addressable market with this new segment, > which potentially will support unlimited verticals in addition > to NFVI vertical. > * DevOps Platform, as a horizontal pipeline, is the theme, or a > “string”, to connect all of our assets and projects together in a > systematic way: > o Horizontally, DevOps Platform combines our current CI/CD > pipeline, testing framework, and testing tools with the > potential to evolve to a more general-purpose pipeline, test > framework and tools with the options for customization that fits > different verticals. > + We already see the need of evolution to XCI cases > + DevOps Platforms open the path for further
