[17:33] <frankban> uiteam, rick_h, bac, jrwren: initial branch for the redis charm: https://code.launchpad.net/~frankban/charms/trusty/redis/initial-charm/+merge/259812
[17:34] <frankban> could you please take a look? sorry for the big diff
[17:35] <frankban> lazyPower, cory_fu: at https://code.launchpad.net/~frankban/charms/trusty/redis/initial-charm/+merge/259812 you can find the initial impl of the redis charm with the services framework
[17:36] <frankban> lazyPower, cory_fu all your suggestions are welcome!
[17:46] <hatch> wow....that diff ;)
[17:51] <bac> i think that is a misuse of the term.
[17:51] <hatch> of diff?
[17:51] <hatch> you mean because it's  the first branch?
[17:51] <hatch> so technically it's diff is undefined? 
[18:15] <bac> hatch: no, i meant the other was basically thrown out and replaced.
[18:43] <hatch> oh :)
[21:47] <mattrae> is it possible with juju gui and the local provider, to choose which machines i deploy a bundle to? when i click 'deploy this bundle' it asks if i'm sure, but doesn't give me an opportunity to choose which machines i want to use
[21:49] <rick_h_> hatch: ^ 
[22:16] <hatch> mattrae: hey sorry I stepped out, still around?
[22:21] <mattrae> hatch: yeah i'm still here :) yeah i was just wondering if juju-gui had the feature of allowing me to choose the machines a bundle is deployed to
[22:22] <hatch> mattrae: it does in the beta release of the charm. If you're interested in giving that a go. There are a few known bugs that we are squashing still 
[22:22] <mattrae> hatch: i'm using the local provider, and i noticed it juju-gui doesn't allow me to manually place units. it only lets me auto place. so is this just a restruction just of the local provider?
[22:22] <hatch> nope that's just a restriction of that version of the GUI - bundles were an all-or-nothing thing
[22:23] <mattrae> hatch: ahh ok, i did try deploying the with juju-gui-source 'develop'. does should that get the beta version?
[22:23] <hatch> juju deploy cs:~juju-gui/trusty/juju-gui-49 && juju set juju-gui juju-gui-source=develop juju-gui-console-enabled=true juju-gui-debug=true
[22:23] <hatch> there you'll wawnt to run that
[22:23] <mattrae> ah sweet, i'll give it a try
[22:23] <mattrae> thanks hatch
[22:24] <hatch> the last two config options are for us. If you see any issues the browser console should show an error which you can copy/paste to me :D
[22:24] <mattrae> cool, sounds good :)
[22:24] <hatch> two known bugs you may run into https://bugs.launchpad.net/juju-gui/+bug/1456750 and https://bugs.launchpad.net/juju-gui/+bug/1454765
[22:24] <mup> Bug #1456750: Changing the display name after setting config doesn't update the name in set config <landscape> <juju-gui:In Progress by hatch> <https://launchpad.net/bugs/1456750>
[22:24] <mup> Bug #1454765: deploying large bundle across nodes fails <juju-gui:New for makyo> <https://launchpad.net/bugs/1454765>
[22:25] <hatch> both are being fixed right now, but just so you're aware
[22:25] <mattrae> cool no problem
[22:25] <hatch> I'll be around for a while now so if you run into any issues or have any more questions just ping
[22:32] <firl> hatch : let me know if you want me to try to duplicate / look at 1454765 with you
[22:35] <hatch> hey firl Makyo is actually just finishing up a branch which fixes that issue 
[22:36] <firl> very cool
[22:36] <hatch> we were actually able to find a number of other edge case issues while fixing your bugs...so yay!
[22:36] <hatch> :)
[22:36] <firl> hah nice
[22:37] <firl> i’ve been using autopilot because I couldn’t get it rolling; will have to try it again later once it gets released
[22:37] <hatch> definitely - how are you liking autopilot?
[22:38] <firl> It’s nice for a quick turn around, definitely a lot of potential 
[22:39] <firl> it’d be nice to see a juju-gui around it to see how it interacts / add nodes via the gui after install and what not
[22:39] <hatch> yeah, we're hoping to get this release out next week 
[22:40] <firl> oh yeah? nice.
[22:43] <firl> If I could more easily deploy the openstack / ceph bundle, I would use the juju-gui in a heartbeat
[22:43] <hatch> yeah this release will really help with that
[22:44] <firl> I might have to check it out next week then
[22:46] <hatch> firl: as far as making openstack easier to deploy. That primarily focuses around the machine placement functionality? Or were there other things which would help
[22:47] <firl> The placement before “applying” a bundle was one of the issues I was encountering. I think “sensible” defaults or a guide around those that would be the equivilent of what autopilot encourages was the other issue I encountered.
[23:09] <mattrae> hatch: so far when i drag a unit to a machine, it has no effect in chrome.. when i do it in firefox, i get a page cannot be loaded message from firefox and have to hit reload to log back into juju-gui
[23:10] <hatch> hmmm
[23:10] <hatch> ohhh 
[23:10] <hatch> (interesting UX issue)
[23:10] <hatch> mattrae: so you need to first select the machine so that 'root container' shows up in the right column
[23:10] <hatch> then drag the unit to that
[23:11] <mattrae> hatch: ahh thanks, looks like that is allowing me to add the unit.
[23:12] <hatch> I'll file an issue around this...because it isn't obvious
[23:15] <mattrae> hatch: cool thanks :)
[23:40] <hatch> mattrae: I'm stepping out for a while, if you run into any more issues ping and I will respond when I get back