Thanks Kris and Sam for your replies!
On 18/06/15 01:20, Kris G. Lindgren wrote:
On 6/17/15, 10:59 AM, Neil Jerram neil.jer...@metaswitch.com wrote:
On 17/06/15 16:17, Kris G. Lindgren wrote:
See inline.
Kris Lindgren
Senior Linux Systems
On 6/17/15, 10:59 AM, Neil Jerram neil.jer...@metaswitch.com wrote:
On 17/06/15 16:17, Kris G. Lindgren wrote:
See inline.
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.
On 6/17/15, 5:12 AM, Neil Jerram
Hi Kris,
Apologies in advance for questions that are probably really dumb - but
there are several points here that I don't understand.
On 17/06/15 03:44, Kris G. Lindgren wrote:
We are doing pretty much the same thing - but in a slightly different way.
We extended the nova scheduler to
On 17/06/15 16:17, Kris G. Lindgren wrote:
See inline.
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.
On 6/17/15, 5:12 AM, Neil Jerram neil.jer...@metaswitch.com wrote:
Hi Kris,
Apologies in advance for questions that are probably
Adding -dev because of the reference to the Neutron Get me a network
spec. Also adding [nova] and [neutron] subject markers.
Comments inline, Kris.
On 05/22/2015 09:28 PM, Kris G. Lindgren wrote:
During the Openstack summit this week I got to talk to a number of other
operators of large
We are doing pretty much the same thing - but in a slightly different way.
We extended the nova scheduler to help choose networks (IE. don't put
vm's on a network/host that doesn't have any available IP address). Then,
we add into the host-aggregate that each HV is attached to a network
metadata
We at NeCTAR are starting the transition to neutron from nova-net and neutron
almost does what we want.
We have 10 “public networks and 10 “service networks and depending on which
compute node you land on you get attached to one of them.
In neutron speak we have multiple shared externally
