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

cloud-init: fix 64bit libraries

2015-04-23T15:30:08+00:00

We need to ensure that the cloud-init to install in the correct location (/usr/lib64) Signed-off-by: Eddy Raineri Signed-off-by: Bruce Ashfield

cloud-init: update to 0.7.6

2015-04-15T03:39:48+00:00

Signed-off-by: Bruce Ashfield

controller: add package management by default

2015-03-02T16:42:02+00:00

Signed-off-by: Bruce Ashfield

support-libs: fix clean issues

2015-02-24T17:16:11+00:00

With recent changes to oe-core make clean is run during the configuration phase of python packages. For some packages, this causes breakage as 'make clean' is not supported. To keep the build going, we mark them as brokenclean to avoid the issue. Signed-off-by: Bruce Ashfield

QA: fix build and runtime warnings

2015-02-21T05:42:47+00:00

oe-core now warns on detected missing runtime and build time warnings. So we update our recipes to have these missingn deps (largely bash). Signed-off-by: Bruce Ashfield

bbappends: resync to oe-core versions

2015-02-20T20:41:06+00:00

Updating the bbappends to match the oe-core versions ~commit 530565c6cb77319f4cc49edeea6fec6be997415d Signed-off-by: Bruce Ashfield

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