[10:29] <cargill> trying to find out why test are failing, when I only do "d = amulet.Deployment(); d.add('postgresql'); d.setup(900)" I get "ValueError: juju-info does not exist for postgresql"
[10:30] <cargill> acually there is an error when installing amulet: File "/usr/lib/python3.4/subprocess.py", line 897, in __del__, TypeError: 'NoneType' object is not callable
[11:01] <Lord_Set> Any of the juju devs available? I have a few questions
[11:04] <mgz> Lord_Set: you should just ask your questions
[11:04] <mgz> when someone is around who knows the answer, they can do so without the extra handshake
[12:03] <hazmat> cargill, oh..
[12:04] <hazmat> cargill, can you pastebin the full error there
[12:05] <cargill> hazmat: http://pastebin.ubuntu.com/7027104/
[12:06] <hazmat> marcoceppi, cargill, looks like a deployer error, doesn't support juju-info implicit provides needed for most subordinates.
[12:06] <hazmat> er.. sorry not deployer error.. amulet error
[12:07] <marcoceppi> hazmat: cargill this is a known issue in amulet being patched and released today
[12:07] <marcoceppi> sorry about that!
[12:12] <Lord_Set> Alright, Does the Juju team already have plans for the integration of the Icehouse release of Openstack. Just curious how some of the competing features will integrate... Since Icehouse brings bare metal provisioning and various other services.
[12:22] <cargill> marcoceppi: great, thanks, how do I find out that it's been released? Will there be a mail to juju@?
[12:22] <marcoceppi> cargill: well, there should be, but patch releases have been landing so fast that I haven't announced 1.3.x yet
[12:22] <marcoceppi> cargill: I can ping you here when it's up
[12:23] <cargill> marcoceppi: cheers
[12:34] <hazmat> Lord_Set, well more specifically the ubuntu server team is already working on icehouse support for our openstack charms
[12:35] <hazmat> Lord_Set, for the core openstack.. ironic is not core openstack.. its an incubator.. ie.. maas, crowbar, cobbler are all other valid bare metal provisioning tools for deploying openstack.
[12:36] <Lord_Set> Ahh ok
[12:37] <hazmat> Lord_Set, ie baremetal is nothing more than a driver config on nova... so yeah.. that's easy to support. (and its not merged yet to nova fwiw https://review.openstack.org/#/c/51328/)
[12:40] <Lord_Set> Cool, thanks for the info.
[13:06] <lazyPower> cargill: how goes your vagrant experience?
[13:36] <cargill> lazyPower: so far little luck on the actual testing, but much better otherwise, my test scripts do get executed now :)
[13:36] <lazyPower> Brilliant :) I'm really happy to hear its moving forwad. New discovery while working through the docs that you may be happy to hear. That 800mb base box can go to /dev/null - the precise basebox works ootb for the problem I was solving
[13:36] <lazyPower> I've updated the docs to reflect that finding as well.
[13:37] <marcoceppi> cargill: I've got an RC in trunk that, if tests okay, will be released
[13:41] <cargill> marcoceppi: that's great
[13:58] <marcoceppi> hazmat: is there anyway to tell deployer to upgrade charm on subsequent runs?
[14:03] <jcastro> hey marcoceppi
[14:03] <jcastro> input/output classes, sounds like a good idea: https://github.com/juju/docs/pull/20/files
[14:04] <marcoceppi> jcastro: yeah
[14:04] <marcoceppi> TheMue, evilnickveitch, and I spoke briefly about it Friday
[14:05] <TheMue> jcastro: you like it? fine
[14:06] <jcastro> marcoceppi, are we going to just do those docs-wide?
[14:06] <marcoceppi> jcastro: it's a helper class for when it makes sense
[14:06] <marcoceppi> like, if you don't demonstarate output, don't stick an input class, etc
[14:06] <TheMue> jcastro: if it's ok with everyone I'll do it
[14:07] <marcoceppi> TheMue: no one will object
[14:07] <marcoceppi> to you doing it
[14:07] <jcastro> marcoceppi, merge that badboy!
[14:07] <marcoceppi> jcastro: in a min
[14:23] <hazmat> marcoceppi, -u
[14:24] <marcoceppi> hazmat: cool, wasn't sure if that would trigger the upgrade charm or not
[14:24] <hazmat> marcoceppi, it doesnt upgrade charm
[14:24] <hazmat> marcoceppi, no upgrade charm support in deployer atm
[14:24] <marcoceppi> hazmat: ah, okay, that's what I was getting at
[14:53] <jcastro> marcoceppi, what's the tldr on wildfly in the store?
[14:53] <marcoceppi> jcastro: look at the queue
[14:53] <marcoceppi> so, soon
[14:53] <marcoceppi> I'm trying to patch a critical bug in amulet
[14:53] <jcastro> ack
[15:16] <jamespage> sinzui, is this really right:
[15:16] <jamespage> 2014-03-03 15:15:52 INFO juju.cmd.juju status.go:96 Status not supported by the API server, falling back to 1.16 compatibility mode (direct DB access)
[15:16] <jamespage> that's a 1.17.4 client talking to 1.17.3 environment...
[15:17] <sinzui> jamespage, I have seen that. 1.17.4 is not compatible with 1.17.3
[15:17] <jamespage> sinzui, ok - just checking :-)
[15:17] <sinzui> jamespage, at least status works with 1.16.6 and 1.18.0 spec
[15:18] <jamespage> \o/
[16:28] <marcoceppi> cargill: 1.3.3 was released, but it's still in queue for the ppa builder
[16:29] <cargill> marcoceppi: thanks
[17:52] <marcoceppi> cargill: 1.3.3 is built and released
[17:52] <cargill> marcoceppi: 1.3.3 works like a charm :) I have a test environment now, so I can do something productive, tomorrow
[17:53] <cargill> (that pun has been overused a bit around here, I suppose)
[18:18] <jcastro> hey marcoceppi, mbruzek, or lazyPower
[18:18] <jcastro> can I get a quick review on this? https://github.com/juju/docs/pull/21
[18:18] <jcastro> I need it in the docs asap
[18:18] <lazyPower> marco's on it
[18:18] <marcoceppi> jcastro: ack
[18:18] <mbruzek> Yeah I can take a look
[18:20] <mbruzek> patch pilots?
[18:20] <jcastro> marcoceppi, I see your issues, fixing.
[18:22] <jcastro> marcoceppi, huh, in the charm instructions we just say to push to LP and sub ~charmers
[18:22] <marcoceppi> jcastro: well, those are wrong as well then
[18:22] <jcastro> hah
[18:22] <jcastro> https://juju.ubuntu.com/docs/authors-charm-store.html
[18:22] <jcastro> so steps 8 and 9?
[18:23] <marcoceppi> that explains why people are having issues getting stuff in the queue
[18:23] <jcastro> ok, fixing
[18:23]  * marcoceppi is glad he subscribed to all bugs in charms
[18:23] <jcastro> ok so submitting fixes is fine
[18:24] <jcastro> because that uses a real MP
[18:24] <marcoceppi> jcastro: right, all you need is the MP
[18:24] <marcoceppi> but for new charms it needs to be a bug, with charmers subscribed to the bug, with you as the author in the assigned field and the lp branch linked
[18:28] <jcastro> anyone remember the way to link to your own account in LP? Something like +me
[18:29] <jcastro> https://code.launchpad.net/people/+me
[18:29] <jcastro> aha!
[18:29] <jcastro> marcoceppi, ok going to fix it in both places.
[18:33] <jcastro> marcoceppi, pushed. What do you think
[18:41] <marcoceppi> jcastro: you also have to assign yourself to the bug
[18:41] <jcastro> huh?
[18:41] <marcoceppi> you have to assign yourself to the bug in lp for it to show in the review-queue
[18:41] <marcoceppi> in addition to linking a branch
[18:42] <jcastro> are you sure on that?
[18:43] <marcoceppi> jcastro: positive
[18:43] <marcoceppi> like, 110%
[18:43] <jcastro> why is that? that makes no sense, the reporter will already get bugspammed
[18:43] <jcastro> jcsackett, can we fix that?
[18:43] <marcoceppi> jcastro: the reporter is not alwasy who is assigned to the bug
[18:44] <jcastro> right, what I am saying is why does the queue need to care if the bug is assigned or not? there's a bug and a branch
[18:44] <marcoceppi> jcastro: idk, didn't make up the rules
[18:46] <jcastro> ok these steps are out of control now
[18:46] <jcastro> all that should be necessary is subscribing ~charmers to a bug to get it in the queue
[18:50] <jcastro> marcoceppi, ok I'm not going to submit a PR for that last but with the reporter, I'm going to just make us fix the queue
[18:50] <jcastro> these steps are already too high-barrier-to-entry
[20:29] <bodie_> any TODOs a newbie should take a crack at to get acquainted with Go?  I'm a pretty good programmer just never used Go seriously
[20:36] <marcoceppi> bodie_: we have a whole list of bugs, not sure if any are tagged papercut though
[20:36] <marcoceppi> bodie_: it might be best to go ask in #juju-dev as that's where a lot of the core developers are chatting
[20:38] <bodie_> I see.  thanks :)
[20:49] <bloodearnest> rick_h_: trying out local charmworld currently
[21:16] <bloodearnest> rick_h_: I'm 99% of the way there, but failing at the last hurdle
[21:17] <bloodearnest> rick_h_: I've set the local juju-gui's charmworld-url to point to the correct ip according to your instructions
[21:17] <bloodearnest> whcih for me is http://10.0.3.217:6543/
[21:18] <bloodearnest> but I'm getting a notification saying: Charm API server did not respond
[21:20] <bloodearnest> rick_h_: also, shouldn't sandbox be true? As I will have no network so actual local deploy's will hang?
[21:23] <bloodearnest> rick_h_: ah - digging into logs, problem is unknown cert on the local charmworld
[21:28] <bloodearnest> rick_h_: aaaand setting secure=False fixes
[21:28] <bloodearnest> sweeet!
[21:28] <bloodearnest> no I just need to wait for ingest :)
[21:42] <bloodearnest> rick_h_: I updated the google doc
[21:50] <rick_h_> bloodearnest: yes, you can set sandbox to be true
[21:50] <rick_h_> bloodearnest: so the question is can you pull up the web front end on the charmworld deployment?
[21:50] <bloodearnest> rick_h_: yes
[21:50] <rick_h_> ah, ok so you got it
[21:50] <rick_h_> ok coolio
[21:51] <bloodearnest> rick_h_: yeah, it needed secure=False - have added that to the doc
[21:51] <rick_h_> ah ok
[21:51] <bloodearnest> rick_h_: it's pretty sweet :)
[21:51] <rick_h_> bloodearnest: on the charmworld side?
[21:51] <rick_h_> bloodearnest: coolio, glad it's working out
[21:51] <bloodearnest> rick_h_: no, on juju-gui/squistart side
[21:51] <bloodearnest> gah
[21:52] <bloodearnest> quickstart
[21:52] <rick_h_> oh
[21:52]  * rick_h_ missed that I guess. cool then
[21:52] <rick_h_> oh I probably did it via the gui vs quickstart. Oh well my bad
[21:53] <bloodearnest> rick_h_: easy fix :)
[21:53] <rick_h_> bloodearnest: thanks for finding/updating.
[21:53] <bloodearnest> rick_h_: hm - does the gui support manual provisioning yet?
[21:53] <rick_h_> bloodearnest: no, that's the work we're doing now
[21:54] <rick_h_> bloodearnest: it does support local charms though. Might be useful if you want to deploy something, just download a zip of the charm
[21:54] <rick_h_> bloodearnest: but no icons and such for local charms atm, so it's still not going to be the amazing demo yet
[21:54] <bloodearnest> rick_h_: ooooh - is that github import in trunk yet?
[21:54] <bloodearnest> that would be a cool demo
[21:55] <bloodearnest> ah - you downloaded the zip from git hub, IIRC?
[21:55] <rick_h_> bloodearnest: so if you go to github, and click "download zip" and drop that into the gui it'll deploy. We've been using https://github.com/hatched/ghost-charm as a sample
[21:55] <rick_h_> bloodearnest: but it requires really new juju to have it auto find the charm in the directory tree
[21:55] <rick_h_> bloodearnest: so heads up if you try it to test it out first
[21:56] <bloodearnest> rick_h_: am on 1.17.2 I think
[21:56] <rick_h_> the first release wanted all the charm files to be in the first directory of the zip, later they added the ability to walk the zip to find it
[21:56] <rick_h_> bloodearnest: ok, might need .3, not sure
[21:56] <bloodearnest> rick_h_: ack, will try
[21:57] <bloodearnest> rick_h_: do you *need* juju gui in the charmworld env? If you didn't have it in the bundle, you could add the demo gui in the same env?
[21:57] <bloodearnest> no?
[21:57] <rick_h_> bloodearnest: right, but the goal is to hide charmworld during demo
[21:57] <rick_h_> bloodearnest: we don't want to spread that too much and it keeps the demo environment clean
[21:58] <bloodearnest> rick_h_: good point
[21:58] <rick_h_> bloodearnest: yea, the instructions are drawn up for salesly people and such as well. So you can tweak to your demo you need
[22:00] <bloodearnest> rick_h_: another question - in the demo env, the juju-gui charm doesn't have an icon
[22:28] <bloodearnest> I now have 4 bootstrapped and running local provider juju envs, and one manual, running on my laptop
[22:28] <bloodearnest> :)
[22:33] <rick_h_> bloodearnest: lol
[22:34] <rick_h_> bloodearnest: hmm, the gui charm doesn't have an icon? Oh, it must not be ingested in charmworld yet.
[22:34] <rick_h_> bloodearnest: all icons come from charmworld
[22:49] <dalek49> Hi guys, I can't figure out how to make `juju debug-log` run
[22:49] <dalek49> (in local mode)
[22:50] <dalek49> I'm getting "Permission denied (publickey,password)."
[22:54] <rick_h_> dalek49: debug log doesn't currently work for the local provider
[22:56] <dalek49> found it in the docs. https://juju.ubuntu.com/docs/config-LXC.html#debug-log