Tuesday, 2017-12-19

*** chyka has quit IRC00:00
*** fnaval has quit IRC00:03
*** d0ugal has joined #openstack-meeting00:04
*** fnaval has joined #openstack-meeting00:05
*** fnaval has quit IRC00:08
*** rcernin has quit IRC00:09
*** rcernin_ has joined #openstack-meeting00:09
*** ijw has joined #openstack-meeting00:13
*** VW_ has joined #openstack-meeting00:15
*** VW has quit IRC00:18
*** ijw has quit IRC00:18
*** VW_ has quit IRC00:19
*** fnaval has joined #openstack-meeting00:24
*** ijw has joined #openstack-meeting00:26
*** yangyapeng has joined #openstack-meeting00:27
*** fnaval has quit IRC00:28
*** ijw has quit IRC00:30
*** yangyapeng has quit IRC00:31
*** marst has quit IRC00:35
*** bobh has joined #openstack-meeting00:39
*** d0ugal has quit IRC00:40
*** wanghao has joined #openstack-meeting00:41
*** diablo_rojo_ has joined #openstack-meeting00:47
*** diablo_rojo has quit IRC00:47
*** tovin07_ has joined #openstack-meeting00:48
*** pvaneck has quit IRC00:50
*** rcernin_ has quit IRC00:50
*** d0ugal has joined #openstack-meeting00:51
*** jamesmcarthur has joined #openstack-meeting00:52
*** psachin has joined #openstack-meeting00:52
*** jamesmcarthur has quit IRC00:56
*** edmondsw has joined #openstack-meeting00:58
*** chyka has joined #openstack-meeting01:01
*** gyee has quit IRC01:01
*** kiennt26 has joined #openstack-meeting01:03
*** chyka has quit IRC01:06
*** fnaval has joined #openstack-meeting01:09
*** salv-orlando has quit IRC01:13
*** yuanying has quit IRC01:14
*** salv-orlando has joined #openstack-meeting01:14
*** bobh has quit IRC01:14
*** fnaval has quit IRC01:14
*** bobh has joined #openstack-meeting01:14
*** yangyapeng has joined #openstack-meeting01:16
*** dmacpher has quit IRC01:16
*** yangyapeng has quit IRC01:17
*** yangyapeng has joined #openstack-meeting01:17
*** iyamahat has joined #openstack-meeting01:17
*** salv-orlando has quit IRC01:18
*** ijw has joined #openstack-meeting01:26
*** zaneb has quit IRC01:27
*** vishwanathj has joined #openstack-meeting01:30
*** epico has joined #openstack-meeting01:31
*** ijw has quit IRC01:32
*** Apoorva_ has joined #openstack-meeting01:32
*** fnaval has joined #openstack-meeting01:33
*** kiennt26 has left #openstack-meeting01:33
*** Apoorva has quit IRC01:36
*** fnaval has quit IRC01:36
*** Apoorva_ has quit IRC01:37
*** fnaval has joined #openstack-meeting01:45
*** Dinesh_Bhor has joined #openstack-meeting01:46
*** edmondsw has quit IRC01:53
*** ijw has joined #openstack-meeting01:54
*** andreas_s has joined #openstack-meeting01:55
*** jamesmcarthur has joined #openstack-meeting01:56
*** andreas_s has quit IRC01:59
*** jamesmcarthur has quit IRC02:01
*** geguileo has quit IRC02:01
*** ijw has quit IRC02:01
*** aselius has quit IRC02:05
*** ijw has joined #openstack-meeting02:06
*** rcernin has joined #openstack-meeting02:11
*** geguileo has joined #openstack-meeting02:12
*** geguileo is now known as Guest3717802:13
*** ekcs has quit IRC02:14
*** salv-orlando has joined #openstack-meeting02:14
*** ijw has quit IRC02:15
*** caowei has joined #openstack-meeting02:16
*** psachin has quit IRC02:18
*** salv-orlando has quit IRC02:20
*** bobh has quit IRC02:20
*** tovin07_ has quit IRC02:20
*** bobh has joined #openstack-meeting02:21
*** tovin07_ has joined #openstack-meeting02:21
*** bobh has quit IRC02:24
*** bobh has joined #openstack-meeting02:24
*** gcb has joined #openstack-meeting02:27
*** markstur has quit IRC02:28
*** Apoorva has joined #openstack-meeting02:29
*** psachin has joined #openstack-meeting02:36
*** Tom-Tom has joined #openstack-meeting02:45
*** bobh has quit IRC02:52
*** bobh has joined #openstack-meeting02:53
*** fnaval has quit IRC02:53
*** ijw has joined #openstack-meeting02:54
*** vishwanathj_ has quit IRC02:56
*** mriedem has quit IRC02:56
*** ijw has quit IRC02:59
mkrai#startmeeting zun03:00
openstackMeeting started Tue Dec 19 03:00:06 2017 UTC and is due to finish in 60 minutes.  The chair is mkrai. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
mkrai#link https://wiki.openstack.org/wiki/Zun#Agenda_for_2017-12-19_0300_UTC Today's agenda03:00
mkrai#topic Roll Call03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: zun)"03:00
openstackThe meeting name has been set to 'zun'03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
mkrai#topic Roll Call03:00
*** openstack changes topic to "Roll Call (Meeting topic: zun)"03:00
*** Dinesh_Bhor has quit IRC03:01
*** kiennt26 has joined #openstack-meeting03:02
mkraiHi kiennt2603:03
mkraiThank you for joining the meeting03:03
mkraiIt seems we are only two in the meeting03:03
mkraiLet's have a short update from both of us03:03
mkraikiennt26: Would you like to go first?03:03
kiennt26mkrai: yeah, ok.03:04
mkraiThank you03:04
*** kevzha01 has joined #openstack-meeting03:04
*** kevzha01 is now known as kevinz03:04
kiennt26last week, i have worked on blueprint Use privsep03:04
kiennt26hi kevinz03:04
mkraiHi kevinz03:04
kevinzsorry I'm late03:04
mkraiI am glad you're here today03:04
kevinzHi kiennt26 mkrai03:04
kiennt26#link https://review.openstack.org/#/c/511430/03:04
mkraikiennt26: is giving an update now03:04
*** ZacharyMa has joined #openstack-meeting03:04
kiennt26mkrai, kevinz: I have proposed a patch to implement blueprint use-privsep03:05
kiennt26the above link, could you test and review it? :)03:05
mkraikiennt26: Thank you for it03:05
mkraiYes sure I will review it03:06
kevinzkiennt26: I will review too:-)03:06
mkraikiennt26: Anything else from your side?03:06
kiennt26My 2nd work is publishing Zun-tempest-plugin's documentation. The patch was landed.03:06
kiennt26#link https://review.openstack.org/#/c/527886/03:06
mkraiGreat. With that the migration is completed I assume?03:07
kiennt26mkrai: yeah, i think :)03:07
kiennt26That's all from me last weak.03:07
mkraikiennt26: Thank you03:08
mkraikevinz: Would you like to provide an update?03:08
kevinzyeah sure03:08
kevinzI'm working on volume attach for capsule. Now the function is finished. I will submit a patch after fix some UT error03:09
mkraikevinz: I saw that the multi-attach support is merged in Nova now03:09
mkrai#link http://lists.openstack.org/pipermail/openstack-dev/2017-December/125356.html03:09
mkraiThat might help you03:10
kevinzmkrai: Good news. I will follow this03:10
kevinzmkrai: Now only support one attach03:10
kevinzin zun03:10
mkraikevinz: Great03:10
kevinzalso I'm looking at virtual-kubelet03:11
kevinzwhich we can use with kubernetes-connector03:11
mkrai#link https://github.com/virtual-kubelet/virtual-kubelet03:11
mkraiI don't know much about it03:12
mkraiHow is it used with k8s-connector?03:12
mkraiAnd then zun?03:12
*** yamahata has quit IRC03:12
kevinzThis project will make ACI or AWS as the kubernetes backend03:13
kevinzSo the same with Zun. We can use this project to register a node in Kubernetes.03:13
mkraiThat node is an Openstack node?03:13
kevinzin general, make zun cluster as a single node in Kubernetes03:14
mkraiOk got it03:14
kevinzThe node is K8s node.03:14
mkraikevinz: If possible, I would like to have a diagram for this support03:14
mkraiThat will make things easier to understand03:14
mkraiHow k8s, zun, k8s-connector all are connected sort of diagram03:15
*** edmondsw has joined #openstack-meeting03:15
kevinzOK, I will compile one after meeting :-)03:15
kiennt26mkrai: +103:15
mkraiGreat. Thank you for this kevinz :)03:15
*** salv-orlando has joined #openstack-meeting03:15
mkraiI will mark an action for it03:16
kiennt26kevinz: looking for it, thank you!03:16
mkraikevinz: Is it ok?03:16
kevinzmkrai: kiennt26: my pleasure03:16
kevinzThat's all from my side03:16
*** fnaval has joined #openstack-meeting03:16
mkrai#action kevinz to create a diagram explaining the k8s-connector feature03:16
mkraikevinz: Thank you for all your hard work :)03:16
mkraiOk so my turn now!03:16
kevinzmkrai: yw03:16
*** bobh has quit IRC03:17
mkraiSo I have been working on the clear container support in ZUn03:17
mkrai#link https://review.openstack.org/#/c/499534/03:17
*** yamahata has joined #openstack-meeting03:17
mkraiNow that there is new Kata containers, the patch is in question03:18
mkraiI posted a comment saying that this can be merged for now and later replace with kata containers03:18
*** fnaval has quit IRC03:18
mkraiKata containers will take time to be ready03:18
mkraiI also posted a patch to add a document on how to use CC with Zun03:18
mkrai#link https://review.openstack.org/#/c/527611/03:19
mkraiI will update this patch today03:19
mkraiSo that's all I did last week03:19
mkraiAny questions on the same?03:19
*** edmondsw has quit IRC03:19
*** salv-orlando has quit IRC03:20
kiennt26mkrai, kevinz : Zun-tempest-plugin still 404.03:20
kiennt26I have pushed a patch to fix it03:20
kiennt26#link https://review.openstack.org/#/c/527851/03:20
kevinzmkrai: Not yet. Maybe come up with some questions after review the patch03:20
mkraikiennt26: Ok I will review it03:20
mkraiI guess this is critical patch03:21
mkraikevinz: Thank you!03:21
kevinzkiennt26: me too03:21
kiennt26mkrai, kevinz : thank you :) Hope this patch will fix our problem.03:21
kevinzmkrai: yw03:21
mkraikiennt26: sure, Thank you!03:22
mkrai Anything else to discuss?03:22
*** armax has quit IRC03:22
kiennt26Nothing from me.03:22
kevinzThat's all from my side03:22
mkraiOk thank you all for joining the meeting :)03:22
mkraiSee you next week!03:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"03:23
openstackMeeting ended Tue Dec 19 03:23:06 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:23
openstackMinutes:        http://eavesdrop01.openstack.org/meetings/zun/2017/zun.2017-12-19-03.00.html03:23
openstackMinutes (text): http://eavesdrop01.openstack.org/meetings/zun/2017/zun.2017-12-19-03.00.txt03:23
openstackLog:            http://eavesdrop01.openstack.org/meetings/zun/2017/zun.2017-12-19-03.00.log.html03:23
*** markvoelker has joined #openstack-meeting03:24
*** yamahata has quit IRC03:27
*** iyamahat has quit IRC03:27
*** iyamahat has joined #openstack-meeting03:27
*** VW has joined #openstack-meeting03:29
*** iyamahat has quit IRC03:35
*** fnaval has joined #openstack-meeting03:36
*** fengshengqin has joined #openstack-meeting03:39
*** fengshengqin has quit IRC03:39
*** e0ne has joined #openstack-meeting03:42
*** e0ne has quit IRC03:47
*** VW has quit IRC03:48
*** tpatil has joined #openstack-meeting03:51
*** VW has joined #openstack-meeting03:52
*** Dinesh_Bhor has joined #openstack-meeting03:52
*** ijw has joined #openstack-meeting03:55
*** sridharg has joined #openstack-meeting03:55
*** dmacpher has joined #openstack-meeting03:56
*** markvoelker has quit IRC03:58
*** ijw has quit IRC03:59
*** rkmrHonjo has joined #openstack-meeting04:00
*** bobh has joined #openstack-meeting04:00
*** samP has joined #openstack-meeting04:01
tpatilsamP: Ping?04:01
*** e0ne has joined #openstack-meeting04:01
tpatilrkmrHonjo : Hi04:01
*** armax has joined #openstack-meeting04:01
rkmrHonjotpatil: hi04:01
tpatilsamP: Hi04:01
samPcould you please start the meeting04:01
tpatilsamP: Ok04:02
tpatil#startmeeting Masakari04:02
openstackMeeting started Tue Dec 19 04:02:13 2017 UTC and is due to finish in 60 minutes.  The chair is tpatil. Information about MeetBot at http://wiki.debian.org/MeetBot.04:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:02
*** openstack changes topic to " (Meeting topic: Masakari)"04:02
openstackThe meeting name has been set to 'masakari'04:02
Dinesh_BhorHi all04:02
rkmrHonjoHi. sorry, I left this meeting at 13:45.04:02
tpatilDinesh_Bhor: Hi04:02
samPHi all,04:02
tpatil#topic High priority items04:02
*** openstack changes topic to "High priority items (Meeting topic: Masakari)"04:02
samP sorry for long absent04:02
tpatilsamP: How was your vacation?04:03
samPtpatil: It was good, but too busy04:03
samPwith family04:03
*** bobh has quit IRC04:04
*** Apoorva has quit IRC04:04
tpatilsamP: That must be fun04:04
tpatilNo high priority item for discussion04:05
samPyeh..kind of04:05
tpatilmoving ahead04:05
tpatil#topic Bugs (stuck/critical)04:05
*** openstack changes topic to "Bugs (stuck/critical) (Meeting topic: Masakari)"04:05
tpatilNo new bugs reported in LP04:05
tpatil#topic Discussion points04:07
*** openstack changes topic to "Discussion points (Meeting topic: Masakari)"04:07
tpatilHorizon Plugin04:07
*** VW has quit IRC04:07
tpatilNiraj has proposed initial cookie cutter patch04:07
tpatil#link https://review.openstack.org/#/c/528647/04:07
tpatilZulu jobs Is failing, he will fix this problem04:08
*** reedip has joined #openstack-meeting04:08
samPtpatil: thanks04:08
tpatilInstall guide document (in progress)04:08
tpatilAll patches were merged, I will delete this topic from agenda in the next meeting04:09
samPexcept masakari-monitors04:09
samPI will review that soon04:09
rkmrHonjosamP: thanks.04:09
samP#link https://review.openstack.org/#/q/topic:operators_guide04:09
tpatilsorry, I will mention this point in the agenda then04:09
*** abhishekk has joined #openstack-meeting04:10
samPAre those docs are hosted in public?04:10
tpatilRecovery method customization04:10
*** fnaval has quit IRC04:11
tpatilsmaP: you mean, similar to this one https://docs.openstack.org/releasenotes/nova/unreleased.html04:11
samPtpatil: yes.04:12
*** fnaval has joined #openstack-meeting04:12
samPis that automated or do we have to do something?04:12
samPtpatil: sorry, I mean here vv04:13
samP#link https://docs.openstack.org/queens/04:13
*** e0ne has quit IRC04:13
tpatilsamP: Not sure, maybe it requires some additional changes04:14
*** niraj_singh has joined #openstack-meeting04:14
tpatilas I don't see Masakari project is listed here https://docs.openstack.org/queens/admin/04:14
*** rbudden has quit IRC04:15
samPtpatil: true. let's check what else we have to do to host them on docs.openstack.org04:16
*** e0ne has joined #openstack-meeting04:16
*** fnaval has quit IRC04:16
tpatilAnyone interested to find out this info?04:16
*** salv-orlando has joined #openstack-meeting04:16
samP#link https://docs.openstack.org/doc-contrib-guide/release.html04:17
samPI guess me or someone in release team have to do it.04:18
*** gouthamr has quit IRC04:18
samPFor now I will take this task..04:18
tpatilsamP: thank you04:18
rkmrHonjosamP: thanks.04:18
tpatil#action : samP will submit a patch to publish masakari documentation release04:19
tpatilRecovery method customization04:19
tpatil#link https://review.openstack.org/#/c/458023/04:19
tpatilPlease review the specs04:20
samPtpatil: sure I will04:20
tpatilQueens Work Items04:20
tpatilI don't see there are any changes in the work items04:21
*** salv-orlando has quit IRC04:21
*** e0ne has quit IRC04:21
tpatilAnsible support for Masakari04:21
tpatilDinesh_Bhor will work on this item. No progress yet04:22
Dinesh_BhorI am working on this. Soon I will let you know my findings.04:22
samPReally sorry that I was not able to publish sample masakari playbooks before I go to vacation.04:23
tpatilDinesh_Bhor: Thank you04:23
samPDinesh_Bhor: tpatil: I will do it soon04:23
Dinesh_BhorsamP: No problem, Thank you04:23
tpatilCall Force down API when host-failure will be notified04:23
tpatil#link https://review.openstack.org/#/c/526598/04:24
rkmrHonjotpatil: thank you for reviewing. But, I have question. I'll write it on gerrit after that.(Sorry, I don't finished to confirm nova codes yet.)04:25
tpatilrkmrHonjo: OK04:25
rkmrHonjotpatil: thanks.04:26
tpatilsamP: Do you want to discuss about BM HA (ironic + nova)?04:26
*** e0ne has joined #openstack-meeting04:26
samPtpatil: No progress. sorry04:27
tpatil#topic AOB04:27
*** openstack changes topic to "AOB (Meeting topic: Masakari)"04:27
tpatilMigrate from launchpad to Storyboard04:27
tpatilNo progress yet04:28
samPtpatil: For my best understanding, no community wide movement for this item04:28
tpatilAnyone has anything else for discussion?04:28
tpatilsamP: Ok04:28
samPtpatil: yep, about PTG04:29
samPI am not sure whether I can attend to this PTG04:30
*** psachin has quit IRC04:30
samPHow many of you going there? and I think session dead line is closed or very near now04:31
*** ricolin has joined #openstack-meeting04:31
*** e0ne has quit IRC04:31
samPI will check for session and room availability at PTG04:32
tpatilDinesh and I will attend PTG04:32
samPtpatil: OK04:32
*** jamesmcarthur has joined #openstack-meeting04:32
*** coolsvap has joined #openstack-meeting04:32
samPor we could have a virtual mid-cycle meetup04:32
samPLet's discuss this on ML04:33
tpatilsamP: Sure04:33
*** rajulk has quit IRC04:34
*** psachin has joined #openstack-meeting04:35
tpatilIf there is no topics left for discussion, let's end this meeting04:35
samPnothing from my side04:36
rkmrHonjome too.04:36
tpatilThank you, All04:36
samPtpatil: thank you for handling the meeting04:36
Dinesh_BhorThank you all04:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:36
openstackMeeting ended Tue Dec 19 04:36:23 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:36
openstackMinutes:        http://eavesdrop01.openstack.org/meetings/masakari/2017/masakari.2017-12-19-04.02.html04:36
openstackMinutes (text): http://eavesdrop01.openstack.org/meetings/masakari/2017/masakari.2017-12-19-04.02.txt04:36
openstackLog:            http://eavesdrop01.openstack.org/meetings/masakari/2017/masakari.2017-12-19-04.02.log.html04:36
*** samP has left #openstack-meeting04:36
*** rkmrHonjo has quit IRC04:36
tpatilsamP: No problem04:36
*** jamesmcarthur has quit IRC04:36
*** cdub has quit IRC04:39
*** andreas_s has joined #openstack-meeting04:40
*** Tom-Tom has quit IRC04:41
*** e0ne has joined #openstack-meeting04:41
*** tpatil has quit IRC04:41
*** iyamahat has joined #openstack-meeting04:42
*** janki has joined #openstack-meeting04:43
*** andreas_s has quit IRC04:45
*** tovin07_ has quit IRC04:46
*** e0ne has quit IRC04:46
*** abhishekk has left #openstack-meeting04:51
*** armax has quit IRC04:53
*** kiennt26 has quit IRC04:54
*** kiennt26 has joined #openstack-meeting04:55
*** markvoelker has joined #openstack-meeting04:55
*** e0ne has joined #openstack-meeting04:56
*** gcb has quit IRC04:56
*** yamamoto has joined #openstack-meeting04:57
*** gcb has joined #openstack-meeting04:58
*** e0ne has quit IRC05:01
*** e0ne_ has joined #openstack-meeting05:01
*** e0ne_ has quit IRC05:07
*** yamamoto has quit IRC05:07
*** psachin has quit IRC05:07
*** ekcs has joined #openstack-meeting05:08
*** yamamoto has joined #openstack-meeting05:08
*** janki has quit IRC05:09
*** e0ne has joined #openstack-meeting05:10
*** janki has joined #openstack-meeting05:10
*** Tom-Tom has joined #openstack-meeting05:11
*** e0ne has quit IRC05:15
*** psachin has joined #openstack-meeting05:16
*** salv-orlando has joined #openstack-meeting05:17
*** salv-orlando has quit IRC05:22
*** armax has joined #openstack-meeting05:22
*** e0ne has joined #openstack-meeting05:23
*** yamamoto has quit IRC05:26
*** e0ne has quit IRC05:28
*** markvoelker has quit IRC05:28
*** armax has quit IRC05:28
*** yamamoto has joined #openstack-meeting05:30
*** e0ne has joined #openstack-meeting05:32
*** Dinesh_Bhor has quit IRC05:34
*** ZacharyMa has quit IRC05:34
*** Dinesh_Bhor has joined #openstack-meeting05:34
*** ZacharyMa has joined #openstack-meeting05:35
*** yamamoto has quit IRC05:36
*** e0ne has quit IRC05:37
*** Dinesh_Bhor has quit IRC05:38
*** Dinesh_Bhor has joined #openstack-meeting05:39
*** caowei has quit IRC05:40
*** Dinesh_Bhor has quit IRC05:42
*** Dinesh_Bhor has joined #openstack-meeting05:43
*** e0ne has joined #openstack-meeting05:44
*** caowei has joined #openstack-meeting05:45
*** links has joined #openstack-meeting05:47
*** e0ne has quit IRC05:49
*** chyka has joined #openstack-meeting05:50
*** ekcs has quit IRC05:51
*** chyka has quit IRC05:51
*** iyamahat_ has joined #openstack-meeting05:53
*** iyamahat has quit IRC05:53
*** e0ne has joined #openstack-meeting05:54
*** wanghao_ has joined #openstack-meeting05:58
*** e0ne has quit IRC05:59
*** e0ne has joined #openstack-meeting06:01
*** wanghao has quit IRC06:02
*** Tom-Tom has quit IRC06:02
*** afazekas has quit IRC06:11
*** afazekas has joined #openstack-meeting06:11
*** e0ne has quit IRC06:13
*** chyka has joined #openstack-meeting06:15
*** e0ne has joined #openstack-meeting06:16
*** chyka has quit IRC06:20
*** armax has joined #openstack-meeting06:21
*** e0ne has quit IRC06:21
*** kiennt26 has quit IRC06:22
*** kiennt26 has joined #openstack-meeting06:22
*** janki has quit IRC06:22
*** Dinesh_Bhor has quit IRC06:23
*** markvoelker has joined #openstack-meeting06:25
*** armax has quit IRC06:28
*** e0ne has joined #openstack-meeting06:28
*** eN_Guruprasad_Rn has joined #openstack-meeting06:31
*** e0ne has quit IRC06:33
*** yamamoto has joined #openstack-meeting06:35
*** wanghao_ has quit IRC06:35
*** wanghao has joined #openstack-meeting06:35
*** wanghao has quit IRC06:37
*** wanghao has joined #openstack-meeting06:37
*** Dinesh_Bhor has joined #openstack-meeting06:37
*** Tom-Tom has joined #openstack-meeting06:41
*** yamamoto has quit IRC06:41
*** e0ne has joined #openstack-meeting06:42
*** e0ne has quit IRC06:47
*** edmondsw has joined #openstack-meeting06:51
*** dmacpher has quit IRC06:52
*** e0ne has joined #openstack-meeting06:53
*** marios has joined #openstack-meeting06:55
*** edmondsw has quit IRC06:55
*** e0ne has quit IRC06:58
*** markvoelker has quit IRC06:59
*** e0ne has joined #openstack-meeting06:59
*** jchhatbar has joined #openstack-meeting07:00
*** slaweq_ has joined #openstack-meeting07:02
*** e0ne has quit IRC07:04
*** slaweq_ has quit IRC07:07
*** chyka has joined #openstack-meeting07:08
*** armax has joined #openstack-meeting07:10
*** armax has quit IRC07:11
*** chyka has quit IRC07:13
*** pchavva has quit IRC07:14
*** e0ne has joined #openstack-meeting07:14
*** andreas_s has joined #openstack-meeting07:18
*** salv-orlando has joined #openstack-meeting07:19
*** e0ne has quit IRC07:20
*** salv-orlando has quit IRC07:23
*** e0ne has joined #openstack-meeting07:28
*** rcernin has quit IRC07:31
*** e0ne has quit IRC07:33
*** e0ne has joined #openstack-meeting07:35
*** unicell has joined #openstack-meeting07:37
*** ircuser-1 has joined #openstack-meeting07:39
*** e0ne has quit IRC07:41
*** yamamoto has joined #openstack-meeting07:45
*** slaweq has joined #openstack-meeting07:46
*** mmethot_ has joined #openstack-meeting07:49
*** mmethot has quit IRC07:51
*** e0ne has joined #openstack-meeting07:51
*** salv-orlando has joined #openstack-meeting07:54
*** e0ne has quit IRC07:55
*** e0ne has joined #openstack-meeting07:58
*** rcernin has joined #openstack-meeting08:02
*** d0ugal has quit IRC08:03
*** e0ne has quit IRC08:03
*** d0ugal has joined #openstack-meeting08:07
*** Dinesh_Bhor has quit IRC08:07
*** e0ne has joined #openstack-meeting08:07
*** Dinesh_Bhor has joined #openstack-meeting08:08
*** phil_ has joined #openstack-meeting08:08
*** phil_ is now known as Guest7820208:08
*** slaweq_ has joined #openstack-meeting08:09
*** wanghao has quit IRC08:09
*** HeOS has joined #openstack-meeting08:09
*** unicell has quit IRC08:09
*** slaweq_ has quit IRC08:14
*** e0ne has quit IRC08:16
*** Dinesh_Bhor has quit IRC08:17
*** Dinesh_Bhor has joined #openstack-meeting08:18
*** Dinesh_Bhor has quit IRC08:21
*** alexchadin has joined #openstack-meeting08:22
*** wanghao has joined #openstack-meeting08:24
*** Dinesh_Bhor has joined #openstack-meeting08:24
*** e0ne has joined #openstack-meeting08:28
*** andreas__ has joined #openstack-meeting08:30
*** jamesmcarthur has joined #openstack-meeting08:33
*** andreas_s has quit IRC08:34
*** reedip_ has joined #openstack-meeting08:35
*** jamesmcarthur has quit IRC08:37
*** edmondsw has joined #openstack-meeting08:39
*** eN_Guruprasad_Rn has quit IRC08:42
*** eN_Guruprasad_Rn has joined #openstack-meeting08:42
*** Dinesh_Bhor has quit IRC08:43
*** edmondsw has quit IRC08:44
*** wanghao has quit IRC08:45
*** salv-orlando has quit IRC08:45
*** salv-orlando has joined #openstack-meeting08:46
*** alexchadin has quit IRC08:47
*** alexchadin has joined #openstack-meeting08:48
*** priteau has joined #openstack-meeting08:50
*** salv-orlando has quit IRC08:51
*** epico has quit IRC08:52
*** epico has joined #openstack-meeting08:52
*** markvoelker has joined #openstack-meeting08:56
*** chyka has joined #openstack-meeting08:58
*** salv-orlando has joined #openstack-meeting08:58
*** brault has joined #openstack-meeting08:59
*** e0ne has quit IRC09:00
*** andreas_s has joined #openstack-meeting09:00
*** wanghao has joined #openstack-meeting09:00
*** chenying has joined #openstack-meeting09:01
chenying#startmeeting karbor09:01
openstackMeeting started Tue Dec 19 09:01:46 2017 UTC and is due to finish in 60 minutes.  The chair is chenying. Information about MeetBot at http://wiki.debian.org/MeetBot.09:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:01
*** openstack changes topic to " (Meeting topic: karbor)"09:01
openstackThe meeting name has been set to 'karbor'09:01
jiaopengjuhi chenying09:02
*** chyka has quit IRC09:02
chenyingThere is no topic today. Do you have any topic want to discuss?09:02
jiaopengjuno yet :)09:03
chenying#topic Open Discussion09:03
*** openstack changes topic to "Open Discussion (Meeting topic: karbor)"09:03
chenyingI have release karbor python-karborclient karbor-dashborad a new version in queens cycle.09:03
chenyingI plan to release them to 1.0.0 version at the end of this cycle.09:04
jiaopengjugood job09:04
*** andreas__ has quit IRC09:04
chenyingYou also do a good job.09:04
*** Dinesh_Bhor has joined #openstack-meeting09:05
jiaopengjuI am struggling with openstack ansible :(09:05
jiaopengjuI will ask more help from ansible group09:06
jiaopengjuTo ensure we can finish this job before the end of this cycle09:07
chenyingWe may need ask for helps from other guys.09:07
chenyingSound good.09:07
chenyingI have submitted all the patches about json schema.09:07
jiaopengjunice :)09:07
chenyingNext step, we may need pay more attention to bugfix.09:08
jiaopengjuit seems we have step 2 of json schema09:08
jiaopengjuremove the original validation?09:09
chenyingYes. I will submit a patch about it.09:09
*** Dinesh_Bhor has quit IRC09:10
chenyingSo all guys in karbor team did great job in queen cycle. Lots of bp and features have been finished in this sycle.09:11
chenyingwe may need do some work about bugfix, doc, api example in the next step09:12
jiaopengjuyes, the doc and api examples are really needed to update09:13
*** fzdarsky has joined #openstack-meeting09:15
chenyingIf we don't have any more topic to discuss, so I will end this meeting. We can discuss in karbor irc channel?09:15
*** wanghao has quit IRC09:18
*** Dinesh_Bhor has joined #openstack-meeting09:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:23
openstackMeeting ended Tue Dec 19 09:23:55 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:23
openstackMinutes:        http://eavesdrop01.openstack.org/meetings/karbor/2017/karbor.2017-12-19-09.01.html09:23
openstackMinutes (text): http://eavesdrop01.openstack.org/meetings/karbor/2017/karbor.2017-12-19-09.01.txt09:24
openstackLog:            http://eavesdrop01.openstack.org/meetings/karbor/2017/karbor.2017-12-19-09.01.log.html09:24
*** Dinesh_Bhor has quit IRC09:24
*** Dinesh_Bhor has joined #openstack-meeting09:25
*** markvoelker has quit IRC09:29
*** Dinesh_Bhor has quit IRC09:30
*** Dinesh_Bhor has joined #openstack-meeting09:33
*** wanghao has joined #openstack-meeting09:34
*** wanghao has quit IRC09:34
*** wanghao has joined #openstack-meeting09:35
*** Dinesh_Bhor has quit IRC09:42
*** eN_Guruprasad_Rn has quit IRC09:44
*** yangyapeng has quit IRC09:45
*** eN_Guruprasad_Rn has joined #openstack-meeting09:45
*** eN_Guruprasad_Rn has quit IRC09:49
*** eN_Guruprasad_Rn has joined #openstack-meeting09:49
*** eN_Guruprasad_Rn has quit IRC09:54
*** eN_Guruprasad_Rn has joined #openstack-meeting09:55
*** rarora has quit IRC09:57
*** wanghao has quit IRC09:58
*** wanghao has joined #openstack-meeting09:59
*** afazekas has quit IRC10:01
*** kiennt26 has quit IRC10:02
*** afazekas has joined #openstack-meeting10:07
*** fzdarsky has quit IRC10:08
*** ykatabam has quit IRC10:15
*** psachin has quit IRC10:24
*** markvoelker has joined #openstack-meeting10:26
*** edmondsw has joined #openstack-meeting10:27
*** e0ne has joined #openstack-meeting10:31
*** edmondsw has quit IRC10:32
*** reedip_ has quit IRC10:38
*** sambetts|afk is now known as sambetts10:39
*** epico has quit IRC10:41
*** jchhatbar is now known as janki10:41
*** niska has quit IRC10:42
*** brault has quit IRC10:44
*** brault has joined #openstack-meeting10:45
*** electrofelix has joined #openstack-meeting10:46
*** yangyapeng has joined #openstack-meeting10:47
*** brault has quit IRC10:50
*** brault has joined #openstack-meeting10:51
*** fzdarsky has joined #openstack-meeting10:51
*** niska has joined #openstack-meeting10:52
*** Exhar has joined #openstack-meeting10:53
*** yangyapeng has quit IRC10:53
*** yamamoto has quit IRC10:55
*** yamamoto has joined #openstack-meeting10:55
*** Tom-Tom has quit IRC10:56
*** yamamoto has quit IRC10:56
*** yamamoto has joined #openstack-meeting10:56
*** reedip_ has joined #openstack-meeting10:57
*** markvoelker has quit IRC11:00
*** yangyapeng has joined #openstack-meeting11:03
*** caowei has quit IRC11:03
*** yangyapeng has quit IRC11:08
*** salv-orlando has quit IRC11:09
*** salv-orlando has joined #openstack-meeting11:09
*** yamamoto has quit IRC11:09
*** andreas_s has quit IRC11:10
*** andreas_s has joined #openstack-meeting11:11
*** yamamoto has joined #openstack-meeting11:13
*** salv-orlando has quit IRC11:14
*** yamamoto has quit IRC11:18
*** andreas_s has quit IRC11:24
*** yangyapeng has joined #openstack-meeting11:24
*** andreas_s has joined #openstack-meeting11:26
*** yangyapeng has quit IRC11:29
*** andreas_s has quit IRC11:30
*** jamesmcarthur has joined #openstack-meeting11:33
*** reedip_ has quit IRC11:36
*** jamesmcarthur has quit IRC11:38
*** ZacharyMa has quit IRC11:38
*** brault has quit IRC11:39
*** andreas_s has joined #openstack-meeting11:40
*** e0ne has quit IRC11:41
*** alexchadin has quit IRC11:44
*** yangyapeng has joined #openstack-meeting11:45
*** brault has joined #openstack-meeting11:45
*** yangyapeng has quit IRC11:49
*** andreas_s has quit IRC11:50
*** brault has quit IRC11:50
*** andreas_s has joined #openstack-meeting11:51
*** e0ne has joined #openstack-meeting11:51
*** andreas_s has quit IRC11:53
*** reedip_ has joined #openstack-meeting11:53
*** andreas_s has joined #openstack-meeting11:53
*** reedip_ has quit IRC11:57
*** markvoelker has joined #openstack-meeting11:57
*** reedip_ has joined #openstack-meeting11:59
*** raildo has joined #openstack-meeting12:00
*** yangyapeng has joined #openstack-meeting12:05
*** yamamoto has joined #openstack-meeting12:06
*** alexchadin has joined #openstack-meeting12:06
*** salv-orlando has joined #openstack-meeting12:10
*** yamamoto has quit IRC12:10
*** yangyapeng has quit IRC12:11
*** salv-orlando has quit IRC12:14
*** edmondsw has joined #openstack-meeting12:16
*** edmondsw has quit IRC12:20
*** e0ne has quit IRC12:22
*** links has quit IRC12:23
*** yangyapeng has joined #openstack-meeting12:29
*** markvoelker has quit IRC12:29
*** brault has joined #openstack-meeting12:30
*** reedip_ has quit IRC12:33
*** anilvenkata has joined #openstack-meeting12:34
*** yangyapeng has quit IRC12:34
*** yamamoto has joined #openstack-meeting12:38
*** yamamoto has quit IRC12:39
*** alexchadin has quit IRC12:46
*** eN_Guruprasad_Rn has quit IRC12:48
*** weshay_pto is now known as weshay12:48
*** yangyapeng has joined #openstack-meeting12:49
*** hichihara has joined #openstack-meeting12:50
*** aarefiev has joined #openstack-meeting12:50
*** bobh has joined #openstack-meeting12:52
*** bobh has quit IRC12:53
*** yangyapeng has quit IRC12:53
*** rajulk has joined #openstack-meeting12:55
*** zhurong has joined #openstack-meeting13:00
*** zhurong has quit IRC13:02
*** zhurong has joined #openstack-meeting13:03
*** wanghao has quit IRC13:04
*** wanghao has joined #openstack-meeting13:04
*** ruijie has joined #openstack-meeting13:04
*** wanghao has quit IRC13:05
*** wanghao has joined #openstack-meeting13:05
*** wanghao has quit IRC13:05
*** wanghao has joined #openstack-meeting13:06
*** wanghao has quit IRC13:06
*** wanghao has joined #openstack-meeting13:06
*** wanghao has quit IRC13:07
*** wanghao has joined #openstack-meeting13:07
*** wanghao has quit IRC13:08
*** wanghao has joined #openstack-meeting13:08
*** wanghao has quit IRC13:08
*** wanghao has joined #openstack-meeting13:09
*** rbowen has joined #openstack-meeting13:09
*** wanghao has quit IRC13:09
*** wanghao has joined #openstack-meeting13:10
*** yangyapeng has joined #openstack-meeting13:10
*** wanghao has quit IRC13:10
*** wanghao has joined #openstack-meeting13:10
*** salv-orlando has joined #openstack-meeting13:11
*** wanghao has quit IRC13:11
*** janki has quit IRC13:11
*** janki has joined #openstack-meeting13:11
*** wanghao has joined #openstack-meeting13:12
*** d0ugal has quit IRC13:14
*** yangyapeng has quit IRC13:15
*** salv-orlando has quit IRC13:15
*** wanghao has quit IRC13:16
*** rossella_s has joined #openstack-meeting13:18
*** links has joined #openstack-meeting13:18
*** rcernin has quit IRC13:20
*** d0ugal has joined #openstack-meeting13:22
*** zhurong has quit IRC13:25
*** dprince has joined #openstack-meeting13:25
*** sgrasley1 has quit IRC13:26
*** markvoelker has joined #openstack-meeting13:27
*** markvoelker has quit IRC13:28
*** markvoelker has joined #openstack-meeting13:29
*** yangyapeng has joined #openstack-meeting13:30
*** Tom-Tom has joined #openstack-meeting13:31
*** coolsvap has quit IRC13:32
*** guhcampos has joined #openstack-meeting13:35
*** yangyapeng has quit IRC13:35
*** sgrasley1 has joined #openstack-meeting13:36
*** d0ugal has quit IRC13:37
*** pchavva has joined #openstack-meeting13:38
*** fnaval has joined #openstack-meeting13:38
*** yangyapeng has joined #openstack-meeting13:39
*** d0ugal has joined #openstack-meeting13:39
*** yamamoto has joined #openstack-meeting13:40
*** fnaval has quit IRC13:42
*** yangyapeng has quit IRC13:44
*** lhx_ has joined #openstack-meeting13:44
*** yamamoto has quit IRC13:48
*** mlavalle has joined #openstack-meeting13:50
*** Tom-Tom_ has joined #openstack-meeting13:51
*** makowals has joined #openstack-meeting13:53
*** annp has joined #openstack-meeting13:54
*** Tom-Tom has quit IRC13:54
*** hoangcx_ has joined #openstack-meeting13:55
*** mriedem has joined #openstack-meeting13:58
*** boden has joined #openstack-meeting13:59
*** jlibosva has joined #openstack-meeting14:00
jlibosva#startmeeting networking14:00
openstackMeeting started Tue Dec 19 14:00:40 2017 UTC and is due to finish in 60 minutes.  The chair is jlibosva. 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
jlibosvaHello friends14:00
jlibosva#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: networking)"14:01
mlavallehowdy boden, from Texas14:01
*** shintaro has joined #openstack-meeting14:01
jlibosvaWe're now working towards Q3 milestone14:01
jlibosva#link https://releases.openstack.org/queens/schedule.html#q-314:01
jlibosvathe date is set to Jan 2514:02
jlibosvathis is the last meeting in 2017 as there won't be a meeting next week on Dec 2514:02
* mlavalle will send a message to the ML14:03
jlibosvaI see you put it to agenda :) so I'm going according it14:03
jlibosvanext announcement is rather a reminder to not forget to register for the PTG14:03
jlibosva#link https://www.openstack.org/ptg/14:03
*** links has quit IRC14:03
jlibosvaand those were all announcements from me or wiki page14:04
jlibosvadoes anybody want to announce anything?14:04
*** cdub has joined #openstack-meeting14:04
hichiharaWhen does meeting of 2018 start? Jan 2?14:04
hichiharaI got it14:04
mlavalleI will indicate that in the message to the ML14:04
mlavallemight be a slow one, though14:05
jlibosvawe need to make sure as I think the meetings are based on even and odd weeks14:05
mlavallejlibosva: ahhh, right14:05
jlibosvaso depending what is this week :)14:05
jlibosvait's 5114:06
jlibosvaso I guess mlavalle was right, it's Jan 214:06
mlavalleyeah, so we can resume on Januay 2nd14:06
bcafarelso week 1 should be on Tuesday :)14:06
jlibosvaok, thanks :) anything else?14:06
*** yangyapeng has joined #openstack-meeting14:06
jlibosvalet's jump to blueprints then14:07
jlibosva#topic Blueprints14:07
*** openstack changes topic to "Blueprints (Meeting topic: networking)"14:07
jlibosva#link https://launchpad.net/neutron/+milestone/queens-314:07
jlibosvadoes anybody have anything related to blueprints? any issues or blockers?14:08
annpFor logging, I'd like to change entry point of logging plugin14:08
annpfrom "logapi" to "log"14:08
jlibosvahttps://review.openstack.org/#/c/528977/ ?14:08
amotokisorry for interrupt. the week of Dec 25 2017 is ISO week 52, and the week of Jan 2 2018 is ISO week 1, so we will have regular rotation of even/odd.14:09
annpCould you please have a look?14:09
amotoki"ncal -w -3" helps me14:09
annpJlibosva: yes.14:09
jlibosvaamotoki: I think that's correct. That means we have odd week now and we'll start with odd week, no?14:09
amotokijlibosva: right14:10
amotokijlibosva: most years has 52 ISO weeks14:10
jlibosvaamotoki: thanks for bringing this up14:10
jlibosvaregarding the patch from annp - do we have any promise towards trunk chasers we should keep compatibility in the master or we good to change it?14:10
jlibosvaby me the patch is fine but maybe there is some policy?14:11
mlavalleIMO, we can change14:11
*** salv-orlando has joined #openstack-meeting14:11
*** yangyapeng has quit IRC14:12
annpjlibosva, mlavalle, thanks. :)14:12
jlibosvaok, now we need to decide whether it's logging or just log :)14:12
amotoki+1 to change. even if there are trunk chasers, the feature is not complete14:12
mlavalleamotoki: you got it14:12
annpamotoki: +114:13
jlibosvaok, seems like we have an agreement here14:13
jlibosvaany other blueprints need attention?14:13
annpjlibosva: thanks14:14
jlibosvait seems there are none so let's move on14:14
jlibosva#topic Starter Approved RFEs14:14
*** openstack changes topic to "Starter Approved RFEs (Meeting topic: networking)"14:14
jlibosvathere is one RFE at the wiki14:14
jlibosva#link https://bugs.launchpad.net/neutron/+bug/165393214:14
openstackLaunchpad bug 1653932 in neutron "[rfe] network router:external field not exported" [Wishlist,Triaged]14:14
jlibosvaif you feel like working on rfe, this is a very good candidate14:15
jlibosvamlavalle: do you want to add anything to this rfe?14:15
mlavalleyou did great. Thanks!14:15
jlibosvaok, let's move on then14:16
jlibosva#topic Bugs14:16
*** openstack changes topic to "Bugs (Meeting topic: networking)"14:16
jlibosvaslaweq sent out the bug deputy report to ML14:16
jlibosva#link http://lists.openstack.org/pipermail/openstack-dev/2017-December/125718.html14:16
*** salv-orlando has quit IRC14:16
slaweqyes, if You want me to add something, just ask :)14:17
*** links has joined #openstack-meeting14:17
jlibosvasounds like there is nothing burning there at this point, right?14:17
slaweqit looks so14:18
mlavallethere was a critical bug last week, I think14:18
mlavallehang on14:18
slaweqbut there was few which I need help on prioritize14:18
haleybmlavalle: i updated the review after some testing14:18
slaweqmlavalle: there was high for sure: https://bugs.launchpad.net/neutron/+bug/173861214:18
openstackLaunchpad bug 1738612 in neutron "Floating IP update breakes decomposed plugins" [High,Fix released] - Assigned to Gary Kotton (garyk)14:18
mlavalleI was talking about the one haleyb pointed out14:19
*** Tom-Tom_ has quit IRC14:19
haleybbug 173229414:19
openstackbug 1732294 in neutron "Probable DOS in linuxbridge" [Critical,In progress] https://launchpad.net/bugs/1732294 - Assigned to Brian Haley (brian-haley)14:19
*** Tom-Tom has joined #openstack-meeting14:19
slaweqmlavalle: but it wasn't reported last week :)14:20
mlavallehaleyb: thanks!14:20
haleybthat required a lot of extra work to deal with restarts since it left stale chains and rules around14:20
haleybof course there are no existing tests... :(14:20
mlavallehaleyb: are you planning to add tests?14:21
haleybis it fixed if we don't add tests? :)  i'll try to add some unit tests quickly14:21
mlavalleThanks :-)14:22
*** HoloIRCUser2 has joined #openstack-meeting14:22
mlavalleslaweq: thanks for the great report!14:22
*** HoloIRCUser2 is now known as reedip-holo14:23
jlibosvaslaweq++ :)14:23
*** salv-orlando has joined #openstack-meeting14:23
slaweqmlavalle: jlibosva: you welcome :)14:23
jlibosvanext week seems like yamamoto is a bug deputy but let's nope we won't get many reports over the holidays :-p14:23
*** Tom-Tom has quit IRC14:24
jlibosva#topic Docs14:24
*** openstack changes topic to "Docs (Meeting topic: networking)"14:24
jlibosvaboden: hi :)14:24
* mlavalle will keep fingers crosssed14:24
bodenhi, nothing new on the docs front14:24
*** yangyapeng has joined #openstack-meeting14:24
jlibosvaalright :) thanks, we can move fast today14:25
jlibosva#topic OSC14:25
*** openstack changes topic to "OSC (Meeting topic: networking)"14:25
jlibosvaamotoki: hi :)14:25
amotokiI think VPNaaS OSC support is ready for review14:25
mlavalleah great14:25
amotokiVPNaaS is being back to the stadium thoguh the governance patch merge faield due to the docs jobs :(14:26
jlibosvacongrats to all involved getting it back :)14:26
amotokiVPNaaS OSC support and log support are good candidates for queens client.14:27
mlavallethat's hoangcx_, yamamoto and others14:27
amotokiif there are any other client support for queens, let us know here.14:27
mlavalleamotoki: do you have the links handy?14:27
amotokivpnaas: https://review.openstack.org/43997814:27
amotokilog support https://review.openstack.org/40981914:27
*** sgrasley1 has left #openstack-meeting14:28
amotokithat's all from me this week14:28
jlibosvawow, the log patch celebrated one year birthday recently :)14:28
jlibosvaamotoki: thanks for updates14:28
amotokiany bot to celebrate an anniversary of a patch? :)14:29
*** yangyapeng has quit IRC14:29
mlavallethat's a good idea, LOL14:29
jlibosvaok, moving to the next topic14:30
jlibosvawhich is14:30
jlibosva#topic neutron-lib14:30
*** openstack changes topic to "neutron-lib (Meeting topic: networking)"14:30
jlibosvaboden: hi again :)14:30
*** andreas_s has quit IRC14:30
*** andreas_s has joined #openstack-meeting14:30
bodenso nothing new from last time… I would like to mention that we haven’t landed any lib patches in quite some time; a month or so14:31
bodenI wonder if we shouldn’t consider expanding the +1W rights on lib14:31
mlavalleboden: I will take a look this week on neutron-lib patches14:32
mlavalleI will make a point of reviewing at least once a week14:32
mlavallelet's do that for a few weeks14:33
bodenmlavalle: ack thanks… but I think longer term we need more than just you reviewing from a +W perspective14:33
amotokiI tend to agree expanding +W right of neutron-lib is worth considered.14:33
mlavalleI agree14:33
mlavalleI didn't mean I was opposing that14:33
bodenwhats the right forum to discuss that?? an RFE?14:33
mlavalledo you have candidates in mind?14:34
amotokifolks who understand neutron-lib policy well are worth considered like stable team.14:34
amotokiboden is a good candidate to  me :)14:34
reedip-holo+1 :)14:34
bodenIMO minally it seems the neutron core team should have +W rights14:34
mlavalleboden: you have +W in nuetron-lib, right?14:35
bodenmlavalle I do not, only neutron-drivers team does14:35
mlavalleI'll fix that today14:35
mlavalleI wasn't aware14:36
jlibosvait's good you've brought this up boden , I also thought you have the powers :)14:36
bodenlooking for the ACL link14:36
*** kiennt26 has joined #openstack-meeting14:37
bodenI will find it a ping it to the neutron room14:37
bodenah yes thanks14:37
jlibosvaI see boden there14:37
mlavalleand I'll make sure the Neutron core team can +W in neutron-lib14:37
jlibosvaooh, it's specific to +W14:37
jlibosvaI see now14:37
bodenLabel Workflow Exclusive neutron-drivers-core14:38
mlavalleboden: will fix it14:38
mlavallethanks for bringing it up14:38
bodenthanks for listening :)14:38
bodenfinally I will just mention I have a few NeutronLibImpact patches out there to consume some of the callback event payloads14:39
bodenwe don’t have to digress, just FYI14:39
bodenand thats all from me, unless questions14:39
* mlavalle is already looking at that one14:39
jlibosvaseems like there are no questions14:40
jlibosvathanks boden :)14:40
jlibosva#topic Open Agenda14:40
*** openstack changes topic to "Open Agenda (Meeting topic: networking)"14:40
jlibosvaI don't see any topic at the wiki page14:40
jlibosvadoes anybody have anything to dicuss?14:40
mlavalleI have one14:40
mlavallebut will wait for others to speak up first14:41
slaweqI wanted to ask once again about neutronclient status as there is couple quite new patches for it currently14:41
*** shintaro has quit IRC14:41
slaweqAFAIR someone wanted to discuss it on ML but I didn't see any email about that (maybe I missed it)14:42
*** VW has joined #openstack-meeting14:43
amotokislaweq: good point. it is about neutron CLI future.14:43
amotokiwe are still accepting patches on OSC plugins and python bindings. do you see several patches on 'neutron' CLI?14:43
slaweqwhat about patches like for example https://review.openstack.org/#/c/526984/14:44
slaweqor https://review.openstack.org/#/c/526981/14:44
amotokipatches from hongbin are both about python bindings14:44
*** andreas_s has quit IRC14:45
amotokiso they are no problem to be merged.14:45
slaweqamotoki: ok14:45
mlavalleslaweq: you happy?14:45
slaweqmlavalle: I think so, thx14:45
*** andreas_s has joined #openstack-meeting14:45
mlavalleamotoki: thanks for the wisdom :-)14:46
*** gouthamr has joined #openstack-meeting14:46
jlibosvamlavalle: perhaps you want to bring your topic now? :)14:47
mlavalleI just wanted to thank each and everyone of you for your hard work during 201714:47
mlavalleIt is a privilege to belong to this team14:47
*** felipemonteiro has joined #openstack-meeting14:47
*** cleong has joined #openstack-meeting14:47
*** andreas_s has quit IRC14:48
mlavalleIt is a humbling experience the amount of learning I get from you all14:48
*** andreas_s has joined #openstack-meeting14:48
mlavalleI wish you all a great holidays season14:48
hichiharamlavalle: you too :)14:49
mlavalleif in your country or system of beliefs you don't have a holiday over the next copuiple of weeks, please invent one14:49
mlavalleand enjoy it14:49
*** rbudden has joined #openstack-meeting14:49
amotokigood idea :)14:49
haleybmlavalle: thanks!  and don't work too hard over the holidays14:49
mlavalleand I wish you all a very succesful 1814:49
jlibosvamlavalle: thanks :)14:50
mlavallethat's it14:50
slaweqthanks :)14:50
jlibosvaI also wish the best in 2018 to all of you14:50
jlibosvathis is the last meeting this year, so thanks for keeping coming :)14:50
annpthanks. happy holiday season :)14:50
hichiharaThanks great PTL :)14:50
jlibosvasee you all next year, I'm about to close this meeting14:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:51
openstackMeeting ended Tue Dec 19 14:51:48 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:51
openstackMinutes:        http://eavesdrop01.openstack.org/meetings/networking/2017/networking.2017-12-19-14.00.html14:51
openstackMinutes (text): http://eavesdrop01.openstack.org/meetings/networking/2017/networking.2017-12-19-14.00.txt14:51
openstackLog:            http://eavesdrop01.openstack.org/meetings/networking/2017/networking.2017-12-19-14.00.log.html14:51
*** boden has left #openstack-meeting14:51
*** hichihara has quit IRC14:52
*** hoangcx_ has quit IRC14:52
mlavalleslaweq: I'll be a few minutes late14:54
slaweqmlavalle: no problem14:54
slaweqthx for info14:54
*** pchavva has quit IRC14:59
slaweq#startmeeting neutron_qos15:01
*** zaneb has joined #openstack-meeting15:01
openstackMeeting started Tue Dec 19 15:01:20 2017 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:01
openstackThe meeting name has been set to 'neutron_qos'15:01
slaweqwelcome on last QoS meeting this year :)15:01
*** yangyapeng has joined #openstack-meeting15:01
slaweqmlavalle will be few minutes late so I think we can wait for him15:02
* mlavalle joins the meeting15:02
*** pchavva has joined #openstack-meeting15:03
*** andreas_s has quit IRC15:03
*** andreas_s has joined #openstack-meeting15:03
slaweqhi mlavalle15:04
*** salv-orlando has quit IRC15:04
slaweqit looks that we are only two on meeting :/15:04
*** salv-orlando has joined #openstack-meeting15:04
mlavallelet's do a quick one15:04
slaweqso first topic is15:05
slaweq#topic RFEs15:05
*** openstack changes topic to "RFEs (Meeting topic: neutron_qos)"15:05
slaweqwe have one new rfe bug reported:15:05
*** jlibosva has left #openstack-meeting15:05
slaweq#link https://bugs.launchpad.net/neutron/+bug/172757815:05
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Confirmed]15:05
slaweqit's even not triagged yet15:05
slaweqand I didn't have time to read it yet15:06
mlavalleyamamoto already chimed in15:06
slaweqreedip-holo: hi15:06
mlavalleit would be great if you can take a look at it15:06
mlavallehey reedip-holo15:07
slaweqmlavalle: I will read it carefully tomorow15:07
mlavallethanks :-)15:07
slaweq#action slaweq will look at https://bugs.launchpad.net/neutron/+bug/172757815:07
openstackLaunchpad bug 1727578 in neutron "[RFE]Support apply qos policy in VPN service" [Wishlist,Confirmed]15:07
slaweqnext one15:07
slaweq#link https://bugs.launchpad.net/neutron/+bug/164951715:07
openstackLaunchpad bug 1649517 in neutron "qos policy attached to network, qos_policy_id is reflecting on neutron net-show , but not on the port with neutron port-show" [Wishlist,Triaged] - Assigned to Reedip (reedip-banerjee)15:07
slaweqmlavalle: it's still waiting for drivers team :)15:07
reedip-holoIt's still stuck15:07
slaweqwill be drivers meeting this week?15:08
mlavalleit was discussed during last meeting15:08
slaweqah, so I missed logs from it15:08
*** salv-orlando has quit IRC15:09
mlavallethe team didn't see a strong reason to implement it15:09
mlavalleI will update it later today15:10
slaweqmlavalle: ok, thx15:10
mlavalleand yo can respond there15:10
mlavallebut the point was15:10
*** marst has joined #openstack-meeting15:10
mlavallethat you can always look at the port15:10
mlavalleand the show it's network15:11
*** kiennt26 has quit IRC15:11
mlavalleand see if it is the same policy15:11
*** kiennt26 has joined #openstack-meeting15:11
slaweqyes, You can15:11
reedip-holoBut that's not the exact thing achieved in this RFE, I guess15:11
slaweqbut it was more for the case when port inherits policy from network15:11
slaweqand don't have own policy15:11
slaweqthen it is not clear that port have got any policy attached15:12
mlavallein that situation.....15:12
*** andreas_s has quit IRC15:12
slawequnless user will not do network-show for each port which he have15:12
mlavallewill the policy-id shown in the port will be the same as in the network?15:13
*** andreas_s has joined #openstack-meeting15:13
slaweqthis patch which reedip-holo did adds additional field to port15:13
mlavalleI know15:13
mlavallebut currently15:13
mlavallebefore the patch15:13
slaweqbefore this patch there will be no policy-id if it is inherited from network15:14
mlavallewhat happens if the port inherited it's network policy?15:14
slaweqthis field is empty15:14
reedip-holoYep as slaweq said15:14
slaweqfor port15:14
mlavalleso we need to clarify that in the rfe15:14
mlavallewe misunderstood15:14
slaweqreedip-holo: will You write it there?15:15
mlavalleso I will post a response from the last meeting15:15
reedip-holoOk I will15:15
mlavalleand then reedip-holo can reply15:15
reedip-holoOk ok15:15
slaweqmlavalle: yep, thx15:15
reedip-holoOk :)15:15
*** salv-orlando has joined #openstack-meeting15:15
mlavalleand it's at the top of the list15:16
mlavalleso we will discuss again this Friday15:16
reedip-holoOk gr815:16
slaweqgood, thx :)15:16
slaweqso moving to next one15:17
slaweq#link https://bugs.launchpad.net/neutron/+bug/159661115:17
openstackLaunchpad bug 1596611 in neutron "[RFE] Create L3 IPs with qos (rate limit)" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)15:17
slaweqthis is FIP QoS15:17
slaweqit is almost merged :)15:17
slaweqremaining patches waiting for review #link https://review.openstack.org/#/q/topic:bp/floating-ip-rate-limit+(status:open+OR+status:merged)15:17
mlavalleI have a couple of questions15:17
slaweqmlavalle: shoot15:18
mlavalle1) you tested the agent side and it works, right?15:18
slaweqmlavalle: yes, I tested it on my devstack and it looked that it works15:18
*** anilvenkata has quit IRC15:18
mlavalle2) in the docs patch, he states that if a policy with no limit rules is attached to a FIP, it will do nothing15:19
slaweqat least on tc side everything looked good on my side15:19
slaweqyes, it is done in same way like it was some time ago for ports/network15:19
*** aarefiev has quit IRC15:20
*** chyka has joined #openstack-meeting15:20
mlavallebut can't we check that in the server and return BadRequest15:20
slaweqbut later we added validation mechanism when policy is attached for port or network15:20
slaweqI think we should but I think it can be next step maybe15:20
*** armax has joined #openstack-meeting15:20
*** anilvenkata has joined #openstack-meeting15:21
mlavalleslaweq: I agree. I just don't want to leave that in the docs15:21
*** reedip_ has joined #openstack-meeting15:21
mlavalleor at least clarify that it will be fixed15:21
slaweqIMHO it should be like that for now as it is true15:21
mlavallemakes sense?15:21
slaweqI agree that it can be clarify that it will be changed15:21
slaweqyes :)15:21
mlavalleok, cool15:21
mlavallewe are good15:22
slaweqand also I pointed in this docs patch that some update of qos internal document should be also updated15:22
mlavalledid he agree to that?15:22
slaweqit is not done still so IMO we should wait for that15:22
slaweqAFAIR he told something about completly new document for FIP QoS15:23
*** andreas_s has quit IRC15:23
slaweqI don't know if it is necessary but maybe his right :)15:23
slaweqok, next one?15:25
mlavallesaid couple of questions15:25
slaweqthx mlavalle15:25
*** bobh has joined #openstack-meeting15:26
slaweqso moving on15:26
slaweq#link https://bugs.launchpad.net/neutron/+bug/156096315:26
openstackLaunchpad bug 1560963 in neutron "[RFE] Minimum bandwidth support (egress)" [Wishlist,In progress]15:26
*** chyka has quit IRC15:26
slaweqthis one has no volunteer currently15:26
mlavalleis there a patchset already?15:26
slaweqand nothing changed since last time about it15:26
reedip_I think this wAS taken up by ralonsoh15:26
*** chyka has joined #openstack-meeting15:26
reedip_wasnt it?15:26
reedip_if there is some info, I can tke it up15:27
slaweqreedip_: it was15:27
*** andreas_s has joined #openstack-meeting15:27
*** kiennt26 has quit IRC15:27
slaweqbut later also hichihara was working on it15:28
slaweqbut his patch is abandoned for now15:28
slaweqand ralonsoh patch for LB was reverted probably because there was something wrong with it15:29
slaweqbut I'm not sure about that15:29
*** felipemonteiro has quit IRC15:29
slaweqif You would have anyone who wants to start working on it, that would be great :)15:29
reedip_I can get working on it15:30
slaweqreedip_: that would be great15:30
mlavallethanks reedip_15:30
*** felipemonteiro has joined #openstack-meeting15:30
slaweqif You will need anything, just ask me on irc15:30
*** reedip-holo has quit IRC15:30
reedip_yeah sure :)15:30
slaweqthx reedip_15:31
slaweqso last rfe which I have for today15:31
slaweq#link https://bugs.launchpad.net/neutron/+bug/169295115:31
openstackLaunchpad bug 1692951 in neutron "[RFE] DSCP mark on the outer header" [Wishlist,In progress] - Assigned to Ali Sanhaji (ali-sanhaji)15:31
*** chyka has quit IRC15:31
slaweqI was trying to catch author of this patch on IRC but I couldn't15:31
slaweqbut I was talking with tmorin and he told me that author should continue his work on it15:32
slaweqIt was almost ready as I remember15:32
slaweqmlavalle: what You think if I would continue work on this patch if author will be still not available for week or two?15:33
slaweqbecause I would like to finish it if it would be possible15:33
mlavallego for it15:33
slaweqmlavalle: ok, thx15:33
*** awaugama has joined #openstack-meeting15:34
slaweqso I will keep an eye on it15:34
*** andreas_s has quit IRC15:34
slaweqso, next topic is15:34
slaweq#topic Bugs15:34
*** openstack changes topic to "Bugs (Meeting topic: neutron_qos)"15:34
*** andreas_s has joined #openstack-meeting15:34
slaweqthere is couple of QoS related bugs reported15:35
slaweq#link https://bugs.launchpad.net/neutron/+bug/166210915:35
openstackLaunchpad bug 1662109 in neutron "tempest scenario test_qos fails intermittently" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)15:35
slaweqrecently I was trying to find on logstash if it is still an issue15:35
slaweqbut it looks that test results from this job are not indexed on logstash15:35
slaweqI couldn't find any results from it :/15:36
slaweqmlavalle: maybe You can help on checking this logs on logstash? and if job is configured properly?15:36
mlavalleslaweq: ok, I will take a look15:37
slaweqmlavalle: thx15:37
slaweqit's neutron-tempest-plugin-dvr-multinode-scenario job15:37
slaweqI can send You query which I was trying on logstash if You want15:38
slaweqbut that can be after meeting I think15:38
*** eharney has joined #openstack-meeting15:38
slaweqnext one15:39
slaweq#link https://bugs.launchpad.net/neutron/+bug/173364915:39
openstackLaunchpad bug 1733649 in neutron "fullstack neutron.tests.fullstack.test_qos.TestDscpMarkingQoSOvs.test_dscp_marking_packets(openflow-native) failure" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)15:39
slaweqthis is also related to failing tests (fullstack)15:39
slaweqso I added some additional logs of tcpdump output but this issue didn't happen since few days15:39
slaweqso I'm just checking every morning if I will find something15:40
slaweqnot too much to add here15:40
*** julim has joined #openstack-meeting15:40
*** julim has quit IRC15:40
slaweqnext one15:40
slaweq#link https://bugs.launchpad.net/neutron/+bug/173667415:40
openstackLaunchpad bug 1736674 in neutron "sg rules are sometimes not applied" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)15:40
slaweqthat is also assigned to me15:41
slaweqand it has patch ready to review: https://review.openstack.org/#/c/527965/15:41
slaweqI would be grateful if You could look on it15:41
reedip_in my To DO list now15:42
slaweqit's related to qos because DSCP marking packets in linuxbridge agent breaks security groups rules in iptables15:42
slaweqreedip_: thx15:42
slaweqnext one is also about failing fullstack test15:42
slaweq#link https://bugs.launchpad.net/neutron/+bug/173789215:42
openstackLaunchpad bug 1737892 in neutron "Fullstack test test_qos.TestBwLimitQoSOvs.test_bw_limit_qos_port_removed failing many times" [High,Confirmed]15:42
slaweqI found that it happen few times so I reported it as bug15:43
slaweqbut I haven't got time to debug it yet15:43
slaweqany questions or we can go to next one?15:44
*** liusheng has quit IRC15:45
reedip_we can move on15:45
*** liusheng has joined #openstack-meeting15:45
slaweqmlavalle: are You still with us? :)15:45
slaweqso next15:45
slaweq#link https://bugs.launchpad.net/neutron/+bug/167687715:45
openstackLaunchpad bug 1676877 in neutron "Increase "TestQosPlugin.test_update_policy_rule" coverage" [Medium,In progress] - Assigned to Reedip (reedip-banerjee)15:45
mlavalleslaweq: yes15:45
slaweqreedip_: mlavalle reviewed Your patch today15:46
slaweqreedip_: please check his comments15:46
slaweqmlavalle: great :)15:46
reedip_I would tomorrow...15:46
mlavalleI'm ok with the code15:46
reedip_I am tired today ( its 2115 here )15:46
slaweqreedip_: sure :)15:46
mlavalleI just think the commit message doesn't reflect all the code does15:46
reedip_okie dokie15:47
slaweqok, next one is #link https://bugs.launchpad.net/neutron/+bug/173679215:47
openstackLaunchpad bug 1736792 in neutron "DSCP marking QOS policy applied to port not properly updating OVS flow table" [Medium,New]15:47
slaweqit was reported for Newton release15:48
slaweqso I think that we should first check if it's still an issue for master15:48
mlavallegood idea :-)15:49
slaweqI will add it to my list of todos but if someone would have time to check it, would be great15:49
slaweq#action slaweq check if https://bugs.launchpad.net/neutron/+bug/1736792 is still an issue on master15:49
openstackLaunchpad bug 1736792 in neutron "DSCP marking QOS policy applied to port not properly updating OVS flow table" [Medium,New]15:49
slaweqnext #link https://bugs.launchpad.net/neutron/+bug/172472915:49
openstackLaunchpad bug 1724729 in neutron "ovs-lib not support qos type egress-policer for ovs-dpdk" [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)15:49
slaweqpatch is in review: #link https://review.openstack.org/#/c/513398/15:50
slaweqplease review if You will have some time15:50
reedip_TO do List15:51
slaweqreedip_: thx15:51
slaweqok, and the last one for today #link https://bugs.launchpad.net/neutron/+bug/173285215:51
openstackLaunchpad bug 1732852 in neutron "neutron don't support Router gateway rate limit " [Low,In progress] - Assigned to Slawek Kaplonski (slaweq)15:51
slaweqthis is not new one15:51
*** edmondsw has joined #openstack-meeting15:52
slaweqpatch for docs is already merged15:52
slaweqbut it's kind of workaround only15:52
slaweqin future we should probably think how to fix it in better way :)15:52
*** salv-orlando has quit IRC15:52
*** salv-orlando has joined #openstack-meeting15:53
slaweqany questions to those bugs?15:53
slaweqreedip_: mlavalle ?15:53
*** jamesmcarthur has joined #openstack-meeting15:54
mlavallenone from me15:54
slaweqso last topic for today15:55
*** HoloIRCUser2 has joined #openstack-meeting15:55
slaweq#topic Open Discussion15:55
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_qos)"15:55
slaweqI don't have anything15:55
*** reedip_ has quit IRC15:55
*** HoloIRCUser2 is now known as reedip_15:55
slaweqdo You have something to add?15:55
mlavalleme neither15:55
reedip_Sorry I disconnected15:55
reedip_Nothing from my side15:56
reedip_Seems my PC is more sleepy than me15:56
*** edmondsw has quit IRC15:56
slaweqok, so Merry Christmass and Happy New Year15:56
slaweqnext meeting will be in 2018 :)15:56
slaweqreedip_: :D15:56
reedip_Happy New Year and Merry Christmas... We would be having Q3 soon so enjoy the holidays15:57
*** salv-orlando has quit IRC15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:57
openstackMeeting ended Tue Dec 19 15:57:32 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop01.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-12-19-15.01.html15:57
openstackMinutes (text): http://eavesdrop01.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-12-19-15.01.txt15:57
openstackLog:            http://eavesdrop01.openstack.org/meetings/neutron_qos/2017/neutron_qos.2017-12-19-15.01.log.html15:57
*** reedip_ has quit IRC15:58
*** ihrachys has joined #openstack-meeting15:59
*** jlibosva has joined #openstack-meeting16:00
ihrachys#startmeeting neutron_ci16:01
openstackMeeting started Tue Dec 19 16:01:21 2017 UTC and is due to finish in 60 minutes.  The chair is ihrachys. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: neutron_ci)"16:01
openstackThe meeting name has been set to 'neutron_ci'16:01
ihrachys#topic Actions from prev meeting16:01
*** openstack changes topic to "Actions from prev meeting (Meeting topic: neutron_ci)"16:01
ihrachys"jlibosva to post wishlist bugs for fullstack improvements (reuse db dump; reuse env per class)"16:01
jlibosvaI did a few minutes ago16:01
openstackLaunchpad bug 1739075 in neutron "fullstack: Improve test suite by creating environment per test class" [Wishlist,New]16:02
openstackLaunchpad bug 1739078 in neutron "fullstack: Use a pre-built database schema" [Wishlist,New]16:02
ihrachysjlibosva, is 'rfe' tagneeded?16:03
*** markstur has joined #openstack-meeting16:03
jlibosvaI did tag it as rfe since it's an enhancement and not a real bug16:03
ihrachyswe have Wishlist for that alredy16:03
jlibosvabut dunno :)16:03
ihrachys'rfe' would trigger drivers discussion16:03
jlibosvaok, I'll remove the rfe tags16:03
mlavalleand we want to avoid those guys16:04
ihrachysyeah they are the worst16:04
jlibosvaremoved :)16:04
ihrachysok thanks for the reports! moving on16:04
ihrachys"haleyb to post patch disabling east-west tests"16:04
haleybhttps://review.openstack.org/#/c/527992/ merged16:05
haleybthere is another change that seems related16:05
ihrachysis it the reason why dvr flavor failed on setup?16:06
haleybyes it could be, i just noticed this morning so haven't looked closely16:06
ihrachysI think it is. I saw dvr job failing after ~20mins of setup without triggering tempest16:07
ihrachyssince the patch passes dvr job it should be ok16:07
ihrachysI +2d, thanks for the link16:07
haleybfrickler: ^^ ?16:07
*** markstur has quit IRC16:08
frickleryes, that was the latest reason I saw for dvr failure16:08
ihrachysthanks frickler !16:08
ihrachys#topic Tempest plugin16:08
*** openstack changes topic to "Tempest plugin (Meeting topic: neutron_ci)"16:08
*** apetrich has joined #openstack-meeting16:08
ihrachysthere is still some cleanup work to do16:09
ihrachysthough I saw Chandan posted a governance patch marking it as completed here: https://review.openstack.org/#/c/524605/216:09
*** markstur has joined #openstack-meeting16:09
ihrachysI think we should first clean up than claim victory16:09
fricklerI have a question there related to stable branches16:10
fricklerthe jobs using tempest plugin are failing on stable branches for neutron-dynamic-routing16:10
frickleris the intention to use tests from neutron repo instead for that instead?16:11
ihrachysI don't think they are supposed to be used for any stable branches16:11
ihrachysyes, new repo = queens+16:11
fricklere.g. https://review.openstack.org/52899016:11
fricklerso I'd cancel these cherry-picks and do unmodified backports of the "original" legacy jobs?16:11
ihrachysyeah. for stable you just move legacy jobs as is, using in-tree tests16:12
ihrachysI remember Chandan said he will update subproject patches consuming new repo but I don't see updates except for midonet that is all red anyway: https://review.openstack.org/#/c/521342/16:14
ihrachyswhat we need to do with all subprojects is to switch to new paths and install plugin using devstack plugin that was merged in https://review.openstack.org/#/c/526044/16:16
ihrachysshould we ask project owners to take over those patches?16:16
mlavallethat's a good idea16:17
ihrachyswe have midonet, vpnaas and dynamic-routing that are stadium projects16:17
ihrachysit looks like frickler drives d-r16:17
mlavallewith midonet, yamamoto can help16:17
mlavallewith dynamic-routing garyk can help16:18
ihrachyswho's vpnaas point of contact16:18
ihrachysmlavalle, would you mind if I ask you to reach out to yamamoto and hoangcx about those two patches? https://review.openstack.org/#/c/521341/ and https://review.openstack.org/#/c/521342/16:19
fricklermlavalle: do you need help with https://review.openstack.org/522931? master is working, so I think having this new patch for stable/pike seems the right approach16:19
mlavallenot a problem16:19
*** ricolin has quit IRC16:19
*** guhcampos has quit IRC16:19
ihrachysfrickler, I believe that's another topic we should discuss now. mlavalle had master patch doing the same that we may want to move forward first.16:19
ihrachysthis: https://review.openstack.org/#/c/525345/16:20
mlavalleonce that merges, I'll take care of the cherrypicks16:20
*** brault has quit IRC16:20
mlavallehttps://review.openstack.org/522931 should be abandoned16:21
fricklerah, I hadn't seen that one, o.k.16:21
ihrachysmlavalle, do you have a patch ready that rips of duplicate jobs from gate?16:21
*** brault has joined #openstack-meeting16:21
mlavalleihrachys: no, I will do that next16:22
ihrachysI think we should prioritize it right now because x2 number of jobs => unstable gate16:22
ihrachysok cool16:22
ihrachys#action mlavalle to send patch(es) removing duplicate jobs from neutron gate16:22
fricklerif you ping me once they are ready, I can push them on the infra side16:22
ihrachysyou already have https://review.openstack.org/#/c/516724/ for -api so maybe makes sense to reuse it16:22
mlavallefrickler: thanks. will do16:23
mlavalleihrachys: yes, I will expand that16:23
ihrachysok cool16:23
*** ruijie has quit IRC16:24
ihrachysand also once we migrate subprojects to new imports we should be able to kill tempest remainings in neutron tree (the base class etc.)16:24
ihrachysseems like that's all there is for migration16:24
fricklera bit related: the neutron-api test on devstack-gate currently is doing nothing because the tests it tries to run are removed from neutron repo16:24
fricklerthis is to use the plugin job instead: https://review.openstack.org/52900016:24
*** salv-orlando has joined #openstack-meeting16:25
ihrachysfrickler, yeah good catch16:25
*** brault_ has joined #openstack-meeting16:25
*** brault has quit IRC16:26
*** andreas_s has quit IRC16:26
ihrachysfrickler, gerrit suggests it needs a respin16:26
*** jamesmcarthur has quit IRC16:26
ihrachysnot sure if that's correct though16:26
*** andreas_s has joined #openstack-meeting16:26
*** jamesmcarthur has joined #openstack-meeting16:27
ihrachysok now let's move from migration issues to looking at new patches for the plugin16:27
*** chandankumar has joined #openstack-meeting16:27
chandankumarihrachys: hello16:27
fricklerihrachys: yes, I'll rebase16:27
ihrachyschandankumar, heya, we were discussing remaining migration bits for new tempest plugin for neutron. we decided that subproject owners will take over patches you have for vpnaas, midonet, and dynamic-routing16:28
chandankumarihrachys: sure16:28
chandankumarihrachys: but i have one questions16:28
chandankumarother neutron dependent projects have also their intree tempest plugins are they also moving to new repo or merging in the same neutron tempest plugin?16:29
ihrachyseach repo may have its own plugin, it's ok16:30
ihrachysbut for stadium projects, we may consider adopting their tests too16:30
ihrachysmlavalle, what do you think?16:30
chandankumarthen it will be so many plugins repo again16:30
chandankumarihrachys: i was thinking to merge all in the neutron tempest plugin16:30
chandankumarone tempest plugin to rule them all16:31
mlavalleyeah, I also thin we can adopt their tests16:31
*** janki has quit IRC16:31
mlavallebcafarel has been asking about that16:31
chandankumarihrachys: for telemetry projects i have merged aodh, ceilometer, panko in one project telemetry-tempest-plugin16:31
*** jamesmcarthur has quit IRC16:31
ihrachysI think it's a matter of will and effort. from my perspective it makes sense that stadium extensions are part of neutron api and hence covered by unified plugin.16:32
ihrachysbut it's probably a question for drivers16:32
ihrachysbecause it involves definition of neutron api and stadium structure etc.16:33
mlavallewe can discuss in the next drivers meeting16:33
*** Guest78202 has quit IRC16:33
chandankumarihrachys: l2gw tests are moved to a new repo tempest plugin as it does not comes under neutron deliverables16:33
ihrachys#action mlavalle to report back about result of drivers discussion on unified tempest plugin for all stadium projects16:34
ihrachyschandankumar, yes, anything not in stadium is out of discussion :)16:34
mlavallel2gw won't re-join the stadium16:34
mlavalleI had a conversation about it in Sydney16:35
ihrachysok back to plugin patches...16:35
ihrachyslet's look at the patch adding dns test: https://review.openstack.org/#/c/520233/16:35
chandankumarhttps://review.openstack.org/#/c/510525/ was a patch to move l2gw under stadium but it got abandoned16:36
ihrachysI had a concern there about us importing code from designate plugin here: https://review.openstack.org/#/c/520233/11/neutron_tempest_plugin/scenario/test_dns_integration.py@3616:36
ihrachysthis is needed to get access to all the helpers that inspect dns zones16:36
ihrachysI suggested to maybe keep the test inside designate plugin but frickler replied that the functionality under test is in neutron repo16:37
ihrachysso I guess we are good to go with it? of course assuming that designate tempest plugin changes will be gated against the job right?16:37
mlavalleI am good with it16:37
fricklerthere's a patch up for that already: https://review.openstack.org/52295016:37
ihrachysfrickler, it's not voting. is it going to change? or you think it's not a risk?16:38
fricklerihrachys: well, it is not voting yet on the neutron side either16:38
ihrachysah right16:39
ihrachysso it will inherit once we flip in neutron?16:39
fricklerbut I'd envision changing both, once it proves stable, yes16:39
mlavallewe talked about that a few weeks ago, didn't we?16:40
*** andreas_s has quit IRC16:40
ihrachysok. one risk is that currently designate job is not in neutron gate at all. so we may break the dns driver and in result block your gate and plugin gate16:40
ihrachysmlavalle, we haven't discussed the tempest cross-import details16:40
*** jamesmcarthur has joined #openstack-meeting16:41
haleybwe will also need a dashboard update right?16:41
ihrachyshaleyb, yeah true16:41
ihrachys#action frickler to post patch updating neutron grafana board to include designate scenario job16:41
frickleryes, I can do that16:42
*** gyee has joined #openstack-meeting16:42
ihrachysanyway, as for the test itself, I think it's ok to land. we can revisit voting later.16:42
ihrachysok other patches in the queue just need reviewer love but seem innocent to skip them16:43
ihrachys#topic Grafana16:43
*** openstack changes topic to "Grafana (Meeting topic: neutron_ci)"16:43
ihrachyswe have dvr-scenario at 100% but it should resolve with brian's and frickler's patches16:44
*** annp has quit IRC16:44
ihrachysI am eager to see result after both land16:44
ihrachysbesides that, there is linuxbridge scenario and fullstack16:45
jlibosvaI saw another failure in dvr-scenario related to trunk16:45
jlibosvaI think it might be a race between ovs firewall and trunk handler. I need to investigate further16:45
ihrachysjlibosva, how did you see it if it's supposedly broken? do you have a link to a bug?16:45
* mlavalle stepping away from keyboard for a few minutes16:45
ihrachysI guess it's not 100% failure because of devstack-gate issue16:46
jlibosvaI saw it here http://logs.openstack.org/92/527992/2/check/neutron-tempest-plugin-dvr-multinode-scenario/166eee3/logs/testr_results.html.gz16:46
ihrachyssame test fails in slightly different but similar way for linuxbridge too: http://logs.openstack.org/88/526488/5/check/neutron-tempest-plugin-scenario-linuxbridge/66f8835/logs/testr_results.html.gz16:47
frickleryes, I saw that a couple of times, too. maybe also mark that one as unstable?16:47
*** marios has quit IRC16:47
jlibosvathe dvr one fails with SSH failure probably because of an issue in trunk plugging16:47
ihrachyswe first need to make sure there is a bug report for the failure16:47
ihrachysthere is https://bugs.launchpad.net/neutron/+bug/1722644 for dvr job16:48
openstackLaunchpad bug 1722644 in neutron "TrunkTest fails for OVS/DVR scenario job" [High,Confirmed]16:48
ihrachysthough the error message is different there16:48
ihrachysI haven't seen that one for a while16:48
ihrachysso we probably should close it and create a new one16:48
jlibosvathis is my suspected culprit http://logs.openstack.org/92/527992/2/check/neutron-tempest-plugin-dvr-multinode-scenario/166eee3/logs/subnode-2/screen-q-agt.txt.gz#_Dec_14_18_31_25_80143216:48
jlibosvaI'll do that16:49
ihrachys#action jlibosva to close bug 1722644 and open a new one for trunk connectivity failures in dvr and linuxbridge scenario jobs16:49
openstackbug 1722644 in neutron "TrunkTest fails for OVS/DVR scenario job" [High,Confirmed] https://launchpad.net/bugs/172264416:49
ihrachysjlibosva, thanks!16:49
ihrachysjlibosva, this seems ovs specific, so maybe two bugs for dvr and linuxbridge respectively16:50
jlibosvaI see16:50
ihrachysjlibosva, you will post a disabling patch right?16:51
ihrachys#action jlibosva to disable trunk scenario connectivity tests16:52
* mlavalle back16:53
ihrachysanother failure in linuxbridge is test_ip_prefix_negative here: http://logs.openstack.org/88/526488/5/check/neutron-tempest-plugin-scenario-linuxbridge/66f8835/logs/testr_results.html.gz16:53
ihrachysI don't think we have a bug for that reported either16:53
*** andreas_s has joined #openstack-meeting16:53
slaweqI think that my patch: https://review.openstack.org/#/c/527965/ fixes this one16:53
openstackLaunchpad bug 1736674 in neutron "sg rules are sometimes not applied" [High,In progress] - Assigned to Slawek Kaplonski (slaweq)16:54
slaweqfrickler: thx, I just wanted to post link to it :)16:54
ihrachysok let's review it then :)16:55
ihrachysI see linuxbridge is green for this patch, good ;)16:55
ihrachys#topic Fullstack16:55
*** openstack changes topic to "Fullstack (Meeting topic: neutron_ci)"16:55
ihrachyswe have little time so let's review it quick16:55
ihrachysfullstack job is same 80% as it was for a while16:55
ihrachysexample: http://logs.openstack.org/65/527965/4/check/legacy-neutron-dsvm-fullstack/12b03b9/logs/testr_results.html.gz16:55
slaweqrecently I found new issue on fullstack: https://bugs.launchpad.net/neutron/+bug/173789216:56
openstackLaunchpad bug 1737892 in neutron "Fullstack test test_qos.TestBwLimitQoSOvs.test_bw_limit_qos_port_removed failing many times" [High,Confirmed]16:56
slaweqbut I haven't got time to check it yet16:56
*** sridharg has quit IRC16:56
ihrachysnot enough details to suggest anything there yet. I assume agent log is clean?16:57
slaweqto be honest I didn't check it yet16:57
slaweqI just reported issue on launchpad16:57
slaweqbut I will try to debug it ASAP if anyone else will not take it :)16:58
ihrachysI bet no one will16:58
slaweqyes, so I will try to debug it :)16:59
ihrachysok there is little time, but I will take it on myself to report the security group failure16:59
slaweqit's qos and fullstack so it's what I like most :D16:59
ihrachys#action ihrachys to report sec group fullstack failure16:59
mlavalleno meeting next week?16:59
slaweqihrachys: You can add action for me that I will check this issue with qos and fullstack16:59
ihrachysslaweq, your desires are unconventional ;)16:59
ihrachysmlavalle, yeah absolutely17:00
mlavallemeaning no meeting?17:00
ihrachys#action slaweq to debug qos fullstack failure https://bugs.launchpad.net/neutron/+bug/173789217:00
openstackLaunchpad bug 1737892 in neutron "Fullstack test test_qos.TestBwLimitQoSOvs.test_bw_limit_qos_port_removed failing many times" [High,Confirmed] - Assigned to Slawek Kaplonski (slaweq)17:00
ihrachysmlavalle, sure. we will have shutdown as expected17:00
ihrachysnext time Jan 2 right?\17:01
ihrachysI will send an email, I hope 1/2 is fine with most17:01
*** salv-orlando has quit IRC17:01
ihrachyswe are out of time, thanks everyone for all the hard work!17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:01
openstackMeeting ended Tue Dec 19 17:01:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop01.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-12-19-16.01.html17:01
openstackMinutes (text): http://eavesdrop01.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-12-19-16.01.txt17:01
openstackLog:            http://eavesdrop01.openstack.org/meetings/neutron_ci/2017/neutron_ci.2017-12-19-16.01.log.html17:01
*** salv-orl_ has joined #openstack-meeting17:01
*** walshh has joined #openstack-meeting17:02
*** jlibosva has left #openstack-meeting17:02
*** andreas_s has quit IRC17:03
*** iyamahat_ has quit IRC17:04
*** walshh has quit IRC17:07
*** slaweq has quit IRC17:08
*** anilvenkata has quit IRC17:19
*** andreas_s has joined #openstack-meeting17:26
*** gagehugo has joined #openstack-meeting17:26
*** Swanson has quit IRC17:27
*** Swanson has joined #openstack-meeting17:27
*** tlam_ has joined #openstack-meeting17:34
*** jamesmcarthur has quit IRC17:34
*** jamesmcarthur has joined #openstack-meeting17:35
*** ruan__he has joined #openstack-meeting17:36
*** brault_ has quit IRC17:38
*** brault has joined #openstack-meeting17:38
*** jamesmcarthur has quit IRC17:39
*** edmondsw has joined #openstack-meeting17:40
*** brault has quit IRC17:43
*** andreas_s has quit IRC17:43
*** Apoorva has joined #openstack-meeting17:43
*** Apoorva has quit IRC17:43
*** Apoorva has joined #openstack-meeting17:44
*** ekcs has joined #openstack-meeting17:44
*** ekcs has quit IRC17:44
*** edmondsw has quit IRC17:44
*** andreas_s has joined #openstack-meeting17:48
*** davidalles has joined #openstack-meeting17:52
*** hagridaaron has joined #openstack-meeting17:54
*** ekcs has joined #openstack-meeting17:55
*** davidalles_ has joined #openstack-meeting17:57
lbragstad#startmeeting keystone18:00
openstackMeeting started Tue Dec 19 18:00:02 2017 UTC and is due to finish in 60 minutes.  The chair is lbragstad. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
lbragstad#link https://etherpad.openstack.org/p/keystone-weekly-meeting18:00
lbragstadagenda ^18:00
lbragstadping ayoung, breton, cmurphy, dstanek, edmondsw, gagehugo, henrynash, hrybacki, knikolla, lamt, lbragstad, lwanderley, kmalloc, rderose, rodrigods, samueldmq, spilla, aselius, dpar, jdennis, ruan_he18:00
lbragstaddavidalles: ^18:00
lbragstadwe have all sorts of stuff to talk about today18:00
lbragstadjust a quick couple of announcements, gagehugo is gonna give a quick vmt update, then we'll get into the specs18:01
lbragstadwe'll give folks a couple minutes to join18:01
*** andreas_s has quit IRC18:02
lbragstadalright - let's get started18:03
lbragstad#topic announcements: feature proposal freeze18:03
*** openstack changes topic to "announcements: feature proposal freeze (Meeting topic: keystone)"18:03
lbragstad#info Feature proposal freeze for Queens is this week18:03
*** sambetts is now known as sambetts|afk18:03
lbragstadfor what we've accepted for this release, i don't think anything is in jeopardy18:03
lbragstadunified limits, application credents, project tags, and system scope all have implementations that are up and ready for review18:04
lbragstadwhich means we will have a busy milestone for reviews, but glad to see things proposed18:04
lbragstadin addition to that18:04
lbragstad#info All targeted/expected specifications have merged18:04
hrybackigood job to all the folks doing hard work to make that happen18:04
lbragstadso - as far as what we discussed at the PTG and the Forum/Summit, we're consistent in our roadmap and our specification repository18:05
lbragstadwhich is a really good thing18:05
lbragstadespecially now that unified limits merged18:05
lbragstad#link https://review.openstack.org/#/c/455709/18:05
lbragstadthanks cmurphy kmalloc wxy for pushing that through and capturing the details we got from sdake18:06
lbragstad(sorry sdake!)18:06
sdakelbragstad it happens18:06
sdake(all the time:)18:06
lbragstadtons of things are up for review for those looking to review some code18:07
lbragstadnew features too that need to be played with18:07
*** jdennis has joined #openstack-meeting18:08
lbragstadand without a doubt, some client stuff that still needs to be done based on the new feature work18:08
lbragstad(unified limits, application credentials, for sure)18:08
lbragstadthere are no shortages of work, that's for sure :)18:08
lbragstadthanks again to folks for shaping up the release, things are looking good18:09
lbragstad#topic VMT coverage18:09
*** openstack changes topic to "VMT coverage (Meeting topic: keystone)"18:09
lbragstadgagehugo: o/18:09
gagehugoso fungi and lhinds have looked over the vmt doc for keystonemiddleware and documented their findings here18:10
gagehugo#link https://etherpad.openstack.org/p/keystonemiddleware-ta18:10
gagehugoso now I think the idea is that the keystone team and them meet to finalize it18:10
lbragstadsounds like we need to review their findings18:11
*** spilla has joined #openstack-meeting18:11
gagehugos/finalize/review and finalize/18:11
gagehugowe can setup a meeting after the holidays if that works18:11
lbragstadthat sounds good to me18:11
gagehugoalso there are drafts for keystoneauth and oslo.cache18:11
gagehugo#link https://review.openstack.org/#/q/topic:keystone-vmt18:12
kmallocgagehugo: thanks! I appreciate you working so hard on this18:12
gagehugokmalloc :) anytime18:12
gagehugoit's been an interesting process18:12
gagehugothat's all I got for that update18:12
*** lhx_ has quit IRC18:12
lbragstadthanks gagehugo18:12
lbragstad#topic specification review and discussion18:13
*** openstack changes topic to "specification review and discussion (Meeting topic: keystone)"18:13
lbragstadhrybacki:  ruan__he davidalles_ o/18:13
lbragstad#link https://review.openstack.org/#/c/323499/18:13
davidalleshere we are18:13
davidallesEnterprise objective in telecom Cloud is to be able to Audit and Remediate the list of users and their roles on multiple openstack deployments inside one country via dedicated processed run outside from openstack IaaS18:13
davidallesAs a consequence we want to implement inside the IaaS regions the Identity and Access Management features so that local keystones are the source of truth on ‘per-openstack deployment’ basis18:13
kmallocmy -2 disappeared from a patch.18:14
kmallochold on i need to go chat w/ infra. brb18:14
lbragstadkmalloc:  doh!18:14
hrybackistill there kmalloc18:14
davidallescurrently what is missing is the proper way to synchronize the reference for projects18:14
davidalleson the various openstack deployments18:14
jdennisthis is essentially an attempt to federate diverse clouds runining different version of opentstack18:15
kmallocnvm - terrible gerrit UI, old patches don't show scores.18:15
*** harlowja has joined #openstack-meeting18:15
davidalles==>synchro is run from one external tool18:15
davidalleswhich will use the standard keystone APIs18:15
davidallesexcept for the keystone/createProject where we would like to 'force' the project's ID:18:15
davidallessame openstack ID on all deployment18:16
ruan__hewhen we talk about an external tool, it's a module which coordinates multiple Openstack18:16
* knikolla sorry for being late 18:16
ruan__heif we have this feature, the module will be able to create projects of  different openstack with the same id18:16
ruan__hethis is what we call "synchronization"18:17
jdennisshouldn't this be an upstream project to work out all the details of federated disjoint clouds?18:17
ruan__heit could be, I've presented this work to LOCC yet18:17
ruan__hebut, don't we need to do that step by step?18:18
lbragstaddavidalles: ruan__he when we talked, it sounded like you had some restrictions you had to adhere to?18:18
*** chyka has joined #openstack-meeting18:18
davidallesmy request on keystone team is to start step-by-step: allowing to synchronize the project’s ID across sites18:19
*** rmascena has joined #openstack-meeting18:19
davidalles(then we may open a refactoring for this external tool for IAM & ACM)18:19
kmalloci am against the standard APIs being used for that.18:19
kmallocthis should be a system-scoped/admin only option IMO18:19
ruan__hekmalloc, this feature existed before18:20
kmallocnot in v318:20
kmallocit has never existed in v318:20
davidallessounds before noone fully expressed a need to 'port it' to v3?18:20
davidallessounds no one fully..18:20
kmallocno, we explicitly decided that we didn't want it in v3, it was brought up18:21
kmallocand it was decided that v3 100% controlls all ids.18:21
davidallesah, it is different!18:21
ruan__hefor which raison you want 100% control?18:21
*** corey_ has joined #openstack-meeting18:21
kmallocfor a lot of reasons, mostly centering around the fact that we had issues with guaranteeing no conflicts for generated/derived resources18:22
kmallocaka, mapping ending for users.18:22
*** cleong has quit IRC18:22
*** raildo has quit IRC18:22
davidalles[I understand that Cern company also have the same request because the same requirement]: How do you identify one alternative approach18:23
kmallocit prevents malicious use / issues creating a project that could then generate for mapped users a known set of IDs from a different IDP or to surreptitiously own a domain/project prior to the IDP being linked18:23
davidallesto comply to the requirement?18:23
*** links has quit IRC18:23
ruan__heif it only option, it will not change the standard usage18:23
rmascenaI believe that the revocation events + role assignments controls should become way more difficult to deal with with we enable that change, so I believe that we should specify in that spec, how we are gonna deal with that kind of sync evens on that scenario18:23
kmallocso, if you want this, I am going to tell you it cannot be in the standard APIs.18:23
kmallocit must be done as a privileged (cloud admin/system scope)18:24
kmallocit means a cloud admin/system scope is needed to do this work, not a "domain admin"18:24
kmallocthe issue is around domain-admins who can create projects.18:24
lbragstadeven so - we should still think about the ramifications of the revocation argument18:24
kmallocand similar effects.18:24
*** corey_ is now known as cleong18:24
cmurphywhy does this need to be part of the API instead of synchronizing the project table?18:24
davidallesAgreed: let's enforce this via 'system scoping' only because this is a Cloud Service Provider privilege18:25
jdenniscmurphy: because the are entirely different clouds18:25
knikollawhy not use k2k with a mapping which guarantees project -> project mappings.18:25
hrybacki^^ does everyone understand this is their use case?18:25
kmallocnow. that said, the best option is to navigate allowing an external authority on project IDs similar to federated auth, that can be sync'd.18:25
kmallocbut that is new tech.18:25
davidalles... I understand that K2K is a synchro on Authentication, not authz18:25
kmallocand i don't know how that works.18:26
hrybackidavidalles: ruan__he can you explain (high level) your project and how it differs from the way the cores are used to working with OpenStack?18:26
kmallock2k is basically SAML2 between keystones.18:26
ruan__heok, we set up a upper layer to coordinate multiple independant openstack18:26
kmallocit is AuthN with AuthZ still being based upon the SP side of the handshake (RBAC)18:26
davidallesI understand that standard usage of openstack deployments are independent cloud and customers are consuming various clouds in 'hybrid way' (from one or multiple CSP)18:27
ruan__headmin manipulate directly on the upper layer, and the upper layer in charge of send requests to each openstack18:27
lbragstadbut it's expected to be able to use the same token between each cloud?18:27
lbragstadso it's more like different regions in a single deployment, right?18:28
hrybackilbragstad: yes, that is what they are going for. I don't know of anyone else that has tried this18:28
kmallocthings we also need to explicitly cover: what happens if cloudX has the same ID already as CloudY for a project. -- this is something we can't really fix (nor should we) but it is a major security concern [in your upper layer]18:28
hrybackisingle openstack per region18:28
hrybackibeing synced/controlled by an 'over the top layer' of custom software18:28
kmallocif you're using the same token across different clouds, i am a hard -2 on all this.18:28
kmallocwe're not adding that support upstream in keystone.18:28
davidallesHere for Telco cloud with multiple sites, the CSP is responsible for the creation of the customer accounts (projects on all sites, allocating the users and configuring their permissions)18:28
*** AJaeger has joined #openstack-meeting18:29
knikollawith k2k you can trivially get a token for the other side.18:29
kmallocit is just way way way too much exposure.18:29
ruan__heas a security expert, the same project with different project ID in each openstack is a security concern !18:29
kmallock2k is explicitly setup and you're getting a token issued by the otherside.18:29
kmallocso revocations/project checks/etc are all managed on the SP side.18:29
davidallesand because the CSP is the Telco operator it is forced to comply to local regulation with hard IAM process and strong Audit & Compliance management18:30
hrybackikmalloc lbragstad -- how do we handle very large consumers of OpenStack that want to push bounds? I think the 'opt in' approach here makes this a 'enter at your own risk' Perhaps there is a process around 'experimental' features?18:30
lbragstadwe used to mark APIs as experimental, but we haven't done that in a while18:31
lbragstadwe also don't do extensions18:31
kmallochrybacki: simply put, I'm going to say if you want to use the same token on multiple clouds, you're doing a ton of synchornization already, all IDs must be in sync, so my stance is I am not conceding any thing besides project IDs via system scope18:31
davidalles'experimental' for CSP usage at 'system scoping' would be a very nice balance for use: and our openstack editor will support this with/out support exception.18:31
*** bobh has quit IRC18:32
davidallesbut on my side I am not requesting to synchronize all the IDs on all the resources18:32
ruan__hekmalloc, we have tested K2K, it has a performance issue for our requirement18:32
lbragstadis it possible to get bugs opened for those performance issues?18:32
kmallocyou're probably moving into realms where you're solving how to sync the backends for keystone behind the scenes. i don't want every resource to have the "submit an API request with an ID to make a special resource"18:32
davidallesreminder: only need to be able to control the assignment on 'per-keystone deployement'18:32
kmallocruan__he: how about proper SSO [OIDC] or SAML to the individual keystone's18:33
kmallocrather than "just take a token issued by keystone A to keystone B18:33
knikollaruan__he: only when you get a token, you can reuse it for the lifetime of it with zero impact on performance18:33
lbragstaddavidalles: that can be done with roles assignments on shadow-users, right?18:33
knikollakmalloc: i agree, this sounds like a federation scenario18:33
jdennisI am really concerned about all the other id's, this just feels like an opportunity for difficult to debug synchronization issues.18:33
davidallesall the other resources (and their IDs) are in the 'project scoping'18:34
kmallocjdennis: i think this is something that needs to be built into the backend in the write phase, a driver. not on top of the APIs.18:34
davidallesthen no request on them18:34
lbragstaddavidalles: ruan__he is it possible to see what happened with your performance findings?18:34
lbragstadif there are things that aren't performant from a federation perspective upstream, we should fix those18:35
ruan__heif we make this feature as an option, we can show you later how we achieve this federation18:35
lbragstadit sounded like you tried k2k already but hit performance road blocks?18:36
ruan__helbragstad, we worked on k2k 2 years before, and then we decided to go to another approach18:36
lbragstadwere the issues that drove you to another approach performance related?18:36
jdennisbut you're asking to expose an API that may have significant issues, what do we do when the API is present and the problems are found?18:36
ruan__heanother important point is that, it's not only about the federation of 2-3 openstack, but about maybe more than 10!18:37
davidallesThis requirement is on the shoulders of the CSP, to comply to regulations and hard OPS process18:38
kmallocjdennis: i really feel like this whole thing needs to be a driver.18:38
davidallesand exactly we are dealin,g with tenS of telco datacenters18:38
kmallocjdennis: so it can coordinate centrally and provide acks/etc.18:38
*** aselius has joined #openstack-meeting18:38
kmallocrather than a soft "we'll try and do it via public APIs"18:38
lbragstaddavidalles: who is the CSP in this case? just so everyone can level set on terms18:39
*** andreas_s has joined #openstack-meeting18:39
lbragstadruan__he:  if we're federating 10 different deployments and it trips up because performance is bad, then we should try to fix those performance issues18:39
davidallesThe CSP is the Telco itself: both IaaS provider18:39
ruan__hekmalloc, maybe a driver will be a good choice, but at least we should start by making it as an option?18:40
*** iyamahat has joined #openstack-meeting18:40
davidallesof the multiple Telco DC and the customer who deploys the workloads18:40
kmallocthe benefit is a driver can be developed out of tree you can build in all the logic to cooridnate the project-id sync.18:40
kmallocand if you're liking it, we can consider it for in-tree.18:40
kmallocor it could be on a feature branch18:40
ruan__hewe can contribute to this feature firstly, and in charge of developping a driver later18:41
* lbragstad thinks that could lead to interop issues18:41
kmallocso, let me be really clear, a "new API" is a big hurgle18:41
kmallocwe cannot ever remove an API18:42
davidallesto ALL: is a driver-logic acceptable when you accessed that 'V3 must control the generation of IDs;  driver is installed by the CSP18:42
davidalles... the 'system scoping' in other way18:42
ruan__heit's not a new API, but an option for a existing API18:42
*** tlam_ has quit IRC18:42
kmallocthe driver is below the API, so - the "make a project" generates an ID in the manager/controller layer18:42
hrybackikmalloc: are modifications to an existing api considered a new api?18:42
jdennisno new API's, especially one that could be problematic18:42
*** tlam_ has joined #openstack-meeting18:43
kmallocruan__he: it is NOT an option for an existing API18:43
kmallochrybacki: i'm going to -2 changes to the project_api for specifying the ID.18:43
*** ekcs has quit IRC18:43
kmallocthis really needs to be a system-scope thing if we're doing it.18:43
*** andreas_s has quit IRC18:43
kmalloci'm willing to be open to that.18:43
kmallocjust not a modification of the current project_api.18:44
hrybackilet's help ruan__he and davidalles develop a plan that is congruent with the core's thoughts18:44
davidallesdriver could be acceptable: but could this be done as experiental in Queen?18:44
*** unicell has joined #openstack-meeting18:44
davidallesbecause RedHat company is out distro editor and they are working on 'per Long Term Support' basis: Queen then 'T' version18:45
kmallocdavidalles: it is something that would be best on a feature branch of out of tree as expirimental- we've largely moved away from in-tree expirimental (though lbragstad could say I'm wrong and we can do that again, i'd be ok iwth it)18:45
*** chyka has quit IRC18:45
kmallocso in driver logic, as a quick rundown of how it would work:18:45
kmallocAPI request to make new project is received. the id is generated at the manager/controller layer18:45
*** hagridaaron has quit IRC18:46
kmallocthe driver would check/sync the project ID to the participating clouds (with ACKs) -- this is not via public APIs though another mechanism to guarantee uniquness and acks / cloud was down and needs to get created ids after it comes back up cases18:46
kmallocdriver would then store the project id locally.18:46
*** cleong has quit IRC18:47
lbragstadso - we developed k2k specifically for this18:47
kmallocyou need to handle the sync logic, and the "catchup from downtime" logic in the external service / keystone-comes-back-on-line.18:47
jdenniskmalloc: acks being "yes, I can accept this id"?18:47
kmallocjdennis: correct. or "I accepted and stored locally"18:47
lbragstadif there are performance issues with k2k, then it'd be good to see what those are and go fix those18:47
kmalloclbragstad: ++18:47
knikollalbragstad: ++18:47
kmallocjdennis: probably a combination of "i can and did accept"18:48
lbragstadbecause that means there are still issues in that implementation and it's not useable for what we designed it for18:48
kmallocand I 100% get the desire for the same project_ids across deployments18:48
kmalloci think that is a fine thing to strive towards, i worry about public apis to do the sync18:48
*** cdub has quit IRC18:48
ruan__heI haven't understand how the driver can garrantee the same projecd ID?18:48
*** chyka_ has joined #openstack-meeting18:49
kmallocruan__he: the driver can modify the values stored. we only display the id in the response18:49
cmurphyat the manager layer it would have to query the other cloud to get the ID and then use that instead of generating its own18:49
*** chyka_ has quit IRC18:49
*** cleong has joined #openstack-meeting18:49
kmallocso you could even ask "hey external service, issue me a unique-uuid-that-is-not-conflicted" you can do that18:49
*** stevebaker has left #openstack-meeting18:49
*** chyka_ has joined #openstack-meeting18:50
*** cdub has joined #openstack-meeting18:50
ruan__heit seems to be a good temporal solution in short term18:50
davidallesyep: seams possible: on site 'Y' or 'X', this request would result in 'the centralized ID generator knows the ID to be given because already allocate on site '1'18:50
kmallocyou're still dealing with something that is sync'd between sites, but if it is just a store of IDs you can do high-performance lookup table18:51
*** ekcs has joined #openstack-meeting18:51
*** hagridaaron has joined #openstack-meeting18:51
kmallocand that should avoid the legal troubles of syncing the actual keystone data18:51
kmallocsince it's all random (cryptographically generated) IDs and nothing else.18:51
kmallocnow, that said, it would still be a requirement that the IDs are UUID-like in form, since other projects require that.18:52
kmalloc(e.g. nova)18:52
*** brault has joined #openstack-meeting18:52
kmalloci am very very concerned with changing the APIs and/or adding a new API.18:53
*** brault has quit IRC18:53
lbragstadis it possible to get the performance metrics where k2k starts to become unusable?18:53
knikollaalso look into https://github.com/openstack/mixmatch18:53
kmallocbut i would like to also fix k2k18:53
knikollaif you decide to go k2k18:53
kmallocif there are real performance issues.18:53
kmallocit seems like this is exactly what k2k is meant to fix.18:53
*** rajulk has quit IRC18:53
ruan__hebut if the modification of api doesn't impact others, I don't think that it will be an issue18:53
knikollait's a k2k proxy with caching.18:53
*** brault has joined #openstack-meeting18:54
hrybackiI would still like to hear a ack/nack on the idea of running this as an experimental feature (for record)18:54
lbragstadthat's my concern... we built something to solve this already, but we're going to try and solve it again by changing our API18:54
kmallocruan__he: you're missing the point. APIs are not allowed to be "config based behavior" in keystone.18:54
*** chyka_ has quit IRC18:54
kmallocso, once we land a change it's forever18:54
kmallocand we need to support it18:54
knikollaand we pledged to never remove v3.18:54
kmallocwe already built things for this, if they aren't working for perf reasons, i want to fix that18:54
ruan__hekmalloc, i get the point, that's why I called it an option18:55
kmallocif they don't work for functional reasons.18:55
kmallocthen i want to supply more functional support, but adding/changing APIs is a large hurdle if it could be done behind the scenes cleanly and not impacting interop/security of the APIs (user-facing UX)18:55
jdennisruan__he: there no such thing as an option, it's either in the API or not18:55
lbragstadthe concern for an optional solution is that it can changed across deployments (which is something we've been trying to not do openstack-wide)18:55
kmallocjdennis: ++18:55
lbragstadit just makes interoperability really hard for consumers moving between clouds18:56
kmalloci've -2'd a number of things that are "optional" proposed to keystone. Keystone should work 100% the same (API wise) across all deployments of that release.18:56
*** ekcs has quit IRC18:56
davidalles... OKi... because I am not a source code specialist: is this driver mechanism already available: can we use it inside the existing Queen code18:56
ruan__hekmalloc, but at the same time, we should improve keystone for new use cases18:57
davidalleswithout any source code modification ... ? or even on previous versions?18:57
kmallocdavidalles: you can load any driver via keystone's config18:57
kmallocyou could subclass the current one and write your logic over the top18:57
kmallocso supply a driver and say "load this driver"18:57
ruan__hekmalloc, the way we use openstack becomes much more wide then before18:58
cmurphythere is some minimal documentation here https://docs.openstack.org/keystone/latest/contributor/developing-drivers.html18:58
lbragstad#link https://docs.openstack.org/keystone/latest/contributor/developing-drivers.html18:58
lbragstadbah - cmurphy beat me to it!18:58
davidallesunderstood: thanks.... Ruan, how to measure the work effort to develop the driver? staff*weeks and what's the level of knowledge to do it?18:58
lbragstadone minute remaining18:59
davidallesand how to share with out partner?18:59
lbragstadwe can move to -keystone to finish this up if needed18:59
hrybackiapologies for the lack of open discussion18:59
davidallesbrauld: are you there?18:59
lbragstadbut the infra folks we need the meeting room soon :)18:59
*** hagridaaron has quit IRC18:59
cmurphyi wrote an assignment driver myself, it only took a couple of days18:59
cmurphya resource driver would not take that much work18:59
kmallocdrivers are easy imo18:59
lbragstadlet's move to openstack-keystone18:59
hrybackithanks folks19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:00
openstackMeeting ended Tue Dec 19 19:00:00 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop01.openstack.org/meetings/keystone/2017/keystone.2017-12-19-18.00.html19:00
openstackMinutes (text): http://eavesdrop01.openstack.org/meetings/keystone/2017/keystone.2017-12-19-18.00.txt19:00
openstackLog:            http://eavesdrop01.openstack.org/meetings/keystone/2017/keystone.2017-12-19-18.00.log.html19:00
davidallesOKi, so the conclusion it: BP is --219:00
davidallesexternal work at drver level:)19:00
clarkbanyone here for the infra meeting?19:00
AJaegeryes, you and me ;)19:00
fungiinfra things double-plus good19:00
AJaegerfungi: squared?19:00
ianwand me :)19:00
clarkb#startmeeting infra19:01
openstackMeeting started Tue Dec 19 19:01:20 2017 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
clarkb#topic Announcements19:01
*** openstack changes topic to "Announcements (Meeting topic: infra)"19:01
clarkbWe will be skipping next week's meeting on the 26th of December19:01
clarkbI won't be around and don't really expect anyone else to be around19:01
*** andreas_s has joined #openstack-meeting19:01
*** ruan__he has quit IRC19:02
clarkbRelated to that we should probably be very slushy next week in the changes we make as I expect there won't be many of us around for significant periods of time19:02
*** ruan_he has joined #openstack-meeting19:02
clarkb#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
clarkbfungi modified the jenkins votes in gerrit19:03
jeblairthere is no jenkins, only fungi19:03
fungii did indeed. spammed the whole community. it was glorious19:03
clarkband at least one person asked about it so it didn't go compeltely unnoticed19:04
fungii got plenty of comments through various channels19:04
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2017/infra.2017-12-12-19.01.txt Minutes from last meeting19:04
clarkbthat was the only action item from last time19:04
clarkb#topic Specs approval19:04
*** openstack changes topic to "Specs approval (Meeting topic: infra)"19:04
*** spilla has left #openstack-meeting19:05
clarkbWe don't have any current specs up for approval, but thank you to everyon that read and reviewed the top level project hosting spec, that spec is now in and currently being worked on19:05
jeblairthere's still a work item up for grabs19:05
jeblairtalk to me if you want to help19:05
fungigit servers, right?19:05
*** hagridaaron has joined #openstack-meeting19:06
clarkb#info talk to jeblair if you want to help with work items on the top level project hosting spec19:06
clarkbalso everyone should feel free to review the changes that go up fro that :)19:06
clarkb#topic Priority Efforts19:06
*** openstack changes topic to "Priority Efforts (Meeting topic: infra)"19:06
clarkb#topic Zuul v319:07
*** openstack changes topic to "Zuul v3 (Meeting topic: infra)"19:07
clarkbThere are one and a half zuul v3 topic that are on the agenda. The first is closing down the zuulv3 issues etherpad and moving more towards typical bug tracking19:07
clarkbconsidering that we are no longer in firefighting mode I am in favor of this19:07
mordredalso - thank god for not being in firefighting mode19:08
* fungi hangs up asbestos suit19:08
jeblairwe should probably ask folks to file general job problems against their best guess as to the jobs repo involved -- openstack-zuul-jobs, zuul-jobs, project-config19:08
clarkbjeblair: ++19:08
jeblairplease don't file "my job doesn't work" against zuul itself :)19:08
fungi... individual project repo19:09
AJaegerwe still have some backlog for Zuulv3 - like the docs jobs that mordred has been working on...19:09
AJaegerbut those are smallish fires ;)19:09
ianwin storyboard or launchpad?19:09
clarkbbut ya if we can all take ~15 minutes to migrate the items we are familiar with I expect that will go quickly19:09
fungiAJaeger: these are more fires related to other efforts which have involved zuul jobs, not zuul v3 imposed breakage, right?19:09
clarkbianw: the projects we care about are in storyboard so I think there19:09
ianwa few people have turned up an said "i have a bug not a story", so we might like to make that clear19:09
jeblaira bug is just a sad story19:10
fungii've also suggested in the past we might want a custom reporting view for the storyboard webclient which is a "bug/defect reporting" interface19:10
jeblairwe should replace the etherpad content with a big "report bugs here" thing19:10
clarkb#link https://etherpad.openstack.org/zuulv3-issues please take a moment to migrate the items you are familiar with on this etherpad to storyboard and try to be specific about using the correct repo (zuul-jobs, openstack-zuul-jobs, project-config, etc)19:10
fungithe current work in progress for custom reporting urls likely makes that a lot saner19:11
AJaegerfungi, we fix the problem that repos that need required-projects in docs publishing are failing to publish - so, that's a migration fallout19:11
*** ricolin has joined #openstack-meeting19:11
fungiAJaeger: oh, yep definitely19:11
*** davidalles has quit IRC19:11
fungii was thinking you meant teh pti-related docs job work19:11
*** davidalles_ has quit IRC19:11
*** iyamahat has quit IRC19:11
clarkbThe other half an issue is how many changes are required to create new projects. This is lsited under general topics but I think zuul v3 is the major reason for this so maybe we want to talk about it in this context instead19:12
AJaegerfungi: but mordred added some more goals into it as well - like the pti work. so, those are related.19:12
clarkbhrm no dmsimard here19:12
AJaegerfungi: solving the docs publishing is a side effect of the PTI work19:12
*** chyka has joined #openstack-meeting19:12
fungigot it19:12
clarkbbut basically you have to create the project in gerrit first, then in zuul, then add jobs to it19:13
clarkband that is because zuul needs to load the project from its source before it can do anything with it19:13
jeblairdid we merge mordred's fix to bring this back down to 2 changes?19:13
clarkb#link https://review.openstack.org/#/c/528375/ documents the process19:14
clarkbjeblair: I'm not aware of that change so I don't know19:14
clarkbis this the idea where we'd do zuul after gerrit in the ansible cron?19:14
jeblairAJaeger's change which you linked documents the 2 change process19:14
jeblairclarkb: yep19:14
fungisolving the need to split adding a project to zuul and adding jobs for the project (in project-config) isn't solvable without altering how zuul handles validating configuration changes right?19:15
*** andreas_s has quit IRC19:15
clarkbjeblair: ah ok, the meeting agenda item still said 319:15
jeblairand yes, that change merged19:15
mordredclarkb: I think we did19:15
jeblair#link 2 change process https://review.openstack.org/52874419:15
*** jamesmcarthur has joined #openstack-meeting19:15
AJaegerclarkb, jeblair : I think the topic was added *before* mordred did his change, so I consider this void and propose to move on19:16
jeblairfungi: yep.  if we consider that a problem, then it's a much different problem.19:16
clarkbI don't expect we'll be able to improve the number of changes much beyond that, are there other things we can do the make the process easier (documentation like AJaeger's change helps I'm sure)19:16
*** chyka has quit IRC19:17
jeblairwe probably *could* but they would be more than simple bugfixes19:17
fungiseems hairy and fraught with possible security implications19:17
AJaegerlet's merge my change for now - I had too many people just send on and think we need to be louder about it19:17
jeblairlike extending zuul to dynamically evaluate main.yaml (crazy!) or not adding projects to project-config and only doing in-repo config.19:17
clarkbAJaeger: ya I think we improved docs we can table this and see how it goes19:18
fungithe latter solution of the two seems more likely to be viable, and only loses us the ability to have an explicit system-required project-template19:18
fungi(which could probably be resolved somewhat safely by implementing support for implicit project-templates?)19:19
jeblairoh, there was a change for that... did it merge?19:19
clarkbimplicit project templates meaning every project gets system-required template regardless of any explicit config?19:19
*** jamesmcarthur has quit IRC19:20
clarkbalso new projects are an excellent place to start with in repo configs :)19:20
mordredclarkb: ++19:20
fungiif that's already a thing, then maybe we don't need a second project-config change for projects who want to define jobs in-repo19:20
jeblairyeah, tobiash had a change19:20
jeblairi'm having trouble finding it19:21
clarkb#link https://review.openstack.org/513368 implicit project-templates in zuul19:21
jeblairstill open but has a +2 from me19:21
fungiso... soon to become possibly simpler to add new projects19:22
clarkbcool, sounds like there is work in progress ( and some done) to make this whole project addition process easier19:22
clarkbany other zuulv3 related items?19:23
jeblairyeah, i think considering that generally the only thing we expect a new project to do in project-config is add system-required, if we drop that, we could get down to one change19:23
jeblairwith no loss in functionality19:23
jeblairor substantial change in polices19:23
mordredoh yeah - that change. I thought I'd reviewed that19:23
jeblairmordred: i think you expressed pleasure about it19:23
jeblairwhich is like a review19:24
clarkbnot hearing about other zuulv3 things so moving on19:25
clarkbI'm going to skip dmsimard's other topic in hopes that dmsimard joins us soon and talk about the control plane upgrades first19:25
clarkb#topic General Topics19:25
*** openstack changes topic to "General Topics (Meeting topic: infra)"19:25
clarkbas I mentioned in an email on friday I think we were reasonably successful with the control plane upgrade sprint19:26
fungii have a sort of zv3-related topic i didn't put on the agenda and was saving for open discussion19:26
*** tobiash has joined #openstack-meeting19:26
clarkbfungi: ok I expect we will have time at the end of the meeting19:26
fungithough it's sort of related to the upgrade sprint as well19:26
clarkboh well then maybe talk about it now ;)19:27
jeblairit is conveniently related to all agenda topics19:27
clarkbI did want to mention I thought jeblairs idea of each of us trying to knock out a service per week or so would be nice19:27
fungibasically we still have some v2-specific servers hanging out there and not only are they potentially wasting resources now but they're somewhat of a liability19:27
clarkbkeeps the momentum going and we don't ignore the problem until the next rush19:27
*** jamesmcarthur has joined #openstack-meeting19:27
pabelangerfungi: +119:28
clarkbfungi: at htis point it is just zuul.openstack.org and nodepool.openstack.org right?19:28
jeblairclarkb: cool... i should get started -- i haven't done one this week :)19:28
fungie.g., rackspace decided to do the reboot-based migration of zuul.o.o a day later than they told us, so it came up with the service running and commenting on changes for several days19:28
*** edmondsw has joined #openstack-meeting19:28
jeblairzuul.openstack.org has an http redirect, and nodepool.o.o is still our zookeeper server?19:28
pabelangerfor nodepool.o.o we need to decide how to migrate zookeeper into zk01.o.o/zk02.o.o/zk03.o.o19:28
*** iyamahat has joined #openstack-meeting19:28
pabelangerjeblair: yes19:28
clarkbjeblair: yes. I think for zuul.o.o we can just cname to zuulv3.openstack.org?19:28
ianwclarkb: openstackstatus/etherpad/ethercalc should all be ready-ish to go19:29
AJaegerclarkb: we should19:29
fungiwondering if we can safely remove the zuul.o.o a/aaaa records and replace with a cname to zuulv3.o.o for now19:29
fungiif so, that should allow us to drop the redirect/delete the old server?19:29
pabelangerreplacement zookeeper is up and running, we just need to confirm it works as expected (plus migrate)19:29
jeblairfungi: can we add a vhost on zuulv3.o.o to keep the redirect rule?19:29
fungijeblair: ahh, good point, or a catch-all redirect on the zuulv3 vhost19:29
*** awaugama has quit IRC19:29
fungiassuming zuulv3.o.o is the default vhost though, it may "just work" anyway?19:30
jeblairand then, when we redeploy on zuul.o.o, which we should do soon (maybe after the puppet-openstackci stuff lands?)  we can do the same in reverse.19:30
clarkb#agreed add vhost to zuulv3.o.o and redirect zuul.openstack.org to zuulv3.openstack.org then when we redeploy zuul.openstack.org we can do the same in reverse19:30
clarkbsomething like ^19:30
clarkbthat will allow us to delete existing zuul.openstack.org19:30
jeblairyeah -- whatever allows us to accomplish that :)19:31
fungii can safely test whether a redirect is needed or abusing the default vhost is sufficient19:31
fungiand then we can move formward with better information19:31
fungier, forward19:31
clarkbfor nodepool/zookeeper my reading of zk docs is that we can't easily do an online migration of data from existing single node cluster into new 3 node cluster19:31
jeblairpabelanger: did you find out if we can add zk* to the current nodepool.o.o zk system?19:31
jeblairoh :( ^19:31
clarkbwe can take a downtime stop old zk, copy all data to the other nodes then start zk on other nodes and point nodepool services to new cluster19:31
jeblairand zuul19:32
pabelangeryah, that's basically what I found too19:32
clarkbor we could take a downtime and just build new state on new cluster19:32
fungiso no expand/contract for migrating clusters i guess19:32
*** edmondsw has quit IRC19:32
clarkbfungi: not with the version we have aiui, the next version would allow it if you can ninja interactive management socket commands19:32
pabelangerclarkb: we'd need to build / upload images for that19:32
fungiwas it just that it's unsafe to have an even number of cluster members, or were there additional issues?19:32
tobiashhow long do image rebuilds and uploads take in openstack land?19:33
fungisounds like the challenge ran deeper. okay19:33
pabelangerwhich we could start now with images, if we move 1 builder to new zookeeper19:33
clarkbfungi: the way I understand it is the existing 3 node cluster has quorum and numbers, so will win out if we join the old node to it19:33
jeblairclarkb: what if we do one at a time?19:33
clarkbfungi: the way you work around that is with the management socket stuff where you say "these N nodes are from the other side of quorum"19:33
jeblairtobiash: it used to take a day?  but i think it got faster...19:33
fungitobiash: a few hours at this point i think, but i haven't looked in a while so don't have hard numbers19:34
clarkbjeblair: I couldn't find any docs that said that would work it was all either do the shutdown and start or do the newer management stuff19:34
tobiashso just rebuilding takes probably too ling19:34
pabelangeryah, we can do an image in 60mins build / upload with nb04 I think19:34
clarkbpabelanger: we could even move both builders, continue to just use old images on old side and then switch over19:34
pabelangernb03 is much longer due to network limits19:34
jeblairtobiash: yeah, long enough that if we did that, we'd want to start up a builder ahead of time like pabelanger suggested19:34
clarkbwe'd just want to do that in a shortish period of time19:34
fungiclarkb: and couldn't incrementally add the new cluster members to the "old" cluster of one?19:34
pabelangeryah, if we want to use old images for a day or so, we can do that19:35
mordredthe data isn't too huge, yeah? so a downtime to export/import data wouldn't be super long most likely?19:35
pabelangermight be a good test too19:35
clarkbfungi: I couldn't find any documentation on how to do that19:35
pabelangerof zookeeper19:35
clarkbmordred: correct its mostly about coordinating all the things I think19:35
fungiso zk basically has a predetermined cluster size you can't expand later i guess?19:35
mordredwe could schedule that for whenever our next gerrit project rename downtime might be19:35
clarkbfungi: ya that was the sense I got like you didn't want to add data until you had a quorum19:36
fungithanks, good to keep in mind for future scaling plans19:36
clarkbits also possible I just didn't find the relevant docs or they haven't been written :)19:36
fungii guess clustering with zk doesn't eliminate the need for forklift migrations19:37
clarkbmordred: or we just pcik a slow day and do it separately19:37
clarkb(to reduce things in flux)19:37
*** edmondsw has joined #openstack-meeting19:37
clarkbI know a lot of people are not around that first week of january but I will be here to do things like this if we want19:37
fungispeaking of upcoming outages, we still need to do the mysql charset migration for gerrit right?19:38
*** ricolin_ has joined #openstack-meeting19:38
clarkbfungi: yes19:38
clarkb(but its also getting close to feature freeze and release and all that)19:38
clarkbso anything we decide on we should run by the release team19:38
fungisimilarly, we need an outage to fix nova-specs19:38
fungiand of course pending project rename(s)19:39
AJaegerand there's a rename request for some months which needs an outage19:39
fungiwonder how many of these things we can safely roll together19:39
clarkbfor the project rename front we said last week? or was it week before last we just need to write down what the new process is in zuulv3 land19:39
clarkbI have not had time to look at that with the psrint and other stuff going on19:39
clarkbif someone else wants to do that the help is much appreciated :)19:40
fungimostly to do with order of operations merging changes?19:40
clarkbya basically keeping zuul happy as things move19:40
*** ricolin has quit IRC19:40
clarkb(remove project from zuul, stop gerrit, rename things, start gerrit, add back to zuul with new name or similar)19:40
*** openstack has joined #openstack-meeting19:41
*** ChanServ sets mode: +o openstack19:41
clarkbpabelanger: were you still planning on sorting out the zk stuff?19:42
fungietherpad-based maintenance plans have been effective in the past19:42
pabelangerclarkb: which stuff is that?19:42
clarkbpabelanger: deciding on which upgrade ethod we want to do and writing it down19:43
mordredfungi: we're going to need to figure out how to land the change to the project's zuul.yaml file to do the project rename there ...19:43
pabelangerclarkb: Oh, Yup. I can do that19:43
clarkb#action pabelanger write down zookeeper migration doc/plan19:43
mordredOR - get around to implementing the patch to remove the need for the name field in a project stanza in in-repo configs19:43
clarkbpabelanger: I think with that we can give release team accurate data on "this is the impact when can we move ahead"19:44
fungimordred: oh, yep, great point19:44
*** edmondsw has quit IRC19:44
mordredotherwise we're going to need to force-merge things19:44
pabelangerclarkb: agree19:44
mordredso maybe we should write the remove name patch19:44
jeblairmordred: ++ i think we can/should get that change in before 3.019:44
mordredsince we want it anyway19:44
fungimordred: maybe we'll get lucky this time and the project being renamed doesn't have any in-repo jobs yet19:44
fungibut that does make it more complicated if they do19:44
mordredfungi: well - unfortunatley, I have a repo rename ot add to the list - and it has in-repo jobs19:44
pabelangeroh yes19:45
clarkbmordred: do we want to say fixing that feature is a prereq for renames then write down the process with that in mind?19:45
pabelangerforgot about that19:45
AJaegermordred: so, remove in-repo jobs first, rename, readd? ;(19:45
*** gouthamr has quit IRC19:45
mordredoh. OH GOD - I just realized another issue ...19:45
AJaegeroh fun ;(19:45
clarkbmordred: I think you may be self nomimating yourself to write down this stuff :)19:45
fungior we configure zuul to ignore in-repo job configs from that project and have a no-op job phase for it until the in-repo configs are fixed19:45
AJaegerdo we need "aliases", to tell zuul about renames?19:45
clarkbbut ya there are enough corner cases that we should write down a plan and consider these issues19:45
fungiahh, yes any projects requiring that project are also a liability19:46
mordredfungi: I think required-projects entries are the larger issue19:46
fungimaybe this is the point at which we declare we will no longer support renaming git repositories? ;)19:46
mordredsincethose could be quite literally anywhere19:46
fungi(only half-joking)19:46
clarkbmordred: fungi can I pencil you in for doing that? (since you are doing it now anyways)19:46
fungiclarkb: sure19:46
clarkb#action mordred and fungi sort out issues with project renames in a zuulv3 world and write down process for renaming projects19:47
fungiyou can at least pencil me in for drafting the announcement taht we've decided renaming git repos is too complex to support from now on ;)19:47
*** yamahata has joined #openstack-meeting19:47
clarkbfungi: ha19:47
*** tdasilva has quit IRC19:47
*** tdasilva has joined #openstack-meeting19:47
mordredthe new rename method is to retire the old repo and import it with a new name19:48
clarkbjust so we don't forget I know things are slowing down due to holidays but lets try to keep the momentum up on the xenial upgrades. I plan to review ianw's changes for ether* to help out there19:48
*** electrofelix has quit IRC19:48
clarkbI'll also likely work to upgrade logstash.openstack.org this week19:48
fungihow do we feel about advance notification timeframe for the gerrit xenial upgrade?19:49
ianwmordred: we started an etherpad at the last rename point -> https://etherpad.openstack.org/p/rename-2017-10-20 .  i'm still happy to summarise what *actually* happens into documentation19:49
pabelangerwe also need to discuss git.o.o, I jus checked and they are not upgraded to 7.4 yet. We seem to not run yum update daily19:49
fungiare we still concerned about people with "special" firewall rules for the gerrit server's ip addresses?19:49
pabelangerso, we likley need to do rolling updates there19:49
ianwbut i imagine initially we should just etherpad it out, and then see what happens in real life19:49
clarkbpabelanger: that sounds like a bug19:49
pabelangerclarkb: most likely yes19:49
clarkbpabelanger: get daily updates working then do rolling restarts19:49
fungiianw: if we budget a lengthy outage for zuul, i think that's a fine plan19:50
mordredfungi: probably so ... should we consider shifting the gerrit server to a cloud that lets us create a long-lived neutron port?19:50
clarkbre Gerrit, I was thinking after ptg might be best just with everything zuul related and release happening between now and then19:50
mordredlike, I know on vexxhost, for instance, one can create a port, then attach that port to the server (like floating ips, but without nat) - so we could have the dns entries point to the standalone port and not to the one that just happens to be attached to the vm19:51
fungimordred: i'm more inclined to tell people that occasional ip address changes are a way of life and if you need access to the gerrit ssh api and a week warning that its ip address is changing isn't sufficient for you to get your corporate firewall overlords to adjust an exception in their egress filters, it's not our problem19:51
mordredfungi: "welcome to cloud"19:51
clarkbalso https does work and most corps allow https out19:51
*** hagridaaron has quit IRC19:51
jeblairremember also gerrit needs reverse dns on v4 and v6, and 64GB of ram19:52
fungiright, i expect this to mostly be an issue for third-party ci systems which need the ssh event stream19:52
clarkboh right it is a mail server so reverse dns is important19:52
fungiat least until we can integrate mqtt support into zuul ;)19:52
clarkbalso we should do review-dev first19:52
mordredwell, we can get the reverse done at vexxhost too - but we can also keep it where it is19:52
jeblairfungi: then we can deal with firewalls and the mqtt port?19:52
*** ekcs has joined #openstack-meeting19:52
clarkbmake sure java 8 doesn't break anything then settle on a review.o.o plan19:53
fungijeblair: yep!19:53
pabelangerI'd like to help with gerrit update this time around if possible19:53
pabelangerI haven't done one yet19:53
*** ricolin_ has quit IRC19:53
* mordred nominates pabelanger to do all the upgrading19:53
fungijeblair: except we are also working on websockets proxying for mqtt19:53
clarkbpabelanger: sweet, I can help walk through it on review dev if you want19:53
fungiso maybe not if they allow https19:53
pabelangerclarkb: great19:53
jeblairfungi: cool, so everyone's okay except the folks with MITM corporate proxies that don't support ws:// :)19:54
clarkbbut ya I think we should likely get review-dev where we want it. updated database, updated charset, updated to xenail then schedule production19:54
clarkbif we roughly schedule now and say production after PTG that still gives us through end of january to have ~1 month of notice19:54
*** dprince has quit IRC19:55
clarkband I'm happy to work with pabelanger to get review-dev side going19:55
fungiwould be nice to also not have it linger so long that it impacts our ability to upgrade the gerrit release early next cycle19:55
clarkbya though this is all prerequisite work for 2.14 anyways19:56
fungii'm assuming we want to decouple the distro upgrade and service upgrade19:56
clarkbso if we get it done on review-dev we can then sort out the 2.14 upgarde there19:56
fungiupgrade distro first obviously since it's a prereq19:56
clarkb(prereq because 2.14 needs java8)19:57
clarkbwe are almost out of time19:57
clarkb#topic open discussion19:57
fungii just mean i'm assuming we want to run gerrit 2.13 on xenial for at least a little while in production and not do xenial+2.14 all in one go19:57
clarkbfungi: ya19:57
fungi(or 2.15+ by then)19:57
clarkbalso did we lose the bot?19:57
clarkboh hey we did19:58
fungi1941 <-- openstack (~openstack@openstack/openstack) has quit (Remote host closed the connection)19:58
clarkbI'm guessing it was the http url fix that did it19:58
fungi1941 --> openstack (~openstack@openstack/openstack) has joined #openstack-meeting19:58
fungiyeah, i forgot that would restart it automatically19:58
clarkbwell thats about it for time. Enjoy the holidays and you can find us in #openstack-infra19:59
fungibut it did indeed merge during the meeting19:59
fungii'll go clean up channel topics now19:59
AJaegerthanks, fungi!19:59
*** gouthamr has joined #openstack-meeting19:59
clarkbfungi: thanks that allows me to find lunch20:00
pabelangergood year!20:00
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"20:00
*** AJaeger has left #openstack-meeting20:00
*** gouthamr has quit IRC20:01
*** tobiash has left #openstack-meeting20:04
*** VW_ has joined #openstack-meeting20:11
*** VW has quit IRC20:14
*** gouthamr has joined #openstack-meeting20:21
*** hagridaaron has joined #openstack-meeting20:23
*** dprince has joined #openstack-meeting20:23
*** hagridaaron has quit IRC20:23
*** slaweq_ has joined #openstack-meeting20:27
*** hagridaaron has joined #openstack-meeting20:27
*** VW_ has quit IRC20:35
*** ykatabam has joined #openstack-meeting20:48
*** Apoorva has quit IRC20:51
*** jamesmcarthur has quit IRC20:56
*** chyka has joined #openstack-meeting21:02
*** rossella_s has quit IRC21:04
*** rossella_s has joined #openstack-meeting21:06
*** chyka has quit IRC21:06
*** rbowen has quit IRC21:10
*** cleong has quit IRC21:10
*** edmondsw has joined #openstack-meeting21:17
*** Apoorva has joined #openstack-meeting21:20
*** ssathaye has quit IRC21:20
*** ssathaye has joined #openstack-meeting21:20
*** edmondsw has quit IRC21:22
*** hagridaaron has quit IRC21:26
*** rmascena has quit IRC21:27
*** slaweq_ is now known as slaweq21:33
*** HeOS has quit IRC21:38
*** slaweq has quit IRC21:38
*** pchavva has quit IRC21:42
*** fnaval has joined #openstack-meeting21:46
*** priteau_ has joined #openstack-meeting21:46
*** fnaval has quit IRC21:48
*** hagridaaron has joined #openstack-meeting21:49
*** priteau has quit IRC21:50
*** gouthamr has quit IRC21:52
*** slaweq has joined #openstack-meeting21:55
*** ijw has joined #openstack-meeting21:56
*** diablo_rojo_ has quit IRC21:59
*** slaweq has quit IRC22:00
*** rossella_s has quit IRC22:00
*** eharney has quit IRC22:05
*** priteau_ has quit IRC22:09
*** priteau has joined #openstack-meeting22:09
*** diablo_rojo has joined #openstack-meeting22:14
*** priteau has quit IRC22:14
*** gouthamr has joined #openstack-meeting22:23
*** rcernin has joined #openstack-meeting22:28
*** armstrong has joined #openstack-meeting22:28
*** HeOS has joined #openstack-meeting22:32
*** slaweq has joined #openstack-meeting22:32
*** salv-orl_ has quit IRC22:36
*** salv-orlando has joined #openstack-meeting22:37
*** slaweq has quit IRC22:37
*** hagridaaron has quit IRC22:38
*** hagridaaron has joined #openstack-meeting22:40
*** marst has quit IRC22:41
*** salv-orlando has quit IRC22:41
*** salv-orlando has joined #openstack-meeting22:42
*** hagridaaron has quit IRC22:45
*** slaweq has joined #openstack-meeting22:53
*** fnaval has joined #openstack-meeting22:57
*** slaweq has quit IRC22:58
*** lennyb has quit IRC22:58
*** rbudden has quit IRC23:00
*** fnaval has quit IRC23:00
*** lennyb has joined #openstack-meeting23:00
*** singlethink has joined #openstack-meeting23:01
*** edmondsw has joined #openstack-meeting23:06
*** edmondsw has quit IRC23:10
*** felipemonteiro has quit IRC23:24
*** felipemonteiro has joined #openstack-meeting23:24
*** andreas_s has joined #openstack-meeting23:28
*** fnaval has joined #openstack-meeting23:28
*** andreas_s has quit IRC23:32
*** fnaval has quit IRC23:33
*** HeOS has quit IRC23:34
*** singlethink has quit IRC23:49
*** jdurgin has quit IRC23:59

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