Tuesday, 2013-08-06

*** ytwu1 has quit IRC00:00
*** Tacho has quit IRC00:00
*** ytwu has joined #openstack-meeting00:00
*** ytwu2 has quit IRC00:02
*** hemna is now known as hemnafk00:03
*** alexpilotti has joined #openstack-meeting00:04
*** alexpilotti has quit IRC00:05
*** stevemar has joined #openstack-meeting00:05
*** ytwu1 has joined #openstack-meeting00:06
*** gyee has quit IRC00:06
*** ryanpetrello has joined #openstack-meeting00:07
*** ytwu has quit IRC00:07
*** IlyaE has quit IRC00:08
*** ytwu has joined #openstack-meeting00:11
*** mdenny has quit IRC00:12
*** ytwu1 has quit IRC00:12
*** nijaba_ has joined #openstack-meeting00:12
*** nijaba has quit IRC00:13
*** jrodom has quit IRC00:15
*** sarob has joined #openstack-meeting00:16
*** ytwu1 has joined #openstack-meeting00:16
*** markpeek has joined #openstack-meeting00:16
*** ytwu has quit IRC00:17
*** alexb_ has quit IRC00:20
*** ytwu has joined #openstack-meeting00:20
*** ytwu1 has quit IRC00:20
*** sarob has quit IRC00:20
*** virajh has quit IRC00:21
*** MarkAtwood has quit IRC00:23
*** ytwu1 has joined #openstack-meeting00:23
*** ytwu has quit IRC00:24
*** ytwu has joined #openstack-meeting00:27
*** ytwu1 has quit IRC00:28
*** stevemar has quit IRC00:29
*** ryanpetrello has quit IRC00:32
*** ytwu1 has joined #openstack-meeting00:32
*** ytwu has quit IRC00:34
*** jrodom has joined #openstack-meeting00:36
*** ytwu has joined #openstack-meeting00:36
*** IlyaE has joined #openstack-meeting00:36
*** ytwu1 has quit IRC00:36
*** ytwu1 has joined #openstack-meeting00:40
*** ytwu has quit IRC00:40
*** colinmcnamara has joined #openstack-meeting00:42
*** ytwu has joined #openstack-meeting00:44
*** bdpayne has quit IRC00:44
*** ytwu1 has quit IRC00:45
*** SumitNaiksatam has quit IRC00:48
*** ytwu1 has joined #openstack-meeting00:49
*** kebray has quit IRC00:50
*** anniec has joined #openstack-meeting00:51
*** ytwu has quit IRC00:51
*** ytwu has joined #openstack-meeting00:51
*** ytwu1 has quit IRC00:53
*** yuan has joined #openstack-meeting00:53
*** ytwu1 has joined #openstack-meeting00:55
*** ytwu has quit IRC00:56
*** sushils has quit IRC00:57
*** ytwu has joined #openstack-meeting00:59
*** ytwu1 has quit IRC00:59
*** gongysh has quit IRC01:00
*** jrodom has quit IRC01:01
*** ytwu1 has joined #openstack-meeting01:04
*** colinmcnamara1 has joined #openstack-meeting01:05
*** ytwu has quit IRC01:06
*** skraynev has joined #openstack-meeting01:06
*** colinmcnamara has quit IRC01:07
*** armax has quit IRC01:07
*** SumitNaiksatam has joined #openstack-meeting01:08
*** Mandell has quit IRC01:08
*** ytwu has joined #openstack-meeting01:11
*** shang has quit IRC01:11
*** SridarK has quit IRC01:11
*** nijaba_ has quit IRC01:12
*** nijaba has joined #openstack-meeting01:12
*** ayoung has quit IRC01:13
*** ytwu1 has quit IRC01:13
*** ytwu1 has joined #openstack-meeting01:15
*** colinmcnamara1 has quit IRC01:17
*** ytwu2 has joined #openstack-meeting01:18
*** ytwu has quit IRC01:18
*** ytwu1 has quit IRC01:20
*** ytwu has joined #openstack-meeting01:21
*** rkukura has left #openstack-meeting01:22
*** ytwu2 has quit IRC01:22
*** shang has joined #openstack-meeting01:22
*** llu has quit IRC01:23
*** thang has quit IRC01:23
*** llu has joined #openstack-meeting01:24
*** ytwu1 has joined #openstack-meeting01:24
*** tianst20 has joined #openstack-meeting01:24
*** tian has quit IRC01:24
*** ytwu has quit IRC01:25
*** danwent has quit IRC01:27
*** jrodom has joined #openstack-meeting01:28
*** jrodom has quit IRC01:28
*** danwent has joined #openstack-meeting01:29
*** jrodom has joined #openstack-meeting01:30
*** markwash has joined #openstack-meeting01:30
*** fnaval_ has joined #openstack-meeting01:32
*** markmcclain has quit IRC01:32
*** danwent has quit IRC01:34
*** markwash has quit IRC01:34
*** ivar-lazzaro has quit IRC01:35
*** markwash has joined #openstack-meeting01:35
*** reed has quit IRC01:35
*** jrodom has quit IRC01:38
*** ytwu has joined #openstack-meeting01:39
*** ytwu1 has quit IRC01:40
*** ytwu1 has joined #openstack-meeting01:42
*** ytwu has quit IRC01:43
*** ytwu has joined #openstack-meeting01:44
*** yaguang has joined #openstack-meeting01:45
*** gongysh has joined #openstack-meeting01:46
*** ytwu1 has quit IRC01:46
*** fnaval_ has quit IRC01:49
*** fnaval_ has joined #openstack-meeting01:50
*** ytwu1 has joined #openstack-meeting01:51
*** ytwu has quit IRC01:51
*** armax has joined #openstack-meeting01:52
*** jrodom has joined #openstack-meeting01:54
*** ytwu has joined #openstack-meeting01:54
*** ytwu1 has quit IRC01:55
*** rongze_ has joined #openstack-meeting01:55
*** ytwu1 has joined #openstack-meeting01:57
*** rongze has quit IRC01:57
*** nati_ueno has quit IRC01:57
*** ytwu has quit IRC01:58
*** ytwu has joined #openstack-meeting02:01
*** ytwu1 has quit IRC02:03
*** ytwu1 has joined #openstack-meeting02:04
*** ytwu has quit IRC02:05
*** neelashah has joined #openstack-meeting02:06
*** ytwu has joined #openstack-meeting02:07
*** ytwu1 has quit IRC02:09
*** epim has joined #openstack-meeting02:09
*** nijaba has quit IRC02:12
*** anniec has quit IRC02:13
*** ytwu1 has joined #openstack-meeting02:14
*** nijaba has joined #openstack-meeting02:15
*** nijaba has quit IRC02:15
*** nijaba has joined #openstack-meeting02:15
*** lifeless has quit IRC02:16
*** ytwu has quit IRC02:16
*** ytwu has joined #openstack-meeting02:19
*** ytwu1 has quit IRC02:21
*** novas0x2a|laptop has quit IRC02:21
*** dcramer_ has joined #openstack-meeting02:22
*** ytwu1 has joined #openstack-meeting02:23
*** ytwu has quit IRC02:24
*** ytwu has joined #openstack-meeting02:25
*** ytwu1 has quit IRC02:27
*** ytwu1 has joined #openstack-meeting02:28
*** ytwu has quit IRC02:30
*** ytwu has joined #openstack-meeting02:34
*** ytwu1 has quit IRC02:35
*** ytwu1 has joined #openstack-meeting02:38
*** ytwu has quit IRC02:39
*** epim_ has joined #openstack-meeting02:39
*** markwash has quit IRC02:40
*** ayoung has joined #openstack-meeting02:42
*** nijaba_ has joined #openstack-meeting02:42
*** jrodom has quit IRC02:42
*** glikson has joined #openstack-meeting02:42
*** changbl_ has joined #openstack-meeting02:43
*** ytwu has joined #openstack-meeting02:44
*** ytwu1 has quit IRC02:44
*** brucer_ has joined #openstack-meeting02:47
*** glikson has quit IRC02:47
*** ytwu1 has joined #openstack-meeting02:47
*** esmute_ has joined #openstack-meeting02:47
*** nijaba has quit IRC02:47
*** changbl has quit IRC02:47
*** epim has quit IRC02:47
*** morganfainberg has quit IRC02:47
*** esmute has quit IRC02:47
*** adalbas has quit IRC02:47
*** esmute_ is now known as esmute02:47
*** brucer has quit IRC02:47
*** morganfainberg has joined #openstack-meeting02:47
*** epim_ is now known as epim02:47
*** morganfainberg has quit IRC02:48
*** morganfainberg has joined #openstack-meeting02:48
*** jhenner has quit IRC02:48
*** NobodyCam has left #openstack-meeting02:48
*** ytwu has quit IRC02:49
*** ytwu1 has quit IRC02:54
*** ytwu has joined #openstack-meeting02:54
*** yaguang has quit IRC02:56
*** ytwu1 has joined #openstack-meeting02:57
*** adalbas has joined #openstack-meeting02:57
*** ytwu has quit IRC02:59
*** MarkAtwood has joined #openstack-meeting02:59
*** lifeless has joined #openstack-meeting03:00
*** ytwu has joined #openstack-meeting03:03
*** ytwu1 has quit IRC03:05
*** ytwu1 has joined #openstack-meeting03:07
*** yaguang has joined #openstack-meeting03:08
*** ytwu has quit IRC03:08
*** ytwu has joined #openstack-meeting03:11
*** ytwu1 has quit IRC03:12
*** ytwu1 has joined #openstack-meeting03:13
*** armax has quit IRC03:14
*** nijaba_ has quit IRC03:14
*** armax has joined #openstack-meeting03:15
*** nijaba has joined #openstack-meeting03:15
*** ytwu has quit IRC03:16
*** ryanpetrello has joined #openstack-meeting03:17
*** dguitarbite has joined #openstack-meeting03:19
*** ytwu has joined #openstack-meeting03:21
*** ytwu1 has quit IRC03:22
*** terriyu has quit IRC03:22
*** ytwu1 has joined #openstack-meeting03:23
*** jecarey has joined #openstack-meeting03:24
*** ytwu has quit IRC03:25
*** bdpayne has joined #openstack-meeting03:26
*** ytwu has joined #openstack-meeting03:26
*** ytwu1 has quit IRC03:28
*** ytwu1 has joined #openstack-meeting03:29
*** zehicle_at_dell has joined #openstack-meeting03:29
*** ytwu has quit IRC03:30
*** martine has joined #openstack-meeting03:31
*** martine is now known as Guest6710203:31
*** ytwu has joined #openstack-meeting03:32
*** ketan985 has joined #openstack-meeting03:32
*** ytwu1 has quit IRC03:33
*** ryanpetrello has quit IRC03:34
*** dcramer_ has quit IRC03:35
*** ytwu1 has joined #openstack-meeting03:37
*** beagles has quit IRC03:39
*** ytwu has quit IRC03:39
*** ytwu has joined #openstack-meeting03:40
*** bdpayne has quit IRC03:40
*** jlucci has joined #openstack-meeting03:41
*** ytwu1 has quit IRC03:41
*** lbragstad_ has quit IRC03:44
*** neelashah has quit IRC03:45
*** afazekas has quit IRC03:47
*** ytwu1 has joined #openstack-meeting03:48
*** ytwu has quit IRC03:49
*** ytwu has joined #openstack-meeting03:52
*** Guest67102 has quit IRC03:52
*** epim has quit IRC03:53
*** ytwu1 has quit IRC03:53
*** yaguang has quit IRC03:55
*** ytwu1 has joined #openstack-meeting03:57
*** ytwu has quit IRC03:58
*** adrian_otto has joined #openstack-meeting03:59
*** ytwu has joined #openstack-meeting04:00
*** ytwu1 has quit IRC04:01
*** SergeyLukjanov has joined #openstack-meeting04:03
*** ytwu1 has joined #openstack-meeting04:04
*** ytwu has quit IRC04:05
*** adrian_otto has quit IRC04:07
*** ytwu has joined #openstack-meeting04:07
*** ytwu1 has quit IRC04:09
*** cbaesema_ has joined #openstack-meeting04:10
*** ytwu1 has joined #openstack-meeting04:10
*** xBsd has joined #openstack-meeting04:10
*** ytwu has quit IRC04:12
*** yaguang has joined #openstack-meeting04:13
*** ytwu has joined #openstack-meeting04:13
*** nijaba has quit IRC04:14
*** ytwu1 has quit IRC04:15
*** nijaba has joined #openstack-meeting04:16
*** ytwu1 has joined #openstack-meeting04:17
*** ytwu has quit IRC04:17
*** xBsd has quit IRC04:19
*** ytwu has joined #openstack-meeting04:20
*** ytwu1 has quit IRC04:21
*** changbl_ has quit IRC04:22
*** ytwu1 has joined #openstack-meeting04:23
*** ytwu has quit IRC04:24
*** bdpayne has joined #openstack-meeting04:27
*** ytwu has joined #openstack-meeting04:28
*** ytwu1 has quit IRC04:29
*** glikson has joined #openstack-meeting04:29
*** SergeyLukjanov has quit IRC04:30
*** SergeyLukjanov has joined #openstack-meeting04:31
*** danwent has joined #openstack-meeting04:32
*** ytwu1 has joined #openstack-meeting04:33
*** ytwu has quit IRC04:34
*** ytwu has joined #openstack-meeting04:39
*** ytwu1 has quit IRC04:40
*** glikson has quit IRC04:43
*** ytwu1 has joined #openstack-meeting04:43
*** ytwu has quit IRC04:43
*** boris-42 has joined #openstack-meeting04:44
*** ytwu has joined #openstack-meeting04:45
*** ytwu1 has quit IRC04:47
*** ytwu1 has joined #openstack-meeting04:48
*** zul has quit IRC04:48
*** danwent has quit IRC04:49
*** ytwu has quit IRC04:49
*** glikson has joined #openstack-meeting04:53
*** bdpayne has quit IRC04:54
*** wolfdreamer has quit IRC04:54
*** henrynash has joined #openstack-meeting04:55
*** ytwu has joined #openstack-meeting04:58
*** ytwu1 has quit IRC04:59
*** changbl_ has joined #openstack-meeting05:00
*** danwent has joined #openstack-meeting05:01
*** ytwu1 has joined #openstack-meeting05:01
*** ytwu has quit IRC05:03
*** troytoman is now known as troytoman-away05:08
*** ytwu has joined #openstack-meeting05:09
*** changbl_ has quit IRC05:09
*** ytwu1 has quit IRC05:10
*** lastidiot has quit IRC05:10
*** ytwu1 has joined #openstack-meeting05:13
*** ketan985 has quit IRC05:14
*** nijaba has quit IRC05:15
*** ytwu has quit IRC05:15
*** nijaba has joined #openstack-meeting05:16
*** nijaba has joined #openstack-meeting05:16
*** ytwu has joined #openstack-meeting05:17
*** ytwu1 has quit IRC05:17
*** ytwu1 has joined #openstack-meeting05:21
*** ytwu has quit IRC05:21
*** adrian_otto has joined #openstack-meeting05:21
*** abaron has joined #openstack-meeting05:22
*** SergeyLukjanov has quit IRC05:24
*** xBsd has joined #openstack-meeting05:29
*** ytwu has joined #openstack-meeting05:29
*** markpeek has quit IRC05:29
*** ytwu1 has quit IRC05:29
*** ytwu has quit IRC05:33
*** ytwu has joined #openstack-meeting05:33
*** jackmccann_ has quit IRC05:34
*** dguitarbite has quit IRC05:35
*** gongysh has quit IRC05:36
*** kebray has joined #openstack-meeting05:37
*** ytwu1 has joined #openstack-meeting05:38
*** ytwu has quit IRC05:38
*** MarkAtwood has quit IRC05:39
*** ytwu has joined #openstack-meeting05:40
*** ytwu1 has quit IRC05:42
*** ytwu1 has joined #openstack-meeting05:42
*** ytwu has quit IRC05:44
*** ytwu has joined #openstack-meeting05:45
*** ytwu1 has quit IRC05:47
*** ytwu1 has joined #openstack-meeting05:47
*** ytwu has quit IRC05:49
*** gongysh has joined #openstack-meeting05:49
*** ytwu has joined #openstack-meeting05:50
*** ytwu1 has quit IRC05:52
*** ytwu1 has joined #openstack-meeting05:54
*** ytwu has quit IRC05:55
*** ytwu has joined #openstack-meeting05:58
*** [1]glikson has joined #openstack-meeting05:59
*** glikson has quit IRC05:59
*** [1]glikson is now known as glikson05:59
*** ytwu1 has quit IRC05:59
*** ytwu1 has joined #openstack-meeting06:00
*** abaron has quit IRC06:01
*** ytwu has quit IRC06:02
*** ytwu has joined #openstack-meeting06:04
*** ytwu1 has quit IRC06:07
*** ytwu1 has joined #openstack-meeting06:08
*** ytwu has quit IRC06:09
*** ytwu has joined #openstack-meeting06:12
*** ytwu1 has quit IRC06:13
*** nijaba has quit IRC06:13
*** kebray has quit IRC06:15
*** ytwu1 has joined #openstack-meeting06:15
*** nijaba has joined #openstack-meeting06:16
*** nijaba has quit IRC06:16
*** nijaba has joined #openstack-meeting06:16
*** ytwu has quit IRC06:16
*** MarkAtwood has joined #openstack-meeting06:18
*** ytwu has joined #openstack-meeting06:21
*** ytwu1 has quit IRC06:22
*** armax has quit IRC06:25
*** hua has quit IRC06:25
*** ytwu1 has joined #openstack-meeting06:26
*** glikson has quit IRC06:26
*** ytwu has quit IRC06:28
*** doron_afk has joined #openstack-meeting06:28
*** ytwu has joined #openstack-meeting06:29
*** ytwu1 has quit IRC06:30
*** ytwu1 has joined #openstack-meeting06:32
*** abaron has joined #openstack-meeting06:33
*** ytwu has quit IRC06:33
*** henrynash has quit IRC06:35
*** henrynash has joined #openstack-meeting06:37
*** kebray has joined #openstack-meeting06:37
*** ytwu has joined #openstack-meeting06:38
*** ytwu1 has quit IRC06:39
*** salv-orlando has joined #openstack-meeting06:40
*** ytwu1 has joined #openstack-meeting06:40
*** ytwu has quit IRC06:42
*** ytwu has joined #openstack-meeting06:44
*** ytwu1 has quit IRC06:44
*** otherwiseguy has quit IRC06:44
*** ytwu1 has joined #openstack-meeting06:47
*** ytwu has quit IRC06:48
*** danwent has quit IRC06:49
*** ttrifonov_zZzz is now known as ttrifonov06:49
*** jcoufal has joined #openstack-meeting06:51
*** ytwu has joined #openstack-meeting06:54
*** ytwu1 has quit IRC06:56
*** ytwu1 has joined #openstack-meeting06:56
*** kebray has quit IRC06:58
*** ytwu has quit IRC06:59
*** ohadlevy_ is now known as ohadlevy07:00
*** ohadlevy is now known as Guest9212007:00
*** Guest92120 is now known as ohadlevy_07:00
*** jhenner has joined #openstack-meeting07:01
*** adrian_otto has quit IRC07:03
*** ytwu has joined #openstack-meeting07:03
*** slavayssiere has joined #openstack-meeting07:03
*** IlyaE has quit IRC07:04
*** ytwu1 has quit IRC07:05
*** IlyaE has joined #openstack-meeting07:06
*** ytwu1 has joined #openstack-meeting07:06
*** tianst20 has quit IRC07:07
*** ytwu has quit IRC07:07
*** yaguang has quit IRC07:07
*** jlucci has quit IRC07:08
*** ytwu has joined #openstack-meeting07:10
*** ytwu1 has quit IRC07:13
*** ytwu2 has joined #openstack-meeting07:13
*** ytwu has quit IRC07:15
*** nijaba has quit IRC07:15
*** ytwu2 has left #openstack-meeting07:15
*** nijaba has joined #openstack-meeting07:16
*** glikson has joined #openstack-meeting07:18
*** ytwu has joined #openstack-meeting07:19
*** yaguang has joined #openstack-meeting07:20
*** MarkAtwood has quit IRC07:21
*** jhenner has quit IRC07:23
*** ndipanov_gone is now known as ndipanov07:23
*** ytwu1 has joined #openstack-meeting07:25
*** ytwu has quit IRC07:25
*** ytwu has joined #openstack-meeting07:27
*** tkammer has joined #openstack-meeting07:28
*** ytwu1 has quit IRC07:29
*** salv-orlando has quit IRC07:29
*** ytwu1 has joined #openstack-meeting07:31
*** salv-orlando has joined #openstack-meeting07:31
*** yaguang has quit IRC07:31
*** slavayssiere has quit IRC07:31
*** ytwu has quit IRC07:32
*** jaimegil has joined #openstack-meeting07:34
*** ytwu has joined #openstack-meeting07:34
*** mrunge has joined #openstack-meeting07:35
*** ytwu1 has quit IRC07:35
*** ytwu1 has joined #openstack-meeting07:38
*** ytwu has quit IRC07:39
*** safchain has joined #openstack-meeting07:41
*** sushils has joined #openstack-meeting07:41
*** ytwu has joined #openstack-meeting07:43
*** johnthetubaguy has joined #openstack-meeting07:43
*** yaguang has joined #openstack-meeting07:44
*** ytwu1 has quit IRC07:44
*** johnthetubaguy1 has joined #openstack-meeting07:46
*** safchain has quit IRC07:47
*** ytwu1 has joined #openstack-meeting07:47
*** rwsu-away has quit IRC07:48
*** ytwu has quit IRC07:48
*** johnthetubaguy has quit IRC07:48
*** ytwu has joined #openstack-meeting07:50
*** SumitNaiksatam has quit IRC07:51
*** ytwu1 has quit IRC07:51
*** SumitNaiksatam has joined #openstack-meeting07:52
*** ytwu1 has joined #openstack-meeting07:55
*** ytwu has quit IRC07:56
*** ytwu has joined #openstack-meeting07:57
*** IlyaE has quit IRC07:58
*** ytwu1 has quit IRC07:59
*** rwsu-away has joined #openstack-meeting08:00
*** sushils has quit IRC08:00
*** ytwu has quit IRC08:01
*** ytwu has joined #openstack-meeting08:01
*** sushils has joined #openstack-meeting08:01
*** ytwu1 has joined #openstack-meeting08:05
*** ytwu has quit IRC08:05
*** dosaboy_alt has joined #openstack-meeting08:08
*** SergeyLukjanov has joined #openstack-meeting08:08
*** slavayssiere has joined #openstack-meeting08:10
*** pnavarro has joined #openstack-meeting08:10
*** ytwu has joined #openstack-meeting08:11
*** ytwu1 has quit IRC08:11
*** nijaba has quit IRC08:13
*** romcheg has joined #openstack-meeting08:14
*** ytwu1 has joined #openstack-meeting08:15
*** ytwu has quit IRC08:16
*** nijaba has joined #openstack-meeting08:17
*** ytwu has joined #openstack-meeting08:19
*** ytwu1 has quit IRC08:21
*** jhenner has joined #openstack-meeting08:22
*** derekh has joined #openstack-meeting08:23
*** ytwu has quit IRC08:23
*** ytwu1 has joined #openstack-meeting08:23
*** doron_afk is now known as doron08:24
*** ociuhandu has quit IRC08:24
*** johnthetubaguy1 is now known as johnthetubaguy08:27
*** jhenner has quit IRC08:28
*** ytwu has joined #openstack-meeting08:28
*** sdake_ has quit IRC08:30
*** ytwu1 has quit IRC08:30
*** doron is now known as doron_afk08:30
*** ytwu1 has joined #openstack-meeting08:31
*** ytwu has quit IRC08:33
*** ytwu has joined #openstack-meeting08:36
*** jhenner has joined #openstack-meeting08:37
*** ytwu1 has quit IRC08:38
*** Yada has joined #openstack-meeting08:38
*** ytwu1 has joined #openstack-meeting08:38
*** ytwu has quit IRC08:40
*** jhenner has quit IRC08:42
*** pnavarro has quit IRC08:43
*** ytwu has joined #openstack-meeting08:44
*** ytwu1 has quit IRC08:45
*** ytwu1 has joined #openstack-meeting08:48
*** ytwu has quit IRC08:48
*** ytwu has joined #openstack-meeting08:52
*** ytwu1 has quit IRC08:52
*** ytwu1 has joined #openstack-meeting08:55
*** ytwu has quit IRC08:56
*** ytwu has joined #openstack-meeting09:03
*** ytwu1 has quit IRC09:04
*** ytwu1 has joined #openstack-meeting09:06
*** ytwu has quit IRC09:07
*** ytwu has joined #openstack-meeting09:11
*** ytwu1 has quit IRC09:12
*** ytwu1 has joined #openstack-meeting09:13
*** ytwu has quit IRC09:16
*** nijaba has quit IRC09:16
*** nijaba has joined #openstack-meeting09:17
*** ytwu has joined #openstack-meeting09:17
*** ytwu1 has quit IRC09:18
*** ytwu1 has joined #openstack-meeting09:23
*** ytwu has quit IRC09:23
*** woodspa has joined #openstack-meeting09:24
*** woodspa has quit IRC09:24
*** ytwu has joined #openstack-meeting09:27
*** ytwu2 has joined #openstack-meeting09:29
*** ytwu1 has quit IRC09:29
*** pnavarro has joined #openstack-meeting09:30
*** ytwu has quit IRC09:31
*** ytwu2 has quit IRC09:35
*** ytwu has joined #openstack-meeting09:36
*** ytwu1 has joined #openstack-meeting09:40
*** ytwu has quit IRC09:41
*** ytwu has joined #openstack-meeting09:44
*** ytwu1 has quit IRC09:47
*** ytwu1 has joined #openstack-meeting09:48
*** ytwu has quit IRC09:48
*** ytwu has joined #openstack-meeting09:52
*** ytwu1 has quit IRC09:52
*** slavayssiere has quit IRC09:56
*** ytwu1 has joined #openstack-meeting09:56
*** ytwu has quit IRC09:56
*** ytwu has joined #openstack-meeting09:58
*** ytwu1 has quit IRC10:00
*** ytwu1 has joined #openstack-meeting10:03
*** ytwu has quit IRC10:05
*** ytwu has joined #openstack-meeting10:07
*** ytwu1 has quit IRC10:08
*** ytwu1 has joined #openstack-meeting10:11
*** ytwu has quit IRC10:11
*** [1]glikson has joined #openstack-meeting10:14
*** ytwu has joined #openstack-meeting10:14
*** boris-42 has quit IRC10:15
*** ytwu1 has quit IRC10:15
*** nijaba has quit IRC10:16
*** glikson has quit IRC10:17
*** [1]glikson is now known as glikson10:17
*** nijaba has joined #openstack-meeting10:20
*** pcm_ has joined #openstack-meeting10:27
*** pcm_ has quit IRC10:27
*** ytwu1 has joined #openstack-meeting10:28
*** pcm_ has joined #openstack-meeting10:28
*** ytwu has quit IRC10:29
*** ytwu has joined #openstack-meeting10:33
*** ytwu1 has quit IRC10:35
*** ytwu1 has joined #openstack-meeting10:36
*** ytwu has quit IRC10:37
*** ketan985 has joined #openstack-meeting10:37
*** euanh has joined #openstack-meeting10:39
*** ytwu has joined #openstack-meeting10:39
*** martine has joined #openstack-meeting10:39
*** euanh has left #openstack-meeting10:39
*** martine is now known as Guest240010:39
*** ytwu1 has quit IRC10:41
*** ytwu1 has joined #openstack-meeting10:43
*** gongysh has quit IRC10:43
*** ytwu has quit IRC10:43
*** yaguang has quit IRC10:43
*** ytwu has joined #openstack-meeting10:48
*** ytwu1 has quit IRC10:49
*** ytwu1 has joined #openstack-meeting10:50
*** Yada has quit IRC10:51
*** [1]glikson has joined #openstack-meeting10:51
*** ytwu has quit IRC10:52
*** glikson has quit IRC10:53
*** [1]glikson is now known as glikson10:53
*** ytwu has joined #openstack-meeting10:54
*** ytwu1 has quit IRC10:55
*** radez_g0n3 is now known as radez10:59
*** ytwu1 has joined #openstack-meeting11:02
*** ytwu has quit IRC11:03
*** ytwu has joined #openstack-meeting11:05
*** ytwu1 has quit IRC11:07
*** ytwu1 has joined #openstack-meeting11:07
*** ruhe has joined #openstack-meeting11:08
*** ytwu has quit IRC11:09
*** ytwu has joined #openstack-meeting11:10
*** ytwu1 has quit IRC11:12
*** jtomasek has joined #openstack-meeting11:12
*** ytwu1 has joined #openstack-meeting11:14
*** ytwu2 has joined #openstack-meeting11:16
*** anniec has joined #openstack-meeting11:16
*** nijaba has quit IRC11:17
*** ytwu has quit IRC11:17
*** nijaba has joined #openstack-meeting11:18
*** ytwu1 has quit IRC11:19
*** anniec_ has joined #openstack-meeting11:20
*** anniec has quit IRC11:21
*** anniec_ is now known as anniec11:21
*** pnavarro has quit IRC11:22
*** ytwu has joined #openstack-meeting11:26
*** woodspa has joined #openstack-meeting11:27
*** ytwu2 has quit IRC11:27
*** henrynash has quit IRC11:33
*** zul has joined #openstack-meeting11:33
*** boris-42 has joined #openstack-meeting11:34
*** ohadlevy_ is now known as ohadlevy11:38
*** ohadlevy has quit IRC11:38
*** ohadlevy has joined #openstack-meeting11:38
*** slavayssiere has joined #openstack-meeting11:38
*** ytwu1 has joined #openstack-meeting11:38
*** ytwu has quit IRC11:40
*** ytwu has joined #openstack-meeting11:43
*** ytwu1 has quit IRC11:45
*** jamespage_ has joined #openstack-meeting11:46
*** jasondotstar has quit IRC11:47
*** beagles has joined #openstack-meeting11:50
*** troytoman-away is now known as troytoman11:54
*** ytwu has quit IRC11:55
*** ytwu has joined #openstack-meeting11:56
*** ytwu1 has joined #openstack-meeting11:58
*** ytwu has quit IRC12:00
*** dosaboy_alt has quit IRC12:00
*** dosaboy_alt has joined #openstack-meeting12:01
*** abaron has quit IRC12:02
*** jamespage_ has quit IRC12:03
*** sandywalsh has quit IRC12:03
*** ytwu has joined #openstack-meeting12:08
*** dkranz has joined #openstack-meeting12:09
*** ytwu1 has quit IRC12:10
*** lbragstad has quit IRC12:12
*** doron_afk is now known as doron12:13
*** ohadlevy has quit IRC12:14
*** [1]glikson has joined #openstack-meeting12:14
*** ohadlevy has joined #openstack-meeting12:14
*** ohadlevy is now known as Guest2839112:15
*** ytwu1 has joined #openstack-meeting12:15
*** ytwu has quit IRC12:15
*** ketan985 has quit IRC12:16
*** sandywalsh has joined #openstack-meeting12:17
*** ytwu has joined #openstack-meeting12:17
*** abaron has joined #openstack-meeting12:17
*** glikson has quit IRC12:17
*** [1]glikson is now known as glikson12:17
*** nijaba has quit IRC12:17
*** nijaba has joined #openstack-meeting12:18
*** ytwu1 has quit IRC12:19
*** markvoelker has joined #openstack-meeting12:20
*** doron is now known as doron_afk12:21
*** ytwu1 has joined #openstack-meeting12:23
*** Guest28391 has quit IRC12:24
*** ytwu has quit IRC12:25
*** ytwu1 has quit IRC12:27
*** ytwu has joined #openstack-meeting12:28
*** Guest2400 is now known as martine_12:28
*** henrynash has joined #openstack-meeting12:28
*** ohadlevy_ has joined #openstack-meeting12:29
*** ladquin has joined #openstack-meeting12:30
*** henrynash has quit IRC12:31
*** ytwu has quit IRC12:32
*** ytwu has joined #openstack-meeting12:32
*** jasondotstar has joined #openstack-meeting12:35
*** xBsd has quit IRC12:35
*** ytwu1 has joined #openstack-meeting12:36
*** ytwu has quit IRC12:36
*** ytwu has joined #openstack-meeting12:41
*** psedlak has joined #openstack-meeting12:42
*** ytwu1 has quit IRC12:42
*** psedlak has quit IRC12:44
*** ytwu1 has joined #openstack-meeting12:46
*** pnavarro has joined #openstack-meeting12:48
*** ytwu has quit IRC12:48
*** dprince has joined #openstack-meeting12:48
*** ytwu has joined #openstack-meeting12:49
*** ytwu1 has quit IRC12:50
*** ruhe has quit IRC12:50
*** jaimegil has quit IRC12:56
*** edmund has joined #openstack-meeting12:56
*** anteaya has joined #openstack-meeting12:59
*** dkehn_ has joined #openstack-meeting13:00
*** dkehn has quit IRC13:01
*** xBsd has joined #openstack-meeting13:02
*** dkehn_ is now known as dkehn13:02
*** romcheg has quit IRC13:04
*** ytwu1 has joined #openstack-meeting13:07
*** ytwu has quit IRC13:08
*** lbragstad has joined #openstack-meeting13:09
*** whenry has joined #openstack-meeting13:11
*** romcheg has joined #openstack-meeting13:12
*** ytwu has joined #openstack-meeting13:12
*** woodspa_ has joined #openstack-meeting13:13
*** jecarey_ has joined #openstack-meeting13:13
*** jecarey has quit IRC13:14
*** ytwu1 has quit IRC13:14
*** psedlak has joined #openstack-meeting13:14
*** woodspa has quit IRC13:16
*** nijaba has quit IRC13:17
*** doron_afk is now known as doron13:18
*** nijaba has joined #openstack-meeting13:18
*** doron is now known as doron_afk13:22
*** spzala has joined #openstack-meeting13:23
*** neelashah has joined #openstack-meeting13:23
*** abaron has quit IRC13:23
*** henrynash has joined #openstack-meeting13:24
*** ryanpetrello has joined #openstack-meeting13:27
*** sushils has quit IRC13:29
*** zul has quit IRC13:29
*** sushils has joined #openstack-meeting13:29
*** ruhe has joined #openstack-meeting13:31
*** krtaylor has quit IRC13:36
*** changbl_ has joined #openstack-meeting13:36
*** pentameter has joined #openstack-meeting13:36
*** doron_afk is now known as doron13:37
*** abaron has joined #openstack-meeting13:37
*** ytwu1 has joined #openstack-meeting13:41
*** zehicle_at_dell has quit IRC13:41
*** markpeek has joined #openstack-meeting13:43
*** egallen has joined #openstack-meeting13:43
*** ytwu has quit IRC13:44
*** dscannell has joined #openstack-meeting13:44
*** woodspa__ has joined #openstack-meeting13:49
*** dcramer_ has joined #openstack-meeting13:50
*** garyk has joined #openstack-meeting13:50
*** writerDi_ has joined #openstack-meeting13:50
*** changbl_ has quit IRC13:50
*** woodspa_ has quit IRC13:52
*** vijendar has joined #openstack-meeting13:52
*** Tacho has joined #openstack-meeting13:52
*** MarkAtwood has joined #openstack-meeting13:57
*** markwash has joined #openstack-meeting13:57
*** ytwu has joined #openstack-meeting13:59
*** ytwu1 has quit IRC14:00
garykboris-42: is the scheduling meeting now?14:00
garykn0ano: ping14:01
n0anogaryk, ack14:01
garykn0ano: thanks!14:01
garykmy apoligies for not making the last few.14:01
n0anoBTW, scheduling meeting is an hour from now14:01
n0anoNP, we just deferred things to today14:01
garykoops. will join in an hour14:01
garykthanks14:01
boris-42garyk hi14:02
boris-42hi all+014:02
*** vkmc has joined #openstack-meeting14:03
garykboris-42: i got the time mixed up. the meeting is in another hour14:04
*** jecarey_ has quit IRC14:04
*** dscannell has quit IRC14:05
*** romcheg has quit IRC14:05
*** dkranz has quit IRC14:05
*** ytwu1 has joined #openstack-meeting14:08
*** ytwu has quit IRC14:09
*** galstrom_zzz is now known as galstrom14:10
*** ytwu has joined #openstack-meeting14:10
*** ytwu1 has quit IRC14:12
*** romcheg has joined #openstack-meeting14:13
*** ytwu1 has joined #openstack-meeting14:14
*** rnirmal has joined #openstack-meeting14:14
*** ytwu has quit IRC14:14
*** noslzzp has joined #openstack-meeting14:14
*** spzala has quit IRC14:14
*** lastidiot has joined #openstack-meeting14:14
*** nijaba has quit IRC14:15
*** psedlak has quit IRC14:15
*** edmund has quit IRC14:16
*** krtaylor has joined #openstack-meeting14:17
*** stevemar has joined #openstack-meeting14:17
*** venkatesh has joined #openstack-meeting14:17
*** yaguang has joined #openstack-meeting14:17
*** markmcclain has joined #openstack-meeting14:18
*** nijaba has joined #openstack-meeting14:19
*** wolfdreamer has joined #openstack-meeting14:20
*** wolfdreamer has left #openstack-meeting14:21
*** epim has joined #openstack-meeting14:22
*** esker has joined #openstack-meeting14:23
*** ytwu has joined #openstack-meeting14:23
*** jecarey has joined #openstack-meeting14:24
*** burt has joined #openstack-meeting14:24
*** ytwu1 has quit IRC14:26
*** zul has joined #openstack-meeting14:26
*** lastidiot has quit IRC14:27
*** thomasbiege has joined #openstack-meeting14:27
*** yaguang has quit IRC14:28
*** xBsd has quit IRC14:28
*** mdenny has joined #openstack-meeting14:28
*** markvan has joined #openstack-meeting14:30
*** ytwu1 has joined #openstack-meeting14:32
*** colinmcnamara has joined #openstack-meeting14:33
*** ytwu has quit IRC14:33
*** dscannell has joined #openstack-meeting14:36
*** cody-somerville_ is now known as cody-somerville14:38
*** debo_os has joined #openstack-meeting14:40
*** yaguang has joined #openstack-meeting14:40
*** stevemar has quit IRC14:40
*** ytwu has joined #openstack-meeting14:40
*** ytwu1 has quit IRC14:41
*** tanisdl has joined #openstack-meeting14:41
*** adrian_otto has joined #openstack-meeting14:42
*** doron is now known as doron_afk14:43
*** ytwu1 has joined #openstack-meeting14:44
*** tianst has joined #openstack-meeting14:45
*** ytwu has quit IRC14:47
*** doron_afk has quit IRC14:47
*** colinmcnamara has quit IRC14:47
*** ruhe has quit IRC14:48
*** ytwu has joined #openstack-meeting14:48
*** epim has quit IRC14:48
*** ytwu1 has quit IRC14:49
*** esker has quit IRC14:49
*** obondarev has quit IRC14:49
*** otherwiseguy has joined #openstack-meeting14:50
*** changbl_ has joined #openstack-meeting14:51
*** colinmcnamara has joined #openstack-meeting14:51
*** danwent has joined #openstack-meeting14:52
*** egallen has quit IRC14:54
*** ytwu1 has joined #openstack-meeting14:55
*** noslzzp has quit IRC14:56
*** sushil_ has joined #openstack-meeting14:56
*** ytwu has quit IRC14:56
*** eharney has joined #openstack-meeting14:57
*** romcheg has left #openstack-meeting14:57
*** noslzzp has joined #openstack-meeting14:58
*** Yada has joined #openstack-meeting14:58
*** sushils has quit IRC14:58
*** abaron has quit IRC14:58
*** IlyaE has joined #openstack-meeting14:59
n0ano#startmeeting scheduler14:59
openstackMeeting started Tue Aug  6 14:59:52 2013 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: scheduler)"14:59
openstackThe meeting name has been set to 'scheduler'14:59
*** lpabon has joined #openstack-meeting15:00
n0anoanyone here for the scheduler meeting?15:00
*** PhilDay has joined #openstack-meeting15:00
debo_osHi this is Debo15:00
debo_osfor the scheduler meeting15:00
*** sushil_ has quit IRC15:00
debo_osI am covering for Senhua who left the Openstack world for now :)15:01
* glikson here15:01
n0anodebo_os, NP, just waiting for people to gather15:01
*** sushils has joined #openstack-meeting15:01
garykhi all15:02
*** rongze_ has quit IRC15:02
*** llu-laptop has joined #openstack-meeting15:02
*** PaulMurray has joined #openstack-meeting15:02
*** funzo_ has joined #openstack-meeting15:02
n0ano#topic instance groups15:03
*** openstack changes topic to "instance groups (Meeting topic: scheduler)"15:03
n0anogaryk, I believe this was your issue15:03
garykn0ano: yes, that is correct15:03
n0anocare to expand upon it a little15:03
garyki just wanted to bring everybody up to date with our developments and bottlenecks15:04
*** markwash has quit IRC15:05
garykn0ano: the BP is https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension15:05
garykand the wiki is https://wiki.openstack.org/wiki/GroupApiExtension15:05
*** ruhe has joined #openstack-meeting15:05
*** adrian_otto has quit IRC15:05
garykat the moment we the DB support approved in H215:05
garykthe API was looking good until we were asked to use the object model.15:06
garykthat was a blocking feature about 3 weeks ago.15:06
garykwe have added the support - https://review.openstack.org/#/c/38979/ and are planning to update the API to use this15:06
debo_osI am updating the API extn based on the support15:07
garykIn addition to this the schsuling support has been added (was approved and then reverted) and is now back in reveiw15:07
garykhttps://review.openstack.org/#/c/33956/15:07
garykAt the moment my concern is that this feature, which we decided at the portland summit was importnat, may not make the H3 cut due to the issue that are out of our control.15:07
*** lastidiot has joined #openstack-meeting15:08
garyki wanted to know if there is anyway that we can get some help here with the review process and the issue of the object.15:08
*** bdpayne has joined #openstack-meeting15:08
garyksorry - obuject support (this is added and we'll integrate in the coming days - just feels like we are going to default on this)15:08
n0anoreviews are always an issue, just rattle the cages here and on the mailing list is the best technique15:08
n0anomore interesting is your problem, is that with the object model and, if so, what's the issue?15:09
PhilDay@garyk - in terms of polices within a group, what is implemented at the moment ?15:09
garykn0ano: the API patch was nacked due to the fact that it had direct access with the database15:09
garykPhilDay: at the moment anti affinity is in the review process15:09
garykPhilDay: Jay Lau want to add affinity host support above this15:10
PhilDay@garyk - Ok thanks, and I assume that builds on the exiting filter ?15:10
garykPhilDay: we are also planning network proximity - but that will certainly not be in the H cycle15:10
*** yaguang has quit IRC15:10
garykPhilDay: yes, they are both using existing filters, they are now hooking into the databse structure for instance group management.15:11
garykprior to that it was an ugly hack15:11
PhilDayIt was the network proximity reference in the wiki that made me ask the question - I didn't remember seeing anything related to that in the code15:12
garykPhilDay: it was something we discussed at the sumiit and was in the queue for development.15:12
garyki guess that we can discuss that part at the next summit.15:12
PhilDay@garyk - thansk for the clarification - so this set of changes is really about tidying up the group management15:13
garykPhilDay: correct.15:13
n0anowell, tigying up except for the nack on the API change, that seems rather significant, do you have an alternative15:13
garykmy concern is making the cut for the H cycle. I feel that we are being unlucky with various changes in Nova out of our control (for example the usage of objects)15:13
garykn0ano: not sure i understand15:14
n0anoyou said they nacked because of direct access to the DB, what's your alternative to that?15:15
garykn0ano: we have implemented the object support. We are in the process of integrating this into the API layer. Now it is just the review process.15:15
garykis theer anyway that we can get a core reviewer assigned to this?15:16
n0anoI not a core reviewer so I can't help, have you asked on the mailing list15:17
garykin neutron we do this - that is, a core reviewr is assigned to developments15:17
*** reed has joined #openstack-meeting15:17
*** dkranz has joined #openstack-meeting15:17
garykn0ano: i do not have anything to add. maybe dabo or glikson have something to add15:18
garyksorry debo_os not dabo15:18
*** nijaba has quit IRC15:18
*** kroberts has joined #openstack-meeting15:19
*** nijaba has joined #openstack-meeting15:19
*** nijaba has joined #openstack-meeting15:19
n0anowell, there's the Nova meeting this Thurs, you could ask for reviewers there, that meeting worries about scheduling/review issues15:20
garykn0ano: ok, will do. i'll try and attend - the hours are crazy for us15:20
debo_osWell I am updating the API code based on Gary's patch and I would second Gary about the core reviewer15:20
n0anogaryk, I'll be at the meeting, if you don't make it I'll be sure to raise your review issue15:21
debo_osand his comments ....15:21
garykn0ano: thanks! much appreciated15:21
n0anoNP15:21
n0anoUnless there's more on this...15:21
n0ano#topic overall scheduler plan15:22
*** openstack changes topic to "overall scheduler plan (Meeting topic: scheduler)"15:22
n0anoThis was more jog0 issue but we talked about it a little at the last meeting and I suggested everyone think about it15:22
*** jcoufal has quit IRC15:23
n0anothere are a lot of random BPs out against the scheduler, does it make sense to come up with a more unified plan for the scheduler15:23
garykn0ano: agreed.15:24
*** fnaval_ has quit IRC15:24
garykn0ano; i think that the details that boris-42 posted are very imported and highlight some serious issues15:24
n0anowhich details were you thinking of?  I'm concerned about scaling issues myself.15:25
*** jmontemayor has joined #openstack-meeting15:25
boris-42garyk out meeting time hi all15:25
PhilDayCan you repeat (or point to boris-42's comments) ?15:25
*** egallen has joined #openstack-meeting15:25
boris-42n0ano scaling + flexibility15:25
garykboris-42: can you please post the link to your doc15:25
boris-42garyk one sec15:25
n0anowell, I think the current deisgn (plugable filters/weights) is pretty flexible, not so sure about it scalability15:26
*** jtomasek has quit IRC15:26
boris-42nano no it is not flexible15:26
debo_oshave folks done scalabiity tests and posted results somewhere15:26
boris-42debo_os we are going to test on real deployments15:26
boris-42debo_os different approaches15:26
boris-42debo_os and show results on HK summit15:27
n0anodebo_os, yes/no, bluehost did some work but their environment is unique enough that some people don't think their results apply in general15:27
*** egallen has quit IRC15:27
boris-42nano they rewrite half openstack=)15:27
boris-42n0ano *15:27
n0anoboris-42, indeed15:27
boris-42by the way they are agree with our approach15:28
PhilDayThey also don't really schedule as such - they place onto specific hosts15:28
boris-42https://docs.google.com/a/mirantis.com/document/d/1_DRv7it_mwalEZzLy5WO92TJcummpmWL4NWsWf0UWiQ/edit15:28
n0anoboris-42, when you say `real deployments', what kind of scale are you talking about15:28
*** yaguang has joined #openstack-meeting15:28
boris-42we would like to test on 10-30k nodes15:28
PaulMurrayboris-42 it would be good to know where performance problems are as well as just straight scale measures15:28
boris-42at least just use case of creating instances15:28
boris-42ahaha15:28
PaulMurrayIs that in your plan?15:28
boris-42whole openstack is one big botleneck=)15:29
PaulMurray:)15:29
PaulMurrayI noticed15:29
n0anoboris-42, now, now :-)15:29
boris-42first problem are periodic_tasks15:29
boris-42second scheduler15:29
boris-42and then we will see=)15:29
n0anoboris-42, indeed, I still need to create a BP to remove the periodic scheduler update, we're in violent agreement there15:30
boris-42actually we almost finished new version of scheduler15:30
boris-42DOC is a little bit out of date15:30
boris-42we are going to store data not locally15:30
boris-42in scheduler15:30
garykboris-42: there are a number of bottlenecks and they can be dealt with15:30
boris-42but in distributed master-master memcached15:30
n0anomore problematic is your idea to remove the DB, there is a significant group of opionion that fan-out to the scheduler is wrong and storing state in the DB is right15:30
PhilDayIs there a BP / review for that work boris-42 ?15:31
garykthe scheduler is certainly one and has a number of shortcomings. i guess it is a process to get this straight.15:31
*** vijendar has quit IRC15:31
boris-42DB is botleneck15:31
garykthese would be good topis for the up and coming summit15:31
boris-42there is no fanout15:31
*** markmcclain has quit IRC15:31
debo_ossorry I am a scheduler noob ... but is the main issue the central DB and the fact that its embedded into nova15:31
*** mrunge has quit IRC15:32
boris-42we will produce N/(PERIODIC_TASK_TIME*SCHEDULERS_COUNT) requests to schedulers15:32
llu-laptopboris-42: if no fanout, than how all schedulers can get the same compute node's upate?15:32
boris-42memcached15:32
n0anoso you're replacing the DB with memcached15:32
boris-42we will use one memchaced for all shceudlers15:32
boris-42and scheduler will keep all data15:32
boris-42not nova15:32
*** edmund has joined #openstack-meeting15:33
PaulMurrayboris-42 what do you mean not nova - is this cheduler outside nova?15:33
PhilDaySo running memcached will become a requirement for all Nova installs - or is this an optional new scheduler ?15:34
*** psedlak has joined #openstack-meeting15:34
*** zehicle_at_dell has joined #openstack-meeting15:34
garykboris-42: i am not sure that memcached is a solution. but i think that the design is more importnat than the implementations at the moment15:34
PhilDay(Just thinking that elsewhere memcahce has been an option, not a requirement so far)15:34
boris-42PhilDay We will implement only for memchached (but you are able to impelemtn realization for others backends)15:34
debo_osboris-42: well memcached or any other distributed low latency DB :)15:34
boris-42yes15:34
boris-42debo_os ^15:34
boris-42there will be interface15:35
boris-42with get(), put(), and get_all() methos15:35
debo_osof course15:35
boris-42you could implement it for mysql even=)15:35
boris-42but we choose memcached=)15:35
PhilDaySo this is an alternative to the filter scheduler - or a new version / replacement for the filter scheduler ?15:35
boris-42for 1 example15:35
debo_osis there a version build with memcached15:35
boris-42PhilDay we are going step by step to change scheduler in next way15:35
boris-421. Remove compute_node_get_all methods, and add one new rpc methods to scheduler, update_node()15:36
boris-42and use schedulers DB to store all infromation15:36
boris-42So the mechanism will be the same15:36
boris-422. Cleanup Nova (to remove data from compute_node)15:37
boris-42and periodic tasks15:37
n0anoso, rather than the compute nodes updating a DB you're going to send the data to a scheduler so it can update the DB - how is that faster15:37
boris-42Memcahced is faster15:37
boris-42we will show real results from real big deployment15:37
n0anoand your scheme will work with multiple schedulers?15:38
boris-423. Add more flexibility shceudler.compute_update() could be called from different projects15:38
boris-42n0ano yes of course15:38
boris-424. Use data from different source, as first cinder15:38
n0anowhich means you are doing a fan-out message15:38
boris-42no15:39
boris-42fan-out means compute nodes -> all scheduler15:39
*** anniec has quit IRC15:39
PhilDaySo for step 1 the scheduler(s) will still update the existing DB - and then you'll make memcache an optional alternative Db driver for the scheduler ?15:39
boris-42we are doing compute nodes -> one of the scheduler -> memchacned15:39
llu-laptopboris-42: so other schedulers read from memcached?15:39
boris-42PhilDay I mean there will be 3 pathces =)15:39
boris-42PhilDay baby steps style=)15:39
boris-42llu-laptop all schedulers are connected to one distributed memcached15:40
debo_osbut what state are you planning to store15:40
n0anoyou do have the issues of master scheduler dies, who takes over and how do you do the hand off15:40
debo_osfor starters it will be a replica of the db state for now, right?15:40
PhilDayStep style is good :-)   Just want to also see that steps introduce options rather that force a change in deployment15:40
boris-42there is no master scheduler15:40
debo_osI think we should have a layer to isolate the scheduler and the state stuff ... then it wont matter15:41
boris-42debo_os it want metter15:41
boris-42already15:41
n0anoonly one scheduler recieves messages and updates memcached => that's the master15:41
boris-42We have memcached that is distributed15:41
boris-42no15:41
boris-42nano let me describe more carefull15:41
debo_osagree memcache is just the store, rioght ....15:41
debo_osinstead of a slow DB u have memcache which could have been redis too or couch15:42
debo_osso the point is why mandate just memcache15:42
boris-42We have some KEY_VALUE storage15:42
n0anoeverybody take a deep breath and pause for a minute15:42
debo_oshave a state API15:42
boris-421 KEY_VALUE storage15:42
*** hartsocks has joined #openstack-meeting15:42
boris-42distributed fast and such things15:42
boris-42we have A lot of schedulers15:42
boris-42we have one RPC queue15:42
debo_osok thats good .. have a pure keyval api and maybe not mandate specific memcache etc15:42
boris-42for shceudlers15:42
boris-42all schedulers are getting one by one message from qeueu15:43
n0anoI believe boris-42 has a detailed write up, we gave the link above, may I suggest we all read that write up, understand it, and come back next week to talk about it in detail15:43
boris-42and update global DB15:43
debo_osdo you have  a doc with this new design you are doing ....15:43
debo_osyeah15:43
boris-42n0ano we should update part about using memcahed15:43
*** hartsocks has left #openstack-meeting15:43
boris-42n0ano our first variant was without memcached15:44
*** colinmcnamara has quit IRC15:44
boris-42and fan-out15:44
n0anowhat I've hearing is a lot of confusion that, hopefully, is cleared up a bit by the write up15:44
*** beagles has quit IRC15:44
boris-42n0ano We will update our DOC soon ok?) not it describes solution with fan-out and without KEY-Value storage15:45
*** vijendar has joined #openstack-meeting15:45
*** hartsocks has joined #openstack-meeting15:45
boris-42n0ano could I ping you, after we update our doc?)15:45
n0anothat would be good as those are areas that are confusing.15:46
*** hartsocks has left #openstack-meeting15:46
n0anoboris-42, please do ping me, yes15:46
boris-42n0ano yeah that was result of common discussion with Mke (from BlueHost)15:46
n0anothis is good area but I want to make sure we can have a productive discussion about it.15:47
boris-42n0ano sure15:47
boris-42nods=)15:47
n0anolet's move on (note that everyone needs to do homework before the next meeting :-)15:47
PhilDayCan we all get pinged when the doc is updated ?15:47
n0ano#topic multiple active scheduler policies15:47
*** openstack changes topic to "multiple active scheduler policies (Meeting topic: scheduler)"15:47
n0anoI don't think we completely finished the discussion last week, were there anymore issues anyone here is concerned about this topic?15:48
gliksonwe've recently submitted a new patch15:48
*** fnaval_ has joined #openstack-meeting15:48
gliksonhttps://review.openstack.org/#/c/37407/15:49
n0anoare you getting reviewers :-)15:49
gliksonthe implementation now is rather different than the original idea, but still..15:49
*** armax has joined #openstack-meeting15:49
*** venkatesh has quit IRC15:49
gliksonwe've got Russell's -2 :-)15:49
n0anowell, that's attention anyway15:50
gliksonwhich he didn't remove yet. hopefully the last patch addressess the main concerns, and we will be able to make progress.15:50
*** ociuhandu has joined #openstack-meeting15:50
n0anohow did the implementation change, in a nutshell15:50
gliksonnow we just specify scheduler options in flavor extra spec15:51
gliksonno pre-defined configurations/policies in nova.conf, no association with aggregates..15:51
n0anoso the user can select scheduler policies that are created by the administrator, I guess that's OK15:51
*** sarob has joined #openstack-meeting15:52
gliksonso, for example, you can define a flavor with CoreFilter and cpu_allocation_ration=2.0, and another different set of parameters15:52
glikson(yes, "you"=admin")15:53
PaulMurrayglikson these things will be visible to users yes?15:53
gliksonthen, one can use existing AggregateInstanceExtraSpec to map to aggregates15:53
gliksonPaulMurray: we are suggesting not to return these properties for non-admin users.15:54
PaulMurrayok, i see15:54
n0anoglikson, how would you do that, flavors are visible to all15:54
gliksonn0ano: in the api. the behavior is often different between admin and non-admin, so we added another "if"..15:55
gliksoneveryone see the flavor15:55
gliksonjust some of the extra specs are not shown15:55
gliksonif you are not an admi15:55
*** AlanClark has joined #openstack-meeting15:55
gliksonn15:55
PhilDayThere is an APi extension which determines if the extra-spec values are availabel or not - is that enough ?15:55
PaulMurrayextra extra specs :)15:55
gliksonPhilDay: you mean, all the extra specs?15:56
n0anough, I don't really like that but I'm not going to argue against it, just seems wrong15:56
*** tianst has quit IRC15:56
PaulMurrayIs there some drift going on here....15:56
PaulMurrayI mean are things being used in a way there were not meant to rather15:57
PaulMurray...in order to fit15:57
PhilDayI didn't say I liked it either :-)    Just feels like extra specs might be now being pulled in many different ways15:57
n0anoPaulMurray, well, extra specs has always been a catch all but, with the scope applied to the keys, it sort works out OK15:57
*** whenry has quit IRC15:57
n0anos/sort/sort of15:58
gliksonwe are adding namespace to the new keys15:58
*** jcoufal has joined #openstack-meeting15:58
n0anoglikson, you better :-)15:58
n0anosorry guys but we're coming up to the hour15:58
gliksonI am not sure this is the ideal solution -- but this seemed to be the preferred approach from the feedbacks we received15:58
*** kebray has joined #openstack-meeting15:59
PhilDaySo maybe the extra_spec APi exnesion should be updated to allow the admin to define which namespaces are exposed - rather than it being an all or nothing15:59
n0anoI'd like to thank everyone and we'll talk again next week (feel free to email me with agenda suggestions)15:59
*** PhilDay has quit IRC15:59
gliksonPhilDay: interesting idea. hopefully our patch will not be blocked until it is implemented :-)15:59
n0ano#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Tue Aug  6 15:59:58 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-08-06-14.59.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-08-06-14.59.txt16:00
*** beagles has joined #openstack-meeting16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-08-06-14.59.log.html16:00
*** PaulMurray has quit IRC16:00
*** llu-laptop has quit IRC16:00
*** Yada has quit IRC16:01
*** mrodden has quit IRC16:02
*** lexinator has joined #openstack-meeting16:03
*** epim has joined #openstack-meeting16:05
*** sarob_ has joined #openstack-meeting16:08
*** sarob has quit IRC16:08
*** virajh has joined #openstack-meeting16:11
*** ytwu has joined #openstack-meeting16:12
*** ytwu1 has quit IRC16:12
*** mrodden has joined #openstack-meeting16:12
*** jlucci has joined #openstack-meeting16:13
*** jlucci has quit IRC16:14
*** glikson has quit IRC16:17
*** nijaba has quit IRC16:19
*** nijaba has joined #openstack-meeting16:19
*** sarob_ has quit IRC16:21
*** sarob has joined #openstack-meeting16:22
*** dkranz has quit IRC16:22
*** hemna_ has quit IRC16:22
*** hemna has joined #openstack-meeting16:23
*** tkammer has quit IRC16:24
*** funzo_ is now known as funzo16:24
*** lexinator has quit IRC16:24
*** lexinator has joined #openstack-meeting16:24
*** yaguang has quit IRC16:27
*** ytwu has quit IRC16:28
*** glikson has joined #openstack-meeting16:28
*** lexinator has quit IRC16:28
*** lexinator has joined #openstack-meeting16:30
*** abaron has joined #openstack-meeting16:35
*** dkranz has joined #openstack-meeting16:35
*** sdake_ has joined #openstack-meeting16:36
*** debo_os has quit IRC16:36
*** spzala has joined #openstack-meeting16:37
*** thomasbiege has quit IRC16:37
*** sandywalsh has quit IRC16:39
*** yaguang has joined #openstack-meeting16:40
*** boris-42 has quit IRC16:41
*** SumitNaiksatam has quit IRC16:42
*** zul has quit IRC16:43
*** abaron has quit IRC16:46
*** eharney has quit IRC16:48
*** gyee has joined #openstack-meeting16:48
*** krtaylor has quit IRC16:53
*** sandywalsh has joined #openstack-meeting16:55
*** markwash has joined #openstack-meeting16:57
*** cwolferh has joined #openstack-meeting16:59
*** yaguang has quit IRC16:59
*** sandywalsh has quit IRC17:00
*** lexinator has quit IRC17:00
*** dkranz has quit IRC17:00
*** funzo is now known as funzo|brb17:02
*** eharney has joined #openstack-meeting17:03
*** markpeek has quit IRC17:04
*** ruhe has quit IRC17:04
*** markpeek has joined #openstack-meeting17:04
*** lexinator has joined #openstack-meeting17:06
*** SumitNaiksatam has joined #openstack-meeting17:06
*** dosaboy_alt has quit IRC17:07
*** cdub_ has joined #openstack-meeting17:08
*** lpabon_ has joined #openstack-meeting17:10
*** terriyu has joined #openstack-meeting17:10
*** lpabon_ has quit IRC17:12
*** lpabon has quit IRC17:12
*** lpabon has joined #openstack-meeting17:12
*** sandywalsh has joined #openstack-meeting17:13
*** zul has joined #openstack-meeting17:13
*** mrunge has joined #openstack-meeting17:15
*** derekh has quit IRC17:15
*** glikson has quit IRC17:16
*** dkranz has joined #openstack-meeting17:16
*** nijaba has quit IRC17:19
*** yaguang has joined #openstack-meeting17:19
*** nijaba has joined #openstack-meeting17:20
*** nijaba has quit IRC17:20
*** nijaba has joined #openstack-meeting17:20
*** afazekas has joined #openstack-meeting17:20
*** nati_ueno has joined #openstack-meeting17:23
*** IlyaE has quit IRC17:27
*** danwent has quit IRC17:27
*** krtaylor has joined #openstack-meeting17:31
*** danwent has joined #openstack-meeting17:31
*** SergeyLukjanov has quit IRC17:32
*** SergeyLukjanov has joined #openstack-meeting17:33
*** ruhe has joined #openstack-meeting17:33
*** ruhe has quit IRC17:34
*** SergeyLukjanov has quit IRC17:34
*** Mandell has joined #openstack-meeting17:36
*** ivar-lazzaro has joined #openstack-meeting17:38
*** yaguang has quit IRC17:38
*** mrunge has quit IRC17:38
*** RajeshMohan has quit IRC17:39
*** vipul is now known as vipul-away17:40
*** debo_os has joined #openstack-meeting17:40
*** funzo|brb is now known as funzo17:40
*** RajeshMohan has joined #openstack-meeting17:41
*** sadasu has joined #openstack-meeting17:41
*** stevemar has joined #openstack-meeting17:42
*** jpich has joined #openstack-meeting17:43
*** sadasu has quit IRC17:43
*** thomasbiege has joined #openstack-meeting17:43
*** thomasbiege1 has quit IRC17:44
*** jrodom has joined #openstack-meeting17:46
*** ruhe has joined #openstack-meeting17:47
*** ndipanov is now known as ndipanov_gone17:49
*** arunkant has joined #openstack-meeting17:49
*** glikson has joined #openstack-meeting17:50
*** fabio has joined #openstack-meeting17:51
*** arunkant has quit IRC17:52
*** arunkant has joined #openstack-meeting17:52
*** debo_os has quit IRC17:53
*** salv-orlando has quit IRC17:53
*** bknudson has joined #openstack-meeting17:55
*** dkranz has quit IRC17:57
ayoungKeystone powers active!17:59
*** brich1 has joined #openstack-meeting17:59
henrynashengage17:59
lbragstadhey18:00
*** boris-42 has joined #openstack-meeting18:00
bknudsonhi18:00
*** dolphm has joined #openstack-meeting18:00
henrynashhi there18:00
gyeeayoung, that a pokemon thing?18:00
dolphmam i in the wrong meeting?18:00
*** topol has joined #openstack-meeting18:00
ayounggyee, a little bit before pokemon18:01
topolHi18:01
dolphmhttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:01
gyeehe-man18:01
ayounggyee, even earlier.  Child of 1970s bad cartoons.18:02
gyeeway out of my demographic18:02
*** gkotton has joined #openstack-meeting18:02
dolphm#startmeeting keystone18:02
topolwhat was the 1970 bad cartoon. Ive seen them all18:02
openstackMeeting started Tue Aug  6 18:02:34 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
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
*** afazekas has quit IRC18:02
dolphmhenrynash: thanks for last week!18:02
*** vipul-away is now known as vipul18:02
fabioHi18:03
henrynashdolphm: no18:03
henrynashdolphm: np (!)18:03
*** sarob has quit IRC18:03
dolphmlol18:03
* topol awkward18:03
spzalaHi!18:03
*** sarob has joined #openstack-meeting18:03
ayoungthis is turning into a real community effort.18:03
dolphmforgive me, i'm still getting back up to speed :)18:03
henrynashdolphm: (that'l teach me to type with apple pie and custard in one hand)18:03
*** kebray has quit IRC18:04
*** garyk has quit IRC18:04
dolphmhenrynash: you should use a plate18:04
*** gkotton is now known as garyk18:04
henrynashdolphm: yes, it is a bit gooey18:04
dolphmhenrynash: and maybe a desk18:04
gyeehenrynash, what's on your *other hand*? :)18:04
henrynashdolphm: bad boy18:04
*** divyeshk has joined #openstack-meeting18:04
dolphmi definitely want to go through havana-3 BP's today, but that can just be open discussion18:05
henrynashgyee: bad boy18:05
*** markmcclain has joined #openstack-meeting18:05
dolphm#topic Critical issues18:05
*** openstack changes topic to "Critical issues (Meeting topic: keystone)"18:05
ayoungNo critical bugs as of right now18:05
dolphmi'm way behind on triaging new bugs though :(18:05
gyeedolphm, I filed one for auth_token middleware, apparently we are using v2.0 for admin token18:06
dolphmif anyone is aware of an issue that's still New, feel free to mention it18:06
dolphmgyee: link?18:06
ayoungdolphm, I've been doing abit of triage.  Please feel free to assign any LDAP based bugs you come across to me, to include stuff on the mixed Identity backend18:06
gyeehttps://bugs.launchpad.net/bugs/120792218:06
uvirtbotLaunchpad bug 1207922 in python-keystoneclient "auth_token middleware always use v2.0 to request admin token" [Undecided,Confirmed]18:06
gyeedolphm, I am about to file another one18:06
dolphmgyee: that's not immediately breaking something though, right?18:07
gyeewe should not be using httplib in auth_token middleware anymore as it does not validate server cert18:07
gyeethat might be a security issue18:07
dolphmgyee: there's a bug and bp for that already18:07
*** kebray has joined #openstack-meeting18:07
dolphmgyee: i think it's assigned to jamielennox18:07
*** sarob has quit IRC18:07
gyeedolphm, oh ok, that's good18:08
ayoungdolphm, he's working on it, and a lot of client related issues18:08
dolphmayoung: +118:08
*** rcrit has joined #openstack-meeting18:08
ayoungdolphm, he broke his work up in to a series of reviews.18:08
dolphmi'll assume there's nothing too exciting going on, but again... i had literally 100+ emails from launchpad about bugs when i got back lol18:08
ayoungdolphm, last week I was haranguing the core keystone devs to do more client reviews18:08
ayoungso y'all consider yourselves re-harangued:  do more client reviews18:09
dolphmayoung: thanks! the client should really get more of everyone's attention than it does18:09
gyeeyes absolutely18:09
ayoungdolphm, so the problem is that I think people don't really understand how the client is put together until they deep dive it18:10
* dolphm harangue18:10
*** dkranz has joined #openstack-meeting18:10
morganfainbergayoung: thankfully diving into it isn't too bad.18:10
ayoungdolphm, maybe next week we put a few minutes aside for a walk through?18:10
topolayoung +118:10
dolphmayoung: during the meeting?18:10
lbragstadayoung: +118:10
ayoungdolphm, it is the only time we have everyone together.  Either then, or a special one off/18:11
topolI have a callin number. would we use that?18:11
morganfainbergayoung: i'd think a special one off might be easier.18:11
ayoungI think it might be time well spent.  And, morganfainberg is right, it isn't that bad18:11
topolor is it an irc based walkthrough?18:11
morganfainbergayoung: we can setup webex/g2meeting or something with audio as well, might help.18:11
ayoungtopol, I think IRC would be sufficient18:11
*** slavayssiere has quit IRC18:11
dolphmsure, if someone wants to coordinate something, this would be the best place to promote it, but i'm not sure it's the best venue to conduct it18:11
morganfainbergi'll defer if you think IRC is suffcient though18:11
ayoungI'm partial to elluminate myself18:11
* dolphm always happy to answer questions on irc18:12
ayoungdolphm, cool, put down an action item and I'll try to arrainge18:12
gyeecom'on ppl, topol is offering his bridge18:12
dolphm#action ayoung to coordinate client walkthrough18:12
gyeetake advantage of it!18:12
topolgyee +118:12
ayoungideally, we would get jamielennox there, which makes it a little late for the Europe folks18:12
dolphm#action topol to make bridges18:12
stevemartopol, gyee +118:12
gyeefor one, I like to hear ayoung's voice18:12
ayounggyee, you lie18:12
gyeemake sure his real18:12
* ayoung lies too18:12
morganfainberggyee: lol18:12
dolphmwhat's jamielennox's time zone?18:13
ayoungdolphm, brisbane australia18:13
dolphmoh wow18:13
topoldo we want a web conference as well or just abridge?18:13
bknudsonrecord it and then we can watch it whenever18:13
ayoung 4:13 AM for him right now18:13
dolphmbknudson: +118:13
lbragstadbknudson: +118:13
morganfainbergbknudson: +118:13
dolphm(who put bp notifications on the agenda?)18:13
lbragstadme18:13
dolphm#topic bp notifications18:14
*** openstack changes topic to "bp notifications (Meeting topic: keystone)"18:14
dolphm#link https://blueprints.launchpad.net/keystone/+spec/notifications18:14
lbragstadGot keystone running in apache per ayoung and bknudson notes. Pulled in the latest olso notifier and dependencies. Applied the logging fix to remove eventlet issues in keystone/openstack/common/local.py. Applied notifications module and tested with tenants on CUD, first step, tested with log notifier, then tested with rpc notifier. Applied a patch to https://github.com/openstack/oslo-incubator/blob/master/openstack/common/rpc/amqp.18:14
ayoungdolphm, with the exception of henrynash I think we are all US eastern or later.  Our team meets at 5:30 PM on Modnay, and he can make that meeting18:14
*** xBsd has joined #openstack-meeting18:14
*** ociuhandu has left #openstack-meeting18:14
lbragstadthe short of it.. the current olso notification implementation works in keystone apache httpd18:14
lbragstadfor tenant create, update, and delete18:14
ayounglbragstad, nice18:14
dolphmlbragstad: yay!18:14
morganfainberglbragstad: nice.18:14
bknudsonlbragstad: is the code posted for review?18:15
ayounglbragstad, do I need to remove a -2 somewhere then?18:15
dolphmlbragstad: should notifications be targetted at havana-m3 then?18:15
dolphmlbragstad: probably lol18:15
*** jmontemayor has quit IRC18:15
dolphmayoung: * ^18:15
*** glikson has quit IRC18:15
lbragstadno, it's strung together in like 6 commits on my local branches18:15
lbragstadI have to fix something i Oslo18:15
lbragstadin oslo18:15
dolphmi guess https://blueprints.launchpad.net/keystone/+spec/unified-logging-in-keystone should be targetted first18:15
lbragstaddolphm: correct18:15
lbragstadthat *needs* to be fixed18:15
dolphmlbragstad: is that a realistic goal?18:16
ayounglbragstad, are you planning on  submitting them as 6 commits, or squashing?18:16
dolphmlbragstad: one or both for m318:16
*** jhenner has joined #openstack-meeting18:16
lbragstadI am going to have to clean them up and submit them individually18:16
*** SergeyLukjanov has joined #openstack-meeting18:16
ayoungWe have a month.  THat should be realistic, assuming Oslo moves, and they are pretty responsive.18:16
lbragstadgrabbing alink18:16
*** debo_os has joined #openstack-meeting18:16
dolphmassuming we can be officially unblocked by oslo18:16
lbragstadhere is part of it *( the logging fix)18:16
lbragstad#link https://review.openstack.org/#/c/39934/18:17
lbragstadthat implements unified logging for kestyone using the fix for local.py that removes the eventlet dependency18:17
lbragstadfrom there, we can sync with the notifier in oslo18:17
dolphmsweet18:17
lbragstadand then I can push the notification module/tests/implementation as a commit on it's own18:18
bknudsonI think there are 3 reviews now pulling in the same stuff from oslo18:18
ayoungOK, recommend we target this for H3, then18:18
lbragstadbknudson: yes18:18
dolphmlbragstad: updated bp unified-logging-in-keystone target & impl18:18
lbragstaddolphm: thank you18:18
*** Mandell has quit IRC18:18
lbragstadIhave to look into the jenkins issue18:18
*** nijaba has quit IRC18:19
lbragstadI have some fixes that are in keystone/openstack/common/rpc/amqp.py that need to land in Oslo first18:19
lbragstadI can get started on filing a bug for that later today18:19
dolphmlbragstad: let's leave notification targeted at 'next' until logging is totally complete, then we can see how much time we have18:19
lbragstaddolphm: ok, that sounds fair18:19
*** nijaba has joined #openstack-meeting18:20
ayoungdolphm, henrynash has an interesting review that seems to slip in under the letter of the law for an acceptable feature18:20
dolphm#topic High priority code reviews18:20
*** openstack changes topic to "High priority code reviews (Meeting topic: keystone)"18:20
dolphmlink em up18:20
ayounghttps://review.openstack.org/#/c/39530/18:20
dolphm#link https://review.openstack.org/#/c/40170/18:20
ayoung#link https://review.openstack.org/#/c/39530/18:20
ayoung"Implement domain specific Identity backends"18:21
morganfainbergayoung: henrynash's change is pretty cool.18:21
ayoungdolphm, it has no new API and config file is 100% backwards compat18:22
henrynashso this was already targeted at H318:22
*** ruhe has quit IRC18:22
*** xBsd has quit IRC18:22
bknudsoncan we have multiple identity_api providers now?18:22
ayoungbknudson, with 39530, yes18:22
bknudsonbut the dependency registry only supports a single one?18:22
ayoungplease take a look at the config file changes18:22
henrynashbut I would like some guidance on the config changes…18:23
ayoungthere is some need to push up a cleaner API to the oslo code base, but it supports what we want to do18:23
ayoungthere are two options.  I'll link18:23
henrynash…the goals is to be able  to create new config structure for each instantiated bbackend driver18:23
ayoung#link https://review.openstack.org/#/c/39530/11/keystone/common/config.py18:23
henrynashayoung: do 11 and the most recent18:23
ayoungand18:24
ayoung#link https://review.openstack.org/#/c/39530/12/keystone/common/config.py18:24
henrynashayoung: yep, those are the two18:24
*** xBsd has joined #openstack-meeting18:24
ayoungideally, the helper methods like register_cli_int  would be on the config object itself18:24
ayoungso we could do18:24
ayoungconf.register_cli_int18:24
dolphmayoung: oslo's config object?18:25
ayoungdolphm, yeah18:25
*** jhenner has quit IRC18:25
dolphmayoung: oslo hates that we use those functions at all18:25
henrynashdolphm: so the 2nd link is a version that removes them18:25
ayoungdolphm, is version 12 how they want us to do it?18:25
gyeehenrynash, look like good stuff at the first glance18:25
dolphmayoung: i'd ask markmc, and take his advice :)18:25
morganfainbergoh we have a review to remove those helper functions?18:25
henrynashdolphmL, while the first one is a version that tries to keep them18:25
*** jhenner has joined #openstack-meeting18:25
henrynashgyee: thx18:26
dolphmayoung: henrynash: get markmc on that review!18:26
henrynashdolphm: ok18:26
ayoungadded him18:26
dolphmhenrynash: thanks18:26
*** Mandell has joined #openstack-meeting18:26
bknudsonI thought the whole point of oslo config is that you could have command-line overrides for all the options.18:26
ayoungbknudson, this is not command line, though18:26
bknudsonalthough I've never tried it.18:26
morganfainbergbknudson: that was my understanding.18:26
ayoungthis is multiple config files18:26
ayounghenrynash, care to explain what you are doing in a bit more detail?18:27
bknudsonright, the command-line overrides the value in the config file18:27
henrynashsure18:27
dolphmbknudson: in part, yes... and i'm not sure how i would expect CLI options to interact with / override per-domain config18:27
henrynashso we use the identity Manager layer to allow multiplexing of driver backends (e.g, LDAP server 1 for domainA, LDAP sever 3 for domain b, the rest share SQL etc.)18:28
* dolphm [X] multiplexing18:28
*** [1]glikson has joined #openstack-meeting18:28
dolphmmore checkboxes for marketing18:28
gyeenice18:28
henrynashfor each domain that wants its one backend, you create a 'keystone.<domain_name>.comf' file that just contains the config overrides for the domain18:28
topolhenrynash, very cool!18:29
henrynashso the manger picks up all those files, creates a new conf structure for each one and inits the request driver withit18:29
henrynash…hence the need to be able to create a separate conf structure (which is where we came into this discusion)18:29
ayoungone possible use of this pattern in the future is multiple SQL datasources18:30
gyeehenrynash, besides LDAP, are there any other use case for this?18:30
dolphmhenrynash: as long as you can exploit with something dumb like POST /v3/domains {"domain": {"name": "/../../etc/passwd; #"}}18:31
henrynashgyee: well, yes it isn't constrained to ldap….you could have separate SQL drivers if you wanted to keep data in different DBs per domain18:31
*** adrian_otto has joined #openstack-meeting18:31
henrynashdolphm: not sure I follow18:31
bknudsondo I have to restart Keystone when create domain?18:32
dolphmhenrynash: you're reading paths off the file system that are provided by API users18:32
dolphmhenrynash: generally that's not a good idea18:32
*** jhenner has quit IRC18:32
ayounghenrynash, actually, I was thinking that it would be good to be able to split table spaces on module lines, so, say tokens could go into a separate RDBMS than policy or something, too.  I think you are setting up a pattern, and I want people to validate that.18:32
gyeedolphm, some injection attack? :)18:32
*** harlowja_ has quit IRC18:32
dolphmhenrynash: if the format was keystone.{domain_id}.conf then the file names would be determined by keystone, and not the API user, and we can all be a lot less paranoid18:32
henrynashdolphm: I toyed with whether it should be domain_id or domain_name18:33
dolphmhenrynash: you're also requiring that domain names be encodable in the constraints of the file system... another problem that system-assigned ID's would solve18:33
ayoung keystone.{domain drop table tokens;}.conf18:33
* topol just because you are paranoid doesn't mean they aren't out to get you18:33
henrynashdolphm: was just concerned over readability….but I'm oK with Ids18:34
henrynashbknudson: yes, that is an issue18:34
*** debo_os_ has joined #openstack-meeting18:34
*** morganfainberg has quit IRC18:34
*** morganfainberg has joined #openstack-meeting18:34
*** chuck__ has joined #openstack-meeting18:34
*** jhenner has joined #openstack-meeting18:34
henrynashbknduson: I was going to have a separate extension that provided a new API call to re-init a domain…and have that called by keystone-manage18:34
*** zul has quit IRC18:34
dolphmhenrynash: i certainly understand the readability issue18:35
henrynashbknudson: that would be the only extension bit of this…18:35
bknudsonnot a big concern since this requires config option.18:35
topolwhen would re-init get called?18:35
dolphmhenrynash: init?18:35
*** harlowja has joined #openstack-meeting18:35
henrynashtopol: so today, it's a keystone restart18:35
topolyep18:35
henrynashdolphm: yes, the manager init18:35
*** debo_os has quit IRC18:35
dolphmhenrynash: oh to initialize drivers and whatnot18:35
topoland in the future?18:35
*** debo_os_ is now known as debo_os18:35
*** MarkAtwood has quit IRC18:35
dolphmhenrynash: normally that wouldn't be done through a web api18:36
henrynashtopol: so I thought for now we might allow keystone-mange to have a "domain-init" function?18:36
henrynashdolplhm: open to how best to do that18:36
topolhenrynash, OK18:36
*** dvarga has joined #openstack-meeting18:37
gyeehenrynash, more fun when we have the need to support nested domains?18:37
henrynashdolphm: on the domain_name vs domain_id issue, I also thought that anyone using external serves like LDAP etc. would likely have good domain names18:37
ayoungdomain is in the assignments backend.  It is OK to modify that to have additional information about the domains config18:37
topolnested domains, we have a use case for that???18:38
dolphmhenrynash: i'd make sure it's an issue with people actually deploying keystone before you pursue some complicated proprietary solution to a problem that doesn't actually exist :(18:38
henrynashgyee: hmm, indeed :-)18:38
*** jhenner has quit IRC18:38
ayounggyee is instigating18:38
morganfainberggyee: domains all the way down?18:38
dolphmhenrynash: restarting a keystone process to pick up new config isn't unreasonable18:38
*** Haneef has joined #openstack-meeting18:38
topoldolphm +118:38
henrynashdolphm: that's what you have today out of the box18:38
topol(until someone complains :-) )18:38
*** chuck__ is now known as zul18:39
dolphmtopol: +118:39
dolphm#topic open discussion18:39
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:39
dolphm#link https://launchpad.net/keystone/+milestone/havana-318:39
ayoungDo bug triage18:39
henrynashi raised the issue on the agenda of the migration being proposed to fix the credentials index?18:40
* dolphm will do18:40
bknudsonserver never supported paging, so suggest removing it from spec: https://review.openstack.org/#/c/39828/18:40
dolphm#action dolphm to triage all the bugs18:40
fabiodolphm, regarding OS-EP-FILTER18:40
dolphmbknudson: thanks!18:40
fabio#link https://review.openstack.org/#/c/33118/18:40
henrynash#link https://review.openstack.org/#/c/40170/18:41
bknudsonhenrynash: that review is mysql-only18:41
ayoungdolphm, that is not just for you18:41
henrynashbknduson: err, do you mean sqlite?18:41
bknudson if migrate_engine.name != 'mysql': return18:41
bknudsonso it only runs if mysql18:41
dolphmayoung: aww, that'd be appreciated lol18:41
ayoungdolphm, suggestion: for all bugs that are new, assign them to someone on core to verify18:41
*** ivasev has joined #openstack-meeting18:41
henrynashbknuson: ahh, hmm I thought it was sqllite that was the problem…oh, well18:42
topol(thats got to go: if migrate_engine.name != 'mysql': return )18:42
ayoungdolphm, once we've verified, mark as verified, and then you can triage18:42
bknudsonI don't understand why only mysql had this problem.18:42
dolphmayoung: how about subscribing ya'll as appropriate?18:42
topolgo away18:42
dolphmayoung: and you assign to yourself18:42
henrynashtopol : the reaso is that I think it's only broken for one DB type18:42
ayoungdolphm, I've been grabbing ones18:42
*** troytoman is now known as troytoman-away18:42
ayoungmostly around LDAP and identity18:42
dolphmayoung: i don't want to assign bugs to only core, as i don't want to block non-core from feeling like they can contribute fixes18:43
ayoungdolphm, fair enough18:43
dolphmayoung: MUCH appreciated18:43
dolphmayoung: like for serious18:43
*** troytoman-away is now known as troytoman18:43
topolhenrynash, perhaps a comment then metnioning that18:43
henrynashbkudson: I think it was a previous change that removed a constraint, and left an index hanging around…but if that is true for msysql, I agree it should be true for postgres etc.18:43
*** novas0x2a|laptop has joined #openstack-meeting18:43
*** gkleiman has joined #openstack-meeting18:44
henrynashbkundson: confused face in place18:44
bknudsonhenrynash: once the tests are fixed to verify on all engines, I'll give it a whirl.18:44
ayoungdolphm, I think we have 97 bugs open that have no one assigned, if I performed the query correctly18:44
ayoungOh, some of those have fix committed18:45
henrynashdolphm: my reason to raise it all is that we had said "no more migrations"…do we allow this one if we think it is fixing a real issue?18:45
dolphmhenrynash: still planning on working this bp during m3, or should it be untargeted? https://blueprints.launchpad.net/keystone/+spec/pagination-backend-support18:45
*** lpabon has quit IRC18:45
*** lpabon_ has joined #openstack-meeting18:45
henrynashdolphm: I am planning to attack it next week18:45
dolphmayoung: it's still a lot of bugs :(18:46
dolphmhenrynash: cool, just wanted to check18:46
dolphmhenrynash: it's our only 'not started' .. no pressure ;)18:46
henrynashdolphm: :-)18:46
*** dani4571 has joined #openstack-meeting18:46
dolphmhenrynash: i'm lost on the context of your question about migrations though18:46
*** jodom has joined #openstack-meeting18:46
*** jrodom has quit IRC18:46
morganfainbergdolphm: as soon as i have a little breathing room on dayjob front, I'll hit some of the bugs i can.18:47
*** jrodom has joined #openstack-meeting18:47
*** nachi_ has joined #openstack-meeting18:47
*** nachi has joined #openstack-meeting18:47
dolphmmorganfainberg: what's your dayjob, anyway?18:47
*** sarob has joined #openstack-meeting18:47
* topol my money's on henynash getting is started :-)18:47
morganfainbergdolphm: writing openstack code internally for my company.18:47
henrynashdolphm: I thought we had said (maybe I 'm wrong) that we had decided no more sql migrations for H318:47
*** sarob has quit IRC18:47
*** epim has quit IRC18:47
ayounghttps://bugs.launchpad.net/keystone/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.18:47
ayounghas_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on18:47
dolphmhenrynash: i guess i missed that discussion... why not?18:47
ayoungugh, too long18:47
bknudsonif there's no new features then there's no new migrations18:48
*** sarob has joined #openstack-meeting18:48
dolphmayoung: bit.ly?18:48
ayoungdolphm, yeah, one sec18:48
dolphmbknudson: migrations can fix bugs, though18:48
henrynashdolphm: For some reason I thought we were trying to have no DB changes between H2 -> H318:48
henrynashdolphm: sounds like I was imagining this… :-)18:48
ayounghttp://bit.ly/11KfaLF18:48
dolphmbknudson: the ec2 -> credentials migration would be another that wouldn't fit18:48
ayoungThose should be the ones on one has looked at yet:  new, undecided priority18:49
nachidolphm: https://review.openstack.org/#/c/38367/18:49
*** [1]glikson has quit IRC18:49
dolphmhenrynash: sounds like something that might happen by coincidence, but i certainly wouldn't -2 any migration review until icehouse or anything18:49
dolphmhenrynash: bknudson: check out nachi's review above ^18:50
gyeedolphm, I am lost, we are saying no new migrations till IceHouse?18:50
ayoungdolphm, so my thought was that extension migrations would go in their own repos, but for core, we would still allow them in the common repo.18:50
henrynashdolphm: Ok, fine…I'll chalk that up to eating too much blue cheese late at night....18:50
dolphmgyee: no no, i was asking where that notion came from18:50
dolphmgyee: if there was a discussion about it, i missed it is all18:50
gyeedolphm, no, that why I was confused18:51
dolphmi suspect it's something we should take review by review though?18:51
gyeeagreed18:51
ayoungdolphm, that is why I was pushing for the repo split, to make things clearer.  But it looks like we are not all of the same mind there.18:51
bknudsonI like the repo split18:51
*** dcaro has joined #openstack-meeting18:51
bknudsonif someone wants to use it they'll be able to once the code's in.18:52
dolphmayoung: i'm not opposed to splitting the repo, i'm mostly playing devil's advocate there / don't see an immediate benefit18:52
fabioayoung: is the repo split targeted for m3?18:52
bknudsonsome people think there should be no extensions.18:52
ayoungbknudson, the one concern that dolphm has voiced that is worth repeating here is that with Alembic, we will end up with multiple steps .18:52
dolphms/immediate benefit/immediate benefit for anyone but us/18:53
*** martine_ has quit IRC18:53
ayoungheh, we are going to have extensions.  jaypipes is actually going to resubmit his "regions" change as an extension, even after that discussion18:53
*** pnavarro has quit IRC18:53
jaypipesindeed.18:53
dolphmayoung: he hasn't done that though, and i now see why :P18:53
ayoungdolphm, so, my though was that it lest su split out an extension from the main database.  I was thinking18:53
ayoungfor something like kds, that may not belon in Keystone lng term18:53
gyeejaypipes, you decided that after a couple of drinks? :)18:54
dolphmi assume he's philosophically opposed to authoring an api extension :)18:54
ayoungdolphm, no, he is philosophically opposed to wastingtime when a core dev decides to roadblock18:54
topol"couple"  -- you are being generous  :-)18:54
jaypipesgyee: no, I was always willing to do what what was asked of me... doesn't mean I can't debate it in public though ;)18:54
* dolphm <3 open source community spirit18:55
*** danwent has quit IRC18:55
ayoungdolphm, so I see the repo split as the logical result of the focus on extensions.  It lets us keep separate concerns separate18:55
ayoungand, if we decide that something should be spun off into its own server, we have a way of deploying just that extension...sort of.18:56
gyeeayoung, speaking of that, shouldn't we be concerned about repo split with henry's separate driver per domain thingy?18:56
ayoungIt means that the changes for that extnesion are not intertwined with the migrations for unrelated code/18:56
ayounggyee, nope.  Doesnt' affect it18:56
bknudsongyee: yes, interesting, how to keystone-manage db_sync with multiple sql backends?18:56
ayounggyee, his is, right now, only LDAP18:57
*** abaron has joined #openstack-meeting18:57
dolphmayoung: agree, that's certainly a benefit for devs18:57
dolphmayoung: i don't want to inconvenience deployers at all in the process though18:57
ayoungdolphm, I was thinking also that we could enable extenstions in the future18:57
dolphmayoung: when they don't get anything out of it18:57
gyeebknudson, especially if we are using different backends per domain, we have to make sure db_sync work correctly18:57
ayoungso, say KDS becomes a long term supported extension, we make it a default migration when you run db_sync18:57
dolphmgyee: eek, hadn't considered that18:58
ayoungright now, there are no default migrations, but it doesn;t have to stay that way18:58
bknudsongyee: or at least document what you need to do.18:58
dolphmayoung: what do you mean by default migrations?18:58
ayounggyee, if we have that, each would have a migrate_version table (or the alembic equivalent) and we would be able to query it  to see what it supported18:58
bknudsondb_sync --domain xxxx18:59
ayoungdolphm, as of latest patch now db_syn only runs through what is in common18:59
ayoungdolphm, and you suggested that it run through everything18:59
gyeeI mean it could get ugly if we are not careful18:59
ayoungI am thinking of a middle ground18:59
ayoungit will run through common, and a list of default support extensions18:59
*** epim has joined #openstack-meeting18:59
ayoungso, in icehouse, if we make an extension supported by default, we will run through its migrations when db_sync is run with no parameters19:00
ayoungdolphm, this way, an extension is really 0 impact if it is not enabled19:00
dolphm#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Aug  6 19:00:43 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-08-06-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-08-06-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-08-06-18.02.log.html19:00
jeblairci/infra people around?19:00
pleia2o/19:00
clarkb\o19:01
*** bknudson has left #openstack-meeting19:01
clarkb(that is a high five)19:01
fungiheyo19:01
*** fabio has quit IRC19:01
*** brich1 has left #openstack-meeting19:01
*** olaph has joined #openstack-meeting19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Aug  6 19:01:29 2013 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-30-19.02.html19:01
*** troytoman is now known as troytoman-away19:01
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:01
*** krtaylor has quit IRC19:01
zaroo/19:02
*** spzala has quit IRC19:02
*** vijendar has quit IRC19:02
clarkbjeblair has super exciting news I think19:02
* fungi thinks so too19:02
*** vijendar has joined #openstack-meeting19:02
jeblairthat's a slightly stale agenda, but i think we can work with it19:03
*** adrian_otto has quit IRC19:03
*** jeblair sets mode: -o jeblair19:03
jeblair#topic asterisk19:03
*** openstack changes topic to "asterisk (Meeting topic: infra)"19:03
mordredo/19:03
jlko/19:03
*** vijendar has quit IRC19:03
*** nachi has quit IRC19:03
*** nachi_ has quit IRC19:03
jeblairit's probably not worth calling in again, as i'm not sure anyone has had a chance to identify causes/solutions to the high cpu from transcoding we saw...19:04
clarkbjeblair: I haven't seen any puppet changes to address that19:04
clarkbthere was one small change to deal with NAT better but I doubt that is related19:04
jeblairrussellb: i haven't had a chance to look into it, have you?19:04
jeblairpabelanger isn't around :(19:04
*** nachi has joined #openstack-meeting19:05
*** nachi_ has joined #openstack-meeting19:05
russellbjeblair: i haven't touched it19:05
russellbclarkb: not realted19:05
*** divyeshk has left #openstack-meeting19:05
*** epim has quit IRC19:05
russellbthat was related to me helping someone get their local PBX behind NAT working19:05
russellbi don't think we know that it's transcoding specifically, and not just the cost of running the conference bridge19:05
russellbi don't think we had monitoring set up last week?  so would be worth doing it again once we have a graph to look at i guess19:06
*** jlucci has joined #openstack-meeting19:06
fungi#link http://cacti.openstack.org/cacti/graph_view.php?action=tree&tree_id=1&leaf_id=3919:07
russellbawesome19:07
fungidid we possibly under-size the vm? we can always grow it to the next flavor up if needed, i expect19:08
fungibut we'll obviously want to observe its performance under load19:08
russellbi don't see CPU on there19:08
clarkbshould we call in again to get some numbers in cacti?19:08
clarkbrussellb: second page19:08
russellboops :)19:08
jeblair(or set "graphs per page" to a high number at the top)19:08
fungiwhere "high number" is i excess of the ~25 graphs currently generated19:09
jeblairthat's 5 min intervals19:09
jeblairlet's aim for calling in again next week19:10
clarkbok19:10
* russellb is in now in case anyone wants to call in and idle for a bit19:10
jeblairoh, or we could do it now.  :)19:11
russellbshould see if we can get a graph of number of calls on here too19:11
russellbi'm in bridge 600019:11
fungiwhat's the did again?19:11
russellbhttps://wiki.openstack.org/wiki/Infrastructure/Conferencing19:11
*** epim has joined #openstack-meeting19:11
fungi#link https://wiki.openstack.org/wiki/Infrastructure/Conferencing19:11
fungithanks!19:11
*** cp16net has quit IRC19:12
russellbi couldn't figure out how to mute my other client, lol.19:13
russellbsorry.19:13
* mordred not calling in beause he's in brazil. btw19:13
*** cp16net has joined #openstack-meeting19:13
jeblairmordred: you could try SIP :)19:14
* jeblair is listening in stereo19:14
*** ttrifonov is now known as ttrifonov_zZzz19:14
*** jlucci has quit IRC19:15
*** debo_os has quit IRC19:15
fungiso we presumably want to load the pbx for a good 10 minutes to get a decent snmp sample period19:15
jeblairfungi: yeah19:16
jeblairso while that's going on...19:17
*** johnthetubaguy has quit IRC19:17
jeblair#topic Multiple Jenkins masters (jeblair)19:17
*** openstack changes topic to "Multiple Jenkins masters (jeblair) (Meeting topic: infra)"19:17
fungiyes!19:17
jeblairwe have them!19:17
clarkb\o/19:17
fungiseveral!19:17
*** hartsocks has joined #openstack-meeting19:17
jeblairall of the test load should now be on jenkins01 and jenkins0219:17
*** dvarga is now known as dvarga|away19:17
jeblairwhile jenkins is running the jobs on the special slaves19:17
*** ttrifonov_zZzz is now known as ttrifonov19:18
jeblairthis is going to be a big help in that we can scale out jenkins with our test load19:18
fungii've seen no problem reports which seem attributable to the change19:18
*** anteaya has quit IRC19:19
*** zul has quit IRC19:19
jeblair(from an overall system pov, we've moved the bottleneck/spof to zuul, but there's a logical bottleneck there in terms of having a single logical gate)19:19
*** gyee has quit IRC19:19
*** nijaba has quit IRC19:20
*** nijaba has joined #openstack-meeting19:20
*** nijaba has quit IRC19:20
*** nijaba has joined #openstack-meeting19:20
*** IlyaE has joined #openstack-meeting19:21
jeblairnext i'm going to be working on devstack-gate reliability, and then speed improvements19:21
fungii haven't looked back at the resource graphs for zuul recently to see whether that's creeping upward19:22
jeblairit seems to be keeping up with gerrit changes, etc19:22
jeblairi think the new scheduler there did a lot to help that19:23
*** dvarga|away is now known as dvarga19:23
jeblairso, completely unscientifically, now that we're spreading the load out a bit, it seems as if jenkins itself is able to keep up with the devstack-gate turnover better.19:23
* mordred bows down to jeblair and the jenkinses19:23
fungicpu and load average look fine on zuul19:23
jeblairat least, when i've looked, the inprogress and complete jobs are finishing quickly19:23
jeblair#topic Requirements and mirrors (mordred)19:24
*** openstack changes topic to "Requirements and mirrors (mordred) (Meeting topic: infra)"19:24
clarkband we can upgrade jenkins eith zero downtime :)19:24
jeblairmordred, fungi: updates on that?19:24
jeblairclarkb: yes!  i hope to do that soon!19:24
mordredwell... we've goten somewhere19:25
fungioops, i hung up on the pbx19:25
mordreddevstack is now updating all projects requirements to match openstack/requirements19:25
mordredbefore installing them19:25
mordredand requirements is now gated on devstack19:25
mordredso that's super exciting19:25
fungianyway, i've tried and scrapped about three different designs for separate-branch mirrors and settled on one i think should work19:26
mordredwoot19:26
fungii've got a wip patch for the job additions up right now while i hammer out the jeepyb run-mirror.py addition19:26
*** terriyu has quit IRC19:26
fungii still don't have good ideas got bootstrapping new branches of openstack/requirements to the mirror without manualintervention19:27
*** krtaylor has joined #openstack-meeting19:27
clarkbfungi: is listing the branches in the requirements repo not sufficient?19:27
fungiand what to do with milestone-proposed periods19:27
*** ttrifonov is now known as ttrifonov_zZzz19:28
clarkbmilestone proposed belongs to the parent branch right?19:28
fungiclarkb: well, if we branch requirements for a new release, we want the mirror to already be there so tests will run, right?19:28
*** dolphm has quit IRC19:28
clarkbfungi: yes, we can branch requirements first though19:29
*** ttrifonov_zZzz is now known as ttrifonov19:29
fungiso do we rename the mirrors in place, or duplicate them, or play with symlinks during transitions or...19:29
mordredI'm not sure we should ever have a milestone-proposed requirements, should we?19:29
clarkbI think we can duplicate. It is easy, pip cahce prevents it from being super slow19:29
clarkband python packages are small19:29
mordredcan we do failover-to-master ? or is that crazy19:29
fungimordred: not so much a milestone-proposed requirements, but what do we gate nova milestone-proposed against? master? havana?19:29
mordredfungi: gotcha19:30
fungithinking mostly in terms of which mirror to use in integration tests around release time19:30
mordredyah19:30
*** ttrifonov is now known as ttrifonov_zZzz19:30
jeblairmordred: particularly since devstack forces the requirements now, the m-p branch of code will either use what's in requirements/m-p or requirements/master19:30
fungiso anyway, i'll get the bare functionality up first and then we can iterate over release-time corner cases for the automation19:30
*** ivar-lazzaro_ has joined #openstack-meeting19:30
jeblairmordred: if we don't branch requirements, then that means master requirements must be frozen during the m-p period19:31
*** vijendar has joined #openstack-meeting19:31
mordrednod. branching requirments seems sensible19:31
jeblairwhich i think is counter to what we want m-p for (to keep master open)19:31
jeblairso i think we probably have to branch requirements...19:31
mordredand if we branch it first, then that could trigger the m-p mirror19:31
mordredyeah. I'm on board with that now19:31
jeblairfungi: the act of creating a branch is a ref-updated event that could trigger the run19:31
fungiagreed19:31
jeblairso it should be transparent to the projects as long as requirements is branched first19:32
fungianother point in question here is, once we have requirements-sync enforced on projects, do we need to keep carrying forward the old package versions?19:32
jeblairfungi: we'll want to make sure that the release documentation for the m-p branching process is updated for this.19:32
fungiabsolutely19:32
jeblairfungi: it doesn't seem like we do need to carry those.19:33
*** grapex has joined #openstack-meeting19:33
*** ivar-lazzaro has quit IRC19:33
jeblairfungi: maybe clean them up after 48/72 hours or something?19:33
jeblairfungi: (to give us a chance to pin them if something breaks)19:33
*** vipul is now known as vipul-away19:34
fungii wouldn't think so either, just wanted to make sure i didn't go to extremes to populate new branch mirrors with the contents of the old ones indefinitely19:34
*** anteaya has joined #openstack-meeting19:34
jeblairwe may also need requirements branches for feature branches19:35
fungicleaning up old packages will be an interesting endeavor as well... especially if different python versions cause different versions of a dependency to get mirrored19:35
*** colinmcnamara has joined #openstack-meeting19:35
clarkbjeblair: I think it is fair to make feature branches dev against master19:35
clarkbs/master/master requirements/19:36
fungiso we can't necessarily guarantee that if two versions appear i the mirror, the lower-numbred one should be cleared out19:36
jeblairfungi: yeah, i don't think there's any rush to do that.  if you were mostly asking about carrying existing things to new branches, then i think nbd.19:36
clarkbotherwise you won't be able to sanely test keystone branch foo against everything else master in tempest19:36
jeblairclarkb: the feature branch requirements would see that it is done.19:36
fungijeblair: that was mostly it. create the new mirror from scratch when the branch happens, vs prepopulating with a copy of the old mirror first19:36
clarkbjeblair: the problem with it is if nova master conflicts with keystone foo19:37
jeblairclarkb: if reqs has feature branches, then devstack will now force the feature reqs to be the deps for all the projects.  that will either work or not in the same way as master.19:37
clarkbthen all of your testing fails19:37
clarkbjeblair: I think the net effect is you end up with something a lot like the master requirements19:38
jeblairclarkb: yes, such a requirements change would not be allowed to merge to the feature branch.19:38
jeblairclarkb: so that's the system working as intended.19:38
clarkbyup, but the diff between master and foo requirements will be tiny19:38
jeblairclarkb: if two openstack projects need updating to work with an updated requirement in the feature branch, then two openstack projects will need that feature branch.19:38
clarkbgotcha19:38
jeblairclarkb: tiny but important.19:38
jeblair(important enough for you to go through all this hassle to get a new version of something.  :)19:39
mordred++19:39
jeblairanything else?19:39
jeblair(i really like the way this is heading)19:40
jeblair#topic  Gerrit 2.6 upgrade (zaro)19:40
*** openstack changes topic to "Gerrit 2.6 upgrade (zaro) (Meeting topic: infra)"19:40
jeblairwe forgot to link zaro's change last meeting (or maybe it wasn't pushed yet)19:40
jeblairzaro: do you have the link to your gerrit patch handy?19:40
zaroyes, give me a min.19:41
fungizaro: btw i played around with your wip feature poc and it seems to do what we want19:41
mordredI agree19:41
fungiexcellent stuff19:41
zaro# link https://gerrit-review.googlesource.com/4825419:41
mordredI like it19:41
jeblairof: [cgit, py3k, git-review, and storyboard], which do we need to talk about at this meeting?19:41
zaro#link https://gerrit-review.googlesource.com/4825419:41
zaro#link https://gerrit-review.googlesource.com/4825519:41
zarowas uploaded for almost a week, no love yet.19:42
clarkbjeblair: cgit and py3k have recent changes19:42
fungii have py3k and g-r updates, but they're not critical to be covered19:42
zaroso just waiting now..19:42
*** lpabon_ has quit IRC19:43
* ttx lurks19:43
clarkbzaro: should we try and get people to review that change?19:43
zaroi could make a request.19:43
clarkbzaro: I am not sure what their review backlogs look like, but asking in IRC might help19:43
zaroprobably mfick19:43
*** lpabon has joined #openstack-meeting19:43
jeblairzaro: david did have a nit on that second change19:43
zarohe just came back from vacation.19:43
jeblairzaro: very cool19:44
zarojeblair: was a nit but didn't give a score.19:44
*** arunkant has quit IRC19:44
*** tr3buche1 is now known as tr3buchet19:44
zarojeblair: i was waiting for maybe someone else to score before fixing the nit19:44
jeblairzaro: anyway, you might want to update that, and then, yeah, start pestering people.  :)19:44
zarojeblair: ok. will give that a try.19:45
jeblair#topic cgit server status19:45
*** openstack changes topic to "cgit server status (Meeting topic: infra)"19:45
pleia2so, we're pretty close, 2 of the 3 reviews outstanding should be pretty good to go19:45
*** lpabon has quit IRC19:46
jeblairsomeone keeps scope-creeping at least one of them, sorry.  :)19:46
*** ohadlevy_ is now known as ohadlevy19:46
pleia2yeah, that's the 3rd :)19:46
fungipleia2: i see the replication and https changes open... what's the third?19:46
pleia2fungi: ssl19:46
pleia2oh19:46
*** lpabon has joined #openstack-meeting19:46
*** ohadlevy has quit IRC19:46
*** ohadlevy has joined #openstack-meeting19:46
clarkbI intend on updating my reviews now that there are new patchsets (I believe)19:46
pleia2fungi: git daemon https://review.openstack.org/#/c/36593/19:47
jeblairpleia2: did we agree https only ?19:47
fungiahh, yes19:47
pleia2jeblair: yeah19:47
pleia2patched ssl one accordingly19:47
jeblairthat seems reasonable to me, fwiw.  https (no http) and git:// otherwise.19:47
clarkb++19:47
fungiwfm19:47
pleia2once these are done there is just cleanup and theming if we want19:48
*** epim has quit IRC19:48
mordred++19:48
jeblairttx: you may be interested in the "Requirements and mirrors" topic earlier in this meeting19:48
mordredI'd like theming - but I'm fine with that coming later19:48
clarkbyeah, I think right now having performant fetches on centos is more important that theming :)19:48
pleia2also, I'm flying to philly on thursday for fosscon, so my availability will be travel-spotty as I prep and attend that19:48
ttxjeblair: reading backlog19:49
jeblairttx: short version: we will probably need to create a m-p branch of the openstack/requirements repo before doing any other project m-p branches.19:49
clarkbpleia2: have fun19:49
pleia2clarkb: thanks :)19:49
jeblair#topic Py3k testing support19:49
*** openstack changes topic to "Py3k testing support (Meeting topic: infra)"19:49
fungiwe have a couple outstanding moving parts which need to get reviewed19:49
fungi#link https://review.openstack.org/#/q/status:open+project:openstack-infra/config+branch:master+topic:py3k,n,z19:49
*** epim has joined #openstack-meeting19:50
fungiclark has a patch out there to start non-voting py33 tests on all the clients after those above go in19:50
clarkb#link https://review.openstack.org/#/c/40323/19:50
*** boris-42 has quit IRC19:50
ttxjeblair: I'll need to do a m-p for swift 1.9.1 tomorrow or thursday morning19:50
jeblairttx: if it's just for swift, it shouldn't be an issue19:51
jeblairttx: it only matters if the requirements for master and m-p diverge, which i am certain will not happen for swift.  :)19:51
jeblairttx: so you should be able to ignore it for this, and hopefully we'll have all the machinery in place by h319:52
ttxjeblair: ack19:52
jeblairfungi: i will promote those to the top of my queue19:52
fungijeblair: awesome. thanks19:52
fungiother than that, the projects which are testing on py33 seem to be doing so successfully19:52
funginot much to add on that topic19:53
jeblairvery excited about running py33 tests for the clients, since zul is actually submitting changes there!19:53
jeblair#topic Releasing git-review 1.23 (fungi)19:53
*** openstack changes topic to "Releasing git-review 1.23 (fungi) (Meeting topic: infra)"19:53
fungithis was on the agenda just as a quick heads up19:53
*** danwent has joined #openstack-meeting19:53
mordredfungi: cool. did we get anywhere with installing the hook differently?19:53
mordredfungi: so that it applies to merge commits too?19:54
fungiwe have a contributed patch to convert git-review to pbr19:54
fungi#link https://review.openstack.org/#/c/35486/19:54
fungiand i want to tag a release on the last commit before that19:54
*** vipul-away is now known as vipul19:54
*** nachi_ has quit IRC19:54
mordred++19:54
fungijust so if we have installation problems in the following release for some users, the fallback is as up to date as possible19:54
*** gabrielhurley has joined #openstack-meeting19:55
fungii've been using the current tip of master for weeks successfully19:55
fungihave one cosmetic patch i want to cram in and then tag it, probably later this week19:55
jeblairfungi: sounds good19:55
*** epim has quit IRC19:55
mordredyup19:55
fungithe pbr change is exciting though, because we have integration tests which depend on that19:55
mordredvery exciting19:55
jeblairah, that's what's holding that up19:55
fungi#link https://review.openstack.org/#/c/35104/19:56
jeblair#topic Storyboard (anteaya)19:56
*** openstack changes topic to "Storyboard (anteaya) (Meeting topic: infra)"19:56
fungialso i want to turn on the tests as no-ops first so we can gate them on themselves19:56
jeblairanteaya: 4 minutes.  :(19:56
anteayahello19:56
ttxhi!19:56
anteayawell most of my questions from last week were answered19:56
anteayaI hadn't set up the db properly19:56
anteayaI have a patch waiting to merge that adds those instructions to the readme19:57
* ttx started working on the project group feature today19:57
*** epim has joined #openstack-meeting19:57
anteayabasically what I do know is that ttx wants to stay with 1.4 django, correct ttx?19:57
jeblairttx: https://review.openstack.org/#/q/status:open+project:openstack-infra/storyboard,n,z19:57
jeblairttx: i think both of those changes could use some input from you if you have a min.19:57
anteayaand other than that I am still trying to get the models straight19:57
ttxjeblair: oh. I wasn't notified on those for some reason19:58
anteayathat is about it from me, ttx, anything else19:58
*** zaneb has joined #openstack-meeting19:58
jeblairttx: ah, you may need to add it to your watched projects list in gerrit19:58
jeblairhttps://review.openstack.org/#/settings/projects19:58
ttxdoing that right now19:58
fungittx: i don't think i've started watching it in gerrit either. good reminder19:58
jeblair(used to happen as part of the lp group sync)19:58
mordredttx: I personally don't see any reason to stay with 1.419:59
*** SlickNik has joined #openstack-meeting19:59
*** adrian_otto has joined #openstack-meeting19:59
mordredbut defer to you19:59
clarkbupgrade to all the new things19:59
ttxno good reason, except that supporting 1.4 is not really causing an issue19:59
fungioh, and reminder to everyone i'm working from seattle the week of the 18th, then mostly unreachable the week after that20:00
anteayattx if I were able to put together a patch to upgrade to 1.5, would you look at it?20:00
*** dprince has quit IRC20:00
ttxI'm fine with 1.5+ if we end up using something that is only 1.5 :)20:00
clarkbdjango is tricky because supporting mutliple versions isn't super straightforward aiui20:00
*** Haneef has quit IRC20:00
jeblairthanks all!20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
mordredyah - and 1.5.1 is the current release20:00
openstackMeeting ended Tue Aug  6 20:00:32 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-08-06-19.01.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-08-06-19.01.txt20:00
*** dolphm has joined #openstack-meeting20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-08-06-19.01.log.html20:00
dolphmo/20:00
ttxWho is around for the TC meeting ?20:00
mordredo/20:00
zanebo/20:00
*** markmc has joined #openstack-meeting20:01
gabrielhurley\o20:01
markwasho/20:01
markmchey20:01
notmynamehere20:01
markmcclaino/20:01
ttxrussellb, jd__, annegentle, mikal, jgriffith, vishy: around ?20:01
*** clayg has joined #openstack-meeting20:01
jd__o/20:01
claygwoooooo!20:01
annegentleo/20:01
russellbo/20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Aug  6 20:01:41 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
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
*** lastidiot has quit IRC20:01
ttxFYI Zane Bitter (zaneb) is proxying for shardy20:01
*** dvarga is now known as dvarga|away20:02
ttxOur agenda:20:02
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:02
*** lastidiot has joined #openstack-meeting20:02
ttxhub_cap should join us in ~30min to discuss Trove so we'll move that to the end20:02
mikalhi20:03
ttx#topic New program application: Release cycle management20:03
*** openstack changes topic to "New program application: Release cycle management (Meeting topic: tc)"20:03
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-August/012842.html20:03
ttx(1) Scope, mission statement, how "essential" the effort is to OpenStack20:03
*** olaph has left #openstack-meeting20:03
ttxSo... this effort has been present since the beginning but never formalized in any way20:03
ttxFor me this is more an alignment thing, to justify for example that it has its own topic at the Design Summit20:03
notmynamedoes this mean there will be a PTL and elections?20:03
ttxnotmyname: yes20:04
ttxnotmyname: though the "team members" are just the release team, stable team and VMT, so pretty limited20:04
mordredttx: who will elect20:04
mordredah - you answered the question20:04
* markmc can't wait to see ttx fight off all the PTL candidates20:04
ttxteam members like any program20:04
ttxmarkmc: I could use some vacation :)20:05
dolphmon the mission statement -- is it necessary to specify time-based releases? seems like it shouldn't be necessary to change the mission statement if you found it more appropriate to release in some other manner20:05
gabrielhurleythat actually answered my question too, which was "who contributes to this program"20:05
markmcttx, tough :)20:05
*** dcaro has quit IRC20:05
jgriffitho/20:05
mordreddolphm: ++20:05
annegentle+1 to dolphm20:05
ttxgabrielhurley: note that I punt on the ATC issue by saying that all team members should be ATC by contributing to another project anyway20:05
ttxdolphm: +120:05
notmynamedolphm: +120:05
* ttx redacts mission statement20:06
markmcwould a switch away from time-based releases be something we'd want TC approval on?20:06
mikalmarkmc: I would hope so20:06
gabrielhurleygonna go with yes20:06
annegentlettx: are you precluding the possibility of a security program?20:07
ttxmarkmc: good point, so baking it in the mission statement is a way to ensure that it is20:07
mordredI'd say that we'd probably go to the TC whether it's in your mission statement or not20:07
ttxannegentle: define security program20:07
markwashmordred: +120:07
mordredbasically, beause ttx would say "time releases suck now" and _someone_ would disagree20:07
mordredand raise the issue20:07
ttx"""To organize the release cycle and the work necessary to produce coordinated releases of the integrated components of20:07
ttxOpenStack. To collect bugfix backports and produce stable point releases20:07
ttxfor the previously-released branch. To coordinate the publication of20:07
ttxsecurity patches and advisories (OSSA) for security-supported branches."""20:07
mordredor - NOBODY would dissent at all, in which case lazy consensus would be reached20:08
notmynamettx: +120:08
mordredI doubt the second would happen :)20:08
zanebI think markmc's point was that it doesn't matter if it's baked in to the mission statement, because it would have to come back in front of the TC anyway20:08
mordred++20:08
mordredttx: ++20:08
annegentlettx: I'm thinking that by taking "Too coordinate the publication of security patches..." under the release program you'd take away a mission statement for a future possible security program?20:08
ttxzaneb: or I would run with it but someone would notice and complain to the TC, which ends up the same20:08
notmynamettx: how does a new contributor join the release cycle management team?20:08
dolphmttx: ++20:09
ttxannegentle: yes. If we decide the VMT is a separate program we would edit the current statement20:09
annegentlettx: ok20:10
*** krtaylor has quit IRC20:10
* mordred thinks VMT is an aspect of release management20:10
ttxnotmyname: by becoming a VMT member or by becoming a release manager for a stable release20:10
mordredbecause it's related to the long-term life of a release20:10
ttxnotmyname: the latter case is about volunteering to handle one, like adam_g proved20:10
dolphmmordred: agree, that's what i would assume... i'd have to be convinced otherwise20:10
notmynamettx: also, if your deliverable is a signed release, where are the signing keys kept and how are they changed? (perhaps off topic for this discussion?)20:11
ttxmordred: it's definitely related to lifecycle, which makes it a not-too-weird addition to the mix20:11
*** colinmcnamara has quit IRC20:11
mordredttx: can I suggest that volunteering to become a release manager for a stable release at least go through a  vote of the people currently in release-core and stable-core ?20:11
mordrednot that I think there's likely to be dissent - but it seems like a good decision point20:11
ttxnotmyname: it's always been signed using a personal key20:11
mordrednotmyname: we've been discussing an openstack keyring20:12
mordrednotmyname: of keys used for releases20:12
mordredpotentially requiring key being keysigned by other folks20:12
ttxmordred: what problem are you trying to solve with approving stable release managers ?20:12
mordredttx: who says yes when someone volunteers20:13
ttxmordred: currently, the PTL of the program (me)20:13
mordredor, more importantly, who says no if someone really crazy/inappropriate does20:13
mordrednone of the rest of our programs appoint people to positions by ptl fiat20:13
ttxmordred: err.. core members ?20:14
ttxmordred: there is much more power in controlling infra-core than a stable release coordinator :)20:14
ttxwhich just herds cats20:14
mordredI don't feel strongly about it - you're obviously doing a great job ...20:14
ttxmordred: ptls appoint core members. It's about the same.20:15
mordredI'm just bringing it up as a point to thikn about20:15
notmynamemordred: technically, aren't core members appointed by the PTL. by social convention it's done after a group consensus20:15
mordredthey do not20:15
mordredreally? crazy20:15
mordredI have always seen core members vote on other core members20:15
notmynamemordred: ie, I'm the one who actually clicks the button20:15
gabrielhurleythe vote is often pro forma20:15
mikalmordred: it varies by project20:15
ttxmordred: not all projects use the group consensus thing20:15
*** topol has quit IRC20:15
mordredk. good to know20:15
* mordred stands correct20:15
mordredcorrected20:15
ttxmordred: anyway, I would certainly also use group consensus, but that doesn't answer your question20:15
jeblairhttps://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess20:16
*** psedlak has quit IRC20:16
*** glikson has joined #openstack-meeting20:16
jeblairis there a written process that contradicts that?20:16
ttxjeblair: this was overruled when we saud the PTLs has ultimate control over his project.20:16
jeblairsounds like a reach20:17
gabrielhurley"his or her project". we're not biased here...20:17
notmynamedifferent discussion for a different time?20:17
*** adrian_otto has quit IRC20:17
mordrednotmyname: ++20:17
ttxjeblair: anyway, that's another discussion, I'm fine withusing the same rule as coredev for stable release dudes20:17
markwashttx enjoy waiting 90 days to appoint anyone!20:18
ttxhahaha20:18
ttx(2) Team/effort/community maturity20:18
ttxThe only remark I have on that side is that it's more the result of the grouping of 3 different teams20:18
ttxBut with a common focus around branches, release cycle and stable branch maintenance policies20:18
ttxAny question on that part ?20:18
mordrednope. makes sense to me20:19
ttxfwiw I don't expect anything to change, it's just formilizing a bit20:19
*** nijaba has quit IRC20:20
notmynamettx: how does this affect your personal participation on the TC? ie you were directly elected previously. now by virtue of PTL20:20
ttxformalizing*20:20
ttxnotmyname: with the new election model we are all elected20:20
notmynameafter the next elections. ok20:20
ttxdoesn't change the current tc20:20
*** wolfdreamer has joined #openstack-meeting20:20
ttx(we didn't add the recent program ptls)20:20
*** nijaba has joined #openstack-meeting20:21
*** nijaba has quit IRC20:21
*** nijaba has joined #openstack-meeting20:21
*** wolfdreamer has quit IRC20:21
ttxOK, ready to vote ?20:21
ttxany more questions ?20:21
*** dosaboy_ has joined #openstack-meeting20:21
annegentlettx: did we ever formalize how the TC chair is placed?20:21
russellbnot a question, but a comment, ttx: thanks for doing such an awesome job with this area of the project :-)20:21
ttxannegentle: it's baked in the bylaws actually20:21
annegentlettx: ok I didn't find it with a quick search but that's ok20:21
ttxannegentle: though there is a lack of clarity at one point20:22
*** wolfdreamer has joined #openstack-meeting20:22
ttxannegentle: i.e. the bylaws tend to say we don't even have to run new chair elections until the previous chair is formally removed20:22
zanebannegentle: everyone takes a giant step backwards, and whoever is slowest gets stuck with it20:22
ttxwhile the TC charter says we should designate someone20:22
annegentlezaneb: :)20:23
annegentlettx: yeah ok I see that, not a topic for today though20:23
ttxto solve that we'll probably choose the chair again after the TC elections, just in case someone else wants the fun of handling those meetings20:23
annegentlettx: :)20:23
ttxok, vote ?20:24
annegentlettx: ok ready20:24
*** dosaboy has quit IRC20:24
ttx#startvote Accept release cycle mgmt as an official OpenStack program? yes, no, abstain20:24
openstackBegin voting on: Accept release cycle mgmt as an official OpenStack program? Valid vote options are yes, no, abstain.20:24
openstackVote using '#vote OPTION'. Only your last vote counts.20:24
markmc#vote yes20:24
dolphm#vote yes20:24
annegentle#vote yes20:24
jd__#vote yes20:24
mikal#vote yes20:24
ttx#vote abstain20:24
zaneb#vote yes20:24
markmcclain#vote yes20:24
notmyname#vote yes20:24
markwash#vote yes20:24
jgriffith#vote yes20:24
gabrielhurley#vote yes20:24
ttx30 more seconds20:24
wolfdreamer#vote yes20:24
russellb#vote yes20:25
notmynamettx: nice swap where you are the one abstaining and I'm in the majority ;-)20:25
mordred#vote yes20:25
ttx#endvote20:25
openstackVoted on "Accept release cycle mgmt as an official OpenStack program?" Results are20:25
openstackyes (14): markmc, zaneb, notmyname, annegentle, jd__, russellb, markwash, mikal, mordred, gabrielhurley, wolfdreamer, dolphm, jgriffith, markmcclain20:25
openstackabstain (1): ttx20:25
ttxnotmyname: heh20:25
ttxawesome, thx everyone20:25
ttxdo we have hub_cap yet ?20:25
ttxlooks like we don't, so let's do some open discussion20:26
ttx#topic Open discussion20:26
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:26
ttxWanted to raise the question of schedule for the end-of-cycle graduation review.20:26
ttxThat needs to be completed by September 20, which is when the program PTL elections begin20:26
ttxSo I think we can schedule the review for September 3 and 1020:26
ttxWith September 17 as a backup date in case the discussion is longer than expected20:26
notmynamewhat's the release date for havana?20:27
ttxShould be enough for the two things we have in incubation at this point.20:27
annegentlenotmyname: Oct 1720:27
russellbhttps://wiki.openstack.org/wiki/Havana_Release_Schedule20:27
notmynameannegentle: thansk20:27
notmynamerussellb: ditto20:27
ttxfwiw ptl nomination would be sep 20-26, election Sep 27-Oct 320:27
ttxtc nomination Oct 4-10, election Oct 11-&720:28
annegentlettx: without the "What is core" process framed out can we meet Sep 3 and 10? Or is that the point?20:28
ttx17*20:28
ttxannegentle: we don't care about core in that review20:28
ttxannegentle: we decide on integration on the next reklease cycle20:28
markmcannegentle, recall "integrated" vs "core" status20:28
ttxi.e. are those projects mature enough to be included in the integrated release of icehouse20:29
markmcannegentle, separate things, precisely so we don't have to block on the board deciding stuff20:29
*** xBsd has quit IRC20:29
zanebttx: is the PTL nomination date even important now that core PTLs don't affect the TC makeup?20:29
annegentlettx: markmc: okie doke. Who else is looking for integrated status?20:29
zanebincubated projects have to run PTL elections regardless20:29
ttxzaneb: that's a good point. The TC charter has the weeks hardcoded20:29
ttxzaneb: we /could/ change that, but I figured knowing who the PTLs are is a good indication for the TC elections20:30
*** dvarga|away is now known as dvarga20:30
annegentlezaneb: ttx: I think it's important to keep the dates for the sake of summit plannign?20:30
markmcannegentle, Trove and Ironic ... the currently incubating projects20:30
zanebyeah, I wasn't suggesting changing it ;)20:30
ttxannegentle: yes, we need the program PTLs elected at least one month before summit20:30
ttxso that they can help with scheduling fun20:30
*** sdake has quit IRC20:31
annegentlemarkmc: ok, thanks20:31
zanebjust that it's kind of orthogonal to making graduation decisions20:31
ttxzaneb: oh, I see what you mean, that's a good point20:32
ttxzaneb: we could run the review at the same time we vote for PTLs20:32
zanebif necessary, yes20:32
zanebby all means schedule it before20:32
zanebit doesn't seem like a disaster if it goes over20:32
ttxack20:33
ttxok, let's discuss Trove now and go back to open discussion later, time permitting20:33
ttxwe have vipul representing hub_cap20:33
ttx#topic Trove scope expansion to NRDB20:33
*** openstack changes topic to "Trove scope expansion to NRDB (Meeting topic: tc)"20:33
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2013-July/000314.html20:33
ttxSo... while the original Trove incubation request mentioned relational and non-relational DBs, we limited the scope of the accepted incubated project to RDBs20:33
ttxThe rationale behind the limitation was that there was no code to show the impact of supporting NRDBs, so we would revisit the scope when that would be less vaporware20:34
ttxApparently that went faster than expected since a Redis POC is available now20:34
ttxso here we are20:34
vipulttx: hub_cap has asked me to share this: https://review.openstack.org/#/c/40239/320:34
*** dvarga has quit IRC20:34
vipulthis is a POC showing the Redis integration with trove20:34
ttxvipul: thx20:34
vipuland as you will see, it was fairly simple, with no API changes20:34
ttxI looked briefly earlier and it doesn't seem to introduce enough disruption to justify a separate project20:34
ttxMy only gripe would be: widening the scope before polishing the current scope20:35
*** hub_cap has joined #openstack-meeting20:35
vipuland there's hub_cap!20:35
ttxah, here he is20:35
hub_capheyo20:35
hub_capdid i miss much? /me hasnt checked the logs yet20:35
gabrielhurleyon the other hand, better to expand scope before graudation so we get the scope right for the "real" project20:35
mordredvipul, hub_cap: and the idea is that the backend is impl dependent like virt layer in nova?20:35
ttxhub_cap: will paste backlog for you20:35
hub_capttx: ill read on eavestdrop20:36
mordredor that a single deploy could have multiple choices20:36
mordredso that auser could say "trove give me a mysql" or "trove give me a redis"20:36
ttxhub_cap: see last lines @ http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2013-08-06.log20:36
zanebso, one question. Trove, as I understand it, is designed around the user creating and managing database instances (=VMs), and they pay for the number of nova servers they use, right?20:36
vipulA single deploy could support both, through a service_type20:36
ttxonly last 3 min20:36
*** kroberts has quit IRC20:36
mordredvipul: great20:36
hub_capok perfect up to speed20:36
ttxgabrielhurley: +120:36
mordredvipul: if that is the case, then I can be on board20:37
annegentleso, conceptually, is this similar to how cinder enables multiple storage vendors, or is it as different as block storage v object storage (nosql v sql)20:37
hub_capzaneb: that is correct20:37
mordredI just would not like to see a user ask for a database and get a redis when he thought he was going to get a mysql20:37
dolphmannegentle: good analogy20:37
vipulmordred: that is the case as of now, we record the 'type' in the instances table20:37
mordredbecause, well, thats wierd20:37
hub_capwait you dont want mongo? all mongo? all the time?20:37
mordredand I cannot imagine that being a workable experience for any cloud end user20:37
annegentlemarkmc: I think you were going to look into why AWS has their sql and nosql separate?20:37
notmynamehub_cap: in trove can a redis implementation not be implemented as an extension or plugin? if so, would that be a more appropriate path?20:38
dolphmannegentle: ++20:38
dolphmi'm only concerned about ending up with a complicated api that is trying to solve two very different problems (regardless of whether they are implemented by a single codebase or not)20:38
zanebhub_cap: ok, thanks. so, it seems like with NoSQL you could also have a model where servers are completely abstracted and you pay by usage (storage + bandwidth)20:38
markmcannegentle, I was?20:38
markwashAWS has a nosql api, and a sql provisioning api20:38
markwashmaybe it was this mark20:38
* markmc wonders did he black out in a TC meeting :)20:38
hub_capnotmyname: we have been batting this around somewhat, but as of now they are "backend impls" so to speak20:38
zaneband if somebody wanted to start that project, I wouldn't want is to turn them away20:38
markmcmarkwash, ah :)20:38
markwashtrove is a provisioning api20:38
annegentlemarkmc: woops sorry20:38
*** sarob has quit IRC20:38
markwashit makes sense to provision lots of DBS, no matter what kind of format they talk20:38
mordredright - I tihnk the fact that trove is a provisioning api20:38
ttxdolphm: the API is pretty much the same, looking at the proposed patch20:38
hub_capzaneb: that could easily be done since we push our own notifications20:38
jd__so soon Trove will start providing private object storage by deploying Swift instances? :)20:38
mordredand does not try to filter useage20:39
mordredis why I tihnk this is ok20:39
*** vkmc has quit IRC20:39
mordredwith the earlier stipulation on sanity20:39
markwashjust so long as Trove doesn't become a data api, and stays a provisioning api (for databases) I'm very happy20:39
gabrielhurleymarkwash: ++20:39
hub_capprovisioning. always and forever (kippy from napolean voice)20:39
markwashwhich i think is exactly what is wanted on all sides, so. . nbd20:39
jd__mordred: +120:39
hub_capwe arent in the business of a data api, we let the product do that20:40
markwashmarkmc: do you think you would "/me blacks out" when you do black out?20:40
markwash:-)20:40
dolphmttx: agree, which is a great start, but that may evolve in the long run20:40
mordredhub_cap: if you don't expose service_type in the api, I will hunt you down with a large stick20:40
ttxjd__: After "openstack on openstack" we'll have "Swift on Trove" :)20:40
annegentlemarkwash: lol20:40
mordredmarkwash:hahaha20:40
dolphmttx: and i'm not qualified to predict how20:40
hub_capmordred: so20:40
hub_capwe will absolutely expose it20:40
markmcmarkwash, I'd hope so - it's the kind of thing you'd want a record of archived20:40
markmc#blackout markmc20:40
*** sdake has joined #openstack-meeting20:40
*** sdake has quit IRC20:40
*** sdake has joined #openstack-meeting20:40
hub_capbut if the service provider wants only 1 service, they can "default" it20:40
mordredhub_cap: but I don't think that's necessarily a TC thing - just that I will personally do that20:40
hub_capi _only_ want redis, ok we can do that, and u dont have to provide it in the api calls20:41
notmynamehub_cap: but as a provisioning API, why does redis need to be included into the core? and why now?20:41
mordredhub_cap: sure. as long as my api call to a service that has defaulted it that is explicit doesn't error20:41
annegentlehub_cap: only other scenario I can think of is first redis, then what20:41
*** sdake has quit IRC20:41
*** sdake has joined #openstack-meeting20:41
*** sdake has quit IRC20:41
*** sdake has joined #openstack-meeting20:41
hub_capnotmyname: this is less a case of why redis and why _not_ redis so to speak.20:41
markmcwhat part of troves API limits it to just provisioning databases ?20:42
hub_capwe are trying to expand scope to > RDB's and that includes things like redis20:42
notmynamehub_cap: my perspective is colored by the work red hat is doing to use gluster volumes behind swift. this isn't something that is in swift core20:42
ttxnotmyname: we're not really judging the implementation, just blessing that Trove provisions databases, not just SQL ones.20:42
markmclike, could it be extended to provision an NFS server?20:42
*** ryanpetrello has quit IRC20:42
hub_capmarkmc:.....20:42
*** gyee has joined #openstack-meeting20:42
hub_capit could, as of now, as as matter of fact i did that in a demo 4 summits ago20:42
hub_capbut20:42
markmchub_cap, I don't want this, I'm trying to understand what part of troves API makes it specifically a database thing20:43
hub_capwe dont want to be in the business of "we can do every service ever"20:43
*** gyee_ has joined #openstack-meeting20:43
ttxmarkmc: I was asking myself the same question20:43
hub_capwe will do database services because they all 'more or less' require clustering, backups, constant montioring etc...20:43
zanebhub_cap: btw memcached comes to mind as something that should be supported also20:43
notmynamehub_cap: what you just said is the answer to "why _not_ redis"20:43
hub_capzaneb: absolutely20:43
*** gyee_ has quit IRC20:43
*** sarob has joined #openstack-meeting20:43
hub_capnotmyname: ?20:43
markmchub_cap, sounds like a glusterfs or ceph deployment too20:43
*** jlucci has joined #openstack-meeting20:44
hub_capcan u elaborate?20:44
mordredoh god. flashbacks to the brian aker v. linus torvalds filesystem vs. database discussion20:44
hub_capannegentle: i believe that haomaiwa_ is working on leveldb, so that could be next20:44
notmynamehub_cap: you asked, why not do redis support earlier. my answer is what you just said: scope expansion isn't a a priori good thing20:44
*** Mandell has quit IRC20:44
*** Mandell has joined #openstack-meeting20:45
hub_capi see what you are saying notmyname, but i dont think that it creeps the scope of the application20:45
notmynamettx: so we're being asked to bless what it already does? then what's the point of a vote? it supports X.. (looking for clarity)20:45
markmcit wouldn't need a vote if it didn't :)20:45
hub_capits just introduces another impl for people to leverage :)20:46
ttxnotmyname: at this point it is precluded from accepting that patch because of the scope we blessed20:46
markwashI think the point of a vote is that the wording of the scope needs to change, not necessarily the spirit of it20:46
hub_capnotmyname: ttx: remember in my original "scope of trove" i asked to be both RD/NRD but we limited it due to a lack of impl20:46
ttxhub_cap: yes20:46
mordredyeah - we explicitly asked them to come back to us if they were going to do NRD20:47
hub_cap:)20:47
ttxand so they do20:47
*** dvarga has joined #openstack-meeting20:47
*** novas0x2a|laptop has quit IRC20:47
ttxI'm fine with Trove being about provisioning databases in the large sense, as I think the actions ( clustering, backups, monitoring) are the same concepts in both20:48
hub_capexactly ttx20:48
*** markvan has quit IRC20:48
jd__that question might sounds weird, but if we consider ISC bind as some sort of NRDB, could it be in Trove scope for example?20:49
zanebinclined to agree, and I assume the mission statement mentions explicitly that it's only about provisioning and not being a data api (DynamoDB-style)20:49
ttxif it were a data API that would of course be different, but it's not20:49
hub_capnever a data api, period20:49
zanebbecause I think there's room for a NoSQL data api in OpenStack as well, but obviously this isn't it20:49
*** novas0x2a|laptop has joined #openstack-meeting20:50
russellbzaneb: indeed20:50
mordred++20:50
russellbbut that's ok, and provisioning seems reasonable20:50
russellbin trove20:50
gabrielhurleyjd__: that'd be a heck of a stretch IMHO, and other projects/programs are more suited to dealing with that20:50
ttxok, I'm ready to vote20:50
hub_cap+1 gabrielhurley20:50
ttxmore questions ?20:50
*** debo_os has joined #openstack-meeting20:50
markwashwe should add something like "and try not to step on anyones toes" to the trove mission statement :-)20:50
jd__yeah, I just find the definition line very thin20:51
markwashto cover all the crazy cases20:51
ttxjd__: I think you'd want a data API to go with DNS20:51
zanebrussellb: agree, just hope it will be explicit that we are not turning *that* project away, if it arries20:51
ttxjd__: (what designate does)20:51
zanebarrives20:51
annegentlezaneb: good point20:51
russellbzaneb: +120:51
jd__ttx: probably indeed20:51
jd__i'm just thinking trove seems to be a service deployment service that wants to limit itself to databases for whatever reason20:52
*** apevec has joined #openstack-meeting20:52
ttxjd__: you could argue that clustering and data backup are relevant for more than just DBs20:53
zanebhub_cap: just looking at the mission statement... would you be willing to consider amending to specifically mention provisioning?20:53
mordredhonestly, I'm fine with trove having self-restraint in that area20:53
hub_capdef zaneb20:53
*** gkleiman has quit IRC20:53
ttxok, raise your hand if you have more questions before we vote20:53
jd__mordred: I guess we can say "you have to start with something" anyway :)20:53
mordredjd__: ++20:53
ttx#startvote Accept Trove scope expansion to NRDB? yes, no, abstain20:54
openstackBegin voting on: Accept Trove scope expansion to NRDB? Valid vote options are yes, no, abstain.20:54
openstackVote using '#vote OPTION'. Only your last vote counts.20:54
dolphm#vote yes20:54
russellb#vote yes20:54
ttx#vote yes20:54
gabrielhurley#vote yes20:54
markmcclain#vote yes20:54
markwash#vote yes20:54
jd__#vote yes20:54
annegentle#vote yes20:54
jgriffith#vote yes20:54
zaneb#vote yes20:54
mikal#vote yes20:54
ttxnotmyname: your turn to abstain :)20:54
hub_cap:)20:55
markmc#vote yes20:55
*** sushils has quit IRC20:55
mordred#vote yes20:55
notmyname#abstain20:55
wolfdreamer#vote yes20:55
notmynamettx: ;-)20:55
ttx30 more seconds20:55
notmyname#vote abstain20:55
zanebfail20:55
ttx#endvote20:55
openstackVoted on "Accept Trove scope expansion to NRDB?" Results are20:55
openstackyes (14): markmc, ttx, annegentle, jd__, russellb, wolfdreamer, markwash, mikal, mordred, gabrielhurley, zaneb, dolphm, jgriffith, markmcclain20:55
openstackabstain (1): notmyname20:55
hub_capthx all!20:55
hub_capi will amend the mission to include 'provisioning'20:56
zaneb++ :)20:56
ttxhub_cap: btw we said that we would discuss graduation to integrated at the beginning of September20:56
hub_capand a meme of markwash singing "but i still love provisioning"20:56
markwash+120:56
ttxhub_cap: just so you know, time is running short :)20:56
hub_capokey. im good with that20:56
ttx#topic Open discussion20:56
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:56
hub_capi feel like we are close to being able to discuss20:56
ttx4 minutes...20:56
ttxwe could discuss "what is core" to death, or have a beer before the release meeting.20:57
mordredbeer20:57
* hub_cap runs20:57
ttxmordred: yes, but what does core mean ?20:57
* AlanClark smiles20:57
mordredttx: beer20:57
jkyle+1 on beer vote20:57
dolphm#vote yes for beer20:57
jd__core means beer?20:57
gabrielhurleyjd__: +1 decided.20:58
* markwash hears crickets20:58
mordredjd__: and beer means core. and corebeer means beercore and beerbeer means corecore20:58
* hub_cap head explodes20:58
dolphmVoted on "core means beer" Results are 100% in favor20:58
jd__mordred: I see you didn't lose time on that beer :-)20:58
markmcmordred, I imply that resentment20:58
ttxlet's quickly make a t-shirt20:58
mordredmarkmc: :)20:58
ttxawesomesauce.20:59
ttx#endmeeting20:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:59
openstackMeeting ended Tue Aug  6 20:59:31 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-08-06-20.01.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-08-06-20.01.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-08-06-20.01.log.html20:59
ttxone minute break20:59
ttx[interlude elevator music]20:59
ttxHi!21:00
ttxmarkmc, dolphm, notmyname, jd__, markwash, jgriffith, russellb, shardy, gabrielhurley, markmcclain: around ?21:00
*** clayg has left #openstack-meeting21:00
gabrielhurleylol21:00
notmynamehi21:00
gabrielhurley\o21:00
markmcclaino/21:00
med_snort.21:00
*** SlickNik has left #openstack-meeting21:00
russellbhi21:00
jd__beer/21:00
*** sushils has joined #openstack-meeting21:00
jeblairjd__:  wins21:00
ttxzaneb: proxying for shardy again ?21:00
jgriffitho/21:01
zanebttx: stevebaker has volunteered to be in the hot seat for this one21:01
stevebakerme for heat21:01
dolphmo/21:01
zanebuh, no pun intended21:01
ttxstevebaker: great!21:01
zanebthanks stevebaker!21:01
* zaneb runs21:01
stevebakerl8er21:01
ttxHeat PTL will now be known as "the hot seat"21:01
*** krtaylor has joined #openstack-meeting21:01
gabrielhurleyhaha21:01
*** markwash has quit IRC21:01
zaneblol21:01
ttx#startmeeting project21:01
openstackMeeting started Tue Aug  6 21:01:58 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
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
mordredcan redhat pay for hot hot heat to play at the summit?21:02
*** glikson has quit IRC21:02
ttx#topic General stuff21:02
*** openstack changes topic to "General stuff (Meeting topic: project)"21:02
ttxredhot?21:02
ttxI documented the optional FeatureProposalFreeze at:21:02
*** lexinator1 has joined #openstack-meeting21:02
ttx#link https://wiki.openstack.org/wiki/FeatureProposalFreeze21:02
*** markwash has joined #openstack-meeting21:02
ttxSo far only Nova (Aug 21) and Neutron (Aug 23) declared they would use this21:02
ttxLet me know if you plan to have one and I'll make it appear on https://wiki.openstack.org/wiki/Havana_Release_Schedule21:03
dolphminteresting...21:03
ttxapevec: status for the 2013.1.3 release at this point ?21:03
apevecttx, on track for Thursday release21:03
*** lexinator has quit IRC21:03
apeveccall-for-testing sent to openstack-dev21:04
dolphmttx: the wiki makes no mention of how the date for this relates to the rest of the cycle?21:04
*** zbitter has joined #openstack-meeting21:04
dolphmnvm! "generally happens one or two weeks ahead of FeatureFreeze."21:04
ttxdolphm: you pick the date.21:04
apevecno feedback yet, assuming no news==good news21:04
*** grapex has left #openstack-meeting21:04
ttxapevec: no news==no tester in my book21:05
*** MarkAtwood has joined #openstack-meeting21:05
ttxsdague, annegentle, mordred: news from QA/Docs/Infra programs ?21:05
mordredrequirements - requirements are gating now, and devstack is homogenizing them. the list is a little bit behind because we were waiting on gating for it... soon you'll all be getting automatic proposals on requirements updates21:05
jeblairour test jobs are now running on possibly the world's first multi-master jenkins setup!  this explains 'jenkins0[12].openstack.org' urls from zuul if you see them.  I'll write a blog post later this week.21:05
sdagueglobal requirements is now in devstack21:05
*** stevemar has quit IRC21:05
sdagueper mordred's comment ^^^^21:05
jeblairwe'll begin making use of requirements repo branches (eg for stable/) soon (thanks fungi!)21:06
*** jodom has joined #openstack-meeting21:06
mordredclient libs - setuptools upgrade nightmare is almost over - but it would be really great if everyone could land the recent client lib sync requests and then cut new releases21:06
annegentleo/21:06
*** zaneb has quit IRC21:06
mordredwhich removes the d2to1 requirement, which will unbreak lots of thigns out in the world21:06
sdaguetestr for tempest runs is getting close. We'll probably switch to testr single threaded this week for the regular jobs, and the parallel as soon as the races are fixed21:06
mordredsdague: w00t21:06
jd__mordred: noted21:07
sdaguestill optimistic we get parallel for h321:07
ttxannegentle: anything to report ?21:07
jgriffithmordred: in progress on cinder side21:07
annegentleJust 2 things - 1) Next Tues. is the monthly doc team meeting.21:07
annegentle2) I've been asked to post my "What's Up Doc?" status report to openstack-docs and openstack-dev, it's basically a roundup of the week (or weeks). Sound okay to cross post?21:08
*** abaron has quit IRC21:08
annegentleor do I just post to -dev?21:08
mordredjgriffith: thank you21:08
*** SergeyLukjanov has quit IRC21:08
ttxannegentle: it's fine to cross-post... just make sure you point follow-ups to one list only21:09
annegentlettx: ah good guidance, thanks21:09
ttxi.e. "please follow-up on $list"21:09
fungiif only more muas supported the mft header21:09
ttxsigh yes21:09
ttx#topic Oslo status21:09
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:09
ttxmarkmc: hi!21:09
markmcyo21:09
ttx#link https://launchpad.net/oslo/+milestone/havana-321:09
markmcI don't think I've much to report since last week21:10
ttx40% done, 40% under review, 20% in progress, 0% not started21:10
*** jrodom has quit IRC21:10
ttxLooking good21:10
markmcmain thing is I've started porting Nova to oslo.messaging21:10
ttxWould be great to be all done before Nova and Neutron's FeatureProposalFreeze so that the final syncs can get in21:10
markmcso there's reasonable hope oslo.messaging will get done21:10
markmcwhen is FeatureProposalFreeze?21:10
ttxfor Nova (Aug 21) and Neutron (Aug 23)21:10
mordredwe added oslo.messaging git head to devstack, but have not added it to the gate21:10
*** emagana has joined #openstack-meeting21:11
markmc#link https://review.openstack.org/39929 - nova port to oslo.messaging21:11
mordredif you're adding it to nova now, should we add it to the gate?21:11
markmcmordred, yep, that's awesome21:11
ttxmarkmc: trusted-messaging is marked 'Needs code review' but I couldn't find a review about it ?21:11
*** epim has quit IRC21:11
ttxI'm becoming a bit skeptical on our ability to deliver such a key feature so late in the cycle, especially while still chasing the key distribution server part21:11
markmcmordred, I promised sdague getting it in the gate is a pre-req for that patch going out of WIP21:11
mordredmarkmc: cool21:11
markmcttx, I updated the links in the secure messaging BP a few minutes ago21:11
*** epim has joined #openstack-meeting21:11
markmcttx, the patches are actually really close now21:11
ttxlooking21:12
markmcttx, several rounds of review, I'm close to being ready to merge the big one21:12
* markmc checks on the kds patch21:12
*** derekh has joined #openstack-meeting21:12
markmchmm, https://review.openstack.org/3935021:13
ttxmarkmc: I fear the KDS patch will take time21:13
markmcoh wait, that's ayoung's copy of the patch?21:13
markmchttps://review.openstack.org/#/c/37118/21:13
ttxright, that one21:14
markmcdunno what to say21:14
markmcI'm not ready to write it off yet21:14
*** sdake has quit IRC21:14
markmcmaybe dolphm is21:14
markmcapart from that, ...21:14
ttxmarkmc: does it make sense to land anothing in oslo if that's not going in ?21:14
ttxanything*21:15
markmcI just realized I don't know if any new bps have come in lately21:15
markmcdon't really know how to start triaging21:15
ttxGiven how much post-integration it requires (think: https://blueprints.launchpad.net/ceilometer/+spec/use-new-rpc-messsage), time is running short for this on havana21:15
ttxno new stuff apparently21:15
markmctime is running short, yes21:16
*** vipul is now known as vipul-away21:16
ttxok, will talk to dolphm in keystone sectin21:16
ttxo21:16
ttxmarkmc: anything you wanted to raise ?21:16
markmcit probably makes sense to merge into oslo-incubator, keystone and then nova21:16
markmcin that order21:16
ttxQuestions about Oslo ?21:16
markmcif it goes into oslo-incubator and kds doesn't go in, no big deal21:16
dolphm(not sure i have much to add -- haven't been following KDS too closely)21:16
ttxmarkmc: ack21:16
ttx#topic Keystone status21:16
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:17
ttxdolphm: hello!21:17
*** sarob_ has joined #openstack-meeting21:17
dolphmo/21:17
ttx#link https://launchpad.net/keystone/+milestone/havana-321:17
*** salv-orlando has joined #openstack-meeting21:17
ttx0% done, 28% under review, 57% in progress, 14% not started21:17
ttxGetting a bit late21:17
*** debo_os has quit IRC21:17
ttxIf endpoint-filtering has no assignee it should probably be removed from havana-3 at this point ?21:17
dolphmah, i can fix that21:18
dolphmit's been making good progress, and an impl is in review21:18
ttxok, fix assignee and status then21:18
ttxTwo proposed blueprints need triaging (priority set): domain-quota-management-and-enforcement and unified-logging-in-keystone21:18
ttxdolphm: anything you wanted to raise ?21:19
dolphmyes..21:19
dolphmi'm definitely interested in pursuing FreatureProposalFreeze for keystone (today is the first i've heard of it)21:19
*** sdake has joined #openstack-meeting21:19
*** sdake has quit IRC21:19
*** sdake has joined #openstack-meeting21:19
dolphmi'll need to discuss with keystone-core and pick a date that makes sense for us21:20
*** sarob has quit IRC21:20
dolphmbut it seems to be a perfect for for keystone21:20
ttxdolphm: was discussed at last summit during the release cycle session21:20
dolphmsad i missed it :(21:20
ttxdolphm: ok, just let me know (and communicate to everyone on your blueprints)21:20
*** sarob has joined #openstack-meeting21:20
*** nijaba has quit IRC21:20
dolphmwill do, and that is all from me21:20
ttxQuestions anyone ?21:21
*** sarob_ has quit IRC21:21
ttx#topic Ceilometer status21:21
*** openstack changes topic to "Ceilometer status (Meeting topic: project)"21:21
ttxjd__: hey21:21
jd__o21:21
ttx#link https://launchpad.net/ceilometer/+milestone/havana-321:21
*** nijaba has joined #openstack-meeting21:21
*** nijaba has quit IRC21:21
*** nijaba has joined #openstack-meeting21:21
ttx14% done, 7% under review, 57% in progress, 21% not started21:21
ttxNot a lot of progress since last week... still feeling lucky ?21:21
*** nati_ueno has quit IRC21:21
jd__yes, I've stolen a blueprint from eglynn to make sure we'll make it21:22
jd__so I'm increasing bandwidth :)21:22
*** markmc has quit IRC21:22
ttx...not... sure ...I should be happy with that21:22
jd__well I say I've stolen, but I won't handle it, sileht will actually :)21:23
jd__that's the bandwitdh increase21:23
ttxjd__: next week if you don't land stuff we'll definitely need to cut stuff21:23
jd__ttx: fair enough21:23
ttxjd__: I see, it's your name on it... but your minions are doing it for you :)21:23
ttxjd__: anything you wanted to mention ?21:24
jd__hehe21:24
ttxQuestions on Ceilometer ?21:24
jd__nop, all good21:24
ttx#topic Swift status21:24
*** openstack changes topic to "Swift status (Meeting topic: project)"21:24
notmynamehi21:24
ttxnotmyname: o/21:24
ttx#link https://launchpad.net/swift/+milestone/1.9.121:24
*** stevemar has joined #openstack-meeting21:24
ttxnotmyname: the "missing" patch should be proposed tomorrow before you get up...21:24
ttxThat leaves you with the rest of the day to push in whatever else you want and get the changelog aligned21:24
*** markvan has joined #openstack-meeting21:24
notmynamettx: I've got all that ready to go21:24
ttxThen I can cut milestone-proposed and tag rc1 early Thursday morning (or late Wednesday depending on your TZ), if you give me the go-ahead before going to bed21:25
notmynamettx: I think it will be proposed around 8am pacific tomorrow21:25
notmynamettx: I'll give you the sha ASAP21:25
notmynamelooks like I need to update some LP stuff maybe21:25
*** vijendar has quit IRC21:25
ttxnotmyname: then I /might/ be able to cut earlier, we'll see if I can jump on irc during the evening21:26
notmynameand so I guess it's not a secret now that we'll cut 1.9.1 RC tomorrow?21:26
notmyname;-)21:26
ttxnotmyname: no it's not :)21:26
*** rwsu-away has quit IRC21:26
ttxnotmyname: anything you wanted to raise ?21:26
notmynameya, one thing21:26
*** markvan_ has joined #openstack-meeting21:27
notmynameSwiftStack is sponsoring a Swift hackathon in October in Austin. Details coming shortly21:27
ttxCool. Questions about Swift ?21:27
ttx#topic Glance status21:27
*** openstack changes topic to "Glance status (Meeting topic: project)"21:27
* markwash blacks out21:27
ttxmarkwash: o/21:27
notmynameheh21:27
ttxWAKE UP21:27
*** dosaboy has joined #openstack-meeting21:27
ttx#link https://launchpad.net/glance/+milestone/havana-321:27
markwasho/21:27
ttx28% done, 14% under review, 42% in progress, 14% not started21:28
ttxThis looks on track so far...21:28
markwashbut not a ton of improvement since last week21:28
ttxI'm growing a bit worried about async-glance-workers, since it appears to be a prerequisite of new-upload-workflow... what's the status of that ?21:28
markwashso I"ll look at adjusting21:28
markwasha lot of active discussion on async glance workers, if you've seen the ML21:28
*** dosaboy_ has quit IRC21:28
markwashhowever, I'm not sure folks are quite branch ready21:28
*** dscannell has quit IRC21:28
ttxseen it, it just is a bit late for discussion now :)21:28
markwashso we'll be discussing this week and next to see what we can actually get done now that we see how much still needs to be resolved21:29
markwashttx: I guess that's why its "high" and not "critical" ;-)21:29
*** markvan has quit IRC21:29
ttxmarkwash: if code is not proposed by next week, we'll probably have to skip new-upload-workflow21:29
markwashI agree21:29
*** markvan_ is now known as markvan21:29
ttxHow is api-v2-property-protection progressing ?21:29
markwasha bit better, active coding21:29
ttxNB: glance-tests-code-duplication needs to be triaged21:30
ttxmarkwash: we still need a python-glanceclient release to ship out the recent security fix21:30
*** jasondotstar has quit IRC21:30
ttxlet me know if I can help you with that21:30
markwashttx: I know :-( I've been hopelessly derelict, but I've been getting some help recently from @DeanTroyer21:30
markwashand trove docs21:30
ttxmarkwash: anything you wanted to mention ?21:30
markwashshould not be hard, probably just need to feel comfortable writing the commit message21:30
markwashnothing at this time21:31
ttxQuestions on Glance ?21:31
*** woodspa__ has quit IRC21:31
ttxmarkwash: thx!21:31
devanandaquestion on glanecclient review status21:31
ttxdevananda: go for it21:31
devanandaanything we can do to facilitate https://review.openstack.org/#/c/33327/ being reviewed more actively?21:31
*** neelashah has quit IRC21:31
markwashdevananda: I've been in talk with some other glance-core about that recently21:32
markwashI'll add it to the agenda for this weeks glance meeting21:32
devanandathanks :)21:32
ttx#topic Neutron status21:32
*** openstack changes topic to "Neutron status (Meeting topic: project)"21:32
ttxmarkmcclain: hi!21:32
markwashit would be great if someone could help us with any questions we have21:32
markmcclainhi21:32
ttxGood news is that the neutron gate has been reenabled, thanks to nati_ueno's work21:32
ttxIt needs to be closely watched though as it may quickly degrade again (think bug 1208661)21:32
uvirtbotLaunchpad bug 1208661 in neutron "floating ip exercise fails because IP not available" [Critical,In progress] https://launchpad.net/bugs/120866121:33
ttx#link https://launchpad.net/neutron/+milestone/havana-321:33
ttx23% done, 51% under review, 18% in progress, 6% not started21:33
ttxlooks like you might pull it off if you continue to review as fast21:33
markmcclainyeah.. today's gate brokeness has been slowing us down21:34
ttxRemoving a few targets couldn't hurt though:21:34
*** emagana has quit IRC21:34
ttxlike the few "not started" you still have*21:34
markmcclainI'm really close to deferring those21:34
markmcclainI don't think there will be consensus fast enough21:34
ttxok, do it before next week if there is no movement on those21:34
ttxthey are unlikely to make it (but likely to create a disturbance in the review queue when proposed later)21:35
ttx10 proposed blueprints are still in need of triaging... my suggestion if you accept them is to set most of them to "Low" priority21:35
ttxmarkmcclain: anything you wanted to raise ?21:35
markmcclainwill triage them.. nothing new to raise21:36
ttxQuestions on Neutron ?21:36
ttx#topic Cinder status21:36
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:36
ttxjgriffith: hola!21:36
jgriffithttx: hey ya21:36
ttx#link https://launchpad.net/cinder/+milestone/havana-321:36
ttx26% done, 6% under review, 46% in progress, 20% not started21:36
ttxNeed more code proposed, otherwise there will be a review traffic jam in a few weeks21:36
*** sdake has quit IRC21:36
jgriffithttx: already have that :(21:36
jgriffithttx: but yes21:36
ttxread-only-volumes (Medium) is marked as depending on volume-acl (Low)... if its a true dep, volume-acl should be >=Medium21:37
jgriffithttx: workign on stepping things up21:37
*** sdake has joined #openstack-meeting21:37
*** sdake has quit IRC21:37
*** sdake has joined #openstack-meeting21:37
jgriffithttx: that's been changed21:37
jgriffithttx: there's a r/o impl under review that doesn't rely on acl21:37
jgriffithttx: trying to resolve some infighting on that one though21:37
ttxjgriffith: ok, I'll remove the dep then21:37
jgriffithttx: thanks21:37
*** rwsu-away has joined #openstack-meeting21:37
*** eharney has quit IRC21:38
ttxclone-image-imageid is marked implemented but has https://review.openstack.org/#/c/38037/ going on21:38
jgriffithttx: I'll fix that21:38
ttxthx21:38
ttxfwiw 3 proposed blueprints need triaging: coraid-driver-refactoring-for-havana, cinder-volume-driver-optional-iscsi-support, windows-storage-driver-extended21:38
ttxjgriffith: anything on your mind ?21:38
jgriffithttx: nope, just hitting the rush21:39
ttxQuestions on Cinder ?21:39
ttx#topic Nova status21:39
*** openstack changes topic to "Nova status (Meeting topic: project)"21:39
ttxrussellb: hey21:39
jgriffithttx: hold on a sec21:39
russellbhey21:39
* russellb holds21:39
* ttx holds21:39
jgriffithttx: so the problem is there are multiples of that clone_image21:39
jgriffithttx: I'll sort out the deltas and update21:40
jgriffithttx: that's all21:40
ttxok, thx :)21:40
jgriffithrussellb: sorry :)21:40
russellball good21:40
ttx#link https://launchpad.net/nova/+milestone/havana-321:40
ttx10% done, 30% under review, 59% in progress, 0% not started21:40
ttxNot too bad, but we need more implemented and more under review if you want to hit FeatureProposalFreeze in good shape21:40
russellbi've moved some to low, but more are still coming in21:40
russellbyeah, at least a lot are under review21:40
russellbso hopefully we can do a review push on those in the near term21:40
ttxA few other remarks:21:40
ttxhttps://blueprints.launchpad.net/nova/+spec/baremetal-havana looks a bit sketchy21:40
ttxCan't really see what needs to be done there... and it depends on cinder/bare-metal-volumes which is not targeted to any milestone nor assigned to anyone21:41
*** alexb_ has joined #openstack-meeting21:41
*** nati_ueno has joined #openstack-meeting21:41
* ttx hugs his UPS in the middle of the storm21:41
*** jodom has quit IRC21:41
russellbttx: yeah, i can't figure that one out either21:41
russellbttx: actually, there used to be nova blueprints21:42
devanandai'm not aware of any work on baremetal-volumes21:42
russellband they all got deferred21:42
russellbdevananda: can you look at that nova blueprint and let me know if we should mark it implemented?  or what?21:42
ttxrussellb: maybe clarify with devananda and remove if not relevant anymore21:42
russellbttx: ack21:42
ttxin other news I'm not confident that encrypt-cinder-volumes will be unblocked -- https://review.openstack.org/#/c/30974/ has been stalling forever now21:42
devanandalooking21:42
*** lbragstad has quit IRC21:42
ttxdb-slave-handle seems to be struggling in review too.21:42
ttx(just in case you look for potential defers)21:42
russellbwe're pushing db-slave-handle pretty hard, i feel ok about that one21:43
russellbthe other ... not as much, especially since it's blocked21:43
ttxOnly one blueprint left needing triage db-compute-node-stats-remove21:43
russellbi've been checking in with the cinder encryption owner each week21:43
russellbhe seems confident each time, or at least hopeful ...21:43
devanandanova/pxeboot-ports is relevant and in progress, but the going has been very slow. different negative feedback at each turn, since most of the work is in neutron but it does tie into nova21:43
ttxrussellb: maybe lower the priority to indicate you have no idea if it will make it21:44
*** vipul-away is now known as vipul21:44
russellbttx: ok, will do so21:44
devanandabut that's the only nova BP still under the barmetal-havana umbrella.21:44
devanandamay be worth just dropping the umbrella since everything else was defferred?21:44
russellbdevananda: if it's the only one, maybe we should just cloe the tracker21:44
russellbheh21:44
ttxdevananda: yes21:44
ttxrussellb: anything else you wanted to mention ?21:44
russellbnope, thanks21:44
ttxAny question on Nova ?21:44
ttx#topic Heat status21:45
*** openstack changes topic to "Heat status (Meeting topic: project)"21:45
ttxstevebaker: o/21:45
stevebakeryop21:45
ttx#link https://launchpad.net/heat/+milestone/havana-321:45
ttx32% done, 16% under review, 48% in progress, 4% not started21:45
ttxSame remark as Cinder, not looking too bad but need more code proposed :)21:45
ttxHas work started on multiple-engines yet ?21:45
stevebakeryes, we'll decide on a FeatureProposalFreeze tomorrow, which will give us a new stick to wave21:45
ttxmore sticks!21:46
stevebakerI think some multiple-engines pre-work has happened, but will confirm tomorrow if it has a chance21:46
ttxIs there more to be done on watch-ceilometer ?21:46
stevebakerwe could force-defer some bps, but possibly not without offending some first contributors21:46
ttxgot reviews linked but all landed21:46
stevebakerI think watch-ceilometer still has some mopping up21:47
ttxok21:47
ttxopen-api-dsl (targeted to h3) depends on template-inputes and param-constraints, which have been deferred to 'next' ?21:47
*** henrynash has quit IRC21:47
ttxor is that not a strong dep ?21:47
stevebakeropen-api-dsl is a bit if a catch-all anyway. I'll discuss with randal tomorrow21:48
ttxit's better to have actionable bits as blueprints21:48
ttxthemes and catch-alls don't work very well when it comes to "landing" them21:48
ttxheat-trusts looks in jeopardy with delegation-impersonation-support not being completed yet21:48
stevebakeryes, that one needs to be more fine-grained21:48
ttxbut I guess that's shardyland21:49
stevebakerindeed it is, i believe there are some keystoneclient reviews in21:49
ttxas a general rule of thumb, stuff depending on other projects don't work very well in te last milestone of the cycle21:49
*** lpabon has quit IRC21:50
ttxit's better to nail them all by X-221:50
stevebakeryeah21:50
ttxbecause in X-3 everyone has their own cats to care for21:50
ttxstevebaker: anything else you want to raise ?21:50
stevebakerAt least FeatureProposalFreeze gives us a concrete date to make defer decisions21:50
stevebakerthat is it I think21:51
ttxright, let me know your chosen date and I'll document it21:51
stevebakerok21:51
ttxQuestions about Heat ?21:51
ttx#topic Horizon status21:51
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:51
ttxgabrielhurley: o/21:51
gabrielhurley\o21:51
ttx#link https://launchpad.net/horizon/+milestone/havana-321:51
*** AlanClark has quit IRC21:51
ttx6% done, 43% under review, 37% in progress, 12% not started21:51
ttxNeed to make progress on reviews and start landing stuff, otherwise the following weeks will be a bit busy21:51
gabrielhurleyagreed21:52
gabrielhurleythere are definitely some that will start merging this week21:52
ttxdidn't have anything special scaring me though.21:52
gabrielhurleythe openstack-requirements fiasco for django-openstack-auth has been a long road21:52
gabrielhurleywe're at the end though21:52
ttxgabrielhurley: indeed. anything else you wanted to mention ?21:53
gabrielhurleynot this week. I'll start clamping down on things next week21:53
*** dosaboy has quit IRC21:53
ttxQuestions on Horizon ?21:53
ttx#topic Incubated projects21:53
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:53
ttxhub_cap, devananda: news, questions ?21:54
hub_caphello. no news really. got 3 essential bps and 2 are in code review, 1 is heat and will be done by sep121:54
ttxhub_cap: how is the heat integration going ?21:54
hub_capits been siderailed for a while due to onboarding / other work21:54
hub_capbut i expect to pick it up this wk21:55
ttx"will be done by sep1" ok21:55
hub_capcorrect :)21:55
hub_capdone _and_ merged21:55
*** kspear has joined #openstack-meeting21:55
*** jlk has left #openstack-meeting21:55
hub_capdo we have do feature freeze this go round?21:55
ttxheh21:55
devanandattx: neither here. things are coming along, but nothing deployable yet21:55
ttxhub_cap: you don't *have* to21:55
devanandattx: i wont be putting in a feature freeze or any such, as it wouldn't make sense for ironic at this point21:55
hub_capi might after heat lands, lets say sep1 for us21:56
ttxhub_cap: it's sep 4 for almost everyone else.21:56
hub_capoh well i guess im an overachiever21:56
ttx(feature freeze)21:56
hub_capsep4 it is!21:56
hub_capso feature freeze is 1 day before h3 is cut?21:57
ttxfeature proposal freeze is an extra deadline some projects will use to defer features early21:57
ttxtwo days before, yes21:57
hub_capok cool21:57
ttxwe do a friday cut due to some holiday in some country that week21:57
hub_capput me down for a feature freeze21:57
hub_capill take a double shot of freeze plz21:57
*** wolfdreamer has quit IRC21:58
ttx"Sep 2Labor Day"21:58
med_US Holiday at least21:58
ttx"feature freeze" should be the name of a cocktail.21:58
hub_capdef21:59
hub_caplets make it so at HK21:59
med_Mike's Hard Feature Freeze21:59
ttxok, if you don't have more questions we'll close now21:59
hub_capjust hugs21:59
ttx#endmeeting21:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:59
openstackMeeting ended Tue Aug  6 21:59:29 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-08-06-21.01.html21:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-08-06-21.01.txt21:59
ttxthx everyone !21:59
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-08-06-21.01.log.html21:59
med_thanks ttx21:59
gabrielhurleyHey Horizon folks. I'm actually booked for another meeting currently, so I probably shouldn't run this one. If anyone else would like to volunteer, the startmeeting, endmeeting and topic commands are about all you need to know.22:01
*** dosaboy has joined #openstack-meeting22:01
*** hartsocks has quit IRC22:02
david-lylejust #startmeeting or topic too?22:02
*** Vasiliy has joined #openstack-meeting22:02
gabrielhurleyjust #startmeeting horizon22:02
david-lyle#startmeeting Horizon22:02
openstackMeeting started Tue Aug  6 22:02:29 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:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: Horizon)"22:02
openstackThe meeting name has been set to 'horizon'22:02
david-lyleThere we go22:02
jcoufalnice david-lyle22:02
*** sarob has quit IRC22:02
jcoufalhey everybody22:02
gabrielhurleyI do have one note, which is that if you've heard about the new CRIME/BREACH security news today the short version is that yes, Horizon is vulnerable along with most of the rest of the web, but that there's not much we can immediately do. Best thing to do for now is just to add some info on disabling gzip body compression to the docs.22:02
*** sarob has joined #openstack-meeting22:03
gabrielhurleyI can go into more detail later, or may send something to the list22:03
gabrielhurleythe scope/scale of the attack is still somewhat limited for django-based apps, thankfully22:03
gabrielhurleyat best you can compromise one session for the duration of that session, and there are *lots* of ways to steal a token in OpenStack currently (sadly)22:04
gabrielhurleythat's about it for me22:04
gabrielhurleyI'll lurk, but I leave the meeting to y'all22:04
*** epim has quit IRC22:05
jcoufalgabrielhurley: could you send more info into the list?22:05
*** epim has joined #openstack-meeting22:05
gabrielhurleysure22:05
jcoufalthanks22:06
david-lyle#topic Blueprints22:06
*** openstack changes topic to "Blueprints (Meeting topic: Horizon)"22:06
jpichjcoufal: fyr: https://www.djangoproject.com/weblog/2013/aug/06/breach-and-django/22:06
jcoufaljpich: oh, thank you, this is useful22:07
david-lylethanks jpich22:07
VasiliyHi all! Also please take a look at new blueprint - https://blueprints.launchpad.net/horizon/+spec/boot-from-volume-type-image22:07
*** sarob has quit IRC22:07
Vasiliyit's small implementation of new Nova feature22:07
*** sarob has joined #openstack-meeting22:08
jcoufalI have few blueprints here waiting for approvals22:08
jcoufalone is about navigation enhancements, we already discussed that, but it's waiting for approval: https://blueprints.launchpad.net/horizon/+spec/navigation-enhancement22:09
jcoufaldavid-lyle: would you be so kind to have a look on it, since you are involved? ^22:09
*** burt has quit IRC22:10
*** jlucci has quit IRC22:10
david-lylejcoufal: sure22:10
*** wolfdreamer has joined #openstack-meeting22:11
jcoufaldavid-lyle: thanks22:11
lchengUpdate for https://blueprints.launchpad.net/horizon/+spec/group-role-assignment, I've split this into two patches to make it easier to review. The first patch would be just for refactoring the project-user assignment page.  Then the second patch will cover the actual project-group assignment.22:11
*** SumitNaiksatam has quit IRC22:11
kspearVasiliy: is that different from https://blueprints.launchpad.net/horizon/+spec/improved-boot-from-volume ?22:11
Vasiliykspear: let me check22:11
kspearlcheng: thanks for that. will review both asap22:11
jcoufalthere are two more new BPs, both are related more to OpenStack Dashboard improvements22:12
lchengkspear: I haven't submitted the second patch, just in case I need to make some fixes for the first patch. :)22:12
jcoufalUpgrading Twitter Bootstrap to v3: https://blueprints.launchpad.net/horizon/+spec/bootstrap-update22:13
jcoufalMoving to font-icons: https://blueprints.launchpad.net/horizon/+spec/font-icons22:13
*** ivasev has quit IRC22:13
jcoufalif anybody can have a look as well on these two ^^22:13
dvargahttps://blueprints.launchpad.net/horizon/+spec/horizon-rootwrap new, wanting to pull in openstack common rootwrap for use by plugin writers.  Just want to get it on the radar so people can provide feedback.22:14
david-lylethat change scares me a bit22:15
kspearlcheng: fair enough. will review the first one then :)22:15
david-lyledvarga: if we go forward with it, is there a way to make that a configuration option?22:16
kspeardvarga: my first thought was can't you use rootwrap in your own tool? it doesn't seem like a massive benefit for this to be in horizon22:16
dvargadavid-lyle: If you do not supply any filters (none will be shipped by default) the command will not be executed22:17
dvargakspear: I could bundle it myself, but if other plugins would want this functionality it would be easier to make horizon a bit more extensible for anyone to use22:18
Vasiliykspear: thanks - you are right, this blueprint https://blueprints.launchpad.net/horizon/+spec/improved-boot-from-volume already includes feature from blueprint https://blueprints.launchpad.net/horizon/+spec/boot-from-volume-type-image.22:18
*** jecarey has quit IRC22:18
david-lyleok, I'll look at it again, but I think kspear has a valid point22:19
dvargahttps://wiki.openstack.org/wiki/Nova/Rootwrap goes into more detail on how that all works.  But basically if the command isn't listed in one of those filters it will not run22:19
*** vkmc has joined #openstack-meeting22:19
*** markvan has quit IRC22:20
kspearVasiliy: okay. would be good to coordinate with the assignee of the other bp and see what the plan is22:20
jpichVasiliy: Feel free to reach out to the current assignee to see if he could use a hand, if you'd like to help with the feature22:20
*** apevec has quit IRC22:20
*** nijaba has quit IRC22:20
david-lyleI've been working on https://blueprints.launchpad.net/horizon/+spec/rbac22:20
david-lylethe main issue I've come across is that no services seem to be loading their policy.json files into keystone yet22:21
*** colinmcnamara has joined #openstack-meeting22:21
Vasiliyjpich: ok - thanks - I will touch to him22:21
david-lylejust reading them from the file-system22:21
*** nijaba has joined #openstack-meeting22:21
david-lyledoes anyone have an installation where policy files are uploaded in keystone?22:22
kspeardavid-lyle: i think if horizon could intepret its own policy.json that would be a good start22:22
david-lylebut essentially Horizon's is the union of the services22:23
*** dcramer_ has quit IRC22:23
*** mdomsch has joined #openstack-meeting22:23
kspeardavid-lyle: i wonder if this something that really belongs in the python-*clients. how do we map policy entries to endpoints?22:23
gabrielhurleydvarga: I'll have to look into that one. It's definitely not a Havana target, and I'd have to see some compelling use cases for what you'd want to run as root on the webserver. That's a pretty nasty potential vulnerability vector when mostly you should be talking to service via APIs.22:23
david-lyleSo I'd like to propose copying keystone's for now and honoring that, get the policy engine going and working and then either expand to have policy files from the other services as well22:24
david-lyleand eventually pull them from keystone22:25
*** radez is now known as radez_g0n322:25
dvargagabrielhurley: thanks.  Basically the plugin I'm developing would be collecting diagnostic data and logs (sosreport) and that needs to run as root.  Rootwrap gives some nice filtering and restrictions which don't open it up to running arbitrary commands as root.22:25
gabrielhurleydavid-lyle: starting with keystone's seems reasonable.22:25
*** dolphm has quit IRC22:26
*** lastidiot has quit IRC22:26
gabrielhurleydvarga: mostly I'm leery of other things even running in the same execution context as Horizon. that seems like the wrong place to start.22:26
*** debo_os has joined #openstack-meeting22:26
gabrielhurleydvarga: when I deploy a webservice I want it to be as isolated as possible.22:26
david-lylegabrielhurley: that may be the scope for Havana-322:27
david-lyledepending on how many distractions I have22:27
gabrielhurleydavid-lyle: if that's what makes sense I'd certainly like to see the initial proof-of-concept so we know what work is ahead of us to take it the rest of the way22:27
gabrielhurleyit's a major undertaking, I'm aware22:27
david-lyleabsolutely22:27
david-lyleI think once the first one's in the other's should come quickly, but retrofitting to read from keystone will be another larger work item22:28
gabrielhurleyinteresting. I'd expect that to be relatively easy compared to the initial "parse this and do the right thing"22:28
gabrielhurleyit should be the same exact data, just one fetched via API and one read from disk22:29
david-lylewell, most of the engine comes from oslo22:29
david-lylejust need to add the policy checks around the calls22:29
gabrielhurleygotcha22:29
gabrielhurleywell, we'll see22:29
kspeardavid-lyle: that's what i'm wondering about. will there be a one to one mapping between policy checks in keystone and the actual api routes?22:30
david-lyle#topic Discussion22:30
*** openstack changes topic to "Discussion (Meeting topic: Horizon)"22:30
david-lylekspear: pretty much, although the Keystone file is not exhaustive for all potential api calls22:31
Vasiliysammiestoel: Hi Sam, I'd like help you with features on blueprint https://blueprints.launchpad.net/horizon/+spec/improved-boot-from-volume We started working on the same improvements https://blueprints.launchpad.net/horizon/+spec/boot-from-volume-type-image22:31
kspeardavid-lyle: okay, that should make things easier22:32
kspearso i hear that feature freeze is September 522:32
*** jrodom has joined #openstack-meeting22:32
kspearSeptember 4*22:33
*** changbl_ has quit IRC22:33
david-lyle1 month, it's coming quickly22:33
*** jrodom has quit IRC22:33
kspearso it'd be good to get code for bps up within around 2 weeks22:33
kspeardavid-lyle: it really is22:33
david-lylejpich: do you know where the ceilometer integration stands?22:34
jpichVasiliy: I don't think he's on IRC at the moment, his nickname starts with "Samos". There is a "Contact this user" link on his user page on launchpad, you might want to use that instead.22:34
*** jrodom has joined #openstack-meeting22:34
jpichdavid-lyle: Waiting on UX feedback still I think22:34
*** jrodom has quit IRC22:34
*** jrodom has joined #openstack-meeting22:35
Vasiliyjpich: thanks22:35
jcoufaljpich: is that? where is it happening?22:35
david-lyleok, I see it out there for review all the time, just want to make sure I'm not ignoring it for the wrong reason :)22:35
jcoufalI can have a look on that22:35
jcoufalif needed22:36
jpichjcoufal: Looks like you already replied to Brooklyn in the UX community :) Would love actionable feedback, even if it's just a start to be improved on later22:36
jcoufalah, that's the one22:36
jcoufalok22:36
jpichdavid-lyle: It'd be cool to get the API bits merged for a start, though there are some review comments on it that don't seem to have been taken into account it22:37
*** colinmcnamara has quit IRC22:37
jpichIt's on my TODO to poke at the reviews again...22:37
david-lyleseems like it will need to land in the next week or two22:37
jcoufaltalking about UX22:38
jcoufalI have one thing to bring up22:38
jcoufalthere is ongoing voting for new tool for UX discussions22:38
jpichThanks so much for driving this jcoufal22:39
*** edmund has quit IRC22:39
*** wolfdreamer has quit IRC22:39
jcoufalit is for all of developers, if you will need help with UX question that would be the tool where to start22:39
jcoufalso, whoever is interested, feel free to participate here: http://www.surveymonkey.com/s/MNGV8D522:40
jcoufaldeadline is until Friday midnight (GMT)22:40
david-lylejust need time to checkout Discourse22:40
pcm_vote early vote often :)22:40
david-lylea Chicago voter in the house22:41
jcoufaljpich: np, I am happy we moved forward22:41
lifelessttx: sorry, I need to put the meeting in my calendar :(22:41
david-lyleSeems like we're winding down, any other issues/topics?22:42
*** galstrom is now known as galstrom_zzz22:42
david-lylelooks like we're good. Thanks everyone!22:44
jpichThanks22:44
david-lyle#endmeeting22:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:44
openstackMeeting ended Tue Aug  6 22:44:33 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-08-06-22.02.html22:44
*** lbragstad_ has joined #openstack-meeting22:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-08-06-22.02.txt22:44
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-08-06-22.02.log.html22:44
kspearbye all22:44
*** kspear has quit IRC22:44
*** pcm_ has quit IRC22:45
*** gabrielhurley has quit IRC22:45
jcoufalthanks david-lyle, it was professional22:45
david-lyleit was something ;)22:45
jcoufalhave a good night/day all22:45
david-lylethanks for bearing with me22:45
*** sarob has quit IRC22:46
jpich:) Thanks for chairing david-lyle22:46
jpichHave a good day everyone22:46
*** jpich has quit IRC22:46
*** jcoufal has quit IRC22:46
*** sarob has joined #openstack-meeting22:46
*** Vasiliy has quit IRC22:50
*** sarob has quit IRC22:51
*** lbragstad_ has quit IRC22:53
*** vkmc has quit IRC22:54
*** sarob has joined #openstack-meeting22:55
*** mdomsch has quit IRC22:56
*** SumitNaiksatam has joined #openstack-meeting22:58
*** thomasbiege has quit IRC23:00
*** pentameter has quit IRC23:02
*** dvarga has quit IRC23:07
*** jrodom has quit IRC23:08
*** ivar-lazzaro_ has quit IRC23:08
*** Swami has quit IRC23:10
*** david-lyle has quit IRC23:11
*** sushils has quit IRC23:11
*** david-lyle has joined #openstack-meeting23:11
*** Swami has joined #openstack-meeting23:12
*** mrodden has quit IRC23:14
*** rnirmal has quit IRC23:19
*** nijaba has quit IRC23:21
*** nijaba has joined #openstack-meeting23:22
*** fnaval_ has quit IRC23:24
*** alexb_ has quit IRC23:25
*** sarob has quit IRC23:25
*** markpeek has quit IRC23:25
*** sarob has joined #openstack-meeting23:26
*** tedross has joined #openstack-meeting23:28
*** sarob has quit IRC23:30
*** mrodden has joined #openstack-meeting23:33
*** IlyaE has quit IRC23:34
*** mrodden1 has joined #openstack-meeting23:35
*** mrodden has quit IRC23:37
*** tedross has quit IRC23:40
*** haomaiwa_ has quit IRC23:45
*** zul has joined #openstack-meeting23:49
*** lastidiot has joined #openstack-meeting23:49
*** dani4571 has quit IRC23:53

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