Wednesday, 2017-12-20

*** fnaval has joined #openstack-meeting00:00
*** mlavalle has left #openstack-meeting00:00
*** fnaval has quit IRC00:03
*** salv-orlando has quit IRC00:05
*** salv-orlando has joined #openstack-meeting00:05
*** edmondsw has joined #openstack-meeting00:08
*** salv-orlando has quit IRC00:11
*** edmondsw has quit IRC00:13
*** jdurgin has joined #openstack-meeting00:14
*** tlam_ has quit IRC00:18
*** yangyapeng has quit IRC00:27
*** yangyapeng has joined #openstack-meeting00:28
*** fnaval has joined #openstack-meeting00:31
*** bobh has joined #openstack-meeting00:32
*** yangyapeng has quit IRC00:32
*** fnaval has quit IRC00:34
*** esberglu has quit IRC00:38
*** xuzhuang has joined #openstack-meeting00:43
*** song has joined #openstack-meeting00:43
*** jamesmcarthur has joined #openstack-meeting00:44
*** tovin07_ has joined #openstack-meeting00:45
*** armstrong has quit IRC00:48
*** Yipei has joined #openstack-meeting00:50
*** joehuang has joined #openstack-meeting00:52
*** xuzhuang_ has joined #openstack-meeting00:52
*** zhiyuan_ has joined #openstack-meeting00:54
*** xuzhuang has quit IRC00:55
*** bobh has quit IRC00:56
*** kiennt26 has joined #openstack-meeting00:56
*** cyg has joined #openstack-meeting00:59
*** VW has joined #openstack-meeting00:59
zhiyuan_#startmeeting tricircle01:00
openstackMeeting started Wed Dec 20 01:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is zhiyuan_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:00
*** openstack changes topic to " (Meeting topic: tricircle)"01:00
openstackThe meeting name has been set to 'tricircle'01:00
*** dongfeng has joined #openstack-meeting01:00
*** jamesmcarthur has quit IRC01:01
zhiyuan_the patch for distinguishing request source has been merged, so it's time for us to move on and finish the resource deletion reliability feature01:01
zhiyuan_the spec for that feature is submitted and under review, what about the implementation?01:02
songthe code have finished, i need to test it.01:02
songafter the test i pull it.01:02
zhiyuan_ok, thanks song01:04
songyou are welcome.01:04
zhiyuan_xuzhuang, have you read the spec? any comment? since you are going to finish the security group deletion part01:06
*** salv-orlando has joined #openstack-meeting01:06
xuzhuang_yes, I have readed and gived some comment01:06
*** wanghao has joined #openstack-meeting01:08
xuzhuang_I think the workload of deleting sg is not much. It's better to write the first version of code and test it.01:08
xuzhuang_Now I need the api the deleting_resource, I will complete the first version of code as soon as possible after son has pushed.01:10
*** bzhao has quit IRC01:10
*** salv-orlando has quit IRC01:11
zhiyuan_yes,  you can download his code via "git review -d ID" and start from his code01:11
songyes, I can give you my code.01:11
zhiyuan_ID is the number you can see in the review page link01:12
*** bzhao has joined #openstack-meeting01:12
*** wanghao has quit IRC01:12
*** bbzhao has joined #openstack-meeting01:12
*** yangyapeng has joined #openstack-meeting01:12
xuzhuang_Got it01:12
*** wanghao has joined #openstack-meeting01:13
joehuangor you can get the code from the upper right link (download) of the patch01:14
zhiyuan_joe, will this way also keep the commit history?01:15
zhiyuan_or just download the patch files01:15
joehuangjust download files01:17
*** zxh has joined #openstack-meeting01:17
xuzhuang_Got it01:17
joehuangthere are several links: checkout, pull, cherry pick, I did not try all of them, may be check out can keep the git commit history01:18
zhiyuan_xuzhuang, you can have a try :)01:18
zhiyuan_next, new cross-neutron l3 networking model, Yipei, have time to investigate it?01:19
Yipeii have already finished my own business01:20
Yipeialready working on it01:20
*** yamamoto has joined #openstack-meeting01:21
*** yamamoto has quit IRC01:21
zhiyuan_have risk? we have about one month for the last milestone01:22
*** ZacharyMa has joined #openstack-meeting01:23
*** psachin has joined #openstack-meeting01:23
*** jamesmcarthur has joined #openstack-meeting01:25
Yipeii think it is difficult to finish the implementation before the last milestone. but it will try my best, and need you guys' help01:26
songthe next openstack is q,  i know it is about in next year  2.28. that is right?01:26
*** Apoorva_ has joined #openstack-meeting01:26
zhiyuan_Yipei, fine, I can support you01:27
Yipeiok, thanks a lot, zhiyuan01:27
*** psachin has quit IRC01:28
*** Apoorva has quit IRC01:29
zhiyuan_the final release for Q is from Feb26th to Mar2nd01:29
songthanks zhiyuan .out project milestone is early than it?01:30
*** Apoorva_ has quit IRC01:31
songcan we can start the new milestone after the next month?01:31
zhiyuan_we follow the openstack schedule, have three milestones, RC1 and the final RC01:31
zhiyuan_here is the schedule:
*** psachin has joined #openstack-meeting01:32
songoh thanks.01:32
*** aselius has quit IRC01:32
zhiyuan_so far for the progress update, any other topics?01:33
songno for me.01:34
xuzhuang_no for me01:34
Yipeino from me01:35
zhiyuan_then we just finish our meeting a bit earlier, thanks for attending01:35
*** openstack changes topic to "OpenStack Meetings ||"01:35
openstackMeeting ended Wed Dec 20 01:35:48 2017 UTC.  Information about MeetBot at . (v 0.1.4)01:35
openstackMinutes (text):
*** dongfeng has left #openstack-meeting01:35
*** song has quit IRC01:36
*** cyg has quit IRC01:37
*** Yipei has left #openstack-meeting01:37
*** yamahata has quit IRC01:38
*** yamahata has joined #openstack-meeting01:39
*** zxh has quit IRC01:40
*** xuzhuang_ has quit IRC01:41
*** zhiyuan_ has quit IRC01:42
*** makowals has quit IRC01:43
*** andreykurilin has quit IRC01:43
*** makowals has joined #openstack-meeting01:44
*** andreykurilin has joined #openstack-meeting01:46
*** dmacpher has joined #openstack-meeting01:47
*** joehuang has quit IRC01:53
*** gagehugo has left #openstack-meeting01:56
*** jamesmcarthur has quit IRC01:57
*** edleafe- has joined #openstack-meeting01:57
*** edleafe has quit IRC01:57
*** yamamoto has joined #openstack-meeting01:57
*** felipemonteiro has quit IRC01:57
*** ekcs has quit IRC02:02
*** iyamahat has quit IRC02:03
*** iyamahat has joined #openstack-meeting02:03
*** dprince has quit IRC02:06
*** salv-orlando has joined #openstack-meeting02:07
*** salv-orlando has quit IRC02:11
*** epico has joined #openstack-meeting02:20
*** fzdarsky_ has joined #openstack-meeting02:29
*** fzdarsky has quit IRC02:30
*** VW has quit IRC02:32
*** bobh has joined #openstack-meeting02:34
*** Tom-Tom has joined #openstack-meeting02:41
*** unicell has quit IRC02:45
*** bobh has quit IRC02:51
*** bobh has joined #openstack-meeting02:52
*** llu has left #openstack-meeting02:53
*** gmann has quit IRC02:55
*** ijw has quit IRC02:58
*** markstur has quit IRC02:59
*** bobh has quit IRC03:06
*** salv-orlando has joined #openstack-meeting03:07
*** lin_yang has quit IRC03:08
*** yamahata has quit IRC03:11
*** iyamahat has quit IRC03:12
*** salv-orlando has quit IRC03:12
*** bobh has joined #openstack-meeting03:13
*** Tom-Tom has quit IRC03:25
*** Tom-Tom has joined #openstack-meeting03:25
*** ZacharyMa has quit IRC03:29
*** Tom-Tom has quit IRC03:29
*** andreas_s has joined #openstack-meeting03:29
*** ZacharyMa has joined #openstack-meeting03:29
*** tinwood has quit IRC03:30
*** tinwood has joined #openstack-meeting03:31
*** artom has quit IRC03:31
*** artom has joined #openstack-meeting03:31
*** andreas_s has quit IRC03:33
*** keiko has joined #openstack-meeting03:43
*** edmondsw has joined #openstack-meeting03:44
*** Apoorva has joined #openstack-meeting03:44
*** gongysh has joined #openstack-meeting03:48
*** slaweq has joined #openstack-meeting03:49
*** edmondsw has quit IRC03:49
*** gyee has quit IRC03:51
*** epico has quit IRC03:51
*** slaweq has quit IRC03:54
*** markstur has joined #openstack-meeting03:57
*** IgorYozhikov has quit IRC03:58
*** zhurong has joined #openstack-meeting03:59
*** IgorYozhikov has joined #openstack-meeting04:00
*** markstur has quit IRC04:01
*** yamamoto_ has joined #openstack-meeting04:08
*** salv-orlando has joined #openstack-meeting04:08
*** yamamoto has quit IRC04:11
*** salv-orlando has quit IRC04:13
*** cdub has quit IRC04:20
*** shu-mutou has joined #openstack-meeting04:20
*** ricolin_ has joined #openstack-meeting04:24
*** phuoc_ has joined #openstack-meeting04:24
*** epico has joined #openstack-meeting04:25
*** iyamahat has joined #openstack-meeting04:25
*** tbh has joined #openstack-meeting04:25
*** diga has joined #openstack-meeting04:29
*** joxyuki has joined #openstack-meeting04:30
*** Tom-Tom has joined #openstack-meeting04:30
*** dkushwaha has joined #openstack-meeting04:31
gongysh#startmeeting tacker04:31
openstackMeeting started Wed Dec 20 04:31:04 2017 UTC and is due to finish in 60 minutes.  The chair is gongysh. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:31
*** openstack changes topic to " (Meeting topic: tacker)"04:31
openstackThe meeting name has been set to 'tacker'04:31
gongyshdkushwaha, hi04:31
gongysh#topic roll call04:31
*** openstack changes topic to "roll call (Meeting topic: tacker)"04:31
gongyshphuoc_, hi04:31
phuoc_hi mr.Gongysh04:32
*** tbh has quit IRC04:32
phuoc_hi joxyuki04:32
*** tbh has joined #openstack-meeting04:33
*** YanXing_an has joined #openstack-meeting04:33
gongyshtbh, YanXing_an , hi04:34
gongysh#topic bp04:34
*** openstack changes topic to "bp (Meeting topic: tacker)"04:34
gongyshphuoc_, do you have any update for your bps?04:34
phuoc_gongysh, I am starting in implementation04:35
*** tbh has quit IRC04:35
*** Tom-Tom has quit IRC04:35
*** iyamahat has quit IRC04:35
phuoc_if you guys have time, please give me feed back in
phuoc_I will update the other, and document for this patch soon04:36
gongyshphuoc_,  nice progress04:37
*** tbh has joined #openstack-meeting04:38
gongyshit seems there are difference between vnfds for openstack and k8s04:38
*** iyamahat has joined #openstack-meeting04:39
phuoc_gongysh, I follow
phuoc_they define new type: tosca.datatypes.nfv.VnfcConfigurableProperties04:40
phuoc_so, I try to match to new definition in TOSCA04:41
gongyshtbh, hi04:41
*** kapil_ has joined #openstack-meeting04:42
*** VW has joined #openstack-meeting04:42
gongyshok,  I will have a look at.04:43
*** YanXing_an has quit IRC04:44
*** armax has quit IRC04:44
gongyshdkushwaha,  could you have a look at it too?04:44
dkushwahagongysh, sure.04:44
gongyshphuoc_, do you have other bps during the cycle?04:45
*** tbh has quit IRC04:45
phuoc_no, I don't04:45
gongyshdiga, could you please talk about the API bp?04:45
phuoc_I and mardim will implement vnffg update04:46
gongyshphuoc_, yes, thanks04:46
phuoc_thank gongysh and dkushwaha04:47
digagongysh: okay04:47
gongyshok, please04:47
digahello everyone04:47
digacurrent approach I have taken using the falcon framework04:48
phuoc_hi diga :)04:48
digaI see we need only one dependancy now which falcon module04:48
*** bobh has quit IRC04:48
digawhich is also part of openstack requirement04:48
digaso we don't have to ask for approval for openstack requirement team04:48
*** zhhuabj has quit IRC04:49
digawhich is already exist there04:49
gongyshWhich frameworks are in use in Mitaka:04:49
gongyshFalcon: 4 projects04:49
gongyshCustom + routes: 12 projects04:49
gongyshPecan: 12 projects04:49
gongyshFlask: 2 projects04:49 1 project04:49
digaAS this is first patch as part of this developmenet04:49
gongyshthis is from
digayes gongysh04:49
gongyshso we will use falcon anyway.04:49
gongyshthat's fine.04:49
digagongysh: yeah04:50
*** YanXing_an has joined #openstack-meeting04:50
*** YanXing_an has quit IRC04:50
digacurrently zuul is failing because falcon feature branch is too old, so I am working with infra team to rebase the feature branch with master branch04:50
digaI hope this issue will get resolved by today/tomorrow04:50
phuoc_diga, that's good04:51
*** armax has joined #openstack-meeting04:51
gongyshdiga, we will wait for you and let the API improvement go smoothly and fast.04:51
digaonce we merge the first patch, my next target is to implement one after one api of tacker into falcon framework04:51
*** armax has quit IRC04:51
digagongysh: yes, sure04:51
gongyshdiga, thanks04:52
digagongysh: I understand that this is long term pending thing but anyway I am targetting this for queens release04:52
gongyshdiga, I remember that your team help with tacker openstack command04:52
digalets see how far we go on this if nothing major comes on the road04:52
digagongysh: yes, but I have now only one person working on tacker04:53
digacurrently kapil_ is working on solving bugs04:53
*** YanXingAn has joined #openstack-meeting04:53
gongyshdkushwaha, do you have any updates on bps?04:54
digaI am giving him enough time to solve the bugs first, then I am thinking to involve him in the tacker api framework04:54
digabecause i see so much work involved in this feature04:54
dkushwahagongysh, not for now.04:54
gongyshYanXingAn, do you have any to say for your bps?04:55
gongyshok, seems YanXingAn  is still at their company meeting.04:56
gongysh#topic bug04:56
*** openstack changes topic to "bug (Meeting topic: tacker)"04:56
gongyshfirst bug is about CI system04:56
openstackLaunchpad bug 1739342 in tacker "tacker ci does not support tls_proxy service enabled" [High,In progress] - Assigned to yong sheng gong (gongysh)04:56
gongyshit seems our tacker CI job does not support tls proxy04:57
gongyshI have an quick fix to disable the tls proxy first.04:57
*** ianw is now known as ianw_pto04:57
gongyshand need some time to investigate how we support tls proxy.04:57
*** links has joined #openstack-meeting04:57
openstackLaunchpad bug 1719841 in tacker "vim configuration does not allow the INSECURE property" [Medium,Triaged] - Assigned to Taseer Ahmed (taseer94)04:57
phuoc_I see many people meet that bug04:58
gongyshok, let fix it in that bug04:59
*** YanXingAn has quit IRC04:59
gongyshhe is not active,  then I will try to fix it.05:00
gongyshwho knows Taseer Ahmed (taseer94) ?05:00
*** zhhuabj has joined #openstack-meeting05:00
phuoc_he is from opnfv-sfc project05:01
gongyshdkushwaha, do you have any other bug to talk?05:02
gongyshto discuss05:02
*** ykatabam has quit IRC05:02
dkushwahagongysh, not worked in that part in last week.05:02
*** caowei has joined #openstack-meeting05:03
*** felipemonteiro has joined #openstack-meeting05:03
gongyshok, if you have time, please keep an eye on the bug reports.05:03
gongysh#topic open dicusssion05:03
*** openstack changes topic to "open dicusssion (Meeting topic: tacker)"05:03
dkushwahagongysh, sure, will do.05:03
dkushwahagongysh,  i have some points to discuss regarding heat stack05:04
gongyshdkushwaha, sure, please05:04
*** ricolin_ has quit IRC05:05
dkushwahagongysh, we are doing some PoC regarding resource reservation in Tacker05:05
*** VW has quit IRC05:05
*** slaweq has joined #openstack-meeting05:05
dkushwahagongysh, so we are integrating Tacker-Blazor for that05:05
phuoc_dkushwaha, that sounds good05:06
dkushwahagongysh, in some cases we needs to update the heat stack, but as of now we can not update heat stack in vnf-update operation05:06
dkushwahagongysh, i want to know the approach how we can update it?05:07
*** Tom-Tom has joined #openstack-meeting05:08
gongyshdkushwaha, what do you mean the resource reservation related to heat stack.05:08
gongyshdo you have devise a way to do it in pure heat environment?05:08
gongyshcan you paste tacker-blazor url here too?05:09
*** salv-orlando has joined #openstack-meeting05:09
*** slaweq has quit IRC05:09
phuoc_dkushawaha, I think we can call e.g. heat stack update to update vnf05:10
*** yamamoto_ has quit IRC05:10
dkushwahagongysh, i am not sure, i can paste link here, as it private for now, but my team started drafting spec for that05:10
gongyshdkushwaha, to do it, the steps are: first devise a way to do in pure heat way, and then do integration on tacker. maybe we need to update tacker codes to do it.05:12
joxyukihi all, I am working tacker-blazar with dkushwaha.05:14
dkushwahagongysh, once a vnf deployed, we create reservation in blazor side, and then needs to update vnf with that reservation data. which requires update05:14
dkushwahajoxyuki, could you please explain05:14
*** salv-orlando has quit IRC05:15
joxyukiyes, to create a VM using reserved resource, heat stack need to know reservation-id in HOT.05:15
gongyshjoxyuki, that's good.05:16
joxyukigongysh, what do you mean "device" exactly?05:16
gongyshdevice is old term for vnf?05:16
gongyshdevice is old term for vnf.05:17
joxyukii see, thax05:17
gongyshpreviously, tacker is service vm manager.05:17
gongyshjoxyuki, so you seq is: vnfm -> nfvo: reserve resource05:18
gongyshvnfm -> instantiate vnf with reservation id.05:18
joxyukigyngysh, no.05:19
dkushwahajoxyuki, sorry for interrupting, but i think you interpreting  "devise" as "device"05:20
*** coolsvap has joined #openstack-meeting05:20
joxyuki1) user-> tacker: vnf-create, 2) user -> blazar: reservation, 3) user->tacker: input reservation-id05:21
joxyukiyes, devise -> device05:21
gongyshjoxyuki, 1) user -> tacker: vnf-create will create vms on target openstack, why do you still need to do 2)?05:22
*** phuoc_ has quit IRC05:22
gongyshI think the sequence is to be: a) user -> blazar: reservation b) user-> tacker: vnf-create with reservation-id05:23
joxyukigongysh, could you see ? this is our use case.05:24
gongyshjoxyuki, ok, I will have a look05:25
*** VW has joined #openstack-meeting05:25
joxyukigongysh, this is a use case need reservation for short term events such as  sports match.05:25
gongyshjoxyuki, glad to know your team is trying to use tacker.05:25
gongyshjoxyuki, keep in touch at tacker channel05:27
gongyshthanks everyone05:27
joxyukigongysh, yes, keep in touch.05:27
*** openstack changes topic to "OpenStack Meetings ||"05:27
openstackMeeting ended Wed Dec 20 05:27:42 2017 UTC.  Information about MeetBot at . (v 0.1.4)05:27
openstackMinutes (text):
*** edmondsw has joined #openstack-meeting05:32
*** yamamoto has joined #openstack-meeting05:32
*** kapil_ has quit IRC05:35
*** edmondsw has quit IRC05:37
*** sridharg has joined #openstack-meeting05:38
*** joxyuki is now known as help05:40
*** help is now known as Guest1011405:40
*** yangyapeng has quit IRC05:40
*** Guest10114 is now known as joxyuki05:41
*** yangyapeng has joined #openstack-meeting05:41
*** yangyapeng has quit IRC05:45
*** Apoorva has quit IRC05:50
*** yanxingan has joined #openstack-meeting05:51
*** gouthamr has quit IRC05:57
*** manikanta_tadi has joined #openstack-meeting06:00
*** yangyapeng has joined #openstack-meeting06:03
*** wanghao_ has joined #openstack-meeting06:04
*** VW has quit IRC06:06
*** wanghao has quit IRC06:08
*** salv-orlando has joined #openstack-meeting06:10
*** MinWookKim has joined #openstack-meeting06:10
*** salv-orlando has quit IRC06:15
*** marios has joined #openstack-meeting06:16
*** d0ugal has quit IRC06:17
*** Tom-Tom has quit IRC06:21
*** d0ugal has joined #openstack-meeting06:23
*** Tom-Tom has joined #openstack-meeting06:24
*** salv-orlando has joined #openstack-meeting06:28
*** VW has joined #openstack-meeting06:30
*** diga has quit IRC06:31
*** VW has quit IRC06:34
*** ykatabam has joined #openstack-meeting06:37
*** felipemonteiro has quit IRC06:38
*** felipemonteiro has joined #openstack-meeting06:39
*** unicell has joined #openstack-meeting06:40
*** ianychoi has quit IRC06:44
*** e0ne has joined #openstack-meeting06:47
*** yamamoto has quit IRC06:49
*** janki has joined #openstack-meeting06:49
*** felipemonteiro has quit IRC06:50
*** andreas_s has joined #openstack-meeting06:56
*** yamamoto has joined #openstack-meeting07:04
*** rcernin has quit IRC07:08
*** yamamoto has quit IRC07:09
*** e0ne has quit IRC07:12
*** gongysh has quit IRC07:17
*** e0ne has joined #openstack-meeting07:19
*** yanxingan has quit IRC07:19
*** yamamoto has joined #openstack-meeting07:20
*** edmondsw has joined #openstack-meeting07:21
*** yanxingan has joined #openstack-meeting07:23
*** yamamoto has quit IRC07:24
*** edmondsw has quit IRC07:25
*** e0ne has quit IRC07:25
*** dmacpher has quit IRC07:34
*** kiennt26 has quit IRC07:35
*** sapd has quit IRC07:40
*** sapd has joined #openstack-meeting07:41
*** iyamahat has quit IRC07:42
*** gongysh has joined #openstack-meeting07:42
*** slaweq has joined #openstack-meeting07:45
*** HeOS has joined #openstack-meeting07:46
*** iyamahat has joined #openstack-meeting07:49
*** iyamahat has quit IRC07:50
*** unicell has left #openstack-meeting07:51
*** iyamahat has joined #openstack-meeting07:57
*** mkoderer__ has joined #openstack-meeting08:01
*** yamamoto has joined #openstack-meeting08:04
*** phil_ has joined #openstack-meeting08:05
*** phil_ is now known as Guest4613908:06
*** iyamahat has quit IRC08:08
*** yangyapeng has quit IRC08:09
*** yamamoto has quit IRC08:09
*** yangyapeng has joined #openstack-meeting08:11
*** Tom-Tom has quit IRC08:14
*** Tom-Tom has joined #openstack-meeting08:15
*** zhurong has quit IRC08:17
*** tovin07_ has quit IRC08:18
*** tovin07_ has joined #openstack-meeting08:19
*** Tom-Tom has quit IRC08:19
*** Tom-Tom has joined #openstack-meeting08:19
*** Alex_Staf_ has joined #openstack-meeting08:22
*** salv-orlando has quit IRC08:22
*** iyamahat has joined #openstack-meeting08:23
*** alexchadin has joined #openstack-meeting08:26
*** sapd has quit IRC08:33
*** yamamoto has joined #openstack-meeting08:34
*** sapd has joined #openstack-meeting08:35
*** yamamoto has quit IRC08:39
*** kmalloc has quit IRC08:41
*** slaweq_ has joined #openstack-meeting08:49
*** yamamoto has joined #openstack-meeting08:50
*** yamamoto has quit IRC08:54
*** slaweq_ has quit IRC08:54
*** yamamoto has joined #openstack-meeting08:56
*** yamamoto has quit IRC08:56
*** salv-orlando has joined #openstack-meeting08:57
*** anilvenkata has joined #openstack-meeting08:58
*** alexchadin has quit IRC09:04
*** alexchadin has joined #openstack-meeting09:04
*** yamamoto has joined #openstack-meeting09:05
*** wanghao has joined #openstack-meeting09:06
*** wanghao_ has quit IRC09:10
*** joxyuki has quit IRC09:13
*** rossella_s has joined #openstack-meeting09:13
*** yanxingan has quit IRC09:18
*** slaweq_ has joined #openstack-meeting09:20
*** YanXing_an has joined #openstack-meeting09:20
*** slaweq_ has quit IRC09:25
*** e0ne has joined #openstack-meeting09:26
*** oidgar has joined #openstack-meeting09:28
*** anilvenkata has quit IRC09:28
*** anilvenkata has joined #openstack-meeting09:29
*** lpetrut has joined #openstack-meeting09:30
*** wanghao has quit IRC09:36
*** wanghao has joined #openstack-meeting09:36
*** wanghao has quit IRC09:37
*** wanghao has joined #openstack-meeting09:37
*** wanghao has quit IRC09:38
*** wanghao has joined #openstack-meeting09:38
*** wanghao has quit IRC09:38
*** wanghao has joined #openstack-meeting09:39
*** wanghao has quit IRC09:39
*** wanghao has joined #openstack-meeting09:39
*** wanghao has quit IRC09:40
*** wanghao has joined #openstack-meeting09:40
*** iyamahat has quit IRC09:40
*** wanghao has quit IRC09:41
*** wanghao has joined #openstack-meeting09:41
*** wanghao has quit IRC09:42
*** wanghao has joined #openstack-meeting09:42
*** wanghao has quit IRC09:42
*** wanghao has joined #openstack-meeting09:43
*** wanghao has quit IRC09:43
*** YanXing_an has quit IRC09:49
*** XueFeng has quit IRC09:51
*** YanXing_an has joined #openstack-meeting09:52
*** XueFeng has joined #openstack-meeting09:52
*** YanXing_an has quit IRC10:00
*** psachin has quit IRC10:01
*** tovin07_ has quit IRC10:06
*** rossella_s has quit IRC10:06
*** yanxingan has joined #openstack-meeting10:07
*** e0ne_ has joined #openstack-meeting10:08
*** rossella_s has joined #openstack-meeting10:09
*** psachin has joined #openstack-meeting10:10
*** e0ne has quit IRC10:11
*** Qiming has quit IRC10:14
*** Qiming has joined #openstack-meeting10:14
*** jeblair has quit IRC10:15
*** bcafarel has quit IRC10:15
*** armstrong has joined #openstack-meeting10:15
*** jeblair has joined #openstack-meeting10:16
*** yanxingan has quit IRC10:17
*** psachin has quit IRC10:20
*** caowei has quit IRC10:21
*** Neptu_ is now known as Neptu10:23
*** Tom-Tom has quit IRC10:24
*** rossella_s has quit IRC10:26
*** sambetts|afk is now known as sambetts10:27
*** rossella_s has joined #openstack-meeting10:27
*** aarefiev has joined #openstack-meeting10:30
*** Qiming has quit IRC10:30
*** Qiming has joined #openstack-meeting10:36
*** ruan_he has quit IRC10:40
*** alexchadin has quit IRC10:41
*** alexchadin has joined #openstack-meeting10:42
*** gongysh has quit IRC10:42
*** bcafarel has joined #openstack-meeting10:42
*** krtaylor has quit IRC10:53
*** edmondsw has joined #openstack-meeting10:57
*** oneswig has joined #openstack-meeting11:00
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Dec 20 11:00:24 2017 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.11:00
*** openstack changes topic to " (Meeting topic: scientific-sig)"11:00
openstackThe meeting name has been set to 'scientific_sig'11:00
oneswigSeasons greetings11:00
oneswig#link there isn't an agenda as such
armstrongThanks and same to you11:01
*** edmondsw has quit IRC11:01
oneswigHey armstrong have you moved timezones?  Thought you were in Canada...11:01
armstrongYes I am still in Canada11:02
armstrongI missed the meeting yesterday11:02
oneswigWas it Ontario?11:03
armstrongI am in Montréal11:05
oneswigHave you completed your PhD?11:06
*** krtaylor has joined #openstack-meeting11:06
armstrongNo not yet11:06
*** rossella_s has quit IRC11:06
oneswigHow's the research going?11:07
armstrongSo far so good11:07
*** rossella_s has joined #openstack-meeting11:07
*** yamamoto_ has joined #openstack-meeting11:08
oneswigIt's on private cloud infrastructure, right?  What are you looking at?11:08
armstrongLive migration11:08
oneswigInteresting.  Live migration in research computing or more generally?11:09
armstrongResearch computing11:09
*** yamamoto has quit IRC11:11
oneswigWhat are you finding so far?11:11
*** gcb has quit IRC11:12
oneswigLive migration doesn't come into the workloads I typically see, but certainly does come into the supporting components deployed around it - web APIs, house keeping activities, jenkins instances etc.11:15
armstrongBased on my last presentation @Sydney, I want to add different VMM, because so far only KVM and Xen were considered11:16
oneswigI hadn't seen this presentation - got a link to it?11:16
armstrongIt’s in the link of the Tuesday’s presentation we had11:19
oneswigarmstrong: what other VMM is there?11:19
armstrongVMware etc.11:19
armstrongThere are five or so supported by OpenStack11:20
oneswigAh OK, got it.11:20
*** reedip has quit IRC11:21
oneswigarmstrong: are there findings you'd like to share some time in a Americas-timezone meeting?11:22
*** priteau has joined #openstack-meeting11:24
oneswigarmstrong: if you're interested in doing that11:26
armstrongSure oneswig, I am interested11:27
oneswigLet me know when you would like to do that, we can put it on the agenda.11:27
armstrongOk good11:28
*** rossella_s has quit IRC11:29
oneswigI've been planning for 2018 to bring in some of the discussions that have been going on with the team at CERN, around developing OpenStack's support for research computing11:29
*** caboucha has joined #openstack-meeting11:30
*** andreas__ has joined #openstack-meeting11:30
armstrongThat is interesting11:30
armstrongCERN uses OpenStack ?11:31
oneswigyes, quite a lot :-)11:31
*** neiljerram has joined #openstack-meeting11:31
*** andreas__ has quit IRC11:31
ildikovoneswig: I have a quick question when we get to the open discussion part :)11:31
oneswigildikov: there are no other kinds of discussion today - we are taking it easy :-)11:32
ildikovoneswig: coolio :)11:32
oneswigfire away11:32
*** rossella_s has joined #openstack-meeting11:32
ildikovoneswig: just wanted to ask whether the scientific SIG would be interested in occupying a few slots at the PTG ?11:33
*** andreas_s has quit IRC11:33
oneswigFor development work?11:33
*** alexchadin has quit IRC11:33
ildikovoneswig: Technical discussions or even development work11:34
*** reedip has joined #openstack-meeting11:35
ildikovoneswig: we're providing space for working groups/SIG at the beginning of the week and thought to ask whether there's interest from you guys11:35
oneswigI don't know how many active SIG members will be in Dublin but I'm assuming a few will be attending.  From our firm, probably 3-4 (ie, half the company :-)11:35
ildikovWould you like to have dedicated slots or rather joining project discussions and other sessions?11:36
oneswigildikov: can you explain the difference from the forum?11:37
ildikovoneswig: most of the attendees are developers and we're focusing on planning for the upcoming cycle and any other more technical discussions11:38
oneswigildikov: it's hard to know.  If the forum's about communicating needs and pain points, what input is needed at the PTG - more of the same?11:38
ildikovWhile the forum is more about gathering the user, operator and developer communities for feedback and a bit higher level chats11:39
oneswigMy first thought is to sit in on project meetings rather than have dedicated slots, but that's going to be happening anyway.11:39
*** alexchadin has joined #openstack-meeting11:39
*** psachin has joined #openstack-meeting11:39
oneswigildikov: if there was a dedicate slot for the scientific sig, how would you like to see it used?11:40
ildikovPTG would be about to figure out how to address the pain points11:40
*** oidgar has quit IRC11:40
armstrongIIdikov: when is the PTG coming up?11:40
ildikovoneswig: how to use it is on the group really11:41
ildikovoneswig: it's not a must rather than an offer to think about whether you can utilize it as a group11:41
oneswigildikov: when do you need to know?11:42
ildikovoneswig: you can use to have discussions around some items you would like get addressed and have devs in the room as well11:42
ildikovoneswig: sooner rather than later, will ask my colleague who's organizing the slots11:43
oneswigI can imagine it being useful in various ways - agreed.  I think it may come down to whether some of the key SIG members involved are planning to go to Dublin11:43
ildikovarmstrong: it's the week of February 26th11:43
ildikovoneswig: yeah, it's definitely more useful if you have a reasonable coverage from the team11:44
oneswigI shall enquire...11:44
armstrongiIdikov: thanks, I will like to attend11:44
ildikovoneswig: there are also options to occupy a half day or a full, etc11:44
ildikovarmstrong: awesome!11:44
ildikovarmstrong: let me know if you have any questions11:46
oneswighalf-day tops, I think.  Can't expect anyone to listen for longer than that11:46
armstrongiIdikov: ok I will let you know. Thanks 😃11:46
ildikovoneswig: ok, I will let Kendall know and will check back on deadlines11:47
ildikovoneswig: BTW, I will attend RCUK in January11:48
oneswigildikov: and I'll ask around for likely attendees.  I think if we have enough, there will be a critical mass.11:48
oneswigRCUK: excellent - are you presenting?11:48
oneswigI will be and I believe the Tuba Guy will be too :-)11:48
oneswigOr at least, taking part.11:48
ildikovoneswig: yep a short one on the Passport program and a bit on ORC11:49
*** alexchadin has quit IRC11:49
oneswigOh nice.  I'd be interested in the passport program11:49
ildikovoneswig: coolio11:49
oneswigNot seen a presentation on that yet11:49
ildikovoneswig: are you aware of any other happening that week in London that's OpenStack related?11:50
ildikovoneswig: I think there was on the Summit, will look for links when I'm back to my laptop11:50
oneswigCommunity events, no.  But I think the London OpenStack is overdue another meetup, and I can nudge Darryl.11:51
oneswigThanks ildikov - don't worry I think I can find it11:51
ildikovoneswig: thanks11:52
ildikovoneswig: yep, that should be the one11:52
oneswigarmstrong I looked for your summit presentation but didn't find it11:52
armstrongiIdikov: is the PTG a sponsored program?11:53
armstrongoneswig: really?11:53
ildikovarmstrong: you whether the event itself is sponsored by companies?11:54
armstrongImmediately after I did the presentation, I submitted the link to the slides and works11:54
*** rossella_s has quit IRC11:55
armstrongiIdikov: yes is it sponsored by OpenStack11:55
ildikovarmstrong: it is an OpenStack event organized by the Foundation11:55
*** oidgar has joined #openstack-meeting11:56
armstrongIIdikov: Ok thanks, I asked because I saw something like $100 registration at Eventbrite :)11:57
ildikovarmstrong: yes, it has a registration fee11:58
armstrongoneswig: where you not in the hall on Tuesday? When we were presenting? I think I was the last to pressent that day11:58
*** rossella_s has joined #openstack-meeting11:58
ildikovarmstrong: I can ask whether we have the travel support program still open for this one if you need it11:58
oneswigarmstrong: Ah, at the scientific-SIG lightning talks?  Now I'm with you.11:59
armstrongIIdikov: yes please I will need it thanks11:59
oneswigThought there was something more involved in the summit schedule.11:59
*** salv-orl_ has joined #openstack-meeting11:59
ildikovarmstrong: will get back to you on this when I got the info from my colleagues12:00
*** unicell has joined #openstack-meeting12:00
armstrongIIdikov: ok waiting on the feedback12:01
oneswigWe are out of time, that crept up12:01
*** epico has quit IRC12:01
oneswigGotta close the session12:01
oneswigildikov: will let you know on the PTG slot, thanks for suggesting it.12:01
oneswig... and have a lovely Christmas.12:01
*** openstack changes topic to "OpenStack Meetings ||"12:02
openstackMeeting ended Wed Dec 20 12:02:14 2017 UTC.  Information about MeetBot at . (v 0.1.4)12:02
openstackMinutes (text):
ildikovoneswig: cool thanks12:02
ildikovoneswig: Happy Holidays!12:02
*** priteau has quit IRC12:03
oneswigRight back at ya :-)12:03
*** ricolin_ has joined #openstack-meeting12:03
oneswigthanks armstrong12:03
*** salv-orlando has quit IRC12:03
*** priteau has joined #openstack-meeting12:03
*** oneswig has quit IRC12:04
*** rossella_s has quit IRC12:04
*** rossella_s has joined #openstack-meeting12:06
*** andreas_s has joined #openstack-meeting12:06
*** priteau has quit IRC12:08
*** andreas_s has quit IRC12:11
*** andreas_s has joined #openstack-meeting12:11
*** alexchadin has joined #openstack-meeting12:15
*** raildo has joined #openstack-meeting12:29
*** rossella_s has quit IRC12:33
*** aarefiev has quit IRC12:33
*** rossella_s has joined #openstack-meeting12:35
*** ricolin_ has quit IRC12:36
*** MinWookKim has quit IRC12:36
*** ricolin has joined #openstack-meeting12:36
*** gcb has joined #openstack-meeting12:39
*** liuyulong has joined #openstack-meeting12:43
*** edmondsw has joined #openstack-meeting12:45
*** bobh has joined #openstack-meeting12:45
*** yanxingan has joined #openstack-meeting12:45
*** ZacharyMa has quit IRC12:45
*** felipemonteiro has joined #openstack-meeting12:46
*** gcb has quit IRC12:47
*** edmondsw has quit IRC12:49
*** felipemonteiro has quit IRC12:50
*** kiennt26 has joined #openstack-meeting12:53
*** rossella_s has quit IRC12:57
*** rossella_s has joined #openstack-meeting13:03
*** dmellado has quit IRC13:05
*** coolsvap has quit IRC13:05
*** dprince has joined #openstack-meeting13:08
*** yangyapeng has quit IRC13:08
*** yangyapeng has joined #openstack-meeting13:09
*** e0ne has joined #openstack-meeting13:10
*** e0ne_ has quit IRC13:13
*** yangyapeng has quit IRC13:13
*** ykatabam has quit IRC13:14
*** dmellado has joined #openstack-meeting13:15
*** dmellado has quit IRC13:19
*** dmellado has joined #openstack-meeting13:21
*** dmacpher has joined #openstack-meeting13:27
*** alexchadin has quit IRC13:27
*** stevebaker has joined #openstack-meeting13:28
*** guhcampos has joined #openstack-meeting13:28
*** manikanta_tadi has quit IRC13:30
*** bobh has quit IRC13:31
*** yamamoto_ has quit IRC13:34
*** rmascena has joined #openstack-meeting13:35
*** raildo has quit IRC13:37
*** pchavva has joined #openstack-meeting13:39
*** edleafe- is now known as edleafe13:45
*** gongysh has joined #openstack-meeting13:45
*** SerenaFeng has joined #openstack-meeting13:45
*** yangyapeng has joined #openstack-meeting13:45
*** kiennt26 has quit IRC13:46
*** gongysh has quit IRC13:49
*** psachin has quit IRC13:49
*** eharney has joined #openstack-meeting13:49
*** mriedem1 has joined #openstack-meeting13:52
*** mriedem has quit IRC13:55
*** mriedem1 is now known as mriedem13:56
*** rbowen has joined #openstack-meeting14:00
*** jamesmcarthur has joined #openstack-meeting14:04
*** yangyapeng has quit IRC14:09
*** yangyapeng has joined #openstack-meeting14:09
*** cleong has joined #openstack-meeting14:10
*** yamamoto has joined #openstack-meeting14:10
*** andreas_s has quit IRC14:12
*** armstrong has quit IRC14:14
*** andreas_s has joined #openstack-meeting14:17
*** lhx_ has joined #openstack-meeting14:17
*** yamamoto has quit IRC14:23
*** andreas_s has quit IRC14:26
*** tlam_ has joined #openstack-meeting14:29
*** andreas_s has joined #openstack-meeting14:31
*** yanxingan has quit IRC14:32
*** rbudden has joined #openstack-meeting14:35
*** oidgar has quit IRC14:35
*** cdub has joined #openstack-meeting14:40
*** andreas_s has quit IRC14:41
*** donghao has joined #openstack-meeting14:44
*** donghao has quit IRC14:44
*** donghao has joined #openstack-meeting14:45
*** donghao has quit IRC14:45
*** andreas_s has joined #openstack-meeting14:45
*** donghao has joined #openstack-meeting14:45
*** oidgar has joined #openstack-meeting14:48
*** yanxingan has joined #openstack-meeting14:48
*** msimonin has joined #openstack-meeting14:51
*** gouthamr has joined #openstack-meeting14:51
*** kgiusti has joined #openstack-meeting14:55
*** mriedem is now known as mriedem_away14:57
*** yanxingan has quit IRC14:57
*** ad_rien_ has joined #openstack-meeting14:58
*** Tom-Tom has joined #openstack-meeting14:59
ad_rien_#strartmeeting massively-distributed-clouds15:00
*** pbressan has joined #openstack-meeting15:00
ad_rien_#startmeeting massively-distributed-clouds15:00
openstackMeeting started Wed Dec 20 15:00:56 2017 UTC and is due to finish in 60 minutes.  The chair is ad_rien_. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: massively-distributed-clouds)"15:00
openstackThe meeting name has been set to 'massively_distributed_clouds'15:01
ad_rien_#chair ad_rien_15:01
openstackCurrent chairs: ad_rien_15:01
ad_rien_#topic roll call15:01
*** openstack changes topic to "roll call (Meeting topic: massively-distributed-clouds)"15:01
ad_rien_Hi guys15:01
*** bobh has joined #openstack-meeting15:01
*** avankemp has joined #openstack-meeting15:01
ad_rien_I don't know how many folks will be there today15:02
ad_rien_rcherrueau and dpertin are giving a lecture regarding enos15:02
ad_rien_so anyone else ?15:02
avankempHi everyone15:02
kgiustiansmith is on holiday until 1/215:02
ad_rien_yes… he is right ;)15:03
ad_rien_so let's wait two or three minutes,meanwhile you can give a look to the different links I put on the etherpad15:03
ad_rien_#link Agenda line 163815:04
ad_rien_anyone from the dragonflow team?15:05
*** SerenaFeng has quit IRC15:05
*** awaugama has joined #openstack-meeting15:05
ad_rien_so let's start15:06
ad_rien_#topic news15:06
*** openstack changes topic to "news (Meeting topic: massively-distributed-clouds)"15:06
*** marst has joined #openstack-meeting15:06
oansonSorry I'm late15:06
msimoninHi oanson15:07
*** SerenaFeng has joined #openstack-meeting15:07
ad_rien_1./ regarding the telcos organized by the foundation, I think we have an interesting session where we discuss some scenarios regarding possible edge use-cases15:07
ad_rien_I believe we will consolidate this list by begining of January15:07
*** makowals has quit IRC15:08
ad_rien_You can give it a look (amend and complete it I guess)15:08
msimoninwhich link is it ?15:08
ad_rien_the other link is related to a template related to the use-case. Since parus is not there today, I propose to skip that point15:09
*** Tom-Tom has quit IRC15:10
*** niraj_singh has quit IRC15:10
ad_rien_Then there is another interesting post that has been made by Matt Riedmann15:10
*** Tom-Tom has joined #openstack-meeting15:10
ad_rien_regarding the use of CellV2 concepts to deal with edge infrastructures15:10
*** niraj_singh has joined #openstack-meeting15:11
ad_rien_I would have appreciated to reply but unfortunately I cannot see the post anymore (stupid click on the report instead of forward :()15:11
ad_rien_If someone knows how I can rollback such an action, please let me know15:11
ad_rien_Meanwhile, could you please tell me whether you can access it?15:11
msimoninI can't but maybe other can, I'm not linkedin friendly15:12
*** niraj_singh has quit IRC15:12
ad_rien_if others can see it, then I will manage from my side sorry ;)15:13
ad_rien_so let's go ahead15:13
ad_rien_Last but not the least, I should send informations regarding edge sessions during the next PTG.15:14
*** liuyulong has quit IRC15:14
ad_rien_Could you please confirm that you will attend/by interested to take part to some discussions in Dublin15:15
ad_rien_if yes, please update the etherpad15:15
*** niraj_singh has joined #openstack-meeting15:15
msimoninIs this epad related to the PTG ?15:16
ad_rien_kgiusti:  you told me that you should be in Dublin with Andy ?15:16
kgiustiad_rien_: yes - we're confirmed and on that epad15:17
ad_rien_#link line 21, PTG attendees15:17
kgiustiline 24 :)15:17
ad_rien_so that's all from my side regarding the news15:18
ad_rien_anythings else from your side?15:19
*** esberglu has joined #openstack-meeting15:20
*** oidgar has quit IRC15:20
ad_rien_@msimonin can you please share some information regarding the performance WG?15:20
ad_rien_before moving to the next topic?15:20
ad_rien_msimonin: ?15:21
ad_rien_still there :-P15:21
msimoninDo you have somethiong in mind ?15:21
ad_rien_are there new concrete actions ?15:21
ad_rien_(a part from the AMQP evaluations you are doing guys)15:21
ad_rien_for instance, around the cell V2?15:21
msimoninActually, well, no15:22
ad_rien_ok thanks :D15:22
ad_rien_#topic ongoing-actions: use-cases15:23
*** openstack changes topic to "ongoing-actions: use-cases (Meeting topic: massively-distributed-clouds)"15:23
*** yamamoto has joined #openstack-meeting15:23
ad_rien_ok I think we can  skip that one15:23
ad_rien_parus is not there and I didn't see any folks from FBK15:23
ad_rien_Can I move to the next topic?15:24
ad_rien_#topic ongoing-actions: amqp15:24
*** openstack changes topic to "ongoing-actions: amqp (Meeting topic: massively-distributed-clouds)"15:24
ad_rien_So msimonin kgiusti please15:24
kgiustiSo we've been meeting weekly to discuss the oslo.messaging testing15:25
kgiustiLast we talked msimonin and avankemp were still testing small distributions under rabbit15:25
kgiustiWe're getting together tomorrow for an update.15:26
ad_rien_ok thanks15:27
kgiustimsimonin: avankemp anything I missed?15:27
msimoninThat's perfect :)15:27
avankempnop, maybe I can just add that we're scaling the experiments now to thousands of agents15:27
ad_rien_msimonin:  you put a couple of questions on the etherpad. Do you want to go through please?15:28
msimoninoh yes sure15:28
msimoninespecially if we have kgiusti and oanson15:28
msimoninit's related to oslo.messaging and dragonflow15:29
*** Apoorva has joined #openstack-meeting15:29
msimoninlast time oanson told us that the pub/sub implementation of dragonflow was plugable15:29
msimoninbut there was no plugin for oslo.messaging15:30
oansonI was just reading through the question in the agenda.15:30
oansonI don't know oslo.messaging too well15:30
kgiustiI don't believe I've worked with dragonflow - is there a good website describing it?15:30
kgiusti(save me the google fu)15:30
oansonWe have a blog, but mostly it's just us for now :)15:30
msimonin(you should use qwant :) )15:30
oansonEspecially for technical details15:30
kgiustioanson: I recommend you keep it that way.15:30
kgiustioanson: oslo.messaging that is ;)15:30
kgiustiSo from the epad is the Q if an oslo.messaging plug in to dragonflow available?15:31
kgiustiNot that I'm aware of.15:31
oansonCurrently there's no oslo.messaging driver.15:31
oansonIt would be a great contribution, but we don't have the resources to do it. Especially since we have 2-3 other drivers already working well15:32
msimoninthe point is what would be missing in oslo messaging (or not)15:32
kgiustimsimonin: in terms of dragonflow messaging requirements?15:32
oansonI doubt there's anything missing. Dragonflow only needs a way to send a message, be notified when a message is received15:32
kgiustimsimonin: like topic subscriptions?15:32
msimoninI don't know if line 1665 to l1667 are clear enough for example15:32
oansonThere is also the ability to subscribe to topics15:32
msimoninare those topics dynamics ?15:33
oansonCurrently we have a global topic that every one registers to. And a topic per tenant/project15:33
msimonindo you have a topic per sec-group for example ?15:33
oansonNot currently.15:33
msimoninthat an agent would subscribe to if needed15:34
oansonBut our agent is an all-or-nothing15:34
msimoninah ?15:34
msimoninwhat do you mean ?15:34
oansonWe have a single agent that does everything:15:34
oansonThe Dragonflow controller runs on each compute node.15:34
oansonIt connects to the OVS switch, and implements everything it can through that15:35
*** yamamoto has quit IRC15:35
oansonWhat it does is defined by the applications that were loaded15:35
oansonSo the Dragonflow controller (our single agent) subscribes (using the pub/sub mechanism) to events according to specific tenants/projects15:35
oansonIf selective proactive is enabled, only the tenants installed on it (i.e. ports bound to this node). Otherwise, it subscribes to everything.15:36
oansonmsimonin, this was a bit long. Does it answer your question?15:36
msimoninIf a sec-group is modified, are all the agents notified ?15:37
oansonIn general, yes15:37
msimonineven if they aren't interrested in this secgroup15:37
oansonBasically, we can filter this on the tenant level - if the node doesn't have any tenant ports installed, it won't get the event.15:37
msimoninso in a massively distributed clouds this would make a big multicast ?15:38
oansonBut all nodes with ports belonging to the tenant (or project) will get the event15:38
oansonWe trust the publish subscribe mechanism to be light enough.15:38
msimoninand reliable enough ?15:39
oansonNo. We verify we're up-to-date by syncing with the database15:40
oansonI think the sync time is configurable15:40
msimoninif an agent miss some messages, it detects it and resync with the db ?15:40
*** trozet has quit IRC15:40
msimoninI think this would be a good exercice to check if oslo messaging could be a plugin.15:41
kgiustioanson: msimonin: I can do that15:41
oansonThat would be great!15:42
kgiustihopefully by next meeting, but no promises (will *try* to limit the egg nog)15:42
msimoninkgiusti: if there anything I can do to help ?15:42
oansonkgiusti, I am available for any help you need15:42
ad_rien_I've been preempted15:42
*** slaweq has quit IRC15:43
msimoninI'm interesting in the topic and this sounds related to the experiments we are planning to do15:43
kgiustimsimonin: did you want to do the evaluation?  I didn't mean to rush in15:43
msimoninregarding the massively distributed RPCs15:43
*** trozet has joined #openstack-meeting15:43
ad_rien_Guys may I ask you to take some notes on the pad just to have an overview of what you discuss? races for the other15:43
ad_rien_s/race for the other/ /15:43
kgiustiad_rien_: yep - happy holidays + new year to you!15:44
msimoninkgiusti: not I'm interested but since I don't know at all the oslo_messaging internals I don't think I am the best candidate15:44
*** armax has joined #openstack-meeting15:44
kgiustimsimonin: let me take a quick pass through then we can plan work if that is the next logical step.15:44
*** iyamahat has joined #openstack-meeting15:44
msimoninkgiusti: ack :)15:44
ad_rien_(kgiusti I'm back now, have been preempted for the last couple of minutes)15:45
*** iyamahat has quit IRC15:45
ad_rien_Can we move to the other topic15:45
msimoninshould we put an action ?15:45
kgiustioanson: if you can send me some pointers where I can start ramp up on dragonflow + drivers ( that'd be great15:45
*** iyamahat has joined #openstack-meeting15:45
kgiustimsimonin: I'll do that15:45
oansonkgiusti, sure. I'll do that!15:45
ad_rien_Actually, I would like to start preparing the PGT meeting as I think it is important to come with foods for core-devs discussions15:46
kgiustigo for it - I'm all set!15:46
ad_rien_can we switch or you have a last point to discuss ?15:46
kgiustiswitch ok!15:47
*** avankemp has quit IRC15:47
*** shu-mutou has quit IRC15:47
*** keiko has quit IRC15:47
msimonin(oanson, kgiusti could you cc me at some point, I'll try to learn)15:47
ad_rien_oanson:  msimonin ok for you too?15:47
ad_rien_So I propose to jump over the two last items regarding the on-going actions as we did not make significant progress and I propose to discuss the PTG topic ;)15:48
ad_rien_#topic PTG-Preparation15:48
*** openstack changes topic to "PTG-Preparation (Meeting topic: massively-distributed-clouds)"15:48
ad_rien_so my goal is to try to prepare as much as possible the PTG15:49
*** eharney has quit IRC15:49
ad_rien_I would like to propose to work in subgroups15:49
msimoninWhat will be the format ?15:49
ad_rien_in order to collect as much as possible informations regarding the code base15:49
*** yanxingan has joined #openstack-meeting15:49
ad_rien_format will be the one we want to have15:49
ad_rien_I think there will be at least one sessions regarding the use-cases15:50
msimoninOh :)15:50
ad_rien_but because I know that we can discuss about use-cases during three days without diving into details15:50
ad_rien_I think it is important to come with more concrete stuffs15:50
ad_rien_for instance an etherpad with three identified use-cases15:50
ad_rien_and then conduct a gap analysis of the current code-base w.r.t. these use-cases15:51
ad_rien_So If we can define some milestones just to help us to move forward and be sure we will have enough materials before the PTG15:51
ad_rien_I think it would be great15:51
ad_rien_right now we have one use-case15:51
*** pcaruana has joined #openstack-meeting15:51
ad_rien_i.e. control plane is centralized and we have remote nodes15:52
*** donghao has quit IRC15:52
ad_rien_we can also think about using the cells15:52
ad_rien_what are the pros/cons of such an approcha?15:52
ad_rien_using the regions what are the pros/cons15:52
ad_rien_for each try to see whether we need additional piece of code15:52
ad_rien_of if we can just revise the current code bas15:53
ad_rien_or if we should really fork the code in order to propose another implementation/alternative of a particular service15:53
*** coolsvap has joined #openstack-meeting15:53
ad_rien_(e.g. DragonFlow in comparison to the vanilla neutron implementation).15:53
*** janki has quit IRC15:53
ad_rien_so far so good?15:53
ad_rien_Any remarks/other ideas ?15:53
*** felipemonteiro has joined #openstack-meeting15:54
ad_rien_no remark :-P ?15:55
msimoninUsage of pub/sub in the context of massively distributed deployment ?15:55
msimonin(I'm biased)15:55
ad_rien_from my view point this is interesting but probably a bit too specific15:55
ad_rien_The goal from my viewpoint is to be able to discuss with the core developpers15:55
ad_rien_core developpers will be focused on the code base15:55
ad_rien_if we arrive with ''just'' another solution without any strong arguments against the current code base, I think our viewpoints will not be considered?15:56
ad_rien_but it can be a topic indeed15:56
ad_rien_How can core-services can communicate WANWide with intermittent network connectivity15:56
ad_rien_Can you add it into the pad15:56
*** ricolin_ has joined #openstack-meeting15:57
ad_rien_anything else ?15:57
ad_rien_Two minutes left ?15:57
msimoninIMHO the dragonflow implementations are interresting15:57
ad_rien_oanson:  maybe you would like to discuss network aspects15:57
ad_rien_exactly ;)15:57
ad_rien_thanks msimonin15:57
*** jamesmcarthur has quit IRC15:57
ad_rien_but the same we need to come with some materials15:57
oansonad_rien_, sure.15:58
ad_rien_so if dragonflow folks are interested and have time to prepare a bit15:58
ad_rien_it would be nice15:58
*** jamesmcarthur has joined #openstack-meeting15:58
*** guhcampos has quit IRC15:58
oansonDefinitely. We'll see what we can come up with.15:58
ad_rien_I know that the neutron team is planning to impement a cell like concept within the neutron code15:58
ad_rien_ok thanks guy15:58
ad_rien_please put some notes into the pad15:58
ad_rien_nothing else from my side15:58
ad_rien_I wish you a merry christmas15:58
msimoninThanks ad_rien_ ! You too15:59
ad_rien_and all the best for the two next weeks !15:59
oansonThanks! You too.15:59
*** openstack changes topic to "OpenStack Meetings ||"15:59
openstackMeeting ended Wed Dec 20 15:59:27 2017 UTC.  Information about MeetBot at . (v 0.1.4)15:59
openstackMinutes (text):
*** rossella_s has quit IRC15:59
*** ricolin has quit IRC15:59
*** yanxingan has quit IRC16:00
*** pbressan has quit IRC16:00
jungleboyj#startmeeting cinder16:00
openstackMeeting started Wed Dec 20 16:00:18 2017 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
*** yanxingan has joined #openstack-meeting16:00
jungleboyjcourtesy ping:  jungleboyj DuncanT diablo_rojo, diablo_rojo_phon, rajinir tbarron xyang xyang1 e0ne gouthamr thingee erlon patrickeast tommylikehu eharney geguileo smcginnis lhx_ lhx__ aspiers jgriffith moshele hwalsh felipemonteiro16:00
_pewp_jungleboyj (^▽^)/ ʸᵉᔆᵎ16:01
*** msimonin has quit IRC16:01
jungleboyjHey tbarron16:01
*** markstur has joined #openstack-meeting16:01
*** avankemp has joined #openstack-meeting16:02
*** walshh2 has joined #openstack-meeting16:02
*** shu-mutou has joined #openstack-meeting16:02
*** keiko has joined #openstack-meeting16:02
*** changes topic to "ongoing-actions: amqp (Meeting topic: massively-distributed-clouds)"16:02
*** walshh2 has quit IRC16:02
*** walshh2 has joined #openstack-meeting16:02
*** avankemp has quit IRC16:02
*** avankemp has joined #openstack-meeting16:02
*** walshh has joined #openstack-meeting16:02
*** jamesmca_ has joined #openstack-meeting16:02
jungleboyjGive people another minute to get here.16:02
*** jamesmcarthur has quit IRC16:02
*** Guest37178 is now known as geguileo16:02
jungleboyje0ne:  Thanks!16:03
jungleboyjWaiting for smcginnis  since he has a topic on there.16:03
*** rossella_s has joined #openstack-meeting16:03
jungleboyjsmcginnis:  Yay! and I guess Gorka is just a Guest now.16:04
*** walshh2 has quit IRC16:04
* smcginnis tries to remember what I wanted to talk about16:04
jungleboyjOk, so we might as well get started.16:05
jungleboyj#topic announcements16:05
*** openstack changes topic to "announcements (Meeting topic: cinder)"16:05
jungleboyjI haven't seen too many reviews added to the tracking etherpad.16:05
jungleboyjPlease take some time to do that if you can please.16:05
jungleboyjWith Queens-2 passing I have moved all the new driver proposals to a -2 for now.16:06
jungleboyjTrying to get caught up on reviews.  Will keep working on that through Christmas.16:06
*** jamesmca_ has quit IRC16:07
jungleboyj#topic Plan for up-coming meetings16:07
*** openstack changes topic to "Plan for up-coming meetings (Meeting topic: cinder)"16:07
jungleboyjThat leads me to the next topic which is what we want to do about our up-coming meetings.16:07
jungleboyjI know a lot of people are on vacation next week.16:07
jungleboyjWould anyone be opposed to skipping the 12/27 meeting?16:08
smcginnisI'm probably around on Wednesday, but I will be travelling the next two weeks.16:08
smcginnisSkipping sounds good to me.16:08
jungleboyjsmcginnis:  Will you be around on 1/3/18 ?16:09
*** mriedem_away is now known as mriedem16:09
e0newhat about meeting on Jan, 3rd?16:09
jungleboyjYeah, that was the next question e0ne16:09
smcginnisjungleboyj: That one is less likely for me. I think I will be in Portland.16:09
*** SerenaFeng has quit IRC16:09
*** jamesmcarthur has joined #openstack-meeting16:09
*** msimonin has joined #openstack-meeting16:09
jungleboyjsmcginnis:  Ok, I am going to be in workshops in RTP and am not sure that I will be able to run the meeting.16:10
*** yanxingan has quit IRC16:10
smcginnisjungleboyj: We can skip two weeks.16:10
jungleboyjThe agendas have been pretty light.16:10
smcginnisjungleboyj: Or have a quick one next week for those around, then skip the next one.16:10
*** yanxingan has joined #openstack-meeting16:10
smcginnisI'd be fine skipping two.16:10
ildikovI don't think too much is going to happen during these two weeks16:10
smcginnisWe can always bring up issues in channel.16:10
jungleboyjildikov:  True.16:10
tommylikehusmcginnis:  that's true16:11
smcginnisildikov: You don't think multiattach will land in the next two weeks? :)16:11
jungleboyjHe he he.16:11
jungleboyjWe can dream.16:11
e0neany options are good for me16:11
ildikovWe should get the multiattach spec landed though but I believe jgriffith needs to update it first16:11
smcginnisildikov: Good point.16:11
jungleboyjildikov:  Right.  I have been wanting to merge it.  Not sure if it has been updated.  I need to look at that.16:11
ildikovsmcginnis: I will be already happy if the spec does...16:12
jungleboyjLets move that to Open Discussion.16:12
jungleboyjSo, I think we have landed on skip two weeks.16:12
jungleboyj#agreed Skip 12/27 and 1/3/18 .16:13
jungleboyj#action jungleboyj to send an e-mail to the mailing list.16:13
*** avankemp has quit IRC16:13
ildikovIt looks like we want to skip those days :)16:13
jungleboyjOkie dokie.16:14
jungleboyj#topic LVM Extend Issues16:14
*** openstack changes topic to "LVM Extend Issues (Meeting topic: cinder)"16:14
smcginnis#link Extend bug report16:14
openstackLaunchpad bug 1731984 in Cinder "LVM: iSCSI tgts not refreshed after volume extend" [Undecided,New]16:14
smcginnisSo I was doing some bug triaging the last few days and came across this.16:14
*** cdub has quit IRC16:15
jungleboyjsmcginnis:  Thank you.16:15
smcginnisAnd I'm not sure if it's valid or not, so I wanted to get it out to more folks that might have some experience there.16:15
smcginnisIt surprised my a bit, because I thought we had tests for this that are passing with LVM.16:15
smcginnisSo checking to see if anyone knows anything about the need to refresh iSCSI targets after extending a volume.16:15
*** cdub has joined #openstack-meeting16:16
jungleboyjsmcginnis:  Is this talking about on the host or in the VM?16:16
smcginnisjungleboyj: I believe it's on the host exposing the LV.16:17
smcginnisAnd the iSCSI targets it presents.16:17
jungleboyjOh ....16:17
smcginnisThe paste included in the bug seems to indicate a difference, but not sure if that's really what the nova host sees.16:17
jungleboyjYeah, I see that now.16:17
smcginnisThough maybe I'm wrong about having test coverage here. I should double check that.16:18
*** andreas_s has quit IRC16:18
jungleboyjI am not totally sure that we do.16:18
smcginnisIf no one has any background on this, that's OK. Just thought I would raise it in case someone knew something about it.16:18
smcginnisSeems easy enough to add the call they mention in the bug.16:18
jungleboyjsmcginnis:  It sounds like it may be a valid but.  I think with the extend in-use we had thought that there might be a driver impact and it just didn't get followed up upon.16:20
*** yanxingan has quit IRC16:20
jungleboyjNo one is jumping up and down with input.16:20
smcginnisjungleboyj: Yeah, I suppose. We can move on. Doesn't sound like anyone knows this bit. :)16:20
*** yanxingan has joined #openstack-meeting16:20
jungleboyjsmcginnis:  I would think that eharney or hemna might have input.16:21
*** edmondsw has joined #openstack-meeting16:21
jungleboyjThey seem to know something about iSCSI.  :-)16:21
smcginnisMaybe they'll chime in later.16:21
jungleboyjsmcginnis:  Are you going to follow through with the bug then?16:21
smcginnisjungleboyj: If no one else grabs it before me I can. Need to wrap up a couple other things first.16:22
jungleboyjOk ... sounds good.16:22
*** felipemonteiro_ has joined #openstack-meeting16:22
jungleboyj#topic Open Discussion16:22
*** openstack changes topic to "Open Discussion (Meeting topic: cinder)"16:22
*** andreas_s has joined #openstack-meeting16:22
jungleboyjildikov: smcginnis jgriffith  Ok, back to the multi-attach spec16:23
*** iyamahat has quit IRC16:24
smcginnis#link Multiattach spec16:24
*** felipemonteiro_ has quit IRC16:24
jungleboyjsmcginnis:  Thank you, was just trying to find that.16:24
*** felipemonteiro_ has joined #openstack-meeting16:24
ildikovIt's still set to WIP16:25
*** yanxingan has quit IRC16:25
jungleboyjSo it looks like we need John to update it.16:25
*** yanxingan has joined #openstack-meeting16:25
*** edmondsw has quit IRC16:26
ildikovI think we're mainly in an agreement on the points though, so maybe on the meeting tomorrow the latest someone can update it if jgriffith will not do it by then16:26
smcginnisGood plan.16:26
*** felipemonteiro has quit IRC16:26
jungleboyjAgreed.  I will review before tomorrow's meeting.  If we are all in agreement and if John can't get to it I can do an update.16:26
ildikovok, we can stick with that then as I guess one day doesn't count by now16:27
ildikovjungleboyj: sounds good, thanks16:27
*** Exhar has quit IRC16:27
jungleboyj#agreed Finish up review at 12/21 meeting and jungleboyj will update the spec if jgriffith is unavailable.16:28
jungleboyjDo we agree we need to get that in before the holiday?16:28
smcginnisWould be good to have that done.16:29
jungleboyj#agreed Should merge the spec before the holiday break.16:29
ildikovwe need to set the base for code changes16:29
ildikovand jgriffith said we shouldn't have too much up before having the spec merged16:29
jungleboyjildikov:  Thanks for bringing that up.16:29
*** ricolin_ has quit IRC16:30
jungleboyjSo we have a plan there.16:30
ildikovand as I need to make my hands dirty here as well and I'm slow the earliest we could have it land the better16:30
*** erlon has joined #openstack-meeting16:30
jungleboyj:-)  Yeah.  Really want to get that done.16:30
jungleboyjAny other topics for today?16:31
smcginnisYeah, I have one more...16:31
jungleboyjsmcginnis:  Go ahead sir.16:31
smcginnisSo cinder repo reviews are... what they are. But also wanted to point out we have os-brick, python-cinderclient, python-brick-cinderclient-ext, and now cinder-tempest-plugin.16:32
*** andreas_s has quit IRC16:32
smcginnisWe need reviews on those patches as well.16:32
smcginnisThere's not a ton out there, but they haven't been getting much attention lately.16:32
smcginnisThat's it, just wanted to give that public service announcement.16:32
jungleboyjsmcginnis: Thank you.  Good point.16:33
jungleboyjsmcginnis:  I need to add cinder-tempest-plugin to my list of things I get e-mail for.16:33
* jungleboyj also needs to clean out my review inbox.16:34
*** kgiusti has left #openstack-meeting16:34
smcginnisOh, on that point too, make sure we don't add any more tempest tests to the cinder repo. They should be going in the new repo now.16:34
smcginnisI have a patch to remove the cinder tests, but I think that's still out there.16:35
*** Exhar has joined #openstack-meeting16:35
jungleboyjsmcginnis:  If you point me to that patch we can try to get it through.16:35
* jungleboyj waits for smcginnis to think of something else...16:36
smcginnisjungleboyj: Nothing else from me.16:36
*** sridharg has quit IRC16:37
jungleboyj:-)  Ok.  Then I think we can wrap the meeting up.16:37
e0nehave a good holidays!16:37
jungleboyjI wish everyone a Merry Christmas and a safe and Happy New Year!16:37
smcginnis#link Tempest removal16:37
jungleboyjLook forward to continuing to work with everyone in the new year!16:37
jungleboyjsmcginnis:  Thank you.16:38
_pewp_jungleboyj ヽ(´・ω・`)、16:38
*** openstack changes topic to "OpenStack Meetings ||"16:38
openstackMeeting ended Wed Dec 20 16:38:28 2017 UTC.  Information about MeetBot at . (v 0.1.4)16:38
openstackMinutes (text):
*** walshh has quit IRC16:43
*** links has quit IRC16:44
*** joe_w has quit IRC16:47
*** e0ne has quit IRC16:49
*** gibi is now known as gibi_away16:50
*** andreas_s has joined #openstack-meeting16:50
*** lhx_ has quit IRC16:50
*** chyka has joined #openstack-meeting16:50
*** Alex_Staf_ has quit IRC16:51
*** yanxingan has quit IRC16:52
*** andreas_s has quit IRC16:55
*** aselius has joined #openstack-meeting16:56
*** marios has quit IRC16:57
*** rajulk has joined #openstack-meeting16:57
*** anilvenkata has quit IRC16:58
*** ijw has joined #openstack-meeting16:59
*** gyee has joined #openstack-meeting17:01
*** priteau has joined #openstack-meeting17:04
*** rajulk has quit IRC17:04
*** priteau has quit IRC17:08
*** Tom-Tom has quit IRC17:10
*** iyamahat has joined #openstack-meeting17:14
*** awaugama has quit IRC17:15
*** andreas_s has joined #openstack-meeting17:22
*** dprince has quit IRC17:23
*** d0ugal has quit IRC17:23
*** msimonin has quit IRC17:23
*** Guest46139 has quit IRC17:24
*** Apoorva has quit IRC17:30
*** d0ugal has joined #openstack-meeting17:35
*** andreas_s has quit IRC17:40
*** neiljerram has quit IRC17:42
*** lpetrut has quit IRC17:43
*** neiljerram has joined #openstack-meeting17:44
*** jamesmcarthur has quit IRC17:44
*** andreas_s has joined #openstack-meeting17:45
*** iyamahat has quit IRC17:45
*** yanxingan has joined #openstack-meeting17:47
*** andreas_s has quit IRC17:49
*** rmcall has joined #openstack-meeting17:51
*** bzhao has quit IRC17:52
*** bzhao has joined #openstack-meeting17:53
*** sambetts is now known as sambetts|afk17:53
*** pchavva has quit IRC17:55
*** hemna_ has quit IRC17:56
*** yanxingan has quit IRC17:56
*** iyamahat has joined #openstack-meeting18:00
*** sapd_ has joined #openstack-meeting18:01
*** sapd has quit IRC18:01
*** dprince has joined #openstack-meeting18:03
*** Apoorva has joined #openstack-meeting18:06
*** Apoorva has quit IRC18:06
*** unicell1 has joined #openstack-meeting18:07
*** Apoorva has joined #openstack-meeting18:07
*** unicell has quit IRC18:08
*** neiljerram has quit IRC18:09
*** edmondsw has joined #openstack-meeting18:09
*** makowals has joined #openstack-meeting18:11
*** edmondsw has quit IRC18:13
*** Apoorva has quit IRC18:13
*** e0ne has joined #openstack-meeting18:16
*** yamahata has joined #openstack-meeting18:17
*** rajulk has joined #openstack-meeting18:19
*** Apoorva has joined #openstack-meeting18:19
*** Apoorva has quit IRC18:24
*** niraj_singh has quit IRC18:27
*** awaugama has joined #openstack-meeting18:27
*** jamesmcarthur has joined #openstack-meeting18:28
*** ad_rien_ has quit IRC18:28
*** bbzhao has quit IRC18:31
*** Douhet has quit IRC18:31
*** bbzhao has joined #openstack-meeting18:32
*** jamesmcarthur has quit IRC18:32
*** Apoorva has joined #openstack-meeting18:34
*** unicell1 has quit IRC18:34
*** pchavva has joined #openstack-meeting18:39
*** jamesmcarthur has joined #openstack-meeting18:46
*** niraj_singh has joined #openstack-meeting18:48
*** niraj_singh has quit IRC18:49
*** oidgar has joined #openstack-meeting18:50
*** Tom-Tom has joined #openstack-meeting18:52
*** Tom-Tom has quit IRC18:52
*** ijw has quit IRC18:52
*** niraj_singh has joined #openstack-meeting18:53
*** oidgar has quit IRC18:55
*** niraj_singh has quit IRC18:56
*** niraj_singh has joined #openstack-meeting18:56
*** jamesmcarthur has quit IRC18:57
*** niraj_singh has quit IRC18:59
SotKstoryboard time!18:59
SotK#startmeeting storyboard18:59
openstackMeeting started Wed Dec 20 18:59:57 2017 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:59
*** openstack changes topic to " (Meeting topic: storyboard)"19:00
openstackThe meeting name has been set to 'storyboard'19:00
*** coolsvap has quit IRC19:00
SotK#link Agenda19:00
diablo_rojoHello :)19:00
SotK#topic In Progress Work19:00
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"19:00
SotKhey diablo_rojo :)19:00
*** yanxingan has joined #openstack-meeting19:00
*** Zara has joined #openstack-meeting19:01
SotKso since the last meeting I started working on a patch to implement the ability to link to a partially-filled new story form19:01
Zarao/ my clock is 2 min behind =D19:02
SotKwith support for forcing the created story to be private too19:02
SotK:D welcome19:02
Zarathank you! I have an enormous review backlog now19:02
SotKthat is the current WIP19:02
* fungi is late19:02
diablo_rojoSotK, awesome! Will check it out.19:02
SotKit doesn't actually work fully yet, I've not had much chance to improve it since last week19:03
* SotK suddenly remembered that christmas is a thing that needs preparation19:03
fungii got to thinking about the implementation there, and i feel like it's not only a big piece of the vmt and docs need, but also goes a long way towards the more general bug reporting solution i've been hearing everyone say they want19:03
*** ad_rien_ has joined #openstack-meeting19:04
SotKyeah, I'm hopeful it will be helpful for that19:04
SotKsince it'll allow people to create links with project-specific "bug templates" for example19:05
*** unicell has joined #openstack-meeting19:05
fungiif nothing else, i think some careful application of custom reporting urls solves the "i want to report a bug, not a story" confusion19:06
*** unicell1 has joined #openstack-meeting19:06
Zaraor even 'I want to make a bug' :D19:06
fungithough i really liked in the infra meeting yesterday when jeblair said (paraphrasing because i don't feel like looking it back up) "a bug is just a sad story"19:06
fungior maybe that was in the zuul meeting19:07
* fungi has pre-holiday brain fog19:07
persiaI think that was infra: I think it's true, but helping folk understand that by providing custom forms is likely to be a good thng.19:07
ZaraI only realised today that I'd lost my connection to #openstack-meeting19:07
ZaraI thought it was quiet19:07
diablo_rojoAgreed. Comically difficult for people to understand that bugs and new features are both just code changes.19:08
* fungi has been trying to refer to storyboard as "defect and task tracking"19:08
*** jamesmcarthur has joined #openstack-meeting19:09
persiaPerhaps more consumable than "a tool for communicating desire and intent"19:09
*** unicell has quit IRC19:09
fungiwhile most people ultimately need a task tracking system, they're operating under the assumption that what they want is a defect tracking system19:10
Zara!/page/about has our current blurb fwiw19:10
*** yanxingan has quit IRC19:10
Zarait mentions bugs as a subset of stories19:10
Zarawell, bug reports19:10
fungioh, thanks! i'd forgotten that existed. i'll try to remember to link it more often19:10
Zarait should be the page that comes up by default when someone navigates to sb but isn't logged in iirc19:11
SotKit is :)19:11
Zaraso that new users know what is19:11
*** oidgar has joined #openstack-meeting19:11
fungiexcellent. i just never see it because i'm always following deeper links into teh webclient19:11
Zarayeah, I had to dig to remember what it said on there, but it looks like it's up to date :)19:12
*** oidgar has quit IRC19:13
*** salv-orl_ has quit IRC19:14
SotKin terms of other things we have on the go, there is the patch I sent to switch to a markdown renderer that is actually maintained19:14
SotKit'd be good to get that merged in some form19:14
*** salv-orlando has joined #openstack-meeting19:14
*** yanxingan has joined #openstack-meeting19:15
* diablo_rojo puts reviews on my list today19:15
* diablo_rojo puts reviews on her list today19:15
*** makowals has quit IRC19:15
fungidiablo_rojo: looks like you already +1'd that one19:16
*** jamesmcarthur has quit IRC19:16
SotKdiablo_rojo has reviewed all of my patches that are ready for review I think19:16
SotKthanks btw :)19:16
fungi+2, looks like a pretty simple change19:16
fungialso note that mordred has pushed up a largeish (i think, haven't looked yet) webclient patch to switch up the framework a bit19:17
SotKyeah, I'm looking forward to trying that out19:17
SotKit'll be good to get our tooling up to date, thanks mordred19:18
fungimaybe he'll reciprocate with some reviewing other webclient changes19:18
diablo_rojoOh sweet. Then I am actually kind of on top of things.19:18
*** salv-orlando has quit IRC19:19
SotKhave there been any developments in the launchpad migration since last meeting?19:20
*** bobh has quit IRC19:20
Zara(thanks for the links. I'm the one slowing down reviews atm I think.)19:21
Zara(have had holidays and things, am around more now)19:21
fungii haven't migrated anyone new, not sure what updates diablo_rojo has on discussions to that effect for upcoming candidates19:21
SotKZara: whilst you're looking, there is also and of mine that are waiting on reviews :)19:22
Zaratonight with any luck19:23
Zaramaybe won't get to everything but do want that markdown parser change in asap19:23
*** yanxingan has quit IRC19:25
mordredfungi, SotK: oh - there will be more to come - that one is just the beginning ... I figure starting small is best :)19:26
*** jamesmcarthur has joined #openstack-meeting19:26
SotKexcellent :D19:26
fungiit'll be nice to modernize, thanks again mordred!19:26
persiamordred: 5K lines is small?19:26
mordredpersia: in this case - yes19:27
fungiat least most of that is generated code19:27
fungiyay javascript19:28
mordredpersia: (the yarn.lock is an auto-generated file - package.json is where the important bits are)19:28
persiaNearly all of it: the actual patch is mostly deleting stuff that shouldn't be used anymore, with a couple minor adjustments in pathnames as a result.19:28
*** felipemonteiro__ has joined #openstack-meeting19:28
*** msimonin has joined #openstack-meeting19:28
*** bobh has joined #openstack-meeting19:28
*** pcaruana has quit IRC19:29
mordredyah. I now noticed you left a review comment/question - I should go respond to that ... but tl;dr  - yes, for applications such as storyboard-webclient the lock file is recommended to be committed19:29
*** oidgar has joined #openstack-meeting19:29
mordredperhaps I should rebase it on top of the marked patch?19:30
*** oidgar has quit IRC19:30
SotKthat would be ideal, thanks19:31
persiaDepends on the review order: the marked patch is
*** felipemonteiro_ has quit IRC19:32
*** ijw has joined #openstack-meeting19:32
*** bobh has quit IRC19:33
*** bobh has joined #openstack-meeting19:33
SotKanything else in progress?19:35
SotK#topic Discussion19:36
*** openstack changes topic to "Discussion (Meeting topic: storyboard)"19:36
SotKif there is anything else folk want to discuss, go ahead19:36
SotKotherwise I will end the meeting in a few minutes19:36
* fungi has nothing else19:37
*** bobh has quit IRC19:38
* Zara has nothing, I just need to get on with reviews :)19:39
*** msimonin has quit IRC19:40
SotKwell then, thanks for coming everyone!19:40
*** openstack changes topic to "OpenStack Meetings ||"19:40
openstackMeeting ended Wed Dec 20 19:40:21 2017 UTC.  Information about MeetBot at . (v 0.1.4)19:40
openstackMinutes (text):
fungithanks SotK!19:41
Zarathanks! :D19:41
*** ijw has quit IRC19:43
*** ijw has joined #openstack-meeting19:44
*** bobh has joined #openstack-meeting19:44
diablo_rojo_phonThanks SotK !19:45
*** oidgar has joined #openstack-meeting19:47
*** oidgar has quit IRC19:47
*** pcaruana has joined #openstack-meeting19:48
*** bobh has quit IRC19:49
*** ad_rien_ has quit IRC19:54
*** pcaruana has quit IRC19:54
*** bobh has joined #openstack-meeting19:55
*** rm_mobile has joined #openstack-meeting19:56
*** edmondsw has joined #openstack-meeting19:57
*** ijw has quit IRC19:59
*** bobh has quit IRC19:59
*** mkoderer__ has quit IRC20:00
*** dprince has quit IRC20:01
*** ijw has joined #openstack-meeting20:01
*** rajulk has quit IRC20:02
*** edmondsw has quit IRC20:02
*** msimonin has joined #openstack-meeting20:04
*** oidgar has joined #openstack-meeting20:04
*** eharney has joined #openstack-meeting20:04
*** oidgar has quit IRC20:05
*** ijw has quit IRC20:05
*** bobh has joined #openstack-meeting20:05
*** pcaruana has joined #openstack-meeting20:06
*** slaweq_ has joined #openstack-meeting20:06
*** rmascena__ has joined #openstack-meeting20:08
*** rajulk has joined #openstack-meeting20:08
*** rmascena has quit IRC20:10
*** bobh has quit IRC20:10
*** rmascena__ is now known as raildo20:11
*** jamesmcarthur has quit IRC20:11
*** pcaruana has quit IRC20:13
*** bobh has joined #openstack-meeting20:14
*** bobh has quit IRC20:19
*** rm_mobile has quit IRC20:21
*** jamesmcarthur has joined #openstack-meeting20:23
*** ad_rien_ has joined #openstack-meeting20:23
*** bobh has joined #openstack-meeting20:24
*** yangyape_ has joined #openstack-meeting20:25
*** yangyapeng has quit IRC20:26
*** jamesmcarthur has quit IRC20:27
*** bobh has quit IRC20:28
*** unicell1 has quit IRC20:30
*** unicell has joined #openstack-meeting20:30
*** msimonin has quit IRC20:31
*** m_kazuhiro has joined #openstack-meeting20:33
*** unicell has left #openstack-meeting20:35
*** oidgar has joined #openstack-meeting20:35
*** rledisez has joined #openstack-meeting20:38
*** oidgar has quit IRC20:40
*** links has joined #openstack-meeting20:41
*** links has quit IRC20:47
*** chyka has quit IRC20:48
*** timburke has joined #openstack-meeting20:52
*** felipemonteiro_ has joined #openstack-meeting20:53
*** felipemonteiro__ has quit IRC20:53
*** patchbot has joined #openstack-meeting20:53
*** tlam_ has quit IRC20:53
*** tlam_ has joined #openstack-meeting20:54
*** acoles has joined #openstack-meeting20:59
notmyname#startmeeting swift21:00
openstackMeeting started Wed Dec 20 21:00:13 2017 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
*** dprince has joined #openstack-meeting21:00
notmynamewho's here for the swift team meeting?21:00
claygmeeting meeting meeting21:00
claygtdasilva: !!21:00
*** kota_ has joined #openstack-meeting21:01
*** joeljwright has joined #openstack-meeting21:01
*** raildo has quit IRC21:01
*** ijw has joined #openstack-meeting21:01
*** ijw has quit IRC21:02
*** ijw has joined #openstack-meeting21:02
rledisezhi o/21:02
*** torgomatic has joined #openstack-meeting21:02
joeljwrighthello :)21:02
claygrledisez: acoles: torgomatic: joeljwright: !!! everyone is here !!!21:03
* clayg steps out for a bit21:03
notmynamewelcome, everyone21:03
notmynameagenda at21:03
notmynamea few things to review and a new topic from m_kazuhiro21:03
notmynamefirst up, some FYI stuff...21:03
notmyname#topic general stuff21:04
*** openstack changes topic to "general stuff (Meeting topic: swift)"21:04
notmynamepatch 528582 is making its way through the gate21:04
patchbot - swift - Native Zuul v3 tox jobs21:04
*** diablo_rojo has quit IRC21:04
notmynameand in fact it changes the gate21:04
*** priteau has joined #openstack-meeting21:04
notmynameit's the in-repo definition of check and gate jobs for swift21:04
notmynameusing the new zuul v3 stuff21:04
notmynameit's a great improvement because it allows us to define test jobs in our own repo (AIUI, even with ansible scripts to set up an environment, if needed)21:05
notmynamethis first patch is the last step int he old centralized job definition to the new zuul v3 way21:06
claygtdasilva: ^^^ pretty cool huh!?21:06
claygall hail zuul v321:06
tdasilvavery! was thinking we could add libec, probe tests21:06
clayg~ a whole new world ~21:06
notmynamespeaking of probe tests, we all probably noticed by now that the swiftstack community qa cluster has been throwing errors. I've finally burned through enough on my todo list to get to that item21:07
claygburn it down!21:07
notmyname(1) I hope to fix it, of find someone who can (2) some of it may not be needed any more with the zull v3 definitions21:07
notmynameany other general stuff to bring up?21:08
claygoh... i mean fix it... but you COULD burn it down - that would *also* be fun...21:08
notmynameI thought I had something else, but of course I didn't write it down...21:08
timburkei was actually thinking of that wrt to the func tests...21:08
kota_i think, libec and pyeclib are also in progress for zuul v321:08
claygtimburke: yeah burn 'em!21:08
notmynameI heard something about some conference talks being accepted, acoles cschwede, tdasilva21:08
timburkewe should totally get some cross-policy testing happening in the gate though!21:08
acolesnotmyname:  IIRC the community cluster functional test was setup to cover an EC policy which we now have an in process test for21:08
notmynameacoles: ya21:08
claygcschwede: !!!21:09
patchbotpatch 528546 - pyeclib - Convert tox job to native v3 Zuul21:09
*** priteau has quit IRC21:09
*** jamesmcarthur has joined #openstack-meeting21:10
tdasilvathere are two swift talks missing from there right now, but i expect they will be there soon21:10
acolestdasilva: and cschwede assure me they will be there too, otherwise I'll have to drink belgian beer on my own :/21:10
tdasilvaand give 3 talks21:10
timburkekota_: oh man! that makes me so happy that i made a liberasurecode-git tox env for pyeclib...21:11
acolestdasilva: t's swift, same talk 3 times over :)21:11
notmynameacoles: tdasilva: cschwede: that's great :-)21:11
notmynameok, let's move on to the agenda topics21:12
notmyname#topic symlink status21:12
*** openstack changes topic to "symlink status (Meeting topic: swift)"21:12
notmynamepatch 23216221:12
patchbot - swift - Symlink implementation. (MERGED)21:12
notmynameit's merged!21:12
notmyname(what follow-ons are still open?)21:12
patchbotpatch 527583 - swift - functest for symlink + versioned writes21:13
kota_it looks like that it got a merge conflict21:14
acolesnotmyname: - clayg or i need to rebase it21:14
patchbotpatch 527583 - swift - functest for symlink + versioned writes21:14
acolesthe conflict is all my fault, think I fixed a teardown in two patches21:14
notmynameother than the rebase, how's it look?21:14
*** bobh has joined #openstack-meeting21:15
claygbooo `liberasurecode-git tox env`21:15
clayger... booo `The change could not be rebased due to a conflict during merge` even21:15
claygcopy/paste error21:15
claygmerge all the things!21:15
notmynameanything else needed for symlinks follow-on?21:16
acolesclayg: if you dont get there before me i will fix the conflict tomorrow21:16
notmynameclayg: didn't you have a pile of them? did they all get squashed or landed?21:16
*** salv-orlando has joined #openstack-meeting21:16
claygwhat symlink follow-on?  idk... i'd have to work on a list21:16
kota_there ware 5 follow up patches but 4 of them landed already AFAIK21:16
clayga bunch got landed21:16
*** diablo_rojo has joined #openstack-meeting21:16
claygnotmyname: see kota_  is on it - you don't have to worry - i'm not worried21:16
notmynamesounds good!21:17
notmyname#topic SLO data segments21:17
*** openstack changes topic to "SLO data segments (Meeting topic: swift)"21:17
notmynamepatch 36537121:17
patchbot - swift - Add support for data segments to SLO and Segmented...21:17
timburkeoh man, so many. it was great. p 527595 p 528073 p 528072 p 527477 p 52747521:17
patchbot - swift - Add more assertions for Symlink + Copy unit tests (MERGED)21:17
patchbot - swift - add symlink to probetest for reconciler (MERGED)21:17
patchbot - swift - add symlink to container sync default and sample c... (MERGED)21:17
notmynametimburke: looks like you just pushed a patch set21:17
patchbot - swift - Assert X-Newest and X-Backend headers are propagat... (MERGED)21:17
patchbot - swift - Symlink doc clean up (MERGED)21:17
patchbottimburke: don't abuse the patchbot21:18
kota_oh, 6 total and 5 got mreged.21:18
timburkenotmyname: yup. had to fix it up after the name change in 52808121:18
timburkep 52808121:18
patchbot - swift - rename utils function less like stdlib (MERGED)21:18
notmynametimburke: thanks21:18
notmynamejoeljwright: wanna give it a quick look to see if it still resembles what you remember? :-)21:19
joeljwrightI've been keeping an eye on it21:19
timburkegate looks happy -- just waiting on the extra long test21:19
joeljwrightbut I'll give it another look for patchset 4021:19
notmynametimburke: joeljwright: did either of you test the nested SLOs with a recent patch set? when I looked, it looked good, but that was an outstanding question21:19
joeljwrightit's evolved into something really cool thanks to timburke21:19
*** bobh has quit IRC21:20
notmynameyeah, it's a pretty cool feature21:20
notmynameI suspect it will become a commonly-used feature21:20
*** salv-orlando has quit IRC21:20
timburkenotmyname: yeah, there's a func test for that now. look for 'nested-data-manifest'21:20
*** ssathaye has quit IRC21:20
*** ssathaye has joined #openstack-meeting21:21
notmynamesounds good21:21
notmyname#topic s3api work status21:21
joeljwrightI haven't tested since patch 38 or 39, happy to take another look tomorrow21:21
patchbot - openstack-infra/system-config - Added entry for building manuals. (MERGED)21:21
*** openstack changes topic to "s3api work status (Meeting topic: swift)"21:21
notmynamekota_: tdasilva: what's going on here?21:21
timburkettfb on SLOs got you down? inline the first meg! ;-)21:21
notmynametimburke: first 7k ;-)21:21
tdasilvaTBH i haven't had a chance to take a look at s3api for a while, definetely need to back to it :(21:22
notmynameI havne't looked at the s3api feature branch in a bit21:22
notmynamesame for you timburke?21:22
tdasilvalast i was working on merging tests21:22
notmynamekota_: have you spent any time on it lately?21:22
kota_oh, sorry I was left for a bit21:22
tdasilvamerge as in merging trees, not landing new tests21:22
*** slaweq_ has quit IRC21:23
notmynamegot it21:23
kota_I was starting to work on it yesterday21:23
kota_wait a bit21:23
kota_paste the trillo link...21:23
kota_i took 2 of tasks from backlog21:24
patchbotpatch 529238 - swift (feature/s3api) - Add s3api section into docs21:24
patchbotpatch 529268 - swift (feature/s3api) - Avoid global LOGGER instance21:24
kota_and some minor things21:25
notmynamethat's great. thanks for keeping work going on it21:25
claygkota_: is on a roll121:25
kota_hopefully, i expect timburke helps to land. in particular LOGGER one starts to touch a bunch of places21:25
*** rajulk has quit IRC21:26
kota_tdasilva: if you have a patch for functests even if its intermediate, i may help you to cleanup.21:26
tdasilvakota_: that sounds great, i'll try to propose as a WIP21:26
timburkeyeah, i'll be sure to help review when i can21:27
notmynameyay team swift :-)21:27
kota_that's all from me for s3api21:27
notmyname#topic general task queue21:27
*** openstack changes topic to "general task queue (Meeting topic: swift)"21:27
notmynamem_kazuhiro: this is what you've been working on21:27
clayggeneral task queue!!!21:27
patchbotpatch 517389 - swift - WIP: Update object expirer to use general task que...21:28
m_kazuhiroThis is updating work for expirer's task queue and this is next work for auto-tiering.21:28
notmynamem_kazuhiro: and you've been working with rledisez and mattoliverau(?) on it?21:28
m_kazuhironotmyname: yes.21:28
notmynamehow's work going?21:29
claygrledisez: is all about it21:29
rlediseztotally :)21:29
m_kazuhiroI implemented main code for that. But I want to discuss some topics about it.21:29
claygm_kazuhiro: do you have your tickets booked for PTG?21:30
m_kazuhiroclayg: I'm going to get tickets now.21:30
* clayg is just asking - he hasn't booked his travel either - but I think other people have started doing so21:30
tdasilvam_kazuhiro: great good doc21:31
m_kazuhirothe great doc is made by mattoliverau !!21:31
* tdasilva high fives mattoliverau 21:32
rledisez+1 very good summary of discussion we had in sidney21:32
notmynameis there a particular question that we need to discuss in this meeting?21:33
notmynamelooks like it will be a very good topic in dublin21:33
tdasilvaRomain Expirer Algorithm21:34
*** bobh has joined #openstack-meeting21:34
*** rajulk has joined #openstack-meeting21:34
tdasilvayay, swift finally has named an algorithm21:34
claygneat idea to use partitions to break up work...21:34
m_kazuhiroToday's main discussion topic is in end of the google doc.21:35
m_kazuhiro"Known problems"21:35
*** bnemec has quit IRC21:36
claygm_kazuhiro: can you restate that problem - i don't understand it in that context... I read something about a migration?  maybe taking the old containers and backfilling into the new per-partition containers?21:36
rledisezbasically, if every objects server fetch a different account for object-expiring tasks, what about the legacy tasks. all objects servers will fetch the same account. if you have a lot of object server, it's a DDoS of the account server21:37
rledisezmigration could be difficult path if you have hundreds of millions of tasks21:37
claygrledisez: i agree - i'd rather now have to translate the rows21:38
torgomaticshard the migration work with the new queue system21:38
m_kazuhirorledisez: Thanks21:38
*** cleong has quit IRC21:38
torgomatic(half serious :) )21:38
*** rmcall has quit IRC21:38
*** bobh has quit IRC21:38
claygrledisez: how many object-expirier's do you currently run?  You're worried about a bunch of account GETs ... i... I'm not sure I'm scared... once it's in the page cache... I'm not sure21:39
clayglike... what... 10K requests?  meh..21:39
timburkecould we have some config option that says "continue pulling work from the old location, but write new work down in two places" then later flip it to "pull work from new place (and only write down new work in one place)"?21:39
rledisez10K requests, every minutes ?21:39
rledisezthat's a lot, I already killed a cluster that way21:39
tdasilvatimburke: i was about to propose something like object-expirer221:40
rledisezi was thinking of something based on the device id and current day. a process would fetch task if day % device_id == 0 not that great, but it would limit the concurrency on legacy account21:40
rledisezwell, it's actually a very bad ideai, forget it :)21:42
*** bobh has joined #openstack-meeting21:42
m_kazuhiroI got an idea about that from kota_... and I think it is great. The idea is that expirer has "check_legacy_queue" boolean configure. We can controll expirer count which checks legacy queue with the value.21:43
notmynamem_kazuhiro: does that answer help you move forward for now?21:44
rledisezi'd rather have something the operator does not need to think about. if the operator forget that new param, the feature is broken. doesn't feel nice. but as we require that the operator run object-expirer on object-server, it might be OK I guess21:44
m_kazuhironotmyname: Yes. I can move forward with the answer. But I want to get opinions about the idea.21:46
*** ykatabam has joined #openstack-meeting21:46
*** yanxingan has joined #openstack-meeting21:46
claygrledisez: so you HAVE deployed enough object-expirers that the container server's holding the .expiring_objects account were not happy with the current amount of listings?  I don't think i've ever had that problem.21:46
clayger... account servers or account/container servers21:47
rledisezclayg: it was not object-expirer, but an other internal process working pretty much the same way AFAIR21:47
claygI've seen specific expiring_object/<timeslice> *containers* get busy (but that's because they're eating row updates)21:47
*** bobh has quit IRC21:47
claygand that part at least has been better since the RAX guys did the thing to make 100 containers for every timeslice or however dfg wrote it21:48
rledisezmaybe i should do an other test on our biggest cluster to see how it behave now21:48
timburkei feel like i must be missing something... probably need to read about it more. but the migration path for inherently ephemeral data seems like it shouldn't be a stumbling block. is it that we're changing the cardinality of workers?21:48
claygdoes the new design have a bunch of accounts?  I thought it was account-per-task so I don't quite follow how the load at the account layer is reduced ... and I'm not sure how many GETs on account would need to happen before I'd be concerned...21:49
rledisezclayg: account per $task-$ring-$partition_number21:50
claygI mean... i think we can write these processes to be pretty nice to swift - and we'll only have as many clients as nodes.. and there's probably more external clients than internal nodes...21:50
claygORLY!?  ok then...21:50
*** ijw has quit IRC21:50
*** priteau has joined #openstack-meeting21:51
claygok, yeah I minunderstood the diagram - the indentation is account -> container -> object - gotcha21:51
claygok cool!21:51
torgomaticas long as we don't wind up with some Kafka-esque rules for how our queue system works, things should be fine21:51
notmynamem_kazuhiro: thanks for bringing this topic up. it's a good question21:52
*** tlam_ has quit IRC21:53
*** bobh has joined #openstack-meeting21:53
notmynameto everyone, where's the best place to keep discussing it? in -swift? or something else like the google doc?21:53
*** tlam_ has joined #openstack-meeting21:53
notmynamem_kazuhiro: what woudl you prefer?21:53
claygI think we should ignore it21:54
*** diablo_rojo has quit IRC21:54
m_kazuhiroI think remainning topic can be discussed on IRC (not this meeting). So we can finish acout task queue for now.21:54
claygthis problem at least21:55
claygWe could come up with all kinds of arbitrary ways to limit the number of deployed nodes which handle the legacy data21:55
notmynamethat's brought us pretty close to full time21:55
*** diablo_rojo has joined #openstack-meeting21:55
notmyname#topic open discussion21:55
clayg"also_do_legcy_work = false"21:55
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:55
notmynameI remembered the other thing I wanted to bring up at the beginning21:55
notmynamenext meeting time21:55
clayg"legacy_processes = 4" "legacy_process = 1"21:56
notmynameI suggest we skip the next 2 weeks21:56
*** priteau has quit IRC21:56
notmynameand next meeting is january 1021:56
claygnotmyname: can I still get into openstack-swift and tell everyone what santa brings me?21:56
kota_sounds good21:56
claygon the 27th21:56
notmynameany objections? (objecting is the same as volunteering to run a meeting)21:56
claygno objections21:56
acolesnotmyname: no objections21:56
* joeljwright stays silent21:57
acolesugh, I lost21:57
*** yanxingan has quit IRC21:57
rledisezok for me, i'll be off starting friday21:57
notmynameok, next meeting is january 1021:57
claygrledisez: have a good holiday!21:57
rledisezthx clayg :)21:57
kota_rledisez: enjoy!21:57
notmynameif you are taking a holiday, I hope you have a good time with friends and family21:57
acolesrledisez: bon vacances21:57
rledisezthx all, i'm sure i'll enjoy it!21:58
notmynamethanks, everyone, for all your work on swift :-)21:58
notmynamethanks for a good swift-in-201721:58
*** openstack changes topic to "OpenStack Meetings ||"21:58
openstackMeeting ended Wed Dec 20 21:58:30 2017 UTC.  Information about MeetBot at . (v 0.1.4)21:58
*** bobh has quit IRC21:58
openstackMinutes (text):
*** rledisez has left #openstack-meeting21:58
*** timburke has left #openstack-meeting21:59
*** ad_rien_ has quit IRC22:00
*** Apoorva_ has joined #openstack-meeting22:01
*** joeljwright has left #openstack-meeting22:02
*** torgomatic has left #openstack-meeting22:03
*** Apoorva has quit IRC22:04
*** rajulk has quit IRC22:06
*** gouthamr has quit IRC22:06
*** apetrich has quit IRC22:11
*** apetrich has joined #openstack-meeting22:11
*** salv-orlando has joined #openstack-meeting22:17
*** chyka has joined #openstack-meeting22:17
*** m_kazuhiro has quit IRC22:19
*** felipemonteiro__ has joined #openstack-meeting22:20
*** salv-orlando has quit IRC22:22
*** chyka has quit IRC22:22
*** e0ne has quit IRC22:23
*** felipemonteiro_ has quit IRC22:24
*** bobh has joined #openstack-meeting22:24
*** david-lyle has quit IRC22:24
*** e0ne has joined #openstack-meeting22:26
*** e0ne has quit IRC22:26
*** e0ne has joined #openstack-meeting22:27
*** e0ne has quit IRC22:28
*** e0ne has joined #openstack-meeting22:28
*** bobh has quit IRC22:28
*** e0ne has quit IRC22:28
*** awaugama has quit IRC22:30
*** rcernin has joined #openstack-meeting22:32
*** trozet has quit IRC22:32
*** yanxingan has joined #openstack-meeting22:34
*** yanxingan has quit IRC22:40
*** ijw has joined #openstack-meeting22:40
*** yanxingan has joined #openstack-meeting22:41
*** yanxingan has quit IRC22:44
*** pchavva has quit IRC22:46
*** erlon has quit IRC22:49
*** ijw has quit IRC22:53
*** bobh has joined #openstack-meeting22:54
*** rajulk has joined #openstack-meeting22:56
*** david-lyle has joined #openstack-meeting22:56
*** bobh has quit IRC22:59
*** diablo_rojo has quit IRC23:02
*** rmcall has joined #openstack-meeting23:09
*** rmcall has quit IRC23:10
*** dprince has quit IRC23:10
*** rmcall has joined #openstack-meeting23:10
*** bobh has joined #openstack-meeting23:14
*** diablo_rojo has joined #openstack-meeting23:14
*** salv-orlando has joined #openstack-meeting23:17
*** bobh has quit IRC23:18
*** salv-orlando has quit IRC23:21
*** Apoorva_ has quit IRC23:24
*** felipemonteiro__ has quit IRC23:24
*** felipemonteiro__ has joined #openstack-meeting23:24
*** bobh has joined #openstack-meeting23:25
*** Apoorva has joined #openstack-meeting23:25
*** bobh has quit IRC23:29
*** gouthamr has joined #openstack-meeting23:30
*** bobh has joined #openstack-meeting23:33
*** edmondsw has joined #openstack-meeting23:33
*** yanxingan has joined #openstack-meeting23:33
*** bobh has quit IRC23:37
*** edmondsw has quit IRC23:38
*** felipemonteiro__ has quit IRC23:41
*** jamesmcarthur has quit IRC23:46
*** felipemonteiro__ has joined #openstack-meeting23:46
*** ijw has joined #openstack-meeting23:53
*** ijw has quit IRC23:59

Generated by 2.15.3 by Marius Gedminas - find it at!