5:59 p.m.
Is there any documentation which describes the packaging lifecycles for RDO
packages? I'm currently using the Juno el-7 packages, and was curious since
kilo is coming out now if updates will stop being built there.
The 2014.2.3 update has been out for a bit, but I wasn't able to find where
if anywhere this might be in the pipeline for update.
What is the lifecycle for these kinds of updates? Do you just follow
upstream for releases and EOL or stop once a new release is available? Is
it possible to get involved with helping on older releases which aren't EOL
but don't have updates if they're not normally going to be done?
5:39 p.m.
Sorry, something fell on my keyboard and sent the message while typing it.
As stated, we follow upstream release cycle:
https://wiki.openstack.org/wiki/Releases
And if you want to help in maintaining RDO, you're more than welcome
https://www.rdoproject.org/packaging/rdo-packaging.html
Our long-term goal is to fully open up RDO contribution process, and
most of it is done.
RDO Juno already includes features contributed by non-redhatters.
We hold a packaging meeting every wedsnesday (notification sent on the
list 2 days prior),
feel free to join us.
Regards,
H.
9:29 a.m.
There are a number of fixes that have been put into git for RDO-juno but
the rpms have not been updated.
Is there going to be another build of the rpms to get these changes so yum
update/packstack applies them? I've resorted to patching individual files.
On Wed, May 6, 2015 at 6:39 PM, Haïkel <hguemar(a)fedoraproject.org> wrote:
Sorry, something fell on my keyboard and sent the message while
typing it.
As stated, we follow upstream release cycle:
https://wiki.openstack.org/wiki/Releases
And if you want to help in maintaining RDO, you're more than welcome
https://www.rdoproject.org/packaging/rdo-packaging.html
Our long-term goal is to fully open up RDO contribution process, and
most of it is done.
RDO Juno already includes features contributed by non-redhatters.
We hold a packaging meeting every wedsnesday (notification sent on the
list 2 days prior),
feel free to join us.
Regards,
H.
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com
7:45 a.m.
@Tom: could you point out these packages ? I CC'ed Alan, he'll be able
to push the pending updates.
Regards,
H.
3:48 p.m.
I've been trying to get Live Migration going in CentOS
python-nova is definitely one I need.
I had to get a repo for CentOS that provided qemu-kvm-rhev because upstream
built qemu-kvm with migration disabled.
There's probably more that prevents block migration buried in there.
On Sun, May 10, 2015 at 8:45 AM, Haïkel <hguemar(a)fedoraproject.org> wrote:
@Tom: could you point out these packages ? I CC'ed Alan,
he'll be able
to push the pending updates.
Regards,
H.
3:41 a.m.
On Mon, May 11, 2015 at 04:48:48PM -0400, Tom Buskey wrote:
I've been trying to get Live Migration going in CentOS
python-nova is definitely one I need.
I had to get a repo for CentOS that provided qemu-kvm-rhev
Haïkel pointed me to a build from CentOS build system on IRC. This is
now called "qemu-kvm-ev":
http://cbs.centos.org/koji/buildinfo?buildID=863
Until a proper repo is created for it, you might want to quickly create
a local repo (using the `createrepo` tool).
because upstream built qemu-kvm with migration disabled.
There's probably more that prevents block migration buried in there.
--
/kashyap
6:44 a.m.
Hi,
On 05/12/2015 10:41 AM, Kashyap Chamarthy wrote:
On Mon, May 11, 2015 at 04:48:48PM -0400, Tom Buskey wrote:
> I've been trying to get Live Migration going in CentOS
>
> python-nova is definitely one I need.
>
> I had to get a repo for CentOS that provided qemu-kvm-rhev
Haïkel pointed me to a build from CentOS build system on IRC. This is
now called "qemu-kvm-ev":
http://cbs.centos.org/koji/buildinfo?buildID=863
Until a proper repo is created for it, you might want to quickly create
a local repo (using the `createrepo` tool).
As a note, CBS provides testing repos for each tag e.g :
http://cbs.centos.org/repos/virt7-kvm-common-testing/x86_64/os/
However there are testing repos and may change at any time, so the
createrepo method is a bit more secure.
Just mentioning this for fast prototyping/testing.
--
Thomas
3269
days inactive
3276
days old
8 comments
6 participants
participants (6)
-
Alan Pevec -
Haïkel -
Jeff Weber -
Kashyap Chamarthy -
Thomas Oulevey -
Tom Buskey