/srv/irclogs.ubuntu.com/2017/02/23/#juju.txt

=== hbaum_ is now known as hbaum
sur_anrah:06:17
sur_are you there06:17
sur_sur:06:18
sur_sur_:06:18
=== frankban|afk is now known as frankban
anrahnow i am08:34
kjackalGood morning Juju world!08:44
Zichi here, if I want to remove on of my kubernetes-worker in a CDK bundle, do I simply need to remove that machine from Juju and charms will do the proper cleanup expected?09:04
brymmorning all11:26
magicaltroutlazyPower: lmk when you're in your seat12:16
Zic-> to answer myself, yeah, the kubernetes-worker charms manage remove-unit well, I did a test on my test cluster12:45
Zicit was cleanly remove from Kubernetes before removing it from Juju12:45
=== gaughen_ is now known as gaughen
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
joedborghello all.  does anyone know if there's a juju command to monitor which set_states are being called in real time?16:37
=== mup_ is now known as mup
=== mup_ is now known as mup
kwmonroejoedborg: this isn't what you asked for, but in case it's helpful, i use this to monitor states on a given unit:  juju run --unit foo/0 'charms.reactive get_states'16:59
kwmonroethat's not real-time, but it's useful to know what states are set to debug why a handler is (or isn't) firing.17:00
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
=== mup_ is now known as mup
joedborg@kwmonroe thanks17:14
joedborg@kwmonroe although everything seems to come back as None value, is this normal?17:14
kwmonroejoedborg: yeah, i don't think state keys have 'values' per se.  cory_fu might have more enlightening things to say about the normalcy of "state: null", but fwiw, here's an example of the states set on a hadoop slave:  http://paste.ubuntu.com/24054153/17:18
kwmonroe^^ and that's normal17:18
cory_fuRight, the only states that would have values are relation states.  That helper should really just be returning the keys17:19
=== frankban is now known as frankban|afk
cory_fukwmonroe, petevg: Travis passing: https://github.com/juju-solutions/layer-cwr/pull/9418:17
kwmonroecrap, i guess i have to merge stuff now18:17
kwmonroemerged cory_fu.. don't worry about releasing cwr-52 to stable, i'll cut a new one that picks this up.18:20
kwmonroehahah cory_fu, you just conflicted kjackal (https://github.com/juju-solutions/layer-cwr/pull/93).  payback, eh?18:22
cory_fu:)18:23
joedborg@corey_fu @kwmonroe: ah, so these all are one that have been fired?18:23
joedborg@cory_fu ^^18:24
kwmonroejoedborg: 'charms.reactive get_states' will show you all the states that have been set.  that doesn't necessarily mean any handler has fired, only that it could if it's written to react to those states.18:26
joedborg@kwmonroe ah okay, i'm trying to see which ones have been fired to debug an issue18:27
admcleod_joedborg: i find this useful: jgs() { juju run --unit $1 "charms.reactive --format=yaml get_states"; }18:27
stormmoreo/ juju world18:28
redir\o stormmore18:51
stormmoreare we having fun today?19:03
kwmonroejoedborg: i don't think there's a history of handlers that have fired outside of "juju debug-log -i unit-foo-0 --replay" and fancy grepping...19:04
kwmonroestill, if you see a state has been set, it's pretty safe to assume any handler reacting to that state has fired.19:05
joedborg@kwmonroe thanks19:07
kwmonroenp joedborg - if you need any help debugging, just holler... i'm happy to dig through debug-log output with you.  well, maybe not happy, but i'll do it :)19:08
joedborgkwmonroe: thanks man, I'll probably take you up on that offer :)19:28
kwmonroecory_fu: did we have a rationale for making hadoop-client single-series?  https://jujucharms.com/hadoop-client/.  i think we didn't want to mess with the trusty version (perhaps back when the java interface was added?) but i need to rebuild it and am curious if we should just make it multi.19:31
cory_fukwmonroe: I really don't recall19:34
=== lamont` is now known as lamont
tvansteenburghlorenzotomasini: https://github.com/juju/python-libjuju/pull/5619:52
tvansteenburghlorenzotomasini: that addresses the issues we talked about last week. trying to get some tests in there before merging, but hoping to release those changes soon19:53
rick_htvansteenburgh: ping21:04
tvansteenburghrick_h: pong21:04
rick_htvansteenburgh: back from a break and poking at this adding of list models method21:04
rick_htvansteenburgh: is there some pattern established for turning a Model object from the _client into a Model object from model.py?21:05
rick_htvansteenburgh: I feel like I should get the facade bits back and build a proper Model object out of it somehow but not seeing anything atm21:05
tvansteenburghrick_h: got any code i can look at? i don't entirely follow21:07
rick_htvansteenburgh: https://pastebin.canonical.com/180574/ is what I've got in my head/current code21:10
rick_htvansteenburgh: basically I'm looking that I shouldn't expose the end user of the controller/model code to the internal object types used in _client.py21:11
rick_htvansteenburgh: so I'm wondering if there's any pattern for transforming one into the other21:11
tvansteenburghrick_h: so you'll want to make new Model() and then call connect(...) on them21:15
rick_htvansteenburgh: right, but list_models should return what, in your mind?21:15
rick_htvansteenburgh: in the spirit of the library atm21:15
tvansteenburghimo it should just return strings21:16
rick_htvansteenburgh: of what? uuids? names?21:16
tvansteenburghlist of model names21:16
tvansteenburghor uuids21:16
bdxis remote lxd provider a thing now?22:42

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!