Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan

[HU, BIN]

Hi Georg and Ash,

Thank you very much for sharing your view and concern.

First of all, please refer to the message I sent earlier that tried to answer 
Manuel’s concerns. That message outlines the thought-process and my view to 
address Manuel’s 3 concerns.

Then back to your concern, i.e. integrated platform capability and compliance 
toolset that we are having now. I am really sorry that if there is a 
misunderstanding here. My view is that the offering (or the delivered product) 
will be defined in Step 2 in detail (as a Product Management function). My 
personal understanding is that what we can offer is a portfolio instead of a 
single product. Our OPNFV product portfolio may include:

  *   DevOps solution as outlined in User Story on slide #12.
  *   A packaged testing tool chain that can be offered standalone
  *   An Integrated Platform Capabilities grown from our DevOps pipeline (our 
original product)
  *   A conformance testing solution of the integrated platform (our CVP / 
Dovetail)
  *   A LaaS infrastructure solution
  *   Etc.

Just like a cloud provider has a portfolio of products and services, including 
fundamental IaaS, PaaS and SaaS solutions and services. So it is a portfolio.

Please note that I used the word “Product” to  illustrate what we can offer. It 
does not mean anything commercial.

Hopefully I clarified it. Of course, we cannot do it all at one time. so when 
we define product portfolio in Step 2, we also need to define the roadmap and 
timeline in long term view. Once we have the strategy, and then portfolio and 
roadmap, we will have a very good story to market it and attract investment and 
resources back, and of course the most important is to implement it with 
necessary resources.

Please let me know if you have more questions.

Thank you
Bin

From: Georg Kunz 
Sent: Wednesday, November 21, 2018 9:04 AM
To: Ash Young ; HU, BIN 
Cc: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tsc] Discussion of OPNFV Strategic Plan

Hi Bin, Ash, all,

I’d like to pick up Manuel’s question about the value that our stakeholders 
would like to see and Ash’s point of building a reference platform: I believe 
that both aspects point towards the need for strengthening our compliance 
program – which is already based on a broad base of great test tools. OVP does 
not yet consume enough of the available tests for various reasons – having to 
admit this as a former Dovetail PTL. But I also think that we can still improve 
the capabilities of the OPNFV platform – by means of integration and closing 
gaps upstream. This is a requirement for adding additional tests covering NFV 
capabilities to the corresponding test tools and then eventually to OVP. 
Additional NFV capabilities we could think about include, for instance, L2GW, 
SR-IOV, LBaaS, FWaaS – in addition to emerging use cases like edge computing 
and cloud native computing, i.e., covering both OpenStack and K8s-based 
deployments.

So, in the context of the proposed DevOps approach, I am a little concerned 
that we lose track of enabling platform capabilities which are a requirement 
for the test tools and the compliance program. We need to make sure that this 
does not get out of focus too much (in my opinion). Specifically, if the main 
deliverable of OPNFV is an integration and CI framework, who do we consider 
performs the integration of components into a (reference) software stack: the 
users of OPNFV (using the new toolchain) or still OPNFV itself, leveraging the 
new toolchain?

Best regards
Georg

From: opnfv-...@lists.opnfv.org 
mailto:opnfv-...@lists.opnfv.org>> On Behalf Of Ash 
Young
Sent: Wednesday, November 21, 2018 4:24 PM
To: HU, BIN mailto:bh5...@att.com>>
Cc: opnfv-...@lists.opnfv.org; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tsc] Discussion of OPNFV Strategic Plan

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 

Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan

[HU, BIN]

Manuel,

Thank you so much for sharing your concerns. Those are really good points. Let 
me try to address it by first starting with a thought-process based on my 
experience of how industry is doing things, and then addressing specific 
concern.


  1.  General thought-process

I have been working for startups and established companies in Silicon Valley 
for 20 years. No matter in startups or in startup-style divisions within 
established companies, we generally looked for new business opportunity in the 
following way (terminology or steps might be varied, but the thought-processes 
are pretty much the same):

  *   Step 1: Set up a strategy (vision and direction) based on potential 
