[Openstack] MidoNet Quantum plugin proposal for G-3

Hi Everyone, I know that it's late in the cycle, but I am very excited to notify everyone that we have been working on the MidoNet Quantum plugin for Grizzly, which would enable MidoNet (Midokura's virtual networking solution) in Quantum, and we are hoping to have it included in for the Grizzly-3

Re: [Openstack] POC for Pluggable Network Service

/network-service. Thanks, Hisaharu Ishii (2011/04/01 11:34), Ishimoto, Ryu wrote: Hi Hisaharu, Great to see some action happening on the topic of network service! Thanks for creating this detailed spec! We, at Midokura, would love to contribute to this project. I took a look

Re: [Openstack] POC for Pluggable Network Service

Hi Hisaharu, Great to see some action happening on the topic of network service! Thanks for creating this detailed spec! We, at Midokura, would love to contribute to this project. I took a look at the code and noticed a few things: - You have started the merging of flat, flat_dhcp and vlan

Re: [Openstack] multi-nic blueprint - data migration

. Does that help? -trey On Mon, Mar 28, 2011 at 10:54 AM, Ishimoto, Ryu r...@midokura.jp wrote: Thanks, that cleared it up for me. Staying on the topic of multi-nics, I have been trying to understand the direction in which Nova is going in regards to networking, and reading up

[Openstack] multi-nic blueprint - data migration

Hi All, I was looking at the multi-nic blueprint( https://blueprints.launchpad.net/nova/+spec/nova-multi-nic), and in particular: 1) removing mac_address column from the instances table and creating a mac_addresses table. This is for storing which instances own which mac addresses as well as

[Openstack] Decoupling of Network and Compute services for the new Network Service design

Hi everyone, I have been following the discussion regarding the new 'pluggable' network service design, and wanted to drop in my 2 cents ;-) Looking at the current implementation of Nova, there seems to be a very strong coupling between compute and network services. That is, tasks that are done

Re: [Openstack] Network Service for L2/L3 Network Infrastructure blueprint

It seems that there must be a decision made to what extent should an OpenStack 'network service' is expected to support. Should it support L2-only networks? Or should it assume ONLY the IP-based network services to be available? Looking at http://wiki.openstack.org/NetworkService, there