[00:41] =8> [00:41] just checking.. and streching my legs. [00:56] SpamapS: ^^ (quantal branches) I couldn't push to quantal branches either... bzr: ERROR: Permission denied: "~mark-mims/charms/quantal/junk/trunk/": : No such distribution series: 'quantal'. [01:08] adam_g: give that another try when you get a chance [01:09] SpamapS: please double-check https://launchpad.net/charms/quantal when you get a chance [01:09] m_3: looks like it works now. :) [01:09] adam_g: cool thanks [01:10] we hadn't actually created a distro series for quantal yet [01:41] m_3: you catch my note about the github svn + bzr svn interface ? [01:42] imbrandon: yup... I'd have to try it out [01:43] cool cool ,me too, i just tried it enought to see if it was r/o or r/w [01:44] once i seen it was r/w i was hmmmm i bet the bzr-svn and git-svn tools are much more mature :) [01:44] but its just for $sometime [01:49] cool [01:49] yeah, that's a great idea if we keep up the gitpad mirror [01:50] yea and the url is the same as the git https one except it drops the .git from the end [01:50] for co etc [03:11] * zooko looks at https://juju.ubuntu.com/docs/write-charm.html [03:33] "Assuming the current directory is the juju trunk" [03:34] Hm... does that mean I need to check out some repository first? [03:34] Perhaps https://code.launchpad.net/charms [03:35] zooko: You don't need to checkout any repositories to start writing charms [03:35] That tutorial is a little...out of date. [03:36] Where should I start? [03:36] Well, it's not that bad actually [03:37] Should I go ahead and check out https://code.launchpad.net/charms? [03:37] that wording is just a little confusing, it's supposed to be charm trunk, so for instance you want to create a directory like ~/charms then inside that directory create the series directory, (precise), then the name of the charm. [03:38] so, pretty much if you're making a "foo" charm, mkdir -p ~/charms/precise/foo [03:39] Ok. [03:39] :-) [03:39] Thanks. [03:41] marcoceppi: what's an example of a good README I should emulate? [03:45] zooko: there are a few, you can take a look at http://jujucharms.com/charms/precise/hadoop [03:46] Ohh, ohh, me me! [03:52] surgemcgee: you you what? You wrote a good README? :-) [04:17] Should I list Python as a "requires" for Tahoe-LAFS? [04:18] And I wonder if I should "provide" anything? [04:31] zooko: I am pretty sure, it is here in my branch --> http://bazaar.launchpad.net/~robertsteckroth/charms/precise/django-rainbow/trunk/files [04:58] Having written his README, zooko returns to https://juju.ubuntu.com/docs/write-charm.html [04:59] Errrrmm... now I get to choose bash or Python for my intall script. [04:59] Hm,. [05:00] Well, that was easy. [05:01] http://codepad.org/hy5Hh7BI [05:24] Hm, I don't understand in which script I should do the creation of the state. [05:24] Time for some sleep anyway. [05:25] zooko: gn :) [05:43] :-) === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan [11:08] jcastro: roger that :) === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === zyga is now known as zyga-food === zyga-food is now known as zyga === al-maisan is now known as almaisan-away [15:58] http://news.ycombinator.com/item?id=4069164 [15:58] woo! [15:58] Here's what m_3's been working on for a day or so [15:58] well, the post was only that long, the rest was a bunch of hard work. :) [15:59] 'morning all [16:02] negronjl, g'mroning [16:02] 'morning hazmat [16:02] just noticing its rather silly to distinguish tcp/udp in open/close port [16:12] Only 3 upvotes, come on people, we need to get on the front page to share this with the world! http://news.ycombinator.com/item?id=4069164 [16:21] Up to 7 upvotes now, but could use a few more;) http://news.ycombinator.com/item?id=4069164 [16:22] jcastro: how do you vote ? [16:22] sign up [16:22] and then click the little arrow to the left of the title [16:23] negronjl: btw, please check the article for stupidity :) [16:23] m_3: I will ... but I doubt I will find any :) [16:31] i rather liked the article (which i upvoted), it gives great insight into why this was an interesting if preliminary experiment [16:32] jimbaker: thanks... yeah, I think it's a good story [16:32] and the results are pretty much expected === zyga is now known as zyga-afk [17:10] jcastro: hey, I had on my calendar charm review on Thursday, was it moved? [17:10] you're the only one this week, so however you want to slice it is fine [17:10] I don't think anyone moved it [17:10] jcastro: k :) [17:10] jcastro: any official guide for review or just go with my gut? [17:11] (just in case) [17:11] https://juju.ubuntu.com/Charms [17:11] yeah [17:11] look in "Reviewers" [17:11] jcastro: lovely, thanks :9 [18:14] marcoceppi: wotcha up to right now [18:15] jcastro: sitting through a boring meeting, what's up? [18:15] spdy is default in firefox13 [18:15] booooya [18:15] clint's charm is basically done, I think it needs a review and promulgation? [18:16] I'll take a look [18:16] maybe we can whine to ben to fix that subordinate opening a port bug [21:10] <_mup_> Bug #1009221 was filed: Adds format: 2 support to juju, while maintaining backwards compatibility for old charms. < https://launchpad.net/bugs/1009221 > [22:33] heya, so first off juju is awesome(yeah you guys already know). I'm looking at a way to manage what charms are installed on systems and see network diagrams. I was considering using mcollective for this but it seems like something that would be already solved by someone else. Any ideas? [22:35] RaptorsAtatck, "juju status --format=dot" might interest you [22:35] I'm not sure what you mean by "what charms are installed on systems" though [22:36] @its the services/units bit that juju already handles [22:36] so never mind on that part ;) [22:36] ok :-) [22:36] reading into the docs while trying to poke holes [22:37] the status output will draw a graph of the services/units you have and the relations between them [22:41] gah love the relationship hooks. [22:41] configuration management has been a pain, even with puppet. [23:02] hey so I have an environment deployed and configured how I want it with the appropriate relationships. Is there a way to take a snapshot of this and deploy a mirror of this to a new environment? [23:07] A simple bash script can do that, no need to go higher than juju already is. [23:09] yeah, but maintaining that will suck [23:10] So, going to make a simple script that will take the output of the status and rebuild that in the selected environment [23:10] then I can just check status outputs in when I'm happy with how they look [23:12] oh man can take that idea/concept alot farther. [23:13] Not on a professional/production level [23:13] Although, destoyed my environment like 20 times (don't tell amazon. ha). [23:14] If somebody else will pay for the EC2 fees, I'll measure how Tahoe-LAFS behaves with 5000 servers and write a blog post about it. :-) [23:14] well its actually for managing private clouds [23:15] a common issue I've ran into is developers needing complex environments setup [23:15] so we normally make a VM image w/ puppet/mcollective and then update those as needed [23:15] huge pain in the ass when the developers change things [23:16] this way we can keep a snapshot of what a developer environment looks like and just execute that as needed [23:16] (the developer that is) [23:18] Sounds like high level software development. Most web projects can easly re-configure and deploy to some user friendly cloud like use app engine. [23:23] yeah, many people on the project ;)