addressable market and potential customer needs, and our expertise and 
strength. This is the first milestone that we are doing now – the strategic 
direction.
 *   It doesn’t mean there is no competitor. In most of cases, there are 
already established competitors there with decent market share. But if we have 
expertise and strength there, we go for it after thought-process.
 *   Example: when Google started in 1998, there were established search 
engines on market already such as Infoseek, AltaVista, Yahoo, Excite, 
WebCrawler, etc. You name it. We all know what is the result today.
  *   Step 2: Once we have a strategic direction, we need to define what we can 
offer in very careful details. This is the function of Product Management
 *   Product Management defines what specific product should look like, how 
the product can differentiate from our competitors etc. It need to take into 
account use cases, user experience, how current products from competitors work 
and what are the gaps etc.
 *   This is the step of 1st bullet point on slide #16, which we need to do 
after we approve a strategic plan.
  *   Step 3: development of product. This is quite obvious, and the step of 
2nd and 3rd bullet points on slide #16 to make it real.
  *   Other steps include marketing, technology roadmap (e.g. bullet point #4 
on slide #16) etc.

You can see that we are doing Step 1 right now as strategic plan to set up a 
vision and direction, in order to continue Step 2+ outlined in the strategic 
plan with much more details. This thought-process is well aligned with how 
industry is doing its business. Well, we OPNFV is a kind of startup since 2014 
from business point of view, right? 😊


  1.  Your concerns

Regarding your first concern, that is what we should do at Step 2 when we 
define what we can offer by taking input from stakeholders. I would encourage 
that we all talk internally and gather pain points. At least, I have been 
talking internally, and gathering pain points and desired results. I hope that 
once we can agree to a common vision, we can start to work on it immediately. 
We can then discuss the details of our offering, what features can 
differentiate ourselves so that we can successfully penetrate the market 
(hopefully as Google did in penetrating search engine market 😊.

Regarding your second concern, I am sorry for perhaps the misunderstanding 
here. The intent of mentioning cloud service is just to provide one option as 
potential evolution. It doesn’t mean we must put everything entirely on cloud. 
Thus we need to:

  *   Carefully evaluate what we need considering different factors, including 
but not limited to geographic distribution and heterogeneity of hardware for 
edge case and IOT case, and overall cost constrained by annual budget, etc.
  *   Work out roadmap, including what we must do on premise, and what we can 
put on cloud if it saves cost, and what is evolution path.
 *   This is the last bullet point on slide #16 that we should take

Regarding your third concern, I agree to your observation that companies have 
shifted their investment from OPNFV to somewhere else, e.g. ONAP. I am not sure 
if we can get a definitive answer to those questions that we ask those 
companies. When I talked to those who might be OPNFV’s potential stakeholders 
and users, the first question was always “what value you OPNFV can bring to 
me?” or “what you OPNFV can offer?”. So we may not get answers. Instead, we may 
get counter questions. Thus it is back to Step 2 to define what we can offer, 
which is subject to Step 1 our strategic plan. IMHO, there is a clear ROI 
(Return On Investment) reason behind the investment shift. At least, it implies 
that current offering from OPNFV is not bringing expected return to those that 
have shifted resources. So we need to have a vision and strategy to guide the 
definition of what we can offer so that we can continuously provide value, and 
attract the investment and resources back to our community with those values 
and improved ROI to those companies.

Hopefully I answered your questions and concerns.

That being said, I also would love to hear the input of a better strategy, 
vision and direction from everyone, and the value we can bring to stakeholders.

Re: [opnfv-tech-discuss] OPNFV Hunter MS1 - Release Plan - Nov 23 #release #Hunter

[David McBride]

Still waiting for release plans from many of you.  For those in the U.S.,
please try to submit your plan before you leave for your Thanksgiving
holiday.  Thanks.

David

On Mon, Nov 19, 2018 at 7:33 AM David McBride 
wrote:

> Reminder... MS1 - Release Plan is this Friday.
>
> Particularly for those of you in the U.S., recall that this is a short
> week, due to the Thanksgiving holiday, so please be sure to post your
> release plan before you leave on holiday.
>
> David
>
> On Thu, Nov 15, 2018 at 10:05 AM David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Please do the following by Nov 23:
>>
>>1. Prepare a project release plan for the Hunter release.  Projects
>>are free to create a plan that is best suited to their project.  However,
>>if you're not sure what to do, you may use this template
>>
>>to get started.
>>2. Create a summary
>>
>>(see directions on page).
>>
>> Let me know if you have any questions.
>>
>> David
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>


-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22422): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22422
Mute This Topic: https://lists.opnfv.org/mt/28148347/21656
Mute #release: https://lists.opnfv.org/mk?hashtag=release&subid=2783016
Mute #hunter: https://lists.opnfv.org/mk?hashtag=hunter&subid=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

[Georg Kunz]

Hi Bin, Ash, all,

I’d like to pick up Manuel’s question about the value that our stakeholders 
would like to see and Ash’s point of building a reference platform: I believe 
that both aspects point towards the need for strengthening our compliance 
program – which is already based on a broad base of great test tools. OVP does 
not yet consume enough of the available tests for various reasons – having to 
admit this as a former Dovetail PTL. But I also think that we can still improve 
the capabilities of the OPNFV platform – by means of integration and closing 
gaps upstream. This is a requirement for adding additional tests covering NFV 
capabilities to the corresponding test tools and then eventually to OVP. 
Additional NFV capabilities we could think about include, for instance, L2GW, 
SR-IOV, LBaaS, FWaaS – in addition to emerging use cases like edge computing 
and cloud native computing, i.e., covering both OpenStack and K8s-based 
deployments.

So, in the context of the proposed DevOps approach, I am a little concerned 
that we lose track of enabling platform capabilities which are a requirement 
for the test tools and the compliance program. We need to make sure that this 
does not get out of focus too much (in my opinion). Specifically, if the main 
deliverable of OPNFV is an integration and CI framework, who do we consider 
performs the integration of components into a (reference) software stack: the 
users of OPNFV (using the new toolchain) or still OPNFV itself, leveraging the 
new toolchain?

Best regards
Georg

From: opnfv-...@lists.opnfv.org  On Behalf Of Ash 
Young
Sent: Wednesday, November 21, 2018 4:24 PM
To: HU, BIN 
Cc: opnfv-...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tsc] Discussion of OPNFV Strategic Plan

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 mailto:bh5...@att.com>> 
wrote:
Hello community,

