18:00:19 #startmeeting trove 18:00:19 Meeting started Wed Sep 17 18:00:19 2014 UTC and is due to finish in 60 minutes. The chair is amcrn. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:22 The meeting name has been set to 'trove' 18:00:59 what up amcrn 18:01:12 what's up cp16net :) 18:01:38 o/ 18:01:42 o/ 18:01:50 waiting on my new lappy to be delivered... 18:02:04 o/ 18:02:06 o/ 18:02:07 waiting is the hardest part 18:02:12 cp16net: nice. you're not going to accidentally ruin this one too are you 18:02:13 o/ 18:02:15 ;) 18:02:37 haha i better not :-P 18:02:43 we'll give it a minute or two for a few folks to trickle in, but the agenda seems to blank, so this should be short 18:02:51 to be* 18:03:05 so you guys that were at OSSV - how was the panel? 18:03:08 those are the longest meetings tho :-P 18:03:25 o/ 18:03:39 dougshelley66: i feel it went well 18:03:39 o/ 18:04:00 amcrn, that's good 18:04:07 amcrn, any tough questions 18:04:14 #topic general discussion 18:04:36 so with no action items on the agenda, does anyone have anything for general discussion? 18:04:52 dougshelley66: a couple of interesting ones, but nothing mind blowing 18:05:01 grilled cheese is amazing. 18:05:04 o/ 18:05:14 Thanks for merging that config parm fix for fake mode 18:05:19 amcrn: ^ 18:05:20 thats all i have 18:05:23 grapex: no problem. 18:05:50 I've been working on the new event simulator. In theory it seems easy enough- I'm using greenlet directly which exposes a really simple way to do true coroutines which is all I ever wanted for the event simulator 18:05:56 thanks to kevinconway for that tip 18:06:06 but it's locking up when I run the tests. Something is causing it to hang 18:06:12 if I can figure that out I think it could be ready pretty soon 18:06:21 thanks to kevinconway for that bug? 18:06:22 grapex: excellent, looking forward to continued progress on that front; cheers to you and kevinconway 18:06:36 I've got a question: Anyone know what the guest_id option in cfg.py is for? 18:06:52 peterstac: it's used for /etc/guest_info, which the guest uses to register to the rabbitmq topic 18:07:04 When I add a help line to it, the guest agent fails to start (due to dupe option) 18:07:05 amcrn: No problem. Always glad to help! 18:07:05 * grapex throws down smoke bomb, shoots grappling hook and ziplines away 18:07:26 amcrn: Ah, so I can't just delete it :( 18:07:30 peterstac it is defined in the trove-guestagent bin 18:07:48 in trove/cmd/guest.py 18:08:12 possibly remove it from there and add to cfg 18:08:14 right, so any ideas about why adding a help string to it would cause a complaint about duped options? 18:08:27 cause is is defiend twice 18:09:00 so if it's defined in trove/cmd/guest.py can I take it out of cfg.py ? 18:09:06 yes 18:09:07 robertmyers ^^ 18:09:18 robertmyers: ok, solved, thanks! 18:09:35 alright, if that does it, let's give some time back to folks and end the meeting 18:09:55 anything else? 18:09:57 peterstac: possibly all the guest options need to be in a different cfg.py 18:10:19 as they aren't needed in trove api 18:11:19 alright, calling it. if there's more on this cfg.py for guest conversation, we can spill it over into the main channel. 18:11:24 thanks everyone! 18:11:27 robertmyers: sure, but I'll leave for a different bug ;) 18:11:27 #endmeeting