Interpretation of acronyms in Fuel commands

Interpretation of acronyms in Fuel commandsΒΆ


The Fuel command-line interface has been updated. Although old fuel commands are still available, we recommend that you use the new fuel2 commands instead. See the Fuel CLI commands comparison matrix.

Fuel CLI commands contain a number of acronyms. For a better understanding of those, see the example command output below.


Nailgun populates the database with hardware configuration information about all the managed nodes it discovers as well as the configuration and status of each node.

The fuel node list command is used on the Fuel Master node to list out the current information about the nodes for the environment:

[root@fuel ~]# fuel nodes

id | status   | name             | cluster | ip        | mac               | ...
---|----------|------------------|---------|-----------|-------------------| ...
4  | ready    | Untitled (b0:77) | 1       | | 56:40:fa:cc:cf:45 | ...
1  | ready    | Untitled (ca:9a) | 1       | | ca:03:e6:b1:13:46 | ...
3  | ready    | Untitled (0e:64) | 2       | | 26:1f:eb:91:d8:49 | ...
2  | ready    | Untitled (c1:ef) | 2       | | 22:2a:45:36:5d:42 | ...
5  | discover | Untitled (e1:c4) | None    | | 08:00:27:1a:e1:c4 | ...

id | status   | name             |...| roles      | pending_roles | online | group_id
4  | ready    | Untitled (b0:77) |...| compute    |               | True   | 1
1  | ready    | Untitled (ca:9a) |...| controller |               | True   | 1
3  | ready    | Untitled (0e:64) |...| compute    |               | True   | 2
2  | ready    | Untitled (c1:ef) |...| controller |               | True   | 2
5  | discover | Untitled (e1:c4) |...|            |               | True   | None

The meaning of these fields is:


The node identifier, assigned incrementally when the node is first discovered (when the Fuel agent sends its first request to the Fuel Master node).

This ID is the Primary Key for this record in the database; it is unique and is never reassigned; when you delete a node from the environment, that node’s ID is deleted; the next node added to the environment is assigned a new ID that is higher than the highest-numbered ID in the database.


Current state of the node:

ready:Node is deployed and provisioned, ready to use
discover:Node is not deployed and not provisioned
provisioning:Node is in the process of being provisioned (operating system is being installed)
provisioned:Node is provisioned but not deployed
deploying:Node is being deployed (OpenStack is being installed and configured)
error:Deployment/provisiong of the node has failed

Name of the node as displayed on the screen when you assign roles. By default, this is “Untitled” with the final digits of the MAC address used by the Admin interface for that node. You can double-click on that title to change the name.


ID of the environment to which the node is assigned.


IP address of the admin interface, which is the IP address for the default route.


MAC address of the admin interface, determined the same way as the IP address.


A role of a node; populated only after deployment.

The following two columns appear at the right end of this display; they are not shown here:


Before deployment, lists the roles that have been assigned to this node. When deployment is complete, the contents of this field are moved to the roles column.

This field can also contain the primary value to indicate that this node is the primary controller node. The primary value is persisted in the database through the use of the has_primary field in the openstack.yaml file.


Status of the node:

False:Node is offline.
True:Node is available via the Fuel admin network.

The group node identifier. When you assign roles to your target nodes, Fuel tries to automatically determine the node’s group based on the DHCP address.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.