21:00:49 #startmeeting Cloud SIG 21:00:49 Meeting started Thu Feb 10 21:00:49 2011 UTC. The chair is rbergeron. Information about MeetBot at http://wiki.debian.org/MeetBot. 21:00:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 21:00:50 abadger1999: +1 21:00:55 #meetingname Cloud SIG 21:00:55 The meeting name has been set to 'cloud_sig' 21:01:12 #topic Roll Call! 21:01:16 Who's about? 21:01:21 * jforbes is about somewhere 21:01:28 * clalance is here. 21:01:44 yo 21:01:46 * jsmith is lurking 21:02:05 clalance :) 21:02:13 jforbes, clalance, jdarcy. :) 21:02:16 * rackerhacker chirps 21:02:21 oh, clalance gets 2 smiles. 21:02:30 * rbergeron meant that smiley for brianlamere. and rackerhacker. 21:02:38 Haha. 21:02:39 * rbergeron kicks her computer for being odd and laggy 21:02:40 * mmorsi says hi 21:02:41 I'm special ;). 21:02:50 * skvidal is here 21:03:19 * rbergeron waves at skvidal 21:03:24 * ke4qqq is here 21:03:30 who? :) 21:03:38 rbergeron: when it is just one finger it is not a "wave" 21:03:55 * jforbes kicks himself for being odd and laggy... 21:03:56 skvidal: one finger means I care for you deeply. really. 21:04:02 jgreguske! 21:04:05 hi! 21:04:11 forgive my tardiness 21:04:13 it's my special way of being excellent to you :) 21:04:15 hi jgreguske :) 21:04:18 #topic EC2 21:04:23 jforbes: take it away 21:04:33 * rbergeron will note that she filed a ticket for a test day :) 21:04:35 jgreguske: should I be able to build images in koji again? 21:04:44 doesn't it mean you think he's number one? 21:04:47 rbergeron: indeed you did, thanks :) 21:05:02 jforbes: I love filing tickets. 21:05:07 jforbes: you *should* be able to, however not just yet because of tune2fs breaking 21:05:30 jgreguske: any ETA on the fix? 21:05:51 jforbes: I have a dirty workaround but dgilmore said he was going to do a little testing himself 21:06:00 okay 21:06:00 brianlamere: everyone already knows that about skvidal :) 21:06:30 dgilmore: I know you're busy with the f15 branch... when do you think you'll get to testing appliance-tools as well? 21:07:05 the dirty workaround is to mount all of /dev in the chroot rather than just /dev/{mapper,shm,pts} 21:07:19 we could hotfix a koji builder to do that in an image build 21:07:40 but it's dgilmore's call I think 21:07:59 jgreguske: hopefully before the weekend 21:08:05 okay, cool 21:08:13 when is alpha release? 21:08:20 3-1 21:08:28 i think 21:08:28 jf march 1 21:08:33 Right, so we have a little bit of time 21:08:35 jforbes: march 1 21:08:36 yes, i knew it! 21:08:37 we've got time, but I totally understand jforbes' desire to check a box off :) 21:08:42 freeze is in 2 weekd 21:09:07 so we really only have 2 weeks to fix it 21:09:31 dgilmore: which freeze? 21:09:49 rbergeron: code/infra etc 21:09:59 Well, I still have to test changes to the publsh script... I am not 100% confident that euca2ools works as documented there 21:10:06 infra is next week on the 15th 21:10:12 as is string freeze, etc 21:10:21 jforbes: FYI, we've been using it in aeolus, and it does seem to work for us. 21:10:27 (though our use-case is kind of constrained) 21:10:34 maybe ive been looking at the wrong schedule 21:10:39 jforbes: There are some slight differences in behavior from ec2-ami-tools. 21:11:24 dgilmore: everything is on the Schedules wiki page - or here - http://rbergero.fedorapeople.org/schedules/f-15/ 21:11:26 clalance: yeah, I have used it from the command line some... Just need to make sure the scripts do what I expect. 21:12:49 * rbergeron wonders if there is anything that she should be actioning people on here or if she should just sit back in her lounge chair and watch 21:13:31 I think we are good on actions, the koji bit has to be fixed for more than just ec2. I believe it is also used for spins 21:13:45 * rbergeron nods 21:13:56 Okay. Anything else in ec2-land going on 21:13:57 ? 21:14:04 jforbes: its only effecting appliance creation 21:14:15 nopr 21:14:16 i used koji last night to make the tc1 livecds 21:14:21 livecd generation goes down a different code path in imgcreate 21:14:26 Hmm, okay 21:14:39 jforbes: granted f14 is broken for another reason... 21:14:45 but f15 works as far as I know 21:15:06 I think dgilmore had some success with it recently 21:15:36 jgreguske: yeah, dont think F14 will be fixed in koji 21:15:57 jforbes: it just requires a fix in f15 be backported to f14 I think 21:16:06 right 21:16:09 at the livecd-tools level 21:16:26 jforbes: is f14 a priority? I figured f15 was the Big Deal 21:17:14 jgreguske: f15 is the big deal 21:17:18 jforbes: if we really want updated f14 images we need to backport a patch 21:17:39 Well, we can do f14 images another way, though it would be nice to use koji for them 21:18:39 jforbes: we can fix f14 too, we'll handle it :) 21:18:51 nice :) thanks 21:18:54 dgilmore: may ping you tomorrow on that, I can help 21:19:13 ok, I'm going to say it - Fed14 will likely be more stable than 15. Heck, lots of conversations about that at FudCon - how some releases are more conservative than others 21:19:22 jforbes: its doable just needs doing 21:19:22 so a 14 fix would be nice ;) 21:20:39 brianlamere: I would be less concerned about f15 stability on the appliance level... gnome3 is the big shakey piece 21:21:16 heh 21:21:17 It would be weird if every release turned out to be exactly as stable as the others. 21:21:23 brb 21:21:40 jforbes: hmm...ok, yeah, true 21:21:42 jforbes: Well, the other bit is systemd. 21:22:03 clalance: and less upstart as a result? sign me up :P 21:22:18 Heh, I think it is a good move, but also a potentially destabilizing one. 21:22:20 (just saying) 21:22:25 clalance: sure, but I expect it will be less problematic in this context b release time. 21:22:34 Yeah, probably. 21:22:48 Shall I move on? :) 21:23:13 rbergeron: sure 21:23:38 sweet. 21:23:41 #topic CloudFS 21:23:49 This will be a short section. 21:23:55 :) 21:24:16 I requested that CloudFS *not* be included in F15, as I felt I had essentially missed the deadline to come up with something sufficiently useful+usable. 21:24:31 FESCo approved the request, so it'll be retargeted for F16. 21:24:39 :( 21:24:48 jdarcy: are you leaving the code in for people to test/play with? 21:24:52 Work continues though. New dev starting next week. I'm still excited about it. 21:25:16 hey obino :) 21:25:18 The project goes on. It just won't be released in time for F15. 21:25:29 that's unfortunate; it's a great use of the ephemeral storage which I can't otherwise touch because it's...ephemeral. heh 21:25:37 hi rbergeon, I'm late as usual :( 21:25:46 brianlamere: You can still use what's there, it's just kinda rough. 21:25:49 obino: no worries 21:26:14 I think the F16(ish) release will rock. 21:26:27 :) 21:26:44 anything else? 21:26:51 jdarcy: I'm a bit confused... are we still going to have packages as a "tech preview"? 21:26:53 Nope. Just thanks to everyone. 21:26:53 * rbergeron shall look forward to seeing you at the meetings in the meantime of course :) 21:27:01 jdarcy: Or does it just need more time to cook? 21:27:24 jsmith: I think it just needs more time to cook. The feedback I've gotten has been great, I see a clear path to making things *way* better. 21:27:31 Cool. 21:27:35 Thanks for the clarification :-) 21:27:42 jsmith: I think the definition around "tech preview" really needs more definition for people to feel comfortable doing something like that... at least IMO :) 21:28:24 #topic Aeolus / Deltacloud 21:28:36 clalance, mmorsi: Are you bringing me something awesome for F16? :) 21:28:39 rbergeron: Traditionally, "tech preview" means "It's in there, it's not installed by default, but people can play with the packages as they exist." 21:28:48 rbergeron: (We can take futher discussion offline) 21:28:52 s/futher/further/ 21:29:02 rbergeron: That is the plan. 21:29:11 rbergeron: We got closer this week with mmorsi pushing rails 3 into F-15. 21:29:24 jsmith: by that definition, all of virt is tech preview :) 21:29:24 * rbergeron saw. it's in! 21:29:31 jforbes: :) 21:29:53 rbergeron: Let's see, other than that... 21:30:06 rbergeron: You saw I released the first version of Oz late last week. 21:30:14 indeed. thanks for sending that to the list. 21:30:15 (since there was interest in that stand-alone) 21:30:26 * gholms walks in 21:30:34 Image Factory (which uses Oz underneath) is probably also going to have a release soon. 21:30:57 The UI itself *is* stabilizing; the sprint ends next week, and I think we should have packages then. 21:31:06 * rbergeron just wants to make sure that people know that there are always new releases just around the corner - and wiating till f15 is out the door isn't as efficient as just continuing to plow forth on things. :) 21:31:08 (still very early alpha stuff, but at least installable) 21:31:16 Oh yeah, definitely. 21:31:18 (I'm pretty sure you are all aware of that, but, you know. :D) 21:31:25 We host our own repos for stuff that is not yet in Fedora. 21:31:31 as always you can install the latest / greatest from our yum repo 21:31:45 http://repos.fedorapeople.org/repos/aeolus/packages/ 21:31:50 * rbergeron nods 21:32:06 clalance: it would be easy to include some of that in the virt-preview repos as you start to stabalize for F16 21:32:06 yum install deltacloud-configure from there and then 'deltacloud-configure' and you should be good to go 21:32:21 I really like the updates that you guys post to the list. It's really helpful for us to know what's going on, etc. :) 21:32:23 jforbes: Good point. Though I'm not sure whether it belongs there. 21:32:31 (it is semantically a layer on top of virt) 21:32:56 clalance: yeah, just happens to be a simple place to track 21:33:05 Yeah, true. 21:33:21 I just don't want to confuse the current virt-preview users. 21:33:27 But when we have packages, we can discuss further. 21:33:48 Anything else? :) 21:34:00 * rbergeron moves along 21:34:06 #topic Eucalyptus 21:34:10 * rbergeron looks at obino and gholms 21:34:19 lol 21:34:21 * rbergeron figured she'd just ask what's in the works for the future 21:34:24 :D 21:34:36 * gholms looks up 21:34:43 Oh, lol 21:34:46 You guys have any magical F16 plans? :) 21:34:53 I mean, I love having you here either way. 21:35:00 But. :) 21:35:11 * rbergeron is wondering if you guys are thinking about it. 21:35:16 I got Eucalyptus building against F14 yesterday. 21:35:48 it's hard for us to do plan: we are in freezing mode for a release 21:36:00 It's still littered with bundled java libs, so once the next release gets out the door that'll be on my agenda to fix. 21:36:06 my plan is to start populating the wiki page for Eucalyptus 21:36:18 with gholms help of course :) 21:36:24 :) 21:36:34 Cool. 21:36:36 * obino codeword for gholms will do the job and I'll drink coffee 21:36:44 lol 21:37:00 a quick google didn't give me a euca2ools roadmap; either of you have such? curious how it might be expanding in the future 21:37:00 gholms: hosting a yum repo for itsomewhere? 21:37:00 is that like when I throw someone under the bus? :) 21:37:03 I'd rather have you police the forums anyway. 21:37:35 * rbergeron thinks it's amazing how ke4qqq pops in right when i start talking about throwing people under the bus 21:37:39 :) 21:37:50 rbergeron: You're reading into it too much. 21:38:09 Ah, darnit 21:38:14 ke4qqq: We will be. Up until yesterday all the builds were against F12 because no one knew how to fix linkage failures due to F13's linker change. 21:38:24 gholms: cool 21:38:36 brianlamere: I think the plan is to expand compatibility 21:39:01 anything in particular you were looking for? 21:39:18 Long story short, the person next to me is working on revamping the way we do repos and builds right now, so we can hopefully expect F13 packages some time this month. 21:39:45 Yeah, you: the person staring at my screen right now. 21:39:48 Stop being so creepy. 21:40:07 * rbergeron raises an eyebrow at the creepy person 21:40:12 :) 21:40:15 well, I was curious about the other toolsets too - such as route53, rds, etc. Easier in how-to guides to tell people how to use a public tool versus mine which I can't generally give out 21:40:26 * skvidal wonders if gholms is talking to his "friend" who the rest of us can't see 21:40:49 skvidal: In this case it's the person sitting next to me who is setting up the new repo layout we're going to use. 21:41:04 gholms: can the rest of us see this person if you are not in the room? 21:41:18 Yeeesss... 21:41:20 ;) 21:41:21 lol 21:41:37 If not then she's getting paid a lot more than she should be. 21:41:40 OKAY THEN 21:41:44 :) 21:41:49 :P 21:42:00 oh, brianlamere had a question - i guess i'll wait on that before i move on 21:42:11 or maybe a question/statement 21:42:48 As I pull deps out of Eucalyptus I'm going to make rpms out of them and submit them for review to Fedora in whatever order makes sense. Once I finally have enough to build on Fedora I'll start worrying about making EPEL branches for everything. 21:43:04 well yeah - just whether we can expect expansions to things outside of ec2-api-tools :) 21:43:09 Fedora will need ~25 new packages; EPEL ~70. 21:43:17 * gholms shuts up 21:43:34 gholms: /me is happy to do review swaps with you - I am in a similiar boat 21:43:38 but that's a different matter than making them happy as rpms in the current iteration 21:43:50 brianlamere: you can always submit feature requests :) 21:44:55 [Everyone stares at brianlamere] 21:45:09 [everyone stares at gholms' supposed person sitting next to him] 21:45:17 ha - ok. next topic! 21:45:17 D: 21:45:25 #topic BoxGrinder 21:45:29 gholms: she is not creepy 21:45:31 * rbergeron thought she saw mr. goldmann about 21:45:37 I can guarantee that she is very lovely 21:45:39 oh, he's away 21:45:46 and smells better than gholms :D 21:45:53 obino: Only when staring at my screen, reading what I type. 21:46:09 Any other BG people here? 21:46:12 sounds creepy to me 21:46:16 #action one of you needs to ask her out on a date instead of being creepy :) 21:46:22 lol 21:46:25 rbergeron: She's married 21:46:34 o0 21:46:41 gholms: oh. well 21:46:44 hmmm 21:46:47 * rbergeron has no comment. MOVING ON 21:46:52 Good one. 21:46:56 no marek today, but he's kicking butt and taking names. 21:47:01 there was a kickstart discussion that started up via emails involving boxgrinder, dwalsh, etc 21:47:04 And he did eventually get home from FUDCon. :) 21:47:20 but I need to poke the conversation I think 21:47:27 rbergeron: I had some good discussions with him about integrating BG and Oz. 21:47:31 AFAIK you can kickstart a EC2 instance the same way you can kickstart a regular box. 21:47:35 I really hope it isn't waiting for my input, because that can take AGES sometimes. 21:47:45 gholms: ami-creator seems to be a direction for that, right? 21:47:46 (haven't written any code yet, but at least we have some ideas) 21:47:50 clalance: Do tell. 21:47:51 brianlamere: I'd prod it 21:48:08 gholms: Essentially, BG would call out to Oz as a backend to do installs. 21:48:16 skvidal: What he wants to do is have the instance kickstart itself when it starts. 21:48:26 (it requires changes to BG, unfortunately, as there is some overlap between Oz and BG) 21:48:39 But if we did that, then BG could install non-Fedora OSs. 21:48:44 (and non-Linux OSs, for that matter) 21:48:52 gholms: yeah, an instance that can boot up just like PXE/etc would, and knows how to run off and kickstart itself. lovely idea. 21:48:56 That's a gib plus. 21:48:59 *big 21:49:19 brianlamere: That's kind of what Oz does as well. 21:49:29 (though it uses a virtual machine to do so) 21:49:40 Yeah, downside is running bg on an EC2 instance 21:49:48 brianlamere: Grab the kernel and initrd from images/pxeboot on the mirror, then hand that kernel the location of your kickstart as a parameter. Done. 21:50:29 I think you'd boxgrinder the image that can kickstart itself - I don't think you'd make an image that can boxgrinder an image. I mean, there's only so far that is useful 21:51:05 gholms: sure, but there's specialness about ec2 that might confuse anaconda just a tad. and thus might need special kickstart args 21:51:26 gholms: so the benefit of being able to kickstart ON the machine is that you can do your normal scripts 21:51:39 skvidal: Exactly 21:51:46 but if you can generate/upload an ami using a kickstart as the only input 21:51:47 of course, I say this as a person that hasn't done VMs locally for years, as I've not needed them. So I may just have too dusty a memory to be useful. 21:51:49 isn't that the same? 21:52:07 skvidal: no 21:52:12 brianlamere: why? 21:52:56 because a kickstart can source a location for minor tweeks. it can be told to get info from an amqp message to change what it builds. it can build the instance with the most updated rpms 21:53:24 making a static AMI means you have to update it, and make thousands of static AMIs for each and every possible need 21:53:42 perhaps - feels like a big cost for startup - but maybe that's not that big 21:53:47 better to just have a single AMI that can pop itself out as a fully patched, updated, and exact version of what you need :) 21:54:14 What's the difference in startup time? 21:54:19 nope, building it as patched is faster than pushing an AMi and then patching that AMI. Especially when SELinux gets involved 21:54:22 It's very un-cloud-like, but it will still work. 21:54:28 jdarcy: well an image is pretty much instantlyavailable 21:54:38 jdarcy: a kickstart is 'format + download pkgs + install pkgs' 21:55:09 * skvidal wonders if you could build an ami ON a host in ec2 21:55:12 so the upload is faster 21:55:12 I dunno, I see it as more cloud-like - get a queue message to make exactly what you want, versus some static image harkening back to days of building systems from a blessed gold image on a tape 21:55:15 I suspect so 21:55:39 skvidal: So even though the actual startup is likely to be quicker than a fully-loaded AMI the total "press button to log in" time would probably be longer, right? 21:55:41 brianlamere: I agree about that part 21:55:59 user-data, read from a url, read from a queue, whatever - read configs for the kickstart and build that 21:56:00 jdarcy: it varies - I think it would depend on how much you do in %post 21:56:06 skvidal: Of course you can. I ran a Gentoo box on EC2 for a while. :) 21:56:18 * rbergeron announces that she has to strap on her jetpack in approximately 2 minutes. anyone want to take the reins? 21:56:32 rbergeron: For your jetpack? No way! 21:56:36 but we haven't talked about s3cmd! 21:56:47 gholms: of the meeting :) 21:56:48 jdarcy: and depending on where you were installing from - you could end up incurring some bandwidth costs. 21:56:51 s3cmd can be next! 21:56:56 I think the Aeolus folks might have some ideas about image creation vs. subsequent "personalization" too. 21:57:20 * clalance also has to run 21:57:29 * skvidal would generally prefer everything be focused on kickstarts 21:57:34 either making images from kickstarts 21:57:34 * rbergeron spins the wheel of fate 21:57:43 #chair gholms ke4qqq 21:57:43 Current chairs: gholms ke4qqq rbergeron 21:57:44 or making it so the image can run anaconda and therefore kickstart 21:57:44 rbergeron: I can run the meeting... 21:57:52 * rbergeron notes that ke4qqq has something to say when this is done so harass him about it plz 21:58:09 * ke4qqq looks up 21:58:19 yeah, an image that can run anaconda itself to kickstart a new image would be super-keen. 21:58:32 ke4qqq: the underside of the bus is shiny, no? :) 21:58:40 brianlamere: pxe for ec2 21:58:44 no, actually a bit grimy 21:58:49 oh 21:58:51 (er...and that instance becoming the new image - not that instance making a new AMI) 21:58:54 * rbergeron sniffs and leaves, bbiab 21:58:56 * skvidal looks at rackerhacker ^^^^ what about that at rackspace? 21:59:03 * skvidal waves to rbergeron 21:59:09 * jdarcy waves. 21:59:35 does rackerhacker have a pv-grub like kernel? (displays ignorance) 21:59:37 skvidal: i'm all for it ;) 21:59:40 err...rackspace 21:59:46 brianlamere: we have pv-grub, but it's not usable automatically 21:59:52 rackerhacker: so lemme know when next week that'll be available 21:59:54 :) 22:00:35 Shall we move on to s3cmd? 22:01:18 #topic s3cmd 22:02:10 s3cmd! 22:02:15 :D 22:02:52 ok, I'll be honest - my main concern with s3cmd is it is maintained at the same place as s3sync, and I've had lots of problems with s3sync ;) I tried out s3cmd and it seems to work well enough, BUT... 22:03:34 s3sync seemed to have problems with larger sets of files....20G +.... 22:04:22 I tried putting up a lot of info with s3cmd and it seemed ok, but I'm not sure at what point it should be blessed. The repos are massive, but it would cost me real money to do a test similar to that amount of stuff 22:05:01 sure AWS is cheap, but once you start shoving 900G around, stuff starts adding up :P and I have no business need for it atm, so I can't "test" that way. 22:05:03 thoughts? 22:05:15 IIRC, jforbes has some sort of magical account that might be useful for testing that sort of thing. 22:05:46 yeah, I can't nominate myself to use his account though ;) nor am I sure if it has free S3 22:06:01 jforbes: ping 22:06:53 Do s3cmd and s3sync use similar code? 22:07:18 gholms: magical account? 22:07:55 jforbes: I seem to recall someone or other getting permission to use S3 for testing Fedora-related stuff. 22:08:08 gholms: Umm, not really 22:08:09 * rbergeron is back 22:08:20 gholms: We have 1 account which is for hosting official images only 22:08:33 There goes that idea. 22:08:35 gholms: and another account which we actually pay for, used for testing fedora images 22:09:08 Would a similar account for putting repo mirrors on S3 be possible? 22:09:27 gholms: not sure what the arrangement is there 22:09:28 jforbes: so my concern is that s3sync broke down with large sets of data. So to really know if s3cmd would work, it should be tested with data sets similar to what it would actually be used for 22:09:40 It sounds like brianlamere's small-scale testing was successful, so I think that's the next logical step. 22:10:01 jforbes: would it be worth it for me to try to re-ping the AWS folks and see if they'd lend me a temporary account to test with? 22:10:47 brianlamere: more than welcome to, but knowing the amount of overhead required for them to do anything, it might be a massive waste of time 22:10:50 I don't necessarily like contacting an org and present myself as a representative of another org, without really being blessed to do it for that action - heh 22:11:25 I'm happy to waste my time, so long as someone can just say it's cool to ask for it on the Fedora Community's behalf 22:11:31 brianlamere: heh, dont know that I would contact them as a representative of fedora myself to do that 22:11:33 Does it help at all when the requests come from rh.com addresses? 22:12:06 brianlamere: consider yourself blessed if the org you are representing fedora cloud-sig :) default to you have permission :) 22:12:15 gholms: I don't know the extent of the RH relationship with them, but I dont think they are even offering us free space for repos mirrors, so no clue 22:12:24 baaack! 22:12:26 :-\ 22:12:31 hey marek :) 22:12:42 rbergeron: Jetpack broke down? 22:12:42 hey rbergeron 22:12:49 they were suggesting that fedora repo space would be offered, but man...that's been months. I'll dust off those conversations ;) 22:12:54 Unfortunately the best I can do is test stuff against Eucalyptus, and I'm not sure we have that much storage space. 22:13:09 gholms: I successfully retrieved younglings from educational stuff 22:13:24 (And I'm not sure if I have the cycles to test it right now) 22:13:24 brianlamere: last I heard, there were discussions on that, and it was decided that they would not, but those discussions were with gregdek, so not sure 22:13:35 brianlamere: it doesn't hurt to try :) 22:13:35 gholms: the problem is that it is s3 that sometime burps, and a tool needs to handle that well enough...so if your local stuff handles it, that's not really a test 22:13:41 s3 disappears sometimes 22:13:53 brianlamere: Yep 22:14:14 Then again it's easy to make walrus hiccup as well, since you can bounce it easily enough. 22:14:29 * rbergeron makes a note to try that sometime 22:14:48 Interpret that however you want. 22:15:13 walrus hiccups are rather smelly, fyi 22:15:19 * rbergeron notes that as well 22:15:46 * rbergeron looks for more comments on s3cmd ... ? 22:16:04 #info Small-scale testing with s3cmd was successful. We now need a way to do larger-scale testing with a full-size Fedora repo. 22:16:15 so wait - brianlamere wants to do testing - he either needs funds or a free account 22:16:37 who can get him funds for account or free account? 22:16:53 i have no idea how to get money out of anyone 22:16:56 ke4qqq: well I've also been assuming I'd have a large set of files of my own to upload at some point, it just hasn't happened. there's still a chance that will happen Any Day Now 22:17:01 oh, wait: that's not true 22:17:05 It sounds like Fedora repos on S3 are something red hat will eventually need to pay for. 22:17:14 rbergeron: Challenge them to bowling games? 22:17:17 gholms: maybe, I've not lost hope ;) 22:17:20 gholms: i lost to spevack twice 22:17:22 * ke4qqq knows how to get money 22:17:35 I'm sorry, but I need to go now:( will read the logs and attend next week's meeting, latesr and have a nice evening! 22:17:43 mgoldmann|away: have a good night :) 22:17:53 thanks, bye! 22:17:55 brianlamere: how much money are we talking about here? 22:18:04 would we guesstimate 22:18:05 *Someone* will have to pay for it. If RH can't even get free hosting for Fedora images there's little chance we'll get them to do it for repos. 22:18:07 remember - if fedora already has an account, they can create a bucket and give my account temporary ability to upload to just that bucket, and nothing else. IAm to the rescue 22:18:29 sec, lemme relook at the prices and I can tell yu 22:18:31 you 22:18:31 jforbes: the account tha tyou have that spevack is hooked up with - is that all worked out? 22:19:01 or is that still in the air with the moving around of accounts 22:19:16 Yeah, that's all worked out 22:19:16 647G * 0.15 USD per GB per month == 97.05 USD per month. 22:19:22 That one comes out of his budget though 22:19:28 thats ok 22:19:31 it's under 500 bucks 22:19:33 That's for one mirror, so we would need four of those. 22:19:34 just do it 22:19:47 you don't even need to ask him for permission 22:19:48 There are also charges to transfer the stuff in. 22:19:50 $0.10/G for data transfer in. $0.14/G for storage. Now...how many gigs is in a repo? ;) 22:19:53 would we need this continuously every month? 22:20:04 brianlamere: Right now, 647G. 22:20:05 or just 1x for testing purposes and then moving it over to engineering stuff 22:20:39 jforbes: can we just allocate him some space in the way he just listed? 22:20:40 would probably want to transfer the block up, then mess with it a lot - remove random sections of it, change things, etc - you know, testing the syncing 22:20:53 so it would probably push a TB by the end of it all 22:21:03 rbergeron: I am just a user of the account, you would have to ask spevack about that 22:21:14 spevack would have to do the allocating? 22:21:29 or tell someone to do it 22:21:54 The account is really there for Fedora infrastructure stuff as I recall. We just use it for image testing to simplify billing 22:22:10 hmmm perhaps more people need privs to unblock that. 22:22:18 perhaps smooge or skvidal 22:22:19 and I can shoot a simple set of instructions on how to lock down my ability to do *only* that activity 22:22:32 jforbes: that's neat 22:22:36 b/c I've never seen it :) 22:22:56 lols 22:23:09 not really a priv thing, more of a budget thing. 22:23:31 still - this strikes me as less than 500 bucks, we ought to just make it happen. 22:23:32 jforbes: and there is a separate engineering account somewhere too? 22:23:55 or am i insane 22:24:04 ke4qqq: When running this in production we would need four copies, though. 22:24:09 well I can also just help show what would be a sufficient test, if someone else wants to just run it themselves :) if infrastructure already has ~674G of files sitting around on an instance, they're halfway there so far as the cost is concerned 22:24:13 rbergeron: I am sure there is a RHEL account for engineering, I dont know anything about it though 22:24:13 rbergeron, jforbes: ping spot about this 22:24:25 rbergeron, jforbes: b/c we were told to start collecting accounts 22:24:27 yeah, lots less than $500 22:24:28 skvidal: about wha tthe purposes is? 22:24:37 gholms: yes, but still less than 500 even with 4 copies 22:24:44