[10:47] <_mup_> Bug #830995 was filed: default-instance-type and default-image-id are unhelpful <Ensemble:New> < https://launchpad.net/bugs/830995 >
[10:52] <_mup_> Bug #830999 was filed: cannot specify machine constraints <Ensemble:New> < https://launchpad.net/bugs/830999 >
[13:18] <fwereade> I need to learn to pay attention to my status :/
[13:20] <_mup_> Bug #831058 was filed: cobbler FileStorage assumes no authentication required <Ensemble:New> < https://launchpad.net/bugs/831058 >
[13:38] <niemeyer> Hello all
[13:38] <niemeyer> Good week kickoffs for everybody
[13:49] <fwereade> niemeyer: heyhey!
[13:49] <fwereade> niemeyer: how's it going?
[13:51] <niemeyer> fwereade: Hey!
[13:51] <niemeyer> fwereade: Very nice
[13:51] <niemeyer> fwereade: Had a good relaxing weekend
[13:51] <niemeyer> fwereade: You?
[13:51] <fwereade> niemeyer: pretty good thanks
[13:51] <fwereade> niemeyer: keeping half an eye on libya, what with it being right in my back yard
[13:52] <niemeyer> fwereade: :(
[13:53] <fwereade> niemeyer: it seems to me like a tentative ":)" at the moment, but who knows what's coming :/
[13:54] <fwereade> niemeyer: and we didn't give back his fighters, so I doubt we have much to fear from the new lot :p
[13:54] <fwereade> niemeyer: anyway :)
[13:54] <fwereade> niemeyer: I've been wondering about bug importance and milestones
[13:54] <niemeyer> fwereade: Yeah.. worth paying some attention to
[13:55] <niemeyer> fwereade: Ok
[13:55] <fwereade> niemeyer: there are a few bugs marked "high" but not assigned to eureka -- is that explicit notice that we shouldn't be worrying about them now?
[13:58] <niemeyer> fwereade: It's a good hint they might either a) be misplaced; or b) be miscategorized
[13:58] <fwereade> niemeyer: hm, ok :)
[13:58] <fwereade> niemeyer: I've been a little reluctant to go around assigning priorities and suchlike, what with still being pretty new
[13:59] <fwereade> niemeyer: which is why 90% of my branches have been fixes to "uncategorized" bugs
[13:59] <fwereade> niemeyer: should I perhaps be taking a different approach?
[14:00] <niemeyer> fwereade: I would guess this happens due to our overuse of bugs to mean "task"
[14:00] <niemeyer> fwereade: You're working on a single High priority problem
[14:00] <niemeyer> fwereade: Getting physical deployments working
[14:00] <fwereade> niemeyer: similarly, when I report a bug, I don't usually assign a milestone; I only do that when I'm actually working on something, but I'm suddenly worrying that they'll just fly under the radar
[14:01] <niemeyer> fwereade: You can tons of uncategorized bugs because they are simply a path to get pieces of that work landed
[14:01] <niemeyer> s/You can/You get/
[14:01] <fwereade> niemeyer: makes sense
[14:01] <niemeyer> fwereade: The bug priority is most interesting when it's an actual issue we want to stash away without an assignee
[14:01] <niemeyer> fwereade: Because it tells the next guy what he should be paying attention to
[14:03] <fwereade> niemeyer: I probably kinda mostly see
[14:03] <fwereade> niemeyer: as an example, there's this idea that we should be able to specify more about what sort of machines are used in certain circumstances
[14:04] <fwereade> niemeyer: a bug for that didn't leap out at me, so I filed one this morning, as a general "we should do this sometime" note
[14:04] <niemeyer> fwereade: That sentence gives such a positive feeling :-)
[14:04] <fwereade> niemeyer: haha :)
[14:05] <fwereade> that's lp:830999, which has no importance, assignee, or milestone
[14:06] <fwereade> niemeyer: should it maybe be High, None, Eureka?
[14:06] <niemeyer> fwereade: Definitely not Eureka
[14:06] <niemeyer> fwereade: I'd personally qualify that as a Medium, non-Eureka
[14:06] <niemeyer> fwereade: Eureka has a short time span (as usual ;-)..
[14:06] <fwereade> niemeyer: I feel vindicated in my reluctance to go around categorizing things myself ;)
[14:07] <fwereade> niemeyer: I don't think I know when eureka actually is targeted to... LP thinks it was 1/1/2011, which I suspect to be incorrect (:p)
[14:07] <niemeyer> fwereade: As far as physical deployment goes, Eureka is about finishing the barebones
[14:07] <niemeyer> fwereade: Making it work reliably
[14:08] <niemeyer> fwereade: Rather than getting fancy features in
[14:08] <niemeyer> fwereade: Eureka is 11.10
[14:08] <fwereade> niemeyer: that's fine by me ;)
[14:08] <niemeyer> fwereade: End of September, pretty much
[14:09] <fwereade> niemeyer: ok, makes sense, and we have some sort of special dispensation to release whatever we have done (while most things have already passed the deadline to get in) ...right?
[14:10] <niemeyer> fwereade: Kind of.. this is actually the real deadline
[14:10] <niemeyer> fwereade: For everyone
[14:10] <niemeyer> fwereade: Or rather.. for everyone in similar circumstances
[14:11] <niemeyer> fwereade: E.g. Ensemble is in universe, it's already there right now, etc
[14:20] <hazmat> i think the close out of the milestone is scheduled right before the final testing freeze
[14:20] <hazmat> hmm.. actually its not, i should move it up
[14:21] <hazmat> the final freeze is sept 22nd
[14:21] <hazmat> er 29th
[14:21] <hazmat> 22nd is beta 2
[14:37] <niemeyer> hazmat: SpamapS requested us to land things by Sep 22nd for testing..
[14:37] <niemeyer> hazmat: We can close the milestone with 29th
[14:38] <niemeyer> hazmat: and have that week for testing on our side too
[14:38] <niemeyer> Still within Eureka
[15:04] <jcastro> negronjl: ok, I tried a few times over the weekend and just now, still getting this "error: { "$err" : "not master", "code" : 10107 }" every time
[15:28] <niemeyer> Lunch time..
[15:34] <jcastro> Ensemble is on devops cafe! http://devopscafe.org/show/2011/8/22/devops-drop-004.html
[15:36] <robbiew> nice
[15:40] <robbiew> jcastro: did they talk about it?
[15:40] <jcastro> yeah
[15:40] <jcastro> it's a short podcast, worth a listen
[15:43] <robbiew> jcastro: interesting..thanks
[16:02] <_mup_> ensemble/expose-cleanup r328 committed by jim.baker@canonical.com
[16:02] <_mup_> Initial refactoring per review
[16:03] <_mup_> ensemble/expose-cleanup r329 committed by jim.baker@canonical.com
[16:03] <_mup_> Merged trunk
[16:07] <negronjl> jcastro:  I'll look into it.
[16:07] <jcastro> negronjl: ok I tried some other things and that didn't work either
[16:08] <jcastro> I have the instance up and running now if you want to check it out
[16:08] <negronjl> sure.  add my ssh-id ( negronjl ) 
[16:24] <SpamapS> lol... John Willis
[16:24] <SpamapS> love his monitoring lightning talk
[16:27] <niemeyer> jcastro: How is it in the podcast?
[16:27] <SpamapS> starts around 4:50 in
[16:28]  * niemeyer downloads
[16:28] <niemeyer> Mostly curious about what the take was
[16:28] <niemeyer> and what's the "ironic twist" :)
[16:28] <SpamapS> Not sure
[16:28] <SpamapS> still listening
[16:30] <jcastro> I have like a minute of silence in mine
[16:31] <SpamapS> yeah
[16:31] <SpamapS> thats a quote
[16:31] <SpamapS> turn it up
[16:31] <SpamapS> its from Fast Times @ Ridgemont High
[16:31] <SpamapS> whoa I got a silence at 8:49 too
[16:32] <SpamapS> right at the juicy part ;)
[16:32] <SpamapS> its like the missing fuzz on the nixon tapes. ;)
[16:34] <SpamapS> yeah that missing minute is really weird
[16:40] <niemeyer> Nice.. quite positive overall
[16:43] <jcastro> clearly he'll have to do another one with more detail. :)
[16:43] <SpamapS> Maybe one of his listeners will write a formula w/ Chef. ;)
[17:10] <hazmat> ensemble team, wikimedia, check emails
[17:10] <hazmat> happening now
[17:38] <_mup_> ensemble/expose-cleanup r330 committed by jim.baker@canonical.com
[17:38] <_mup_> Added mock tests with respect to refactoring of remove_security_groups
[17:54] <RoAkSoAx> fwereade: ping...
[17:54] <RoAkSoAx> fwereade: has something change whithin the code that generates the cloud-init user data?
[18:04] <adam_g> w/in 14
[18:11]  * SpamapS cheers for adam_g's w/inning
[18:14] <_mup_> ensemble/expose-cleanup r331 committed by jim.baker@canonical.com
[18:14] <_mup_> PEP8, PyFlakes, call remove_security_groups more robustly
[18:44] <robbiew> so dumb question:  have we tried testing ensemble against Oneiric images in EC2/OpenStack...or are we still using Natty-based amis
[18:54] <hazmat> robbiew, we've tried it, its not the default
[18:55] <SpamapS> bug 816169 has broken a few peoples' formulas..
[18:55] <_mup_> Bug #816169: When using Ensemble, add-apt-repository no longer functions properly <ensemble (Ubuntu):Confirmed> <python2.7 (Ubuntu):Confirmed> <software-properties (Ubuntu):Confirmed> < https://launchpad.net/bugs/816169 >
[18:55] <SpamapS> need to tak a look at that pronto
[18:56] <hazmat> we should probably switch that to oneiric, there's a bug open about using the default package distros instead of the ppa
[18:56] <hazmat> SpamapS, i thought i merged the fix for that
[18:56] <hazmat> oh.. nevermind
[18:56] <robbiew> might be good to switch it once beta is out
[18:57] <hazmat> SpamapS, there was another bug about pythonpath env variable leaking to executed hooks, and causing issues with package installation. that's no longer the case though
[19:00] <niemeyer> SpamapS: Do you know why they broke?
[19:00] <niemeyer> SpamapS: There's a thread with some questioning around that
[19:01] <niemeyer> adam_g mentioned the interactivity, but Michael Vogt mentioned it actually checks for the tty presence
[19:01] <niemeyer> Not sure about what's happening there
[19:02] <adam_g> niemeyer: its actually cloud-init that was screwing with the tty check
[19:02] <SpamapS> I have not looked at it, just followed the thread.
[19:03] <adam_g> SpamapS: just fixed that cloud-init bug, will check on the other python problems soon
[19:04] <adam_g> niemeyer: the interactivity change is unrelated to #816169 that SpamapS mentioned
[19:04] <_mup_> Bug #816169: When using Ensemble, add-apt-repository no longer functions properly <ensemble (Ubuntu):Confirmed> <python2.7 (Ubuntu):Confirmed> <software-properties (Ubuntu):Confirmed> < https://launchpad.net/bugs/816169 >
[19:16] <adam_g> SpamapS: looks like that is no longer an issue. seems there was some weirndess in the python environment that has since settled? im going to wait for cloud-init to be updated in images so i can bootstrap+deploy without hacking before confirming 100%
[19:17] <SpamapS> adam_g: so since we don't really know where the problem was.. maybe just close all the tasks as Invalid once you've confirmed it doesn't exist anymore?
[19:17] <adam_g> SpamapS: will do
[19:19] <SpamapS> adam_g: sweet thx!
[19:26]  * robbiew needs to eat...back in a bit
[19:36] <RoAkSoAx> fwereade: when you are around pelase give me a shout
[19:51] <hazmat> adam_g, yeah.. it was probably fixed as part of bug 816264
[19:51] <_mup_> Bug #816264: PYTHONPATH causing corrupt environment <Ensemble:Fix Released by hazmat> < https://launchpad.net/bugs/816264 >
[19:58] <adam_g> hazmat: ah, nice
[20:31] <niemeyer> I'll break for some coffee
[20:31] <niemeyer> biab
[20:34] <robbiew> niemeyer: your Google GOpher just arrived at my house
[21:02] <niemeyer> robbiew: Hah :)
[21:02] <robbiew> niemeyer: I'll be sure to bring it to UDS
[21:02] <robbiew> squishable.com....never heard of them before
[21:03] <robbiew> but apparently they are pretty popular
[21:03] <robbiew> the GOpher must be "special"
[21:03] <robbiew> lol
[21:04] <niemeyer> robbiew: They are, somehow.. :-)
[21:05] <niemeyer> robbiew: Thanks for feeding it, meanwhile ;)
[21:05] <robbiew> lol...sure thing
[21:10] <niemeyer> I thought they were going to send the gopher here as they asked for my home address, but if they actually sent the gopher to the original address I provided, I wonder what they've put in the mail now..
[21:40] <niemeyer> Today was remarkably unproductive
[22:43] <_mup_> ensemble/lxc-lib-merge r323 committed by kapil.thangavelu@canonical.com
[22:43] <_mup_> merge lxc-lib
[22:45] <_mup_> ensemble/formula-state-with-url r315 committed by kapil.thangavelu@canonical.com
[22:45] <_mup_> parameterize trunk in ENSEMBLE_TRUNK env variable for makefile
[22:45] <_mup_> ensemble/formula-state-with-url r316 committed by kapil.thangavelu@canonical.com
[22:45] <_mup_> link reference doc for s3 auth url
[23:02] <_mup_> ensemble/formula-state-with-url r317 committed by kapil.thangavelu@canonical.com
[23:02] <_mup_> formula urls are required, also seed ec2 test provider base class with fake credentials
[23:03] <_mup_> ensemble/formula-state-with-url r318 committed by kapil.thangavelu@canonical.com
[23:03] <_mup_> merge trunk
[23:06] <_mup_> ensemble/trunk r323 committed by kapil.thangavelu@canonical.com
[23:06] <_mup_> merge formula-state-with-url [r=niemeyer,bcsaller][f=761053]
[23:06] <_mup_> Formula states are now created in an enviroment with a url to their
[23:06] <_mup_> location in provider storage. This is to enable machine agents not to
[23:06] <_mup_> need access to the provider for deploying formulas.
[23:14] <_mup_> ensemble/machine-agent-uses-formula-url r316 committed by kapil.thangavelu@canonical.com
[23:14] <_mup_> merge trunk
[23:21] <_mup_> ensemble/trunk r324 committed by kapil.thangavelu@canonical.com
[23:21] <_mup_> merge machine-agent-uses-formula-url [r=niemeyer,fwereade][f=828189]
[23:21] <_mup_> Machine agents download formulas using the formula url, instead of 
[23:21] <_mup_> retrieving them directly from provider storage, when deploying units.
[23:27] <_mup_> Bug #831688 was filed: Openstack compatibility is needed <Ensemble:New> < https://launchpad.net/bugs/831688 >
[23:31] <niemeyer> Can someone please have a second review on this: https://code.launchpad.net/~fwereade/ensemble/cobbler-zk-connect-error-messages/+merge/72033?
[23:32] <_mup_> ensemble/stack-crack r326 committed by kapil.thangavelu@canonical.com
[23:32] <_mup_> formulas are published with a formulas- prefix instead of a formulas/, per workaround for bug 829880
[23:44] <_mup_> ensemble/flex-origin r323 committed by jim.baker@canonical.com
[23:44] <_mup_> Fix test that was depending on hash ordering in dict