Tuesday, 2014-05-27

*** edmund has quit IRC00:01
*** edmund has joined #openstack-meeting00:01
*** xuhanp has joined #openstack-meeting00:05
*** kun_huang has joined #openstack-meeting00:06
*** kun_huang has quit IRC00:09
*** HenryG has quit IRC00:11
*** cdub has quit IRC00:11
*** nati_ueno has joined #openstack-meeting00:12
*** xuhanp has quit IRC00:16
*** kenhui has joined #openstack-meeting00:16
*** cdub has joined #openstack-meeting00:16
*** nati_ueno has quit IRC00:17
*** AndChat|27729 has quit IRC00:18
*** nati_uen_ has joined #openstack-meeting00:22
*** matsuhashi has joined #openstack-meeting00:26
*** nati_ue__ has joined #openstack-meeting00:27
*** banix has quit IRC00:29
*** nati_uen_ has quit IRC00:30
*** Mandell has quit IRC00:32
*** nati_ue__ has quit IRC00:32
*** matsuhashi has quit IRC00:33
*** matsuhashi has joined #openstack-meeting00:34
*** nati_uen_ has joined #openstack-meeting00:35
*** xuhanp has joined #openstack-meeting00:36
*** caleb_ has joined #openstack-meeting00:36
*** banix has joined #openstack-meeting00:37
*** zhiyan_ is now known as zhiyan00:38
*** nati_uen_ has quit IRC00:39
*** xianghui has joined #openstack-meeting00:44
*** stevemar has joined #openstack-meeting00:45
*** rakhmerov has joined #openstack-meeting00:47
*** tomoe_ has quit IRC00:47
*** xuhanp has quit IRC00:49
*** rakhmerov has quit IRC00:51
*** gokrokve_ has quit IRC00:51
*** gokrokve has joined #openstack-meeting00:52
*** igor_ has joined #openstack-meeting00:52
*** nati_uen_ has joined #openstack-meeting00:52
*** nati_ue__ has joined #openstack-meeting00:54
*** gokrokve has quit IRC00:56
*** igor_ has quit IRC00:57
*** nati_uen_ has quit IRC00:57
*** nati_ueno has joined #openstack-meeting00:57
*** cdub has quit IRC00:58
*** nati_ue__ has quit IRC00:59
*** nati_ueno has quit IRC00:59
*** nati_ueno has joined #openstack-meeting01:00
*** kayaliu_ has joined #openstack-meeting01:02
*** carl_baldwin_m has quit IRC01:03
*** carl_baldwin_m has joined #openstack-meeting01:03
*** nati_ueno has quit IRC01:04
*** carl_baldwin_m has quit IRC01:07
*** nati_ueno has joined #openstack-meeting01:09
*** yaguang has joined #openstack-meeting01:11
*** cdub has joined #openstack-meeting01:27
*** david-lyle has quit IRC01:30
*** kenhui has quit IRC01:31
*** matsuhashi has quit IRC01:33
*** nati_ueno has quit IRC01:33
*** matsuhashi has joined #openstack-meeting01:34
*** yamahata has joined #openstack-meeting01:37
*** imsurit has joined #openstack-meeting01:40
*** oomichi has joined #openstack-meeting01:40
*** edmund has quit IRC01:41
*** edmund1 has joined #openstack-meeting01:41
*** gokrokve has joined #openstack-meeting01:44
*** nosnos has joined #openstack-meeting01:44
*** edmund1 has quit IRC01:45
*** edmund has joined #openstack-meeting01:45
*** rakhmerov has joined #openstack-meeting01:47
*** gokrokve has quit IRC01:48
*** rakhmerov has quit IRC01:52
*** saschpe has quit IRC01:53
*** igor_ has joined #openstack-meeting01:53
*** saschpe has joined #openstack-meeting01:55
*** igor_ has quit IRC01:57
*** nati_ueno has joined #openstack-meeting02:00
*** jjmb has joined #openstack-meeting02:01
*** persia has quit IRC02:01
*** persia_ has joined #openstack-meeting02:03
*** persia_ is now known as Guest7785002:04
*** persia has joined #openstack-meeting02:04
*** persia is now known as Guest997502:04
*** Guest9975 has joined #openstack-meeting02:04
*** Guest9975 is now known as persia02:04
*** nati_ueno has quit IRC02:10
*** IlyaE has quit IRC02:10
*** cdub has quit IRC02:11
*** tomoe_ has joined #openstack-meeting02:12
*** zz_pablosan is now known as pablosan02:16
*** nati_ueno has joined #openstack-meeting02:19
*** yingjun has joined #openstack-meeting02:22
*** Mandell has joined #openstack-meeting02:22
*** nati_ueno has quit IRC02:25
*** vkmc has quit IRC02:29
*** zhiyan is now known as zhiyan_02:29
*** david-lyle has joined #openstack-meeting02:31
*** pablosan is now known as zz_pablosan02:32
*** nati_ueno has joined #openstack-meeting02:33
*** david-lyle has quit IRC02:35
*** lcheng_ has joined #openstack-meeting02:35
*** mberlin has joined #openstack-meeting02:36
*** mberlin1 has quit IRC02:37
*** HenryG has joined #openstack-meeting02:37
*** gokrokve has joined #openstack-meeting02:41
*** hdd_ has joined #openstack-meeting02:42
*** gokrokve has quit IRC02:46
*** zhiyan_ is now known as zhiyan02:46
*** jjmb has quit IRC02:46
*** rakhmerov has joined #openstack-meeting02:48
*** rakhmero_ has joined #openstack-meeting02:50
*** rakhmerov has quit IRC02:50
*** zhiyan is now known as zhiyan_02:52
*** zhiyan_ is now known as zhiyan02:52
*** igor_ has joined #openstack-meeting02:54
*** igor_ has quit IRC02:58
*** kenhui has joined #openstack-meeting02:59
*** coolsvap|afk is now known as coolsvap03:06
*** kenhui has quit IRC03:08
*** paragan has joined #openstack-meeting03:08
*** paragan has joined #openstack-meeting03:08
*** kenhui has joined #openstack-meeting03:09
*** dims has quit IRC03:16
*** kenhui has quit IRC03:23
*** nosnos has quit IRC03:25
*** yamamoto_ has joined #openstack-meeting03:27
*** eghobo has joined #openstack-meeting03:30
*** david-lyle has joined #openstack-meeting03:32
*** matiu has quit IRC03:32
*** matiu has joined #openstack-meeting03:33
*** matiu has quit IRC03:33
*** matiu has joined #openstack-meeting03:33
*** david-lyle has quit IRC03:36
*** david-lyle has joined #openstack-meeting03:38
*** gokrokve has joined #openstack-meeting03:42
*** david-lyle has quit IRC03:43
*** gokrokve has quit IRC03:46
*** akuznetsov has joined #openstack-meeting03:48
*** igor_ has joined #openstack-meeting03:55
*** igor_ has quit IRC03:59
*** yingjun has quit IRC04:01
*** yingjun has joined #openstack-meeting04:02
*** neelashah has quit IRC04:03
*** yingjun has quit IRC04:06
*** haomaiwa_ has joined #openstack-meeting04:07
*** zhiyan is now known as zhiyan_04:14
*** akuznetsov has quit IRC04:16
*** akuznetsov has joined #openstack-meeting04:18
*** banix has quit IRC04:18
*** zhiyan_ is now known as zhiyan04:21
*** david-lyle has joined #openstack-meeting04:24
*** kayaliu_ has quit IRC04:25
*** IlyaE has joined #openstack-meeting04:28
*** nati_ueno has quit IRC04:31
*** nati_ueno has joined #openstack-meeting04:32
*** TravT has joined #openstack-meeting04:33
*** imsurit has quit IRC04:39
*** haomaiwa_ has quit IRC04:42
*** haomaiwang has joined #openstack-meeting04:42
*** gokrokve has joined #openstack-meeting04:43
*** Longgeek has joined #openstack-meeting04:45
*** nosnos has joined #openstack-meeting04:46
*** gokrokve has quit IRC04:48
*** gokrokve has joined #openstack-meeting04:48
*** IlyaE has quit IRC04:51
*** haomaiw__ has joined #openstack-meeting04:52
*** coolsvap is now known as coolsvap|afk04:54
*** edmund has quit IRC04:55
*** haomaiwang has quit IRC04:55
*** igor_ has joined #openstack-meeting04:55
*** ildikov has quit IRC04:56
*** yingjun has joined #openstack-meeting04:58
*** igor_ has quit IRC05:00
*** lcheng_ has quit IRC05:01
*** rakhmero_ is now known as rakhmerov05:05
*** hdd_ has quit IRC05:08
*** vkdrao has joined #openstack-meeting05:12
*** xianghui has quit IRC05:17
*** gokrokve has quit IRC05:17
*** IlyaE has joined #openstack-meeting05:17
*** gokrokve has joined #openstack-meeting05:18
*** Mandell has quit IRC05:22
*** gokrokve has quit IRC05:22
*** nshaikh has joined #openstack-meeting05:23
*** Longgeek has quit IRC05:25
*** uaberme has joined #openstack-meeting05:30
*** IlyaE has quit IRC05:31
*** TravT has quit IRC05:33
*** Mandell has joined #openstack-meeting05:34
*** SridharG has joined #openstack-meeting05:37
*** zhiyan is now known as zhiyan_05:40
*** ildikov has joined #openstack-meeting05:40
*** zhiyan_ is now known as zhiyan05:41
*** lcheng_ has joined #openstack-meeting05:43
*** eghobo has quit IRC05:44
*** _nadya_ has joined #openstack-meeting05:46
*** gokrokve has joined #openstack-meeting05:48
*** coolsvap|afk is now known as coolsvap05:50
*** lcheng_ has quit IRC05:52
*** ArthurBerezin has joined #openstack-meeting05:53
*** gokrokve has quit IRC05:54
*** igor_ has joined #openstack-meeting05:56
*** caleb_ has quit IRC05:59
*** igor_ has quit IRC06:00
*** mrunge has joined #openstack-meeting06:03
*** IlyaE has joined #openstack-meeting06:04
*** brucer has quit IRC06:04
*** ArthurBerezin has quit IRC06:05
*** ArthurBerezin has joined #openstack-meeting06:05
*** xuhanp has joined #openstack-meeting06:05
*** _nadya_ has quit IRC06:08
*** Mikhail_D_ltp has joined #openstack-meeting06:09
*** ArthurBerezin has quit IRC06:10
*** _nadya_ has joined #openstack-meeting06:11
*** paragan has quit IRC06:12
*** paragan has joined #openstack-meeting06:17
*** doron_afk has joined #openstack-meeting06:23
*** dstanek_zzz is now known as dstanek06:24
*** Macaveli has joined #openstack-meeting06:30
*** gpocentek has quit IRC06:31
*** LIYUEZHOU has joined #openstack-meeting06:32
*** gpocentek has joined #openstack-meeting06:34
*** stevemar has quit IRC06:34
*** evgenyf has joined #openstack-meeting06:34
*** belmoreira has joined #openstack-meeting06:42
*** mrunge has quit IRC06:43
*** gokrokve has joined #openstack-meeting06:49
*** hemna_ has quit IRC06:50
*** jtomasek has joined #openstack-meeting06:52
*** I159 has joined #openstack-meeting06:52
*** I159_ has joined #openstack-meeting06:52
*** gokrokve has quit IRC06:54
*** david-lyle has quit IRC06:54
*** sushils has joined #openstack-meeting06:56
*** igor_ has joined #openstack-meeting06:57
*** dstanek is now known as dstanek_zzz07:00
*** igor_ has quit IRC07:01
*** Fdot has joined #openstack-meeting07:03
*** msdubov has quit IRC07:03
*** boris-42 has quit IRC07:03
*** egallen has joined #openstack-meeting07:03
*** sushils has quit IRC07:05
*** afazekas has joined #openstack-meeting07:08
*** cerndev has joined #openstack-meeting07:09
*** yogeshmehra has joined #openstack-meeting07:10
*** msdubov has joined #openstack-meeting07:11
*** boris-42 has joined #openstack-meeting07:11
*** Edward-Zhang has joined #openstack-meeting07:15
*** jtomasek has quit IRC07:15
*** jtomasek has joined #openstack-meeting07:15
*** jcoufal has joined #openstack-meeting07:17
*** salv-orlando has joined #openstack-meeting07:17
*** nati_ueno has quit IRC07:18
*** nati_ueno has joined #openstack-meeting07:19
*** hashar has joined #openstack-meeting07:19
*** haomaiw__ has quit IRC07:20
*** Longgeek has joined #openstack-meeting07:22
*** markmcclain has joined #openstack-meeting07:23
*** nati_ueno has quit IRC07:23
*** yamamoto_ has quit IRC07:24
*** xianghui has joined #openstack-meeting07:25
*** d0ugal_ has quit IRC07:25
*** flaper87|afk is now known as flaper8707:26
*** IlyaE has quit IRC07:28
*** pradipta_away is now known as pradipta07:28
*** jtomasek has quit IRC07:29
*** ttrifonov_zZzz is now known as ttrifonov07:30
*** jlibosva has joined #openstack-meeting07:31
*** phil_ has joined #openstack-meeting07:31
*** uaberme has quit IRC07:34
*** markmcclain has quit IRC07:35
*** IlyaE has joined #openstack-meeting07:35
*** sushils_ has joined #openstack-meeting07:39
*** ArthurBerezin has joined #openstack-meeting07:39
*** ygbo has joined #openstack-meeting07:40
*** matrohon has joined #openstack-meeting07:43
*** akuznetsov has quit IRC07:43
*** ArthurBerezin has left #openstack-meeting07:44
*** amotoki has joined #openstack-meeting07:49
*** gokrokve has joined #openstack-meeting07:49
*** nati_ueno has joined #openstack-meeting07:50
*** Longgeek has quit IRC07:54
*** gokrokve has quit IRC07:54
*** nati_ueno has quit IRC07:54
*** safchain has joined #openstack-meeting07:54
*** belmoreira1 has joined #openstack-meeting07:58
*** belmoreira has quit IRC07:59
*** nacim has joined #openstack-meeting08:02
*** jgallard has joined #openstack-meeting08:04
*** Mandell has quit IRC08:06
*** akuznetsov has joined #openstack-meeting08:09
*** derekh_ has joined #openstack-meeting08:17
*** rakhmerov has quit IRC08:17
*** IlyaE has quit IRC08:17
*** coolsvap is now known as coolsvap|afk08:34
*** yingjun_ has joined #openstack-meeting08:35
*** yingjun__ has joined #openstack-meeting08:36
*** yingjun_ has quit IRC08:36
*** yingjun has quit IRC08:36
*** Mandell has joined #openstack-meeting08:39
*** igor_ has joined #openstack-meeting08:41
*** Mandell has quit IRC08:44
*** mrda is now known as mrda_away08:45
*** coolsvap|afk is now known as coolsvap08:45
*** nosnos has quit IRC08:48
*** rakhmerov has joined #openstack-meeting08:48
*** nosnos has joined #openstack-meeting08:48
*** mberlin1 has joined #openstack-meeting08:49
*** gokrokve has joined #openstack-meeting08:49
*** nati_ueno has joined #openstack-meeting08:50
*** mberlin has quit IRC08:51
*** mrunge has joined #openstack-meeting08:52
*** nosnos has quit IRC08:53
*** gokrokve has quit IRC08:53
*** nati_ueno has quit IRC08:55
*** pradipta is now known as pradipta_away08:55
*** andreaf has joined #openstack-meeting08:59
*** Longgeek has joined #openstack-meeting09:00
*** Longgeek has quit IRC09:00
*** Longgeek has joined #openstack-meeting09:00
*** rakhmerov has quit IRC09:02
*** nelsnelson has joined #openstack-meeting09:07
*** igordcard has joined #openstack-meeting09:10
*** jtomasek has joined #openstack-meeting09:14
*** xuhanp has quit IRC09:19
*** egallen has quit IRC09:21
*** amotoki has quit IRC09:22
*** ttrifonov is now known as ttrifonov_zZzz09:22
*** egallen has joined #openstack-meeting09:23
*** evgenyf has quit IRC09:23
*** deepakcs has joined #openstack-meeting09:24
*** egallen has quit IRC09:24
*** Edward-Zhang has quit IRC09:26
*** idegtiarov has joined #openstack-meeting09:26
*** egallen has joined #openstack-meeting09:27
*** egallen has quit IRC09:27
*** rakhmerov has joined #openstack-meeting09:28
*** egallen has joined #openstack-meeting09:30
*** ttrifonov_zZzz is now known as ttrifonov09:30
*** xuhanp has joined #openstack-meeting09:31
*** yogeshmehra has quit IRC09:31
*** rakhmerov has quit IRC09:33
*** nosnos has joined #openstack-meeting09:35
*** salv-orlando_ has joined #openstack-meeting09:35
*** yingjun__ has quit IRC09:36
*** yingjun has joined #openstack-meeting09:36
*** salv-orlando has quit IRC09:37
*** salv-orlando_ is now known as salv-orlando09:37
*** egallen has quit IRC09:37
*** kun_huang has joined #openstack-meeting09:38
*** zhiyan is now known as zhiyan_09:39
*** egallen has joined #openstack-meeting09:40
*** yingjun has quit IRC09:41
*** rakhmerov has joined #openstack-meeting09:44
*** ttrifonov is now known as ttrifonov_zZzz09:46
*** nacim has quit IRC09:47
*** Mikhail_D_ltp has quit IRC09:48
*** evgenyf has joined #openstack-meeting09:49
*** gokrokve has joined #openstack-meeting09:49
*** gokrokve_ has joined #openstack-meeting09:51
*** nati_ueno has joined #openstack-meeting09:51
*** gokrokve has quit IRC09:53
*** ttrifonov_zZzz is now known as ttrifonov09:54
*** nati_ueno has quit IRC09:55
*** gokrokve_ has quit IRC09:55
*** haomaiwang has joined #openstack-meeting09:57
*** matsuhashi has quit IRC09:58
*** belmoreira1 has quit IRC09:58
*** ttrifonov is now known as ttrifonov_zZzz09:59
*** ttrifonov_zZzz is now known as ttrifonov09:59
*** che-arne has joined #openstack-meeting09:59
*** matsuhashi has joined #openstack-meeting10:00
*** coolsvap is now known as coolsvap|afk10:00
*** belmoreira has joined #openstack-meeting10:01
*** nacim has joined #openstack-meeting10:01
*** ttrifonov is now known as ttrifonov_zZzz10:02
*** nacim has quit IRC10:03
*** ttrifonov_zZzz is now known as ttrifonov10:03
*** nacim has joined #openstack-meeting10:04
*** matsuhashi has quit IRC10:07
*** nosnos has quit IRC10:07
*** matsuhashi has joined #openstack-meeting10:07
*** jgallard has quit IRC10:08
*** jgallard has joined #openstack-meeting10:08
*** matsuhashi has quit IRC10:12
*** jgallard has quit IRC10:13
*** xuhanp has quit IRC10:14
*** hdd_ has joined #openstack-meeting10:23
*** gmatefi has joined #openstack-meeting10:23
*** ominakov has joined #openstack-meeting10:24
*** paragan has quit IRC10:26
*** maxdml has joined #openstack-meeting10:27
*** salv-orlando has quit IRC10:29
*** vkdrao has quit IRC10:29
*** ArthurBerezin has joined #openstack-meeting10:31
*** ArthurBerezin has left #openstack-meeting10:31
*** nacim_ has joined #openstack-meeting10:31
*** nacim has quit IRC10:33
*** tomoe_ has quit IRC10:34
*** _nadya_ has quit IRC10:44
*** yingjun has joined #openstack-meeting10:45
*** yingjun has quit IRC10:47
*** yingjun has joined #openstack-meeting10:47
*** yingjun_ has joined #openstack-meeting10:49
*** gokrokve has joined #openstack-meeting10:49
*** yingjun_ has quit IRC10:49
*** SridharG has quit IRC10:51
*** nati_ueno has joined #openstack-meeting10:52
*** yingjun has quit IRC10:52
*** gokrokve has quit IRC10:53
*** nati_ueno has quit IRC10:56
*** tomoe_ has joined #openstack-meeting11:01
*** tomoe_ has quit IRC11:01
*** tomoe_ has joined #openstack-meeting11:02
*** igordcard has quit IRC11:02
*** egallen has quit IRC11:09
*** tomoe_ has quit IRC11:10
*** zhiyan_ is now known as zhiyan11:17
*** vpanizo has quit IRC11:21
*** jjmb has joined #openstack-meeting11:25
*** dims has joined #openstack-meeting11:28
*** 20WAAGQA1 is now known as shadower11:28
*** haomaiwang has quit IRC11:29
*** safchain has quit IRC11:31
*** haomaiwang has joined #openstack-meeting11:32
*** haomaiwang has quit IRC11:32
*** haomaiwang has joined #openstack-meeting11:34
*** safchain has joined #openstack-meeting11:36
*** paragan has joined #openstack-meeting11:36
*** paragan has quit IRC11:36
*** paragan has joined #openstack-meeting11:36
*** yamahata has quit IRC11:36
*** haomaiwang has quit IRC11:38
*** haomaiwang has joined #openstack-meeting11:40
*** hdd_ has quit IRC11:42
*** haomaiwang has quit IRC11:44
*** haomaiwang has joined #openstack-meeting11:49
*** salv-orlando has joined #openstack-meeting11:49
*** gokrokve has joined #openstack-meeting11:49
*** deepakcs has quit IRC11:50
*** vkmc has joined #openstack-meeting11:51
*** vkmc has quit IRC11:51
*** vkmc has joined #openstack-meeting11:51
*** xianghui has quit IRC11:51
*** haomaiw__ has joined #openstack-meeting11:51
*** haomaiw__ has quit IRC11:52
*** haomaiwang has quit IRC11:53
*** gokrokve has quit IRC11:53
*** jgallard has joined #openstack-meeting11:54
*** nati_uen_ has joined #openstack-meeting11:55
*** _nadya_ has joined #openstack-meeting11:55
*** haomaiwang has joined #openstack-meeting11:57
*** haomaiwang has quit IRC11:57
*** weshay has joined #openstack-meeting11:58
*** nati_uen_ has quit IRC11:59
*** _nadya__ has joined #openstack-meeting12:00
*** _nadya_ has quit IRC12:00
*** haomaiwang has joined #openstack-meeting12:01
*** haomaiwang has quit IRC12:01
*** ArxCruz has joined #openstack-meeting12:02
*** belmoreira has quit IRC12:03
*** SridharG has joined #openstack-meeting12:03
*** gmatefi has quit IRC12:04
*** belmoreira has joined #openstack-meeting12:05
*** jhenner has quit IRC12:05
*** jhenner has joined #openstack-meeting12:05
*** doron_afk is now known as doron12:05
*** ttrifonov is now known as ttrifonov_zZzz12:06
*** afazekas has quit IRC12:07
*** salv-orlando has quit IRC12:07
*** mwagner_lap has quit IRC12:08
*** ttrifonov_zZzz is now known as ttrifonov12:10
*** flaper87 is now known as flaper87|afk12:11
*** markvoelker has quit IRC12:12
*** haomaiwang has joined #openstack-meeting12:13
*** haomaiwang has quit IRC12:13
*** markvoelker has joined #openstack-meeting12:14
*** dstanek_zzz is now known as dstanek12:14
*** yaguang has quit IRC12:14
*** jjmb has quit IRC12:15
*** haomaiwang has joined #openstack-meeting12:17
*** haomaiwang has quit IRC12:17
*** dprince has joined #openstack-meeting12:18
*** haomaiwang has joined #openstack-meeting12:19
*** dims has quit IRC12:20
*** rakhmerov has quit IRC12:21
*** afazekas has joined #openstack-meeting12:21
*** cerndev has quit IRC12:24
*** dprince has quit IRC12:25
*** dprince has joined #openstack-meeting12:26
*** haomaiwang has quit IRC12:27
*** salv-orlando has joined #openstack-meeting12:27
*** haomaiwang has joined #openstack-meeting12:28
*** haomaiwang has quit IRC12:29
*** jjmb has joined #openstack-meeting12:29
*** jjmb has quit IRC12:30
*** bswartz has quit IRC12:30
*** haomaiwa_ has joined #openstack-meeting12:30
*** haomaiwa_ has quit IRC12:30
*** afazekas is now known as _afazekas_mtg12:31
*** rakhmerov has joined #openstack-meeting12:32
*** haomaiwa_ has joined #openstack-meeting12:32
*** aysyd has joined #openstack-meeting12:33
*** rakhmerov has quit IRC12:33
*** rakhmerov has joined #openstack-meeting12:33
*** jdob has joined #openstack-meeting12:33
*** paragan has quit IRC12:37
*** haomaiwa_ has quit IRC12:37
*** neelashah has joined #openstack-meeting12:38
*** erlon has joined #openstack-meeting12:40
*** belmoreira has quit IRC12:41
*** dstanek is now known as dstanek_zzz12:41
*** egallen has joined #openstack-meeting12:42
*** yamahata has joined #openstack-meeting12:42
*** cerndev has joined #openstack-meeting12:43
*** haomaiw__ has joined #openstack-meeting12:43
*** eharney has joined #openstack-meeting12:43
*** haomaiw__ has quit IRC12:44
*** haomaiwang has joined #openstack-meeting12:44
*** haomaiwang has quit IRC12:45
*** dims has joined #openstack-meeting12:45
*** yamahata has quit IRC12:45
*** che-arne has quit IRC12:45
*** yamahata has joined #openstack-meeting12:46
*** luis_fdez has joined #openstack-meeting12:46
*** gokrokve has joined #openstack-meeting12:49
*** haomaiwang has joined #openstack-meeting12:50
*** cerndev has left #openstack-meeting12:50
*** dstanek_zzz is now known as dstanek12:50
*** haomaiwang has quit IRC12:50
*** cerndev has joined #openstack-meeting12:50
*** haomaiwang has joined #openstack-meeting12:51
*** salv-orlando has quit IRC12:51
*** rakhmerov has quit IRC12:52
*** haomaiwang has quit IRC12:52
*** haomaiwang has joined #openstack-meeting12:53
*** haomaiwang has quit IRC12:53
*** rbowen has joined #openstack-meeting12:53
*** jgrimm has quit IRC12:53
*** gokrokve has quit IRC12:54
*** nati_ueno has joined #openstack-meeting12:55
*** rpodolyaka has joined #openstack-meeting12:56
*** radez_g0n3 is now known as radez12:56
*** rakhmerov has joined #openstack-meeting12:57
*** akamyshnikova has joined #openstack-meeting12:57
*** noslzzp has joined #openstack-meeting12:58
*** ArthurBerezin has joined #openstack-meeting12:58
jlibosvahello12:59
akamyshnikovahi12:59
mesteryo/12:59
rpodolyakao/12:59
*** nati_ueno has quit IRC13:00
*** baoli has joined #openstack-meeting13:00
HenryGHi all!13:00
HenryG(Hoping to see salv-orlando and markmcclain here soon)13:01
*** itzikb has joined #openstack-meeting13:01
HenryGLet's get started and hope they show up13:02
HenryG#startmeeting neutron_db13:02
openstackMeeting started Tue May 27 13:02:34 2014 UTC and is due to finish in 60 minutes.  The chair is HenryG. Information about MeetBot at http://wiki.debian.org/MeetBot.13:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:02
*** openstack changes topic to " (Meeting topic: neutron_db)"13:02
*** rakhmerov has quit IRC13:02
openstackThe meeting name has been set to 'neutron_db'13:02
HenryG#topic Introduction13:02
*** jhenner has quit IRC13:02
*** openstack changes topic to "Introduction (Meeting topic: neutron_db)"13:02
HenryGsalv-orlando has called into question the need for this weekly meeting and forming a "subteam".13:03
HenryGThe TC identified the Neutron DB migrations has the #0 priority Gap (higher than the #1 priority Gap) for nova-network parity.13:03
HenryG#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Neutron_Gap_Coverage13:03
*** jhenner has joined #openstack-meeting13:03
*** carl_baldwin_m has joined #openstack-meeting13:03
HenryGWe need to make sure this work gets done correctly and on time.13:03
HenryGI agree it's not really a subteam. If we are efficient the meetings and "subteam" can be dissolved soon.13:03
mesteryI think a sub-team operating until #0 is fixed is warranted HenryG.13:03
*** _afazekas_mtg has quit IRC13:04
*** jhenner has quit IRC13:04
HenryGSure. Let's keep the red tape to a minimum though.13:04
HenryGI'll try to stay out of everyone's way while tracking progress and removing obstacles where I can.13:04
HenryGDo not wait on me or postpone work until the next meeting if there is something that needs to be hashed out.13:05
*** haomaiwang has joined #openstack-meeting13:05
*** haomaiwang has quit IRC13:05
HenryGPlease use the mailing list and IRC effectively.13:05
HenryGAllright, let's go through the agenda.13:05
HenryG#link https://wiki.openstack.org/wiki/Meetings/NeutronDB#Agenda13:05
*** julim has joined #openstack-meeting13:05
HenryG#topic Plan/Design13:05
*** openstack changes topic to "Plan/Design (Meeting topic: neutron_db)"13:05
HenryGThe plan we discussed at the summit is written in the etherpad13:05
HenryG#link https://etherpad.openstack.org/p/neutron-db-migrations13:05
*** haomaiwang has joined #openstack-meeting13:05
*** haomaiwang has quit IRC13:06
HenryGI am writing a spec for the work.13:06
HenryG#action HenryG to write a spec and submit to neutron-specs.13:06
jlibosvaoh, I was active and tried to write it: https://review.openstack.org/#/c/95738/13:06
HenryGIt is not clear to me what the final design will be.13:06
akamyshnikovaI've got some drafts on this topic.13:06
jlibosvait's really a very first draft though13:06
*** haomaiwang has joined #openstack-meeting13:06
*** haomaiwang has quit IRC13:07
*** jcoufal has quit IRC13:07
HenryGjlibosva: Great! No problem. We can use yours. We'll build on it until it is OK.13:07
*** jcoufal_ has joined #openstack-meeting13:07
*** carl_baldwin_m has quit IRC13:07
*** carl_baldwin_m has joined #openstack-meeting13:07
*** haomaiwang has joined #openstack-meeting13:08
akamyshnikovaI create a kind of plan where are shown some options #link https://docs.google.com/a/mirantis.com/document/d/10p6JKIQf_rymBuNeOywjHiv53cRTfz5kBg8LeUCeykI/edit13:08
*** haomaiwang has quit IRC13:08
HenryGSorry I missed it. My laptop was stolen and I lost track of some happenings in the community for a week or so.13:08
HenryGakamyshnikova: Thanks for that!13:09
*** haomaiwa_ has joined #openstack-meeting13:09
*** haomaiwa_ has quit IRC13:09
HenryGSo let's continue discussing on the ML and IRC about those options.13:10
rpodolyakaakamyshnikova: 2 looks hard to implement (as you would need to write this non-trivial conditional logic in SQL)13:10
*** haomaiwa_ has joined #openstack-meeting13:10
*** haomaiwa_ has quit IRC13:10
rpodolyakaakamyshnikova: we could probably assume we stick to online migrations for this one13:10
rpodolyakaakamyshnikova: 1 is doable, but I don't think we should go through all these steps13:11
akamyshnikovaI created some test changes too. But today I was told about one more option that I didn't check how to use, it is number 3 in the list, but it could be the best decision.13:11
rpodolyakaas still you would need to compare every single column of every single table and do an 'update' (which can be: change type, change default value, etc)13:11
HenryGExcuse my ignorance, but other than developers, who uses offline migrations?13:12
*** mberlin1 has quit IRC13:12
rpodolyakaHenryG: in theory, DBAs :)13:12
rpodolyakaakamyshnikova: so what I'm trying to say here is that all this is already implemented in alembic13:12
rpodolyakaso alembic provides support for autogeneration of migration scripts13:13
*** xuhanp has joined #openstack-meeting13:13
*** changbl has quit IRC13:13
rpodolyakait basically takes your metadata (which you defined in terms of model definitions) and compares it to the current state of the database13:13
*** jhenner has joined #openstack-meeting13:13
rpodolyaka(it reflects the DB schema by the means of SQLAlchemy)13:13
rpodolyakathen it compares two SQLAlchemy MetaData instances and generate a list of differences13:14
*** banix has joined #openstack-meeting13:14
rpodolyakanew indexes, new tables, changes of types, default values, etc13:14
jlibosvarpodolyaka: will autogenerate work after removing register_models() ?13:14
jlibosvarpodolyaka: sorry, stupid question. Disregard13:14
*** oomichi has quit IRC13:14
rpodolyakajlibosva: yep, it has nothing to do with it13:14
akamyshnikovarpodolyaka, yeah, I see this. I think I will research this option tomorrow.13:15
rpodolyakathen, for each difference it generates a corresponding alembic operation13:15
rpodolyakaop.alter_column(), op.create_constraint(), etc13:16
rpodolyakaI think, this will cover 90% of problems we have13:16
rpodolyakathere is probably just a few cases left13:16
*** _afazekas_mtg has joined #openstack-meeting13:16
rpodolyakae.g. ENUMs in PostgreSQL (AFAIK, these are not reflected by SQLAlchemy)13:16
*** haomaiwang has joined #openstack-meeting13:16
rpodolyakanot sure if have migrations changing ENUMs though13:17
rpodolyakaso I'd try to use alembic for this first13:17
*** haomaiwang has quit IRC13:17
HenryGrpodolyaka: And it will generate a "downgrade" too, for those who chicken out and want to go back?13:17
rpodolyakaHenryG: haven't checked that, but probably yes13:17
akamyshnikovarpodolyaka, there are migrations that change enums13:18
jlibosvaaren't all/most of current migration scripts created by autogenerate?13:19
rpodolyakaakamyshnikova: ah... so we should either add fixes for those manually or teach SQLAlchemy/alembic how to treat ENUMs13:19
rpodolyakajlibosva: yep13:19
*** _afazekas_mtg is now known as afazekas13:19
HenryGHow does this fit with salv-orlando's idea here: http://lists.openstack.org/pipermail/openstack-dev/2014-May/035567.html ?13:19
rpodolyakaI like salv-orlando's idea that this should be done in a migration script rather than by a separate call13:21
*** _nadya__ has quit IRC13:21
HenryGThere are many good ideas, but we need to converge.13:21
*** tomoe_ has joined #openstack-meeting13:21
*** carl_baldwin_m has quit IRC13:22
rpodolyakashould not be a problem, but I'll need to take a look at alembic API first. there are a few cases, when you have to call alembic commands instead of doing calls programatically from Python13:22
*** haomaiwang has joined #openstack-meeting13:22
*** carl_baldwin_m has joined #openstack-meeting13:22
*** jaypipes has joined #openstack-meeting13:22
jlibosvait could be a separate executable module with ability to import and re-use in neutron-db-manage13:22
*** haomaiwang has quit IRC13:22
*** trey_h has joined #openstack-meeting13:23
*** carl_baldwin_m has quit IRC13:23
jlibosvathis way you can heal on demand and be part of automatic upgrade13:23
rpodolyakafwiw, this is just my two cents. I believe, this will be easier to implement than write schema comparison from scratch13:23
*** mberlin has joined #openstack-meeting13:24
*** haomaiwa_ has joined #openstack-meeting13:24
*** haomaiwa_ has quit IRC13:24
akamyshnikovaI think that I need to look deeply in alembic.13:24
HenryGrpodolyaka: It certainly makes sense to me.13:24
*** jecarey has quit IRC13:25
rpodolyakawe use alembic to do schema comparison in oslo-db so that we can show differences between your models definitions and migration scripts13:25
HenryG#action rpodolyaka, akamyshnikova, jlibosva to investigate and propose solution using alembic for schema comparison and base script.13:26
akamyshnikovathis script is used in my work about sync models and migrations13:26
*** haomaiwang has joined #openstack-meeting13:26
rpodolyakaso far it worked good for us (just a few tweaks needed, e.g. tell it to compare server default values, or tell it that TINYINT(1) is a valid BOOLEAN column for MySQL, and things like that)13:26
*** haomaiwang has quit IRC13:26
HenryGLet's keep everyone in the loop with discussions in the ML and IRC.13:26
rpodolyakaML is probably easier to follow13:27
*** kenhui has joined #openstack-meeting13:27
*** varora has left #openstack-meeting13:27
akamyshnikovaI've another big question. What should we do with new migrations that appear  in Neutron? Should they be unconditional from very beginning?13:28
HenryGakamyshnikova: My understanding is that we want to start that now.13:29
*** cdub has joined #openstack-meeting13:29
rpodolyaka+113:29
jlibosva-1. I don't think so. They would fail because most of them are dependent on previous migrations.13:29
HenryGakamyshnikova: By "now" I mean from Icehouse.13:29
jlibosvait will break deployment with devstack13:29
rpodolyakajlibosva: hmm, what would it break new deployments?13:30
*** belmoreira has joined #openstack-meeting13:30
jlibosvae.g. you deploy neutron with ml2 and someone makes a change in column for other specific plugin. Table would be missing, migration will fail13:31
jlibosvabecause this particular migration would be executed13:31
*** Longgeek has quit IRC13:31
*** Longgeek has joined #openstack-meeting13:31
*** paragan has joined #openstack-meeting13:31
*** paragan has joined #openstack-meeting13:31
*** kayaliu_ has joined #openstack-meeting13:31
*** _nadya_ has joined #openstack-meeting13:32
akamyshnikovaIf it should be started from now. I think that it should be announced for everyone.13:32
jlibosvaI'd suggest to keep conditional migrations for now until we have something that brings idempotent operation above db13:32
rpodolyakawon't we runn ALL migrations unconditionally?13:33
HenryGMy understanding is you would have the old conditional migrations until Icehouse. Then the healing script. Then all tables will be present and all migrations from Icehouse on are unconditional.13:33
*** rakhmerov has joined #openstack-meeting13:33
jlibosvasince we want to get rid of conditional migration, there will be other patch removing conditions themselves.13:33
akamyshnikovajlibosva, where you find such changes of columns?13:33
jlibosvaHenryG: agreed, question is what to do with current patches coming to master13:34
HenryGjlibosva: If I understood Mark correctly, we "undo" them and replace them with unconditional ones.13:34
HenryGWe undo the ones that are committed in the Juno cycle.13:35
*** dripton_ is now known as dripton13:35
*** haomaiwa_ has joined #openstack-meeting13:35
jlibosvayes, that was my idea. But not starting using '*' in all patches going to master13:35
HenryGOnce we have laid down the code for uncondtional migrations, we no longer allow patches with conditional migrations.13:35
*** haomaiwa_ has quit IRC13:36
jlibosvae.g. https://github.com/openstack/neutron/blob/master/neutron/db/migration/alembic_migrations/versions/35c7c198ddea_lbaas_healthmon_del_status.py#L46 if lbaas is not present, patch like this won't pass deployment13:36
jlibosvaHenryG: agreed13:36
*** _nadya_ has quit IRC13:37
*** sballe_ has joined #openstack-meeting13:37
*** haomaiwa_ has joined #openstack-meeting13:37
*** haomaiwa_ has quit IRC13:37
akamyshnikovayes, in this case. But if some new tables create?13:38
jlibosvaakamyshnikova: you mean not using "if not migration.should_run(active_plugins, migration_for_plugins):" at all?13:39
*** sballe has quit IRC13:39
jlibosvaakamyshnikova: if so, then I agree. It's a good thing. Good poing.13:39
jlibosvapoint13:39
*** dkliban_gone is now known as dkliban13:40
akamyshnikovaIf some new tables created - yes13:40
jlibosvaok, +113:40
*** coreywright_ is now known as coreywright13:40
*** kayaliu_ has quit IRC13:41
HenryGI would like to move on in the agenda.13:41
akamyshnikovaof course if migration is changing table it should be conditional for now.13:41
HenryGWe can discuss more at the end or in the ML/IRC.13:41
*** doron is now known as doron_afk13:41
akamyshnikovaok13:41
HenryG#topic Blueprints13:42
*** openstack changes topic to "Blueprints (Meeting topic: neutron_db)"13:42
*** sballe_ has quit IRC13:42
HenryGWhat blueprints do we have? Here is one:13:42
HenryG#link https://blueprints.launchpad.net/neutron/+spec/neutron-robust-db-migrations13:42
*** haomaiwang has joined #openstack-meeting13:42
*** haomaiwang has quit IRC13:42
*** phil_ has quit IRC13:42
jlibosvaHenryG: here is my draft https://review.openstack.org/#/c/95738/13:42
*** ayoung has joined #openstack-meeting13:42
akamyshnikovathis should be updated neutron-robust-db-migrations13:43
HenryGjlibosva: "Blueprint" vs. "Spec". :)13:43
akamyshnikovaas it was only for service plugins13:43
*** varora has joined #openstack-meeting13:43
*** sushils_ has quit IRC13:43
jlibosvaHenryG: aha, it's difference. sorry :)13:43
*** haomaiwang has joined #openstack-meeting13:43
akamyshnikovaI can do that tomorrow. If there is no other bp13:43
*** flaper87|afk is now known as flaper8713:44
HenryGI think one spec is enough, but it may refer to a couple of blueprints.13:44
*** cdub has quit IRC13:44
HenryGI think we need a blueprint for the healing script.13:45
HenryG#action HenryG to file BP for healing script.13:46
HenryG#topic Testing13:46
*** openstack changes topic to "Testing (Meeting topic: neutron_db)"13:46
*** vijendar has joined #openstack-meeting13:46
HenryGCurrently there is no unit testing for migrations.13:46
HenryGBut akamyshnikova is syncing some framework for this from oslo.13:46
*** Edward-Zhang has joined #openstack-meeting13:46
HenryG#link https://review.openstack.org/7651913:46
HenryGLet's see if we can use this to improve migration unit testing.13:46
*** rakhmerov has quit IRC13:46
*** phil_ has joined #openstack-meeting13:46
HenryGI will discuss the "if and how" of functional testing with marun after the meeting.13:47
HenryG#action HenryG to discuss functional testing with marun.13:47
HenryGMost important in the topic of testing is tempest, specifically grenade coverage.13:47
HenryGCan someone summarize the current status and plan? jlibosva?13:47
*** prad_ has joined #openstack-meeting13:47
*** jgrimm has joined #openstack-meeting13:47
*** liyuezho has joined #openstack-meeting13:48
*** liyuezho has quit IRC13:48
jlibosvacurrently icehouse->master is broken. There are two issues I'm aware of.13:48
*** sushils_ has joined #openstack-meeting13:48
jlibosvathere is an issue with mounting some image for swift, probably because some neutron service is not stopped. I have a testing patch for getting more info https://review.openstack.org/#/c/94351/13:49
*** gokrokve has joined #openstack-meeting13:49
*** jcoufal has joined #openstack-meeting13:49
*** SridharG has quit IRC13:49
*** SridharGaddam has joined #openstack-meeting13:49
jlibosvasecond issue is probably more reproducible wrt policy - I don't know much about this yet, looked at it yesterday afternoon: http://logs.openstack.org/79/95479/2/check/check-grenade-dsvm-neutron/89b999e/logs/new/screen-q-svc.txt.gz?#_2014-05-26_10_49_46_45213:49
jlibosvaif someone is familiar with such an error, I would be glad to get help13:50
HenryGjlibosva: Will the conversion to unconditional migrations help to fix these?13:50
jlibosvaHenryG: I don't think so. It's rather related to Neutron configuration than db13:50
HenryGjlibosva: OK, thanks.13:51
jlibosvaAlso I see time to time failure on stable/icehouse tempest even before upgrade starts13:51
jlibosvaseems like the stable is not that much stable :)13:51
*** jjmb has joined #openstack-meeting13:51
HenryGPlease everyone who can, help jlibosva to look at these issues.13:51
jlibosvathanks13:51
HenryGThanks jlibosva13:51
HenryG#topic Division of labour13:52
*** openstack changes topic to "Division of labour (Meeting topic: neutron_db)"13:52
*** cdub has joined #openstack-meeting13:52
HenryGCode contributors (so far): akamyshnikova, salv-orlando, jlibosva, HenryG13:52
HenryGCore mentors: markmcclain, salv-orlando, marun13:52
*** jcoufal_ has quit IRC13:52
HenryGNew: rpodolyaka :)13:52
HenryGPersonally I am no expert on databases, so I would prefer to work more on the python side of things.13:53
HenryGAny objections or additions?13:53
*** balajiiyer has joined #openstack-meeting13:53
*** gokrokve has quit IRC13:53
akamyshnikovaI think i will continue my researching for creating a script13:54
rpodolyakaakamyshnikova: I'll help you on alembic side :)13:54
*** jjmb1 has joined #openstack-meeting13:54
HenryGjlibosva: focus on grenade/tempest?13:54
*** sballe has joined #openstack-meeting13:54
*** igor_ has quit IRC13:54
*** rakhmerov has joined #openstack-meeting13:54
*** ArthurBerezin has quit IRC13:54
jlibosvaHenryG: ok, I'd like to also participate on the healing script13:54
akamyshnikovarpodolyaka, thank a lot! I rely on your help13:55
HenryGjlibosva: of course13:55
*** IlyaE has joined #openstack-meeting13:56
*** jjmb2 has joined #openstack-meeting13:56
*** jjmb has quit IRC13:56
*** nati_ueno has joined #openstack-meeting13:56
HenryGjlibosva: we are accustomed to turning to you (and salv-orlando) for grenade wisdom :)13:56
*** jjmb has joined #openstack-meeting13:56
*** caleb_ has joined #openstack-meeting13:57
HenryG#topic Mid-cycle sprint13:57
*** openstack changes topic to "Mid-cycle sprint (Meeting topic: neutron_db)"13:57
HenryGJust wanted to ensure everyone is aware of the mid-cycle sprint to focus on nova-networking parity.13:57
HenryG#link https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting13:57
*** zhiyan is now known as zhiyan_13:57
*** jjmb has quit IRC13:57
*** jjmb has joined #openstack-meeting13:58
akamyshnikovayes, I've heard about it13:58
*** jjmb1 has quit IRC13:58
*** rakhmerov has quit IRC13:59
*** terriyu has joined #openstack-meeting13:59
HenryGFor those who can't attend, I will try to set up some interactive thing with a webcam.13:59
*** sballe has quit IRC13:59
*** SridharGaddam has quit IRC13:59
*** annegentle has joined #openstack-meeting13:59
*** SridharG has joined #openstack-meeting14:00
*** pcm__ has joined #openstack-meeting14:00
HenryGEveryone try to squeeze some travel funds out of their bosses. :)14:00
*** doron_afk is now known as doron14:00
rpodolyaka:)14:00
*** jjmb2 has quit IRC14:00
HenryG#topic Open discussion14:00
*** openstack changes topic to "Open discussion (Meeting topic: neutron_db)"14:00
*** nati_ueno has quit IRC14:00
sc68calHenryG: we have the ipv6 meeting14:00
HenryG#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Tue May 27 14:01:11 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_db/2014/neutron_db.2014-05-27-13.02.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_db/2014/neutron_db.2014-05-27-13.02.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_db/2014/neutron_db.2014-05-27-13.02.log.html14:01
*** beekneemech is now known as bnemec14:01
sc68calHenryG: thanks14:01
HenryGSorry sc68cal :)14:01
*** dane_leblanc has joined #openstack-meeting14:01
sc68cal#startmeeting neutron_ipv614:01
openstackMeeting started Tue May 27 14:01:34 2014 UTC and is due to finish in 60 minutes.  The chair is sc68cal. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_ipv6)"14:01
openstackThe meeting name has been set to 'neutron_ipv6'14:01
sc68calWho's here for IPv6?14:01
*** tomoe_ has quit IRC14:01
xuhanphello everyone14:01
*** rpodolyaka has left #openstack-meeting14:01
baoliHi14:01
dane_leblancHello14:01
*** BrianB__ has joined #openstack-meeting14:02
*** doron is now known as doron_afk14:02
sc68cal#link https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam#Agenda_for_May_27th14:02
pcarverHi14:02
sc68cal#topic blueprints14:03
*** openstack changes topic to "blueprints (Meeting topic: neutron_ipv6)"14:03
*** Longgeek has quit IRC14:03
sc68cal#info Make sure you are creating blueprints in the neutron-specs repo and submitting to gerrit14:03
sc68cal#link https://wiki.openstack.org/wiki/Blueprints#Neutron Blueprint info14:04
sc68calDo we have any blueprints to discuss?14:04
*** thangp has joined #openstack-meeting14:05
*** Macaveli has quit IRC14:05
*** lcheng_ has joined #openstack-meeting14:06
*** cfriesen__ has joined #openstack-meeting14:06
*** hashar has quit IRC14:06
*** Longgeek has joined #openstack-meeting14:07
*** gokrokve has joined #openstack-meeting14:07
*** paragan has quit IRC14:07
sc68calOK - if not we will continue on to code reviews14:07
*** ArthurBerezin has joined #openstack-meeting14:08
sc68cal#topic code reviews14:08
*** openstack changes topic to "code reviews (Meeting topic: neutron_ipv6)"14:08
*** ArthurBerezin has left #openstack-meeting14:08
*** gokrokve_ has joined #openstack-meeting14:08
xuhanpsc68cal, I restore my client code change, but seems like Mark still has the -2 on it.14:08
sc68calxuhanp: I e-mailed mark mcclain to ask him to clear his -2 for your python-neutronclient change14:08
sc68cal#link https://review.openstack.org/#/c/75871/6 Python-neutronclient change for ipv6 attributes14:08
*** terriyu has quit IRC14:08
xuhanp:-) we are thinking about the same thing14:09
sc68cal:)14:09
sc68cal#info markmcclain needs to clear -2 since we're in Juno release14:09
sc68calI hate to put a strong voice in the logs like that, but the -2 was because he didn't want it in the Icehouse release14:09
*** cdub has quit IRC14:09
*** jjmb has quit IRC14:10
sc68calWe may need to really get moving on the implementation patches that orchestrate dnsmasq14:10
xuhanp+114:10
sc68calto help facilitate the clearing of that -2.14:10
*** doron_afk is now known as doron14:10
sc68calSo - looks like Shixiong Shang is not online - I'm going to make an executive decision and start breaking up his patches into smaller chunks14:11
*** cdub has joined #openstack-meeting14:11
sc68calthen offering them to people to work on14:11
*** eddie_ has joined #openstack-meeting14:11
*** gokrokve has quit IRC14:11
*** zz_pablosan is now known as pablosan14:11
xuhanpsc68cal, let me know what I can help. We have env in our lab to test it.14:11
sc68calPefect14:12
*** flaper87 is now known as flaper87|afk14:12
sc68cal#link https://review.openstack.org/#/c/70649/ Dnsmasq IPv6 patch that needs to be broken up14:12
sc68cal#action sc68cal break that review into pieces so we can have multiple people working on the patch14:12
baoliI didn't see responses to the comments people had posted to the review.14:13
*** pablosan has quit IRC14:13
sc68calThere were ~50 comments on the review, it probably just got too big to really handle14:14
*** pablosan has joined #openstack-meeting14:14
baoliSome fundamental comments need to be addressed, at least14:14
sc68calagree - when we break it up we'll need to consult the comments of that review to help guide the work14:15
*** cdub has quit IRC14:16
*** pablosan has quit IRC14:16
*** ttrifonov is now known as ttrifonov_zZzz14:16
sc68calBefore I forget - xuhanp mentioned he has a lab to test the patches - I'm also working with SridharG to add API tests to Tempest, and scenario tests for IPv6 functionality14:16
*** corvus is now known as jeblair14:16
sc68calso we can get things testing at the gate14:16
xuhanpsc68cal, sure. That should be easy to test since tempest is still all-in-one node, right?14:17
sc68calNot 100% sure - there has been a lot of work to start doing multi node- but I don't know the status of that work14:18
*** itzikb has quit IRC14:18
sc68cal#link https://review.openstack.org/#/c/93502/ Tempest IPv6 attribute tests14:18
sc68calI think I need to update that review, it is possible that they removed testtools as a dependency for tempest in the last couple days14:19
sc68calwent from passing (except for icehouse) to failing completely :-\14:19
*** paragan has joined #openstack-meeting14:19
*** paragan has quit IRC14:19
*** paragan has joined #openstack-meeting14:19
*** tvoran has joined #openstack-meeting14:20
*** ddieterly has joined #openstack-meeting14:20
*** yaguang has joined #openstack-meeting14:20
*** SridharG has quit IRC14:20
sc68calhmm no it's still a dependency. Well going to have to figure that one out. testr has the most useful error reporting </sarcasm>14:20
*** jmontemayor has joined #openstack-meeting14:21
sc68caldo we have any other code reviews to discuss?14:22
*** pablosan has joined #openstack-meeting14:22
*** lcheng_ has quit IRC14:22
xuhanpsc68cal, I also has a code review to discuss14:22
xuhanp#link https://review.openstack.org/#/c/76125/14:22
xuhanpit has been there for a while, and baoli and I were discussing about this on mail list14:22
*** stevemar has joined #openstack-meeting14:23
xuhanpI would like to hear team's opinion on this.14:23
xuhanphttp://lists.openstack.org/pipermail/openstack-dev/2014-May/034914.html14:24
xuhanphere is the email discussion14:24
*** lcheng_ has joined #openstack-meeting14:24
sc68calxuhanp: I agree with your analysis about allowing two LLA's for a subnet14:25
xuhanpThe major concern about attaching subnet with LLA gateway to a router will cause the gateway port has two LLA addresses.14:25
xuhanpsc68cal, yep14:25
sc68calI'm temptest to just say, if you attach a router to a subnet that already has a LLA set - *overwrite it*14:25
sc68cal*tempted14:25
sc68calalthough on second thought - multiple routers attached to a subnet14:26
sc68calfor east-west traffic14:26
xuhanpsc68cal, by "overwrite" you mean use the IP in the subnet instead?14:26
sc68calno I was thinking take the LLA of the router when it is attached to the subnet and replace the gateway attr of the subnet (if set)14:27
sc68calmost of the time people are not going to set the gateway IP of a subnet then attach a router14:27
*** jecarey has joined #openstack-meeting14:28
*** sileht has quit IRC14:28
sc68calthey'll most likely create a subnet with just the cidr and ip version then attach a router14:28
xuhanpI see14:28
*** SridharG has joined #openstack-meeting14:28
sc68calSo perhaps throw an error if the gateway attr is already set when attempting to attach a router?14:28
sc68calUntil we can think of something to handle multiple routers attached to a subnet14:29
sc68calI have to take a look at the extraroute attributes14:29
xuhanpyep. that makes sense. Let me think about that.14:29
*** sileht has joined #openstack-meeting14:29
sc68calTo be honest I don't know how much of a problem this is *right now* since we don't have dnsmasq fixed yet14:30
*** david-lyle has joined #openstack-meeting14:30
sc68calbut it certainly will become a problem once we get that working14:30
*** terriyu has joined #openstack-meeting14:30
xuhanpsc68cal, agree that the dnsmasq fix has higher priority.14:30
sc68calanything else before we turn to bugs?14:31
*** sballe_ has joined #openstack-meeting14:31
*** cerndev_ has joined #openstack-meeting14:32
sc68cal#topic bugs14:33
*** openstack changes topic to "bugs (Meeting topic: neutron_ipv6)"14:33
sc68cal#link https://bugs.launchpad.net/neutron/+bugs?field.tag=ipv614:33
*** gokrokve has joined #openstack-meeting14:33
sc68calWe have some new and interesting bugs :)14:33
sc68cal#link https://bugs.launchpad.net/neutron/+bug/132294514:33
uvirtbotLaunchpad bug 1322945 in neutron "Attaching a IPv6 private subnet to a L3 Router, breaks it and its IPv4 Floating IPs" [High,New]14:33
*** cerndev has quit IRC14:34
baolisc68cal, when working on the SNAT bug, in the review, we discussed issues associated with ipv4 floating ip.14:34
*** jbrogan has joined #openstack-meeting14:35
baolihttps://review.openstack.org/#/c/88584/1/neutron/agent/l3_agent.py14:35
*** atiwari has joined #openstack-meeting14:35
baoliThe comments talked about some issues14:35
baoliI was wondering if a BP is needed to address them all14:35
*** gokrokve_ has quit IRC14:36
*** otherwiseguy has joined #openstack-meeting14:36
sc68calMy first thought is just to file a bug(s)14:37
sc68calit sounds just like misbehavior14:37
*** sileht has quit IRC14:37
baoliThe ipv4 floating ip api needs to be looked at in the context of ipv4 and ipv6 together14:37
sc68calagree14:37
sc68calaveiga is out this week but we're working on a way to do floats in v6, without NAT14:38
sc68calbut yeah dual stack floating ips - probably nobody has thought of that14:39
*** vhoward has left #openstack-meeting14:39
*** sileht has joined #openstack-meeting14:39
*** vhoward has joined #openstack-meeting14:39
*** TravT has joined #openstack-meeting14:39
*** ivasev has joined #openstack-meeting14:40
sc68calbaoli: I'll make a note to bring this up at the main meeting - this is a very interesting issue14:40
*** keshava-hp has joined #openstack-meeting14:40
sc68cal#action sc68cal bring up baoli's analysis of the floating ip API and dual stacking in the main meeting14:40
sc68calbaoli: for the time being can you write up a bug so I can link it for them?14:40
baolisc68cal, that would be great. It should be considered in the case of dual stack and ipv6 only14:40
baolisc68cal, will do.14:41
*** Longgeek_ has joined #openstack-meeting14:41
sc68cal#action baoli write up bug report about dual stack and v6 only floating ips14:41
*** kayaliu_ has joined #openstack-meeting14:41
sc68calSo the other bug I wanted to bring attention to is this one14:42
*** Mandell has joined #openstack-meeting14:42
sc68cal#link https://bugs.launchpad.net/ironic/+bug/132315214:42
uvirtbotLaunchpad bug 1323152 in ironic "CI failure "unable to enable dhcp for" (dup-of: 1321494)" [Undecided,New]14:42
uvirtbotLaunchpad bug 1321494 in ironic "NodeLocked causing random test failures" [High,In progress]14:42
sc68calbasically dnsmasq barfs on a v6 subnet14:42
sc68calI'm sure we've all seen that error in devstack when testing v6 :)14:43
sc68calso - I think one of the fixes is bumping the dnsmasq min version14:43
sc68calhttps://bugs.launchpad.net/neutron/+bug/123333914:44
uvirtbotLaunchpad bug 1233339 in neutron "bump dhcp.Dnsmasq.MINIMUM_VERSION" [Medium,Triaged]14:44
*** Longgeek has quit IRC14:44
sc68calthe other fix is getting the dnsmasq patches for v6 merged :)14:44
*** toan-tran has joined #openstack-meeting14:45
*** sballe_ has quit IRC14:45
sc68calAny other bugs to discuss?14:45
sc68calotherwise I'll turn to open discussion14:45
sc68cal#topic open discussion14:46
*** openstack changes topic to "open discussion (Meeting topic: neutron_ipv6)"14:46
*** Mandell has quit IRC14:46
*** venkatesh has joined #openstack-meeting14:47
*** gcb has joined #openstack-meeting14:49
*** sileht has quit IRC14:49
sc68calIf there's nothing else to discuss, I can give everyone back 10 minutes and end the meeting14:50
*** ArthurBerezin has joined #openstack-meeting14:50
xuhanp:-)14:51
*** sileht has joined #openstack-meeting14:51
*** Edward-Zhang has quit IRC14:51
sc68calOk everyone, take care, see you all next week!14:51
sc68cal#endmeeting14:51
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:52
openstackMeeting ended Tue May 27 14:51:59 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-05-27-14.01.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-05-27-14.01.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-05-27-14.01.log.html14:52
*** ArthurBerezin has left #openstack-meeting14:52
*** cdub has joined #openstack-meeting14:52
*** thedodd has joined #openstack-meeting14:53
*** rakhmerov has joined #openstack-meeting14:55
*** BrianB__ has quit IRC14:56
*** caleb_ has quit IRC14:57
*** nati_ueno has joined #openstack-meeting14:57
*** n0ano has joined #openstack-meeting14:57
*** otherwiseguy has quit IRC14:57
*** PaulMurray has joined #openstack-meeting14:57
*** otherwiseguy has joined #openstack-meeting14:58
*** gcb has quit IRC14:58
*** mspreitz has joined #openstack-meeting14:58
*** pcm__ has left #openstack-meeting14:58
*** egallen has quit IRC15:00
*** egallen has joined #openstack-meeting15:00
*** jmontemayor has quit IRC15:00
*** cdub has quit IRC15:00
bauzasn0ano: ping ? :)15:00
*** Longgeek_ has quit IRC15:00
* mspreitz waits to hear echo15:00
bauzasecho-echo-echo15:00
toan-tranpong15:00
*** Longgeek has joined #openstack-meeting15:01
*** lascii is now known as alaski15:01
*** SridharG has quit IRC15:01
bauzaswe're waiting for the One :)15:01
*** garyk has joined #openstack-meeting15:01
*** nati_ueno has quit IRC15:01
*** jmontemayor has joined #openstack-meeting15:01
*** KurtMartin is now known as kmartin15:01
*** rkukura has joined #openstack-meeting15:02
*** egallen has quit IRC15:02
bauzaslet's wait one more minute agani15:02
toan-tranbauzas: the One and the Many? :)15:02
bauzasand then I'll start15:02
bauzasn0ano should chair that one15:02
*** yaguang has quit IRC15:03
n0ano#startmeeting gantt15:03
openstackMeeting started Tue May 27 15:03:39 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: gantt)"15:03
openstackThe meeting name has been set to 'gantt'15:03
* n0ano really should type into the right window15:03
*** jmontemayor has quit IRC15:04
bauzashurraaaaa15:04
* doron here15:04
n0anoI started the meeting in openstack-dev and was saying bad things about no one joining :(15:04
bauzasso, I think we can start15:04
n0anoanyway15:04
*** kun_huan_ has joined #openstack-meeting15:04
n0ano#Juno summit recap15:04
bauzasmspreitz and toan-tran said hello15:04
*** morganfainberg_Z is now known as morganfainberg15:04
*** egallen has joined #openstack-meeting15:05
n0anojust so everyone knows, the etherpads from the friday sched sessions were:15:05
n0anoforklift15:05
n0anohttps://etherpad.openstack.org/p/juno-nova-gantt-apis15:05
n0anono-db scheduler15:05
n0anohttps://etherpad.openstack.org/p/juno-nova-no-db-scheduler15:05
n0anosimultaneout scheduling for server groups15:05
n0anohttps://etherpad.openstack.org/p/juno-nova-scheduling-server-groups15:05
n0anohints for VM lifecycle15:05
n0anohttps://etherpad.openstack.org/p/juno-nova-scheduler-hints-vm-lifecycle15:05
*** zhiyan_ is now known as zhiyan15:05
*** kun_huang has quit IRC15:05
bauzaswe also discussed in -dev ML15:05
bauzaslemme find the link15:05
n0anowe can do a brief rundown of the sessions:15:06
*** blamar has quit IRC15:06
n0anoforklift - forge ahead, clean up the interfaces in nova first and then split the code out15:06
bauzas#link http://lists.openstack.org/pipermail/openstack-dev/2014-May/035415.html15:06
n0anonodb - the memcached is used as a journal of the changes (not what I expected and created a large bit of discussion)15:07
n0anosimultaneous scheduler for server groups - should look into maybe merging this into climate15:07
*** tianst has joined #openstack-meeting15:07
bauzass/Climate/Blazar now :)15:07
n0anon0ano, sigh, can't tell the players without a score card (baseball reference :-)15:08
mspreitzand some of them have funny names15:08
*** rakhmerov has quit IRC15:08
n0anohings for VM lifecycle - good idea, issue is where to store the hings15:08
bauzasright15:09
n0anothat's my summary of results, anyone want to expand any of that?15:09
toan-tranyeah15:09
bauzasthe detailed analysis is in the link I gave previously15:09
*** iqbalmohomed has joined #openstack-meeting15:09
toan-tranon VM lifecycle15:09
*** aviau has quit IRC15:09
toan-tranIMO it's really necessary15:10
toan-tranand the solution that Jay Lau proposed sounds well15:10
*** blamar has joined #openstack-meeting15:10
toan-tranjust want to know when the bp starts :)15:10
bauzastoan-tran: there was a consensus about the need15:10
*** dane_leblanc has quit IRC15:10
*** terryw has joined #openstack-meeting15:10
n0anobauzas, +115:10
mspreitzWhich is Jay's solution?15:10
bauzastoan-tran: the discussion was about how to persist it15:10
mspreitz+1 on th need15:10
*** kayaliu_ has quit IRC15:11
toan-tranmspreitz: stores hints in db15:11
toan-tranwhether instance metadata  or something else15:11
bauzasmspreitz: the idea was to store hints in  compute_nodes table15:11
bauzasright15:11
*** otherwiseguy has quit IRC15:11
bauzasthe discussion was about the possible interest of system_metadata15:11
*** caleb_ has joined #openstack-meeting15:11
toan-tranI got another thought15:11
toan-transince this hint can be used with Instance Group15:12
toan-transo that user can add VMs into groups15:12
*** carl_baldwin_ has joined #openstack-meeting15:12
toan-tranit's not bad iea to have it stored with instance group15:12
toan-trans/iea/idea15:13
*** primeministerp has joined #openstack-meeting15:13
bauzastoan-tran: hints are not only for groups15:13
johnthetubaguyat the session, people didn't like the idea of every VM having a group, but its an option for sure15:13
n0anowhat bauzas said, I would think the hings should be VM specific15:13
n0anos/hings/hints/15:13
mspreitzn0ano? should be?  Are!  right?15:13
toan-tranOK, so idea reversed:15:13
johnthetubaguyn0ano: +1 for now it has to be really15:13
toan-tranmake Instance group use hints ?15:14
bauzashttps://review.openstack.org/#/c/88983/ is the nova-spec15:14
*** egallen has quit IRC15:14
mspreitztoan-tran: how?15:14
*** zhiyan is now known as zhiyan_15:14
toan-tranmspreitz: sorry ?15:15
mspreitzI am asking what you mean15:15
*** egallen has joined #openstack-meeting15:15
mspreitzexpand on your remark pls15:15
toan-tranI mean we can use hint to make instance group policy persistant15:15
bauzasthe proposed change is planned to be located in instances table15:15
mspreitzI thought Instance Grp policy is already persistent15:16
*** kun_huan_ has quit IRC15:16
toan-tranright now the problem of instance group, IMO, is that whenever user wants to create a VM, it has to connect with the group's current policy15:16
toan-tranthus from my point of view, instance group' s policy and hint is the same15:16
n0anotoan-tran, are you getting confused, we need to make the hints for a VM persisten, how the instance groups uses those hints is up to the instance group code15:16
mspreitztoan-tran: I'm confused, that's the point of Inst grp15:16
*** YorikSar has joined #openstack-meeting15:17
bauzasn0ano: heavy +115:17
*** kun_huang has joined #openstack-meeting15:17
*** che-arne has joined #openstack-meeting15:17
mspreitzStoring hints in instances table makes sense to me15:17
*** rkukura has left #openstack-meeting15:17
toan-tranwell, I'm saying that if we think of how new VM should be created for a group15:17
bauzasmspreitz: that's what's proposed in the spec15:17
garyki am not sure i follow15:18
bauzastoan-tran: please address your concerns there : https://review.openstack.org/#/c/88983/17/specs/juno/persist-scheduler-hints.rst15:18
garykthe spawn today uses the hint to indicate which instance group to ise15:18
garyksorry, use15:18
*** afazekas has quit IRC15:18
garykthe group is persistent.15:18
mspreitzbauzas: I have not had a chance to read that patch yet, I presume it follows the spec (store in instances table)15:18
n0anoI thought the only issue from the summit was whether to store the hings in a new instance table column or a new table15:19
bauzasmspreitz: you presume well15:19
toan-trann0ano: no argument here15:19
*** ccorrigan has quit IRC15:19
mspreitzSo I am +1 on the spec and patch15:19
toan-tranI just think of how instance group can profit from persistent hint15:19
n0anotoan-tran, so is you only concern `how` the instance group code uses that data15:19
toan-trann0ano: yes15:20
bauzastime is precious, and we still need to discuss about other summit topics15:20
bauzascould we move on ?15:20
toan-tranbauzas: i'm done :)15:20
*** akuznetsov has quit IRC15:20
n0anoI think we've discovered we're in violent agreement, so sure15:20
bauzas:)15:20
n0anobauzas, you had another point?15:20
bauzasI just wanted to discuss about no-db15:20
bauzasand sched-forklift15:20
bauzasbut sched forklift can wait for the next topic15:21
bauzasI just saw YorikSar joining15:21
bauzasYorikSar: ping ?15:21
n0anois boris-42 or one of his team members available?15:21
YorikSarbauzas: Hi :)15:21
bauzasYorikSar: hi :)15:21
YorikSarn0ano: I'm here15:21
n0anoYorikSar, can we talk about the no-db scheduler work15:21
bauzasYorikSar is the current owner of the no-db patches15:21
YorikSarSure.15:21
bauzasYorikSar was not present at Summit15:21
bauzasso we need to make sure we're on the same page15:22
bauzasYorikSar: has boris-42 discussed with you about the results of the session ?15:22
YorikSarAs I understood from what boris-42 told me, I need to make the new host state delivering scheme optional.15:22
*** tvoran has quit IRC15:22
iqbalmohomedAt the summit, there was some confusion/questions about the 60 second sync ups ..15:22
n0anoI was confused when the summit session indicated the memcache would be a tranascation journal and not a state cache, is that still the case15:22
YorikSarAnd for the rest of it people were agreed upon it.15:23
*** gyee has joined #openstack-meeting15:23
bauzasYorikSar: well, that's a point, the second one was about journalising updates15:23
bauzasn0ano: +115:23
toan-trann0ano: +115:23
YorikSariqbalmohomed: We can have pluggable backends that store all data used by Synchronizer.15:23
n0anobauzas, yeah, I think there was negative agreement on the journaling issue15:23
YorikSarn0ano: ^15:23
*** NithyaG has joined #openstack-meeting15:24
YorikSarIt includes smth like a journal but is not limited to it.15:24
*** aviau has joined #openstack-meeting15:24
n0anoI don't understand why you have a journal at all, why not a state table15:24
YorikSarSo just like with SQL backend we can ask for all new updates and fetch only records that were changed with those updates.15:25
iqbalmohomedregarding the journal ... was the idea that there is a periodic checkpoint that is done?15:25
mspreitzYorikSar: changed since <what> ?15:25
*** akuznetsov has joined #openstack-meeting15:25
*** ddieterly has quit IRC15:25
*** venkatesh has quit IRC15:26
YorikSarSince last sync action. Sync is done before every read/15:26
mspreitzThere are multiple consumers, right?  So it's since <this client's> last sync, right?15:26
iqbalmohomedok ... i guess the sync = the checkpoint15:26
YorikSarSo most common case will be: user spawns an instance, scheduler fetches list of updates since last its request and fetches records touched by those updates.15:27
YorikSarmspreitz: Yes.15:27
toan-tranok so basically there are two storage: one for the whole state and another for changes15:27
toan-tran?15:27
YorikSariqbalmohomed: Well... You can name it that way.15:27
*** cerndev_ has quit IRC15:27
YorikSartoan-tran: No.15:28
mspreitzYorikSar: So there is some way of identify the client or its last sync.  What is that?15:28
YorikSarUpdate is just a record that some Record has been changed, no data.15:28
n0anoYorikSar, ?? (now I'm confused)15:28
*** mrodden has quit IRC15:29
YorikSarmspreitz: Every client stores a token of the latest update it have seen.15:29
YorikSarSo it asks backend "give me all records that were changed by updates with token greater that this one"15:29
iqbalmohomedWhen a new client comes in (e.g. during crash recovery), how does it catch up?15:29
mspreitzYorikSar: token = sequence number, works because updates are totally ordered ?15:29
YorikSarmspreitz: Yes15:29
*** emagana has joined #openstack-meeting15:30
YorikSariqbalmohomed: It fetches all records from the backend15:30
YorikSarAnd a latest update's token.15:30
*** edmund has joined #openstack-meeting15:30
*** johnpur has joined #openstack-meeting15:30
mspreitzSo there is one central thing that is totally ordering updates.  Is that a scalability problem?15:30
YorikSarmspreitz: For SQL backend it's just an autoincremented primary key.15:31
YorikSarmspreitz: For memcached it's a key that will be inc()'ed for every new update.15:32
bauzasYorikSar: IIUC, the debate was about the need of implementing checkpoints with memcache15:32
toan-tranYorikSar: how big the data it has to sends ? it's quite a problem if the client is far behind15:32
bauzasYorikSar: because that was a logic that memcache could handle on its own, no need to implement it at software level15:32
YorikSarbauzas: I'm not sure I understand what's a checkpoint in this context.15:32
*** kun_huang has quit IRC15:32
bauzascorrect me if I'm wrong, but you're implementing transactions at the implementation level ?15:33
YorikSartoan-tran: If the client is far behind (lost next update after his last one) it'll eventually refetch all records from backend.15:33
*** tvoran has joined #openstack-meeting15:34
*** kenhui has quit IRC15:34
YorikSarbauzas: No, with memcached there is no transactions.15:34
bauzasYorikSar: the point that has been raised was about why implementing it and not leave memcache holding this?15:34
n0anoOK, everyone take a deep breath and let's pause for a minute...15:35
bauzasn0ano: :)15:35
YorikSarLet me throw in some spec I've written before summit15:35
n0anoI think there is a `lot` of confusion about the details of this design...15:35
YorikSar#link https://review.openstack.org/#/c/92128/2/specs/juno/no-db-scheduler.rst15:35
YorikSarIt feels like I'm retelling some parts of it.15:35
*** NithyaG is now known as NithyaG_afk15:35
*** tvoran has quit IRC15:35
* mspreitz wants to study before speaking more15:36
*** jmontemayor has joined #openstack-meeting15:36
n0anoYorikSar, thank you, that's what I was about to ask for, let's all read that spec and come back next week with some understanding and raise any issues we have15:36
*** jmontemayor has quit IRC15:36
mspreitz+115:36
bauzasn0ano: +215:36
*** tvoran has joined #openstack-meeting15:36
YorikSarn0ano: Great idea :)15:36
toan-trann0ano: +315:36
*** pdmars has joined #openstack-meeting15:36
*** jmontemayor has joined #openstack-meeting15:36
n0anoYorikSar, BTW, thank for doing this, we're really not trying to beat up on you, there's just lots of confusion15:37
YorikSarI hope I'll be able to address some of John's comments there.15:37
YorikSarn0ano: I understand.15:37
iqbalmohomed+115:37
johnthetubaguyYorikSar: cool, its just the optional bits that makes me −2 at this point, I love the idea in general15:37
YorikSarI guess noone noticed that spec after John -2'd it15:37
bauzasn0ano: indeed, we're just reporting discussion from the Summit15:37
n0anomoving on, any other summit comments before we move to forklift efforts?15:38
bauzasn0ano: maybe we could put an action15:38
YorikSarn0ano: I totally understand.15:38
*** beagles has left #openstack-meeting15:38
n0ano#action everyone to read the no-db spec and come back for detailed discussion next week15:38
bauzassweet15:38
YorikSarjohnthetubaguy: Yes, I've just been waiting or summit to pass before getting back to the spec15:38
johnthetubaguyYorikSar: cool, no problem, ping me if I miss an updated, happy to help review that15:39
n0ano#topic forklift efforts15:39
*** openstack changes topic to "forklift efforts (Meeting topic: gantt)"15:39
bauzassoooo15:39
*** jgrimm has quit IRC15:39
n0anobauzas, can you provide a brief summary15:39
YorikSarjohnthetubaguy: Sure. Will do.15:39
*** fnaval has joined #openstack-meeting15:39
*** zhiyan_ is now known as zhiyan15:39
bauzasthere are 3 bps I'm owning for that15:39
bauzas2 are still specs to review15:40
*** belmoreira has left #openstack-meeting15:40
bauzasthe most important one is to isolate the sched db15:40
bauzashttps://review.openstack.org/8989315:40
bauzasI made some changes, based on Summit feedback15:40
bauzasI'm planning to begin working on that by next week15:40
*** mrodden has joined #openstack-meeting15:41
bauzasthat one is really huge to work on15:41
bauzasso, work items are important15:41
bauzaspeople interested in contributing can review the spec15:41
*** leeantho has joined #openstack-meeting15:41
bauzasin order to make I'm not forgetting a crucial piece of work15:41
johnthetubaguybauzas: the currently approved blueprint has all its patches up for review now?15:41
mspreitzCan you pls post a pointer to all 3 bps?15:41
bauzass/make/make sure15:41
bauzasmspreitz: sure15:41
bauzas#link https://review.openstack.org/82133 (scheduler-lib validated)15:42
bauzas#link https://review.openstack.org/89893 (isolate-sched-db review in progress)15:42
bauzas#link https://review.openstack.org/94916 (prep_resize to move to conductor - review in progress)15:43
bauzasthese are the 3 bps I'm owning15:43
bauzassched-lib is targeted for juno-115:43
*** eghobo has joined #openstack-meeting15:43
*** ominakov has quit IRC15:43
bauzasI'll speak about it right after15:43
n0anobauzas, when you say `review in progress`, is that the BP or the patches to implement the BP?15:43
bauzasisolate-sched-db is planned for juno-315:43
mspreitzhttps://review.openstack.org/#/c/94916/ is a change with no associated BP15:44
bauzasspec is currently in review15:44
bauzasmspreitz: my bad, missed the bp link15:44
bauzasmspreitz: bp/move-prep-resize-to-conductor15:44
bauzasmspreitz: you can find it as bp name15:45
bauzasmspreitz: but will amend the patch15:45
mspreitzbauzas: thanks15:45
bauzasmspreitz: that one is quite small to do15:45
bauzasmspreitz: the most important efforts will go to https://review.openstack.org/89893 implementation15:45
bauzashence the juno-3 target15:45
bauzasso, I pledge you to review the spec and comment it15:46
bauzasjuno-2 is beginning in 2 weeks15:46
johnthetubaguybauzas: about this one: https://blueprints.launchpad.net/nova/+spec/scheduler-lib15:46
johnthetubaguybauzas: are all the patches up for that now?15:46
bauzasjohnthetubaguy: the current patch is https://review.openstack.org/8277815:47
*** tianst has quit IRC15:47
bauzasjohnthetubaguy: it's just missing unittests for sched-lib15:47
johnthetubaguybauzas: do you expect any more patches?15:47
johnthetubaguyah, OK, its not complete yet, fair enough15:47
bauzasjohnthetubaguy: I will do another one for patching the calls of select_destinations15:47
johnthetubaguyjust its targeted at juno-115:48
bauzasjohnthetubaguy: it will be ended by tomorrow15:48
bauzasjohnthetubaguy: I nearly finished to write the tests, will submit them today or tomorrow15:48
bauzasjohnthetubaguy: so you can review it15:49
johnthetubaguybauzas: OK, so all patches hopefully up by tomorrow then, thats cool15:49
*** markwash has joined #openstack-meeting15:49
*** xuhanp has quit IRC15:49
*** jbrogan has quit IRC15:49
bauzasjohnthetubaguy: yup15:49
*** egallen has quit IRC15:49
johnthetubaguyonce is ready, you can move to needscodereview blueprint state, which is cool, thanks15:49
bauzasjohnthetubaguy: so that next week will be focused on delivering new patchsets if any requested15:49
bauzasjohnthetubaguy: ok will do15:49
n0anobauzas, maybe a couple of actions, bauzas to complete the one patch, everyone to do reviews?15:51
bauzasso, as I said, I'm looking for support on reviews for both the isolate-sched-db spec and the sched-lib patch15:51
*** zhiyan is now known as zhiyan_15:51
bauzasn0ano: would love to15:51
toan-tranbauzas: +115:51
*** balajiiyer has quit IRC15:51
n0ano#action all to review isolate-sched-db spec & sched-lib patch15:51
bauzasthanks15:52
*** jgrimm has joined #openstack-meeting15:52
n0ano#action bauzas to complete tests for scheduler-lib patch15:52
bauzascool15:52
*** Realmy has joined #openstack-meeting15:52
n0anobauzas, BTW, tnx for the effort, it's much appreciated15:52
iqbalmohomedIn the last few mins, could we do a quick recap of the simultaneous server group scheduling discussion?15:53
bauzasyour welcome15:53
*** egallen has joined #openstack-meeting15:53
n0ano#topic opens15:53
*** openstack changes topic to "opens (Meeting topic: gantt)"15:53
bauzassure, I'm don15:53
bauzasdone15:53
n0anoiqbalmohomed, sure, go ahead15:53
bauzasiqbalmohomed: what do you want to know ?15:53
iqbalmohomedSo what I got was that we need to talk to the climate folks first15:53
iqbalmohomedfigure out how that integrates with GANTT15:53
iqbalmohomedand then, we'll be ready to get started15:54
iqbalmohomedbut i didn't hear strong objection to the capability15:54
iqbalmohomedany other thoughts?15:54
bauzasiqbalmohomed: that's right15:54
n0anoiqbalmohomed, that's what I heard15:54
bauzasiqbalmohomed: I'm one of the Climate folks, btw.15:54
mspreitzSo quick question: when I looked at the API a month ago, I was disappointed to find no way to make a reservation without creating a VM at the same time.  Is that still true?15:55
doroniqbalmohomed: climate is now blazar- it was renamed....15:55
bauzasiqbalmohomed: the idea is to see how to integrate that idea in Climate and see what pieces are missing in Nova15:55
*** beagles has joined #openstack-meeting15:55
iqbalmohomedcool .. will follow up in the climate discussion group and report back here15:55
bauzasmspreitz: you're right, we're not having a no-op plugin15:56
*** hashar has joined #openstack-meeting15:56
*** shakamunyi has joined #openstack-meeting15:56
bauzasmspreitz: but that's not a huge amount of work15:56
mspreitzWe want some separation.  Discussion to follow, this meeting is about to end.15:56
bauzasiqbalmohomed: you can join #openstack-blazar15:56
bauzasiqbalmohomed: for discussion15:56
iqbalmohomedbauzas: thanks ... do15:56
n0anomspreitz, do you want me to queue this up for next weeks agenda?15:57
mspreitznot sure yet, let us discuss with Blazar folks first15:57
*** xuhanp has joined #openstack-meeting15:57
n0anomspreitz, sounds good15:57
iqbalmohomedthx all15:57
toan-tranbtw why blazar?15:57
bauzasI promise it won't be the Blazaar :)15:57
toan-tranbauzas: :)15:58
n0anoWinding down for today, any last minute comments?15:58
*** devlaps has joined #openstack-meeting15:58
bauzastoan-tran: I leave you check Wikipedia :)15:58
bauzastoan-tran: Novas and Blazars are common objects in space :)15:58
toan-tranyeah super-nova IMO15:58
n0anoOK, tnx everyone, talk again next week15:59
*** danpb has joined #openstack-meeting15:59
n0ano#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
toan-tranbauzas: that's why I asked15:59
openstackMeeting ended Tue May 27 15:59:14 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
toan-tran:)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-05-27-15.03.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-05-27-15.03.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/gantt/2014/gantt.2014-05-27-15.03.log.html15:59
*** ddieterly has joined #openstack-meeting15:59
bauzasn0ano: thanks for your support :)15:59
n0anobauzas, NP15:59
bauzasmuch appreciated15:59
*** alexpilotti has joined #openstack-meeting15:59
*** mspreitz has left #openstack-meeting15:59
*** iqbalmohomed has quit IRC15:59
*** PaulMurray has left #openstack-meeting16:00
*** samcdona has joined #openstack-meeting16:00
*** jhenner1 has joined #openstack-meeting16:00
*** YorikSar has left #openstack-meeting16:00
*** Munish has joined #openstack-meeting16:01
primeministerp#startmeeting hyper-v16:01
openstackMeeting started Tue May 27 16:01:09 2014 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: hyper-v)"16:01
openstackThe meeting name has been set to 'hyper_v'16:01
primeministerphi all16:01
*** jhenner has quit IRC16:01
*** toan-tran has quit IRC16:01
*** xuhanp has quit IRC16:01
primeministerpalexpilotti: morning ;)16:01
primeministerpluis_fdez: hi there16:01
alexpilottiprimeministerp luis_fdez: hi there!16:01
primeministerpso today we'll discuss some updates from the summit16:02
primeministerp#topic summit updates16:02
*** openstack changes topic to "summit updates (Meeting topic: hyper-v)"16:02
*** jlibosva has quit IRC16:02
alexpilottihere’s the link with the design summit’s etherpad:16:03
alexpilotti#link https://etherpad.openstack.org/p/nova-hyperv-juno16:03
primeministerpso we had a design session that went extremely well16:03
alexpilottiit’s a lot of stuff :-)16:03
primeministerpthis pretty much lays out our plans for the next 2 release cycles16:03
primeministerpschwicht: you'll be interested in that16:03
alexpilottitop feature is going to be SMB316:04
*** zul has left #openstack-meeting16:04
*** balajiiyer has joined #openstack-meeting16:04
alexpilottihere’s a quick list:16:04
alexpilottiNova and Cinder SMB3 integration16:04
alexpilottiNova x509 based Windows password-less authentication16:04
alexpilottiGeneration 2 VMs16:04
alexpilottiNova SMB shared storage16:04
alexpilottiNova serial console16:05
alexpilottiNova soft reboot16:05
alexpilottiNova host power actions16:05
alexpilottiNova rescue16:05
alexpilottiNova RemoteFX support16:05
alexpilottiNova / Neutron Hyper-V SR-IOV pass-through16:05
alexpilottiNova Hyper-V clustering support16:05
primeministerpschwicht: ^16:05
*** rakhmerov has joined #openstack-meeting16:05
alexpilottibeside that16:05
alexpilottiironic Hyper-V driver16:05
alexpilottiwith planned contributrions from HP16:06
primeministerpthanks for supplying the list16:06
alexpilottiso this is it :-)16:06
*** balajiiyer has left #openstack-meeting16:06
primeministerpwe'll be adding blueprints for these if they are not on thier way already16:06
primeministerp#topic ci16:06
*** openstack changes topic to "ci (Meeting topic: hyper-v)"16:06
primeministerpadditionally we're in process for building additonal ci infra16:07
primeministerpto support all the addtional testing we'll be taking on16:07
primeministerpwe're on target for that infra to be operational by end of j16:07
primeministerp#topic puppet16:07
*** openstack changes topic to "puppet (Meeting topic: hyper-v)"16:08
primeministerpluis_fdez: ping16:08
primeministerpluis_fdez: any word on the work you've done to align w/ the upstream modules?16:08
*** paragan has quit IRC16:08
primeministerpluis_fdez: if not we can pick up later16:08
*** dkliban is now known as dkliban_brb16:08
primeministerpI still am in the process of deploying the necessary test infra here which could take some time16:08
*** jhenner1 has quit IRC16:09
primeministerp#topic openvswitch16:09
*** openstack changes topic to "openvswitch (Meeting topic: hyper-v)"16:09
*** asselin has joined #openstack-meeting16:09
primeministerpso the cloudbase folks released installers for the ovs for hyper-v b its16:09
*** rakhmerov has quit IRC16:10
alexpilottiso the great news, we published Open vSwitch for Hyper-V16:10
alexpilottiincluding an installer to fully automate the deployment:16:10
alexpilotti#link http://www.cloudbase.it/open-vswitch-on-hyper-v/16:10
alexpilottiwe’re now fixing a few remaining bugs and we’re ready for the RTW16:11
alexpilottithe installer is built automatically by our jenkins servers as soon as a patch lands in one of the github repos16:11
*** marcoemorais has joined #openstack-meeting16:11
alexpilottiwe’re also working on an article showing the integration with Neutron and the OVS plugin16:12
*** danpb has left #openstack-meeting16:13
primeministerpgreat16:13
*** egallen has quit IRC16:13
primeministerpthanks for the ovs update16:13
primeministerpso I have nothing else for now16:13
primeministerplet's close it quick as I know parties are busy16:13
primeministerp#endmeeting16:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:13
openstackMeeting ended Tue May 27 16:13:45 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-05-27-16.01.html16:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-05-27-16.01.txt16:13
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-05-27-16.01.log.html16:13
alexpilottibye!16:13
*** nati_ueno has joined #openstack-meeting16:14
*** egallen has joined #openstack-meeting16:15
*** aswadr has joined #openstack-meeting16:15
*** idegtiarov has quit IRC16:16
*** amotoki has joined #openstack-meeting16:17
*** phil_ has quit IRC16:19
*** sushils_ has quit IRC16:20
*** thedodd has quit IRC16:21
*** thedodd has joined #openstack-meeting16:21
*** egallen has quit IRC16:23
*** egallen has joined #openstack-meeting16:24
*** tvoran has quit IRC16:24
*** jseutter has joined #openstack-meeting16:25
*** jgallard has quit IRC16:26
*** egallen has quit IRC16:26
*** derekh_ has quit IRC16:26
*** tvoran has joined #openstack-meeting16:26
*** pablosan is now known as zz_pablosan16:26
*** jhenner has joined #openstack-meeting16:27
*** egallen has joined #openstack-meeting16:27
*** Longgeek has quit IRC16:27
*** rossk has joined #openstack-meeting16:29
*** ArxCruz has quit IRC16:29
*** ArthurBerezin has joined #openstack-meeting16:30
*** Realmy_ has joined #openstack-meeting16:30
*** jcoufal has quit IRC16:32
*** Realmy has quit IRC16:33
*** tkay has joined #openstack-meeting16:33
*** lsmola2 has joined #openstack-meeting16:33
*** gokrokve has quit IRC16:34
*** rushiagr has left #openstack-meeting16:35
*** gokrokve has joined #openstack-meeting16:35
*** mwagner_lap has joined #openstack-meeting16:35
*** vhoward has left #openstack-meeting16:36
*** terryw is now known as otherwiseguy16:36
*** doron is now known as doron_afk16:38
*** kenhui has joined #openstack-meeting16:39
*** gokrokve has quit IRC16:39
*** jtomasek has quit IRC16:39
*** lsmola3 has joined #openstack-meeting16:40
*** jmontemayor has quit IRC16:40
*** lsmola2 has quit IRC16:42
*** nacim_ has quit IRC16:42
*** doron_afk has quit IRC16:42
*** zhiyan_ is now known as zhiyan16:42
*** safchain has quit IRC16:42
*** nshaikh has quit IRC16:43
*** evgenyf has quit IRC16:44
*** evgenyf has joined #openstack-meeting16:44
*** lsmola3 has quit IRC16:45
*** lsmola2 has joined #openstack-meeting16:45
*** zdiN0bot has joined #openstack-meeting16:46
*** pdmars has quit IRC16:47
*** tvoran has quit IRC16:47
*** ArthurBerezin has left #openstack-meeting16:47
*** Fdot has quit IRC16:48
*** zhiyan is now known as zhiyan_16:51
*** david-lyle has quit IRC16:51
*** david-lyle has joined #openstack-meeting16:52
*** david-lyle has quit IRC16:52
*** IgorYozhikov is now known as iyozhikov16:52
*** nati_ueno has quit IRC16:53
*** kgriffs is now known as kgriffs|afk16:54
*** lsmola2 has quit IRC16:54
*** dkliban_brb is now known as dkliban16:54
*** SumitNaiksatam has quit IRC16:54
*** harlowja_away is now known as harlowja_16:55
*** yamahata has quit IRC16:55
*** nati_ueno has joined #openstack-meeting16:56
*** ildikov has quit IRC16:57
*** aviau has quit IRC16:57
*** aviau has joined #openstack-meeting16:58
*** Leonr has joined #openstack-meeting16:58
*** thinrichs has joined #openstack-meeting16:59
*** zdiN0bot has quit IRC17:00
*** Gamekiller77 has joined #openstack-meeting17:00
*** ssurana has joined #openstack-meeting17:00
*** _nadya_ has joined #openstack-meeting17:00
*** coreywright is now known as coreywright_17:00
*** hashar is now known as hasharOut17:00
*** jlibosva has joined #openstack-meeting17:01
*** igormarnat has joined #openstack-meeting17:01
*** haomaiwang has quit IRC17:01
*** shardy has joined #openstack-meeting17:02
*** caleb_ has quit IRC17:02
*** mspreitz has joined #openstack-meeting17:03
*** kgriffs|afk is now known as kgriffs17:03
*** xwizard has joined #openstack-meeting17:04
*** arunkant has joined #openstack-meeting17:05
*** rakhmerov has joined #openstack-meeting17:06
*** Ajaeger has joined #openstack-meeting17:06
boris-42#startmeeting rally17:07
openstackMeeting started Tue May 27 17:07:06 2014 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:07
*** openstack changes topic to " (Meeting topic: rally)"17:07
openstackThe meeting name has been set to 'rally'17:07
*** xwizard is now known as tnurlygayanov_17:07
boris-42marcoemorais Gamekiller77 jseutter ping17:07
jseutterhere17:07
Gamekiller77here17:07
*** sushils has joined #openstack-meeting17:08
*** penguinRaider has joined #openstack-meeting17:08
boris-42penguinRaider hi there17:08
*** dims has quit IRC17:08
boris-42msdubov ping17:08
penguinRaiderboris-42, hi :-)17:08
*** sarob has joined #openstack-meeting17:09
*** _nadya_ has quit IRC17:09
*** _nadya_ has joined #openstack-meeting17:09
boris-42#topic persistence context & pre created users17:10
*** openstack changes topic to "persistence context & pre created users (Meeting topic: rally)"17:10
*** sarob_ has joined #openstack-meeting17:10
boris-42marcoemorais hi there17:10
marcoemoraisboris-42: hi, can you see this doc? https://docs.google.com/a/yahoo-inc.com/document/d/1R60Unka07zpiLyjNBM3xgNBGvKE6pJ8yp2BMVxaVyhQ/edit#17:10
boris-42marcoemorais could you introduce everybody in this stuff17:10
boris-42marcoemorais nope17:10
boris-42marcoemorais make it public on the web17:10
*** aviau has quit IRC17:11
marcoemoraisboris-42: let me copy it over to my google drive account — seems that my company settings require person-by-person access when outside the company17:11
Gamekiller77yah will not let me log in at all17:12
*** igordcard has joined #openstack-meeting17:12
*** aviau has joined #openstack-meeting17:12
*** esker has joined #openstack-meeting17:12
marcoemoraisboris-42 Gamekiller77 jseutter: how abt this https://docs.google.com/document/d/16hp6K37C8_j7VQcUGq0oGJ_2dLV4Hlul_IyYpouE-tE/edit#17:12
boris-42marcoemorais ^ this one works17:13
Gamekiller77yup i can see it17:13
*** dims has joined #openstack-meeting17:13
boris-42marcoemorais so actually we will need some kind of blueprint or actually 2 blueprints17:13
*** sarob has quit IRC17:13
boris-42marcoemorais one for persistance-context and one for pre-created-users17:13
*** ssurana has quit IRC17:13
*** evgenyf has quit IRC17:14
boris-42marcoemorais for predefined users we already have https://blueprints.launchpad.net/rally/+spec/benchmark-context-predefined-users17:14
marcoemoraisboris-42: wouldn't pre-created users just be users passed in to 'context —create' to match the schema that rally expects for users?17:14
*** crandquist has joined #openstack-meeting17:14
*** zzelle has joined #openstack-meeting17:14
boris-42marcoemorais but it should be rewritten17:14
*** zzelle has left #openstack-meeting17:14
boris-42marcoemorais yep something like that17:14
boris-42marcoemorais it will be super simple17:14
boris-42marcoemorais after persistence stuff17:14
*** egallen has quit IRC17:15
marcoemoraisboris-42 Gamekiller77 jseutter : I am abt 1/2 through doc, will add more17:15
Gamekiller77that would be super helpful17:15
marcoemoraisboris-42 Gamekiller77 jseutter: would like to put all the comments in the doc, then just have the blueprint point to the doc? what do you thin?17:15
boris-42marcoemorais works for me17:16
jseutterI'm okay with that17:16
boris-42marcoemorais or you can make just empty blueprint17:16
*** gokrokve has joined #openstack-meeting17:16
boris-42marcoemorais with link to this file17:16
marcoemoraisboris-42: yep17:16
Gamekiller77marcoemorais, that would work for me so i can keep reading up on what you guys change17:16
Gamekiller77sorry if this derails the topic is there plans to support other DB systems like MySql for Rally ?17:17
boris-42Gamekiller77 lol17:18
boris-42Gamekiller77 it's already supported..17:18
Gamekiller77crap17:18
Gamekiller77need to read more17:18
Gamekiller77sorry17:18
*** rakhmerov has quit IRC17:18
*** jbrogan has joined #openstack-meeting17:18
boris-42marcoemorais ok doc looks fine just need more details17:18
penguinRaider]17:18
*** jungleboyj has joined #openstack-meeting17:19
*** aviau has quit IRC17:19
*** esker has quit IRC17:19
*** jungleboyj has left #openstack-meeting17:19
boris-42#topic rally as a Service17:19
*** openstack changes topic to "rally as a Service (Meeting topic: rally)"17:19
*** gokrokve_ has joined #openstack-meeting17:19
*** ArxCruz has joined #openstack-meeting17:20
boris-42Okay we already have a base for making service from rally only thing that we need is to implement Controllers17:20
boris-42I am going to implement a first controller and make a list of all things that we need in API17:20
boris-42(another one doc)17:20
*** aviau has joined #openstack-meeting17:20
*** andreaf has quit IRC17:20
boris-42marcoemorais Gamekiller77 penguinRaider jseutter ^17:20
Gamekiller77that sounds good17:21
boris-42any questions?17:21
*** gokrokve has quit IRC17:21
Gamekiller77for the context stuff is there any plans or ideas for static entry possibly via putting them in the DB so you do not have to retype them for each run or a context config files just wondering the flow and thoughts on your side17:22
*** ArxCruz has quit IRC17:22
*** rdopiera has joined #openstack-meeting17:22
boris-42Gamekiller77 did you read that DOC from Marco?)17:22
*** I159_ has quit IRC17:22
*** I159 has quit IRC17:22
*** _nadya_ has quit IRC17:22
Gamekiller77yah was not clear17:22
boris-42Gamekiller77 that is the goal17:23
Gamekiller77good good17:23
boris-42Gamekiller77 of persistence context17:23
marcoemoraisGamekiller77: you use the context subcommand to manage persistence context saved in the db17:23
boris-42Gamekiller77 it is stored in DB so we can run different tasks against one context17:23
Gamekiller77ooo ok now i see it17:23
Gamekiller77perfect17:23
marcoemoraisGamekiller77: when you do a *create* you get a uuid, and you use that uuid to pass to the task subcommand17:23
Gamekiller77sorry but of a noob on this stuff17:23
boris-42Gamekiller77 that allows us to have pre created users17:23
*** amotoki has quit IRC17:23
Gamekiller77that rules17:23
Gamekiller77i can work with that17:24
*** ali-mohsin has joined #openstack-meeting17:24
boris-42Gamekiller77 cause there will be context, that just accepts set of users17:24
marcoemoraisGamekiller77: we will actually accept 1 or more persistence context uuids17:24
Gamekiller77yah see that is perfect17:24
marcoemoraisGamekiller77: in case that you use separate persistence context to store your users and your images, etc..17:24
Gamekiller77i am still learning17:24
boris-42Gamekiller77 you should write some code=)17:24
Gamekiller77hehe need to wipe off my coding fingers17:25
*** mspreitz has quit IRC17:25
*** changbl has joined #openstack-meeting17:25
Gamekiller77need to patch my eclipse17:25
*** ArxCruz has joined #openstack-meeting17:26
boris-42Gamekiller77 hehe=)17:26
boris-42So persisntace-context will be supper cool stuff17:26
Gamekiller77this is all written in python right17:26
boris-42Gamekiller77 yep mostly17:26
Gamekiller77never learned Python17:26
boris-42Gamekiller77 time to do it=)17:26
Gamekiller77mostly C++ for my robots17:26
Gamekiller77need to learn it for my Rasp Pi17:27
Gamekiller77but yes when this gets in place i so want to test it with my setup17:27
boris-42Gamekiller77 =)17:27
boris-42#topic results of summit17:27
*** openstack changes topic to "results of summit (Meeting topic: rally)"17:27
*** emagana has quit IRC17:27
*** Gamekiller77 has quit IRC17:28
boris-42Epic win with osprofiler -> that will be merged everywhere17:28
boris-42so we are going to have out of box working stuff17:28
*** hasharOut has quit IRC17:28
boris-42http://pavlovic.me/rally/profiler/ <- for not related people17:28
marcoemoraisboris-42: +1+1+1+1+117:28
boris-42I am going to finalize lib17:28
boris-42and make one more time version 0.0.117:29
boris-42=)17:29
marcoemoraisboris-42: will Rally be the place to build utilities on top of profiler?17:29
boris-42marcoemorais not sure17:29
marcoemoraisboris-42: in other words, things that summarize the output of profiler eg X counts to db, Y rpc calls, etc…17:30
boris-42marcoemorais osprofiler or rally one of this=)17:30
*** emagana has joined #openstack-meeting17:30
boris-42marcoemorais yep I am still thinking17:30
*** lbragstad has joined #openstack-meeting17:30
marcoemoraisboris-42: basically will be nice to have a cli for profiler17:30
boris-42marcoemorais heh I think probably extending osprofiler lib is better idea17:30
boris-42it's more open source17:30
boris-42then putting in rally it17:31
*** nati_ueno has quit IRC17:31
boris-42#topic Tempest & Rally future steps17:32
*** openstack changes topic to "Tempest & Rally future steps (Meeting topic: rally)"17:32
boris-421. Okay we are going to move out of rally tempest.conf generation17:32
boris-422. We are going to put more data to subunit stream (e.g. duration of setup and cleanup)17:33
*** xyhuang has joined #openstack-meeting17:34
boris-42#topic free discussion17:34
*** openstack changes topic to "free discussion (Meeting topic: rally)"17:34
boris-42marcoemorais jseutter penguinRaider any questions?17:35
marcoemoraisboris-42: are you still receptive to the idea of reporting benchmark results at api call granularity?17:35
boris-42marcoemorais ?17:35
marcoemoraisboris-42: in other words, monkey patching the openstack clients so that every call wraps atomic action timer17:36
boris-42marcoemorais yep17:36
jseutterboris-42: not really.  I'm kind of lost at the moment :)17:36
boris-42marcoemorais it will be very useful17:36
penguinRaiderboris-42, I think I will be able to complete most of my GSOC work well before deadline except for the report generation is there anything else you would want me to work on?17:36
boris-42penguinRaider we will find=)17:36
penguinRaiderboris-42, cool :-)17:37
boris-42penguinRaider but you have a lot of work =)17:37
*** jprovazn has joined #openstack-meeting17:37
penguinRaiderboris-42, yeah I guess but more or less its related similar to each other17:38
boris-42penguinRaider yep it is17:38
*** zz_pablosan is now known as pablosan17:38
boris-42penguinRaider so don't worry if you finish everything fast it will be just bette17:39
*** alexpilotti has quit IRC17:39
boris-42cause we always have a lot of tasks=)17:39
penguinRaiderboris-42, yeah :-)17:39
*** comay has quit IRC17:40
boris-42penguinRaider for example to fix autocomplete stuff in cli=)17:40
*** comay has joined #openstack-meeting17:41
boris-42ok I think we can end meeting=)17:41
boris-42and go to rally chat back=)17:41
*** alexpilotti has joined #openstack-meeting17:41
boris-42#endmeeting17:41
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:41
openstackMeeting ended Tue May 27 17:41:27 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:41
*** pablosan is now known as zz_pablosan17:41
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-05-27-17.07.html17:41
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-05-27-17.07.txt17:41
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2014/rally.2014-05-27-17.07.log.html17:41
*** eghobo has quit IRC17:41
*** eghobo has joined #openstack-meeting17:42
*** ali-mohsin has quit IRC17:42
*** nati_ueno has joined #openstack-meeting17:42
*** aswadr has left #openstack-meeting17:42
*** zhiyan_ is now known as zhiyan17:43
*** caleb_ has joined #openstack-meeting17:44
*** vhoward has joined #openstack-meeting17:49
*** jlibosva has quit IRC17:49
*** caleb_ has quit IRC17:52
*** zhiyan is now known as zhiyan_17:52
*** davlaps has joined #openstack-meeting17:52
*** caleb_ has joined #openstack-meeting17:52
*** zdiN0bot has joined #openstack-meeting17:52
*** balajiiyer has joined #openstack-meeting17:53
*** caleb_ has quit IRC17:59
*** leeantho has quit IRC17:59
stevemaro/18:00
*** henrynash has joined #openstack-meeting18:00
dolphmayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76, nkinder, lloydm, shrekuma: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:00
morganfainbergdolphm, ayoung, bknudson, dstanek, jamielennox, morganfainberg, stevemar, gyee, henrynash, topol, marekd, lbragstad, joesavak, shardy, fabiog, fmarco76, nkinder, lloydm, shrekuma18:00
morganfainbergit's that time!18:00
stevemarhowdy18:00
henrynashhi18:00
ayoungHello.18:00
lbragstaddolphm: morganfainberg hey18:00
*** nkinder has joined #openstack-meeting18:00
gyee\o18:00
bknudsonhi18:00
*** browne has joined #openstack-meeting18:00
nkindero/18:00
* ayoung just found a chocolate chip cookie in a platic bag in his poocket. 18:01
morganfainberglooks like we have a bunch of people here18:01
* ayoung ready for meeting18:01
morganfainberg#startmeeting keystone18:01
openstackMeeting started Tue May 27 18:01:12 2014 UTC and is due to finish in 60 minutes.  The chair is morganfainberg. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
*** balajiiyer has left #openstack-meeting18:01
morganfainberg#topic identity-specs repo18:01
*** openstack changes topic to "identity-specs repo (Meeting topic: keystone)"18:01
ayoungmorganfainberg, you running things today?18:01
morganfainbergdolphm, o/18:01
dolphmmorganfainberg: this is yours18:01
bknudsonI'm working on a spec18:01
morganfainbergayoung, yeah.18:01
morganfainbergok so we offically have a specs repo now!18:02
*** emaganap has joined #openstack-meeting18:02
* ayoung thinks all of the power of being on monty's team is headed ot morganfainberg 's head18:02
dolphmyay18:02
stevemarhaha18:02
morganfainbergayoung, LOL18:02
morganfainberg#link https://github.com/openstack/keystone-specs18:02
bknudsonthis new spec is for v3 extension advertisement18:02
morganfainbergthe repo is keystone-specs (after much deliberation every program is using the code names)18:02
ayoungmorganfainberg, already updated.  Should be able to just modify the link in .git/config to point to the new repo18:03
*** esker has joined #openstack-meeting18:03
dolphmjuno 1 is june 12, so basically anything not about to land will need a spec https://wiki.openstack.org/wiki/Juno_Release_Schedule18:03
morganfainbergdolphm, ++18:03
*** caleb_ has joined #openstack-meeting18:03
*** esker has quit IRC18:03
*** alexpilotti has quit IRC18:03
*** emagana has quit IRC18:03
*** clu_ has joined #openstack-meeting18:03
*** esker has joined #openstack-meeting18:03
henrynashis there a template of a spec for us to follow (I see a template.rst in there, but not sure it has anything in it)?18:03
morganfainbergkeystone core members are responsible for reviewing specs as well now (we don't have a separate team like some other projects do)18:04
*** thinrichs has quit IRC18:04
dolphmdocs also asked that we move all our specs from identity-api into keystone-specs - which would also make it easier for us to propose API changes as part of spec proposals18:04
stevemarhenrynash, hmmm, there was a lengthy template, i'll see if i can find it18:04
henrynashahh, sorry,  I see it is one level up18:04
bknudsonhenrynash: the template has the sections to fill in18:04
morganfainbergdolphm, does the doc team mind if we don't give them commit rights?18:04
nkinderhenrynash: the template seems to provide a good overiew18:04
morganfainbergdolphm, right now they have commit rights to identity-api18:04
stevemarhenrynash, ++18:04
morganfainbergerm... approval18:04
dolphmhenrynash: there are two - the empty one needs to nuked?18:04
*** ssurana has joined #openstack-meeting18:04
bknudsonit's a symlink18:05
dolphmmorganfainberg: i think that might have been the point - they don't want our API specs :)18:05
morganfainbergdolphm, the templates that are empty are symlinks so docs will build until we have a actual spec18:05
morganfainbergcc henrynash ^18:05
*** david-lyle has joined #openstack-meeting18:05
morganfainbergonce we have a real spec we can remove the symlink18:05
bknudsondon't try checking it out on windows18:05
henrynashmorganfainberg: right, ok got it18:05
morganfainbergbknudson, so, i hear we need to not do symlinks next time and maybe just a copy?18:05
stevemarare we having a J2 cutoff for all features that aren't extensions again?18:06
*** rodrigods has joined #openstack-meeting18:06
morganfainbergor just fix it now as well so we don't break people.18:06
*** ssurana has quit IRC18:06
*** jamielennox has joined #openstack-meeting18:06
dolphmbknudson: this is going to break my workflow then18:06
*** Mandell has joined #openstack-meeting18:06
gyeedefinitely will break windows 8.118:07
*** brich1 has joined #openstack-meeting18:07
*** mrunge has quit IRC18:07
bknudsonseems like we should fix the doc build so that it doesn't break if there's no files in a directory18:07
*** sarob_ has quit IRC18:07
dolphmgyee: windows 8.0 4 life, yo18:07
gyeeheh18:07
*** Mandell has quit IRC18:07
dstanek:( i think i'm in the wrong meeting18:07
morganfainbergbknudson, sure.18:07
morganfainbergbknudson, i think it's just how the index base is built, not sure we can "fix" it though18:08
*** yogeshmehra has joined #openstack-meeting18:08
dolphmmorganfainberg: the symlink dies as soon as we have a real spec, correct?18:08
dolphm(is there only one?)18:08
morganfainbergdolphm, that is the plan18:08
bknudsonmaybe we could have a spec for the release... e.g., there's some work to do for every release18:08
*** _nadya_ has joined #openstack-meeting18:09
morganfainbergdolphm, there is a symlink for each directory (e.g. ksc, juno, etc)18:09
bknudsonfor example, removing stuff that's deprecated.18:09
dolphmbknudson: deprecations and removals and whatnot?18:09
dolphmrelease notes?18:09
morganfainbergdolphm, pre-development notes?18:09
morganfainbergdolphm, summit summary?18:09
*** hashar has joined #openstack-meeting18:09
dolphmi'd like release note contributions to be an artifact produced by the -specs repo anyway18:09
*** Mandell has joined #openstack-meeting18:09
ayoungdolphm, what about a doc about work that was bumped from the previous release?18:11
*** leeantho has joined #openstack-meeting18:12
morganfainbergayoung, i think a summit summary (even if it's just a link to the etherpads) would be a solid start. anything bumped from previous release would need to be re-proposed (might be a summary approval, but still needs reproposal)18:13
dolphmayoung: that'll basically be tracked by blueprints that are unmerged, the specs will have to be proposed as a move to the next release18:13
dolphmmorganfainberg: ++18:13
*** nati_ueno has quit IRC18:13
dolphms/unmerged/not "Implemented"/18:13
*** nati_ueno has joined #openstack-meeting18:14
*** Youcef has joined #openstack-meeting18:14
morganfainbergdolphm, you have a great summary (i saw you taking tons of notes) mind replacing the symlink with that? or something derived from that?18:14
morganfainbergand future releases we'll do the same18:14
dolphmmorganfainberg: my summit summary thing?18:14
*** samcdona has quit IRC18:14
morganfainbergdolphm, yeah18:15
*** rakhmerov has joined #openstack-meeting18:15
dolphmmorganfainberg: i'm not clear on what do you want me to do with it?18:15
dolphm#link http://dolphm.com/openstack-juno-design-summit-outcomes-for-keystone/18:15
dstanekmorganfainberg: even with real docs won't it still be broken on windows because of the specs symlink?18:15
morganfainbergdolphm, aha, i was thinking of just taking that and stick it in the repo as the "juno targets"18:15
morganfainbergdolphm, instead of the symlink to the template18:16
dolphmmorganfainberg: not all of them are *targets* for juno (like Centralized quota-management), nor specific to keystone (like TC-blessed API conventions)18:16
morganfainbergah18:16
morganfainbergdstanek, probably same issue :(18:17
dolphmmorganfainberg: i don't know that we need to care too much about -specs + windows18:18
morganfainbergdolphm, probably not.18:18
*** hashar is now known as hasharOut18:18
dolphmclient seems to be the only place where windows users seem to appear18:18
dolphmand they're few and far between18:18
morganfainbergwill client run on windows 3.1 for workgroups?18:19
bknudsonanother lame joke that went terribly awry.18:19
morganfainbergcause...18:19
*** gmatefi has joined #openstack-meeting18:19
morganfainbergbknudson, legitimately my previous company many people contributed from windows systems (did checkouts etc)18:19
morganfainbergmost converted to a non-windows OS eventually18:19
dolphmmorganfainberg: we only support two stable releases back, so windows 98se & windows XP18:20
morganfainbergdolphm, ++18:20
ayoungWin2k was never considered stable?18:20
dolphmmorganfainberg: #topic18:20
morganfainberganyway back on topic18:21
ayoungExcuse me ME18:21
ayoungWin ME18:21
morganfainbergi think we're done on specs18:21
morganfainbergnext topic18:21
morganfainberg#topic Hackathon information18:21
*** openstack changes topic to "Hackathon information (Meeting topic: keystone)"18:21
morganfainbergdolphm, this one is you.18:21
morganfainberg#link http://dolphm.com/openstack-keystone-hackathon-for-juno/18:21
dolphmi have no new information to report since last week :( haven't heard back from geekdom but i sent them another ping today18:21
*** krtaylor has quit IRC18:22
dolphmif you are eager to book something, do flights but not hotels yet18:22
bknudsonrackspace is not close to geekdome?18:22
dstanekdates are firm right?18:23
dolphmbknudson: geekdom is middle of downtown18:23
dolphmdstanek: yes, let's say dates are firm. if geekdom somehow falls through, we'll do rackspace castle again18:23
dstanekok, on the security lists there were telling folks to get approval for those dates18:24
dolphmcool18:24
bknudsonI understand there's an OSSG meeting before keystone meeting18:24
nkinderdstanek: the security team is likely going to move things to a different date18:24
dstaneknkinder: not the same week anymore?18:24
dolphmnkinder: significantly later in the cycle, or?18:24
nkinderthere are some date conflicts for a number of OSSG members, so something else will likely be set up18:24
nkinderThe exact dates aren't clear yet.18:25
*** edmondsw has joined #openstack-meeting18:25
dstanekah, i didn't see that follow up18:25
dolphmnkinder: and barbican is still planning on July 7, 8, 9, correct?18:25
nkinderdolphm: that is my understanding, yes18:25
morganfainbergnkinder, thats unfortunate would have been good to have all the security minded folks/teams (OSSG, barbican, keystone) around18:25
dolphmgood, because i'm pursuing space for them on those dates :P18:25
nkinderdstanek: it was sent out privately18:25
*** reed has joined #openstack-meeting18:25
dstaneknkinder: that would explain it then..that's too bad - i was looking forward to seeing how you guys operate18:26
gyeemorganfainberg, security is a mindset anyway :)18:26
morganfainberggyee, hehe18:26
bknudsonsince we've got the OSSG we don't have to think about security for ourselves18:27
nkinder:o18:27
dstanekbknudson: that's a good point! we can just mark everything as having a security impact18:27
ayoungShall we talk plugins?18:27
morganfainberg#info Dates are set for meetup July 9-11th, 201418:28
morganfainberg#topic Open Discussion18:28
*** openstack changes topic to "Open Discussion (Meeting topic: keystone)"18:28
nkinderI added a topic to the agenda about auth plugins18:28
morganfainbergnkinder, hm i didn't see it18:28
morganfainbergnkinder, aha18:28
morganfainbergok18:28
morganfainbergwell then18:28
morganfainberg#topic Auth plugin method signature changes18:28
*** openstack changes topic to "Auth plugin method signature changes (Meeting topic: keystone)"18:28
morganfainbergnkinder, all you18:28
*** jmontemayor has joined #openstack-meeting18:29
ayoungBreak all the old clients!18:29
nkinderI'm working on hardening how unscoped/scoped tokens work when using a token for auth18:29
*** rakhmerov has quit IRC18:29
nkinderThis requires scope information from the request to be available inside of the auth plugins18:29
gyeeayoung, you break the clients, somebody will wait for you at the parking lot18:29
ayoungnkinder, specifically from Horizon, which is the nasty use case....18:29
nkinderUnfortunately, we don't pass that info right now.18:29
*** jmontemayor has quit IRC18:29
ayoungnkinder, auth plugins are mistnamed18:30
ayoungthis on the server, you mean?18:30
ayoungon the server, auth plugins should be authentication only18:30
nkinderI would like to pass the entire AuthInfo object (or a copy) to the auth plugins, but this requires changing the public method signature18:30
*** jmontemayor has joined #openstack-meeting18:30
*** che-arne has quit IRC18:30
*** ajayaa has joined #openstack-meeting18:30
nkinderforget horizon.  I'm talking about the keystone server18:30
bknudsonthere's other ways to pass it in... for example could have a setter18:30
gyeenkinder, so you want to entire payload18:31
ayoungbknudson, nope18:31
ayoungwe need the token creation to be a pipeline18:31
ayoungthis is not a job for the auth plugins,18:31
ayoungthis is for the Token Provider18:31
bknudsoncould provide a new method18:31
nkinderayoung: well, this is specific to token authentication18:31
morganfainbergbknudson, ReallySecureTokenAuthNoWeMeanItThisTime?18:31
ayoungnkinder, doesn't matter...the user is still authenticated, just not authorized for that new service18:32
nkinderif I authenticate with an existing token, I want to disallow changing project scope18:32
bknudsonmorganfainberg: authenticate2()18:32
ayoungnkinder, that is fine, but it should not be auth plugin that does that18:32
ayoungits in18:32
ayoungthe monolith18:32
morganfainbergbknudson, ++ yeah or conditional with a decorator or something.18:32
gyeeI thought authentication and scoping are two separate deal18:32
bknudsonwhy can't we change project scope?18:32
gyeescoping is controlled by policies18:32
*** ssurana has joined #openstack-meeting18:32
*** shivharis has joined #openstack-meeting18:32
*** shivharis has left #openstack-meeting18:33
nkinderayoung: ok, so we would need a whole new method that an authn/authz plugin would have to deal with.18:33
dstanekdoes the plugin have access to the request object?18:33
ayounghttp://git.openstack.org/cgit/openstack/keystone/tree/keystone/token/providers/common.py#n41418:33
bknudsonif I request a token with no scope and the user has a default project then it'll be scoped to the project18:33
nkinderok, let me step back to talk about scoping18:33
morganfainbergbknudson, isn't that a v2.0 ism?18:33
dstanekthis seems like that that belongs on the request itself18:33
bknudsonso I'd have to get an unscoped token18:33
ayoungnkinder, I don't think so....I think that we need logic in that provider...18:33
ayoungbut we need to make the token pipeline easier to work with18:33
nkinderThe idea is that an unscoped token is like a TGT in Kerberos18:33
ayoungright now the logic for v3 is like this:18:33
nkinderIt can be used to fetch scoped tokens18:33
nkinderayoung: wait and let me explain the motivation first18:33
*** ssurana has quit IRC18:34
ayoungaut.controller->pluging->token.provider18:34
nkindera scoped token should only be allowed to be used for the project it is scoped to18:34
nkinderCurrently, you can take a scoped token and authenticate with it to get a new token for another project (or even a new unscoped token)18:34
ayoungnkinder, oh, I agree with you that it is broken as is18:35
bknudsonmorganfainberg: not sure what you mean about v2.0ism -- v3 has default_project and v2 has tenantId (or tenant_id??)18:35
nkinderThis means that a scoped token has no security properties, as a service that obtains the token can be used to get another token to perform other operations.18:35
ayoungand Horizon is what has caused that brokenness18:35
morganfainbergjamielennox, how much breakage would that cause in the session object(s)? ^ or how hard would that be?18:35
gyeenkinder, you can rescope if you don't have roles on that project18:35
gyeeyou can't18:35
nkinderI would like scoped tokens to be used to allow a user to create a restricted token18:35
ayoungnkinder, an unscoped token should not be used to do anything but talk to keystone18:35
morganfainbergayoung, ++18:35
ayounghorizon should hold on to an unscoped token and use it to get scoped tokens for the current project18:36
ayoungasking them to hold on to two tokens per user should not be too dire18:36
nkindergyee: I know, but what if you are an admin on one project and have low level rights on another project?18:36
jamielennoxmorganfainberg: i've always known i need a way to handle rescoping auth plugins, i just haven't got to the point where someone asked for it - beyond that idon't see why it would cause many problems18:36
ayoungthen when a user changes project, they revoke the scoped token and used the unscoped to get a new scoped token18:36
gyeeayoung, that's essentially how horizon operates today, trade in an unscoped token for a scoped token18:36
nkindergyee: in that case, your "low-level" token can be intercepted and reused during it's validity period to get your admin privileges on the other project.18:36
jamielennoxmorganfainberg: although an unscoped token doesn't have any catalog - i would like to change that so an unscoped token at least contains a catalog with keystone it in18:36
*** emaganap has quit IRC18:36
ayoungand the code to enforce that you can only go from unscoped->scoped would be enforced in the token provider18:37
morganfainbergjamielennox, nod.18:37
ayoungjamielennox, ++18:37
*** coreywright_ is now known as coreywright18:37
nkindergyee: I created a writeup with my proposal...18:37
morganfainbergjamielennox, not unreasonable. actually i think that works well into the id-only stuff down the line18:37
nkinder#link https://blog-nkinder.rhcloud.com/?p=10118:37
ayoungjamielennox, gyee that is not how Horizon operates18:37
*** chuckC has quit IRC18:38
ayoungits how horizon should operate, but they instead keep one, scoped token around, and expect to be able to transfer that to another scoped token18:38
jamielennoxayoung: ?18:38
morganfainberghorizon also does explicit token revocations now.18:38
morganfainbergayoung, i think we have to work with them in either case on this front18:38
ayoungmorganfainberg, I know.  I broke that at one point, too18:38
gyeenkinder, ahh, escalated privilege18:38
jamielennoxright, this will cause problems for horizon and mean that we need to remove the concept of default_project_id - these are things i'm in favour of but it's a tough transition18:38
ayoungand I think we should break that rule to work like this:18:38
nkindergyee: yes18:38
ayoung1.  Unscoped tokens are for Horizon.  An unscoped has an origin18:38
morganfainbergjamielennox, default_project_id has been painful over many releases18:39
ayoungan unscoped token must come fromthat origin and will time out in 10 minutes18:39
ayoungbasically, make unscoped tokens a session18:39
ayoungso, sliding windo18:39
ayoungw18:39
morganfainbergayoung, with a refresh timer perhaps?18:39
ayoungif they refresh unscoped within 10 minutes, they get a new unscoped18:39
ayounglets call them session tokens18:39
gyeenkinder, in that case, any rescoping is bad then?18:40
nkindergyee: yes, which is the patch I was working on18:40
ayounggyee, session token to scoped token18:40
morganfainberggyee, it's less secure overall.18:40
nkindergyee: unscoped->scoped should be allowed18:40
ayoungonly thing that should be allowed18:40
nkindergyee: projA -> projB should not be allowed18:40
ayoungnkinder, and only from the same origin as the unscoped was requested from18:40
gyeebut unscoped->scoped would have the same effect right?18:41
morganfainbergayoung, or would you accept a unscoped token w/ say x509 binding vs strict origin?18:41
nkindergyee: unscoped is a privileged token.18:41
ayoungideally, unscoped session tokens would be bound to a Kerberos principal or an x50918:41
jamielennoxnkinder: i like that, it's how i thought unscoped tokens worked originally and then i found the default_project mess18:41
*** ssurana has joined #openstack-meeting18:41
jamielennoxit gives an actual purpose to unscoped tokens18:41
*** IlyaE has quit IRC18:41
ayoungmorganfainberg, if Horizon used an X509 to talk to Keystone, that would be what the token gets bound to18:41
gyeenkinder, what I mean is if I intercept an unscoped token, its go-time too right?18:42
morganfainbergayoung, i was thinking of unscoped from non-horizon clients18:42
nkindergyee: you hang onto it and use it to fetch scoped tokens as needed.  You only use the unscoped token to talk to Keystone and get scoped tokens.18:42
nkindergyee: yes, which is why you only ever send it to keystone18:42
ayoungmorganfainberg, bind to an X509 or Kerberos principal18:42
nkindergyee: over SSL/TLS...18:42
morganfainbergayoung, ++18:42
dstaneknkinder: ayoung: what do you mean by origin?18:42
gyeehelll yeah, I am all for x.50918:42
ayoungdstanek I want to guard against stolen tokens18:42
ayoungso I would say:18:43
ayoungif Kerberos or X509 is in use, then "origin" means "same authentication doc"18:43
*** emagana has joined #openstack-meeting18:43
ayoungdstanek, but if not...look at the requestor IP Address?18:43
*** tkay has quit IRC18:43
ayoungI don;t know if there really is a way to limit the damage done there, but we should at least try18:43
*** emagana has quit IRC18:44
dstanekayoung: so horizon (and other services) would be passing that through to keystone?18:44
*** zhiyan_ is now known as zhiyan18:44
morganfainbergdstanek, ayoung   or something like csrf from the horizon18:44
ayoungdstanek, yeah18:44
morganfainbergdstanek, just some kind of binding to try and ensure authenticity of the requestor18:44
ayoungdstanek, wait...no18:44
*** markwash has quit IRC18:44
ayoungdstanek, I mean that Horizon requests the token18:44
ayoungHorizon would not pass it through.18:44
dstanekayoung: and then only horizon can use the token?18:44
ayoungSo If I get an unscoped from Horizon, only Horizon can use it to get a scoped from Keystone18:44
ayoung++18:45
*** emaganap has joined #openstack-meeting18:45
morganfainbergnkinder, how close are we aiming to re-implementing kerberos ? [not a bad thing]18:45
dstanekdoes that only apply for unscoped?18:45
*** wenlock has joined #openstack-meeting18:45
*** jmontemayor has quit IRC18:45
gyeere-implementing kerberos?18:45
*** rpodolyaka1 has joined #openstack-meeting18:45
morganfainberggyee, token-granting-tokens, etc.18:45
nkindermorganfainberg: it's similar conceptually18:46
ayoungmorganfainberg, this is not Kerberos18:46
*** raildo has joined #openstack-meeting18:46
nkindermorganfainberg: it's still quite different though18:46
ayoungKerberos is authentication.  THis is authorization18:46
*** chuckC has joined #openstack-meeting18:46
henrynashi’d say just making unscoped tokens shortlived plus only allowing unscoped->scoped (and not scoped->scoped) would in itslef me a major step fowrard18:46
*** rcarrillocruz has joined #openstack-meeting18:46
gyeeso we have kite, and this thing?18:46
*** yogeshmehra has quit IRC18:46
gyeeboth based on Kerberos?18:46
ayounghenrynash, ++18:46
*** akuznetsov has quit IRC18:46
morganfainbergnkinder, ok making sure we weren't just going too far down a path of reimplementing18:47
*** beagles has left #openstack-meeting18:47
morganfainbergnkinder, figured we were fairly diverged still18:47
morganfainbergayoung, ++18:47
bknudsondo we have a way to force an unscoped token even if user has a defualt project?18:47
nkindermorganfainberg: yeah, it's very different in other areas (revocation abilities, etc.)18:47
ayoungmorganfainberg, now....SAML is a different question18:47
nkinderbknudson: it didn't look like it to me18:48
henrynashbknudson: no18:48
gyeebknudson, I am afraid not18:48
bknudsonseems like we'd just scope: {}18:48
nkinderbknudson: I had to unset the default project to get an unscoped token18:48
ayoungbknudson, yeah, we could return both?18:48
jamielennoxso what is the advantage of shortening unscoped tokens? currently you can't get a token with a longer lifetime than the one that was used to authenticate it18:48
henrynashbknudson: once you specify the defaul_project in the user entity, no unscoped tokens from then pb18:48
ayoungjamielennox, we need to change that18:48
henrynash(then on)18:48
nkinderjamielennox: ayoung wants that for the horizon session case really18:48
ayoungwe need to let a session be a session and have a sliding windo18:48
ayoungw18:48
nkinderjamielennox: time out an inactive user18:48
morganfainbergwe would actually need unscoped tokens to live longer than scoped18:49
ayoung10 minutes18:49
ayoungmorganfainberg, nope18:49
ayoungwe need them to live a very short time, but be renewable18:49
*** jmontemayor has joined #openstack-meeting18:49
bknudsondo we revoke unscoped tokens when the password changes?18:49
*** IlyaE has joined #openstack-meeting18:49
henrynashbknudson: I’d hope so….18:49
*** tkay has joined #openstack-meeting18:50
*** markvoelker has quit IRC18:50
nkinderbknudson: hopefully you're not using passwords in the first place... :)18:50
morganfainbergayoung, so scoped tokens would no longer be revoked if the parent unscoped token was?18:50
ayoungbknudson, I'd say so, yes18:50
*** zdiN0bot has quit IRC18:50
dstanekayoung: for long running operations would the calling service have to renew the token?18:50
bknudsonI guess it only applies to sql users anyways, so really doesn't work anyways18:50
morganfainbergayoung, or just the validity of the scoped token would extend beyond the unscoped (depending on config)18:50
morganfainberg?18:50
*** jmontemayor has quit IRC18:50
*** jcallawa has joined #openstack-meeting18:50
ayoungmorganfainberg, correct: but we should support the opposite18:50
morganfainbergayoung, right. ok18:50
nkinderI think the short lived unscoped token idea is really a second step18:50
ayoungrevoke unscoped->revoke all scoped...18:50
morganfainbergayoung, truely a session token18:51
jamielennoxnkinder: ++, i'm not sold on that yet18:51
nkinderThe first step would be to just lock down the unscoped->scoped idea18:51
morganfainbergnkinder, i'd probably make it configurable: default is the same TTL as normal tokens18:51
*** IlyaE has quit IRC18:51
nkinderWith the current code, the scoped token inherits the expiration time from the scoped token18:51
henrynashnkinder: ..from the unscoped one18:52
morganfainberghenrynash, from any token, expiry is the same18:52
nkinderhenrynash: whoops, correct (though you currently CAN go scoped->scoped)18:52
ayoungnkinder, we need to solve these other issues too18:52
henrynashmorganfainberg: yep18:52
morganfainbergas it's parent18:52
morganfainbergwe would need some other unique identifier to solve the unscoped inheritance then18:52
nkinderayoung: yes, but it's not a pre-requisite18:52
ayoungI don't think we want to do this in two jumps18:52
ayoungnkinder, it kindof it18:52
ayoungis18:52
*** jesusaurus has quit IRC18:53
ayoungnkinder, the whole "whoops we just loggged you out" thing in Horizon is going to be a problem18:53
dstaneknkinder: is your blog post going to be turned into a spec?18:53
*** hasharOut is now known as hashar18:53
nkinderdstanek: yes, I'm going to write one18:53
dstaneki'm very curious to read about all of these cases18:53
ayoungnkinder, we can implement in steps18:53
nkinderayoung: how is that different than now?18:53
ayoungbut lets figure out the whole design,18:53
ayoungnkinder, we shortened the token length to an hour18:53
ayoungbeforer it was the whole day18:53
morganfainbergayoung, e.g. a spec proposed? :P18:53
morganfainbergayoung, i think we can solve the design in the spec.18:54
nkinderok, so my question was really about where the scope change should be implemented, as I was trying to put it in the token auth plugin18:54
ayoungnkinder, we will have puppet resetting the default back to 24 hours or whatever18:54
ayoungmorganfainberg, ++18:54
nkinderIt sounds like I should look at the token provider and deal with it there if the 'token' method is listed18:54
ayoungmorganfainberg, just so long as this is understood in context18:55
*** zhiyan is now known as zhiyan_18:55
ayoungnkinder, No, we need to deal with it in Horizon first18:55
ayoungI already had that "fix" yanked about 18 months ago18:55
nkinderayoung: Well, that brings the second part of this...  Should the behavior be configurable?18:55
morganfainbergnkinder, i think the answer is yes it goes in the provider, but it blocks on getting horizon to solve some issues.18:55
ayoungnkinder, Oh god, no18:56
nkinderWe can't lock this down until Horizon knows how to deal with it18:56
jamielennoxhow much does horizon really have to do? it must already handle the case where it gets either an unscoped token or a scoped one on first auth18:56
*** lsmola2 has joined #openstack-meeting18:56
*** trey_h_ has joined #openstack-meeting18:56
ayoungnkinder, would you want to ever be able to hand in a kerberos service ticket to get another service ticket?  Should that be configurable?18:56
ayounglets just fix it18:56
morganfainbergjamielennox, minor changes really, but we couldn't make this hard and fast unless horizon had those changes.18:56
bknudsonI'd expect Horizon doesn't care if it gets a scoped token or unscoped, treats them as unscoped either way18:57
nkinderI think Horizon would need to get the unscoped token and just use it to get a scoped token when you select a project18:57
ayoungnkinder, yes18:57
*** UtahDave has joined #openstack-meeting18:57
ayoungnkinder, and...funny you should mention that18:57
morganfainbergdolphm, do we support the concept of keystone across different versions of other services?18:57
ayoungif I might remind morganfainberg about his request for Kerberos help18:57
morganfainbergdolphm, don't think that is a real OS requirement... but.18:57
nkindermorganfainberg: that's one of my worries too18:57
jamielennoxmorganfainberg, bknudson: right, so lets get something proposed and I don't think horizon will have the problems we thing18:57
ayoungThere is a pattern here:  Horizon work to talk to Keystone is something that is going to require some design18:57
nkindermorganfainberg: ...which would be an argument for making it configurable (even though I'd prefer not to)18:58
*** markvoelker has joined #openstack-meeting18:58
*** trey_h has quit IRC18:58
morganfainbergnkinder, i don't know how many people don't deploy lock-step18:58
*** nati_ueno has quit IRC18:58
morganfainbergnkinder, i think this impacts orgs that track master much more though18:58
morganfainbergnkinder, it probably needs to be configurable18:58
ayoungnkinder, OK,  so I kind of agree, in that I want to break the token provider up into a pipeline18:58
morganfainberg~1min18:59
ayoungand the "token  to token" portion could be swapped out then18:59
*** nati_ueno has joined #openstack-meeting18:59
*** arnaud__ has joined #openstack-meeting18:59
ayoungnkinder, I'd like to have a separate paste pipeline where its like:18:59
nkindermorganfainberg: that's the same conclusion I was arriving at.  Leave the default behavior as it is today, change horizon, then switch the default down the road18:59
morganfainbergok lets take this back to -keystone18:59
morganfainbergthanks everyone!18:59
*** browne has left #openstack-meeting18:59
ayoungauth_plugins  biz_rule1 2 3 4  sign_token _persist18:59
*** arnaud__ has quit IRC18:59
morganfainberg#endmeeting18:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:59
openstackMeeting ended Tue May 27 18:59:47 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-05-27-18.01.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-05-27-18.01.txt18:59
nkinderah, it's time already...  Thanks for letting me hijack the second half of the meeting18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2014/keystone.2014-05-27-18.01.log.html18:59
fungihey-o!19:00
jeblairinfra folks?19:00
*** caleb_ has quit IRC19:00
rdopierahello19:00
mordredo/19:00
zaroo/19:00
SergeyLukjanovo/19:00
*** brich1 has quit IRC19:00
jeblair#startmeeting infra19:00
openstackMeeting started Tue May 27 19:00:30 2014 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: infra)"19:00
openstackThe meeting name has been set to 'infra'19:00
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:00
jeblairagenda ^19:00
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-05-20-19.02.html19:00
jeblairprevious meeting ^19:00
jeblair#topic Actions from last meeting19:00
jeblairfungi add a wait for acl file creation on gerrit project initialization19:00
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:00
fungijeblair: lemme find the review and see if it merged19:00
jeblairfungi: istr you put a patch up for that19:01
clarkbo/19:01
anteayao/19:01
jeblairbut we didn't test it with the recent batch of creates19:01
*** rpodolyaka1 has left #openstack-meeting19:01
ianwo/19:01
fungi#link https://review.openstack.org/#/c/94684/19:01
jeblairi think SergeyLukjanov submitted a patch to create a specs repo19:01
fungilooks like i wuo'd it19:01
*** jamielennox has left #openstack-meeting19:01
fungiwip'd19:01
jeblairshould we try to use it for that create?19:01
clarkbyes, SergeyLukjanov has a change up for sahara-specs I have +2'd it looks good19:01
SergeyLukjanovjeblair, i do19:02
fungineed to rework it to jive with sdague's https://review.openstack.org/94196 error handling19:02
fungii'll do that right after the wrap up the meeting19:02
fungiright after we19:02
*** beagles has joined #openstack-meeting19:02
*** derekh_ has joined #openstack-meeting19:02
*** krtaylor_ has joined #openstack-meeting19:02
jeblair#topic  manage-projects status (fungi)19:02
*** openstack changes topic to "manage-projects status (fungi) (Meeting topic: infra)"19:02
jeblairi think we kind of just did that19:03
fungiyup19:03
jeblair#topic  A home for Devstack within Infra (anteaya)19:03
*** openstack changes topic to "A home for Devstack within Infra (anteaya) (Meeting topic: infra)"19:03
anteayao/19:03
fungihome is where you hang your devstack19:03
anteayaso right now the devstack docs aren't under the infra umbrella19:03
anteayait would be helpful if they were19:03
*** nkinder has left #openstack-meeting19:03
anteayadtroyer is amenable to that19:03
anteayatwo things are needed19:03
*** jang has quit IRC19:04
clarkbanteaya: you mean the stuff on devstack.org?19:04
anteayasomeone at the foundation willing for anotherjesse to transfer the devstack.org name to19:04
anteayayes19:04
anteayaand an ip for the stuff19:04
anteayathoughts?19:04
jeblairthat would probably be jbryce; i believe he has handled most of the domain transfers19:04
fungiwas anyone able to get in touch with anotherjessee about it?19:04
*** rdopiera has quit IRC19:04
*** Penick has joined #openstack-meeting19:04
anteayayes19:04
anteayadtroyer had that chat19:04
fungiokay, great19:04
*** rdopiera has joined #openstack-meeting19:04
anteayaanotherjessee is willing to make the transfer19:04
anteayawe just need someone to catch19:05
jeblairi believe that jbryce and sparkycollier would be happy for that to happen19:05
anteayayay19:05
anteayaso I will track down jbryce and see if he can coordinate with anotherjesse19:05
*** baoli has quit IRC19:05
jeblairanteaya: Jonathan Bryce <jonathan@openstack.org>, Mark Collier <mark@openstack.org>19:05
anteayagreat19:05
clarkbwe should be able to start publishing the docs to a new location now too19:05
anteayawhich leaves the ip19:05
clarkbthey justwon't be available at devstack.org19:05
anteayaso what server do we want them to live on19:05
*** baoli has joined #openstack-meeting19:06
anteayaand if we have devstack.org, we can control where folks land when they use it19:06
fungii assume we just create another rackspace cloudsites site and use the same docs jobs we're using for docs.o.o, developer.o.o, et cetera19:06
*** Mandell has quit IRC19:06
*** pdmars has joined #openstack-meeting19:06
jeblairmaybe docs.openstack.org/developer/devstack would be okay19:06
jeblairthat's where project docs usually live19:06
clarkbjeblair: I like that19:07
*** tvoran has joined #openstack-meeting19:07
fungior that, and a redirect at devstack.org19:07
fungime too19:07
clarkbannegentle: ^ are you around?19:07
*** gmatefi has quit IRC19:07
*** jmontemayor has joined #openstack-meeting19:07
anteayadtroyer isn't here right now, but I would like his input on the path19:07
anteayabut for now I can get the domain transfer underway19:07
*** rockyg has joined #openstack-meeting19:07
anteayaand hope to hear from dtroyer by next week19:07
jeblairanteaya: ++ we can work out the rest later19:07
*** lcheng_ has quit IRC19:08
fungiprobably just worth noting that we can either host content at devstack.org or have it redirect to an existing docs site and get the interested parties to weigh in19:08
*** IlyaE has joined #openstack-meeting19:08
jeblairfungi: yep19:08
*** lcheng_ has joined #openstack-meeting19:08
SergeyLukjanov++ for docs.openstack.org/developer/devstack and redirect from devstack.org19:08
jeblairanteaya: end of topic?19:08
anteayayes19:08
anteayathanks19:08
mordredwell19:08
jeblairthank you!19:08
jeblairmordred: oh?19:08
mordredwe should probably figure out the docs build19:08
mordredthey're in gh-pages right now19:09
mordredshouldn't be hard - but that's not how we do other thigns19:09
anteayaI'd like dtroyer here for this part19:09
fungiyeah, that's a task to add to the list... get docs building so they can be uploaded in cooked format rather than raw19:09
anteayacan we continue this next week?19:09
mordredfungi: ++19:09
jeblairmordred: well 'gh-pages' isn't so much a build thing as a publish thing19:09
jeblairmordred: and i think the conversation so far has been about changing how we publish it19:09
mordredjeblair: yes. except I think gh-page will auto-render md for you?19:10
mordredjeblair: sure - just saying - the thing that puts things in gh-pages may need to be investigated - it's possible it's a human19:10
anteayadtroyer has some specific things he is looking for19:10
jeblairmordred: yeah, i think it's static content19:10
fungiright, presumably there are some additional transformations which will need to be applied to the current source to turn it into something we can put on a webserver19:10
anteayaand it is best if I let him tell you19:10
mordredkk19:10
fungior maybe it's just straight html in which case no need19:10
jeblairmordred: once we have a publishing method for the content, then we have a known way to change the content.19:10
mordredjeblair: ++19:11
jeblair#topic  Third Party CI Gerrit Account name format (anteaya)19:11
*** openstack changes topic to "Third Party CI Gerrit Account name format (anteaya) (Meeting topic: infra)"19:11
anteayaokay so on the linked etherpad19:11
jeblair#link https://etherpad.openstack.org/p/juno-infra-improving-3rd-party-testing19:11
anteayathanks19:11
anteayathere was a request for standardization of third party ci names19:11
anteayafor email filtering19:11
anteayaand it has also come up on the ml for filtering for gerrit js19:12
anteayahow do we decide a new format?19:12
fungiyeah, we didn't get time to discuss it at that summit session, but i stuck it on there just because i've been asked for it a few times as well (in regard to e-mail filtering)19:12
anteayathen how to we get current accounts to comply with the new format?19:12
krtaylor_That was me19:12
jeblairsomething like "Foo CI" ?19:12
anteayayay krtaylor_19:12
clarkbjeblair: I like Foo Bot19:12
fungikrtaylor_: oh, perhaps you read my mind then ;) thanks!19:13
jeblairanteaya: we're going to ask third party ci folks to make several changes; i think we should do it all at once...19:13
clarkbbecause we may want bots to do other things19:13
* anteaya nods19:13
*** jang has joined #openstack-meeting19:13
anteayaand there was a comment on the email list that there are more bots than just ci bots19:13
jeblairanteaya: so that means getting the new wiki pages set up, and making sure we have each of the new reqs documented19:13
ianwclarkb: bot seems like a common suffix, so you might have foobot bot?19:13
anteayaso perhaps more than one filter19:13
fungiright, the consensus so far had been that we should have a pattern which identifies clearly that the account is for an automated system and able to differentiate whether it's a third-party system or one run by infra19:13
jeblairanteaya: then i think we ask them all to change once that is all in order19:13
anteayayes19:13
*** raildo has left #openstack-meeting19:13
anteayasounds fair19:13
fungiand i think the welcome message account should probably get exempted from that19:14
anteayayes19:14
anteayaso there are bots19:14
anteayathere is ci19:14
clarkband there is third party19:14
anteayathere is the welcome message account19:14
anteayais third party the same set as ci?19:14
jeblairthere's the proposal bot -- are there any other bots that are not 3rd party ci or welcome message?19:15
fungi"jenkins"19:15
*** vkmc has quit IRC19:15
anteayawhat is the project creator bot19:15
fungianteaya: that one doesn't comment19:15
Ajaeger"OpenStack Proposal Bot" ;)19:15
mordredI can't think of any others that leave comments righ tnow19:15
anteayaso it sounds like we have to list all the accounts affected by this as a starting point19:15
Ajaegerbut that one does not comment19:15
anteayathen decided on categories19:15
fungiwe did have "trivial rebase" commenting, but that's gone with gerrit 2.819:16
anteayathen select a keyword that a regex can isolate19:16
jeblairi'm just not sure that we need to design a naming system that accomodates the proposal bot...  it does something very different than 3rd party ci and doesn't leave comments19:16
anteayaI can start an etherpad listing everthing and then we can work on categorizeing them in a way we agree on19:16
mgagnejeblair: I think you missed elastic recheck bot19:16
ianwwould some api-type service that returns some json describing current bot names work?  seems that could plug in easily to gerritjs19:16
jeblairmgagne: thank you!19:16
mordredI think we should have this on the full name and the username - so "SmokeStack CI" and "smokestack-ci" for instance?19:16
mordredmgagne: ++19:17
krtaylor_I am good with anything as long as it is standardized19:17
*** ssurana has quit IRC19:17
fungii think it's sufficient if we decide in the meeting that it should be done, what eth basic parameters are, and then leave the specifics to hash out in a spec/ml thread/code review19:17
mordredianw: I think people also want to be able to do email filters to not see emails of comments from ci bots19:17
mordredfungi: ++19:17
clarkbfungi: ++19:17
anteayait should be done19:18
jeblairso how about "Foo CI" and "Bar Bot" depending on whether you are, well, a ci system or a bot....19:18
SergeyLukjanovfungi ++19:18
clarkbjeblair: wfm19:18
fungithat seems sane enough19:18
*** jesusaur has joined #openstack-meeting19:18
fungiwhatever we settle on should be encoded in our third-party account documentation19:18
jeblairyup19:18
anteayayes19:18
jeblair#topic  Review Third Party wiki template (anteaya)19:19
*** openstack changes topic to "Review Third Party wiki template (anteaya) (Meeting topic: infra)"19:19
fungiwe should start composing the visible names of the accounts ourselves at account creation based on info provided by the requesters19:19
*** olaph has joined #openstack-meeting19:19
anteayaoh me again19:19
jeblair#link https://wiki.openstack.org/wiki/Template:ThirdPartySystemInfoSubst19:19
anteayathanks19:19
jeblairyup, i'm reordering19:19
anteayathere is a template19:19
anteaya#link https://etherpad.openstack.org/p/third-party-wiki-templating19:20
anteayathis is the etherpad I am working from for the templating19:20
clarkbthe template looks good to me19:20
clarkbit captures informantion that would allow me to udnerstand what is going on19:20
anteayagreat, thanks19:20
*** jang has quit IRC19:20
jeblair#link https://wiki.openstack.org/wiki/ThirdPartySystems19:20
fungiwe do need to make sure it's fairly comprehensive before we ask the operators to start filling it out, since we don't want to have to keep going back to them all asking for new bits19:20
jeblairthat's also nice to see ^19:20
anteayaAjaeger put it together for me19:20
jeblairi think that's illustrating how the page structure will come together; i like it19:21
anteayagreat19:21
Ajaegerteamwork with anteaya and fungi!19:21
anteayaI'll work on the other template for the openstack programs template19:21
anteayathanks19:21
anteayaI just needed some initial feedback to ensure we were going in the right direction19:22
anteayaI have what I need from this topic19:22
fungionce we collect info on what projects the operators think they should be voting on, we can start rolling out tighter acls limiting them to that19:22
anteayayay19:22
clarkbfungi: ya and/or just give tem the ability to manage them19:22
Ajaegeranteaya: fifieldt started with this one for programs: https://wiki.openstack.org/wiki/Template:ProjectBox19:22
fungiclarkb: right19:23
anteayaAjaeger: interesting19:23
*** primeministerp has quit IRC19:23
jeblairanteaya: maybe it's implied in structure, but maybe not...19:23
jeblairanteaya: but a description of what is being tested and how would be useful for devs19:23
fungiclarkb: we could set the neutron-tpt group owned by neutron-core for example19:23
anteayaI will make it explict19:23
anteayaI don't find implying anything works with this group19:23
jeblaireg, "we test patches on our super-expensive network switch thingy in such and such configuration"19:24
anteayagreat19:24
*** kenhui has quit IRC19:24
anteayaI will expand that section19:24
jeblair#topic  How do we want to handle patches to openstack_project and openstack tooling that fix downstream issues.19:24
*** openstack changes topic to "How do we want to handle patches to openstack_project and openstack tooling that fix downstream issues. (Meeting topic: infra)"19:24
jeblairclarkb: i think that's you?19:25
clarkbyup19:25
*** rakhmerov has joined #openstack-meeting19:25
clarkbso on the agenda are links to a couple examples of changes that update openstack_project to make it useable by downstreams19:25
jeblairsdague: ping19:25
clarkbI don't want to chase people away when they do those things, but I think that we are misplacing effort19:25
clarkbopenstack_project is well the openstack project19:25
*** Mandell has joined #openstack-meeting19:26
clarkbwe will do domain specific things tehre and IMO allowing for every use case is a bit overboard there19:26
mordredI agree that it's the openstack project - but I think there is a bunch of stuff in it that doesn't need to be there19:26
clarkbwould be good to come up with a consistent way of addressing these things19:26
clarkbmordred: yup agreed19:26
mordredlike, I don't think openstack_project needs to be very configurable19:26
mordredbut I _do_ think a bunch can get refactored out into things that are more re-usable19:26
mordreds/very//19:27
clarkbpersonally I would like to see refactors instead like jesusaur's jenkins reorg19:27
fungii definitely don't want to see us extracting all the variables out of o_p into the global site manifest, for example19:27
mordred++19:27
mordred(to both)19:27
mordredI think also AaronGr's heira-in-tree can help us to have _less_ parameters in openstack_project19:27
mordredbecause many of them are there for passthrough needs19:27
mordredand not because we need parameters19:28
fungiyeah, that has led to a major spaghetti effect19:28
mordredso - if the refactors actually make things cleaner and simpler, I think theyre awesome19:28
mordredand I'd love to stop having to plumb variables through 6 layers of use19:28
rcarrillocruz++19:28
wenlockclarkb we had the same battle when starting to consume config as upstream... it was natural for us to make our own <project>_project , but we also came back with a need for an instance specific module which held more of this config integration with parameters.19:29
jesusaurI think that moving most of the puppet modules out into their own repos would help define the line: openstack-infra/config should be openstack_project and manifests/site.pp (which don't need to be configurable), other modules and projects should be more configurable and reusable19:29
wenlockmoving things to a hiera tree has been helping us alot19:29
fungidistilled, if the change makes it easier for downstreams *and* us to modify, it's worthwhile19:29
mordredfungi: ++19:29
*** rakhmerov has quit IRC19:29
*** jbjohnso has joined #openstack-meeting19:30
jeblairhttps://review.openstack.org/#/c/87384/ is instructive19:30
*** krtaylor_ has quit IRC19:30
fungiand yeah, like jesusaur mentions, we should continue to push for bits people want to reuse to go down into the individual modules when it can be done cleanly, rather than just accepting that everyone tried to reuse openstack_project directly19:30
mordredjeblair: yeah. that's the other aspect of this question19:31
jeblairit's not pupput; it's shell code that we use to build our images19:31
clarkbjeblair: ya so that is the other type of change we see19:31
*** _nadya_ has quit IRC19:31
mordredI think we should take those case-by-case - tbh19:31
jeblairi mean, it's super easy for a downstream to replace it with their own scripts19:31
jeblairbut, otoh, apparently ours are 99.9% good enough19:31
mordredin this case, I think the move to dib will obviate teh need for that patch - and a class of that type of patch19:32
*** eglynn-afk has joined #openstack-meeting19:32
clarkbmordred: to a degree19:32
mordredbut it's still illustrative of a person who needs a feature that wants to go into ours, and it's not a feature we'll ever need19:32
clarkbbut the jenkins scripts fall under that category now too19:32
jeblairso maybe that's a matter of just weighing the extra cost; if it's a few lines of "dead" (to us at least) code, sure.  but if it's more, then we say it's better to use new scripts19:32
mordredbut it facilitates them not forking a script they could otherwise consume19:32
mordredjeblair: ++19:32
clarkbmordred: well so you shouldn't have to fork right?19:32
clarkbyou just set the variable in your wrapper script and exec ours19:32
jeblairclarkb: that's a good approach to this case19:33
*** nati_ueno has quit IRC19:33
mordredclarkb: yes. except the actual mechanics there are hard19:33
clarkbmordred: export FOO=bar ; exec script is hard?19:33
mordredbecause the scripts are in openstack_project, which is not really a thing you're likely to be consuming directly19:33
jeblairmordred: well, we essentially already do that ourselves19:33
fungiwhat i would see as a "good" compromise there would be to refactor some of our scripts to make them better building blocks which can be more easily called from downstream scripts/tooling19:33
clarkbfungi: ++19:34
jeblairfungi: they already are somewhat blocky -- more specific ones call less specific ones19:34
mordredfungi: ++ - but also what jeblair said above, which is that I think we should weight the costs as those come up19:34
mordredand know that we don't want to add senseless complexity19:34
fungiyep, i agree they're mostly that way already19:34
mordredbut oftentimes such refactors help us too19:34
mordredkinda like the devstack-gate hook functions19:35
clarkbyup19:35
*** caleb_ has joined #openstack-meeting19:35
jeblairclarkb: (i think you should suggest the script callout on that patch, see what the authors think)19:35
clarkbjeblair: will do19:35
mordredclarkb: or, tell them to wait for the dib refactor, which already has a different way of dealing with proxies and local content injection19:36
clarkbso I think we haev agreement that we should push towards proper refactoring for reconsumption19:36
mordredclarkb: ++19:36
clarkbif the change is minor then ok19:36
jeblairi was hoping sdague would be around to talk about how this affects test-matrix19:36
clarkbya so test-matrix is the other thing19:36
clarkbmordred: have you fermeted on that more?19:37
clarkb*fermented19:37
* jeblair is worried that he fomented19:37
*** terriyu has quit IRC19:38
clarkbtl;dr on that is again we have instructiev code that determines how we test stuff19:39
clarkband others would like to make it instructive for not upstream openstack19:39
clarkbwhich bothers me because it is clearly an openstack specific tool for upstream testing19:39
mordredyeah - I mean19:39
clarkband we can't test the downstream use case at all19:39
mordredI don't think it's a specific openstack tool19:40
*** lsmola2 has quit IRC19:40
mordredI think we've spent a lot of time telling people to re-use the tools we've written for their internal testing and they've listended19:40
clarkbmordred: it is used to deploy from source openstack clouds19:40
clarkbso that they can be tested19:40
mordredyes19:40
mordredI believe we have tons of people now wanting to replicate this infrastructure that we've built to do exactly that thing19:40
clarkbbut they don't want to replicate the development model19:41
jesusaurclarkb: what do you mean?19:41
mordredwhat I'm saying is that I don't think test-matrix is necessarily or has to necessarily be "upstream only"19:41
clarkbjesusaur: openstack is very particluar in its dev flow in order to handle 1k devs19:41
mordredin fact, I think sean has done a good job of making it a thing which takes data to make decisions19:41
clarkbjesusaur: other folks want to mix it up for their 1k folks19:42
clarkbmordred: right so we discussed making those bits more properly config, but you didn't like that for some reason19:42
clarkb(I forget what the actual concern was)19:42
*** jang has joined #openstack-meeting19:42
jeblairmordred: i don't see how we can keep putting test variations into test-matrix that we don't test; i don't think we can review them intelligently, and i think it will hurt what we're trying to do by making it more complex19:42
mordredjeblair: I do not think we shoudl do that at all, so I agree19:42
jeblairmordred: i think for downstream test configs, that has to live outside of d-g and test-matrix, but we can facilitate that with plugin/hook points, etc.19:43
fungiyeah, i do worry that our current branch handling is already jenga-like to the point where we risk even impacting our own use cases (when a change ends up modifying a behavior we weren't testing well enough)19:43
jeblairclarkb: a config file sounds ideal to me...19:43
mordredyah. agreed19:43
mordredI think the main concern I had ...19:43
jeblairfungi: i think we should have a giant jenga thing at the next summit19:43
fungijeblair: it should be the THEME of the next summity19:43
mordredis that we keep in mind that someone may want to wholesale consume our config for test-matrix as well, and simply to suppliment it19:43
jeblairmordred: sounds reasonable19:44
mordredbut, I think we keep that in mind generally, so it shoudln't be a big departure19:44
*** SumitNaiksatam has joined #openstack-meeting19:44
*** nelsnelson has quit IRC19:44
jeblairclarkb: end of topic?19:44
clarkbjeblair: yes  Ithink so19:44
jeblaircool19:44
jeblair#topic  About splitting Horizon repo in two parts (rdopiera)19:44
*** openstack changes topic to "About splitting Horizon repo in two parts (rdopiera) (Meeting topic: infra)"19:44
clarkbbasically push to refactoring and config rather than instructive code changes19:44
mordredclarkb: I believe our disagreement is that I wanted to add awareness of branch prefixing to our branch fallback algorithm19:45
sdaguejeblair: just back from CSA pickup, what's up?19:45
mordredclarkb: but I think that's out of scope for now19:45
*** nelsnelson has joined #openstack-meeting19:45
*** dprince has quit IRC19:45
mordredooh! splitting horizon!19:45
rdopieraso I came to ask for advice, because we are going to do some changes in the horizon's repos, and we want to know the best way to proceed19:45
jeblairsdague: read previous topic fyi and possible further discussion, but we need to move on now i think19:45
* mordred is excited19:45
jeblairrdopiera: we're very excited!  splitting them should make a lot of things easier!19:46
rdopierabasically what we plan to do is to have a separate repo for the library and the application parts of horizon, plus a bunch of packages for all the js libraries19:46
*** andreaf has joined #openstack-meeting19:46
*** zhiyan_ is now known as zhiyan19:46
fungirdopiera: please clarify what you mean by "packages" in that sense19:46
rdopierathe js libraries part I already started on, we are using xstatic to package them, and putting them on stackforge19:46
fungigot it ;)19:46
krotscheckThis is the “use pip to package javascript things” discussion, yes?19:46
rdopieraxstatic is basically a minimal python package with the js libraries as data files in it19:47
clarkbkrotscheck: partially yes19:47
rdopieraand some metadata19:47
rdopieraso it can be installed from pypi, etc.19:47
jeblairrdopiera: have you put any in stackforge yet?19:47
fungithis is as opposed to installing the js bits via npm and everything else via pip?19:47
clarkbthe change to add them all to stackforge is proposed19:47
rdopierajeblair: there is a patch19:47
*** lcheng_ has quit IRC19:47
clarkbfungi: correct19:48
rdopierathat part is the easy part19:48
rdopierawhat I would like to ask all of you about is tackling the horizon's code itself19:48
rdopierawe were thinking about cloning the repo, and removing half the files in each of them19:48
fungithat does make them somewhat less consumable to the broader js community/ecosystem, though if horizon's dashboard is the only consumer right now then i don't suppose it's much of a concern19:48
rdopierathis way we retain the history and the patch queue on one of them19:48
rdopierafungi: MoinMoin 2 also uses the same system19:49
Ajaegerrdopiera: this might need changes to the translation jobs, please add this to your todo list.19:49
jeblairlet's tackle the repo split first19:49
rdopierafungi: and we hope more apps will use it with time19:49
clarkbrdopiera: typically the way we do this is by git filter branching the initial state of one repo19:49
clarkbthen in the other repo submit a change t odelete the excess19:49
SergeyLukjanovhonestly, I'm feeling some inconsistence when see pip handling js libs19:49
fungirdopiera: right, the git repo split can be fairly easily handled via git filter-branch *if* the files which go in each repo are fairly well separated already19:49
*** nati_ueno has joined #openstack-meeting19:50
jeblairrdopiera: which will be in the "horizon" repo?  the dashboard or library?19:50
rdopierafungi: they are separated19:50
rdopierajeblair: the openstack_dashboard will get renamed to horizon, and the horizon (library) will get renamed to django-horizon19:50
*** lcheng_ has joined #openstack-meeting19:50
fungiand also i'm curious to know what the release model will become for each (both still integrated releases? library switching to ad-hoc with no stable branches?)19:51
rdopierajeblair: so the patch queue will stay with dashboard, which I think is good, because most changes are there19:51
jeblairrdopiera: cool, that makes sense.19:51
anteayawould webui work in there at all for naming19:51
rdopierafungi: simultaneus release, from what I understand19:51
jeblairrdopiera: so we can help with the filter branch when you're ready19:52
anteayaisn't that what we are doing with storyboard and vinz?19:52
*** ajayaa has left #openstack-meeting19:52
clarkbanteaya: the architecture of the two is different19:52
anteayaoh okay19:52
jeblairrdopiera: or if you want to do it, you can just host the new repo somewhere19:52
rdopieradjango-horizon is mostly front-end stuff, like widgets and views19:52
jeblairrdopiera: and when we create the project, import it from there19:52
rdopierajeblair: that sounds good, because I can test different approaches then19:53
jeblairrdopiera: i think that the horizon repo will still have the history for both projects though19:53
clarkbyup and I tink it should19:53
rdopierayes, that's fine19:53
jeblairok19:53
clarkbbecause we need to track that they became two at some point19:53
fungiright, most likely outcome is that the old library bits get deleted from the horizon repo in one mass commit19:53
*** dims has quit IRC19:54
rdopierathat commit will probably invalidate a lot of patches in the queue, but the sooner we do it, the better19:54
jeblairrdopiera: i think what you may want to do is to "freeze" the library inside of horizon, create the new project, then get it working in devstack-gate, then rm the lib from horizon19:54
rdopierajeblair: sorry, what is devstack-gate?19:55
*** jang has quit IRC19:55
jeblairrdopiera: it's what we used to do integration testing of all the projects19:55
jeblairrdopiera: it uses devstack to install everything and runs tempest19:55
*** zhiyan is now known as zhiyan_19:55
rdopieraI will look for it, thank you19:55
fungi#link http://git.openstack.org/cgit/openstack-infra/git-review/tree/README.rst19:56
fungier, wrong link19:56
fungi#link http://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/README.rst19:56
clarkbclose :)19:56
fungi(silly clipboard!)19:56
jeblairrdopiera: so i expect there to be some patches to devstack and devstack-gate after the new project is created19:56
rdopieraok, thank you everyone19:56
jeblairrdopiera: sdague, dtroyer, and i can help out with those parts19:56
jeblairrdopiera: thank you!19:56
*** gyee has quit IRC19:57
jeblairrdopiera: so we don't have a lot of time, and i'm not sure this is the best forum for the discussion anyway, but the other half of this, the xstatic part, interests some of the people here19:57
sdaguejeblair: sounds good19:57
jeblairrdopiera: is there a mailing list thread about it?19:57
*** saschpe has quit IRC19:58
rdopierajeblair: we had a design session on that https://etherpad.openstack.org/p/juno-summit-horizon-static-files19:58
jeblairrdopiera: so that people can learn about it or discuss?  particularly, i want to make sure that zigo weighs in on it19:58
rdopierajeblair: and there is an e-mail with some summary of progress here:19:58
jeblairrdopiera: because i recall from the design session that there was a lot of talk about doing this to help debian, but zigo wasn't actually there19:59
clarkbjeblair: yes and red hat iirc19:59
*** zehicle_at_dell has joined #openstack-meeting19:59
jeblairred hat was there and seemed okay with xstatic19:59
mordredyah - I also have an extreme view myself that it's not our job to make things easier on the distros19:59
rdopierahttp://lists.openstack.org/pipermail/openstack-dev/2014-May/035370.html19:59
clarkbbut fedora does have npm now so I don't know19:59
mordredbut rather to do the thigns that make sense for us19:59
fungipabelanger has also expressed a desire to be able to pip-install the django lib19:59
*** saschpe has joined #openstack-meeting19:59
*** caleb_ has quit IRC20:00
jeblairrdopiera: also, mordred had an idea about using pbr and nodeenv to build things at tarball creation time20:00
mordredyup20:00
*** markmc has joined #openstack-meeting20:00
rdopieramordred: xstatic is actually designed with easy packaging for distros in mind20:00
jeblairso i want to make sure zigo and mordred have an opportunity to chime in20:00
mordredrdopiera: right. I don't share that as a goal20:00
*** nati_ueno has quit IRC20:00
rdopieramordred: you can configure it to keep the actual files in any place20:00
*** markmcclain has joined #openstack-meeting20:00
mordredI share participating in and with upstreams more in mind20:00
mordredand if the distros can't figure out javascript, then they'll be replaced by distros that can figure out javascript20:01
mordredbut like I said, I'm an extremist20:01
jeblairand i think we're out of time20:01
mordred:)20:01
jeblairrdopiera: thanks!20:01
mordredrdopiera: ++20:01
jeblair#endmeeting20:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:01
rdopieracan we continue it tomorrow in -infra?20:01
openstackMeeting ended Tue May 27 20:01:21 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-05-27-19.00.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-05-27-19.00.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2014/infra.2014-05-27-19.00.log.html20:01
mordredrdopiera: always!20:01
*** rcarrillocruz has left #openstack-meeting20:01
fungirdopiera: please to!20:01
fungido!20:01
*** rdopiera has quit IRC20:01
*** caleb_ has joined #openstack-meeting20:01
*** caleb_ has quit IRC20:01
*** jesusaur has quit IRC20:01
ttxAnyone here for the TC meeting ?20:01
jeblairo/20:01
sdagueo/20:01
dhellmanno/20:02
markmcclaino/20:02
vishyo/20:02
*** wenlock has left #openstack-meeting20:02
ttxrussellb, markmc, annegentle, mikal, mordred, devananda, jaypipes: around ?20:02
jaypipeso/20:02
devanandao/20:02
*** caleb_ has joined #openstack-meeting20:02
markmchowdy20:02
annegentleyep20:02
ttx#startmeeting tc20:03
openstackMeeting started Tue May 27 20:03:04 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
zehicle_at_dello/20:03
openstackThe meeting name has been set to 'tc'20:03
mikalMorning20:03
ttxHere is our agenda for today:20:03
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:03
ttxdavid-lyle: around?20:03
david-lyleo/20:03
ttx#topic Integrated projects and new requirements: Gap coverage plan for Horizon20:03
*** openstack changes topic to "Integrated projects and new requirements: Gap coverage plan for Horizon (Meeting topic: tc)"20:03
ttxLast week we did a gap analysis for Horizon20:03
ttx#link https://etherpad.openstack.org/p/horizon-gap-analysis20:03
ttxA number of gaps were identified:20:03
ttx* Scope needs to be documented20:03
ttx* Refresh of horizon-coresec needed20:04
ttx* Integration test framework tied to gate20:04
ttx* Non-standard test/packaging/translation tooling due to combined projects in one repo20:04
ttxTwo non-blocking remarks were made:20:04
ttx* A major architectural change is planned (split of repo into toolkit and django app)20:04
ttx* Would be nice to have a listing of API calls not available in GUI per service20:04
ttxdavid-lyle: Do you have a plan to address the gaps in the near future ?20:04
david-lylehttps://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Horizon_Gap_Coverage20:04
david-lylemissed the non-standard tooling item20:04
*** samcdona has joined #openstack-meeting20:04
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee/Horizon_Gap_Coverage20:05
david-lylewill have to amend20:05
jeblairwell, in the last meeting rdopiera came to talk about splitting the horizon repo20:05
mordredo/20:05
*** zdiN0bot has joined #openstack-meeting20:06
ttxdavid-lyle: plan looks good to me20:06
jeblairso i'm optimistic that will get better soon, though it doesn't necessarily follow that everything will become more standard20:06
markmcnicely done david-lyle20:06
ttxAny objection on the proposed plan ?20:06
*** krtaylor has joined #openstack-meeting20:06
*** marcoemorais has quit IRC20:07
annegentledavid-lyle: where will you document the gaps?20:07
david-lylejeblair: there is a larger issue in the community regarding nodejs20:07
*** marcoemorais has joined #openstack-meeting20:07
sdaguettx: lgtm20:07
david-lyleannegentle: good question, likely on w.o.o20:07
david-lyleI think it's too transient to put anywhere in the code base20:08
dhellmannwhat is "Exhaustive list of API calls not supported"? Is that calls into other projects that horizon doesn't use anywhere?20:08
ttx#info Gap coverage plan looks sane, will review for progress after milestones20:09
annegentledavid-lyle: sounds good to me, was going to suggest wiki20:09
david-lyledhellmann, the goal is find areas where Horizon doesn't match features exposed by the CLI20:09
david-lylethat is a common complaint against Horizon20:10
ttxAnything else on that topic ?20:10
dhellmannok, maybe consider rephrasing that gap in the way you just said it because it wasn't obvious what was meant by the current wording20:10
david-lylewe're hoping to fill those gaps, so users aren't forced to switch to CLI to accomplish certain tasks20:11
david-lyledhellmann: sure20:11
*** olaph has left #openstack-meeting20:11
markmcclaindavid-lyle: I'd also suggest maybe breaking out into subsets for each project20:11
dhellmannotherwise it all looks good20:11
ttxOK then, let's move on to next topic20:11
ttxdavid-lyle: many thanks!20:11
david-lylemarkmcclain: yes20:11
ttxzehicle_at_dell: around?20:11
*** baoli has quit IRC20:12
zehicle_at_dello/20:12
ttx#topic "TC direction" 0.5 scores refinement on Defcore scoring page20:12
*** openstack changes topic to ""TC direction" 0.5 scores refinement on Defcore scoring page (Meeting topic: tc)"20:12
*** nati_ueno has joined #openstack-meeting20:12
ttx#link https://wiki.openstack.org/w/images/e/e3/DefCore_Capabilities_Scoring.pdf20:12
*** hashar has quit IRC20:12
ttxSo we wanted to double-check the scoring on that page, especially the "TC direction" column and those 0.5 scores20:13
zehicle_at_dellDefCore meeting last week also wanted to get TC input on how to handle scoring going into the future20:13
ttxzehicle_at_dell: FWIW I formally contacted the PTLs to help on those unscored lines20:13
*** ssurana has joined #openstack-meeting20:13
zehicle_at_dellthat's likely a dedicated meeting topic20:13
*** chuckC has quit IRC20:13
zehicle_at_dellttx, thanks20:13
ttxzehicle_at_dell: yes20:13
zehicle_at_delllet me know how we can help.  I'll make myself available20:13
ttxI looked at the current scores in htat column and they make sense to me20:13
zehicle_at_dellWe're making a point of finding a good time for mikal at the next meeting20:13
ttxAnyone would like to suggest different scores for any of those ?20:13
*** UtahDave has left #openstack-meeting20:14
mikalzehicle_at_dell: I haven't gotten around to that yet, but I think I'll want to sit down with you to work through the nova ones some time in the next week20:14
mikalzehicle_at_dell: I will also reply to the meeting time email today20:14
zehicle_at_dellttx, was wondering how the TC wanted to collect feedback about scores that need discussion.  was thinking gerrit like process20:14
zehicle_at_dellbut happy to do it more interactive if that's the preference20:14
ttxzehicle_at_dell: trying to determine how much we need to tweak them20:15
*** radez is now known as radez_g0n320:15
annegentlezehicle_at_dell: I should know this, but how can I get a deeper description of a capability, such as compute-auth?20:15
*** dhellman_ has joined #openstack-meeting20:15
annegentlezehicle_at_dell: in tempest itself?20:15
zehicle_at_dellttx, we starting thinking ahead into the Icehouse & Juno reviews.  Assuming that we start from Havana and then need to discuss line by line20:15
markmcdefinitely would be good to have a way of tracking the discussion that went into any particular score20:15
*** baoli has joined #openstack-meeting20:16
markmcbut it is looking fairly reasonable to me20:16
zehicle_at_dell#link https://github.com/stackforge/refstack/tree/master/defcore/havana20:16
ttxI think we can do hte havana one interactively but yes, some more gerrit-driven approach would sclae better for future occurences20:16
zehicle_at_dellannegentle, we want to add more detail to the capability json file20:16
zehicle_at_dellttx, +1 on that.  would like to get a discussion about that on a future TC agenda then20:17
zehicle_at_dellhopefully, next releases are just deltas20:17
sdagueannegentle: the answer *should* be in tempest itself, however our docs aren't what they should be either.20:17
sdagueannegentle: so it would mostly involve reading code at this point20:17
zehicle_at_dellsdague, that's why we need to roll up into capabilities20:17
ttx#action ttx to schedlue discussion on future scoring process at a future TC meeting20:17
zehicle_at_delleven getting short descriptions into that capabilities.json would be a great step for users20:18
sdaguezehicle_at_dell: yep. We also talked a lot about new doc standards in tempest that would go a long way here20:18
ttxzehicle_at_dell: looks like the current scoring is good enough. That only leaves the unscored lines20:18
sdaguehonestly, random folks using tempest need this info too, so I'd love to get it baked back i nthere20:18
*** primeministerp has joined #openstack-meeting20:18
mordred++20:18
zehicle_at_dellsdague, +120:18
*** otherwiseguy has quit IRC20:19
ttxzehicle_at_dell: for the unscored lines you should try to extract data frmo PTLs first20:19
ttxzehicle_at_dell: we  can get involved if that process gets stuck, I guess20:19
zehicle_at_dellttx, yes.  was going that route.  was hoping to collaborate on it w/ TCs20:19
sdaguetotally happy to do it in a way that would make it easily / machine extractable for defcore20:19
ttxzehicle_at_dell: did any of the PTLs conact you yet ?20:19
markmczehicle_at_dell, mapping to tempest tests here: https://github.com/stackforge/refstack/blob/master/defcore/havana/capabilities.json20:19
zehicle_at_dellSwift20:19
markmcsorry, that was for annegentle20:19
zehicle_at_dellnotmyname, has been pretty engaged20:19
*** msdubov has quit IRC20:20
*** primeministerp has quit IRC20:20
ttxzehicle_at_dell: I suspect mikal will engage at the next meeting if he can make it20:20
zehicle_at_dell(which brings up the other topics we need help with - designated sections)  mikal is working with us on that20:20
ttxzehicle_at_dell: that leaves jgriffith20:20
*** primeministerp has joined #openstack-meeting20:20
mikalYes, mikal feels guilt about this and means to get to it ASAP20:20
zehicle_at_dellyes, jgriffith (thinking @notmyname twitter)20:20
zehicle_at_dellmikal, I'm working on a blog about designated sections.  Would be happy to co-author with you.  I'll send you a link20:21
*** boris-42 has quit IRC20:21
mikalzehicle_at_dell: cool, let's talk about it in email20:21
ttxzehicle_at_dell: looks like those 0.5 scores actually reflect reality after all20:21
*** boris-42 has joined #openstack-meeting20:21
annegentlethanks markmc zehicle_at_dell20:22
ttxzehicle_at_dell: anything more you need at this point ?20:22
*** msdubov has joined #openstack-meeting20:22
zehicle_at_delltimeframe?20:22
zehicle_at_dellI'd like everyone on board w/ timing20:22
zehicle_at_dellsince we'd like to have the advisory Havana list compelete for community review by 7/420:23
zehicle_at_dellso that we can have the board approve it at the OSCON meeting20:23
zehicle_at_dellthat means all the .5s, the missing sections and (ideally) designated code for the impacted projects20:23
*** reed has quit IRC20:23
jgriffithttx: zehicle_at_dell I can help with the Cinder sections, but had some q's for zehicle_at_dell20:24
ttxzehicle_at_dell: you mean we shouldn't leave any 0.5 ? I think they were acceptable scores ?20:24
jgriffithmaybe after the meeting?20:24
ttxjgriffith: yes20:24
zehicle_at_dellttx, we were trying to make it binary for now20:24
markmcttx, AIUI 0.5 == FIXME :)20:25
ttxzehicle_at_dell: ah! sorry, totally missed that.20:25
zehicle_at_dellwe were using .5 as a place holder for revuew needed.  yes20:25
*** afazekas has joined #openstack-meeting20:25
ttxHmm, then I think we'll have to come up with a formal proposal20:25
ttxand Gerrit it20:25
ttxany TC member up for drafting a binary proposal for the TC direction column ?20:25
zehicle_at_dellttx, we have the tests in gerrit now20:25
zehicle_at_dellI could add the scores to that json file and then let them go under review20:25
zehicle_at_dellthat's not a process, just the doc20:26
ttxI would do it if I weren't traveling all week20:26
zehicle_at_dellbut it would let you address individual scores per test/capability20:26
*** dims has joined #openstack-meeting20:26
ttxzehicle_at_dell: let's try to make a proper TC resolution on that20:26
mordredttx: I can do it20:27
ttxmordred: cool, thx20:27
zehicle_at_dell+120:27
*** jmontemayor has quit IRC20:27
ttx#action mordred to draft binary proposal for the "TC direction" column scores20:27
zehicle_at_dellhappy to have a smaller or 1x1 meeting about it.  we spent some time in DefCore talking about exactly that20:28
mordredttx: for completeness, I think it should be the whole column, yeah?20:28
ttxzehicle_at_dell: then for the missing lines, if you don't get what you need frmo PTLs we can escalate to TC mid-June so that you're still on time for OSCON20:28
ttxmordred: indeed20:28
zehicle_at_dellthanks.  yes20:28
ttxAnything more on that topic ?20:28
dhellman_are we assuming that once they are defined in https://github.com/stackforge/refstack/blob/master/defcore/havana/capabilities.json a given capability's definition won't change?20:29
zehicle_at_dellmordred, yes.  since any change to the row can impact the whole score.  it's a single unit for review20:29
zehicle_at_delldhellman_, release by release they will likely change20:29
*** ewindisch has joined #openstack-meeting20:29
*** pdmars has quit IRC20:29
zehicle_at_dellsmall source of confusion > we're using capabilities as proxies for the tests right now.  in next releases, we really should consider the tests20:29
zehicle_at_dellbecause a capability _may_ have some that are not required yet20:30
zehicle_at_dellit was just too much work to do it from the bottom up20:30
zehicle_at_dellso capabilities were a good compromise20:30
dhellman_sure20:30
dhellman_I'm just trying to reconcile the idea the the TC is going to vote on a definition of "compute-volume" and that definition will be changing later in a repo where we don't get a re-vote20:31
sdaguezehicle_at_dell: so in an ideal world, is there a capability level grouping in tempest that we are missing? I sort of thought the capabilities here mapped to tempest directories, but now I'm not quite so sure20:31
zehicle_at_dellsdague, yes.  Ideally, it would be managed there20:31
*** tvoran has quit IRC20:31
sdaguezehicle_at_dell: ok, so if there is feedback on restructures to make that clearer in the tempest, that would be appreciated. I think that team would be receptive to it.20:32
zehicle_at_dellmainly we did not expect DefCore to take long term ownership of that.  it was needed to move forward this cycle20:32
ttxdhellman_: we get to revote at each release actually20:32
sdaguezehicle_at_dell: yep, all good. Just want to use the feedback to make things better for everyone.20:32
zehicle_at_dellI think users would appreciate a consistent capabilities set even if we change some of the tests inside them20:32
dhellman_ttx: ok20:33
*** edmondsw has left #openstack-meeting20:33
*** jmontemayor has joined #openstack-meeting20:33
zehicle_at_dell+100020:33
ttxok, I think we can move on20:33
sdaguezehicle_at_dell: agreed. And I think it's a good way of "consuming" the information out of tempest, which has become pretty vast20:33
zehicle_at_dell+120:33
zehicle_at_dellsdague, I'm working on specs for refstack to help w/ visualization20:33
*** IlyaE has quit IRC20:34
sdaguezehicle_at_dell: great20:34
ttx#topic K release naming20:34
*** openstack changes topic to "K release naming (Meeting topic: tc)"20:34
ttxWe need to come up with a short list of 3-5 names to submit to a public poll (after trademark checks)20:34
*** IlyaE has joined #openstack-meeting20:34
ttxLast time we used a Condorcet TC members poll to select that short list out of a larger pool of candidates20:34
ttxThe candidate names (following the naming rules) are up at:20:34
ttx#link https://wiki.openstack.org/wiki/ReleaseNaming20:34
ttxWhich ones from this list would you like to see on the Condorcet for the short list?20:34
mikalCan we have another mutiny over names?20:34
anteayakepler20:34
ttxmikal: NO20:34
sdagueso after talking with mikal, I'd like to apply for a grizzly class exception :)20:35
mikalI'd like to see Kilo / Kilogramme added to that list20:35
markmcclainwhy do I get the suspicion that kyoto will win?20:35
ttxPersonally I'd pick Kepler, Kleber, Kossuth, Kourou, Kyoto20:35
mikalIts in Paris, and its a cool name20:35
zanebmikal: ++ :)20:35
dhellman_yeah, we should definitely not put names commonly associated with other places on the list20:35
devanandakerity, klang, or kepler -- if we stick to that list20:35
*** pberis has quit IRC20:35
jeblairdevananda: the "havana" boat already sailed ;)20:35
ttxmikal: Kilo doesn't mean anything and Kilogramme is WAYY too long. Furthermore, we don't need an exception :)20:35
mikalBut its out big chance to make fun of those non-metric people20:36
ttxAnd Kepler is an awesome dude, too20:36
anteaya++20:36
jeblair++kepler20:36
* dhellman_ will be voting for Klébér because he wants unicode characters in all the package names20:36
ttxFurthermore the refeence kilogram is NOT EVEN in Paris20:36
anteayakindwiller isn't bad20:37
jeblairttx: !!?20:37
ttxIt's in Sevres. Not Paris. Close. But not Paris.20:37
*** vkmc has joined #openstack-meeting20:37
*** vkmc has quit IRC20:37
*** vkmc has joined #openstack-meeting20:37
mordred++kepler20:38
devanandattx: and Juno is not in Atlanta20:38
anteayawe need a few choices20:38
mikalThe IPK and its six sister copies are stored at the International Bureau of Weights and Measures (known by its French-language initials BIPM) in an environmentally monitored safe in the lower vault located in the basement of the BIPM’s Pavillon de Breteuil in Sèvres on the outskirts of Paris.20:38
mikalIts in a vault in Paris20:38
mikalWhch is awesome20:38
*** rm_work|away is now known as rm_work20:38
ttxkey word is "outskirts" :)20:38
mordredrule is state - not city20:38
mgagnemordred: I'm sad, I can't find a place named Kraken in France20:38
mikalSigh. Dude.20:38
anteayakeryado20:39
mikalNone of us know the edge of Paris20:39
mikalIts just a big blob of Frenchyness to us20:39
markmcttx is right, though - 'kilo' is not 'kilogram'20:39
markmckepler it is20:39
ttxmikal: I object to that20:39
*** trey_h_ has quit IRC20:39
*** pberis has joined #openstack-meeting20:39
ttx#info names to include i poll20:39
ttx#info Kepler, Kleber, Kossuth, Kourou, Kyoto20:39
mikalkepler is a good name though20:39
ttx#info kerity, klang20:39
*** jbjohnso has quit IRC20:39
anteayakeryado?20:39
markmckeller ?20:40
anteayaI don't think that is hard to figure out how to pronounce20:40
markmcclainwhy not KILLEM? :)20:40
ttxkillem is pretty neat20:40
anteayano no no20:40
mikalIs it too late to argue to Koala?20:40
* mikal is mostly trolling20:40
jeblairi would like to see kilo on the list, though i would probably vote for kepler over it20:40
ttxmikal: stick to the rules!20:40
*** otherwiseguy has joined #openstack-meeting20:41
ttxanteaya: is keryado a french city?20:41
anteayait is on the list20:41
ttx#info keryado20:41
*** jtomasek has joined #openstack-meeting20:41
ttxmarkmcclain: want killem on the short list condorcet poll ?20:41
ttx#info keller20:41
markmchttp://en.wikipedia.org/wiki/Helen_Keller20:42
jaypipeskepler ftw20:42
zanebinteresting that almost all the city names beginning with a K are German...20:42
markmcclainttx:  sure20:42
wendarthat struck me as odd too, history of conquest, I suppose20:42
ttxzaneb: yes, Alsacian region20:42
ttxthe other half are Brittany20:42
ttxKer* stuff20:43
ttxKer meaning village there20:43
zanebah, interesting20:43
anteayaif killem makes the list I want kindwiller20:43
ttxanyway, I'll set up the condorcet poll so that TC members can pick a short list of 520:43
zanebI assume K is not a popular letter at the beginning of a word in French20:43
ttx#info kindwiller20:43
ttxyou assume correctly20:44
ttxthen we'll submit the list for cursory trademark checks20:44
*** jprovazn has quit IRC20:44
ttxand the resulting list of 3-4 will be pushed on a public poll20:44
ttx#action ttx to set up the condorcet poll for TC members to pick the short list20:45
zanebI like the sound of Kirchberg. reminds me of Bavaria :)20:45
ttx#topic Requirements changes20:46
*** openstack changes topic to "Requirements changes (Meeting topic: tc)"20:46
ttx* Add Ceilometer requirements (https://review.openstack.org/85978)20:46
*** zhiyan_ is now known as zhiyan20:47
ttxI'm tempted to abandon this one20:47
ttxthis it doesn't get enough attention from proposer and clogs the meeting every week20:47
sdagueon the ceilometer bit, I'd kind of like to pull out that + heat + horizon statements and do a more general "integrated projects should integrate with other projects"20:47
sdaguein a more general way20:47
*** jecarey has quit IRC20:48
ttxsdague: sounds like a good proposal that would make that one obsolete20:48
sdaguewhich I'm happy to propose if there is some agreement on that direction20:48
sdagueok, will take as a todo20:48
ttxsdague: that said, I think that's where we started from20:48
ttxand then people got more specific20:48
sdagueyeh, let me take a whack at language changes and see if people like it20:49
devanandai also remember there being concern at leaving it too generic20:49
zanebsdague: +1 but example don't hurt either20:49
dhellman_we did, because we wanted to list the expected ways that integration should happen, at a high level20:49
ttxright, so I remember correctly20:49
sdagueI think general with examples works well. Before it was just general, with no examples20:49
*** gduan has quit IRC20:49
*** jcallawa has quit IRC20:49
devanandagive some direction so that future TCs don't miss necessary items in their pre-graduation gap analysis20:49
sdaguethat's how I was redoing the upgrade language20:49
*** garyduan has joined #openstack-meeting20:49
dhellman_the problem with general is it doesn't provide a checklist for reviewing integration proposals; we need the checklist *somewhere*20:50
markmcclain+1 to checklist20:50
devanandadhellman_: ++20:50
*** lcheng_ has quit IRC20:50
devanandaperhaps we should actually just checklist against /all/ projects20:50
*** hashar has joined #openstack-meeting20:50
sdaguedhellman_: honestly, checklists for graduation requirements are overrated I think20:50
sdaguebecause there is *so* much context behind these20:50
*** jdob has quit IRC20:50
*** zdiN0bot has quit IRC20:50
sdagueand we've seen substantial confusion on the lists so far20:50
*** marcoemorais has quit IRC20:51
devanandawhich is, itself, a general statement20:51
ttx#action ttx to talk to jd__ about his proposal and threaten to abandon it if it doesn't get more love20:51
ttx* add upgrade expectations (https://review.openstack.org/87234)20:51
*** marcoemorais has joined #openstack-meeting20:51
annegentleI'm all for talking to future TCs20:51
*** jseutter has left #openstack-meeting20:51
ttxI think the latest version of that one should be good to go, just missing fresh votes20:52
sdaguemuch appreciation to devananda and eglynn-afk for catching all my typos20:52
dhellman_ttx, I'm rebasing it now20:52
ttxwill approve when it gets 7 YES20:52
*** gokrokve_ has quit IRC20:52
*** gduan has joined #openstack-meeting20:52
ttx#topic Minor governance changes20:52
*** openstack changes topic to "Minor governance changes (Meeting topic: tc)"20:52
jeblairsdague: er20:53
dhellman_https://review.openstack.org/#/c/85978/320:53
ttx* Add project mission statement for Ceilometer (https://review.openstack.org/87526)20:53
jeblairsdague: This requirement becomes relevant after the first stable release that199 a project ships in20:53
*** eglynn-afk is now known as eglynn20:53
jeblairsdague: so it's not really a graduation requirement, it's a post-graduation requirement?20:53
sdaguejeblair: correct20:53
ttxOne more approval and this one is good to go20:53
sdaguejeblair: it's in the First Integrated Cycle Expections section20:53
jeblairsdague: is there any aspect of that we would want to consider before the graduation vote?20:54
ttxThe other 3 are housecleaning, and will be approved unless someone screams really soon:20:54
ttx* removed openstack/database-api from programs (https://review.openstack.org/95416)20:54
ttx* Add infra-specs to infra program (https://review.openstack.org/94896)20:54
ttx* add oslo-specs to oslo program (https://review.openstack.org/95226)20:54
*** pberis has quit IRC20:54
ttx#topic Open discussion20:54
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:54
*** garyduan has quit IRC20:54
sdaguejeblair: I'd love to nudge projects there, which is the reason for this language20:54
sdague"19820:54
sdagueThis requirement becomes relevant after the first stable release that19920:54
sdaguea project ships in, however projects are encouraged to incorporate a20020:54
sdagueculture of upgradability early in their project lifecycle."20:54
ttxsdague: so maybe we can expand on that question of specific vs. general guidelines20:55
jeblairsdague: yeah, i think that's really clear.  ++20:55
sdaguettx: on open discussion, yay for designate incubation proposal!20:56
*** zhiyan is now known as zhiyan_20:56
sdaguehappy to be discussing that next week20:56
jeblairyaaaay!20:56
markmcclainfinally glad it's back20:56
ttxsdague: are they up to snuff on the QA side ? Haven't looked at it yet20:56
mikalI have some concerns with designate, but I've mentioned them to the team20:56
sdaguettx: haven't yet, will do this week20:57
*** caleb_ has quit IRC20:57
mikalFor example, they have an API rewrite planned20:57
devanandai continue to have some concerns about ceilometer's scope, but that seems to be overridden by the majority, and i think we've got good progress on the mission statement.20:58
devanandaawaiting feedback from eglynn on my last suggestion20:58
*** markwash has joined #openstack-meeting20:58
*** pberis has joined #openstack-meeting20:59
eglynndevananda: just looking at that, I'd be happy to resubmit with those suggested changes20:59
* ttx looks up devananda's concerns20:59
jeblairfwiw i also think the 'avoid examples in mission statement' is a good point20:59
dhellman_eglynn: if you're going to make more changes, that "reliably" bit seems redundant (we want all of the openstack projects to be reliable, don't we?)21:00
eglynndhellman_: reliably was inserted early in response to feedback21:00
eglynn(from jogo IIRC)21:00
devanandattx: gathering billing data vs gathering performance data vs gathering performance data of the tenant's application (eg, for Heat scaling)21:00
ttxok, time is up. Looks like that ceilo mission statement could use one more patchset21:00
devanandattx: three separate things IMO21:00
ttxdevananda: feel free to -1 it to block it :)21:01
*** hashar has quit IRC21:01
*** huats has quit IRC21:01
dhellman_devananda: gathering similar data for multiple purposes21:01
eglynnok, one more roundtrip to the well :)21:01
*** julim has quit IRC21:01
ttx#endmeeting21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue May 27 21:01:20 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-05-27-20.03.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-05-27-20.03.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2014/tc.2014-05-27-20.03.log.html21:01
*** alexpilotti has joined #openstack-meeting21:01
*** huats has joined #openstack-meeting21:01
ttxdhellmann, dolphm, notmyname, eglynn, markwash, jgriffith, mikal, zaneb, david-lyle, kmestery, SlickNik, SergeyLukjanov: around ?21:01
notmynamehere21:01
zanebo/21:01
devanandaproblem is the code already does the things I object to... so the mission statement is (converging on) an accurate statement of what the prjoect does21:01
dhellman_o/21:01
mesteryo/21:01
eglynno/21:01
dolphmo/21:01
markwasho/21:01
david-lyleo/21:01
*** gyee has joined #openstack-meeting21:02
ttxdevananda: we can adjust the mission statement if the project gets "fixed"21:02
ttx#startmeeting project21:02
openstackMeeting started Tue May 27 21:02:15 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
*** jecarey has joined #openstack-meeting21:02
openstackThe meeting name has been set to 'project'21:02
ttxVery short agenda today...21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttx#topic News from the 1:1 sync points21:02
*** openstack changes topic to "News from the 1:1 sync points (Meeting topic: project)"21:02
*** beagles has quit IRC21:02
jeblairand i'm totally not bringing anything up here today21:02
*** Penick has quit IRC21:02
mesteryjeblair: :P21:03
*** Leon has joined #openstack-meeting21:03
*** b3nt_pin has joined #openstack-meeting21:03
ttxCombined log of the 1:1s sync from today:21:03
ttxhttp://eavesdrop.openstack.org/meetings/ptl_sync/2014/ptl_sync.2014-05-27-13.13.html21:03
*** Leon is now known as Guest9660021:03
ttxWas a bit chaotic since I was traveling today21:03
*** hashar has joined #openstack-meeting21:03
ttx#topic Other program news21:03
*** openstack changes topic to "Other program news (Meeting topic: project)"21:03
ttxIt was suggested that programs without an integrated project shall also have space to proclaim their news21:04
notmynamettx: swift feature freeze during the storage policies merge will most likely start tomorrow21:04
ttx#info swift feature freeze during the storage policies merge will most likely start tomorrow21:04
notmynamethanks :-)21:04
*** ArxCruz has quit IRC21:04
ttxWould a standing item at the beginning of this meeting work ?21:04
ttxjeblair: ^21:04
ttxannegentle: ^21:04
ttxmtreinish: ^21:04
mtreinishttx: yeah that's fine for me21:04
*** Penick has joined #openstack-meeting21:04
jgriffitho/21:04
jeblairttx: that's fine, but i sort of figure we can add things to the agenda21:05
ttxjeblair: you should feel free to edit that wikipage21:06
dolphmttx: could also be a special open-ish timeslot in #openstack-relmgr-office so it's archived as part of the other "news"21:06
*** pberis has quit IRC21:06
ttxdolphm: hmm, we could do that too21:06
*** Leonr has quit IRC21:06
ttxif I find a time where they could all join if they want stuff included21:06
*** SlickNik has joined #openstack-meeting21:06
ttxjeblair, mtreinish: would you prefer that ?21:06
SlickNiko/21:07
dolphmhow long before this meeting is the last 1:1?21:07
SlickNiksorry running a bit late on meetings.21:07
*** chuckC has joined #openstack-meeting21:07
*** eharney has quit IRC21:07
*** Guest96600 has quit IRC21:07
jeblairttx: that seems weird to me...21:07
* SergeyLukjanov lurking21:07
*** gyee has quit IRC21:07
jeblairttx: i mean, the 1:1s are for you to coordinate with ptls on detailed deliverable times/progress/etc21:08
mtreinishttx: I'll defer to you and jeblair I don't have an opinion on this :)21:08
jeblairi don't really have that need21:08
ttxjeblair: right21:08
*** nati_ueno has quit IRC21:08
ttxI think hte idea is that you could get stuff in the ptl_sync summary21:08
*** markvan_ has quit IRC21:08
ttxbut then probably better to #info your stuff during the meeting directly21:08
ttxok, let's try a standing item at start of meeting21:09
annegentlesorry for the delay, yes, that's fine21:09
ttxand we'll revisit if tha tdoesn't work21:09
ttx#topic Open discussion21:09
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:09
eglynnquick question about juno-1 ...21:09
ttxThat's actually all we had on the agenda21:09
ttxeglynn: shoot21:09
eglynndoes the new fasttrack tag-driven milestone release process buy us an extra couple of days dev time?21:10
*** henrynash has quit IRC21:10
eglynni.e. instead of calling time for landing patches by EoD Monday21:10
eglynn... that gets pushed out to say EoD Wednesday of the milestone week?21:10
ttxeglynn: the idea is that you can call the tag anytime between Tuesday and Thursday21:10
*** markvan has joined #openstack-meeting21:10
eglynnttx: cool21:10
ttxso yes, that can buy you a couple of days if needed21:10
ttxI epect that will mostly be useful for Feature Freeze21:11
ttxsince j1 and j2 don't matter that much21:11
*** nati_ueno has joined #openstack-meeting21:11
eglynnyeah, for j-1 especially21:11
eglynncool, got it21:11
*** markmc has quit IRC21:11
dolphmttx: does it have to be the latest hash?21:11
*** jtomasek has quit IRC21:12
dolphmi guess it doesn't matter too much, nevermind!21:12
*** aysyd has quit IRC21:12
ttxdolphm: not really21:12
*** dims has quit IRC21:13
*** lcheng_ has joined #openstack-meeting21:13
ttxAnything else, anyone ?21:13
*** ivasev has quit IRC21:14
ttxwell then21:14
ttx#endmeeting21:14
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:14
openstackMeeting ended Tue May 27 21:14:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2014/project.2014-05-27-21.02.html21:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2014/project.2014-05-27-21.02.txt21:15
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2014/project.2014-05-27-21.02.log.html21:15
SlickNikThanks ttx!21:15
*** dkliban is now known as dkliban_afk21:15
*** eglynn has quit IRC21:15
ttxcheers!21:15
mesterythanks ttx!21:15
*** tnurlygayanov_ has quit IRC21:15
*** rockyg has quit IRC21:15
*** whenry has quit IRC21:16
*** markwash_ has joined #openstack-meeting21:16
*** Mandell has quit IRC21:17
*** markwash has quit IRC21:17
dolphmgood meeting :)21:17
*** ArthurBerezin has joined #openstack-meeting21:17
*** SlickNik has left #openstack-meeting21:17
*** Ajaeger has left #openstack-meeting21:18
*** gyee has joined #openstack-meeting21:18
*** vpanizo has joined #openstack-meeting21:18
*** tsekiyama has joined #openstack-meeting21:18
*** vpanizo has quit IRC21:19
*** dhellman_ has quit IRC21:19
*** bgorski has joined #openstack-meeting21:19
*** markwash_ has quit IRC21:21
*** markmcclain has quit IRC21:21
*** markwash has joined #openstack-meeting21:21
*** Realmy_ is now known as Realmy21:23
*** markwash has quit IRC21:23
*** prad_ has quit IRC21:26
*** rakhmerov has joined #openstack-meeting21:26
*** whenry has joined #openstack-meeting21:28
*** mrda_away is now known as mrda21:28
*** Mandell has joined #openstack-meeting21:29
*** asalkeld has joined #openstack-meeting21:31
*** rakhmerov has quit IRC21:31
*** ArthurBerezin has left #openstack-meeting21:31
-openstackstatus- NOTICE: Zuul is offline due to an operational issue; ETA 2200 UTC.21:33
*** ChanServ changes topic to "Zuul is offline due to an operational issue; ETA 2200 UTC."21:33
*** jesusaurus has joined #openstack-meeting21:33
*** Leonr has joined #openstack-meeting21:33
*** eharney has joined #openstack-meeting21:34
*** Leonr has quit IRC21:34
*** Leonr has joined #openstack-meeting21:35
*** nati_ueno has quit IRC21:37
*** thangp has quit IRC21:37
*** caleb_ has joined #openstack-meeting21:38
*** Penick has quit IRC21:38
*** davidlenwell_ has joined #openstack-meeting21:40
*** noslzzp has quit IRC21:41
*** vuil has joined #openstack-meeting21:42
*** Edward-Zhang has joined #openstack-meeting21:42
*** caleb_ has quit IRC21:42
*** IlyaE has quit IRC21:43
*** nati_ueno has joined #openstack-meeting21:43
*** marcoemorais has quit IRC21:43
*** SumitNaiksatam has quit IRC21:43
*** davidlenwell_ has quit IRC21:44
*** marcoemorais has joined #openstack-meeting21:44
*** caleb_ has joined #openstack-meeting21:44
*** baoli has quit IRC21:44
*** marcoemorais has quit IRC21:45
*** marcoemorais has joined #openstack-meeting21:45
*** SumitNaiksatam has joined #openstack-meeting21:45
*** davidlenwell has quit IRC21:45
*** dims has joined #openstack-meeting21:45
*** davidlenwell has joined #openstack-meeting21:47
*** zhiyan_ is now known as zhiyan21:48
*** mwagner_lap has quit IRC21:52
*** emaganap has quit IRC21:54
*** emagana has joined #openstack-meeting21:55
*** harlowja_ is now known as harlowja_away21:57
*** zhiyan is now known as zhiyan_21:57
*** harlowja_away is now known as harlowja_21:57
*** edmund has quit IRC21:57
*** vpanizo has joined #openstack-meeting22:01
*** caleb_ has quit IRC22:02
*** caleb_ has joined #openstack-meeting22:03
*** shakamunyi has quit IRC22:03
*** hashar has quit IRC22:04
*** nati_ueno has quit IRC22:05
*** vijendar has quit IRC22:05
*** otherwiseguy has quit IRC22:06
*** yamahata has joined #openstack-meeting22:07
*** ildikov has joined #openstack-meeting22:08
*** thedodd has quit IRC22:08
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:10
-openstackstatus- NOTICE: Zuul is started and processing changes that were in the queue when it was stopped. Changes uploaded or approved since then will need to be re-approved or rechecked.22:10
*** shakamunyi has joined #openstack-meeting22:10
*** asalkeld has left #openstack-meeting22:10
*** victor13 has joined #openstack-meeting22:15
*** victor13 has quit IRC22:15
*** tomoe_ has joined #openstack-meeting22:16
*** baoli has joined #openstack-meeting22:18
*** SumitNaiksatam has quit IRC22:19
*** neelashah has quit IRC22:20
*** jmontemayor has quit IRC22:22
*** SumitNaiksatam has joined #openstack-meeting22:23
*** ddieterly has quit IRC22:23
*** noslzzp has joined #openstack-meeting22:25
*** jgrimm has quit IRC22:27
*** rakhmerov has joined #openstack-meeting22:27
*** stevemar has quit IRC22:29
*** henrynash has joined #openstack-meeting22:30
*** emagana has quit IRC22:30
*** ssurana1 has joined #openstack-meeting22:31
*** rakhmerov has quit IRC22:31
*** nati_ueno has joined #openstack-meeting22:32
*** ssurana has quit IRC22:32
*** caleb_ has quit IRC22:34
*** kgriffs is now known as kgriffs|afk22:35
*** marcoemorais has quit IRC22:38
*** marcoemorais has joined #openstack-meeting22:38
*** Sukhdev has joined #openstack-meeting22:38
*** marcoemorais has quit IRC22:38
*** marcoemorais has joined #openstack-meeting22:39
*** nati_uen_ has joined #openstack-meeting22:42
*** nati_ueno has quit IRC22:42
*** Penick has joined #openstack-meeting22:43
*** fnaval has quit IRC22:45
*** zaneb has quit IRC22:45
*** sushils has quit IRC22:46
*** changbl has quit IRC22:47
*** zhiyan_ is now known as zhiyan22:48
*** zaneb has joined #openstack-meeting22:49
*** derekh_ has quit IRC22:51
*** dstanek is now known as dstanek_zzz22:52
*** atiwari has quit IRC22:54
*** trey_h has joined #openstack-meeting22:56
*** Realmy has quit IRC22:57
*** zdiN0bot has joined #openstack-meeting22:57
*** zhiyan is now known as zhiyan_22:58
*** andreaf has quit IRC22:59
*** zdiN0bot has quit IRC23:00
*** zdiN0bot has joined #openstack-meeting23:00
*** baoli has quit IRC23:06
*** mwagner_lap has joined #openstack-meeting23:08
*** brucer has joined #openstack-meeting23:08
*** henrynash has quit IRC23:11
*** edmund has joined #openstack-meeting23:12
*** sanjay_sohoni has quit IRC23:14
*** jjmb has joined #openstack-meeting23:14
*** yamahata has quit IRC23:16
*** jjmb1 has joined #openstack-meeting23:16
*** trey_h has quit IRC23:16
*** jjmb has quit IRC23:19
*** SumitNaiksatam has quit IRC23:23
*** otherwiseguy has joined #openstack-meeting23:23
*** SumitNaiksatam has joined #openstack-meeting23:24
*** david-lyle has quit IRC23:25
*** jjmb1 has quit IRC23:26
*** rakhmerov has joined #openstack-meeting23:28
*** zdiN0bot has quit IRC23:28
*** noslzzp has quit IRC23:29
*** igordcard has quit IRC23:29
*** Penick has quit IRC23:30
*** rakhmerov has quit IRC23:32
*** davlaps has quit IRC23:33
*** dstanek_zzz is now known as dstanek23:33
*** devlaps has quit IRC23:33
*** ssurana1 has quit IRC23:34
*** jjmb has joined #openstack-meeting23:34
*** eharney has quit IRC23:35
*** TravT has quit IRC23:35
*** baoli has joined #openstack-meeting23:39
*** gokrokve has joined #openstack-meeting23:41
*** jjmb has quit IRC23:42
*** dstanek is now known as dstanek_zzz23:43
*** Mandell has quit IRC23:43
*** fbo has quit IRC23:44
*** keshava-hp has quit IRC23:44
*** ddieterly has joined #openstack-meeting23:49
*** eguz has joined #openstack-meeting23:51
*** carl_baldwin_ has quit IRC23:52
*** zdiN0bot has joined #openstack-meeting23:52
*** marcoemorais has quit IRC23:53
*** ddieterly has quit IRC23:53
*** henrynash has joined #openstack-meeting23:54
*** zdiN0bot1 has joined #openstack-meeting23:55
*** eghobo has quit IRC23:55
*** tsekiyam_ has joined #openstack-meeting23:55
*** baoli has quit IRC23:56
*** zdiN0bot has quit IRC23:57
*** lcheng_ has quit IRC23:58
*** henrynash has quit IRC23:59
*** tsekiyama has quit IRC23:59
*** zaneb has quit IRC23:59

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