[00:23] <marcoceppi> paulczar_: no
[00:24] <marcoceppi> lazyPower: thanks for the bugs o/
[01:10] <lazyPower> marcoceppi: anytime
[01:10] <lazyPower> I'm going to have more coming, I'm going to start by charming hubot.
[01:10] <lazyPower> helllooooo node
[01:10] <lazyPower> Wrapping up some template edits, then back to charm school
[01:14] <marcoceppi> lazyPower: there's a node.js charm, similar to the rails charm, you might want to check it out
[01:18] <lazyPower> Thats the plan :)
[03:09] <stokachu> fyi: https://juju.ubuntu.com/docs/config-environments.html seems to be a broken link
[03:10] <stokachu> was from the getting started page https://juju.ubuntu.com/docs/getting-started.html
[03:59] <stokachu> https://juju.ubuntu.com/docs/howto.html both deploy docs point to nodejs
[03:59] <stokachu> ah i see where i can just branch and fix it
[03:59] <stokachu> ill do that
[04:02] <davecheney> stokachu: grab charm tools from
[04:02] <davecheney> ppa:juju/stable
[04:02] <davecheney> then you can do
[04:02] <davecheney> mkdir charms
[04:02] <davecheney> sorry
[04:02] <davecheney> mkdir charms/precise
[04:02] <davecheney> cd charms/precise
[04:03] <davecheney> charm get nodejs
[04:03] <davecheney> play with it
[04:03] <davecheney> then
[04:03] <davecheney> juju deploy --repository=$(pwd)/../.. local:precise/nodejs
[04:03] <davecheney> you can also switch to your local version of the charm if you have the charmstore one deployed
[04:04] <stokachu> davecheney: ah is this related to the online documentation? thats what i was referring to
[04:04] <stokachu> davecheney: was going to update the docs as some of the urls are incorrect
[04:05] <davecheney> stokachu: cool
[04:06] <davecheney> docs are in a branch in lp:juju-core
[04:06] <stokachu> davecheney: cool thanks checking it out locally now
[04:06] <stokachu> are MP's the preferred way or does a bug need to be linked to it?
[04:08] <davecheney> stokachu: we'll take anything we can get
[04:08] <stokachu> davecheney: sounds good :D will get those done in a few minutes
[04:41] <stokachu> so many broken links, should I not worry about them under the assumption those pages will eventually be added? or should i remove the link references until a page is created
[04:41] <stokachu> for example, https://juju.ubuntu.com/docs/troubleshooting.html
[04:52] <stokachu> davecheney: ok got a MP created for my initial pass-through
[15:00] <yolanda> hi, i have a subordinate charm that will be reused for 3 different services. Do i have to deploy a different subordinate charm for each of the services?
[15:24] <jamespage> yolanda, juju deploy subordinate subordinate-instance-1
[15:24] <jamespage> yolanda, juju deploy subordinate subordinate-instance-2
[15:24] <jamespage> yolanda, juju deploy subordinate subordinate-instance-3
[15:25] <yolanda> jamespage, ok, that's what i first tried
[15:25] <yolanda> but i have a problem
[15:25] <jamespage> the last parameter names the instance of the subordinate service
[15:25] <yolanda> i need a way to discriminate between if the relation is for one charm or another
[15:25] <yolanda> i have a configurator charm, that updates config for gerrit, zuul, jenkins
[15:26] <yolanda> so i will have to create 3 different interfaces then?
[15:27] <yolanda> we have something common for the 3, and then we have something like: if relation_ids('gerrit-configurator') : ...
[15:28] <yolanda> then i find that when i associate that zuul it also has the gerrit-configuration relationship
[15:29] <yolanda> so i'll try with 3 different subordinates
[15:51] <stokachu> hi, just fyi i filed an MP for some juju-docs corrections
[16:07] <marcoceppi> stokachu: thanks for the submission!
[16:12] <jamespage> yolanda, yeah - you would need to implement three differently typed interfaces
[16:12] <yolanda> jamespage, ok, that works, but i wasn't sure if that was the right way
[17:26] <jcastro> heya jamespage
[17:26] <jcastro> Reminder that you're down for reviewer this week
[17:27] <jcastro> m_3: marcoceppi: we're still in a hole if you guys have time to dig in
[17:27] <jcastro> negronjl: We miss you. :)
[17:28] <negronjl> jcastro: lol ... miss you too people ... but they have me tied down like a slave here :/
[17:34] <marcoceppi> jcastro: ack, I've got amulet to release, but I'll poke at the queue with a hard stick soon
[17:49] <stokachu> marcoceppi: thanks, ive got a big project im working on that will drive more documentation to the public facing juju site
[18:07] <m_3> jcastro: ack
[19:15] <zradmin> anyone on?
[19:16] <marcoceppi> zradmin: yup, though it's best to just ask your question as people might not be here right this second
[19:22] <zradmin> Thanks marcoceppi, I'm still having the same issue with quantum not functioning properly. It brings up all of the other bridges except br-ex on eth1 but I have confirmed that I can manually assign an address to eth1 and talk on the external network. Is there a log file I can check for openvswitch (or maybe the charm setup log) that I can check to see why its failing to setup?
[19:32] <rick_h_> sinzui: can you join #juju-gui for a sec? We've got a promulgation question on bundles and how to link branches to series
[19:32]  * sinzui #juju-gui
[19:45] <sidnei> jcastro: around?
[19:51] <sidnei> or marcoceppi
[19:55] <marcoceppi> sidnei: hey
[19:56] <sidnei> marcoceppi: hey, just realized https://juju.ubuntu.com/Events/ is missing the charm school & talk im giving at PythonBrasil
[19:56] <sidnei> not sure how to get it updated (even if quite late by now )
[19:56] <marcoceppi> sidnei: we can usually do it but we're looked out ATM
[19:57] <sidnei> ok, no problem
[20:01] <jcastro> sidnei: I'm getting on a call, you need to mail Peter Mahnke to add it
[22:24] <arosales> hazmat, what was the cavet for local provider on systems without swap?
[22:50] <hazmat> arosales, with encrypted home dirs.. JUJU_HOME env var needs to be set to not be in $HOME
[22:50] <hazmat> arosales, else reboot won't work and env will need be to destroyed before using
[22:52] <arosales> hazmat, but other than than swapless system is ok with local?
[22:53] <hazmat> arosales, should be fine given enough mem to run core.. what's the context?
[22:53] <hazmat> er. to run core and mongo
[22:55] <arosales> hazmat, just my fragmented memory recalling a caveat with swapless systems
[22:56] <arosales> hazmat, I think I just may be hitting some if the issues thumper has recently fixed
[22:56] <hazmat> arosales, i can't think of a reason why a system wouldn't have swap
[22:58] <arosales> hazmat, ok and thanks for the reply
[22:58] <hazmat> i mean.. for a laptop.. for example no suspend to disk.. no virtual memory.. you get oom to kill your processes instead overcommit.
[23:00] <lazyPower> marcoceppi: Juju stole the show at work with the GUI. I used screenshots to present it initially, I have a functional demo scheduled next week.
[23:13] <bic2k> I have an issue where the juju tools can no longer communicate with our bootstrap server (which is returning 503). SSH'ed on to the server, only thing that is odd is that the /var/log/juju/all-machines.log is rolling out tons of text, probably eat up all the free space in an hour or so. This is on AWS with juju-1.13.1-unknown-amd64 on the client and 1.14.1-precise-amd64 on the server
[23:14] <bic2k> ls -l
[23:24] <bic2k> and nvm. Turns out my JUJU_HOME was set differently after a .bashrc change
[23:27] <sarnold> interesting, thanks..
[23:29] <zradmin> bic2k: i had the same issue, you need to upgrade juju to at least 1.13.3.1 to get rid of that error, both on your main node and the bootstrap node
[23:30] <bic2k> zradmin: Ya, I'm stuck on whatever is ported to brew for now. Looks like I'll be able to work around it for now