21:02:33 <rbergeron> #startmeeting Cloud SIG
21:02:33 <zodbot> Meeting started Thu Nov 11 21:02:33 2010 UTC.  The chair is rbergeron. Information about MeetBot at
21:02:33 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
21:02:44 <rbergeron> #meetingname Cloud SIG
21:02:44 <zodbot> The meeting name has been set to 'cloud_sig'
21:02:55 <rbergeron> #chair gholms jforbes
21:02:55 <zodbot> Current chairs: gholms jforbes rbergeron
21:03:04 <rbergeron> #topic Roll Call, yo
21:03:30 * mgoldmann says hi!
21:03:35 <rbergeron> hey mgoldmann ;)
21:03:37 * sgordon is here
21:03:47 * rbergeron waves at sgordon
21:04:15 * sgordon does a solo mexican wave
21:04:33 * rbergeron isn't sure what that looks like exactly but thinks it sounds interesting
21:05:01 <rbergeron> alright. let's get started, we had the whole time change thing so hopefully the folks in #fedora-cloud will notice my yelling that it's time to come over
21:05:36 <rbergeron> #topic BoxGrinder
21:05:39 <rbergeron> #chair mgoldmann
21:05:39 <zodbot> Current chairs: gholms jforbes mgoldmann rbergeron
21:05:50 <mgoldmann> uh :)
21:05:51 <rbergeron> mgoldmann: what's the scoop
21:05:52 <mgoldmann> what now?!
21:06:05 <rbergeron> I saw you posted some bz's?
21:06:06 * gholms grabs axe
21:06:09 <gholms> I've been highlighted!
21:06:15 <gholms> Oh, the cloud meeting.
21:06:19 <rbergeron> yeah, that thing
21:06:24 <mgoldmann> I started the process of submitting BoxGrinder to Fedora
21:06:43 * rbergeron nods
21:06:47 <mgoldmann> not all gems are submited because I need to focus on moving to euca2ools
21:06:59 * jsmith shows up late, again
21:07:26 <rbergeron> ok
21:07:30 <rbergeron> how much is that gonig to impact you?
21:07:32 <mgoldmann> now I'm waiting for reviewer to fix my errors :)
21:07:50 <rbergeron> can you list the bz's for us so we have them?
21:07:54 <mgoldmann> or to point out – I'll fix them of course :)
21:07:58 <mgoldmann> sure, one sec
21:08:01 <rbergeron> thanks!
21:08:02 <gholms> I'm on that; hang on a sec
21:08:04 * rbergeron waves to jsmith
21:08:29 <mgoldmann>
21:08:36 <rbergeron> #link
21:08:47 <rbergeron> #info mgoldmann is in the process of submitting BoxGrinder to Fedora
21:08:52 <gholms> Please wait before adding more links!
21:08:52 <mgoldmann>
21:08:58 <rbergeron> #info not all gems are submitted because he needs to move to euca2ools
21:09:18 * mgoldmann waits
21:09:30 <rbergeron> [we all pause and wait for gholms' wisdom
21:09:31 <rbergeron> ]
21:09:32 <rbergeron> ;D
21:09:51 <gholms> I'm just going to post links in a form that is more useful to the minutes.  You can go ahead and keep talking.
21:10:03 <mgoldmann> uff, ok :)
21:10:05 <rbergeron> ah, kewl.
21:10:27 <mgoldmann> tomorrow I'll update Feature page on wiki
21:10:31 <rbergeron> as far as the actual Feature page - do you need any help filling that out, or are there any specific things.....
21:10:34 <rbergeron> ;)
21:10:42 <rbergeron> ... thatyou think you'll need help with, other than reviews?
21:11:03 <mgoldmann> currently I think I have everything uder control
21:11:10 <mgoldmann> thank you
21:11:16 * rbergeron is thinking specifically of things like documentation and getting those docs maybe into the fedora docs - jsmith, is that something we need/should do or does it matter?
21:11:32 <mgoldmann> our docs are currently wiki based
21:11:34 <rbergeron> or sparks - if you're around - ^^ :)
21:11:36 <mgoldmann> is that an issue?
21:12:05 <rbergeron> Well, I know Fedora has its own documentation so thatpeople can pull it up more or less from the desktop
21:12:20 <rbergeron> so I don't know if tehre is an easy way to link in the Fedora docs to your documentatino, or what the norm there is.
21:12:20 <mgoldmann> ah, right
21:12:34 <rbergeron> stickster - maybe you have thoughts
21:12:44 <mgoldmann> ok, if someone could shed some light on it – I would be thankful
21:12:45 * rbergeron will just ping the planet until someone comes to share their docs wisdom
21:12:59 <gholms> Incoming spam!
21:13:05 <rbergeron> wooo, spam
21:13:05 <gholms> #help Review Request: rubygem-boxgrinder-core (
21:13:09 <gholms> #help Review Request: rubygem-boxgrinder-build (
21:13:14 <gholms> #help Review Request: rubygem-boxgrinder-rpm-based-os-plugin (
21:13:18 <gholms> #help Review Request: rubygem-boxgrinder-build-fedora-os-plugin (
21:13:20 <stickster> rbergeron: Not sure if I understand the question
21:13:23 <gholms> #help Review Request: rubygem-boxgrinder-build-vmware-platform-plugin (
21:13:27 <gholms> #help Review Request: rubygem-boxgrinder-local-delivery-plugin (
21:13:31 <gholms> #help Review Request: rubygem-boxgrinder-sftp-delivery-plugin (
21:13:35 <gholms> </spam>
21:13:43 <jsmith> rbergeron: Sorry, was on the phone... what's the question?
21:13:46 <rbergeron> stickster: mgoldmann is working on BoxGrinder as a feature - and they already have some documentation, but it's on the jboss wiki.
21:13:55 <rbergeron> Do we normally take that type of documentatino and then pull it into the Fedora docs?
21:13:59 <rbergeron> or how does that work?
21:14:00 <mgoldmann> something like that:
21:14:11 <rbergeron> Or do we just do a redirect essentially?
21:14:22 <stickster> rbergeron: Generally one would find a file in /usr/share/doc/BoxGrinder-* that might be a README saying, "Refer to <URL> for full documentation"
21:14:40 <stickster> That might be packaged already in the BG code?
21:15:06 <stickster> I don't think the norm is to snapshot a whole set of content and then duplicate it in Fedora Documentation
21:15:12 <mgoldmann> well -every plugin has a README with that info
21:15:44 <rbergeron> okay. I just didn't know if we needed to duplicate stuff into docs.fp.o or... what, though I don't know how that all magically gets built. ;)
21:15:49 <rbergeron> oh, the things i have to learn still.
21:15:52 <gholms> If the documentation is part of the source tarball then it one usually packages it.  Otherwise, those readmes should be fine.
21:16:18 <stickster> gholms: Exactly
21:16:20 <mgoldmann> example README:
21:16:25 <rbergeron> Okay then :)
21:16:27 <mgoldmann> it's not big, I can extend it
21:16:31 <stickster> The Fedora Docs project really concentrates on Fedora-specific documentation, as opposed to upstream
21:17:02 <rbergeron> okeedoke.
21:17:24 <rbergeron> so mgoldmann is on track with the BG feature... and we just need some help with reviews.
21:17:27 <rbergeron> :)
21:17:54 <rbergeron> Anything else here?
21:18:05 <rbergeron> mgoldmann: can you link the feature onto the cloud sig page down at the bottom?
21:18:10 <jforbes> Ugh, timechange fail, sorry folks
21:18:18 <mgoldmann> once I get all dependencies – I'll submit more gems
21:18:25 <mgoldmann> rbergeron: sure!
21:18:44 <jforbes> mgoldmann: I did some looking at boxgrinder this week, will get with you offline when you have time for some questions...
21:18:56 <rbergeron> mgoldmann:
21:18:57 <mgoldmann> jforbes: sure
21:19:01 <rbergeron> in there is dandy
21:19:05 <rbergeron> mgoldmann: thanks!
21:19:24 <rbergeron> #action mgoldmann to link feature to Cloud_SIG currect projects on wiki
21:19:37 <rbergeron> anythign else?
21:19:42 * rbergeron shall move onwards
21:19:54 <rbergeron> #topic EC2
21:20:05 <rbergeron> jforbes: since you're just in time ;) how goes
21:20:15 <rbergeron> anything exciting going on
21:21:21 <jforbes> Goes okay, I had a bit of distraction this week with some kvm bits, but I am at a bit of a loss on how to do the EBS bit with just the tools we have.  That got me looking a bit more at Boxgrinder since it will be in F15
21:21:43 <rbergeron> m/e saw some business on the list about a httpd hang -
21:21:46 <jforbes> Basically it seems that I can get boxgrinder to produce the images that we want with a few code changes
21:22:05 <rbergeron> ahhhh, yes.
21:22:05 <mgoldmann> jforbes: good news!
21:22:20 * rbergeron cues up professor farnsworth
21:23:43 <jforbes> Trying to look at it a bit more this afternoon since my code changes are good for fedora, but might not be ideal for boxgrinder as a whole.  They need to be redone into config options
21:23:59 * rbergeron nods
21:24:16 <jforbes> but killer headache is making this much more painful than it should be, so I might have to pick it back up in the am
21:24:33 * rbergeron nods
21:25:00 <mgoldmann> jforbes: feel free to join #boxgrinder and ping me any time works for you when I'll be onlie
21:25:39 <jforbes> I guess that begs the question, do we want to put images out for broader testing that cannot be reproduced without patching boxgrinder as well?
21:26:33 <gholms> How does it compare to what we have now?
21:26:58 <jforbes> gholms: much better
21:27:08 <jforbes> well, I haven't done the 32bit images to test
21:27:20 <jforbes> but the same thing would be done for them
21:27:27 <gholms> If it's better than what we have, at this point I would go for it.
21:27:45 <gholms> We *are* all still learning this, after all.
21:28:05 <jforbes> Okay, I will get the 32bit done in the AM and post both along with the patch and appl config for bg
21:28:48 <rbergeron> thanks, jforbes.
21:29:11 <gholms> #action jforbes will work on boxgrinder-based EC2 images
21:29:55 <rbergeron> any other ec2-related stuff?
21:30:15 <jforbes> not from me
21:30:18 <gholms> !
21:30:54 <rbergeron> gholms: is that a yes?
21:30:57 <rbergeron> ;)
21:31:03 <gholms> Once we get some new images up would it be worth someone doing a blog post or something about how to use them so it'll hopefully show up on planet.fp.o?
21:31:12 <gholms> (or whatever it's called)
21:31:16 <jforbes> gholms: yup, will do
21:31:26 <gholms> Oh, great!
21:31:33 * gholms was going to volunteer  :)
21:31:35 <jforbes> should we blog the test though, or just the full images?
21:31:37 * rbergeron can tweet and dent about it.
21:31:45 <jforbes> gholms: you too, the more the better
21:32:15 <rbergeron> yep.
21:32:24 <rbergeron> +1 to that
21:32:26 <gholms> Something like "Here's how to launch Fedora on EC2:  install euca2ools, pick from the list on the wiki, ..."
21:33:38 <gholms> [Somewhere in the distance, a dog barks]
21:34:13 * rbergeron grins
21:34:38 * rbergeron votes for 'plz blog as you see fit'
21:35:03 <rbergeron> #action rbergeron to advertise blog posts via
21:36:14 <gholms> What's next?
21:36:16 * rbergeron shall move on
21:36:19 <rbergeron> #topic OpenStack
21:36:38 <rbergeron> silassewell isn't here, but I thought i'd just check in on his packages.
21:36:47 <rbergeron> hola, jdarcy.
21:36:53 <jdarcy> Hiya.
21:36:59 <rbergeron> #link
21:37:12 <rbergeron> specifically - looks like python-carrot needs a reviewer -
21:37:20 <rbergeron>
21:37:38 <rbergeron> gholms: does #help actually work with mr. zodbot
21:37:38 <rbergeron> ?
21:37:59 <gholms> rbergeron: It does if zodbot's code at all resembles upstream's.
21:38:18 <rbergeron> #help (python-carrot)
21:38:21 <rbergeron> cool.
21:38:24 <rbergeron> I guess we'll see shortly.
21:38:36 <rbergeron> Other than that - looks like ti's coming right along.
21:39:04 <rbergeron> #topic Any other business?
21:39:19 <rbergeron> jdarcy: you putting in any nice cloud-related features for f15? ;)
21:40:15 <jdarcy> rbergeron: some new features for GlusterFS - sort of CloudFS Lite.
21:40:23 <rbergeron> ah, yes.
21:40:23 <jsmith> If anybody is able to reproduce the HTTPD hang issue, please let Joe Orton know in the bugzilla ticket
21:40:34 <jdarcy> Just submitted my first full translator to them today.
21:41:10 <gholms> Damn, and I just bought that soda...
21:41:12 <mgoldmann> jsmith: I was able
21:41:20 <jdarcy> Not sure how much of CloudFS will make it into an F15 timeframe.  Maybe all but the multi-site replication.
21:41:23 <jsmith> mgoldmann: Did you report it?
21:41:42 <mgoldmann> no, one of our community members pointed that out and we tried to found the issue
21:41:46 <mgoldmann> I failed
21:42:08 <rbergeron> jdarcy: cool. anything major?
21:42:27 <jsmith> #link
21:43:07 <jdarcy> rbergeron: Auth*, encryption, some multi-tenancy, some internal improvements.  I'll put together an F15 feature page.
21:43:16 <rbergeron> woo. fun
21:43:24 <gholms> Sounds nice!
21:43:46 <jsmith> Are we getting Sheepdog in F15 as well?
21:43:52 * rbergeron hasn't looked at glusterfs in ages, though now i can't remember if i looked at it or lustre
21:43:52 * jsmith can't wait to play w/ all the goodies
21:44:00 <rbergeron> jsmith: yes, sdake is working on it
21:44:08 <jsmith> Cool :-)
21:44:23 <rbergeron> at least he was last time i asked him about it
21:44:26 <rbergeron> which I think was last week
21:45:12 <jdarcy> Maybe we should consider RBD (RADOS Block Device, uses the lower layer of Ceph) as well.
21:45:30 <rbergeron> jdarcy: thoughts on who might want to do that / have bandwidth?
21:45:32 * rbergeron goes and looks
21:45:45 <jdarcy> It's functionally similar to Sheepdog, same level/type of integration, and I've been pinged about it a couple of times.
21:45:49 <rbergeron> #info We might consider  RBD (RADOS Block Device, uses the  lower layer of Ceph) as well.
21:46:03 <jdarcy> Perhaps me, perhaps Josef Bacik.
21:46:04 <rbergeron> #action rbergeron to ping sdake about sheepdog for f15
21:46:09 * rbergeron nods
21:46:49 <jdarcy> IIRC it's essentially working, just needs to be packaged.
21:47:15 <mgoldmann> jsmith: added a comment to that bug report
21:47:23 <jsmith> mgoldmann: Thanks :-)
21:47:31 <rbergeron> #info jdarcy has submitted some stuff to glusterfs, and will be making a feature page
21:47:46 <mgoldmann> not very helpful, but at least more people are talking about it
21:47:51 <rbergeron> jdarcy: that might be interesting to check out.
21:47:58 <mgoldmann> hopefully we find the cause
21:48:04 * rbergeron is all about having more toys in the sandbox
21:48:49 <rbergeron> Anyone else have anything to discuss?
21:49:41 <gholms> [You hear the sound of distant drums]
21:49:45 * rbergeron waits for gholms to do something in brackets
21:49:51 <rbergeron> oh, there it is.
21:49:54 <gholms> \o/
21:49:57 <rbergeron> *grni*
21:50:02 <rbergeron> no! *grin* there we go
21:50:03 <gholms> Nice
21:50:27 <rbergeron> alrighty.
21:50:31 <rbergeron> Thanks for coming, everyone :)
21:50:41 <mgoldmann> thanks!
21:50:45 <rbergeron> #endmeeting