openstack/fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
8,411 Commits 4 Branches 3 Tags 267 MiB
3070f3fa3c
Go to file
Sergii Golovatiuk 3070f3fa3c Increase settings for dnsmasq and sysctl 
* Make a new variable dhcp_lease_max. It increases the number of
  available leases from 1000 to 1800. It allows to provision nodes on
  scale, when Debian Installer or Anaconda looses IP in the middle of
  install.
* Make a new variable lease_time. It increases the default lease size
  to 120m, up from the default 60m.
* Add cache-size to dnsmasq template. dnsmasq will keep more entries in
  case.
* Increased neighbour table on master node to keep more ARP requests
  that come in parallel once deployment is started. This change also
  removes unneed broadcast traffic. New values are:
  net.ipv4.neigh.default.gc_thresh1 = 256
  net.ipv4.neigh.default.gc_thresh2 = 1024
  net.ipv4.neigh.default.gc_thresh3 = 2048
* Fix linting

Related-Bug: #1376680
Related-Bug: #1379917
Related-Bug: #1381997
blueprint 100-nodes-support
DocImpact

Change-Id: I4da8070143e401f7a9246e72eda35e601b8c6386
2014-10-20 11:59:46 +02:00
deployment/puppet Increase settings for dnsmasq and sysctl 2014-10-20 11:59:46 +02:00
docs merge with fuel-777 (22053e4e5f) branch 2013-07-30 20:35:42 +04:00
utils Run syntax check for OCF scripts 2014-10-09 12:30:54 +03:00
.gitignore Make rdoc script 2013-09-16 15:59:43 +04:00
.gitreview Setup git-review 2013-12-11 14:31:13 +04:00
CHANGELOG Edit Changelog 2013-05-23 13:38:03 +03:00
LICENSE LICENCE added 2014-06-05 20:00:54 +00:00
README.md RabbitMQ FAQ notes prettified 2013-05-08 23:19:41 +04:00

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.