To quote from yesterday's RDO IRC meeting:
We have basically not had a CentOS Cloud SIG meeting for 2 months. Part of this is because of travel/summer/whatever. I also have a standing conflict with that meeting, which I'm trying to fix. But more than that, I think it's because the Cloud SIG is just a rehash of this meeting, because only RDO is participating.
On the one hand, we don't really accomplish much in that meeting when we do have it. On the other hand, it's a way to get RDO in front of another audience.
So, I guess I'm asking if people still think it's valuable, and will try to carve out a little time for this each week. Or as was suggested in the meeting, should we attempt to merge the two meetings in some meaningful way, until such time as other Cloud Software communities see a benefit in participating?
Is there interest from non-KVM or non-OpenStack communities in the CentOS cloud SIG ?
Tim
On 18/08/16 19:03, "centos-devel-bounces@centos.org on behalf of Rich Bowen" <centos-devel-bounces@centos.org on behalf of rbowen@redhat.com> wrote:
To quote from yesterday's RDO IRC meeting:
We have basically not had a CentOS Cloud SIG meeting for 2 months. Part of this is because of travel/summer/whatever. I also have a standing conflict with that meeting, which I'm trying to fix. But more than that, I think it's because the Cloud SIG is just a rehash of this meeting, because only RDO is participating.
On the one hand, we don't really accomplish much in that meeting when we do have it. On the other hand, it's a way to get RDO in front of another audience.
So, I guess I'm asking if people still think it's valuable, and will try to carve out a little time for this each week. Or as was suggested in the meeting, should we attempt to merge the two meetings in some meaningful way, until such time as other Cloud Software communities see a benefit in participating?
-- Rich Bowen - rbowen@redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
2016-08-18 19:03 GMT+02:00 Rich Bowen rbowen@redhat.com:
To quote from yesterday's RDO IRC meeting:
We have basically not had a CentOS Cloud SIG meeting for 2 months. Part of this is because of travel/summer/whatever. I also have a standing conflict with that meeting, which I'm trying to fix. But more than that, I think it's because the Cloud SIG is just a rehash of this meeting, because only RDO is participating.
On the one hand, we don't really accomplish much in that meeting when we do have it. On the other hand, it's a way to get RDO in front of another audience.
So, I guess I'm asking if people still think it's valuable, and will try to carve out a little time for this each week. Or as was suggested in the meeting, should we attempt to merge the two meetings in some meaningful way, until such time as other Cloud Software communities see a benefit in participating?
As a follow-up, we'll start copying centos-devel list for RDO meeting minutes.
-- Rich Bowen - rbowen@redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 18/08/16 18:03, Rich Bowen wrote:
So, I guess I'm asking if people still think it's valuable, and will try to carve out a little time for this each week. Or as was suggested in the meeting, should we attempt to merge the two meetings in some meaningful way, until such time as other Cloud Software communities see a benefit in participating?
As we saw last week with the tripleO issues, its quite important we not only retain this meeting, but also bring all interfaces from the RDO side into the CentOS project to this meeting. At the very least, the Cloud SIG's usage of resources ( and interfaces to/from cbs.centos.org / ci.centos.org / buildlogs.centos.org and the mirror network ) should be talked through at the meeting.
At this point its all done via arbitrary pings on irc, emails etc - and while this is ok for emergency work, the regular stuff should be brought to the SIG meeting.
Secondly, not having this meeting means there is no way for the other SIG's to interface with the group - its taking a long time, as an example, to sort out what is needed and what the process might be for the Power8le builds for RDO to kick off; similarly as folks request deps on other SIG content ( ceph as an example ) - we still need a place focus those conversations and I think it makes far more sense to do that in the Cloud SIG meeting rather than a RDO meeting, since it works both ways.
So, I think the question that there is no other cloud community working with the Cloud SIG, is actually a wrong question. The question should be, is RDO doing anything that anyone else in the ecosystem needs to care about - and is anyone else in the ecosystem doing anything that RDO should care about ? Then work that back through to also include, does RDO do anything that the CentOS Project interfaces with.
regards,
On 08/24/2016 08:49 PM, Karanbir Singh wrote:
On 18/08/16 18:03, Rich Bowen wrote:
So, I guess I'm asking if people still think it's valuable, and will try to carve out a little time for this each week. Or as was suggested in the meeting, should we attempt to merge the two meetings in some meaningful way, until such time as other Cloud Software communities see a benefit in participating?
As we saw last week with the tripleO issues, its quite important we not only retain this meeting, but also bring all interfaces from the RDO side into the CentOS project to this meeting. At the very least, the Cloud SIG's usage of resources ( and interfaces to/from cbs.centos.org / ci.centos.org / buildlogs.centos.org and the mirror network ) should be talked through at the meeting.
At this point its all done via arbitrary pings on irc, emails etc - and while this is ok for emergency work, the regular stuff should be brought to the SIG meeting.
Secondly, not having this meeting means there is no way for the other SIG's to interface with the group - its taking a long time, as an example, to sort out what is needed and what the process might be for the Power8le builds for RDO to kick off; similarly as folks request deps on other SIG content ( ceph as an example ) - we still need a place focus those conversations and I think it makes far more sense to do that in the Cloud SIG meeting rather than a RDO meeting, since it works both ways.
So, I think the question that there is no other cloud community working with the Cloud SIG, is actually a wrong question. The question should be, is RDO doing anything that anyone else in the ecosystem needs to care about - and is anyone else in the ecosystem doing anything that RDO should care about ? Then work that back through to also include, does RDO do anything that the CentOS Project interfaces with.
Well, ok, but when we have these meetings, it's a few RDO people talking to one another, with rare exceptions.
The consensus on the RDO mailing list is that folks aren't interested in attending another meeting in which the same things are rehashed.
So, I guess I need help 1) figuring out what the agenda for this meeting actually is and 2) getting people to actually show up for it. If 1) we're discussing the wrong things and 2) nobody's there, it doesn't seem like a valuable way to spend anyone's time.
--Rich
2016-08-29 22:40 GMT+02:00 Rich Bowen rbowen@redhat.com:
On 08/24/2016 08:49 PM, Karanbir Singh wrote:
On 18/08/16 18:03, Rich Bowen wrote:
So, I guess I'm asking if people still think it's valuable, and will try to carve out a little time for this each week. Or as was suggested in the meeting, should we attempt to merge the two meetings in some meaningful way, until such time as other Cloud Software communities see a benefit in participating?
As we saw last week with the tripleO issues, its quite important we not only retain this meeting, but also bring all interfaces from the RDO side into the CentOS project to this meeting. At the very least, the Cloud SIG's usage of resources ( and interfaces to/from cbs.centos.org / ci.centos.org / buildlogs.centos.org and the mirror network ) should be talked through at the meeting.
At this point its all done via arbitrary pings on irc, emails etc - and while this is ok for emergency work, the regular stuff should be brought to the SIG meeting.
Secondly, not having this meeting means there is no way for the other SIG's to interface with the group - its taking a long time, as an example, to sort out what is needed and what the process might be for the Power8le builds for RDO to kick off; similarly as folks request deps on other SIG content ( ceph as an example ) - we still need a place focus those conversations and I think it makes far more sense to do that in the Cloud SIG meeting rather than a RDO meeting, since it works both ways.
So, I think the question that there is no other cloud community working with the Cloud SIG, is actually a wrong question. The question should be, is RDO doing anything that anyone else in the ecosystem needs to care about - and is anyone else in the ecosystem doing anything that RDO should care about ? Then work that back through to also include, does RDO do anything that the CentOS Project interfaces with.
Well, ok, but when we have these meetings, it's a few RDO people talking to one another, with rare exceptions.
The consensus on the RDO mailing list is that folks aren't interested in attending another meeting in which the same things are rehashed.
So, I guess I need help 1) figuring out what the agenda for this meeting actually is and 2) getting people to actually show up for it. If 1) we're discussing the wrong things and 2) nobody's there, it doesn't seem like a valuable way to spend anyone's time.
--Rich
I have a topic for thursday which is aarch64 enablement in CBS. We finally agreed on enabling it by default w/ Brian and Marcin, but we need to put that in motion.
I can't summarize quickly my thoughts, but I'm not dropping the ball. Main reason, I'm CC'ing RDO meeting minutes on this list is to continue providing feedback to the CentOS community on what's happening until we find a better solution.
H.
-- Rich Bowen - rbowen@redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 30/08/16 17:14, Haïkel wrote:
I have a topic for thursday which is aarch64 enablement in CBS. We finally agreed on enabling it by default w/ Brian and Marcin, but we need to put that in motion.
I can't summarize quickly my thoughts, but I'm not dropping the ball. Main reason, I'm CC'ing RDO meeting minutes on this list is to continue providing feedback to the CentOS community on what's happening until we find a better solution.
lets talk about in this weeks CentOS Cloud meeting - there is a ton of work that needs to be done behind the scene even after the cbs builds are done, in order to enable aarch64 and power builds to release, and I've been doing it slowly since afaict noone other than ovirt were ready with content.
regards,
On 05/09/16 12:05, Karanbir Singh wrote:
On 30/08/16 17:14, Haïkel wrote:
I have a topic for thursday which is aarch64 enablement in CBS. We finally agreed on enabling it by default w/ Brian and Marcin, but we need to put that in motion.
I can't summarize quickly my thoughts, but I'm not dropping the ball. Main reason, I'm CC'ing RDO meeting minutes on this list is to continue providing feedback to the CentOS community on what's happening until we find a better solution.
lets talk about in this weeks CentOS Cloud meeting - there is a ton of work that needs to be done behind the scene even after the cbs builds are done, in order to enable aarch64 and power builds to release, and I've been doing it slowly since afaict noone other than ovirt were ready with content.
additionally : https://bugs.centos.org/view.php?id=11090 and https://bugs.centos.org/view.php?id=11367 are two things that I'd like to talk through this week if we can
On Wed, Sep 7, 2016 at 12:29 AM, Karanbir Singh mail-lists@karan.org wrote:
On 05/09/16 12:05, Karanbir Singh wrote:
On 30/08/16 17:14, Haïkel wrote:
I have a topic for thursday which is aarch64 enablement in CBS. We finally agreed on enabling it by default w/ Brian and Marcin, but we need to put that in motion.
I can't summarize quickly my thoughts, but I'm not dropping the ball. Main reason, I'm CC'ing RDO meeting minutes on this list is to continue providing feedback to the CentOS community on what's happening until we find a better solution.
lets talk about in this weeks CentOS Cloud meeting - there is a ton of work that needs to be done behind the scene even after the cbs builds are done, in order to enable aarch64 and power builds to release, and I've been doing it slowly since afaict noone other than ovirt were ready with content.
additionally : https://bugs.centos.org/view.php?id=11090 and https://bugs.centos.org/view.php?id=11367 are two things that I'd like to talk through this week if we can
Wouldn't all those issues fit https://www.centos.org/community/calendar/#Community_Buildsystem_&_Infra... ?
Alan
On 07/09/16 09:00, Alan Pevec wrote:
Wouldn't all those issues fit https://www.centos.org/community/calendar/#Community_Buildsystem_&_Infra... ?
not really these are fallouts from the custom work I did to support RDO itself, these are not part of a generic process in cbs/ci that we offer everyone/
On 29/08/16 21:40, Rich Bowen wrote:
Well, ok, but when we have these meetings, it's a few RDO people talking to one another, with rare exceptions.
The consensus on the RDO mailing list is that folks aren't interested in attending another meeting in which the same things are rehashed.
So, I guess I need help 1) figuring out what the agenda for this meeting actually is and 2) getting people to actually show up for it. If 1) we're discussing the wrong things and 2) nobody's there, it doesn't seem like a valuable way to spend anyone's time.
Anything that interfaces with, or is related with the CentOS Infra, the CentOS Mirror network, the CI and CBS resources, should be brought to the CentOS Cloud Instance Meetings, I am not interested in hanging around in the RDO meetings since thats a waste of my time.
I'd rather have a 20 min topical relevant meeting against a schedule that also permits anyone else doing any work with the content from the Cloud SIG to come along.
w.r.t specifics, you will need to speak with the RDO Crew, there is a near constant set of requests and issues being thrown up through the week, and they really should get consolidated down to that one meeting.
-
Alan Pevec -
Haïkel -
Karanbir Singh -
Rich Bowen -
Tim Bell