We plan to have keystone support CRUD operations for those policy files with
the next API, but that API hasn't yet been nailed down. Regardless of where the
policy.json file comes from, I'd recommend creating one for quantum under
etc/policy.json (like nova does) that defines a set of actions, r
.@lists.launchpad.net
Date: 05/16/2012 04:48PM
Subject: Re: [Netstack] Want to start Keystone support for
Quantum Client
Hi,
On the IRC meeting last night the following was discussed
- https://blue
gt;
>
> -netstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -
> To: netstack@lists.launchpad.net
> From: Gary Kotton **
> Sent by: netstack-bounces+gongysh=cn.ibm@lists.launchpad.net
> Date: 05/16/2012 04:48PM
> Subject: Re: [Netstack] Want to start Keystone support
s.launchpad.net
From: Gary Kotton
Sent by: netstack-bounces+gongysh=cn.ibm@lists.launchpad.net
Date: 05/16/2012 04:48PM
Subject: Re: [Netstack] Want to start Keystone support for
Quantum Client
he beginning. Is there a special
>> blueprint for API?
> Not that I am aware of.
>>
>> Thanks
>>
>>
>> -netstack-bounces+gongysh=cn.ibm@lists.launchpad.net wrote: -
>> To: netstack@lists.launchpad.net
>> From: Gary Kotton
>> Sent by: netstac
n.ibm@lists.launchpad.net
Date: 05/16/2012 04:48PM
Subject: Re: [Netstack] Want to start Keystone support for Quantum Client
Hi,
On the IRC meeting last night the following was discussed -
https://blueprints.launchpad.net/quantum/+spec/authorization-support-for-quantum.
Are these tasks mutually excl
start Keystone support for Quantum Client
Hi,
On the IRC meeting last night the following was discussed -
https://blueprints.launchpad.net/quantum/+spec/authorization-support-for-quantum.
Are these tasks mutually exclusive?
I guess that with the Melange addition the client AP
Hi,
On the IRC meeting last night the following was discussed -
https://blueprints.launchpad.net/quantum/+spec/authorization-support-for-quantum.
Are these tasks mutually exclusive?
I guess that with the Melange addition the client API may also change -
all I have seen is http://etherpad.openst
hi,Do we have a blueprint for quantum api2.0? I think we have no need to change the old clients for 1.0 and 1.1 api. I will have the new client based on the new api 2.0.Thanks.-Yong Sheng Gong/China/IBM wrote: -To: netstack@lists.launchpad.netFrom: Yong Sheng Gong/China/IBMDate: 05/12/20
On Mon, 2012-05-14 at 09:30 -0700, Dan Wendlandt wrote:
> I think Jason is cool with this, so I'll reassign that existing
> blueprint
> to you.
I am definitely cool with it ;)
Happy Hacking!
7-11
--
Mailing list: https://launchpad.net/~netstack
Post to : netstack@lists.launchpad.net
Unsu
Thanks for putting this together Yong!
Comments inline.
On Fri, May 11, 2012 at 4:21 PM, Yong Sheng Gong wrote:
> Hi,
> I want to start a blueprint to implement the "*Keystone support for
> Quantum Client*" listed in http://wiki.openstack.org/QuantumStarterBugs
>
> Workflows:
> My idea is to ma
Hi,
How can I help with the common openstack client? I think quantum needs
its own client to be implemented first and then common openstack client
(just as a thin wrapper) can call the client module if we have quantum
client designed as nova client.
Thanks -netstack-bounces+gongysh=cn.ibm.
On Fri, 2012-05-11 at 18:44 -0500, Jason Kölker wrote:
> On Sat, 2012-05-12 at 07:21 +0800, Yong Sheng Gong wrote:
> > Hi,
> > I want to start a blueprint to implement the "Keystone support for
> > Quantum Client" listed in http://wiki.openstack.org/QuantumStarterBugs
> >
> I would recommend helpi
On Sat, 2012-05-12 at 07:21 +0800, Yong Sheng Gong wrote:
> Hi,
> I want to start a blueprint to implement the "Keystone support for
> Quantum Client" listed in http://wiki.openstack.org/QuantumStarterBugs
>
I would recommend helping the common client guys out with their
implementation.
Happy Hac
Hi,I want to start a blueprint to implement the "Keystone support for Quantum Client" listed in http://wiki.openstack.org/QuantumStarterBugsWorkflows:My idea is to make an initial workable quantum client with keystone service support.Quantum client's workflow will look like:1. To send auth request
15 matches
Mail list logo
