Wednesday, 2019-02-20

*** jamesmcarthur has quit IRC00:22
*** jamesmcarthur has joined #openstack-tc00:23
*** jamesmcarthur has quit IRC00:27
*** lbragstad has quit IRC00:34
*** lbragstad has joined #openstack-tc01:01
mnasertc office hours :-)01:01
lbragstado/01:02
mnaserpretty happy of the turnout for the upcoming election honestly01:14
fungioffice hours indeed01:14
fungiand yes, i'm pleased with the list of candidates as well01:15
mnaseri'm happy to see some of the names that came and hope this is finally when we get some apac represetnation01:17
fungior at least get more apac representation01:20
lbragstad++01:27
flwanglbragstad: waves from NZ01:43
lbragstadflwang o/ glad to see you're running for TC :)01:44
zanebmnaser: +101:47
flwanglbragstad: yep, i'm brave again to run for it01:48
*** whoami-rajat has joined #openstack-tc02:32
*** jamesmcarthur has joined #openstack-tc02:37
*** ricolin has joined #openstack-tc03:01
*** jamesmcarthur has quit IRC03:21
*** jamesmcarthur has joined #openstack-tc03:22
*** jamesmcarthur has quit IRC03:27
*** jamesmcarthur has joined #openstack-tc03:44
*** jamesmcarthur has quit IRC03:59
*** jamesmcarthur has joined #openstack-tc04:00
*** jamesmcarthur has quit IRC04:05
*** jamesmcarthur has joined #openstack-tc04:09
*** ricolin has quit IRC04:18
*** jamesmcarthur has quit IRC04:22
*** jamesmcarthur has joined #openstack-tc04:25
*** ricolin has joined #openstack-tc04:30
*** jamesmcarthur has quit IRC04:30
*** lbragstad_ has joined #openstack-tc04:36
*** lbragstad has quit IRC04:37
*** jamesmcarthur has joined #openstack-tc04:53
*** diablo_rojo has quit IRC04:55
*** jamesmcarthur has quit IRC04:59
*** lbragstad has joined #openstack-tc05:23
*** lbragstad_ has quit IRC05:25
*** lbragstad_ has joined #openstack-tc05:29
*** lbragstad has quit IRC05:31
*** lbragstad has joined #openstack-tc05:41
*** lbragstad_ has quit IRC05:43
*** lbragstad_ has joined #openstack-tc05:57
*** lbragstad has quit IRC05:58
*** lbragstad has joined #openstack-tc06:20
*** lbragstad_ has quit IRC06:22
*** Luzi has joined #openstack-tc06:52
*** dangtrinhnt has quit IRC07:01
*** jamesmcarthur has joined #openstack-tc07:18
*** jamesmcarthur has quit IRC07:22
*** e0ne has joined #openstack-tc07:25
*** dangtrinhnt has joined #openstack-tc07:26
*** lbragstad has quit IRC08:15
*** jpich has joined #openstack-tc08:24
*** dtantsur|afk is now known as dtantsur08:34
*** tosky has joined #openstack-tc08:43
*** ricolin has quit IRC08:55
*** e0ne has quit IRC09:33
*** zaneb has quit IRC09:53
*** ianychoi has quit IRC10:59
*** e0ne has joined #openstack-tc11:54
*** cdent has joined #openstack-tc12:04
*** jamesmcarthur has joined #openstack-tc13:18
*** jamesmcarthur has quit IRC13:22
*** cdent_ has joined #openstack-tc13:22
*** jamesmcarthur has joined #openstack-tc13:22
*** ianychoi has joined #openstack-tc13:22
*** cdent_ has quit IRC13:23
*** mriedem has joined #openstack-tc13:28
*** ijolliffe has joined #openstack-tc13:29
*** jamesmcarthur has quit IRC13:33
openstackgerritMerged openstack/governance master: Create separate Placement project  https://review.openstack.org/63641613:40
*** spsurya has joined #openstack-tc13:44
*** jamesmcarthur has joined #openstack-tc13:51
*** jamesmcarthur has quit IRC13:51
*** jamesmcarthur has joined #openstack-tc13:52
*** lbragstad has joined #openstack-tc14:32
*** lbragstad_ has joined #openstack-tc14:40
*** lbragstad has quit IRC14:41
*** jamesmcarthur has quit IRC14:53
*** lbragstad has joined #openstack-tc14:53
*** lbragstad_ has quit IRC14:54
*** lbragstad_ has joined #openstack-tc14:56
*** lbragstad has quit IRC14:58
*** lbragstad_ has quit IRC14:58
*** lbragstad has joined #openstack-tc15:01
*** Luzi has quit IRC15:11
*** lbragstad_ has joined #openstack-tc15:12
*** lbragstad has quit IRC15:13
*** lbragstad_ is now known as lbragstad15:18
*** e0ne has quit IRC16:01
*** e0ne has joined #openstack-tc16:02
*** e0ne has quit IRC17:04
*** dtantsur is now known as dtantsur|afk17:14
*** jpich has quit IRC17:25
*** jaosorior has quit IRC17:49
*** jaosorior has joined #openstack-tc17:49
*** diablo_rojo has joined #openstack-tc18:01
*** cdent has quit IRC18:09
dhellmanntonyb , diablo_rojo , fungi : I have tagged the governance repo at c452ccff321f5a776e9bb0ca1540ff551bc93d7d with feb-2019-elections as requested. Please let me know if everything looks right.18:10
fungidhellmann: lgtm!18:33
fungithanks a ton18:33
*** cdent has joined #openstack-tc18:42
*** e0ne has joined #openstack-tc18:50
diablo_rojothanks dhellmann!19:00
dhellmannthanks for confirming19:01
*** e0ne has quit IRC19:10
*** jaosorior has quit IRC19:18
*** jaosorior has joined #openstack-tc19:28
*** e0ne has joined #openstack-tc19:30
mnaserone day i'll convince some people to write an oslo messaging driver that uses a combination of etcd+http to do rpc19:34
jroll++19:34
mnaserand the best part is it wouldn't even be that complicated because as long as we can get an implementation inside oslo messaging going, it'd be so easy afterwards19:35
cdentI thought someone had already started that?19:35
cdentI'm not sure how far they got though19:36
smcginnisTooz and etcd3gateway?19:36
jrollI'm just curious how well the interface maps to that model19:37
jrollone day I'll have the time to turn off everything else and dive in19:37
cdentrotflmaocoptr19:38
cdent"one day"19:38
dhellmannthe best idea no one ever implemented...19:39
mnaseri guess i have fun weekend plans ahead of me19:40
cdentDo you have a vice or favorite drink/food/whatever mnaser ?19:40
cdentI'd like to promise you such a thing if you manage to pull it off, but want to get in the right ballpark.19:41
mnaseri'd probably just be happy enough if people pick it up and it becomes a standard, then i never have to run rabbitmq ever again19:41
smcginnismnaser: https://github.com/dims/etcd3-gateway19:41
*** e0ne has quit IRC19:41
mnaserou thats useful19:42
smcginnisIn use for distributed locking, but seems like it shouldn't be too difficult to use for messaging too.19:43
mnasersmcginnis: the idea is that we wouldnt use it for messaging, but instead simply as a key-value store to register services and endpoints19:43
mnaserand they talk directly to each other instead of through $some_tool19:43
cdentit's probabl possible to fake rpc over etcd with watchers19:44
smcginnisTricky part would be handling service restarts and such.19:44
cdentwhich would more closely align with the oslo.messaging interface19:44
jrollmnaser: not etcd-based, but this may be relevant to your interests as well: https://review.openstack.org/#/c/633052/19:44
cdentbut it might be that trying to hew to om interface is an impedance mismatch19:45
smcginnisjroll: Any noticable performance improvements with that?19:45
mnaseroh thats interesting19:45
mnaserjson-rpc hmm19:45
jrollsmcginnis: the patch was originally written to make a tiny standalone ironic deployment easier - I haven't had time to see how it does at scale19:45
mnaserwow thats really interesting19:46
smcginnisHah, funny. I remember talking to jgriffith about doing something similar for a smaller cinder standalone option.19:46
jrollI'd also prefer a real API over json-rpc, but this got the job done19:46
mnaseri was pretty much thinking of pushing that a step lower down to oslo.messaging and we'd all get that benefit i guess19:46
dhellmannmnaser : you should look at the oslo.messaging cast() feature. it doesn't really work with point-to-point semantics, it's more of a work queue.19:46
mnaserdhellmann: yeah, that's an interesting thing you're bringing up here as well19:47
dhellmannif we were just doing point-to-point rpc someone would have removed rabbit a long time ago19:47
mnaseri guess the "alternative" is that we can do really do point-to-point technically19:48
dhellmannmy idea was to use etcd as the broker, instead of rabbit. post messages to a specific place based on the topic, etc. then have clients listening there.19:48
mnaserwe can get a list of all the services identified by name (i.e. nova-scheduler)19:48
mnaserand then pick one at random to send a request to19:48
dhellmannthe zmq advocates tried the approach of using zmq to build their own broker, but that just meant you had to run *that*19:49
dhellmannI don't know if that's going to have the same load balancing characteristics of what we do now, but it's interesting19:49
mnasertechnically, that's about the same thing as casting it, because usually we assume only a single consumer19:49
dhellmannoh, cast() can also have multiple responses, I think? maybe talk to kgiusti19:49
mnaseri can imagine other scenarios like periodic updates from agents to update other agents on their state19:49
mnaseri dont know the super internals of oslo messaging yet but im assuming there's two types of casts, one that is picked up by all agents (i.e. periodic update) and one that is picked up by one only to do work (i.e. nova-conductor asking schedulers to pick a host)19:50
*** e0ne has joined #openstack-tc19:51
mnaserit would probably be a good exercise to also look at how other tools build their architecture (say, k8s.. for messaging)19:56
tonybdhellmann: Thanks.  #shipit Oh wait ... :D19:57
smcginnisAlso keep in mind active/passibe and active/active HA deployments. That can get tricky real quick if you start talking point to point communications.19:59
dhellmannmnaser : there are 4 methods for sending in the driver, for direct, topic, fanout, and notify. I don't remember off the top of my head how they're used by the higher-level code, though20:00
dhellmannsmcginnis : good point. there's a reason that message brokers exist.20:00
mnaserdhellmann: interesting20:01
mnaserof course, i'm not saying that we should start building our own message broker .. but, they are a big pain point for deployers20:01
dhellmannhence my suggestion to put the message in etcd, which is something they're used to running with fewer complaints, and build the driver to use etcd as a broker20:02
dhellmannif it was easy, we would have done it a long time ago20:02
*** jamesmcarthur has joined #openstack-tc20:02
cdentAnother thing to keep in mind with the way we do RPC, now, is that we tend to send around big objects, rather than signalling that a thing (kept centrally) needs something to happen20:04
mnasercdent: yeah thats' the thing that's on my mind when im thinking about this20:04
mnaserif say, etcd is designed to move huge objects around20:04
cdentIf we were a bit more pub/subby we could say "identifier X needs someone to take an action on it"20:05
cdentrather than "someone, I provide you with X, please do this thing"20:05
mnasercdent: i think part of it is the fact that conductors are a thing20:06
mnaserso agents need to still get all the info they need because they cant talk to the db20:06
mugsiefrom what I remember k8s has issues using etcd for a queue - for larger (100+ nodes) we used to have to try and separate the events etcd from the state store one.20:39
*** spsurya has quit IRC20:42
*** jamesmcarthur has quit IRC21:05
*** jamesmcarthur has joined #openstack-tc21:17
*** jamesmcarthur has quit IRC21:55
*** jamesmcarthur has joined #openstack-tc21:59
*** mriedem has quit IRC22:25
*** whoami-rajat has quit IRC22:31
*** e0ne has quit IRC22:32
*** gagehugo has quit IRC22:41
*** ijolliffe has quit IRC22:41
*** cdent has quit IRC22:44
*** jamesmcarthur has quit IRC23:55
*** jamesmcarthur has joined #openstack-tc23:56
*** mriedem has joined #openstack-tc23:57

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