Monday, 2019-02-25

*** ansmith has joined #openstack-oslo00:15
*** ansmith has quit IRC00:33
*** threestrands has joined #openstack-oslo01:10
*** dave-mccowan has joined #openstack-oslo01:29
*** dave-mccowan has quit IRC01:35
*** threestrands has quit IRC01:35
*** dave-mccowan has joined #openstack-oslo02:24
*** dave-mccowan has quit IRC02:53
openstackgerritMerged openstack/oslo.messaging stable/pike: Add release note for amqp library TLS/SSL error  https://review.openstack.org/63873503:42
openstackgerritMerged openstack/oslo.service master: Update oslo.service to require yappi 1.0 or newer  https://review.openstack.org/63848905:27
*** larainema has quit IRC06:02
*** Luzi has joined #openstack-oslo06:51
*** aojea has joined #openstack-oslo07:20
*** takamatsu_ has quit IRC08:19
*** takamatsu_ has joined #openstack-oslo08:21
*** takamatsu_ has quit IRC08:32
*** takamatsu_ has joined #openstack-oslo08:38
*** hberaud|gone has quit IRC08:44
*** e0ne has joined #openstack-oslo08:51
*** tosky has joined #openstack-oslo08:55
*** giblet is now known as gibi08:55
*** rcernin has quit IRC09:00
*** hberaud has joined #openstack-oslo09:00
*** hberaud has quit IRC09:06
*** hberaud has joined #openstack-oslo09:06
*** shardy has joined #openstack-oslo09:08
*** shardy has quit IRC09:23
*** shardy has joined #openstack-oslo09:23
*** a-pugachev has joined #openstack-oslo09:40
*** sambetts_ has quit IRC10:28
*** sambetts_ has joined #openstack-oslo10:30
*** jaosorior has joined #openstack-oslo10:37
*** cdent has joined #openstack-oslo10:43
*** trident has quit IRC10:47
*** trident has joined #openstack-oslo10:50
openstackgerritColleen Murphy proposed openstack/oslo.policy master: Add py36 and py37 tox envs  https://review.openstack.org/63906011:11
openstackgerritColleen Murphy proposed openstack/oslo.limit master: Add py36 and py37 tox envs  https://review.openstack.org/63906311:14
*** snapiri has quit IRC11:23
*** ansmith has joined #openstack-oslo11:34
*** finucannot is now known as stephenfin11:40
*** ansmith has quit IRC11:46
*** hberaud is now known as hberaud|lunch12:01
*** raildo has joined #openstack-oslo12:07
*** moguimar has joined #openstack-oslo12:13
*** cdent has quit IRC12:17
*** njohnston has joined #openstack-oslo12:31
*** cdent has joined #openstack-oslo12:34
*** e0ne has quit IRC12:47
*** hberaud|lunch is now known as hberaud13:07
*** ansmith has joined #openstack-oslo13:15
*** e0ne has joined #openstack-oslo13:35
*** snapiri has joined #openstack-oslo13:37
*** elbragstad has joined #openstack-oslo14:01
*** mmethot has joined #openstack-oslo14:03
*** dave-mccowan has joined #openstack-oslo14:07
moguimarbeekneemech: around?14:12
moguimararen't the items in today's agenda from last week?14:12
*** a-pugachev has quit IRC14:33
*** kgiusti has joined #openstack-oslo14:40
*** cdent has quit IRC14:53
sean-k-mooneyo/15:01
sean-k-mooneydhellmann: can i get your input on a posible future oslo.preivsep change it want to do in train15:02
sean-k-mooneyin os-vif we do not allow eventlet's to be a runtime depency.15:02
sean-k-mooneybut in our test code we have to cat eventlet.Timeout exceptions15:03
sean-k-mooneyhttps://github.com/openstack/os-vif/blob/master/os_vif/tests/functional/base.py#L44-L5115:03
sean-k-mooneyfrom privsep15:03
*** e0ne has quit IRC15:03
sean-k-mooneydo you think we could intoduce a privsep timeout instead in a future privsep version?15:03
openstackgerritAndy Smith proposed openstack/oslo.messaging master: Update messaging intermediaries for amqp1 tests  https://review.openstack.org/62507715:04
sean-k-mooneyi belive the hope is we can swap to asio in U when we drop py27 support so having a privsep.Timeout excpetion class woudl help smooth that transition also15:04
dhellmannsean-k-mooney: that makes sense to me, although I'm not sure how we'd implement it safely without subclassing it from the eventlet class. maybe that's good enough?15:05
*** e0ne has joined #openstack-oslo15:05
sean-k-mooneyeffectivly i think this is a leaky abstration. am i could play with subclassing and see15:05
dhellmannin order to maintain backwards compatibility someone catching the existing exception would also have to catch the new one15:05
sean-k-mooneywell if we did it in two cycles we could subclass in train and try and get people to move over to catching the privsep class15:07
sean-k-mooneyat that point we can decouple the privsep class if and when we choose15:07
sean-k-mooneyit would solve the os-vif usecase in any case.15:08
sean-k-mooneydhellmann: one final question then. should i file this as a bug or blueprint/spec?15:08
dhellmannsure, but we need that 2 step approach15:08
dhellmannthe second step is a lot bigger than the first, so...15:08
dhellmanntracking is up to beekneemech15:09
dhellmannwe're usually pretty lightweight15:09
dhellmannI'd start a mailing list thread, at least, though15:09
sean-k-mooneywell if we do step 1 i can remove eventlet form the test depencies15:09
sean-k-mooneyso that will make me happy15:09
dhellmannprivsep will still pull it in, right?15:10
sean-k-mooneysure i can post to the ml15:10
sean-k-mooneyyep15:10
sean-k-mooneyos-vif is also invoked form nova and soon neutron from a deamon that uses eventlets15:10
sean-k-mooneyi just dont want an explict depency in the os-vif code15:10
sean-k-mooneyif i could i would remove eventlest form the nova compute agent and neutron l2 agents but im not going to open that can of worms untill at least U15:12
*** zaneb has joined #openstack-oslo15:12
dhellmannmaybe that can be part of the "let's just have one agent" project15:13
*** Luzi has quit IRC15:13
sean-k-mooneymaybe. if that does every become a thing i think its an opertunity to remove some depencies like eventlets that have standard lib alternitives in python 315:14
sean-k-mooneyanyway thanks for sanity checking this idea/request :)15:15
dhellmannany time!15:16
openstackgerritKen Giusti proposed openstack/oslo.messaging stable/queens: Mark telemetry tests nv and remove from gate  https://review.openstack.org/63912615:16
*** beekneemech is now known as bnemec15:21
bnemec#startmeeting oslo15:22
openstackMeeting started Mon Feb 25 15:22:45 2019 UTC and is due to finish in 60 minutes.  The chair is bnemec. Information about MeetBot at http://wiki.debian.org/MeetBot.15:22
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:22
*** openstack changes topic to " (Meeting topic: oslo)"15:22
openstackThe meeting name has been set to 'oslo'15:22
bnemeccourtesy ping for amotoki, amrith, ansmith, bnemec, dansmith, dhellmann, dims15:23
bnemeccourtesy ping for dougwig, e0ne, electrocucaracha, flaper87, garyk, gcb, haypo15:23
bnemeccourtesy ping for hberaud, jd__, johnsom, jungleboyj, kgiusti, kragniz, lhx_15:23
bnemeccourtesy ping for moguimar, njohnston, raildo, redrobot, sileht, sreshetnyak, stephenfin15:23
bnemeccourtesy ping for stevemar, therve, thinrichs, toabctl, zhiyan, zxy, zzzeek15:23
moguimaro/15:23
bnemec#link https://wiki.openstack.org/wiki/Meetings/Oslo#Agenda_for_Next_Meeting15:23
hberaudo/15:23
kgiustio/15:23
bnemecApologies for being late. I forgot that my appointment this morning overlapped this meeting.15:23
ansmitho/15:23
jungleboyjo/15:23
dhellmanno/15:23
jungleboyjbnemec:  Were you able to get to your appointment?15:23
bnemecjungleboyj: Days like today are why I have a 4x4 truck. :-)15:24
bnemecBut yeah, it's post-snowpocalyptic out there.15:24
stephenfino/15:24
bnemecAbandoned cars everywhere and stuff.15:24
jungleboyj:-)  I have just decided not to tempt fate and am hiding at home.15:24
jungleboyjbnemec:  I heard that.15:24
bnemecYeah, it figures that the one day I have to go out is today. :-)15:25
bnemec#topic Red flags for/from liaisons15:25
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"15:25
bnemecOther than red flag wind warnings. :-)15:25
jungleboyjNothing from Cinder.15:26
bnemecI guess from our side, there's the amqp 2.4.1 bump.15:26
bnemecIf you're running oslo.messaging with ssl to rabbit, you very much want amqp 2.4.1.15:27
bnemecThat goes back to pike, but we can't backport the requirements change.15:27
bnemecWe'll be release noting it too, but I'm trying to publicize the change as much as possible.15:27
bnemecAlso, oslo.cache is currently broken, but I think it's unit tests only.15:28
bnemecI'll be taking a look at hberaud's change to fix that today.15:28
hberaudyeah due to https://github.com/sqlalchemy/dogpile.cache/commit/7e8d9b0a2eb552adb6734c8570c63eb6ea2e3a7a15:28
bnemec#action bnemec to look at hberaud's oslo.cache fix15:28
bnemecAnyone else is welcome to also.15:28
hberaudmy fix is under WIP yet15:28
hberaudbut I know why the problem occure15:29
bnemecOkay, so more to do there, and keep that in mind if you're trying to get a patch in to oslo.cache.15:29
bnemecAlthough we're past feature freeze, so that's less likely.15:30
bnemecI know we had the python 3 bug in that library too, which we'll need to discuss once we unblock the gate.15:30
bnemecOkay, lots of red flags this week, actually. :-/15:31
bnemec#topic Releases15:32
*** openstack changes topic to "Releases (Meeting topic: oslo)"15:32
bnemecWill do the normal releases today.15:32
bnemecIdeally this will be the last set with any feature releases this cycle.15:32
bnemecAlthough we may have to make an exception for the oslo.cache bug, but we'll cross that bridge when we come to it.15:32
bnemecmoguimar: I believe the new castellan should be released now.15:33
moguimarok, thanks bnemec15:33
bnemecI know you the barbican team was asking about that last week.15:33
bnemecs/you//15:33
*** zaneb has quit IRC15:33
bnemec#topic Action items from last meeting15:34
*** openstack changes topic to "Action items from last meeting (Meeting topic: oslo)"15:34
bnemecSpeaking of which...15:34
bnemec"bnemec to release castellan"15:34
bnemecDone15:34
bnemec"bnemec send email to openstack-discuss about Oslo feature freeze"15:34
bnemecDone15:34
bnemec"Oslo team perform technical vision evaluation"15:34
bnemecNot done. :-(15:34
bnemecI'll leave it on my todo list though.15:35
bnemec"kgiusti to investigate connection explosion related to get_transport_url"15:35
*** elbragstad is now known as lbragstad15:35
kgiustibnemec: it was recommended to adopt the singleton pattern used by other projects15:35
bnemeckgiusti: Okay, did we have documentation of that?15:36
kgiustibnemec: nope.15:36
kgiustibnemec: #action kgiusti document singleton pattern15:36
kgiusti#action kgiusti document singleton pattern15:37
kgiusti?15:37
bnemecThat should do it.15:37
bnemecNot sure whether the bot will have picked up the one addressed to me.15:37
bnemeckgiusti: Thanks15:37
kgiustibnemec: we should consider integrating that pattern into the library itself15:37
kgiustibnemec: for train15:37
bnemecYep, that would be a good followup.15:38
bnemecThat was it for action items from last week.15:38
bnemec#topic Oslo Feature Freeze15:39
*** openstack changes topic to "Oslo Feature Freeze (Meeting topic: oslo)"15:39
bnemecWe're now officially in feature freeze for Oslo.15:39
bnemecAs I mentioned, hopefully the releases I submit today will be the last feature ones for the cycle.15:39
bnemecBut we can discuss FFE's as needed.15:40
*** agopi has quit IRC15:40
bnemecSo in general, cores please don't merge anything feature-y without discussing it with me first.15:40
bnemecIf we merge a feature without an FFE it will just block releasing that library.15:41
bnemecI think we have an experienced enough core team that we shouldn't need to procedural -2 everything.15:42
bnemecAt least that's my hope because I'd rather not spend the time to do that. :-)15:42
jungleboyjYou get a -2 and you get a -2!15:42
bnemecEveryone gets a -2!15:42
jungleboyjYay!15:42
bnemecThe other topics on the agenda were addressed last week, so I think that's it for those.15:43
bnemec#topic Weekly Wayward Review15:43
*** openstack changes topic to "Weekly Wayward Review (Meeting topic: oslo)"15:43
moguimarI think this is the first feature freeze I'm seeing from a closer distance15:43
moguimarso we should hold +2 and +w?15:44
bnemecmoguimar: +2 is okay, but don't +w anything that would trigger a feature release.15:45
* bnemec grabs a link to the release criteria...15:45
moguimarok15:45
bnemec#link https://releases.openstack.org/reference/using.html#using-new-release-command15:46
*** a-pugachev has joined #openstack-oslo15:46
bnemecIn general we follow semver, but that provides a short description of each release type that I find useful.15:46
bnemecFor wayward reviews, we obviously have a more limited set because of feature freeze.15:46
bnemecBut I think we can probably do this one:15:46
bnemec#link https://releases.openstack.org/reference/using.html#using-new-release-command15:47
bnemecBleh.15:47
bnemec#link https://review.openstack.org/#/c/62537215:47
bnemecOh, I see stephenfin asked for a reno on that.15:48
bnemechberaud: Since you already kind of adopted that one, would you be able to write a reno?15:49
hberaudbnemec: yeah15:49
bnemechberaud: Great, thanks!15:49
moguimardoes it needs a release note?15:49
* moguimar wrote his first release note on openstack last week =D15:50
moguimarcastellan folks made me do it15:50
bnemecI would think that either a reno or lp bug would be good for discoverability.15:50
bnemecI don't know that our git commit messages are SEO'd especially well. :-)15:51
bnemecI personally wouldn't require both.15:51
moguimar+1 for the lp15:51
bnemecstephenfin was the one who asked, so maybe he can weigh in too.15:52
* stephenfin checks15:52
hberaudI'll create the lp15:53
stephenfinIt doesn't need a reno, but for a user facing tool like this it is mighty helpful15:53
hberaudstephenfin: +115:53
stephenfinHelps with discoverability of these issues (user: "why is X happening", user -> Google)15:54
bnemecYeah15:54
bnemecThe reno could be pretty brief since it can reference the lp for details.15:55
bnemecOkay, I marked that one WIP. That should get cleared when a new patch set is pushed so we'll know to look again.15:57
bnemec#topic Open discussion15:57
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"15:57
bnemecAnything else for this week?15:57
moguimaryep15:58
moguimarI was checking open changes and found this one15:58
moguimarhttps://review.openstack.org/#/c/61011115:58
moguimarso it basically updates .zuul.d/project.yaml and tox.ini15:58
moguimarthe current state of project.yaml tests py35 py36 and py3715:59
moguimardo we have any best practices for that cross projects?15:59
johnsomSorry I missed the liaison section, but wanted to follow up on the oslo.service /yappi issue we had.15:59
moguimarlike, when are we suposed to add py38 and frop 35?16:00
bnemecmoguimar: We may need to discuss this on the list again. I looked when I approved all of the py37 changes last week, and the previous conclusion was that we would drop py35 and add py37 this cycle.16:00
bnemecBut I'm not clear that we ever actually dropped py35.16:00
moguimarand is it better to keep the tox.ini one in the lower one (3.5) until it gets deprecated to make it fail fast during dev?16:00
johnsomI think it is all resolved now, but that oslo.service release broke all of our live test gates. Luckily I was able to reach the yappi developer and he was willing to cut a new release of yappi with the fix.16:00
bnemecAnd I'm idly tempted to say we should wait to drop things until next cycle.16:01
moguimarI like having the last 3 versions as it is right now16:01
bnemecI guess dropping py35 is pretty safe since it isn't going to break the gate, but I think we should clarify our support stance.16:01
bnemecjohnsom: Yeah, that's weird. I would have expected a problem like that to get caught in the gate since it happened on installation of the lib.16:02
moguimarok, I'll create some WIP on that and we can push it forward16:02
johnsomYeah, me too. Not sure what the magic combination was that triggered it for DIB installs16:02
gsantomaggioI am looking how Open Stack does use RabbitMQ,16:04
gsantomaggioI found this HA policy:16:04
gsantomaggiohttps://git.openstack.org/cgit/openstack/openstack-ansible-rabbitmq_server/tree/defaults/main.yml#n15416:04
gsantomaggioIf I am not wrong, open stack does not use the autodelete queues anymore.16:04
gsantomaggioIt works using queues with TTL, right?16:04
gsantomaggioSo, this policy should be changed from '^(?!amq\.).*'  to '^(?!reply_\.).*'16:04
gsantomaggioWhat do you think?16:04
bnemecmoguimar: Sounds good. Let me find the mailing list thread where this was first discussed. I think we should probably reopen that.16:04
moguimarok16:05
kgiustigsantomaggio: quite possibly - let me take a look16:06
bnemecjohnsom: Weirdly, it never broke our gate. I see passing test jobs that used .99: http://logs.openstack.org/88/637688/1/check/openstack-tox-py36/0b4045f/job-output.txt.gz#_2019-02-20_00_50_27_98895416:06
gsantomaggio@kgiusti thanks16:06
bnemecMaybe dib does something different with the encoding that tripped up the pip install?16:07
*** zaneb has joined #openstack-oslo16:07
johnsombnemec Agreed. They had a bug and patch for it already. No idea how/what caused it to fail to install. It was a xenial image, nothing special.16:07
bnemecOh, that's right. Someone else actually reported it first.16:08
bnemecmoguimar: Okay, this actually goes back to the openstack-dev days: http://lists.openstack.org/pipermail/openstack-dev/2018-October/135626.html16:08
bnemec#action moguimar to follow up on status of py35 in the gate16:09
moguimarthanks16:10
bnemecjohnsom: Do you have any proposed actions to take to avoid this in the future?16:10
openstackgerritHervé Beraud proposed openstack-dev/pbr master: Resolve ``ValueError`` when mapping value contains a literal ``=``.  https://review.openstack.org/62537216:11
johnsombnemec I would if I knew what the trigger was, but I don't. They py2 and 3 gates should have caught it.16:11
bnemecjohnsom: Well, at least now we have a known-working version so we can add version exclusions if it happens again.16:12
johnsomYeah, it's fixed and released on the yappi side. I have added the blacklist on yappi in g-r, so we should be good.16:12
bnemec#action kgiusti and gsantomaggio to investigate OSA rabbitmq_policies16:13
bnemecI think that covers all of the topics so far in open discussion.16:14
bnemecI'll take this opportunity to note that anyone can add items to the agenda, so if you have something to discuss please feel free. :-)16:14
bnemecAnything else before we end?16:15
moguimarnot on my end16:15
gsantomaggioNope :)!16:15
bnemecThanks for joining everyone!16:17
bnemecShould be back to normal schedule next week.16:17
bnemec#endmeeting16:17
*** openstack changes topic to "OpenStack Common Libraries | https://wiki.openstack.org/wiki/Oslo"16:17
openstackMeeting ended Mon Feb 25 16:17:11 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:17
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2019/oslo.2019-02-25-15.22.html16:17
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2019/oslo.2019-02-25-15.22.txt16:17
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2019/oslo.2019-02-25-15.22.log.html16:17
kgiustigsantomaggio: I think you are correct in that those 'reply_' queues should probably be configured with a ttl16:21
gsantomaggioI think that also  'reply_' queues should not be mirrored16:22
kgiustigsantomaggio: I'm no rabbitmq HA expert - is there any advantage to mirroring single consumer queues?16:25
*** e0ne has quit IRC16:26
gsantomaggioNothing, it is only a waste of resources16:26
gsantomaggiothis is why I think we should exclude reply_ queues from the mirror16:26
kgiustigsantomaggio: In general I think RPC is a best effort message QOS.  Mirroring/persisting such messages seems overkill to me.16:27
gsantomaggio> Mirroring/persisting such messages seems overkill to me.16:27
gsantomaggioWe are in the same path :)16:27
gsantomaggiothis is why I am suggesting to *remove* the reply_ queues fro mirror policies16:28
*** agopi has joined #openstack-oslo16:28
kgiustiThen we are in agreement!16:28
gsantomaggioI will prepare a PR.16:29
kgiustigsantomaggio: +1 great!16:30
*** e0ne has joined #openstack-oslo16:31
*** takamatsu_ has quit IRC16:39
*** aojea has quit IRC16:39
*** takamatsu_ has joined #openstack-oslo16:41
openstackgerritKen Giusti proposed openstack/oslo.messaging master: Explain why Listener connections cannot be pooled  https://review.openstack.org/63915216:41
*** takamatsu_ has quit IRC16:45
*** takamatsu_ has joined #openstack-oslo16:51
gsantomaggio> So, a connection cannot be shared between thread/greenthread and16:52
gsantomaggioBy default the connections are thread safe, the channel is not thread safe in RabbitMQ16:52
gsantomaggio( using the standard clients you can use the same connection to send and receive messages using different channels )16:52
gsantomaggioI think this a limitation from the kombu, right?16:53
kgiustigsantomaggio: I never understood the need to create a dedicated connection for every consumer.16:54
gsantomaggioI am reading https://review.openstack.org/#/c/639152/1/oslo_messaging/_drivers/common.py16:54
kgiustigsantomaggio: it may be due to the threading of oslo.messaging itself.16:55
gsantomaggio>I never understood the need to create a dedicated connection for every consumer.16:55
gsantomaggioin general is not the best practice16:55
kgiustigsantomaggio: agreed - it's a waste of resources.16:55
gsantomaggioespecially because, open stack creates and destroy connections  continuously, so we should create and destroy channels istead of connection.16:59
gsantomaggioit is a cheap operation and very fast, I think we could drastically drop the number of the connections :)16:59
kgiustigsantomaggio: that would help scaling up clients significantly17:00
gsantomaggioand it would avoid problems as TIME_WAIT sockets, file descriptors problems etc17:01
gsantomaggioI have to study Kombu and py-amqp17:02
gsantomaggionever used before :)17:02
kgiustigsantomaggio: be careful - you may become our resident rabbitmq expert :)17:04
*** takamatsu_ has quit IRC17:06
*** takamatsu_ has joined #openstack-oslo17:07
gsantomaggio:)17:11
*** e0ne has quit IRC17:18
*** takamatsu_ has quit IRC17:21
*** takamatsu_ has joined #openstack-oslo17:22
*** takamatsu_ has quit IRC17:25
openstackgerritMerged openstack/oslo.versionedobjects master: Allow lists to be generated from any non-string iterable  https://review.openstack.org/63738917:29
*** a-pugachev has quit IRC17:29
*** takamatsu_ has joined #openstack-oslo17:31
openstackgerritHervé Beraud proposed openstack/oslo.cache master: fix dogpile.cache issue due to the new usage of decorate in the lib  https://review.openstack.org/63878817:37
openstackgerritMerged openstack/oslo.messaging stable/rocky: Add release note for amqp library TLS/SSL error  https://review.openstack.org/63846117:40
openstackgerritHervé Beraud proposed openstack/oslo.cache master: fix dogpile.cache issue due to the new usage of decorate in the lib  https://review.openstack.org/63878817:44
openstackgerritHervé Beraud proposed openstack/oslo.cache master: fix dogpile.cache issue due to the new usage of decorate in the lib  https://review.openstack.org/63878817:46
*** takamatsu_ has quit IRC17:46
*** takamatsu_ has joined #openstack-oslo17:48
*** hberaud is now known as hberaud|gone17:49
*** takamatsu_ has quit IRC18:05
*** takamatsu_ has joined #openstack-oslo18:10
*** njohnston has quit IRC18:13
*** takamatsu_ has quit IRC18:14
*** shardy has quit IRC18:18
*** takamatsu_ has joined #openstack-oslo18:20
*** bnemec has quit IRC18:40
*** e0ne has joined #openstack-oslo18:44
*** bnemec has joined #openstack-oslo18:45
*** takamatsu_ has quit IRC18:50
*** takamatsu_ has joined #openstack-oslo18:56
*** njohnston has joined #openstack-oslo19:00
*** ansmith has quit IRC19:07
openstackgerritMerged openstack/oslo.limit master: Add python3.7 job on Stein+  https://review.openstack.org/61064119:16
openstackgerritHervé Beraud proposed openstack/oslo.cache master: Fix memcache issue due to the __new__ attribute reassign.  https://review.openstack.org/63445720:27
* bnemec shakes his fist at the zmq unit tests20:55
*** dkehn has joined #openstack-oslo20:58
*** agopi has quit IRC20:58
*** agopi has joined #openstack-oslo20:59
*** agopi_ has joined #openstack-oslo21:07
*** raildo has quit IRC21:09
*** agopi has quit IRC21:10
*** agopi__ has joined #openstack-oslo21:13
*** agopi_ has quit IRC21:16
*** agopi__ is now known as agopi21:16
*** e0ne has quit IRC21:21
*** kgiusti has left #openstack-oslo21:32
*** rcernin has joined #openstack-oslo21:46
*** e0ne has joined #openstack-oslo21:54
*** e0ne has quit IRC21:55
*** agopi has quit IRC22:00
*** e0ne has joined #openstack-oslo22:05
*** e0ne has quit IRC22:08
*** agopi has joined #openstack-oslo22:19
openstackgerritMerged openstack-dev/pbr master: Resolve ``ValueError`` when mapping value contains a literal ``=``.  https://review.openstack.org/62537222:43

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