On Thu, Sep 22, 2011 at 5:12 PM, Salvatore Orlando <
salvatore.orla...@eu.citrix.com> wrote:
> Hi,
>
> ** **
>
> I have installed an Openstack testbed with Quantum (OVS Plugin) and
> standard nova IPAM. Hypervisor backend is XenServer.
>
> Although I managed to get a couple of VMs for two
On Thu, Sep 22, 2011 at 2:15 PM, Salvatore Orlando <
salvatore.orla...@eu.citrix.com> wrote:
> ** **
>
> For this reason I believe that Quantum API needs at least a WADL file. I’m
> voting for WADL in order to be consistent with the other Openstack projects,
>
>
That seems like the right call if
Hey Dan,
Replies below..
On Thu, Sep 22, 2011 at 6:33 PM, Dan Wendlandt wrote:
>
>
> On Thu, Sep 22, 2011 at 5:25 PM, Brad Hall wrote:
>>
>> >
>> > o QuantumManager.allocate_for_instance was failing because the JSON
>> > response from Quantum was not being serialized. I then looked at
>> > ne
On Thu, Sep 22, 2011 at 5:25 PM, Brad Hall wrote:
>
> >
> > o QuantumManager.allocate_for_instance was failing because the JSON
> > response from Quantum was not being serialized. I then looked at
> > network.quantum.client.py and found that if the response code was 202
> the
> > response was n
Hey Salvatore,
Replies inline..
On Thu, Sep 22, 2011 at 5:12 PM, Salvatore Orlando
wrote:
> Hi,
>
>
>
> I have installed an Openstack testbed with Quantum (OVS Plugin) and standard
> nova IPAM. Hypervisor backend is XenServer.
Thanks for trying it out.. sorry that you ran into issues.
>
> Alth
Hi,
I have installed an Openstack testbed with Quantum (OVS Plugin) and standard
nova IPAM. Hypervisor backend is XenServer.
Although I managed to get a couple of VMs for two different tenants up and
running on the appropriate networks, I had to do things that I feel I shouldn't
have done.
I ho
Hello Netstackers,
I've been working with the extensions framework lately and wanted to
know how data extensions are supposed to work. What I want to do is
something like this:
A hypothetical device that I'm writing a plugin for has a property on
the port called "foo" and I want to be able to cr
Andy, Dan,
The other Openstack projects currently provide a WADL file in their
documentation.
However, unlike WS-*, to the best of my knowledge, with RestFul Web Services
there's no official "schema" for documenting inputs and outputs for each
operation.
WADL files are typically used to this pu
Hi,
OK - I guess it is clear enough that the only allowed strings for port-state
are ACTIVE and DOWN, and hopefully the behavior for ACTIVE or DOWN
is roughly the same on all implementations.
It's more than a first step. It is very complete, except for the formal
schema..
Our application develo
On Thu, Sep 22, 2011 at 10:00 AM, Andy Bierman wrote:
> Hi,
>
> I read the API spec (again) and I have the same comment as last time.
>
> There are no normative definitions for any output from Quantum.
> IMO, a RelaxNG pattern is needed for every 'XML blob' that is defined
> by example.
>
> An ap
Hi,
I read the API spec (again) and I have the same comment as last time.
There are no normative definitions for any output from Quantum.
IMO, a RelaxNG pattern is needed for every 'XML blob' that is defined
by example.
An application needs to know the XML or JSON structure to expect.
It needs t
Hi Salvatore,
Great work.
I will review it and get back to you shortly.
Best,
Ying
From: netstack-bounces+yinliu2=cisco@lists.launchpad.net
[mailto:netstack-bounces+yinliu2=cisco@lists.launchpad.net] On
Behalf Of Dan Wendlandt
Sent: Thursday, September 22, 2011 8:51 AM
To: Sa
Great Salvatore,
I reviewed the new sections, they look good. I've added some typos to the
comments on the merge prop (
https://code.launchpad.net/~salvatore-orlando/quantum/quantum-api-doc/+merge/75588).
I'm fine fixing those myself when I merge into trunk, if that is easier for
you (Diablo rel
13 matches
Mail list logo
