openstack team mailing list archive

[Ziad Sawalha <ziad.sawalha@xxxxxxxxxxxxx>]

Hi Ygsnian -

I'm not sure which version of Keystone your install deployed. One issue we
had is that there were significant changes in the API between D5 (which
was not officially released) and Diablo. However, there were some packages
and deployments that used D5.

We've tried to address this with a middleware that accepts D5 requests and
responds in D5 format (here https://review.openstack.org/#change,2136).

You mention that Keystone is expecting a PUT and not a POST. Actually,
most Keystone calls should be POSTs, so I'm not sure where you got that
information. If you can find out exactly where that disconnect is and what
version of Keystone you are using we'd be happy to help.

Regards,

Ziad




On 12/12/11 10:27 AM, "ygsnian ygsnian" <ygsnian@xxxxxxxxx> wrote:

>Hi openstack list,
>
>Currently, we are enabling dashboard in Openstack (diablo version)
>and meet a lot of mismatch issues.
>We used grid dynamic packed openstack within RHEL6 like this:
>$sudo rpm -i wget
>http://yum.griddynamics.net/yum/diablo-3/openstack/openstack-repo-2011.3-0
>.3.noarch.rpm
>
>The mismatch issues that we met:
>1. Dashboard got the response data from keystone, but the data
>structure mismatched between dashboard and keystone:
>For example, In dashboard, role_id or user_id are actually the role's
>name and the user's name. Then it passes role_id OR user_id to
>keystone. However, keystone expects the role's id AND the user's id to
>perform the task.
>2. Some method mismatches in openstackx and keystone.
>For example, openstackx uses "POST" but keystone accepts only "PUT".
>3. Others...
>So that, in order to enable the Dashboard, we need to debug the code
>for each item in Dashboard for Diablo openstack.
>
>My questions are:
>1. What openstack version and Dashboard version are the dashboard
>developers  working based on?
>2. How future plan to solve this dependence issue between Dashboard
>and other project (nova, keystone and etc.)
>3. If we has some fix in old version, what kind of thing we can do
>best to make it aviable for future release?
>
>Thank you!
>
>_______________________________________________
>Mailing list: https://launchpad.net/~openstack
>Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~openstack
>More help   : https://help.launchpad.net/ListHelp