ihashacksSpamapS: is the mysql-oneway-replication horribly broken like Nagios was or is it just me?03:17
ihashackserrors: http://paste.ubuntu.com/998416/03:17
ihashacksrunning: juju add-relation skydb-master:master skydb-slave:slave03:18
ihashacksjuju status: http://paste.ubuntu.com/998419/03:19
ihashacksI know that there are settings for "user password hostname port dumpurl" referenced here: https://juju.ubuntu.com/Interfaces/mysql-oneway-replication03:19
ihashacksNot clear to me if the burden of setting those is on me or the relation scripts03:19
JoseeAntonioRHi guys! I have a question: if you deploy mysql, do you get a web interface or something?03:23
ihashacks"deploy mysql" gives you a mysql server that you can "add-relation" to other services such as wordpress for the web part.03:24
JoseeAntonioRgreat, thanks03:25
=== TheMue_ is now known as TheMue
=== al-maisan is now known as almaisan-away
SpamapSihashacks: mysql-onewa-replication should work in theory.. but like the nagios charm, it may have bitrotten since I first created it almost a year ago15:10
jcastrohazmat: good afternoon!17:06
jcastrohow we looking wrt. the queue page?17:06
SpamapSjcastro: heh.. negronjl did a nice job producing a cmdline version :)17:07
SpamapSjcastro: I'm about to +1 the merge proposal into charm-tools17:07
negronjlSpamapS: nice :)17:07
jcastroI was going to ask that next, heh17:07
hazmatgreetings jcastro17:08
hazmatjcastro, wip17:08
SpamapSnegronjl: threading buys me about 0.5s ... the other 3.5s is all waiting for the bug search :-P17:08
SpamapSnegronjl: merge away, sir17:10
negronjlSpamapS: thx17:10
jcastrohey so, by default for ubuntu sponsorship each person does 4h a month17:11
jcastroobviously we're much smaller17:11
jcastroso I was thinking going for something like 2 hours a week?17:12
jcastrofor people in ~charmers17:12
jcastrois that too much/little?17:12
SpamapSjcastro: I don't think we all have 2 hours a week to give17:19
SpamapSjcastro: nor does the influx of sponsorship demand 2 hours a week17:19
SpamapSjcastro: 4 hours, in one block, is more valuable than 2 hours in 4 blocks, IMO.17:19
jcastrook so you're thinking once we get past the hump we should just go with that?17:19
SpamapSjcastro: we don't need 24/7 coverage either.. we just need "most of the day on most days" coverage17:20
* jcastro nods17:20
SpamapSjcastro: a quick link to the calendar in topic or just on the Charms page would be nice tho.. so you can see when there is coverage17:21
negronjljcastro, SpamapS: For the time being, we could concentrate on number of reviews ( say one per person per week )17:21
SpamapSnegronjl: I'm hesitant to change the plan we came up with17:21
jcastrowe have about ~7 people in charmers that have been regular reviewers17:21
SpamapSnegronjl: patch pilot works because it is simple and focused on using peoples' time to maximum effect17:21
jcastroSpamapS: the topic and calendar and stuff will be easy17:22
negronjlSpamapS: I'm ok with that.  Let's just pick something.  I threw that suggestion out there because I saw some hesitation to move forward with the current plan.17:22
jcastrowe'll be fine I think17:23
SpamapSnegronjl: only hesitation from jcastro.. ;)17:23
SpamapSwho listens to *that* guy? ;)17:23
jcastroI have no hesitation, I was just wondering if the # of hours was right17:23
negronjlSpamapS: not many people :)17:23
SpamapSjcastro: we have no baseline.. so we can try 4 hrs and measure the effect17:27
jcastroSpamapS: I was thinking of proposing "everyone all in until we get it under control, then go nice and easy"17:31
SpamapSjcastro: I've tried that before. Doesn't seem to have much effect. The usual people do their usual awesomeness, then return to not having enough time to address the queue.17:35
SpamapSjcastro: lets just light the fire of 4 hours per month.. assign people days.. nag them.. and if things aren't getting touched enough, bug people who are in ~charmers to do more.17:36
SpamapSWe have, what, 27 people!?17:36
negronjlSpamapS, jcastro:  I agree that, with 27 people and no baseline, 4 hours is as good as anything so, for now ... start there.17:41
SpamapSI would hope that those 27 would be a little more involved with a known time to plan for17:44
negronjlSpamapS: that makes me think that, the same way that there is a process to become a charmer, there should be one to remove people that are inactive.  Just a thought17:50
SpamapSnegronjl: I'm fine with developing an inactivity report.. we can simply scan the bugs commented on for each user and if there are non in /charms for the past 3 months, warn then remove.17:53
SpamapSnegronjl: Lets make that a TODO for something to add to policy after we get policy in the bzr repo.17:53
* SpamapS opens a charms bug17:53
jcastroI was just going to mention it in the sponsorship initial mail17:53
jcastro"if you're in ~charmers and haven't been reviewing you have a few days to get out, otherwise I'll start assigning you and annoying you."17:54
SpamapSYeah start seeding now "please participate or flag yourself as not participating so we can set expectations appropriately"17:54
negronjljcastro:  Have you created the calendar yet ?17:58
jcastrodaniel's script just adds your assignment to your work calendar17:59
SpamapSjcastro: would be much better if it was a single calendar that people can see18:00
negronjljcastro:  I think I like that better as well18:01
jcastroI'll figure something out18:01
SpamapSOk, filed bug 1002406 for the ~charmers policy18:03
_mup_Bug #1002406: Add policy to discuss when charmers members should be automatically removed <policy> <Juju Charms Collection:New> < https://launchpad.net/bugs/1002406 >18:03
twobottuxLaunchpad bug 1002406 in charms "Add policy to discuss when charmers members should be automatically removed" [Undecided,New]18:03
_mup_Bug #1002406: Add policy to discuss when charmers members should be automatically removed <policy> <Juju Charms Collection:New> < https://launchpad.net/bugs/1002406 >18:03
SpamapStwobottux: you need to go away18:04
twobottuxSpamapS: Error: "you" is not a valid command.18:04
twobottuxSpamapS: Error: I am only a bot, please don't think I'm intelligent :)18:04
SpamapSwhose bot is that?18:08
hazmattwobottux, its an askubuntu bot afaik18:14
twobottuxhazmat: Error: "its" is not a valid command.18:14
twobottuxhazmat: Error: I am only a bot, please don't think I'm intelligent :)18:14
hazmatSpamapS, -> <twobottux> 07:52:48> Announcement from my owner (amithkk): Hey! I'm 2bottuX, A bot by Amith KK. I'm on 2 ubuntu channels and #2buntu. My Function is to provide AskUbuntu Integration. If you want me in any of your channels watching a tag, msg amithkk18:14
hazmatmarcoceppi, ^18:14
hazmatnot sure why its doing lp stuff18:15
SpamapSYeah it needs to ignore bugs18:21
SpamapSotherwise bugs will be 3 lines of spam every time18:22
marcoceppihazmat: I'll talk to amithkk18:22
jrgiffordmarcoceppi: SpamapS so you need it to ignore bugs?18:26
marcoceppijrgifford: yeah, the _mup_ bot already does that18:26
marcoceppiif it's to do anything it should only follow the juju tag on Ask Ubuntuy18:27
=== koolhead17 is now known as koolhead17|afk
jrgiffordok, let me see if amithkk left the tmux session running18:27
marcoceppiAt least until that functionality is merged into the _mup_ bot18:28
jrgiffordi'm going to ctrl-c it at the console, it'll be (hopefully) right back18:29
jrgifforddo you really want it in #juju-dev ?18:29
marcoceppiJuju questions should end up in this room, not juju-dev18:31
jrgiffordi think i fixed it18:31
jrgiffordlets try it in a moment18:31
jrgiffordBug #100240618:32
_mup_Bug #1002406: Add policy to discuss when charmers members should be automatically removed <policy> <Juju Charms Collection:New> < https://launchpad.net/bugs/1002406 >18:32
jrgiffordlooks like i fixed that18:32
marcoceppijrgifford: is the source for this public?18:32
jrgiffordmarcoceppi: um, no. at least, not right now as far as i know18:32
jrgiffordi think amithkk's going to submit a merge request like, next week or something with his changes18:33
SpamapSjrgifford: *thank you*18:35
jrgiffordSpamapS: no problem.18:36
jrgiffordit's on my server, i'd be really disappointed if i couldn't stop it. :P18:36
marcoceppinegronjl SpamapS jcastro with the "Review Queue" stuff merged in to charm-tools do we still want to pursue that web-based thing?19:04
SpamapSmarcoceppi: I'm fine w/ the cmdline tool. :)19:05
marcoceppiGuess I'll learn Django another day19:06
jcastrolet's keep it web based19:37
jcastroI mean, having a companion CLI tool is nice19:37
jcastrobut it'd be nice to have it part of the web UI, so anyone can see what's going on, etc.19:37
marcoceppiDjango is back on, hazmat if I get you code for this in the form of a Django project will you be able to integrate it into the current Charm World thing?19:39
hazmatmarcoceppi, negronjl already provided it19:57
marcoceppimakes that easy19:57
hazmatnegronjl, http://jujucharms.com/review-queue21:17
marcoceppihazmat: sexy21:19
marcoceppiShould we drop the Charm Needed: stuff?21:20
hazmatmarcoceppi, yeah.. probably, the need has been fufilled21:20
hazmatalthough that's a matter of perspective i suppose21:21
hazmatits still needed till its in 'main'21:21
marcoceppiIMO, if it's a bug in the charm project, it's for a charm being worked on; Since we can open bugs directly against promulgated charms, etc21:21
SpamapSI'd leave the Charm needed21:27
SpamapSFor the Proposals I'd rather see the URL there than "Proposal"21:27
SpamapSThough I think we talked about grabbing the summary of any linked bugs21:27
hazmatSpamapS, fixing that right now21:29
hazmata couple of other minors as well21:29
SpamapSAnother way to go would be Proposal: $(charmname)21:29
hazmatSpamapS, i'm doing Merge proposal for %{charmname/branch_name}21:30
hazmathm.. although perhaps i should just do %series/charm_name21:31
SpamapSYeah perfect21:32
hazmatSpamapS, should be good now21:47
hazmatlet me know if you think of any other tweaks21:47
SpamapShazmat: its sorted with newest on top21:48
hazmatSpamapS, you want inverse?21:48
hazmater. normal sort21:48
SpamapSwell I think we do21:48
* SpamapS is once again spinning too many plates to recall which direction this plate should be spinning21:48
hazmatSpamapS, fixed.. you'll have to ctrl-r for your browser to force a fetch21:50
SpamapShazmat: looks good21:50
hazmatits setup for a 3m http cache, and a 10m cron update21:50
SpamapSI think we may want to remove In Progress tho21:51
SpamapShazmat: thats mighty fine. :)21:51
hazmatSpamapS, most of those have branches attached re 'in progress'21:51
hazmatyour call though21:51
hazmatSpamapS, for example.. https://bugs.launchpad.net/charms/+bug/983339  this one wouldn't be in the queue otherwise21:54
_mup_Bug #983339: New Charm: munin-node <new-charm> <Juju Charms Collection:In Progress> < https://launchpad.net/bugs/983339 >21:54
hazmatwell i guess it would for being a new charm tag21:54
SpamapShazmat: the merge proposals In Progress are fine. The bugs, are not.21:55
SpamapSa bug in progress means charmers is not expected to do anything21:55
SpamapSthough perhaps instead, we should just unsubscribe charmers and let the user ask for attention again when its time.21:56
hazmatSpamapS, so the munin charm isn't ready for review?21:56
SpamapShazmat: the munin merge proposal is21:56
hazmatSpamapS, :-)21:56
SpamapSno never mind21:56
SpamapShazmat: so james page set it back to 'In Progress' to suggest that its not ready for any further review. I think.21:57
hazmatSpamapS, work in progress works well on a merge proposal.. on a bug there isn't a clear way to indicate ready for review outside of a tag21:58
hazmatright now pretty much all bug states outside of committed, released with a 'new-charm' tag are considered part of the queue21:58
SpamapShazmat: yeah, I think we just need to think about how we want to manage the queue a bit22:00
SpamapShazmat: simplest is to just have new-charm be the clear "I need help" flag22:00
SpamapSor, I think we'll change it to subscribing ~charmers22:00
hazmatSpamapS, new-charm works for the initial point of contact, but as things progress, its unclear that it remains cogent of the current state of the charm branch22:01
hazmatSpamapS, looking over https://bugs.launchpad.net/charms/+bug/806044 for example, the author has incorporate review feedback, but there's really no way of knowing it from the bug per se.22:01
_mup_Bug #806044: Charm needed: Moodle <new-charm> <Juju Charms Collection:In Progress by rkather> < https://launchpad.net/bugs/806044 >22:01
dpb_hi folks.  I had a 75GB log file after just a few days of running a local lxc 2-service test bed.  Is this a known issue?  (machine-agent.log)22:19
hazmatdpb_, yes.. its fixed, and awaiting an sru22:35
hazmatSpamapS, any updates on that getting pushed out?22:35
dpb_hazmat: cool, thx22:40
dpb_hazmat: in the ppa already?22:40
SpamapShazmat: I'll upload to precise-proposed tomorrow23:11
SpamapSwow.. charm getall takes a *long* time23:44

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!