[00:20] <babbageclunk> thumper: review my race fix plz? https://github.com/juju/juju/pull/8698
[00:47] <babbageclunk> or wallyworld? ^
[00:47] <babbageclunk> oh, and this one too https://github.com/juju/juju/pull/8688
[02:06]  * thumper looks
[02:10] <thumper> babbageclunk: first one done
[02:10] <babbageclunk> ta
[02:11] <thumper> babbageclunk: other done
[02:11] <babbageclunk> awesome, fanks thumper
[02:12] <thumper> np
[02:14] <thumper> wallyworld: up for a chat about the review any time
[02:15] <babbageclunk> thumper: I thought the unsubscribe would be enough too, but it wasn't.
[02:15] <thumper> um...
[02:15] <thumper> I beg to differ
[02:15] <thumper> chat?
[02:17] <babbageclunk> I mean, feel free to try it - I put the unsubscribe in first, and it didn't fix the race.
[02:18] <babbageclunk> thumper: The other option that worked was to put a mutex into the suite and lock around both s.reqs = make(chan) and the send in the callback.
[02:18] <babbageclunk> But the local variable seemed cleaner.
[02:19] <babbageclunk> thumper: in 1:1?
[02:19] <thumper> coming
[02:29] <wallyworld> thumper: just got back from meeting witn anastasia, ping when you are free
[02:29] <thumper> wallyworld: ack
[02:38] <thumper> wallyworld: now?
[02:38] <wallyworld> sure
[02:41] <wallyworld> thumper: am in HO when you are ready
[03:42] <babbageclunk> wallyworld or thumper, another one to take a look at? https://github.com/juju/juju/pull/8699
[03:43]  * thumper looks
[04:05] <babbageclunk> thumper: thanks for the glowing review!
[04:05] <thumper> :)
[04:13] <thumper> jam: has anyone looked at the network PR yet?
[04:14] <thumper> jam: wow... not a small change then
[04:16] <jam> thumper: yeah. Manadart looked at some of it already
[04:16] <jam> thumper: most of that is lots more tests
[04:18] <thumper> jam: I guess it looks good to me, although I'm not sure if I'm a good judge or not
[04:19] <thumper> jam: re: https://github.com/juju/juju/pull/8687 - like your comment on whether or not we should have different params structs for v5 and latest
[04:19] <thumper> or just add new field to params
[04:24] <jam> thumper: thanks for the approval. Ultimately it needs to be tested, and I can at least test the VLAN stuff directly, and I think someone just gave me a bonded machine to test that part on.
[04:24] <thumper> sweet
[04:25] <thumper> hmmm... wondering why our windows reboot tests are trying to initialize a lxd container manager
[04:25] <thumper> that seems dumb
[04:48] <jam> thumper: I think new types are better. It means generating automated descriptions of API preserves the shape of old APIs
[04:48]  * thumper nods
[04:54] <wallyworld> thumper: i would like a second opinion on the use of a bulk remove vs creating a slice of individual removes using removeInCollectionOps() in https://github.com/juju/juju/pull/8700
[04:54] <wallyworld> to remove the credentials for a deleted cloud
[05:22] <thumper> fuck fuck fuckity fuck
[05:22]  * thumper loses the will to keep going today
[05:22] <thumper> will attack tomorrow with gusto...
[05:23] <thumper> laters peeps
[08:18] <manadart> externalreality: Want to cast an eye over this one for me? https://github.com/juju/juju/pull/8703
[08:19] <manadart> Not here. jam ^. Will get on to yours next.
[08:20] <jam> manadart: not here?
[08:20] <manadart> Eric.
[08:48] <manadart> jam: Approved #8697. Looks like nothing new on OCI. I assume we're taking a pass again...
[08:49] <jam> yeah
[09:38] <manadart> jam: OK if I forward port https://github.com/juju/juju/pull/8690 ?
[09:39] <jam> manadart: any reason to not just merge 2.3 into develop?
[09:40] <manadart> jam: Suppose not. I'll give it a lash.
[09:55] <manadart> https://github.com/juju/juju/pull/8704
[12:12] <bobeo> o/
[12:21] <eriklonroth> Does anyone know of a charm/layer for tensorRT ?
[12:28] <bobeo> how do I show the results of an action run with the run-action command? is that juju show run-action by chance?
[12:29] <bobeo> figured it out.
[12:30] <bobeo> my next question, if an action completes successfully, it updates the config file correct?
[12:40] <bobeo> just to clarify, I send all my log files to filebeats in logstash on its port to import logs into ELK correct? kwmonroe
[12:41] <bobeo> ooh, and its working! time to feed it o.o
[14:11] <admcleod_> any update on when we might get 2.3.8 stable?
[14:15] <rick_h_> admcleod_: working on it, the team's successfully gotten a container in bionic on a vlan and tossing the current updates at the full test suite to see what other gaps needs to be fixed up
[14:15] <admcleod_> awesome
[14:15] <admcleod_> thanks
[14:31] <bobeo> am I the only one having severe issues with elasticsearch at the moment?
[14:32] <bobeo> nothing seems to be able to connect to elasticsearch, regardless of what application I deploy and install.
[15:30] <bobeo> rick_h_: so I was looking at a bundle for ELK, andit got me thinking. If i simply take the bundle, and install everything piecemeal, that would allow me to bypass the restriction on deploying bundles with the --to option correct?
[15:31] <rick_h_> bobeo: sure, but the what restriction are you hitting with --to now?
[15:31] <jhobbs> I'm trying to deploy arm64 nodes using an amd64 controller and juju-2.4 beta2
[15:31] <bobeo> rick_h_: --to tells me i cant deploy bundles using the --to option.
[15:31] <jhobbs> I should just need to configure agent-stream=devel on the model right?
[15:32] <rick_h_> bobeo: oh right, I mean a bundle has --to placement stuff in it so putting a bundle on a machine doesn't work out right
[15:32] <rick_h_> bobeo: so yea, you just break it down and run the manual commands you want
[15:32] <bobeo> rick_h_: so when I was previously trying to deploy elk, it was with --to lxd:<machine#>, whch was failing, and when I tried to deploy it as is, its when it broke everything, as in I hit that bug that I found yesterday. So I decided today to open the bundle.yaml to try and better understand bundles.
[15:33] <bobeo> rick_h_: right. so my question is, how do you translate the relations sections of the yaml files to understand what relations are requirements for which charm?
[15:33] <rick_h_> bobeo: sec, otp
[15:45] <kwmonroe> bobeo: can you pastebin the bundle that you're working with?
[16:12] <bobeo> for instance, in the bundle.yaml for ELK, you have this:   - - "openjdk:java"     - "logstash:java"   - - "kibana:rest"     - "elasticsearch:client"   - - "logstash:elasticsearch"     - "elasticsearch:client"
[16:12] <bobeo> kwmonroe: sure! lnk is easier though https://api.jujucharms.com/charmstore/v5/~elasticsearch-charmers/elk-stack/archive/bundle.yaml
[16:13] <bobeo> kwmonroe: as for the above, im assuming the -- and the - mean they are related, so for instance, juju relate openjdk:java logstash:java would be one relational pairing
[16:13] <bobeo> with each set of -- and - being another pair.
[16:14] <kwmonroe> cool bobeo.  you asked how to translate the relation section of the bundle yaml.. for that bundle, you would achieve the same thing with juju from the CLI like this:
[16:14] <kwmonroe> juju relate openjdk:java logstash:java
[16:14] <kwmonroe> juju relate kibana:rest elasticsearch:client
[16:14] <kwmonroe> juju relate logstash:elasticsearch elasticsearch:client
[16:14] <kwmonroe> the -- and - are just the way bundles in the store format that section of yaml
[16:15] <kwmonroe> so the first "-" means here comes a relation, and it's between - openjdk and - logstash.
[16:15] <bobeo> kwmonroe: awesome! yay im learning! it feels good to be able to finally realize im understanding how the yamls interact to build charms.
[16:16] <kwmonroe> :) good to hear!
[16:17] <bobeo> ok so jumping in further, kwmonroe looking at the config files, I have realized alot of things that youd configure in the files arent always there. so my question is as I go into the files to configure them, if I reset the box, will it blow away those required changes that werent in the charm that I had to add later, or will they be rolled back, even though they arent in the charm config file
[16:18] <bobeo> my concern for instance with ELK, I had to go into logstash, kibana, and elastic to make changes that werent included by default with filebeat, kibana, and elastic. While I am still having issues, I hav efewer ones now. If I reset the boxes, I dont want to lose my current configs as I move closer to it working as intended.
[16:20] <bobeo> http://paste.ubuntu.com/p/dPmwsHDvMn/  http://paste.ubuntu.com/p/jbR33H84Pc/  http://paste.ubuntu.com/p/jnCBKcZfPk/   http://paste.ubuntu.com/p/3yJFqx67JY/ for reference, juju status, kibana, logstash, and elasticsearch respectively
[16:21] <bobeo> kwmonroe: I understand that juju manages the file(s) to manage configurations, or deploys by snaps, but additional configurations will sometimes be required.
[16:24] <kwmonroe> bobeo: if you manually ssh to a unit and update, for example, /etc/logstash/logstash.conf, those changes may very well get overwritten by juju on a subsequent hook.
[16:24] <kwmonroe> bobeo: best practice is to let juju handle the config, which may mean updating the charm to expose config that isn't available.
[16:24] <kwmonroe> bobeo: what kinds of things are you manually configuring?
[16:25] <bobeo> logstash, filebeats, and hopefully client and admin systems for elastic so it will work. currently its not responding to web requests or curl requests, which is why mine isnt working
[16:26] <bobeo> I wish I knew how to do that. I know how to configure these systems via generic install with ease, but not with juju. if you guys can show me how, I can do a lot to contribute, even if they might need a few tweeks.
[16:26] <bobeo> I would love to give back kwmonroe
[16:27] <kwmonroe> sure bobeo -- just tell me what you've had to change.  you mentioned elastic wasn't responding to curl -- did you change something in /etc/elasticsearch/elasticsearch.yml to make it work for you?
[16:28] <kwmonroe> similarly with filebeat -- was it something in /etc/filebeat/filebeat.yaml that you had to configure so that logs would ship to logstash?
[16:29] <bobeo> kwmonroe: no, its still not responding. Ive had issues with elasticsearch in graylog and in ELK, making me think elasticsearch is having issues. graylog says elastic 6x isnt workign with graylog 2.4 atm, and ELK seems to be having issues with elastic as well, at least as far as I can tell so far. Logstash and kibana are working fine for me.
[16:31] <bobeo> kwmonroe: yea, I had to make changes in filebeat. specifically I had to add elasticsearch IP from localhost
[16:32] <bobeo> for some reason, it had elasticsearch uncommentd, with correct port, but pointed at local host instead of at the IP for elasticsearch
[17:06] <jhobbs> rick_h_: where can i find the agent stream on the web? are agents for non x86 architectures built for non released versions of juju?
[17:09] <rick_h_> jhobbs: typically no we don't. We must at some point but not sure if beta or rc is when that kicks in. I've got a question out but not sure yet.
[17:14] <rick_h_> jhobbs: ok found http://streams.canonical.com/juju/tools/agent/2.4-beta2/
[17:14] <rick_h_> But have to find the stream file to reference it
[17:15] <jhobbs> cool, arm64 agent is what i'm after
[17:15] <jhobbs> is that devel? proposed?
[17:20] <rick_h_> jhobbs: searching the various stream files I can see. I don't have it yet. I'm not up on which one is used.
[17:20] <jhobbs> ok no problem
[17:21] <jhobbs> i can try them all!
[17:21] <jhobbs> thanks rick_h_
[17:23] <rick_h_> Yea at least feel better I can see arch built agents
[17:23] <jhobbs> yeah, and now i know to test with beta2 instead of edge
[17:23] <jhobbs> so i'm in a happier place
[17:30] <bobeo> hey rick_h_ is there a way to marry both graylog and elk together? I mean, I like the way graylog handles data a lot better than ELK, especially with indexing, and I like its ease of use, but I like the UI better frrom older kibana instances. is this possible you think?
[17:32] <rick_h_> jhobbs: ok, they're listed in http://streams.canonical.com/juju/tools/streams/v1/com.ubuntu.juju-devel-tools.sjson
[17:32] <rick_h_> bobeo: sorry no, I'm not familiar enough with graylog/elk unfortunately.
[17:37] <jhobbs> rick_h_: woo hoo! thank you
[18:08] <bdx> bobeo: what do you mean marry the two together?
[18:50] <bobeo> bdx: so there are several really great portions of both, for instance kibana, I love kibana, way more than the graylog UI, and I love how graylog does indexing, and handles logs, way more than how elk does it. Id like to take the kibana UI, put it on graylog, and use how graylog imports and processes logs, as compared to logstash, which it might be using? Im still digging through graylog docs on what its actually "made of/from"
[18:57] <bdx> bobeo: you can connect kibana to the elasticsearch that you use for graylog and have what you desire
[18:58] <bobeo> bdx: I did that actually, remember that "X" i wanted to build? I built that today. Now I just need to make sure elastic is working properly, but im hitting issues. Its not responding to curl requests.
[18:59] <bobeo> bdx: it, as in ElasticSearch, my current deployment of it. http://paste.ubuntu.com/p/tKTTVkQ6Mn/
[19:56] <kwmonroe> bobeo: fwiw, i took the elk-stack bundle and swapped logstash for graylog.. the result is https://jujucharms.com/u/kwmonroe/egk-stack/
[19:57] <kwmonroe> bobeo: it's totally a dev bundle, but it illustrates how you might swap ELK components to your liking.. (logstash for graylog, in this case)
[20:00] <kwmonroe> bobeo: fwiw, i don't have any trouble curl'ing ES:9200 from within the cluster:
[20:00] <kwmonroe> $ juju run --unit elasticsearch/0 'curl -XGET http://localhost:9200/_cluster/health'
[20:00] <kwmonroe> {"cluster_name":"elasticsearch","status":"yellow","timed_out":false,"number_of_nodes":1,"number_of_data_nodes":1,"active_primary_shards":5,"active_shards":5,"relocating_shards":0,"initializing_shards":0,"unassigned_shards":1,"delayed_unassigned_shards":0,"number_of_pending_tasks":0,"number_of_in_flight_fetch":0,"task_max_waiting_in_queue_millis":0,"active_shards_percent_as_number":83.33333333333334}
[20:00] <kwmonroe> i mean, yeah it's yellow, but yellow ain't red!
[20:03] <TheAbsentOne> kwmonroe: can I create bundles from local charms?
[20:03] <kwmonroe> you betcha TheAbsentOne!
[20:04] <kwmonroe> TheAbsentOne: have a look at https://jujucharms.com/hadoop-processing/ see 'bundle-local.yaml' in the side bar
[20:04] <kwmonroe> TheAbsentOne: you'll note the "charm:" directive includes a local path for the charms that you want to pull from your local filesystem... you'd deploy that one with "juju deploy bundle-local.yaml", but substitue whatever your bundle name is.
[20:06] <TheAbsentOne> ahn awesome since you guys were talking about bundles I was asking myself that question xD
[20:07] <TheAbsentOne> thanks for the info kwmonroe
[20:07] <kwmonroe> np
[20:13] <veebers> Morning o/
[20:20] <rick_h_> nmorning veebers
[20:21] <veebers> hi rick_h_ o/
[20:22] <veebers> rick_h_: saw your email, digging in now
[20:22] <rick_h_> veebers: cool, definitely let me know if there's something I should see/walk me through something. Gave it a go but still a lot to learn there.
[20:49] <veebers> rick_h_: right, so I figured out why the cleanup wasn't working and updated lxd on grumpig. (still from xenial backports, haven't moved over to snap yet :-\
[20:50] <rick_h_> veebers: k, by cleanup you mean old lxds from the failed runs?
[21:02] <wallyworld> thumper: you coming to caas standup?
[21:02] <thumper> wallyworld: no, I have another call
[22:28] <thumper> wallyworld: https://github.com/juju/collections/pull/1
[22:28] <wallyworld> looking
[22:29] <wallyworld> thumper: lgtm, so we only had set and dequeue?
[22:30] <thumper> wallyworld: https://github.com/juju/names/pull/88
[22:30] <thumper> yes
[22:30] <veebers> thumper: was making a tea, yep you want to hangout?
[22:30] <thumper> veebers: yeah
[22:30] <thumper> 1:1?
[22:30] <veebers> sounds good omw
[22:30] <wallyworld> thumper: why oh why doesn't go have generics :-(
[22:31] <thumper> uh ha
[22:33] <wallyworld> thumper: done
[23:27] <thumper> wallyworld: https://github.com/juju/proxy/pull/1 and yes, I'm leaving the years the same
[23:27]  * thumper heads to physio
[23:27] <thumper> bbs
[23:47] <wallyworld> kelvinliu__: there's a couple of more things to remove which I've mentioned in the PR
[23:49] <kelvinliu__> wallyworld, yes, i saw the comments, i will fix them soon, thanks.