Tuesday, 2013-12-10

*** ryanpetrello has quit IRC00:03
*** herndon has quit IRC00:03
*** HenryG has quit IRC00:04
*** HenryG has joined #openstack-meeting00:04
*** Leo_ has quit IRC00:06
*** sacharya has joined #openstack-meeting00:10
*** oubiwann-lambda has quit IRC00:12
*** yfujioka has joined #openstack-meeting00:15
*** fnaval has quit IRC00:16
*** jcooley_ has joined #openstack-meeting00:17
*** rakhmerov has quit IRC00:18
*** rnirmal has quit IRC00:19
*** Abosherpa has joined #openstack-meeting00:19
*** epim has joined #openstack-meeting00:20
*** sdake_ has joined #openstack-meeting00:21
*** Abosherpa has quit IRC00:25
*** tedross has joined #openstack-meeting00:26
*** colinmcnamara has joined #openstack-meeting00:27
*** colinmcn_ has joined #openstack-meeting00:27
*** novas0x2a|laptop has quit IRC00:29
*** IlyaE has quit IRC00:29
*** novas0x2a|laptop has joined #openstack-meeting00:29
*** gokrokve has quit IRC00:31
*** gokrokve has joined #openstack-meeting00:31
*** novas0x2a|laptop has joined #openstack-meeting00:31
*** rongze has quit IRC00:34
*** s0mik has quit IRC00:34
*** jdbarry has quit IRC00:37
*** EntropyWorks has quit IRC00:37
*** radix__ has joined #openstack-meeting00:38
*** ilyashakhat_ has joined #openstack-meeting00:38
*** ilyashakhat has quit IRC00:38
*** docaedo has quit IRC00:38
*** dripton has quit IRC00:38
*** _ozstacker_ has quit IRC00:38
*** docaedo has joined #openstack-meeting00:39
*** dripton has joined #openstack-meeting00:39
*** _ozstacker_ has joined #openstack-meeting00:39
*** yamahata_ has joined #openstack-meeting00:39
*** jdbarry has joined #openstack-meeting00:39
*** EntropyWorks has joined #openstack-meeting00:40
*** fifieldt has quit IRC00:40
*** aloga_ has joined #openstack-meeting00:41
*** lbragstad1 has joined #openstack-meeting00:41
*** herndon has joined #openstack-meeting00:41
*** scroiset_ has joined #openstack-meeting00:42
*** davidlenwell has joined #openstack-meeting00:42
*** dcramer_ has joined #openstack-meeting00:44
*** radix_ has quit IRC00:45
*** aloga has quit IRC00:45
*** scroiset has quit IRC00:46
*** aguzikova has quit IRC00:46
*** lbragstad has quit IRC00:46
*** kashyap has quit IRC00:46
*** ityaptin has quit IRC00:46
*** davidlenwell_ has quit IRC00:46
*** colinmcnamara has quit IRC00:46
*** colinmcn_ has quit IRC00:46
*** kashyap has joined #openstack-meeting00:47
*** spzala_ has joined #openstack-meeting00:47
*** jcooley_ has quit IRC00:47
*** ityaptin has joined #openstack-meeting00:48
*** smoser` has joined #openstack-meeting00:48
*** GheRiver1 has joined #openstack-meeting00:49
*** openstack has joined #openstack-meeting00:49
*** ChanServ sets mode: +o openstack00:49
*** SpamapS has joined #openstack-meeting00:50
*** jcooley_ has joined #openstack-meeting00:51
*** aguzikova has joined #openstack-meeting00:51
*** jcooley_ has quit IRC00:51
*** fifieldt has joined #openstack-meeting00:52
*** spzala has quit IRC00:57
*** toabctl has quit IRC00:57
*** changbl has quit IRC00:57
*** smoser has quit IRC00:57
*** hua has quit IRC00:57
*** GheRivero has quit IRC00:57
*** asalkeld has quit IRC00:57
*** ravikumar_hp has quit IRC00:57
*** asalkeld has joined #openstack-meeting00:57
*** hua has joined #openstack-meeting00:58
*** sushils has quit IRC00:59
*** tedross has quit IRC00:59
*** jorisroovers has quit IRC01:00
*** ravikumar_hp has joined #openstack-meeting01:01
*** changbl has joined #openstack-meeting01:02
*** IlyaE has joined #openstack-meeting01:03
*** colinmcnamara has joined #openstack-meeting01:05
*** colinmcn_ has joined #openstack-meeting01:05
*** SumitNaiksatam has quit IRC01:06
*** fifieldt has quit IRC01:07
*** hemna has quit IRC01:10
*** ItSAN____ has quit IRC01:15
*** rakhmerov has joined #openstack-meeting01:15
*** ItSANgo has joined #openstack-meeting01:15
*** Duane has joined #openstack-meeting01:16
*** IlyaE has quit IRC01:16
*** Duane has quit IRC01:16
*** rakhmerov has quit IRC01:18
*** epim has quit IRC01:18
*** colinmcn_ has quit IRC01:20
*** colinmcnamara has quit IRC01:20
*** adalbas has quit IRC01:22
*** cdub has quit IRC01:24
*** nermina has quit IRC01:25
*** mrodden has quit IRC01:26
*** smoser` is now known as smoser01:26
*** matiu has quit IRC01:27
*** nosnos has joined #openstack-meeting01:28
*** bill_az has quit IRC01:29
*** SumitNaiksatam has joined #openstack-meeting01:30
*** matiu has joined #openstack-meeting01:32
*** matiu has quit IRC01:32
*** matiu has joined #openstack-meeting01:32
*** Tross has joined #openstack-meeting01:33
*** Tross has left #openstack-meeting01:33
*** bdpayne has quit IRC01:34
*** Jianyong has joined #openstack-meeting01:35
*** thedodd has quit IRC01:37
*** ryanpetrello has joined #openstack-meeting01:42
*** mrodden has joined #openstack-meeting01:43
*** lblanchard has quit IRC01:50
*** wendar_ is now known as wendar01:50
*** rongze has joined #openstack-meeting01:51
*** yamahata_ has quit IRC01:51
*** rongze has quit IRC01:51
*** nermina has joined #openstack-meeting01:52
*** rongze has joined #openstack-meeting01:52
*** julim has quit IRC01:53
*** rongze is now known as 36DABWUXY01:53
*** rongze has joined #openstack-meeting01:53
*** rongze is now known as 45PAAS1G101:53
*** dkranz has joined #openstack-meeting01:54
*** julim has joined #openstack-meeting01:56
*** 45PAAS1G1 has quit IRC01:57
*** 36DABWUXY has quit IRC02:04
*** rongze has joined #openstack-meeting02:04
*** galstrom_zzz is now known as galstrom02:06
*** mrodden has quit IRC02:07
*** radix__ has quit IRC02:10
*** rwsu has quit IRC02:12
*** enikanorov__ has joined #openstack-meeting02:14
*** notmyname has quit IRC02:14
*** asalkeld is now known as angus_is_eating02:14
*** michchap_ has joined #openstack-meeting02:15
*** venkatesh has joined #openstack-meeting02:15
*** notmyname has joined #openstack-meeting02:15
*** al-maisan has quit IRC02:16
*** rakhmerov has joined #openstack-meeting02:16
*** enikanorov has quit IRC02:16
*** michchap has quit IRC02:17
*** al-maisan has joined #openstack-meeting02:17
*** mrodden has joined #openstack-meeting02:18
*** dkranz has quit IRC02:18
*** Mandell has quit IRC02:21
*** sarob has quit IRC02:22
*** sarob has joined #openstack-meeting02:22
*** oubiwan__ has joined #openstack-meeting02:22
*** sarob has quit IRC02:23
*** sarob has joined #openstack-meeting02:24
*** yaguang has joined #openstack-meeting02:25
*** zhikunliu has joined #openstack-meeting02:25
*** rwsu has joined #openstack-meeting02:26
*** yaguang has quit IRC02:29
*** sarob has quit IRC02:29
*** banix has joined #openstack-meeting02:32
*** marun has quit IRC02:32
*** marun has joined #openstack-meeting02:33
*** fungi has quit IRC02:34
*** dperaza has quit IRC02:34
*** rongze_ has joined #openstack-meeting02:35
*** rongze has quit IRC02:35
*** dperaza has joined #openstack-meeting02:35
*** weshay has quit IRC02:36
*** cdub has joined #openstack-meeting02:39
*** venkatesh has quit IRC02:42
*** toabctl has joined #openstack-meeting02:43
*** gongysh has joined #openstack-meeting02:47
*** jmontemayor has quit IRC02:47
*** paragan has joined #openstack-meeting02:48
*** epico has joined #openstack-meeting02:48
*** vkozhukalov has joined #openstack-meeting02:49
*** rakhmerov has quit IRC02:50
*** spzala_ has quit IRC02:50
*** samcdona has quit IRC02:51
*** samcdona has joined #openstack-meeting02:52
*** cdub has quit IRC02:52
*** venkatesh has joined #openstack-meeting02:54
*** ItSANgo has quit IRC02:55
*** ItSANgo has joined #openstack-meeting02:55
*** loq_mac has joined #openstack-meeting02:56
*** bgorski has quit IRC02:59
*** noslzzp has quit IRC03:00
*** masayukig has joined #openstack-meeting03:04
*** noslzzp has joined #openstack-meeting03:05
*** michchap has joined #openstack-meeting03:07
*** fnaval has joined #openstack-meeting03:07
*** rakhmerov has joined #openstack-meeting03:07
*** dcramer_ has quit IRC03:09
*** michchap_ has quit IRC03:09
*** angus_is_eating is now known as asalkeld03:14
*** novas0x2a|laptop has quit IRC03:17
*** slagle has quit IRC03:19
*** slagle has joined #openstack-meeting03:20
*** ctracey|away has quit IRC03:20
*** michchap_ has joined #openstack-meeting03:20
*** ctracey|away has joined #openstack-meeting03:20
*** yaguang has joined #openstack-meeting03:20
*** michchap has quit IRC03:23
*** fungi has joined #openstack-meeting03:24
*** fungi has quit IRC03:25
*** venkatesh has quit IRC03:25
*** lbragstad1 has quit IRC03:29
*** brucer_ has joined #openstack-meeting03:34
*** fungi has joined #openstack-meeting03:34
*** brucer has quit IRC03:35
*** yamahata_ has joined #openstack-meeting03:36
*** saschpe_ has joined #openstack-meeting03:37
*** jgrimm has quit IRC03:37
*** saschpe has quit IRC03:37
*** amotoki has joined #openstack-meeting03:39
*** gyee has quit IRC03:40
*** yamahata_ has quit IRC03:40
*** haomaiwang has joined #openstack-meeting03:40
*** banix has quit IRC03:41
*** vkmc has quit IRC03:41
*** chandankumar__ has quit IRC03:43
*** noslzzp has quit IRC03:49
*** ItSANgo has quit IRC03:50
*** ItSANgo has joined #openstack-meeting03:51
*** chandankumar has joined #openstack-meeting03:52
*** galstrom is now known as galstrom_zzz03:59
*** banix has joined #openstack-meeting04:05
*** herndon has quit IRC04:15
*** mrodden1 has joined #openstack-meeting04:16
*** brucer__ has joined #openstack-meeting04:16
*** mrodden has quit IRC04:16
*** ryanpetrello has quit IRC04:18
*** yamahata_ has joined #openstack-meeting04:19
*** dcramer_ has joined #openstack-meeting04:19
*** brucer_ has quit IRC04:19
*** ryanpetrello has joined #openstack-meeting04:22
*** ryanpetrello has quit IRC04:24
*** galstrom_zzz is now known as galstrom04:24
*** _ozstacker_ has quit IRC04:24
*** _ozstacker_ has joined #openstack-meeting04:24
*** stevemar has quit IRC04:37
*** ryanpetrello has joined #openstack-meeting04:37
*** SergeyLukjanov has joined #openstack-meeting04:38
*** elo1 has joined #openstack-meeting04:41
*** nati_ueno has quit IRC04:42
*** julim has quit IRC04:44
*** ryanpetrello has quit IRC04:48
*** elo1 has quit IRC04:50
*** boris-42 has joined #openstack-meeting04:50
*** fifieldt has joined #openstack-meeting04:50
*** yamahata_ has quit IRC04:50
*** banix has quit IRC04:51
*** ryanpetrello has joined #openstack-meeting04:54
*** galstrom is now known as galstrom_zzz04:55
*** colinmcnamara has joined #openstack-meeting05:02
*** colinmcn_ has joined #openstack-meeting05:02
*** fnaval has quit IRC05:02
*** fnaval has joined #openstack-meeting05:03
*** colinmcnamara has quit IRC05:08
*** colinmcn_ has quit IRC05:08
*** loq_mac has quit IRC05:08
*** dcramer_ has quit IRC05:11
*** yamahata_ has joined #openstack-meeting05:11
*** elo1 has joined #openstack-meeting05:13
*** banix has joined #openstack-meeting05:20
*** banix has quit IRC05:22
*** yamahata_ has quit IRC05:23
*** yamahata_ has joined #openstack-meeting05:23
*** banix has joined #openstack-meeting05:24
*** banix has quit IRC05:26
*** gokrokve has quit IRC05:34
*** rongze_ has quit IRC05:34
*** colinmcnamara has joined #openstack-meeting05:35
*** colinmcn_ has joined #openstack-meeting05:35
*** otherwiseguy has quit IRC05:36
*** akuznetsov has quit IRC05:41
*** rongze has joined #openstack-meeting05:44
*** oubiwan__ has quit IRC05:49
*** rongze has quit IRC05:50
*** rongze has joined #openstack-meeting05:59
*** NikitaKonovalov has joined #openstack-meeting05:59
*** michchap_ has quit IRC06:00
*** akuznetsov has joined #openstack-meeting06:04
*** masayukig has quit IRC06:06
*** markpeek has quit IRC06:07
*** jdurgin1 has quit IRC06:09
*** fifieldt has quit IRC06:10
*** SergeyLukjanov is now known as _SergeyLukjanov06:10
*** _SergeyLukjanov has quit IRC06:10
*** venkatesh has joined #openstack-meeting06:11
*** vkozhukalov has quit IRC06:12
*** jcoufal has joined #openstack-meeting06:13
*** GheRivero has joined #openstack-meeting06:13
*** GheRivero has quit IRC06:13
*** GheRiver1 has quit IRC06:14
*** GheRivero has joined #openstack-meeting06:14
*** GheRivero is now known as Ghe_HPDiscover06:15
*** colinmcnamara has quit IRC06:15
*** colinmcn_ has quit IRC06:15
*** cody-somerville has quit IRC06:21
*** jlibosva has joined #openstack-meeting06:31
*** sacharya has quit IRC06:32
*** jcooley_ has joined #openstack-meeting06:33
*** rongze has quit IRC06:35
*** rongze has joined #openstack-meeting06:38
*** mrunge has joined #openstack-meeting06:55
*** maxdml has quit IRC06:57
*** scott__ has quit IRC06:59
*** scottda has quit IRC06:59
*** radsy has quit IRC07:00
*** _ozstacker_ has quit IRC07:04
*** gokrokve has joined #openstack-meeting07:05
*** ozstacker has joined #openstack-meeting07:08
*** gokrokve has quit IRC07:10
*** denis_makogon has joined #openstack-meeting07:10
*** comay has quit IRC07:10
*** gongysh has quit IRC07:11
*** brucer__ has quit IRC07:11
*** scottda has joined #openstack-meeting07:14
*** scott__ has joined #openstack-meeting07:14
*** MaxV has joined #openstack-meeting07:18
*** doron_afk has joined #openstack-meeting07:19
*** gongysh has joined #openstack-meeting07:20
*** IlyaE has joined #openstack-meeting07:21
*** jhenner has quit IRC07:25
*** akuznetsov has quit IRC07:31
*** belmoreira has joined #openstack-meeting07:32
*** thomasbiege has joined #openstack-meeting07:33
*** samcdona has quit IRC07:37
*** boris-42 has quit IRC07:39
*** thomasbiege1 has joined #openstack-meeting07:46
*** ndipanov has quit IRC07:46
*** thomasbiege has quit IRC07:47
*** ndipanov has joined #openstack-meeting07:47
*** MaxV has quit IRC07:48
*** MaxV has joined #openstack-meeting07:48
*** ildikov has joined #openstack-meeting07:50
*** jtomasek has joined #openstack-meeting07:51
*** vkozhukalov has joined #openstack-meeting07:52
*** SergeyLukjanov has joined #openstack-meeting07:53
*** MaxV has quit IRC07:53
*** DinaBelova has joined #openstack-meeting07:54
*** nati_ueno has joined #openstack-meeting07:56
*** Tross has joined #openstack-meeting07:58
*** ndipanov has quit IRC07:58
*** rongze has quit IRC07:59
*** avishayb has joined #openstack-meeting08:02
*** ndipanov has joined #openstack-meeting08:02
*** rongze has joined #openstack-meeting08:05
*** gokrokve has joined #openstack-meeting08:05
*** yfujioka has quit IRC08:11
*** gokrokve has quit IRC08:11
*** brucer has joined #openstack-meeting08:14
*** colinmcnamara has joined #openstack-meeting08:18
*** colinmcnamara has quit IRC08:18
*** brucer has quit IRC08:21
*** thomasbiege1 has quit IRC08:21
*** akuznetsov has joined #openstack-meeting08:24
*** fbo_away is now known as fbo08:29
*** ihrachyska has quit IRC08:31
*** rossella_s has joined #openstack-meeting08:34
*** rossella_s has quit IRC08:39
*** MaxV has joined #openstack-meeting08:42
*** MaxV has quit IRC08:43
*** ygbo has joined #openstack-meeting08:43
*** MaxV has joined #openstack-meeting08:43
*** radix_ has joined #openstack-meeting08:44
*** jcooley_ has quit IRC08:45
*** ihrachyska has joined #openstack-meeting08:46
*** ndipanov has quit IRC08:47
*** flaper87|afk is now known as flaper8708:50
*** denis_makogon has quit IRC08:56
*** sdake_ has quit IRC08:58
*** yassine has joined #openstack-meeting08:59
*** ndipanov has joined #openstack-meeting09:00
*** gokrokve has joined #openstack-meeting09:05
*** venkatesh has quit IRC09:06
*** ihrachyska has quit IRC09:07
*** derekh has joined #openstack-meeting09:09
*** safchain has joined #openstack-meeting09:09
*** gokrokve has quit IRC09:09
*** DinaBelova has quit IRC09:10
*** rongze has quit IRC09:11
*** colinmcnamara has joined #openstack-meeting09:12
*** colinmcnamara has quit IRC09:12
*** rongze has joined #openstack-meeting09:15
*** ihrachyska has joined #openstack-meeting09:19
*** thomasbiege has joined #openstack-meeting09:22
*** IlyaE has quit IRC09:29
*** Fdot has joined #openstack-meeting09:30
*** thomasbiege has quit IRC09:31
*** SergeyLukjanov is now known as _SergeyLukjanov09:34
*** _SergeyLukjanov has quit IRC09:34
*** ArthurBerezin has joined #openstack-meeting09:35
*** ArthurBerezin has left #openstack-meeting09:38
*** thomasbiege has joined #openstack-meeting09:41
*** markmcclain has joined #openstack-meeting09:42
*** sushil_ has joined #openstack-meeting09:43
*** romcheg1 has joined #openstack-meeting09:43
*** romcheg1 has left #openstack-meeting09:43
*** DinaBelova has joined #openstack-meeting09:45
*** SergeyLukjanov has joined #openstack-meeting09:45
*** nermina has quit IRC09:45
*** nprivalova has joined #openstack-meeting09:55
*** jlibosva has quit IRC09:55
*** jlibosva has joined #openstack-meeting09:58
*** Guest23714 has joined #openstack-meeting09:59
*** chandankumar has quit IRC10:00
*** jcoufal has quit IRC10:03
*** gokrokve has joined #openstack-meeting10:05
*** chandankumar has joined #openstack-meeting10:07
*** zhikunliu has quit IRC10:07
*** gokrokve has quit IRC10:10
*** colinmcnamara has joined #openstack-meeting10:12
*** colinmcnamara has quit IRC10:12
*** jorisroovers has joined #openstack-meeting10:13
*** doron_afk is now known as doron10:20
*** avishayb has quit IRC10:24
*** gongysh has quit IRC10:24
*** yaguang has quit IRC10:25
*** Jianyong has quit IRC10:30
*** avishayb has joined #openstack-meeting10:30
*** markmcclain has quit IRC10:30
*** paragan has quit IRC10:30
*** jlibosva1 has joined #openstack-meeting10:31
*** jlibosva has quit IRC10:33
*** markmcclain has joined #openstack-meeting10:33
*** adalbas has joined #openstack-meeting10:35
*** epico has quit IRC10:38
*** doron is now known as doron_afk10:39
*** yamahata_ has quit IRC10:49
*** cyeoh has quit IRC10:50
*** avishayb has quit IRC10:51
*** rongze has quit IRC10:52
*** rongze has joined #openstack-meeting10:52
*** rongze has quit IRC10:55
*** thomasbiege has quit IRC10:59
*** Jianyong has joined #openstack-meeting11:00
*** Jianyong has left #openstack-meeting11:00
*** thomasbiege has joined #openstack-meeting11:01
*** boris-42 has joined #openstack-meeting11:05
*** gokrokve has joined #openstack-meeting11:05
*** markmcclain has quit IRC11:05
*** gokrokve has quit IRC11:09
*** jaimegil has joined #openstack-meeting11:11
*** jorisroovers has quit IRC11:14
*** Guest23714 has quit IRC11:16
*** rfolco has joined #openstack-meeting11:18
*** thomasbiege has quit IRC11:19
*** ildikov has quit IRC11:22
*** ildikov has joined #openstack-meeting11:22
*** mdenny has quit IRC11:23
*** ArthurBerezin has joined #openstack-meeting11:24
*** MaxV has quit IRC11:25
*** MaxV has joined #openstack-meeting11:26
*** markwash has quit IRC11:28
*** jhenner has joined #openstack-meeting11:28
*** jcooley_ has joined #openstack-meeting11:28
*** MaxV has quit IRC11:30
*** jcooley_ has quit IRC11:33
*** jcoufal has joined #openstack-meeting11:34
*** markwash has joined #openstack-meeting11:34
*** saurabh_ has joined #openstack-meeting11:38
*** saurabh_ has joined #openstack-meeting11:38
*** saurabh_ has left #openstack-meeting11:39
*** gduan has joined #openstack-meeting11:40
*** rongze has joined #openstack-meeting11:41
*** garyduan has quit IRC11:42
*** persia has quit IRC11:42
*** persia has joined #openstack-meeting11:42
*** persia is now known as Guest9977411:43
*** jorisroovers has joined #openstack-meeting11:46
*** ArxCruz has joined #openstack-meeting11:48
*** rongze has quit IRC11:51
*** amotoki has quit IRC11:53
*** Guest99774 has quit IRC11:55
*** Guest99774 has joined #openstack-meeting11:55
*** Guest99774 is now known as persia11:55
*** HenryG has quit IRC11:55
*** rongze has joined #openstack-meeting11:56
*** paragan has joined #openstack-meeting11:57
*** colinmcnamara has joined #openstack-meeting12:00
*** colinmcnamara has quit IRC12:00
*** colinmcn_ has joined #openstack-meeting12:00
*** colinmcn_ has quit IRC12:00
*** vkmc has joined #openstack-meeting12:02
*** ArthurBerezin has quit IRC12:05
*** gokrokve has joined #openstack-meeting12:05
*** gokrokve has quit IRC12:10
*** aloga_ has quit IRC12:13
*** ArthurBerezin has joined #openstack-meeting12:20
*** weshay has joined #openstack-meeting12:21
*** SergeyLukjanov is now known as _SergeyLukjanov12:21
*** _SergeyLukjanov has quit IRC12:21
*** MaxV has joined #openstack-meeting12:23
*** doron_afk is now known as doron12:23
*** MaxV has quit IRC12:27
*** cyeoh_ has joined #openstack-meeting12:27
*** MaxV has joined #openstack-meeting12:27
*** cyeoh_ is now known as cyeoh12:27
*** ArthurBerezin has left #openstack-meeting12:27
*** nosnos has quit IRC12:29
*** jcooley_ has joined #openstack-meeting12:29
*** thomasbiege has joined #openstack-meeting12:30
*** jcooley_ has quit IRC12:35
*** SergeyLukjanov has joined #openstack-meeting12:38
*** cyeoh has quit IRC12:38
*** simon-AS559 has joined #openstack-meeting12:44
*** boris-42 has quit IRC12:50
*** boris-42 has joined #openstack-meeting12:52
*** doron is now known as doron_afk12:52
*** thomasbiege has quit IRC12:55
*** mdurnosvistov has joined #openstack-meeting12:56
*** thomasbiege has joined #openstack-meeting12:56
*** MaxV has quit IRC12:58
*** MaxV has joined #openstack-meeting12:58
*** yassine_ has joined #openstack-meeting13:00
*** ildikov has quit IRC13:00
*** Jianyong has joined #openstack-meeting13:00
*** pdmars has joined #openstack-meeting13:01
*** nprivalova has quit IRC13:02
*** yassine has quit IRC13:02
*** MaxV has quit IRC13:03
*** nermina has joined #openstack-meeting13:04
*** eharney has joined #openstack-meeting13:04
*** jhenner has quit IRC13:04
*** sandywalsh_ has joined #openstack-meeting13:05
*** MaxV has joined #openstack-meeting13:05
*** gokrokve has joined #openstack-meeting13:05
*** ildikov has joined #openstack-meeting13:05
*** avishayb has joined #openstack-meeting13:06
*** jhenner has joined #openstack-meeting13:06
*** gokrokve has quit IRC13:10
*** nprivalova has joined #openstack-meeting13:12
*** zhikunliu has joined #openstack-meeting13:20
*** doron_afk is now known as doron13:20
*** oubiwan__ has joined #openstack-meeting13:22
*** salv-orlando has quit IRC13:23
*** thomasem has joined #openstack-meeting13:27
*** sandywalsh__ has joined #openstack-meeting13:29
*** HenryG has joined #openstack-meeting13:29
*** rongze_ has joined #openstack-meeting13:29
*** jcooley_ has joined #openstack-meeting13:31
*** sandywalsh_ has quit IRC13:32
*** rongze has quit IRC13:33
*** jcooley_ has quit IRC13:36
*** lblanchard has joined #openstack-meeting13:38
*** dims has quit IRC13:39
*** thomasbiege has quit IRC13:41
*** armax has joined #openstack-meeting13:41
*** dims has joined #openstack-meeting13:41
*** jdob has joined #openstack-meeting13:43
*** bauzas has joined #openstack-meeting13:44
*** oubiwan__ has quit IRC13:45
*** rongze_ has quit IRC13:48
*** lbragstad has joined #openstack-meeting13:49
*** dkranz has joined #openstack-meeting13:49
*** haomaiwang has quit IRC13:49
*** haomaiwang has joined #openstack-meeting13:50
*** dcramer_ has joined #openstack-meeting13:52
*** lbragstad has quit IRC13:54
*** ryanpetrello has quit IRC13:54
*** galstrom_zzz is now known as galstrom13:54
*** venkatesh has joined #openstack-meeting13:55
*** dcramer_ has quit IRC13:56
*** ttrifonov is now known as ttrifonov_zZzz13:56
*** DrBacchus has joined #openstack-meeting13:57
* annegentle waves13:59
annegentlewho's here for doc team meeting?13:59
*** doron is now known as doron_afk13:59
*** DrBacchus has quit IRC13:59
*** DrBacchus has joined #openstack-meeting14:00
*** dianefleming has joined #openstack-meeting14:00
annegentlehey dianefleming14:00
annegentleok, I'll go ahead and start14:00
*** yjiang5 has joined #openstack-meeting14:00
*** bauzas has left #openstack-meeting14:00
*** dprince has joined #openstack-meeting14:00
*** jcoufal has quit IRC14:00
dianeflemingsounds good and good morning everyone14:00
annegentle#startmeeting DocTeamMeeting14:01
openstackMeeting started Tue Dec 10 14:01:20 2013 UTC and is due to finish in 60 minutes.  The chair is annegentle. 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: DocTeamMeeting)"14:01
openstackThe meeting name has been set to 'docteammeeting'14:01
annegentleOk, the agenda is here:14:01
annegentle#link https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting14:01
*** jasondotstar has joined #openstack-meeting14:01
annegentlelooking for the Actions14:02
*** mrichman has joined #openstack-meeting14:02
annegentle#topic Action items from last meeting14:02
*** openstack changes topic to "Action items from last meeting (Meeting topic: DocTeamMeeting)"14:02
annegentleOk, this one is not done, but I have notes.14:02
annegentleAnne to write a blog post describing all the titles and their priorities (we'd want integrated projects to "plug in" are install, config, admin, ops; security and HA are secondary)14:02
*** dvarga has joined #openstack-meeting14:02
annegentleand14:02
annegentleAnne to follow up with HP Cloud's Spector for a podcast/screencast14:02
annegentlewhich is also not complete, but in the works14:02
annegentleThat's it for actions14:03
*** Sam-I-Am has joined #openstack-meeting14:03
annegentle#topic Monthly Google Hangout starting Jan 201414:04
*** openstack changes topic to "Monthly Google Hangout starting Jan 2014 (Meeting topic: DocTeamMeeting)"14:04
annegentlewelcome Sam-I-Am14:04
Sam-I-Ammorning14:04
annegentleWe had a great Hangout and I got good input that we want to continue those, so we'll start them up monthly in January14:04
annegentleGive input on your favorite days/times so we can all gather 'round and chat14:05
*** Tross has quit IRC14:05
annegentle#topic Operations Guide developmental edit14:05
*** openstack changes topic to "Operations Guide developmental edit (Meeting topic: DocTeamMeeting)"14:05
*** gokrokve has joined #openstack-meeting14:05
*** neelashah1 has joined #openstack-meeting14:06
*** jhenner has quit IRC14:06
annegentleAs most of you probably know, the Ops Guide is being edited by O'Reilly14:06
annegentleWe have our first set of comments, mostly high level, and next week we'll have annotaed PDFs of the first couple of chapters14:06
annegentleI can't spell annotated apparently14:06
*** Tross has joined #openstack-meeting14:06
*** yaguang has joined #openstack-meeting14:07
annegentlethen, by mid-January, we'll have edits of the entire book, and at the end of January we're doing a mini sprint in Boston with the original authors14:07
*** jdbarry has quit IRC14:07
*** neelashah has quit IRC14:07
*** suo has quit IRC14:07
*** pleia2 has quit IRC14:07
nerminanice14:07
annegentleI think Brian, the O'Reilly editor, can meet us those days since they're nearby14:07
*** sandywalsh_ has joined #openstack-meeting14:07
*** dkranz has quit IRC14:07
Sam-I-Amhow does one get involved in these things?14:08
chandankumarhello14:08
*** ttrifonov_zZzz is now known as ttrifonov14:08
*** mrichman has quit IRC14:08
*** sandywalsh__ has quit IRC14:08
*** markvan has quit IRC14:08
nerminamaybe a scheduler like tom used could be helpful for hangouts14:08
annegentleSome of the tasks: expand the preface to situate the Ops Guide in relation to the other guides, an intro chapter about OpenStack showing a high-level overview and emphasizing how components work together14:08
*** bdperkin has quit IRC14:09
annegentleSam-I-Am: good question. The original criteria for authors was having run OpenStack for at least six months in production as of last Feb.14:09
Sam-I-Amok, thats definitely not me :/14:09
*** pleia2 has joined #openstack-meeting14:09
*** dripton has quit IRC14:09
*** suo has joined #openstack-meeting14:09
*** dripton has joined #openstack-meeting14:09
*** zhikunliu has quit IRC14:09
annegentleSam-I-Am: yeah it's tough to turn away willing authors but it's experience that's needed14:09
*** gokrokve has quit IRC14:10
annegentleSam-I-Am: but, you could certainly review edits as they go in and comment, especially the overview, since you have fresh eyes14:10
*** jdob has quit IRC14:10
*** saschpe_ has quit IRC14:10
Sam-I-Amprobably14:10
annegentleAnother interesting comment we're working through is that the book contains tactics but not a lot of strategy14:10
*** eharney has quit IRC14:10
*** esheffield has quit IRC14:10
*** markvan has joined #openstack-meeting14:10
annegentleMy favorite is that it is quite "clean" heh14:10
annegentleSo we'll answer questions like, how does the cloud controller make your job easier? what do you need to be concerned about?14:11
annegentleany questions on that?14:11
*** Kharec has quit IRC14:11
*** saschpe has joined #openstack-meeting14:11
*** esheffield has joined #openstack-meeting14:11
Sam-I-Amhow can i take a look at it?14:11
chandankumarannegentle, That will be going to be great for us.14:11
*** martines has quit IRC14:12
*** ameade_ has quit IRC14:12
*** ameade has joined #openstack-meeting14:12
annegentleSam-I-Am: the book itself is at http://docs.openstack.org/ops14:12
*** Kharec has joined #openstack-meeting14:12
Sam-I-Amthanks14:12
*** martines has joined #openstack-meeting14:12
annegentlelet's see, what's next14:12
annegentle#topic Doc core can now set a patch to WIP14:12
*** openstack changes topic to "Doc core can now set a patch to WIP (Meeting topic: DocTeamMeeting)"14:12
*** nermina has quit IRC14:12
annegentleThis is just a public service reminder as a new part of our review process14:13
*** cloudon has joined #openstack-meeting14:13
*** litong has joined #openstack-meeting14:13
*** jd__ has quit IRC14:13
*** jd__ has joined #openstack-meeting14:13
*** weshay has quit IRC14:13
*** markwash has quit IRC14:13
annegentleAnyone up for updating the wiki with the new ability to set a patch as WIP?14:14
*** ryanpetrello has joined #openstack-meeting14:14
annegentleI think it goes in https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation14:14
*** doron_afk has quit IRC14:14
chandankumarannegentle, i will do that14:14
*** markwash has joined #openstack-meeting14:14
annegentlechandankumar: thanks!14:14
*** jamespage_ has joined #openstack-meeting14:14
annegentle#action chandankumar to update https://wiki.openstack.org/wiki/Documentation/HowTo#Reviewing_Documentation with note about WIP14:14
chandankumarannegentle, yw :)14:14
*** jdbarry has joined #openstack-meeting14:15
*** nermina has joined #openstack-meeting14:15
annegentle#topic Doc tools update - openstack-doc-tools repository14:15
*** openstack changes topic to "Doc tools update - openstack-doc-tools repository (Meeting topic: DocTeamMeeting)"14:15
annegentleAndreas has been working steadily at the new repo setup14:15
annegentleHere's a link to the review queue14:16
annegentle#link https://review.openstack.org/#/q/status:open+project:openstack/openstack-doc-tools,n,z14:16
*** bdperkin has joined #openstack-meeting14:16
annegentleHe's also working through the right way to get consistent gate checks on all the docs repos14:17
*** dianefleming has quit IRC14:17
*** jamespage_ has quit IRC14:17
*** dianefleming has joined #openstack-meeting14:17
*** troytoman is now known as troytoman-away14:17
annegentleThis move also helps with building translated documents14:17
*** cloudon has quit IRC14:17
annegentleany questions?14:17
*** galstrom is now known as galstrom_zzz14:18
annegentle#topic Doc Bug Day Dec 2014:18
*** openstack changes topic to "Doc Bug Day Dec 20 (Meeting topic: DocTeamMeeting)"14:18
chandankumari will review the doctools14:18
annegentleOk, this is going to be a fun day14:18
chandankumaryes14:18
annegentlechandankumar: thank you! Needs reviewers for sure14:18
annegentleMy team at Rackspace is going to help where they can14:18
Sam-I-Amsome of us need a walk-through for fixing bugs14:18
annegentleI've been triaging bugs in anticipation14:18
Sam-I-Amso i dont screw stuff up :)14:18
annegentleSam-I-Am: no worries about screwing up, it won't get through reviewers if it is screwy :)14:19
*** aloga has joined #openstack-meeting14:19
Sam-I-Amthere is that...14:19
annegentleSam-I-Am: my hope is to have triaged bugs so that there are ones anyone can pick up14:19
annegentleSam-I-Am: some of doc bug day will be triaging too, so if you know the answers, make a comment in the bug14:19
annegentleSam-I-Am: and hopefully fix a bunch, close some, consolidate14:19
annegentleSam-I-Am: I'd be happy to walk you through on IRC any time14:20
Sam-I-Ammost of mine are filed but there's plenty of things that could use rewording for streamlining/consolidating or major rewriting14:20
Sam-I-Ams/for/or14:20
Sam-I-Am<- early here14:20
Sam-I-Ami'll take you up on that offer14:21
annegentleSam-I-Am: heh. well, doc bug day is not for major rewriting, but it is a good chance to dig into books14:21
annegentleSam-I-Am: cool, I have notes from a workshop, I'll put them on the wiki14:21
Sam-I-Amthanks14:21
Sam-I-Amhopefully there's not much more to making neutron work in the ubuntu/redhat install guides14:22
annegentleIt's funny, that's the day before holiday break for some of us14:22
annegentleSam-I-Am: I am hoping you can sort through the comments and existing bugs and figure out the core issues14:22
annegentleSam-I-Am: that would be a good doc bug day task14:22
annegentlegoal14:22
annegentleSam-I-Am: I think it's close14:23
*** rongze has joined #openstack-meeting14:23
annegentleOk, that's all I had on the agenda14:23
*** AJaeger has joined #openstack-meeting14:23
Sam-I-Amok14:23
*** jdob has joined #openstack-meeting14:23
annegentle#topic Open Discussion14:23
*** openstack changes topic to "Open Discussion (Meeting topic: DocTeamMeeting)"14:23
annegentlewelcome AJaeger!14:23
AJaegerSorry for beeing late...14:23
AJaegerHi annegentle and Everybody else ;)14:23
nerminahi ajaeger, my savior14:24
*** oubiwan__ has joined #openstack-meeting14:24
AJaegernermina, you should be sleeping ;)14:24
nerminalol14:24
*** avishayb has quit IRC14:24
*** loq_mac has joined #openstack-meeting14:24
AJaegerdid you discuss the openstack-doc-tools repo?14:24
*** loq_mac has quit IRC14:24
annegentleAJaeger: yep, sure did!14:24
AJaegerah, then I'll read minutes lateron...14:25
*** eharney has joined #openstack-meeting14:25
*** noslzzp has joined #openstack-meeting14:25
annegentleAJaeger: http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2013-12-10.log14:25
annegentle:)14:25
*** weshay has joined #openstack-meeting14:25
chandankumaranderstj, can i github repo link of  openstack-doc-tools?14:25
*** jhenner has joined #openstack-meeting14:26
*** lbragstad has joined #openstack-meeting14:26
annegentleAJaeger: I think the devstack-checkout job is the way to go, for replication14:26
annegentleAJaeger: I'll write back on the list14:26
annegentlenermina: AJaeger sounds like you have a good plan for moving forward with the training guide?14:27
AJaegerannegentle, let's give it a try - if it works out, great, if not we adjust ;)14:27
annegentleAJaeger: yep, sounds just right14:27
*** loq_mac has joined #openstack-meeting14:27
*** avishayb has joined #openstack-meeting14:27
AJaegerregarding the training guide: Not sure how to handle the section/chapter problem in the best way...14:27
nerminaannegentle, sean's team on board and it might just work out14:28
*** julim has joined #openstack-meeting14:28
AJaegerUsing xpointer is one option - but an ugly hack IMO14:28
*** banix has joined #openstack-meeting14:28
nerminai'm meeting pranav sometime today14:28
*** jeckersb_gone is now known as jeckersb14:28
annegentleAJaeger: xpointer is probably the right way, but does make for more maintenance, what's another way to share content?14:28
AJaegerannegentle, creating one large chapter perhaps? No good idea yet - but I don't have much experience here14:30
*** neelashah1 has quit IRC14:30
*** sandywalsh__ has joined #openstack-meeting14:30
nerminai need to give it a fresh look, annegentle ajeager14:30
annegentleAJaeger: I thought about a chapter wrapper, but maybe that's what they're doing already14:30
annegentlenermina: is pranav the person Sean's handing off to?14:31
nerminayes, he's my goto guy14:31
annegentlenermina: ok, cool14:32
nerminahe said he knows how to fix the problem. i just haven't had the chance to connect in real time due to time zones.14:32
annegentlenermina: oh right, Aussie14:32
*** jcooley_ has joined #openstack-meeting14:32
loq_macwhere in australia?14:32
loq_maccan i help?14:32
nerminabut we'll find the time14:32
annegentleSpeaking of Aussies, I do want to make sure people know I don't expect people to attend a meeting that's so out of their time zone it would drive them batty :)14:32
annegentleTwo a month should hopefully be sufficient14:33
*** sandywalsh_ has quit IRC14:33
*** colinmcnamara has joined #openstack-meeting14:33
nerminaloq_mac, thanks, we're doing cross-pollination between training guides and cloud admin guide14:33
*** colinmcn_ has joined #openstack-meeting14:33
annegentleAlso, MirandaZhang starts her internship next week14:33
annegentleShe's in Australia too, Canberra. dianefleming is her mentor and loq_mac should be able to help as well for any in-Aussie-time needs14:33
loq_maci'm in canberra from 26 dec to 5 jan, IIRC14:34
loq_macso i'll try and grab a coffee with her then14:34
*** dianefleming has quit IRC14:34
nerminalove that we have interns14:34
loq_mac:D14:34
annegentlenermina: yes!14:35
annegentleI miss Laura Alves :)14:36
nerminawhat happened?14:36
annegentlenermina: oh she went back to school!14:36
nerminaah14:36
annegentlenermina: it's what you do :)14:36
annegentleok, that's all I've got14:36
*** stevemar has joined #openstack-meeting14:36
annegentleta!14:36
annegentle#endmeeting14:36
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:36
openstackMeeting ended Tue Dec 10 14:36:42 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-10-14.01.html14:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-10-14.01.txt14:36
loq_macthanks annegentle14:36
openstackLog:            http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-10-14.01.log.html14:36
Sam-I-Amthanks anne14:36
nerminathank you, annegentle14:36
*** jcooley_ has quit IRC14:36
chandankumarthanks annegentle14:37
*** Sam-I-Am has left #openstack-meeting14:38
*** salv-orlando has joined #openstack-meeting14:39
*** ivasev has joined #openstack-meeting14:42
*** thomasbiege has joined #openstack-meeting14:42
*** sandywalsh_ has joined #openstack-meeting14:43
*** salv-orlando_ has joined #openstack-meeting14:44
*** sandywalsh__ has quit IRC14:44
*** beagles is now known as beagles_brb14:45
*** salv-orlando has quit IRC14:46
*** salv-orlando_ is now known as salv-orlando14:46
*** burt has joined #openstack-meeting14:47
*** jecarey has joined #openstack-meeting14:48
*** jcoufal has joined #openstack-meeting14:48
*** galstrom_zzz is now known as galstrom14:48
*** galstrom is now known as galstrom_zzz14:49
*** saurabh_ has joined #openstack-meeting14:53
*** neelashah has joined #openstack-meeting14:54
*** paragan has quit IRC14:54
*** luis_fdez has joined #openstack-meeting14:54
*** kevinconway has joined #openstack-meeting14:55
*** galstrom_zzz is now known as galstrom14:55
*** elo1 has quit IRC14:56
*** cfriesen_ has joined #openstack-meeting14:56
*** salv-orlando has quit IRC14:56
*** trey_h has joined #openstack-meeting14:57
*** akuznetsov has quit IRC14:58
*** topshare has joined #openstack-meeting14:59
*** MikeSpreitzer has joined #openstack-meeting14:59
*** cloudon_ has joined #openstack-meeting15:00
n0ano#startmeeting scheduler15:00
openstackMeeting started Tue Dec 10 15:00:21 2013 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: scheduler)"15:00
openstackThe meeting name has been set to 'scheduler'15:00
*** armax has quit IRC15:00
n0anoanyone here for the scheduler meeting?15:00
MikeSpreitzeryes15:00
*** llu-laptop has joined #openstack-meeting15:00
*** sandywalsh__ has joined #openstack-meeting15:01
*** thomasbiege1 has joined #openstack-meeting15:01
*** glikson has joined #openstack-meeting15:01
alaskio/15:01
trey_hsi15:01
gliksonhi15:01
*** sandywalsh_ has quit IRC15:01
cloudon_yes15:01
cfriesen_yup15:01
llu-laptophello15:01
*** toan-tran has joined #openstack-meeting15:02
*** cloudon1 has joined #openstack-meeting15:02
n0ano#topic Scheduler as a service15:02
*** openstack changes topic to "Scheduler as a service (Meeting topic: scheduler)"15:02
*** jgallard has joined #openstack-meeting15:02
n0anoanyone have a chance to go over the BP I referred to in the agenda?15:02
alaskido you have a link?15:03
*** tianst has joined #openstack-meeting15:03
jgallardhi all : https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout15:03
n0ano#link https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout15:03
alaskithanks15:03
toan-tranhi all15:03
n0anonote that `as a service' is a little bit of a miss-nomer, the current effor is mainly to split the scheduler code into it's own repository...15:03
*** AJaeger has left #openstack-meeting15:03
n0anoafter that it should be possible to turn it into a separate service15:04
MikeSpreitzerThat bp refers to the etherpad we all saw and the ML discussion15:04
n0anoMikeSpreitzer, indeed, I want to see if there are any issues/concerns as we are actively working on implementing that BP15:04
cloudon1think the agenda referenced the no-db-scheduler BP?15:04
*** thomasbiege has quit IRC15:05
MikeSpreitzerthat was item 215:05
n0anocloudon1, second topic for today15:05
cloudon1ok, thanks15:05
*** gokrokve has joined #openstack-meeting15:05
toan-tranMikeSpreitzer: but I think we could fusion the two15:05
*** julim has quit IRC15:05
toan-tranactually there are two approaches:15:06
toan-tranone with Robert idea of forflifting first, separate DB latter15:06
*** BillArnold has joined #openstack-meeting15:06
gliksonn0ano: I'm curious, who exactly is "actively working on implementing that BP"?15:06
toan-tranone with Boris': separate DB first , forklift latter15:06
*** Yathi has joined #openstack-meeting15:06
n0anoglikson, me for one, I'm trying to create the initial scheduler only repo that everyone can then start working on15:07
*** julim has joined #openstack-meeting15:07
gliksonn0ano: cool15:07
*** tedross has joined #openstack-meeting15:07
*** garyk has joined #openstack-meeting15:08
n0anoI actually have the first cut ready (https://github.com/n0ano/gantt), I'd like to move it to an official place soon and open it up to eveyone15:08
* n0ano git foo is getting better15:08
cfriesen_n0ano:  are you on the forklift first, change other stuff later"15:08
cfriesen_plan?15:08
n0anocfriesen_, yes, that will cause a little duplicated updating but otherwise we might get delayed waiting for no-db to be ready15:09
llu-laptopn0ano: does the new repo means new stackforge projects in Jenkins?15:09
gliksonI guess it might be useful if someone could outline the work items on launchpad, so that people who are interested to contribute could have a better view of what is going on..15:09
garykn0ano: gantt? as in gantt chart :)15:09
alaskin0ano: I agree.  forklift first means we're not waiting, boris can keep working while it's happening15:10
n0anogaryk, my alterntaive was pert if gantt doesn't work :-)15:10
*** gokrokve has quit IRC15:10
n0anoglikson, that's what the refterenced BP points to, a detailed etherpad with the forklift steps15:10
*** dkranz has joined #openstack-meeting15:11
n0anollu-laptop, yes, I believe eventually a new project will be created, once we move to scheduler as a service15:11
*** jcoufal has quit IRC15:11
*** jgrimm has joined #openstack-meeting15:12
*** reaper has joined #openstack-meeting15:12
llu-laptophow about putting the TODO list in the workItem section of BP to make it more easily to be found15:12
*** reaper has quit IRC15:12
n0anollu-laptop, I would suggest that the etherpad is the appropriate place for that, easily referenced from the BP15:12
llu-laptopn0ano: then before that, what about if someone want to propose a patch to the new repo?15:13
*** venkatesh has quit IRC15:13
*** jdob_ has joined #openstack-meeting15:13
n0anollu-laptop, not sure what your question is15:13
*** jdob has quit IRC15:13
*** yjiang5 has quit IRC15:13
garykn0ano: question is how to get this into stackforge and then having all of the relevant processed in tack15:14
n0anogaryk, llu-laptop I'm working with russellb to create the initial, bare bones repo, once we have that my assumption is it gets linked into the infrastructure so that gerrit workflows will work against it15:15
garykok, thanks for the clarification15:15
n0anowe absolutely want the current work flow, with patch approval process, to happen as soon as possible15:16
*** rnirmal has joined #openstack-meeting15:16
* n0ano bootstrapping is always a little messy15:16
*** cl_ has joined #openstack-meeting15:16
*** saurabh_ has quit IRC15:17
alaskillu-laptop: For now you would propose patches against the current scheduler code, but depending on the scope of the patch you may be asked to wait until the new repo is up and re propose there15:17
n0anoalaski, +115:18
*** loq_mac has quit IRC15:18
llu-laptopn0ano, alaski: got that, thanks15:18
*** saurabh_ has joined #openstack-meeting15:18
n0anothe goal is not to stop development (at the expense of some extra work to update two repos potentially)15:19
n0anosounds like we all understand, if there are no other issues we can move on15:19
n0anoboris-42, yt?15:19
*** hnarkaytis has joined #openstack-meeting15:19
*** loq_mac has joined #openstack-meeting15:20
n0ano#topic instance groups15:20
*** openstack changes topic to "instance groups (Meeting topic: scheduler)"15:20
n0anowhile waiting to see if boris-42 is around, garyk do you have an update on instance groups15:20
boris-42n0ano ouch hi15:20
n0anogaryk, hold off a sec15:20
n0anoboris-42, tnx15:21
n0ano#topic no-db scheduler15:21
*** openstack changes topic to "no-db scheduler (Meeting topic: scheduler)"15:21
boris-42n0ano so I am here15:21
n0anoboris-42, I saw you link to the BP, nice write up, what the status of the changes15:21
*** aloga has quit IRC15:21
*** ywu has joined #openstack-meeting15:21
boris-42n0ano alaski garyk did you read the doc?15:21
hnarkaytislet me give update on patch status15:21
hnarkaytisdesign docs were shared yesterday15:22
n0anoboris-42, I did15:22
*** markpeek has joined #openstack-meeting15:22
*** topol has joined #openstack-meeting15:22
hnarkaytisright now work focused on test suite15:22
*** jgrimm has quit IRC15:22
*** msdubov has joined #openstack-meeting15:22
boris-42n0ano yep let hnarkaytis share with us15:22
alaskiboris-42: I haven't yet, sorry.  let me go find it15:23
*** beagles_brb is now known as beagles15:23
n0anocloudon1, this was your interest, do you have any questions?15:23
hnarkaytisthere is a plan to add two more patches that will complete integration of the no-db schema15:23
hnarkaytisthat's it - patches are ready for reviews15:23
*** otherwiseguy has joined #openstack-meeting15:23
n0anocool, I like the exmphasis on testing, good point15:24
cfriesen_do we have performance numbers?15:24
*** loq_mac has quit IRC15:24
hnarkaytisyes - we prepared extended doc on this15:24
hnarkaytisI will share draft tomorrow15:24
*** Jianyong has quit IRC15:24
hnarkaytis100x gain for memchached15:24
*** coolsvap has joined #openstack-meeting15:25
*** radez_g0n3 is now known as radez15:25
n0anohnarkaytis, one point, sounds like you have more development to do but also have patches ready for review, when do you think you'll be complete?15:25
*** loq_mac has joined #openstack-meeting15:25
hnarkaytisend-to-end story will be complete till end of this week15:25
hnarkaytisright now we presented only a Synchronizer object15:26
*** gokrokve has joined #openstack-meeting15:26
hnarkaytistwo additional patches will replace existing approach on new one15:26
MikeSpreitzerBTW, what is URL for "design docs were shared yesterday"15:26
*** ArthurBerezin has joined #openstack-meeting15:26
*** gokrokve_ has joined #openstack-meeting15:26
hnarkaytishttps://etherpad.openstack.org/p/scheduler-design-proposal15:26
hnarkaytishttps://docs.google.com/a/mirantis.com/document/d/1irmDDYWWKWAGWECX8bozu8AAmzgQxMCAAdjhk53L9aM/edit15:27
hnarkaytisI posted into mail thread15:27
MikeSpreitzerthanks15:27
*** loq_mac has quit IRC15:27
MikeSpreitzermind if I add those to the BP?15:27
hnarkaytisthis mail thread - [openstack-dev] [Nova][Schduler] Volunteers wanted for a modest proposal for an external scheduler in our lifetime15:27
n0anoMikeSpreitzer, note, those are the same doc, just different locations15:27
MikeSpreitzerwhich two are the same?15:28
*** boris-42 has quit IRC15:28
hnarkaytisetherpad and google doc are the same15:29
n0anohttps://etherpad & https://docs.google.com just given by hnarkaytis15:29
*** jdob_ has quit IRC15:29
*** IlyaE has joined #openstack-meeting15:29
MikeSpreitzerthat's odd, they look different to me15:29
*** jdob has joined #openstack-meeting15:29
hnarkaytisthis is copy/paste - read any of them15:29
n0anoI just looked an, barring formatting, they have the same content15:29
MikeSpreitzerOK15:30
MikeSpreitzerSo if the BP references just one of those, which should it be?15:30
hnarkaytisas soon as last two patches will be ready - we will notify all subscribed reviewers15:30
*** gokrokve has quit IRC15:30
n0anoI'd vote for the etherpad, keep it in the family15:31
hnarkaytisyes - lets use etherpad for references15:31
llu-laptophnarkaytis: how about update the BP with the latest URL?15:31
*** sandywalsh__ has quit IRC15:31
hnarkaytisok - will do15:31
MikeSpreitzerYeah, "Set the URL for this specification"15:31
*** cl_ has quit IRC15:31
*** dianefleming has joined #openstack-meeting15:32
n0anohnarkaytis, boris-42 - good work, tnx for the effort, anyone have any other questions for them today?15:33
*** dianefleming has quit IRC15:33
*** dianefleming has joined #openstack-meeting15:34
n0anomoving on15:34
n0ano#topic instance groups15:34
*** openstack changes topic to "instance groups (Meeting topic: scheduler)"15:34
n0anogaryk, anything to say?15:34
*** aloga has joined #openstack-meeting15:34
*** maxdml has joined #openstack-meeting15:35
*** saurabh_ has quit IRC15:35
*** akuznetsov has joined #openstack-meeting15:35
*** jgrimm has joined #openstack-meeting15:35
*** dianefleming has quit IRC15:35
*** dianefleming has joined #openstack-meeting15:35
*** saurabh_ has joined #openstack-meeting15:36
hnarkaytisjust a quick note on performance test issue - document with performance numbers is referenced in BP https://docs.google.com/a/mirantis.com/document/d/1_DRv7it_mwalEZzLy5WO92TJcummpmWL4NWsWf0UWiQ/edit15:36
n0anolooks like I scared him off, I'll talk to garyk via email15:36
n0ano#topic mid-cycle meetup15:37
*** openstack changes topic to "mid-cycle meetup (Meeting topic: scheduler)"15:37
n0anothere will be a meetup in Feb in Utah, I'm going to try to attend, will anyone else be there?15:37
*** akuznetsov has quit IRC15:37
alaskiI should be there15:37
n0anolooks like the scheduler won't have a major presence there but hopefully will be a good meetup anyway15:39
n0ano#opens15:39
n0anoAny new items anyone wants to raise today?15:39
*** rongze_ has joined #openstack-meeting15:39
*** salv-orlando has joined #openstack-meeting15:40
*** rongze has quit IRC15:40
llu-laptopjust one suggestion, how about next time we put agenda to #link https://wiki.openstack.org/wiki/Meetings/Scheduler?15:40
llu-laptopsorry, https://wiki.openstack.org/wiki/Meetings/Scheduler15:41
n0anollu-laptop, I can try but I'm notoriously lax about updating Wiki, we'll see if I can motivate myself to do that15:41
* n0ano like email :-)15:41
*** herndon has joined #openstack-meeting15:42
n0anoOK, I want to thank everyone and we'll talk next week (probably cancel the two after that but we can discuss that next week)15:42
n0ano#endmeeting15:43
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:43
openstackMeeting ended Tue Dec 10 15:43:15 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:43
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-10-15.00.html15:43
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-10-15.00.txt15:43
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-10-15.00.log.html15:43
alaskithanks15:43
*** rongze_ has quit IRC15:43
*** dianefleming has quit IRC15:44
*** nermina has quit IRC15:44
*** cl_ has joined #openstack-meeting15:44
*** galstrom is now known as galstrom_zzz15:44
*** AlanClark has joined #openstack-meeting15:44
*** cfriesen_ has left #openstack-meeting15:45
*** dianefleming has joined #openstack-meeting15:45
*** dianefle_ has joined #openstack-meeting15:45
*** ArthurBerezin has quit IRC15:46
*** dianefle_ has quit IRC15:46
*** saurabh_ has quit IRC15:47
*** nermina has joined #openstack-meeting15:47
*** MikeSpreitzer has left #openstack-meeting15:47
*** fnaval has quit IRC15:47
*** mdenny has joined #openstack-meeting15:47
*** saurabh_ has joined #openstack-meeting15:47
*** galstrom_zzz is now known as galstrom15:48
*** salv-orlando has quit IRC15:48
*** nati_ueno has quit IRC15:48
*** cl_ has quit IRC15:49
*** toan-tran has quit IRC15:49
*** haomaiwang has quit IRC15:49
*** dianefleming has quit IRC15:49
*** haomaiwang has joined #openstack-meeting15:50
*** msdubov has quit IRC15:50
*** Yathi has quit IRC15:50
*** NikitaKonovalov has quit IRC15:52
*** galstrom is now known as galstrom_zzz15:53
*** tianst has quit IRC15:54
*** changbl has quit IRC15:54
*** greglucas has joined #openstack-meeting15:54
*** llu-laptop has quit IRC15:54
*** haomaiwang has quit IRC15:55
*** SergeyLukjanov has quit IRC15:55
*** changbl has joined #openstack-meeting15:55
*** garyk has quit IRC15:57
*** DinaBelova has quit IRC15:57
*** lexx has joined #openstack-meeting15:57
*** stevemar has quit IRC15:58
*** loq_mac has joined #openstack-meeting15:58
*** stevemar has joined #openstack-meeting15:58
*** saurabh_ has quit IRC15:58
*** greglucas has quit IRC15:59
*** tedross has quit IRC15:59
*** mhu has joined #openstack-meeting15:59
*** pnavarro has joined #openstack-meeting16:00
*** yaguang has quit IRC16:00
*** sushil_ has quit IRC16:00
*** jgallard has quit IRC16:01
*** ociuhandu has joined #openstack-meeting16:01
*** loq_mac has quit IRC16:01
*** Leo_ has joined #openstack-meeting16:02
*** jorisroovers has quit IRC16:02
*** sushils has joined #openstack-meeting16:02
*** jorisroovers has joined #openstack-meeting16:02
*** jaimegil has quit IRC16:03
*** luis_fdez has quit IRC16:03
*** sarob has joined #openstack-meeting16:04
*** fnaval has joined #openstack-meeting16:04
*** venkatesh has joined #openstack-meeting16:04
*** HenryG_ has joined #openstack-meeting16:05
*** vkozhukalov has quit IRC16:05
*** HenryG has quit IRC16:05
*** sarob has quit IRC16:05
*** sarob has joined #openstack-meeting16:06
*** jcooley_ has joined #openstack-meeting16:06
*** jroovers has joined #openstack-meeting16:06
*** glikson has quit IRC16:07
*** trey_h has quit IRC16:07
*** lijli has quit IRC16:09
*** jorisroovers has quit IRC16:10
*** sarob has quit IRC16:10
*** nermina has quit IRC16:11
*** sarob has joined #openstack-meeting16:11
*** mdurnosvistov has quit IRC16:11
*** tedross has joined #openstack-meeting16:11
*** sarob has quit IRC16:12
*** thomasbiege1 has quit IRC16:12
*** reed has joined #openstack-meeting16:12
*** saurabh_ has joined #openstack-meeting16:13
*** sarob has joined #openstack-meeting16:13
*** lijli has joined #openstack-meeting16:13
*** sarob has quit IRC16:14
*** sarob has joined #openstack-meeting16:16
*** jcooley_ has quit IRC16:16
*** jroovers has quit IRC16:16
*** jcooley_ has joined #openstack-meeting16:17
*** sarob has quit IRC16:17
*** loq_mac has joined #openstack-meeting16:18
*** saurabh_ has quit IRC16:19
*** lexx has quit IRC16:19
*** saurabh_ has joined #openstack-meeting16:20
*** sarob has joined #openstack-meeting16:20
*** HenryG_ has quit IRC16:21
*** sarob has quit IRC16:22
*** HenryG has joined #openstack-meeting16:23
*** sarob has joined #openstack-meeting16:23
*** spzala has joined #openstack-meeting16:24
*** sarob has quit IRC16:24
*** sacharya has joined #openstack-meeting16:25
*** sarob has joined #openstack-meeting16:26
*** avishayb has quit IRC16:27
*** thomasbiege has joined #openstack-meeting16:30
*** sarob has quit IRC16:30
*** sarob has joined #openstack-meeting16:31
*** boris-42 has joined #openstack-meeting16:33
*** sdague has left #openstack-meeting16:33
*** sdague has joined #openstack-meeting16:33
*** sarob has quit IRC16:36
*** ildikov has quit IRC16:37
*** sarob has joined #openstack-meeting16:38
*** jcooley_ has quit IRC16:40
*** nprivalova has quit IRC16:40
*** mrodden1 has quit IRC16:40
*** jcooley_ has joined #openstack-meeting16:40
*** colinmcnamara has quit IRC16:42
*** colinmcn_ has quit IRC16:42
*** loq_mac has quit IRC16:42
*** akuznetsov has joined #openstack-meeting16:43
*** sarob has quit IRC16:43
*** bdperkin has quit IRC16:44
*** bdperkin has joined #openstack-meeting16:44
*** topshare has quit IRC16:45
*** jcooley_ has quit IRC16:45
*** aloga has quit IRC16:45
*** sarob has joined #openstack-meeting16:45
*** topshare has joined #openstack-meeting16:45
*** belmoreira has quit IRC16:45
*** glikson has joined #openstack-meeting16:46
*** belmoreira has joined #openstack-meeting16:46
*** topshare has quit IRC16:46
*** marun has quit IRC16:46
*** MaxV has quit IRC16:46
*** elo1 has joined #openstack-meeting16:46
*** sarob_ has joined #openstack-meeting16:47
*** MaxV has joined #openstack-meeting16:47
*** HenryG has quit IRC16:47
*** colinmcnamara has joined #openstack-meeting16:47
*** colinmcn_ has joined #openstack-meeting16:47
*** sarob_ has quit IRC16:48
*** elo1 has joined #openstack-meeting16:48
*** sarob has quit IRC16:49
*** SumitNaiksatam has quit IRC16:50
*** belmoreira has quit IRC16:50
*** elo1 has quit IRC16:51
*** MaxV has quit IRC16:51
*** gyee has joined #openstack-meeting16:52
*** MarkAtwood has joined #openstack-meeting16:52
*** mrichman_ has joined #openstack-meeting16:53
*** msdubov has joined #openstack-meeting16:54
*** venkatesh has quit IRC16:55
*** mrodden has joined #openstack-meeting16:55
*** nati_ueno has joined #openstack-meeting16:57
*** elo1 has joined #openstack-meeting17:00
*** flaper87 is now known as flaper87|afk17:00
*** glikson has quit IRC17:00
*** NikitaKonovalov has joined #openstack-meeting17:01
*** loq_mac has joined #openstack-meeting17:02
*** BillArnold has quit IRC17:03
*** jmontemayor has joined #openstack-meeting17:05
boris-42hey all17:06
boris-42#startmeeting17:06
openstackboris-42: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'17:06
boris-42#startmeeting Rally17:06
openstackMeeting started Tue Dec 10 17:06:23 2013 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:06
*** openstack changes topic to " (Meeting topic: Rally)"17:06
openstackThe meeting name has been set to 'rally'17:06
boris-42msdubov harlowja jaypipes hi17:07
*** NikitaKonovalov has quit IRC17:07
msdubovboris-42 hi17:07
boris-42jd__ hi17:07
*** Alexei_987 has joined #openstack-meeting17:08
*** NikitaKonovalov has joined #openstack-meeting17:08
boris-42Alexei_987 hi17:09
Alexei_987Hi :)17:09
boris-42jog0 ping17:09
boris-42Ok let's start17:09
*** NikitaKonovalov has quit IRC17:09
boris-42#topic Updates in benchmark engine17:10
*** openstack changes topic to "Updates in benchmark engine (Meeting topic: Rally)"17:10
*** SergeyLukjanov has joined #openstack-meeting17:10
boris-42msdubov can you share with us17:10
boris-42msdubov your recent efforts17:10
*** simon-AS559 has quit IRC17:10
msdubovboris-42 The main update is no doubt the patch implementing the generic cloud cleanup after launching benchmarks implemented by boden17:11
*** eyerediskin has joined #openstack-meeting17:11
*** SergeyLukjanov is now known as _SergeyLukjanov17:11
msdubovIt has been merged today and required me to put a lot of efforts on rebasing my patches17:11
*** _SergeyLukjanov is now known as SergeyLukjanov17:11
*** SumitNaiksatam has joined #openstack-meeting17:12
msdubovAs for my patches, they are implementing the init() procedure, which is a kind of the opposite thing to cleanup. In init(), one can initialize some resources required for a benchmark scenario, e.g. servers17:12
boris-42msdubov I saw some concerns from Alexei_98717:12
*** NikitaKonovalov has joined #openstack-meeting17:12
msdubovI also exemplify it with the patch that implements the benchmark scenario for setting and deleting metadata to a predefined (in init()) server17:13
msdubovboris-42 Yep they are addressing the way the benchmark engine works currently17:13
Alexei_987boris-42: msdubov yes17:13
boris-42Alexei_987 do you have some ideas how to improve it?17:13
msdubovThe restrictions posed by multiprocessing tool used in the benchmark engine lead to a somewhat ugly way of implementing the engine.17:13
msdubov*pool17:13
*** NikitaKonovalov has quit IRC17:13
Alexei_987boris-42: msdubov our benchmarking system is a lot alike unittest framework17:13
boris-42Alexei_987 not sure17:14
Alexei_987and I think we should reuse their code and experience17:14
Alexei_987why not?17:14
Alexei_987they have setUp/tearDown + run17:14
eyerediskinwhy not using threads?17:14
boris-42Alexei_987 yep but they don't have billions of temp users17:14
Alexei_987otherwise we'll have to reinvent the wheel all over again17:14
boris-42Alexei_987 projects17:14
boris-42Alexei_987 resources that should be cleaned17:14
Alexei_987why do you think they don't?17:15
boris-42Alexei_987 and unit test are run only 1 time17:15
Alexei_987unittest is used in many various scenarios17:15
boris-42Alexei_987 we already use pytest as a base of our benchmark system17:15
boris-42Alexei_987 it was made by Eugeniy17:15
Alexei_987anyway I'm not talking about using unittest17:15
msduboveyerediskin I suppose threads will pose the same restrictions on the things we can pass to the called methods? The primary problem actually is we can't pass openstack clients to benchmark scenarios17:15
Alexei_987I'm talking about that current design that we have has many issues17:16
boris-42Alexei_987 like?17:16
Alexei_987related to code organization17:16
Alexei_987object creation and so on17:16
boris-42Alexei_987 and how are you going to avoid object creation using pytest unit test or something other?17:16
Alexei_987I've mentioned one of them to msdubov17:16
*** jpich has joined #openstack-meeting17:17
Alexei_987for example classmethod can only be called under certain conditions17:17
boris-42Alexei_987 I mean let's start from task17:17
boris-42Alexei_987 we have 1 method that is benchmark scenario17:17
*** loq_mac has quit IRC17:17
*** NikitaKonovalov has joined #openstack-meeting17:17
msdubovAlexei_987 Yep the possible bug you mentioned indeed can take place, but in fact the benchmark engine manages classes in such a way that this cannot happen17:17
Alexei_987ok.. I mean that unittest and other big frameworks have certain way and procedure of when and how to create objects17:17
*** pablosan has joined #openstack-meeting17:17
boris-42Alexei_987 could you explain17:18
boris-42Alexei_987 on current task17:18
Alexei_987for example our problem is that we have to pass objects to other process17:18
Alexei_987which is bad17:18
boris-42Alexei_987 yep but how are you going to fix it?17:18
Alexei_987they should be created where they are actually used17:18
boris-42Alexei_987 no17:19
eyerediskincreate object in process instead of passing it?17:19
Alexei_987without passing them all over the system17:19
Alexei_987yes17:19
boris-42Alexei_987 no17:19
*** lexx has joined #openstack-meeting17:19
Alexei_987why not?17:19
boris-42Alexei_987 because the case is another17:19
eyerediskinjust like setUp method in tests17:19
msdubovAlexei_987 But we may launch a benchmark scenario millions of times, and we want to create OpenStack clients only once17:19
*** yjiang5 has joined #openstack-meeting17:19
Alexei_987why?17:19
boris-42Alexei_987 because we are testing not abstract shit=)17:19
eyerediskinobjects are created once thread/process is started17:19
Alexei_987creation of a python object takes almost 0 ms17:19
boris-42Alexei_987 creation of billions users take a lot of time17:20
eyerediskinagreed with Alexei_98717:20
Alexei_987users yes but not clients17:20
*** yjiang5 has left #openstack-meeting17:20
Alexei_987you can pass user credential17:20
Alexei_987plain dict17:20
*** terriyu has joined #openstack-meeting17:20
Alexei_987and create a complex object later17:20
boris-42Alexei_987 and Floting IPs FixedIps17:20
boris-42Alexei_987 images17:20
boris-42Alexei_987 other stuff that you need in init17:20
boris-42Alexei_987 also if you put this to thread17:20
boris-42Alexei_987 then you will need to create them in each method17:21
eyerediskinthis stuff created once per process/thread. created only objects needed by process/thread17:21
Alexei_987what do you mean by each method?17:21
boris-42Alexei_987 eyerediskin  https://github.com/stackforge/rally/blob/master/rally/benchmark/scenarios/nova/servers.py#L29-L3717:21
*** cdub has joined #openstack-meeting17:21
boris-42Alexei_987 eyerediskin  this method get's random clients in cls17:22
Alexei_987clients?17:22
Alexei_987I don't see any clients in there17:22
boris-42Alexei_987 yep clients17:22
*** yassine_ has quit IRC17:22
msdubovAlexei_987 (chosen randomly of many client users)17:22
msdubovAlexei_987 they are used in utils17:22
Alexei_987so it chooses a random user credential17:22
Alexei_987please be precise17:22
boris-42Alexei_987 https://github.com/stackforge/rally/blob/master/rally/benchmark/scenarios/nova/utils.py#L28-L4917:23
Alexei_987client is not tied to user17:23
*** mdurnosvistov has joined #openstack-meeting17:23
Alexei_987the only things that connects it to the user is auth token17:23
Alexei_987again let's separate clients and users17:24
Alexei_987user -> auth_token is just a string17:24
boris-42Alexei_987 again I don't care about users17:24
boris-42Alexei_987 in becnhmarks17:24
Alexei_987why not?17:24
boris-42Alexei_987 I care about clients17:24
Alexei_987clients?17:24
Alexei_987then I must have missed something17:24
boris-42Alexei_987 glacne, nova, keystone, …. clients for this user17:24
Alexei_987so...17:24
Alexei_987there is a word user17:24
boris-42Alexei_987l so I would like to be able cls.clients("nova").servers.create(server_name, image_id,17:25
boris-42                                                    flavor_id, **kwargs)17:25
boris-42cls.clients("nova")17:25
boris-42use from benchmark dirrectly17:25
Alexei_987yes but user is hidden inside17:25
boris-42Alexei_987 yep17:25
Alexei_987so we can change code in such a way that we only pass users17:25
*** aloga has joined #openstack-meeting17:25
Alexei_987and not clients17:25
boris-42Alexei_987 why17:26
boris-42Alexei_987 to create in each method client every time by hand?17:26
boris-42Alexei_987 it is called "copy paste"17:26
Alexei_987(facepalm)17:26
Alexei_987client manager can handle this17:26
boris-42Alexei_987 in each benchmark I need clients17:26
*** NikitaKonovalov has quit IRC17:26
Alexei_987and reuse 1 client object for 1000 benchmarks17:26
Alexei_987just bind it to certain user before usage17:26
Alexei_987the main idea is that we have to define data flow17:27
Alexei_987and data dependencies17:27
boris-42Alexei_987 hm I don't understand17:27
Alexei_987so we won't have to apply dirty hacks to make it work17:27
*** NikitaKonovalov has joined #openstack-meeting17:27
*** bgorski has joined #openstack-meeting17:28
boris-42Alexei_987 we need to be able to pass the same data in every thread17:28
*** geekinutah has joined #openstack-meeting17:28
boris-42Alexei_987 or even more different data17:28
*** sdake_ has joined #openstack-meeting17:28
Alexei_987why we should do it?17:28
*** ygbo has quit IRC17:28
boris-42Alexei_987 in every call of method17:28
Alexei_987we should only pass data that is used in that thread17:28
boris-42Alexei_987 ?17:28
boris-42Alexei_987 and it could be all data from INIT17:28
boris-42Alexei_987 that is called only 1 time17:29
*** sandywalsh_ has joined #openstack-meeting17:29
boris-42Alexei_987 like create 20k fixed IPs17:29
*** geekinutah has left #openstack-meeting17:29
Alexei_987and 1 tests uses all 20k fixed ips?17:29
boris-42Alexei_987 I don't know what will test use17:29
*** loq_mac has joined #openstack-meeting17:30
*** bknudson has joined #openstack-meeting17:30
Alexei_987ok.. such discussion is not productive at all17:30
Alexei_987need additional digging in here17:30
boris-42Alexei_987 lol17:30
boris-42Alexei_987 we should talk about user case17:30
boris-42Alexei_987 my user case was next17:30
boris-42Alexei_987 use case*17:30
boris-42Alexei_987 then it will be more clean17:31
boris-42msdubov could you write etherpad with full description about our use cases and how they are implemented17:32
boris-42msdubov Alexei_987  ^ so we will be able to continue this discussion next week17:32
*** atiwari has joined #openstack-meeting17:32
boris-42okay let's close this discussion a got to another topic17:32
Alexei_987ok :)17:32
*** galstrom_zzz is now known as galstrom17:32
msdubovboris-42 ok17:32
boris-42#topic Profiling system17:32
*** openstack changes topic to "Profiling system (Meeting topic: Rally)"17:32
*** sandywalsh has quit IRC17:33
boris-42Alexei_987 could you say for jd__ and jog0 current status of your work17:33
Alexei_987cool :)17:33
Alexei_987I have 1 patch in ceilometer on review17:33
Alexei_987that adds data collector functionality17:33
Alexei_987+ I have 1 patch in process of polishing in nova17:33
*** s0mik has joined #openstack-meeting17:34
Alexei_987that adds library that will collect and send data17:34
*** ivar-lazzaro has joined #openstack-meeting17:34
Alexei_987that's the current status17:34
*** sacharya has quit IRC17:34
Alexei_987I also have some problems that we can discuss17:34
boris-42Alexei_987 could you share with links to the patches?17:34
Alexei_987https://review.openstack.org/#/c/60262/17:35
Alexei_987https://review.openstack.org/#/c/60797/17:35
boris-42Alexei_987 and what problem do you have?17:35
*** troytoman-away is now known as troytoman17:35
*** blamar has joined #openstack-meeting17:35
Alexei_987so the problem is: how and where do we store a profiler object on single service17:35
boris-42Alexei_987 could you explain?17:36
Alexei_987this is kind of cross functionality that should be accessible from anywhere17:36
Alexei_987but we should not bind it to singleton of any kind17:36
*** sacharya has joined #openstack-meeting17:36
Alexei_987in openstack I didn't find a proper way of doing such a thing17:36
Alexei_987it's somewhat common with logging system17:37
Alexei_987but logger is created for each file separately17:37
boris-42Alexei_987 but why we are not able just to put Profiler class to oslo-incubator17:37
boris-42Alexei_987 and copy paste it to all projects?17:37
Alexei_987nah.. the code will lie in oslo17:37
boris-42Alexei_987 and what is the problem?17:37
*** sarob has joined #openstack-meeting17:37
Alexei_987I mean when we create a profiler object: Profiler(service='nova')17:37
Alexei_987where do we put it?17:38
*** cloudon1 has quit IRC17:38
boris-42You should call it Profiler(service="oslo") and it will be replaced during sync to ("proect_name")17:38
boris-42Alexei_987 ^17:38
boris-42Alexei_987 and this could be done in oslo code actually17:38
Alexei_987hm the name?17:38
Alexei_987or the object?17:39
Alexei_987name ok..17:39
boris-42Alexei_987 all can be stored there17:39
Alexei_987ha ha17:39
Alexei_987you should ask Roman Po..17:39
Alexei_987how much pain they have now cause of global config object17:39
boris-42Alexei_987 first of all they have another problmes17:39
Alexei_987yes...17:40
boris-42Alexei_987 they would like to move the code in separated lib17:40
Alexei_987but library should not create any active objects17:40
boris-42Alexei_987 that use another libs17:40
Alexei_987that's why it's libraryt17:40
Alexei_987library should only provide functionality17:40
boris-42Alexei_987 but actually we are going to patch with our lib another libs17:40
boris-42Alexei_987 like oslo.log, oslo.messegin?17:41
Alexei_987oslo.log - no17:41
*** jmontemayor has quit IRC17:41
*** safchain has quit IRC17:41
Alexei_987messaging - maybe17:41
Alexei_987but mostly it will be used on higher level code17:41
Alexei_987such as controllers, etc.17:41
*** cloudon_ has quit IRC17:41
*** loq_mac has quit IRC17:42
boris-42Alexei_987 so I don't see any problem to just take Profiler() code put it into oslo17:42
*** Fdot has quit IRC17:42
Alexei_987and I do :)17:42
boris-42Alexei_987 then sync a create locally in every code17:42
boris-42Alexei_987 project*17:42
boris-42Alexei_987 and then use it for tracing17:42
Alexei_987code yes17:42
Alexei_987objects no17:42
boris-42Alexei_987 and have 2 new config options (in oslo or projects)17:42
boris-42Alexei_987 you don't need to store any objects17:42
boris-42Alexei_987 what is the problem?17:43
boris-42Alexei_987 I didn't have any problems with using DB code in all projects17:43
boris-42Alexei_987 and DB code is much more complex that this 50lines17:43
boris-42Alexei_987 and have much more dependencies17:43
Alexei_987there are some problems related to ENGINE being a singleton17:44
boris-42Alexei_987 Engine?17:44
Alexei_987yes.. connection object17:44
boris-42Alexei_987 you are speaking now about DB?17:44
Alexei_987(facepalm)17:44
Alexei_9871 sec17:44
boris-42Alexei_987 omg17:44
*** nati_ueno has quit IRC17:45
Alexei_987https://github.com/openstack/oslo-incubator/blob/master/openstack/common/db/sqlalchemy/session.py#L35617:45
Alexei_987ENGINE17:45
Alexei_987global object17:45
*** fabio_ has joined #openstack-meeting17:45
Alexei_987cause of it we cannot implement slave reads properly17:45
*** fabio_ is now known as fabiog17:45
*** troytoman is now known as troytoman-away17:46
*** NikitaKonovalov has quit IRC17:46
Alexei_987anyway...17:46
*** IlyaE has quit IRC17:46
Alexei_987so there is a problem in this object placement..17:46
Alexei_987and I suggest to move on for now17:46
boris-42Alexei_987 okay17:46
Alexei_987so we don't waste all the time17:46
boris-42#topic Deploy engines17:47
*** openstack changes topic to "Deploy engines (Meeting topic: Rally)"17:47
boris-42eyerediskin hey can you share with your updates17:47
eyerediskinFuel engine is coming soon. One or wo days17:47
boris-42eyerediskin oh nice17:47
*** jcooley_ has joined #openstack-meeting17:48
*** bdpayne has joined #openstack-meeting17:48
boris-42eyerediskin I saw some changes are checking configs17:48
boris-42eyerediskin around checking configs*17:48
eyerediskinyep, this is almost done17:48
boris-42eyerediskin what is left?17:49
*** comay has joined #openstack-meeting17:49
*** tedross has left #openstack-meeting17:49
*** jmontemayor has joined #openstack-meeting17:49
eyerediskinconfig validation in providers. Maxim is working on it17:49
*** MaxV has joined #openstack-meeting17:49
eyerediskinhttps://review.openstack.org/#/c/60275/17:50
eyerediskinhttps://review.openstack.org/#/c/60030/17:50
eyerediskinsome patches waiting for +2 =)17:50
*** jcooley_ has quit IRC17:50
boris-42eyerediskin https://review.openstack.org/#/c/60030/ <- +2ed17:51
*** anniec has joined #openstack-meeting17:51
boris-42eyerediskin and how about LXCEngine?17:51
boris-42eyerediskin are you working around it, to make it work inside OS cloud?17:51
eyerediskinI gonna continue with it after fuel engine is done17:52
boris-42eyerediskin okay nice17:52
boris-42okay let's move to the next topic17:52
eyerediskinboris-42: I'got solution in my mind. Just need to code it17:52
boris-42eyerediskin nice17:52
boris-42#topic Rally as a Service17:53
*** openstack changes topic to "Rally as a Service (Meeting topic: Rally)"17:53
*** lexx has quit IRC17:53
*** dolphm_ has joined #openstack-meeting17:53
boris-42We would like to add Web UI, and make it possible to work together with one Rally instances17:53
boris-42So the right way is to make from Rally service17:53
boris-42and make something like in nova and other projects17:53
boris-42we will build REST with pecan17:54
boris-42And make API + Managers (or master + workers) using oslo.messeging17:54
*** ociuhandu has left #openstack-meeting17:54
boris-42I don't think that these decisions requires discussion17:54
Alexei_987we'll use the same async approach with eventlet and hookers?17:55
boris-42But there is a discussion how to make it better17:55
boris-42Alexei_987 ?17:55
*** dstanek has joined #openstack-meeting17:55
*** troytoman-away is now known as troytoman17:55
Alexei_987nonblocking code and all the stuff like in nova17:55
*** jmontemayor has quit IRC17:55
Alexei_987in our service17:55
*** NikitaKonovalov has joined #openstack-meeting17:56
boris-42Alexei_987 There will be API that just make plain operation (get data from DB) or stat task and make record in DB17:56
boris-42And call managers that will actually run all other stuff17:56
Alexei_987ok.. so no async code and no eventlet :)17:56
Alexei_987cool17:56
boris-42Alexei_987 so we will use rpc.cast calls17:56
boris-42Alexei_987 for long operations17:56
*** HenryG has joined #openstack-meeting17:56
*** jlibosva1 has quit IRC17:57
boris-42Alexei_987 so yep no eventlet shit17:57
Alexei_987ok I got it17:57
*** vedlad has joined #openstack-meeting17:57
boris-42And we actually started discussion17:57
boris-42About how to make this possible inside Rally17:57
boris-42and what changes we should make17:57
*** lsmola_ has joined #openstack-meeting17:57
*** mrunge has quit IRC17:57
boris-42https://etherpad.openstack.org/p/rally-service-arch17:57
boris-42here is it ^17:57
boris-42it is just draft not ready so if everyone is interested it can help with advices17:58
boris-42So okay17:58
boris-42that is all17:58
boris-42#topic free discussions17:58
*** openstack changes topic to "free discussions (Meeting topic: Rally)"17:58
boris-42So if somebody have any questions or something else just ask17:58
eyerediskinthere is blueprint in devstack17:59
*** nkinder has joined #openstack-meeting17:59
eyerediskinhttps://blueprints.launchpad.net/devstack/+spec/devstack-rally17:59
eyerediskinmeybe someone wants to implement it18:00
*** noslzzp has quit IRC18:00
*** sacharya has quit IRC18:00
boris-42eyerediskin could you specify drafter, assignee and so on?18:00
boris-42eyerediskin and series18:00
boris-42eyerediskin I think that it will be nice to implement it18:00
boris-42eyerediskin especially if we are going to make from Rally service18:01
*** sacharya has joined #openstack-meeting18:01
*** henrynash has joined #openstack-meeting18:01
*** ihrachyska has quit IRC18:01
boris-42okay let's finish this meeting18:01
boris-42#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Tue Dec 10 18:01:53 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-10-17.06.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-10-17.06.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-10-17.06.log.html18:01
henrynashhi18:02
bknudsonhi18:02
morganfainbergo/18:02
dstaneko/18:02
shardyo/18:02
morganfainbergdolphm_, ayoung, gyee, stevemar o/18:02
gyee\o18:02
dolphm_O/18:02
dolphm_#startmeeting keystone18:02
openstackMeeting started Tue Dec 10 18:02:43 2013 UTC and is due to finish in 60 minutes.  The chair is dolphm_. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
tristanCHello guys!18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
ayoungYou rang!18:02
dolphm_#topic keystone hackday!18:03
fabioghi18:03
*** openstack changes topic to "keystone hackday! (Meeting topic: keystone)"18:03
*** jlibosva has joined #openstack-meeting18:03
*** noslzzp has joined #openstack-meeting18:03
*** jamielennox has joined #openstack-meeting18:03
dolphm_As mentioned a bit at the summit, I'd like to host a keystone hackday around the end of milestone 2 at Rackspace's office in San Antonio, TX. I put two options for dates on the agenda-- if you can attend and prefer one or the other, speak up! Otherwise I'm running with option 1 which end on the last Friday of milestone development18:03
morganfainbergweee!18:03
lbragstadHi18:03
dolphm_Can someone past the options from the meeting agenda?18:03
* gyee is looking forward to the two week mandatory Christmas vacation18:03
morganfainbergOption 1: Wednesday-Thursday-Friday January 17-19th (ahead of the milestone)18:03
dolphm_I'm trapped on my phone again :)18:03
morganfainbergOption 2: Monday-Tuesday-Wednesday January 22-24th (around the milestone)18:03
bknudsonisn't it chinese new year around then?18:04
henrynasheither is fine by me18:04
*** marekd has joined #openstack-meeting18:04
dolphm_bkhudson: sure why not18:04
morganfainbergI think ahead of the milestone is better18:04
morganfainberg(option 1)18:04
morganfainbergbut that is just personal bias.18:04
dstaneki think i'd be find with either18:04
gyeeI can bring chinese fire crackers to celebrate18:05
dolphm_agree, and we wanted a Friday :)18:05
ayoungdolphm_, Gettin close on dates, we probably need to lock it down for airfare18:05
morganfainbergdolphm_, ++18:05
*** lexx has joined #openstack-meeting18:05
ayounggyee, Bringing fireworks to Texas is like bringing Coal to Newcastle18:05
morganfainbergand letting employers know and all that.18:05
dolphm_ayoung: I'd like to pick now for that reason18:06
stevemari'll let topol know, not sure if he's here18:06
*** brich1 has joined #openstack-meeting18:06
*** mrichman_ has quit IRC18:06
gyeestevemar, just submit the expense report later18:07
*** eyerediskin has left #openstack-meeting18:07
stevemargyee, that's insanity18:07
dolphm_gyee++ ask for forgiveness18:07
*** jmontemayor has joined #openstack-meeting18:07
ayoungdolphm_, so, I think we should agree that if we go with the later date, anything done during the hackfest is fair game for Icehouse, API freeze or no.  Otherwise, it has to be the earlier one.18:07
morganfainbergdolphm_, uhm... is my calendar wrong? but... 17-19 seems to be friday, saturday, sunday?18:07
stevemaroooo i like that, ayoung ++18:08
dolphm_ayoung: earlier one the18:08
dolphm_n18:08
*** kevinconway has quit IRC18:08
ayoungmorganfainberg, you are right18:08
dolphm_did I calendar bad?18:08
stevemaryou did18:08
dolphm_dammit18:08
morganfainbergyep18:08
*** nati_ueno has joined #openstack-meeting18:08
ayoungWhen is I2?18:08
morganfainberg#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule18:09
*** sushils has quit IRC18:09
gyee1/2318:09
morganfainbergJan 2318:09
ayounghttps://launchpad.net/keystone/+milestone/icehouse-218:09
*** dolphm has joined #openstack-meeting18:09
ayoungSo 15-17 would be Wed-Fri before18:10
morganfainbergi think the first one would need to be jan 15, 16, 17 (wed -> fri)18:10
ayoungand 20-2218:10
dolphmalright so icehouse-m2 is the 23rd, which means branching on the 21st, which means Option 1 was supposed to be Jan 15-1718:11
*** pdmars_ has joined #openstack-meeting18:11
morganfainbergand i like that one better because it gives us a (short) window to follow up on anything that comes out of it to hit i2 if needed18:11
dolphmi bet i was looking at 2012 or something18:11
*** pdmars has quit IRC18:11
*** loq_mac has joined #openstack-meeting18:12
dolphm#agreed Keystone Hackday Icehouse January 15-17 @ San Antonio, TX18:12
bknudson1218 miles for me... straight down i3518:12
*** mrunge has joined #openstack-meeting18:12
dolphmbknudson: you've got 3 items on the agenda -- which do you want first ?18:12
*** mrunge has quit IRC18:12
*** mrunge has joined #openstack-meeting18:12
bknudsonlet's start at the beginning18:12
bknudsontempest change for assignments-doesn't-check-identity18:13
dolphm#topic Tempest change for assignments-doesn't-check-identity18:13
bknudsonso I put the change in at henrynash 's request18:13
bknudsonand then it failed tempest because they added a test that if you assign a role to a user doesn't exist then it fails18:13
bknudsonso I added the tempest change but they didn't like it... wanted a blueprint18:13
henrynashbknudson: :-(18:13
dolphm#link assignments-doesn't-check-identity18:13
dolphmerr18:14
dolphm#link https://review.openstack.org/#/c/56106/18:14
bknudsonso I looked for blueprint and didn't see one that would be obvious to tempest18:14
bknudsonI could use federation ... but I don't think that's obvious18:14
bknudsonso how about a new blueprint?18:14
bknudsonsplit-identity was also suggested, but that one is closed already18:15
ayoungbknudson, you should be able to create a role assignment for a bogus user and have it succeed.  Then create the user in SQL and they get the roles when next they get a token18:15
*** s0mik has quit IRC18:15
bknudsonayoung: that's what my fix does, and what the tempest tests don't allow18:15
dolphm#link https://review.openstack.org/#/c/54647/18:16
gyeewith federation, you'd be insane to assign roles directly to users18:16
*** ihrachyska has joined #openstack-meeting18:16
dolphmbknudson: new bp ++18:17
*** topol has quit IRC18:17
bknudsondolphm: ok, just wanted to make sure.18:17
*** dolphm_ has quit IRC18:17
dolphmgyee: ++ not really possible at all18:17
dstanekbknudson: is you comment true that assigning to a non-existent use may return either a success or 404?18:17
*** vkozhukalov has joined #openstack-meeting18:18
ayounggyee, except that we are going to have to.  There are no group mechanisms in Identity that we can count on, and we don't have user groups in Assignments18:18
bknudsondstanek: the identity spec doesn't says that it can return success, and the keystone server can also return 40418:18
dolphmayoung: mapping comes into play18:18
gyeealways maps users to groups, that's the best way to manage changes18:19
ayoungbknudson, the split-identity blueprint should cover this behavior18:19
ayounghttps://blueprints.launchpad.net/keystone/+spec/split-identity18:19
gyeeyour auditing will be that much easier18:19
bknudsonayoung: but the split-identity blueprint is complete ... would seem odd to re-open it?18:19
*** topol has joined #openstack-meeting18:19
dstanekbknudson: i can see why sdague doesn't like it - it really is multiple scenarios18:19
dolphmayoung: re-opening released bp's is a no-no18:19
ayoungbknudson, hmmmm18:20
morganfainberggyee, ++, it still doesn't change the fact that you can't rely on identity to assign a role in all cases.  you'd need to still assign without checking / not fail?18:20
bknudsonMaybe I can make the new blueprint a continuation of split-identity.18:20
*** vipuls is now known as vipuls-away18:20
dolphmbknudson: yeah, we can link them up18:20
ayoungcould also be covered under federation if it is for future work18:20
gyeemorganfainberg, you'll always assign roles to groups18:21
ayounghttps://blueprints.launchpad.net/keystone/+spec/federation18:21
morganfainberggyee, yes.18:21
bknudsonayoung: the concern I have with using federation bp is that I don't think it's going to be obvious to tempest what the connection is.18:22
morganfainbergbknudson, make a new bp linked to federation?18:22
ayoungmorganfainberg, ++18:22
bknudsona new bp linked to federation would make it obvious, so I'm fine with that18:22
*** Abhishek_ has joined #openstack-meeting18:23
ayoungI think all of the arrows are pointing the wrong way in the dependency graph https://blueprints.launchpad.net/keystone/+spec/federation18:23
ayoungI'll take the action item to write the BP18:24
gyeeayoung, good observation18:24
bknudsonayoung: great, thanks18:24
ayoungbknudson, and then I'll assign to you?18:24
bknudsonyep18:24
*** adalbas has quit IRC18:24
dolphm#action syoung to write the bp18:24
ayoungdolphm, probably want more context in those #action lines....18:25
*** vipuls-away is now known as vipuls18:25
dolphm#topic REMOTE_USER auth v2 and v3 mismatch18:25
*** s0mik has joined #openstack-meeting18:25
*** vahidh has joined #openstack-meeting18:25
gyeedidn't we beat this horse to death already?18:26
ayoungdolphm, I think the latest patch is on track for REMOTE_USER18:26
dolphmA) we need to provide compat with grizzly throuhg master, which is currently broken18:26
*** hemnafk is now known as hemna18:26
dolphmayoung: good to hear18:26
bknudsonso on this one... I think it would be great to have some doc that says what the plugins we want are.18:26
ayoung#link https://review.openstack.org/#/c/50362/18:26
bknudsonmaybe I'm the only one who needs this to be more explicit so we can make sure we've got them all.18:26
dolphmbknudson: genreally thats the bp system :P18:26
gyeebknudson, ++ on good doc, that's the best we can do here18:26
ayoungbknudson, we need to old behavior, which turns all of REMOTE_USER into the user-id, and we need the Split on the @ sign for Kerberos18:27
dolphmuse cases for each should be doc'd in bp's18:27
bknudsonok, I'll aim for a bp.18:27
bknudsonthat was it18:28
dolphmcool18:28
dolphm#topic Moving keystone tests to tempest18:28
*** msdubov has quit IRC18:28
bknudsonso, unfortunately I missed the summit session.18:28
bknudsonbut I had some time so I decided to get started on this.18:29
bknudsonI thought the best way to go is to essentially copy keystone's client tests to tempest18:29
*** eharney has quit IRC18:29
bknudsonbecause don't want to lose any coverage they're giving us18:29
bknudsonso I posted 1 test for now, to see if tempest was ok with it18:30
bknudsonbut, I don't think they want our tests as they are...18:30
ayoungbknudson, the fixtures were always the weak link18:30
jamielennoxbknudson: understandable18:30
*** vuil has joined #openstack-meeting18:30
bknudsonI put them in "scenarios", and they don't fit well with the other scenario tests.18:30
*** eharney has joined #openstack-meeting18:30
bknudsonnow, shardy had made a new directory for client API tests18:30
bknudsonbut that change is -2 and abandoned at this point18:31
shardybknudson: I spoke to sdague a while back, and IIRC he said put them under scenario18:31
bknudsonso maybe tempest can be convinced to accept a new directory for client tests18:31
ayoungDo they have a standards document that they are saying we need to meet, or is it all Project norms at this point?18:31
shardyI think the separate tree was what caused all the upset ;)18:31
dolphmaren't we blocked on the patch that mordred mentioned on list?18:31
ayoungWhat is a "scenario"18:31
*** nkinder has left #openstack-meeting18:31
*** pdmars_ has quit IRC18:31
*** kevinconway has joined #openstack-meeting18:32
bknudsonshardy: the new trust tests would probably be an excellent candidate for a scenario test...18:32
bknudsoncould go through a whole scenario where get token, get trust, do something, delete trust, etc.18:32
dolphmayoung: basically a configuration of openstack18:32
dolphmayoung: i.e. stable/havana keystone running on SQL vs a year old release of keystoneclient18:32
shardybknudson: Yeah, I've revived the API surface tests, and I'll revive those client trusts tess as scenario tests soon18:32
bknudsonthe API surface test is the one that I think tempest has more concern about18:33
ayoungdolphm, so all of the operations we would want to perform should be done in a scenario, and I assume separate smallish tests for each aspect of that are acceptable.18:33
jamielennoxdolphm: that would indicate scenario is not a good fit18:33
shardyayoung: http://docs.openstack.org/developer/tempest/field_guide/scenario.html18:33
shardy#link http://docs.openstack.org/developer/tempest/field_guide/scenario.html18:33
dolphmi don't think this has been mentioned yet, but all of test_keystoneclient (and all the git checkout business) is basically testing v2.0, which we're also now deprecating...18:33
ayoungwe fall more under this http://docs.openstack.org/developer/tempest/field_guide/cli.html18:34
dstanekshardy: excellent link thanks18:34
bknudsonit might take us so long to get the tests to tempest that they'll be deprecated by then!18:34
dolphmso, maybe only focus on porting authentication tests (things testing /v2.0/tokens and /v2.0/tenants stuff)18:34
ayoungor this http://docs.openstack.org/developer/tempest/field_guide/api.html18:35
ayoungexplicitly not scenario tests. Otherwise we are hiding what we are trying to do.18:35
bknudsontempest thinks that "api" is "REST API"18:35
*** n0ano has quit IRC18:35
ayoungbknudson, yes, we are scope creeping tempest here18:35
ayoungwe have stated that all along18:35
ayoungbut the client API is a contract that we need to be held to as much as the remote HTTP API18:36
dolphmayoung: ++ today we're testing those in one suite for v2.0 ... we could break them apart into separate tests18:36
* shardy has to go18:36
ayoungshardy, thanks18:36
bknudsonmy latest request in my tempest patch was if we could get it in the python API tests that shardy proposed and is -2d18:37
*** shardy is now known as shardy_afk18:37
ayoungdolphm, lets follow the guidelines for the API tests, then18:37
jamielennoxayoung: ++,  i think we should be arguing for a new folder for client tests18:37
* dolphm shardy sponsored by Fiber One® Breakfast Cereal, Fiber Bars & Healthy Yogurt18:37
jamielennoxand encouraging other clients to do the same18:37
ayoungjamielennox, so that should probably be a Tempest Blueprint18:37
bknudsonthere is one for keystone...18:38
jamielennoxayoung: yea18:38
*** dolphm_ has joined #openstack-meeting18:38
*** adalbas has joined #openstack-meeting18:38
bknudson#link https://blueprints.launchpad.net/tempest/+spec/keystoneclient-api18:38
ayoungbut it sounds like Monty is cranking on just that already, wonder if he has a bp he is working from?18:38
jamielennoxbut at least reading through the field guide we'll be really struggling to get included in any of those groups18:38
topolo/  Showing up way late18:38
dstanekthere seems to be a big gap between cli tests and api tests...does tempest already have a bp to address this?18:39
*** nachi has joined #openstack-meeting18:39
dolphm#link https://review.openstack.org/#/c/41931/18:39
dolphmbug 93969918:39
uvirtbotLaunchpad bug 939699 in openstack-ci "client lib integration tests should hit multiple branches" [High,In progress] https://launchpad.net/bugs/93969918:39
jamielennoxdstanek: not sure about tempest and the blueprint but it doesn't surprise me, there has been an attitude that the CLI is the important part of a client18:39
bknudsonI'm not sure I totally follow the link between what infra is doing and how that matches with what keystone's client tests are doing.18:40
bknudsonbut infra team seems to think it's "equivalent"18:40
bknudsonor adequate, or more correct.18:40
dolphmbknudson: infra is most interested in matrix testing supported client and server versions18:40
*** dolphm_ has quit IRC18:40
bknudsonthey also are the ones who are asking for it to be in tempest...18:41
dolphmbknudson: whether that's CLI or python lib, i don't think tempest really cares18:41
* gyee sees business opportunity for OpenStack certification test suite :)18:41
ayounggyee, it will be called Tempest18:42
gyeeoh damn18:42
jamielennoxgyee: i'm pretty sure they are doing that18:42
bknudsongyee: I think the board or foundation is considering doing that... calling it "core" openstack18:42
dolphmgyee: you're a year late :P http://www.rackspace.com/blog/newsarticles/rackspace-launches-certification-program-for-openstack/18:42
jamielennoxcan't remember what it is called18:42
dolphmoh, the TC wants to use tempest to certify clouds.. yeah18:42
*** Alexei_987 has quit IRC18:43
bknudsonhttp://robhirschfeld.com/2013/07/22/kicking-off-core/18:43
gyeeexcellent!18:43
gyeeso yeah, client tests are the acid tests18:43
jamielennoxgyee: http://refstack.org/18:43
bknudsontempest is not doing much python API testing at this point... the scenario tests do use the python API18:44
bknudson(v2 for keystoneclient)18:44
*** loq_mac has quit IRC18:44
bknudsonI haven't looked at the cli tests to know what they cover for keystoneclient18:44
dolphmjamielennox: that website needs some grammar help18:44
dstanekso what do we need to do about this - propose a blueprint for real client tests instead of the cli tests?18:44
bknudsonI think we have a blueprint -- https://blueprints.launchpad.net/tempest/+spec/keystoneclient-api18:45
bknudsonagain, thanks to shardy_afk !18:45
*** krotscheck has joined #openstack-meeting18:45
dolphmbknudson: ++18:45
jamielennoxdstanek: i think so, but from the list and from those bugs we should coordinate with monty and see whether we can just piggyback that effort18:45
bknudsonI'll try to engage the tempest team more and see if they agree with the bp.18:47
*** jcooley_ has joined #openstack-meeting18:47
dstanekjust to summarize our goal - we want to test the matrix of all supported keystone client versions against all supported keystone server versions...is that right?18:47
*** galstrom is now known as galstrom_zzz18:47
dolphmdstanek: yes18:47
*** MarkAtwood has quit IRC18:47
bknudsonthe supported keystone client versions are apparently 0.1.1, essex-3, and master18:47
dstanekbknudson: if you can keep me in the loop here because i am heavily interested in this topic18:47
topolbknudson how did you determine that?18:48
dolphmbknudson: that's debatable18:48
jamielennoxbknudson: i don't think that is really the case18:48
dolphmtopol: that's what we have in test_keystoneclient18:48
dolphmbut we should really have 0.2.x tests, 0.3.x tests, and now 0.4.x tests18:48
jamielennoxbknudson: i'd like to see 0.2.2, 0.3.x and an 0.4.018:48
jamielennox+ master18:48
dolphmand master18:48
*** kevinconway has quit IRC18:48
bknudsonI could make that change to test_keystoneclient first.18:49
*** jcooley_ has quit IRC18:49
bknudson(or somebody else could)18:49
*** MarkAtwood has joined #openstack-meeting18:49
dolphmbknudson: there's already a patch in review to drop essex-318:49
*** jcooley_ has joined #openstack-meeting18:49
jamielennoxanyone know what was special about 0.1.1?18:50
dolphmjamielennox: it was released18:50
gyee:)18:50
dstanekbknudson: i can change test_keystoneclient18:50
bknudsondstanek: thanks!18:50
*** jeckersb is now known as jeckersb_gone18:50
bknudsonI'm guessing everything since 0.1.1 was put into the "master" testcase18:50
bknudsonso it will require some work to figure out where each test works18:51
bknudsonmaybe just throw them all into compat and skip them18:51
jamielennoxbknudson: is it worth fixing test_keystoneclient? why don't we just start again in tempest, and do it how they want it18:51
dolphmbknudson: well, you'll see them fail, and we can review the skips in gerrit to make sure they're legit18:51
dolphmerr, intended18:52
dolphmjamielennox: this bit of work has to be done either way18:52
*** jlibosva has quit IRC18:52
*** ihrachyska has quit IRC18:52
dolphmjamielennox: coverage can be ported piece by piece once we have something organized enough to port18:52
bknudsonI think it will be easier and better to get our own house in order before having to go through a different set of reviewers18:52
*** jcooley_ has quit IRC18:53
dstanekwhat i had a hard time grokking in tempest was how it would run using different client versions and not pulling them from git18:53
*** rakhmerov has quit IRC18:53
bknudsondstanek: I don't know how that's going to happen either... that was my comment earlier about not seeing the link.18:53
bknudsoncan the tests in tempest know what version of keystoneclient they're using and skip tests?18:54
*** jcooley_ has joined #openstack-meeting18:54
gyeedstanek, how does grenade test upgrades?18:54
* dolphm 5 minutesish18:54
bknudson(also, maybe that's a better way to write the client tests in keystone18:54
jamielennoxdolphm: wouldn't mind a quick chat on backwards compat in client18:55
dstanekbknudson: maybe we just need to have a quick chat with some tempest folks to really hash out what we are trying to do18:55
bknudsongyee: I started looking at grenade but didn't have enough time to figure it out.18:55
jamielennoxi put up a auth plugin WIP https://review.openstack.org/#/c/6075118:55
gyeejamielennox, good stuff18:55
*** galstrom_zzz is now known as galstrom18:55
bknudsondstanek: I assume they have a meeting like ours18:55
jamielennoxis it appropriate to say if you pass a session object to a client then you are using the *new way* and that you should not expect the previous behaviours to apply?18:55
dstanekgyee: grenade test upgrades?18:55
dolphmjamielennox: yes18:55
dolphmjamielennox: that's backwards-compatible18:55
gyeedstanek, that's my understanding18:55
ayoung5 minutes left18:55
*** anniec has quit IRC18:56
jamielennoxdolphm: it turns testing into a bit of a mess18:56
dstanekbknudson: would it be https://wiki.openstack.org/wiki/Meetings/QATeamMeeting?18:56
*** salv-orlando has joined #openstack-meeting18:56
dolphmjamielennox: you could also just have a new constructor18:56
gyeeI would like to re-introduce pagination if y'all don't mind18:56
bknudsonok, I think we've got a TODO for dstanek and I to talk to tempest and try to make progress.18:56
gyeepagination never got killed and we need it18:56
dolphmgyee: i didn't follow up on the pagination discussion at the summit, other than knowing everyone went into it despising pagination18:57
jamielennoxdolphm: ie don't use v3.client.Client ?18:57
dolphmjamielennox: right18:57
bknudsondstanek: we'll have no idea when they meet because they have different times depending on the week!18:57
dolphmjamielennox: that's why I was suggesting keystoneclient.Client()18:57
gyeedolphm, that session didn't happen and we need some pagination18:57
gyeeI would like to re-introduce the ones we had originally18:57
*** gokrokve_ has quit IRC18:57
gyeepage,per_page as the minimum18:57
jamielennoxdolphm: i've been hoping to make keystoneclient.Client() the discoverable entry point18:57
*** markmc has joined #openstack-meeting18:57
*** gokrokve has joined #openstack-meeting18:58
dolphmgyee: we talked about supporting hard limits in conf... is that all you want?18:58
jamielennoxdolphm: but as that is a new feature as well maybe it can be rolled into one18:58
*** vedlad has quit IRC18:58
dolphmjamielennox: ++18:58
gyeedolphm, not so much about implementation, we need to get it back onto the API spec first18:58
dolphmgyee: the configuration approach does not impact API18:58
gyeewe removed them from the spec18:58
dolphmgyee: the spec still supports paginated links -- we're just not using them18:59
gyeeI mean page and per_page is not on the API spec currently18:59
gyeedolphm, as list filters18:59
bknudsonI think I removed them from the spec because they weren't implemented18:59
gyeei.e. GET /v3/projects?page=518:59
bknudsonand I didn't see them being implemented18:59
gyeebknudson, it is implemented in common controller18:59
*** anniec has joined #openstack-meeting18:59
dolphmgyee: hardly18:59
bknudsonthe implementation in common controller was "return"19:00
gyeedolphm, I can finish up the implementation19:00
gyeethe bare minimum19:00
dolphmgyee: we can talk about hard limits in conf first, which was the actual deployer ask19:00
dolphm#endmeeting19:00
*** dolphm is now known as dolphm_19:00
dolphm_#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Dec 10 19:00:52 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
ayoungdolphm, any idea on how much lodging will run in San Antonio?19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-12-10-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-12-10-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-12-10-18.02.log.html19:00
*** dolphm_ is now known as dolphm19:01
*** jamielennox has left #openstack-meeting19:01
*** tristanC has left #openstack-meeting19:01
dolphmayoung: my next step is to find out if i can get ya'll discounts19:01
clarkbo/19:01
fungiheyo19:02
*** gokrokve has quit IRC19:02
ayoungdolphm, at  1 Fanatical Pl, Windcrest, TX ‎ right19:02
*** jcooley_ has quit IRC19:02
*** marekd is now known as marekd|away19:02
jeblairmordred, hub_cap, pleia2, SergeyLukjanov: ping19:02
mordredo/19:02
SergeyLukjanovo/19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Dec 10 19:02:59 2013 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
lifelesso/19:03
*** troytoman is now known as troytoman-away19:03
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:03
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-03-19.02.html19:03
jeblair#topic Actions from last meeting19:03
*** openstack changes topic to "Actions from last meeting (Meeting topic: infra)"19:03
jeblair#action jeblair file bug about cleaning up gerrit-trigger-plugin19:04
jeblair#action jeblair move tarballs.o.o and include 50gb space for heat/trove images19:04
jeblairfungi: do you think it's safe for me to do that ^ now?19:04
*** jlibosva has joined #openstack-meeting19:04
*** nachi has left #openstack-meeting19:04
SergeyLukjanovwhisper: and for savanna images too, please19:04
fungimmm, well we have space on logs and on docs-draft19:04
pleia2o/19:04
*** esker has joined #openstack-meeting19:04
*** ihrachyska has joined #openstack-meeting19:04
*** ArthurBerezin has joined #openstack-meeting19:05
fungiand the /srv/static partition itself is 100g mostly empty19:05
jeblairfungi: i'd probably make a 200g volume for it19:05
*** ArthurBerezin has left #openstack-meeting19:05
*** thomasbiege has quit IRC19:05
jeblairfungi: current real tarball usage is 30g19:05
*** MaxV has quit IRC19:05
*** troytoman-away is now known as troytoman19:05
fungibut no available extents in the vg, and no ability to add any more cinder volumes (we ended up needing 10tib to get the two volumes to 50% freeish)19:05
fungiunless we request a quota bump19:06
jeblairfungi: okay, so we need to ask rackspace for a quota increase19:06
fungii can open a case asking about it19:06
zaroo/19:06
mordredwe could add a second server19:06
*** MaxV has joined #openstack-meeting19:06
anteayao/19:06
mordredthat has volumes onto which we publish build artifacts19:06
fungimordred: well, the 10tib quota limit is tenant-wide according to their faq19:06
mordredoh. ok19:06
mordredI grok now - nevermind19:06
jeblairmordred: but we may also need to do that.19:06
mordredI was somehow thinking it was how many we can attach to one thing19:07
*** Abhishek_ has quit IRC19:07
fungi#action fungi ask rackspace for cinder quota increase19:07
clarkbright beacuse there is a 16 device limit as well19:07
jeblairmordred: if the 10tib limit is increased, we'll be able to put 14tib on one server19:07
fungiyep19:07
mordredk19:07
*** jcooley_ has joined #openstack-meeting19:07
jeblairfungi grow logs and docs-draft volumes so they're 50% full19:07
fungi#link http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=717&rra_id=all19:08
fungi#link http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=718&rra_id=all19:08
jeblair^ i think we just covered that; anything else, fungi ?19:08
fungi#link https://review.openstack.org/#/c/46099/19:08
fungi(the doc update associated with it)19:08
jeblairfungi: that link isn't right19:08
fungigah19:08
fungi#link https://review.openstack.org/#/c/59615/19:09
clarkbthough there is an interesting discussion under 46099 :)19:09
fungias for the graphs, nothing exciting, just don't look too closely at where i accidentally stuck the extra space on docs-draft at first and had to rsync the contents over and back during the course of the weekend19:09
fungiclarkb: yeah, the comments at the end of 46099 are part of my to do list for today, which is why the mispaste19:10
*** fabiog has quit IRC19:10
*** pabelanger has joined #openstack-meeting19:10
*** sarob has quit IRC19:11
*** MaxV has quit IRC19:11
*** brich1 has quit IRC19:11
*** sarob has joined #openstack-meeting19:11
jeblaircool.  the rest of the action items will fall into other topics19:11
jeblair#topic Trove testing (mordred, hub_cap)19:11
*** openstack changes topic to "Trove testing (mordred, hub_cap) (Meeting topic: infra)"19:11
jeblairmordred to harrass hub_cap until he's writen the tempest patches19:11
fungithough in the rsync'ing, i learned that the jenkins scp publisher will annihilate any symlinks it finds in the destination path19:11
jeblairmordred: ^ how's the harrassing going?19:12
mordredjeblair: I believe he started doing that?19:12
mordredhub_cap: ^^ ?19:12
hub_caphey19:12
hub_capi havent been harassed enough19:13
*** salv-orlando has quit IRC19:13
hub_capalthough i think that slicknik is going ot start some of the work. hes getting our dib elements out of trove-integration19:13
*** saurabh_ has quit IRC19:13
hub_capso i suspect he will begin taking my place for this stuff19:13
mordredok. I'll harrass him then19:13
*** jcoufal has joined #openstack-meeting19:13
mordredI thought you started work on it? or was that just savana?19:14
*** henrynash has quit IRC19:14
hub_capi didnt get anything tangible done19:14
hub_capill be working w/ him on it so ill be sure to pass on what i have19:14
anteayaI seem to excel at harrassing for tempest, did you want me to add that to my list?19:15
*** adalbas has quit IRC19:15
anteayawhy should I just bug neutron?19:15
hub_capoh and we have someone from mirantis working on actual tempest tests too19:15
hub_capanteaya: hehe sure :)19:15
*** jhenner has quit IRC19:15
SergeyLukjanovhub_cap, are there any work started on automating image building?19:15
SergeyLukjanovand publishing them to tarballs.o.o?19:15
hub_caphey SergeyLukjanov ive passed the buck to slicknik19:16
*** sarob has quit IRC19:16
hub_caphes moving our dib elements and then i suspect he will work on that19:16
SergeyLukjanovhub_cap, hey :) ok, I'll ping him to sync our efforts19:16
SergeyLukjanovhub_cap, thx19:16
devanandahub_cap: who @ mirantis?19:16
devanandahub_cap: two folks there also working on ironic/tempest too19:17
jeblairhub_cap: do you expect this to be done by icehouse-2?19:17
hub_capdevananda: i cannot remember his name, he just started19:17
hub_capjeblair: its currently targeted for i219:17
hub_capdevananda: he just started working w/ us, ill find out his name and ping u19:17
* mordred loves piles of russians19:18
*** troytoman is now known as troytoman-away19:18
*** jcooley_ has quit IRC19:18
anteayawould it be worthwhile to have a gathering of folks working on tempest tests from various projects19:18
anteayay'know to compare notes19:18
clarkbanteaya: maybe push them to the qa channel and open up dialogue? I am not really sure how much of this is happening outside of bubbles19:19
devanandai think it would benefit us if the mirantis folks who are starting to work on ironic/tempest tests to talk/meet with infra folks19:19
devanandaand have been pushing them that way19:19
anteayaright, fairly bubbly right now19:19
hub_capclarkb: the rainbows are pretty inside our bubbles though19:19
*** salv-orlando has joined #openstack-meeting19:19
anteayaI'll host a meeting and post to the ml19:20
*** weshay has quit IRC19:20
anteayaand hope lots of interested folks show up19:20
anteayahow's that?19:20
clarkbwfm, though in general I think people just need to learn to lurk in the right places :)19:20
anteayayes19:20
anteayahard to keep up on all the backscroll though19:20
*** romcheg has joined #openstack-meeting19:21
anteayaI'm having a hard time19:21
anteayaanyway19:21
jeblairyou don't have to read all the backscroll19:21
zaroclean slate for me everyday..19:21
pleia2zaro: hehe19:21
jeblairanteaya: before you host a meeting about tempest; you might want to talk to sdague.19:21
clarkb++19:21
anteayajeblair: yes, good point19:22
jeblairanyway, this is off-topic.19:22
anteayawill do so19:22
jeblair#topic Tripleo testing (lifeless, pleia2)19:22
*** openstack changes topic to "Tripleo testing (lifeless, pleia2) (Meeting topic: infra)"19:22
lifelesshi, perfect timing, we're going to collide :)19:22
lifelessone sec19:22
pleia2hah19:22
fungiany way to temporarily merge two channels? ;)19:22
*** akuznetsov has quit IRC19:23
clarkbfungi: we could have a bot mirror discussion19:23
fungiindeed19:23
clarkbI am sure that is a terrible idea19:23
lifelessok so19:23
*** henrynash has joined #openstack-meeting19:23
lifelesspleia2: you should talk ;)19:23
*** rpodolyaka1 has joined #openstack-meeting19:23
*** jistr has joined #openstack-meeting19:23
pleia2so I've been cleaning up some tripleo scripts so they can be used in the more automated CI stuff19:23
pleia2it's also led to some changes in devstack.sh so we can properly support the testing infrastructure (and of course this makes sense in general too)19:24
*** saurabh_ has joined #openstack-meeting19:24
*** RajeshMohan has quit IRC19:24
*** jprovazn has joined #openstack-meeting19:24
*** rakhmerov has joined #openstack-meeting19:24
*** ccrouch has joined #openstack-meeting19:24
*** RajeshMohan has joined #openstack-meeting19:24
pleia2derekh and dprince have been working on gearman setup and lifeless has been tackling some of the gnarly network bits19:24
*** akuznetsov has joined #openstack-meeting19:24
lifelessyah, the network config is validated now, we know it will work19:24
pleia2progress is still being tracked on https://etherpad.openstack.org/p/tripleo-test-cluster19:25
pleia2I think derekh and dprince will need an infra chat in the near future19:25
* dprince can't wait19:26
dprince:)19:26
*** mordred has quit IRC19:26
*** mordred has joined #openstack-meeting19:26
pleia2dprince: want to pencil something in with jeblair this week? thinking an asterisk call19:26
jeblairwhat's the topic?19:26
*** ivar-lazzaro has quit IRC19:26
*** viktors1 has joined #openstack-meeting19:26
dprincepleia2/jeblair: we can but derekh will definately want to be on this one too19:27
lifelesso/19:27
pleia2dprince: you can fill in jeblair of specifics better than I19:27
*** anniec has quit IRC19:27
dprincejeblair: topic would be 'TripleO CI: where the rubber meets the road'19:28
dprincejeblair: hows that sound?19:28
pleia2I think he means specifically what we need from infra :)19:28
mordredI love rubber and roads19:28
pleia2mordred: no you don't, you're always in airplanes19:28
*** anniec has joined #openstack-meeting19:29
clarkbpleia2: dprince: right, what exactly do we plan on going over19:29
lifelessI don't think a call it needed19:29
lifelesswe have very clear guidance from infra about the contract and interactions, and we aren't ready to move from experimental to check yet.19:29
mordredpleia2: doesn't mean I don't love them19:29
pleia2mordred :)19:29
dprinceyeah, I'm not sure it is 100% needed either but it wouldn't hurt to get everyone on the same page19:29
*** Mandell has joined #openstack-meeting19:29
*** AaronGr has joined #openstack-meeting19:29
dprincebut we can probably punt on it for this week at least19:30
jeblairdprince, pleia2: is there anything infra-related that's blocking your work?19:30
lifelessdprince: I think we are: jeblair has been through the design and code reviewed the broker, for instance.19:30
jeblairdprince, pleia2: and do you expect to be making infra changes soon related to it?19:30
*** ayoung is now known as ayoung_BeatNavy19:30
pleia2jeblair: no blockers yet19:30
dprincejeblair: on the HP tripleO side no. On the RedHat TripleO side maybe. But it is still premature to go there I think.19:31
*** weshay has joined #openstack-meeting19:31
* dprince aludes to his problem with getting IPv4 addresses for a TripleO testing rack19:31
*** jcoufal has quit IRC19:31
*** mrunge has quit IRC19:31
clarkbI don't think we need IPv419:32
jeblairclarkb: does hpcloud support v6?19:32
*** jcoufal has joined #openstack-meeting19:32
*** jlibosva has quit IRC19:32
clarkbjeblair: no, but hpcloud is only running slaves19:32
mordredjeblair: the tripleo rack has v619:32
lifelessthe infra control plane is dual stack; for tripleo regions we specify that either we need a /25 or we need IPv619:32
fungimight be interesting to find out what sorts of breakage we hit with ipv6-only slaves19:32
*** ayoung_BeatNavy is now known as ayoung19:33
jeblairdprince: can you get v4 for the infra control plane?19:33
dprincejeblair: I haven't got a hard number yet. Maybe.19:33
lifelessjeblair: what's the 'infra control plane' in a slave only cloud ?19:33
*** gothicmindfood has joined #openstack-meeting19:34
fungii would be slightly more comfortable with the ipv6-only idea if rackspace didn't have known brokenness with ipv6 in some ways (particularly dscp marking for low latency communications)19:34
lifelessjeblair: if there is infra work needed to support a v6 slave only region, as long as its reasonably modest, I think TripleO will be happy to step up and do it.19:34
jeblairlifeless: i assumed you meant the part of the system that talks to infra tools;19:34
*** salv-orlando has quit IRC19:34
lifelessjeblair: I meant zuul and nodepool which AIUI run in rackspace19:34
*** sushils has joined #openstack-meeting19:35
lifelessjeblair: we specifically will not have enough ipv4 in many regions to use one ipv4 address per jenkins slave19:35
lifelessjeblair: some proposed regions - like MS - have already told use they simply cannot do IPv4 at all.19:35
lifelessjeblair: so, I'd like to frame this as - what work do we need to do to enable ipv6 only slave clouds19:35
jeblairlifeless: okay, then yes, zuul, nodepool, gear, gearman-plugin will all need to be made to be dual-stack19:35
lifelessif you can point us at the work, we can make sure its in our plan to do it19:36
*** eharney has quit IRC19:36
lifelessjeblair: should we take this offline to do details?19:37
jeblairit's possible some of those may already be; but they are all untested with v619:37
lifelessthat was the bit I was missing19:37
jeblairnodepool will definitely need some work, but it's moderate19:37
*** markvan_ has joined #openstack-meeting19:37
jeblairgear may need a small amount or none but is untested19:37
jeblairunsure about gearman-plugin and its java gearman dependency19:38
*** markvan has quit IRC19:38
lifelessdprince: / pleia2: Can one of you capture the list zuul, nodepool, gear, gearman-plugin and the status jeblair is uttering now into a new etherpad? Called 'ipv6-infra-test-clouds' or something ?19:38
mordredlifeless, jeblair do they need gearman-plugin to be ipv6?19:39
pleia2lifeless: on it19:39
jeblairzuul may not be an issue.19:39
lifelessyou need anything that talks to jenkins slaves or to the API endpoint19:39
mordredkk.19:39
*** eharney has joined #openstack-meeting19:39
dprincelifeless: sure19:39
pleia2https://etherpad.openstack.org/p/ipv6-infra-test-clouds19:39
dprincepleia2: thanks19:39
jeblairthe job runners are jenkins slaves, right?  (they talk to the broker to then farm out the work)19:40
*** AaronGr is now known as AaronGr_afk19:40
jeblairiirc, the jenkins slaves are spun up as normal by nodepool from an openstack vm cloud19:41
jeblairmordred: so i think that's why ^19:41
pleia2right19:41
*** novas0x2a|laptop has joined #openstack-meeting19:41
mordredriht. but then they're not running gearman plugin - they just need ipv6 on the ssh connection from jenkins and from nodepool to their cloud - gearman to jenkins stays in our cloud19:42
jeblairlifeless: i will be happy to see v6-enabling work happen on these.  i would personally love everything we do to be on v619:42
mordred++19:42
fungihear hear19:42
jeblairmordred: good point, zuul only talks to the gearman master19:43
lifelessjeblair: they are, they are already defined in nodepool infact19:43
jeblairmordred: good point, zuul only talks to the jenkins master19:43
lifelessjeblair: we're using the term tripleo-gate for them, a-la devstack-gate19:43
*** lbragstad has quit IRC19:44
*** morazi has joined #openstack-meeting19:44
jeblairmordred, lifeless: if the jenkins master can use a v4 address, then you don't need to worry about gearman-plugin.  if the jenkins master is v6 only, then it does need to be considered.19:44
jeblairand i suppose we are running the jenkins master.  :)19:44
lifelessyou're running the master19:45
jeblairmordred: so yes, i think we can strike gearman-plugin from that list.19:45
lifelessthe interface is exactly the same as for d-g19:45
lifelessnodepool makes a node, hands it to jenkins, jenkins ssh's to it19:45
lifelessso I would expect the list to be nodepool and jenkins19:45
lifelessdoes gear talk directly to slaves?19:46
jeblairlifeless: no, gear interactions are only zuul <-> jenkins master19:46
lifelessok19:46
lifelessso , I tink we we need to timebox this19:46
fungijeblair: though does that change with jenkinsless slaves?19:46
lifelessotherwise both meetings will run out of steam19:47
jeblairlifeless: i updated the etherpad.19:47
mordredthen it would just need turbohipster to be able to do v619:47
lifelesslets pick up ipv6 discussion in a couple of weeks19:47
jeblairlifeless: sounds good, thanks19:47
*** IlyaE has joined #openstack-meeting19:47
fungigreat planning progress tho19:47
lifelessit's not front line yet - the RH region will be the second one to come online, and the HP does have ipv4.19:47
jeblairfungi: yes, in the future, non-jenkins slaves will talk directly to gearman, but they'll do it with gear, so presumably the problem will be solved by then.19:48
jeblair(talk directly to zuul's gearman server)19:48
jeblairthis is why we have these meetings.  :)19:49
jeblair#topic Savanna testing (SergeyLukjanov)19:49
*** openstack changes topic to "Savanna testing (SergeyLukjanov) (Meeting topic: infra)"19:49
jeblairSergeyLukjanov: how's it going?19:49
SergeyLukjanovI've finalized savanna-devstack integration to be able to use it in d-g jobs last week19:49
SergeyLukjanovand create some small patches for tempest to make simple savanna api tests19:50
SergeyLukjanovhere are the CRs for it - https://review.openstack.org/#/q/topic:savanna-tempest,n,z19:50
*** lbragstad has joined #openstack-meeting19:50
SergeyLukjanovthe next step will be impl api tests for all resources19:50
SergeyLukjanovand then to start moving integration tests19:50
SergeyLukjanovfrom savanna repo to tempest scenarios19:51
SergeyLukjanovand we'll need to build/publish images for it19:51
*** spzala has quit IRC19:51
SergeyLukjanovthere are no blockers atm19:51
*** lexx has quit IRC19:51
jeblaircool!19:51
SergeyLukjanovthat's about enabling savanna d-g jobs for exp pipeline in tempest19:52
jeblairzaro: what's the most urgent thing you want to discuss?19:52
SergeyLukjanovfor testing patches19:52
zaroupgrade gerrit i guess19:52
jeblair#topic Upgrade gerrit (zaro)19:52
*** openstack changes topic to "Upgrade gerrit (zaro) (Meeting topic: infra)"19:52
SergeyLukjanovhttps://review.openstack.org/#/c/61125/19:52
zarofungi ran a manually upgrade of review-dev from 2.4.x to 2.8.19:52
fungiwell, it's still in progress there19:53
jeblairSergeyLukjanov: i should be able to review that today19:53
zaroThere was an error during the db schema conversion which is probably a bug in gerrit that isn't handling some badness in the db correctly  #link http://paste.openstack.org/show/5474319:53
*** gokrokve has joined #openstack-meeting19:53
SergeyLukjanovjeblair, great, thank you!19:53
zaroWe will need to debug further.19:53
zaroIt will take a little effort to debug because i would need to setup mysql and get the review-dev site and db dump from fungi.19:53
*** jcooley_ has joined #openstack-meeting19:53
zaroI suggested that in parallel to debugging the problem we should manually run a quick upgrade test against review to see if we get any errors.19:53
*** viktors1 has quit IRC19:54
zaroI think we'll need to do that anyway.19:54
fungiif there is a pressing need to have review-dev back on 2.4.x in the interim, we can revert the upgrade (warfile url change) and i can restore the db from teh backup i've been using19:54
jeblairzaro, fungi: keep in mind we had horrible id sync scripts running on both servers19:54
jeblairzaro, fungi: some cleanup happened to the prod db that may not have happened to the dev one19:54
mordredgood call. I think testing a review db dump before upgrading is important19:54
clarkb++19:54
fungijeblair: yes, dupes there spring to mind as one possibility19:54
jeblairzaro, fungi: so, yeah, testing db dumps from both servers sounds like a very good idea19:54
fungii think there will be multiple tests of each before we're satisfied19:55
jeblairzaro, fungi: and also, it's possible we can fix this with further db cleanup.19:55
clarkbI think we should also convert the tables to utf8 in this process or at least test the conversion19:55
jeblairzaro, fungi: (just something to keep in mind)19:55
clarkbsince we will have to setup all the machinery anyways19:55
zarojeblair: good idea.  db cleanup.19:55
clarkbhttps://bugs.launchpad.net/openstack-ci/+bug/979227 is the bug tracking that problem19:55
uvirtbotLaunchpad bug 979227 in openstack-ci "convert gerrit's mysql tables to utf8" [Medium,Triaged]19:55
zarook, nothing else about gerrit upgrade atm.19:56
mordredI support the upgrade19:56
fungii'd like to discuss potentially getting zaro's ssh key added to review-dev so i don't have to worry about getting db exports and file archives to him out of band19:56
*** jvrbanac has joined #openstack-meeting19:56
zarofungi: what?  i like the personal touch.19:56
fungizaro: yeah, i know. i have that way with people19:57
*** weshay has quit IRC19:57
* zaro nods19:57
jeblairfungi: it looks like review-dev has completely segregated credentials (ie, not the same as review)19:57
* mordred is now left with the words fungi zaro and personal touch19:57
*** olaph has joined #openstack-meeting19:57
*** markpeek has quit IRC19:57
* fungi nods19:57
clarkbjeblair: I think that is true since it replicates to a different github org19:57
jeblairfungi: given that, i am in favor.19:57
mordred++19:57
clarkbme too19:57
*** gokrokve has quit IRC19:57
*** rakhmerov has quit IRC19:58
fungiokay, zaro we'll get that taken care of to help speed this along19:58
zarocool19:58
jeblairzaro: propose a change to infra/config to add your key and add it to the review-dev server, and make sure you read and agree to http://ci.openstack.org/sysadmin.html#ssh-access19:59
zarowill do.19:59
jeblairthat's it; thanks everyone.  we'll get to other topics next week.20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Dec 10 20:00:04 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-10-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-10-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-10-19.02.log.html20:00
ttxOK... who is around for the TC meeting ?20:00
devananda\o20:00
mordredo/20:00
annegentleholla20:00
vishyo/20:00
jraimI'm here for Barbican if needed20:00
ttxrussellb, markmc, mikal, jgriffith, markmcclain, jeblair, lifeless, sdague, dhellmann : around ?20:00
markmchey20:00
russellbo/20:00
lifelessheyo20:00
ttxjraim: thanks for being here, i'm sure there will be questions20:01
jeblairttx: o/20:01
ttxThats's 7+, we can proceed20:01
ttx#startmeeting tc20:01
*** olaph has left #openstack-meeting20:01
openstackMeeting started Tue Dec 10 20:01:23 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** jbryce has joined #openstack-meeting20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
sdagueo/20:01
ttxOur agenda for today:20:01
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:01
*** dieseldoug has joined #openstack-meeting20:01
ttx#topic Assert control over website and memberdata systems20:02
*** openstack changes topic to "Assert control over website and memberdata systems (Meeting topic: tc)"20:02
ttx#link https://review.openstack.org/#/c/58072/20:02
ttxmordred: did you post a thread about that anywhere, yet ?20:02
ttxI guess we can still discuss it...20:02
sdaguemikal raises a good point that there hasn't been a recent thread on that20:02
mordredttx: I did not.20:02
*** ccrouch has left #openstack-meeting20:02
ttxsdague: that prevents us from closing the vote, but not from having a discussion about it20:02
sdaguettx: I got in a twitter fight about it, but I don't think that counts :)20:02
*** MaxV has joined #openstack-meeting20:02
annegentlemordred: is there discussion elsewhere? heh sdague oh I'll look for that one then20:03
mordredsdague: :)20:03
ttxmordred: care to summarize the issue ?20:03
*** pabelanger has left #openstack-meeting20:03
mordredthe issues is - the website and the membership system are run by thefoundation and not part of infra at all20:03
mordredthat means that there are, effectively, project resources which are not under our technical governance20:03
mordredwhich I think is unacceptable20:04
*** marekd|away is now known as marekd20:04
*** lsell has joined #openstack-meeting20:04
jbrycemordred: there is a distinction between project resources and foundation resources20:04
*** jcooley_ has quit IRC20:04
mordredjbryce: is the foundation membership system required to check in code?20:04
jbrycemordred: and they actually have different requirements that come into play20:04
mordredjbryce: because if it is, it should be under the governance of the project20:05
lifelessjbryce: is there? When I read the charter as a result of that motion being put up, I didn't see one.20:05
jbrycemordred: if that's the biggest issue maybe we could get some help on the review to get the id system moved into infra20:05
jbrycemordred: https://review.openstack.org/#/c/53644/1820:05
mordredjbryce: we're going to be on that right after this :)20:05
lifelessjbryce: the foundation is the seat of everything, and then the subsection labelled 'technical' is carved off, lock stock and barrel.20:05
jeblairjbryce: that change is merged.  and it had SO MUCH HELP.20:05
mordredjbryce: the other thing is - the source code that runs the website, and I don't mean the content in the website20:05
jeblairjbryce: i would call that a triumph of community development process.  :)20:05
*** jmontemayor_ has joined #openstack-meeting20:06
mordredshould be open source and in infra20:06
jeblairjbryce: i think everything should be run that way20:06
jbrycejeblair: run which way?20:06
mordredwe have one of the best dev systems in the world, that is one of the most openly collaborative20:06
mordredwe should use it for development20:06
ttxmordred: while I think it would be better if it was open source and under infra, I don't think anything forces them to be20:06
jeblairjbryce: the direction the id system is heading.20:06
jgriffitho/20:07
*** jcoufal has quit IRC20:07
mordredttx: 'technical governance of the project' - I'm pretty sure that source code running the project's website meets that definition20:07
mordredunless we're saying that the website is the website of the foudation20:07
jeblairttx: i agree with mordred's reading of the bylaws20:08
lifelesshow is the foundation distinct from the project?20:08
jbrycemordred: there is actually utility for both the project and the foundation in having some distinction between the resources20:08
ttxmordred: I think that's jbryce's argument ("foundation website")20:08
*** rfolco has quit IRC20:08
*** jmontemayor has quit IRC20:08
jeblairjbryce: is openstack.org not the web site for the openstack project?20:08
* russellb has a hard time understanding why anyone would *not* want infra running all this stuff20:08
mordredrussellb: ++20:08
ttxmordred: anyway, i would rather have those resources voluntarily placed under infra/TC than being forced to20:09
mordredttx: I would to20:09
mordredtoo20:09
jbrycerussellb: it's not that we don't want it running in one way or another20:09
jeblairttx: me too, and i thought we had come to an agreement about that > 1 year ago20:09
sdaguerussellb: yeh, that's the camp I'm in as well20:09
*** rpodolyaka1 has left #openstack-meeting20:09
mordredalso, I'd like it if the website wasn't running on a proprietary system, but instead ran on openstack20:09
mordredBUT20:09
*** weshay has joined #openstack-meeting20:09
jbrycethe teams working on it have been moving that direction over time20:09
mordredI'm willing to defer even talking about that20:09
jbryceand the id portion is a very big piece of the member system that they are attempting to split out completely in the new model20:10
*** anniec has quit IRC20:10
*** jcooley_ has joined #openstack-meeting20:10
jbrycerunning in infra and through gerrit from the get go20:10
*** NikitaKonovalov has quit IRC20:10
russellbawesome20:10
mordredthat's awesome, honestly.20:10
ttxjbryce: ignoring what the bylaws may or may not say on the topic, would you agree that those should be placed under infra program ?20:10
mordredI just don't understand why the existing git repos can't be moved20:10
*** lsell has quit IRC20:10
*** lsell has joined #openstack-meeting20:11
markmcif we can agree that moving this stuff under infra would be good for its own sake20:11
markmcthen it would be awesome to avoid a bylaws debate :)20:11
mordred++20:11
*** mrunge has joined #openstack-meeting20:11
ttxI'd rather not have the TC asserting its understanding of the bylaws tp force the hand of anyone20:11
*** jcooley_ has quit IRC20:11
ttxto*20:11
ttxand have people voluntarily converge20:12
jeblairttx: i think that would be swell20:12
*** denis_makogon has joined #openstack-meeting20:12
*** pdmars has joined #openstack-meeting20:12
ttxso is it a problem of the migration not going fast enough, or the idea of migration being completely refused ?20:12
jbrycettx: that's what i was just going to ask20:13
mordredI'd say it's going so slow as to amount to being politely refused20:13
*** jcooley_ has joined #openstack-meeting20:13
mordredit's been a year since we started discussing it20:13
mordredmoving a git repo without making any other changes at all to deployment20:13
* ttx feels like an arbitrator now20:13
mordredtakes about 30 minutes20:13
mordredif that happened, then sdague could submit a patch when he notices a problem with the profile page, and everyone is happy20:14
lifelesshere's what I'd like20:14
ttxjbryce: do you agree with the idea of a migration ? and if yes do you think it could happen faster ?20:14
mordredI ask - because people ask us when stuff goes wrong, because they assume we run it20:14
lifelessif there is consensus that the operation should all be moving to -infra20:15
sdagueI also think things came to a head when openstack.org had a big outage last month20:15
mordredyup20:15
mordredmore than one20:15
*** lblanchard has quit IRC20:15
sdagueand people streamed into -infra asking what was up20:15
ttxlifeless: that's what we must first establish20:15
lifelessthen I'd like there to be - asap - like by next week - a set of bugs in -infra, which when all closed, will mean that all the ops is in -infra20:15
mordredand people pinged us immediately20:15
*** jmontemayor_ has quit IRC20:15
lifelessI don't think we need to talk -at all- about the mechanics of moving20:15
mordredlifeless: agree20:15
lifelessas long as there is consensus that we should, and a public list of what work - so we can see it being burnt down.20:15
*** kevinconway has joined #openstack-meeting20:16
jgriffithsdague: sorry... wrong number20:16
jgriffithsdague: just sayin20:16
*** jcooley_ has quit IRC20:16
lifelessttx: I bring this up because the discussion is getting into implementation.20:16
jgriffithsdague: people "ask infra" is not a good reason IMO20:16
jbrycettx: in general terms yes, but again there are many additional restrictions on foundation resources than on the project resources20:16
lifelessttx: and since mordred has agreed, we can now focus back on the broad consensus question20:16
lifelessjbryce: can you clarify what that even means?20:16
mordredjbryce: like what, if I may ask?20:16
russellbjbryce: can you elaborate a little?20:17
russellbheh20:17
mordredjinx20:17
lifelessjbryce: because I don't understand the distinction you're drawing; the technical subpart of the project is in the bylaws20:17
* markmc had same typed too :)20:17
*** jhenner has joined #openstack-meeting20:17
jbrycethe website/member system/foundation database are basically all in a single datastore currently20:17
lifelessjbryce: so, the first thing I want to understand, is what is a 'foundation resource' vs a 'project resource'20:17
jbrycethis is what the team is working on breaking into separate pieces20:17
jbryceindividual members are legally members of the foundation20:18
lifelessjbryce: thats interesting work, but I don't understand the relevance to the broad discussion, probably because I don't understand the distinction again.20:18
jbryceATCs are a subset of that20:18
mordredjbryce: right. but we're not suggesting moving the operation of that data store - just the source code20:18
mordredI would personally rather not have access to that database20:18
jbrycethere are contractual and legal requirements about access and control of the data and the systems that have access the data20:18
ttxjbryce: if mordred were to rasie a thread about this on -infra or -dev, would you be willing to publicly map the remaining tasks to complete to migrate the stuff ? Then we can understand the steps and check progress...20:19
lifelessmordred: I think you're jumping ahead of the discussion - and I'm 100% sure you know a lot more about the plumbing than the rest of us; could you perhaps let us learn :)20:19
mordredI'm not20:19
mordredthis is where the confusion lies20:19
mordredI'm NOT saying that we should take over operatoin of all of the things that have potential legal ramifications20:19
*** jcooley_ has joined #openstack-meeting20:19
lifelessmordred: you are saying that 'The management of the technical matters relating to the OpenStack Project shall be managed by the Technical Committee. ' applies20:20
mordredlifeless: ok. fair20:20
lifelessthat this is a technical matter, which we should be managing20:20
* mordred shuts up - passes mic back to jbryce20:20
lifelessrunning ops of a secure database with legal ramifications is a supremely technical matter20:20
jbrycelifeless: is a sponsorship contract between a corporation and the foundation a matter of the project?20:20
lifelessthat it needs to be only accessed by specific personal due to legal issues is a huge and important constraint20:20
lifelessso in order for me to say 'hey, mordred, I agree with you', I think we need to understand why some bits count as 'technical' and others don't20:21
mordredlifeless: right. and to be clear - I thnk it's not that the bits are technical - I think it's key that some of them are technical parts of the project20:22
mordredI do agree with jbryce that there are potentially technical bits that are not part of the project20:22
jbrycelifeless: or a proprietary operations data a user has submitted under the condition that it only be shared with the foundation20:22
jbrycemordred: i think that's a key distinction20:22
jbryceto take a step back20:22
*** gothicmindfood has quit IRC20:22
jbrycei don't think any of us is against the idea of moving repos to follow the standard contribution process20:22
lifelessjbryce: I don't know! This is why I'm asking these 'please define stuff for me' questions!20:22
jbrycewe are not against running resources on -infra resources where possible20:23
lifelessbecause it's not clear to me why a git repo for running a foundation-but-not-project website would be a technical matter for the project20:23
lifelessBUT20:23
lifelessthe ops of said website wouldn't be20:23
lifelessthere's no bright line I can see [yet] that delineates one but not the other20:23
mordredI think ultimately, once the legal bits are segregated, that there is no difference20:24
ttxmordred/jbryce: I think the main issue is the absence of roadmap -- it's difficult to comment on how fast we go (or how blocked we are) if you don't even agree on the list of work items20:24
lifelesspart of that is that I don't actually understand the difference between 'the foundation' and the 'project' except that the foundation exists to nurture the project20:24
mordredttx: ++20:25
markmcttx, yep20:25
ttxmordred/jbryce: so to move on, I'd like you two to participate in an open ML thread on the topic20:25
mordredttx: ok. shall I start that?20:25
*** jistr has quit IRC20:25
ttxmordred/jbryce: see if we can converge at least on the list of steps and the limits20:25
lifelessIn principle, could infra run the website and delegate back to *only foundation staff* all potential access to the legally sensitive bits?20:25
markmcand maybe rather than debate the meta issues in the thread20:25
ttxmarkmc: yes20:26
markmcfocus more on what systems could next move to infra20:26
markmcand what one's can't20:26
lifelessif so, I could see an easy line of 'it's technical -> infra' but also 'this is legal -> only foundation staff touch'20:26
jeblairif incidental access to a sensitive database was required for infra-root, i'm sure we'd be willing to accomodate legal and technical requriements.  we already maintain high standards of access to systems that we run.20:26
mordredwell - yes - there is one thing though ... I _do_ at some point want to establish, possibly in this thread20:26
mordredwhich bits are actually under the governance of the TC and which bits are not20:26
ttxbecause I think I agree with both of you I think. It should be infra/open source wherever it can20:26
jbrycei do have a problem with a broad assertion about tc oversight in anything that could be classified as "technical" and is necessary for the operations of the foundation. so i think the scope issue is very important20:26
lifelessjbryce: would that sort of chain work for the foundation, from a legal perspective?20:26
mordredroadmap for implementation of getting them pysically controlled stems from that20:26
jeblairlifeless: in other words, to your suggestion: possibly; but i'd like to explore the idea of a flat structure because i think it could work.20:26
*** hnarkaytis has quit IRC20:26
jgriffithjbryce: I think I'm with you on that20:27
mordredbecause I do not believe we are in agreement on that point yet20:27
ttxjbryce: yes, I think we have to recognize that the Foundation is different from the Open source project20:27
lifelessjbryce: I want to understand the scope issue too ;)20:27
mordredjbryce: exactly20:27
lifelessjbryce: to be clear, I don't have a specific axe to grind here, I'm doing my best to understand it all :)20:27
markmcjbryce, right, I'm saying if we all put that assertion aside for a while we might make more concrete progress20:27
mordredjbryce: I _don't_ think we have oversight of all things technical that the foundation might do20:27
*** dieseldoug has quit IRC20:27
mordredI'd like to figure out which ones we do have oversight of though20:27
jbrycemordred: ok. let's work on that20:28
lifelessmordred: I'd like to figure out a rule for figuring them out ;)20:28
*** ywu has quit IRC20:28
ttxok, let's move on20:28
mordredjbryce: ++20:28
lifelessif possible20:28
ttx#action mordred to start public thread on that20:28
ttx#topic Barbican incubation request (initial discussion)20:28
*** openstack changes topic to "Barbican incubation request (initial discussion) (Meeting topic: tc)"20:28
*** lsell has left #openstack-meeting20:28
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/020830.html20:28
ttx#link https://wiki.openstack.org/wiki/Barbican20:29
* ttx can stop juggling with his hats20:29
ttxAs usual we'll do this over two meetings20:29
ttxThe first one we'll discuss and raise the main objections, so that the Barbican team can address them in new threads20:29
ttxThe second one we'll do the final review and push for votes20:29
*** vipuls is now known as vipuls-away20:30
russellbhm, i seem to recall a bunch more information added to the wiki20:30
russellbwas it a different page?20:30
russellbjraim: ^ ?20:30
russellbscope, mission statement, for example20:30
ttxI looked at this request and I have a number of issues with it20:30
jraimrussellb I added a bunch to the incuation section20:30
jraim#link https://wiki.openstack.org/wiki/Barbican/Incubation20:30
ttxhttps://wiki.openstack.org/wiki/Barbican/Incubation20:30
ttxyep20:30
russellbah yes thanks20:30
jraimI can move it out to the main page if we like it all20:31
ttxMy main objection would be similar to the one we rejected Designate for20:31
*** jcooley_ has quit IRC20:31
ttx68% of commits coming from the same person20:31
ttx96% of commits coming from a single company20:31
ttxwhich makes it a bit brittle20:31
*** jcooley_ has joined #openstack-meeting20:31
ttxif said company or individual were to move on20:31
jraimRack has 3 FT devs, 1 FT test in addition to product / doc writers20:32
jraimWe've had some interest from other groups in contributing20:32
jraimI'm hoping that incubation will help that process along20:32
*** lbragstad has quit IRC20:32
mordredthis is the same chicken and egg problem, tbh20:33
mordredand I think we're going to have to sort it out at some point - it's not going to keep not coming up20:33
ttxjraim: yes, unfortunately we don't have a status for that "attract contributors to this promising thing" state yet20:33
ttxMy plan is to propose one such state very soon20:33
lifelessso we have a new set of guidelines we're working up20:33
ttxBarbican request came before I could20:33
jraimttx understood, but I think we have a strong team working the product now. That should allow us to attract developers over time20:33
lifelesslooks like barbican falls short of them to me20:33
mordredactually, I don't thinkn we need a new one20:34
lifelesslike - no tempest thirdparty tests yet20:34
jraimttx I'd agree with you if there wasn't already a team on it20:34
russellblifeless: a number of them actually20:34
mordredwe take programs without incubating them20:34
mordredtripleo is one20:34
mordredit has projects20:34
sdaguelifeless: it's actually devstack-gate for pre-incubation20:34
mordredif those projects want to be incubated20:34
sdaguetempest comes after20:34
mordredit has to propose them20:34
mordredso I think we have the structure already20:34
lifelessrussellb: a number of requirements; or a number of proposed sets of requirements?20:34
sdaguelifeless: d-g is also missing20:34
mordredwe can accept the program proposal from barbican20:34
ttxmordred: so you think they should apply for a program first ?20:34
lifelesssdague: right, I was using an example :)20:34
russellblifeless: barbican is missing a number of the things we have listed requirements20:35
jraimWe do have a pretty good integration test suite. It uses the CloudCAFE testing framework20:35
mordredwhich would make them 'official' and people could work on them - but the repo barbican is still not incubated even20:35
jeblairjraim: what kind of feedback are you getting from other groups about their interest in barbican?20:35
russellba number in progress already20:35
mordredttx: yes20:35
lifelessrussellb: right - I think we agree :)20:35
sdaguerussellb: I think you did a good job higlithing that in your thread, I see the list of tasks at "Tasks for Incubation" to be pre-incubation requirements20:35
ttxmordred: I have several objections to that...20:35
mordredttx: beeause I think that accepting the program means we agree on the need20:35
russellbsdague: yep20:35
sdagueso it seems premature to be doing this until those are done20:35
*** electrichead has joined #openstack-meeting20:35
jraimjeblair I'm seeing a lot of desire for the features we can help with. e.g projects wanting to provide encryption services20:35
russellbthat's my opinion, yes20:35
russellbwe could give it a "promising" status if we can come up with one though20:35
mordredttx: okj20:35
mordredgah20:35
jeblairjraim: what happens when you ask them to commit resources to it?20:36
*** jcooley_ has quit IRC20:36
ttxmordred: that means they would place themselves under the TC authority even if they get rejected from incubation ?20:36
mordredttx: welcome to the jungle, yeah20:36
*** vahidh has quit IRC20:36
mordredttx: again - tripleo is under tc authority, none of their repos are integrated20:36
mordredor incubated20:36
ttxmordred: trying to wrap my head around it20:36
jraimjeblair We've had good responses (from swift for example) when we asked if they would be interseted in merging encryption patches20:36
markmcwe don't have it listed in our requirements for new programs, but I'm surprised ...20:37
sdaguemordred / ttx : that seems like a meta discussion for another day20:37
jgriffithjraim: what is "good response"?20:37
lifelessintegration is for the integrated release20:37
markmcwould have thought diversity and viability of the new program's team would be just as important20:37
lifelessprograms are for initiatives we see that we need with teams built up around them20:37
ttxmordred: so programs could be about scope and incubation about maturity and integrated scope fit20:37
jraimjgriffith ptl said he would be willing to merge the patches and gave us guidance on what they would need to look like20:37
annegentlejraim: this line of thinking still gets me to barbican being under another umbrella, perhaps a security program20:37
russellbmarkmc: it was in there at one point ..20:37
jgriffithjraim: thanks20:37
lifelessprojects are deliverables of programs20:37
lifelessdevstack isn't integrated20:37
jraimjgriffith We've also seen work from the APL guys on transparent encryption for cinder which seemed reasonably well received20:38
lifelessnor is infra20:38
jgriffithjraim: ;)20:38
jgriffithjraim: I'm vaguely familiar20:38
*** marekd is now known as marekd|away20:38
jgriffithjraim: I assumed Cinder was the primary target here TBH20:38
ttxmordred: I guess approving program but not incubation could be one way out of this maze20:38
*** dieseldoug has joined #openstack-meeting20:38
*** dieseldoug has left #openstack-meeting20:38
jraimjgriffith they are cetainly on the list, though I think the current approach is too limiting (e.g. tagged to libvirt)20:39
*** dieseldoug has joined #openstack-meeting20:39
sdaguejraim: so honestly, using cloudcafe ends up being probably long term problematic because you'll need to convert over to tempest for integration20:39
jeblairttx: 2 things: i think a program needs a diverse team too so may not be a solution; and are we straying from the topic? :)20:39
jraimjgriffith I want to see if we can enable transparent encyrption for all storage on a VM, not just cinder or ephemeral, but both with the same code.20:39
ttxjeblair: ok20:39
jgriffithjraim: we should chat off meeting sometime20:39
ttxLet's discuss scope for a bit20:39
annegentlejraim: I think it's fine you've got a writer started, I want to provide a template approach for other projects who want to plug into openstack docs eventually20:39
russellbjraim: jgriffith probably off topic :)20:39
jraimsdague this seems to be a conversation we have to have. I'm assured that the CloudCAFE tests can be run in the gate. IF that's not true, we obviously have a problem20:40
jraimjgriffith will do20:40
ttxjraim: could you explain where barbican actually stores data ? Swift ? Cinder ? Own data store ?20:40
jgriffithrussellb: and thus my "we should chat off meeting"20:40
sdaguejraim: you have been asured incorrectly20:40
annegentlejraim: what sdague said20:40
jraimannegentle she said she was going to touch base with you, but happy to talk more20:40
russellbjgriffith: yep, latency.20:40
jgriffithrussellb: but tbh the majority of comments of late are "off topic"20:40
jraimttx we store data in our own database. We also allow an optional HSM to be used to secure that data store20:40
mordredjraim: what sdague says is true20:41
ttxjraim: is there any reason to believe the sort of auditable and secured storage features you have in Barbican wouldn't make sense as part of... say... swift ?20:41
jraimsdague than I agree that is a major problem. I agree that our integration test suite must be run as part of the gate. If CloudCAFE won't work, we'll have to move it20:41
mordredjraim: we do testing in openstack with tempest. there is nothing stopping rackspace from running cloudcafe as a third-party thing20:42
markmcjraim, how would you compare Barbican capabilities to similar capabilities offered by existing public clouds (like AWS CloudHSM) ?20:42
*** jprovazn has quit IRC20:42
mordred(or anyone else, for that matter)20:42
jraimttx all projects will expose their own end user services (e.g. encryption, auditing, etc). Barbican offers a way for services to deliver those services in a much easier way20:42
russellbAFAIK, you can't write third-party tempest tests though, can you?20:42
markmcjraim, not so much about quality or anything, but what's Barbican analogous to ?20:42
russellbdoesn't have a plugin mechanism or something20:42
sdaguerussellb: we don't have a stable internals api20:42
sdagueso you could... but it was be rebase chasing20:43
russellbso up and coming projects, for now, have to write an independent suite of some sort20:43
jraimmordred true, but all our integration tests are currently in CloudCAFE. Sounds like we'd need some or all of them in tempest20:43
mordredjraim: ++20:43
lifelessjraim: yes :)20:43
russellbpoint being ... we can't tell people they need to be in tempest20:43
russellbbecause you can't do that20:43
jeblairexcept you can put them in tempest until they are integrated.20:43
sdaguerussellb: so the d-g job idea was to have basic sanity20:43
russellbsdague: right, i get it, and i've been working through it with solum20:44
jraimmarkmc Barbican uses the same HSM that Amazon does. However, amazon is bascially provisioning you a slice of an HSM and allowing direct access. We use an HSM as a backend, but Barbican takes care of multi-tenancy and 'speaking openstack'20:44
sdaguerussellb: I think the line we took in the proposal was "some kind of job" in a d-g env for incubation, then tempest testing for integration20:44
* russellb nods20:44
mordredright. so you could add tests to tempest in incubation, and would need to for graduatoin I think?20:44
jraimmarkmc Barbican is very similar to the software you would find in an HSM, just open-source and free. We do add some features and OpenStack integration, but the API is basically key management and generation20:44
sdaguewhere "for" means prereq of20:44
sdaguenot during20:44
markmcjraim, cool, thanks20:44
mordredsdague: ++20:45
russellbpoint is, tempest won't accept tests pre-incubation AFAIK20:45
mordredsdague: I agree with that20:45
sdaguerussellb: yes, that's true20:45
russellbso it's kind of all mixed up20:45
ttxjraim: thx for the explanation, solves most of my scope concerns20:45
devanandajeblair: *cant* put them in tempest until they are integrated?20:45
russellbbut yes, you can still do a basic devstack-gate job without tempest20:45
russellbdevananda: correct20:45
sdaguerussellb: so honestly.... we have the problem that we have integrated projects that have no tempest testing :)20:45
annegentlejraim: so the user cases are: give me access to my encrypted cinder volume? Or: give me access to the secret that gives me access to the cinder volume?20:45
russellbsdague: *nod*20:45
mordredwait. no. that's not what we just said20:45
jraimSo it seems like we would want to move our basic integration tests over to tempest before graduation. CloudCAFE could still store additional tests as desired?20:46
mordredyou can't put them into tempest until their incubated20:46
mordreds/their/they're/20:46
russellbmordred: that20:46
jraimannegentle Users would access an encrypted volume thorugh cinder20:46
russellband you can't write tempest tests outside of tempest20:46
jraimannegentle cinder would use barbican20:46
sdaguedevananda: what mordred said20:46
devanandasdague: and incubated projects taht want to be tested. but ...20:46
lifelessand this is why I think we need to make tempest have a somewhat stable api20:46
russellbso you just need "something"20:46
* lifeless opens the can of worms20:46
russellbfor incubation IMO20:46
russellblifeless: +120:46
mordredright. so during incubatoin, one is expected to write tempest tests and put them there20:46
devanandawait. now i'm confused20:46
sdaguedevananda: incubated projects are fair game20:46
devanandalol20:46
russellbbut just talking about what we have today20:46
devanandasdague: ack20:46
jraimannegentle users would use barbican directly for auditing, logging or recokation20:46
russellbmordred: yes20:46
lifelessAs it stands, I think cloudcafe is entirely fine for *pre-integration*20:46
lifelesssorry20:47
russellbmordred: or port your stuff to tempest20:47
jraimannegentle customers of an openstack cloud would also use it for secret storage20:47
lifeless*pre-incubation*20:47
jgriffithincubating directory in Tempest... separate tag and gate job (non-voting)20:47
mordredrussellb: ++20:47
lifelessonce the incubation switch is flipped, moving into tempest...20:47
mordredok - we might be going off into the weeds talking about tempets extension mechanisms here20:47
lifelessbecomes a priority20:47
russellbbut hopefully your devstack-gate job runs whatever you *do* have pre-incubation20:47
jgriffithrussellb: or that :)20:47
markmcjraim, do you forsee pretty much all OpenStack services eventually depending on Barbican, sorta similar to how everything depends on Keystone20:47
russellbthat seems reasonable20:47
annegentlejraim: for your scope, do you expect an admin api and auditing capability before "completion"20:47
* markmc notes the current topic is scope of the project, not tempest integration :)20:48
sdagueyeh... we've gone off topic quite a bit20:48
ttxok so to summarize20:48
jraimmarkmc I hope so. Most projects should / want to offer encryption services to customers. I hope that Barbican provides the ability to do that in a way that is secure, auditable and meets compliance requirments20:48
ttxit looks like the scope of the project is well-defined and makes sense20:48
jraimannegentle we have an admin api in the code now, we just haven't put anything in it yet20:48
*** dstanek has quit IRC20:49
ttxthere are some concerns about time size/diversity and some work to be done before filling all the current requirements for incubation20:49
ttxow20:49
ttxs/time/team20:49
lifeless~20:49
markmcjraim, I guess that's implicit in the Future section of your Roadmap? would be good to list out the future potential integration points20:49
jraimmarkmc will do20:50
markmcjraim, excellent20:50
jeblairttx: agreed; my biggest concern is diversity.20:50
ttxI think we can discuss all that this week in the thread and move on to a final decision next meeting20:50
ttxany other concern that was not directly mentioned yet ?20:50
russellbi think you guys have done a great job responding to work items so far, so thanks for that20:50
jeblairjraim: is hardware HSM testing required, or will software only (in the cloud) testing sufficiently test the project?20:50
jraimttx I will reach out to some folks that have expressed interest and see if they can speak up20:50
russellbi'm concerned it probably won't all get done by next week, though20:51
jraimjeblair we offer a 'dev' hsm that is fine for testing in the cloud20:51
russellbso it may be worth talking about the program but not project idea a bit more on list20:51
ttxjraim: I'll explore the idea of applying to become an official "program", before applying for incubation20:51
sdagueyeh, it seems like it might be better to table a vote until after that list got knocked out20:51
jeblairjraim: thanks20:51
russellbttx: +120:51
ttxok let's move on20:51
ttx#topic Incubation / Graduation / New program requirements20:51
*** openstack changes topic to "Incubation / Graduation / New program requirements (Meeting topic: tc)"20:51
ttx#link https://review.openstack.org/#/c/59454/20:52
*** anniec has joined #openstack-meeting20:52
*** gokrokve has joined #openstack-meeting20:52
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/020844.html20:52
russellb#vote yes20:52
ttxI pushed a second version based on early comments.20:52
ttxThe goal is to get to a consensual base version and then address new requirements as incremental change to this (living) document20:52
* devananda perks up20:52
ttxIt will be much easier to review incremental changes after the base one is in20:52
ttxSo please check if there is any rule you disagree strongly with20:52
jeblairttx: +1 thinking about it -- like i said, i'm skeptical; i think a new program should have a diverse team too.  i'm still mentioning this because it's current for this topic as well.  :)20:52
*** hallyn_ has left #openstack-meeting20:52
ttxif you want more in there, propose them as future changes instead of blocking this one20:52
mordred"Project must have a basic devstack-gate job set up"20:53
mordredI do not disagree with the rule20:53
ttxWill approve it once it passes the required number of +120:53
mordredBUT20:53
mordredas we're currently working on the early bits of tripleo-gate too - I think we might want to genercise that sentence?20:53
russellbgate job that runs some sort of functional testing?20:53
lifelesshang on20:53
russellbcan do that as a follow-up change though i think20:53
russellbnot critical20:53
lifelessright now, d-g is the only way things in the *integrated gate* get tested.20:53
mordredyeah. I'm not going to -1 it20:54
lifelessIt's entirely accurate as-is.20:54
mordredyes20:54
*** DennyZhang has joined #openstack-meeting20:54
mordredit's fine to pass20:54
mordredjust being that guy20:54
ttxok20:54
*** rakhmerov has joined #openstack-meeting20:54
lifelessTripleO's deliverables aren't in the integrated gate, nor are they integrated or incubated.20:54
russellband for most projects, something based on devstack-gate is how you'd add functional testing20:54
sdagueyeh, let's clarify in post20:54
lifelessTuskar will be a project that we incubate soonish.20:54
russellb(a bit of a pain to be honest, but doable)20:54
ttxmoving on then :)20:54
lifelessAnd that will either go in d-g, or we'll revisit the language at that time.20:54
ttx#topic Other governance changes in progress20:54
*** openstack changes topic to "Other governance changes in progress (Meeting topic: tc)"20:54
mordredoh - wait20:55
russellbi refuse to wait20:55
ttx#undo20:55
mordreddammit20:55
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3a2ff10>20:55
ttxmordred: yes ?20:55
mordredProject must be compatible with all currently OpenStack-supported versions of python20:55
markmcgood point20:55
jeblairttx that's amazing i've never seen that before.20:55
lifelessI had quibbles with that20:55
ttxright, lifeless didn't like that one that much either20:55
mordredI think that should genericize20:55
lifelessI can live with it, but I don't think it actually captures intent20:55
ttxjeblair: watch and learn20:55
*** troytoman-away is now known as troytoman20:56
*** vuil has quit IRC20:56
mordredbecause aiui, we do not yet have a hard-fast-encoded rule about must be python20:56
lifeless'I think this is trying to say 'must be deployable anywhere current OpenStack can be deployed today' using 'compatible with the Pythons we support' as a proxy - I'd rather we state the thing more directly.'20:56
lifelessIs what I said in review20:56
markmcyeah, something like that works20:56
ttxmordred: how about you propose those in a subsequent change ?20:56
mordredttx: ok. Iwill do that20:56
ttxit's not as if the document was binding us or anything20:56
russellbdeployable where openstack is deployable today would imply no new requirements20:57
russellbwhich isn't terribly realistic :)20:57
markmcnew projects introducing new dependencies is potentially ok, though20:57
russellbmarkmc: jinx20:57
ttxit's more of an hopefully up-to-date matrix to check and communicate to wannabees20:57
markmc:)20:57
mordredmust comply with current TC software policies20:57
markmcwe have those?20:57
lifelessrussellb: huh? no, it says that anyone coming in can't be incompatible with where we support deployments20:57
mordredmarkmc: yah20:57
markmcmordred, documented ? :)20:57
jeblairmordred: all our integrated projects are python, and we have established supported python versions20:57
jgriffitharosen: that was my question too20:57
jeblairi actually don't see a problem with it as written20:57
*** lbragstad has joined #openstack-meeting20:57
ttxlet's get this one in, wil be so much easier to discuss additions one by one after that ;)20:57
jgriffitherr... markmc ^^20:57
mordredttx: ok20:58
ttx#topic Other governance changes in progress20:58
*** openstack changes topic to "Other governance changes in progress (Meeting topic: tc)"20:58
lifelessjeblair: something that doesn't work with the RH patched Python2.6 for instance, would that be a problem?20:58
ttxI approved the Compute program mission statement yesterday as we mentioned it at last meeting and it reached enough approvals20:58
jeblairthese are guidelines; they don't prohibit us from varying from them or accepting non-python projects, which will require some work anyway.20:58
ttxAlphabetize list of extra ATCs: https://review.openstack.org/#/c/58610/20:58
vishyy20:58
lifelessjeblair: even though it does work with vanilla Python2.620:58
jeblairlifeless: it already is.  :)20:58
ttxI think that one shall be abandoned, given that the main use for this list is time-sorted rather than alpha-sorted, and it didn't get that much YESes20:58
lifelessjeblair: I mean, would we reject their incubation on that basis?20:58
markmclifeless, jeblair, that eventlet/subprocess thing is resolved now, btw20:58
lifelessmarkmc: cool20:59
markmclifeless, jeblair, and RH Python maintainers accept it was their screwup20:59
*** bdpayne has quit IRC20:59
ttxwill abandon if it doesn't get enough YES by EOW20:59
ttx#topic Open discussion20:59
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:59
jeblairlifeless: i expect we should have a discussion about it and seriously consider whether to waive the requirement20:59
markwash#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/021233.html20:59
*** bdpayne has joined #openstack-meeting20:59
markwashpotential glance scope adjustment20:59
mordredjeblair: sure. I'm just saying we don't have to duplicate our current policies on that subject20:59
markwashnot sure if of TC interest20:59
mordredjeblair: we can reference them20:59
jeblairlifeless: in that case, i would consider that this list of requirements had the intended effect.20:59
ttxJ naming poll coming up, waiting for the lawyers pass on proposed name20:59
lifelessmarkmc: doit; you don't have enough on your plate atm20:59
ttx(go Jekyll)20:59
lifelessbah20:59
lifelessmarkwash: ^20:59
ttxproposed names*20:59
mordredjekyll++21:00
jgriffithmarkwash: I'm interested :)21:00
lifelessJekyll, indiana?21:00
mordredlifeless: jekyll island, georgia21:00
ttxmarkwash: thanks for the link21:00
lifelessI mean, it has to be Indiana or Idaho right, for crazy names...21:00
jeblairmordred: okay.  :)  it would be good if it pointed to something concrete though, so a new project would know what's expected.  that's what this list accomplishes.21:00
russellbJekyll++21:00
*** NehaV1 has joined #openstack-meeting21:00
mordredjeblair: ++21:00
russellbdone21:00
ttxok, time is up21:00
mordredjeblair: I was really just trying to make sure that if we change them, we don't have to remember to do it in two places21:01
ttx#endmeeting21:01
lifelessmordred: ++21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Dec 10 21:01:13 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-12-10-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-12-10-20.01.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-12-10-20.01.log.html21:01
*** troytoman is now known as troytoman-away21:01
ttxrelease / cross-project meeting now21:01
ttxdims, dolphm, notmyname, jd__, markwash, jgriffith, russellb, stevebaker, david-lyle, markmcclain, hub_cap: around ?21:01
dims\o21:01
david-lyleo/21:01
notmynamehere21:01
markwasho/21:01
russellbohai21:01
hub_caphowdy21:01
jgriffitho/21:02
ttxdims is replacing the traveling dhellmann21:02
*** samcdona has joined #openstack-meeting21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Dec 10 21:02:25 2013 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
openstackThe meeting name has been set to 'project'21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
devananda\o21:02
ttx#topic Swift 1.11.021:02
*** openstack changes topic to "Swift 1.11.0 (Meeting topic: project)"21:02
*** ryanpetrello has quit IRC21:02
ttxWe have a milestone-proposed branch for 1.11.0 set up and if all goes well that should be released on Thursday21:02
ttx#link https://launchpad.net/swift/+milestone/1.11.021:02
ttxnotmyname: still no issue with it yet ?21:03
*** romcheg has quit IRC21:03
notmynamenope. things look good21:03
*** anniec has quit IRC21:03
ttxnotmyname: OK I'll wait for your go-ahead/ping/email to apply tag and upload resulting tarball21:03
*** rakhmerov has quit IRC21:03
notmynamettx: target wed pm or thurs am?21:03
*** ryanpetrello has joined #openstack-meeting21:03
ttxnotmyname: your call, ideally when we are both awake21:04
notmynameok :-)21:04
ttxso your thurs morning / my thursday evening21:04
ttxor you ack on thu evening and I get it tagged on Friday morning21:04
notmynamesounds good to me21:04
ttxnotmyname: anything else on that subject ?21:05
notmynameI don't have anythingon that for this meeting21:05
*** HenryG has quit IRC21:05
ttxok then21:05
ttx#topic Icehouse-221:05
*** openstack changes topic to "Icehouse-2 (Meeting topic: project)"21:05
ttxWe looked into icehouse-2 roadmaps during the 1:1s today21:06
ttxLooks mostly in order21:06
*** dstanek has joined #openstack-meeting21:06
ttxabout 129 tracked blueprints and many many more if you cound Low ones21:06
*** afazekas has quit IRC21:06
*** portante has joined #openstack-meeting21:07
ttxremember icehouse-2 is branched on January 21, tagged on January 2321:07
*** s0mik has quit IRC21:07
ttxany question on that ?21:07
*** AaronGr_afk is now known as AaronGr21:07
russellbhow can we incentivize people to target things realistically, and not just the soonest milestone?21:07
russellba problem i have in nova anyway ... the world is targeted to icehouse-2 right now21:07
russellbwas i1 before21:08
ttxhmm, public shaming when stuff gets deferred ?21:08
russellbjust something to think about, don't have to go into too deep right now ...21:08
russellbheh, perhaps21:08
ttxtar and father ?21:08
ttxfeathers*21:08
russellbset their blueprints on fire?21:08
*** s0mik has joined #openstack-meeting21:08
ttxfrankly, it's a promised delivery date21:08
ttxif you constantly say crap, then you lose credibility21:09
ttxand your blueprints should lose priority as a result21:09
markwashI'm not sure there's always a counterparty to such a promise21:09
russellbi guess it's less of an issue for the Low ones21:09
russellbbut if you get bumped > Low and you miss, it should drop back to Low21:09
*** lblanchard has joined #openstack-meeting21:09
*** fbo is now known as fbo_away21:10
*** atiwari has quit IRC21:10
ttxbut yeah suggestions welcome21:10
russellbthanks21:10
russellbcan move on :)21:10
ttx#topic Storing quotas in keystone21:10
*** openstack changes topic to "Storing quotas in keystone (Meeting topic: project)"21:10
ttxSo there was some controversy around a feature proposed for keystone21:10
ttxAlthough not proposed as blueprint for icehouse, nor discussed in a HK summit session afaict21:10
ttxnotmyname: do you want to try to summarize the concerns ?21:10
ttxdolphm: is that thing even on your roadmap ?21:11
portantettx: can you post the feature description link?21:11
notmynameIIRC from the email thread, the proposal was to add all quotas into keystone (ie keystone as the authoritative place to store quotas for everything in a system)21:11
ttxportante: sure, one sec21:11
*** markmc has quit IRC21:11
*** jbryce has quit IRC21:11
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-December/020799.html21:12
portantettx: thanks21:12
*** julim has quit IRC21:12
notmynamettx: my concern is that I think this is a terrible idea since it makes scaling this store impossible and makes using quota'd systems slow21:12
*** DennyZhang has quit IRC21:13
chmoueli think oleg email is more informative http://lists.openstack.org/pipermail/openstack-dev/2013-December/020981.html than mine21:13
ttxdolphm: you around ?21:13
chmouelnotmyname: afaik from the discussion the keystone quota would push out to swift via a notifcation system21:13
*** DennyZhang has joined #openstack-meeting21:13
russellbi don't think it makes any sense, it's not an identity concern21:13
notmynamettx: and I mentioned it last week to ensure it got cross-project eyes on it so that we go in a direction good for the project overall21:13
dolphmttx: sorry, i'm trying to attend two meetings at once :(21:13
markwashnotmyname: +1 some details have to be denormalized and highly consistent. putting those details (e.g. usage and limit) across service boundaries sounds bad21:13
ttxdolphm: bad idea21:14
ttx<ttx> dolphm: is that thing even on your roadmap ?21:14
notmynamechmouel: and how do you notify changes to 3 million containers?21:14
dolphmcentralized storage of quotas -- yes21:14
russellbon your roadmap?21:14
russellbdolphm: did you get support from any other projects on it?21:14
dolphmrussellb: from the people in whatever session we talked about it in.. about 2 summits ago21:15
ttxdolphm: couldn't find a blueprint21:15
dolphmit's been slow progress since21:15
dolphmttx: one sec21:15
*** radez is now known as radez_g0n321:15
chmouelnotmyname: it's by account I was looking at it not for container quota (which is user based in swift)21:15
ttxdolphm: at least not a icehouse blueprint :)21:15
dolphmhttps://blueprints.launchpad.net/keystone/+spec/domain-quota-management-and-enforcement21:15
dolphmhttps://blueprints.launchpad.net/keystone/+spec/store-quota-data21:15
*** jecarey has quit IRC21:15
ttxhah21:15
russellbi think clear *current* support from other projects should be a pre-req21:15
russellb2 summits ago is like ancient times21:15
dolphmthe second one was a direct result of the summit in SF i believe21:15
dolphmrussellb: ++21:16
ttxdolphm: do you agree with notmyname's scalability concerns ?21:16
chmouelthe etherpad followup in HK  https://etherpad.openstack.org/p/CentralizedQuotas21:16
dolphmthe direction from the summit was centralized management & peristence of domain- and project-based quotas, but maintain decentralized reservations and enforcement21:16
russellbjust doesn't seem to make sense why that's centralized, but nothing else is21:17
russellbkeystone shouldn't be trying to solve openstack-wide administration usability21:17
ttxis there a benefit ?21:17
*** jeckersb_gone is now known as jeckersb21:18
dolphmttx: of course; the suggested answer was that services should pull the latest quotas when necessary, and then subscribe for notifications of updates21:18
ttxsounds a bit outside of "identity" to me21:18
annegentlehow would domain and project quotas map to swift?21:18
russellbttx: +121:18
ttxdolphm: ok21:18
dolphmannegentle: domain-based quotas wouldn't, i don't think21:18
chmouelbut project would do i believe21:18
annegentlechmouel: ok21:18
*** ctracey|away is now known as ctracey21:19
*** vipuls-away is now known as vipuls21:19
ttxdolphm: the way it stands I fear tat there will be quotas in keystone but all the projects would keep their own21:19
ttxwhich makes the benefits of "centralized quotas" (if any), even more dubious21:19
markwashI think we just shouldn't confuse central administration with central storage21:20
notmynamedolphm: chmouel: they both may and may not map to swift. depends on the implementation of the cluster. identity is decoupled from resources in swift, so can be mapped by whatever application is using them21:20
*** terriyu has quit IRC21:20
*** otherwiseguy has quit IRC21:20
ttxso without buy-in from at least one consuming project there is little point in implementing that in keystone21:20
ttxyou could even argue that's out of keystone scope21:21
dolphmin terms of roadmap in keystone, i see this as purely an extension at the moment, and it's not blocking any other work at the moment, at least in keystone.21:21
comstudit feels like centralized quotas will be difficult to keep accurate (in sync)21:21
comstudbut even if we did them, I don't feel like keystone is the correct place for them21:21
comstudIMO21:21
dolphmcomstud: where would you suggest?21:21
russellbdolphm: but who wants to use the extension?21:21
notmynamecomstud: cache invalidation being a hard problem? :-)21:21
dolphmit sounds like a standalone service to me21:21
*** dieseldoug has quit IRC21:21
notmynamedolphm: quotas-as-a-service?21:22
*** topol has quit IRC21:22
*** galstrom is now known as galstrom_zzz21:22
ttxare decentralized quotas actually bad ? What problem are we trying to solve here ?21:22
comstudMy current suggestion is keeping them within each project :)21:22
russellbquotas-as-a-lib > quotas-as-a-service IMO21:22
ttx+1 to both21:22
comstudrussellb: +221:22
hub_capquotas lib is necessary21:22
notmynamecomstud: which AFAIK is where they are now (and working already)21:22
morganfainbergrussellb, ++, putting on my deployer hat i don't want a quota-service21:22
russellbright21:22
comstudcorrect21:22
notmynamewhat is even in a quotas lib?21:23
morganfainbergrussellb, well a service for the sake of being a service, not that it couldn't exist in something already there.21:23
russellbnotmyname: just some shared code21:23
russellbi think we even have some of it in oslo-incubator right?21:23
ttxdolphm: so in summary I feel like this is a feature without a user, so at best a waste of time, at worse an unwarranted keystone scope extension...21:23
dolphmttx: i don't disagree!21:24
ttxdolphm: heh21:24
russellbyes, quota.py in oslo-incubator21:24
dolphmi haven't spent much of my own time on it :P21:24
russellbdolphm: so, save us from spending time arguing against it then?21:24
russellb:)21:24
ttxdolphm: I hope this discussion will give you more grounds to reject the feature if it gets proposed21:25
russellbi thought dolphm said earlier it was on the roadmap for icehouse21:25
dolphmrussellb: if other projects aren't clearly interested, i'll happily push back21:25
russellbok21:25
dolphmrussellb: it is currently, but it's not blocking21:25
ttxhttps://blueprints.launchpad.net/keystone/+spec/domain-quota-management-and-enforcement is in21:25
chmoueldolphm: +1 if no others are interested21:25
dolphmrussellb: keystone itself isn't the stakeholder21:25
russellbwho is?21:25
russellbhonestly this is all about saving you (keystone) some time21:26
dolphmrussellb: appreciated :)21:26
russellband from ending up with a confusing mixed state of affairs come icehouse21:26
dolphmuntargeting now21:26
russellbok21:26
comstudrussellb: just say 'nova is not interested in a centralized quota service' ;)21:26
ttxsounds good, moving on ?21:26
comstudheheh21:26
russellbcomstud: well swift started it, i just piled on :-)21:27
ttx#topic Red Flag District / Blocked / Interlocked blueprints21:27
*** openstack changes topic to "Red Flag District / Blocked / Interlocked blueprints (Meeting topic: project)"21:27
comstud:)21:27
ttxNo blocked blueprint afaict21:27
russellbyay21:27
ttxThat said there are a few cross-project dependencies prio mismatch we need to discuss21:27
ttxhorizon/ceilometer-api-enhancements (Medium, lsmola, icehouse-2) depends on:21:27
ttxceilometer/statistics-order-by-and-limit-for-grouped-query (Undefined, No assignee, next)21:27
ttxjd__, david-lyle ?21:28
*** lexx has joined #openstack-meeting21:28
* jd__ listening21:28
ttxIf that's a true dep we might need to raise prio/targeting of the Ceilo blueprint21:28
ttxif that one doesn't get done maybe the horizon plan should be anadoned21:28
ttxabandoned*21:28
jd__I can change the prio and target it, but if nobody is assigned to it, it won't be done21:28
ttxjd__: no point in targeting it if nobody does it21:29
jd__my point (pun intended)21:29
david-lyleI think it is a partial dependency21:29
david-lyleWe may be able to achieve sections of the bp without this particular ceilometer bp21:29
*** jcooley_ has joined #openstack-meeting21:30
*** colinmcn_ has quit IRC21:30
*** colinmcnamara has quit IRC21:30
david-lyleI'll work with lsmola to resolve if no one picks up the dependency21:30
ttxdavid-lyle: so I'd split the blueprint in two, one part depending and the other not, and target the second part to "next"21:30
david-lylettx: will do21:30
ttxthat way the i2 work doesn't depend on something nobody is working on (yet)21:30
*** neelashah1 has joined #openstack-meeting21:30
ttxlsmola said that complex-filter-expressions-in-api-queries might actually solve the requirement though21:30
ttxso maybe it's just about replacing the depend to point to that instead21:31
ttxOK, the other one is:21:31
ttxheat/management-api (High, andersonvom, icehouse-2) depends on:21:31
ttxkeystone/service-scoped-role-definition (Undefined, arvind-tiwari, No milestone)21:31
*** neelashah has quit IRC21:32
ttxsame thing, if it's a true depend it's unlikely to be doable if the keystone BP itself is not in icehouse21:32
ttxstevebaker, dolphm: ?21:32
*** otherwiseguy has joined #openstack-meeting21:32
stevebakerdolphm: could this please be evaluated for approval? https://blueprints.launchpad.net/keystone/+spec/service-scoped-role-definition21:32
*** herndon has quit IRC21:33
stevebakerdolphm: we have a High icehouse-2 blueprint depending on it, so one way or another the blueprints will need to be aligned21:33
ttxstevebaker: ideally Arvind Tiwari would target the appropriate milestone21:33
*** sayali has joined #openstack-meeting21:33
* ttx reads heat/management-api waiting for dolphm21:35
ttxhttps://blueprints.launchpad.net/heat/+spec/management-api21:35
*** anniec has joined #openstack-meeting21:36
ttxstevebaker: any idea if Arvind is likely to deliver that ? i.e. is it more of a resource assignment problem, or a BP acceptation problem ?21:36
*** neelashah has joined #openstack-meeting21:36
david-lylespoke with Arvind re: this bp, he is working to get the bp accepted21:37
*** neelashah1 has quit IRC21:37
stevebakeractually I think it may not be a hard dependency, management-api could move to using service-scoped-roles after it lands21:37
ttxdavid-lyle: you should ask Arvind to set the milestone21:37
ttxdavid-lyle: it won't get on dolph's radar until he does21:37
david-lylettx: ack21:38
stevebakerI'll check with shardy_afk to see how hard the dep is21:38
ttxSo... Arvind targets milestone, Dolph to review/aprove it, stevebaker to check if the BP could be split between one part depending and the other not depending on that21:38
ttxand we'll review the blocker again next week21:39
ttxstevebaker: works for you ? Looks like we lost dolphm21:39
stevebakerlgtm21:39
dolphmttx: stevebaker: david-lyle: apologies! i'll have to read back later, and follow up21:39
russellbdolphm: this meeting is better21:39
ttxdolphm: moving on read backlog and let us know if proposed plan looks good21:40
ttx#topic Incubated projects21:40
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:40
ttxwho do we have21:40
devananda\o21:41
ttxSergeyLukjanov ?21:41
SergeyLukjanovo/21:41
ttxI don't think I see kurt_griffiths21:41
ttxSo quick release integration status update21:41
ttxdevananda: Ironic got a tag for icehouse-121:42
russellbnick is currently kgriffs_afk21:42
devanandattx: indeed - thanks!21:42
ttxdevananda: do you feel you're ready to switch to a milestone-proposed branch and tarball model for i2 ?21:42
*** flaper87|afk is now known as flaper8721:42
ttxi.e. will have a usable deliverable by then ?21:42
ttxto summarize, the milestone-proposed branch model is:21:43
devanandafor some definition of "usable deliverable" - yes :)21:43
ttxon the Tuesday/Wednesday to create a branch from master pointing to the proposed milestone SHA21:43
ttxyou can backport stuff to the branch for a couple days if really needed (like the tarball is unusable)21:43
devanandabut yes, I think we'll have the essential bits working, and I would like to go through the process at i221:44
ttxthen on Thursday/Friday I tag the HEAD of milestone-proposed21:44
*** DrBacchus has quit IRC21:44
devanandaAIUI, we dont need Nova integration at this stage (though there's a chance we'll have that, too)21:44
ttxthat generates a tarball, which is uploaded on Launchpad milestone page21:44
ttx(and signed)21:44
*** ohnoimdead has joined #openstack-meeting21:44
ttxdevananda: ok, so we'll try the switch for i221:44
devanandayea, all of that ^ would be great to do, so that downstream folks can consume it and start testing / giving us feedback21:45
ttxSergeyLukjanov: Savanna did the full MP dance / tarball thing for I1, so you're ready21:45
ttxwe'll do the same for I221:45
SergeyLukjanovttx, yup21:45
ttxNo news from Marconi21:45
* ttx should more formally encourage kgriffs to join us here21:46
SergeyLukjanovttx, and it was done by you, so, the correct process was ensured ;)21:46
ttxdevananda, SergeyLukjanov: any question on release management integration ?21:46
SergeyLukjanovttx, nope21:46
devanandajust one, slightly tangential21:46
devanandaany guidelines on a numbering scheme for client releases? I knkow they're not coordinated...21:47
*** dprince has quit IRC21:47
markwashsemantic versioning?21:47
ttxMost libs do major.minor.patch21:47
ttxwhat markwash said21:47
devanandacool. thanks21:47
ttxdevananda, SergeyLukjanov: how are the other parts of your incubation going so far ?21:47
ttxlike QA/docs21:48
devanandattx: just had some lengthy discussions with tempest folks about ironic getting in there21:48
devanandait's on track21:48
ttxok21:48
SergeyLukjanovttx, the first version of heat integration will be landed soon21:48
devanandahttps://review.openstack.org/#/c/48109/8 and https://review.openstack.org/#/c/53917/821:48
ttxSergeyLukjanov: sounds good21:48
notmynamedevananda: http://www.python.org/dev/peps/pep-0440/21:48
devanandaand there's an ML thread on it now, as well. so we should see that land soon21:48
annegentleSergeyLukjanov: ttx: I do have an action item to write up some guidelines for writing pluggable docs21:48
SergeyLukjanovttx, first patches for tempest was created to add api tests21:48
annegentlethat should help incubating projects write docs that are easily placed in our existing titles21:49
devanandattx: as for docs, we auto generate both API and developer docs at this point. and i am planning to start working on deployer docs closer to the end of the cycle21:49
*** boris-42 has quit IRC21:49
ttxSergeyLukjanov, devananda: you might be interested in https://review.openstack.org/#/c/59454/ to see TC requirements for incubation and graduation21:49
SergeyLukjanovannegentle, cool21:49
devanandaannegentle: it would be good for us to talk at some point about adding ironic as we look at applying for graduation21:50
SergeyLukjanovttx, I've already placed some comments and monitoring changes21:50
devanandattx: looked at that when it came up in the TC meeting21:50
ttxSergeyLukjanov: ok21:50
devanandattx: i think we will meet nearly all of taht already, except for # of core reviewers (we have 4 today)21:50
ttxit's a living document, trying to represent what the TC is likely to apply as rules21:50
SergeyLukjanovttx, as for the docs, we have http://docs.openstack.org/developer/savanna/ with all docs including different guides and api descriptions21:50
ttxok21:50
annegentledevananda: yeah, the docs team would prefer to not add a new title this release, but next release, revise the install guide.21:51
ttxlet's move on to open discussion, feel free to continue to ask questions21:51
*** jooools has joined #openstack-meeting21:51
ttx#topic Open discussion21:51
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:51
annegentledevananda: so you're on the radar but not this release, if that makes sense21:51
annegentle\o21:51
SergeyLukjanovttx, I'd like to return back this month to discuss the more detailed list of requirements for savanna to graduate21:51
devanandaannegentle: interesting. how does that work - let's assume we graduate, but are not in the docs?21:51
annegentledevananda: docs team mission is to document core21:52
ttxSergeyLukjanov: raising a thread on the ML about that would be appropriate21:52
*** jdob has quit IRC21:52
annegentledevananda: we are so underresourced we have to draw a line, but we want to work with teams21:52
SergeyLukjanovttx, ok21:52
annegentledevananda: to get more docs. heat and ceilometer got some docs in, for example21:52
ttxSergeyLukjanov: just make sure the TC members are aware of the thread (posting a link to the -dev discussion on the -tc list is ok)21:52
ttxPTLs: By popular demand I'll probably switch our 1:1s to a specific (logged) channel, like #openstack-relmgr-office or something21:52
devanandaannegentle: understood about resource shortage ... any suggestions on what we can do in the absence of having docs in the official docs?21:52
SergeyLukjanovttx, you've answered my next question :)21:52
ttxPeople want to be able to conveniently access 1:1s content, without having to filter noise from #openstack-dev channel logs21:52
*** anniec has quit IRC21:53
devanandaannegentle: ah. so it's fine for us to contribute docs then?21:53
ttxrussellb: ^21:53
russellbttx: neat21:53
annegentledevananda: we want them to plug in to specific titles we already have. What I'm saying is that for icehouse I'm not sure we have a pluggable model for you...21:53
annegentledevananda: probably over explaining, but tripleo won't get much from the doc team during icehouse21:54
ttxanything else, anyone ?21:54
annegentleme me!21:54
annegentlepick me!21:54
* russellb imagines annegentle jumping up and down raising her hand21:54
ttxannegentle: this is open discussion, feel free to speak :)21:54
annegentleWe have four interns starting next week with the GNOME Outreach Program for Women21:54
annegentle#link https://wiki.gnome.org/OutreachProgramForWomen/2013/DecemberMarch21:54
russellbawesome21:54
ttxwe as in openstack ? or docs ?21:54
devanandaannegentle: hmm, let's chat a bit after the meeting. i may be able to toss some resource your way, but if there's no where to plug the documentation in, then i'm not sure what to do (besides a wiki page)21:55
annegentleDec. 10 is their start date21:55
ttxnice21:55
russellb2 docs 2 horizon looks like?21:55
annegentlettx: details are in that link but there is one for API docs, two working on Horizon, one for Marconi21:55
*** jeckersb is now known as jeckersb_gone21:55
russellbMarconi one sounded like a doc thing i guess?21:56
annegentlerussellb: yeah the Marconi one is more or less doc but mentored by a marconi dev21:56
ttxannegentle: yep, saw that on link21:56
russellbcool21:56
russellbthanks for coordinating, very cool program.21:56
*** jooools has quit IRC21:56
annegentleI need to write a blog post21:56
annegentlerussellb: thanks!21:56
annegentlehappy for HP to step in to fund some extras after the first round of funding, that was cool21:56
annegentleRackspace, the OpenStack Foundation, and HP (plus GNOME) are making it all happen21:56
ttxany other good news ?21:57
annegentlettx: 15 days until Christmas?21:57
annegentle:)21:57
ttxtrue. Hope you've been nice.21:57
russellbindeed ... and i'm taking a week off from christmas to new years21:57
annegentlealways21:58
russellbbecause i have to ... but it should be nice.21:58
ttxmost people do. It's another "recommended off week"21:58
russellb+121:58
*** bdpayne has quit IRC21:58
ttxok then, let's wrap up21:58
ttxthanks everyone21:58
stevebakerI'll be 2 weeks off. its summer here21:58
russellbthanks, ttx!21:58
ttx#endmeeting21:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:58
openstackMeeting ended Tue Dec 10 21:58:47 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-10-21.02.html21:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-10-21.02.txt21:58
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-10-21.02.log.html21:58
*** bdpayne has joined #openstack-meeting21:59
devanandanotmyname: thanks for the pep ref. exactly what i was looking for21:59
*** rakhmerov has joined #openstack-meeting21:59
*** bdehamer has joined #openstack-meeting22:00
*** jcoufal has joined #openstack-meeting22:00
notmynamedevananda: I hope that's the right one. I know there was "a thing" in the python word about it. that's what I could find in the limited time22:00
devanandanotmyname: huh. well, until someone tells me otherwise, it's better than me just making something up based on my own preference/experience22:01
*** Toshi has joined #openstack-meeting22:01
david-lyle#startmeeting Horizon22:01
openstackMeeting started Tue Dec 10 22:01:50 2013 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: Horizon)"22:01
openstackThe meeting name has been set to 'horizon'22:01
*** portante has left #openstack-meeting22:01
jcoufalo/22:02
david-lyleHello Horizon folks!22:02
lsmola_hello22:02
lblanchardhi all!22:02
MaxVo/22:02
jtomasekhi22:02
mrungehello!22:02
bdehamerhi22:02
jomarahowdy22:02
*** pdmars has quit IRC22:02
*** anniec has joined #openstack-meeting22:02
david-lylehttps://wiki.openstack.org/wiki/Meetings/Horizon22:03
ohnoimdeadhi!22:03
david-lyleNo general announcements today22:03
david-lyleso let's jump in22:03
david-lyle#topic Discuss integration of TripleO UI22:04
*** openstack changes topic to "Discuss integration of TripleO UI (Meeting topic: Horizon)"22:04
david-lyleSo this item was added to the agenda based on a mailing list thread22:04
lsmola_david-lyle, so what are the conditions for the merge?22:04
*** jasondotstar has quit IRC22:05
lsmola_david-lyle, given that make sense, cause all UIs belongs in Horizon22:05
david-lyleThe general question posted was would it make more sense for the UI component of Tuskar to merge into the Horizon program rather than the TripleO program22:05
david-lyleI think from a code make-up perspective and an eventual home perspective this makes perfect sense, however..22:06
*** kgriffs has joined #openstack-meeting22:06
jtomaseka note: on the TripleO meeting we agreed that yes.22:06
jpichSo far we've carried UIs in our own tree when a project gets integrated22:06
david-lyleI'm not sure what the organization structure would be22:06
*** colinmcnamara has joined #openstack-meeting22:07
*** colinmcn_ has joined #openstack-meeting22:07
david-lylejpich, to be fair the aims of tuskar UI is much larger than say Trove as far as Horizon is concerned22:07
lsmola_david-lyle, not sure either22:07
kgriffsrussellb: o/22:07
jcoufalI am torn to pieces as well22:07
*** s0mik has quit IRC22:08
jpichIf I understood correctly a big part of Tuskar was a new "Infrastructure" dashboard, at the same level than project and admin? Maybe my information is outdated22:08
mrungeI think it will fit there22:08
david-lyleyes, It's a well populated dashboard22:08
lsmola_david-lyle, well I do see it as separate panel, that just shows when Tuskar is present22:08
lblanchardjpich: that's my understanding22:08
jcoufalat one side it all make sense to be part of UI project22:08
jtomasekjpich: correct22:08
mrungewe have had several requests about adding features, which belong to infrastructure22:09
jpichlblanchard, jtomasek: Thanks!22:09
*** mdurnosvistov has quit IRC22:09
david-lyleI do think it makes sense, but I think it would still have to be a separate code base for now22:09
mrungeso it would make sense for horizon to have it22:09
david-lyleand there will be a need for core-reviewer overlap22:09
*** lexx_ has joined #openstack-meeting22:09
jcoufaldavid-lyle: +122:09
lsmola_david-lyle, so do you mean separate codebase placed under Horizon program?22:09
jtomasekdavid-lyle: +1 if that is not an issue from Horizon point22:09
jpichdavid-lyle: Until when?22:10
david-lylelsmola_: yes, until TripleO/Tuskar is an intergrated part of the release22:10
jcoufalI think this sounds very reasonable22:10
jpichThat makes sense to me22:10
lsmola_david-lyle, I am not really sure how that can be done, but yes that seems to be reasonable22:10
david-lyleThe code base will be what I image it is today, an extension of the current Horizon repo22:10
mrungewe even could add it now or very soon22:10
jcoufal yes please22:11
mrungeand make tuskar a config option22:11
jcoufalthe sooner the better22:11
lsmola_david-lyle, ok22:11
mrungerdopieralski had the plugin concept merged today22:11
*** lexx has quit IRC22:11
lsmola_mrunge, well yeah, we could add it now, and it would stay hidden unless user will have Tuskar22:11
david-lylemrunge, that's right22:11
mrungeand a demo option is about configuring tuskar22:11
lsmola_mrunge, which they wont22:11
mrungeswitch on/off22:12
david-lyleless overhead for the tuskar folks then22:12
mrungeexactly22:12
jomarathat sounds good22:12
david-lyleSo, this jumps topics a bit, but review backlog worries me a lot22:12
david-lyleeven with the current scope22:13
mrungeand we don't get any evil surprises, when tuskar becomes official22:13
david-lyleadding more core-reviewers from tuskar should help, but I think patches are languishing much too long now22:13
lsmola_mrunge, I have to check that plugin patch22:13
mrungeso, david-lyle should we move to topic #2?22:13
mrunge(reviews)22:13
david-lylewell, I think it effects #122:14
mrungeyes, I agree22:14
david-lyleSo let's circle back to #1 in a sec22:14
jtomasekdavid-lyle: I thing good amount of tripleo-core reviewers working on tuskar-ui will jump to Horizon reviews right away (me included)22:14
david-lyle#topic Reviews22:14
*** openstack changes topic to "Reviews (Meeting topic: Horizon)"22:14
mrungethat was brought by me22:14
jpichI would appreciate a general rule from when we accept new components' UI into our tree. We've turned away code before because the project was incubated but not integrated, a clear guideline would help being fair and treating everyone the same way22:15
mrungeand I'm currently concerned about a long review queue22:15
mrungejpich +122:15
*** lexx_ has quit IRC22:15
david-lyleaccording to russell's stats we have:22:15
david-lyleNew patch sets in the last 30 days: 545 (18.2/day)22:15
jpichWe are getting a lot more patches and contributors than before, which also very cool - even if it means reviews are taking longer at the moment (which sucks)22:16
*** DennyZhang has quit IRC22:17
mrungestill I see very few core reviews during the last days22:17
david-lyleyes, which means we need more reviewers, hopefully these new contributors are willing to lend some review time22:17
jpichPersonally I've had less time for reviews since the Summit though I hope to be back to normal in the new year - sorry for not helping picking up much of the slack at the moment22:17
david-lyleI think several new contributors have jumped right in22:17
ohnoimdeadand some old contributors as well :)22:17
mrungebut in general, we'd love to see more folks doing reviews22:18
jpichYep we should definitely encourage people to review :)22:18
lsmola_david-lyle, we have been blessed today to make mor reviews, 6 more people from tuskar should do at least a review per day22:18
david-lyleI think the current review load has no margin of error, that is if a core goes on vacation has a work commitment we fall terribly behind22:19
lsmola_david-lyle, to make things moving :-)22:19
mrungegood news lsmola_22:19
david-lyleso, in that light I would love to see a larger review pool22:19
david-lyles/review/reviewer/22:19
*** s0mik has joined #openstack-meeting22:19
jpichso all the patches are perfect by the time a core reviewer gets to it :-)22:19
lsmola_:-)22:20
mrungeha! I'd love to see it22:20
jpichI believe ;)22:20
*** casanch1 has joined #openstack-meeting22:20
david-lyleSo, to the current tuskar folks, do you worry about the latency for your incubating project?22:20
*** MarkAtwood has quit IRC22:21
david-lyleincubating projects require a faster turn around time then we currently provide22:21
jomarawe do have blazing review turnaround right now22:21
lsmola_david-lyle, yes22:21
jomaraso it is a concern22:21
mrungehow many of you tuskar guys have been core at tripleO?22:21
jcoufalmrunge: for UI?22:21
lblanchardis there something that the tripleo team is doing that speeds up their review time? Or is it simply the number of patches vs. reviewers?22:21
lsmola_david-lyle, we have to make a lot of patches for tuskar-ui and also for horizon in coming months22:21
mrungeyes22:21
lsmola_mrunge, me22:22
jcoufalmrunge: I think 5-622:22
jomarame, jtomasek, lsmola22:22
lsmola_mrunge, jomara, jtomasek22:22
lsmola_hehe22:22
mrungeok, I see.22:22
*** litong has quit IRC22:23
mrungein my eperience, not answering to reviewers requests has been an issue in the past22:23
mrungeesp. from you tuskar guys22:23
david-lylehate to bring this up, but all tuskarUI folks are RedHat?22:23
mrungethat slowed the process down a bit22:23
jcoufaldavid-lyle: that's correct22:23
jomarayeah22:23
lblancharddavid-lyle: yep22:23
jomarajust the tuskar-ui guys, not all tripleo22:23
lsmola_mrunge, tzumainn, lsmola, jtomasek, jomara + non core akrivoka, rdopieralsky22:24
david-lyleI ask merely because we try not to have all 3 people, author, 2 core be from the same company, a working principle in general22:24
david-lyleI'm not sure how that changes for an incubated project22:24
david-lylenot sure that it bothers me either22:24
jpichI think it's a good rule22:25
mrungeI was tuskar core?22:25
jpich*principle22:25
lsmola_mrunge, (though rdopieralsky have kickass python skills, he just came late)22:25
*** markpeek has joined #openstack-meeting22:25
jcoufalmrunge: you don't know about that?22:25
lsmola_mrunge, no the mesage is to you :-)22:25
jcoufal:)22:25
mrungeno22:25
mrungehahaha22:25
jomaramrunge: lsmola_ uses an odd IRC client that puts a comma when he tab completes22:26
jomaramrunge: shame him!22:26
*** dvarga has quit IRC22:26
lsmola_jomara, hehe22:26
ohnoimdead+1 on the general concept of reviews not all coming from the same company for any specific patch (although i must admin nebula has been guilty of that in the past, but it was a smaller project then)22:26
mrunge+1 ohnoimdead22:26
mrungethat's rule I like22:27
jpichAgreed22:27
ohnoimdeadadmin=admit fyi22:27
mrungebut in the past, that has not be a problem22:27
*** lexx has joined #openstack-meeting22:27
*** AaronGr is now known as AaronGr_afk22:27
ohnoimdeadstupid question: where does the tusker-ui code currently live?22:28
*** epim has joined #openstack-meeting22:28
jtomasekohnoimdead: you mean +2 reviews, right?22:28
jomaraseems fair to have at minumum 1/3 of (reviewr1+reviewer2+author) not be from the same company22:28
lsmola_ohnoimdead, as part of tripleo program22:28
ohnoimdeadjtomasek: yeah22:28
*** esker has quit IRC22:28
mrungeohnoimdead, https://github.com/openstack/tuskar-ui/tree/master/tuskar_ui22:28
ohnoimdeadmrunge: thanks!22:28
mrungeif I'm not terribly wrong22:28
lsmola_david-lyle, well that could slow things down in few coming months, though won be a problem later I guess22:29
jomarait will22:29
lsmola_david-lyle, we are currently rebuilding it due to feedback from the conference22:29
david-lyleI think we have some logistics to work out, but I would be in favor of adding tuskar ui22:30
mrungeso, would it be possible for you tuskar guys to make a plan, how the code shall be merged into our code base?22:30
*** ItSANgo has quit IRC22:30
mrunge... just to discuss this at the next meeting?22:30
mrungeis that too quick?22:30
lsmola_mrunge, can we sit on that tomorrow with rdopieralsky, seems like you already have a plan :-)22:30
mrungeI was just thinking about reading a 20k lines of code patch22:31
jpich:|22:31
mrungeand I don't like the idea22:31
david-lylejpich, I think the main difference here between tuskar and other service UIs is that Tuskar is a more fundamental change to the direction of Horizon22:31
lsmola_david-lyle, would it be possible to allow to only Redhat people for the Infrastructure tab?22:31
david-lyleI'd rather not react late to such a scope change22:32
mrungelsmola_, is there a reason for this?22:32
lsmola_david-lyle, before other people will get to pace of what Tuskar-Ui is22:32
ohnoimdeadIsmola_: O.o22:32
david-lylelsmola_: not sure, I think there may need to be some mechanics before the two core teams merge22:32
jpichI think lsmola mean, is it ok if for a while the +2 reviews happen to come from the same company for this specific part of the code22:32
ohnoimdeadah22:33
lsmola_jpich, yes, thank you for rephrasing :-)22:33
*** rakhmerov has quit IRC22:33
mrungethat sounds different22:33
david-lylejpich: that would be fine22:33
mrungeI was worried about prohibiting other contributors to patch there something...22:33
*** kevinconway has quit IRC22:33
*** jcooley_ has quit IRC22:34
lsmola_jpich, :-) thanks for understanding me22:34
david-lyleThere certainly will be a ramp up phase22:34
*** jcooley_ has joined #openstack-meeting22:34
jpichlsmola: No worries... though I had to read twice too :o)22:34
lsmola_david-lyle, also itś not entirely easy to run development env for tuskar UI22:34
*** Toshi has quit IRC22:35
jpichIs the assumption that the core teams will be merged straight away?22:35
lsmola_david-lyle, also costs at least 12GB ram, preferably 16GB22:35
david-lyleI think that needs to be discussed as well22:35
*** galstrom_zzz is now known as galstrom22:35
*** michchap has joined #openstack-meeting22:35
david-lylelsmola_: you may be doing it wrong ;)22:35
*** michchap has quit IRC22:35
lsmola_david-lyle, we are running to many openstacks :-)22:35
*** Toshi has joined #openstack-meeting22:36
lsmola_david-lyle, itś the minimal required env with simulatin 4 baremetals22:36
jpichdavid-lyle: Fair enough, re: fundamental change. I'm realising this as I read more :) (/me was thinking, well it's a new dashboard/tab right, just coming with a bit more code than usual)22:36
*** derekh has quit IRC22:36
*** michchap has joined #openstack-meeting22:36
ohnoimdeadanother stupid question: does tusker work with devstack?22:36
lsmola_david-lyle, well core merge would be welcome22:36
jomaraohnoimdead: not a stupid question at all22:37
lsmola_ohnoimdead, no, tuskar is for deployment22:37
lsmola_ohnoimdead, so it also does what devstack do (tuskar+tripleo)22:37
* mrunge is not using devstack at all....22:37
ohnoimdeadgotcha. makes sense.22:38
jpichIt sounds like leveraging our new plugin mechanism is also an option, even if the project/repo moves under the horizon umbrella22:38
lsmola_ohnoimdead, think of openstack as an regular application(like wordpress), you will use openstack to deploy the application (meaning it will deploy itself :-))22:38
mrungejpich +122:38
*** jcooley_ has quit IRC22:38
* ohnoimdead needs to go read a lot more about tusker+triple-o22:38
*** oubiwan__ has quit IRC22:39
lifelessohnoimdead: you could use devstack to bring up a baremetal/ironic cloud22:39
lifelessohnoimdead: and run tuskar on that to deploy a KVM cloud separately22:40
*** electrichead has left #openstack-meeting22:40
ohnoimdeadvery cool. i'm a little behind on some of the new os projects.22:40
ohnoimdeadnew being within the last 6 months. :p22:40
lsmola_lifeless, I think I have tried similar crazines from start :-) but failed22:41
mrungedavid-lyle, let's make an action item, the tuskar guys should come up with a merge plan ?22:41
lifelesslsmola_: yeah, *I* wouldn't try it, but in principle...22:41
lsmola_hehe22:41
david-lyleIs there anyone who wants to express a strong opinion against bring tuskar into the Horizon program?22:41
lsmola_lifeless, yeah I get you :-)22:41
*** SergeyLukjanov has quit IRC22:41
david-lyleif not, I'd like to see a plan for the merging of code that is not a massive code drop22:42
*** toanster_ has quit IRC22:42
jpich+1 to bringing it under the Horizon umbrella - although should we still wait for it to be integrated? Can a program have both incubated and integrated elements?22:42
mrunge+1 for the merge in smaller pieces22:42
lsmola_jpich, good question22:42
lifelessjpich: a program can22:43
lifelessjpich: in fact programs don't have to have any incubated or integrated elements.22:43
david-lylethat's why I initially was thinking separate code bases22:43
lifelessjpich: infra, devstack for instance.22:43
lsmola_mrunge, yes it should be perfectly doable, as the tuskar part will be hidden by default22:43
jpichOk!22:43
lifelessjpich: the integrated gate is specifically the set of things that get released every 6 months and their direct deps22:43
lifelessish22:43
lifeless:)22:43
*** herndon has joined #openstack-meeting22:44
*** ivasev has quit IRC22:44
david-lyleok, who wants to own the merge plan?22:45
jpichlifeless: Yes, ok. It just seems programs have had a general set of repos usually that are either all not integrated, or all incubated, or all integrated - to my knowledge22:45
lifelesslsmola_ volunteered on the TripleO side already :)22:45
lsmola_david-lyle, i took it from tripleo side, so me? ;-)22:45
mrungecongrats lsmola_ !22:45
* lifeless throws lsmola_ into the lion pit22:45
david-lylethanks lsmola22:45
lsmola_david-lyle, I will put heads together with mrunge and rdopieralsky to figure this out22:46
lblanchardhahaha22:46
lsmola_lifeless, hehe22:46
mrungeno, no no22:46
david-lylebringing mrunge down with you22:46
mrunge;-)22:46
lsmola_lol :-)22:46
david-lylelet's see a plan, I'll work on a plan for core-reviewer merge, no-merge, 3 from a company, but only on the second Tuesday logistics22:47
*** AaronGr_afk is now known as AaronGr22:47
jpichhaha22:47
*** epim has quit IRC22:47
david-lyleSo, let's just note for the record that we're accepting Tuskar-UI and we're working on the details22:48
jomara+1 to all that including 2ndtuesday22:48
lsmola_excellent22:48
jcoufalawesome22:48
jtomasekgreat news22:48
david-lyleWelcome, bring friends :)22:48
lsmola_:-D22:48
ohnoimdead(thumbsup)22:48
mrungeand beer22:48
lblanchardfriends who like to review!!22:48
jpichhaha22:49
david-lyle#topic Ceilometer integration (lsmola)22:49
*** openstack changes topic to "Ceilometer integration (lsmola) (Meeting topic: Horizon)"22:49
jcoufallsmola started to get more folks in (teaching his son django already)22:49
david-lylelsmola_22:49
lblanchardjcoufal: his son is 3 weeks old, right?22:49
mrungehis son can't even sit.22:49
lsmola_david-lyle, given we dont have much time, the agenda sums it pretty good22:49
lblanchardlol22:49
lsmola_lblanchard, please if you could look on 1. and .2, it would be great22:50
lsmola_lblanchard, we need to have some great wireframes for that :-)22:50
david-lyleso lsmola_ you do have a bp that depends on a ceilometer bp that is not owned by anyone22:50
lblanchardlsmola: will do22:50
jpichIs it also on the UX AskBot?22:50
lsmola_david-lyle, it is22:50
david-lylehttps://blueprints.launchpad.net/horizon/+spec/ceilometer-api-enhancements22:50
lsmola_david-lyle, and it should land in I2, that shift this to I322:50
jcoufaljpich: there is first version to review22:50
* jpich admires the dependency tree22:51
jcoufalwe need to get more focus on that22:51
david-lylehttps://blueprints.launchpad.net/ceilometer/+spec/statistics-order-by-and-limit-for-grouped-query22:51
jpichCool!22:51
david-lyleis the ceilo bp22:51
lsmola_david-lyle, this one expecially https://blueprints.launchpad.net/ceilometer/+spec/complex-filter-expressions-in-api-queries22:51
lsmola_david-lyle, that will bring big changes to ceilometer22:51
david-lyleso, do we need the other ceilo item?22:51
lsmola_david-lyle, they are willing to prioritize things we need in Horizon22:51
david-lyleconfused, is one replacing the other?22:52
lsmola_david-lyle, yeah, but itś not a blocker I guess, we can have non-optimal version just with that one22:52
lsmola_david-lyle, the others are more about optimization of queries. With more data i will bomdard the server with queries22:53
*** stevemar has quit IRC22:53
david-lylesince the non-owned one is not likely to land, until someone actually owns it, will you split your bp to reflect the work for each22:53
david-lylemakes release planning a bit easier :)22:53
lblanchardlsmola: I envisioned that Admin users would see a similar Overview page as other users...22:53
lsmola_david-lyle, yes, I should change the deps a bit22:53
david-lylelsmola_: thanks22:53
lsmola_david-lyle, things ae changing so fast :-)22:54
lsmola_david-lyle, ok, we can go to next22:54
david-lyle#topic update from I18N (amotoki)22:54
*** openstack changes topic to "update from I18N (amotoki) (Meeting topic: Horizon)"22:54
jpichamotoki can't attend, but the translation update for stable was a success, thanks everyone22:55
david-lyleexcellent22:55
lsmola_lblanchard, yes, could be, though they might be interested in diferent stats. Risght now the overview pages differ22:55
jpichMost patches got merged a bit late but the stable-maint team has agreed it makes sense to have a freeze exception for translations in general, 3 days after the stable freeze22:55
david-lylethanks to all who provided reviews22:55
david-lyle#topic Open Discussion22:56
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"22:56
MaxVfew questions here22:56
jpichThis is enough for stable updates which have few strings, the process for new release tbd22:56
MaxVdo we start forcing people using angular?22:56
*** dcramer_ has joined #openstack-meeting22:56
david-lyleMaxV, I just noticed the Jasmine target got removed from the agenda, apologies22:56
lsmola_MaxV, I guess only when they want to write javascript libs22:56
david-lyles/target/topic22:56
MaxVthiswas my second question22:57
david-lyleMaxV: force seems strong22:57
*** casanch1 has quit IRC22:57
jomarai think force is reasonable, if the option is "large pile of jquery" vs angular22:57
david-lyleI think there is going to be a bit of time getting most of the existing coder base up to speed on angular22:58
jomaraie, dont let people write new interactionsw ith a bunch of jquery22:58
david-lylenew functionality makes sense, but fixes etc, not so much22:58
jomaraya22:58
jtomasekdavid-lyle: +122:58
MaxVagreed22:58
lblanchardlsmola: agreed…I will look into these both further and we can discuss more this week about designs!22:58
*** thomasem has quit IRC22:58
lsmola_exactly22:58
lsmola_lblanchard, excellent, thank you very much22:59
*** NehaV1 has quit IRC22:59
david-lyleWe do have at least two whole views that are primarily javascript22:59
jomaraMaxV: were you going to talk about jasmine too?22:59
MaxVmy second question was about jasmine22:59
david-lyleI'm not sure forcing a rewrite to augment the network topology screen makes sense either22:59
david-lyleeventually22:59
MaxVto correctly test angular we need a javascript mocking library23:00
MaxVat least23:00
lsmola_david-lyle, agreed, same for the heat topology23:00
david-lylelsmola_: yes that was the other of the two23:00
david-lyle:)23:00
lsmola_:-)23:00
david-lyleI spent a little time looking into Jasmine, I didn't see a big issue with it23:01
david-lyleDid anyone have any concerns?23:01
MaxVmaybe we can keep qunit23:01
MaxVfor old things23:01
david-lylejpich: did you do the qunit implementation?23:01
MaxVand force jasmine on angular testing23:01
*** morazi has left #openstack-meeting23:01
ohnoimdead+1 for jasmine. it's dope.23:01
jomaraMaxV: id happily rewrite my tests in jasmine23:01
jpichdavid-lyle: It was already there when I came on board, I believe23:02
david-lylejpich: ok23:02
*** ItSANgo has joined #openstack-meeting23:02
*** epim has joined #openstack-meeting23:02
mrungedavid-lyle, as far as I can remember, it's good old code, at least a year old, probably more23:02
mrungemore 1.5 years now23:02
lsmola_:-)23:02
ohnoimdeadqunit stuff has been around forever, since we started23:03
*** weshay has quit IRC23:03
mrungeohnoimdead, might know it23:03
david-lyleI don't have a problem moving forward then.  If we are going to have more javascript then we need to have better testing of it and since we're moving to angular, let's optimize for that23:03
mrungeha ;-)23:03
*** colinmcn_ has quit IRC23:03
*** colinmcnamara has quit IRC23:03
MaxVI propose to keep qunit for old testing23:03
mrungeI'd love to unify all that stuff23:03
ohnoimdeadi'm less enthusiastic about angular, but that's a different topic. :p23:03
lsmola_+1 to have jasmine for angular23:03
*** colinmcnamara has joined #openstack-meeting23:03
*** colinmcn_ has joined #openstack-meeting23:03
david-lylealright, let's get the Jasmine patch reviewed and let the testing progress23:04
david-lyleovertime23:04
david-lyleThanks everyone!23:04
jpichThanks everyone23:04
mrungedavid-lyle, thank you!23:04
david-lylegood to see you ohnoimdead23:04
jcoufalo/23:04
david-lyle#endmeeting23:04
jcoufalthanks guys23:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:04
openstackMeeting ended Tue Dec 10 23:04:57 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:04
jomarathnaks guys23:05
lsmola_thanks everyone, have a good night23:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-10-22.01.html23:05
jtomasekthanks all23:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-10-22.01.txt23:05
lblanchardthanks all!23:05
ohnoimdeadthank you! you folks are wonderful!23:05
*** jcoufal has quit IRC23:05
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-10-22.01.log.html23:05
*** ohnoimdead has quit IRC23:05
*** jpich has quit IRC23:05
*** jcooley_ has joined #openstack-meeting23:05
*** Toshi has quit IRC23:06
*** burt has quit IRC23:07
*** lsmola_ has quit IRC23:07
*** dhh has joined #openstack-meeting23:07
*** jcooley_ has quit IRC23:08
*** jcooley_ has joined #openstack-meeting23:08
*** sayali has quit IRC23:09
*** bdehamer has quit IRC23:10
*** jgrimm has quit IRC23:10
*** chuck__ has joined #openstack-meeting23:11
*** bknudson has left #openstack-meeting23:12
*** dhh has quit IRC23:12
*** yamahata_ has joined #openstack-meeting23:12
*** jcooley_ has quit IRC23:12
*** sushils has quit IRC23:13
*** denis_makogon has quit IRC23:15
*** sushils has joined #openstack-meeting23:17
*** stevemar has joined #openstack-meeting23:17
*** jcooley_ has joined #openstack-meeting23:18
*** dstanek has quit IRC23:18
*** epim has quit IRC23:19
*** vuil has joined #openstack-meeting23:20
*** vuil has quit IRC23:20
*** kgriffs is now known as kgriffs_afk23:21
*** dims has quit IRC23:21
*** jcooley_ has quit IRC23:22
*** jcooley_ has joined #openstack-meeting23:22
*** RajeshMohan has quit IRC23:22
*** lblanchard has quit IRC23:22
*** sacharya has quit IRC23:22
*** RajeshMohan has joined #openstack-meeting23:23
*** HenryG has joined #openstack-meeting23:27
*** neelashah has quit IRC23:27
*** epim has joined #openstack-meeting23:28
*** flaper87 is now known as flaper87|afk23:28
*** rakhmerov has joined #openstack-meeting23:29
*** jcooley_ has quit IRC23:30
*** epim has quit IRC23:30
*** stevemar has quit IRC23:30
*** jcooley_ has joined #openstack-meeting23:30
*** lbragstad has quit IRC23:31
*** lbragstad has joined #openstack-meeting23:31
*** colinmcnamara has quit IRC23:32
*** colinmcn_ has quit IRC23:32
*** henrynash has quit IRC23:32
*** dkranz has quit IRC23:32
*** vuil has joined #openstack-meeting23:33
*** vuil has quit IRC23:33
*** rnirmal has quit IRC23:33
*** epim has joined #openstack-meeting23:34
*** rakhmerov has quit IRC23:34
*** epim has quit IRC23:34
*** AlanClark has quit IRC23:35
*** maxdml has quit IRC23:35
*** jcooley_ has quit IRC23:35
*** jtomasek has quit IRC23:36
*** jcooley_ has joined #openstack-meeting23:37
*** lbragstad has quit IRC23:38
*** jtomasek has joined #openstack-meeting23:38
*** colinmcnamara has joined #openstack-meeting23:41
*** colinmcn_ has joined #openstack-meeting23:41
*** ctracey is now known as ctracey|away23:41
*** MaxV has quit IRC23:43
*** epim has joined #openstack-meeting23:43
*** MaxV has joined #openstack-meeting23:43
*** coolsvap has quit IRC23:44
*** jcooley_ has quit IRC23:44
*** lblanchard has joined #openstack-meeting23:44
*** jcooley_ has joined #openstack-meeting23:44
*** jcooley_ has quit IRC23:44
*** jcooley_ has joined #openstack-meeting23:45
*** fbo_away is now known as fbo23:45
*** galstrom is now known as galstrom_zzz23:45
*** dstanek has joined #openstack-meeting23:45
*** chuck__ has quit IRC23:45
*** MaxV has quit IRC23:48
*** dstanek has quit IRC23:50
*** jtomasek has quit IRC23:50
*** mrunge has quit IRC23:53
*** michchap_ has joined #openstack-meeting23:53
*** jcooley_ has quit IRC23:53
*** jcooley_ has joined #openstack-meeting23:54
*** dstanek has joined #openstack-meeting23:55
*** michchap has quit IRC23:57
*** jcooley_ has quit IRC23:58
*** jcooley_ has joined #openstack-meeting23:58
*** Leo_ has quit IRC23:59
*** mrodden has quit IRC23:59
*** radsy has joined #openstack-meeting23:59

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