Thursday, 2015-06-18

*** amit213 has quit IRC00:00
*** amit213 has joined #openstack-meeting-300:00
*** shwetaap1 has quit IRC00:01
*** amit213 has quit IRC00:02
*** sdake has quit IRC00:02
*** amit213 has joined #openstack-meeting-300:03
*** amit213 has quit IRC00:09
*** amit213 has joined #openstack-meeting-300:09
*** amit213 has quit IRC00:15
*** amit213 has joined #openstack-meeting-300:16
*** amit213 has quit IRC00:22
*** amit213 has joined #openstack-meeting-300:22
*** yamamoto has quit IRC00:23
*** amit213 has quit IRC00:24
*** amit213 has joined #openstack-meeting-300:24
*** puranamr has joined #openstack-meeting-300:25
*** amit213 has quit IRC00:29
*** amit213 has joined #openstack-meeting-300:29
*** amit213 has quit IRC00:31
*** amit213 has joined #openstack-meeting-300:31
*** Longgeek has joined #openstack-meeting-300:32
*** clu_ has quit IRC00:35
*** amit213 has quit IRC00:38
*** amit213 has joined #openstack-meeting-300:38
*** kebray has quit IRC00:40
*** dims has joined #openstack-meeting-300:43
*** amit213 has quit IRC00:44
*** amit213 has joined #openstack-meeting-300:45
*** carl_baldwin has joined #openstack-meeting-300:49
*** pavel_bondar has quit IRC00:50
*** pavel_bondar has joined #openstack-meeting-300:50
*** amit213 has quit IRC00:50
*** amit213 has joined #openstack-meeting-300:51
*** ivar-lazzaro has quit IRC00:53
*** ivar-lazzaro has joined #openstack-meeting-300:54
*** ivar-lazzaro has quit IRC00:54
*** ivar-lazzaro has joined #openstack-meeting-300:55
*** amit213 has quit IRC00:57
*** amit213 has joined #openstack-meeting-300:57
*** hurgleburgler has quit IRC01:02
*** alexsyip has quit IRC01:02
*** amit213 has quit IRC01:04
*** amit213 has joined #openstack-meeting-301:04
*** Longgeek has quit IRC01:06
*** yamamoto has joined #openstack-meeting-301:08
*** amit213 has quit IRC01:10
*** amit213 has joined #openstack-meeting-301:10
*** banix has quit IRC01:14
*** amit213 has quit IRC01:16
*** amit213 has joined #openstack-meeting-301:16
*** shwetaap has joined #openstack-meeting-301:18
*** shwetaap1 has joined #openstack-meeting-301:19
*** carl_baldwin has quit IRC01:19
*** qwebirc58022 has joined #openstack-meeting-301:20
*** carl_baldwin has joined #openstack-meeting-301:21
*** qwebirc58022 has quit IRC01:21
*** puranamr has quit IRC01:21
*** shwetaap has quit IRC01:22
*** amit213 has quit IRC01:22
*** amit213 has joined #openstack-meeting-301:23
*** amit213 has quit IRC01:29
*** amit213 has joined #openstack-meeting-301:29
*** amit213 has quit IRC01:29
*** amit213 has joined #openstack-meeting-301:30
*** amit213 has quit IRC01:36
*** amit213 has joined #openstack-meeting-301:36
*** stanzgy has joined #openstack-meeting-301:38
*** s3wong has quit IRC01:46
*** asrangne has joined #openstack-meeting-301:46
*** banix has joined #openstack-meeting-301:47
*** asrangne__ has quit IRC01:49
*** amit213 has quit IRC01:49
*** amit213 has joined #openstack-meeting-301:50
*** asrangne has quit IRC01:51
*** ivar-lazzaro has quit IRC01:51
*** amit213 has quit IRC01:51
*** amit213 has joined #openstack-meeting-301:51
*** amit213 has quit IRC01:57
*** amit213 has joined #openstack-meeting-301:57
*** sbalukoff has quit IRC01:58
*** amit213 has quit IRC01:59
*** amit213 has joined #openstack-meeting-301:59
*** woodster_ has quit IRC02:01
*** nati_ueno has quit IRC02:01
*** nati_ueno has joined #openstack-meeting-302:01
*** amit213 has quit IRC02:01
*** amit213 has joined #openstack-meeting-302:02
*** carl_baldwin has quit IRC02:02
*** amit213 has quit IRC02:03
*** amit213 has joined #openstack-meeting-302:03
*** yuikotakada has joined #openstack-meeting-302:03
*** Networkn3rd has joined #openstack-meeting-302:04
*** Poornima has joined #openstack-meeting-302:06
*** bpokorny has quit IRC02:07
*** amit213 has quit IRC02:10
*** amit213 has joined #openstack-meeting-302:10
*** amit213 has quit IRC02:16
*** amit213 has joined #openstack-meeting-302:16
*** jckasper has joined #openstack-meeting-302:18
*** amit213 has quit IRC02:24
*** amit213 has joined #openstack-meeting-302:24
*** fallenpegasus has joined #openstack-meeting-302:26
*** rushiagr_away is now known as rushiagr02:29
*** amit213 has quit IRC02:30
*** amit213 has joined #openstack-meeting-302:30
*** jckasper has quit IRC02:31
*** amit213 has quit IRC02:31
*** amit213 has joined #openstack-meeting-302:31
*** dims has quit IRC02:32
*** dims has joined #openstack-meeting-302:33
*** jckasper has joined #openstack-meeting-302:34
*** fallenpegasus has quit IRC02:37
*** amit213 has quit IRC02:37
*** amit213 has joined #openstack-meeting-302:38
*** amit213 has quit IRC02:39
*** amit213 has joined #openstack-meeting-302:39
*** aswadr has joined #openstack-meeting-302:40
*** dims has quit IRC02:41
*** fallenpegasus has joined #openstack-meeting-302:41
*** amit213 has quit IRC02:45
*** amit213 has joined #openstack-meeting-302:45
*** Longgeek has joined #openstack-meeting-302:48
*** Piet has quit IRC02:49
*** amit213 has quit IRC02:51
*** amit213 has joined #openstack-meeting-302:51
*** amit213 has quit IRC02:51
*** amit213 has joined #openstack-meeting-302:52
*** amit213 has quit IRC02:53
*** amit213 has joined #openstack-meeting-302:53
*** shwetaap1 has quit IRC02:56
*** amit213 has quit IRC02:59
*** amit213 has joined #openstack-meeting-303:00
*** stevemar has joined #openstack-meeting-303:01
*** shwetaap has joined #openstack-meeting-303:03
*** shwetaap has quit IRC03:04
*** amit213 has quit IRC03:17
*** amit213 has joined #openstack-meeting-303:17
*** woodster_ has joined #openstack-meeting-303:18
*** Longgeek has quit IRC03:22
*** lazy_prince has joined #openstack-meeting-303:22
*** amit213 has quit IRC03:23
*** amit213 has joined #openstack-meeting-303:23
*** rushiagr is now known as rushiagr_away03:26
*** amit213 has quit IRC03:28
*** amit213 has joined #openstack-meeting-303:28
*** Networkn3rd has quit IRC03:29
*** amit213 has quit IRC03:34
*** amit213 has joined #openstack-meeting-303:34
*** davidmichaelkarr has quit IRC03:37
*** amit213 has quit IRC03:41
*** amit213 has joined #openstack-meeting-303:41
*** rushiagr_away is now known as rushiagr03:44
*** amit213 has quit IRC03:45
*** amit213 has joined #openstack-meeting-303:46
*** rushiagr is now known as rushiagr_away03:47
*** tobe has joined #openstack-meeting-303:49
*** amit213 has quit IRC03:51
*** amit213 has joined #openstack-meeting-303:51
*** davidmichaelkarr has joined #openstack-meeting-303:54
*** badveli has quit IRC03:55
*** sdake_ has quit IRC03:56
*** amit213 has quit IRC03:56
*** amit213 has joined #openstack-meeting-303:56
*** Poornima has quit IRC04:01
*** banix has quit IRC04:04
*** Poornima has joined #openstack-meeting-304:07
*** amit213 has quit IRC04:09
*** amit213 has joined #openstack-meeting-304:09
*** Longgeek has joined #openstack-meeting-304:19
*** amit213 has quit IRC04:25
*** amit213 has joined #openstack-meeting-304:25
*** irenab has quit IRC04:26
*** amit213 has quit IRC04:27
*** amit213 has joined #openstack-meeting-304:27
*** coolsvap|away is now known as coolsvap04:30
*** amit213 has quit IRC04:31
*** amit213 has joined #openstack-meeting-304:32
*** jckasper has quit IRC04:35
*** amit213 has quit IRC04:38
*** amit213 has joined #openstack-meeting-304:38
*** sdake_ has joined #openstack-meeting-304:41
*** zz_natorious is now known as natorious04:43
*** amit213 has quit IRC04:44
*** amit213 has joined #openstack-meeting-304:44
*** natorious is now known as zz_natorious04:48
*** amit213 has quit IRC04:50
*** amit213 has joined #openstack-meeting-304:51
*** Longgeek has quit IRC04:51
*** amit213 has quit IRC04:52
*** amit213 has joined #openstack-meeting-304:52
*** vinay_yadhav has joined #openstack-meeting-304:55
*** amit213 has quit IRC04:58
*** puranamr has joined #openstack-meeting-304:59
*** amit213 has joined #openstack-meeting-304:59
*** amit213 has quit IRC05:00
*** amit213 has joined #openstack-meeting-305:00
*** vinay_yadhav has quit IRC05:16
*** amit213 has quit IRC05:18
*** irenab has joined #openstack-meeting-305:18
*** amit213 has joined #openstack-meeting-305:18
*** Swami has joined #openstack-meeting-305:23
*** amit213 has quit IRC05:24
*** amit213 has joined #openstack-meeting-305:24
*** coolsvap is now known as coolsvap|away05:28
*** amit213 has quit IRC05:29
*** amit213 has joined #openstack-meeting-305:29
*** nkrinner has joined #openstack-meeting-305:30
*** amit213 has quit IRC05:35
*** amit213 has joined #openstack-meeting-305:35
*** coolsvap|away is now known as coolsvap05:36
*** amit213 has quit IRC05:39
*** amit213 has joined #openstack-meeting-305:39
*** sdake_ has quit IRC05:45
*** Longgeek has joined #openstack-meeting-305:48
*** amit213 has quit IRC05:52
*** amit213 has joined #openstack-meeting-305:52
*** belmoreira has joined #openstack-meeting-305:52
*** radek_ has joined #openstack-meeting-305:56
*** mrunge has joined #openstack-meeting-305:57
*** amit213 has quit IRC05:58
*** Swami has quit IRC05:58
*** amit213 has joined #openstack-meeting-305:58
*** davidmichaelkarr has quit IRC06:07
*** amit213 has quit IRC06:11
*** amit213 has joined #openstack-meeting-306:11
*** Longgeek has quit IRC06:14
*** amit213 has quit IRC06:17
*** amit213 has joined #openstack-meeting-306:17
*** amit213 has quit IRC06:19
*** amit213 has joined #openstack-meeting-306:19
*** amit213 has quit IRC06:25
*** amit213 has joined #openstack-meeting-306:25
*** belmoreira has quit IRC06:31
*** amit213 has quit IRC06:31
*** amit213 has joined #openstack-meeting-306:31
*** vinay_yadhav has joined #openstack-meeting-306:31
*** amit213 has quit IRC06:32
*** amit213 has joined #openstack-meeting-306:33
*** puranamr has quit IRC06:41
*** amit213 has quit IRC06:41
*** amit213 has joined #openstack-meeting-306:41
*** amit213 has quit IRC06:47
*** amit213 has joined #openstack-meeting-306:47
*** melwitt has quit IRC06:51
*** woodster_ has quit IRC06:51
*** sbalukoff has joined #openstack-meeting-306:52
*** armax has quit IRC06:53
*** coolsvap is now known as coolsvap|away06:53
*** amit213 has quit IRC06:54
*** amit213 has joined #openstack-meeting-306:54
*** amit213 has quit IRC06:55
*** amit213 has joined #openstack-meeting-306:56
*** melwitt has joined #openstack-meeting-306:57
*** ihrachyshka has joined #openstack-meeting-306:58
*** mpavlase has joined #openstack-meeting-306:59
*** coolsvap|away is now known as coolsvap07:01
*** amit213 has quit IRC07:01
*** stevemar has quit IRC07:02
*** amit213 has joined #openstack-meeting-307:02
*** zz_ttrifonov is now known as ttrifonov07:02
*** e0ne has joined #openstack-meeting-307:04
*** vinay_yadhav has quit IRC07:05
*** amit213 has quit IRC07:07
*** amit213 has joined #openstack-meeting-307:08
*** jcoufal has joined #openstack-meeting-307:09
*** wojdev has joined #openstack-meeting-307:10
*** lazy_prince has quit IRC07:10
*** amit213 has quit IRC07:13
*** amit213 has joined #openstack-meeting-307:14
*** Longgeek has joined #openstack-meeting-307:15
*** btully has quit IRC07:18
*** btully has joined #openstack-meeting-307:19
*** matrohon has joined #openstack-meeting-307:21
*** e0ne has quit IRC07:23
*** amit213 has quit IRC07:26
*** amit213 has joined #openstack-meeting-307:26
*** devvesa has joined #openstack-meeting-307:28
*** amit213 has quit IRC07:32
*** amit213 has joined #openstack-meeting-307:33
*** coolsvap is now known as coolsvap|away07:34
*** amit213 has quit IRC07:34
*** amit213 has joined #openstack-meeting-307:34
*** jlvillal has quit IRC07:37
*** salv-orl_ has quit IRC07:40
*** amit213 has quit IRC07:41
*** amit213 has joined #openstack-meeting-307:42
*** jrist has quit IRC07:44
*** jrist has joined #openstack-meeting-307:44
*** stendulker has joined #openstack-meeting-307:48
*** amit213 has quit IRC07:52
*** amit213 has joined #openstack-meeting-307:52
*** SotK has joined #openstack-meeting-307:53
*** jlvillal has joined #openstack-meeting-307:54
*** mickeys has joined #openstack-meeting-307:57
*** Longgeek has quit IRC08:04
*** Longgeek has joined #openstack-meeting-308:04
*** mickeys has quit IRC08:07
*** ihrachyshka has quit IRC08:09
*** amit213 has quit IRC08:10
*** amit213 has joined #openstack-meeting-308:10
*** amit213 has quit IRC08:16
*** amit213 has joined #openstack-meeting-308:17
*** safchain has joined #openstack-meeting-308:19
*** amit213 has quit IRC08:23
*** amit213 has joined #openstack-meeting-308:23
*** ramanjaneya has joined #openstack-meeting-308:34
ramanjaneyaHi08:34
*** yuikotakada is now known as yuikot_dinner08:40
*** yuikot_dinner has quit IRC08:40
*** pkarikh has quit IRC08:40
*** pkarikh has joined #openstack-meeting-308:41
*** jtomasek has joined #openstack-meeting-308:41
*** amit213 has quit IRC08:41
*** amit213 has joined #openstack-meeting-308:41
*** zhenguo has quit IRC08:44
*** dims has joined #openstack-meeting-308:44
*** amit213 has quit IRC08:47
*** e0ne has joined #openstack-meeting-308:48
*** amit213 has joined #openstack-meeting-308:48
*** dims has quit IRC08:48
*** amit213 has quit IRC08:49
*** amit213 has joined #openstack-meeting-308:49
*** amit213 has quit IRC08:55
*** amit213 has joined #openstack-meeting-308:55
*** e0ne is now known as e0ne_08:58
*** e0ne_ is now known as e0ne09:00
*** belmoreira has joined #openstack-meeting-309:02
*** coolsvap|away is now known as coolsvap09:02
*** amit213 has quit IRC09:06
*** amit213 has joined #openstack-meeting-309:06
*** amit213 has quit IRC09:12
*** amit213 has joined #openstack-meeting-309:12
*** VW has joined #openstack-meeting-309:17
*** amit213 has quit IRC09:30
*** amit213 has joined #openstack-meeting-309:30
*** amit213 has quit IRC09:37
*** amit213 has joined #openstack-meeting-309:37
*** amit213 has quit IRC09:43
*** amit213 has joined #openstack-meeting-309:44
*** yamamoto has quit IRC09:49
*** amit213 has quit IRC09:50
*** amit213 has joined #openstack-meeting-309:50
*** yamamoto has joined #openstack-meeting-309:50
*** e0ne is now known as e0ne_09:57
*** e0ne_ is now known as e0ne09:59
*** dims has joined #openstack-meeting-310:00
*** jcoufal has quit IRC10:02
*** amit213 has quit IRC10:03
*** amit213 has joined #openstack-meeting-310:04
*** yamamoto has quit IRC10:07
*** amit213 has quit IRC10:10
*** amit213 has joined #openstack-meeting-310:10
*** yamamoto has joined #openstack-meeting-310:11
*** Longgeek_ has joined #openstack-meeting-310:20
*** Poornima has quit IRC10:21
*** Longgeek has quit IRC10:23
*** amit213 has quit IRC10:23
*** amit213 has joined #openstack-meeting-310:24
*** salv-orlando has joined #openstack-meeting-310:26
*** salv-orl_ has joined #openstack-meeting-310:29
*** amit213 has quit IRC10:30
*** amit213 has joined #openstack-meeting-310:30
*** salv-orlando has quit IRC10:31
*** amit213 has quit IRC10:32
*** amit213 has joined #openstack-meeting-310:32
*** amit213 has quit IRC10:33
*** amit213 has joined #openstack-meeting-310:34
*** rhagarty_ has quit IRC10:34
*** tobe has quit IRC10:34
*** rhagarty_ has joined #openstack-meeting-310:35
*** amit213 has quit IRC10:36
*** amit213 has joined #openstack-meeting-310:36
*** amit213 has quit IRC10:37
*** amit213 has joined #openstack-meeting-310:38
*** tobe has joined #openstack-meeting-310:40
*** rhagarty_ has quit IRC10:44
*** amit213 has quit IRC10:44
*** rhagarty_ has joined #openstack-meeting-310:44
*** amit213 has joined #openstack-meeting-310:44
*** stanzgy has quit IRC10:50
*** e0ne is now known as e0ne_10:50
*** amit213 has quit IRC10:51
*** amit213 has joined #openstack-meeting-310:51
*** wojdev has quit IRC10:55
*** coolsvap is now known as coolsvap|away10:56
*** amit213 has quit IRC10:57
*** amit213 has joined #openstack-meeting-310:57
*** e0ne_ has quit IRC11:00
*** btully has quit IRC11:00
*** sahid has joined #openstack-meeting-311:01
*** egallen has quit IRC11:01
*** btully has joined #openstack-meeting-311:02
*** amit213 has quit IRC11:03
*** amit213 has joined #openstack-meeting-311:04
*** amit213 has quit IRC11:05
*** amit213 has joined #openstack-meeting-311:06
*** beagles|afk is now known as beagles11:09
*** beagles is now known as b3nt_pin11:09
*** tobe has quit IRC11:09
*** b3nt_pin is now known as beagles11:09
*** stendulker has quit IRC11:09
*** mwagner_afk has quit IRC11:10
*** tobe has joined #openstack-meeting-311:11
*** amit213 has quit IRC11:12
*** amit213 has joined #openstack-meeting-311:12
*** amit213 has quit IRC11:18
*** amit213 has joined #openstack-meeting-311:19
*** asrangne has joined #openstack-meeting-311:19
*** asrangne__ has joined #openstack-meeting-311:20
*** aswadr has quit IRC11:21
*** amit213 has quit IRC11:21
*** amit213 has joined #openstack-meeting-311:21
*** devvesa has quit IRC11:21
*** VW has quit IRC11:23
*** asrangne has quit IRC11:24
*** tobe has quit IRC11:25
*** sdake has joined #openstack-meeting-311:27
*** amit213 has quit IRC11:27
*** amit213 has joined #openstack-meeting-311:27
*** egallen has joined #openstack-meeting-311:28
*** jlvillal has quit IRC11:30
*** wojdev has joined #openstack-meeting-311:30
*** jlvillal has joined #openstack-meeting-311:31
*** amotoki_ has joined #openstack-meeting-311:33
*** amit213 has quit IRC11:34
*** amit213 has joined #openstack-meeting-311:34
*** e0ne has joined #openstack-meeting-311:36
*** amit213 has quit IRC11:40
*** amit213 has joined #openstack-meeting-311:40
*** amit213 has quit IRC11:47
*** amit213 has joined #openstack-meeting-311:47
*** btully has quit IRC11:54
*** baoli has joined #openstack-meeting-311:54
*** btully has joined #openstack-meeting-311:55
*** jrist has quit IRC11:56
*** jrist has joined #openstack-meeting-311:56
*** rushiagr_away is now known as rushiagr11:58
*** amit213 has quit IRC11:58
*** amit213 has joined #openstack-meeting-311:59
*** matrohon has quit IRC11:59
*** amit213 has quit IRC12:00
*** amit213 has joined #openstack-meeting-312:01
*** amit213 has quit IRC12:07
*** amit213 has joined #openstack-meeting-312:07
*** salv-orl_ has quit IRC12:11
*** amit213 has quit IRC12:13
*** amit213 has joined #openstack-meeting-312:14
*** bknudson has joined #openstack-meeting-312:20
*** amit213 has quit IRC12:20
*** amit213 has joined #openstack-meeting-312:21
*** amit213 has quit IRC12:22
*** amit213 has joined #openstack-meeting-312:22
*** btully has quit IRC12:22
*** yamamoto has quit IRC12:23
*** amit213 has quit IRC12:24
*** amit213 has joined #openstack-meeting-312:24
*** btully has joined #openstack-meeting-312:25
*** bknudson has quit IRC12:26
*** puranamr has joined #openstack-meeting-312:28
*** ajmiller has quit IRC12:28
*** ramanjaneya has quit IRC12:29
*** amit213 has quit IRC12:30
*** amit213 has joined #openstack-meeting-312:30
*** e0ne is now known as e0ne_12:32
*** matrohon has joined #openstack-meeting-312:34
*** puranamr has quit IRC12:35
*** radek_ has quit IRC12:36
*** amit213 has quit IRC12:36
*** radek_ has joined #openstack-meeting-312:37
*** amit213 has joined #openstack-meeting-312:37
*** e0ne_ is now known as e0ne12:39
*** dims has quit IRC12:40
*** dims has joined #openstack-meeting-312:41
*** bknudson has joined #openstack-meeting-312:43
*** amit213 has quit IRC12:43
*** amit213 has joined #openstack-meeting-312:43
*** rushiagr is now known as rushiagr_away12:44
*** amit213 has quit IRC12:45
*** amit213 has joined #openstack-meeting-312:45
*** woodster_ has joined #openstack-meeting-312:45
*** amit213 has quit IRC12:51
*** amit213 has joined #openstack-meeting-312:52
*** puranamr has joined #openstack-meeting-312:53
*** amit213 has quit IRC12:58
*** amit213 has joined #openstack-meeting-312:58
*** amit213 has quit IRC13:02
*** amit213 has joined #openstack-meeting-313:03
*** julim has joined #openstack-meeting-313:03
*** salv-orlando has joined #openstack-meeting-313:07
*** doug-fish has joined #openstack-meeting-313:09
*** amit213 has quit IRC13:09
*** amit213 has joined #openstack-meeting-313:09
*** salv-orl_ has joined #openstack-meeting-313:12
*** salv-orlando has quit IRC13:15
*** amit213 has quit IRC13:15
*** amit213 has joined #openstack-meeting-313:16
*** VW has joined #openstack-meeting-313:17
*** puranamr has quit IRC13:19
*** amit213 has quit IRC13:22
*** amit213 has joined #openstack-meeting-313:22
*** amit213 has quit IRC13:22
*** amit213 has joined #openstack-meeting-313:23
*** yamamoto has joined #openstack-meeting-313:24
*** irenab has quit IRC13:25
*** jckasper has joined #openstack-meeting-313:26
*** amit213 has quit IRC13:29
*** amit213 has joined #openstack-meeting-313:29
*** yamamoto has quit IRC13:29
*** belmoreira has quit IRC13:30
*** amit213 has quit IRC13:30
*** amit213 has joined #openstack-meeting-313:31
*** tellesnobrega has joined #openstack-meeting-313:32
*** fallenpegasus has quit IRC13:34
*** singlethink has joined #openstack-meeting-313:36
*** amit213 has quit IRC13:37
*** mwagner_afk has joined #openstack-meeting-313:37
*** amit213 has joined #openstack-meeting-313:37
*** peristeri has joined #openstack-meeting-313:38
*** puranamr has joined #openstack-meeting-313:40
*** tmckay has joined #openstack-meeting-313:41
*** jckasper has quit IRC13:41
*** lblanchard has joined #openstack-meeting-313:42
*** amit213 has quit IRC13:43
*** elmiko has joined #openstack-meeting-313:43
*** amit213 has joined #openstack-meeting-313:43
*** puranamr has quit IRC13:45
*** wojdev has quit IRC13:45
*** singleth_ has joined #openstack-meeting-313:45
*** amit213 has quit IRC13:45
*** amit213 has joined #openstack-meeting-313:45
*** puranamr has joined #openstack-meeting-313:46
*** carl_baldwin has joined #openstack-meeting-313:48
*** singlethink has quit IRC13:48
*** vgridnev has joined #openstack-meeting-313:49
*** egallen has quit IRC13:50
*** amit213 has quit IRC13:51
*** amit213 has joined #openstack-meeting-313:52
*** pino|work has joined #openstack-meeting-313:54
*** shwetaap has joined #openstack-meeting-313:55
*** sigmavirus24_awa is now known as sigmavirus2413:57
*** esikachev has joined #openstack-meeting-313:57
*** kchen has joined #openstack-meeting-313:59
*** amit213 has quit IRC13:59
*** hdd has joined #openstack-meeting-314:00
*** amit213 has joined #openstack-meeting-314:00
SergeyLukjanovhey sahara folks14:00
vgridnevhi14:01
esikachevhi!14:01
NikitaKonovalovo/14:01
kcheno/14:01
*** tosky has joined #openstack-meeting-314:01
tmckayhola14:01
elmikoyo/14:01
SergeyLukjanov#startmeeting sahara14:01
openstackMeeting started Thu Jun 18 14:01:19 2015 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: sahara)"14:01
openstackThe meeting name has been set to 'sahara'14:01
alazarevo/14:01
SergeyLukjanov#topic sahara@horizon status (crobertsrh, NikitaKonovalov)14:01
*** openstack changes topic to "sahara@horizon status (crobertsrh, NikitaKonovalov) (Meeting topic: sahara)"14:01
SergeyLukjanov#link https://etherpad.openstack.org/p/sahara-reviews-in-horizon14:01
NikitaKonovalovI've no updates here since I've been focused on other things14:02
NikitaKonovalovBut I guess not much has changed form the last meeting14:02
*** crobertsrh has joined #openstack-meeting-314:02
*** amit213 has quit IRC14:02
vgridnevEvent log change still on review, that is sad14:02
SergeyLukjanovNikitaKonovalov, do you probably know anything about moving sahara dashboard to contrib dir in horizon?14:02
*** amit213 has joined #openstack-meeting-314:02
elmikovgridnev: =(14:03
crobertsrhTemplate editing changes still on review == sadd14:03
crobertsrhI haven't added any new UI patches recently, been working more on service side of things.14:03
NikitaKonovalovSergeyLukjanov: haven't seen any movement there14:03
*** egallen has joined #openstack-meeting-314:03
alazarevNikitaKonovalov, any movements in other projects?14:03
*** yamamoto has joined #openstack-meeting-314:04
*** banix has joined #openstack-meeting-314:04
NikitaKonovalovlooks like no14:04
SergeyLukjanovsahara was just enabled for horizon integration tests https://review.openstack.org/#/c/192645/14:05
*** amit213 has quit IRC14:05
*** amit213 has joined #openstack-meeting-314:05
toskyoh, merged, nice; I missed the commit message14:05
NikitaKonovalovSergeyLukjanov: does that mean that we can have fake plugin tests14:06
tosky(another review will reenable the horizon integration tests as voting)14:06
SergeyLukjanovNikitaKonovalov, hm, I think so14:06
NikitaKonovalovI mean make UI create a cluster with a fake plugins an check that all panels, configs, etc are in place14:06
toskyNikitaKonovalov: I though Horizon integration tests are for full deployment14:07
SergeyLukjanovNikitaKonovalov, tosky I think it should be possible now14:07
kchenWe have registered a bp to integrate manila and sahara in https://blueprints.launchpad.net/sahara/+spec/edp-manila-hdfs. We are working on the spec.14:07
SergeyLukjanovhttps://github.com/openstack/horizon/blob/master/openstack_dashboard/test/integration_tests/tests/test_sahara_job_binaries.py14:07
*** puranamr has quit IRC14:08
kchenHope we can have a spec by the next week14:08
*** yamamoto has quit IRC14:08
tmckaykchen, excellent14:08
NikitaKonovalovjob_binaries are quite standard == easy to test14:08
NikitaKonovalovclusters should be more interesting14:09
*** btully has quit IRC14:09
*** banix has quit IRC14:09
SergeyLukjanovNikitaKonovalov, yeah, but seems like no difference if we have full devstack install14:09
SergeyLukjanovanything else re sahara@horizon?14:10
crobertsrhnothing I can think of14:10
NikitaKonovalovnothing from me14:10
SergeyLukjanovso, let's move on14:10
SergeyLukjanovthx folks14:10
SergeyLukjanov#topic News / updates14:10
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:10
*** btully has joined #openstack-meeting-314:10
*** huichun has joined #openstack-meeting-314:11
NikitaKonovalovI've been working on refactoring of sahara.utils module. There are too many things now some of which are required by provisioning plugins and some not14:11
*** amit213 has quit IRC14:11
elmikoi was out part of last week and at spark summit this week. i have talked with apavlov about the keystone sessions, i think we are close to a spec for that. also i've been investigating using gabbi to fuzz test a live sahara server. also, lots of cool stuff at spark summit, i think we need to improve our spark support =)14:11
*** amit213 has joined #openstack-meeting-314:12
vgridnevFinished work with recommendations provider, really need for review some my changes14:12
crobertsrhI've been doing a little experimental work getting a Spark 1.3 cluster up and running the Zeppelin notebook stuff on top of the cluster.  Looks promising so far.14:12
vgridnev#link https://review.openstack.org/#/q/owner:%22Vitaly+Gridnev%22+status:open,n,z14:12
sreshetnyakI'm working on HDP 2.2 plugin14:12
NikitaKonovalovSo the idea is to move the code from utils to where it's actually needed so the sahara-plugins split will be easier14:12
*** yamahata has joined #openstack-meeting-314:12
SergeyLukjanovNikitaKonovalov, at least in theory, if we'll agree to do it :)14:13
esikachevi'm working on custom scenarios14:13
*** stevemar has joined #openstack-meeting-314:13
tmckayreviewing/testing egafford's job interface mapping, I think it's almost ready for a +2 from me14:13
huichunworking on scheduler and recurrence edp job14:13
tmckaylooks good14:13
alazarevI'm trying to test hadoop performance with disks attached directly to VM via cinder driver14:13
*** btully has quit IRC14:15
*** banix has joined #openstack-meeting-314:15
SergeyLukjanovsounds like time to move on14:15
SergeyLukjanov#topic Liberty-114:16
*** openstack changes topic to "Liberty-1 (Meeting topic: sahara)"14:16
tmckaymaybe for open topics, but I think someone needs to work on hdp plugin ci tests (if not already) or we should move them to non-voting for now.  They break too often, and HWX is not here to fix them :)14:16
*** puranamr has joined #openstack-meeting-314:16
SergeyLukjanovso, we have a liberty-1 next week14:16
SergeyLukjanovtmckay, esikachev working on CI failures now14:16
tmckayyay!  thanks14:16
SergeyLukjanov#info Liberty-1 next14:17
*** btully has joined #openstack-meeting-314:17
*** nkrinner has quit IRC14:17
SergeyLukjanov#undo14:17
openstackRemoving item from minutes: <ircmeeting.items.Info object at 0x9c87690>14:17
SergeyLukjanov#info Liberty-1 next week (Jun 23-25)14:17
SergeyLukjanov#link https://wiki.openstack.org/wiki/Liberty_Release_Schedule14:17
SergeyLukjanov#info Liberty release tag for sahara will be 3.0.014:18
elmikoneat14:18
SergeyLukjanovso, Liberty-1 is 3.0.0b114:18
*** amit213 has quit IRC14:18
SergeyLukjanovthe Sahara changes was applyed already in I6a35fa0dda798fad93b804d00a46af80f08d475c14:18
SergeyLukjanovand I'm now working on doing the same for the rest repos14:18
*** amit213 has joined #openstack-meeting-314:18
*** yamamoto has joined #openstack-meeting-314:19
SergeyLukjanovso, note that epoch should be increased :)14:19
SergeyLukjanovany questions about it?14:19
SergeyLukjanov#topic Next client releases14:20
*** openstack changes topic to "Next client releases (Meeting topic: sahara)"14:20
SergeyLukjanovI'd like all of you to think about all potential changes to client that should be done in Liberty14:20
SergeyLukjanovespeccially new features addition14:21
SergeyLukjanovand I'd like to make a release schedule for the client14:21
alazarevSergeyLukjanov, why do we need release schedule for it?14:21
*** egafford has joined #openstack-meeting-314:21
alazarevSergeyLukjanov, usually it is shipped when needed14:21
SergeyLukjanovnote: we should have final "feature" release of client by liberty-314:22
crobertsrhI have at least 2 client changes that will be needed, for editing data sources and job binaries.14:22
SergeyLukjanovalazarev, it's needed for us14:22
vgridnevat least one change with auto-configuration parameter to client14:22
tellesnobregai would like to add storm job submission on the client14:22
tmckayI have one tiny one that tosky noted.  default templates should be marked somehow in the template list output14:22
SergeyLukjanovthere are two main issues I'd like to solve by listing needed client features - not miss any of them in official Liberty client and decrease latency of releasing new features14:22
tellesnobregaand also if multiple clusters creation enters I would have to implement on the client as well (if we use a new api call)14:23
egaffordInterface field on both job and job template need to get into the client as well.14:23
elmikoSergeyLukjanov: +114:23
SergeyLukjanovtellesnobrega, will it be different comparing to the other jobs?14:23
tellesnobregano14:23
*** Piet has joined #openstack-meeting-314:23
tellesnobregai have to take a look to see if any changes are needed14:24
tmckaysounds like we need an etherpad for this (did I miss one above?)14:24
*** btully has quit IRC14:24
alazarevtmckay, +114:25
SergeyLukjanovhttps://etherpad.openstack.org/p/sahara-liberty-client14:25
tmckayyay!  good work SergeyLukjanov.  Fast too :)14:25
*** btully has joined #openstack-meeting-314:25
SergeyLukjanovPlease, add links to the specs / CRs, put your name to have a contact, if you have an idea, when the patch will be ready, put the date as well.14:26
elmiko#link https://etherpad.openstack.org/p/sahara-liberty-client14:26
elmikojust for the logs =)14:26
SergeyLukjanovtmckay, I've been creating it in time when you write the idea :)14:26
SergeyLukjanovelmiko, thx14:26
tmckayparallel, excellent14:26
SergeyLukjanovtmckay, yeah, like a hadoop :)14:27
*** amit213 has quit IRC14:27
SergeyLukjanovso, it'll help a lot to plan client release and merge all of the stuff in time14:27
tmckayWe Are a Cluster14:27
*** amit213 has joined #openstack-meeting-314:27
tellesnobrega+114:27
SergeyLukjanovyay!14:27
SergeyLukjanovI'll write a follow-up to mailing list as well14:27
*** hdd has quit IRC14:28
tmckayall, make sure you actually create the bug/spec/bp if you put ( words ) on the etherpad!14:28
tmckayI'll do mine today14:28
SergeyLukjanovrandom idea: do we probably want to make a saharaclient-core group with all sahara-cores plus someone else?14:28
elmikoSergeyLukjanov: is it a different group in gerrit?14:29
tmckayhmmm, do other projects do this?14:29
SergeyLukjanovtmckay, swift already doing it14:29
crobertsrhMy first instinct is that It seems like it might be overkill14:29
SergeyLukjanovtmckay, probably someone else14:29
SergeyLukjanovcrobertsrh, ++14:29
elmikoyea, kinda agree with crobertsrh14:29
tmckaywhat about combined client? will python-saharaclient go away eventually?14:29
SergeyLukjanovbut it could be helpful if will have someone very active in client14:29
SergeyLukjanovnot the case right now14:30
toskytmckay: the CLI client could go away, but not the library14:30
tmckayI think we only have a few client changes per cycle, not too bad14:30
tmckaygotcha14:30
SergeyLukjanovtmckay, its python part still needed, it's only about combined CLI14:30
egaffordAgreed that it seems like overkill.14:30
tmckayso I hear -114:30
tosky("client" is a bit overloaded word in OpenStack, unfortunately)14:30
*** yamahata has quit IRC14:30
SergeyLukjanovyeah14:30
*** hdd has joined #openstack-meeting-314:30
SergeyLukjanov#agreed no need for the separate saharaclient core group14:31
tmckaycrobertsrh, btw, I was going to jam through those spec approvals today14:31
tmckayeveryone has had more than enough time to comment :)14:31
crobertsrhgreat14:31
tmckayif someone has a big issue, they can re-open as a CR14:31
*** btully has quit IRC14:32
SergeyLukjanov#topic Hadoop 1 drop14:32
*** openstack changes topic to "Hadoop 1 drop (Meeting topic: sahara)"14:32
SergeyLukjanovI'd like to chat about it again14:32
tmckaypoor hadoop 114:32
toskyquestion: vanilla is the first, and then it will be for all other plugins, or is it up to each plugin "maintainer"?14:32
SergeyLukjanovthere were no requests for the hadoop 1 for the whole sahara life (even when it was savanna, eho, etc)14:33
SergeyLukjanovtosky, HDP plugin is now maintained by community14:33
SergeyLukjanovdue to the lack of HWX support14:33
huichunso we won't support hadoop1?14:33
*** ajmiller has joined #openstack-meeting-314:33
SergeyLukjanovhuichun, do you need it? :)14:33
huichunneed not14:33
*** amit213 has quit IRC14:34
*** btully has joined #openstack-meeting-314:34
*** amit213 has joined #openstack-meeting-314:34
SergeyLukjanovmy reasoning for it - not to support the obsolete thing, it requires CIs, images, etc.14:34
SergeyLukjanovbut noone asking for it14:34
elmiko+114:35
*** iben has joined #openstack-meeting-314:35
egaffordSergeyLukjanov: HDP1 has been a repeat offender in terms of failing all the CI jobs, as well.14:35
tmckayso do we need a deprecation cycle?14:35
toskySergeyLukjanov: is also Mapr 3.1.1 based on Hadoop 2?14:35
tmckaydeprecated for L, removed in "M"onster14:35
tellesnobrega+114:36
SergeyLukjanovtmckay, probably not for the Hadoop 114:36
SergeyLukjanovnot sure that we should keep them while noone using them14:36
elmikoyea, makes no sense to keep it if there have been no requests for it.14:36
tellesnobregaeven apache has lost a bit of interest in hadoop 114:36
tmckaytruth is, plugin SPI is relatively stable, wouldn't be hard for someone to maintain out-of-tree if they really wanted to14:36
SergeyLukjanovtellesnobrega, correct14:37
egaffordtmckay: From a customer perspective, everyone's on 2. For enthusiasts, less sure; there could be someone out there running Hadoop 1 on Sahara in his/her basement who'd be very angry at us.14:37
SergeyLukjanovtmckay, if we'll be going to extract plugins, it'll be additional work14:37
elmikoegafford: lol14:37
*** davidmichaelkarr has joined #openstack-meeting-314:37
tmckayegafford, they always have Kiko14:37
*** e0ne is now known as e0ne_14:37
*** e0ne_ is now known as e0ne14:37
SergeyLukjanovplus sreshetnyak is now working on the HDP plugin rework and we'll be able to drop current HDP plugin as well14:37
tmckayack.  I have no problem with it14:37
*** puranamr has quit IRC14:38
SergeyLukjanovand Liberty will be shipped to customers like early next year, so, I think it's pretty safe :)14:38
SergeyLukjanovNikitaKonovalov, have you already created Hadoop 1 drop spec?14:38
NikitaKonovalovyes14:38
tmckayplus it makes the gate faster ++14:38
SergeyLukjanovtmckay, exactly!14:39
NikitaKonovalov#link https://review.openstack.org/#/c/192563/14:39
SergeyLukjanovgreat14:39
SergeyLukjanovso, we could discuss it offline in spec14:39
SergeyLukjanovit sounds like we have partial agreement on dropping hadoop 114:39
SergeyLukjanovat least no users here ;)14:40
*** egallen has quit IRC14:40
tmckaywe can always send an email about it to openstack-dev and see if anyone screams14:40
tmckayLike a doctor saying "Does this hurt?"14:40
SergeyLukjanovtmckay, yeah14:40
SergeyLukjanov#topic Open discussion14:40
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:40
tmckaythen we can prescribe Hadoop 2 as the cure14:40
*** amit213 has quit IRC14:40
elmikohas anyone talked with the cognitive team?14:41
*** amit213 has joined #openstack-meeting-314:41
elmikoto find out what it is they are putting together?14:41
tmckaygood question.  channel is kind of quiet14:41
tmckay(by kind of, I mean totally)14:41
*** fallenpegasus has joined #openstack-meeting-314:41
toskyoh, I have a question about unit tests14:41
toskyquick copy&paste coming :)14:41
toskywe have a global dependency on testtools>=0.9.6, but some unit test implicitely depends on newer versions14:41
toskyfor example, I've seen usage of assertRegex which works only with testtools>=1.2 (thanks to unittest2); and other stuff like that14:42
toskyshould we consider these usages as wrong and file bugs for them? Otherwise the global requirements have no meanings14:42
toskyIt's not a problem on the gates because they test only the last version of deps (so testtools 1.8)14:42
tellesnobregai have a question about the multiple clusters spec. sreshetnyak talked to me this week suggesting that i created a new api call, clusters/multiple, this way we keep compatibility and we dont to wait until API v2 to have this feature in14:43
tmckaytosky, so shouldn't the global dep be moved past 0.9.6, if the gates use 1.8?14:43
tellesnobregasorry tosky, kinda broke the thought there14:43
toskytmckay: that's the other possibility, but I'm not sure how it works in that case14:44
toskytmckay: maybe there are requirements from distributions; ubuntu has 0.9.6, we ship 1.1...14:44
toskyI have no idea14:44
tmckayI see14:44
elmikotosky: maybe talk with the infra team to learn a little more about global reqs and why it's at 0.9.6?14:44
elmikootherwise, yea bugs would be good14:45
toskyit would be worth to check, but maybe SergeyLukjanov knows something with his infra hat14:45
toskyor at least, who can we talk about for this?14:45
tmckaytosky, well, technically, it's not bounded.  It doesn't say >= 0.9.6, < XXXX14:45
tmckayso, it's not really a bug per se.  I see your point, though14:45
toskytmckay: it is a bug, IMHO; it's not working with a supported version14:46
tmckayI think we need to fix the global req.  bump it up, or bound it, or everything is okay14:46
elmikoguess it depends how each distro satisfies those reqs14:46
toskyso either you raise the dependency or you fix the code14:46
elmikotosky: +114:46
tmckayyeah, I think investigate moving the version in the global req, and if it can't be moved, then bound it, and find bugs14:47
SergeyLukjanovoops, I'm return back :)14:47
*** amit213 has quit IRC14:47
pino|work(imho the global requirements.txt that everybody must take is a sort of annoyance)14:47
*** amit213 has joined #openstack-meeting-314:47
tmckaySergeyLukjanov, lots of talk about infra stuff ^^14:48
elmikopino|work: necessary evil i suppose ;)14:48
SergeyLukjanovtosky, IMO it's good to bump testtools version14:48
SergeyLukjanovtosky, there were the same input from heat team14:48
toskySergeyLukjanov: yep, they have a similar issues in their unit tests14:48
vgridnevthere are already one bump patch for testtools14:48
vgridnevhttps://review.openstack.org/#/c/192574/14:48
toskythat's what my grep says :)14:48
toskyoh, from yesterday14:49
SergeyLukjanovin fact, we should be able to work on a min version14:49
toskyif the dependency is raised, will this be backported to kilo?14:49
toskybecause also kilo is affected14:49
SergeyLukjanovbut, the specific solution for it now is better to bump min version14:49
*** amit213 has quit IRC14:49
elmikoif we can bump, that seems like the ideal14:49
*** amit213 has joined #openstack-meeting-314:49
SergeyLukjanovlet's review and +1/2 https://review.openstack.org/#/c/192574/14:50
elmikosounds good14:50
*** amit213 has quit IRC14:50
*** john-davidge has joined #openstack-meeting-314:50
*** zz_jgrimm is now known as jgrimm14:51
*** amit213 has joined #openstack-meeting-314:51
elmikotellesnobrega: i think adding new endpoints to v1.1 is fine with regards to v2. v2 will be more about improving the api and perhaps breaking some bad patterns from the past.14:51
tellesnobregasure14:51
tellesnobregaanyone opposes to that?14:51
SergeyLukjanovelmiko, ++14:51
tellesnobregai'm going to rewrite the spec detailing that i'm going to add a new call to the API14:52
tellesnobregaalso going to write the spec for the saharaclient14:52
elmikotellesnobrega: sounds good14:53
elmikoSergeyLukjanov: have you talked with the cognitive team at all? (i'm curious what kind of overlap we might have with them)14:53
SergeyLukjanovelmiko, (trying to remember what is cognitive)14:53
elmikoMLaaS14:54
elmikoi'm wondering if they are going to deploy spark or something14:54
tmckay(mailing lists as a service)14:54
elmikolol14:54
tellesnobregatmckay, thats what i read14:54
tellesnobregalol14:54
elmikoMachineLearning-aas14:54
*** egallen has joined #openstack-meeting-314:55
tmckayelmiko, we could just start posting stuff in the channel14:55
elmikoyea, i'm just curious if anyone has talked to them yet. that will be the next step, but i have too much on my plate already ;)14:56
elmikoSergeyLukjanov: fyi https://wiki.openstack.org/wiki/Cognitive14:56
SergeyLukjanovoh, I remeber there were an email about it14:56
SergeyLukjanovand I answered something like folks, please, don't duplicate :)14:56
*** yamahata has joined #openstack-meeting-314:56
SergeyLukjanovit's good if they will use sahara as a base14:56
SergeyLukjanovfor example to provisioning cluster for ML14:57
*** amit213 has quit IRC14:57
*** amit213 has joined #openstack-meeting-314:57
*** egallen has left #openstack-meeting-314:58
elmikoyea, that would be awesome14:58
*** puranamr has joined #openstack-meeting-314:58
*** johnbelamaric has joined #openstack-meeting-314:59
*** regXboi has joined #openstack-meeting-314:59
*** mlavalle has joined #openstack-meeting-314:59
tmckaywow, we used the whole meeting14:59
*** Networkn3rd has joined #openstack-meeting-314:59
tellesnobregathe same with happened with the project Surge (stream processing on openstack)15:00
elmikointeresting...15:00
*** amit213 has quit IRC15:00
*** amit213 has joined #openstack-meeting-315:00
carl_baldwinHi, L3 meeting scheduled for now.15:00
tellesnobregai guess our time is up15:01
tmckayyep, we have to leave15:01
kchenbye all15:01
elmikocarl_baldwin: sorry15:01
huichunbye15:01
esikachevbye15:01
tellesnobregabye15:01
elmikojust need SergeyLukjanov to #endmeeting15:01
*** ramanjaneya_ has joined #openstack-meeting-315:01
*** pc_m has joined #openstack-meeting-315:01
carl_baldwinelmiko: thanks!15:01
*** esikachev has left #openstack-meeting-315:01
pc_mhi15:02
carl_baldwin#startmeeting neutron_l315:02
openstackcarl_baldwin: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.15:02
tmckay#endmeeting15:02
carl_baldwinOh, thought I saw endmeeting already.15:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:02
openstackMeeting ended Thu Jun 18 15:02:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-06-18-14.01.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-06-18-14.01.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-06-18-14.01.log.html15:02
regXboitmckay: thanks!15:02
elmikothanks tmckay15:02
tmckaywow, it let me do it!15:02
tmckay:)15:02
tmckaybye15:02
carl_baldwin#startmeeting neutron_l315:02
openstackMeeting started Thu Jun 18 15:02:39 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:02
openstackThe meeting name has been set to 'neutron_l3'15:02
*** MarkAtwood has joined #openstack-meeting-315:02
*** tmckay has left #openstack-meeting-315:02
regXboi#info regXboi (Ryan Moats)15:02
carl_baldwin#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
regXboicarl_baldwin: as promised/threatened :)15:03
*** crobertsrh has left #openstack-meeting-315:03
*** puranamr has quit IRC15:03
*** pino|work has left #openstack-meeting-315:03
ramanjaneya_Hi carl15:03
haleybhi15:03
*** tosky has left #openstack-meeting-315:03
yamahatahello15:03
carl_baldwinI’d like to welcome haleyb as our first core focusing on the L3 area.15:03
yamamotohi15:03
johnbelamarichi15:03
pavel_bondarhi15:04
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:04
pc_mYay!15:04
yamamotohaleyb: congrats15:04
*** e0ne has quit IRC15:04
johnbelamarichaleyb: welcome, congrats15:04
mlavallehaleyb: yeah, congratulations!15:04
carl_baldwinThe Neutron mid-cycle is next week in Fort Collins.  I look forward to seeing as many of you as possible.15:04
johnbelamariccarl_baldwin: looks like I can make it now :)15:05
carl_baldwinjohnbelamaric: great15:05
carl_baldwin#link https://etherpad.openstack.org/p/neutron-liberty-mid-cycle15:05
haleybthanks, i look forward to helping out more15:05
carl_baldwinAlso, Liberty-1 is next week too.15:05
regXboicarl_baldwin: is there any change the mid-cycle will have an IRC channel or way for remotes to get involved?15:05
regXbois/change/chance/15:05
mohankumarHi15:05
carl_baldwinregXboi: mestery has put a note at the bottom of the etherpad.15:06
*** mickeys has joined #openstack-meeting-315:06
carl_baldwin#topic Bugs15:06
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:06
regXboicarl_baldwin: thanx, I see that - will bug mestery (I'm good at that)15:06
*** tidwellr has joined #openstack-meeting-315:06
*** kchen has quit IRC15:06
*** amit213 has quit IRC15:07
carl_baldwinThanks to mlavalle for helping us to stay on top of the bugs with the l3-ipam-dhcp tag15:07
*** amit213 has joined #openstack-meeting-315:07
mlavallecarl_baldwin: :-)15:07
carl_baldwinOur bug list is shrinking.  That is good.  Just in time to write some more.  ;)15:08
carl_baldwin#topic Routing Network Segments15:08
*** openstack changes topic to "Routing Network Segments (Meeting topic: neutron_l3)"15:08
carl_baldwinThis is the hot topic for today, I think.15:08
regXboi:)15:08
carl_baldwinSo, where do we start?  I guess I could get a couple of links.15:09
regXboialways good for the minutes :)15:09
*** mickeyspiegel has joined #openstack-meeting-315:09
HenryGI am a bit out of the loop on this. Is it intended to cover all the various segmentation strategies that the operators are mentioning (no two seem to be the same)?15:10
carl_baldwin#link https://bugs.launchpad.net/neutron/+bug/145889015:10
openstackLaunchpad bug 1458890 in neutron "Add segment support to Neutron" [Undecided,Triaged]15:10
carl_baldwin^ this is the rfe15:10
*** mickeys has quit IRC15:10
carl_baldwinHenryG: I guess that is what we’re here to discuss.15:10
carl_baldwin#link https://review.openstack.org/#/c/172244/15:11
*** tsbot_ has quit IRC15:11
carl_baldwin^ This is the spec that I wrote with a similar network segments concept.15:11
regXboiI guess the first question is whether the spec covres the rfe?15:11
* HenryG pings baoli to pay attention because he was asking about this15:12
carl_baldwinregXboi: Not entirely.  The spec is written for a different use case.  However, it does introduce network segments which map to a given set of hosts.15:12
carl_baldwinI believe that the network segment idea could be shared between the two.15:13
regXboicarl_baldwin: I think I saw a comment from you that the spec was at best partial coverage because of that (am I remembering correctly)?15:13
carl_baldwinBeyond network segments, the rfe talks about some Nova work to pass a segment id when creating a port and then using IP usage information in scheduling.15:13
*** amit213 has quit IRC15:13
*** amit213 has joined #openstack-meeting-315:14
carl_baldwinregXboi: Yes, just to be clear:  The spec does not completely cover the use case in the rfe.15:14
regXboicarl_baldwin: a concern - how would this rfe interact with the multiple provider extension?15:14
* regXboi worries about overloading the segment concept15:15
carl_baldwinregXboi: Good point, it did not cross my mind yet.15:15
*** vgridnev has quit IRC15:16
*** amit213 has quit IRC15:16
*** amit213 has joined #openstack-meeting-315:16
regXboicarl_baldwin: I would like to think that we could start from that point, although it risks conflating physical segmentation with the rfe, which wants to include logical segmenation15:16
*** jckasper has joined #openstack-meeting-315:17
*** egallen has joined #openstack-meeting-315:17
carl_baldwinregXboi: Right, I think it is worth some of my time to reconcile these with multiple provider extension.15:17
regXboicarl_baldwin: I'd be willing to pitch some cycles there as well15:17
regXboibecause I think it might be possible to pull all three (mpe, rfe, backing networks) together15:18
*** rhagarty_ has quit IRC15:18
carl_baldwinregXboi: I think you’re right.  At least find the commonality and use it to build a good base for the rfe and routing network segments to build from.15:19
pc_mregXboi: Any links to info on the multiple provider extension?15:19
regXboi#link http://developer.openstack.org/api-ref-networking-v2-ext.html15:20
* pc_m trying to come up to speed on this15:20
pc_mregXboi: Thanks!15:20
regXboipc_m: yw15:20
carl_baldwinpc_m: Under “Networks multiple provider extension”15:20
pc_myeah found it. thanks.15:20
carl_baldwinregXboi: Let’s do some homework today and maybe we could meet in the neutron room tomorrow at some time for a discussion.15:21
regXboicarl_baldwin: sounds like a plan - I'll check my calendar and hit you with some times I can be there15:21
*** amit213 has quit IRC15:21
*** amit213 has joined #openstack-meeting-315:22
carl_baldwinregXboi: Great.  Anyone else want to be notified of the time?15:22
carl_baldwinIf so, ping regXboi15:22
pc_msure15:22
carl_baldwinOkay.  Anything else on network segments that we should hit today?15:22
*** sdake has quit IRC15:23
carl_baldwinI plan to attend the LDT meeting after this meeting.  We may mention it there too.15:24
*** amit213 has quit IRC15:24
*** amit213 has joined #openstack-meeting-315:24
regXboicarl_baldwin: feel free to let folks there know to ping me for notification about tomorrow's times15:24
carl_baldwinregXboi: I will.15:24
regXboi:)15:24
pc_mcarl_baldwin: What channel?15:24
carl_baldwinpc_m: LDT?15:25
pc_mfor the LDT meeting15:25
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/LDT15:25
pc_mthx15:25
carl_baldwin#topic bgp-dynamic-routing15:25
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:25
*** amit213 has quit IRC15:26
carl_baldwintidwellr: ping15:26
*** amit213 has joined #openstack-meeting-315:26
tidwellrhey15:26
*** kebray has joined #openstack-meeting-315:26
carl_baldwinHow are we doing here?15:26
*** vgridnev has joined #openstack-meeting-315:26
*** devvesa has joined #openstack-meeting-315:26
*** vgridnev has quit IRC15:26
*** armax has joined #openstack-meeting-315:26
devvesaHi. I think I log in time15:27
carl_baldwindevvesa: You are here.  Hi.  Didn’t mean to miss you.15:27
tidwellrI think we're in good shape .  I'm working on another patch set for the API/DB layer. I'm taking the time to do API tests as I go.15:27
devvesaOh, just logged now :)15:27
devvesaSorry15:28
*** amit213 has quit IRC15:28
carl_baldwintidwellr: Are all of the patches on a topic we could like to here?15:28
*** amit213 has joined #openstack-meeting-315:28
carl_baldwindevvesa: Good timing.15:28
*** salv-orlando-mob has joined #openstack-meeting-315:28
*** amit213 has quit IRC15:28
tidwellrbp/bgp-dynamic-routing15:29
*** amit213 has joined #openstack-meeting-315:29
carl_baldwin#link https://review.openstack.org/#/q/topic:bp/bgp-dynamic-routing,n,z15:29
regXboitidwellr, carl_baldwin: is there a plan for incorporating these tests into the gate?15:30
regXboiI ask because I suspect the LDR folks will want to tune that test for their specific deployments15:30
tidwellryes,  that needs to be done, not sure how to start though15:30
regXboi(sorry LDT, not LDR) or is the plan to have that in 3P/CI testing so that each LDT can tune it as needed?15:31
tidwellrI've a little myopic about just getting tests running in my environment, but my intention is to have a CI job for BGP15:31
tidwellrcould use a little help there......15:32
regXboitidwellr: unfortunately, I'm not sure I can commit to that, but let me look around and see if I can scare up some help...15:33
carl_baldwinWell, let’s hit the reviews and keep our eye on building tests for the gate.15:34
carl_baldwinAnything else for this topic?15:34
carl_baldwin#topic neutron-ipam15:34
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:34
pavel_bondarhi15:35
tidwellrnot from me, devvesa?15:35
*** bpokorny has joined #openstack-meeting-315:35
*** sdake has joined #openstack-meeting-315:35
carl_baldwinpavel_bondar: great work on breaking up the large review.  It is a lot easier to review now.  It is nice to have check-points along the way.15:36
*** amit213 has quit IRC15:36
*** Ericn has joined #openstack-meeting-315:36
devvesaneither. Just waiting your next patch, tidwellr :)15:36
pavel_bondarI have created 3 more review today:)15:36
*** amit213 has joined #openstack-meeting-315:36
pavel_bondarnext review in chain to be merged is #link https://review.openstack.org/#/c/189299/15:36
*** amit213 has quit IRC15:36
*** amit213 has joined #openstack-meeting-315:37
pavel_bondarand 6 more reviews are on top of that15:37
johnbelamaricpavel_bondar: nice, lots of work but I think it is much easier this way15:37
carl_baldwinpavel_bondar: This one is looking pretty good.15:38
pavel_bondarjohnbelamaric: agree15:38
pavel_bondarcarl_baldwin: nice15:38
*** singleth_ has quit IRC15:38
pavel_bondarI can post full review chain into IRC if needed15:39
carl_baldwinSo, we just keep going.  Reviewers can start with this^ and follow the chain.15:39
*** amit213 has quit IRC15:39
carl_baldwinpavel_bondar: Probably not needed.15:39
*** amit213 has joined #openstack-meeting-315:39
pavel_bondarcarl_baldwin: ok15:39
*** egallen has quit IRC15:39
carl_baldwinAnything to discuss?15:39
*** amit213 has quit IRC15:40
*** amit213 has joined #openstack-meeting-315:40
carl_baldwin#topic ML3 Router plugin15:40
*** openstack changes topic to "ML3 Router plugin (Meeting topic: neutron_l3)"15:40
carl_baldwinAnyone here to give a report on this?15:40
yamahataHello.15:40
yamahataSo far we gathered the use cases in etherpad15:40
*** salv-orlando-mob has quit IRC15:40
yamahatahttps://etherpad.openstack.org/p/neutron-modular-l3-router-plugin-use-cases15:40
yamahataThey are for requirement.15:41
yamahataSo the next step is to define operation scenario in order to define desired API or CLI operations15:41
yamahatapcarver: ping?15:42
regXboiyamahata: Use Case #4 looks very close to service chaining - is that intentional?15:42
carl_baldwinThese look good.15:42
yamahataregXboi: Yeah. the difference is that the service is on edge.15:42
yamahataIf SFC supports it, it's quite fine with it.15:42
*** amit213 has quit IRC15:43
*** amit213 has joined #openstack-meeting-315:43
yamahataDeployer may think SFC is overkill. they may want more simpler way to just deploy single function.15:43
regXboiyamahata: got it - but I need to go off and think about whether you've just created an SFC implementation unintenionally15:43
regXboiyamahata: I'm not saying that's a bad thing15:44
* regXboi needs to think about the implications15:44
yamahataregXboi: I don't want to reinvent SFC.15:44
*** amit213 has quit IRC15:44
yamahatapcarver doesn't seem here. Contact him off line.15:45
*** amit213 has joined #openstack-meeting-315:45
regXboiyamahata: understood, like I said, let me think about the implications15:45
yamahataregXboi: sure.15:45
carl_baldwinyamahata: How do we go about the next step?15:45
*** sridhar_ram has joined #openstack-meeting-315:45
*** mpavlase has quit IRC15:45
yamahataI'll write up a draft for desired operation scenario. then get review.15:46
carl_baldwinyamahata: Sounds like a plan.15:46
*** praveens has joined #openstack-meeting-315:46
carl_baldwinAnything else?15:46
carl_baldwin#topic dns-resolution15:46
*** openstack changes topic to "dns-resolution (Meeting topic: neutron_l3)"15:46
carl_baldwinmlavalle: ping15:46
mlavalleKiall helped us to respond to the concerns in https://review.openstack.org/#/c/8862315:47
carl_baldwinI was looking at those this morning.15:47
mlavalleHe added a comment yesterday. I'll update the spec today15:47
*** amit213 has quit IRC15:47
*** amit213 has joined #openstack-meeting-315:48
*** Ericn_ has joined #openstack-meeting-315:48
mlavalleHe also wrote the discussion in vancouver to https://review.openstack.org/#/c/88624/, so it is looking good15:48
mlavalleThe nova side https://review.openstack.org/#/c/90150/ was refreshed by me laste last week andgot a +1. Will follow up with johnthetubaguy to get it reviewed by him15:49
*** belmoreira has joined #openstack-meeting-315:49
regXboimlavalle: I assume you are looking for reviews on updated 88623 and 88624?15:49
*** amit213 has quit IRC15:49
mlavalleAnd I am already coding for https://review.openstack.org/#/c/8862315:50
*** amit213 has joined #openstack-meeting-315:50
mlavalleregXboi: yes15:50
carl_baldwinmlavalle: Good progress.15:50
*** stevelle has joined #openstack-meeting-315:50
regXboimlavalle: thx15:50
mlavalleI should push WIP patchset soon15:50
*** amit213 has quit IRC15:50
*** amit213 has joined #openstack-meeting-315:51
mlavalleKial comments to 88623 change code a bit, but not much.15:51
mlavallethat's all I have15:51
carl_baldwinmlavalle: I look forward to seeing it.  Ping at least haleyb and me for reviews.  And, anyone else interested.15:51
mlavallewill do15:52
carl_baldwin#topic Address Scopes15:52
*** openstack changes topic to "Address Scopes (Meeting topic: neutron_l3)"15:52
* mlavalle looking forward to get review from our brand new core :-)15:52
*** amit213 has quit IRC15:52
*** amit213 has joined #openstack-meeting-315:52
carl_baldwinI added an update to the BP:  https://review.openstack.org/#/c/192914/15:52
carl_baldwinOtherwise, I’m coding now and hope to have things working on the L3 agent side in a couple of days.15:53
carl_baldwinThe address scope crud work has also started.15:53
carl_baldwinhttps://review.openstack.org/#/c/189741/15:54
*** datsun180b has joined #openstack-meeting-315:54
carl_baldwinVikram is still on vacation but should return soon.15:54
carl_baldwin#link https://review.openstack.org/#/c/189741/15:54
carl_baldwin#topic IPv615:54
*** openstack changes topic to "IPv6 (Meeting topic: neutron_l3)"15:54
*** james_li has joined #openstack-meeting-315:55
*** arunrajan has joined #openstack-meeting-315:55
carl_baldwinAnything here?  I know I’ve been neglecting the PD reviews.  I’ve been trying to get to it and will soon.15:55
*** amit213 has quit IRC15:55
john-davidgecarl_baldwin: Thanks, I know it’s a big patch!15:55
*** amit213 has joined #openstack-meeting-315:55
*** kozhukalov_ has joined #openstack-meeting-315:57
*** matrohon has quit IRC15:57
*** muralia has joined #openstack-meeting-315:57
carl_baldwinIn general, this needs more reviewer attention.  Not just from cores.  I’d like to see it start to build some consensus with multiple +1s.15:57
*** jay-s-b has joined #openstack-meeting-315:57
* haleyb needs to re-review the PD changes as well15:58
*** salv-orl-mobile has joined #openstack-meeting-315:58
john-davidgeHere’s the first PD patch in the chain: https://review.openstack.org/#/c/15869715:58
*** amit213 has quit IRC15:58
*** amit213 has joined #openstack-meeting-315:58
*** victor_lowther has left #openstack-meeting-315:59
carl_baldwinHow can we get more attention on this from the community?15:59
john-davidgeThe second is currently in merge conflict with the ongoing db_plugin_v2 decomp work15:59
john-davidgecarl_baldwin: Reviews keeping it near the top of the list will help, otherwise I could spam the mailing list with demo videos :)16:00
carl_baldwinI guess our time is up.16:00
*** amit213 has quit IRC16:00
carl_baldwinWe can take stuff to the neutron room.16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Jun 18 16:00:27 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-06-18-15.02.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-06-18-15.02.txt16:00
*** amit213 has joined #openstack-meeting-316:00
yamamotobye16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-06-18-15.02.log.html16:00
pc_mbye16:00
*** pc_m has left #openstack-meeting-316:00
elmiko#startmeeting api wg16:00
openstackMeeting started Thu Jun 18 16:00:46 2015 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
yamahatabye16:00
*** openstack changes topic to " (Meeting topic: api wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
*** arunrajan has quit IRC16:00
*** cdent has joined #openstack-meeting-316:01
elmiko#topic agenda16:01
salv-orl-mobileAloha16:01
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:01
cdento/16:01
jaypipes.....0...../16:01
edleafeo/16:01
miguelgrinberghi16:01
*** regXboi has left #openstack-meeting-316:01
* jaypipes comes running in...16:01
etoewso/16:01
elmiko#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:01
muraliao/16:01
elmikojaypipes: lol16:01
*** johnbelamaric has left #openstack-meeting-316:01
edleafejaypipes: thought you had long arms :)16:01
*** hdd has left #openstack-meeting-316:01
elmikolots of stuff on the agenda today16:01
jaypipesedleafe: no, I just tripped running to the meeting,.16:01
*** egallen has joined #openstack-meeting-316:02
*** arunrajan has joined #openstack-meeting-316:02
elmikolet's give folks a minute or two16:03
stevelleo/16:03
elmikoi'm not sure on the freshness of our action item list, we'll see16:03
elmiko#topic previous meeting action items16:04
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:04
sdagueo/16:04
elmiko#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-06-04-16.00.html16:04
elmikoi did both of mine16:05
elmikolooks like the rest were between cdent and sdague, you guys wanna give updates?16:05
sdagueelmiko: I did a pretty detailed review of the artifacts api in glance, I haven't looked at their follow up16:05
elmikosdague: awesome!16:05
cdentsdague and I made some comments on the glance api proposal. It felt a bit like a pileon but I think the input from everyone was useful.16:05
sdagueI'm assuming our reviews of other project APIs are advisory, as in "we think this would be a better way to do it, but it's your API"16:06
etoewscdent: what's the sentiment on the api wg reviews?16:06
elmikoi certainly hope it's taken that way16:06
sdagueI don't think I scored my review for that reason16:06
sdaguethis was the revision everyone pretty much reviewed - https://review.openstack.org/#/c/177397/3/specs/liberty/artifacts-api.rst,cm16:06
krotschecko/16:07
cdentetoews: I haven't been able to get guage on reactions16:07
*** amit213 has quit IRC16:07
*** amit213 has joined #openstack-meeting-316:07
sdagueyeh, there hasn't been an update yet to the review, so I don't know16:08
etoewshmmm...zero replies to the comments.16:08
sdaguejaypipes you are a little closer to that team, any idea on how they are feeling about it?16:08
*** zz_natorious is now known as natorious16:08
jaypipessdague: they will align with the API WG guidelines.\16:08
elmikocool16:08
jaypipessdague: they've already stated as much. will have to align ex post facto, since they merged already, but they will align.16:09
*** amit213 has quit IRC16:09
sdagueoh, the API is already merged?16:09
*** hurgleburgler has joined #openstack-meeting-316:09
*** amit213 has joined #openstack-meeting-316:09
*** hurgleburgler has left #openstack-meeting-316:09
etoewsmclaren and nikhil_k are the CPLs for glance16:10
jaypipessdague: some of it is, yes, AFAIK.16:10
*** amit213 has quit IRC16:11
elmikodo we have an action here, or just wait and see what happens with the review?16:11
*** amit213 has joined #openstack-meeting-316:11
etoewsi think we're in wait and see mode at the moment16:11
elmikok16:11
cdentthe other action I had was about changes-since: I dropped a question on the filtering spec about changes-since and got the expected reply: that something more generic is probably the right way to go and in any case whatever it is, not on that spec16:12
cdentso the question remains: do we want (and if we do who wants to) to formalize a mode of doing changes-since across all collection apis?16:12
sigmavirus24hi16:13
*** amit213 has quit IRC16:13
*** amit213 has joined #openstack-meeting-316:13
etoewscdent: how many apis is changes-since in? only nova comes to my mind.16:13
stevelleglance also16:13
*** singlethink has joined #openstack-meeting-316:14
stevellehttps://review.openstack.org/#/c/192926/ is relevant to this topic16:14
jaypipesglance does.16:14
miguelgrinbergcdent: by "changes-since" you mean give me the list of entities that were modified since a given date, correct?16:14
sigmavirus24miguelgrinberg: believe so16:14
jaypipesmiguelgrinberg: yup.16:14
miguelgrinbergthen this is a query on the last_modified field16:14
jaypipesdoens't Ceilo also have that?16:14
miguelgrinbergwhy can't we treat it as a regular query then?16:14
cdentmiguelgrinberg: as I understand it, yes, but I get the impression that changes-since has somewhat more magical semantics than modified_time>somedate?16:15
miguelgrinbergdon't know, what's special about it?16:15
cdentso the underlying question is: what are those magical semantics?16:15
jaypipescdent: nope, that's pretty much the extent of it :)16:15
stevellecdent: speaking only of glance V1, it's magic was to include deleted rows16:15
cdentthat's quite magic if they are _actually_ deleted :)16:15
jaypipesah16:15
jaypipescdent: welcome to the world of soft-delete.16:15
stevellefor V2 glance that is to be supported via a status field filter16:16
sdaguecdent: welcome to the world of soft-deletes16:16
sdaguejaypipes: jinx16:16
jaypipesha!16:16
cdentisn't there a wiki page about changes since somewhere?16:16
* cdent looks16:16
*** s3wong has joined #openstack-meeting-316:16
cdenthttp://docs.openstack.org/developer/nova/v2/polling_changes-since_parameter.html16:16
*** rushiagr_away is now known as rushiagr16:16
*** egafford has left #openstack-meeting-316:16
cdentyeah, looks like nova also has some attention to things recently deleted as well16:16
cdentso presumably a simple attribute query would not have that?16:17
*** alexsyip has joined #openstack-meeting-316:17
miguelgrinbergyou could ask for the last_modified *and* a state=active,deleted,whatever-else16:18
cdentthus the magic of changes-since...do we as a group care to enshrine that?16:18
miguelgrinbergso we do it without magic16:18
sdaguecdent: honestly, I think what a project decides it wants to return should be fine16:18
jaypipescdent: I do not care to enshrine anything "magic" in our APIs, no.16:18
*** amit213 has quit IRC16:18
cdentI'm cool with that. Prefer it in fact.16:18
elmikomiguelgrinberg: i like that approach, seems more explicit16:19
*** amit213 has joined #openstack-meeting-316:19
sdagueI kind of like it as a more abstract changes-since concept that would be common accross projects16:19
Ericnmagic changes over time....16:19
stevellemiguelgrinberg: yes, exactly16:19
sigmavirus24sdague: as in "projects should implement changes-since"?16:19
cdentright on, good, this is the right outcome: filter with a combined query is more sensible16:19
cdentand comprehensible too16:19
sdaguesigmavirus24: on resources that you expect to be polled, we recommend you implement this16:19
sigmavirus24isn't there only two states for the magic switch to be set to in OpenStack? "magic" and "more magic"?16:20
sigmavirus24sdague: that seems reasonable16:20
elmikosigmavirus24: lol16:20
sigmavirus24s/isn't/aren't/16:20
edleafesdague: +116:20
sdaguebecause as a consumer having to know all the states I'm looking for explicitly is weird16:20
sdagueI really semantically just want "tell me your changes"16:20
*** sahid has quit IRC16:20
sigmavirus24"gimme your deltas"16:20
sdagueright16:20
sigmavirus24(The new motto for Pull Requests as a Service)16:20
Ericnit is up to the server to decide what is a valid change16:21
sdagueand sure, it's a little less explicit, but it's really understandable from a consumer point of view16:21
sdagueand the explicit filters might be there for those that care16:21
stevelleso changes-since is ?state=neq:deleted&updated_at=gt:<ISO8201> under the draft filter guidelines16:21
stevelledon't need to know the states16:21
sdaguestevelle: well in glance and nova it includes deleted16:21
stevellesdague: agreed16:22
miguelgrinbergit should include everything if you don't say what states you want, that makes sense to me16:22
miguelgrinbergbut it should be consistent with other queries, IMHO16:22
sdagueand if you do care about specific states, then you can ask about it16:22
elmikosdague: wouldn't that just be ?updated_at=gt:<ISO8201> ?16:22
elmiko(following miguelgrinberg's state logic)16:23
cdentmiguelgrinberg: including deleted by default seems weird16:23
sdagueso, honestly, my feeling is that depending on the resource, returning deleted may or may not make sense, and the server probably knows better about that16:23
cdent(meant to have a ? on the end of that)16:23
sdaguewhich is why I kind of like leaving that decision up to the implementation on a point basis with changes-since16:24
miguelgrinbergif there is a "deleted" state, then those entities need to be returned if the client didn't explicitly take them out16:24
*** jay-s-b has left #openstack-meeting-316:24
stevellesdague: that inconsistency of expectation is exactly what makes me uncomfortable about changes-since16:24
miguelgrinbergdon't like that idea of doing implicit filtering based on what query the client is requesting16:25
sdaguewe give clients the explicit filters16:25
sdaguethey can do that thing16:25
etoewswe should probably move on from this in another minute or two. it can continue to be discussed in #openstack-api afterwards.16:25
elmikoetoews: +116:25
cdentetoews++16:25
cdentmabye a mailing list post16:25
sdaguethis is a value judgement call from the resource about "here's what we think you need"16:25
sdaguesure16:25
*** amit213 has quit IRC16:25
cdenteach time I bring this up I'm always surprised at how much chat it generates16:26
elmiko#action start a mailing list thread about changes-since topic16:26
*** amit213 has joined #openstack-meeting-316:26
elmikomoving on16:26
edleafeand what 'deleted16:26
edleafeugh16:26
etoewselmiko: who's got that action?16:26
edleafewhat 'deleted' means16:26
elmikooops, good point16:26
elmikocdent: you wanna start that thread?16:26
cdentSure, as long as I'm allowed to be ignorant and hand wavey16:27
elmikolol, of course ;)16:27
elmiko#action cdent start a mailing list thread about changes-since topic16:27
*** arunrajan has quit IRC16:27
cdent16:27
elmiko#topic weekly newsletter16:27
*** openstack changes topic to "weekly newsletter (Meeting topic: api wg)"16:27
elmikoetoews: i think this was from you?16:27
etoewsyep16:27
*** amit213 has quit IRC16:27
*** amit213 has joined #openstack-meeting-316:28
*** praveens has quit IRC16:28
etoewsso i really want to start up a weekly newsletter for the api wg ala "What's Up Doc?"16:28
elmikoa fine idea16:28
etoewssummarize our activity weekly for better visibilty and information dissemination16:28
cdenta great idea, but where do people find the time?16:29
*** praveens has joined #openstack-meeting-316:29
*** mlavalle has left #openstack-meeting-316:29
*** amit213 has quit IRC16:29
miguelgrinbergcan it be auto-generated from reviews,etc.  At least part of it?16:29
elmikoi don't know much about the generation of "What's Up..", do they use a template or something?16:29
etoewscdent: find the time for what exactly?16:29
*** amit213 has joined #openstack-meeting-316:30
cdentadd yet another thing to do (like manage a newsletter)16:30
etoewsmiguelgrinberg: yep. i was thinking about auto-generating parts of it.16:30
elmikoetoews: would it mainly be advertising things in freeze and recently merged?16:30
sdagueso, honestly, auto generated english basically gets deleted by people16:30
*** singleth_ has joined #openstack-meeting-316:30
etoewscdent: if i can nail down some automation with gerrit16:30
etoewsthat would make it much easier16:31
sdagueif there is a desire to be effective, it should be manually currated and entertaining, and done less often16:31
sdagueotherwise it's just spam16:31
*** Aish has joined #openstack-meeting-316:31
etoewssdague: i'd only be generate a "by the numbers" section16:31
*** Aish has left #openstack-meeting-316:31
elmikosdague: how frequently would you recommend?16:31
etoewsthe rest is manually currated and entertaining16:31
sdagueso, weekly seems like pretty often16:31
sdagueI'd be more inclined to say every 3 or 4 weeks16:32
sdagueso that there is enough content in it16:32
etoewsone of the reasons i was thinking weekly was that we could roll the "Guidelines ready for cross project review" into the newsletter16:32
elmikosdague: that makes some sense and addresses cdent's comment16:32
etoewsand the "Finalized guidelines" too16:32
elmikoetoews: but the entertaining content might suffer on a weekly release, ie might get bothersome after a few months.16:33
cdentetoews: guideliens ready is a call to action yes?16:33
cdentwhereas the rest of it is kind of news and such16:33
cdenthaving those two in the same place is a way to ensure that the call to action isn't acted upon, unfortunately16:33
etoewscdent: yes16:33
*** singlethink has quit IRC16:34
cdentI think as a starting point the best value for effort is to automate the call to action16:34
* etoews ponders16:34
cdentand see where that gets us16:34
cdent(people can always respond to that email if they want to gossip etc)16:34
elmikoi'm cool with that for a start, we need it anyway with all the guidelines that are coming16:34
*** clu_ has joined #openstack-meeting-316:35
etoewsyes. it's not easy to know what state the reviews are in at a glance.16:35
etoewsokay. i'm willing to experiment a bit with this.16:36
elmikocool16:36
cdentetoews++16:36
*** devvesa has quit IRC16:36
elmiko#action etoews experiment with creating a guideline status mailing list update16:36
elmikosound good?16:36
*** amit213 has quit IRC16:36
*** amit213 has joined #openstack-meeting-316:37
etoewsmore like "...a api wg mailing list update"16:37
elmikowill undo remove the last action?16:37
etoewsbut fine to leave as is16:37
*** arunrajan has joined #openstack-meeting-316:38
etoewsdoes anyone have any experience working with the openstack gerrit api?16:38
etoews(let's discuss that after and move on)16:38
elmikok16:38
sdagueetoews: yeh, ping me in channel16:38
elmiko#topic merge the merge process?16:38
*** openstack changes topic to "merge the merge process? (Meeting topic: api wg)"16:38
elmikoi'm +1 on this, we got really solid and positive response after the initial ML post16:39
elmikoany objections?16:39
*** Ericn_ has quit IRC16:39
sdaguenope16:40
etoewsi'll fix up the minor stuff in another patch.16:40
elmikocool, +workflowed16:40
etoewsi don't want disrupt the current green forest of +1s16:40
elmikohehe16:40
etoewselmiko: thx16:40
elmiko#topic guidelines16:40
*** openstack changes topic to "guidelines (Meeting topic: api wg)"16:40
elmikoso we have 3 that have been recommended for freeze, and 2 that need a re-review i think16:41
*** Ericn_ has joined #openstack-meeting-316:41
elmiko#link https://review.openstack.org/#/c/183694/16:41
elmiko#link https://review.openstack.org/#/c/177468/16:41
elmiko#link https://review.openstack.org/#/c/181931/16:42
cdent+1 on freezing the candidate freezers16:42
elmikothose have all been put forward as freezeable16:42
etoewselmiko: btw, freeze means -1 on workflow. not -2 code review.16:42
elmikoryanb isn't here, but i think 177468 might need another fix16:43
elmikoetoews: ack, i'll adjust my process. sorry bout that16:43
etoewsnp16:43
etoewsjaypipes: can you respond to doug's comment in https://review.openstack.org/#/c/179365/3/guidelines/http.rst ?16:44
*** amit213 has quit IRC16:44
elmikoso, should we go another round of consensus on the 177468 review before moving to freeze?16:44
*** amit213 has joined #openstack-meeting-316:44
elmiko(plus it needs a bug fix)16:44
jaypipeselmiko: yep, will do.16:44
elmiko#action jaypipes respond to comments on #link https://review.openstack.org/#/c/179365/16:45
elmikois alex here?16:46
cdentSomething I think we all need to be aware of is that as soon as any guideline is actually out there in the published world people are going to find all kinds of issues with it, so we may as well keep the process of publication as friction free as possible and instead insure that we have a robust process of post-merge review16:46
*** amit213 has quit IRC16:46
etoewsping alex_xu16:46
*** amit213 has joined #openstack-meeting-316:46
*** matrohon has joined #openstack-meeting-316:46
elmikocdent: +116:46
elmikoi think alex_xu and bknudson were having a conversation on that one, needs some resolution16:47
cdentgerrit kind of works against reviewing existing stuff, but with narrative especially it is critical that we are constantly reviewing master16:47
jaypipeselmiko: done with that action item.16:47
sdagueit's middle of the night for alex_xu16:47
elmikojaypipes: lol, fast!16:47
elmikoah ok16:47
stevellefwiw 177468 has another fix in16:47
elmikowe'll push that one till next time16:47
elmikostevelle: oh, very cool16:47
elmikoso, we'll freeze the 3 listed then.16:48
etoewsif a guideline author does decide to do a minor type/fix and erase all of the +1s, how do we track the +1s from the previous patch set to know that it's okay to merge?16:48
elmikoetoews: man... that's a darn good question16:48
sdagueetoews: all the comments are still there16:49
etoewsbut not the +1s AFAICT16:49
sdaguethe comments have the vote in them16:49
*** amit213 has quit IRC16:49
sdagueyou can still read them16:49
*** amit213 has joined #openstack-meeting-316:49
*** jproulx has joined #openstack-meeting-316:49
etoewsah. i see.16:50
etoewsconceivably you could automate that (if the api supports it)16:50
etoewsautomate displaying the +1s of the previous patch set that is16:51
etoewslet's move on16:51
elmikoetoews, jaypipes, does one of you want to freeze those reviews and make the ML announce?16:51
jaypipesetoews: feel free to freeze.16:51
elmikohehe16:51
etoews#action etoews to freeze the 3 review and announce on ML16:51
elmikocool16:51
elmikothanks16:51
elmiko#topic APIImpact16:52
*** openstack changes topic to "APIImpact (Meeting topic: api wg)"16:52
elmikosigmavirus24: you had a note here16:52
*** puranamr has joined #openstack-meeting-316:52
elmiko#link https://review.openstack.org/191542/16:52
*** amit213 has quit IRC16:52
*** amit213 has joined #openstack-meeting-316:52
*** praveens has quit IRC16:53
sigmavirus24oh sorry16:53
sigmavirus24So that spec is mostly a security measure for glance16:54
sigmavirus24That said, it'll change change somethings about representations in the API16:54
sigmavirus24If you look at L57 and ignore the untrimmed trailing whitespace16:54
*** yamamoto has quit IRC16:55
sigmavirus24You'll see what the proposal currently recommends, which I'm not convinced is actually correct, but there's some precedent for it (specifically how Amazon does this)16:55
sigmavirus24I give some reasoning around L70 though that the API-WG should like so .. eh16:55
sigmavirus24Mostly, I want feedback around the API Impact of the change16:55
elmikodoes "Content-<algo>" give enough uniqueness to the header?16:56
*** pkarikh has quit IRC16:56
sigmavirus24Yeah that's my concern16:56
sigmavirus24Not sure I can think of a different way to do it though16:56
elmikomaybe just tack an OpenStack- on the front?16:57
sigmavirus24The most common variant of that is Content-MD516:57
*** amit213 has quit IRC16:57
sigmavirus24Yeah but it's not really OpenStack specific16:57
elmikoahh16:57
*** amit213 has joined #openstack-meeting-316:57
sigmavirus24Content-SHA256 shouldn't ever conflict with anything else16:57
sigmavirus24But maybe it will?16:57
sigmavirus24In reality, I'd expect either Content-SHA2 or Content-SHA256 for that header16:58
*** bpokorny has quit IRC16:58
elmikomake sense to me16:58
*** bpokorny_ has joined #openstack-meeting-316:58
sigmavirus24okay16:58
*** sgordon has joined #openstack-meeting-316:58
*** arunrajan has quit IRC16:58
*** devkulkarni has joined #openstack-meeting-316:58
elmiko1 minute left, any last thoughts?16:58
jaypipesBeer.16:58
elmiko+116:58
*** Zucan has joined #openstack-meeting-316:58
nikhil_kthe artifacts API in glance is EXPERIMENTAL for now16:59
cdentjaypipes: can you send me one please16:59
jaypipesnikhil_k: I am 100% opposed to experimental APIs.16:59
nikhil_kso that we can adjust variations suggested but not many16:59
jaypipescdent: will do! :)16:59
*** ShillaSaebi has joined #openstack-meeting-316:59
sdagueyeh, experimental is useless construct. Once things are out in the world, they get used.16:59
etoewswould beta be a better term?16:59
nikhil_kjaypipes: we are working on making it non-experimental this cycle (hopefully)16:59
*** baoli has quit IRC16:59
elmikonikhil_k, jaypipes, we need to take this to openstack-api for further talk16:59
jaypipesnikhil_k: experimental APIs are a tried and true way of having nothing tried and true in your API. :) Trusst me, we tried that with Nova v316:59
*** fifieldt has joined #openstack-meeting-317:00
elmikothanks everyone!17:00
elmiko#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
cdento/17:00
openstackMeeting ended Thu Jun 18 17:00:08 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-06-18-16.00.html17:00
*** amit213 has quit IRC17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-06-18-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-06-18-16.00.log.html17:00
*** cdent has left #openstack-meeting-317:00
etoewsthx elmiko17:00
sdagueetoews: no, if you put software out into the world, it either gets used and you can't change it, or it doesn't get used and there was no point17:00
*** amit213 has joined #openstack-meeting-317:00
docaedo#startmeeting app-catalog17:00
openstackMeeting started Thu Jun 18 17:00:38 2015 UTC and is due to finish in 60 minutes.  The chair is docaedo. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: app-catalog)"17:00
openstackThe meeting name has been set to 'app_catalog'17:00
*** baoli has joined #openstack-meeting-317:00
*** singleth_ is now known as singlethink17:00
*** stevelle has left #openstack-meeting-317:00
docaedoTodays agenda available here:17:00
docaedo#link https://wiki.openstack.org/wiki/Meetings/app-catalog17:00
*** belmoreira has quit IRC17:01
docaedo#topic rollcall17:01
*** openstack changes topic to "rollcall (Meeting topic: app-catalog)"17:01
* fifieldt waves17:01
muraliao/17:01
fifieldtunfortunately, it's 1am, so I can't stay :)17:01
*** kfox1111 has joined #openstack-meeting-317:01
datsun180b<--17:01
*** cburkett has joined #openstack-meeting-317:01
docaedoah yes, I know so late for you, sorry17:01
*** Youcef has joined #openstack-meeting-317:01
*** jlk has joined #openstack-meeting-317:02
*** amit213 has quit IRC17:02
kebray\o17:02
*** yamamoto has joined #openstack-meeting-317:02
jlkis this for the ops guide?17:02
*** amit213 has joined #openstack-meeting-317:02
devkulkarnidevkulkarni17:02
datsun180bjlk: app catalog17:02
james_lijames li17:02
*** arunrajan has joined #openstack-meeting-317:02
docaedojlk: this is for the app catalog http://apps.openstack.org17:02
jlkstrange, maybe there was a conflict.17:02
jproulxI was also looking for ops guide17:02
docaedoHmm, this merged without conflict, and didn't show anything else on the calendar?17:03
kebrayjlk, maybe the ops meeting is an another hour?   A lof of the time conversion websites are wrong.  I tried to join the app-catalog meeting an hour ago.17:03
*** amit213 has quit IRC17:03
datsun180bit's 1704Z by my clock17:04
*** bpokorny_ has quit IRC17:04
*** amit213 has joined #openstack-meeting-317:04
*** carl_baldwin has quit IRC17:04
*** sridhar_ram has quit IRC17:04
docaedoMoving on I think? sorry for confusion, I have 17:05 zulu on my clock too :)17:05
kfox1111yeah.17:05
docaedo#topic Announcements17:05
*** openstack changes topic to "Announcements (Meeting topic: app-catalog)"17:05
*** jlk has left #openstack-meeting-317:05
docaedoMoving app catalog hosting to OpenStack infra complete as of 6/15:17:05
docaedo#link https://review.openstack.org/18786317:05
docaedo#link https://review.openstack.org/18999317:05
docaedo#link https://review.openstack.org/18701817:05
docaedoRegarding infra and hosting, changing the object store to community managed one (vs. current rackspace files location) is something I propose we discuss later, as it's not pressing.17:06
*** sridhar_ram has joined #openstack-meeting-317:06
docaedoWe don't have a flood of incoming binaries to host ATM, and it's "on OpenStack" so not a rush - I will start a discussion on ML for how best to handle it going forward.17:06
*** amit213 has quit IRC17:06
docaedo#action docaedo start ML discussion re: object store for app catalog17:06
*** amit213 has joined #openstack-meeting-317:06
docaedoI also wanted to point out a few pending reviews for general openstack project housekeeping. If you want to review these, please do - they're basically ready to go AFAIK17:06
docaedo#link https://review.openstack.org/191990 (add site to cacti)17:06
docaedo#link https://review.openstack.org/190343 (enable IRC logging)17:06
docaedo#link https://review.openstack.org/191478 (mailing list)17:06
*** Ericn_ has quit IRC17:07
docaedoThat last one, the mailing list, relates to the "handling stale entries" topic that I was going to let Gosha lead but he's on vaca until next week, so we'll pick it up next week.17:07
docaedoAny other announcements?17:07
docaedook, guess not - moving on17:08
*** amit213 has quit IRC17:08
kebraydocaedo, just that we'd like to get Solum languagepacks avaialble on apps.openstack.org.  what are the requirements?17:08
*** amit213 has joined #openstack-meeting-317:08
*** cburkett has quit IRC17:08
kebrayThat is, how are things decided to be listed or not listed as a new category on apps.openstack.org?17:08
kebrayso, not an announcement.. a question.  we can take it up later if need be.17:09
docaedokebray: let's cover that later, but today - we need to discuss how to add more categories (and definitely want to see solum LPs in there)17:09
kebraygreat!  thx.17:09
docaedo#topic Proposal: stale entries (kfox1111)17:09
*** openstack changes topic to "Proposal: stale entries (kfox1111) (Meeting topic: app-catalog)"17:09
*** mpmsimo has joined #openstack-meeting-317:09
*** jproulx has left #openstack-meeting-317:09
*** yamahata has quit IRC17:09
docaedokfox1111: you had started a conversation on the mailing list re: stale entries, and for a start, I think you wanted to add an additional field17:10
*** Ericn has quit IRC17:10
kfox1111yeah.17:10
docaedosomething like "entry_maintainer" or so17:10
sgordonmakes sense17:10
*** kztsv_mbp has joined #openstack-meeting-317:10
kfox1111if something breaks, how do we know how to contact the maintiner to fix their website,17:10
sgordoni would think we could also do some automation to detect if a url is now a 404?17:10
kfox1111or let them know we will pull the entry after some amount of time with it being broken.17:10
*** amit213 has quit IRC17:10
kfox1111yeah. with such a field, eventually it could pull and notify directly.17:11
*** amit213 has joined #openstack-meeting-317:11
docaedomakes sense to me, and yes, this field would be useful for an automatic script checking external links17:11
docaedoGosha volunteered to write a simple script that zuul would run periodically, to check external links and notify a mailing list (plus the email), so I see that as phase 2, but first off17:12
docaedoadd this field to the schema17:12
*** mpavlase has joined #openstack-meeting-317:12
docaedoshould we populate the entries with whoever put in the patch relating to that entry?17:12
docaedo(pre-populate for now I mean, and then going forward just make it a required field)17:13
kfox1111that, and maybe email them letting them know we've done that, giving them the opertunity to change it if they want.17:13
docaedo+117:13
kfox1111yeah. required as soon as possible would be good.17:13
docaedoany volunteers to do this?17:14
*** krtaylor has quit IRC17:14
kfox1111I can take a stab at it I think.17:14
docaedothanks, I'll help, will coordinate with you on IRC17:15
*** krtaylor has joined #openstack-meeting-317:15
kztsv_mbpalso. how would taking down work? Is there an enabled/disabled param, that can be switched on/off in a yaml file or shall the whole entry be removed?17:15
kfox1111related to that, should we create a common.schema.yaml that we validate all the other yamls against? Then I can put the required admin metadata stuff in there.17:15
kztsv_mbpSorry if that has been discussed or if I'm asking a dumb question.17:15
docaedo+1 on common.schema.yaml17:15
docaedokztsv_mbp: not a dumb question, and hasn't been decided exactly17:16
*** matrohon has quit IRC17:16
docaedothe method for removal right now is a code review17:16
kfox1111there isn't a field yet, but we could add one. a hidden/disabled" field?17:16
*** natorious is now known as zz_natorious17:16
docaedoI think it's better to pull something out completely if there's reason to - easy enough to add later, and to me makes sense to drop the entry entirely17:16
docaedowith justification noted in the commit message17:16
kfox1111yeah, so long as we're backing it with git, we still have all the history, so adding it back would be easy.17:17
docaedothen there's an obvious trail of who wanted something out, and why17:17
docaedoexactly - as much as possible I want to use the gerrit workflow17:17
kztsv_mbpdocaedo: the reasoning behind the question is that taking the whole entry down is a, rather drastic thing to do. A person who submitted the asset would have to go through the review process from scratch.17:18
*** amit213 has quit IRC17:18
*** amotoki_ has quit IRC17:18
*** amit213 has joined #openstack-meeting-317:18
kztsv_mbpWhile flipping a bool field seems like a less restrictive approach17:18
kfox1111I think we probably should come up with a policy of some sort. we send 3 or 4 emails over some time period, then pull it.17:18
*** mattgriffin has joined #openstack-meeting-317:18
docaedotrue, but just flipping the bool would only hide it from the web site frontend, it would still be in the yaml17:18
kfox1111maybe we have a flag we set on the entry as soon as its detected flagging it visually to the users as potentially broken?17:19
docaedoso if there is a need for somethign to be "not there", seems completely removing it is the best option17:19
sgordonwould the boolean be in the yaml anyway though?17:19
*** amit213 has quit IRC17:19
docaedobut maybe in case of something being temporarily 404 (like while the zuul checker happened to run), completely removing would seem drastic, yeah17:19
*** amit213 has joined #openstack-meeting-317:20
kfox1111agreed.17:20
kfox1111or they are in a downtime for an hour or so.17:20
docaedoand yes, the boolean would be in the yaml too - my question I guess is what's the advantage of hiding over removing17:20
kfox1111shouldn't totally kill things.17:20
kfox1111theres a window, 404 detected ...... user tries to launch,17:21
kfox1111that it could be fixed between.17:21
kztsv_mbpdocaedo: it's more like a 2 step removing. If the entry is down for 2 days — flip the switch. If it's still down after a week and the author didn't contact anyone — remove completely17:21
sgordonright17:21
kfox1111if its only checked once a day for example, it could have been fixed after only an hour, and users wouldn't be able to use it for 23 more.17:21
sgordoni dont think we would have to check as infrequently as once a day for a simple is the link valid17:22
docaedokztsv_mbp: I could see that, but would personally advocate for putting in a review that removes it, mark it WIP, and send the "owner" a warning that it's marked for removal17:22
sgordonif we wand to download it and confirm that hash then that is more invasive17:22
sgordondocaedo, +1 i like that approach17:22
docaedootherwise my fear is that we'll eventually be flipping that bool on and off a lot (and if we do that, we could end up with dozens of flipping on and off)17:23
kztsv_mbpoh. yep. I'm not advocating automatic removing here.17:23
sgordonto me if the bool is in the yaml anyway there is no advantage over proposing removal - in either case both the removal and adding it back later require a review cycle17:23
kfox1111yeah. you'd have to have the bool outside the yaml that gets merged in on retrieve to be more automatic.17:23
docaedoyeah when it comes to automating this stuff, I want to push that conversation down the road a little bit17:24
kfox1111probably more trouble then its worth for now.17:24
kztsv_mbpThe flipping could possibly be a commit, by some bot then? but be approved by those with common sense =)17:24
docaedoeventually, we are going to need to tackle that stuff, maybe even soon-ish, but right now with just having flat yamls, easier to minimize the number of commits17:24
docaedoyep, whether it's a bool flip, or full removal, still needs human to +217:25
kfox1111It may be tricky to automate the yaml editing without causing other lines in the file to be rearanged.17:25
docaedohow about this:17:25
docaedoI'll write up the options, send to ML, and we'll let broader audience weigh in?17:25
kztsv_mbpsounds right to me =)17:26
kfox1111k17:26
docaedonice :) moving on...17:26
sgordonkfox1111, mmm the marker for the start of an entry is fairly easy to spot though iirc17:26
sgordonkfox1111, is simple a matter of chopping from there to the next one17:26
kfox1111yeah. just not as simple as yaml import, set new value, yaml export though.17:26
*** amit213 has quit IRC17:26
*** carl_baldwin has joined #openstack-meeting-317:27
*** amit213 has joined #openstack-meeting-317:27
sgordonkfox1111, sure but if at some point you have to remove it anyway...17:27
docaedosgordon: I'm with you, adjusting or chopping is going to be pretty easy to automate17:27
kfox1111thats why I'd kind of perefer it be in a seperate document thats merged on fetch.17:27
kfox1111I'm thinking we may want to do that anyway down the line for stuff like user submitted stars.17:28
kfox1111don't want to need a gerrit review for all of those. :/17:28
docaedokfox1111: user submitted stars as patches would overwhelm the catalog instantly, and poses too high a barrier for people to give their thoughts on an asset17:28
kfox1111exactly.17:29
docaedothat topic is a big one, in a little bit we'll have a quick throw down of things to discuss17:29
docaedofor now, lets move on and take this topic to ML17:29
kfox1111k.17:29
docaedo#topic Versions for entries (docaedo)17:29
*** openstack changes topic to "Versions for entries (docaedo) (Meeting topic: app-catalog)"17:29
sgordonyeah i dont think necessarily merging in a separate file scales for that use case anyway17:29
*** amit213 has quit IRC17:29
*** ramanjaneya_ has quit IRC17:29
docaedoIt would be nice to version the entries in some way, but maybe it's not even worth discussing as long as we have everything in a flat yaml17:30
*** amit213 has joined #openstack-meeting-317:30
docaedobut I wanted to bring up today because it's an issue that has popped up several times17:30
sgordondocaedo, what kind of versioning were you imagining - different versions of the same asset class (e.g. Ubuntu 14.04 vs 15.04) or the entry itself17:30
docaedoand not really sure the best way to deal with it right now - what do you think, do we even NEED to deal with this right now?17:30
*** ativelkov has joined #openstack-meeting-317:30
docaedosgordon: the entry iteself17:30
sgordonmmm, i guess what are the examples where it has come up?17:30
docaedothe example would be an updated entry17:30
sgordonright17:31
kfox1111I was thinking the same thing earlier. If we want to be able to support downloading a set of artifacts that are dependencies of the app the user wants to launch, we proabably need some versioning stuff in the entries.17:31
sgordoni just wonder if the user cares17:31
sgordonor do they just want the most up to date entry always17:31
docaedolike new murano asset with associated bits, gets a change -17:31
docaedosgordon: I think that's a good point, user shouldn't care17:31
kfox1111no, often users do care. :/17:31
docaedoand until we have a more complicated back end, probably not worth spending much time/thought on this17:31
sgordonit depends on the class of user17:31
*** nbouthors has joined #openstack-meeting-317:32
sgordonthe users who do care in my experience probably arent grabbing random stuff off the web17:32
kfox1111because new software has a horible tendency to break old data/modules. :/17:32
*** vnod has joined #openstack-meeting-317:32
sgordonbut maintaining their own catalog17:32
*** sdake_ has joined #openstack-meeting-317:32
kfox1111people tend not to care, until they do. :/17:32
sgordonmaybe a problem worth punting, not sure17:32
docaedokfox1111: I don't see where people are going to turn to app catalog as an update though, would they?17:32
kfox1111ok punting for now, but I think we'll see it come back eventually.17:32
sgordonright17:32
docaedoyeah, agree with punting17:32
sgordonatm for all classes17:32
sgordonyou have to pull the entire thing again17:33
sgordonthere is no update in place as such17:33
docaedolets move on, spend just a few minutes on the next topic:17:33
docaedo#topic Discussion: ideas for getting more contributors involved?17:33
*** openstack changes topic to "Discussion: ideas for getting more contributors involved? (Meeting topic: app-catalog)"17:33
kztsv_mbpsry, what's punting? +) are we postponing the issue for now?17:33
docaedoyes, postponing the issue for now, but not forgetting about it :)17:33
kfox1111oh. sorry. yeah, postponing.17:34
kztsv_mbpok. anyway with flat yaml I can't imagine a feasible way to version things17:34
docaedoSo just wanted basically a few quick thoughts on how we can get more people interested and involved, all of which will likely lead to work on mailing lists or something (but17:34
sgordonmmm well you could but you'd basically have to keep all versions of each entry17:34
sgordonplus versioning in a separate field, fairly manual and prone to error17:35
docaedoI want to get more feedback from you all on that topic)17:35
sgordonanyway...17:35
kfox1111yeah.17:35
sgordonwell i think the conversations on the dev list are a good start at drumming up some interest17:35
sgordone.g. the solum lang packs thing that came up17:35
kfox1111distro's have very similar issues.17:35
sgordontrying to work out how to fit in with other existing efforts17:35
*** sdake has quit IRC17:36
docaedosgordon: good point, and yeah - for now maybe there's not much more to do other than keep active on ML, as for other integrations17:36
docaedowill pitch that as a topic to discuss in future meetings, kfox1111 and I have mentioned some of that on IRC17:36
*** amit213 has quit IRC17:37
*** sarob has joined #openstack-meeting-317:37
*** amit213 has joined #openstack-meeting-317:37
docaedo(but big topic - integrate with other projects, or make standalone app and horizon panel that plugs in to other projects)17:37
*** asrangne__ has quit IRC17:37
docaedoactually that topic alone should stir up a lot of conversation on ML :)17:37
sgordonyeah17:38
kfox1111Yeah, I think we've got 3 different use cases we may want to cover.17:38
ativelkovI still believe that it should be tigthly integrated with Glance Artifacts aka v317:38
sgordonit does seem to me like there is some scope for some additional UI, even though obviously murnao, heat, glance all have UI enablement of their own17:38
kfox1111* Global place to find OpenStack compatable Artifacts.17:38
docaedoI think we already moved on to next topic, perfect!17:38
docaedo#topic Discussion: other topics to cover, longer-term roadmap ideas17:38
*** openstack changes topic to "Discussion: other topics to cover, longer-term roadmap ideas (Meeting topic: app-catalog)"17:38
kztsv_mbpactually integrating with horizon would be super-nice. Imagine you have app-catalog as a source of the image in glance. And say, have autosuggestions as you type, that suggest images from app-catalog.17:38
*** zz_natorious is now known as natorious17:39
*** amit213 has quit IRC17:39
kfox1111*Single global,  Google AppStore like thing for OpenStack Clouds. Ie, user runs app, it works. no need to assemble themselves.17:39
*** amit213 has joined #openstack-meeting-317:39
kfox1111and 3,17:39
*** sarob has quit IRC17:39
kfox1111* Global repository for contributed OpenSource artifacts that can be maintaned by the community (OpenSource heat templates, for example)17:39
kfox1111kztsv_mbp: I have a bit of a prototype on my box of horizon integration. :)17:40
*** amit213 has quit IRC17:40
*** amit213 has joined #openstack-meeting-317:41
kfox1111the new angular stuff made most of it very simple.17:41
docaedoOK - so first topic for deeper discussion: integration with other projects17:41
*** kztsv_mbp has quit IRC17:42
docaedokebray wanted to cover adding additional content, want to make sure we catch that during open discussion next17:42
kfox1111+1.17:43
*** kztsv_mbp has joined #openstack-meeting-317:43
docaedobut before moving on, what other points/issues/concerns did you all have in mind, for things we need to cover in the next few weeks/months?17:43
kfox1111Would like some way to distinguish catagory #1 things from #2 things though.17:43
kfox1111A user is never going to want to launch a "solum language pack" themselves, since its just a shared library artifact.17:43
kfox1111so some tag that destinguishes "applications" from non apps would be useful.17:44
*** kztsv_ws has joined #openstack-meeting-317:44
ativelkovkfox1111: I believe that the user is not lauchning anything at all17:44
*** yamamoto has quit IRC17:44
docaedoah that's a good point - catalog is meant to be a place for "things that run on openstack", not necessarily lower level things17:45
kfox1111ativelkov: For the horizon prototype I've been working on, you'd be able to select a heat template for example, and then go right into the launch heat stack workflow.17:45
docaedolike not the right place for puppet manifests17:45
kebraydocaedo, I have to go grab food before my next meeting in 15 minutes. If there are requirements to add new things, can you hit me up on IRC later in the app-catalog channel or send email to mailing list?17:45
arunrajan+1 on Horizon plugin. I expect ability to "single click" deploy community verified apps would be useful. Curious - how to showcase credibility for templates/packages. i.e. anyway to see if other users have used and rated it high (thinking of an e-commerce shopping experience)17:45
ativelkovkfox1111: right, but that is the HEAT which runs it17:45
ativelkovso, apps are run by Murano17:45
docaedokebray: sure, will be sure to coordinate this with you on IRC or mailing list17:45
kfox1111but it is a solum (openstack) artifact, so it does make sense to go in the catalog.17:45
ativelkovImages are spawned into VMs by Nova17:45
ativelkovetc17:46
*** sarob has joined #openstack-meeting-317:46
kfox1111yeah, so lets take glance.17:46
*** absubram has joined #openstack-meeting-317:46
ativelkovThe catalog just provides artifacts for the services to consume it17:46
kfox1111there may be applience images that are "apps" that the user can simply "launch".17:46
sgordonright17:46
kfox1111there may be images that need a murano app or heat stack to be useful. the image would not be tagged as an app.17:46
kfox1111but still available so the machinery could find and download it as needed.17:47
sgordonmakes sense17:47
kfox1111so users may want to filter out all things not marked with the app tag.17:47
sgordonthere may also be cases where the image is usable standalone *and* augment via heat and/or murano usage17:47
sgordonbut an app tag would cater to that too i think17:47
*** sarob has quit IRC17:47
kfox1111sgordon: then its an app I think.17:47
sgordonright17:47
kfox1111no reason an app cant be used by another.17:48
*** amit213 has quit IRC17:48
*** amit213 has joined #openstack-meeting-317:48
sgordonsimilar situation exists as i understand it for the containerized apps on murano17:48
sgordonwhere they depend on each other17:48
ativelkovIn Artifacts Repository we distinguish artifacts and just binary assets. The image which is unusable on its own is not a standalone artifact in this point of view17:48
docaedoyep, I think the idea of tagging something as an app vs. a component makes sense to me17:48
muralia+117:48
*** rushiagr is now known as rushiagr_away17:49
sgordoni guess the existential question i have is w.r.t. the operating system images17:49
sgordonthey aren't really apps, but they are used to layer apps on17:49
sgordonsome users will want to use them directly though17:49
kfox1111yeah. they are rather gray. ubuntu is usually a building bloc, but could be considerdd an app of its own.17:49
docaedoI would say if they work standalone, they count as an app in this context17:49
sgordonyeah im ok17:49
kfox1111+1.17:50
docaedoso bigger topic here for further discussion: tagging and categorizing assets17:50
sgordonin the case of a lot of the glance images i guess mentally i think of them more as appLIANCE than appLICATION17:50
sgordon:)17:50
devkulkarnidocaedo: what do you mean by work standlone?17:50
kztsv_mbpCan't the idea seems nice, although might not apply cleanly to murano apps, as some of them can be used both as a standalone app and a component. but that makes it an app. so I might be wrong =)17:50
devkulkarnis/standlone/standalone/17:50
kfox1111slight clarification. if its a bare os image, like "Centos 7", then tag as an app.17:50
sgordonkztsv_mbp, right i think that is the same as what i was getting at above17:50
ativelkovkztsv_mbp: well, Murano packages may be class libraries17:50
sgordonkztsv_mbp, both the individual apps and their combination are an "app'17:51
kfox1111if its somethting like "centos 7 with trove guest agent", its really a component of trove and not an app.17:51
docaedodevkulkarni: I mean like a glance image that is useful on it's own, vs. a glance image that's really meant to be used by heat or murano as a base component for an application stack17:51
*** banix has quit IRC17:51
devkulkarnidocaedo: I see..17:51
muraliadocaedo: who add's these tags? in solums case, would solum add a tag to an atrifact once added to the catalog? or are these preset tags in the catalog?17:52
devkulkarnikfox1111: solum languagepacks would be bare os images.. tagging them as an app seems bit incorrect.. is the tagging system extensible?17:52
kfox1111devkulkarni: no, because there's no way to boot a bare language pack in solum I believe.17:52
docaedomuralia: my thinking is that assets are tagged by whoever adds it17:52
kfox1111you add a git repo that is your app.17:52
devkulkarniok, that makes sense17:52
devkulkarniso solum lps won't be tagged as an app. makes sense17:52
sgordondocaedo, +117:53
devkulkarnidocaedo: +117:53
sgordonuser tagging might be something we look at later but this one seems fairly fundamental as something you should know at the time you are adding the entry17:53
*** james_li has quit IRC17:53
*** amit213 has quit IRC17:53
docaedobut tagging is for next week (or mailing list this week), as the catalog is not structured to easily support that right now17:54
*** amit213 has joined #openstack-meeting-317:54
kztsv_mbp+1. if the reviewer thinks that the tag is inappropriate he will -1 the review17:54
docaedoI do see tagging as essential though for expanding the assets that the catalog can hold17:54
sgordoninded17:54
sgordon*indeed17:54
devkulkarniyes17:54
docaedobig topic, but maybe most important thing to sort next17:54
*** VW has quit IRC17:54
docaedobecause if we get it right (and we will!), makes the app catalog useful for more and more "things that run on openstack"17:55
muraliai would like extensible tags as I'm also looking at storing lots of metadata for me to search for solum LPs17:55
*** salv-orl-mobile has quit IRC17:55
muraliasuch as: give me all LPs bases on ubuntu 14.0417:55
muraliaor all LPs of type Python17:55
*** sankarshan is now known as sankarshan_away17:56
docaedomuralia: yes, also impacts ability to rate/star assets, and provide feedback about them as well - none of that works in flat yamls reviewed in gerrit17:56
*** iben has quit IRC17:56
kfox1111that brings up elastic serch... :)17:56
*** amit213 has quit IRC17:56
*** SumitNaiksatam has joined #openstack-meeting-317:56
docaedoso I'm big +1 for more metadata, but -1 if we start cramming 75-100 lines per asset, all in a handful of yaml files17:56
muralia+117:56
*** amit213 has joined #openstack-meeting-317:56
kfox1111should we install it on the server and dump all the yaml's in?17:56
kfox1111would make searching it very simple.17:57
kfox1111faceting too.17:57
docaedokfox1111: would need to see a blueprint with a way to see a POC of that I think, so we can get more eyes on it17:57
kfox1111k.17:57
docaedoseems a great idea though :)17:57
docaedo(three minutes left, and I have to jump immediately after btw)17:57
kztsv_mbpI have a really small and really unrelated topic — I would suggest we research/adopt a better UI, regarding copy-pasting the of the glance/murano name field. Currently it's 1) editable, 2) there is no copy button. If no one objects — I would like to volunteer and improve it. I have smth like gerrit or github fields in mind.17:58
muraliaone more question, will the catalog actually store the artifact, or just a pointer to glace or swift or whereever the actual artifact is stored?17:58
docaedokztsv_mbp: sounds good, want to put that in a blueprint?17:58
kztsv_mbpIt might require a flash solution, I guess there was some discussion about it on github. But in any case I feel that it really needs to be improved, as it is the UI, the user interacts with.17:59
docaedomuralia: yes I think the ultimate plane is to have catalog store the asset (think docker repository)17:59
muraliaok17:59
docaedoflash! yikes!17:59
ativelkovI want to try making a POC of running the catalog's API on Glance V317:59
kfox1111muralia: That was what I was talking about I think with use case #3. We have no such place currently.17:59
docaedowe're out of time .. but good conversation!17:59
*** ivar-lazzaro has joined #openstack-meeting-318:00
docaedolet's take the rest up on #openstack-app-catalog18:00
muraliathanks all.18:00
docaedoand I'll send update later today to ML18:00
kztsv_mbpdocaedo: ok. I think I'll be able to do it over the weekend, maybe =)18:00
docaedothanks everyone!18:00
docaedo#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Thu Jun 18 18:00:31 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-06-18-17.00.html18:00
kfox1111kztsv_mbp: I'd like to switch the ui to angular.js so we can share with horizon.18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-06-18-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-06-18-17.00.log.html18:00
*** ativelkov has left #openstack-meeting-318:00
*** mickeyspiegel has quit IRC18:00
*** ivar-lazzaro has quit IRC18:00
*** tidwellr has left #openstack-meeting-318:00
*** datsun180b has left #openstack-meeting-318:01
SumitNaiksatamivar-lazzaro: igordcard_  s3wong: hi18:01
s3wonghello18:01
igordcard_SumitNaiksatam: hello18:01
igordcard_hello all18:01
*** kfox1111 has left #openstack-meeting-318:01
*** rkukura has joined #openstack-meeting-318:01
*** ivar-lazzaro has joined #openstack-meeting-318:01
rkukurahi18:01
SumitNaiksatamrkukura: ivar-lazzaro hi18:02
ivar-lazzarohi18:02
SumitNaiksatamlets get started18:02
SumitNaiksatam#startmeeting networking_policy18:02
openstackMeeting started Thu Jun 18 18:02:19 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: networking_policy)"18:02
openstackThe meeting name has been set to 'networking_policy'18:02
*** banix has joined #openstack-meeting-318:02
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#June_18th_201518:02
SumitNaiksatam#topic Bugs18:02
*** openstack changes topic to "Bugs (Meeting topic: networking_policy)"18:02
SumitNaiksatam#link https://bugs.launchpad.net/group-based-policy/+bug/146202418:03
openstackLaunchpad bug 1462024 in Group Based Policy "Concurrent create_policy_target_group call fails" [High,Confirmed] - Assigned to Robert Kukura (rkukura)18:03
SumitNaiksatamrkukura: did you have a chance to look at the above?18:03
*** egallen has quit IRC18:03
rkukuraI have an idea what’s needed, but haven’t looked yet18:03
*** amit213 has quit IRC18:03
*** amit213 has joined #openstack-meeting-318:04
SumitNaiksatamrkukura: ok great, does this need taskflow or is there a shorter term fix?18:04
*** muralia has quit IRC18:04
*** amit213 has quit IRC18:04
*** amit213 has joined #openstack-meeting-318:05
rkukurashorter term I hope - create the implicit resources in separate transactions and make sure to use the ones that get committed18:05
SumitNaiksatamrkukura: ah ok18:05
rkukurawhoever wins18:05
ivar-lazzarorkukura: do you mean the DB creation?18:05
ivar-lazzarorkukura: or the full plugin call?18:06
*** kztsv_mbp has left #openstack-meeting-318:06
rkukuraI’m hoping its possible to suspend the current transaction while making the plugin call that creates the implicit resource18:06
*** muralia has joined #openstack-meeting-318:06
*** banix has quit IRC18:07
SumitNaiksatamrkukura: as opposed to a sub-transaction?18:07
rkukuraI think these are different - I need the create transaction to commit before the original transaction commits. Maybe subtransactions can do that, but I need to check.18:07
SumitNaiksatamrkukura: okay18:08
rkukuraThis will of course introduce new failure modes - using TaskFlow will be a better long term solution18:08
*** bpokorny has joined #openstack-meeting-318:08
SumitNaiksatamrkukura: so would you say that the ETA for this fix will be a week’s time?18:09
rkukuraOnce I finish the nova node driver, I should be able to work on this, so hopefully18:09
SumitNaiksatamrkukura: thanks18:09
*** sankarshan_away is now known as sankarshan18:10
SumitNaiksatamany other bugs that we need discuss here?18:10
rkukurayes18:11
rkukuraI don’t recall the bug number, but we’ve planned to use the new neutron subnet pool feature for our subnet allocation. Do we want to get that in our kilo release?18:11
SumitNaiksatamrkukura: yes18:12
*** amit213 has quit IRC18:12
rkukuraThis one is likely to require schema changes, so would be harder to do on a proper stable branch18:12
SumitNaiksatam#link https://bugs.launchpad.net/group-based-policy/+bug/138394718:12
openstackLaunchpad bug 1383947 in Group Based Policy "subnet mapping broken with overlapping ips" [High,Confirmed] - Assigned to Robert Kukura (rkukura)18:12
*** muralia has quit IRC18:12
*** amit213 has joined #openstack-meeting-318:12
SumitNaiksatamrkukura: i believe that one ^^^?18:12
*** sarob has joined #openstack-meeting-318:12
rkukurathat’s related, but there is a different bug focused on performance and scalability issues with the current algorithm.18:13
*** baoli has quit IRC18:13
*** sarob has quit IRC18:13
rkukura#link https://bugs.launchpad.net/group-based-policy/+bug/138214918:13
openstackLaunchpad bug 1382149 in Group Based Policy "subnet allocation does not scale" [Medium,Confirmed] - Assigned to Robert Kukura (rkukura)18:13
SumitNaiksatamrkukura: yeah just saw that too18:13
SumitNaiksatami was looking for high priority one18:13
rkukuraIts referenced in the one you linked18:13
SumitNaiksatamones18:13
*** ShillaSaebi has quit IRC18:13
SumitNaiksatamrkukura: would the usual process of migration scripts not work?18:14
*** muralia has joined #openstack-meeting-318:14
rkukuraIt would be a very difficult migration - the current allocations would need to somehow be transfered to a neutron subnet-pool.18:14
SumitNaiksatamrkukura: ah you mean data migration18:15
rkukuraMigrating just schema would be easy - migtrating data would be practically impossible18:15
*** egallen has joined #openstack-meeting-318:15
rkukuraAnd I’d prefer not to have to maintain both mechanisms (i.e. as a driver)18:15
SumitNaiksatamrkukura: agree18:15
SumitNaiksatamrkukura: perhaps we can do some investigation and see if it is going to affect any users18:16
rkukuraI’m thinking this might be higher priority to get in before kilo is released than the race condition we were just discussing, which should not have migration issues18:16
SumitNaiksatamrkukura: okay18:16
*** VW has joined #openstack-meeting-318:17
rkukuraI’ll try to protoype it at least ASAP18:17
SumitNaiksatamrkukura: perhaps good to have the patch in the master posted, and we can subsequently make a call on how to handle the backport18:17
rkukurajust to make sure the neutron feature is really usable18:17
*** sarob has joined #openstack-meeting-318:17
SumitNaiksatamrkukura: okay18:18
rkukurawhen do we create the stable/kilo branch?18:18
rkukuraThis cannot be backported to juno because the subnet-pools aren’t in juno18:18
*** bpokorny_ has joined #openstack-meeting-318:18
SumitNaiksatamrkukura: the original plan has been the end of this month18:18
*** amotoki_ has joined #openstack-meeting-318:18
SumitNaiksatamrkukura: ah okay18:18
*** amit213 has quit IRC18:19
ivar-lazzaroalternatively we could push this to Liberty that we already know will be incompatible with former releases18:19
SumitNaiksatamrkukura: perhaps we can investigate if we can make the logic configurable18:19
*** amit213 has joined #openstack-meeting-318:19
rkukuraSumitNaiksatam: That would be needed if we want to implement after releasing our kilo, but I think we can get in in by then18:20
*** devkulkarni has quit IRC18:20
*** bpokorny has quit IRC18:21
SumitNaiksatamrkukura: thanks for bringing that up18:21
SumitNaiksatamany other bugs that we need to discuss today18:21
*** sarob has quit IRC18:22
SumitNaiksatam#topic Functional/Integration tests18:22
*** openstack changes topic to "Functional/Integration tests (Meeting topic: networking_policy)"18:22
SumitNaiksatamis jishnu here?18:22
SumitNaiksatami believe he is doing some refactoring for making it easy for others to add tests18:23
rkukuraThis would be useful for an end-to-end nova node driver test18:23
*** singleth_ has joined #openstack-meeting-318:23
*** amotoki_ has quit IRC18:23
SumitNaiksatamrkukura: true18:23
rkukurafor now, a devstack exercise seems the only option, or am I missing something?18:24
SumitNaiksatamrkukura: that is the easier one to do18:24
*** Yi_ has joined #openstack-meeting-318:24
SumitNaiksatamrkukura: and provides reasonable coverage at least with sanity testing the basic workflow18:25
Yi_hi18:25
rkukuraSumitNaiksatam: I’ll stick with that for now18:25
SumitNaiksatamYi_: hi!18:25
SumitNaiksatamrkukura: ok18:25
SumitNaiksatamthere were some failures on teh integration job yesterday18:25
SumitNaiksatamwhat now seems like transient, since after repeated rechecking all patches are passing (on the stable/juno patch)18:26
*** jishnu has joined #openstack-meeting-318:26
SumitNaiksatamivar-lazzaro: i believe you didnt change anything on the patches, right?18:26
jishnuhi18:26
*** amit213 has quit IRC18:26
ivar-lazzaroSumitNaiksatam: right18:26
SumitNaiksatamjishnu: hi18:26
*** singlethink has quit IRC18:26
*** amit213 has joined #openstack-meeting-318:27
SumitNaiksatamivar-lazzaro: ok18:27
ivar-lazzaroSumitNaiksatam: I didn't notice they fixed themselves!18:27
ivar-lazzaroOur code is smarter than us. Scary18:27
SumitNaiksatamivar-lazzaro: :-)18:27
*** elmiko has quit IRC18:27
SumitNaiksatammagesh rechecked everything in the morning, and they all seem to be passing now18:27
*** jtomasek has quit IRC18:28
SumitNaiksatami noticed that his patch was failing yesterday on a completely different error (related to passwords)18:28
*** mas939 has joined #openstack-meeting-318:28
SumitNaiksatami did some refactoring on the gate hook script yesterday to make it more robust to errors18:28
SumitNaiksatamso the expectation is that even if stack.sh fails, the logs from the openstack services will now be archived18:29
SumitNaiksatamwe will know when something fails if this works correctly ;-P18:29
SumitNaiksatamjishnu: joined in the nick of time :-)18:29
rkukuraSumitNaiksatam: nice18:29
*** amit213 has quit IRC18:30
*** amit213 has joined #openstack-meeting-318:30
SumitNaiksatamjishnu:  i believe you are making updates to the gbpfunc test package?18:30
SumitNaiksatamany update/guidance for the team?18:30
*** VW has quit IRC18:30
*** mas939 has quit IRC18:31
jishnuYes they are done... in that I have not added new testcases, only the structuring of the suite has been changed... I was planning to add two more testcases, but backed it out18:31
*** amit213 has quit IRC18:31
SumitNaiksatamjishnu: any ETA on some high level document/wiki page on this?18:32
SumitNaiksatamjishnu: i mean how to add more tests18:32
jishnuWrt usage of the suite: Currently we should do the following18:32
*** amit213 has joined #openstack-meeting-318:32
SumitNaiksatamjishnu: lets add the info here: #link https://wiki.openstack.org/wiki/GroupBasedPolicy/Testing18:33
SumitNaiksatamand also any documentation on developing the tests18:33
*** amit213 has quit IRC18:33
*** amit213 has joined #openstack-meeting-318:33
jishnu@Sumit: For what you are asking I need to put a wiki/doc in place and in all likeliness I can  do that around last wk of the month18:34
SumitNaiksatamjishnu: thanks, earlier would be better, but we trust that you will do whatever is possible18:35
SumitNaiksatam#topic Packaging18:35
*** openstack changes topic to "Packaging (Meeting topic: networking_policy)"18:35
jishnuSurely Sumit..18:35
SumitNaiksatamjishnu: thanks18:35
SumitNaiksatamrkukura: so the issue regarding the gbpautomation milestone package in fedora18:36
rkukuraNothing new on my end - I’d still like to update master and kilo fedora/RDO packages, but lower priority than the coding for kilo18:36
*** kozhukalov_ has quit IRC18:37
SumitNaiksatamrkukura: did you get a chance to respond to the person who raised that issue?18:37
rkukuraSumitNaiksatam: Two issues really - broken dependencies, and moving our heat add-on into their repo18:37
rkukuraI haven’t responded to Zane, but can if you’d like.18:37
SumitNaiksatamrkukura: the latter cannot be achieved retroactively for kilo18:37
*** jishnu has quit IRC18:37
rkukuraSumitNaiksatam: Good point18:37
SumitNaiksatamrkukura: i suspect he is going to send another email if we dont18:38
SumitNaiksatamrkukura: my suggestion was that we just pull that milestone package out, since i am out sure anyone is using it anymore, is that an option?18:38
rkukuraI’ll let him know I’ll fix the kilo packages ASAP, and we’ll try to do the right thing on master18:38
SumitNaiksatam*i am out -> i am not18:38
rkukuraWe haven’t packaged the milestone yet - doing so should fix the first issue18:38
*** ajmiller has quit IRC18:38
SumitNaiksatamrkukura: i mean the milestone k2 package that is perhaps causing him pain18:39
SumitNaiksatamrkukura: that will buy us some time18:39
rkukuraI don’t think we’ve ever updated to any kilo packages - still juno18:39
rkukuraI could be wrong, and will check18:40
SumitNaiksatamrkukura: okay then i am confused, why there would be an issue with juno packages18:40
SumitNaiksatamrkukura: our juno packages rely on the other openstack juno pakcages (including heat)18:40
rkukurabecause fedora is still trying to build out juno packages on fedora versions that have moved on to kilo18:40
rkukuraso there is no juno heat on fedora 21+, AFAIK, except in RDO, which is seperate from the fedora packages18:41
*** amit213 has quit IRC18:41
*** amit213 has joined #openstack-meeting-318:42
SumitNaiksatamrkukura: ok, i did not realize that older releases are not maintained in fedora18:42
rkukurafedora 20 is still getting updates, and is juno-based18:42
SumitNaiksatamrkukura: okay, so is it possible to make our juno package only fedora 20 specific, and yank it out of the 21+?18:43
*** amit213 has quit IRC18:43
SumitNaiksatamyou know what to do best here18:43
*** amit213 has joined #openstack-meeting-318:43
rkukurawe could yank from 21+, but I’d prefer to just update the packing to use our k-2 or k-318:44
SumitNaiksatamrkukura: okay, so we cant use k-2 there since that would still rely on juno18:44
SumitNaiksatamwe would need to use k-318:44
SumitNaiksatamrkukura: you can check with amit if he can help you with this18:45
rkukuraI think I’m way off on the fedora versions - juno is either 21 or 2218:45
*** yamamoto has joined #openstack-meeting-318:45
SumitNaiksatamhe can build the k-3 packages and you can post them18:45
SumitNaiksatamrkukura: okay18:45
rkukuraThe builds are done by fedora infrastructure18:45
*** VW has joined #openstack-meeting-318:45
rkukurahumans never touch the rpms, just the tarballs and spec from which they are automatically produced18:46
SumitNaiksatamrkukura: okay, so i guess we have to update the tarballs18:46
rkukuraWe can certainly use the k-2 tarballs until k-3 are ready18:47
rkukurawait, sorry - k-3 are ready, and we are working towards k-418:47
SumitNaiksatamrkukura: yeah k3 has been ready since 5/2618:47
SumitNaiksatamok 12 mins left18:48
SumitNaiksatamrkukura: thanks for the discussion here18:48
rkukuraIf I could spend a day on it, I’d update all 4 fedora packages to k-3 for the appropriate fedora versions18:48
*** jtomasek has joined #openstack-meeting-318:48
SumitNaiksatamrkukura: ok thanks18:48
SumitNaiksatamteam logistics18:48
SumitNaiksatam#topic Core reviewers18:48
*** openstack changes topic to "Core reviewers (Meeting topic: networking_policy)"18:48
SumitNaiksatamafter the summit i reached out to the then set of core reviewers to check if they were planning to be active with the reviews going forward18:49
*** muralia has quit IRC18:49
*** Sukhdev has joined #openstack-meeting-318:49
*** matrohon has joined #openstack-meeting-318:50
SumitNaiksatambased on the responses, the current set of core reviewers stands at: ivar-lazzaro, rkukura, magesh, myself, subramanyam, hemanth, s3wong18:50
*** VW has quit IRC18:50
*** amit213 has quit IRC18:50
*** yamamoto has quit IRC18:50
*** amit213 has joined #openstack-meeting-318:50
*** VW has joined #openstack-meeting-318:51
*** banix has joined #openstack-meeting-318:51
SumitNaiksatamso kevin, ronak, and banix have moved out of the core reviewers18:51
SumitNaiksatamany concerns or thoughts on the above changes?18:51
SumitNaiksatamgoing forward based on the review contributions we will add more folks (and also the outgoing cores once they get more time to review)18:53
SumitNaiksatamso thanks to everyone for their effort on the reviews18:53
ivar-lazzaro++18:54
SumitNaiksatamand especially to banix and ronak who have been the founding members on this team18:55
rkukura+218:55
*** banix has quit IRC18:56
SumitNaiksatam#topic Kilo features18:56
*** openstack changes topic to "Kilo features (Meeting topic: networking_policy)"18:56
SumitNaiksatamrunning short on time18:56
*** mattgriffin has quit IRC18:56
*** banix has joined #openstack-meeting-318:56
*** amit213 has quit IRC18:57
*** amit213 has joined #openstack-meeting-318:57
SumitNaiksatamivar-lazzaro: on #link https://review.openstack.org/179327 and #link https://review.openstack.org/166424 do you need to bring up anything, or is it a longer discusion (perhaps for #openstack-gbp)18:57
SumitNaiksatam?18:57
*** devkulkarni has joined #openstack-meeting-318:57
*** devkulkarni has left #openstack-meeting-318:57
ivar-lazzaroSumitNaiksatam: yeah on the second one18:57
ivar-lazzaroI think it's time to converge on a decision18:58
ivar-lazzarowhether we want the services to be owned by the provider or by an admin tenant :)18:58
SumitNaiksatam“Admin tenant owns service chain instances”18:58
ivar-lazzarowe could use the NSP to regulate this behavior18:58
ivar-lazzarobut we need a default nonetheless18:58
*** mwagner_afk has quit IRC18:58
SumitNaiksatamivar-lazzaro: lets check with rukhsana, magesh since they had concerns18:59
ivar-lazzaroyes18:59
SumitNaiksatami will take that as an action item18:59
ivar-lazzaroTheir concern was about single tenant services18:59
*** sridhar_ram has quit IRC18:59
ivar-lazzaroand service sharding based on tenant18:59
*** amit213 has quit IRC19:00
SumitNaiksatam“service sharding” thats a new one :-)19:00
*** amit213 has joined #openstack-meeting-319:00
SumitNaiksatamivar-lazzaro: yeah, lets follow up19:00
SumitNaiksatamwe are the hours19:00
SumitNaiksatam* hour19:00
ivar-lazzarook19:00
SumitNaiksatam#topic Open Discussion19:00
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"19:00
*** mattgriffin has joined #openstack-meeting-319:00
SumitNaiksatamigordcard_: sorry did not get time to discuss your patch19:00
SumitNaiksatamany update from mcard on the UI?19:01
igordcard_SumitNaiksatam: he's finishing the writing of his dissertation, so he's been moving slow19:01
ivar-lazzaroigordcard_: how is the steering proceeding? Let me know if anything is blocking you in the refactor19:01
igordcard_SumitNaiksatam: but he started integrating with the GBP codebase19:01
*** sridhar_ram has joined #openstack-meeting-319:02
SumitNaiksatamigordcard_: okay, lets followup on the email thread19:02
*** amit213 has quit IRC19:02
*** amit213 has joined #openstack-meeting-319:02
igordcard_ivar-lazzaro: thanks, I do not yet have relevant updates on that :(19:02
SumitNaiksatamigordcard_: per ivar-lazzaro’s comment, let us know if there is any blocker for you19:02
SumitNaiksatamokay 3 minutes over19:02
igordcard_SumitNaiksatam: ivar-lazzaro: thanks19:02
SumitNaiksatamlets carry over the discussion to -gbp19:02
rkukurathanks SumitNaiksatam!19:02
SumitNaiksatamthanks all for joining today19:02
SumitNaiksatambye!19:02
rkukurabye19:02
Yi_bye19:03
SumitNaiksatam#endmeeting19:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:03
ivar-lazzarobye19:03
openstackMeeting ended Thu Jun 18 19:03:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-06-18-18.02.html19:03
igordcard_bye all19:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-06-18-18.02.txt19:03
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2015/networking_policy.2015-06-18-18.02.log.html19:03
*** rkukura has left #openstack-meeting-319:03
*** amit213 has quit IRC19:04
*** amit213 has joined #openstack-meeting-319:04
*** iben has joined #openstack-meeting-319:05
*** amit213 has quit IRC19:06
*** amit213 has joined #openstack-meeting-319:06
*** Piet has quit IRC19:07
*** Yi_ has quit IRC19:07
*** amit213 has quit IRC19:08
*** Yi_ has joined #openstack-meeting-319:08
*** amit213 has joined #openstack-meeting-319:08
*** Yi_ has quit IRC19:08
*** linkedinyou has joined #openstack-meeting-319:09
*** amit213 has quit IRC19:10
*** amit213 has joined #openstack-meeting-319:10
*** Yi_ has joined #openstack-meeting-319:12
*** huichun has quit IRC19:13
*** amit213 has quit IRC19:13
*** amit213 has joined #openstack-meeting-319:13
*** iben has quit IRC19:13
*** amit213 has quit IRC19:15
*** amit213 has joined #openstack-meeting-319:15
*** sdake has joined #openstack-meeting-319:17
*** banix has quit IRC19:17
*** sarob has joined #openstack-meeting-319:18
*** sdake_ has quit IRC19:21
*** amit213 has quit IRC19:22
*** amit213 has joined #openstack-meeting-319:22
*** uschreiber_ has joined #openstack-meeting-319:23
*** sarob has quit IRC19:23
*** amit213 has quit IRC19:24
*** amit213 has joined #openstack-meeting-319:24
*** banix has joined #openstack-meeting-319:25
*** uschreiber_ has quit IRC19:25
*** amit213 has quit IRC19:26
*** amit213 has joined #openstack-meeting-319:26
*** mrunge has quit IRC19:26
*** Piet has joined #openstack-meeting-319:30
*** sarob has joined #openstack-meeting-319:31
*** ttrifonov is now known as zz_ttrifonov19:31
*** sridhar_ram1 has joined #openstack-meeting-319:32
*** sdake_ has joined #openstack-meeting-319:33
*** amit213 has quit IRC19:33
*** amit213 has joined #openstack-meeting-319:33
*** sridhar_ram has quit IRC19:34
*** arunrajan has left #openstack-meeting-319:35
*** sdake has quit IRC19:36
*** sridhar_ram1 has quit IRC19:36
*** Yi_ has quit IRC19:39
*** Yi_ has joined #openstack-meeting-319:40
*** amit213 has quit IRC19:40
*** amit213 has joined #openstack-meeting-319:41
*** vgridnev has joined #openstack-meeting-319:41
*** Yi_ has quit IRC19:42
*** Yi_ has joined #openstack-meeting-319:42
*** Longgeek_ has quit IRC19:43
*** amit213 has quit IRC19:44
*** amit213 has joined #openstack-meeting-319:44
*** amit213 has quit IRC19:47
*** amit213 has joined #openstack-meeting-319:47
*** sdake has joined #openstack-meeting-319:47
*** baoli has joined #openstack-meeting-319:50
*** sdake_ has quit IRC19:51
*** singlethink has joined #openstack-meeting-319:51
*** mattgriffin has quit IRC19:52
*** mattgriffin has joined #openstack-meeting-319:54
*** iben has joined #openstack-meeting-319:54
*** amit213 has quit IRC19:54
*** amit213 has joined #openstack-meeting-319:54
*** singleth_ has quit IRC19:55
*** amit213 has quit IRC19:56
*** amit213 has joined #openstack-meeting-319:57
*** amit213 has quit IRC19:57
*** amit213 has joined #openstack-meeting-319:57
*** belmoreira has joined #openstack-meeting-319:58
*** singleth_ has joined #openstack-meeting-319:58
*** amit213 has quit IRC19:59
*** amit213 has joined #openstack-meeting-319:59
mattgriffin#startmeeting HA-Guide20:00
openstackMeeting started Thu Jun 18 20:00:27 2015 UTC and is due to finish in 60 minutes.  The chair is mattgriffin. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: HA-Guide)"20:00
openstackThe meeting name has been set to 'ha_guide'20:00
*** iben has quit IRC20:00
mattgriffinWho's here for the HA Guide meeting?20:00
*** armax has quit IRC20:01
*** amit213 has quit IRC20:01
*** baoli has quit IRC20:01
*** amit213 has joined #openstack-meeting-320:01
mattgriffinmegm, howdy20:01
*** singlethink has quit IRC20:01
megmGreetings and salutations!20:01
mattgriffin:)20:02
*** baoli has joined #openstack-meeting-320:02
*** katomo has joined #openstack-meeting-320:02
mattgriffinkatomo, here for the HA Guide meeting?20:02
mattgriffinbaoli, ^ also?20:03
*** amit213 has quit IRC20:03
*** amit213 has joined #openstack-meeting-320:03
katomomattgriffin: I think so20:03
mattgriffin:)20:03
mattgriffinexcellent...20:04
mattgriffinhere's our agenda for today:20:04
mattgriffin#link https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting20:04
katomoHello, I'm KATO Tomoyuki.20:05
*** amit213 has quit IRC20:05
*** amit213 has joined #openstack-meeting-320:05
mattgriffinmegm, had an idea in the last meeting to start this spreadsheet - keep track of progress, identify roles/responsibilities, help recruiting experts, and tell all when content is progressing20:05
mattgriffinhere's the spreadsheet:20:05
mattgriffin#link https://docs.google.com/spreadsheets/d/17EApMTVzCgddR62ZYJC4qAs9imdZWDcSy81UNEae8WY/edit#gid=020:05
*** Shamail has joined #openstack-meeting-320:06
mattgriffinkatomo, please feel free to add your name in spots for "Writer(s)" or "SME(s)"20:06
megmHi, Kato!20:06
mattgriffinhi Shamail ... just going through the agenda - https://wiki.openstack.org/wiki/Documentation/HA_Guide_Update#Next_Meeting20:06
*** natorious is now known as zz_natorious20:07
*** markmcclain has quit IRC20:07
*** amit213 has quit IRC20:07
ShamailHi mattgriffin, megm, everyone!20:07
*** amit213 has joined #openstack-meeting-320:07
megmWelcome, Shamail!  Thanks for the reviews!20:07
mattgriffinso i'm going to make an action item for all to add their names to Writer and SME where they see fit20:07
mattgriffin#action Add your name to Writer and SME column in the tracking spreadsheet - https://docs.google.com/spreadsheets/d/17EApMTVzCgddR62ZYJC4qAs9imdZWDcSy81UNEae8WY/edit#gid=020:07
ShamailYou're welcome megm, sorry for not taking the initiative on my own.20:08
*** markmcclain has joined #openstack-meeting-320:08
megmShamail, you've been busy ;-)20:08
Shamailmattgriffin: can you clarify what line #20 represents?20:08
*** amit213 has quit IRC20:08
Shamail(In the spreadsheet)20:08
megmMeg is guilty for lines 19 and 20...20:09
mattgriffinmegm, for content that is "Merged" in the RST Conversion column, is it ready for people to really dig into the content and fix and improve?20:09
*** amit213 has joined #openstack-meeting-320:09
*** reed has quit IRC20:09
megmI'm looking for a technical person to own the "flow" of information for configuring HA on the Controller and Storage nodes.20:09
*** lblanchard has quit IRC20:09
ShamailGot it.  Thanks megm20:10
megmThis is separate (but could be the same person) from ensuring that the RabbitMQ or Pacemaker piece is accurate and complete20:10
mattgriffinmegm, just added a note to the spreadsheet about this ^20:10
megmThe order of things for Controller seems particularly fraught...20:10
megmmattgriffin, yes, content that is Merged is ready for digging into20:11
megmI'm hoping we'll have a lot more pieces in that category in the next few days.20:11
*** reed has joined #openstack-meeting-320:11
megmAnyone with technical knowledge who doesn't like to write or isn't comfortable with RST, sign up as an SME and request a writer.20:13
*** matrohon has quit IRC20:13
megmI'm available.  Kato, are you also open to such invitations?20:13
mattgriffinmegm, what's the link again for this test version of the merged content?20:13
katomook20:14
mattgriffinnot really "test" ... just merged :)20:14
megmhttp://docs.openstack.org/draft/ha-guide/index.html20:14
*** banix has quit IRC20:15
*** amit213 has quit IRC20:16
*** puranamr has quit IRC20:16
*** sarob has quit IRC20:16
*** amit213 has joined #openstack-meeting-320:16
megmTo see the CRs awaiting review, associated bugs, etc, see our Crude Project Plan https://etherpad.openstack.org/p/openstack-haguide-update-next-steps20:17
mattgriffinso the major things i wanted cover in this meeting were sharing this spreadsheet, asking you guys to recruit SMEs, to review RST sections that are ready for content review (see row 6), and to remind everyone (including myself) to keep reviewing the RST review proposals that megm is producing20:17
mattgriffinthanks megm ... yeah. that's a great list to focus on for reviews20:17
mattgriffinlast week i made a draft timeline which I need to update ...20:18
mattgriffin#action mattgriffin update timeline20:18
mattgriffinany other things to discuss or questions?20:19
megmKato and I continue with the conversions.  If you are interested in a section that is not yet converted, let me know and I'll prioritize that section so you can get to work.20:19
*** puranamr has joined #openstack-meeting-320:19
mattgriffinmegm, ok20:19
katomo:)20:19
mattgriffinif there's nothing else then i think we can wrap up20:20
mattgriffinthe meeting20:20
*** sarob has joined #openstack-meeting-320:20
*** iben has joined #openstack-meeting-320:20
megmAny questions from new people?20:20
katomonone20:21
mattgriffinShamail, any questions?20:21
ShamailI'm good20:21
ShamailI plan to start reviewing actual content for storage next week20:21
mattgriffinexcellent20:22
mattgriffinthen i'm going to end the meeting20:22
mattgriffinthanks for everyone's help20:22
megmPacemaker conversion is almost done; I expect to have more pieces done in the next few days -20:22
megmThanks all!20:22
mattgriffinok20:22
katomothanks, all20:22
mattgriffinhave a great morning/day/evening (depending on where you are located)20:22
mattgriffin#endmeeting20:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:23
openstackMeeting ended Thu Jun 18 20:22:59 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:23
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-06-18-20.00.html20:23
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-06-18-20.00.txt20:23
openstackLog:            http://eavesdrop.openstack.org/meetings/ha_guide/2015/ha_guide.2015-06-18-20.00.log.html20:23
megmThanks, kato -- it's the middle of the night for you, no?20:23
*** amit213 has quit IRC20:23
katomo5 a.m. JST20:23
*** amit213 has joined #openstack-meeting-320:23
katomoverrrrry sleepy20:23
*** puranamr has quit IRC20:24
*** puranamr has joined #openstack-meeting-320:24
*** jtomasek has quit IRC20:25
*** amit213 has quit IRC20:25
*** amit213 has joined #openstack-meeting-320:25
*** Shamail has quit IRC20:26
*** mwagner_afk has joined #openstack-meeting-320:26
*** baoli has quit IRC20:27
*** puranamr has quit IRC20:28
*** baoli has joined #openstack-meeting-320:28
*** iben has quit IRC20:31
*** katomo has quit IRC20:31
*** mattgriffin has quit IRC20:31
*** mickeys has joined #openstack-meeting-320:32
*** amit213 has quit IRC20:32
*** amit213 has joined #openstack-meeting-320:32
*** sarob has quit IRC20:38
*** sarob has joined #openstack-meeting-320:39
*** amit213 has quit IRC20:39
*** amit213 has joined #openstack-meeting-320:40
*** sarob has quit IRC20:40
*** puranamr has joined #openstack-meeting-320:41
*** radek__ has joined #openstack-meeting-320:41
*** amit213 has quit IRC20:41
*** amit213 has joined #openstack-meeting-320:41
*** sambetts has quit IRC20:43
*** puranamr has quit IRC20:43
*** Longgeek has joined #openstack-meeting-320:44
*** belmoreira has quit IRC20:45
*** sridhar_ram has joined #openstack-meeting-320:45
*** sambetts has joined #openstack-meeting-320:46
*** stevemar has quit IRC20:48
*** amit213 has quit IRC20:48
*** MarkAtwood has quit IRC20:48
*** fallenpegasus has quit IRC20:48
*** amit213 has joined #openstack-meeting-320:49
*** Sukhdev has quit IRC20:49
*** sarob has joined #openstack-meeting-320:50
*** amit213 has quit IRC20:51
*** puranamr has joined #openstack-meeting-320:51
*** amit213 has joined #openstack-meeting-320:51
*** Youcef has quit IRC20:52
*** etoews has quit IRC20:53
*** amit213 has quit IRC20:53
*** amit213 has joined #openstack-meeting-320:53
*** puranamr has quit IRC20:54
*** shwetaap has quit IRC20:54
*** puranamr has joined #openstack-meeting-320:54
*** radek__ has quit IRC20:54
*** amit213 has quit IRC20:55
*** amit213 has joined #openstack-meeting-320:55
*** puranamr has quit IRC20:58
*** e0ne has joined #openstack-meeting-320:59
*** mickeyspiegel has joined #openstack-meeting-321:00
*** mickeys has quit IRC21:00
*** mwang2 has joined #openstack-meeting-321:02
*** amit213 has quit IRC21:02
*** amit213 has joined #openstack-meeting-321:02
*** sarob has quit IRC21:05
*** amit213 has quit IRC21:09
*** amit213 has joined #openstack-meeting-321:10
*** Yi_ has quit IRC21:11
*** amit213 has quit IRC21:12
*** amit213 has joined #openstack-meeting-321:13
*** etoews has joined #openstack-meeting-321:13
*** linkedinyou has quit IRC21:13
*** sarob has joined #openstack-meeting-321:13
*** puranamr has joined #openstack-meeting-321:14
*** amit213 has quit IRC21:15
*** amit213 has joined #openstack-meeting-321:15
*** shwetaap has joined #openstack-meeting-321:15
*** kebray has quit IRC21:15
*** amit213 has quit IRC21:16
*** amit213 has joined #openstack-meeting-321:16
*** puranamr has quit IRC21:17
*** baoli has quit IRC21:17
*** amit213 has quit IRC21:17
*** amit213 has joined #openstack-meeting-321:18
*** baoli has joined #openstack-meeting-321:18
*** Longgeek has quit IRC21:19
*** amit213 has quit IRC21:19
*** amit213 has joined #openstack-meeting-321:20
*** sbalukoff has quit IRC21:24
*** peristeri has quit IRC21:25
*** amit213 has quit IRC21:26
*** amit213 has joined #openstack-meeting-321:27
*** puranamr has joined #openstack-meeting-321:29
*** amit213 has quit IRC21:29
*** amit213 has joined #openstack-meeting-321:30
*** safchain has quit IRC21:31
*** muralia has joined #openstack-meeting-321:32
*** amit213 has quit IRC21:32
*** amit213 has joined #openstack-meeting-321:33
*** amit213 has quit IRC21:35
*** amit213 has joined #openstack-meeting-321:35
*** sbalukoff has joined #openstack-meeting-321:36
*** jckasper has quit IRC21:37
*** amit213 has quit IRC21:37
*** puranamr has quit IRC21:38
*** amit213 has joined #openstack-meeting-321:38
*** amit213 has quit IRC21:38
*** amit213 has joined #openstack-meeting-321:38
*** iben has joined #openstack-meeting-321:39
*** puranamr has joined #openstack-meeting-321:39
*** puranamr has quit IRC21:43
*** amit213 has quit IRC21:45
*** amit213 has joined #openstack-meeting-321:45
*** amit213 has quit IRC21:46
*** amit213 has joined #openstack-meeting-321:46
*** singlethink has joined #openstack-meeting-321:46
*** julim has quit IRC21:47
*** amit213 has quit IRC21:49
*** amit213 has joined #openstack-meeting-321:49
*** john-davidge has quit IRC21:49
*** singleth_ has quit IRC21:50
*** amit213 has quit IRC21:51
*** puranamr has joined #openstack-meeting-321:51
*** amit213 has joined #openstack-meeting-321:51
*** bknudson has quit IRC21:54
*** iben has quit IRC21:55
*** jgrimm is now known as zz_jgrimm21:55
*** amit213 has quit IRC21:57
*** amit213 has joined #openstack-meeting-321:57
*** amit213 has quit IRC21:57
*** vgridnev has quit IRC21:58
*** amit213 has joined #openstack-meeting-321:58
*** armax has joined #openstack-meeting-321:59
*** kebray has joined #openstack-meeting-322:00
*** kebray has quit IRC22:01
*** amit213 has quit IRC22:01
*** amit213 has joined #openstack-meeting-322:02
*** kebray has joined #openstack-meeting-322:02
*** Swami has joined #openstack-meeting-322:05
*** puranamr has quit IRC22:06
*** baoli has quit IRC22:07
*** kebray has quit IRC22:08
*** amit213 has quit IRC22:08
*** amit213 has joined #openstack-meeting-322:08
*** kebray has joined #openstack-meeting-322:10
*** puranamr has joined #openstack-meeting-322:13
*** Swami has quit IRC22:13
*** amit213 has quit IRC22:15
*** amit213 has joined #openstack-meeting-322:15
*** amit213 has quit IRC22:17
*** amit213 has joined #openstack-meeting-322:17
*** amit213 has quit IRC22:18
*** amit213 has joined #openstack-meeting-322:18
*** mpmsimo has quit IRC22:20
*** amit213 has quit IRC22:26
*** amit213 has joined #openstack-meeting-322:26
*** amit213 has quit IRC22:28
*** amit213 has joined #openstack-meeting-322:28
*** jckasper has joined #openstack-meeting-322:29
*** singlethink has quit IRC22:30
*** e0ne has quit IRC22:31
*** radek_ has quit IRC22:32
*** amit213 has quit IRC22:34
*** sridhar_ram has quit IRC22:34
*** amit213 has joined #openstack-meeting-322:34
*** sridhar_ram has joined #openstack-meeting-322:34
*** muralia has quit IRC22:37
*** puranamr has quit IRC22:39
*** amit213 has quit IRC22:41
*** amit213 has joined #openstack-meeting-322:41
*** doug-fish has left #openstack-meeting-322:41
*** mickeyspiegel has quit IRC22:43
*** davidlenwell is now known as david_lenwell22:44
*** amit213 has quit IRC22:44
*** david_lenwell is now known as davidlenwell22:44
*** amit213 has joined #openstack-meeting-322:44
*** sigmavirus24 is now known as sigmavirus24_awa22:44
*** amit213 has quit IRC22:46
*** amit213 has joined #openstack-meeting-322:46
*** sarob_ has joined #openstack-meeting-322:47
*** absubram has quit IRC22:47
*** absubram has joined #openstack-meeting-322:48
*** amit213 has quit IRC22:48
*** sarob has quit IRC22:48
*** amit213 has joined #openstack-meeting-322:48
*** kevinbenton has quit IRC22:48
*** TheJulia has quit IRC22:50
*** kevinbenton has joined #openstack-meeting-322:51
*** amit213 has quit IRC22:51
*** amit213 has joined #openstack-meeting-322:51
*** esp has left #openstack-meeting-322:51
*** yamamoto has joined #openstack-meeting-322:53
*** jckasper has quit IRC22:55
*** markvoelker_ has quit IRC22:55
*** tellesnobrega has quit IRC22:55
*** jklare_ has quit IRC22:55
*** mohankumar has quit IRC22:55
*** jwang has quit IRC22:55
*** alazarev has quit IRC22:55
*** B_Smith has quit IRC22:55
*** VW has quit IRC22:55
*** amit213 has quit IRC22:55
*** amit213 has joined #openstack-meeting-322:56
*** sdake_ has joined #openstack-meeting-322:57
*** yamamoto has quit IRC22:57
*** amit213 has quit IRC22:57
*** amit213 has joined #openstack-meeting-322:57
*** amit213 has quit IRC22:58
*** amit213 has joined #openstack-meeting-322:58
*** TheJulia has joined #openstack-meeting-322:58
*** amit213 has quit IRC22:59
*** amit213 has joined #openstack-meeting-322:59
*** sridhar_ram has quit IRC23:00
*** dims_ has joined #openstack-meeting-323:01
*** amit213 has quit IRC23:01
*** sdake has quit IRC23:01
*** amit213 has joined #openstack-meeting-323:01
*** dims has quit IRC23:04
*** puranamr has joined #openstack-meeting-323:06
*** tellesnobrega has joined #openstack-meeting-323:06
*** markvoelker_ has joined #openstack-meeting-323:06
*** jklare_ has joined #openstack-meeting-323:06
*** mohankumar has joined #openstack-meeting-323:06
*** jwang has joined #openstack-meeting-323:06
*** alazarev has joined #openstack-meeting-323:06
*** B_Smith has joined #openstack-meeting-323:06
*** amit213 has quit IRC23:07
*** amit213 has joined #openstack-meeting-323:07
*** sdake_ is now known as sdake23:08
*** amit213 has quit IRC23:08
*** amit213 has joined #openstack-meeting-323:08
*** puranamr has quit IRC23:09
*** amit213 has quit IRC23:10
*** amit213 has joined #openstack-meeting-323:10
*** amit213 has quit IRC23:11
*** amit213 has joined #openstack-meeting-323:12
*** amit213 has quit IRC23:12
*** amit213 has joined #openstack-meeting-323:12
*** amit213 has quit IRC23:14
*** puranamr has joined #openstack-meeting-323:14
*** amit213 has joined #openstack-meeting-323:14
*** amit213 has quit IRC23:15
*** amit213 has joined #openstack-meeting-323:15
*** zhenguo has joined #openstack-meeting-323:16
*** Longgeek has joined #openstack-meeting-323:16
*** amit213 has quit IRC23:17
*** mpavlase has quit IRC23:18
*** alexpilotti has quit IRC23:19
*** yamamoto has joined #openstack-meeting-323:20
*** yamamoto has quit IRC23:24
*** markvoelker_ has quit IRC23:26
*** puranamr has quit IRC23:28
*** puranamr has joined #openstack-meeting-323:29
*** mwang2 has quit IRC23:29
*** Longgeek has quit IRC23:34
*** puranamr has quit IRC23:35
*** puranamr has joined #openstack-meeting-323:36
*** banix has joined #openstack-meeting-323:42
*** sridhar_ram has joined #openstack-meeting-323:46
*** iben has joined #openstack-meeting-323:47
*** absubram has quit IRC23:49
*** dims_ has quit IRC23:53
*** SumitNaiksatam has quit IRC23:56
*** SumitNaiksatam has joined #openstack-meeting-323:56
*** shwetaap has quit IRC23:58
*** shwetaap has joined #openstack-meeting-323:58
*** sarob_ has quit IRC23:59
*** sarob has joined #openstack-meeting-323:59

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