[06:45] <herophuong_> Hi
[06:45] <herophuong_> I need some help on using juju on local machine
[06:45] <herophuong_> I've followed the get started page on juju.ubuntu.com
[06:46] <herophuong_> but the agent-state of mysql/wordpress keeps on 'pending'
[06:46] <herophuong_> when I manually start the container
[06:46] <herophuong_> it says 'Permission denied - Failed to make / rslave'
[06:47] <herophuong_> what should I do now?
[09:52] <bloodearnest> heya, using pyjuju and lxc, is there anyway to disable using apt-cacher-ng?
[09:52] <bloodearnest> is the incoming lxc support for gojuju using it too?
[10:36] <bloodearnest> FWIW, adding "Acquire::HTTP::Proxy::private-ppa.launchpad.net "DIRECT";' into /etc/apt/apt.conf.d/97disable-proxy-ppa did what I needed
[12:23] <marcoceppi> bloodearnest: I don't think it will, the LXC support is being re-written (and re-architected) but I can't say for sure either way
[12:25] <bloodearnest> marcoceppi, ok thanks. Looking forward to trying it out
[12:25] <marcoceppi> bloodearnest: it's been a long wait, but I hear it's landing really soon
[14:06] <marcoceppi> Is there anything I need to do in order to get websockets to work in juju-core?
[14:25] <stokachu> using the apache2 charm how would i install files to that instance after deployment?
[14:31] <marcoceppi> stokachu: if there isn't a configuration option for like a files repo, then juju scp would be your next bet
[14:32] <stokachu> marcoceppi: ok thanks ill look at that
[14:32] <noodles775> Any charmhelpers reviewers able to look at these two MPs?
[14:32] <noodles775> https://code.launchpad.net/~michael.nelson/charm-helpers/ensure_etc_salt_exists/+merge/170546
[14:32] <noodles775> https://code.launchpad.net/~michael.nelson/charm-helpers/namespace-relation-data/+merge/170575
[14:36] <jcastro> evilnickveitch: both local and azure are landing in 1.11.3
[14:36] <jcastro> we should probably sync with thumper or mramm as far as updating the docs, etc.
[14:37] <mramm> well azure is sort of not really there yet
[14:37] <mramm> I think
[14:37] <evilnickveitch> jcastro, yeah, I saw that. I will have to go back and put in all those references to LXC i took out :)
[14:37] <jcastro> oh, I saw it in the release notes draft
[14:37] <evilnickveitch> it is in the release notes
[14:37] <mramm> it will bootstrap
[14:37] <jcastro> oh, we should be explicit about that then
[14:37] <mramm> but it will not deploy services or something like that
[14:38] <evilnickveitch> okay, we should mention it as experimental
[14:38] <mramm> I will check in and make sure the notes get updated
[14:39] <jcastro> I mean we could just mark it tech preview or something
[14:42] <jcastro> evilnickveitch: can you mail cheney and try to coordinate landing the docs at about the same day he releases? We should do a nice announcement, etc.
[14:42] <evilnickveitch> jcastro, ack#
[14:43] <marcoceppi> mramm: what's the version schema, shouldn't a new provider bump to 1.12.0 ?
[14:44] <mramm> x.odd are development releases
[14:44] <mramm> x.even are stable releases
[14:45] <mramm> major version upgrades have some some sort of backwards incompatibility in API
[14:46] <marcoceppi> mramm: awesome, thanks!
[14:57] <ehg> hi guys, what should happen when i assign an elastic IP to an ec2 instance? should goju pick it up?
[14:59] <marcoceppi> ehg: unit-get public-address will work, but it might not properly appear in the status output, I believe the public address is cached in that output
[14:59] <marcoceppi> basically, everything will work. Only juju status might not reflect the change
[15:02] <ehg> marcoceppi: ah ok. i'm asking because we rebooted an instance and it lost its elastic ip, just wondering if that's juju doing it, or something we're doing wrong
[15:02] <marcoceppi> ehg: no, that's actually something that EC2 does
[15:02] <marcoceppi> IIRC
[15:02] <ehg> ah - thanks :)
[15:03]  * ehg <-- ec2 n00b
[15:03] <ehg> is there any way to clear the juju cache?
[15:03] <marcoceppi> ehg: what do you mean by juju cache?
[15:03] <marcoceppi> For the juju status output?
[15:03] <ehg> and juju ssh
[15:04] <marcoceppi> Ah, I believe if you just use juju ssh <machine-number> instead of the service/unit denomination it'll use the correct address
[15:04] <marcoceppi> Otherwise, not that I know of
[15:05] <ehg> i seem to remember juju picking up the elastic public address, i can't remember what i did to get it to do that, maybe restarting some jujud
[15:06] <marcoceppi> ehg: it's possible, I've not really bothered too much with that though. I know the machines output will have the correct address, just the unit's public-address isn't updated (this was also several versions of juju ago that I came across it, haven't dug much in to it since)
[15:07] <ehg> marcoceppi: fair enough. i'll search for/open a bug - thanks :)
[15:28] <jcastro> hey evilnickveitch
[15:28] <jcastro> any thoughts on the developer.u.c resyndication?
[15:28] <jcastro> for the docs etc?
[15:30] <evilnickveitch> jcastro, tbh i haven't looked at it yet, busy rewriting the author docs
[15:31] <jcastro> ok
[15:49] <jcastro> charmers sync up on G+ in 10 minutes!
[15:49] <jcastro> I'll be updating ubuntuonair.com too for people who want to follow along
[15:50] <pavel> jcastro, hello, can you give me a link?
[15:50] <jcastro> I am firing it up now
[15:50] <jcastro> I'll paste it in here in a minute
[15:51] <pavel> jcastro, ok thanks
[15:52] <arosales> jcastro, any way developer.u.c can just pull from the docs bzr branch?
[15:52] <jcastro> yeah probably
[15:52] <jcastro> I think I might just selectively pull
[15:52] <arosales> that we it is just happens with out us having to maintain another location.
[15:53] <arosales> s/we/way/
[15:53] <jcastro> don't worry, I'll make sure we don't do that
[15:53] <jcastro> anything I figure out will be based on one canonical location of the docs
[15:53] <arosales> jcastro, much appreciated
[15:54] <jcastro>  
[15:54] <arosales> evilnickveitch, fyi for Azure it probably won't need any changes to the docs yet. I"ll confirm with the red squad, but I don't think it is ready for the docs just yet.
[15:54] <jcastro> https://plus.google.com/hangouts/_/4e37f79d5ad469b475340d826e93cf3df4d64227?authuser=0&hl=en
[15:54] <jcastro> for anyone wanting to participate today ^^^^
[15:54] <jcastro> in about 5 minutes
[15:55] <jcastro> everyone else if you just want to listen  in on the charm meeting you'll just go to ubuntuonair.com
[15:58] <marcoceppi> http://pad.ubuntu.com/7mf2jvKXNa
[16:31] <kirkland> fyi, 404: https://juju.ubuntu.com/Interfaces/mount
[16:32] <kirkland> I'm trying to use nfs and the mount interface
[16:32] <kirkland> there's a number of pages that link to that address
[17:05] <bbcmicrocomputer> marcoceppi: thanks for reviewing the liferay charm :)
[17:05] <marcoceppi> bbcmicrocomputer: no problem!
[17:07] <jcastro> evilnickveitch: where do people file bugs on the maas docs?
[17:08] <evilnickveitch> jcastro, the MAAS docs are included in the source, so they just file them on the project page
[17:10] <evilnickveitch> jcastro, why? do you have a bug?
[17:10] <jcastro> someone pinged me
[17:10] <jcastro> He's filing a bug
[17:11] <evilnickveitch> cool
[17:17] <jcastro> https://bugs.launchpad.net/maas/+bug/1202314
[17:17] <_mup_> Bug #1202314: discrepancy between docs and behavior <MAAS:New> <https://launchpad.net/bugs/1202314>
[17:18] <jcastro> evilnickveitch: ^
[17:54] <jcastro> http://blog.scraperwiki.com/2013/07/17/weve-migrated-to-ec2/
[17:54] <jcastro> \o/ and they're using Juju!
[17:56] <marcoceppi> jcastro: Awesome!
[18:22] <arosales> go ScraperWiki !
[18:22] <arosales> jcastro, thanks for the link
[18:25]  * marcoceppi compiles latest juju, looks forward to local!
[18:34] <stokachu> marcoceppi: local w/lxc?
[18:40] <marcoceppi> stokachu: local lxc and juju-core!
[18:41] <stokachu> marcoceppi: nice! let us know how it goes i may try it out
[18:59] <jcastro> marcoceppi: LXC report please!
[18:59] <jcastro> also, liferay
[18:59] <marcoceppi> meeting
[19:22] <jcastro> hey marcoceppi
[19:22] <marcoceppi> jcastro: yo
[19:22] <jcastro> kirkland wants to do shared NFS storage like we do for wordpress for his charm
[19:22] <kirkland> marcoceppi: howdy
[19:23] <marcoceppi> kirkland: o/
[19:23] <kirkland> marcoceppi: yeah, I need a basic charm, that uses NFS, for read/write shared filesystem storage across all units
[19:24] <marcoceppi> kirkland: WordPress implements the "mount" interface http://jujucharms.com/interfaces/mount which is provided by the nfs charm (and a few others not in the store yet)
[19:24] <marcoceppi> kirkland: did you just need an example, or did you have a question in particular?
[19:25] <kirkland> marcoceppi: I'd like a charm to clone, as a template
[19:25] <kirkland> marcoceppi: and then modify to my needs
[19:25] <kirkland> marcoceppi: how do I branch the wordpress charm?
[19:26] <marcoceppi> kirkland: if you have charm-tools installed you can use `charm get wordpress` otherwise you can use bazaar with `bzr branch lp:charms/wordpress`
[19:26] <marcoceppi> The WordPress charm is mildly confusing in it's setup. It's the result of pushing bash to it's limits as a language
[19:28] <kirkland> marcoceppi: is there a simpler charm that uses nfs for me to start from, then?
[19:28] <marcoceppi> OwnCloud might be a better example of a more wholistic view on how to handle the mount interface http://jujucharms.com/charms/precise/owncloud though it doesn't do a very good job of data preservation (ie, if the mount relation is broken there's really no data recovery and the mount point isnt removed)
[19:29] <marcoceppi> kirkland: owncloud is the only other charm that's actually in the store that uses the mount interface, so it's your next bet
[19:30] <jcastro> nfs shared storage seems like something we would do as a "cookbook snippet" kind of thing for charm authors
[19:30] <melmoth> actually, there are others http://jujucharms.com/interfaces/mount
[19:31] <marcoceppi> melmoth: those aren't actually reviewed though, so not "officially" in the charm store
[19:32] <marcoceppi> Definitely exist as examples, but take them as you would a grain of salt
[19:35] <kirkland> jcastro: yeah, I would think nfs and mysql should be the two brain dead simple integration points
[19:36] <jcastro> there's ceph in there too if you want to totally use a naval cannon on a nail.
[19:38] <AskUbuntu> Is it possible to use Juju without having sudo access on local machine? | http://askubuntu.com/q/321252
[19:39] <jcastro> heh, timely question
[19:39] <marcoceppi> jcastro: got juju-core compiled, about to give local access a go
[19:40] <jcastro> marcoceppi: save your history so we can use that as the docs for local
[19:40] <marcoceppi> jcastro: ack
[19:42] <jcastro> marcoceppi: toss it in an etherpad when you're done, I'd like to try it too
[19:43] <marcoceppi> jcastro et all, here's the compile instructions: http://pad.ubuntu.com/rzudQRvsmw
[19:47] <jcastro> on it now!
[19:53] <marcoceppi> jcastro: havent' gotten it to work for me yet
[19:53] <marcoceppi> but those are the compile instructions
[19:53] <jcastro> I am still downloading
[20:06] <kirkland> marcoceppi: okay, I've written my charm;  it's in a directory locally;  what's the current syntax for deploying from my local directory?
[20:06] <kirkland> error: Environments configuration error: /home/kirkland/.juju/environments.yaml: environments.openstack.default-image-id: required value not found
[20:07] <kirkland> meanwhile, juju also told me that that was deprecated
[20:07] <marcoceppi> kirkland: what version of juju are you using, what provider are you using?
[20:07] <marcoceppi> `juju version` (or `juju --version`)
[20:07] <kirkland> marcoceppi: ii  juju-core                                 1.11.2-3~1414~raring1                amd64        Juju is devops distilled
[20:07] <kirkland> wait
[20:08] <kirkland> kirkland@x230:~/src/charms$ which juju
[20:08] <kirkland> /usr/bin/juju
[20:08] <kirkland> kirkland@x230:~/src/charms$ what-provides juju
[20:08] <kirkland> juju-core: /usr/bin/juju
[20:08] <kirkland> kirkland@x230:~/src/charms$ juju --version
[20:08] <kirkland> juju 0.7
[20:08] <kirkland> ???
[20:08] <marcoceppi> kirkland: that explains that
[20:08] <marcoceppi> and jcastro says update-alternatives aren't important
[20:08] <kirkland> marcoceppi: shouldn't those two conflict?
[20:09] <roaksoax> i think jamespage is handling the packaging
[20:09] <roaksoax> now
[20:09] <kirkland> jamespage: !
[20:09] <kirkland> :-)
[20:10] <kirkland> marcoceppi: okay, I'm purging juju and juju-0.7
[20:10] <marcoceppi> kirkland: no, you'll want to do this: `sudo update-alternatives --config juju`
[20:11] <marcoceppi> just select the proper juju version, 0.7 and 1.X can live side by side
[20:11] <kirkland> marcoceppi: shouldn't I be able to just purge it?
[20:11] <marcoceppi> kirkland: technically, maybe. I'm not sure how the packaing works entirely
[20:11] <kirkland> kirkland@x230:~/src/charms$ sudo update-alternatives --config juju
[20:11] <kirkland> update-alternatives: error: no alternatives for juju
[20:11] <marcoceppi> kirkland: heh
[20:11] <kirkland> marcoceppi: I'm reinstalling
[20:11] <roaksoax> purging it should work
[20:11] <marcoceppi> kirkland: ack
[20:11] <kirkland> okay, I'm going now
[20:11] <marcoceppi> update-alternatives worked at one point
[20:13] <kirkland> marcoceppi: okay -- now, I'm ready to deploy my charm from my local directory
[20:14] <kirkland> marcoceppi: and i'm on: kirkland@x230:~/src/charms$ juju version
[20:14] <kirkland> 1.11.2-raring-amd64
[20:14] <marcoceppi> kirkland: can you just give me the output of pwd from inside your charm's source directory?
[20:14] <kirkland> marcoceppi: /home/kirkland/src/charms/john
[20:15] <marcoceppi> kirkland: so, if your charm is named "john", you'll need to add a series directory between charms and john, /home/kirkland/src/charms/precise/john
[20:15] <marcoceppi> as this'll be a local repository now
[20:16] <kirkland> okay
[20:16] <marcoceppi> aftera a successful bootstrap, you'll need to run the following:
[20:16] <kirkland> marcoceppi: k
[20:17] <marcoceppi> `juju deploy --repository /home/kirkland/src/charms local:john` which will default to the LTS series (precise) and look for the john charm in the "local" repository defined as /home/kirkland/src/charms
[20:18] <marcoceppi> jcastro: there's a patch needed to get bootstrap working
[20:18]  * marcoceppi ducks
[20:24] <kirkland> marcoceppi: okay, good, deployed
[20:24] <kirkland> marcoceppi: and I deployed nfs
[20:24] <kirkland> marcoceppi: now I need to add the relation?
[20:24] <marcoceppi> kirkland: now you should just need to `juju add-relation nfs john`
[20:25] <marcoceppi> You can inspect the deployments by shelling directly in to them with juju ssh john/0 or juju ssh nfs/0 (<service>/<unit num>)
[20:25] <marcoceppi> there's a log in /var/log/juju/unit*.log that shows you the hook output if you need to debug things
[20:27] <kirkland> marcoceppi: okay, nice, I have john and nfs up, related, and john has mounted the nfs volume
[20:27] <marcoceppi> kirkland: nice!
[20:28] <marcoceppi> kirkland: what you can do now is `juju add-unit john` you'll get another john unit (john/1) and when it spins up it'll be mounted to the same NFS point
[20:28] <kirkland> marcoceppi: right
[20:28] <marcoceppi> each subsequent unit will get the same relation stuff, etc
[20:28] <kirkland> marcoceppi: that's the idea ;-)
[20:28] <marcoceppi> kirkland: sweet, let us know if you have any other questions!
[20:41] <marcoceppi> jcastro: http://i.imgur.com/RfhvxBv.png
[20:56] <thumper> jcastro: morning
[20:56] <thumper> jcastro: there are a few rough edges with the local provider
[20:56] <jcastro> thumper: wanna hop on G+ and sync up?
[20:57] <thumper> jcastro: in particular addressing, but also the containers don't restart with the machine yet
[20:57] <thumper> sure
[20:57] <thumper> jcastro: you start one?
[20:57] <jcastro> yeah one sec
[20:57] <jcastro> https://plus.google.com/hangouts/_/b99ee2ffdc84a9d7b0fb2eb8e45c88e1c65c771c?hl=en
[20:58] <jcastro> marcoceppi: ^^^