18:01:00 <SlickNik> #startmeeting trove-bp-review
18:01:01 <openstack> Meeting started Mon Aug 25 18:01:00 2014 UTC and is due to finish in 60 minutes.  The chair is SlickNik. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:02 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:04 <openstack> The meeting name has been set to 'trove_bp_review'
18:01:15 <SlickNik> Giving folks a couple of minutes to trickle in.
18:01:27 <amrith> ./
18:01:43 <schang> o/
18:02:09 <sgotliv> o/
18:02:11 <dougshelley66> o/
18:02:18 <peterstac> o/
18:02:20 <vgnbkr> o/
18:03:15 <iartarisi> o/
18:03:41 <SlickNik> Agenda at:
18:03:42 <georgelorch> o/
18:03:44 <SlickNik> #link https://wiki.openstack.org/wiki/Meetings/TroveBPMeeting
18:04:24 <SlickNik> #topic SUSE integration
18:04:25 <esmute> o/
18:04:49 <amrith> I stuck this on the agenda ... here comes a paste blast. Over the past several days I have seen some bugs being reported, and some changes being submitted for SuSE support. I don't think the review forum is where the community should debate the overall ramifications of supporting a new platform, and getting bug fixes for a platform we don't test seems problematic. I believe there needs to be a blueprint for SuSE support
18:04:49 <amrith> and then we can prioritize not just code, but also reviews, testing, and CI changes if required.
18:04:49 <amrith> What do others think?
18:05:48 <SlickNik> Are any of the SUSE folks here at the meeting?
18:05:48 <amrith> <EOT>
18:05:54 <amrith> Yes, I invited a few
18:06:06 <amrith> Ionut and Felipe are here
18:06:07 <iartarisi> I'm here
18:06:15 <amrith> sorry, Felipe may not be here.
18:06:25 <iartarisi> freyes: ping
18:06:53 <iartarisi> I agree what amrith said basically, except for s/SuSE/SUSE/ ;)
18:07:09 <iartarisi> I'm open to opening up a blueprint to track this
18:07:10 <amrith> SoRRY
18:07:21 <vgnbkr> A deeper question is "Is trove going to support every distribution of linux?"  If not, do we want to consider building a framework for distribution vendors to certify distros themselves?
18:08:02 <sgotliv> if SUSE is important to someone we definitely need to support it
18:08:45 <sgotliv> for me RHEL and Fedora probably more important :-)
18:08:53 <vgnbkr> So then the Trove community will be taking on support for all 500 distributions?
18:09:14 <SlickNik> sgotliv / vgnbkr: Yes, but there is a resourcing concern. We don't have resources to support / test every linux distro as part of the upstream CI.
18:09:25 <esmute> how are other openstack projects in terms of supporting other OSs besides debian/ubuntu?
18:09:28 <iartarisi> FWIW SUSE is already supported by most of the other openstack projects. There's even an installation guide at: http://docs.openstack.org/icehouse/ for example.
18:09:31 <sgotliv> no, I will verify that Fedora is working someone needs to care about SUSE
18:09:41 <amrith> to be clear, I'm happy to work with ionut and folks on Trove and SUSE.
18:09:54 <amrith> I just would like to make sure we understand the scope of this
18:10:04 <iartarisi> amrith: +1 on defining a scope
18:10:05 <amrith> as it is larger than a breadbox and smaller than world peace
18:10:38 <SlickNik> esmute: Usually the interested parties (RedHat / SUSE) take on the onus of making sure that the project is working for their distro.
18:11:09 <sgotliv> that what I said
18:11:11 <vgnbkr> So then part of that needs to be having the gate test multiple distributions for each patch, otherwise support will just get out of date (as it has done with Fedora).
18:12:03 <sgotliv> vgnbkr, I agree in general
18:12:23 <sgotliv> I just have the same resource problem :-)
18:12:55 <iartarisi> FWIW we also have our own CI infrastructure and run all master and latest stable tests so we can ensure that once we have SUSE support, the tests won't break
18:13:48 <amrith> I didn't want to define the scope here, but get broad agreement on the fact that we need a blueprint.
18:14:00 <iartarisi> this is the public jenkins: https://ci.opensuse.org/view/OpenStack/job/openstack-trackupstream/ there's also a private one for SLES
18:14:03 <amrith> if that's agreed, I think we can pick up the details offline and come back to this team.
18:14:44 <SlickNik> amrith: +1 on a blueprint.
18:15:38 <SlickNik> I'm good with doing this as long as there are points of contact from the distro folks who are driving this.
18:16:20 <amrith> SlickNik: I will make sure of that ...
18:16:29 <amrith> working with iartarisi
18:16:31 <amrith> on it
18:16:32 * iartarisi volunteers as PoC
18:16:42 <iartarisi> thanks, amrith
18:16:45 * amrith volunteers iartarisi ;)
18:18:31 <amrith> if that's agreed, I make a motion to move on to the next topic
18:19:15 <SlickNik> #topic Open Discussion
18:19:40 <SlickNik> Anything else to discuss for today?
18:20:13 <SlickNik> Looks like not.
18:20:23 <SlickNik> #endmeeting