[00:36] <marcoceppi> hazmat: I ran in to an issue
[00:36] <marcoceppi> hatch ^^
[00:36] <marcoceppi> but he's offline
[00:36] <marcoceppi> I'll file bugs
[00:40] <rick_h_> marcoceppi: definitely, anything big?
[00:40] <marcoceppi> rick_h_: well, commit doesn't tell me anything
[00:40] <marcoceppi> like I press commit
[00:40] <marcoceppi> then wait
[00:40] <marcoceppi> and hope
[00:40] <marcoceppi> and pray
[00:40] <rick_h_> huh? you don't get the summary? 
[00:40] <marcoceppi> well, I get summary
[00:40] <rick_h_> and then all the blue circles should turn yellow
[00:40] <marcoceppi> then I'm like "make it so"
[00:41] <marcoceppi> not after some time of lag
[00:41] <rick_h_> and then they turn off the cirlces as Juju takes the commands?
[00:41] <marcoceppi> and it says X items to commit at the bottom
[00:41] <marcoceppi> needs like a spinner
[00:41] <marcoceppi> or something on the commit button
[00:41] <rick_h_> marcoceppi: hmm, ok. We'll take a look at it. 
[00:41] <marcoceppi> so I know it's working
[00:41] <rick_h_> it should be resetting the button after you commit
[00:41] <marcoceppi> a few times I tried to deploy and never got the confirmation screen on commit
[00:41] <rick_h_> we allow you to stack sets of changes, you don't have to wait for one to complete before starting another one
[00:41] <marcoceppi> had to hard refresh and try again
[00:41] <marcoceppi> interesting
[00:42] <marcoceppi> I didn't capture any debug output
[00:42] <marcoceppi> I'll try again to replicate
[00:42] <rick_h_> ok, what provider was this? Was the network slow? I want to try to match up our QA/replication. 
[00:42] <marcoceppi> yeah
[00:42] <marcoceppi> it was local provider and I was connect to my home machine over sshuttle
[00:42] <rick_h_> marcoceppi: ok, thanks a ton for the feedback. I can see where there might be some issues to make more solid there. 
[00:42] <marcoceppi> since I was 25 machines deep
[00:43] <marcoceppi> rick_h_: np, I'll try to videotape/record the issue with deploying a service if it crops up again
[00:43] <marcoceppi> hard to explain
[00:43] <rick_h_> ok, we can try to replicate some slower network and do some more looking at it. Most of our QA is just our machine on lxc, ec2, azure, and maas
[00:43] <marcoceppi> otherwise it was a great experience
[00:43] <rick_h_> ok cool, hopefully worth the growing pains of a new release the day of
[00:43] <marcoceppi> Iw as able to answer the density question by using the machine view
[00:43] <rick_h_> we'll get it more polished for sure
[00:43] <marcoceppi> hah, worth it
[00:43] <marcoceppi> I explained that this was like brand new
[00:43] <marcoceppi> and played it down
[00:43] <marcoceppi> everyone loves a live demo anyways
[00:43] <rick_h_> lol
[00:43] <rick_h_> you know it
[00:44] <rick_h_> yea, please do file bugs with as much info as you can pull together and we'll look into it. 
[00:44] <marcoceppi> def
[09:47]  * fabrice going for lunch with friends
[11:08] <rick_h_> morning
[11:31] <rick_h_> boom! https://insights.ubuntu.com/2014/09/26/juju-machine-view-more-control-at-your-fingertips/
[11:31] <rick_h_> go team go, go team go!
[12:08] <rick_h_> luca__: ok email to canonical-tech sent
[12:08] <luca__> rick_h_: nice
[12:14]  * rick_h_ ducks
[12:18] <rick_h_> ok, posts out, email out, sharing has begun, filed over at the juju reddit...now time for breakfast
[12:31] <jcsackett> there's a juju reddit?
[12:31] <jcsackett> huh. i'll be damned. neat.
[12:33] <rick_h_> hah
[12:42] <rick_h_> Makyo's video is outpacing mine. They love his professional tones! :)
[12:45] <jcsackett> Makyo does have a very good "presenting" voice.
[13:35] <jcsackett> rick_h_: did we test the charm with charm-upgrade? b/c for grins i upgraded my installation this morning (for my blog and stuff) and i'm not seeing changes. :(
[13:36] <jcsackett> upgraded to cs:trusty/juju-gui-8
[13:36] <rick_h_> jcsackett: so it worked on staging and had an error on production
[13:36] <rick_h_> jcsackett: check for an error with a symlink command. frankban was looking into it and seeing it he could replicate it
[13:37] <jcsackett> rick_h_: did it come up in `juju status`? b/c i'm getting no errors reported.
[13:37] <rick_h_> jcsackett: not sure, it was noted in the RT that they hit the error and worked around it by killing the directory and resolving/retry. 
[13:37] <frankban> jcsackett: have you set juju-gui-source to 1.2.0?
[13:37] <rick_h_> which I guess means it hit an error
[13:38] <rick_h_> frankban: oh that's a good point, we have those notes in the prodstack stuff but that's non-obvious if people just try to upgrade their charm :/
[13:38] <rick_h_> ugh, that's a horrible ux sorry jcsackett. Never thought about that 
[13:39] <jcsackett> frankban: my gui-source appears to be "local".
[13:39] <frankban> rick_h_: yeah updating the charm does not mean updating the GUI currently, and that's not obvious
[13:39] <rick_h_> jcsackett: yea, set it to 1.2.0
[13:39] <rick_h_> and then watch out
[13:39] <jcsackett> frankban, rick_h_: does setting gui-source to stable work, or explicit revision required?
[13:39] <frankban> jcsackett: yeah, but since it didn't change, config-changed does not re-run the GUI installation
[13:40] <frankban> jcsackett: stable should work
[13:40] <jcsackett> frankban: well, it's "local" now, so switching to "stable" will run config-changed for me, right?
[13:40] <rick_h_> jcsackett: right, you have to trigger some sort of 'change' and in production we set a hard value. 
[13:40] <frankban> jcsackett: but then next time you'll still have to change "stable" to something else, so I'd prefer the specific version
[13:40] <jcsackett> ah, but then i'll have to set it again to update next time. ok, explicit revision it is. :)
[13:40] <jcsackett> frankban: indeed. :p
[13:41] <rick_h_> that darn disconnect between a charm and what it does vs the software contained. 
[13:41]  * jcsackett nods
[13:42] <jcsackett> rick_h_: it actually makes sense, if i stopped to think about it.
[13:42] <rick_h_> jcsackett: yea, but it is still a horrible UX. I'm trying to think of how one would make that more seemless
[13:42] <jcsackett> rick_h_: i wouldn't want my charm to be tied to the version of the software it installs. ghost is that way now (version is set in the charm and it's a bit of a pain.
[13:42] <rick_h_> jcsackett: yea, it's not an easy fix for sure
[13:43] <jcsackett> yeah.
[13:43] <frankban> rick_h_: we could introduce a new "latest" juju-gui-source option, meaning each time the charm is updated the last revision is downloaded from lp
[13:43] <jcsackett> whoo! update worked, no problems.
[13:43] <rick_h_> frankban: hmm, and cron up something that watches it?
[13:44] <rick_h_> frankban: I was thinking the ideal way would be to get a notification into the GUI itself on charm upgrade or something
[13:44] <rick_h_> frankban: "There's a new version of the GUI available, would you like to upgrade?"
[13:44] <rick_h_> frankban: and then the gui can set the source on itself :)
[13:44] <rick_h_> jcsackett: awesome, <3
[13:44] <jcsackett> that would be pretty cool, actually.
[13:45] <frankban> rick_h_: not really a cron, I'd still prefer an explicit user action. it should just run when you upgrade the charm
[13:45] <rick_h_> but I'm not sure how the GUI would know it had a new source available or something. And what happened if you intentionally set an older version
[13:45] <rick_h_> frankban: that's true, if you upgrade the charm and the old source isn't there and a new one is, upgrading that source seems resonable at first glance
[13:46] <rick_h_> the tarball that is, in the releases folder
[13:54] <hazmat> Makyo, nice work on the voice over the screencast.. you got some complements on it
[13:55] <rick_h_> sweet
[14:20] <luca__> Is this sentence true or false? “In the CLI (command line interface) each unit has to be placed using a specific command, this tends to be quite laborious with most developers scripting it. “
[14:20] <rick_h_> luca__: not sure checking if add-unit can take a list of placement directives
[14:21] <luca__> rick_h_: cool :)
[14:21] <rick_h_> luca__: hmm, help text isn't clear, I'll have to test it out biab
[14:22] <luca__> rick_h_: ok
[14:22] <luca__> rick_h_: I just wanted to express the problem
[14:23] <rick_h_> luca__: yea, I think that's true, but don't want to lie to you
[14:24] <luca__> rick_h_: I’ll run with it for now
[14:24] <luca__> >:)
[14:24] <rick_h_> luca__: bah, hitting ec2 issues due to the big reboot today 
[14:29] <lazyPower> rick_h_: at some point today, you guys need to pull together an animated gif team photo of your team in front of the machine view gui, and all of you just drop the mic and walk off frame.
[14:29] <rick_h_> lazyPower: lol
[14:35] <hatch> holy we have the main page
[14:36] <rick_h_> :)
[14:37] <rick_h_> hatch: when you get your post up let me know and I'll make sure to reshare things out as much as I can
[14:37] <hatch> yeah sure I'll just make some updates now
[14:37] <rick_h_> np
[14:38] <hatch> rick_h_:  was there one from design somhwere too?
[14:39] <rick_h_> luca__: ^
[14:44] <rick_h_> and Makyo's video races ahead to 100 views https://www.youtube.com/user/celebrateubuntu wheee
[14:45] <luca__> rick_h_: mine is out for review
[14:46] <rick_h_> luca__: gotcha hatch ^
[14:46] <hatch> cool, luca will it be up today?
[14:47] <Makyo> \o/
[14:48] <Makyo> Not a big deal, but any chance of changing my name on the post?  It's fine if not, just a bit of a clash with the video.
[14:51] <rick_h_> Makyo: on the insights one? Did I use matt?
[14:52] <Makyo> rick_h_, yeah, toward the bottom. Maybe it's just the title of the video, not sure.
[14:52] <rick_h_> Makyo: I've put in a request for update 
[14:52] <Makyo> Not a big deal.
[14:52] <Makyo> Ah, thanks rick_h_ :)
[14:53] <rick_h_> no, it's a good deal. Sorry about that. It wasn't in my write up but they probably grabbed it from somewhere internalaly
[14:54] <Makyo> YEah, that's fine!  Since it's taking forever to change it legally, it hasn't propagated.
[15:09] <rick_h_> https://docs.google.com/a/canonical.com/forms/d/14pS3d21OKnaYVkKV6eLoLtW77GwWEMgPr-sMimoUYNk/viewform
[15:12] <hatch> luca__: do you think it'll be live today?
[15:13] <rick_h_> heh, the luca__ tell all book of the century! or blog post forced upon him by peer pressure :P
[15:14] <hatch> lol
[15:14] <luca__> hatch: yes
[15:14] <luca__> haha
[15:14] <luca__> it’ll be done!
[15:14] <luca__> writting blog posts is so hard
[15:14] <rick_h_> luca__: what time are we all meeting at the bar?
[15:14] <luca__> I can never dedicate time for it
[15:15] <luca__> haha
[15:15] <luca__> 11am? :D
[15:27]  * rick_h_ heads for early lunch biab
[15:32] <hatch> luca__: ok when you're thing is up can you ping me with the url so i can add it to my post?
[15:32] <luca__> hatch: sure thing, Ale is just reading it now
[15:37] <hatch> This is interesting http://www.getpostman.com/ looks like CURL but for the browser
[15:47] <rick_h_> Makyo: name updated
[16:08] <luca__> rick_h_: hatch ale has had to run off so I’m not sure if she’ll read it today but I’ve the doc with you guys. If you can read it and give feedback that would be great.
[16:08] <hatch> ok sure sounds good
[16:28] <Makyo> rick_h_, thanks!
[17:28] <rick_h_> jujugui I'm going to EOD early and head out. Thanks again for the great release day! Have a good weekend
[17:35] <lazyPower> https://plus.google.com/100016143571682046224/posts/PaVGh51FYCR - i'm just going to leave this here...
[17:49] <jcsackett> lazyPower: awesome!
[20:23] <fabrice> have a good week end everyone
[21:07] <sebas5384> what a nice surprise to see the "machine view" in the https://jujucharms.com :)
[21:07] <sebas5384> what a beautiful work! 
[21:07] <sebas5384> \o/
[21:24] <rick_h_> sebas5384: <3 
[21:50] <sebas5384> rick_h_: :D
[22:19] <sebas5384> rick_h_: I think we have some problems with the charm store search
[22:25] <sebas5384> some charms where missing
[22:46] <rick_h_> sebas5384: let me know which ones are missing and I'll look. We can check if they pass proof (they won't show if they don't) or something else. 
[22:49] <sebas5384> rick_h_: i think they are back to normal now
[22:50] <rick_h_> sebas5384: ah ok, sometimes when the stuff updates and the fulltext index is hit they fade for a few min
[23:31] <sebas5384> ahh ok
[23:31] <sebas5384> :)
[23:32] <sebas5384> rick_h_: we started to work in a juju client api
[23:33] <sebas5384> in javascript
[23:33] <sebas5384> https://github.com/TallerWebSolutions/macumba.js/tree/promised-based-api
[23:33] <sebas5384> inspired in the macumba project :P
[23:34] <sebas5384> but we are a little dependent of the socket opened by the juju-gui
[23:53] <rick_h_> sebas5384: ok, we've been removing promises as we hit some issues with them in use if they are to the A+ spec
[23:53] <rick_h_> sebas5384: https://github.com/juju/juju-gui/blob/develop/app/store/env/go.js is our api 
[23:58] <sebas5384> hmmm rick_h_ good to know