Fuel is an open source deployment and management tool for OpenStack. Developed as an OpenStack community effort, it provides an intuitive, GUI-driven experience for deployment and management of OpenStack, related community projects and plug-ins.
Fuel brings consumer-grade simplicity to streamline and accelerate the otherwise time-consuming, often complex, and error-prone process of deploying, testing and maintaining various configuration flavors of OpenStack at scale. Unlike other platform-specific deployment or management utilities, Fuel is an upstream OpenStack project that focuses on automating the deployment and testing of OpenStack and a range of third-party options, so it’s not compromised by hard bundling or vendor lock-in.Look at Fuel Architecture
28 May 2017 18:33 UTC
9 Mar 2017
Fuel CLI tool is a powerful tool that allows you to:
Fuel CLI has the following usage pattern:
fuel [global optional args]
fuel --env-id=1 node set --node-id=1,4,5 --role=compute
where --env-id=1 is a global optional argument pointing to the specific environment, node - is a namespace for all node control functions, set is an action that assigns specific nodes to some environments in certain roles.
The following Fuel documentation is published on the OpenStack documentation page:
Additional Fuel documentation is available on the Mirantis web-site and includes:
This deployment emulates the provisioning process, providing you with an opportunity to get an insight into the web UI without installing anything on your hardware.
Each version of the installer undergoes hardware compatibility validation. Fuel is battle-tested on platforms like Cisco UCS, Dell PowerEdge, HP Proliant, Lenovo ThinkServer, QCT QuantaPlex, Supermicro SuperServer, and others. For the detailed information on models and their hardware modifications, refer to the Hardware Compatibility List.