Tuesday, 2013-08-20

*** SumitNaiksatam has quit IRC00:03
*** stevemar2 has joined #openstack-meeting00:05
*** vaml1 has quit IRC00:07
*** markpeek has joined #openstack-meeting00:07
*** stevemar has quit IRC00:08
*** jasondotstar has joined #openstack-meeting00:12
*** jlucci has joined #openstack-meeting00:13
*** flaper87 is now known as flaper87|afk00:14
*** nati_ueno has quit IRC00:17
*** jlucci has quit IRC00:21
*** spzala has joined #openstack-meeting00:23
*** bdpayne has quit IRC00:25
*** Jaesang has joined #openstack-meeting00:26
*** lexinator has quit IRC00:26
*** nati_ueno has joined #openstack-meeting00:29
*** SumitNaiksatam has joined #openstack-meeting00:33
*** dvarga has joined #openstack-meeting00:33
*** rwsu is now known as rwsu-away00:38
*** michchap has joined #openstack-meeting00:39
*** lexinator has joined #openstack-meeting00:40
*** ivar-lazzaro has quit IRC00:42
*** stevemar2 has quit IRC00:48
*** jackmccann has left #openstack-meeting00:50
*** jlucci has joined #openstack-meeting00:52
*** novas0x2a|laptop has quit IRC00:53
*** anteaya has quit IRC00:58
*** haomaiwang has quit IRC00:59
*** haomaiwang has joined #openstack-meeting01:00
*** lbragstad has joined #openstack-meeting01:02
*** beagles has quit IRC01:06
*** dvarga has quit IRC01:09
*** alexb_ has quit IRC01:11
*** roampune has joined #openstack-meeting01:23
*** fnaval_ has joined #openstack-meeting01:27
*** fnaval_ has quit IRC01:28
*** fnaval_ has joined #openstack-meeting01:28
*** martine has joined #openstack-meeting01:37
*** martine is now known as Guest8361101:38
*** topshare has quit IRC01:41
*** leif has joined #openstack-meeting01:41
*** dcramer_ has joined #openstack-meeting01:41
*** leif is now known as Guest2339801:41
*** leif_ has quit IRC01:42
*** alexb_ has joined #openstack-meeting01:47
*** dscannell has joined #openstack-meeting01:47
*** lexinator has quit IRC01:49
*** dcramer_ has quit IRC01:55
*** nati_ueno has quit IRC01:57
*** jlucci has quit IRC02:01
*** jrodom has joined #openstack-meeting02:04
*** tanisdl has quit IRC02:10
*** gongysh has joined #openstack-meeting02:10
*** yaguang has joined #openstack-meeting02:11
*** lexinator has joined #openstack-meeting02:12
*** xBsd has joined #openstack-meeting02:16
*** herndon has joined #openstack-meeting02:16
*** leif_ has joined #openstack-meeting02:20
*** stevemar has joined #openstack-meeting02:22
*** lbragstad has quit IRC02:22
*** Guest23398 has quit IRC02:23
*** dscannell has quit IRC02:26
*** radez is now known as radez_g0n302:32
*** jasondotstar has quit IRC02:40
*** asalkeld is now known as asalkeld_lunch02:45
*** jasondotstar has joined #openstack-meeting02:46
*** ayoung is now known as ayoung-zZzZzZz02:47
*** ayoung-zZzZzZz has quit IRC02:48
*** roampune has quit IRC02:50
*** lexinator has quit IRC03:00
*** herndon has quit IRC03:01
*** afazekas_zz is now known as __afazekas_zz03:02
*** markmcclain has quit IRC03:05
*** terriyu has quit IRC03:08
*** neelashah has joined #openstack-meeting03:12
*** yuan has joined #openstack-meeting03:13
*** lexinator has joined #openstack-meeting03:22
*** HenryG has quit IRC03:25
*** bdpayne has joined #openstack-meeting03:30
*** bdpayne has quit IRC03:31
*** herndon has joined #openstack-meeting03:31
*** zul has quit IRC03:31
*** herndon has quit IRC03:32
*** haomaiwa_ has joined #openstack-meeting03:33
*** haomaiwang has quit IRC03:36
*** termie has quit IRC03:40
*** afazekas has joined #openstack-meeting03:42
*** termie has joined #openstack-meeting03:42
*** termie has quit IRC03:42
*** termie has joined #openstack-meeting03:42
*** boris-42 has joined #openstack-meeting03:49
*** Guest83611 has quit IRC03:53
*** xBsd has quit IRC03:53
*** mberwanger has joined #openstack-meeting03:59
*** yaguang has quit IRC03:59
*** gongysh has quit IRC04:01
*** michchap_ has joined #openstack-meeting04:04
*** dcramer_ has joined #openstack-meeting04:06
*** eharney has joined #openstack-meeting04:08
*** michchap has quit IRC04:08
*** rongze has joined #openstack-meeting04:09
*** dcramer_ has quit IRC04:11
*** yaguang has joined #openstack-meeting04:12
*** MarkAtwood has quit IRC04:12
*** spzala has quit IRC04:17
*** dcramer_ has joined #openstack-meeting04:24
*** rongze_ has joined #openstack-meeting04:30
*** rongze has quit IRC04:33
*** asalkeld_lunch is now known as asalkeld04:34
*** mberwanger has quit IRC04:38
*** dcramer_ has quit IRC04:42
*** terriyu has joined #openstack-meeting04:45
*** xBsd has joined #openstack-meeting04:47
*** neelashah has quit IRC04:48
*** yuan has quit IRC04:48
*** reed has quit IRC04:53
*** yaguang has quit IRC04:59
*** dmakogon_ has joined #openstack-meeting05:08
*** garyk has quit IRC05:08
*** yaguang has joined #openstack-meeting05:12
*** alexb_ has quit IRC05:22
*** SergeyLukjanov has joined #openstack-meeting05:23
*** topshare has joined #openstack-meeting05:25
*** alexb_ has joined #openstack-meeting05:25
*** edmund has quit IRC05:26
*** shang has joined #openstack-meeting05:26
*** kbs1 has quit IRC05:27
*** kbs has joined #openstack-meeting05:30
*** mrunge has joined #openstack-meeting05:34
*** mrunge has quit IRC05:34
*** topshare has quit IRC05:35
*** markwash has joined #openstack-meeting05:35
*** topshare has joined #openstack-meeting05:36
*** topshare has quit IRC05:45
*** topshare has joined #openstack-meeting05:45
*** mrunge has joined #openstack-meeting05:46
*** lexinator has quit IRC05:47
*** thomasbiege has joined #openstack-meeting05:48
*** garyk has joined #openstack-meeting05:49
*** markpeek has quit IRC05:54
*** mikal has quit IRC05:55
*** topshare has quit IRC05:56
*** thomasbiege1 has joined #openstack-meeting05:59
*** thomasbiege has quit IRC06:02
*** stevemar has quit IRC06:04
*** haomaiwa_ has quit IRC06:06
*** topshare has joined #openstack-meeting06:13
*** thomasbiege1 has quit IRC06:13
*** eharney has quit IRC06:14
*** thomasbiege has joined #openstack-meeting06:17
*** doron_afk has joined #openstack-meeting06:29
*** flaper87|afk is now known as flaper8706:40
*** tian has quit IRC06:44
*** SergeyLukjanov has quit IRC06:50
*** jhenner has joined #openstack-meeting06:53
*** tkammer has joined #openstack-meeting06:59
*** michchap has joined #openstack-meeting07:00
*** michchap_ has quit IRC07:02
*** egallen has joined #openstack-meeting07:06
*** sjing has joined #openstack-meeting07:10
*** jcoufal has joined #openstack-meeting07:10
*** jaimegil has joined #openstack-meeting07:11
*** SergeyLukjanov has joined #openstack-meeting07:11
*** rods has joined #openstack-meeting07:12
*** SergeyLukjanov has quit IRC07:14
*** ruhe has joined #openstack-meeting07:26
*** gongysh has joined #openstack-meeting07:33
*** boris-42 has quit IRC07:34
*** jtomasek has joined #openstack-meeting07:35
*** ndipanov_gone is now known as ndipanov07:36
*** SergeyLukjanov has joined #openstack-meeting07:38
*** michchap has quit IRC07:39
*** michchap has joined #openstack-meeting07:39
*** markwash has quit IRC07:49
*** michchap has quit IRC07:52
*** sushils has joined #openstack-meeting07:55
*** morganfainberg is now known as morganfainberg|a07:55
*** SergeyLukjanov has quit IRC08:00
*** sushils has quit IRC08:04
*** derekh has joined #openstack-meeting08:06
*** topshare has quit IRC08:13
*** hua has joined #openstack-meeting08:20
*** hua has quit IRC08:26
*** hua has joined #openstack-meeting08:27
*** psedlak has joined #openstack-meeting08:27
*** SergeyLukjanov has joined #openstack-meeting08:27
*** complexmind has joined #openstack-meeting08:36
*** boris-42 has joined #openstack-meeting08:40
*** johnthetubaguy has joined #openstack-meeting08:47
*** johnthetubaguy1 has joined #openstack-meeting08:49
*** Jaesang has quit IRC08:50
*** johnthetubaguy has quit IRC08:52
*** doron_afk is now known as doron08:53
*** sjing has quit IRC08:54
*** sushils has joined #openstack-meeting08:56
*** doron is now known as doron_afk09:13
*** doron_afk is now known as doron09:27
*** johnthetubaguy1 is now known as johnthetubaguy09:29
*** doron is now known as doron_afk09:30
*** SergeyLukjanov has quit IRC09:32
*** rongze has joined #openstack-meeting09:36
*** rongze_ has quit IRC09:39
*** rohitk has joined #openstack-meeting09:40
*** yaguang has quit IRC09:43
*** shang has quit IRC10:00
*** ruhe has quit IRC10:12
*** alexpilotti has joined #openstack-meeting10:12
*** ruhe has joined #openstack-meeting10:21
*** thomasbiege has quit IRC10:28
*** ocozalp has joined #openstack-meeting10:28
*** gongysh has quit IRC10:28
*** egallen has quit IRC10:30
*** SergeyLukjanov has joined #openstack-meeting10:37
*** ocozalp has quit IRC10:41
*** jasondotstar has quit IRC10:45
*** doron_afk is now known as doron10:47
*** lpabon has joined #openstack-meeting10:55
*** martine has joined #openstack-meeting10:57
*** dosaboy_ has joined #openstack-meeting10:57
*** martine is now known as Guest6749910:57
*** dosaboy has quit IRC10:59
*** topshare has joined #openstack-meeting11:02
*** thomasbiege has joined #openstack-meeting11:02
*** christophk is now known as cmk11:06
*** doron is now known as doron_afk11:06
*** hua has quit IRC11:07
*** SergeyLukjanov has quit IRC11:12
*** zul has joined #openstack-meeting11:19
*** sjing has joined #openstack-meeting11:24
*** ruhe has quit IRC11:32
*** SergeyLukjanov has joined #openstack-meeting11:39
*** tkammer has quit IRC11:44
*** doron_afk has quit IRC11:44
*** SergeyLukjanov has quit IRC11:44
*** tkammer has joined #openstack-meeting11:44
*** doron_afk has joined #openstack-meeting11:44
*** zul has quit IRC11:46
*** doron_afk is now known as doron11:46
*** pcm_ has joined #openstack-meeting11:46
*** lpabon has joined #openstack-meeting11:49
*** HenryG has joined #openstack-meeting11:49
*** egallen has joined #openstack-meeting11:55
*** topshare has quit IRC11:58
*** afazekas is now known as afazekas_no_irq11:59
*** radez_g0n3 is now known as radez11:59
*** yaguang has joined #openstack-meeting12:02
*** ruhe has joined #openstack-meeting12:06
*** lpabon has quit IRC12:17
*** doron is now known as doron_afk12:19
*** sandywalsh has quit IRC12:22
*** sandywalsh has joined #openstack-meeting12:24
*** dvarga has joined #openstack-meeting12:26
*** anteaya has joined #openstack-meeting12:28
*** jaimegil has quit IRC12:30
*** lblanchard has joined #openstack-meeting12:32
*** SergeyLukjanov has joined #openstack-meeting12:35
*** ruhe has quit IRC12:36
*** zul has joined #openstack-meeting12:37
*** rods1 has joined #openstack-meeting12:37
*** leif_ has quit IRC12:39
*** dprince has joined #openstack-meeting12:39
*** dkranz has joined #openstack-meeting12:39
*** rods has quit IRC12:40
*** ocozalp has joined #openstack-meeting12:40
*** troytoman-away is now known as troytoman12:44
*** topshare has joined #openstack-meeting12:46
*** ruhe has joined #openstack-meeting12:47
*** SergeyLukjanov has quit IRC12:47
*** eric__ has joined #openstack-meeting12:49
*** jasondotstar has joined #openstack-meeting12:49
*** cbaesema has quit IRC12:50
*** cbaesema has joined #openstack-meeting12:51
*** fnaval_ has quit IRC12:52
*** eric__ has left #openstack-meeting12:52
*** eric__ has joined #openstack-meeting12:52
*** eric__ has joined #openstack-meeting12:53
*** eric__ has quit IRC12:54
*** jrodom has quit IRC12:54
*** dkranz has quit IRC12:55
*** ocozalp has left #openstack-meeting12:56
*** brucer has joined #openstack-meeting12:59
*** jog0 is now known as jog0-away13:01
*** mberwanger has joined #openstack-meeting13:01
*** brucer has quit IRC13:02
*** edmund has joined #openstack-meeting13:02
*** adalbas has quit IRC13:03
*** nmiller has joined #openstack-meeting13:03
*** tssgery has joined #openstack-meeting13:07
*** nmiller has quit IRC13:07
*** eharney has joined #openstack-meeting13:07
*** kiall has quit IRC13:08
*** nmiller has joined #openstack-meeting13:09
*** shang has joined #openstack-meeting13:11
*** changbl has quit IRC13:12
*** fnaval_ has joined #openstack-meeting13:14
*** doron_afk is now known as doron13:17
*** jrodom has joined #openstack-meeting13:19
*** jrodom has quit IRC13:19
*** jrodom has joined #openstack-meeting13:19
*** rods1 has quit IRC13:20
*** rods has joined #openstack-meeting13:20
*** vijendar has joined #openstack-meeting13:20
*** dscannell has joined #openstack-meeting13:22
*** dcramer_ has joined #openstack-meeting13:23
*** egallen has quit IRC13:24
*** markpeek has joined #openstack-meeting13:26
*** stevemar has joined #openstack-meeting13:27
*** lbragstad has joined #openstack-meeting13:27
*** HenryG has quit IRC13:27
*** egallen has joined #openstack-meeting13:28
*** egallen has quit IRC13:29
*** litong has joined #openstack-meeting13:29
*** michchap has joined #openstack-meeting13:30
*** egallen has joined #openstack-meeting13:30
*** egallen has quit IRC13:30
*** mberwanger has quit IRC13:35
*** garyk has quit IRC13:39
*** marcinx21 has joined #openstack-meeting13:40
*** neelashah has joined #openstack-meeting13:41
*** burt has joined #openstack-meeting13:42
*** thomasbiege2 has joined #openstack-meeting13:43
*** ayoung has joined #openstack-meeting13:45
*** thomasbiege has quit IRC13:46
*** egallen has joined #openstack-meeting13:48
*** dscannell has quit IRC13:49
*** whenry has joined #openstack-meeting13:50
*** hyson has joined #openstack-meeting13:50
*** esker has joined #openstack-meeting13:51
*** hyson is now known as Guest2417413:51
*** shang has quit IRC13:52
*** Guest24174 has left #openstack-meeting13:52
*** KurtMartin has joined #openstack-meeting13:57
*** bgorski has joined #openstack-meeting13:57
*** michchap has quit IRC13:57
*** markvan has joined #openstack-meeting13:58
*** yingjun has joined #openstack-meeting13:58
*** jodom has joined #openstack-meeting14:00
*** marcinx21 has quit IRC14:00
*** Guest67499 is now known as martine_14:01
*** martine_ has quit IRC14:01
*** martine has joined #openstack-meeting14:01
*** martine is now known as martine_14:01
*** edmund has quit IRC14:02
*** eharney has quit IRC14:03
*** rwsu-away is now known as rwsu14:03
*** jrodom has quit IRC14:04
*** Fdot has joined #openstack-meeting14:05
*** markvan_ has joined #openstack-meeting14:07
*** egallen has quit IRC14:09
*** eharney has joined #openstack-meeting14:09
*** markvan has quit IRC14:10
*** markvan_ is now known as markvan14:10
*** MarkAtwood has joined #openstack-meeting14:10
*** xBsd has quit IRC14:10
*** xBsd has joined #openstack-meeting14:10
*** egallen has joined #openstack-meeting14:11
*** xBsd has quit IRC14:12
*** shang has joined #openstack-meeting14:14
*** shang has quit IRC14:15
*** spenceratx has joined #openstack-meeting14:16
*** lpabon has joined #openstack-meeting14:16
*** changbl has joined #openstack-meeting14:20
*** kevinconway has left #openstack-meeting14:20
*** KurtMartin has quit IRC14:21
*** xBsd has joined #openstack-meeting14:21
*** marc_p has left #openstack-meeting14:22
*** jodom has quit IRC14:23
*** dvarga_ has joined #openstack-meeting14:23
*** jrodom has joined #openstack-meeting14:23
*** jcoufal has quit IRC14:23
*** dvarga has quit IRC14:25
*** jrodom has quit IRC14:25
*** spzala has joined #openstack-meeting14:25
*** hemna has quit IRC14:26
*** jtomasek has quit IRC14:26
*** sjing has quit IRC14:27
*** beagles has joined #openstack-meeting14:28
*** thomasbiege2 has quit IRC14:28
*** kevinconway has joined #openstack-meeting14:31
*** Fdot has quit IRC14:31
*** vkmc has joined #openstack-meeting14:31
*** topshare has quit IRC14:32
*** lblanchard1 has joined #openstack-meeting14:32
*** shang has joined #openstack-meeting14:32
*** alexb_ has quit IRC14:33
*** shang has quit IRC14:34
*** lblanchard has quit IRC14:34
*** jmontemayor has joined #openstack-meeting14:35
*** armax has joined #openstack-meeting14:36
*** doron is now known as doron_afk14:37
*** topshare has joined #openstack-meeting14:37
*** markmcclain has joined #openstack-meeting14:37
*** ruhe has quit IRC14:38
*** Fdot has joined #openstack-meeting14:38
*** otherwiseguy has joined #openstack-meeting14:39
*** yaguang has quit IRC14:40
*** __afazekas_zz has quit IRC14:41
*** nmiller has quit IRC14:41
*** jtomasek has joined #openstack-meeting14:42
*** hartsocks has joined #openstack-meeting14:46
*** lexinator has joined #openstack-meeting14:46
*** wolfdreamer has joined #openstack-meeting14:46
*** hartsocks has left #openstack-meeting14:46
*** derekh has quit IRC14:50
*** SergeyLukjanov has joined #openstack-meeting14:51
*** jcoufal has joined #openstack-meeting14:55
* lsmola is away: Away14:56
*** kebray has joined #openstack-meeting14:56
*** david-lyle has quit IRC14:57
*** thang_ has joined #openstack-meeting14:58
*** doron_afk has quit IRC14:59
*** sushils has quit IRC15:01
*** sandywalsh has quit IRC15:01
*** tanisdl has joined #openstack-meeting15:02
*** topshare has quit IRC15:02
*** topshare has joined #openstack-meeting15:03
*** sushils has joined #openstack-meeting15:05
*** shanewang1 has joined #openstack-meeting15:05
*** lexinator has quit IRC15:05
*** dscannell has joined #openstack-meeting15:05
*** markwash has joined #openstack-meeting15:06
*** topshare has quit IRC15:08
*** ruhe has joined #openstack-meeting15:08
*** shanewang1 has quit IRC15:09
*** leif has joined #openstack-meeting15:11
*** leif is now known as Guest1018515:11
*** Guest10185 has quit IRC15:11
*** xBsd has quit IRC15:12
*** Fdot has quit IRC15:13
*** bashok has joined #openstack-meeting15:14
*** leif_ has joined #openstack-meeting15:14
*** lexinator has joined #openstack-meeting15:15
*** david-lyle has joined #openstack-meeting15:16
*** jlucci has joined #openstack-meeting15:16
*** sandywalsh has joined #openstack-meeting15:17
*** ruhe has quit IRC15:20
*** lexinator has quit IRC15:20
*** sacharya has joined #openstack-meeting15:21
*** jcoufal has quit IRC15:21
*** ruhe has joined #openstack-meeting15:22
*** jmontemayor has quit IRC15:22
*** reed has joined #openstack-meeting15:23
*** lexinator has joined #openstack-meeting15:24
*** lexinator1 has joined #openstack-meeting15:25
*** lexinator has quit IRC15:25
*** ivasev has joined #openstack-meeting15:25
*** jmontemayor has joined #openstack-meeting15:25
*** rohitk has quit IRC15:26
*** patelna has joined #openstack-meeting15:27
*** MarkAtwood has quit IRC15:30
*** rods has quit IRC15:32
*** yingjun has quit IRC15:33
*** rods has joined #openstack-meeting15:33
*** bdpayne has joined #openstack-meeting15:35
*** lexinator1 has quit IRC15:36
*** Mandell has quit IRC15:37
*** jmontemayor has quit IRC15:41
*** afazekas_no_irq is now known as afazekas15:42
*** thomasbiege has joined #openstack-meeting15:42
*** jmontemayor has joined #openstack-meeting15:45
*** rnirmal has joined #openstack-meeting15:46
*** lblanchard1 has quit IRC15:46
*** zehicle_at_dell has joined #openstack-meeting15:47
*** troytoman is now known as troytoman-away15:48
*** lblanchard has joined #openstack-meeting15:50
*** changbl has quit IRC15:51
*** mrodden has quit IRC15:53
*** ociuhandu has joined #openstack-meeting15:53
*** alexb_ has joined #openstack-meeting15:53
*** davidhadas has quit IRC15:54
*** lexinator has joined #openstack-meeting15:54
*** ruhe has quit IRC15:55
*** jcoufal has joined #openstack-meeting15:57
*** hanrahat has joined #openstack-meeting15:58
*** xBsd has joined #openstack-meeting15:59
*** jmontemayor has quit IRC16:00
*** tkammer has quit IRC16:00
*** complexmind has quit IRC16:00
*** dcramer_ has quit IRC16:02
*** mrodden has joined #openstack-meeting16:04
*** schwicht has joined #openstack-meeting16:05
*** MarkAtwood has joined #openstack-meeting16:05
*** gyee has joined #openstack-meeting16:05
alexpilotti#startmeeting hyper-v16:06
openstackMeeting started Tue Aug 20 16:06:43 2013 UTC and is due to finish in 60 minutes.  The chair is alexpilotti. Information about MeetBot at http://wiki.debian.org/MeetBot.16:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:06
*** openstack changes topic to " (Meeting topic: hyper-v)"16:06
openstackThe meeting name has been set to 'hyper_v'16:06
*** isviridov has quit IRC16:06
alexpilottiPeter is flying to the Puppet conf16:07
*** isviridov has joined #openstack-meeting16:07
alexpilottiso I'm gonna be your host today :-)16:07
alexpilottiwho's in the meeting?16:07
ociuhanduhi all16:07
alexpilotticrowded, today :-)16:08
alexpilotti#topic blueprints16:08
*** openstack changes topic to "blueprints (Meeting topic: hyper-v)"16:08
alexpilottiAll the Bps we are targeting for Havana are under review16:08
alexpilottiwe're responding to review requests, tipically adding tests16:09
alexpilottibut things look fairly good16:09
zehicle_at_dellI'm interested in hearing about how we're tracking16:10
alexpilottithe only commit blocked is the one related to RDP by russellb as he's expecting to release an admin private API first16:10
alexpilottizehicle_at_dell: what do you mean with tracking?16:11
*** dvarga_ has quit IRC16:11
*** dvarga has joined #openstack-meeting16:11
alexpilottizehicle_at_dell: ping16:11
alexpilottiok, anyway16:12
alexpilottiwe have two new blueprints16:12
alexpilottilet me fetch the links16:12
russellbalexpilotti: https://review.openstack.org/#/c/42770/16:12
russellbadmin API ^16:12
alexpilottirussellb: cool tx16:12
alexpilottirussellb: so we can start working on them or should we wait for this patch to merge?16:13
*** thomasbiege has quit IRC16:13
alexpilottirussellb: since you are around, talking about BPs16:14
alexpilottirussellb: we had to add a new Nova one:16:14
alexpilotti#link https://blueprints.launchpad.net/nova/+spec/hyper-v-metrics16:14
*** armax has left #openstack-meeting16:14
russellbis there a patch for this already?16:15
alexpilottias we require some minor settings on the VM to support Ceilometer16:15
alexpilottialmost ready16:15
alexpilottilike in a couple of days16:15
russellbsmall patch?16:15
russellbdeadline is tomorrow, or it can't go in16:15
alexpilottitomorrow is the deadline for presenting Bps afaik16:16
alexpilottiwhile implementation can be done until the 4th, or am I wrong?16:16
russellbwrong :-)16:16
russellbcode must be proposed by EOD tomorrow16:16
*** asomya has joined #openstack-meeting16:16
*** asomya has left #openstack-meeting16:16
russellband then *merge* deadline is 2 weeks later16:16
*** jcoufal is now known as jcoufal_afk16:16
alexpilottiok, what about for example the RDP one that depends on the the admin api you just published16:17
alexpilottiwe need to do it by tomorrow?16:17
russellbcode is already up for review right?16:17
*** jmontemayor has joined #openstack-meeting16:17
russellbthen it's ok16:17
russellbeven if it needs a revision16:17
alexpilottiok, that sounds good :-)16:17
russellbi mean, a patch that has a comment saying "insert real implementation here" doesn't count :-)16:18
alexpilottias all the Bps are already under review16:18
russellbjust needs to be reasonably close to ready to go in16:18
alexpilottihehe, got the message  :-)16:18
alexpilottiso going back to the BPs, we have a similar one16:19
alexpilottifor Neutron16:19
alexpilotti#link https://blueprints.launchpad.net/neutron/+spec/hyper-v-metrics16:19
*** SumitNaiksatam has quit IRC16:19
*** kebray has quit IRC16:20
alexpilottimarkmcclain: ping16:20
alexpilottidoes anybody have any question in the meantime?16:21
*** kebray has joined #openstack-meeting16:21
alexpilottiok, blueprints are obviously the big topic this week16:21
alexpilottibeside that:16:22
alexpilotti#topic bugs16:22
*** openstack changes topic to "bugs (Meeting topic: hyper-v)"16:22
*** jmontemayor has quit IRC16:22
alexpilottithere are some discussions going on on migration16:22
*** boris-42 has quit IRC16:22
zehicle_at_dellback, sorry was afk16:23
alexpilottilet me fetch the link16:23
*** mdomsch has joined #openstack-meeting16:23
alexpilotti#link https://bugs.launchpad.net/nova/+bug/120830116:23
uvirtbotLaunchpad bug 1208301 in nova "The VM will be destroyed on source host during resizing for Hyper-V" [Undecided,New]16:23
alexpilottiwe are hissing a bug on migration16:23
alexpilottibasically if the target goes down before migrate_disks_and_power_off completes16:24
alexpilottiwhen the target nova-compute restarts it does not continue the migration16:24
alexpilottiand there are complains related to the fact that we destroy the VM (but not the disks) at the end of migrate_disks_and_power_off16:25
alexpilottiI want to stress the fact that the primary concern here is to avoid the risk of having the same VM booted up twice on the network16:25
*** lexinator has quit IRC16:26
alexpilottithat's why we get rid of the source VM asap16:26
*** lexinator has joined #openstack-meeting16:26
alexpilottiif somebody has complains about this, it's a good moment to talk about them16:26
alexpilottiOk, I guess we can continue16:27
alexpilottiWe can close the meeting here from what I'm concerned, unless somebody has more topics to discuss16:27
zehicle_at_dellI've got a small thing related to crowbar16:28
zehicle_at_delland coordinating w/ hyperv work w/ Havana on crowbar16:28
alexpilottiI was almost hissing end meeting, just in time :-)16:28
alexpilotti*hitting, damn autocorrector16:28
alexpilottizehicle_at_dell: please go on16:29
zehicle_at_dellWe're planning to clean up our Grizzly branch ("pebbles") and cut a new branch to start on the Havana work16:29
zehicle_at_dellin the next week or so16:29
*** neelashah has quit IRC16:29
zehicle_at_dellusing havana pull-from-source16:29
alexpilottistill on 1.x or on 2.0?16:29
zehicle_at_dell2x is ramping up too16:30
zehicle_at_dellwe're looking to see if we can jump most of the effort to 2 after the summit16:30
zehicle_at_dellbut we want to get havana working for the summit on 1x16:30
zehicle_at_dellI'm trying to make sure that we get your stuff into Pebbles so we can branch and focus on Havana16:30
alexpilottithat's great16:31
alexpilottiwe have the stuff up for review now16:31
zehicle_at_dellwe've got people (SUSE led I believe) who want it for Grizzly on Pebbles16:31
zehicle_at_dellwe're more focused on Havana at this point because it helps get the community moving early if we have it working for the summits16:31
*** martine has joined #openstack-meeting16:32
*** martine_ has quit IRC16:32
zehicle_at_dellso, no action items except getting your pulls in16:32
alexpilottiit makes sense, given the status of the project16:32
*** martine is now known as martine_16:32
alexpilottifor supporting Havana, beside of course the Quantum/Neutron renaming16:32
*** rods1 has joined #openstack-meeting16:33
*** rods has quit IRC16:33
zehicle_at_delljust wanted to make sure that everyone is aware so we can coordinate16:33
alexpilottithe Hyper-V integration is quite straightforward16:33
*** neelashah has joined #openstack-meeting16:33
alexpilottiShould we talk about it at the Crowbar design meeting tomorrow?16:34
zehicle_at_dellwe're not having one tomorrow16:35
*** radez is now known as radez_g0n316:35
zehicle_at_dellsorry, we need to cancel16:35
alexpilottiok, np, good to know! :-)16:36
zehicle_at_dellwe should discuss on list, just to make sure we're coordinate16:36
*** xBsd has quit IRC16:36
zehicle_at_dellmainly I wanted to make sure that people are aware, so we can build more use/test for this integration16:36
*** psedlak has quit IRC16:36
alexpilottitx zehicle_at_dell !16:36
alexpilottilast two notes for today, unless somebody has other topics:16:36
alexpilotti#link https://bugs.launchpad.net/pbr/+bug/121091216:37
uvirtbotLaunchpad bug 1210912 in pbr "requirements.txt install fails on Windows " [Critical,Fix committed]16:37
alexpilotti#link https://bugs.launchpad.net/neutron/+bug/121238516:37
zehicle_at_delli'm done16:37
uvirtbotLaunchpad bug 1212385 in neutron "Setup fails on Windows due to changes in neutron/hooks.py" [High,Fix committed]16:37
alexpilottiThe first was a bug that blocked ANY OpenStack component setup  on Windows16:37
alexpilottifrom python-*client to Nova, Neutron etc16:37
*** adalbas has joined #openstack-meeting16:38
alexpilottiwe addressed and solved it over the weekend16:38
alexpilottithe second one was blocking the Neutron setup on Hyper-V16:38
alexpilottiboth solved16:38
alexpilottiagain, let me stress the need for a Windows CI gate16:38
alexpilottithose errors are not showing up on the Linux gates, being platform related16:39
alexpilottiluckily we have the night builds of our installers16:39
alexpilottiso we get prompt notification when something fails16:39
alexpilottibut we should avoid those patches to get merged before, if possible :-)16:40
alexpilottiOk, that was the last info I wanted to talk about16:40
alexpilottiSee you next week!16:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:40
openstackMeeting ended Tue Aug 20 16:40:41 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-08-20-16.06.html16:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-08-20-16.06.txt16:40
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-08-20-16.06.log.html16:40
*** jhenner has quit IRC16:41
*** nati_ueno has joined #openstack-meeting16:42
*** nati_ueno has quit IRC16:42
*** ivasev has quit IRC16:42
*** sushils has quit IRC16:42
*** nati_ueno has joined #openstack-meeting16:43
*** ivasev has joined #openstack-meeting16:43
*** alexpilotti has quit IRC16:44
*** ociuhandu has quit IRC16:44
*** branen_ has joined #openstack-meeting16:48
*** ivasev has quit IRC16:48
*** mdenny has joined #openstack-meeting16:48
*** jtomasek has quit IRC16:49
*** sushils has joined #openstack-meeting16:49
*** neelashah has quit IRC16:50
*** MarkAtwood2 has joined #openstack-meeting16:50
*** neelashah has joined #openstack-meeting16:51
*** MIDENN_ has quit IRC16:51
*** lcheng has quit IRC16:51
*** neelashah has quit IRC16:51
*** branen has quit IRC16:52
*** alexpilotti has joined #openstack-meeting16:52
*** roampune has joined #openstack-meeting16:53
*** lcheng has joined #openstack-meeting16:53
*** afazekas has quit IRC16:54
*** lexinator has quit IRC16:54
*** lexinator has joined #openstack-meeting16:58
*** jmontemayor has joined #openstack-meeting16:59
*** mrunge_ has joined #openstack-meeting16:59
*** ndipanov has quit IRC17:01
*** mrunge has quit IRC17:01
*** jcoufal_afk is now known as jcoufal17:02
*** egallen has quit IRC17:03
*** edmund has joined #openstack-meeting17:03
*** egallen has joined #openstack-meeting17:04
*** morganfainberg|a is now known as morganfainberg17:04
*** jhenner has joined #openstack-meeting17:06
*** martine_ has quit IRC17:08
*** dprince has quit IRC17:08
*** vaml has joined #openstack-meeting17:11
*** comay has joined #openstack-meeting17:13
*** jhenner has quit IRC17:15
*** vipul is now known as vipul-away17:16
*** jcoufal has quit IRC17:21
*** vipul-away is now known as vipul17:22
*** hemnafk is now known as hemna17:22
*** jpich has joined #openstack-meeting17:26
*** mrunge_ is now known as mrunge17:27
*** pcm_ has quit IRC17:29
*** noslzzp has joined #openstack-meeting17:29
*** ivasev has joined #openstack-meeting17:30
*** neelashah has joined #openstack-meeting17:30
*** benl_ has joined #openstack-meeting17:31
*** pcm_ has joined #openstack-meeting17:32
*** SergeyLukjanov has quit IRC17:34
*** mrunge has quit IRC17:35
*** jrodom has joined #openstack-meeting17:35
*** tssgery has quit IRC17:38
*** flaper87 is now known as flaper87|afk17:40
*** troytoman-away is now known as troytoman17:40
*** zul has quit IRC17:42
*** SumitNaiksatam has joined #openstack-meeting17:44
*** radez_g0n3 is now known as radez17:46
*** nachi has joined #openstack-meeting17:52
*** brich1 has joined #openstack-meeting17:53
*** bknudson has joined #openstack-meeting17:55
*** roampune_ has joined #openstack-meeting17:56
*** aababilov has joined #openstack-meeting17:56
aababilovhi everyone!17:57
morganfainbergaababilov: hi!17:57
aababilovare we going to discuss apiclient today?17:58
stevemarhola o/17:59
morganfainbergnot sure, if it's not on the specific agenda, there is always an open agenda time17:59
bknudsonaababilov: here's the agenda: https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting17:59
morganfainbergand you should bring it up17:59
*** henrynash has joined #openstack-meeting17:59
morganfainbergbknudson: aha there we go *bookmarks that*17:59
henrynasheven'in all17:59
*** roampune has quit IRC17:59
morganfainberghenrynash: how fares your side of the pond?18:00
*** rcrit has joined #openstack-meeting18:00
henrynashsunny and warm….must be some mistake...18:00
morganfainbergyou can have some of the warm from SoCal atm if you want18:00
*** dolphm has joined #openstack-meeting18:00
morganfainbergi'll send it to you18:00
henrynashok, nice!18:00
*** topol has joined #openstack-meeting18:01
dolphm#start keystonemeeting18:01
dolphm#topic FeatureProposalFreeze & Havana milestone 318:01
gyeedoesn't look like its started18:01
dolphm#startmeeting keystone18:01
openstackMeeting started Tue Aug 20 18:01:55 2013 UTC and is due to finish in 60 minutes.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
* topol opening night jitters?18:02
dolphmi should write this stuff in advance and just copy/paste it18:02
dolphm#topic FeatureProposalFreeze & Havana milestone 318:02
*** openstack changes topic to "FeatureProposalFreeze & Havana milestone 3 (Meeting topic: keystone)"18:02
dolphmm3 is cut sept 4 (2 weeks-ish)!18:02
morganfainbergrolling up fast!18:02
dolphmand more immanently, feature proposal freeze is starting to hit for several projects this week18:02
gyeedolphm, what's 8/28 date then?18:02
dolphmours is next week18:03
dolphm#link https://wiki.openstack.org/wiki/FeatureProposalFreeze18:03
dolphmgyee: read the description ^18:03
bknudsonwhen's FeatureFreeze?18:03
dolphmSeptember 4th18:04
dolphm#link https://wiki.openstack.org/wiki/Havana_Release_Schedule18:04
*** fabio has joined #openstack-meeting18:04
dolphmoverall release schedule ^18:04
dolphmfeature freeze takes effect with milestone-proposed / release-proposed is created18:04
dolphmthen we open back up for icehouse18:05
dolphmso, on a related note...18:05
dolphm#topic pagination vs feature proposal freeze18:05
*** openstack changes topic to "pagination vs feature proposal freeze (Meeting topic: keystone)"18:05
dolphm#link https://blueprints.launchpad.net/keystone/+spec/pagination-backend-support18:05
dolphmthe one bp that has no implementation in review yet!18:06
dolphmhenrynash: i'm not caught up on the mailing list thread, but as far as i've read, there's certainly some discouragement against pursuing pagination at all?18:06
*** divyeshk has joined #openstack-meeting18:06
gyeedolphm, right, thought we are going to tackle filtering first18:06
henrynashso if you following the url spec in the Bbp, I wrote up an enterhpad to summarize18:06
henrynash#linnk https://etherpad.openstack.org/pagination18:07
bknudsonthere doesn't seem to be a question about better filtering18:07
henrynashbknudsonL agreed…everyone wants that18:07
gyeewe should go after filtering first, least that area is more certain18:07
dolphmhenrynash: are you pursuing filtering in havana?18:08
henrynashso I have working a filtering systems that allows drivers to filter if they can, the controller will if they can't18:08
dolphmhenrynash: should the pagination bp be un-targeted from havana?18:08
henrynashI also have pagination work as well18:08
dolphm(is there a filtering-in-drivers bp?)18:08
gyeewe should separate them out into two BPs18:08
morganfainberggyee: ++18:08
*** jamielennox has joined #openstack-meeting18:08
henrynashdolphm: no..but maybe we should split it18:09
*** changbl has joined #openstack-meeting18:09
morganfainbergi also think with filtering, if leveraged correctly, the pagination quesiton might go away.18:09
henrynashok, that's fine - I can that18:09
dolphmhenrynash: sounds like pagination is dependent on filtering?18:09
henrynashso here's the rub, however18:09
henrynashif we define really rich filtering which only some of our backends can do....18:09
dolphmmorganfainberg: especially if you require filtering18:09
morganfainbergdolphm: exactly18:10
bknudsonkvm does not do filtering.18:10
*** egallen has quit IRC18:10
bknudsonoops, kvs18:10
henrynashthen we can't do things like limit the number of response or paginate at the driver leve18:10
dolphmbknudson: no one does kvs18:10
morganfainbergbknudson: kvs is a special case imo18:10
*** jamielennox_ has joined #openstack-meeting18:10
henrynashif we don't have parity in what filters LDAP and SQL support, then we will still have long response times for the "poorer" backend18:11
gyeehenrynash, not sure if I understand18:11
gyeethey are two separate issues18:11
bknudsonLDAP has pretty good filtering.18:11
bknudsoneven does soundex.18:11
henrynashbknudson: sounds good18:11
bknudsonmost of them do anyways18:11
dolphmhenrynash: what's the disparity in your implementation?18:11
morganfainberghenrynash: perhaps it makes sense allow the driver to advertise what it can do? encourage filtering as the 1st choice (obviously tackle filtering first as a concept)18:11
henrynashso the issue is conceptual, not implementation18:12
*** zqfan has joined #openstack-meeting18:12
henrynashassuming that we need to either paginate or put a had limit on how many response we want back from SQL/ or LDAP....18:12
gyeemorganfainberg, sure, drivers should tell Keystone what they can do18:12
*** kbs has quit IRC18:13
henrynashthen you can't do that if you don't implement ALL you filters in the driver18:13
henrynash…i.e. by the SQL or LDAP backend18:13
gyeehenrynash, you don't have to implement ALL18:13
dolphmhenrynash: but what *can't* be implemented? why not require the implementation satisfy appropriate tests in test_backend?18:14
henrynashbut if you don't, you can't limit the output (say max 100 entries)18:14
morganfainberghenrynash: you could also pass through filtering arguments if they are uniform if the driver supports it18:14
gyeeyou just need to document what you can do18:14
*** jamielennox_ has quit IRC18:14
dolphmhenrynash: i don't see a use case (yet) for special casing a use case for filtering in drivers18:14
*** kbs1 has joined #openstack-meeting18:14
dolphmerr special casing *a specific filter* in a driver18:14
henrynashdolphm: when I say drivers I mean use the filtering of the underlying database (SQL or LDAP)18:14
dolphmhenrynash: right18:14
gyeejust pass whatever query params in the drivers and we are done :)18:15
henrynashsure, I've done that18:15
morganfainberggyee: ++, just make sure we make the params uniform.18:15
henrynashI think this is too complex an issue to discuss on IRC...18:15
dolphmhenrynash: you said you had no disparity in filtering capability between LDAP and SQL - so test equally in test_backend and ensure all driver implementations maintain feature parity18:15
*** Mandell has joined #openstack-meeting18:16
henrynashdolphm:…ok, so that means we will ONLY support filtering at the capability level that is the lowest common denominator between SQL and LDAP18:16
henrynashdiolphm: that might be ok18:16
henrynashdolphm: we can't add "extra filtering at the controller level"18:17
gyeehenrynash, we need all the query params18:17
dolphmhenrynash: so, split the bp into filtering & pagination, and put something up in time for feature proposal freeze to continue the discussion?18:17
henrynashdolphm: for those drivers that are doing their one filtering18:17
gyeein the drivers18:17
*** zul has joined #openstack-meeting18:17
henrynashdolphm: I guess, I see them more inter-related, but ok to split18:18
jamielennoxI've missed everything that's come before this, but no to actually doing filtering and pagination in the controller, but yes to standardizing the names of parameters in controllers18:18
morganfainberghenrynash: i think we keep it at the lowest common denominator to start (filtering), if data shows that is insufficient we can approach how to pass other filtering through?  It'll be more work to keep compat, but i think its the easiest to approach.18:19
henrynashdolphm: that's the point I am trying to make…IF we want to paginate/limit, then it affects what filtering we can do where18:19
bknudsondo the backends do the paging, too?18:19
dolphm#action henrynash to split new filtering blueprint out of existing 'pagination-backend-support' blueprint18:19
dolphmbknudson: not currently18:19
henrynashbknduson: in mine, yes18:19
bknudsonso not sure what the issue is... the backend gets that query parameters (filter & paging) and handles it.18:20
*** dcramer_ has joined #openstack-meeting18:20
henrynashbknudson: that's what I;m doing18:20
dolphm(i only put this on the agenda to get a status update vs feature proposal freeze, which i think we've got ;)18:21
dolphmmoving on..18:21
dolphm#topic keystoneclient library - public vs private interfaces18:21
*** openstack changes topic to "keystoneclient library - public vs private interfaces (Meeting topic: keystone)"18:21
dolphmbknudson: !18:21
bknudsonthis has come up in an irc discussion last week...18:21
bknudsonwe've got several reviews affecting keystoneclient18:21
dolphmsounds like this change https://review.openstack.org/#/c/40173/ broke what was perceived to be a public API18:22
bknudsonand to be safe, we really should not be changing anything public18:22
dolphmbknudson: but we haven't defined what's public and what's private?18:22
morganfainbergdolphm: precisely18:22
bknudsonThere's a pep8 standard that says how to define public /private18:22
bknudsonbut we're not really following it.18:22
dolphm#link http://www.python.org/dev/peps/pep-0008/#public-and-internal-interfaces18:22
bknudsonso not sure what to do about it... assume everything is public?18:22
bknudsondo the work to actually define what's public/private?18:22
bknudson(bring the code up to pep8)18:23
*** xBsd has joined #openstack-meeting18:23
topolwe really need to delineate between public and private. Our folks get burned by this all the time and yell at Brant or me18:23
dolphmtopol: in the client library?18:23
bknudsonI'll try to put something together for the mailing list... I had intended to do that.18:23
jamielennoxso regarding the above review it's fairly easy to bring back the compatibility they want18:23
topoldolphm, in general18:23
topolwherever we are being lax18:24
dolphmtopol: in python interfaces?18:24
jamielennoxhowever for example this one: https://review.openstack.org/#/c/42254/ it removes a function that has really only private usage but is defined in a public way18:24
bknudsonjamielennox: right, those are the weirdy ones.18:24
dolphmtopol: i want to understand specifically where we're causing people pain18:24
*** vaml has quit IRC18:24
topoldolphm, even in our driver code folks perceived interfaces to be public and got burned18:24
dolphmtopol: we never hear anyone speak up18:24
bknudsonjamielennox: safe thing to do, and I think what's indicated to do by openstack guidelines, is we don't allow it.18:24
topolbrant, u remember I hope18:24
*** mdomsch has quit IRC18:25
gyeedolphm, fyi we (HP) is extending keystoneclient classes18:25
bknudsontopol: I remember... it wasn't the client it was the identity API.18:25
topolbknudson and I handled the uproar behind the scenes18:25
dolphmgyee: which ones18:25
topolbknudson, agreed. but the principle applies18:25
gyeeboth v2 and v3 client classes18:25
morganfainbergdolphm: same with metacloud (limitedly)18:26
bknudsongyee: did you think you were extending a public or private interface?18:26
morganfainbergwe are extending client classes18:26
morganfainbergbut nothing burned yet.18:26
bknudsonand, if you thought it was public, why?18:26
gyeebknudson, the client classes are public18:27
dolphma "workaround": release the next version of keystoneclient as "0.4.0" (dissuading expectation of backwards compatibility)18:27
jamielennoxso i think there are a couple of ways forward. First we need a standard way to start deprecating functions in keystoneclient. Then we need to be super vigilant about enforcing _function_names for things that are expected private18:27
bknudsonpep8 defines what's public, and by that definition nothing is public since it's not documented at the keystoneclient level.18:27
*** mrunge has joined #openstack-meeting18:27
*** vaml has joined #openstack-meeting18:27
morganfainbergbknudson: i think we need to be explicit, even if technically we aren't advertising anything as public18:27
*** rverchikov has joined #openstack-meeting18:27
gyeebknudson, exactly, key is documentation18:28
dolphmjamielennox: we're talking about classes specifically here, not just methods18:28
bknudsonyou can name classes with _18:28
jamielennoxdolphm, both i would say18:28
bknudsonand packages.18:28
morganfainbergdolphm: i think his concern still applies for the initial transition.18:28
*** jrodom has quit IRC18:28
*** roampune_ has quit IRC18:28
bknudsonone option is we fork keystoneclient2 from keystoneclient ... seems drastic18:28
morganfainbergbknudson: or we do a staged deprecation18:29
morganfainbergtransitional + warnings18:29
jamielennoxbknudson, well we still have the option to do keystoneclient 118:29
morganfainbergthough.. that has other pitfalls18:29
*** roampune has joined #openstack-meeting18:29
dolphmbknudson: jamielennox: and modules?18:29
bknudsondolphm: and modules18:29
jamielennoxi think there are modules like utils that are not supposed to be public on keystoneclient18:30
gyeeyes modules18:30
*** sushils has quit IRC18:30
morganfainbergcorrect, _ prefix is good for any namespace in theory18:30
morganfainbergto mark it as private18:30
dolphmbackwards compatibility can be restored in jamielennox's patch by introducing an "empty" keystoneclient.client implementation that just does "from keystonclient.httpclient import *"18:30
gyeeor use the manager-driver approach, everything in manager is by definition public18:30
*** vipul is now known as vipul-away18:30
*** vipul-away is now known as vipul18:30
*** jrodom has joined #openstack-meeting18:31
morganfainbergdolphm: i would actually encourage something that issues a warning coupled with that if thats the approach18:31
jamielennoxdolphm, right that first one is easy. you don't need import * i think you just need import HTTPClient18:31
dolphmmorganfainberg: ++18:31
jamielennoxi was waiting for the discoverability thing to go forward as it's using client.py but i can add that first18:31
morganfainbergi also think proper use of __all__ is important for things that are public18:32
bknudsonpep8 also says to use __all__18:32
dolphmmorganfainberg: which we don't use anywhere18:32
bknudsontherefore everything in keystoneclient is private therefore we can just change it.18:32
morganfainbergi saw a rough implementation that populated __all__ with a decorator @public18:32
morganfainbergit might be worth using that kind of _very_ explicit mechanism18:33
morganfainbergmight be too much overhead though18:33
jamielennoxmorganfainberg, yea, it was interesting but i think it's just better to do manually18:33
morganfainbergregardless of implementation18:33
bknudsonso what do people think about enforcing pep8 public/private on keystoneclient changes?18:34
morganfainbergbknudson: ++ all for it.18:34
dolphmbknudson: i wish i could agree, but i'd argue that *any* examples we have documented in openstack-manuals etc should be considered public API's18:34
bknudsondolphm: yes, I was going to look for examples in manuals...18:34
dolphmbknudson: ++ moving forward18:34
bknudsonthere is the one doc in keystoneclient that just mentions v2 client and tenants18:35
gyeesure, following pep8 is a good start18:35
jamielennoxbknudson, absolutely in future, i'm not sure about what's currently there though18:35
*** dscannell has quit IRC18:35
dolphm#action all core reviewers familiarize yourself with http://www.python.org/dev/peps/pep-0008/#public-and-internal-interfaces and begin to enforce on reviews moving forward18:35
jamielennoxtaking for example the one in the review get_auth_ref_from_keyring had no business ever being public api and won't be in any examples18:35
dolphmjamielennox: ++18:35
bknudsonI'll try to make the time to see what I can do about going through and marking things deprecated, or setting __all__, etc.18:35
bknudsondocstrings on things that are meant to be public18:36
morganfainbergbknudson / jamielennox: if there is a question, we make it private and provide a wrapper that logs deprecated18:36
dolphmanyone want to take a pass at implementing __all__ everywhere, and renaming private methods appropriately?18:36
jamielennoxbut yes, i think we can say that what is there is public and we start deprecating for a release cycle18:36
dolphmthat way we break everyone all at once, and can release 0.4.0 accordingly :P18:37
bknudsondolphm: put me down. I'll try to make the time for it.18:37
bknudsonI assume there isn't a huge hurry for this.18:37
dolphm#action bknudson to implement __all__ and rename private methods accordingly18:37
morganfainbergbknudson: if you need any help, let me know.  i'll toss some cycles to help out18:37
lbragstadbknudson: same, I'll pitch in a help if I can18:37
stevemarbknudson, same here18:37
jamielennoxbknudson, yea i'm keen on this one too18:37
dolphmlbragstad: bknudson: morganfainberg: thanks!18:37
dolphmjamielennox: ditto ^18:38
dolphm#topic open discussion18:38
*** benl_ has quit IRC18:38
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:38
morganfainbergaababilov: you wanted to bring up apiclient right?18:38
fabiodolphm, would it be possible to submit extensions after m3?18:38
dolphmthere's also a high priority code review on the agenda (m3 targeted bp impl): https://review.openstack.org/#/c/38308/18:38
lbragstadI have a couple reviews for the notification stuff if people want to pick through it18:38
dolphmfabio: identity-api docs or implementation?18:39
dolphmfabio: and for havana or icehouse?18:39
fabiodolphm, both18:39
lbragstadstevemar: morganfainberg thanks for reviewing18:39
stevemarnp lbragtad18:39
morganfainberglbragstad: of course.18:39
fabiodolphm, after Havana m3 and before Icehouse m118:39
dolphmfabio: absolutely not18:40
*** markmcclain has quit IRC18:40
dolphmfabio: you're welcome to submit identity-api changes anytime, though18:40
bknudsondo we have some way to check in changes not to master? a topic branch or something?18:40
dolphmfabio: their scope of impact will be limited to the next api revision, though18:40
dolphmbknudson: sure, push to the corresponding branch in gerrit18:41
fabiodolphm: thanks for the clarification18:41
rverchikovdolphm: is there any activity on https://bugs.launchpad.net/keystone/+bug/1205506? Do you mind if I start working on it?18:41
bknudsondo we want them sitting in gerrit for months?18:41
uvirtbotLaunchpad bug 1205506 in keystone "get_group_project_roles() asks same ldap query for all groups associated with user" [Medium,Triaged]18:41
morganfainbergbknudson: it'll mean likely heavy rebasing by the time they go in.18:42
morganfainbergin either case.18:42
fabioall: please review OS-EP-FILTER, #link https://review.openstack.org/#/c/33118/18:42
morganfainbergfabio: i'll look at that today.18:42
stevemarfabio: will do, it's looking pretty good18:42
*** johnthetubaguy has quit IRC18:42
dolphmrverchikov: i'd ask ayoung (who's not online right now) since it's currently assigned to him18:42
ayoungI'm in for 2 minutes...anyone have anything burning for me?18:42
stevemarayoung: you were gone?18:42
dolphmrverchikov: in the mean time, feel free to comment on the bug / request bug assignment / suggest a solution18:42
*** SergeyLukjanov has joined #openstack-meeting18:43
rverchikovdolphm: thanks18:43
ayoungrverchikov, patch submitted for that, I think18:43
aababilovsorry for delay18:43
dolphmrverchikov: slash, ayoung is back!18:43
aababilovI'm here18:43
rverchikovayoung: could you give a link?..18:43
dolphmbknudson: changes to topic branches can merge18:43
morganfainbergquick question regarding caching implementation.  I am certain i'll have the caching core and token (revocation list, token, validate) done for M3.  any thoughts on other system i should see about hitting if possible? or just wait for I?18:43
*** SergeyLukjanov has quit IRC18:43
ayoungrverchikov, https://review.openstack.org/#/c/40283/18:44
dolphmmorganfainberg: i noticed that get_domain was hit repeatedly and could benefit18:44
dolphmmorganfainberg: so, maybe a bit of identity?18:44
ayoungrverchikov, if that is not sufficient, then, yes, take it and run18:44
dolphmmorganfainberg: assignment is probably hit pretty hard as well18:44
morganfainbergdolphm: i'll aim for some id/assignment where the revocations aren't ghastly18:44
morganfainbergsome are a rabbit hole to handle invalidates for atm18:45
bknudsondoes the revocation list get cached?18:45
morganfainbergbknudson: on the remote ends, i think it does.18:45
bknudsonthat would help when there's lots of tokens.18:45
dolphmmorganfainberg: domain crud should be about as complex as the token operations, so cache invalidation should be similar18:45
ayoungit gets fetched on a schedule18:45
bknudsonthe clients are requesting every second.18:45
morganfainbergbknudson: but in my cache proposal, yes it is cached18:45
ayoungdefautl is set in auth_token middleware in client code18:45
morganfainbergand explicitly refreshed on token revocation instead of just invalidated.18:45
*** vipul is now known as vipul-away18:46
bknudsonmorganfainberg: that's going to be great.18:46
morganfainbergbknudson: yeah, over time i want to have most anything hit regularly cached.18:47
ayoungmorganfainberg, +118:47
ayoungmorganfainberg, caches that we can control are key18:47
ayoungotherwise, people will cache outside of Keystone, and that will be bad18:47
*** roampune has quit IRC18:47
ayoungthis is double plus good18:47
morganfainbergayoung: exactly18:47
morganfainbergdogpile.cache was just accepted into requirements, so i'll be doing cleanup and posting changesets for review shortly18:48
*** roampune has joined #openstack-meeting18:48
jamielennoxmorganfainberg, i haven't looked at dogpile, but is it something that should be looked at for what is currently done by memcache/18:50
morganfainbergjamielennox: dogpile can use memcache backend, redis, in-memory, file-based, etc.18:50
bknudsonhttp provides ways to cache and check if something is changed since some time...18:50
dolphmmorganfainberg: awesome, i didn't see that18:50
morganfainbergdolphm: pending gate.18:50
dolphmjamielennox: dogpile.cache can back to memcache18:51
*** openstack` has joined #openstack-meeting18:51
-rajaniemi.freenode.net- [freenode-info] please register your nickname...don't forget to auto-identify! http://freenode.net/faq.shtml#nicksetup18:51
dolphmmorganfainberg: what's the benefit over a kvs driver?18:51
jamielennoxgyee, but at least for auth_token the token is going to need to be shared across process18:51
morganfainbergdolphm: in theory, you can hook a proxy in front of it and change behavior.  ohter than that, maybe nothing18:52
morganfainbergdolphm: i'll need to think about it18:52
jamielennoxgyee, keyring can do it but i'm not sure it's advisable, and i think it's doing memcache there anyway18:52
morganfainbergdolphm: well and the decorators can hook into it18:52
*** openstack` is now known as openstack18:52
gyeeI don't think keyring are meant for sharing across processes18:52
*** ChanServ sets mode: +o openstack18:52
dolphmjamielennox: why does auth_token need to share data across processes?18:52
jamielennoxdolphm, tokens across httpd workers18:52
morganfainbergdolphm: doesn't autho_token have a concept of memcache store as is?18:52
*** boris-42 has joined #openstack-meeting18:52
dolphmjamielennox: i asked why18:52
jamielennoxI guess to prevent multiple httpd worker threads all hitting keystone for an individual token18:53
dolphmmorganfainberg: yes18:53
jamielennoxbut i'm pretty sure that's in memcache anyway18:53
morganfainbergwe'll need to look at those options, but it's doable.18:53
*** afazekas has joined #openstack-meeting18:53
dolphmjamielennox: so, it's a nice-to-have performance gain, not a 'need'18:53
gyeedolphm, that's how it works when auth_token is used in conjunction with Swift cache18:54
*** zqfan has quit IRC18:54
morganfainberggyee: ahh.18:54
gyeetoken data is shared across all proxies18:54
*** jrodom has quit IRC18:54
dolphmgyee: understood18:54
*** otherwiseguy has quit IRC18:54
jamielennoxi'm pretty sure it works that way now anyway, it was just if it was worth extending18:54
*** bgorski has quit IRC18:54
*** novas0x2a|laptop has joined #openstack-meeting18:54
gyeekeystoneclient keyring was meant for CLI18:55
jamielennoxgyee, right, unfortuanetly it was implemented in the HTTPClient rather than in shell18:55
gyeeyeah, I smell refactoring :)18:55
bknudsonjust leave the old one there and deprecated.18:56
jamielennoxthe review i posted earlier at least abstracts it to a general cache object, the idea was to give a memcache backend when it got to auth_token18:56
gyeebknudson, sure, it should be in OpenStack CLI anyway18:57
gyeejamielennox, auth_token cache is abstracted18:57
gyeeit was implemented exactly the same as Nova18:57
*** markvan has quit IRC18:57
*** fabio has left #openstack-meeting18:58
jamielennoxgyee, i don't know enough about how caching there works18:58
gyeeyou can configure it to use an existing cache (i.e. swift_cache) or the default one18:58
*** MarkAtwood2 has quit IRC18:58
*** jrodom has joined #openstack-meeting18:58
ttxdolphm: precision: icehouse branch actually opens when we reach keystone havana-rc118:59
*** olaph has joined #openstack-meeting18:59
*** jrodom has quit IRC18:59
bknudsonso we think the keyring work should be done in python-openstackclient?18:59
ttxi.e. whenever you get to the botton of your RC bugs list and produce a realistic release candidate18:59
gyeebknudson, no, should be in OpenStack CLI19:00
dolphmttx: ah, that makes sense. thank you!19:00
bknudsonright, that's python-openstackclient19:00
gyeeespecially if we want the auth code to be embedded by all the clients19:00
ttx#link http://wiki.openstack.org/ReleaseCycle19:00
stevemargyee: python-openstackclient == openstackCLI19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Aug 20 19:00:41 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-08-20-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-08-20-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-08-20-18.01.log.html19:00
gyeeah, k, we are on the same page then19:00
jamielennoxi don't m ind the concept of a general cache in keystoneclient, probably keyring is a bad one though19:00
jeblairhello infra people19:00
ttxhello infra guy19:01
*** jamielennox has left #openstack-meeting19:01
*** brich1 has quit IRC19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Aug 20 19:01:38 2013 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
*** jrodom has joined #openstack-meeting19:02
jeblairhi, i'd like to scrap our normal agenda and instead check in on the things we're doing to deal with the high load this week, and then go back to doing those things.19:02
*** jrodom has quit IRC19:02
mordredjeblair: ++19:02
jeblairany objections?19:02
jeblairokay, i'll start it off then19:03
ttxhigh load this week and the next and the next19:03
jeblair#topic nodepool19:03
*** openstack changes topic to "nodepool (Meeting topic: infra)"19:03
jeblairttx: indeed :)19:03
jeblairso, the good news is that we managed to get nodepool running in time to meet monday's rush19:03
ttxshould ~calm down once Featurefrozen on september 419:03
jeblairthe bad news is that nodepool was running during monday's rush19:03
*** divyeshk has left #openstack-meeting19:04
jeblairon the one hand, it did help us actually provide the test nodes that jenkins needed19:04
*** otherwiseguy has joined #openstack-meeting19:04
jeblairso as far as our concern for being able to have enough test resources for this roush, i think we managed to do that19:05
clarkbwe (mostly jeblair) added 16 new precise slaves as well19:05
jeblairbut it showed us where the next problems are:19:05
*** thomasbiege1 has joined #openstack-meeting19:06
jeblair* nodepool is easily capable of gitting rate limits; i'm working on fixing that now (by serializing novaclient calls)19:06
*** aababilov has left #openstack-meeting19:06
jeblair* it might be stressing jenkins a bit if it does a lot of deletes at once19:06
*** gyee has quit IRC19:07
*** vipul-away is now known as vipul19:07
*** vipul is now known as vipul-away19:07
*** vipul-away is now known as vipul19:07
jeblair* running so many jobs has increased the load on review.o.o, where all the jobs fetch repo updates (before the fetch changes from zuul)19:07
*** bashok has quit IRC19:08
jeblairso i'm pretty sure we can get a new version of nodepool that is a bit more stable and friendly to providers (first point) in today19:08
*** benl_ has joined #openstack-meeting19:08
jeblairafter that, we may think about the second point (jenkins)19:08
jeblairand we'll talk about the third point in a minute...19:08
jeblairany questions about nodepool?19:08
clarkbjeblair: is it still running az1 in a decreased capacity?19:09
jeblair#link http://tinyurl.com/kmotmns19:09
*** vaml has quit IRC19:09
jeblairthere's a graph, btw, of what nodepool has been doing ^19:09
fungiwhat specific jenkins stress were we seeing during mass node deletion bursts?19:09
*** vijendar has quit IRC19:09
fungii think i must have missed that specific symptom19:09
jeblairclarkb: yes, it's configured to only spawn up to 2 nodes at a time there, basically to keep us from hitting a rate limit (which seems to be different there)19:10
*** nachi has left #openstack-meeting19:10
anteayais the graph time UTC?19:10
*** jrodom has joined #openstack-meeting19:10
jeblairfungi: we saw jenkins get very slow at one point, possibly related to node deletions.  it's also possible it was related to a bug in the gearman-plugin.19:11
fungigiven the short time-to-deletion after completion of a job, i assume it's best to interpret "used" as really being "in-use" for the most part19:11
mordredthat's how I'm reading it19:11
fungiunlike in the past where used slaves often stuck around for hours19:11
jeblairfungi: i don't have much more specific than that, it's more of 'keep an eye on this' at this point19:11
mordredlike, 'not waiting in pool'19:11
fungijeblair: thanks19:11
jeblairfungi: indeed, and even if it has trouble deleting, it tries to set the node to the delete state asap19:12
jeblairyou can see it had such trouble late yesterday (az1)19:12
* fungi nods19:12
jeblairanteaya: i have no idea what the timezone is.  :(19:12
clarkbjeblair: anteaya I think it is local to whatever your browser is giving out in its request headers19:13
*** benl_ has quit IRC19:13
jeblairanteaya: it does not look like localtime or utc for me.19:13
anteayajeblair: okay, trying to understand the dip at 9pm chart time19:13
jeblairto me, it looks like "now" is just past 2pm.19:13
anteayamaybe that was when you restarted zuul?19:13
*** rverchikov has left #openstack-meeting19:13
anteayaclarkb: ah okay19:13
fungilooks like utc-0500 to me, which is odd because my machine wants utc everywhere and i'm currently in utc-070019:14
anteayajeblair: yes, I have "now" at just past 2pm too19:14
*** topol has quit IRC19:14
fungibut not entirely relevant for now19:14
zarojeblair: are we deleteing or just putting slaves offline?19:14
jeblairwe should probably do something about that.19:14
jeblairanteaya: yes, that dip was when zuul got stuck.19:14
anteayajeblair: okay thanks19:14
jeblairzaro: nodepool deletes them 60 seconds after the job finishes (and gearman-plugin takes them offline)19:15
*** markmcclain has joined #openstack-meeting19:15
jeblair#topic zuul19:16
*** openstack changes topic to "zuul (Meeting topic: infra)"19:16
jeblairso zuul got stuck last night; it was processing its queues VERY slowly19:16
jeblairand our logging was insufficient to determine why19:16
*** jhenner has joined #openstack-meeting19:17
jeblairit could be related to review.o.o being slow, but i don't think it's a direct relation (because it didn't get stuck early when we were most busy)19:17
clarkbI have written a change that will dump each running thread's stack into the debug log on SIGUSR219:17
clarkb#link https://review.openstack.org/#/c/42959/19:17
jeblairclarkb: thanks, that should help us if we are in that kind of situation again19:17
jeblairi also want (me or someone else) to go through the key points in the new queue processor and add some missing log entries19:18
jeblair(because that will give us timing info, which would be very useful)19:18
*** dprince has joined #openstack-meeting19:18
jeblairanything else re zuul?19:19
clarkbAlex_Gaynor is reporting that jobs finishing and being recorded in zuul is slow19:19
clarkbI believe this is potentially related to the blockage yesterday19:20
jeblairclarkb: currently?19:20
clarkbjeblair: yeah see -infra19:20
*** kiall_ has joined #openstack-meeting19:20
jeblairclarkb: well, if we have to restart again, we'll make sure we get your patch in at least19:20
jeblair#topic git.o.o19:21
*** openstack changes topic to "git.o.o (Meeting topic: infra)"19:21
clarkbit isn't stuck like before, but does seem to be slow. There are a few lost jobs that may be lost due to the slowness.19:21
*** rockyg has joined #openstack-meeting19:21
*** jrodom has joined #openstack-meeting19:21
fungii wonder if this slowness is a precursor to the extreme slowness we saw later yesterday19:21
pleia2having some trouble putting the git daemon behind an haproxy because specifying an alternate port while running it from xinetd is a bit of a mess19:22
fungiload on review.o.o is up >100 again, fwiw19:22
*** vipul is now known as vipul-away19:22
pleia2so currently working on just turning it into a service (writing init script now) and calling that specifically from puppet19:22
mordredpleia2: cool19:22
pleia2that way we can specify port and stuff without doing something awful like modifying /etc/services19:23
clarkbpleia2: then we can rely on haproxy for DDoS mitigation as it gives us a slightly more flexible set of tools to work with19:23
clarkbjeblair: I think we should merge the d-g change to use git.o.o https19:23
clarkbthat will hopefully allevaite some of the stress on review.o.o19:24
jeblairclarkb, pleia2: how should we work that into horizontally-scaled git.o.o?19:24
jeblairclarkb: well, yes, but it won't merge for a long time at this point.19:24
fungiclarkb: load on review.o.o looks like it may primarily be concurrent git-upload-pack and git-pack-object activities19:24
clarkbjeblair: should we force it in?19:24
jeblairclarkb: i'd be open to that.  it did pass tests.19:25
clarkbjeblair: I think there are two possible ways of using haproxy in a horizontally scaled git.o.o. Either use the current haproxy stuff as a model for balancing several git daemons and run the balancing ourselves. Or use lbaas to balance a bunch of haproxies in front of git daemon19:25
*** nati_ueno has quit IRC19:26
clarkbjeblair: I like the second option, as it allows us to keep our haproxy simple while taking advantage of our cloud services19:26
*** HenryG has joined #openstack-meeting19:26
*** alexb_ has quit IRC19:26
jeblairclarkb: in option 2, would our haproxies be doing anything?19:26
clarkbjeblair: they would be doing queueing19:27
jeblairclarkb: possibly sub-optimally, though, right?19:27
fungiclarkb: what if we're doing http(s) instead of git protocol though... then does haproxy buy us anything over what aache's already doing?19:28
clarkbjeblair: yes, however I think haproxy has a dynamic round robin balance type that should shift load away from a server with a backed up queue19:28
clarkbfungi: load balancing across many apaches19:28
clarkbfungi: and we can do both19:28
fungioh, i guess if haproxy on the server is intelligently communicating load information back to the central lbaas then that makes sense19:29
clarkbjeblair: fungi pleia2 my vote is we push the d-g change in to use https://git.o.o. Then we can make a better assessment of whether or not we need to keep focusing on git:// to get past the feature freeze19:29
fungiclarkb: i concur19:30
pleia2clarkb: +119:30
jeblairsounds good to me19:30
jeblairthe other part of git.o.o i'd like to consider is 3 aspects of how the server should be tuned:19:30
*** nati_ueno has joined #openstack-meeting19:30
*** jrodom has quit IRC19:31
jeblair1) the git repo itself; we should look into things like packed-refs and decide if there's any other tuning on the repo itself we should do19:31
jeblair2) concurrency -- we should find out how many simultaneous git operations a server can handle (this is probably mostly about filesystem access/locking, etc)19:31
*** jrodom has joined #openstack-meeting19:31
jeblairit's also probably a tradeoff between number of clients and speed, so i think there may need to be some benchmarking there19:32
jeblairwith different values19:32
jeblair3) server sizing -- we have a huge server for git.o.o, but it's possible we could serve just as many git repos with a smaller one19:33
jeblairsimilar benchmarking there, i think19:33
jeblairok, any other topics?19:34
clarkbmysql backups19:34
jeblair#topic mysql backups19:34
*** openstack changes topic to "mysql backups (Meeting topic: infra)"19:34
mordredjeblair: re: 2) figuring out the trade off between artificially reducing concurrency19:34
mordredand how much faster that may make individual operations - for reducing queue size19:34
*** jlucci has quit IRC19:34
*** thomasbiege1 has quit IRC19:34
mordredI think should be factored in19:34
clarkbthe new mysql backup define is running on etherpad.o.o and etherpad-dev.o.o.19:34
jeblairmordred: ++19:34
clarkb#link https://review.openstack.org/#/c/42785/19:34
clarkbthat change will make the cron job quieter at the expence of possibly bit bucketing something important on stderr. I am open to suggestsion on how to deal with this better19:35
clarkbI think once the problem 42785 addresses is corrected we are ready to start adding this to the gerrit servers and anywhere else we believe the mysql db is important19:35
fungiit's possible to filter stderr through grep in the cron job to just ignore patterns you don't care about on an individual basi19:36
*** rcrit has left #openstack-meeting19:37
clarkbI am not as familiar as I should be with bup, what is the process of adding off host backups once we have the DB tarballs?19:37
jeblairclarkb: http://ci.openstack.org/sysadmin.html#backups19:38
clarkbjeblair: danke19:38
*** ivasev has quit IRC19:38
*** ayoung has quit IRC19:38
clarkbfungi: yeah, could do that too, will need to brush up on bourne to figure out what they will look like19:38
jeblairclarkb: we could probably puppet some of that too.19:39
jeblairclarkb: fungi left a link in your review19:39
fungiclarkb: i linked an example in that comment from another place i had tested it and gotten it working previousy19:39
*** ivasev has joined #openstack-meeting19:39
*** benl_ has joined #openstack-meeting19:39
jeblairanything else?19:40
clarkbfungi: the problem here is I am already piping stdout to gzip so I need to figure out some tee magic or something along those lines19:40
clarkbfungi: or write a proper script19:41
*** jrodom has quit IRC19:41
clarkbjeblair: no I think that is it for backups19:41
fungiclarkb: ahh, yeah i'm redirecting stdout to a file and stderr to a pipe in my example19:41
fungiclarkb: two pipes may add a little extra complexity there19:42
*** xBsd has quit IRC19:42
*** ayoung has joined #openstack-meeting19:42
dhellmannclarkb: I think you need to use a fifo19:43
*** egallen has joined #openstack-meeting19:43
*** vipul-away is now known as vipul19:43
fungiyeah, that's the first solution i'd reach for, but maybe overkill in this case19:43
fungiperhaps mysqldump has options to skip specific tables19:44
*** jrodom has joined #openstack-meeting19:44
mordredit does19:44
*** lpabon has quit IRC19:44
mordredand I'm thinking that might be a better option19:44
mordredthan writing crazy output filtering/processing things19:44
clarkbok I will hunt down that option19:45
fungiyeah, if we can tell mysqldump it doesn't need to care about the events table, then so much the better19:45
mordredclarkb: --ignore-table=name19:45
*** benl_ has quit IRC19:47
*** zul has quit IRC19:47
*** vaml has joined #openstack-meeting19:47
*** hub_cap has joined #openstack-meeting19:48
*** topol has joined #openstack-meeting19:49
clarkbAnyone else or are we ready to jump back into making things work better?19:49
jeblairthanks everyone!19:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:49
openstackMeeting ended Tue Aug 20 19:49:42 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-08-20-19.01.html19:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-08-20-19.01.txt19:49
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-08-20-19.01.log.html19:49
*** rockyg has left #openstack-meeting19:49
pleia2thanks jeblair19:50
*** olaph has left #openstack-meeting19:52
*** gabrielhurley has joined #openstack-meeting19:52
*** dvarga has quit IRC19:52
*** afazekas has quit IRC19:54
*** troytoman is now known as troytoman-away19:56
*** AlanClark has joined #openstack-meeting19:56
*** SergeyLukjanov has joined #openstack-meeting19:58
*** markmc has joined #openstack-meeting19:59
ttxWho is around for the TC meeting ?19:59
markwash#vote $vish20:00
ttxrussellb, jd__, markmc, dolphm, annegentle, mikal, mordred, notmyname, jgriffith, vishy, gabrielhurley, markmcclain: around ?20:00
ttxquorum reached, let's get started20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Aug 20 20:01:11 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
*** vijendar has joined #openstack-meeting20:01
ttx#link https://wiki.openstack.org/wiki/Governance/TechnicalCommittee20:01
ttxHopefully will be a short one. The pool awaits20:01
ttx#topic Motion to start using Gerrit for TC votes20:01
*** openstack changes topic to "Motion to start using Gerrit for TC votes (Meeting topic: tc)"20:01
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-August/013164.html20:01
ttxIn summary, mordred proposed that we use Gerrit to track the various iterations over a motion words, and the recording of final approval/rejection votes20:02
ttxThen the merged motions would end up in some repository where they would be used as reference20:02
*** mikal has joined #openstack-meeting20:02
ttxmordred: does that summarize it well ?20:02
ttxPersonally I think that would solve some confusion, etherpads and in-channel pastes20:02
mordredprobably goes without saying that if we approve that...20:02
ttxAs well as provide an automated record of what we voted on and how we voted on that.20:02
mordredwe'd need to go back through the previous things we've done, make a repo with those things in it20:03
mordredso that new things we do can be additions to that20:03
ttxmordred: sounds a lot less great now that you mention it20:03
mordredttx: :)20:03
gabrielhurley+1 to having a repo of important documents20:03
mordred"automated record of what we voted on and how we voted on that" is the main driving impetus20:03
markmcttx, I think he volunteered :)20:03
dolphmmordred: while that sounds nice, why do you think its necessary?20:03
dolphmmordred: but if you're volunteering, then i won't ask why20:04
ttxmarkmc: lgtm20:04
mordreddolphm: we've been making decisions in IRC for 3 years now, and it's getting tough to know what the actual current set of policy is for people20:04
markmcgabrielhurley, yeah - we're not great at recording our motions in the wiki after the fact20:04
* gabrielhurley despises wikis20:04
annegentlegabrielhurley: high520:04
*** markwash is now known as wikis20:04
annegentlemarkmc: noooo20:04
mordredso, obviously we can have this auto-publish on commit and whatnot20:04
ttxmordred: most TC-era motions should be found in the meeting minutes I post after meetings20:04
* wikis despise gabrielhurley20:04
gabrielhurleywikis: I despise you20:04
*** wikis is now known as markwash20:04
mordredand I'm not volunteering myself, but I do volunteer resources to have it done20:04
ttxbut pre-TC motions might just be forgotten or inappropriate20:04
dolphmmordred: ttx: i assume TC 'reviews' would be public for any ATC to comment on?20:05
mordredttx: well, pre-tc motions lead to the tc charter20:05
ttxgiven future changes20:05
*** zehicle_at_dell has quit IRC20:05
mordreddolphm: YES!20:05
ttxmordred: ok, so post-TC motions at least20:05
mordreddolphm: so, I thik that "proposing a motion" should be "propose a commit to the tc repo"20:05
markwashcan we just add the TC meeting notes?20:05
markwashsummary sounds complex and potentially legalistically confusing20:05
ttxmordred: then we'll see if we need t orevive some pre-TC ones20:05
markwashyes, legalistically20:05
dolphmmordred: so, any ATC can propose changes - correct?20:05
ttxmordred: So my only concern is that it should not encourage us to bypass discussion (ML and meeting)20:05
ttxdolphm: yes20:06
ttxmordred: So I would add two constraints:20:06
ttx1. Prefer the ML to discuss the whole concept and alternative solutions20:06
russellbttx: i thought that too, but i'm not sure it's much different than what we have now20:06
russellbbetween ML and then discussion/vote in this meeting20:06
ttx2. Require that the motion stays up for review until at least one TC meeting has occurred to discuss it (we can even vote during that meeting)20:06
mordredttx: that works for me20:06
ttxthen I think with these safeguards on, we are golden20:06
ttxNB: I checked and I don't think we need to change the TC charter to pass that20:06
markwashdid we decide how to represent rejected decisions?20:07
*** mikal has quit IRC20:07
ttxThe only thing that is no longer totally applicable is proxying, but we can keep proxies and handle them "manually" using comments20:07
markwashor do we skip that?20:07
mordredmarkwash: as abandoned changes? :)20:07
*** mikal_1 has joined #openstack-meeting20:07
*** jrodom has quit IRC20:07
ttxmarkwash: I don't think we need to track rejected motions, further than the review link20:07
*** mikal_1 is now known as mikal_laptop20:08
mikal_laptopSorry I'm late, DSL problems20:08
markmcttx, remind me how the voting works again? who has approve rights?20:08
mordredttx: where is the current TC charter?20:08
markwashhow does the gerrit discussion get archived?20:08
notmynamettx: markwash: rejections, or the reasons for them, can be just as important as things that are approved20:08
mordredmarkmc: I was suggesting we give the TC chair APRV rights20:08
markmcmordred, sounds good20:08
ttxmordred: http://wiki.openstack.org/Governance/Foundation/TechnicalCommittee20:08
dolphmttx: so even with gerrit, we'd wouldn't use "asynchronous" voting? (we'd be voting during the course of a regular meeting?)20:08
markmcthis will encourage people to properly document proposals upfront too20:08
ttxmarkmc: TC members have +2, Chair has APRV to tally votes20:09
vishydo we need proxies if we are going to have longer to vote?20:09
annegentlemarkmc: not sure it really will. Etherpad/wiki is quite easy to use for proposals.20:09
* mordred doesn't think so - but doesn't feel strongly about it20:09
*** spenceratx has quit IRC20:09
markmcannegentle, we'll nitpick the hell out of these proposals in gerrit, like we do with everything else in gerrit20:09
ttxvishy: I think we can keep them, if only to avoid having to introduce a special motion to chnage the charter20:09
* mordred was talking about proxies20:09
annegentleI also think we should have the votes in the meeting, because isn't attendance at a certain number of meeting a requirement for serving?20:09
ttxvishy: but I would expect their usage to drop20:10
vishysounds like there is confusion about whether votes will be async20:10
vishybased on dolphm and annegentle 's comments20:10
dolphmvishy: ++20:10
markwashfor some reason I really like the idea of having records of official-ish TC activity in a git repo. . which is why I'm interested in recording rejections and tracking discussion somehow20:10
annegentleI would support Gerrit for wording/policies, but voting at meetings20:10
ttxvishy: the idea would be async votes, but you don't close the vote until the end of the next TC meeting20:10
ttxannegentle: we can vote using Gerrit during the meeting20:11
ttxI actually inhtend to cast my +2/-2 during the meeting20:11
russellbok, so proxies are probably less relevant then20:11
annegentlettx: true, we could20:11
ttxand use +1/-1 until the meeting is held20:11
mikal_laptopWell, if you can't make the meeting surely you can +2 early?20:12
mikal_laptopThus avoiding a proxy?20:12
ttxbut if people are confident they will never change their minds, they can use +2/-2 alright20:12
ttxmikal_laptop: I like to be convinced DURING the meeting20:12
* mordred likes to hold on to pre-conceived notions in the face of reason20:12
mikal_laptopYeah, cool. So the +2 during the meeting bit is more of a guideline than a rule. Like the pirate code.20:12
mordredmikal_laptop: ++20:12
dolphmmordred: can ATC's vote +1/-1 to express support (or not) of a motion? (assuming TC members can cast +2/-2)20:13
*** neelashah1 has joined #openstack-meeting20:13
mordreddolphm: yeah. I don't see why not20:13
ttxdolphm: yes20:13
*** mikal has joined #openstack-meeting20:13
mordredit would be an interesting way to record that sort of thing20:13
mordredalso, I think we'd set the merge mode in gerrit to be cherry pick20:13
mordredwhich means votes will get aded to the commit message20:14
markwashmordred: oh cool20:14
ttxmikal: we would close the vote if we reach enough +2/-2 during the meeting. Otherwise we'd just let the vote continue over the nex tweek async20:14
mordred(seeing as how I do not expect 100 patches to this repo per week)20:14
markwashmordred: +1 to that20:14
notmynamemaybe a silly question, but does gerrit have any issues with having dozens of +/-2s or hundreds of +/-1s on a particular patch?20:14
ttxuntil we get enough +2/-220:14
*** neelashah has quit IRC20:14
mordrednotmyname: it shouldn't - although it'll be interesting to see :)20:14
mordrednotmyname: the votes are all in a db table20:14
markmcthat would be fun20:14
markmc100s of +1s20:14
dolphmnotmyname: i like the way you think20:14
mordredthe UI might look terrible at that point20:15
ttxidentifying issues where generic people care enough to cast a vote is useful, too20:15
annegentleI think asynch with ATC votes is a good way to get input from the ATC crowd, better than IRC.20:15
dolphmis the TC repo named? ;)20:15
*** dmakogon_ has quit IRC20:16
ttxLet me know when you're ready to vote... one of the last ones we'll have maybe :)20:16
markmctrove is a nice name for a repo of documents20:16
markwashmarkmc: lol20:16
ttxmarkmc: "quantum" is nice name too20:16
annegentlemarkmc: bwah ha20:16
mikal_laptopI'm ready to vote20:16
notmynameI'm imagining a situation where something is open for a bit to get ATC feedback and is a hot issue. it could very easily get lots of participation and attention. that's one of the whole charter goals for openstack (open governance)20:16
jd__would it need incubation too?20:16
mikal_laptopSeagate is a great name for a networking product20:17
markmcnotmyname, yes, that would be a great side-effect of the change20:17
ttxnotmyname: +120:17
mordrednotmyname: +120:17
russellb+2 APRV20:17
ttxnotmyname: we'd use common sense in not closing an issue too fast20:17
notmynamejust wait until techcrunch or gigaom is promoting at TC vote ;-)20:17
ttxnotmyname: hence my recommendation to not cast +2/-2 too early20:17
mordredmaybe we'll get fancy and convince the board to do this too ...20:17
*** vaml has quit IRC20:17
ttxlet's do this20:18
notmynameso with that said, I consider markwash's comment about tracking discussion and rejections importatn too20:18
gabrielhurleyrussellb: thanks. someone needed to finish it. ;-)20:18
notmynameand if we have a tool that does that, use it instead of blueprints /anothertopic20:18
ttx#startvote Use Gerrit in the near future to track motions and record TC votes? yes, no, abstain20:19
openstackBegin voting on: Use Gerrit in the near future to track motions and record TC votes? Valid vote options are yes, no, abstain.20:19
openstackVote using '#vote OPTION'. Only your last vote counts.20:19
markmc#vote yes20:19
markmcclain#vote yes20:19
russellb#vote yes20:19
jd__#vote yes20:19
ttx#vote yes20:19
markwashnotmyname: we might just have to set up a record of gerrit history somewhere20:19
dolphm#vote yes20:19
shardy#vote yes20:19
mikal_laptop#vote yes20:19
vishy#vote yes20:19
notmyname#vote yes20:19
markwash#vote yes20:19
ttx30 more seconds20:19
markmcmarkwash, is gerrit not a record of gerrit history?20:19
mordred#vote yes20:19
markwashmarkmc, not one I can access offline as easily, or backup in as many places20:20
openstackVoted on "Use Gerrit in the near future to track motions and record TC votes?" Results are20:20
openstackyes (12): markmc, ttx, notmyname, vishy, shardy, jd__, russellb, markwash, mordred, dolphm, mikal_laptop, markmcclain20:20
ttxmotion approved20:20
mordredmarkwash: I _believe_ newer gerrit is moving to storing discussion in the git repo20:20
ttxmordred: need anything frmo us/me to get this going ?20:20
notmynamemarkmc: and I'd imagine that rejections, by being called rejections (or abandoned) have the connotation of being disposable20:20
mordredmarkwash: but I have not verified that20:20
*** jrodom has joined #openstack-meeting20:20
jd__markwash: we need to make Gerrit use Git repository for tracking votes :)20:20
mordredttx: nah - I'll sync up with you to talk about getting the repo set up and populated20:20
ttxmordred: I'll be around20:21
mordredmarkwash, jd__: I believe upstream gerrit is already working on that20:21
markwashjd__: turtles and elephants all the way down!20:21
ttx#topic ATC exception for Jaromir Coufal and Liz Blanchard20:21
mordredthey want to make everything stored in git and nothing in a database20:21
*** openstack changes topic to "ATC exception for Jaromir Coufal and Liz Blanchard (Meeting topic: tc)"20:21
jd__mordred: awesome :)20:21
ttx#link http://lists.openstack.org/pipermail/openstack-tc/2013-August/000336.html20:21
ttxWe have a provision in our charter for exceptionally granting ATC status to technical contributors when their contribution does not end up as a commit in a git repo20:21
ttxgabrielhurley nominated Jaromir Coufal and Liz Blanchard for their work on Horizon UX20:21
dolphm(we probably need to do this way more often)20:21
*** bknudson has left #openstack-meeting20:21
ttxgabrielhurley: could you do a quick praise ?20:21
*** alexb_ has joined #openstack-meeting20:21
ttxmordred: (sidenote) we could actually maintain the list of "extra ATCs" in that gerrit-for-motions thing, together with associated project and expiration date20:22
*** pcm_ has quit IRC20:22
ttxmordred: so we could programmatically use it when we compute ATC lists20:22
ttx(like for election setup purposes)20:22
mikal_laptopttx: although perhaps set an approval expiry in gerrit...20:23
gabrielhurleyThey've both been leading the efforts to build a UX community for OpenStack, contributing to discussions both in the Horizon community and on the ML for OpenStack in general. Moreover they're actively engaged in blueprint work, helping to get people to the right design decisions. I think that makes them active technical contributors even if they never commit a line to github/gerrit.20:23
mikal_laptopttx: and then just renew by tweaking the config20:23
*** HenryG has quit IRC20:23
dolphmmikal_laptop: base it on the date from git blame?20:23
russellbgabrielhurley: sounds like a great use of this rule then20:23
gabrielhurleyI thought so :-)20:23
mikal_laptopdolphm: renewing is harder then, right?20:23
gabrielhurleyI would be sad if they weren't at the design summit20:23
dolphmmikal_laptop: ah, hmm..20:24
markwashsounds like an easy vote!20:24
mikal_laptopAnyway, yes. These people sound like ATCs to me.20:24
* jd__ don't want a sad gabrielhurley 20:24
ttxDo we need two separate votes or one will do ?20:24
russellbme either!20:24
russellbsounds like one should do20:24
gabrielhurleyone is fine with me20:24
jd__one's fine20:24
*** mikal has quit IRC20:24
ttxAny question before we #startvote ?20:24
*** spenceratx has joined #openstack-meeting20:24
ttxNote: Charter says the exception is valid one year (two elections)20:25
notmynameIMO we should vote separately20:25
ttx(like any commit)20:25
mordredttx: yes to above sidenote20:25
ttxnotmyname: except that nothing in what was presented to me let me distinguish one from the other20:26
dolphmttx: not implying that notmyname would vote differently for each candidate, but if anyone wants to, then a separate vote is a must20:26
notmynamettx: good point20:26
gabrielhurleytwo votes is also fine with me20:26
ttxI'm fine with two votes. Let's do this20:26
markwashthree votes!20:26
ttx#startvote Grant Jaromir Coufal exceptional ATC status? yes, no, abstain20:26
openstackBegin voting on: Grant Jaromir Coufal exceptional ATC status? Valid vote options are yes, no, abstain.20:26
openstackVote using '#vote OPTION'. Only your last vote counts.20:26
russellb#vote yes20:26
gabrielhurley#vote yes20:26
*** mrunge has quit IRC20:26
markmcclain#vote yes20:26
markmc#vote yes20:26
annegentle#vote yes20:26
mikal_laptop#vote yes20:26
dolphm#vote yes20:26
notmynamedolphm: I think 2 votes would be good as a precedent and consistency with future votes20:26
markwash#vote yes20:26
ttx(no we won't vote on who should go first)20:26
notmyname#vote yes20:26
shardy#vote yes20:26
jd__#vote yes20:26
ttx#vote yes20:26
dolphmnotmyname: agree20:26
vishy#vote yes20:27
ttx30 more seconds20:27
dolphmttx: we've had time to internet-stalk both candidates20:27
holms#vote yes20:27
openstackVoted on "Grant Jaromir Coufal exceptional ATC status?" Results are20:27
openstackyes (14): markmc, ttx, notmyname, vishy, annegentle, jd__, shardy, russellb, holms, markwash, gabrielhurley, dolphm, mikal_laptop, markmcclain20:27
ttx#startvote Grant Liz Blanchard exceptional ATC status? yes, no, abstain20:27
openstackBegin voting on: Grant Liz Blanchard exceptional ATC status? Valid vote options are yes, no, abstain.20:27
openstackVote using '#vote OPTION'. Only your last vote counts.20:27
gabrielhurley#vote yes20:28
russellb#vote yes20:28
markmcclain#vote yes20:28
dolphm#vote yes20:28
markwash#vote yes20:28
mikal_laptop#vote yes20:28
annegentle#vote yes20:28
markmc#vote yes20:28
shardy#vote yes20:28
holms#vote yes20:28
notmyname#vote yes20:28
ttxisn't voting fun ?20:28
vishy#vote yes20:28
ttx#vote yes20:28
jd__#vote yes20:28
ttx30 more seconds20:28
jd__will be funnier with Gerrit!20:28
openstackVoted on "Grant Liz Blanchard exceptional ATC status?" Results are20:28
openstackyes (14): markmc, ttx, notmyname, vishy, annegentle, jd__, shardy, russellb, holms, markwash, gabrielhurley, dolphm, mikal_laptop, markmcclain20:28
jd__*click* *click* *click*20:28
dolphm /vote for gerrit20:28
gabrielhurleygreat. thanks folks!20:28
ttxnotmyname: t occurred to me that under the new use-gerrit-to-vote, abstain will look a lot like not voting at all20:29
ttxmaking it a lot less fun20:29
notmynamettx: we have a +020:29
*** jlucci has joined #openstack-meeting20:29
ttxbut those look like comments most of the time.20:29
dolphmttx: i use +0 regularly as an intentional "this is my feedback but i'm abstaining from a +1 or -1"20:29
markwashgabrielhurley: its great to bring in people who help out the community without necessarily being code committers20:29
ttxnotmyname: I guess it would work if you're careful with it20:29
ttx#info Both motions approved20:30
ttx#topic Open discussion20:30
*** openstack changes topic to "Open discussion (Meeting topic: tc)"20:30
ttxAnything, anyone ?20:30
notmynamettx: ya, seems like an abstain should be explored20:30
ttx"After using git/gerrit for code and infrastructure, OpenStack decides to use it for governance too"20:31
*** hanrahat has quit IRC20:31
ttxnotmyname: I think Gerrit 2.6 has something along those lines configurable20:31
ttxif I remember what jeblair said in the thread correctly20:31
*** jrodom has quit IRC20:32
markwashregarding the uploading history to the git repo20:32
markwashsrsly can we just put the meeting logs in a directory in that repo?20:32
markwashI don't think we immediately need a cleaned up summary of all the things20:33
markwash*old* meeting logs, that is20:33
ttxmarkwash: if we just do TC-era, it should be easy20:33
dolphmmarkwash: ah to establish history?20:33
markwasha scifi dream world where you monitor your government by doing git pull :-)20:34
gabrielhurleycan I --rebase?20:34
gabrielhurleyor --amend?20:34
ttxmordred: ideally the TC charter wiki page should be a readonly mirror of a version we'll put in the governance repo20:34
markwashpush -f!20:34
mordredttx: yes20:34
gabrielhurleyttx: +1 to that!20:34
mordredttx: or a redirect page to a published page on openstack.org/ even20:35
markwashI'm pretty sure huxley would have a field day with my silliness. . maybe he already did20:35
jeblairthe governance repo can be a sphinx doc and published on openstack.org, then the wiki can link there20:35
ttxmordred: whatever20:35
ttxok, we'll flesh out implementation in the next weeks20:35
ttxAny last minute comment before we close ?20:35
dolphmcan we use markdown?20:36
ttxdolphm: anything wrong with XML ?20:36
*** kiall_ is now known as Kiall20:36
ttxXML is enterprise. Always an option20:36
mikal_laptopLet's port the TC to Java20:37
holmsxml is enteprise :)))))20:37
jd__considering how OpenStack is going entreprise20:37
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:37
openstackMeeting ended Tue Aug 20 20:37:27 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-08-20-20.01.html20:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-08-20-20.01.txt20:37
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-08-20-20.01.log.html20:37
ttxThanks everyone20:37
*** ocozalp has joined #openstack-meeting20:37
ttxnext meeting: release status meeting in 23min20:37
*** mikal has joined #openstack-meeting20:38
*** hanrahat has joined #openstack-meeting20:38
mordredttx: btw, did you se this: https://github.com/emonty/cookiecutter-openstack ?20:39
mordredmarkmc: ^^20:39
markmcmordred, nope, but it's definitely a good idea20:40
markmcmordred, when I started tuskar, I was going to do something like that20:40
*** MarkAtwood2 has joined #openstack-meeting20:40
markmcmordred, but include basic service stuff, config files, logging, rest API, etc.20:40
markmcmordred, your approach is probably better to start with20:40
*** MarkAtwood2 has quit IRC20:41
mordredmarkmc: cool - well, I proposed pulling it in as a new repo20:41
markwashmordred: your gravatar is terrifying!20:41
markmcmordred, link?20:41
mordredmarkmc: with hacking-core having +2 - since it seems like it' in that general world...20:41
markwashmordred: its staring into my soul20:41
*** SergeyLukjanov has quit IRC20:42
hub_capmordred: there was a guy who was trying to do this cookiecutter type stuff on the ML like ~1mo ago20:43
hub_capbut he wasnt using cookiecutter20:43
mordredhub_cap: oh yeah?20:43
hub_capbonedragon or something he named it20:43
*** jrodom has joined #openstack-meeting20:43
hub_capbone something20:43
markmcmordred, hacking-core would make it part of oslo, but it's not a library20:43
markmcmordred, sounds good to me, though20:43
mordredmarkmc: yeah - I was torn on that - figured it's probably a decent enough set of people to start, but happy to give it a different group20:43
markmcmordred, I think it's in scope for oslo - e.g. "this is how a new project should handle config files"20:45
markmcmordred, it'll naturally go down that route in time20:45
* markmc adds another project to Oslo wiki page :)20:45
*** lblanchard1 has joined #openstack-meeting20:45
*** lblanchard has quit IRC20:46
russellb#endmeeting ?20:51
markwashrussellb: it already ended20:51
markwashback when we started talking about XML :-)20:51
markwashttx has a pool to attend to20:51
*** roampune has quit IRC20:52
*** stevemar has quit IRC20:54
ttxnow, that was short20:54
*** jrodom has quit IRC20:55
*** mikal has quit IRC20:56
*** ocozalp has left #openstack-meeting20:59
ttxmarkmc, dolphm, notmyname, jd__, markwash, jgriffith, russellb, shardy, gabrielhurley, markmcclain: still around ?21:00
*** dolphm_ has joined #openstack-meeting21:00
ttxle's get this rolling21:01
ttx#startmeeting project21:01
openstackMeeting started Tue Aug 20 21:01:26 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: project)"21:01
openstackThe meeting name has been set to 'project'21:01
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:01
ttx#topic General stuff21:01
*** openstack changes topic to "General stuff (Meeting topic: project)"21:01
ttxSome FeatureProposalFreezes hit this week:21:01
ttxNova and Cinder on Aug 21, Neutron and Heat on Aug 2321:01
*** jrodom has joined #openstack-meeting21:02
ttxthat's all I had21:02
ttxsdague, annegentle, mordred: news from QA/Docs/Infra programs ?21:02
ttxOr anything newsworthy before we dive into project-specific stuff ?21:03
ttxwell, I guess not21:04
*** dolphm has quit IRC21:04
ttx#topic Oslo status21:04
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:04
ttxmarkmc: hi!21:04
ttx#link https://launchpad.net/oslo/+milestone/havana-321:04
markmcso, the main thing on my mind is the patch set to port nova to oslo.messaging: https://review.openstack.org/3992921:04
markmcit's in pretty good shape21:05
ttx100% done, 0% under review, 0% in progress, 0% not started21:05
*** gyee has joined #openstack-meeting21:05
markmcalso, we deferred secure messaging to icehouse21:05
ttxYou mentioned freezing oslo-incubator's features ahead of projects FeatureProposalFreeze so that the relevant syncs can be proposed in time...21:05
markmcthere's a few low priority bps close to being merged21:05
markmcyeah, I consider us feature frozen apart from those three21:05
ttxThere are 3 "Low" blueprints under review, and at least some of them look like they will end up in the incubator code ?21:05
markmcgiving them another week or so21:05
*** jrodom has quit IRC21:05
*** anniec has joined #openstack-meeting21:06
markmcnone of them should be a big regression risk for projects21:06
markmcthey're all net-new21:06
ttxWe should just make sure the consuming projects are fine for syncs after their FeatureProposalFreezes21:06
ttxcorner case21:07
markmcyeah, I don't think it'll apply for any of these three21:07
markmcI'm not sure any projects will start using them in havan21:07
markmcwhich obviously begs the question, why merge them :)21:07
markmcbut, since they're close ... :)21:07
*** nati_ueno has quit IRC21:07
russellbmarkmc: mainly to let someone have it checked off their todo list21:08
ttxwhich begs the question, should Oslo feature-freeze around h2 ?21:08
markmcnah, it's just specifically those three21:08
ttxto let the consuming project catch up in making use of that stuff21:08
markmcvery plausible that stuff merging today could be picked up by other projects21:08
*** nati_ueno has joined #openstack-meeting21:08
markmcand that the per-project bps could have been approved ages ago21:08
ttxmarkmc: I was just trolling you. anything else you wanted to raise ?21:09
markmcyeah, setting a date for releasing oslo.config and oslo.messaging 1.2.021:09
markwashyeah that21:09
markmcI'm figuring after havana-321:09
markmcit's all just about having time to update the requirements.txt of projects to not point to tarballs.openstack.org21:09
ttxmarkmc: I suspect it's only bugfixes compares to current versions ?21:09
markmcright, exactly21:10
markwashis it an issue for packagers for us to depend on an alpha release in glance? sorry if I'm not remembering things I ought to21:10
ttxmarkmc: can be a post-h3 pre-rc1 thing21:10
*** roampune has joined #openstack-meeting21:10
markmcmarkwash, https://wiki.openstack.org/wiki/Oslo#Why_aren.27t_alpha_releases_of_oslo.config_published_to_PyPI.3F :)21:10
*** danwent has joined #openstack-meeting21:10
markmcmarkwash, it's not an issue for packagers, no21:10
ttxOther questions about Oslo ?21:10
markwashI looked there, and couldn't find what I wanted, but I am lazy21:11
ttx#topic Keystone status21:11
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:11
ttxdolphm: hi21:11
ttx#link https://launchpad.net/keystone/+milestone/havana-321:11
ttx54% done, 18% under review, 27% in progress, 0% not started21:11
ttxLooks good to me21:11
dolphm_i think we managed to go from 0% done to 54% since last week :P21:12
ttxdolphm_: About key-distribution-server, did we settle on merging it early in icehouse ?21:12
ttxAnd concentrate on moving the other projects to fully use trusted-messaging within that cycle ?21:12
dolphm_ttx: i haven't had a chance to talk to simo about it yet, but that's certainly what i'm leaning towards after the ML discussion21:12
ttxdolphm_: looks like that's what markmc understood too21:13
markwashhas the security team been involved in this plan, and I just missed it? this is a case where sometimes audits are comforting21:13
ttxdolphm_: please update blueprint accordingly when you get it confirmed21:14
dolphm_ttx: will do, i'll also poke the list in that thread21:14
dolphm_markwash: not that i'm aware of21:14
ttxmarkwash: They are summoned using SecurityImpact tag21:14
ttxalthough that doesn't work all the time21:14
ttxdolphm_: store-quota-data and pagination-backend-support are marked "Slow progress", could you elaborate on that ?21:15
ttxBoth getting unlikely to make it ?21:15
dolphm_they're raising red flags for me..21:15
dolphm_store-quote-data has just had a slow code review cycle thus far, but hopefully we can start dedicating more review bandwidth to it21:16
ttxdoes that mean you're pretty confident for the 'Caching layer implementation around driver calls' thing ?21:16
dolphm_pagination has expanded in scope and is being split into a second blueprint to focus on filtering21:16
dolphm_we'll likely target filtering to havana-m3 and pagination will be dependent on that21:16
ttxdolphm_: Within the remaining features, is there anything that the consuming projects need changes to take advantage of the feature (like the KDS) or is it all internal ?21:17
ttxtrying to make sure they have enough turnaround to make it useful21:17
dolphm_store-quota-data and KDS would both be disabled by default, but expose new API's when explicitly included in the wsgi pipeline21:18
*** vipul is now known as vipul-away21:18
dolphm_the same goes for endpoint-filtering21:18
ttxdolphm: anything you wanted to raise ?21:18
dolphm_i think we covered it all!21:18
ttxQuestions anyone ?21:18
*** vipul-away is now known as vipul21:18
ttx#topic Ceilometer status21:19
*** openstack changes topic to "Ceilometer status (Meeting topic: project)"21:19
ttxjd__: hey21:19
ttx#link https://launchpad.net/ceilometer/+milestone/havana-321:19
ttx25% done, 25% under review, 50% in progress, 0% not started21:19
ttxStill a bit behind, but looking better with only 8 blueprints left :)21:19
jd__we are à fond les ballons21:19
ttxjd__: Is there more to alarming-logical-combination than the two reviews already proposed ?21:19
jd__ttx: not sure, but I think it's at least 80% of the bp21:20
jd__I didn't check with sileht yet, he sent the working patches today21:20
ttxWhat's the status of eglynn "High" blueprints (alarm-audit-api and alarm-service-partitioner) ?21:20
jd__eglynn has been on vacation but he's going to finish RSN21:20
jd__he has patches almost ready to be sent21:20
*** thingee has joined #openstack-meeting21:20
jd__and I'm still working with terriyu on the group by one21:21
ttxjd__: anything else you wanted to mention ?21:21
ttxQuestions on Ceilometer ?21:21
*** neelashah1 has quit IRC21:21
ttx#topic Swift status21:22
*** openstack changes topic to "Swift status (Meeting topic: project)"21:22
ttxnotmyname: o/21:22
ttxnotmyname: what news ?21:22
notmynamewe got 1.9.1 released, and so now the next thing is moving to pbr21:22
notmynameI'll be working with mordred on this this week21:22
*** thomasbiege1 has joined #openstack-meeting21:22
notmynamethat will necessitate some versioning dances, and it will affect packagers21:22
ttxHe completed the merge-tags thing21:22
mordrednotmyname: I may need to have you work with clarkb or someone else21:23
mordredI'm out starting tomorrow morning21:23
notmynameright, but we have a migration phase to do21:23
notmynamemordred: ok21:23
mordredor, wait two weeks until I'm back21:23
mordredI'm fine either way21:23
notmynamesooner the better since it affects every packager out there21:23
ttxnotmyname: ok, keep me in the loop, I'll have to adjust release process accordingly21:23
*** thang_ has quit IRC21:23
notmynamettx: will do21:23
notmynamein other news..21:23
*** benl_ has joined #openstack-meeting21:23
notmynameerasure coding discussions and progress is coming along21:24
notmynameand the local file system work is going well also21:24
ttxnotmyname: Can you confirm the next Swift release should probably be the Havana coordinated one ?21:24
notmynameyes, it should, unless there is something major that comes up, like a security issue21:25
notmynameI'm not sure yet if these will be completed before havana, but they are major features we're tracking21:25
ttxAny major feature on your roadmap for this one ? I suspect erasure codes won't make it ?21:25
*** lexinator has quit IRC21:25
notmynameEC likely won't21:25
ttxnotmyname: anything else you wanted to raise ?21:25
notmynameI hope the LFS things will21:25
notmynamehotel block for the swift hackathon has been set21:26
*** thomasbiege1 has quit IRC21:26
notmynamethat's what I have21:26
ttxQuestions about Swift ?21:26
ttx#topic Glance status21:27
*** openstack changes topic to "Glance status (Meeting topic: project)"21:27
ttxmarkwash: o/21:27
ttx#link https://launchpad.net/glance/+milestone/havana-321:27
ttx50% done, 0% under review, 50% in progress, 0% not started21:27
ttxround numbers21:27
markwashthat's the goal21:27
ttxLooks good, though more code proposed wouldn't hurt21:27
*** sushils has joined #openstack-meeting21:27
ttxmarkwash: Should configurable-formats be considered "Needs Code Review" with https://review.openstack.org/#/c/42535/ ?21:28
markwasha fair amount is proposed, and just needs some more review and rework, so maybe I haven't been updating the formats correctly21:28
markwashso should basic quotas21:28
markwashand scrubber refactoring21:28
*** benl_ has quit IRC21:28
ttxmarkwash: ok, I'll let you update them all21:28
ttxHow is api-v2-property-protection looking at this point ?21:28
ttxYou know how much I like this one.21:29
markwashI know21:29
markwashwe should probably keep it around for icehouse, for your sake21:29
ttxI'll be sad to see it go, but otoh...21:29
markwashI'll be doubleplusgood and resolve that one for next week21:29
markwashwe've also had some important bugs pop up21:30
*** lexinator has joined #openstack-meeting21:30
markwashso those will take some priority for me21:30
markwashthough they are mostly also in review21:30
ttxmarkwash: please target them t oh3 so that we keep them on hte milstone radar21:30
ttxmarkwash: anything you wanted to mention ?21:30
markwashwhat does a fond les ballons mean?21:30
*** bdpayne has quit IRC21:31
markwashso I don't spend all next week puzzling over it21:31
markmcfound of balloons21:31
ttxvery quickly21:31
ttxlike "à fond la caisse".21:31
markwashoh yes, like that21:31
ttxQuestions on Glance ?21:31
markwash. . .21:31
ttxmeans "very quickly"21:31
ttx#topic Neutron status21:32
*** openstack changes topic to "Neutron status (Meeting topic: project)"21:32
ttxmarkmcclain: hi!21:32
ttx#info Neutron feature code needs to be up for review by Friday21:32
ttx#link https://launchpad.net/neutron/+milestone/havana-321:32
*** vijendar has quit IRC21:32
ttx41% done, 51% under review, 7% in progress, 0% not started21:32
ttxSo it's that 7% in progress that needs to be solved this week21:32
*** bdpayne has joined #openstack-meeting21:33
ttxsounds more than doable21:33
*** litong has quit IRC21:33
ttxHow are ipv6-feature-parity and configurable-ip-allocation looking so far ?21:33
*** alexpilotti has quit IRC21:33
markmcclainconfigurable ip allocations is still good21:33
*** dklyle has joined #openstack-meeting21:33
ttxand ipv6-feature-parity still in jeopardy ?21:34
*** topol has quit IRC21:34
markmcclainipv6 will be close21:34
ttxwell, you can give you an exception quite eaily21:34
markmcclainyeah.. there's a good chance that will happen21:35
ttxYou have two Low blueprints without a status set: nec-port-binding and nvp-vpnaas-plugin21:35
ttxwould be cool to ask their assignees to give us an idea of where they are21:35
ttxAlso two blueprints in the triaging queue: multi-workers-for-api-server and neutron-fwaas-explicit-commit21:35
markmcclainah.. missed those earlier.. I'll follow up21:35
ttxoh, and a third one just added21:36
ttxUnless they come with code proposed my suggestion would be to defer them :)21:36
markmcclainso mulitworkers has 3 code proposals that we're sorting out21:36
ttxYou have a lot of Low blueprints that shall go down the drain at the end of the week. Hope you communicated that FeatureProposalFreeze well :)21:36
markmcclainexplicit commit has code proposed, but still trying to develop a team consensus21:37
ttxbut it should really help to focus review activity21:37
markmcclainI have, but I get the feeling reality will set in when they move out of havana21:37
ttxmarkmcclain: anything else you wanted to raise ?21:37
markmcclainno.. we've covered it21:38
ttxQuestions on Neutron ?21:38
ttx#topic Cinder status21:38
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:38
ttxjgriffith: hola!21:38
ttx#info Cinder feature code needs to be up for review by tomorrow21:38
ttx#link https://launchpad.net/cinder/+milestone/havana-321:38
*** dprince has quit IRC21:38
ttx35% done, 29% under review, 23% in progress, 11% not started21:38
*** zhelezniakov has joined #openstack-meeting21:38
ttxis jgriffith around ?21:39
*** dklyle has quit IRC21:39
ttxI guess not, let's skip21:40
ttx#topic Nova status21:40
*** openstack changes topic to "Nova status (Meeting topic: project)"21:40
ttxrussellb: hey21:40
ttx#info Nova feature code needs to be up for review by tomorrow21:40
ttx#link https://launchpad.net/nova/+milestone/havana-321:40
russellbi sent out a review call to arms to nova-core yesterday :-)21:40
russellbgoing to be an intense couple of weeks getting in what we can21:41
russellbmost stuff is ready for review, or super close ... lots in "Low" that will get deferred i suspect21:41
ttxLast time I looked this was lacking a bit in the %done department...21:41
russellbi haven't been watching that stuff very closely21:41
russellbhence the call to arms to reviewers21:41
ttxBut my main concern is those %inprogress with one day left21:41
ttx25% done, 57% under review, 17% in progress, 0% not started21:41
*** boris-42 has quit IRC21:41
russellball the ones left in progress are ones people have told me will be ready on time21:42
russellbwe'll see21:42
russellbbut i have no problems deferring any of them if not21:42
ttxEspecially the 4 "High" ones21:42
russellbi think they'll make it21:42
ttxWould be great to properly complete compute-api-objects21:42
ttxand graceful-shutdown21:42
russellbi haven't gotten a libvirt console logging update this week though21:42
russellbgraceful shutdown was deferred21:43
russellb( a few minutes ago)21:43
russellbwas able to confirm it won't make it21:43
russellbcompute api objects has a ton of patches up for review or already merged21:43
ttxmikal might be a bit busy with newkid21:43
russellbso that one may not make it ... :-/21:43
russellbthe issue that we just can't ever make go away21:44
ttxit's amlready a miracle so many made it, tbh21:44
ttxrussellb: anything else you wanted to mention ?21:44
russellbdon't think so21:44
ttxAny question on Nova ?21:44
ttx#topic Heat status21:44
*** openstack changes topic to "Heat status (Meeting topic: project)"21:44
ttxshardy: o/21:44
ttx#info Heat feature code needs to be up for review by Friday21:45
shardyttx: hi21:45
ttx#link https://launchpad.net/heat/+milestone/havana-321:45
ttx61% done, 19% under review, 19% in progress, 0% not started21:45
*** Daisy has joined #openstack-meeting21:45
ttxLooking good, just need to convert those 19% to "under review" before eow21:45
shardyThink we're looking OK apart from the two blocked ones21:45
shardytrusts and vpnaas21:45
ttxAbout heat-trusts - looks like it might need to be deferred or granted an exception to deal with lateness on the python-keystoneclient side...21:46
shardyyeah, I have a feeling some of the in-progress are already under review, but need to check with the assignees21:46
shardyWell the keystoneclient patch is up just needs review21:46
ttxDo you expect that to move before the end of the week ?21:46
shardydolphm_: ^^21:47
ttxmaybe hunt down some keystone reviewers :)21:47
dolphm_i can get some eyes on it :)21:47
ttxdolphm_: thx21:47
ttxshardy: anything else you want to raise ?21:47
shardyI'm hoping to post the heat part of the patch tomorrow, but we can't merge it without the keystoneclient patch, and a keystoneclient release I guess21:47
shardyttx: no think that's it, thanks!21:47
ttxshardy: you can post it so that it gets early reviews21:48
ttxand passes FPF21:48
ttxQuestions about Heat ?21:48
*** jhenner has quit IRC21:48
shardyttx: yeah, just been battling with various trusts issues for a few days, nearly there now ;)21:48
ttx#topic Horizon status21:49
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:49
ttxgabrielhurley: o/21:49
ttx#link https://launchpad.net/horizon/+milestone/havana-321:49
ttx35% done, 42% under review, 21% in progress, 0% not started21:49
ttxLooks very much on track to me21:49
ttxNo further comment.21:49
gabrielhurleyThe review status is actually mostly waiting on gerrit/jenkins. we've had a lot of merge issues lately. note the 11 reviews which are approved but not merged here: https://review.openstack.org/#/q/status:open+project:openstack/horizon,n,z21:49
gabrielhurleybut yeah, I'd say on track21:50
ttxgabrielhurley: is it just general slowness, or exceptional recent slowness ?21:50
* ttx checks queue21:50
gabrielhurleytoday's been slower than usual21:50
ttxgate is 40-changes deep21:50
gabrielhurleyand recently we just incidentally had a bunch of merge conflicts that required rebases21:50
ttxwill take some time21:51
gabrielhurleyso we've had to run some of these repeatedly21:51
*** spzala has quit IRC21:51
gabrielhurleyI figure give it a day or two and those'll all get through21:51
gabrielhurleynot ideal21:51
gabrielhurleybut not terrible21:51
*** thomasbiege1 has joined #openstack-meeting21:51
ttxthat's why it's better to not rely on it being usable in the last week(s). There will always be too much load21:51
ttxand merge the key stuff before21:51
ttxgabrielhurley: anything else you wanted to mention ?21:52
gabrielhurleyI added https://blueprints.launchpad.net/horizon/+spec/add-trove-panels-unit-tests-coverage to the H3 targets... I may or may not keep it there. Gonna discuss more at the Horizon meeting next.21:52
*** roampune has quit IRC21:52
gabrielhurleythat's all I've got21:52
ttxhttps://blueprints.launchpad.net/horizon/+spec/swift-display-metadata could use a status other than unknown21:52
hub_capgabrielhurley: do the guys working on the trove stuff know about it?21:52
*** kspear_ has joined #openstack-meeting21:53
hub_cap*do they know u are discussing in next meeting21:53
gabrielhurleyttx: it's needs code review. fixed. I got distracted on that one21:53
ttxOther questions on Horizon ?21:53
ttxIs jgriffith in the house ?21:53
gabrielhurleyhub_cap: no, I only added it an hour ago. but it's not about the code. it's more of a principle decision21:53
hub_capokey! im sure they'd like to listen, i know i will ;)21:54
hub_capill tell them not to interject too much heh21:54
gabrielhurleysounds good21:54
ttxLooks like we don't have jgriffith today.21:54
*** dklyle has joined #openstack-meeting21:54
ttxI'll catch up with him tomorrow21:54
*** vasiliy has joined #openstack-meeting21:54
ttx#topic Incubated projects21:55
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:55
*** robertmyers has joined #openstack-meeting21:55
ttxNobodyCam: hola!21:55
ttxdevananda, hub_cap: howdy21:55
ttxAny question ?21:55
*** ftcjeff has joined #openstack-meeting21:55
hub_capnope. just fnishing heat21:55
NobodyCamhola ! it's /me for devananda21:55
hub_capin a mountain in NC lol21:55
NobodyCamWe are down a couple of contributors, out on vacation. Deva is off in the desert burning things for the next two weeks, but we are moving forward slowly.21:55
*** Toshi has joined #openstack-meeting21:56
ttxhub_cap: still on track for integrating heat in h3 ?21:56
hub_capas of now most def21:56
ttxNobodyCam: ack21:56
hub_capill know more next wk21:56
hub_capim sure ill have bugs but thats what RC1 is for ;)21:56
ttxno that's what integration tests are for :)21:57
ttxnext on the todo list I gather :)21:57
hub_capits #2 good sir21:58
ttxok, well unless you have more questions, or we see the last minute return of jgriffith...21:58
*** topol has joined #openstack-meeting21:58
ttxWe'll close now21:58
hub_caplol im good21:58
*** topol has quit IRC21:58
* ttx hugs back21:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:58
openstackMeeting ended Tue Aug 20 21:58:48 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-08-20-21.01.html21:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-08-20-21.01.txt21:58
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-08-20-21.01.log.html21:58
gabrielhurleywith one minute to spare21:59
*** topol has joined #openstack-meeting21:59
*** dklyle has quit IRC21:59
*** thomasbiege1 has quit IRC22:00
kspear_the last minute is now reserved for hugs22:00
*** robertmyers has left #openstack-meeting22:00
gabrielhurley#startmeeting horizon22:00
openstackMeeting started Tue Aug 20 22:00:45 2013 UTC and is due to finish in 60 minutes.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
*** openstack changes topic to " (Meeting topic: horizon)"22:00
openstackThe meeting name has been set to 'horizon'22:00
*** AlanClark has quit IRC22:01
gabrielhurley#topic overview22:01
*** openstack changes topic to "overview (Meeting topic: horizon)"22:01
*** lblanchard1 is now known as lblanchard22:01
gabrielhurleyHello folks!22:01
lblanchardhey all!22:01
vasiliyhi ^)22:01
gabrielhurleyI've got more "general" business than usual today. Shocking, I know.22:01
*** absubram_ has joined #openstack-meeting22:01
*** gyee has quit IRC22:01
*** robertmyers has joined #openstack-meeting22:01
*** markmc has quit IRC22:02
gabrielhurleyFirst off, I'd like to let everyone know that Liz Blanchard and Jaromir Coufal were granted ATC status by the technical committee earlier today for the contributions in the UX arena. So congrats to them!22:02
lblanchardwoo hoooo! And thanks to gabrielhurley for the nomination :) Happy to be an ATC!22:02
jpichCongratulations :)22:02
*** rnirmal has quit IRC22:02
*** markwash has left #openstack-meeting22:03
gabrielhurleyNext up, I've got a big item I'd like to get some group feedback on...22:03
vkmc:) Congratz!22:03
gabrielhurleyThe Trove team put up a review for adding panels to manage Trove databases and backups: https://blueprints.launchpad.net/horizon/+spec/add-trove-panels-unit-tests-coverage22:03
*** markmcclain has quit IRC22:03
robertmyershello, that is my doing :)22:04
gabrielhurleyNormally my policy is not to include projects into the OpenStack Dashboard repo until they graduate from incubation (due to pains with Quantum a few years back)22:04
*** noslzzp has quit IRC22:04
robertmyersI see22:04
gabrielhurleyhowever Trove is in very stable shape, all the TC feedback has been positive, the API seems stable, and it's properly filtered behind the service being in the service catalog.22:04
*** ayoung has quit IRC22:05
hub_capthanks gabrielhurley!22:05
gabrielhurleySince I think there are gonna be a lot of folks interested in Trove sooner rather than later, I could see it being a significant boon to them to have an optional inclusion in the dashboard in the final H release while they prepare for an official release in I.22:05
robertmyersThat would be great22:05
hub_cap+ <322:05
vasiliy+1 for Trove22:05
gabrielhurleyPerhaps it'd also encourage them not to mess with their APIs too much ;-)22:05
gabrielhurleyso I mostly wanted to see if any of the Horizon core folks had objections to the inclusion in H22:06
hub_capgabrielhurley: oh besides the entire api rewrite once we go incubated (jk) ;)22:06
*** dcramer_ has quit IRC22:06
robertmyersgabrielhurley: there seems to be 2 Blueprints22:06
gabrielhurleyhaha. yeah22:06
*** whenry has quit IRC22:07
gabrielhurleyrobertmyers: so there are. I think that one can be closed as a duplicate in favor of the one I linked/you've been working on.22:07
gabrielhurleynow I'm confused22:07
gabrielhurleyI had that backwards22:07
robertmyersthe one I just sent was the one the review is attached to22:07
gabrielhurleyso the other should be closed22:07
gabrielhurleyI'll fix that22:08
gabrielhurleywe only need one BP22:08
*** burt has quit IRC22:08
robertmyersI think the other assumes the trove panels were added22:08
robertmyersas we do need tests22:08
david-lylethey both seem valid22:08
gabrielhurleylet's get some tests into the current review before it merges, please22:08
robertmyerssounds reasonable22:09
robertmyersI wanted eyes on it first to see if it was on the right path22:09
gabrielhurleyusually having a basic suite of tests is part of the bar for feature inclusion22:09
gabrielhurleytotally understandable22:09
gabrielhurleylet's just add the tests before merging it22:09
gabrielhurleybut I haven't heard any objections so let's go ahead with the review and aim to merge it in H3!22:09
*** dcramer_ has joined #openstack-meeting22:09
lblanchardrobertmyers: would you post some screenshots in the blueprint?22:09
gabrielhurleythanks for stepping up robertmyers and hub_cap :-)22:09
*** spenceratx has quit IRC22:09
robertmyerslblanchard: sure I can22:10
robertmyersgabrielhurley: your welcome22:10
hub_capgabrielhurley: thx for the approval on the bp and the overall support!22:10
hub_capitll be great to have in dashboard22:10
lblanchardrobertmyers: awesome, thanks…will definitely have a look22:10
gabrielhurleyLet's see... next item: I still haven't heard any new news about design summit talk submissions, will continue to let y'all know when there's news.22:10
*** shang has joined #openstack-meeting22:11
gabrielhurleyNext, also important: We really ought to fix https://bugs.launchpad.net/horizon/+bug/1179526 so our source language is correct in transifex22:11
uvirtbotLaunchpad bug 1179526 in horizon "source_lang in Horizon repo is overwritten by Transifex" [High,Confirmed]22:11
*** shang has quit IRC22:11
Daisynice !22:12
gabrielhurleywe've been stalling on this for a while, and I'd rather not let Havana get released without fixing it22:12
gabrielhurleyyep, I saw you there, Daisy ;-)22:12
gabrielhurleyI'm afraid it's gonna mean manually re-uploading a bunch of the translation files, but it needs to happen22:12
jpichAre we going to go the deletion + recreation way?22:12
DaisyI want to help but I'm not the maintainer so I cannot fix it. My plan is to delete the old resource and upload the new version.22:12
*** egallen has quit IRC22:12
gabrielhurleyI can add whoever wants to fix it as an admin on the Horizon transifex project.22:13
gabrielhurleyIf I could get a volunteer to work with Daisy that'd be fantastic.22:13
DaisyThen please add me. And please tell me where is the latest POT file?22:13
jpichI'd like to become more familiar with Transifex so I can try and help22:13
gabrielhurleyDaisy: will do, though it'll probably be easier if one of the Horizon core folks works with you too22:14
jpichWe can try and fix  https://bugs.launchpad.net/horizon/+bug/1182011 at the same time22:14
*** gyee has joined #openstack-meeting22:14
uvirtbotLaunchpad bug 1182011 in horizon "djangojs.po not available on Transifex" [High,Confirmed]22:14
gabrielhurleyjpich: perfect22:14
gabrielhurleyI'll get you both set up22:14
gabrielhurleyall I can really say is "preserve as much as possible of the existing translation work, but getting the job done is more important"22:14
*** ivasev has quit IRC22:14
DaisyYes, I came here to discuss about these with you.22:15
*** dcramer_ has quit IRC22:15
DaisyFirst, I think we need the latest POT file on Transifex with source language as en.22:15
*** stevemar has joined #openstack-meeting22:15
gabrielhurleyjpich: you're already added as a transifex admin, so that's good to go22:16
DaisyThen I need to understand when is the string frozen date.22:16
DaisyFrom Havana release plan, Sep 4 will be the string frozen date. Does that mean, after Sep 4, there won't be any string change?22:16
gabrielhurleythat's the idea22:16
*** robertmyers has quit IRC22:16
gabrielhurleyDaisy: I just added you as a maintainer on the Horizon transifex project as well22:17
DaisyLet's say this way, our translation team can focus on Horzion translation after string frozen. When finishing translation, we can also run Horzion in different langauge setting, which is called Translation Verification Test.22:17
gabrielhurleyYep. That's perfect. We'll do our best to enforce the string freeze.22:18
DaisyWe may find bugs during TVT and we will report.22:18
DaisyWe hope we can get latest POT file update before Sep 4 so that we can spend some time on translation in order to get enough time after string frozen.22:18
DaisyAs I know, the Horizon in Transifex is not updated automatically by Jenkins job. Can I know when and how you update them in Transifex?22:19
gabrielhurleythings shouldn't change *significantly* in the next few weeks, so the sooner you can get the source language issue fixed the sooner you can start working22:19
gabrielhurleyoh, did that never get set up? that's lame...22:20
*** edmund has quit IRC22:20
Daisymaybe I'm wrong...22:20
gabrielhurleyI used to have it linked to the github repo so that it would get the changes when the files changed in the repository22:20
gabrielhurleynot sure if that's been broken subsequently22:20
gabrielhurleyif y'all can investigate that too, that'd be good22:20
gabrielhurleyor if the infra team wants to get things working that's good too. updating manually with the transifex client is easy, but automated is better22:20
Daisyok. let me do the investigation then.22:21
Daisywhere is the link to PoT file in repo?22:21
jpichSo we push pot files out to Transifex automatically, but pull translations manually, is that correct?22:21
gabrielhurleythat's the idea, yeah22:22
Daisydo you generate PoT file manually?22:22
jpichI think many of the projects pull automatically, should we consider doing this too so translators see their contributions included earlier?22:22
gabrielhurleyjpich: it'd be nice to get that working, it didn't happen originally 'cuz the infra folks didn't want to write a second code path to work with django's particularities vs. babel.22:24
jpichDaisy: I think we have 3 pot files to upload, though they may not be up to date at the moment in the repository22:24
*** henrynash_ has joined #openstack-meeting22:24
gabrielhurleyI'm fine with that being an Ichouse target unless you want to work on it22:24
jpichgabrielhurley: I see, that makes sense22:24
gabrielhurleyanyhow, I'll let you two work on it. Email me if you get stuck.22:25
Daisygot it. Thank you, gabrielhurley and jpich .22:25
gabrielhurleylet's jump over to blueprints now22:25
jpichNot sure it'll be possible for me now, but a Icehouse target would be nice22:25
gabrielhurley#topic blueprints22:25
*** openstack changes topic to "blueprints (Meeting topic: horizon)"22:25
gabrielhurleyOverall the blueprint progress is looking really good22:25
vasiliyBlueprint: https://blueprints.launchpad.net/horizon/+spec/improved-boot-from-volume I'd like to discuss screen-shots https://docs.google.com/document/d/1Zg5PS3-s4OJtSoYGttI13OMHEtragDPYv63GUl4zpF4/edit for patch: https://review.openstack.org/#/c/41728/ I need more opinions about implementation of planning changes in the pop-up "Launch Instance".22:25
*** henrynash has quit IRC22:26
*** henrynash_ is now known as henrynash22:26
*** changbl has quit IRC22:26
gabrielhurleyvasiliy: did you have specific questions? I reviewed that this morning and thought it seemed reasonable.22:27
vasiliyno specific question - just would like to hear opinion from core-developers22:27
david-lylelooks good to me, just need to finish reviewing the code22:28
gabrielhurleyalthough, now that I look at the screenshots, I realize that this has the downside of moving a required field off the first tab...22:29
*** lbragstad has quit IRC22:29
vasiliywe will combine all needed options in one tab "Storage Backend"22:30
david-lylethat's already been the case though (key)22:30
kspear_personally i'd prefer to merge the entire storage backend tab with the details tab22:30
gabrielhurleydavid-lyle: keypair isn't technically required, though that does catch people out.22:30
gabrielhurleyIn the short term I think I'm with kspear_... in the long term, I think we may want to investigate a two-step form like when launching things through Heat22:31
david-lylecan't create an instance without one or network22:31
*** stevemar has quit IRC22:32
gabrielhurleyby which I mean you'd have a first form where you select the source of the instance (image, volume, etc.) and submit that, then from you'd get the approriate set of other options in a second form. This would also simplify some of the work we're doing with tailoring flavor options to image sizes, etc.22:32
*** sacharya has quit IRC22:32
lblanchardI agree that long term we can revisit this form to organize mostly everything on one clean page22:32
gabrielhurleyjust throwing thoughts out there for long-term22:32
gabrielhurleyFor now though I do think keeping image selection on the first tab would be best22:33
gabrielhurleyit's a place where there's no sane default, and you'll just get an error if you try to submit (unlike keypair, network, etc)22:33
gabrielhurley(we should work on improving the sane defaults of those fields, btw, but that has nthing to do with this patch)22:34
gabrielhurleyvasiliy: does that make sense?22:34
vasiliymake sense - but it's better to understand what do we need to make to complete current work on this blueprint22:35
zhelezniakovin any cases user can select only one option: image, volume, snapshot etc/22:35
zhelezniakovso, i don't see any reasons, why this options should be on the different tabs22:36
gabrielhurleycorrect, it should only be on one, but I'm pretty sure it should be on the first tab, 'cuz it's fundamental to launching the instance. I would almost say it is the most fudamental aspect of choosing what instance you're going to launch.22:37
zhelezniakovi think it is good idea22:37
vasiliyso let's combine options from "storag backend" with first tab?22:38
vasiliygood - thanks22:38
zhelezniakovIf all fundamental options are placed on the one tab22:38
gabrielhurleySo, on other blueprints...22:39
gabrielhurleyI did hear from bradjones about https://blueprints.launchpad.net/horizon/+spec/network-quotas and he's gonna look at it this week. If nothing's up by next week I'm gonna bump that.22:39
jpichThis kind of looks like what I did to fix a bug22:40
uvirtbotLaunchpad bug 1109140 in horizon "Floating IP quota not coming from Quantum" [Medium,In progress]22:40
*** sandywalsh has quit IRC22:40
gabrielhurleyI think the BP encompasses more22:40
gabrielhurleybut I'm glad you fixed that22:40
absubram_can I bring up the cisco blueprint :)22:40
gabrielhurleyabsubram_: sure22:40
*** shardy is now known as shardy_afk22:40
*** zhelezniakov has quit IRC22:41
absubram_thanks.. I have my diffs out on review but it failed Jenkins a few times already.. thanks to jpich and david-lyle for pointing out my commit message error22:41
*** jmontemayor has quit IRC22:41
absubram_but it still looks like Jenkins is arbitarily failing different tests for me each time.. it passes once fails the next without any changes to my diffs22:41
absubram_I have actually as of now sent my diffs for the new dashboard with it turned off by default22:42
*** nijaba has quit IRC22:42
gabrielhurleyyeah, I see some LOST jobs on there. Jenkins hasn't been great lately.22:42
absubram_there are some changes to the cisco plugin that if it goes into H3 will need corresponding changes to Horizon too22:42
gabrielhurleyI don't know that I can offer much except to say "keep trying" as far as Jenkins goes.22:42
absubram_so I felt having it turned off for the moment was better but that I could at least get the infrastructure up so that I could get some review comments22:43
gabrielhurleyit would be good to know if those plugin changes are going to happen ASAP22:43
absubram_plus I also need to add test cases22:43
absubram_and fix some existing tests when the dashboard is turned om22:43
gabrielhurleyyep, definitely need those22:43
*** kbs has joined #openstack-meeting22:43
absubram_will get the testcases fixed and new ones added by this week22:43
*** leif_ has quit IRC22:44
absubram_but I wouldn't mind feedback about the rest of the code in the meantime given that this is my first attempt :)22:44
gabrielhurleyI think people are aware of it... I'll try and take a look. Perhaps you could offer up some advice on how to test your patch since I don't think most folks know how to simulate a Cisco N1K...22:44
absubram_there's a blueprint in neutron for the plugin changes22:44
absubram_I believe the review will be up in a day or so22:44
absubram_ah of course.. as I mentioned though I have actually tuend the dashboard off22:45
gabrielhurleyThe Neutron BP is all well and good, but this is why we try not to land features on our side that aren't done by early H3 at the very latest... these last minute changes to plugins mean we end up with unstable code.22:45
absubram_so there should be no change to horizon functionally with my diffs right now22:45
gabrielhurleyokay. we'll see how the changes in Neutron go22:45
*** bdpayne has quit IRC22:46
absubram_I see ok.. I'll put up instructions on how to work with the cisco n1k in the bklueprint so people can try it out22:46
absubram_I'll also add screenshots22:46
gabrielhurleythat would be good, thanks.22:46
gabrielhurleyAnybody else have blueprints they want to bring up or that they're concerned about?22:46
Toshican I bring up my topology view bp?22:46
gabrielhurleyI spent almost all day reviewing today, and feel like I know where things are at.22:46
gabrielhurleyToshi: definitely22:46
*** stevemar has joined #openstack-meeting22:47
ToshiI think this implememtation is not so much different from the previous version, and no impact to other component, so If you could review and it would be merged to habana, that would be great.22:47
*** kbs1 has quit IRC22:47
gabrielhurleyyep. for a while there I wasn't sure we'd see code for it, but now that it's up I see no reason not to include it22:47
gabrielhurleyI'll retarget that now22:47
gabrielhurleyblueprint is back in H322:48
*** bdpayne has joined #openstack-meeting22:48
lblanchardToshi: UI design looks great at first glance, I will add more specific feedback in the BP tomorrow.22:48
Toshigabrielhurley:Thank you very much!22:48
gabrielhurleyYou're welcome22:48
gabrielhurleyAnybody else got BPs to discuss?22:48
Toshilblanchard:Thanks, any coments are welcome :-)22:49
*** jlucci has quit IRC22:50
gabrielhurleyJust as a general FYI, Jenkins is really backed up currently, so things are taking a very long time to merge. There have also been a lot of merge conflicts unfortunately, so if you see a review that didn't merge cleanly but is otherwise ready to go, try and be proactive in updating it and getting the merge job kicked again. I'd like to shrink our review queue drastically this week.22:50
gabrielhurleyThere are 11 reviews that are approved but unmerged currently, and another 5-10 that need a second review. We can get 2/3 of what's open merged this week, easily.22:50
*** mikal has joined #openstack-meeting22:51
gabrielhurley#topic open discussion22:51
*** openstack changes topic to "open discussion (Meeting topic: horizon)"22:51
gabrielhurleyI think I've covered all of what I had. I just encourage everyone to keep diligent on the reviews22:51
gabrielhurleyWe've got ten minutes if anyone has any other topics they care about currently.22:52
lchengDoes anyone have an idea on this: https://answers.launchpad.net/horizon/+question/233742 ?22:52
*** mikal has quit IRC22:52
jpichlcheng: https://bugs.launchpad.net/horizon/+bug/1210253 has some debugging information22:52
*** vasiliy has quit IRC22:52
lchengI wonder if the  issue is on the debian packaging.22:52
uvirtbotLaunchpad bug 1210253 in horizon "With Havana 2 installed, Launching horizon UI results in the error " NameError: name 'Dashboard' is not defined"" [Undecided,Triaged]22:52
gabrielhurleyno clue, personally22:52
jpichand surfaced another bug with assert22:52
kspear_lcheng: circular import maybe?22:53
kspear_lcheng: (that's a wild guess)22:53
lchengjpich: thanks didn't notice there was updates on the ubg22:53
*** sandywalsh has joined #openstack-meeting22:53
david-lyleAre there plans to add an openstack-auth launchpad page?  Defects associated  with that repo don't seem to sync with gerrit.  Case in point https://review.openstack.org/#/c/42219/ isn't reflected in https://bugs.launchpad.net/horizon/+bug/1212748  or is there a way to get them to sync?22:54
uvirtbotLaunchpad bug 1212748 in horizon "log in for user with first project disabled fails" [High,Confirmed]22:54
lchengkspear: maybe, I'll try to dig around when I get the chance.22:54
*** nijaba has joined #openstack-meeting22:54
jpichI noticed something strange when setting Debug to False with Django 1.5.2 while trying to debug this, maybe someone can reproduce it and get a stack trace (nothing showed in the log, but the home page showed an error 500 page instead of the login screen, while it's fine with Django 1.4.5)22:54
*** ftcjeff has quit IRC22:55
*** markmcclain has joined #openstack-meeting22:55
*** michchap has joined #openstack-meeting22:55
gabrielhurleydavid-lyle: probably a good idea. could you email the ML or ping monty about that?22:55
*** wolfdreamer has quit IRC22:57
gabrielhurleywe're just about out of time here. any last minute items?22:58
absubram_when is our exact freeze date?22:58
lchengjpich:  If there is an error in the Auth middleware in django, it just fails silently. It might be the version of openstack_auth causing the issue. It requires at least 1.0.9 to run in django 1.5.22:58
absubram_Sept 4th or end of this week?22:58
jpichlcheng: Ah, good one. I'll try that in the morning! Thanks22:59
gabrielhurleyabsubram_: there's no *hard* feature freeze before the RC cut, but as it gets closer I use heavier discretion on the risk associated with the change.22:59
absubram_got it.. thanks :)22:59
gabrielhurleyokay, that's it folks!23:00
gabrielhurleythanks, and have a great week!23:00
lchengbtw, for the reviewers you need to add django_openstack_auth to your watched projects to get notifications.23:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:00
openstackMeeting ended Tue Aug 20 23:00:42 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-08-20-22.00.html23:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-08-20-22.00.txt23:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-08-20-22.00.log.html23:00
*** ozstacker has joined #openstack-meeting23:00
lblanchardthanks all!23:00
kspear_bye all23:01
lchengThanks, bye!23:01
*** lblanchard has quit IRC23:01
*** SumitNaiksatam has quit IRC23:01
*** kspear_ has quit IRC23:01
*** lblanchard has joined #openstack-meeting23:01
*** gabrielhurley has quit IRC23:02
*** jlucci has joined #openstack-meeting23:02
*** jpich has quit IRC23:03
*** otherwiseguy has quit IRC23:03
*** fnaval_ has quit IRC23:05
*** mrodden has quit IRC23:06
*** lblanchard has quit IRC23:07
*** radez is now known as radez_g0n323:10
*** Toshi has quit IRC23:13
*** markpeek has quit IRC23:13
*** esker has quit IRC23:14
*** SumitNaiksatam has joined #openstack-meeting23:23
*** patelna has quit IRC23:27
*** mrodden has joined #openstack-meeting23:28
*** changbl has joined #openstack-meeting23:29
*** Daisy has quit IRC23:30
*** HenryG has joined #openstack-meeting23:31
*** bdpayne has quit IRC23:37
*** bdpayne has joined #openstack-meeting23:42
*** fifieldt has joined #openstack-meeting23:51
*** topol has quit IRC23:52
*** absubram_ has quit IRC23:55
*** spzala has joined #openstack-meeting23:55
*** MarkAtwood has quit IRC23:55

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