- Switched default linter to cookstyle
- Renamed rake tasks to better conform with Chef conventions
- Normalized template banner
Change-Id: I76bdb4149965ab7b23709762559bd6c71753cc8b
Now depends on mysql ~> 5.3 and database ~> 2.2.
The mysql-server recipe now uses the mysql cookbook
wrapper method.
Blueprint: move-to-mysql-v5
Change-Id: I74111ead1555c46d32c3e096c380fec27b3ef593
*_python_packages attributes are being moved to -common in order to
remove the duplication from all the cookbooks which are using them
Change-Id: I848690a84f53b3c6c5e54f4b19f56d5494890f1b
Implements: blueprint move-python-db-client-attrs-to-common
This will allow the ibm_powerkvm platform to be recognized and will
simplify uses of multiple platforms from the same family.
Change-Id: Iebf2aad9f3b4649fb5c27d2fc93ee60c67e42737
Partially-Implements: blueprint add-ibm-powerkvm-enablement
Implements: blueprint platform-family
The problem that this change addresses is that the address_for method
will not work correctly if there are multiple IP address associated
with the specified interface.
The approach to solving this problem and moving towards the overall
goal of having one place where service networking information is
stored is to convert address_for calls into endpoints, and add a
address() method to the endpoints interface for IP address resolution.
The address() method has the following behavior: if the
bind_interface of an endpoint is set, then the IP is looked up on
the interface. Otherwise, the IP specified in the host attribute is
returned. This allows the caller to choose either method of
determining what IP a service will be bound to.
This initial change switches both the openstack-ops-database and
openstack-ops-messaging cookbooks over to use endpoints instead of
address_for. The other cookbooks will be switched over time.
blueprint increase-ip-binding-flexibility
Change-Id: I2d1c40ec79a2533be150c5b4ea6e1f396c500e9d
- Update rubocop config to handle entire repo in one file
- Update Strainerfile to run rubocop only once
- Update attributes to comply with rubocop
Change-Id: I299c2775a5a124b0af74f2e3d844cbd91f93380f
Addresses: blueprint rubocop-for-ops-database
The openstack-common library provides the new attributes, this
cookbook needs to integrate against those.
Change-Id: I99f9577b6d96693463d21dced9633bab61469378
This cookbook should handle the creation of tables, users, grants
for use with OpenStack. Once this is merged, will remove the
db recipe from each cookbook.
Change-Id: I309c4d0fedc8c78f779dbd17b265bfa7e78ffd89
Brought in openstack-common as a dep. Updated the tests to
better match what the recipes are doing (added tests where
missing). Updated attributes to match the format of our other
cookbooks. This is mostly some cleanups, to prepare for features.
Since this cookbook is not in use, made a larger commit than
would have if adding functionality to a released cookbook. Also,
upgraded to new Berkshelf which handles locking to cookbooks properly.
Change-Id: I8e4123d30012a9890ce3029184e1396d2083a6f1
This creates basic testing of the recipes as well as remove unused code such as
the fedora support and the use of passing attributes to openstack::packages.
Change-Id: Iece19811151fbdfd067e12d3b3163cfb78174e49
Just bring in Matt's original work on the ops-database
cookbook.
Corrects what I think was a typo for the database service
role name attribute from openstack::role::database to
openstack::database::server_role
Brings in Berksfile and Gemfile and stubbed specs to pass
gates. Also sets version to 7.0.0 to match semantic versions
of openstack project cookbooks.
Change-Id: Idc02435ff7d3ff4b8a04c2bfc5abbb1e3091cb68
Ghanshyam Mann