Tuesday, 2013-05-21

*** SumitNaiksatam has joined #openstack-meeting00:04
*** colinmcnamara has quit IRC00:05
*** IlyaE has quit IRC00:07
*** martine has joined #openstack-meeting00:08
*** nati_ueno has quit IRC00:10
*** ryanpetrello has joined #openstack-meeting00:12
*** markvoelker1 has quit IRC00:12
*** jecarey has joined #openstack-meeting00:14
*** novas0x2a|laptop has quit IRC00:18
*** seanrob has joined #openstack-meeting00:25
*** bdpayne has quit IRC00:29
*** nati_ueno has joined #openstack-meeting00:29
*** seanrob has quit IRC00:30
*** seanrob has joined #openstack-meeting00:30
*** salv-orlando has joined #openstack-meeting00:32
*** salv-orlando_ has quit IRC00:32
*** digitalsanctum has joined #openstack-meeting00:33
*** seanrob has quit IRC00:35
*** sushils has quit IRC00:37
*** cp16net|away is now known as cp16net00:37
*** reed_ has joined #openstack-meeting00:39
*** Mandell has joined #openstack-meeting00:40
*** jecarey has quit IRC00:40
*** Racha has joined #openstack-meeting00:40
*** jasondotstar has joined #openstack-meeting00:41
*** Racha has quit IRC00:45
*** reed__ has joined #openstack-meeting00:47
*** reed_ has quit IRC00:48
*** lloydde has joined #openstack-meeting00:52
*** IlyaE has joined #openstack-meeting00:53
*** llu_linux has quit IRC00:54
*** llu has joined #openstack-meeting00:54
*** vbannai_ has quit IRC00:55
*** ryanpetrello has quit IRC00:57
*** salv-orlando has quit IRC00:57
*** lloydde has quit IRC00:57
*** flwang has quit IRC00:59
*** changbl has joined #openstack-meeting01:00
*** openrk has joined #openstack-meeting01:02
*** tomoe_ has joined #openstack-meeting01:04
*** gyee has quit IRC01:05
*** yaguang has joined #openstack-meeting01:05
*** markpeek has quit IRC01:08
*** shang_ has joined #openstack-meeting01:09
*** martine has quit IRC01:09
*** nati_ueno has quit IRC01:09
*** Tross has quit IRC01:15
*** digitalsanctum has quit IRC01:16
*** markvoelker1 has joined #openstack-meeting01:19
*** radez_g0n3 is now known as radez01:20
*** IlyaE has quit IRC01:20
*** maurosr- has joined #openstack-meeting01:22
*** manip has quit IRC01:23
*** test_ has joined #openstack-meeting01:23
*** test_ has left #openstack-meeting01:24
*** carl_baldwin has quit IRC01:24
*** Tross has joined #openstack-meeting01:26
*** maurosr has quit IRC01:26
*** carl_baldwin has joined #openstack-meeting01:27
*** openrk has quit IRC01:28
*** litong has quit IRC01:30
*** terry7 has quit IRC01:31
*** ewindisch has quit IRC01:33
*** neelashah has joined #openstack-meeting01:34
*** marun has joined #openstack-meeting01:36
*** jrodom has joined #openstack-meeting01:37
*** jogo has joined #openstack-meeting01:40
*** seanrob has joined #openstack-meeting01:40
*** jogo has left #openstack-meeting01:40
*** radez is now known as radez_g0n301:43
*** seanrob has quit IRC01:45
*** jrodom has quit IRC01:46
*** carl_baldwin has quit IRC01:46
*** jrodom has joined #openstack-meeting01:47
*** adalbas has quit IRC01:48
*** markpeek has joined #openstack-meeting01:50
*** saurabhs has quit IRC01:53
*** shiv_ has quit IRC01:59
*** timello has quit IRC02:01
*** timello has joined #openstack-meeting02:02
*** enikanorov_ has quit IRC02:05
*** carl_baldwin has joined #openstack-meeting02:06
*** timello has quit IRC02:06
*** enikanorov has joined #openstack-meeting02:06
*** seanrob has joined #openstack-meeting02:09
*** bdpayne has joined #openstack-meeting02:15
*** flwang has joined #openstack-meeting02:17
*** shang_ has quit IRC02:18
*** shang has quit IRC02:18
*** amotoki has quit IRC02:18
*** yamahata__ has quit IRC02:18
*** yamahata__ has joined #openstack-meeting02:21
*** amotoki has joined #openstack-meeting02:21
*** dwcramer has quit IRC02:22
*** carl_baldwin has quit IRC02:24
*** devananda is now known as cipher_zero02:24
*** emagana has quit IRC02:24
*** cipher_zero is now known as devananda02:24
*** elo has joined #openstack-meeting02:25
*** nati_ueno has joined #openstack-meeting02:26
*** timello has joined #openstack-meeting02:26
*** nati_ueno has quit IRC02:27
*** Tross has quit IRC02:27
*** nati_ueno has joined #openstack-meeting02:28
*** carl_baldwin has joined #openstack-meeting02:29
*** ewindisch has joined #openstack-meeting02:29
*** fungi has quit IRC02:30
*** seanrob has quit IRC02:32
*** seanrob has joined #openstack-meeting02:33
*** dwcramer has joined #openstack-meeting02:34
*** timello has quit IRC02:36
*** yaguang has quit IRC02:36
*** cp16net is now known as cp16net|away02:37
*** seanrob has quit IRC02:38
*** mytest has quit IRC02:41
*** timello has joined #openstack-meeting02:41
*** MarkAtwood has joined #openstack-meeting02:41
*** timello has quit IRC02:42
*** timello has joined #openstack-meeting02:44
*** yaguang has joined #openstack-meeting02:46
*** jrodom has quit IRC02:46
*** timello has joined #openstack-meeting02:47
*** fungi has joined #openstack-meeting02:49
*** timello has quit IRC02:51
*** timello has joined #openstack-meeting02:52
*** carl_baldwin has quit IRC02:54
*** changbl has quit IRC02:56
*** timello has quit IRC02:58
*** gongysh has quit IRC02:58
*** timello has joined #openstack-meeting02:58
*** Tross has joined #openstack-meeting03:00
*** ashwini has quit IRC03:03
*** bdpayne has quit IRC03:05
*** dperaza has quit IRC03:09
*** neelashah has quit IRC03:10
*** vkmc has quit IRC03:12
*** shang has joined #openstack-meeting03:16
*** jasondotstar has quit IRC03:20
*** Tross has quit IRC03:21
*** amyt has joined #openstack-meeting03:22
*** sandywalsh has quit IRC03:26
*** amyt has quit IRC03:28
*** amyt has joined #openstack-meeting03:29
*** IlyaE has joined #openstack-meeting03:40
*** seanrob has joined #openstack-meeting03:43
*** SergeyLukjanov has joined #openstack-meeting03:44
*** Tross has joined #openstack-meeting03:45
*** seanrob has quit IRC03:48
*** danwent has joined #openstack-meeting03:56
*** dwcramer has quit IRC03:59
*** ozstacker has joined #openstack-meeting04:01
*** nati_ueno has quit IRC04:04
*** _ozstacker_ has quit IRC04:05
*** sungju has quit IRC04:05
*** rkukura has quit IRC04:07
*** anniec has joined #openstack-meeting04:07
*** keith_bray has joined #openstack-meeting04:07
*** danwent has quit IRC04:09
*** _ozstacker_ has joined #openstack-meeting04:12
*** ozstacker has quit IRC04:15
*** sungju has joined #openstack-meeting04:20
*** martine has joined #openstack-meeting04:28
*** boris-42 has joined #openstack-meeting04:33
*** alexxu has quit IRC04:39
*** anniec has quit IRC04:43
*** lloydde has joined #openstack-meeting04:44
*** asalkeld has quit IRC04:46
*** reed__ has quit IRC04:46
*** keith_bray has quit IRC04:47
*** alexxu has joined #openstack-meeting04:52
*** asalkeld has joined #openstack-meeting04:55
*** carlp is now known as carlp-away04:55
*** na_bot8 has joined #openstack-meeting04:58
*** SergeyLukjanov has quit IRC04:59
*** haomaiwang has joined #openstack-meeting05:03
*** martine has quit IRC05:05
*** boris-42 has quit IRC05:05
*** markvoelker1 has quit IRC05:06
*** Kharec has joined #openstack-meeting05:08
*** dguitarbite has joined #openstack-meeting05:08
*** ctracey has quit IRC05:09
*** SergeyLukjanov has joined #openstack-meeting05:14
*** SergeyLukjanov has quit IRC05:15
*** afazekas has joined #openstack-meeting05:41
*** danwent has joined #openstack-meeting05:42
*** nati_ueno has joined #openstack-meeting05:44
*** mrunge has joined #openstack-meeting05:45
*** amyt has quit IRC05:47
*** markpeek has quit IRC05:47
*** danwent has quit IRC05:47
*** nati_ueno has quit IRC05:49
*** MarkAtwood has quit IRC05:58
*** SergeyLukjanov has joined #openstack-meeting06:00
*** IlyaE has quit IRC06:01
*** garyk has joined #openstack-meeting06:02
*** lloydde has quit IRC06:04
*** mikal has quit IRC06:12
*** sacharya has joined #openstack-meeting06:14
*** danwent has joined #openstack-meeting06:21
*** jcoufal has joined #openstack-meeting06:25
*** sungju has quit IRC06:33
*** sacharya1 has joined #openstack-meeting06:38
*** sacharya has quit IRC06:38
*** _ozstacker_ has quit IRC06:39
*** jhenner has joined #openstack-meeting06:41
*** derekh has joined #openstack-meeting06:44
*** Mandell has quit IRC06:45
*** flaper87 has joined #openstack-meeting06:47
*** danwent has quit IRC06:47
*** egallen has joined #openstack-meeting06:50
*** crank has quit IRC06:53
*** boris-42 has joined #openstack-meeting06:56
*** MarkAtwood has joined #openstack-meeting06:58
*** derekh has quit IRC06:59
*** boris-42 has quit IRC07:01
*** boris-42 has joined #openstack-meeting07:03
*** epim has quit IRC07:06
*** ozstacker has joined #openstack-meeting07:21
*** ozstacker has quit IRC07:24
*** ozstacker has joined #openstack-meeting07:26
*** ozstacker has quit IRC07:27
*** haomaiwang has quit IRC07:28
*** ozstacker has joined #openstack-meeting07:29
*** ozstacker has quit IRC07:31
*** ozstacker has joined #openstack-meeting07:33
*** alexheneveld has joined #openstack-meeting07:33
*** ozstacker has quit IRC07:35
*** derekh has joined #openstack-meeting07:35
*** haomaiwang has joined #openstack-meeting07:36
*** MarkAtwood has quit IRC07:36
*** ozstacker has joined #openstack-meeting07:36
*** ozstacker has quit IRC07:41
*** ozstacker has joined #openstack-meeting07:42
*** derekh has quit IRC07:44
*** sungju has joined #openstack-meeting07:44
*** Kharec has quit IRC07:44
*** sacharya1 has quit IRC07:45
*** Kharec has joined #openstack-meeting07:46
*** jtomasek has joined #openstack-meeting07:49
*** ozstacker has quit IRC07:51
*** ozstacker has joined #openstack-meeting07:53
*** crank has joined #openstack-meeting07:54
*** ndipanov has joined #openstack-meeting07:54
*** afazekas has quit IRC07:54
*** afazekas has joined #openstack-meeting07:54
*** derekh has joined #openstack-meeting07:55
*** psedlak has joined #openstack-meeting07:58
*** sungju has quit IRC08:00
*** Mandell has joined #openstack-meeting08:01
*** Mandell has quit IRC08:09
*** aloga has joined #openstack-meeting08:11
*** afazekas has quit IRC08:12
*** mkollaro has joined #openstack-meeting08:12
*** mrunge has quit IRC08:19
*** johnthetubaguy has joined #openstack-meeting08:23
*** mrunge has joined #openstack-meeting08:24
*** afazekas has joined #openstack-meeting08:32
*** haomaiwang has quit IRC08:33
*** haomaiwang has joined #openstack-meeting08:34
*** flwang has quit IRC09:03
*** sungju has joined #openstack-meeting09:07
*** sungju has quit IRC09:18
*** gongysh has joined #openstack-meeting09:18
*** samc_ has joined #openstack-meeting09:36
*** sungju has joined #openstack-meeting09:37
*** salv-orlando has joined #openstack-meeting09:41
*** sungju has quit IRC09:41
*** tomoe_ has quit IRC09:42
*** johnthetubaguy1 has joined #openstack-meeting09:42
*** johnthetubaguy has quit IRC09:44
*** sante has joined #openstack-meeting09:51
*** garyk has quit IRC09:56
*** garyk has joined #openstack-meeting09:59
*** haomaiwang has quit IRC10:00
*** mikal has joined #openstack-meeting10:03
*** haomaiwang has joined #openstack-meeting10:14
*** flwang has joined #openstack-meeting10:28
*** salv-orlando has quit IRC10:29
*** salv-orlando_ has joined #openstack-meeting10:29
*** flwang has quit IRC10:37
*** egallen has quit IRC10:43
*** yaguang has quit IRC10:54
*** dguitarbite has quit IRC10:57
*** alexheneveld has quit IRC10:57
*** sandywalsh has joined #openstack-meeting10:58
*** bogdando has quit IRC11:03
*** salv-orlando has joined #openstack-meeting11:08
*** salv-orlando_ has quit IRC11:08
*** martine_ has joined #openstack-meeting11:11
*** samc_ has quit IRC11:11
*** bogdando has joined #openstack-meeting11:12
*** jrodom has joined #openstack-meeting11:13
*** alexheneveld has joined #openstack-meeting11:16
*** jrodom has quit IRC11:17
*** BobBall has quit IRC11:18
*** jrodom has joined #openstack-meeting11:18
*** adalbas has joined #openstack-meeting11:27
*** jrodom has quit IRC11:40
*** EmilienM has quit IRC11:41
*** christophk has quit IRC11:41
*** SergeyLukjanov has quit IRC11:41
*** johnthetubaguy1 has quit IRC11:41
*** jang has quit IRC11:41
*** nimi has quit IRC11:41
*** markvoelker has quit IRC11:41
*** jamespage has quit IRC11:41
*** rainya has quit IRC11:41
*** kpepple_ has quit IRC11:41
*** ttx has quit IRC11:41
*** noslzzp has quit IRC11:41
*** hartsocks has quit IRC11:41
*** med_ has quit IRC11:41
*** troytoma` has quit IRC11:41
*** edleafe has quit IRC11:41
*** radez_g0n3 has quit IRC11:41
*** smoser has quit IRC11:41
*** dendrobates has quit IRC11:41
*** mkollaro has quit IRC11:41
*** DuncanT has quit IRC11:41
*** ttrifonov has quit IRC11:41
*** jdurgin has quit IRC11:41
*** elo has quit IRC11:41
*** Tross has quit IRC11:41
*** cyeoh has quit IRC11:41
*** christophk has joined #openstack-meeting11:41
*** dendrobates has joined #openstack-meeting11:41
*** troytoman-away has joined #openstack-meeting11:41
*** dendrobates has quit IRC11:41
*** dendrobates has joined #openstack-meeting11:41
*** ttx has joined #openstack-meeting11:41
*** ttx has quit IRC11:41
*** ttx has joined #openstack-meeting11:41
*** edleafe has joined #openstack-meeting11:41
*** radez_g0n3 has joined #openstack-meeting11:41
*** smoser has joined #openstack-meeting11:41
*** johnthetubaguy has joined #openstack-meeting11:41
*** elo has joined #openstack-meeting11:41
*** hartsocks has joined #openstack-meeting11:42
*** kpepple has joined #openstack-meeting11:42
*** ttrifonov has joined #openstack-meeting11:42
*** rainya has joined #openstack-meeting11:42
*** Tross has joined #openstack-meeting11:42
*** DuncanT has joined #openstack-meeting11:42
*** noslzzp has joined #openstack-meeting11:42
*** SergeyLukjanov has joined #openstack-meeting11:42
*** christophk has quit IRC11:42
*** edleafe has quit IRC11:42
*** rainya has quit IRC11:42
*** hartsocks has quit IRC11:42
*** noslzzp has quit IRC11:42
*** ttx has quit IRC11:42
*** radez_g0n3 has quit IRC11:42
*** johnthetubaguy has quit IRC11:42
*** dendrobates has quit IRC11:42
*** DuncanT has quit IRC11:42
*** smoser has quit IRC11:42
*** ttrifonov has quit IRC11:42
*** elo has quit IRC11:42
*** troytoman-away has quit IRC11:42
*** SergeyLukjanov has quit IRC11:42
*** nimi has joined #openstack-meeting11:42
*** Tross has quit IRC11:42
*** edleafe has joined #openstack-meeting11:42
*** dendrobates has joined #openstack-meeting11:42
*** dendrobates has quit IRC11:42
*** dendrobates has joined #openstack-meeting11:42
*** rainya has joined #openstack-meeting11:42
*** troytoman-away has joined #openstack-meeting11:42
*** mkollaro has joined #openstack-meeting11:42
*** ttx has joined #openstack-meeting11:42
*** ttx has quit IRC11:42
*** ttx has joined #openstack-meeting11:42
*** smoser has joined #openstack-meeting11:42
*** radez_g0n3 has joined #openstack-meeting11:42
*** johnthetubaguy has joined #openstack-meeting11:42
*** elo has joined #openstack-meeting11:42
*** christophk has joined #openstack-meeting11:42
*** jang has joined #openstack-meeting11:42
*** hartsocks has joined #openstack-meeting11:42
*** cyeoh has joined #openstack-meeting11:42
*** DuncanT has joined #openstack-meeting11:42
*** Tross has joined #openstack-meeting11:42
*** noslzzp has joined #openstack-meeting11:43
*** ttrifonov has joined #openstack-meeting11:43
*** SergeyLukjanov has joined #openstack-meeting11:43
*** markvoelker has joined #openstack-meeting11:43
*** jdurgin has joined #openstack-meeting11:43
*** sandywalsh has quit IRC11:43
*** EmilienM has joined #openstack-meeting11:43
*** christophk has quit IRC11:43
*** EmilienM has quit IRC11:43
*** jang has quit IRC11:43
*** johnthetubaguy has quit IRC11:43
*** radez_g0n3 has quit IRC11:43
*** nimi has quit IRC11:43
*** hartsocks has quit IRC11:43
*** edleafe has quit IRC11:43
*** rainya has quit IRC11:43
*** markvoelker has quit IRC11:43
*** ttx has quit IRC11:43
*** noslzzp has quit IRC11:43
*** kpepple has quit IRC11:43
*** dendrobates has quit IRC11:43
*** troytoman-away has quit IRC11:43
*** elo has quit IRC11:43
*** DuncanT has quit IRC11:43
*** mkollaro has quit IRC11:43
*** jdurgin has quit IRC11:43
*** ttrifonov has quit IRC11:43
*** cyeoh has quit IRC11:43
*** smoser has quit IRC11:43
*** Tross has quit IRC11:43
*** SergeyLukjanov has quit IRC11:43
*** ttx has joined #openstack-meeting11:43
*** EmilienM has joined #openstack-meeting11:43
*** ttx has quit IRC11:43
*** ttx has joined #openstack-meeting11:43
*** dendrobates has joined #openstack-meeting11:43
*** dendrobates has joined #openstack-meeting11:44
*** troytoman-away has joined #openstack-meeting11:44
*** rainya has joined #openstack-meeting11:44
*** radez_g0n3 has joined #openstack-meeting11:44
*** kpepple has joined #openstack-meeting11:44
*** edleafe has joined #openstack-meeting11:44
*** EmilienM has quit IRC11:44
*** ttx has quit IRC11:44
*** kpepple has quit IRC11:44
*** dendrobates has quit IRC11:44
*** radez_g0n3 has quit IRC11:44
*** troytoman-away has quit IRC11:44
*** edleafe has quit IRC11:44
*** smoser has joined #openstack-meeting11:44
*** elo has joined #openstack-meeting11:44
*** johnthetubaguy has joined #openstack-meeting11:44
*** jcoufal has quit IRC11:44
*** hartsocks has joined #openstack-meeting11:44
*** hartsocks has quit IRC11:44
*** elo has quit IRC11:44
*** johnthetubaguy has quit IRC11:44
*** smoser has quit IRC11:44
*** ttx has joined #openstack-meeting11:44
*** troytoman-away has joined #openstack-meeting11:44
*** ttx has quit IRC11:44
*** ttx has joined #openstack-meeting11:44
*** dendrobates has joined #openstack-meeting11:44
*** dendrobates has joined #openstack-meeting11:44
*** christophk has joined #openstack-meeting11:44
*** ttx has quit IRC11:44
*** christophk has quit IRC11:44
*** dendrobates has quit IRC11:44
*** troytoman-away has quit IRC11:44
*** radez_g0n3 has joined #openstack-meeting11:44
*** ttx has joined #openstack-meeting11:44
*** ttx has joined #openstack-meeting11:44
*** dendrobates has joined #openstack-meeting11:44
*** dendrobates has quit IRC11:44
*** dendrobates has joined #openstack-meeting11:44
*** noslzzp has joined #openstack-meeting11:44
*** troytoman-away has joined #openstack-meeting11:44
*** mkollaro has joined #openstack-meeting11:44
*** Tross has joined #openstack-meeting11:44
*** Ritz-Laptop has quit IRC11:44
*** edleafe has joined #openstack-meeting11:44
*** smoser has joined #openstack-meeting11:44
*** SergeyLukjanov has joined #openstack-meeting11:44
*** ttrifonov has joined #openstack-meeting11:44
*** DuncanT has joined #openstack-meeting11:44
*** johnthetubaguy has joined #openstack-meeting11:44
*** elo has joined #openstack-meeting11:44
*** markvoelker has joined #openstack-meeting11:44
*** hartsocks has joined #openstack-meeting11:44
*** dabo has quit IRC11:44
*** kpepple has joined #openstack-meeting11:44
*** johnthetubaguy has quit IRC11:44
*** markvoelker has quit IRC11:44
*** mkollaro has quit IRC11:44
*** dendrobates has quit IRC11:44
*** rainya has quit IRC11:44
*** noslzzp has quit IRC11:44
*** kpepple has quit IRC11:44
*** hartsocks has quit IRC11:44
*** edleafe has quit IRC11:44
*** troytoman-away has quit IRC11:44
*** ttx has quit IRC11:44
*** radez_g0n3 has quit IRC11:44
*** ttrifonov has quit IRC11:44
*** DuncanT has quit IRC11:44
*** elo has quit IRC11:44
*** smoser has quit IRC11:44
*** SergeyLukjanov has quit IRC11:44
*** ttx has joined #openstack-meeting11:44
*** ttx has quit IRC11:44
*** ttx has joined #openstack-meeting11:44
*** dendrobates has joined #openstack-meeting11:44
*** dendrobates has joined #openstack-meeting11:44
*** christophk has joined #openstack-meeting11:44
*** christophk has quit IRC11:44
*** dendrobates has quit IRC11:44
*** ttx has quit IRC11:44
*** troytoman-away has joined #openstack-meeting11:44
*** jdurgin has joined #openstack-meeting11:44
*** pcm__ has joined #openstack-meeting11:44
*** troytoman-away has quit IRC11:44
*** radez_g0n3 has joined #openstack-meeting11:44
*** jdurgin has quit IRC11:44
*** Tross has quit IRC11:44
*** ttx has joined #openstack-meeting11:44
*** ttx has quit IRC11:44
*** ttx has joined #openstack-meeting11:44
*** dendrobates has joined #openstack-meeting11:44
*** dendrobates has joined #openstack-meeting11:44
*** smoser has joined #openstack-meeting11:44
*** nimi has joined #openstack-meeting11:44
*** ttx has quit IRC11:44
*** radez_g0n3 has quit IRC11:44
*** johnthetubaguy has joined #openstack-meeting11:44
*** johnthetubaguy has quit IRC11:44
*** hartsocks has joined #openstack-meeting11:44
*** jcoufal has joined #openstack-meeting11:44
*** elo has joined #openstack-meeting11:44
*** troytoman-away has joined #openstack-meeting11:44
*** nimi has quit IRC11:45
*** hartsocks has quit IRC11:45
*** dendrobates has quit IRC11:45
*** elo has quit IRC11:45
*** troytoman-away has quit IRC11:45
*** smoser has quit IRC11:45
*** ttrifonov has joined #openstack-meeting11:45
*** cyeoh has joined #openstack-meeting11:45
*** ttx has joined #openstack-meeting11:45
*** ttx has quit IRC11:45
*** ttx has joined #openstack-meeting11:45
*** ttrifonov has quit IRC11:45
*** ttx has quit IRC11:45
*** cyeoh has quit IRC11:45
*** troytoman-away has joined #openstack-meeting11:45
*** dabo has joined #openstack-meeting11:45
*** dendrobates has joined #openstack-meeting11:45
*** dendrobates has joined #openstack-meeting11:45
*** noslzzp has joined #openstack-meeting11:45
*** ttx has joined #openstack-meeting11:45
*** ttx has joined #openstack-meeting11:45
*** radez_g0n3 has joined #openstack-meeting11:45
*** christophk has joined #openstack-meeting11:45
*** DuncanT has joined #openstack-meeting11:45
*** smoser has joined #openstack-meeting11:45
*** jcoufal has quit IRC11:45
*** hartsocks has joined #openstack-meeting11:45
*** Tross has joined #openstack-meeting11:45
*** jdurgin has joined #openstack-meeting11:45
*** markvoelker has joined #openstack-meeting11:45
*** ttrifonov has joined #openstack-meeting11:45
*** rainya has joined #openstack-meeting11:45
*** edleafe has joined #openstack-meeting11:45
*** mkollaro has joined #openstack-meeting11:45
*** kpepple has joined #openstack-meeting11:46
*** nimi has joined #openstack-meeting11:46
*** EmilienM has joined #openstack-meeting11:46
*** cyeoh has joined #openstack-meeting11:46
*** johnthetubaguy has joined #openstack-meeting11:47
*** SergeyLukjanov has joined #openstack-meeting11:51
*** jang has joined #openstack-meeting11:52
*** ayoung has quit IRC11:54
*** jcoufal has joined #openstack-meeting11:57
*** radez_g0n3 is now known as radez11:57
*** radez is now known as radez_g0n311:57
*** vkmc has joined #openstack-meeting12:02
*** vkmc has joined #openstack-meeting12:02
*** radez_g0n3 is now known as radez12:02
*** egallen has joined #openstack-meeting12:07
*** adalbas has quit IRC12:07
*** maurosr- is now known as maurosr12:08
*** digitalsanctum has joined #openstack-meeting12:08
*** digitalsanctum has left #openstack-meeting12:08
*** sandywalsh has joined #openstack-meeting12:17
*** krtaylor has joined #openstack-meeting12:20
*** radez is now known as radez_g0n312:20
*** HenryG has quit IRC12:21
*** jrodom has joined #openstack-meeting12:22
*** adalbas has joined #openstack-meeting12:23
*** jamespage has joined #openstack-meeting12:23
*** jamespage has quit IRC12:23
*** jamespage has joined #openstack-meeting12:23
*** tomoe_ has joined #openstack-meeting12:24
*** salv-orlando_ has joined #openstack-meeting12:24
*** salv-orlando has quit IRC12:24
*** salv-orlando_ is now known as salv-orlando12:24
*** jrodom has quit IRC12:30
*** SergeyLukjanov has quit IRC12:30
*** lbragstad has quit IRC12:37
*** mdomsch has quit IRC12:38
*** jrodom has joined #openstack-meeting12:45
*** anniec has joined #openstack-meeting12:46
*** SergeyLukjanov has joined #openstack-meeting12:49
*** jbjohnso has joined #openstack-meeting12:50
*** jang has quit IRC12:52
*** elo has joined #openstack-meeting12:54
*** jang has joined #openstack-meeting12:56
*** lbragstad has joined #openstack-meeting13:01
*** ndipanov has quit IRC13:01
*** dprince has joined #openstack-meeting13:03
*** salv-orlando has quit IRC13:03
*** salv-orlando_ has joined #openstack-meeting13:03
*** salv-orlando has joined #openstack-meeting13:04
*** salv-orlando_ has quit IRC13:04
*** ayoung has joined #openstack-meeting13:05
*** beagles has joined #openstack-meeting13:07
*** eharney has joined #openstack-meeting13:07
*** mrunge has quit IRC13:08
*** jrodom has quit IRC13:09
*** litong has joined #openstack-meeting13:12
*** ndipanov has joined #openstack-meeting13:15
*** dperaza has joined #openstack-meeting13:15
*** neelashah has joined #openstack-meeting13:16
*** jang has quit IRC13:17
*** dolphm has joined #openstack-meeting13:18
*** dolphm has quit IRC13:18
*** jang has joined #openstack-meeting13:19
*** Tross has quit IRC13:21
*** medberry has joined #openstack-meeting13:22
*** medberry has joined #openstack-meeting13:22
*** afazekas has quit IRC13:23
*** pnavarro has joined #openstack-meeting13:24
*** Tross has joined #openstack-meeting13:28
*** woodspa has joined #openstack-meeting13:31
*** spzala has joined #openstack-meeting13:36
*** HenryG has joined #openstack-meeting13:37
*** sacharya has joined #openstack-meeting13:42
*** afazekas has joined #openstack-meeting13:44
*** jamespage_ has joined #openstack-meeting13:49
*** stevemar has joined #openstack-meeting13:49
*** jaypipes has joined #openstack-meeting13:51
*** dwcramer has joined #openstack-meeting13:51
*** ashwini has joined #openstack-meeting13:52
*** changbl has joined #openstack-meeting13:52
*** salv-orlando has quit IRC13:53
*** jamespage_ has quit IRC13:53
*** amyt has joined #openstack-meeting13:54
*** markpeek has joined #openstack-meeting13:55
*** radez_g0n3 is now known as radez14:05
*** ndipanov has quit IRC14:09
*** egallen has quit IRC14:13
*** matiu has quit IRC14:18
*** dolphm has joined #openstack-meeting14:20
*** ndipanov has joined #openstack-meeting14:22
*** johnthetubaguy1 has joined #openstack-meeting14:26
*** johnthetubaguy has quit IRC14:28
*** keith_bray has joined #openstack-meeting14:29
*** ladquin has quit IRC14:32
*** ladquin has joined #openstack-meeting14:32
*** sacharya has quit IRC14:36
*** cp16net|away is now known as cp16net14:37
*** jeblair is now known as fakegerritbot14:38
*** mdomsch has joined #openstack-meeting14:38
*** fakegerritbot is now known as jeblair14:39
*** ijw has joined #openstack-meeting14:41
*** glikson has joined #openstack-meeting14:44
*** ladquin has quit IRC14:44
*** ladquin has joined #openstack-meeting14:44
*** ociuhandu has joined #openstack-meeting14:45
*** johnthetubaguy1 is now known as johnthetubaguy14:45
*** IlyaE has joined #openstack-meeting14:47
*** PhilDay has joined #openstack-meeting14:47
*** carl_baldwin has joined #openstack-meeting14:51
*** jgallard_ has joined #openstack-meeting14:54
*** luis_fdez has joined #openstack-meeting14:54
*** liuxpei has joined #openstack-meeting14:55
*** ladquin has quit IRC14:55
*** ladquin has joined #openstack-meeting14:55
*** ladquin has quit IRC14:57
*** ladquin has joined #openstack-meeting14:57
n0ano#startmeeting scheduler sub-group15:00
openstackMeeting started Tue May 21 15:00:19 2013 UTC.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: scheduler sub-group)"15:00
openstackThe meeting name has been set to 'scheduler_sub_group'15:00
n0anoshow of hands, anyone here for the scheduler meeting?15:00
*** senhuang has joined #openstack-meeting15:00
* glikson here15:00
*** yoshiotu has joined #openstack-meeting15:00
jgallard_hi all :)15:00
senhuanghi all15:00
*** dhellmann-away is now known as dhellmann15:01
*** danwent has joined #openstack-meeting15:01
n0anoWell, while waiting for people to get here, a little administrivia...15:01
n0anoI have to leave after 20 min (my wife is having oral surgery) senhuang can I tag you to chari when I leave (mainly make sure you do an #endmeeting)?15:02
senhuangsure15:02
n0anos/chari/chair15:02
n0anosenhuang, tnx15:02
senhuangn0ano: no problem!15:02
jgallard_n0ano, I'm not sure someone else can do an endmeeting for you15:02
n0ano#chair senhuang15:02
openstackCurrent chairs: n0ano senhuang15:02
*** mdomsch has quit IRC15:03
n0anouh oh, I have to be careful, senhuang can override my commands now :-)15:03
n0anoanyway, let15:03
jgallard_n0ano, ok :)15:03
n0anolet's get started, maybe some lurkers will appear15:03
n0ano#topic network bandwidth aware scheduling15:04
*** openstack changes topic to "network bandwidth aware scheduling (Meeting topic: scheduler sub-group)"15:04
PhilDayI filed a BP to cover this.15:04
n0anoanyone here want to drive this discussion (I have some ideas but this is not my BP)15:04
n0anoPhilDay, you have the floor15:04
alaskihi all15:04
garykhi15:04
PhilDayBasic idea for now is pretty simple - count the bandwidth allocated to flavors in the the same sort of way that we do memory15:05
PhilDayso that its possibel to use overall bandwidth of a server as a scheduling constraint15:05
n0anofine idea, my concern is that this is rather specific, I'd prefer a more general mechanism15:06
garykPhilDay: do you mean taking free bandwidth into account?15:06
PhilDayDifference is that the hypervisor probably can't derive the total available bandwidth, so it will need to be configured on a per host basis15:06
senhuangthis requires the host-manager to report the total bandwidth capability to the scheduler?15:06
PhilDayYep15:06
n0anocould this be part of something like extending data in host state that has been proposed?15:06
PhilDayIf that is in place then we'd build on that for sure15:06
*** mdomsch has joined #openstack-meeting15:07
PhilDaythe flavor already has an rxtx_factor which is used in Xen15:07
senhuangPhilDay: I see. that is good.15:07
PhilDaythere used to be an rxtx_cap, which is more along the lines that we were looking for15:07
gliksonyep, sounds like a reasonable extension to yet another kind of resource that would make sense to manage host capacity for.15:07
n0anowould this be an extension to the rxtx_factor or a replacement for it?15:08
PhilDayI'm not quiet sure what triggered the shift,  rxtx_factor is just a relative measure - so what you get with that depoend on which host you get scheduled to15:08
senhuangwhat the constraint will look like? will we have a constraint for rx and one for tx?15:09
PhilDayI was thinkign that maybe we could also set the rxtx valeu as a port property in case Quantum can do somethign more fancy with it in terms of QoS -15:09
PhilDayI was thiking more of just a sinlge cap, but I guess it could be two values if you think there is a use case.15:09
senhuangPhilDay: that might be something we can discuss with Quauntum team. they are also working on a QoS blueprint.15:10
n0anoif the rxtx is truly a ratio then it wouldn't really work for a QoS value, I can still steal rx bandwidth just by doing some tx15:10
PhilDayGiven that it goes into the flavor I'm wary of havign to have lost of different flavors for people to choose from15:10
n0anoPhilDay, in that case maybe it's more appropriate to be part of the image attributes15:11
garykin quantum there was a little discusion about qos, but nothing concreate at the moment15:11
*** jbjohnso has quit IRC15:11
PhilDayI'm always wary of buildign on too many other BPs - so maybe we juist go for a simple bandwitdh based scheduleing for now (i.e the network peer of memory capacity) so that we can stay independent15:11
*** kirankv has joined #openstack-meeting15:12
n0anounfortunately, the cloud provider (the who worries about bandwidth) has no control over the image attributes so that might not work.15:12
*** gyee has joined #openstack-meeting15:12
PhilDaydon'f follow your comment on image attricbutes ?15:12
gliksonPhilDay: true, adding an additional kind of resource would potentially invite many more flavors.. but I personally think it still makes sense.15:13
n0anoI thought there was an image contraints filter that utilized attributes stored as part of the meta data for the image15:14
*** dolphm has quit IRC15:14
* n0ano moved to a new house and my network isn't complete, can't access the right machine to research this15:14
n0anosenhuang, got to go, you are now in control15:15
PhilDayWell there are all sorts of additional filters you can have - but that's just adding more constartints to the scheduler to work with.  I don't see why image attributes wouls clash with network capacity ?15:15
senhuangn0ano: no problem.15:15
gliksonthere is a filter that matches image properties. but is it really an image property?15:15
*** keith_bray has quit IRC15:15
senhuangglikson: i agree that it is not an image property15:15
PhilDayI think it matches an image property (liek I need an AMD server) to a host capability (liek I an an AMD or x86 server)15:16
PhilDayI.e its just a binary capability filter.15:16
PhilDayThe network bandwidth is just concerned with "where does an instance of this flavor fit"15:17
senhuangPhilDay: There is also a json filter that can do more operators based on requests and capabilities.15:17
gliksonright -- not a capacity requirement. which sometimes could make sense, btw (to make sure that certain image can run with certain flavors).15:17
PhilDayYou can match images to flavors via min_ram and min_disk metadata15:17
PhilDayI'm not sure I'd see a used for min_rx or min_tx though15:18
PhilDayFliter scheduler does both capacity and capability matching15:18
PhilDayI think adding to the flavor definiton is a better model.15:19
PhilDayI'd rathe rhave it as a core property that encoded in extra_specs15:20
*** dolphm has joined #openstack-meeting15:20
senhuangthen the # of flavors *= # of min_rx, min_tx pairs15:20
*** keith_bray has joined #openstack-meeting15:21
senhuangi guess a little bit more details on the proposal will help15:21
PhilDayWell that depends on how much flexibility you want to provide users with15:21
PhilDayYou could make the same case for providing every single memory size, but no-one does that15:21
senhuangPhilDay: that is true..15:22
PhilDayThere is a BP page - hang on I'll dig out the link15:22
PhilDayhttps://blueprints.launchpad.net/nova/+spec/network-bandwidth-entitlement15:22
PhilDayhttps://wiki.openstack.org/wiki/NetworkBandwidthEntitlement15:22
PhilDayMaybe people could take a look and provide feedback next week ?15:23
senhuangthat is a good idea.15:23
senhuangshall we move on?15:23
senhuang#topic group/ensemble scheduling15:24
*** openstack changes topic to "group/ensemble scheduling (Meeting topic: scheduler sub-group)"15:24
garyksenhuang: you should know what this one is about :)15:24
senhuanggaryk: yep. i know. :-) let's update the whole subteam.15:25
garykok, i'll let you do that15:25
senhuangon the instance group api extension, gary has submitted 30+ patches on the db support15:25
senhuanghttps://review.openstack.org/#/c/28880/15:26
*** jbjohnso has joined #openstack-meeting15:26
senhuangthe development of api support for this is on-going work15:26
*** haleyb has left #openstack-meeting15:26
senhuangi hope i can submit the initial patch today or tomorrow15:26
senhuanggaryk: do you need more help on the review?15:27
garyksenhuang: i think that we have ironed out all of the issues. we just need some core guys to take a look15:27
garykthe doc describing it all is https://docs.google.com/document/d/1QUThPfZh6EeOOz1Yhyvx-jFUYHQgvCw9yBAGDGc0y78/edit?usp=sharing15:27
senhuangblueprint: https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension15:27
*** danwent has quit IRC15:28
senhuangwiki: https://wiki.openstack.org/wiki/GroupApiExtension15:28
garyki am going to start the conductor api side soon so that the scheduler can make use of the info15:28
PhilDayI found it a bit hard from just the DB change to work out exactly what relationships will be supported15:28
*** markwash has joined #openstack-meeting15:28
PhilDayI thought there was a general move away from introducing features in small pieces - or has this been OK'd ?15:29
garykthe idea is that we will have an instance group.15:29
*** reed has joined #openstack-meeting15:29
senhuangbasically, a group-instance will contains a group of VM instances, with a list of policies that can be enforced by the scheduler15:29
*** maoy has joined #openstack-meeting15:29
PhilDayYeah I got the idea from the BP - what I'm saying is that it can be quite hard to meaningfully review just one part of the changes in isolation.15:30
garykPhilDay: agreed.15:30
*** briancline has quit IRC15:30
*** sandywalsh has quit IRC15:30
PhilDayHaving a DB model with no code to drive it makes it pretty hard to see if the DB code is OK or not15:30
garykhopefully when we have the API and the conductor side it will all fit in together15:30
senhuangyes.15:30
senhuangi am working on the API part15:31
gliksonyep, we might need some refactoring around db APIs once other parts are developed15:31
garyki do not think that this should prevent the pacth going through. it is very generic and covers all bases at the moment15:31
PhilDayWhy not make that all same commit then ?15:31
*** bdpayne has joined #openstack-meeting15:31
PhilDayJust saying that there has been push back on this kind of appraoch before15:31
PhilDay(But I like where teh BP is headed)15:32
garykto be honest i am not sure what the approach in nova is. in quantum this is acceptability. we can certainly build the patches on on top of another if that will provide a better picture15:32
garyki just think that adding one huge feature will take a tone of time.15:32
*** jcoufal has quit IRC15:32
PhilDayIts hard to get the right balance.15:33
*** stevemar has quit IRC15:33
gliksongaryk: in some cases we used dependencies between changes to have the bigger context but still review smaller pieces15:33
garykglikson: i am not sure how the db piece can be made smaller. it is very isolated15:34
senhuangthe DB part is quite stand-alone implementation15:34
*** markwash_ has joined #openstack-meeting15:35
PhilDayI haven't seen anyone from core comment on thsi yet - which is odd for something with 30+ iterations15:35
*** ijw has quit IRC15:35
gliksongaryk: I mean, to link with other pieces15:35
senhuangit also has enough meterials for review.15:35
PhilDayMayeb worth reaching out to Russell ?15:35
*** bdpayne has quit IRC15:35
*** markwash has quit IRC15:36
*** markwash_ is now known as markwash15:36
garykok, i'll try and be in touch with him15:36
gliksonsenhuang: correct, but in several other reviews it was stated that it is not a good practice to merge code that noone is using..15:36
PhilDayRight now its a great patch for adding a DB table - but that seems an odd chunk to do in isolation to me15:36
senhuang#action Reaching out to Russell about the code reviews for parts of a big feature15:36
*** cp16net is now known as cp16net|away15:36
russellbprobably need the rest before you'll get much review on the db part15:37
russellbi wouldn't want to see it go in until the feature to use it is ready to go right behind it15:37
*** cp16net|away is now known as cp16net15:37
*** cp16net is now known as cp16net|away15:38
senhuangrussellb: okay15:38
garykin the mean time i will add in the conductor side of things. this just seems like it is really prolonging the integration and adoption15:38
*** bdpayne has joined #openstack-meeting15:38
*** johnthetubaguy has quit IRC15:38
PhilDayintegration maybe - but you can't really adopt anything without the API and scheduler layer ?15:39
russellbright15:39
*** ociuhandu has quit IRC15:39
russellbbut my comment is just a general approach to review and acceptance of any feature15:39
russellbwe don't merge the code until the whole thing is ready (with few exceptions)15:40
senhuangit will be a long process since there are so many pieces for the whole thing15:40
gliksonPhilDay: well, I can think of usefulness of grouping even without having it supported in the scheduler -- but sure, the bulk of it will come with the scheduler support.15:40
PhilDayThe risk of partial features is that they tend to de-stablise trunk, esp if you have to rework parts as you add the upper leyaers15:40
*** jbjohnso has quit IRC15:40
garykat the moment the scheduler has a very patchy implementation of the grouping - using the isnatnce metadata. this will be formalized and easily updated here15:40
*** johnthetubaguy has joined #openstack-meeting15:41
gliksongaryk: right, ideally without changing the hint syntax15:41
*** hemna has quit IRC15:41
*** hemna has joined #openstack-meeting15:42
PhilDayglikson:  No objection to submtiing a complete (but smaller) subset of the grouping feature and then adding scheduler support - the important part is that it completly implements some feature15:42
garyki understand. i'll add the patches above this one and hopefully it will make a better picture.15:42
garykwe will also need nova client support15:43
*** Mr__T has joined #openstack-meeting15:44
gliksonmight make sense to add nova client support together with the api support15:44
*** s1rp has joined #openstack-meeting15:44
senhuanggaryk: i should be able to have the api part ready today. should i submit a new patch or on top of the patch you have?15:44
garyksenhuang: that would be great.15:45
garykPhilDay: russellb: is that acceptable?15:45
russellbsounds like it15:46
russellbneed novaclient support too though15:46
*** schwicht has joined #openstack-meeting15:46
*** sandywalsh has joined #openstack-meeting15:46
*** luis_ has joined #openstack-meeting15:46
garykwe'll take care of that15:46
senhuangokay. let's move on to another topic?15:47
senhuang#topic open-discussion15:47
*** openstack changes topic to "open-discussion (Meeting topic: scheduler sub-group)"15:47
*** jlucci has joined #openstack-meeting15:48
gliksonI have a question regarding multi-scheduler blueprint (definition of different scheduler drivers and/or policies for different host aggregates). One of the assumption that we need is that host aggregates that use this feature are disjoint. Does it sound like a reasonable assumption that admin will manage it? or do we need to introduce the notion of disjoint host aggregates in the code? it might be relevant for other features as well..15:50
*** schwicht has quit IRC15:50
*** schwicht has joined #openstack-meeting15:51
russellbwhy do they need to be disjoint?15:51
PhilDaySo would that be a property of an aggregate - i.e you can define an aggregate that it must be disjoint, and it will then reject hosts that are part of another aggregate ?15:51
PhilDayI think that woudl also be useful for AZs15:51
russellbrequest comes in with an AZ (host aggregate), and that would be your key to figure out which scheduling path to take, right?15:52
*** gokrokve has joined #openstack-meeting15:52
gliksonrussellb: otherwise it might create some inconsistencies, if the same host belongs to two aggregates each associated with different scheduler..15:52
*** luis_fdez has quit IRC15:52
*** cp16net|away is now known as cp16net15:52
russellba host may be in AZ 1 and AZ 2, but the *request* specified AZ 2, so you'd schedule based on that15:53
*** jbjohnso has joined #openstack-meeting15:53
*** jtomasek has quit IRC15:53
russellbthe scheduling path you take has to be entirely based on what is in the request15:53
gliksonI didn't think to use AZ hint for that -- just properties of the flavor, like we do with standard aggregate filter..15:53
PhilDayI was thinking that it woudl just be a useful safeguard in setting up AZs.  At the moment a host can be in more than one AZ (just beacause aggregates support it) - but I can't see a reason you would want to to that15:53
russellbthere are certainly use cases for overlapping aggregates15:54
russellbaggregate with special hardware thing 1, and aggregate with special hardware thing 2, and some hosts may have both15:54
gliksonPhilDay: agree, disjoint aggregates based on certain property might make sense regardless of this particular feature15:54
*** ociuhandu has joined #openstack-meeting15:54
PhilDaySo having an aggregate property that says "this aggregate must be disjoint from these aggregates" would be useful at that level to avoid mistakes15:54
*** rahmu has joined #openstack-meeting15:55
primeministerphi all15:55
primeministerpwhoops my clock seems to be off by 515:55
*** egallen has joined #openstack-meeting15:55
PhilDayAgreed that overlapping is a useful capability in some cases - I think disjoint would have to be relative to specific other aggregates15:56
gliksonit might make sense to be able to express something like: "this aggregate should be disjoint with all the aggregates of type AZ"15:56
PhilDaySo why does the multi scheduler need disjoint aggregates15:56
gliksonkind of grouping of aggregates..15:56
*** luis_ is now known as luis_fdez15:57
gliksonPhilDay: for consistency.. e.g., if we want to know which scheduler to use to migrate a given instance off a host, we would go to the scheduler associated with the "scheduling aggregate" that this host belongs to15:58
PhilDayFor use in the scheduler you'd need disjoint to not be linked just to aggregates of type AZ - maybe we also need an aggregate type then (I think AZ is a special case at the moment no) ?15:58
gliksonyep, exactly -- aggregate type sounds like a good approach. and for certain type we may require them to be disjoint (within that type).15:59
*** mriedem has joined #openstack-meeting15:59
senhuangokay. guys. the time is almost there.15:59
*** martines has quit IRC15:59
senhuanglet's continue the discussions next week15:59
*** martines has joined #openstack-meeting15:59
*** hanrahat has joined #openstack-meeting16:00
PhilDayworks for me.  See ya16:00
gliksonok. thanks, bye.16:00
senhuang#end-meeting16:00
jgallard_ok, thanks a lot, it was very interesting :)16:00
*** neelashah has quit IRC16:00
*** PhilDay has quit IRC16:00
primeministerp#endmeeting16:00
senhuang#end16:00
senhuang#endmeeting16:00
*** openstack changes topic to " (Meeting topic: state-management)"16:00
openstackMeeting ended Tue May 21 16:00:50 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler_sub_group/2013/scheduler_sub_group.2013-05-21-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler_sub_group/2013/scheduler_sub_group.2013-05-21-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler_sub_group/2013/scheduler_sub_group.2013-05-21-15.00.log.html16:00
primeministerp#startmeeting hyper-v16:01
openstackMeeting started Tue May 21 16:01:05 2013 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: hyper-v)"16:01
*** yoshiotu has quit IRC16:01
openstackThe meeting name has been set to 'hyper_v'16:01
primeministerpHi Everyone16:01
luis_fdezhi!16:01
gokrokvehi16:01
mriedemhi16:01
primeministerpwow16:01
pnavarrohello16:01
primeministerplots of new folk16:01
primeministerpgreat16:01
kirankvhi16:01
primeministerpociuhandu: where's alex?16:01
primeministerplet's wait a minute for those who are late16:02
primeministerpluis_fdez: thanks for the pull requests16:02
liuxpeihi, this is Xiao Pei from China16:03
primeministerpluis_fdez: we should talk about this more off line16:03
primeministerpliuxpei: hellow16:03
ociuhanduprimeministerp: entering now16:03
ociuhanduhi all16:03
primeministerpociuhandu: great16:03
luis_fdezprimeministerp, ok, I have some suggestions/ideas to discuss16:03
primeministerpluis_fdez: we need to coordinate16:03
*** alexpilotti has joined #openstack-meeting16:03
primeministerpluis_fdez: so you can understand what I already have done16:03
primeministerpluis_fdez: and what's not included in those bits yet16:03
alexpilottihi there!16:03
primeministerpalexpilotti: hi alex16:03
primeministerpfull house today16:04
pnavarrohi alexpilotti !16:04
luis_fdezprimeministerp, ok16:04
primeministerpok let's begin then16:04
alexpilottiliuxpei: hi, thanks for joining us!16:04
*** ijw has joined #openstack-meeting16:04
primeministerp#topic open issues16:04
*** openstack changes topic to "open issues (Meeting topic: hyper-v)"16:04
primeministerpso there have been some new bugs16:04
liuxpeithanks, I wil try to join as much as I can :)16:05
alexpilottiI can start on this one16:05
primeministerpalexpilotti: please16:05
alexpilottiThere's an annoying bug on snapshot management16:05
alexpilottirelated to the size of the image16:05
primeministerpliuxpei: thanks for your help with that one16:06
alexpilottiI attempted the easy way, consisting in trying to convince Glance that the size of the image is the virtual one, not th eVHD file size16:06
alexpilottibut that's a dead end16:06
pnavarroalexpilotti: please  link?16:07
alexpilottithe only other way to get this done is to consider the VHD file size16:07
alexpilottipnavarro: right away :-)16:07
liuxpeihttps://bugs.launchpad.net/nova/+bug/117792716:07
uvirtbotLaunchpad bug 1177927 in nova "VHD snapshot from Hyper-V driver is bigger than original instance" [Undecided,In progress]16:07
pnavarrothanks16:07
alexpilottitx liuxpei16:07
liuxpeiyw16:07
primeministerp#link https://bugs.launchpad.net/nova/+bug/117792716:07
alexpilottiso when we spawn an image, we could simply resize the VHD to instance['root_gb'] - vhd_header_size16:08
*** lloydde has joined #openstack-meeting16:08
alexpilottithis way we can guarantee that the file size will be alway less than the flavor size16:08
primeministerpalexpilotti: and I'm assuming this is currently the easiest way to overcome the size difference16:09
alexpilottiwe have to be consistent with this during resize as well16:09
alexpilottiyep. The shortest path after trying to trick Glance failed :-)16:09
primeministerpalexpilotti: does this make it easier to be consistant?16:09
*** jcoufal has joined #openstack-meeting16:09
alexpilottiwe have no choice16:09
primeministerpalexpilotti: ok then16:09
alexpilottiI mean, thin disks are working now16:10
primeministerpalexpilotti: then let's do it16:10
alexpilottibecause the file size limit is not capped16:10
liuxpeia question: for VHDs with different size, does vhd_header_size always the same?16:10
alexpilottinote: we have also to backport it to grizzly16:10
*** jgallard_ has quit IRC16:10
alexpilottiliuxpei: yep16:10
alexpilottiwe have to remember to check aslo the VHDX header size ;-)16:11
primeministerpalexpilotti: does it increase for vhdx?16:11
primeministerphehe16:11
alexpilottiit's a different value, but still fiuxed16:11
alexpilotti*fixed16:11
primeministerpbut different16:11
primeministerpi would assume it would increase16:11
alexpilottisince we are talking about a few KB16:11
primeministerpok16:11
alexpilottiwe can just add a fixed vlaue > max(vhd_header, vhdx_header)16:12
alexpilotti*value16:12
primeministerpi understood16:12
alexpilottiand solve this issue16:12
primeministerpthat works16:12
*** amotoki has quit IRC16:12
primeministerpI'm all for taking this approach,  I'm assuming the ammount of code is trivial16:12
alexpilottithe alternative would be to try to add a "tolerance" in manager.py16:12
alexpilottibut I have to convince the rest of the Nova world for that to happen ;-)16:13
primeministerpalexpilotti: we don't want to have to do that16:13
primeministerp;)16:13
alexpilottiI think we have enough w the rest there :-)16:13
primeministerpI agree16:13
alexpilottiok, comments on this issue or should we move on?16:13
primeministerpok are w/ good with this topic?16:13
alexpilottilol16:14
primeministerppnavarro: ?16:14
pnavarro+1 !16:14
liuxpeianother question: file size for a VHD is the actual size for it?16:14
*** anniec has quit IRC16:14
primeministerpliuxpei: right now?16:14
primeministerpliuxpei: I believe so16:15
alexpilottiliuxpei: can you please define "actual size"?16:15
liuxpeidisk size16:15
primeministerpI think she means what's currently being used as disk size16:15
alexpilottiyep file size = disk size16:15
*** senhuang has quit IRC16:15
primeministerpok16:15
primeministerp#topic H116:16
*** openstack changes topic to "H1 (Meeting topic: hyper-v)"16:16
liuxpei after adding a fixed vlaue > max(vhd_header, vhdx_header), then will the file size continue to be the disk size?16:16
alexpilottiyep16:16
alexpilottiand file size = disk size <= flavor size :-)16:16
liuxpeiok, I am ok with that now~16:17
*** garyk has quit IRC16:17
primeministerpgreat16:17
alexpilotticool16:17
primeministerpalexpilotti: H116:17
alexpilottiouch16:17
primeministerpalexpilotti: hehe16:17
primeministerpI thought you were going to say that16:17
alexpilottilet me fetch the link with the blueprints16:17
alexpilottilol16:17
primeministerpI know dust is still settling16:17
primeministerppnavarro: while he's mentioning blueprints16:18
alexpilotti#link https://blueprints.launchpad.net/nova?searchtext=hyper-v16:18
primeministerppnavarro: are there any specific to cinder we will require?16:18
alexpilottiso here' the list16:18
alexpilottiI aded "only" nova and ceilometer so far16:18
alexpilotticinder and quantum are missing (the latter for a good reason) :-)16:19
pnavarroprimeministerp: I'd add some one to complete the missing features that were added in G16:19
alexpilottipnavarro: great16:19
primeministerppnavarro: thank you16:19
primeministerpalexpilotti: yes understood16:19
pnavarrobut, I won't have time for H116:19
primeministerppnavarro: fair enough16:20
primeministerpH1 is close16:20
*** epim has joined #openstack-meeting16:20
*** mriedem has left #openstack-meeting16:20
alexpilottiH1 is just for waking up16:20
primeministerphahaha16:20
alexpilottiH2 is the real deal and H3 is for the last minute panic16:20
alexpilottiso there's plenty of time :-)16:21
primeministerpok16:21
primeministerpalexpilotti: do you want to update on the status of the clustering discussion16:21
alexpilottikidding, we'll have a lot of stuff in on H216:21
primeministerpwe missed that whole thing last week16:21
alexpilottiohh yeah, clustering16:21
primeministerpmaybe for the record16:21
alexpilottiyep16:21
primeministerp#topic clustering16:21
*** openstack changes topic to "clustering (Meeting topic: hyper-v)"16:21
*** kwss has joined #openstack-meeting16:21
*** jtomasek has joined #openstack-meeting16:21
alexpilottiI want to hear also IBM opinion here :-)16:22
primeministerpalexpilotti: I know they have one16:22
alexpilottiso the idea is that we got tons of requests for supporting Hyper-V host level clusters16:22
alexpilottiaka old school MSCS clusters with CSV storage etc16:22
schwichtprimeministerp: he he16:22
primeministerp**hyper-v cluster as compute node***16:22
gokrokveyes. this is a hot topic16:23
primeministerpschwicht: ahh you joined us16:23
*** Mr__T has left #openstack-meeting16:23
primeministerpschwicht: glad you made it frank16:23
schwichtsorry it took so long ...16:23
primeministerpnp16:23
alexpilottischwicht: nice to meet you16:23
primeministerpalexpilotti: please continue, we have proper ibm representation in the channel16:23
*** hanney has joined #openstack-meeting16:24
alexpilottiteh diea is that most Nova core guys are totally against clustering at the Nova level16:24
alexpilottitheyr main argument is that it simply doesn't belong to OpenStack16:24
alexpilottiit's not particularly easy from a technical standpoint, but feasible16:25
*** sushils has joined #openstack-meeting16:25
*** stevemar has joined #openstack-meeting16:25
alexpilottion the other side, support for vCenter and SCVMM might be on the roadmap16:25
liuxpeione thing I want is that for VM hA, to evacuate a vm from a failure hyper-v host to another16:25
alexpilottiby using cells16:25
gokrokveIf I am not mistaken Xen clusters were supported by OpenStack. At least I heard that it should work.16:25
alexpilottiliuxpei: that's our goal as well16:25
liuxpeiin Havana?16:26
alexpilottigokrokve: they are using a aspecific Nova feature for "grouping" the servers16:26
alexpilottigokrokve: but they still have a single scheduler on top (nova-scheduler)16:26
primeministerpalexpilotti: is that something we could take advantage of?16:27
alexpilottithe main issue in using any type of failvore clustering solution is that nova-scheduler will have a second scheduler in front16:27
alexpilottiwhich is understandable16:27
primeministerpalexpilotti: in this case the hyper-v cluster resource mgr16:27
alexpilottialternative would be to consider the cluster as single macro-host16:28
alexpilottileaving the actual host sceduling to the cluster16:28
alexpilottibut that doesn't work for a lot of reasons16:28
primeministerpalexpilotti: i can see how16:28
schwichtalexpilotti: can you name a few?16:28
primeministerpit doesn't16:29
primeministerpwell16:29
primeministerpyou need a single point16:29
primeministerpof entry16:29
primeministerpif it's handling hte host scheduling16:29
primeministerpwhich means16:29
primeministerpone node would have to be that16:29
alexpilottiissues:16:29
primeministerpbc it would make sence16:29
primeministerpto have a nova compute on each individual node16:30
alexpilottinova-scheduler would see a single host with e.g. 200GB memory free16:30
alexpilottiwhich asctually are separated in e.g. 20GB on 5 hosts16:30
schwichtok that does not work , I agree ...16:30
primeministerpexactly16:30
schwichtit makes sense to see how vmware solves that16:30
alexpilottiat this point it could try to boot a VM with 40GB, which is not working16:31
schwichtthey have a total capacity and the largest deployable capacity16:31
alexpilottistill, the largest deployable can be above the current limit16:31
primeministerpschwicht: they handle it by having it talk to the higher vsphere layer16:31
pnavarroguys, I have to leave, I'll read the logs later16:32
primeministerppnavarro: thanks again16:32
alexpilottipnavarro: bye!16:32
alexpilottibeside that, the stats would be very coarse, but that's a trivial issue16:32
*** garyk has joined #openstack-meeting16:33
alexpilottianother problem is related to manual failover16:33
alexpilottior live-migration16:33
primeministerpschwicht: make sense16:33
alexpilottibeing a single host from the nova perspective, there's no way to interact with each single host16:34
alexpilottiI proposed an alternbative, while waiting for the cell based approach to take shape16:34
*** jaybuff has joined #openstack-meeting16:34
alexpilottithere's no particular reason for being forced to use MSCS16:35
alexpilottias long as we can achieve proper HA16:35
gokrokveWhy not to expose all cluster components individually but provide a hint to the scheduler that it is a cluster?16:35
alexpilottithe idea is to add a heartbeat service on each compute host16:35
alexpilottigokrokve: they ditched that idea16:36
alexpilottigokrokve: it was proposed for baremetal initially16:36
primeministerpalso in theory you can reach the same result of vm avialability with out the complexity of a cluster underneith16:36
alexpilottianyway, to finish with the potential solution16:37
alexpilottiwe can provide agents for heartbeat16:37
schwichtalexpilotti: primeministerp: I think you need both .. a single point of entry for the scheuling and vm management and the enumerate cluster members to be able to set a node in maint mode16:37
*** neelashah has joined #openstack-meeting16:37
alexpilottiand provide failover on top of nova itself16:37
*** Mandell has joined #openstack-meeting16:37
alexpilottiNova has a feature called "evacuate"16:37
alexpilottiwe can use that to failover in case of missing heartbeat reports16:38
alexpilottiand handle the usual live-migration for manual failvovers as we already do16:38
alexpilottiIMO this would be a fairly simple approach, working with any hypervisor and available in a few days16:38
schwichtalexpilotti: you would miss MS system Center co-existance .. that you may get with Cell, or did I misunderstand that ?16:39
alexpilottithink about HALinux or similar solutions as a reference16:39
primeministerpschwicht: you would get that w/ a cell16:39
alexpilottischwicht: correct16:39
primeministerpok16:40
alexpilottischwicht: but for that we need to wait for cells to get to the stage to support it16:40
*** salv-orlando has joined #openstack-meeting16:40
alexpilottischwicht: and even with all of VMWare pressure on the subject, I doubt it will happen for Havana16:40
alexpilottiso to recap we have 3 choices:16:40
alexpilotti1) fork and do our cluster16:40
alexpilotti2) a clustering project on top of Nova16:41
* primeministerp doesn't support forks16:41
alexpilotti3) wait for cells16:41
alexpilottiprimeministerp: it was just for completeness ;-)16:41
primeministerpI'll throw a +1 for #316:41
primeministerpalexpilotti: i know16:41
alexpilottiany other votes or comments?16:42
schwichtI like # 3 best because it seems clean16:42
primeministerpok16:42
primeministerpgokrokve: ?16:42
gokrokveNumber 2 looks like more general approach and might work not only for Hyper-V16:43
gokrokveWhile 1 and 3 looks like workarounds16:43
russellbideally help and not just wait :-)16:43
primeministerprussellb: agreed16:44
alexpilottirussellb: hehe16:44
primeministerpschwicht: <cough>16:44
primeministerpok16:44
primeministerpmoving on16:44
alexpilottirussellb: do you think it's feaible to get it done for Havana?16:44
russellbdoesn't look like it, nobody is working on it yet16:45
primeministerpschwicht: <cough --^>16:45
alexpilottirussellb: that was my feeling as well ;-)16:45
russellbyep, just an idea so far16:45
schwichtprimeministerp: I heard the first one - gesundheit16:45
primeministerpschwicht: ;)16:45
alexpilottirussellb: do you know of anybody else interested in this?16:46
alexpilottirussellb: we could set up a cross-driver team, to say so :-)16:46
russellbplenty of interest in the idea ... nobody saying they want to help write it16:46
*** derekh has quit IRC16:46
russellbideally anyone interested in the affected systems ... so the VMware sub-team16:46
gokrokveWe are looking for clstering support in OpenStack.16:46
alexpilottirussellb: ok, beside us and VMWare, nobody else?16:47
alexpilottirussellb: just to know to who I should reach out16:47
russellbopenstack-dev list in general16:47
gokrokveMirantis will join development.16:47
russellbsome core nova folks that need to be involved in the architecture/design of it16:47
alexpilottigokrokve: cool!16:47
alexpilottirussellb: I guess I'm going to bug dansmith as usual then :-D16:48
russellbthose that seem most interested seem to be me, dansmith, and comstud16:48
*** lpabon has joined #openstack-meeting16:48
alexpilottirussellb: do you know the IRC nick of the VMWare-sub lead mantainer?16:48
russellbbut probably mostly from an advisory capacity16:48
dansmithhartsocks, IIRC16:49
russellbhartsocks: <---16:49
alexpilottidansmith: tx guys16:49
primeministerprussellb: thanks16:49
alexpilottimaybe his around and can join us16:49
primeministerpalexpilotti: so additional issues to address?16:50
alexpilottiI'd love to see if the VMWare guys are around as we have a pretty good group online to talk about this briefly16:50
alexpilottibut it doesn't seem so16:50
primeministerpalexpilotti: I would reach out via the list16:51
primeministerpalexpilotti: as a start16:51
alexpilotticool16:51
russellbping dan wendlant too16:51
kirankvVMware sub team meets tomorrow16:51
primeministerpkirankv: thdx16:51
primeministerper thx16:51
alexpilottikirankv: tx16:51
schwichtprimeministerp: a common approach is best for the openstack consumers (like us) as well16:51
alexpilottiprimeministerp: you wnated to introduce the vhdx subject? :-)16:51
primeministerpo16:51
primeministerpdid i?16:51
primeministerp#topic vhdx16:52
*** openstack changes topic to "vhdx (Meeting topic: hyper-v)"16:52
primeministerpalexpilotti: that work?16:52
* primeministerp might be missing something16:52
primeministerpalexpilotti: actually i've forgotten was there something specific to vhdx we needed to discuss?16:52
alexpilottiprimeministerp: it was just a follow up on your "thdx" typo :-)16:52
primeministerphaha16:53
primeministerpok16:53
alexpilottiwhich had a perfect timing16:53
kirankvVmware subteam meeting time is 1700 UTC16:53
alexpilottiwe are working on doing the V2 WMI api support16:53
alexpilottithat will unlock VHDX16:53
alexpilottiVHDX itself is a fairly easy feature16:53
primeministerpalexpilotti: H2 timeframe?16:53
alexpilottiprimeministerp: sure16:53
primeministerphehe16:53
alexpilottiancutaly most blueprints depend on V216:54
alexpilotti*actually16:54
alexpilottiwhich means that we won't have new features on V116:54
alexpilottiaka 2008 R216:54
alexpilottiI just wanted to make this clear16:54
alexpilottiand hear if somebody has different ideas about it16:55
primeministerpalexpilotti: I think we've been clear about that for some time16:55
*** dhellmann is now known as dhellmann-away16:55
alexpilotticool16:55
primeministerpalexpilotti: the platform is 201216:55
alexpilotticool16:55
alexpilottishould we move to the RDP console?16:55
primeministerp#topic RDP Console16:56
*** openstack changes topic to "RDP Console (Meeting topic: hyper-v)"16:56
alexpilottischwicht: are you guys planning to add graphical console support on top of Hyper-V?16:56
schwichtthis is important to us lets say16:57
alexpilottiok, I'm just interested to understand the extent of the interest16:57
primeministerpI would image it's important to anyone planning on using hyperv16:57
alexpilottithat was my point as well, until I met a lot of people who simpole didn't care :-)16:58
schwichtfor the product consuming we try to get it into the release, but need to see if the code is solid16:58
alexpilottianyway, from a technicalk standpont we are there16:58
*** bdpayne has quit IRC16:58
alexpilottibut it requires a bit of work to add a few simple nova changes16:59
luis_fdezalexpilotti, is it feasible for Havana?16:59
alexpilottithat will inpact of all Nova, not only the Hyper-V driver16:59
alexpilottiluis_fdez: technically for sure16:59
alexpilottiluis_fdez: all we need is a sigle rest API call16:59
alexpilottiluis_fdez: and rename any reference to VNC in Nova ;-)17:00
luis_fdezok17:00
alexpilottiunless we want to add a "get_rdp_console" method17:00
alexpilottiwhich would add on top of get_vnc_console and get_spice_console17:00
alexpilottithe interface is getting crowded and IMO needs some cleanup17:01
*** boris-42 has quit IRC17:01
schwichtalexpilotti: primeministerp: we will follow up off line on the topic, need to check the latest17:01
primeministerpschwicht: ok17:01
alexpilottischwicht: sure17:01
primeministerpguys we're out of time17:01
primeministerplet's end it and make note to pick up the rdp discussion next week17:01
alexpilottischwicht: tx, let me know if you'd like to schedule a meetinmg for that17:01
primeministerp#endmeeting17:01
*** openstack changes topic to " (Meeting topic: state-management)"17:02
openstackMeeting ended Tue May 21 17:01:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-05-21-16.01.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-05-21-16.01.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-05-21-16.01.log.html17:02
gokrokveIs there a method  to understand which interface (RDP, VNC, SPICE) is available?17:02
*** mrunge has joined #openstack-meeting17:02
alexpilottisee you guys!17:02
primeministerpluis_fdez: #openstack-hyper-v17:02
*** glikson has quit IRC17:03
hanrahatprimeministerp: joining our next call?17:03
*** gokrokve has quit IRC17:07
*** HenryG has quit IRC17:07
*** mdomsch has quit IRC17:10
*** SergeyLukjanov has quit IRC17:13
*** terry7 has joined #openstack-meeting17:15
*** kwss has quit IRC17:15
*** lbragstad has quit IRC17:17
*** HenryG has joined #openstack-meeting17:17
*** kirankv has quit IRC17:23
*** tomoe_ has quit IRC17:24
*** tomoe_ has joined #openstack-meeting17:26
*** liuxpei has quit IRC17:27
*** tomoe_ has quit IRC17:27
*** danwent has joined #openstack-meeting17:28
*** hanrahat has quit IRC17:30
*** alexheneveld has quit IRC17:32
*** mrunge has quit IRC17:35
*** gokrokve_ has joined #openstack-meeting17:35
*** bdpayne_ has joined #openstack-meeting17:36
*** SumitNaiksatam has quit IRC17:36
*** SergeyLukjanov has joined #openstack-meeting17:38
*** davidhadas has quit IRC17:39
*** davidhadas has joined #openstack-meeting17:39
*** jtomasek has quit IRC17:40
*** lbragstad has joined #openstack-meeting17:46
*** saurabhs has joined #openstack-meeting17:46
*** johnthetubaguy has quit IRC17:47
*** egallen has quit IRC17:50
*** markmcclain has quit IRC17:51
*** danwent has quit IRC17:54
*** bknudson has joined #openstack-meeting17:55
*** danwent has joined #openstack-meeting17:55
*** dhellmann-away is now known as dhellmann17:59
*** atiwari has joined #openstack-meeting18:00
ayoungKeystone!18:00
*** SumitNaiksatam has joined #openstack-meeting18:00
*** brich has joined #openstack-meeting18:00
stevemaro/18:01
bknudsonhi18:01
*** danwent has joined #openstack-meeting18:02
dolphmo/18:02
ayoungdolphm, want to get this party started?18:02
spzalaHi18:02
dolphmgyee: termie: o/18:02
dolphm#startmeeting keystone18:02
openstackMeeting started Tue May 21 18:02:43 2013 UTC.  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
ayoung#link https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting18:02
openstackThe meeting name has been set to 'keystone'18:02
gyee\018:02
*** harlowja has quit IRC18:02
*** harlowja has joined #openstack-meeting18:03
dolphm#topic Havana milestone 118:03
*** openstack changes topic to "Havana milestone 1 (Meeting topic: keystone)"18:03
dolphmJust a reminder that our first milestone is on May 3018:03
gyeepluggable token provider!18:03
ayoungSo only BP not impl is the loggin one18:03
dolphm#link https://wiki.openstack.org/wiki/Havana_Release_Schedule18:03
ayoung#link https://blueprints.launchpad.net/keystone/+spec/unified-logging-in-keystone18:03
ayoungAnd it is up for review18:03
dolphmthat's targetted at m1 ^18:03
dolphm#link https://launchpad.net/keystone/+milestone/havana-118:03
*** sushils has quit IRC18:04
dolphmand it's our last m1 blueprint18:04
ayoungbut it makes me sad, as it once again buries eventlet code deep in Keystone18:04
dolphmso we're certainly in good shape for conservative milestone goals18:04
dolphmayoung: from openstack common?18:04
ayoungdolphm, yeah  keystone/openstack/common/rpc/amqp.py uses weakref to store the context in a WeakLocal object. log.py also does this18:05
dolphmif there's any other blueprints that should be moved from m2 to m1 because they're VERY close to being ready, give me a heads up18:05
dolphm#topic No downtime database migrations18:05
*** openstack changes topic to "No downtime database migrations (Meeting topic: keystone)"18:05
dolphmi've had this on the agenda for a while, but we haven't had time for it :)18:05
*** haomaiwang has quit IRC18:05
dolphmthere was a summit session on the topic:18:06
dolphm#link http://openstacksummitapril2013.sched.org/event/8d559940a2a905c8221ccaec19e91f28#.UZu3byuDQ1918:06
dolphmand a subsequent discussion on the mailing list:18:06
lbragstadhey, missed first part but I just saw the unified logging stuff18:06
dolphm#link http://lists.openstack.org/pipermail/openstack-dev/2013-May/008340.html18:06
*** hanney has quit IRC18:06
dolphmi just wanted to make everyone aware (go participate in the mailing list discussion!) ^18:06
ayoungdolphm, problem is that Keystone  then needs to run with two different versions of the schema18:06
dolphmayoung: exactly18:06
dolphmthis isn't something we've ever tackled before in keystone18:07
ayoungdolphm, we've probably already broken it for Griz-Havana18:07
bknudsonI don't think we've got any migrations in H yet.18:07
dolphmif other projects go down this road, we'll certainly need to follow; if anyone wants to champion the effort, please follow the progress in other projects and comment on migrations reviews accordingly :)18:08
dolphmayoung: probably so; i see havana as a "let's try this out" cycle for keystone, at least18:08
ayoungdolphm, sounds good.  I would say, though, that from Keystone, it would probably be better if we had a fallback18:08
dolphmit will take a testing infrastructure that we don't have today to make sure it works18:08
ayoungsay, we can validate tokens, but no database updates allowed18:08
dolphmi assume someone is already working on that18:08
ayoungand then we can upgrade Keystone while in that mode18:08
ayoungIf we cached the token revocation lists, we could put the server into a mode to just return those and the certificates18:09
ayoungThen we can update Keystone, and, while new tokens can't be issues, existing ones will still work.18:10
dolphmayoung: all dependent on appropriate external testing though, and a stakeholder to champion it18:10
dolphm#topic open discussion18:10
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:10
dolphmshort agenda today!18:10
bknudsonI've finally got the changes in to hopefully fix eventlet/dnspython problem : https://review.openstack.org/#/c/29712/18:11
ayoungdolphm, Jamie is going to try to work with the Kent folks to get the lazy provisioning ready for review18:11
bknudsonand this other set of changes is to get unit tests working again: https://review.openstack.org/#/c/29670/18:11
dolphmayoung: cool, there's still some identity-api related discussions there first though18:12
*** Mandell has quit IRC18:12
dolphmthere's two discrete api features that are required first, one needs to apply across the entire api and will need to be implemented accordingly (it can't just affect /users)18:12
bknudsondid we decide which route we're going to take for LDAP domains?18:12
gyeewhat's the status on the read-only LDAP bp?18:13
gyeeanyone working on that?18:13
dolphmayoung: ^ ? it sounded like you were leaning towards merging my patch? can you provide an update?18:13
dolphmgyee: link?18:13
gyeedidn't brad created one?18:13
gyeeI wasn't sure18:13
ayoungdolphm, so, while I am leaning toward yours, I told spzala that he got once more chance to get his working.18:13
dolphmgyee: i don't see one18:13
ayoungthe more I think about it, the more I think multiple domains in one ldap is a mistake18:13
spzaladolphM: about the default domain patch, I am working on it ... as ayoung just mentioned18:14
ayoungbut I would hate to break it on the one person that decided to go that route18:14
gyeeayoung, LDAP is made for domains18:14
ayounggyee, right18:14
ayounggyee, and, I think that if we kept it that way, it makes the other code changes easier as well18:14
ayoungnamely, split identity into its composite parts18:14
spzaladolphm: the approach I am taking now is that, we can't really ignore domain_id so set domain_id to default when it's ignore case18:15
dolphmspzala: ayoung: consider merging mine, and then applying some of spzala's work on top of it? i think there's value in both18:15
dolphmspzala: ayoung: have about a week left for 2013.1.2 i think18:15
*** SumitNaiksatam has quit IRC18:15
ayoungdolphm, so if we merge yours, we will break domains in LDAP, right?18:15
ayoungI'm ok-ish with this, if you are.18:15
dolphmspzala: what do you mean "set domain_id" ? provide it to ldap? or provide it to the api?18:15
dolphmayoung: multi-domain support goes away, yes18:16
spzaladolphm: provide it to ldap18:16
ayoungdolphm, the backend will have to fill in the domain_id with the default if it is an attribute ignore18:16
spzalaso that domain_id is always there .... default or other18:16
dolphmspzala: if domain_id is ignored, then provide the default domain to ldap? that doesn't sound like it solves anything18:16
spzalaayoung: agree18:16
dolphmspzala: that's also the exact opposite behavior that i expect from the ignore_attribute lists18:17
spzaladolphm: we can't ignore the domain_id18:17
spzaladolphm: in a way it makes sense that18:17
ayoungdolphm, I think we can choose to merge your patch at any point.  So, if spzala doesn't get it working, yours gets approved by default18:17
dolphmspzala: define "ignore"?18:17
spzalawe always have a default domain18:17
dolphmspzala: my patch validates the domain_id, and then avoids providing it to the ldap server18:17
bknudsonI think we want it to work so that if domain_id is ignored then any objects returned by Keystone have domain_id set to the default domain.18:17
dolphmbknudson: +118:18
ayoungdolphm, but even if he does get it working, doesn't mean we have to take it...it just makes it a deliberate decision as opposed to a forced one18:18
dolphmand if domain_id is ignored, the ldap server should be treated as domain-agnostic18:18
*** Mandell has joined #openstack-meeting18:19
spzaladolphm: agree.. ignore is 'ignore' but since we have at least have a 'default' domain so was thinking to pass it to the server.18:20
ayoungdolphm, so, lets give him a day or two to get it working, and agree that a reviewed patch has to be accepted in time to meet the  2013.1.2 deadline18:20
ayoungotherwise, we go with you patch18:20
ayoungyour18:21
bknudsonspzala: pass the default domain ID to the LDAP server? what's the LDAP server going to do with it since there's no attribute for domain_id.18:21
spzalaayoung: thanks :) .. dolphm: hopefully i will update the patch today ..if it works out18:21
spzalabknudson: so by passing, to me, don't "stip off" the domain_id18:21
spzalaI see that, that's what we do with ignore18:22
bknudsonspzala: the LDAP entries have a domain_id attribute?18:22
ayoungbknudson, yes they do18:23
spzalabknudson: yes if I am not wrong18:23
ayoung#link https://github.com/openstack/keystone/blob/master/keystone/identity/backends/ldap/core.py#L38918:24
ayoungThere too https://github.com/openstack/keystone/blob/master/keystone/identity/backends/ldap/core.py#L84518:24
bknudsonayoung: that's the case when domain_id isn't ignored.18:24
bknudsonbut what about when domain_id is in the ATTRIBUTE_IGNORE list?18:25
ayoungdolphm, are you OK with this approach, or would you prefer that we just go with your patch?18:25
dolphm(wrong channel)18:25
dolphmayoung: spzala: for what it's worth, jcannava tested both patches as of about a week ago in a deployment against read-only AD; both worked fine18:25
dolphmayoung: i don't think you can just ignore either patch, both have value at this point for stable18:26
ayoungdolphm, um...but I am guesing he had an attribute that he could use for the domain_id18:26
dolphmwhat we want in havana can be a another conversation18:26
ayoungdolphm, what is it from your patch that would be pulled into spzala's?18:27
ayoungI am OK with saying "remove multi-domain" as there is a chance it will affect 0 users18:27
dolphmayoung: validation that a valid domain was specified by the api; including a valid domain_id in all relevant responses back to the api18:28
dolphmayoung: the way i see it, my patch fixes the read-only issue by removing multi-domain support; spzala's patch on top of that could restore multi-domain, and maybe they could be backported together18:29
*** SumitNaiksatam has joined #openstack-meeting18:29
*** SumitNaiksatam has left #openstack-meeting18:29
*** needscoffee is now known as morganfainberg18:30
ayoungdolphm, OK...that is a strategy.  spzala can you rework your patch such that it applies on top of dolphm's and then we only have to decide "dolph's only" or "both"18:30
ayoungdolphm, lets #action that18:30
spzalaayoung: sure, that's a good idea.18:30
dolphm#action spzala to rework patch such that it applies on top of dolphm's18:30
ayoungdolphm, we can accept your patch at any point, I think18:31
ayoungany reason to hold off?18:31
dolphmnot for master18:31
dolphmi don't think?18:31
ayoungactually, it might make sense to get it in soon18:31
ayoungthen , if anyone is tracking master, we find out if we broken them....18:31
ayoungtracking master and doing multi domain ldap18:31
dolphmwhich is definitely no one, but yes :)18:32
*** arunkant has joined #openstack-meeting18:32
ayoungbknudson, I +2ed.  Feel free to approve if you are comfortable with it18:32
ayoungdolphm, OK,  so..I thin that leads into split identity18:33
dolphmi think it does18:33
ayoungdolphm, I posted to the mailing list, and am getting positive feedback.  Are you OK with the general thrust of it?18:33
dolphmayoung: yeah; at the summit i was just worried the implementation was going to be very difficult, but it sounds like we're making lots of small rational steps in that direction18:34
ayoungLDAP and potentiall PAM can  "plug in" to fill a domain.  My guiess is that domains, and projects would mainly be handled by SQL18:34
ayoungso multi domain support across 2 or more LDAP servers should be do-able, and in a rational manner18:35
dolphmis the consensus that projects should be in not-ldap?18:35
ayoungdchadwick suggested that we further split project into projects and assignments18:35
dolphm(that's always made sense to me, but i'm not an ldap stakeholder)18:36
ayoungdolphm, I think that some people might keep them there for the short term18:36
ayoungbut I would say that most people would prefer to not have them in LDAP18:36
*** HenryG has quit IRC18:36
ayoungso for a given domain,  we could say that Identity is in LDAP, but proejcts and assignments are in sql or18:36
ayoungall three are in LDAP18:36
ayoungas they are today18:36
bknudsonIdentity is users and groups?18:37
ayoungbknudson, yes18:37
ayoungprojects is Projects  and roles18:37
*** rahmu has quit IRC18:37
bknudsonthat sure maps to ldap18:37
ayoungassignments is the mapping between them18:37
*** glikson has joined #openstack-meeting18:37
bknudsonassignments is which users are in which groups?18:38
ayoungbknudson, no18:38
bknudsonbecause ldap groups are lists of users (by DN)18:38
ayoungbknudson, more like which users and/or groups are assigned to which roles18:38
brichayoung: Does "split" imply APIs, services and configuration needed for said split?18:39
bknudsonok18:39
ayoungbrich, web API stays the same18:39
ayoungbrich, only the backend splits18:39
ayoungthere might be some ugliness with the unique identifiers, but I think the current scheme can handle it, so there should be no change from a client perspective18:40
brichayoung: but under the official API, we could have remotable services? My impression is that is where Chadwick's thought would go18:40
ayoungbrich, that would be a step beyond this.18:40
ayoungbut this work is necessary to implement his, I think18:41
brichayoung: agree.  just wondered how far you were thinking to go in Havana18:41
ayoungdolphm, ok to #action that I update the BP to reflect this?  Are we agreed this is the right general direction?18:42
bknudsonayoung: Looking at dolphm's patch https://review.openstack.org/#/c/28197/10/keystone/identity/backends/ldap/core.py , removes the DomainApi from LDAP... so spzala's is just going to re-add it back in?18:42
*** novas0x2a|laptop has joined #openstack-meeting18:43
*** otherwiseguy has quit IRC18:43
ayoungbknudson, if it is approved, yes,18:43
spzalabknudson: I guess so, i think we need that for multi-domain support18:43
ayoungspzala, how important is it to your group?18:44
dolphmayoung: which bp?18:44
spzalaayoung: multi domain support?18:44
ayoungdolphm, first off, split identity, but also the domain subbp18:44
dolphmayoung: this all sounds like multiple blueprints, btw18:44
ayoung#link https://blueprints.launchpad.net/keystone/+spec/split-identity18:44
spzalaayoung: read only domain is more important as far as I know18:44
ayoung#link https://blueprints.launchpad.net/keystone/+spec/extract-projects-from-id18:45
dolphmayoung: there's seperate blueprints to split credentials and domains18:45
dolphm(i seriously can't spell separate correctly from muscle memory)18:45
gyee:)18:45
ayoung#link https://blueprints.launchpad.net/keystone/+spec/auth-domain-architecture18:45
ayoungdolphm, neither can I18:45
gyeeI don't speak english so I generally get a pass on spelling18:46
*** maoy has quit IRC18:47
ayoungOK, one last thing...the whole index/token revocation mess18:47
ayoungtermie's point is that the serving of the revocation list should not require iterating over a list....18:47
dolphmspzala: marked this as obsolete; let me know if that's innaccurate https://blueprints.launchpad.net/keystone/+spec/ldap-fake-domain18:47
ayoungso he's blocked two patches which fix bugs.  One is a fix to the token backendm, and the other indexes the sql backend18:48
*** dwaite has joined #openstack-meeting18:48
spzaladolphm: it goes with the current patch on static domain18:48
ayoungI think he has a point...so...18:48
bknudsonhow are we going to generate a list without iterating over a list?18:49
ayoungwhat if we held the revocation list in memcached, lazy constructed, and return it as a single document?  When a revocation event comes in, we rebuild it.18:49
bknudsonmaybe the problem is too many tokens18:49
morganfainbergayoung: that isn't a bad idea.18:50
bknudsonthe servers are constantly requesting the revocation list, so lazy constructing doesn't make any difference18:50
*** bdpayne_ has quit IRC18:50
ayoungbknudson, nah, that would only happen once18:50
ayoungat start up time18:50
morganfainbergbknudson: the revocation events are infrequent enough that it shouldn't be too bad…unless revoke_tokens_for group / user is called with enough tokens to exceed a memcache page (the proposed fix doesn't handle that in either case)18:50
ayoungmorganfainberg, exactly18:51
bknudsonrevocation events are infrequent, but the other servers are constantly asking for it.18:51
gyeeayoung, we do delta revocation list or one big list?18:51
ayounggyee, one big18:51
morganfainberggyee:  currently one big list18:51
gyeedoh!18:51
bknudsongyee: but they do eventually timeout18:51
bknudsonwhen the token expires, don't need it in the list anymore18:51
gyeewait, timeout and revocation are two different thing right?18:52
ayounggyee, right18:52
morganfainbergit does a memcache append() vs building it when a revocation occurs. but the current mechanism for evicting expired tokens from the list (vs. active that are revoked) is to wait for the page to expire…which it might not18:52
gyeeso in theory, revocation list should be smaller18:52
bknudsonrevocation is when you change roles and your old tokens go away18:52
sorenIs Keystone doing cryptographically signed tokens these days?18:52
bknudsonexisting tokens are now invalid18:52
*** timello has quit IRC18:52
ayounggyee, a revoked token that has expired token no longer needs to be reported as revoked18:52
ayoungsoren, yes18:53
gyeeayoung, right18:53
dolphmsoren: yes, by default in havana18:53
sorenCool.18:53
bknudsonsoren: it's the PKI tokens. There's also UUID tokens.18:53
dolphmsoren: err, grizzly18:53
sorenOh. Sorry. /me realises this is a meeting and not just #openstack-dev or whatnot18:53
sorenCarry on :)18:53
ayoungsoren, signed, but not encrypted18:53
*** otherwiseguy has joined #openstack-meeting18:53
ayoungmorganfainberg, OK, I'll writ that up.  Are you up for implementing it?18:54
morganfainbergsure18:54
morganfainbergit wont be hard to do.18:54
bknudsonis this only for the memcache backend for tokens?18:54
ayoung#action ayoung writes up revocation list out of memcache18:54
morganfainbergbknudson: for now, since it is most directly affected.18:55
ayoung#action morganfainberg implements memcached revocation list18:55
morganfainbergSQL is more efficient at telling revoked vs. expired18:55
bknudsonare we splitting up the token backend?18:55
ayoungbknudson, looks like it18:55
bknudsonthe sql today is not efficient18:55
gyeeayoung, bknudson, not sure if I understand termie's commend on the review18:55
morganfainbergi can work on SQL as well.18:55
ayoungbknudson, it will be a cache18:55
gyeeso he wants a clock impl?18:55
ayounggyee, clock is not going to happen, as elegant as it is18:55
ayoungwe would need a clock per user/project18:56
morganfainberggyee: the clock impl is good, just the problem is it changes the business rules in a way that would be bad.18:56
morganfainbergsince revoking all tokens for a user on an event is bad18:56
morganfainberg(short of a password change)18:56
morganfainbergso, elegant, but needs more than the simple concept.18:56
gyeeyeah, seem like a small bang for big buck18:56
morganfainbergayoung: i'll take a gander at the SQL implementation as well and see if I can come up with something while I'm mucking around in the memcache driver here.18:57
gyeeyou think that bad, wait till henry's inherit role impl :)18:57
bknudsonwe already have a couple of things for the sql backend18:58
morganfainbergbknudson: ah, ok, so i shouldn't worry about the revocation stuff in it?18:58
bknudsonthe most obvious one is to add the index to expires and revoked18:58
morganfainberg(sorry realized the meeting was going on and hopped over to this window a little late)18:59
ayoung#link https://blueprints.launchpad.net/keystone/+spec/cache-token-revocations18:59
dolphmtime to switch to -dev18:59
*** glikson has quit IRC18:59
dolphm#endmeeting18:59
*** openstack changes topic to " (Meeting topic: state-management)"18:59
openstackMeeting ended Tue May 21 18:59:16 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-05-21-18.02.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-05-21-18.02.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-05-21-18.02.log.html18:59
*** garyk has quit IRC18:59
*** dwaite has left #openstack-meeting18:59
*** brich has left #openstack-meeting18:59
*** glikson has joined #openstack-meeting19:00
jeblairci/infra?19:00
fungiinfra team assemble!19:00
annegentleform of:legos!19:00
* fungi appreciates annegentle's wonder twins reference19:01
annegentlethough I think I'm off by a factor of assembly... more like water or fire or plastic I suppose.19:01
jeblair#startmeeting infra19:02
openstackMeeting started Tue May 21 19:02:04 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
reedyou're all revealing your age with silly references to sillier cartoons19:02
fungireed: yes, i'll be 6 years old for the rest of my life probably19:02
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:03
jeblairagenda ^19:03
jeblair#topic actions from last meeting19:03
*** openstack changes topic to "actions from last meeting (Meeting topic: infra)"19:03
jeblairthere are no actions from last meeting19:03
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-05-14-19.02.html19:03
jeblairfungi: is there anything to talk about re jenkins slave os?19:04
fungijeblair: should probably talk about taking it off the agenda so you don't ask again next week ;)19:04
*** ijw has quit IRC19:04
fungii'll take care of that19:04
jeblairfungi: done19:04
jeblair#topic testr in project progress19:04
jeblairclarkb: ?19:04
*** openstack changes topic to "testr in project progress (Meeting topic: infra)"19:04
reedI vote to abolish passwords from websites, there has to be a better way to authenticate19:05
*** atiwari has quit IRC19:05
clarkbhi19:05
clarkbceilometer has been testr'd according to lp19:05
clarkbjgriffith plans to try and get cinder testr'd during H-219:05
*** bknudson has left #openstack-meeting19:07
clarkbstill need to convince the keystone folks that this is worth doing. I think swift will be on board if I poke them.19:07
clarkbglance is going to be the fun one because their test suite is interesting19:07
clarkbthings are moving, just slowly19:07
jeblairis there a particular strong objection from keystone, or just no one willing to pitch in?19:08
*** mrunge has joined #openstack-meeting19:08
*** timello has joined #openstack-meeting19:09
*** danwent has quit IRC19:09
clarkbit seemed to more a matter of motivating effort and not a technical objection19:09
dolphmfor testr support? no objections here19:09
clarkbyeah it was called busy work at one point. But I don't think anyone is against testr itself19:09
*** jrodom has joined #openstack-meeting19:10
dolphmkeystoneclient is already done19:10
jeblairokay, we'll just need to promise everlasting fame and glory to whoever does keystone19:11
*** radez is now known as radez_g0n319:12
zaroo/19:12
jeblairi think the bug calendar agenda item is stale, so i'm converting it to a reminder:19:12
*** boris-42 has joined #openstack-meeting19:12
jeblairNext bug day: June 4, 2013 at 1700UTC19:12
*** radez_g0n3 is now known as radez19:12
jeblair#topic Publishing of old documentation now that diablo and essex are EOL.19:12
*** openstack changes topic to "Publishing of old documentation now that diablo and essex are EOL. (Meeting topic: infra)"19:12
jeblair#link https://bugs.launchpad.net/openstack-ci/+bug/97272419:12
uvirtbotLaunchpad bug 972724 in openstack-ci "Dev docs sites for past releases of nova (2011.1) now 404 error" [Medium,Triaged]19:12
jeblairi think we needed input from annegentle on that19:12
annegentlethere's one for swift too19:13
jeblairclarkb: do you want to speak?19:13
annegentle#link https://bugs.launchpad.net/openstack-manuals/+bug/102509919:13
uvirtbotLaunchpad bug 1025099 in openstack-org "Redirects needed for swift 1.4.3, 1.4.4, 1.4.5, etc doc builds" [Undecided,Confirmed]19:13
annegentleI marked it won't fix19:14
clarkboh yes19:14
clarkbannegentle: so you are happy letting those die on the vine?19:14
clarkbannegentle: anything folsom or greater will have the correct files in place. its just a matter of linking to them where you want19:15
annegentleclarkb: that sounds like a great idea19:15
annegentleclarkb: so there's still a task to link to the "correct" versions?19:15
annegentleclarkb: but it's folsom and up19:15
clarkbannegentle: that depends. We are copying them to specific places19:15
clarkbannegentle: it will be under the project/tag_name dir for that project19:16
annegentleclarkb: oh, ok19:16
clarkbannegentle: I don't think we are currently automagically editing links within the aggregator sections of the docs19:16
annegentleclarkb: that sounds like a marvelous solution, is it just a matter of assigning someone to edit?19:16
annegentleclarkb: automagic is even better19:16
clarkbMy worry with automagic is I am not sure how friendly docbook will be to that19:17
clarkbyes, if you want to link to things today you can just do so by hand19:17
annegentleclarkb: these aren't docbook, theyre sphinx sites19:17
clarkbhttp://docs.openstack.org/developer/python-novaclient/2.9.0/ for example19:18
*** jrodom has quit IRC19:18
clarkband http://docs.openstack.org/developer/nova/2013.1/19:18
annegentleclarkb: but tell me why it matters?19:18
clarkbannegentle: because making a thing to automagically add links when nova et al tag a release is something new that would need to be written19:19
clarkbwe don't currently have anything like that today19:19
clarkband it would probably propose a change rather than merge it automatically so the human element remains19:19
*** mdomsch has joined #openstack-meeting19:20
jeblairclarkb: where would you add links?19:20
*** glikson has quit IRC19:20
annegentlejeblair: the links existed in the sidebars of the nova and swift sphinx sites19:20
annegentlejeblair: with the new templating for nova for example, the links aren't there19:21
clarkboh I was thinking the links would be at http://docs.openstack.org/developer/ or similar19:21
annegentleclarkb: we manually maintain http://docs.openstack.org/developer/openstack-projects.html19:21
*** markmcclain has joined #openstack-meeting19:22
annegentlefor example, jeblair, cinder uses the "old" template at http://docs.openstack.org/developer/cinder/19:22
clarkbannegentle: the problem with putting links internal to nova itself is that if you compile those sphinx docs without having the old stuff you will get broken links19:22
*** alexpilotti has quit IRC19:22
annegentleclarkb: yeah I'm fine with removing the links then19:23
*** hub_cap has joined #openstack-meeting19:24
clarkbannegentle: does that mean we need to go and clean some of the sphinx docs up? is that something the doc team would do?19:24
annegentleclarkb: honestly we don't have the time/resources for sphinx docs19:24
annegentleclarkb: I see a new doc bug for cinder to not link to "versioned" sites that are broken19:24
annegentleclarkb: so I guess just log bugs?19:25
clarkbin that case probably best file bugs against the projects themselves19:25
annegentleclarkb: and indicate the tagging mechanism?19:25
clarkbannegentle: yup19:25
annegentleclarkb: makes sense to me19:25
dprinceclarkb: log question for you. What is the best way to handle the logs for this jenkins job: https://review.openstack.org/#/c/29978/19:25
jeblairdprince: this is the meeting channel.  :)19:26
dprincejeblair: thanks!19:26
jeblairclarkb: any other questions about old docs?19:27
clarkbjeblair: nope I think that covers it19:27
jeblairclarkb: clouddocs-maven-plugin internalization?  do we need to talk about that, or is that now an off-line task?19:27
clarkbjeblair: I think that is now an offline task19:28
annegentlejeblair: I really really really want forward motion on that though.19:28
annegentlewhere's it at? Waiting on dwcramer?19:28
clarkbannegentle: I started looking at it last week. zaro and I discussed the jenkins jobs19:28
jeblairannegentle: i agree, i only meant "is clarkb working on that".  :)19:28
annegentleah ok19:28
clarkbannegentle: the biggest thing right now is having working jenkins jobs to do releases to maven19:28
clarkbonce we have that we can do the switch without impacting your release process19:29
annegentleoh ok I wasn't sure what the next steps were after the summit, I'm behind :)19:29
*** alexpilotti has joined #openstack-meeting19:29
annegentleclarkb: NICE in all caps for sure then.19:29
zaroi entered bug on that: https://bugs.launchpad.net/openstack-ci/+bug/118215419:29
uvirtbotLaunchpad bug 1182154 in openstack-ci "Automatic deploy to jenkins-ci.org repository" [Undecided,New]19:29
jeblairlets rearrange the agendo to continue talking about annegentle's topics:19:30
jeblair#topic  OpenStack Operations Guide - tooling, licensing, publishing discussion19:30
*** openstack changes topic to "OpenStack Operations Guide - tooling, licensing, publishing discussion (Meeting topic: infra)"19:30
*** gyee has quit IRC19:30
annegentleok thanks jeblair19:30
annegentledo you want an overview?19:30
jeblairannegentle: would love one19:30
*** luis_fdez has quit IRC19:30
annegentleok, here goes19:30
dwcramerI'll sync up with  you guys on the clouddocs-maven-plugin soon.19:30
clarkbdwcramer: awesome19:30
dwcramerI learned a bit more about how Maven works.19:30
dwcramerThat I didn't know at the summit.19:31
annegentleAt the Summit, I got to talk to O'Reilly community manager and a strategic accounts manager.19:31
annegentleThey mentioned that they've had difficulty getting an author to finish an OpenStack book19:31
annegentleI had heard this previously from an O'Reilly editor.19:31
annegentleSince we have a "completed" book more or less, they wanted to know if the Foundation wanted pro-editing on it and more publishing channels and epub-ish outputs.19:32
annegentleCurrently we have non-pro editing, a Lulu publishing channel, and no epub-like output that is automated.19:32
*** jhenner has quit IRC19:33
annegentleso we started the conversation and asked for a few meetings and a proposal for a contract with O'Reilly between them and the Foundation19:33
*** dolphm has quit IRC19:33
*** IlyaE has quit IRC19:34
annegentlethe O'Reilly workflow involves a tool called Atlas. Authors collaborate in a github repo using docbook or asciidoc with a web front editor, O'Reilly editors interact with the content and authors online.19:34
annegentleO'Reilly uses Github to gather public feedback about Atlas19:34
annegentle#link https://github.com/MakerPress/atlas-public-feedback/issues?labels=&page=3&state=open19:34
annegentlebut as far as I can tell, Atlas is not open sourced19:35
annegentlesince it's git backed, my (likely mistaken) hope was that we could use the same repo to publish through our current Gerrit/Jenkins process and to O'Reilly's channels.19:35
annegentlehowever we're very early in the days of exploration and learning19:36
annegentlethe latest today is that Mark Collier at the Foundation has a copy of O'Reillys proposal and is reviewing it19:36
annegentleI'm not sure it's quite what we had in mind but we're going to discuss.19:36
annegentlewhew.19:36
*** nachi_ has quit IRC19:37
annegentleI'd like to connect team CI to O'Reilly technical contacts.19:37
annegentleSince I have questions from one perspective, but you're going to have questions from another.19:37
*** harlowja has quit IRC19:37
jeblairannegentle: that sounds like a great idea.  i'd be happy to talk to them19:37
jeblairannegentle: i'm really curious about the contract with the foundation...19:38
annegentleThe other part is that the authors have to agree to do this, so far all six of them are onboard, for finding out more details.19:38
annegentleAll of this is not a done deal at all. I know you all know this but emphasizing for anyone reading the logs.19:38
jeblaira contract around marketing, trademarks, etc makes sense19:38
*** markmcclain has quit IRC19:38
jeblairif the contract involves tooling, that seems weird.  and i don't see how there could/should be a need for a contract regarding rights to the content itself19:39
annegentleAnother consideration is translation for this particular book.19:39
jeblairsince it's CC-by licensed19:39
annegentlewe have a Chinese and Japanese version already19:39
annegentlejeblair: yeah the contract I saw today isn't what I expected in terms of keeping CC-By.19:39
annegentlejeblair: so we have a ways to go19:39
annegentlejeblair: does it make sense to loop you in to the contract info with Mark Collier?19:40
*** harlowja has joined #openstack-meeting19:40
jeblairso with the caveat that we're sill exploring and learning about this, i'll just say some general thoughts based on what i've heard so far19:40
annegentlejeblair: or not yet? I don't want to waste your time either.19:40
annegentlejeblair: sure, want to hear more thoughts19:40
jeblairi don't know anything at all about their tool and how it works, which is about as far from open as you can get19:41
* mordred also wants to talk with them19:41
jeblairand open is one of our core community values19:41
* mordred is lurking over phone tethering waiting for plane to take off19:41
jeblairi understand that the git workflow isn't always great for documentors, but i'm really concerned about whether their tool is a right fit for our project19:42
annegentlemordred: thanks for that19:43
jeblairthen there's the technical issue, about whether it would work with anything else we're doing at all.19:43
*** ayurchen has quit IRC19:44
annegentlejeblair: so for the use case of accessing an established publishing brand, I don't know how you'd accomplish that with a completely open source tool19:44
mordredannegentle: I reject that premise19:44
jeblairannegentle: i don't know what that means.  :(19:44
annegentlejeblair: it's like the training/certification tooling, will we be able to have all-open for that?19:44
mordredannegentle: yes19:44
annegentlemordred: fair 'nough :)19:44
mordredannegentle: o'reilly has made MILLIONS on open source19:44
* ttx waves19:44
annegentlehey ttx19:45
mordredI believe it's not too much to ask for tools to interact with them to be open19:45
mordredor else I'm going to have to call Tim out as a hypocrite19:45
annegentlemordred: I certainly have made that request. I'm just saying, what if it's not possible.19:45
mordredif it's not possible, then I think we'll need to have a very deep though about what's important to us19:45
mordredbecause if all we want is world domination and we don't also want openness19:45
mordredthat's one path forward19:45
annegentlewe use open source fonts, we are open source as far as we can for the use case of publishing documentation. For publishing books, do you need to have Lulu's source for their ecommerce site?19:45
*** ayurchen has joined #openstack-meeting19:46
annegentleis it possible that certain use cases don't lend themselves to all-open, that's all I'm asking here.19:46
mordredI'm not passing judgement on any specific case19:46
mordredI'm saying that so far al of our tools are open19:46
mordredand it's an important community value19:46
jeblairannegentle: i don't think the contribution workflow for our documentation should be proprietary19:46
mordredso if we're going to undercut that, I want us to fully understand the ramifications of that19:47
mordredand I _personally_ do not believe there is any valid reason why we should need a non-free tool19:47
jeblairannegentle: i think anyone should be free to publish our documentation using whatever systems they want.  but i don't think we should start embracing propretary access to contributing.19:47
mordred++19:47
clarkb++19:47
annegentlejeblair: ah, okay, that helps me understand19:47
fungiwell said19:48
annegentlejeblair: I don't really want to stop contributors from using our current workflow either.19:48
*** litong has quit IRC19:48
*** SergeyLukjanov has quit IRC19:48
mordredright.19:48
jeblairannegentle: yeah, i like to think that being able to contribute to docs in the same way as the rest of the project is a worthwhile system.19:48
mordredwhich means that we'll need to have some deep conversations with oreilly about things19:49
mordredbecause our workflow is likely different than what they're planning for19:49
annegentleso to me, when I look at it, I get git-backing. But yesterday you pointed out that OpenStack source is not technically housed on github.19:49
mordredif their system is _a_ way to get at things, then I'm less opposed to it19:49
mordredannegentle: that is correct19:49
annegentleSo I saw Atlas as a second view into the source.19:49
mordredif it is a second view, I will have many less objections19:49
mordredhowever, oreilly is going to have to grok how our system works19:50
mordredbecause so far most of the 3rd party folks who have tried ot "integrate" with us19:50
mordreddon't seem to understand that we don't use github19:50
annegentlemordred: ok, good -- I think we have the same core value, but I had a bit of a bridge to build from github to openstack that I didn't have conceptually yet.19:50
mordredyah19:50
mordredit's definitely a conceptual bridge19:50
fungiannegentle: if it just consumes our git history and displays it, that's one thing... but if they have editors working on t we'll want a feedback loop of some kind19:50
clarkbyeah this is similar to the transifex issue19:50
mordredright. which means figuring out how that interacts with a review pipeline19:50
annegentleI think I have it conceptually now, but we still need a technical bridge. Are you all willing to explore the technical framework a bit? I can really use the help.19:50
mordredabsolutely19:51
jeblairyep19:51
clarkbwe are basically forcing everything to be unidirectional for sanity19:51
mordredalthough - it would be easier for us to have that discussion with them if their tool wasn't proprietary junk :)19:51
annegentleclarkb: ooo that's a good one too, Transifex as a second source.19:51
*** bdpayne has joined #openstack-meeting19:51
*** pnavarro has quit IRC19:51
*** dprince has quit IRC19:51
annegentlemordred: I honestly didn't get the vibe that it would never be open source, more like "we're a tad bit disorganized to actually show everyone the source"19:52
jeblairannegentle: maybe we can help motivate them.  :)19:52
clarkbannegentle: not anymore. transifex is now the only source19:52
fungiif they wait until it19:52
clarkbif you consider automagic process19:52
annegentleOk, so I think the agreement is to connect the ci team to O'Reilly technical contact(s) (I'm pretty sure I have at least one). How should I do that? Email?19:52
*** adalbas has quit IRC19:52
clarkbyou can still propose a fix to things by hand19:52
fungiif they wait until it's bug-free to release, they'll be the only bug-free open source project in history i think19:53
mordredannegentle: email is probably a great intro - I'm guessing it'll take a phone call too, since there is a LOT of ground to cover19:53
jeblairannegentle: my guess is email to set up a phone call19:53
*** seanrob has joined #openstack-meeting19:53
annegentlejeblair: yeah ok19:53
mordredI'd be happy to provide a conference bridge for that purpose19:53
annegentlemordred: ok I have one too.19:53
mordredawesome19:53
annegentleOk, thanks for exploring... the crazy world of dead trees and ISBNs.19:53
annegentlesorry to take up so much tim19:54
annegentletime19:54
jeblairannegentle: thanks for chatting with us here about this; i think it's important19:54
mordred++19:54
jeblairthere's a few minutes left to talk about remote participation....19:54
jeblair#topic What can infra do to enable remote participation at the next Design Summit?19:54
*** openstack changes topic to "What can infra do to enable remote participation at the next Design Summit? (Meeting topic: infra)"19:54
jeblairreed: around?19:54
fungii have academic/technology librarian friends who are big into free/open publication. i can solicit some suggestions there too19:54
annegentlefungi: cool19:54
jeblair#topic open discussion19:56
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:56
*** ayoung has quit IRC19:56
annegentleI could swear I had something for open discussion but it has slipped my mind.19:57
*** epim has quit IRC19:57
annegentleAhwell.19:57
mordredjeblair: just was chatting with zul about pymox19:57
mordredjeblair: apparently there is a python3 compat fork of it19:57
mordredjeblair: but the upstream will not take the patch19:57
mordredsigh19:57
jeblair(!)19:57
*** seanrob has quit IRC19:57
mordredthis brought up the idea of making a pymox3 fork, hosting it ourselves and publishing to pypi ourselves19:57
jeblairmordred: fork all the things19:57
mordredyeah19:58
mordredI mean19:58
mordrednot my first choice, but also, jeez19:58
mordredso, zul was going to look at adding it as a stackforge project, but I was thinking it might should be an openstack-dev/pymox3 instead?19:58
clarkbmordred: any response from holger?19:58
mordredthoughts?19:58
jeblairannegentle: did you want volunteers to convert all the manuals to TeX?19:58
fungiperhaps this python 3 support craze is just a passing fad?19:58
annegentlejeblair: LOL19:58
mordredclarkb: yes. he and I are going to have a phone call the next couple of days19:58
clarkbmordred: ! yay19:59
*** markmc has joined #openstack-meeting19:59
mordredzul is putting in a lot of effort to python3-ify our stuff, and I'd like to be supportive of that19:59
jeblairmordred: openstack-dev seems right19:59
clarkbmordred: I am more than happy to be the hg guinea pig if that helps19:59
mordredjeblair: kk19:59
mordredclarkb: I will get confirmation from him on acceptability of the idea, and then point you at it if he says ok19:59
fungii am honestly thrilled to see more attention paid to python 3 support19:59
mordredzul: ^^ openstack-dev/pymox319:59
jeblairand on that bombshell20:00
jeblair#endmeeting20:00
*** openstack changes topic to " (Meeting topic: state-management)"20:00
openstackMeeting ended Tue May 21 20:00:08 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-05-21-19.02.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-05-21-19.02.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-05-21-19.02.log.html20:00
jeblairugh we have to reset the channel topics sometime20:00
jeblairthey got messed up in the netsplit20:00
ttxo/20:00
markmcyo20:00
clarkbjeblair: I think you can through the meetbot admin interface20:00
ttxrussellb, shardy, jd__, dolphm, annegentle, mikal, mordred, notmyname, markwash, jgriffith, vishy, gabrielhurley, markmcclain: around ?20:00
shardyo/20:00
*** dolphm has joined #openstack-meeting20:00
dolphmo/20:00
jd__o/20:00
russellbo/20:00
notmynamehere20:00
markwasho/20:00
mikalHi20:00
mordredttx: I will not be able to be at the meeting, I've asked jeblair to proxy for me20:01
ttxyay, quorum20:01
ttxmordred: noted20:01
*** ChanServ sets mode: +o jeblair20:01
* devananda lurks20:01
*** epim has joined #openstack-meeting20:01
*** jeblair changes topic to "OpenStack meetings"20:01
*** gabrielhurley has joined #openstack-meeting20:01
hub_capheh devananda me220:01
ttx#startmeeting tc20:01
openstackMeeting started Tue May 21 20:01:40 2013 UTC.  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
ttxA couple discussion topics on the agenda today20:01
gabrielhurley\o20:01
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:01
jgriffith\o20:02
ttx#topic Common API version discovery mechanism20:02
*** openstack changes topic to "Common API version discovery mechanism (Meeting topic: tc)"20:02
ttxWe said in a past meeting that we would track progress on this20:02
ttx#link https://etherpad.openstack.org/api-version-discovery-proposal20:02
ttxgabrielhurley: care to give a quick update ?20:02
gabrielhurleyWhere it stands currently is that the versioning stuff is pretty much settled. I'd hoped to get some consensus around "capability" discovery too, but that's been a trickier issue, so I think progressing on version discovery independently is the thing to do for now.20:03
markmcyay baby steps20:03
*** radez is now known as radez_g0n320:04
gabrielhurleyNext step is to put together an API sample/spec that everyone can agree on for what the response to a version discovery request should look like.20:04
ttxgabrielhurley: do you think you need anything formal from the TC, or you're happy to go ahead summarizing the road ahead on openstack-dev and jfdi ?20:04
ttxok20:04
gabrielhurleyyep, I'll continue to drive from the dev list side currently, but it's always good to know the TC supports it20:04
*** radez_g0n3 is now known as radez20:05
ttxquestions on that ?20:05
notmynamegabrielhurley: I have yet to see any response to the concerns raised by the swift team on some of the version discovery (although that shouldn't derail the larger questions)20:05
gabrielhurleywhich concern was that?20:05
notmynamethe specific on is that /version/capabilities won't work for swift20:05
notmynameit was on the etherpad (since deleted) and also on the mailing list thread20:06
vishyo/20:06
dolphmgabrielhurley: how do we approach backwards compatibility with existing 300 multiple choice responses? last i checked, there were some discrepancies on the implementation between projects20:06
gabrielhurleygotcha. I think I misunderstood that point. can you ping me separately about that so I can follow up?20:06
gabrielhurleyas I said though, capabilities is gonna have to be a separate issure20:06
*** danwent has joined #openstack-meeting20:06
gabrielhurleydolphm: good question, and we may just have to have workarounds in the clients to deal with the "legacy" responses.20:07
notmynameon the api versioning side, is there any concern that an existing app at host/v1 is now raising it's scope to respond to /?20:07
dolphmgabrielhurley: what about legacy clients?20:07
*** salv-orlando has quit IRC20:07
*** salv-orlando has joined #openstack-meeting20:08
*** pcm__ has quit IRC20:08
dolphmgabrielhurley: just assume none of them are smart enough to be using it? (auth_token currently does some trivial inspection of the 300 response)20:08
gabrielhurleydolphm: the only way out is to rewrite history, which I don't think we're in the business of doing. Legacy clients don't support version discovery. They're pinned to whatever version they were built to work with.20:08
*** ijw1 has joined #openstack-meeting20:08
*** mrunge has quit IRC20:09
gabrielhurleybackporting version discovery sounds like a painful, messy and dangerous task20:09
gabrielhurleyIMHO it's a "from here on out this works" type of deal20:09
dolphmagree20:09
ttxgabrielhurley: see notmyname's question just above20:09
ttx<notmyname> on the api versioning side, is there any concern that an existing app at host/v1 is now raising it's scope to respond to /?20:09
gabrielhurleynotmyname: I don't see a problem with it personally, but I'm open to concerns on it20:09
gabrielhurleythe app technically already owns the / space, even if it's not responding there20:10
gabrielhurleyOpenStack doesn't have good support for services not living at root currently20:10
ttxgabrielhurley: I propose that we consider the topic solved as far as the TC goes -- please just raise it back from the dead if you encounter a roadblock that you think we can collectively help you with20:10
dolphmi'm thinking we need a openstack/common-api project to consistently define things at that level for (at least) core projects20:10
gabrielhurleydolphm: +100020:10
ttxdolphm: a new doc project ?20:11
*** markmcclain has joined #openstack-meeting20:11
ttxOther questions on that topic ?20:12
*** arunkant has quit IRC20:12
dolphmttx: don't know, good question20:12
ttxdolphm: what would be in your openstack/common-api project ? base principles that every openstack API should implement ? Or code to that effect ?20:13
*** alexheneveld has joined #openstack-meeting20:13
dolphmttx: api documentation for the 300 response, approach to versioning that response (if any), perhaps /capabilities when we get there20:13
gabrielhurleybase principles at least would be my hope. reusable code would probably be better off living in oslo, but the two are related20:13
dolphmgabrielhurley: +120:13
ttxgabrielhurley: ok, so common API design rules20:14
gabrielhurleyyeah20:14
gabrielhurleywe direly need a place for that sort of thing to live20:14
* markmcclain thanks to delta.. I'm here for a little while20:14
ttxgabrielhurley: yes. Could be some wiki doc, though20:14
gabrielhurleypros and cons... wikis are easy to change ;-)20:15
dolphmso, keystone-core has plustwoability over https://github.com/openstack/identity-api even though i sort of see it as a doc project -- i'm not sure there's an existing group that makes sense for reviewing openstack/common-api ?20:15
* annegentle catches up reading20:15
notmynamethere is api-site20:15
gabrielhurleythat documents the existing APIs20:15
gabrielhurleythis is more about defining best practices and specs for *new* APIs20:15
gabrielhurleya goal for us all to work towards20:16
*** alexpilotti has quit IRC20:16
dolphmgabrielhurley: ah, you want to include hateos, etc, there long-term?20:16
ttxwe can have a new project and let TC plustwoing it20:16
*** geekinutah has joined #openstack-meeting20:16
gabrielhurleydolphm: yeah. and things like needs around filtering, pagination, etc. that all projects need some form of. we need to stop reinventing the wheel on those.20:16
gabrielhurleyttx: that'd make the most sense20:17
*** geekinutah has left #openstack-meeting20:17
ttxanyway, implementation details. Anything more before we switch to talking about copyright headers ?20:17
*** markmcclain has quit IRC20:17
*** jasondotstar has joined #openstack-meeting20:17
annegentleis there any new requirement for a doc standpoint to support capabilities?20:17
annegentlefor/from20:17
dolphmgabrielhurley: i'm down for that, as long as we make a distinction between what is required of openstack api's and what is a very strongly recommended best practice20:17
gabrielhurleyannegentle: I don't think so20:18
gabrielhurleynot yet at least20:18
annegentlemethinks we don't document extensions very well today so I don't know how capabilities will be an improvement, docs-wise, other than letting the api self-doc? I guess?20:18
gabrielhurleydolphm: absolutely. we can't force anyone to do anything20:18
*** jrodom has joined #openstack-meeting20:18
gabrielhurleyannegentle: it's more for downstream consumers (like Horizon) to understand what things should be allowed in the interface20:18
gabrielhurleybut yes, the docs for extensions are weak. that's a separate issue. ;-)20:19
ttxok, next topic20:19
ttx#topic Getting rid of copyright headers20:19
*** openstack changes topic to "Getting rid of copyright headers (Meeting topic: tc)"20:19
ttxmarkwash raised the idea of getting rid of copyright notices in file headers20:19
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-May/009189.html20:20
ttxI think that *if* we do this, we have to do it consistently across all "OpenStack" projects20:20
markwashwell20:20
mikalDo we really think its worth the effort?20:20
markwashfor some more context #link http://softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html20:20
dolphmmikal: is it really that much effort?20:20
markwashguys, can we hold on here for a sec20:20
ttxmikal: personally I'm not convinced of that20:20
jgriffithI agree with ttx about global, however I think this is going to be more problematic than it's worth20:21
ttxbut some people are not even convinced it's a good idea to drop per-file info20:21
*** mdomsch has quit IRC20:21
* ttx holds20:21
markwashso there are three proposals in that email20:21
hub_capso being a new project, i have 16 different versions of the headers in my code (overstatement). what is the purpose of keeping them?20:21
markwashthe first proposal is pretty simple and cultural: we just try to avoid adding new copyright headers20:22
jgriffithhub_cap: None, except some false sense of *something* to *someone*20:22
markwashthe justification for that is that copyright headers are a small but not insignificant effort to keep up to date20:22
markwashand our best efforts so far have produced huge inaccuracies20:22
*** jrodom has quit IRC20:22
markwashon top of that, they are completely unnecessary for folks to retain copyright20:22
russellbhub_cap: don't confuse the copyright statement with the license in the header, different issues20:22
hub_caprussellb: oh i mean copyright... i know u fixed a good bit of them but ive had issues internally w/ them and my team20:23
*** radez is now known as radez_g0n320:23
markwashthis proposal has no enforcement mechanism other than communication and review20:23
*** seanrob has joined #openstack-meeting20:23
markwashwe're essentially defining what the "new normal is"20:23
ttxmarkwash: I think you increase inaccuracies if you stop adding them while keeping old ones around20:23
dolphmtangential: i don't totally understand how anyone can claim copyright without directly conflicting with the CLA Grant of Copyright License clause- https://review.openstack.org/static/cla.html20:24
ttx(or at least you increase confusion)20:24
* markmc notes the combination of "these headers don't mean anything" and "oh noes! they're inaccurate!"20:24
markmcdon't really get it20:24
jgriffithTBH I'm still trying to figure out the maintenance burden?20:24
jeblairdolphm: granting a copyright licenese is not the same as copyright ownership20:24
markwashjgriffith: there was an email in the thread that documented the effort that was going into reviewing the headers20:25
jgriffithMy thought is if it makes somebody or somebody's legal team feel warm and fuzzy they can add copyright20:25
jeblairdolphm: typically you or your employer owns the copyright in the code you write, and that's what the header indicates20:25
jgriffithmarkwash: I read it, but didn't see the effort20:25
markwashjgriffith: the problem is that we get a lot of cargo-culting around those warm-and-fuzzies20:25
dolphmjeblair: makes sense; thanks!20:25
jgriffithmarkwash: I understand that20:25
jgriffithmarkwash: I'm not saying I like it/agree with it20:26
markwashI think another thing to consider is that, inaccurate copyrights could give the wrong impression to someone20:26
ttxjgriffith: if our group spends more than 10 minutes discussing it, I think that will be more time spent on it than maintaining them ever will20:26
jgriffithJust a firm believer in choosing my battles20:26
markmcjgriffith, yes, yes20:26
jgriffithttx: haha, +120:26
markwashfor example, several files in glance, I might think I can talk direclty to red hat to license the content20:26
markmcsorry20:26
markmcttx, agree20:26
* jgriffith is sad that markmc didn't agree with him :(20:26
markwashttx: my hope with a policy like this is that at least if we know how things *should* be, we can outgrow the problem20:26
markmcjgriffith, oh, I actually did20:27
*** IlyaE has joined #openstack-meeting20:27
* jgriffith yell Yay!!!20:27
markwashwell, I can see you guys have already dismissed my concern about the reviewing time20:27
ttxmarkwash: the trick is that it's not really a technical problem, I think. People/companies are also attached to the fuzzy attribution that those notice get them20:27
markwashbut frankly it is not fun when someone -1s your review becuase of copyright headers20:27
jgriffithmarkwash: they should be slapped20:28
ttxso reaching any kind of consensus around this is likely to take time20:28
ttxfor a... limited gain.20:28
annegentlettx: markwash: there's git blame, and there's copyright headers, for trying to figure out who might know something about a particular file. You can pick which you believe.20:28
*** seanrob has quit IRC20:28
markwashannegentle: since folks should not believe the headers, they seem like a liability20:28
mikalDid we end up with NOTICE files being agreed to?20:28
ttxmikal: no20:29
markmcmikal, no, very much not20:29
markwashI don't really like NOTICE files either. . much better to accept that in-source isn't the way to go20:29
markmcI occasionally pull people up on Copyright headers20:29
markmce.g. if they're obviously just sticking in OpenStack Foundation with no basis20:29
markmcit's not hard to understand what to put in a header20:29
markmcand I expect most people only need to be told once20:29
markmcand then don't make the most obvious mistakes again20:29
*** jcoufal has quit IRC20:29
sdaguemarkmc: my experience differs on that :)20:30
jeblairand copyright is important for an open source project20:30
russellbsdague: on submitters?  hopefully not reviewers20:30
sdagueI've found repeated education required on both contributors and reviewers20:30
jeblairwe should be able to document for new contributors what is expected, and it shouldn't take that much time in the long run20:30
mikalSo, I agree that copyright lines in the headers are inaccurate and annoying. I just worry that its a really big job to remove them. Not technically, but from an arguing with people perspective.20:30
russellbthat's sad, because honestly if you're reviewing code, you *better* have a basic understanding of this stuff20:30
markwashmikal: I feel like the whole "we have to remove them all" is a false dilemma20:30
jgriffithOk, maybe you guys have a point here20:31
*** jcru has joined #openstack-meeting20:31
sdaguerussellb: people didn't get chosen for core reviewing based on how they evaluated copyright headers20:31
markwashoffered by folks who didn't like the proposal to begin with and didn't like finding out their legal advice was out of date20:31
mikalmarkwash: in the sense of you just want to stop adding more and leave the current ones?20:31
jeblairthat's a false solution20:31
mikalmarkwash: cause that seems unfair to me...20:31
markwashmikal: that, plus remove the easy ones, like openstack foundation, and red hat (which has already offered unilateral permission)20:32
markwashmikal: in what way?20:32
markwashjeblair: how so?20:32
mikalmarkwash: I'm sure that people will say "how come I can't have one when all those people over there have them?"20:32
jgriffithmarkwash: I think you'll have the "well they did it, why can't I"20:32
sdagueyeh, pretty mcuch20:32
jeblairmarkwash: that will only make them more inaccurate20:32
sdaguejeblair: +120:32
ttxmikal: +120:32
markwashand we'll say "those are historical artifacts of no import"20:32
jeblairmarkwash: ideally, would you like no copyright notices anywhere?20:33
sdagueif they are of no import, they should come out :)20:33
markwashjeblair: yes20:33
ttxmarkwash: unfortunately some companies see copyright notices as a contribution advertising space. So keeping the old ones around while new contributions don't generate new ones is likely to be... contested20:33
notmynameand the corporate council of all the contributing companies feel that they are of no import? seems unlikely20:33
jeblairthe trouble i have with that is that we would be distributing open source software with no indication of who actually owns the copyright20:34
jeblairi find that disturbing20:34
markwashjeblair: do you feel that way after reading http://softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html ?20:34
markwashI was impressed by the logic there20:34
markwashttx: feels like a job for an AUTHORS file20:35
ttxmarkwash: I fear it's not a legal or technical issue. It's a warm fuzzies and a "why me and not him" issue20:35
jeblairmarkwash: yes, i do actually.  i think it would be very strange not to have any idea who owned the copyright to OpenStack code20:35
notmynameor vcs logs20:35
sdaguettx: that's exactly the bind i'm in. I've gotten preliminary sign off that ibm is cool with them coming out, as long as it's policy and everyone's comes out.20:35
sdaguebut a partial solution is a problem20:35
ttxmarkwash: I agree with you that technically and legally, what you propose is fine20:35
*** davidlyle has joined #openstack-meeting20:35
sdaguejeblair: this is already policy on all the apache projects, do you not use them because of it?20:36
ttxmarkwash: but I expect contributors to continue to push copyrigth notices... and us having little ground to deny them20:36
ttx(unless they are all removed)20:36
jeblairnotmyname: vcs logs can be wrong (and are often VERY wrong in our projects), and moreover, they don't actually tell you who owns the copyright20:36
mikaljeblair: many people don'20:36
mikalt add these headers for non-trivial changes20:36
ttxsdague: agreed. I expect more companies will react just like IBM, hence my "all of them or nothing" stance20:36
mikaljeblair: Look at nova/virt/libvirt/driver.py for example20:37
mikaljeblair: the true list of copyright holders for that file will be much longer than what's there20:37
markwashone potentially tangential concern is, why do people need to track down the copyrights? why can't they just accept asl 2.0 licensing from the foundation?20:37
jgriffithmarkwash: FWIW I agree with the philosophy and what your saying20:37
jgriffithmarkwash: I think the backlash is worse than the maintenance though20:38
markwashjeblair: we can also put in notices that say "you should look to this projects something-or-other for any hope of tracking down copyrights" in every file20:38
jgriffithmarkwash: and I agree with others that it has to be global or nothing20:38
mikalWell, we also haven't tested the backlash at all20:38
mikalWe could just try it with nova and see how bad it is20:38
sdaguemikal: +120:38
markwashso the main reason for global or nothing, is a sense of fairness for companies that want to use notices as a advertising space?20:38
markwashmikal: unfortunately nova is the worst20:38
mikalMaybe we're over estimating how much people care20:38
ttxagree that nobody should care, from a technical or legal standpoint. But in practice they care, because their name is on something, and it has value to them20:39
ttxmikal: we already know IBM cares. I expect others to take the same "ok if everyone does it" stance20:39
markwashttx: I feel like "moving to NOTICE" rather than "removing" might help soften the blow, do you agree?20:39
markmcttx, not NOTICE, that's a whole other ball of wax20:39
ttxmarkwash: yeah, that's why I looked into that, see my thread on legal-discuss20:39
markmcttx, maybe a centralised file, but naming it NOTICE opens a whole other thing20:40
jeblairmikal, sdague: i think it would be terrible to start rejecting commits to nova because they had (C) notices, but not do the same for every project -- not doing the same across all projects is going to cause SO MUCH confusion20:40
ttxmarkmc: NOTICE or whatever works20:40
*** gyee has joined #openstack-meeting20:40
sdaguejeblair: honestly, with different review teams on different projects, it's not going to be any worse than the current situation20:40
markwashin any case, I think its clear that files are not required to have copyright headers, correct?20:41
ttxSo in summary, I expect resistance from companies liking that they are mentioned, unless everyone is removed. Which makes the whole thing a bit complex to set up20:41
ttxand /maybe/ not worth it20:42
markwashso I'd honestly at this point be pretty happy if the canonical HACKING documentation was "put one in if you really want, but we don't really think there are any good legal or otherwise reasons to, so please try to restrain yourself" and leave it at the current free for all20:42
markwashthen perhaps in a year or two, the problem will be relatively smaller in terms of cleanup20:42
ttxmarkwash: that's fine with me, as it's legally and technically accurate20:43
*** elo has quit IRC20:43
markwashalso, if you substantially modify a file, I'm pretty sure you are allowed to remove previous headers and replace your own20:43
markwashso we should make sure people know that as well20:43
markwashand tend towards simple removal without replacement20:44
ttxmarkwash: but my trust in human nature is not as large as yours ;)20:44
markwashttx: honestly, most heads-down devs I've talked to find headers very tedious20:44
*** IlyaE has quit IRC20:44
markwashso being given license not to add anything would be nice for them20:44
markwashI'd like to remove all openstack foundation ones as well, honestly20:45
markwashbut perhaps folks would prefer to wrap up the discussion for now?20:45
ttxmarkwash: I suspect most devs put in what their company asks them to.20:45
dolphmmarkwash: can we agree to remove the openstack foundation/llc ones as a first step here?20:45
mikalWell, I think many of those were added by Rackspace20:45
ttxjeblair: you has a good rationale for keeping per-file info, though20:45
markwashttx: we used to just copy and paste and update the year20:45
jeblairdolphm: hardly20:45
jeblairdolphm: i don't think they are yours to remove20:46
jeblair(nor mine, just to be clear)20:46
* markmc agrees with jeblair 20:46
markwashjeblair: we would need permission from the foundation, yes20:46
markwashbut considering all the inaccurate assignment to the foundation that goes on presently, I think they'd be inclined to accept20:47
mikalI wonder if we should ask the board to back us up here... Ask the board members to go back to their companies and explain the rationale for not adding more copyright headers?20:47
russellbthis is turning into quite a time sink20:47
markmcmarkwash, I actually doubt it - the foundation's counsel is pretty conservative IMHO20:47
ttxmikal: the board and the contributors are two separate bodies20:47
markwashalso I don't believe the foundation hopes to license the parts of openstack they hold copyright to separately from the ASL 2.020:47
markmcmarkwash, dual-licensing is nothing to do with this20:48
markwashoh?20:48
ttxWe should spend that time spent discussing this onto something much more useful, like suggesting names for stuff20:48
jeblairmarkwash: my understanding is that the foundation has copyright ownership of a chunk of code that rackspace donated to it, and that its (current) bylaws prohibit it from doing anything with that code other than releasing it under ASL-2.020:48
jeblairmarkwash: it may also own copyright in code that fungi and I write.20:49
markwashttx: Infuriating :-)20:49
*** lpabon has quit IRC20:49
*** seanrob has joined #openstack-meeting20:49
* fungi nods20:49
markwashjeblair: that seems like they don't need notices then20:49
fungii bet ttx can write code too ;)20:49
ttxfungi: I can and I do :)20:50
ttxbut i'm not a Foundation employee so I'll put in whatever I want !20:50
hub_capheh20:50
fungiahh, right. crazy contractors20:50
jeblairmarkwash: i'm not sure why the foundation owning a significant amount of code means they don't need a notice...20:50
markwashjeblair: to me it seems like the set of rights they have with code they own copyright to, and the set of rights they have with code licensed to them by the CLA, are congruent20:51
jeblairmarkwash: it seems like aside from anything else, for the purposes of copyright ownership of code, the foundation is in the same boat as all the other contributors20:51
markwashjeblair: the other issue is that folks at least for a time have been misattributing copyrights to the foundation20:52
markmcmarkwash, adding or removing the headers doesn't change ownership20:52
jeblairmarkwash: that should stop.  :)20:52
*** Vek has joined #openstack-meeting20:52
ttxseriously, this may seem like an easy problem to solve, but it's not -- and the current situation is not nearly bad enough for us to invest in fixing it20:53
jeblairttx: +120:53
ttxSo documenting the technical and legal realities will certainly help in clearing things up20:53
dolphmttx: that sounds like a sane conclusion for the moment20:53
*** rahmu has joined #openstack-meeting20:54
*** SlickNik has joined #openstack-meeting20:54
ttxbut I wouldn't hold my breath on hoping everyone can dance to the same tune on that anytime soon20:54
markwashI think if we document the realities better, and some simple advice, we'll be in a better place20:54
ttxit's one of thsoe things you need to get right from the beginning20:54
annegentlettx: I have to offer https://wiki.openstack.org/wiki/Documentation/Copyright20:54
ttxbecause touching it afterwards is painful20:54
ttxbecause it's not just a technical issue.20:54
markwashannegentle: I'd like to streamline that page, would you be open to reviewing some changes?20:55
markmcwould be good to add to https://wiki.openstack.org/wiki/LegalIssuesFAQ too20:55
*** HenryG has joined #openstack-meeting20:55
annegentlemarkwash: yes, and you could also move it out from under /Documentation/20:55
annegentlemarkmc: will do20:55
markwashannegentle: we need some hard and fast rules "do do this" "don't do this" for some of the obvious problems we have seen20:56
annegentleI think 1-2 years and some guidance will help.20:56
* markwash is happy about not being on the hook for writing HACKING checks, at least20:57
ttxheh20:57
ttx#topic Open discussion20:57
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:57
ttx2 more minutes, anyone has anything to raise ?20:57
dolphmhard and fast is difficult when the legal speak is subjective enough to use wording like "substantially revised or updated"20:58
annegentleI wanted to bring up a doc rename in progress here.20:58
hub_caphey just wanted to mention that we are changing names in reddwarf land, nothign really to discuss20:58
ttxhub_cap: we could... suggest names.20:58
ttxwe like to do that.20:58
annegentleWe've been removing "Developer Guide" from the titles of documents in <project>-api repositories.20:58
hub_capttx: https://gist.github.com/hub-cap/562271420:58
hub_capmy favorite so far is cask :)20:58
markwashhub_cap: you would20:58
hub_capif u do have a suggestion feel free to ping me, ill add it20:58
annegentleSome of you have/haven't noticed. I originally was guiding Diane Fleming to make them "API Specifications" but I think "API Reference" is more apt for cross-project truthiness.20:59
hub_capmarkwash: \o/20:59
markwash:-)20:59
ttx"Stratius" :)20:59
markmchah20:59
* markmc was about to say exactly the same20:59
*** matty_dubs has joined #openstack-meeting20:59
annegentleIf you PTLs/TCers have input, do say so in the reviews.20:59
markmcRover? really?20:59
dolphmhub_cap: it'd be nice if that list had a one liner explanation for each name lol20:59
* jeblair looks for a weather baloon smothering someone21:00
hub_capdolphm: peep the last line21:00
markmchub_cap, nice work though, naming is frickin hard21:00
hub_capmarkmc: ya not a fan of rover or rex... but when i removed them it hurt someones feelings.. and im def not in the business of that LOL21:00
dolphmhub_cap: then why is there a gist?!21:00
hub_capdolphm: cuz i locked it down21:00
hub_capit went crazy quick21:00
ttxok, end21:00
ttx#endmeeting21:00
*** openstack changes topic to "OpenStack meetings"21:00
openstackMeeting ended Tue May 21 21:00:57 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-05-21-20.01.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-05-21-20.01.txt21:01
russellbhub_cap: sometimes being a leader is being willing to say no and hurt someone's feelings :-p21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-05-21-20.01.log.html21:01
mikalLaters peoples21:01
ttxmarkmc, dolphm, notmyname, jd__, markwash, jgriffith, russellb, shardy, gabrielhurley, markmcclain: still around ?21:01
russellbyep.21:01
notmynamehere21:01
gabrielhurley\o21:01
jd__o/21:01
shardyo/21:01
* markwash sighs21:01
*** robertmyers has joined #openstack-meeting21:01
jgriffitho/21:01
markmcyep21:01
dolphmo/21:02
ttx#startmeeting project21:02
openstackMeeting started Tue May 21 21:02:16 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
*** cp16net is now known as cp16net|away21:02
ttxAt the end of the day next Tuesday we will cut the havana-1 milestone-proposed branches21:02
*** robertmyers has left #openstack-meeting21:02
ttxThat leaves one week to merge stuff in havana-1, so we'll look into plans and postpone what we already know won't make it21:02
ttx#topic General stuff21:02
*** openstack changes topic to "General stuff (Meeting topic: project)"21:02
*** jaybuff has left #openstack-meeting21:03
ttxI don't have anything cross-project to report21:03
ttxannegentle, jeblair/mordred, sdague/davidkranz: news from Docs/Infra/QA teams ?21:03
*** SlickNik has left #openstack-meeting21:03
ttxannegentle: I guess that doc rename also applies here21:03
*** jang1 has joined #openstack-meeting21:03
annegentlettx: was just going to mention.21:03
ttxplease do21:03
annegentleall, look for "API Specifications" being renamed to "API Reference" as the naming is more apt for cross-project use21:04
annegentleThey're currently called "Developer Guides" which is confusing.21:04
*** cp16net|away is now known as cp16net21:04
jeblairttx: nak21:04
*** jbjohnso has quit IRC21:04
annegentleDoc team has some automation scripts now for bringing in all config info automatically (did I report that last week?)21:04
annegentleWe're also hiring a contractor this summer to help with install guide madness.21:05
ttx(maybe?)21:05
*** sandywalsh has quit IRC21:05
annegentleCisco is hiring the contractor.21:05
ttxThanks, Cisco.21:05
annegentlethat's all I've21:05
ttxanything else before we go project-specific ?21:05
sdaguettx: nothing notable on QA21:06
ttx#topic Oslo status21:06
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:06
ttxmarkmc: hi!21:06
ttxsdague: ok21:06
markmcyo21:06
ttx#link https://launchpad.net/oslo/+milestone/havana-121:06
markmctwo havana-1 bps left21:06
ttxLooks like you're in pretty good shape, if I am to trust those delivery statuses21:06
markmcdelayed-messaging is coming along, may make it21:06
markmccommon-apiclient is a big patch, but the author is splitting it up21:07
markmcso, that may make it too21:07
ttxok21:07
ttxTwo remarks on the roadmap:21:07
ttxhttps://blueprints.launchpad.net/oslo/+spec/service-restart was proposed for havana and needs to be triaged21:07
ttxmarkmc: Did you look into trusted-messaging's dependency on key-distribution-server ?21:07
markmcyes, I put a tonne of info into the bp on that21:08
markmcbasically, yes we require *some* key distribution method21:08
markmckeystone as a kds is the current plan21:08
markmcso, right now - it's blocked on that21:08
*** cp16net is now known as cp16net|away21:08
markmcif that wasn't making progress, we might consider a hacky short term plan21:08
ttxmarkmc: can I mark it Blocked to reflect that ?21:09
markmcwill look at service-restart21:09
markmcok, will do21:09
ttxmarkmc: anything you wanted to raise ?21:09
*** cp16net|away is now known as cp16net21:09
markmcwe added two new oslo-core members today21:09
markmcFlavio Percoco21:09
markmcand Zhongyue Luo21:09
markmcwill send out a mail on that21:09
ttxcongrats!21:09
markmcthat's it, otherwise21:10
ttxQuestions about Oslo ?21:10
ttx#topic Keystone status21:10
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:10
ttxdolphm: o/21:10
dolphmo/21:10
ttx#link https://launchpad.net/keystone/+milestone/havana-121:10
*** bdpayne has quit IRC21:10
ttxdolphm: you deferred delegated-auth-via-oauth ?21:11
dolphmttx: yes, although there's good progress against that bp that will probably merge in m1, there's a long list of remaining TODO's that won't make it21:11
dolphmi'm looking into splitting the bp into more achievable goals21:11
dolphmso we might have a completed checkbox for m1, but if not -- it's on track for m221:12
ttxbug 967832 is targeted to havana-1 but has no assignee -- any idea if someone will work on that ?21:12
uvirtbotLaunchpad bug 967832 in keystone "Instances are still running when a tenant are deleted" [High,Confirmed] https://launchpad.net/bugs/96783221:12
*** jhenner has joined #openstack-meeting21:12
ttx(or if we should just untarget it ?)21:12
dolphmthat's being worked in bp notifications21:12
dolphmhttps://blueprints.launchpad.net/keystone/+spec/notifications21:13
ttxso for havana-2 ?21:13
dolphmwhich is blocked by https://blueprints.launchpad.net/keystone/+spec/unified-logging-in-keystone ... which we just added to m1 and is nearly complete21:13
dolphmttx: yes, looks to be on pace for m221:13
ttxok will retarget it21:13
*** markmc has quit IRC21:14
*** HenryG has quit IRC21:14
ttxOn the more general havana plan, I saw that ayoung's proposal to split backends (https://blueprints.launchpad.net/keystone/+spec/split-identity) is missing from it21:14
*** markmcclain has joined #openstack-meeting21:14
dolphmthe scope of that bp is huge, and i'm trying to get some clarity on what we can accomplish in more discrete blueprints, one of which is https://blueprints.launchpad.net/keystone/+spec/domain-backend21:15
*** boris-42 has quit IRC21:15
markmcclaino/21:15
ttxyes, that's why I was a bit concerned to not see it appear anywhere21:15
dolphmalong with https://blueprints.launchpad.net/keystone/+spec/extract-credentials-id which has already merged21:15
ttxok, ideally there would be a set of dependent bps21:15
*** luis_fdez has joined #openstack-meeting21:16
ttxdolphm: Anything more about Keystone ?21:16
dolphmttx: will do21:16
*** gokrokve_ has quit IRC21:16
dolphmthat's it!21:16
ttxQuestions anyone ?21:16
ttx#topic Ceilometer status21:16
*** openstack changes topic to "Ceilometer status (Meeting topic: project)"21:16
jd__o/21:16
ttxjd__: hey21:16
ttx#link https://launchpad.net/ceilometer/+milestone/havana-121:16
ttxWhat's the status on udp-publishing and scheduler-counter ?21:17
jd__scheduler-counter should be merged RSN now, no blocker21:17
jd__udp publishing will be sent to review tomorrow21:17
ttxcollector-stores-events seems to be a bit short for next week ?21:17
jd__ttx: yes21:18
*** sandywalsh has joined #openstack-meeting21:18
jd__add-event-table took more time we think I guess21:18
jd__I'll talk with sandywalsh about it and I think we'll postpone21:18
ttxjd__: how about deferring it to havana-2 and move it back to h1 in case it miraculously makes it ?21:18
jd__ttx: yeah works for me :)21:18
ttxOK. Looking into the general havana plan now...21:19
ttxYou have 3 proposals to triage @ https://blueprints.launchpad.net/ceilometer/havana/+setgoals21:19
ttxas if you didn't have enough BPs already ;)21:19
ttxto which you may want to add https://blueprints.launchpad.net/ceilometer/+spec/hyper-v-agent21:19
ttxjd__: sqlalchemy-metadata-query is marked "Essential" -- who will be working on it ?21:19
jd__ttx: nobody, and that's a problem, we keep essential so someone is willing to take it..21:20
jd__whishful thinking21:20
ttxhrm, not sure it's not the other way around :)21:20
jd__haha21:20
ttxif nobody takes it at start of H2 we'll have to remove it or down-prioritize it21:21
jd__ttx: agreed21:21
ttxI don't want to communicate that it WILL be in when it's likely that it won't21:21
ttxAlso it would be great to have a milestone target indicated for the two high-priority blueprints: hbase-metadata-query and alarm-api21:21
ttxjd__: anything you wanted to mention ?21:21
jd__nop, everything's fine otherwise21:22
ttxQuestions on Ceilometer ?21:22
*** cody-somerville has quit IRC21:22
*** matty_dubs is now known as matty_dubs|gone21:22
ttx#topic Swift status21:22
*** openstack changes topic to "Swift status (Meeting topic: project)"21:22
notmynamehi21:22
ttxnotmyname: o/21:22
ttx#link https://launchpad.net/swift/+milestone/1.8.121:22
ttxnotmyname: quick update on 1.8.1 progress ?21:22
notmynameI want to start getting it ready for release when the last global clusters feature lands21:23
notmynameshould happen Real Soon Now (tm), but no dates yet21:23
notmynameb/c there's more that goes into it than just the patch landing21:23
ttxa bit of black magic is needed too21:23
notmyname:-)21:23
ttxnotmyname: anything else you wanted to raise ?21:24
notmynameI've also updated #link https://wiki.openstack.org/wiki/Swift/API to be more funtion-centric21:24
notmynameit's our current work on formalizing the swift v1 api spec21:24
*** luis_fdez has quit IRC21:24
ttx#link https://wiki.openstack.org/wiki/Swift/API21:24
notmynamethose are the two topics I have21:24
notmynamethanks21:24
ttxQuestions about Swift ?21:24
*** jasondotstar has quit IRC21:24
ttx#topic Glance status21:25
*** openstack changes topic to "Glance status (Meeting topic: project)"21:25
ttxmarkwash: o/21:25
ttx#link https://launchpad.net/glance/+milestone/havana-121:25
markwashhello!21:25
ttxpreparing a heavy havana-2, I see21:26
*** ayoung has joined #openstack-meeting21:26
markwashwell, some of those bps are just rolling on through21:26
markwashI have been and will continue to seek more feedback from some of the assignees I'm not working as closely with21:26
ttxYou also have 4 bugs targeted...21:26
ttxno recent activity on bug 1163012 and bug 102074921:26
uvirtbotLaunchpad bug 1163012 in glance "glance-manage should use entry_points instead of scripts" [Wishlist,In progress] https://launchpad.net/bugs/116301221:27
uvirtbotLaunchpad bug 1020749 in glance "Use Openstack-Common notifier" [Wishlist,Triaged] https://launchpad.net/bugs/102074921:27
ttxreview for bug 1173415 is abandoned21:27
uvirtbotLaunchpad bug 1173415 in glance "Remove glance-control from the test suite" [High,In progress] https://launchpad.net/bugs/117341521:27
ttxShould any of those be removed from the list ?21:27
markwashttx, I'll clean that up21:27
ttxcool, thx21:27
ttxLooking at the general havana plan now...21:27
markwashbeen focusing on blueprints so far21:27
ttxLooks pretty good to me now21:28
* markwash tries21:28
ttxmarkwash: anything you wanted to mention ?21:28
markwashnothing at the moment, thanks21:28
ttxQuestions on Glance ?21:28
ttxmarkwash: thx!21:29
ttxmarkmcclain: around ?21:29
markmcclainhi21:29
ttx#topic Quantum status21:29
*** openstack changes topic to "Quantum status (Meeting topic: project)"21:29
ttxmarkmcclain: hi!21:29
ttx#link https://launchpad.net/quantum/+milestone/havana-121:29
ttxNice progress, still a lot to land but you're in a pretty good shape21:30
ttxmarkmcclain: About remove-use-of-quantum: do you think it's still doable for havana-1 ?21:30
ttxdo you have some patch prepared that just needs the go-ahead on the naming ?21:30
markmcclainit's still doable, but I haven't heard back on the names we sent over21:30
ttxmarkmcclain: I asked Mark Collier to get back to you ASAP21:31
*** IlyaE has joined #openstack-meeting21:31
*** sushils has joined #openstack-meeting21:31
markmcclainawesome.. thanks21:31
ttxnot sure we can actually get everything lined up, including CI, with the rush on reviews pre-h121:31
markmcclainyeah.. that's my biggest concern21:32
*** bdpayne has joined #openstack-meeting21:32
*** dhellmann is now known as dhellmann-away21:32
ttxmaybe it's a better bet to do it just after h1. Not very happy with publishing another thing called "quantum" now but meh21:32
ttxwe'll see what we can do21:32
ttx#action ttx to check with CI impact of renaming quantum a few days before milestone publication21:32
ttxLooking at your 19 havana-1-targeted bugs now...21:33
ttxbug 1136252 does not seem to be worked on... still want to keep it in-list ?21:33
uvirtbotLaunchpad bug 1136252 in quantum "[Metaplugin] fails with VIF extension" [Wishlist,Confirmed] https://launchpad.net/bugs/113625221:33
*** sushils has quit IRC21:34
markmcclainthat bug was added last day or so21:34
ttxmarkmcclain: I somehow doubt that21:34
markmcclainif code is not ready by Thursday I'm going to move it out21:34
ttxlast activity 2013-03-05 21:47:5721:34
*** sushils has joined #openstack-meeting21:34
ttxmarkmcclain: ok21:35
ttxA couple remarks on the general havana plan:21:35
*** eharney has quit IRC21:35
ttxA few blueprints are targeted to havana-2 but not in the havana series goal: quantum-service-agent, lbaas-integration-with-service-types, varmour-fwaas-driver21:35
markmcclainttx: you're right I was thinking about another metaplugin bug21:36
ttxipsec-vpn-reference, lbaas-agent-scheduler and sharing-model-for-external-networks need a priority set...21:36
*** cody-somerville has joined #openstack-meeting21:36
markmcclainI'll clean up those BPs21:36
ttxthat's all I had21:36
ttxmarkmcclain: anything you wanted to raise ?21:36
*** colinmcnamara has joined #openstack-meeting21:36
markmcclainwe covered renaming which was my main item21:37
ttxQuestions on Quantum ?21:37
ttx#topic Cinder status21:37
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:37
ttxjgriffith: hi!21:37
ttx#link https://launchpad.net/cinder/+milestone/havana-121:37
jgriffithhola21:37
ttxLooks like it's a bit late21:37
ttxAnything you already know won't make it ?21:37
jgriffithttx: I already kicked a few out, EMC and NetApp held up by legal21:38
jgriffithttx: I think the rest will make it21:38
ttxok21:38
ttxYou also have 7 open bugs on the havana-1 list...21:38
jgriffithttx: I'll adjust tomorrow night if things don't go as I plan21:38
ttxbug 1169290, bug 1166899, bug 1171906 and bug 1161557 have no assignee21:38
uvirtbotLaunchpad bug 1169290 in cinder "local attach of iSCSI silently fails" [High,New] https://launchpad.net/bugs/116929021:38
uvirtbotLaunchpad bug 1166899 in cinder "MultiBackend naming convention not compatable with zmq" [Medium,Confirmed] https://launchpad.net/bugs/116689921:38
uvirtbotLaunchpad bug 1171906 in cinder "cinder fail test_schedule_happy_day test" [Medium,Confirmed] https://launchpad.net/bugs/117190621:38
uvirtbotLaunchpad bug 1161557 in nova "Race condition in handling of udev generated symlinks" [Low,Triaged] https://launchpad.net/bugs/116155721:38
*** bradjones|away is now known as bradjones21:38
jgriffithttx: Yes21:38
ttxand the others haven't seen any recent activity... so this list could probably be refreshed/refined21:38
jgriffithttx: I'll be the default for the ones not assigned21:38
jgriffithttx: I may drop two of them, haven't decided yet21:39
ttxjgriffith: maybe go over them and remove the milestone target if nobody will work on them21:39
jgriffithI'll get to them in the next 48 hours though21:39
ttxLooking at the general havana plans now...21:39
ttxYou have four more to triage at https://blueprints.launchpad.net/cinder/havana/+setgoals21:39
*** epim has quit IRC21:39
ttxjgriffith: Did you work with Avishay on breaking up his volume-migration blueprint ?21:39
jgriffithdang it!21:39
jgriffithttx: I've asked him to do it, but haven't seen any effort there yet21:40
jgriffithttx: I'll harass him in our meeting tomorrow or do it for him21:40
ttxjgriffith: Sounds good. Anything else on your mind ?21:40
jgriffithhaha...21:40
jgriffithnot that I should share here :)21:40
ttxnaughty.21:40
ttxQuestions on Cinder ?21:40
ttx#topic Nova status21:41
*** openstack changes topic to "Nova status (Meeting topic: project)"21:41
russellbo/21:41
ttxrussellb: hey21:41
ttx#link https://launchpad.net/nova/+milestone/havana-121:41
russellbbeen updating during meeting, heh21:41
ttxNice progress overall... anything you suspect won't make it ?21:41
russellbi think everything left is doable21:41
russellbwill continue to track progress and push on these things throughout the week21:41
ttxI see you fixed the bug list too, good21:42
ttxAbout the general havana plan, there are 9 hyper-v blueprints that are targeted to havana-{2,3} for which the series goal should probably be set21:42
russellbyeah, untargeted a bunch of stuff that didn't need to block the release21:42
ttxYou can see them at https://blueprints.launchpad.net/nova?searchtext=hyper-v21:42
russellbargh ... this part of launchpad drives me crazy21:43
russellbso hard to catch all of these21:43
russellbok, will fix these up21:43
ttxthe trick is there is no way to really automate this one way or another21:43
ttxsince half of them should be denied21:43
russellbi like how setting havana is gated, but wish the milestone was too21:44
ttxrussellb: anything else you wanted to mention ?21:44
russellbdon't think so21:44
ttxAny question on Nova ?21:45
*** jang1 has quit IRC21:45
ttx#topic Heat status21:45
*** openstack changes topic to "Heat status (Meeting topic: project)"21:45
shardyhi21:45
ttxshardy: o/21:45
ttx#link https://launchpad.net/heat/+milestone/havana-121:45
ttxLooks like you're in good shape...21:45
ttxWhat's the status of native-cinder-volume ?21:45
shardyYep, couple of bugs might get bumped, but otherwise good21:46
*** jlucci has quit IRC21:46
ttxWas wondering if https://blueprints.launchpad.net/heat/+spec/scalingpolicy-update-stack wasn't actually complete21:46
ttxshardy: yes, your targeted bug list looks pretty current... except maybe bug 1166084 and bug 115859821:47
shardyttx: native-cinder-volume patches are under review atm, last one pending to be merged I think21:47
uvirtbotLaunchpad bug 1166084 in heat "Creation of NetworkInterface resource failed because GroupSet attribute is invalid" [Medium,Triaged] https://launchpad.net/bugs/116608421:47
uvirtbotLaunchpad bug 1158598 in heat "REST error body should be parseable by clients" [Medium,Triaged] https://launchpad.net/bugs/115859821:47
ttxbut otherwise looks good21:47
*** martine_ has quit IRC21:47
shardyyes you're probably right re scalingpolicy-update-stack, will fix21:47
shardywill clarify which bugs, if any, move to h2 at our meeting tomorrow21:48
*** dolphm has quit IRC21:48
ttxI see you added milestone targets to most BPs21:48
ttxIn the high-prio list that only leaves open-api-dsl untargeted21:48
shardyyes, particularly the high priorit ones21:48
ttxAlso resource-template (High priority) depends on resource-properties-schema (Low priority) -- that should be adjusted21:49
shardythat is deliberate, since it's kind of an umbrella BP21:49
ttxshardy: ok21:49
shardyand also we're still very much discussing the scope of what will be achievable for havana21:49
*** amyt_ has joined #openstack-meeting21:50
shardyttx: ok, will fix the resource-* ones21:50
ttxshardy: anything else you want to raise ?21:50
shardyttx: don't think so, no21:50
ttxQuestions about Heat ?21:50
ttx#topic Horizon status21:50
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:50
ttxgabrielhurley: o/21:50
gabrielhurley\o21:50
ttx#link https://launchpad.net/horizon/+milestone/havana-121:50
gabrielhurleyrefresh if you haven't recently21:51
ttxTime to land stuff, apparently :)21:51
gabrielhurleyyeah. the story is basically "everything's got patches, and we need to do a lot of reviewing"21:51
*** amyt_ has quit IRC21:51
gabrielhurleybut aside from that it's all looking good for next tuesday21:51
*** amyt has quit IRC21:51
ttxWas wondering if https://blueprints.launchpad.net/horizon/+spec/admin-password-for-server shouldn't be marked "implemented"21:51
ttxcouldn't find another review up for it21:52
gabrielhurleypossibly21:52
*** amyt has joined #openstack-meeting21:52
ttxWhat's the status for heat-ui ?21:52
gabrielhurleyI'm a little behind the last day or two21:52
ttxall patches proposed ?21:52
gabrielhurleyheat-ui just got posted and I need to look at it. everything's up, but it's got the most work needed.21:52
ttxok21:52
ttxyou refined your bug list I see21:53
gabrielhurleyyep21:53
gabrielhurleyI always just roll the bugs I think *can* be fixed from milestone to milestone21:53
ttxso those are all the ones you'd like to see closed by h1 delivery day ?21:53
gabrielhurleyideally21:53
gabrielhurleyit's really just the transifex stuff that doesn't have a review already21:54
ttxok, we'll refine again next week with the ones that would be worth backporting hassle21:54
gabrielhurleyyep21:54
ttxIn other news, two new blueprints were proposed for havana21:54
*** stevemar has quit IRC21:54
ttxhttps://blueprints.launchpad.net/horizon/havana/+setgoals21:54
ttxgabrielhurley: anything you wanted to mention ?21:55
gabrielhurleynot currently21:55
ttxQuestions on Horizon ?21:55
*** woodspa has quit IRC21:55
ttx#topic Incubated projects21:55
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:55
ttxhub_cap, devananda: hi!21:55
devanandattx: hi!21:56
ttxdevananda: got your repo set up ?21:56
devanandayes :)21:56
hub_caphai21:56
*** jpich has joined #openstack-meeting21:56
* hub_cap doesnt have a name... or a repo21:56
ttxhub_cap will wait for a new name before he can move off stackforge21:56
hub_capdef21:56
ttxAny question ?21:57
*** spzala has quit IRC21:57
ttxI don't think it makes a lot of sense to do a h1 for any of you next week21:57
devanandano questions here. i can give a small update if you want21:57
*** kspear has joined #openstack-meeting21:57
*** timello has quit IRC21:57
hub_capttx: we honestly could... our project is pretty far along so to speak21:57
ttxsince one doesn't have a lot to show and the other doesn't have the definitive name yet ?21:57
hub_capoh well ya21:57
*** SlickNik has joined #openstack-meeting21:57
ttxhub_cap: how about we do one once you get the name in21:58
hub_capthats a sticking point isint it :P21:58
hub_capttx: sounds great21:58
devanandabut yea, h1 doesn't make sense for Ironic. mostly straw-men here right now :)21:58
ttx#action ttx to help with reddwarf h1 publication when the name issue is settled21:58
ttxdevananda: please go ahead21:58
ttx(with a small update)21:58
devanandawe're still laying the groundwork for most things21:59
*** seanrob has quit IRC21:59
devanandaAPI spec should be relatively complete soon, hopefully this week21:59
devanandamanager service and so on as well21:59
*** seanrob has joined #openstack-meeting21:59
devanandabut lots to do :) still hoping to have something to show for h2, but hard to be sure yet what it'll be22:00
devananda[eol]22:00
ttxdevananda: thx!22:00
hub_capupdate in one line: Heat integration and devstack/tempest integration my two highest prios. backups and notifications just merged for h1. hope to have heat in h2.22:00
ttxthat closes our meeting. Thanks everyone !22:00
ttx#endmeeting22:00
*** openstack changes topic to "OpenStack meetings"22:00
openstackMeeting ended Tue May 21 22:00:49 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-05-21-21.02.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-05-21-21.02.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-05-21-21.02.log.html22:00
*** Vek has left #openstack-meeting22:01
gabrielhurley#startmeeting horizon22:01
openstackMeeting started Tue May 21 22:01:38 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: horizon)"22:01
openstackThe meeting name has been set to 'horizon'22:01
gabrielhurleyhello folks22:01
gabrielhurley#topic overview22:01
*** openstack changes topic to "overview (Meeting topic: horizon)"22:01
bradjoneshey22:01
jpichHello22:01
*** shardy has left #openstack-meeting22:02
davidlyleHello22:02
gabrielhurleyThe milestone-proposed branch for H1 will be cut about this time next Tuesday, so we've got 'til then to land stuff.22:02
*** amyt_ has joined #openstack-meeting22:02
gabrielhurleyThat said, I think we're in good shape.22:02
gabrielhurleythere's lots of stuff to review (I'm working my way through it right now)22:02
*** vkmc has quit IRC22:02
gabrielhurleybesides that info, I can't say there's a ton of stuff going on right now from the project level.22:02
gabrielhurleySeeing as how my attention is split 3 ways I'm gonna just open it up for questions and discussion and let y'all lead this one to some degree.22:03
gabrielhurley#topic open discussion22:03
*** openstack changes topic to "open discussion (Meeting topic: horizon)"22:03
*** seanrob has quit IRC22:04
bradjonesI have a bit of an issue with horizon + devstack + fedora you may have seen the email from Kyle in the mailer?22:04
*** afazekas has quit IRC22:04
gabrielhurleyI did see that22:04
jpichAbout https://bugs.launchpad.net/horizon/+bug/1182011 -- I think there is a translation file missing on Transifex, who should be contacted to upload it?22:04
uvirtbotLaunchpad bug 1182011 in horizon "djangojs.po not available on Transifex" [High,Confirmed]22:04
gabrielhurleyjpich: I can handle that one22:04
jpichgabrielhurley: Thanks!22:04
bradjonesWell if we run horizon from run-tests runserver everything works22:05
bradjonesjust running from devstack all the js is broken22:05
jpichbradjones: I had a similar issue on a VM where I just upgraded devstack, but it works fine on a fresh install (this may not help, I realise)22:05
jpichusing Fedora 1822:05
bradjonesthinking this may be some sort of cache issue22:05
bradjonesjpich: yes22:05
gabrielhurleyI've been reading along but haven't had a chance to investigate. Nothing jumps to mind so obviously that I can say what it is without trying it.22:06
*** amyt has quit IRC22:06
*** amyt_ is now known as amyt22:06
bradjonesWhen we go back to a commit before pulling everything seems fine hence thinking maybe some sort of local cache22:06
bradjonesjpich: I also have it working on a completely fresh vm just hoping there may be a solution other than wiping and starting again22:07
*** dwcramer has quit IRC22:08
bradjonesI'm struggling to know if the issue sits with devstack or horizon?22:09
gabrielhurleyyou could try just deleting your STATIC_DIR directory...22:09
gabrielhurleywhatever that's set to in your local_settings22:09
*** davidlyle- has joined #openstack-meeting22:09
davidlyle-davidlyle222:10
*** davidlyle- has quit IRC22:11
*** dklyle has joined #openstack-meeting22:11
jpichUnrelated: I was also wondering about jenkins testing on both Django 1.4 and 1.5. I think we talked about it but I can't remember what was the next step to get it done. I would expect we'll lose compatibility fairly quickly if we don't check for it22:12
gabrielhurleyneed to work that with the CI team22:12
*** davidlyle has quit IRC22:12
gabrielhurleymordred would be the best person to ask22:12
bradjonesgabrielhurley: I can't see where that is defined22:13
jpichOk, I'll do that22:13
gabrielhurleybradjones: sorry, it's STATIC_ROOT https://github.com/openstack/horizon/blob/master/openstack_dashboard/settings.py#L5122:14
gabrielhurleyalso, you might check the COMPRESS_OUTPUT_DIR specifically, inside the static root dir. https://github.com/openstack/horizon/blob/master/openstack_dashboard/settings.py#L12522:15
bradjonesgabrielhurley: thanks I will give that a try22:15
gabrielhurleythat's the only place where (depending on configuration) things get compiled locally (which is sort of like caching)22:15
gabrielhurleyI've forgotten, is devstack set up to do run the collecstatic and compress commands, or to serve the media in debug mode without those?22:16
bradjoneswould I be right in saying that by default this folder would be in /opt/stack/horizon/ ?22:16
gabrielhurleybradjones: probably. to be honest I haven't made an edit to the horizon devstack code in over a year. I got it working way-back-when and have ignored it ever since.22:17
*** eharney has joined #openstack-meeting22:17
*** eharney has quit IRC22:17
*** eharney has joined #openstack-meeting22:17
* gabrielhurley ought to go look at it...22:17
bradjoneswell i've tried just deleting everything from /opt/stack/horizon/ then letting devstack reclone the repo but the issue persists, this should have cleared everything out22:19
gabrielhurleyhmmm22:19
gabrielhurleythat's very strange22:19
gabrielhurleyI'm pretty sure there aren't any weird apache modules installed that'd be doing that...22:20
bradjonesyou mentioned about setting devstack up to run the collectstatic commands could you elaborate as how I can set that up22:21
*** changbl has quit IRC22:23
*** amyt has quit IRC22:23
*** Brainspa1kle is now known as Brainspackle22:24
gabrielhurleyit doesn't look like devstack is serving the static media that way22:24
gabrielhurleybut if you wanted to run the commands I believ you can do "./run_tests.sh -m collectstatic" and "./run_tests.sh -m compress"22:25
gabrielhurleythe "-m" passes the command through to django's manage.py with the right settings file and such under the hood22:25
*** neelashah has quit IRC22:25
gabrielhurleycaveat: I haven't tried running those myself in a few months22:25
bradjonesok thanks I will try out all the suggestions failing that I guess wipe and start again as that doesn't cause any issues22:26
*** keith_bray has quit IRC22:27
*** flaper87 has quit IRC22:27
gabrielhurleythat's really weird though22:27
gabrielhurleyI'd love to know what's at the root of it22:27
bradjonesif I find a fix I will respond in the mailer22:28
*** cp16net is now known as cp16net|away22:31
*** alexheneveld has quit IRC22:31
*** jhenner has quit IRC22:32
*** markmcclain has quit IRC22:36
*** enikanorov has quit IRC22:39
*** enikanorov has joined #openstack-meeting22:40
*** dperaza1 has joined #openstack-meeting22:41
*** dperaza has quit IRC22:42
jpich...I'm gonna guess the meeting's over now. Chat with you all next week ;)22:43
gabrielhurleyah. whoops. yes, meeting over. Thanks folks!22:44
gabrielhurley#endmeeting22:44
*** openstack changes topic to "OpenStack meetings"22:44
openstackMeeting ended Tue May 21 22:44:21 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-05-21-22.01.html22:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-05-21-22.01.txt22:44
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-05-21-22.01.log.html22:44
*** gabrielhurley has quit IRC22:45
*** jpich has quit IRC22:48
*** bradjones is now known as bradjones|away22:48
*** alexheneveld has joined #openstack-meeting22:49
*** dklyle has quit IRC22:50
*** epim has joined #openstack-meeting22:50
*** tomoe_ has joined #openstack-meeting22:53
*** seanrob has joined #openstack-meeting22:54
*** otherwiseguy has quit IRC22:55
*** tomoe_ has quit IRC22:58
*** tomoe_ has joined #openstack-meeting22:58
*** seanrob has quit IRC23:02
*** matiu has joined #openstack-meeting23:02
*** bdpayne has quit IRC23:03
*** seanrob has joined #openstack-meeting23:03
*** sushils has quit IRC23:04
*** alejandro has joined #openstack-meeting23:06
*** alejandro has left #openstack-meeting23:08
*** kspear has quit IRC23:10
*** nati_ueno has joined #openstack-meeting23:10
*** markpeek has quit IRC23:11
*** colinmcnamara1 has joined #openstack-meeting23:19
*** colinmcnamara has quit IRC23:19
*** markmcclain has joined #openstack-meeting23:24
*** sungju has joined #openstack-meeting23:24
*** Swami has joined #openstack-meeting23:26
*** sungju has quit IRC23:27
*** sungju has joined #openstack-meeting23:27
*** alexxu has quit IRC23:28
*** colinmcnamara has joined #openstack-meeting23:30
*** colinmcnamara1 has quit IRC23:32
*** stevemar has joined #openstack-meeting23:33
*** tomoe_ has quit IRC23:33
*** mikal has quit IRC23:33
*** mikal has joined #openstack-meeting23:35
*** IlyaE has quit IRC23:37
*** colinmcnamara has quit IRC23:37
*** colinmcnamara has joined #openstack-meeting23:37
*** alexheneveld has quit IRC23:41
*** anniec has joined #openstack-meeting23:42
*** alexheneveld has joined #openstack-meeting23:46
*** seanrob has quit IRC23:49
*** seanrob has joined #openstack-meeting23:49
*** otherwiseguy has joined #openstack-meeting23:50
*** Swami has quit IRC23:54
*** seanrob has quit IRC23:54
*** jcru has quit IRC23:54
*** mdenny has quit IRC23:55
*** vkmc has joined #openstack-meeting23:57
*** gyee has quit IRC23:57

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