Caution
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.
You may need to deploy a node with an operating system installed only, that is an empty role, where you can further deploy your own service out of Fuel control.
To deploy a node with an empty role:
Verify available operating systems:
fuel release
Example of system response:
id | name | state | operating_system | version
---|----------------------------|-------------|------------------|-----------
2 | Mitaka on Ubuntu 14.04 | available | Ubuntu | mitaka-9.0
3 | Mitaka on Ubuntu+UCA 14.04 | available | Ubuntu | mitaka-9.0
1 | Mitaka on CentOS 6.5 | unavailable | CentOS | mitaka-9.0
Note down the operating system id
you need to install on the node.
Verify available nodes:
fuel node
Example of system response:
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|----------|------------------|---------|-----------|-------------------|-------|---------------|--------|---------
2 | discover | Untitled (90:9b) | None | 10.20.0.4 | 08:00:27:f5:90:9b | | | True | None
3 | discover | Untitled (53:f1) | None | 10.20.0.5 | 08:00:27:14:53:f1 | | | True | None
1 | discover | Untitled (7c:11) | None | 10.20.0.3 | 08:00:27:72:7c:11 | | | True | None
Create a new environment if you do not have one:
fuel env create --name <ENV_NAME> --release 2
Example of system response:
Environment `<ENV_NAME>` with id=1 was created!
Verify that the environment has been created:
fuel env
Example of system response:
id | status | name | release_id
---|--------|------------|-----------
1 | new | <ENV_NAME> | 2
Note down the id
of the environment.
Verify available roles:
fuel role --release 2
Example of system response:
name
-------------------
compute-vmware
compute
cinder-vmware
virt
base-os
controller
ceph-osd
ironic
cinder
cinder-block-device
mongo
The role that you need is base-os
.
Add one of the discovered nodes to the environment with the base-os
role assigned:
fuel node set --env 1 --node 1 --role base-os
Example of system response:
Nodes [1] with roles ['base-os'] were added to environment 1
Verify the status of the nodes:
fuel node
Example of system response:
id | status | name | cluster | ip | mac | roles | pending_roles | online | group_id
---|----------|------------------|---------|-----------|-------------------|-------|---------------|--------|---------
1 | discover | Untitled (7c:11) | 1 | 10.20.0.3 | 08:00:27:72:7c:11 | | base-os | True | 1
2 | discover | Untitled (90:9b) | None | 10.20.0.4 | 08:00:27:f5:90:9b | | | True | None
3 | discover | Untitled (53:f1) | None | 10.20.0.5 | 08:00:27:14:53:f1 | | | True | None
Your node with an empty role has been added to the environment.
Note
By default, Fuel does not apply network configuration.
To set up network configuration, run the netconfig
puppet manifests
that comes with fuel-library
.
Fuel automatically executes the following tasks on base-os
nodes only:
hiera
globals
logging
See the tasks.yaml configuration file
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.