8:33 a.m.
Hi everyone,
I'm wondering what is the current status on the supporting packages
for OpenStack in RDO and how they are handled? I personally think
it's really nice that everything comes packaged from one repository
and we don't have to go to upstream (in the exception of -ev
packages).
In this case, I'm wondering if it is possible to get a newer version
of RabbitMQ in the Mitaka RDO repos, the reason behind this is that
there is a bug affecting us which results in RabbitMQ nodes crashing.
The details of the bug are here:
https://github.com/rabbitmq/rabbitmq-management/issues/245
This issue is resolved in 3.6.4, but 3.6.2 is what is included in the
RDO repos. We could just start using the upstream packages however I
think it's far more productive for everyone in the community to have
updated packages so they don't run into the same surprises that we ran
into and RDO maintains a working out-of-the-box set of packages for
OpenStack without having to resort to other package sources.
I guess all this summarizes to two questions: What's the policy on the
supporting packages in OpenStack and could we work to get an update
RabbitMQ version?
Thanks!
Mohammed
--
Mohammed Naser
9:12 a.m.
In this case, I'm wondering if it is possible to get a newer
version
of RabbitMQ in the Mitaka RDO repos, the reason behind this is that
there is a bug affecting us which results in RabbitMQ nodes crashing.
The details of the bug are here:
https://github.com/rabbitmq/rabbitmq-management/issues/245
This issue is resolved in 3.6.4, but 3.6.2 is what is included in the
RDO repos.
There is 3.6.5 update in the pending repo:
http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Pac...
Please test it and report here.
Cheers,
Alan
9:29 a.m.
So I think what's the underlying question here is how do we define
when to update non-OpenStack components that RDO carries in it's
repositories.
I think with OpenStack components it's easier, there's branches and we
build/test them throughout the lifecycle.
Once we have the proper testing in place, we can update those more frequently.
This isn't limited to RabbitMQ, there's other things like
mariadb/galera, puppet and so on.
Should we try to always have the most up-to-date version (given we are
confident enough in our testing?) ?
Should we only update on a need/request basis ? Only when there's a
known critical bug or CVE ?
We should agree on something and document that somewhere.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Tue, Sep 20, 2016 at 10:12 AM, Alan Pevec <apevec(a)redhat.com> wrote:
> In this case, I'm wondering if it is possible to get a newer
version
> of RabbitMQ in the Mitaka RDO repos, the reason behind this is that
> there is a bug affecting us which results in RabbitMQ nodes crashing.
> The details of the bug are here:
>
> https://github.com/rabbitmq/rabbitmq-management/issues/245
>
> This issue is resolved in 3.6.4, but 3.6.2 is what is included in the
> RDO repos.
There is 3.6.5 update in the pending repo:
http://cbs.centos.org/repos/cloud7-openstack-common-pending/x86_64/os/Pac...
Please test it and report here.
Cheers,
Alan
_______________________________________________
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
10:05 a.m.
On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard <dms(a)redhat.com> wrote:
I think with OpenStack components it's easier, there's
branches and we
build/test them throughout the lifecycle.
Once we have the proper testing in place, we can update those more frequently.
Ideally same would apply for dependencies like rabbitmq, mariadb, we'd
update frequently and release after testing but also vetted by package
maintainers.
Let's start by this last part: I'll check that components in RDO
bugzilla have correct default owner then we setup nagging like
https://fedoraproject.org/wiki/Upstream_release_monitoring for few
critical dependencies.
Alan
10:50 a.m.
Hi Alan:
Thanks for pointing me to the RabbitMQ packages, we're going to test
those internally and report if we run into the issue again.
I do agree with what David has pointed out in that there should be a
process setup in order to make sure that the shipped packages that
come with RDO (at least the supporting ones such as MariaDB/Galera,
etc) should be good-to-go. I imagine this might make things a bit
more difficult in terms of testing them, so I'm not sure what would be
the best path to take in this case.
Thanks
Mohammed
On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec <apevec(a)redhat.com> wrote:
On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard
<dms(a)redhat.com> wrote:
> I think with OpenStack components it's easier, there's branches and we
> build/test them throughout the lifecycle.
> Once we have the proper testing in place, we can update those more frequently.
Ideally same would apply for dependencies like rabbitmq, mariadb, we'd
update frequently and release after testing but also vetted by package
maintainers.
Let's start by this last part: I'll check that components in RDO
bugzilla have correct default owner then we setup nagging like
https://fedoraproject.org/wiki/Upstream_release_monitoring for few
critical dependencies.
Alan
_______________________________________________
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
11:55 a.m.
2016-09-20 17:50 GMT+02:00 Mohammed Naser <mnaser(a)vexxhost.com>:
Hi Alan:
Thanks for pointing me to the RabbitMQ packages, we're going to test
those internally and report if we run into the issue again.
I do agree with what David has pointed out in that there should be a
process setup in order to make sure that the shipped packages that
come with RDO (at least the supporting ones such as MariaDB/Galera,
etc) should be good-to-go. I imagine this might make things a bit
more difficult in terms of testing them, so I'm not sure what would be
the best path to take in this case.
Thanks
Mohammed
These are already tested in our CI + upstream CI.
And get immediate feedback when pushing broken versions of these
components in -testing (AFAIK, -release is safe)
On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec
<apevec(a)redhat.com> wrote:
> On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard <dms(a)redhat.com> wrote:
>> I think with OpenStack components it's easier, there's branches and we
>> build/test them throughout the lifecycle.
>> Once we have the proper testing in place, we can update those more frequently.
>
> Ideally same would apply for dependencies like rabbitmq, mariadb, we'd
> update frequently and release after testing but also vetted by package
> maintainers.
> Let's start by this last part: I'll check that components in RDO
> bugzilla have correct default owner then we setup nagging like
> https://fedoraproject.org/wiki/Upstream_release_monitoring for few
> critical dependencies.
>
> Alan
>
> _______________________________________________
> 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
_______________________________________________
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
10:22 a.m.
On Tue, Sep 20, 2016 at 12:55 PM, Haïkel <hguemar(a)fedoraproject.org> wrote:
2016-09-20 17:50 GMT+02:00 Mohammed Naser
<mnaser(a)vexxhost.com>:
> Hi Alan:
>
> Thanks for pointing me to the RabbitMQ packages, we're going to test
> those internally and report if we run into the issue again.
>
> I do agree with what David has pointed out in that there should be a
> process setup in order to make sure that the shipped packages that
> come with RDO (at least the supporting ones such as MariaDB/Galera,
> etc) should be good-to-go. I imagine this might make things a bit
> more difficult in terms of testing them, so I'm not sure what would be
> the best path to take in this case.
>
> Thanks
> Mohammed
>
These are already tested in our CI + upstream CI.
And get immediate feedback when pushing broken versions of these
components in -testing (AFAIK, -release is safe)
Hi everyone:
We've been running this for a few days now with no reported issues.
We don't seem to be running into that issue anymore that was crashing
nodes.
Would it be possible to look into promoting this packages so that
other RDO users are not affected this issue?
Thanks!
Mohammed
> On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec
<apevec(a)redhat.com> wrote:
>> On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard <dms(a)redhat.com>
wrote:
>>> I think with OpenStack components it's easier, there's branches and
we
>>> build/test them throughout the lifecycle.
>>> Once we have the proper testing in place, we can update those more
frequently.
>>
>> Ideally same would apply for dependencies like rabbitmq, mariadb, we'd
>> update frequently and release after testing but also vetted by package
>> maintainers.
>> Let's start by this last part: I'll check that components in RDO
>> bugzilla have correct default owner then we setup nagging like
>> https://fedoraproject.org/wiki/Upstream_release_monitoring for few
>> critical dependencies.
>>
>> Alan
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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
3:38 p.m.
2016-09-27 17:22 GMT+02:00 Mohammed Naser <mnaser(a)vexxhost.com>:
On Tue, Sep 20, 2016 at 12:55 PM, Haïkel
<hguemar(a)fedoraproject.org> wrote:
> 2016-09-20 17:50 GMT+02:00 Mohammed Naser <mnaser(a)vexxhost.com>:
>> Hi Alan:
>>
>> Thanks for pointing me to the RabbitMQ packages, we're going to test
>> those internally and report if we run into the issue again.
>>
>> I do agree with what David has pointed out in that there should be a
>> process setup in order to make sure that the shipped packages that
>> come with RDO (at least the supporting ones such as MariaDB/Galera,
>> etc) should be good-to-go. I imagine this might make things a bit
>> more difficult in terms of testing them, so I'm not sure what would be
>> the best path to take in this case.
>>
>> Thanks
>> Mohammed
>>
>
> These are already tested in our CI + upstream CI.
> And get immediate feedback when pushing broken versions of these
> components in -testing (AFAIK, -release is safe)
>
Hi everyone:
We've been running this for a few days now with no reported issues.
We don't seem to be running into that issue anymore that was crashing
nodes.
Would it be possible to look into promoting this packages so that
other RDO users are not affected this issue?
Thanks!
Mohammed
If you mean the following build: rabbitmq-server-3.6.5-1.el7 , it's
coming, I'm looking to upgrade erlang at the same time.
Regards,
H.
>> On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec
<apevec(a)redhat.com> wrote:
>>> On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard <dms(a)redhat.com>
wrote:
>>>> I think with OpenStack components it's easier, there's branches
and we
>>>> build/test them throughout the lifecycle.
>>>> Once we have the proper testing in place, we can update those more
frequently.
>>>
>>> Ideally same would apply for dependencies like rabbitmq, mariadb, we'd
>>> update frequently and release after testing but also vetted by package
>>> maintainers.
>>> Let's start by this last part: I'll check that components in RDO
>>> bugzilla have correct default owner then we setup nagging like
>>> https://fedoraproject.org/wiki/Upstream_release_monitoring for few
>>> critical dependencies.
>>>
>>> Alan
>>>
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> 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
5:16 p.m.
Hi Haikel,
Please let me know if you need any testing of those packages at our
side as well.
Thanks,
Mohammed
On Tue, Sep 27, 2016 at 4:38 PM, Haïkel <hguemar(a)fedoraproject.org> wrote:
2016-09-27 17:22 GMT+02:00 Mohammed Naser
<mnaser(a)vexxhost.com>:
> On Tue, Sep 20, 2016 at 12:55 PM, Haïkel <hguemar(a)fedoraproject.org> wrote:
>> 2016-09-20 17:50 GMT+02:00 Mohammed Naser <mnaser(a)vexxhost.com>:
>>> Hi Alan:
>>>
>>> Thanks for pointing me to the RabbitMQ packages, we're going to test
>>> those internally and report if we run into the issue again.
>>>
>>> I do agree with what David has pointed out in that there should be a
>>> process setup in order to make sure that the shipped packages that
>>> come with RDO (at least the supporting ones such as MariaDB/Galera,
>>> etc) should be good-to-go. I imagine this might make things a bit
>>> more difficult in terms of testing them, so I'm not sure what would be
>>> the best path to take in this case.
>>>
>>> Thanks
>>> Mohammed
>>>
>>
>> These are already tested in our CI + upstream CI.
>> And get immediate feedback when pushing broken versions of these
>> components in -testing (AFAIK, -release is safe)
>>
>
> Hi everyone:
>
> We've been running this for a few days now with no reported issues.
> We don't seem to be running into that issue anymore that was crashing
> nodes.
>
> Would it be possible to look into promoting this packages so that
> other RDO users are not affected this issue?
>
> Thanks!
> Mohammed
>
If you mean the following build: rabbitmq-server-3.6.5-1.el7 , it's
coming, I'm looking to upgrade erlang at the same time.
Regards,
H.
>>> On Tue, Sep 20, 2016 at 11:05 AM, Alan Pevec <apevec(a)redhat.com>
wrote:
>>>> On Tue, Sep 20, 2016 at 4:29 PM, David Moreau Simard
<dms(a)redhat.com> wrote:
>>>>> I think with OpenStack components it's easier, there's
branches and we
>>>>> build/test them throughout the lifecycle.
>>>>> Once we have the proper testing in place, we can update those more
frequently.
>>>>
>>>> Ideally same would apply for dependencies like rabbitmq, mariadb,
we'd
>>>> update frequently and release after testing but also vetted by package
>>>> maintainers.
>>>> Let's start by this last part: I'll check that components in RDO
>>>> bugzilla have correct default owner then we setup nagging like
>>>> https://fedoraproject.org/wiki/Upstream_release_monitoring for few
>>>> critical dependencies.
>>>>
>>>> Alan
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>> _______________________________________________
>>> 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
3095
days inactive
3102
days old
8 comments
4 participants
participants (4)
-
Alan Pevec -
David Moreau Simard -
Haïkel -
Mohammed Naser