Wednesday, 2018-01-17

*** awaugama has quit IRC00:02
*** genek has quit IRC00:05
*** rmcall_ has joined #openstack-meeting00:07
*** yamamoto has joined #openstack-meeting00:08
*** rossella_s has quit IRC00:08
*** rossella_s has joined #openstack-meeting00:10
*** rbudden has quit IRC00:13
*** VW has joined #openstack-meeting00:17
*** jamesmcarthur has quit IRC00:29
*** jamesmcarthur has joined #openstack-meeting00:29
*** jamesmcarthur has quit IRC00:32
*** chyka has quit IRC00:32
*** yangyapeng has quit IRC00:38
*** yangyapeng has joined #openstack-meeting00:38
*** pchavva has quit IRC00:39
*** bobh has joined #openstack-meeting00:40
*** yangyapeng has quit IRC00:43
*** jamesmcarthur has joined #openstack-meeting00:43
*** jamesmcarthur has quit IRC00:43
*** jamesmcarthur has joined #openstack-meeting00:43
*** AlanClark has quit IRC00:45
*** zhurong has joined #openstack-meeting00:45
*** lamt` has quit IRC00:45
*** tovin07_ has joined #openstack-meeting00:46
*** hongbin has quit IRC00:48
*** kaz has joined #openstack-meeting00:48
*** spzala has quit IRC00:51
*** Dinesh_Bhor has joined #openstack-meeting00:57
*** dongfeng has joined #openstack-meeting00:59
*** tovin07_ has quit IRC01:00
*** caisan has joined #openstack-meeting01:01
*** jamesmcarthur has quit IRC01:01
*** jamesmcarthur has joined #openstack-meeting01:01
*** Yipei has joined #openstack-meeting01:03
*** Yipei has quit IRC01:04
*** jaypipes has quit IRC01:06
*** yangyapeng has joined #openstack-meeting01:11
*** dongfeng has left #openstack-meeting01:11
*** kiennt26 has joined #openstack-meeting01:12
*** david-lyle has quit IRC01:23
*** markvoelker has quit IRC01:25
*** jamesmcarthur has quit IRC01:27
*** kevzha01 has joined #openstack-meeting01:28
*** caisan_ has joined #openstack-meeting01:28
*** caisan has quit IRC01:32
*** Dinesh_Bhor has quit IRC01:39
*** Dinesh_Bhor has joined #openstack-meeting01:41
*** edmondsw has joined #openstack-meeting01:45
*** julim has quit IRC01:45
*** tovin07_ has joined #openstack-meeting01:46
*** rbudden has joined #openstack-meeting01:47
*** gongysh has joined #openstack-meeting01:49
*** edmondsw has quit IRC01:50
*** genek has joined #openstack-meeting01:50
*** caisan has joined #openstack-meeting01:52
*** chyka has joined #openstack-meeting01:54
*** bobh has quit IRC01:54
*** genek has quit IRC01:55
*** caisan_ has quit IRC01:55
*** genek has joined #openstack-meeting01:55
*** jamesmcarthur has joined #openstack-meeting01:57
*** chyka has quit IRC01:59
*** jamesmcarthur has quit IRC02:01
*** cdub has quit IRC02:15
*** AlanClark has joined #openstack-meeting02:17
*** caisan_ has joined #openstack-meeting02:21
*** Tom-Tom_ has quit IRC02:23
*** hongbin has joined #openstack-meeting02:24
*** caisan has quit IRC02:24
*** epico has joined #openstack-meeting02:29
*** jamesmcarthur has joined #openstack-meeting02:33
*** liyi has joined #openstack-meeting02:38
*** jamesmcarthur has quit IRC02:38
*** rmcall_ has quit IRC02:40
*** gyee has quit IRC02:41
*** liyi has quit IRC02:43
*** beekhof_mb has quit IRC02:43
*** esberglu has quit IRC02:44
*** caisan has joined #openstack-meeting02:45
*** fzdarsky_ has joined #openstack-meeting02:45
*** fnaval_ has quit IRC02:46
*** caisan_ has quit IRC02:48
*** fnaval has joined #openstack-meeting02:48
*** fzdarsky|afk has quit IRC02:50
*** AlanClark has quit IRC02:57
*** yamahata has quit IRC02:59
*** iyamahat has quit IRC02:59
*** gongysh has quit IRC03:01
*** caisan_ has joined #openstack-meeting03:10
*** caisan has quit IRC03:13
*** gcb has quit IRC03:14
*** gongysh has joined #openstack-meeting03:15
*** gcb has joined #openstack-meeting03:18
*** epico has quit IRC03:24
*** markvoelker has joined #openstack-meeting03:26
*** ekcs has quit IRC03:28
*** bobh has joined #openstack-meeting03:30
*** esberglu has joined #openstack-meeting03:31
*** ricolin has joined #openstack-meeting03:34
*** ricolin has quit IRC03:34
*** iyamahat has joined #openstack-meeting03:39
*** spzala has joined #openstack-meeting03:40
*** yamahata has joined #openstack-meeting03:42
*** julim has joined #openstack-meeting03:43
*** caisan_ has quit IRC03:46
*** caowei has joined #openstack-meeting03:46
*** caisan has joined #openstack-meeting03:46
*** rbudden has quit IRC03:46
*** epico has joined #openstack-meeting03:46
*** bobh has quit IRC03:47
*** caisan has quit IRC03:47
*** caisan has joined #openstack-meeting03:48
*** ricolin has joined #openstack-meeting03:48
*** rbudden has joined #openstack-meeting03:48
*** daidv has joined #openstack-meeting03:50
*** caisan has quit IRC03:50
*** caisan has joined #openstack-meeting03:51
*** caisan has quit IRC03:55
*** gongysh has quit IRC03:55
*** fnaval has quit IRC03:59
*** markvoelker has quit IRC04:01
genek404:02
*** genek has quit IRC04:02
*** gongysh has joined #openstack-meeting04:03
*** Dinesh_Bhor has quit IRC04:05
*** coolsvap has joined #openstack-meeting04:05
*** anilvenkata has joined #openstack-meeting04:07
*** jamesmcarthur has joined #openstack-meeting04:10
*** kaz has quit IRC04:12
*** rbudden has quit IRC04:14
*** jamesmcarthur has quit IRC04:14
*** tobiash has left #openstack-meeting04:20
*** david-lyle has joined #openstack-meeting04:23
*** jbadiapa_ has quit IRC04:25
*** caowei has quit IRC04:25
*** jamesmcarthur has joined #openstack-meeting04:25
*** caowei has joined #openstack-meeting04:25
*** liyi has joined #openstack-meeting04:27
*** YanXingAn has joined #openstack-meeting04:29
gongysh#startmeeting tacker04:30
openstackMeeting started Wed Jan 17 04:30:19 2018 UTC and is due to finish in 60 minutes.  The chair is gongysh. Information about MeetBot at http://wiki.debian.org/MeetBot.04:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:30
*** openstack changes topic to " (Meeting topic: tacker)"04:30
openstackThe meeting name has been set to 'tacker'04:30
*** jamesmcarthur has quit IRC04:30
gongyshhi04:30
gongysh#topic roll call04:30
*** openstack changes topic to "roll call (Meeting topic: tacker)"04:30
*** psachin has joined #openstack-meeting04:31
gongyshYanXingAn, hi04:31
*** psachin has quit IRC04:31
*** liyi has quit IRC04:31
YanXingAnhi04:31
*** kaz has joined #openstack-meeting04:32
*** caisan has joined #openstack-meeting04:32
longkbo/04:33
*** psachin has joined #openstack-meeting04:33
*** YanXingAn has quit IRC04:34
*** YanXingAn has joined #openstack-meeting04:34
*** YanXing_an has joined #openstack-meeting04:36
*** zhurong has quit IRC04:36
YanXing_anhi, gongysh04:37
gongyshYanXing_an, hi04:37
gongyshit seems other guys are not available here.04:38
gongyshwe will have a short meeting04:38
*** dkushwaha has joined #openstack-meeting04:38
dkushwahao/04:38
gongyshlongkb, please update the patch04:38
gongyshI have see your demo04:38
gongyshdkushwaha, YanXing_an , please see the longkb patch and demo04:38
YanXing_angongysh, ok04:39
gongysh#info https://www.youtube.com/watch?v=7xzRaKVeikc&feature=youtu.be04:39
dkushwahagongysh, sure04:39
gongyshdkushwaha, do you have something to discuss?04:39
dkushwahagongysh, couple of bugs04:39
*** jamesmcarthur has joined #openstack-meeting04:39
*** YanXingAn_ has joined #openstack-meeting04:39
gongyshok,  we can go through these bugs one by one04:40
dkushwahagongysh, https://review.openstack.org/#/c/532046/04:40
*** YanXingAn has quit IRC04:41
gongyshdkushwaha, I think it is should be, the vnf cannot be deleted if it is part of any  ns04:41
longkbgongysh, I will update it04:41
gongyshlongkb, do you have guys to use this feature?04:42
*** bobh has joined #openstack-meeting04:42
dkushwahagongysh, i think, we should delete only those VNFs which are in ACTIVE state, because, errored VNFs can be deleted(not sure). and another main point is if delete_ns called, it will set state as pending_delete and then proceed for VNF deletion. In that case it will get blocked04:42
dkushwahagongysh, thats why i check for ACTIVE only. what is your suggestion on that?04:43
*** caisan has quit IRC04:44
gongyshdkushwaha,  is there anyway to tell  if the deletion of vnf is triggered by deletion of ns?04:45
dkushwahagongysh, yup, by db.04:46
dkushwahagongysh, let me search & paste link here04:46
gongyshdkushwaha, lets do this way.04:47
*** beekhof_mb has joined #openstack-meeting04:47
*** jamesmcarthur has quit IRC04:48
*** jamesmcarthur has joined #openstack-meeting04:48
*** andreas_s has joined #openstack-meeting04:49
*** links has joined #openstack-meeting04:49
*** gouthamr has joined #openstack-meeting04:49
dkushwahagongysh, you mean keep it as it is?04:49
*** bobh has quit IRC04:50
gongyshdkushwaha, I mean to tell  if the deletion of vnf is triggered by deletion of ns by db.04:50
gongyshyou said by db,  we can do.04:50
dkushwahagongysh, ok, i will check it again and update it.04:51
dkushwahagongysh,  https://review.openstack.org/#/c/491658/04:52
*** gouthamr has quit IRC04:53
dkushwahacould you please check it again04:53
*** andreas_s has quit IRC04:53
dkushwahai think its good to go04:53
gongyshdkushwaha, could you add a unit test for it?04:54
dkushwahagongysh, ok, will do it04:54
*** caisan has joined #openstack-meeting04:54
*** caowei has quit IRC04:55
gongyshand how the command line to provide a '' description?04:55
*** markvoelker has joined #openstack-meeting04:57
dkushwahagongysh, yea it can be an empty string04:57
gongyshdkushwaha, tacker ns-create --nsd-name admin-nsd1 --description '' nnnn, right?04:58
dkushwahagongysh, yes04:58
gongyshok04:58
*** jamesmcarthur has quit IRC04:58
gongyshnext bug, please04:59
dkushwahagongysh, https://bugs.launchpad.net/tacker/+bug/165836404:59
openstackLaunchpad bug 1658364 in tacker "DBReferenceError when Deploy or delete vnffg" [High,In progress] - Assigned to Tim Rozet (trozet)04:59
*** caisan has quit IRC04:59
dkushwahai was lookong for this, but i needs to rebase it05:00
gongyshok05:00
gongyshdkushwaha, please add a reno doc for each bug fix too.05:01
dkushwahagongysh, sure05:01
dkushwahagongysh, https://review.openstack.org/#/c/532802/05:01
gongyshhttp://logs.openstack.org/02/532802/1/check/tacker-functional-devstack/5b811f1/testr_results.html.gz05:02
gongyshdkushwaha, the name you are using is not an legal one in heat.05:02
gongyshdkushwaha. we also need to consider the compatibility of previous uuid way.05:03
dkushwahagongysh, you mean something like vnf_name + vnf_id?05:04
gongyshdkushwaha, yes05:04
dkushwahagongysh, ok, will update it05:04
gongyshdkushwaha, compatibility is a big issue05:04
dkushwahagongysh, i feel the above error is may be due to some test cases,which i missed to update, but ok, i will check it again05:05
gongyshwe have to first consider the previous name pattern, and then new name pattern when we do vnf deletion or other operations.05:05
dkushwahagongysh, I done from my side for now.05:07
gongyshdkushwaha, ok, thanks05:08
gongysh#topic annoucement05:08
*** openstack changes topic to "annoucement (Meeting topic: tacker)"05:08
*** hongbin has quit IRC05:09
gongyshit seems china mobile has a use cases for tacker, so we will do some big refactor in next cycle.05:09
*** liyi has joined #openstack-meeting05:09
*** noslzzp_ has joined #openstack-meeting05:09
gongysh#topic open discussion05:10
*** openstack changes topic to "open discussion (Meeting topic: tacker)"05:10
*** beekhof_mb has quit IRC05:10
gongyshit seems phuoc cannot be here, we will talk k8s vnf at tacker channel when I can meet him.05:10
gongyshanything else?05:10
gongyshok05:11
gongyshlets end meeting05:11
gongyshthanks05:11
gongysh#endmeeting05:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"05:11
openstackMeeting ended Wed Jan 17 05:11:44 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-01-17-04.30.html05:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-01-17-04.30.txt05:11
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2018/tacker.2018-01-17-04.30.log.html05:11
*** hongbin has joined #openstack-meeting05:12
*** noslzzp has quit IRC05:12
*** gongysh has quit IRC05:13
*** deathsparton has joined #openstack-meeting05:14
*** liyi_ has joined #openstack-meeting05:14
*** deathsparton has joined #openstack-meeting05:14
*** liyi has quit IRC05:14
*** markvoelker has quit IRC05:16
*** caisan has joined #openstack-meeting05:16
*** spzala has quit IRC05:17
*** deathsparton has quit IRC05:18
*** bswartz has quit IRC05:18
*** trozet has quit IRC05:19
*** chyka has joined #openstack-meeting05:21
*** edmondsw has joined #openstack-meeting05:21
*** YanXingAn_ has quit IRC05:24
*** edmondsw has quit IRC05:26
*** chyka has quit IRC05:26
*** jamesmcarthur has joined #openstack-meeting05:29
*** hongbin has quit IRC05:30
*** VW has quit IRC05:31
*** spzala has joined #openstack-meeting05:32
*** spzala has quit IRC05:32
*** spzala has joined #openstack-meeting05:34
*** caowei has joined #openstack-meeting05:34
*** YanXing_an has quit IRC05:35
*** tushar_ has quit IRC05:35
*** bswartz has joined #openstack-meeting05:36
*** trozet has joined #openstack-meeting05:37
*** jamesmcarthur has quit IRC05:37
*** deathsparton has joined #openstack-meeting05:39
*** jamesmcarthur has joined #openstack-meeting05:40
*** deathsparton has quit IRC05:42
*** trinaths has joined #openstack-meeting05:44
*** jamesmcarthur has quit IRC05:45
*** zhurong has joined #openstack-meeting05:48
*** YanXing_an has joined #openstack-meeting05:48
*** gongysh has joined #openstack-meeting05:48
*** jamesmcarthur has joined #openstack-meeting05:53
*** jamesmcarthur has quit IRC05:58
*** caowei has quit IRC05:59
*** ykatabam has quit IRC06:00
*** armax has quit IRC06:01
*** sridharg has joined #openstack-meeting06:01
*** caowei has joined #openstack-meeting06:01
*** armax has joined #openstack-meeting06:01
*** armax has quit IRC06:02
*** jamesmcarthur has joined #openstack-meeting06:02
*** armax has joined #openstack-meeting06:02
*** armax has quit IRC06:02
*** caowei has quit IRC06:03
*** absubram has joined #openstack-meeting06:06
*** caisan_ has joined #openstack-meeting06:08
*** jamesmcarthur has quit IRC06:08
*** caisan has quit IRC06:11
*** jamesmcarthur has joined #openstack-meeting06:12
*** iyamahat has quit IRC06:17
*** Dinesh_Bhor has joined #openstack-meeting06:17
*** jamesmcarthur has quit IRC06:17
*** jbadiapa has joined #openstack-meeting06:18
*** spzala has quit IRC06:19
*** kaz has quit IRC06:19
*** janki has joined #openstack-meeting06:20
*** Dinesh_Bhor has quit IRC06:22
*** Dinesh_Bhor has joined #openstack-meeting06:23
*** jamesmcarthur has joined #openstack-meeting06:27
*** markvoelker has joined #openstack-meeting06:28
*** Dinesh_Bhor has quit IRC06:28
*** Dinesh_Bhor has joined #openstack-meeting06:28
*** YanXing_an has quit IRC06:31
*** jamesmcarthur has quit IRC06:31
*** caowei has joined #openstack-meeting06:32
*** jamesmcarthur has joined #openstack-meeting06:34
*** fnaval has joined #openstack-meeting06:35
*** YanXing_an has joined #openstack-meeting06:36
*** caisan has joined #openstack-meeting06:36
*** sapd__ has quit IRC06:38
*** marios has joined #openstack-meeting06:39
*** sapd__ has joined #openstack-meeting06:39
*** jamesmcarthur has quit IRC06:39
*** caisan_ has quit IRC06:40
*** ekcs has joined #openstack-meeting06:42
*** Alex_Staf has joined #openstack-meeting06:43
*** jamesmcarthur has joined #openstack-meeting06:48
*** ekcs has quit IRC06:49
*** spzala has joined #openstack-meeting06:50
*** spzala has quit IRC06:54
*** jamesmcarthur has quit IRC06:57
*** Dinesh_Bhor has quit IRC06:58
*** Dinesh_Bhor has joined #openstack-meeting06:59
*** makowals has joined #openstack-meeting07:01
*** caisan_ has joined #openstack-meeting07:02
*** markvoelker has quit IRC07:02
*** Dinesh_Bhor has quit IRC07:03
*** caisan has quit IRC07:04
*** Dinesh_Bhor has joined #openstack-meeting07:06
*** jamesmcarthur has joined #openstack-meeting07:08
*** edmondsw has joined #openstack-meeting07:09
*** absubram has quit IRC07:10
*** Dinesh_Bhor has quit IRC07:12
*** jamesmcarthur has quit IRC07:12
*** Alex_Staf has quit IRC07:13
*** andreas_s has joined #openstack-meeting07:14
*** edmondsw has quit IRC07:14
*** jamesmcarthur has joined #openstack-meeting07:17
*** Dinesh_Bhor has joined #openstack-meeting07:17
*** caowei has quit IRC07:17
*** iyamahat has joined #openstack-meeting07:19
*** iyamahat has quit IRC07:20
*** spzala has joined #openstack-meeting07:20
*** caowei has joined #openstack-meeting07:21
*** jamesmcarthur has quit IRC07:21
*** deathsparton has joined #openstack-meeting07:24
*** spzala has quit IRC07:25
*** caowei has quit IRC07:25
*** jamesmcarthur has joined #openstack-meeting07:25
*** julim has quit IRC07:26
*** YanXing_an has quit IRC07:27
*** jkilpatr has quit IRC07:28
*** deathsparton has quit IRC07:29
*** jamesmcarthur has quit IRC07:29
*** gongysh has quit IRC07:30
*** caisan has joined #openstack-meeting07:30
*** caisan_ has quit IRC07:33
*** spzala has joined #openstack-meeting07:33
*** Dinesh_Bhor has quit IRC07:37
*** jamesmcarthur has joined #openstack-meeting07:38
*** Dinesh_Bhor has joined #openstack-meeting07:38
*** spzala has quit IRC07:38
*** rbartal has joined #openstack-meeting07:39
*** jkilpatr has joined #openstack-meeting07:39
*** claudiub has joined #openstack-meeting07:40
*** Dinesh_Bhor has quit IRC07:41
*** Dinesh_Bhor has joined #openstack-meeting07:42
*** jamesmcarthur has quit IRC07:43
*** spzala has joined #openstack-meeting07:45
*** pcaruana has joined #openstack-meeting07:48
*** jamesmcarthur has joined #openstack-meeting07:49
*** gongysh has joined #openstack-meeting07:49
*** spzala has quit IRC07:50
*** spzala has joined #openstack-meeting07:51
*** honza has quit IRC07:53
*** Dinesh_Bhor has quit IRC07:53
*** jamesmcarthur has quit IRC07:53
*** pcaruana has quit IRC07:55
*** pcaruana has joined #openstack-meeting07:55
*** spzala has quit IRC07:56
*** spzala has joined #openstack-meeting07:57
*** markvoelker has joined #openstack-meeting07:58
*** caisan_ has joined #openstack-meeting07:58
*** jamesmcarthur has joined #openstack-meeting08:01
*** spzala has quit IRC08:01
*** caisan has quit IRC08:01
*** jamesmcarthur has quit IRC08:05
*** phil has joined #openstack-meeting08:05
*** phil is now known as Guest2958008:06
*** spzala has joined #openstack-meeting08:06
*** spzala has quit IRC08:11
*** Alex_Staf has joined #openstack-meeting08:13
*** jamesmcarthur has joined #openstack-meeting08:15
*** Dinesh_Bhor has joined #openstack-meeting08:16
*** spzala has joined #openstack-meeting08:19
*** jamesmcarthur has quit IRC08:21
*** alexchadin has joined #openstack-meeting08:22
*** Dinesh_Bhor has quit IRC08:24
*** spzala has quit IRC08:24
*** caowei has joined #openstack-meeting08:28
*** tesseract has joined #openstack-meeting08:29
*** jamesmcarthur has joined #openstack-meeting08:29
*** spzala has joined #openstack-meeting08:31
*** markvoelker has quit IRC08:32
*** jamesmcarthur has quit IRC08:34
*** Dinesh_Bhor has joined #openstack-meeting08:34
*** spzala has quit IRC08:35
*** jamesmcarthur has joined #openstack-meeting08:37
*** caowei has quit IRC08:39
*** trinaths has quit IRC08:40
*** Dinesh_Bhor has quit IRC08:41
*** jamesmcarthur has quit IRC08:42
*** trinaths has joined #openstack-meeting08:43
*** Dinesh_Bhor has joined #openstack-meeting08:45
*** rcernin has quit IRC08:45
*** trinaths has quit IRC08:46
*** jamesmcarthur has joined #openstack-meeting08:47
*** spzala has joined #openstack-meeting08:50
*** caowei has joined #openstack-meeting08:50
*** jamesmcarthur has quit IRC08:53
*** psachin` has joined #openstack-meeting08:54
*** spzala has quit IRC08:54
*** psachin has quit IRC08:54
*** deathsparton has joined #openstack-meeting08:57
*** edmondsw has joined #openstack-meeting08:58
*** caisan has joined #openstack-meeting08:59
*** daidv has quit IRC09:01
*** tovin07_ has quit IRC09:01
*** jamesmcarthur has joined #openstack-meeting09:01
*** spzala has joined #openstack-meeting09:01
*** daidv has joined #openstack-meeting09:01
*** tovin07_ has joined #openstack-meeting09:01
*** caisan_ has quit IRC09:02
*** julim has joined #openstack-meeting09:02
*** edmondsw has quit IRC09:02
*** jamesmcarthur has quit IRC09:05
*** spzala has quit IRC09:06
*** oidgar has joined #openstack-meeting09:06
*** fzdarsky_ is now known as fzdarsky09:07
*** psachin` has quit IRC09:09
*** jamesmcarthur has joined #openstack-meeting09:11
*** psachin has joined #openstack-meeting09:13
*** jamesmcarthur has quit IRC09:15
*** YanXing_an has joined #openstack-meeting09:16
*** caisan_ has joined #openstack-meeting09:16
*** caisan has quit IRC09:19
*** jamesmcarthur has joined #openstack-meeting09:20
*** caowei has quit IRC09:20
*** liyi_ has quit IRC09:20
*** caowei has joined #openstack-meeting09:21
*** Kevin_Zheng has quit IRC09:23
*** jamesmcarthur has quit IRC09:24
*** jamesmcarthur has joined #openstack-meeting09:27
*** markvoelker has joined #openstack-meeting09:29
*** deathsparton has quit IRC09:32
*** jamesmcarthur has quit IRC09:32
*** Dinesh_Bhor has quit IRC09:35
*** caisan has joined #openstack-meeting09:40
*** rcernin has joined #openstack-meeting09:40
*** kaz_ has joined #openstack-meeting09:42
*** arxcruz|off is now known as arxcruz|rover09:42
*** kaz_ has quit IRC09:42
*** jamesmcarthur has joined #openstack-meeting09:43
*** caisan_ has quit IRC09:44
*** qwebirc47540 has joined #openstack-meeting09:46
*** qwebirc47540 has quit IRC09:47
*** e0ne has joined #openstack-meeting09:47
*** jamesmcarthur has quit IRC09:47
*** yamamoto has quit IRC09:49
*** gongysh has quit IRC09:52
*** tovin07_ has quit IRC09:53
*** sshnaidm|off is now known as sshnaidm09:54
*** jamesmcarthur has joined #openstack-meeting09:55
*** yamamoto has joined #openstack-meeting09:57
*** jamesmcarthur has quit IRC10:00
*** caowei has quit IRC10:01
*** markvoelker has quit IRC10:02
*** caisan has quit IRC10:03
*** spzala has joined #openstack-meeting10:07
*** jamesmcarthur has joined #openstack-meeting10:10
*** spzala has quit IRC10:12
*** jamesmcarthur has quit IRC10:14
*** powerd has joined #openstack-meeting10:19
*** jamesmcarthur has joined #openstack-meeting10:20
*** spzala has joined #openstack-meeting10:21
*** dbecker has joined #openstack-meeting10:23
*** jamesmcarthur has quit IRC10:25
*** spzala has quit IRC10:26
*** aspiers has quit IRC10:27
*** sambetts|afk is now known as sambetts10:28
*** jamesmcarthur has joined #openstack-meeting10:30
*** yamamoto has quit IRC10:31
*** gongysh has joined #openstack-meeting10:31
*** yamamoto has joined #openstack-meeting10:31
*** yamamoto has quit IRC10:31
*** spzala has joined #openstack-meeting10:33
*** jamesmcarthur has quit IRC10:34
*** spzala has quit IRC10:37
*** jamesmcarthur has joined #openstack-meeting10:39
*** daveholland has joined #openstack-meeting10:42
*** zhurong has quit IRC10:43
*** jamesmcarthur has quit IRC10:44
*** jamesmcarthur has joined #openstack-meeting10:45
*** priteau has joined #openstack-meeting10:49
*** jamesmcarthur has quit IRC10:51
*** jamesmcarthur has joined #openstack-meeting10:52
*** spzala has joined #openstack-meeting10:53
*** belmoreira has joined #openstack-meeting10:56
*** efried has quit IRC10:56
*** oneswig has joined #openstack-meeting10:57
*** erlon has joined #openstack-meeting10:57
*** jamesmcarthur has quit IRC10:57
*** dims has quit IRC10:57
*** spzala has quit IRC10:58
*** yankcrime has joined #openstack-meeting10:58
*** dims has joined #openstack-meeting10:58
*** markvoelker has joined #openstack-meeting11:00
oneswig#startmeeting scientific-sig11:00
openstackMeeting started Wed Jan 17 11:00:31 2018 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.11:00
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
oneswigahoy there11:00
davehollandmorning11:00
oneswig#link Agenda for today https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_January_17th_201811:00
oneswigHi daveholland, morning11:00
yankcrimeo/11:01
oneswigHi Nick!11:01
johnthetubaguyo/11:01
* ildikov is lurking :)11:01
oneswigAnd John!11:01
strigaziHello11:01
vabadahi11:01
*** andreas_s has quit IRC11:01
oneswigand indeed, hi everyone11:01
* ildikov is looking at johnthetubaguy with cat eyes from Shrek :)11:01
*** andreas_s has joined #openstack-meeting11:01
priteauGood morning!11:02
oneswigWhile people gather, we have Spyros with us today, Magnum PTL.  Thanks for coming Spyros11:02
oneswigHi priteau11:02
belmoreirahi11:02
*** jamesmcarthur has joined #openstack-meeting11:02
*** spzala has joined #openstack-meeting11:02
oneswigReady to get stared?11:03
oneswigstarted...11:03
oneswig(hi belmoreira)11:03
oneswig#topic Magnum for research computing use cases11:03
*** openstack changes topic to "Magnum for research computing use cases (Meeting topic: scientific-sig)"11:03
oneswigSpyros, thanks for coming.  We have a ton of questions and I'm sure others do too.11:04
oneswigCan you set the ball rolling by describing what's happening with Magnum and bare metal?  It appears to have really improved in the last year11:04
strigaziSure, thanks11:05
strigaziSince the Newton cycle in 2016 magnum has the concept of cluster drivers11:05
strigaziThe goal of this change is to focus each cluster deployment in a combination of server type (vm|bm), Operating System and COE11:06
*** jamesmcarthur has quit IRC11:06
oneswigA single driver for each 3-tuple of these?11:07
strigaziFollowing this pattern we ended up having a driver for vm based drivers and ironic11:07
strigaziyes11:07
*** spzala has quit IRC11:07
strigazied fedora-atomic, virtual machine, kubernetes11:07
strigazis/ed/eg11:07
strigaziIronic wasn't playing nice with neutron at that time11:08
strigaziAnd the implementation was a assuming that all nodes are in a pre-existing network11:09
strigaziplus we didn't have a way to make the usage of cinder optional.11:09
*** epico has quit IRC11:09
*** jamesmcarthur has joined #openstack-meeting11:09
oneswigAll good points...11:10
oneswigSo what happened?11:10
strigaziWe used to have a cinder volume in each node moutned for container storage without the option to opt-out11:10
*** andreas_s has quit IRC11:10
*** rfolco has joined #openstack-meeting11:11
strigaziSo, we just made all these configurable and optionnal11:11
* johnthetubaguy noodles about manila mounts for storage needs11:11
strigaziWe can now use the same setup for both VMs and physical servers11:12
oneswigSo Ironic is a support through a set of options.  But COE is still a different driver, right?11:12
priteaustrigazi: You mentioned issues between Ironic and Neutron. Do you require multi-tenant networking to be configured?11:13
strigaziyes, we have a patch in flight to consolidate and weach COE is tied to the operating system11:13
*** alexchadin has quit IRC11:13
*** janki has quit IRC11:13
strigazipriteau: the usual use case is to have a private network where all nodes will be running. This network can be shared among tenants11:14
*** jamesmcarthur has quit IRC11:14
*** spzala has joined #openstack-meeting11:14
oneswigstrigazi: any plan to offer an unusual case?  ingest bandwidth is an issue for us11:15
*** fzdarsky has quit IRC11:15
strigazioneswig: what do you mean? What network configuration do you need?11:15
oneswiganything without a neutron router process between the data source and the container cluster, ideally11:16
*** andreas_s has joined #openstack-meeting11:16
oneswigFor example, a simplified setup where the nodes are deployed bound to a pre-existing (provider) network.  Would work for us but we may be niche11:17
davehollandthat layout would be of interest to us too11:17
johnthetubaguyI was thinking of using additional ips rather than floating ips, for example11:17
*** YanXing_an has quit IRC11:17
strigaziWill you be able to create ports to that network?11:18
oneswigstrigazi: yes11:18
*** jamesmcarthur has joined #openstack-meeting11:18
*** alexchadin has joined #openstack-meeting11:18
* johnthetubaguy thinks you can pass ports into nova for ironic instances now, not 100% sure11:19
strigaziI think that can done today already without patching magnum11:19
*** spzala has quit IRC11:19
priteauoneswig: Do you have a write-up of how you use these existing provider networks to bypass a centralized Neutron router? We would be interested in Chameleon to perform high-bandwidth experiments11:19
oneswigstrigazi: so we can configure Magnum not to create the network and router?11:20
*** deathsparton has joined #openstack-meeting11:21
*** caisan has joined #openstack-meeting11:21
oneswigpriteau: I'm not sure there's any rocket science to it - but our system is not as multi-tenant as yours.  Lets talk after.11:21
strigazioneswig: yes, that is already in pike for vms, ironic machines are expected to work in the same way in queens11:21
priteauoneswig: Thanks, I don't want to go off-topic11:21
oneswigstrigazi: sounds good to me.11:22
oneswigstrigazi: we are a little off mainline but we may have problems with deploying using Atomic Host cloud images - they lack drivers for some of the krazy hardware in our nodes (IB, etc).  Is it possible to build our own images and bake this stuff in?11:22
strigaziGetting the network architecture set correctly is the first thing to do11:22
*** jamesmcarthur has quit IRC11:22
*** spzala has joined #openstack-meeting11:23
strigaziWe used to have a diskimage-builder script for custom atomic hosts but we stopped using it and went for the upstream fedora releases. We can update it11:24
oneswigstrigazi: If it's on git, we'd be happy to refresh it.11:24
strigaziThe best option would be if those drivers could be installed on a running instance11:24
strigaziWould that be possible?11:25
oneswigCan be problematic for RAID devices, otherwise it should be11:25
*** deathsparton has quit IRC11:25
*** andreas_s has quit IRC11:25
*** caisan has quit IRC11:26
strigazianother option would be to use the standard images build with DIB and add the ostee storage for system containers11:26
*** andreas_s has joined #openstack-meeting11:26
johnthetubaguyimage builder is really good for ironic though, given ironic doesn't do snapshots11:26
oneswigIt's already part of our workflow in many other areas, we are immune to the pain11:27
oneswigor perhaps numbed11:27
johnthetubaguyheh11:27
johnthetubaguyboth probably11:28
*** spzala has quit IRC11:28
strigaziso we can have a working item after this meeting, run system container on non-atomic hosts OR build custom atomic images11:29
*** jamesmcarthur has joined #openstack-meeting11:29
strigazialways with diskimage-builder11:29
strigaziyou use diskimage-builder right?11:29
oneswigstrigazi: I haven't checked if DIB supports atomic as a target, but if it does, that sounds like a good plan to me.11:29
*** spzala has joined #openstack-meeting11:30
*** andreas_s has quit IRC11:30
*** andreas_s has joined #openstack-meeting11:31
*** martial__ has joined #openstack-meeting11:31
johnthetubaguythose network requirements, its it really just the need to define the ports before building the instance (to get the IP address?)11:31
strigazijohnthetubaguy: yes11:31
priteauoneswig: I don't see atomic support in the DIB repo, but there is http://teknoarticles.blogspot.co.uk/2016/04/generate-fedora-atomic-images-using.html11:32
*** yamamoto has joined #openstack-meeting11:32
*** yamamoto has quit IRC11:32
*** yamamoto has joined #openstack-meeting11:32
oneswigThanks priteau, I'll bookmark that11:32
*** markvoelker has quit IRC11:32
oneswigOK, did we have other questions on Magnum for now?11:33
strigaziit is also here https://github.com/openstack/magnum/tree/master/magnum/drivers/common/image/fedora-atomic11:33
oneswigIt kind of ties in to the next topic which relates to the PTG activities11:33
strigazioneswig: I have a question towards users :)11:33
oneswigstrigazi: good link - I know that guy :-)11:34
*** jamesmcarthur has quit IRC11:34
strigaziIs your main use case short or long living clusters?11:34
*** spzala has quit IRC11:34
oneswigFor us on the SKA project, it's long-lived, by which we mean weeks11:35
oneswigThat seems to be the pattern so far.11:35
johnthetubaguynot sure about the virtual lab case, depends if they run on the cluster, or they are clusters11:35
davehollandat Sanger: possibly both/either (long-lived for replacing the current compute clusters; short-lived for burst-y adding capacity to those)11:36
oneswigHow short is short?11:36
*** lpetrut has joined #openstack-meeting11:36
strigaziLet's say less than two months11:36
*** julim has quit IRC11:36
oneswigOne thing we'd love to see is dynamic ramp up/down in a demand driven cycle.  We have a use case for that11:36
oneswig#link would be excellent to see a Magnum equivalent of this http://www.informaticslab.co.uk/dask/2017/07/21/adaptive-dask-clusters-on-kubernetes-and-aws.html11:38
johnthetubaguytrue, add/remove node is more likely than add/remove cluster11:38
strigaziWe can work on a kubernetes autoscaler for magnum11:38
oneswigstrigazi: do you know of anything underway?11:38
martial__I agree, I think most of us have this need to autoscale11:39
oneswigHi martial__, morning11:39
oneswig#chair martial__11:39
openstackCurrent chairs: martial__ oneswig11:39
martial__Hi Stig11:39
strigaziNothing at the moment, but since kube 1.8 or 1.9 it is possible to write autoscaler with user defined metrics11:39
*** fabian_ has joined #openstack-meeting11:39
*** spzala has joined #openstack-meeting11:39
oneswigI believe there are public cloud plugins for this but nothing for OpenStack as of ~6 months ago11:40
*** jamesmcarthur has joined #openstack-meeting11:40
strigaziWell in openstack the resources usually are not infinite11:40
strigaziThe auto scaling feaure is not the same in a private cloud with quotas11:41
johnthetubaguyalthough credit cards have limits too11:41
johnthetubaguybut granted, its not identical11:41
oneswigstrigazi: http://www.stackhpc.com/baremetal-cloud-capacity.html - we do want to use the capacity we have to the fullest extent11:42
oneswigWe should move on11:43
strigaziWhen we have preemptibles :)11:43
oneswigFinal items for Magnum?11:43
strigaziOne last thing from me.11:43
oneswigstrigazi: excellent.  To be continued...11:43
*** gongysh has quit IRC11:43
strigaziDo you support server rebuilds on ironic nodes? We can continue another time if you want11:44
*** spzala has quit IRC11:44
oneswigstrigazi: sometimes it helps to rebuild a node11:44
*** jamesmcarthur has quit IRC11:44
oneswigI've used it.  Not in a Magnum context.  But people like the IPs they know...11:44
oneswigWe can continue in ~5 weeks at the PTG perhaps?11:45
strigazioneswig: sounds good to me, we want to base the upgrade capability on it (rebuild)11:45
strigazisure11:45
*** jamesmcarthur has joined #openstack-meeting11:46
oneswigstrigazi: I've seen Nova people not liking rebuilds - johnthetubaguy can you comment?11:46
*** absubram has joined #openstack-meeting11:46
*** caisan has joined #openstack-meeting11:46
oneswigPerhaps we should take that offline too11:47
oneswigTime is pressing11:47
oneswig#topic SIG representation at PTG11:47
*** openstack changes topic to "SIG representation at PTG (Meeting topic: scientific-sig)"11:47
oneswigAha, so we have some time during the cross-project phase to advocate use cases.11:47
martial__should we have a second session on this topic?11:48
oneswigCurrently this has some CERN/SKA discussions and the Ironic configurable deploy steps11:48
oneswigmartial__: perhaps request input and follow up?11:48
johnthetubaguyoneswig: thinking still, should work in theory.11:48
oneswig#link deployment steps spec https://review.openstack.org/#/c/412523/11:49
oneswigUse cases I've seen have requested kexec and boot-to-ramdisk, for example11:50
oneswigAll a bit unusual in a cloud mindset11:50
oneswigbut very useful for SIG members11:50
oneswigpriteau: are you still following this spec?11:50
johnthetubaguygetting the use cases and context accurate really helps get the right design11:50
*** jamesmcarthur has quit IRC11:51
*** caisan has quit IRC11:51
ildikovjohnthetubaguy: +111:52
ildikovoneswig: I have one item regarding PTG too11:52
oneswigildikov: go for it11:52
priteauoneswig: for Chameleon I think many users may want to use the new "Boot from Volume" functionality when we move to Pike or later, but I am still interested in a more configurable Ironic -- I haven't fully reviewed the spec yet though.11:52
ildikovoneswig: I'm dedicated that we will have multi-attach in Queens11:52
oneswigYou certainly are dedicated :-)11:53
*** spzala has joined #openstack-meeting11:53
ildikovoneswig: well I hope johnthetubaguy has a half day to review the Nova patches like today or tomorrow the latest :)11:53
ildikovoneswig: back to the topic, it's a first version and we're planning a cross-project session with Cinder and Nova on improvements for the PTG11:54
johnthetubaguyits honestly looking like Friday :(11:54
*** YanXing_an has joined #openstack-meeting11:54
oneswigI can expect this to be extremely useful if we can do the all-read-only, cached mode that alas seems to be beyond this version11:54
ildikovoneswig: and would love to have use cases and some input on how people are planning to use it11:54
ildikovjohnthetubaguy: I will ask melwitt if she might have a little time for it11:55
*** coolsvap has quit IRC11:55
johnthetubaguyits permissive, so you can do it with read/write volumes I think11:55
ildikovjohnthetubaguy: please do it on Friday then as the gate is blowing up all the time, so if anything needs to be fixed that's a bloodbath next week to get it done :(11:55
ildikovjohnthetubaguy: we're turning cache off which I think is the issue with the case oneswig mentioned11:56
oneswigcorrect - would need a model where clients can cache or the fan-in of load will be bad11:57
johnthetubaguyI didn't think it was that good of a cache we turned off, but that is a needed optimization11:57
johnthetubaguyI know v1 is libvirt only too, I guess we might need ironic support11:58
*** jamesmcarthur has joined #openstack-meeting11:58
priteauoneswig: Do you have more details about when the SIG session would happen during the PTG? The Blazar meetings are getting moved to Monday and Tuesday to remove conflict with Nova sessions.11:58
ildikovoneswig: it's definitely an interesting case as those settings happening at attach time and I'm not aware of changing that easily later11:58
oneswigWe should continue this - and will - in following meetings.  Thanks ildikov for raising it11:58
ildikovoneswig: thanks for the opportunity :)11:58
oneswigpriteau: half day on either Monday or Tuesday AFAIK.11:58
ildikovjohnthetubaguy: +1 for Ironic11:58
*** spzala has quit IRC11:58
martial__sounds like a plan, lots of things to continue in a follow up meeting11:59
johnthetubaguywould be great to get phase 2 planned for multi-attach11:59
oneswigjohnthetubaguy: +1 on that11:59
ildikovjohnthetubaguy: I just wish to get phase one in finally first :)12:00
oneswigIt has huge potential, I think12:00
johnthetubaguyildikov: +10012:00
oneswigWe are out of time, alas12:00
oneswigAnd johnthetubaguy has just used up every plus-sign in the country12:00
martial__lots of good things to follow up on12:00
ildikov:)12:00
* johnthetubaguy takes a bow12:00
oneswigThanks everyone12:00
oneswig#endmeeting12:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"12:00
openstackMeeting ended Wed Jan 17 12:00:47 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_sig/2018/scientific_sig.2018-01-17-11.00.html12:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_sig/2018/scientific_sig.2018-01-17-11.00.txt12:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_sig/2018/scientific_sig.2018-01-17-11.00.log.html12:00
*** oneswig has quit IRC12:01
*** alexchadin has quit IRC12:02
*** jamesmcarthur has quit IRC12:02
*** alexchadin has joined #openstack-meeting12:03
*** spzala has joined #openstack-meeting12:06
*** jkilpatr has quit IRC12:07
*** jamesmcarthur has joined #openstack-meeting12:07
*** armstrong has joined #openstack-meeting12:08
armstrong@smcginnis12:09
armstrongHello12:09
*** yankcrime has left #openstack-meeting12:09
*** jkilpatr has joined #openstack-meeting12:09
*** liyi has joined #openstack-meeting12:10
*** caisan has joined #openstack-meeting12:10
*** spzala has quit IRC12:11
*** sshnaidm is now known as sshnaidm|afk12:11
*** jamesmcarthur has quit IRC12:12
*** rcernin has quit IRC12:14
*** caisan has quit IRC12:14
*** liyi has quit IRC12:15
*** sshnaidm|afk has quit IRC12:16
*** caisan has joined #openstack-meeting12:17
*** jamesmcarthur has joined #openstack-meeting12:20
*** spzala has joined #openstack-meeting12:20
*** caisan has quit IRC12:22
*** jaypipes has joined #openstack-meeting12:24
*** jamesmcarthur has quit IRC12:25
*** beekhof_mb has joined #openstack-meeting12:25
*** spzala has quit IRC12:26
*** markvoelker has joined #openstack-meeting12:29
*** spzala has joined #openstack-meeting12:30
*** jamesmcarthur has joined #openstack-meeting12:32
*** chyka has joined #openstack-meeting12:34
*** edmondsw has joined #openstack-meeting12:34
*** spzala has quit IRC12:35
*** jamesmcarthur has quit IRC12:36
*** yangyapeng has quit IRC12:38
*** edmondsw has quit IRC12:38
*** chyka has quit IRC12:39
*** dprince has joined #openstack-meeting12:40
*** liyi has joined #openstack-meeting12:40
*** YanXing_an has quit IRC12:43
*** spzala has joined #openstack-meeting12:46
*** jamesmcarthur has joined #openstack-meeting12:48
*** kiennt26_ has joined #openstack-meeting12:48
*** rbowen has joined #openstack-meeting12:48
*** eharney has joined #openstack-meeting12:49
*** fabian_ is now known as chenyb412:49
*** spzala has quit IRC12:50
*** liyi has quit IRC12:51
*** verdurin_ is now known as verdurin12:51
*** jamesmcarthur has quit IRC12:53
*** alexchadin has quit IRC12:53
*** janki has joined #openstack-meeting12:54
*** sshnaidm|afk has joined #openstack-meeting12:55
*** spzala has joined #openstack-meeting12:55
*** sshnaidm|afk is now known as sshnaidm12:55
*** Guest29580 has quit IRC12:57
*** alexchadin has joined #openstack-meeting12:57
*** jamesmcarthur has joined #openstack-meeting12:58
*** spzala has quit IRC12:59
*** jamesmcarthur has quit IRC13:02
*** markvoelker has quit IRC13:03
*** bobh has joined #openstack-meeting13:07
*** spzala has joined #openstack-meeting13:09
*** jamesmcarthur has joined #openstack-meeting13:09
*** yangyapeng has joined #openstack-meeting13:11
*** aspiers has joined #openstack-meeting13:11
*** absubram has quit IRC13:12
*** pchavva has joined #openstack-meeting13:13
*** spzala has quit IRC13:13
*** jamesmcarthur has quit IRC13:13
*** YanXing_an has joined #openstack-meeting13:15
*** caisan has joined #openstack-meeting13:15
*** deathsparton has joined #openstack-meeting13:19
*** caisan has quit IRC13:19
*** jamesmcarthur has joined #openstack-meeting13:20
*** markvoelker has joined #openstack-meeting13:21
*** deathsparton has quit IRC13:21
*** cleong has joined #openstack-meeting13:23
*** jamesmcarthur has quit IRC13:24
*** vabada has quit IRC13:25
*** YanXing_an has quit IRC13:25
*** daveholland has quit IRC13:25
*** vabada has joined #openstack-meeting13:26
*** vabada has quit IRC13:26
*** vabada has joined #openstack-meeting13:27
*** vabada has quit IRC13:27
*** vabada has joined #openstack-meeting13:28
*** kiennt26 has quit IRC13:30
*** jamesmcarthur has joined #openstack-meeting13:31
*** chenyb4 has quit IRC13:31
*** Tom-Tom has joined #openstack-meeting13:32
*** fabian_ has joined #openstack-meeting13:32
*** fabian_ is now known as chenyb413:32
*** deathsparton has joined #openstack-meeting13:35
*** deathsparton has quit IRC13:35
*** spzala has joined #openstack-meeting13:35
*** deathsparton has joined #openstack-meeting13:35
*** deathsparton has quit IRC13:35
*** jamesmcarthur has quit IRC13:35
*** deathsparton has joined #openstack-meeting13:35
*** fnaval has quit IRC13:37
*** deathsparton has quit IRC13:37
smcginnisarmstrong: Hello13:38
*** spzala has quit IRC13:39
*** bobh has quit IRC13:40
*** jamesmcarthur has joined #openstack-meeting13:45
*** edmondsw has joined #openstack-meeting13:45
*** alexchadin has quit IRC13:46
*** kiennt26_ has quit IRC13:46
armstrong@smcginnis I will like to join the release team and actively participate in meetings13:47
*** anilvenkata has quit IRC13:47
smcginnisarmstrong: That's great! When not in meetings, we are in the #openstack-release channel.13:48
armstrongOk thanks13:48
*** jamesmcarthur has quit IRC13:49
*** deathsparton has joined #openstack-meeting13:50
*** rbudden has joined #openstack-meeting13:51
*** ssathaye has quit IRC13:52
armstrong@smcginnis: I have some questions on my Ph.D research concerning the release of OpenStack. Maybe I should contact you on email about that.13:52
*** ssathaye has joined #openstack-meeting13:52
*** simon-AS559 has joined #openstack-meeting13:53
*** esberglu has quit IRC13:54
*** jamesmcarthur has joined #openstack-meeting13:55
*** andreas_s has quit IRC13:56
*** chenyb4 has quit IRC13:56
*** andreas_s has joined #openstack-meeting13:56
*** tssurya has quit IRC13:56
*** fabian_ has joined #openstack-meeting13:57
*** fabian_ is now known as chenyb413:57
*** spzala has joined #openstack-meeting13:59
*** kgiusti has joined #openstack-meeting13:59
*** jamesmcarthur has quit IRC14:00
mugsie#startmeeting Designate14:00
openstackMeeting started Wed Jan 17 14:00:25 2018 UTC and is due to finish in 60 minutes.  The chair is mugsie. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: Designate)"14:00
openstackThe meeting name has been set to 'designate'14:00
mugsie#topic Roll Call14:00
*** openstack changes topic to "Roll Call (Meeting topic: Designate)"14:00
bnemeco/14:01
mugsielets give people a few minutes to jump in14:01
*** jamesmcarthur has joined #openstack-meeting14:02
*** deathsparton has quit IRC14:02
*** spzala has quit IRC14:03
*** rbartal has quit IRC14:04
*** YanXing_an has joined #openstack-meeting14:04
mugsiefrickler: simon-AS559 daidv courtesy ping14:04
mugsiebnemec: looks like it is just you and me :)14:05
*** andreas_s has quit IRC14:05
bnemec:-)14:05
*** spzala has joined #openstack-meeting14:05
*** andreas_s has joined #openstack-meeting14:05
mugsieI don't have much, I have been out of work sick since last week14:05
mugsieapart from needing someone to run the meeting next week, as I am going to on vacation14:06
mugsieor we could skip the meeting14:06
*** jamesmcarthur has quit IRC14:06
mugsiei can send a message to -dev asking for someone to step up14:07
bnemecI'm still pretty much focused on deploying Designate with TripleO.14:07
mugsiecool - is there anything your finding that we need to fix>14:07
mugsie?*14:07
bnemecNot at the moment.  My current problems are the poor state of TripleO container docs.14:08
bnemecI've actually got it deploying on baremetal alright.14:08
*** martial__ has quit IRC14:08
*** tssurya has joined #openstack-meeting14:08
bnemecI expect I'll have some questions when I start trying to do ha and such.14:09
*** spzala has quit IRC14:10
*** caisan has joined #openstack-meeting14:11
*** cdub has joined #openstack-meeting14:12
*** esberglu has joined #openstack-meeting14:12
*** archit has joined #openstack-meeting14:14
*** YanXing_an has quit IRC14:14
mugsieOK - if you need anything, just shout :)14:15
mugsieI think that may be it for today :)14:16
*** caisan has quit IRC14:16
mugsie#endmeeting14:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:16
openstackMeeting ended Wed Jan 17 14:16:21 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/designate/2018/designate.2018-01-17-14.00.html14:16
*** spzala has joined #openstack-meeting14:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/designate/2018/designate.2018-01-17-14.00.txt14:16
openstackLog:            http://eavesdrop.openstack.org/meetings/designate/2018/designate.2018-01-17-14.00.log.html14:16
*** kiennt26 has joined #openstack-meeting14:16
*** jamesmcarthur has joined #openstack-meeting14:17
*** bobh has joined #openstack-meeting14:18
*** belmoreira has quit IRC14:20
*** spzala has quit IRC14:21
*** jamesmcarthur has quit IRC14:21
*** caisan has joined #openstack-meeting14:22
*** spzala has joined #openstack-meeting14:23
*** caisan_ has joined #openstack-meeting14:23
*** YanXing_an has joined #openstack-meeting14:24
*** fzdarsky has joined #openstack-meeting14:26
*** caisan_ has quit IRC14:27
*** caisan has quit IRC14:27
*** spzala has quit IRC14:28
*** mjturek has joined #openstack-meeting14:29
*** jamesmcarthur has joined #openstack-meeting14:31
*** spzala has joined #openstack-meeting14:31
*** belmoreira has joined #openstack-meeting14:33
*** VW has joined #openstack-meeting14:33
*** YanXing_an has quit IRC14:35
*** jamesmcarthur has quit IRC14:35
*** spzala has quit IRC14:36
*** mjturek has quit IRC14:36
*** mjturek has joined #openstack-meeting14:36
*** jamesmcarthur has joined #openstack-meeting14:37
*** david-lyle has quit IRC14:37
*** gongysh has joined #openstack-meeting14:37
*** deathsparton has joined #openstack-meeting14:41
*** jamesmcarthur has quit IRC14:41
*** bobh has quit IRC14:42
*** deathsparton_ has joined #openstack-meeting14:42
*** ansmith has joined #openstack-meeting14:42
*** deathsparton has quit IRC14:46
*** sshnaidm is now known as sshnaidm|mtg14:46
*** spzala has joined #openstack-meeting14:46
*** awaugama has joined #openstack-meeting14:46
*** jamesmcarthur has joined #openstack-meeting14:46
*** deathsparton_ has quit IRC14:47
*** deathsparton has joined #openstack-meeting14:48
*** ianychoi has quit IRC14:48
*** deathsparton has quit IRC14:51
*** ianychoi has joined #openstack-meeting14:52
*** spzala has quit IRC14:52
*** spzala has joined #openstack-meeting14:52
*** andreas_s has quit IRC14:54
*** andreas_s has joined #openstack-meeting14:54
*** felipemonteiro has joined #openstack-meeting14:55
*** fnaval has joined #openstack-meeting14:57
*** guhcampos has joined #openstack-meeting14:57
*** ad_ri3n_ has joined #openstack-meeting14:57
*** felipemonteiro_ has joined #openstack-meeting14:57
ad_ri3n_#startmeeting fog-edge-massively-distributed-clouds15:00
openstackMeeting started Wed Jan 17 15:00:36 2018 UTC and is due to finish in 60 minutes.  The chair is ad_ri3n_. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: fog-edge-massively-distributed-clouds)"15:00
openstackThe meeting name has been set to 'fog_edge_massively_distributed_clouds'15:00
ad_ri3n_#chair  ad_ri3n_15:01
openstackCurrent chairs: ad_ri3n_15:01
ad_ri3n_#chair  ad_ri3n_15:01
openstackCurrent chairs: ad_ri3n_15:01
ad_ri3n_arg…15:01
*** parus has joined #openstack-meeting15:01
*** felipemonteiro has quit IRC15:01
ad_ri3n_so let's see who join15:01
ad_ri3n_#topic roll call15:01
*** openstack changes topic to "roll call (Meeting topic: fog-edge-massively-distributed-clouds)"15:01
parusGood day!15:01
ad_ri3n_(best wishes BTW, if I'm right this is our first meeting ;))15:01
ad_ri3n_Hi Parus15:01
*** pbressan has joined #openstack-meeting15:02
kgiustio/15:02
ansmitho/15:02
*** gongysh has quit IRC15:02
ad_ri3n_#link https://etherpad.openstack.org/p/massivfbely_distributed_ircmeetings_2018 line 29 agenda15:02
*** avankemp has joined #openstack-meeting15:02
ad_ri3n_sorry wrong link15:03
ad_ri3n_#link https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018 line 29 agenda15:03
avankempo/15:03
*** Marie_ has joined #openstack-meeting15:03
*** andreas_s has quit IRC15:03
ad_ri3n_Please go through the announcement section15:03
ad_ri3n_If you have question please feel free15:03
*** msimonin has joined #openstack-meeting15:03
ad_ri3n_;)15:03
*** alisanhaji has joined #openstack-meeting15:03
msimonino/15:04
alisanhajihi15:04
ad_ri3n_new resolutions for 2018, let's try to be more fruitful15:04
*** VW_ has joined #openstack-meeting15:04
ad_ri3n_;)15:04
ad_ri3n_Hi alisanhaji15:04
msimoninhey alisanhaji :)15:04
ad_ri3n_ok so last minute for asking questions regarding the news :)15:05
alisanhajiWhat are the news?15:05
ad_ri3n_sorry alisanhaji15:05
*** VW_ has quit IRC15:05
ad_ri3n_please give a look to our etherpad:15:05
ad_ri3n_https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018 line 2915:05
*** VW_ has joined #openstack-meeting15:05
ad_ri3n_and BTW please add your name in the attendees section15:06
ad_ri3n_thanks15:06
ad_ri3n_maybe I can just add that we have been working with rcherrueau the whole day trying to achieve a gap analysis15:06
*** AJaeger has joined #openstack-meeting15:06
ad_ri3n_of existing code base w.r.t. edge requirements15:06
*** AJaeger has left #openstack-meeting15:06
*** rcherrueau has joined #openstack-meeting15:07
rcherrueauo/15:07
msimoninhi rcherrueau15:07
parusIs there an etherpad?15:07
rcherrueauhi msimonin15:07
msimoninparus:  +115:07
alisanhajihi rcherrueau15:07
*** VW has quit IRC15:07
ad_ri3n_I'm not sharing it yet as it is really crappy from the formatting viewpoint now15:07
*** YanXing_an has joined #openstack-meeting15:07
*** tssurya has quit IRC15:08
rcherrueauhi alisanhaji15:08
parusIf we are still in news. I can point out two new community initiatives.15:08
ad_ri3n_sure please go ahead15:09
ad_ri3n_(and add it to the pad ;))15:09
parus1- The ONAP usecase team has started a group looking at Edge computing.15:09
ad_ri3n_great15:09
*** felipemonteiro_ has quit IRC15:09
ad_ri3n_some links?15:09
parus2- The IEEE, withing 5g.ieee.org has started a group called EAP (Edge Automation Platform) that is developping a framework for Edge.15:09
*** felipemonteiro has joined #openstack-meeting15:10
ad_ri3n_thanks15:10
parusI will dig out the links and post on etherpad.15:10
ad_ri3n_good to not15:10
ad_ri3n_to know15:10
ad_ri3n_I'm wondering how we can combine our effort15:10
ad_ri3n_(we should really fine a way to do not reinvent the wheel again and again)15:10
*** links has quit IRC15:11
ad_ri3n_ok nothing else?15:11
ad_ri3n_So let's switch to the first topic:15:11
ad_ri3n_#topic ongoing-action-AMQP15:11
*** openstack changes topic to "ongoing-action-AMQP (Meeting topic: fog-edge-massively-distributed-clouds)"15:11
ad_ri3n_guys, the floor is yours15:12
msimoninso15:12
*** bobh has joined #openstack-meeting15:12
kgiustidragonflow - I've been sidetracked on other stuff but will begin eval work this week.15:12
msimoningreat15:13
kgiustiotherwise that's about all I have this week (aside from a fix or two for the ombt2 tool)15:13
*** armax has joined #openstack-meeting15:14
ad_ri3n_thanks kgiusti15:14
*** efried_ has joined #openstack-meeting15:14
ad_ri3n_msimonin:  ?15:14
ad_ri3n_do you want to add something particular?15:14
msimoninFrom the massively distributed RPCs test plan side15:14
*** jamesmcarthur has quit IRC15:14
msimoninUntil now we are iterating on several tools : ombt2, the test framework, plugins15:15
msimoninplugins for collectd*15:15
msimoninI think we diverge a bit from the innitial goal15:15
msimoninwhich was to implement the test case (https://docs.openstack.org/performance-docs/latest/test_plans/massively_distribute_rpc/plan.html)15:15
ad_ri3n_ok15:16
msimoninWe'll need to refocus a bit during the next few weeks15:16
msimoninespecially get back to the initial massively distributed aspects of the test case15:16
ad_ri3n_ok no problem. I guess if did this choice because it was/is relevant?15:17
ad_ri3n_s/if did/ if you did15:17
*** andreas_s has joined #openstack-meeting15:17
msimoninYes, all the tools are better than before, the framework is strong15:17
ad_ri3n_cool15:18
ad_ri3n_You need to provide us a short overview of this stack ;)15:18
ad_ri3n_a white paper :-P15:18
ad_ri3n_anything else?15:18
msimonin#link https://github.com/msimonin/ombt-orchestrator15:18
msimoninthis a good entry point I guess15:19
*** absubram has joined #openstack-meeting15:19
ad_ri3n_(@msimonin it seems someone forgot to put the link toward the first results regarding rabbit)15:19
ad_ri3n_line 54 in the pad15:19
ad_ri3n_thanks15:20
msimoninad_ri3n_:  done15:20
*** jamesmcarthur has joined #openstack-meeting15:21
ad_ri3n_ok in a few words15:21
ad_ri3n_what are the first lessons you discovered?15:21
msimoninWe made all the experiments using rabbitmq (so centralized message bus)15:21
*** deathsparton has joined #openstack-meeting15:21
*** deathsparton has quit IRC15:22
*** deathsparton has joined #openstack-meeting15:22
*** deathsparton has quit IRC15:22
ad_ri3n_and?15:22
msimoninThis are more baseline study for now15:22
ad_ri3n_ok15:22
*** deathsparton has joined #openstack-meeting15:22
*** deathsparton has joined #openstack-meeting15:23
ad_ri3n_ok so more infos next time I guess?15:23
msimoninYou are greedy :)15:23
ad_ri3n_:-P15:24
ad_ri3n_ok so let's move to the next topic15:24
ad_ri3n_#topic ongoing-actions-cockroach15:24
*** openstack changes topic to "ongoing-actions-cockroach (Meeting topic: fog-edge-massively-distributed-clouds)"15:24
ad_ri3n_@rcherrueau @Marie_15:24
ad_ri3n_?15:24
rcherrueauNothing really new regarding nova. WIP ... (still struggling with the correlated subqueries)15:25
rcherrueau15:25
*** jamesmcarthur has quit IRC15:25
*** andreas_s has quit IRC15:25
rcherrueauGood news btw, Marie_ (o/ Marie_ ?) started an internship at Inria and she gonna work on cockroachdb perf15:26
rcherrueauWe plan to do perf analysis of Keystone + Galera vs. Keystone + CockroachDB15:26
*** andreas_s has joined #openstack-meeting15:26
Marie_Hi everyone :)15:27
rcherrueau(maybe we will reuse the framework of msimonin & co ;)15:27
msimoninI  can help writing the experiments :)15:27
rcherrueauWe plan to redo scenario defined in the performance working group15:27
avankempso can I :) (Hi Marie !)15:27
rcherrueauBut if you have a specific scenario in mind, and want us to test is, do not hesitate15:28
rcherrueauto test it*15:28
parus@rcherrueau: is there anything we can learn from the paper that Allison shared15:28
ad_ri3n_Thanks, maybe one can mention also that you push a blog related to the edge activities within the discovery and the first ticket is around the implementation cockroach-based keystone15:28
parus#link http://cnp.neclab.eu/projects/lightvm/lightvm.pdf15:28
*** mjturek has quit IRC15:29
ad_ri3n_yes parus ?15:29
*** hemna_ has quit IRC15:29
parusIn particular the part where they remove database?15:29
ad_ri3n_@rcherrueau can you please c/p the link to the post15:29
msimoninShould we go discuss at the PTG with Keystone teamp ?15:29
rcherrueauad_ri3n_: yep, discovery blog15:29
*** hongbin has joined #openstack-meeting15:29
rcherrueau#link https://beyondtheclouds.github.io/blog/15:29
rcherrueauparus: I have to take a look at the paper, thanks for the link15:30
msimoninrcherrueau:  We could ping Keystone folks to gather use cases15:31
*** yamamoto has quit IRC15:31
* ad_ri3n_ is looking for the section dealing with DB stuff (any hint welcome ;))15:31
rcherrueaumsimonin: you are right, lemme add this as a TODO on my side.15:32
ad_ri3n_parus: I cannot see this paragraph15:32
ad_ri3n_can you point me?15:32
*** mjturek has joined #openstack-meeting15:33
parusGive me a minute! I am not as fast as you are :-)15:33
*** jamesmcarthur has joined #openstack-meeting15:33
parussection 5.1 No XenStore15:33
ad_ri3n_thanks15:33
ad_ri3n_I will give it a look15:33
ad_ri3n_thanks15:33
*** mjturek has quit IRC15:34
ad_ri3n_I'm not sure (I may be wrong as I just went through the paper quickly)15:34
ad_ri3n_but the paper looks to be focused on a single hypervisor15:34
ad_ri3n_I will read it deeply and let's see what we can learn from it.15:35
parusIt is! but Allison's point is that we can learn from their methodology.15:35
parusTheir results are irrelevant to Openstack. The methodology can be reused.15:36
ad_ri3n_ok thanks for claryfing and in any case, reading SOSP papers is never waisted time ;)15:36
ad_ri3n_ok anything else regarding the cockroach stuff15:36
ad_ri3n_?15:36
rcherrueaunop15:36
ad_ri3n_#ongoing-action-usecases15:36
ad_ri3n_parus:  do you want to mention a few words?15:36
parusyes.15:37
parusThings are moving with the help of the foundation on use cases.15:37
parusI would like to get this team lined up behind this effort.15:37
ad_ri3n_for sure, there are discussions15:37
parusFor instance, the etherpad above gives details on a use case for a medium size scenario..15:38
ad_ri3n_what we can work on is to try to identify expected features in terms of functions15:38
parusI would like to use that same model and flesh out the other use cases.15:38
ad_ri3n_and conduct a gap analysis w.r.t the Openstack code base (and the different deployment scenarios)15:38
ad_ri3n_?15:38
ad_ri3n_what do you think parus?15:39
parusYes15:39
ad_ri3n_we select one use-case (let's say medium) and dive into details15:39
ad_ri3n_a few lines from the work we did today with rcherrueau15:39
parusyes?15:40
ad_ri3n_#link https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2018 line 6915:40
*** jamesmcarthur has quit IRC15:40
*** coolsvap has joined #openstack-meeting15:41
parusWho would like to help?15:41
*** mjturek has joined #openstack-meeting15:41
ad_ri3n_so from our side we hope to have a first proposal to be discussed by the end of the week15:42
*** jamesmcarthur has joined #openstack-meeting15:42
ad_ri3n_parus:  regarding your comment in the pad15:43
ad_ri3n_we think rather in terms of expected features from the naive one to most advanced15:43
parusOK15:43
ad_ri3n_openstack footpring for instance is something we should consider but we believe after15:44
ad_ri3n_Level 1:15:44
ad_ri3n_I want to be able to perform normal cloud operations on one site15:44
ad_ri3n_Level 2: I want to be able to perform nomral/usual cloud operation on another site15:44
ad_ri3n_Level 3: network split brain comes into the picture15:44
ad_ri3n_Level 4: mesh applications (cross network vpn, relocation of workloads)15:45
ad_ri3n_Level 5: can be space limitations15:45
ad_ri3n_what do you think?15:45
parusWhat about storage?15:45
ad_ri3n_you mean SWIFT like solution?15:45
ad_ri3n_or storage for the workloads (i.e. to be able to boot them)?15:45
parusI see level 4e has something.15:46
ad_ri3n_Level 1.f.15:46
ad_ri3n_too15:46
ad_ri3n_level 1 normal cloud, I want to use remote attached volume in one edge site15:46
*** yamamoto has joined #openstack-meeting15:46
parusand 4c would cover chaining?15:47
ad_ri3n_I believe that even before space limitations (i.e. openstack footprint15:47
ad_ri3n_yes15:47
ad_ri3n_exactly15:47
ad_ri3n_Level 5 can be related to all advanced admin operations (zero provisionning15:47
ad_ri3n_etc…)15:47
*** jamesmcarthur has quit IRC15:47
*** VW_ has quit IRC15:47
parusHow about failure/recovery?15:48
*** VW has joined #openstack-meeting15:48
ad_ri3n_failure is cover in Level 315:48
parus1000 nodes coming back online at the same time.15:48
ad_ri3n_recovery is not cover yet15:48
ad_ri3n_:D15:48
ad_ri3n_advanced operations15:48
ad_ri3n_Level 515:48
ad_ri3n_:D15:48
ad_ri3n_you are the FEMDC killer ;)15:48
*** fabian_ has joined #openstack-meeting15:48
parusThat sounds like a plan.15:48
ad_ri3n_and then we conduct a gap analysis15:49
ad_ri3n_according to15:49
ad_ri3n_vanilla openstack15:49
ad_ri3n_with remote compute nodes15:49
ad_ri3n_federated keystone15:49
ad_ri3n_regions15:49
ad_ri3n_cells15:49
*** walshh has joined #openstack-meeting15:49
*** oidgar has quit IRC15:49
parusGreat plan!15:49
ad_ri3n_I hope we can present a clean etherpad soon15:50
ad_ri3n_If you want to help us ;)15:50
ad_ri3n_you are more than welcome15:50
ad_ri3n_(and if you have a better idea, same ;))15:50
parusLet me get on a plane :-)15:50
ad_ri3n_:-)15:50
ad_ri3n_ok I will keep you in touch soon15:50
parus+115:51
ad_ri3n_ok let's move forward I would like to discuss a bit the other points15:51
ad_ri3n_is there any dragonflow folks?15:51
*** yamamoto has quit IRC15:51
*** chenyb4 has quit IRC15:51
ad_ri3n_I'm not sure15:51
ad_ri3n_ok so let's move to the open discussion (I have nothing to add regarding the other points)15:52
ad_ri3n_#topic ongoing-action-dragonflow15:52
*** openstack changes topic to "ongoing-action-dragonflow (Meeting topic: fog-edge-massively-distributed-clouds)"15:52
ad_ri3n_Not discuss15:52
*** gman-tx has joined #openstack-meeting15:52
*** gman-tx has quit IRC15:52
ad_ri3n_#topic ongoing-acton-p2p-ericsson15:53
*** openstack changes topic to "ongoing-acton-p2p-ericsson (Meeting topic: fog-edge-massively-distributed-clouds)"15:53
ad_ri3n_not discuss15:53
ad_ri3n_#topic open discussion15:53
*** openstack changes topic to "open discussion (Meeting topic: fog-edge-massively-distributed-clouds)"15:53
msimonin(dragonflow )I think kgiusti filled the pad l5315:53
*** efried_ is now known as efried15:53
ad_ri3n_I want to higlight the vancouver CFP once again (already highlighted in the news)15:53
ad_ri3n_it would be great if we can identify15:53
ad_ri3n_what presentations can be submitted by the FEMDC group15:53
*** alexchadin has joined #openstack-meeting15:54
ad_ri3n_can we make a first roundtable ?15:54
*** abishop has joined #openstack-meeting15:54
*** slaweq has quit IRC15:54
ad_ri3n_@rcherrueau cockroach?15:54
*** deathsparton has quit IRC15:54
ad_ri3n_@msimonin @kgiusti et al. AMQP ?15:54
rcherrueauad_ri3n_: yes it could be a good idea.15:54
*** slaweq has joined #openstack-meeting15:55
ad_ri3n_@parus use-case/gap analysis?15:55
ad_ri3n_anything else?15:55
parusAnything on performance?15:55
ad_ri3n_the AMQP evaluations I gues15:55
kgiustimsimonin: perhaps something around the AMQP eval?15:56
ad_ri3n_cockroach can also incluse some performance15:56
*** kiennt26 has quit IRC15:56
ad_ri3n_please see the pad15:56
ad_ri3n_I put some proposals15:56
rcherrueauparus: same for cockroach I guess15:56
msimoninkgiusti:  oh yes this would be great15:56
ad_ri3n_kgiusti: is there a link toward the PTG schedule please ?15:56
kgiustiI'd be willing to help present (if I can get travel)15:56
msimoninkgiusti:  we can discuss this during our weekly session15:57
*** Alex_Staf has quit IRC15:57
kgiustiad_ri3n_: I'm not aware of a detailed schedule yet - ansmith?15:57
ad_ri3n_@parus will you come to the PTG?15:57
parusI am not confirmed yet. Trying to !15:57
ansmithI have not seen15:57
ad_ri3n_ok15:58
ad_ri3n_one minute left15:58
ad_ri3n_anything else to mention?15:58
kgiustiad_ri3n_: but just in terms of my availability I need to help run the oslo meeting (which I think is during the first two days)?15:58
ad_ri3n_(please put it in the pad)15:58
ad_ri3n_kgiusti:  shame :(15:58
ad_ri3n_it is a pitty we do not have the schedule15:58
msimoninad_ri3n_: ttx sends a mail on the ml regarding the schedule (still struggling with it I gues)15:58
ad_ri3n_because it is really difficult to synchronise the effort15:58
*** deathsparton has joined #openstack-meeting15:58
ad_ri3n_msimonin:  thanks15:58
ad_ri3n_ok time to conclude15:58
parusthanks15:58
*** andreas_s has quit IRC15:59
*** slaweq has quit IRC15:59
ad_ri3n_ok thakns15:59
ad_ri3n_talk to you next time15:59
ad_ri3n_or by mail15:59
ad_ri3n_#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:59
openstackMeeting ended Wed Jan 17 15:59:29 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fog_edge_massively_distributed_clouds/2018/fog_edge_massively_distributed_clouds.2018-01-17-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fog_edge_massively_distributed_clouds/2018/fog_edge_massively_distributed_clouds.2018-01-17-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/fog_edge_massively_distributed_clouds/2018/fog_edge_massively_distributed_clouds.2018-01-17-15.00.log.html15:59
msimoninthanks ad_ri3n_15:59
Marie_thanks16:00
jungleboyj#startmeeting cinder16:00
openstackMeeting started Wed Jan 17 16:00:19 2018 UTC and is due to finish in 60 minutes.  The chair is jungleboyj. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
smcginniso/16: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
geguileohi! o/16:00
eharneyhey16:00
xyanghi16:00
tbarronhi16:00
erlonhey16:00
*** Marie_ has left #openstack-meeting16:01
tommylikehuhey16:01
abishopo/16:01
*** avankemp has quit IRC16:01
e0nehi16:01
jungleboyj@!16:01
_pewp_jungleboyj (✧∇✧)╯16:01
jungleboyjGood start to a quorum here.16:02
jungleboyjHope everyone is well.16:02
patrickeasto/16:02
*** gman-tx has joined #openstack-meeting16:02
*** alisanhaji has left #openstack-meeting16:02
*** sridharg has quit IRC16:02
*** msimonin has left #openstack-meeting16:03
jungleboyjOk, lets get started.16:03
*** kgiusti has left #openstack-meeting16:03
*** parus has left #openstack-meeting16:03
jungleboyj#topic Announcements16:03
*** openstack changes topic to "Announcements (Meeting topic: cinder)"16:03
jungleboyjQueens review priorities:16:03
*** makowals has quit IRC16:03
jgriffitho/16:04
jungleboyj#link https://etherpad.openstack.org/p/cinder-spec-review-tracking16:04
*** makowals has joined #openstack-meeting16:04
*** yamamoto has joined #openstack-meeting16:04
amito(o/ not entirely present)16:04
*** makowals has quit IRC16:04
*** fabian_ has quit IRC16:04
jungleboyjSo, I just updated that list based on what I could find out in review.o.o and launchpad.16:04
jungleboyjIf you have updates, please make them ASAP.16:04
jungleboyjMore on that later in the meeting.16:04
*** makowals has joined #openstack-meeting16:04
jungleboyjThe proposed Rocky schedule is now available:16:05
*** makowals has quit IRC16:05
jungleboyj#link https://releases.openstack.org/rocky/schedule.html16:05
SwansonHello.16:05
*** makowals has joined #openstack-meeting16:05
jungleboyjI am going to propose a patch to that, that will basically keep the same release schedule had for Queens if there are no objections.16:05
jungleboyjSwanson:  Moving slow in the cold?  ;-)16:05
*** makowals has quit IRC16:06
DuncanTAnother 6 month cycle?16:06
jungleboyjDuncanT:  Hey!16:06
smcginnisDuncanT: Yep, no change there.16:06
jungleboyjDuncanT:  Yes, couldn't get agreement on anything else.16:06
jungleboyjThe train moves on.16:06
e0nelooks pretty the same as for Pike16:06
*** makowals has joined #openstack-meeting16:06
*** makowals has quit IRC16:06
*** belmoreira has quit IRC16:06
jungleboyje0ne:  Exactly, so don't see a need to change things for Rocky.16:07
e0nejungleboyj: +116:07
*** pbressan has quit IRC16:07
jungleboyjAnyone disagree?16:07
smcginnisSounds good to me.16:07
*** yamamoto has quit IRC16:08
jungleboyj#action jungleboyj  To propose schedule for Rocky based on the Queens schedule.16:08
*** VW_ has joined #openstack-meeting16:08
jungleboyjLast item for announcements is a reminder that the Dublin PTG Planning etherpad is up.  If you are planning to go, please add your name16:09
jungleboyjIf you have topics, please add them.16:09
jungleboyj#link https://etherpad.openstack.org/p/cinder-ptg-rocky16:09
tommylikehugreat16:09
jungleboyjThank you for smcginnis  for getting the link into the greater list of etherpads.  :-)16:09
jungleboyjI think that was all I had for announcements.16:10
jungleboyj#topic Queens release schedule16:10
*** openstack changes topic to "Queens release schedule (Meeting topic: cinder)"16:10
jungleboyj#link https://releases.openstack.org/queens/schedule.html16:10
*** tssurya has joined #openstack-meeting16:10
jungleboyjSo, we are quickly approaching the end of Queens.16:10
* jungleboyj wonders how that happened.16:10
* erlon is ready: https://i.pinimg.com/originals/c2/0a/bc/c20abc45453fba99285395310a1e5e69.jpg16:10
jungleboyjOMG, I dare you erlon16:11
jungleboyjI gotta see taht.16:11
*** tpsilva has joined #openstack-meeting16:11
jungleboyj:-)16:11
erlonjungleboyj: haha don't challange me :P16:11
smcginnisThat's Scottish, not Irish. :)16:11
jungleboyjsmcginnis:  Shhhh, don't tell him that!16:11
erlonsmcginnis: crap, spend a lot of money on that16:12
jungleboyjSo, Feature freeze is Friday 1/19 as is library Freeze.16:12
*** janki has quit IRC16:12
e0neerlon: :)16:12
*** VW has quit IRC16:12
e0nejungleboyj: do we have any multiattach-ralated patches in progress now?16:13
jungleboyjI tried to get the remaining patches for os-brick through yesterday.  I need to see if those merged.16:13
jungleboyje0ne:  I will get to that.16:13
jungleboyjI should cut os-brick mid day tomorrow.16:13
jungleboyjClient Library freeze is next Friday.16:14
jungleboyjNot sure where we are on client patches.  I will look into that.16:15
smcginnisThursday!16:15
jungleboyjI really would like to make sure that we don't let a release go out where the Client and Server MVs don't match.16:15
smcginnisFreeze is always and has always been Thursday.16:15
smcginnisNot sure why people never seem to remember that. :)16:15
jungleboyjsmcginnis:  Sorry.  So that date on the list is actually the day after?16:16
smcginnisWhere?16:16
SwansonYou aren't the boss of us, McGinnis!16:16
tommylikehuSwanson: lol16:16
smcginnisSwanson: :P16:17
jungleboyjsmcginnis:  The release page says Jan 21 to 26 is the freeze week.16:17
smcginnisYes, that is the freeze week. And deadlines are always on Thursday as noted in a few of the specific items.16:17
jungleboyjOk.  :-)  thank you release master.16:18
jungleboyjSo, I stand corrected.16:18
tbarronsmcginnis: you ought to send out weekly reminders about that stuff16:18
*** jamesmcarthur has joined #openstack-meeting16:18
jungleboyjUpdated the notes in the meeting notes.16:18
tbarron:)16:18
jungleboyjtbarron:  Oh hush!16:18
smcginnistbarron: :)16:18
*** ad_ri3n_ has left #openstack-meeting16:19
*** VW_ has quit IRC16:19
jungleboyjAnyway, moving on.  If anyone knows of client code that needs to go in please get that up ASAP and make me aware of it.16:19
*** sshnaidm|mtg is now known as sshnaidm16:19
jgriffithjungleboyj: yeah16:19
*** VW has joined #openstack-meeting16:20
jgriffithjungleboyj: I haven't had a chance to work on it, but the whole broken client AUTH_TYPE thing needs fixed16:20
jungleboyjjgriffith:  Is there going to be anything related to multi-attach?16:20
jungleboyjjgriffith:  I think there is a patch for that out there.16:20
jgriffithjungleboyj: Ideally I'd liek to get the mode patch finished and proposed this week16:20
jgriffiths/liek/like/16:20
*** absubram has quit IRC16:21
jgriffithbut figuring out the mv issues from the shell is going to slow me down even more than usual16:21
jungleboyjjgriffith:  That would be good.16:21
smcginnisGah, is that still out there?16:21
e0nejungleboyj, jgriffith: is it https://review.openstack.org/#/c/532217/ a needed patch?16:21
smcginnisLet's fix it and revert it a few more times.16:21
jgriffithe0ne: I'll test it now and if so +2/A it and remove my shell alias that does unset OS_AUTH_TYPE16:21
jgriffithI swear we've broken/fixed this at least 3 times now :)16:22
smcginnisAt least.16:22
e0nejgriffith: I'll added a  reminer for myself to16:22
e0nejgriffith: I'll added a  reminer for myself to create functional tests for this16:22
jungleboyjjgriffith:  Is that what you were talking about needing to fix though?  https://review.openstack.org/#/c/532217/16:22
smcginnisLooks like that might be it.16:23
jgriffithe0ne: jungleboyj smcginnis yep, that fixes it16:23
jungleboyjsmcginnis:  That was how I interpreted it.16:23
jungleboyjjgriffith:  Great.  I will take another look at that now that it has been updated.16:24
jgriffithjungleboyj: oops :)16:24
jgriffithI already +2/A 'd it16:24
jungleboyjjgriffith:  WFM.16:24
e0ne:)16:24
jgriffithWFM?16:24
jungleboyjWork For Me16:24
jungleboyj*Works16:24
* jungleboyj can't type today.16:24
jgriffithAhh.. worried you meant WTF Man?16:24
jgriffith:)16:24
smcginnisNot Well FU Man.16:25
jgriffiththat's ok, I can't type ever16:25
e0ne:)16:25
* jungleboyj shakes my head16:25
jungleboyjDamn numb finger.16:25
jgriffithsmcginnis: yeah, that's kinda what I was thinking he meant :)16:25
*** slaweq has joined #openstack-meeting16:25
jungleboyjYes, because I so often say that to you.  ;-)16:25
smcginnishehe16:26
*** guhcampos has quit IRC16:26
jungleboyjAnyway, so I am going to check the state of the os-brick patches, spin up a release and then take a look at where things are for the client.16:26
smcginnisBy tomorrow.16:26
jungleboyj#action jungleboyj  To spin os-brick release.16:26
smcginnisThursday.16:26
smcginnis:)16:26
jungleboyj#action Get cinderclient patches merged ... brick-cinderclient-ext as well.16:27
* jungleboyj ignores smcginnis 16:27
e0nejungleboyj: FYI, we don't have opened brick-cinderclient-ext patches now16:27
jungleboyje0ne:  Ok, good.  I didn't think we did but I wanted to verify.16:28
smcginnise0ne: Good point, we could do a final release for this cycle on that if we have unreleased things.16:28
e0neI just checked it16:28
*** rcherrueau has quit IRC16:28
jungleboyjsmcginnis:  I am not sure that we do.  I did a release of that a bit ago and don't think anything new has gone in but will check.16:28
xyangso the deadline for both cinderclient and brick-cinderclient-ext is next Thursday?16:28
e0nexyang: yes16:29
xyangok16:29
smcginnisYep, Thursday. :)16:29
jungleboyj#action Jay to do brick-cinderclient-ext release if necessary.16:29
jungleboyjsmcginnis:  When?16:29
smcginnisjungleboyj: Just a requirements update: https://github.com/openstack/python-brick-cinderclient-ext/compare/0.7.0...master16:29
jungleboyjWednesday?16:29
smcginnisTHURSDAY16:29
jungleboyjI love releasing on Saturday.16:30
e0nejungleboyj: do you mean Friday-Monday night?16:30
jungleboyj#action release brick-cinderclient-ext by next THURSDAY16:30
jungleboyjOk, lets stop beating the THURSDAY horse and move on.16:31
smcginnis:)16:31
jungleboyj#topic Feature Freeze Concerns:16:31
*** openstack changes topic to "Feature Freeze Concerns: (Meeting topic: cinder)"16:31
jungleboyjSo, follow up on a few of the things in our review list that look like they are going to miss.16:32
jungleboyjWe have Update cheesecake promotion specification16:32
*** slaweq has quit IRC16:32
jungleboyjI don't see code for this anywhere.16:32
jungleboyjpatrickeast:  You know anything about this?16:32
jungleboyjOr eharney ?  I don't see jbernard around.16:33
eharneyno16:33
jungleboyjOk, I am thinking that is one that is going to get pushed out to Rocky.  I can move the spec.16:33
jungleboyjWill put it as a discussion item for the PTG to see where that is at?16:34
*** alexchadin has quit IRC16:34
jungleboyjeharney:  jbernard coming to the PTG again?16:35
eharneyyes16:35
jungleboyj#action jungleboyj to move spec out and add discussion at the PTG.16:35
jungleboyjeharney:  Cool.16:35
jungleboyjtransfer snapshots with volumes16:35
jungleboyjThe only code for this out there is a WIP.16:35
jungleboyjeharney:  You were -2 on this.16:36
eharneyi had some complaints on this one, it got updated a couple of days ago still as WIP... not sure about the current status16:36
jungleboyjOk, I will put at note in the review asking what is up.16:36
jungleboyj#action jungleboyj  Follow up on state of the patch.16:37
jungleboyjI would be willing to let that slip a little after FF if we can make progress on that.16:37
jungleboyjeharney:  smcginnis  any arguments?16:37
eharneyi'm a little concerned about the driver calls for that work, but it's been too long since i've looked at it, need to go study up on the spec again16:37
smcginnisI agree, I think that's kind of a bug we have that we should fix.16:37
eharneyhaving it in general would be good though16:38
jungleboyjOk.  So, lets see if we can work that one in.  I need to look closer at that review.16:38
jungleboyj#action jungleboyj smcginnis eharney  To work the patch through if possible.16:38
*** gyee has joined #openstack-meeting16:39
jungleboyjNext provisioning improvements.16:39
jungleboyjerlon:  Where is this at>?16:39
*** guhcampos has joined #openstack-meeting16:40
jungleboyjpaging erlon16:40
*** marios has quit IRC16:40
erlonjungleboyj: hey, so, have finished the code, but have hit a hidding bug on unit tests :/16:41
jungleboyjerlon:  Ok ...16:41
jungleboyjIs there a WIP patch pushed up?16:41
erlonworking activelly to get that ready16:41
erlonjungleboyj: we have some internal preocess to get things upstream, and that usually starts when the code is ready and passing our internal CI16:42
erlonIll try to see there if I can get a version upstream16:42
jungleboyjerlon:  Ok.16:42
jungleboyjsmcginnis:  Thoughts on this one.  Again, it is kind of a bug we are fixing up but also it seems like it could have broader impact.16:42
smcginniserlon: Is it close, or do you think the internal review will take long?16:43
smcginnisjungleboyj: But yes, that's kind of an existing bug that I would agree we could still try to get in if possible.16:44
erlonsmcginnis: its close, we have done the internall review actually, the only problem are that there are some tests not related to the change breaking16:44
jungleboyjerlon:  Ok.16:44
geguileoerlon: is the unit test bug the only thing stopping the process from moving forward?16:44
geguileoerlon: can we help you with those?16:44
erlonsmcginnis: if we pushing that upstream even with the problem people coud try to help, migh be a problem elsewhere16:44
erlongeguileo: yes16:45
jungleboyjerlon:  Yeah, that sounds like a reasonable note.16:45
geguileoerlon: I can try to help you if you want, ping me on the channel and we can try to debug the issues16:45
erlonjungleboyj: smcginnis let me see what I can do to make that available ASAP16:45
erlongeguileo: thanks16:45
geguileonp16:46
jungleboyjgeguileo:  Thanks!16:46
*** Tom-Tom has quit IRC16:46
jungleboyjSo I would say that the two issues above can go in if we can get it done in the next week or so.16:46
*** pcaruana has quit IRC16:46
jungleboyjI would put Multi-attach in the same bucket.  Not a train I think we should get in front of.16:47
jungleboyjSo, work those and checkpoint next week.16:47
jungleboyjAny concerns?16:47
jungleboyjGood, so I want to get to the next topic and make sure we don't run out of time.16:48
jungleboyj#topic RBD encryption changes16:48
*** openstack changes topic to "RBD encryption changes (Meeting topic: cinder)"16:48
jungleboyjeharney:16:48
eharneyhey16:48
jungleboyjHey.  Take it away.16:48
eharneyi've submitted some patches to enable encryption support in the RBD driver16:48
*** david-lyle has joined #openstack-meeting16:49
eharneythis is a feature that's been missing for quite a while, and it looks like things are lining up to land it in Queens16:49
eharneylyarwood has some Nova changes in flight to support this as well16:49
eharneythere are three patches up for cinder -- i'm going to squash it down into two patches later today16:50
eharneyhttps://review.openstack.org/#/c/534811/16:50
smcginnisI know I've been asked a few times about support for this, so I think it would be good to get in.16:50
jungleboyjRight.  We have encryption for our other backends but not for the one that the most people use.16:51
jungleboyjThat was why I am open to this.16:51
eharneyyeah, it's been a fairly significant feature gap for a while16:51
*** diablo_rojo has quit IRC16:52
*** absubram has joined #openstack-meeting16:52
eharneyso i'll update the patches in a bit, and start making sure we have all of the details documented about system-level requirements etc16:52
jungleboyjHaven't looked at the patches yet but you said you could keep them mostly in the RBD driver with only minor changes to the general code base?16:52
eharneyyeah, the non-RBD driver patch is this: https://review.openstack.org/#/c/534810/16:52
*** YanXing_an has quit IRC16:53
eharneywe need to pass a context object in create_volume()16:53
eharneypretty minor change, and it lines up with how a lot of other driver calls, so it seems good16:54
eharneyhow a lot of other driver calls work*16:54
jungleboyjOk.  Which is something that is surprising we don't already do.16:54
jungleboyjOk.  As I mentioned earlier, the one request is that we get a spec for this addition put in place before we cut the release so that this is documented as an addition.16:54
eharneyyep, i can do that16:55
jungleboyjCool.  jgriffith smcginnis  Any concerns with that?16:55
smcginnisNope16:55
jungleboyjeharney:  Do you think you can do this by next Wednesday?16:55
jungleboyjAt least get the code all worked up and merged in?16:55
eharneyjungleboyj: yes16:56
jungleboyjExcellent.16:56
*** rfolco is now known as rfolco_doctor16:56
jungleboyj#topic Cinder Shirts16:56
*** openstack changes topic to "Cinder Shirts (Meeting topic: cinder)"16:57
*** diablo_rojo has joined #openstack-meeting16:57
*** mjturek has quit IRC16:57
jungleboyjSo, I want back and looked at the notes from the PTG and it sounds like we all just wanted a shirt that had the new logo on the front.16:57
jungleboyjDo people just want a T-Shirt with a large logo or a polo type shirt with a smaller logo?16:57
jungleboyjIf we go the T-Shirt route I thought it might be cool to have 'Who manages your backend?" under the logo.16:58
xyangjungleboyj: can I have a T-shirt with the old logo on the front?:)16:58
smcginnis:)16:59
* jungleboyj laughs I saw that coming.16:59
smcginnisUnrelated, but I wanted to bring it up in the meeting and we are out of time. Thanks eharney for fixing driverfixes unit test problems, and CFP for the Summit is open so think about any talks.16:59
jgriffithjungleboyj: LOL, that's AWESOME16:59
jungleboyjxyang:  I could maybe do some of those.  I have no idea what the cost of these will be.  Asked management at Lenovo if they might be willing to help cover some costs.  No response yet.17:00
*** deathsparton has quit IRC17:00
jungleboyjjgriffith: I thought so!17:00
xyangjungleboyj: :)17:00
jungleboyjsmcginnis:  ++17:00
jungleboyjSo, lets take that discussion to the channel for those interested.17:00
smcginnisTime up.17:00
jungleboyjThank you team for a good meeting!17:00
*** anilvenkata has joined #openstack-meeting17:00
jungleboyjLets get this release done!17:00
jungleboyj#endmeeting17:00
*** abishop has left #openstack-meeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"17:01
openstackMeeting ended Wed Jan 17 17:00:59 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2018/cinder.2018-01-17-16.00.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2018/cinder.2018-01-17-16.00.txt17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2018/cinder.2018-01-17-16.00.log.html17:01
*** VW has quit IRC17:01
*** david-lyle has quit IRC17:02
*** david-lyle has joined #openstack-meeting17:03
*** VW_ has joined #openstack-meeting17:03
*** david-lyle has quit IRC17:03
*** dklyle has joined #openstack-meeting17:03
*** chyka has joined #openstack-meeting17:08
*** yamamoto has joined #openstack-meeting17:08
*** e0ne has quit IRC17:09
*** honza has joined #openstack-meeting17:11
*** rfolco_doctor is now known as rfolco17:15
*** mjturek has joined #openstack-meeting17:16
simon-AS559@mugsie Thanks for the courtesy ping; unfortunately I have another remote meeting every other week that collides with the Designate timeslot )-; Next week should be fine!17:17
*** yamamoto has quit IRC17:17
*** archit has quit IRC17:19
*** gman-tx has quit IRC17:19
*** tesseract has quit IRC17:21
*** tobberydberg has quit IRC17:23
*** tobberydberg has joined #openstack-meeting17:24
*** oidgar has joined #openstack-meeting17:25
*** slaweq has joined #openstack-meeting17:31
*** gman-tx has joined #openstack-meeting17:32
*** oidgar has quit IRC17:34
*** slaweq has quit IRC17:36
*** archit has joined #openstack-meeting17:37
*** esberglu has quit IRC17:44
*** simon-AS559 has quit IRC17:57
*** armstrong has quit IRC17:58
*** diablo_rojo has quit IRC18:00
*** dbecker has quit IRC18:02
*** mjturek has quit IRC18:02
*** julim has joined #openstack-meeting18:02
*** dklyle has quit IRC18:02
*** Tom-Tom has joined #openstack-meeting18:03
*** felipemonteiro has quit IRC18:06
*** Alex_Staf has joined #openstack-meeting18:07
*** mjturek has joined #openstack-meeting18:09
*** longkb has quit IRC18:10
*** ekcs has joined #openstack-meeting18:11
*** ianychoi has quit IRC18:14
*** e0ne has joined #openstack-meeting18:15
*** ianychoi has joined #openstack-meeting18:15
*** Tom-Tom has quit IRC18:27
*** yamahata has quit IRC18:29
*** e0ne has quit IRC18:30
*** simon-AS559 has joined #openstack-meeting18:30
*** guhcampos has quit IRC18:30
*** felipemonteiro has joined #openstack-meeting18:31
*** sambetts is now known as sambetts|afk18:33
*** simon-AS559 has quit IRC18:34
*** mjturek has quit IRC18:36
*** mjturek has joined #openstack-meeting18:38
*** slaweq has joined #openstack-meeting18:42
*** markstur has joined #openstack-meeting18:46
*** slaweq has quit IRC18:46
*** acoles has joined #openstack-meeting18:51
*** rmcall_ has joined #openstack-meeting18:51
*** psachin has quit IRC18:52
*** anilvenkata has quit IRC18:58
*** priteau has quit IRC18:58
Zaraanyone about for the... STORYBOARD MEETING?18:59
Zarait's that time again18:59
SotKo/18:59
* clarkb is lurking19:00
Zara:D19:00
Zara#startmeeting StoryBoard19:00
openstackMeeting started Wed Jan 17 19:00:14 2018 UTC and is due to finish in 60 minutes.  The chair is Zara. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: StoryBoard)"19:00
openstackThe meeting name has been set to 'storyboard'19:00
Zara#link https://wiki.openstack.org/wiki/Meetings/StoryBoard19:00
Zara^ agenda, looks like it's not updated for this week19:00
Zarahopefully will be a short one! :D19:00
Zara#topic Announcements19:00
*** openstack changes topic to "Announcements (Meeting topic: StoryBoard)"19:00
ZaraTHERE ARE NONE, EXCELLENT WORK19:00
Zara#topic In-progress Work19:01
*** openstack changes topic to "In-progress Work (Meeting topic: StoryBoard)"19:01
ZaraI believe the agenda items are from last week, it notes story templates and launchpad migration19:01
ZaraI guess jump in with things on those if you have them19:01
Zaraso instead quick round up of things currently in review19:01
Zaradhellman has sent many, many patches to our docs! :D19:02
Zarasince it's more than 10 I won't link them individually19:02
Zara#link https://review.openstack.org/#/q/project:openstack-infra/storyboard19:02
Zara^ that is where they can be found19:02
*** david-lyle has joined #openstack-meeting19:02
Zarathey range from new content to theming to various formatting fixes19:02
ZaraI'm very happy someone is taking time to update these and clean them up; thanks dhellman! :)19:03
* persia is also very excited to see a new approach to the docs19:04
Zaraon the webclient side, we have some general updating afoot19:04
Zaramix of updating our existing packages in an effort to reduce the wall of deprecation warnings and replacing things with newer tooling19:05
Zara#link https://review.openstack.org/#/c/384554/19:05
Zara^ is one that could do with more eyes on it to check if it breaks anything19:05
*** iyamahat has joined #openstack-meeting19:05
Zara#link https://review.openstack.org/#/c/534424/19:05
Zara^ a wip for webpack (thanks mordred!) so we can see where things are headed there19:05
mordred\o/19:06
Zarawe also have other patches in need of review more generally19:06
*** yamahata has joined #openstack-meeting19:06
Zara#link https://review.openstack.org/#/c/534461/19:06
Zarahopefully fixes links displaying as links19:06
ZaraI haven't got to reviewing that yet, but looks like nobody else has, so waving arms here! :D19:07
Zara#link https://review.openstack.org/#/c/526219/19:07
Zaraneeds more eeyes19:07
Zaraaiui idea is so that project teams can link directly to that in case they want to fill some fields automatically19:08
Zarafor templates etc19:08
SotKindeed19:08
*** david-lyle has quit IRC19:08
Zara#link https://review.openstack.org/#/c/530656/19:08
Zara'allow branches to be browsed by project id'19:08
SotKit also enables the construction of a link which will automatically create a private story with for example the VMT team added19:08
Zaraah yes I remember now19:09
SotKit also requires that change19:09
Zaraaha I was about to say I know nothing about that change but assume it depends on it19:09
*** coolsvap has quit IRC19:09
ZaraI think it went up when I was very distracted, sorry :)19:09
Zaraanyone interested in bug templates and VMT support should review those changes, then19:09
Zaraon the api side...19:10
SotKindeed it did19:10
Zara#link https://review.openstack.org/#/c/529433/19:10
Zarazuul has a problem with this, I have no idea why, is a fix to a migration script19:10
Zaralooked like it was just timeouts19:10
Zaramaybe needs poking, maybe needs more rechecks19:11
Zara#link https://review.openstack.org/#/c/533353/19:11
Zara'fallback to natural language search if syntax is bad'19:11
ZaraI haven't looked at this at allllllll19:11
SotKhmm, we really should try to find time to properly solve that timeout issue19:11
ZaraI like the idea of it though19:12
Zarayep19:12
Zaraour tests are ugh19:12
SotKoh yeah I did that when I was vaguely bug triaging the other day19:12
Zarathanks :)19:12
Zaraoh also I sent this19:12
Zara#link https://review.openstack.org/#/c/532367/19:12
Zarathat removes stuff about the vagrant setup19:13
Zarasince nobody uses it or has used it in... 3 years?19:13
ZaraI need to investigate why zuul is complaining19:13
* fungi looks19:13
*** e0ne has joined #openstack-meeting19:13
Zarait might've just been sent at a weird time, I remmeber there were some status messages going up in channel around then19:14
Zarathough it's also possible there are some tests that expect it that I didn't remove19:14
fungiyeah, looks like tox_install_sibling_packages failed on all of them. recheck it19:14
Zaradone! :)19:14
Zarathanks19:14
Zara#topic Open Discussion19:15
*** openstack changes topic to "Open Discussion (Meeting topic: StoryBoard)"19:15
fungiit was being refactored and a mistake slipped through19:15
Zaraah okay, thanks for catching that! :D19:15
fungiand our tests weren't correctly exercising that19:15
fungior we would have caught it19:15
Zarait's a good way to find gaps. :) I raced through items so we know what's currently going on and people can pick the most interesting to talk about19:16
Zaraso roundup complete, Openly Discuss away! :D19:16
ZaraI'm trying not to focus on too many things personally so my own focus is on updating our packages, especially for the webclient19:17
Zarabecause I don't want to suddenly hit a wall with it when some transitive dependency is removed forever19:17
fungii did bring the robots.txt topic up in the infra meeting yesterday. i think we're going to try rewriting the baked-in one on the production server and then see if goog indexes anything (or whether there's any performance impact)19:17
Zaracool, it will be interesting to see! :) I should be able to check for any strange performance19:18
SotKnice, hopefully it works better than expected19:18
*** absubram has quit IRC19:18
fungiyeah, not holding out much hope but we'll see19:18
ZaraI'm wondering if it'll index the things at the api endpoints instead19:19
fungientirely possible19:19
*** esberglu has joined #openstack-meeting19:19
Zara#link https://storyboard.openstack.org/api/v1/stories/200000119:19
Zara(for anyone wondering what I mean by that, there's an example)19:19
Zarawhich could still be useful I suppose, though likely confusing for most :D19:20
Zarabetter than nothing19:20
persiaAs part of the general upgrade-all-the-components, is an upgrafde to newer angular also planned?  That might help with the robots.txt bits.19:20
Zarahopefully updating more of the webclient more generally will make it more feasible to change our routing19:20
persiaThat's the first-ever bug filed in production after LP migrations started?  Wow.  Interesting artifact.19:21
* fungi isn't webdev-savvy enough to know what "routing" means in this context anyway19:21
Zarapersia: I don't think we intend to change the angular version itself any time soon, but my hope is to update various packages we're using atm and steadily replace them with the newer ones19:21
*** jamesmcarthur has quit IRC19:22
persiaI believe "routing" means "determine what to do for a given URL": in the case of Storyboard, the ansewr is mostly "give the browser the webui, and have the webui consume the XML at the endpoint"19:22
fungiaha, got it19:22
fungia decision tree of sorts19:22
Zarait's also some things like 'what to do when something hasn't loaded yet'19:22
funginot unlike how traditional network routers operated19:22
persiaZara: The reason I asked is because I was pointed at features in angular2 that would server-side render the app, which might help in the crawler case.19:22
SotKwe aren't likely to switch to angular (as opposed to angularjs/angular 1) any time soon, it would need a large amount of work19:22
Zarayeah, that's the issue, it's a very big change19:23
Zarawe'd *like* it to be 2, but I don't think there's anyone around who can take that on atm19:23
ZaraI want it to be 2 because then I could read the code19:24
persiafungi: Likely more important for cases where something in the middle is the break between "path" and "data", e.g.: "http://example.org/programs/myexecutable.cgi/widgets/suppliers/index/"19:24
fungimaybe mordred's secretly scheming to work on that ;)19:24
Zara#link https://review.openstack.org/#/c/384554/19:24
*** jamesmcarthur has joined #openstack-meeting19:24
Zarashows some routing things if curious19:24
Zarathe js changes19:24
fungicool!19:24
Zarapossibly not done right since I was mostly pattern matching from docs, but it's that kiiiind of thing19:25
fungiwell, there are _worse_ places to take usage examples from than the documentation for the framework you're trying to use, i suppose19:25
Zara:) I think historically we used a separate package for page routes because there wasn't one built into angular19:25
Zarathen later on one was built in19:25
Zarabut I came to things way later and can barely write js19:25
fungisounds likely19:25
fungithe angular growing one in its stdlib thing, not your js proficiency19:26
persiaSotK: Ah.  I was confused by the name.  When the first suggestion in results for "upgrade from angularjs to angular" is "rewrite your app", I appreciate that this may not happen.19:26
fungiyou're far more effective at this than i could hope to be19:26
*** gman-tx has quit IRC19:26
Zarahahaha dw :) so in general there are some design decisions that made sense at the time but would be very strange to make now :)19:26
Zarapersia: there's both angular 1 and angular 2, 2 isn't backwards compatible with 1, and both have.. microversions?19:27
Zaraso 'upgrade angular' could also mean '1.5 to 1.whatever' and that'd be fine19:27
persiaOr even just "versions" :)  Yes.  I appreciate that now, in a way that I did not at the start of the meeting.19:27
*** caisan has joined #openstack-meeting19:28
SotKand "2" is now just "angular", because it is up to something like 419:28
persiaIn the case of 384554, it's a downgrade from 1.6.7 to 1.5.8, as a handy example of changing version while staying within the same epoch.19:28
*** lpetrut has quit IRC19:28
Zara('we should move to angular 2' is kinda a running joke because the reason it was rewritten was it was so tough to use)19:28
*** jamesmcarthur has quit IRC19:29
Zaraangular 1 terminology is verrrry dense and angular1-specific imo)19:29
*** jamesmcarthur has joined #openstack-meeting19:29
Zara(but I'm biased because I generally have no idea what's going on)19:29
Zara(sotk's a better authority on that one)19:29
Zaraanyyyway19:30
*** lpetrut has joined #openstack-meeting19:31
Zaraplease check that patch with some logging in and logging out and navigating in both states, an earlier local draft hit bugs when logging out19:31
Zarait'd be extra great if someone could test it with token expiry19:31
* SotK will do some testing at some point19:32
*** diablo_rojo has joined #openstack-meeting19:32
*** caisan has quit IRC19:32
Zara#link https://storyboard.openstack.org/#!/story/200040719:32
Zaramay be helpful for directions19:32
Zararight at the end of that description are the steps we took to check access token interaction last time19:33
*** slaweq has joined #openstack-meeting19:33
Zaraanyone have anything else to discuss?19:33
SotKI don't think I have anything pressing19:34
ZaraI'm really happy so many people are helping out with patches and review in general! :D19:34
Zarait is very motivational19:35
Zaraso thanks everyone for that19:35
ZaraI don't have anything else personally, I have a wall of review19:35
*** iyamahat has quit IRC19:35
persiaIndeed.  I think I've thought about Storyboard more this week than I have otherwise for a couple months.19:35
Zara:)19:36
Zarain that case, I will end the meeting!19:37
Zara#endmeeting19:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"19:37
openstackMeeting ended Wed Jan 17 19:37:07 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2018/storyboard.2018-01-17-19.00.html19:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2018/storyboard.2018-01-17-19.00.txt19:37
Zarathanks, all! :D19:37
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2018/storyboard.2018-01-17-19.00.log.html19:37
*** e0ne has quit IRC19:38
*** slaweq has quit IRC19:38
*** mjturek has quit IRC19:38
*** iyamahat has joined #openstack-meeting19:40
*** david-lyle has joined #openstack-meeting19:43
*** walshh has quit IRC19:47
*** e0ne has joined #openstack-meeting19:49
*** mjturek has joined #openstack-meeting19:52
*** simon-AS559 has joined #openstack-meeting19:53
*** simon-AS5591 has joined #openstack-meeting19:54
*** lpetrut has quit IRC19:55
*** lpetrut has joined #openstack-meeting19:55
*** simon-AS559 has quit IRC19:57
*** cleong has quit IRC20:08
*** mjturek has quit IRC20:12
*** slaweq has joined #openstack-meeting20:17
*** rmascena has joined #openstack-meeting20:19
*** raildo has quit IRC20:21
*** ykatabam has joined #openstack-meeting20:26
*** Tom-Tom has joined #openstack-meeting20:27
*** mjturek has joined #openstack-meeting20:30
*** dprince has quit IRC20:31
*** julim has quit IRC20:31
*** Tom-Tom has quit IRC20:31
*** julim has joined #openstack-meeting20:33
*** corvus is now known as jeblair20:37
*** jeblair is now known as corvus20:37
*** lpetrut has quit IRC20:42
*** dustins has joined #openstack-meeting20:45
*** rledisez has joined #openstack-meeting20:49
*** rmascena has quit IRC20:51
*** patchbot has joined #openstack-meeting20:56
*** m_kazuhiro has joined #openstack-meeting20:56
*** dustins has quit IRC20:58
*** beekhof_mb has quit IRC20:58
*** timburke has joined #openstack-meeting20:59
notmyname#startmeeting swift21:00
openstackMeeting started Wed Jan 17 21:00:10 2018 UTC and is due to finish in 60 minutes.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
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
notmynamewho's here for the swift team meeting?21:00
kota_hi21:00
m_kazuhiroo/21:00
mattoliverauo/21:00
rledisezgood (morning|afternoon|evening) o/21:00
notmynamerledisez: what about the night time?21:01
*** joeljwright has joined #openstack-meeting21:01
rledisezyeah, my bad good night everybody :)21:01
notmyname:-)21:01
acoleshello21:01
joeljwrighthello21:01
timburkeo/21:03
notmynamewelcome21:03
*** diablo_rojo has quit IRC21:03
notmynamethere's been a ton of stuff landing since our last meeting. great work!21:03
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift21:03
mattoliverauOr you could use UGT time then we can all say good morning21:03
*** eharney has quit IRC21:03
notmynamethere's the agenda for this week21:04
joeljwrightgood morning!21:04
*** jamesmcarthur has quit IRC21:04
notmynamemostly I want to review stuff for the 2.17.0 release21:04
*** torgomatic has joined #openstack-meeting21:04
torgomatichi21:04
notmyname#topic next release21:05
*** openstack changes topic to "next release (Meeting topic: swift)"21:05
notmyname#link https://wiki.openstack.org/wiki/Swift/PriorityReviews21:05
notmynamenearly everything on there is marked off21:05
notmynamepatch 53238321:05
patchbothttps://review.openstack.org/#/c/532383/ - swift - Don't make async_pendings during object expiration21:05
notmyname...is open21:05
*** jamesmcarthur has joined #openstack-meeting21:05
notmynameas is the data segments in SLOs patch 36537121:05
patchbothttps://review.openstack.org/#/c/365371/ - swift - Add support for data segments to SLO and Segmented...21:05
notmynameunless there's any other major bugs or blockers, I'd like to see those land and then tag the release21:06
joeljwrightI think timburke addressed all the outstanding issues on 36537121:06
acolesI will look at p 532383 again tomorrow, most likely +A21:06
patchbothttps://review.openstack.org/#/c/532383/ - swift - Don't make async_pendings during object expiration21:06
notmynameacoles: thanks21:06
*** Alex_Staf has quit IRC21:06
notmynamejoeljwright: yeah, I think it's just that people have been (rightly) reviewing the expiry patches21:06
joeljwright+121:07
notmynameI've got the start of the authors/changelog patch at https://review.openstack.org/#/c/534528/21:07
patchbotpatch 534528 - swift - WIP21:07
notmynamethanks to clayg and timburke for the comments so far21:07
notmynameI'll update those today or tomorrow, and add info about the other patches that have landed21:08
notmynameany questions on the mechanics or logistics of this release?21:08
notmynametorgomatic: we'll get to your question next21:08
*** rfolco has quit IRC21:09
notmynameok, let's move on to torgomatic's question then :-)21:09
notmyname#topic checkpoint release?21:10
*** openstack changes topic to "checkpoint release? (Meeting topic: swift)"21:10
*** dustins has joined #openstack-meeting21:10
notmynametorgomatic: would you like to introduce it?21:10
*** jamesmcarthur has quit IRC21:10
torgomaticright now, we've got to consider rolling cluster upgrades across all past versions, and that makes things more difficult21:10
torgomaticI'd like to introduce some cutoffs where we don't allow upgrades from any old version to the latest, but make you go through some intermediate steps first21:11
torgomaticor, at least, to talk about doing that21:11
notmynamethanks. what does everything think? what questions do you have?21:12
torgomaticOne way is checkpoint releases: you have some releases C1, C2, etc. and you can upgrade from any version v < C1 to C1, then any version v <= C1 < C2 to C2, and so on21:12
notmyname(it's a big question, IMO, so I'd expect us to talk about it for a while)21:12
torgomatic(sorry, I have the slow fingers today)21:12
torgomaticanyhow, this came up in the context of https://review.openstack.org/#/c/534749/ , where we have a rolling-upgrade compatibility issue with proxies from 2013 and earlier21:13
patchbotpatch 534749 - swift - Preserve expiring object behaviour with old proxy-...21:13
acoleswould it lose us the openstack upgrade tag thing? I forget the correct terminology21:13
notmynameacoles: that depends on how we role out the idea21:14
notmyname*roll21:14
torgomaticI think we'd keep it as long as you could perform a rolling upgrade to the latest checkpoint release. (That's a property I very much want to keep, FWIW)21:14
*** dustins has quit IRC21:15
mattoliverauGoing from any to the latest us obvious is a big selling point, but alot of extra effort as me do more and more releases.21:16
notmynameaside from the patch you just linked, are there other places where "upgrade straight to latest" is currently obviously hurting us?21:16
torgomaticCheckpoints aren't the only way to go; we could define a window where you can upgrade from the last N minor versions or the last Y years21:16
*** eharney has joined #openstack-meeting21:16
torgomaticnotmyname: once we land Pete Zaitcev's improvements to the object PUT path, we still have to keep all that old protocol stuff in the proxy forever21:16
acolesone advantage I see is that we are reaching the point where we may not have the collective memory to realise when we let an upgrade issue slip in21:17
notmynamethose are both very good points21:17
notmynamekota_: rledisez: joeljwright: what are your thoughts?21:18
*** jamesmcarthur has joined #openstack-meeting21:19
rledisezI understand the need, and i'm not against the idea. i'm concerned about for how long (in month/years) would you support an upgrade path?21:19
joeljwrightit sounds reasonable to me, although we always did staged updates anyway21:19
rledisezi would say the minimum is a year, probably 2 is better, or to try to sync with some major distro release interval21:20
kota_not opposite opinion but a bit worried about how frequently we should care about the checkpoint. I don't expect it'll happen every release.21:20
kota_rledisez: it seems i'm with you.21:20
mattoliverauIt would be good to have stats on how often, people upgrade.. because having a wide enough gap would be good. Say every 3 or 4 years.. or by versions maybe? (Every 2 major versions)21:20
notmynamebased on the conversation in -swift a few hours ago, I'd said that we needed to make sure a 2 year-old release has supported upgrades but a 4 year-old one seemed like long enough to not worry too mcuh21:20
torgomaticYeah, a couple years at minimum for upgrades IMO.21:20
joeljwrighttorgomatic: +121:21
acolesI assumed we were talking in terms of years21:21
notmynameseems we're all in agreement on the unit to measure it21:21
mattoliverauEver couple of major versions would be easy for people to remember.. and represent major API changes21:21
notmynamemattoliverau: for all those major version bumps and API updates we do? ;-)21:22
mattoliverauYeah.. but the difference would be we coild21:22
mattoliverauCould..21:22
*** rfolco has joined #openstack-meeting21:22
*** jamesmcarthur has quit IRC21:23
notmynamein my mind, we started with swift 1.x. we got to 2.x with storage policies. we'll hit 3.x with a rewrite of the storage layer (eg protocols, new language, etc)21:23
notmynamehowever, that's getting a bit off-topic :-)21:23
notmynametorgomatic: help me out here. fi we decided to make a checkpoint at 2.17 and we agreed to support upgrades for 2 years, how long do we support 2.16 features? how long do we support 2.17? 2.18?21:24
mattoliverauYour welcome21:24
torgomaticnotmyname: user-facing features? Pretty much forever, like we do now.21:25
notmyname( rledisez: LOSF is part of that storage layer update, too ;) )21:25
notmynametorgomatic: ok. upgrades then?21:25
torgomaticIf we made 2.17 a checkpoint, then in a couple of years we'd make another checkpoint at, say, 2.34, and then another one at 2.60 in another couple years, and so on21:26
notmynameif someone has 2.16 installed, then what?21:26
timburkeanother way of looking at it: how far back will we feel comfortable removing cruft between 2.17 and 2.18?21:26
torgomaticso then in five years' time, that person with 2.16 would have to upgrade 2.16 -> 2.17 -> 2.34 -> 2.60 to get to the latest21:26
torgomaticand in this case, after we made 2.34 a checkpoint, 2.34.1 could remove compatibility cruft for anything 2.17 -> 2.1821:27
notmynameok, It hink I got it21:27
notmynamethe difference with a time-based method is that we support eg anything that was released 2 years ago21:27
notmynamecalendar-based21:28
notmynameso in 2018 we drop support for upgrading from anything released in 201521:28
notmynamethat sort of thing21:28
notmynamethe difference is that deployers would need to be on a (very slow moving) upgrade train21:28
notmynameright?21:28
torgomaticno, deployers could still wait a long time21:29
torgomaticwhen they did decide to upgrade, they'd just have to upgrade several times to get to the latest21:29
acoleswe would only be dropping support for upgrading *directly* from 2015 to 2018 releases right?21:29
notmynameright21:29
notmynameacoles: right21:29
torgomaticyes21:29
acolesright!21:29
rledisezan example: what about the renaming of .durable to #d for EC? should it be converted before moving on with version or will it be maintained forever?21:30
notmynametorgomatic: deployers could only upgrade, at most, to something released 2 years after their current version21:30
torgomaticnotmyname: yes21:30
notmynameok. just making sure the different methods are spelled out for everyone (myself included!)21:30
torgomaticrledisez: that one, we'd probably have to keep forever since we don't automatically convert things21:31
*** rmcall_ has quit IRC21:31
timburkewhat all would be in-scope for breaking? backend protocols, sure; client APIs, definitely not -- what about operator-facing things like https://github.com/openstack/swift/blob/2.16.0/swift/common/manager.py#L724-L72721:31
torgomaticon-disk data formats live forever, storage-node and replication protocols live a couple years21:31
rledisez^ seems reasonable21:32
* kota_ is wondering, it may make us to remove rolling container db scheme change for creating storage policy???21:32
*** jamesmcarthur has joined #openstack-meeting21:32
acolesrledisez: torgomatic +! and good clarification, on disk data always supported21:33
timburkeoh yeah, speaking of JIT migrations -- https://review.openstack.org/#/c/502529/21:33
patchbotpatch 502529 - swift - Create policy_stat table in auditor if missing21:33
notmynamehere's what I think we should do: ask any further questions about generally how it works, go and sleep on it, and come back together later to talk about specifics or if we even like the idea21:33
notmynameI don't think we need to get into "what about lines 200-210 in this module" right now ;-)21:33
timburkenotmyname: i was just grepping for 'compat' :-)21:33
notmynameheh21:34
notmynameno, they're important to ask21:34
timburkesee what broad classes of things are out there21:34
notmynameI want to make sure everyone feels they understand the idea of time-based vs checkpoint releases for dropping compatibility21:34
*** aeng has joined #openstack-meeting21:34
notmynameare there any questions? do you (everyone) feel good enough with the concept to explain it to your boss?21:35
notmynameif not, ask now!21:35
notmynameif so, let's each go ponder it for a bit. not to try to slow down conversation too much, but this may be an interesting topic for the PTG21:35
mattoliverau+1 ptg topic21:36
notmyname+1 if youre' good with it21:36
kota_notmyname: sorry, i have to wait my boss waking up :P21:36
joeljwright:D21:36
mattoliverauLol21:36
notmyname:-)21:36
kota_notmyname: let me confirm on the mean you said *vs* between time-based and checkpoint21:36
timburkei'm still wondering whether something like https://github.com/openstack/swift/commit/ebf0b22 would be in scope for removal post-2.17 or not...21:37
notmynamekota_: versus. meaning that you know the differences between the two and how they relate21:37
kota_yeah, and... i may be missing the context or the summary here.... (scrolling back to the log...)21:37
notmynamekota_: I just want to check that you understand both and can think on it for a while in order to figure out what it means for the codebase21:38
kota_notmyname: got it21:38
notmynameFWIW, I'm not totally sold on the idea, nor am I rushing to make our next release a checkpoint one. but I love the conversation, and I'm happy to be convinced either way (doing a checkpoint or not)21:39
kota_thx21:39
notmynamekota_: I normally try to leave out idioms and colloquialisms. it's my fault. thanks for asking me to clarify21:39
kota_ok ok. I'm sure I can explain the concept and discuss what we (in company) want!21:40
notmyname#topic updates on current work21:40
*** openstack changes topic to "updates on current work (Meeting topic: swift)"21:40
timburkesoemthing tells me this discussion will continue into Dublin...21:40
notmynamelet's review some ongoing work21:40
*** pchavva has quit IRC21:40
notmynamecontainer sharding21:40
notmynamemattoliverau: acoles: ?21:40
acolesprogress continues...21:41
notmynameanything blocking you that the rest of us can help with?21:41
acolessince last week we decided to reduce scope on listings while sharding is in progress21:41
acoleswhich has helped21:41
notmynamegreat!21:41
acolesI have a long patch chain that would be great to get merged, mattoliverau and timburke are helping with that21:42
notmynameok21:42
notmynamemattoliverau: timburke: anything to add?21:42
*** slaweq_ has joined #openstack-meeting21:42
mattoliverauAnd people should join in discussions on Trello or etherpad if there interested21:42
acolesoh, today I started another etherpad to start to doc the internal API changes, maybe help newcomers21:43
mattoliverauNice21:43
acoleshttps://etherpad.openstack.org/p/deep-containers-apis21:43
acoles#link https://etherpad.openstack.org/p/deep-containers-apis21:43
notmynamethanks21:44
mattoliverauMy week hasn't been the most shard friendly week, but will hopefully spend more time post release reviews (my time is limited :()21:44
claygi was catching up on checkpoint releases21:44
notmynamemattoliverau: and you'll be at lca next week, right? so not too much hands-on-keyboard time there21:45
acolesBTW, all sharding docs are linked from https://etherpad.openstack.org/p/deep-containers21:45
*** simon-AS5591 has quit IRC21:45
acolesso that is the mother-ship ^^21:45
mattoliverauYup LCA next week \o/21:45
claygI hate to say that if you're running swift from 2015 upgrading to master isn't exactly something I'd have a high confidence in going great anyway... it's more about putting a name to reality21:45
notmynameacoles: I added a link to that parent etherpad to the ideas wiki21:46
notmynamekota_: any progress on s3api this week?21:46
kota_i update the logger patch according to tim's comment, and waiting his review21:46
notmynameok21:47
notmynamem_kazuhiro: rledisez: any updates for us on the task queue?21:47
timburkei knew there was another patch i should review!21:47
kota_on the functional, I 've started to make sure what's the status of tdasilva21:47
*** slaweq_ has quit IRC21:47
kota_since yesterday21:47
m_kazuhiroI'm working at patch 51738921:47
patchbothttps://review.openstack.org/#/c/517389/ - swift - Update object-expirer to use general task queue sy...21:47
m_kazuhiroI implemented all tests so I removed 'WIP' from the patch.21:48
kota_nice21:48
notmynamenice21:48
notmynamem_kazuhiro: anything currently blocking you, aside from reviews?21:49
m_kazuhiroNothing. Review is what I want.21:50
*** fnaval has quit IRC21:50
notmynamerledisez: how's progress on LOSF work?21:50
rledisezpretty good. we should make a (big) move to put the code on production in the next 2 or 3 weeks21:51
mattoliverauWow21:51
rledisezso, we may be running a whole on production wiht LOSF by the next PTG21:52
mattoliverauCool21:52
notmynamethat is "wow" :-)21:52
notmynamespeaking of the PTG...21:52
rledisezalso, a new developer will join our team in march, he will assist alexandre in upstreaming the code21:52
notmynamethat's coming up soon21:52
notmynamerledisez: cool21:52
notmynamethe PTG is at the end of february21:53
notmynameI'd like to start organizing topics in two weeks21:53
claygrledisez: I haven't heard anything about how alexandre ended up dealing with the eventlet + grpc issues he was dealing with?21:54
notmynamealso, I'll be out next wednesday. would someone like to run the meeting? or would you like to skip it?21:54
mattoliverauWell really you'll just be on my time21:54
mattoliverauBut I'll be busy so happy to akio21:55
mattoliverau*skip21:55
rledisezclayg: right now there is no real solution. we pinned a specific version of grpc that works (partialy, but enough for us) with eventlet. that's not a long term solution. either droping eventlet or changing grpc for another protocol is the way to go21:56
*** jamesmcarthur has quit IRC21:56
notmynameI think everyone already logged off. so that answers that about skipping next week :-)21:57
joeljwright:)21:57
notmynamemeet again in two weeks. jan 31, 2100UTC21:57
notmynamethanks for your work on swift. thanks for coming today21:58
notmyname#endmeeting21:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"21:58
openstackMeeting ended Wed Jan 17 21:58:16 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-01-17-21.00.html21:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-01-17-21.00.txt21:58
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2018/swift.2018-01-17-21.00.log.html21:58
*** timburke has left #openstack-meeting21:59
*** jamesmcarthur has joined #openstack-meeting21:59
*** rbowen has quit IRC21:59
*** joeljwright has left #openstack-meeting22:00
*** david-lyle has quit IRC22:00
*** m_kazuhiro has quit IRC22:01
*** acoles has left #openstack-meeting22:01
*** torgomatic has left #openstack-meeting22:01
*** rcernin has joined #openstack-meeting22:02
*** rmcall_ has joined #openstack-meeting22:06
*** rmcall_ has quit IRC22:14
*** slaweq_ has joined #openstack-meeting22:14
*** jamesmcarthur has quit IRC22:15
*** claudiub has quit IRC22:15
*** jamesmcarthur has joined #openstack-meeting22:16
*** slaweq_ has quit IRC22:20
*** e0ne has quit IRC22:20
*** slaweq has quit IRC22:23
*** e0ne has joined #openstack-meeting22:26
*** e0ne_ has joined #openstack-meeting22:27
*** liyi has joined #openstack-meeting22:28
*** e0ne has quit IRC22:30
*** VW has joined #openstack-meeting22:31
*** VW_ has quit IRC22:31
*** e0ne_ has quit IRC22:32
*** liyi has quit IRC22:32
*** diablo_rojo has joined #openstack-meeting22:34
*** VW has quit IRC22:37
*** VW has joined #openstack-meeting22:38
*** VW has quit IRC22:42
*** rmcall_ has joined #openstack-meeting22:50
*** david-lyle has joined #openstack-meeting22:51
*** slaweq has joined #openstack-meeting22:54
*** jkilpatr has quit IRC22:54
*** slaweq has quit IRC22:55
*** archit has quit IRC22:57
*** jamesmcarthur has quit IRC23:00
*** jamesmcarthur has joined #openstack-meeting23:01
*** edmondsw has quit IRC23:02
*** hongbin has quit IRC23:06
*** cdub has quit IRC23:14
*** persia has quit IRC23:18
*** persia_ has quit IRC23:18
*** persia has joined #openstack-meeting23:18
*** persia_ has joined #openstack-meeting23:18
*** jamesmcarthur has quit IRC23:20
*** jamesmcarthur has joined #openstack-meeting23:22
*** slaweq has joined #openstack-meeting23:26
*** jamesmcarthur has quit IRC23:27
*** felipemonteiro has quit IRC23:27
*** felipemonteiro has joined #openstack-meeting23:27
*** mjturek has quit IRC23:28
*** slaweq has quit IRC23:31
*** rmcall_ has quit IRC23:32
*** jamesmcarthur has joined #openstack-meeting23:50
*** persia has quit IRC23:53
*** persia_ has quit IRC23:53
*** powerd has quit IRC23:55
*** awaugama has quit IRC23:56
*** jamesmcarthur has quit IRC23:57
*** gyee has quit IRC23:58
*** slaweq has joined #openstack-meeting23:58

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