=== kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === kadams54 is now known as kadams54-away === perrito667 is now known as perrito666 [14:35] lazyPower: hey what software do you use for your blog now? [14:35] hatch: pellican [14:36] ahh I thought you'd might use Hugo [14:36] hugo was in an inconsistent state when i evaluated it [14:36] it was a toss up between jekyll and pelican. i opted into python [14:37] ahh gotcha [14:37] I added a few new features to the ghost blog this weekend [14:37] I saw ;) [14:37] (I saw your comment on an issue thx) [14:37] * lazyPower thumbs up [14:37] you're on the right track [14:37] you care about concerns. I'm +1 for that * 100000000 [14:38] encapsulation = key to a rich experience [14:38] thanks - the big issue now is how to properly add ssl support [14:38] thats the responsibility of the front-end [14:38] nginx, haproxy, etc. [14:38] and looking over the existing relations - it seems like its a candidate for a new relationship so you can encapsulate teh ssl certificate in the middleware (ghost) - and pass it off over the wire to the web head when it creates teh vhost [14:39] but that may not be the propper approach. I haven't given it much more thought than the 5 minutes i spent reading issues. [14:39] I wish we had a promoted nginx charm [14:39] so I could do haproxy > nginx > ghost [14:39] and call it a day :) [14:40] you dont really gain much by putting haproxy in front of nginx imho [14:40] nginx as a scale out LB webhead is phenomenal in terms of performance [14:40] well nginx should probably be a subordinate [14:40] is it? [14:40] there's use cases for both [14:40] yep [14:40] oh interesting [14:40] i ran a pure nginx shop @ level [14:40] it was the lowest maintenance webheads i had [14:41] so you're the guy to write the nginx charm then? :P [14:41] http://nginx.org/en/docs/http/load_balancing.html [14:41] hatch: well, let me frame the context here [14:41] I figured this out http://fromanegg.com/post/105250564587/how-to-rewrite-and-redirect-with-haproxy [14:41] i have a broken rails charm, dns charm to be completed, kubernetes work to catch up on, docker charm to add features to, and documentation all around to update [14:41] so that I can use the existing haproxy charm [14:41] yeah, i did enjoy that read and you're on teh right path there [14:41] oh so you have lots of free time :P [14:42] something like that :) [14:42] I'm not sure that haproxy can do ssl with 1.4 [14:42] something I'll have to look into this week [14:42] i think / feel at this point - you're comign to a cross roads where it makes sense to develop what you want vs jack hammering haproxy [14:43] take the existing nginx / apache charms - convert to a sub, and implement the relationship you want/need - propose @ the list for discussion and if they dont like the implementation - PR's are welcome [14:44] you win by getting what you want, store wins by getting another implementation of a webhead [14:44] * lazyPower afk's to head to the dentist [14:44] looks like haproxy requires 1.5 [14:44] enjoy :) [14:44] - for ssl that is [15:38] uiteam I need one more review for my guicharm branch (small) https://code.launchpad.net/~hatch/charms/trusty/juju-gui/add-uuid-configjs/+merge/248826 [15:40] don't everyone jump at once :P === kadams54 is now known as kadams54-away [17:07] rick_h_: ping [17:22] sebas5384: pong [17:23] rick_h_: hey! I'm at the event, and tomorrow I'm gonna present using the online demo of juju gui [17:23] sebas5384: cool a new release was cut with bug fixes [17:23] rick_h_: I sow the bugs are still there [17:23] sebas5384: so let me know if you need anything [17:23] huh? [17:23] great!! [17:23] hatch: ^ [17:23] sebas5384: try upgrading [17:23] * hatch perks up [17:23] take a look [17:23] demo.jujucharms.com [17:24] demo.jujucharms.com was not updated [17:24] sebas5384: oh right, it's not installed there yet [17:24] the real release was [17:24] sebas5384: that'll be Tues unfortunately [17:24] hmmm [17:24] sebas5384: but hte gui charm is updated [17:24] so deploy it somewhere and it'll be good [17:24] sebas5384: can you deploy the real charm to an env? [17:24] even local? [17:24] sebas5384: a workaround is to not drag from the charmbrowser [17:24] yeah i'm gonna do it locally [17:24] but instead click it then 'add to canvas' [17:24] if you must use demo.jc [17:25] hatch: demo.jc ? [17:25] demo.jc.c [17:25] demo.(j)uju(c)harms.(c)om [17:25] :) [17:25] sorry don't know what that is [17:25] abreviation fail [17:25] hahahhaa [17:25] lol [17:25] ok got it [17:26] lemme know if you run into any other issues [17:26] rick_h_: is supposed to be swapping today :P [17:27] i'm have to leave now but I'll be back and install it to see whats happen [17:27] later :D [17:28] hatch: swapping today? [17:28] frankban: so I'm merging in my branch into the develop-trunk branch now - I complete the merge but I now need to write a comment. SHould I just copy the first msg from the PR? [17:29] rick_h_: yeah, didn't you say you were swapping today [17:29] ? [17:29] hatch: oh yea, leaving now :) [17:29] :) cya [17:29] hatch: yes [17:30] thx [17:32] Makyo: I just merged in the branch that was in pending - you may want to pull guicharm [17:32] hatch, will do, thanks [17:44] hatch: does juju-gui have documentation online somewhere? [17:44] lazyPower: user docs? [17:44] si [17:44] negative [17:44] there is a guide on how to use it when you first boot it up though [17:44] ಠ_ಠ [17:44] there is also the charm details [17:44] well thats better than nothing - can i get a link? [17:44] but that's it [17:45] lazyPower: to see it you can go here https://demo.jujucharms.com/ and then click "More" then click "Tutorial" [17:45] it's pretty basic [17:46] oh [17:46] i asked about the wrong product [17:46] * lazyPower facepalms [17:46] i meant quickstart, sorry [17:46] lol [17:46] * lazyPower hangs his head in shame [17:46] not really beyond the help once it's installed [17:46] mbruzek was working on some I think [17:47] lazyPower: I'd love to see some of those docs on docs.jujucharms.com [17:47] hatch: your dead to me [17:47] lol [17:49] lazyPower: bug mbruzek I am pretty sure he said he was working on the documentation last week [17:50] well this exists [17:50] https://pypi.python.org/pypi/juju-quickstart [17:50] its rather sparse, but it helps [17:51] hatch: if i write the base docs, you guys gonna carry it to the finish line and keep it up to date? [17:52] best bet is to fire an email with your plans to the mailing list [17:52] I can probably churn them out today while i'm digging my hands deep into kubernetes docs [17:52] hatch: you mean https://github.com/juju/docs/issues/261 doesn't cover it sufficiently? [17:54] lazyPower: assuming the appropriate parties see that bug :) [18:01] lazyPower: when adding features to my ghost charm - is it better to queue up a bunch of changes then push up for promulgation review to reduce noise in the queue? Or does mutliple updates not really matter as long as you only do a single review sometime in the future [18:01] hatch: i'm a fan of small changes that are dependency linked [18:02] but thats personal preference. it makes the review go much faster as concerns are isolated and I know that i'm making an isolated change [18:02] it took me a while to grokk launchpad and how it does that - but stub quickly educated me in that realm [18:02] so if I pushed 3 updates, would there be three items in the queue or would it get consolidated into one? [18:02] it would be 3 items [18:03] and you don't mind the noise [18:03] I suppose it does make the reviews faster [18:03] but more frequent [18:04] yeah, i dont mind the noise. if you have dependency linked changes - it may cause failures in CI if they are dependent on teh functionality landing - so ymmv [18:04] gotcha - I'll stop queuing them up in GH :) [18:10] * mbruzek returns from lunch. [18:10] * mbruzek reads scroll back to see what bus he was thrown under. [18:11] just a school bus [18:11] hatch: I I was working on a bundle's documentation when I asked about the quickstart stuff. [18:11] nothing too bug [18:11] big [18:11] ohh [18:11] well then! [18:13] Hey hatch. I hosted a Ubuntu Global Jam for Minnesota and we found a few bugs over the weekend on jujucharms.com. I could not remember where to create the bug so I just did it on launchpad. [18:13] Since getting to work today lazyPower has set me straight that you would like those bugs in github [18:14] Do I need to copy them over or do you see the two that I created this weekend about "no author" [18:14] no problem - I pointed them out to the peeps in standup this morning [18:14] thanks for those [18:14] hatch: wait until you get the bill ;) [18:15] I suspect those could be the way the charm was pushed, to the repository. If you need something done from a charmer side ... please ping lazyPower [18:15] uhh yeah...sent those to invoices@dev.null [18:15] :P [18:15] haha [18:15] hatch: funny, i have dev.null aliased to fromanegg.com [18:15] \o/ [18:15] lol [18:15] haha [18:15] so that's why I'm getting all this spam [18:16] * lazyPower whistles [18:20] ermahgerd so much documentation kadams54-away [18:20] :) [18:24] kadams54-away: review done [18:28] hatch: just shot the email @ the list. feel free to reign fire down upon my plans [19:19] lazyPower: email looks good to me [19:19] :) === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 [21:09] hatch: thanks for the docs review. Yeah, there's still undocumented stuff… and I really should update to use doctests… and then there's API docs to generate… *sigh* [21:10] haha - docs are hard work for sure === kadams54 is now known as kadams54-away [21:59] Morning === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away === kadams54-away is now known as kadams54 === kadams54 is now known as kadams54-away