Multiple OpenStack release management - was: OpenStack status
On Thu, May 24, 2012 at 11:27:55AM -0500, Pádraig Brady wrote:
== Diablo on EPEL ==
There was a request from Brookhaven National Lab
as to how to continue using Diablo on RHEL (derivatives)
given that EPEL has now updated to the Essex release.
Older builds can be downloaded from koji, and these
in conjunction with the yum-priorities plugin can be
used to create a diablo repo on top of EPEL.
A [http://pbrady.fedorapeople.org/openstack-diablo-el6/ convenience repository for Diablo
on EPEL] was made available,
containing instructions on how it was created and how to use it.
i'd like for us to consider making a permanent repo, and policy, for
maintaining older openstack releases going forward. the request to
maintain diablo, in addition to essex, necessitates the conversation.
epel isn't designed to hold multiple supported versions of a whole
suite of packages, such as openstack. they have different lifecycle
requirements, as the above proves.
as such, can we:
1) set a policy for how long the sig wants to maintain a given
openstack release?
2) define a permanent repository location for each openstack release?
3) consider likewise for other cloud sig frameworks (openshift, eucalyptus,
cloudstack, opennebula) should the need arise (which i would
anticipate).
it may necessitate creating new top-level projects such as epel was,
for each, with rel-eng and infrastructure resources. scratch-builds
and manual copying only get us so far.
thoughts?
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO