linux/meta-cloud-services.git/meta-openstack/recipes-support/postgresql/postgresql_9.2.4.bbappend, branch morty

meta-openstack: fix dangling bbappends by adding wildcard

2015-08-06T13:35:50+00:00

Several bbappends were raising 'dangling' warnings since the base recipe version has changed without a similar change being made in this repo. The following are renames that include a wildcard to broaden the versions to which these bbappends will be applied to. This will address the 'dangling' warnings while ensuring the changes made in this repo are properly applied to the associated recipes. For the most part the files remain unchanged, in the case of postgresql the 'brokensep' has been removed as there exists no more S != B issues in the base recipe. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openstack: add support for openstackchef class to services

2014-09-26T13:09:22+00:00

Openstackchef enables us to recreate configuration files for services in an openstack installation. It does this by creating template file(s) out of configuration file(s) exposed to the class by services. The following services are inheriting the openstack class and then exposing a set of configuration files to the class. These services expose their configuration files to openstackchef by assigning them to the variable CHEF_SERVICES_CONF_FILES. The files are assumend to have been installed in the image directory under the service's WORKDIR. At build-time, openstackchef makes chef-solo templates out of the registered files. And at run-time, the deploychef package makes a call to chef-solo, which in-turn use the template files to recreate the registered configuration files. For legacy reasons, the string OPENSTACKCHEF_ENABLED is defined in openstackchef class, but it can be overwritten in a .bb, .class, .bbappend or local.conf file to an empty string when openstackchef support is not desired. This enables all of these services to be built without openstackchef support. In addition, it prevents the recipes from substituting the placeholders in their configuration files when inheriting openstackchef. Signed-off-by: Mustapha Lansana

housekeeping: remove PRINC from recipes

2014-08-29T14:20:18+00:00

Removing PRINC from recipes to silence the bitbake warning about it being a depreciated variable. Signed-off-by: Bruce Ashfield

postgres: fix xml configuration error

2014-07-16T18:14:00+00:00

Not only must postgres depend on libxml for xml support, we need to point at the sysroot/staging area for the header files to be found. Signed-off-by: Bruce Ashfield

autotools: B != S build fixes

2014-05-21T17:22:18+00:00

Since oe-core introduced the autotools separated build and source directory changes, some package builds broke. With this change, we can build against the latest oe-core master. It should be noted that this masks the build issues, and the bbappends should be removed as dependency layers update or "real" fixes are generated. Signed-off-by: Bruce Ashfield

cleanup: leave source config files pristine

2014-04-24T03:36:03+00:00

Editing the files in ${WORKDIR} using sed or similar tools as part of do_install means they can only be edited once. Supplying a modified CONTROLLER_IP in local.conf and building the image again will not result in the CONTROLLER_IP being properly updated since the substitution placeholders will no longer exist. We therefore simply swap the other of things, installing the configuration files first, then editing them to swap the placeholders. This means we can run the do_install again and again and get the results we expect. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

OpenStack: Fix postgresql file permissions

2014-03-15T04:42:00+00:00

- make database directory to be configurable, defaulting to /var/lib/postgres/data - modify init scripts to create database's data directory if it doesn't exist Signed-off-by: Amy Fong Signed-off-by: Bruce Ashfield

postgresql-init: Fix logic inversion

2013-12-09T15:21:20+00:00

The logic was flipped in the wrong place. This makes things right and fixes up the possibility that the symlink already exists. Signed-off-by: Jason Wessel

init: remove remaining createdb commands to separate init packages

2013-11-25T21:17:20+00:00

After moving all database creation initialization packages, we also remove it from the RDEPENDS of the various control node recipes. This allows images to select database initialization or skip it. Signed-off-by: Bruce Ashfield

initscripts: split into -setup and init packages

2013-11-25T20:25:38+00:00

Many OpenStack modules require a first boot action to setup up users, databases, bridges, etc. These same packages install initscripts to start daemons and servers. The 1st boot package post install actions immediately exit to indicate that the action cannot be performed in the cross environment and instead should be done on first boot. The update-rc.d post install actions are intended to be run in the cross environment to symlink scripts into the proper runlevels. The early exit from the db setup routines, means that the rc files are not linked in host cross. If the rootfs doesn't contain update-rc.d, they also will not be set up on first boot. The end result is a system that does not start all of its required services on boot. To fix this, we split out db and other first boot setup tasks into dedicated (but empty) -setup packages. These run on first boot, while update-rc.d is left to create the proper symlinks. Signed-off-by: Bruce Ashfield