DescribeInstances reply is not ordered as in EC2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Russell Bryant |
Bug Description
This is probably not documented api behavior in EC2, but against ec2, 'euca-describe-
Against openstack:
$ euca-describe-
RESERVATION r-hm0g1p5n smoser_project default
INSTANCE i-000000c8 ami-00000017 10.55.60.8 10.55.60.8 running mykey 0m1.large 2011-08-
RESERVATION r-d0n8ifhf smoser_project default
INSTANCE i-000000ca ami-00000017 10.55.60.12 10.55.60.12 running mykey 0m1.small 2011-08-
RESERVATION r-txxl8iri smoser_project default
INSTANCE i-000000c6 ami-00000011 91.189.93.89 10.55.60.6 running mykey 0m1.large 2011-08-
Against EC2:
$ euca-describe-
RESERVATION r-e746d088 950047163771 default
INSTANCE i-7d75081c ami-fdc50494 stopped brickies0 m1.large 2011-08-
RESERVATION r-f1660a9e 950047163771 default
INSTANCE i-b35300d2 ami-7134f518 terminated brickies 0 t1.micro 2011-08-
RESERVATION r-0d422e62 950047163771 default
INSTANCE i-6b97c40a ami-7b35f412 ec2-184-
smoser@brickies:~$ euca-terminate-
INSTANCE i-6b97c40a
Note, above that in EC2, the most recently launched instance is shown last.
Changed in nova: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
summary: |
- DescribeInstances reply is not ordered correctly + DescribeInstances reply is not ordered as in EC2 |
Changed in nova: | |
assignee: | nobody → Russell Bryant (russellb) |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
this could easily be done with a sort.