Wednesday, 2016-08-31

*** liuhanxi has joined #openstack-meeting00:02
*** aeng has quit IRC00:03
*** tinwood has quit IRC00:04
*** baoli has joined #openstack-meeting00:04
*** tinwood has joined #openstack-meeting00:05
*** baoli_ has joined #openstack-meeting00:05
*** leeantho has quit IRC00:05
*** zhurong has quit IRC00:06
*** takashi has joined #openstack-meeting00:07
*** baoli has quit IRC00:09
*** ivar-laz_ has joined #openstack-meeting00:13
*** yamahata has quit IRC00:14
*** sdake has joined #openstack-meeting00:16
*** ivar-lazzaro has quit IRC00:17
*** ivar-laz_ has quit IRC00:18
*** manikanta_tadi has joined #openstack-meeting00:19
*** aeng has joined #openstack-meeting00:21
*** jungleboyj has joined #openstack-meeting00:21
*** thorst has joined #openstack-meeting00:21
*** sdake has quit IRC00:21
*** ivc_ has quit IRC00:22
*** Swami__ has joined #openstack-meeting00:24
*** Julien-zte has joined #openstack-meeting00:25
*** sdake has joined #openstack-meeting00:25
*** takashi has quit IRC00:26
*** dfflanders has joined #openstack-meeting00:26
*** Swami has quit IRC00:28
*** sdague has joined #openstack-meeting00:32
*** tonytan4ever has quit IRC00:33
*** rfolco has joined #openstack-meeting00:33
*** Wenzhi has joined #openstack-meeting00:33
*** sindhu has quit IRC00:34
*** mtanino has quit IRC00:34
*** thorst_ has joined #openstack-meeting00:37
*** spzala has joined #openstack-meeting00:39
*** thorst has quit IRC00:39
*** liuhanxi has quit IRC00:40
*** pvaneck has quit IRC00:41
*** Suyi_1 has quit IRC00:43
*** spzala has quit IRC00:43
*** yamamoto_ has joined #openstack-meeting00:44
*** zzxwill has joined #openstack-meeting00:47
*** yamahata has joined #openstack-meeting00:47
*** banix has joined #openstack-meeting00:51
*** zzxwill has quit IRC00:52
*** asettle has joined #openstack-meeting00:54
*** delattec has quit IRC00:56
*** manikanta_tadi has quit IRC00:58
*** asettle has quit IRC00:59
*** Julien-z_ has joined #openstack-meeting01:02
*** Julien-zte has quit IRC01:03
*** salv-orlando has joined #openstack-meeting01:03
*** ivc_ has joined #openstack-meeting01:03
*** kota_ has left #openstack-meeting01:05
*** Apoorva has quit IRC01:06
*** gongysh has joined #openstack-meeting01:06
*** shashank_hegde has quit IRC01:06
*** fnaval has quit IRC01:07
*** hongbin has joined #openstack-meeting01:07
*** Apoorva has joined #openstack-meeting01:09
*** salv-orlando has quit IRC01:11
*** ronghui has quit IRC01:11
*** salv-orlando has joined #openstack-meeting01:13
*** zhurong has joined #openstack-meeting01:13
*** zzxwill has joined #openstack-meeting01:15
*** donghao has joined #openstack-meeting01:17
*** salv-orlando has quit IRC01:17
*** donghao has quit IRC01:20
*** dmorita has quit IRC01:21
*** david-lyle_ has joined #openstack-meeting01:23
*** donghao has joined #openstack-meeting01:24
*** baoli_ has quit IRC01:24
*** fzdarsky_ has joined #openstack-meeting01:25
*** fnaval has joined #openstack-meeting01:27
*** jckasper has quit IRC01:27
*** rfolco has quit IRC01:28
*** jckasper has joined #openstack-meeting01:28
*** Swami has joined #openstack-meeting01:28
*** fzdarsky|afk has quit IRC01:29
*** Apoorva has quit IRC01:30
*** yamamoto_ has quit IRC01:31
*** ronghui has joined #openstack-meeting01:31
*** Swami__ has quit IRC01:32
*** jckasper has quit IRC01:32
*** sdague has quit IRC01:32
*** tonytan4ever has joined #openstack-meeting01:33
*** liuhanxi has joined #openstack-meeting01:35
*** rrecio has quit IRC01:35
*** dmacpher has joined #openstack-meeting01:36
*** thorst_ has quit IRC01:38
*** yamamoto_ has joined #openstack-meeting01:38
*** thorst has joined #openstack-meeting01:38
*** tonytan4ever has quit IRC01:38
*** yuanying has quit IRC01:45
*** yuanying has joined #openstack-meeting01:46
*** thorst has quit IRC01:46
*** spzala has joined #openstack-meeting01:55
*** yulong|away is now known as liuyulong01:55
*** ivar-lazzaro has joined #openstack-meeting01:59
*** vishwanathj has quit IRC01:59
*** zhurong_ has joined #openstack-meeting01:59
*** zhurong has quit IRC02:02
*** diablo_rojo has joined #openstack-meeting02:03
*** esumerfd has joined #openstack-meeting02:04
*** zzxwill has quit IRC02:04
*** ivc_ has quit IRC02:04
*** esumerfd has quit IRC02:08
*** s3wong has quit IRC02:08
*** saggi has quit IRC02:10
*** aeng has quit IRC02:10
*** unicell has quit IRC02:13
*** Kevin_Zheng has joined #openstack-meeting02:13
*** sdake has quit IRC02:16
*** shashank_hegde has joined #openstack-meeting02:16
*** sdake has joined #openstack-meeting02:17
*** saggi has joined #openstack-meeting02:20
*** Sukhdev has joined #openstack-meeting02:23
*** aeng has joined #openstack-meeting02:23
*** Swami__ has joined #openstack-meeting02:25
*** spzala has quit IRC02:26
*** Swami has quit IRC02:28
*** Swami_ has quit IRC02:29
*** Swami has joined #openstack-meeting02:29
*** ivar-lazzaro has quit IRC02:29
*** mriedem has quit IRC02:31
*** david-lyle_ has quit IRC02:31
*** gyee has quit IRC02:31
*** zzxwill has joined #openstack-meeting02:32
*** epico has joined #openstack-meeting02:32
*** baoli has joined #openstack-meeting02:34
*** fnaval has quit IRC02:34
*** tonytan4ever has joined #openstack-meeting02:34
*** yamahata has quit IRC02:35
*** iyamahat has quit IRC02:36
*** dimtruck is now known as zz_dimtruck02:37
*** fnaval has joined #openstack-meeting02:38
*** tonytan4ever has quit IRC02:38
*** tonytan4ever has joined #openstack-meeting02:38
*** baoli has quit IRC02:40
*** zzxwill has quit IRC02:43
*** thorst has joined #openstack-meeting02:45
*** reed_ has joined #openstack-meeting02:46
*** reed_ has quit IRC02:47
*** yamamoto_ has quit IRC02:48
*** thorst has quit IRC02:52
*** hongbin has quit IRC02:52
*** zzxwill has joined #openstack-meeting02:53
*** banix has quit IRC02:57
*** ronghui has quit IRC03:00
*** mriedem has joined #openstack-meeting03:00
*** jamespage has quit IRC03:01
*** jamespag` has joined #openstack-meeting03:01
*** mriedem has quit IRC03:01
*** mriedem has joined #openstack-meeting03:01
*** yamamoto_ has joined #openstack-meeting03:02
*** donghao has quit IRC03:12
*** ronghui has joined #openstack-meeting03:13
*** mickeys has quit IRC03:13
*** donghao has joined #openstack-meeting03:14
*** salv-orlando has joined #openstack-meeting03:17
*** bobh has joined #openstack-meeting03:21
*** dmorita has joined #openstack-meeting03:21
*** anilvenkata has joined #openstack-meeting03:21
*** yamamoto_ has quit IRC03:22
*** yamamoto_ has joined #openstack-meeting03:22
*** yamamoto_ has quit IRC03:22
*** salv-orlando has quit IRC03:24
*** yamamoto_ has joined #openstack-meeting03:25
*** dmorita has quit IRC03:26
*** aeng has quit IRC03:26
*** Ravikiran_K has joined #openstack-meeting03:27
*** ayoung has quit IRC03:27
*** prateek_ has joined #openstack-meeting03:27
*** yamamoto_ has quit IRC03:29
*** prateek has joined #openstack-meeting03:30
*** parora has quit IRC03:30
*** prateek_ has quit IRC03:33
*** RuiChen has joined #openstack-meeting03:35
*** shashank_hegde has quit IRC03:36
*** woodster_ has quit IRC03:39
*** dmorita has joined #openstack-meeting03:42
*** sindhu has joined #openstack-meeting03:42
*** aeng has joined #openstack-meeting03:43
*** bobh has quit IRC03:45
*** shashank_hegde has joined #openstack-meeting03:45
*** dmorita has quit IRC03:46
*** thorst has joined #openstack-meeting03:50
*** cody-somerville has quit IRC03:51
*** zzxwill has quit IRC03:51
*** cody-somerville has joined #openstack-meeting03:52
*** jckasper has joined #openstack-meeting03:52
*** jckasper has quit IRC03:57
*** thorst has quit IRC03:57
*** galstrom_zzz is now known as galstrom03:57
*** donghao has quit IRC03:58
*** tochi has quit IRC03:59
*** fnaval_ has joined #openstack-meeting04:00
*** padkrish has joined #openstack-meeting04:00
*** tochi has joined #openstack-meeting04:01
*** prateek has quit IRC04:03
*** fnaval has quit IRC04:03
*** prateek has joined #openstack-meeting04:04
*** ijw has quit IRC04:04
*** zzxwill has joined #openstack-meeting04:05
*** esumerfd has joined #openstack-meeting04:06
*** cartik has joined #openstack-meeting04:07
*** ijw has joined #openstack-meeting04:08
*** cody-somerville has quit IRC04:08
*** cody-somerville has joined #openstack-meeting04:08
*** cody-somerville has quit IRC04:08
*** cody-somerville has joined #openstack-meeting04:08
*** esumerfd has quit IRC04:11
*** crinkle_ has joined #openstack-meeting04:16
*** njohnsto_ has joined #openstack-meeting04:16
*** sankarshan_away is now known as sankarshan04:17
*** cschwede has quit IRC04:17
*** crinkle has quit IRC04:17
*** cschwede has joined #openstack-meeting04:17
*** kaisers has quit IRC04:17
*** kaisers has joined #openstack-meeting04:19
*** sankarshan is now known as sankarshan_away04:20
*** su_zhang has joined #openstack-meeting04:26
*** spzala has joined #openstack-meeting04:26
*** salv-orlando has joined #openstack-meeting04:27
*** ijw has quit IRC04:27
*** ijw has joined #openstack-meeting04:28
*** yamamoto_ has joined #openstack-meeting04:29
*** zzxwill has quit IRC04:29
*** spzala has quit IRC04:31
*** salv-orlando has quit IRC04:32
*** ijw has quit IRC04:33
*** yuanying has quit IRC04:34
*** yuanying has joined #openstack-meeting04:34
*** fnaval has joined #openstack-meeting04:35
*** zzxwill has joined #openstack-meeting04:36
*** links has joined #openstack-meeting04:36
*** coolsvap_ has joined #openstack-meeting04:36
*** Hosam has joined #openstack-meeting04:37
*** fnaval_ has quit IRC04:39
*** padkrish has quit IRC04:40
*** padkrish has joined #openstack-meeting04:41
*** sarob has joined #openstack-meeting04:41
*** padkrish has quit IRC04:41
*** njohnsto_ has quit IRC04:42
*** zzxwill has quit IRC04:46
*** sarob has quit IRC04:46
*** su_zhang has quit IRC04:47
*** prateek has quit IRC04:48
*** su_zhang_ has joined #openstack-meeting04:50
*** egallen has joined #openstack-meeting04:51
*** zzxwill has joined #openstack-meeting04:52
*** su_zhang_ has quit IRC04:52
*** su_zhang has joined #openstack-meeting04:53
*** thorst has joined #openstack-meeting04:54
*** ijw has joined #openstack-meeting04:55
*** Julien-z_ has quit IRC04:56
*** su_zhang has quit IRC04:57
*** asettle has joined #openstack-meeting04:57
*** donghao has joined #openstack-meeting04:59
*** Fdaisuke has quit IRC04:59
*** ijw has quit IRC05:00
*** anilvenkata has quit IRC05:01
*** Fdaisuke has joined #openstack-meeting05:01
*** claudiub has joined #openstack-meeting05:01
*** thorst has quit IRC05:01
*** prateek has joined #openstack-meeting05:02
*** asettle has quit IRC05:02
*** yamahata has joined #openstack-meeting05:04
*** donghao has quit IRC05:04
*** yamahata has quit IRC05:06
*** cdub has joined #openstack-meeting05:09
*** sdake has quit IRC05:10
*** sdake_ has joined #openstack-meeting05:10
*** salv-orlando has joined #openstack-meeting05:13
*** galstrom is now known as galstrom_zzz05:14
*** ilyashakhat has joined #openstack-meeting05:16
*** Leom has joined #openstack-meeting05:16
*** anilvenkata has joined #openstack-meeting05:18
*** yonglihe has joined #openstack-meeting05:22
*** fnaval_ has joined #openstack-meeting05:23
*** hichihara has joined #openstack-meeting05:24
*** hichihara has quit IRC05:24
*** roxanaghe has joined #openstack-meeting05:25
*** fnaval has quit IRC05:25
*** sdake_ has quit IRC05:26
*** sindhu has quit IRC05:28
*** Leom has quit IRC05:29
*** ilyashakhat has quit IRC05:30
*** shu-mutou has quit IRC05:30
*** roxanaghe has quit IRC05:32
*** sdake has joined #openstack-meeting05:33
*** Na3iL has joined #openstack-meeting05:34
*** saju_m has joined #openstack-meeting05:36
*** martines has quit IRC05:37
*** cdub has quit IRC05:38
*** sridharg has joined #openstack-meeting05:38
*** cdub has joined #openstack-meeting05:39
*** Julien-zte has joined #openstack-meeting05:39
*** martines has joined #openstack-meeting05:44
*** dbecker has joined #openstack-meeting05:46
*** kaz has joined #openstack-meeting05:46
*** kaz has left #openstack-meeting05:46
*** mtanino has joined #openstack-meeting05:48
*** cdub has quit IRC05:53
*** _nadya_ has joined #openstack-meeting05:54
*** armax has quit IRC05:56
*** donghao has joined #openstack-meeting05:56
*** sandanar has joined #openstack-meeting05:57
*** ilyashakhat has joined #openstack-meeting05:57
*** aeng has quit IRC05:57
*** markvoelker has joined #openstack-meeting05:58
*** _nadya_ has quit IRC05:59
*** thorst has joined #openstack-meeting06:00
*** cartik has quit IRC06:00
*** nkrinner_afk is now known as nkrinner06:01
*** bvandenh has quit IRC06:04
*** Swami has quit IRC06:04
*** Swami__ has quit IRC06:04
*** donghao has quit IRC06:05
*** thorst has quit IRC06:07
*** salv-orl_ has joined #openstack-meeting06:07
*** janki has joined #openstack-meeting06:09
*** lpetrut has joined #openstack-meeting06:09
*** salv-orlando has quit IRC06:10
*** aeng has joined #openstack-meeting06:10
*** ianychoi has quit IRC06:12
*** sankarshan_away is now known as sankarshan06:12
*** ianychoi has joined #openstack-meeting06:12
*** esumerfd has joined #openstack-meeting06:13
*** unicell has joined #openstack-meeting06:13
*** pcaruana has joined #openstack-meeting06:15
*** yuval has joined #openstack-meeting06:16
*** claudiub has quit IRC06:17
*** esumerfd has quit IRC06:18
*** ilyashakhat has quit IRC06:19
*** andreas_s has joined #openstack-meeting06:20
*** rcernin has joined #openstack-meeting06:21
*** sdake has quit IRC06:22
*** xinwu has joined #openstack-meeting06:23
*** sheel has joined #openstack-meeting06:24
*** salv-orl_ has quit IRC06:24
*** xinwu has left #openstack-meeting06:27
*** ijw has joined #openstack-meeting06:28
*** azbiswas has joined #openstack-meeting06:28
*** amotoki has joined #openstack-meeting06:29
*** cartik has joined #openstack-meeting06:31
*** mtanino has quit IRC06:32
*** watanabe_isao has joined #openstack-meeting06:32
*** neel has joined #openstack-meeting06:34
*** markvoelker has quit IRC06:34
*** anilvenkata has quit IRC06:38
*** diablo_rojo has quit IRC06:39
*** saju_m has quit IRC06:40
*** mikelk has joined #openstack-meeting06:45
*** ub has joined #openstack-meeting06:49
*** ilyashakhat has joined #openstack-meeting06:49
*** ijw has quit IRC06:53
*** ilyashakhat has quit IRC06:54
*** bvandenh has joined #openstack-meeting06:55
*** rasca has joined #openstack-meeting06:55
*** amotoki has quit IRC06:56
*** neel has left #openstack-meeting06:57
*** kaminohana has quit IRC07:03
*** lpetrut has quit IRC07:03
*** sudipto has joined #openstack-meeting07:04
*** sudipto_ has joined #openstack-meeting07:04
*** manikanta_tadi has joined #openstack-meeting07:05
*** thorst has joined #openstack-meeting07:05
*** egallen has quit IRC07:05
*** liuyulong has quit IRC07:06
*** liuyulong has joined #openstack-meeting07:07
*** tesseract- has joined #openstack-meeting07:08
*** thorst has quit IRC07:12
*** toscalix has joined #openstack-meeting07:13
*** ihrachys has joined #openstack-meeting07:14
*** sshnaidm|afk is now known as sshnaidm07:15
*** amotoki has joined #openstack-meeting07:16
*** nmagnezi has joined #openstack-meeting07:18
*** hichihara has joined #openstack-meeting07:22
*** bvandenh has quit IRC07:23
*** hichihara has quit IRC07:24
*** spzala has joined #openstack-meeting07:26
*** duvarenkov_ has quit IRC07:29
*** jlanoux has joined #openstack-meeting07:29
*** duvarenkov has joined #openstack-meeting07:30
*** markvoelker has joined #openstack-meeting07:30
*** ljxiash has joined #openstack-meeting07:30
*** hichihara has joined #openstack-meeting07:31
*** sudipto_ has quit IRC07:31
*** sudipto has quit IRC07:31
*** spzala has quit IRC07:31
*** numans has joined #openstack-meeting07:31
*** ebalduf has quit IRC07:34
*** markvoelker has quit IRC07:35
*** jamespag` is now known as jamespage07:35
*** dlahn has left #openstack-meeting07:35
*** dmacpher has quit IRC07:36
*** sudipto has joined #openstack-meeting07:36
*** sudipto_ has joined #openstack-meeting07:36
*** egallen has joined #openstack-meeting07:36
*** salv-orlando has joined #openstack-meeting07:39
*** sudipto has quit IRC07:41
*** sudipto_ has quit IRC07:41
*** spzala has joined #openstack-meeting07:42
*** _nadya_ has joined #openstack-meeting07:43
*** JRobinson__ has quit IRC07:43
*** fzdarsky_ is now known as fzdarsky07:43
*** sudipto has joined #openstack-meeting07:44
*** hashar has joined #openstack-meeting07:44
*** zhurong_ has quit IRC07:45
*** egallen has quit IRC07:46
*** sudipto has quit IRC07:46
*** jlanoux has quit IRC07:47
*** eezhova has joined #openstack-meeting07:47
*** spzala has quit IRC07:47
*** zhurong has joined #openstack-meeting07:48
*** dmacpher has joined #openstack-meeting07:49
*** bvandenh has joined #openstack-meeting07:50
*** hichihara has quit IRC07:51
*** Sukhdev has quit IRC07:52
*** xinwu has joined #openstack-meeting07:52
*** dbecker has quit IRC07:53
*** jckasper has joined #openstack-meeting07:54
*** zzxwill has quit IRC07:54
*** zzxwill has joined #openstack-meeting07:56
*** priteau has joined #openstack-meeting07:57
*** xinwu has quit IRC07:57
*** shashank_hegde has quit IRC07:57
*** spzala has joined #openstack-meeting07:58
*** jckasper has quit IRC07:59
*** mugsie|alt has quit IRC08:00
*** mugsie__ has quit IRC08:00
*** hichihara has joined #openstack-meeting08:00
*** mugsie|alt has joined #openstack-meeting08:01
*** markvoelker has joined #openstack-meeting08:01
*** matthewbodkin has joined #openstack-meeting08:01
*** r-mibu has quit IRC08:02
*** mugsie_ has joined #openstack-meeting08:03
*** spzala has quit IRC08:03
*** azbiswas has quit IRC08:03
*** matrohon has joined #openstack-meeting08:05
*** markvoelker has quit IRC08:07
*** thorst has joined #openstack-meeting08:09
*** claudiub has joined #openstack-meeting08:11
*** ljxiash has quit IRC08:12
*** rossella_s has joined #openstack-meeting08:16
*** toscalix has quit IRC08:16
*** imcsk8 has quit IRC08:17
*** imcsk8_ has joined #openstack-meeting08:17
*** lbrune has joined #openstack-meeting08:17
*** thorst has quit IRC08:17
*** toscalix has joined #openstack-meeting08:20
*** mickeys has joined #openstack-meeting08:20
*** ljxiash has joined #openstack-meeting08:21
*** e0ne has joined #openstack-meeting08:24
*** liuhanxi has quit IRC08:24
*** mickeys has quit IRC08:25
*** gongysh has quit IRC08:26
*** oomichi has quit IRC08:27
*** oomichi has joined #openstack-meeting08:29
*** markvoelker has joined #openstack-meeting08:29
*** lbrune1 has joined #openstack-meeting08:30
*** lbrune has quit IRC08:31
*** eezhova has quit IRC08:31
*** rossella_s has quit IRC08:31
*** gongysh_ has quit IRC08:31
*** r-mibu has joined #openstack-meeting08:33
*** Julien-zte has quit IRC08:33
*** markvoelker has quit IRC08:34
*** adiantum has joined #openstack-meeting08:34
*** jaypipes has joined #openstack-meeting08:35
*** anilvenkata has joined #openstack-meeting08:36
*** Julien-zte has joined #openstack-meeting08:36
*** ihrachys has quit IRC08:37
*** xinwu has joined #openstack-meeting08:38
*** samueldmq has quit IRC08:38
*** samueldmq has joined #openstack-meeting08:39
*** xinwu has quit IRC08:43
*** sarob has joined #openstack-meeting08:43
*** esumerfd has joined #openstack-meeting08:44
*** gongysh_ has joined #openstack-meeting08:44
*** ivc_ has joined #openstack-meeting08:46
*** bzhao has quit IRC08:46
*** dmorita has joined #openstack-meeting08:46
*** bzhao has joined #openstack-meeting08:47
*** sarob has quit IRC08:48
*** esumerfd has quit IRC08:49
*** dbecker has joined #openstack-meeting08:49
*** senk has joined #openstack-meeting08:50
*** ivc_ has quit IRC08:50
*** sudipto has joined #openstack-meeting08:51
*** watanabe_isao has quit IRC08:51
*** dmorita has quit IRC08:51
*** lbrune has joined #openstack-meeting08:52
*** lbrune1 has quit IRC08:54
*** numans has quit IRC08:55
*** oneswig has joined #openstack-meeting08:57
*** asettle has joined #openstack-meeting08:58
*** lpetrut has joined #openstack-meeting08:58
*** dariov has joined #openstack-meeting08:58
*** hichihara has quit IRC08:59
*** markvoelker has joined #openstack-meeting08:59
*** Wenzhi has quit IRC09:00
oneswig#startmeeting scientific-wg09:00
openstackMeeting started Wed Aug 31 09:00:49 2016 UTC and is due to finish in 60 minutes.  The chair is oneswig. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: scientific-wg)"09:00
openstackThe meeting name has been set to 'scientific_wg'09:00
oneswigGreetings all09:01
dariovhello there!09:01
senkHello o/09:01
priteauHi o/09:01
oneswig#link today's agenda (such as it is) is here: https://wiki.openstack.org/wiki/Scientific_working_group09:01
oneswigBlair has been in touch, he's just returning from holidays, might be able to join us later09:02
*** zzxwill has quit IRC09:02
oneswigBefore we begin, any items to add?09:02
*** jakeyip has joined #openstack-meeting09:02
*** lpetrut has quit IRC09:02
*** lpetrut1 has joined #openstack-meeting09:02
oneswigI had one - the CFP for HPCloudSys 2016 in Luxembourg closes this week09:03
oneswig#link HPCloudSys2016 is here http://2016cloudcom.ux.uis.no/conf/workshops/hpcloudsys.html09:03
*** RichB has joined #openstack-meeting09:04
*** markvoelker has quit IRC09:04
*** azbiswas has joined #openstack-meeting09:04
oneswigOK #topic Summit Scientific OpenStack guide09:04
oneswigFlanders from the Foundation was in touch with an outreachy idea09:04
oneswigTo scan the schedule and pick out some topics WG members and scientific compute uses in general might be interested in09:05
*** lpetrut1 is now known as lpetrut09:05
priteauThat's a very good idea! I haven't gone through the schedule yet09:05
*** nijaba has quit IRC09:05
oneswigThen generate a SuperUser article and/or mailing of those09:05
oneswigpriteau: me neither!09:06
oneswig#link https://www.openstack.org/summit/austin-2016/categories/ - schedule's somewhere off this page09:06
oneswigIn the course of this meeting, can we browse and pick out items of interest09:07
*** nijaba has joined #openstack-meeting09:07
*** nijaba has quit IRC09:07
*** nijaba has joined #openstack-meeting09:07
*** electrofelix has joined #openstack-meeting09:07
priteauthe URL says "austin", but changing it to barcelona only changes the header09:07
priteauthe rest of the content is the same09:08
oneswigGood grief, you're right!09:08
oneswigooops09:08
priteau#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/ Barcelona summit schedule09:08
*** andreykurilin has quit IRC09:09
*** azbiswas has quit IRC09:09
oneswig#link GlusterFS in OpenStack "In this presentation we will talk about the journey we are still on in finding the best fit for a file system inside a large fully-orchestrated cloud application stack" https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15987/clustered-file-systems-in-your-application-stack09:09
*** numans has joined #openstack-meeting09:10
dariovwow, that looks interesting to us09:11
dariovI’ll tell our people to drop by :-)09:11
oneswig#link We have an interest in using Monasca for high performance telemetry, might like to sit in on this one https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15166/monasca-one-year-later09:12
*** liuhanxi has joined #openstack-meeting09:13
oneswigIf anyone sees a talk they'd find interesting for research computing, please chip in!09:14
*** ihrachys has joined #openstack-meeting09:14
*** thorst has joined #openstack-meeting09:14
priteau#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/full/ Full Barcelona summit schedule on a single page09:15
oneswig#link realistically I think I'll learn a lot from "BrokenStack: failure stories" https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15448/brokenstack-openstack-failure-stories09:15
dariovlol09:16
priteauthere are 5 talks with HPC in the title09:16
oneswig#link A talk from CERN is always interesting and networking is something they've historically struggled with, it'll be interesting to see their solution https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15865/neutron-at-cern-moving-thousands-of-production-nodes-from-nova-network09:16
oneswigpriteau: any picks from those?09:17
priteau#link Image is Everything: Dynamic HPC VM Repositories using Murano https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1616109:18
priteau#link Neutron and SLURM: Software-defined Networking for HPC Clusters https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1545409:18
priteau#link “Spartan”, a HPC - Cloud Hybrid: Delivering Performance and Flexibility https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1654009:18
priteauall of them really :-)09:18
oneswigNice!09:19
priteaublair's talk too of course09:19
oneswig#link Blair's talk on Lustre https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16548/lustre-integration-for-hpc-on-openstack-at-cambridge-and-monash09:20
oneswigAny more suggestions?09:20
*** jlanoux has joined #openstack-meeting09:20
priteau#link HPC, Unikernels and OpenStack https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/1587909:20
oneswigpriteau: that's one I'm particularly interested in, thanks for reminding!09:21
*** eezhova has joined #openstack-meeting09:21
oneswigOK, keep browsing, lets move the topic on09:21
oneswig#topic OpenStack / HPC white papers09:21
*** openstack changes topic to "OpenStack / HPC white papers (Meeting topic: scientific-wg)"09:21
*** lbrune has quit IRC09:21
oneswigSo over the summer I've been gathering research on five white paper topics on OpenStack and HPC09:22
*** thorst has quit IRC09:22
oneswigThree are now in draft form (phew), one's half way and one's not started yet.09:22
oneswigWhat I'm looking for is subject matter experts on the various topics09:23
oneswigThe two remaining are bare metal infrastructure and high performance data09:23
oneswigpriteau: you wouldn't happen to know anyone who works on a bare metal infrastructure system would you ? :-)09:23
*** brnelson has quit IRC09:23
*** brnelson has joined #openstack-meeting09:24
priteauoneswig: I contacted one of our Chameleon users who did a performance comparison of bare-metal vs KVM vs Docker, but no answer :(09:25
oneswigpriteau: that's OK I think I have enough on overhead, including your previous introductions.09:25
oneswig#link HPC and the overhead of virtualisation https://docs.google.com/document/d/1xJJKPltk-ScA4uKrPVnIAHQRptzgViJNMq1kNLWAQTE/edit?usp=sharing09:25
priteauI would be happy to be a reviewer on the bare-metal topic09:25
*** bbzhao has joined #openstack-meeting09:26
*** zhongjun_ has quit IRC09:26
*** lock_ has joined #openstack-meeting09:26
oneswig#link OpenStack and HPC network fabrics https://docs.google.com/document/d/1d2nOxPQPARNhmnc0hXBIMW9c_bjDyaUkUZAzMBNPfEA/edit?usp=sharing09:26
oneswig#link OpenStack and HPC workload management https://docs.google.com/document/d/1dbN6HRWQuuETqPIw5qYM8Ya6f3RD1WNbGr_hg2CyHPw/edit?usp=sharing09:26
dariovI’m afraid we can’t help you on this, guys09:27
oneswigpriteau: thanks, appreciate that.  Can we make Chameleon into a case study on that?09:27
* dariov feeling a little bit useless09:27
*** zhongjun_ has joined #openstack-meeting09:27
oneswigdariov: the articles I'm hoping are useful for people who know about HPC but want to learn more about how it fits into OpenStack. That's the target audience09:28
priteauoneswig: If Chameleon fits your requirements for this white paper, I would be happy to!09:28
oneswigpriteau: Great, thanks.  I'll get my act together and be in touch...09:28
*** markvoelker has joined #openstack-meeting09:29
*** saju_m has joined #openstack-meeting09:29
*** bzhao has quit IRC09:29
priteauI wasn't sure if the testbed itself was a good fit (rather than the research users do with), since it is a very specific use case09:29
priteauI guess it will be clearer once I have read your drafts09:29
*** mars has joined #openstack-meeting09:29
*** ianychoi has quit IRC09:29
oneswigpriteau: Well it is but what I've been looking for is some diversity between the data points, and you're not Bridges and you're not Aurora so that's even better :-)09:29
dariovoneswig, then I’m your perfect guinea pig09:30
oneswigdariov: any input is gratefully appreciated, thank you09:30
oneswigMove on?09:31
oneswig#topic Working group activities at Barcelona09:31
*** openstack changes topic to "Working group activities at Barcelona (Meeting topic: scientific-wg)"09:31
*** mars has quit IRC09:32
*** andreykurilin has joined #openstack-meeting09:32
oneswigSomebody last week suggested the WG meeting might work well with a poster session.09:32
oneswigI think this is a good idea, especially if we get a good number09:32
oneswigThe concern there being it's a bit late to put something together09:32
oneswigAny thoughts on this?09:33
*** jakeyip has quit IRC09:33
*** BobBall has left #openstack-meeting09:33
*** andreykurilin has left #openstack-meeting09:33
*** markvoelker has quit IRC09:33
oneswigPerhaps it is one to consider for a future summit to enable some forward planning09:34
priteauHow many people would a call for posters reach?09:35
*** andreykurilin__ has quit IRC09:36
oneswigpriteau: I am not sure.  I have ~200 mails in my address book, could spam them (and annoy people)09:36
*** andreykurilin has joined #openstack-meeting09:36
oneswigI'd prefer not to09:36
priteauWe could try academic mailing lists as well. But you're right that is it quite late notice09:36
oneswigIt works for people who have posters from other conferences09:37
oneswigAnother idea is to do something like the brown bag talks - lightning talks from WG members09:37
oneswigAn ideal situation would be to have two adjoining rooms, some refreshments and a mix of the two formats09:38
priteaulightning talks may be easier to organize and get people to present09:39
oneswigI'll see what can be arranged - space is tight in the venue.  They might even prefer two smaller rooms to one big one.09:40
oneswigThanks priteau good point09:40
*** qwebirc32754 has joined #openstack-meeting09:40
oneswigAfter the success in Austin there's also discussion of a WG social one evening.  Probably the Thursday when I understand nothing official is planned09:41
oneswigDoes anyone know Barcelona at all and can suggest a venue?09:42
oneswigA friend of mine, formerly at Barcelona Supercomputer Center, suggested a few places they sometimes used09:42
priteausorry, I have never been to Barcelona09:42
oneswig#link cute website, doesn't look vegetarian friendly http://www.asadordearanda.net09:44
*** ljxiash has quit IRC09:44
oneswigWas there anything further on summit activities?09:45
*** salv-orlando has quit IRC09:45
oneswig#topic Any Other Business09:45
*** openstack changes topic to "Any Other Business (Meeting topic: scientific-wg)"09:45
oneswigWhat has been missed?09:46
*** b1airo has joined #openstack-meeting09:46
priteauoneswig: I wanted to ask, do you have any more information about the OpenStack HPC meetup you mentioned the other day?09:46
priteauIs it part of http://www.meetup.com/Openstack-London/09:46
oneswigThe meetup in London, I followed up on it a few days ago and they couldn't get a venue so it has been postponed09:47
oneswigAlas09:47
*** qwebirc32754 has quit IRC09:47
oneswigthanks, I'd forgotten about that09:47
*** egallen has joined #openstack-meeting09:47
priteauRemoving it from my calendar09:47
b1airohi folks, finally made it09:47
b1airobit of a marathon this evening09:48
oneswigAre you going to OpenStack Day UK?09:48
oneswigHi b1airo, welcome back?09:48
oneswig(I mean !)09:48
b1airothanks oneswig :-)09:48
oneswigWe were just on AOB - I think we are pretty much done for the week09:49
*** gongysh_ has quit IRC09:49
dariovoneswig, is the “Cambridge meetup” thing still in the pipe?09:49
priteauoneswig: I would like to go but I need to check if I can. Is the speaker line-up complete?09:49
b1airoany big news i missed discussing?09:49
oneswigdariov: Good point, we had to defer over the summer on account of all those bl**dy holidays, lets pick up again09:49
dariov(I’m off for 3 weeks now, but something is October should be good)09:49
oneswigdariov: b*gger, it rolls on09:49
oneswigOctober it is09:50
b1airoi haven't yet reviewed the full summit agenda but looking forward to seeing what you all thought was good09:50
dariovyup, my boss here is keen in hosting, if needed09:50
oneswigb1airo: We need links into the schedule to recommend09:50
oneswigdariov: great, I love a field trip09:50
dariovoneswig, cool09:50
dariovI’ll be “back in the office” on the 20th of September09:51
b1airook, i'll try to make sure i get to looking at it soon before work people realise i'm back from leave09:51
dariovwe can try to find a date in october09:51
b1airoelse it'll end up being the usual JITSS (just in time summit schedule)09:51
oneswigdariov: when are you finishing before your holiday?  Might be good to get something in advance09:51
dariovpossibly after the 10th, we have a deadline on that day09:52
oneswigb1airo: I usually find the events I'm most interested in slightly after they've finished09:52
dariovin until friday, but I should be able to respond to email anyway, just slowish09:52
oneswigdariov: OK lets follow up offline09:52
*** janki has quit IRC09:52
dariovoneswig, ok09:53
oneswigAnything else to raise?09:53
oneswigOh, I had one item09:54
oneswigWhat is considered to be decent TCP bandwidth over VXLAN?09:54
b1airoah, still having issues there?09:54
oneswigWe have 50G Ethernet NICs.  With SR-IOV we get > 20GBits/s.  With VXLAN, at best 1.6 GBits/s09:55
oneswigStill having issues, going for a webex later09:55
oneswigBut I wanted to find out how many orders of magnitude out we are...09:56
priteauoneswig: I suppose that you've checked the MTU size?09:56
b1airosounds like you're 10+ times slower than expected09:57
*** markvoelker has joined #openstack-meeting09:57
oneswigIt's standard MTU in this case, 1400 bytes after encapsulation.  Not sure we can realistically change that for these networks09:57
priteaubut is the VM configured to have a smaller MTU?09:57
priteauthan 150009:57
b1airopriteau: i think they are benchmarking on a tight cluster LAN so MTU *shouldn't* be a major factor (still a factor, but not orders of magnitude)09:58
oneswigpriteau: correct, it gets trimmed down09:58
priteaubecause of the VXLAN encapsulation inside UDP, if the VM uses 1500 it would cause fragmentation09:58
b1airooneswig: have you seen the MLNX numbers here: https://www.mellanox.com/related-docs/whitepapers/CB_Mellanox_Ethernet_NIC_Advantage.pdf09:58
b1airoah yes good priteau09:58
b1airo*good point09:59
oneswigb1airo: thanks, I shall got to the webex with those numbers...09:59
oneswigOK - I think we must wrap up10:00
oneswigThanks all10:00
oneswigI'll gather together the schedule picks and follow up10:01
oneswig#endmeeting10:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"10:01
openstackMeeting ended Wed Aug 31 10:01:13 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)10:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-08-31-09.00.html10:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-08-31-09.00.txt10:01
openstackLog:            http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-08-31-09.00.log.html10:01
priteauGood bye everyone10:01
*** Hosam_ has joined #openstack-meeting10:01
*** yamamoto_ has quit IRC10:01
*** zhurong has quit IRC10:01
*** markvoelker has quit IRC10:02
*** salv-orlando has joined #openstack-meeting10:02
*** eranrom has quit IRC10:02
*** oneswig has quit IRC10:02
b1airocya10:02
*** Hosam has quit IRC10:04
*** janki has joined #openstack-meeting10:07
*** dariov has left #openstack-meeting10:07
*** Hosam has joined #openstack-meeting10:12
*** mars has joined #openstack-meeting10:15
*** Hosam_ has quit IRC10:15
*** verdurin has left #openstack-meeting10:16
*** Julien-zte has quit IRC10:19
*** thorst has joined #openstack-meeting10:20
*** ivc_ has joined #openstack-meeting10:22
*** markvoelker has joined #openstack-meeting10:26
*** thorst has quit IRC10:26
*** sudipto has quit IRC10:27
*** HeOS has quit IRC10:30
*** markvoelker has quit IRC10:30
*** HeOS has joined #openstack-meeting10:30
*** Hosam_ has joined #openstack-meeting10:42
*** sarob has joined #openstack-meeting10:44
*** Hosam has quit IRC10:45
*** b1airo has quit IRC10:45
*** mestery has quit IRC10:46
*** sdague has joined #openstack-meeting10:46
*** sarob has quit IRC10:49
*** sdake has joined #openstack-meeting10:49
*** anilvenkata is now known as anilvenkata_afk10:55
*** markvoelker has joined #openstack-meeting10:56
*** markvoelker has quit IRC11:00
*** iyamahat has joined #openstack-meeting11:03
*** salv-orlando has quit IRC11:04
*** tlaxkit has joined #openstack-meeting11:06
*** ronghui has quit IRC11:08
*** amotoki has quit IRC11:09
*** fzdarsky is now known as fzdarsky|lunch11:09
*** Na3iL has quit IRC11:10
*** senk has left #openstack-meeting11:11
*** iyamahat has quit IRC11:11
*** epico has quit IRC11:12
*** jaypipes has quit IRC11:12
*** amotoki has joined #openstack-meeting11:14
*** wznoinsk has quit IRC11:18
*** sarob has joined #openstack-meeting11:19
*** pc_m has left #openstack-meeting11:20
*** maeca1 has joined #openstack-meeting11:20
*** ronghui has joined #openstack-meeting11:20
*** dmorita has joined #openstack-meeting11:23
*** sarob has quit IRC11:24
*** markvoelker has joined #openstack-meeting11:25
*** salv-orlando has joined #openstack-meeting11:26
*** dmorita has quit IRC11:27
*** tlaxkit has quit IRC11:28
*** rtheis has joined #openstack-meeting11:28
*** markvoelker has quit IRC11:29
*** wznoinsk has joined #openstack-meeting11:33
*** baoli has joined #openstack-meeting11:37
*** xyang1 has quit IRC11:39
*** amakarov_away is now known as amakarov11:40
*** esumerfd has joined #openstack-meeting11:40
*** dfflanders has quit IRC11:41
*** thorst has joined #openstack-meeting11:43
*** vishwanathj has joined #openstack-meeting11:44
*** lbrune has joined #openstack-meeting11:45
*** baoli_ has joined #openstack-meeting11:46
*** rfolco has joined #openstack-meeting11:47
*** coolsvap_ is now known as coolsvap11:47
*** baoli has quit IRC11:49
*** sshnaidm is now known as sshnaidm|afk11:50
*** asettle has quit IRC11:53
*** prometheanfire has joined #openstack-meeting11:54
*** jckasper has joined #openstack-meeting11:55
*** markvoelker has joined #openstack-meeting11:56
*** jungleboyj has quit IRC11:57
*** asettle has joined #openstack-meeting11:58
*** asettle has quit IRC11:58
*** larainema has quit IRC11:58
*** asettle has joined #openstack-meeting11:59
*** yamamoto has joined #openstack-meeting11:59
*** spzala has joined #openstack-meeting11:59
*** yamamoto_ has joined #openstack-meeting11:59
*** Kevin_Zheng has quit IRC11:59
coolsvap#startmeeting requirements12:00
openstackMeeting started Wed Aug 31 12:00:10 2016 UTC and is due to finish in 60 minutes.  The chair is coolsvap. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: requirements)"12:00
openstackThe meeting name has been set to 'requirements'12:00
*** jckasper has quit IRC12:00
coolsvap#topic Roll-call12:00
*** openstack changes topic to "Roll-call (Meeting topic: requirements)"12:00
prometheanfireo/12:00
dirko/12:01
coolsvapprometheanfire dirk o/12:01
*** markvoelker has quit IRC12:01
*** larainema has joined #openstack-meeting12:02
*** longxiongqiu has joined #openstack-meeting12:02
*** Na3iL has joined #openstack-meeting12:03
*** tongli has quit IRC12:03
*** spzala has quit IRC12:03
*** yamamoto has quit IRC12:03
*** Kevin_Zheng has joined #openstack-meeting12:04
coolsvaplets wait for a min before we start with meeting12:04
*** salv-orlando has quit IRC12:04
*** asselin_ has quit IRC12:04
*** mars has quit IRC12:04
coolsvaplets move12:05
coolsvap#topic Announcements12:05
*** openstack changes topic to "Announcements (Meeting topic: requirements)"12:05
coolsvapI have a session accepted in barcelona with dims12:05
coolsvap#link  https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/15330/openstack-requirements-what-we-are-doing-what-to-expect-and-whats-next12:05
*** anilvenkata_afk is now known as anilvenkata12:05
*** bobh has joined #openstack-meeting12:06
coolsvap#topic Any controversies in the Queue?12:06
*** openstack changes topic to "Any controversies in the Queue? (Meeting topic: requirements)"12:06
prometheanfireI don't think so12:07
coolsvap#link https://review.openstack.org/#/c/358470/12:07
prometheanfirethe constant blocking of os-client-config sucks though12:07
coolsvap#link https://review.openstack.org/#/c/333264/12:08
coolsvap#link https://review.openstack.org/#/c/363150/12:08
prometheanfirewhat's wrong with the gr-update?12:08
coolsvap"Updated from generate-constraints" review needs some attention for libraries which are only updated with this review12:09
*** rodrigods has quit IRC12:09
*** rodrigods has joined #openstack-meeting12:09
coolsvapopenstack libraries get updated with dims/dhellmann reviews12:09
coolsvapbut others are not12:10
prometheanfireright12:10
prometheanfireI think we should strip the openstack libs out from that and get it merged today12:10
coolsvapprometheanfire: will you do that?12:11
prometheanfiresure12:11
coolsvap#action prometheanfire to update the g-r review to strip the openstack libs12:11
coolsvapprometheanfire: thanks12:11
prometheanfirethat's just this review12:11
*** salv-orlando has joined #openstack-meeting12:12
prometheanfirenot the actual job, but we should probably think about that12:12
coolsvapprometheanfire: yes we might need some work on the job as well12:12
*** bobh has quit IRC12:12
coolsvapdhellmann: dims around?12:13
dimspong coolsvap : what's up?12:13
coolsvapdims: reg. review https://review.openstack.org/#/c/358470/12:13
*** dprince has joined #openstack-meeting12:13
coolsvapwe are thinking if we can strip openstack libs in the "Updated from generate-constraints" reviews12:14
coolsvapdims: ^^12:14
coolsvapprometheanfire: regarding the other two, I am not sure if we need a decision on the two new libraries before freeze12:15
dimsyou mean the bot can propose 2 reviews? one with openstack libs and one without?12:15
dimsi'd run that by dhellmann for sure12:15
prometheanfiredims: one the normal one by one updates, one outside deps12:16
coolsvapcurrently openstack reviews are merged with your/dhellmann/ttx patches generated after release change merge12:16
*** sheel has quit IRC12:16
coolsvapopenstack library updates i meant12:16
coolsvapbut other libraries are getting ignored in the process12:17
prometheanfireI updated the gr review for today12:17
dimscoolsvap : not all openstack libs will get reviews filed by me/dhellmann/ttx12:17
dimscoolsvap : example python-k8sclient12:17
prometheanfireoh, should I add that back in?12:18
coolsvapdims: yeah thats another case12:18
prometheanfiresmaugeclient?12:18
dimsi'd rather have the bot differentiate into 2 buckets one from repositories owned by openstack and one outside12:18
dimsbut remember it will make it harder to test12:18
*** tochi has quit IRC12:19
dimsvarious combinations12:19
dimsso not sure what problem you are trying to solve here12:19
coolsvapmy initial thought process was to merge "Updated from generate-constraints" reviews but we decided to merge individual reviews12:19
coolsvapbut currently we are merging individual reviews12:19
coolsvapso the consolidated reviews are kinda ignored12:19
*** dmorita has joined #openstack-meeting12:19
dimswhich is fine, the bot does not get mad :)12:20
coolsvapeither because it always fails with jenkins12:20
*** pradk has joined #openstack-meeting12:20
coolsvapbut then we are losing on the updates for non-openstack libs12:20
* dhellmann arrives late12:20
dimscoolsvap : so then the bot logging 2 reviews is a better idea i think12:21
coolsvapdims: yeah12:21
prometheanfirewell, added smaug/k8s12:21
prometheanfireanyway, updated that review12:21
dhellmannoh, we shouldn't be ignoring the bot updates12:21
coolsvapdhellmann: yeah12:22
dimsdhellmann : ++ :)12:22
dhellmannit will be pretty complex to have the bot submit 2 reviews, I think. unless we build the changes in one repo, then figure out which lines to add to which patch?12:22
prometheanfireI wasn't ignoring it, I tended to work on client updates first to shrink down be bot update, then try to get that merged once a week (on the weekend typically)12:22
dhellmannthe idea is that all of the changes the bot proposes work together, so as soon as we start splitting them...12:22
dhellmannit might be safer to rebase the bot patch by hand to let it merge safely, and then approve it12:22
prometheanfiredhellmann: the problem is that the bot submits so many changes at once that it almost always fails12:23
prometheanfirethat's what I've been doing (by hand edits to prune down the changeset)12:23
dhellmannah12:23
coolsvapprometheanfire: yeah but its kinda ignored most of the times12:23
dhellmannwell, maybe having it ignore our libs entirely would make it better?12:24
coolsvapafaics12:24
prometheanfirecoolsvap: not by me :P12:24
*** dmorita has quit IRC12:24
dhellmannthough that might just lead to more failures12:24
prometheanfiredhellmann: that's my early morning guess (before coffee)12:24
*** markvoelker has joined #openstack-meeting12:24
dhellmannyeah12:25
*** hashar has quit IRC12:25
coolsvaplets monitor this for couple of weeks before making a decision12:25
coolsvapif its feasible to make it work by hand everytime12:26
prometheanfireagreed12:26
*** hashar has joined #openstack-meeting12:26
prometheanfireI just wanted to have people start thinking about it12:26
* coolsvap too12:26
dirkcan we just merge reviews that ignore the thigns that cause failures?12:26
prometheanfire#note think about removing openstacklibs from gr updates (those that are already submitted seperately)12:26
dirke.g. if externallibfoo-newrelease causes the bot to fail, letst just exclude that one to keep the proposal bot things mergeable12:27
*** ygbo has joined #openstack-meeting12:27
dirkwe just need to keep the backlog somewhere that investigates and fixes those issues as they happen12:27
prometheanfiredirk: generally yes, last week was bad because there were a couple of updates that caused breakage12:27
prometheanfireso it was multistep12:27
dhellmannyeah, figuring out which library is bad is non-trivial12:27
coolsvaplets move on12:28
coolsvap#topic Requirements freeze R-5 (Aug 29 - Sept 02)12:28
prometheanfireagreed12:28
*** openstack changes topic to "Requirements freeze R-5 (Aug 29 - Sept 02) (Meeting topic: requirements)"12:28
coolsvap#link https://releases.openstack.org/newton/schedule.html12:28
coolsvaptonyb sent the announcement on mailing list12:29
*** markvoelker has quit IRC12:29
coolsvap#link http://lists.openstack.org/pipermail/openstack-dev/2016-August/102581.html12:29
*** sshnaidm|afk is now known as sshnaidm12:29
*** annegentle has joined #openstack-meeting12:29
*** Ravikiran_K has quit IRC12:29
dirkI have a question regarding that.. is that only about g-r changes (new additions, new base versions) or also about uc changes?12:30
*** sudipto has joined #openstack-meeting12:31
coolsvapI think for both, dims dhellmann ^^12:31
prometheanfireboth12:31
prometheanfireafaik12:31
*** rossella_s has joined #openstack-meeting12:32
* dims defers to dhellmann 12:32
dirkso that means we should get an propsosal bot change merged pretty soon12:32
dhellmannyes, completely frozen except in the case of a bug in one of our libs12:32
dirkproposal..12:32
*** sindhu has joined #openstack-meeting12:32
coolsvapdirk: yeah thx dhellmann for the confirmation12:32
coolsvaplets monitor the change proposed by prometheanfire12:33
*** cartik has quit IRC12:33
*** Rong_hui has joined #openstack-meeting12:34
dhellmanncoolsvap, dirk : I found it very helpful to create a process document for the release team in openstack/releases/PROCESS.rst. we could add details to that to make it clear about what is frozen when (if what I have there already isn't clear)12:34
coolsvapdhellmann: ack12:35
*** sindhu has quit IRC12:35
prometheanfire#link https://github.com/openstack/releases/blob/master/PROCESS.rst12:35
coolsvapI think we have that down the agenda12:35
coolsvap#topic Coordinating with the release team12:35
*** openstack changes topic to "Coordinating with the release team (Meeting topic: requirements)"12:35
*** su_zhang has joined #openstack-meeting12:36
coolsvapfreezing requirements - http://git.openstack.org/cgit/openstack/releases/tree/PROCESS.rst#n10712:36
coolsvapstable branch for openstack/requirements - http://git.openstack.org/cgit/openstack/releases/tree/PROCESS.rst#n13812:36
dirkdhellmann: thanks for the pointer, I didn't see that yet12:36
dhellmannI think I saw in the requirements channel that tonyb said he would apply the -2 to all pending patches on his Thursday12:36
dhellmannor was it friday?12:37
* dhellmann looks back12:37
coolsvapdhellmann: Friday12:37
dhellmannyeah, friday12:37
dhellmannwhich I think is late our thursday? how do timezones work again?12:37
dhellmannanyway, I think that's good12:37
coolsvapyes its late thursday your time morning for tonyb12:38
prometheanfirehe said his thursday, our friday12:38
dhellmannif we end up needing to land one of them that his -2 and he's away for the weekend we can start a new patch for the udpate12:38
prometheanfireI may have that backwards12:38
dhellmannit's unlikely, but we never know so it's good to have a plan12:38
prometheanfiredhellmann: I'll keep that in mind12:39
dhellmannprometheanfire : I checked the scrollback and he said friday12:39
dhellmannhis friday12:39
dhellmannand since he lives in the future, that's our thursday12:39
prometheanfireah, right12:39
* dhellmann hasn't had enough caffeine to do date math12:40
*** cartik has joined #openstack-meeting12:40
coolsvapokay lets convey this to tonyb if he's online tomorrow12:40
coolsvap#topic Barcelona Design Summit12:40
*** openstack changes topic to "Barcelona Design Summit (Meeting topic: requirements)"12:40
coolsvaptonyb has requested a (fishbowl) session for Barcelona12:41
prometheanfirenot going :(12:41
coolsvapmaybe we can discuss the topics in some next meetings12:41
coolsvapwe have a requirements session accepted in main track (not sure if everyone saw the announcements)12:42
dirkyep, saw that, good stuff12:42
prometheanfireyarp12:42
coolsvaplets move on12:42
coolsvap#topic Mascot12:42
*** openstack changes topic to "Mascot (Meeting topic: requirements)"12:42
coolsvapThe only mascot idea that had multiple votes was waterfall so tonyb asked Heidi to select that one12:43
*** ItSANg___ has quit IRC12:43
* coolsvap has no idea what was waterfall12:43
dirkI think its a good choice12:44
dhellmannI liked that one, it made me think "upstream"12:44
*** zhurong has joined #openstack-meeting12:44
coolsvapcool12:45
prometheanfireI think I proposed that one, it's our devel methodology right?12:45
prometheanfireit fits for other reasons though12:45
dhellmannhaha12:45
coolsvap#topic Tasks from Etherpad12:46
*** openstack changes topic to "Tasks from Etherpad (Meeting topic: requirements)"12:46
dhellmannI have to step away. Thanks everyone, and congratulations on becoming a big tent team!12:46
coolsvapthanks dhellmann12:47
coolsvap#link https://etherpad.openstack.org/p/requirements-tasks12:47
*** zhiyuan has joined #openstack-meeting12:47
coolsvapany updates on this?12:47
prometheanfireI've been keeping up on the other projects and failing requirements updates12:47
* coolsvap has none12:47
*** tongli has joined #openstack-meeting12:47
prometheanfirebut no progress this week, one is stuck in legal, the other in review hell12:47
prometheanfirethat's all I have12:48
coolsvapthanks prometheanfire for the update12:48
*** woodster_ has joined #openstack-meeting12:48
*** tongli has quit IRC12:48
coolsvapwhich one is stuck in review?12:48
*** tongli has joined #openstack-meeting12:49
prometheanfirehttps://review.openstack.org/#/c/352501/12:49
prometheanfire#link https://review.openstack.org/#/c/352501/12:49
prometheanfirevitrage is the other one stuck in legal12:49
prometheanfireit's the three under #20 in the list right now12:49
*** hemnafk has quit IRC12:49
coolsvapah okay12:50
*** hemnafk has joined #openstack-meeting12:50
*** Fdaisuke has quit IRC12:51
*** yinxiulin has joined #openstack-meeting12:51
* coolsvap thought something stuck in requirements queue12:51
coolsvapmoving on12:51
*** Fdaisuke has joined #openstack-meeting12:51
coolsvap#topic Volunteer for next meeting12:51
*** openstack changes topic to "Volunteer for next meeting (Meeting topic: requirements)"12:51
coolsvapI think we have volunteer for next two meetings12:52
*** Yipei has joined #openstack-meeting12:52
*** ijw has joined #openstack-meeting12:52
coolsvapSep 07 - tonyb12:52
coolsvapSep 14 - prometheanfire12:52
coolsvapanyone up for sep 21?12:52
*** mestery has joined #openstack-meeting12:52
coolsvapalright lets see in next meeting again12:53
dirkI might be able to do sep 21, not sure yet12:53
dirkway too far in the future :)12:53
*** markvoelker has joined #openstack-meeting12:54
coolsvapdirk: alright we can always check in next meetings12:54
coolsvapskipping topic optional-requirements since did not see number8012:54
coolsvap#topic Open Discussion12:54
*** openstack changes topic to "Open Discussion (Meeting topic: requirements)"12:54
coolsvapanyone has anything to bring up in open discussion?12:54
prometheanfirenon12:55
*** Rong_hui has quit IRC12:55
* dirk is good12:56
coolsvapokay back to #openstack-requirements. Thanks folks12:56
coolsvap#endmeeting12:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"12:56
openstackMeeting ended Wed Aug 31 12:56:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)12:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-08-31-12.00.html12:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-08-31-12.00.txt12:56
openstackLog:            http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-08-31-12.00.log.html12:56
*** prometheanfire has left #openstack-meeting12:56
*** ijw has quit IRC12:57
*** dongfeng has joined #openstack-meeting12:58
*** markvoelker has quit IRC12:58
*** ilyashakhat has joined #openstack-meeting12:59
*** fzdarsky|lunch is now known as fzdarsky12:59
*** joehuang has joined #openstack-meeting13:00
*** mriedem has joined #openstack-meeting13:00
joehuanghello13:00
Yipeihi13:01
dongfenghi13:01
joehuang#startmeeting tricircle13:01
openstackMeeting started Wed Aug 31 13:01:12 2016 UTC and is due to finish in 60 minutes.  The chair is joehuang. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: tricircle)"13:01
openstackThe meeting name has been set to 'tricircle'13:01
zhiyuanhello13:01
*** pradk has quit IRC13:01
yinxiulinhello13:01
*** xuan0802 has joined #openstack-meeting13:02
joehuang#topic rollcall13:02
*** openstack changes topic to "rollcall (Meeting topic: tricircle)"13:02
joehuang#info joehuang13:02
*** xuan0802 has quit IRC13:02
yinxiulin#info xiulin13:02
dongfeng#info dongfeng13:02
Yipei#info Yipei13:02
*** Rong_hui has joined #openstack-meeting13:03
Rong_hui:)13:03
*** hejiawei has joined #openstack-meeting13:03
zhiyuan#info zhiyuan13:03
Rong_hui#info ronghui13:03
joehuang#topic feature implementation progress review13:03
hejiawei#info hejiawei13:03
*** openstack changes topic to "feature implementation progress review (Meeting topic: tricircle)"13:03
joehuanghello, please describe your feature implementation progress shortly13:04
*** xuan0802 has joined #openstack-meeting13:04
*** jckasper has joined #openstack-meeting13:04
*** markvoelker has joined #openstack-meeting13:04
*** spzala has joined #openstack-meeting13:04
Yipeii have already submitted a patch, i will update the patch based on your comments. Further, i will try to finish the patch of adding resource_affinity_tag ASAP13:05
Yipeigo on updating the patch of dynamic pod binding13:05
joehuangto Yipei, except resource_affinity_tag, also one field in pod binding13:05
*** lzy2 has joined #openstack-meeting13:05
joehuangto represent current active binding13:05
*** Julien-zte has joined #openstack-meeting13:06
dongfengI have commit a document of pod api features. tempest test for pod is still going on.13:06
*** amitgandhinz has quit IRC13:06
*** azbiswas has joined #openstack-meeting13:06
zhiyuanpatches for resource clearing of floating ip, subnet, router have been submitted, but they all depends on the shared-vlan-l3 patch, which has not been merged13:06
joehuanggood, to Dongfeng, do you know how to do the tempest test?13:06
*** amitgandhinz has joined #openstack-meeting13:07
yinxiulinI'm doing server action function. The action which only need server_id parameter  has been finished, and passed the unit  test.13:07
dongfengno, tempest doesn't contain the pod test cases. i am studying it.13:07
zhiyuannow i am working on the separation of api-gateway and networking automation13:07
joehuangto Zhiyuan, so we need to merge shared-vlan-l3 first, so that other patches can get merged13:07
Yipeido we need to add a table to store historical binding relationship, instead of adding a field in binding table? i mean all the records in the binding table are active13:07
*** xuan0802 has quit IRC13:07
zhiyuanto joe, that's right13:07
hejiaweiI read some document to learn how to test my patch ,and next week I will continue to test it .13:08
joehuangto Xiulin, great!13:08
Yipeior just add a field13:08
joehuangno need to add a new table, just use active, deactive, and the time related field for example update_at to store the history information13:09
joehuangto Zhiyuan, good job, quick reaction to new proposal13:10
*** markvoelker has quit IRC13:10
joehuangto Jiawei, learn from other's patch will accelearate your experience on how to do test13:10
Yipeito joe, ok, got it. will add it into the binding table13:11
*** azbiswas has quit IRC13:11
Rong_huiFor me, the environment meet some problems, and i solve it and record it in the our test and  uploading to wiki13:11
Rong_huiand also do some creating the new organization for our team.13:12
*** prateek has quit IRC13:12
zhiyuanto ronghui, is the installation guide in wiki page ready?13:12
Rong_huii will finish it this week  and add some case for it13:13
joehuangI suggest you guys who has no lots of experience on test, need to learn unit test and tempest test13:13
*** maeca2 has joined #openstack-meeting13:14
Rong_huiok13:14
dongfengok13:14
Yipeiok, got it13:14
hejiaweiI got it13:14
longxiongqiu#info longxiongqiu13:14
zhiyuandocument for mock: http://www.voidspace.org.uk/python/mock/13:14
longxiongqiuhi joehuang, i will update my patch ASAP13:14
*** maeca1 has quit IRC13:15
*** mtanino has joined #openstack-meeting13:15
longxiongqiuand continue my working  ASAP13:15
Rong_huixiongqiu has come back to our team13:15
*** Administrator has joined #openstack-meeting13:15
*** Administrator is now known as Guest311013:15
*** Guest3110 has quit IRC13:15
joehuanghi, Xiongqiu, shake hand13:16
*** sridharg has quit IRC13:16
*** sdake_ has joined #openstack-meeting13:16
longxiongqiu:)13:16
joehuanglong time no see13:16
*** rooneym has joined #openstack-meeting13:17
longxiongqiuyes, i just come back yesterday13:17
*** cleong has joined #openstack-meeting13:17
*** Hosam_ has quit IRC13:18
*** zz_dimtruck is now known as dimtruck13:18
*** su_zhang has quit IRC13:18
joehuangI'll try to find some material about unit test and functional test. and share that to you in #openstack---\\-\\\-tricircle13:19
joehuang#openstack-tricircle13:19
Rong_huiok  i think is very helpful to us13:19
*** sdake has quit IRC13:19
*** cartik has quit IRC13:19
joehuang#topic proposal to move tricircle forward for its big-tent application13:20
*** openstack changes topic to "proposal to move tricircle forward for its big-tent application (Meeting topic: tricircle)"13:20
Rong_huialso some material about the tempest13:20
*** leyuquan has joined #openstack-meeting13:20
*** esberglu has joined #openstack-meeting13:20
*** sridharg has joined #openstack-meeting13:20
*** yamamoto_ has quit IRC13:20
*** ilyashakhat has quit IRC13:20
joehuanghello, last week we talked about that the TCs concerns on Tricircle big-tent application13:21
joehuangand the proposal to move forward was prepared13:21
joehuang#link https://docs.google.com/presentation/d/1kpVo5rsL6p_rq9TvkuczjommJSsisDiKJiurbhaQg7E/13:21
*** sdake_ is now known as sdake13:22
joehuang#info the basic idea for the proposal 2 is to divide tricircle into two sub-projects13:22
*** liuhanxi has quit IRC13:23
joehuang#info one for networking automation13:23
*** lblanchard has joined #openstack-meeting13:23
*** coolsvap is now known as _coolsvap_13:23
*** takashi has joined #openstack-meeting13:23
joehuang#info the other one for API Gateway for Nova/Cinder13:24
joehuangso would like to know your comments13:24
joehuangFor proposal, plugin mechanism in Nova/Cinder will take long time to discuss13:25
joehuangthe proposal 2 will also make tricircle being more flexible in deployment for different scenario13:26
zhiyuanthe difference between proposal 2 and our current implementation is that we also need to add a new plugin in bottom Neutron server13:28
Rong_huii dont really understand about the plugin mechanism13:28
*** annegentle has quit IRC13:29
*** jckasper has quit IRC13:29
*** liukun has joined #openstack-meeting13:29
joehuangto Ronghui, you mean Neutron or Nova/Cinder?13:29
*** ljxiash has joined #openstack-meeting13:29
Rong_huiCinder13:30
joehuangNova/Cinder don't support plugin mechnism yet in its API layer13:30
*** zul has quit IRC13:30
Rong_huiok13:30
liukun#info liukun13:30
*** janki has quit IRC13:30
*** akuznetsov has joined #openstack-meeting13:30
*** rossella_s has quit IRC13:31
joehuangFor Nova/Cinder, if we want to add plugin mechanism then we have to develop that in Nova/Cinder, and need Nova/Cinder to approve it13:31
joehuanghi liukun, welcome back13:31
liukunthx13:31
*** su_zhang has joined #openstack-meeting13:31
joehuangneed long time discussion in Nova/Cinder team13:31
Rong_huigot it13:31
Yipeiwhy do nova and cinder need plugins, in current implementation, we do not use plugins13:32
Rong_hui+113:32
*** cardeois has joined #openstack-meeting13:33
*** prateek has joined #openstack-meeting13:33
joehuangthere is also proposal for Nova API-GW and Ciner API-GW for global objects like volume_type, flavor implementation to remove the overlapping implementation with Nova/Cinder13:33
*** zul has joined #openstack-meeting13:33
*** manikanta_tadi has quit IRC13:33
*** shiyangkai has joined #openstack-meeting13:34
*** ljxiash has quit IRC13:34
shiyangkai#info shiyangkai13:34
zhiyuanin our current implementation, we need to implement nova/cinder api gateway, we need to handle api request ourselves, parse and validate the request body, process and return the response body13:34
joehuangto Yipei, Because TCs worried about that the tricircle will introduce different in the Nova/Cinder API13:35
zhiyuanif plugin mechanism is introduced, we can focus on the processing, no need to care about the request and response body13:35
joehuangTCs want single API implementation and always keep the API consistency with the openstack documentation13:36
Yipeiok, i see. actually, we do not introduce any different API13:36
joehuangsyntax or sematics difference13:36
joehuangwe have already used tempest to guarantee the syntax consistency, but they still worried that sematics difference will be there someday13:37
*** mtanino has quit IRC13:37
joehuangwelcome shiyangkai13:38
joehuanghow do you think about proposal for Nova API-GW and Ciner API-GW for global objects like volume_type, flavor implementation13:38
joehuang                  to remove the overlapping implementation with Nova/Cinder13:38
shiyangkaithank you very much13:39
*** su_zhang has quit IRC13:39
*** su_zhang has joined #openstack-meeting13:39
*** sankarshan is now known as sankarshan_away13:40
zhiyuan+1 for this proposal13:40
joehuangbefore project dividen( we also look forward response from community and Monty/TCs etc13:40
joehuangwe can do first to move the networking automation trigger from Nova API-GW to local neutron plugin13:41
joehuangand optimize the volume_type/flavor etc implementation13:41
joehuangno matter we divide the project or not, these two proposal brings benefit to Tricircle13:42
joehuangwe can wait for comment from community to see if we need to divide the project or not13:42
Rong_huiok13:43
joehuanghow about your thoughts?13:43
Rong_huii got it13:43
*** su_zhang has quit IRC13:44
Yipeino other questions, i think it is a good idea13:44
Rong_huiIt is another way for us to let TCs accept more easy and also benefit to Tricircle13:44
*** xyang1 has joined #openstack-meeting13:44
joehuanggood13:44
joehuang#info optimize tricircle to be prepared for divide13:45
joehuangother topics?13:46
*** amotoki has quit IRC13:46
Rong_huino for me13:46
*** banix has joined #openstack-meeting13:46
liukunno13:46
yinxiulinno for me13:46
zhiyuanno for me13:46
Yipeino for me13:46
dongfengno for me13:46
*** liuhanxi has joined #openstack-meeting13:47
shiyangkaino13:47
*** liuhanxi has quit IRC13:47
joehuangok, let's conclude the meeting13:47
*** jckasper has joined #openstack-meeting13:47
*** liuhanxi has joined #openstack-meeting13:47
joehuangthank you attending the meeting, see you next time13:47
joehuang#endmeeting13:47
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:48
Yipeisee u13:48
zhiyuansee you13:48
openstackMeeting ended Wed Aug 31 13:47:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tricircle/2016/tricircle.2016-08-31-13.01.html13:48
joehuangbye13:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tricircle/2016/tricircle.2016-08-31-13.01.txt13:48
liukunsee  u13:48
*** zhiyuan has quit IRC13:48
openstackLog:            http://eavesdrop.openstack.org/meetings/tricircle/2016/tricircle.2016-08-31-13.01.log.html13:48
Rong_huibye13:48
dongfengsee you13:48
liukunbye13:48
yinxiulinbye13:48
*** longxiongqiu has quit IRC13:48
*** joehuang has quit IRC13:48
shiyangkaigoodbye13:48
*** Yipei has quit IRC13:48
*** shiyangkai has quit IRC13:48
*** liukun has quit IRC13:49
*** dongfeng has quit IRC13:49
*** hejiawei has quit IRC13:50
leyuquanbye13:50
*** leyuquan has quit IRC13:50
*** baumann has joined #openstack-meeting13:50
*** rossella_s has joined #openstack-meeting13:52
*** amotoki has joined #openstack-meeting13:53
*** ljxiash has joined #openstack-meeting13:53
*** eharney has joined #openstack-meeting13:54
*** ayoung has joined #openstack-meeting13:54
*** bobh has joined #openstack-meeting13:55
*** msmol has joined #openstack-meeting13:56
*** tongli_ has joined #openstack-meeting13:58
*** Swanson has quit IRC13:58
*** efried has quit IRC13:58
*** yinxiulin has quit IRC13:59
*** Jeffreyc42 has joined #openstack-meeting13:59
krotscheck#startmeeting #javascript14:00
openstackMeeting started Wed Aug 31 14:00:07 2016 UTC and is due to finish in 60 minutes.  The chair is krotscheck. 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: #javascript)"14:00
krotscheck...?14:00
openstackThe meeting name has been set to '_javascript'14:00
krotscheckwait.14:00
krotscheck#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Wed Aug 31 14:00:17 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
krotscheck#startmeeting javascript14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/_javascript/2016/_javascript.2016-08-31-14.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/_javascript/2016/_javascript.2016-08-31-14.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/_javascript/2016/_javascript.2016-08-31-14.00.log.html14:00
openstackMeeting started Wed Aug 31 14:00:20 2016 UTC and is due to finish in 60 minutes.  The chair is krotscheck. 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: javascript)"14:00
krotscheckThere we go14:00
openstackThe meeting name has been set to 'javascript'14:00
krotscheckGood morning everyone!14:00
vkramskikhhi14:00
cardeoisHello !14:00
krotscheckWooo good progress this week!14:00
*** links has quit IRC14:00
*** ebalduf has joined #openstack-meeting14:00
krotscheck#link Agenda: https://etherpad.openstack.org/p/javascript-meeting-2016-08-3114:00
krotscheckOUt of curiosity, who's been putting together the agenda each week?14:01
*** tongli has quit IRC14:01
* krotscheck wants to thank them.14:01
krotscheck#topic Action Followup: jsdoc-sphinx14:01
*** openstack changes topic to "Action Followup: jsdoc-sphinx (Meeting topic: javascript)"14:01
krotscheckYeah, I totally didn't do that.14:01
krotscheck#action krotscheck Create story to fix bugs in jsdoc-sphinx14:01
*** spotz_zzz is now known as spotz14:01
*** bobh has quit IRC14:02
krotscheck#topic Action Followup: MVP14:02
*** openstack changes topic to "Action Followup: MVP (Meeting topic: javascript)"14:02
*** shamail has joined #openstack-meeting14:02
krotscheckOk, so lots of meat here.14:02
betherlyo/14:02
*** pradk has joined #openstack-meeting14:02
krotscheckWe've landed most of keystone. There's a bunch of things that shook out as work on glance and neutron started.14:02
*** rfolco has quit IRC14:03
cardeoisYeah almost started14:03
krotscheckcardeois put up a patch to genericize version negotiation. https://review.openstack.org/#/c/363304/14:03
*** zhurong has quit IRC14:03
cardeoisFor glance DSVM jobs are failing but I found the issue and will fix before the end of the meeting14:03
*** zhurong has joined #openstack-meeting14:03
krotscheckcardeois: Oh? Nice! I was trying to figure out what's going on with this patch -> https://review.openstack.org/#/c/363301/14:04
*** rfolco has joined #openstack-meeting14:04
*** dimtruck is now known as zz_dimtruck14:04
krotscheckOh yeah, and we've got a patch up that will turn on voting for DSVM jobs.14:04
krotscheckGlance has been built out all the way to imageList14:04
*** jprivard has joined #openstack-meeting14:05
jprivardsorry I'm late14:05
*** spotz is now known as spotz_zzz14:05
krotscheckNova's a bit stuck until we have cardeois' version negotiation patch, because nova registers its services differently14:05
* krotscheck needs to build on that14:05
*** spotz_zzz is now known as spotz14:05
krotscheckBut with nova, glance, and neutron, that's really all we need to get the functional portion of the MVP done14:05
krotscheck(We may need to add key management?14:05
*** baojg has joined #openstack-meeting14:05
krotscheckThe only outstanding part there then is documentation14:06
*** sdake_ has joined #openstack-meeting14:06
krotscheckI do have a design discussion point on the MVP for later.14:06
krotscheckAny questions on the MVP?14:07
*** cardeois_ has joined #openstack-meeting14:07
*** cardeois has quit IRC14:07
*** yamamoto has joined #openstack-meeting14:07
krotscheckOh! I forgot. We ripped out all the requestInterception code, as it wasn't being used, and was causing our tests to fail. Once we need it we can always add it back14:07
*** sdake has quit IRC14:07
* msmol is sharing his laptop with cardeois, his keeps crashing14:08
*** tonytan4ever has quit IRC14:09
krotscheckSee, now I'm thinking of this: http://vignette3.wikia.nocookie.net/forgottenrealms/images/e/e1/Ettin_-_Sam_Wood.jpg/revision/latest?cb=2007022103130114:09
krotscheckBut I digress, moving on14:09
*** tonytan4ever has joined #openstack-meeting14:09
krotscheck#topic Action Followup: Documentation14:09
*** openstack changes topic to "Action Followup: Documentation (Meeting topic: javascript)"14:09
krotscheckNot complete, will punt14:09
krotscheck#action krotscheck split design-by-documentation into to-implement segments14:10
krotscheckI think that's it for actions. Anyone have smoething they did last week that they want to highlight to the rest of us?14:10
cardeois_well not much, just want to remind that all jobs should be green before merging now. As DSVM jobs were fixed14:11
*** rfolco has quit IRC14:11
*** cardeois_ is now known as cardeois14:11
*** spzala has quit IRC14:12
krotscheckRight, until https://review.openstack.org/#/c/363200/ forces it14:12
*** rfolco has joined #openstack-meeting14:12
cardeoisYes14:12
krotscheckAlright, moving on.14:12
vkramskikhyeah I've merged lots of stuff with red dsvm jobs, by bad14:12
cardeoissure no pb, now you know14:12
*** spzala has joined #openstack-meeting14:12
krotscheck#topic Action Followup: Brainstorm Outreach Ideas14:12
*** openstack changes topic to "Action Followup: Brainstorm Outreach Ideas (Meeting topic: javascript)"14:12
krotscheckSo, who's got ideas?14:13
krotscheckMy biggest idea this week was when I put to the list that I'm departing OpenStack, and suddenly everyone was interested in the Javascript SDK.14:13
krotscheckIn particular, TravT from searchlight.14:13
msmolso what you're saying is, you should announce your depature on a more regular basis to keep interest levels high?14:14
krotscheckmsmol: Indeed. Keep coming back and leaving again :)14:14
krotscheckAnyway- he wants to play with the SDK to see whether he can use it for the all-javascript components in the searchlight-ui.14:14
*** akuznetsov has quit IRC14:14
krotscheckAnd he ran smack into the lack of a Readme or documentaiton14:15
krotscheckSo, yeah, we kinda need that before we ship14:15
cardeoisgood point14:15
*** sandanar has quit IRC14:15
krotscheckAlso, he mentioned that he'd be able to contribute engineering resources to build out searchlight and murano.14:15
*** longxiongqiu has joined #openstack-meeting14:16
*** amotoki has quit IRC14:16
krotscheckAnd advocate on our behalf inside of HPE. So I'm going to keep that converstaion going, and walk him through any and all pain points that he may encounter as he explores the SDK.14:16
krotschecki.e. a first user :)14:16
*** tpsilva has joined #openstack-meeting14:16
*** spzala has quit IRC14:17
krotscheckAnother idea I had is sending out release announcements to the dev list14:17
krotscheckDid anyone else have ideas?14:17
cardeoismhh not really14:17
krotscheckbetherly, anything from you?14:17
* krotscheck remembers that betherly was struggling with a check box yesterday.14:18
*** mickeys has joined #openstack-meeting14:18
*** tonytan4ever has quit IRC14:18
betherlynot really at the moment sorry! been pretty deep in ironic-ui stuff getting ready for next release14:18
krotscheckAlrightey!14:19
betherlycheckbox issue solved thank goodness. more a case of looking at the same code for too long and not seeing wood for the trees14:19
krotscheckCoolio.14:19
krotscheckMoving on14:19
*** tonytan4ever has joined #openstack-meeting14:20
krotscheck#topic Keystone Configuration object14:20
*** openstack changes topic to "Keystone Configuration object (Meeting topic: javascript)"14:20
krotscheckSo, this is something that I encountered while I was building out glance and nova.14:20
*** mickeys has quit IRC14:20
*** mtanino has joined #openstack-meeting14:20
krotscheckThose two services are, by necessity, configured from their entries in the service catalog.14:20
krotscheckExcept... keystone's configured using the clouds.yaml format.14:20
*** sindhu has joined #openstack-meeting14:21
*** su_zhang has joined #openstack-meeting14:21
*** liamji has joined #openstack-meeting14:21
krotscheckI'd like to propose that keystone also is configured using the same catalog configuration entry, and that that clouds.yaml format be used for the OpenStack SDK wrapper.14:21
krotscheckThat way, Clouds,yaml is used to configure a cloud, and the service catalog is used to configure services.14:21
krotscheckAny thoughts?14:21
cardeoisYeah so I agree keystone should be contructed the same way glance and nova are. That means clouds.yaml is used somewhere else, or is optionnal for advanced users.14:22
*** yuval has quit IRC14:23
krotscheckvkramskikh? ^^14:23
msmolsounds reasonable... +114:23
*** rbak has joined #openstack-meeting14:23
vkramskikh+1 from me14:23
*** uxdanielle has joined #openstack-meeting14:23
krotscheckAlrightey14:24
krotscheck#agreed use catalog entry to configure keystone14:24
krotscheck#topic switch to babel-transform-runtime14:24
*** openstack changes topic to "switch to babel-transform-runtime (Meeting topic: javascript)"14:24
krotscheckWho put that on the agenda?14:24
vkramskikhit was me14:25
*** zz_dimtruck is now known as dimtruck14:25
vkramskikhI think it's necessary before cutting MVP14:25
krotscheck#link https://www.npmjs.com/package/babel-plugin-transform-runtime14:25
vkramskikhbecause web bundle currently is about 300kb in size14:25
*** lzy2 has quit IRC14:25
vkramskikhbecause it includes the whole babel-polyfill14:25
krotscheckSo, just to clarify....14:25
cardeoisoh wow14:26
krotscheckWhat this does is it takes all our polyfills, and makes sure they don't end up in the final package.14:26
krotscheckThat'd then require our end users to add them as dependencies themselves?14:26
*** amotoki has joined #openstack-meeting14:26
krotscheck(Which should be automatic)14:26
vkramskikhno, it just polyfills only necessary parts which are actually used in the porject14:27
msmolthat's super cool, good idea vkramskikh14:27
krotscheckOh, gotcha14:27
krotscheckNice!14:27
vkramskikhfor example, we don't use generators, so it won't include polyfills for generators in the resulting bundle14:27
cardeois+1 !14:27
krotscheck+114:27
msmolhave you tried including it yet? by how much can we expect to shrink?14:28
krotscheck(Also, generators don't work that well, because apparently babel doesn't play well with yield14:28
*** rajinir has joined #openstack-meeting14:28
vkramskikhno i didn't do this yet for js-openstack-lib, though it's used in fuel14:28
*** fnaval_ has quit IRC14:28
*** spzala has joined #openstack-meeting14:28
krotscheckvkramskikh: What was the impact on fuel?14:29
*** donghao has joined #openstack-meeting14:29
*** yamamoto has quit IRC14:29
*** yamamoto has joined #openstack-meeting14:29
vkramskikhkrotscheck: I doubt I can remember exact number, but I think it was about 30-40 kb, but that' because fuel is quite large project14:29
vkramskikhfor js-openstack-lib it should reduce the size dramatically14:29
krotscheckRIght, and we're still pretty small14:29
krotscheckvkramskikh: Are you able to do that work?14:30
* krotscheck doesn't know what the effort would be.14:30
vkramskikhkrotscheck: I think I am, shouldn't be too hard14:30
krotscheckAwesome!14:30
krotscheck#agreed swithc to babel-transform-runtime14:30
*** tonytan4ever has quit IRC14:30
krotscheck#action vkramskikh Swithc to babel-transform-runtime14:31
krotscheckAny othequestions?14:31
*** tonytan4ever has joined #openstack-meeting14:31
cardeoisnope14:31
krotscheckALright.14:31
krotscheck#topic Open Discussion14:31
*** openstack changes topic to "Open Discussion (Meeting topic: javascript)"14:31
krotscheckSo, as of next week I'm volunteer-time-only.14:32
krotscheckAlso, I will not be at the summit, as my talk was not accepte.d14:32
krotscheckAnd new-employer will only send me if I have a talk14:32
msmolwhat new adventures will you be embarking on krotscheck if you don't mind answering ;-)14:33
Zara:(14:33
krotscheckmsmol: I will become an App-On-Openstack developer14:33
*** nmagnezi has quit IRC14:33
krotscheckOr, well, an App-On-Cloud developer14:33
cardeoisCool so that means, you "could" have to use the js-openstack-lib sdk14:34
vkramskikhthen I think we should elect more cores, since I cannot spend much time on this project14:34
* msmol googles what that means14:34
krotscheck"Could".14:34
cardeoishaha yeah "could"14:34
krotscheckcardeois: Yes, continuing to work on it willd efinitely be part of my new job, only it won't be part of it immediately14:34
*** Swanson has joined #openstack-meeting14:34
* krotscheck can't name his new employer for legal reasons14:34
krotscheckvkramskikh: I agree. I nominate cardeois, since he's been the most vocal on reviews, and has submitted patches ;)14:35
*** amotoki has quit IRC14:35
msmol+114:35
vkramskikh+114:35
cardeoiscool thanks ! I agree to volunteer14:35
krotscheckcardeois: Sucker.14:36
krotscheck;)14:36
krotscheck#agreed cardeois elected to core.14:36
cardeois:)14:36
vkramskikhshould we organize a formal vote or we can just add him to the core group?14:36
*** su_zhang has quit IRC14:36
*** shamail_ has joined #openstack-meeting14:36
krotscheckvkramskikh: I'll doublecheck with fungi, since we're still technicall under infra.14:36
msmoldepends, who has voting rights? current cores only or open to the public14:36
krotscheckAlso, I don't apparently have the rigst to add someone14:36
*** su_zhang has joined #openstack-meeting14:37
*** david-lyle_ has joined #openstack-meeting14:37
*** jungleboyj has joined #openstack-meeting14:37
krotscheckmsmol: Everyone has +1 rights, only cores can +2A and tag a release.14:37
msmolto elect another core is the same?14:37
fungifor infra projects, because we have multiple core review groups, the ptl is the group owner and controls addition/removal of core reviewers14:37
cardeoisThought I have no idea what cores means except for the +2. Is there any other responsability that that?14:38
*** salv-orlando has quit IRC14:38
fungiif you want to add core reviewers on one of the js repos in infra, just hit me up14:38
krotscheckmsmol: Ya know, we never settled on that. I always thought that election-by-consensus-of-cores was the thing, unless someone on the public list had a big big problem.14:38
krotscheckfungi: Danke, willdo :)14:38
krotscheckfungi: Actually, could you add cardeois as a core to js-openstack-lib? :D14:38
krotscheck(we just elected him ^^)14:38
krotscheckFor now I think this is fine.14:39
fungiin a general openstack developer community sense, core review teams are basically delegated by ptls. the ptl is in turn elected by all contributors to all repos under their project14:39
*** shamail has quit IRC14:39
*** shamail_ is now known as shamail14:39
fungikrotscheck: sure, just a sec and i'll take care of it14:39
krotscheckAwesome.14:39
krotscheckfungi: Thank you!14:40
krotscheckAnything else for open discussion14:40
krotscheck??14:40
*** fnaval has joined #openstack-meeting14:40
cardeoisnope14:40
fungi#link https://review.openstack.org/#/admin/groups/1408,members14:40
fungicardeois has been added14:40
krotscheckcardeois: Congratulations!14:40
cardeoisgreat, thanks fungi and krotscheck14:40
fungiwelcome to added responsibility! ;)14:41
*** shamail has quit IRC14:41
msmolOh gee I hope this new power doesn't get to his head. I still have to sit next to him all day :o14:41
*** su_zhang has quit IRC14:41
krotscheckmsmol: It's your job to keep him in chEKC14:41
*** su_zhang has joined #openstack-meeting14:41
krotscheckArgh baby fingers14:41
krotscheckAlright, i'm calling the meeting. Thanks everyone!14:41
krotscheck#endmeeting14:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:41
openstackMeeting ended Wed Aug 31 14:41:40 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/javascript/2016/javascript.2016-08-31-14.00.html14:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/javascript/2016/javascript.2016-08-31-14.00.txt14:41
openstackLog:            http://eavesdrop.openstack.org/meetings/javascript/2016/javascript.2016-08-31-14.00.log.html14:41
cardeoisbye!14:41
*** shamail has joined #openstack-meeting14:42
Zarathat meeting ended dramatically :D14:42
*** tonytan4ever has quit IRC14:43
* Zara hopes krotscheck eventually retrieves his keyboard from the baby14:43
*** tonytan4ever has joined #openstack-meeting14:43
krotscheckZara: Yeaaah that's going to eb tricky14:43
*** esker has joined #openstack-meeting14:44
Zara:) if the baby can do a convincing impersonation then I guess we'll be fine14:44
*** ricolin has joined #openstack-meeting14:44
*** amotoki has joined #openstack-meeting14:48
*** amitgandhinz has quit IRC14:48
*** amitgandhinz has joined #openstack-meeting14:49
*** tonytan_brb has joined #openstack-meeting14:49
*** jckasper has quit IRC14:49
*** jckasper has joined #openstack-meeting14:50
*** jckasper has quit IRC14:50
*** annegentle has joined #openstack-meeting14:50
*** tonytan4ever has quit IRC14:50
*** maeca2 has quit IRC14:51
*** jckasper has joined #openstack-meeting14:51
*** Swami has joined #openstack-meeting14:52
*** markvoelker has joined #openstack-meeting14:52
*** sudipto has quit IRC14:54
*** nkrinner is now known as nkrinner_afk14:54
*** ricolin has quit IRC14:54
*** m_kazuhiro has joined #openstack-meeting14:54
*** sudipto has joined #openstack-meeting14:55
*** sudipto has quit IRC14:55
*** saju_m has quit IRC14:57
*** bobh has joined #openstack-meeting14:58
*** m_kazuhiro has quit IRC14:59
*** Drago has joined #openstack-meeting14:59
*** david-lyle_ has quit IRC14:59
*** asselin_ has joined #openstack-meeting14:59
*** ijw has joined #openstack-meeting15:00
Zarastoryboard meeting time! anyone around?15:00
*** shamail has quit IRC15:00
*** m_kazuhiro has joined #openstack-meeting15:01
matthewbodkinhey15:01
Zara#startmeeting storyboard15:01
openstackMeeting started Wed Aug 31 15:01:20 2016 UTC and is due to finish in 60 minutes.  The chair is Zara. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: storyboard)"15:01
*** Drago has left #openstack-meeting15:01
openstackThe meeting name has been set to 'storyboard'15:01
Zara#link https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting15:01
*** tongli_ has quit IRC15:01
Zara#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: storyboard)"15:02
ZaraNone here!15:02
Zara#topic Urgent Items15:02
*** openstack changes topic to "Urgent Items (Meeting topic: storyboard)"15:02
SotKhey!15:02
Zaranone listed, again.15:02
*** tongli has joined #openstack-meeting15:02
Zara#topic In Progress Work15:02
*** openstack changes topic to "In Progress Work (Meeting topic: storyboard)"15:02
ZaraI didn't get round to updating the agenda with mine15:02
*** bobh has quit IRC15:02
ZaraI've been documenting the python client!15:03
Zara#info Zara has been documenting the python client15:03
Zaraand misc other things15:03
Zara#link https://review.openstack.org/#/c/362878/315:03
*** efried has joined #openstack-meeting15:03
Zarawe have a couple of patches for the gerrit-storyboard syntax docs awaiting reviews15:04
Zara#link https://review.openstack.org/#/c/360668/15:04
Zaraand15:04
Zara#link https://review.openstack.org/#/c/361423/15:04
Zaraother than that, tiny UI fixes and review from me.15:04
*** dmellado is now known as dmellado|mtg15:04
*** m_kazuhiro has quit IRC15:04
SotKI've been fixing bugs in the events timeline patch15:05
SotKand am now fixing bugs in the subscriptions for worklists patch15:05
*** bvandenh has quit IRC15:05
SotKand soon I will resend them both containing less bugs15:05
*** ricolin has joined #openstack-meeting15:05
Zara\o/15:05
ricolino/15:05
Zarahi ricolin15:06
*** enriquetaso has joined #openstack-meeting15:06
Zarathe versions with more bugs are more fun to review, but I think it's a fair trade-off :)15:06
*** tongli has quit IRC15:07
Zaraany updates from anyone else?15:07
Zaraoh, I also tried to look at task links/notes aliasing last week, to unblock the complex priorities patch15:08
SotKThe "add to worklist from story view" thing hasn't moved since I've been sidetracked fixing bugs15:08
*** azbiswas has joined #openstack-meeting15:08
*** ronghui has quit IRC15:08
Zarahah, snappish.15:08
Zarawell I tried to fix the thing blocking it and discovered I'd misunderstood something15:08
Zaraso I hope to look at it again after the meeting15:09
*** ijw has quit IRC15:09
*** armax has joined #openstack-meeting15:09
*** _coolsvap_ is now known as coolsvap15:09
*** hemnafk is now known as hemna15:09
Zaraotherwise I'll need to ask about process for renaming something in the db, and I imagine do it as two migrations15:09
Zara(that is, rename as one, new thing with old name as other)15:09
SotKshould be able to do it all in one migration15:10
*** yamahata has joined #openstack-meeting15:10
SotK(rename column, add new column with old name)15:10
ZaraI thought two would be easier to avoid mistakes if I'm not sure of it, but if I can run it by someone before I run it then I'm happy to try it all-in-one15:10
*** iyamahat has joined #openstack-meeting15:10
*** zhurong has quit IRC15:11
persiaThe problem with two migrations is that it is trickier to ensure the DB is in a consistent state after a commit.15:11
persiaDoing the transition in a single migration is likely more sensible.15:11
*** msmol has quit IRC15:12
Zarabut it's a shame; I thought to unblock it all we'd need would be for task links to be called task notes everywhere except the db (and one place in the api that changes the name to 'notes')...15:12
Zarabut then I couldn't find a way to do that15:12
Zaraso if there are any pointers on that I can get on that now15:12
*** Leom has joined #openstack-meeting15:12
*** azbiswas has quit IRC15:12
*** dprince has quit IRC15:13
Zaraanyway, that's where that's at.15:13
Zarano discussion topics...15:13
Zaraso if nobody has anything to add...15:14
Zara#topic Open Discussion15:14
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"15:14
*** Leom_ has joined #openstack-meeting15:14
*** tongli has joined #openstack-meeting15:14
ZaraI think that's our record! anybody have anything to discuss?15:14
Zaraone week later, ish, gerrit integration seems to be working fine15:15
*** sudipto has joined #openstack-meeting15:15
*** tonytan4ever has joined #openstack-meeting15:15
*** rrecio has joined #openstack-meeting15:15
Zarathough I've just remembered we meant to make sure it could auth for private stories15:16
Zarazaro also asked in-channel about the process for adding projects to storyboard, which I wanted to ask about more widely, but he doesn't seem to be about right now15:17
*** Leom has quit IRC15:17
*** tongli has quit IRC15:18
*** tonytan_brb has quit IRC15:18
Zarastill, if any infra folk have some input on that, maybe it's good to have it here for the logs15:18
*** Hosam has joined #openstack-meeting15:19
Zara^ fungi15:19
Zara(this is for non-infra projects)15:19
fungibasically just adding use-storyboard: true in the gerrit/projects.yaml file in the openstack-infra/project-config repo15:20
*** ronghui has joined #openstack-meeting15:20
fungithough if they need existing bugs imported from launchpad that gets trickier15:20
fungiwe'll have a migration plan at some point for how/when to make that happen properly15:20
Zaraokay, thank you. :) should I update the storyboard stuff in system-config? there's a note that says only infra projects should go up on storyboard, but I think that's out of date15:21
*** Rong_hui has quit IRC15:21
*** hockeynut has joined #openstack-meeting15:21
Zarayeah, I have a feeling the lp migration script has some cobwebs15:21
fungiyeah, i think it's fine to update that, though the situation is still a little complex15:21
*** pcaruana has quit IRC15:22
*** rcernin has quit IRC15:22
*** liuhanxi has quit IRC15:22
Zaraheh, okay, I can mention that things are more complex for folks wishing to import existing bugs...15:22
fungieven once we get the migration script fixed up for current storyboard, there's still the complication that many projects in launchpad have bug overlap with other projects (bugs affecting multiple projects) so it's fiddly if we import one project and not the others15:23
Zarainching forward toward the day when it can say 'GO FOR IT, FULFILL ALL YOUR TASK-TRACKING DREAMS'15:23
Zaraah, okay15:23
fungiwhich is why coordinating a migration is touchy... we pretty much need to do a lot of our major projects as a big-bang cutover15:23
*** sudipto has quit IRC15:23
fungiall-or-none there15:24
Zarayeah, especially awkward since the whole strength is how it works for cross-project work.15:24
*** CarolBarrett has joined #openstack-meeting15:24
fungiit would be easier if lp didn't also work passably for cross-project task tracking :/15:24
fungibut because it does, we have quite a lot of interlinked bug reports in there15:25
*** su_zhang has quit IRC15:25
Zarayeah15:26
*** su_zhang has joined #openstack-meeting15:26
*** jprivard has quit IRC15:26
*** yamamoto has quit IRC15:26
*** andreas_s has quit IRC15:27
*** ljxiash has quit IRC15:29
*** janki has joined #openstack-meeting15:29
*** sandanar has joined #openstack-meeting15:29
*** su_zhang has quit IRC15:30
*** jasond has joined #openstack-meeting15:30
ZaraI hope we can find a way forward with it; so far we've talked to a representative from nova about their blockers and they don't seem too big, but other projects are an unknown.15:30
*** jasond has left #openstack-meeting15:31
*** dmellado|mtg is now known as dmellado15:33
*** jlanoux has quit IRC15:34
* SotK hopes so too15:34
*** tonytan_brb has joined #openstack-meeting15:36
*** tesseract- has quit IRC15:36
*** tommylikehu_ has joined #openstack-meeting15:37
ZaraI intend to make some noise around the python client so people can try interacting with the StoryBoard api15:37
Zarasince I can guess that that will come up again and again15:37
Zaraas every project will have scripts15:38
*** tonytan4ever has quit IRC15:38
SotKthat is probably a good start15:39
Zaraso actually, that reminds me, I think we either need a new home for those docs online, or we put them in wiht hte storyboard odcs15:39
Zaraerm, put them in with the storyboard docs15:40
*** salv-orlando has joined #openstack-meeting15:40
Zarathe python client has docs in its own repo15:40
*** sdake_ is now known as sdake15:40
persiaAre the python client docs rendered somewhere accessible?15:40
*** adiantum has quit IRC15:41
Zaranot that I'm aware of, that's what I mean15:41
*** eezhova has quit IRC15:41
ZaraI don't think they're on docs.openstack.org, and now sure how things get there15:41
persiaTo follow the example of other projects, I think they belong in different places.15:42
persiaContrast the python-novaclient docs to the compute API docs.15:43
Zarayeah, the webclient is on storyboard so I wondered if that would stop folks looking elsewhere for python client docs and just assume we had none15:43
Zara*webclient docs are lumped in with storyboard api docs15:43
persiaPersonally, I think the webclient docs belong somewhere else, but I'm not sure there's a good default yet.15:43
* SotK agrees that webclient docs belong elsewhere15:43
*** mikelk has quit IRC15:44
Zaraagree, though storyboard is a lot smaller than nova so I'm not sure it matters so much.15:44
persiaI suspect the right place to ask is the javascript team meeting, to find best practices for other JS UI docs.15:44
*** banix has quit IRC15:44
* SotK agrees with that too15:44
persiaPity that just concluded, so there's 166.25 hours until the next one :)15:44
ZaraI'm in favour of separating the docs and then making docs for one part to link to the docs for the other parts15:44
*** cody-somerville has quit IRC15:45
*** armax has quit IRC15:45
Zaraso to me it's a question for infra about how to put repo-contents on docs.o.o, and then we just move things/link things as necessary.15:46
*** salv-orlando has quit IRC15:46
*** _nadya_ has quit IRC15:46
persiaSeems a sensible approach.15:46
*** armax has joined #openstack-meeting15:47
SotKit may be that there is a favoured tool for js projects that is not sphinx15:47
*** matrohon has quit IRC15:48
*** markvoelker has quit IRC15:48
*** mugsie_ has quit IRC15:49
Zarayeah, there's been work and discussion on it and I'm not sure where it's up to off the top of my head; krotscheck, wanna fill us in?15:49
krotscheckThere is, sortof.15:49
Zarauh oh15:50
* krotscheck is fighting with an infant for access to the keyboard15:50
krotscheckThere's a project called jsdoc-sphinx15:50
*** janki has quit IRC15:50
krotscheckIt converts JSDoc output into RST, which we then pipe through sphinx15:50
*** cbouch has joined #openstack-meeting15:50
*** jgregor has joined #openstack-meeting15:50
krotscheckThe tool is not perfect, but it's better than nothing15:50
*** diablo_rojo has joined #openstack-meeting15:50
*** tommylikehu_ has quit IRC15:51
krotscheckFor an idea of how to do this, look at this patch: https://review.openstack.org/#/c/358120/15:51
*** tommylikehu_ has joined #openstack-meeting15:52
Zaraah, thanks15:52
ZaraI will start experimenting with that though to begin with I'll try to get a home for pythonclient things15:53
*** swap-nil has joined #openstack-meeting15:53
Zarasince we have webclient docs up, albeit in the wrong place15:53
Zarawhereas we have no pythonclient docs up15:53
Zaraso that's marked as more urgent in my head15:53
SotKthat looks helpful, thanks krotscheck15:53
ZaraI'm happy to see js things getting more independence from python tools in the openstack world15:54
*** rcernin has joined #openstack-meeting15:54
*** banix has joined #openstack-meeting15:55
Zara#action Zara to ask infra about a home for python client docs15:56
Zara3 mins left15:57
*** sheel has joined #openstack-meeting15:57
* SotK has nothing else to discuss15:57
Zaraokay, ending this meeting! Thanks, everyone! :)15:58
Zara#endmeeting storyboard15:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:58
openstackMeeting ended Wed Aug 31 15:58:41 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:58
SotKthanks Zara :)15:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2016/storyboard.2016-08-31-15.01.html15:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2016/storyboard.2016-08-31-15.01.txt15:58
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2016/storyboard.2016-08-31-15.01.log.html15:58
*** Akis__ has joined #openstack-meeting15:58
matthewbodkinthanks guys, and with that I need to head off for my driving lesson, 'night15:59
*** Akis__ has quit IRC15:59
*** Akis__ has joined #openstack-meeting15:59
smcginnis#startmeeting Cinder16:00
openstackMeeting started Wed Aug 31 16:00:01 2016 UTC and is due to finish in 60 minutes.  The chair is smcginnis. 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
smcginnisping dulek duncant eharney geguileo winston-d e0ne jungleboyj jgriffith thingee smcginnis hemna xyang1 tbarron scottda erlon rhedlind jbernard _alastor_ bluex patrickeast dongwenjuan JaniceLee cFouts Thelo vivekd adrianofr mtanino yuriy_n17 karlamrhein diablo_rojo jay.xu jgregor baumann rajinir wilson-l reduxio wanghao thrawn01 chris_morrell stevemar watanabe.isao,tommylike.hu16:00
openstackThe meeting name has been set to 'cinder'16:00
geguileoo/16:00
*** matthewbodkin has quit IRC16:00
_alastor__o/16:00
*** mugsie_ has joined #openstack-meeting16:00
*** tbarron has joined #openstack-meeting16:00
eharney\o16:00
jgregorHola16:00
smcginnishttps://wiki.openstack.org/wiki/CinderMeetings#Next_Cinder_Team_meeting16:00
baumannHello16:00
tbarronhi16:00
ntpttro/16:00
DuncanTHey16:00
scottdahi16:00
mtaninohi16:00
smcginnis#topic Announcements16:00
*** openstack changes topic to "Announcements (Meeting topic: Cinder)"16:00
swap-nilhi16:00
*** gyee has joined #openstack-meeting16:00
smcginnisSomehow we are already at N-316:01
tommylikehu_hi16:01
smcginnisTime flies when you're having fun.16:01
smcginnis#link https://releases.openstack.org/newton/schedule.html16:01
tommylikehu_that's true16:01
diablo_rojoHello :)16:01
dulekhi16:01
smcginnisSo this is feature freeze, soft string freeze, and client freeze.16:01
*** sindhu has quit IRC16:01
smcginnisAnd requirements freeze.16:01
e0nehi16:01
SwansonHello16:01
dulekFreezes are explained here: https://releases.openstack.org/newton/schedule.html16:01
geguileosmcginnis: If somebody wants to request an FFE, when does it need to happen?16:02
diablo_rojoTime flies when you're having fun.16:02
xyang1hi16:02
smcginnisSo let's try to wrap up any outstanding items, then work on testing and making sure we're sending out something good.16:02
DuncanTIt's too warm here to freeze anything.16:02
*** weshay is now known as weshay_food16:02
smcginnisgeguileo: Begging and gifts of high quality coffee. :)16:02
geguileoDuncanT: +116:02
*** Akis_ has quit IRC16:02
smcginnisgeguileo: I don't think we need a formal FFE process.16:02
geguileosmcginnis: And is there a date limit?16:02
smcginnisAt least we haven't so far.16:02
geguileosmcginnis: So anytime within the next 2 weeks would be OK?16:03
smcginnisI've always left it at the discretion of the core team whether to allow anything in after the freeze.16:03
smcginnisBased on the risk and importance.16:03
*** jungleboyj has quit IRC16:03
DuncanThttps://review.openstack.org/#/c/337061/ is been aproved for a while but is triggering jenkins bugs, I'd like to nominate it for FFE16:03
smcginnisgeguileo: Yeah, I think so.16:03
*** imcsk8_ is now known as imcsk816:03
*** jungleboyj has joined #openstack-meeting16:03
geguileosmcginnis: Thanks16:03
smcginnisUp until we tag RC I think is OK, if we are all OK with the risk of letting it in.16:03
jungleboyjo/16:03
tommylikehu_+116:04
DuncanTI'll chase the jenkins issue again16:04
smcginnisDuncanT: I'm hoping this last recheck makes it through.16:04
*** edtubill has joined #openstack-meeting16:04
e0nehttps://review.openstack.org/#/c/178262/ - can we get it in Newton?16:04
tommylikehu_hoping so16:04
geguileoDuncanT: +116:04
*** Guest36472 has joined #openstack-meeting16:04
*** saggi has quit IRC16:04
geguileo(not to the chase but to the FFE)16:04
*** xyang2 has joined #openstack-meeting16:04
e0neDuncanT: IMO, FFE is good if it caused by jenkins failure16:04
DuncanTsmcginnis: It is triggering a know bug in the ansible code according to infra folks.16:05
smcginnisIf anyone has any high priority items to make it in to Newton, please ping cores in #openstack-cinder and make sure we are aware of it.16:05
DuncanTe0ne: I agree, just wanted to bring it up16:05
*** devananda|MOVING is now known as devananda16:05
smcginnisDuncanT: Oh? I hadn't heard of that one yet.16:05
smcginnise0ne: Yeah, I agree too.16:05
smcginnis#topic Options for maintaining os-brick on stable branches16:06
*** openstack changes topic to "Options for maintaining os-brick on stable branches (Meeting topic: Cinder)"16:06
smcginnisgeguileo: Hey16:06
geguileoHi!16:06
hemnahey16:06
*** ildikov has quit IRC16:06
geguileoOk, we seem to be stuck in a situation where we cannot change stable releases os-brick versions16:06
smcginnishemna: Speaking of backward compatibility: https://review.openstack.org/#/c/363444/16:06
geguileoOn one hand we don't do backports, even though semver would allow it16:06
hemnageguileo, why do we need to?  there is no upper constraint, just get the latest version16:07
*** rockyg has joined #openstack-meeting16:07
smcginnisI think that was always fine until we added privsep.16:07
geguileohemna: What do you mean there's no upper constraint?16:07
geguileohemna: There is an upper constraint in requirements project16:07
hemnais there?16:07
geguileoYes16:07
hemnabah16:07
dulekCurrently 1.5 I think.16:07
smcginnisSo we've never really had a need to do a stable library release before. But that doesn't mean we can't.16:08
geguileoAnd if we try to bump it like here16:08
eharneyi don't see much reason not to do releases for older branches16:08
geguileohttps://review.openstack.org/36087816:08
e0nehemna: https://github.com/openstack/requirements/blob/stable/mitaka/upper-constraints.txt16:08
eharneyit will be nice for large fixes once master has moved forward a lot16:08
hemnaeharney, +116:08
*** Jeffreyc42 has quit IRC16:08
geguileoWe have problems because now we have privsep and we cannot do the version bump16:08
diablo_rojodulek, Yes I think you're right, 1.516:08
e0neeharney: +116:08
geguileoeharney: +116:08
tommylikehu_+116:08
smcginnisOur policy isn't/wasn't that we absolutely will not do stable releases. Just we never had a need to before.16:08
geguileoAnd we already have a bunch of patches in stable/liberty ahead of master16:09
hemnaso the issue is pulling a new version of brick that then installs privsep where it didn't exist previously?16:09
geguileohttps://github.com/openstack/os-brick/compare/0.5.0...stable/liberty16:09
DuncanTAre we better dumping privsep as a failed experiment? Seems to have done way more harm than good, and has bought zero security improvements so far16:09
*** jprovazn has joined #openstack-meeting16:09
hemnaDuncanT, -116:09
*** hashar has quit IRC16:09
smcginnisWhat? How is privsep a failed experiment?16:09
hemnanah man, we can't16:09
eharneyi'm pretty sure we should continue with privsep16:09
*** Julien-zte has quit IRC16:09
geguileoeharney: +116:09
hemnaif we go that route, then the same argument will be made that brick is a failed experiment16:09
DuncanTWhy?16:09
jungleboyjDuncanT: Agreed.  It has been a mess!16:10
*** ygbo has quit IRC16:10
DuncanThemna: Ah, ok, that's a point, though I would disagree with anybody saying that16:10
smcginnisWe've had some transition issues, but I don't think the premise is wrong.16:10
eharneywe are working on initial problems, but the good stuff like https://review.openstack.org/#/c/312498/ is still barely starting16:10
jungleboyjhemna: I don't think they would say that.16:10
hemnabecause nova won't tolerate going back to being tightly coupled with rootwrap filters and brick versions.16:10
smcginniseharney: +116:10
diablo_rojojungleboyj, How much luck have you had talking to angus about the crap messages it throws?16:10
hemnajungleboyj, that's what nova was saying previously16:10
hemnajungleboyj, that unless we fixed the rootwrap filter nightmare that nova wanted to nuke using brick.16:11
*** links has joined #openstack-meeting16:11
jungleboyjdiablo_rojo: I have a todo to get him more info this week.16:11
hemnait's the entire reason we moved to privsep in the first place16:11
jungleboyjHope to work on that tomorrow maybe.16:11
*** Sukhdev has joined #openstack-meeting16:11
smcginnisgeguileo: I don't think with stable policy we can do much for liberty anymore. But we could certainly release a new Mitaka os-brick release.16:11
hemnadiablo_rojo, I have a defect filed against privsep that's been there for a while16:11
jungleboyjhemna: Ah, ok.  So we did privsep to make Nova happy.16:11
hemnazero response, and the bug hasn't been triaged16:11
eharneyjungleboyj: no16:12
geguileosmcginnis: Yeah, I wasn't aiming at liberty really  XD16:12
*** azbiswas has joined #openstack-meeting16:12
DuncanTeharney: Ah ha, I hadn't seen that, thanks, that is more encouraging16:12
jungleboyjhemna: I have one for some issues where privsep just doesn't send any info back that had us wrapped around the axel for days.16:12
geguileosmcginnis: I just think that we should allow backports to os-brick and do stable releases16:12
smcginnisjungleboyj: To decouple the need to copy rootwrap files between nova and cinder and to be able to move forward with better more secure privileged code.16:12
hemnajungleboyj, yes, because when new connectors are added or when a new command needs to be executed for a connector, you have to ship os-brick, and then put a patch against nova to add the new rootwrap filter.16:12
eharneyjungleboyj: there are pure-cinder things that privsep gives us, i dunno where that's coming from16:12
hemnathat's bad mmmkay16:12
diablo_rojohemna, *sigh*16:12
jungleboyjhemna: For an issue that is easy to encounter.16:12
smcginnisgeguileo: I'm good with that.16:12
*** asettle has quit IRC16:12
geguileosmcginnis: Should we vote?16:12
*** tongli has joined #openstack-meeting16:13
*** ianw has quit IRC16:13
smcginnisgeguileo: We can get some things backported, then raise the Mitaka upper constraints after we release a 1.4.1 or whatever version it would be.16:13
geguileosmcginnis: Because in the end it'll be the stable maintainer who'll -2 those patches16:13
geguileoXD16:13
hemnageguileo, so what and how many are we needing to backport16:13
smcginnisJust has to be minor backwards compatible bugfixes.16:13
*** asettle has joined #openstack-meeting16:13
* jungleboyj nominates diablo_rojo to support privsep. ;-)16:13
geguileohemna: Well, there's the multipath patches16:13
geguileohemna: And there was another patch trying to get in16:13
*** sindhu has joined #openstack-meeting16:13
*** vhoward has joined #openstack-meeting16:13
*** leeantho has joined #openstack-meeting16:14
hemnawell, I'm not sure those are really issues to be honest16:14
diablo_rojosmcginnis, That sounds like a decent plan.16:14
geguileohemna: For now, I can think of 4 patches16:14
jungleboyjhemna: eharney Ok, I will be honest that I haven't fully understood the privsep stuff.16:14
geguileosmcginnis: +116:14
*** singhj has joined #openstack-meeting16:14
jungleboyjsmcginnis: So we would add a 1.4.1 release for stable/mitaka to get wanted bug fixes in?16:14
hemnaok, so I'm fine with backports because of privsep16:14
smcginnisjungleboyj: Yep.16:14
*** Akis_ has joined #openstack-meeting16:15
jungleboyjsmcginnis: Ok, sounds good.16:15
smcginnisSo stable folks, let's look at backports for os-brick.16:15
smcginnisIf we're good with what's there we can request a new .1 release.16:15
geguileoSo we all agree that backporting in os-brick is allowed and that we'll do stable releases?16:15
smcginnisOnce that's released we can raise upper-constraints for stable/mitaka16:15
scottda+116:15
DuncanTjungleboyj: See the patch Eric linked... it shows what privsep is *meant* to be like16:15
smcginnisgeguileo: Judiciously16:15
hemnashit, so mitaka is stuck at 1.2.016:15
hemnafwiw16:15
hemnaso even if we did a 1.2.1 for a bugfix mitaka won't get it16:16
hemnaand 1.2.0 is ancient.16:16
hemnahttps://github.com/openstack/requirements/blob/stable/mitaka/upper-constraints.txt#L20216:16
hemnaso I don't think we are solving anything.16:16
smcginnishemna: Why wouldn't it get a 1.2.1?16:16
hemnait's upper constraint pegged at 1.2.016:16
*** winston-d has joined #openstack-meeting16:16
smcginnisIt certainly limits what we can get backported, but we can raise the upper constraint to 1.2.1 once we have a release.16:16
geguileohemna: Even if we end up not solving anything for Mitaka, maybe it will help for Newton once it's in stable16:16
*** Sukhdev has quit IRC16:17
*** yamamoto has joined #openstack-meeting16:17
jungleboyjDuncanT: Will do.16:17
hemnaare we even allowed to touch those upper constraints for stable branches ?16:17
smcginnisgeguileo: Might not be an issue after this point. At least until another big thing like privsep comes along.16:17
eharneyyou can bump them via the normal requirements process on its stable branch to some degree16:17
smcginnishemna: Yeah, we can if we need to.16:17
hemnaok16:17
*** asettle has quit IRC16:17
hemna1.2.0 is so damn old though16:17
smcginnishemna: No kidding. I was hoping it was newer than that.16:17
hemna:(16:18
*** duvarenkov has quit IRC16:18
smcginnisDidn't realize we had done so much since Mitaka freeze.16:18
*** shamail has joined #openstack-meeting16:18
*** sindhu has quit IRC16:18
hemnaanyway, mitaka is crazy out of date with brick then16:18
jungleboyjhemna: and diablo_rojo were busy!16:18
*** Akis__ has quit IRC16:18
hemnaso backporting fixes to mitaka isn't really reasonable16:18
*** sindhu has joined #openstack-meeting16:18
hemnajungleboyj, :)16:19
smcginnishemna: There's probably not too much we can actually backport, but maybe some bugfixes.16:19
hemnabut that also means that newton is the first release to use privsep16:19
smcginnisYep16:19
geguileohemna: I think some patches can actually be backported16:19
ntpttrhemna: yeah actually another thing I ran into in rolling upgrades testing is that cinder-manage doesn't work after pulling down master16:19
hemnasmcginnis, there have been so many changes since the 1.1.X and 1.2.X versions that it's to many changes imho16:20
diablo_rojohemna, Is that a bad thing since we aren't really sure if it works now anyways?16:20
ntpttrbecause of an import in brick that it can't find16:20
hemnaI completely rewrote the multipath code since 1.2.x16:20
eharneythis is a good example of something that would be backported to mitaka os-brick: https://review.openstack.org/#/c/341085/16:20
hemnait would be tough16:20
*** ijw has joined #openstack-meeting16:20
dulekntpttr: Same happens when you install 1.5, which is in upper-constraints?16:20
hemnaeharney, the encryptors stuff didn't exist back then in brick16:21
geguileohemna: Yeah, maybe they can't be backported16:21
ntpttrdulek: the only thing I tried to fix it, which worked, was to do 'pip install -U os-brick'16:21
geguileohemna: But at least we open the patch to do backports for the future16:21
ntpttrthat fixed the problem16:21
smcginnisOK, we'll see if there is enough that can be backported and enough value to warrant a new stable release. If so we can do the release and bump the upper constraint.16:21
geguileohemna: If it doesn't work for Mitaka, bad luck  ;-)16:21
eharneythe executor stuff did...16:21
smcginnisIf not, oh well16:21
geguileosmcginnis: +116:21
diablo_rojoShould we make a list of things to backport somewhere?16:21
hemnageguileo, but I thought the reasoning behing allowing backports was because of privsep16:21
hemnaso.....16:22
*** lpetrut has quit IRC16:22
hemnaNewton requires it16:22
geguileohemna: Not only because of privsep16:22
smcginnisThat's just the compelling reason at this point I think.16:22
eharneydiablo_rojo: we should track such things in launchpad, there are methods for doing that we've used for a long time already16:22
*** Benj_ has joined #openstack-meeting16:22
hemnaand prior to Newton the upper constraints is so old that backporting is going to be tough16:22
diablo_rojoeharney, That works.16:22
geguileohemna: But we probably cannot go on bumping stable os-brick version unless we ensure backward compatibility16:22
geguileohemna: Which afaik we don't do16:22
smcginnisDefinitely we're not backporting privsep! :)16:22
hemnaI'm just saying I'm not seeing much value.  the backports to the 1.1.x and 1.2.x will be few and far between.16:22
smcginnishemna: Your probably right.16:23
eharney1.1.x and 1.2.x are both Newton... it will take a bit to see what we'd want to backport there?  (and we'd only backport to 1.2.x anyway, i think)16:23
diablo_rojoAgreed16:23
*** Swami has quit IRC16:23
hemnageguileo, well for the most part that's been the idea.  any of my major work I've done in os-brick has always tried, if not required backwards compatibility16:23
hemnaand I was under the assumption that always had to be the case.16:23
*** dmorita has joined #openstack-meeting16:23
jungleboyjsmcginnis: Oh come on, live dangerously.  ;-)16:23
*** gzholtkevych has joined #openstack-meeting16:24
eharneyif 1.1.x was created and obsoleted within newton then there isn't a reason to backport to it16:24
hemnaeharney, +116:24
geguileohemna: It should be the case, but we don't try it as strictly as in cinder afaik16:24
jungleboyjFor future reference, though, this is important to agree upon.  Unfortunate that privsep complicates it in this case.16:24
*** ijw has quit IRC16:24
hemnageguileo, I've been enforcing it as much as possible in brick16:25
diablo_rojoeharney +116:25
hemnawhich is one of the reasons that diablo_rojo and I had so much trouble getting the connector break out patch in16:25
*** sridharg has quit IRC16:25
eharneyto be sure on backward compatibility we need to define a policy and ensure we have gate jobs to back it up16:25
diablo_rojohemna yeah that was..quite the experience..16:25
eharneyi don't really know how close we are to that at this point16:25
e0neeharney: +116:25
*** shashank_hegde has joined #openstack-meeting16:25
geguileoeharney: +116:26
smcginniseharney: I think the tests run when we try to bump the u-c are the enforcement there, but too little too late probably.16:26
*** tongli_ has joined #openstack-meeting16:26
eharneyi think today we were mostly trying to find our way toward a policy16:26
hemnaeharney, there are gate jobs that test ceph and lio16:26
smcginnisI don't think our policy was ever that we wouldn't do a stable library release. Just that we never had need to before.16:27
hemnaso I guess what I'm asking is, does it make sense to allow an Ocata/Master fix backported to stable/Newton16:27
smcginnisOnward and upward.16:27
hemnasince newton requires privsep16:27
hemnaand that's really the major limiting factor IMO16:27
*** donghao has quit IRC16:27
eharneyi think it does because a lot of fixes will be independent of privsep (hopefully)16:27
jungleboyjhemna: It sounds like that is what we are leaning towards.16:28
smcginniseharney: +116:28
eharneyor be reworked to fit the old model as part of the backport process16:28
hemnaeharney, sure, but the reason we wanted to allow backports was because we couldn't force privsep on older releases16:28
jungleboyjprivsep just complicates it in this case.16:28
eharneyi don't think that was the reason...16:28
hemnaand now moving forward privsep will be there, just get the latest version.16:28
smcginniseharney: If we need to change rootwrap filters, I don't think that's going to fly.16:28
*** roxanaghe has joined #openstack-meeting16:28
hemnaeharney, afaik it was16:28
*** dmorita has quit IRC16:28
smcginnishemna: +1 Yep16:28
geguileohemna: If we don't allow backports, and we'll be doing version bumps, we need a job to test os-brick against N-1 release on every patch, right?16:28
hemnathat's the only justification16:29
eharneywell, i'll say it this way, that's not the reason i'm interested in backports16:29
geguileoBy version bumps I mean bumping the upper constraints16:29
*** tongli has quit IRC16:29
*** mickeys has joined #openstack-meeting16:29
eharneyit's the same idea as cinder stable backports... you grab important fixes and assess risk vs benefit etc16:29
hemnageguileo, yah to have newton get a new version it'd require a upper constraints bump16:29
*** dprince has joined #openstack-meeting16:30
*** longxiongqiu has quit IRC16:30
geguileohemna: But then we should be making sure nothing in master gets merged that would break that, right?16:30
*** tongli_ has quit IRC16:30
hemnathe one downside to just pulling the latest, is you'll get new features16:30
smcginnisgeguileo: The patch to raise u-c will test that, but that doesn't help make sure nothing gets in to break backwards compat before then.16:30
*** ub has quit IRC16:30
*** yamamoto has quit IRC16:30
hemnawhen you may have only wanted a simple critical bug fix16:30
geguileosmcginnis: That's the problem16:30
smcginnisgeguileo: Yeah16:30
*** weshay_food is now known as weshay16:30
geguileosmcginnis: By then, if it's broken we probably have no way of getting out16:31
winston-dwhat's the highest os-brick version w/o privsep?16:31
*** ricolin has quit IRC16:31
geguileosmcginnis: Because we can't do the bump or backports16:31
hemna1.4 ?16:31
geguileosmcginnis: Same situation as we are now16:31
smcginniswinston-d: 1.4. I believe.16:31
hemnaso from a distribution's perspective they'd just want bug fixes I'd guess16:31
hemnaand not be required to pull the latest version for an older release, just to get a fix in.16:31
smcginnisgeguileo: Well, if we backport and it fails when we try to raise to 1.4.1, we could always go for a 1.4.2, right. ;)16:32
winston-dso I assume the stable os-brick would be do another 1.4.x release with some 1.5+ changes backported to 1.4.x?16:32
*** tongli has joined #openstack-meeting16:32
hemnaso for newton are we going to set the upper constraint to <= 1.7.0 ?16:32
smcginniswinston-d: We might have to look at 1.2.1 since 1.2.0 was the cap for Mitaka.16:32
hemnathen any 1.6.X fixes can go in16:32
*** sindhu has quit IRC16:32
hemna1.6.0 is the latest release16:33
hemnaand is what newton will use16:33
winston-dsmcginnis: so bumping cap for stable branch is not allowed?16:33
smcginnisIt's currently 1.5 https://github.com/openstack/requirements/blob/master/upper-constraints.txt#L20116:33
jungleboyjhemna: I think that makes sense.16:33
smcginnishemna: We need to address the unit test failures from using 1.6 before we can raise it.16:33
geguileowinston-d: It is allowed afaik16:33
hemnaeharney, does that make sense ?16:33
winston-dnova and cinder is the only consumer/downstream project of os-brick, I assume.16:33
smcginnishemna: I was going to ask for a 1.6.1 that adds the connector mapping that Tony put up.16:34
hemnawinston-d, the cinderclient extension does16:34
hemnaas well16:34
hemnasmcginnis, +116:34
eharneyit would be <1.7.0... but, i think so16:34
winston-dok, so if nova.mitaka & cinderclient extension.mitaka is happy iwht 1.4x os-brick, we can bump upper cap then.16:34
hemnaeharney, ah yah < not <=16:35
eharneynova mitaka has u-c of ==1.2.016:35
*** egallen has quit IRC16:35
eharneycinder mitaka has !=1.4.016:35
jungleboyjeharney: Oh yeah, we need to make sure not to forget Nova.  :-)16:35
hemnawinston-d, master u-c is 1.5.016:35
hemnaso newton is already using privsep (as a requirement for nova)16:36
eharneyjungleboyj: the requirements process manages all of this centrally anyway, in theory... it should be pretty hard to forget and break it16:36
smcginniseharney: Oh yeah, I think 1.4 was actually where we added privsep, then everything blew up in grenade tests and there was the lengthy debate about how to handle upgrades.16:36
diablo_rojoeharney, Lol, in theory.16:36
*** tongli has quit IRC16:36
jungleboyjeharney: :-)  *crossing fingers*16:36
*** shashank_hegde has quit IRC16:37
winston-dso 1.3.x then...16:37
smcginnisWell, in the interest of time, we can look at doing stable releases if we need to. Let's move on.16:37
smcginnisgeguileo: That OK?16:37
hemnasmcginnis, I'm ok with it fwiw16:37
smcginnishemna: Thanks! :)16:37
*** Jeffreyc42 has joined #openstack-meeting16:37
*** sindhu has joined #openstack-meeting16:37
smcginnisDid we lose geguileo ?16:38
*** tongli has joined #openstack-meeting16:38
geguileosmcginnis: No I'm here16:38
geguileolol16:38
smcginnisgeguileo: :)16:38
smcginnisgeguileo: You ok if I move on?16:38
jungleboyjsmcginnis: He started the fight and left.  ;-)16:38
hemnaI just really wanted to understand the reasoning and need.16:38
geguileosmcginnis: If you set an agreed item I will be glad to move on  ;-)16:38
smcginnisIf we have a needm then there's a reason. :)16:38
DuncanT20 minute warning...16:39
smcginnisgeguileo: I think the agreed item is we will look at what can be backported safely, and if things needed can safely be backported we will do a stable release and raise the Mitaka upper constraints.16:39
*** aswadr_ has joined #openstack-meeting16:39
smcginnisAnyone absolutely against that?16:39
geguileosmcginnis: I'm ok with that16:40
smcginnisOK...16:40
smcginnis#topic Add volume-type filter to Get-Pools16:40
*** openstack changes topic to "Add volume-type filter to Get-Pools (Meeting topic: Cinder)"16:40
tommylikehu_yes, small feature https://review.openstack.org/#/c/362747/16:40
smcginnistommylikehu_: You're up.16:40
tommylikehu_depends on https://blueprints.launchpad.net/cinder/+spec/allow-api-users-to-get-info-about-a-specified-pool16:40
smcginnisSeems reasonable. So just like we have volume_backend=X extra specs, you're prosposing including pool as an explicit option?16:41
*** lbrune has quit IRC16:41
* smcginnis hasn't read the spec yet16:41
eharneyis it true that you can always determine which types can and can't land on a pool in a meaningful way?16:42
bswartzspec was published yesterday...16:42
tommylikehu_smcginnis:yes16:42
smcginnis#link https://review.openstack.org/#/c/362747/ Pool spec16:42
DuncanTeharney: Almost totally true, and should be true16:42
tommylikehu_lol16:42
*** tongli has quit IRC16:43
smcginnistommylikehu_: We'll be reviewing specs for Ocata soon. Is there a specific point you wanted to discuss in the meeting?16:43
tommylikehu_actual no16:43
smcginnistommylikehu_: Or just get visibility and awareness?16:43
smcginnistommylikehu_: OK, cool.16:43
*** ianw has joined #openstack-meeting16:43
*** _nadya_ has joined #openstack-meeting16:43
*** dmorita has joined #openstack-meeting16:43
smcginnistommylikehu_: I'll move along then. Thanks!16:43
smcginnis#topic Whether use OVO object instead of ORM object in a function receiving OVO object through RPC16:43
*** openstack changes topic to "Whether use OVO object instead of ORM object in a function receiving OVO object through RPC (Meeting topic: Cinder)"16:43
*** tongli has joined #openstack-meeting16:44
smcginnisLisa's not here though.16:44
Guest36472smcginnis: I am here16:44
smcginnisGuest36472: Oh good.16:44
*** _nadya_ has quit IRC16:44
jungleboyjHiding as a guest.16:44
smcginnis#link https://etherpad.openstack.org/p/patch26860816:44
Guest36472let me clarify the problem: https://review.openstack.org/#/c/268609/31/cinder/volume/manager.py in the function of detach_volume, both ovo object and db object is used16:44
smcginnisI'm looking to dulek and geguileo :)16:45
Guest36472the problem is that in this patch I add corresponding interfaces in ovo object, and use ovo object instead of db object16:45
dulekI'm here. ;)16:45
geguileosmcginnis: I've reviewed both patches in question16:45
dulekI thought we've agreed that this is fine for objects flying over RPC and the problem was if we want to switch from sending plain IDs to sending whole o.vo16:46
geguileosmcginnis: And I don't think we really have any problem, but let's hear what Guest36472 has to say16:46
geguileodulek: +116:46
Guest36472smcginnis: geguileo: dulek: John raised a question whether should add usch ovo methods as seems it increases complex16:47
geguileoGuest36472: I know, but we discussed it on the IRC channel16:47
*** yamamoto has joined #openstack-meeting16:47
geguileoGuest36472: And I think he ended up saying that it was ok16:47
geguileoAt least that's what I last remember16:47
bswartzwhen OVO was introduced, the theory was that we wouldn't need to use ORM objects anymore on RPC call handlers16:48
*** tongli has quit IRC16:48
Guest36472I didn't get his response from the irc. But anyway if both of you think it is ok, I will move on16:48
*** Apoorva has joined #openstack-meeting16:48
geguileoGuest36472: I think it's OK16:48
geguileoJust some nits I commented on the patches16:49
bswartzit was supposed to act more or less like OVO does in nova, but without a conductor service16:49
Guest36472geguileo: yes I just submitted the patches, but I think I still have some update to do16:49
geguileobswartz: Yeah, and I really think we should make our scheduler work as a conductor for OVOs16:49
Guest36472geguileo: +116:50
DuncanTWe should probably update the devref with details of where we're aiming to get to with this ovo work16:50
smcginnis10 minute warning16:50
DuncanTgeguileo: Why?16:50
*** numans has quit IRC16:50
dulekDuncanT: That would help us with DB schema changes.16:50
geguileoDuncanT: Because right now it's quite "fragile" and we have a lot of complex stuff going on to work around the lack of conductor16:51
dulekDuncanT: Nova is handling a lot of DB upgtrade problems in o.vo because only conductor accesses the DB.16:51
dulek(techically conductor and n-api)16:51
DuncanTIf we're going that way, add a conductor, don't overload the scheduler16:51
winston-dDuncanT: +116:52
*** _nadya_ has joined #openstack-meeting16:52
geguileoDuncanT: Well, this is quick work16:52
* bswartz wonders if conductor is a better approach to rolling upgrades than what we have16:52
jungleboyjDuncanT: Oh, we have been here before.  :-)16:52
dulekDuncanT: Hm, +1, we might want to switch to something like Gannt one day16:52
DuncanTc-api performance would suck if we got rid of direct db access in api16:52
geguileoDuncanT: But I'm ok either way16:52
hemnaDuncanT, +116:52
*** piet has joined #openstack-meeting16:52
geguileoDuncanT: Oh, but the idea wouldn't be to have an actual conductor16:52
*** roxanaghe has quit IRC16:52
DuncanTgeguileo: Can we talk in the cinder channel after the meeting? I'd like to understand the issues16:52
geguileoDuncanT: It would only be a service to do the backporting of OVOs when necessary16:53
dulekbswartz: It helps with schema changes - you can upgrade conductors in an atomic steps - requests will get queued in MQ.16:53
smcginnisMight be good to take this there later since we still have another topic.16:53
geguileoDuncanT: Ok16:53
geguileosmcginnis: +116:53
bswartzdulek: I know how it works, what I don't know is whether it's superior to what we're trying to do16:53
dulekOkay, so we've agreed Lisa's patches are okay?16:53
smcginnisGuest36472: Thanks16:53
Guest36472thanks all of yo16:53
Guest36472s/yo/you16:53
smcginnisdulek: I think that was what I was hearing.16:53
*** roxanaghe has joined #openstack-meeting16:54
smcginnisWith some comments to address yet.16:54
*** lbrune has joined #openstack-meeting16:54
smcginnis#topic Marking NFS as unsupported16:54
*** openstack changes topic to "Marking NFS as unsupported (Meeting topic: Cinder)"16:54
smcginnisDuncanT: Have at it. :)16:54
* jungleboyj start crying16:54
jungleboyj;-)16:54
e0ne:)16:54
DuncanTSo I bought this up. We defined a policy a few weeks ago, we should follow it16:54
diablo_rojojungleboyj, Lol16:54
smcginnisjungleboyj: I was just typing up something along those lines! :)16:55
e0neDuncanT: +116:55
hemnaDuncanT, because there is no NFS CI ?16:55
jungleboyjDuncanT: +116:55
jungleboyjI agree.16:55
DuncanTNFS fails to have CI and it fails to meet minimum features16:55
jgregorDuncanT: +116:55
DuncanT(I did ping jungleboyj privately, for the record, to see how much pain this would cause)16:55
smcginnisDuncanT: You also mention block driver in the meeting agenda as well...16:55
hemnaenable_unsupported_driver=True16:55
jungleboyjSo, mriedem Responded to the note I sent to the mailing list noting the first thing we should do is get the existing CI working without snapshots and cloning.16:56
DuncanTNeed to check if the raw block device driver meets minimum features or not16:56
eharneyi objected to doing this for Mitaka because it causes upgrade issues for people16:56
jungleboyjDuncanT: I know, giving you a hard time buddy.16:56
*** egallen has joined #openstack-meeting16:56
smcginniseharney: Objected to what exactly?16:56
e0neDuncanT: it does, AFAIR16:56
eharneyjungleboyj: when i worked on CI, i didn't think it was valuable to make the job run w/o the snapshot features16:56
hemnaeharney, so does removing drivers.  that issue is dead.16:56
jungleboyjI have baumann working on that now.16:56
DuncanTeharney: It is meant to. It is an unsupported driver16:56
*** Guest36472 has quit IRC16:56
DuncanTe0ne: Ok. The agenda item was purely to remind me to ask :-)16:56
eharneyhemna: DuncanT: i'll be satisfied with that when someone can explain what it gains us16:56
hemnathe driver code stays in tree.16:57
*** unicell has quit IRC16:57
hemnaand the deployer can re-enable it.16:57
eharneyok16:57
hemnainstead of having to go out to git and copy/paste code into their new tree.16:57
DuncanTeharney: It encourages vendors to fix their shit, and the inconvenience encourages customers to pressure vendors into fixing their shit16:57
jungleboyjeharney: It is just following our process.  We will get things fixed up and move on.16:57
*** salv-orlando has joined #openstack-meeting16:57
*** tongli has joined #openstack-meeting16:57
eharneyDuncanT: the shit is being fixed at maximum shit-fixing speed now16:57
jungleboyjeharney: It is a little silly but I think we should eat our own dog food here.16:57
hemnaat least they have a mechanism to getting access to their volumes.16:57
eharneybut it's fine if we'd like to go along with the policy, sure16:58
mriedemeharney: you don't see value in a CI job that runs with the cinder NFS driver?16:58
mriedemwhen hacking on said driver?16:58
*** ivar-lazzaro has joined #openstack-meeting16:58
eharneymriedem: not what i said... i made the CI job.  i just intended to let it fail until snapshots landed16:58
*** rpioso has joined #openstack-meeting16:58
DuncanTeharney: This time, yes, but we have a process, we should follow it. If they fix it before release, we can remove the unsupported flag, and no hard done16:58
DuncanTeharney: Same as any other vendor16:58
eharneyDuncanT: ok16:58
mriedemeharney: being able to attach and detach a volume to a VM is kind of a big deal16:58
mriedemregardless of snapshots16:58
jungleboyjeharney: How long do you think before we can land the snapshot support?16:58
*** shamail has left #openstack-meeting16:59
hemnacan we just skip the snapshot tests for now ?16:59
eharneyhemna: that's the proposal16:59
hemnaat least we have a ci up and running16:59
jungleboyjhemna: ++16:59
hemnaok, I'd be ok with that.16:59
hemnawe all skip tests for some reason or another at times.16:59
e0nehemna: +116:59
smcginnisIn order to run the CI tests for this, the job will need to set the enable_unsupported_drivers option.17:00
*** anilvenkata has quit IRC17:00
*** esker is now known as esker[away]17:00
smcginnisIf we add that flag.17:00
smcginnisShoot, time.17:00
smcginnisThanks everyone.17:00
*** bobh has joined #openstack-meeting17:00
DuncanTI'll try to throw an unsupported driver patch up, it will be interesting to see what it looks like17:00
smcginnis#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Wed Aug 31 17:00:45 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2016/cinder.2016-08-31-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2016/cinder.2016-08-31-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2016/cinder.2016-08-31-16.00.log.html17:00
jlvillal#startmeeting ironic_qa17:00
openstackMeeting started Wed Aug 31 17:00:54 2016 UTC and is due to finish in 60 minutes.  The chair is jlvillal. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: ironic_qa)"17:01
openstackThe meeting name has been set to 'ironic_qa'17:01
smcginnisjlvillal: Sorry for the delay. :)17:01
jlvillalsmcginnis: Thanks!17:01
rpiosoo/17:01
*** cdearborn has joined #openstack-meeting17:01
geguileoThanks!17:01
cdearborno/17:01
jlvillalSo I was going to cancel this meeting as not much has been done on multi-node.17:01
jlvillalI have been trying to focus on Newton priorities this week.17:02
jlvillalAny objections?17:02
*** winston-d has left #openstack-meeting17:02
jlvillalSorry for the late notice :(17:02
*** tongli has quit IRC17:02
rajiniro/17:02
*** vgadiraj has joined #openstack-meeting17:02
jlvillalI'll take that as no objections :)17:02
rajinirjlvillal:no problem17:02
jlvillalSorry for the late notice on cancellation. Go back to your Newton work! :)17:03
*** esker[away] is now known as esker17:03
*** iyamahat has quit IRC17:03
jlvillal#info Canceled meeting this week to focus on Newton deliverables17:03
jlvillal#endmeeting17:03
*** esker is now known as esker[away]17:03
*** tbarron has left #openstack-meeting17:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:03
openstackMeeting ended Wed Aug 31 17:03:34 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic_qa/2016/ironic_qa.2016-08-31-17.00.html17:03
*** saju_m has joined #openstack-meeting17:03
*** cdearborn has left #openstack-meeting17:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic_qa/2016/ironic_qa.2016-08-31-17.00.txt17:03
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic_qa/2016/ironic_qa.2016-08-31-17.00.log.html17:03
*** bobh has quit IRC17:05
*** yamahata has quit IRC17:05
*** ivar-laz_ has joined #openstack-meeting17:05
*** swap-nil has quit IRC17:07
*** ivar-lazzaro has quit IRC17:08
*** spzala has quit IRC17:09
*** mjturek has joined #openstack-meeting17:09
*** baojg has quit IRC17:10
*** egallen has quit IRC17:12
*** tongli has joined #openstack-meeting17:12
*** amitgandhinz has quit IRC17:12
*** dbecker has quit IRC17:13
*** amitgandhinz has joined #openstack-meeting17:13
*** egallen has joined #openstack-meeting17:13
*** su_zhang has joined #openstack-meeting17:15
*** markvoelker has joined #openstack-meeting17:15
*** e0ne has quit IRC17:16
*** tongli has quit IRC17:17
*** singhj has quit IRC17:17
*** xyang2 has quit IRC17:17
*** rossella_s has quit IRC17:18
*** rossella_s has joined #openstack-meeting17:19
*** su_zhang has quit IRC17:23
*** eezhova has joined #openstack-meeting17:23
*** iyamahat has joined #openstack-meeting17:23
*** esumerfd has quit IRC17:23
*** su_zhang has joined #openstack-meeting17:23
*** Jeffreyc42 has quit IRC17:23
*** su_zhang has quit IRC17:24
*** tongli has joined #openstack-meeting17:24
*** su_zhang has joined #openstack-meeting17:25
*** tommylikehu_ has quit IRC17:26
*** _nadya_ has quit IRC17:26
*** tongli has quit IRC17:28
*** esumerfd has joined #openstack-meeting17:28
*** vishnoianil has quit IRC17:29
*** tongli has joined #openstack-meeting17:30
*** jdob has joined #openstack-meeting17:31
*** tongli_ has joined #openstack-meeting17:31
*** cbouch has quit IRC17:32
*** manjeets_ has quit IRC17:34
*** tongli_ has quit IRC17:34
*** watanabe_isao has joined #openstack-meeting17:34
*** yamamoto has quit IRC17:34
*** tongli has quit IRC17:35
*** tongli_ has joined #openstack-meeting17:35
*** watanabe_isao has quit IRC17:36
*** bradjones has quit IRC17:38
*** ivar-laz_ has quit IRC17:38
*** bradjones has joined #openstack-meeting17:38
*** ivar-lazzaro has joined #openstack-meeting17:38
*** tonytan_brb has quit IRC17:38
*** pcaruana has joined #openstack-meeting17:39
*** tongli_ has quit IRC17:39
*** bradjones is now known as Guest3037417:39
*** egallen has quit IRC17:39
*** unicell has joined #openstack-meeting17:39
*** rpioso has quit IRC17:39
*** egallen has joined #openstack-meeting17:40
*** tongli has joined #openstack-meeting17:40
*** imcsk8 has left #openstack-meeting17:41
*** Leom_ has quit IRC17:41
*** yamahata has joined #openstack-meeting17:42
*** sindhu has quit IRC17:42
*** electrofelix has quit IRC17:42
*** sambetts is now known as sambetts|afk17:43
*** tongli has quit IRC17:43
*** ekcs has joined #openstack-meeting17:43
*** markvoelker has quit IRC17:43
*** tongli has joined #openstack-meeting17:44
*** rwsu has quit IRC17:44
*** tongli has quit IRC17:46
*** tongli has joined #openstack-meeting17:46
*** shashank_hegde has joined #openstack-meeting17:48
*** esker[away] is now known as esker17:49
*** tongli has quit IRC17:50
*** tongli has joined #openstack-meeting17:50
*** dimtruck is now known as zz_dimtruck17:51
*** Na3iL has quit IRC17:53
*** s3wong has joined #openstack-meeting17:54
*** ihrachys has quit IRC17:54
*** KamilRenczewski has joined #openstack-meeting17:54
*** rpioso has joined #openstack-meeting17:55
*** _nadya_ has joined #openstack-meeting17:55
*** georgk has joined #openstack-meeting17:56
*** tongli has quit IRC17:58
*** tongli has joined #openstack-meeting17:58
*** e0ne has joined #openstack-meeting17:59
*** bh526r has joined #openstack-meeting17:59
bh526r#startmeeting gluon17:59
openstackMeeting started Wed Aug 31 17:59:40 2016 UTC and is due to finish in 60 minutes.  The chair is bh526r. Information about MeetBot at http://wiki.debian.org/MeetBot.17:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:59
*** openstack changes topic to " (Meeting topic: gluon)"17:59
openstackThe meeting name has been set to 'gluon'17:59
KamilRenczewskiHi Bin17:59
bh526rHi Kamil17:59
bh526rHi everyone18:00
ALUVialo/18:00
*** tongli_ has joined #openstack-meeting18:00
bh526rHi Vince18:00
*** dkehn_ has quit IRC18:00
*** trevormc has joined #openstack-meeting18:00
bh526r#topic Roll Call and Introduction18:00
*** openstack changes topic to "Roll Call and Introduction (Meeting topic: gluon)"18:00
bh526r#info Bin Hu18:00
trevormco/18:00
KamilRenczewski#info Kamil Renczewski18:01
georgk#info Georg Kunz18:01
bh526rHi trevormc18:01
pcarver#info Paul Carver18:01
*** zz_dimtruck is now known as dimtruck18:01
*** SKipp_ has joined #openstack-meeting18:02
ALUVial#info Vincent Button18:02
*** liamji has quit IRC18:02
trevormcHi Bin, this is Trevor with the AT&T community team.18:02
tomhambleton#info Tom Hambleton18:02
bh526rHi Trevor, glad you join us18:02
bh526rwelcome onboard18:02
bh526r#topic Admin Update18:03
*** openstack changes topic to "Admin Update (Meeting topic: gluon)"18:03
*** tongli has quit IRC18:03
bh526r#info Not much admin update18:03
*** sarob has joined #openstack-meeting18:03
bh526r#topic Tracking Progress of PoC (JIRA Ticket in OPNFV)18:04
*** openstack changes topic to "Tracking Progress of PoC (JIRA Ticket in OPNFV) (Meeting topic: gluon)"18:04
*** eezhova has quit IRC18:04
*** singhj has joined #openstack-meeting18:04
*** spzala has joined #openstack-meeting18:05
bh526r#info we use JIRA in OPNFV to track the progress of PoC18:05
*** jgregor has left #openstack-meeting18:05
*** Jeffreyc42 has joined #openstack-meeting18:05
*** anilvenkata has joined #openstack-meeting18:05
jinli#info Jin Li18:05
jinliHi everyone18:05
bh526r#info The Epic is https://jira.opnfv.org/browse/NETREADY-2118:05
bh526rIt seems that opnfv.org is down for now18:05
Jeffreyc42#info Jeff Collins18:06
Jeffreyc42Hey guys18:06
bh526rHi Jeff18:06
*** CarolBarrett has quit IRC18:06
*** sudipto has joined #openstack-meeting18:06
*** Kevin_Zheng has quit IRC18:06
*** su_zhang has quit IRC18:07
*** bobh has joined #openstack-meeting18:07
*** syjulian has left #openstack-meeting18:07
bh526r#info we created one task for Ian to push the code from Github to our repo here18:07
*** salv-orl_ has joined #openstack-meeting18:08
bh526r#info https://jira.opnfv.org/browse/NETREADY-2318:08
*** larainema has quit IRC18:08
bh526r#info we create on story for Tom to work on Gluon Neutron ML2 Plugin: http://jira.opnfv.org/browse/NETREADY-2218:09
*** comay_ has quit IRC18:09
bh526r#info we added 2 initial tasks for now under this story18:09
bh526r#info Task 1 is the initial proposal describing ML2 approach: http://jira.opnfv.org/browse/NETREADY-2418:10
*** salv-orlando has quit IRC18:10
*** comay has joined #openstack-meeting18:11
bh526r#info Task 2 is to push interim code to Gerrit review, if any: http://jira.opnfv.org/browse/NETREADY-2518:11
*** tongli has joined #openstack-meeting18:11
bh526r#info More tasks will be added whenever needed18:11
*** Kevin_Zheng has joined #openstack-meeting18:11
*** larainema has joined #openstack-meeting18:11
*** lpetrut has joined #openstack-meeting18:12
bh526r#info The 2nd story is for Niko to work on database migration from sqllite to MySQL: http://jira.opnfv.org/browse/NETREADY-2618:12
*** egallen has quit IRC18:12
*** dkehn_ has joined #openstack-meeting18:12
*** xenogear has joined #openstack-meeting18:12
*** ShillaSaebi has joined #openstack-meeting18:12
*** nk2527 has quit IRC18:13
bh526r#info Initial task of this story is an implementation proposal of MySQL for database migration: http://jira.opnfv.org/browse/NETREADY-2718:13
*** jinli has quit IRC18:13
*** jamemcc has quit IRC18:14
bh526r#info More tasks will be added whenever needed18:14
*** sarob has quit IRC18:14
*** tongli_ has quit IRC18:14
bh526r#info In addition, other tasks such as addressing database sync, installer support, testing, etc., will be added soon18:15
bh526rAny question?18:15
trevormcIf Tom needs help with the Gluon Neutron ML2 Plugin I'm here to help. I would at least like to shadow if possible.18:16
KamilRenczewskiopnfv.org is back18:16
*** xenogear has quit IRC18:17
bh526rThank you Trevor, that's great.18:17
bh526rI will connect you with Tom too18:17
tomhambletonSounds good18:17
*** eezhova has joined #openstack-meeting18:18
*** Suyi_ has joined #openstack-meeting18:18
bh526r#info BTW, I forgot to mention that we will have 5 blades in our cloud infrastructure.18:18
*** tonytan4ever has joined #openstack-meeting18:18
bh526r#info the data center will be ready in 2 weeks.18:18
bh526r#info Then Daniel will work on migrating our blades in another week18:19
bh526r#info So our infrastructure will be ready by 9/2318:19
*** egallen has joined #openstack-meeting18:19
*** toscalix has quit IRC18:20
*** jamemcc has joined #openstack-meeting18:20
bh526r#topic New Blueprint Discussion18:20
*** openstack changes topic to "New Blueprint Discussion (Meeting topic: gluon)"18:20
*** prateek has quit IRC18:20
bh526r#info we have a BP Gluon Nova Plugin: https://blueprints.launchpad.net/python-gluon/+spec/gluon-nova-plugin18:21
bh526r#info It was assigned to Ian18:21
*** e0ne has quit IRC18:21
bh526r#info We discussed it last week, and Paul commented that it is better to add more details in this BP18:21
*** uxdanielle has quit IRC18:22
bh526r#info Ian is very busy, so he didn't have a chance to add more details yet18:22
*** e0ne has joined #openstack-meeting18:22
*** hashar has joined #openstack-meeting18:23
bh526r#info we can leave it open until Ian has time18:23
*** hashar is now known as hasharAway18:23
bh526rAny other comments or questions?18:23
bh526rThat's pretty much from my side18:24
*** egallen has quit IRC18:25
Jeffreyc42nope, I think you summed it all up18:25
bh526rThank you Jeff.18:25
tomhambletonGood summary.  Thanks for creating the Jira tasks.18:25
trevormcFor new comers to the project, what would be the best way to start contributing?18:25
*** vishnoianil has joined #openstack-meeting18:26
bh526rGood question. I will ask Ian to finish his task (i.e. pushing code from Github to our repo) first18:26
*** zaro has quit IRC18:26
*** sandanar_ has joined #openstack-meeting18:27
*** Sukhdev has joined #openstack-meeting18:27
bh526rThen you can look at the code18:27
trevormcAhh ok18:27
*** zaro has joined #openstack-meeting18:27
bh526rIt's not perfect yet18:27
bh526rTom is looking at ML2 plugin, which he will push some interim code (after Ian's task is done)18:27
bh526rSo you may work with Tom by reading his interim code, comment, and start to contribute to part of it18:28
*** sarob has joined #openstack-meeting18:28
*** _nadya_ has quit IRC18:28
*** sandanar_ has quit IRC18:28
KamilRenczewskiI am also interested in Tom's code as I am starting to work on Contrail mechanism driver18:29
*** sindhu has joined #openstack-meeting18:29
bh526rThere are other tasks such as updating devstack to install Gluon, install etcd, Fuel plugin to install Gluon,18:29
*** prateek has joined #openstack-meeting18:29
trevormcok we will look into installing gluon with devstack this week and report something in the next meeting.18:30
bh526rinvestigate and resovle sync issue between Gluon and Proton, synchronize binding operation with SDN-C etc18:30
*** sandanar has quit IRC18:30
tomhambletonOnce we get the repo in decent shape, there are many tasks that need to be done.18:30
tomhambletonI sent Bin a list yesterday18:30
*** ivar-lazzaro has quit IRC18:30
*** ivar-lazzaro has joined #openstack-meeting18:31
bh526rLet me put the list on our wiki and to our repo doc18:31
*** amotoki has quit IRC18:31
*** esker has quit IRC18:31
bh526rAnd I need to create series JIRA stories and tasks too for tracking the items on the list18:32
*** jaugustine has joined #openstack-meeting18:32
bh526rAny other questions/comments?18:32
bh526rif no more topics, I suggest to adjourn the meeting to save everyone 30 minutes18:33
bh526rThank you all, and talk to you next week18:34
georgkbye18:34
bh526r#info Meeting adjourned18:34
*** Leo_ has joined #openstack-meeting18:34
bh526rbye guys18:34
KamilRenczewskibye18:35
*** _nadya_ has joined #openstack-meeting18:35
Jeffreyc42bye18:35
*** rockyg has quit IRC18:35
bh526r#endmeeting18:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:35
openstackMeeting ended Wed Aug 31 18:35:16 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:35
*** yamamoto has joined #openstack-meeting18:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gluon/2016/gluon.2016-08-31-17.59.html18:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gluon/2016/gluon.2016-08-31-17.59.txt18:35
openstackLog:            http://eavesdrop.openstack.org/meetings/gluon/2016/gluon.2016-08-31-17.59.log.html18:35
*** sudipto has quit IRC18:35
tomhambletonBye all18:35
bh526rThank you Tom and bye18:36
*** dprince has quit IRC18:36
*** sshnaidm is now known as sshnaidm|afk18:36
*** ivar-lazzaro has quit IRC18:36
*** jaypipes has joined #openstack-meeting18:36
*** KamilRenczewski has left #openstack-meeting18:37
*** ivar-lazzaro has joined #openstack-meeting18:38
*** flwang1 has quit IRC18:38
*** mickeys has quit IRC18:39
*** xenogear has joined #openstack-meeting18:40
*** lbrune has quit IRC18:40
*** bh526r has quit IRC18:41
*** yamamoto has quit IRC18:42
*** SKipp_ has quit IRC18:43
*** tongli has quit IRC18:43
*** Sukhdev has quit IRC18:43
*** jinli has joined #openstack-meeting18:43
*** _nadya_ has quit IRC18:44
*** tongli has joined #openstack-meeting18:44
*** trevormc has left #openstack-meeting18:44
*** eezhova has quit IRC18:45
*** tongli_ has joined #openstack-meeting18:46
*** cdub has joined #openstack-meeting18:47
*** tongli has quit IRC18:48
*** hasharAway is now known as hashar18:49
*** ItSANgo has joined #openstack-meeting18:50
*** amakarov is now known as amakarov_away18:51
*** david-lyle_ has joined #openstack-meeting18:52
*** david-lyle_ has quit IRC18:52
*** nk2527 has joined #openstack-meeting18:53
*** rcaballeromx has joined #openstack-meeting18:54
*** sheel has quit IRC18:56
*** ijw has joined #openstack-meeting18:57
*** karlamrhein has joined #openstack-meeting18:57
*** dprince has joined #openstack-meeting18:59
*** rpioso has left #openstack-meeting19:00
*** ivar-lazzaro has quit IRC19:00
*** ildikov has joined #openstack-meeting19:01
*** sindhu has quit IRC19:02
*** hrybacki is now known as hrybacki|afk19:02
*** flwang1 has joined #openstack-meeting19:03
*** rvasilets__ has quit IRC19:03
*** ilyashakhat has joined #openstack-meeting19:05
ShillaSaebi#startmeeting docteam19:05
openstackMeeting started Wed Aug 31 19:05:30 2016 UTC and is due to finish in 60 minutes.  The chair is ShillaSaebi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:05
*** openstack changes topic to " (Meeting topic: docteam)"19:05
openstackThe meeting name has been set to 'docteam'19:05
ShillaSaebihello anyone here for the docs team meeting?19:05
strigazio/19:06
ShillaSaebihello strigazi19:06
rcaballeromxHello19:06
*** ivar-lazzaro has joined #openstack-meeting19:06
ShillaSaebihi rcaballeromx19:07
rcaballeromxHi ShillaSaebi!19:07
ShillaSaebialright lets give it another minute and then we can get started19:07
ShillaSaebiagendas looking pretty light today19:07
*** ronghui has quit IRC19:08
lbragstado/19:08
ShillaSaebihi lbragstad19:08
ShillaSaebiok looks like its the 4 of us19:08
ShillaSaebi#topic Action items from the last meeting19:08
*** openstack changes topic to "Action items from the last meeting (Meeting topic: docteam)"19:08
ShillaSaebithere are none19:08
ShillaSaebi#topic Specs in review19:09
*** openstack changes topic to "Specs in review (Meeting topic: docteam)"19:09
ShillaSaebi#link https://review.openstack.org/#/q/status:open+project:openstack/docs-specs,n,z19:09
ShillaSaebifeel free to take a peek at these19:09
ShillaSaebireview if possible19:09
*** Sam-I-Am has joined #openstack-meeting19:09
Sam-I-Amhello19:09
ShillaSaebihi Sam-I-Am19:09
ShillaSaebiwe were just discussing the action items from last week, which were none19:10
*** anilvenkata has quit IRC19:10
ShillaSaebiand now specs in review19:10
ShillaSaebi#link https://review.openstack.org/#/q/status:open+project:openstack/docs-specs,n,z19:10
Sam-I-Amjust a bit late today19:10
ShillaSaebino worries19:10
ShillaSaebiwe have a couple of specs out19:11
ShillaSaebi#topic Speciality teams19:11
*** openstack changes topic to "Speciality teams (Meeting topic: docteam)"19:11
ShillaSaebi#link https://etherpad.openstack.org/p/Speciality_Team_Reports19:11
ShillaSaebi#info install guide testing should be in progress19:12
ShillaSaebi#link https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting19:12
ShillaSaebiany updates from other speciality teams?19:12
Sam-I-Amnetworking guide...19:12
rcaballeromxI am part of the install guide testing.19:12
*** lbrune has joined #openstack-meeting19:12
*** lbrune has quit IRC19:12
rcaballeromxIf any of you have tips or any feedback I am open to suggestions.19:13
Sam-I-Amworking on restructuring the deployment scenarios, but a lot of new content is pouring in ahead of newton feature-freeze... thus i've been busy with it.19:13
*** lbrune has joined #openstack-meeting19:13
*** lbrune has quit IRC19:13
*** links has quit IRC19:13
*** eezhova has joined #openstack-meeting19:15
Sam-I-Amdont see many other specialty teams19:15
rcaballeromxThe personas content was updated with gender neutral names.19:16
rcaballeromx#link https://review.openstack.org/#/c/362337/19:16
*** ShillaSaebi_ has joined #openstack-meeting19:16
ShillaSaebi_sorry got d/c19:16
ShillaSaebi_anyone have anythign else to add on specialty teams?19:16
*** lbrune has joined #openstack-meeting19:16
Sam-I-Amnot i19:17
*** ShillaSaebi has quit IRC19:17
*** ShillaSaebi_ is now known as ShillaSaebi19:17
*** piet has quit IRC19:18
ShillaSaebi#topic Countdown to release:19:18
*** openstack changes topic to "Countdown to release: (Meeting topic: docteam)"19:18
ShillaSaebi#info 35 days until release19:18
Sam-I-Amsure comes up quickly19:19
ShillaSaebi#link https://wiki.openstack.org/wiki/Documentation/NewtonDeliverables19:19
ShillaSaebisure does19:19
*** salv-orl_ has quit IRC19:19
ShillaSaebianything else on that?19:19
Sam-I-Amnewp19:20
rcaballeromxNot from me.19:20
ShillaSaebi#topic Open Discussion19:20
*** openstack changes topic to "Open Discussion (Meeting topic: docteam)"19:20
*** e0ne has quit IRC19:20
ShillaSaebiI am very curious to know what happened at the ops guide session at the mid cycle19:20
*** ronghui has joined #openstack-meeting19:20
Sam-I-Ami went to the mid-cycle ops meetup last week19:20
ShillaSaebiSam-I-Am you were there for that right19:20
ShillaSaebihow did that go?19:20
Sam-I-Amthere wasn't a specific session about the ops guide, but documentation in general19:20
*** sarob has quit IRC19:20
*** vhoward has quit IRC19:20
rcaballeromxAnything interesting?19:21
Sam-I-Amthe tl;dr is that documentation is hard to find and isn't necessarily up to date19:21
Sam-I-Amthere's an etherpad from the discussion...19:21
Sam-I-Am#link https://etherpad.openstack.org/p/NYC-ops-Documentation19:21
ShillaSaebithank you19:21
ShillaSaebiill catch up on that in a bit19:21
Sam-I-Amthere's also some versioning issues... clients vs. services vs. things like APIs19:21
*** ivar-lazzaro has quit IRC19:22
*** coolsvap has quit IRC19:22
ShillaSaebiok19:22
*** ivar-lazzaro has joined #openstack-meeting19:22
rcaballeromxOk19:22
*** rfolco has quit IRC19:22
rcaballeromxI am happy to say that I will be going to Barcelona.19:22
ShillaSaebime 219:22
Sam-I-Amthere were also some devs present, so i floated the idea of more docs going into repos... or at least giving them the option. whatever works best, as long as the presentation is the same.19:22
*** anilvenkata has joined #openstack-meeting19:22
Sam-I-Ami'll probably be there too19:22
rcaballeromxWe can look further into these topics.19:23
ShillaSaebiwas there a lot of interest in the docs session? just curious19:23
*** rfolco has joined #openstack-meeting19:23
rcaballeromxI think the idea of project repos is great, as long as the content of the project repos use the same guidelines to ensure consistency and reusability.19:23
ShillaSaebi+119:23
strigazi+119:23
ShillaSaebiconsistency is key19:24
Sam-I-Amthere werent too many people at the session. however, it conflicted with the osops session19:24
Sam-I-Amwhich, arguably, is a form of docs that operators want19:24
rcaballeromxYes, developers provide content and the docs team ensure consistency...19:24
Sam-I-Amso the conclusion there was that our ops guide should reference the osops stuff19:24
ShillaSaebiok19:24
rcaballeromxOk. I am looking forward to meeting you guys.19:26
ShillaSaebiyeah ditto19:26
ShillaSaebionce we get closer to the summit, we should have room # and info19:26
ShillaSaebiwe can meet at the working sessions19:26
ShillaSaebiI look fwd to it as well19:26
rcaballeromxAbsolutely.19:26
ShillaSaebidoes anyone have anything else to bring up?19:27
*** lbrune has left #openstack-meeting19:27
Sam-I-Amnot me19:27
rcaballeromxNope19:27
strigazime neither19:27
ShillaSaebiok well thank you all for joining19:28
ShillaSaebimeeting adjourned19:28
ShillaSaebi#endmeeting19:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:28
openstackMeeting ended Wed Aug 31 19:28:09 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteam/2016/docteam.2016-08-31-19.05.html19:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteam/2016/docteam.2016-08-31-19.05.txt19:28
rcaballeromxTake care.19:28
openstackLog:            http://eavesdrop.openstack.org/meetings/docteam/2016/docteam.2016-08-31-19.05.log.html19:28
*** rcaballeromx has left #openstack-meeting19:28
*** claudiub has quit IRC19:29
Sam-I-Ambye19:29
*** Sam-I-Am has left #openstack-meeting19:29
*** gyee has quit IRC19:29
*** Swami has joined #openstack-meeting19:30
*** aswadr_ has quit IRC19:31
*** sdake_ has joined #openstack-meeting19:32
*** lbrune has joined #openstack-meeting19:33
*** sdake has quit IRC19:33
*** lbrune has quit IRC19:33
*** ShillaSaebi has quit IRC19:33
*** _nadya_ has joined #openstack-meeting19:34
*** sdake has joined #openstack-meeting19:35
*** egallen has joined #openstack-meeting19:35
*** sdake_ has quit IRC19:36
*** sarob has joined #openstack-meeting19:38
*** lbrune has joined #openstack-meeting19:39
*** mickeys has joined #openstack-meeting19:40
*** sarob has quit IRC19:42
*** pvaneck has joined #openstack-meeting19:43
*** rfolco has quit IRC19:43
*** rfolco has joined #openstack-meeting19:44
*** anilvenkata has quit IRC19:44
*** mickeys has quit IRC19:45
*** maeca1 has joined #openstack-meeting19:55
*** annegentle has quit IRC19:55
*** ekhugen has joined #openstack-meeting19:55
*** egallen has left #openstack-meeting19:56
ekhugen#startmeeting WOS-mentoring19:58
openstackMeeting started Wed Aug 31 19:58:15 2016 UTC and is due to finish in 60 minutes.  The chair is ekhugen. Information about MeetBot at http://wiki.debian.org/MeetBot.19:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:58
*** openstack changes topic to " (Meeting topic: WOS-mentoring)"19:58
openstackThe meeting name has been set to 'wos_mentoring'19:58
*** su_zhang has joined #openstack-meeting19:58
aimeeuhello!19:58
ekhugenhi aimeeu19:58
ekhugenanyone else on for WOS-mentoring yet?19:59
diablo_rojoHola :)19:59
ekhugenhi diablo_rojo19:59
ekhugenwe'll give people a few more minutes to join20:00
*** aimeeu has quit IRC20:00
*** georgk has left #openstack-meeting20:00
*** aimeeu has joined #openstack-meeting20:00
*** annegentle has joined #openstack-meeting20:00
ildikovo/20:01
ekhugenhi ildikov!20:01
ildikovhi ekhugen!20:01
ekhugen#topic WOS-mentoring agenda https://etherpad.openstack.org/p/WOS_mentoring_12_320:02
*** openstack changes topic to "WOS-mentoring agenda https://etherpad.openstack.org/p/WOS_mentoring_12_3 (Meeting topic: WOS-mentoring)"20:02
ekhugenI guess it's just the 4 of us, so might as well get started20:02
*** gyee has joined #openstack-meeting20:03
ekhugenFirst topic is speed mentoring at Barcelona20:03
*** _nadya_ has quit IRC20:03
*** tonytan4ever has quit IRC20:03
ekhugenI think we said we were going to put out a call for more mentors probably next week or so20:03
ekhugendoes anyone want to volunteer to send out the email to the listservs (probably the general one and the -dev one)?20:04
diablo_rojoThat survey has been all updated and stuff right?20:04
*** rfolco has quit IRC20:04
ekhugenoh that's a good point diablo_rojo, I was going to talk about surveys later20:04
ekhugenbut I still haven't heard back from Erin that the mentoring feedback survey is updated20:05
ekhugenwe were going to send her the updates to the main survey after we got the feedback survey out20:05
*** sarob has joined #openstack-meeting20:05
diablo_rojoI can volunteer to email the dev one :)20:05
*** rfolco has joined #openstack-meeting20:05
diablo_rojoHas the for to be a mentor gotten updated too?20:05
diablo_rojo*form20:05
ekhugenno, we had the updates for that ready, but we didn't send them to erin yet20:05
vkmco/20:06
ekhugenshe was kind of swamped with summit stuff, do you work with her regularly diablo_rojo20:06
ekhugenhi vkmc20:06
diablo_rojoErin Disney?20:06
ekhugenyes20:06
diablo_rojoI can probably get her to give me access to it to make the necessary changes.20:07
ekhugenoh that would be great, I can send you an  email with the changes20:07
ekhugencan you pm me your new email at the foundation, please?20:07
*** sigmavirus is now known as sigmavirus|awa20:07
diablo_rojosure :)20:08
*** sindhu has joined #openstack-meeting20:08
ekhugenthanks!20:08
ekhugenokay, so aside from the call for mentors, anything to talk about on Speed Mentoring?20:08
aimeeuHas it been officially scheduled yet?20:09
diablo_rojoaimeeu +120:09
ekhugenaimeeu no, I haven't seen that the summit has been opened up for workgroups sessions yet20:09
*** ivar-lazzaro has quit IRC20:09
aimeeuOk. That's coming in the next couple of weeks I presume.20:10
*** lbrune has quit IRC20:10
aimeeuAre we thinking Tuesday morning?20:10
*** jprovazn has quit IRC20:10
ekhugenI hope it's coming soon20:11
ekhugenyes, we were thinking Tuesday morning again, before the keynotes20:11
diablo_rojoSeems like a good time to me.20:11
*** eharney has quit IRC20:11
aimeeu+120:12
ekhugenwe will definitely need volunteers, as well20:12
*** ilyashakhat_mobi has joined #openstack-meeting20:13
*** sindhu has quit IRC20:13
ekhugenshould we put out a call for volunteers in the WOS meeting?  last time we had 3-4 people and I think that worked out well20:13
*** ivar-lazzaro has joined #openstack-meeting20:13
aimeeuThat's probably the best approach. I'm hesitant to commit since I don't know if work is sending me.20:13
*** synegy34 has joined #openstack-meeting20:13
ildikovit sounds like a good idea, you can never ping people enough times20:14
diablo_rojoVolunteering to be the mentors? Or for what?20:14
ekhugenokay, the next WOS meeting is on Labor Day in the US, is anyone planning on calling in?20:14
*** ilyashakhat has quit IRC20:14
aimeeuI think that meeting has been cancelled20:14
*** synegy34 has quit IRC20:14
*** synegy34 has joined #openstack-meeting20:15
ekhugenwell we said we'd send out a call for mentors in mid-september, but we'll also need volunteers to help direct people/help with the rotations20:15
ekhugenalso room setup and cleanup20:15
*** piet has joined #openstack-meeting20:15
aimeeuI can certainly help with setup/cleanup etc (if I'm going...)20:15
diablo_rojoekhugen I would call in.20:15
diablo_rojoBut I think aimeeu is right.. I think its been cancelled20:16
aimeeuThe WOS Agenda tracker has the next meeting scheduled for 19 Sept20:16
*** gatekeep has quit IRC20:16
diablo_rojoShould we email the WoO mailing list? Or just wait?20:16
ekhugenoh okay, sorry I was looking at the calendar entry instead20:16
*** tongli_ has quit IRC20:16
ekhugenI think waiting until the meeting on the 19th won't be too bad20:16
ekhugenhopefully everyone will know for sure if they'll be in Barcelona or not by then20:17
diablo_rojoStill over a month in advance.20:17
diablo_rojoYeah that should be good.20:17
aimeeuFor helping the day off - I'll add it to the meeting agenda etherpad20:17
ekhugenthanks aimeeu20:17
ekhugenwe'll probably also need some help ahead of time, last time we did a prep meeting for the mentors to let them know what to expect20:18
ekhugenand we did the baseball cards20:18
diablo_rojoI talked to Erin and she is making the changes to the form now.20:18
ekhugenoh awesome! it'll be good to get that out and get some feedback on how the first round of matches have gone20:19
*** banix has quit IRC20:19
ekhugenso maybe if we ask at the meeting on the 19th for volunteers to help with the speed mentoring event day of and also help with prep20:20
diablo_rojoSounds good to me20:21
aimeeuI've added that to the meeting agenda20:21
ekhugencool, any other questions or topics on Speed Mentoring?20:21
*** rstarmer has quit IRC20:22
*** dimtruck is now known as zz_dimtruck20:23
ekhugenokay, next topic is interaction with upstream training, ildikov any updates?20:23
*** sarob has quit IRC20:23
ildikovthe training is now added to the schedule: https://www.openstack.org/summit/barcelona-2016/summit-schedule/#day=2016-10-2320:23
ekhugen#topic WOS-mentoring interaction with upstream training20:23
*** openstack changes topic to "WOS-mentoring interaction with upstream training (Meeting topic: WOS-mentoring)"20:23
*** sindhu has joined #openstack-meeting20:23
ildikovekhugen: sorry, I was too fast :)20:23
ildikov#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/#day=2016-10-2320:24
ildikov#link https://www.openstack.org/summit/barcelona-2016/summit-schedule/#day=2016-10-2420:24
*** sarob has joined #openstack-meeting20:24
ildikovthe RSVP is also open, we have 50 people as a limit for the course and 20 spots on the waiting list20:24
ildikovI've just recognised that the mentoring program question is missing from the form, so I'll ask for an update20:25
ekhugennice ildikov20:25
*** sarob has quit IRC20:25
ildikovwe are planning for remote/virtual sprints to update the existing content and have new modules as well20:25
*** hockeynut has quit IRC20:26
ekhugenare you still planning a tooling sprint as well?20:26
ildikovif anyone interested from this group I created a Doodle poll to see what dates can work: #link http://doodle.com/poll/geaq6fdsg749nsnc20:27
ildikovekhugen: I need to double check that with Marton, but if we can find a slot with a few people interested I think we can add that as well20:27
ekhugenalright, let us know20:28
ildikovekhugen: as we are getting closer to the Summit it might get lower priorities depending on progress with the training content and setup20:28
ekhugenis the upstream training team looking for everyone to also be in the mentoring program as well as upstream training, or is that just optional20:28
*** sarob has joined #openstack-meeting20:28
ildikovI sent out a mail to the WoO and Docs mailing lists, so if you're interested you can also send a reply, it might gets more people interested20:29
*** jpeeler has quit IRC20:30
ekhugensounds like a good idea20:30
ildikovekhugen: you mean the attendees to participate in the mentoring program?20:30
ekhugenright, last time we really encouraged everyone to sign up for both20:30
ekhugenI don't know if that was really necessary though20:31
*** ilyashakhat_mobi has quit IRC20:31
ildikovso the question that's currently missing is Whether the applicants are interested in attending a mentoring program or not20:31
ekhugenokay, so we're just going to offer that as an option this time20:31
ildikovmaybe it's a sign that the phrasing was not good enough in the original one :)20:31
*** sarob has quit IRC20:31
ildikovso the thing is that I don't think we can force people into it20:32
ildikovso the idea behind the question was to see how much people are interested20:32
ekhugenwell last time we did spend a lot of time "encouraging" people into it and yeah, maybe it's better to just ask if they're interested20:32
ildikovI would like to encourage people as well as we all know the training itself will not be enough20:32
*** claudiub has joined #openstack-meeting20:32
ildikovit's a good foundation, but it's really the step before the first kinda thing20:33
ekhugenyes, agreed20:33
ildikovif you have any suggestion on how to phrase a question to be an encouragement as well that would be great20:33
ildikovalso if you have any other suggestions I'm happy to do those as well, like social media, etc.20:34
ekhugenhm, maybe something like "Mentoring can be a great way to continue learning after the class has ended.  Would you be interested in signing up for the long-term mentoring program?"20:34
ildikovI would like to avoid having much effort in paring people with mentors, etc. and end up not many people interested20:34
ildikovcool, that definitely sounds better than my original one was :)20:35
*** whenry has quit IRC20:35
ildikovThanks!20:35
ekhugenyw20:35
ekhugenanything else about the  interaction with upstream and mentoring?20:36
*** torgomatic has joined #openstack-meeting20:36
ildikovwe are also trying to have a more modular architecture for the training20:36
ildikovand extending the scope with modules like documentation or working groups20:36
ildikovif any of you have an area in mind that would be great to have covered as part of this training please ping me or add it to the etherpad20:37
ekhugenthat makes sense, so the modules could be taught individually to groups that have less time?20:37
ildikovalso if any of you would like to participate in putting together the material for either of these modules you're more than welcomed :)20:37
ekhugenthanks20:38
ildikovI would rather say that we would like to reach out to people who's primary focus is not necessarily code contribution20:38
*** sarob has joined #openstack-meeting20:39
ildikovso we plan to have a common introduction part to talk about where and how to register, how to communicate, where to find information, etc.20:39
ildikovand then have the more specific modules in parallel20:39
ildikovlike who's interested in code they can learn how to run the unit and functional tests for instance, while others interested more in docs they can learn how to build docs with Sphinx locally20:40
ekhugenalso good ideas20:40
ildikovit also depends how diverse the group will be by the end of the day, maybe everyone will want to do only code this time20:41
*** mickeys has joined #openstack-meeting20:41
ekhugenyes, definitely, is there anything you need from the mentoring team, other than maybe help on writing the modules?20:42
ildikovbut the material itself should be easy to maintain, so I'm not afraid of having wasted efforts on this as it will all be publicly available and can be visited later by anyone to learn something new20:42
ildikovI wonder how much you have mentors for these new modules?20:42
*** mickeys has quit IRC20:42
*** mickeys_ has joined #openstack-meeting20:42
ekhugenyou mean mentors who can help write the modules?20:43
ildikovfor instance the WG concept sometimes seems a bit unclear to even those who run one20:43
ildikovso I meant more how we can help and maybe even mentor these people20:43
ildikovI wouldn't say it's for Barcelona though, I think it's a more long term question20:44
ekhugenoh like mentors for non-technical things?  we do have the career mentoring available for non-technical people20:44
ekhugenand I think several of our mentors there are workgroup leaders20:45
ildikovah ok, that's great!20:45
*** sarob has quit IRC20:45
ildikovthen I would say if anyone can chime in and if not writing, but reviewing the material as we go that would be very helpful20:46
ildikovin my experience reviewing can be an even bigger bottleneck than finding someone to add content20:46
ekhugenokay, maybe we can send out a note to our career mentors at some point and ask if any of them are interested in helping review the material20:47
ekhugenmaybe after barcelona20:47
ildikovthat sounds good20:47
ildikovI can also send out summary mails with a few review links as a reminder if anyone has the bandwidth to check them20:47
ekhugenokay, cool20:47
*** sarob has joined #openstack-meeting20:47
*** jrichli has joined #openstack-meeting20:48
ildikovI don't have much more in mind now, I think we touched on the most important parts20:48
*** cdub has quit IRC20:48
ekhugenokay, thanks!20:48
ekhugennext topic was the graduation plan20:48
ekhugen#topic mentoring graduation plan20:49
*** openstack changes topic to "mentoring graduation plan (Meeting topic: WOS-mentoring)"20:49
ekhugenlast time we said we wanted to wait until we had some more people20:49
*** cdub has joined #openstack-meeting20:50
ekhugendo we have enough people to discuss it?  or do we want to wait for the feedback survey results to discuss it more?20:50
diablo_rojoRight. I still don't have any ideas lol.20:50
diablo_rojoI think the survey results would help.20:50
aimeeuMaybe the survey results will give us ideas20:50
diablo_rojoAnd the survey hasn't been sent out yet right?20:50
ekhugenright, once erin has that updated, we can send it out20:51
diablo_rojoI have a link for it that I can pm to whomever wants to right the email to the current mentor/mentees.20:51
diablo_rojoHa ha *write20:51
diablo_rojonot right20:51
diablo_rojoWow its been a long day20:51
ekhugenit's just this one, right (write :-p)? https://openstackfoundation.formstack.com/forms/mentoring_feedback_survey20:51
diablo_rojoYes that looks right ;)20:52
ekhugenso yes, does anyone want to volunteer to send out the emails (after Erin gets the updates in, obvs)?20:52
ekhugenI can generate the list of emails20:53
diablo_rojoWait a sec..she said it was updated... this is the link she gave me. https://openstackfoundation.formstack.com/forms/mentoring_feedback_survey20:54
diablo_rojoDoes that not have the changes?20:54
ekhugenwell it doesn't  say Austin anymore so that's update.  I think we also asked if the follow up question could have a box for them to put in a way for us to follow up20:54
ekhugenbecause otherwise we won't know how to contact them20:55
ekhugen(or even who they are)20:55
*** eharney has joined #openstack-meeting20:55
*** bobh_ has joined #openstack-meeting20:55
*** DL has joined #openstack-meeting20:56
*** e0ne has joined #openstack-meeting20:56
*** m_kazuhiro has joined #openstack-meeting20:56
*** rtheis has quit IRC20:56
*** DL is now known as Guest9450920:56
ekhugenI can send erin a follow up email20:56
*** cutforth has joined #openstack-meeting20:57
diablo_rojoOkay cool.20:57
ekhugenI think we only have a few minutes left before the next meeting starts, any other topics?20:57
ekhugenare we okay with every other week meetings, or should we go back to every week as we get closer to the summit20:57
ekhugen#topic open discussion20:57
*** openstack changes topic to "open discussion (Meeting topic: WOS-mentoring)"20:57
diablo_rojoMaybe do every week towards the end of September/ start of October?20:58
*** hosanai has joined #openstack-meeting20:58
ekhugenokay we'll revisit in on the 14th20:58
ekhugenrevisit it*20:58
ekhugenthanks everyone for attending!20:58
*** jdob has quit IRC20:58
*** patchbot has joined #openstack-meeting20:58
*** kota_ has joined #openstack-meeting20:59
diablo_rojoThank you!20:59
ekhugen#endmeeting20:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:59
openstackMeeting ended Wed Aug 31 20:59:22 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/wos_mentoring/2016/wos_mentoring.2016-08-31-19.58.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/wos_mentoring/2016/wos_mentoring.2016-08-31-19.58.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/wos_mentoring/2016/wos_mentoring.2016-08-31-19.58.log.html20:59
ildikovthanks ekhugen and all!20:59
*** timur has joined #openstack-meeting20:59
*** bobh has quit IRC20:59
*** pdardeau has joined #openstack-meeting20:59
notmynameswift team meeting time21:00
*** nadeem has joined #openstack-meeting21:00
*** rwsu has joined #openstack-meeting21:00
notmyname#startmeeting swift21:00
*** jungleboyj has quit IRC21:00
openstackMeeting started Wed Aug 31 21:00:11 2016 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
patchbotYou've given me 5 invalid commands within the last 60 seconds; I'm now ignoring you for 10 minutes.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
*** lbrune has joined #openstack-meeting21:00
*** ekhugen has left #openstack-meeting21:00
notmynamewho's here for the swift team meeting?21:00
bkeller`o/21:00
pdardeauo/21:00
mathiasbo/21:00
*** rfolco has quit IRC21:00
jrichlihi21:00
cutforthhola21:00
nadeemhi21:00
cschwedeo/21:00
kota_hello21:00
tdasilvaeu21:00
hosanaio/21:00
torgomatic.21:00
dmoritahi21:00
m_kazuhiroo/21:00
mattoliverauo/21:01
kmARCo/21:01
*** timburke has joined #openstack-meeting21:01
notmynamewelcome everyone21:01
notmynameseveral things to go over this week. agenda is at..21:01
notmyname#link https://wiki.openstack.org/wiki/Meetings/Swift21:01
notmynamefirst up...21:02
notmyname#topic new swift core21:02
*** openstack changes topic to "new swift core (Meeting topic: swift)"21:02
notmynameI'm happy to announce that jrichli is now on swift core21:02
cschwedeHoorayy! Welcome Janie :D21:02
mattoliverau\o/21:02
nadeemcongrats jrichli!21:02
notmynamejrichli: congrats (and my apologies)21:02
*** baoli_ has quit IRC21:02
* bkeller` applause21:02
pdardeaujrichli: congrats!!21:02
jrichlilol21:02
dmoritaCongrats jrichli21:02
jrichlithanks!21:02
mathiasbcongratulations janie!21:02
kota_congratulations!21:02
*** lbrune has quit IRC21:02
hosanaijrichli: congrats!21:03
m_kazuhirocongratulations!21:03
*** joeljwright has joined #openstack-meeting21:03
*** baoli has joined #openstack-meeting21:03
notmynamejrichli's been doing great work, and I'm looking forward to working with her as a core reviewer21:03
*** salv-orlando has joined #openstack-meeting21:03
*** tonytan4ever has joined #openstack-meeting21:04
notmyname#topic barcelona schedule21:04
*** openstack changes topic to "barcelona schedule (Meeting topic: swift)"21:04
*** cdub has quit IRC21:04
notmynamebrief update on the schedule for barca21:04
notmynamelike in tokyo, this summint is slightly compressed. it's tuesday through friday21:04
notmynameon the design summit side, here's the overview21:04
notmynametuesday is ops stuff and some cross project stuff21:05
notmynamewednesday is cross project stuff and some individual team sessions21:05
notmynamethursday is individual team sessions21:05
*** Guest94509 has quit IRC21:05
notmynamefriday morning is individual team sessions, and friday afternoon is for the contributor meetup21:05
notmynameso that's a half-day on friday instead of the full day that's been available in the past21:06
mattoliverauk, yeah a little more compressed then21:07
notmynameI've submitted the schedule request to ttx. I asked for 2 fishbowl (like we had in austin) and 13 working sessions. I made a note that having fishbowl on wed pm and working sessions thursday and friday (plus the friday pm meetup) would be best for us21:07
notmynamebasically, this means plenty of ops and cross-project time and still a couple of days for swift-specific stuff21:07
notmynamealso, don't fly home on friday evening. wait until saturday ;-)21:07
notmynamemake sense to everyone? any questions about that?21:08
cschwedei think most people will leave Friday evening…21:08
notmynamecschwede: the cool kids will stay through saturday. you want to be a cool kid, right? ;-)21:08
*** tonytan4ever has quit IRC21:09
joeljwrightdammit, I'm flying home on Friday21:09
joeljwright:(21:09
cschwedenotmyname: i am the cool kid that is at a concert on Friday evening in Hamburg!21:09
notmynamelol21:09
hosanailol21:09
notmynamethat's much cooler than being in a hotel conference room21:09
notmynameseriously, though, people leaving on friday is totally normal and expected.21:09
cschwedewe need to work faster on teleporting.21:10
notmynamebut if you currently *don't* have concert tickets for friday night, then stay for swift stuff21:10
kota_cschwede: true21:10
notmynameas we get closer to the summit, we'll start an etherpad to gather topics, like we've done in the past21:10
notmynameno need to start that yet, though21:10
*** ayoung has quit IRC21:10
*** priteau has quit IRC21:11
notmynameok, if no questions, then let's move on21:11
notmyname#topic swiftclient release21:11
*** openstack changes topic to "swiftclient release (Meeting topic: swift)"21:11
notmynamewe need a release for swiftclient for 2 reasons21:11
notmyname1, there's good stuff we should make available to users21:12
notmyname2, getting close to the openstack library deadlines to be included in the overall release21:12
notmynamethere's one last patch that might land for it21:12
notmynamepatch 18495621:12
patchbothttps://review.openstack.org/#/c/184956/ - python-swiftclient - Accept gzip-encoded API responses21:12
notmynameand mattoliverau's going to look at that right after the meeting (he already have a +2 previously before a rebase)21:13
mattoliverauyup will look at that this morning.21:13
*** mickeys_ has quit IRC21:13
notmynameis there anything else that anyone knows of that really must be in this release?21:13
notmyname(docs are great, but can be landed after since we build docs at every commit now)21:13
*** mickeys has joined #openstack-meeting21:14
timburkenah, the other interesting stuff are probably better left for next cycle21:14
notmynametimburke: s/cycle/release/21:14
joeljwrightnotmyname: I think we managed to land everything that was ready21:14
notmynameok21:14
notmynameso that gets us to a segue topic..21:14
notmynameI've got https://review.openstack.org/#/c/361775/ up for the normal authors/changelog updates21:14
patchbotpatch 361775 - python-swiftclient - authors/changelog updates for 3.1.0 release21:14
notmynamebut there's one other thing there: reno release notes21:15
*** eezhova has quit IRC21:15
notmynameto summarize reno, it's a way to commit yaml files into your repo so that you get a release notes link on an openstack release web page21:15
notmynamesee https://releases.openstack.org for examples of other projects' notes https://releases.openstack.org21:16
notmynamewell, click through some stuff21:16
notmynamebut there's a little more to it than that21:16
torgomaticwhatever happened to plain text? release notes are for humans, so why embed that stuff in some markup?21:16
notmynametorgomatic: yeah...about that21:16
cschwedei like reno21:16
*** shashank_hegde has quit IRC21:17
notmynameus not having the reno yaml files in our repo is one of the things that some people on the TC complained about us not using21:17
*** shashank_hegde has joined #openstack-meeting21:17
cschwedetorgomatic: releasenotes are now able to contain semantic for stuff like „security“, „fixes“, „minor stuff“ etc21:17
notmynameso far, it seems relatively simple (apart for yaml having 63 different ways to format a multi-line string)21:17
notmynameand so that patch above simply takes the human-readable thing I normally write and reformats it into yaml21:18
*** rossella_s has quit IRC21:18
*** annegentle has quit IRC21:18
*** e0ne has quit IRC21:18
notmynamecschwede: yeah, and that's kinda nice.21:18
*** rossella_s has joined #openstack-meeting21:18
* torgomatic can't wait for the first security hole to be found in our release-notes builder21:19
cschwedenotmyname: the nice thing is that each patch can contain a reno note snippet, making it (hopefully) easier to sumup the final release note21:19
*** dprince has quit IRC21:19
cschwedenotmyname: so that should help you at the end - at least in theory ;)21:19
*** lblanchard has quit IRC21:19
notmynamecschwede: so I disagree with that. I'm the person that actually goes through the patches to build release notes, and I'll still have to do that21:19
*** e0ne has joined #openstack-meeting21:19
notmynamethere's often patches that need to be grouped into a single release note21:19
notmynameand I'll still have to look at patches that don't have notes on them21:20
notmynamebut I get the theory21:20
*** e0ne has quit IRC21:20
cschwedenotmyname: yes, but it can be really helpful if people contribute to the reno notes. but it will take some time to adopt (and reviewers might need to ask for a note)21:21
notmynamefor now, what I'm thinking is that at a release time I'll still go build release notes by hand (I enjoy this--it's not a chore) and then make the `reno report` match it21:21
*** spzala has quit IRC21:21
notmynamecschwede: so yeah, if people want to add a release note, that's fine. and if they don't, personally I'm ok with that too21:21
*** spzala has joined #openstack-meeting21:22
tdasilvai'm not sure that works out well...we should either have for every patch or not...21:22
notmynameI feel similarly to torgomatic on this. I want hand-curated notes because it's supposed to be read by humans. and I suspect that one person doing it at the end of a release will have better results than trying to make every patch also add a yaml file to our repo21:23
tdasilvai'm ok if notmyname wants to just build one note at the end, just the idea that some patches would have notes and others would not that doesn't seem like a good idea21:23
notmynametdasilva: why does it need to be black-and-white?21:23
notmynametdasilva: what if I simply delete the other yaml files and roll their contents into the one release notes note (like this swiftclient patch has)21:24
notmynametdasilva: then the notes in a file hint and what to include, and the final results end up being not a jumbled mess21:24
tdasilvanotmyname: i'm just afraid it will lead to confusion when some patches have reno notes and others dont21:25
bkeller`somehow i doubt "we can let people use reno if they want but we'll still ignore it" is what the tc wants us to do21:25
notmynamebkeller`: no, I'm not proposing ignoring anything21:25
notmynameclayg asked me an interesting question about this yesterday: would I even have considered using this if not for the TC criticism about it?21:25
cschwedeimo only patches that add a new feature, fix a bug etc need a reno note - ie something that should be mentioned in the final release note21:25
notmynameand yes, I would, because of its integration with the automated release tooling21:25
tdasilvabkeller`: i think the TC will get what they want which is the release notes being automatically created at release time21:26
*** spzala has quit IRC21:26
*** banix has joined #openstack-meeting21:26
notmynamecschwede: I guess I think (somewhat based on experience) that it's hard to always know at the time of a patch how its notes come release time relate to other patches that landed21:26
dhellmannhaving one person write all of the notes at the end of the cycle misses the point of building a culture around having all contributors think about how their changes impact users21:27
cschwedenotmyname: sure; but if i fix a typo that doesn’t need a reno; if i fix an important bug it could have a reno and lower the work for you at the end21:27
*** baumann has quit IRC21:28
notmynamebkeller`: but I think I get what you're trying to say. I don't want to use reno just to give some sort of lip-service. integrated with the automatic tooling is good--we should do as much of that as we can21:28
*** banix has quit IRC21:28
*** sdague has quit IRC21:28
bkeller`yeah21:28
notmynamecschwede: perhaps. well, it does to some extent21:28
*** banix has joined #openstack-meeting21:28
notmynamecschwede: but it doesn't eliminate it. that's my point21:29
notmynameI've still gotta review those and all the other patches too21:29
tdasilvacschwede, notmyname : sorry, just read my previous message and I meant "every patch" that makes sense to have a note, i agree not every single patch needs a note21:29
*** fzdarsky has quit IRC21:29
cschwedenotmyname: sure, there is still some work to do21:30
jrichliit might be interesting to have the point of view of a deployer.  do they appreciate the more cohesive summaries, and how would they feel about seeing a lot more verbage21:30
*** esumerfd has quit IRC21:30
notmynamejrichli: what do you mean? which one has "a lot more verbage"?21:30
*** zz_dimtruck is now known as dimtruck21:31
*** eezhova has joined #openstack-meeting21:31
jrichlimore verbage may result from having individuals all contribute over time21:31
patchbotError: I haven't seen verbage.21:31
jrichlithanks, patchbot21:31
tdasilvalol21:31
notmynamebah! patchbot is sick21:31
*** patchbot has left #openstack-meeting21:31
cschwedehaha ^^21:32
jrichlihaving notes from several commits : not having a way to group some together21:32
notmynamejrichli: perhaps. but the balance is highlighting the important stuff so that its not lost in lots of less important stuff21:32
*** clayg has joined #openstack-meeting21:32
notmynamejrichli: oh, I get it. that's actually what you're saying21:32
jrichliyes, that is what i am thinking too21:33
jrichli:-)21:33
* clayg sneaks in the back21:33
notmynamecschwede: I feel like you might not agree (or at least have a different perspective)21:33
*** CarolBarrett has joined #openstack-meeting21:34
cschwedenotmyname: well, it helped us in the last project, and the results were good - less work for the one who cutted a release21:34
bkeller`we could use the groups like cschwede was saying21:35
bkeller`unless i'm misunderstanding21:35
cschwedebut we only added reno notes when there was something worth to mention; for example the last patch in a chain of patches for feature XYZ21:35
*** annegentle has joined #openstack-meeting21:35
notmynamesure. like I said, if someone wants to add notes to a patch, that's fine21:35
notmynameit works with the release tooling, there's a link on a web page, and patch authors can add some extra notes if they want to their patch21:36
cschwedenotmyname: well, back to the topic, we can learn from the experience and improve the workflow over time? ie see what’s working for us as group and you as release cutter?21:37
notmynamecschwede: of course :-)21:37
*** sindhu has quit IRC21:37
*** sarob has quit IRC21:37
mattoliverauif its something that we do, it should be documented somewhere. ie. note naming standard etc.21:37
*** sarob has joined #openstack-meeting21:38
*** thorst has quit IRC21:38
mattoliverauor is it just patch sha and version each time21:38
*** rwsu has quit IRC21:38
notmynamemattoliverau: it's install reno then use `reno new` and edit the resulting file21:38
mattoliveraunotmyname: right, even easier :P21:38
*** rwsu has joined #openstack-meeting21:38
notmynameand `reno report` to look at the results (although note that the yaml file must be in the git DAG before being used--you can't just have a local scratch file that's uncommitted [`git commit -am WIP` will be common, I suspect]21:39
notmynameok, we need to move on :-)21:39
claygnotmyname: I don't recall asking you if you think this is something you'd want outside of it recently becoming a topic of contention - but I like that sentiment!21:40
notmynamereno's a thing. ta da!21:40
claygit *feels* like something I would say21:40
claygalso hooray!21:40
notmyname#topic liaisons21:40
*** openstack changes topic to "liaisons (Meeting topic: swift)"21:40
* clayg should have stayed in his hole21:40
joeljwrightclayg: go, I'll cover you21:40
claygNO MAN LEFT BEHIND!21:41
notmynameFYI, if someone is passionate about some of the things happening in other projects, take a look at https://wiki.openstack.org/wiki/CrossProjectLiaisons21:41
notmynameif there's not a name listed, it defaults to the PTL21:41
*** egallen has joined #openstack-meeting21:41
notmynameI'm not asking everyone to sign up for something--that's up to you (and I'm happy to continue being a point person as needed)21:41
*** kaminohana has joined #openstack-meeting21:41
notmynamebut I want to make sure people are aware of this way to get involved in other openstack efforts21:42
notmyname#topic plan for golang, post TC decision21:42
*** openstack changes topic to "plan for golang, post TC decision (Meeting topic: swift)"21:42
notmynameok, this will probably take the rest of our time today21:42
notmynamelast week I was in NYC and I talked fact-to-face with quite a few TC members21:43
notmynamehonestly, it would be very hard to summarize (especially in the next 15 minutes)21:43
notmynamebut from a very high level, there's lots of opinions :-)21:44
nadeem:)21:44
*** Hosam has quit IRC21:44
* clayg sorta had some thought on the cross-project stuff - we spent to much time talking about release notes formatting software/process :'(21:44
notmynamebut in this meeting, let's focus on some of the tech issues and actual user problems21:45
notmynamethere's a ton going on in swift by everyone21:45
notmynameand as we've been talking about for the last many months, the golang replication and object server is hugely important21:45
notmynameright now, we've got feature/repconn for the object replicator daemon work21:45
notmynameI'm expecting to see something there from nadeem very very soon so we can all dig into it21:46
*** dimtruck is now known as zz_dimtruck21:46
notmynamethe goal with repconn is to get the golang replacement for the python object replicator, initially focussed on the new repconn protocol21:46
notmynamefor now, work will continue in the feature branch21:47
*** lbrune has joined #openstack-meeting21:47
notmynamewe will not merge it to master and we will not move it to a separate repo yet21:47
notmynamebasically, let's not do something drastic until we actually have to (ie a release where a golang replicator is a thing)21:47
notmynamenadeem: what the status of the repconn work21:48
notmyname?21:48
*** cleong has quit IRC21:48
* notmyname knows he saw nadeem in here earlier...21:49
claygnotmyname: i was *going* to work on feature/hummingbird this week - but I barely got started before pulled onto something else21:49
nadeemI should have a PR ready either tonight or tomorrow morning21:49
mattoliveraumaybe he's getting his notes in order to paste :)21:49
notmynamenadeem: yay!21:50
claygbut i'm almost done with that!  so hope to get back at it by the end of thweek21:50
notmynameclayg: looks like nadeem has something for you to look at by then :-)21:50
claygnotmyname: yeah... it's going to be interesting to see how feature/hummingbird and feature/repconn evolve21:50
*** maeca1 has quit IRC21:50
notmynameindeed21:51
*** maeca1 has joined #openstack-meeting21:51
*** maeca1 has quit IRC21:51
nadeemhowever in this PR, I am only working on moving REPCONN call from object server to replicator21:51
notmynamenadeem: great starting point. that's what we talked about in san antonio21:51
claygbasically we've put nadeem in charge of putting together a vision for how swift will evlove to ingest hummingbird - we sorta narrowed scope for him - but it's got to be a huge chore21:51
*** esumerfd has joined #openstack-meeting21:51
nadeemcool21:51
notmynameclayg: that's for all of us to work on :-)21:51
claygi'm sorta surpised he hasn't had more questions like "well shit, how the f am i going to pull apart xyz - do ya'll have an opinon on option a vs b?"21:51
clayg... maybe it was less than I realized21:52
claygnotmyname: idk, depends on how big the patch is21:52
notmynamewe'll see in the morning21:52
*** zz_dimtruck is now known as dimtruck21:52
claygnadeem: do you expect your upcoming push to be... like "done" or is it toally just a starting point wip to start a conversation?21:52
nadeemWIP21:52
notmynameand for everyone, yes, you have permission to work on the golang object replicator in the repconn branch or the more general golang stuff in hummingbird21:52
claygnadeem: are we gunna need to like skype or something so you can highbandwidth drop some knowledge on us?21:52
nadeemmostly21:52
nadeembecause we haven't decided on how to split objectserver & replicator21:53
claygnadeem: oic21:53
claygnadeem: so you are going to push to feature/repconn on feature/hummingbird with just that change (move the REPCONN connection)21:53
nadeemwe can decide that after this initial PR21:54
nadeemright now to just feature/hummingbird21:54
claygnadeem: "that"?21:54
notmynamenadeem: oh?21:54
claygnadeem: ok, np, that makes sense21:54
notmynameI was under the assumption you were going to push to repconn21:54
nadeemonce we finalize on how to split the object server & replicator we can push it to repconn21:54
claygnotmyname: no that makes sense - get the feature/hummingbird (which works) in order closer to our target so we can start to think about what the real drop feature/repconn is going to look like21:55
notmynameok21:55
claygnotmyname: nadeem: I think this is correct (not that anyone asked me)21:55
*** esumerfd has quit IRC21:55
notmynameyeah, it makes sense21:55
claygnadeem: you should have clarified - you can just just drop in channel and be like "FYI i'm doing this" - *I* totally appreciate that21:55
nadeemsorry I should have clarified earlier21:56
nadeemanyhow will do that going forward21:56
claygnadeem: dood, no worries21:56
notmynamenadeem: I'm looking forward to seeing it :-)21:56
claygyeah for sure21:56
notmynameany other questions or issues to bring up on the golang work?21:56
nadeemdo we have a time frame for when Repconn will be mainstream?21:57
*** egallen has quit IRC21:57
notmynamenadeem: asap21:57
claygnadeem: I think realistically the newton release is off the table :'(21:57
notmynameusers are broken today without it21:58
claygbut that's just my pessemistic opinion21:58
notmynameback in austin, we were hoping that it would be done by barca21:58
nadeembut it will still be in feature branch...21:58
notmynamehowever the tc governance discussions kinda delayed that by several months21:58
claygright, i think we all got derailed and there's still some unknowns - not so much with technical feasability - but like just the merge and gate and upgrades - who knows21:58
pdardeaunotmyname: are you expecting it to be in separate repo?21:58
*** lbrune has quit IRC21:59
notmynamepdardeau: don't know yet21:59
*** hrybacki|afk is now known as hrybacki21:59
*** designbybeck has quit IRC21:59
notmynamenadeem: yeah, and as soon as it's a good replacement to the python one, we'll be at the decision point for where it lives21:59
claygpdardeau: right now it's a branch - can't make a choice about where to merge until it's ready to merge somehwere!21:59
pdardeauclayg: understood. just asking about plans21:59
*** mdenny has quit IRC22:00
claygpdardeau: FWIW, IMHO, merge to openstack/swift or openstack/swift-extra is a win either way - as long as we fix replication and continue to deliver ever improving cloud software to operators we're "doing it right"22:00
notmynamefocus on the users :-)22:00
claygthey don't care about python vs. golang - they don't care about git vs bzr or some other repo - they need better replication22:00
notmynameok, we're out of time22:00
notmynamethank you everyone for coming22:00
notmynamethank you for working on swift22:00
*** timur has left #openstack-meeting22:00
notmynameand thank you jrichli for your work and for stepping up to core22:01
nadeemhowever splitting stuff will take toll on swift community22:01
notmyname#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Wed Aug 31 22:01:08 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2016/swift.2016-08-31-21.00.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2016/swift.2016-08-31-21.00.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2016/swift.2016-08-31-21.00.log.html22:01
*** kota_ has left #openstack-meeting22:01
jrichliyou are welcome!22:01
*** hosanai has quit IRC22:01
*** joeljwright has left #openstack-meeting22:01
*** timburke has left #openstack-meeting22:01
*** torgomatic has left #openstack-meeting22:01
*** pdardeau has left #openstack-meeting22:01
*** jrichli has left #openstack-meeting22:02
*** m_kazuhiro has quit IRC22:02
*** shashank_hegde has quit IRC22:02
*** kaminoha_ has joined #openstack-meeting22:04
*** singhj has quit IRC22:05
*** kaminohana has quit IRC22:06
*** bobh_ has quit IRC22:06
*** esker has joined #openstack-meeting22:06
*** hashar has quit IRC22:08
*** spotz is now known as spotz_zzz22:09
*** spzala has joined #openstack-meeting22:10
*** singhj has joined #openstack-meeting22:10
*** dmorita has quit IRC22:11
*** sindhu has joined #openstack-meeting22:11
*** cutforth has quit IRC22:12
*** mriedem has quit IRC22:12
*** asettle has joined #openstack-meeting22:14
*** spzala has quit IRC22:15
*** piet has quit IRC22:15
*** spzala has joined #openstack-meeting22:15
*** singhj has quit IRC22:15
*** xyang1 has quit IRC22:15
*** eharney has quit IRC22:17
*** esberglu has quit IRC22:17
*** CarolBarrett has quit IRC22:18
*** esberglu has joined #openstack-meeting22:18
*** asettle has quit IRC22:19
*** dmorita has joined #openstack-meeting22:21
*** cardeois has quit IRC22:21
*** piet has joined #openstack-meeting22:21
*** banix has quit IRC22:22
*** ivc_ has quit IRC22:23
*** eezhova has quit IRC22:23
*** esberglu has quit IRC22:24
*** JRobinson__ has joined #openstack-meeting22:25
*** lpetrut has quit IRC22:26
*** Sukhdev has joined #openstack-meeting22:28
*** rooneym has quit IRC22:29
*** Leo_ has quit IRC22:29
*** annegent_ has joined #openstack-meeting22:30
*** banix has joined #openstack-meeting22:30
*** su_zhang has quit IRC22:32
*** annegentle has quit IRC22:33
*** Sukhdev has quit IRC22:34
*** sindhu has quit IRC22:36
*** piet has quit IRC22:37
*** shashank_hegde has joined #openstack-meeting22:37
*** hemna is now known as hemnafk22:40
*** efried has quit IRC22:40
*** esker has quit IRC22:45
*** Sukhdev has joined #openstack-meeting22:45
*** zhurong has joined #openstack-meeting22:47
*** mriedem has joined #openstack-meeting22:47
*** esumerfd has joined #openstack-meeting22:48
*** zhurong has quit IRC22:52
*** rbak has quit IRC22:52
*** esker has joined #openstack-meeting22:52
*** esumerfd has quit IRC22:52
*** jaypipes has quit IRC22:55
*** Sukhdev has quit IRC22:55
*** njohnsto_ has joined #openstack-meeting22:57
*** dtrainor has quit IRC22:58
*** njohnsto_ has quit IRC23:01
*** annegent_ has quit IRC23:01
*** njohnsto_ has joined #openstack-meeting23:02
*** saju_m has quit IRC23:02
*** pradk has quit IRC23:03
*** ronghui has quit IRC23:07
*** Benj_ has quit IRC23:09
*** dtrainor has joined #openstack-meeting23:09
*** edtubill has quit IRC23:10
*** tpsilva has quit IRC23:14
*** Julien-zte has joined #openstack-meeting23:19
*** sindhu has joined #openstack-meeting23:19
*** ronghui has joined #openstack-meeting23:19
*** njohnsto_ has quit IRC23:20
*** krtaylor has quit IRC23:22
*** maeca1 has joined #openstack-meeting23:23
*** gyee has quit IRC23:24
*** salv-orlando has quit IRC23:25
*** Julien-zte has quit IRC23:25
*** hockeynut has joined #openstack-meeting23:26
*** njohnsto_ has joined #openstack-meeting23:29
*** dtrainor has quit IRC23:31
*** krtaylor has joined #openstack-meeting23:34
*** njohnsto_ has quit IRC23:34
*** njohnsto_ has joined #openstack-meeting23:35
*** gongysh has joined #openstack-meeting23:37
*** Swami has quit IRC23:37
*** tochi has joined #openstack-meeting23:38
*** oomichi has quit IRC23:39
*** oomichi has joined #openstack-meeting23:39
*** oomichi has quit IRC23:40
*** gyee has joined #openstack-meeting23:41
*** Sukhdev has joined #openstack-meeting23:41
*** claudiub has quit IRC23:42
*** Sukhdev has quit IRC23:43
*** yuanying has quit IRC23:43
*** yuanying has joined #openstack-meeting23:44
*** dtrainor has joined #openstack-meeting23:44
*** oomichi has joined #openstack-meeting23:44
*** esker has quit IRC23:47
*** nadeem has quit IRC23:51
*** akamyshnikova has quit IRC23:52
*** akamyshnikova has joined #openstack-meeting23:52
*** fnaval has quit IRC23:53
*** donghao has joined #openstack-meeting23:54
*** ramineni_ has joined #openstack-meeting23:57
*** Suyi_ has quit IRC23:58
*** rwsu has quit IRC23:59

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