04:00:41 <krtaylor> #startmeeting third-party
04:00:42 <openstack> Meeting started Wed Mar 11 04:00:41 2015 UTC and is due to finish in 60 minutes.  The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.
04:00:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
04:00:45 <openstack> The meeting name has been set to 'third_party'
04:00:53 <krtaylor> anyone here for third party working group meeting?
04:01:33 <krtaylor> hey asselin_
04:01:40 <asselin_> hi
04:01:56 <krtaylor> might be a quick one tonight, just us so far
04:02:18 <asselin_> ok
04:02:23 <krtaylor> anything on your mind?
04:03:12 <asselin_> lots of stuff. I discussed on monday a bit in the other 3rd party meeting.
04:03:31 <asselin_> got some patches up finally for openstackci
04:03:53 <krtaylor> yes, I saw, good stuff
04:04:42 <asselin_> #link https://review.openstack.org/#/q/topic:downstream-puppet,n,z
04:06:04 <asselin_> you?
04:07:48 <krtaylor> so, how were you thinking of moving that forward, we had discussed the possibility of having a mini -sprint for it
04:07:48 <krtaylor> downstream-puppet (openstackci)
04:08:31 <krtaylor> me? don't understand
04:08:37 <asselin_> yeah...I would like to get some momentum going first, then do a mini-sprint
04:08:45 <krtaylor> right, ok
04:08:46 <asselin_> you--> anything on your mind
04:08:51 <krtaylor> ah, ok
04:08:53 <krtaylor> hehheh
04:09:27 <krtaylor> I am ready to get horizontal, DST makes this...interesting
04:09:56 <asselin_> yeah...late for me, later for you
04:11:06 <krtaylor> especially since we created this meeting for the other side of the world, and no one attends, makes me wonder about going back to one time for WG and then also have the Office Hours on Monday for infra coaching
04:11:38 <krtaylor> we really need to have a few people to make a meaningful meeting, get something done
04:11:47 <asselin_> agreed
04:12:06 <krtaylor> but, I digress
04:12:21 <krtaylor> on my mind, yes
04:12:42 <krtaylor> I did finish a first pass at the TPWG wiki
04:12:53 <krtaylor> complete with index for tools as we discussed
04:12:54 <asselin_> TPWG?
04:13:04 <krtaylor> Third Party Working Group
04:13:12 <asselin_> rihgt.....it's late :)
04:13:17 <krtaylor> I get tired of typing that out
04:14:01 <krtaylor> here's the link
04:14:04 <krtaylor> #link https://wiki.openstack.org/wiki/ThirdPartyCIWorkingGroup
04:14:14 * asselin_ looking
04:14:28 <krtaylor> I havent linked it into the meetings yet, just getting started
04:14:45 <krtaylor> please feel free to add/change
04:15:00 <patrickeast> hey guys, sry i'm late
04:15:06 <krtaylor> hey patrickeast
04:15:10 <asselin_> cools..that's a great start!
04:15:20 <krtaylor> asselin_, thanks
04:15:37 <asselin_> patrickeast, hi
04:15:56 <krtaylor> it's a start, gets an agenda for third party people that want to make all this better, not just run whats there
04:16:17 <patrickeast> oo nice, glad to see the in tree ci stuff movin along
04:16:29 <patrickeast> i like the wiki page too
04:16:44 <krtaylor> I'd like to start thinking about liberty work, if we have enough good stuff, we can propose a design session
04:16:51 <krtaylor> patrickeast, feel free to add to it too
04:18:13 <krtaylor> have you all heard about your summit talk yet?
04:18:28 <asselin_> no...not yet. are decisions made already?
04:18:38 <patrickeast> i haven't heard anything
04:18:59 <krtaylor> not sure, I havent heard anything yet, but I have been internal facing a lot lately
04:19:47 <krtaylor> I did hack some swift tools for log hosting
04:20:03 <krtaylor> I am hoping to add those to the tools index in the wiki
04:20:16 <krtaylor> but I need to get approval to push them out to my github
04:20:53 <krtaylor> that is where a stackforge repo would really help
04:21:29 <patrickeast> different policy for open sourcing stuff that way?
04:21:35 <asselin_> why's that different?
04:22:08 <krtaylor> because it is somewhat under the openstack way of doing things, has already been approved for us to contribute
04:22:17 <patrickeast> gotcha
04:22:18 <krtaylor> big company, you understand :)
04:22:29 <patrickeast> hehe yea
04:23:25 <krtaylor> asselin_, I think I have intel for next week "highlighting a third party  system", want to get on the agenda for the following week for your HP system?
04:23:35 <asselin_> patrickeast, had you tried disk image builder?
04:23:42 <asselin_> krtaylor, sure
04:23:54 <krtaylor> perfect, I'll make a section in the wiki
04:24:03 <patrickeast> not yet, still working out some kinks in my ci system after moving it around/adding new stuff
04:24:12 <asselin_> krtaylor, well...prefer to present in a morning time
04:24:24 <krtaylor> asselin_, absolutely
04:24:31 <krtaylor> so in 3 weeks
04:24:37 <asselin_> krtaylor, yes
04:25:28 <krtaylor> one of my team tried disk image builder, had some problems, I'm not sure what
04:25:37 <asselin_> fyi: dib is the way to go for anyone who hasn't start yet.
04:25:49 <krtaylor> agreed
04:26:03 <patrickeast> yea i'm pretty excited to try it out
04:26:08 <asselin_> krtaylor, really? I had way less problems with it than the script approach
04:26:26 <krtaylor> yeah, I'm not sure why, I need to follow up on that
04:26:27 <patrickeast> doesn't it end up doing pretty much the same things?
04:26:29 <asselin_> much more modular and simpler to work around issues, debug, and way faster
04:27:03 <asselin_> patrickeast, the result is basically the same, but the process is better in every aspect I can think of
04:27:10 <krtaylor> nice
04:27:28 <asselin_> actually, the result is much better too :)
04:27:53 <patrickeast> very cool
04:28:28 <asselin_> in our case I was adding some new nodepool providers. With DIB, they can start working right away, because the image is ready.
04:28:52 <asselin_> previously they would spend 2-6 hours building a new image before being operational
04:28:55 <patrickeast> ahh yea, that is convienent, having to wait for a new image is a pain
04:28:59 <patrickeast> oh ouch
04:29:10 <patrickeast> mine only takes ~45 min
04:29:35 <krtaylor> why so long?
04:29:45 <patrickeast> is that from the network speeds? or are you using something different from the infra devstack node prep scripts?
04:30:01 <asselin_> not sure...it used to be fast. I think some of the images are very big and all the caching slows it down
04:30:27 <asselin_> also, it doesn't help that I have 16*2 providers all building at the same time.
04:30:46 <patrickeast> yea that definitely would slow it down
04:30:48 <asselin_> I bet my systems got detected and squeezed into a smaller pipe
04:31:22 <asselin_> so dib scales much better
04:31:33 <krtaylor> detected? hehheh
04:31:44 <patrickeast> luckily right now i only have a single provider
04:31:57 <patrickeast> will be adding more in for FC though, probably following a similar setup that you have
04:32:12 <patrickeast> well
04:32:17 <patrickeast> thats not true, i have two mirrored setups
04:32:22 <patrickeast> one for dev/messing around with
04:32:53 <asselin_> i have 3: one for openstack, one for internal, and one for me to break
04:32:55 <patrickeast> i like the idea of dib though so that i know the 'dev' one will be the exact same as the 'live' version
04:34:40 <krtaylor> yes, we do too, very helpful, but we keep dev at tip and production is a static known working infra, much more stable that way
04:35:14 <krtaylor> but we routinely break dev and have started another environment for really breaking things  :)
04:35:46 <patrickeast> hehe yea
04:36:28 <krtaylor> patrickeast, we are kinda free form tonight, is there anything you wanted to bring up?
04:36:45 <patrickeast> nah, nothing here
04:37:52 <patrickeast> i've finally got the last of my cinder changes through for kilo, so aside form testing and bug fixes i'm hoping to have more time to help out with the thirdparty things
04:38:11 <krtaylor> excellent!
04:39:13 <krtaylor> in one of the earlier meetings, we'l bring up liberty work, things happening that we want to be involved in
04:39:23 <krtaylor> that will be coming up in the next few weeks
04:39:29 <patrickeast> sounds good
04:39:39 <krtaylor> as well as downstream-puppet (openstackci)
04:40:47 * asselin_ hopes to have openstackci working before the summit
04:41:23 <krtaylor> that would be great, if not, maybe we could work on it there
04:41:45 <patrickeast> yea either way it would be pretty awesome
04:41:47 <krtaylor> asselin_, I take it you are going, or is that dependent on the summit talk?
04:41:49 <asselin_> yeah. I think it would be a huge enable for more stuff
04:41:57 <krtaylor> agreed
04:42:14 <asselin_> krtaylor, I am going, I did get approved! :)
04:42:21 <patrickeast> nice!
04:43:06 <krtaylor> perfect
04:44:10 * krtaylor thinks we'll have to have a beverage session
04:44:22 <asselin_> +1
04:44:30 <patrickeast> +1
04:44:53 <krtaylor> anything else to discuss?
04:45:51 <asselin_> not from me
04:46:23 <patrickeast> same
04:47:14 <krtaylor> alright, we'll wrap this up then
04:47:32 <krtaylor> thanks everyone!
04:47:46 <asselin_> goodnight
04:47:51 <krtaylor> #endmeeting