No server will be scheduled to disabled compute service, thus we
should not count the corresponding compute node information.
It's arguable if we should count for 'down' service, since service
may be marked down because of communication error. If we do want to
exclude the down service, we need passing the information from caller
because the up/down state is not kepts in database, and it means compute
and cell api changes.
Reviewed: https:/ /review. openstack. org/80708 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=8cd2b890710 ba6e53884f43b5d 6ce095672732a4
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8cd2b890710ba6e 53884f43b5d6ce0 95672732a4
Author: Yunhong Jiang <email address hidden>
Date: Thu Mar 13 16:29:26 2014 -0700
Not count disabled compute node for statistics
No server will be scheduled to disabled compute service, thus we
should not count the corresponding compute node information.
It's arguable if we should count for 'down' service, since service
may be marked down because of communication error. If we do want to
exclude the down service, we need passing the information from caller
because the up/down state is not kepts in database, and it means compute
and cell api changes.
Closes-Bug: #1285259
Change-Id: I5e3e71ef30683c 5eb5cc4462f58fa 5f29d7c3f4b