[00:15] <kwmonroe> bolthole: blahdeblah is correct, you can't rely on order of any hook execution.. so the hooks must handle the potential for nothing being returned by relation-get
[00:16] <blahdeblah> thanks for confirming, kwmonroe
[00:16] <kwmonroe> in your case, it would probably be easiest to wire in your webapp using webapp-container-relation-changed
[00:16] <kwmonroe> you are guaranteed that relation-changed *will* fire anytime data on the relation changes
[00:16] <kwmonroe> (vs relation-joined)
[00:18] <kwmonroe> so, a webapp-container-relation-changed hook for you might look like "FOO=`relation-get webapp-path`; if [ ! -z $FOO ]; then wget the webapp and move it to $FOO; else do nothing and wait for the next time relation-changed runs.
[00:18] <kwmonroe> eventually, relation-get webapp-path will return data (once tomcat sends it), and your -changed hook will get it.
[00:20] <bolthole> thanks. I kinda empirically found out that gets fired when I want it to. Nice to know that it's guarranteed that way.
[00:21] <bolthole> now that I think about it some more though...
[00:22] <bolthole> I trhink that mbruzek is approaching the information exchange the wrong way.
[00:22] <bolthole> he is using the relationship to share the tomcat webapp directory
[00:23] <bolthole> but... when and ifjuju ever gets to the point whre subordinate services can be removed....
[00:23] <bolthole> I'm thinking that the relationship may be severed, before the service gets told to 'stop' itself.
[00:23] <bolthole> But at that point, it has just lost the information on where to cleanup itself. becuase that information was in the relatoinship, which doesnt exist
[00:24] <kwmonroe> you can remove subordinate services today in juju.  relation-departed will fire, which is where you should remove any data that you don't want left on the principal unit.
[00:24] <bolthole> huh. so relatoin-departed is inappropriately named? it should be called "relation-deparTING"?  ;-)
[00:25] <kwmonroe> meh, i guess.  -departed means the relationship is tearing down but you can still access relation data (like webapp-path).  -broken means the relation is gone.
[00:38] <bolthole> WOOO! I got it to work!
[00:44] <kwmonroe> nice bolthole!
[00:48] <bolthole> kwmonroe could you please aprove my one-char-syntax-error fix to the tomcat charm?
[00:49] <bolthole> i submitteed it this morning. it was ignored, and someon else worked on the charm so there were conflicting lines.
[00:49] <bolthole> i just redid it for no conflicts. please push it through before more conflicts happen?
[00:50] <bolthole> the webapp-path value is completely unusable without the fix.
[00:52] <kwmonroe> sure bolthole - let me take a look
[00:53] <kwmonroe> bolthole: i only see this from 18 hours ago.  did you see another commit to trusty/tomcat that made this merge conflict?
[00:53] <kwmonroe> https://code.launchpad.net/~bolthole/charms/trusty/tomcat/trunk/+merge/284213
[00:57] <bolthole> yeah just 60 seconds beofre i wrote that :)
[00:57] <bolthole> https://code.launchpad.net/~bolthole/charms/precise/tomcat/trunk/+merge/284373
[00:58] <bolthole> on wiat, its precise
[00:58] <bolthole> not trusty. yet.
[00:59] <bolthole> so i guess thre's no conflict for the trusty one, and hyou could just approve that one too ;)
[01:31] <bolthole> Thanks
[01:33] <kwmonroe> bolthole: you talking to me?  if so, yw :)
[01:34] <bolthole> :)   So.. how does the charm version in the store, get derived from the backend code baes?
[01:34] <bolthole> one is at 15, the other is at 3 or something?
[01:35] <kwmonroe> yeah bolthole - there's no correlation.  at least not one that i can figure out.
[01:36] <kwmonroe> i mean, i guess you could have 10 commits to LP, push to store making charm rev 1, then 4 more commits to LP, push to make charm rev 2, then 1 more LP commit, push to make charm rev3.
[01:36] <kwmonroe> i but i don't know how you could look at an LP commit number and figure out the charm revno.
[01:37] <bolthole> okay, so it isnt automatic; you have to make some kind of explicit push each time
[01:37] <kwmonroe> that's correct
[01:39] <kwmonroe> well, no, that's not correct.  i don't know how it works.  the numbers just go up ;)
[01:39] <bolthole> dohhh
[01:40] <kwmonroe> oh oh oh -- maybe it is how it works.. each commit bumps the LP revision, but only a push triggers the ingestion into the store.
[01:40] <kwmonroe> and now i have thought too much about this.  thanks.
[08:06] <icey> does juju on openstack support the storage hooks?
[09:26] <jamespage> gnuoy, quick review pls - https://code.launchpad.net/~james-page/charm-helpers/lp1537155/+merge/284411
[09:34] <bloodearnest> marcoc|airplane, the subordinate thing is a red herring, I would just like to be able to discover the units running on the this machine, in the same way I can find out the hostname of the machine
[09:34] <bloodearnest> to avoid having to explicitly configuring that info in every charm
[09:40] <bloodearnest> the context here is *not* charm code. It's a library that is used by our apps to standardise/improve their log outout
[09:41] <bloodearnest> we currently tag each log line with the hostname of the machine, which is easy to discover. But the hostname is kinda useless in a juju world, we are more interested in the juju unit that the app runs under
[09:41] <bloodearnest> so I was wondering if there's away to discover the juju units running automatically
[09:42] <bloodearnest> or else, every charm for each service that uses this library (10+) would need to be manually updated to set an env var or similar with the unit name
[13:16] <deanman> Hi, I'm trying to learn more about Juju by using the official vagrant boxes and they fail to properly boot up both on windows and MacOSX. I've tried trusty64 trusty32 and wily 64. All of them are stuck at "Intalling package: cloud-utils"
[13:46] <stokachu> kadams54: with theblues library how can i pull a specific revision? for example, bundle = cs.bundle('data-analytics-with-sql-like/5')
[13:48] <stokachu> specifically for a bundle
[13:58] <rick_h_> stokachu: yes, https://api.jujucharms.com/charmstore/v4/openstack-base-34/archive/bundle.yaml vs https://api.jujucharms.com/charmstore/v4/openstack-base-39/archive/bundle.yaml
[13:58] <rick_h_> stokachu: the thing is that a new revision might be due to a readme update or the like
[13:58] <rick_h_> stokachu: so not all reivsions will be changes to the bundle.yaml file itself
[13:58] <stokachu> ah ok
[13:59] <rick_h_> I was confused because that openstack 38 and 39 revisions the files were the same
[13:59] <rick_h_> but the readme was different
[14:04] <stokachu> so i can generate the archive url with cs.archive_url('data-analytics-with-sql-like-4') but that doesn't contact the charmstore to validate it
[14:05] <rick_h_> stokachu: not sure on the library itself
[14:05] <stokachu> i guess i could just generate the api url and check that a 200 is returned
[14:06] <rick_h_> stokachu: yea, have to bug jcsackett or some other folks that work on that atm
[14:06] <stokachu> rick_h_: ok cool, will do thanks
[16:47] <tych0> marcoc|airplane: https://github.com/lxc/lxd/issues/1477
[16:47] <stokachu> how do you force a destroy-controller with juju 2.0?
[16:48] <stokachu> i interrupted a lxd bootstrap and now juju is unable to cleanup after itself
[16:48] <tych0> marcoceppi: er, https://github.com/juju/juju/pull/4191
[16:48] <tych0> i am bad at copying and pasting
[16:58] <marcoceppi> tych0: aren't we all
[17:05] <cmagina> tvansteenburgh: hey, did you get a chance reproduce that bundletester issue i've been hitting?
[17:07] <tvansteenburgh> cmagina: i was unable to repro. would you mind filing a bug here https://github.com/juju-solutions/bundletester/issues
[17:07] <cmagina> tvansteenburgh: will do, thanks for trying
[17:07] <tvansteenburgh> please include traceback
[17:08] <tvansteenburgh> i will have another look soon
[20:28] <adam_g> does juju / local provider log output of uvtool errors?
[21:59] <lazypower|travel> adam_g I don't believe so
[21:59] <lazypower|travel> But i'm not 100% on that.
[22:49] <bolthole> scalability question: what if we have a 'cloud' where we anticipate 200-300 services? how can we use juju for that and keep it manageable?
[23:03] <rick_h_> bolthole: we'd suggest a controller with multiple models in HA mode
[23:03] <rick_h_> bolthole: the controller multiple model work is in the 2
[23:03] <rick_h_> p alpha work
[23:03] <rick_h_> bah 2.0
[23:24] <bolthole> rick_h_ sounds like you are describing more scalability. however, I am actually trying to focus on manageability
[23:25] <rick_h_> bolthole: i'm talking about moving those 200 services into 20 more tightly scoped models
[23:25] <rick_h_> so you're managing things in smaller groups
[23:25] <bolthole> ah, good
[23:26] <bolthole> demo or screenshots?
[23:26] <rick_h_> bolthole: https://jujucharms.com/docs/devel/wip-systems
[23:27]  * rick_h_ looks for youtube talk
[23:27] <rick_h_> https://youtu.be/-1aVgnJIwLk
[23:28] <rick_h_> bolthole: shows the old gui visualizing it
[23:28] <rick_h_> bolthole: don't have one with the new gui atm
[23:28] <bolthole> ah
[23:28] <bolthole> thanks for the video
[23:31] <bolthole> cant use sound at the moment....  is "model" the thing tothe right of juju/admin ?
[23:31] <bolthole> so,
[23:31] <bolthole> juju/admin/openstack
[23:31] <bolthole> "openstack" is a model view?
[23:35] <rick_h_> bolthole: yea the model name is sonething you give whwb you create it
[23:36] <rick_h_> you'll see different names as the video goes on
[23:36] <bolthole> "it"
[23:38] <bolthole> you said that was with the "old" gui... but I dont see that option with the trusty/juju-gui screen?
[23:38] <rick_h_> bolthole: it was a demo
[23:39] <rick_h_> bolthole: today you use the jes festure flag in that doc link
[23:39] <rick_h_> bolthole: and use the gui 2.0 deployed into the admin model
[23:39] <bolthole> oh. um.. waitaminute though...
[23:41] <bolthole> the feature flag you are referring to, is   for "multiple environments"?
[23:41] <rick_h_> bolthole: yes
[23:41] <bolthole> models == enviroments? or someting else?
[23:42] <rick_h_> bolthole: where we're doing s/environments/models in 2.0
[23:42] <bolthole> ugh. naming overload:(
[23:42] <bolthole> but.. I dont want to set up a separate juju .. controller(?) for every model wehave
[23:42] <bolthole> that seems rather wasteful
[23:42] <rick_h_> no one controller many models
[23:43] <bolthole> huh
[23:43] <rick_h_> once your bootstrapped you can creat more and more models
[23:43] <rick_h_> try it out in that doc link
[23:43] <bolthole> so whats the new name for what is now called environments? :-D taht is to say "my azure environment" vs "my amazon environment" ?
[23:44] <rick_h_> my azure controller
[23:44] <rick_h_> and in 2.0 you give them names and can have multiple azurr controllers
[23:44] <rick_h_> so cloud-controllers-models
[23:44] <bolthole> ah, k.  thanks.  Rough ETA for release of this thing?
[23:45] <rick_h_> 16.04
[23:45] <rick_h_> april release
[23:45] <bolthole> thanks
[23:45] <rick_h_> i'm showing some of it at the summit next wed
[23:45] <rick_h_> the charmers summit