50d402821b
Before this change, on the first start of the nova-compute service on any host, this method is logging the "No compute node record for host" error which is confusing for people debugging issues. For example, if the compute service starts up before the Placement service is running, the compute is checking in and failing to connect to the placement endpoint which might take the compute node out of consideration for scheduling. When debugging that kind of issue, people can get hung up on this error message which is actually an expected case on the first start of nova-compute on a new host. This change simply plumbs through a boolean to tell it if we're starting up or not. This doesn't tell us if it's the first time we're starting this service or a restart, but the thinking is, if it's a restart we don't get the NotFound error and if we do, then we do want the error level message. Change-Id: Id7a05b579ead6ac5445ca5b1eeab6d223d545a6c
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
To learn how to use Nova's API, consult the documentation available online at:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
http://docs.openstack.org/developer/nova/feature_classification.html
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at: