17:11:21 <rbergeron> #startmeeting Cloudy Docs Sprint
17:11:21 <zodbot> Meeting started Thu Sep 15 17:11:21 2011 UTC.  The chair is rbergeron. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:11:21 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
17:11:24 <rbergeron> #chair sparks
17:11:24 <zodbot> Current chairs: rbergeron sparks
17:11:30 <rbergeron> #meetingname Cloudy Docs Sprint
17:11:30 <zodbot> The meeting name has been set to 'cloudy_docs_sprint'
17:11:51 <Sparks> Okay, I'm going to skip the EC2 stuff as I think that's on the wiki
17:12:11 <Sparks> And I think I can probably do the CloudStack stuff (just guessing)
17:13:00 <Sparks> I guess what I'm missing is OpenStack, SheepDog, Aeolus, and BoxGrinder
17:13:12 <rbergeron> sparks: is that necessary? I mean - CS isn't in Fedora.
17:13:13 <rbergeron> yet.
17:13:16 * rbergeron looks at ke4qqq
17:13:23 <Sparks> It *will* be
17:13:28 <rbergeron> yes it will
17:13:30 <Sparks> If I have to package it myself
17:13:42 <rbergeron> okay. so let's start with.... boxgrinder
17:13:45 <Sparks> And it's available for Fedora... :)
17:13:45 <rbergeron> #topic BoxGrinder
17:13:49 <rbergeron> msavy: are you around?
17:14:09 <rbergeron> So - sparks, what are we filling in right now?
17:14:20 <rbergeron> the beat or more looking for guide stuff or just looking for where to find things?
17:14:38 <Sparks> Yes
17:14:44 <rbergeron> There are a few cases I'd think would be good here.
17:14:44 <Sparks> The Guide is blank at the moment
17:14:58 <Sparks> So we can start with beat information and I can continue the research
17:15:03 <rbergeron> #idea Boxgrinder basics - what it is, how it works, etc.
17:15:19 <rbergeron> #idea Using BoxGrinder to create a Fedora image
17:15:42 <rbergeron> #idea Using the BoxGrinder/Fedora AMI on EC2 to create a Fedora instance on Amazon
17:15:56 <rbergeron> the third one is ... ehhh. might need to ask mgoldmann/msavy for help.
17:16:02 <rbergeron> let me see if i can find some docs on it real quicklike.
17:16:16 <rbergeron> #link http://boxgrinder.org/
17:16:37 <rbergeron> #link http://boxgrinder.org/tutorials/boxgrinder-build-usage-instructions/
17:16:40 <jsmith> rbergeron: OK, I'm updating the Cloud Guide outline with that information in real-time :-)
17:16:49 <Sparks> jsmith: You rock!
17:16:55 <rbergeron> #link http://boxgrinder.org/tutorials/
17:17:54 <rbergeron> #idea go into some of the details about OS options, platform plugins, delivery plugsins
17:18:08 * gholms wanders in with a bewildered look on his face
17:18:08 <rbergeron> #info Some of this info may be well-written out already in BG documentation
17:18:17 <rbergeron> gholms: helping docs out with what to document
17:18:48 <rbergeron> #info OS plugins - rhel, fedora, centos (various version)
17:19:04 <rbergeron> #info Platform plugins - virtualbox, vmware, ec2
17:20:15 <rbergeron> #info Delivery platforms (where it can get delivered AUTOMAGICALLY) - EBS, cloudfront for S3, sftp, ami for s3, local filesystem, s3 for s3
17:20:33 <rbergeron> #idea Connive spevack into writing up some documentation or something about What All These Different Amazon Things Are
17:21:11 <Sparks> +1
17:22:15 <rbergeron> That's about the end of my train on BoxGrinder
17:22:24 <Sparks> Okay, that's a good dump for that.
17:22:30 <msavy> rbergeron: yah, whats up
17:22:30 <rbergeron> gholms, msavy, anyone else think i'm missing anything there
17:22:38 * msavy reads back
17:22:40 <rbergeron> msavy: sparks is working on the Fedora Cloud guide
17:22:50 * gholms is still reading through scrollback
17:22:51 <rbergeron> sparks: can you link where it's at
17:23:04 <rbergeron> msavy: basically just want to have some at least basic info in it about how to use BG
17:23:07 <jsmith> Sparks, rbergeron: I just pushed the latest changes to the outline
17:23:12 <rbergeron> so I was giving him just a bit of framework to go off of
17:23:12 <Sparks> #link https://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html
17:23:16 <rbergeron> so we can start getting people to fill in
17:23:25 <jsmith> Sparks: You wanna push the latest changes?
17:23:28 <Sparks> That's the draft version.
17:23:41 <msavy> ok, boxgrinder is super simple to use. Any time you want information or contributions feel free to ask.
17:23:54 <Sparks> jsmith: Ummm...  Well, it won't get updated until the top of the hour.
17:23:54 <rbergeron> #info BG guys hang in #boxgrinder
17:24:29 <gholms> How is ceph related to the cloud?
17:24:41 <Sparks> gholms: It is and there's a section for it.
17:24:52 <gholms> Sparks: That doesn't answer my question.
17:24:59 <Sparks> gholms: I believe I stuck it under File Systems
17:25:06 <rbergeron> gholms: ask ke4qqq, it was his idea
17:25:17 <gholms> The "Storage in the Cloud" section
17:25:20 * rbergeron doesn't get to throw ke4qqq under the bus enough
17:25:22 * jsmith has to run, but will be back later
17:25:30 <gholms> ke4qqq: You around?
17:25:34 <Sparks> jsmith: Cool.  TU.  I'll grab the source soon.
17:25:43 <gholms> ke4qqq: Trying to figure out what makes ceph cloud-related
17:26:20 <rbergeron> gholms: they'r eintegrated with some stack these days... cloudstack or openstack
17:26:36 <rbergeron> and i think some integration with kvm somehow
17:26:52 <gholms> cluster != cloud
17:27:07 <gholms> If they were the same then DRBD and Hadoop would also be in the list.
17:27:27 <gholms> need to be, rather
17:27:36 * Sparks notes the list isn't complete/final
17:27:49 <kkeithley> As I understand it, Ceph is an object store, like EMC Atmos or a bit less like EMC Centera. Industry seems to think of them as cloud storage.
17:29:05 * gholms reads their page again
17:29:33 <gholms> Aaand their wiki is broken. Awesome.
17:29:38 <rbergeron> WINNING
17:29:45 <gholms> Heh
17:29:50 <Sparks> rbergeron: Want to move on to the next topic?
17:30:02 <ke4qqq> gholms: I am
17:30:10 <gholms> Oh crap, sorry for hijacking the topic. :|
17:30:35 <rbergeron> gholms: no worries
17:30:35 <ke4qqq> ceph can do more than object storage......
17:30:37 <Sparks> gholms: You didn't!  I'm looking for any and all information to put into the guide.
17:30:41 <ke4qqq> it can do real filesystem as well
17:30:57 <ke4qqq> it's a hazy-cloudy-relationship
17:31:11 <rbergeron> do we not have a FS guide? is there any way we should link those two to oneanother (or at least point to FS guide from cloud guide)?
17:31:20 <gholms> So it's a distributed filesystem. What does that have to do with cloud?
17:31:40 <Sparks> rbergeron: We don't have a FS guide
17:31:47 <gholms> Don't get me wrong; it's a great sort of thing to have in one's datacenter.
17:31:49 * rbergeron will let ke4qqq and gholms argue over semantics and move on to HekaFS since she just saw kkeithley wander in
17:31:52 <Sparks> rbergeron: There is a chapter in the CG for FS
17:31:54 <rbergeron> #topic HekaFS
17:31:59 <rbergeron> sparks: excellent
17:32:04 <rbergeron> so... HekaFS
17:32:11 * rbergeron looks at some of the links kkeithley has sent out lately, plz hold
17:32:31 <Sparks> rbergeron: I think I got a bunch of stuff in HekaFS based on a wiki post
17:32:44 * Sparks doesn't think he published that, though.
17:33:08 <rbergeron> okay. Soooo
17:33:09 <gholms> rbergeron: FWIW, such semantics determine whether or not it even belongs in a cloud guide.  Still better to discuss it later, though. ;)
17:33:16 <Sparks> #link https://fedoraproject.org/wiki/HekaFS
17:33:20 <ke4qqq> gholms: in the old days you'd have called things like ceph cluster-releated....and that's sorta morphed into cloud. /me isn't opposed to yanking it, but do you really want to use non-distributed FSs with your distributed cloud?
17:33:32 <rbergeron> well i realize now that "semantics" has such a nasty sound to it when i used it in the sentence, but i wasn't meaning to downplay your discussion
17:33:43 <rbergeron> just trying to get other things captured as well without ratholing, but by all means - discuss!
17:33:52 <kkeithley> #link https://fedoraproject.org/wiki/SimpleHekaFS ksa
17:33:54 <gholms> Let's focus on hekafs first. :)
17:34:25 <kkeithley> s/ksa/is a how-to set up a simple hekafs cluster/
17:34:47 <Sparks> kkeithley: What's the difference betwen Simple HekaFS and HekaFS?
17:35:27 <kkeithley> HekaFS page is just an overview of HekaFS. SimpleHekaFS is a step-by-step guide to setting it up
17:35:30 <ke4qqq> Sparks: amount of effort
17:36:25 <Sparks> ke4qqq: Are you saying that one is... simple?
17:36:32 <Sparks> Ahhh
17:36:42 <kkeithley> it's a how-to for setting up a simple cluster
17:36:43 <Sparks> kkeithley: Awesoe
17:36:50 <Sparks> Awesome even
17:37:15 <gholms> Nice guide!
17:37:58 <kkeithley> Eventually I write a how-to for more complex set-ups.
17:38:05 <kkeithley> s/I/I'll/
17:39:59 * rbergeron nods
17:40:33 <rbergeron> i mean, we probably want to note that it sits on top of glusterfs (AIUI)
17:40:41 <Sparks> Okay, so I can probably grep those two pages for information
17:40:43 <rbergeron> and get some of those links, but i tihnk kkeithley has that all pretty well documented in here
17:40:48 <rbergeron> yeah, there's a ton in here.
17:40:50 <kkeithley> yup, hekafs is a layer on top of glusterfs
17:40:59 <rbergeron> #info hekafs is a layer on top of glusterfs
17:42:21 <rbergeron> hang on. i'm fillin gmy caffeine bucket
17:43:03 <gholms> rbergeron: What, did you notice some blood going through your caffeine vessels? :P
17:43:10 <rbergeron> i know, it's weird.
17:43:12 <rbergeron> mdomsch :)
17:43:43 <rbergeron> Okay.
17:43:54 <rbergeron> gholms: esp. since i don't have a heart
17:43:56 <rbergeron> and all that
17:45:00 <mdomsch> better late than never
17:45:03 <rbergeron> indeed.
17:45:07 <rbergeron> okay, so what's next?
17:45:12 <rbergeron> #topic OpenStack
17:45:21 <rbergeron> ah, so weird without zodbot.
17:45:24 <Sparks> Yeah, that's a good one to do
17:45:27 <rbergeron> Okay, so I know markmc has written up a few things.
17:45:31 <rbergeron> more specific to fedora.
17:46:44 * rbergeron looks
17:47:06 <rbergeron> well, let's see here
17:47:34 <rbergeron> #link https://fedoraproject.org/wiki/Features/OpenStack
17:47:53 <rbergeron> #link https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova
17:48:16 <rbergeron> so a few things to know:
17:48:36 <rbergeron> #info OpenSTack has a few individual pieces that we have right now that can be documented individually if we want - Nova, Swift, and Glance
17:48:49 <rbergeron> and to give the "for dummies version" since that's about all i know -
17:49:20 <rbergeron> #info Nova is management/UI/deploying of things, Swift is object storage, and Glance is image creation
17:49:27 * rbergeron waits for someone to correct her
17:50:02 <rbergeron> sparks: this will probably be of immense help
17:50:06 <rbergeron> #link http://docs.openstack.org/
17:50:36 <gholms> Doesn't nova manage the VMs as well?
17:50:36 <zoglesby> talking docs without me? how rude!
17:51:15 <Sparks> rbergeron: Yeah, this should be good.
17:51:48 <rbergeron> that's what i meant by management
17:51:53 <rbergeron> zoglesby: :)
17:52:04 <rbergeron> okay. soooo moving on then
17:52:08 <gholms> !
17:52:10 <rbergeron> #topic Aeolus
17:52:12 <rbergeron> #undo
17:52:12 <zodbot> Removing item from minutes: <MeetBot.items.Topic object at 0x17322e0c>
17:52:15 <rbergeron> yes?
17:52:28 <gholms> Something in that guide needs to tell you where to get the euca-* commands from?
17:52:33 <gholms> s/?/./
17:52:40 <gholms> I can't type today. :/
17:53:04 <rbergeron> gholms: which guide? the openstack guide?
17:53:10 <rbergeron> or just the cloud guide needs euca-related love?
17:53:11 <gholms> https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova
17:53:42 <Sparks> #link https://fedoraproject.org/wiki/Getting_started_with_OpenStack_Nova
17:53:44 <rbergeron> #info openstack getting started guide needs to tell you wheree to get the euca-* commands from
17:53:45 <gholms> You need euca2ools to use bits of nova, so I figured it might be good to mention that that has to be installed at some point.
17:53:48 <gholms> That's all.
17:54:00 <Sparks> gholms: Good stuff.
17:54:04 <rbergeron> gholms: Shall we make euca2ools a separate piece in the guide?
17:54:15 <rbergeron> since I know that Euca will be coming our way fully at some point in future releases?
17:54:37 <gholms> rbergeron: It doesn't really warrant its own section since it's only used in conjunction with things like AWS and Nova.
17:54:50 <gholms> ...which have their own sections.,
17:55:25 <Sparks> I should be able to duplicate some text in each section discussing Euca
17:55:39 <Sparks> Write once... translate once...  read twice
17:56:02 <gholms> Perhaps, though I suspect that ``yum install euca2ools'' is about all the duplication you're going to get.
17:56:12 <gholms> That's up to you, though. ;)
17:56:22 * gholms returns to his hole
17:56:23 <rbergeron> I mean, i think even having something basic like "wtf is euca2ools" might be useful
17:56:41 <Sparks> gholms: Just thinking about the usage of Euca
17:56:55 <rbergeron> #idea Having at least some basic info about what is euca2ools might be useful, at least WRT sections on AWS and Nova
17:57:19 <gholms> That's an idea.  If you think it would be useful then go for it.
17:57:27 <rbergeron> okay.
17:57:27 * gholms can answer questions
17:57:38 <rbergeron> #info gholms can answer euca-related questions if needed.
17:57:42 <rbergeron> okay. thanks :)
17:57:44 <rbergeron> #topic Aeolus
17:58:04 <rbergeron> So aeolus has not quite as replete documentation, but at least has some basic usage information.
17:58:11 <rbergeron> #link http://aeolusproject.org/use_it.html
17:58:46 <rbergeron> #info Aeolus is made up of a bunch of different pieces - Audrey, Conductor, Configure, ImageFactory, Image Warehouse, Oz, Spherical.
17:58:55 <rbergeron> I'm not entirely sure if ALL the pieces are in. I'll check.
17:59:05 <rbergeron> mmorsi: ping
17:59:47 * rbergeron just went and pinged clalance
17:59:58 <clalance> rbergeron: Hello :)
18:01:24 <rbergeron> hey.
18:01:33 <rbergeron> clalance: so there are like... a bunch of projects in aeolus
18:01:41 <clalance> There are?
18:01:43 <rbergeron> Audrey, Conductor, Configure, ImageFactory, Image Warehouse, Oz, Spherical is the list i see on the page.
18:01:44 <clalance> (I kid, I kid)
18:01:47 <rbergeron> Well.
18:01:48 <rbergeron> :)
18:01:56 <rbergeron> Are those *all* in Fedora? Or only some?
18:02:03 <clalance> rbergeron: You can drop spherical.
18:02:06 <clalance> We aren't using it for anything.
18:02:30 <clalance> rbergeron: All of the rest except for Audrey are in Fedora.
18:02:52 <rbergeron> okay. So:
18:03:08 <rbergeron> #info Pieces of Aeolus used in Fedora are Conductor, Configure, ImageFactory, Image Warehouse, Oz.
18:03:23 <clalance> Exactly.
18:03:51 <rbergeron> clalance: is there any draft documentation anywhere other than what is in the useit link on the aeolusproject.org page?
18:04:24 <clalance> rbergeron: I'm honestly not sure.
18:04:31 <clalance> rbergeron: I can point you to the (small) pieces I know about.
18:04:36 <clalance> rbergeron: There is the Use It stuff.
18:04:39 <rbergeron> clalance: that would be very helpful
18:04:41 * rbergeron nods
18:04:57 <clalance> rbergeron: There is also the Oz documentation: http://aeolusproject.org/oz.html
18:05:00 <clalance> (and sub-pages)
18:05:04 <clalance> And then we have wiki pages.
18:05:16 <rbergeron> #link OZ Documentation - http://aeolusproject.org/oz.html
18:05:16 <clalance> Which are wiki pages, so are in various states of badness :).
18:05:29 <clalance> rbergeron: The right person to ask here is jclift.
18:05:49 <rbergeron> #info jclift (justin clift, aeolus comm. mgr) is probably the right person to ask.
18:06:06 <rbergeron> sparks: we may wnat to see if there are basic definitions for what all those bits do individually, for poeple's references
18:06:13 <Sparks> Okay
18:06:55 <rbergeron> clalance: thanks :)
18:06:58 <rbergeron> sorry to harass
18:07:04 <rbergeron> just having a bit of hackfest fun here
18:07:26 <rbergeron> #topic Sheepdog
18:07:42 <clalance> rbergeron: No problem at all, happy to help.
18:07:48 <rbergeron> #link http://www.osrg.net/sheepdog/
18:08:07 <rbergeron> #link https://fedoraproject.org/wiki/Features/Sheepdog
18:08:33 <rbergeron> #link https://github.com/collie/sheepdog/wiki
18:09:11 <rbergeron> #link https://github.com/collie/sheepdog/wiki/Getting-Started
18:09:28 <rbergeron> sparks: there is stuff in there about installing corosync, and that is already available in fedora due to this guy i live with
18:09:59 <rbergeron> just as an FYI in case you were going to look
18:10:07 <Sparks> rbergeron: Okay.
18:10:40 <rbergeron> #topic Anything else?
18:10:55 <Sparks> I think that's a pretty good start
18:10:55 <rbergeron> clalance: opinions on condor-cloud and documentation?
18:11:10 * rbergeron wonders about matahari as well but doens't think it's highly applicable but may go harass russellb aobut it
18:11:13 <rbergeron> oh wait
18:11:15 <rbergeron> russellb is here
18:11:19 <rbergeron> russellb: HI
18:11:30 <clalance> rbergeron: Sorry, that's also mostly out of my domain.
18:11:38 <clalance> rbergeron: Ian Main is your man there.
18:11:40 <clalance> (Slower on IRC)
18:11:48 <clalance> Let me see if I can fetch him.
18:11:49 <russellb> rbergeron: hi.
18:12:00 <rbergeron> russellb: We're hacking a bit on what should be in the Fedora Cloud guide
18:12:06 <rbergeron> wondering about matahari
18:12:15 <rbergeron> ...since it's a feature
18:12:24 <rbergeron> and if it really belongs in the cloud guide, or not so much
18:12:39 <russellb> well, cloud is certainly one of the primary driving use cases.
18:12:46 <rbergeron> while noting that we're all over the place between hekafs and amazon and openstack and aeolus
18:13:01 <russellb> it's certainly a developer focused feature, lower level type thing
18:13:10 <russellb> i'm not sure what the intended scope of the guide is
18:13:38 <Sparks> russellb: To document cloud stuff in F
18:13:43 <rbergeron> Basically - how to use any of the cloud-related things in Fedora.
18:13:45 <rbergeron> http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/Cloud_Guide/index.html
18:13:48 <rbergeron> Which i know is vague
18:13:49 <russellb> ok.
18:13:52 <rbergeron> but either (a) how to use fedora in a cloud
18:13:57 <rbergeron> or (b) how to use fedora to build a cloud
18:14:08 <rbergeron> or (c) how to use fedora in your cloud
18:14:10 <rbergeron> oh wait
18:14:12 <rbergeron> that's a
18:14:14 <rbergeron> yeah.
18:14:24 <rbergeron> You get the picture. :)
18:14:24 <russellb> so, it'd probably be good to put something in about tools you can use to manage fedora systems deployed in a cloud.
18:14:34 <rbergeron> Yup.
18:14:36 <russellb> and you could link to our manual, which is ... a work in progress :-)
18:14:44 <Sparks> url?
18:14:44 <russellb> http://matahariproject.org/manual/
18:14:53 <Sparks> #link http://matahariproject.org/manual/
18:14:59 <Sparks> Awesome
18:15:00 <rbergeron> #info Matahari would be good for "tools you can use to manage fedora systems deployed in a cloud"
18:15:27 <Sparks> rbergeron: I think that's probably a good start.
18:16:19 <clalance> rbergeron: Sorry, I'm not getting a response from Ian.
18:16:26 <clalance> rbergeron: I'll send him mail asking him to contact you.
18:16:34 <clalance> (or someone else, if you prefer)
18:17:03 <rbergeron> clalance: no worries. yeah, actually just the cloud mailing list would be fine, I think, unless sparks has a better thought.
18:17:12 <rbergeron> Or you could send him directly to sparks
18:17:29 <clalance> rbergeron: What's sparks email?
18:17:36 <Sparks> sparks@fp.o
18:17:42 <clalance> Sparks: Thanks.
18:18:08 <Sparks> Thank you!
18:18:34 <rbergeron> #info Still outstanding - need info from Ian Main (slower on irc) re: condor cloud
18:18:38 <rbergeron> Okay. What's left?
18:18:54 <rbergeron> Oh.
18:19:13 <rbergeron> #topic How to get Fedora for use on EC2
18:19:32 * clalance runs away
18:19:36 <clalance> That is always a long discussion ;).
18:19:40 <rbergeron> clalance:
18:19:45 <rbergeron> I mean if it's already there :)
18:19:51 <rbergeron> ASSUMING there is a working AMI
18:19:56 <rbergeron> what do I do with it and what can i do with it
18:20:01 <clalance> Ah, righto.
18:20:02 <clalance> Haha.
18:20:04 <rbergeron> Far simpler.
18:20:15 <rbergeron> No drama.
18:20:18 <rbergeron> Not today anyway.
18:20:45 <rbergeron> #info We have AMIs for Fedora (knock on wood) published to EC2.
18:20:55 <rbergeron> #idea How do we find them, where do we get the information?
18:20:55 <gholms> Start up a VM, log into it, and use it like any other server? :P
18:21:32 <rbergeron> #idea How do I get a vm started, what can i use it for, what are all these various AWS services
18:21:55 <rbergeron> #idea Troll Max Spevack at all possible opportunities
18:22:59 <gholms> Well, what you can use a VM for is already known.
18:23:17 <gholms> What you can use the *cloud* for revolves around building entire applications.
18:23:35 <gholms> Just sayin'
18:23:38 <rbergeron> gholms: pretend, for a second, that you are dumb and heard about this ec2 thing and it sounds cool. So just pretend you are me and you dont even know where to start. :)
18:24:15 <rbergeron> Now, that said, I think having some information about the various interpretations of cloudiness and *aaS acronyms and so forth might be helpful for people in general in the guide
18:24:31 <Sparks> rbergeron: I have a hard stop in about five minutes...
18:24:43 <rbergeron> sparks: as do I, i'm hungry
18:24:50 <rbergeron> i guess that's not entirely a hard stop but i am starvin' marvin
18:25:03 <zoglesby> rbergeron: that is a hard stop
18:25:16 <zoglesby> the first F in the 4 Fs is really Food
18:26:11 <rbergeron> LOL.
18:26:12 <rbergeron> okay.
18:26:15 <rbergeron> Sooooooooooooooooooooooooooooooooooooooooooooo
18:26:24 * rbergeron looks at gholms for more commentary
18:26:41 * gholms produces a bottle of mustard
18:27:31 * zoglesby can derail a meeting like no other
18:28:00 <rbergeron> okay.
18:28:04 * rbergeron will close out in a minute
18:28:06 <gholms> There's one thing that sticks out in my mind:
18:28:10 <rbergeron> yes?
18:29:06 <gholms> The answer to, "What can I do with an instance in EC2 once I have started it?" is exactly the same as the answer to, "What can I do with a virtual server?"
18:29:31 <rbergeron> Run irssi in screen, right?
18:29:33 <rbergeron> :D
18:29:36 <gholms> Yeeessss
18:29:45 <Sparks> Did I hear Drupal instance?
18:29:52 <gholms> The fact that it happens to be running in EC2 doesn't make it special.
18:29:54 <zoglesby> for way more then the price of a linode vm
18:30:40 <russellb> "don't confuse marketing with reality"
18:30:58 <gholms> The before-and-after bits revolving around launching them and destroying them are definitely EC2-specific, but the "What can I do with it?" answer doesn't change.
18:32:02 * gholms is tired; sorry
18:32:13 <gholms> Time to break for lunch?
18:32:31 * Sparks is out.
18:32:52 <Sparks> rbergeron: Thanks for getting this going.  I'll collect the notes later this evening and try to start putting it all together.
18:33:16 <Sparks> zoglesby jsmith: And I'll publish the next version of the guide to docs.fp.o as well.
18:33:23 <russellb> do doc peeps, what do you use to edit docbook?
18:33:29 <russellb> the app i've been using is non-free ...
18:33:35 <Sparks> russellb: I use vim
18:33:36 <russellb> s/do/so/
18:33:52 <zoglesby> russellb: emacs!
18:34:01 * Sparks was waiting for that
18:34:16 <zoglesby> Sparks: let me know what you need help with
18:34:25 <Sparks> zoglesby: Sanity
18:34:29 <zoglesby> I am free sat to hack
18:34:36 <Sparks> Okay.
18:34:57 <zoglesby> though I may be playing with boxgrinder and html
18:37:57 * rbergeron wonders if she can endmeeting? :)
18:40:15 <rbergeron> #endmeeting