[00:36] <jrwren_> marcoceppi: we were going to look at that yaml thing tonight. I'm exhausted. Another time?
[00:36] <marcoceppi> jrwren_: yes, another time indeed
[08:55] <james_w> hello, how do I upgrade-charm from my locally modified copy when I initially deployed from the charm store?
[10:36] <marcoceppi> james_w: hello, you can use the --switch flag
[11:31] <james_w> marcoceppi: thanks
[12:17] <benji> dpb1: /quit
[12:17] <benji> pfft
[13:23] <hazmat> mbruzek, the other mp is referenced in the bottom of that first's comments
[13:23] <mbruzek> hazmat, got it.
[16:27] <aisrael> Using vagrant for work on a charm. I have it and postgresql deployed, and add a relation between the two. If I ssh to my charm's machine and try to use psql to connect to postgresql, using the relation's private-address/user/password, it's failing, saying there's no entry in pg_hba.conf.
[16:28] <aisrael> I'm connecting from 10.0.3.232, but postgresql is seeing it as 10.0.3.1
[16:28] <aisrael> Should I be able to connect from machine to machine that way?
[16:40] <html> well  you got to first figure out why the ip is not working- then move on to the config file.
[16:40] <html> aisrael,
[16:55] <aisrael> thanks html. I'll dig in deeper and see what I can find.
[16:56] <html> aisrael,  im just a noob that is saying the basics
[16:57] <aisrael> Understood :)
[16:58] <html> aisrael,  luckly you that you got juju working- i dont know or even get it working
[16:59] <html> i wish :/
[17:07] <aisrael> I'm still learning myself, but this is a good place to ask questions if you're stuck on something.
[17:19] <lazyPower> aisrael: are you executing that from the host, the vagrant virtual environment, or from the postgresql lxc container running in the vagrant environment?
[17:34] <Flint_> Hi Bruzer
[17:34] <mbruzek> Hello Flint_
[17:34] <Flint_> how goes the battle?
[17:35] <Flint_> ..er work
[17:35] <mbruzek> round and round.
[17:36] <Flint_> do you have bluetooth with your linux box?
[17:36] <Flint_> ...looking for a stable setup
[17:37] <mbruzek> Yes I have bluetooth working on Ubuntu 14.04
[17:37] <mbruzek> Flint how would you plan to use it?
[17:38] <mbruzek> Flint_, although I suspect that depends on the hardware using it.  I am using a Thinkpad with an intel wireless + bluetooth card.
[17:39] <aisrael> lazyPower: inside vagrant. It fails the same way if I juju ssh mycharm/0 and try to connect, or via debug-hook on db-relation-joined
[17:40] <lazyPower> aisrael: have you confirmed the postgresql service is running on postgresql/0?
[17:40] <Flint__> sorry it lagged
[17:41] <Flint__> I'm suspecting its my headset going bad
[17:42] <Flint__> although Motorola should be reliable
[17:42] <mbruzek> Flint__, I use a bluetooth mouse when I travel and it works pretty well.
[17:43] <mbruzek> Flint__, trouble connecting with your computer or having trouble keeping it connected?
[17:43] <Flint__> keeping it connected
[17:43] <Flint__> I have seen a decrease in battery life, so it might be the root failure
[17:45] <Flint__> I'm setting up Kubuntu 14.04, and had heard that some bluetooth drivers weren't up to speed for a while.
[17:45] <mbruzek> Flint__, Well that actually is something I noticed.  The bluetooth mouse's battery status is not correctly reported in linux.
[17:46] <mbruzek> Flint__, when I connect the mouse it reads 0% charged, and they are fresh batteries
[17:47] <aisrael> lazyPower: Yep. I suspect it might be vagrant at fault, with the way it's routing requests between machines
[17:47] <Flint__> ok, thanks
[17:47] <lazyPower> aisrael: hmm.. its all being routed through a local loopback interface though.
[17:48] <lazyPower> are you running 2 vagrant boxes, with services spread between them?
[17:49] <aisrael> Just one vagrant box for all the services. I pretty much followed the juju vagrant workflow.
[17:50] <lazyPower> ok, that's the recommended method to use the vagrant box - interesting that you're having an issue connecting though. If you are stuck in a blocked state, file a bug aganist the pgsql charm and assign it to me please. I'll investigate it at my earliest availability
[17:51] <lazyPower> (i'm lazypower on launchpad as well)
[17:52] <aisrael> Will do, thanks.
[17:55] <marcoceppi> aisrael: did you get your psql figured?
[17:56] <marcoceppi> aisrael: you need to vagrant ssh, then you'll probably need to `juju ssh` in to the unit of the charm you're writing
[17:56] <marcoceppi> that should give you the proper access to psql
[17:56] <marcoceppi> there's also a psql charm you could deploy which will give you console access
[17:57] <aisrael> marcoceppi: not yet. I did those steps, but it appears that postgresql/0 sees the connect coming from the gateway, not the unit ip
[17:57] <marcoceppi> aisrael: so you're inside your deployed LXC machine? interesting
[17:57] <marcoceppi> sounds like a weird artifact of the local provider
[17:57] <aisrael> Correct.
[17:58] <aisrael> I'm walking through the config(s) to see if anything sheds some light on it
[18:01] <Flint_> sorry it cut em out again
[18:18] <Flint_> getting W: Failed to fetch http://ppa.launchpad.net/ubuntu-audio-dev/ppa/ubuntu/dists/trusty/main/binary-i386/Packages
[18:33] <marcoceppi> Flint_: I think you're in the wrong room
[18:34] <Flint_> nah, just tried the laod instructions
[18:35] <mbruzek> Flint_, what operation generated that error?
[18:35] <Flint_> sudo apt-get update && sudo apt-get install juju-core
[18:35] <sarnold> it's just a warning
[18:36] <sarnold> and the failure of a ubuntu-audio-dev PPA is unlikely to have an influence on how well juju works :)
[18:36] <mbruzek> Flint_, I found that that ppa does not yet have a trusty release.
[18:36] <Flint_> ah ok
[18:37] <mbruzek> Flint_, I suspect that was installed for an older version of Ubuntu?
[18:37] <Flint_> trusty, i think so
[18:39] <Flint_> although the documents say it should have been final realease in april
[18:48] <lazyPower> marcoceppi: i'm having cranial flatulence. If we exit(0) from a hook due to the environment not being ready - how do we re-execute the hook context? we have to relation-set on the initiator dont we?
[18:49] <marcoceppi> lazyPower: well, yes, each relation-set will re-execute the -changed hook for the opposing unit in the relation
[20:47] <natefinch> marcoceppi: how do I get help on juju charm subcommands?  juju help charm generate,  juju charm help generate, juju charm-help generate, charm-help generate, juju-charm help generate  all fail
[20:48] <natefinch> marcoceppi: nevermind... juju charm generate --help works.
[21:58] <stokachu> marcoceppi, this recent change in mysql http://manage.jujucharms.com/charms/trusty/mysql, pretty much breaks anything that was using juju add-relation nova-compute mysql
[21:58] <stokachu> since now it is required to set the interface we want
[22:04] <jrwren_> stokachu: what recent change?
[22:09] <stokachu> jrwren_, https://bazaar.launchpad.net/~charmers/charms/trusty/mysql/trunk/revision/124
[22:09] <stokachu> added an additional interface
[22:10] <jrwren_> stokachu: don't know about that one, sorry.
[22:32] <hazmat> stokachu, its not about the additional interface surely but the multi-request around shared db
[22:33] <stokachu> hazmat, either case you used to be able to do juju add-relation nova-compute mysql
[22:33] <hazmat> stokachu, ack, change broke extant
[22:33] <hazmat> but diagnosis is the key to recovery
[22:34] <stokachu> indeed
[22:35] <hazmat> stokachu, what breaks exactly.. i don't see additional interface of note
[22:35] <stokachu> it doesn't know whether you want shared-db or nrpe-external-master
[22:36] <hazmat> ugh
[22:36] <hazmat> fair enough
[22:38] <hazmat> stokachu, nova-compute is wrong btw
[22:39] <hazmat> the only charms that can require on a container scoped relation are subordinates
[22:39] <hazmat> the hosts are all providers
[22:39] <stokachu> jamespag`, ^
[22:40] <hazmat> stokachu, he's on vacay this week
[22:40] <stokachu> ah
[22:40] <hazmat> since its broken anyways the simplest fix is remove that line from nova-compute
[22:41]  * hazmat runs blame out of curosity
[22:43] <hazmat> about a year ago bundled in an ancilliary change
[23:10] <rharper> is it ok to mix juju 1.20.1 and 1.20.5 ?  the state-server is 1.20.1, the allocated nodes (maas env) are getting 1.20.5 --