d3b4818b7b
Tie ring_*_device resource to ring_devices resource by setting autorequire, thus making ring_devices resource run after ring_*_device and ensure it is before rebalance anchor How to test: 1) install swift binaries 2) run: rm /var/lib/puppet/state/graphs/* && puppet apply --graph -vd --modulepath /home/vvk/git/fuel/deployment/puppet/ -e 'anchor{"rebalance_begin":} Ring_devices<||> -> Anchor['rebalance_begin'] ring_devices{'all': storages=> [{"storage_address"=>"10.10.10.10"}] }' 3) read /var/lib/puppet/state/graphs/relationships.dot The purpose is to set all ring_*_device before Anchor['rebalance_begin'] Change-Id: If9e724342eeeb8399093103a875719b82a429bc5 Closes-Bug: #1305826 |
||
---|---|---|
deployment/puppet | ||
docs | ||
utils | ||
.gitignore | ||
.gitreview | ||
CHANGELOG | ||
README.md |
README.md
Fuel is the Ultimate Do-it-Yourself Kit for OpenStack
Purpose built to assimilate the hard-won experience of our services team, it contains the tooling, information, and support you need to accelerate time to production with OpenStack cloud.
OpenStack is a very versatile and flexible cloud management platform. By exposing its portfolio of cloud infrastructure services – compute, storage, networking and other core resources — through ReST APIs, it enables a wide range of control over these services, both from the perspective of an integrated Infrastructure as a Service (IaaS) controlled by applications, as well as automated manipulation of the infrastructure itself.
This architectural flexibility doesn’t set itself up magically; it asks you, the user and cloud administrator, to organize and manage a large array of configuration options. Consequently, getting the most out of your OpenStack cloud over time – in terms of flexibility, scalability, and manageability – requires a thoughtful combination of automation and configuration choices.
Mirantis Fuel for OpenStack was created to solve exactly this problem.