Tuesday, 2019-02-12

*** SWDevAngel has quit IRC00:05
*** tetsuro has joined #openstack-meeting00:25
*** TxGirlGeek has quit IRC00:25
*** macza has joined #openstack-meeting00:29
*** tetsuro has quit IRC00:30
*** tetsuro has joined #openstack-meeting00:32
*** macza has quit IRC00:34
*** tetsuro has quit IRC00:35
*** tetsuro_ has joined #openstack-meeting00:35
*** iyamahat has joined #openstack-meeting00:42
*** yamamoto has joined #openstack-meeting00:51
*** gyee has quit IRC00:54
*** yamamoto has quit IRC00:56
*** mnasiadka has joined #openstack-meeting00:59
*** sweston has joined #openstack-meeting00:59
*** mrhillsman has joined #openstack-meeting00:59
*** TheJulia has joined #openstack-meeting00:59
*** coreycb has joined #openstack-meeting00:59
*** patrickeast has joined #openstack-meeting01:00
*** sdake has joined #openstack-meeting01:02
*** macza has joined #openstack-meeting01:08
*** ijw has joined #openstack-meeting01:12
*** macza has quit IRC01:13
*** tetsuro has joined #openstack-meeting01:20
*** tetsuro_ has quit IRC01:20
*** mriedem has quit IRC01:23
*** cloudrancher has joined #openstack-meeting01:26
*** markvoelker has quit IRC01:30
*** markvoelker has joined #openstack-meeting01:31
*** tetsuro has quit IRC01:35
*** tetsuro_ has joined #openstack-meeting01:35
*** markvoelker has quit IRC01:35
*** sdake has quit IRC01:37
*** sdake has joined #openstack-meeting01:39
*** sdake has quit IRC01:43
*** enriquetaso has quit IRC01:44
*** yamamoto has joined #openstack-meeting01:53
*** tetsuro has joined #openstack-meeting02:01
*** tetsuro_ has quit IRC02:01
*** TxGirlGeek has joined #openstack-meeting02:05
*** lbragstad has quit IRC02:06
*** ijw has quit IRC02:07
*** macza has joined #openstack-meeting02:22
*** macza has quit IRC02:27
*** macza has joined #openstack-meeting02:27
*** jamesmcarthur has joined #openstack-meeting02:28
*** hongbin has joined #openstack-meeting02:29
*** cloudrancher has quit IRC02:29
*** macza has quit IRC02:31
*** markvoelker has joined #openstack-meeting02:31
*** jamesmcarthur has quit IRC02:32
*** iyamahat has quit IRC02:35
*** TxGirlGeek has quit IRC02:36
*** yamamoto has quit IRC02:48
*** markvoelker has quit IRC03:05
*** bbowen has quit IRC03:10
*** armax has quit IRC03:12
*** yamamoto has joined #openstack-meeting03:14
*** tetsuro has quit IRC03:22
*** tetsuro_ has joined #openstack-meeting03:22
*** tetsuro has joined #openstack-meeting03:26
*** tetsuro_ has quit IRC03:26
*** armax has joined #openstack-meeting03:34
*** dmacpher_ has joined #openstack-meeting03:34
*** dmacpher has quit IRC03:34
*** sdake has joined #openstack-meeting03:40
*** tpatil has joined #openstack-meeting03:43
*** samP has joined #openstack-meeting03:55
*** TxGirlGeek has joined #openstack-meeting03:57
*** shilpasd_ has joined #openstack-meeting03:59
*** sdake has quit IRC03:59
samPHi all for masakari04:00
tpatilHi04:01
samP#startmeeting masakari04:01
openstackMeeting started Tue Feb 12 04:01:05 2019 UTC and is due to finish in 60 minutes.  The chair is samP. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: masakari)"04:01
openstackThe meeting name has been set to 'masakari'04:01
samPtpatil: Hi04:01
*** tashiromt has joined #openstack-meeting04:01
samP#topic Bugs and pathces04:01
*** openstack changes topic to "Bugs and pathces (Meeting topic: masakari)"04:01
samPAny bugs or patches to discuss?04:01
tpatilNew bug reported : https://bugs.launchpad.net/masakari/+bug/181465604:02
openstackLaunchpad bug 1814656 in masakari "Update host allows to update host name for any non-existing compute host in nova" [Undecided,In progress] - Assigned to jayashri bidwe (jayashrib)04:02
*** markvoelker has joined #openstack-meeting04:02
tpatilPatch is proposed : https://review.openstack.org/#/c/635710/04:02
patchbotpatch 635710 - masakari - Allow updating host name only if it exists in nova - 1 patch set04:02
tpatilNeed to review04:02
tpatilThis issue was fixed for create case, but update api was missed at that time. Silly mistake04:03
samPtpatil: thanks. I will review this04:03
*** imsurit_ofc has joined #openstack-meeting04:04
*** tetsuro has quit IRC04:05
samPAbout python3, we need to make py3 jobs voting.04:06
samP#link https://wiki.openstack.org/wiki/Python304:07
tpatilOk04:07
*** lbragstad has joined #openstack-meeting04:09
tpatilI think most of py3 jobs are passing on gate for masakari projects. will verify this point and make it a voting job04:09
*** diablo_rojo has quit IRC04:09
samPtpatil: sure, thanks.04:11
samPCan you please update the status of masakari in the wiki04:12
samPhttps://wiki.openstack.org/wiki/Python304:12
tpatilsamP: sure04:13
samPtpatil: thanks04:13
samPLet's move to next topic04:13
samP#topic Stein Work Items04:13
*** openstack changes topic to "Stein Work Items (Meeting topic: masakari)"04:13
samPPlease share the updates, if you have any04:13
tpatil1)  Add event notification feature to masakari04:14
samPI have to review a lot..04:14
tpatilNeed to review specs: https://review.openstack.org/#/c/473057/804:14
patchbotpatch 473057 - masakari-specs - Add event notification feature to masakari - 8 patch sets04:14
tpatilPatches are also ready : https://review.openstack.org/#/q/topic:bp/notifications-in-masakari+(status:open+OR+status:merged)04:14
tpatilI have reviewed all these patches before and all patches LGTM But I want other core reviewers to take a look at it first before I vote +2.04:15
samPtpatil: Thanks04:15
tpatil2) Add progress details for recovery workflow04:16
tpatilSpecs up for review : https://review.openstack.org/#/c/632079/04:16
patchbotpatch 632079 - masakari-specs - Add progress details for recovery workflow - 3 patch sets04:16
tpatilImplementation is in progress04:16
tpatilMain blocker is taskflow doesn't support to retrieve tasks progress details in the order of workflow task execution.04:17
tpatilWe will report this issue in taskflow04:17
samPtpatil: thanks04:17
tpatilbut we have found out an alternative way to solve this issue until this issue is not fixed in the taskflkow library04:18
tpatil3) Add functional CI job and tests04:18
tpatilPatch : https://review.openstack.org/#/c/633663/04:19
patchbotpatch 633663 - masakari - Add functional CI job and tests for segments - 5 patch sets04:19
tpatilFew minor comments needs to be addressed04:19
tpatilIn this patch ,CI job and  segment tests are added. More patches to follow.04:20
tpatilThat's all update about stein work items from my end04:21
samPtpatil: Thanks.04:21
samPAny other items to discuss?04:21
samPI will do review the patches and spec.04:22
shilpasd_tpatil: thank you04:22
shilpasd_samP: thank you04:22
samPshilpasd_: np04:22
samPif nothing else to share, we could finish the meeting early today.04:23
tpatilsamP: Ok04:23
tashiromtsamP: OK, thanks04:24
samPPlease use #openstack-masakari IRC@freenode or openstack-discuss ML for further discussion.04:24
samPThank you all!04:24
samP#endmeeting04:24
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:24
openstackMeeting ended Tue Feb 12 04:24:32 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-02-12-04.01.html04:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-02-12-04.01.txt04:24
openstackLog:            http://eavesdrop.openstack.org/meetings/masakari/2019/masakari.2019-02-12-04.01.log.html04:24
*** tpatil has left #openstack-meeting04:25
*** armax has quit IRC04:28
*** shilpasd_ has quit IRC04:29
*** jamesmcarthur has joined #openstack-meeting04:29
*** janki has joined #openstack-meeting04:30
*** armax has joined #openstack-meeting04:30
*** jamesmcarthur has quit IRC04:34
*** markvoelker has quit IRC04:34
*** manjeets has quit IRC04:41
*** armax has quit IRC04:59
*** dmacpher_ has quit IRC05:03
*** niska has quit IRC05:14
*** niska has joined #openstack-meeting05:24
*** hongbin has quit IRC05:30
*** markvoelker has joined #openstack-meeting05:32
*** dmacpher has joined #openstack-meeting05:32
*** TxGirlGeek has quit IRC05:56
*** niska has quit IRC06:05
*** markvoelker has quit IRC06:05
*** vishakha has joined #openstack-meeting06:08
*** niska has joined #openstack-meeting06:15
*** whoami-rajat has joined #openstack-meeting06:19
*** sridharg has joined #openstack-meeting06:20
*** e0ne has joined #openstack-meeting06:24
*** jamesmcarthur has joined #openstack-meeting06:30
*** jamesmcarthur has quit IRC06:34
*** e0ne has quit IRC06:35
*** lbragstad has quit IRC06:50
*** Luzi has joined #openstack-meeting06:53
*** zaneb has quit IRC06:53
*** ralonsoh has joined #openstack-meeting06:59
*** markvoelker has joined #openstack-meeting07:02
*** kopecmartin|off is now known as kopecmartin07:05
*** e0ne has joined #openstack-meeting07:12
*** factor has quit IRC07:15
*** e0ne has quit IRC07:16
*** e0ne has joined #openstack-meeting07:24
*** e0ne has quit IRC07:32
*** markvoelker has quit IRC07:35
*** jrbalderrama has joined #openstack-meeting07:35
*** e0ne has joined #openstack-meeting07:42
*** slaweq has joined #openstack-meeting07:44
*** jrbalderrama has quit IRC07:45
*** dkushwaha has joined #openstack-meeting07:47
*** aojea has joined #openstack-meeting07:52
*** phuochoang has joined #openstack-meeting07:58
*** joxyuki has joined #openstack-meeting07:59
*** longkb has joined #openstack-meeting08:01
dkushwaha#startmeeting tacker08:02
openstackMeeting started Tue Feb 12 08:02:16 2019 UTC and is due to finish in 60 minutes.  The chair is dkushwaha. Information about MeetBot at http://wiki.debian.org/MeetBot.08:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:02
*** openstack changes topic to " (Meeting topic: tacker)"08:02
openstackThe meeting name has been set to 'tacker'08:02
dkushwaha#topic Roll Call08:02
*** openstack changes topic to "Roll Call (Meeting topic: tacker)"08:02
dkushwahawho is here for Tacker weekly meeting?08:02
hyunsikyanghello:)08:02
*** bhagyashris has joined #openstack-meeting08:02
phuochoanghi all08:03
bhagyashrisHi08:03
hyunsikyangHi again.08:03
joxyukihello08:03
dkushwahaHello all08:04
dkushwahaok lets start..08:05
dkushwaha#topic Tacker release cycle08:05
*** openstack changes topic to "Tacker release cycle (Meeting topic: tacker)"08:05
dkushwahaCurrently Tacker has cycle-with-intermediary release, but there is a proposal to make it cycle-with-rc08:06
dkushwaha#link https://review.openstack.org/#/c/635660/08:06
patchbotpatch 635660 - releases - Switch Tacker service to cycle-with-rc - 1 patch set08:06
dkushwahaAs of now, I am not much sure about cycle-with-rc, so i first needs to check that08:07
dkushwahamoving next..08:08
dkushwaha#topic kestone v3 api usages08:09
*** openstack changes topic to "kestone v3 api usages (Meeting topic: tacker)"08:09
dkushwaha#link https://review.openstack.org/#/c/632725/08:09
patchbotpatch 632725 - tacker - Move to use only kestone v3 api - 5 patch sets08:09
dkushwahaI had updated the patch, but seems functional jobs failing again.08:10
dkushwahaI will check again, and will update the patch.08:10
dkushwahamoving next..08:11
dkushwaha#topic  force delete08:11
*** openstack changes topic to "force delete (Meeting topic: tacker)"08:11
dkushwahaphuochoang, I hope no further work required on https://review.openstack.org/#/c/620381/08:12
patchbotpatch 620381 - python-tackerclient - Adds support force delete resources - 2 patch sets08:12
dkushwahaphuochoang, if it is done(client patch) from your side, we can merge it08:13
dkushwahawdyt?08:13
phuochoangI think client patch is good to merge08:13
*** longkb has quit IRC08:14
dkushwahaphuochoang, ok, So lets merge it.08:14
phuochoangthanks :)08:15
dkushwahaphuochoang, I will check https://review.openstack.org/#/c/626854/ again, and will update it if required08:15
patchbotpatch 626854 - python-tackerclient - Adds support force delete for NS. - 1 patch set08:15
phuochoangI will give a look at it08:16
dkushwahaphuochoang, thanks08:17
phuochoangIn this patch, https://review.openstack.org/#/c/63091408:18
patchbotpatch 630914 - tacker (stable/queens) - Add VNF to monitor after restarting tacker service - 2 patch sets08:18
phuochoangfunctional test in queens can't run, I will try to do same thing in https://review.openstack.org/#/c/578170 to fix this08:19
patchbotpatch 578170 - tacker - Add multinode jobs (MERGED) - 47 patch sets08:19
bhagyashrisphuochoang: IMO this https://review.openstack.org/#/c/578170. Is related to multimode setup for tests so is the multimode setup is required in stable/queens08:20
patchbotpatch 578170 - tacker - Add multinode jobs (MERGED) - 47 patch sets08:20
phuochoangI think multiple node setup patch is not applied on queens08:22
phuochoangif we can support that, it will be better08:22
bhagyashrisI guess this patch is introduce in rocky to test the placement policy and that was required the multimode setup/job to test the placement policy08:23
dkushwahaphuochoang, bhagyashris lets avoid multinode setup patch for Q08:23
phuochoangahh, sorry, I got your point08:24
dkushwahaphuochoang, any other workaround for that?08:24
phuochoangI have only problem that functional test in queens version is not working08:25
dkushwahaphuochoang, bhagyashris ok I will spend some time on that, and will notify08:27
bhagyashrisyeah, I saw the same issue on all stable/queens patches08:27
dkushwahaok, coming back on force-delete topic.08:28
dkushwahaphuochoang, I am thinking to update the patch https://review.openstack.org/#/c/620385/08:29
patchbotpatch 620385 - tacker - [WIP] Adds support force delete resources - 3 patch sets08:29
dkushwahalet me know if it ok and you are not updating it currently08:29
phuochoangI will update it and let you known08:30
*** jamesmcarthur has joined #openstack-meeting08:31
dkushwahaphuochoang, cool.08:31
*** markvoelker has joined #openstack-meeting08:32
dkushwahaOnce this will start working I will push server side ns patch(as this patch will be required inside ns patch)08:32
dkushwahamoving next..08:32
dkushwaha#topic reservation-vnfm08:33
*** openstack changes topic to "reservation-vnfm (Meeting topic: tacker)"08:33
dkushwahaI am creating local setup on my env, will test & review it.08:34
dkushwahacan somebody also test this patch08:34
joxyukidkushwaha, thanks08:35
*** e0ne has quit IRC08:35
bhagyashrisdkushwaha: thank you!08:35
joxyukiyea, I will.08:35
*** jamesmcarthur has quit IRC08:35
dkushwahajoxyuki, anyother update from your side?08:36
joxyukinothing from me08:36
dkushwahamoving next08:37
*** e0ne has joined #openstack-meeting08:37
dkushwahaphuochoang, do you have something to updates?08:38
phuochoangnothing from me08:38
*** e0ne has quit IRC08:38
dkushwahaok08:38
dkushwaha#topic Open Discussion08:38
*** openstack changes topic to "Open Discussion (Meeting topic: tacker)"08:38
bhagyashrisJust small update that https://review.openstack.org/#/c/630914/ https://review.openstack.org/#/c/631108/ pushed the patches ,Kindly review the same08:39
patchbotpatch 630914 - tacker (stable/queens) - Add VNF to monitor after restarting tacker service - 2 patch sets08:39
patchbotpatch 631108 - tacker (stable/pike) - Add VNF to monitor after restarting tacker service - 3 patch sets08:39
dkushwahabhagyashris, ok, I will do08:41
bhagyashrisdkushwaha:  thank you :)08:41
dkushwahaFolks, As we are going close to release, we needs volunteer who can help on Bug triages08:42
dkushwahaWe have more than 150 open bugs https://bugs.launchpad.net/tacker08:42
dkushwahaThat will we gr8 if someone can lead in this area.08:43
dkushwahahyunsikyang, hi08:44
hyunsikyanghi08:44
dkushwahahyunsikyang, a query regarding https://review.openstack.org/#/c/636272/08:45
patchbotpatch 636272 - tacker-specs - Adding Multi-Interface for Containerized VNF in Ta... - 3 patch sets08:45
hyunsikyanglike last time, when i found these thing i will look at it.08:45
hyunsikyangabout bugs.08:46
hyunsikyangyes08:46
*** e0ne has joined #openstack-meeting08:46
hyunsikyangi sumbitted one features . please look at it:)08:46
dkushwahahyunsikyang, is it deffer than  https://blueprints.launchpad.net/tacker/+spec/kuryr-kubernetes-integration08:46
hyunsikyangthis feature is extend the network feature for C-VNF08:47
hyunsikyangnow, when user deploy the C-VNF, user only can use one interface08:48
*** e0ne has quit IRC08:48
dkushwahahyunsikyang, through intrgrating kuryr-kubernetes. right ?08:48
hyunsikyangyes, I will use a kuryr features.08:49
dkushwahaok08:49
hyunsikyangbut, not integratiing all of it. It alreadly did.08:49
dkushwahahyunsikyang, ok, I didnt reviewed your patch, but I realized that both are same.08:50
dkushwahawill check it again08:51
dkushwahahyunsikyang, btw, Thanks for heading up for working on bugs. :)08:51
hyunsikyangyes, but it is not same. I extended it. interfaces feautures.08:51
hyunsikyangYou're welcome! I just found it, and report and fix :)08:52
hyunsikyangPhuoc helps too. but I will test new patch of last bug  soon:)08:52
dkushwahaThanks08:53
dkushwahaNothing from my side, now.08:53
dkushwahaAnyone have something more to talk?08:54
*** e0ne has joined #openstack-meeting08:54
*** iyamahat has joined #openstack-meeting08:54
*** whoami-rajat has quit IRC08:54
dkushwahaotherwise, we can close this meeting.08:54
*** e0ne has quit IRC08:56
dkushwahaThanks all for joining.08:56
*** joxyuki has left #openstack-meeting08:56
dkushwaha#endmeeting08:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:56
openstackMeeting ended Tue Feb 12 08:56:41 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-02-12-08.02.html08:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-02-12-08.02.txt08:56
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2019/tacker.2019-02-12-08.02.log.html08:56
*** priteau has joined #openstack-meeting08:59
*** tetsuro has joined #openstack-meeting09:00
*** tetsuro has quit IRC09:05
*** markvoelker has quit IRC09:05
*** tetsuro has joined #openstack-meeting09:05
*** tetsuro has quit IRC09:16
*** tssurya has joined #openstack-meeting09:17
*** tetsuro has joined #openstack-meeting09:17
*** iyamahat has quit IRC09:19
*** a-pugachev has joined #openstack-meeting09:20
*** e0ne has joined #openstack-meeting09:25
*** e0ne has quit IRC09:26
*** tetsuro has quit IRC09:39
*** jamesmcarthur has joined #openstack-meeting09:59
*** stephenfin_ is now known as stephenfin10:01
*** markvoelker has joined #openstack-meeting10:02
*** jamesmcarthur has quit IRC10:04
*** samP has quit IRC10:05
*** tashiromt has quit IRC10:11
*** belmoreira has joined #openstack-meeting10:12
*** bhagyashris has quit IRC10:25
*** markvoelker has quit IRC10:35
*** erlon has joined #openstack-meeting11:07
*** lpetrut has joined #openstack-meeting11:15
*** factor has joined #openstack-meeting11:30
*** markvoelker has joined #openstack-meeting11:32
*** tetsuro has joined #openstack-meeting11:33
*** dkushwaha has quit IRC11:38
*** tetsuro has quit IRC11:46
*** imsurit_ofc has quit IRC11:47
*** bbowen has joined #openstack-meeting11:49
*** erlon has quit IRC11:51
*** a-pugachev has quit IRC11:53
*** a-pugachev has joined #openstack-meeting11:56
*** a-pugachev has quit IRC11:59
*** markvoelker has quit IRC12:05
*** raildo has joined #openstack-meeting12:08
*** bbowen has quit IRC12:09
*** kaisers has quit IRC12:24
*** erlon has joined #openstack-meeting12:29
*** kaisers has joined #openstack-meeting12:31
*** rubasov has joined #openstack-meeting12:34
*** coreycb has quit IRC12:36
*** coreycb has joined #openstack-meeting12:37
*** lpetrut has quit IRC12:38
*** lpetrut has joined #openstack-meeting12:39
*** janki has quit IRC12:44
*** janki has joined #openstack-meeting12:44
*** markvoelker has joined #openstack-meeting13:02
*** yamamoto has quit IRC13:03
*** enriquetaso has joined #openstack-meeting13:03
*** mriedem has joined #openstack-meeting13:04
*** yamamoto has joined #openstack-meeting13:08
*** yamamoto has quit IRC13:15
*** bbowen has joined #openstack-meeting13:17
*** Liang__ has joined #openstack-meeting13:21
*** whoami-rajat has joined #openstack-meeting13:22
*** ociuhandu has joined #openstack-meeting13:26
*** sdake has joined #openstack-meeting13:32
*** markvoelker has quit IRC13:35
*** yamamoto has joined #openstack-meeting13:46
*** rbudden has joined #openstack-meeting13:47
*** vishakha has quit IRC13:50
*** davidsha has joined #openstack-meeting13:51
*** yamamoto has quit IRC13:56
*** e0ne has joined #openstack-meeting13:56
*** lajoskatona has joined #openstack-meeting13:58
*** vishakha has joined #openstack-meeting13:58
*** boden has joined #openstack-meeting13:59
*** mlavalle has joined #openstack-meeting14:00
mlavalle#startmeeting networking14:00
openstackMeeting started Tue Feb 12 14:00:30 2019 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: networking)"14:00
openstackThe meeting name has been set to 'networking'14:00
bcafarelo/14:00
haleybhi14:01
davidshao/14:01
lajoskatonahi14:01
rubasovo/14:01
mlavalle#topic Announcements14:03
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:03
*** sdake has quit IRC14:03
mlavalleOur Stein-3 milestone is around the corner, March 4 - 814:03
mlavalleany other announcements I might be missing?14:04
amotokihi14:05
mlavalleok, let's move on14:05
mlavalle#topic Blueprints14:05
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:05
*** yamamoto has joined #openstack-meeting14:06
*** yamamoto has quit IRC14:06
mlavalleDoes anyonbe have any updates on blueprints?14:06
bcafarelfor subnet onboarding, https://review.openstack.org/#/c/348080/ looks pretty close to merge (I don't see ryan around)14:07
patchbotpatch 348080 - neutron - Enable adoption of subnets into a subnet pool - 49 patch sets14:07
bcafarelbut the last issue on engineface looks strange, expert eyes welcome :)14:07
mlavalleok, i'll take a look as soon as possible14:08
bcafarelthanks mlavalle14:09
mlavalleIn regards to https://blueprints.launchpad.net/neutron/+spec/network-segment-range-management14:09
*** mriedem is now known as mriedem_snow14:10
mlavalleI did a round of reviews last week of the two patches:14:10
mlavallehttps://review.openstack.org/#/c/62470814:10
patchbotpatch 624708 - neutron - Support Network Segment Range CRUD as extensions - 19 patch sets14:10
mlavallehttps://review.openstack.org/#/c/62470914:10
patchbotpatch 624709 - neutron - Use network segment ranges for segment allocation - 19 patch sets14:10
mlavalleauthor responded to that reviews and I encourage the team to take a look at the new revisions14:11
mlavallerubasov, lajoskatona: any quick updates on https://blueprints.launchpad.net/neutron/+spec/strict-minimum-bandwidth-support?14:12
rubasovmlavalle: yes14:12
rubasovwe have good progress, but reviews are always welcome14:12
rubasovhere https://review.openstack.org/62914214:12
patchbotpatch 629142 - tempest - Add QoS policies and minimum bandwidth rule client - 5 patch sets14:12
rubasovand here https://review.openstack.org/63099914:13
patchbotpatch 630999 - neutron - New agent attribute: resources_synced - 6 patch sets14:13
rubasovboth are change series14:13
rubasovone in neutron and the other in tempest14:13
mlavalleif we merge these two series, will we be done in Stein?14:13
rubasovyes14:13
mlavalleah cool14:14
mlavalleI will take a look this week then14:14
mlavalleand encourage the team to do the same14:14
rubasovthe networking guide chapter is still to be written14:14
mlavallethanks for your hard work, rubasov and lajoskatona14:14
rubasovI'll do that soon14:14
mlavallerubasov: is gibi back? is he doing well?14:15
gibimlavalle: thanks for asking14:15
rubasovof course, thanks everyone for the help14:15
*** liuyulong has joined #openstack-meeting14:15
gibimlavalle: I'm back and rocking14:15
mlavallegibi: glad to see you around \o/14:15
gibi:)14:15
lajoskatonamlavalle: thanks for the support for the whole team14:15
mlavalleeven though I don't see njohnston_ around, we probably need to take a look at patches related to https://blueprints.launchpad.net/neutron/+spec/speed-up-neutron-bulk-creation14:17
mlavalleHere's the related patch: https://review.openstack.org/#/c/624815/14:18
patchbotpatch 624815 - neutron - Utilize bulk port creation ops in ml2 plugin - 31 patch sets14:18
mlavalleplease take a look14:18
mlavalleand we are also making an extra effort with https://blueprints.launchpad.net/neutron/+spec/openflow-based-dvr14:19
*** Liang__ has quit IRC14:19
mlavallePatches are https://review.openstack.org/#/c/52833614:19
patchbotpatch 528336 - neutron - L3 agent refactor patch - 29 patch sets14:19
mlavallehttps://review.openstack.org/#/c/47228914:20
patchbotpatch 472289 - neutron - [POC] Introduction of OpenFlow implementation of DVR. - 17 patch sets14:20
mlavallewe had some questions in an ML thread answered last week14:20
*** sdake has joined #openstack-meeting14:20
*** sdake has quit IRC14:21
mlavallethat were answered and igordc indicated he was going to continue based on the answers provided14:21
mlavalleso please be on the lookout for the next revision of those patches14:21
mlavalleanyhting else with blueprints?14:21
mlavalleok, let's move on14:23
mlavalle#topic Community goals14:23
*** openstack changes topic to "Community goals (Meeting topic: networking)"14:23
mlavalleslaweq: any comments on Python 3?14:23
slaweqhi14:23
slaweqbasically all my patches were merged14:24
slaweqso I think that most of jobs are now on Py314:24
bcafarelyay14:24
mlavalle\o/14:24
amotokineutron py3 support is most completed :)14:24
mlavallecan we claim victory on this goal yet?14:25
amotokisome stadium projects still need py3 work..14:25
slaweqI will check and update etherpad today before ci meeting but I'm almost sure that all is fine now14:25
slaweqonly some experimental jobs are not switched to py314:25
slaweqbut that can be handled later IMO14:25
*** lajoskatona has left #openstack-meeting14:25
mlavalleGreat work slaweq. Thank you very much!14:25
slaweqohh, no - we still don't have grenade jobs switched14:25
slaweqso, that is still left and I think njohnston_ is assigned to it14:26
mlavalleare you going to work on those?14:26
*** priteau has quit IRC14:26
mlavalleack14:26
slaweqif njohnston_ will not have time for that, I will probably do it14:26
slaweqI will try next week maybe14:26
mlavallegood progress on community goals this cycle14:26
slaweq+114:27
amotoki+114:27
mlavallewe are up to date with the community14:27
bcafarelnice14:27
amotokihow about py3 support in stadium projects?14:27
amotokiI plan to look into fwaas and vpnaas stuffs14:27
slaweqamotoki: I didn't have time to look at stadium at all14:27
bcafarelit may be worth start a ML thread on it (aka "hello stadium projects, what is your py3 status?")14:28
amotokislaweq: it is not surprising. you have a lot to do14:28
slaweqI can look into dynamic routing when I will have a while :)14:28
slaweqamotoki: as any of us :)14:28
amotokiI think this is worth checked http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002364.html14:29
*** erlon has quit IRC14:30
mlavalleamotoki: when you say look into fwaas and vpnaas, do you intend to work on those py3 convertions?14:30
amotokimlavalle: regarding neutron-fwaas, the func test is failing around oslo.privsep14:30
amotokimlavalle: other stuffs in neutron-fwaas seems to work well at a glance14:31
amotokiperhaps py3 convention have been covered.14:31
*** markvoelker has joined #openstack-meeting14:32
amotokiI haven't checked vpnaas stuffs yet.14:32
mlavallecool, I'll also take a look14:32
mlavallelet's move on14:33
amotokione thing14:33
mlavalle#topic Bugs14:33
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:33
mlavalle#undo14:33
openstackRemoving item from minutes: #topic Bugs14:33
mlavalleamotoki: go ahead14:33
amotokiregarding policy-in-code, some patches are waiting final reviews14:33
amotokiplease check open reviews in https://review.openstack.org/#/q/topic:bp/neutron-policy-in-code+(status:open+OR+status:merged)14:33
slaweqI saw Your patches today and I have opened them in tabs but still didn't get to them :/14:34
*** lbragstad has joined #openstack-meeting14:34
slaweqbut I will, I promise :)14:34
amotokislaweq:  thanks. It is an improvement of the policy reference. others need to land to complete the blueprint.14:35
mlavalleamotoki: thanks, I will also take a look14:35
*** sdake has joined #openstack-meeting14:35
amotokithat's all from me on policy-in-code.14:35
mlavalle#topic Bugs14:35
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:35
mlavalleOur deputy last week was amotoki14:36
mlavallehere's the report: http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002597.html14:36
amotoki http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002599.html is the updated version14:36
*** sdake has quit IRC14:37
*** sdake_ has joined #openstack-meeting14:37
mlavalleamotoki: so it seems it was a relatively quiet week14:38
amotokiyeah, the last week was quiet14:38
mlavallenothing seems on fire14:38
amotokibug 1815463 is worth investigated but I don't think it is critical.14:39
openstackbug 1815463 in neutron "[dev] Agent RPC version does not auto upgrade if neutron-server restart first" [Undecided,New] https://launchpad.net/bugs/181546314:39
mlavalleamotoki: ok, will look at it14:40
mlavalleand I will ping Sridark regarding the FWaaS bug14:40
amotokimlavalle: I will look into that one this week too. I travelled bus trip last week.14:40
mlavallecool amotoki14:40
mlavalleThis week our bugs deputy is haleyb14:41
haleybyes, and hopefully it's just not as busy as last week14:41
* mlavalle crosses fingers14:42
mlavalleany other bugs we should discuss today?14:42
mlavalleok, let's move on14:43
mlavalle#topic neutron-lib14:43
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:43
mlavalleboden: you around or should I do the update?14:44
bodenmlavalle here14:44
*** e0ne has quit IRC14:44
mlavallego ahead14:44
boden1 quick thing I'd like to mention14:44
bodenlast week we merged my patch to remove neutron.common.rpc in https://review.openstack.org/#/c/634790/14:45
patchbotpatch 634790 - neutron - remove neutron.common.rpc (MERGED) - 2 patch sets14:45
bodenunfortunately I missed a few projects; those projects who were not importing neutron.common.rpc, but just mocking it as a string14:45
bodenI've submitted patches for those here: https://review.openstack.org/#/q/topic:use-lib-rpc+status:open14:45
bodenI'll try to watch for these types of consumers in the future and hopefully reviewers of my patches can help me double check that I didn't miss anything14:46
mlavallegood point14:46
slaweqyep, thx boden :)14:46
mlavalleyeah, we reviewers share this responsiblity14:46
bodenIMHO it's better to import and use mock.patch.object() rather than a global mock.patch() with a string package name, but it is what it is14:47
bodenanyway, that's all I have14:47
mlavallethanks for the update14:47
*** janki has quit IRC14:47
mlavalle#topic On demand agenda14:48
*** openstack changes topic to "On demand agenda (Meeting topic: networking)"14:48
mlavalleanything else we should discuss today?14:48
*** hongbin has joined #openstack-meeting14:49
bcafarelI may have missed it, but amotoki, did you discuss https://bugs.launchpad.net/neutron/+bug/1811352/comments/5 in a previous meeting?14:49
openstackLaunchpad bug 1811352 in neutron "[RFE] Include neutron CLI floatingip port-forwarding support" [Wishlist,New]14:49
amotokibcafarel: not yet14:49
amotokiDo we discuss it now? I can share my point.14:50
mlavallego ahead14:50
amotokisure14:50
amotokiAs of now, some features in neutron repo are covered by OSC itself and some are covered by OSC neutronclient plugin14:50
amotokiexamples of the latter are trunk or network log.14:50
amotokibut it brings some confusion and the criteria on which route we should go.14:51
amotokiso my idea is to implement all neutron features in OSC (+ openstacksdk) first.14:51
*** awaugama has joined #openstack-meeting14:51
mlavalleyes, that makes sense14:52
amotokinote that all stadium project support will still be implemented by neutronclient OSC plugin.14:52
slaweqdo we have plans to move existing features from neutronclient to OSC and SDK?14:52
amotokislaweq: good poiint14:53
amotokiSDK support is straight-forward, but migration from OSC plugin to OSC needs to be careful.14:53
amotokiideally I would like to move existing features to OSC14:53
mlavalleshould it be a blueprint for the TRain cycle?14:54
amotokimlavalle: fair enough14:54
amotokiit is not targeted to Stein of course :)14:54
mlavallewe can declare it an official blueprint, track it weekly and ask for volunteers14:54
mlavalledoes it make sense?14:55
slaweqI can help especially with SDK14:55
amotoki+114:55
mlavalleok, decided14:55
bcafarel+1 and hope to have time to help, as I love the idea14:55
slaweq+114:55
mlavallebcafarel, amotoki: thanks for bringing this up14:55
amotokiyou're welcome14:56
mlavalleanything else we should discuss today?14:56
*** boden has left #openstack-meeting14:56
mlavalleenjoy the rest of your week!14:56
mlavalleand thanks for attending14:56
slaweqthx, You too :)14:56
mlavalle#endmeeting14:56
davidshathanks!14:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:56
openstackMeeting ended Tue Feb 12 14:56:56 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:56
slaweqo/14:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-02-12-14.00.html14:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-02-12-14.00.txt14:57
openstackLog:            http://eavesdrop.openstack.org/meetings/networking/2019/networking.2019-02-12-14.00.log.html14:57
bcafarelo/14:57
amotokio/14:57
ralonsoh#startmeeting neutron_qos15:00
*** eharney has joined #openstack-meeting15:00
mlavalleo/15:00
openstackMeeting started Tue Feb 12 15:00:39 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
ralonsohHello15:00
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:00
openstackThe meeting name has been set to 'neutron_qos'15:00
mlavalleHola15:00
rubasovo/15:00
ralonsohhola!15:00
*** cloudrancher has joined #openstack-meeting15:01
ralonsohlet's give some time, one more minute15:01
mlavalleno problem15:01
ralonsohdavidsha, if we have time, at the end, we have your topic in the agenda15:02
ralonsohlet's start15:02
ralonsoh#topic RFEs15:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:02
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/157898915:02
openstackLaunchpad bug 1578989 in neutron "[RFE] Strict minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Bence Romsics (bence-romsics)15:02
ralonsohlinks -->15:02
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/neutron+branch:master+topic:minimum-bandwidth-allocation-placement-api15:02
ralonsoh#link https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/bandwidth-resource-provider15:02
ralonsoh#link https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placement-api+(status:open+OR+status:merged)+project:openstack/tempest15:02
ralonsoh#link https://review.openstack.org/#/c/629253/15:02
patchbotpatch 629253 - tempest - Minimum bandwidth allocation with placement - 6 patch sets15:02
ralonsohrubasov, any update?15:02
rubasovI guess that's mine :-)15:02
rubasovsince we're close to freeze I'll try to give a thorough update15:03
rubasovI think we're on good track to merge this in stein15:03
rubasovstuff in review:15:03
rubasovlajoskatona's end to end test in tempest (series): https://review.openstack.org/62914215:03
patchbotpatch 629142 - tempest - Add QoS policies and minimum bandwidth rule client - 5 patch sets15:03
rubasovrubasov's neutron patch series (placement sync and changes to port binding) (series): https://review.openstack.org/63099915:04
patchbotpatch 630999 - neutron - New agent attribute: resources_synced - 6 patch sets15:04
rubasovthe last patch in the neutron series will need a new neutron-lib release15:04
rubasovif these get merged the neutron side of the feature is basically working15:05
ralonsohrubasov, maybe you can ask boden if this is a good time for it (to add https://review.openstack.org/#/c/626210/)15:05
patchbotpatch 626210 - neutron-lib - New agent attribute: resources_synced (MERGED) - 5 patch sets15:05
mlavallerubasov: is the stuff you need in neutron-lib already merged?15:05
ralonsohyes15:05
rubasovit's merged, but not released15:05
*** markvoelker has quit IRC15:05
ralonsohpatch: https://review.openstack.org/#/c/626210/15:05
patchbotpatch 626210 - neutron-lib - New agent attribute: resources_synced (MERGED) - 5 patch sets15:05
rubasovralonsoh: I'll ask boden15:05
ralonsohperfect15:05
ralonsohand then we still have 5 patches in out side (Neutron), to be reviewed15:06
rubasovstuff in flight still for stein:15:06
mlavallerubasov: ok, if you need help with that, please ping me15:06
rubasovmlavalle: will do, thanks15:06
rubasova fullstack test for the recovery of transient errors in placement sync: lajoskatona is working on it15:07
*** ianychoi has quit IRC15:07
rubasova patch to reject as NotImplemented: update of qos min-bw rule on bound ports: rubasov is working on it15:07
rubasovnetworking guide chapter on the feature: rubasov will work on it after the previous one15:07
*** ianychoi has joined #openstack-meeting15:07
rubasovdo you think we are missing anything else (on neutron side) for stein?15:08
ralonsohrubasov: so you will stop any qos update for bound ports, for now, is that correct?15:08
ralonsohqos update for min-bw15:08
rubasovralonsoh: only for min-bw rules15:09
rubasovralonsoh: yes15:09
ralonsohok15:09
*** e0ne has joined #openstack-meeting15:09
*** hongbin has quit IRC15:09
rubasovfor example do we need any other kind of documenatation beyond api-ref and networking guide?15:09
ralonsohIMO, everything related to placement + qos should be there (api-ref and networking)15:10
ralonsohplacement + BW scheduling15:10
rubasovralonsoh: ok15:11
rubasovthen a bit about the nova side15:11
ralonsohof course, if needed, we can add more documentation on demand15:11
rubasovmaybe gibi pops up and corrects me :-)15:11
ralonsohsure, in the nova side for the sheduling15:11
rubasovto my understanding the nova side of the feature has made really good progress15:11
*** annp has joined #openstack-meeting15:11
rubasovlots and lots of changes were merged15:11
rubasovif you want to test end to end there's one gotcha:15:12
rubasovthe current patch series in nova leaves the feature turned off15:12
rubasovthere will be a patch still in stein turning it on (introducing a new microversion)15:12
rubasovbut until then you have to flip this15:12
rubasovhttps://github.com/openstack/nova/blob/ac1fafb84c94ed9f8e610c7c3e152e38aef844ed/nova/api/openstack/common.py#L55215:12
*** hongbin has joined #openstack-meeting15:12
gibirubasov i scorrect15:12
gibiI'm in the process to propose the last patch that introduces the new microversion in the nova API15:13
ralonsohrubasov, good stuff for testing, thanks!15:13
rubasovralonsoh: of course15:13
rubasovthat's about all I had in mind15:14
ralonsohrubasov, gibi and lajoskatona: thank you very much!15:14
rubasovralonsoh: thanks for the reviews15:15
ralonsohlet's move to the next one15:15
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/177762715:15
openstackLaunchpad bug 1777627 in neutron "RFE: QoS – rule's management (set,delete, show…) requires <qos-policy> parameter in addition to <rule-id>" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel)15:15
mlavallefor this one15:15
ralonsoh#link https://review.openstack.org/#/c/613820/: a couple of review comments to be addresses15:15
patchbotpatch 613820 - neutron - Define qos-rules-alias extension - 5 patch sets15:15
ralonsohaddressed15:15
*** yamamoto has joined #openstack-meeting15:16
mlavalleI need to deploy the patch and do the final testing15:16
mlavallewith my job change, my dev infra is in "flux"15:16
mlavallebut I am getting to a point where I can deploy this week15:16
mlavalleso I intend to finish it this week15:16
ralonsohmlavalle, if you want extra help, ping me15:17
mlavalleralonsoh: I will, thanks15:17
ralonsohok, let's move to the next one15:18
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/179692515:18
openstackLaunchpad bug 1796925 in neutron "[RFE] port forwarding floating IP QoS" [Wishlist,Fix released] - Assigned to LIU Yulong (dragon889)15:18
ralonsoh#link https://review.openstack.org/#/c/631448/15:18
patchbotpatch 631448 - neutron - Add port forwarding floating IP QoS (MERGED) - 5 patch sets15:18
ralonsohThe patch was merged last week15:18
ralonsohthis patch was for the agent and the server side15:18
ralonsohliuyulong, do you think we can close this RFE?15:19
liuyulongNo, I'm working on the DOC.15:20
mlavallethanks liuyulong15:20
ralonsohliuyulong, ok, perfect (yes, I always forget the docs)15:20
mlavalleBTW, let's not forget to congratulate our new Neutron core, liuyulong15:20
ralonsohliuyulong+++15:20
ralonsohcongrats!15:20
davidshacongrats!15:21
liuyulongThanks, : )15:21
mlavalleliuyulong: did you have a great Spring Festival? Happy new year15:21
ralonsoh(he's still celebrating!)15:22
mlavalleit seems so. LOL15:22
ralonsohlast one15:22
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/156096315:22
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)15:22
ralonsoh#link https://review.openstack.org/#/q/topic:bug/1560963+(status:open)15:23
ralonsohpatches are in good shape, lots of reviews15:23
ralonsohaddressing last comments15:23
ralonsohno blockers, no problem15:23
mlavalleGreat. Thanks15:23
*** TxGirlGeek has joined #openstack-meeting15:23
ralonsohjust one comment: https://review.openstack.org/#/c/406841/15:24
patchbotpatch 406841 - neutron - Add QoS minimum egress bandwidth rule into ovs-agent - 21 patch sets15:24
ralonsohI know this patch is big and scary, but you are welcome to review it15:24
ralonsoh(maybe if I don't have reviews, I'll split it)15:24
mlavallethe ones for network segment range management are scarier15:25
mlavalleit's ok15:25
ralonsohhehehe15:25
mlavallewe are machos here and we can take it15:25
ralonsohhahahahaha15:25
ralonsohand that's all for RFEs15:25
ralonsoh#topic Bugs15:25
*** yamamoto has quit IRC15:25
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:25
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/181257615:26
openstackLaunchpad bug 1812576 in neutron "L2 agent do not clear old QoS rules after restart" [Medium,Fix released] - Assigned to Chengqian Liu (liuchengqian90)15:26
ralonsoh#link https://review.openstack.org/#/c/632014/15:26
patchbotpatch 632014 - neutron - Clear old rules that have been applied before appl... (MERGED) - 27 patch sets15:26
ralonsohpatch merged, congrats!15:26
ralonsohI'll remove it from the list next week15:26
ralonsohnext one15:26
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/178518915:26
openstackLaunchpad bug 1785189 in neutron "Floatingip and router bandwidth speed limit failure" [Medium,In progress]15:26
*** liuyulong has quit IRC15:26
ralonsoh#link: https://review.openstack.org/#/c/596637/15:26
patchbotpatch 596637 - neutron - Fix bug when floatingip and router bandwidth speed... - 4 patch sets15:26
ralonsohok, let's see15:27
ralonsohI replied in the bug and launchpad15:27
ralonsohI tested this by using iperf both in the route namespace and in a VM15:27
ralonsohof course, the VM test makes more sense, but is almost the same15:27
mlavallethanks for verifying it15:28
ralonsohIf I define, in the filtered interface (the one shaping the traffic)15:28
ralonsoha MTU of 64KB15:28
ralonsohand the traffic doesn't exceed this MTU (it's not possible, BTW)15:29
ralonsohthere is not ip fragmentation and no retransmissions (just a few)15:29
ralonsohI tested several BW and I don't see any performance degradation15:29
ralonsohand, BTW, the packets inside the filter won't be augmented (with new headers or anything else)15:30
*** priteau has joined #openstack-meeting15:31
ralonsohso, IMO, 64KB (for IPv4 the maximum allowed size) is enough15:31
mlavalleok15:31
mlavallegreat work15:31
ralonsohmore info in the bug, that's all15:31
davidshathanks15:31
davidshamlavalle: would floating ip bw be something to keep in mind when working on ovs dvr?15:32
*** njohnston_ has quit IRC15:32
mlavalledavidsha: I think it is15:32
davidshamlavalle: kk15:32
mlavallebut we can release implement it first without worrying about it15:32
mlavalleget it working and then we iterate with the QoS stuff15:33
*** e0ne has quit IRC15:33
mlavallewe cannot implement everythin at the same timne15:33
davidshaTrue!15:33
ralonsohok, let's go for the last bug15:34
ralonsohhttps://bugs.launchpad.net/neutron/+bug/181561815:34
openstackLaunchpad bug 1815618 in neutron "cannot update qos rule" [High,Confirmed] - Assigned to Bence Romsics (bence-romsics)15:34
ralonsohcreated 42 mins ago15:35
rubasovI just opened that :-)15:35
ralonsohyes15:35
ralonsohI didn't have time to review it15:35
ralonsohrubasov, do you know what is happening?15:35
rubasovit's a small problem of updating some qos rules with osc15:35
rubasovI didn't fully locate the client side of it yet - whether it's in pyhton-openstackclient or python-neutronclient15:36
rubasovbut I can clearly reproduce it15:36
rubasovand I see in tcpdump what's the problem15:36
rubasovalso the server side request validation could be improved to avoid a 500 internal server error15:37
ralonsohthat means, probably, is in the server side15:37
rubasovonly some of it15:37
rubasovneutronclient can update15:37
rubasovosc cannot15:37
ralonsohhmmm15:37
ralonsohbtw, you have assigned yourself this patch15:37
ralonsohbug15:38
ralonsohare you going to work on it?15:38
*** jrbalderrama has joined #openstack-meeting15:38
rubasovyep, I'll go on fixing it15:38
ralonsohperfect!!15:38
ralonsohI don't have anything else in the etherpad backlog (for bugs)15:38
ralonsohSomething else?15:39
mlavallenot from me15:39
rubasovnot from me too15:39
ralonsohcool15:39
ralonsoh#topic Open Discussion15:39
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:39
ralonsoh#link https://bugs.launchpad.net/neutron/+bug/1476527 - Adoption of Neutron Classifier API into QoS15:39
openstackLaunchpad bug 1476527 in neutron "[RFE] Add common classifier resource" [Wishlist,Triaged] - Assigned to Igor D.C. (igordcard)15:39
ralonsohdavidsha,15:39
ralonsohplease15:39
davidshaThanks15:39
davidshaWe merged the last patch for the Neutron Classifier API 2 weeks back15:40
*** armax has joined #openstack-meeting15:40
*** liuyulong has joined #openstack-meeting15:41
*** Luzi has quit IRC15:41
davidshaWe originally were aiming to have it adopted into QoS to have targeted traffic tagging fro DSCP and bw limiting, how do people feel about enabling these features now?15:41
*** e0ne has joined #openstack-meeting15:41
*** macza has joined #openstack-meeting15:42
ralonsohthat means we need to use this extension to classify the traffic15:42
davidshaI'm working on some patches at the moment to see what challenges there could be to integrating the features15:42
mlavalleare the patches a PoC?15:43
davidsharalonsoh: yes, it would be an optional parameter15:43
davidshamlavalle: at the moment yes, I put some up earlier today15:43
mlavallelet's take a look15:43
davidshahttps://review.openstack.org/#/c/636330/15:44
patchbotpatch 636330 - neutron-lib - (PoC)Classification field in Neutron DSCP - 2 patch sets15:44
mlavalleand go from there15:44
davidshahttps://review.openstack.org/#/c/636333/115:44
patchbotpatch 636333 - neutron - (PoC)Classification field in Neutron DSCP - 1 patch set15:44
davidshahttps://review.openstack.org/#/c/636336/115:44
patchbotpatch 636336 - neutron-classifier - Migrating Classification Groups - 1 patch set15:44
liuyulongJust lost my connection, reading the log...15:44
davidshaThose are the three main patches, I have a few others for OSC15:44
ralonsohwith those patches will be able to shape traffic depending on the DSCP marks15:45
davidshaNo, with these patches depending on the traffic leaving a port you could assign a DSCP mark to it15:46
ralonsohok15:46
davidshaIf I expand on the validation of multiple QoS Rules you could have multiple DSCP marks depending what traffic you want tagged15:47
*** diablo_rojo has joined #openstack-meeting15:47
*** cloudrancher has quit IRC15:47
ralonsohthat means you need more than one DSCP rule per QoS policy15:47
ralonsohand per direction15:47
davidshapotentially, and there wouldn't be much point tagging traffic coming into the port15:48
davidshaBut for example if you want IPv4 traffic destined for a certain host to have a certain DSCP mark and all SSH traffic leaving the port to have another that would be a potential use case for have multiple targeted dscp rules.15:49
ralonsohhmmm the potential problem is, only if you have this extension enabled, more than one DSCP rule should be allowed15:49
ralonsohor maybe just a verification to have several DSCP rules, all of them different15:50
davidshaI believe the QoS rules have validation to make sure you don't bw limit less than the garuntee right?15:50
ralonsohI think so, I need to check it15:50
davidshaYou could compare the classification_group_id and if it matches a DSCP rule already in the policy then throw an exception15:51
*** mriedem_snow is now known as mriedem15:52
davidshahttps://github.com/openstack/neutron/blob/master/neutron/objects/qos/qos_policy_validator.py#L2915:52
*** erlon has joined #openstack-meeting15:52
ralonsohyes, I was there right now15:53
ralonsohI think you can extend this function15:53
ralonsohnot only for BW check15:53
mlavalleI have to leave for an internal meeting15:54
mlavalleo/15:54
davidshacya!15:54
ralonsohbye15:54
ralonsohdavidsha, ok so I think we need to take a look at your PoC patches15:54
ralonsohand deploy to test them15:55
ralonsohbut IMO is a good idea15:55
davidsharalonsoh: kk, at the moment they only implement the API side15:55
ralonsohBTW, I don't know if a RFE will be needed, just in case15:55
davidshaI'll have the backend driver by next week hopefully15:55
davidshakk, I have an old one from 3 years ago if that sounds appealing ;)15:56
ralonsohhahaha yes now I remember15:56
ralonsohok, something else to be discussed?15:57
ralonsohthank you all! see you in gerrit!15:58
davidshaThanks! talk to you!15:58
ralonsoh#endmeeting15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:58
rubasovthank you15:58
openstackMeeting ended Tue Feb 12 15:58:20 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-02-12-15.00.html15:58
rubasovbye15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-02-12-15.00.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2019/neutron_qos.2019-02-12-15.00.log.html15:58
slaweq#startmeeting neutron_ci16:00
slaweqhi16:00
openstackMeeting started Tue Feb 12 16:00:25 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
*** mjturek has joined #openstack-meeting16:00
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:00
openstackThe meeting name has been set to 'neutron_ci'16:00
*** erlon has quit IRC16:00
slaweqlets wait few minutes for other people to join16:02
*** markvoelker has joined #openstack-meeting16:03
slaweqbut looks like there is no crowd today :)16:03
*** lpetrut has quit IRC16:03
ralonsohhi! I'm still here16:04
slaweqhi ralonsoh, good to see You :)16:04
slaweqI know that mlavalle will not be available today16:04
bcafarelo/16:04
slaweqbut maybe haleyb and bcafarel will join16:04
slaweqhi bcafarel :)16:04
slaweqhongbin: are You around for CI meeting?16:05
bcafarelmy spider sense was telling me I should switch IRC channel :)16:05
haleyboh, hi, looking at bugs16:05
hongbino/16:05
slaweqok, so now I think we can start :)16:05
slaweqwelcome everyone!16:05
slaweq#topic Actions from previous meetings16:05
*** openstack changes topic to "Actions from previous meetings (Meeting topic: neutron_ci)"16:05
slaweqfirst one was:16:05
slaweqmlavalle to continue investigate why L3 agent is considered as down and cause trunk tests fail16:05
*** jamesmcarthur has joined #openstack-meeting16:06
slaweqmlavalle gave me some update about his findings on it16:06
slaweqhe said that problem is with the test migrating router from HA to dvr/legacy. That migration implies deleting the existing router state_change_monitor16:06
slaweqso we try to execute 'kill', '-15', 'pid'' and that cause agent "dead" basically16:06
slaweqplease look here: http://paste.openstack.org/show/744001/16:06
*** wwriverrat has quit IRC16:07
slaweqpossibly we are missing filter in https://github.com/openstack/neutron/blob/master/etc/neutron/rootwrap.d/l3.filters for kill neutron-keepalived-state-change process16:07
slaweqhaleyb: do You think that it is possible?16:08
haleybso it's getting an error trying to kill the state change monitor?16:08
slaweqIIUC what mlavalle was saying than yes :)16:09
slaweqand indeed IMO this KillCommand filter is missing there16:09
slaweqso that can be some issue16:10
haleybyes, that missing KillFilter could be an issue16:10
slaweqso mlavalle will send patch to add it and we will see if that will help16:11
haleyb+116:11
slaweq#action mlavalle to check if adding KillFilter for neutron-keepalived-state-change will solve issues with L3 agent in dvr jobs16:12
bcafareland it worked before without filter?16:12
slaweqbcafarel: I think that possibly it wasn't killing keepalived-state-change process but agent was running fine16:12
slaweqmaybe change py27->py36 for this job triggered this somehow16:13
slaweqalso mlavalle told me that it happens during router migration16:13
slaweqfrom ha to dvr/legacy16:13
slaweqand such scenario isn't tested in other jobs16:14
*** wwriverrat has joined #openstack-meeting16:14
slaweqso it is possible that python 36 triggered that somehow16:14
slaweqcan we move on or do You have anything else to add here?16:15
bcafarelnothing, it was mostly personal curiosity :)16:15
bcafarelthanks slaweq16:15
*** jrbalderrama has quit IRC16:16
slaweqbcafarel: sure :) I'm also wondering how it may be possible16:16
slaweqok, lets move on16:17
slaweqnext action was:16:17
slaweqnjohnston Work on grenade job transition16:17
slaweqI think he didn't make any progress on this recently16:17
*** wwriverrat has quit IRC16:18
*** wwriverrat has joined #openstack-meeting16:18
slaweqnext one was:16:18
bcafarelI sent https://review.openstack.org/#/c/636356/ to see how it goes with simple change in the meantime16:18
patchbotpatch 636356 - neutron - Switch grenade jobs to python3 - 1 patch set16:18
slaweqslaweq to check if new ovsdb monitor implementation can allow to listen only for events from specific bridge16:19
slaweqbcafarel: thx, lets get back to it in python3 section, ok?16:19
bcafarelslaweq: oops sorry multitasking is bad for attention16:20
slaweqbcafarel: no, it's fine :)16:20
slaweqaccording to ovsdb monitor, I checked that SimpleInterfaceMonitor isn’t moved to new implementation yet so there was nothing to check for now.16:20
slaweqralonsoh is still working on it, right?16:20
ralonsohslaweq, yes, but I'm still facing the same functional tests problems16:21
ralonsohand I don't know how to solve them16:21
ralonsohI think this is a race condition16:21
ralonsohbut I can't probe it16:21
slaweqralonsoh: do You have link to patch?16:21
ralonsoh#link https://review.openstack.org/#/c/612400/16:21
patchbotpatch 612400 - neutron - [WIP] Add native OVSDB implementation for polling ... - 18 patch sets16:21
slaweqa lot of events logged: http://logs.openstack.org/00/612400/18/check/neutron-functional-python27/6e7d69b/job-output.txt.gz#_2019-02-07_12_04_15_37686916:23
slaweqis it normal?16:23
ralonsohno, just for testing (is in the patch comment)16:24
slaweqbut except that "issue" I don't see any failed test in PS18 in functional tests job16:24
ralonsohsorry, neutron-fullstack16:26
ralonsohtest_l2_agent_restart(OVS,VLANs,openflow-cli)16:26
ralonsohalways the same16:26
slaweqralonsoh: ok, I will take a look at logs from this test later16:27
ralonsohthanks!16:27
slaweqmaybe I will find something :)16:27
slaweqok, lets move on16:27
slaweqlast action from last week was:16:27
slaweqnjohnston to take care of periodic UT jobs failures16:27
*** manjeets has joined #openstack-meeting16:27
slaweqI know that he fixed this issue as periodic jobs are fine now16:27
slaweqbut I don't have link to specific patch16:27
slaweqok, anything else You want to ask/add about actions from last week?16:29
slaweqok, lets move on then16:30
slaweq#topic Python 316:30
*** openstack changes topic to "Python 3 (Meeting topic: neutron_ci)"16:30
slaweqEtherpad: https://etherpad.openstack.org/p/neutron_ci_python316:31
slaweqFYI: after we merged switch of some jobs to py3 versions I pushed patch to update Grafana: https://review.openstack.org/63635916:31
patchbotpatch 636359 - openstack-infra/project-config - Add new python 3 Neutron jobs to grafana dashboard - 1 patch set16:31
slaweqfor now from gate/check queues we are only missing:16:32
slaweq* neutron-tempest-dvr-ha-multinode-full - patch in progress https://review.openstack.org/63397916:32
patchbotpatch 633979 - neutron - Migrate neutron-tempest-dvr-ha-multinode-full job ... - 7 patch sets16:32
slaweq* neutron-grenade-multinode - patch with new job already proposed: https://review.openstack.org/#/c/622612/  but is failing16:32
patchbotpatch 622612 - openstack-dev/grenade - Add grenade-multinode-py3 job - 3 patch sets16:32
slaweq* neutron-grenade-dvr-multinode - should be done when above job will be done,16:32
slaweqbcafarel: so according to Your patch, I think You should rebase/recheck this patch from njohnston https://review.openstack.org/#/c/622612/ and get this merged16:33
patchbotpatch 622612 - openstack-dev/grenade - Add grenade-multinode-py3 job - 3 patch sets16:33
slaweqthen we can switch to use this job in neutron16:33
slaweqwhat do You think?16:34
bcafarelhaving the job defined in grenade itself will be nice indeed16:34
*** markvoelker has quit IRC16:35
bcafarelI'll check once we have some initial results on https://review.openstack.org/#/c/636356/ (just enabling python 3 on our side)16:35
patchbotpatch 636356 - neutron - Switch grenade jobs to python3 - 1 patch set16:35
slaweqok16:36
slaweq#action bcafarel to continue work on grafana jobs switch to python 316:36
slaweqthx bcafarel16:36
slaweq:)16:36
bcafarel:)16:36
slaweqthat's all from my side according to python 316:36
slaweqdo You want to add anything?16:36
bcafarellist is getting shorter and shorter that's good :)16:38
slaweqindeed :)16:38
*** annp has quit IRC16:38
slaweqok, lets move on16:38
slaweq#topic Grafana16:38
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:38
slaweq#link http://grafana.openstack.org/dashboard/db/neutron-failure-rate16:38
slaweqI don't see anything "very bad" in dashboard16:40
slaweqthings are running as usual16:41
slaweqdo You see anything special what You want to discuss related to grafana?16:41
slaweqok, so I will take this as no :)16:42
slaweqnext topic16:42
slaweq#topic fullstack/functional16:42
*** openstack changes topic to "fullstack/functional (Meeting topic: neutron_ci)"16:42
slaweq2 things here16:43
slaweqfirst, about https://review.openstack.org/#/c/629420/ -16:43
patchbotpatch 629420 - neutron - Revert "Mark mysql related functional tests as uns... - 3 patch sets16:43
slaweqI was thinking about this a bit today16:43
slaweqand I think that maybe I can add new decorator, something like "skip_if_timeout"16:43
slaweqit would be similar to unstable_test() but will skip only if timeout exception would be raised in test16:44
slaweqthat way we can still track how many times this issue occurs and see other failures properly16:44
slaweqwhat do You think about this idea?16:45
haleybi like it better than using unstable_test since it is only catching one condition16:45
slaweqhaleyb: thx, so I will go with it tomorrow :)16:46
bcafareltrying to think of situations where timeout would be an actual failure (that we would then miss)16:46
bcafarelbut it sounds reasonable indeed16:46
slaweq#action slaweq to propose patch with new decorator skip_if_timeout in functional tests16:46
hongbin+116:47
slaweqbcafarel: yes, it may happen but it's still better than how it's now :)16:47
bcafareldefinitely!16:47
slaweqok, and second thing related to functional tests for today is new (old) https://bugs.launchpad.net/neutron/+bug/181514216:48
openstackLaunchpad bug 1815142 in neutron "ovsdbapp.exceptions.TimeoutException in functional tests" [High,Confirmed]16:48
slaweqit hits us from time to time16:48
slaweqTBH I suspect that it may be similar issue like with those db tests and it's just slow VM16:49
slaweqbut maybe we can ask otherwiseguy to look at it again16:49
slaweqthats all from my side regarding fullstack/functional jobs16:51
slaweqdo You want to add anything else?16:51
slaweqok, so let's move on then16:53
slaweq#topic Tempest/Scenario16:53
*** openstack changes topic to "Tempest/Scenario (Meeting topic: neutron_ci)"16:53
slaweqwe still have some random ssh failure issues in scenario jobs16:53
slaweqbut that is "know" issue and I don't have any updates about that16:53
slaweqI today found some new issue which happend at least 2 times in linuxbridge job:16:54
slaweqhttps://bugs.launchpad.net/neutron/+bug/181558516:54
openstackLaunchpad bug 1815585 in neutron "Floating IP status failed to transition to DOWN in neutron-tempest-plugin-scenario-linuxbridge" [High,Confirmed]16:54
slaweqare You aware of such problem?16:54
haleybi am16:54
slaweqdo You know what can be a reason of it?16:55
haleybalthough my initial debugging did not find an answer.  basically when the port is removed from the instance, we expect the floating status to change, but it didn't16:56
haleybat least that is what the test is doing16:56
*** TxGirlGeek has quit IRC16:57
slaweqhaleyb: and of course when doing it locally it works fine, right?16:57
*** sridharg has quit IRC16:58
*** rossella_s has quit IRC16:58
haleybit seemed to16:58
slaweq:/16:59
slaweqok, bug is reported, for now it not happens very often16:59
slaweqmaybe someone will find culprit :)16:59
slaweqwe are running out of time16:59
slaweqso thx for attending16:59
slaweqand see You all next week :)16:59
slaweq#endmeeting16:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"16:59
openstackMeeting ended Tue Feb 12 16:59:53 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-02-12-16.00.html16:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-02-12-16.00.txt16:59
*** hongbin has quit IRC16:59
slaweqo/16:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ci/2019/neutron_ci.2019-02-12-16.00.log.html16:59
*** sdake_ has quit IRC17:01
bcafarelo/17:01
*** sdake has joined #openstack-meeting17:02
*** liuyulong has quit IRC17:09
*** aojea has quit IRC17:14
*** aagate has joined #openstack-meeting17:20
*** e0ne has quit IRC17:27
*** _pewp_ has quit IRC17:27
*** rossella_s has joined #openstack-meeting17:27
*** _pewp_ has joined #openstack-meeting17:28
*** jamesmcarthur has quit IRC17:31
*** jamesmcarthur_ has joined #openstack-meeting17:32
*** markvoelker has joined #openstack-meeting17:32
*** armax has quit IRC17:32
*** armax has joined #openstack-meeting17:33
*** whoami-rajat has quit IRC17:36
*** anteaya has joined #openstack-meeting17:38
*** jamesmcarthur_ has quit IRC17:42
*** e0ne has joined #openstack-meeting17:43
*** yamamoto has joined #openstack-meeting17:44
*** sdake has quit IRC17:44
*** mriedem is now known as mriedem_afk17:45
*** dtrainor has quit IRC17:46
*** sdake has joined #openstack-meeting17:46
*** gyee has joined #openstack-meeting17:47
*** dtrainor has joined #openstack-meeting17:48
*** yamamoto has quit IRC17:48
*** davidsha has quit IRC17:51
*** jamesmcarthur has joined #openstack-meeting17:51
*** armax has quit IRC17:53
*** jamesmcarthur has quit IRC17:56
*** jamesmcarthur has joined #openstack-meeting17:58
*** jamesmcarthur has quit IRC17:58
*** kopecmartin is now known as kopecmartin|off17:58
*** mlavalle has left #openstack-meeting18:00
*** jamesmcarthur has joined #openstack-meeting18:01
*** artom has quit IRC18:04
*** markvoelker has quit IRC18:06
*** jamesmcarthur has quit IRC18:07
*** jamesmcarthur has joined #openstack-meeting18:08
*** wwriverrat has quit IRC18:09
*** tssurya has quit IRC18:09
*** wwriverrat has joined #openstack-meeting18:10
*** yamamoto has joined #openstack-meeting18:11
*** jamesmcarthur has quit IRC18:12
*** imacdonn has quit IRC18:24
*** imacdonn has joined #openstack-meeting18:25
*** armax has joined #openstack-meeting18:31
*** eharney has quit IRC18:33
*** ralonsoh has quit IRC18:37
*** ociuhandu_ has joined #openstack-meeting18:43
*** sdake has quit IRC18:44
*** ociuhandu has quit IRC18:47
*** priteau has quit IRC18:47
*** ociuhandu_ has quit IRC18:48
*** sdake has joined #openstack-meeting18:51
*** ociuhandu has joined #openstack-meeting18:55
*** jamesmcarthur has joined #openstack-meeting18:56
*** jamesmcarthur has quit IRC18:58
*** slaweq has quit IRC18:59
*** ociuhandu has quit IRC18:59
*** ociuhandu has joined #openstack-meeting19:00
clarkbHello Infra team. Anyone else here for the meeting?19:00
fungisure19:00
ianwo/19:00
clarkb#startmeeting infra19:01
*** patchbot has left #openstack-meeting19:01
openstackMeeting started Tue Feb 12 19:01:13 2019 UTC and is due to finish in 60 minutes.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
clarkb#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting19:01
*** nguyenhai_ has joined #openstack-meeting19:01
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbI have no announcements19:01
clarkb#topic Actions from last meeting19:02
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:02
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-01-29-19.01.txt minutes from last meeting19:02
* diablo_rojo stands at the back of the room and makes a cup of tea19:02
clarkbcorvus: did update dns docs for us.19:02
clarkb#link https://review.openstack.org/#/c/633569/ Update DNS docs19:03
*** markvoelker has joined #openstack-meeting19:03
clarkbfungi: ^ that chagne in particualr was one you noticed we need. Should be a quick review if you have a moment19:03
*** vishalmanchanda_ has joined #openstack-meeting19:03
fungiawesome, thanks!19:03
clarkb#topic Specs approval19:04
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:04
clarkb#link https://review.openstack.org/#/c/587283/ LetsEncrypt Spec19:04
clarkbI'm not sure this spec is ready for approval. But wanted to have some time to talk about it so that we can get it there19:04
*** ociuhandu has quit IRC19:04
*** stephenfin has quit IRC19:04
*** vishalmanchanda has quit IRC19:04
*** jroll has quit IRC19:04
*** number80 has quit IRC19:04
*** geguileo has quit IRC19:04
*** bdperkin has quit IRC19:04
*** mugsie has quit IRC19:04
*** fdegir has quit IRC19:04
*** belmoreira has quit IRC19:04
*** yamahata__ has quit IRC19:04
*** tinwood has quit IRC19:04
*** nguyenhai has quit IRC19:04
*** vishalmanchanda_ is now known as vishalmanchanda19:04
ianwyeah, given the opendev developments, dns based approach might be better19:04
clarkbAs we do more opendevy things not needing to run out and pay $8.88USD for new certs for every service would be great19:04
*** tinwood has joined #openstack-meeting19:04
*** yamahata__ has joined #openstack-meeting19:05
*** mugsie has joined #openstack-meeting19:05
clarkbI also wanted to check in if our changes to DNS and config management have changed anyones thoughts on how we should approach this19:05
ianwsince we run our own for that19:05
clarkbianw, yup I noticed that if we wanted to use the same cert with .openstack.org altnames it is still a problem but we may be able to avoid that in most cases19:05
clarkbs/noticed/noted/19:05
*** fdegir has joined #openstack-meeting19:05
fungii'm unclear on how we would do that other than pushing new dns zone changes for review and hurriedly approving them19:05
clarkbin particualr we could maintain separate vhosts for openstack.org that redirect to opendev.org and continue to use the old school by hand management of those certs19:05
*** stephenfin has joined #openstack-meeting19:06
*** jroll has joined #openstack-meeting19:06
clarkbfungi: I think that is likely how it would work and if we have a renewal period with say 10 days of leeway we should be able to approve those quickly enough19:06
clarkbfungi: we could also potentially hvae it bypass review19:06
*** number80 has joined #openstack-meeting19:06
fungihow long is the challenge/response window for le acme servers, generally?19:06
*** ociuhandu has joined #openstack-meeting19:06
*** jamesmcarthur has joined #openstack-meeting19:07
ianwi've only ever used the tool with a live apache where it's seconds19:07
ianwbut surely there's enough time for dns updates built in19:08
*** bbowen has quit IRC19:08
ianwi will investigate how it can work with our new opendev setup and update the spec19:08
ianwmaybe it's worth a day or two's coding to do something hacky and bespoke to integrate with rackdns19:09
corvuswe're leaving rackdns19:09
ianwon the thought that it's "temporary" ... or at least won't be the primary dns option19:10
corvusthe only dns that matters in the future is opendev dns, which is managed in git19:10
corvus(i mean, we can manage it some other way if we need, it's managed by us.  but right now it's managed in git)19:10
clarkbcorvus: the one place it might matter is where we want to verify ownership of openstack.org domains for cert altnames19:10
ianwsure, maybe i weigh the status quo a bit more heavily than corvus, but definitely the spec wants updating now opendev is formalised19:11
clarkbbut as mentioend earlier we can probably avoid that and manage those certs in a more old school fashion then eventually stop doing openstack.org -> opendev.org redirects19:11
ianwso i'll do that19:11
fungiwell, for the redirect to work we'd still need the original in the san list19:11
corvusi grant there will be a transition period, but i feel fairly certain that things are moving quickly enough that investment in rackdns would be misplaced.19:11
clarkbianw: the other piece I'm trying to wrap my head around is whether or not the centralized config management push out of the cert data is still desireable with ansible/docker19:11
corvusi don't know that we should be thinking about openstack/opendev altnames19:12
fungihaving a redirect from https://etherpad.openstack.org/ to https://etherpad.opendev.org/ doesn't help if the certificate served by that server doesn't include etherpad.openstack.org as an altname19:12
clarkbfungi: other option is multiple vhosts with distinct certs19:12
corvusi think it may be much easier to put all of our redirects on a static server.19:13
fungiunless we maintain separate certs for those two i guess19:13
fungiyeah, putting the redirects somewhere other than the servers to which they redirect could be one way out19:13
corvusyeah, i'd much rather us throw a bunch of vhosts on files.o.o serving htaccess redirects so our new opendev servers don't have a bunch of complicated vhost baggage19:13
corvus(or a bunch of complicated cert baggage)19:13
clarkblong story short we should be able to make a dns story work now that we have better direct control of our dns19:14
clarkbso ++ to investigating that further and updating th spec19:14
ianwclarkb: to my mind, the certs are secrets and having it managed like all the other secrets is the easiest thing19:14
ianwbut, i'm sure opinions vary19:14
corvusi'd be happy to treat certs as being more ephemeral so that bringing up a new service could be completely automatic.19:15
clarkbthe main contraint we are trying to accomdoate for here is the first bring up of the webserver right? but if we switch to dns then maybe it could be entirely ephemeral without that constraint to accomodate?19:15
fungiif the certs weren't handled centrally, they could be treated as ephemeral along with their keys19:17
clarkbmaybe we can add an alternative to the spec that roughly sketches out what ^ looks like given the dns verification?19:17
fungihave each server create a key, a csr, and initiate dialogue via acme to fetch a cert, then serve that19:17
clarkbthen we'll be better able to evaluate the two major options?19:17
ianwi guess if the challenge response is already in dns, and the acme update happens before the webserver starts, it could work19:17
fungithat also has the benefit that the keys never leave the servers which use them, so less risk of compromise shipping them around unnecessarily19:17
clarkbianw: ya I'm thinking we may be able to sufficiently simply the config management side that its simpler overall to treat them as ephemeral19:18
clarkbs/simply/simplify/19:18
clarkbmy typing is particularly bad today19:18
fungian alternative to using dns there is to set the webserver up to use a self-signed cert and then have certbot or whatever replace that once the challenge/response is concluded19:18
ianwfungi: yes, i mean mostly the idea was to have to avoid re-writing as much legacy puppet as possible but still have things work19:19
fungithe same key could be reused for both the snakeoil and the csr, so you only need to generate one key19:19
*** wwriverrat has left #openstack-meeting19:19
fungiianw: i expect both those models could be used in parallel. the central broker as a stop-gap, with local per-server acme as the eventual goal to work toward?19:20
clarkband as we add services like gitea without that legacy we might be able to use the preferable setup whatever that may be19:21
fungithat way we still eventually get to stop tracking keys and certs in hiera19:21
clarkbthough I'm nto sure how that will tie into octavia19:21
clarkbcorvus: mordred ^ do you know what that looks like?19:21
fungidoes octavia need layer-7 visibility?19:21
clarkbfungi: no19:21
*** bdperkin has joined #openstack-meeting19:22
ianwfungi: true; the DNS approach is certainly simpler.  i know jhesketh's comments/preference was to just use that on rackdns too19:22
clarkbfungi: I'm not sure if our k8s setup does though19:22
fungiif it can work at layer-4 and just pass the sockets through, then not terminating https on the lb ought to be fine19:22
corvusyeah, we're doing l4 with octavia19:22
mordredclarkb: I do not know the answer to that question - but I think we're just l419:22
mordredcorvus beat me to it19:22
corvuswe will terminate ssl in k8s19:22
clarkbcool thansk for confirming19:23
corvuswe haven't done that yet19:23
corvusthanks for reminding me we still need to do that :)19:23
clarkbok it sounds like the definite next step is reevaluate dns as verification method. And then maybe given that new context we can reevaluate centralized control as the desired end goal? It may end up being a path to the end goal19:24
clarkbdid I capture the discussion well enough in ^19:24
ianwclarkb: ++ yes, i'll go back it with all this in mind now19:25
fungiseems sane19:25
clarkbgreat, thanks everyone.19:25
clarkb#topic Priority Efforts19:25
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:25
clarkb#storyboard19:25
clarkber19:25
clarkb#topic Storyboard19:25
*** openstack changes topic to "Storyboard (Meeting topic: infra)"19:25
clarkbfungi friday still looking like a good day for upgrading production storyboard?19:26
clarkband has the local db move aided with debuggability? I think we decided it didn't drastically change performance19:26
fungiyes, i need to send an announcement about brief 5-minute friday downtime19:27
fungimoving to a local db on storyboard-dev didn't change performance but did allow us to see that the db worker process spikes up to consume an entire cpu for 10 seconds or so whenever you try to load a tag-query-based board in your browser19:27
mordredoh good!19:28
clarkbfungi: ok so valuable after all19:28
fungiso suspicions around highly inefficient queries mostly confirmed there, and we at least have more options to debug deeper and profile things now, i guess19:28
clarkbgreat.19:29
fungiin other news, SotK has pushed up a bunch of changes to implement story attachments19:29
clarkbAre there any changes we need to get in place before we can do the production upgrade? or is mostly just a matter of doing it at this point19:29
clarkboh nice19:29
*** jamesmcarthur has quit IRC19:30
fungithe only blocker we found is already fixed now. un-capping sqlalchemy last november resulted in a much newer version installed on the new servers which broke adding worklists to boards because of the way inferred nulls were treated in insert queries19:30
clarkb#link https://review.openstack.org/#/q/topic:story-attachments19:30
funginon-backward-compatible change between sqlalchemy 0.9.10 and 1.0.019:31
fungithankfully SotK was able to track down the offending code and whip up a several-line hotfix there19:31
clarkband the fix was a roll forward fix right?19:31
fungicorrect19:31
clarkb(eg we didn't reinstall old sqlalchmeny)19:31
diablo_rojoCorrect19:31
clarkbSounds good. Any other storyboard topics?19:32
diablo_rojoI think fungi covered the big stuff19:32
fungioh, and SotK has a dockerfile he's using to so test deployments19:32
fungiit's in his github repo at the moment but he's going to push it up for review soon it sounds like19:33
clarkb++19:33
fungiso that might make for easier onboarding of new contributors too19:33
corvuswe're pretty good at testing dockerfile builds these days if you want to add a job to verify it works19:34
fungiand that's all the news i've got19:34
fungicorvus: yep, i suggested that as well19:34
clarkbthat all sounds excellent19:34
fungiwe could even start publishing images if we wanted19:34
*** artom has joined #openstack-meeting19:34
clarkbNot to jump in but we have a few more topics so lets keep moving19:34
clarkb#topic Update Config Management19:34
*** openstack changes topic to "Update Config Management (Meeting topic: infra)"19:34
corvusdiablo_rojo, SotK: ^ lemme know if you want help with that19:34
*** artom has quit IRC19:35
corvusclarkb: ++19:35
clarkbcmurphy and I got etherpad-dev01 running puppet4 at fosdem19:35
*** artom has joined #openstack-meeting19:35
clarkbthere was one minor error/warning in the logs that I got fixed yesterday19:35
cmurphyoh hi19:35
diablo_rojocorvus, that would be awesome19:35
clarkbI think the next steps there are to puppet futureparser the afs and kerberos servers, test puppet-4 on a centos machine, then we can puppet-4 all the things19:35
diablo_rojowhen SotK gets the patch up we can chat about that19:36
clarkbcorvus: mordred is there an especially good time to take the puppet futureparser plunge on the afs and kerberos machinery? if not I'll probably try to push that along tomorrow/thurdsay19:36
*** markvoelker has quit IRC19:36
clarkbFor the zuul as CD engine stuff https://review.openstack.org/#/c/604925/ was rebased to fix a merge conflict and updated to address a comment from pabelanger19:36
clarkbthat chagne adds a zuulcd user to bridge that zuul jobs can use to ssh in and run ansioble19:37
clarkbcorvus: mordred ^ I think that is potentially interesting with the gitea work19:37
clarkb(since the gitea work is so far mostly self contained)19:37
corvusclarkb: i can't think of a good time.  but mind quorums and it mostly should be fine.19:37
clarkbcorvus: ok19:37
corvusclarkb: yeah, i think we can move to zuulcd on that fairly quickly19:37
clarkbthat is what I had for config management updates19:38
clarkbcmurphy: anything else to call out re puppet-4?19:38
cmurphyi don't think so19:38
cmurphyit's all in topic:puppet-419:38
clarkbcool. Continuing to move on due to hour meeting and unexpectedly full agenda :)19:38
clarkb#topic OpenDev19:38
*** openstack changes topic to "OpenDev (Meeting topic: infra)"19:38
corvuswe're very close to having the opendev githea stuff running via ansible19:39
clarkbI left a -1 comment on the change that cleans some of that up. I think there was maybe a missing git add?19:39
clarkbmordred: ^ did you see that?19:39
corvusit would be great if folks could keep on top of the gerrit review topic19:39
clarkbwe try to run an ansible playbook that doesn't seem to exist19:39
corvusclarkb: he updated19:40
mordredclarkb: I just pushed an update a few minutes ago19:40
clarkbah cool I missed it with meeting prep19:40
corvusi believe i've mostly got the cgit redirects written as well19:40
clarkb#link https://review.openstack.org/#/q/topic:opendev-gerrit+status:open is the change listing for related changes19:40
mordredalso - I got a patch upstreamed into gitea that handles the cgit style line number lines19:40
corvusmordred: \o/19:41
mordredso next release we should be able to drop our local hack19:41
clarkbnice19:41
corvusso i think within a few days (realistically, next week due to absences this week), we're going to be in a good place to really start pushing forward on this19:41
mordred++19:41
corvusi think what i'd like to do now is break out a slightly more detailed task list than what's in the spec19:41
corvusand try to get people to put their names on things19:41
corvusdoes that sound like something we should do next week?19:41
clarkbcorvus: that sounds great to me. I think it will help find places for people to slot in (also encourage interaction with the new system(s))19:42
corvusthe other thing i think maybe it's time to think about is whether we should start sending emails about the move19:42
ianw++ as someone watching, some chunks that can happen more standalone would help to contribute19:42
*** sdake has quit IRC19:42
clarkbcorvus: it would probably be good to have a permanentish home we can point people too. So they can interact with it?19:43
clarkbI'm not sure if we feel we are there yet (https maybe? I guess not strictly required)19:43
clarkbbut ya we should communicate it as soon as we are happy to have people look at it19:43
corvusspecifically -- is it time to send a heads up to the top level projects saying we don't have a date for the move yet, but we will soon.  in the meantime, please start thinking about what project renames you would like to do as part of the move.19:43
corvusclarkb: yeah, i think maybe we should not communicate before gitea is served from opendev.org, that way there will be a nice thing for people to look at and hopefully be happier.  :)19:44
clarkb++ once that is in place I think we should communicate that this is the tool we're moving towards and have projects communicate any other input like the renaming stuff19:45
corvusokay.  i'll put that on the task list too.  :)19:46
corvusi think that's it for opendev-gerrit19:46
*** tobiash has joined #openstack-meeting19:47
clarkbok we've got ~13 minutes and two more topics so lets keep moving19:47
clarkb#topic General Topics19:47
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:47
fungii wonder whether we shouldn't rename something first to have a slightly more concrete example to point at19:47
fungibut we can discuss later19:47
corvusfungi: rename what?19:47
clarkbcorvus: openstack-infra/zuul -> zuul-ci/zuul (or zuul/zuul) maybe?19:48
*** eharney has joined #openstack-meeting19:48
clarkbcorvus: I think a project being hosted19:48
corvuswe can't rename it before we switch the hostname19:48
clarkbcould be confusing to do so before19:49
clarkbbut we can followup on that. Lets go to next topics before we run out of time19:49
fungiright, i guess it's a question of do we want to start talking about renames before we've already renamed something? but i guess communicating early and then having to alter plans later when we discover we didn't take something into account is fine too19:49
corvusfor example, git.openstack.org/openstack-infra/zuul -> opendev.org/zuul/zuul  will happen at the same time.19:49
corvusthis is important19:49
corvusi don't think we're talking about the same thing19:49
*** vishakha has quit IRC19:50
fungii'll have to reread. thought we were talking about repo/namespace renames19:50
corvuswhen we switch domain names, we will be renaming all of the repositories because we will change their hostnames19:50
corvusgrr19:51
corvuswe need better words to talk about this19:51
corvuswe will also be renaming some git repos as well19:51
fungii see. we have to perform the server dns name changes at the same time as the repository namespace changes19:51
fungiso we need people to tell us what namespaces they plan to use in advance, before we try to do that19:52
corvusi think maybe we should give projects as much time as possible to decide to opt in to a namespace change along with the hostname change19:52
clarkbya that will reduce renaming pain19:52
corvusbecause it's a very high cost to a project to rename a repo, and a low cost for us to do so at that time19:52
clarkbonce transition instead of two19:52
corvusclarkb: exactly19:52
clarkb#link https://etherpad.openstack.org/2019-denver-ptg-infra-planning 2019 Denver PTG Planning19:52
corvusand every project is going to incur some amount of cost with the hostname rename, so we may as well solicit ways to minimize additional cost.19:53
clarkbThis is mostly a heads up that ^this etherpad exists and I plan to start filling in ideas this afternoon19:53
clarkbcorvus: ++19:53
corvusokay, i gather we're all on the same page now :)19:53
corvus*and* we have better words19:53
fungii'm pretty sure for a lot of projects, they won't notice they can have new namespaces until after we perform the dns change and some namespace changes along with that, and then they'll all start queuing up with new namespace requests. but i'm not really sure how to solve that bit of human nature and resistance to paying attention to announcements19:53
clarkbif you have PTG ideas please add them to the etherpad too19:53
clarkbfungi: we might directly reach out to individuals we expect to be interested19:54
clarkbildikov and hogepodge and corvus for that set of foundation level project for example19:54
corvuswe might suggest to the tc if they want to evict non-official projects, this could be an appropriate time.19:54
clarkbcorvus: all yours to talk about zuul-preview when ready19:54
clarkbcorvus: ++19:54
corvusand yeah, we might make sure that starlingx knows19:54
ildikovo/19:55
corvusin pitching in on the netlify work, we realized that a lot of apps out there expect to be hosted at the root of a domain19:56
corvusso we wrote a thing called zuul-preview which is basically a very simple http proxy for our log servers19:56
corvusit will work with both the current static and future swift log servers with no changes19:56
corvusand it runs as a small docker container19:56
clarkbcorvus: I assume the deployment method in mind is to build the software in a container and deploy it that way?19:57
clarkb(so we don't have to worry about packaging or build toolchain in config management)19:57
corvusyeah, in almost exactly the same way that we now have the docker registry deployed19:57
corvus(btw, we're running a docker registry -- it's our first production docker service)19:57
corvusso as soon as the zuul-preview source repo lands, i'd like to deploy that in opendev19:57
clarkbmy only other thought is that small stateless services like this would be perfect for a multi function k8s19:57
clarkbthat way we don't have to run dedicated "hardware" for each service, get some redundancy and packing efficiency19:58
fungiwhen you say "will work with [...] future swift log servers" you presumably mean by running zuul-preview on a separate dedicated server/container and having it fetch/serve the data zuul archives to swift19:58
clarkbbut probably too much of a requirement to couple new k8s cluster with that19:58
corvusbut it's a new service, and it's a slight deviation from my "lets stop running proxies" mantra (which is now "lets stop running complicated proxies"), so i thought it worth some discussion.  :)19:58
clarkbbut we do have a number of other almost stateless small services we could collocate like that maybe19:58
corvusfungi: it proxies to any hosting url, it doesn't care what backs it.19:58
clarkb(somethign to keep in mind I guess)19:59
fungicorvus: right, but point being it won't somehow get served by swift, it'll be running somewhere else19:59
*** jamesmcarthur has joined #openstack-meeting19:59
corvusclarkb: yeah, i agree, though i think that's a better future thing after we k8s better19:59
clarkbfungi: the swift there is location of the logs not the service19:59
clarkbfungi: since we are trying to eventually put the logs in swift too19:59
corvusfungi: the thing i mean to say here is that the docker container we'd be running for this won't have to change when we change our log storage.  because it neither knows or cares.20:00
fungias i understand it the site preview builds would get archived to swift just like job logs or similar artifacts20:00
corvusfungi: correct20:00
clarkbcorvus: no real objectiosn from me. We may want to write down our thoughts on proxies though (since some observers may be unhappy about the loganalyze changes? maybe? I dunno)20:00
fungibut zuul-preview will be a webserver we run somewhere20:00
clarkbfungi: yup it will have to run on a "server"20:01
corvusclarkb: well, i'm still hoping we managed to land some mitigating patches in zuul before we drop osla20:01
clarkbcorvus: cool20:01
fungiso at least in this case still somewhat like how osloganalyze works on the existing logs.o.o if it were backed with data from somewhere else not local20:01
clarkbwe are time. I'll let current discussion finish before ending the meeting. Thank you everyone20:01
corvusyes, and were one line of apache config instead of a mod_wsgi script :)20:02
fungithanks clarkb!20:02
mordredyeah. I think writing down proxy thoughts is likely a good idea ... one of the differences I see here is that zuul-preview is project/content agnostic, whereas osla is a specific proxy filter that applies to some of the content produced by some of the projects hosted20:02
clarkbcorvus: well with a bunch of code running behind apache still20:02
clarkb(still far less than osla)20:02
corvusclarkb: none of the code is involved in processing or serving the data20:02
clarkbya20:02
fungione line of apache config and a (c++/rust/python) cli vs a few lines of apache config and a wsgi script, but sure20:02
corvusi see you disbelieve me, but i think i'm trying to make a valid point20:03
mordredcorvus: ++ control-plane custom code vs. data-plane custom code20:03
clarkbworth calling the lack of processing data out though as that semes to be the distinction we are making with the proxies we'd want to run20:03
corvusthere was a patch several years ago to add swift backend support to osla20:03
clarkbya it does greatly simplify the serving of the data20:03
corvusit never landed because it exploded the complexity of the program20:03
clarkbcorvus: we actually did land it20:04
corvus*that* is the distinction i'm trying to make here20:04
corvusand reverted it?20:04
fungii don't disbelieve, just trying to relate the level of server maintenance to something we currently have, for context20:04
clarkbthen sdague made us revert it because it broke some user functionality he wanted20:04
clarkbcorvus: ya the big thing for sdague was sorting of periodic jobs, swift doesn't do file mod times like posix fs. We now get that functionality out of the zuul builds listings20:04
corvusso anyway, that event directly related to this20:05
clarkbbut at the time there wasn't a good way to look at today/yseterday's periodic job20:05
corvusi don't want to manage a giant proxy that does all things for everyone20:05
corvusand, i don't think anyone else here does either :)20:05
mordred++20:05
corvusi don't even think sdague did when he was around :)20:05
*** mriedem_afk is now known as mriedem20:05
clarkbyup, the constrained scope of the proxy being basically a redirect lookup is far easier to manage20:05
corvusya, that's what i'm trying to say :)20:05
fungii do agree lots of little proxies with their own simple tasks are easier to reason about than one big proxy doing everything20:06
corvusi hope we don't grow a lot of little ones either, but i admit it's a possibility20:06
corvusi think most of what we get from osla can actually move into zuul javascript.  i think that's still the plan, and we're making small steps toward that.20:06
fungiand the close relationship of this to a particular use case for a general class of zuul jobs helps too20:07
fungisince it's less likely to be another one-off codebase we're maintaining just for our own deployment20:07
mordredyeah. I think that's a real key here - it's a general purpose thing that is applicable to a class of zuul jobs - and is applicable to non-openstack deployments too20:07
fungizuul-preview seems far more reusable by others outside the context of our particular ci deployment than oslogalanyze is (or likely could ever be)20:08
clarkbalright I'll end the meeting now. Find us in #openstack-infra of openstack-infra@lists.openstack.org if you need to get in touch before next week's meeting20:09
clarkb#endmeeting20:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:09
clarkbthanks again!20:09
openstackMeeting ended Tue Feb 12 20:09:31 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-02-12-19.01.html20:09
corvusclarkb: thanks!20:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-02-12-19.01.txt20:09
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2019/infra.2019-02-12-19.01.log.html20:09
*** bbowen has joined #openstack-meeting20:18
*** slaweq has joined #openstack-meeting20:19
*** e0ne has quit IRC20:25
*** jamesmcarthur has quit IRC20:31
*** awaugama_ has joined #openstack-meeting20:33
*** markvoelker has joined #openstack-meeting20:33
*** awaugama has quit IRC20:34
*** mjturek has quit IRC20:47
*** awaugama_ has quit IRC20:47
*** e0ne has joined #openstack-meeting20:48
*** jamesmcarthur has joined #openstack-meeting20:52
*** jamesmcarthur has quit IRC20:54
*** bbowen_ has joined #openstack-meeting21:03
*** slaweq_ has joined #openstack-meeting21:03
*** slaweq has quit IRC21:06
*** bdperkin has quit IRC21:06
*** fdegir has quit IRC21:06
*** tinwood has quit IRC21:06
*** bbowen has quit IRC21:06
*** mugsie has quit IRC21:06
*** markvoelker has quit IRC21:06
*** mugsie has joined #openstack-meeting21:06
*** tinwood has joined #openstack-meeting21:06
*** mjturek has joined #openstack-meeting21:08
*** raildo has quit IRC21:18
*** tobiash has left #openstack-meeting21:20
*** bdperkin has joined #openstack-meeting21:23
*** sdake has joined #openstack-meeting21:27
*** e0ne has quit IRC21:28
*** slaweq_ is now known as slaweq21:32
*** _alastor_ has quit IRC21:41
*** artom has quit IRC21:42
*** mjturek has quit IRC21:48
*** sdake has quit IRC21:50
*** zaneb has joined #openstack-meeting21:58
*** _alastor_ has joined #openstack-meeting21:59
*** markvoelker has joined #openstack-meeting22:03
*** jamesmcarthur has joined #openstack-meeting22:27
*** slaweq has quit IRC22:34
*** markvoelker has quit IRC22:36
*** JangwonLee_ has quit IRC22:45
*** slaweq has joined #openstack-meeting22:50
*** armax has quit IRC22:53
*** armax has joined #openstack-meeting22:54
*** armax has quit IRC22:54
*** slaweq has quit IRC22:54
*** enriquetaso has quit IRC22:58
*** enriquetaso has joined #openstack-meeting22:58
*** cloudrancher has joined #openstack-meeting22:59
*** jamesmcarthur has quit IRC23:11
*** whoami-rajat has joined #openstack-meeting23:12
*** artom has joined #openstack-meeting23:18
*** ociuhandu has quit IRC23:30
*** ociuhandu has joined #openstack-meeting23:30
*** jamesmcarthur has joined #openstack-meeting23:32
*** jamesmcarthur has quit IRC23:32
*** jamesmcarthur has joined #openstack-meeting23:33
*** markvoelker has joined #openstack-meeting23:33
*** macza has quit IRC23:42
*** macza has joined #openstack-meeting23:42
*** sdake has joined #openstack-meeting23:44
*** cloudrancher has quit IRC23:44
*** cloudrancher has joined #openstack-meeting23:45
*** cloudrancher has quit IRC23:49
*** jamesmcarthur has quit IRC23:56

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