[meta-virtualization] [m-c-s][PATCH 00/11] fixup danglers

Mark Asselstine mark.asselstine at windriver.com
Wed Aug 5 13:29:41 PDT 2015


The primary goal of this patch series was to address the numerous
dangling bbappends that exist on the the 'master' branch (I suspect
the other branches have danglers too but master is what I have been
building lately and my goal is to get these on to master where they
can then be propagated to any applicable branches).

The first set of patches therefor address the danglers. Through
inspection some of the danglers can be deemed no longer needed and
have been removed. Others appear to still be relevant and thus were
re-attached (using wildcards when possible). I tried to capture
details in the commit logs as I looked at each dangler, for some of
the obvious ones I did do some grouping to avoid multiple repetitive
commits. For most of the re-attached danglers no changes were needed
but again details of any required changes were captured in the
associated commit logs.

The series grew a bit beyond just addressing the danglers as the main
images - openstack-image-compute and openstack-image-controller - were
not build-able. So some of this series introduces changes that were
required to get these images build-able again. Once I had build-able
images I was able to poke around to ensure that my dangler
removal/re-attachments didn't cause any immediate runtime issues. I
was able to do some validation but due to issues with the openstack
dashboard I wasn't able to perform the minimal openstack tests
(spinning up an instance, interacting with the dashboard...).

Obviously I would like to be able to validate with the base usecase
but the series has already grown beyond the initial goal. With the
images previously being unbuild-able I can only assume the issues with
the dashboard etc. were preexisting. I will continue to work on
getting 'master' to a working state but please consider merging this
series so that the changes can be available to anyone else who would
like to work on 'master' but currently can't even build it.

Regards,
Mark


P.S. The "[m-c-s]" in the subject line is obviously for
'meta-cloud-services'. I had to use the abbreviation as git was
truncating things otherwise. Looking at the mailing list it seems I am
the first one to send more than a single patch and thus the first to
run in to the truncation.


More information about the meta-virtualization mailing list