summaryrefslogtreecommitdiffstats
path: root/meta-openstack/recipes-extended/glusterfs/glusterfs_3.4.2.bbappend
Commit message (Collapse)AuthorAgeFilesLines
* chef: remove the use of chefMark Asselstine2017-01-091-6/+0
| | | | | | | | | | | The use of chef was never complete, had isses with updating binary database files and had a cumbersome implementation. Since we are using Ansible in meta-overc we are dropping the use of chef here and will look to being at par with meta-overc by using Ansible if/when we get time to look at runtime configuration in meta-cloud-services. Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* openstack: restart daemons exposed by the following services in openstackMustapha Lansana2014-09-261-0/+6
Openstackchef class provides the framework to reconfigure openstack at run-time. These services are inheriting openstackchef so that script file(s), specified in the respective recipe file, using the variables below are restarted by the decentralized openstackchef class framework when reconfiguring openstack: INITSCRIPT_PACKAGES: The list of init-scripts to start/stop when reconfiguring openstack. INITSCIPT_NAME_x: The name of the init-script mentioned above. INITSCRIPT_PARAMS_X: This parameter defines the run-level and priority for the init-script. However, the only parameter in this variable that is of interest to openstackchef class is the priority of the init-script. Changes to none of the above variables is shown by this patch set, however, it's to point out that openstackchef makes the assumption that these variables are set in the service's recipe file. Failure to set these variables, could lead to the service not working properly after the stack is re-configured. Signed-off-by: Mustapha Lansana <Mustapha.Lansana@windriver.com>