The Bare Metal service provides physical hardware management features.
The Bare Metal service provides physical hardware as opposed to virtual machines. It also provides several reference drivers, which leverage common technologies like PXE and IPMI, to cover a wide range of hardware. The pluggable driver architecture also allows vendor-specific drivers to be added for improved performance or functionality not provided by reference drivers. The Bare Metal service makes physical servers as easy to provision as virtual machines in a cloud, which in turn will open up new avenues for enterprises and service providers.
The Bare Metal service is composed of the following components:
When a user requests to boot an instance, the request is passed to the Compute service via the Compute service API and scheduler. The Compute service hands over this request to the Bare Metal service, where the request passes from the Bare Metal service API, to the conductor which will invoke a driver to successfully provision a physical server for the user.
/var/log/nova/nova-conductor.log contains the following error:
NoValidHost: No valid host was found. There are not enough hosts available.
No valid host was found means that the Compute service
scheduler could not find a bare metal node suitable for booting the new
This means there will be some mismatch between resources that the Compute service expects to find and resources that Bare Metal service advertised to the Compute service.
If you get this message, check the following:
Introspection should have succeeded for you before, or you should have entered the required bare-metal node properties manually. For each node in the ironic node-list command, use:
$ ironic node-show <IRONIC-NODE-UUID>
and make sure that
properties JSON field has valid values for keys
The flavor in the Compute service that you are using does not exceed the bare-metal node properties above for a required number of nodes. Use:
$ openstack flavor show FLAVOR
Make sure that enough nodes are in
available state according to the
ironic node-list command. Nodes in
manageable state usually
mean they have failed introspection.
Make sure nodes you are going to deploy to are not in maintenance mode. Use the ironic node-list command to check. A node automatically going to maintenance mode usually means the incorrect credentials for this node. Check them and then remove maintenance mode:
$ ironic node-set-maintenance <IRONIC-NODE-UUID> off
It takes some time for nodes information to propagate from the Bare Metal service to the Compute service after introspection. Our tooling usually accounts for it, but if you did some steps manually there may be a period of time when nodes are not available to the Compute service yet. Check that the openstack hypervisor stats show command correctly shows total amount of resources in your system.