To add more context to what Nachi quoted, in general the operational status
of a virtual advanced network service depends on the drivers that
implements it.
So far, the drivers being developed for firewall, VPN, and possibly even
Load Balancing all implement the same architecture. In my opinion it
On Thu, 25 Jul 2013 10:29:47 -0400
Sean Dague s...@dague.net wrote:
Some new tempest tests have been showing up that push deeper into the
Nova API, and popping out seem to be a lot of places where we are
returning 422 status codes.
422 is WebDav reserved code, not in a proper HTTP spec
Comments in the review as well. There are a couple of tabs that need
to be cleaned up, then I'm good. What's the long term outlook for
floating-ips, security groups, and aggregates for cells?
On Fri, Jul 26, 2013 at 9:22 PM, Chris Behrens cbehr...@codestud.com wrote:
I have just put up a review
Am 24. Juli 2013 18:00:30 schrieb Monty Taylor mord...@inaugust.com:
On 07/23/2013 03:02 PM, Brian Curtin wrote:
On Jul 23, 2013, at 3:51 PM, Eric Windisch e...@cloudscaling.com
mailto:e...@cloudscaling.com
wrote:
On Tue, Jul 23, 2013 at 4:41 PM, Logan McNaughton lo...@bacoosta.com
Forwarding to -dev from -operators.
Any know why when a fixed-ip gets added to an external network guest port,
all connectivity on all fixedips for the guest on the external network get
block outbound on the compute node?
John
-- Forwarded message --
From: John Gruber
On 7/26/2013 10:39 AM, Jay Pipes wrote:
On 07/26/2013 08:04 AM, Sean Dague wrote:
Also there are EC2 design points that have request lengths greater than
what Apache (or any other web front end) is compiled to support, as they
have the possibility of enourmous GET strings (16K at least).
- Original Message -
From: Dolph Mathews dolph.math...@gmail.com
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Sent: Saturday, 27 July, 2013 4:56:10 AM
Subject: Re: [openstack-dev] Proposal for API version discovery
On Wed, Jul 24, 2013 at 12:41 AM,
On 07/26/2013 05:43 AM, Thierry Carrez wrote:
I would rather support solution 3: create a single, separate executable
that does those 20 things that need to be done (can be a shell script
with some logic in it), and have rootwrap call that *once*. That way you
increase speed by 20 times
