This cookbook provides a reference example of database configuration for the OpenStack deployment provided by Chef for OpenStack. It currently supports MySQL and PostgreSQL.
Chef 11 with Ruby 1.9.x required.
- Ubuntu-12.04
- SLES 11 SP3
- RHEL/CentOS 6.5
The following cookbooks are dependencies:
- database
- openstack-common
- mysql
- postgresql
The usage of this cookbook is optional, you may choose to set up your own databases without using this cookbook. If you choose to do so, you will need to do the following:
- create the schema specified by the
openstack-dbrecipe. - create and upload encrypted data bags into your chef environment, as
specified by
#get_passwordin theopenstack-dbrecipe.
None
None
- database client configuration, selected by attributes
- database server configuration, selected by attributes
- calls mysql::ruby and mysql::client and installs the mysql client python packages
- configures the mysql server for OpenStack
- calls postgresql::ruby and postgresql::client and installs the postgresql client python packages
- configures the PostgreSQL server for OpenStack
- creates necessary tables, users, and grants for OpenStack
The following attributes are defined in attributes/database.rb of the common cookbook, but are documented here due to their relevance:
openstack["endpoints"]["db"]["host"]- The IP address to bind the database service toopenstack["endpoints"]["db"]["scheme"]- Unused at this timeopenstack["endpoints"]["db"]["port"]- The port to bind the database service toopenstack["endpoints"]["db"]["path"]- Unused at this timeopenstack["endpoints"]["db"]["bind_interface"]- The interface name to bind the database service to
If the value of the "bind_interface" attribute is non-nil, then the database service will be bound to the first IP address on that interface. If the value of the "bind_interface" attribute is nil, then the database service will be bound to the IP address specified in the host attribute.
Please refer to the TESTING.md for instructions for testing the cookbook.
Berks will resolve version requirements and dependencies on first run and
store these in Berksfile.lock. If new cookbooks become available you can run
berks update to update the references in Berksfile.lock. Berksfile.lock will
be included in stable branches to provide a known good set of dependencies.
Berksfile.lock will not be included in development branches to encourage
development against the latest cookbooks.
| Author | Justin Shepherd ([email protected]) |
| Author | Jason Cannavale ([email protected]) |
| Author | Ron Pedde ([email protected]) |
| Author | Joseph Breu ([email protected]) |
| Author | William Kelly ([email protected]) |
| Author | Darren Birkett ([email protected]) |
| Author | Evan Callicoat ([email protected]) |
| Author | Matt Thompson ([email protected]) |
| Author | Matt Ray ([email protected]) |
| Author | Sean Gallagher (<[email protected]>) |
| Author | John Dewey ([email protected]) |
| Author | Ionut Artarisi ([email protected]) |
| Copyright | Copyright (c) 2012-2013, Rackspace US, Inc. |
| Copyright | Copyright (c) 2012-2013, Opscode, Inc. |
| Copyright | Copyright (c) 2013, AT&T Services, Inc. |
| Copyright | Copyright (c) 2013-2014, SUSE Linux GmbH |
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.