Tuesday, 2019-11-19

*** diablo_rojo has quit IRC00:04
*** macz has quit IRC00:08
*** jamesmcarthur has joined #openstack-meeting00:15
*** zaneb has joined #openstack-meeting00:17
*** jamesmcarthur has quit IRC00:23
*** jamesmcarthur has joined #openstack-meeting00:25
*** jamesmcarthur has quit IRC00:34
*** ykatabam has joined #openstack-meeting00:45
*** ykatabam has quit IRC00:51
*** ykatabam has joined #openstack-meeting00:52
*** jamesmcarthur has joined #openstack-meeting00:53
*** brinzhang has joined #openstack-meeting00:56
*** nanzha has joined #openstack-meeting01:04
*** redrobot has quit IRC01:07
*** nanzha has quit IRC01:10
*** slaweq has joined #openstack-meeting01:11
*** nanzha has joined #openstack-meeting01:13
*** slaweq has quit IRC01:15
*** haleyb has joined #openstack-meeting01:16
*** jamesmcarthur has quit IRC01:19
*** zaneb has quit IRC01:24
*** gyee has quit IRC01:29
*** jamesmcarthur has joined #openstack-meeting01:31
*** ociuhandu has joined #openstack-meeting01:31
*** ociuhandu has quit IRC01:36
*** jamesmcarthur has quit IRC01:39
*** jamesmcarthur has joined #openstack-meeting01:42
*** ociuhandu has joined #openstack-meeting01:44
*** ociuhandu has quit IRC01:48
*** jamesmcarthur has quit IRC01:49
*** ociuhandu has joined #openstack-meeting01:49
*** jamesmcarthur has joined #openstack-meeting01:52
*** ociuhandu has quit IRC01:57
*** ricolin has joined #openstack-meeting02:04
*** slaweq has joined #openstack-meeting02:11
*** slaweq has quit IRC02:16
*** jamesmcarthur has quit IRC02:21
*** igordc has quit IRC02:21
*** brinzhang_ has joined #openstack-meeting02:30
*** jamesmcarthur has joined #openstack-meeting02:30
*** brinzhang has quit IRC02:33
*** baojg has joined #openstack-meeting02:47
*** ociuhandu has joined #openstack-meeting02:56
*** ociuhandu has quit IRC03:01
*** ociuhandu has joined #openstack-meeting03:03
*** ociuhandu has quit IRC03:07
*** apetrich has quit IRC03:08
*** ociuhandu has joined #openstack-meeting03:10
*** slaweq has joined #openstack-meeting03:11
*** slaweq has quit IRC03:16
*** ociuhandu has quit IRC03:18
*** ociuhandu has joined #openstack-meeting03:25
*** ociuhandu has quit IRC03:30
*** ociuhandu has joined #openstack-meeting03:32
*** ociuhandu has quit IRC03:36
*** jamesmcarthur has quit IRC04:00
*** jamesmcarthur has joined #openstack-meeting04:00
*** macz has joined #openstack-meeting04:04
*** jamesmcarthur has quit IRC04:06
*** ociuhandu has joined #openstack-meeting04:06
*** macz has quit IRC04:09
*** slaweq has joined #openstack-meeting04:11
*** ociuhandu has quit IRC04:14
*** slaweq has quit IRC04:15
*** ykatabam has quit IRC04:16
*** ykatabam has joined #openstack-meeting04:22
*** brinzhang has joined #openstack-meeting04:27
*** brinzhang_ has quit IRC04:30
*** jamesmcarthur has joined #openstack-meeting04:31
*** ykatabam has quit IRC04:37
*** brinzhang_ has joined #openstack-meeting04:42
*** jamesmcarthur has quit IRC04:44
*** brinzhang has quit IRC04:44
*** brinzhang has joined #openstack-meeting04:46
*** jamesmcarthur has joined #openstack-meeting04:47
*** brinzhang_ has quit IRC04:49
*** ykatabam has joined #openstack-meeting04:53
*** ociuhandu has joined #openstack-meeting05:18
*** nanzha has quit IRC05:18
*** nanzha has joined #openstack-meeting05:19
*** brinzhang_ has joined #openstack-meeting05:20
*** jamesmcarthur has quit IRC05:20
*** ociuhandu has quit IRC05:22
*** brinzhang has quit IRC05:23
*** ociuhandu has joined #openstack-meeting05:30
*** baojg has quit IRC05:31
*** brinzhang has joined #openstack-meeting05:33
*** baojg has joined #openstack-meeting05:34
*** ociuhandu has quit IRC05:35
*** brinzhang_ has quit IRC05:36
*** links has joined #openstack-meeting05:40
*** pcaruana has joined #openstack-meeting05:43
*** dkushwaha_ has joined #openstack-meeting05:47
*** jamesmcarthur has joined #openstack-meeting05:51
*** lennyb has joined #openstack-meeting05:54
*** jamesmcarthur has quit IRC05:55
*** zaneb has joined #openstack-meeting05:59
*** Luzi has joined #openstack-meeting06:00
*** slaweq has joined #openstack-meeting06:11
*** slaweq has quit IRC06:15
*** dkushwaha_ has quit IRC06:17
*** zaneb has quit IRC06:25
*** lpetrut has quit IRC06:25
*** Lucas_Gray has joined #openstack-meeting06:34
*** pcaruana has quit IRC06:56
*** rcernin has quit IRC06:58
*** ykatabam has quit IRC07:00
*** brinzhang_ has joined #openstack-meeting07:03
*** nanzha has quit IRC07:04
*** brinzhang_ has quit IRC07:04
*** nanzha has joined #openstack-meeting07:04
*** brinzhang_ has joined #openstack-meeting07:04
*** brinzhang_ has quit IRC07:04
*** dkushwaha has joined #openstack-meeting07:05
*** brinzhang has quit IRC07:05
*** apetrich has joined #openstack-meeting07:34
*** dtrainor has quit IRC07:35
*** brinzhang has joined #openstack-meeting07:41
*** brinzhang_ has joined #openstack-meeting07:49
*** brinzhang has quit IRC07:51
*** tpatil has joined #openstack-meeting07:52
*** keiko-k has joined #openstack-meeting07:59
*** slaweq has joined #openstack-meeting08:00
*** takahashi-tsc has joined #openstack-meeting08:03
*** joxyuki has joined #openstack-meeting08:03
dkushwaha#startmeeting tacker08:05
openstackMeeting started Tue Nov 19 08:05:45 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:05
*** openstack changes topic to " (Meeting topic: tacker)"08:05
openstackThe meeting name has been set to 'tacker'08:05
dkushwaha#topic Roll Call08:05
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:05
dkushwahahello keiko-k08:07
dkushwahahi all08:08
dkushwahalets start..08:08
dkushwaha#chair joxyuki08:08
openstackCurrent chairs: dkushwaha joxyuki08:08
dkushwaha#topic BP08:09
*** openstack changes topic to "BP (Meeting topic: tacker)"08:09
dkushwahaI could not have community work after summit, and started today08:09
dkushwahakeiko-k, I have posted some comments on your spec08:10
dkushwaha#link https://review.opendev.org/#/c/59186608:10
keiko-kThanks. I will check it later08:11
dkushwahaMain challenge i see is regarding introducing image create in vnfm side08:12
tpatildkushwaha: Heat doesn't support creation of image using file that's present in the CSAR08:13
tpatilso we are planning to use openstacksdk in tacker to create images08:14
tpatilHeat only allows to create image using web-download  method, no support for glance-direct.08:15
dkushwahatpatil, yo mean, we needs glance driver ?08:16
tpatilAlso when the VNF will be terminated, tacker will need to delete those images created for a deployment flavor.08:16
dkushwahatpatil, +108:17
tpatilopenstacksdk connection to call glance image create aPI to create image from file.08:17
tpatilinstead of using glance-client, I think using openstacksdk would help to interact with many other cross services including heat client.08:18
*** tesseract has joined #openstack-meeting08:18
dkushwahatpatil, I agree to delete those created image, but I think this responsibilities(create/delete image) should not be at VNFM level.08:20
joxyukidkushwaha, ideally yes.08:20
joxyukiso I think we should move that functionality to NFVO fron VNFM after V release08:21
joxyukisorry, after V release ->  V release or after08:22
tpatiljoxyuki: agree, as in U release, we are not planning to make any changes to the NFVO08:22
dkushwahaok, so lets make approach like: introduce an infra driver for glance api, that will be called as in pre_vnf_instantiation, and post_termination to create and delete those images08:25
dkushwahaand in future we will move tose calls to NFVO side08:26
dkushwahajoxyuki, tpatil wdyt ?08:26
tpatildkushwaha: why infra driver? IMO, a new method in existing openstack driver would also do the same job.08:27
joxyukitpatil, we should have abstraction layer of openstack VIM and kubernetes VIM.08:29
tpatilto create image, we will need VIM and it could be openstack or kubernetes.08:30
dkushwahajoxyuki, +1, tpatil, my opinion is to not to mix image task with vnf instantiation08:30
dkushwahaand it will reduce future refactoring tasks08:32
joxyukitpatil, yes. So we should have a rapper to abstract interfaces of openstack glance and k8s image management(I am not sure).08:32
tpatilok, so no need to add image creation interface to VnfAbstractDriver, but create a new one which VNFM will instantiate for now, and later it will be instantiate by NFVO, correct?08:34
*** pcaruana has joined #openstack-meeting08:36
*** ykatabam has joined #openstack-meeting08:36
*** rsimai has joined #openstack-meeting08:37
joxyukialmost yes, if you mean "instantiate" -> "image create".08:38
tpatiljoxyuki: Yes08:38
dkushwahatpatil, yes, Ex. it is like heat_client in  infra_driver, and will be called in some pre_vnf_instantiation  to create image08:40
tpatildkushwaha: Yes, it's clear now08:42
dkushwahaanything else from anyone08:43
dkushwaha#topic OpenDiscussion08:44
*** openstack changes topic to "OpenDiscussion (Meeting topic: tacker)"08:44
dkushwahaWe have a nice group pic from PTG https://www.dropbox.com/sh/1my6wdtuc1hf58o/AACU49pjWxzFNzcZJgjLG8n1a?dl=0&preview=Tacker.JPG08:45
joxyukiyeah! I included it in my summit & PTG report.08:46
dkushwahaDo we have anything else? otherwise we can close this meeting08:47
tpatilNice photo!!!08:47
takahashi-tscAbout Event alarm support,08:48
takahashi-tscFirst I checked zabbix plugin, but it support only command in VNF, so it is not suit our requirement...08:48
takahashi-tscI'd like to know if event_alarm is supported. Is there any good approach to confirm it?08:49
*** ralonsoh has joined #openstack-meeting08:50
dkushwahatakahashi-tsc, I needs to check, will notify you08:52
takahashi-tscThanks, if you give us an just overview, we will investigate the details.08:54
joxyukitakahashi-tsc, see https://review.opendev.org/#/c/561840/11/specs/stein/reservation-vnfm.rst line26408:55
*** priteau has joined #openstack-meeting08:55
joxyukiwe are using OS::Aodh::EventAlarm when handling reservation notification.08:55
joxyukiI think this does not meet your requirements but just information.08:56
takahashi-tscThank you. Is this using EventAlarm for a specific purpose? i.e. we requires another feature to use EventAlarm directly08:57
takahashi-tscanyway, I'll check the above, thanks!08:57
joxyukiyes, this is only for reservation handling, we cannot use it for general alarming.08:58
takahashi-tscOK, I got it.08:59
dkushwahaThanks all. time up..08:59
dkushwahaclosing this meeting09:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:00
openstackMeeting ended Tue Nov 19 09:00:20 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-11-19-08.05.html09:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-11-19-08.05.txt09:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-11-19-08.05.log.html09:00
*** tpatil has quit IRC09:00
*** ociuhandu has joined #openstack-meeting09:00
*** baojg has quit IRC09:01
*** brinzhang has joined #openstack-meeting09:02
*** joxyuki has left #openstack-meeting09:03
*** Luzi has quit IRC09:04
*** brinzhang_ has quit IRC09:05
*** rpittau|afk is now known as rpittau09:08
*** dkushwaha has quit IRC09:15
*** keiko-k has quit IRC09:15
*** Luzi has joined #openstack-meeting09:19
*** ykatabam has quit IRC09:21
*** Luzi has quit IRC09:21
*** takahashi-tsc has quit IRC09:42
*** ociuhandu has quit IRC09:43
*** jamesmcarthur has joined #openstack-meeting09:48
*** ykatabam has joined #openstack-meeting09:52
*** jamesmcarthur has quit IRC09:53
*** njohnston_ has joined #openstack-meeting09:53
*** njohnston has quit IRC09:54
*** mahatic has joined #openstack-meeting09:57
*** ykatabam has quit IRC10:15
*** Lucas_Gray has quit IRC10:19
*** Lucas_Gray has joined #openstack-meeting10:21
*** e0ne has joined #openstack-meeting10:23
*** brinzhang_ has joined #openstack-meeting10:29
*** brinzhang_ has quit IRC10:31
*** ociuhandu has joined #openstack-meeting10:31
*** brinzhang_ has joined #openstack-meeting10:32
*** davidsha has joined #openstack-meeting10:32
*** brinzhang has quit IRC10:32
*** brinzhang has joined #openstack-meeting10:33
*** tetsuro has quit IRC10:36
*** brinzhang_ has quit IRC10:37
*** tetsuro has joined #openstack-meeting10:37
*** lpetrut has joined #openstack-meeting10:40
*** rfolco has joined #openstack-meeting10:43
*** jamesmcarthur has joined #openstack-meeting10:50
*** brinzhang_ has joined #openstack-meeting10:51
*** brinzhang has quit IRC10:53
*** brinzhang has joined #openstack-meeting10:54
*** jamesmcarthur has quit IRC10:54
*** brinzhang_ has quit IRC10:56
*** brinzhang_ has joined #openstack-meeting11:07
*** brinzhang has quit IRC11:11
*** brinzhang has joined #openstack-meeting11:21
*** brinzhang has quit IRC11:22
*** brinzhang has joined #openstack-meeting11:23
*** brinzhang_ has quit IRC11:24
*** ociuhandu has quit IRC11:52
*** ociuhandu has joined #openstack-meeting11:53
*** ociuhandu has quit IRC11:53
*** ociuhandu has joined #openstack-meeting11:54
*** raildo has joined #openstack-meeting11:57
*** ociuhandu has quit IRC11:59
*** enriquetaso has joined #openstack-meeting11:59
*** jamesmcarthur has joined #openstack-meeting12:19
*** brinzhang_ has joined #openstack-meeting12:31
*** brinzhang_ has quit IRC12:32
*** brinzhang_ has joined #openstack-meeting12:32
*** brinzhang_ has quit IRC12:33
*** brinzhang_ has joined #openstack-meeting12:34
*** brinzhang has quit IRC12:34
*** brinzhang_ has quit IRC12:34
*** ociuhandu has joined #openstack-meeting12:36
*** Lucas_Gray has quit IRC12:43
*** ociuhandu has quit IRC13:00
*** ociuhandu has joined #openstack-meeting13:01
*** jamesmcarthur has quit IRC13:12
*** jamesmcarthur has joined #openstack-meeting13:12
*** ociuhandu has quit IRC13:17
*** ociuhandu has joined #openstack-meeting13:18
*** ociuhandu_ has joined #openstack-meeting13:22
*** davee__ has joined #openstack-meeting13:22
*** ociuhandu has quit IRC13:26
*** efried_pto is now known as efried13:28
*** ykatabam has joined #openstack-meeting13:33
*** liuyulong has joined #openstack-meeting13:35
*** eharney has quit IRC13:41
*** mriedem has joined #openstack-meeting13:42
*** ociuhandu_ has quit IRC13:52
*** jamesmcarthur has quit IRC13:52
*** ociuhandu has joined #openstack-meeting13:53
*** ociuhandu has quit IRC13:58
slaweq#startmeeting networking14:00
openstackMeeting started Tue Nov 19 14:00:47 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. 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: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
*** njohnston_ is now known as njohnston14:00
*** davidsha has quit IRC14:01
*** ociuhandu has joined #openstack-meeting14:02
slaweqok, lets start than14:03
slaweq#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:03
slaweqwe have quite many announcements for today14:03
slaweqShanghai PTG summary: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010702.html and also on http://kaplonski.pl/blog/shanghai_ptg_summary/ (with photos from team dinner)14:03
slaweqif You would like to have follow up discussion about some of the topics from this summary, please open new thread on ML for that14:04
slaweqok, next ona14:04
slaweqToday I sent emails about "new daddies need" for few projects:14:05
slaweqneutron-fwaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010929.html14:05
slaweqnetworking-bagpipe/bgpvpn: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010930.html14:05
slaweqneutron-vpnaas: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010931.html14:05
slaweqlets now wait if there will be any volunteers to maintain those projects14:05
slaweqhi liuyulong14:06
slaweqfor now amotoki talked with dkushwaha who is Tacker PTL and he will take care of networking-sfc14:07
slaweqso we already found "new daddy" for one stadium project :)14:07
*** ociuhandu has quit IRC14:08
bcafarelglad for networking-sfc :)14:08
slaweqand today lajoskatona offered on IRC that Ericsson can take care of networking-bgpvpn and bagpipe14:08
slaweqyeah :)14:09
slaweqlets now wait few more weeks to see how it will be14:09
slaweqok, next announcement14:09
slaweqRemoving of neutron-interconnection from stadium project is in progress: https://review.opendev.org/#/q/branch:master+topic:neutron-interconnection-retire14:09
slaweqI need to add some proper releasse note to one of those patches14:09
slaweqand I saw that Thomas vote -1 on https://review.opendev.org/#/c/694480/ as he wants to move the repo to x/ namespace14:10
slaweqbut that can be done later as separate step, at least that's how I understood this procedure14:11
slaweqnjohnston: am I right?14:11
slaweqor am I missing something there?14:11
njohnstonyes, I think fungi's suggestion is the best way http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010893.html14:11
rubasovlate o/14:12
njohnstonwhich would not change your patches, he would just revert the code removal change once he imported the code into the new x/ repo14:12
*** ykatabam has quit IRC14:12
slaweqyes, ok. So I understood this procedure correctly14:13
slaweqit's quite complicated process to remove such repo14:13
slaweqok, lets move on14:13
slaweqnext announcement14:13
slaweqI added "review-priority" vote to gerrit, details about it can be found at http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010825.html14:13
njohnstonShould we come to a general agreement as to what constitutes an "important change"?14:14
*** maciejjozefczyk has joined #openstack-meeting14:14
njohnstonotherwise it's rather subjective14:14
slaweqbasically core reviewers can now add +2, +1 or -1 vote to this new category and in dashboard14:14
slaweqel%253AReview%252DPriority%253D%252D1 everyone can check what are current top priority patches to review14:14
maciejjozefczyk\o sorry for beign late14:15
slaweqnjohnston: so, IMO "important change" may be some changes which fixes gate failures, or changes which are targeted to milestone which is just around the corner14:16
ralonsohslaweq, can you copy-paste this url in http://paste.openstack.org/?14:16
slaweqralonsoh: sorry, short version is here https://tinyurl.com/vezk6n614:16
njohnstonslaweq: OK, I can use that rule of thumb14:16
*** davidsha has joined #openstack-meeting14:16
slaweqnjohnston: and also, I hope that as only cores can set those priorities we should be fine as each of us have already some experience and feeling what is "important change" for review14:17
njohnstonsounds good14:18
slaweqmaybe also fixes for bugs marked as "critical" can be marked as "high priority" to review14:18
liuyulongSome security bug or critical bug should also be important and with higher review priority, IMO。14:18
slaweqliuyulong: yes, it can be14:19
*** lajoskatona has joined #openstack-meeting14:19
slaweqso to sumup, I would say: lets use our personal experience and feeling for that and lets see how it will work for us14:19
slaweqI will review this dashboard before every neutron team meeting and if there will be anything to discuss, I will raise it during the meeting14:20
slaweqok for You?14:20
bcafarelreview of the review list? thanks :)14:21
slaweqbcafarel: lol, yeah14:22
slaweqok, so one last announcement from me today14:22
slaweqlast week I prepared some plan of cleaning our CI jobs14:23
slaweqI sent it here: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010838.html14:23
slaweqI think we can discuss about it during CI meeting in details but I would also ask everyone from the team to check it and tell me what You think about it14:23
slaweqand that's all announcements from me for today14:24
slaweqdo You have any other things to announce?14:24
liuyulongWe have qos meeting in next our? Or we will move it to this one?14:25
slaweqliuyulong: qos meeting is just after this one14:26
liuyulongWe have any meeting rescheduling announcementa?14:26
ralonsoh(there is no agenda for QoS meeting today)14:27
slaweqliuyulong: this meeting isn't rescheduled14:27
liuyulongslaweq, sure, I remember that the ovn and performance meeting are merged to neutron team meeting, right?14:28
slaweqI didn't add it to announcements14:28
slaweqbut I have new item on the meeting agenda for that :)14:29
liuyulongOK, no more questions from me then.14:29
slaweqbut qos meeting isn't changed14:29
slaweqok, so lets move on14:29
slaweq#topic Blueprints14:29
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:29
slaweqBlueprints for Ussuri-1: https://launchpad.net/neutron/+milestone/ussuri-114:29
slaweqI added to this list also RFEs approved recently (or those which we talked about in Shanghai and we want to work on them)14:30
slaweqduring this week I will contact with people who proposed those rfe if they will work to implement that14:30
slaweqand if we can assign it to them14:31
slaweqI have also one question about those RFEs: do You think we should have BP opened for each of them?14:31
slaweqor RFE is enough?14:31
ralonsohdepends on the size of this feature and dependencies14:32
ralonsohif the RFE needs some patches and no dependencies from othre features, a bug is enough14:32
ralonsohBP where used before for nova-neutron features, with n-lib and os-vif dependencies14:32
ralonsoh(and OSsdk and OSclient ones)14:33
njohnstonI think an RFE might be good for the bulk tagging RFE in order to make sure we fully flesh out the API14:33
njohnstonsorry, a BP might be good for the bulk tagging RFE14:33
slaweqok, I see Your point, You're both right14:33
slaweqI will create Blueprints for those which I think that will require such changes around various projects14:33
ralonsohhaving a BP is not a big overhead14:33
njohnston+1 thanks14:34
slaweqif You have any other BP/RFE which should be target to Ussuri-1 and tracked here, please ping me after the meeting14:35
slaweqI can add it to the list14:35
slaweqand as for now, do You have any updates about BPs/RFEs from this list?14:36
slaweqor can we move on to the next section?14:36
slaweqok, lets move on than :)14:37
slaweq#topic Community goals14:37
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:37
slaweqas for community goals, we have one new on the list14:37
slaweqDrop Python 2.7 Support14:37
slaweqit is already accepted goal for Ussuri14:37
slaweqnjohnston - do You want to be "owner" of this one on Neutron's side?14:38
slaweqthx a lot14:38
slaweqas for other goals which are proposed, I will add them to this list when will be accepted by TC14:39
njohnstonfor this goal I will be guided by the decisions written down in https://etherpad.openstack.org/p/drop-python2-support from the TC discussion14:39
slaweqso I think that this is all about community goals for today14:40
slaweq#topic Bugs14:40
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:40
slaweqAs we didn't have this meeting for few weeks, we have 3 different reports to mention:14:41
slaweqBugs report for week of October 28th: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010521.html14:41
slaweqBugs report for week of November 4th: http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010676.html14:41
slaweqBugs report for week of November 11th: https://docs.google.com/spreadsheets/d/1DdWgFhMWrK67YJHBgzSbnOcFprQbOLFM16WQcPt0RS8/edit#gid=014:41
* njohnston is ready to go for bug deputy starting the 25th14:42
slaweqnjohnston: thx, but first this week is mlavalle on bug deputy :)14:43
*** links has quit IRC14:44
*** ykatabam has joined #openstack-meeting14:44
slaweqas for bugs from those reports, I would like to ask L3 subteam to take a look at https://bugs.launchpad.net/neutron/+bug/185165914:44
openstackLaunchpad bug 1851659 in neutron "removing a network from a DHCP agent removes L3 rules even if it shouldn't" [High,New]14:44
slaweqwhich is marked as High14:44
slaweqwe have also gate failure related to networking-sfc: https://bugs.launchpad.net/neutron/+bug/185150014:45
openstackLaunchpad bug 1851500 in neutron ""test_show_port_chain" conflicts with Flow Classifier" [Medium,Confirmed]14:45
slaweqso I will try to ask dkushwaha if he can take a look at this14:45
slaweqand we have https://bugs.launchpad.net/neutron/+bug/1851194 which is related to FWaaS so I'm not sure if there will be anyone to take a look at it14:46
openstackLaunchpad bug 1851194 in neutron "FWaaSv2 configures iptables with invalid port name" [Medium,New]14:46
slaweqany other bugs You want to talk about today?14:46
*** enriquetaso has quit IRC14:47
slaweqok, I will take that as "no" :)14:48
slaweqso lets move on14:48
slaweqnext topic is new in agenda14:48
slaweq#topic Networking OVN and ML2+OVS+DVR Convergence14:48
*** openstack changes topic to "Networking OVN and ML2+OVS+DVR Convergence (Meeting topic: networking)"14:48
* haleyb waves14:48
slaweqas we discussed in Shanghai, I proposed to remove old meeting https://review.opendev.org/69499114:49
*** enriquetaso has joined #openstack-meeting14:49
*** ociuhandu has joined #openstack-meeting14:49
slaweqnow it's haleyb turn - do You have anything else to talk about for today?14:49
*** dtrainor has joined #openstack-meeting14:50
haleybslaweq: i will touch base with you regarding sending an email to the ML14:50
slaweqhaleyb: ok14:51
haleybi will also update the spec one more time...14:51
slaweqtbh I forgot about this email :/ sorry for that14:51
haleybnp, blame it on jetlag14:51
slaweqhaleyb: ok :)14:52
slaweqanything else related to the ovn for today? or can we move on?14:53
haleybi don't have anything today14:54
slaweqok, so lets move on to the last point for today14:54
slaweq#topic On Demand agenda14:54
*** openstack changes topic to "On Demand agenda (Meeting topic: networking)"14:54
slaweqthere is no any topics in meeting agenda14:54
slaweqbut maybe someone wants to talk about something?14:54
slaweqif so, You have about 5 minutes14:55
slaweqok, I guess that there is no more topics for today than14:56
slaweqso thx for attending and have a great week14:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:56
openstackMeeting ended Tue Nov 19 14:56:53 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-11-19-14.00.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-11-19-14.00.txt14:56
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-11-19-14.00.log.html14:56
*** eharney has joined #openstack-meeting14:58
ralonsoh#startmeeting neutron_qos15:00
openstackMeeting started Tue Nov 19 15:00:14 2019 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
ralonsohtoday David is not going to attend15:00
ralonsohand the agenda is quite short15:00
ralonsohso let's wait 1 min first15:00
ralonsoh#topic RFEs15:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:01
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/147652715:01
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:01
ralonsohAs commented, David is not going to attend today15:02
slaweqhi again15:02
ralonsohhi slaweq15:02
*** shintaro has joined #openstack-meeting15:02
ralonsohDavid will present the spec in drivers meeting, in Friday15:02
ralonsohas agreed last meeting15:02
ralonsohthen, once the spec is approved we can continue with the code review15:03
slaweqralonsoh: please keep in mind that I cancelled this week's drivers meeting15:03
ralonsohI'll talk to David then15:03
ralonsohmy bad. But he needs to present the spec and RFE to someone else15:03
slaweqsorry for that but we will not have quorum this week15:04
slaweqralonsoh: but this rfe https://bugs.launchpad.net/neutron/+bug/1476527 is approved already15:04
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:04
ralonsohI know, he is trying to push it for the last 18 months15:04
ralonsohI know, but the spec15:05
ralonsohjust to know how to implement it15:05
slaweqso it's "only" about reviewing spec, right?15:05
ralonsohyes yes15:05
ralonsohok then, we can move to next section15:06
ralonsoh#topic Bugs15:06
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:06
slaweqit is this spec https://review.opendev.org/#/c/678865/ right?15:06
ralonsohlet me send the current links for it15:07
ralonsoh    #link https://review.opendev.org/678865 : Spec dscp + classifier15:07
ralonsoh    #link https://review.opendev.org/670049 : Neutron-Lib - classifier migration15:07
ralonsoh    #link https://review.opendev.org/670050 : Neutron Classifier migration into Neutron15:07
ralonsoh    #link https://review.opendev.org/636330 : DSCP + Classifier neutron-lib15:07
ralonsoh    #link https://review.opendev.org/636333 : DSCP + Classifier neutron15:07
ralonsoh(all in https://etherpad.openstack.org/p/neutron_qos_meeting_chair)15:07
slaweqok, I will try review it this week15:07
ralonsohslaweq, thanks a lot15:08
ralonsohlet's move to bugs15:08
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/184517615:08
openstackLaunchpad bug 1845176 in neutron "Removing of QoS queue in neutron-ovs-agent fails due to existing references" [Medium,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:08
ralonsohand the patch15:08
ralonsoh#link https://review.opendev.org/#/c/687922/15:09
ralonsohI still need to address some problems with fullstack tests15:09
ralonsohrelated to the need cache variables added, of course15:10
ralonsohbut at least I think the patch is addressing the problem we have15:10
ralonsohany comment?15:10
ralonsohnext one15:11
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/184516115:11
openstackLaunchpad bug 1845161 in neutron "Neutron QoS Policy lost on interfaces" [High,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:11
ralonsohand the patch15:12
ralonsoh#link https://review.opendev.org/#/c/690098/15:12
ralonsohthis one is just failing randomly in the tests15:12
ralonsohbut I didn't see any error related to the patch15:12
ralonsoh(according to my understanding)15:13
*** lajoskatona has quit IRC15:13
ralonsohreviews are welcome always!15:13
slaweqsure ralonsoh15:14
slaweqI will review15:14
ralonsohok, next seciton15:15
ralonsoh#topic Open Discussion15:15
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:15
ralonsohI don't have anything here15:15
ralonsohand you slaweq ?15:15
ralonsohnice to see you15:17
ralonsohwhat is that?15:17
ralonsohahhh yes15:17
davidshaHey, just got out of a meeting @.@15:17
davidshaSorry about that15:17
ralonsohthe DSCP ofctl implementation15:17
*** ykatabam has quit IRC15:17
davidshaWhile I was working on the the classifier DSCP backend I realised that QoS and a few other extensions are not using the Native openFlow driver15:18
ralonsohinstead of using the native implementation, the DSCP is using the cli one15:18
ralonsohI know this is another stone in the shoe15:19
ralonsohbut we want to get rid of the CLI implementation and use only the native one15:19
davidshaI'm working on a patch atm for the QoS to use the native driver, but we should probably try to deprecate: https://github.com/openstack/neutron/blob/master/neutron/agent/common/ovs_lib.py#L34315:19
ralonsohand you are going to refactor extensively the DSCP part15:19
ralonsohyou should first use the native imp here15:19
ralonsohI agree:  run_ofctl should be removed ASAP15:20
ralonsohI'll open a bug to track this, I'll send you the link15:20
davidshaWill I include the deprecation flag in the patch?15:20
davidshaAck, thanks!15:21
*** markmcclain has quit IRC15:21
davidshaof run_ofctl15:21
ralonsohyes, we should15:21
*** shintaro has quit IRC15:21
ralonsohlet me check how many calls in neutron are made to this function15:21
davidshawill do, In Neutron, I don't think there are any after QoS, but I did see this being used in networking-sfc, I'll properly check Neutron.15:22
ralonsohthis is used in Neutron just in OVSBridge15:23
*** markmcclain has joined #openstack-meeting15:23
slaweqI didn't even know that we still have such method15:23
davidshayes, but the native is a child of OVSBridge15:23
ralonsohdavidsha, yes, but only few methods using ofctl15:24
ralonsohthe problem in sfc15:24
ralonsohis sfc using OVSBridge methods?15:24
davidshaSFC has one or 2 calls to it15:24
ralonsohor it's own implementation15:24
ralonsohto ovsbridge methods?15:24
davidshaLine 57 above it proxies self to self.bridge15:26
ralonsohI understand they use it, it's easier15:26
ralonsohactually the way to run an os-ken application is not trivial15:26
davidshaYa, I'm still trying to get the DSCP mark to work15:27
ralonsohthe good point in ovs dscp you are already inside an os-ken application15:27
ralonsohok, let me open the bug to deprecate ofctl and I'll send you the link15:28
davidshakk, I need to drop, thanks!15:28
ralonsohanything else here in open discussion?15:28
ralonsohthank you all for attending and reading the log15:29
ralonsohsee you here in two weeks15:29
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:30
openstackMeeting ended Tue Nov 19 15:30:07 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-11-19-15.00.html15:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-11-19-15.00.txt15:30
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-11-19-15.00.log.html15:30
*** jamesmcarthur has joined #openstack-meeting15:31
*** lamt has joined #openstack-meeting15:44
*** lajoskatona has joined #openstack-meeting15:48
*** pcaruana has quit IRC15:50
*** pcaruana has joined #openstack-meeting15:51
*** armax has quit IRC15:54
*** armax has joined #openstack-meeting15:56
slaweq#startmeeting neutron_ci16:00
openstackMeeting started Tue Nov 19 16:00:12 2019 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
slaweqhi (again)16:00
slaweqok, lets start16:01
slaweqfirst of all16:01
slaweqGrafana dashboard: http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:01
slaweqplease open it and we will move on16:01
slaweq#topic Actions from previous meetings16:01
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:01
slaweqslaweq to investigate failed neutron.tests.fullstack.test_qos.TestDscpMarkingQoSOvs16:01
slaweqBug reported https://bugs.launchpad.net/neutron/+bug/185272416:02
openstackLaunchpad bug 1852724 in neutron "Fullstack test for dscp_marking_packets fails if first icmp is not send properly" [Medium,Fix released] - Assigned to Slawek Kaplonski (slaweq)16:02
slaweq      Patch proposed: https://review.opendev.org/69450516:02
slaweqit's even merged already16:02
slaweqso next one16:03
slaweqnjohnston prepare etherpad to track stadium progress for zuul v3 job definition and py2 support drop16:03
njohnstonyeah, I did not get to that, I'll work on it today16:03
njohnstonsomehow I missed it in my todo list16:03
slaweqso, just as a reminder16:03
slaweq#action njohnston prepare etherpad to track stadium progress for zuul v3 job definition and py2 support drop16:04
slaweqand we will get back to this in next meeting16:04
slaweqnext one16:04
slaweqslaweq to take a look at connectivity issues after resize/migration16:04
slaweqI did some analysis and described it in comment https://bugs.launchpad.net/neutron/+bug/185055716:04
openstackLaunchpad bug 1850557 in neutron "DHCP connectivity after migration/resize not working" [Medium,Confirmed] - Assigned to Slawek Kaplonski (slaweq)16:04
slaweqbut I don't know exactly why it happens like that16:04
slaweqas it happend at least few times in tempest-slow job, which runs tests in serial, I will try to reproduce this issue locally16:05
*** gyee has joined #openstack-meeting16:05
slaweqbut tbh I didn't saw it this week in ci results16:05
slaweqok, next one16:07
slaweqnjohnston delete old tests from neutron-dynamic-routing repo16:07
njohnstonup for review16:08
slaweqthx njohnston16:08
slaweqI will review it as soon as zuul will be happy :)16:08
slaweqok, next one16:09
slaweqslaweq to move neutron-tempest-with-os-ken-master to zuulv3 syntax and switch to run neutron related tests only16:09
slaweqPatch https://review.opendev.org/69477016:09
slaweqready for review :)16:09
bcafarellate o/16:09
slaweqhi bcafarel :)16:09
slaweqand this is in fact last "non-grenade" legacy job in neutron repo IIRC16:09
slaweqnext one was16:10
slaweqslaweq to fix python version in tempest-slow-py3 job16:10
slaweqBug reported: https://bugs.launchpad.net/tempest/+bug/185300416:10
openstackLaunchpad bug 1853004 in tempest "tempest-slow-py3 job uses python 2.7 on subnodes" [Undecided,In progress] - Assigned to Slawek Kaplonski (slaweq)16:10
slaweqPatch https://review.opendev.org/69476816:10
slaweqbut I found out today that this is not only related to tempest-slow-py316:11
slaweqalso tempest-multinode-full-py3 has this issue16:11
slaweqand it is also addressed by patch 69476816:11
slaweqbut also neutron-tempest-plugin-multinode-dvr job has got same issue16:11
slaweqand patch to fix it is here:16:11
slaweqso please review :)16:12
slaweqok, and the last one from last week is16:12
slaweqnjohnston to check failing NetworkMigrationFromHA in multinode dvr job16:12
* bcafarel tries to keep up with the flurry of review links16:13
njohnstonI did not have a chance to look at that16:13
slaweqwill You have time to look at it this week maybe?16:13
njohnstonI will do my best16:14
slaweqthx njohnston :)16:14
slaweqI know You will16:14
slaweq#action njohnston to check failing NetworkMigrationFromHA in multinode dvr job16:14
slaweqthat was all actions from last week16:15
slaweqanything else You want to add/ask maybe?16:15
slaweqok, so lets move on16:16
slaweq#topic Stadium projects16:16
*** openstack changes topic to "Stadium projects (Meeting topic: neutron_ci)"16:16
slaweqwe already talked about neutron-dynamic-routing patch16:16
slaweqand I don't think we have anything else to talk about here today16:17
slaweqin next weeks we can track here progress of migrating jobs to zuulv3 and dropping py2 jobs16:17
*** ociuhandu has quit IRC16:17
slaweqbut for now I don't have anything else16:17
*** nanzha has quit IRC16:17
slaweqbut maybe You have something to talk about here?16:18
lajoskatonaHi, I just realized that CI meeting is in progress16:18
slaweqhi lajoskatona :)16:18
njohnstonhello lajoskatona16:18
lajoskatonaI have one networkingüodl small bug: https://review.opendev.org/66890416:18
lajoskatonaIt is a unit test that fails sporadically16:19
lajoskatonaIf you have some time to check it that would be helpful, sorry for adding new things to the piles16:19
ralonsohsorry, in this patch I don't see the UTs failing16:20
slaweqralonsoh: I think that this patch fixes failing UT16:20
ralonsohI need to read better.....16:20
lajoskatonaralonsoh: yes, soryy for bad wording, the ut that fails is networking-odl: test_feature_configs_does_not_mutate_default_features16:21
lajoskatonaralonsoh: thanks anyway16:21
slaweqlajoskatona: I'm not odl expert but patch seems reasonable for me16:21
bcafarelone-liner to add init/reset is reasonable yeah16:22
lajoskatonaslaweq: yeah the good thing is that this is in python, not in Java at least :-)16:22
slaweqlajoskatona: true :)16:23
slaweqlajoskatona: I just +W your patch16:23
lajoskatonaslaweq: thanks, a lot less recheck from this day16:23
slaweqok, lets move on16:24
slaweq#topic Grafana16:24
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:24
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:24
slaweqas You may see there, empest-slow-py3 and tempest-multinode-full-py3 high failure rate today16:24
slaweqsame for neutron-grenade16:24
slaweqand all that issues are caused by nova's patch https://review.opendev.org/#/c/687954/16:25
slaweqnova went too far with dropping py2 support16:25
slaweqI know they were talking today how to fix this for now16:26
slaweqso hopefully it will be fine soon16:26
lajoskatonaslaweq: so let's wait with rechecks?16:27
slaweqlajoskatona: for now, yes16:27
lajoskatonaslaweq: ok16:27
slaweqfor sure neutron-grenade job, tempest-slow-py3 and tempest-multinode-full-py3 will fail16:27
slaweqtempest-slow-py3 and tempest-multinode-full-py3 should be fixed when my patch to switch it "fully" to py3 will be merged16:27
slaweqand for neutron-grenade we have already patch to remove it from neutron queue16:28
slaweqso in fact if all those patches will be merged, we should be good even without fix on nova's side16:28
njohnstonif they need any more reviews, can you post the URLs?16:29
ralonsohbtw, with one of those patches (devstack) USE_PYTHON3 will be True by default16:29
slaweqnjohnston: thx, I already sent links to those patches before16:30
njohnstonah ok16:30
slaweqother than that I think we are fine16:31
njohnstondo you think we will need to squash the changes in order to get them through the gate?  Or should we wait for Nova to clean up?16:31
slaweqnjohnston: no, we don't need to squash anything16:31
slaweqas fix for tempest-slow-py3 and tempest-multinode-full-py3 is in tempest repo: https://review.opendev.org/69476816:32
slaweqand remove of neutron-grenade is in neutron repo: https://review.opendev.org/#/c/694039/16:33
slaweqso first patch in tempest should land and than our patch in neutron will be able to land16:33
slaweqand than we should be good probably16:33
slaweqbut I'm not sure which version will be faster, that one or fix on nova's side16:34
slaweqok, I think we can move on16:34
slaweqbasically this issue is biggest issue for now, so I don't have prepared any other issues for today16:35
slaweqbut I want to talk a bit about scenario jobs16:35
slaweq#topic Tempest/Scenario16:35
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:35
slaweqfew days ago I sent email http://lists.openstack.org/pipermail/openstack-discuss/2019-November/010838.html16:36
slaweqwith some comparison of single/multinode jobs16:36
slaweqand also with comparison of tempest- and neutron-tempest-plugin- jobs16:36
slaweqand I would like to discuss here a bit about what do You think should we do with those jobs?16:36
ralonsohfirst, what are we going to do with LB?16:37
ralonsohbecause the future (or not) of LB could decide about those jobs16:37
slaweqsome job with LB should be still there16:38
ralonsohif we remove Lb too?16:38
slaweqralonsoh: for now we will not remove it for sure16:38
slaweqwe are starting some discussion about deprecating it16:38
ralonsohI know16:38
slaweqbut nothing else for now16:38
slaweqand for now we have 2 jobs: neutron-tempest-plugin-scenario-linuxbridge and neutron-tempest-linuxbridge16:39
slaweqmaybe we could merge them into one job?16:39
ralonsohthen we should keep it16:39
ralonsohwe are doing different things there, but could work16:39
ralonsohI'll check this16:40
slaweqralonsoh: what do You mean by "different things"?16:40
ralonsohthe tests are different16:41
slaweqyes, tests are different16:41
slaweqthat's why I think that maybe we can run one job which will run tests from both tempest and than neutron-tempest-plugin repo16:41
ralonsohthat could speed up the CI16:42
slaweqand would be one less job which can fail maybe :)16:42
slaweqbut the second question is: do we really need to run all tempest tests for it?16:43
slaweqas it is single node job, it don't test things like live-migration for example16:43
slaweqso basically it runs a lot of nova related tests and neutron related tests16:44
slaweqneutron related things we can cover in neutron-tempest-plugin job as well16:44
slaweqand from nova point of view - what we really need to test, if it's only if vm can be spawned and ssh than we have this covered in neutron-tempest-plugin tests also16:45
slaweqso maybe we could stay only with neutron-tempest-plugin-scenario-linuxbridge job?16:45
slaweqand exactly same situation is for neutron-tempest-iptables_hybrid16:46
ralonsoh(I would need to check both jobs and the tests executed)16:46
*** rsimai is now known as rsimai_away16:46
*** lajoskatona has quit IRC16:46
slaweqralonsoh: sure, please check them and maybe reply to my email on ML16:46
slaweqwe can continue this discussion there16:46
slaweqthx a lot16:46
slaweqnext thing are grenade jobs16:47
slaweqwe have grenade-py3 and neutron-grenade-multinode in check and gate queue16:47
slaweqthose jobs are the same16:47
slaweqonly difference between them is that grenade-py3 is single node job16:47
slaweqcan we maybe drop this one? and use only neutron-grenade-multinode job?16:48
ralonsohsingle node is not used in production16:48
ralonsohso yes16:48
bcafareland I suppose we don't have any tests that *requires* single node :)16:48
bcafarel(so also yes)16:48
slaweqbcafarel: exactly :)16:48
slaweqok, so as I see agreement here, I will propose patch to drop single node job16:48
slaweqthat's all from me about this topic16:49
slaweqif You would have any other opinions/ideas about it, please reply to the email and we can continue this discussion there16:50
slaweqfrom other things16:50
slaweqI sent patch https://review.opendev.org/#/c/694049/ which will start running queens jobs using neutron-tempest-plugin with some specific tag16:50
*** tesseract has quit IRC16:51
slaweqso we can drop those jobs from master branch queues16:51
slaweqplease review it also :)16:51
bcafarelooh nice16:51
slaweqand one last thing which I want to mention16:52
slaweqI have patch to switch default deployment to uwsgi https://review.opendev.org/#/c/694042/16:52
slaweqbut it has some problems with grenade jobs16:52
slaweqso I will investigate that and I hope it will be ready soon16:52
ralonsohslaweq, https://review.opendev.org/#/c/694266/16:53
ralonsohwhich one is failing?16:53
ralonsohor you mean in https://review.opendev.org/#/c/694042/16:54
njohnstonthe second one16:54
slaweqralonsoh: yes, it's failing in https://review.opendev.org/#/c/694042/16:54
slaweqbut I think I know why it is failing16:55
slaweqI will just need to test that in gate :)16:55
slaweqok, that's all from me for today16:55
slaweqanything else You want to talk about today?16:55
bcafarelsounds like all action points from ptg have patches in progress then?16:56
bcafarelnice work :)16:56
slaweqbcafarel: I hope so16:56
slaweqbut if I missed anything, forgive me :)16:56
ralonsohno mercy16:57
slaweqok, we are almost on time16:57
slaweqthx for attending the meeting guys16:57
slaweqand see You online o/16:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:57
openstackMeeting ended Tue Nov 19 16:57:43 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-11-19-16.00.html16:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-11-19-16.00.txt16:57
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-11-19-16.00.log.html16:57
*** jamesmcarthur has quit IRC17:05
*** rpittau is now known as rpittau|afk17:06
*** jamesmcarthur has joined #openstack-meeting17:17
*** ociuhandu has joined #openstack-meeting17:22
*** ociuhandu has quit IRC17:27
*** geguileo has quit IRC17:41
*** jamesmcarthur has quit IRC17:43
*** munimeha1 has joined #openstack-meeting17:49
*** igordc has joined #openstack-meeting17:52
*** ociuhandu has joined #openstack-meeting18:04
*** davidsha has quit IRC18:04
*** ricolin has quit IRC18:04
*** e0ne has quit IRC18:08
*** ociuhandu has quit IRC18:08
*** tosky has joined #openstack-meeting18:11
*** armax has quit IRC18:11
*** ociuhandu has joined #openstack-meeting18:17
*** ociuhandu has quit IRC18:21
*** Shrews has joined #openstack-meeting18:42
*** enriquetaso has quit IRC18:45
*** armax has joined #openstack-meeting18:51
*** ayoung has joined #openstack-meeting18:52
*** AJaeger has joined #openstack-meeting18:56
*** davee__ has quit IRC18:59
fungianyone on hand for an infra meeting?19:01
fricklero/ ... kind of19:01
toskyyep (a point in the agenda)19:02
fungiwill start in just a sec (standing in for clarkb)19:03
AJaegerthanks, fungi !19:03
*** ralonsoh has quit IRC19:03
fungiokay, let's get this party started19:05
fungi#startmeeting infra19:05
openstackMeeting started Tue Nov 19 19:05:23 2019 UTC and is due to finish in 60 minutes.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:05
*** openstack changes topic to " (Meeting topic: infra)"19:05
openstackThe meeting name has been set to 'infra'19:05
fungi#link http://lists.openstack.org/pipermail/openstack-infra/2019-November/006518.html agenda19:06
* corvus hopes mordred is around for a gerrit update (gratuitous ping)19:06
fungi#topic announcements19:06
*** openstack changes topic to "announcements (Meeting topic: infra)"19:06
fungiclarkb is indisposed, so you get my retro meeting treatment19:07
* corvus hopes this doesn't mean clarkb has a cavity19:07
fungimy brain has a cavity19:07
fungianyway, i've been apprised of no announcements19:08
fungianyone have something?19:08
clarkbI dont but dentist was slow getting to the exam portion if the visit19:08
fungii'm taking your silence as a tacit declination19:08
fungi#topic Actions from last meeting19:08
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:08
fungi#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-11-12-19.01.html minutes from last meeting19:09
fungiAction items: "1. (none)"19:09
fungiseems we can move on19:09
fungi#topic Specs approval19:09
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:09
fungino specs up for approval which i can see19:10
fungi#topic Priority Efforts: A Task Tracker for OpenStack19:11
*** openstack changes topic to "Priority Efforts: A Task Tracker for OpenStack (Meeting topic: infra)"19:11
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack19:11
fungiSotK has pushed up a refresh of the attachments work19:11
SotKit uses openstacksdk now and also doesn't leak auth tokens19:12
fungi#link https://review.opendev.org/#/q/topic:story-attachments+status:open19:12
fungiended up using tempurls right?19:13
fungirather than formpost19:13
SotKindeed, I couldn't get the formpost signature that openstacksdk produced to work, and using tempurls made it easier to name the objects something that wasn't their filename19:14
fungimordred: ^ you may also have some input there19:15
fungi#topic Priority Efforts: Update Config Management19:16
*** openstack changes topic to "Priority Efforts: Update Config Management (Meeting topic: infra)"19:16
fungi#link http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management19:16
fungii didn't make any further progress on the mediawiki puppetry update this week19:17
fungithough i think i keep conflating this with the trusty upgrades19:17
fungithere is work in progress to letsencrypt-ify the gitea deployment19:17
fungioh, though that's listed under the opendev topic already19:18
fungii guess the main activity under this actual topic currently is mordred's dockerification of our gerrit deployment19:19
*** e0ne has joined #openstack-meeting19:19
fungibut it seems like he's probably not around at the moment so we can circle back to this at the end if we get time19:20
fungi#topic Priority Efforts: Zuul as CD engine19:20
*** openstack changes topic to "Priority Efforts: Zuul as CD engine (Meeting topic: infra)"19:20
fungithe bullet depth on the agenda is not entirely clear19:21
fungii'm not aware of any new developments on this front in the past few weeks19:22
clarkbprobably the only recent update was the discussion we had at the ptg19:23
clarkband how its the project ssh keys that give us trouble that we need to sort out in zuul somehow?19:23
fungiyeah, which has been summarized on the ml19:23
fungioh, or did that make it into the summary?19:24
fungii guess that was in the zuul-related bits you elided19:24
fungianyway, in short, running jobs for different projects to connect to the same resource is challenging, and mordred (was it mordred?) suggested sort of proxying them by configuring jobs in one project to essentially be triggered by events from another project19:26
clarkbyup taking advantage of the proposed http trigger19:26
corvusyeah; i think that made it into the etherpad notes19:26
clarkbor an internal zuul event trigger system that could be added19:26
fungithat would require a new zuul feature, but seemed non-contentious once we talked through some of the logistics19:26
fungior at least a slight extension to an existing feature19:27
fungianyway, that's more of a zuul-side discussion we probably need to restart with the broader community now that we're not in shanghai19:28
fungi#topic Priority Efforts: OpenDev (LetsEncrypt issued cert for opendev.org)19:28
*** openstack changes topic to "Priority Efforts: OpenDev (LetsEncrypt issued cert for opendev.org) (Meeting topic: infra)"19:28
fungi#link https://review.opendev.org/694181 LetsEncrypt issued cert for opendev.org19:28
fungiclarkb has been hacking on this19:28
fungithe manually-acquired opendev.org ssl cert is due to expire in ~w0 days19:29
fungier, ~10 days19:29
ianwi think it's right to go?  the sticking point yesterday was failing mirror jobs, which we ended up tracking down to afs server being offline19:29
fungibut the implementation there seems to be working and ready for review, allowing us to switch to letsencrypt fo rthose19:29
clarkbianw: ya I've rechecked the change19:30
clarkbif it comes back +1 I think we can go ahead and have gitea01 try it19:30
fungiso yeah, not super urgent would be good to land in the next few days so we have a week to make sure it's working before we end up having to buy a new cert at the last minute19:30
clarkb++ I should be able to approve and monitor the gitea01 change today19:31
fungi#topic Priority Efforts: OpenDev (Possible gitea/go-git bug in current version of gitea we are running)19:31
*** openstack changes topic to "Priority Efforts: OpenDev (Possible gitea/go-git bug in current version of gitea we are running) (Meeting topic: infra)"19:31
fungi#link https://storyboard.openstack.org/#!/story/2006849 Possible gitea/go-git bug in current version of gitea we are running19:31
fungiianw has been trying to sort this out with tonyb19:32
fungistrange disconnects on the server side and client-side errors during git fetch for openstack/nova19:32
ianwno smoking gun, but upstream has asked us to upgrade to 1.9.619:32
ianw#link https://review.opendev.org/69489419:33
fungiat first we thought it was isolated to gitea06 but then identified similar behavior with gitea0119:33
ianwif there's still issuses with that ... well ... it's a one way trip to debug town i guess19:33
corvusdoes it persist if fetching directly from the backends, not going through th lb?19:33
clarkbcorvus: yes19:33
ianw#link https://github.com/go-gitea/gitea/issues/900619:34
fungiload balancer shenanigans were also an early suspicion, but got ruled out, yeah19:34
fungi#topic Trusty Upgrade Progress: Wiki updates19:36
*** openstack changes topic to "Trusty Upgrade Progress: Wiki updates (Meeting topic: infra)"19:36
fungithis one's on me, i guess19:37
fungino progress since shanghai, should be able to pick it back up again this week19:37
fungi#topic static.openstack.org19:37
*** openstack changes topic to "static.openstack.org (Meeting topic: infra)"19:37
*** ociuhandu has joined #openstack-meeting19:37
fungiaccording to the agenda text, "Ajaeger started writing some changes"19:37
fungi#link https://review.opendev.org/#/q/topic:static-services+status:open19:38
ianwyeah, i'm on the hook for creating volumes, but haven't got to it yet19:38
AJaegerfungi: some time ago ;) First one just got approved, rest needs review and AFS creation - and mnaser can take those over and then add the remaining changes...19:39
fungiianw: no worries, per chatter in #openstack-infra we should probably get the spice flowing on existing volumes first anyway19:39
clarkbfungi: ++19:39
fungi#topic ask.openstack.org apache2 crashing daily during logrotate19:41
*** openstack changes topic to "ask.openstack.org apache2 crashing daily during logrotate (Meeting topic: infra)"19:41
clarkbI kept this on the agenda because I hadn't heard anything new on this topic19:41
clarkbbut I was also sick late last week and may have missed updates19:41
clarkbIt looks like ask is running now19:41
fricklerit seems the patch to change the logrotate posthook is working fine19:41
clarkbfrickler: doing a restart instead of a reload?19:41
fricklerI merged that on friday and didn't need a manual intervention since then19:42
fricklerclarkb: yes19:42
fungithat was the old fix and somehow got undone in an upgrade, right?19:42
frickleractually 4 of them in a row19:42
fricklerfungi: no, I tested it manually earlier and it was undone by the next puppet run19:42
fricklernot sure why it started breaking initially after running seemingly fine for some time19:43
fricklerpossibly some ubuntu update19:43
fricklerbut I think we can regard that as solved for now, in particular giving that we may stop running it at all in the future19:44
fungiokay, cool. thanks!19:45
clarkbfrickler: thank you!19:45
fungi#topic Installing tox with py3 in base images runs some envs with py3 now19:45
*** openstack changes topic to "Installing tox with py3 in base images runs some envs with py3 now (Meeting topic: infra)"19:45
fungi#link http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2019-11-15.log.html#t2019-11-15T11:10:5719:45
fricklerokay, the issue here are tox envs that don't specify a basepython19:45
fricklerlike functional19:46
fungithey presumably use whatever python tox was installed with19:46
toskyas you can see from the linked job, a job from a stable branch is now failing19:46
toskymy understanding/hope is that stable jobs shouldn't be affected by changes like this19:46
toskysorry, jobs running on stable branches19:46
fricklerand we seem to have changed installing tox from py2 to py3 in dib not long ago19:46
ianwi bet somehow it has to do with I3414fb9e503f94ff744b560eff9ec0f4afdbb50e19:47
*** ociuhandu has quit IRC19:47
clarkbtosky: I'm not sure we can assert that. stable jobs break all the time because the world around them has to move forward19:48
fricklerone solution is to hardcode basepython=py2 where needed, but tosky argues that we shouldn't force people to touch so many stable jobs19:48
toskyclarkb: uhm, I'm not sure about that19:48
clarkbtosky: even centos 7 updates have done it19:49
toskywe have requirement boundaries for this19:49
toskybut something that forces all functional jobs (and maybe others) for all repositories?19:49
clarkbtosky: it does not force it, instead it changes a default19:49
clarkba forward looking default19:49
ianwyeah, i think that would do it ... i did not intend this fwiw19:50
toskybut it changes it in a way that was needed for that stable branch19:50
clarkbthe default here is tox's default python which is based on what it got installed under19:50
fungithe way we've defended stable jobs against such uncertainty in the past is by being explicit about what those jobs use. making them explicitly declare a python interpreter version is consistent with that in my opinion19:51
toskyok, time is running out and I see where it's heading, so what I'd like to ask is at least19:51
toskyto send an email explaining the issue19:52
ianwthese jobs must be running on bionic?19:52
fungiimplicit dependencies are where we get into trouble19:52
toskyand if someone really feels like that, an set of infra forced jobs to fix this, like the openstack->opendev migration19:52
toskys/forced jobs/forced pushes/19:52
toskybut at least the email19:53
*** artom has quit IRC19:53
clarkbtosky: ya I think we can send email about it. I don't think the change was intentional or expected (hence not catching it earlier), but I do think the change is likely desireable as we try to put python2 behind us19:54
fungito reiterate ianw's question, is this only happening for jobs running on bionic (so, say, stable/train and master branch jobs?)19:54
clarkbin general if tox environments require a python version they should specify that in the tox config though19:54
ianwfungi: i think it must be -- what has happened is that we install the environment now with what dib thinks is the default python for the platform19:55
ianwwhich is python3 for bionic, but not for xenial19:55
fungiyeah, if so the problem domain is small and recent19:55
*** artom has joined #openstack-meeting19:55
ianwi can put in an override, as such, that forces bionic to install with python219:56
fungiwe don't need to, say, backport these basepython additions to extended-maintenance branches19:56
toskyuhm, when was bionic introduced? Rocky?19:56
ianwone small point is, though, *outside* the gate, it seems fragile for anyone trying to run things19:56
clarkbianw: yes exactly. the tox config should be specific19:56
clarkbotherwise it is broken for people running tox locally half the time19:57
*** gmann is now known as gmann_afk19:57
clarkb(depending on what python version they've elected to install tox with)19:57
ianwclarkb: yep, but i also understand tosky's point that it was annoying to throw this out there without warning19:57
ianw(although, it was totally unintentional)19:57
fungitosky: whatever openstack release cycle started after april 201819:57
fungiso stein, looks like19:58
fungibecause the rocky cycle started in february 201819:59
toskyI totally understand it was unintentional, that was never a problem; issues happen19:59
fungiokay, we're out of time20:00
fungimordred: if you're around later and want to provide a gerrit status update in #openstack-infra, there's interest20:00
ianwtosky: i can take a point to send a mail to opendev-list about this today, and we can decide on the path20:01
fungiand anyone with further things to discuss, find us similarly in the #openstack-infra channel20:01
fungithanks everyone!20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:01
openstackMeeting ended Tue Nov 19 20:01:29 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-11-19-19.05.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-11-19-19.05.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-11-19-19.05.log.html20:01
*** tosky has left #openstack-meeting20:01
clarkbfungi: thank you for running the meeting20:01
fungiany time20:01
fungiit's like a blast from the past ;)20:02
*** Shrews has left #openstack-meeting20:03
*** Qiming has quit IRC20:03
*** Qiming has joined #openstack-meeting20:05
*** AJaeger has left #openstack-meeting20:17
*** ociuhandu has joined #openstack-meeting20:38
*** ociuhandu has quit IRC20:42
*** ociuhandu has joined #openstack-meeting20:43
*** eharney has quit IRC20:48
*** igordc has quit IRC20:50
*** ociuhandu has quit IRC20:58
*** gmann_afk is now known as gmann21:03
*** e0ne has quit IRC21:07
*** igordc has joined #openstack-meeting21:15
*** ayoung has quit IRC21:24
*** ociuhandu has joined #openstack-meeting21:29
*** raildo has quit IRC21:45
*** e0ne has joined #openstack-meeting21:45
*** ociuhandu has quit IRC21:48
*** mriedem has quit IRC21:48
*** eharney has joined #openstack-meeting21:48
*** jamesmcarthur has joined #openstack-meeting21:48
*** lpetrut has quit IRC21:50
*** mriedem has joined #openstack-meeting21:51
*** rcernin has joined #openstack-meeting21:59
*** rcernin has quit IRC22:01
*** rcernin has joined #openstack-meeting22:01
*** rcernin has quit IRC22:01
*** rcernin has joined #openstack-meeting22:02
*** e0ne has quit IRC22:08
*** priteau has quit IRC22:15
*** pcaruana has quit IRC22:33
*** slaweq has quit IRC22:39
*** ociuhandu has joined #openstack-meeting22:41
*** jamesmcarthur has quit IRC22:42
*** ociuhandu has quit IRC22:46
*** slaweq has joined #openstack-meeting22:48
*** munimeha1 has quit IRC22:49
*** slaweq has quit IRC22:53
*** e0ne has joined #openstack-meeting22:54
*** slaweq has joined #openstack-meeting23:03
*** ociuhandu has joined #openstack-meeting23:07
*** e0ne has quit IRC23:09
*** ociuhandu has quit IRC23:09
*** ociuhandu has joined #openstack-meeting23:11
*** armax has quit IRC23:13
*** armax has joined #openstack-meeting23:14
*** ociuhandu has quit IRC23:16
*** slaweq has quit IRC23:16
*** armax has quit IRC23:16
*** priteau has joined #openstack-meeting23:19
*** slaweq has joined #openstack-meeting23:25
*** slaweq has quit IRC23:30
*** efried has quit IRC23:30
*** ociuhandu has joined #openstack-meeting23:30
*** ociuhandu has quit IRC23:40
*** slaweq has joined #openstack-meeting23:42
*** slaweq has quit IRC23:47
*** Liang__ has quit IRC23:54
*** slaweq has joined #openstack-meeting23:57
*** ociuhandu has joined #openstack-meeting23:58

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