[03:32] <hatch> Makyo: I was thinking the juju terminal console - wouldn't he be able to get it from there? Improv should be dumping that sort of stuff no?
[08:20]  * mariusko thinks he hits bug #1149410 again...
[08:20] <_mup_> Bug #1149410: Stuck on "Trying to connect to the Juju environment" <juju-gui:Incomplete> <juju (Ubuntu):Incomplete> < https://launchpad.net/bugs/1149410 >
[08:21] <frankban> mariusko: what provider are you using?
[08:22] <frankban> mariusko: and what version of the GUI?
[08:25] <mariusko> frankban: AWS
[08:26] <mariusko> I changed back to a stable version. That is juju-api-branch: lp:~hazmat/juju/rapi-rollup and juju-gui-source: stable
[08:26] <mariusko> Worked for some time. I also sometimes have more success using IP address that DNS name
[08:53] <frankban> mariusko: you switched back to stable using "juju set"?
[08:57] <mariusko> frankban: nope, it was a new installation
[08:57] <mariusko> new deployment
[09:02] <frankban> mariusko: any javascript console errors?
[09:09] <mariusko> frankban: "Application Cache Error event: Master entry fetch failed (-1)"
[09:10] <frankban> mariusko: humm.. are you using chrome/chromium?
[09:10] <mariusko> frankban: chromium. Isn't FF still not supported?
[09:17] <frankban> mariusko: try to delete the appcache: go to chrome://appcache-internals/ and remove the entry corresponding to your ec2 machine
[10:01] <mariusko> frankban: same problem with FF. Python process on the machine is using a lot of CPU 
[10:02] <mariusko> but it has 1,7 GB RAM
[10:56] <mariusko> "WebSocket connection to 'wss://x.x.x.x/ws' failed: WebSocket is closed before the connection is established"
[11:02] <mariusko> frankban: debugging further, /ws gives "503 Service Unavailable: No server is available to handle this request."
[11:03] <mariusko> I see that there is a haproxy there, and "http://127.0.0.1:8080/" gives nothing
[11:06] <mariusko> Uhm, even "/var/lib/juju" is gone on the server now
[11:44] <frankban> mariusko: any error in /var/log/upstart/juju-*
[12:25] <rick_h_> did something change with the tests? The ones loading json are failing for me as the paths to the test/data/xxx seems to have changed?
[12:25] <rick_h_> bah, some test is monkeying with the url adding a / to the end in chrome causing the paths to fail
[12:29] <frankban> rick_h_: make test-server works well for me in trunk
[12:30] <rick_h_> frankban: yea, there's a test half way through that's adding a / after index.html and causes all the relative paths to test data files to be index.html/data/xxxx.json
[12:30] <rick_h_> frankban: might be an interaction with chrome I've got here
[12:31] <rick_h_> hmm, does it for me in test-prod as well though so must not be a chrome thing
[12:33] <rick_h_> nvm, guess it's something in this branch. 
[12:43] <rick_h_> hatch: when you get a chance can you peek at/QA the button fix you noticed yesterday? https://codereview.appspot.com/8363043
[12:44] <mariusko> frankban: killed the instance. Will check next time. New instance working.
[12:45] <frankban> mariusko: ack
[13:25] <bac> hatch: ping when you're around
[13:25] <rick_h_> bac: looks like the branch yesterday went ok then? Caught the reviews after EOD. 
[13:26] <bac> rick_h_: yeah, just doing some clean up
[13:26] <rick_h_> bac: I didn't lead you too far astray when what they meant I hope?
[13:26] <rick_h_> cool
[13:26] <bac> thanks for your advice
[13:32] <Makyo> hatch, re juju terminal/improv - that was a live install, not improv, but there is a chance the bootstrap node would have it in its logs; I don't know if that all gets logged.
[13:36] <Makyo> Also, frankban, last daily for the tablet just about bricked the thing, so I was screwing with that all yesterday, sorry I didn't get more review done; I'll do that first thing.
[13:36] <frankban> Makyo: no problem, and thanks.
[13:38]  * frankban fighting against allhands
[13:55] <benji> hatch: do you need a review for "implement unexpose"?
[13:57] <hatch> benji yeah looks like i need one more
[13:57] <benji> hatch: I'll be glad to.  I don't see the URL on the card, do you have it at hand?
[13:57] <hatch> https://codereview.appspot.com/8339044/
[13:57] <hatch> thank yas
[13:58] <hatch> bac: I'm here
[13:58] <bac> hey hatch
[13:59] <bac> thanks for the excellent review.  i only had one question about one of your comments.  i think my question is in the review now.
[13:59] <hatch> alright lemme check
[13:59] <bac> first comment at https://codereview.appspot.com/8338043/diff/5001/app/store/endpoints.js#newcode24
[14:00] <hatch> the endpoints map and subscriptions is the properties I was talking about - if you define them in the initializer then they are local to the instance not on the prototoype
[14:00] <hatch> that's what I mean
[14:00] <hatch> wrt 'following properties'
[14:02] <hatch> so judging from your comments you already did that
[14:03] <hatch> brb
[14:04] <bac> hatch: cool.  please update the review if you think it is landable
[14:17] <hatch> bac: endpoints.js has a syntax error...
[14:18] <hatch> lol how did that get through the linter
[14:18] <hatch> ln 44
[14:20] <bac> hatch: it is a style issue but not syntax i think
[14:20] <bac> fixed
[14:21] <hatch> oh right
[14:21] <hatch> that's what i meant :)
[14:22] <hatch> LGTM'd
[14:22] <bac> thx
[14:22] <bac> hatch: i still have an open question about reset as i'm unsure when that is called.
[14:23] <bac> hatch: should reset call unbind?
[14:25] <hatch> if there aren't any endpoints in there would you still want to listen to those events?
[14:26] <hatch> if reset calls unbind then you'll need to rebind them again no?
[14:30] <bac> yes
[14:31] <bac> i'll land as is and pick ben's brain later.
[14:35] <frankban> benji: do you have some notes re missing go watcher attrs? I am filing a bug I will work on after my current handlers/converters refactoring branch is merged
[14:36] <benji> frankban: I turned the ones I found into cards.
[14:39] <frankban> benji: are they in story 1? I cannot find them in the board
[14:39] <benji> frankban: I only found two and one is done now.
[14:40] <benji> perhaps you found a treasure trove of missing data that I missed.
[14:43] <frankban> benji: no, I am just trying to figure out what's missing.
[14:53] <hatch> rick_h_: is huw using OSX and that's why he can't lbox?
[14:58] <frankban> benji: do you have a minute for a quick call?
[14:58] <rick_h_> hatch: no, he's had a few diff errors. A couple look like LP timeouts. Another was just problem figuring our linting. CSS rules matching xxx_yyy vs xxx-yyy don't actually output a message
[14:58] <rick_h_> hatch: so he's just not spent time figuring it all out so he's getting a pass
[14:59] <benji> frankban: sure
[14:59] <benji> frankban: the normal hangout?
[14:59] <frankban> benji: yes, I am there
[15:00] <benji> frankban: hold on, the Google hangouts plugin isn't working
[15:01] <hatch> rick_h_: ahh ok
[15:05] <hatch> rick_h_: I'm a little confused as to why we are using images for that add button - I don't see anything there that coudln't be done with a icon font and some css
[15:06] <rick_h_> hatch: I'm not sure at all. Since we're getting .pngs from UX I'm not sure if it's a time thing to pull it out or if there's something about it. We can bring it up.
[15:07] <hatch> alright thanks - yeah because that's 3 http requests right there which could be one icon font and some css
[15:08] <hatch> I'll approve it but just make a note please :)
[15:09] <rick_h_> hatch: will add a discussion card to our board
[15:09] <hatch> (Y)
[15:11] <hatch> oh look at that CI broke
[15:22] <bac> benji: reviewed your branch.
[15:22] <benji> bac: the go-juju one?
[15:22] <hatch> oh hmm, doesn't look like I can actually do destroy_service until remove_relation is done
[15:22] <bac> benji: yep
[15:23] <benji> bac: is your review "binding" (i.e., can I count it as my second review?  please say yes, please say yes...)
[15:23] <bac> guihelp: i had a pre-existing committment at noon today before we changed our meeting time.  i'm going to have to miss the meeting today.
[15:23] <hatch> :'(
[15:24] <bac> benji: sure.  i'll be happy to LGTM it when fixed
[15:24] <Makyo> bac, alright.  Anything about your current work we ought to know?
[15:24] <bac> Makyo: it is stellar
[15:24] <frankban> :-)
[15:24] <Makyo> \o/
[15:24] <benji> bac: what I mean is, are we appoved as full reviewers for go-juju?
[15:24] <bac> Makyo: branch landed.  doing misc stuff right now (lp2kanban, reviews, etc) before picking up another item after lunch
[15:24] <bac> benji: yes, that is my understanding
[15:25] <Makyo> bac, sounds good.
[15:25] <benji> excellent
[15:25] <bac> Makyo: i'm open to suggestions on what to do next if the crowd has ideas
[15:25] <bac> benji: the times i've prefaced reviews with "i'm not an official reviewer" the juju-core guys pushed back and said "you're good enough"
[15:25] <hatch> bcsaller: are you in yet?
[15:26] <benji> k
[15:26] <bac> benji: why the lack of tests on that branch?
[15:27] <benji> bac: I'm confused.  It has tests, not many, but it doesn't do much and it follows the same pattern as the other branches that do similar things.
[15:27] <bcsaller> hatch: yes, mostly
[15:28] <bac> benji: did i miss something?  i just saw the one api_test
[15:28] <bac> i may have missed it due to multiple revisions on the rietveld
[15:28] <hatch> bcsaller: ok I THINK the order I need to do things are... add_relation > remove_relation > destroy_service
[15:28] <hatch> because you can't destroy a service unless it has no relations
[15:28] <hatch> and you need to be able to remove the relations if it has some
[15:28] <hatch> but you can't remove any if you haven't added any
[15:29] <hatch> yay TDD
[15:29] <hatch> :D
[15:29] <benji> bac: yep, that's probably all there is; for better or worse that is what has been deemed acceptable.
[15:29] <hatch> bcsaller: so what I"m asking is if that order of events makes sense to you
[15:29] <bac> benji: ok.  i expecte to see something in statecmd.  but, as you say, it doesn't do much.
[15:30] <bac> "expecte" -- it's like i'm speaking french now
[15:31] <Makyo> expecté
[15:31] <bcsaller> hatch: that makes sense to me. 
[15:31] <hatch> word
[15:31] <hatch> these look like large tasks
[15:32] <bcsaller> hatch: they kind of are, my stuff turned out to be bigger than I thought. W/o relying on the validation juju does (for improv) there is quite a bit to check on any mutation
[15:33] <bcsaller> hatch: I need to finish the ones I'm doing but I'm open to pairing on it later if you want that 
[15:33] <hatch> well last night I was dabbling in some C# so I'm glad to be back in javascript...:)
[15:34] <hatch> c# has 4 different 'length' methods depending what type of array you have....cuz that makes sense
[15:35] <hatch> :P
[15:38] <hatch> although the most irritating is the fact that methods AND classes have an uppercase first letter so you have no idea what can be instantiated by looking at the name
[15:54] <benji> bac: I have fixed the errors you pointed out and re-proposed the branch. (https://codereview.appspot.com/8366043)
[15:54] <frankban> guihelp: the javascript console (trunk) shows this error when double clicking a service: http://pastebin.ubuntu.com/5677068/
[15:55] <hatch> that looks like an error caused by bac's changes
[15:55] <bcsaller> indeed
[15:55] <hatch> bac are you still around?
[15:56] <teknico> oh dear gjslint, why do you explode rather than telling what it is that you actually don't like?
[15:56] <hatch> frankban: maybe create a ticket and assign to bac so he can fix when he returns?
[15:56] <teknico> it's not good for your health, you know
[15:57] <frankban> hatch: will do
[15:57] <hatch> jujugui guichat in 2
[16:01] <Makyo> bcsaller, rick_h_, luca____  ping
[16:10] <teknico> https://codereview.appspot.com/8345046
[16:14] <hatch> teknico: I'll take one
[16:14] <teknico> hatch, thanks!
[16:18] <hatch> done
[16:21] <teknico> hatch, thanks! (remember to tag yourself on the card, actually *before* you make a review :-) )
[16:21] <teknico> speaking of which: benji, did you say you already got two reviews for your branch? I see no tags on its card
[16:22] <hatch> tagged
[16:22] <teknico> (playing card tag police here :-) )
[16:22] <teknico> hatch, thanks again :-)
[16:23] <benji> teknico: only one of the reviewers is on the gui team, the juju-core guys don't use that technique.
[16:23] <benji> my self-imposed rule is that only reviews for projects completely "inside" the gui team use tags to claim reviews
[16:24] <teknico> benji, but bac said that we can be authoritative reviewers on juju-core too, so why not?
[16:24] <teknico> I mean, we could add tags for reviews from the juju-core team in their place
[16:24] <benji> if we can get them to participate, then it would be great; partial participation seems worse than non-participation though
[16:25] <benji> we could do that
[16:27] <teknico> Makyo, thank you too (I added your tag :-) ), landing!
[16:27] <Makyo> teknico, good catch, thanks
[16:51] <hatch> that moment when you realize you just deleted the wrong folder...
[16:53] <teknico> yeah, that one :-)
[17:13] <hatch> in python `for pair in endpoint_pairs[1:]:`  what does the : inside the [] mean?
[17:19] <benji> hatch: that : makes it a slice, so [1, 2, 3, 4][1:] == [2, 3, 4]
[17:19] <bac> oy
[17:19] <hatch> ahh ok
[17:19] <hatch> thanks
[17:19] <benji> the first index goes before and a second index goes after, if the first is left off it means 0, if the last is left off it means -1 (last)
[17:20] <hatch> bac: https://bugs.launchpad.net/juju-gui/+bug/1164589
[17:20] <_mup_> Bug #1164589: addServiceToEndpointsMap error <juju-gui:Triaged> < https://launchpad.net/bugs/1164589 >
[17:20]  * bac looking
[17:24] <hatch> bac: just updated with a new comment on that ticket
[17:27] <hatch> bac: that error is actually blocking me so I can help if needed
[17:27] <bac> hatch: first one was easy.  looking into the other
[17:28] <hatch> oh ok excellent - be sure to now write a test to cover that error :)
[17:32] <bac> hatch: yes dear
[17:32] <hatch> lol
[17:32] <bac> hatch: after the fix for the first i cannot replicate the add relation issue
[17:32] <hatch> egggggggcelent
[17:34] <hatch> is there a special procedure for staff purchases from shop.canonical.com?
[18:11] <BradCrittenden> hatch: re: purchases - no.  if they are still doing the discount code, you should've gotten it when joining.
[18:18] <bac> hatch: proposing fix now
[18:21] <hatch> kewl
[18:21] <hatch> thanks
[18:26] <hatch> hehe fix-goof
[18:34] <hatch> bac: a 4 character fix? hehe
[18:34] <BradCrittenden> i think it is eight.  i had to delete 'null' before adding 'this'
[18:35] <hatch> oh lol - charmStore needs to be destroyed no?
[18:35] <hatch> in your test
[18:38] <hatch> no codereview url has come by so that's why I mentioned in here :)
[18:39] <bac> https://codereview.appspot.com/8364044
[18:39] <bac> hatch: could you qa this branch to see if you can cause the add relation failure?
[18:41] <hatch> yep checking it out now
[18:42] <rick_h_> jcsackett: hatch if you guys get a few min please? https://codereview.appspot.com/8356044 it's a step one so you can qa it that it works, but it's fugly and only works via direct url calls (can't click into the view)
[18:43] <bac> benji, rick_h_ : could one of you do a quick review on https://codereview.appspot.com/8364044
[18:43] <rick_h_> bac: sure thing, loading up
[18:43] <bac> thx
[18:43] <hatch> bac, QA'd and OK
[18:43] <benji> missed it
[18:43] <bac> thanks hatch
[18:45] <hatch> rick_h_: I still don't see a position absolute in this branch :P
[18:45] <rick_h_> hatch: nope :)
[18:45] <rick_h_> hatch: honestly, last thing we'll do. This way we know any bugs are our own and not interactions
[18:45] <rick_h_> well, maybe not last...
[18:46] <benji> bac: if you get a second, I could use a +1 on the review from earlier
[18:48] <bac> benji: done
[18:48] <rick_h_> bac done
[18:49] <hatch> rick_h_: so no more issues with the routing code?
[18:49] <bac> thanks rick_h_
[18:49] <rick_h_> hatch: :/ only issue is the double/triple call which I'm ignoring for now
[18:49] <rick_h_> hatch: goal is to try to get the basics setup for huw to go through and be able to apply UX love to things
[18:49] <hatch> oh yeah but that was an issue long before the routing stuff
[18:49] <rick_h_> hatch: ah, well I wasn't really involved before so meh
[18:50] <hatch> neither was I :P
[18:50] <rick_h_> hatch: I do forsee one issue I need to work through, but haven't looked awt the problem much yet
[18:50] <rick_h_> I really wish I had a way to generate urls in handlebars based on something with some brains on current state
[18:50] <rick_h_> because if I do the url routing in my views by catching click events I don't get dispatch
[18:51] <rick_h_> but in the templates there's no reall app state to say "oh, you're in /fullscreen so all links should stay in /fullscreen land
[18:57] <hatch> rick_h_: create a helper which references the generator in the router code
[18:57] <hatch> I generate urls that way in the service views
[18:57] <rick_h_> hatch: cool, will look there then. 
[18:57] <hatch> but instead of using a helper I do it before passing it in
[18:58] <rick_h_> oh cool, yea dirty thing would be for the master view to set an magic ATTR that's 'whoami' or something but it's nasty/dirty
[18:58] <hatch> serviceRemoteUri: this.get('nsRouter').url({ gui: '/service/'})
[18:58] <hatch> for example
[18:58] <hatch> so that says, change the url for the gui namespace to /service/
[18:59] <hatch> well....build me a url with the gui namespace with /service/
[19:00] <rick_h_> hmm, yea the big thing will be the CharmToken widget, when clicked on, will need to open /bws/XXXX/precise/charmid to load the details
[19:01] <rick_h_> in sidebar, that's this expanded sidebar version, in fullscreen, it's the fullscreen details view
[19:01] <rick_h_> where sidebar/fullscreen is XXXXX
[19:01] <rick_h_> so need to get something into the CharmToken Widget to be smart about generating that url/click
[19:01] <hatch> yup
[19:06] <rick_h_> thanks bac 
[19:10] <rick_h_> bac: so in testnig it out YUIDoc doesn't care about the lack of return. The methods don't return anything and rather than add more noise with the whole mutates only mess I just leave it out. 
[19:10] <rick_h_> at least make code-doc and make view-code-doc don't complain
[19:10] <bac> rick_h_: that is great news and should be shouted from some mountain top or roof
[19:15]  * hatch is back on track
[19:15] <hatch> thanks for the patch bac
[19:20] <hatch> bcsaller: have a second to explain to me how relationships work from the higher level? I see the code but I'm wondering how they function inside each charm....or if this is documented somewhere I could read that instead :)
[19:21] <bcsaller> hatch, one min
[19:24] <hatch> sure
[19:24] <bcsaller> hatch: in hangout
[19:44] <bac> statik signed on at Mar 10, 2013 20:37:57 and has been idle for 594hr 59min 51s
[19:44] <bac> i guess i'll try email
[19:47] <hatch> lol
[19:50] <hatch> bcsaller: so that I am sure I get this right
[19:50] <hatch> relationships are valid if
[19:50] <hatch> they are the same type...
[19:50] <hatch> one is client, one is server
[19:50] <hatch> both are 'peer'
[19:52] <hatch> I'm not sure how peer to peer differs from 'both same type' but they are checked for separately
[19:52] <bcsaller> hatch: at a high level yes, there is also a notion of subordinate scoped relations which have the same basic rules but generally use an implicitly provided relation, 'juju-info'
[19:53] <bcsaller> hatch: with client-server, one is client, the other is server (roles) and they have the same interface type
[19:53] <bcsaller> hatch: with peer they are peers, they all have the same role
[19:53] <hatch> ahh ok
[19:54] <bcsaller> hatch: the special behavior around peer relations is that they are automatically joined on deploy
[19:55] <bcsaller> hatch: there is no explicit step needed because they are 'related to self'
[19:55] <bcsaller> hatch: you can see that at the bottom of juju/control/deploy.py
[19:56] <bcsaller> (which I don't know if we implement in our version)
[19:56] <hatch> doesn't look like it
[19:56] <bcsaller> nope
[19:56] <bac> hatch: did you do anything to fix jenkins or was it not a real failure?
[19:57]  * bac trying to get all set up with vpn, etc
[19:57] <hatch> there was a lot of work done to do all this in python to throw it all away and redo in go...
[19:57] <rick_h_> bac: I think my land came alnog after yours and forced a re-run?
[19:57] <hatch> bac: I just left it, I'll do it towards the EOD
[19:57] <rick_h_> bac: but guessing as I thuoght the failure on yours was mine
[19:57] <hatch> rick_h_: no it complets and then does it again, it doesn't stop
[19:58] <rick_h_> see, what do I know about how it's setup? nadda :)
[19:58] <bac> hatch: so we assume the failure was spurious/canonistack
[19:58] <bcsaller> hatch: we really need to fix our use-cases for this thing, we don't want to build all the juju behavior in JS I think, just get the env running
[19:58] <hatch> bac: I'm going to yes - there is no reason any of our changes have caused that failure
[19:59] <bcsaller> but it still takes alot to get just as far as we need
[19:59] <hatch> bcsaller: yeah - how I understood it is that we want it to 'look' like it's working as expected
[20:00] <hatch> so I'm sure we can forego some of the more complex checks
[20:00] <hatch> but I am pretty sure we want to check to make sure the relation stuff works properly
[20:01] <bcsaller> hatch: yeah, its one of the main things we draw
[20:10] <hatch> bcsaller: mind taking a look in topology/relation.js and let me know if I am seeing this wrong...It looks like we only support server and client connections in the GUI? 625-631 and 659-665
[20:19] <bcsaller> hatch: peer relations are not ambiguous which is what that method is checking
[20:20] <bcsaller> hatch: we dont' draw peer relations though as they would look like an arrow pointing back to self or a ring or something.
[20:26] <hatch> well sure but that's the only method which actually calls add_relation
[20:26] <hatch> so right now the gui doesn't actually check the charm to see if it's a server or client
[20:27] <hatch> it just says "you're a client, and you're a server"
[20:27] <bac> hatch: i'm trying to setup my vpn to the qa lab.  you know the drill, right?
[20:28] <hatch> bac: umm mine was a little different because I'm using 12.10
[20:28] <hatch> so I coudln't follow the guide
[20:28] <bac> hatch: that's what i'm using
[20:28] <hatch> oh ok, lemme boot up my laptop
[20:29] <bac> hatch: well, real, quick, once you have network-manager set up, how do you get it to open the vpn connection?
[20:29] <hatch> click the network symbol in the top right
[20:29] <bac> if i double-click on it, then it just opens the edit configuration dialog
[20:30] <bac> top right of what?
[20:30] <hatch> nope single click on the thing that looks like a cell phone signal strength (with my icon set) then go down to 'VPN Connections'
[20:30] <hatch> in the very top right of the screen
[20:30] <bac> ok, i was trying w/in the nm
[20:30] <hatch> then that will open up another menu that has whatever you called the vpn connection
[20:31] <hatch> do you see it?
[20:32] <hatch> honestly my configuration is so messed up I don't think I'll ever be able to upgrade to 13.04 without something exploding :D
[20:32] <hatch> this was also installed with wubi 3 years ago and without wubi in 13.04 I'm not sure I'll actually be able to upgrade anyways
[20:33] <bac> hatch: cool, i'm in
[20:35] <hatch> right on
[20:35] <hatch> plz don't delete our jenkins configuration :)
[20:45] <hatch> LG Optimus G at my cell provider is $0 on a 3 year contract....or $499 on a two year...lol
[20:49] <hatch> bcsaller: I need the mysql equiv to test/data/wordpress-charmdata.json any idea how I would generate that?
[20:51] <bcsaller> hatch: http://jujucharms.com/charms/precise/mysql has everything
[20:52] <bcsaller> hatch: under the repo link you can find the interfaces in metadata.yaml (same as for any charm) but they are also spelled out on the website
[20:53] <hatch> ok so that json file was manually created?
[20:57] <hatch> must be, I can't find any file which has all of this information in it
[20:58] <rick_h_> hatch: what file are you looking for?
[20:58] <hatch> well I need to deploy mysql along side wordpress in the in memory environment tests
[20:58] <hatch> so I am guessing I need the mysql version of test/data/wordpress-charmdata.json
[20:59] <rick_h_> k, let me look what api endpoint that is on charmworld
[21:00] <rick_h_> hatch: http://jujucharms.com/charms/precise/mysql/json
[21:00] <hatch> oh lol it was that easy eh
[21:00] <hatch> :)
[21:01] <rick_h_> hatch: and that's called from the model.load() using the 'charmstore' store
[21:11] <hatch> kewl
[21:12] <hatch> pro...gress
[22:12] <hatch> bcsaller: reviewing
[22:12] <bcsaller> hatch: thanks :)
[22:40] <hatch> review done