[00:41] <surgemcgee> =8>
[00:41] <surgemcgee> just checking.. and streching my legs.
[00:56] <m_3> 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] <m_3> adam_g: give that another try when you get a chance
[01:09] <m_3> SpamapS: please double-check https://launchpad.net/charms/quantal when you get a chance
[01:09] <adam_g> m_3: looks like it works now. :)
[01:09] <m_3> adam_g: cool thanks
[01:10] <m_3> we hadn't actually created a distro series for quantal yet
[01:41] <imbrandon> m_3: you catch my note about the github svn + bzr svn interface ?
[01:42] <m_3> imbrandon: yup... I'd have to try it out
[01:43] <imbrandon> cool cool ,me too, i just tried it enought to see if it was r/o or r/w
[01:44] <imbrandon> 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] <imbrandon> but its just for $sometime
[01:49] <m_3> cool
[01:49] <m_3> yeah, that's a great idea if we keep up the gitpad mirror
[01:50] <imbrandon> yea and the url is the same as the git https one except it drops the .git from the end
[01:50] <imbrandon> for co etc
[03:11]  * zooko looks at https://juju.ubuntu.com/docs/write-charm.html
[03:33] <zooko> "Assuming the current directory is the juju trunk"
[03:34] <zooko> Hm... does that mean I need to check out some repository first?
[03:34] <zooko> Perhaps https://code.launchpad.net/charms
[03:35] <marcoceppi> zooko: You don't need to checkout any repositories to start writing charms
[03:35] <marcoceppi> That tutorial is a little...out of date.
[03:36] <zooko> Where should I start?
[03:36] <marcoceppi> Well, it's not that bad actually
[03:37] <zooko> Should I go ahead and check out https://code.launchpad.net/charms?
[03:37] <marcoceppi> 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] <marcoceppi> so, pretty much if you're making a "foo" charm, mkdir -p ~/charms/precise/foo
[03:39] <zooko> Ok.
[03:39] <zooko> :-)
[03:39] <zooko> Thanks.
[03:41] <zooko> marcoceppi: what's an example of a good README I should emulate?
[03:45] <marcoceppi> zooko: there are a few, you can take a look at http://jujucharms.com/charms/precise/hadoop
[03:46] <surgemcgee> Ohh, ohh, me me!
[03:52] <zooko> surgemcgee: you you what? You wrote a good README? :-)
[04:17] <zooko> Should I list Python as a "requires" for Tahoe-LAFS?
[04:18] <zooko> And I wonder if I should "provide" anything?
[04:31] <surgemcgee> zooko: I am pretty sure, it is here in my branch -->  http://bazaar.launchpad.net/~robertsteckroth/charms/precise/django-rainbow/trunk/files
[04:58] <zooko> Having written his README, zooko returns to https://juju.ubuntu.com/docs/write-charm.html
[04:59] <zooko> Errrrmm... now I get to choose bash or Python for my intall script.
[04:59] <zooko> Hm,.
[05:00] <zooko> Well, that was easy.
[05:01] <zooko> http://codepad.org/hy5Hh7BI
[05:24] <zooko> Hm, I don't understand in which script I should do the creation of the state.
[05:24] <zooko> Time for some sleep anyway.
[05:25] <koolhead17> zooko: gn :)
[05:43] <zooko> :-)
[11:08] <lynxman> jcastro: roger that :)
[15:58] <jcastro> http://news.ycombinator.com/item?id=4069164
[15:58] <jcastro> woo!
[15:58] <jcastro> Here's what m_3's been working on for a day or so
[15:58] <jcastro> well, the post was only that long, the rest was a bunch of hard work. :)
[15:59] <negronjl> 'morning all
[16:02] <hazmat> negronjl, g'mroning
[16:02] <negronjl> 'morning hazmat
[16:02] <hazmat> just noticing its rather silly to distinguish tcp/udp in open/close port
[16:12] <jcastro> 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] <mramm> Up to 7 upvotes now, but could use a few more;) http://news.ycombinator.com/item?id=4069164
[16:22] <negronjl> jcastro:  how do you vote ?
[16:22] <jcastro> sign up
[16:22] <jcastro> and then click the little arrow to the left of the title
[16:23] <m_3> negronjl: btw, please check the article for stupidity :)
[16:23] <negronjl> m_3:  I will ... but I doubt I will find any :)
[16:31] <jimbaker> i rather liked the article (which i upvoted), it gives great insight into why this was an interesting if preliminary experiment
[16:32] <m_3> jimbaker: thanks... yeah, I think it's a good story
[16:32] <m_3> and the results are pretty much expected
[17:10] <lynxman> jcastro: hey, I had on my calendar charm review on Thursday, was it moved?
[17:10] <jcastro> you're the only one this week, so however you want to slice it is fine
[17:10] <jcastro> I don't think anyone moved it
[17:10] <lynxman> jcastro: k :)
[17:10] <lynxman> jcastro: any official guide for review or just go with my gut?
[17:11] <lynxman> (just in case)
[17:11] <jcastro> https://juju.ubuntu.com/Charms
[17:11] <jcastro> yeah
[17:11] <jcastro> look in "Reviewers"
[17:11] <lynxman> jcastro: lovely, thanks :9
[18:14] <jcastro> marcoceppi: wotcha up to right now
[18:15] <marcoceppi> jcastro: sitting through a boring meeting, what's up?
[18:15] <jcastro> spdy is default in firefox13
[18:15] <marcoceppi> booooya
[18:15] <jcastro> clint's charm is basically done, I think it needs a review and promulgation?
[18:16] <marcoceppi> I'll take a look
[18:16] <jcastro> 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. <juju:In Progress by jimbaker> < https://launchpad.net/bugs/1009221 >
[22:33] <RaptorsAtatck> 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] <james_w> RaptorsAtatck, "juju status --format=dot" might interest you
[22:35] <james_w> I'm not sure what you mean by "what charms are installed on systems" though
[22:36] <RaptorsAtatck> @its the services/units bit that juju already handles
[22:36] <RaptorsAtatck> so never mind on that part ;)
[22:36] <james_w> ok :-)
[22:36] <RaptorsAtatck> reading into the docs while trying to poke holes
[22:37] <james_w> the status output will draw a graph of the services/units you have and the relations between them
[22:41] <RaptorsAtatck> gah love the relationship hooks.
[22:41] <RaptorsAtatck> configuration management has been a pain, even with puppet.
[23:02] <RaptorsAtatck> 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] <surgemcgee> A simple bash script can do that, no need to go higher than juju already is.
[23:09] <RaptorsAtatck> yeah, but maintaining that will suck
[23:10] <RaptorsAtatck> So, going to make a simple script that will take the output of the status and rebuild that in the selected environment
[23:10] <RaptorsAtatck> then I can just check status outputs in when I'm happy with how they look
[23:12] <RaptorsAtatck> oh man can take that idea/concept alot farther.
[23:13] <surgemcgee> Not on a professional/production level
[23:13] <surgemcgee> Although, destoyed my environment like 20 times (don't tell amazon. ha).
[23:14] <zooko> 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] <RaptorsAtatck> well its actually for managing private clouds
[23:15] <RaptorsAtatck> a common issue I've ran into is developers needing complex environments setup
[23:15] <RaptorsAtatck> so we normally make a VM image w/ puppet/mcollective and then update those as needed
[23:15] <RaptorsAtatck> huge pain in the ass when the developers change things
[23:16] <RaptorsAtatck> this way we can keep a snapshot of what a developer environment looks like and just execute that as needed
[23:16] <RaptorsAtatck> (the developer that is)
[23:18] <surgemcgee> 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] <RaptorsAtatck> yeah,  many people on the project ;)