Wednesday, 2017-03-29

*** hoonetorg has quit IRC00:32
*** gcb has quit IRC00:41
*** hoonetorg has joined #openstack-oslo00:45
*** zhangguoqing has joined #openstack-oslo00:48
*** tovin07_ has joined #openstack-oslo00:59
*** jamielennox is now known as jamielennox|away01:02
*** pblaho has quit IRC01:11
*** pblaho has joined #openstack-oslo01:12
*** jamielennox|away is now known as jamielennox01:16
*** e0ne has joined #openstack-oslo01:20
*** david-lyle has joined #openstack-oslo01:24
*** e0ne has quit IRC01:25
*** hoonetorg has quit IRC01:42
*** amotoki has joined #openstack-oslo01:46
*** hoonetorg has joined #openstack-oslo01:54
*** gcb has joined #openstack-oslo01:58
*** amotoki has quit IRC01:58
*** tommylikehu_ has joined #openstack-oslo02:03
*** tommylikehu_ has quit IRC02:08
*** yamahata has quit IRC02:14
*** e0ne has joined #openstack-oslo02:21
*** e0ne has quit IRC02:25
*** yamamoto has joined #openstack-oslo02:29
*** yamamoto has quit IRC02:33
*** dharinic has joined #openstack-oslo02:34
*** david-lyle has quit IRC02:36
*** xianghui has joined #openstack-oslo02:40
*** xianghui_ has joined #openstack-oslo02:43
*** xianghui has quit IRC02:46
*** ihrachys has joined #openstack-oslo02:46
*** amotoki has joined #openstack-oslo03:00
*** xianghui1__ has joined #openstack-oslo03:04
*** xianghui1__ has quit IRC03:04
*** xianghui_ has quit IRC03:07
*** links has joined #openstack-oslo03:12
*** nicolasbock has quit IRC03:15
*** e0ne has joined #openstack-oslo03:22
*** dimtruck is now known as zz_dimtruck03:23
*** e0ne has quit IRC03:23
*** erlon has quit IRC03:35
*** david-lyle has joined #openstack-oslo03:37
*** gcb has quit IRC03:45
*** gcb has joined #openstack-oslo03:59
*** Dinesh_Bhor has joined #openstack-oslo04:00
*** zhangguoqing has quit IRC04:06
*** e0ne has joined #openstack-oslo04:22
*** e0ne has quit IRC04:27
*** pksingh has joined #openstack-oslo05:08
*** sanfern has joined #openstack-oslo05:10
pksinghHello , i am getting 'oslo_config.cfg.NoSuchOptError: no such option verbose in group [DEFAULT]', in tox -epy27, yesterday it was working fine05:10
pksinghis there any changes related this in oslo?05:10
*** zhangguoqing has joined #openstack-oslo05:17
*** e0ne has joined #openstack-oslo05:23
*** e0ne has quit IRC05:28
gcbpksingh,  which project?05:30
gcbpksingh:  we removed  option  verbose in https://review.openstack.org/#/c/444217/05:31
pksinghgcb: openstack/watcher05:32
pksinghgcb: https://github.com/openstack/watcher/blob/master/watcher/tests/conf_fixture.py#L39, do we need to remove this option?05:32
*** zhangguoqing has quit IRC05:32
*** zhangguoqing has joined #openstack-oslo05:34
gcbpksingh:  yes, please remove the usage of option, then it should work05:34
*** yamamoto has joined #openstack-oslo05:35
*** zhangguo_ has joined #openstack-oslo05:36
*** zhangguoqing has quit IRC05:38
pksinghgcb: thanks a lot05:39
*** rcernin has joined #openstack-oslo05:39
gcbpksingh: np05:39
*** zhangguo_ has quit IRC05:39
*** zhangguoqing has joined #openstack-oslo05:40
*** zhangguoqing has quit IRC05:40
*** yamamoto has quit IRC05:40
*** zhangguoqing has joined #openstack-oslo05:41
*** zhangguoqing has quit IRC05:45
*** lpetrut has joined #openstack-oslo05:45
*** yamahata has joined #openstack-oslo05:47
*** zhangguoqing has joined #openstack-oslo05:48
*** lpetrut has quit IRC05:49
*** zhangguoqing has quit IRC05:49
*** jamielennox is now known as jamielennox|away06:10
*** zhangguoqing has joined #openstack-oslo06:11
*** jaosorior has joined #openstack-oslo06:14
*** nkrinner_afk is now known as nkrinner06:20
*** pcaruana has joined #openstack-oslo06:24
*** tovin07 has joined #openstack-oslo06:25
*** jamielennox|away is now known as jamielennox06:25
*** dharinic has quit IRC06:35
*** yamamoto has joined #openstack-oslo06:41
*** gcb has quit IRC06:42
*** yamamoto has quit IRC06:47
*** pksingh has quit IRC06:47
*** oanson has quit IRC06:48
*** jamielennox is now known as jamielennox|away06:50
*** gcb has joined #openstack-oslo06:51
*** jamielennox|away is now known as jamielennox06:57
*** dharinic has joined #openstack-oslo07:01
*** dharinic has quit IRC07:09
*** tesseract has joined #openstack-oslo07:14
openstackgerritMerged openstack/oslo.messaging master: Updated from global requirements  https://review.openstack.org/44294607:20
*** aarefiev_afk is now known as aarefiev07:32
*** jpena|off is now known as jpena07:39
*** yamamoto has joined #openstack-oslo07:43
*** sileht has quit IRC07:45
*** tovin07 has quit IRC07:45
*** yamamoto has quit IRC07:48
*** lucas-afk is now known as lucas-event07:49
*** jpena is now known as jpena|off07:53
*** e0ne has joined #openstack-oslo07:54
openstackgerritMerged openstack/oslo.messaging master: Add HACKING.rst  https://review.openstack.org/44939107:55
*** jpena|off is now known as jpena07:59
*** zzzeek has quit IRC08:00
*** zhangguoqing has quit IRC08:00
*** zzzeek has joined #openstack-oslo08:03
*** shardy has joined #openstack-oslo08:03
*** zhangguoqing has joined #openstack-oslo08:08
*** tommylikehu_ has joined #openstack-oslo08:09
*** tommylikehu_ has quit IRC08:13
openstackgerritChangBo Guo(gcb) proposed openstack/oslo.messaging master: Try to fix TestSerializer.test_call_serializer failed randomly  https://review.openstack.org/45123908:15
*** jamielennox is now known as jamielennox|away08:17
openstackgerritChangBo Guo(gcb) proposed openstack/oslo.messaging master: serializer: remove deprecated RequestContextSerializer  https://review.openstack.org/44739008:22
*** gcb has quit IRC08:39
*** gcb has joined #openstack-oslo08:39
*** yamamoto has joined #openstack-oslo08:45
*** yamamoto has quit IRC08:50
*** chenying__ has quit IRC08:57
*** rpodolyaka_afk is now known as rpodolyaka08:57
*** chenying__ has joined #openstack-oslo08:57
*** ihrachys has quit IRC09:09
*** ihrachys has joined #openstack-oslo09:10
*** ihrachys has quit IRC09:17
*** yamahata has quit IRC09:27
*** sdague has joined #openstack-oslo09:29
*** sambetts|afk is now known as sambetts09:30
*** zhangguoqing has quit IRC09:32
*** zhangguoqing has joined #openstack-oslo09:33
*** amotoki has quit IRC09:40
*** yamamoto has joined #openstack-oslo09:46
*** zhangguoqing has quit IRC09:51
*** yamamoto has quit IRC09:52
*** zhangguoqing has joined #openstack-oslo09:53
*** zhangguoqing has quit IRC09:55
*** e0ne has quit IRC10:01
*** e0ne has joined #openstack-oslo10:01
*** tommylikehu_ has joined #openstack-oslo10:10
*** tommylikehu_ has quit IRC10:15
*** amotoki has joined #openstack-oslo10:16
*** gcb has quit IRC10:16
*** amotoki has quit IRC10:17
*** tovin07_ has quit IRC10:20
*** boden has joined #openstack-oslo10:28
*** zhangguoqing has joined #openstack-oslo10:29
*** nicolasbock has joined #openstack-oslo10:31
*** amotoki has joined #openstack-oslo10:31
openstackgerritMerged openstack/oslo.service master: Updated from global requirements  https://review.openstack.org/45105310:33
openstackgerritMerged openstack/oslo.service master: Fix some reST field lists in docstrings  https://review.openstack.org/44848410:34
*** amotoki has quit IRC10:40
*** yamamoto has joined #openstack-oslo10:48
openstackgerritMerged openstack/oslo.service master: Use Sphinx 1.5 warning-is-error  https://review.openstack.org/44857010:50
*** yamamoto has quit IRC10:54
*** sanfern has quit IRC10:55
*** yamamoto has joined #openstack-oslo11:09
*** tommylikehu_ has joined #openstack-oslo11:10
*** amotoki has joined #openstack-oslo11:11
*** tommylikehu_ has quit IRC11:18
*** yamamoto has quit IRC11:19
*** tommylikehu_ has joined #openstack-oslo11:22
*** Guest16838 has quit IRC11:26
*** Guest16838 has joined #openstack-oslo11:29
*** tommylikehu_ has quit IRC11:30
openstackgerritMerged openstack/tooz master: tests: fix etcd and consul test run  https://review.openstack.org/44856411:37
*** sanfern has joined #openstack-oslo11:47
*** tommylikehu_ has joined #openstack-oslo11:56
*** tommylikehu_ has quit IRC11:57
*** zhangguoqing has quit IRC11:59
*** zhangguoqing has joined #openstack-oslo11:59
*** zhangguoqing has quit IRC12:03
openstackgerritMerged openstack/oslo.messaging master: Trivial: Add executor 'threading' in docstring  https://review.openstack.org/44742412:18
*** yamamoto has joined #openstack-oslo12:20
*** bjornar_ has joined #openstack-oslo12:20
*** gordc has joined #openstack-oslo12:23
*** yamamoto has quit IRC12:25
*** tommylikehu_ has joined #openstack-oslo12:28
openstackgerritDolph Mathews proposed openstack/oslo.config master: Unit tests to illustrate positional argument bug  https://review.openstack.org/45095612:36
openstackgerritDolph Mathews proposed openstack/oslo.config master: Support required positional arguments correctly  https://review.openstack.org/45092812:36
*** jpena is now known as jpena|lunch12:40
*** ansmith has joined #openstack-oslo12:46
*** dtardivel has joined #openstack-oslo13:01
*** gordc has quit IRC13:02
*** gordc has joined #openstack-oslo13:02
*** lucas-event is now known as lucasagomes13:03
*** ihrachys has joined #openstack-oslo13:05
*** kgiusti has joined #openstack-oslo13:05
*** ihrachys has quit IRC13:10
*** sileht has joined #openstack-oslo13:19
*** links has quit IRC13:20
*** erlon has joined #openstack-oslo13:20
*** yamamoto has joined #openstack-oslo13:22
rpodolyakabjornar_: hey! I noticed that you pinged me about handling of multi-server DB configurations in oslo.db on Monday while I was away13:25
rpodolyakabjornar_: I know that zzzeek has been working on something called haalchemy which must be what you want to see13:25
rpodolyakabjornar_: take a look at https://bitbucket.org/zzzeek/haalchemy13:26
*** yamamoto has quit IRC13:28
rpodolyakabjornar_: I'm not sure how mature it is, I just took a quick a look at the docs today, but I like the idea that multi-server config is going to be transparent to clients like oslo.db13:28
bjornar_rpodolyaka, looks good, but is the project still aliive?13:29
rpodolyakabjornar_: not sure :(13:30
bjornar_rpodolyaka, what we do currently is to have loadbalancers-everywhere, but it should not really be needed, but better than the central lb approach13:30
*** kiseok7_ has joined #openstack-oslo13:32
*** kiseok7_ has left #openstack-oslo13:33
*** tommylikehu_ has quit IRC13:34
*** gcb has joined #openstack-oslo13:36
*** jaosorior has quit IRC13:38
*** dmsimard is now known as dmsimard|afk13:39
*** e0ne has quit IRC13:41
*** e0ne has joined #openstack-oslo13:41
*** pkoniszewski has left #openstack-oslo13:42
*** jaosorior has joined #openstack-oslo13:43
*** jpena|lunch is now known as jpena13:45
*** tommylikehu_ has joined #openstack-oslo13:47
*** tongli has joined #openstack-oslo13:51
*** e0ne has quit IRC13:54
openstackgerritMerged openstack-dev/pbr master: Lazy import pkg_resources  https://review.openstack.org/45091313:54
*** lpetrut has joined #openstack-oslo13:55
*** eck` is now known as eck`gone14:03
*** eck`gone is now known as eck`14:03
*** nicolasbock has quit IRC14:05
*** tommylikehu_ has quit IRC14:09
*** tommylikehu_ has joined #openstack-oslo14:10
*** yamamoto has joined #openstack-oslo14:24
*** yamamoto has quit IRC14:29
*** ihrachys has joined #openstack-oslo14:30
*** zz_dimtruck is now known as dimtruck14:30
zzzeekrpodolyaka: I'm likely not continuing w/ haalchemy for now, check out http://www.proxysql.com/14:42
rpodolyakabjornar_: ^14:43
sileht/14:44
rpodolyakaalthough, I guess what bjornar_ is looking for is no proxy in the middle, but rather just the connection string pointing to multiple servers14:45
bjornar_zzzeek, bah14:45
zzzeekbjornar_: why14:45
bjornar_zzzeek, this is not the right solution, the application should be able to handle upstream failure anyway14:45
bjornar_zzzeek, a proxy is a unnessesary bottleck, requires extra hops, extra latency, extra configuration/scaleout complexity and is a spof unless multiple ips are used (which it cannot)14:47
zzzeekbjornar_: the most recent haalchemy concept included a service that runs to report health on the DB, it just doesn't go "between" the application and database.  but was still required.  an earlier concept had each application process pinging the database independently.  that approach has a lot of disadvantages14:47
zzzeekbjornar_: are we talking about openstack w/ galera ?14:47
bjornar_zzzeek, for example, but could be anything basically with multiple ip's .. most relevant is perhaps galera, but not directly related14:48
zzzeekbjornar_: and you have load-profiled haproxy and found it to be a bottleneck ?14:48
bjornar_we are basically talking about a connection pool with multiple servers/ips -- where it points to is irelevant -> could even point to the haproxy proxy for all I care14:48
zzzeekbjornar_: b.c. that's a huge claim.   the latency of haproxy etc. is incredibly low14:48
bjornar_zzzeek, its irelevant. Its extra hops, extra complexity, extra software, spof and so on14:49
bjornar_and if the implementation of a connection pool is beyond scope of oslo.db developers, I hope you are actively trying to find new ones.14:50
zzzeekbjornar_: building a database pinger into every openstack process is more complex and more software (E.g. it is custom to openstack and needs a maintainer)14:50
bjornar_its not about every-openstack project, its about oslo.db or eventually sqlalchemy or whatever dependency14:50
bjornar_memcached and rabbit already has this14:50
rpodolyakabjornar_: curiously enough, it's one of the pain points with the memcache14:51
zzzeekbjornar_: not clear on what "this" is at this point.    HAAlchemy had lots and lots of things it wanted to do, not sure which specific things you are looking for.  do you ahve a document ?14:51
rpodolyakawhen one (or more) of the memcached nodes go down we wait $read_timeout seconds on each request to it14:52
rpodolyakauntil we mark it as "dead"14:52
zzzeekbjornar_: but I will say, "I hope you as maintainer of project X are looking for more people to help with your project because you don't have enough features" is not a helpful statement14:52
rpodolyakaand that knowledge is not shared between forks of openstack services - each one must keep its own list of "dead" memcached's14:53
bjornar_rpodolyaka, sure, the algo can be tuned, but same goes for a keepalived whatever failover for a virtual ip or how one does it14:53
zzzeekbjornar_: direct application->db w/ in-app failover is interesting but is very hard to justify given the existing approaches.   people dont really care about "hops" unless you can show measurable degradation in performance14:54
bjornar_zzzeek, its not just about latency and hops, its also about failover scenarios and so on. Complexity of the setup as a whole14:54
zzzeekbjornar_: that said, haalchemy was going for that approahc where apps connect to the DB directly, the service is used for coordiantion. but it is *very* complicated14:55
bjornar_say one wants to use two loadbalancers for example, its not currently possible14:55
zzzeekbjornar_: you'd use haproxy14:55
bjornar_zzzeek, so how do I ask for example keystone to connect to two haproxy instances?14:56
zzzeekbjornar_: put another one in between14:56
*** amotoki has quit IRC14:56
bjornar_zzzeek, its not that complex, and most of the logic is already inside sqlalchemy.. I mean, it does the pings and reconnects, the whole difference is _where_ it reconnects14:57
bjornar_zzzeek, stil a single one, see14:57
rpodolyakaservice discovery via dns? like consul?14:57
bjornar_so when haproxy fails for some reason, you move it to a different server, and sqlalchemy is able to reconnect14:57
zzzeekbjornar_: theres a lot of things we need in this area and the current pinging it does is not really sufficient.14:58
bjornar_most of this can just be done on the tcp layer14:58
zzzeekbjornar_: the pinging needs to be asynchronous in a background thread14:58
bjornar_does not even need to know protocol14:58
zzzeekbjornar_: also, connection pooling among hundreds of independent processes is a big use case, i wanted to tackle that also14:58
zzzeekhaalchemy was going to try some very ambitious way of doing this but proxysql makes this easy, working similarly to pgbouncer14:59
bjornar_glb is probably the better option14:59
bjornar_but should not be needed anyway I think14:59
bjornar_currently we spawn pen on every container, and exposes a socket for sqlalchemy to connect to15:00
zzzeekbjornar_: please read https://bitbucket.org/zzzeek/haalchemy/src/6623f93c122f5e4ac9de208c09512699e30a76f8/docs/build/index.rst?at=master&fileviewer=file-view-default to see what i was working on.  it's hard to justify given the existence of proxysql - if the only difference is "hops"15:00
bjornar_zzzeek, the connection pooling in the application side should just be simple, I mean.. either a host listens on tcp port X so one can establish a connection, or it does not15:01
bjornar_zzzeek, this is needed even if haproxy15:01
openstackgerritJulien Danjou proposed openstack/tooz master: redis: fix concurrent access on acquire()  https://review.openstack.org/44719915:01
bjornar_then leave the complexity of figuring out if the application layer is really alive to the "proxy", and make it just not reject connections or not advertise it's ip if its not feeling well15:02
*** pblaho has quit IRC15:02
bjornar_zzzeek, in that way, it does not really have to work differently (as I said above) to how sqlalchemy currently treats a haproxy or whatever that goes down and comes up again --> only difference is that it should be able to connect to multiple ips (I dont think it even does that with dns and multiple A-records)15:04
bjornar_zzzeek, this document you provided is far too complex, and as complex projects go, they seldom get finished, and contain lots of bugs if they do15:04
bjornar_zzzeek, the main thing "we" need is beeing able to spesify multiple ip's, and have the db-layer reconnect to the next server (and some kind of hashing) if the connection is "dead"15:05
*** rcernin has quit IRC15:05
zzzeekbjornar_: the haalchemy initial versions did that on top of plain vanilla sqlalchemy, you can use a custom "connect" routine to get this behavior right now15:08
zzzeekbjornar_: the problem w/ that kind of routing for "us" is that, if a DB has been restarted, the pool has a stale connection.  it looks "dead".  but, we dont want to go to the next node in that case, we want to first test the *same* node to see if its back up15:10
zzzeekbjornar_: all of this connection testing, if you use the current "ping" in oslo.db, happens up front when someone is trying to actually make a request to do something15:10
zzzeekbjornar_: for "us" also, it's important that all applications connect to the *same* database at once.   we need coordination to make sure they are all doing the same thing15:11
*** dmsimard|afk is now known as dmsimard15:11
zzzeekif you dont need that, then you can provide a connect() routine that just connects to whichever host is up, that's a simple extension15:12
*** e0ne has joined #openstack-oslo15:13
bjornar_huh.. if you need that, you just spesify a single server, right?15:13
bjornar_I dont see the relevance15:13
bjornar_zzzeek, yeah, so thats what oslo.db should implement, I think.. connecting to multple host, a timeout value for "dead" hosts and a hashing based on whatever15:16
*** mtanino has joined #openstack-oslo15:16
bjornar_?intial_server=123415:16
bjornar_and then server = initial_server % num_servers15:17
zzzeekbjornar_: this is like a "micro" load balancer feature that serves a very narrow set of use cases.   feel free to propose a gerrit as an oslo.db feature15:18
bjornar_I dont think reconnecting on failure and exposing multiple server is a narrow use case, as it just opens possibilities that are more advanced15:19
zzzeekbjornar_: as haalchemy does, you intercept the engine's creation, the most modern way is using http://docs.sqlalchemy.org/en/latest/core/connections.html?highlight=createengineplugin#sqlalchemy.engine.CreateEnginePlugin15:19
zzzeekbjornar_: it's narrow because it doesnt allow for coordination among processes.  it only allows "everyone connects to many hosts" balancing.  it doesn't provide for, "Everyone connects to host A, then host B, atomically"15:20
zzzeekbjornar_: a proxy server OTOH can ensure everyone does the same thing15:20
bjornar_zzzeek, who would coordinate along processes and why?15:20
*** pblaho has joined #openstack-oslo15:20
zzzeekbjornar_: in our case it's because we keep all of openstack on one galera master at a time to avoid failed transactions15:21
zzzeekbjornar_: as well as replication lag15:21
bjornar_zzzeek, this can still be done with multiple ip's .. you dont need to change your proxy configuration15:21
bjornar_zzzeek, but: you can have multiple proxies doing the same thing, and faster failover, better scalability and ha15:22
*** yamahata has joined #openstack-oslo15:22
bjornar_and lets face it.. database sync is not the scalability/latency issue in openstack -- its the braindead developers writing sql ;)15:23
zzzeekbjornar_: i dont understand what "multiple ips / multiple proxies" refers to15:23
bjornar_so, currently you probably have a single haproxy instance that you send your sql queries to..15:24
zzzeekbjornar_: galera has replication lag.  it can cause failures right now15:24
bjornar_and from here you do some black-magic to keep all the connection on one galera backend15:24
bjornar_you can still do the same with multiple proxies -- the way your loadbalancing/proxy server is configured/synchronized is beyond the scope of having the ability to connect to multiple ip's15:25
bjornar_zzzeek, where is the documentation on the bug that can cause failures?15:25
zzzeekbjornar_: the ability to connect to multiple ips is unnecessary if you just use proxies15:26
*** yamamoto has joined #openstack-oslo15:26
zzzeekbjornar_: https://www.percona.com/blog/2013/03/03/investigating-replication-latency-in-percona-xtradb-cluster/15:26
bjornar_zzzeek, why do you say that?15:26
bjornar_201315:26
zzzeekbjornar_: we put the multiple database hosts behind the proxy15:26
*** tongli has quit IRC15:26
bjornar_zzzeek, sure, but why not use multiple ip's? you see the fact that loadbalancer scale and ha can be improved this way without affecting your l7 balancing15:28
bjornar_zzzeek, ask yourself: where is your spof15:28
zzzeekbjornar_: does "multiple ips" mean, "embed multiple ips in the client" like you are proposing?15:28
bjornar_sure15:29
bjornar_the client is the only place where you can do this in a scalable way without a spof15:29
zzzeekbjornar_: it is difficult to ensure that all python processes use the *same* host at exactly the same time, especially when a node fails15:29
bjornar_the client _needs_ to be able to use multiple ip's .. loadbalancer or not15:29
zzzeekbjornar_: i had it doing this using a fixed scheme15:29
zzzeekbjornar_: but it still doesnt work unless you have an asynchronous pinger15:30
bjornar_zzzeek, it it is that dangerous for you, you should have only a master/slave setup -- that stuff you say there is just plain BS15:30
*** yamamoto has quit IRC15:31
bjornar_zzzeek, so how does sqlalchemy work on proxy down today?15:31
bjornar_zzzeek, will it be any difference with multiple ip's?15:31
zzzeekbjornar_: problem.  process A is very busy.   database node 1 is stopped and restarted.  process A's pinger has stale pooled connection, it pings, sees DB as down (But its actually up again).  LB routine bounces it to database #2.  slower Python process B decides to do some work, connects to DB 1, sees nothing wrong.  the scheme has now failed15:31
bjornar_zzzeek, this is your very spesific setup15:32
zzzeekbjornar_: from my POV *you* have a very specific setup :)15:32
bjornar_zzzeek, and as I said: you do not need to connect to the database directly even if you can spesify multiple ip's15:32
zzzeekwhere you can go to any node at any time15:32
bjornar_zzzeek, the multiple ips ca all reside on a single haproxy for all I care, or synchronized haproxies that all select the same active server, or whatever you want --- out of scope for the simple fact of spesifying multiple upstream servers15:33
*** eliqiao has quit IRC15:33
bjornar_zzzeek, so having multiple  A-records for a domain is very special?15:33
zzzeekbjornar_: anyway, what you want is super easy to build.  look into CreateEnginePlugin and then set up a pool creator() function and you're good to go15:33
zzzeekbjornar_: for an internal application database connection URL, yes that's fairly uncommon15:34
zzzeekbjornar_: but also, easy to support15:36
*** eliqiao has joined #openstack-oslo15:37
bjornar_its not about the problem of building it, its the fact that it should be included in oslo.db15:38
openstackgerritMerged openstack/oslo.config master: Add HACKING.rst  https://review.openstack.org/44940915:41
zzzeekbjornar_: propose a gerrit to oslo.db.  we have that nutty NDB thing going in I am bothered a lot more by that :)15:42
zzzeekbjornar_: this only bothers me b.c. i can see people thinking it does a lot more than it does15:42
*** lpetrut has quit IRC15:42
openstackgerritChangBo Guo(gcb) proposed openstack/oslo.config master: Make method set_override's parameter enforce_type=True by default  https://review.openstack.org/32869215:43
*** chenying__ has quit IRC15:43
zzzeekbjornar_:  openstack is, "open".   if your issue is, "openstack should have feature X and *someone in openstack needs to write it for us*", that's not as much the culture :)15:43
*** chenying__ has joined #openstack-oslo15:44
zzzeekbjornar_: i will gladly +2 a well written and tested round-robin url plugin for oslo.db if that's all we're talking about15:44
*** eliqiao has quit IRC15:46
*** nkrinner is now known as nkrinner_afk15:51
bjornar_zzzeek, sure, its just about doing some basic clientside ha, what one uses it for is beyond scope15:53
*** eliqiao has joined #openstack-oslo15:53
bjornar_zzzeek, I think it's more about getting it up for discussion. I think the reasons for having it outweighs the reasons for _not_ having it.15:54
bjornar_And actually I was surprised that not sqlalchemy nor oslo.db provided this func already15:55
*** tommylikehu_ has quit IRC15:56
*** tommylikehu_ has joined #openstack-oslo15:57
*** amotoki has joined #openstack-oslo15:57
*** tesseract has quit IRC15:58
*** bjornar_ has quit IRC16:01
openstackgerritJohn Perkins proposed openstack/oslo.config master: Oslo Validator  https://review.openstack.org/38455916:01
*** amotoki has quit IRC16:03
*** e0ne has quit IRC16:06
*** e0ne has joined #openstack-oslo16:06
*** aarefiev is now known as aarefiev_afk16:08
*** dmsimard is now known as dmsimard|afk16:13
*** d0ugal has quit IRC16:17
*** Rockyg has joined #openstack-oslo16:24
*** tommylikehu_ has quit IRC16:25
*** yamamoto has joined #openstack-oslo16:27
*** yamamoto has quit IRC16:33
*** shardy has quit IRC16:35
*** e0ne has quit IRC16:38
*** lpetrut has joined #openstack-oslo16:38
*** d0ugal has joined #openstack-oslo16:38
*** d0ugal has quit IRC16:43
*** kzaitsev_ws has quit IRC16:44
*** lucasagomes is now known as lucas-afk16:49
*** pblaho has quit IRC16:50
*** yamahata has quit IRC16:50
*** shardy has joined #openstack-oslo16:52
*** amotoki has joined #openstack-oslo16:59
*** eliqiao has quit IRC17:01
*** eliqiao has joined #openstack-oslo17:02
openstackgerritMerged openstack/oslo.messaging master: [zmq] pass a dummy TransportURL to register_opts  https://review.openstack.org/44917217:03
*** amotoki has quit IRC17:04
*** pblaho has joined #openstack-oslo17:07
*** links has joined #openstack-oslo17:07
*** lpetrut has quit IRC17:07
*** sambetts is now known as sambetts|afk17:11
*** yamahata has joined #openstack-oslo17:13
*** links has quit IRC17:19
*** jpena is now known as jpena|off17:20
*** lpetrut has joined #openstack-oslo17:21
openstackgerritMerged openstack/oslo.messaging master: Fix simulator's use of Notifier - use 'topics' not 'topic'  https://review.openstack.org/44755917:22
*** yamamoto has joined #openstack-oslo17:29
*** bjornar_ has joined #openstack-oslo17:32
*** yamamoto has quit IRC17:35
openstackgerritJohn Perkins proposed openstack/oslo.config master: Oslo Validator  https://review.openstack.org/38455917:37
*** mtanino has quit IRC17:40
*** e0ne has joined #openstack-oslo17:42
openstackgerritMerged openstack/tooz master: tests: tests fail if no URL is set + run partitioner tests on basic drivers  https://review.openstack.org/44856817:44
*** eliqiao has quit IRC17:49
*** eliqiao has joined #openstack-oslo17:50
*** pcaruana has quit IRC17:52
*** e0ne has quit IRC17:53
*** lpetrut has quit IRC18:00
*** dtardivel has quit IRC18:00
*** amotoki has joined #openstack-oslo18:00
*** amotoki has quit IRC18:05
*** bjornar_ has quit IRC18:08
*** mtanino has joined #openstack-oslo18:09
openstackgerritMerged openstack/tooz master: redis: fix concurrent access on acquire()  https://review.openstack.org/44719918:12
*** yamamoto has joined #openstack-oslo18:31
*** yamamoto has quit IRC18:36
*** openstackstatus has joined #openstack-oslo18:45
*** ChanServ sets mode: +v openstackstatus18:45
*** e0ne has joined #openstack-oslo18:50
*** gordc has quit IRC18:59
*** amotoki has joined #openstack-oslo19:01
openstackgerritSean Dague proposed openstack/oslo.log master: WIP: this is all the hackiest hackness of systemd integration  https://review.openstack.org/45152519:02
*** amotoki has quit IRC19:05
*** e0ne has quit IRC19:06
*** Guest16838 has quit IRC19:14
openstackgerritStephen Finucane proposed openstack/oslo.config master: generator: Support outputting in JSON format  https://review.openstack.org/45152919:15
*** david-lyle has quit IRC19:19
*** david-lyle has joined #openstack-oslo19:19
*** Guest16838 has joined #openstack-oslo19:25
*** bjornar_ has joined #openstack-oslo19:26
*** david-lyle has quit IRC19:27
*** eliqiao has quit IRC19:28
*** david-lyle has joined #openstack-oslo19:30
*** yamamoto has joined #openstack-oslo19:32
*** openstackgerrit has quit IRC19:33
*** jamielennox|away is now known as jamielennox19:33
*** eliqiao has joined #openstack-oslo19:33
*** yamamoto has quit IRC19:38
*** syjulian has quit IRC19:44
*** d0ugal has joined #openstack-oslo19:49
*** d0ugal has quit IRC20:00
*** amotoki has joined #openstack-oslo20:02
*** amotoki has quit IRC20:06
*** dimtruck is now known as zz_dimtruck20:21
*** openstackgerrit has joined #openstack-oslo20:26
openstackgerritSean Dague proposed openstack/oslo.log master: WIP: this is all the hackiest hackness of systemd integration  https://review.openstack.org/45152520:26
*** Guest6666 has quit IRC20:28
*** Guest6666 has joined #openstack-oslo20:29
*** ansmith has quit IRC20:32
*** david-lyle has quit IRC20:33
*** yamamoto has joined #openstack-oslo20:34
*** david-lyle has joined #openstack-oslo20:35
*** yamamoto has quit IRC20:40
*** david-lyle has quit IRC20:40
*** zz_dimtruck is now known as dimtruck20:42
*** david-lyle has joined #openstack-oslo20:42
*** david-lyle has quit IRC20:46
*** david-lyle has joined #openstack-oslo20:52
*** syjulian has joined #openstack-oslo20:58
*** amotoki has joined #openstack-oslo21:02
*** amotoki has quit IRC21:07
*** kgiusti has left #openstack-oslo21:15
*** ihrachys has quit IRC21:26
*** ansmith has joined #openstack-oslo21:33
*** yamamoto has joined #openstack-oslo21:36
*** bjornar_ has quit IRC21:36
openstackgerritJohn Perkins proposed openstack/oslo.config master: Oslo Validator  https://review.openstack.org/38455921:37
*** dimtruck is now known as zz_dimtruck21:41
*** yamamoto has quit IRC21:42
*** dmitryme has quit IRC21:43
*** DinaBelova has quit IRC21:44
*** Guest16838 has quit IRC21:45
*** dmitryme has joined #openstack-oslo21:46
*** DinaBelova has joined #openstack-oslo21:46
*** Guest16838 has joined #openstack-oslo21:47
*** shardy has quit IRC21:50
*** erlon has quit IRC21:55
*** boden has quit IRC22:00
*** amotoki has joined #openstack-oslo22:03
*** bjornar_ has joined #openstack-oslo22:06
*** amotoki has quit IRC22:08
*** jamielennox is now known as jamielennox|away22:09
*** jamielennox|away is now known as jamielennox22:12
*** zz_dimtruck is now known as dimtruck22:17
*** yamamoto has joined #openstack-oslo22:38
*** bjornar_ has quit IRC22:42
*** yamamoto has quit IRC22:42
*** sdague has quit IRC22:46
*** tommylikehu_ has joined #openstack-oslo22:51
*** tommylikehu_ has quit IRC22:56
*** amotoki has joined #openstack-oslo23:04
*** tommylikehu_ has joined #openstack-oslo23:06
*** kornica has joined #openstack-oslo23:06
*** kornicameister has quit IRC23:08
*** amotoki has quit IRC23:09
*** tommylikehu_ has quit IRC23:10
*** yamamoto has joined #openstack-oslo23:39
*** yamamoto has quit IRC23:44
*** hieulq has quit IRC23:47
openstackgerritMerged openstack/oslo.config master: Use Sphinx 1.5 warning-is-error  https://review.openstack.org/44658923:49

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