Select Register New Email at the link provided in the error message (using
yorik@gmail.com, if you have not already) and confirm your address using
the link which is then emailed to you.
remote: ERROR: You have not registered any email addresses.
remote: ERROR:
remote: ERROR: To register
++
-Dolph
On 08/26/2011 02:46 PM, Mark Collier wrote:
+1
On 8/26/11 1:19 PM, Devin Carlendevin.car...@gmail.com wrote:
Hey all,
I've been following the code vs architect debate that's been unfolding
over the past week or so. Here are some of the problems I've seen from
my point of
Instead of a mailing list full of political posturing around our
toolset, how about someone post a concrete problem with gerrit, and
we'll pretend to be a bunch of engineers and solve it.
-Dolph
On 09/08/2011 04:27 AM, Chris Behrens wrote:
Sure, I agree with the below. I tend to think the
Keystone was just revised to separate Tenant id's from names.
ID's are now backend-managed (auto-incremented SQL primary keys, for example),
while names are read/writable through the admin API.
The same change also applies to Users (and Roles is in the works).
-Dolph
On 09/14/2011 12:32 AM,
I believe this review satisfies the remaining requirements that keystone was
lacking:
https://review.openstack.org/#change,516
See the new functional test in keystone/test/functional/test_auth.py:
test_user_auth_with_role_on_tenant(), which illustrates the flow you outlined.
At the moment,
versioning very thoroughly, and it needed to be updated to *something*
post-diablo. So, this is certainly open to feedback/suggestions/discussion!
-Dolph
From: Mark McLoughlin [mar...@redhat.com]
Sent: Monday, October 24, 2011 2:03 AM
To: Ziad Sawalha; Dolph
the October release...)
-Dolph
From: Mark McLoughlin [mar...@redhat.com]
Sent: Monday, October 24, 2011 10:36 AM
To: Dolph Mathews
Cc: Ziad Sawalha; Thierry Carrez; openstack@lists.launchpad.net
Subject: RE: Keystone versioning and tarballs
Hi Dolph,
On Mon
+11
On Thu, Oct 27, 2011 at 8:56 AM, George Reese george.re...@enstratus.comwrote:
Version and content desired belong in the headers for request and response.
The imaginary crap you are dealing with a) don't require them in a URL
unless you are pulling it from the URL bar of a browser, which
Looking for some support from anyone with experience with
sqlalchemy-migrate on the following review...
https://review.openstack.org/#change,1200
See my Nov 1 comment -- sqlalchemy's built-in `./manage.py test` command
fails, but you can test each migration individually (forward backward)
and
Yogi just answered my question below -- In short, the ./manage.py test
command didn't behave as I understood.
It simply tests the latest migration forwards backwards, not the entire
history of migrations in sequence.
Thanks, Yogi!
-Dolph
On Fri, Nov 4, 2011 at 10:37 AM, Dolph Mathews
I flooded gerrit with 34 reviews picked from trunk this afternoon that are
proposed to form the basis of keystone's diablo+ stable release.
There are a few pending trunk commits (namely DB migrations and a bug fix
to follow) that need to be included as well, but in the mean time, your
+1's and
Because it should be keystone's responsibility to test it's constant stream
of API changes, and abstract that away from it's consumers.
On Mon, Nov 7, 2011 at 3:25 PM, Caitlin Bestler caitlin.best...@nexenta.com
wrote:
Monty Taylor wrote:
OpenStack projects that need to depend on these will
Keystone needs your help testing!
The goal of this branch is to be completely compatible with diablo,
while including as many improvements as possible. Pending your
satisfaction, we'd like to tag this branch in the coming days.
Browse stable/diablo:
should
probably reference the commit 6baa62c28fd5594127017be3680eee6578b4b7f6 ?
(Cc'ing Dolph Mathews)
--
Julien Danjou
// eNovance http://enovance.com
// ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81
___
Mailing list
The unscoped token keystone returns to you allows you to call GET /tenants
and exchange your unscoped token for one scoped to a tenant. This is
documented in the API developer guide, but the following functional test
illustrates the flow from a client perspective pretty well:
The first command (templated version response) failing is non-critical (the
functional calls should still work), but it looks like keystone isn't
finding it's static content where expected.
Where is keystone actually located in your install? (not /usr/keystone/?)
Ping me on IRC (dolphm) if
Yes (and there's actually more than 2 floating around, in various states);
we're moving towards providing a single client, independent of keystone,
which can be consumed by other projects (including keystone itself).
There's no milestone target for this effort yet, but:
, 2011 at 8:43 AM, Julien Danjou
julien.dan...@enovance.comwrote:
On Fri, Dec 16 2011, Dolph Mathews wrote:
Yes (and there's actually more than 2 floating around, in various
states);
we're moving towards providing a single client, independent of keystone,
which can be consumed by other
Just an FYI, I'm adding prettytable as a dependency to keystone as part
of our keystone-manage2
(blueprinthttps://blueprints.launchpad.net/keystone/+spec/keystone-manage2)
implementation.
Blueprint: https://blueprints.launchpad.net/keystone/+spec/keystone-manage2
PyPi:
Ewan,
Thanks for the detailed report -- that definitely is an odd behavior.
I'm fine with the shortcut pattern, although my instinct says the system is
getting itself into a state that shouldn't be in at all, and I'd like to spend
some time reproducing it.
-Dolph Mathews
On Jan 13, 2012
How did you install MySQL? What permissions does keystone's MySQL user have
over the database?
-Dolph Mathews
On Jan 14, 2012, at 5:51 AM, Xuyun Zhang xyzhan...@gmail.com wrote:
I set the database by running ./sampledata
Then I tried to use curl to get tokens, the command is:
$ curl -d
It is definitely not a documented call (hence the should this be removed?
comment in the implementation); if it were to be promoted from
undocumented to an extension, I imagine it would belong in OS-KSADM.
- Dolph
On Thu, Jan 26, 2012 at 10:51 AM, Yee, Guang guang@hp.com wrote:
I see it
A) This wasn't documented at all (AFAIK), so there's no concern of breaking
contracts.
B) Even if it's moved to an extension, would the call change from it's current
form?:
DELETE /tokens/{token_id}
I'm not sure what the extension convention is here.
-Dolph Mathews
On Jan 26, 2012, at 4
My fault! see https://bugs.launchpad.net/devstack/+bug/925718
Keystone standardized it's config file to use underscores at some point
during essex, and started throwing warnings if you continued to use
hyphens. I patched devstack to produce a config file matching the current
version of keystone.
items we are working on adding to redux at time of writing.
Support for XML and LDAP integration. We propose evaluating the merge with
these known issues, as work is being done to re-add support before E4.
State of XML (via Dolph Mathews)
Work is underway to support the existing XSD/WADLs
To answer the second half of your question:
keystoneclient cli does not support list-roles-for-user
https://bugs.launchpad.net/keystone/+bug/932282
On Thu, Mar 8, 2012 at 4:46 PM, Jason Hedden jhed...@mcs.anl.gov wrote:
It seems a little odd that the mapping of users to roles is
Proposed fix: https://review.openstack.org/#change,5153
Usage:
$ keystone role-list --user=user-id --tenant_id=tenant-id
On Thu, Mar 8, 2012 at 10:01 PM, Deepak Garg deepakgarg.i...@gmail.comwrote:
I have also been trying to find a cli to get a user's role in a
particular tenant.
I could
The 'file' handler is missing from your loggers; in other words, logging to a
file is not enabled, as-is. Try:
[logger_keystone]
level=ERROR
handlers=file
qualname=keystone
-Dolph Mathews
On Mar 19, 2012, at 12:47 AM, Andrew Michael Weiss wei...@purdue.edu wrote:
Hey Kevin,
I have found
With: https://review.openstack.org/#change,5528
Out of the box:
1) uncomment log_config in keystone.conf
2) Run ./bin/keystone-all (with proposed logging configuration, no output
will occur on the CLI)
3) ./keystone.log will be produced containing WARNING / ERROR / CRITICAL.
On Mon, Mar 19,
Wasn't this fixed in keystoneclient (properly handling an unexpected
trailing slash)?
-Dolph
On Wed, Mar 21, 2012 at 6:56 PM, Gabriel Hurley
gabriel.hur...@nebula.comwrote:
It looks like you’ve got an extra slash in your URL. That probably means
you’ve got a trailing slash on your
keystoneclient ($ keystone) is actually the new way to perform these types
of operations instead of keystone-manage ($ keystone-manage)
You'll first need to let keystoneclient authenticate with your keystone
server as an admin, see:
I'm not sure if there's an open bug on this or not (definitely should be), but
you're attempting to perform operations using a SERVICE_TOKEN and
SERVICE_ENDPOINT (
that require
-Dolph Mathews
On Mar 22, 2012, at 1:42 PM, Joshua Harlow harlo...@yahoo-inc.com wrote:
Hi all,
When trying
Accidentally hit send...
Anyway... which does not necessarily correspond to a normal user with a service
catalog.
The error message should explain this and direct you to use an OS_USERNAME,
OS_PASSWORD, OS_TENANT_* and OS_AUTH_URL instead (which can have a service
catalog).
-Dolph Mathews
=demo
On 3/22/12 1:39 PM, Dolph Mathews dolph.math...@gmail.com wrote:
Accidentally hit send...
Anyway... which does not necessarily correspond to a normal user with a
service catalog.
The error message should explain this and direct you to use an
OS_USERNAME,
OS_PASSWORD
( This is significant gap in the current keystone docs, so I'll be ensuring
this makes it into the docs ASAP; feedback here is very much appreciated! )
There are two driver options for your service catalog - one based on a flat
file, and one backed by SQL. The flat file does not support
Agree with the other posters; Keystone is not reachable from Horizon --
make sure it's running, keystone's IP and ports are reflected correctly in
horizon config, etc.
-Dolph
On Mon, Mar 26, 2012 at 6:21 AM, Guilherme Souza
souza.guilherm...@gmail.com wrote:
Hello Razique,
What do you want
I think I'm to blame (apologies!) for suggesting that one driver was
preferred over the other (that was my understanding a few weeks ago, based
on test coverage). However, test coverage has since improved and I think
people are having good experience with the SQL driver.
The two methods are *not*
in, but it had identified a problem on access, then i up the
service and i can log in. Them i think that's a bug, cannot be another
thing once that all configurations are right.
Em 26 de março de 2012 13:11, Dolph Mathews dolph.math...@gmail.comescreveu:
Agree with the other posters; Keystone
jaypi...@gmail.com wrote:
On 03/26/2012 11:43 AM, Dolph Mathews wrote:
( This is significant gap in the current keystone docs, so I'll be
ensuring this makes it into the docs ASAP; feedback here is very much
appreciated! )
There are two driver options for your service catalog - one based
Chmouel,
That's pretty much the strategy keystone does already; the problem you're
seeing is just a completely useless error message. A bug with tagged for RC
would be helpful.
-Dolph
On Tue, Mar 27, 2012 at 10:35 AM, Chmouel Boudjnah chmo...@chmouel.comwrote:
Hello,
Posting here, as I am
Nicolas,
It looks like that guide was written for the diablo (or perhaps pre-diablo)
keystone API. The corrections you're suggesting are accurate to bring the
guide forward to essex.
However, you might find the following a bit easier, as we now have a real
auth client
That would do it! Glad you found your problem.
I'll be working on improving the docs for building your service catalog
pretty soon; common issues like this are useful to know about.
-Dolph
On Fri, Mar 30, 2012 at 11:03 PM, Pete Zaitcev zait...@redhat.com wrote:
On Sat, 31 Mar 2012 10:26:10
Included one answer for you below :)
-Dolph
On Tue, Apr 3, 2012 at 9:53 AM, Pierre Amadio
pierre.ama...@canonical.comwrote:
The ubuntu user is associated to the admin role (i know i did it with
keystone user-role-add , altough i m not sure how to list the role of a
given user to double
for improvement
there as well.
-Dolph Mathews
On Apr 25, 2012, at 11:37 AM, Nguyen, Liem Manh liem_m_ngu...@hp.com wrote:
I would like to keep the service type and name under the service and not the
endpoint, too. Make it easier to parse for a given service.
One thing is that I am not sure if we
specific ways that don't lock in other systems to
be deployed and implemented in the same fashion.
** **
-joe
** **
** **
On Apr 20, 2012, at 1:47 PM, Lorin Hochstein wrote:
On Apr 13, 2012, at 12:34 PM, Adam Gandelman wrote:
On 04/13/2012 10:50 AM, Dolph Mathews wrote
to
be deployed and implemented in the same fashion.
-joe
On Apr 20, 2012, at 1:47 PM, Lorin Hochstein wrote:
On Apr 13, 2012, at 12:34 PM, Adam Gandelman wrote:
On 04/13/2012 10:50 AM, Dolph Mathews wrote:
While $(tenant_id)s is certainly the documented syntax, it appears that
the SQL catalog
wrote:
On 04/13/2012 10:50 AM, Dolph Mathews wrote:
While $(tenant_id)s is certainly the documented syntax, it appears that
the SQL catalog backend (and *only* the SQL catalog backend, as far as I
can tell) explicitly supports both $(tenant_id)s and %(tenant_id)s:
** **
https
to
be deployed and implemented in the same fashion.
-joe
On Apr 20, 2012, at 1:47 PM, Lorin Hochstein wrote:
On Apr 13, 2012, at 12:34 PM, Adam Gandelman wrote:
On 04/13/2012 10:50 AM, Dolph Mathews wrote:
While $(tenant_id)s is certainly the documented syntax, it appears that the
SQL catalog backend
the API).
-Dolph Mathews
On Apr 26, 2012, at 7:58 PM, Adrian Moya adrianm...@gmail.com wrote:
Hi everyone, I'm currently building a customer panel to offer public cloud
services based on openstack. I'd like to share my plans to validate my
approach is good and hear suggestions/feedback from
It looks like the PDF is rendering trying to render the outside quotes as
\\paired smart quotes// instead of ||regular double quotes||.
Try this instead: http://paste.openstack.org/raw/14073/
-Dolph
On Fri, Apr 27, 2012 at 9:35 AM, Shake Chen shake.c...@gmail.com wrote:
HI
Canonical
I very much like the idea that we should have a well documented
recommendation on this topic.
My only criticism is that the API/service names should be used in place of
project names, e.g. https://hostname/identity, https://hostname/compute,
etc.
-Dolph
On Mon, Apr 30, 2012 at 11:34 AM, Adam
On Mon, Apr 30, 2012 at 1:18 PM, Doug Hellmann
doug.hellm...@dreamhost.comwrote:
On Mon, Apr 30, 2012 at 12:13 PM, Adam Spiers aspi...@suse.com wrote:
Dean Troyer (dtro...@gmail.com) wrote:
One of the first things to do is to find out who is interested in
contributing to this project.and
On Apr 30, 2012, at 3:20 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Mon, Apr 30, 2012 at 01:58:24PM -0500, Dolph Mathews wrote:
I very much like the idea that we should have a well documented
recommendation on this topic.
My only criticism is that the API/service names should
I disagree with all three... the line between admin and not admin is
going to get very blurry in the long run. Example: I may be a regular user,
but I've been granted what is normally an admin capability on tenant X.
Does that make me an admin? Do I now need to use two different clients?
I also
depending on how we are
tracking API versioning inside of the client.
So I suppose the question is... how does the client approach API
versioning?
-Matt
On Wed, May 2, 2012 at 6:14 AM, Dolph Mathews dolph.math...@gmail.com
wrote:
I disagree with all three... the line between admin
The philosophy in essex is that it's meaningless for a user to have a role
without that role being applied to a tenant, so the call that's implemented
is:
GET /tenants/{tenant_id}/users/{user_id}/roles
Calling this instead should get you an HTTP 501 stating User roles not
supported: tenant
service-list calls the admin API (port 35357), but the auth_url you
provided was port 5000. I don't think the current keystoneclient is smart
enough to try and switch to the correct endpoint. If you have an admin
role, switching to port 35357 should work for you.
Additionally, you won't get a
/GET_listRolesForUserOnTenant_v2.0_tenants__tenantId__users__user_id__roles_Admin_API_Service_Developer_Operations-d1e1356.html
Everett
On Thu, May 3, 2012 at 9:34 AM, Dolph Mathews dolph.math...@gmail.comwrote:
The philosophy in essex is that it's meaningless for a user to have a
role without that role being applied to a tenant, so the call that's
implemented is:
GET
, 2012 at 1:08 AM, Dolph Mathews dolph.math...@gmail.comwrote:
service-list calls the admin API (port 35357), but the auth_url you
provided was port 5000. I don't think the current keystoneclient is smart
enough to try and switch to the correct endpoint. If you have an admin
role, switching
This actually just changed yesterday in
https://github.com/openstack/python-keystoneclient/commit/e9ba370434537bcf1e53266e24397311d595b71e
PRIOR to that commit:
$ keystone help role-list
usage: keystone role-list [--user user-id] [--tenant_id tenant-id]
List all roles, or only those granted to
Your swift endpoint appears to be literally configured in keystone as
http://${SWIFT_HOST}:8080/v1/...; -- I'm guessing that's unreachable :)
Based on your logs, I'm not certain that will fix your 500, however.
-Dolph
On Mon, May 7, 2012 at 5:23 AM, Leander Bessa leande...@gmail.com wrote:
leande...@gmail.com wrote:
Does that mean that glance is somehow configured to use swift as storage
instead of the local file system or is does the error simply occur due to
the a parsing error because of ${SWIFT_HOST}?
On Mon, May 7, 2012 at 2:59 PM, Dolph Mathews dolph.math...@gmail.comwrote
The request URL is actually fine, but the request body is quite malformed:
{tenantName: labSpaceDemo, passwordCredentials: {username:
adminUser,
password: lfplhfgthvf}}}
What's there would be just fine if it were wrapped in an auth element
(see
It also just occurred to me that perhaps you're using a *very* old
novaclient against a more recent version of keystone?
-Dolph
On Wed, May 9, 2012 at 3:30 PM, Dolph Mathews dolph.math...@gmail.comwrote:
The request URL is actually fine, but the request body is quite malformed
Hrm, good catch! I see no problems with that request at all...
-Dolph Mathews
On May 9, 2012, at 5:58 PM, Kevin L. Mitchell kevin.mitch...@rackspace.com
wrote:
On Wed, 2012-05-09 at 15:32 -0500, Dolph Mathews wrote:
It also just occurred to me that perhaps you're using a *very* old
an
explicit relationship between the two. Using default tenants is optional with
this method, but will affect how users must auth.
-Dolph Mathews
On May 9, 2012, at 3:46 PM, Joshua Harlow harlo...@yahoo-inc.com wrote:
A question,
I am using anvil to setup the keystone roles/users/tenants
+1
The second way to accomplish this is exactly what keystone currently supports
(explicit role grants), which didn't change between diablo and essex at all.
The first method (using global unscopedness) was dropped because its just as
confusing as you describe it.
-Dolph Mathews
On May 10
Services
Nimbis Services, Inc.
www.nimbisservices.com
On May 10, 2012, at 3:50 AM, Dolph Mathews wrote:
+1
The second way to accomplish this is exactly what keystone currently
supports (explicit role grants), which didn't change between diablo and
essex at all.
The first method (using
/
keystone log is empty.
Regards,
Leander
On Mon, May 7, 2012 at 4:51 PM, Dolph Mathews dolph.math...@gmail.comwrote:
There's not enough information in those logs to say (check your glance
config and glance/keystone logs) -- but you'll definitely need to recreate
that endpoint
Can you paste those deprecation warnings, your keystone.conf, and logging.conf?
-Dolph Mathews
On May 10, 2012, at 10:37 AM, Leander Bessa Beernaert leande...@gmail.com
wrote:
Both. The log file is completely empty and the stdout only prints deprecation
warnings :/
On Thu, May 10, 2012
There's a very related open review in progress concerning the auth_token
docs at http://keystone.openstack.org/ as well.
https://review.openstack.org/#/c/7217
-Dolph
On Thu, May 10, 2012 at 12:09 AM, Milind milindkpa...@gmail.com wrote:
Hi,
In Admin installation document guide of Ubuntu
On Fri, May 11, 2012 at 2:25 PM, Joshua Harlow harlo...@yahoo-inc.comwrote:
Cool, I’m glad that is the ultimate goal.
Working on it! https://blueprints.launchpad.net/keystone/+spec/rbac-keystone
It seems like nova should be asking keystone for an initial policy
template of some kind,
I'm not sure if you have a weird copy/paste there or not, but the line with
multiple imports shouldn't work at all (it should work as three separate
lines).
import ldap
import keystone
import keystone.identity
If python-ldap is correctly installed, you should definitely be able to do
I haven't tested it myself, but I imagine you *could* deploy
legacy_token_auth (which rewrites from keystone stable/diablo or essex-3
with stable/essex or folsom; however, there are a couple of issues that
need to be resolved first.
The output to the curl command below should definitely point you in the
right direction -- devstack is expecting keystone to return an
authentication response there, but it's getting something else instead.
Feel free to paste the results to the list.
-Dolph
On Wed, May 23, 2012 at 11:47 PM,
The wiki page for meetings has a link to an iCal feed you can subscribe to:
http://wiki.openstack.org/Meetings
Direct iCal link: http://goo.gl/okDGE
On Wed, May 23, 2012 at 10:43 PM, Paul Belanger
paul.belan...@polybeacon.com wrote:
On 12-05-23 10:00 PM, Jay Pipes wrote:
The weekly QA Team
keystoneclient is looking for enough arguments for it to either fully
authenticate or bypass authentication.
To fully authenticate:
keystone --os_username=admin --os_password=secret
--os_tenant_name=project-x --os_auth_url=http://keystone:5000/v2.0/tenant-list
To bypass authentication (i.e. you
That's just a warning you can safely ignore for now (and a known issue):
https://bugs.launchpad.net/keystone/+bug/936404
On Thu, May 31, 2012 at 12:09 PM, Từ Minh Mẫn tuminh...@gmail.com wrote:
Dear all,
When I Create Tenants: I use command: keystone tenant-create --name admin,
Have error: No
Can you share your keystone configuration and keystoneclient configuration? A
400 could be as simple as the keystone service not running.
-Dolph Mathews
On Jun 2, 2012, at 1:48 AM, Từ Minh Mẫn tuminh...@gmail.com wrote:
When I try to do tenant-create I also have problem:
No handlers could
it to be done with
case-insensitivity to avoid confusion.
However, the machine-readable identifier is really intended to be the Role ID
(UUID, etc) from keystone.
-Dolph Mathews
On Jun 8, 2012, at 6:35 PM, Christopher B Ferris chris...@us.ibm.com wrote:
case-insensitive - why would 'Admin' and 'admin
On Jun 8, 2012, at 6:47 PM, Nguyen, Liem Manh liem_m_ngu...@hp.com wrote:
Hi Joe/Dolph,
I have a few questions on the v3 API’s create_user (sorry the comments
section in the Google docs is getting pretty cluttered now):
(POST) /users == create_user
{
tenant_id: ...
name: ...
The X-Subject-Token solution is definitely not valid HTTP, in that it
implies that two otherwise identical requests for GET /tokens would return
two completely different results (hence the need for a Vary header, as we
include for X-Auth-Token).
I have a slightly more proper (and complicated)
The URL http://192.168.20.7:5000/auth/v1.0 is not one supported by
keystone; does that command work if you use http://AUTH_HOSTNAME:5000/v2.0
instead?
For anyone interested, direct link to the doc in question:
Alternatively, if anyone would like to tar and feather me for picking port
5000 in the first place, I'm available. That said, I have no attachment to
port 5000... but I'm curious, are people experiencing real issues trying to
use port 5000?
-Dolph
On Wed, Jun 20, 2012 at 6:16 PM, Joseph Heck
If you let webob calculate the Content-Length by itself it won't resort to
adding a Transfer-Encoding header:
https://review.openstack.org/#/c/8818
On Thu, Jun 21, 2012 at 12:54 PM, Tomasz Paszkowski ss7...@gmail.comwrote:
I have created bug report:
Easy +1
-Dolph Mathews
On Jun 26, 2012, at 4:06 PM, Joseph Heck he...@mac.com wrote:
Given his work in Keystone since the redux, I would like propose Adam Young
(ayoung) be added to the group keystone-core.
For a process in doing this, I thought we'd generally follow Nova's
core
On Jul 3, 2012, at 4:55 PM, Adam Young ayo...@redhat.com wrote:
However, nothing in the API comments on the token length.
This is very intentional! If a specific length is documented somewhere, it
should be corrected.
-Dolph Mathews
___
Mailing
The SERVICE_ENDPOINT and SERVICE_TOKEN variables are effectively overriding
the corresponding OS_* variables from your environment (they're not
intended to be used together); try removing the SERVICE_* variables.
The OS_* variables provide a normal authentication flow while the SERVICE_*
REPOSE would be worth taking a look at, as well (includes rate limiting):
https://github.com/rackspace/repose
http://openrepose.org/documentation.html
-Dolph
On Wed, Jul 11, 2012 at 9:19 AM, Kevin L. Mitchell
kevin.mitch...@rackspace.com wrote:
On Wed, 2012-07-11 at 01:50 +0200, Rafael
On Thu, Jul 12, 2012 at 2:37 PM, George Reese george.re...@enstratus.comwrote:
This ain't the first time I've had a run in with you where your response
was essentially if you don't like it, go code it.
And obviously you missed the entire constructive point in my response.
It's this:
The
The philosophy from the keystone side of the fence is that once you have
non-unique names you can't go back; whereas, it's trivial to go from unique
to non-unique names. So, without a solid business case to push us in either
direction, we started by enforcing uniqueness.
With the Identity API v3
Adam speaks lies ;)
Here's a regular user requesting a list of tenants on port 5000 (notice
they only get back 1 tenant):
GET http://localhost:5000/v2.0/tenants
==
X-Auth-Token: a6094f62e38c4fafa57e6edf7bd04961
200 OK
==
Status: 200
Content-Length: 133
not documented
anywhere if it exists.
-Matt
On Tue, Jul 17, 2012 at 2:19 PM, Matt Joyce
matt.jo...@cloudscaling.comwrote:
Works for me. =D
On Tue, Jul 17, 2012 at 1:51 PM, Dolph Mathews
dolph.math...@gmail.comwrote:
Adam speaks lies ;)
Here's a regular user requesting a list
Try running the same command with the --debug option, and share the output
here.
Thanks,
-Dolph
On Sunday, July 22, 2012, MURAOKA Yusuke wrote:
Hi,
There is devstack all-in-one openstack builder. http://devstack.org/
Officially, its not supporting RHEL 6.1 on the site. But its only
Replace AUTH_HOSTNAME with the IP/hostname port of your keystone
server (e.g. 127.0.0.1:35357).
-Dolph
On Mon, Aug 6, 2012 at 9:15 PM, 王鹏 breakwin...@gmail.com wrote:
Hi,every:
That is my first install swift,I according to
objectstorage-adminguide-essex.pdf from www.openstack.org.
when I
I have the majority of the latest v3 draft implemented on both the client
and server, but it's neither complete nor polished... yet.
My goal is to have a solid implementation (perhaps in a branch?) for
everyone to poke at in plenty of time for the summit :)
-Dolph
On Mon, Aug 20, 2012 at 4:33
While there's no implementation of this in keystone today, I'm sure you
could write your own LDAP driver in keystone, heavily leveraging the
existing LDAP driver.
-Dolph
On Mon, Aug 20, 2012 at 4:19 PM, Ryan Lane rl...@wikimedia.org wrote:
On Mon, Aug 20, 2012 at 1:52 PM, pat p...@xvalheru.org
What exactly happens when you try to start it directly?
cd /opt/stack/keystone /opt/stack/keystone/bin/keystone-all
--config-file /etc/keystone/keystone.conf --log-config
/etc/ke'stone/logging.conf -d --debug
What happens when you curl http://localhost:5000/v2.0/ on that machine? And
with
That potentially a different issue; likely a pypi mirror not responding?
You can download/install prettytable directly if you need to:
http://pypi.python.org/pypi/PrettyTable/
-Dolph
On Thu, Aug 23, 2012 at 3:39 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
Me too experiencing
Keystone doesn't return 301's (ever). However, your 301 response headers
show:
Server: BlueCoat-Security-Appliance
I'm guessing that wasn't installed by devstack :)
-Dolph
On Fri, Aug 24, 2012 at 3:03 AM, Lu, Lianhao lianhao...@intel.com wrote:
Hi gang,
I used the devstack to install a
1 - 100 of 194 matches
Mail list logo
