The output of euca-describe-instances via awsome is missing a lot of detail

[Michael Still]

Trying out awsome, I notice that euca-describe-instances is a lot less useful via awsome when using canonistack.

Without awsome (the grep is because I am an admin and would get everything):

 $ euca-describe-instances | grep mikal
 RESERVATION r-g8tykb1c mikal_project default
 INSTANCE i-00001b28 ami-00000049 server-6952 server-6952 running mikal (mikal_project, edasich) 0 m1.tiny 2012-03-20T05:30:27Z nova

With awsome:
 RESERVATION 3faef505-8968-454d-af5e-4abd3eae80c3 None
 INSTANCE 3faef505-8968-454d-af5e-4abd3eae80c3 running openstack

I think its cool that you're using uuids for the instance and reservation ids. At the very least I think this output needs to include the AMI id (uuid would be fine if that's internally consistent with the output of euca-describe-images), project, IP defailts, instance size and compute node.

I haven't spent a lot of time using AWS, but it seems that sample euca-describe-instances output I see for Amazon instances shows a lot more detail too, so I think people used to AWS would have similar concerns.

[Martin Packman (gz)]

Yup, it's pretty ugly against canonistack right now, it was better before the upgrade changed a bunch of things. Most parts will be trivial to fix, where I've been unsure is which bits are specific to canonistack configuration quirks.

[Martin Packman (gz)]

Added some tests and made a few small improvements to the mapping last week, so the output now looks like:

RESERVATION eedf54f1-9e53-4e49-962a-5cf3a878ffc7 gz_project
INSTANCE eedf54f1-9e53-4e49-962a-5cf3a878ffc7 fc6133d8-ee9b-4485-866f-a20819b33f24 10.55.60.213 running 2012-04-02T09:21:26Z nova

There are a few obvious things left to solve. UUIDs really aren't pretty with the tool's output formatting, but we're a bit stuck on that. Mapping the flavor id back to a name means an extra backend request but is pretty simple. Getting the security groups is also another backend request per instance.