Comment 10 for bug 958135

I have an update as I now have a working set up:

First problem:
my /etc/nova/nova.conf line was wrong initially

I had
    --keystone_ec2_url=http://172.29.0.1:5000/v2.0/tokens
instead of
    --keystone_ec2_url=http://172.29.0.1:5000/v2.0/ec2tokens

When I corrected this, this moved from the metadata_ref stack trace [#0], to the TypeError: 'NoneType' object has no attribute '__getitem__' (#1) stack trace. I assumed, same/similar bugs causing the issue.

At this point chmouel and I went on to debug the setup.
We found that I was using a named of my tenant, instead of the ID in my EC2 credentials. (#7)

With this in place, we still were getting the stack trace seen in #1.

On looking at this further - I then took the complete keystone.conf from source, including the local template catalog file and THIS WORKED.

Not to be deterred from using a MySQL backend for my catalog and I got this working too. Then looking through the diffs in the keystone.conf that is shipped with ubuntu's packages and the one you can find in Git shows these interesting lines

< ubuntu confs
> Git confs, which work

< driver = keystone.token.backends.sql.Token
---
> driver = keystone.token.backends.kvs.Token
52c55
< driver = keystone.contrib.ec2.backends.sql.Ec2
---
> driver = keystone.contrib.ec2.backends.kvs.Ec2