This is our current service-list:
heat-admin@bootstack-vm-4:~$ nova service-list
+------------------+--------------------------------------------------+----------+---------+-------+----------------------------+
| Binary | Host | Zone | Status | State | Updated_at |
+------------------+--------------------------------------------------+----------+---------+-------+----------------------------+
| nova-conductor | bootstack-vm-4.notcompute.novalocal | internal | enabled | up | 2013-05-26T23:42:55.000000 |
| nova-cert | bootstack-vm-4.notcompute.novalocal | internal | enabled | up | 2013-05-26T23:42:58.000000 |
| nova-scheduler | bootstack-vm-4.notcompute.novalocal | internal | enabled | up | 2013-05-26T23:42:57.000000 |
| nova-consoleauth | bootstack-vm-4.notcompute.novalocal | internal | enabled | up | 2013-05-26T23:43:00.000000 |
| nova-compute | bootstack-vm-4.notcompute.novalocal | nova | enabled | down | 2013-05-23T08:33:59.000000 |
| nova-compute | compute-test | nova | enabled | down | 2013-05-24T08:54:40.000000 |
| nova-compute | compute-test2 | nova | enabled | up | 2013-05-26T23:42:54.000000 |
| nova-compute | compute-group | nova | enabled | down | 2013-05-24T08:55:04.000000 |
| nova-compute | compute-group.novacompute0.novacompute.novalocal | nova | enabled | down | 2013-05-24T09:07:51.000000 |
| nova-compute | compute-test0 | nova | enabled | up | 2013-05-26T23:43:01.000000 |
| nova-compute | compute-test1 | nova | enabled | up | 2013-05-26T23:42:55.000000 |
| nova-compute | compute-test3 | nova | enabled | up | 2013-05-26T23:42:53.000000 |
| nova-compute | compute-test4 | nova | enabled | up | 2013-05-26T23:43:00.000000 |
| nova-compute | compute-test5 | nova | enabled | up | 2013-05-26T23:42:53.000000 |
note that the hosts in state down will never be coming back - we've rotated them out. There doesn't seem to be a way to gc this except by fiddling by hand. If there is, perhaps this is just a doc bug.
Related blueprint with a patch: https:/ /blueprints. launchpad. net/nova/ +spec/remove- nova-compute