20b5983868
This change adds two new custom_setup_class options to the mysql class. With this change, we now support 'percona' and 'percona_packages' to be passed to the mysql::server class that will cause percona to be used. This change adds the use_percona and use_percona_packages params to the existing galera class. The 'use_percona' option will cause the configuration to use the Linux distrubution classes for the Percona installation. This only works with Ubuntu. By setting both 'use_percona' and 'use_percona_packages' to true, the puppet configuration will use the Percona provided packages for installation. This assumes that the Percona packages are available to the system. Additionally tests have been added to the galera class to ensure that expected resources are configured for both the regular packages and the percona packages. By default, the existing galera configuration remains the same and assumes the use of existing packages. Partial blueprint: detach-components-from-controllers DocImpact Change-Id: I972698a8b2dae4caca6101db6d48bab405e40eae Co-Authored-By: Nikita Koshikov <nkoshikov@mirantis.com> Co-Authored-By: Alex Schultz <aschultz@mirantis.com> |
||
|---|---|---|
| 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.