All,
Anyone aware of Havana based work to create notifiers for ceilometer
which would push host/hyper capacity based metrics? For example
used/free values for cpu/mem/disk on a per host (hypervisor) basis?
Maybe my google-foo is weak this morning, but I didn't find anything
obvious.
Thanks
Hi,
I was poking around for a way to scope host aggregates at the domain
level and moreover support the notion multiple tenant access.
For example:
* As an Cloud provider, I want to isolate aggregates/availability zones
at the domain level (i.e. assign which domain can spawn instances on a
All,
From an upper level management stack perspective, has anyone else seen
the need for AMQP based notifications from Keystone identity and/or
heard of any activity in this space?
For example, similar to nova's notification system
(https://wiki.openstack.org/wiki/SystemUsageData based on
Consideration / food for thought...
I was recently standing up a grizzly based Cloud whereupon we were
implementing a fairly simple role based scheme and wanted to provide
some feedback on that experience with respect to setting up the
policy.json files properly.
Long story short -- I found
Defect created: https://bugs.launchpad.net/keystone/+bug/1055763
Thanks
On 9/21/2012 2:18 PM, Dolph Mathews wrote:
I'm not aware that this was ever implemented during essex (it was
available in diablo) -- definitely worth opening a bug!
-Dolph
On Fri, Sep 21, 2012 at 11:15 AM, boden
I came across the following Keystone dev API docs:
http://docs.openstack.org/api/openstack-identity-service/2.0/content/GET_listRolesForUserOnTenant_v2.0_tenants__tenantId__users__user_id__roles_Admin_API_Service_Developer_Operations-d1e1356.html
This set of keystone v2.0 docs includes documented
As per the Keystone v2.0 API docs, I've been trying to use the 'get user
by name' and 'get tenant by name' APIs to retrieve the respective
resource by name. The URI signatures are:
v2.0/users​?name=string
v2.0/tenants​?name=string
respectively.
However, both of these APIs are returning the full
I've been munking with the latest Keystone LDAP identity driver and
based on what I'm seeing the driver does not support the 'list' resource
based methods. For example 'list users', 'list tenants'...
For example, config your keystone.conf up to use an LDAP backend which
contains the supported DIT
On Mon, Sep 10, 2012 at 11:32 AM, Adam Young ayo...@redhat.com
mailto:ayo...@redhat.com wrote:
On 09/10/2012 11:29 AM, boden wrote:
I've been munking with the latest Keystone LDAP identity driver and
based on what I'm seeing the driver does not support the 'list
Hi,
I'm trying to better understand the current status of PKI
(http://wiki.openstack.org/PKI) and delegated authZ from a folsom
perspective. I can see the blueprint targets folsom-rc1, is marked as
implemented (https://blueprints.launchpad.net/keystone/+spec/pki) and
I've browsed some of the
All,
Although I'm still ramping up on OpenStack in general, it appears (via
visual code inspection and reading https://gist.github.com/2969337#id18)
there is no support from a REST API perspective to return translated
data to REST consumers by honoring the 'Accept-Language' in the request
header
All,
Is anybody here familiar with the 'sort_key' and 'sort_dir' parameters
for collection based APIs?
Specifically I'm wondering if there are any plans to add support for
these 2 params across the board (all collections based REST APIs
including the 'primary compute extensions')? Based on my
12 matches
Mail list logo
