summaryrefslogtreecommitdiffstats
path: root/meta-openstack/recipes-devtools/python/python-keystone_git.bb
diff options
context:
space:
mode:
authorMustapha Lansana <Mustapha.Lansana@windriver.com>2014-05-27 22:02:55 -0400
committerBruce Ashfield <bruce.ashfield@windriver.com>2014-09-26 09:09:21 -0400
commit98e1afbc185a7f87427860f4273a7285e5b6407e (patch)
tree13558f56af0e27bcebd9202ed68e3c89efb317fa /meta-openstack/recipes-devtools/python/python-keystone_git.bb
parentea4560f65862a7c94d15cfe6006f8059ab62ea74 (diff)
downloadmeta-cloud-services-98e1afbc185a7f87427860f4273a7285e5b6407e.tar.gz
deploychef: makes chef-solo templates from openstack conf files
The current openstack build bakes a number of variables into openstack services' configuration files at build-time. This makes it impossible to deploy an openstack image built for one run-time environment into a different run-time environment. The deploychef package uses chef-solo to enable the re-use of an openstack image in different run-time environments. The attached patch set is deploychef package recipe and init script files. The script deploychef.init gives us the ability to make a copy of the postinstall script before they are tainted. This enables us to create chef-solo templates out of the untainted postinstall scripts. The template files are then used to recreate the postinstall script whenever the stack needs to be reconfigured at run-time. Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>
Diffstat (limited to 'meta-openstack/recipes-devtools/python/python-keystone_git.bb')
0 files changed, 0 insertions, 0 deletions