Tuesday, 2013-09-03

*** michchap has quit IRC00:01
*** michchap has joined #openstack-meeting00:01
*** stevemar has joined #openstack-meeting00:07
*** colinmcnamara has quit IRC00:08
*** epim has joined #openstack-meeting00:13
*** michchap has quit IRC00:13
*** primeministerp has joined #openstack-meeting00:14
*** michchap has joined #openstack-meeting00:14
*** danwent has joined #openstack-meeting00:16
*** epim has quit IRC00:17
*** danwent has quit IRC00:25
*** sushils has quit IRC00:26
*** epim has joined #openstack-meeting00:34
*** danwent has joined #openstack-meeting00:36
*** fnaval_ has joined #openstack-meeting00:38
*** derekh has quit IRC00:39
*** fnaval_ has quit IRC00:39
*** pcm__ has quit IRC00:42
*** stevebaker has left #openstack-meeting00:44
*** otherwiseguy has joined #openstack-meeting00:45
*** flaper87 is now known as flaper87|afk00:50
*** danwent has quit IRC00:51
*** salv-orlando has quit IRC00:51
*** stevebaker has joined #openstack-meeting00:53
*** danwent has joined #openstack-meeting00:54
*** jlucci has joined #openstack-meeting00:55
*** arosen1 has quit IRC00:56
*** arosen1 has joined #openstack-meeting00:57
*** zul has quit IRC00:57
*** zul has joined #openstack-meeting00:57
*** jlucci has quit IRC00:59
*** markmcclain has quit IRC01:01
*** ozstacker has quit IRC01:05
*** kevinconway has quit IRC01:13
*** mikal has quit IRC01:13
*** mikal has joined #openstack-meeting01:14
*** Mandell has joined #openstack-meeting01:15
*** arosen1 has quit IRC01:17
*** arosen1 has joined #openstack-meeting01:17
*** danwent has quit IRC01:19
*** ozstacker has joined #openstack-meeting01:24
*** dcramer_ has quit IRC01:26
*** yaguang has joined #openstack-meeting01:26
*** sjing has joined #openstack-meeting01:29
*** rdxc has quit IRC01:36
*** jlucci has joined #openstack-meeting01:42
*** marun has quit IRC01:55
*** dcramer_ has joined #openstack-meeting01:55
*** colinmcnamara has joined #openstack-meeting02:03
*** jlucci has quit IRC02:04
*** colinmcnamara has quit IRC02:07
*** nati_ueno has quit IRC02:09
*** nati_ueno has joined #openstack-meeting02:09
*** nati_ueno has quit IRC02:09
*** nati_ueno has joined #openstack-meeting02:10
*** stevemar has quit IRC02:15
*** egallen has quit IRC02:19
*** shang has joined #openstack-meeting02:20
*** shakayumi has quit IRC02:21
*** nati_ueno has quit IRC02:30
*** colinmcnamara has joined #openstack-meeting02:30
*** nati_ueno has joined #openstack-meeting02:30
*** nati_ueno has quit IRC02:35
*** radsy_ has joined #openstack-meeting02:37
*** radsy has quit IRC02:39
*** elo1 has joined #openstack-meeting02:43
*** elo1 has quit IRC02:43
*** elo1 has joined #openstack-meeting02:44
*** radsy_ is now known as radsy02:46
*** anteaya has quit IRC02:47
*** jlucci has joined #openstack-meeting02:48
*** kebray has joined #openstack-meeting02:50
*** terriyu has joined #openstack-meeting02:52
*** oubiwann has quit IRC02:59
*** garyk1 has joined #openstack-meeting02:59
*** nati_ueno has joined #openstack-meeting03:00
*** garyk has quit IRC03:00
*** oubiwann has joined #openstack-meeting03:02
*** oubiwann is now known as Guest6801503:02
*** epim_ has joined #openstack-meeting03:05
*** epim has quit IRC03:05
*** epim_ is now known as epim03:05
*** stevemar has joined #openstack-meeting03:06
*** nati_uen_ has joined #openstack-meeting03:06
*** nati_uen_ has quit IRC03:06
*** colinmcnamara has quit IRC03:06
*** nati_uen_ has joined #openstack-meeting03:06
*** colinmcnamara has joined #openstack-meeting03:07
*** colinmcnamara1 has joined #openstack-meeting03:08
*** colinmcnamara has quit IRC03:08
*** garyk1 has quit IRC03:08
*** nati_ueno has quit IRC03:09
*** garyk has joined #openstack-meeting03:18
*** dcramer_ has quit IRC03:27
*** nati_ueno has joined #openstack-meeting03:29
*** SergeyLukjanov has joined #openstack-meeting03:40
*** dosaboy has joined #openstack-meeting03:44
*** dosaboy_ has quit IRC03:47
*** marun has joined #openstack-meeting03:50
*** danwent has joined #openstack-meeting03:54
*** nati_ue__ has joined #openstack-meeting03:54
*** kebray has quit IRC03:55
*** dcramer_ has joined #openstack-meeting03:56
*** colinmcnamara1 has quit IRC03:57
*** nati_uen_ has quit IRC03:58
*** colinmcnamara has joined #openstack-meeting03:58
*** yaguang has quit IRC04:03
*** dcramer_ has quit IRC04:08
*** colinmcnamara has quit IRC04:09
*** danwent has quit IRC04:15
*** colinmcnamara has joined #openstack-meeting04:15
*** yaguang has joined #openstack-meeting04:16
*** markpeek has quit IRC04:32
*** garyk has quit IRC04:38
*** jlucci has quit IRC04:46
*** jlucci has joined #openstack-meeting04:47
*** boris-42 has joined #openstack-meeting04:54
*** radsy has quit IRC04:54
*** colinmcnamara has quit IRC05:05
*** iLikeIT has joined #openstack-meeting05:06
*** obondarev_ has joined #openstack-meeting05:12
*** iLikeIT has left #openstack-meeting05:13
*** SergeyLukjanov has quit IRC05:19
*** Mandell has quit IRC05:23
*** haomaiwang has joined #openstack-meeting05:28
*** obondarev_ has quit IRC05:28
*** haomaiwang has quit IRC05:42
*** haomaiwang has joined #openstack-meeting05:43
*** egallen has joined #openstack-meeting05:43
*** jhenner has joined #openstack-meeting05:50
*** hub_cap is now known as hubcap05:52
*** hubcap is now known as hub_cap05:53
*** jlucci has quit IRC05:54
*** hub_cap is now known as hubcap05:54
*** Mandell has joined #openstack-meeting05:54
*** hubcap is now known as hub_cap05:54
*** nati_ue__ has quit IRC05:56
*** arosen1 has quit IRC06:00
*** arosen1 has joined #openstack-meeting06:00
*** romcheg has joined #openstack-meeting06:04
*** romcheg has quit IRC06:07
*** garyk has joined #openstack-meeting06:08
*** arosen1 has left #openstack-meeting06:11
*** romcheg has joined #openstack-meeting06:16
*** egallen has quit IRC06:18
*** eglynn has joined #openstack-meeting06:19
*** haomaiwa_ has joined #openstack-meeting06:20
*** haomaiwang has quit IRC06:24
*** glikson has quit IRC06:30
*** doron_afk has joined #openstack-meeting06:31
*** romcheg has joined #openstack-meeting06:43
*** glikson has joined #openstack-meeting06:45
*** otherwiseguy has quit IRC06:45
*** flaper87|afk is now known as flaper8706:51
*** nati_ueno has quit IRC06:53
*** nati_ueno has joined #openstack-meeting06:53
*** eglynn has quit IRC06:54
*** tian has quit IRC06:56
*** mrunge has joined #openstack-meeting06:57
*** nati_ueno has quit IRC06:57
*** glikson_ has joined #openstack-meeting07:05
*** eglynn has joined #openstack-meeting07:06
*** romcheg has left #openstack-meeting07:06
*** glikson has quit IRC07:07
*** glikson_ is now known as glikson07:07
*** jhenner has quit IRC07:08
*** jhenner has joined #openstack-meeting07:09
*** jcoufal has joined #openstack-meeting07:09
*** jhenner has quit IRC07:11
*** jhenner has joined #openstack-meeting07:11
*** ndipanov has joined #openstack-meeting07:13
*** nati_ueno has joined #openstack-meeting07:17
*** boris-42 has quit IRC07:23
*** jaimegil has joined #openstack-meeting07:24
*** salv-orlando has joined #openstack-meeting07:30
*** IlyaE has quit IRC07:31
*** SergeyLukjanov has joined #openstack-meeting07:33
*** iLikeIT has joined #openstack-meeting07:35
*** iLikeIT has left #openstack-meeting07:37
*** comay has quit IRC07:39
*** jtomasek has joined #openstack-meeting07:41
*** Yada has joined #openstack-meeting07:49
*** sushils has joined #openstack-meeting07:57
*** glikson has quit IRC08:00
*** nati_ueno has quit IRC08:05
*** nati_ueno has joined #openstack-meeting08:05
*** nati_ueno has quit IRC08:09
*** yassine has joined #openstack-meeting08:10
*** pnavarro has joined #openstack-meeting08:14
*** yuan has joined #openstack-meeting08:17
*** jtomasek has quit IRC08:18
*** ruhe has joined #openstack-meeting08:19
*** jtomasek has joined #openstack-meeting08:19
*** derekh has joined #openstack-meeting08:21
*** johnthetubaguy has joined #openstack-meeting08:21
*** nati_ueno has joined #openstack-meeting08:22
*** iLikeIT has joined #openstack-meeting08:27
*** Mandell has quit IRC08:29
*** johnthetubaguy1 has joined #openstack-meeting08:33
*** complexmind has joined #openstack-meeting08:33
*** johnthetubaguy has quit IRC08:35
*** fifieldt has quit IRC08:35
*** SergeyLukjanov has quit IRC08:36
*** graflu0 has joined #openstack-meeting08:37
*** sjing has quit IRC08:37
*** T_rex has joined #openstack-meeting08:39
*** SergeyLukjanov has joined #openstack-meeting08:41
*** T_rex has quit IRC08:48
*** doron_afk is now known as doron08:49
*** boris-42 has joined #openstack-meeting08:50
*** doron is now known as doron_afk08:54
*** alexpilotti has joined #openstack-meeting09:01
*** doron_afk is now known as doron09:03
*** doron is now known as doron_afk09:07
*** nati_ueno has quit IRC09:07
*** nati_ueno has joined #openstack-meeting09:08
*** alexpilotti has quit IRC09:11
*** nati_ueno has quit IRC09:12
*** graflu0 has quit IRC09:12
*** glikson has joined #openstack-meeting09:19
*** nati_ueno has joined #openstack-meeting09:19
*** ocozalp has joined #openstack-meeting09:23
*** doron_afk is now known as doron09:23
*** ocozalp has left #openstack-meeting09:24
*** johnpur has quit IRC09:27
*** doron is now known as doron_afk09:30
*** glikson has quit IRC09:33
*** nati_ueno has quit IRC09:34
*** nati_ueno has joined #openstack-meeting09:35
*** nati_ueno has quit IRC09:35
*** ndipanov_ has joined #openstack-meeting09:37
*** doron_afk is now known as doron09:38
*** ndipanov has quit IRC09:38
*** alexpilotti has joined #openstack-meeting09:39
*** al-maisan_ is now known as al-maisan09:40
*** blamar has quit IRC09:45
*** Akendo_ has quit IRC09:48
*** dosaboy has quit IRC09:49
*** thomasbiege has joined #openstack-meeting09:49
*** lexx has joined #openstack-meeting09:51
*** dosaboy has joined #openstack-meeting09:51
*** thomasbiege has quit IRC09:56
*** doron is now known as doron_afk09:58
*** ruhe has quit IRC09:58
*** ndipanov_ has quit IRC10:01
*** ndipanov has joined #openstack-meeting10:02
*** ruhe has joined #openstack-meeting10:06
*** lexx has quit IRC10:07
*** matiu_ has quit IRC10:09
*** pcm_ has joined #openstack-meeting10:18
*** ruhe has quit IRC10:18
*** pcm_ has quit IRC10:18
*** pcm_ has joined #openstack-meeting10:19
*** SergeyLukjanov has quit IRC10:21
*** michchap has quit IRC10:27
*** sdague has joined #openstack-meeting10:32
*** yaguang has quit IRC10:33
*** SergeyLukjanov has joined #openstack-meeting10:34
*** SergeyLukjanov has quit IRC10:54
*** ruhe has joined #openstack-meeting10:54
*** radez_g0n3 is now known as radez10:57
*** michchap has joined #openstack-meeting10:58
*** SergeyLukjanov has joined #openstack-meeting11:02
*** boris-42 has quit IRC11:04
*** matiu has quit IRC11:05
*** michchap has quit IRC11:06
*** ccorrigan has quit IRC11:07
*** ccorrigan has joined #openstack-meeting11:08
*** flaper87 is now known as flaper87|afk11:16
*** ruhe has quit IRC11:18
*** shang has quit IRC11:27
*** flaper87|afk is now known as flaper8711:28
*** seagulls has quit IRC11:28
*** beagles has joined #openstack-meeting11:28
*** ruhe has joined #openstack-meeting11:32
*** pnavarro has quit IRC11:32
*** tedross has joined #openstack-meeting11:37
*** eglynn has quit IRC11:39
*** tedross has left #openstack-meeting11:41
*** flaper87 is now known as flaper87|afk11:41
*** rdxc has joined #openstack-meeting11:44
*** shakayumi has joined #openstack-meeting11:48
*** anteaya has joined #openstack-meeting11:53
*** yaguang has joined #openstack-meeting11:54
*** HenryG has quit IRC11:57
*** flaper87|afk is now known as flaper8711:58
*** noslzzp has joined #openstack-meeting12:05
*** yassine has quit IRC12:05
*** topol has joined #openstack-meeting12:08
*** SergeyLukjanov has quit IRC12:09
*** SergeyLukjanov has joined #openstack-meeting12:09
*** dkranz has quit IRC12:10
*** flaper87 is now known as flaper87|afk12:10
*** Mikhail has quit IRC12:18
*** yassine has joined #openstack-meeting12:19
*** shakayumi has quit IRC12:20
*** dprince has joined #openstack-meeting12:22
*** markmcclain has joined #openstack-meeting12:23
*** markmcclain has quit IRC12:24
*** jcoufal_ has joined #openstack-meeting12:30
*** jcoufal has quit IRC12:31
*** doron_afk is now known as doron12:32
*** yaguang has quit IRC12:35
*** jasondotstar has joined #openstack-meeting12:43
*** dvarga has joined #openstack-meeting12:43
*** eharney has joined #openstack-meeting12:46
*** annegentle_away is now known as annegentle12:46
*** jaimegil has quit IRC12:48
*** blamar has joined #openstack-meeting12:52
*** eharney has quit IRC12:54
*** lblanchard has joined #openstack-meeting12:54
*** pnavarro has joined #openstack-meeting13:01
*** ayoung has joined #openstack-meeting13:06
*** lpabon has joined #openstack-meeting13:07
*** flaper87|afk is now known as flaper8713:08
*** dkehn_away is now known as dkehn13:10
*** lbragstad has quit IRC13:11
*** neelashah has joined #openstack-meeting13:13
*** topol has quit IRC13:15
*** HenryG has joined #openstack-meeting13:16
*** adalbas has quit IRC13:17
*** kevinconway has joined #openstack-meeting13:18
*** adalbas has joined #openstack-meeting13:18
*** yassine has quit IRC13:19
*** michchap has joined #openstack-meeting13:20
*** ruhe has quit IRC13:20
*** eharney has joined #openstack-meeting13:25
*** bgorski has joined #openstack-meeting13:26
*** ruhe has joined #openstack-meeting13:31
*** ruhe has quit IRC13:32
*** sandywalsh has joined #openstack-meeting13:32
*** vkmc has joined #openstack-meeting13:33
*** sabeen has joined #openstack-meeting13:35
*** yassine has joined #openstack-meeting13:35
*** mrunge is now known as mrunge_afk13:37
*** vijendar has joined #openstack-meeting13:39
*** changbl has quit IRC13:43
*** ruhe has joined #openstack-meeting13:43
*** lbragstad has joined #openstack-meeting13:47
*** markmcclain has joined #openstack-meeting13:48
*** boris-42 has joined #openstack-meeting13:49
*** markpeek has joined #openstack-meeting13:50
*** sabeen has left #openstack-meeting13:50
*** burt has joined #openstack-meeting13:53
*** rwsu has joined #openstack-meeting13:53
*** ruhe has quit IRC13:54
*** markvan has joined #openstack-meeting14:01
*** yaguang has joined #openstack-meeting14:02
*** dcramer_ has joined #openstack-meeting14:04
*** mrodden has joined #openstack-meeting14:07
*** scott__ has quit IRC14:09
*** Guest92807 has quit IRC14:09
*** johnpur has joined #openstack-meeting14:10
*** Guest92807 has joined #openstack-meeting14:10
*** lblanchard1 has joined #openstack-meeting14:12
*** lpabon has quit IRC14:14
*** lblanchard has quit IRC14:14
*** johnpur has quit IRC14:25
*** scott__ has joined #openstack-meeting14:27
*** topol has joined #openstack-meeting14:28
*** cody-somerville has joined #openstack-meeting14:28
*** dkranz has joined #openstack-meeting14:28
*** tanisdl has joined #openstack-meeting14:29
*** doron is now known as doron_afk14:29
*** ruhe has joined #openstack-meeting14:29
*** galstrom_zzz is now known as galstrom14:30
*** tanisdl has quit IRC14:31
*** tanisdl has joined #openstack-meeting14:32
*** scott__ has quit IRC14:33
*** scott__ has joined #openstack-meeting14:34
*** scott__ has quit IRC14:37
*** scott__ has joined #openstack-meeting14:38
*** dscannell has joined #openstack-meeting14:38
*** scott__ has quit IRC14:40
*** scott__ has joined #openstack-meeting14:41
*** changbl has joined #openstack-meeting14:42
*** scott__ has quit IRC14:42
*** otherwiseguy has joined #openstack-meeting14:42
*** gokrokve has joined #openstack-meeting14:43
*** scott__ has joined #openstack-meeting14:43
*** sdake has joined #openstack-meeting14:43
*** sdake has quit IRC14:43
*** sdake has joined #openstack-meeting14:43
*** doron_afk is now known as doron14:44
*** flashgordon is now known as jog014:44
*** scott__ has quit IRC14:47
*** scott__ has joined #openstack-meeting14:49
*** epim has quit IRC14:49
*** scott__ has quit IRC14:50
*** tianst has joined #openstack-meeting14:51
*** scott__ has joined #openstack-meeting14:51
*** doron is now known as doron_afk14:53
*** n0ano has joined #openstack-meeting14:56
*** murkk has joined #openstack-meeting14:57
*** SergeyLukjanov has quit IRC14:57
*** glikson has joined #openstack-meeting14:58
*** danwent has joined #openstack-meeting14:59
*** IlyaE has joined #openstack-meeting14:59
*** schwicht has joined #openstack-meeting14:59
*** mrunge_afk has quit IRC14:59
*** briancline has joined #openstack-meeting15:00
n0anoAnyone here for the Scheduler meeting?15:00
*** jcoufal_ is now known as jcoufal15:00
*** mrodden has quit IRC15:01
garykyeah15:01
garykn0ano: maybe everyone is in a last minute rush to get their patches in by weds15:02
n0anoschedules (you should excuse the pun) will do that :-)15:02
garyk:)15:02
*** PhilDay has joined #openstack-meeting15:02
n0ano#startmeeting scheduler15:02
openstackMeeting started Tue Sep  3 15:02:51 2013 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: scheduler)"15:02
openstackThe meeting name has been set to 'scheduler'15:02
n0anowe can start the meeting, just on the off chance some others arrive15:03
PhilDaySure15:03
*** SergeyLukjanov has joined #openstack-meeting15:04
garykon the mail list you mentioned you wanted to speak about ideas for sessions at summit15:04
n0anoyeah, I thought maybe we should coordinate a little, see what ideas people have15:05
n0ano#topic session topics for the Icehouse summit15:05
*** openstack changes topic to "session topics for the Icehouse summit (Meeting topic: scheduler)"15:05
gliksonhi15:05
glikson'future of scheduler'? :-)15:05
garykcool. myself and a few colleagues have been discussing extending the image properties filter and would like to expand on this to be able to deploy templates15:05
n0anoone thought was should we have a big `futures` session to talk about long term directions15:05
n0anoglikson, looks like we're on the same page here15:06
garykthat is, have the image properties, couple with host support drive the scheduling decisions15:06
*** pentameter has joined #openstack-meeting15:06
gliksonanother candidate would be around scheduling policies15:07
PhilDayWould be good if we can avoid last year's crush of trying to do 11 subjects in one session15:07
n0anogaryk, seem like something close to what my group has been calling enhanced platform awareness15:07
*** euanh has joined #openstack-meeting15:07
garykn0can you please elaborate a little more on ethat15:07
PhilDayI think part of the reason it was hard to land soem changes in H was that they didn't really get enough time at the summit15:07
gliksonPhilDay: agree.. PTL sets the agenda, right?15:07
n0anoPhilDay, partly that was due to a lot of late submissions, if we can be more prompt this year it might be better15:07
garykthe instance group feature has been in the queue since the beginning of H.15:08
n0anoglikson, I would imagine there's also only so many sessions available, hard to fit everything in15:08
*** doron_afk is now known as doron15:08
gliksonn0ano: sure, so, it is also a matter of priorities15:09
garykthe last summit there were a ton of scheduling sessions. i think that we did well to collaborate on presenting the data.15:09
garykphil was instrumental in getting everyone together before and syncing15:09
*** debo_os has joined #openstack-meeting15:09
garyki hope that this time we will also have a platform to present ideas and discuss them15:09
gliksonI am not saying anything went wrong in Portland.. Just saying that maybe this time there will be more awareness.15:10
*** euanh has left #openstack-meeting15:10
PhilDayFeels like we need a session to bottom out the whole "to what extend should the scheduler depend on or just feed into celiometer" issue15:10
garykagreed.15:10
n0anoPhilDay, that's an important area that will warrant a separate session I belive15:10
gliksonPhilDay: yep, metrics, etc15:10
garykbut this is certainly something that we would need to try and sync with the ceilometer guys and have a combined session15:10
gliksonit could be also related to the question of using DB versus RPC versus whatever to keep/deliver metrics..15:11
debo_ossorry for joining the chat late - are we trying to use ceil for communicating the "state" that a scheduler can use later on or just for metrics15:11
n0anoSo I;m seeing at least - future directions, metrics(Ceilometer), image properties&host capabilities - at least 3 sessions so far15:11
gliksonn0ano: policies15:12
PhilDayDoes Future directiosn cover teh proposal from Boris et al ?15:12
*** wwallnrr__ has quit IRC15:12
n0anoglikson, oops, that's 4 - DB vs. fanout15:12
garykglikson: yeah, things we want to add to instances15:12
debo_os+115:12
gliksonalso would be good to revisit the topic of scheduling across nova/cinder/etc15:13
PhilDayI want to do a session on the pcloud / whole host stuff - only partially related to scheduler though15:13
garykPhilDay: i think that the performance is very important. Not sure if implementation details is where the discussion is at the moment (that is my two cents)15:13
PhilDay@garyk - sorry, not sure i follow ?15:14
*** kebray has joined #openstack-meeting15:14
garykPhilDay: in the few times we have spoken about boris's proposal the discussion seems to be drawn into the implementaion details. i think that there are design issues that we need to address first.15:15
n0anowell, the big design issues is fanout vs. DB, until we resolve that it hard to go any further15:15
*** litong has joined #openstack-meeting15:15
PhilDayOk, yes agreed. a shared view of the design is the key thing we need to come away with15:16
garykn0ano: agreed15:16
*** ruhe has quit IRC15:16
*** ndipanov has quit IRC15:16
garykboris-42: you around?15:16
boris-42yes I am here15:17
boris-42garyk ^15:17
boris-42whats up?15:17
*** ndipanov has joined #openstack-meeting15:17
n0anoboris-42, we're talking about potential summit sessions, are you planning on doing one on your scheduler proposal15:17
debo_osgaryk: +1 about hte design comments ....15:18
garyksame same. we are talking possible scheduler sessions ad the performance issue arose. i guess we should have a session on that too.15:18
boris-42n0ano yeah it will be nhice15:18
boris-42n0ano we are going to present real nubmers15:18
boris-42n0ano between current and our approaches15:18
*** jtomasek has quit IRC15:18
gliksonregarding DB versus fanout.. would it be feasible to keep both? e.g., with a separate HostManager implementation?15:19
boris-42there is no fanout15:19
boris-42w don't want to use fanaout at all15:19
doronguys, isn't the hong-kong sessions voting ended already, or is this for a different scope?15:19
n0anoboris-42, one issue is design vs. implementation, we're still lacking concensus on the basic design, how do we achieve that15:19
boris-42just another way to store in key value storage all information15:19
debo_osboris and I have started merging the 2 documents15:19
boris-42n0ano we already achive it15:20
boris-42n0ano but we should make some other cleanups15:20
debo_oshttps://docs.google.com/document/d/1cR3Fw9QPDVnqp4pMSusMwqNuB_6t-t_neFqgXA98-Ls/edit# and boris' implementation details into one15:20
boris-42n0ano to remove compute_nodes table and compute_nodes update15:20
n0anodoron, no, that's for presentations, working sessions are still open15:20
doronn0ano: thanks. I'd love to join15:20
n0anoboris-42, I'm not sure we have concensus, I think jog0 is still unconvinced at minimum15:21
boris-42n0ano we will show numbers from real deployment15:21
boris-42n0ano btw here is patch15:22
boris-42https://review.openstack.org/#/c/43151/15:22
boris-42that improves performance in safe way15:22
n0anonumbers are good but they don't trump all other considerations15:22
*** mrodden has joined #openstack-meeting15:22
n0anonote that I'm really Devil's Advocate here, I happen to mostly agree with you but I don't think everybody does15:23
*** yaguang has quit IRC15:23
garyki agree partially but there is a still a lot of cases to be discussed.15:24
n0anowhich is why I think real resolution will have to happen at the summit15:24
boris-42n0ano numbers that could be repeated are not just numbers15:25
garyki think if we have a session at the summit it will be great. number also help, but use cases and understanding the exact tests is also very important15:25
boris-42n0ano we are going to add new project Rally (that will be benchmark system for OS)15:25
n0anogaryk, +115:25
debo_oscan we have a list of requirements for the scheduker improvements from everyone and collate a bunch of approaches15:25
garykdebo_os: +115:26
boris-42+115:26
boris-42yes this should be done before session15:26
debo_oshave a etherpad for now15:26
debo_osyeah it needs to be done now15:26
garykthat is a good approach15:26
n0anoboris-42, curious about Rally, would like more info on that (but later)15:26
garykcoming with crystalized ideas will enable us to hash out the details15:27
*** ruhe has joined #openstack-meeting15:27
debo_osfor example one clear requirement is to make placement decisions based on cinder nova neutron15:28
*** michchap has quit IRC15:28
debo_osalso scheduler = placement + state machine to shedule15:28
*** michchap has joined #openstack-meeting15:28
debo_osif we can collect simple requirements and then hash out pre summit we might have conclusions by nov 815:29
*** colinmcnamara has joined #openstack-meeting15:29
n0anodebo_os, I think you're a little optmistic, if we can just get the requirements out before then I'd be happy (conclusions come later)15:29
PhilDay+1 to setting up either pads now for the set of sessions that non captures from this session (or maybe one pad to plan the sessions?)     If we can offer Russell a list of 4-5 scheduler session we want to have that might be a good way to avoid last year's problems15:30
debo_osn0ano: optimism is cheap ;)15:30
garykPhilDay: +115:30
n0anoPhilDay, I like the idea of 1 etherpad for planning, does someone want to signup for creating/maintaing that pad?15:30
garykone a practical level it would also be nice if we can get core reviewers to look at the various scheduling changes (some have been around for longer than forever)15:31
* n0ano would sing up but I'm on vacation for the next 2 months (eat your hearts out :-)15:31
*** jtomasek has joined #openstack-meeting15:31
PhilDaySure - I can set up the pad15:31
garykPhilDay: i am happy to help out to15:32
n0ano#action PhilDay to setup up scheduler planning etherpad for the Icehouse summit15:32
PhilDayThanks Gary15:32
n0ano#action `everyone` to maintain the planning pad15:32
*** vijendar has quit IRC15:33
*** thomasbiege has joined #openstack-meeting15:33
n0anolet's move on a little bit15:33
n0ano#topic multiple-scheduler-drivers15:33
*** openstack changes topic to "multiple-scheduler-drivers (Meeting topic: scheduler)"15:33
n0anoglikson, I believe there is some controvery on the mailing list about this, is there anything that can be done to resolve things?15:34
garyki like the idea :)15:34
gliksonSo, almost nothing left from the original idea -- but we did submit several small incremental patches which should not be controversial..15:34
gliksonat least based on my discussion with jog0 the other day15:35
n0anoso does that mean the ultimate design goal has changed?15:35
*** wolfdreamer has joined #openstack-meeting15:36
gliksonbasically improving the existing AggregateCoreFilter and AggregateRamFilter -- making the overriding mechanism generic, and then extending to additional filters/option types15:36
gliksonwell, the ultimate goal has not changed -- but the goal for Havana has15:36
n0anoso kind of a step wise progression, which doesn't sound all that bad, just takes a little longer15:36
gliksonthe rest requires discussion at the summit15:37
gliksonyep15:37
gliksonmuch longer :-)15:37
*** doron is now known as doron_afk15:37
n0anoglikson, refer back to the last action item, update the planning etherpad :-)15:37
*** gyee has joined #openstack-meeting15:37
gliksonyep, will certianly contribute to that15:37
n0anoOK, onward15:38
*** SumitNaiksatam has quit IRC15:38
n0ano#topic temporary moderator15:38
*** openstack changes topic to "temporary moderator (Meeting topic: scheduler)"15:38
*** markmcclain has quit IRC15:38
gliksonas a general thought.. I think it would be very helpful to engage people from core early.15:38
debo_os+115:38
n0anoNote this is my last meeting for 2 months, is there anyone willing to moderate this meeting while I'm gone?15:38
*** zz_Guest44086 is now known as leif15:39
*** complexmind has quit IRC15:39
*** leif is now known as Guest7181315:39
gliksoneven not having someone from core in this forum is not a good sign..15:39
*** gokrokve has quit IRC15:40
n0anoglikson, just incentive for all of us here to become core members :-)15:40
n0anoanyway, I don't need an answer right now, think about moderating this meeting, it's not that hard.15:41
n0ano#topic opens15:41
*** openstack changes topic to "opens (Meeting topic: scheduler)"15:41
*** thomasbiege has quit IRC15:41
n0anoAnyone have anything new they want to bring up today?15:41
*** topol has quit IRC15:41
garykn0ano: i can moderate whilst you are away15:42
n0anogaryk, excellent, tnx much15:42
garykn0ano: ok. from next week?15:42
n0ano#action garyk to moderate this meeting for the next 2 months, start on 9/1015:43
n0anoOK, hearing nothing else, let's close for today15:43
*** rnirmal has joined #openstack-meeting15:44
n0anotnx everyone, hopefully I'll see you all at the summit15:44
n0ano#endmeeting15:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:44
openstackMeeting ended Tue Sep  3 15:44:17 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-09-03-15.02.html15:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-09-03-15.02.txt15:44
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-09-03-15.02.log.html15:44
garykn0ano: enjoy the vacation (and try to stay out of trouble :))15:44
n0anomoi - of course, what could possibly go wrong during a month in Europe :-)15:45
garykenjoy!15:45
*** tianst has quit IRC15:47
*** debo_os has quit IRC15:47
*** tianst has joined #openstack-meeting15:48
*** tianst has quit IRC15:48
*** topol has joined #openstack-meeting15:48
gliksonPhilDay: there?15:48
*** doron_afk is now known as doron15:51
*** zehicle_at_dell has joined #openstack-meeting15:53
*** Yada_ has joined #openstack-meeting15:54
*** reed has joined #openstack-meeting15:54
*** Yada has quit IRC15:55
*** Yada_ is now known as Yada15:55
*** shang has joined #openstack-meeting15:56
*** hartsocks has joined #openstack-meeting15:56
*** glikson has quit IRC15:56
*** hartsocks has left #openstack-meeting15:57
*** schwicht has quit IRC15:57
*** colinmcnamara has quit IRC15:58
*** colinmcnamara has joined #openstack-meeting15:59
*** jcoufal has quit IRC15:59
*** hemna_ has joined #openstack-meeting16:00
*** hanrahat has joined #openstack-meeting16:00
*** ndipanov is now known as ndipanov_afk16:00
primeministerp#startmeeting hyper-v16:01
openstackMeeting started Tue Sep  3 16:01:27 2013 UTC and is due to finish in 60 minutes.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: hyper-v)"16:01
openstackThe meeting name has been set to 'hyper_v'16:01
primeministerphi everyone16:01
primeministerpwe'll wait a couple more minutes for the others to join16:01
zehicle_at_dellHey!16:02
primeministerphey rob16:02
*** vijendar has joined #openstack-meeting16:02
*** dcramer_ has quit IRC16:02
zehicle_at_dellHi Peter16:02
primeministerpback from vacation with a bang today16:03
primeministerp;)16:03
alexpilottihola16:03
primeministerphi alex16:04
primeministerpi know pedro's time is limited today16:04
primeministerpso if we can start16:05
*** michchap has quit IRC16:05
primeministerp#topic review backlog16:05
*** openstack changes topic to "review backlog (Meeting topic: hyper-v)"16:05
primeministerpso obviously we still have the problem of our backlog of reviews16:06
primeministerpand it looks like unless we get a priority bump on our blueprints16:06
primeministerpwe might not get them reviewed16:06
alexpilottiI'm frankly quite concerned about the situation16:07
primeministerpwell16:07
primeministerpso am i16:07
alexpilottithis will lead straight towards a fork for most drivers IMO16:07
alexpilottiwe are not the only ones in this situation16:07
*** markwash has quit IRC16:08
alexpilottibasically driver specific blueprints are marked as low priority16:08
primeministerphas there been any other discussion of this from the other hypervisors, like xen and vmare?16:08
alexpilottiin the ML there was already some discussion16:08
alexpilottiI forwarded you already some links16:08
primeministerpstill got 500+ to go16:08
alexpilottiin general look for "frustration" in the ML subjects and there are quite a few :-)16:08
*** schwicht has joined #openstack-meeting16:09
primeministerphahaha16:09
primeministerpthanks16:09
primeministerpunfortunately16:09
primeministerpi wish it was something different16:09
alexpilottilet me see if we can get Russell16:09
alexpilottirussellb: ping16:09
dansmithso16:11
russellbhey16:11
primeministerphey guys16:11
dansmithsomething has to be prioritized, right?16:11
primeministerpthanks for the time16:11
alexpilottihi ru16:11
alexpilottihi russellb16:11
primeministerpdansmith: obviously16:11
alexpilottiwe are not putting into discussion your hard work16:12
dansmithwe're merging crazy amounts of code, and reviewing even more16:12
alexpilottibtw thanks dansmith for the help on the WMIV2 one16:12
*** dosaboy has quit IRC16:12
alexpilottiat the moment, not even a single one of our Nova Bps got merged16:12
russellbhonestly, the root cause here is how much was delivered right at the end of the cycle16:12
*** beagles has quit IRC16:13
russellb(not just you, across the project)16:13
russellbreview bandwidth doesn't magically increase at the end :-)16:13
*** dosaboy has joined #openstack-meeting16:13
*** zaneb has quit IRC16:13
alexpilottisure, but blueprints can be retargetted16:13
russellbhm?16:13
alexpilottifor example by knowing the situation before we could have decided to move stuff to I16:13
alexpilottiinstead of running aroung on a gazillion reviews and blueprints for nothing16:14
*** boris-42 has quit IRC16:14
russellbthe blueprint list for h3 has been insane since mid-cycle16:14
russellband i sent multiple messages to the ML about this16:14
russellband brought it up many times in weekly meetings16:14
zehicle_at_dellis there an thought that some of the code may have to move to I if the backlog is not resolved?16:14
alexpilottiwell, somebody approved them16:14
russellbzehicle_at_dell: yes, whatever doesn't make it will move out16:14
russellbalexpilotti: an approval isn't a guarantee that it will make it16:15
alexpilottiso russellb, what is the realistically expectation for our stuff?16:15
russellbhopefully we can get your most important stuff, some of it probably won't make it16:15
russellbdue to being caught up with so many other things late in the dev cycle16:15
russellbi get that your v2 API stuff is important for platform support16:15
primeministerprussellb: is there possibilities of the others making it as a feature freeze exception?16:15
russellbthe others seem less likely16:15
russellbyou can apply16:16
russellbwill have to sort through how many applications there are16:16
alexpilottiwell WMI V2 is required for Nova to work on Hyper-V V216:16
russellbunderstood16:16
alexpilottisorry, on Hyper-V 2012 R216:16
russellbso that's a good candidate for an exception if it doesn't make it16:16
primeministerprussellb: unfortunately most of ours depend on that one16:16
alexpilottithe small ceilometer patch is required for… Ceilometer16:16
alexpilottithe rest is basically on cascade on the WMI V2 one16:17
russellbok.16:17
alexpilottiso we spent one month rebasing patches basically16:17
alexpilottithe WMI V2 one has been put as "high" in Neutron, for example16:17
*** beagles has joined #openstack-meeting16:17
alexpilottiwhile in Nova is just a "low" one among the rest16:18
alexpilottiand the WMI V2 is is just to have Nova running on the new Hyper-V16:18
dansmithI definitely understand the importance of that,16:18
alexpilottiso basically, we risk to end up having 0 new features in Havana16:18
russellbi told you V2 is a good candidate for an exception16:19
alexpilottias I wouldn't count compatibility as a feature16:19
russellbi think that one can make it at least16:19
russellbwell, ok.16:19
russellbthen the lesson is don't deliver at the end of the cycle :-)16:19
russellbor you're at risk of this happening16:19
alexpilottiJuly?16:19
russellbnot V2, the others16:19
russellbbut anyway16:20
alexpilottionly a couple of them got in late (as in Aug 21th)16:20
russellbwhat would you like me to do?16:20
alexpilottiexceptions would be great of course16:20
*** doron is now known as doron_afk16:20
alexpilottiall that stuff is simple 100% included in the driver16:20
russellbwe'll cross that bridge after feature freeze, you're welcome to apply16:20
alexpilottionly the API stuff it's outside16:20
*** martine has joined #openstack-meeting16:21
dansmithexceptions don't increase review bandwidth, and it has to be weighed against other stuff that also needs an exception, right?16:21
*** dkehn_ has joined #openstack-meeting16:21
*** martine is now known as martine_16:21
russellbdansmith: yeah, we'll have to wait to see what exception applications we get16:21
alexpilottiif "welcome to apply" means getting ignored, I don't think it's too useful16:21
primeministerpI'll second that statement16:21
russellbi'm not able to give an answer without having the other applications in front of me16:21
*** yassine has quit IRC16:22
primeministerprussellb: that's fair16:22
russellbjust raging at me isn't going to help :-)16:22
primeministerprussellb: not trying to rage at anyone16:22
dansmithI take offense at the suggestion that we'd ask you to apply just to ignore you16:22
alexpilottirussellb: I'm not raging at you :-)16:22
russellbbut i promise to review every application and give a response16:22
primeministerprussellb: just trying to find a resolution to our current situation16:22
russellbyou both suggesting that i would ignore you is pretty frustrating16:22
alexpilottinor I think that you should become the scapegoat of this situation16:22
*** doron_afk has quit IRC16:22
russellbi'm taking time out of one of the busiest days of the year to talk here16:22
*** dkehn has quit IRC16:22
russellbyet i'm ignoring?  come on.16:22
russellbanyway, i hope we can review some of your stuff16:23
russellbdefinitely want to get V2 in for you16:23
russellbthe rest, please apply for exceptions and we'll sort it out soon16:23
russellbthanks guys16:23
* russellb goes back to reviewing16:23
primeministerprussellb: thank you for your time16:23
alexpilottiadd please the ceilometer one16:23
primeministerprussellb: the intent wasn't to offend16:23
primeministerprussellb: dansmith: sorry if we did16:23
primeministerpok16:24
alexpilottiwell, back to the meeting16:24
primeministerpyep16:24
primeministerpso16:24
alexpilottiwhat I fear is that we're gonna have a fork16:24
alexpilottiall the stuff that won't make it, will go into our github repo16:25
alexpilottithe installer will be based on that16:25
*** johnthetubaguy1 is now known as johnthetubaguy16:25
primeministerpnot what i wanted16:25
alexpilottiand the same will probably happen for the other hypervisors16:25
alexpilottiI don't want this to happen16:25
alexpilottibut I don't see any way out16:25
*** zaneb has joined #openstack-meeting16:26
primeministerplet's wait a day or two, see where we stand then decide what needs a feature freeze request16:26
*** diogogmt has joined #openstack-meeting16:26
primeministerpand start that process16:26
*** obondarev has quit IRC16:26
alexpilottione day actually, as the freeze in on the 4th :-)16:27
hanrahati have a long term concern, too.  i don't think this was a case of late submissions.  the process is overwhelmed.  how does this get fixed in future releases... 'I' and beyond... i've followed the discussion about options, but there wasn't any resolution.16:27
primeministerphanrahat: that's a discussion above this meeting16:27
primeministerpthis is most likely going to be an issue next release too16:28
*** PhilDay has quit IRC16:28
primeministerpand not just for us16:28
*** ilyashakhat has quit IRC16:28
alexpilottithe solution IMO is increasing the review bandwidth16:29
alexpilottiwe're preparing a guy for this work16:29
alexpilottito do our part16:29
*** ilyashakhat has joined #openstack-meeting16:30
alexpilottithe other important part of the solution is not to approve so many blueprints16:30
alexpilottiif you already know you cannot make it16:30
alexpilottiand the last one is better communication with the blueprint owners16:30
primeministerpalexpilotti: i think there's always optisism that they will make it16:31
alexpilottisure, hope beer dies :-)16:31
alexpilottiloool16:31
alexpilottidamn autocorrector16:31
primeministerphaha16:31
primeministerpwas wondering what that meant16:31
alexpilottimeant "never"16:31
alexpilottiI see this as a positive sign ;-)16:32
primeministerpme too16:32
primeministerplet's move on then16:32
alexpilottiagree16:32
primeministerponly other thing i had was to talk puppet bits16:32
primeministerpbut luis didn't make it today16:32
primeministerpso I'll hold off on that, as I still have much to get cought up on.16:33
primeministerpso one other thing16:33
primeministerpto discuss is live-migration16:33
primeministerp#topic live-migration16:33
*** openstack changes topic to "live-migration (Meeting topic: hyper-v)"16:33
alexpilottithanks primeministerp16:34
primeministerpalexpilotti: you had something to add to this16:34
alexpilottiso there's a new cool feature added by vishy16:34
alexpilottiwhich most probably won't make it16:34
alexpilottibut as there was a chance to get a shot at it, we implemented it in Hyper-V anyway16:34
primeministerpgreat16:34
alexpilottilive-migration is a "host" snapshot of a VM16:35
alexpilottibasically, what we call snapshots in Hyper-V16:35
*** nati_ueno has joined #openstack-meeting16:35
*** nati_ueno has quit IRC16:35
alexpilottithe VM gets snapshotted, the image + memory dump uploaded in Glance16:35
alexpilottiand from there you can spawn new images out of it16:35
*** nati_ueno has joined #openstack-meeting16:35
alexpilottithe advantage is that VM boot time is almost 016:36
primeministerpso storing running state as an image16:36
*** markmcclain has joined #openstack-meeting16:36
*** adrian_otto has joined #openstack-meeting16:36
*** dkehn has joined #openstack-meeting16:36
alexpilottithink about VDI, possibly in conjunction with RemoteFX16:36
primeministerpyep16:36
primeministerpvery interesting use case for it16:36
alexpilottiyou can have running VDI images in a matter of 1-2 seconds16:36
alexpilottiand since a differential disk is used also for the snapshot disks16:37
*** dkehn_ has quit IRC16:37
primeministerpdisk image is tiny too16:37
alexpilottithere's basically no disk usage16:37
alexpilottiit's a great feature IMO16:38
alexpilottiit will not make it for a single reason:16:38
*** nati_ueno_2 has joined #openstack-meeting16:38
primeministerpbeing?16:38
alexpilottiit's not ready in libvirt / qemu16:38
primeministerpahh16:38
alexpilottias in the project, not the Nova driver16:38
primeministerpgot it16:38
alexpilottiwhile the APIs are perfectly working16:39
alexpilottibut they don't want to merge them as there's no driver implementing it16:39
alexpilottithat's why I gave a shot at it16:39
russellbfwiw guys, i'm going to have a design summit session on the general future of compute drivers in nova16:40
primeministerpgood thinking16:40
alexpilottirussellb: cool16:40
*** nati_ueno has quit IRC16:40
primeministerprussellb: great, i'm hoping to have team there, I'll make sure it's on the required viewing list16:40
alexpilottirussellb: since you are around, no chance I guess for the live-snapshot apis?16:40
russellbno16:41
*** ilyashakhat has quit IRC16:41
primeministerpalexpilotti: do we have anything else to discuss16:41
alexpilottirussellb: lol, I had to ask but I didn't have big hopes :-)16:41
alexpilottiprimeministerp: yes, the positive news, aka what merged:16:42
primeministerpalexpilotti: go for it16:42
*** ilyashakhat has joined #openstack-meeting16:42
alexpilottipnavarro's Cinder patch merged (yeiii)16:42
alexpilottitx pnavarro! :-)16:42
primeministerpalexpilotti: yes he brough me up to speed on that this morning16:42
*** Yada has quit IRC16:42
primeministerpthanks again pnavarro !16:42
alexpilotticeilometer merged16:42
primeministerpalso great news16:42
alexpilottiNeutron Hyper-V V2 merged16:43
*** nati_ueno_2 has quit IRC16:43
alexpilottia bunch of bug fixes16:43
alexpilottiand a bunch of Nova pieces16:43
alexpilottinone of them make an entire blueprint unfortunately yet16:43
primeministerpgotcha16:43
*** azcricketnut has joined #openstack-meeting16:43
alexpilottijohnthetubaguy was incredibly helpful yesterday and today in helping out with WMI V216:44
primeministerpjohnthetubaguy: thanks for the help!16:44
alexpilottiso we have one +2 to go for having this feature merged16:44
alexpilottiand basically this is it16:44
johnthetubaguyno worries, happy to help out16:44
zehicle_at_delllet me know when we're ready to talk on the Crowbar HyperV progress16:44
primeministerpzehicle_at_dell: we can add that as a topic as well16:45
primeministerplet's do it now16:45
zehicle_at_dellthanks16:45
primeministerp#topic crowbar/hyper-v16:45
*** openstack changes topic to "crowbar/hyper-v (Meeting topic: hyper-v)"16:45
alexpilottizehicle_at_dell: sure16:45
primeministerpzehicle_at_dell: the floor is yours16:45
zehicle_at_dellThere are a lot of pull requests in the queue for HyperV support16:45
*** gokrokve has joined #openstack-meeting16:46
alexpilottizehicle_at_dell: you mean our requests or pulls on our barclamp?16:46
*** nati_ueno has joined #openstack-meeting16:46
zehicle_at_dellboth16:46
*** fsargent-nyc is now known as fsargent16:47
zehicle_at_dellit looks like they are going to settle pretty soon16:47
zehicle_at_delland we're ready to branch and start the havana work in ernest16:47
alexpilottiok16:47
*** ociuhandu has joined #openstack-meeting16:47
*** azcricketnut has quit IRC16:48
alexpilottiwe merged lately some pulls on the Hyper-V barclamp16:48
zehicle_at_dellgreat!16:48
ociuhanduhy all, sorry for being late16:48
alexpilottibasically in the day we got them, afaik16:48
zehicle_at_dellfor Havana, we'll use PFS16:48
zehicle_at_dellso, we should be able to bring in the code even if it has not been through review & into trunk16:49
alexpilottiociuhandu: do you have some more details on the pulls on the Hyper-V barclamp?16:49
zehicle_at_dellthat's part of the goal - I think it would be easier to get reviews if you'd been able to show integratation16:49
ociuhanduyes, we have only 2 left, one for SSL and one that's from today, some code cleanuo16:50
alexpilottiintegration? as in having a CI framework in place?16:50
primeministerpalexpilotti: was that for me?16:51
*** enikanorov-w has quit IRC16:51
*** markwash has joined #openstack-meeting16:51
primeministerpalexpilotti: that last question?16:51
alexpilottino, for zehicle_at_dell16:51
alexpilottizehicle_at_dell: ping16:52
zehicle_at_dellsorry16:52
*** enikanorov-w has joined #openstack-meeting16:52
alexpilottinp!16:52
*** dims has joined #openstack-meeting16:52
zehicle_at_dellour primary goal has been to make sure they are not breaking other stuff16:52
zehicle_at_dellwe have people who shoudl be able to do that - I'll get them connected to you16:53
zehicle_at_dellthat's grizzly target'16:53
zehicle_at_dellbut I'm interested in migrating that work to Havana soon16:54
zehicle_at_dellbecause I think it will be easier to make adjstments and fast feedback16:54
alexpilottiok, that's not too complicated for us16:54
zehicle_at_dellso, expect a branch where we can work on Havana.  then we can target the hyperv code to your github16:54
alexpilottiok16:55
primeministerpzehicle_at_dell: perfect16:55
zehicle_at_dellthe key is that I want to align our internal tests, they need to be able to get a workable build16:55
zehicle_at_dellbecause they are not in a position to integtrate directly from the code16:55
alexpilottione question: let's say that some of the Havana stuff under review does not make it for Havana16:55
alexpilottido we still include it in Crowbar?16:55
zehicle_at_dellyes16:55
alexpilottigood16:55
primeministerpI agree to that statement16:56
zehicle_at_dellwe do that for advanced features, it's one of the reasons that we use PFS16:56
zehicle_at_dellbecause sometimes, you're working ahead of trunk16:56
zehicle_at_dell(esp w/ these backlogs)16:56
*** schwicht has quit IRC16:56
zehicle_at_dellIMHO, if we can show it's working against trunk on a multi-node system then it should be easier to get reviews to flow16:57
primeministerpzehicle_at_dell: agreed16:57
*** schwicht has joined #openstack-meeting16:57
primeministerpok guys we're coming to the end of our time16:57
alexpilottizehicle_at_dell (and primeministerp) how do you plan to organise the testing?16:57
zehicle_at_dellI know that there's a balance between the Grizzly work that's trying to land and getting Havana integrations16:57
primeministerpalexpilotti: that's still under discussion right now16:58
zehicle_at_dellI've been waiting for a green light from you that we've got a usable build16:58
zehicle_at_delland then have that team work 1x1 so that they can replicate your environemtn16:58
zehicle_at_dellfirst, they'll baseline that build w/ the defaults16:58
zehicle_at_delland then add in the HyperV parts in collabroation w/ you16:59
zehicle_at_dellI'm expecting that we'll create a doc in the process so the community can replicate the process16:59
alexpilotticool16:59
ociuhanduzehicle_at_dell: sounds great16:59
zehicle_at_delloriginally, I'd thought to do that w/ grizzly bits but I think we may want to consider Hanava16:59
primeministerpzehicle_at_dell: ideally we'll be able to share our test plans/cases as well16:59
zehicle_at_dellwhioch would be more helpful?17:00
primeministerpzehicle_at_dell: probably havana17:00
zehicle_at_dellprimeministerp: yes, that makes sense17:00
*** dachary has quit IRC17:00
zehicle_at_dell+1 on Havana.  We just have to get the baseline set17:00
zehicle_at_dellok, we're out of time.  this was helpful.  Thanks17:00
primeministerpok guys, let's free up the channel, we can continue the discussion int he hyper-v channel if necessary17:01
*** dachary has joined #openstack-meeting17:01
primeministerpthanks everyone17:01
primeministerp#endmeeting17:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:01
openstackMeeting ended Tue Sep  3 17:01:15 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-09-03-16.01.html17:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-09-03-16.01.txt17:01
alexpilottithank you! bye17:01
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-09-03-16.01.log.html17:01
ociuhanduthanks, bye17:02
*** elo has joined #openstack-meeting17:02
*** derekh has quit IRC17:02
*** sarob has joined #openstack-meeting17:05
*** garyk has quit IRC17:06
*** glikson has joined #openstack-meeting17:06
*** anteaya has quit IRC17:08
*** Yada has joined #openstack-meeting17:10
*** nati_uen_ has joined #openstack-meeting17:10
*** nati_ueno has quit IRC17:10
*** nati_ueno has joined #openstack-meeting17:11
*** SergeyLukjanov has quit IRC17:12
*** jcoufal has joined #openstack-meeting17:12
*** nati_ueno has quit IRC17:16
*** markpeek has quit IRC17:19
*** Mandell has joined #openstack-meeting17:21
*** lpabon has joined #openstack-meeting17:22
*** Yada has quit IRC17:25
*** HenryG has quit IRC17:25
*** markpeek has joined #openstack-meeting17:26
*** zehicle_at_dell has quit IRC17:27
*** sarob has quit IRC17:28
*** sarob has joined #openstack-meeting17:28
*** zehicle_at_dell has joined #openstack-meeting17:28
*** sarob has quit IRC17:33
*** jpich has joined #openstack-meeting17:35
*** johnpur has joined #openstack-meeting17:35
*** jmontemayor has joined #openstack-meeting17:36
*** colinmcnamara has quit IRC17:37
*** sarob has joined #openstack-meeting17:37
*** ocozalp has joined #openstack-meeting17:40
*** HenryG has joined #openstack-meeting17:42
*** adrian_otto has quit IRC17:43
*** SergeyLukjanov has joined #openstack-meeting17:45
*** garyk has joined #openstack-meeting17:50
*** johnpur has quit IRC17:50
*** shakayumi has joined #openstack-meeting17:52
*** johnpur has joined #openstack-meeting17:52
*** adrian_otto has joined #openstack-meeting17:54
*** bknudson has joined #openstack-meeting17:56
*** yjiang5_away is now known as yjiang517:57
*** boris-42 has joined #openstack-meeting17:58
ayoungLet's do this17:59
*** nachi has joined #openstack-meeting17:59
bknudsonhi18:00
morganfainbergo/18:00
*** henrynash has joined #openstack-meeting18:00
*** dolphm has joined #openstack-meeting18:00
dolphmo/18:00
*** jtomasek has quit IRC18:01
henrynashhi there18:01
gyee\018:01
gyeedolphm, is m3 cut, I don't see a tag18:01
morganfainbergmorning.  or afternoon…or whatever timezone greeting is proper18:01
dolphmgyee: nope18:01
ayounghttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Agenda_for_next_meeting for all that need the link18:01
lbragstadhey18:01
ayounggyee, Sept 418:02
dolphm ^18:02
gyee2morrow18:02
dolphmmilestone-proposed is cut today18:02
gyeeso stuff gets approved today can still make it18:02
ayoungyep18:03
ayounggyee, it better be ready and rock steady18:03
*** dstepanenko has joined #openstack-meeting18:03
gyeeyay!18:03
ayoungdolphm, want to start this thing?18:03
*** shang has quit IRC18:03
dolphm#startmeeting keystone18:03
openstackMeeting started Tue Sep  3 18:03:36 2013 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
bknudsonwhat happens after? still have master?18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: keystone)"18:03
openstackThe meeting name has been set to 'keystone'18:03
dolphmwas pizza'ing18:03
dolphm#topic feature freeze18:04
*** openstack changes topic to "feature freeze (Meeting topic: keystone)"18:04
topolhello just joined18:04
ayoungSo, I know we have henrynash 's Filter feature under discussion.  Before we get lost in that18:04
ayounganything else major that needs review18:04
gyeeayoung, how about nachi's generic signature auth plugin18:04
gyeewould be nice to get that one in18:05
dolphmHavana milestone 3 milestone-proposed is cut later today at which point features are late and a pain18:05
morganfainberghttps://review.openstack.org/#/c/43609/ if we want caching on assignment CRUD stuff (project, domain, role)18:05
dstepanenkoguys, what about centralized quota management in keystone? are we going to have it in havana?18:05
dolphmthe final milestone branch is cut tomorrow at which point feature freeze is in full effect18:05
*** syerrapragada has joined #openstack-meeting18:05
dolphmand that'll be representative of havana as a whole :D18:05
henrynashmorganfainberg: I approved that a short time ago18:05
gyeeyes, quota as well18:05
*** jamielennox has joined #openstack-meeting18:05
*** vijendar1 has joined #openstack-meeting18:05
morganfainberghenrynash, oh didn't see it. thanks18:05
*** vijendar has quit IRC18:05
*** syerrapragada has left #openstack-meeting18:05
ayoungdstepanenko, that one was close, as I recall18:05
ayoungpost your review links here18:06
*** SumitNaiksatam has joined #openstack-meeting18:06
dolphmdstepanenko: i missed thing meeting last week, but my understanding is that keystone-core felt it hadn't gotten enough attention during the milestone and wanted to postpone it18:06
dolphms/thing/the/18:06
*** ruhe has quit IRC18:06
dolphmi saw that someone retargetted it to havana-m318:06
ayoungdolphm, I thin the discussion was more than that18:06
ayoungit was under active development, and I was browbeating people into looking at it, IIRC18:06
dolphmayoung: can you summarize?18:07
gyeewould be nice to get someone from swift and nova to review the quota one as well18:07
dolphmgyee: ++18:07
ayoungdolphm, it is an extension, and needs to be disabled, but other than that, I thought it was pretty close18:07
gyeethey will be the first consumers I think18:07
dstepanenkodesign -  https://review.openstack.org/#/c/37545, db part of code https://review.openstack.org/#/c/44878/1, api part of code - https://review.openstack.org/#/c/4056818:07
*** garyk has quit IRC18:07
ayoungah..and needed the API review finished, too18:07
morganfainbergdstepanenko, i think there is only one question i have on the API spec.  how do user quotas fit in / use case for them.18:07
ayoungnever put commas at the end of your urls. Correct grammar be damned18:08
dstepanenkoactually, I split patchset into 2 parts so that we can review it separately18:08
morganfainbergdstepanenko, other than that, it looked good to me.  the patchsets were close imo18:08
dolphmayoung: my client handles it :)18:08
morganfainbergayoung, textual (my client) did the right thing :P18:08
stevemarayoung: youre on your own18:08
ayoungstevemar, I represent the non l33t masses18:09
stevemardstepaneko, there are tests missing for both patches18:09
dolphmas gyee suggested, i don't know if keystone-core can sufficiently represent the stakeholders of quota storage, so if we at least postpone it until icehouse-m1, that gives us some breathing room for stakeholder feedback to influence the api throughout icehouse18:09
dolphmwithout stringently requiring backwards compatibility with havana18:10
ayoungdstepanenko, that was not the review I remember...18:10
dstepanenkomorganfainberg I asked you via comments, but still admin can use user quotas for distributing resource between users. For example, admin can prevent some user use all the memory by creating as many cinder volumes as possible. In this case other users won't be able to create  their volumes because of memory exhaustion18:10
dstepanenkothis is first use case I see18:10
*** colinmcnamara has joined #openstack-meeting18:10
*** aepifanov has joined #openstack-meeting18:10
bknudsonwho's the stakeholders for quota storage?18:10
dstepanenkoactually, our customes have many others and asks us to implement this feature18:10
ayoungrussellb, can you chime in as a rep from Nova on whether quota's are a must have for Havana?18:11
dolphmbknudson: glance is the first on my radar18:11
*** debo_os has joined #openstack-meeting18:11
ayoungbknudson, swift, nova, cinder, and neutron all need quotas, but I don't think they will be able to consume it in the Havana time frame18:11
russellbquotas for what18:11
ayoungand glance...duh18:12
dolphmrussellb: centralized quota storage in keystone18:12
ayoungrussellb, the quoate storage in Keystone.18:12
russellbok18:12
bknudsonI wasn't sure if it was other openstack services or other users.18:12
russellbwell yeah, certainly can't consume anything new in havana at this point18:12
dolphm++18:12
russellbso, not important to nova to have in havana18:12
ayoungrussellb,  https://review.openstack.org/#/c/44878/1 and https://review.openstack.org/#/c/37545,18:12
ayoungdstepanenko, we ahve a lot of code that falls into that category.  Icehouse 1 is going to be a busy milestone release18:13
russellbfor that sort of thing, more important to land as early as possible in icehouse if you want it used in icehouse18:13
morganfainbergi think that was the general gist of the conversation from last week's meeting18:13
jamielennoxi think icehouse, there are still -1s on api and code18:14
stevemarjaimelennox ++18:14
ayoungdstepanenko, do you have any reason that it *has* to be in Icehouse?  Assuming we could commit it as soon as the Havana/Icehouse branch happens, would that suit your needs18:14
*** dstanek_ has joined #openstack-meeting18:14
*** zehicle_at_dell has quit IRC18:15
bknudsonif it was in icehouse-m1 it could be core rather than extension18:15
morganfainbergI would rather have a nice solid API spec that covers everything as well.  vs. something rushed that then has to maintain compat.18:16
dolphmbknudson: i think the featureset should be core, for now18:16
dstepanenkoayoung what concrete dates are we talking about?18:16
*** ocozalp has left #openstack-meeting18:16
*** zehicle_at_dell has joined #openstack-meeting18:16
morganfainbergthe spec is close, but still i think warrants some discussion to make sure it hits the usecases.18:16
ayoungdolphm, when do we open up for commits to Icehouse?18:17
jamielennoxbknudson, dolphm: core? why? what's wrong with it as an extension?18:17
dolphmdstepanenko: there's no concrete date ... it's whenever we've satisfied our release blocking bugs that release-proposed is created and master is re-opened for icehouse18:17
ayoungbknudson, Quota's should probably stay extension18:17
dolphmbknudson: ahh, should be an *extension*! my mistake18:18
dolphmjamielennox: ^18:18
ayoungdstepanenko, assuming we go based on the Grizzly example...18:18
*** vijendar has joined #openstack-meeting18:19
*** vijendar1 has quit IRC18:19
dolphmalright, i'm going to target it to 'next' until we have an icehouse-m1 to target18:20
*** vijendar has quit IRC18:20
ayoungdstepanenko, rc1 was tagged on  Mar 3118:20
*** vijendar has joined #openstack-meeting18:20
*** Mandell has quit IRC18:20
ayoungEr Mar 2218:20
dolphm#action dolphm to postpone https://blueprints.launchpad.net/keystone/+spec/store-quota-data until icehouse-m118:20
dolphm#action release blockers18:21
dolphmwhoops18:21
dolphm#topic release blockers18:21
*** openstack changes topic to "release blockers (Meeting topic: keystone)"18:21
dolphm#link https://launchpad.net/keystone/+milestone/havana-318:21
dstepanenkoayoung so 9 days passed between this 2 dates, right?18:21
dolphmI don't think any of the in progress bugs represent milestone release blockers? (if you feel otherwise, please correct me!)18:21
dolphmbut if any of those are unmerged by CoB today, i believe they should become release blockers for havana18:22
ayoungdstepanenko, longer than that, I think.  The g3 date was Feb21st18:22
henrynashdolphm: I'd like to try and fix #120148718:22
ayoungand RC was supposed to be Mar 14t18:22
dolphmayoung: you have two bugs that don't appear to be started18:22
henrynashdolphm: assigned to me anyway18:22
ayoung#link https://wiki.openstack.org/wiki/GrizzlyReleaseSchedule18:22
ayoungdolphm, I'll update.  Working on them.18:23
ayoungdon't think either will really upste things if they get defered18:23
henrynashdolphm: agreed18:23
dolphmhenrynash: i was looking at that earlier today... i'd love for that to be fixed18:23
henrynashdolphm: I'll fix it18:23
dolphmcurrent list of release blockers:18:24
dolphm#link https://launchpad.net/keystone/+milestone/havana-rc118:24
ayoungdolphm, should we discuss filtering?18:24
dolphmfeel free to tackle those or suggest more that should be added to the list! ^18:24
*** novas0x2a|laptop has quit IRC18:24
henrynashayoung: I think we should :-)18:24
dolphmsure, but one more thing from the agenda first...18:24
dolphm#topic Keystone-related documentation bugs18:25
*** openstack changes topic to "Keystone-related documentation bugs (Meeting topic: keystone)"18:25
dolphm#link https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=keystone18:25
dolphmthe DocImpact tag signifies you've merged a feature that should result in revised documentation. a bug is automatically filed and tagged with the relevant project...18:25
dolphmplease follow up on those bugs and revise the relevant docs18:26
dolphmthey're piling up on us, and keystone is only trailing nova in terms of the number of unresolved doc bugs18:26
jamielennoxthat's cool, i didn't know that18:26
morganfainbergah cool.18:27
ayounghenrynash, so, I've yet to see a solid explanation of why Filtering is safe, and without that, I am unwilling to put my name on it.18:27
morganfainberggood to know that's how that works.18:27
dolphm#topic code reviews for havana blueprints18:27
*** openstack changes topic to "code reviews for havana blueprints (Meeting topic: keystone)"18:27
henrynashdolphm: filtering?18:27
ayoungI'm willing to back off if some other core devs step up and are willing to vouch for it18:27
dolphmmorganfainberg: merge conflict https://review.openstack.org/#/c/43609/18:27
dolphmhenrynash: sure18:27
henrynashperhaps, first, I could summarises where we are18:27
*** johnthetubaguy has quit IRC18:27
*** haomaiwa_ has quit IRC18:27
morganfainbergdolphm, trying to resolve, can't connect to gerrit atm18:27
morganfainbergreview is just hanging.18:27
henrynashthere were 3 main issues raised in the review:18:28
dolphm#link https://review.openstack.org/#/c/43257/18:28
morganfainbergs/review/git review/18:28
henrynash1) list limiting was combined with filtering - Fixed by splitting them out so can review separately18:28
henrynash2) Controller-Driver contract was muddied and unclear, used url semantics etc. - Fixed (although needs review)18:29
henrynash3) …and potentially the thorny one….is it safe to use SQL Alchemy filtering if the "valuye" of the where clause comes from a url18:29
henrynashthe last one is the main issue that ayoung has18:29
*** Mandell has joined #openstack-meeting18:29
ayounghenrynash, yeah, although I still think that we are violating the H2 API freeze, but tha was dolphm 's burning platform, not mine18:30
*** dcramer_ has joined #openstack-meeting18:30
henrynashhow?18:30
dolphm.filter_by(column=value) ?18:30
stevemarmorganfainberg: he was just giving you a heads up to rebase 4360918:30
henrynashdolphm, yes18:30
jamielennoxi think issue 3 is ok so long as there is a hard upper limit on the number of returned items18:30
morganfainbergstevemar, nod.18:30
dolphmayoung: henrynash's change doesn't expose any new functionality to the api18:31
ayoungdolphm, I'll let you be the judge.18:31
gyeehenrynash, if you save the original query_dict in ListDirectives, you get my vote18:31
dolphmayoung: if you can perform filtering or anything against henry's change through the http api, please speak up and point it out18:31
henrynashgyee: the __init__() takes the quer_dict as a param and builds the list directive18:32
gyeehenrynash, I need to lookup the original one18:32
gyeehenrynash, self.query_dict = query_dict18:32
gyeethat's all I need :)18:32
dolphmgyee: for?18:33
gyeedolphm, I have some custom drivers18:33
dolphmgyee: drivers really shouldn't be consuming raw garbage from the http api18:34
henrynashgyee: and you use the query string to pass them data?18:34
gyeeyou only build query string from valid filters, I need to be able to extend it18:35
gyeeto support HP-specific filters18:35
*** ruhe has joined #openstack-meeting18:35
gyeecompetitive advantage, whatever :)18:35
dolphmgyee: can you present a use case for what you're solving for after the meeting?18:35
henrynashgyee: OK, let's discuss….but I'd like to get back to the BIG issue….of whether we are OK with using SQLA filtering18:35
gyeedolphm, k18:36
ayoungdolphm, are you comfortable with the current approach to the URL -> SQL transformation?  Do you feel like there has been sufficent Security review?  If so, add it to the review and I'll remove my -118:36
ayoungsame goes for any other core devs18:36
dolphmthere's no demonstrated vulnerability against sqlalchemy, so concerns about injection are just blather18:36
henrynashwhat I have done is included tests that try and break it by doing sql injection in the value field, so far it holds up18:37
bknudsonhenrynash: those tests are great.18:37
morganfainberghenrynash, fuzz testing? (I haven't looked closely at those tests)18:37
jamielennoxi think we should trust sqlalchemy's injection prevention, it's just a matter of checking that we use it all the time18:38
henrynashbknudson: I would;t call them a total sweep of sql injection…but it does appear that SQLA is protecting itself against it18:38
ayoungdolphm, not blather, just an attempt to make sure we are doing due diligence. I'm not saying there is an attack, just that we have confirmed that there is not one.18:38
*** elo has quit IRC18:38
morganfainbergif sqla had an injection vuln, i think we'd not be the only ones seeing it or affected by it. it seems to be fairly sane about param binding etc.18:38
*** ruhe has quit IRC18:38
ayoungor that we are appropriately using SqlA18:39
ayoungfine...I'll remove the -118:39
dolphmayoung: so ask for a review, investigate further, but blocking a review due to unjustified concerns doesn't make any sense18:39
morganfainbergif it really is a huge concern, we could have henrynash withhold the actual filtering peice to Icehouse 1, just pass the query strings down to the drivers?18:40
morganfainbergdrivers would do nothing unless someone implemented a filtering implementation.18:40
henrynashmorganfainberg: if we can show there IS a huge concern, I'd agree with that….I just haven't seen the evidence yet...18:41
morganfainbergthat would, give plenty of breathing room on security review and proper use of SqlA18:41
morganfainberghenrynash, i would agree, that is an if.18:41
dolphmthe assumption that filter parameters would come from the query string is (while reasonable), completely arbitrary and shouldn't be reflected in the driver interface18:41
henrynashmorganfainberg: it also means we can't limit the lists either (since you have to filter first before you limit)18:42
gyeesecurity is a process, software is a tool :)18:42
topolgyee +118:42
henrynashdolphm: is that a comment on the new implementation or a general one?18:42
morganfainberghenrynash, i am torn on the limit part, i don't like that the client has no knowledge of the limiting occuring, but defaulting it to off seems fine. (not a blocker imo)18:42
*** dprince has quit IRC18:43
ayoungI've removed the -1.18:43
dolphmhenrynash: in general18:43
henrynashdolphm: Ok :-) and agree18:43
henrynashdolphm: you convinced me of that18:43
dolphmmorganfainberg: i share that concern... but i understand a deployer wanting to set a reasonably high limit there (e.g. 1000)18:44
dolphmin fact... we used to have that feature in diablo18:44
dolphmit was dropped in essex and i haven't heard anyone complain18:44
*** dkehn is now known as dkehn_away18:44
henrynashdolphm, morganfainberg: and we default to off, here too of course18:44
henrynash(i.e no limit)18:45
dolphmhenrynash: setting a default limit *was* surprising though... so defaulting the feature to off should be mandatory18:45
morganfainberghenrynash, as long as it is unlimited by default, i see no reason to block it.  if an operator wants to limit, that really becomes an explicit choice at that point18:45
dolphmhenrynash: (i think the limit was 1000, which was super non-obvious when results were returned in a random order, sorted client-side, and a specific entry appeared in the middle of the resultset appeared to be missing)18:46
henrynashmorganfainberg: it is unlimited by default18:46
dolphm#topic open discussion18:46
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:46
bknudsonwhat's the version for havana (for use in man page, etc)? 2013.2?18:46
gyeedolphm, henrynash, I need to query_string saved so I can support provider-specific filtering18:47
*** jhenner has quit IRC18:47
dolphmi'm going to apologize right now -- i want to see RC1 go out the door happily bug free, so i'll be harassing keystone-core for bug fixes and reviews more than ever for the next couple weeks18:47
henrynashdolphm: more power to you18:47
dolphmmorganfainberg: gyee: henrynash: bknudson: ayoung: sorry!18:48
morganfainbergdolphm, hehe i'm ok with it18:48
dolphmmostly for reviews18:48
ayoungdolphm, fine by me18:48
topoldolphm no need to apologize.  being the leader means having to be tough :-)18:48
gyeeha, np, we'll be busy doing code reviews anyway18:48
bknudsonI hope it's bug free too.18:48
dolphmbug fixes will come out of the woodwork this time of year18:48
dolphmtopol: community-elected cat herder*18:49
gyeemeow18:49
topolyes, that too18:49
stevemarcat herding is tough business18:49
ayoungdolphm, Are we doing API freeze in I2?18:49
henrynashayoung:look ahead planning, I like it18:50
dolphmayoung: i'd like to discuss it again at the summit (did it work in havana? etc)18:50
topolayoung, I liked it as well.   Seemed like all of you were less stressed this time compared to the previous release18:50
dolphmayoung: assume yes based on precedent, but come to the summit with an opinion18:50
dolphmtopol: ++++++18:51
stevemartopol ++18:51
ayoungdolphm, OK,  so it is a wroking propsal, then?18:51
ayoungworking18:51
dolphmayoung: sure18:51
ayoungWe have a bunch of wrok poised for I1 already18:51
ayoungKDS, QUotas, etc18:51
*** zaro0508 has joined #openstack-meeting18:51
dolphmi think featureproposalfreeze was also awesome, and given a bit more notice, i'd like to do it a week in advance for m1 and m2, and then 2 weeks in advance of m318:51
gyeeand we're going to fix service catalog right?18:52
ayoungmight be nice to warn people that want things to go in , especially things that have already been discussed, like regions support18:52
ayoung"start now"18:52
*** novas0x2a|laptop has joined #openstack-meeting18:52
*** ociuhandu has quit IRC18:52
dolphmgyee: yeah, i'd like to have a summit session to architect GET /v3/catalog18:52
gyee+++++++++++++18:52
*** jmontemayor has quit IRC18:52
ayoungdolphm, would be nice to get the summit Keystone proposals posted.18:52
dolphm(cc: ayoung, morganfainberg) i filed a summit session on token revocation, mostly just so i could play with summit.openstack.org http://summit.openstack.org/cfp/details/518:53
morganfainbergdolphm, nice.18:53
ayoungdolphm, nice18:53
gyeewhat revocation?18:53
gyeewhat happen to short-lived tokens?18:53
ayounggyee, instead of posting a list of revoked tokens18:53
dolphmayoung: i also found this which makes me sad http://www.google.com/patents/US2013012522818:54
ayoungwe post a list of criteria for determining if a token is still valid18:54
gyeeoh, wtf?18:54
dolphmgyee: i wanted to put very-short-lived tokens on the list as a potential solution, but didn't see a bp for it18:54
morganfainbergdolphm, isn't that basically TOTP?18:54
morganfainbergoh oh18:54
morganfainbergthat is sad18:54
dolphmyeah18:54
topolwhy does the patent upset you?18:54
morganfainbergat least google has a history of being nice to OSS projects (as i recall)18:55
jamielennoxhow the hell did that get passed being filed in 2011?18:55
dolphmtopol: because it's patenting a viable solution to our token revocation woes18:55
ayoungdolphm, short lived tokens are not a stand alone feature.  I think that they are dependent on some other features.18:55
topolthere must be prior art that blow that patent out18:55
ayoungWe can pull that all together into one session, though18:55
topolits easy to get around patents18:56
stevemarmorganfainberg: it's not google though, its RIM18:56
ayoungdolphm, https://blueprints.launchpad.net/keystone/+spec/delegation-workplans18:56
morganfainbergstevemar, oh. misread.18:56
morganfainbergstevemar, crud.18:56
topolneed to look at its process (flowchart) and then have a different flowchart18:56
ayoungbascially, we need a way to tell a remote service "When the time comes to do something on my behalf, use this delgation mechanism"18:57
ayoungthen, a token doesn't ahve to live for the entire workflow18:57
topolthere must be prior art18:57
topoltoken revocation is not new18:58
morganfainbergayoung, agreed.18:58
stevemarsounds like topol is volunteering to do work/research :P18:58
*** dcaro has joined #openstack-meeting18:58
ayoungdolphm, so...maybe a session on the steps needed to reduce token lifespan, with both of those topics covered?18:59
*** jpeeler has quit IRC18:59
topolIll go read the patent. then you need to explain to me your solution. Ideally the flowcharts are different18:59
dolphmtopol: the filing is a bit specific, but it's basically a broadly scoped form of https://blueprints.launchpad.net/keystone/+spec/revocation-events18:59
*** jpeeler has joined #openstack-meeting18:59
stevemardolphm: can we get an icehouse-m1 tag in launchpad?18:59
dolphmayoung: start running devstack with a shorter default token duration :)18:59
dolphmayoung: and then make it shorter again18:59
stevemardolphm: and start targetting blueprints?19:00
gyeetill someone screams19:00
dolphmstevemar: that's up to ttx19:00
stevemarkk19:00
dolphmstevemar: rather, i think i could do that, but i don't want to step on ttx's toes19:00
jamielennoxthere is a crowd sourced forum somewhere that's job is to dig up prior art on patents19:00
stevemar:)19:00
*** HenryG has quit IRC19:00
ayoungnot too worried,  I don'19:00
dolphmstevemar: he probably has a script to do it for all projects at once19:01
morganfainbergjamielennox, it would be good to try and avoid that need.19:01
stevemardolphm: nudge ttx then :P19:01
ttxdolphm: I do have such a script yes19:01
dolphmstevemar: it's coming, i just couldn't tell you when19:01
ayoungt think that we are going to end up using that particualr method anyway19:01
jamielennoxmorganfainberg, of course19:01
stevemaranddd we're over19:01
*** nati_ueno has joined #openstack-meeting19:01
lbragstadthanks all19:01
dolphmahh19:01
dolphm#endmeeting19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Tue Sep  3 19:01:57 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-09-03-18.03.html19:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-09-03-18.03.txt19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-09-03-18.03.log.html19:02
* dolphm "stevemar: over what?"19:02
clarkbjeblair: o/19:02
jeblairhi infra folks!19:02
fungiahoy, mateys!19:02
mroddenhi19:03
*** jamielennox has left #openstack-meeting19:03
jeblair#startmeeting infra19:03
openstackMeeting started Tue Sep  3 19:03:22 2013 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
clarkbfungi: I really hope you spoke like that on the cruise19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
*** zyuan_ has joined #openstack-meeting19:03
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:03
*** adrian_otto1 has joined #openstack-meeting19:03
*** zyuan_ has left #openstack-meeting19:03
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-08-27-19.02.html19:03
fungiclarkb: only most of the time ;)19:03
*** adrian_otto1 has quit IRC19:03
jeblair#topic Operational issues update19:04
*** openstack changes topic to "Operational issues update (Meeting topic: infra)"19:04
jeblairi think this is kind of a non-topic at this point...19:04
jeblairexcept there are some folks back from vacation19:04
* fungi is very back, and very trying to catch up on what happened19:05
ttxo/19:05
*** bgorski has quit IRC19:05
jeblairso, maybe if fungi or sdague or anyone else has questions, we could cover what happened while they were gone19:05
clarkb++19:05
*** johnpur has quit IRC19:05
fungii think i grok most of what got done with the git.o.o fan out/ha19:05
fungilooks like additional slaves got added too19:06
fungianything else major last week?19:06
jeblairthe really short version is:  nodepool is stable and fast, git.o.o is stable and fast, static.o.o is stable and fast, and jenkins is still jenkins.19:06
sdagueI'm still in dig out mode, so I'll refrain from asking questions until I've gone through the relevant lists19:06
sdaguenice19:06
jeblairsdague, fungi: the summary from last week might be useful:19:07
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-08-27-19.02.log.html19:07
* fungi nods19:07
clarkbthere were also some changes to zuul19:07
*** adrian_otto has quit IRC19:07
clarkbincluding lots of bugfixes and a rolled back set of optmimzations that turned out to not help19:07
*** vijendar has quit IRC19:07
*** elo has joined #openstack-meeting19:07
ttxjeblair: was wondering... is it just calmer now, or are we processing so fast that the queue stays small ?19:08
clarkbthe test environment was not representative of production hence the miss on those optimizations19:08
jeblairyep.  it turns out having 30,000 refs in the zuul repo meant that when it fetch new changes it was slow.  we got rid of them.  we'll figure something out long term19:08
*** sushils has quit IRC19:08
*** jlucci has joined #openstack-meeting19:09
jeblairttx: i think we're seeing fairly typical load at this point (though not the atypically high load we saw around proposal freeze)19:09
*** otherwiseguy has quit IRC19:09
*** olaph has joined #openstack-meeting19:09
fungigot it. some sort of automated expiring/pruning of old zuul refs at some point i guess19:09
*** ayoung has quit IRC19:09
jeblairttx: i think the infra changes and the switch to testr has really sped things up19:09
*** jmontemayor has joined #openstack-meeting19:09
clarkbttx: jeblair: ya our slowest tests are under 30 minutes now19:10
fungiwow. that's a pretty amazing development19:10
jeblairi don't anticipate that we'll make any major changes this week (H3 is on friday)19:11
clarkb++19:11
fungithat'll hopefully give me a chance to catch up anyway19:11
ttxjeblair, clarkb awesome19:12
jeblairafter that, we have a disruptive change to zuul to add reporter support (which is pretty cool -- i think we'll be able to have it send summary email reports for the bitrot jobs)19:12
jeblair(disruptive in this case means graceful shutdown and momentary outage)19:12
jeblairwe want to further improve responsiveness by having all of the slaves be managed by nodepool19:13
fungino argument there19:13
jeblairand then i've been working on a new scheduler algorithm for zuul, which could speed up throughput even further19:13
fungiexcept special-purpose slaves maybe?19:13
jeblair(at the cost of using _even more_ test nodes)19:13
jeblairfungi: yep19:13
clarkbjeblair: the really nice thing about that zuul scheduling algorithm is it simplifies zuul's internals19:13
jeblair#link https://review.openstack.org/#/c/44346/19:13
jeblairyeah, so far (before tests), its +52 -135 lines of code19:14
jeblair(and docs)19:14
jeblairanything else on this topic?19:15
clarkbwe might want to consider scaling back git.o.o after the freeze19:15
*** dripton_ is now known as dripton19:15
jeblairyeah, after we figured out what was going on with packed-refs, it turns out it's a bit overbuilt.19:16
jeblair#link http://cacti.openstack.org/cacti/graph_view.php?action=tree&tree_id=219:16
jeblair#topic Backups19:17
*** openstack changes topic to "Backups (Meeting topic: infra)"19:17
jeblairclarkb: what's the latest?19:17
*** writerDiane has joined #openstack-meeting19:18
*** IlyaE has quit IRC19:18
*** thomasbiege1 has joined #openstack-meeting19:18
clarkb#link https://review.openstack.org/#/c/44129/19:18
clarkbnow that people are back from vacation that can get another review. Backups are in place on etherpad(-dev) and review(-dev) if you want to look at them19:19
clarkbfungi: ^19:19
fungiclarkb: added to the top of my reading lisr19:19
fungilist19:19
clarkbonce that change merges (I hope to merge it today) next step is getting bup running on those hosts so that the backups end up offsite19:19
*** bknudson has left #openstack-meeting19:19
clarkber backups are not in place on review.o.o yet, just review-dev19:19
clarkb44129 adds mysql backups to review.o.o and wiki.o.o19:20
clarkbhopefully by the time the next meeting rolls around we will have proper mysql backups for these hosts19:20
*** zul has quit IRC19:21
jeblairyay!  that sounds so professional!  :)19:21
jeblair#topic Asterisk server19:22
*** openstack changes topic to "Asterisk server (Meeting topic: infra)"19:22
jeblairrussellb: ping19:22
russellbpong19:22
jeblairso i spun up like lots of asterisk servers19:22
*** ayoung has joined #openstack-meeting19:22
jeblairnow i think we just need to schedule a time to dial into (some of?) them and see if we notice a difference in quality19:22
russellbOK, sounds like a plan.19:23
russellbtoday and tomorrow are not good for me ...19:23
russellbother than that, most days are as good as any other19:23
*** anteaya has joined #openstack-meeting19:23
russellb(feature freeze rush)19:23
jeblairokay, maybe friday morning then?  or we can wait till next week if it would be better19:23
russellbfriday is OK19:23
clarkbfriday works for me19:24
russellblooks like i have a meeting at 11 AM Eastern19:24
russellbso anything outside of that hour is fine19:24
jeblair10am pacific, 1pm eastern (17 utc) ?19:25
russellbwfm19:25
fungisounds good to me19:25
*** lsmola_ has joined #openstack-meeting19:25
jeblair#action jeblair send email about asterisk testing friday, 1700 utc19:25
jeblairthanks!19:25
jeblair#topic puppet-dashboard (pleia2, anteaya)19:26
*** openstack changes topic to "puppet-dashboard (pleia2, anteaya) (Meeting topic: infra)"19:26
pleia2anteaya: joined just in time!19:26
anteayayay phone guy19:26
anteayago pleia219:26
pleia2so last week the puppet-dashboard server filled up, and we decided that instead of rescuing it again we should just finally reinstall it on a new (non-legacy) server19:26
*** ocozalp has joined #openstack-meeting19:27
pleia2#link https://bugs.launchpad.net/openstack-ci/+bug/121863119:27
uvirtbotLaunchpad bug 1218631 in openstack-ci "Build new puppet-dashboard server" [Undecided,New]19:27
*** ocozalp has left #openstack-meeting19:27
pleia2anteaya outlined our options in a comment from this morning19:27
pleia2#1 is the easiest, anteaya is suggesting #2 - discuss! :)19:28
jeblairi like easy and supported19:28
pleia2that's not an option19:28
pleia2so #2 requires a different version of ruby than what ships with precise, which makes it tricky19:29
jeblairugh19:29
clarkbdoesn't precise offer both 1.8 and 1.9?19:29
pleia2anteaya: or will it work on 1.8.7?19:29
anteaya#1 just takes us back into the same pigeon holes that we have now, that ended up with a broken dashboard19:29
pleia2clarkb: oh, if it does it would be nice, let's see...19:29
*** johnpur has joined #openstack-meeting19:29
anteaya#2 will work on 1.8.719:29
jeblairanteaya: i think we ended up with a broken dashboard because we didn't delete old stuff19:30
anteayaI don't recommend 1.8.7, but #2 option will work on it19:30
*** gyee has quit IRC19:30
clarkblooks like 1.9.1 is on precise with some 1.9.319:30
jeblair#2 is worth considering in case there's a security problem with the dashboard itself, it would be nice to have an upgrade channel there19:30
anteayajeblair: yes, because the db optimization rake task is really unique, and broke our db at least once19:30
fungiprecise offers ruby 1.9.3.0 in its ruby1.9.1 package19:30
pleia2anteaya: oh ok, I think I misread but now rereading it I do see that you said 1.8.7 would work19:30
anteayaso we didn't run the db optimizaation task again19:30
jeblairanteaya: that wasn't my understanding at all.19:30
clarkbfungi: nice19:31
anteayajeblair: okay, what did you understand?19:31
jeblairanteaya: but perhaps it's not worth going into, if we all agree that we want to run the sodabrew fork for other reasons19:31
anteaya1.8.7 will work with sodabrew19:31
*** nachi has left #openstack-meeting19:32
anteayaI lean heavily toward 1.9.3 but 1.8.7 will work with it19:32
clarkbI think we should run the fork for the reason jeblair lists. And I think we should be able to run it with either version of ruby19:32
jeblairanteaya: why 193?19:32
*** thomasbiege1 has quit IRC19:32
anteayait is being heavily supported by the ruby community and 1.8.7 has bascially been end of lifed19:32
anteayaI can't speel19:32
anteayaspell19:32
anteayaclarkb: +19:33
*** hanrahat has quit IRC19:33
jeblairas long as canonical are supporting 187, it's not a big deal, but it seems they're supporting both, so that's not much of a tiebreaker19:33
*** zul has joined #openstack-meeting19:33
jeblair187 means it may perhaps share more puppet configuration with our other hosts...19:33
*** trey_h has joined #openstack-meeting19:33
pleia2jeblair: +119:33
jeblairi worry a little about the puppet needed in order to have a different ruby version on one (puppet-managed) host19:34
anteayain terms of selected which of the 4 options, no not a tiebreaker19:34
fungiworth speculating... will running dashboard under 1.9.3 and generating puppet reports from machines using 1.8.7 work? i had gotten the impression puppet used some ruby-specific data types in its reports which changed starting in 1.9.1 which was part of the issue i ran into puppeting fedora 1819:34
clarkbfungi: oh interesting19:34
jeblairfungi: gah!19:34
clarkbfungi: it does use yaml which supports serializing objects19:34
anteayafungi: I haven't heard of this19:34
clarkbfwiw I think we do need to start thinking long term about using newer puppet19:35
anteayabut if it is true, I second jeblair "gah!"19:35
anteayaclarkb: or newer provisioning19:35
fungianteaya: i'll dig up my old notes. puppet report in puppet 2.7 wouldn't work with the ruby 1.9.3 on fedora 18 as a result19:35
jeblairhere's how i'm leaning: sodabrew with 187, so that there's less work to stand it up, and it is similar to the rest of the hosts.19:35
anteayafungi: okay, and yes I would like to see your notes once you find them19:36
*** megan_w has joined #openstack-meeting19:36
jeblairand hopefully that tides us over until we have newer puppet (+ newer ruby, presumably)19:36
pleia2jeblair: +1, and re-evaluate once we start moving to puppet3 and newer ruby19:36
clarkbjeblair: ++19:36
anteayawfm19:36
jeblairand if something comes up, we can probably upgrade that host to 193 if necessary19:36
fungianteaya: several ruby 1.9.3 fixes were added in puppet 3 and never backported to 2.7 was the gist19:36
anteayajeblair: hopefully yes19:36
pleia2the next Ubuntu LTS comes out in 8 months, so that's a nice target and it will have newer ruby19:36
anteayafungi: ah that sounds about right19:37
pleia2so, the next question is how we want to pull in sodabrew fork19:37
pleia2vcsrepo trunk?19:37
anteayayay new Ubuntu LTS19:37
jeblairpleia2: i think so, unless they're building .debs?19:37
pleia2no debs as far as I could see19:37
clarkbif they have tagged releases we could vcsrepo on those19:38
pleia2clarkb: I looked at the tagged releases, they are all old19:38
clarkbin that case trunk :) or maybe a specific commit off of trunk19:38
pleia2ok, I'll work with anteaya to get this rolling19:39
anteayasounds good19:39
*** sacharya has joined #openstack-meeting19:39
jeblaircool, thanks!19:40
jeblair#topic Bug day on Tuesday September 10th at 1700UTC19:40
*** openstack changes topic to "Bug day on Tuesday September 10th at 1700UTC (Meeting topic: infra)"19:40
pleia2that's just an announcement really19:40
jeblairtsia? :)19:40
pleia2over 170 bugs right now, lots of new we should browse through19:40
jeblairthat's the second day of the doc sprint, but i believe i'll be around19:41
jeblairs/sprint/bootcamp/19:41
clarkbpleia2: will you be attending that too19:41
clarkb?19:41
pleia2clarkb: wasn't planning on it19:41
*** vipul is now known as vipul-away19:41
jeblairi'm doing some speaking the first day19:41
jeblairabout automation, etc19:41
clarkbcool, was going to suggest maybe moving it if more than jeblair was going to be there19:41
clarkbbut  Ithink we will get by :)19:42
pleia2yeah, we can ping him about specific updates as needed19:42
jeblairi don't expect to attend the second day19:42
jeblair(though that may change)19:42
pleia2ok19:42
*** vijendar has joined #openstack-meeting19:42
annegentlebug day! Woohoo!19:42
*** sarob_ has joined #openstack-meeting19:43
jeblairbig day19:43
annegentletoo bad it overlaps19:43
annegentleyeah19:43
* ttx should add a bug counter for infra19:43
anteayattx file a bug report19:43
ttxtoo bad damn Launchpad does not do stats all by itself19:43
fungittx: we don't want to break your gauge19:43
ttx(hint hint)19:43
jeblair#topic Open discussion19:43
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:43
ttxsummit.o.o is up for icehouse summit, still running manually on top of openstack-infra/odsreg code... haven't had time to complete infra migration there unfortunately. Will be announced tomorrow.19:43
annegentleo/19:43
annegentlejust wanted to see who all from infra will be at doc boot camp19:44
*** dcaro has quit IRC19:44
annegentlewe're getting the first of the new tshirt design19:44
jeblairttx: it's at least heading in the right direction19:44
jeblairttx: when are the elections?19:44
mroddenoh i had a question... was there any more discussion on the pypi mirror stuff?19:44
ttxjeblair: it also now has the feature to handle "absence of summit" gracefully, so it's almost there19:44
anteayaannegentle: you have shirts for your bootcamp?19:44
jeblairannegentle: i'll be there for the 1st day, at least, second if you need me19:44
clarkbttx: does that host need mysql backups as well? we could potentially start with a little puppet to do that19:44
mroddenrsync vs lmirror ... etc19:44
annegentleanteaya: not for the bootcamp specifically but openstack tshirts19:45
anteayaannegentle: ah okay19:45
ttxclarkb: it does need backup, although it runs on sqlite atm19:45
pleia2annegentle: I wasn't planning on attending during the days, but I'm local-ish (SF) so if folks are meeting for an evening meal I'd love to visit19:45
ttxclarkb: I run manual backup informally19:45
clarkbttx: ok19:45
annegentlejeblair: thanks19:45
*** sarob has quit IRC19:45
annegentlepleia2: you are welcome to join us Monday evening19:45
ttxclarkb: like I said, I just missed 2 weeks to finalize it properly :/19:45
clarkbmrodden: no, I don't think that has been brought up again. We have been busy making everything else work19:45
pleia2annegentle: great, I'll be in touch for time/location19:46
annegentlepleia2: and actually I'd love another local driver if you're avaialble19:46
pleia2annegentle: my husband has our car on weekdays, but he works in mt view so I'll see what I can do and let you know19:46
*** elo has quit IRC19:46
*** amitgandhi has joined #openstack-meeting19:46
annegentlepleia2: thanks!19:47
clarkbmrodden: there is still a need for other folks to build a repository locally? I feel like leanign towards more general mirror building scripts might be the least painful way to do that19:47
*** sarob_ has quit IRC19:47
*** ndipanov_afk is now known as ndipanov19:47
pleia2re: this week, I'm going to be out Wednesday evening - Thursday, but I'll be back Friday :)19:47
mroddenclarkb: i have one i run internally behind teh firewall19:48
mroddenand more importantly "on-site"19:48
jeblair#link http://amo-probos.org/post/1519:48
mroddenits a bunch of scripts i threw together...19:48
jeblairI wrote a blog post about some of the zuul/jenkins-related system changes we made over the past year19:48
anteayayay19:48
jeblairfungi, sdague: ^ more catch-up reading if you want19:48
fungiadded19:49
pleia2jeblair: nice!19:49
clarkbmrodden: we have scripts too :) but lifeless doesn't like that they come with a lot of dependencies. We are working on splitting them into their own project19:49
*** vijendar has quit IRC19:49
sdaguejeblair: will check out19:49
clarkbI think mordred deleted the old project that had the pypimirror name19:49
clarkbwe should be able to start working on that transition now19:49
*** otherwiseguy has joined #openstack-meeting19:49
*** kgriffs has joined #openstack-meeting19:49
mroddenclarkb: oh... i have that change to re-create so we can move run_mirror.py over19:49
mroddenit probably was auto-abandoned19:50
jeblairmrodden: ah yeah, we should be able to merge that now if you want to restore it19:50
mroddenhttps://review.openstack.org/#/c/39399/19:50
mroddenrestored19:51
clarkbcool, I will take another look at that change. it may need ar ebase19:51
clarkbmrodden: maybe you want to test if it is mergable locally and rebase if necessary?19:51
*** IlyaE has joined #openstack-meeting19:51
mroddenclarkb: will do. i have some other fires i'm working on at the moment, but i'll try to get to it...19:51
*** danwent has quit IRC19:52
clarkbI plan on updating the openstack infra publications talk with logstash info (I am giving that talk at openstack on ales at the end of the month) are there other things people would like to be added to that?19:52
clarkbjeblair: fungi ^19:52
jeblairclarkb: the overview talk?19:53
clarkbjeblair: ya19:53
jeblairclarkb: cool19:53
*** jlucci has quit IRC19:53
fungiahh, that one19:53
pleia2it would be nice to get publications in general sorted so people can access them (and I'd like to add mine)19:53
*** lblanchard1 has quit IRC19:53
pleia2via the web19:53
clarkbpleia2: I think that may have gotten sorted out19:53
fungii think the index generation job/script may still be broken19:54
pleia2http://docs.openstack.org/infra/publications/ still is Forbidden19:54
fungii haven't dug into it other than to confirm it seemed not to generate an index.html in there19:54
*** shardy has joined #openstack-meeting19:54
clarkbpleia2: append overview to that and it works so you can at least directly link19:54
pleia2clarkb: that's just one talk19:54
pleia2we have lots of slides19:54
clarkbI can look into the index.html when modifying the talk19:54
*** zyuan_ has joined #openstack-meeting19:55
pleia2the index page should create a listing of all the slide decks, including /overview19:55
fungithat would be greatly appreciated19:55
clarkbok, added to the list19:55
pleia2thanks19:55
fungipleia2: the script tries to, at least. probably something trivial missing19:55
pleia2and I could use instructions for adding my talk, maybe something to add to ci.openstack.org19:55
pleia2fungi: *nods*19:55
clarkbpleia2: good idea19:55
clarkbI can do that too19:55
pleia2you rock \o/19:56
*** colinmcnamara has left #openstack-meeting19:57
*** zehicle_at_dell has quit IRC19:57
jeblairthanks everyone!  talk to you friday, i hope.  :)19:57
*** lpabon has quit IRC19:57
jeblair#endmeeting19:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:58
openstackMeeting ended Tue Sep  3 19:58:00 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-09-03-19.03.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-09-03-19.03.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-09-03-19.03.log.html19:58
*** zehicle_at_dell has joined #openstack-meeting19:58
*** oz_akan_ has joined #openstack-meeting19:59
*** ametts has joined #openstack-meeting19:59
ttxWho is around for the TC meeting ?20:00
mikalMoi20:00
ttxrussellb, shardy, jd__, dolphm, annegentle, mordred, notmyname, markwash, jgriffith, vishy, gabrielhurley, markmcclain: around ?20:00
russellbhi20:00
ttxNB: markmc is proxied by russellb20:00
annegentlehey o20:00
shardyo/20:00
*** gabrielhurley has joined #openstack-meeting20:00
jgriffithavishay: ttx o/20:00
*** johnpur has quit IRC20:00
jgriffitherrr20:00
jgriffith:)20:00
gabrielhurley\o20:00
*** vipul-away is now known as vipul20:01
dolphmo/20:01
ttx8 members, looks like we have quorum20:01
markwasho/20:01
ttxand more20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Sep  3 20:01:42 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: tc)"20:01
openstackThe meeting name has been set to 'tc'20:01
ttxOur agenda:20:01
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:01
ttxI suspect we'll probably to next week20:02
*** olaph has left #openstack-meeting20:02
ttxerr20:02
jd__o/20:02
ttxs/probably/overflow/20:02
hub_cap:)20:02
ttx#topic Marconi incubation request: final discussion20:02
*** openstack changes topic to "Marconi incubation request: final discussion (Meeting topic: tc)"20:02
flaper87\o/20:02
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-August/014076.html20:02
*** johnpur has joined #openstack-meeting20:02
markmcclaino/20:02
ttx#link https://wiki.openstack.org/wiki/Marconi/Incubation20:02
russellboh, i'm proxying for markmc20:02
russellbbtw.20:03
ttxrussellb: 2 votes! power to you !20:03
russellbyeah!20:03
ttxI think last week we covered Marconi scope questions, like:20:03
ttx- Marconi is a queuing service itself, not a provisioning service for some other queue software20:03
*** johnpur has quit IRC20:03
ttx- Marconi shall provide alternatives to MongoDB on the storage backend, but ideally keep the user-facing API(s) consistent20:03
flaper87We put together a Q&A section in MArconi's incubation page: https://wiki.openstack.org/wiki/Marconi/Incubation#Raised_Questions_.2B_Answers20:03
*** danwent has joined #openstack-meeting20:04
ttxflaper87: just read that, it's pretty nice20:04
ttxI wanted us to discuss integration points with other projects.20:04
flaper87+120:04
ttxObviously you will integrate with Keystone, I suspect you'll appear in Horizon at some point too...20:04
kgriffssure thing20:04
flaper87ttx: we already support keystone20:04
ttxYour wiki page mentions running on Nova servers, behind "OpenStack load balancers" -- Neutron LBaaS stuff, or somethign else ?20:04
kgriffsre Horizon, I could see it being helpful to see queue stats, create/delete queues, a few management things like that, so20:04
kgriffsttx: LBaaS20:05
ttxkgriffs: What about using Heat vs. using Nova directly ?20:05
russellband it doesn't use nova directly does it?20:05
russellbare you saying that it's possible to deploy on top of nova?20:05
russellbas opposed to specific integration?20:05
*** Guest71813 is now known as zz_Guest7181320:06
kgriffssorry, that blurb may be a bit misleading20:06
russellbjust like you could run glance on nova, or whatever20:06
kgriffswhile we expect that the majority of deployments will utilize LBaaS and IaaS marconi's design does not preclude running elsewhere20:06
flaper87yeah, I'd say so, yes!20:07
flaper87what kgriffs said!20:07
russellbok.20:07
russellbso, it's not specific integration20:07
ttxcan't wait until Ironic makes all that even more confusing20:07
russellbjust that you expect that it will be common to deploy that way20:07
kgriffsjright20:07
flaper87As per Ceilo, we're planning to integrate w/ it for states and billing. I started digging into how it could be done20:07
kgriffsright20:07
russellbcool20:07
annegentlekgriffs: has marconi been tested with neutron's lb?20:07
kgriffsideally you would also hook into heat/autoscale20:07
flaper87stats*20:07
flaper87annegentle: it hasn't20:08
kgriffsbut thats an operation thing and not tightly coupled to marconi20:08
russellbyeah, so maybe there's some integration work with the deployment program (tripleo)20:08
notmyname /late20:08
russellbsome integration that could be done, i mean.20:08
flaper87russellb: totally20:08
russellbas in, help develop the heat templates to get this stuff deployed20:08
ttxnotmyname: we were just slowly getting more excited.20:08
notmyname:-)20:08
notmynamejust caught up with the buffer playback20:08
ttxSidenote: if accepted, Queue service will become a new "program" with the Marconi project itself being in incubation for integration in the common release20:09
ttxThe "mission statement" for the program is mentioned on the wiki page linked above20:09
flaper87ttx: +120:09
ttxyou might want to review it as part of your decision -making process20:09
jeblairhi. i'd like to encourage marconi to target integration with devstack, tempest, and the devstack-gate tests early; and i'd like to encourage the tc to view that as a goal for promotion from incubation.20:09
russellbjeblair: +120:10
ttxjeblair: yes, we intend to be a lot more blocking on that20:10
flaper87FWIW, the integration with other services and tools like devstack is part of our roadmap for our incubation process20:10
flaper87meaning, we want to get all that done before graduating20:10
ttxjeblair: especially with projects that will be aware of that condition from incubation day 020:10
kgriffs+120:10
flaper87(at least we discussed that, FWIW)20:10
ttxMore questions on Marconi before we vote ?20:10
jeblaircool; it's pretty easy to run alternate devstack tests/environments now, so a project can start running those kinds of tests before it joins the shared devstack-gate queue with the rest of the common release projects20:10
annegentlekgriffs: so this is where I get confused. As an admin user, I could go to Horizon to see my OpenStack deployment's queue?20:11
flaper87jeblair: +120:11
kgriffsrussellb: re heat templates, I think it only makes sense for the Marconi team to contribute there20:11
russellbannegentle: nah, this is different from the queues used as a part of the infrastructure20:11
annegentlekgriffs: as opposed to some cool stock quote queue I made up as a web dev?20:11
flaper87annegentle: yup20:11
annegentlerussellb: ok that's what I thought, we'd really need to map out the Horizon integration then20:11
ttxPersonally I consider a queue service to be pretty essential in a IaaS+ setting20:11
ttxI'd like the focus to be first on providing a featureful and performant solution...20:12
*** vijendar has joined #openstack-meeting20:12
flaper87ttx: Agreed20:12
ttx...rather than on supporting multiple "transports" and "backends".20:12
annegentleflaper87: I think the answer is "no?" no?20:12
annegentleflaper87: :)20:12
ttxWith that caveat noted, I'm ready to vote20:12
oz_akan_ttx: +120:12
russellbready here too20:12
flaper87ttx: that's our goal20:12
*** martine_ has quit IRC20:12
flaper87annegentle: right20:12
flaper87:D20:12
annegentleflaper87: ok, whew20:12
annegentlettx: ok good to go too20:12
* flaper87 bites his nails20:12
mikalHeh20:13
ttxflaper87: note that it's everyoen goal, and then vendors start contributing weird stuff20:13
russellbheh20:13
kgriffsquick question20:13
russellbyeah, don't want to get distracted by too much of that ...20:13
*** sarob has joined #openstack-meeting20:13
jgriffithttx: +120:13
ttx(no, i won't give examples :)20:13
annegentlettx: you're too funny20:13
flaper87ttx: lol20:13
kgriffswould you see an alternative backend (e.g., MySQL) as a requirement for successful incubation?20:13
notmynameIMO, no20:14
annegentlekgriffs: is successful incubation graduation to integrated?20:14
russellbi'd like to say no ... but the licensing of mongodb probably means we should consider it20:14
ttxkgriffs: I think some people see a non-AGPL deployemnt option as a key requirement20:14
kgriffsyes, graduation20:14
russellbbecause i think a lot of people are going to hate that20:14
russellbfor graduation20:14
kgriffsok20:14
flaper87ok20:14
ttxkgriffs: but personally I would not block on that20:14
russellbi would be tempted to personally ...20:15
flaper87awesome feedback, thanks20:15
zanebrussellb: didn't we burn that bridge with ceilometer? ;)20:15
russellbwell, maybe i wouldn't block20:15
russellbheh20:15
kgriffsthanks for the clarification, makes sense20:15
russellbi mean if people are upset enough, they should help add what they want, right?  :-)20:15
russellbbut i expect it to be an "issue" with some folks.20:15
gabrielhurleyrussellb: seconded20:15
ttxkgriffs: so maybe I wouldn't require for graduation, but would be a good feature to add before the first integrated release20:15
russellbcool20:15
ttx(i.e. during the J cycle once you graduated)20:16
kgriffsttx: cool beans20:16
russellbthat's like *forever* from now right?20:16
kgriffsheh. :D20:16
ttxmore questions ? or all TC members ready to vote ?20:16
dolphmttx: i thought there was a licensing issue? no?20:16
mikalI'm ready20:16
russellbready20:16
annegentlewhat's ceilometer using now?20:16
zanebdolphm: no, the client is permissively licensed20:16
ttxdolphm: no. There is a licensing issue with one deployment option of marconi20:17
vishyo/20:17
russellbvishy: just in time for the best part!20:17
mordredo/20:17
jd__annegentle: mongodb or sql20:17
* mordred scans scrollback real quick20:17
ttxvishy, mordred: you might want to file questions before we vote ?20:17
annegentlejd__: thanks20:17
mordred<--- "some people see a non-AGPL deployemnt option as a key requirement" +10020:17
vishysorry i'm late, just got through airport security20:17
mordredvishy: I'm in an airport too! :)20:18
ttxmordred: I was trying to proxy you informally20:18
mordredI would say non-agpl deployment option should be a requirement for graduation20:18
mordredceilometer has one20:18
*** zaro0508 has quit IRC20:18
*** aepifanov has quit IRC20:18
flaper87ok20:18
russellbdefinitely more important than a new transport IMO20:18
ttxmordred: they can use sqlite, does it count ?20:19
*** reed has quit IRC20:19
notmynamelicensing is a separate issue than "alternate backends", IMO.20:19
ttx:P20:19
flaper87ttx: lol20:19
gabrielhurleysqlite--20:19
notmynameback to the first question of it being a requirement for graduation20:19
russellbjson blob text files20:19
mikalWell, at least one distro uses sqlite as their default20:19
mikalFor nova glance etc20:19
gabrielhurleymikal: I don't consider that to be any better20:19
russellbmikal: and that's just bonkers20:19
gabrielhurleydistro--20:19
mikalI didn't say it was a good idea, just observing...20:19
dolphmalso worth reiterating that graduation is also decided by the future TC, not us20:19
* notmyname likes sqlite20:20
* mordred just doesn't want to see 'install mongodb' be a requirement for anyone wanting to run it 'for real'20:20
* mordred likes sqlite too20:20
ttxdolphm: apply for reelection!20:20
dolphmttx: just sayin'20:20
kgriffsmordred: makes total sense to me20:20
ttxmordred, vishy: you ready to vote ?20:20
* mordred does not know enough about how it uses sqlite to know if it's sensible like swift, or whether it's a silly choice like a nova + sqlite would be20:20
notmyname...just a funny discussion when a typical swift deployment can have millions of sqlite DBs20:20
dolphmwe had a conversation previously about setting terms for graduation on a project going into incubation20:20
kgriffsmordred: sqlite is just for localhost dev/test environments20:20
ttxnotmyname: you're using it in a unique way arguably :)20:21
mordrednotmyname: I think your architecture makes sense with sqlite - you don't have a central sqlite20:21
kgriffs(not production!)20:21
mordredkgriffs: right. so I think that for me it's a graduation requirement20:21
mordredand I say that20:21
gabrielhurleyI would be +1 for calling it a graduation requirement, fwiw20:21
mordredjust because I think we shoudl be explicit about things we expect you to work on in incubation20:21
lifelessoh look, a meeting.20:21
flaper87FWIW, we were already planning to implement a rel-based backend, it was a matter to know when20:21
kgriffsI'm cool with that20:21
mordredcool20:21
flaper87so, having it for graduation makes that decision easier20:22
flaper87:D20:22
*** sarob has quit IRC20:22
notmynamemordred: gabrielhurley: "it" being "an alternate storage backend" or "it" being "something not agpl licensed"?20:22
ttxgabrielhurley: having graduation requirements is all about learning from our past mistakes after all20:22
kgriffswe sort of expected folks would want a couple deployment options, in any case20:22
mordrednotmyname: "something not agpl licensed"20:22
dolphmnotmyname: +1 for simply "not agpl licensed"20:22
gabrielhurleynotmyname: I'd go with "something not agpl licensed which is already common in OpenStack deployments"20:22
mordrednotmyname: ability to install marconi in a real production manner without having to install something AGPL20:22
gabrielhurleyI don't like the increasing number of projects increasing the requisite number of underlying services a deployer has to support.20:22
kgriffsgabrielhurley: +120:22
ttxgabrielhurley: +120:22
notmynameok, so if they ripped out mongo and replaced it with something else, but not "pluggable", that's ok20:22
mordredgabrielhurley: +10020:22
gabrielhurleywe shouldn't be requiring 4 different databases.20:22
mordredyes. I would be fine with that20:23
markwashgabrielhurley: +120:23
mordredalthough I doubt they will make that choice :)20:23
annegentlegabrielhurley: fo shizzle20:23
* mordred ready20:23
notmynamemordred: perhaps, but ttx (and others agreed) that the priority should be on functionality rather than plugins20:23
*** weshay has joined #openstack-meeting20:23
dolphm#ready20:24
russellb#set20:24
markwash#abstain20:24
ttxnotmyname: unfair! I was thinking ZeroMQ transport and RabbitMQ backend when I said that20:24
ttx:)20:24
notmynamettx: ah, sorry for the misrepresentation20:24
gabrielhurleymarkwash: lol20:24
hub_caplol20:24
ttxnotmyname: no, you're right. And I stand corrected.20:24
ttx#startvote Accept Queue service as a new program with the Marconi project in incubation during the Icehouse cycle? yes, no, abstain20:24
openstackBegin voting on: Accept Queue service as a new program with the Marconi project in incubation during the Icehouse cycle? Valid vote options are yes, no, abstain.20:24
openstackVote using '#vote OPTION'. Only your last vote counts.20:25
notmyname#vote yes20:25
russellb#vote yes20:25
mikal#vote yes20:25
annegentle#vote yes20:25
*** imsplitbit has joined #openstack-meeting20:25
ttx#vote yes20:25
*** russellb is now known as markmc_by_proxy20:25
markmc_by_proxy#vote yes20:25
shardy#vote yes20:25
dolphm#vote yes20:25
markmcclain#vote yes20:25
*** markmc_by_proxy is now known as russellb20:25
mordred#vote yes20:25
gabrielhurley#vote abstain20:25
ttxrussellb: who needs gerrit when we have NICKCHANGE20:25
russellbttx: yes!20:25
jd__#vote yes20:25
vishy#vote abstain20:25
ttx30 more seconds20:25
markwash#vote abstain20:25
jgriffith#vote abstain20:26
ttx#endvote20:26
openstackVoted on "Accept Queue service as a new program with the Marconi project in incubation during the Icehouse cycle?" Results are20:26
openstackyes (11): ttx, notmyname, markmc_by_proxy, jd__, annegentle, russellb, mikal, mordred, shardy, dolphm, markmcclain20:26
openstackabstain (4): gabrielhurley, markwash, vishy, jgriffith20:26
ttxFor the abstain votes: is that no opinion? not really convinced ?20:26
jgriffithnot convinced20:26
russellbor haven't had enough time to investigate?20:26
ttxjgriffith: fair enough20:27
jgriffithOnly real argument I see is "Amazon has it"20:27
russellbcurious which part you're not convinced of though ... it's fit for openstack?  goals?  etc?20:27
zanebjgriffith: not convinced of the need, or not convinced of this approach?20:27
gabrielhurleyI have nothing against marconi, I just haven't really been convinced that it should be an integrated project under a new Program.20:27
*** rnirmal has quit IRC20:27
jgriffithgoals, value, what the implementation is really going to look like etc etc20:27
gabrielhurleyjgriffith: +120:27
* markwash got last minute cold feet. .20:27
hub_caplol20:27
ttxid devanada back from Burning man ?20:28
markwashgenerally positive20:28
ttxis*20:28
dolphm(fwiw, i was nearly an abstain, due to concerns about scope creep into notifications)20:28
ttxdevananda: around ?20:28
vishyttx: just because i missed the first part of the meeting20:28
ttxvishy: perfect reason!20:28
russellbi'm a little worried about scope creep in transports, even, but i took a leap of faith, heh20:28
hub_capaww ttx u dont wanna do trove first ;)20:28
jgriffithhaha20:28
hub_capNobodyCam is maybe around in devananda's stead?20:28
ttxjust making sure I haven't missed something obvious20:28
gabrielhurleyIf marconi does eventually become integrated I'm all for it, fwiw20:28
kgriffswe can definitely curtail that scope creep, FWIW. :D20:28
ttxhub_cap: ironic should be fast. I'm trying to delay yours so that you can get heat-trusts in :P20:29
gabrielhurleylol20:29
hub_capHAH ttx20:29
zaneblol20:29
*** debo_os has quit IRC20:29
hub_capttx: thats a bug afaic20:29
hub_capin trove20:29
jgriffithhub_cap: code faster.....20:29
hub_capnot a feature, wink wink20:29
ttxunfortunately nobody from ironic is around yet...20:29
russellbkgriffs: yep, i have faith20:29
ttxhub_cap: so you go now20:29
notmynamettx: default deny request?20:29
ttx#topic End-of-cycle graduation review: Trove20:29
*** openstack changes topic to "End-of-cycle graduation review: Trove (Meeting topic: tc)"20:29
flaper87Thanks guys20:29
hub_caplol notmyname glad im here!20:30
ttxhub_cap: Could you describe your current status and progress ?20:30
hub_capso fwiw, the heat optional provisioning is under review and passing tests20:30
hub_capsure ttx20:30
*** amitgandhi has left #openstack-meeting20:30
hub_capwe are integrated into horizon (thx gabrielhurley +crew)20:30
hub_capwe have gone from 2 companies to about 8 with at least 4 actually coding daily20:30
dolphmkgriffs: i think my concerns weren't valid... you're clearly venturing into notifications, but the long term scope seems reasonably well defined20:30
hub_capweve cleaned up a good bit of tech debt20:31
ttxhub_cap: I think there were two main concerns I think wrt graduation: Heat integration and Tempest integration20:31
gabrielhurleyhub_cap: ++20:31
hub_capttx: we decided it woudl be just plain wrong to push tempest on me20:31
ttxIf those are not addressed yet we at least need to be convinced that they will be addressed soon enough to not adversely impact the Icehouse cycle20:31
hub_capa few wks ago20:31
hub_capheat is under review, w 2 caveats20:31
shardyhub_cap: can you link the heat provisioning patch pls?20:31
hub_caphttps://review.openstack.org/#/c/44530/20:31
hub_cap1) trusts20:31
hub_cap2) resize isint using heat, because we rely on the confirm resize nova step to do some "stuff"20:32
hub_cap#2 id like to address by not necessarily using the nova resize, but a smarter cluster-like resize20:32
ttxhub_cap: like I just said, i wouldn't block graduation on that... we just need to be convinced this is top prio and will not be a problem during Icehouse20:32
hub_capif possible20:32
*** hanrahat has joined #openstack-meeting20:32
hub_capttx: its my #1 past heat20:32
shardyso trusts *should* land really really soon, hopefully tomorrow20:32
hub_capwoo shardy20:32
*** esker has joined #openstack-meeting20:33
hub_capi really want to do tempest integration really really bad20:33
jeblairhow about CI integration?20:33
hub_capi want official gating tests20:33
shardyhub_cap: https://review.openstack.org/#/c/43380/20:33
zanebhub_cap: but your use case should work now, even without trusts20:33
ttxjeblair: that's what I mean by tempest integration20:33
* mordred is specifically less worried about tempest and trove due to existence of trove ci stuff - I know the work exists, so porting it in in icehouse should be doable20:33
hub_capzaneb: it does when i send the password20:33
jeblairmordred: it's existed for a long time but still isn't being run in the context of openstack ci20:33
hub_capyes mordred, but i still really want to make all new tests go thru tempest20:33
mordredjeblair: agree20:34
jeblairit's being run as a third party test system20:34
hub_capi dont know if we want to do that jeblair/mordred20:34
* mordred thinks all of trove ci needs to be integrated20:34
zanebhub_cap: there was a patch to remove that requirement... I thought it got merged20:34
mordredhub_cap: we do20:34
hub_capid rather start making tempest tests20:34
jeblairwhich is just a little weird for an official openstack project20:34
vishyhub_cap: can the current version be configured to work using full vms instead of openvz containers.20:34
hub_capmordred: id be happy to work w/ you20:34
hub_capvishy: default is not ovz20:34
hub_capits whatever devstack uses20:34
hub_captrove is virt agnostic20:34
mordredhub_cap: the question is whether or not we give you a pass on not having done that yet :)20:34
vishyhub_cap: corollary: so it might be possible to do it via docker instead?20:34
vishy(for example)20:35
shardyhub_cap: bug #1217617 will allow most use-cases except autoscaling work with token auth and no trusts20:35
uvirtbotLaunchpad bug 1217617 in heat "Always requiring password on create is too restrictive" [High,In progress] https://launchpad.net/bugs/121761720:35
hub_capmordred: well sure, but i dont remember that being a requrement a few mo' ago20:35
hub_capvishy: if docker works w/ nova then hell yes20:35
ttxjeblair: the "no graduation without integration tests" condition was added a bit recently, while the trove folks were already struggling to get our "heat integration" condition in20:35
hub_cap+1 ttx20:35
*** vladimir3p has joined #openstack-meeting20:35
hub_captrust me ;) its my highest prio20:35
mordredhub_cap: yup. but that's before we realized that letting things graduate without ci integration was getting us into a bad place as a project20:35
vishyhub_cap: interesting. Do you make use of cinder volumes?20:35
hub_cappast getting heat in20:35
jeblairttx: well, this is your show, but honestly, it's not like devstack or tempest or the openstack ci system has been a secret20:35
zanebhub_cap: actually, my bad. you are waiting on this: https://review.openstack.org/#/c/44400/20:35
mordredhub_cap: because you _do_ have some CI, I can be convinced that making it an icehouse task might not be terrible20:35
hub_capzaneb: yessir20:35
ttxjeblair: so for that last time I'd settle with "it's my top priority once heat is in, which should be in a few days"20:36
hub_capmordred: should be pretty easy honestly i bet we could get it knocked out in a few days20:36
gabrielhurleysounds acceptable to me. there's clearly a plan here.20:36
*** oz_akan_ has left #openstack-meeting20:36
ttxjeblair: but I tend to agree with you it should have been worked on even while not being a strict condition.20:36
hub_capya we got it running a while ago and havent really mucked w/ it. id gather we could get it running before the summit tho20:37
hub_capits really just running a script on a vm20:37
hub_capthats all we do :P20:37
*** pnavarro has quit IRC20:38
hub_capand you have the whole "prov a vm" stuff worked out20:38
mordredhub_cap: no, I think we're missing each other20:38
jgriffithvishy: yes it does, but hub_cap will have to provide details20:38
hub_capmordred: im always missing you /me sniffles20:38
jgriffithat least last time I looked20:38
hub_capvishy: yes we do (Sry)20:38
mordredhub_cap: we're not interested in infra running additional things that aren't related to devstack-gate20:38
*** oz_akan_ has joined #openstack-meeting20:39
mordredhub_cap: we're interested in integrating the things that your script does into the normal scripts20:39
hub_capmordred: ah ic. i dont blame you! then it can be retrofitted id imagine :)20:39
ttxhub_cap: is there any missing feature in your havana release that you would definitely want to add during the Icehouse cycle ?20:39
ttxlike a blatant feature gap ?20:39
hub_capwell tempest, buit that not a feature20:39
ttxhub_cap: apart from the two already-mentioned20:39
hub_capttx: i have wants but nothing is missing20:39
hub_capconfig mgmt is gonna be nice20:39
hub_capand so is clustering20:39
hub_capand replication/resizes20:40
hub_capbut those arent missing20:40
hub_capthey just arent done yet20:40
mordredhub_cap: does troveclient work with normal OS_* env vars yet?20:40
mordredoh! the plane is moving20:40
* mordred runs away20:40
russellbha.20:40
hub_capHA mordred not yet but i can knock that out fast20:40
mordredplease do20:40
*** gyee has joined #openstack-meeting20:40
hub_capaboslutely20:40
NobodyCamgah thought today was monday :(20:41
hub_capill put it as a bug in rc120:41
hub_capcuz it is a bug to me20:41
ttxhub_cap: you mentioned 4 companies working daily on the project now... but then you seem to be the only one working on graduation-essential stuff like CI and heat integration ?20:41
ttxdoes that mean they contribute tactical features ?20:41
hub_capheh.. well yes20:41
hub_capbasically ya20:41
hub_capmirantis/cern made rhel work, and are making the dev env a bit nicer before they jump in full force w/ features20:42
ttxwhen you say "you", is that "rackspace" or really just you ? Worrying about bus factor20:42
hub_capi prefer the lotto factor ttx20:42
hub_capim not the only person working on public facing interests20:42
hub_capi just took it upon myself to tackle the graduation stuff20:43
hub_caphorizon got done via rax/cern/mirantis together20:43
hub_capdevstack is a hp thing thats happening20:43
hub_capso other teams/companies are working on non tactical features20:43
hub_capwell non $tactical$ features20:43
ttxOK. On my side I can report that trove has been following the release schedule for a few milestones already and it worked really well20:44
hub_capyes thank you ttx for the help w/ all that20:44
ttxso no objection from a release management perspective20:44
hub_capits nice to be in the know at the begin of the process20:44
hub_caprather than after graduation20:44
hub_capi liked a full cycle of milestones + rc's (when that comes), ff, etc..20:44
ttxmaybe other programs could chime in (docs, QA, infra) -- although jeblair already raised his QA/Infra concerns20:45
ttxannegentle: is Docs fine with trove being integrated in Icehouse ?20:45
hub_capdocs http://docs-draft.openstack.org/30/44530/3/check/gate-trove-docs/cef4dbc/doc/build/html/20:45
ttxannegentle: I guess that would be a prio 2 (non core) project ?20:45
annegentleso for a docs perspective, they have done the work we've outlined with openstack processes20:45
hub_capalso we have a mirantis fellow who has created docs for a existing install20:45
hub_capthats under review20:45
*** ayoung has quit IRC20:45
hub_caphttps://review.openstack.org/#/c/44668/20:46
ttxOK, I'm ready to vote -- other questions ? Anyone wanting a delay before we vote ?20:46
ttxit's our first end-of-cycle graduation review so the rules are a bit fresh20:46
hub_cap:)20:47
hub_caphorray /me is a guinea pig20:47
hub_capoh nm20:47
hub_capjust this cycle lol20:47
russellb#ready20:47
ttxI guess we could do it over two meetings if that gives people time to look into the code with more details20:47
*** grapex has joined #openstack-meeting20:47
russellb#ornot20:47
hub_capHA20:47
ttxalthough I don't expect that many people reading random code those days20:47
* jgriffith is still ready20:47
russellbttx: quite a busy week ahead ...20:48
hub_capw/ the review rush ttx ;)20:48
* gabrielhurley is ready20:48
dolphmrussellb: ++20:48
mikalready20:48
russellbsteady!20:48
hub_capgo?20:48
jgriffith:)20:48
*** esker has quit IRC20:48
russellb-220:48
russellbkidding.20:48
jgriffithrussellb: slap!20:48
hub_capouch i got a big red X from russellb20:48
ttxI'm giving it another minute to make sure everyone is fine with voting now20:48
jgriffith:)20:49
hub_caphes good at giving those ;)20:49
annegentlefine with voting now20:49
jd__same20:49
ttx#startvote Graduate Trove to be integrated during the Icehouse cycle? yes, no, abstain20:49
openstackBegin voting on: Graduate Trove to be integrated during the Icehouse cycle? Valid vote options are yes, no, abstain.20:50
openstackVote using '#vote OPTION'. Only your last vote counts.20:50
russellb#vote yes20:50
jgriffith#vote yes20:50
*** russellb is now known as markmc_by_proxy20:50
markwash#vote yes20:50
shardy#vote yes20:50
markmc_by_proxy#vote yes20:50
ttx#vote yes20:50
gabrielhurley#vote yes20:50
*** markmc_by_proxy is now known as russellb20:50
markmcclain#vote yes20:50
*** jhenner has joined #openstack-meeting20:50
*** esker has joined #openstack-meeting20:50
mikal#vote yes20:50
dolphm#vote yes20:50
ttx30 more seconds20:50
*** IlyaE has quit IRC20:50
vishy#vote yes20:50
jd__#vote yes20:50
notmyname#vote abstain20:50
annegentle#vote yes20:50
*** debo_os has joined #openstack-meeting20:50
*** robertmyers has joined #openstack-meeting20:51
ttx#endvote20:51
openstackVoted on "Graduate Trove to be integrated during the Icehouse cycle?" Results are20:51
openstackyes (13): ttx, vishy, markmc_by_proxy, jd__, annegentle, shardy, russellb, markwash, mikal, gabrielhurley, dolphm, jgriffith, markmcclain20:51
openstackabstain (1): notmyname20:51
dolphmno mordred?20:51
gabrielhurleyhe got on a palce20:51
hub_capmordred: is on a plane20:51
ttxmordred: on a plae now20:51
gabrielhurley*plane20:51
hub_capsnakes not included20:51
hub_capthx everyone!!20:51
ttx#topic End-of-cycle graduation review: Ironic20:51
*** openstack changes topic to "End-of-cycle graduation review: Ironic (Meeting topic: tc)"20:51
ttxhub_cap: congrats!20:51
russellbhub_cap: nice work20:51
ttxstill no ironic dude around ?20:52
zanebcongrats hub_cap20:52
NobodyCamme20:52
ttxNobodyCam: hi!20:52
NobodyCamdeva is driving right now20:52
*** imsplitbit has left #openstack-meeting20:52
ttxNobodyCam: So my understanding is it's pretty obvious this one should not graduate, since devananda himself said it's not ready20:52
ttx...and it does not really work yet...20:52
NobodyCamcorrect20:52
ttxSo the question is more... should it continue to be incubated or should it be dropped because it's not going anywhere ?20:52
*** zehicle_at_dell has quit IRC20:52
*** esheffield has joined #openstack-meeting20:53
NobodyCamit is going forward!20:53
annegentleoh I hope we keep incubating20:53
*** zehicle_at_dell has joined #openstack-meeting20:53
vishynot going anywhere?20:53
mikalI would be opposed to dropping it from incubation20:53
mikalAlthough I also don't have the time to work on it...20:53
ttxvishy: s/because/if/20:53
ttxvishy: just making sure we still all want it in incubation.20:53
russellbironic - 72 code reviews in the laast 30 days20:54
vishyi haven't been keeping up with the status20:54
russellbso still moving20:54
notmynamettx: perhaps a better way to phrase it is "should it be dropped and reapply when it is ready"20:54
*** SumitNaiksatam has quit IRC20:54
markwashstupid english lacking subjunctive20:54
*** sarob has joined #openstack-meeting20:54
russellb462 reviews in the last 90 days20:54
russellbso, quieter in the last month20:54
mikalrussellb: do you have stats on how many active devs?20:54
lifelesswell, burning man20:54
russellblifeless: yeah20:54
NobodyCamyes we are moving forward we had a lot vacations last couple of weekes20:54
russellbmikal: just reviewers20:54
*** SumitNaiksatam has joined #openstack-meeting20:54
russellbhttp://russellbryant.net/openstack-stats/ironic-reviewers-90.txt20:54
ttxnotmyname: yes, better. That said I'm very fine with projects taking more than one cycle to incubate properly20:54
gabrielhurleydo you think it'll take one more cycle to be ready? two? three?20:54
*** Adri2000 has quit IRC20:55
dolphmmikal: 24?20:55
ttxI would be glad to set a precedent, actually20:55
notmynamettx: one of the issues being discussed now is that graduation isn't "winning" just as not graduation isn't "losing"20:55
*** cp16net has joined #openstack-meeting20:55
dolphmmikal: ah, nvm20:55
notmynamettx: (being discussed in context of the "what is core" stuff)20:55
mikaldolphm: wow, more than I expected20:55
russellbdefine active20:55
* mordred back20:55
ttxmordred: trove was accepted, discussing ironic now20:56
russellbhttp://stackalytics.com/?release=havana&metric=commits&project_type=openstack&module=ironic&company=&user_id=20:56
russellbironic contributors ^20:56
* mikal looks20:56
ttxSo I'm fine with voting for keeping Ironic in incubation now20:56
mordreddo we need to vote on that?20:56
ttxnot sure we really need more time to discuss it, but was can also wait until next week20:56
russellblooks like the project could use some more heavy contributors beyond devananda20:56
jgriffithrussellb: +120:57
*** elo has joined #openstack-meeting20:57
ttxmordred: maybe ? It's the first cycle we do end-of-cycle reviews :)20:57
mordredI was sort of looking forward to seeing the incubation process for this last until it's ready20:57
ttxmordred: I'm fine with not voting too.20:57
*** IlyaE has joined #openstack-meeting20:57
russellbprobably only needs a vote if anyone suggests that it be dropped20:57
russellbi think the default answer should be that it stays20:57
mordredttx: it is currently incubated - nothing automatically removes that - I think it's just still incubated unless someone wants to move that we un-incubate it20:57
mordredwhat russellb said20:58
ttxmordred: we need some way to remove dead stuff from incubation, but that can be ad-hoc rather than a regular review20:58
ttxrussellb: +120:58
mordredttx: I think someone will propose we drop it if it's dead20:58
ttx#info Ironic stays in incubation for the Icehouse cycle20:58
mordredyikes. laggy plane wifi20:58
russellbdang, productive meeting :)20:58
jgriffithmordred: first world problems20:59
ttx#topic Open discussion20:59
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:59
dolphmmikal: since june, 19 authors (including jenkins and a dupe)... so 17 by my count http://paste.openstack.org/raw/45694/20:59
*** branen__ has quit IRC20:59
ttxall: You might have noticed that we're not using Gerrit to vote yet20:59
markwashjgriffith: lol20:59
ttxThe repository is almost set up, blocking on bug 121973120:59
uvirtbotLaunchpad bug 1219731 in openstack-ci "Populate tech-committee* groups in Gerrit" [Undecided,New] https://launchpad.net/bugs/121973120:59
ttxThen we can review/accept the initial commit of reference documents at:20:59
ttx#link https://review.openstack.org/#/c/44489/20:59
ttxAnything else, anyone ?20:59
*** boris-42 has quit IRC20:59
*** markmc has joined #openstack-meeting21:00
ttxmarkmc from France !21:00
russellbmarkmc: oh snap!21:00
markmcyah :)21:00
* mordred thinks everyone is great - and also you all might have blinky lights around your head in mmy mind21:00
*** grapex has left #openstack-meeting21:00
ttxok then, next meeting21:01
ttx#endmeeting21:01
*** danwent has quit IRC21:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Tue Sep  3 21:01:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-09-03-20.01.html21:01
clarkbttx: I just did the group stuff for tech-committee21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-09-03-20.01.txt21:01
mikalBye21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-09-03-20.01.log.html21:01
ttxclarkb: awesome!21:01
*** carl_baldwin has joined #openstack-meeting21:01
*** glikson has quit IRC21:01
*** sarob_ has joined #openstack-meeting21:01
ttxmarkmc, dolphm, notmyname, jd__, markwash, jgriffith, russellb, shardy, gabrielhurley, markmcclain: around ?21:01
gabrielhurley\o21:01
notmynamehere21:01
jgriffithalo21:01
shardyhi21:01
markwasho/21:01
jd__o/21:01
markmchey21:02
dolphmo/21:02
*** dvarga has quit IRC21:02
markmcclaino/21:02
russellbo/21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Sep  3 21:02:36 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:02
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttx#topic General stuff21:02
*** openstack changes topic to "General stuff (Meeting topic: project)"21:02
ttx#info Feature Freeze is EOD tomorrow, together with the havana-3 branch cut21:02
ttx#info havana-3 publication is planned for Friday.21:03
ttxThat leaves today and tomorrow to merge stuff, before we defer or use exceptions21:03
*** mdenny has quit IRC21:03
ttxsdague, annegentle, mordred: news from QA/Docs/Infra programs ?21:03
annegentleo/21:04
gabrielhurleyttx: string freeze and feature freeze coincide, yes?21:04
ttxgabrielhurley: good point, yes21:04
gabrielhurleycool, just making sure21:04
ttx#link https://wiki.openstack.org/wiki/Havana_Release_Schedule21:05
annegentleNova is in the most need of docs based on doc bugs21:05
annegentle#link https://bugs.launchpad.net/openstack-manuals/+bugs/?field.tag=nova21:05
*** sarob has quit IRC21:05
*** sarob_ has quit IRC21:05
russellbi really want to figure out how to push for more help from nova contributors on that21:05
annegentlewe're continuing to reorganize the openstack-manuals repo around the new titles that are overarching for OpenStack21:05
ttxannegentle: I hope feature freeze will drive dozens of developers to help you21:06
annegentleOur docs boot camp starts next Monday21:06
russellbwe have no shortage of people trying to push features in, so we can probably afford to raise the bar21:06
annegentlettx: I hope so/think so too21:06
annegentlerussellb: yes21:06
ttxAny other general announcement before we dive into project-specific stuff ?21:06
annegentlethat's it21:06
ttx#topic Oslo status21:07
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:07
ttxmarkmc: hi! how is France ?21:07
markmchey21:07
ttx#link https://launchpad.net/oslo/+milestone/havana-321:07
markmcgood, good21:07
russellbvery French?21:07
markmcso, I'm not really here :)21:07
ttx2 Low blueprints left21:07
*** weshay has quit IRC21:07
markmcwell, my whiskey is irish right now21:07
ttxguru-meditation-report looks extremely close, with a small test mismatch21:07
markmcyeah, so looks like the guru meditation one is almost merged21:07
ttxcache-backend-abstraction looks a bit more far away21:07
markmcright, agree21:08
markmcthese are the two that don't pose a regression risk21:08
ttxmarkmc: would you require a FFe for things that wouldn't merge by tomorrow's deadline ?21:08
markmchow about we defer cache-backend-abstraction to icehouse21:08
markmcand give guru-meditation-report another week21:08
markmcwe can require the FFE process if you like21:08
* markmc is easy21:08
markmcmostly because they don't pose a risk21:09
ttxmarkmc: ok, so one FFe for guru-meditation-report if it needs a couple more days21:09
markmcok21:09
ttxI'll look at it tomorrow, but should be fine21:09
markmcgreat, ahsnk21:09
ttxQuestions about Oslo ?21:09
markmcthanks21:09
ttxmarkmc: you can return to your Muscat21:09
markmcthanks :)21:09
ttx#topic Keystone status21:09
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:09
ttxdolphm: hello!21:09
dolphmo/21:09
ttx#link https://launchpad.net/keystone/+milestone/havana-321:10
ttx2 blueprints left21:10
dolphmwhich was the same blueprint last week :)21:10
dolphmbp list-limiting was split from bp filtering-backend-support21:10
ttxright21:10
ttxhow far is that ? Can be merged today or tomorrow ?21:10
dolphmthey've both been in review, but it was sort of two features rolled into one, so the blueprints and reviews were both split apart21:10
ttx83% done, 16% under review, 0% in progress, 0% not started21:10
*** dkehn_away is now known as dkehn21:11
dolphmfeature complete and in review, but not user-facing or exposing anything new for havana (so not a big deal if it doesn't land)21:11
ttxdolphm: ok21:11
*** ametts has left #openstack-meeting21:11
*** ndipanov has quit IRC21:11
ttxWould you require a feature freeze exception for it if it fails to land by tomorrow ?21:12
dolphmno21:12
*** robertmyers has left #openstack-meeting21:12
ttxok, merge or wait. Perfect.21:12
*** SergeyLukjanov has quit IRC21:12
ttxYou have 4 havana-3 bugs... anything h3-critical in there ? Or should I just defer to RC1 anything that doesn't make it ?21:12
*** pentameter has quit IRC21:12
*** sandywalsh has quit IRC21:12
dolphmnone of those should block havana-321:13
ttxdolphm: OK. anything specific you wanted to tell us ?21:13
dolphmnope!21:13
dolphmhappy feature freeze, everyone!21:13
ttx#topic Ceilometer status21:13
*** openstack changes topic to "Ceilometer status (Meeting topic: project)"21:13
ttxjd__: hey21:14
jd__o/21:14
ttx#link https://launchpad.net/ceilometer/+milestone/havana-321:14
ttx61% done, 23% under review, 15% in progress, 0% not started21:14
ttx5 >Low blueprints left21:14
jd__at this stage I don't think any low bp not started will go in indeed :)21:14
ttxjd__: heh21:14
ttxQuick status update21:15
ttxIs api-group-by likely to land by tomorrow ?21:15
jd__ttx: no21:15
ttxjd__: would you consider requesting a FeatureFreeze exception for it ? Or defer to icehouse ?21:16
jd__FFE21:16
ttxjd__: ok, we'll discuss it together tomorrow21:16
jd__ack21:16
ttxwhat about alarm-service-patitioner / alarm-audit-api ?21:17
jd__all the patches have been presented for review now21:17
jd__so we just need to ping-pong with eglynn at this stage to get things merged21:17
jd__it looks pretty good21:17
ttxjd__: ok, so that might merge. If it doesn't, would you do a FFE for that as well ?21:18
*** kgriffs has left #openstack-meeting21:18
jd__very likely21:18
ttxsame for alarming-logical-combination ?21:18
jd__yep21:19
*** dcramer_ has quit IRC21:19
ttxpaginate-db-search is medium, would that be deferred if it doesn't make it ?21:19
jd__yes, it could be deferred21:19
ttxjd__: ok, we'll look how disruptive those FFE features are and how much more time they actually need21:19
ttxwill ping you tomorrow21:19
jd__not much I hope :) ok!21:19
ttxYou have 6 havana-3 bugs... anything h3-critical in there ?21:19
ttxMaybe https://bugs.launchpad.net/bugs/1219776 ?21:20
uvirtbotLaunchpad bug 1219776 in ceilometer "PostgreSQL migration is broken" [Critical,In progress]21:20
ttxor should I just defer to RC1 anything else that doesn't make it ?21:20
jd__yes this one break devstack-gate actually21:20
ttxah, sounds worthy of a backport then21:20
jd__the other can be deferred21:20
ttxok, thx21:20
*** pcm_ has quit IRC21:20
ttxjd__: anything you wanted to mention ?21:20
jd__nop21:20
ttxcool, thx21:20
ttx#topic Swift status21:20
*** openstack changes topic to "Swift status (Meeting topic: project)"21:21
ttxnotmyname: o/21:21
notmynamehello21:21
ttx#link https://launchpad.net/swift/+milestone/1.9.321:21
* notmyname hasn't updated LP yet :-(21:21
*** dolphm has quit IRC21:21
ttxnotmyname: anything specific you wanted to raise ?21:21
notmynamewe're thinking of splitting of the swift-bench bin into a separate repo21:21
notmynamestill under discussion21:22
notmynamethings are coming along well for the havana release21:22
ttxnotmyname: sounds doable to me21:22
notmynamethe big stuff right now is finishing up the DiskFile abstraction21:22
notmynameand the DBBroker abstraction21:22
*** markmc has quit IRC21:22
*** oz_akan_ has quit IRC21:23
notmynameother than that, we're still doing well21:23
ttxnotmyname: sounds interesting. Will read blueprints when you file them :P21:23
notmynameI think there is one :-)21:23
notmynamejust need targeting, and perhaps split21:23
*** sarob has joined #openstack-meeting21:23
ttxok :)21:23
ttxQuestions about Swift ?21:23
*** sandywalsh has joined #openstack-meeting21:24
ttxnotmyname: thx!21:24
ttx#topic Glance status21:24
*** openstack changes topic to "Glance status (Meeting topic: project)"21:24
ttxmarkwash: o/21:24
ttx#link https://launchpad.net/glance/+milestone/havana-321:24
ttx71% done, 28% under review, 0% in progress, 0% not started21:24
markwasho/21:24
ttx2 blueprints left21:24
markwashall reviews are submitted21:24
*** armax has joined #openstack-meeting21:24
ttxMy favorite, api-v2-property-protection21:25
markwashglance scrubber refactoring should roll in tonight21:25
ttxmarkwash: ok21:25
markwashapi v2 property protection is fighting its way off the ropes21:25
ttxAnything you think would need a feature freeze exception if it fails to land by tomorrow ?21:25
*** weshay has joined #openstack-meeting21:25
markwashprotected properties if it feels close enough21:25
ttxI'm generally fine with FFEs if it's likely that adding a few days will make a difference21:26
ttxok, we'll discuss it when/if necessary21:26
*** radsy has joined #openstack-meeting21:26
markwashthere is a bp in next (async processing) that might be ready soon if we have enough bandwidth21:26
*** hanrahat has quit IRC21:26
markwashand get lucky21:26
ttxok, we'll retroactively add it to h3 if it makes it21:26
ttxYou have 4 havana3-targeted bugs...21:26
ttxAny chance bug 1213241 will be covered before EOD Thursday ? Looks heavy21:27
uvirtbotLaunchpad bug 1213241 in glance "Pickled data in Glance database enables remote code execution" [Critical,Confirmed] https://launchpad.net/bugs/121324121:27
*** zehicle_at_dell has quit IRC21:27
markwashI think it should be easy to do. I am taking it on21:28
markwashshould have updated the assignee21:28
markwashcan you clarify the timing on these things. I'm confused about the gap between FF and RC21:28
ttxsure21:28
markwashwhat is expected to happen during that time? known bugs? or only unknowns that pop up?21:28
*** sushils has joined #openstack-meeting21:29
ttxVery early thursday morning I'll cut a release branch for H3 (milestone-proposed)21:29
ttxwe can still backport H3-critical bugfixes to it21:29
markwashearly thursday morning == what time UTC?21:29
ttxTo track that, we clean up the H3 bug list so that it only contains stuff we'll go through the hassle to backport21:29
ttxI'd say 0800 UTC. Some people would call it "late on Wednesday". I call it "EOD Wednesday"21:30
markwashso at what point does I1 effectively open up?21:30
ttxmarkwash: but we can still backport bugfixes that land in master, to milestone-proposed21:31
ttxuntil H3 publication.21:31
* markwash is sorry he has not completely clarified this for himself before21:31
ttxI1 opens up after RC121:31
ttx(the icehouse development branch opens once you produce a first release candidate21:31
*** debo_os has quit IRC21:31
markwashgotcha21:31
ttxDetails at https://wiki.openstack.org/wiki/ReleaseCycle21:31
ttxSo I'll keep that critical bug in the buglist and defer the others to the RC1 buglist21:32
*** writerDiane has quit IRC21:32
ttxmarkwash: anything you wanted to mention ?21:32
markwashI'm good, thank you for the hand-holding21:32
ttxmarkwash: np21:32
ttx#topic Neutron status21:32
*** openstack changes topic to "Neutron status (Meeting topic: project)"21:32
ttxmarkmcclain: hi!21:32
ttx#link https://launchpad.net/neutron/+milestone/havana-321:32
ttx70% done, 29% under review, 0% in progress, 0% not started21:33
ttxlots of recent progress I see21:33
markmcclainhi21:33
markmcclainyes.. lots of reviews lately21:33
ttxSo that's 15 >Low blueprints still in progress...21:33
ttxHow is ipsec-vpn-reference going ?21:33
markmcclainit is in final testing21:34
markmcclainI expect it to merge21:34
ttxok21:34
*** lblanchard has joined #openstack-meeting21:34
ttxmarkmcclain: Would you consider granting a feature freeze exception to any of those 15 if they fail to make it by EOD tomorrow ?21:34
NobodyCamservice nagios3 restart21:34
ttxNobodyCam: [ OK ]21:34
NobodyCamdoh21:34
NobodyCamsorry21:34
markmcclainthere are 2 that might be good candidates for an FFE21:35
markmcclainthey're relatively isolated from rest of code base and the code is already written21:35
*** ivar-lazzaro has joined #openstack-meeting21:35
markmcclainjust need to bake a bit more21:35
*** lbragstad has quit IRC21:35
ttxmarkmcclain: names, for reference ?21:35
ttx(I'll defer everything else that doesn't make it, and keep those ones for us to review)21:36
markmcclainVCNS and NVP Firewall Plugin21:36
ttxthx! You also have 34 H3-targeted bugs. Is there anythign H3-critical in there ? Or can I just defer to RC1 anything that isn't FixCommitted when I cut the branch ?21:36
markmcclainsounds good21:36
markmcclaindeferring should be fine.. I'll scan the list again tomorrow to double check21:37
ttxmarkmcclain: ok. anything else you wanted to raise ?21:37
markmcclainnothing new21:37
ttxmarkmcclain: ok, thx!21:37
ttx#topic Cinder status21:37
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:37
*** litong has quit IRC21:37
ttxjgriffith: hola!21:37
ttx#link https://launchpad.net/cinder/+milestone/havana-321:37
jgriffithhey there21:38
*** alaski is now known as alaski-vacation21:38
ttx73% done, 26% under review, 0% in progress, 0% not started21:38
ttxAlso lots of progress recently21:38
jgriffithworking on it21:38
jgriffithI expect a few more to land tonight21:38
ttx5 Medium blueprints still in progress21:38
jgriffithand a couple I think I'm going to kick out21:38
* jgriffith is looking...21:38
ttxWould you consider a feature freeze exception for any of those ?21:38
jgriffithttx: nope21:39
jgriffithttx: 3 of them I expect to land today21:39
jgriffithif they don't I'd consider exceptions21:39
jgriffithqemu assisted snaps, zadara and vmdk driver21:39
ttxok21:39
ttxYou've also got 8 H3-targeted bugs.. anything H3-critical in there ?21:39
jgriffithI expect this to sort itself pretty well by tmororw night21:40
ttx(bug 1219950 is not assigned to anyone fwiw)21:40
uvirtbotLaunchpad bug 1219950 in cinder "C:\iSCSIVirtualDisks dir created during tests" [Undecided,New] https://launchpad.net/bugs/121995021:40
ttxjgriffith: ok, anything else on your mind ?21:40
jgriffiththanks... I missed that one21:40
jgriffithnope, not for now21:40
ttxQuestions on Cinder ?21:40
ttx#topic Nova status21:41
ttxrussellb: hey21:41
*** openstack changes topic to "Nova status (Meeting topic: project)"21:41
ttx#link https://launchpad.net/nova/+milestone/havana-321:41
russellbhey21:41
ttx64% done, 35% under review, 0% in progress, 0% not started21:41
russellbprogress21:41
russellba lot of it is really close21:41
russellbwe're pushing hard21:41
ttxNice progress but still a long way to go... 15 >Low blueprints21:41
ttxQuick status update on the "High" prio stuff...21:41
russellbyeah, i know a lot will get deferred, i accepted that a while ago, heh21:42
ttxHow is compute-api-objects going on ?21:42
russellbit's fine, there's still some patches up for review21:42
russellbbut we basically rescoped it to covered what we *know* will make it21:42
russellbso just tying up the last ends on it21:42
ttxrussellb: heh21:42
russellb:)21:42
ttxencrypt-cinder-volumes ?21:42
russellbthe two encryption ones are probably going to get deferred21:42
russellbi'm giving it a little more time for a ML discussion to play out21:43
ttxok21:43
ttxfix-libvirt-console-logging ?21:43
russellbbut basically ... it's not *actually* usable ...21:43
russellbheh21:43
russellblibvirt console logging has promise, needs review time, but can make it i think21:43
ttxfwiw that would be (actually is) considered a bug21:43
russellbtrue, so I definitely think we can make an exception for it21:43
ttxit's just a significant bugfix :)21:43
russellbright21:43
ttximprove-block-device-handling ?21:44
russellbi expect an update on that one first thing in the morning to cover last bit of concern, then it will be merged tomorrow21:44
*** zz_Guest71813 is now known as leif21:44
ttxcold-migrations-to-conductor and live-migration-to-conductor ?21:44
russellbcold migration to conductor doesn't look good, will probably get deferred21:44
russellblive migration looks in good shape, last patch under review, can make it21:44
ttxCould any of these trigger a featurefreeze exception request ?21:44
*** leif is now known as Guest2620721:45
russellbyes21:45
russellbprimarily the libvirt console log one21:45
ttxand compute-api-objects in case its new scope needs a couple more hours21:45
russellblive migration to conductor and improve block devices as well ...21:45
russellbbut only because i think it would just need another day if so21:45
ttxright21:45
russellbyeah21:45
ttxWhat about the Medium-prio ones ? Any FFE candidate lost in there ?21:45
russellbi'm not seeing anything that would get an exception other than just needing a couple extra days for review time / final tweaks21:46
ttxPort to oslo.messaging ?21:46
russellbport to oslo.messaging ... markmc has been aggressively updating that and rebasing it21:46
russellbjust needs review time21:46
gabrielhurleycan I ask about https://blueprints.launchpad.net/nova/+spec/hyper-v-rdp-console ? The Nova reviews are under review but nothing's merged. There's a Horizon review to support that feature, but if it's not gonna land in Nova then it needs to be pushed off.21:46
russellbpoor guy is chasing it hard on vacation too21:46
ttxcould use a FFE too ?21:46
russellbttx: yes21:46
russellbgabrielhurley: seems incredibly unlikely to make it21:47
gabrielhurleycool. that's all I needed to know. :-)21:47
*** Mandell has quit IRC21:47
russellbgabrielhurley: it's fairly complex, and a bit down the list21:47
*** Mandell has joined #openstack-meeting21:47
ttxrussellb: You've got like 37 bugs targeted to H3, are any of those H3 blockers ?21:47
*** Guest68015 is now known as oubiwann21:47
ttxMaybe one of the 4 critical ones ?21:47
ttxerr. 321:47
russellbbug 121672021:47
uvirtbotLaunchpad bug 1216720 in nova "Security groups with source groups no longer work" [Critical,Confirmed] https://launchpad.net/bugs/121672021:47
russellbnot sure if it's an h3 blocker ... definitely an rc blocker though21:47
russellbi know vishy saw it21:48
ttxagreed, the other two don't sound that critical to me21:48
russellb(related to a patch he did)21:48
russellbyeah same21:48
russellbjust haven't made it to review/lower them21:48
ttxOK, will defer them to RC1 if they don't make it by branch cut time.21:48
russellblots of people like to mark their bugs as ciritical :-)21:48
russellbsounds perfect21:48
ttxthat's why we have guidelines to protect us from them21:48
ttxhttps://wiki.openstack.org/wiki/Bugs21:48
*** SumitNaiksatam has quit IRC21:48
ttxrussellb: anything else you wanted to mention ?21:49
russellbdon't think so21:49
ttxAny question on Nova ?21:49
russellbjust general request for understanding on the stuff that doesn't make it :-)21:49
russellbthe heat is really turning up on me this week on that stuff, heh21:49
hub_capqueue the glenn frey song21:49
russellbthat's what happens when 100 blueprints are delievered in the last dev milestone :-)21:50
russellbthat's it, thanks!21:50
ttxrussellb: yes, I don't know how to set expectations right... people submitting their work for H3 should know it has chances to skip21:50
*** amotoki_ has joined #openstack-meeting21:50
*** amotoki_ has quit IRC21:50
ttxrussellb: but they are always surprised21:50
russellbyep21:50
*** amotoki_ has joined #openstack-meeting21:50
ttx#topic Heat status21:50
*** openstack changes topic to "Heat status (Meeting topic: project)"21:50
ttxshardy: o/21:51
shardyo/21:51
ttx#link https://launchpad.net/heat/+milestone/havana-321:51
ttx85% done, 14% under review, 0% in progress, 0% not started21:51
shardynearly there..21:51
ttx4 blueprints left... quick status update on the high-prio ones:21:51
ttxone*21:51
shardyheat-trusts and parallel-delete are really close21:51
ttxheat-trusts21:51
shardyyep, I think that should make it by EOD tomorrow, down to very minor comments now after several iterations21:52
shardysimilar with parallel-delete I think21:52
ttxAnything you'd consider asking a feature freeze exception for in the unlikely case it doesn't make it in time? heat-trusts ?21:52
shardyI'm less confident about vpnaas and UpdatePolicy21:52
shardyYep definitely heat-trusts, and probably parallel-delete21:52
shardyI'd like the others to land, but if they don't I think we'll bump them as it probably means too much review rework21:53
*** branen has joined #openstack-meeting21:53
*** mdenny has joined #openstack-meeting21:53
ttxright. And even if you could handle them... we need to reduce disruption to let QA/Docs catch up with the added features21:53
ttx9 bugs targeted to H3, any H3 blocker in them ?21:54
shardyyep, both were really proposed too late21:54
shardyNo, I think we can just defer any which don't land in time to rc121:54
ttxok willdo21:54
ttxshardy: anything else you want to raise ?21:54
shardyNo, all good, thanks!21:55
ttxthanks!21:55
ttx#topic Horizon status21:55
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:55
ttxgabrielhurley: o/21:55
gabrielhurleyLemme make this easy ;-)21:55
gabrielhurley The bugs all have patches and will likely merge today. The custom CA cert blueprint is merging currently. That just leaves the Cisco N1K/custom router dashboard BP, which is perenially pretty close, but is so narrow in scope and so isolated that I'm not unlikely to FFE it if it doesn't make it in time. There are a handful of bugs I've already marked as RC1.21:55
ttx#link https://launchpad.net/horizon/+milestone/havana-321:55
*** branen_ has joined #openstack-meeting21:56
ttxleaves me speechless21:56
gabrielhurley"not unlikely"... that was a nice double-negative21:56
*** MIDENN_ has joined #openstack-meeting21:56
ttx100% done, 0% under review, 0% in progress, 0% not started21:56
*** Toshi has joined #openstack-meeting21:56
*** KurtMartin has joined #openstack-meeting21:56
gabrielhurley100% for > Low, yeah21:56
gabrielhurley:-)21:56
ttxLooks like custom CA is marked implemented now21:56
gabrielhurleymy team kicked ass these last few weeks21:56
gabrielhurleyit *just* merged, literally right now21:57
ttxheh21:57
*** dkranz has quit IRC21:57
ttxok then, anything else on Horizon?21:57
gabrielhurleynope, we're good21:57
*** dcramer_ has joined #openstack-meeting21:57
ttxgabrielhurley: next cycle you should go first so that you don't have the full hour to prepare answers for my repetitive questions21:58
gabrielhurleyhaha21:58
ttx#topic Incubated projects21:58
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:58
gabrielhurleya challenge. I like it21:58
ttxdevananda, hub_cap, NobodyCam: 2 minutes, any question ?21:58
*** Toshi has quit IRC21:58
hub_cap2 things, 1) we need more time for this next cycle lol21:58
hub_capand 2)21:58
hub_caphugs21:58
NobodyCamjust notes that ironics devs are starting to come back from vacation21:58
*** Toshi has joined #openstack-meeting21:58
*** eglynn has joined #openstack-meeting21:59
ttx#info Trove graduated from incubation and will be part of the Icehouse integrated release in 7 months21:59
gabrielhurley+121:59
ttx#info Ironic will do incubation for another cycle21:59
*** mdenny has quit IRC21:59
NobodyCam:)21:59
*** branen has quit IRC21:59
ttxTrove havana-3 looking almost done: https://launchpad.net/trove/+milestone/havana-321:59
*** trey_h_ has joined #openstack-meeting22:00
*** eharney has quit IRC22:00
ttx#endmeeting22:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:00
openstackMeeting ended Tue Sep  3 22:00:25 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-09-03-21.02.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-09-03-21.02.txt22:00
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-09-03-21.02.log.html22:00
*** Toshi has quit IRC22:00
*** Toshi has joined #openstack-meeting22:00
gabrielhurley#startmeeting horizon22:01
openstackMeeting started Tue Sep  3 22:01:05 2013 UTC and is due to finish in 60 minutes.  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
gabrielhurley#topic overview22:01
*** openstack changes topic to "overview (Meeting topic: horizon)"22:01
gabrielhurleyBoy oh boy has it been a busy week!22:01
gabrielhurleyHi folks!22:01
lsmola_hello22:01
jpichHello22:01
david-lyleHello22:01
*** absubram_ has joined #openstack-meeting22:01
lblanchardhey everyone22:01
jcoufalhey there22:01
absubram_hi22:01
gabrielhurleySo, first off, AMAZING job getting all that code done and all those reviews in. We all really kicked ass the last two weeks.22:01
amotoki_hi, long time no see22:02
*** ayoung has joined #openstack-meeting22:02
gabrielhurleyWe actually got a "leaves me speechless" from ttx for having completed all that22:02
gabrielhurleyeveryone should feel really positive22:02
*** ftcjeff has joined #openstack-meeting22:02
jcoufalthe highest title possible :)22:02
gabrielhurleySo if you haven't heard, we're at the end of the H3 milestone. ;-)22:03
*** vijendar has quit IRC22:03
gabrielhurleyThe deadline for merges is EOD tomorrow22:03
gabrielhurleyWhat's left in https://launchpad.net/horizon/+milestone/havana-3 is basically what I'd like to see22:03
gabrielhurleythere's a handful of bugfix reviews (two of which i posted today) that need an additional +222:03
*** trey_h has quit IRC22:03
gabrielhurleyand one blueprint left22:03
gabrielhurleyhttps://blueprints.launchpad.net/horizon/+spec/horizon-cisco-n1k22:03
gabrielhurleyWe'll chat a little more on that in the blueprints topic22:04
absubram_ok thanks22:04
gabrielhurleybefore that, a couple more general bits of business22:04
*** trey_h_ has quit IRC22:05
gabrielhurleySome of you may have heard that the Technical Committee is going to move to having formal documents like the TC charter stored in github/gerrit so that changes can be officially voted on and tracked in a better way.22:05
gabrielhurleyConnected to that, the review for the initial set of documents it here: https://review.openstack.org/#/c/44489/222:05
gabrielhurleyThis isn't just general interest, though22:05
gabrielhurleyI specifically wanted to point out https://review.openstack.org/#/c/44489/2/reference/extra-atcs22:05
*** kspear_ has joined #openstack-meeting22:05
*** jhenner has quit IRC22:05
*** Daisy has joined #openstack-meeting22:05
gabrielhurleythe Horizon team has the only two "extra ATCs" in OpenStack, 'cuz we're just that cool. :-)22:06
lblanchard:)22:06
jcoufal:) horizon is the best!22:06
jcoufalgo Horizon, we need more!22:06
lsmola_:-)22:07
gabrielhurleyOn a different but related note, I know you have all been waiting for the design summit session proposals to open. Well, I'm gonna steal thierry's thunder and leak the news that it's now live: http://summit.openstack.org/22:07
gabrielhurleythat'll go out to the ML sometime today or tomorrow22:07
gabrielhurleythe PTLs and such had early notification to make sure it was working and kick the tires22:07
gabrielhurleyso basically, go ahead and start proposing22:07
gabrielhurleypropose as much as you'd like. If I see things that are better suited to other topics, or similar proposals that can be combined I'll start contacting the porposers22:08
ttxgabrielhurley: jcoufal already noticed it22:08
gabrielhurleyI saw ;-)22:08
gabrielhurleyIt wasn't super-secret22:08
gabrielhurleyjust wasn't announced22:08
*** burt has quit IRC22:08
ttxI got lazy and did the beta opening on the public port22:08
jcoufalI am not a cheater, I was just lucky :)22:09
gabrielhurleyttx: tsk tsk. security would have a field day with you.22:09
gabrielhurley;-)22:09
gabrielhurleyanyhow, back to main business22:09
gabrielhurleySo, the Feature Freeze is EOD tomorrow. String Freeze coincides with that.22:09
*** jasondotstar has quit IRC22:09
*** armax has left #openstack-meeting22:09
Daisyany exceptions?22:10
gabrielhurleySo, be extra-mindful of changing translated strings in any bugfix reviews, etc. that happen in RC122:10
gabrielhurleyThere isn't really a formal process for "string freeze exceptions"22:10
gabrielhurleyso far it's just a "pay attention to what's changing and try not to do it"22:10
DaisyIf translation team run the Horizon in their locale environment, they may find some bugs.22:10
*** SumitNaiksatam has joined #openstack-meeting22:11
*** henrynash_ has joined #openstack-meeting22:11
Daisyare there a deadline for these bugs reporting?22:11
gabrielhurleyDaisy: I'd be happy to see bugs/patches from the translation team, because they're the ones being affected by it22:11
gabrielhurleyWe just have to make sure that the changes get sync'd between github and transifex if things do get changed22:11
Daisyso any string changing need to change the po files too.22:12
gabrielhurleyDaisy: when you set up the new translation resources, did you reconnect the auto-updating of the Transifex resources from github?22:12
DaisyI use this checkbox: auto sync.22:12
*** henrynash has quit IRC22:12
*** henrynash_ is now known as henrynash22:12
gabrielhurleyheh. sounds good22:12
Daisyonly en po files are enough.22:12
Daisyno need to change all.22:12
gabrielhurleyso as long as we run the script to update the base translation files those'll get sync'd over22:12
gabrielhurleyyep22:12
gabrielhurleyperfect22:12
Daisyyes, I think so.22:12
gabrielhurleyso like I was saying, be mindful of string changes. If you *do* see any, make sure that the base en po files get updated in the same commit so we can keep everything in sync22:13
Daisy"be extra-mindful of changing translated strings in any bugfix reviews, etc. that happen in RC1"22:13
*** sarob_ has joined #openstack-meeting22:13
Daisyis that mean, only before RC1 allow string changing?22:13
gabrielhurleyyep22:14
*** sarob_ has quit IRC22:14
gabrielhurleyat least "arbitrary" string changing22:14
Daisyor translation changing before RC1?22:14
*** sarob_ has joined #openstack-meeting22:14
gabrielhurleychanging strings marked for translation in the codebase22:14
jpichAny thought about a FFE for https://blueprints.launchpad.net/horizon/+spec/messages-on-login-page if the solution in the current review doesn't become more complex? (There would be string changes)22:14
gabrielhurleytbh I'm not up-to-date on the current solution there22:15
Daisywhen is RC1?22:15
*** markvan has quit IRC22:15
gabrielhurleyjpich: glancing at it currently that's probably reasonable for now. let's look to land that in the next 24 hours if we're going to.22:16
jpichIt uses a short-lived cookie to carry the log out reason. It's ok if it slips, though it would be a nice UX improvement especially when it comes to the new session timeouts (since no reason is given to the user at the moment)22:16
gabrielhurleyDaisy: RC1 will be cut on Thursday22:16
gabrielhurleyjpich: agreed22:17
*** sarob has quit IRC22:17
gabrielhurleylet me put the BP back into H322:17
jpichgabrielhurley: Ok, cheers22:17
*** AndChat-475904 has joined #openstack-meeting22:17
gabrielhurleyI think that's all the general business22:18
gabrielhurley#topic bleuprints22:18
*** openstack changes topic to "bleuprints (Meeting topic: horizon)"22:18
*** dcramer_ has quit IRC22:18
*** sarob has joined #openstack-meeting22:18
*** kspear_ has quit IRC22:19
gabrielhurleySo, we just added https://blueprints.launchpad.net/horizon/+spec/messages-on-login-page back to the list22:19
gabrielhurleythere seems to just be the one question about the whether the trans block in the template is appropriate or not, otherwise I see no reason that can't merge22:19
*** AndChat-475904 has quit IRC22:20
gabrielhurleyso the other BP remaining is https://blueprints.launchpad.net/horizon/+spec/horizon-cisco-n1k22:20
absubram_yes :)22:20
*** sarob_ has quit IRC22:21
gabrielhurleythere have been many many many iterations on that review. it currently has had all the comments addressed.22:21
absubram_yes.. hopefully it'll get a +1 from Paul and amotoki on this iteration?22:22
gabrielhurleyI feel like there may be some impetus to do a little reorganization in I, particularly when we're looking at navigation changes, but for now it seems like adding this in is probably still acceptable given the extreme isolation and narrow scope of the functionality...22:22
gabrielhurleyanyone else have other thoughts?22:22
david-lyleI honestly haven't had a chance to look through it yet, will try to tonight22:23
*** dscannell has quit IRC22:23
*** jmontemayor has quit IRC22:23
absubram_yes.. I definitely have to re-org the unit tests.. I'd really appreciate if we can get this infra in so that I can work on the enhancements in smaller diffs22:24
absubram_it is by default not turned on now though..22:24
absubram_it would be great if you could david-lyle22:24
amotoki_my concern is the navigation structure and i am not sure the policy of adding new dashboard.22:24
gabrielhurleythe navigation isn't ideal, but we can't really fix that in H and will revisit in I22:25
*** noslzzp has quit IRC22:25
amotoki_i hope other folks chimes in and hear their opinions.22:25
jcoufalIn I we would like to review information architecture for Horizon in general22:25
gabrielhurleyas for the policy of adding a new dashboard, there isn't one.22:25
gabrielhurleytbh I don't think it's the right solution here, but I'm not sure what it is22:25
david-lyleuse short names is the policy, I think22:25
gabrielhurleys/it is/is22:25
absubram_:)22:26
*** KurtMartin has quit IRC22:26
gabrielhurleythat's why I said earlier that I think we may want to move/reorganize this entire thing in I22:26
gabrielhurleyit's sort of a canary to see if we end up being okay with it or not22:26
david-lyleabsolutely22:26
gabrielhurleythen we can build a policy around that22:26
absubram_sure22:26
jcoufalagree22:26
lblanchardagreed22:27
amotoki_agree22:27
absubram_reorg I agree.. you;d like to move it itself?22:27
gabrielhurleybut absubram_ has made a very good faith effort this entire release cycle to get it in and I don't think he should be punished for us being unclear on what we want in this regard. ;-)22:27
lsmola_sounds reasonable22:27
absubram_haha.. thank you!22:27
david-lyle+122:27
*** jmontemayor has joined #openstack-meeting22:27
gabrielhurleylike I said, I don't love it being its own dashboard, but we don't *have* a home for this. we should come up with one at the summit22:27
absubram_I'm planning on proposing that already as a topic ;)22:27
*** changbl has quit IRC22:28
jcoufal+122:28
ftcjeff+122:28
lsmola_+122:28
gabrielhurleyit'll also dovetail with jcoufal's proposal on the future of UX Direction of the dashboard, but probably won't overlap depending on how you phrase things.22:28
gabrielhurleyso, +122:28
Toshi+122:29
gabrielhurleyalright, it sounds like we're generally okay with the functionality, and agree it should have *some* home in the dashboard, so let's go forward with it and try to get it reviewed and merged in the next 24 hours as well.22:29
absubram_thank you!22:29
absubram_:))22:29
david-lyleabsubram: thanks for sticking with it22:29
gabrielhurleygreat!22:30
gabrielhurley#topic bugs22:30
*** openstack changes topic to "bugs (Meeting topic: horizon)"22:30
jcoufalI think that the whole IA/navigation enhancements might get it's own session, I expect pretty big discussions around this22:30
jcoufal(sry late)22:30
gabrielhurleyagreed22:30
*** tanisdl has quit IRC22:30
gabrielhurleyReal quick I want to call attention to https://review.openstack.org/#/c/44929/ and https://review.openstack.org/#/c/44938/ that need an extra +2 for the H3 cut22:30
gabrielhurleyand wanted to point out that I've moved a few things that seemed urgent into https://launchpad.net/horizon/+milestone/havana-rc1 with the "high" priority22:31
gabrielhurleythat's about it for bugs at the moment22:31
*** tanisdl has joined #openstack-meeting22:31
*** cp16net has left #openstack-meeting22:31
gabrielhurleyone of those two reviews I posted will fix the docs generation, which will make me happy.22:32
jpichYay to working API references again22:32
*** dcramer_ has joined #openstack-meeting22:32
gabrielhurleythe docs being all broken made me sad22:32
david-lylehttps://bugs.launchpad.net/horizon/+bug/1212748 needs a release of openstack-auth to close22:32
uvirtbotLaunchpad bug 1212748 in horizon "log in for user with first project disabled fails" [High,In progress]22:32
gabrielhurleydavid-lyle: yep. I'm gonna do that today22:32
david-lyleok, thanks!22:32
*** eharney has joined #openstack-meeting22:33
gabrielhurleywe won't need to do anything in the hrizon requirements.txt, though, since it's currently a >=1.1.122:33
gabrielhurleyso I'll just bump the version on openstack-auth and push a new tag22:33
david-lylesounds good22:33
gabrielhurley#topic open discussion22:33
*** openstack changes topic to "open discussion (Meeting topic: horizon)"22:33
gabrielhurleyI think that's it for business that must be discussed this week22:33
*** debo_os has joined #openstack-meeting22:34
*** galstrom is now known as galstrom_zzz22:34
gabrielhurleythe next phase (RC1) is all about testing and polishing22:34
gabrielhurleyso be sure to, you know, *use* the dashboard and stuff. ;-)22:34
lsmola_:-)22:34
gabrielhurleyparticularly the new features like keystone domains/groups, heat, and ceilometer22:34
DaisyI think the translation team need very detail guideline to "use" dashboard.22:34
*** Brian___ has joined #openstack-meeting22:35
gabrielhurleyDaisy: devstack is the place to start. that gives you a full running openstack. from there I suggest looking at the docs teams' basic users guides22:35
Daisyhow can we get the guidelines? are there any test cases?22:35
*** topol has quit IRC22:35
gabrielhurleyI'm not sure what kind of guidelines/tests you're looking for?22:35
amotoki_now i am writing a guideline how to check their own translations  using devstack.22:35
Daisyamotoki_: when can it be ready?22:36
amotoki_will share this week.22:36
Daisythanks.22:36
gabrielhurleyamotoki_: great22:36
amotoki_now i am busy on review rushes22:36
DaisyI think I'm looking for the new features you point out.22:36
gabrielhurleyhopefully it's not much more than "run devstack, log in to horizon, go to user settings, change language"22:36
*** reed has joined #openstack-meeting22:36
gabrielhurleyfrom there "use the dashboard" is very nebulous, but describing how to use every feature of every project is the docs teams' purview and they already have substantial books on the subject22:37
gabrielhurleythere's no short answer22:37
amotoki_how to get translations from transifex , update po/mo files and so on.22:37
Daisyamotoki_ writes the guide lines to use the translations in their environment, not the test guideline.22:37
gabrielhurleyah22:37
gabrielhurleygotcha, like pulling down the translations from transifex22:37
gabrielhurleythat makes sense22:37
DaisyI think we need to regard translators as people who don't understand openstack that much.22:38
*** markpeek has quit IRC22:38
Daisybut they can do as what the guideline writes.22:38
Daisymaybe I will write such one for translation team.22:39
gabrielhurleyNo question there. I just don't think writing a separate set of "here's how to use an OpenStack cloud" for translators helps, because the informationshouldn't be different than for anyone else trying to use OpenStack, and if you write something too narrow then everyone looks at the exact same parts of the dashboard and that doesn't encourage getting good coverage.22:39
DaisyI will try to look for something from doc team.22:40
*** mrodden has quit IRC22:40
DaisyIf there are existing url, that would be very helpful.22:40
gabrielhurleyI'm not arguing there's a disconnect and that this is a problem, I just want to make sure we don't duplicate a lot of effort with docs22:40
*** dcramer_ has quit IRC22:40
gabrielhurleyDaisy: there definitely are things available online, I don't have a URL off the top of my head. ping annegentle on what she thinks would be most helpful.22:41
Daisyok.22:41
*** sarob has quit IRC22:41
*** sarob has joined #openstack-meeting22:41
gabrielhurleyany other topics on people's minds?22:42
absubram_david-lyle, amotoki_: just wanted to quickly point out.. I have a link in my blueprint on launchpad that points to a short demo on how the new dashboard was used internally when using the cisco n1k plugin..22:42
Daisyanother question from me: when can you allow us to import the translations to the code repository? Are there any deadline? Are there any pre-conditions?22:42
amotoki_gabrielhurley: what do you think about FWaaS and VPNaaS support?22:42
amotoki_Should they go to icehouse?22:42
gabrielhurleyamotoki_: great targets for I122:42
absubram_if it helps with the review and understanding :)22:42
amotoki_I think so.22:42
amotoki_they are not tested enough from my impression.22:43
gabrielhurleyDaisy: the final deadline will be the day before we cut the Havana final release. That'll be several weeks at least. I don't have an exact date.22:43
gabrielhurleyIf it would be helpful to commit interim sets of changes we can do that too22:43
*** otherwiseguy has quit IRC22:43
jcoufalone more topic here about IE support22:43
*** weshay has quit IRC22:43
Daisyok.22:43
jcoufalthere is BP around upgrading Bootstrap to v322:44
jcoufalv3 doesn't support IE6 and IE722:44
gabrielhurleyamotoki_: I agree on the testing. I want to make sure they get a lot more robust before we land them, and/or that we land them at the beginning of a release cycle instead of the end like LBaaS in G22:44
jcoufalso the question to the discussion here is if that's any problem for Horizon22:44
david-lylejcoufal: I think IE9+ would be a good support list22:44
Daisygabrielhurley: so there is also no bug reporting deadlines, right? just before final release?22:44
*** markmcclain has quit IRC22:44
gabrielhurleyjcoufal: IE6 and 7 are categorically off the table22:44
jcoufalMy opinion is that we might be safe stating that we support IE8 or IE9+22:44
gabrielhurleyI've been delaying the decision on IE8 because the final final extended support drpo date for microsoft in April 201422:45
lsmola_d3 library has ie9+ I think22:45
jcoufalgabrielhurley: great, just wanted to assure with more people22:45
gabrielhurleyafter April 2014 I'm calling Horizon IE9+ and that's the end of it22:45
*** ocozalp has joined #openstack-meeting22:45
lsmola_+122:45
jcoufalBootstrap is IE8+, so we are safe22:45
gabrielhurleyDaisy: nope, no deadline for bugs22:45
jcoufal+1 for 2014 IE9+22:45
jcoufalthanks22:46
Daisyok. thanks.22:46
lblanchard+122:46
Toshi+122:46
gabrielhurleyIn practice that actually means we need to decide between dropping IE8 for Icehouse Final (which will be released in ~March 2014) or in J1... we'll talk about that later though22:46
*** sarob has quit IRC22:46
david-lyleother than anything graphical IE8 works currently22:47
gabrielhurleyyep22:47
david-lyleis there a max number of design sessions for Horizon?22:48
david-lyleor is it demand based22:48
gabrielhurleywe do have a limited number of slots22:48
gabrielhurleybut there's usually a little wiggle room22:48
*** alexpilotti has quit IRC22:48
*** eglynn has quit IRC22:48
gabrielhurleyoff the top of my head I don't recall the exact number22:49
gabrielhurleyit's usually 6 or 722:49
gabrielhurleyit's gonna be split across two days this time22:49
gabrielhurleyso we'll have a couple early in the week and a couple towards the end22:49
gabrielhurleyI think it's Tuesday and Thursday, offhand22:49
*** ftcjeff has quit IRC22:49
lblanchardah that will be nice to split them...22:49
gabrielhurleyyeah22:49
david-lyleThe pagination item obviously effects all services, so hopefully we'll have good turnout from those groups22:49
gabrielhurleyalso, I'm leaving halfway through Friday, so I couldn't schedule any then22:50
gabrielhurleydavid-lyle: yeah. I'll do what I can to not schedule it against any other critical cross-project sessions22:50
gabrielhurleythis always comes up22:50
david-lyleI suppose designated cross-project sessions would be too noisy22:51
gabrielhurleyI've advocated for a "cross-project" track before and it's never gotten much traction22:52
Daisygabrielhurley: just come up a question: do you know if there is a formal team to test Horizion?22:52
gabrielhurley"test Horizon" how?22:52
Daisyis QA team responsible for the test ?22:52
gabrielhurleythe answer is probably "no" regardless22:52
Daisyjust run and test.22:52
*** ocozalp has quit IRC22:52
gabrielhurleyInfra/QA manage the infrastructure that *runs* the tests and gates all the projects. We write our own tests, though.22:52
Daisyunit test ?22:53
ekarlso-gabrielhurley: how goes the notificitions stuff?22:53
Daisyok. I think I get it. so there is no functional test. Like set up the env, and run to see if there are problems.22:53
*** mrodden has joined #openstack-meeting22:54
gabrielhurleyDaisy: there are some superficial selenium tests, but not nearly as in-depth as they should be22:54
gabrielhurleyekarlso-: what notifications stuff?22:54
ekarlso-live notifications or what the bp is called again22:55
amotoki_Daisy: almost all projects have only unit tests and few functional tests. devstack-tempest and smokestack are the only system tests.22:55
david-lylereal-time?22:55
ekarlso-yes22:55
Daisythanks, amotoki_22:55
gabrielhurleyekarlso-: push to the I release so we can spend a lot of time on it22:55
gabrielhurleywe had a ton on our plate supporting two new projects and new APIs in H22:55
ekarlso-gabrielhurley: that sucks :p22:55
gabrielhurleymore contributors makes things go faste... ;-)22:56
lsmola_:-)22:56
gabrielhurleybut it's a significant priority for everyone from a "we know we want to get there and that'll be really cool" standpoint22:56
*** mrodden1 has joined #openstack-meeting22:56
ekarlso-gabrielhurley: heh, too bad I got way to much atm :p22:56
gabrielhurleythere's some POC code available from Tomas Sedovic (sorry if I spelled that wrong off the top of my head)22:56
gabrielhurleythat'll serve as a good foundation/discussion point in the next cycle22:57
ekarlso-gabrielhurley: it always seems the tasty candy gets postponed to the next release though ?22:57
lsmola_no it is right22:57
gabrielhurleynot always22:57
gabrielhurleywe just do as much as we can22:57
gabrielhurleysometimes that's more, sometimes less22:57
*** gokrokve has quit IRC22:57
lsmola_the realtime communiction is almost complete22:57
gabrielhurleythis one is *huge*, though22:57
gabrielhurleyand we have to get it right22:57
gabrielhurleyit's not one we can land late in a cycle and just sort of let sit there22:57
gabrielhurleypeople expect a lot out of this22:57
gabrielhurleyand getting it wrong will frustrate users and deployers alike22:58
*** MarkAtwood has joined #openstack-meeting22:58
gabrielhurleyFrom my current vantage point I don't see it *not* landing in I22:58
rdxcare you planing to abstract the message broker or just use RMQ and call it done22:58
*** mrodden has quit IRC22:58
ekarlso-gabrielhurley: how early you think in I ?22:58
*** armax has joined #openstack-meeting22:59
lsmola_ekarlso-, giving some feedback to the realtime communication patches would be very good :-)22:59
gabrielhurleyrdxc: there's an element of using the code in oslo to listen on the message bus, but our browser <--> server channel is websockets22:59
gabrielhurleyekarlso-: no idea22:59
gabrielhurleyask again after the summit22:59
ekarlso-ok :p23:00
lsmola_ekarlso-, it all depends of how many people will give feedback23:00
gabrielhurleywe've all been focused on getting Havana out, with all the good things that *are* in it23:00
rdxcok, we built this architecture out in rails w/ web sockets for HPCS23:00
gabrielhurleynow we get to start looking forward again today23:00
rdxcwe learned much from that23:00
gabrielhurleyrdxc: would lov to hear your learnings. will you be at the summit by any chance?23:00
rdxcgetting the underlying plumbing is key to scale23:00
*** danwent has joined #openstack-meeting23:01
rdxcno, but I'll make sure @david-lyle is properly armed23:01
*** mrodden1 is now known as mrodden23:01
gabrielhurleyfwiw, Nebula's dashboard also relies on websockets (and we've worked towards direct browser to service communication via CORS lately, too), so I've learned a few things myself. :-)23:01
gabrielhurleyawesome23:01
gabrielhurleyoh, we're out of time23:02
gabrielhurleyany last minute urgent items?23:02
*** jlucci has joined #openstack-meeting23:02
gabrielhurleylast call23:02
lsmola_nope23:02
david-lyleThanks!23:02
gabrielhurleyThanks everyone. You've all done great! H3 is jam-packed full of goodness.23:02
lblanchardthanks all!23:02
gabrielhurleytalk to you next wek23:02
amotoki_thanks!23:02
gabrielhurley#endmeeting23:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:02
openstackMeeting ended Tue Sep  3 23:02:44 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:02
absubram_thanks!23:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-09-03-22.01.html23:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-09-03-22.01.txt23:02
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-09-03-22.01.log.html23:02
jpichThanks23:02
lsmola_thanks all, bye23:03
ekarlso-gabrielhurley: I'm doing a UI in AngularJS for OpenDaylight. Already using CORS support for all its apis23:03
*** sarob has joined #openstack-meeting23:03
jcoufalthanks! good bye guys23:03
*** jpich has quit IRC23:03
gabrielhurleyekarlso-: yeah, the tough bit is that doing CORS right requires so much consideration from a security standpoint. There's no generic "deploy it this way"23:03
ekarlso-gabrielhurley: how come ?23:04
jcoufalekarlso-: We played with AngularJS in some UIs as well23:04
ekarlso-jcoufal: who23:04
ekarlso-is we ? :)23:04
gabrielhurleyAll the headers that need to be set.23:04
lsmola_ekarlso-, :-)23:04
gabrielhurleyAllow: * is not a good answer23:04
jcoufalekarlso-: haha, our team in Red Hat23:04
gabrielhurleyplus you need to specifically authorize header access for each header you want on the CORS requests, etc.23:05
ekarlso-jcoufal: ok :)23:05
ekarlso-jcoufal: any upstream uis using it ?23:05
*** amotoki_ has quit IRC23:05
*** amotoki_ has joined #openstack-meeting23:05
gabrielhurleyanyhow, I'm off. later folks.23:06
*** gabrielhurley has quit IRC23:06
lsmola_see you next week23:06
jcoufalekarlso-: we are playing with library of UI components written in AngularJS (lately we couldn't pay much attention to it though) - https://github.com/ui-alchemy23:06
lsmola_I am also off,I am sleepy23:07
lsmola_see you guys23:07
jcoufalekarlso-: plus https://github.com/wingedmonkey/wingedmonkey, also no activty lately23:07
jcoufalit was already some time ago23:07
ekarlso-is all that in angular ?23:07
*** lsmola_ has quit IRC23:08
*** absubram_ has quit IRC23:08
jcoufalekarlso-: not ocmpletely, just parts23:08
jcoufalin the UI library, there is ongoing development on full angular support for tables (with various features)23:09
ekarlso-jcoufal: tables like ?23:09
ekarlso-bootstrap or grid?23:09
*** markpeek has joined #openstack-meeting23:09
ekarlso-jcoufal: http://odl.cloudistic.me23:10
ekarlso-OpenDayligt UI in AngularJS23:10
jcoufalekarlso-: data-tables, with filtering, sorting, searching, selections, inline editation, etc23:11
jcoufalekarlso-: http://demo.wingedmonkey.org/login - winged monkey demo23:12
*** vkmc has quit IRC23:12
jcoufalekarlso-: just can't log in23:13
*** esker has quit IRC23:13
jcoufalneed to run away, thanks guys, ttys23:15
*** jcoufal has quit IRC23:16
*** sarob has quit IRC23:19
*** Guest26207 is now known as zz_Guest2620723:19
*** sarob has joined #openstack-meeting23:19
*** shardy is now known as shardy_afk23:21
*** rdxc has quit IRC23:21
*** markwash has quit IRC23:22
*** KurtMartin has joined #openstack-meeting23:23
*** sarob has quit IRC23:24
*** KurtMartin has quit IRC23:24
*** esheffield has quit IRC23:24
*** jmontemayor has quit IRC23:24
*** dcramer_ has joined #openstack-meeting23:25
*** SumitNaiksatam has quit IRC23:28
*** debo_os has quit IRC23:29
*** cdub has quit IRC23:29
*** lblanchard has quit IRC23:32
*** carl_baldwin has quit IRC23:35
*** vipul is now known as vipul-away23:37
*** stevemar has quit IRC23:40
*** zz_Guest26207 is now known as leif23:41
*** leif is now known as Guest1217223:41
*** changbl has joined #openstack-meeting23:42
*** vipul-away is now known as vipul23:44
*** SumitNaiksatam has joined #openstack-meeting23:46
*** cdub has joined #openstack-meeting23:47
*** sarob has joined #openstack-meeting23:50
*** sarob has quit IRC23:51
*** kebray has quit IRC23:51
*** Guest12172 is now known as zz_Guest1217223:53
*** IlyaE has quit IRC23:55
*** diogogmt has quit IRC23:58

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