| *** sshank has quit IRC | 00:12 | |
| *** markvoelker_ has quit IRC | 00:17 | |
| *** yamamoto has joined #openstack-meeting-5 | 00:24 | |
| *** markvoelker has joined #openstack-meeting-5 | 00:25 | |
| *** yamamoto has quit IRC | 00:29 | |
| *** markvoelker has quit IRC | 00:29 | |
| *** markvoelker has joined #openstack-meeting-5 | 00:34 | |
| *** lukepatrick has quit IRC | 00:37 | |
| *** markvoelker has quit IRC | 00:39 | |
| *** markvoelker has joined #openstack-meeting-5 | 00:43 | |
| *** markvoelker has quit IRC | 00:48 | |
| *** markvoelker has joined #openstack-meeting-5 | 00:52 | |
| *** markvoelker has quit IRC | 00:57 | |
| *** markvoelker has joined #openstack-meeting-5 | 01:01 | |
| *** markvoelker has quit IRC | 01:06 | |
| *** markvoelker has joined #openstack-meeting-5 | 01:11 | |
| *** markvoelker has quit IRC | 01:15 | |
| *** markvoelker has joined #openstack-meeting-5 | 01:20 | |
| *** iyamahat has quit IRC | 01:21 | |
| *** yamahata has quit IRC | 01:23 | |
| *** yamamoto has joined #openstack-meeting-5 | 01:24 | |
| *** lukepatrick has joined #openstack-meeting-5 | 01:24 | |
| *** markvoelker has quit IRC | 01:53 | |
| *** markvoelker has joined #openstack-meeting-5 | 01:59 | |
| *** markvoelker has quit IRC | 02:03 | |
| *** markvoelker has joined #openstack-meeting-5 | 02:08 | |
| *** markvoelker has quit IRC | 02:12 | |
| *** markvoelker has joined #openstack-meeting-5 | 02:17 | |
| *** markvoelker has quit IRC | 02:21 | |
| *** markvoelker has joined #openstack-meeting-5 | 02:26 | |
| *** markvoelker has quit IRC | 02:30 | |
| *** markvoelker has joined #openstack-meeting-5 | 02:35 | |
| *** markvoelker has quit IRC | 02:40 | |
| *** TuanLA has joined #openstack-meeting-5 | 02:44 | |
| *** markvoelker has joined #openstack-meeting-5 | 02:44 | |
| *** TuanLA has quit IRC | 02:44 | |
| *** markvoelker has quit IRC | 02:49 | |
| *** TuanLA has joined #openstack-meeting-5 | 02:52 | |
| *** markvoelker has joined #openstack-meeting-5 | 02:53 | |
| *** daidv has quit IRC | 03:02 | |
| *** daidv has joined #openstack-meeting-5 | 03:08 | |
| *** markvoelker has quit IRC | 03:27 | |
| *** lukepatrick has quit IRC | 03:33 | |
| *** TuanLA has quit IRC | 03:45 | |
| *** yamahata has joined #openstack-meeting-5 | 03:45 | |
| *** TuanLA has joined #openstack-meeting-5 | 03:46 | |
| *** markvoelker has joined #openstack-meeting-5 | 04:17 | |
| *** markvoelker has quit IRC | 04:22 | |
| *** markvoelker has joined #openstack-meeting-5 | 04:27 | |
| *** markvoelker has quit IRC | 04:33 | |
| *** markvoelker has joined #openstack-meeting-5 | 04:34 | |
| *** daidv has quit IRC | 05:06 | |
| *** daidv has joined #openstack-meeting-5 | 05:52 | |
| *** markvoelker has quit IRC | 05:54 | |
| *** markvoelker has joined #openstack-meeting-5 | 06:50 | |
| *** ralonsoh has joined #openstack-meeting-5 | 07:49 | |
| *** ralonsoh_ has joined #openstack-meeting-5 | 07:50 | |
| *** ralonsoh has quit IRC | 07:54 | |
| *** ralonsoh_ is now known as ralonsoh | 07:55 | |
| *** daidv has quit IRC | 08:01 | |
| *** iyamahat has joined #openstack-meeting-5 | 08:10 | |
| *** iyamahat_ has joined #openstack-meeting-5 | 08:11 | |
| *** iyamahat has quit IRC | 08:14 | |
| *** iyamahat_ has quit IRC | 08:20 | |
| *** iyamahat_ has joined #openstack-meeting-5 | 08:21 | |
| *** iyamahat_ has quit IRC | 08:25 | |
| *** yamahata has quit IRC | 08:26 | |
| *** derekh has joined #openstack-meeting-5 | 08:34 | |
| *** yamamoto has quit IRC | 08:47 | |
| *** yamamoto has joined #openstack-meeting-5 | 08:55 | |
| *** yamamoto has quit IRC | 08:55 | |
| *** markvoelker has quit IRC | 09:03 | |
| *** markvoelker has joined #openstack-meeting-5 | 09:04 | |
| *** yamamoto has joined #openstack-meeting-5 | 09:15 | |
| *** TuanLA has quit IRC | 10:05 | |
| *** yamamoto has quit IRC | 10:18 | |
| *** yamamoto has joined #openstack-meeting-5 | 10:25 | |
| *** yamamoto has quit IRC | 10:30 | |
| *** yamamoto has joined #openstack-meeting-5 | 11:26 | |
| *** yamamoto has quit IRC | 11:32 | |
| *** yamamoto has joined #openstack-meeting-5 | 11:41 | |
| *** yamamoto_ has joined #openstack-meeting-5 | 11:42 | |
| *** yamamoto has quit IRC | 11:46 | |
| *** yamamoto_ has quit IRC | 11:56 | |
| *** yamamoto has joined #openstack-meeting-5 | 12:19 | |
| *** mjturek has joined #openstack-meeting-5 | 12:54 | |
| *** yamamoto has quit IRC | 12:54 | |
| *** lukepatrick has joined #openstack-meeting-5 | 13:10 | |
| *** felipemonteiro_ has joined #openstack-meeting-5 | 13:43 | |
| *** felipemonteiro__ has joined #openstack-meeting-5 | 13:44 | |
| *** felipemonteiro_ has quit IRC | 13:48 | |
| *** lukepatrick has quit IRC | 13:54 | |
| *** yamamoto has joined #openstack-meeting-5 | 13:55 | |
| *** yamamoto has quit IRC | 14:05 | |
| *** yamahata has joined #openstack-meeting-5 | 14:20 | |
| *** iyamahat has joined #openstack-meeting-5 | 14:41 | |
| *** iyamahat has quit IRC | 14:45 | |
| *** yamamoto has joined #openstack-meeting-5 | 14:47 | |
| *** yamamoto has quit IRC | 14:47 | |
| *** alraddarla has joined #openstack-meeting-5 | 14:55 | |
| *** mateuszb has joined #openstack-meeting-5 | 14:58 | |
| mattmceuen | #startmeeting openstack-helm | 15:00 |
|---|---|---|
| openstack | Meeting started Tue Oct 17 15:00:37 2017 UTC and is due to finish in 60 minutes. The chair is mattmceuen. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: openstack-helm)" | 15:00 | |
| openstack | The meeting name has been set to 'openstack_helm' | 15:00 |
| mattmceuen | #topic rollcall | 15:00 |
| *** openstack changes topic to "rollcall (Meeting topic: openstack-helm)" | 15:00 | |
| portdirect | o/ | 15:00 |
| jayahn | o/ | 15:01 |
| mateuszb | o/ | 15:01 |
| alraddarla | o/ | 15:01 |
| mattmceuen | Here's the agenda, all -- I'll give you a couple mins to add topics: https://etherpad.openstack.org/p/openstack-helm-meeting-2017-10-17 | 15:01 |
| *** gagehugo has joined #openstack-meeting-5 | 15:03 | |
| v1k0d3n | o/ | 15:03 |
| xek | o/ | 15:03 |
| *** kiennt26_ has joined #openstack-meeting-5 | 15:03 | |
| mattmceuen | #topic update to official project status | 15:03 |
| *** openstack changes topic to "update to official project status (Meeting topic: openstack-helm)" | 15:03 | |
| mattmceuen | Just an update -- we submitted OSH for TC governance last week | 15:04 |
| mattmceuen | https://etherpad.openstack.org/p/openstack-helm-meeting-2017-10-17 | 15:04 |
| srwilkers | o/ | 15:04 |
| jayahn | yeap. | 15:04 |
| mattmceuen | Review is ongoing, but it's looking very positive. Seven +1 roll-call votes so far. :) | 15:04 |
| mattmceuen | That's really all I have to say about that. Hopefully good progress next week. Any other thoughts on the topic? | 15:05 |
| mattmceuen | #topic log-based alerting | 15:06 |
| *** openstack changes topic to "log-based alerting (Meeting topic: openstack-helm)" | 15:06 | |
| portdirect | nothing other than congrats mattmceuen | 15:06 |
| portdirect | :D | 15:06 |
| mattmceuen | Thanks @portdirect :) back at you man | 15:06 |
| mateuszb | I've been investigating different methods for sending alerts based on logs | 15:06 |
| mateuszb | Tat was discussed during last AT&T and Intel meeting | 15:06 |
| v1k0d3n | yeah, really happy to see this mattmceuen. great seeing you leading the charge. | 15:07 |
| mateuszb | Before I proceed with an implementation I'd like to know your opinion ;) | 15:07 |
| mateuszb | As for now I'm aware of 2 approaches: | 15:07 |
| mateuszb | 1. Using ElastAlert | 15:07 |
| mateuszb | 2. Using Prometheus plugin for fluentd (https://github.com/kazegusuri/fluent-plugin-prometheus ) | 15:07 |
| mateuszb | The idea behind both of them is the same: search for specified patterns (for example "Can't connect to MySQL") in container logs | 15:08 |
| mateuszb | and if the pattern occurs - fire an alert | 15:08 |
| mateuszb | I'd be rather in favor of using ElastAlert as it's easier to configure and more intuitive for me | 15:09 |
| mateuszb | It periodically queries ElasticSearch to retrieve a given pattern | 15:09 |
| mateuszb | It has highly modular approach - each rule is a separate file | 15:09 |
| jayahn | I will look at ElastAlert. Just a question here. What is our purpose here? there can probably be many method to do log-based alarm. do we want to say "there is a reference implementation on log-based alert"? | 15:09 |
| mateuszb | You can configure timeouts, thresholds and so on out of the box. I'd require, however, additional chart to be implemented | 15:09 |
| mattmceuen | How does that compare to the Prometheus plugin, mateuszb? | 15:10 |
| mattmceuen | Does it also support a modular approach, or more monolithic? | 15:10 |
| mateuszb | jayahn - that's a good question :) I'd like to know what the requirements from AT&T side are | 15:11 |
| portdirect | mateuszb: thats not to important here :) | 15:11 |
| portdirect | what does the community want - hopefully we align internally with that | 15:11 |
| jayahn | important stuff would be "what alert we want to have". this can be a shared list. how to implement it will highly depends on what tools you use. | 15:11 |
| mattmceuen | Agree. | 15:11 |
| mattmceuen | I would like srwilkers as our LMA SME to weigh in as well | 15:12 |
| portdirect | ++ | 15:12 |
| jayahn | so, IMHO, defining the basic set of alerts would be valuable. | 15:12 |
| srwilkers | i'd need to look at the differences between elastalert and the prometheus plugin, but i'd honestly prefer to handle it via prometheus if the end result is the same | 15:12 |
| portdirect | srwilkers: how is the prometheus ps progressing? | 15:13 |
| mateuszb | I agree. I can imagine that for the beginning we can start with alerts which inform about DB/rabbitmq connection issues in specified pods | 15:13 |
| portdirect | its pretty clost to being out of WIP is it not? | 15:13 |
| srwilkers | portdirect: its out of WIP and ready for some initial reviews | 15:13 |
| portdirect | w00t | 15:13 |
| srwilkers | im currently working on getting jobs set up for the controller manager and scheduler, but thats roughly another ~10m worth of work | 15:13 |
| srwilkers | once that's done, i'll be happy with where it stands | 15:14 |
| mattmceuen | would it make sense to take this as a homework assignment: srwilkers and jayahn to get acquainted w/ ElastAlert, and mateuszb maybe you could do a comparative example of a few rules, implemented by both tools, that you could share? | 15:14 |
| jayahn | if we know what alerts we want to create, then we can use that list to evaluate how "a specific alert implmentation tool" can satisfy our requirements. that said, initiating an effort to defining a basic set of alerts would be also valuable. | 15:14 |
| mateuszb | The result would be the same (or at least as for now I don't know any limitations) | 15:14 |
| portdirect | that sounds like an awesome idea mattmceuen | 15:14 |
| srwilkers | if you call this homework, im going to be a typical CS student and wait until the last minute ;) | 15:15 |
| portdirect | and presumably there is nothing precluding both from being implemented? | 15:15 |
| mattmceuen | Sorry, I meant to say "ice cream" | 15:15 |
| portdirect | if they serve diff use cases | 15:15 |
| mateuszb | Ok, so I'll prepare 2 patchets (one for ElastAlert and one for fluentd-prometheus plugin) | 15:16 |
| srwilkers | portdirect: nope, there's not. like jayahn said, it'd just be a matter of determining if we want to choose a reference or not | 15:16 |
| jayahn | we should say "pizza". typical CS student can do anything for pizza. | 15:16 |
| mattmceuen | @jayahn that is another good homework assignment :) do we have any list in progress around specific alerts needed? | 15:16 |
| mattmceuen | ha! | 15:16 |
| srwilkers | mateuszb: in regards to the fluentd plugin, it'd be nice to make sure it works with the fluentbit+fluentd set up that's in review currently | 15:16 |
| jayahn | i can write up some initial docs regarding alert needed | 15:17 |
| mateuszb | srwilkers: I'll do that on top of fluentbit+fluentd PS | 15:17 |
| mateuszb | srwilkers: in fact, that is a requirement for fluentd-prometheus plugin to work | 15:17 |
| mattmceuen | jayahn mateuszb awesome, thank you! | 15:17 |
| *** markvoelker has quit IRC | 15:17 | |
| mateuszb | cause it enforces us to use only one fluentd instance per cluster which I think will be true when fluentd+fluentbit PS is merged | 15:18 |
| mateuszb | jayahn that would be great | 15:18 |
| *** markvoelker has joined #openstack-meeting-5 | 15:18 | |
| mattmceuen | #action mateuszb will prep comparison of ElastAlert and fluentd-prometheus | 15:19 |
| mattmceuen | #action jayahn will take a stab at initial alerting need documentation | 15:19 |
| jayahn | okay | 15:19 |
| * portdirect notes a mech eng student only works for alcohol | 15:19 | |
| mateuszb | :) | 15:19 |
| mattmceuen | Good discussion guys, anything else on this topic? | 15:20 |
| * jayahn an korean student regardless of major onnly works for alcohol | 15:20 | |
| *** iyamahat has joined #openstack-meeting-5 | 15:20 | |
| mateuszb | that's all from my side | 15:20 |
| srwilkers | ahahaha | 15:20 |
| mattmceuen | @jayahn lol | 15:20 |
| mattmceuen | #topic cw's RFC on storage class name | 15:20 |
| *** openstack changes topic to "cw's RFC on storage class name (Meeting topic: openstack-helm)" | 15:20 | |
| mattmceuen | I'm not sure we have cw? | 15:21 |
| srwilkers | doesnt seem so | 15:21 |
| srwilkers | this was just to rename the general storage class right? | 15:21 |
| mattmceuen | Well let's get him some opinions offline. He has an RFC out for whether we should use "general" or some other name. | 15:21 |
| mattmceuen | yup | 15:21 |
| portdirect | I have some feedback in there: https://review.openstack.org/#/c/511975/ | 15:21 |
| mattmceuen | thx portdirect, copy/paste was failing me ;-) | 15:22 |
| mattmceuen | I'll leave it at that for now -- if you'd like to see the discussion or weigh in, please visit the review! | 15:22 |
| *** markvoelker has quit IRC | 15:22 | |
| mattmceuen | #topic Official project docs move (timing and process) | 15:23 |
| *** openstack changes topic to "Official project docs move (timing and process) (Meeting topic: openstack-helm)" | 15:23 | |
| mattmceuen | After we become an official project, I think we'll want to move our docs here, correct? https://docs.openstack.org/openstack-helm/latest/ | 15:23 |
| mattmceuen | (away from readthedocs) | 15:23 |
| portdirect | yup | 15:24 |
| portdirect | I think this should be very simple to do | 15:24 |
| mattmceuen | Will we deprecate the readthedocs at that point, or leave it up? Maintain it? | 15:24 |
| portdirect | I know lamt has insight into what needs done, but i think a theme change and a single ps to infra | 15:25 |
| portdirect | I vote for retiring the readthedocs | 15:25 |
| portdirect | though it would be possible to have both | 15:25 |
| portdirect | and they would stay in sync | 15:25 |
| jayahn | i also vote for retiring the readthedocs once we move to the official doc | 15:25 |
| srwilkers | i'd rather retire them than maintain them | 15:25 |
| portdirect | but seems silly to have them in two places | 15:26 |
| mattmceuen | +1 | 15:26 |
| mattmceuen | #action mattmceuen to discuss readthedocs->docs.openstack.org with lamt | 15:27 |
| mattmceuen | Alrighty: reviews time | 15:27 |
| mattmceuen | #topic reviews needed | 15:27 |
| *** openstack changes topic to "reviews needed (Meeting topic: openstack-helm)" | 15:27 | |
| jayahn | once we move to docs.openstack.org, i can ask official translation to to take openstack-helm project. | 15:27 |
| mattmceuen | great point jay | 15:27 |
| jayahn | i talked with srwilkers on the review. | 15:28 |
| mattmceuen | awesome | 15:28 |
| srwilkers | yep :) | 15:28 |
| portdirect | jayahn: long as you promise not to write nasty things about us in korean ;) | 15:28 |
| mattmceuen | save any nasty comments for english please :-D | 15:28 |
| *** renmak__ has joined #openstack-meeting-5 | 15:29 | |
| jayahn | nothing to add. personally, i would like to have both prometheus and fluent working in our env. asap. :) .. let's get it done. | 15:29 |
| jayahn | ha ha.. | 15:29 |
| mattmceuen | yes | 15:29 |
| srwilkers | jayahn: +1 | 15:29 |
| jayahn | you have google translation. so i will never wirte nasty stuff in korean. | 15:29 |
| mattmceuen | Here's the review for fluent: https://review.openstack.org/#/c/507023/ | 15:30 |
| jayahn | however, we know how to avoid google translation, but still understand each other. tweaked version of korean writing. lol | 15:30 |
| srwilkers | ;) | 15:30 |
| srwilkers | in regards to that review | 15:30 |
| srwilkers | im happy with it after discussing it with jayahn. takeaway was that we can leave kafka as an opportunity for a future addition to OSH | 15:31 |
| portdirect | +2 | 15:31 |
| srwilkers | potentially something for a new contributor to try their hand at | 15:31 |
| jayahn | yes. | 15:31 |
| mattmceuen | excellent | 15:31 |
| portdirect | that was also the one with some fun stuuf in the dep chack was it not? | 15:31 |
| portdirect | *check | 15:31 |
| portdirect | ah yes: https://review.openstack.org/#/c/507023/9/fluent-logging/templates/deployment-fluentd.yaml | 15:32 |
| portdirect | we should probably make a blueprint for extending the dep checking model to account for conditionals | 15:32 |
| portdirect | as this is starting to turn up more and more | 15:32 |
| portdirect | esp in neutron | 15:32 |
| mattmceuen | very good point | 15:32 |
| * portdirect why is it always neutron? | 15:32 | |
| srwilkers | portdirect: i agree | 15:33 |
| jayahn | +1 | 15:33 |
| srwilkers | there are somethings that are best handled via overrides, but conditionals may not be the best place for them | 15:33 |
| srwilkers | took me chewing on that a bit to feel that way | 15:33 |
| srwilkers | well, not all conditionals ill say | 15:33 |
| portdirect | I agree - I've had a few chats with alanmeadows on this | 15:33 |
| portdirect | and will try and summarise what we were mulling over and throw it out there | 15:34 |
| * portdirect notes that hes should bring up somthing else in any other business | 15:34 | |
| mattmceuen | #action portdirect to create a blueprint for extending the OSH dependency checking model to account for conditionals | 15:34 |
| mattmceuen | before other business | 15:35 |
| mattmceuen | any other outstanding reviews we need more eyeballs on? | 15:35 |
| mattmceuen | (also thanks pete :) ) | 15:36 |
| portdirect | https://review.openstack.org/#/c/457754/ | 15:36 |
| srwilkers | nope, im good | 15:36 |
| portdirect | https://review.openstack.org/#/c/507628/ | 15:36 |
| portdirect | ^^ both of these ceph ones are right up on my list of things we want | 15:36 |
| portdirect | i think the disc targetting has a bit to go | 15:36 |
| portdirect | but is getting close | 15:36 |
| mattmceuen | That is great to hear | 15:37 |
| srwilkers | nice. ill take a gander and see what's going on there | 15:37 |
| mattmceuen | Team: good work on reviews this week, I think we're going in a good direction there. | 15:37 |
| mattmceuen | #topic other business | 15:37 |
| *** openstack changes topic to "other business (Meeting topic: openstack-helm)" | 15:37 | |
| mattmceuen | take it away portdirect | 15:37 |
| portdirect | so - (and I'm gonna me a blueprint for this) | 15:38 |
| portdirect | we have a need to be able to run multiple configs of some daemonsets | 15:38 |
| portdirect | ie nova-compute and ovs-agent | 15:38 |
| mattmceuen | is "multiple" on the order of per-node, or a constant? | 15:39 |
| portdirect | we can currently achive this though some footwork using the manifests: true/false, and multiple deployments of a chart, but I'd like a cleaner solution | 15:39 |
| mattmceuen | give me big-o notation, portdirect! | 15:40 |
| portdirect | multiple for us could mean a lot of things unfortunatly - from groups of hardware to canary nodes | 15:40 |
| portdirect | so I'm tinking of extending the to_oslo_config logic for damonsets, and the damonset manifests themselves to allow this | 15:41 |
| portdirect | so an example config would be as folows: | 15:41 |
| * srwilkers waits on the edge of his seat | 15:43 | |
| alraddarla | he probably got distracted while he was typing | 15:43 |
| portdirect | https://www.irccloud.com/pastebin/Fi1hpGbz/ | 15:43 |
| portdirect | so most compute nodes would be debug=true | 15:44 |
| portdirect | ones labeled with `arbitary_label` would be debug=false | 15:44 |
| portdirect | and if its hostname was `hostname` it would be debug=false regardless of what labels etc were applied | 15:44 |
| portdirect | thoughts before I do the initial write-up/proposal? | 15:45 |
| *** lukepatrick has joined #openstack-meeting-5 | 15:45 | |
| srwilkers | hmm | 15:46 |
| mattmceuen | interesting - am I correct in assuming we would continue not to use this for e.g. disk targeting? Or do you see it being used for that? | 15:46 |
| portdirect | disc tragtting could potentially benifit from this | 15:46 |
| portdirect | though thats solving a slightly diff problem | 15:47 |
| mattmceuen | my only concern is that "node_groups" and "nodes" are only meaningful if you already know what they mean | 15:47 |
| portdirect | this would need to be documented | 15:48 |
| *** yamamoto has joined #openstack-meeting-5 | 15:48 | |
| *** mateuszb has quit IRC | 15:48 | |
| mattmceuen | Would it make sense to put them under something (or call them something) more descriptive, like (but better than) per_thing_configs.node_group | 15:48 |
| portdirect | good point | 15:49 |
| portdirect | so like this? | 15:49 |
| portdirect | https://www.irccloud.com/pastebin/FetsDzFf/ | 15:50 |
| mattmceuen | that is a good point, but not the point I was trying to make :) | 15:51 |
| srwilkers | i suppose i'd need to see what's written up and get the line of thinking behind it | 15:51 |
| portdirect | lol | 15:51 |
| portdirect | will do - just putting it out there, for us internally this will be required | 15:51 |
| mattmceuen | I meant literally an id like "per_thing_conf" that made clear what a "node_group" or a "nodes" is -- what's the context | 15:52 |
| portdirect | but would be great to have a solution that works well upstream | 15:52 |
| mattmceuen | I really like the flexibility | 15:52 |
| portdirect | gotcha | 15:52 |
| jayahn | i will follow up on portdirect's upcoming write-up on this. | 15:52 |
| mattmceuen | +1 same, looking forward to it | 15:53 |
| jayahn | and. with my thinking hat. | 15:53 |
| mattmceuen | Aright guys - any other topics? | 15:53 |
| portdirect | I'm good | 15:53 |
| srwilkers | oh, unrelated | 15:53 |
| srwilkers | but TC voting is happening currently | 15:53 |
| srwilkers | dont forget to vote! | 15:53 |
| mattmceuen | thanks for the reminder! | 15:54 |
| mattmceuen | Ok team - good meeting. Have a great day, see you in the chat room! | 15:54 |
| portdirect | theres this dude YamSaple | 15:54 |
| portdirect | whatever you do dont vote for him. | 15:55 |
| v1k0d3n | haha | 15:55 |
| mattmceuen | we don't want to steal time away from him distracting you in our chat room portdirect -- excellent point | 15:55 |
| portdirect | ;) | 15:55 |
| *** yamamoto has quit IRC | 15:55 | |
| mattmceuen | #endmeeting | 15:55 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:55 | |
| openstack | Meeting ended Tue Oct 17 15:55:48 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:55 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-10-17-15.00.html | 15:55 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-10-17-15.00.txt | 15:55 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/openstack_helm/2017/openstack_helm.2017-10-17-15.00.log.html | 15:55 |
| *** alraddarla has left #openstack-meeting-5 | 15:56 | |
| *** gagehugo has left #openstack-meeting-5 | 15:56 | |
| *** kiennt26_ has quit IRC | 16:07 | |
| *** ralonsoh has quit IRC | 16:33 | |
| *** yamahata has quit IRC | 16:34 | |
| *** iyamahat has quit IRC | 16:34 | |
| *** iyamahat has joined #openstack-meeting-5 | 16:53 | |
| *** derekh has quit IRC | 17:09 | |
| *** yamahata has joined #openstack-meeting-5 | 17:11 | |
| *** renmak__ has quit IRC | 17:13 | |
| *** sshank has joined #openstack-meeting-5 | 17:22 | |
| *** sshank has quit IRC | 17:28 | |
| *** ricolin has quit IRC | 17:37 | |
| *** markvoelker has joined #openstack-meeting-5 | 19:26 | |
| *** markvoelker_ has joined #openstack-meeting-5 | 20:15 | |
| *** markvoelker has quit IRC | 20:18 | |
| *** lukepatrick has quit IRC | 20:56 | |
| *** lukepatrick has joined #openstack-meeting-5 | 21:02 | |
| *** lukepatrick has quit IRC | 21:18 | |
| *** lukepatrick has joined #openstack-meeting-5 | 21:23 | |
| *** lukepatrick has quit IRC | 21:23 | |
| *** lukepatrick has joined #openstack-meeting-5 | 21:24 | |
| *** lukepatrick has quit IRC | 21:29 | |
| *** lukepatrick has joined #openstack-meeting-5 | 21:30 | |
| *** felipemonteiro__ has quit IRC | 22:17 | |
| *** lukepatrick has quit IRC | 22:49 | |
| *** mjturek has quit IRC | 22:54 | |
| *** kei-ichi has quit IRC | 23:47 | |
| *** kei-ichi has joined #openstack-meeting-5 | 23:47 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!