Hi Netstackers,
I have pushed for review a proposal for the operational status blueprint.
The changeset is available here: https://review.openstack.org/#change,2097
Please note that this changeset is stacked upon api-framework-essex,
which is still waiting for an approval after the reviewers' c
On Tue, Dec 6, 2011 at 8:55 AM, Salvatore Orlando <
salvatore.orla...@eu.citrix.com> wrote:
> Hi Netstackers,
>
> I have pushed for review a proposal for the operational status blueprint.
> The changeset is available here: https://review.openstack.org/#change,2097
>
Great. For an small API chan
For those who are curious, the thread I was referring to has the subject
line: [Netstack] Wiki page for operational status in Quantum API
On Tue, Dec 6, 2011 at 9:34 AM, Dan Wendlandt wrote:
>
>
> On Tue, Dec 6, 2011 at 8:55 AM, Salvatore Orlando <
> salvatore.orla...@eu.citrix.com> wrote:
>
>
Hello Netstackers,
I have the initial blueprint and associated design wiki available for AuthZ
in Quantum. I have proposed to implement a simplistic first step AuthZ
capability in Quantum leveraging Keystone tokens and roles.
Blueprint --
https://blueprints.launchpad.net/quantum/+spec/authorizati
Hi folks,
One quick of the Quantum API that is potentially confusing is that we use
non-standard HTTP error codes to provide specialized error codes. For
example, instead of a 404 for any not found, we have 420 for "network not
found" and 430 for "port not found". This could be potentially usefu
Dan, Salvatore, folks,
The issue I've seen with this was an error in quantum that raised an unexpected
error within nova, causing a 500 to bubble back to the api. It was a miss
configuration that caused the initial error, but it could have occurred in the
wild as well. This will occur for other
6 matches
Mail list logo