Thank you for the input and discussion of OPNFV Strategy and 
Plan
 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

Re: [opnfv-tech-discuss] Gambia release community awards #gambia #release #awards

[David McBride]

Many of you already noticed this, but I forgot to include a nominating
statement to the list of things to provide when nominating.  Updated list
below:

For nominations, please specify:

   - Name
   - Organization
   - e-mail address
   - Award category
   - Brief nominating statement describing the nominee's contributions and
   why they should receive an award.

Thanks.

David

On Tue, Nov 20, 2018 at 9:02 AM David McBride 
wrote:

> Come on team!  Send in those nominations! - D
>
> On Fri, Nov 16, 2018 at 2:42 PM David McBride <
> dmcbr...@linuxfoundation.org> wrote:
>
>> Team,
>>
>> With the Gambia 7.0 release behind us. I'd like to kick off the
>> nomination period for community awards.  Per the TSC approved community
>> awards procedure ,
>> we have the following award categories (with the number of winners in
>> parentheses).
>>
>>- Code development (3)
>>- Community support/leadership (3)
>>- Integration (3)
>>- Testing (3)
>>- Interns (2)
>>
>> If you're interested in nominating community members for any of the
>> categories above, could you please send them to me by Noon, Pacific
>> Time, on November 30th (Friday)?
>>
>> For nominations, please specify:
>>
>>- Name
>>- Organization
>>- e-mail address
>>- Award Category (see list above)
>>
>>
>> After I receive the nominations, I'll be sending out a SurveyMonkey link
>> for voting to opnfv-tech-discuss.
>>
>> We plan to announce the winners and hand out awards at the Gambia
>> Plugfest in January.  If you have not yet registered, here's a link
>>  to
>> the registration page.
>>
>> David
>>
>> --
>> *David McBride*
>> Release Manager, OPNFV
>> Mobile: +1.805.276.8018
>> Email/Google Talk: dmcbr...@linuxfoundation.org
>> Skype: davidjmcbride1
>> IRC: dmcbride
>>
>
>
> --
> *David McBride*
> Release Manager, OPNFV
> Mobile: +1.805.276.8018
> Email/Google Talk: dmcbr...@linuxfoundation.org
> Skype: davidjmcbride1
> IRC: dmcbride
>


