On Thu, Dec 11, 2014 at 7:41 PM, Daniel P. Berrange
wrote:
>
> Yes, I really think this is a key point. When we introduced the VIF type
> mechanism we never intended for there to be soo many different VIF types
> created. There is a very small, finite number of possible ways to configure
> the li
Hi All,
It's great to see the vendor plugin decomposition spec[1] finally getting
merged! Now that the spec is completed, I have a question on how this may
impact neutronclient, and in particular, its handling of vendor extensions.
One of the great things about splitting out the plugins is that
Hi All,
I noticed that in linux_net.py, the method to create a tap interface[1]
does not let you set the MTU size. In other places, I see calls made to
set the MTU of the device [2].
I'm wondering if there is any technical reasons to why we can't also set
the MTU size when creating tap interface
Hi All,
I was terribly SAD indeed that our spec proposal to add gw-mode
extension[1] to the midonet plugin was not accepted last Sunday, and I am
sending out this email to see if the core reviewers could accept this as
SFE.
It was originally rejected because the upstream plugin was not working
pr
Hi All!
We would like to start holding a weekly IRC meeting for midonet, and
we want to propose the meeting time of 9:00 UTC on Tuesdays.
Please let me know if anyone prefers different time.
Best,
Ryu
__
OpenStack Developme
Hi All,
For feature proposal in MidoNet, I would like that we follow the RFE
process[1] currently practiced in Neutron. It is designed to be
lightweight which makes it easy for everyone, including
non-developers, to initiate the feature development process. I
believe this process is appropriate
On Mon, Dec 14, 2015 at 6:34 PM, Sandro Mathys wrote:
> On Thu, Dec 10, 2015 at 4:46 PM, Galo Navarro wrote:
>>
> Honestly, I don't think this discussion is leading anywhere.
> Therefore, I'd like to request a decision by the MidoNet PTL as per
> [1].
I apologize for jumping in a bit late. Clea
Hi Nick,
We have already designed the data sync feature[1], but this
development was suspended temporarily in favor of completing the v5.0
development of MidoNet.
We will be resuming development work on this project soon (with high priority).
It sounds to me like you need a completed, mature too
On Tue, Dec 15, 2015 at 1:00 AM, Sandro Mathys wrote:
> On Tue, Dec 15, 2015 at 12:02 AM, Ryu Ishimoto wrote:
>
> So if I understand you correctly, you suggest:
> 1) the (midonet/internal) low level API stays where it is and will
> still be called python-midonetclient.
> 2) the
+1 !
On Wed, Apr 26, 2017 at 11:41 AM Takashi Yamamoto
wrote:
> unless anyone objects, i'll add the following people to
> networking-midonet project's core reviewers.
>
> - Antonio Ojea
> - Brandon Berg
> - Xavi León
>
> http://stackalytics.com/report/contribution/networking-midonet/30
> http://
10 matches
Mail list logo