[00:02] <marcoceppi> hazmat: want someone to package that up?
[00:17] <hazmat> marcoceppi, sure
[06:59] <JoshStrobl> hey marcoceppi, you around?
[07:01] <JoshStrobl> what are your thoughts on me changing the stuff like -changed to <name>-relation-changed in authors-charm-hooks.md, such as in the following section: https://juju.ubuntu.com/docs/authors-charm-hooks.html#<name>-relation-departed. I think doing that and putting it between tick marks would make those hooks stand out more when they are being referenced.
[08:32] <lazyPower> JoshStrobl: sounds good to me
[08:56] <JoshStrobl> lazyPower, https://github.com/juju/docs/pull/176
[08:58] <lazyPower> haha, <3 evilnickveitch https://github.com/juju/docs/pull/172
[09:01] <JoshStrobl> ah didn't notice he was going to land that code inconsistency fix :D
[09:02] <JoshStrobl> actually
[09:02] <JoshStrobl> nvm that was you .P
[09:03] <JoshStrobl> I just did a resync of my fork today and was working with what I had, you gotta be more on the ball with getting these pull requests merged man! :P
[09:04] <JoshStrobl> lazyPower, there will be some minor conflicts for your merge, should be easily resolvable though!
[09:05] <lazyPower> JoshStrobl: yep, no big deal. I can pull and revise the PR
[09:05] <lazyPower> this is one of the few quiet times during the day that I feel like i can be really productive, if i keep my heado ut of IRC long enough to do so :P
[09:06] <lazyPower> yesterday i was all aflutter about my blog post landing on HackerNews to be really productive. that tanked my motivation to do anything other than watch stats and merge bundles.
[09:06] <lazyPower> so today i've gotta make up for that lost productivity
[09:06] <JoshStrobl> :D
[09:07] <lazyPower> oye JoshStrobl, did you cat the latest Nu: podcast?
[09:07] <JoshStrobl> lazyPower, yea I already listened to it :P
[09:07] <lazyPower> niiiice
[09:07] <lazyPower> man, you *are* on the ball
[09:07] <JoshStrobl> I was listening to it while working on the docs actually
[09:08] <lazyPower> This friday ~ 5pm EDT, i'll have another live show
[09:08] <lazyPower> looking to do a 3 hour megamix repeat
[09:08] <JoshStrobl> sweet
[09:08] <lazyPower> so if you're around, ping me and i'll hit ya with some details
[09:08] <JoshStrobl> I might jump in SL (it has seriously been a while) and go to the location when that happens
[09:08] <JoshStrobl> 3hr megamix? awesome man.
[09:09] <lazyPower> oh  i actually bailed on that medium
[09:09] <lazyPower> i took the fans from there off the grid and changed format to the podcast for my regular shows
[09:09] <lazyPower> the live mixes are an added bonus for glory
[09:09] <lazyPower> and because nothing beats recovering from a botched transition on stream :P
[09:10] <JoshStrobl> so where will the live show be if not that location? or does mixcloud support live streams?
[09:10]  * JoshStrobl doesn't know.
[09:10] <lazyPower> i run an icecast/shoutcast server
[09:10] <JoshStrobl> ah cool
[09:11] <lazyPower> getting ready to cut this gem after i add relay support and tests - https://code.launchpad.net/~lazypower/charms/trusty/shoutcast/trunk
[09:11] <JoshStrobl> you deploy that with Juju?
[09:11] <JoshStrobl> thought so :D
[09:11] <lazyPower> thats the point of doing this on friday. Incentive to finish it up so i can scale out if we tank the shoutcast server
[09:13] <JoshStrobl> sweet
[09:14] <lazyPower> i plan on collecting metrics and blogging about this as well - i'm hoping to generate enough interest to talk about a real scale out scenario for a change vs theorhetical
[09:21] <JoshStrobl> maybe we could showcase the metrics and scaling so it is easier for people to really understand the benefit of scaling the service as well as making sure your charm's service is scalable.
[09:21] <JoshStrobl> besides, everyone likes "real world" examples v.s. theoretical
[09:25] <lazyPower> indeed!
[09:25] <lazyPower> we'll need to flood the server tho, i'm talking > 50 listeners
[09:25] <lazyPower> a single host running at 1gb of ram can easily transcode/stream to ~ 40/50 hosts before it starts dropping connections
[09:25] <JoshStrobl> lazyPower, any way we can simulate that?
[09:25] <lazyPower> actually. probably
[09:26] <lazyPower> mpg123 the source multiple times from another VPS
[10:40] <gnuoy> I'm using juju from tip (1.21-alpha2) and when I try and do juju sync-tools with a new maas setup it complains that the environment is not bootstrapped. this leaves me in a bit of a chicken/egg situation as I can't bootstrap due to the lack of tools
[10:49] <jamespage> tvansteenburgh, gnuoy: https://code.launchpad.net/~james-page/charm-helpers/disable-hookenv-config-save/+merge/235607
[10:54] <marcoceppi> JoshStrobl: it already has <name> there but it's being rendered as HTML
[10:54] <marcoceppi> I suggest to change it to [name] instead
[10:56] <JoshStrobl> marcoceppi, I did a pull request where that file in particular just has references to particular relation hooks (like -changed) wrapped in "back ticks" so it is easily distinguishable.
[10:57] <JoshStrobl> marcoceppi, pull request @ https://github.com/juju/docs/pull/176 already merged thanks to lazyPower
[10:57] <lazyPower> grr
[10:57] <lazyPower> i didn't think about that
[10:58] <marcoceppi> JoshStrobl: that's cool, but currently the headers are <name>- and those are interpurted as HTML wasn't something you did but we should avoid <var> as keywords in general in the docs now that I see this
[10:58] <lazyPower> marcoceppi: making a fix branch and PR shortly
[10:59] <marcoceppi> lazyPower: cool
[10:59] <JoshStrobl> marcoceppi, well I didn't change it to <name>-relation-joined, just `-joined` so it shouldn't be an issue.
[11:00] <JoshStrobl> I rendered and tested in htmldocs before doing a request and it was rendering properly
[11:00] <JoshStrobl> https://github.com/juju/docs/pull/176/files#diff-5433c68091963235b67c8f260cd46394
[11:01] <lazyPower> https://github.com/juju/docs/pull/177
[11:01] <JoshStrobl> Ah I see what you're referring to.
[11:04] <JoshStrobl> lazyPower, there are references in some files to particular relation hooks, like authors-hook-environment. with the change from < to [, it'll break those direct links. once your PR goes through, want me to change those?
[11:04] <lazyPower> JoshStrobl: +1
[11:05] <l6unchpad> I'm using charmhelpers in a charm and it appears not to be installed on a unit:
[11:05] <l6unchpad> from charmhelpers.contrib import ansible
[11:05] <l6unchpad> ImportError: No module named contrib
[11:06] <JoshStrobl> cool, I'll do that after your PR (that way I don't need to deal with git stashing changes and such)
[11:06] <l6unchpad> any suggestions to this possibly noob question?
[11:07] <l6unchpad> actually scratch that.
[11:09] <l6unchpad> > this: ./scripts/charm_helpers_sync.py -c charm-helpers.yaml
[11:10] <marcoceppi> l6unchpad: yeah, you've got to embed them or pip install them
[11:11] <lazyPower> marcoceppi: https://github.com/juju/docs/pull/177
[11:14] <lazyPower> <3 ty
[11:14] <lazyPower> JoshStrobl: ready for PR
[11:15] <JoshStrobl> lazyPower, cool, I'll update my fork and do the change
[11:20] <JoshStrobl> https://github.com/juju/docs/pull/178
[11:29] <JoshStrobl> lazyPower: bug report - "juju deploy happyness" should be "juju deploy happiness" (ref: your blog)
[11:29] <lazyPower> >.>
[11:29] <lazyPower> <.<
[11:30] <lazyPower> pushed & closed
[11:30] <JoshStrobl> :P
[11:40] <lazyPower> thanks for pointing that out :)
[11:40] <JoshStrobl> lazyPower, no problem. that digitalocean plugin is awesome. that said, you should get DO support built into juju core.
[11:40] <lazyPower> there's a bug for that
[11:41] <JoshStrobl> :O
[11:44] <lazyPower> JoshStrobl: https://bugs.launchpad.net/juju-core/+bug/1372543
[11:44] <mup> Bug #1372543: add a digital ocean provider <digital-ocean> <feature> <juju-core:Triaged> <https://launchpad.net/bugs/1372543>
[11:45] <JoshStrobl> marked as affected
[11:45] <lazyPower> JoseeAntonioR: ping
[11:46] <JoshStrobl> I'll keep track of the bug, once it is merged I'll go ahead and write a doc up on DO provider
[11:46] <lazyPower> Already incoming today based on my blog post with the plugin as our BETA mention of DO
[11:46] <lazyPower> once the provider lands, we'll just strip the plugin install  and command routing and profit.
[11:47] <JoshStrobl> ah cool!
[11:51] <lazyPower> i'll be working on that + getting it merged post lunch
[12:20] <gnuoy> I'm trying to running sync-tools with the maas provider and am getting "environment is not bootstrapped". Given I can't bootstrap without running the key sync  I'm stuck. Any ideas? (I'm using 1.21-alpha1-trusty-amd64)
[12:20] <gnuoy> s/key sync/tool sync/
[12:21] <lazyPower> gnuoy: are you running juju bootstrap --sync-tools? (sorry to be daft, just trying to be thorough)
[12:21] <lazyPower> (replies may be latent, i'm making waffles)
[12:23] <gnuoy> lazyPower, I'm the one that's probably being daft. But to answer your question, no. I'm trying to sync tools first as a standalone command as I have some hand rolled tools to upload
[12:23] <gnuoy> http://paste.ubuntu.com/8410426/
[12:24] <tvansteenburgh> jamespage: merged, thank you!
[12:35] <lazyPower> try bootstrapping, then uploading the tools (unless there is an implicit reason for doing it in reverse order)
[12:35] <gnuoy> lazyPower, bootstrap fails because there are no tools
[12:36] <lazyPower> gnuoy: even when you pass --upload-tools?
[12:36] <gnuoy> hmm, let me give that a go.
[13:02] <gnuoy> natefinch, hi, I'm trying to upload windows juju tools in a maas environment but it's failing. Do you have any time for me to quiz you about it ?
[13:03] <natefinch> gnuoy: sure
[13:04] <gnuoy> natefinch, I'm using maas 1.7 and juju 1.21-alpha1. If I try and upload the locally built juju.exe then juju complains the env is not bootstrapped. But I can't bootstrap without the new tools
[13:05] <natefinch> gnuoy: you should be able to do juju bootstrap --upload-tools
[13:05] <gnuoy> natefinch, but I need to tell juju to pickup the tools from a local directory which is an option to sync-tools but nbot to upload-tools
[13:06] <gnuoy> natefinch, is this a change in behaviour? A lot of dicumentation talks about doing sync-tools before bootstrapping
[13:06] <natefinch> gnuoy: upload tools will automatically look for local tools... just make sure you have a jujud.exe next to your juju client application, and it'll pick those
[13:09] <natefinch> gnuoy: sync tools is really only for environments that don't have access to the internet.  You bootstrap with --upload-tools and then use sync-tools to grab the various tools from the internet and upload them into your environment
[13:10] <gnuoy> natefinch, fair enough. fwiw I've seen sync-tools first in a few places, like https://maas.ubuntu.com/docs/juju-quick-start.html
[13:11] <mgz> as a non-dev user, trying to not use --upload-tools seems correct
[13:12] <mgz> natefinch: is the simplestreams tooling not up to doing windows yet?
[13:12] <natefinch> mgz: yes, definitely
[13:12] <natefinch> mgz: I'm not sure
[13:12] <natefinch> mgz: doesn't look like it
[13:12] <mgz> so I guess it's --upload-tools or nowt for now then
[13:14] <gnuoy> natefinch, it is still complaining about not being able to find tools, http://paste.ubuntu.com/8410715/
[13:14] <natefinch> mgz: https://maas.ubuntu.com/docs/juju-quick-start.html#now-juju     Is it me or are these docs crazy?
[13:14] <gnuoy> I may have not stumbled across the correct name for the tools file yet
[13:15] <natefinch> mgz: it talks about doing sync tools before bootstrap, but sync-tools requires an environment
[13:17] <JoshStrobl> natefinch, I wasn't even aware that there was that documentation. Any reason for it given there is config-maas as juju.ubuntu.com/docs/ ?
[13:18] <JoshStrobl> *at juju.....
[13:19] <mattyw> lazyPower, ping?
[13:19] <lazyPower> mattyw: pong
[13:19] <mattyw> lazyPower, hey there, I might have some time later this week to take a look at the mongo charm auth stuff. I took a look at the weekend and wanted to get some unit tests going but was struggling to get what's there running
[13:20] <mattyw> lazyPower, would you be available to pair for an hour later this week or next?
[13:20] <lazyPower> Sure thing. I need to clean up the tests directory. There are a bunch of leftover old tests
[13:21] <lazyPower> I was going to strike whats in the tests directory save for the amulet based tests, and work on fixing/extending those. as they are failing in CI
[13:22] <lazyPower> and go back and get test coverage around the hooks as a secondary stretch goal
[13:25] <gnuoy> natefinch, sorry, I'm still not clear where the juju7d.exe needs to be and what it needs to be names to get --upload-tools to pick it up
[13:29] <natefinch> gnuoy: I think having it in the same directory where you are running juju is all that should be required
[13:30] <gnuoy> natefinch, what should it be called ? just jujud.exe ?
[13:30] <natefinch> gnuoy: correct
[13:30] <ayr-ton> When write charms, do you guys prefer to use shell script or puppet dsl with standalone puppet?
[13:31] <ayr-ton> I'm looking into this: http://www.slideshare.net/lynxmanuk/juju-puppet-puppetconf-2011
[13:32] <gnuoy> natefinch, doesn't seem to have done the trick http://paste.ubuntu.com/8410809/
[13:34] <natefinch> gnuoy: oh hmm... well, so you can't bootstrap onto windows... only ubuntu.  Windows only works for deploying new units
[13:35] <natefinch> gnuoy: so you need the ubuntu tools for bootstrap
[13:36] <gnuoy> natefinch, ahhh, the plot thickens. So once you've bootstrapped you do add-machine to get a windows machine and then do deploy --to ?
[13:37] <jcastro> is any charmer available for an on the spot review?
[13:37] <jcastro> I need to get this bundle fixed asap
[13:39] <natefinch> gnuoy: you can just do juju deploy <windows-charm> and it'll pick windows because the charm should be labelled as windows
[13:39] <gnuoy> natefinch, oh, cool. thanks
[13:44] <aisrael> jcastro: I'm around, if you can't find someone else
[13:45] <jamespage> gnuoy, i'm reworking the hacluster charm like we discussed - its quite exciting not watching it rip everything apart on the slightest change of data!
[13:45] <jamespage> gnuoy, lp:~james-page/charms/trusty/hacluster/mix-fixes
[13:45] <gnuoy> \o/
[14:10] <pdobrien> hey folks, having an issue
[14:11] <pdobrien> I got my private Openstack cloud bootstrapped yesterday by using an ubuntu image to do it (since the Mac code has a bug)
[14:11] <pdobrien> got it up and running and deployed the GUI, everything working fine
[14:11] <pdobrien> however, when I try to deploy something else (mysql for example), the instances aren't starting
[14:12] <pdobrien> the error in juju status is: agent-state-info: index file has no data for cloud {RegionOne https://server.com:8770/v2.0/}
[14:12] <pdobrien> I think I need to provide the metadata so that it knows which image to use, etc. because I had to do that to bootstrap, but I'm not sure how to do it for charms
[14:36] <james_w> pdobrien: you followed https://juju.ubuntu.com/docs/howto-privatecloud.html?
[14:48] <ayr-ton> About the roadmap, if I want to move a service to a different machine or enviroment, it will be possible?
[14:49] <pdobrien> james_w: I did not see that page, I followed a different guide.  I will check it out, thanks!
[14:51] <james_w> pdobrien: did you set up simplestreams for your cloud?
[14:52] <pdobrien> james_w: I don't think so... I'm looking at that now.
[14:53] <james_w> pdobrien: ok
[14:56] <pdobrien> james_w: I did do the section under "deploying private clouds" where I generated the metadata, etc.  I was able to bootstrap successfully.
[14:57] <james_w> pdobrien: where did you upload the metadata?
[15:02] <pdobrien> james_w: does "juju bootstrap --metadata-source . --upload-tools -v" upload the metadata?
[15:02] <pdobrien> james_w: I see lots of stuff in the object store
[15:02] <james_w> pdobrien: I don't know
[15:04] <james_w> pdobrien: that takes care of the tools
[15:04] <james_w> but it's the image metadata you are having a problem with
[15:05] <james_w> pdobrien: you will have control-bucket set in the juju env definition
[15:05] <james_w> if you list the contents of that in the object store
[15:05] <james_w> then you will hopefully find streams/v1/index.json
[15:07] <pdobrien> james_w: yes, that is there.
[15:09] <pdobrien> james_w: I see the problem... the charms I am using want a precise image, I configured a trusty image for bootstrap
[15:09] <james_w> pdobrien: do the contents have something like http://pastebin.ubuntu.com/8411413/ ?
[15:09] <pdobrien> james_w: so I just need to create metadata for a precise image, I think
[15:12] <james_w> pdobrien: ah, ok
[15:20] <arosales> marcoceppi: lazyPower, mbruzek: do you guys know if the revision file is being used in 1.18?
[15:20] <mbruzek> arosales: I do not believe it is used in that version either
[15:21] <lazyPower> i dont have a definitive answer. But I'm fairly certain that if one is not present, juju will create one on deploy for you.
[15:21] <lazyPower> so it shoudl be safe to disregard it
[15:22] <JoshStrobl> I recall mbruzek telling me just to remove it from my charm (he sent it in a review email a while back) since it wasn't used. that correct mbruzek?
[15:22] <arosales> JoshStrobl: correctly pointed out that it is still being referenced in https://juju.ubuntu.com/docs/authors-charm-components.html
[15:22] <arosales> if 1.18 isn't using it suggest we just removed that linle
[15:22] <arosales> *line
[15:23] <mbruzek> JoshStrobl: I did tell you to remove it.  My understanding is we have not used revision file in QUITE some time.
[15:23] <JoshStrobl> Yea, since it currently just says "revision is now deprecated", I just figured we should just have it not in the doc to begin with.
[15:23] <arosales> JoshStrobl: sounds like it is a +1 for removal, nice find
[15:24] <JoshStrobl> I'll edit it and do a PR then
[15:25] <pdobrien> james_w: (or anyone) I have uploaded updated image metadata with info about where to find the precise image.  Is there a way to restart the deployment process for the charms I have already deployed, or should I remove them and start over?
[15:25] <JoshStrobl> https://github.com/juju/docs/pull/179
[15:27] <JoshStrobl> Hey mbruzek good work on the unmaintained charm workflow doc!
[15:27] <mbruzek> thank you
[15:56] <themonk> lazyPower, hi
[15:56] <lazyPower> greetings themonk
[15:56] <themonk> how are you
[15:56] <themonk> how are you?
[15:56] <lazyPower> I'm well, and yourself?
[15:57] <themonk> i am fine :)
[15:57] <lazyPower> Brilliant :)
[15:58] <themonk> i wrote 2 charm
[15:58] <themonk> i want it to be reviewed and listed in charmstore
[15:59] <themonk> but i found it very confusing
[15:59] <lazyPower> Are you looking for *recommended* status? or are you looking to just get moving quickly by having it int he store?
[15:59] <themonk> in official doc
[15:59] <pdobrien> james_w: (or anyone) I have uploaded the updated image metadata to the object store, but juju metadata validate-images still fails.
[15:59] <JoshStrobl> themonk, are you having issues publishing your charm to your Launchpad account?
[16:00] <JoshStrobl> themonk, or submitting it to be reviewed?
[16:00] <themonk> lazyPower, just want to quickly list it in the store
[16:00] <themonk> for now
[16:01] <JoshStrobl> You can get it listed in the store under your own namespace by following the documentation at https://juju.ubuntu.com/docs/authors-charm-store.html
[16:01] <lazyPower> themonk: follow the namespace charms listing: https://juju.ubuntu.com/docs/authors-charm-store.html#name-space-charms
[16:02] <lazyPower> themonk: however - if you could expand on what was confusing you - it would help us to clean up that document a bit and hopefully help lead other users down the correct path.
[16:02] <JoshStrobl> themonk, have you used the bzr tool to initialize your local repository, add the files, commit them, etc.
[16:02] <JoshStrobl> exactly
[16:03] <themonk> lazyPower, ok, can i later do it "Are you looking for *recommended* status?"
[16:03] <JoshStrobl> themonk, you can submit your charm to be reviewed whenever you decide to. until then it will reside in your personal namespace, but will still be accessible in the store.
[16:04] <JoshStrobl> themonk, Of course we recommend having it be reviewed, it gets you a recommended status and helps ensure it is reliable, high quality, and properly deploys with Juju :)
[16:04] <themonk> ok, doing it now, thanks
[16:05] <themonk> :)
[16:05] <JoshStrobl> themonk, if you have any questions regarding submitting it, even to your own namespace, feel free to reach out! That said, as lazyPower mentioned, we would love feedback on what you found confusing in the documentation so we can improve it!
[16:14] <themonk> JoshStrobl, ok :) i will
[16:14] <themonk> soon
[16:14] <james_w> pdobrien: still the same error?
[16:16] <pdobrien> james_w: yes... index file has no data for cloud
[16:17] <james_w> pdobrien: where did you upload the metadata this time?
[16:17] <pdobrien> james_w: it doesn't look like it's looking at cloud storage for the metadata, it says source: default cloud images
[16:18] <pdobrien> james_w: it's in the cloud storage, images/streams/v1/index.json and com.ubuntu.cloud:released:imagemetadata.json
[16:18] <pdobrien> james_w: 'juju metadata validate-tools' successfully finds the tools metadata in cloud storage
[16:18] <james_w> pdobrien: in the control-bucket?
[16:19] <pdobrien> james_w: yes, same place as the tools metadata
[16:20] <james_w> pdobrien: juju set-environment logging-config="<root>=DEBUG;juju=TRACE"
[16:20] <james_w> that will turn on debug logging
[16:20] <james_w> you can then try again
[16:21] <james_w> and look in the log of the bootstrap node for more info
[16:31] <pdobrien> james_w: should I be looking in /var/log/juju/machine-0.log?
[16:32] <james_w> pdobrien: I'm not exactly sure
[16:33] <james_w> looking for things like DEBUG juju.environs.simplestreams simplestreams.go:388 fetchData failed for "http://<ip>/v1/AUTH_aaaaaaaaa/simplestreams/data/streams/v1/mirrors.json": cannot find URL "http://<ip>/v1/AUTH_aaaaaaaaaaaaaaaaa/simplestreams/data/streams/v1/mirrors.json" not found
[16:33] <james_w> or similar
[16:41] <pdobrien> james_w: I don't see anything like that.  nothing happens when I validate images
[16:41] <pdobrien> I don't think it's even looking
[16:42] <james_w> pdobrien: oh
[16:42] <james_w> sorry
[16:42] <james_w> not validate-images
[16:42] <james_w> that's all on the client
[16:42] <james_w> deploy or something
[16:43] <pdobrien> ah ok
[16:54] <pdobrien> iames_w: it's finding the index.json for images
[16:57] <james_w> pdobrien: interesting
[16:57] <james_w> can you pastebin the contents of the index.json?
[16:58] <james_w> does it have a cloud with the region/endpoint it is complaining about in the error message?
[16:58] <pdobrien> james_w: sure
[17:00] <pdobrien> james_w: http://pastebin.com/3YHYdpUu
[17:00] <james_w> pdobrien: ok, that looks reasonable
[17:01] <james_w> pdobrien: I assume the url matches the one in the error message?
[17:01] <pdobrien> james_w: yes
[17:03] <james_w> pdobrien: could you paste the relevant section of the debug log file please?
[17:05] <pdobrien> james_w: log: http://pastebin.com/1CDByX0D
[17:07] <james_w> hmm
[17:10] <james_w> pdobrien: ok
[17:11] <jamespage> gnuoy, for tomorrow - https://code.launchpad.net/~james-page/charm-helpers/multiple-https-networks/+merge/235676
[17:18] <james_w> pdobrien: I don't know, sorry
[17:18] <james_w> pdobrien: I can't see what is wrong
[17:18] <pdobrien> james_w: no worries, thanks for taking a look!  I'll put up a post on the mailing list
[17:18] <james_w> pdobrien: you could try filing a bug with that last pastebin, the commands you ran, and the juju status output
[17:18] <james_w> yeah
[17:18] <james_w> an expert can probably spot what is going on
[19:44] <JoseeAntonioR> mbruzek: hey, is your latest merge a fix for bug 1372996?
[19:44] <mup> Bug #1372996: make 00-setup executable <audit> <mongodb (Juju Charms Collection):New> <https://launchpad.net/bugs/1372996>
[19:44] <mbruzek> JoseeAntonioR: Not yet, I am on a call at the moment
[19:45] <JoseeAntonioR> ok, I'm going for it
[20:46] <kwmonroe> lazyPower: i'm having a doozie of a time bringing up the juju-gui on a DO tiny node (512mb).  i saw you deploy this in your blog post yesterday, but didn't see you actually connect.  did you?
[20:47] <lazyPower> yep
[20:47] <lazyPower> not in the demo, but it works
[20:47] <lazyPower> can you show me your history of how you deployed it?
[20:47] <kwmonroe> i'm staring at this spinning circle "connecting to the juju env" and it's possibly the slowest page on the internet.
[20:48] <kwmonroe> wondering if a 1gb DO would do better.. or if somebody is up in my tubes.
[20:48] <lazyPower> it woudl be better on a 1gb do
[20:48] <lazyPower> you're underpowering your state server by colo'ing yoru gui on it
[20:49] <kwmonroe> ack.. fwiw, juju docean bootstrap --constraints="mem=512M, region=nyc3" && juju deploy juju-gui --to 0
[20:49] <hatch> kwmonroe: that should be fine
[20:49] <hatch> when you refresh the page does it hang still?
[20:49] <lazyPower> you dont need to specify the mem if you're going for tiny's
[20:49] <lazyPower> it defaults to tiny
[20:50] <kwmonroe> refreshing doesn't seem to help hatch - https://104.131.29.26/
[20:51] <kwmonroe> sometimes it seems like it's progressing (bg turns dark instead of grey).  other times i watch the spinner.
[20:51] <hatch> looking
[20:52] <hatch> kwmonroe: I can get to the login screen
[20:52] <hatch> right away actually
[20:52] <kwmonroe> hmph
[20:52] <hatch> are you behind something which blocks websockets?
[20:52] <hatch> secure websockets specifically
[20:53] <lazyPower> kwmonroe: pull it up in firefox
[20:53] <kwmonroe> i dunno hatch - i don't think so
[20:53] <lazyPower> i had this issue once before with chrome -dev
[20:53] <lazyPower> but it was intermittant
[20:53] <JoshStrobl> I pulled it up fine in Chrome.
[20:53] <kwmonroe> yeah, i did take the chrome update today but haen't restarted it
[20:53] <hatch> kwmonroe: ok what browser are you in? I'd like to do a little debugging to try and find the problem
[20:55] <kwmonroe> hatch: i was in chrome, but hadn't restarted the browser since an update this morning.  derp.  after restart, it's working in chromium 37
[20:55] <kwmonroe> sorry for the noise - thx lazyPower and hatch!
[20:57] <hatch> kwmonroe: haha np :) glad it's working
[20:58] <hatch> lazyPower: bic2k is having issues with the osx brew recipe - is there any known issues with it?
[20:58] <lazyPower> hatch: a user showed up this morning and introduced a new issue about missing command(s)
[21:01] <lazyPower> hatch: https://bugs.launchpad.net/juju-core/+bug/1372550
[21:01] <mup> Bug #1372550: juju metadata missing from brew juju 1.20.7 <feature> <metadata> <osx> <papercut> <juju-core:Triaged> <https://launchpad.net/bugs/1372550>
[21:01] <hatch> ahh I think his was charmtools related
[21:03] <bic2k> lazyPower: Ya, mine is the osx brew forumla fails out with some python related issue. Figured it would work since its mentioned in the charm docs.
[21:03] <lazyPower> bic2k: i brew installed juju thsi morning
[21:03] <lazyPower> it was confirmed working ~ 9am EDT
[21:04] <bic2k> lazyPower: `juju` is installed just fine `charm-tools` does not install
[21:04] <lazyPower> bic2k: stacktrace for me?
[22:47] <aisrael> Is there a preferred/recommended templating module for charming in python?
[23:28] <thumper> aisrael: I think there is something in the charm helpers...
[23:28] <thumper> but I don't recall exactly where
[23:28] <thumper> marcoceppi: ?
[23:28] <aisrael> Yeah, that's a good point. I can look at the templating there as an example.
[23:28] <aisrael> Thanks!
[23:30] <aisrael> Looks like it's using Cheetah