[00:17] <perrito666> nites people
[00:18] <perrito666> what does exactly expose do when used with lxc?
[00:18] <perrito666> I mean, is there anything I should implement in my charm to support it?
[00:30] <davecheney> perrito666: it's sort of theother way around
[00:30] <davecheney> your charm should call open-port when it wants to expose a port to consumers of the charm
[00:32] <perrito666> davecheney: I see, Ill rtfm myself with that info :D tx
[00:33] <davecheney> perrito666: the goal, when everything works right, is as the charm author you shouldn't have to worry about the differences between the various providers
[00:34] <perrito666> davecheney: I see, I was trying to learn juju trough creating a charm, I found a grey area on that particular feature (expose)
[00:35] <davecheney> perrito666: ok, so there are two parts
[00:35] <davecheney> one, in the charm, you say open-port or close-port to indicate to juju that the charm will talk on said ports
[00:35] <davecheney> on the client side, you call juju expose $SERVICE
[00:36] <davecheney> which takes the list of ports indicated by open-port and does firewall magic to make those visible on the public ip
[00:36] <perrito666> davecheney: tx, that is very informative
[06:19] <prathamesh> hi all
[09:35] <onrea> How to install juju manually by this files:
[09:35] <onrea> ubuntu-12.04-server-cloudimg-amd64
[09:35] <onrea> and
[09:35] <onrea> ubuntu-12.04-server-cloudimg-amd64-root
[10:02] <onrea> Oops! How to install juju via cloudimg's?
[12:57] <bloodearnest> so, I use a charm that bundles charm-tools (for reasons currently unknown)
[12:58] <marcoceppi> bloodearnest: wat?
[12:59] <bloodearnest> marcoceppi: I've no idea why
[13:00] <marcoceppi> bloodearnest: is this a charm that you downloaded or one you're writing?
[13:01] <bloodearnest> marcoceppi: it's one some one on my team wrote who has now left, it's an nginx-rate-limiter charm
[13:01] <marcoceppi> bloodearnest: yeahh, there's really no need to embed charm-tools UNLESS they were trying to use the old charm-helpers
[13:01] <bloodearnest> marcoceppi: last commit was 06/2013
[13:01] <marcoceppi> in which case, they should use the PPA that only builds charm-helper-sh/charm-helper-python
[13:02] <marcoceppi> bloodearnest: well, that's not much help
[13:02] <bloodearnest> right, so I need to re-write the charm, I'm good with that, I just don't have time to do it today, as I have some urgent deployments
[13:04] <bloodearnest> the only reason this is blocking me is I can't deploy the charm as is any more with 1.17, I get an error:
[13:04] <bloodearnest> charm-tools has a number of
[13:04] <bloodearnest> ERROR error uploading charm: cannot read extracted archive: charm "$package" using a duplicated relation name: "relation-name"
[13:04] <bloodearnest> gah
[13:04] <bloodearnest> which I believe is due to some template metadata.yaml files in charm tools
[13:05] <marcoceppi> bloodearnest: you can fix that by embedded a more recent version of charm-tools
[13:05] <bloodearnest> the new thing is that somehow juju is finding the those metadata.yaml files and complainging
[13:05] <marcoceppi> but whatttt
[13:05] <bloodearnest> marcoceppi: indeed
[13:05] <marcoceppi> yeah, juju really shouldn't dive /that/ deep
[13:06] <bloodearnest> marcoceppi: ack, will bump charm-tools an move forward, and after deployment will back track and file a bug
[13:06] <marcoceppi> bloodearnest: ta
[13:11] <bloodearnest> marcoceppi: updating to r318 of lp:charm-tools gives a different error, but same issue of parsing a template metadata.yaml:
[13:11] <bloodearnest> ERROR error uploading charm: charm URL has invalid charm name: "local:precise/$package-1"
[13:11] <bloodearnest>  at least, I assume that's the issue, not 100% sure
[13:13] <marcoceppi> bloodearnest: I'm like 98% sure you only need the helpers directory in charm-tools
[13:13] <marcoceppi> but I don't know where to find the charm to verify that
[13:14] <bloodearnest> marcoceppi: it's lp:~ubuntuone-pqm-team/canonical-is-charms/nginx-rate-limiter
[13:16] <bloodearnest> marcoceppi: I will probably rebase on upstream nginx and add the rate limiting as an MP on that
[13:16] <bloodearnest> just wondered if there was a quickfix to get past it
[13:16] <marcoceppi> bloodearnest: very interesting. I don't see charm-tools being used anywhere in the hooks
[13:17] <bloodearnest> marcoceppi: yeah, it's possible I could just remove it?
[13:18] <bloodearnest> marcoceppi: still, it would be good to figure out why it's failing on 1.17.4/trusty and it's been fine on 1.16.x/precise
[13:18] <marcoceppi> bloodearnest: I would just remove it and deploy for now
[13:18] <marcoceppi> oh wait
[13:18] <marcoceppi> bloodearnest: _pythonpath.py shows that it's just using lib/charm-tools/helpers/python
[13:19] <marcoceppi> bloodearnest: delete everything but the helpers dir in charm-tools
[13:19] <marcoceppi> and you should be good to go for the deployment
[13:19] <bloodearnest> marcoceppi: ack will try
[13:24] <zchander> Hi all, does anyone have any pointers (or working config samples) for a reverse proxy setup, so I can expose my charms from my cluster to the 'real' world? My cluster is a private/seperate network from our schoolnetwork (it is being NATted through the MAAS controller)
[13:25] <lazyPower> o/ zchander
[13:25] <lazyPower> marcoceppi: is this something that can be achieved with iptables on the controller node as a gateway?
[13:27] <zchander> Hi lazyPower, for what I have tried for now, is a apache2 reverse proxy setup, but that doesn't seem to proxy
[13:27] <zchander> lazyPower: Did the presentation run well?
[13:28] <lazyPower> zchander: it did. My internet was flakey and dropped while deploying a hadoop cluster
[13:28] <lazyPower> so i wasn't able to give the full technical rundown with magic without a minor bit of failure
[13:28] <lazyPower> but my showmanship was pretty high, so it went over pretty well
[13:29] <zchander> brb: going to get some caffein
[13:38] <zchander> back again...
[13:40] <lazyPower> re
[13:40] <lazyPower> zchander: when you say the apache reverse proxy doesnt work, how so? is the region controller not reaching the internal instances? or...
[13:42] <zchander> It seems so.... I have just reinstalled my MAAS environment from scratch this morning.
[13:54] <zchander> lazyPower: Is seems the 'reverse proxy' redirects all traffic to a https site, which cannot be found, as no ssl enabled site exists (yet)
[13:54] <zchander> And the log mentions POST requests to my MAAS api
[13:59] <zchander> Currently I get a 502 - Bad Gateway from nginx
[14:00] <zchander> And additionally I cannot connect to my MAAS web interface anymore from my school network
[14:02] <jcastro> hazmat, got a minute to talk deployer?
[14:05] <zchander> Please disregard my last issue: I forgot (with my fat fingers) to include the ServerName directive in my VirtualHost
[14:08] <lazyPower> zchander: np :) happens to the best of us
[14:13] <jcastro> ERROR state/api: websocket.Dial wss://10.0.3.1:17070/: dial tcp 10.0.3.1:17070: connection refused
[14:13] <jcastro> I am getting this when trying to teardown the local provider
[14:14] <lazyPower> jcastro: i typically get that when my local provider has gone awry, such as an interrupted bootstrap
[14:14] <jcastro> yeah
[14:14] <jcastro> so the "normal" procedures should work?
[14:14] <lazyPower> just removing .jenv if there are no lxc containers usually resolves that.
[14:14] <jcastro> to clean up
[14:14] <jcastro> yeah
[14:14] <lazyPower> if there are leftover lxc containers, follow the AU post
[14:16] <lazyPower> jcastro: i'm working through porting my writeup on osx/vagrant charm authoring to the docs atm. What subsectionw ould you put this under?
[14:16] <lazyPower> authors-osx-walkthrough?
[14:16] <cargill> in amulet, can Deployment.setup() be called multiple times in the same test?
[14:17] <jcastro> I would do "How To" and then "Vagrant work flow"
[14:17] <lazyPower> cargill: thats part of post deployment commands. I filed a bug about the behavior you will see if you try it :)
[14:17] <marcoceppi> cargill: it can, but you shouldn't add any relations between setup calls, it's not supported
[14:17] <lazyPower> jcastro: ack. ty
[14:18] <marcoceppi> cargill: not supported yet*
[14:18] <marcoceppi> cargill: what's your ultimate goal?
[14:20] <cargill> I'm getting 'service "postgresql-sentry" not found' when I deploy my charm and potgresql, and not when I deploy just potgresql, so I'm trying to find out whether it's a timeout from my charm setting up itself (it does take a long time) or something else
[14:21] <marcoceppi> cargill: what's your test file look like?
[14:21] <cargill> and setting up one, then the other does indeed trigger an error suggesting that setup cannot be run multiple times
[14:23] <cargill> marcoceppi: http://pastebin.ubuntu.com/7067852/
[14:23] <cargill> this is without any "debugging" additions
[14:24] <marcoceppi> cargill: interesting, and so what's the error you're getting? Also, do you have the latest amulet?
[14:24] <marcoceppi> as in, is there a Python traceback?
[14:25] <hazmat> jcastro, shoot
[14:25] <jcastro> can I make bundles with colocated services in LXC containers?
[14:25] <zchander> lazyPower: can I send you my virtual host config (for a wordpress charm, as per tutorial)
[14:25] <hazmat> jcastro, yes
[14:25] <jcastro> let's say I want rails and postgres, but I want all the monitoring stuff in one instance on LXC containers
[14:25] <lazyPower> zchander: sure, pastebin it
[14:25] <hazmat> jcastro, http://pythonhosted.org/juju-deployer/config.html#placement
[14:26] <hazmat> jcastro, placement is somewhat limited at the moment, its a form of deploy x with service y.. and supports containers
[14:27] <jcastro> ok so lxc:wordpress is "whichever machine wordpress ended up on" then?
[14:27] <hazmat> jcastro, i've had some discussions last week about allowing machine specification (ie a machines block in addition to a services block) and then allowing for machines to be placed there.
[14:27] <hazmat> er.. i mean workloads to be placed there
[14:27] <zchander> lazyPower: http://paste.ubuntu.com/7067872/
[14:27] <hazmat> jcastro, yes
[14:28] <cargill> marcoceppi: yes, the vagrant scripts from lazyPower pick up the latest amulet
[14:28] <hazmat> jcastro, i avoided machine spec (minus 0) in the initial pass because its quite fragile unless you can abstract machines a bit from their env specific identity.
[14:28] <jcastro> hazmat, perfect, that's exactly what I needed, thanks
[14:28] <cargill> will post the output shortly
[14:28] <jcastro> well for this bundle I don't care about machines
[14:28] <zchander> lazyPower: I might be back tonight again, going into a meeting in a few minutes
[14:28] <jcastro> I'm making a "rails" one for development and I don't want a ton of instances
[14:28] <lazyPower> cargill: offtopic from what you're talkign about, but I did a writeup using the precise basebox. it'll reduce that overall footprint of the box to 200mb in your vagrant cache.
[14:29] <lazyPower> http://blog.dasroot.net/writing-juju-charms-on-osx/
[14:29] <hazmat> jcastro, cool, for most of them you shouldn't.. the call for machines in deployment is more about real world ops scenarios.. where you want to prep a machine a bit before hand
[14:29] <hazmat> jcastro, ie.. service co-location is ideal for bundles
[14:29] <lazyPower> use that vagrantfile with the precisebasebox and you should be g2g. I've tested it locally with no issues.
[14:29] <hazmat> that re shared/reused.
[14:30] <lazyPower> zchander: i dont see anything apparently wrong with this
[14:30] <lazyPower> zchander: ping me when you get back and we'll do some troubleshooting
[14:30] <cargill> lazyPower: oh, great, right now I'm just running provision everytime, that won't be faster though, will it? but speeding up the bootstrap is definitely a good thing
[14:30] <lazyPower> cargill: it may slow it down since its cloud-init bootstrapping a juju gui
[14:31] <lazyPower> the box you're using right now was specifically tailored for amulet testing
[14:31] <jcastro> hazmat, yeah I didn't want to be like "here's your rails dev bundle, have fun paying for 9 instances an hour!"
[14:32] <hazmat> jcastro, approximately $1 on do ;-) .. if you have a chance i'd love  your feedback on that plugin.
[14:35] <hazmat> jcastro, not sure you can do better than hulk-smash in public clouds atm, vpc/private networking against cloud apis for containers is still wip.
[14:40] <cargill> marcoceppi: this is the log with the test written as above: http://pastebin.ubuntu.com/7067958/
[14:49] <marcoceppi> cargill: interesting
[15:00] <cargill> marcoceppi: this another of the errors I'm getting http://pastebin.ubuntu.com/7068075/
[15:00] <marcoceppi> cargill: what's weird, is the setup is being killed beacuse of timeout, but it keeps going aftwards
[15:00] <marcoceppi> which is probably why you're seeing that error
[15:05] <cargill> that's because the timeout passed to setup() is 900 and there is an internal one of 600 seconds?
[15:09] <jcastro> http://askubuntu.com/questions/432187/how-can-i-deploy-my-local-juju-charm-with-amulet-framework
[15:09] <jcastro> just in case anyone missed this
[15:14] <marcoceppi> cargill: it should respect your timeout, however, if you're doing `charm test` command there's timeout per test
[15:14] <marcoceppi> cargill: actually, that's probably where it's coming from
[15:14] <marcoceppi> cargill: you need to modify whatever is running `charm test` and add `charm test --timeout=10m` or something like that
[15:14] <marcoceppi> lazyPower: ^^
[15:15] <lazyPower> marcoceppi: can you open a bug on the project? I'll get that update pushed in a minute
[15:15] <lazyPower> wrapping up my doc edits
[15:15] <marcoceppi> lazyPower: which project/
[15:15] <lazyPower> https://github.com/chuckbutler/juju-vagrant
[15:16] <cargill> marcoceppi: will try with 30minute timeout, let's see where it gets me next
[15:16] <marcoceppi> cargill: ack
[15:28] <lazyPower> https://github.com/juju/docs/pull/27 -- for anyone thats interested in reviewing the proposed merge for Vagrant based workflow on OSX
[15:28] <lazyPower> also sent an announcement to the list
[15:49] <jcastro> hey lazyPower
[15:49] <jcastro> wrt. your +1 on the hadoop bundle
[15:49] <jcastro> I made a section on how to put them in the store
[15:49] <jcastro> https://juju.ubuntu.com/docs/reference-reviewers.html
[15:50] <jcastro> oh nm, you're not in ~charmers
[16:08] <marcoceppi> lazyPower: see gh for feedback on pull
[16:09] <lazyPower> marcoceppi: fixing, addendum to that is we need to do that for the rails howto then, thats what i modeled it after.
[16:09] <marcoceppi> lazyPower: that's fine, we can fix that later
[16:09] <lazyPower> ack
[16:17] <jcastro> https://github.com/juju/docs/pull/28
[16:17] <jcastro> if someone could ack that it's a simple fix.
[16:20] <lazyPower> marcoceppi: wiped $'s
[16:21] <marcoceppi> lazyPower: re-reviewing
[16:30] <marcoceppi> lazyPower: updated
[16:34] <lazyPower> re-updated
[16:34] <lazyPower> marcoceppi: ^
[16:38] <marcoceppi> lazyPower: okay, finally reviewed everything, only two little things
[16:38] <marcoceppi> I won't be so lazy reviewing next time
[16:42] <lazyPower> marcoceppi: ack. Fixed and pushed.
[16:43] <jcastro> marcoceppi, does bundle proof check that juju-gui is not included in a bundle?
[16:43] <marcoceppi> jcastro: no, but it could/should
[16:43] <jcastro> filing
[16:43] <marcoceppi> open a bug and I'll add it to the next release
[16:44] <marcoceppi> lazyPower: hahah, I found one more thing
[16:44] <marcoceppi> you were a little aggressive with the $ removal
[16:44] <lazyPower> KILL IT WITH FIRE!
[16:45] <lazyPower> marcoceppi: line 240?
[16:45] <marcoceppi> lazyPower: nooooope
[16:45] <marcoceppi> ;)
[16:45] <lazyPower> find and replace came back to haunt me :((
[16:46] <sarnold> not sed -i? :)
[16:46] <lazyPower> sarnold: yuck it up fuzzball :P
[16:47] <sarnold> nyuk nyuk nyuk
[16:47] <lazyPower> <3
[16:47] <sarnold> <3
[16:47] <marcoceppi> lazyPower: commented
[16:48] <marcoceppi> lazyPower: or just ommit that all togehter
[16:48] <lazyPower> but, that cuts out my interesting prompt/path
[16:48] <lazyPower> ack - removing.
[16:54]  * lazyPower goes back to the review queue
[17:07] <jcastro> hey everyone, "State of the Juju Ecosystem" had to be moved to thursday as they added a plenary slot
[17:08] <jcastro> so Thursday will be charm school, state of the eco, and then Amulet tests all in one day
[17:09] <lazyPower> womp
[17:09] <lazyPower> ty for the update jcastro
[17:10] <lazyPower> did we move that around on the eco calendar yet?
[17:11] <jcastro> I didn't know we were putting those  on the calendar
[17:11] <jcastro> in that case, no
[17:11] <lazyPower> maybe we arent. I just looked and didn't see anything there
[17:11] <lazyPower> i figured with it being UDS related, it would go on the calendar, my b.
[17:11] <jcastro> it's UDS, we're supposed to be paying attention heh
[17:12] <jcastro> but if you register yourself at UDS it will generate a calendar of sessions for you, etc.
[17:12] <jcastro> I'll be sending reminders here throughout the week anyway
[17:21] <marcoceppi> lazyPower: noooo
[17:21] <marcoceppi> lazyPower: you only needed to fix that one line, the rest was fine :(
[17:22] <lazyPower> marcoceppi: no idea what you're talking about
[17:22] <marcoceppi> gh
[17:22] <lazyPower> damnit
[17:22] <lazyPower> i'm quit
[17:22] <lazyPower> s/i'm/i
[17:24] <marcoceppi> You even asked, and I was like "nooo, those are fine"
[17:25] <lazyPower> marcoceppi: updated
[17:26] <marcoceppi> lazyPower: now, can you squash 'em all :) <3
[17:31] <jcastro> hey lazyPower
[17:31] <jcastro> now that you've documented the vagrant workflow
[17:31] <jcastro> http://www.vagrantup.com/blog/vagrant-1-5-and-vagrant-cloud.html#features
[17:31] <jcastro> hah.
[17:31] <lazyPower> jcastro: make a card
[17:32] <lazyPower> and stand in line behind marco
[17:33] <jcastro> I think it'll be a bit before we get 1.5
[17:33] <jcastro> utlemming, https://vagrantcloud.com/
[17:33] <jcastro> utlemming, this is just launched, but we should perhaps look at indexing the official boxes there?
[17:34] <lazyPower> jcastro: https://vagrantcloud.com/search?utf8=%E2%9C%93&q=juju
[17:34] <lazyPower> boo
[17:34] <jcastro> indeed!
[17:34] <lazyPower> look at all these chef boxes
[17:35] <lazyPower> boy sure would be nice if JUJU was a featured box
[17:35]  * lazyPower tongues cheek
[17:55] <zchander> ping lazyPower
[17:55] <lazyPower> zchander: pong
[17:56] <zchander> I am at home right now, but with VPN to school
[17:57] <lazyPower> zchander: ok. my thoughts are check connectivity from the gateway node to the internal net. validate its communicating properly
[17:57] <lazyPower> start at the lowest common denominator and unwind the onion of complexity layer by layer
[17:57] <zchander> I can ssh into the node without any problem using the hostname from the controller
[17:58] <lazyPower> ok, is port80 of the node accessible from the controller?
[17:58] <lazyPower> you can use links or similar text based browser to validate
[17:58] <lazyPower> or curl for that matter
[17:59] <zchander> I am installing lynx right now
[18:01] <zchander> Done: I am getting a bad gateway from nginx
[18:02] <lazyPower> that would be on the wordpress charm, and you should have gotten that via the apache reverse proxy. but ok we have validated you have port 80 connectivity
[18:02] <lazyPower> tail your apache logs for the vhost, and attempt to reach the wordpress node.
[18:07] <zchander> snippet from wordpress-access_log: http://paste.ubuntu.com/7069014/
[18:08] <zchander> btw, maas-ctrl-001.nimeto.edu/MAAS also gives a bad gateway from nginx
[18:08] <lazyPower> so the reverse proxy is working?
[18:08] <zchander> (this is the fqdn for my MAAS controller)
[18:09] <zchander> Seems so, but too good? ;)
[18:09] <lazyPower> so, my thoughts are, poke at wordpress and figure out a) why its a bad gateway (probably PHP-FPM failed to start) b) what do you need to add to get the proper hostname on the wordpress unit to respond to the request.
[18:12] <zchander> This a line from the access log from nginx on the wordpress node: 10.0.41.5 - - [10/Mar/2014:18:06:05 +0000] "GET /favicon.ico HTTP/1.1" 404 140 "http://node001.nimeto.edu/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.74.9 (KHTML, like Gecko) Version/7.0.2 Safari/537.74.9"
[18:12] <lazyPower> i saw that. its not finding a site for that hostname.
[18:12] <lazyPower> the 404 in the log detail points to that.
[18:13] <zchander> Seems I have to get up to speed with nginx....
[18:13] <lazyPower> zchander: http://wiki.nginx.org/ServerBlockExample
[18:13] <lazyPower> zchander: there's also a configuration option for the wordpress charm to use apache instead of nginx
[18:14] <lazyPower> zchander: juju set wordpress engine=apache2
[18:14] <lazyPower> https://jujucharms.com/precise/wordpress/#readme
[18:14] <zchander> Can I foo that with a running charm?
[18:14] <lazyPower> yep. so long as the charm is not in an error state, it will reconfigure itself on the fly
[18:16] <zchander> just did it.... Trying again
[18:19] <zchander> getting [agent-state-info: 'hook failed: "config-changed"'], this will resolve itself in time? Or should I 'resolve' the issue?
[18:20] <zchander> brb: getting kid to bed....
[18:22] <mgz> zchander: hook failures need manual resolution
[18:22] <lazyPower> zchander: you can either pass the -r to the resolved command, or use debug-hooks to manually investigate and resolve the issue.
[18:22] <lazyPower> zchander: units in an error state do not magically resolve themselves, and always require manual intervention.
[18:33] <zchander> getting a HOOK W: Failed to fetch http://ppa.launchpad.net/charmers/charm-helpers/ubuntu/dists/precise/main/binary-amd64/Packages  403  Forbidden when switching to apache (??)
[18:35] <zchander> I am going to destroy the service and retry to redeploy
[18:43] <zchander> bbl, got visite... parents...
[19:03] <bac> hi sinzui
[19:03] <sinzui> hi bac
[19:07] <geekmush> anyone playing with juju on Digital Ocean?
[19:28] <lazyPower> geekmush: there are a few using hazmat's plugin for alpha-level testing
[19:28] <hazmat> geekmush, just saw your issue
[19:28] <hazmat> geekmush, so you need the dop library from git atm..
[19:28] <hazmat> geekmush, i'll switch out to just doing a mini digital ocean client lib for the needed bits within the plugin.
[19:29] <hazmat> but probably not today
[19:29] <geekmush> hazmat:  ok, cool … I'll stand by and also try out the git'd version of dop as well
[19:30] <hazmat> geekmush, cool, yeah.. things work if you using the git version of dop.. i put a bug in there for them to make a release, since its been over a release since their last
[19:30] <hazmat> er.. over a year
[20:03] <jcastro> hey fellas, so I am working on a django bundle
[20:03] <jcastro> but the charm hasn't been touched in like a year
[20:03] <jcastro> anyone mind doing it next on the audit?
[20:31] <hazmat> geekmush, any luck/progress?
[20:32] <geekmush> just started … got pulled into last minute conf call …
[22:50] <bodie_> does anyone know the status of juju on debian?
[22:51] <bodie_> i'm seeing some articles linking to a juju package in experimental, but it's gone now
[23:01] <sarnold> bodie_: I don't think there has been any effort to push the juju packages to debian yet; those packages in experimental were probably the old python version 0.5 or so iirc, which, while neat, weren't anything that anyone wanted to tell users to use :)
[23:05] <marcoceppi> bodie_: juju the client should just work
[23:05] <marcoceppi> bodie_: though you may need to compile it from source,
[23:06] <bodie_> I see :)
[23:06] <bodie_> thanks