On 20/07/15 18:50, Ian Wells wrote:
On 20 July 2015 at 10:21, Neil Jerram neil.jer...@metaswitch.com
mailto:neil.jer...@metaswitch.com wrote:
Hi Ian,
On 20/07/15 18:00, Ian Wells wrote:
On 19 July 2015 at 03:46, Neil Jerram
neil.jer...@metaswitch.com
Hi Ian,
On 20/07/15 18:00, Ian Wells wrote:
On 19 July 2015 at 03:46, Neil Jerram neil.jer...@metaswitch.com
mailto:neil.jer...@metaswitch.com wrote:
The change at [1] creates and describes a new 'routed' value for
provider:network_type. It means that a compute host handles data
On 20 July 2015 at 10:21, Neil Jerram neil.jer...@metaswitch.com wrote:
Hi Ian,
On 20/07/15 18:00, Ian Wells wrote:
On 19 July 2015 at 03:46, Neil Jerram neil.jer...@metaswitch.com
mailto:neil.jer...@metaswitch.com wrote:
The change at [1] creates and describes a new 'routed' value
On 19 July 2015 at 03:46, Neil Jerram neil.jer...@metaswitch.com wrote:
The change at [1] creates and describes a new 'routed' value for
provider:network_type. It means that a compute host handles data
to/from the relevant TAP interfaces by routing it, and specifically
that those TAP
Hi Neutron folk!
I'd like to give an update on and encourage wide review of my work on
a type of network that connects VMs through IP routing instead of
through bridging and tunneling at L2. I believe the core Neutron
pieces of this are now complete and ready for detailed review and
potential
