Re: [openstack-dev] [Ceilometer] Allow multiple projects (tenants) in the received kwargs for v2 queries

[Julien Danjou]

On Wed, Sep 18 2013, Pendergrass, Eric wrote:

> What do you think about this?
>
> Can the 'project' key change to 'projects' to support this?

You can't change the current API, though you can extend it. Having some
sort of OR operator is something that I think we would like. However,
that's something that should be generic and apply to any field.

If you have some ideas around that, I support creating a blueprint to
design such a mechanism.

-- 
Julien Danjou
-- Free Software hacker - independent consultant
-- http://julien.danjou.info


signature.asc
Description: PGP signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Ceilometer] Allow multiple projects (tenants) in the received kwargs for v2 queries

[Pendergrass, Eric]

I'm implementing a role based access control system where I'll use a list of
projects to determine which projects a user can query.  This project list
will come from an upstream filter based on roles associated with the user's
auth token.

 

In the current v2/meters/ (Sample) code, the kwargs received are
{'project': u'10032339952700', 'meter': u'network.incoming.bytes'}.  This
indicates one project is received.

 

I'd like to increase the flexibility of some of the v2 API controllers by
allowing a list of projects to be received and subsequently sent to the
storage layer for use in filtering.

 

My questions are:

What do you think about this?

Can the 'project' key change to 'projects' to support this?

 

Any thoughts greatly appreciated.  If this sounds reasonable I'll put out a
blueprint for the change.

 

Thanks

Eric Pendergrass



smime.p7s
Description: S/MIME cryptographic signature
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev