[01:12] <rick_h_> marcoceppi: when you get time want to chat packaging/use charmhelpers. since it's using distutils no setup.py develop command and it's merged back to setuptools anyway so not sure if there's a reason to keep it distutils.
[01:13] <rick_h_> bah, and doesn't have any install_requires
[01:13] <marcoceppi> rick_h_: I haven't had a chance to look at the project for several weeks. Given emerging requirements to include multiple languages I imagine re-organizing the code base and having one source package build several language specific (including a generic charm-helpers package)
[01:15] <marcoceppi> rick_h_: I'm not sure if just a setup.py will cut it for packaging
[01:15] <rick_h_> marcoceppi: gotcha, well let me know if you get there and want a test/second set of eyes on making it installable easy enough
[01:15] <marcoceppi> rick_h_: I'm open to opinions even before I get there :)
[01:15] <rick_h_> marcoceppi: yea, not sure. I'm more a python packager. I did it once, but I live in pypi land
[01:15] <rick_h_> (did a .deb once)
[01:16] <rick_h_> but trying to get it installed, wanted to try out the 'template a new charm' stuff but the readme isn't helpful atm and wasn't sure how best to install it. Figured I'd pull down the source and install into a virtualenv, but the python package doesn't do deps, etc
[01:16] <marcoceppi> rick_h_: I'll likely create a python-charmhelpers package for just the python specific bits
[01:16] <marcoceppi> rick_h_: oh, haha, that's because you don't install it
[01:16] <rick_h_> https://juju.ubuntu.com/docs/authors-charm-writing.html doesn't use it from what I can tell
[01:16] <marcoceppi> it's just "embedded" in charms ATM
[01:17] <marcoceppi> and by charms, I mean Python charms
[01:17] <rick_h_> marcoceppi: so I thought there was a 'create a new charm from a sample tepmlate' command?
[01:17] <marcoceppi> rick_h_: yeah, `juju charm create <name>`
[01:17] <rick_h_> or is that somewhere else then before you get to the charm/python helpers in there
[01:17] <marcoceppi> but that's only one template
[01:17] <marcoceppi> rick_h_: charm-tools
[01:17] <marcoceppi> that's packaged and should be in saucy/juju stable ppa
[01:17] <rick_h_> marcoceppi: ah, /me didn't realize there was charm-tools and charm-helpers
[01:18] <marcoceppi> rick_h_: but it's only one template, and it's a very light weight bash template
[01:18] <rick_h_> they kind of blurred into one on me
[01:18] <marcoceppi> rick_h_: charm-tools is for stuff outside of charms, charm-helpers is for stuff inside of charms
[01:18] <rick_h_> marcoceppi: ok, well I guess if you wanted me to test out writing a new charm from scratch, where should I be starting to test what we tell everyone to do?
[01:19] <rick_h_> marcoceppi: ok, I'll try to see if I can at least pull some readme updates that make that more clear.
[01:19] <marcoceppi> rick_h_: Follow the docs, though I don't think it has charm-tools syntax in it yet, evilnick should be adding that soon. Basically, what I tell people during charm schools is: "Add ppa:juju/stable, apt-get install charm tools, run juju charm create <name>"
[01:20] <marcoceppi> rick_h_: https://juju.ubuntu.com/docs/tools-charm-tools.html
[01:20] <rick_h_> marcoceppi: yea, that's not in the doc on charm-writing ^^
[01:20] <marcoceppi> rick_h_: right, evilnick has a task to fix that
[01:20] <rick_h_> ok cool
[01:20] <marcoceppi> I can ping you once it's updated if you want to give it a go?
[01:20] <marcoceppi> s/\?//
[01:21] <rick_h_> marcoceppi: ok, we'll see.
[01:22] <rick_h_> marcoceppi: so does charm-helpers have a doc listing the api bits it provides for charm writing?
[01:22] <marcoceppi> rick_h_: not that I know of. It's pretty much read the source.
[01:22] <rick_h_> marcoceppi: ok can do
[01:22] <marcoceppi> rick_h_: we did an intro charm school about it. Part of packaging it will be to document it
[01:23] <marcoceppi> rick_h_: let me know any and all feedback on the process. It's rough right now so outside opinions on the process are so very welcomed1
[01:24] <rick_h_> marcoceppi: yea, will do. It's been a while since I tried to charm up my app so starting over vs updating the old code and will go through the process
[01:25] <marcoceppi> rick_h_: you going to write the charm in Python?
[01:26] <rick_h_> marcoceppi: that's the plan
[01:26] <rick_h_> marcoceppi: for https://github.com/mitechie/bookie
[01:26] <marcoceppi> rick_h_: cool, the code in "core" package of charm-helpers will likely help you the most
[01:27] <marcoceppi> rick_h_: you might also want to watch the charm-helpers charm school, it goes over some of the more commonly used charm-helpers
[01:28] <rick_h_> marcoceppi: k, so charm-tools isn't in the dev ppa? I've got 0.3 from there, but looks like 1.0 is out?
[01:28] <marcoceppi> rick_h_: charm-tools is in ppa:juju/stable (and should be in saucy)
[01:28] <marcoceppi> let me check saucy
[01:29] <marcoceppi> yeah, it's in saucy
[01:29] <rick_h_> marcoceppi: ok, this is a raring desktop I'm running on atm. Haven't updated the desktop, only laptop yet. It's running the juju/devel ppa
[01:29] <marcoceppi> rick_h_: ah, yeah all the tools for juju are in ppa:juju/stable
[01:30] <rick_h_> marcoceppi: ok, looks like I've got bigger fish to fry to get going then.
[01:30] <marcoceppi> rick_h_: it's save to have that and devel ppa on your machine, you'll always get latest juju
[01:30] <marcoceppi> safe*
[01:30] <rick_h_> marcoceppi: ah ok
[01:31] <marcoceppi> Yeah, we're making a commitment to have packages of tools in the charm ecosystem in distro, liek charm-tools, amulet, charm-helpers (eventually), deployer, etc
[01:31] <marcoceppi> charm-tools just never got updated for raring
[01:32] <rick_h_> marcoceppi: yea, understand. My fault.
[01:32] <marcoceppi> np np!
[01:32] <marcoceppi> this will definitely be a better trusty story, but it's good to document this in the charm-authors guide. If you're getting tripped up by it others will
[01:34] <rick_h_> README.ex?
[01:53] <routelastresort> is there a good doc w/current info on what I can change to ppa/settings-wise to get all of the latest fixes on saucy??
[02:39] <rick_h_> marcoceppi: well just did bash since I had bash instructions, but http://ec2-54-205-26-172.compute-1.amazonaws.com:6543/ walks through my make commands ok at least it seems
[06:57] <Preytell> I ask this question in the maas channel but maybe it should be here.
[06:57] <Preytell> Morning all, I have a question about maas. I am attempting to put maas regional controller on a machine that how two nics, and I am deploying to hardware that is on a switch with the second nic on the controller.  But when I boot strap it will get to a point where it attempts to wget the tools and it tries to get them from the first nics address and not the nic that it just pxe booted from... Which of course fails.
[06:57] <Preytell> it really juju that is doing this part.
[06:57] <Preytell> it's
[12:40] <rick_h_> jcsackett: around today?
[15:24] <AskUbuntu> JuJu bootstrap error | http://askubuntu.com/q/367340
[20:03] <zradmin> Azendale: Quantum had to be renamed because of a trademark dispute apparently. I am also working on an HA deployment and Neutron doesn't seem to be registering properly as I can't run any commands against the API