linux/meta-cloud-services.git/meta-openstack/recipes-extended, branch juno

libvirt: update bbappend to meta-virtualization latest

2014-10-14T14:36:00+00:00

Signed-off-by: Bruce Ashfield

add monitoring packagegroup into openstack build

2014-09-30T20:29:12+00:00

Include monitoring packagegroups into various openstack packagegroups. Monitoring feature can be turned on by including the following in local.conf OPENSTACK_EXTRA_FEATURES += "monitoring" There are various different system monitoring recipes (e.g. Nagios or Monasca) provide packagegroup-monitoring-xxxxx. To choose what system monitoring to use set the following in local.conf PREFERRED_PROVIDER_virtual/monitoring = "packagegroup-nagios-monitoring" Signed-off-by: Vu Tran

add generic monitor framework

2014-09-30T18:30:18+00:00

Instead of having a central file or group of files to describe what data resources should be monitored. The content of these files will depend on what core system monitoring is used ((e.g. Nagios or Monasca). It's desirable to have each recipe describes what it wants be monitored in generic way such that various system monitors can understand and convert these into their format. If a recipe wishes to register itself to system monitor, it inherits monitor bbclass and use MONITOR_SERVICE_PACKAGES and MONITOR_SERVICE_ to indicate what processes should should be monitored. Also MONITOR_CHECKS_ variale can be used to pass list of scripts which will be run on target and if any of these scripts fail then will report. Eventually monitor.bbclass will be expanded to allow recipe to describe more complicated information passed down to system monitor (e.g. Nagios or Monasca) Signed-off-by: Vu Tran Signed-off-by: Bruce Ashfield

housekeeping: Add a non-numeric PR prefix to allow PRINC in bbappends

2014-09-29T04:47:44+00:00

Although the use of PRINC is deprecated in later versions of Yocto it may still be used and if you are using this layer with older Yocto it is recommended for use in bbappends. It is therefore expected to work. PRINC expects a non-numeric prefix followed by a numeric value, as can be seen in base.bbclass pr_prefix = re.search("\D+",pr) prval = re.search("\d+",pr) if pr_prefix is None or prval is None: bb.error("Unable to analyse format of PR variable: %s" % pr) Failing to stick to this convention yields a parsing error when you attempt to use PRINC: ERROR: Unable to analyse format of PR variable Adding the non-numeric prefix allows PRINC use in bbappends to function correctly. Signed-off-by: Mark Asselstine

openstack: restart daemons exposed by the following services in openstack

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

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

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

update to use new packagegroup-ceph

2014-09-24T13:26:05+00:00

"task-ceph" package group is renamed to "packagegroup-ceph" so update any file in meta-cloud-services layer that uses "task-ceph" Signed-off-by: Vu Tran Signed-off-by: Bruce Ashfield

keystone: Change packages configuration to use apache keystone.

2014-09-22T15:46:43+00:00

This commit changes all required configurations to use keystone running on apache. The following packages configurations were modified for keystone running on apache: python-neutron, python-nova, tempest, python-swift, python-rally, python-heat, python-glance, python-cinder, python-ceilmoeter, python-horizon. Signed-off-by: Liam R. Howlett

troveclient: Split troveclient into separate packages.

2014-09-17T04:48:40+00:00

Update troveclient to newer git commit to support postgresql and split the package into a meta-package, the python package, bin package, and test package. Add the meta-package to the compute image & trove RDEPENDS. Signed-off-by: Liam R. Howlett

trove: Add trove recipe and add the package to controller.

2014-09-17T04:48:40+00:00

Create the OpenStack Database as a service recipe and add it to the controller image. The recipe includes the init script and initial setup to use postgres. Signed-off-by: Liam R. Howlett