-- 
*David McBride*
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: dmcbr...@linuxfoundation.org
Skype: davidjmcbride1
IRC: dmcbride
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22420): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22420
Mute This Topic: https://lists.opnfv.org/mt/28180916/21656
Mute #release: https://lists.opnfv.org/mk?hashtag=release&subid=2783016
Mute #gambia: https://lists.opnfv.org/mk?hashtag=gambia&subid=2783016
Mute #awards: https://lists.opnfv.org/mk?hashtag=awards&subid=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

[Ash Young]

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  wrote:

> Hello community,
>
>
>
> Thank you for the input and discussion of OPNFV Strategy and Plan
> 
> 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
> .
> The outline of the OPNFV Strategic Plan
> 
> 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

Re: [opnfv-tech-discuss] [Testperf] 2018 Test Working Group Weekly Meeting

[Emma Foley]

Hi folks,

Polling for topics for this week's testperf meeting

Currently, there is:
*   Update of sign up for chairing the meeting
*   Test tools CFP for FOSDEM - 
https://etherpad.opnfv.org/p/test-tool-evolution-presentation

Please update the wiki[1] with any additional topics.
Best regards,
Emma
[1] https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting

-Original Appointment-
From: Yuyang (Gabriel) [mailto:gabriel.yuy...@huawei.com]
Sent: Thursday, January 4, 2018 2:33 AM
To: Yuyang (Gabriel); 'opnfv-tech-discuss@lists.opnfv.org'; 
test...@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Testperf] 2018 Test Working Group Weekly Meeting
When: 22 November 2018 23:00 to 23 November 2018 00:00 (UTC+08:00) Perth.
Where: https://global.gotomeeting.com/join/819733085


Hi All,

This initiation is for Testperf Weekly Meeting in 2018. Please find the 
detailed meeting schedules as follows.
For the APAC meeting, there is a separated invitation sent out before which you 
might be able to find in your calendar in the time slot indicated below.
*   Home Page: https://wiki.opnfv.org/display/testing/TestPerf
*   Meeting Page: 
https://wiki.opnfv.org/display/meetings/Test+Working+Group+Weekly+Meeting
*
*   Usual time (this timeslot): Every Thursday 15:00-16:00 UTC
Thursday GTM: https://global.gotomeeting.com/join/819733085
Access Code: 819-733-085
IRC channel: #opnfv-testperf @ 
Freenode
*   APAC time: 2nd Wednesday of the month 8:00-9:00 UTC replaces usual slot 
that week
APAC time: Wednesday GTM https://global.gotomeeting.com/join/819733085
Access Code: 819-733-085
IRC channel: #opnfv-testperf @ 
Freenode

*   Arrangement of Agenda varies but typically is structured:
*   15 min report out / sharing by projects (high level status / plans)
*   20 min discussion on test project collaboration topic/s
*   20 min - share new test projects or other test topics


Best,
Gabriel
  << File: ATT1.txt >>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22418): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22418
Mute This Topic: https://lists.opnfv.org/mt/28277434/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] FW: FOSDEM 2019 Software Defined Networking Devroom CFP -- closing this week

[Emma Foley]

Hi folks, 

The CFP for the FOSDEM Software Defined Networking devroom (formerly the 
SND/NFV devroom) is closing at the end of the week.
Anyone interested in submitting a presentation, it's your last chance to 
submit, so get in there!

Best of luck, 
Emma

-Original Message-
From: network-devroom [mailto:network-devroom-boun...@lists.fosdem.org] On 
Behalf Of Ray Kinsella
Sent: Monday, November 19, 2018 4:53 PM
To: fos...@lists.fosdem.org; network-devr...@lists.fosdem.org
Subject: Re: FOSDEM 2019 Software Defined Networking Devroom CFP

