linux/meta-cloud-services.git/meta-openstack/classes/openstackchef_inc.bbclass, branch morty

openstackchef_inc.bbclass: Update python synthax for except

2016-09-19T20:04:22+00:00

The synthax used is deprecated and causes errors. Signed-off-by: Adrian Dudau Signed-off-by: Bruce Ashfield

openstackchef: add missing parameter to getVar

2016-03-21T14:19:41+00:00

Builds are failing with: File: 'openstackchef_inc.bbclass', lineno: 624, function: deploychef_add_file_to_FILES_PN 0620: pkg_files = "FILES_%s" % pkg 0621: ldata.setVar("OVERRIDES", "%s:%s" % (pkg_files, overrides)) 0622: bb.data.update_data(ldata) 0623: *** 0624: dest_base = d.getVar('CHEF_TEMPLATE_BASE') 0625: pkg_imagedir = d.getVar('CHEF_ROOTFS_BASE', True) 0626: #Add the packages image base directory if it does not already exist 0627: if re.search(pkg_imagedir, files) == None: 0628: #All the directory and all files in it Exception: TypeError: getVar() takes at least 3 arguments (2 given) Add the required parameter to fix the build. Chef is planned to be removed from this layer in the near future, so this change is not tested. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

chef: make deploychef dependencies a distro feature

2015-02-20T03:50:09+00:00

Signed-off-by: Bruce Ashfield

openstackchef: decentralized openstack-chef class implementation

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

This class provides a framework for recipes(packages) to register their configuration files with the deploychef package. This class works together with the deploychef package. This implementation makes it possible for the deploychef package, with the help of chef-solo, to recreate registered configuration files at run-time. Only services that inherit this class and register their configuration files are re-configurable at run-time; and by configurable, we mean to make chefsolo templates out of their configuration files and to be aware of the list of daemons that need to be killed/started at run-time. Therefore, openstackchef class requires the recipes/classes inheriting it to advertise their configuration files, list of start/stop daemons and finally a special callback function when necessary. In order to avoid duplication of common placeholders and substitution across the various recipes inheriting this class, we keep a dictionary of common placeholders and substitutions, but rely on the recipes to define the values these placeholders take at run-time. See the description at the top of the class files (openstackchef.bbclass and openstackchef_inc.bbclass ) for more details. This class makes chef-solo template files out of the configuration files exposed to it by the recipes. The resulting templates are stored at /opt/deploychef/cookbooks/openstack/templates/default. on the resulting rootfs. It also creates a file containing a set of chef-solo default template values known as attributes in chef-solo world. The default values are provided by the recipes and classes inheriting this class. The chefsolo attributes file is stored at /opt/deploychef/cookbooks/openstack/attributes/default.rb at the end of rootfs creation process. At run-time, the deploychef package whose package files are stored at '/opt/deploychef', makes a call to chef-solo. Chef-solo in turn uses the attributes and templates files to overwrite the configuration files for services like neutron, nova, swift, etc.. that registered configuration files with openstackchef class at build time. See accompanying documentation for further explanation. Signed-off-by: Mustapha Lansana