Thursday, 2014-05-29

*** rbowen has joined #openstack-meeting00:00
*** Qiming has quit IRC00:01
*** tomoe_ has quit IRC00:01
*** Leonr has quit IRC00:02
*** Penick has joined #openstack-meeting00:03
*** IlyaE has joined #openstack-meeting00:05
*** leeantho has quit IRC00:08
*** sushils has quit IRC00:08
*** julim has quit IRC00:09
*** Mandell has quit IRC00:10
*** fnaval has joined #openstack-meeting00:12
*** zdiN0bot has joined #openstack-meeting00:13
*** Mandell has joined #openstack-meeting00:14
*** Mandell has quit IRC00:15
*** zdiN0bot has quit IRC00:16
*** zdiN0bot has joined #openstack-meeting00:16
*** arunkant has quit IRC00:16
*** lcheng_ has quit IRC00:19
*** lcheng_ has joined #openstack-meeting00:19
*** Mandell has joined #openstack-meeting00:19
*** tomoe__ has quit IRC00:20
*** tomoe_ has joined #openstack-meeting00:20
*** sushils has joined #openstack-meeting00:22
*** matsuhashi has joined #openstack-meeting00:22
*** jjmb has joined #openstack-meeting00:22
*** eguz has joined #openstack-meeting00:28
*** eguz has quit IRC00:28
*** sunrenjie6 has joined #openstack-meeting00:30
*** Penick has quit IRC00:31
*** eghobo has quit IRC00:33
*** tomoe__ has joined #openstack-meeting00:34
*** catohornet has joined #openstack-meeting00:35
*** colinmcnamara has quit IRC00:35
*** Penick has joined #openstack-meeting00:35
*** Penick has quit IRC00:36
*** tomoe_ has quit IRC00:37
*** jtomasek has quit IRC00:38
*** chuckC has quit IRC00:38
*** gokrokve has joined #openstack-meeting00:38
*** yamahata has joined #openstack-meeting00:41
*** chuckC has joined #openstack-meeting00:42
*** rakhmerov has joined #openstack-meeting00:42
*** gokrokve has quit IRC00:42
*** lcheng_ has quit IRC00:43
*** banix has joined #openstack-meeting00:43
*** ramishra has joined #openstack-meeting00:45
*** baoli has quit IRC00:46
*** baoli has joined #openstack-meeting00:46
*** crc32 has quit IRC00:47
*** chuckC has quit IRC00:47
*** bdpayne has quit IRC00:47
*** rbowen has quit IRC00:48
*** Mandell has quit IRC00:50
*** nati_ueno has quit IRC00:50
*** tomoe__ has quit IRC00:52
*** tomoe_ has joined #openstack-meeting00:53
*** rakhmerov has quit IRC00:55
*** zz_pablosan is now known as pablosan00:55
*** vikasd has quit IRC00:55
*** TravT has quit IRC00:56
*** saurabhs has quit IRC00:58
*** saurabhs has joined #openstack-meeting00:58
*** Qiming has joined #openstack-meeting00:59
*** devlaps has quit IRC00:59
*** davlaps has quit IRC00:59
*** Qiming_ has joined #openstack-meeting01:00
*** fifieldt has joined #openstack-meeting01:00
*** kayaliu_ has joined #openstack-meeting01:01
*** igordcard has quit IRC01:04
*** Qiming has quit IRC01:04
*** pablosan has quit IRC01:04
*** fnaval has quit IRC01:05
*** fnaval has joined #openstack-meeting01:05
*** yingjun has joined #openstack-meeting01:06
*** xwizard has quit IRC01:07
*** nelsnelson has quit IRC01:08
*** nelsnelson has joined #openstack-meeting01:08
*** baoli has quit IRC01:09
*** pablosan has joined #openstack-meeting01:11
*** shakamunyi has quit IRC01:16
*** ssurana has quit IRC01:16
*** otter768 has quit IRC01:18
*** vpanizo has quit IRC01:18
*** otter768 has joined #openstack-meeting01:19
*** otter768 has quit IRC01:20
*** otter768 has joined #openstack-meeting01:20
*** nati_ueno has joined #openstack-meeting01:21
*** marcoemorais has quit IRC01:23
*** neelashah has joined #openstack-meeting01:24
*** Edward-Zhang has quit IRC01:26
*** xuhanp has joined #openstack-meeting01:27
*** otter768 has quit IRC01:27
*** ramishra has quit IRC01:28
*** otter768 has joined #openstack-meeting01:29
*** vkmc has joined #openstack-meeting01:31
*** nati_ueno has quit IRC01:32
*** crandquist has quit IRC01:34
*** chuckC has joined #openstack-meeting01:34
*** baojg has joined #openstack-meeting01:35
*** vpanizo has joined #openstack-meeting01:41
*** gyee has quit IRC01:41
*** nati_ueno has joined #openstack-meeting01:42
*** nati_ueno has quit IRC01:42
*** coreywright_ is now known as coreywright01:42
*** yamahata has quit IRC01:43
*** yamahata has joined #openstack-meeting01:43
*** nosnos has joined #openstack-meeting01:45
*** vkmc has quit IRC01:46
*** ramishra has joined #openstack-meeting01:48
*** crandquist has joined #openstack-meeting01:49
*** gokrokve has joined #openstack-meeting01:51
*** haomaiwang has joined #openstack-meeting01:51
*** rakhmerov has joined #openstack-meeting01:52
*** gyee has joined #openstack-meeting01:54
*** saurabhs has left #openstack-meeting01:55
*** rakhmerov has quit IRC01:56
*** weshay has joined #openstack-meeting01:58
*** yaguang has joined #openstack-meeting02:00
*** elynn has left #openstack-meeting02:00
*** weshay has quit IRC02:00
*** sushils has quit IRC02:02
*** sushils has joined #openstack-meeting02:04
*** pablosan is now known as zz_pablosan02:06
*** garyduan has quit IRC02:06
*** garyduan has joined #openstack-meeting02:07
*** tomoe__ has joined #openstack-meeting02:09
*** tomoe_ has quit IRC02:12
*** sushils has quit IRC02:13
*** noslzzp has quit IRC02:13
*** sushils has joined #openstack-meeting02:14
*** zdiN0bot has quit IRC02:15
*** arnaud has quit IRC02:16
*** zdiN0bot has joined #openstack-meeting02:16
*** arnaud has joined #openstack-meeting02:16
*** Edward-Zhang has joined #openstack-meeting02:16
*** zdiN0bot has quit IRC02:16
*** sushils has quit IRC02:21
*** rossk_ has quit IRC02:24
*** xianghui has joined #openstack-meeting02:24
*** arnaud has quit IRC02:28
*** dims has quit IRC02:29
*** yingjun has quit IRC02:29
*** razec is now known as Razec02:30
*** zhiyan_ is now known as zhiyan02:34
*** SridharG has joined #openstack-meeting02:35
*** baoli has joined #openstack-meeting02:35
*** face has joined #openstack-meeting02:37
*** yingjun has joined #openstack-meeting02:37
*** face is now known as alexandra02:38
*** sld has joined #openstack-meeting02:38
*** rakhmerov has joined #openstack-meeting02:41
*** gokrokve_ has joined #openstack-meeting02:42
*** gokrokve has quit IRC02:45
*** penguinRaider has joined #openstack-meeting02:48
*** IlyaE has quit IRC02:48
*** edmund has joined #openstack-meeting02:51
*** matiu has joined #openstack-meeting02:53
*** matiu has joined #openstack-meeting02:53
*** marcoemorais has joined #openstack-meeting02:57
*** caleb_` has quit IRC02:58
*** mberlin1 has joined #openstack-meeting02:59
*** bdpayne has joined #openstack-meeting02:59
*** bdpayne has quit IRC02:59
*** bdpayne has joined #openstack-meeting02:59
*** bdpayne has quit IRC02:59
*** bdpayne has joined #openstack-meeting03:00
*** matsuhashi has quit IRC03:00
*** bdpayne_ has joined #openstack-meeting03:01
*** mberlin has quit IRC03:02
*** nelsnelson has quit IRC03:02
*** nelsnelson has joined #openstack-meeting03:03
*** Guest53102 has quit IRC03:03
*** Leonr has joined #openstack-meeting03:04
*** bdpayne has quit IRC03:04
*** matsuhashi has joined #openstack-meeting03:04
*** IlyaE has joined #openstack-meeting03:05
*** mattgriffin has quit IRC03:05
*** paragan has joined #openstack-meeting03:10
*** paragan has joined #openstack-meeting03:10
*** ramishra has quit IRC03:12
*** esker has quit IRC03:15
*** esker has joined #openstack-meeting03:15
*** epico has joined #openstack-meeting03:16
*** gokrokve_ has quit IRC03:25
*** bdpayne_ has quit IRC03:26
*** SridharG has quit IRC03:31
*** nosnos has quit IRC03:33
*** matsuhashi has quit IRC03:34
*** matsuhashi has joined #openstack-meeting03:35
*** SridharG has joined #openstack-meeting03:35
*** matsuhashi has quit IRC03:39
*** bdpayne has joined #openstack-meeting03:41
*** JRobinson__ has joined #openstack-meeting03:44
*** baoli has quit IRC03:44
*** eghobo has joined #openstack-meeting03:46
*** zhiyan is now known as zhiyan_03:47
*** shakamunyi has joined #openstack-meeting03:49
*** marcoemorais has quit IRC03:50
*** topol has joined #openstack-meeting03:54
*** edmund has quit IRC03:55
*** matsuhashi has joined #openstack-meeting03:56
*** xianghui has quit IRC03:57
*** yingjun has quit IRC03:58
*** Edward-Zhang has quit IRC04:03
*** MrJoshua has quit IRC04:05
*** shakamunyi has quit IRC04:05
*** baojg has quit IRC04:07
*** baojg has joined #openstack-meeting04:07
*** xianghui has joined #openstack-meeting04:09
*** zhiyan_ is now known as zhiyan04:10
*** akuznetsov has joined #openstack-meeting04:11
*** SridharG has quit IRC04:12
*** coreywright is now known as coreywright_04:14
*** xianghui has quit IRC04:14
*** lcheng_ has joined #openstack-meeting04:16
*** kayaliu_ has quit IRC04:18
*** bdpayne has quit IRC04:21
*** kayaliu_ has joined #openstack-meeting04:22
*** Qiming_ has quit IRC04:23
*** xianghui has joined #openstack-meeting04:26
*** xuhanp has quit IRC04:26
*** Edward-Zhang has joined #openstack-meeting04:33
*** garyk has quit IRC04:33
*** ramishra has joined #openstack-meeting04:36
*** harlowja_ is now known as harlowja_away04:38
*** Penick has joined #openstack-meeting04:43
*** Penick has quit IRC04:43
*** Qiming has joined #openstack-meeting04:43
*** bdpayne has joined #openstack-meeting04:45
*** nosnos has joined #openstack-meeting04:45
*** tomoe_ has joined #openstack-meeting04:46
*** tomoe_ has quit IRC04:47
*** tomoe__ has quit IRC04:49
*** alexandra has quit IRC04:50
*** zhiyan is now known as zhiyan_04:52
*** arnaud has joined #openstack-meeting04:53
*** hemna_ has joined #openstack-meeting04:55
*** Mandell has joined #openstack-meeting04:55
*** bdpayne has quit IRC04:57
*** eghobo has quit IRC04:57
*** eghobo has joined #openstack-meeting04:57
*** xiej has joined #openstack-meeting04:58
*** xiej has quit IRC04:58
*** eguz has joined #openstack-meeting04:59
*** tomoe_ has joined #openstack-meeting05:02
*** shakamunyi has joined #openstack-meeting05:03
*** eghobo has quit IRC05:03
*** oomichi has quit IRC05:03
*** oomichi has joined #openstack-meeting05:06
*** neelashah has quit IRC05:09
*** Edward-Zhang has quit IRC05:09
*** Edward-Zhang has joined #openstack-meeting05:10
*** ramishra has quit IRC05:10
*** ramishra has joined #openstack-meeting05:12
*** banix has quit IRC05:12
*** shakamunyi has quit IRC05:14
*** kayaliu_ has quit IRC05:15
*** tomoe_ has quit IRC05:16
*** ramishra has quit IRC05:16
*** cfriesen__ has quit IRC05:17
*** IlyaE has quit IRC05:20
*** xianghui has quit IRC05:23
*** haomaiwang has quit IRC05:24
*** haomaiwa_ has joined #openstack-meeting05:25
*** lcheng_ has quit IRC05:25
*** J_Robinson has joined #openstack-meeting05:26
*** JRobinson__ has quit IRC05:26
*** yogeshmehra has joined #openstack-meeting05:27
*** IlyaE has joined #openstack-meeting05:27
*** zhiyan_ is now known as zhiyan05:29
*** esker has quit IRC05:31
*** esker has joined #openstack-meeting05:32
*** ttrifonov_zZzz is now known as ttrifonov05:33
*** ttrifonov is now known as ttrifonov_zZzz05:34
*** fnaval_ has joined #openstack-meeting05:34
*** Longgeek has joined #openstack-meeting05:35
*** esker has quit IRC05:36
*** fnaval has quit IRC05:36
*** marcoemorais has joined #openstack-meeting05:37
*** marcoemorais1 has joined #openstack-meeting05:39
*** face has joined #openstack-meeting05:39
*** nelsnelson has quit IRC05:40
*** shakamunyi has joined #openstack-meeting05:40
*** face has quit IRC05:40
*** xianghui has joined #openstack-meeting05:41
*** marcoemorais has quit IRC05:41
*** haomaiwa_ has quit IRC05:42
*** haomaiwang has joined #openstack-meeting05:43
*** hemna_ has quit IRC05:44
*** Mandell has quit IRC05:44
*** haomaiw__ has joined #openstack-meeting05:47
*** lcheng_ has joined #openstack-meeting05:48
*** nshaikh has joined #openstack-meeting05:48
*** haomaiwang has quit IRC05:50
*** shakamunyi has quit IRC05:50
*** cfriesen__ has joined #openstack-meeting05:52
*** evgenyf has joined #openstack-meeting05:56
*** cfriesen__ has quit IRC05:58
*** Mandell has joined #openstack-meeting05:58
*** dstanek is now known as dstanek_zzz05:58
*** yogeshmehra has quit IRC06:01
*** Mandell has quit IRC06:02
*** Mandell has joined #openstack-meeting06:03
*** xuhanp has joined #openstack-meeting06:06
*** fnaval_ has quit IRC06:07
*** arnaud has quit IRC06:07
*** Mandell has quit IRC06:08
*** J_Robinson has quit IRC06:09
*** morganfainberg is now known as stevemar206:09
*** stevemar2 is now known as morganfainberg06:10
*** garyk has joined #openstack-meeting06:10
*** ildikov has quit IRC06:13
*** doron_afk has joined #openstack-meeting06:13
*** yogeshmehra has joined #openstack-meeting06:16
*** doron_afk is now known as doron06:17
*** _nadya_ has joined #openstack-meeting06:20
*** afazekas has quit IRC06:22
*** afazekas has joined #openstack-meeting06:22
*** fnaval has joined #openstack-meeting06:23
*** lcheng_ has quit IRC06:24
*** _nadya_ has quit IRC06:25
*** Mandell has joined #openstack-meeting06:25
*** kayaliu_ has joined #openstack-meeting06:27
*** topol has quit IRC06:27
*** HenryG has quit IRC06:27
*** stevemar has quit IRC06:31
*** jtomasek has joined #openstack-meeting06:33
*** HenryG has joined #openstack-meeting06:33
*** yogeshmehra has quit IRC06:36
*** Leonr has quit IRC06:37
*** yingjun has joined #openstack-meeting06:39
*** rickerc has quit IRC06:39
*** ttrifonov_zZzz is now known as ttrifonov06:40
*** ildikov has joined #openstack-meeting06:40
*** fnaval has quit IRC06:42
*** yogeshmehra has joined #openstack-meeting06:46
*** shakamunyi has joined #openstack-meeting06:47
*** comay has quit IRC06:47
*** ttrifonov is now known as ttrifonov_zZzz06:50
*** doron is now known as doron_afk06:52
*** shakamunyi has quit IRC06:59
*** dstanek_zzz is now known as dstanek07:00
*** fnaval has joined #openstack-meeting07:00
*** Edward-Zhang has quit IRC07:01
*** _nadya_ has joined #openstack-meeting07:01
*** rickerc has joined #openstack-meeting07:03
*** fnaval has quit IRC07:05
*** haomaiw__ has quit IRC07:05
*** haomaiwang has joined #openstack-meeting07:06
*** flaper87|afk is now known as flaper8707:06
*** ttrifonov_zZzz is now known as ttrifonov07:07
*** haomaiw__ has joined #openstack-meeting07:09
*** dstanek is now known as dstanek_zzz07:09
*** gyee has quit IRC07:10
*** IlyaE has quit IRC07:10
*** vpanizo has quit IRC07:11
*** yaguang has quit IRC07:11
*** tris has quit IRC07:11
*** haomaiwang has quit IRC07:12
*** salv-orlando has joined #openstack-meeting07:13
*** jlibosva has joined #openstack-meeting07:14
*** vpanizo has joined #openstack-meeting07:15
*** _nadya_ has quit IRC07:18
*** yaguang has joined #openstack-meeting07:19
*** Mandell has quit IRC07:21
*** eguz has quit IRC07:22
*** xianghui has quit IRC07:24
*** luqas has joined #openstack-meeting07:25
*** shakamunyi has joined #openstack-meeting07:25
*** bogdando has quit IRC07:26
*** bogdando has joined #openstack-meeting07:26
*** Edward-Zhang has joined #openstack-meeting07:26
*** shakamunyi has quit IRC07:36
*** Edward-Zhang_ has joined #openstack-meeting07:38
*** Edward-Zhang has quit IRC07:38
*** Edward-Zhang_ is now known as Edward-Zhang07:38
*** mrda is now known as mrda-away07:39
*** Macaveli has joined #openstack-meeting07:40
*** xuhanp has quit IRC07:41
*** pelix has joined #openstack-meeting07:41
*** xianghui has joined #openstack-meeting07:42
*** sushils has joined #openstack-meeting07:42
*** sushils has quit IRC07:47
*** sushils has joined #openstack-meeting07:49
*** xianghui has quit IRC07:50
*** morganfainberg is now known as morganfainberg_Z07:54
*** zhikunliu has joined #openstack-meeting07:55
*** sushils has quit IRC07:55
*** baojg has quit IRC07:58
*** matsuhashi has quit IRC07:58
*** lintan has quit IRC07:58
*** matsuhashi has joined #openstack-meeting07:59
*** marcoemorais1 has quit IRC08:00
*** matsuhas_ has joined #openstack-meeting08:02
*** mrmartin has joined #openstack-meeting08:02
*** xianghui has joined #openstack-meeting08:02
*** shakamunyi has joined #openstack-meeting08:03
*** kayaliu_ has quit IRC08:03
*** matsuhashi has quit IRC08:04
*** obondarev has joined #openstack-meeting08:06
*** morganfainberg_Z is now known as morganfainberg08:12
*** ArthurBerezin has joined #openstack-meeting08:12
*** ArthurBerezin has left #openstack-meeting08:13
*** shakamunyi has quit IRC08:14
*** yogeshmehra has quit IRC08:18
*** luqas has quit IRC08:18
*** kayaliu_ has joined #openstack-meeting08:24
*** samuelbercovici has joined #openstack-meeting08:24
*** derekh_ has joined #openstack-meeting08:25
*** samuelbercovici1 has joined #openstack-meeting08:27
*** baojg has joined #openstack-meeting08:28
*** sushils has joined #openstack-meeting08:28
*** samuelbercovici has quit IRC08:30
*** samuelbercovici1 is now known as samuelbercovici08:30
*** oomichi has quit IRC08:31
*** xianghui has quit IRC08:32
*** kayaliu_ has quit IRC08:32
*** samuelbercovici1 has joined #openstack-meeting08:35
*** egallen has joined #openstack-meeting08:35
*** igordcard has joined #openstack-meeting08:35
*** belmoreira has joined #openstack-meeting08:36
*** belmoreira has left #openstack-meeting08:36
*** belmoreira has joined #openstack-meeting08:36
*** samuelbercovici has quit IRC08:38
*** samuelbercovici1 is now known as samuelbercovici08:38
*** samuelbercovici1 has joined #openstack-meeting08:40
*** shakamunyi has joined #openstack-meeting08:40
*** mrmartin has quit IRC08:42
*** egallen has quit IRC08:42
*** samuelbercovici has quit IRC08:43
*** samuelbercovici1 is now known as samuelbercovici08:43
*** xianghui has joined #openstack-meeting08:44
*** egallen has joined #openstack-meeting08:45
*** jcoufal has joined #openstack-meeting08:46
*** tomoe_ has joined #openstack-meeting08:47
*** tomoe_ has quit IRC08:47
*** samuelbercovici1 has joined #openstack-meeting08:49
*** luqas has joined #openstack-meeting08:51
*** sunrenjie6 has quit IRC08:52
*** sunrenjie6 has joined #openstack-meeting08:52
*** shakamunyi has quit IRC08:52
*** samuelbercovici has quit IRC08:52
*** samuelbercovici1 is now known as samuelbercovici08:52
*** salv-orlando_ has joined #openstack-meeting08:53
*** matsuhas_ has quit IRC08:53
*** salv-orlando has quit IRC08:54
*** salv-orlando_ is now known as salv-orlando08:54
*** samuelbercovici1 has joined #openstack-meeting08:55
*** mrmartin has joined #openstack-meeting08:56
*** sunrenjie6 has quit IRC08:57
*** matsuhashi has joined #openstack-meeting08:58
*** samuelbercovici has quit IRC08:59
*** samuelbercovici1 is now known as samuelbercovici08:59
*** yingjun has quit IRC09:03
*** salv-orlando has quit IRC09:04
*** samuelbercovici1 has joined #openstack-meeting09:08
*** samuelbercovici has quit IRC09:11
*** samuelbercovici1 is now known as samuelbercovici09:11
*** samuelbercovici1 has joined #openstack-meeting09:16
*** samuelbercovici has quit IRC09:18
*** samuelbercovici1 is now known as samuelbercovici09:18
*** fnaval has joined #openstack-meeting09:18
*** ominakov has joined #openstack-meeting09:19
*** gmatefi has joined #openstack-meeting09:19
*** shakamunyi has joined #openstack-meeting09:19
*** armax has joined #openstack-meeting09:19
*** samuelbercovici1 has joined #openstack-meeting09:24
*** gmatefi has quit IRC09:26
*** samuelbercovici has quit IRC09:27
*** samuelbercovici1 is now known as samuelbercovici09:27
*** zhikunliu has quit IRC09:30
*** zhiyan is now known as zhiyan_09:30
*** shakamunyi has quit IRC09:31
*** matsuhashi has quit IRC09:33
*** matsuhashi has joined #openstack-meeting09:33
*** yingjun has joined #openstack-meeting09:33
*** matsuhashi has quit IRC09:35
*** matsuhashi has joined #openstack-meeting09:36
*** lynxman has quit IRC09:36
*** ccorrigan has joined #openstack-meeting09:37
*** lynxman has joined #openstack-meeting09:37
*** fnaval has quit IRC09:38
*** yingjun has quit IRC09:42
*** samuelbercovici1 has joined #openstack-meeting09:45
*** samuelbercovici has quit IRC09:48
*** samuelbercovici1 is now known as samuelbercovici09:48
*** belmoreira has quit IRC09:48
*** oomichi has joined #openstack-meeting09:49
*** belmoreira has joined #openstack-meeting09:51
*** samuelbercovici1 has joined #openstack-meeting09:52
*** samuelbercovici has quit IRC09:54
*** samuelbercovici1 is now known as samuelbercovici09:54
*** samuelbercovici1 has joined #openstack-meeting09:57
*** Qiming has quit IRC09:57
*** shakamunyi has joined #openstack-meeting09:58
*** samuelbercovici has quit IRC10:00
*** otter768_ has joined #openstack-meeting10:00
*** samuelbercovici1 is now known as samuelbercovici10:00
*** idegtiarov has joined #openstack-meeting10:00
*** ominakov has quit IRC10:01
*** otter768 has quit IRC10:02
*** nosnos has quit IRC10:02
*** ominakov has joined #openstack-meeting10:03
*** jtomasek has quit IRC10:03
*** samuelbercovici1 has joined #openstack-meeting10:04
*** nosnos has joined #openstack-meeting10:05
*** shakamunyi has quit IRC10:05
*** jtomasek has joined #openstack-meeting10:05
*** Edward-Zhang has quit IRC10:07
*** samuelbercovici has quit IRC10:08
*** samuelbercovici1 is now known as samuelbercovici10:08
*** jesusaurus has quit IRC10:10
*** markvan has quit IRC10:10
*** bdperkin has quit IRC10:10
*** bdperkin has joined #openstack-meeting10:10
*** jesusaurus has joined #openstack-meeting10:11
*** markvan has joined #openstack-meeting10:11
*** belmoreira has quit IRC10:13
*** tomoe_ has joined #openstack-meeting10:16
*** samuelbercovici1 has joined #openstack-meeting10:18
*** samuelbercovici has quit IRC10:21
*** samuelbercovici1 is now known as samuelbercovici10:21
*** vkmc has joined #openstack-meeting10:24
*** vkmc has quit IRC10:24
*** vkmc has joined #openstack-meeting10:24
*** xianghui has quit IRC10:25
*** samuelbercovici1 has joined #openstack-meeting10:27
*** ominakov has quit IRC10:28
*** samuelbercovici has quit IRC10:29
*** samuelbercovici1 is now known as samuelbercovici10:29
*** samuelbercovici1 has joined #openstack-meeting10:31
*** paragan has quit IRC10:33
*** samuelbercovici has quit IRC10:35
*** samuelbercovici1 is now known as samuelbercovici10:35
*** belmoreira has joined #openstack-meeting10:39
*** matsuhashi has quit IRC10:41
*** HenryG has quit IRC10:41
*** nosnos has quit IRC10:41
*** samuelbercovici1 has joined #openstack-meeting10:43
*** afazekas is now known as afazekas_sick_do10:43
*** yingjun has joined #openstack-meeting10:45
*** sgordon__ has joined #openstack-meeting10:45
*** vpanizo has quit IRC10:45
*** nosnos has joined #openstack-meeting10:45
*** nosnos has quit IRC10:46
*** samuelbercovici has quit IRC10:47
*** samuelbercovici1 is now known as samuelbercovici10:47
*** nosnos has joined #openstack-meeting10:47
*** nosnos has quit IRC10:48
*** epico has quit IRC10:49
*** Mandell has joined #openstack-meeting10:49
*** Longgeek has quit IRC10:51
*** samuelbercovici1 has joined #openstack-meeting10:53
*** yingjun has quit IRC10:53
*** afazekas_sick_do has quit IRC10:53
*** Mandell has quit IRC10:53
*** Longgeek has joined #openstack-meeting10:55
*** Youcef has quit IRC10:56
*** HenryG has joined #openstack-meeting10:56
*** samuelbercovici has quit IRC10:56
*** samuelbercovici1 is now known as samuelbercovici10:56
*** Youcef has joined #openstack-meeting10:56
*** maxdml has joined #openstack-meeting10:58
*** samuelbercovici1 has joined #openstack-meeting10:58
*** Youcef_ has joined #openstack-meeting11:01
*** Youcef has quit IRC11:01
*** samuelbercovici has quit IRC11:01
*** samuelbercovici1 is now known as samuelbercovici11:01
*** Qiming has joined #openstack-meeting11:04
*** samuelbercovici1 has joined #openstack-meeting11:05
*** yingjun has joined #openstack-meeting11:06
*** yingjun has quit IRC11:06
*** yaguang has quit IRC11:06
*** yaguang has joined #openstack-meeting11:07
*** belmoreira1 has joined #openstack-meeting11:07
*** yaguang has quit IRC11:07
*** ominakov has joined #openstack-meeting11:08
*** samuelbercovici has quit IRC11:09
*** samuelbercovici1 is now known as samuelbercovici11:09
*** belmoreira has quit IRC11:09
*** Youcef_ has quit IRC11:11
*** Youcef has joined #openstack-meeting11:12
*** belmoreira1 has quit IRC11:13
*** belmoreira has joined #openstack-meeting11:13
*** belmoreira1 has joined #openstack-meeting11:14
*** belmoreira has quit IRC11:14
*** pradipta_away is now known as pradipta11:14
*** Mandell has joined #openstack-meeting11:14
*** dims has joined #openstack-meeting11:16
*** prad_ has joined #openstack-meeting11:17
*** samuelbercovici1 has joined #openstack-meeting11:18
*** Mandell has quit IRC11:19
*** deepakcs has joined #openstack-meeting11:20
*** samuelbercovici has quit IRC11:21
*** samuelbercovici1 is now known as samuelbercovici11:21
*** prad__ has joined #openstack-meeting11:22
*** prad_ has quit IRC11:22
*** baoli has joined #openstack-meeting11:23
*** igordcard_ has joined #openstack-meeting11:23
*** igordcard has quit IRC11:24
*** luqas has quit IRC11:25
*** baoli_ has joined #openstack-meeting11:26
*** baoli has quit IRC11:27
*** samuelbercovici1 has joined #openstack-meeting11:28
*** samuelbercovici1 has quit IRC11:29
*** samuelbercovici1 has joined #openstack-meeting11:29
*** Longgeek has quit IRC11:29
*** Longgeek has joined #openstack-meeting11:30
*** samuelbercovici has quit IRC11:31
*** Longgeek has quit IRC11:31
*** samuelbercovici1 is now known as samuelbercovici11:31
*** samuelbercovici1 has joined #openstack-meeting11:33
*** Longgeek has joined #openstack-meeting11:35
*** Longgeek has quit IRC11:36
*** samuelbercovici has quit IRC11:36
*** samuelbercovici1 is now known as samuelbercovici11:36
*** prad__ has quit IRC11:38
*** Longgeek has joined #openstack-meeting11:38
*** belmoreira1 has quit IRC11:41
*** samuelbercovici1 has joined #openstack-meeting11:42
*** rakhmerov has quit IRC11:43
*** salv-orlando has joined #openstack-meeting11:45
*** samuelbercovici has quit IRC11:45
*** samuelbercovici1 is now known as samuelbercovici11:46
*** Mandell has joined #openstack-meeting11:47
*** tomoe__ has joined #openstack-meeting11:48
*** samuelbercovici1 has joined #openstack-meeting11:50
*** tomoe___ has joined #openstack-meeting11:51
*** Mandell has quit IRC11:51
*** lbragstad has quit IRC11:52
*** tomoe_ has quit IRC11:52
*** baoli_ has quit IRC11:52
*** baoli has joined #openstack-meeting11:53
*** samuelbercovici has quit IRC11:53
*** samuelbercovici1 is now known as samuelbercovici11:53
*** tomoe__ has quit IRC11:53
*** bcrochet|g0ne is now known as bcrochet11:54
*** pdmars has joined #openstack-meeting11:56
*** deepakcs_ has joined #openstack-meeting11:57
*** dvy has joined #openstack-meeting11:57
*** samuelbercovici1 has joined #openstack-meeting11:58
*** samuelbercovici has quit IRC11:59
*** samuelbercovici1 is now known as samuelbercovici11:59
*** ominakov has quit IRC11:59
*** deepakcs has quit IRC12:00
*** dims has quit IRC12:00
*** prad_ has joined #openstack-meeting12:00
*** mwagner_lap has quit IRC12:02
*** ominakov has joined #openstack-meeting12:02
*** haomaiw__ has quit IRC12:04
*** maxdml has quit IRC12:04
*** haomaiwang has joined #openstack-meeting12:04
*** weshay has joined #openstack-meeting12:05
*** ArthurBerezin has joined #openstack-meeting12:05
*** ArthurBerezin has left #openstack-meeting12:07
*** salv-orlando has quit IRC12:10
*** tomoe_ has joined #openstack-meeting12:10
*** tomoe___ has quit IRC12:12
*** ArxCruz has joined #openstack-meeting12:14
*** prad_ has quit IRC12:14
*** rakhmerov has joined #openstack-meeting12:14
*** prad_ has joined #openstack-meeting12:15
*** jmh has joined #openstack-meeting12:19
*** pradipta is now known as pradipta_away12:19
*** pradipta_away is now known as pradipta12:19
*** jmh is now known as Guest9157512:19
*** rakhmerov has quit IRC12:19
*** edmund1 has joined #openstack-meeting12:21
*** haomai___ has joined #openstack-meeting12:22
*** salv-orlando has joined #openstack-meeting12:22
*** paragan has joined #openstack-meeting12:22
*** dprince has joined #openstack-meeting12:23
*** haomaiwang has quit IRC12:24
*** weshay has quit IRC12:27
*** baojg has quit IRC12:27
*** weshay has joined #openstack-meeting12:27
*** baojg has joined #openstack-meeting12:28
*** hashar has joined #openstack-meeting12:29
*** eharney has quit IRC12:29
*** fnaval has joined #openstack-meeting12:30
*** pradipta is now known as pradipta_away12:30
*** baojg has quit IRC12:32
*** doron_afk is now known as doron12:33
*** neelashah has joined #openstack-meeting12:33
*** oomichi has quit IRC12:37
*** aysyd has joined #openstack-meeting12:40
*** dstanek_zzz is now known as dstanek12:41
*** jtomasek has quit IRC12:42
*** luqas has joined #openstack-meeting12:42
*** samuelbercovici1 has joined #openstack-meeting12:46
*** doron is now known as doron_afk12:49
*** samuelbercovici has quit IRC12:49
*** samuelbercovici1 is now known as samuelbercovici12:50
*** yamahata has quit IRC12:51
*** noslzzp has joined #openstack-meeting12:52
*** jecarey has quit IRC12:53
*** jtomasek has joined #openstack-meeting12:55
*** doron_afk is now known as doron12:56
*** dstanek is now known as dstanek_zzz12:56
*** _nadya_ has joined #openstack-meeting12:58
*** miqui has joined #openstack-meeting12:58
*** doron is now known as doron_afk12:59
*** dvy has quit IRC13:00
*** fnaval_ has joined #openstack-meeting13:01
*** lbragstad has joined #openstack-meeting13:02
*** PhilD has joined #openstack-meeting13:02
*** rbowen has joined #openstack-meeting13:03
*** fnaval has quit IRC13:03
*** ArxCruz has quit IRC13:05
*** dkliban_afk has left #openstack-meeting13:06
*** ArxCruz has joined #openstack-meeting13:08
*** dstanek_zzz is now known as dstanek13:08
*** jaypipes has quit IRC13:10
*** dims has joined #openstack-meeting13:10
*** jdob has joined #openstack-meeting13:11
*** zhiyan_ is now known as zhiyan13:11
*** banix has joined #openstack-meeting13:12
*** ddieterly has joined #openstack-meeting13:13
*** rakhmerov has joined #openstack-meeting13:15
*** tvoran has joined #openstack-meeting13:15
*** prad_ has quit IRC13:15
*** jaypipes has joined #openstack-meeting13:16
*** doron_afk is now known as doron13:16
*** shakamunyi has joined #openstack-meeting13:16
*** banix has quit IRC13:16
*** shakayumi has joined #openstack-meeting13:19
*** banix has joined #openstack-meeting13:19
*** jorgem has joined #openstack-meeting13:20
*** noslzzp has quit IRC13:20
*** julim has joined #openstack-meeting13:21
*** shakamunyi has quit IRC13:21
*** vijendar has joined #openstack-meeting13:21
*** eghobo has joined #openstack-meeting13:22
*** eharney has joined #openstack-meeting13:25
*** samuelbercovici1 has joined #openstack-meeting13:25
*** coreywright_ is now known as coreywright13:25
*** elambert has quit IRC13:27
*** samuelbercovici has quit IRC13:28
*** samuelbercovici1 is now known as samuelbercovici13:28
*** ramishra has joined #openstack-meeting13:29
*** doron is now known as doron_afk13:29
*** noslzzp has joined #openstack-meeting13:30
*** fnaval_ has quit IRC13:30
*** HenryG has quit IRC13:30
*** bknudson has joined #openstack-meeting13:30
*** HenryG has joined #openstack-meeting13:31
*** jamiem has joined #openstack-meeting13:31
*** Macaveli has quit IRC13:31
*** liyuezhou_ has joined #openstack-meeting13:32
*** thomasbiege has joined #openstack-meeting13:33
*** casanch1 has joined #openstack-meeting13:33
*** coreywright is now known as coreywright_13:33
*** shakayumi has quit IRC13:34
*** rakhmerov has quit IRC13:34
*** carl_baldwin has joined #openstack-meeting13:34
*** zehicle_at_dell has joined #openstack-meeting13:38
*** ashepelev has quit IRC13:39
*** kenhui has joined #openstack-meeting13:40
*** sld has quit IRC13:41
*** Qiming has quit IRC13:42
*** banix has quit IRC13:43
*** gilliard has joined #openstack-meeting13:44
*** cammann has joined #openstack-meeting13:44
*** zz_pablosan is now known as pablosan13:44
*** yamahata has joined #openstack-meeting13:44
*** deepakcs_ has quit IRC13:44
*** pablosan has quit IRC13:44
*** pablosan has joined #openstack-meeting13:45
*** gokrokve has joined #openstack-meeting13:46
*** Beilin has joined #openstack-meeting13:46
*** weshay has quit IRC13:46
*** Longgeek has quit IRC13:48
*** shakayumi has joined #openstack-meeting13:48
*** stevemar has joined #openstack-meeting13:49
*** prad_ has joined #openstack-meeting13:49
*** Longgeek has joined #openstack-meeting13:49
*** jjmb has quit IRC13:52
*** vivek-eb_ has joined #openstack-meeting13:53
*** vivek-ebay has joined #openstack-meeting13:53
*** prad_ has quit IRC13:53
*** vivek-eb_ has left #openstack-meeting13:53
*** blogan has joined #openstack-meeting13:53
*** fnaval has joined #openstack-meeting13:55
*** IlyaE has joined #openstack-meeting13:55
*** haomai___ has quit IRC13:56
*** haomaiwang has joined #openstack-meeting13:57
*** JulianCash_ has joined #openstack-meeting13:57
*** PaulMurray has joined #openstack-meeting13:57
*** nshaikh has quit IRC13:57
enikanorov_neutron lbaas meeting in 3 minutes13:57
*** weshay has joined #openstack-meeting13:58
*** lsmola2 has joined #openstack-meeting13:59
*** aburaschi has joined #openstack-meeting13:59
*** Mandell has joined #openstack-meeting13:59
*** xgerman_ has joined #openstack-meeting13:59
enikanorov_hi13:59
enikanorov_who's online for lbaas meeting?13:59
sbalukoffHello!13:59
aburaschihello! o/13:59
*** sballe_ has joined #openstack-meeting14:00
bloganhello!14:00
vivek-ebayhi14:00
enikanorov_blogan:  rm_work: ping14:00
mesteryI have to go afk now, I'll read the scollback later folks!14:00
Youcefhi14:00
jorgemhello14:00
enikanorov_ok, looks like we have quorum14:00
sballe_morning14:00
enikanorov_#startmeeting neutron lbaas14:00
openstackMeeting started Thu May 29 14:00:27 2014 UTC and is due to finish in 60 minutes.  The chair is enikanorov_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
*** prad_ has joined #openstack-meeting14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron lbaas)"14:00
openstackThe meeting name has been set to 'neutron_lbaas'14:00
*** bbaby has joined #openstack-meeting14:00
dougwigmorning14:00
enikanorov_#link https://wiki.openstack.org/wiki/Network/LBaaS#Agenda14:00
xgerman_morning14:01
enikanorov_this is the agenda for the meeting14:01
enikanorov_blogan: do you want to give an update on the blueprint?14:01
*** PaulMurray has left #openstack-meeting14:01
blogansure14:01
*** danpb has joined #openstack-meeting14:01
*** pcm_ has joined #openstack-meeting14:01
blogani updated the BP to reflect the change to 1:M LoadBalancer to Listener14:02
*** danpb has left #openstack-meeting14:02
enikanorov_is there an agreement on N:M vs 1:M?14:02
bloganUnless there are objections to this, I assume thats the way we want to go for now at least14:02
*** jgrimm has joined #openstack-meeting14:02
vivek-ebay+1 for 1:M14:02
Youcefcan you put a link to the updated blueprint (#link)?14:02
xgerman_+1 for 1:M14:03
*** balajiiyer has joined #openstack-meeting14:03
jorgemagreed14:03
dougwig+1 1:M14:03
enikanorov_Youcef: https://review.openstack.org/#/c/89903/8/specs/juno/lbaas-api-and-objmodel-improvement.rst14:03
blogansbalukoff did wonder if we should put IPv4 and IPv6 addresses on the load balancer object14:03
*** Beilin has quit IRC14:03
bloganI'd like to get everyone's thoughts on that14:03
*** prad__ has joined #openstack-meeting14:03
*** prad_ has quit IRC14:03
*** tomoe__ has joined #openstack-meeting14:03
blogananyone have thoughts?14:04
sbalukoffI'd be for it. :)14:04
bloganlol14:04
jorgemhmm14:04
xgerman_two addresses per node or mixed adresses or both?14:04
Youcef#link  https://review.openstack.org/#/c/89903/8/specs/juno/lbaas-api-and-objmodel-improvement.rst14:04
*** prad__ is now known as prad_14:04
*** tomoe_ has quit IRC14:04
sbalukoffMixed addresses.14:04
enikanorov_i thought that was initial idea, but then we switched to single address per LB14:04
jorgemIf you wanted many ip addresses then it now seems weird if you do that14:04
*** coreywright_ is now known as coreywright14:04
sbalukoffSo, up to one IPv4 and one IPv614:04
jorgemI like single14:05
dougwigdepends on how much code it would take; i'd rather take the smallest bite that we can, and nail it.14:05
xgerman_me, too14:05
jorgemsimpler14:05
xgerman_just wanted to clarify14:05
Youcefjorgem: agree, me too14:05
*** ildikov_ has joined #openstack-meeting14:05
jorgemjust create another lb if you want IPv614:05
jamiemI agree14:05
*** Berlin has joined #openstack-meeting14:05
xgerman_+114:05
*** Mandell has quit IRC14:06
enikanorov_but then N:M may make sense14:06
YoucefIs there a type of ipaddress to know whether you are reading an IPv4 or an IPv6?14:06
bloganSo what would we miss out on if we didn't have the IPv6 on the load balancer?14:06
*** ildikov has quit IRC14:06
enikanorov_(i mean LB:Listener relation)14:06
*** haomai___ has joined #openstack-meeting14:06
*** aysyd has quit IRC14:06
bloganenikanorov_: yeah that was the main reason for that relationship14:06
*** aysyd has joined #openstack-meeting14:07
*** haomai___ has quit IRC14:07
samuelbercovicihello!14:07
sbalukoffblogan: It's more work for the user to maintain two identical listners + sub objects.14:07
*** haoma____ has joined #openstack-meeting14:07
blogansbalukoff: yes that is one big reason14:08
*** eghobo has quit IRC14:08
sbalukoffIt's also extremely common for back-ends that can do IPv6 ro be able to do both IPv4 and IPv6.14:08
samuelbercoviciI think that starting with 1:N with aim of moving to M:N is not good14:08
enikanorov_samuelbercovici: agreed.14:08
blogansamuelbercovici: what do you think about an ipv4 address and ipv6 address on the load balancer object?14:08
jorgemHaving IPv4 and IPv6 on the same lb makes sense for one use case. However, when considering the myriad of use cases (i.e. combination of single to multiple ip address) then you have an inconsistent way of doing things. For example, you could technically have 2 ways of loadbalancing 1) One lb with IPV4 and IPv6 or 2) One lb with IPV4 (IPV6 nulled out) and one with IPv6 (IPv4 nulled out). I think this becomes confusing.14:09
*** haomaiwang has quit IRC14:09
enikanorov_i think N:M should be ok. If user want advanced use case (ipv4+ipv6) its fine to let em deal with some API complexity around it (like attaching listeners to another LB)14:09
sbalukoffjorgem: I don't think it's that confusing. you've actually just listed all the possible permutations.14:09
*** thangp has joined #openstack-meeting14:09
samuelbercoviciif we take out implementaion efforts, I think that the M:N relashionship is the correct one14:10
jorgemsbalukoff: What if I wanted more than 2 ip addresses (some of customers do this and I don't know why really)14:10
blogansamuelbercovici: are you advocating we start with the M:N relationship from the beginning?14:10
samuelbercoviciblogan: yes14:11
sbalukoffI"m just having a hard time seeing many actual practical cases where N:M will actually be used other than the one IPv4 + one IPv6 case.14:11
xgerman_me, too14:11
sballe_sbalukoff: +114:11
dougwig+114:11
xgerman_and ther eis a workaround with two lbs14:11
aburaschiSorry for asking, but what would be the use case for M:N, in short words?14:11
*** topol has joined #openstack-meeting14:11
Youcefso why then do we want to go eventually to M:N? what is the use case that cannot be accomplished?14:11
*** VijayB_ has joined #openstack-meeting14:12
bloganaburashci: it allows a user to reuse a listener thats already assigned a load balancer, so they don't have to redo their configuration for a load balancer with an IPv6 vip14:12
jorgemif its edge case then I'm fine. Just wanted to see if anyone else had a strong position on it. Now that I think about it I'm not really adamant about it.14:12
bloganYoucef: If we do the IPv6 and IPv4 attribute I'd suggest we don't go to the M:N14:12
samuelbercoviciaburaschi: in addition to ipv4+ipv6- a User wants to expose his application to the internet on one network using a virtual ip and then expose the same application on a different network facing only internal users14:13
sbalukoffMy point is that I don't see a reason for N:M *except* for the IPv4 + IPv6 use case being discussed. So, I'm a fan of 1:N only, with the caveat that "1" in this case is an entity that can have up to one IPv4 and one IPv6 address.14:13
*** TrevorV has joined #openstack-meeting14:13
enikanorov_samuelbercovici: good point14:13
Youcefblogan: but even if we don't, we can still accomplish the ipv4+ipv6 with 2 lbs, right?14:13
aburaschisamuelbercovici and blogan, thanks, that make sense.14:13
dougwigif i've got two network configs, is it reasonable to expect to share a listener?14:13
*** gokrokve has quit IRC14:14
vivek-ebay@Youcef, not unless we implement N:M14:14
samuelbercovicidougwig: well, its the exactly same application14:14
sbalukoffsamuelbercovici: In that use case, which seems a little contrived to me, I would say the work-around of having two different (non-shared) listeners is acceptable.14:14
dougwigright, but if i'm defining policies on two different subnets, i usually expect to define two network configs, even if i'm duping them.14:14
samuelbercovicisbalukoff: it is as exceptable as using two different listeners for ipv4 amd ipv614:15
Youcefsbalukoff: agree, having 2 listeners is not a big deal.14:15
*** balajiiyer has left #openstack-meeting14:15
sbalukoffsamuelbercovici: Except that I'm saying the IPv4 + IPv6 for the same "service" or "listener" is a far more common scenario. :P14:15
samuelbercovicisbalukoff: not in the use cases i have encountered14:16
Youcefvivek-ebay: We can have ipv4+ipv6 with 2 different listeners (duplicate the listener), right?14:16
bloganwhat it really comes down to is making it easier for an end user14:16
vivek-ebayYoucef: right14:16
sbalukoffblogan: Exactly.14:16
xgerman_easier - could also mena more consistent which could mean two listeners14:16
samuelbercoviciso if it is the same application (listener and bellow) it should be defined once14:16
sbalukoffHaving two different non-shared listeners is not a show stopper. It's just less convenient for the user.14:16
*** nelsnelson has joined #openstack-meeting14:16
aburaschiI see the point of sharing a listener. Nevertheless, what if we only have a 2:N relationship, beeing only an IPv4/6 issue?14:16
xgerman_I don't like creating special cases in an API --14:17
samuelbercoviciaburaschi: what about the use case, I have described? it can be more than 2...14:17
samuelbercovicixgerman_:+114:17
dougwigit's also a question of where it's easier.  a UI can hide this.  but the api can require separate building blocks, as per xgerman_'s point.14:17
bloganis keeping the user from having to do duplicate work and maintaining more than one listener/pool important enough to keep M:N?14:18
vivek-ebayhow much implementation complexity we see if we go with N:M route ?14:18
aburaschisamuelbercovici, sure :)  Not trying to ignore the use case. Just trying to understand if a dual IPv4/6 interface is an option instead of an M:N relationship.14:18
enikanorov_folks, i think that complexity of ipv4+ipv6 implemented with two LBs is solvable by proper UI14:18
sbalukoffIt's quite a bit more complex to implement N:M14:18
enikanorov_and then we may want to go for more flexible N:M14:18
xgerman_testing is a big hassle14:18
dougwigvivek-ebay: there was a thread on the mailing list a few days ago that outlined some warts it'd bring to the drivers.14:18
sbalukoffdougwig brought up some very good points about inconsistencies that can creep up with N:M, especially if N is a large number. :)14:19
jorgemvivek-ebay: This should be just API. Implementation can be the same either way I would think right?14:19
*** yfujioka has joined #openstack-meeting14:19
samuelbercovicienikanorov_: the key chalenge is with proviosning status and operation status on child objects14:19
samuelbercoviciwe already going to face this with pools14:19
enikanorov_samuelbercovici: that's the whole other big story... I wouldn't even try to address that within this bp14:20
sbalukoffIn any case, I'm willing to go with 1:M with no plans to go with N:M in the future...  any user asking for IPv6 is likely to be slightly more advanced anyway. :)14:20
xgerman_+1 abd might have automation14:20
*** ityaptin has joined #openstack-meeting14:20
sballe_sbalukoff: I like this appraoch since it will keep it simpler14:20
dougwigsbalukoff: +114:20
blogansbalukoff: I just don't want to go with 1:M adn add the IPv4 and IPv6 attributes and then go to N:M and make the IPv6 attribute unnecessary14:21
sbalukoffblogan: Good point.14:21
aburaschi+1 to blogan point14:21
sbalukoffI don't think N:M is good from an implementation perspective (*any* implementation) for reasons that dougwig pointed out on the mailing list.14:21
samuelbercovicican anyone specify, why M:N is an issue from an end user?14:21
enikanorov_samuelbercovici: i think with a proper UI it's not an issue14:22
blogansamuelbercovici: i think its good from an end user standpoint14:22
vivek-ebayM:N should make it easier for end-user....i think its more of a implementation complexity issue14:22
aburaschiagree14:22
sbalukoffImplementation complexity versus user convenience.14:22
jorgemI see either GUI users or API users (which hopefully means programatic interaction). If GUI then the issue can be abstracted. If programatic user it means righting slightly more code. I think 1:N is easier to understand and implement then with these assumptions.14:22
bloganenikanorov_: that is true as well but I don't see how a UI will be able to maintain two different listeners that shoudl be the same14:22
Youcefvivek-ebay: I think M:N is confusing for the user, but this is a matter of opinion :)14:22
sbalukoffIn this case, people are saying the implementation complexity is too great for not much user convenience.14:23
jorgemwriting*14:23
*** eghobo has joined #openstack-meeting14:23
enikanorov_blogan: not sure i understand. N:M means sharing listeners between LBs14:23
xgerman_sbalukoff +114:23
*** doron_afk is now known as doron14:23
bloganenikanorov_: oh i thought you were saying 1:N would be made simpler to do through the UI14:23
samuelbercoviciso are we in agrrement that M:n is the better approach from a user perspective?14:23
vivek-ebaycon someone briefly explain implementation complexity with M:N ? briefly14:23
*** thomasbiege has quit IRC14:24
*** tnurlygayanov has quit IRC14:24
bloganvivek-ebay: dougwig sent an email about some of them on the ML14:24
*** eghobo has quit IRC14:24
bloganvivek-ebay: on Tuesday I think14:24
dougwigbriefly:  "I don't have a strong objection, just an implementation shudder.  Of the14:24
dougwigtwo backends that I'm familiar with, they support 1:N, not N:N  So, we14:24
dougwigfake it by duping listeners on the fly. But, consider the extreme, say14:24
dougwig1000 LB's and 1 shared listener.  How long does it take to create 100014:24
dougwiglisteners?  What happens when it fails on 998?  Ok, we rollback.  What14:24
dougwighappens when the rollback fails?  Inconsistent state.  Driver's can't14:24
dougwigasync.  Driver's can't run cleanup routines later.14:24
dougwigWhat about when half the LB's have lit listeners and the other half don't;14:24
dougwigdoes the db say that N:N link is there yet or not?14:24
dougwigShrink the allowed number of listeners and the window of pain gets14:24
dougwigsmaller, but at operator scale, even a small window will get hit."14:24
*** lsmola2 has quit IRC14:25
vivek-ebayso that supports N:M14:25
*** rickerc has quit IRC14:25
enikanorov_dougwig: we do it per object. what does mean 'create 1000 listeners'?14:25
sbalukoffvivek-ebay: Actually that says N:M leads to the above scenario, which is not good.14:25
aburaschiYes... I thought the whole point of LB was the other way round...14:25
enikanorov_you create listener and associate it to LB14:26
*** ildikov_ has quit IRC14:26
enikanorov_it either fails or succeeds for each association14:26
vivek-ebayN:M would mean shared listner, which means we will have 1 instaed of 100014:26
*** ildikov has joined #openstack-meeting14:26
dougwigenikanorov_: if you have 1000 LB's that share one listener, and a backend that doesn't support M:N, then you have to create 1000 listeners as an "atomic" operation.14:26
*** tnurlygayanov has joined #openstack-meeting14:26
sbalukoffSure, but what if you've got a listener that is already shared to 1000 LBs, and make a change to the listener?14:26
sbalukoffOr one of the sub-objects.14:26
*** tmc3inphilly has joined #openstack-meeting14:26
sbalukoffSame scenario applies that dougwig is describing.14:26
bloganvivek-ebay: but on the backend there will most likely be 1000, depending on how the backend implements it14:26
vivek-ebayoh ok....you meant from driver perspective.14:26
*** doron is now known as doron_afk14:26
sbalukoffvivek-ebay: Yes, I think so.14:27
*** ramishra has quit IRC14:27
samuelbercoviciguys, we have very similar issue with pools14:27
enikanorov_i'd like to see a user that creates 1000 lbs that share the same listeners :)14:27
aburaschime too14:27
blogansamuelbercovici: yes we do :(14:27
*** reed has joined #openstack-meeting14:27
samuelbercoviciso this needs to be solved anyway14:28
enikanorov_he probably pays big money to not to create listeners for each of his lbs :)14:28
samuelbercovicibtw. is is also the case with current implementation of healthmonitors14:28
blogancan we not just start with with 1:M and add the N:M later if it is really needed?14:28
enikanorov_anyway, N:M is definitely more code then 1:N14:28
*** lsmola2 has joined #openstack-meeting14:28
*** david-lyle has joined #openstack-meeting14:28
sballe_blogan: +114:28
bloganenikanorov_: +114:28
enikanorov_blogan: that would be significant API change14:29
*** rickerc has joined #openstack-meeting14:29
dougwigthe 1000 is just to make the problem obvious.  it's still there with 2, it'll just be hit less often.14:29
samuelbercovicienikanorov_: correct14:29
*** yaguang has joined #openstack-meeting14:29
samuelbercoviciwe are already going to do a significant change, so we might as well try to do the critical changes at onec14:29
aburaschi+1 samuelbercovici14:29
bloganenikanorov_: i know and thats the problem with it14:29
rm_worknot having strong feelings either way, my concern would be "is N:M feasible for Juno", more than anything else...14:29
samuelbercovicithis is why we either do 1:N "forever" or do M:N14:30
jorgemIt seems to me that sharing config is a nice concept but the real reason people want to "share" is because they can't copy configs. So copying seems to be the goal not necessarily sharing. Sharing across 1000 lbs sounds nice but what happens when you want to start making changes across these lbs and realize you didn't want to share afterall?14:30
*** rakhmerov has joined #openstack-meeting14:30
jorgemIts the same concept as side effects in coding14:30
enikanorov_jorgem: you disassociate and create different listeners14:30
jorgemcorrect which is a pain14:31
Youcefjorgem: +114:31
jorgemjust like refactoring code with side effects14:31
aburaschiBut you would have to do it anyway with 1:N14:31
*** colinmcnamara has joined #openstack-meeting14:31
*** ominakov has quit IRC14:31
jorgemaburaschi: How so? It wouldn't be shared?14:31
*** reed has quit IRC14:31
enikanorov_i don't see why is it a pain, that would depend on UI14:31
aburaschiI mean, you would have to create all the relations from scratch14:32
enikanorov_doing everything manualy via CLI is pain anyway14:32
samuelbercovicibut if is is realy the same application, than managing M differetn replicas specificaly in TLS and L7 become very inconvinient14:32
xgerman_if we use UI we can also use 1:N14:32
enikanorov_samuelbercovici: agree14:32
jorgemenikanorov: My point is how much extra work is it really for a GUI or programatic API user to "copy" configs?14:32
blogansamuelbercovici: another good point for having M:N14:32
samuelbercovicijorgem: copy only address intiali deploy14:32
samuelbercovicithe key issues is the on-going operation aspects of it14:33
*** kevinconway has joined #openstack-meeting14:33
*** cfriesen__ has joined #openstack-meeting14:33
sbalukoffsamuelbercovici: That's actually a really good point.14:33
bloganso dougwig has voiced his problems with M:N, are there any others?14:33
*** dims has quit IRC14:33
xgerman_tetsing becomes difficult14:33
*** ttrifonov is now known as ttrifonov_zZzz14:33
samuelbercovicinow, the minute that we share pools, we have already made a dive to managing such cases14:33
*** yaguang has quit IRC14:34
dougwigthe l7 point is a good one.  i'm not so fond of the "we're already in pain elsewhere" reasoning.  :)14:34
blogansamuelbercovici: which is why I'd say we go with M:N or 1:N on both14:34
*** rakhmerov has quit IRC14:35
xgerman_1:N all the way :-)14:35
*** matiu has quit IRC14:35
sbalukoffblogan: 1:N on listeners:pools basically breaks L7 entirely, doesn't it?14:35
sbalukoffOr are you suggesting creating duplicate pools?14:35
*** otter768_ has quit IRC14:35
*** xuhanp has joined #openstack-meeting14:35
blogansbalukoff: yep14:35
samuelbercovicifor example, in M:N if you need tu update the default TLS certificate for the application, you do it once, if you replicate you do M times14:36
samuelbercovicisbalukoff: why?14:36
sbalukoffSo, it's really about shifting the complexity of "interesting deployment failure scenarios" back to the user to deal with14:36
*** matiu has joined #openstack-meeting14:36
samuelbercovicioh, you mean not shring pools?14:36
*** banix has joined #openstack-meeting14:36
sbalukoffsamuelbercovici: Yes, that's what I meant.14:37
*** nati_ueno has joined #openstack-meeting14:37
bloganSo you're advocating for sharing of pools?14:37
samuelbercovicisbalukoff: well this becomes even more problematic14:37
bloganbecause if we share pools, i don't know why we wouldn't share listeners14:37
rm_workWe are already 1:N on listener:pool? technically? because it's listener:l7policy:pool for the others14:37
*** OSM has joined #openstack-meeting14:37
sbalukoffblogan: Good point.14:37
*** topol has quit IRC14:37
sbalukoffrm_work: We're N:M because a given pool can be the target of many L7policies.14:38
enikanorov_rm_work: i think it's N:M, because different listeners may use sam pool14:38
enikanorov_*same14:38
*** flaper87 is now known as flaper87|afk14:38
*** otter768 has joined #openstack-meeting14:38
sbalukoffAnd yes, because different listeners can use the same default_pool_id.14:38
samuelbercovici<enikanorov_: sbalukoff: you are both right14:39
*** yfujioka has quit IRC14:39
*** zehicle_at_dell has quit IRC14:39
samuelbercoviciso if we need to handle shared pool provisoning status and operations status, a similar approach should be used for listeners14:40
*** OSM has quit IRC14:40
*** crc32 has joined #openstack-meeting14:40
samuelbercoviciand as far as I understand this is the key compleixty in the implementation14:40
vivek-ebayN:M makes sense for listener to pool14:40
jorgemI honestly think that unintended side effects by sharing configs is more important to a lb user due to the mission critical nature of a lb. I actually advocate not sharing anything. Again, a GUI and script can help me out in terms of setup and scale. I care that my lbs work and are isolated from human error.14:40
sbalukoffSo, not being able to share pools seems to me like a much bigger burden on the user and not being able to share listeners. But again, from the code-- we're having to deal with the same kind of complexity around failure scenarios in any case.14:40
enikanorov_samuelbercovici: i'd say this implementation item should be postponed14:41
Youcefvivek-ebay: agree.14:41
*** matiu is now known as Guest4655614:41
*** isviridov has joined #openstack-meeting14:41
enikanorov_at least it should not be a part of the first patch14:41
*** crc32 has quit IRC14:41
xgerman_jorgem +114:41
bloganenikanorov_: agreed14:41
*** crc32 has joined #openstack-meeting14:41
YoucefI see the lb:listener relationship differently than the listern:pool relationships. the latter is much more common in N:M.14:41
Youcef*listener14:42
samuelbercoviciI care less about steps and more about what will be the delievry for Juno14:42
rm_workyeah but i guess I don't count listener:l7policy:pool as M:N listener:pool, since l7policies aren't shared… so it's M:1 listener:pool, and 1:N:1 listener:l7policy:pool, no?14:42
xgerman_also we said pool is a logical construct and gets provisioned when a listener or lb gets created14:42
samuelbercovicirm_work: why l7 policies not be shared?14:42
sballe_samuelbercovici: +114:42
rm_workare they? i just thought they weren't14:42
rm_workmaybe I am remembering the model wrong14:43
samuelbercovicirm_work: it is one of the options14:43
samuelbercovicirm_work: but lets not add this in for now14:43
rm_workkk14:43
blogani think if we start sharing everything complexity and unexpected side effects increases exponentially14:43
sbalukoffsamuel's L7 policy model allows for sharing of L7 policies. Mine doesn't.14:43
xgerman_+ 114:43
enikanorov_jorgem: N:M is superset of 1:M, so if cloud operator wants, it can then forbid sharing14:43
rm_workah, that'd explain it sbalukoff14:43
sballe_ meant +1 on the Juno delivery as mentioned by samuelbercovici14:44
samuelbercoviciThe blue print should describe the delivery and then the steaps to get ther14:44
rm_workI'd also +1 that (as i said earlier, Juno delivery is what matters most if we don't have strong opinions in either direction)14:44
*** kevinconway has quit IRC14:44
*** weshay has quit IRC14:45
*** colinmcn_ has joined #openstack-meeting14:45
dougwigwe've been talking for 45 minutes.  not usually a sign on not having strong opinions.14:45
dougwig:)14:45
rm_workheh14:45
xgerman_we can vote?14:45
*** kevinconway has joined #openstack-meeting14:45
sbalukoffdougwig: Not in this group. XD14:45
bloganif delivery is what matters then doing 1:M at first with the intention on donig N:M later would make more sense since there is no consensus14:45
jorgemenikanorov: I trying to force it because even as a developer I still have bugs when dealing with "pass by reference" objects and such even though I am aware of these things. Again lbs are missions critical, I want to help humanity from shooting itself in the foot :)14:45
*** colinmcnamara has quit IRC14:46
jorgemIf lbs weren't mission critical I would be indifferent14:46
enikanorov_jorgem: agree, but that's phylosophy. In C++ you can use const&14:46
xgerman_yeah, and I can see the support calls from users chnaging something and not realizing they broke all their lbs14:46
dougwigwould we be voting on B:L:P or 1:L:P or 1:L:1 ?  or just two of those?14:46
samuelbercovicijorgem: if someone don't want to share than he might as well not share14:46
crc32+1 jorgem at this point I don't want to see breaking one loadbalancer breal all the others.14:46
enikanorov_so you may shoot or you may be safe from that14:46
enikanorov_that's flexibility14:46
samuelbercovicideciding on 1:N makes shring impossible14:46
*** yaguang has joined #openstack-meeting14:47
JulianCash_Vote = good.  Before the meeting ends = even better.14:47
rm_workxgerman_ / dougwig: I'm afraid just voting might alienate people with valid opinions :( but i guess at some point it might be necessary?14:47
jorgemenikanorov: I suppose. Your point makes sense it is just a preference then.14:47
crc32enikonarov_: The point with const & is to avoid shoving the whole object on the call stack while still preserving the const.14:47
xgerman_aren't we coding in Python?14:47
*** gokrokve has joined #openstack-meeting14:48
jorgemenikanorov: I guess I can tell our GUI programmers to not share configs so I guess I'm fine then.14:48
bloganalirght we're getting in the weeds14:48
enikanorov_xgerman_: when someone says' shooting in the leg' ...14:48
samuelbercoviciso snake-biting in out foor :-)14:48
jorgemxgerman_: I was using it as sort of metaphor lol14:48
rm_worki think const& was a similie/metaphor/allegory14:48
bloganso should there eb a vote and that vote is the final decision?14:48
rm_workwould the vote need to be a supermajority? >_>14:48
xgerman_we need some mechanism of coming to a decision14:49
*** rushil has joined #openstack-meeting14:49
enikanorov_i see more reasons for N:M14:49
sballe_xgerman_: +114:49
jorgemflexibility is fine. We can control side effects via our GUI at Rackspace and tell API users to be careful.14:49
enikanorov_jorgem: yep14:49
samuelbercoviciblogan: so taking odd the implementation complexity, you think that M:N should not be implemented14:49
samuelbercovici?14:49
rm_workwe can "straw poll" if that's less contentious maybe?14:50
samuelbercoviciodd==off14:50
xgerman_well, if we want to hide ot from users, it's hard to implement, ...14:50
blogansamuelbercovici: I'm leaning towards N:M but not strongly against either one.  I think the flexbility is most important, but I am afraid of the complexity caused by sharing everything14:50
samuelbercoviciI think we need to evalute the implementation complexity off-line14:50
*** rushil has left #openstack-meeting14:50
aburaschiI totally agree with blogan...14:50
aburaschiand with you too, samuelbercovici.14:51
dougwigmy biggest concern is not making things late or brittle for Juno, frankly.14:51
samuelbercoviciare we in agreement that from a user-perspective M:N is the correct approach?14:51
sballe_I agree we need to make this available in Juno14:51
*** thedodd has joined #openstack-meeting14:51
xgerman_I think the copy approach is easieer to understand14:51
rm_workblogan / samuelbercovici / dougwig / sballe_ +114:52
sbalukoffsamuelbercovici: It's certainly the simpler approach for the users and provides the most flexibility.14:52
jorgemN:M is fine ~+1 :)14:52
*** zhiyan is now known as zhiyan_14:52
aburaschiI think we agree that M:N is the most flexible approach, and that there is some concern about getting that to work for Juno14:52
sbalukoffjorgem: LOL!14:52
*** jecarey has joined #openstack-meeting14:52
enikanorov_i think we need to do what is right, even just N:M is not the whole completed refactoring14:52
samuelbercoviciso lets, give it a hsot, to pinpoint the key chalenges in doing it and evaluete complexity so we have abetter measured way to decide14:52
vivek-ebayN:M for listener-to-pool +114:53
bloganokay so back to N:M then?14:53
JulianCash_For me, even if there isn't a "final decision", a sense of how many people want what, and how strongly they feel would be nice before this ends in 7 min.  How can we quickly make a kinda vote thing happen.14:53
JulianCash_?14:53
rm_worksounds like it14:53
*** baojg has joined #openstack-meeting14:53
sbalukoffblogan: More or less.14:53
*** fabiog has joined #openstack-meeting14:53
sbalukoffWe're all sort of luke-warm about it.14:53
sbalukoffit seems.14:53
*** idegtiarov has quit IRC14:53
YoucefN:M for listener to pool +1, N:M for lb:listener: -1  :)14:53
dougwigi'm still 1:N, but not enough to really register a negative vote about it.14:53
bloganI still think going with 1:M to start woudl be better, even though it is a major change later14:53
xgerman_I like 1:M more14:54
sballe_me too +114:54
samuelbercovici+1 for both14:54
rm_workI like M:N but worry about Juno release14:54
sballe_samuelbercovici: Not fair ;-)14:54
blogani like sam's idea of figuring out the implemenation issues offline14:54
sbalukoffblogan: +114:54
dougwigblogan / samuelbercovici +1 on scoping14:55
rm_workyeah, we don't have time in the next 5 minutes for a code review :P14:55
blogandare we try to move on to another topic?14:55
xgerman_sure, we have 514:55
samuelbercoviciso decision? give it till next week to quantify the effort and then get final decision?14:55
enikanorov_blogan: i think we covered most of them14:55
xgerman_yep14:55
rm_worksamuelbercovici +114:55
blogansamuelbercovici: sounds like it to me14:55
enikanorov_except for status of the pool14:55
dougwigwhere is the offline meeting?  who is taking point on that?14:55
jorgemWhat about Epic/Umbrella?14:55
bloganenikanorov: health monitor as well14:55
jorgemthats on the agenda14:56
dougwigany chance of getting an object model bp for l7/ssl, so we can evaluate the N:M in that context better?14:56
enikanorov_blogan: IMO this also better postponed14:56
sballe_I need to drop off. will read the scrollback later. Bye.14:56
*** Alexei_987 has joined #openstack-meeting14:56
bloganenikanorov: thats fine, I think this is a good stopping point anyway14:56
*** llu-laptop has joined #openstack-meeting14:57
jorgemaction items?14:57
bloganresearch scope of implementation issues with N:M14:57
*** gordc has joined #openstack-meeting14:57
jorgem#action research scope of implementation issues with N:M14:57
*** gokrokve has quit IRC14:57
*** dstanek has left #openstack-meeting14:57
samuelbercovicisam to send to ML intial bultes of things to address in M:n14:57
aburaschispace to do that? ML?14:57
samuelbercoviciML14:57
*** weshay has joined #openstack-meeting14:58
jorgemaburaschi: yes14:58
*** gokrokve has joined #openstack-meeting14:58
aburaschiok, that was a late Enter...14:58
bloganwe can discuss some more in #neutron-lbaas as well14:58
aburaschi:)14:58
*** colinmcnamara has joined #openstack-meeting14:58
xgerman_#action sam to send to ML intial bultes of things to address in M:n14:58
Youcef#action research scope of implementation issues with N:M for both lb:listener and listener:pool relationships14:58
sbalukoffYep.14:58
jorgemblogan: true but it would be nice if discussions get paraphrased on ML as well14:58
sbalukoffI'd like to see a bot get added to #neutron-lbaas14:58
*** colinmcn_ has quit IRC14:58
sbalukoffSo that people have a place to look at conversations who can't be online all the time.14:58
jorgemsbalukoff: yup14:58
aburaschi+14:58
aburaschi+14:58
dougwigcan we add neutron-lbaas to eavesdrop?  who's the person to contact about that?14:58
xgerman_+14:59
aburaschi+114:59
enikanorov_i don't know, may be mestery knows14:59
VijayB_blogan: guess we're short on time to discuss the service implementation, so we can go back to the ML for that14:59
Youcef=114:59
JulianCash_+14:59
Youcef+114:59
bloganVijayB_: join #neutron-lbaas14:59
jorgemi++14:59
*** eglynn has joined #openstack-meeting14:59
VijayB_blogan: ok14:59
sbalukoffHaha14:59
rm_work+114:59
enikanorov_ok, we're out of time14:59
sbalukoffOk, thanks y'all!14:59
xgerman_thanks14:59
dougwigbye14:59
enikanorov_thanks everyone for joining14:59
aburaschiThank you all!14:59
jorgemthanks!15:00
*** TrevorV has left #openstack-meeting15:00
enikanorov_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
rm_work+100015:00
*** xgerman_ has left #openstack-meeting15:00
openstackMeeting ended Thu May 29 15:00:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-05-29-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-05-29-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_lbaas/2014/neutron_lbaas.2014-05-29-14.00.log.html15:00
eglynn#startmeeting ceilometer15:00
openstackMeeting started Thu May 29 15:00:17 2014 UTC and is due to finish in 60 minutes.  The chair is eglynn. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: ceilometer)"15:00
JulianCash_Thanks15:00
openstackThe meeting name has been set to 'ceilometer'15:00
*** jorgem has left #openstack-meeting15:00
eglynnhey y'all15:00
*** bbaby has left #openstack-meeting15:00
llu-laptopo/15:00
ildikovo/15:00
prad_o/15:00
nealpho/15:00
_nadya_o/15:00
*** ominakov has joined #openstack-meeting15:01
fabiogo/15:01
ityaptino/15:01
eglynnk folks, lots to get thru' today ...15:01
DinaBelovao/15:01
aviauo/15:02
gordco/15:02
*** aburaschi has left #openstack-meeting15:02
*** gokrokve has quit IRC15:02
eglynn#topic "Quick apology"15:02
*** openstack changes topic to ""Quick apology" (Meeting topic: ceilometer)"15:02
ddieterlyo/15:02
eglynnildikov: the floor is yours ...15:02
ildikovmurphi, alias me owes you an apology :)15:02
*** PhilD has quit IRC15:02
ildikoveglynn promised me to kick me out of the Ceilo channel, if I show up on the meeting on my vacation15:03
ildikovso I borrowed my good friend Murphy's name with a small modification15:03
* eglynn adds murphi to the evergrowing /kick list :)15:03
*** rakhmerov has joined #openstack-meeting15:03
eglynnno worries :)15:04
eglynn#topic Juno-1 blueprints coverage15:04
*** openstack changes topic to "Juno-1 blueprints coverage (Meeting topic: ceilometer)"15:04
eglynn#link https://launchpad.net/ceilometer/+milestone/juno-115:04
* nsaje jumps in late15:04
eglynnlooks like we're in not bad shape for j-115:05
*** Berlin has quit IRC15:05
eglynn... a few BPs with outstanding specs15:05
DinaBelovaeglynn, we have some BP to be reviewed ;)15:05
DinaBelovaI mean code-reviewed)15:05
eglynn... i.e. currrently under review as DinaBelova points out, or else yet to be written15:05
ildikovare those too for j-1?15:06
_nadya_mm, should I rewrite old bp to spec?15:06
DinaBelova_nadya_, well I may do it for you)15:07
eglynn_nadya_: we decided to absolve any BPs that were already approved and already substantially implemented (e.g. as a result of being bumped from Icehouse)15:07
ildikov_nadya_: IIRC that was the agreement that the unapproved/unstarted BPs should be rewritten in spec15:07
_nadya_but it's started and on review15:07
eglynnyep, only "fresh" BPs need to follow the new process15:07
DinaBelova_nadya_, so as your one is almost done and approved...15:07
DinaBelovanp)15:08
_nadya_ok, thanks for clarification15:08
llu-laptopeglynn: how about approved but not started bp ?15:08
eglynn_nadya_: yep ... so if it was previously approved and already substantially implemented, not really a good use of time to retrospecitively write a spec15:08
eglynnllu-laptop: ... in that case, probably best to write a spec I think15:09
eglynndoes anyone have anything else they think merits a BP for j-1?15:09
llu-laptopeglynn: ok. One of my colleagues what to implement the xen inspector bp which is already approved. I told him to write the spec, glad I didn't give hime the wrong answer15:10
eglynnllu-laptop: cool, thanks for pointing him in the right direction :)15:10
DinaBelovaeglynn - well, we have tempest tests - in the tempest - we previously thought it'll be j115:10
eglynnildikov: ... for example, does the docco work need a BP to track?15:10
DinaBelovaeglynn - just spoke with qa folks15:10
ildikoveglynn: good question15:10
ildikoveglynn: I do not know the process for manuals15:11
*** topol has joined #openstack-meeting15:11
*** esker has joined #openstack-meeting15:11
DinaBelovaeglynn - to merge our tests they need to do some extra work in the gate - so the tests will be in gate only at the end of next week15:11
DinaBelovait's the best option we have)15:11
ildikoveglynn: in the Dev doc there will not be a huge change, but if you want e to write a BP for it, I can do that15:11
eglynnildikov: can you ping annegentle to see what her preference is?15:11
DinaBelovaeglynn - but we may have our tepmest patches merged *before*15:11
*** pcm_ has left #openstack-meeting15:11
*** cdent has joined #openstack-meeting15:11
*** esker has quit IRC15:12
_nadya_DinaBelova: what work they need to do?15:12
DinaBelovait's about the feature flags15:12
ildikoveglynn: sure15:12
DinaBelovathey have the mechanism to skip tests in the icehouse job15:12
*** colinmcnamara has quit IRC15:12
*** esker has joined #openstack-meeting15:12
DinaBelova_nadya_ but it's not sufficient15:12
_nadya_DinaBelova: ah, you are talking about icehouse job?15:12
eglynnDinaBelova, _nadya_: so we've an item on that later in the agenda15:12
cdentsorry for late; can't seem to remember to join here on time15:12
DinaBelovaeglynn, _nadya_ - yep, sorry to be impatient)15:13
eglynnDinaBelova: np!15:13
DinaBelovajust as for the j115:13
eglynnDinaBelova: ... yeah on the j1 tracking, d'ya think the tempest work needs a fresh BP to track?15:13
eglynnDinaBelova: ... or more like bug/RFE-level work-items on the QA side15:14
DinaBelovaeglynn - not the Bp in the ceilometer, I guess, but we have unclear BP for the tempest - that's why I'm writing specs now15:14
*** Mandell has joined #openstack-meeting15:14
DinaBelovaand I wonder if it's a good idea to mark them j115:14
eglynnDinaBelova: a-ha, cool, those specs will land in qa-specs repo15:15
DinaBelovayes15:15
DinaBelovaas said - not ceilo BPs, but related15:15
eglynnDinaBelova: ... is j1 a bit ambitious, possibly?15:15
DinaBelovaI guess yes15:15
DinaBelovasome of the pathes will be landed for sure15:15
DinaBelovapatches*15:15
*** gilliard has left #openstack-meeting15:15
*** weshay has quit IRC15:16
DinaBelovabut not all for sure - we have some things like events scenario - it's not started yet at all15:16
_nadya_eglynn: we have all-in-one bp about 'basic ceilo test' and now there is the same about 'scenario (advanced) ceilo tests'15:16
eglynnDinaBelova: ... so ambitious for j1 completion, but seems like some concrete progress definite in timeframe15:16
DinaBelovaeglynn, yes, exactly15:16
eglynncool15:16
eglynnso just a quick reminder, juno-1 tag will be cut on June 12th15:17
_nadya_DinaBelova: eglynn, we should be ready with basic in j115:17
DinaBelova_nadya_ - yes, I hope so - if we'll have no blockers from the qa folks15:17
_nadya_DinaBelova: eglynn, scenario are for j2, j3 I believe15:17
DinaBelovaif they'll keep this "end of next week" estimation - it'll be so)15:17
DinaBelova_nadya_, ++15:18
eglynn_nadya_: cool enough15:18
* eglynn just wants to show definite progress to TC by the time of the j1 review of the gap coverage actions15:18
*** colinmcnamara has joined #openstack-meeting15:18
eglynn(i.e. doesn't need to be 100% there by then)15:19
*** gokrokve has joined #openstack-meeting15:19
DinaBelovaeglynn, we'll have basic api tests landed I guess15:19
DinaBelovaand all other stuff - on review15:19
DinaBelovaor in progress (as for the scenarios)15:19
eglynnDinaBelova: that would be a good outcome for j1 :)15:19
*** esker has quit IRC15:19
*** reed has joined #openstack-meeting15:20
eglynnBTW the new tag-driven milestone release process will buy us maybe a day or two extra development time for j115:20
eglynn... *if * we choose to take it15:20
eglynn... however it's really just borrowing from the juno-2 milestone15:20
eglynn... a zero-sum scenario15:20
ildikovnext topic maybe? ;)15:22
*** weshay has joined #openstack-meeting15:22
llu-laptopshould we continue?15:22
eglynnanything else anyone wants to bring up related to j2?15:22
eglynnk, moving on in that case ...15:22
DinaBelovaeglynn, I guess we may go further)15:22
ildikoveglynn: we have time for j2 ;)15:22
eglynn#topic details of Juno mid-cycle meetup15:22
*** openstack changes topic to "details of Juno mid-cycle meetup (Meeting topic: ceilometer)"15:22
eglynnjd__: the floor is yours :)15:22
eglynnk, no jd__ ... let's punt that topic to next week15:23
*** jergerber has joined #openstack-meeting15:23
DinaBelovajd__, hehe) you here?15:23
gordci think they have a holiday in France last i checked.15:23
aviauYes they do15:23
DinaBelovathat's not the good reason for not being here)15:23
eglynngordc: a-ha, that explains it :)15:23
DinaBelova:D15:24
ildikovhaha, I thought only the Swedish guys don't like working :)15:24
eglynn#topic Performance tests as 3rd party CI15:24
*** openstack changes topic to "Performance tests as 3rd party CI (Meeting topic: ceilometer)"15:24
ityaptinHi) We decided to make performance test more automated15:24
ityaptinIn thoughts it looked like job or scripts which uses ceilometer master and return results from profiler. For api, collector and agents performance.15:24
eglynnityaptin: ... so will it run periodically or on every commit?15:25
*** elambert has joined #openstack-meeting15:25
*** tomoe_ has joined #openstack-meeting15:25
Alexei_987voting to run this on demand15:25
*** tmc3inphilly has quit IRC15:25
*** kenhui has quit IRC15:25
ityaptinI think it shoul to run periodically, because for every commit we have some issues:15:25
Alexei_987no need to run tests since every run requires manual analysis15:25
ityaptinThese tests are too long for run them for each patchset15:25
ildikovmy vote is on periodically or close to release, I do not mean the last day of course :)15:26
eglynnseems a mix of periodic and on-demand would be useful15:26
llu-laptopor close to each mielstone?15:26
*** tomoe_ has quit IRC15:26
llu-laptops/miel/mile/15:26
fabiogcould be run for every code set tagged for the milestone15:27
*** tomoe_ has joined #openstack-meeting15:27
DinaBelovaalso there is the issue with the testing env - if we speak about Jenkins job, for instance, there is only one node there, only standalone storage...15:27
*** doron_afk is now known as doron15:27
*** nati_ueno has quit IRC15:27
DinaBelovathese results won't be really useful15:27
eglynn... so we see say the weekly trend over the cycle, but also run for each milestone/RC tag?15:27
gordcllu-laptop: +1, that'd be a good minimum15:27
*** rbak has joined #openstack-meeting15:27
fabiogeglynn +115:27
DinaBelovaeglynn, I guess it'll be cool15:27
ityaptinI think we may run these test for milestonces15:27
DinaBelovaspeaking about the performance)15:28
eglynnityaptin: how will the results be reported?15:28
ildikovllu-laptop: agree15:28
DinaBelovawe have blockers from QA folks, but we have porking tempest + ceilo15:28
*** tomoe__ has quit IRC15:28
*** andreaf has joined #openstack-meeting15:28
*** mwagner_lap has joined #openstack-meeting15:28
DinaBelovaso gordc - your improvements were cool)15:28
DinaBelovawell, let's be patient)15:28
DinaBelovaabout the performance testing15:29
ityaptinNow I write tests with profiler and it will collect tests results from profileng of runned process15:29
*** andreaf has quit IRC15:29
eglynnityaptin: ... if perf tests are decoupled from individual commits, then clearly results can't be reported as CI votes on gerrit?15:29
*** VijayB_ has quit IRC15:29
gordcDinaBelova: good to know... i haven't turned on multiple workers... debating if we should just to make sure it works.15:29
*** blamar has quit IRC15:29
eglynnityaptin: "profiler" == "os-profiler by boris-42"?15:29
DinaBelovaeglynn, no15:29
Alexei_987eglynn: no profiler -> cProfile15:29
eglynna-ha, k15:30
DinaBelovaos-profiler by boris-42 uses ceilo itself)15:30
prad_can we see the performance test results somewhere after each run?15:30
DinaBelovanot our variant)15:30
ityaptineglynn, about commit - yes15:30
DinaBelovaprad_ - that's  "todo" item - last times ityaptin published them himself15:30
prad_ah ok15:30
eglynnityaptin: ... so I'd like to see the results reported to a well-known/discoverable place15:30
_nadya_regarding performance tests. As I understand, the strategy is still to be discussed. We have ityaptin's scripts but CI-configuration needs to be carefuly thought out15:31
*** gholt has quit IRC15:31
ityaptinFor examle, tests results for each milestones we can whos in wiki and at meetings15:31
DinaBelova_nadya_, yes, exactly15:31
DinaBelovaeglynn, _nadya_ - the issue is about *where and how* to run these tests15:31
*** rbowen has quit IRC15:31
*** rbowen has joined #openstack-meeting15:32
eglynnityaptin: ... what would be would for the test results to be easily discoverable15:32
*** gholt has joined #openstack-meeting15:32
*** vivek-ebay has quit IRC15:32
eglynnityaptin: ... so given a tag, anyone would know where to go find the corresponding results15:32
llu-laptophow about a special commit which never gets merged on gerrit to trigger that perf test? and perf test could post result as a 3rd party CI test15:32
DinaBelovaeglynn, _nadya_ we had the opportunity to create small virtual clusters as the testing labs internally - but I guess this should be somehow improved for the automated testing15:32
eglynn... cool, sounds like there are some aspects of this that need to be worked out in detail15:33
_nadya_so by now, for this meeting, we just wanted to announce that we've started to work on it and ityaptin will be contact person. All suggestions about the place for results, db configurations are welcome15:33
*** akuznetsov has quit IRC15:33
eglynn... (a) when exactly to run, and (b) where & how to report results15:33
DinaBelovaeglynn, exactly15:34
eglynnityaptin: shall we return to this topic maybe next week to get closure on those two questions ^^^15:34
DinaBelovato have these tests on demand we need some nodes to work on -they should be specially configured, etc...15:34
*** lcheng_ has joined #openstack-meeting15:34
DinaBelovalots of infra questions really15:34
_nadya_maybe it would be useful to discuss this one in 2 weeks15:34
_nadya_*once15:35
DinaBelova_nadya_, well, next week we may provide some update, but I guess clear answer will be in two ones15:35
DinaBelovaeglynn ^^15:35
*** zhangleiqiang has joined #openstack-meeting15:35
ityaptineglynn, yes) we should to think this resuts, because now we have not complete answer for these questions15:35
DinaBelovaeglynn - is it ok for announcement? :)15:36
eglynn_nadya_, DinaBelova, ityaptin: cool let's return to this topic next week so (... then every 2nd week maybe thereafter?)15:36
eglynn#topic Tempest integration15:36
*** openstack changes topic to "Tempest integration (Meeting topic: ceilometer)"15:36
DinaBelovayeah)15:36
eglynn... drum roll :)15:36
DinaBelovaso some news about this topic)15:37
_nadya_pretty good news15:37
eglynn... the suspense is killing me! :)15:37
*** lsmola2 has quit IRC15:37
DinaBelova1/ ceilo _ tempest works ok even without multiple collectors with gordc change for SQL backend15:37
*** Macaveli has joined #openstack-meeting15:37
*** leeantho has joined #openstack-meeting15:37
DinaBelovait's even not loaded15:37
eglynn\o/15:37
DinaBelovaI mean ceilometer15:37
DinaBelovawe used profiler to collect the measurements15:37
eglynngordc for the win! :)15:37
llu-laptopbravo gordc15:38
gibinice!15:38
ildikovgordc: congrats :)15:38
prad_gordc++15:38
nsaje\o/15:38
DinaBelovaso even with the additional load provided by profiler it's ok15:38
fabioggordc Congrats!15:38
*** ramishra has joined #openstack-meeting15:38
gordc:) let's see how long it last15:38
eglynn... gordc kicks back and lights a cigar ;)15:38
DinaBelovanah, also we need to say big THANK YOU to Vadim)15:38
*** vrovachev has joined #openstack-meeting15:39
eglynnvrovachev: kudos! :)15:39
gordci'll give sileht credit for having same thoughts as me.15:39
*** doron is now known as doron_afk15:39
_nadya_I believe that v1 dropping was helpful too :)15:39
DinaBelovaokay)15:39
gordcvrovachev: thanks for working on tests!15:39
eglynnso we've goodness now on master15:39
DinaBelovathe next point is 2/ we had several discussions with qa folks15:39
eglynn... but still the problem of branchless Tempest, i.e. skipping testcases against stable/icehouse15:39
DinaBelovaeglynn, exactly)15:40
vrovacheveglynn: oh, thanks :S15:40
*** lsmola2 has joined #openstack-meeting15:40
eglynnTBH I'm a bit concerned about the ideas underpinning branchless tempest, i.e. that the API is just the API15:40
*** coasterz has quit IRC15:40
DinaBelovaeglynn - well, anyway we have the possibility for workaround here15:40
gordceglynn: was the answer we had to get it working in icehouse too?15:41
DinaBelovabut as said - QA folks need some magic in gate to allow this15:41
*** doron_afk is now known as doron15:41
DinaBelovagordc, no, we persuaded QA folks that it's impossible15:41
DinaBelovathank God15:41
eglynnDinaBelova: ... so this is the feature flag idea we discussed with Sean yesterday?15:41
DinaBelovaeglynn, yes, but it looks like it's not so simple15:41
DinaBelovaas our flag will be ceilo specific15:42
DinaBelovaand as "tempest should be used for every cloud"15:42
gordcDinaBelova: cool cool. it might be possible to backport without dropping v1 but if we don't have to that's better.15:42
DinaBelovathey need one more level of abstraction speaking sabout feature flags15:42
DinaBelovaabout*15:42
DinaBelovagordc, ;)15:42
DinaBelovaeglynn, so they promised to make it work before the end of next week15:42
eglynngordc: yeah ... best to avoid the need to backport *every* perf improvement15:43
DinaBelovaand to land out tempest patches before15:43
*** ramishra has quit IRC15:43
DinaBelovaour*15:43
gordceglynn: agreed.15:43
eglynnDinaBelova: excellent! :)15:43
DinaBelova;)15:43
DinaBelovathey'll be just skipped before this "new abstraction level" will be done15:43
DinaBelovaand turned on after this15:43
DinaBelovaso news are quite good ones15:44
*** esker has joined #openstack-meeting15:44
DinaBelovawell, it's almost the all I wanted to point here - I guess I mentioned all important moments15:44
DinaBelovafolks, do you have questions here?15:44
eglynnDinaBelova: great news indeed!15:44
*** rudrarugge has joined #openstack-meeting15:45
eglynnDinaBelova: ... so the "new abstraction level" part, any clarity on what exactly the qa folks intend to do there?15:45
gordclooking forward to getting tempest tests up and running. :)15:45
DinaBelova#info current ceilo master works with tempest15:45
cdent\o/15:45
*** Munish has joined #openstack-meeting15:45
DinaBelova#info tempest gating will be available ~end of next week due to QA infra blockers15:45
DinaBelovaeglynn, well15:45
DinaBelovanot so much really15:46
*** baojg has quit IRC15:46
DinaBelovaI'm not really experienced in tempest to understand Sean in all the moments :-\15:46
eglynnDinaBelova: ... cool enough, it's all magic :)15:46
DinaBelovaeglynn:15:46
DinaBelova[18:58:37]  <sdague> vrovachev: so the reality is we'll need the next level of feature grid in d-g to support this, however that won't happen until next week. But we can get the tempest bits close before then.15:46
DinaBelova:)15:46
*** luqas has quit IRC15:47
*** weshay has quit IRC15:47
eglynn... if Sean's confident it'll be sorted within a week, then we can probably "take that to the bank" :)15:47
DinaBelova;)15:47
*** tomoe_ has quit IRC15:47
*** zhiyan_ is now known as zhiyan15:47
DinaBelovaso let's move on I guess15:47
DinaBelovaeglynn?15:48
* eglynn wants to buy the team a virtual beer to mark this happy occasion :)15:48
*** weshay has joined #openstack-meeting15:48
eglynn... well everyone except _nadya_, just an orange juice for you! ;)15:49
* DinaBelova saying cheers :)15:49
_nadya_eglynn: thanks :)15:49
eglynnvery quickly on "DefCore impact of the lack of Tempest coverage in Havana"15:49
eglynn... so sadly the current DefCore effort is completely based on Havana15:49
*** jcoufal has quit IRC15:50
eglynn... and our first Tempest coverage didn't land until Icehouse (i.e. the alarms tests IIRC)15:50
DinaBelovaeglynn, yep - alarms api afair15:50
*** esker has quit IRC15:50
eglynn... so as a result of the lack of Tempest coverage in H, no telemetry capabilities whatsoever listed in DefCode :(15:50
eglynnhttps://wiki.openstack.org/w/images/e/e3/DefCore_Capabilities_Scoring.pdf15:50
DinaBelovaheh :(15:51
eglynn... so we may need to think about backporting those alarm API tests to stable/havana in Tempest?15:51
*** esker has joined #openstack-meeting15:51
eglynn... just an idea I wanted to throw out on the table15:51
*** doron is now known as doron_afk15:51
*** jackib has joined #openstack-meeting15:52
DinaBelovaeglynn, well15:52
DinaBelovavrovachev what do you think about it?15:52
_nadya_eglynn: with Mongo we may try15:52
eglynnwe may have already missed the boat on that ...15:52
eglynn... but /me thinking it would not reflect well for ceilo to be completely absent from DefCore15:52
vrovachevDinaBelova: i thins, it's good idea :)15:52
vrovachevthe only moment here is to check that they'll work15:53
eglynn... food for thought in any case, running out of time for today15:53
eglynn... so let's rush on15:53
eglynn#topic TSDaaS/gnocchi update15:53
*** openstack changes topic to "TSDaaS/gnocchi update (Meeting topic: ceilometer)"15:53
DinaBelovano __jd :)15:54
*** kgriffs|afk is now known as kgriffs15:54
eglynnseeing jd__ isn't here, DinaBelova anything you wanted to bring up?15:54
eglynnor just punt for today?15:54
*** gokrokve has quit IRC15:54
*** gokrokve has joined #openstack-meeting15:54
DinaBelovawell, I was working on "how to run it???"15:54
DinaBelovawell, currently I have some success :)15:54
*** yaguang has quit IRC15:54
DinaBelovais amalagon here?15:54
eglynnyeap, I saw the discussions on IRC and anamalagon's README15:54
*** mrodden has joined #openstack-meeting15:55
eglynnDinaBelova: don't think so15:55
*** gokrokve has quit IRC15:55
DinaBelovaeglynn, yes - so it's basically working - some gnocchi + swift stuff15:55
*** comay has joined #openstack-meeting15:55
DinaBelovanot really easy to turn it on now, but I guess it'll be better15:55
DinaBelovaso the next steps will be to think about how it might be integrated with ceilo15:56
eglynnDinaBelova: cool ... great to have that "getting started" info written down, easier for others to get involved and kick the tyres15:56
DinaBelovaeglynn, yes, for sure15:56
DinaBelovaI hope amalagon will do this soon15:56
DinaBelova:)15:56
*** emagana has joined #openstack-meeting15:56
DinaBelovawith my help a little bit)15:56
*** doron_afk has quit IRC15:56
eglynnDinaBelova: yeap, we'll need another round of discussion on exactly what that integration will look like15:56
*** crc32 has quit IRC15:56
DinaBelovaeglynn, exaclty15:56
eglynn#link https://review.openstack.org/9632115:56
eglynn^^^ README15:57
*** paragan has quit IRC15:57
DinaBelovaand how it might fit with other features15:57
DinaBelovaevents, for instance ;)15:57
*** zhiyan is now known as zhiyan_15:57
DinaBelovawell, anyway, work is just started)15:57
eglynnDinaBelova: cool, all good :)15:57
eglynn#topic MONaaS update15:57
*** openstack changes topic to "MONaaS update (Meeting topic: ceilometer)"15:57
ildikovI volunteer for the pipelinie part15:57
_nadya_eglynn: where this round be held?15:57
eglynnildikov: great! :)15:57
_nadya_eglynn: ML?15:58
aviauHey everyone :)15:58
eglynn_nadya_: well gerrit, ML, wiki, etherpad, IRC ... all over the place probably15:58
*** Alexei_987 has left #openstack-meeting15:58
eglynnaviau: hey15:58
eglynnaviau: sorry we're up against the shot clock here15:58
DinaBelovaaviau you have two mins)15:58
_nadya_eglynn: I just wanted not to be lost in this discussion15:58
aviauI'll try to go fast.15:59
aviauThere was a lot of work done on the Etherpad, you can take a look at it.15:59
aviau#link https://etherpad.openstack.org/p/MONaaS15:59
aviauI also suggest you take a look at Nick Barcet's article, where he mentions some use cases for MONaaS15:59
aviau#link http://techs.enovance.com/7043/keep-openstack-weird15:59
eglynnaviau: so the HP guys had a lot of feedback on the etherpad also15:59
*** shakayumi is now known as shakamunyi15:59
aviauYou might want to take a look at HP cloud-mon. A recently open-sourced MONaaS solution. It is an example of what we think MONaaS could look like.16:00
eglynnaviau: they gave us an overview of their work at summit16:00
aviau#link https://github.com/hpcloud-mon/mon-arch16:00
eglynnaviau: would it make sense for you to get involved with the HP project?16:00
eglynnaviau: ... apparently it'll soon be moved to stackforge16:00
aviauAbout that,  have started working on the blueprint template and I currently fail to see how we can fit monitoring in the currently proposed Telemetry program mission.16:01
aviauhttps://review.openstack.org/#/c/87526/5/reference/programs.yaml16:01
ildikovwhat about moving to the Ceilo channel with this?16:01
eglynnfolks we've run out of time here, let's move it over to the #openstack-ceilometer channel16:01
ildikovwe ran out of time :(16:01
DinaBelovabye!16:01
*** jmontemayor has joined #openstack-meeting16:02
eglynn#endmeeting ceilometer16:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:02
openstackMeeting ended Thu May 29 16:02:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-05-29-15.00.html16:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-05-29-15.00.txt16:02
openstackLog:            http://eavesdrop.openstack.org/meetings/ceilometer/2014/ceilometer.2014-05-29-15.00.log.html16:02
*** jmontemayor has quit IRC16:02
*** llu-laptop has left #openstack-meeting16:02
*** garyk has quit IRC16:03
*** colinmcnamara has quit IRC16:03
*** colinmcn_ has joined #openstack-meeting16:03
*** jmontemayor has joined #openstack-meeting16:03
*** jmontemayor has quit IRC16:04
*** jmontemayor has joined #openstack-meeting16:04
*** xuhanp has quit IRC16:05
*** sballe_ has quit IRC16:06
*** bdpayne has joined #openstack-meeting16:06
*** Mandell has quit IRC16:07
*** mxin has joined #openstack-meeting16:07
*** colinmcn_ has quit IRC16:08
mxinis this openstack security group irc meeting?16:08
*** zdiN0bot has joined #openstack-meeting16:08
*** cammann has left #openstack-meeting16:08
*** imsurit has joined #openstack-meeting16:08
*** jmontemayor has quit IRC16:08
*** dougw2 has joined #openstack-meeting16:09
*** bdpayne has quit IRC16:10
*** mxin has quit IRC16:11
*** vrovachev has left #openstack-meeting16:11
*** rossk has joined #openstack-meeting16:11
*** rakhmerov has quit IRC16:11
*** kgriffs is now known as kgriffs|afk16:11
*** nati_ueno has joined #openstack-meeting16:12
*** fnaval has quit IRC16:12
*** zhiyan_ is now known as zhiyan16:12
*** colinmcnamara has joined #openstack-meeting16:13
*** marcoemorais has joined #openstack-meeting16:14
*** terryw has joined #openstack-meeting16:14
*** bdpayne has joined #openstack-meeting16:15
*** neelashah has quit IRC16:16
*** blamar has joined #openstack-meeting16:16
*** cdent has left #openstack-meeting16:16
*** otherwiseguy has quit IRC16:17
*** devlaps1 has joined #openstack-meeting16:17
*** gordc has left #openstack-meeting16:17
*** zdiN0bot1 has joined #openstack-meeting16:17
*** Mandell has joined #openstack-meeting16:18
*** zhangleiqiang has quit IRC16:18
*** marcoemorais has quit IRC16:18
*** jmontemayor has joined #openstack-meeting16:19
*** nshaikh has joined #openstack-meeting16:19
*** zhiyan is now known as zhiyan_16:21
*** zdiN0bot has quit IRC16:21
*** cfriesen__ has quit IRC16:21
*** hashar has quit IRC16:22
*** esker has quit IRC16:22
*** esker has joined #openstack-meeting16:22
*** zdiN0bot1 has quit IRC16:24
*** marcoemorais has joined #openstack-meeting16:26
*** nati_ueno has quit IRC16:26
*** liyuezhou_ has quit IRC16:26
*** isviridov is now known as isviridov|away16:26
*** evgenyf has quit IRC16:27
*** jmontemayor_ has joined #openstack-meeting16:27
*** esker has quit IRC16:27
*** jmontemayor has quit IRC16:27
*** jackib has quit IRC16:28
*** neelashah has joined #openstack-meeting16:29
*** zdiN0bot has joined #openstack-meeting16:29
*** jackib has joined #openstack-meeting16:29
*** emagana has quit IRC16:31
*** marcoemorais has quit IRC16:32
*** zhangleiqiang has joined #openstack-meeting16:32
*** marcoemorais has joined #openstack-meeting16:32
*** neelashah has quit IRC16:33
*** colinmcnamara has quit IRC16:34
*** zhangleiqiang has quit IRC16:35
*** devlaps has joined #openstack-meeting16:37
*** emagana has joined #openstack-meeting16:37
*** ArthurBerezin has joined #openstack-meeting16:37
*** ArthurBerezin has left #openstack-meeting16:38
*** neelashah has joined #openstack-meeting16:38
*** vuil has joined #openstack-meeting16:39
*** samuelbercovici1 has joined #openstack-meeting16:39
*** jackib has quit IRC16:40
*** Thurloat has joined #openstack-meeting16:40
*** yogeshmehra has joined #openstack-meeting16:40
*** garyk has joined #openstack-meeting16:41
*** rakhmerov has joined #openstack-meeting16:42
*** samuelbercovici has quit IRC16:42
*** samuelbercovici1 is now known as samuelbercovici16:42
*** gokrokve has joined #openstack-meeting16:42
*** lsmola2 has quit IRC16:43
*** garyk has quit IRC16:44
*** _nadya_ has quit IRC16:44
*** nshaikh has quit IRC16:45
*** garyk has joined #openstack-meeting16:45
*** tsekiyama has joined #openstack-meeting16:45
*** lcheng_ has quit IRC16:46
*** shivharis has joined #openstack-meeting16:47
*** rakhmerov has quit IRC16:47
*** amotoki has quit IRC16:48
*** nelsnelson has quit IRC16:49
*** nelsnelson has joined #openstack-meeting16:49
*** TravT has joined #openstack-meeting16:50
*** jmontemayor_ has quit IRC16:51
*** shivharis has left #openstack-meeting16:51
*** SumitNaiksatam has quit IRC16:54
*** rockyg has joined #openstack-meeting16:55
*** jmontemayor has joined #openstack-meeting16:56
*** jmontemayor has quit IRC16:56
*** IlyaE has quit IRC16:56
*** jmontemayor has joined #openstack-meeting16:56
*** jhenner has quit IRC16:57
*** zdiN0bot has quit IRC16:57
*** chair6 has joined #openstack-meeting16:57
*** chair6 has left #openstack-meeting16:58
*** haoma____ has quit IRC16:58
*** shivharis has joined #openstack-meeting16:58
*** shivharis has left #openstack-meeting16:59
*** Macaveli has quit IRC16:59
*** rockyg has left #openstack-meeting16:59
*** jmontemayor has quit IRC16:59
*** shardy is now known as shardy_afk17:01
*** harlowja_away is now known as harlowja_17:02
*** CristianF has joined #openstack-meeting17:03
*** eglynn has quit IRC17:03
*** Thurloat has left #openstack-meeting17:04
*** sarob has joined #openstack-meeting17:04
*** arnaud has joined #openstack-meeting17:05
*** DrBacchus has joined #openstack-meeting17:05
*** gokrokve_ has joined #openstack-meeting17:07
*** sarob_ has joined #openstack-meeting17:07
*** Leonr has joined #openstack-meeting17:08
*** emaganap has joined #openstack-meeting17:09
*** ominakov has quit IRC17:09
*** rbowen has quit IRC17:10
*** fnaval has joined #openstack-meeting17:10
*** emagana has quit IRC17:10
*** ssurana has joined #openstack-meeting17:11
*** sarob has quit IRC17:11
*** Macaveli has joined #openstack-meeting17:11
*** gokrokve has quit IRC17:12
*** rakhmerov has joined #openstack-meeting17:12
*** SumitNaiksatam has joined #openstack-meeting17:12
*** zhiyan_ is now known as zhiyan17:12
*** zdiN0bot has joined #openstack-meeting17:13
*** jackib has joined #openstack-meeting17:14
*** _nadya_ has joined #openstack-meeting17:14
*** crc32 has joined #openstack-meeting17:15
*** ssurana has quit IRC17:15
*** caleb_ has joined #openstack-meeting17:16
*** DrBacchus is now known as rbowen17:17
*** derekh_ has quit IRC17:18
*** colinmcnamara has joined #openstack-meeting17:19
*** Longgeek has quit IRC17:19
*** terryw is now known as otherwiseguy17:19
*** zhiyan is now known as zhiyan_17:22
*** vivek-ebay has joined #openstack-meeting17:22
*** vivek-eb_ has joined #openstack-meeting17:22
*** IlyaE has joined #openstack-meeting17:22
*** jlibosva has quit IRC17:23
*** jergerber has quit IRC17:23
*** jlibosva has joined #openstack-meeting17:24
*** samuelbercovici1 has joined #openstack-meeting17:25
*** _nadya_ has quit IRC17:25
*** jlibosva has quit IRC17:28
*** sushils has quit IRC17:28
*** samuelbercovici has quit IRC17:28
*** samuelbercovici1 is now known as samuelbercovici17:28
*** caleb_ has quit IRC17:31
*** zdiN0bot has quit IRC17:34
*** balajiiyer has joined #openstack-meeting17:34
*** zdiN0bot has joined #openstack-meeting17:34
*** eghobo has joined #openstack-meeting17:34
*** ildikov has quit IRC17:35
*** arnaud has quit IRC17:35
*** tvoran has quit IRC17:35
*** vivek-ebay has quit IRC17:36
*** vivek-eb_ has quit IRC17:36
*** nati_ueno has joined #openstack-meeting17:37
*** gyee has joined #openstack-meeting17:37
*** vuil has quit IRC17:38
*** ityaptin has quit IRC17:38
*** rudrarugge has quit IRC17:41
*** fnaval has quit IRC17:42
*** colinmcnamara has quit IRC17:42
*** colinmcnamara has joined #openstack-meeting17:45
*** akuznetsov has joined #openstack-meeting17:47
*** vuil has joined #openstack-meeting17:48
*** beagles is now known as beagles_food17:48
*** ssurana has joined #openstack-meeting17:49
*** Mandell has quit IRC17:50
*** ssurana has quit IRC17:50
*** atiwari has joined #openstack-meeting17:51
*** balajiiyer has quit IRC17:51
*** emaganap has quit IRC17:52
*** ssurana has joined #openstack-meeting17:53
*** colinmcnamara has quit IRC17:53
*** emagana has joined #openstack-meeting17:53
*** colinmcnamara has joined #openstack-meeting17:54
*** _nadya_ has joined #openstack-meeting17:55
*** jmontemayor has joined #openstack-meeting17:56
*** jmontemayor has quit IRC17:56
*** jmontemayor has joined #openstack-meeting17:57
*** jmontemayor has quit IRC17:57
*** jmontemayor has joined #openstack-meeting17:58
*** paulmo has joined #openstack-meeting17:58
*** tmcpeak has joined #openstack-meeting17:59
*** yamahata has quit IRC17:59
*** chair6 has joined #openstack-meeting18:00
*** tosky has joined #openstack-meeting18:00
*** nkinder has joined #openstack-meeting18:00
hyakuhei#startmeeting openstack security group18:00
openstackMeeting started Thu May 29 18:00:52 2014 UTC and is due to finish in 60 minutes.  The chair is hyakuhei. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: openstack security group)"18:00
openstackThe meeting name has been set to 'openstack_security_group'18:00
bknudsonhi18:00
*** banix has quit IRC18:01
nkinderhi all18:01
chair6howdy18:01
hyakuheiHi all, roll call :)18:01
bdpayneo/18:01
paulmoPaul Montgomery18:01
tmcpeakhey everybody, Travis McPeak from Symantec here18:01
* hyakuhei Rob from HP18:01
*** sarob_ has quit IRC18:01
*** tosky has left #openstack-meeting18:01
*** edmund1 has quit IRC18:01
*** edmund has joined #openstack-meeting18:01
*** banix has joined #openstack-meeting18:01
*** mxin has joined #openstack-meeting18:01
hyakuheiOk, so I only have one agenda item for today, I presume others have things they want to talk about?18:02
mxinhi, My name is Michael Xin from Rackspace.18:02
paulmoI had one item18:02
paulmoYay, welcome mxin! :)18:02
hyakuheiHi mxin, thanks for joining us!18:02
mxinThanks.18:02
hyakuheipaulmo: great, what was it?18:02
mxinGlad to help.18:02
nkinderhey mxin!18:02
*** dstanek has joined #openstack-meeting18:02
*** esker has joined #openstack-meeting18:02
hyakuheiHey bdpayne, glad to have you back!18:03
paulmoI was starting back on trying to create some OpenStack-wide logging recommendations… starting to edit this to update it: https://wiki.openstack.org/wiki/Security/Guidelines/logging_guidelines18:03
*** esker has quit IRC18:03
bdpaynethanks!18:03
*** susaant has joined #openstack-meeting18:03
paulmoJust had some questions on how we might gain that consensus as a team18:03
tmcpeaklets discuss OSSG meetup in San Antonio if time permits18:03
hyakuheitmcpeak: that's the main thing I want to discuss18:03
mxinThat's cool18:03
tmcpeakoh cool, perfect :)18:03
bknudsonpaulmo: add auth tokens to things not to log18:03
bdpaynerather, OSSG Meeting ... whereever / whenever it may be18:03
hyakuheiindeed.18:03
bdpaynes/Meeting/Meetup/18:04
hyakuheiRight ok, lets talk about logging first18:04
hyakuhei#topic logging18:04
*** openstack changes topic to "logging (Meeting topic: openstack security group)"18:04
paulmoI'm changing that whole page… making diagrams and such.  Check back in a day or so. :)18:04
hyakuhei#link https://wiki.openstack.org/wiki/Security/Guidelines/logging_guidelines18:04
hyakuheipaulmo: do you just want comments, do you need contributions?18:04
paulmoThis topic keeps popping up with plain text credentials in logs and such.  I just wanted to get a feel from the OSSG about tackling some OpenStack-wide standards.18:04
bknudsonpaulmo: is it expected that no logs have passwords, etc., at all levels?18:05
hyakuheiIt's slowly getting weeded out, we keep seeing it in OSSAs. Agree that some guidance needs to be provided18:05
bknudsoneven a trace level?18:05
mxinThat's good start18:05
paulmoThe elevator pitch is: Let's encourage identifying/tagging confidential (non-user data) in the code/through reviews instead of admins trying to chase down that information reactively on the backend log filtering.18:05
mxinPasswords should never be logged anywhere.18:05
hyakuheibknudson: That is my preference but I've seen developers ask for it to stay in debug logs18:05
nkinderI've seen password logging bugs get punted on for client side debug logging18:05
paulmo… and let's create OSSG agreed upon guidelines.  Just my 2 cents. :)18:05
bdpayneyeah, that's a reasonable first step18:06
tmcpeakwhat's the idea behind having them stay in logs?18:06
hyakuheiI think our position should just be don't log passwords mkay?18:06
*** vivek-eb_ has joined #openstack-meeting18:06
*** vivek-ebay has joined #openstack-meeting18:06
bdpaynealthough we may want to work with VMT after we have put together guidelines18:06
hyakuheitmcpeak: Developers thinking they need it for debug18:06
mxinit can be masked like xxxx18:06
hyakuheibdpayne: No harm in getting the VMT's $0.00218:06
tmcpeakhmmm18:06
bdpayneto make sure that they agree... and can help enforce via their bug triage18:06
paulmoThis might be controversial but I do not think log level should have anything to do with relaxing security (logging passwords and such).18:07
hyakuheiSo they already have a pretty good precedent for this18:07
bknudsonkeystone has an "insecure" setting, if you have debug=True in the config18:07
hyakuheipaulmo: +118:07
hyakuheiAuthN failures are pretty obvious, I cant imagine why you'd need to log the detail.18:07
tmcpeakpaulmo: +118:07
paulmobknudson: That at least gives the operator a very definite understanding of what is happening when that config value is set.18:07
hyakuheiOk great. paulmo can you follow up on the ML?18:07
nkinderin addition to logging, we need to worry about audit events (CADF)18:07
bknudsonwhere keystone server will return more info to a client... so was wondering if an insecure setting could log passwords, too18:08
bdpaynebknudson that sounds scary... what else does this insecure setting do?18:08
paulmohyakuhei: Yes, I'm going to get this wiki into shape and then I'll send this out to the ML. :)18:08
bknudsonbdpayne: it is scary18:08
mxinwhat's ML?18:08
nkindermailing list18:08
paulmoMailing List18:08
mxinthanks.18:08
bdpaynepaulmo sounds good, thanks for working on that18:08
mxinI registered the ML, but I never got any email from it.18:09
hyakuheipaulmo: Great work :)18:09
paulmoNo problem; then we can decide the best way to approach the rest of OpenStack once we agree to the general architecture/recommendations.18:09
mxinyes. Great job. Paul!18:09
hyakuheimxin: It's fairly low volume at the moment18:09
mxinic18:09
mxinThanks.18:09
*** susaant has left #openstack-meeting18:09
*** jimo has joined #openstack-meeting18:09
hyakuheiOk, great stuff paulmo, happy for us to move on?18:10
paulmoSure; thanks for the floor!18:10
*** edmund has quit IRC18:10
hyakuhei:)18:10
hyakuhei#topic OSSG Mid-Cycle Meetup18:10
*** openstack changes topic to "OSSG Mid-Cycle Meetup (Meeting topic: openstack security group)"18:10
hyakuheiSo, I think it would be great to have a mid-cycle meetup18:11
*** blogan has left #openstack-meeting18:11
hyakuheifor doing those things that are just too hard to do remotely or where tasks benefit from short periods of intense collaboration18:11
hyakuheiThe book sprint being a great example of this18:11
tmcpeakhyakuhei: +118:11
hyakuheiI spread this around at the summit and the feedback was good.18:12
mxinhyakuhei: +118:12
hyakuheiI spoke to Barbican about us meeting at the same time as those guys seeing as we have so much overlap18:12
hyakuheiThe result is that we've been invited to join the Barbican team when they do their joint meetup with Keystone18:12
hyakuheiHowever, I can't make it, niether can Nkinder and some other folks.18:12
*** balajiiyer has joined #openstack-meeting18:12
hyakuheiSo I'm inclined to host an OSSG mid-cycle separately from the Barbican meetup18:13
*** arnaud has joined #openstack-meeting18:13
mxinsounds good18:13
bdpayneI hear CA is nice in the summer :-)18:13
hyakuheiand those who want to attend the Barbican/Keystone stuff should be able to do so as individuals18:13
hyakuheibdpayne: So is Seattle!18:13
nkinderhyakuhei: I can switch my vacation and make it if it has to happen with Barbican/Keystone18:13
hyakuheiNo lets do our own thing18:13
nkinderok18:13
*** zhiyan_ is now known as zhiyan18:13
hyakuheiIt's Barbicans first mid-cycle and our first one too18:14
*** afazekas has joined #openstack-meeting18:14
hyakuheiLets look maybe to bring them together next time18:14
bdpayneyeah18:14
nkinderBarbican did a meetup in feb with Keystone18:14
hyakuheiCool, so I like the idea of us overlapping18:14
bdpayneshould we aim for sometime in July?18:14
hyakuheibut I'd like us in full strength for our first meetup18:15
hyakuheiLate July/Early August could work well18:15
*** coreywright is now known as coreywright_18:15
bdpayneearly Aug will conflict with DefCon / Blackhat18:15
bdpaynewhich may be an issue with this group18:15
bdpaynealso Usenix Security18:15
*** dkehn has quit IRC18:15
hyakuheiI think we might be a bit grown-up for BH :P18:15
hyakuheiYeah, so lets look at Late July then18:15
*** jimo has quit IRC18:16
hyakuheiI can arrange a location for hosting18:16
tmcpeakwhat are you all thinking timewise? an evening, a couple of days, a week?18:16
hyakuheiHowever if some org that isn't mine wants to propose something I'd be happy with that too18:16
hyakuheitmcpeak: closer to a week18:16
tmcpeakawesome18:16
hyakuheiMaybe a 4 day thing so travel isn't too disruptive18:16
mxinit depends on what we want to achieve18:16
bdpayne+1 for 4 day18:17
*** fabiog has quit IRC18:17
tmcpeak4 day sounds good18:17
nkinderyeah, I was thinking 3-4 days too18:17
*** rakhmerov has quit IRC18:17
mxin3 or 4 days18:17
*** dkehn has joined #openstack-meeting18:17
hyakuheiok so we can work through the agenda to get a good feel for wether it should be 3 or 4 days.18:17
*** colinmcnamara has quit IRC18:17
hyakuheiI know there's lots to be done on the security guide18:17
hyakuheiI think a sprint on the guidelines that paulmo wrote would be useful18:18
hyakuheiI think we need to revist the TA stuff, agree process and get more people involved there too, if we can work out how to do that18:18
hyakuheiI will invite architects from other orgs to come and speak with us, describe their approaches and share their insight18:18
bdpayneTA?18:19
hyakuheiThreat Analysis18:19
bdpaynegotcha18:19
mxinlike threat model18:19
hyakuheiMy hope is that we can get everyone working together, through the OSSG to do threat modelling/analysis for OpenStack18:19
hyakuheimxin: Ya :D18:19
CristianF+1 to include TA18:19
*** Guest53771 has quit IRC18:19
mxincool18:19
hyakuheiThere's probably a bunch of smaller more tactical things we can do18:20
bdpaynethis may also be a good time to spin up 1-2 new efforts18:20
bdpaynelike security testing18:20
bdpayneor ??18:20
mxinWe need someone who know the products very well to have good threat model done.18:20
nkindertesting is a big one...18:20
*** _nadya_ has quit IRC18:20
bdpayneif the right people show up and focus on it, the time can help launch something new18:20
tmcpeakyeah, I've been thinking about some security tests18:20
tmcpeaklow hanging fruit could be a good place to start18:20
*** _nadya_ has joined #openstack-meeting18:20
CristianFprobably a hackaton? :)18:20
tmcpeakshould that go in Tempest or elsewhere?18:20
hyakuheiAbsolutely so we've got a bunch of projects laid out that just need effort18:20
*** tvoran has joined #openstack-meeting18:20
nkinderas Kurt S. said in his e-mail yesterday, guidelines and recommendations only go so far.18:20
bdpayneI'm thinking that a big portion of this will be hackathon (or write-a-thon)18:20
hyakuheinkinder: wanted to do a TLS hackathon to fix all the broken implementations18:20
mxinWe are working on security testing of API18:20
paulmonkinder: +118:21
*** pelix has quit IRC18:21
hyakuheiWriting gate tests for low hanging fruit, use of bad functions etc is something we've been wanting to do for a long time18:21
nkinderhyakuhei: yeah, I want to see how much interest we get on that.  There should be a thread starting on -dev shortly about it.18:21
hyakuheiGreat18:21
bdpayneshould we try to pick a week right now?18:21
bdpayneor perhaps a first and second choice?18:22
tmcpeakprobably better to pick a week sooner than later18:22
nkinderI think an etherpad approach would be a good idea where we can hash out dates18:22
hyakuheiWe could look for something provisionally but it'll go through iterations on the ML I imagine18:22
hyakuheinkinder: +118:22
nkinder...and set agenda items too18:22
bdpayneok18:22
bdpaynepersonally, if I don't nail it down soon then the dates will get taken18:22
nkinderbdpayne: me too18:22
bdpayneI suspect others are similar18:22
mxinagree18:23
tmcpeakyeah, definitely18:23
*** zhiyan is now known as zhiyan_18:23
hyakuhei#action bdpayne to create an etherpad and state his preference for dates for the OSSG meetup18:23
hyakuhei:)18:23
bdpayneheh18:23
bdpayneok18:23
hyakuheiNo reason we can't get the ball rolling in the next few hours18:23
hyakuheiI'll have to work out an appropriate venue18:23
hyakuheiWhere are people spread? Are we mainly west-coast US?18:25
paulmoAustin, TX (help me escape the heat!) :)18:25
mxinI am at San antonio, TX18:25
*** IlyaE has quit IRC18:25
tmcpeakSan Francisco for me18:25
bknudsonrochester, mn18:25
chair6Seattle18:25
nkinderSan Francisco area here too18:26
hyakuheiHmmm. So I guess I'll just have to see what I can get. I imagine we'll be 8-14 people18:26
bdpaynehttps://etherpad.openstack.org/p/ossg-juno-meetup18:26
hyakuhei#link https://wiki.openstack.org/wiki/Security/Guidelines/logging_guidelines18:27
hyakuheiOk, so lets hash out all the details on the etherpad18:27
hyakuheiand look to make a decision very soon18:27
bdpaynehyakuhei adds value with that link ;-)18:27
hyakuheiNow it will show up in the minutes rather than the log18:27
hyakuhei:P18:27
*** zehicle_at_dell has joined #openstack-meeting18:27
paulmoWoot!18:27
bdpayneyeah, but wrong link18:27
bdpayne#link https://etherpad.openstack.org/p/ossg-juno-meetup18:27
nkinderCan I give a quick OSSN update?18:28
*** colinmcnamara has joined #openstack-meeting18:28
*** beagles_food is now known as beagles18:28
tmcpeakplease do18:28
bdpayneI'd like to hear it18:28
hyakuheiSigh. Stupid copy-paste Please do18:28
hyakuheiplease18:28
*** hashar has joined #openstack-meeting18:28
hyakuhei#topic OSSN18:28
*** openstack changes topic to "OSSN (Meeting topic: openstack security group)"18:28
nkinderOSSN-0015 is up for review - https://review.openstack.org/#/c/96540/18:28
hyakuhei:D Nice work nkinder18:28
hyakuhei0014 should be put to bed soon18:29
nkinderI cleaned up some things on OSSN-0014, and it needs one more tweak that was pointed out.18:29
nkinderI'll have a new revision up in 5 minutes18:29
hyakuheiGreat work!18:29
tmcpeakgreat job!18:29
*** arnaud has quit IRC18:29
nkinderThere are a few outstanding OSSNs that need authors18:29
bdpayne14 has been a long haul :-)18:29
nkinderbdpayne: yup18:29
nkinderI'll send out a call to action on the security list in case any new members (or old) are interested18:30
hyakuheinkinder: I'll see if I can get one of our newer members to pick up an OSSN18:30
*** emagana has quit IRC18:30
hyakuheiThey're a great way to get into the whole OpenStack process18:30
nkinderyeah, and I think some of these are pretty easy18:30
mxinwhat's OSSN? Sorry I am new here.18:30
nkinderOpenStack Security Note18:31
bdpayne#link here's the open OSSG tickets https://bugs.launchpad.net/ossn18:31
bdpaynearg.. OSSN ticket18:31
nkinderHere are published examples...18:31
nkinder#link https://wiki.openstack.org/wiki/Security_Notes18:31
mxinGot it. Thanks.18:31
*** emagana has joined #openstack-meeting18:31
hyakuheiSo we haven't officially extended the meeting yet which makes us mostly out of time18:32
*** radez_g0n3 is now known as radez18:32
hyakuhei#topic any other business18:32
*** openstack changes topic to "any other business (Meeting topic: openstack security group)"18:32
paulmoIRC channel for OSSG?18:32
hyakuhei#openstack-security18:32
bdpaynedoes that exist?18:32
paulmoThanks!  Was in another one :)18:32
hyakuheiIt does18:32
* bdpayne is out of date18:33
nkinderbdpayne: you leave for a week and everything changes... :)18:33
hyakuheiSomeone reads the logs ;)18:33
*** morganfainberg is now known as morganfainberg_Z18:33
* bdpayne is still catching up18:33
hyakuheiI know that feeling!18:33
hyakuheiOk, so anyone else for anything else?18:34
hyakuheiThere will be a change in time and meeting length discussed soon18:34
*** emagana has quit IRC18:34
hyakuheiThat'll be on the mailing list though18:34
*** atiwari has quit IRC18:34
bdpayneahh, let's please vote on the time18:34
*** emagana has joined #openstack-meeting18:34
*** rbak has quit IRC18:34
hyakuheiCan't see why we wouldn't - so long as it isn't later than the current meeting I'll be happy18:35
*** ildikov has joined #openstack-meeting18:35
hyakuheiGreat, well thank you everyone for another productive OSSG meeting. I'll distribute the minutes shortly.18:35
*** malini2 has joined #openstack-meeting18:35
tmcpeakthanks everybody18:36
bdpaynecheers18:36
*** chair6 has left #openstack-meeting18:36
CristianFbye18:36
mxinThanks. Nice to meet you all.18:36
hyakuheiOh and don't forget to review OSSN-001518:36
mxinbye18:36
hyakuhei#endmeeting18:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:36
openstackMeeting ended Thu May 29 18:36:20 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-05-29-18.00.html18:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-05-29-18.00.txt18:36
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_security_group/2014/openstack_security_group.2014-05-29-18.00.log.html18:36
*** nkinder has left #openstack-meeting18:37
*** morganfainberg_Z is now known as morganfainberg18:37
*** ssurana has quit IRC18:37
*** sushils has joined #openstack-meeting18:37
*** IlyaE has joined #openstack-meeting18:37
*** rbak has joined #openstack-meeting18:38
*** rbak has quit IRC18:38
*** vuil has quit IRC18:38
*** akuznetsov has quit IRC18:38
*** imsurit has quit IRC18:39
*** vuil has joined #openstack-meeting18:40
*** rbak has joined #openstack-meeting18:41
*** hashar has quit IRC18:41
*** akuznetsov has joined #openstack-meeting18:42
*** samuelbercovici1 has joined #openstack-meeting18:42
*** IlyaE has quit IRC18:44
*** IlyaE has joined #openstack-meeting18:44
*** samuelbercovici has quit IRC18:45
*** samuelbercovici1 is now known as samuelbercovici18:46
*** mxin has quit IRC18:47
*** ssurana has joined #openstack-meeting18:48
*** baoli has quit IRC18:49
*** hashar has joined #openstack-meeting18:49
*** vivek-___ has joined #openstack-meeting18:50
*** vivek-e__ has joined #openstack-meeting18:50
*** IlyaE has quit IRC18:50
*** IlyaE has joined #openstack-meeting18:51
*** vivek-eb_ has quit IRC18:51
*** vivek-ebay has quit IRC18:51
*** jmontemayor has quit IRC18:58
*** mxin has joined #openstack-meeting18:59
*** paulmo has left #openstack-meeting18:59
*** pcm_ has joined #openstack-meeting19:00
*** xwizard has joined #openstack-meeting19:00
*** akuznetsov has quit IRC19:00
*** xwizard is now known as tnurlygayanov_19:00
*** neelashah1 has joined #openstack-meeting19:01
*** thangp has quit IRC19:01
*** neelashah has quit IRC19:03
*** MIDENN_ has quit IRC19:03
*** sseverson has quit IRC19:03
*** leeantho has quit IRC19:03
*** KurtMartin has joined #openstack-meeting19:03
*** pberis1 has joined #openstack-meeting19:03
*** zdiN0bot has quit IRC19:03
*** zdiN0bot1 has joined #openstack-meeting19:03
*** MIDENN_ has joined #openstack-meeting19:03
*** leeantho has joined #openstack-meeting19:04
*** sseverson has joined #openstack-meeting19:05
*** atiwari has joined #openstack-meeting19:05
*** jdurgin has quit IRC19:05
*** pberis has quit IRC19:07
*** kmartin has quit IRC19:07
*** leeantho_ has joined #openstack-meeting19:07
*** jang1 has joined #openstack-meeting19:07
*** mxin has quit IRC19:08
*** fnaval has joined #openstack-meeting19:08
*** samuelbercovici1 has joined #openstack-meeting19:11
*** coasterz has joined #openstack-meeting19:11
*** mattgriffin has joined #openstack-meeting19:12
*** akuznetsov has joined #openstack-meeting19:13
*** coasterz has quit IRC19:14
*** samuelbercovici has quit IRC19:14
*** samuelbercovici1 is now known as samuelbercovici19:14
*** zhiyan_ is now known as zhiyan19:14
*** zdiN0bot1 has quit IRC19:15
*** nati_ueno has quit IRC19:16
*** arnaud has joined #openstack-meeting19:17
*** rakhmerov has joined #openstack-meeting19:18
*** vuil has quit IRC19:18
*** jdurgin has joined #openstack-meeting19:19
*** dprince has quit IRC19:19
*** gokrokve_ has quit IRC19:20
*** hashar has quit IRC19:21
*** akuznetsov has quit IRC19:21
*** dims has joined #openstack-meeting19:21
*** eghobo has quit IRC19:23
*** eghobo has joined #openstack-meeting19:23
*** zhiyan is now known as zhiyan_19:24
*** gokrokve has joined #openstack-meeting19:25
*** arnaud has quit IRC19:25
*** rakhmerov has quit IRC19:26
*** derekh_ has joined #openstack-meeting19:27
*** nati_ueno has joined #openstack-meeting19:28
*** coreywright_ is now known as coreywright19:29
*** jrist has quit IRC19:30
*** coasterz has joined #openstack-meeting19:31
*** mxin has joined #openstack-meeting19:32
*** nati_ueno has quit IRC19:36
*** nati_ueno has joined #openstack-meeting19:36
*** zehicle_at_dell has quit IRC19:38
*** pcm_ has left #openstack-meeting19:40
*** gokrokve has quit IRC19:40
*** gokrokve has joined #openstack-meeting19:41
*** samuelbercovici has quit IRC19:41
*** markwash has joined #openstack-meeting19:43
*** flaper87|afk is now known as flaper8719:44
*** gokrokve has quit IRC19:45
*** jrist has joined #openstack-meeting19:45
*** emagana has quit IRC19:47
*** emagana has joined #openstack-meeting19:47
*** jmontemayor has joined #openstack-meeting19:47
*** jmontemayor has quit IRC19:48
*** _nadya_ has quit IRC19:48
*** jmontemayor has joined #openstack-meeting19:48
*** jmontemayor has quit IRC19:49
*** colinmcnamara has quit IRC19:49
*** jmontemayor has joined #openstack-meeting19:49
*** emagana has quit IRC19:50
*** emagana has joined #openstack-meeting19:51
*** arnaud has joined #openstack-meeting19:52
*** emagana has quit IRC19:52
*** nati_ueno has quit IRC19:54
*** emagana has joined #openstack-meeting19:54
*** baoli has joined #openstack-meeting19:54
*** emagana has quit IRC19:55
*** nati_ueno has joined #openstack-meeting19:57
*** jmontemayor has quit IRC19:57
*** jmontemayor has joined #openstack-meeting19:59
*** fnaval has quit IRC20:00
*** jmontemayor_ has joined #openstack-meeting20:00
*** gokrokve has joined #openstack-meeting20:00
*** colinmcnamara has joined #openstack-meeting20:01
*** nati_ueno has quit IRC20:01
*** rodrigods has quit IRC20:01
*** zdiN0bot has joined #openstack-meeting20:01
*** jmontemayor has quit IRC20:03
*** nati_ueno has joined #openstack-meeting20:03
*** Mikhail_D_ltp has joined #openstack-meeting20:04
*** fnaval has joined #openstack-meeting20:05
*** zdiN0bot has quit IRC20:06
*** zehicle_at_dell has joined #openstack-meeting20:07
*** leeantho_ has quit IRC20:08
*** rbak has quit IRC20:13
*** zhiyan_ is now known as zhiyan20:15
*** nati_ueno has quit IRC20:15
*** vivek-ebay has joined #openstack-meeting20:17
*** vivek-eb_ has joined #openstack-meeting20:17
*** IlyaE has quit IRC20:17
*** IlyaE has joined #openstack-meeting20:17
*** jtomasek has quit IRC20:18
*** derekh_ has quit IRC20:19
*** zehicle_at_dell has quit IRC20:19
*** vivek-___ has quit IRC20:20
*** vivek-e__ has quit IRC20:20
*** ArthurBerezin has joined #openstack-meeting20:20
*** kgriffs|afk is now known as kgriffs20:20
-openstackstatus- NOTICE: Gerrit is going offline to correct an issue with a recent project rename. ETA 20:45 UTC.20:20
*** ChanServ changes topic to "Gerrit is going offline to correct an issue with a recent project rename. ETA 20:45 UTC."20:20
*** jergerber has joined #openstack-meeting20:22
*** ArthurBerezin1 has joined #openstack-meeting20:23
*** Mikhail_D_ltp has quit IRC20:23
*** whenry has quit IRC20:24
*** Mikhail_D_ltp has joined #openstack-meeting20:25
*** edmund has joined #openstack-meeting20:25
*** tmcpeak has left #openstack-meeting20:25
*** eharney has quit IRC20:26
*** zhiyan is now known as zhiyan_20:26
*** ArthurBerezin has quit IRC20:26
*** ArthurBerezin1 has left #openstack-meeting20:31
*** gokrokve has quit IRC20:35
*** zehicle_at_dell has joined #openstack-meeting20:37
*** mwagner_lap has quit IRC20:38
*** Mikhail_D_ltp has quit IRC20:39
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:39
-openstackstatus- NOTICE: Gerrit is back online20:39
*** radez is now known as radez_g0n320:39
*** Realmy has joined #openstack-meeting20:40
*** Mikhail_D_ltp has joined #openstack-meeting20:40
*** malini2 has quit IRC20:40
*** Macaveli has quit IRC20:42
*** chuckC has quit IRC20:44
*** jecarey has quit IRC20:44
*** CristianF has quit IRC20:46
*** gokrokve has joined #openstack-meeting20:47
*** atiwari has quit IRC20:49
*** Mandell has joined #openstack-meeting20:49
*** gokrokve has quit IRC20:50
*** edmund has quit IRC20:51
*** edmund1 has joined #openstack-meeting20:51
*** shakamunyi has quit IRC20:51
*** sushils has quit IRC20:51
*** shakamunyi has joined #openstack-meeting20:52
*** topol has quit IRC20:53
*** jdob has quit IRC20:54
*** rakhmerov has joined #openstack-meeting20:54
*** jecarey has joined #openstack-meeting20:54
*** atiwari has joined #openstack-meeting20:55
*** zdiN0bot has joined #openstack-meeting20:55
*** sushils has joined #openstack-meeting20:55
*** Mikhail_D_ltp has left #openstack-meeting20:56
*** Guest91575 has quit IRC20:57
*** gokrokve has joined #openstack-meeting20:58
*** rakhmerov has quit IRC20:58
*** sarob has joined #openstack-meeting20:59
*** jackib has quit IRC21:01
*** mrmartin has quit IRC21:01
*** flaper87 is now known as flaper87|afk21:03
*** fifieldt has quit IRC21:03
*** sushils has quit IRC21:04
*** sushils has joined #openstack-meeting21:05
*** gokrokve has quit IRC21:06
*** torandu has joined #openstack-meeting21:07
*** aysyd has quit IRC21:07
*** jmontemayor_ has quit IRC21:08
*** pdmars has quit IRC21:10
*** sushils has quit IRC21:13
*** casanch1 has quit IRC21:13
*** shakamunyi has quit IRC21:14
*** sushils has joined #openstack-meeting21:15
*** zhiyan_ is now known as zhiyan21:18
*** arnaud has quit IRC21:18
*** geekinutah has joined #openstack-meeting21:19
*** fifieldt has joined #openstack-meeting21:20
*** vpanizo has joined #openstack-meeting21:22
*** salv-orlando has quit IRC21:24
*** julim has quit IRC21:24
*** eguz has joined #openstack-meeting21:26
*** zhiyan is now known as zhiyan_21:27
*** torandu has left #openstack-meeting21:28
*** Penick has joined #openstack-meeting21:29
*** marcoemorais has quit IRC21:30
*** eghobo has quit IRC21:30
*** nati_ueno has joined #openstack-meeting21:31
*** marcoemorais has joined #openstack-meeting21:31
*** marcoemorais has quit IRC21:31
*** marcoemorais has joined #openstack-meeting21:32
*** salv-orlando has joined #openstack-meeting21:34
*** kinrui has joined #openstack-meeting21:34
*** kinrui has quit IRC21:34
*** salv-orlando has quit IRC21:35
*** malini has joined #openstack-meeting21:36
*** gokrokve has joined #openstack-meeting21:37
*** kgriffs is now known as kgriffs|afk21:37
*** Munish has quit IRC21:37
*** jackib has joined #openstack-meeting21:38
*** gokrokve_ has joined #openstack-meeting21:38
*** eghobo has joined #openstack-meeting21:38
*** eguz_ has joined #openstack-meeting21:39
*** neelashah1 has quit IRC21:39
*** eguz has quit IRC21:39
*** sushils has quit IRC21:39
*** geekinutah has quit IRC21:41
*** gokrokve has quit IRC21:41
*** Realmy has quit IRC21:41
*** sushils has joined #openstack-meeting21:42
*** eghobo has quit IRC21:43
*** gokrokve_ has quit IRC21:43
*** rockyg has joined #openstack-meeting21:46
*** balajiiyer1 has joined #openstack-meeting21:46
*** balajiiyer1 has quit IRC21:46
*** balajiiyer has quit IRC21:48
*** mrda-away is now known as mrda21:48
*** vijendar has quit IRC21:49
*** masayukig has joined #openstack-meeting21:49
*** tris- has joined #openstack-meeting21:51
*** chuckC has joined #openstack-meeting21:52
*** Thurloat has joined #openstack-meeting21:53
*** malini has quit IRC21:53
*** dpaterson has joined #openstack-meeting21:54
*** rakhmerov has joined #openstack-meeting21:55
*** ssurana has quit IRC21:56
*** zdiN0bot has quit IRC21:56
*** ekhugen has joined #openstack-meeting21:57
*** IlyaE has quit IRC21:57
*** IlyaE has joined #openstack-meeting21:58
*** vrovachev has joined #openstack-meeting21:58
*** dims has quit IRC21:58
*** oomichi has joined #openstack-meeting21:58
*** oomichi has quit IRC21:58
*** rakhmerov has quit IRC21:59
*** mlavalle has joined #openstack-meeting21:59
*** ssurana has joined #openstack-meeting22:00
mtreinish#startmeeting qa22:00
openstackMeeting started Thu May 29 22:00:33 2014 UTC and is due to finish in 60 minutes.  The chair is mtreinish. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
*** openstack changes topic to " (Meeting topic: qa)"22:00
openstackThe meeting name has been set to 'qa'22:00
mtreinishhi who's here today?22:00
mlavallehi22:00
vrovachevhi22:00
dpatersonhi22:00
masayukigo/22:00
* clarkb lurks22:00
mtreinish#link https://wiki.openstack.org/wiki/Meetings/QATeamMeeting#Proposed_Agenda_for_May_29_2014_.282200_UTC.2922:00
mtreinish^^^ Today's agenda22:01
mtreinishit's just the boilerplate one today...22:01
*** ylobankov has joined #openstack-meeting22:01
*** gokrokve has joined #openstack-meeting22:01
*** malini has joined #openstack-meeting22:01
* sarob lurks22:01
*** banix has quit IRC22:02
mtreinishok, well let's get started22:02
*** colinmcnamara has quit IRC22:02
mtreinish#topic Specs Review22:02
*** openstack changes topic to "Specs Review (Meeting topic: qa)"22:02
*** jergerber has quit IRC22:02
mtreinishso does anyone have a spec review they'd like to bring up22:02
mtreinishor to discuss22:02
sdagueo/22:02
mtreinishsdague: go ahead22:03
sdagueoh, that was mostly just (I'm here) but while we're at it - https://review.openstack.org/#/c/96445/22:03
sdagueis the write up of the javelin2 overview22:03
*** eguz_ has quit IRC22:03
mtreinishheh, ok well that works out :)22:03
*** eghobo has joined #openstack-meeting22:04
sdagueso right now it mostly demonstrates the cli and the yaml that's being used. Comments welcomed22:04
mtreinish#link https://review.openstack.org/#/c/96445/22:04
sdaguealso breaks down the work chunks expected for the cycle22:04
sdagueeasier read here - http://docs-draft.openstack.org/45/96445/2/check/gate-qa-specs-docs/57ce662/doc/build/html/specs/javelin2.html22:05
mtreinish#link http://docs-draft.openstack.org/45/96445/2/check/gate-qa-specs-docs/57ce662/doc/build/html/specs/javelin2.html22:05
sdaguethat's it unless there are questions22:05
*** zdiN0bot has joined #openstack-meeting22:05
mtreinishI need to look into having a place to publish the specs after they're merged at some point22:06
mtreinishsdague: it looks sane to me, but I'll do a detailed review once it gets a +2 from someone else22:06
*** gokrokve has quit IRC22:06
*** malini has left #openstack-meeting22:07
*** Leonr has quit IRC22:07
mtreinishwhich reminds me we need more reviews on qa-specs in general. Things have felt pretty stagnent on that review queue22:08
mtreinishbut I'll bug people about that after the meeting :)22:08
mtreinishok are there any other spec reviews that people want to bring up?22:08
mlavallemtreinish: I want the team to know I am working on https://review.openstack.org/#/c/95600/. It is for the Neutron scenarios we will be implementing in Juno. It is an early version, but please review it and give feedback22:08
mtreinish#link https://review.openstack.org/#/c/95600/22:09
mlavalleI already got a -1 from yfried. That's what I need at this point, though22:09
*** mxin has left #openstack-meeting22:09
sdaguemtreinish: yeh, I was hoping to get a new unified dashboard with all of that in place. Still haven't quite figured out a way to land project specific dashboards without bugging clarkb22:09
*** weshay has quit IRC22:10
mtreinishmlavalle: it looks like a good start though. That's about what I was expecting for that spec.22:10
mtreinishsdague: yeah having that dashboard might help prioritize things22:10
mlavallecoll, thanks!22:10
*** shakamunyi has joined #openstack-meeting22:11
mtreinishok, if there aren't any other specs to discuss we'll move onto the next topic22:11
* afazekas WIP: https://review.openstack.org/#/c/95794/2/specs/network-debug.rst,cm22:11
mtreinish#link https://review.openstack.org/#/c/95794/2/specs/network-debug.rst,cm22:12
masayukigWIP: https://review.openstack.org/#/c/96163/22:12
masayukig^^^ about tempest server/client/GUI spec22:12
masayukig#link https://review.openstack.org/#/c/96163/22:12
sdaguemasayukig: cool22:12
*** lbragstad has quit IRC22:12
masayukigsdague: thanks :)22:13
*** mrodden has quit IRC22:13
mlavalleafazekas: I'll review it by this weekend22:13
mtreinishmasayukig: oh, I bet that'll be a contentious one :)22:13
mtreinishdon't let jogo see it...22:13
masayukigmtreinish: yeah...22:14
mtreinishafazekas: I'll do a dive down into that at some point22:15
mtreinishI have some concerns about doing out of band debug stuff in tree, like what we have now with the sudo stuff22:15
*** Alexandra_ has joined #openstack-meeting22:16
mtreinishok is that it for specs, or are there any others?22:16
mtreinishok then let's move on22:17
mtreinish#topic Blueprints22:17
*** openstack changes topic to "Blueprints (Meeting topic: qa)"22:17
mtreinishok, does anyone have a blueprint status update22:17
mtreinishI still need to do the blueprint purge22:17
mtreinishbut we have a handful of open bps with specs approved22:17
*** IlyaE has quit IRC22:18
mtreinishsdague: we hit some more branchless tempest edge cases this week right?22:18
*** reed has quit IRC22:18
*** IlyaE has joined #openstack-meeting22:18
*** zhiyan_ is now known as zhiyan22:18
sdagueyeh, ceilometer has a set of tests that are impossibly long in icehouse22:18
sdaguebut work under the juno code22:18
vrovachevyeees :(22:18
sdagueso we need to do some kind of signalling for those in the gate22:19
*** bauzas has quit IRC22:19
sdaguevrovachev: I was actually thinking about this on my bike ride today, would there be a way that we could have some ceilo extension that would give us bogomips of the system?22:20
sdaguebasically an idea of what our event processing rate might be22:20
*** pablosan is now known as zz_pablosan22:20
sdaguethen you could actually ask ceilometer, and know programatically if the tests are viable22:20
mtreinishsdague: just to be a bit harsh we could always rip ceilo out of the icehouse gate to get around this too...22:20
*** bauzas has joined #openstack-meeting22:20
mtreinishbut that should be a last resort, and not something we want to do22:21
sdaguemtreinish: we could, there aren't that many tests anyway, but it makes for a good test case22:21
vrovachevsdague, I think it is unlikely.22:21
*** shakamunyi has quit IRC22:22
*** shakayumi has joined #openstack-meeting22:22
*** nati_ueno has quit IRC22:22
sdaguevrovachev: the issue is I'm not very thrilled about the idea that some magic piece of information is needed to know if this would work in a cloud22:22
sdaguebecause it's not discoverable22:22
sdagueand the thing we were planning to have to use this for was new extensions, which are discoverable22:22
sdagueso this is a very weird thing22:23
mtreinishsdague: we do have other non-discoverable feature flags in the config now22:23
mtreinishnot many though22:23
*** markwash has quit IRC22:23
sdaguemtreinish: not in the feature matrix though22:23
mtreinishthat's fair because most of them don't work in the gate anyway22:23
mtreinishand if they do they default on22:24
*** dims has joined #openstack-meeting22:24
sdagueanyway, can probably take it offline22:24
mtreinishsdague: you're right a prereq for doing this should be having ceilo have some kind of discovery that sql actually works22:24
*** isviridov|away is now known as isviridov22:24
mtreinishsdague: yeah let's take this offline22:24
mtreinishok are there any other bp status updates?22:25
vrovachevI do not know how you can work around this problem in tempest. because problem in the ceilo api in icehouce22:25
mtreinishok if there aren't any other bps let's move on22:26
mtreinish#topic Neutron testing22:26
*** openstack changes topic to "Neutron testing (Meeting topic: qa)"22:26
mtreinishmlavalle: this is your topic right?22:26
mlavallemtreinish: yeah22:26
mlavalleanother couple of api tests merged since last meeting22:27
mlavallewe are at 25 only another 3 to go22:27
mlavalleto complete the set we defined in January22:27
mtreinishmlavalle: we're getting there...22:27
mtreinishhow many new apis were added since that list though?22:27
*** zhiyan is now known as zhiyan_22:27
*** bauzas has quit IRC22:27
mlavallealso made progress this week with fwaas and vpaas scenario tests22:27
mlavallewe will be able to implement in one devstack22:28
*** yamahata has joined #openstack-meeting22:28
mlavalleno need of multinode for those tests22:28
*** ssurana has quit IRC22:28
*** ssurana has joined #openstack-meeting22:29
mlavalleand finally I am tracking what markmcclain is doing as far as nova network parity, in case help is needed22:29
mlavallethat's all I have this week22:29
mtreinishmlavalle: that's too bad I was actually hoping that would be a motivator to actually get someone to set up multinode soon22:29
mtreinishmlavalle: ok, thanks22:29
mtreinishdoes anyone have anything else to add on neutron testing?22:29
mtreinishmlavalle: do you know where we stand with a parallel full run22:29
mlavallemultinode will be needed for other scenarios, so I still see it as my cause22:29
mlavalle:-)22:30
mtreinishbecause I think we need to get that in before we start ramping up more tests?22:30
mlavalleagree22:30
mtreinishI can bug rossella_s and salv_orlando about that later though22:30
mlavalleok22:31
*** bknudson has quit IRC22:31
mtreinishok, if no one else has anything to discuss about neutron testing let's move on22:31
mtreinish#topic Bugs22:31
*** openstack changes topic to "Bugs (Meeting topic: qa)"22:31
*** marcoemorais has quit IRC22:32
mtreinishso I haven't had a chance to look at the bug list lately, I imagine it's grown since our last bug day22:32
*** marcoemorais has joined #openstack-meeting22:32
mtreinishbut does anyone have any bugs they'd like to bring up22:32
*** marcoemorais has quit IRC22:32
mtreinishor anything else to talk about open bugs22:32
*** marcoemorais has joined #openstack-meeting22:33
*** sushils has quit IRC22:33
sdaguenot here, I just want to bug masayukig to take a look at my javelin patches - https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/javelin2,n,z :)22:33
mtreinishheh, ok well that's a good segway into the next topic22:33
*** marcoemorais has quit IRC22:34
mtreinish#topic Critical Reviews22:34
*** openstack changes topic to "Critical Reviews (Meeting topic: qa)"22:34
*** marcoemorais has joined #openstack-meeting22:34
mtreinish#link https://review.openstack.org/#/q/status:open+project:openstack/tempest+branch:master+topic:bp/javelin2,n,z22:34
sdaguenote, we discovered at summit that javelin wasn't doing what we thought22:34
masayukigsdague: sure22:34
mtreinishyes someone look at those22:34
mtreinishjust so sdague stops bugging me about it :)22:34
sdagueso this is an attempt to do a rebuild that will live in tempest that we can call from grenade22:34
sdague:P22:34
mtreinishdoes anyone else have any reviews they'd like to get extra eyes on?22:35
sdaguewell, I'm antsy to start actually testing resources living across upgrades again...22:35
*** gokrokve has joined #openstack-meeting22:35
afazekas#link https://review.openstack.org/#/c/94203/22:35
mtreinishafazekas: yeah that's probably a good fix22:37
*** fnaval has quit IRC22:37
sdagueafazekas: can we simplify that code a bit, map filter, and 2 lambdas are kind of dense22:37
afazekassdague: basically it is copied from the same api test22:38
sdaguewhat about computes = [x for x in hosts if x.service == 'compute']22:38
sdagueand then computes[0].host_name22:38
sdagueafazekas: it's still pretty dense22:38
afazekasok22:38
*** ssurana has quit IRC22:39
mtreinishsdague: heh, I was fine with it, but that'll probably be a bit easier to read22:39
*** sushils has joined #openstack-meeting22:39
mtreinishok are there any other reviews?22:39
sdagueyeh, as someone that spent much of this week reading odd parts of tempest, I'm all for future readability22:39
mtreinish#link https://review.openstack.org/#/c/92606/22:39
mtreinish#link https://review.openstack.org/9251922:40
*** Qiming has joined #openstack-meeting22:40
mtreinishthe first should fix a periodic failure22:40
sdague+2 to the first one22:40
mtreinishand the second has just been sitting for a little bit22:40
mtreinishok well if there aren't any other review, let's open the floor22:41
sdaguethe -1 on that one is probably fair, to respin the readme22:41
*** thedodd has quit IRC22:41
mtreinishsdague: oh I completely missed the -122:41
mtreinishI only saw the +2 sorry22:41
mtreinish#topic Open Discussion22:42
*** openstack changes topic to "Open Discussion (Meeting topic: qa)"22:42
*** arnaud has joined #openstack-meeting22:42
mtreinishok, does anyone have a topic they'd like to bring up that wasn't on the agenda22:42
vrovachevguys, please see sahara api tests https://review.openstack.org/#/c/90101/22:42
mtreinish#link https://review.openstack.org/#/c/90101/22:42
vrovachevthanks :)22:43
sdaguemtreinish: what about a preview of the mid cycle event?22:43
mtreinishoh yeah that's a good idea :)22:44
*** kayaliu_ has joined #openstack-meeting22:44
sdaguewhat's your thinking for both bootstrapping days and the QA dedicated day?22:44
ylobankovvrovachev: :)22:44
mtreinishso for the bootstrapping days it's going to be an overview of both how infra works22:44
mtreinishand an explanation of tempest and grenade22:44
sdague#info QA / Infra Mid Cycle July 14 - 1822:44
mtreinishhow they work etc...22:44
*** crandquist has quit IRC22:45
mtreinishfor the dedicated qa day, I was thinking we either could have a day of f2f discussion22:45
mtreinishor if there was a topic we needed to work through we could have a hacking day22:45
sdagueok, would be interesting to get a rough agenda, even if it's just broken up by "morning / afternoon" topics across the days.22:45
mtreinishsdague: yeah I need to work with jeblair to get more details ironed out22:45
sdaguecoolio22:45
mtreinishI should also say the schedule I posted to the ML is tenantive22:46
mtreinishwe might move things around a bit22:46
sdagueok22:46
mtreinishand steal a bootstrapping day for more qa stuff if we need it22:46
sdaguewell good to get that nailed down soon, as I expect people will be starting to sort out travel soon22:46
mtreinishfor those who missed the post:22:47
mtreinish#link http://lists.openstack.org/pipermail/openstack-dev/2014-May/036262.html22:47
masayukigThe mid-cycle meet-up is interesting! But I need to talk my boss(es) to get the budget.22:47
masayukigGermany is very far from Japan...22:47
mtreinishmlavalle: you're a boss now though :)22:47
masayukigmtreinish: heh :)22:47
*** baoli has quit IRC22:48
mtreinishalso if anyone has suggestions on something they'd like to see for the mid-cycle, please ping me22:48
*** IlyaE has quit IRC22:48
mtreinishok are there any other topics to discuss? otherwise we'll end a little early today22:49
*** zdiN0bot has quit IRC22:49
vrovachevheh, go to sleep :) in Russia 2.49 AM22:50
mtreinishok, well I guess I'll call it for today22:50
mtreinishthanks everyone22:50
mtreinish#endmeeting22:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:50
openstackMeeting ended Thu May 29 22:50:33 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:50
masayukigthanks22:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-05-29-22.00.html22:50
vrovachevthanks :)22:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-05-29-22.00.txt22:50
mlavallesee you22:50
openstackLog:            http://eavesdrop.openstack.org/meetings/qa/2014/qa.2014-05-29-22.00.log.html22:50
*** jackib has quit IRC22:50
ylobankovthanks22:51
*** ekhugen has left #openstack-meeting22:51
*** IlyaE has joined #openstack-meeting22:54
*** prad_ has quit IRC22:54
*** rakhmerov has joined #openstack-meeting22:55
*** nati_ueno has joined #openstack-meeting22:56
*** jackib has joined #openstack-meeting22:56
*** Edward-Zhang has joined #openstack-meeting22:57
*** vrovachev has quit IRC22:58
*** rossk has quit IRC22:59
*** zz_pablosan is now known as pablosan22:59
*** asselin_ has quit IRC23:00
*** markstur__ has quit IRC23:00
*** leeantho has quit IRC23:00
*** sseverson has quit IRC23:00
*** MIDENN_ has quit IRC23:00
*** markstur__ has joined #openstack-meeting23:00
*** asselin_ has joined #openstack-meeting23:00
*** noslzzp has quit IRC23:00
*** leeantho has joined #openstack-meeting23:00
*** kmartin has joined #openstack-meeting23:00
*** rakhmerov has quit IRC23:01
*** mdenny has joined #openstack-meeting23:01
*** mlavalle has quit IRC23:02
*** zdiN0bot has joined #openstack-meeting23:02
*** zdiN0bot has quit IRC23:02
*** kayaliu_ has quit IRC23:02
*** zdiN0bot has joined #openstack-meeting23:03
*** KurtMartin has quit IRC23:04
*** sushils has quit IRC23:04
*** kevinconway has quit IRC23:04
*** jackib has joined #openstack-meeting23:05
*** crandquist has joined #openstack-meeting23:05
*** soulxu1404 has joined #openstack-meeting23:08
*** tvoran has quit IRC23:09
*** derekh_ has joined #openstack-meeting23:09
*** fnaval has joined #openstack-meeting23:13
*** coreywright is now known as coreywright_23:14
*** kayaliu_ has joined #openstack-meeting23:16
*** yogeshmehra has quit IRC23:17
*** yogeshmehra has joined #openstack-meeting23:17
*** david-lyle has quit IRC23:17
*** sarob has quit IRC23:18
*** sarob has joined #openstack-meeting23:19
*** zhiyan_ is now known as zhiyan23:19
*** yamahata has quit IRC23:20
*** yogeshmehra has quit IRC23:22
*** ylobankov has quit IRC23:22
*** sarob has quit IRC23:23
*** dpaterson has quit IRC23:24
*** ddieterly has quit IRC23:27
*** zhiyan is now known as zhiyan_23:28
*** marcoemorais has quit IRC23:31
*** zdiN0bot has quit IRC23:31
*** marcoemorais has joined #openstack-meeting23:32
*** Mandell has quit IRC23:33
*** tsekiyam_ has joined #openstack-meeting23:36
*** atiwari has quit IRC23:38
*** zdiN0bot has joined #openstack-meeting23:38
*** mwagner_lap has joined #openstack-meeting23:39
*** ssurana has joined #openstack-meeting23:40
*** tsekiyama has quit IRC23:40
*** tsekiyam_ has quit IRC23:40
*** Mandell has joined #openstack-meeting23:41
*** chuckC has quit IRC23:41
*** fnaval has quit IRC23:42
*** marcoemorais has quit IRC23:43
*** marcoemorais has joined #openstack-meeting23:43
*** sarob has joined #openstack-meeting23:44
*** derekh_ has quit IRC23:44
*** Mandell has quit IRC23:45
*** elambert has quit IRC23:47
*** sarob_ has joined #openstack-meeting23:48
*** sarob has quit IRC23:48
*** zdiN0bot has quit IRC23:49
*** sarob has joined #openstack-meeting23:50
*** tnurlygayanov_ has quit IRC23:50
*** ddieterly has joined #openstack-meeting23:51
*** chuckC has joined #openstack-meeting23:52
*** sarob_ has quit IRC23:53
*** tinoue has joined #openstack-meeting23:54
*** Mandell has joined #openstack-meeting23:54
*** gokrokve has quit IRC23:54
*** gokrokve has joined #openstack-meeting23:55
*** sarob has quit IRC23:55
*** oomichi has joined #openstack-meeting23:55
*** gokrokve has quit IRC23:55
*** ssurana has quit IRC23:59
*** zhikunliu has joined #openstack-meeting23:59
*** tian has joined #openstack-meeting23:59

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