Hi folks,

Just a quick reminder that the FOSDEM 2019 CFP closes on November 25th.

If you know engineers working on Networking open source in Europe, this is a 
great opportunity for them to promote their work. Would love to see an abstract 
from you or your colleagues.

Thanks,

Ray Kinsella
FD.io TSC Member

Call For Papers @
http://mdr78.github.io/fosdem/2018/10/15/fosdem-2019-cfp.html

On 15/10/2018 18:07, Ray Kinsella wrote:
> 
> (posted at 
> http://mdr78.github.io/fosdem/2018/10/15/fosdem-2019-cfp.html )
> 
> We are pleased to announce the Call for Participation for the FOSDEM
> 2019 Software Defined Networking devroom!
> 
> **Important dates:**
> * Nov 25th 2018:  Submission deadline for talk proposals
> * Dec 17th 2018:  Announcement of the final schedule
> * Feb  2rd 2019:  Software Defined Networking dev room
> 
> We are now inviting proposals for talks about Open Source Software on 
> the topic of Software Defined Networking. This is an exciting and 
> growing field, and FOSDEM gives an opportunity to reach a unique 
> audience of very knowledgeable and highly technical, free and open 
> source software activists.
> 
> **Topics:**
> 
> This year the DevRoom topics will include the following Software 
> Defined Networking fields.
> 
> - Infrastructure: virtual switches & routers, routing daemons, 
> firewall, security, etc.
> - Virtual Network Functions: open source network functions, user-space 
> networking stacks, kernel-space networking innovations.
> - Tooling: Networking SDK's, libraries, frameworks, debuggers, 
> counters & statistics, domain specific languages & extensions, etc.
> - Validation: Testing tools & frameworks, traffic generators etc
> - Orchestration: NFV management, ML2 plugins, CNI plugins, SDN 
> Controllers, etc.
> 
> This year, the DevRoom will focus on low-level networking and high 
> performance packet processing, network automation of containers, 
> virtual machines and private cloud, and the management of networking 
> applications to maintain very high availability and performance 
> independent of whatever the world can throw at their infrastructure 
> (datacenter outages, fires, broken servers, you name it).
> 
> **Suggested Projects:**
> 
> A representative list of the projects and topics we would like to see 
> on the schedule are:
> 
> * Low-level networking and switching: DPDK, IOvisor, eBPF, XDP, Snabb, 
> Open vSwitch, Tungsten Fabric, OpenDataplane …
> * Networking Stacks: FD.io, F-Stack, DMM, mTCP,  …
> * SDN controllers and overlay networking: OpenStack Neutron, 
> Kubernetes CNI, Canal, OpenDaylight, ONOS, Plumgrid, OVN, 
> OpenContrail, Midonet, …
> * Network management; FRRouting, Quagga, BIRD, Netopeer, Go-BGP, …
> * NFV management and orchestration: Open-O, ManageIQ, Juju, OpenBaton, 
> Tacker, OSM, Ganglia, NetSNMP, PNDA.io, …
> * Supporting tooling: VSPerf, CSIT, TRex, Moongen, Scapy, DPDK Packet 
> Gen …
> * NFV related features: Service Function Chaining, fault management, 
> dataplane acceleration, security, …
> 
> Talks should be aimed at a technical audience, but should not assume 
> that attendees are already familiar with your project or how it solves 
> a general problem. Talk proposals can be very specific solutions to a 
> problem, or can be higher level project overviews for lesser known 
> projects.
> 
> **Proposals:**
> 
> Please include the following information when submitting a proposal:
> 
> * Your name
> * The title of your talk (please be descriptive, as titles will be 
> listed with around 250 from other projects)
> * Short abstract of one or two paragraphs
> * Short bio (with photo)
> * The deadline for submissions is November 25th, 2018. FOSDEM will be 
> held on the weekend of February 2-3, 2019 and the Software Defined 
> Networking DevRoom will take place on Saturday, February 2, 2019.
> * Please use the FOSDEM Pentabarf website
> (https://penta.fosdem.org/submission/FOSDEM19) to submit your 
> proposals.(you do not need to create a new Pentabarf account if you 
> already have one from past years).
> 
> You can also join the devroom’s mailing list, which is the official 
> communication channel for the DevRoom: 
> network-devr...@lists.fosdem.org (subscription page - 
> https://lists.fosdem.org/listinfo/network-devroom)
> 
> **Steering Committee:**
> 
> * Ray Kinsella
> * Thomas Monjalon
> * Emma Foley
> * Chris Price
> * Charles Eckel
_

Re: [opnfv-tech-discuss] [opnfv-tsc] Discussion of OPNFV Strategic Plan

[Manuel Buil]

Hi Bin,
Here are some concerns I have, hopefully I am not the only one:
- By your slides I understand that you suggest to focus on doing work
which could be reused internally by the companies involved in OPNFV to
build their devops platform for NFV solutions. I wonder whether there
is a niche there and how the relevant internal departments of the
different companies (stakeholders in your slides) are currently doing
their NFV devops activities and whether they are happy or they are
looking for an alternative. Talking about open source communities, ODL
and Openstack are currently happy with their CI/CD solution and AFAIK,
not looking for something else (please correct me if I am wrong). Do we
have any sort of indication that this direction would be useful by
companies involved in OPNFV? Perhaps we all could talk internally to
check this and even gather some pain points with current tools and
desired features.
- I understand that the end goal of "the evolution of pharos lab" is
having a lab based on cloud services. I am a bit concerned about this
because to some extend we would lose control of our infrastructure and
will need to rely on what the providers give us (which most of the
times is abstracted) and perhaps we will lose geographical distribution
or the heterogeneity of it. Let alone having the possibility to connect
some exotic hardware to test edge use cases or IoT use cases (e.g.
having a pool of raspberries connected to our infra).
- Regarding the community growth, I think that attending developer-
oriented events will not be enough to gather new developers in OPNFV. I
am actually not sure how to address this problem which, in my opinion,
is getting acute. A big part of the people who stopped working in OPNFV
in the last months was not because they did not find OPNFV attractive
or cool but because their employers prioritized other communities (e.g.
ONAP) or some internal work over OPNFV. The best approach for me would
be to reach those employers (I guess they are the stakeholders in the
slides) and ask: what would you like to see in OPNFV in order to
increase the amount of resources you currently provide? or, what you
did not like in OPNFV which resulted in you decreasing the amount of
developers in OPNFV during the last months?. Perhaps the board could be
a good place to ask this?
It would be nice to know other poeple's opinion too! My view might be
completely wrong... :)
Regards,Manuel



On Tue, 2018-11-20 at 15:23 +, HU, BIN wrote:
> Hello community,
>  
> Thank you for the input and discussion of 
> OPNFV Strategy and Plan 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. The outline of the 
> OPNFV Strategic Plan 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 opportunityTechnology
> excellenceCommunity growth
> Slide #11-#13 talks about stakeholder-oriented business opportunity,
> including
> 
> Why should we evolve to DevOps platformA user storyOPNFV 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
> toolchainSlide #15 talks about community growthSlide #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.opnf

[opnfv-tech-discuss] [edge cloud] H release plan

[qihuiz]

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 (#22415): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22415
Mute This Topic: https://lists.opnfv.org/mt/28276413/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] [dovetail] Agenda for weekly meeting 2018-11-21

[xudan]

Hi all,

This is the preliminary agenda for today's call.


  *   JIRA clean and review open JIRA tickets
  *   Next release plan
  *   AOB

Meeting Info

  *   Weekly Technical Discussion Wednesday at 14:00-15:00 UTC (6:00-7:00AM 
Pacific Standard Time)
  *   https://zoom.us/j/2362828999
  *   IRC channel: IRC channel: #opnfv-dovetail@ Freenode (Web 
Chat)
Best regards,
Dan Xu

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#22414): 
https://lists.opnfv.org/g/opnfv-tech-discuss/message/22414
Mute This Topic: https://lists.opnfv.org/mt/28275526/21656
Group Owner: opnfv-tech-discuss+ow...@lists.opnfv.org
Unsubscribe: https://lists.opnfv.org/g/opnfv-tech-discuss/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-