69fc891e27
Currently resolv.conf on the master node sets the master node itself as the only DNS server. The requests are served by dnsmasq running in the cobbler container. Thus name resolution does not work when cobbler is not running (not ready yet, the container is being updated, docker is being updated, etc). This breaks updates and other actions (such as building bootstrap images) which need a working DNS. To solve the issue add the upstream DNS servers to resolv.conf. blueprint fuel-bootstrap-on-ubuntu Change-Id: I16261d2eaf37c3f59f28a494d38ee72c6d3aa2d2 |
||
|---|---|---|
| debian | ||
| deployment/puppet | ||
| files | ||
| specs | ||
| tests | ||
| utils | ||
| .gitignore | ||
| .gitreview | ||
| CHANGELOG | ||
| LICENSE | ||
| 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.