Friday, 2018-12-21

*** macza has quit IRC00:01
*** jamesmcarthur has joined #openstack-meeting00:04
*** _alastor_ has quit IRC00:06
*** jamesmcarthur has quit IRC00:08
*** tetsuro has joined #openstack-meeting00:09
*** tpsilva has joined #openstack-meeting00:09
*** baojg has quit IRC00:14
*** rtjure has quit IRC00:14
*** Swami has quit IRC00:16
*** bobh has joined #openstack-meeting00:17
*** bobh has quit IRC00:22
*** rtjure has joined #openstack-meeting00:22
*** hongbin has quit IRC00:24
*** bobh has joined #openstack-meeting00:27
*** liuyulong_zzz has quit IRC00:34
*** Liang__ has joined #openstack-meeting00:42
*** jamesmcarthur has joined #openstack-meeting00:50
*** imacdonn has quit IRC01:03
*** imacdonn has joined #openstack-meeting01:03
*** jamesmcarthur has quit IRC01:04
*** mriedem has quit IRC01:20
*** jamesmcarthur has joined #openstack-meeting01:35
*** armstrong has joined #openstack-meeting01:36
*** jamesmcarthur has quit IRC01:42
*** armstrong has quit IRC01:43
*** armstrong has joined #openstack-meeting01:43
*** armstrong has quit IRC01:51
*** armstrong has joined #openstack-meeting01:53
*** armax has quit IRC01:59
*** gyee has quit IRC01:59
*** hongbin has joined #openstack-meeting02:00
*** tpsilva has quit IRC02:19
*** mhen has quit IRC02:21
*** mhen has joined #openstack-meeting02:22
*** jamesmcarthur has joined #openstack-meeting02:32
*** armstrong has quit IRC02:36
*** jamesmcarthur has quit IRC03:03
*** jamesmcarthur has joined #openstack-meeting03:06
*** _alastor_ has joined #openstack-meeting03:10
*** _alastor_ has quit IRC03:15
*** psachin has joined #openstack-meeting03:20
*** jamesmcarthur has quit IRC03:24
*** jamesmcarthur has joined #openstack-meeting03:25
*** iyamahat has joined #openstack-meeting03:31
*** jamesmcarthur has quit IRC03:48
*** jamesmcarthur has joined #openstack-meeting03:48
*** lbragstad has quit IRC03:52
*** bobh has quit IRC03:55
*** jamesmcarthur has quit IRC04:37
*** jamesmcarthur has joined #openstack-meeting04:39
*** janki has joined #openstack-meeting04:44
*** jamesmcarthur has quit IRC04:51
*** jamesmcarthur has joined #openstack-meeting05:00
*** sambetts_ has quit IRC05:00
*** sambetts_ has joined #openstack-meeting05:02
*** jamesmcarthur has quit IRC05:05
*** vishalmanchanda has joined #openstack-meeting05:11
*** jamesmcarthur has joined #openstack-meeting05:32
*** jamesmcarthur has quit IRC05:38
*** jamesmcarthur has joined #openstack-meeting05:39
*** Douhet has left #openstack-meeting05:40
*** jamesmcarthur has quit IRC05:43
*** hongbin has quit IRC05:55
*** tetsuro has quit IRC06:15
*** psachin has quit IRC06:16
*** psachin has joined #openstack-meeting06:37
*** janki has quit IRC06:38
*** sridharg has joined #openstack-meeting06:47
*** tetsuro has joined #openstack-meeting06:55
*** slaweq has joined #openstack-meeting07:02
*** aojea has joined #openstack-meeting07:09
*** _alastor_ has joined #openstack-meeting07:11
*** rcernin has quit IRC07:16
*** _alastor_ has quit IRC07:16
*** radeks has joined #openstack-meeting07:23
*** radeks has quit IRC07:28
*** radeks has joined #openstack-meeting07:31
*** e0ne has joined #openstack-meeting07:39
*** kopecmartin|off is now known as kopecmartin07:55
*** ralonsoh has joined #openstack-meeting08:17
*** pcaruana has joined #openstack-meeting08:19
*** e0ne_ has joined #openstack-meeting08:29
*** e0ne_ has quit IRC08:33
*** e0ne__ has joined #openstack-meeting08:33
*** e0ne has quit IRC08:33
*** dmellado has quit IRC08:44
*** dmellado has joined #openstack-meeting08:46
*** janki has joined #openstack-meeting08:56
*** e0ne__ has quit IRC09:03
*** e0ne has joined #openstack-meeting09:04
*** e0ne has quit IRC09:05
*** e0ne_ has joined #openstack-meeting09:05
*** psachin has quit IRC09:11
*** ttsiouts has joined #openstack-meeting09:18
*** tetsuro has quit IRC09:24
*** psachin has joined #openstack-meeting09:29
*** gmann is now known as gmann_pto09:43
*** browny_ has joined #openstack-meeting09:56
*** ssbarnea has joined #openstack-meeting10:14
*** e0ne_ has quit IRC10:18
*** e0ne has joined #openstack-meeting10:18
*** Liang__ has quit IRC10:34
*** ttsiouts has quit IRC10:58
*** ttsiouts has joined #openstack-meeting10:59
*** cheng1 has joined #openstack-meeting10:59
*** ttsiouts has quit IRC11:03
*** _alastor_ has joined #openstack-meeting11:13
*** _alastor_ has quit IRC11:18
*** ygbo has joined #openstack-meeting11:26
*** raildo has joined #openstack-meeting12:02
*** ttsiouts has joined #openstack-meeting12:12
*** ttsiouts has quit IRC12:17
*** erlon has joined #openstack-meeting12:36
*** e0ne has quit IRC12:37
*** e0ne has joined #openstack-meeting12:49
*** bobh has joined #openstack-meeting12:57
*** liuyulong has joined #openstack-meeting13:03
*** e0ne has quit IRC13:04
*** erlon has quit IRC13:08
*** kailun has joined #openstack-meeting13:10
*** e0ne has joined #openstack-meeting13:11
*** cheng1 has quit IRC13:18
*** cheng1 has joined #openstack-meeting13:41
*** mriedem has joined #openstack-meeting13:44
*** psachin has quit IRC13:53
*** mlavalle has joined #openstack-meeting13:56
*** lbragstad has joined #openstack-meeting13:58
*** nicky0419 has joined #openstack-meeting13:59
*** nicky0419_ has joined #openstack-meeting13:59
mlavalle#startmeeting neutron_drivers14:00
openstackMeeting started Fri Dec 21 14:00:25 2018 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_drivers)"14:00
openstackThe meeting name has been set to 'neutron_drivers'14:00
*** Chenjie has joined #openstack-meeting14:01
slaweqhi14:02
kailunhi14:02
mlavallehi14:02
nicky0419_hi14:03
*** nicky0419 has quit IRC14:03
cheng1hi14:03
mlavallelet's wait a few minutes for quorum14:03
nicky0419_https://bugs.launchpad.net/neutron/+bug/1805769 Please take look at it.14:04
openstackLaunchpad bug 1805769 in neutron "[RFE] Add a config option rpc_response_max_timeout" [Undecided,Incomplete] - Assigned to nicky (ss104301)14:04
nicky0419_If possible I want to disscuss this rfe.14:04
mlavallenicky0419_: we will probably not discuss this RFE in this meeting today14:04
*** janki has quit IRC14:04
*** hle2 has joined #openstack-meeting14:05
nicky0419_mlavalle: Got it. Thanks.14:05
mlavallenicky0419_: but I will comment on it later today14:06
haleybhi14:06
mlavallehi haleyb14:07
mlavallewe have quorum now14:07
mlavalle#topic RFEs14:08
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)"14:08
mlavalleLet's discuss https://bugs.launchpad.net/neutron/+bug/179521214:08
openstackLaunchpad bug 1795212 in neutron "[RFE] Prevent DHCP agent from processing stale RPC messages when restarting up" [Wishlist,In progress] - Assigned to Kailun Qin (kailun.qin)14:08
mlavallekailun: I believe this is yours, right?14:09
kailunmlavalle: yes14:09
kailunteam, I've addressed your comments/questions in the launchpad, please kindly have a look14:10
mlavallekailun: yes, I went over it carefully yesterday14:10
mlavallethanks for your responses14:10
kailunmlavalle: thank you, your last comment together w/ slaweq's, I've answered it today14:11
mlavallekailun: yes, I am looking at the code right now14:11
kailunmlavalle: slaweq: see if you have any further comment on that corner case raised14:11
slaweqkailun: mlavalle I think that You dispel my doubts about it14:12
liuyulongThis is worthy to do some testing like booting tons instance at one time, and restart the dhcp agent.14:12
liuyulongRally may be the tool for it.14:13
slaweqliuyulong: yes, I also wonder what impact it will have on performance14:13
kailunliuyulong: the bug was initially coming from a production env, and the fix has been validated based on that as well14:13
kailunslaweq: liuyulong: personally I agree w/ your opinions14:14
liuyulongkailun: Thanks, good to know14:14
slaweqkailun: so, to be sure I understand it correctly, during this delay just after start of agent, You expect that all "stale" rpc messages will be removed from queue?14:15
slaweqand then after delay they will not be processed by agent, am I right?14:16
kailunslaweq: liuyulong: actually the stale RPC msgs would be consumedd quickly since they are discarded w/o doing any real work in the agent, so the performance shouldn't be impacted much14:16
kailunslaweq: correct14:17
slaweqahh, ok14:17
haleybthe other option (which i've probably mentioned before) is to do as the l3-agent does - use a queue14:17
slaweqso during this delay, agent will consume old message and not do anything with them14:17
slaweqand then it will start doing full sync, right?14:17
kailunhaleyb: yes thanks for the proposal, I investigated a little bit but found that it might not meet our requirment14:18
liuyulonghttps://review.openstack.org/#/c/626830/, this patch was submit todady, use resource queue.14:18
kailunslaweq: during the delay, agent will discard the old msgs, but while doing the full sync, it will keep them due to the read lock and process them later14:19
haleybkailun: can you explain a little?  it should order rpc messages based on arrival14:19
kailunhaleyb: please kindly have a look at the comment #8 of the launchpad14:20
kailunhaleyb: I tried to answer your question, I'd like to copy-paste the answer here but I have a problem w/ the irc client:) sry14:21
haleybkailun: ack.  but in your case, how does the agent know there are stale rpc messages, just based on the config option timeout?14:22
mlavalleyes, that is my understanding. it is assumed that after the the wait period, the stale messages would have been consumed14:23
mlavalleright kailun?14:24
kailunhaleyb: I agree it's a little uncertain in comparing w/ timestamp/sequence based, but based on the comment #10, we consider some other points14:24
slaweqcan it happen that delay will be too short and some messages will not be discarded in some cases?14:25
*** _alastor_ has joined #openstack-meeting14:25
kailunhaleyb: personnally, I think it's no harm to add a delay for agents w/ default 014:25
liuyulongIIRC, the oslo.messaging has some settings about the queue duration14:26
haleybslaweq: yes, and i was thinking too long and we throw out "good" ones, but i guess the fullsync would fix that14:27
kailunmlavalle: the msgs will be discarded if not in the syncing stage, but for all those during syncing they'll be delayed processing14:27
mlavallekailun: I understand that14:27
kailunslaweq: as I said, the delay should not be long as the stale msgs can be consumed quickly14:28
slaweqis there maybe any way in oslo messaging to do something like "clean queue from all messages" and then start normal full_sync?14:28
slaweqlike one call instead of delay and pray that it will be enough :)14:28
mlavallekailun: so the "stale" messages will be consumed while waiting here, right: https://review.openstack.org/#/c/609463/10/neutron/agent/dhcp/agent.py@167?14:29
kailunslaweq: understood your wish, but I am not aware of that :)14:29
*** arne_wiebalck has quit IRC14:29
kailunmlavalle: correct14:30
slaweqkailun: maybe it would be good to ask oslo folks about that, and maybe it would be possible to add something like that there?14:30
*** _alastor_ has quit IRC14:30
haleybright, because otherwise there is no perfect setting for every deployment14:30
*** lbragstad has quit IRC14:31
slaweqthere is something like that in rabbitmq: https://www.rabbitmq.com/rabbitmqctl.8.html#purge_queue14:32
mlavallekailun: let's be clear. I think I can safely say we all understand the problem you are bringing up and we highly appreciate the fact that you and your team are uncovering these corner cases14:32
slaweqso probably it can be also implemented in oslo.messaging14:32
haleybright, and it might also be applied to other agents that way14:32
*** lbragstad has joined #openstack-meeting14:33
mlavallekailun: this is clearly a contribution to improve Neutron's performance. we are just thinking with you what the best solution might be14:33
kailunjust one concern, if multiple dhcp agents but only one restarted14:33
kailundoes it make sense for this dhcp agent restarted to clean all messages?14:34
liuyulongEach dhcp agent may have its own topic, clean that14:34
slaweqdon't each agent have own queue?14:35
*** nicky0419_ has quit IRC14:35
*** awaugama has joined #openstack-meeting14:35
slaweqI'm looking at https://github.com/openstack/neutron/blob/master/neutron/api/rpc/agentnotifiers/dhcp_rpc_agent_api.py#L19114:36
*** armstrong has joined #openstack-meeting14:36
slaweqand it looks that messages are sent "to host"14:36
slaweqso to specific agent14:36
kailunslaweq: liuyulong: per host14:36
slaweqand this queue can be purged by agent IMO14:36
slaweqkailun: per host and per agent type, right?14:37
kailunslaweq: yes14:37
slaweqso You will not purge e.g. L3 agent's queue with this14:37
kailunslaweq: no14:37
slaweqI know that I may be annoying with my requests but can You maybe explore also this one possibility instead of doing this delay? Because some constant delay don't look very reliable for me :/14:38
mlavallethe proposed mechanism is simple and doesn't have backwards compatibility issues14:39
liuyulongOne little concern about the current approach, message may be send twice for high availability scenario, right? And dhcp agent just stop that block, I'm not quite sure what will happen after that.14:39
kailunslaweq: it's OK no worry:) I cannot definitely ensure that purge queue is a better approach, but i agree it's worth looking into14:40
mlavallehowever, based, on what we are discussing here, it won't perform predictably in all situations14:40
kailunmlavalle: agree w/ you14:41
kailunmlavalle: as I said, it's no harm anyway, and should address some corner cases as a quick solution14:42
*** verdurin has quit IRC14:42
haleybmlavalle: right, and adding a timer value means more work in other projects, for example, we'll need to support changing it on deploy in tripleo or ansible, etc14:42
mlavallekailun: the good thing is that you and your team are helping us to uncover the corner cases that we have been unable to envision so far. But by definition this corner cases are more dificult to fix and therefore it is reasonable that we have a longer / more heated debate14:43
mlavalledon't you agree?14:43
kailunliuyulong: correct, i need further look into your HA case to give an answer14:44
kailunmlavalle: I agree14:44
*** verdurin has joined #openstack-meeting14:45
mlavallekailun: but again, let me reiterate that we highly appreciate your bringing these cases to our attention14:45
kailunmlavalle: no problem, thank you all14:45
mlavallekailun: before you go, let's also take a look at this patch: https://review.openstack.org/#/c/62683014:46
mlavallelet's consider it in the range of possible solutions, please14:46
mlavalleIt might not be applicable, but at first glance it seems relevant14:46
kailunmlavalle: yes, yulong points that out, i'll take a look14:47
liuyulongThanks kailun for the fix, yes, we have DHCP debts. And we recently also meet some DHCP issue locally during a booting storm...14:47
liuyulongMainly this issue: https://bugs.launchpad.net/neutron/+bug/176004714:48
openstackLaunchpad bug 1760047 in neutron "some ports does not become ACTIVE during provisioning" [High,Triaged] - Assigned to yangjianfeng (yangjianfeng)14:48
kailunliuyulong: thanks, I'll have a look and see if any insight14:49
mlavalleI knew that the discussion of this RFE was going to be long, so I only scheduled this one for today14:49
mlavallethere are a few though that I would like to bring your attention to before we go:14:49
mlavallefirst https://bugs.launchpad.net/neutron/+bug/180576914:50
openstackLaunchpad bug 1805769 in neutron "[RFE] Add a config option rpc_response_max_timeout" [Undecided,Incomplete] - Assigned to nicky (ss104301)14:50
mlavalleI will take the time today to comment on it. If you have spare bandwidth please take a look14:50
slaweqthis one looks reasonable for me, I just though that would be good to have approval from drivers team as it proposes new config option14:51
mlavallewhat do you think haleyb?14:52
haleybi have not read it yet14:53
haleybwas this the config option in neutron-lib14:54
haleyb?14:54
mlavalleok, let's look at it and comment14:54
slaweqhaleyb: it was originally proposed in neutron-lib14:54
slaweqbut now it is moved to neutron14:54
slaweqas all other config options are in neutron14:54
*** nicky0419 has joined #openstack-meeting14:54
haleybhttps://review.openstack.org/#/c/626109/14:55
slaweqyep14:55
haleybi guess it looks fine14:56
haleybwas there a follow-on that used it?14:56
mlavalleI don't think there was14:57
*** e0ne has quit IRC14:57
haleybif a tree falls.... :)14:58
haleybit would be good to have a user14:58
slaweqhttps://review.openstack.org/#/c/623401/1014:58
slaweqthis uses this option14:58
mlavallethanks for digging that one up14:59
mlavallerunning out of time14:59
mlavallelet's finish this one in channel14:59
mlavalle#endmeeting15:00
slaweqok15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Fri Dec 21 15:00:03 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-12-21-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-12-21-14.00.txt15:00
nicky0419Bye15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2018/neutron_drivers.2018-12-21-14.00.log.html15:00
mlavallenicky0419: let's continue in the neutron channel15:00
*** Chenjie has quit IRC15:00
*** nicky0419 has quit IRC15:00
*** hle2 has quit IRC15:02
*** cheng1 has quit IRC15:03
smcginnis#startmeeting releaseteam15:07
openstackMeeting started Fri Dec 21 15:07:34 2018 UTC and is due to finish in 60 minutes.  The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot.15:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:07
*** openstack changes topic to " (Meeting topic: releaseteam)"15:07
openstackThe meeting name has been set to 'releaseteam'15:07
smcginnisping ttx, dhellmann, diablo_rojo_phon, armstrong, evrardjp, lbragstad15:07
smcginnisSorry, time got away from me this morning.15:08
lbragstado/15:08
diablo_rojo_phonHello15:08
smcginnishttps://etherpad.openstack.org/p/stein-relmgt-tracking15:08
dhellmanno/15:08
evrardjpo/15:08
smcginnisWe are at R-16 now.15:08
armstrongo/15:08
smcginnis#topic Meeting time change15:09
*** openstack changes topic to "Meeting time change (Meeting topic: releaseteam)"15:09
evrardjpFYI I am on PTO until R-13.15:09
smcginnisevrardjp: Enjoy!15:09
smcginnisKind of related to the meeting time change, I think we can skip next week's meeting.15:10
evrardjpAgreed15:10
smcginnisI think most are probably going to be taking some time off or be busy with other things.15:10
smcginnisI will be off the 24th to the 2nd.15:10
smcginnisStarting in the new year, we will have a new meeting time.15:11
smcginnisWe had discussed changing and based on the last meeting I had proposed https://review.openstack.org/#/c/625290/15:11
smcginnisIt really doesn't help Tony, unfortunately, but I don't think we could find a time that would work for EU, US, and APAC.15:11
smcginnisSo starting in January, meeting will now be on Thursday at 1600 UTC in the #openstack-release channel.15:12
smcginnisAny comments, concerns, thoughts on that topic?15:13
evrardjpIt's impossible to please everyone...15:13
evrardjpI like the new meeting time15:14
diablo_rojo_phonI'm happy to not have to wake up at 6:57AM after this week?15:14
evrardjpthanks for the change15:14
smcginnisdiablo_rojo_phon: Hopefully that makes it a little more pleasant.15:14
diablo_rojo_phonYes, definitely thank you15:14
ttxThought we had cancelled the meeting this week15:15
smcginnisDid we?15:15
fungialso a reasonable choice15:15
smcginnisWell.. surprise? :)15:15
dhellmannthere's not much to talk about15:15
smcginnisI did want to at least officially state the meeting time change.15:15
ttxTechnically, the eavesdrop calandar does not have one this week15:16
smcginnisBut other than that, not much to go over this week.15:16
*** e0ne has joined #openstack-meeting15:16
dhellmannI threw a link to the eavesdrop session we had on monday into the tracking pad in case someone wants to go through it to look for things we don't have documented more formally15:16
smcginnisAh, that's because the time change patch was merged right away I guess.15:16
ttxsince the change merged earlier this week and describes meetings starting next year :P15:16
smcginnis#topic Release onboarding15:16
*** openstack changes topic to "Release onboarding (Meeting topic: releaseteam)"15:16
ttxI had one topic though :)15:16
smcginnisThis is the other thing I wanted to officially recognize.15:16
smcginnisThanks dhellmann for running that training.15:16
smcginnis#link http://eavesdrop.openstack.org/irclogs/%23openstack-release/%23openstack-release.2018-12-17.log.html#t2018-12-17T19:16:4615:17
fungii found the onboarding session very enlightening, thanks again dhellmann!15:17
dhellmannthank you all for attending!15:17
smcginnisI think that will be useful if anyone else wants to read through too. Even if they don't get the real time code review experience. :)15:17
smcginnisttx: What is you topic?15:18
diablo_rojo_phonThank you dhellmann for spending two hours educating me on release things :)15:18
ttxhttp://lists.openstack.org/pipermail/openstack-discuss/2018-December/001256.html15:18
smcginnis#topic release job failures15:18
*** openstack changes topic to "release job failures (Meeting topic: releaseteam)"15:18
smcginnisOh, the rerelease failure15:18
ttxIf someone knows what that "found 42 vulnerabilities (2 low, 34 moderate, 6 high)" mention refers to, please let me know15:19
ttxIt's a NPM feature, that checks the stuff you're trying to upload for knownvulnerabilities in deps15:19
smcginnisI don't know npm much either, but I think that's pretty normal for that.15:19
dhellmannit sounds like they're pinned to old dependencies15:19
ttxBut the report is a bit unclear15:19
ttxit looks like the vulnerabilities arise from npm 4.6.115:20
ttxbut I could not find where that was pulled in15:20
smcginnisNo response to that last post either. But good that it was called out.15:20
ttxBut it could also be that the report is unclear and that comes from the pinned deps15:20
smcginnisI hope that team is looking into it.15:20
fungiare you saying the vulnerabilities are in/because of using npm 4.6.1, or that the vulnerability checking/reporting was introduced by npm 4.6.1?15:20
ttxFurthermore, it could just be the normal state of things in NPMland15:21
ttxVuln checking was introduced in NPM615:21
ttxBut the report mentions +npm@4.6.115:21
ttxjust before saying "Boo!"15:21
fungiinteresting15:21
ttxbut then that npm@4.6.1 is not listed in the deps of k-s-r15:21
ttxand that is the limit of the extent of my npm knowledge15:22
ttxwhich I'd rather keep at that level for my sanity15:22
smcginnis;)15:22
fungiyeah, i know npm is a javascript something-or-other15:22
ttxso i was pinging the collective mindhive15:22
smcginnisWould it be worth another reply there to bump the thread?15:22
ttxfungi: would we have some other NPM upload job to check if the mention is different?15:23
ttxsmcginnis: I just posted one15:23
smcginnisIt would be nice to have some kind of ack from the team at least that they are aware of it.15:23
smcginnisOK, good.15:23
ttxI was trying to compare with another similar job output but could not find one at first glance15:23
smcginnisIf there's something our release jobs need to be checking for that they are not now, I think someone more involved in JS development would need to tell us what that would be.15:24
fungiit may be that there are a couple of npm upload jobs still because of an incomplete transition to zuul v3 or something, looking15:24
ttxlike maybe that npm@4.6.1 is brought in by the job itself, in which case it might make sense to generally update it15:24
smcginnisHopefully there is a response on the thread. Not sure what we can do (or should do) from here.15:26
smcginnisAnything else to discuss?15:28
fungi#link https://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/install-nodejs/defaults/main.yaml#n215:28
fungilooks like we default to nodejs v6 which presumably provides npm v6?15:29
* dhellmann has nothing15:29
smcginnisOK, let's see if someone more knowledgable on NPM steps forward.15:31
smcginnisI don't have any other agenda items.15:31
ttxnothing else on my side15:31
smcginnisUnless someone else has something, I think we can close early.15:31
ttxexcept happy holidays15:31
ttxstarting VERY soon15:31
smcginnisI hope everyone has a nice break. Thank you all for being part of the release team.15:31
fungithanks smcginnis!15:32
smcginnis#endmeeting15:32
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:32
openstackMeeting ended Fri Dec 21 15:32:13 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:32
openstackMinutes:        http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-12-21-15.07.html15:32
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-12-21-15.07.txt15:32
openstackLog:            http://eavesdrop.openstack.org/meetings/releaseteam/2018/releaseteam.2018-12-21-15.07.log.html15:32
dhellmanno/15:32
diablo_rojo_phonThanks smcginnis!15:32
lbragstadthanks smcginnis15:32
smcginnisdiablo_rojo_phon: You can ship some of those cookies this way if you have too many. :)15:32
*** armstrong has quit IRC15:33
diablo_rojo_phonsmcginnis: you been looking at my Snapchat? ;)15:33
smcginnisThey look great!15:34
diablo_rojo_phonThanks :) The majority are coming with to London for Alex & Andy.15:34
smcginnisNice!15:35
*** iyamahat has quit IRC15:35
*** jackding has left #openstack-meeting15:55
*** armax has joined #openstack-meeting15:56
*** _alastor_ has joined #openstack-meeting16:00
*** kopecmartin is now known as kopecmartin|off16:01
*** hongbin has joined #openstack-meeting16:02
*** mlavalle has left #openstack-meeting16:06
*** bnemec is now known as bnemerryxmas16:08
*** artom has quit IRC16:13
*** stephenfin is now known as finucannot16:14
*** e0ne has quit IRC16:16
*** e0ne has joined #openstack-meeting16:17
*** pcaruana has quit IRC16:18
*** aojea has quit IRC16:20
*** bobh has quit IRC16:24
*** ShilpaSD has quit IRC16:24
*** artom has joined #openstack-meeting16:26
*** tpsilva has joined #openstack-meeting16:27
*** macza has joined #openstack-meeting16:28
*** bobh has joined #openstack-meeting16:34
*** gyee has joined #openstack-meeting16:40
*** e0ne has quit IRC16:40
*** e0ne has joined #openstack-meeting16:42
*** e0ne has quit IRC16:44
*** jamesmcarthur has joined #openstack-meeting16:54
*** munimeha1 has joined #openstack-meeting16:59
*** ralonsoh has quit IRC16:59
*** mriedem is now known as mriedem_afk17:14
*** jamesmcarthur has quit IRC17:18
*** jamesmcarthur has joined #openstack-meeting17:29
*** jamesmcarthur has quit IRC17:34
*** yamahata has quit IRC17:51
*** ygbo has quit IRC18:00
*** iyamahat has joined #openstack-meeting18:06
*** munimeha1 has quit IRC18:17
*** jamesmcarthur has joined #openstack-meeting18:19
*** jamesmcarthur has quit IRC18:23
*** yamahata has joined #openstack-meeting18:28
*** macza has quit IRC18:28
*** macza has joined #openstack-meeting18:28
*** sridharg has quit IRC18:29
*** rossella_s has quit IRC19:05
*** e0ne has joined #openstack-meeting19:20
*** mriedem has joined #openstack-meeting19:38
*** mriedem_afk has quit IRC19:41
*** vishalmanchanda has quit IRC19:44
*** bobh has quit IRC20:02
*** bobh has joined #openstack-meeting20:05
*** bobh has quit IRC20:06
*** edmondsw has quit IRC20:10
*** edleafe has quit IRC20:10
*** bobh has joined #openstack-meeting20:46
*** bobh has quit IRC20:50
*** radeks has quit IRC20:51
*** radeks has joined #openstack-meeting20:51
*** raildo has quit IRC21:12
*** awaugama has quit IRC21:22
*** efried has quit IRC21:27
*** kencjohnston has quit IRC21:29
*** jamesmcarthur has joined #openstack-meeting21:48
*** jamesmcarthur has quit IRC21:53
*** efried has joined #openstack-meeting21:57
*** iyamahat_ has joined #openstack-meeting22:08
*** iyamahat has quit IRC22:11
*** efried has quit IRC22:12
*** slaweq has quit IRC22:16
*** radeks_ has joined #openstack-meeting22:19
*** radeks has quit IRC22:21
*** e0ne has quit IRC22:35
*** slaweq has joined #openstack-meeting22:43
*** slaweq has quit IRC22:47
*** mriedem is now known as mriedem_away22:49
*** smcginnis is now known as smcginnis_away22:49
*** lbragstad has quit IRC22:50
*** e0ne has joined #openstack-meeting22:51
*** bobh has joined #openstack-meeting22:53
*** bobh has quit IRC22:57
*** e0ne has quit IRC23:21
*** browny_ has quit IRC23:26
*** jamesmcarthur has joined #openstack-meeting23:26
*** iyamahat_ has quit IRC23:30
*** dims has quit IRC23:33
*** e0ne has joined #openstack-meeting23:37
*** bobh has joined #openstack-meeting23:38
*** e0ne has quit IRC23:38
*** radeks_ has quit IRC23:41
*** bobh has quit IRC23:42
*** jamesmcarthur has quit IRC23:43
*** slaweq has joined #openstack-meeting23:44
*** jamesmcarthur has joined #openstack-meeting23:47
*** slaweq has quit IRC23:48
*** jamesmcarthur has quit IRC23:52

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