Tuesday, 2013-01-22

*** mrodden has quit IRC00:02
*** annegentle has quit IRC00:02
*** koolhead17 has quit IRC00:04
*** nati_ueno has joined #openstack-meeting00:05
*** Nachi has quit IRC00:08
*** alexpilotti has quit IRC00:10
*** cdub has quit IRC00:13
*** cdub has joined #openstack-meeting00:14
*** jcmartin has joined #openstack-meeting00:15
*** sandywalsh_ has quit IRC00:18
*** dwcramer has quit IRC00:28
*** nati_ueno has quit IRC00:33
*** yamahata_ has joined #openstack-meeting00:37
*** mrodden has joined #openstack-meeting00:39
*** dwcramer has joined #openstack-meeting00:42
*** SumitNaiksatam has quit IRC00:59
*** yaguang has quit IRC01:02
*** gongysh has joined #openstack-meeting01:04
*** lbragstad has joined #openstack-meeting01:05
*** mrodden1 has joined #openstack-meeting01:08
*** mrodden has quit IRC01:11
*** mrodden1 has quit IRC01:14
*** mrodden has joined #openstack-meeting01:14
*** annegentle has joined #openstack-meeting01:15
*** martine has joined #openstack-meeting01:17
*** jcmartin has quit IRC01:19
*** mrodden1 has joined #openstack-meeting01:20
*** jcmartin has joined #openstack-meeting01:20
*** mrodden has quit IRC01:21
*** nati_ueno has joined #openstack-meeting01:22
*** nati_ueno has joined #openstack-meeting01:23
*** reed has joined #openstack-meeting01:25
*** sarob has joined #openstack-meeting01:25
*** sarob has quit IRC01:28
*** sarob has joined #openstack-meeting01:28
*** gongysh has quit IRC01:37
*** annegentle has quit IRC01:37
*** nati_ueno has quit IRC01:40
*** martine_ has joined #openstack-meeting01:41
*** lloydde has quit IRC01:43
*** martine has quit IRC01:44
*** vishy is now known as vishy_zz01:49
*** shang has joined #openstack-meeting01:49
*** MarkAtwood has joined #openstack-meeting01:51
*** rongze has quit IRC01:58
*** vishy_zz is now known as vishy01:59
*** zhuadl has joined #openstack-meeting02:03
*** novas0x2a|laptop has quit IRC02:05
*** vishy is now known as vishy_zz02:05
*** dprince has joined #openstack-meeting02:08
*** vishy_zz is now known as vishy02:08
*** galthaus_ has joined #openstack-meeting02:17
*** galthaus has quit IRC02:18
*** galthaus_ is now known as galthaus02:18
*** dripton_ has joined #openstack-meeting02:20
*** dripton has quit IRC02:20
*** mrodden has joined #openstack-meeting02:20
*** mrodden1 has quit IRC02:21
*** annegentle has joined #openstack-meeting02:21
*** Edward_Zhang has joined #openstack-meeting02:30
*** colinmcnamara has joined #openstack-meeting02:38
*** vishy is now known as vishy_zz02:46
*** morganfainberg has joined #openstack-meeting02:46
*** shang_ has joined #openstack-meeting02:50
*** colinmcnamara has quit IRC02:51
*** shang has quit IRC02:53
*** Youcef has quit IRC02:53
*** danwent_ has joined #openstack-meeting02:55
*** Mandell has quit IRC02:55
*** danwent has quit IRC02:56
*** danwent_ is now known as danwent02:56
*** shang_ has quit IRC02:58
*** shang has joined #openstack-meeting02:59
*** shang has quit IRC03:00
*** danwent_ has joined #openstack-meeting03:00
*** shang has joined #openstack-meeting03:01
*** shang has quit IRC03:03
*** shang has joined #openstack-meeting03:03
*** danwent has quit IRC03:03
*** danwent_ is now known as danwent03:03
*** bencherian has quit IRC03:04
*** vishy_zz is now known as vishy03:07
*** dprince has quit IRC03:12
*** _cerberus_ has quit IRC03:14
*** _cerberus_ has joined #openstack-meeting03:18
*** sarob has quit IRC03:19
*** ewindisch has joined #openstack-meeting03:24
*** nati_ueno has joined #openstack-meeting03:26
*** maurosr has quit IRC03:30
*** jacob1618 has joined #openstack-meeting03:41
jacob1618hi03:41
*** Gordonz has joined #openstack-meeting03:41
jacob1618Hi Gordonz03:42
*** jacob1618 has left #openstack-meeting03:48
*** stevebaker has quit IRC03:52
*** sarob has joined #openstack-meeting03:55
*** dolphm has quit IRC03:59
*** zhuadl has quit IRC04:12
*** Edward_Zhang has quit IRC04:13
*** sarob has quit IRC04:14
*** sarob has joined #openstack-meeting04:14
*** annegentle has quit IRC04:15
*** Gordonz has quit IRC04:15
*** martine_ has quit IRC04:17
*** koolhead17 has joined #openstack-meeting04:17
*** mrodden1 has joined #openstack-meeting04:21
*** nati_ueno has quit IRC04:22
*** mrodden has quit IRC04:23
*** Edward_Zhang has joined #openstack-meeting04:40
*** zhuadl has joined #openstack-meeting04:40
*** vishy is now known as vishy_zz04:41
*** blamar has joined #openstack-meeting04:47
*** blamar_ has joined #openstack-meeting04:48
*** adjohn has quit IRC04:49
*** stevebaker has joined #openstack-meeting04:51
*** blamar has quit IRC04:52
*** blamar_ is now known as blamar04:52
*** dosaboy has quit IRC04:57
*** ewindisch has quit IRC05:08
*** zhuadl_ has joined #openstack-meeting05:11
*** zhuadl has quit IRC05:14
*** zhuadl_ is now known as zhuadl05:14
*** davidkranz has quit IRC05:14
*** davidkranz has joined #openstack-meeting05:15
*** adjohn has joined #openstack-meeting05:18
*** galthaus has quit IRC05:20
*** dolphm has joined #openstack-meeting05:22
*** blamar has quit IRC05:24
*** ewindisch has joined #openstack-meeting05:25
*** brucer has joined #openstack-meeting05:44
*** jcmartin has quit IRC05:48
*** fifieldt has quit IRC05:48
*** koolhead17 has quit IRC05:49
*** EmilienM has quit IRC06:03
*** nati_ueno has joined #openstack-meeting06:06
*** morganfainberg has quit IRC06:17
*** cdub_ has joined #openstack-meeting06:28
*** dolphm has quit IRC06:36
*** afazekas has joined #openstack-meeting06:45
*** zhuadl has quit IRC06:50
*** Edward_Zhang has quit IRC06:50
*** tr3buchet has quit IRC06:54
*** tr3buchet has joined #openstack-meeting06:55
*** mrunge has joined #openstack-meeting06:59
*** Mandell has joined #openstack-meeting06:59
*** cdub_ has quit IRC07:09
*** adiantum has joined #openstack-meeting07:21
*** rongze has joined #openstack-meeting07:22
*** morganfainberg has joined #openstack-meeting07:23
*** afazekas has quit IRC07:23
*** adiantum has quit IRC07:29
*** garyk has quit IRC07:38
*** nati_ueno has quit IRC07:39
*** bencherian has joined #openstack-meeting07:40
*** FallenPegasus has joined #openstack-meeting07:40
*** MarkAtwood has quit IRC07:43
*** garyk has joined #openstack-meeting07:53
*** danwent has quit IRC07:56
*** afazekas has joined #openstack-meeting07:56
*** rafaduran has joined #openstack-meeting07:58
*** nati_ueno has joined #openstack-meeting08:10
*** EmilienM has joined #openstack-meeting08:11
*** henrynash has joined #openstack-meeting08:16
*** jhenner has joined #openstack-meeting08:16
*** afazekas has quit IRC08:28
*** Nachi has joined #openstack-meeting08:29
*** Nachi has quit IRC08:31
*** Nachi has joined #openstack-meeting08:32
*** nati_ueno has quit IRC08:32
*** afazekas has joined #openstack-meeting08:32
*** zhuadl has joined #openstack-meeting08:36
*** nati_ueno has joined #openstack-meeting08:36
*** Nachi has quit IRC08:39
*** Edward_Zhang has joined #openstack-meeting08:43
*** Mandell has quit IRC08:57
*** nati_ueno has quit IRC09:00
*** nati_ueno has joined #openstack-meeting09:01
*** derekh has joined #openstack-meeting09:05
*** afazekas has quit IRC09:11
*** nati_ueno has quit IRC09:20
*** nati_ueno has joined #openstack-meeting09:20
*** Nachi has joined #openstack-meeting09:24
*** darraghb has joined #openstack-meeting09:25
*** nati_ueno has quit IRC09:25
*** adjohn has quit IRC09:26
*** EmilienM has quit IRC09:27
*** EmilienM has joined #openstack-meeting09:29
*** brucer has quit IRC09:45
*** Nachi has quit IRC09:50
*** nati_ueno has joined #openstack-meeting09:50
*** almaisan-away is now known as al-maisan09:55
*** nati_ueno has quit IRC09:56
*** nati_ueno has joined #openstack-meeting09:56
*** nati_ueno has quit IRC10:01
*** flaper87 has joined #openstack-meeting10:17
*** psedlak has joined #openstack-meeting10:35
*** alexpilotti has joined #openstack-meeting10:42
*** afazekas has joined #openstack-meeting10:44
*** flaper87 has quit IRC10:45
*** fesp has joined #openstack-meeting10:45
*** vkmc has joined #openstack-meeting10:50
*** shang has quit IRC11:02
*** maurosr has joined #openstack-meeting11:03
*** Edward_Zhang has quit IRC11:07
*** zhuadl has quit IRC11:07
*** maurosr has quit IRC11:09
*** maurosr has joined #openstack-meeting11:09
*** yamahata__ has joined #openstack-meeting11:23
*** yamahata_ has quit IRC11:24
*** FallenPegasus has quit IRC11:45
*** amotoki has quit IRC11:49
*** bencherian has quit IRC11:58
*** henrynash has quit IRC12:02
*** martine_ has joined #openstack-meeting12:09
*** EmilienM has quit IRC12:11
*** rkukura has quit IRC12:12
*** brucer has joined #openstack-meeting12:19
*** asalkeld has quit IRC12:24
*** zhuadl has joined #openstack-meeting12:42
*** zhuadl_ has joined #openstack-meeting12:44
*** zhuadl has quit IRC12:47
*** Edward_Zhang has joined #openstack-meeting12:48
*** zhuadl_ has quit IRC12:50
*** zhuadl_ has joined #openstack-meeting12:52
*** zhuadl_ is now known as zhuadl12:53
*** henrynash has joined #openstack-meeting12:54
*** EmilienM has joined #openstack-meeting12:55
*** zhuadl has quit IRC12:57
*** galthaus has joined #openstack-meeting12:57
*** markvoelker has joined #openstack-meeting12:58
*** zhuadl has joined #openstack-meeting13:00
*** ijw has joined #openstack-meeting13:01
*** GheRivero is now known as GheRivero_afk13:02
*** zhuadl_ has joined #openstack-meeting13:04
*** galthaus has quit IRC13:04
*** zhuadl has quit IRC13:05
*** galthaus has joined #openstack-meeting13:06
*** zhuadl has joined #openstack-meeting13:06
*** zhuadl__ has joined #openstack-meeting13:09
*** zhuadl_ has quit IRC13:09
*** zhuadl has quit IRC13:11
*** zhuadl__ is now known as zhuadl13:11
*** zhuadl_ has joined #openstack-meeting13:13
*** zhuadl has quit IRC13:17
*** zhuadl has joined #openstack-meeting13:17
*** zhuadl_ has quit IRC13:17
*** sgordon has joined #openstack-meeting13:20
*** zhuadl has quit IRC13:22
*** zhuadl has joined #openstack-meeting13:22
*** zhuadl_ has joined #openstack-meeting13:25
*** markvoelker has quit IRC13:26
*** zhuadl has quit IRC13:27
*** galthaus has quit IRC13:28
*** davidkranz has quit IRC13:28
*** davidkranz has joined #openstack-meeting13:29
*** zhuadl has joined #openstack-meeting13:29
*** zhuadl_ has quit IRC13:30
*** zhuadl_ has joined #openstack-meeting13:31
*** dwcramer has quit IRC13:32
*** sgordon has quit IRC13:34
*** zhuadl has quit IRC13:34
*** zhuadl has joined #openstack-meeting13:35
*** zhuadl_ has quit IRC13:37
*** zhuadl has quit IRC13:40
*** zhuadl has joined #openstack-meeting13:42
*** zhuadl_ has joined #openstack-meeting13:43
*** zhuadl has quit IRC13:47
*** zhuadl_ has quit IRC13:50
*** zhuadl has joined #openstack-meeting13:51
*** zhuadl has quit IRC13:56
*** dprince has joined #openstack-meeting13:57
*** zhuadl has joined #openstack-meeting13:59
*** zhuadl_ has joined #openstack-meeting14:01
*** zhuadl has quit IRC14:04
*** zhuadl_ has quit IRC14:06
*** sandywalsh_ has joined #openstack-meeting14:06
*** sandywalsh has quit IRC14:06
*** ttrifonov_zZzz is now known as ttrifonov14:08
*** sandywalsh has joined #openstack-meeting14:15
*** sandywalsh_ has quit IRC14:16
*** GheRivero_afk is now known as GheRivero14:18
*** woodspa has joined #openstack-meeting14:20
*** ttx has quit IRC14:21
*** ttx` has joined #openstack-meeting14:21
*** zhuadl has joined #openstack-meeting14:24
*** dtroyer has quit IRC14:24
*** dtroyer_zzz has joined #openstack-meeting14:25
*** dtroyer_zzz is now known as dtroyer14:25
*** zhuadl_ has joined #openstack-meeting14:27
*** ttx` is now known as ttx14:27
*** ttx has quit IRC14:27
*** ttx has joined #openstack-meeting14:27
*** rkukura has joined #openstack-meeting14:28
*** zhuadl has quit IRC14:29
*** dwcramer has joined #openstack-meeting14:31
*** zhuadl_ has quit IRC14:32
*** BobBall has quit IRC14:34
*** BobBall has joined #openstack-meeting14:35
*** fnaval has quit IRC14:35
*** dolphm has joined #openstack-meeting14:37
*** BobBall has quit IRC14:38
*** zhuadl has joined #openstack-meeting14:38
*** zhuadl has quit IRC14:43
*** zhuadl has joined #openstack-meeting14:46
*** primeministerp has joined #openstack-meeting14:46
*** ayoung has quit IRC14:47
*** BobBall has joined #openstack-meeting14:48
*** yaguang has joined #openstack-meeting14:49
*** ayoung has joined #openstack-meeting14:52
*** dosaboy has joined #openstack-meeting14:53
*** zhuadl has quit IRC14:53
*** Gordonz has joined #openstack-meeting14:55
*** Edward_Zhang has quit IRC14:55
*** Gordonz has quit IRC14:55
*** dtalton has joined #openstack-meeting14:55
*** al-maisan is now known as almaisan-away14:55
*** Gordonz has joined #openstack-meeting14:56
*** fnaval has joined #openstack-meeting14:56
*** joesavak has joined #openstack-meeting14:57
*** cloudchimp has joined #openstack-meeting14:59
*** galthaus has joined #openstack-meeting15:03
*** markvan has joined #openstack-meeting15:03
*** vkmc has quit IRC15:06
*** garyTh has joined #openstack-meeting15:06
*** topol has joined #openstack-meeting15:06
*** markvan has quit IRC15:08
*** brucer has quit IRC15:09
*** vkmc has joined #openstack-meeting15:09
*** cp16net is now known as cp16net|away15:10
*** markmcclain has joined #openstack-meeting15:11
*** cp16net|away is now known as cp16net15:11
*** eharney has joined #openstack-meeting15:13
*** eharney has joined #openstack-meeting15:13
*** ryanpetrello has joined #openstack-meeting15:15
*** radez_g0n3 is now known as radez15:16
*** patrocinio has joined #openstack-meeting15:16
*** radez is now known as radez_g0n315:17
*** iben has joined #openstack-meeting15:18
ibenGood morning15:18
*** ttrifonov is now known as ttrifonov_zZzz15:19
*** iben has quit IRC15:20
*** dosaboy has quit IRC15:21
*** dosaboy has joined #openstack-meeting15:22
*** dolphm has quit IRC15:22
*** mtreinish has joined #openstack-meeting15:23
*** fesp has quit IRC15:24
*** fesp has joined #openstack-meeting15:26
*** radez_g0n3 is now known as radez15:26
*** dolphm_ has joined #openstack-meeting15:27
*** rnirmal has joined #openstack-meeting15:28
*** roaet is now known as roaet-away15:30
*** roaet-away is now known as roaet15:30
*** john5223 has joined #openstack-meeting15:31
*** glenc_ has joined #openstack-meeting15:37
*** ijw has quit IRC15:38
*** glenc has quit IRC15:39
*** lbragstad has quit IRC15:41
*** luis_fdez has joined #openstack-meeting15:51
*** pnavarro has joined #openstack-meeting15:53
*** cp16net is now known as cp16net|away15:54
*** jog0 has joined #openstack-meeting15:54
*** blamar has joined #openstack-meeting15:55
*** lbragstad has joined #openstack-meeting15:58
*** iben has joined #openstack-meeting15:58
primeministerp#startmeeting hyper-v15:59
openstackMeeting started Tue Jan 22 15:59:12 2013 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: hyper-v)"15:59
openstackThe meeting name has been set to 'hyper_v'15:59
primeministerphi everyone15:59
*** sandywalsh has quit IRC16:00
primeministerpalexpilotti: you around16:00
ibenpeter?16:00
primeministerppnavarro: you here?16:00
alexpilottihi guys!16:00
primeministerpiben: hi there16:00
pnavarrohi all16:00
*** AndChat|150689 has joined #openstack-meeting16:02
*** adjohn has joined #openstack-meeting16:02
pnavarroprimeministerp: I'm here16:02
*** sandywalsh has joined #openstack-meeting16:02
ibenis there an agenda?16:03
*** primeministerp has quit IRC16:05
ibenwoops - didn't mean to scare Peter away...16:05
*** cdub_ has joined #openstack-meeting16:05
*** primeminsterp has joined #openstack-meeting16:05
primeminsterpok16:05
primeminsterpi'm back16:05
ibenwelcome back!16:05
primeminsterpcrappy connection to day guys16:05
primeminsterpso16:05
primeminsterpiben meet alexpilotti16:05
primeminsterpalexpilotti: iben is going to be trying hyper-v shortly16:05
primeminsterplet's proceed w/ the meeting16:06
primeminsterp#topic RDP proxy16:06
*** markmcclain has quit IRC16:06
primeminsterpalexpilotti: do you have a status iben update on the rdp proxy?16:06
*** maoy has joined #openstack-meeting16:06
alexpilottiworking on it16:06
primeminsterpalexpilotti: heheh16:07
*** blamar_ has joined #openstack-meeting16:07
primeminsterpalexpilotti: will we have testable code any time soon?16:07
alexpilottimoved to the 1.1 FreeRDP codebase16:07
alexpilottinot before G3 :-)16:07
primeminsterpthat's ok16:07
primeminsterpwe'll move on then16:07
alexpilottithe gateway will be available for testing sooner16:07
primeminsterp#topic nova refactor16:07
*** markmcclain has joined #openstack-meeting16:08
alexpilottithis one is almost done16:08
alexpilottiI finally got rid of all the dragons and design issues on the original cloud.com code16:08
alexpilottiall the WMI code has been moved to separate classes, that can be finally be mocked16:09
alexpilottipnavarro volunteered for helping with testing all this work16:09
*** blamar has quit IRC16:09
*** blamar_ is now known as blamar16:09
alexpilottitransition to V2 APIs will be also easier now16:09
alexpilottias we'll have to work on a very delimited area16:09
*** primeministerp has joined #openstack-meeting16:10
primeministerpback again16:10
primeministerpwow bad connection16:10
primeministerpok16:10
alexpilottiI'm very glad that this is almost over. We were building a skyscraper on top of very shaky foundations ;-)16:10
primeministerpso no more cloud.com code16:11
primeministerpyes16:11
primeministerpthis is awesome16:11
primeministerpactually16:11
alexpilottiyes, finally16:11
primeministerpwhen do you expect to start commiting the changes upstream?16:11
alexpilottithis week for sure16:11
primeministerpawesome16:11
alexpilottiI'm going to start testing the code today16:11
primeministerpgreat news16:11
alexpilottiI expect a lot of minor fixes, due to the big amount of work involved16:11
*** primeminsterp has quit IRC16:12
primeministerpi would imagine16:12
primeministerpi guess i just quit16:12
primeministerphehe16:12
*** iben has quit IRC16:12
primeministerpok, moving on then16:12
alexpilottiprimeministerp: ?16:12
primeministerpis there something you need?16:12
primeministerp#topic quantum16:14
alexpilottiprimeministerp: I was wondering about your comment :-)16:14
*** hanrahat has joined #openstack-meeting16:14
alexpilottiQuantum plugin is very alive and well :-)16:14
primeministerpthere was an alert in my irc16:14
primeministerpthat I quit the session16:14
primeministerpalexpilotti: good16:14
alexpilottiWe added the agent to our installer as well16:14
primeministerpalexpilotti: I had to poke redmond folks last night for the msdn bits btw16:14
primeministerpalexpilotti: great16:14
primeministerpalexpilotti: good news16:14
*** openstack changes topic to "quantum (Meeting topic: hyper-v)"16:14
alexpilottiwork on NVGRE is going on, although a bit slowly16:14
primeministerpalexpilotti: ok16:14
primeministerpalexpilotti: good to know16:14
alexpilottidur to the priority on Nova refactoring / resize16:14
primeministerpi wasn't sure if it had progressed16:15
primeministerpok16:15
alexpilottiI spoke w pnavarro lately about L3 details16:15
primeministerppnavarro: any comments?16:15
alexpilottiand with goongysh16:15
pnavarronothing to add16:15
alexpilottigoongysh is our quantum core mantainer for the plugin at the moment16:15
alexpilottiI sent him the Powershell scripts to show how it works16:15
alexpilottihe's very helpful as usual16:16
primeministerpok16:16
primeministerpgood to know16:16
primeministerpthen the msdn acct was very important16:16
alexpilottidefinitely16:16
primeministerpok16:16
alexpilottiprimeministerp: do you think we can start offering MSDN on the dev list to any core reviewer that can help in testing the Hyper-V code?16:16
alexpilottiI mean, in Nova, Quantum, Cinder...16:17
hanrahatalexpilotti: yes, we can make the licenses available to the core developers16:17
alexpilottihanrahat: thanks Tom16:17
*** ewindisch has quit IRC16:17
alexpilottithis is the best solution to have them getting out of their "Linux isolation"16:18
alexpilottiand starting work with us, which ultimately will lead to a better Hyper-V community inside of OpenStack16:18
hanrahatalexpilotti: same process as with goongsyh... it takes a little time but trust me we have the process down to as fast as possible here.16:18
alexpilottiand most important, more attention to interoperability16:19
alexpilottihanrahat: I was actually impressed16:19
alexpilottihanrahat: thanks a lot for your effort16:19
*** lloydde has joined #openstack-meeting16:19
alexpilottiI know how much it took the first time I got one as MVP, so I know how complicated it can be16:19
hanrahat:-)16:19
alexpilottiprimeministerp: still online? :-)16:20
*** primeministerp has quit IRC16:20
AndChat|150689Hetr16:21
alexpilottilooks like we lost him :-)16:21
*** primeministerp has joined #openstack-meeting16:21
primeministerpback again16:22
primeministerpsorry16:22
primeministerpabout that16:22
alexpilottiprimeministerp: it's ok16:22
primeministerpalexpilotti: ok let's get though this16:22
primeministerpso16:22
primeministerpyes16:22
primeministerpanyone who wants to test16:22
primeministerpcan reach out to me16:22
primeministerpand I will do facilitate them getting a msdn acct16:22
alexpilotticool. Do you think it's possible to send an email to the dev ML?16:22
primeministerper -do16:22
primeministerpI just cannot promise that it's quickly16:22
alexpilotti:-)16:23
alexpilottiprimeministerp: ping :-)16:23
*** iben has joined #openstack-meeting16:23
alexpilottilooks like primeministerp has some serious connectivity issues today16:24
ibenHey guys - I have a question about this - why do we need msdn when hyper-v is free? Just asking… what other components are we testing here?16:24
*** afazekas has quit IRC16:24
primeministerpi'm here16:24
primeministerpjust typing16:24
alexpilottihi iben good question16:24
primeministerpiben: you technically don16:24
alexpilottiiben: Hyper-V server is free16:24
primeministerpt16:25
primeministerpit's a good will gesture16:25
alexpilottiiben: but you need a domain controller for testing live migration for example16:25
alexpilottiiben: also teh full WIndows Server has GUI tools that people like to use during development16:25
pnavarroalexpilotti: btw, with SMB 3.0 it will be possible to have a domain controller 100% open source ?16:25
ibenBTW - I have MSDN as do the other team members I'm working with but an overview of the current setup and next steps for a lab for testing would be helpful.  If a write up on this doesn't exist I'd like to volunteer to help document it16:25
*** yamahata__ has quit IRC16:25
alexpilottiiben: we do 99% of the development on the free Hyper-V16:26
ibenand the actual openstack environment is the typical linux platform?16:26
primeministerpiben: yes16:26
alexpilottiiben: we have a free installer he: http://www.cloudbase.it/installing-openstack-nova-compute-on-hyper-v/16:26
ibenIn Other words - and existing openstack or devstack users could test this16:26
primeministerpiben: yes16:26
alexpilottiiben: with all the step by step documentation16:26
ibenokay - I will review16:27
primeministerpiben: you just point hyper-v at it16:27
primeministerpiben: and make sure you have a vhd16:27
primeministerpto deploy on hyper-v16:27
primeministerpiben: you can also tweak your scheduler to place vm's properly16:27
*** yamahata__ has joined #openstack-meeting16:27
ibenok - I would like more details on that too16:27
primeministerpalexpilotti: is that documented yet?16:28
alexpilottiiben: we hare also ready mand VHDs for ubuntu 12.04, so contact me if you need a link16:28
primeministerpalexpilotti: the scheduler bits?16:28
primeministerpok then16:28
alexpilottiprimeministerp: it's simply a glance property16:28
primeministerpalexpilotti: yes16:28
primeministerpalexpilotti: ok moving on16:28
primeministerp#topic ci infrastructure16:28
alexpilottiprimeministerp: iben here you go: http://www.cloudbase.it/filtering-glance-images-for-hyper-v/16:28
*** openstack changes topic to "ci infrastructure (Meeting topic: hyper-v)"16:28
*** psedlak has quit IRC16:29
ibenthe main issue right now (hope to hear about this later) is the way to automate Windows VM provisioning including hostname and IP address assignment. Since typically openstack uses images - how do we inject this info?16:29
primeministerpalexpilotti: thx16:29
primeministerpiben: ->16:29
alexpilottiiben: http://www.cloudbase.it/cloud-init-for-windows-instances/16:29
primeministerpiben: do you have windows provisioning already in place?16:29
ibenyes - most customers are using SCCM for this with a PXE boot setup16:29
ibenthere's a way to also use USB image16:29
primeministerpiben:then you can still use that16:30
ibenokay - this is something I'd like to document as well16:30
primeministerpiben: from a iron and making your master images perspective16:30
primeministerpiben: perfect16:30
primeministerpiben: I created the original docs16:30
ibencan we add it to a list and get a few people to work with me on it?16:30
primeministerpiben: i.e. in the admin guide16:30
*** galthaus_ has joined #openstack-meeting16:30
primeministerpiben: definately16:30
primeministerpEmilienM: ping16:31
ibenintegration of sccm and openstack16:31
EmilienMprimeministerp: pong16:31
primeministerpo16:31
primeministerpone sec16:31
primeministerpiben: I won't be using sccm16:31
primeministerpiben: so I won't be able to help16:31
*** dosaboy has quit IRC16:31
primeministerpw/ sccm specific bits16:31
primeministerpiben: however if it's related to core openstack stuff16:32
ibenright - I'd like to work with someone at MS or the OPenstack community on this16:32
primeministerpplease feel free to pubdate the other bits16:32
primeministerpiben: that needs to be a discussion16:32
ibenunderstood16:32
primeministerpiben: w/ the sccm folks16:32
ibenok16:32
ibenlet's move on - I don't want to take over teh meeting16:32
primeministerpiben: i believe we have a talk tomorrow16:32
primeministerpiben: let's start that discussion there16:32
hanrahatprimeministerp: i can help make the connection to the sccm team16:32
primeministerpiben: and drive it inside msft16:33
primeministerpjust want to make sure we're clear16:33
ibensure16:33
*** hemna has joined #openstack-meeting16:33
pnavarroI have to guys, alexpilotti ping me as soos as you have something me to start testing16:33
alexpilottipnavarro: sure, tx!16:33
*** galthaus has quit IRC16:33
*** galthaus_ is now known as galthaus16:33
*** lloydde has quit IRC16:34
*** dosaboy has joined #openstack-meeting16:35
alexpilottiprimeministerp: should we move on to cloud-init?16:35
*** primeminsterp has joined #openstack-meeting16:35
primeminsterpok16:36
primeminsterpback again16:36
primeminsterpsorry about that16:36
primeminsterpjust some updates on the ci16:36
primeminsterpso this is a key link in the chain16:36
primeminsterpI finally go the puppet reg working properly on the back side of the preseed16:36
primeminsterpociuhandu: any movement on the quantum automation?16:37
primeminsterpociuhandu: also I didn't get to look at the cert creation bits yet16:37
primeminsterpociuhandu: i'll try to look at those tonight16:37
*** primeministerp has quit IRC16:37
ociuhanduprimeminsterp: quantum templates will be ready today16:37
primeminsterpociuhandu: great16:37
*** pnavarro has quit IRC16:37
ociuhanduprimeminsterp: the install part is already in place16:37
primeminsterpociuhandu: I'm going to try to test the other bits today out of registration16:38
primeminsterpociuhandu: great16:38
ociuhanduI hope that by tomorrow or the day after, the latest, I wil move to the network controller16:38
primeminsterpociuhandu: also I'll work on finalizing the windows provising16:38
primeminsterpociuhandu: awesome16:38
primeminsterpociuhandu: let's touch base tomorrow16:38
primeminsterpociuhandu: then16:38
ociuhanduprimeminsterp: sure16:38
primeminsterp#topic hyper-v chef16:39
primeminsterpso talking about chef modules today w/ Matt Ray from opscode16:39
primeminsterpwe'll see if we can make any progress16:40
ibenmodules = cookbooks?16:40
ibenor actual ruby code bits?16:40
*** luis_fdez has quit IRC16:44
*** koolhead17 has joined #openstack-meeting16:44
*** primeminsterp has quit IRC16:44
*** primeministerp has joined #openstack-meeting16:46
primeministerpok16:47
primeministerpreally shaky connection16:47
primeministerpclosing the meeting16:47
primeministerpsorry guys16:47
primeministerp#endmeeting16:47
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:47
openstackMeeting ended Tue Jan 22 16:47:22 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-01-22-15.59.html16:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-01-22-15.59.txt16:47
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-01-22-15.59.log.html16:47
*** mrodden1 has quit IRC16:53
*** gyee has joined #openstack-meeting16:54
*** ewindisch has joined #openstack-meeting16:55
ibenhi Eric16:55
ibeni think the meeting's over...16:55
*** bdpayne has joined #openstack-meeting16:55
*** rkukura has left #openstack-meeting16:56
*** EmilienM has quit IRC16:59
*** ijw has joined #openstack-meeting17:00
*** otherwiseguy has joined #openstack-meeting17:01
*** bdpayne has quit IRC17:02
*** bdpayne has joined #openstack-meeting17:03
*** cdub_ has quit IRC17:03
*** annegentle has joined #openstack-meeting17:05
*** primeministerp has quit IRC17:06
*** mrodden has joined #openstack-meeting17:09
*** patrocinio has left #openstack-meeting17:10
*** shengjie_min has quit IRC17:11
*** lloydde has joined #openstack-meeting17:11
*** bobba_ has joined #openstack-meeting17:12
*** jcmartin has joined #openstack-meeting17:16
*** vkmc has quit IRC17:19
*** yamahata__ has quit IRC17:20
*** afazekas has joined #openstack-meeting17:21
*** bobba_ has quit IRC17:22
*** juice_ has joined #openstack-meeting17:23
*** cody-somerville has joined #openstack-meeting17:23
*** psedlak has joined #openstack-meeting17:25
*** diogogmt has joined #openstack-meeting17:27
*** danwent has joined #openstack-meeting17:27
*** jpich has joined #openstack-meeting17:28
*** vishy_zz is now known as vishy17:32
*** bencherian has joined #openstack-meeting17:35
*** metral has joined #openstack-meeting17:37
*** derekh has quit IRC17:39
*** ccorrigan has joined #openstack-meeting17:41
*** rafaduran has quit IRC17:44
*** kaganos has joined #openstack-meeting17:46
*** AndChat|150689 has quit IRC17:48
*** dosaboy has quit IRC17:50
*** danwent has quit IRC17:50
*** danwent has joined #openstack-meeting17:51
*** sarob has quit IRC17:51
*** kwss has joined #openstack-meeting17:52
*** danwent has quit IRC17:53
*** yamahata__ has joined #openstack-meeting17:55
*** ijw has quit IRC17:55
*** stevemar has joined #openstack-meeting17:57
*** dosaboy has joined #openstack-meeting17:57
*** ijw has joined #openstack-meeting17:58
*** ijw has quit IRC17:59
ayoungKey...Key...Keystone Ho!18:00
dolphm_no heckj again?18:00
kwsshello18:00
ayoungdolphm_, heckj doesn't live here anymore18:00
gyee\o18:00
dolphm_:(18:00
topolayoung: I committed a WIP for devstack silent install and configure of LDAP for you to take a look at.  https://review.openstack.org/#/c/20249/18:00
henrynashhi18:00
*** dosaboy has quit IRC18:00
*** AlanClark has joined #openstack-meeting18:00
*** dosaboy1 has joined #openstack-meeting18:00
gyeewhat happen to heckj?18:00
*** nachi has joined #openstack-meeting18:00
*** nachi__ has joined #openstack-meeting18:00
ayoungtopol, kewl18:00
dolphm_he's been on the list, but not on irc18:00
*** brich1 has joined #openstack-meeting18:00
dolphm_#startmeeting keystone18:00
openstackMeeting started Tue Jan 22 18:00:53 2013 UTC.  The chair is dolphm_. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
openstackThe meeting name has been set to 'keystone'18:00
dolphm_#topic High priority bugs or immediate issues?18:01
*** openstack changes topic to "High priority bugs or immediate issues? (Meeting topic: keystone)"18:01
ayoungdolphm_, High priority18:01
*** dwchadwick has joined #openstack-meeting18:01
dolphm_we have several security fixes in the works -- if you have visibility, please review the proposed patches18:01
ayoungno V3 API for tokens18:01
gyeeI need a decision on the auth plugin18:01
dolphm_gyee: do you have code to put up for review?18:02
gyeenot yeah18:02
dolphm_gyee: i think that's going to be the fastest route to solicit solid feedback18:02
gyeeI can finish off the tokens work and leave the auth plugin later18:02
ayoung+118:02
henrynash+118:02
gyeealrighty then18:02
dolphm_gyee: sure18:02
ayounggyee, +2 Frost damage!18:02
dolphm_lol18:02
dolphm_any other high priority things?18:03
dolphm_#action gyee to put v3 auth interface up for review, without pluggability18:03
*** markvoelker has joined #openstack-meeting18:03
dolphm_#action core to review proposed security patches18:04
dolphm_ (^^keep commentary within the bugs for now, please^^)18:04
dolphm_i'll take silence as a no...18:05
dolphm_#topic Default domain and v3 calls where domain_id is not specified18:05
*** openstack changes topic to "Default domain and v3 calls where domain_id is not specified (Meeting topic: keystone)"18:05
henrynashdolphm: will do18:05
dolphm_#link http://lists.openstack.org/pipermail/openstack-dev/2013-January/004691.html18:06
henrynashdolphm: So I made the suggestion to separate the discussion on creation of a default domain from the actions we take on v3 calls18:06
*** Mandell has joined #openstack-meeting18:06
dolphm_henrynash: worthy point18:07
gyeewe can only scope to one domain at a time so specifying a domain ID in create user is irrelevant right?18:07
gyeeunless it is the global ADMIN user18:08
henrynashdolphm: since that re-orders/names the migration files….would be good to get that in asap….the I can layer my changes in18:08
dolphm_gyee: yes, but if multi-tenant tokens merge, we'll also end up with multi-domain tokens18:08
dolphm_gyee: however, i don't think it's going to happen18:08
dwchadwickWhy cannot the keystone admin create multiple users in multiple domains in a single session without needing to swap between domains18:08
dolphm_henrynash: +118:08
*** vkmc has joined #openstack-meeting18:09
ayoungdwchadwick, explicitly, then should be able to do so.  It is justin the implicit case it is  an issue18:09
*** EmilienM has joined #openstack-meeting18:09
henrynashayoung: I notice your suggestion on the loading of different easy of doing this….we could clearly do that…I just wander if it is worth it…since we are only talking about the case when a v3 caller decides NOT to specify a domin18:10
dwchadwickIf it is a multi-domain set up, then you can either mandate explicit domains or default to the domain the admin is currently associated with18:10
henrynash(...different ways of doing this…)18:10
ayounghenrynash, It still doesn't solve the hard question of what should the default behavior be.18:11
ayounghenrynash, but it mitigates the cases where people disagree18:11
dwchadwickRather than having 10 ways of skinning a cat, why not have just one way18:11
dolphm_i'd really rather not have if-then-elseif logic handling this in the core implementation18:11
dwchadwickmeaning that the domain must be specified in a multi-domain system18:12
gyeedolphm_, I am OK with token scoped to multiple domains18:12
dwchadwickIts explicit, its not confusing or ambiguous18:12
henrynashdolphm: I kind of agree….if the operators don't like the default, then they can specify the domain anyway in the call..18:12
gyeebut not multiple projects as it has severe impacts right now18:12
dolphm_i don't really want anything more complicated than, e.g.: create_user_request.setdefault('domain_id', token['domain']['id'])18:13
*** morganfainberg has quit IRC18:13
dolphm_gyee: i don't want to accept multi-project tokens without multi-domain tokens -- they should be merged hand-in-hand (if they hand)18:15
dolphm_lol (if the merge*)18:15
gyeefair enough18:16
dolphm_anyone opposed to my pseudo code above? it corresponds with what me and henrynash were "violently agreeing" on in the mailing list thread18:16
* gyee is comfortably numb18:16
ayoungayoung is comfortably dumb18:17
topoldolphm_ : dare I say it looked good to me!18:17
topol18:17
henrynashayoung: I think you were probably the most keen on giving the options….do you still think it is necessary18:17
ayoungdolphm_, sounds about right...can we post to the larger community as a "here is what we are going to do.   I know you are all going to complain, but we are going to do it anyway, as we have determined all of the other options were more horrible."18:18
*** AlanClark has quit IRC18:18
dolphm_ayoung: i feel like that's what we just did on openstack-dev18:18
ayounghenrynash, if we can agree on a reasonable default, the options can be an ace in the sleeve we keep for later18:18
henrynashayoung: +118:18
ayoungdolphm_, I had trouble following the discussion, I'm sure most people tuned it out18:18
dolphm_ayoung: +118:18
gyeeso A) then?18:19
dolphm_#action utilize domain-scoped authorization to imply owning domain_id on create user & project requests18:19
dolphm_moving on..?18:19
* ayoung hears his cue18:19
dolphm_#topic Tenant to Project, Roles versus Membership, and Trusts18:20
*** openstack changes topic to "Tenant to Project, Roles versus Membership, and Trusts (Meeting topic: keystone)"18:20
*** cp16net|away is now known as cp16net18:20
ayoungOK./..18:20
ayoungso, you might remember I was kindof keen on trusts for a while18:20
*** yamahata__ has quit IRC18:20
ayoungand then it turns out trusts needs tokens to get a full test18:20
ayoungand tokens need roles18:20
ayoungand roles and membership are conflicting concepts18:21
ayoungto be specific18:21
ayoungmember ship old and borkne18:21
dwchadwickWhat is the membership concept18:21
ayoungroles--new hotness18:21
*** AlanClark has joined #openstack-meeting18:21
ayoungdwchadwick, tenants had members18:21
dolphm_dwchadwick: a horrible legacy implementation detail we're trying to get rid of18:21
ayoungdwchadwick, you can pretty much assume that explanation for most of the work we are doing, actually18:21
ayoungso...metadata18:22
ayounganother horrible choice of terms we need to expurgate18:22
dwchadwickAt what point in time do you delete code of deprecated features18:22
dolphm_'membership' is basically treated as an implied role assignment internally, we'd like to make it an explicit role grant that can be managed through the api18:22
dwchadwickYou cannot carry deprecated baggage for ever or you will end up like Windows18:22
dolphm_it came as a result of importing legacy auth data from nova18:23
ayoungdwchadwick, that is an important enough question that I don't want to give a glib answer now18:23
ayoungcan we table it for now?18:23
*** metral_ has joined #openstack-meeting18:23
ayoungthe short is, we will deprecate18:23
dwchadwickok18:23
dolphm_dwchadwick: this isn't so much a user-facing feature; but the answer is 2 release cycles18:23
ayoungfrom an API perspective, we are going to implement user tenant membership via the role entity but keep the APIs...for now18:23
ayoungthis is a V23 thing primarily18:24
ayoungV2 has this stuff,  3 not so much18:24
ayoungAs I go through the code, though I see parallels in domains and groups18:24
ayoungand I want to make sure I have it straight18:24
ayoungdomains should have membership, as domains own the user records18:25
dolphm_ayoung: no! user.domaid_id defines that ownership18:25
henrynashayoung: true to the last bit, but why do we need membership18:25
*** metral has quit IRC18:25
*** yamahata__ has joined #openstack-meeting18:25
*** metral_ is now known as metral18:25
ayoungdolphm_, ah...so I think I can cut out some more code18:26
*** vkmc has quit IRC18:26
dolphm_ayoung: the more you delete the faster i'll +218:26
ayoungthere should be no grants on domains then, right?18:26
dolphm_ayoung: nono, that stays18:26
ayoungdomain relationships are fixed18:26
dolphm_ayoung: thats in the v3 spec18:26
ayoungwhat is a user/domain grant if it is not defined by a role?18:26
dolphm_ayoung: it is18:27
henrynashayoung: grant role x to group Y on domain Z18:27
henrynashayoung: all three elements must be specified18:27
dwchadwickthis is getting to be a mess18:27
dolphm_https://github.com/openstack/identity-api/blob/master/openstack-identity-api/src/markdown/identity-api-v3.md#grant-role-to-user-on-domain-put-domainsdomain_idusersuser_idrolesrole_id18:27
ayoungdwchadwick, agreed, that is why I am trying to remove...18:27
*** vkmc has joined #openstack-meeting18:27
henrynashayoung: I don't follow at all…..18:28
dolphm_ayoung: this should have zero api impact18:28
ayoungdolphm_, right18:28
ayoungthis is implementation18:28
dolphm_ayoung: not even on v318:28
ayoungOK...let me back up18:28
*** jgriffit1 has joined #openstack-meeting18:29
ayoungmetadata:  it is a denormalized blob18:29
ayoungthis pattern is in groups, tenants, domains18:29
ayoungthere are grants for18:29
*** otherwiseguy has quit IRC18:30
ayoungUserProjectGrant UserDomainGrant GroupProjectGrant and GroupDomainGrant18:30
henrynashayoung: yes, and the meta data in each table just has the roles in it, e.g.:18:30
henrynashclass UserDomainGrant(sql.ModelBase, BaseGrant):18:30
henrynash    __tablename__ = 'user_domain_metadata'18:30
henrynash    user_id = sql.Column(sql.String(64), primary_key=True)18:30
henrynash    domain_id = sql.Column(sql.String(64), primary_key=True)18:30
henrynash    data = sql.Column(sql.JsonBlob())18:30
ayoungdenormalized data for things that should have integrity constrains in the DB is a bad approach18:30
dolphm_ayoung: data -> role_id18:30
ayoungdolphm_, that is where I am headed18:30
dolphm_multiple roles could be in data though18:31
ayoungcan we drop the data/extra columns for all of these?18:31
ayoungdolphm_, bad18:31
dolphm_ayoung: yes18:31
ayoungroles are foreign keys18:31
dolphm_ayoung: they should be, yes18:31
ayoungwe looks referential integrity if we do multiple keys in one field18:31
henrynashayoung: why don't we just at a role_id column (in place of the data) and then that is the foreign key18:31
*** jgriffith has quit IRC18:31
henrynashayoung: that was the plan....18:32
ayounghenrynash, sure, that is OK, so long as we are ok with getting rid of the data column18:32
gyee+118:32
dolphm_+118:32
ayoungwe have this nasty tendency to do serialied JSON blobs that we really should not do18:32
henrynash+118:32
dolphm_ayoung: this is not the membership issue though..?18:33
henrynashayoungL so I did commit as part of the groups work to do that normalization18:33
ayoungdolphm_, well, for users to proejcts, membership is replaced by roles18:33
ayoungfor domains, membership is specified by the domain id18:33
gyeesounds 'bout right18:33
dolphm_user_tenant_membership and user_tenant_metadata need to both be migrated to user_project_grants18:34
ayoungdolphm_, yep..I'm working on that18:34
dolphm_ayoung: awesome18:34
ayoungthe code that calls them is common to those as well as domain and group grants:18:34
dolphm_ayoung: let me know if you need help there18:34
ayounglink coming...18:34
dwchadwickI dont suppose there is any chance you can change the name grants to assigns is there?18:34
dolphm_dwchadwick: implementation or api?18:35
ayounghttps://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L24218:35
dwchadwickGrants sounds like you are granting a privilege, whereas in reality you are assigning role membership or similar18:35
dwchadwickthe granting of acces is done by the service via its policy engine18:35
ayoungand the corresponding creates all have logic18:35
dwchadwickAPI primarily, but the implementation ought to match the API18:36
dolphm_dwchadwick: propose the corresponding api changes, they're only superficial there18:36
dwchadwickOK, I am currently reviewing the APIv3 anyway18:36
ayounghttps://github.com/openstack/keystone/blob/master/keystone/identity/backends/sql.py#L55018:37
ayoungso these all assume that the roles are a denormalized list18:37
dolphm_dwchadwick: make it a separate patch though (smaller patches are easier to review and faster to merge with fewer conflicts)18:37
ayoungfor a group/domain grant,18:38
dwchadwickyes my changes wont be anything to do with Kristy's mapping changes18:38
ayoungwhere we are saying group_id gets roles in domain_id18:38
*** jgriffith has joined #openstack-meeting18:38
ayoungthere is no need for membership....OK I think the only thing that was unclear than I needed to get straight was domain18:39
ayounggroups should have membership...right?18:39
gyeeyes18:39
ayoungusers are either a member of a group or they are not...they do not have "roles" in a group.18:39
henrynashayoung: correct18:40
ayounginstead they get roles assigned by being a member of a group....18:40
henrynashayoung: yes18:40
*** donaldngo has joined #openstack-meeting18:40
dwchadwickusers are also members of a role as well18:40
dolphm_ayoung: Grant role to user on domain: PUT /domains/{domain_id}/users/{user_id}/roles/{role_id}18:40
dolphm_ayoung: Grant role to group on domain: PUT /domains/{domain_id}/groups/{group_id}/roles/{role_id}18:40
dwchadwickassign role to user please18:40
henrynashdwchadwick: there is no such call….you must specify a target18:41
*** jgriffit1 has quit IRC18:41
dolphm_dwchadwick: i'm quoting the current spec18:41
ayoungso..users have roles in domains....18:41
dwchadwickI was merely asking that you replace Grant by Assign18:41
dolphm_ayoung: yes, that's what henrynash is working on18:41
ayounghmmmm...that seems superfluous18:41
dolphm_domain role grant, domain-scoped tokens, domain-authz operations in keystone (create user, create project)18:42
ayoungseems like it would be cleaner to keep roles in group assignements18:42
ayoungdolphm_, this is implementation,18:42
dolphm_ayoung: users and groups can both be granted roles in both projects and domains18:42
henrynashayoung: yes…and to be complete a user maybe be able to operate on a domain/project either due to a direct grant or via grant on a group of which they are a member18:42
dolphm_henrynash: +118:42
dolphm_ayoung: this is api18:42
ayoungok..bear with me for  a moment18:43
henrynashdwchadwick; (just using grant since this is current terminology)18:43
topolhenrynash: +118:43
dwchadwickunderstood18:43
ayoungdwchadwick, you understand?  Good...someday you can explain it to me.18:44
ayoungOK...18:44
* gyee is working on understanding Keystone book18:44
dwchadwickexcellent idea18:44
ayoungso domain membership is done via the user object, we don't need a collection there...so the only collection that domain maintains is via role grants18:44
dwchadwickbook should have been written before the code18:44
dolphm_ayoung: this needs to go away http://paste.openstack.org/raw/29722/18:44
dwchadwickthen the code would have been much simpler ;-)18:45
ayoungdolphm_, done this morning in my local repo18:45
henrynashayoung: +218:45
dolphm_ayoung: post for review and we'll take it from there?18:45
ayoungdolphm_, not so simple18:45
ayoungthere are a lot of changes implicit with that18:45
ayoungmigration etc18:45
dolphm_ayoung: yep18:45
dolphm_legacy import rewrite18:46
dolphm_schema migration, data migration18:46
ayoungand I'm still flushing out errors....18:46
dolphm_driver calls that need to be killed18:46
*** metral has quit IRC18:46
ayoung"I've got my country's 500th anniversary to plan, my wedding to arrange, my wife to murder and Guilder to frame for it; I'm swamped. "18:46
dolphm_ayoung: post something WIP so we can make sure everyone is on the same page18:46
*** metral has joined #openstack-meeting18:46
ayoungdolphm_, will do, as soon as I can get even the sql unit tests to run to completion18:47
dolphm_ayoung: i never had time to get that far when i tackled it :(18:47
dolphm_#topic v3/auth18:47
*** openstack changes topic to "v3/auth (Meeting topic: keystone)"18:47
dolphm_gyee: we obviously already talked about this...18:48
*** psedlak has quit IRC18:48
dolphm_gyee: comfortable to land in g-m3?18:48
gyeeyou mean auth plugin?18:48
dolphm_gyee: i think we're just talking about auth on the v3 api in general18:48
gyeewell, v3/auth still result in token issuance18:48
*** AlanClark has quit IRC18:48
dolphm_gyee: using the current spec18:48
henrynashdolphm: maybe we covered this a bit already….I just wanted us to get the v3/auth early since I need to add to itf for domain name spaces18:48
gyeeso v3/tokens seem ok to me18:48
dolphm_henrynash: +118:49
dolphm_gyee: want me to propose the spec changes to move from /v3/tokens -> /v3/auth?18:49
dolphm_happy to help however i can18:49
gyeeg-m3 cut-off is 2/21 right?18:49
dolphm_gyee: yes18:49
*** yaguang has quit IRC18:50
gyeewhy change to v3/auth?18:50
*** gatuus has joined #openstack-meeting18:50
gyeeI am OK with v3/tokens since auth will result in token creation anyway18:50
dolphm_gyee: (mailing list discussion) /tokens is not a collection, it's a noun e.g. /authentication /authorization18:50
dwchadwickand what does auth mean? authn or authz?18:50
dolphm_dwchadwick: intentionally ambiguous since the same api handled both in one call if you need that efficiency18:51
dwchadwickok18:51
gyeedolphm_, go ahead, same amount of code anyway18:51
dolphm_dwchadwick: or you can break it into two steps against the same API (request authentication and then request authorization)18:51
ayoungdwchadwick, I proposed an url scheme /auth/n and /auth/z but was told I was being a smarty pants18:51
dolphm_gyee: yep18:52
gyeethanks18:52
dwchadwick But I thought the service made the authz decision via its policy engine18:52
*** metral_ has joined #openstack-meeting18:52
dolphm_#action dolph to revise v3 API from /v3/tokens -> /v3/auth18:52
dwchadwickAre you proposing that Keystone will run an authz server?18:52
ayoungdwchadwick, to a degree18:52
dolphm_dwchadwick: only that it provides an interface to an authz implementation, which may be a remote server18:52
ayoungdwchadwick, but tenant tokens, where are authN stuff, are provdied by keystone, and keystone can decide not to issue one18:53
dwchadwickWell I like the smarty pants API :-) with the /n and /z18:53
dolphm_ /v3/authentication and /v3/authorization would make the REST fans happy18:54
gyeemy fingers won't be happy18:54
dwchadwickits is also much clearer to the user18:54
dwchadwickbut /v3/authz and /v3/authn are also clear and easier on the fingers18:55
gyeedamn straight!18:55
ayoungdwchadwick, so...there is token issuing and token validation18:55
ayoungwe don't want token  IDs in the URL18:55
dwchadwickYes we have that in our design18:55
ayoungas that is Identified as a security risk18:55
dwchadwickwhy a security risk? is this due to them being bearer tokens?18:56
ayoungthe token is really the signed set of attributesd for the user, so the union of authz and authn data18:56
dwchadwickyou can solve that by holder of key18:56
ayoungdwchadwick, yes18:56
*** metral has quit IRC18:56
*** metral_ is now known as metral18:56
ayoungdwchadwick, and then we need a full SSL handshake18:56
ayoungand then we have reimplemented X50918:56
ayoungwhich we should be using in the first place18:56
gyeeSSL won't protect URL18:56
ayoungor Kerberos18:56
ayoung gyee it wouldn't need to18:57
ayoungif the tokens were not vulnerable to a relay attack18:57
dolphm_dwchadwick: requested URLs are frequently logged, obtaining such a log would provide access with any still-valid tokens18:57
dwchadwickyes replay attacks18:57
ayoungdwchadwick, here is the deal18:58
ayoungthere are lots of secure technologies18:58
dolphm_gyee: +118:58
ayoungwe can't use them because of the webserver that openstack chose18:58
ayoungit is really that simple18:58
ayoungand really that frustrating18:58
dolphm_gyee: getting it out of the URL and then wrapping the connection in SSL makes it sound pretty safe to me18:58
*** markmcclain has quit IRC18:58
ayoungand we have 2 minutes left in our meeting18:58
dolphm_#topic open discussion18:58
*** openstack changes topic to "open discussion (Meeting topic: keystone)"18:58
gyeedolphm_ +218:58
dolphm_anything else in hte last 20 seconds?18:59
dwchadwickI must go now. Bye for now18:59
dolphm_dwchadwick: /wave18:59
dolphm_#endmeeting19:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:00
openstackMeeting ended Tue Jan 22 19:00:01 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-01-22-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-22-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-22-18.00.log.html19:00
*** olaph has joined #openstack-meeting19:00
henrynashdolphm: so you'll push in you default domain creation change?19:00
dolphm_henrynash: push in?19:00
jeblairci/infra ppl?19:00
henrynashdolphm: switch to dev19:01
fungiohai19:01
*** jsavak has joined #openstack-meeting19:01
*** kwss has quit IRC19:02
*** joesavak has quit IRC19:02
jeblairmordred, clarkb: ping19:02
clarkbo/19:02
olapho/19:02
mordredo/19:03
pleia2o/19:03
*** sdake has joined #openstack-meeting19:03
jeblair#startmeeting infra19:03
openstackMeeting started Tue Jan 22 19:03:08 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
*** openstack changes topic to " (Meeting topic: infra)"19:03
openstackThe meeting name has been set to 'infra'19:03
jeblair#topic agenda19:03
*** openstack changes topic to "agenda (Meeting topic: infra)"19:03
*** khaido has joined #openstack-meeting19:03
jeblair#link http://wiki.openstack.org/Meetings/InfraTeamMeeting19:03
jeblairI like, updated the agenda and stuff.19:03
fungioh!19:03
*** dwchadwick has quit IRC19:03
fungii had stopped looking at it19:03
jeblairanyone, everyone, feel free to update that at any time19:03
*** sarob has joined #openstack-meeting19:03
mordreddude19:04
clarkbwoah19:04
jeblairsince i think of things throughout the week, it's nice to have a place to put it. and we can stop doing the "does anyone have an agenda" thing.  which is just way too exciting.19:04
pleia2great19:05
*** dolphm_ has left #openstack-meeting19:05
* mordred is in favor of our new agenda wiki overlords19:05
jeblair#link last meeting: http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-01-15-19.04.html19:05
jeblairthe wiki/calendar are updated (thanks ttx)19:05
jeblairand the rest we'll get to with the wiki (which i want to save for last when ttx will hopefully be here)19:06
jeblair#topic CLA19:06
*** openstack changes topic to "CLA (Meeting topic: infra)"19:06
*** markmcclain has joined #openstack-meeting19:06
*** dosaboy1 has quit IRC19:06
fungiyeah19:06
fungie-mailed toddmorey about getting the updated appsec key to him, so see if he wanted to do that by phone or what19:07
fungireview-dev will no longer break when he changes that19:07
mordredneat19:07
fungistill poking at doc updates as i get time19:07
fungii think we're probably clear to send the announcement though?19:07
jeblairfungi: i gave him a heads up about that on a phone call this morning19:07
fungii've updated the announcement proposed text with the date we agreed upon19:08
jeblairfungi: http://wiki.openstack.org/Project_Group_Management  is dead link?19:08
*** morganfainberg has joined #openstack-meeting19:08
fungijeblair: and should be until we're doing project management in gerrit i think?19:08
jeblairfungi: oh, it's in the annourcement19:08
fungidouble-checking, but thought the announcement said it would appear there once we cut over19:09
fungirevisiting19:09
jeblairfungi: yeah it does19:09
jeblairfungi: how about we make that page exist with the docs, but put a "not implemented" banner at the top19:09
fungididn't want to publish documentation about a process which won't work yet, though i guess i could just slap a big disclaimer on it in that case19:09
* mordred is in favor of our new CLA overlords19:09
fungiyeh, that19:09
fungiwill do19:10
jeblairfungi: cool, then i think it's ready to go.19:10
fungineed to write that up, but i'll send the announcement as soon as that wiki page exists then19:10
*** nachi__ has quit IRC19:10
*** nachi_ has quit IRC19:10
*** nachi has quit IRC19:10
jeblairfungi: cool, by end of week reasonable?19:10
fungiabsolutely reasonable19:10
jeblair#action fungi make http://wiki.openstack.org/Project_Group_Management exist19:10
jeblair#action fungi send CLA announcement19:11
mordredso - for my out-of-touch brain - does that mean we're cutting prod over to new CLA by end of week?19:11
fungiha19:11
mordredor putting up docs and announcement for future cutover19:11
fungimordred: february 2419:11
mordredk. thanks19:11
jeblairmordred: it's right after g319:11
mordredoh right. I remember that now. I'm going to put it on my calendar19:11
jeblairanything else about cla?19:12
fungii figure this week is good for announcing, since it gives everyone a one-month warning19:12
*** jdurgin has joined #openstack-meeting19:12
jeblairfungi: +119:12
fungithat's all there is from me on that19:12
jeblair#topic rechecks19:12
*** openstack changes topic to "rechecks (Meeting topic: infra)"19:12
jeblairSo recheckwatch is in production...19:12
mordredI'd like to quote markmc:19:12
clarkband people are using it :)19:12
mordred"You know what? This is just awesome."19:12
jeblairlooks like it has data:19:12
jeblair#link http://status.openstack.org/rechecks/19:13
mordredfeature request - how do things get off the list?19:13
jeblairso the next/final step is to disable the old syntax.  should we do that now?19:13
jeblairmordred: they age out after a month.  they fall down the list as they become less relevant.19:13
mordredk19:14
*** psedlak has joined #openstack-meeting19:14
fungii'm good with enforcing19:14
jeblairmordred: we could give them additional demerits if the bug is closed (fix committed/released)19:14
jeblairmordred: (to move them down the page faster, but probably not remove them)19:15
fungialso worth noting, we've gotten an influx of ci bugs, many of which seem to relate to people being encouraged to document their rechecks/reverifies19:15
jeblairmordred: (still want to find them easily if the bug is erroneously marked closed)19:15
mordredfungi: ++19:15
jeblairfungi: yeah, i think we should retarget those to whatever projects seem the most relevant19:15
jeblairie, https://bugs.launchpad.net/openstack-ci/+bug/110114219:15
uvirtbotLaunchpad bug 1101142 in openstack-ci "Euca tests failure, cannot ping server with floating ip" [Undecided,New]19:15
jeblairshould probably be targeted to nova and devstack19:16
fungiagreed. none of them were terribly clear to me on first glance, except one i thought was almost certainly nova19:16
fungithe devstack ones are always going to be fuzzy, but maybe the devstack bug peeps can make with more refining once they get them19:16
jeblairwe should probably try to be fairly quick about that too, so that the devs get the benefit of the bugs.19:17
mordred++19:17
fungiagreed19:17
mordredgeneralized bug triage on the openstack-ci project is something I fall down at alot19:17
mordredbut I think that I have email filters that are too broad19:17
jeblairso should we go ahead and require the new syntax?19:17
jeblairor extend the burn-in period?19:18
*** ryanpetrello has quit IRC19:18
clarkbI think we can go ahead and turn it on19:18
*** ryanpetrello has joined #openstack-meeting19:18
clarkbpeople seem to understand how it works, and it hasn't had major problems outside the thing jgriffith pointed out19:19
jeblair#action jeblair update recheck regex to require bug19:19
fungiand discussion about it has more or less died down on the ml with no real detractors19:19
jeblairclarkb: yeah, i'm running that in screen now with the fix in place to catch any further errors.  i should also add proper logging to it.19:19
jeblair#action jeblair add logging to recheckwatch19:20
jeblair#topic jenkins slave operating systems19:20
*** openstack changes topic to "jenkins slave operating systems (Meeting topic: infra)"19:20
jeblairwe should upgrade our precise slaves to quantal, in accordance with the support policy19:20
mordred++19:20
mordredalso, our cloud providers have quantal now19:21
mordredheads up - I believe there is somethign up with running devstack on quantal ...19:21
*** alexpilotti has quit IRC19:21
jeblairawesome.19:21
mordreddevananda: any chance you know what that is? ^^19:21
clarkbquantal uses biosname for interfaces19:21
mordredthat's it19:21
mordreddevananda: nevermind19:21
clarkband that appeared to cause some problems with devstack networking19:22
* devananda reads scrollback anyway19:22
clarkbs/interfaces/network interfaces/19:22
mordredyeah. so eth0 is now em0 or something right?19:22
clarkbcorrect19:22
jeblairis there a devstack fix?19:22
jeblairso i think we need to:19:23
jeblair0) update puppet with a node descriptor for quantal19:23
devanandathere was an issue with node.js on quantal too: https://bugs.launchpad.net/horizon/+bug/107008319:23
uvirtbotLaunchpad bug 1070083 in devstack "devstack fails in quantal - /usr/bin/env node - no such file or directory" [Undecided,Fix released]19:23
jeblair1) launch a long-running quantal slave node19:23
jeblair2) add it to jenkins19:23
fungipresumably node needs to be invoked as nodejs on quantal?19:23
fungidevananda: ^?19:23
mordredjeblair: yah. that way we can try adding some non-voting jobs first19:24
jeblair3) try manually running some unit test jobs on it for various projects19:24
fungioh, already fixed i guess19:24
jeblairmordred: or that19:24
mordredjeblair: are you just talking about unittest nodes now? or devstack nodes too?19:24
jeblair4) move projects or duplicate as non-voting jobs to the quantal slaves19:24
jeblairjust unit test19:24
mordredk.19:24
jeblair5) add it to the devstack-gate pool19:24
jeblair6) try out devstack on it19:25
jeblair[end of rough overview]19:25
mordred++19:25
clarkbsounds about right to me19:25
fungiseems sane19:25
jeblairanyone want to start working down that list?19:25
*** vipul is now known as vipul|away19:25
* mordred is about to get 20 hours of plane flights, so it's probably not me19:25
jeblairi have similar availability19:26
fungii can start trying it once i wrap up the oneiric/quantal puppet cleanup stuff19:26
clarkbI am hoping to do more logstash related hacking, but if I get stalled on that I can probably spin up a quantal node and get the process going19:26
clarkbs/what I said/I can assist fungi/ :)19:26
pleia2fungi: let me know if there is anything I can do to help19:26
fungipleia2: i was about to suggest you might want to be involved too19:27
jeblair#action fungi start quantal upgrade with help from pleia2 and clarkb19:27
jeblairand me too, just at weird hours.  :)19:27
jeblairdavidkranz: ping19:27
jeblair#topic tempest gating19:27
*** openstack changes topic to "tempest gating (Meeting topic: infra)"19:27
jeblairso great news is we're gating on quantum19:28
jeblairand the tempest folks are really making headway on getting tempest ready for more intensive gating19:28
jeblair(and we're all really excited about testr too!)19:28
*** vipul|away is now known as vipul19:29
jeblairdavidkranz: sent me this link this morning:19:29
jeblair#link https://etherpad.openstack.org/turn-on-tempest-gate19:29
jeblairwhich i believe describes an optimization of the gate where we can avoid running some tests for some projects19:29
*** annegentle has quit IRC19:30
jeblairthat sounds nice, though i'm a little concerned about whether that means we'll miss problems due to unforseen interactions...19:30
clarkbwhich could cause the gate to grind to a halt19:31
jeblairfrom a high level pov, it's also an imbalanced gate, where integrated projects run different code.19:31
jeblairthe current "tempest runs full" configuration is a form of that.  obviously, this is _designed_ to be better than that19:31
jeblairbecause it's supposed to only test related code19:31
jeblairbut where reality doesn't match the design, we could see a problem.19:32
*** psedlak has quit IRC19:32
*** fesp is now known as flaper8719:32
jeblairclarkb: exactly.19:32
mordredso, just in general, when it says  "It is too expensive to run complete functional tests for every project on a commit to any project. So19:33
*** novas0x2a|laptop has joined #openstack-meeting19:33
mordredthe following is proposed.19:33
mordred"19:33
mordredI'd love to see what parallelization gets us before we start doing partial tests19:33
mordredbut, in general the matrix in that doesn't look ridiculous19:34
*** jcmartin has quit IRC19:34
fungiwell, parallelization trades expensive time for expensive space (ram, cpu), so it depends on what expensive means there19:35
jeblairyeah.  also, we could do something like the xml/json split in the interim before testr.19:35
*** FallenPegasus has joined #openstack-meeting19:35
jeblairfungi: indeed.  and we don't know our budget.  :)19:35
fungiat least for time, there is a fixed budget. no more than 26 hours a day ;)19:36
jeblairheh19:36
fungi(or was that letters in the alphabet?)19:36
mordredyeah. I've been under the working assumption so far that dev time is the more precious and that our illustrious cloud providers haven't been unhappy with our current usage19:37
*** gyee has quit IRC19:37
jeblairmordred: yep.  and you know i'm happy to increase our usage -- i only want to make sure people understand the exponential function.19:37
mordredjeblair: ++19:37
*** jog0 has quit IRC19:37
jeblairmordred: so maybe let's start an email thread with some tempest folks, and work out a med-long range plan?19:38
mordredjeblair: ++19:38
jeblair#action jeblair start email thread for tempest gate long range planning19:38
jeblair#topic wiki migration19:39
*** openstack changes topic to "wiki migration (Meeting topic: infra)"19:39
mordredjeblair: although I will say that the theory of running relevant tests is a nice one19:39
*** cdub_ has joined #openstack-meeting19:39
mikaljeblair: can you do me a favour?19:39
mikalmordred: you too?19:39
*** darraghb has quit IRC19:39
olaphso, logo/links should be acceptable for v1 of the skin19:39
mikalI just sent you guys an email with a PDF attachment. Can you verify the attachment opens and renders ok, and looks correct for me?19:39
jeblairmikal: sure.  this is a meeting, btw.  :)19:40
mikalOh bugger. Sorry. Wrong channel.19:40
jeblairmikal: it's okay, we'll put you on the agenda for next time.  :)19:40
mikalYay19:40
jeblairolaph: cool, updated link?19:40
clarkbI think ttx is still having trouble with image uploads19:41
olaphsame one:19:41
olaph#link http://openstack-wiki-instance.instance-proxy.wmflabs.org/wiki/Main_Page19:41
clarkbI have no css for that (it must be pulling it from behind the firewall19:42
jeblairolaph: that lgtm (the only thing that really stands out is the mediawiki footer19:43
olaphjeblair: should it disappear, or just be openstackish?19:44
clarkbsilly caches, loads fine in chrome19:44
jeblairolaph: probably just have blue lines instead of orange.19:44
jeblairor grey lines.  or something.19:44
*** Ryan_Lane has joined #openstack-meeting19:44
ttxo/19:45
mordredlook. it's ttx19:45
ttxand Ryan19:45
jeblairRyan_Lane: your redirects patch is merged, right?19:45
Ryan_Laneyep19:46
jeblairRyan_Lane: is that taken care of?19:46
Ryan_Laneit is19:46
Ryan_Laneit'll work when we switch the domain name19:46
ttxyeah, my only standing issue is the inability to upload images19:46
ttxor rather, that uploaded images return 404 when served19:46
*** yamahata__ has quit IRC19:46
Ryan_Lanettx: that's also fixed19:46
ttxThe main page is looking good enough, need image upload to make them look same19:46
ttxRyan_Lane: recently ?19:47
Ryan_LaneI emailed the list in response to you ;)19:47
Ryan_Lanethe same day19:47
ttxI tried like 8 hours ago19:47
Ryan_Lanecrap19:47
ttxsee my own answer to list :P19:47
Ryan_Lanewell, maybe my change was wrong19:47
Ryan_LaneI tested this before making the change and it worked19:48
Ryan_LaneI'll fix that now19:48
jeblairannegentle is not here.  :(19:48
ttxMain page relooked @ https://wiki-staging.openstack.org/wiki/Main_Page19:48
ttxwaiting for the theme to do the last relooking steps19:49
jeblairttx: lgtm (modulo images/css)19:49
ttxRyan_Lane: can we have __NOTITLE__ ?19:49
Ryan_Lanehm. there's some way of handling this, I think19:50
ttxnot a big fan of the "Main page" title on that main page, maybe that's just me19:50
ttxhttp://www.mediawiki.org/wiki/Extension:NoTitle19:50
Ryan_Laneoh19:50
Ryan_Lanefor sure on the main page we can turn that off with css19:50
Ryan_Lanesee wikipedia, as an example19:50
Ryan_Laneugh. I'm dumb. I put the aliases in the wrong order19:51
* mordred points finger at Ryan_Lane and laughs mockingly19:51
* mordred apologizes19:51
clarkb>_> I reviewed that change <_<19:51
ttxRyan_Lane: would that be part of olaph theme ? or do I need to do anything ?19:51
Ryan_Laneyou can modify mediawiki's css through mediawiki19:52
Ryan_LaneI can handle that19:52
ttxI tried {{DISPLAYTITLE:<span style="display:none">{{FULLPAGENAME}}</span>}} but it left a blank space19:52
Ryan_Lanethat's one way of doing it19:52
Ryan_Lanethat can be added anywhere in the page, including the bottom19:52
Ryan_Laneand can be included in a template19:52
ttxbody.page-Main_Page h1.firstHeading { display:none; } in Common.css19:52
ttx(following http://www.mediawiki.org/wiki/Manual:FAQ#How_do_I_hide_the_main_page_title.3F)19:53
Ryan_Laneyep19:53
ttxif I can modify it, will do if nobody beats me to it19:53
Ryan_Lanecool19:53
olapheither way...19:53
jeblairif i read annegentle's email right, she was suggested we schedule the move _after_ the cla change on feb 24...19:53
jeblairis that what other people got out of that?19:54
ttxjeblair: no, my understanding was BEFORE19:54
*** alexpilotti has joined #openstack-meeting19:54
Ryan_Lanehttps://review.openstack.org/20268 <— fixes images19:55
ttxWe just need to avoid concurrency, and I don't see the point in waiting19:55
fungii'm cool either way. it's not like the wiki updates i'm staging will be hard to tweak the markup on19:55
jeblairttx: yeah, i was thinking earlier too.  i just thought her email said "after cla work is complete"19:55
*** jsavak has quit IRC19:55
* ttx checks19:56
clarkbI am ahppy with earlier as well. I think the wiki change is something that if it breaks we can work through it fairly easily19:56
Ryan_Laneif the only changes in the skin are CSS, we may consider just adding it to MediaWiki:Common.css19:56
Ryan_Laneor MediaWiki:<skin>.css19:56
ttxI'd rather do atht early because end of Feb I'll get busy grizzlying19:56
clarkb++19:56
jeblairsince we also need to schedule a wiki update sprint, perhaps we should take the scheduling discussion to email to include anne...?19:57
olaphRyan_Lane: will do19:57
Ryan_Laneolaph: thanks19:57
*** gabrielhurley has joined #openstack-meeting19:58
clarkbjeblair: good idea19:58
jeblairthat, and we're out of time...19:58
*** jd__ has left #openstack-meeting19:58
*** jd__ has joined #openstack-meeting19:58
jeblair#action jeblair start wiki migration scheduling email thread19:59
jeblairthanks all!19:59
jeblair#endmeeting19:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:59
mordredthanks!19:59
openstackMeeting ended Tue Jan 22 19:59:16 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-01-22-19.03.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-01-22-19.03.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-01-22-19.03.log.html19:59
* Ryan_Lane waves19:59
*** Ryan_Lane has left #openstack-meeting19:59
notmynamehere19:59
*** yaguang has joined #openstack-meeting20:00
ttxo/20:01
ttxWho is around for the TC meeting ?20:01
notmynameo/20:01
*** danwent has joined #openstack-meeting20:01
bcwaldonhello!20:01
ttxThat's 4 of us20:02
*** markmc has joined #openstack-meeting20:02
ttx520:02
markmchey20:02
mordredo/20:02
ttxone more...20:02
russellbhey20:02
ttxyay20:02
danwento/20:02
*** bearovercloud has joined #openstack-meeting20:03
ttxjaypipes, vishy, gabrielhurley: you can join any time20:03
* ttx is missing someone20:03
vishyo/20:03
ttx#startmeeting tc20:03
openstackMeeting started Tue Jan 22 20:03:40 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
jaypipesttrifonov_zZzz: o/20:03
jaypipescrap.20:03
*** zykes- has quit IRC20:03
jaypipeso/20:03
ttxAgenda for today is:20:03
ttx#link http://wiki.openstack.org/Governance/TechnicalCommittee20:04
*** joesavak has joined #openstack-meeting20:04
ttx(heckj, annegentle not on channel...) oh, jgriffith.20:04
ttx#topic Discussion: Voting procedure to decide the H release name20:04
*** openstack changes topic to "Discussion: Voting procedure to decide the H release name (Meeting topic: tc)"20:04
ttxSuper important20:04
ttxThe most lightweight and relatively-painful-to-hack method remains to use Launchpad polls as we did in the past20:04
ttxThe main issue with Launchpad polls are that they are single-choice20:05
*** mikal has quit IRC20:05
ttxwhich doesn't work so well when there are 35 options.20:05
ttxSo to reduce that problem my suggestion would be that the TC comes up with a shortlist of 4 names20:05
ttxthen using single-choice polling is not so much of a problem.20:05
*** markvoelker1 has joined #openstack-meeting20:05
ttxIf you agree with that, I can quickly setup a Condorcet vote for the TC20:05
ttxso that we efficiently pick the 4 best options out of http://wiki.openstack.org/ReleaseNaming20:05
ttxThoughts ?20:05
notmynamewhy not a codorcet vote globally?20:05
danwentnotmyname: my question as well, but i'm guessing ttx has a reason :)20:06
ttxnotmyname: two reasons... we would change who gets to vote compared to previous polls...20:06
ttxand we would have to send emails, while I don't want people to feel like they are constantly asked to participate in elections20:06
*** mikal has joined #openstack-meeting20:07
mordredwell, we're going to have to ask them to participate in electoins whether it's 4 choices or 3520:07
ttxhence the lightweight "polling" on the ~openstack LP group announced via various low-touch social media20:07
markmc4 seems just a little low, might take some of the fun out of it20:07
*** hanrahat has quit IRC20:07
mordredI do not support low-touch social media announcement only20:07
*** markvoelker has quit IRC20:07
ttxmordred: not really. We'll annoucne the vote on the ML, not send them all personal emails20:07
russellbHalfway, lol ...20:07
russellbthe Halfway release ...20:07
danwenti don't see either of the two reasons for not using codorcet are that critical.  what is the difference in the set of people who would vote?20:08
mordredok. well, honestly, I'd rather get a vote email than a mail to ~openstack mailing list, which I regularly ignore20:08
ttxdanwent: we'd have to pick between technical contributors or foundation members20:08
mordred(I'll know about the election from being in here, but I'm imagining I'm not the only person)20:08
*** zykes- has joined #openstack-meeting20:08
notmynamemordred: +1 (most people I know filter the ML pretty heavily too)20:08
mordredis this a board or a TC call?20:08
ttxalso IT'S NOT VERY IMPORTANT :)20:09
mordredbecause if it's a TC call, then the vote comes from the Tech contribs quite clearly, since they are our constituents20:09
markmcttx, *nod*20:09
mordredif it's a board call, then the vote needs to come from the foudation membership20:09
*** jsavak has joined #openstack-meeting20:09
mordredttx: I think you might underestimate how much people care about the name20:09
ttxI don't really want to get caught in setting up a 6K voters condorcet20:09
markmcwas grizzly what was voted for last time?20:10
*** iben has quit IRC20:10
mordredyes20:10
* markmc recalls something about going with something different from the vote20:10
bcwaldonthe Waldon exception20:10
markmcmy mistake20:10
russellbthere had to be an exception to get grizzly to be a valid choice20:10
markmcah20:10
russellbit was campaigned for, heh20:10
vishyHamlet, Harbor, Homestead, Hood20:10
ttxanyway, I'm fine with all condorcet, but then someone else shoudl volunteer to irganize it20:10
mordredvishy: ++20:10
vishythere are the four choices. done.20:10
vishy:)20:10
mordredif we go with 4, I support vishy's four20:11
ttxmordred: TC-level condorect is easy to set up, I've it ready to go20:11
mordredttx: then why don't we just do that?20:11
mordredOR - just do your original suggestion with vishy's four :)20:11
* mordred is being useful and agreeing with everyone20:11
*** sandywalsh has quit IRC20:12
ttxmordred: do what ? A 13-viters condorcet to pick the 4 other people will vote on ?20:12
ttxvoters*20:12
mordredoh20:12
ttxor something else ?20:12
mordredI thought you meant you had an ATC condorcet set up already20:12
ttxmordred: well, not really20:12
ttxit's a tad more difficult to set up20:12
*** joesavak has quit IRC20:12
ttxgiven the numbers of people involved20:13
mordredok. well, I don't have time to set it up either ... so I think that's an excellent point20:13
ttxI bet non contributors would bitch about not being able to say something20:13
danwentHatfield: http://en.wikipedia.org/wiki/Hatfield-McCoy_feud20:13
mordredsomeone is always going to bitch20:13
ttxmordred: not if you don't change the system20:13
mordredttx: someone is ALWAYS going to bitch20:14
ttxand continue to use the same system... just select the set of possible answers20:14
mordreds/Harbor/Hatfield/20:14
ttx(which we did the other times as well)20:14
mordredharbor will ellicit silly spelling issues from our harbour-spelling uk friends20:14
bcwaldonI can just suggest something arbitrary again, if that helps20:14
ttxSo to ask it differently, are you OK with what I propose or are you going to run the election yourself ?20:14
mordredbcwaldon: I've already suggested the waldon-exception invoking choice for this cycle20:14
markmcheh, nice20:14
ttxI'm fine either way20:14
russellbHarbor, *because* it will elicit silly spelling issues20:14
mordredrussellb: hehe20:15
mordredbcwaldon: hood isn't technically a town, there's a mount hood, a hood river and it's (barely) on the flag20:15
mordredbcwaldon: but it's a really big mountain, and it's 4 letters, so - you know20:15
russellbHood it is20:16
* russellb really just doesn't care on this topic ...20:16
mordredhehehe20:16
mordredttx: I think russelb just suggested that we decide by fiat and just tell people :)20:16
bcwaldondone20:16
russellbdone and done20:16
ttxok, CIVS sent :P20:17
ttxthen we can decide if we poll people on first 4, or just pick ourselves20:17
ttxWe can get back to it at the end of the meeting, time permitting20:17
ttx#topic Discussion: Evolution of the TC membership to support potential growth20:18
*** openstack changes topic to "Discussion: Evolution of the TC membership to support potential growth (Meeting topic: tc)"20:18
ttxWe started that discussion at the last meeting two weeks ago.20:18
ttxSince then I started a ML thread detailing options at:20:18
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-January/004513.html20:18
ttxSo far the general feedback is that people prefer option (3), but could accept (4) if that's where consensus was20:18
ttx(potentially with a 7 guaranteed PTLs instead of 8)20:18
ttxThey generally prefer (3) because (4) adds complexity in election setup for no obvious gain.20:18
* jaypipes could go either way20:19
ttxAnne hinted that she would prefer some per-theme representation but that option is still very much on the drawing board20:19
notmynamewith the outlier proposal from anne about categories20:19
ttxWe need to make a decision quick as it affects the upcoming elections we have to start setting up20:19
ttxSo if there is opposition to option (3), I'd like to hear it (especially on the thread)20:19
ttxAnd if people prefer detailed alternate options, they should add them to the thread as well.20:19
ttxOtherwise I'll just draft a motion based on (3) for us to vote on at next meeting.20:19
ttxComments ?20:20
mordredI second a motion based on (3)20:20
markmcthirded20:20
* markmc checks what (3) was :)20:20
markmcyeah, that one20:20
mordredwith a poison pill added that if that results in absolute chaos, a unanimous decisions by all standing PTLs can trigger a re-election  :)20:20
ttxI'm all for (3), just thought (4) would be where lazy consensus would lie20:20
* mordred is kidding - just do 320:21
notmynameI think 3 was the least-bad of the options given, but I prefer the category approach20:21
mordredI think at some point we should explore the idea of project categories in general20:21
ttxnotmyname: I'm fine with exploring the category approach further, but for the Fall election20:21
mordredbut I think we might need some beer at the summit to really sort that one out20:21
ttxsince I think it will take time to come up with something good, balanced and practical to organize20:22
ttxs/take time/be near impossible/20:22
vishyhave we discussed any kind of limitation about people serving on both the board and the tc?20:22
ttxvishy: we haven't, you think we should ?20:22
danwentI am concerned that small projects will not get good respresentation, but worry that categories won't be flexible enough as the set of projects evolve.  I still like the idea of having PTLs elect a set of PTLs to represent all PTLs on the board.  That way, several small projects could decide on one person that will represent them all.20:23
danwentBUT, i don't have the cycles to push this, so am up for going with 3 as the other least bad :)20:23
ttxdanwent: you shouldn't think of it as representation for everyone, but more about electing wise people that care about everything openstack20:23
notmynamedanwent: sounds like a consensus government20:23
ttxand provide a variety of opinions20:23
russellbis anyone against #3?20:24
notmynamettx: that's true no matter what method is chosen. you always want to have good people. the trick is making sure you have a system that handles when you don't have a good person20:24
danwentttx: its really more about awareness to me…. its not that the wise people aren't wise, its just hard to know everything that's happening in all of the projects, no matter how wise you are :)20:24
russellbseems like general agreement on 3 being the best/least bad20:24
danwentI guess a PTL can always show up and plead their case, as long as they keep an eye on the agendas and understand their potential impact on their project.20:25
markmcdanwent, notmyname - this stuff would make for really good discussion on the list20:25
markmcI thought that was the idea with starting a thread on the list20:25
markmcgive people a chance to consider each others in-depth opinions a bit more20:26
ttxyeah, I was suprised to see almost direct consensus20:26
ttxok, so I fucked up the CIVS thing, let me retry that20:26
markmcI guess the question is whether more discussion on list will change the consensus on what to do in the short term?20:28
markmcallow the discussion to be more about the best thing to do for future elections?20:28
notmynamewhy does something need to change in the short term? the proposed changes are to protect against future problems20:29
markmcthat's a fair point indeed20:29
russellbwell, we have 2 projects in incubation, i guess that's the pressing issue?20:30
russellbwhat happens if they are brought into the coordinated release20:30
ttxrussellb: yes20:30
notmynamedoes that push us over some tipping point?20:30
russellbheh20:30
markmcoh, if they graduated, they'd be automatically granted seats20:30
ttx15 is a pretty big board20:30
markmcwhich could happen at the start of the H cycle20:30
ttxright, the idea is to pick a mechanism for next elections before that becomes a problem20:31
ttxOK, poll sent ok this time20:31
russellbyour poll email is in French20:32
notmynameso 13 members today (and with the 4 proposed options) is ok, but 15 members for the next 6 months (until fall elections) is too much?20:32
jaypipesttx: lol, poll in French :)20:32
russellbI do not speak your jibberish!20:32
ttxARRh, not that again20:32
ttxstupid sticky language support20:32
ttxI can redo it in english20:32
* russellb was just trolling20:33
* ttx is about to delegate that fun thing20:33
russellbi could google translate if necessary :)20:33
markmcnotmyname, would we aim to reduce back to 13 again in future ?20:33
ttxCIVS creates the poll with the language set in the browser you use to create it, which is rather lame20:33
* markmc thinks 15 is getting too big20:33
ttxI think 13 is already big, personally20:34
*** dwcramer has quit IRC20:34
ttxbut I can live with that20:34
notmynamemarkmc: if that's the decision we come to20:34
ttxI also don't want the dilution to affect people's decision on accepting new projects20:34
mordred++20:35
ttxi.e. people rejecting projects because a 15-people board would be too much in their opinion20:35
ttxwe should accept on technical grounds20:35
ttxnot because our current membership setup makes it a problem20:35
mordredor reject20:35
mordredyah20:35
ttxso the only way would be to fix the membership BEFORE we discuss those20:36
ttxand they are quickly coming20:36
ttxhence me raising this thread now.20:36
*** gatuus has quit IRC20:36
ttxbut yeah, I'm fine with someone pushing the alternate option on the thread: "just accept to potentially have a 15-member TC"20:37
markmcI'm still happier to go with (3) now20:37
russellbsame20:37
mordred++20:37
markmcnot convinced this isn't just kicking the can down the road20:37
notmynamemarkmc: of course it is :-)20:37
ttxok, so if you care and don't like (3), please comment on thread... next topic20:38
ttx#topic Update on the "Future of Incubation / core" joint committee20:38
*** openstack changes topic to "Update on the "Future of Incubation / core" joint committee (Meeting topic: tc)"20:38
*** jog0 has joined #openstack-meeting20:38
ttxWe had meetings on January 10 and 17...20:38
ttxmarkmc: quick update ?20:38
mordredwell, sometimes the can needs kicking20:38
markmcthere's not much to report20:38
markmc2 meetings20:38
markmcboth got into discussing "use cases" for OpenStack users20:38
markmctypes of OpenStack users20:38
markmcone class are the users of our core APIs20:39
markmcnow, I understood the purpose of the discussion was ..20:39
markmc... to come up with a way of deciding what should be core, based on satisfying the needs of those users20:39
markmcand the other types of users we were considering was for potentially other categories, for other types of trademark programs20:39
markmcso real board territory stuff20:39
markmc(we said we wanted the TC to avoid getting into trademark stuff)20:40
markmcbut there was some disagreement about the purpose of the use cases20:40
markmcso ... not sure, really20:40
markmcthat was it20:40
markmc#link https://etherpad.openstack.org/IncUp20:40
markmcthe consensus still seems to be that20:40
markmcCore vs "Integrated"20:40
ttxhopefully it should start moving forward again this week, or the next20:41
markmc(where "Integrated" is "part of the OpenStack release" may have a different name"20:41
markmcCore is the board's domain, Integrated is the TC's domain20:41
ttxin time for us to be able to tell the incubated projects what they may apply to (or not)20:41
ttxmarkmc: done ?20:42
markmcyep20:42
ttxOK, since we have a bit of time left...20:42
ttx#topic H name campaigning20:42
*** openstack changes topic to "H name campaigning (Meeting topic: tc)"20:42
ttxSo you should all have the link to vote in your email20:42
ttxin the diplomatic tongue of the 19th century20:42
ttxTime to convince people to place your favorites toward the top in the poll20:43
russellbha, and 17 minutes to do it20:43
ttxPersonally I like Havana20:43
russellbI request that Halfway be voted 35th20:43
russellbthat's terrible.20:43
ttxrussellb: careful what you wish for20:43
russellb:)20:44
russellbHood is pretty good20:44
russellbbecause we can talk about features 'in the Hood'20:44
ttxI also like Heppner and Helvetia20:45
notmynamea harbor is a safe, calm place. reliable and trusted20:45
markmcHood is short too20:45
markmcwe'll be typing it a lot20:45
notmynamehelvetia is too close to the font name20:45
ttxnotmyname: good point20:46
* ttx downgrades it20:46
russellbHood!20:46
mordredhood is a mountain in the clouds20:46
russellbmordred: nice20:46
ttxHamlet is good too. To be or not to be...20:46
*** n0ano has quit IRC20:47
notmynameisn't mt hood a dormant volcano that may explode and take part of the NW with it?20:47
*** dwcramer has joined #openstack-meeting20:47
russellbnotmyname: even better20:47
*** jhenner has quit IRC20:48
icchaHelix sounds cool http://www.theus50.com/oregon/city.php?cityName=Helix20:48
ttxiccha: it was removed because it's the name of an openstack distro20:49
creihthttp://www.opb.org/programs/ofg/segments/view/126020:49
*** bearovercloud has left #openstack-meeting20:49
ttxhttp://www.morphlabs.com/products/20:49
bcwaldonttx: why isnt Helix on the list?20:50
ttxbcwaldon: because "openstack helix" already exists20:50
russellbseems like a good reason20:50
bcwaldonson of a beesting20:50
russellba shame though, that's a good name20:50
icchaah darn20:50
ttxyeah, was my favorite20:50
*** thingee has joined #openstack-meeting20:50
notmynamecreiht: openstack hell hole? I love it :-)20:50
russellbiccha: +1 for digging it up :)20:50
creihtgoes well with some of the other names chosen in the past20:50
* russellb wants to get his feature in the Hell Hole20:51
russellbdoesn't have a good ring to it20:51
russellbhttp://en.wikipedia.org/wiki/File:Mount_Hood_reflected_in_Mirror_Lake,_Oregon.jpg20:52
russellbgo Hood20:53
ttxso, please cast your vote before the end of the day, and i'll create the LP poll with the first 4 options we collectively pick, to be started Thursday20:53
ttxand on that note let's close the meeting20:53
*** dosaboy has joined #openstack-meeting20:53
ttx#endmeeting20:53
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:53
openstackMeeting ended Tue Jan 22 20:53:58 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-01-22-20.03.html20:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-01-22-20.03.txt20:54
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-01-22-20.03.log.html20:54
*** carlp-away is now known as carlp20:54
ttx(feel free to continue campaigning)20:54
notmynamerussellb: I can do pretty pictures too to get you to vote for harbor http://upload.wikimedia.org/wikipedia/commons/thumb/d/dc/Capri.harbour.from.above.arp.jpg/300px-Capri.harbour.from.above.arp.jpg ;-)20:54
* notmyname actually has harbor as a second choice right now20:55
ttxsame here20:55
*** dwcramer has quit IRC20:55
ttxharbor has this "safe" association to it20:55
bcwaldonttx: what, Grizzly doesn't!?20:56
ttxbcwaldon: hehe20:56
* ttx submits before the browser crashes20:58
notmynameI saw "Hauser" and read "HA user". and thought, "how do you have backup users? that doesn't make any sense"20:58
olaphI saw "Hauser", and thought of Hustler21:00
*** jsavak has quit IRC21:00
ttxmarkmc, heckj, notmyname, bcwaldon, jgriffith, vishy, gabrielhurley, danwent: (still) around ?21:00
markmcyep21:00
gabrielhurleyhere now21:00
notmynamehere21:01
danwentyup21:01
vishyo/21:01
* nijaba around too21:01
jgriffitho/21:01
*** dolphm_ has joined #openstack-meeting21:01
ttxmissing heckj, bcwaldon21:01
ttxlet's start21:01
ttxIf someone can get hold of Joe that would be great21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Jan 22 21:02:19 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:02
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttx#topic General announcements21:02
*** openstack changes topic to "General announcements (Meeting topic: project)"21:02
ttxI had nothing specific21:02
ttxmarkmc, mordred, annegentle, davidkranz: Anything from Stable/CI/QA/Docs teams ?21:02
*** dwchadwick has joined #openstack-meeting21:02
mordrednope21:02
markmc#info 2012.2.3 scheduled for Jan 31, RC Jan 2421:02
markmclatest status posted earlier21:03
markmc#link http://lists.openstack.org/pipermail/openstack-stable-maint/2013-January/000282.html21:03
*** dwchadwick has left #openstack-meeting21:03
markmcsummary is we're looking pretty good21:03
markmcmay see some more nova backports21:03
markmcand a couple of security fixes in the work21:03
markmcs21:03
davidkranzWe are getting close to being able to have more tempest gating turned on for other projects.21:03
russellbnotmyname: pretty picture indeed ... that can have my #2 spot.21:03
*** sdake_z has joined #openstack-meeting21:03
davidkranzI will post a proposal soon.21:03
*** AlanClark has joined #openstack-meeting21:04
ttxOK, let's go project-specific now21:04
ttx#topic Oslo status21:04
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:04
ttx#link https://launchpad.net/oslo/+milestone/grizzly-321:04
ttxmarkmc: Nice progress21:04
markmcoslo-config is inching it's way forward21:05
markmc#link https://review.openstack.org/#/c/20117/21:05
markmcthat's for importing oslo-config into gerrit etc.21:05
markmcapart from that, I'm a bit behind on how the other features are going21:05
ttxmarkmc: The idea would be to switch to bugfixing ASAP so that the common libs are pretty stable around g3 publication time ?21:05
markmcttx, yes, that sounds about right21:06
ttxStill have oslo-build, wsgi-common, no-kombu-default, rpc-api-review with series set to grizzly at https://blueprints.launchpad.net/oslo/grizzly21:06
markmcoh21:06
markmcI'll drop them all21:06
markmcthanks again21:06
ttxok21:06
ttxAnything else on the oslo topic ?21:06
markmcnope21:06
*** gyee has joined #openstack-meeting21:07
* ttx keeps keystone for the end just in case heckj shows up late21:07
ttxdolphm_: can you replace him if he isn't available ?21:07
ttx#topic Swift status21:07
*** openstack changes topic to "Swift status (Meeting topic: project)"21:07
ttxnotmyname: o/21:08
notmynamehi21:08
ttx#link https://launchpad.net/swift/+milestone/1.7.621:08
ttxRelease branch is still under testing...21:08
ttxGoing well so far ? Still targeting Thursday for the release ?21:08
notmynamethings look good AFAIK for 1.7.6 release on thursday21:08
notmynameI'll also tag a new python-swiftclient on thursday too21:08
ttxI just prepared a FINAL=True change for milestone-proposed, for your approval pleasure when everything is ready for release:21:08
ttxhttps://review.openstack.org/#/c/20276/21:09
ttxYou might want to -2 that temporarily to make sure nobody accidentally accepts it :)21:09
notmynameya, was doing that now :-)21:09
ttxAnything more on Swift ?21:10
notmynamenot this week21:10
ttxok then21:10
ttx#topic Glance status21:10
*** openstack changes topic to "Glance status (Meeting topic: project)"21:10
ttxbcwaldon: o/21:10
ttx#link https://launchpad.net/glance/+milestone/grizzly-321:10
*** EmilienM has left #openstack-meeting21:11
bcwaldonttx: hello!21:11
ttxYou said you would lock down glance-notifications-deux assignee this week... Any candidate ?21:11
bcwaldonyes, Andrew melton21:11
ttxbcwaldon: ok, can you assign him ? or should I ?21:12
bcwaldongo right ahead21:12
ttxbcwaldon, iccha: how is glance-api-v2-image-sharing going so far ?21:12
ttx(assigned)21:12
bcwaldonseveral emails about implementation at this point - path forward is clear at this point21:12
ttxok, we'll be keeping an eye on this one to make sure code is proposed early21:13
ttxAnything more on Glance ?21:14
bcwaldonnot from me :)21:14
ttxbcwaldon: markwash is finalizing glance-domain-logic-layer before starting api-v2-property-protection ?21:14
bcwaldonyes21:15
ttxack21:15
ttx#topic Quantum status21:15
*** openstack changes topic to "Quantum status (Meeting topic: project)"21:15
ttxdanwent: hi!21:15
danwenthello :)21:15
ttx#link https://launchpad.net/quantum/+milestone/grizzly-321:15
danwentmore BPs, not less :(21:15
* ttx refreshes21:15
danwentwe talked about this at our team meeting yesterday21:15
ttxScript reports new stuff targeted to grizzly-3 but not approved in series goal:21:16
danwentbasicaly, the core devs are going to focus on making sure that the 6 'high' items get merged.  everything else is "best effort"21:16
danwentttx: yes, people get adding more21:16
ttxbrocade-quantum-plugin, cisco-plugin-exception-handling, cisco-plugin-n1k-support, nvp-qos-extension, quantum-floodlight-bigswitch-l321:16
danwentok, two of those are in, (recently updated after you ran the script). two of those I need to talk to the devs about.21:17
ttxdanwent: I still fear too many reviews might distract core team from fixing key bugs21:17
ttxbut it's difficult to refuse before feature freeze ;)21:17
danwentif core devs are following priorities, I don't think that needs to be the case.21:17
ttxI see you have 6 "High" priority blueprints now. Progressing nicely ?21:17
danwentyes.21:18
ttxhttps://blueprints.launchpad.net/quantum/+spec/vif-plugging-improvements is marked "Implemented" but has https://review.openstack.org/19714 in progress21:18
danwenttwo are not yet in review21:18
danwentthat's a bad tag in the commit message.  the core functionality is in, which is what the bps was tracking21:18
ttxok, will clean that up21:19
danwentthat commit you reference should really be its own bug, i will talk to akihiro21:19
*** markmc has quit IRC21:19
ttxdanwent: do you have an assignee for auto-associate-floating-ip ?21:19
*** thingee has quit IRC21:19
danwentof the two 'high' that are not in review, once is expected to be posted end of this week, and another the week after that.21:19
*** jhenner has joined #openstack-meeting21:19
danwentttx: no.  i'm going to an openstack meetup tomorrow were we will be talking about quantum and people who are looking for things to work on will supposedly be there, that is one of the items on the that "any takers?" list21:20
*** thingee has joined #openstack-meeting21:20
ttxok21:20
danwentif we don't, we'll bump it (its already out of g-3, no?)21:20
danwentah, my mistake21:20
danwentwill remove it from g-3, but keep assigned to grizzly at least for a few more days21:20
ttxNo that would be quantum-v2-euca-compat & load-plugin-supported-extensions (still in G but not in G3)21:20
danwentok, changed21:21
ttxAnything else on Quantum ?21:21
danwentnope21:21
ttxYou seem to have your enormous goals under control. Thanks!21:21
ttx#topic Cinder status21:21
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:21
ttxjgriffith: hi!21:21
ttx#link https://launchpad.net/cinder/+milestone/grizzly-321:21
jgriffithhowdy21:22
ttxYou still have 6 blueprints that were targeted to g3 but not approved in the series goal (or prioritized) yet:21:22
ttxhuawei-volume-driver, xenapinfs-snapshots, xenapinfs-glance-integration, emc-fibre-channel-volume-driver, emc-isilon-iscsi-volume-driver, scality-volume-driver21:22
jgriffithI think I just fixed them... try refresh?21:22
ttxI ran my script like 5 seconds ago... maybe a cache issue21:23
ttxCode for update-vol-metadata was merged, should it be marked Implemented now ?21:23
jgriffithyes21:24
ttxjgriffith: the abovementioned blueprints are still "proposed" for grizzly21:24
ttxhttps://blueprints.launchpad.net/cinder/grizzly/+setgoals21:24
*** dosaboy has quit IRC21:24
* ttx updates update-vol-metadata21:25
jgriffithttx looking21:25
jgriffithregardless, my intent is to approve them for G3 as low pri21:25
ttxWhen will work start on https://blueprints.launchpad.net/cinder/+spec/local-storage-volume ?21:25
jgriffithdoh... direction versus def21:26
jgriffithI need to check with rongze21:26
jgriffithIf he has no update tomorrow I boot it back out21:26
ttxit's been pushed back a bit already, so if it's no longer a grizzly prio, its priority should be downgraded21:26
jgriffithagreed21:26
ttxbtw did you come to a decision for del-vols-with-snaps ? Remove from grizzly goal ?21:26
jgriffithI'm dropping it21:27
ttxok21:27
ttxAnything more in Cinder ?21:27
jgriffithI'll be adding a BP or two later today Aggregates and AZ's21:27
jgriffithOther than that no, not really21:27
jgriffithAlthough that could actually be a bug as opposed to a BP21:28
ttxbugs are good too.21:28
*** stevemar has quit IRC21:28
ttxif properly targeted/prioritized21:28
ttx#topic Nova status21:28
*** openstack changes topic to "Nova status (Meeting topic: project)"21:28
ttxvishy, russellb: o/21:28
vishyhi21:28
ttx#link https://launchpad.net/nova/+milestone/grizzly-321:28
russellbhi21:29
ttxSo before cleanup we had 46 blueprints targeted... and after we have 47 ;)21:29
ttxOr is the cleanup still in progress ?21:29
vishyi cleaned up the untargeted ones21:29
*** dwcramer has joined #openstack-meeting21:29
vishyand untargetted a few i know won't make it21:29
russellbi've been going through some21:29
russellbit's still "early" enough that lots of people are still optimistic, heh21:29
*** ttx has left #openstack-meeting21:30
russellbman down!21:30
sdake_zrage exit21:30
*** ttx has joined #openstack-meeting21:30
ttxbeh21:30
ttxYou have 3 blueprints targeted to g3 but not in series goal (and without priority):21:30
ttxmigrate-volume-block-migration, cpu-entitlement, multi-tenancy-aggregates21:30
ttxlooks like they should be reviewed, and series-set/prioritized if liikely21:31
vishyi'm still going through the other ones that are definitely gone21:31
*** thingee has left #openstack-meeting21:31
ttxOn the positive side, had a few blueprints that might be completed already:21:31
ttxhttps://blueprints.launchpad.net/nova/+spec/db-session-cleanup21:31
ttxhttps://blueprints.launchpad.net/nova/+spec/libvirt-spice21:32
russellbspice is done pretty sure21:32
ttxhttps://blueprints.launchpad.net/nova/+spec/direct-file-copy21:32
* russellb updates21:32
ttxhttps://blueprints.launchpad.net/nova/+spec/trusted-filter-cache21:32
russellband direct-file-copy, that's done too pretty sure ...21:32
vishydb-session is not done21:32
vishytrusted-filter is done21:32
ttxthe comit message on trusted-filter-cache is also pretty definitive21:33
ttxyeah21:33
russellbk, will update trusted filter21:33
ttxWas also wondering about the non-started "High" priority blueprints:21:33
russellbI tried to ping arosen earlier today on the quantum one not started21:33
russellbno response yet21:33
ttxbut only one is left now21:33
ttxok21:33
ttxmight be blocked by some quantum work21:33
ttxrussellb: should rpc-based-servicegroup-driver be removed from no-db-compute deps ?21:34
russellbttx: yes21:34
ttxwill do21:34
russellbthanks21:34
vishyttx: cleaned up the 3 without series goal21:34
vishyrussellb: i pinged him21:34
ttxvishy: nice cleanup on https://blueprints.launchpad.net/nova/grizzly21:34
vishyhe said that he will have a merge prop next week21:34
*** rturk has left #openstack-meeting21:35
vishyttx: i left https://blueprints.launchpad.net/nova/+spec/multi-boot-instance-naming21:35
russellbvishy: k21:35
vishybecause I was hoping to try and get a volunteer to implemnt someting there21:35
ttxsure, that's ok21:35
ttxI think the current view represents what we know21:36
ttxJust need to keep adjusting it over the coming weeks21:36
ttxwhen we learn of stuff that won't make it21:36
*** dosaboy has joined #openstack-meeting21:36
ttxAny question on Nova ?21:36
nijabawhatś the expected date for cell completioon? g3 or before?21:37
russellbit's really close21:37
nijabagreat!  jd__ can't wait :)21:37
ttxyeah, i've been getting optimistic for this one. Looked like it would never make it completely, but it's really getting close now21:37
russellbcomstud said we may be able to call it done already21:37
russellbthere's always going to be some updates in the queue21:37
russellbthe stuff left is just a few additional features that aren't necessarily required IIRC21:38
ttxThat's fine, at some point we need to consider known bugs as bugs21:38
russellbyeah, we have some cells stuff that needs to go into release notes21:38
russellbdo we have a place to start writing that stuff done?21:38
ttxhttp://wiki.openstack.org/ReleaseNotes/Grizzly21:38
russellbperfect21:38
ttxAny other question on Nova ?21:39
ttx#topic Horizon status21:39
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:39
ttxgabrielhurley: hi!21:39
ttx#link https://launchpad.net/horizon/+milestone/grizzly-321:39
gabrielhurleyhi21:39
*** jcmartin has joined #openstack-meeting21:39
gabrielhurleyahead of schedule today, eh ttx?21:40
gabrielhurleyusually it's another ten minutes21:40
ttxI skipped keystone21:40
comstudi think it can be considered done21:40
comstudthe patches up enable further support21:40
ttxgabrielhurley: blame heckj, we all do21:40
gabrielhurleycomstud: I hope you're referring to keystone. ;-)21:40
comstudand that'll be ongoing21:40
comstud:x21:40
ttxgabrielhurley: Plan looks good, slow progress overrall though21:40
russellbcomstud: omg, awesome, i'll update it21:41
gabrielhurleythe blueprints are distributed across a lot of people, so 10 people working slowly isn't so bad.21:41
gabrielhurleywe've had a lot of bugs fixed this week though21:41
gabrielhurleyso that's awesome21:41
ttxIs https://blueprints.launchpad.net/horizon/+spec/file-upload-redux in good shape ?21:41
gabrielhurleypeople's energy has been on those, I think21:41
gabrielhurleydavidlenwell: has his team working on it21:41
cody-somervilleI've started helping David work on file-upload-redux21:42
gabrielhurleybut he's had some delays. I'm communicating with him regularly on it21:42
gabrielhurleyhe's stil lconfident21:42
*** dosaboy has quit IRC21:42
ttxgood21:42
ttxAnything more on Horizon ?21:42
gabrielhurleynot off the top of my head21:42
*** otherwiseguy has joined #openstack-meeting21:42
*** dosaboy has joined #openstack-meeting21:42
gabrielhurleyI'm a little scattered today21:42
ttxheh21:43
arosenhey russellb in progress hopefully i'll  have something soon to put on review in the next day or so.21:43
arosenrussellb: just started this morning though.21:43
ttxarosen: could you update the blueprint status ?21:43
arosenttx:  sorry up let me do that now.21:43
ttxthx!21:43
arosenyup*21:43
ttx#topic Keystone status21:43
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:43
ttxdolphm_: around ?21:44
dolphm_ttx: o/21:44
ttx#link https://launchpad.net/keystone/+milestone/grizzly-321:44
russellbarosen: great thanks!21:44
ttxdolphm_: let me check what questions I had, and if you can do anything abot it without heckj21:44
dolphm_ttx: i just updated the status of a few bp's21:45
ttxI saw https://blueprints.launchpad.net/keystone/+spec/replace-tenant-user-membership which was not targeted to grizzly but is being worked on21:45
ttxI am a bit confused as to how it relates to https://blueprints.launchpad.net/keystone/+spec/trusts21:45
ttxThat's more for ayoung I guess21:45
dolphm_ttx: i'm not the best person to explain, but it is a pre-requisite for implementing trusts21:45
dolphm_ttx: trusts has a long line of blockers at this point21:46
ttxdolphm_: ok, so it should be added as a dependency to trusts and added to the g3 plan21:46
ayoungttx, I can;'t tests trusts without it21:46
ttxI'll try to get Joe to clarify all that21:46
ttxdolphm: How is default-domain going so far ?21:46
ayoungthe problem is basically the v3 api needs https://blueprints.launchpad.net/keystone/+spec/replace-tenant-user-membership in order to work properly21:46
dolphm_ttx: yes, i'm struggling with launchpad's Add Dependency feature and probably butchering it more than anything else21:47
ayoungand trusts just kindof exposes it21:47
ttxayoung: yeahn should probably have series goal and target milestone set21:47
dolphm_ttx: good progress, there's two of us working on it21:47
ttxI see code proposed, I suspect more is coming ?21:47
dolphm_ttx: we've got 2/4 major pieces in code review21:47
ayoungtrusts are based on the idea that you can limit the roles, and then a user gets a token with that limited set of roles.   Thus the definition of tenant membership needs to be scoped down to "the user has some role in a tenant"21:48
dolphm_ttx: schema + data migrations, and then revising v2 API calls to assume that default domain21:48
*** dprince has quit IRC21:48
ttxayoung: you also have the delegation blueprint on your plate, do you think you can complete all those ?21:48
*** jog0 has quit IRC21:49
ttxor should we start adjusting priorities ?21:49
*** galthaus has quit IRC21:50
dolphm_ayoung: i'd vote to bump delegation to the next milestone21:50
ttxdolphm_: that would be H.21:50
dolphm_ttx: correct21:51
*** galthaus has joined #openstack-meeting21:51
dolphm_trusts has more immediate utility and it's what ayoung is spending more time on, at the moment :)21:51
*** galthaus has quit IRC21:51
ttxyeah, i'm all for realistic goals21:52
*** galthaus has joined #openstack-meeting21:52
ttxanyway, i'll try to get hold of heckj and get all those adjusted. I may show up at next keystone meeting to help21:52
dolphm_ttx: thanks21:52
ttxthough the timing is a bit horrible for me21:52
*** danwent has quit IRC21:52
ttxdolphm_: any question you had ?21:52
dolphm_ttx: nope21:52
dolphm_(when will heckj be back?)21:53
ttxI'll track him down with a harpoon21:53
ttx#topic Incubated projects21:53
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:53
nijabao/21:53
ttxyay Ceilometer21:53
ttx#link https://launchpad.net/ceilometer/+milestone/grizzly-321:53
ttxLooks good, slow progress overrall21:53
ttxYou should probably review the 22 blueprints you have with series goal = grizzly21:54
ttxAnd remove the series goal for those which won't make it21:54
nijabattx: yes, but I am confident for what is targeted for g3.  less so for grizzly in general21:54
ttxLooks like https://blueprints.launchpad.net/ceilometer/+spec/meters-discovery was completed in G2. Should I fix that for you ?21:54
ttx(it's not targeted to grizzly-2)21:54
*** danwent has joined #openstack-meeting21:54
nijabattx: will start the cleanup campaign at the next meeting21:54
nijabattx: I just targeted it for g3 as g2 is not avail anymore in my pop up21:55
ttxyes, that's because the milestone is inactive. LP subtleties, let me fix it21:55
nijabathanks21:55
ttxnijaba: questions ?21:55
nijabanope21:56
ttxAnyone from Heat team ?21:56
sdake_zyup hi21:56
ttxsdake: I heard you are going to elect a PTL...21:56
ttxFYI if you apply for integration in the common release for H (before the end of this cycle) you'll have elections again in March like all other projects...21:56
ttxnijaba: fixed21:56
sdake_zyes21:56
sdake_zthats the plan21:57
nijabattx: thanks21:57
ttxok, just made sure you knew that :)21:57
ttx#link https://launchpad.net/heat/+milestone/grizzly-321:57
sdake_zyes, not sure why ppl didn't hold an election - but can't change past:)21:57
*** kspear has joined #openstack-meeting21:57
sdake_zthis week we focused on bugs21:57
sdake_zfixed ~10 or so21:57
ttxShould all 'unknown' status on that page actually mean 'not started' ?21:57
sdake_zour moniker integration was deferred because the moniker client is broken21:58
sdake_zyup i'll adjust that thinks ttx - still learning way around launchpad21:58
sdake_zthinks/thanks ;)21:58
sdake_zi expect some of those work has started though21:58
sdake_zour meeting is tomorrow 2000 UTC i'll get the states set straight then - but set to not started in the meantime21:59
* ttx will remove the grizzly-3 milestone target from moniker-resource since it's deferred21:59
ttxok that's all I had21:59
sdake_zi did that - series goal "none" ?21:59
ttxsdake: questions ?21:59
ttxsdague: the milestone was still set. That's two separate but linked concepts21:59
sdake_zya question about the moniker bp - series goal doesn't seem to remove it from the seriess21:59
ttxsdake: ^21:59
sdake_zgot it thanks21:59
ttxthe problem is that to have consistent views we have to sync them a bit manually22:00
sdake_zwhere is the other button located?22:00
ttx(one is controlled by the drivers (the series goal) while the other is set by the blueprint assignee (the milestone target)22:00
*** AlanClark has quit IRC22:00
ttxSeach for "Milestone target:"22:00
sdake_zok got it22:00
sdake_zyup thanks!22:00
ttxok, we are done22:01
ttxThanks!22:01
ttx#endmeeting22:01
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:01
openstackMeeting ended Tue Jan 22 22:01:10 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-01-22-21.02.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-01-22-21.02.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-01-22-21.02.log.html22:01
russellbttx runs one heck of a meeting to do all that in an hour22:01
nijabanight ttx, and thanks22:01
russellbnice work, sir.22:01
ttxand at 11pm22:01
ttxI actually have a team of monkeys running it with me22:01
ttxI used to prepare all upfront but bcwaldon kept on tricking me with last-minute updates22:02
ttxso now I use my monkey army22:02
* nijaba loves the monkeys we seems to have in the center of france nowdays22:02
gabrielhurleyHORIZON TIIIIIIIME!22:03
gabrielhurley#startmeeting horizon22:03
openstackMeeting started Tue Jan 22 22:03:06 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
cody-somerville\o/22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:03
*** openstack changes topic to " (Meeting topic: horizon)"22:03
openstackThe meeting name has been set to 'horizon'22:03
sdakehttp://wiki.answers.com/Q/What_is_the_average_monkey_IQ22:03
gabrielhurleyHi folks! :-)22:03
gabrielhurleycomments about monkeys aside...22:03
gabrielhurley#topic General Status22:04
*** openstack changes topic to "General Status (Meeting topic: horizon)"22:04
kspearhowdy22:04
gabrielhurleykspear: hi22:04
gabrielhurleyWe've got tons of activity in the bugfix/review arena lately. That's awesome. I'm happy to see people engaged.22:04
*** eharney has quit IRC22:04
gabrielhurleyGood discussion on tickets/reviews, too. I like that we're interacting more to come to better final products.22:05
*** annegentle has joined #openstack-meeting22:05
*** asalkeld has joined #openstack-meeting22:05
gabrielhurleyso keep all that up!22:05
gabrielhurley#topic bugs and blueprints22:05
*** openstack changes topic to "bugs and blueprints (Meeting topic: horizon)"22:05
*** psedlak has joined #openstack-meeting22:05
gabrielhurleyWe had something like a dozen bugs fixed in the past week, which I've now gotten all correctly assigned to the G3 milestone so it reflects all the work y'all are doing.22:06
gabrielhurleyThere was one bug report which concerned me...22:06
gabrielhurleyhttps://bugs.launchpad.net/horizon/+bug/110044422:06
uvirtbotLaunchpad bug 1100444 in horizon "Edit Flavor Window Displays Details of Deleted Flavors" [High,Confirmed]22:06
gabrielhurleySounds like it's probably just a matter of fixing our API call, but editing the wrong flavor is definitely a high priority to fix.22:07
gabrielhurleyOtherwise the fixes outweighed the new reports by far.22:08
gabrielhurleyPeople are picking things off the list too, so I'm not worried at the moment.22:08
gabrielhurleyAs for blueprints, it's still early in the cycle, but does anybody have updates they'd like to give/22:08
gabrielhurley?22:08
kspeari've updated my image organisation blueprint22:09
kspearhttps://blueprints.launchpad.net/horizon/+spec/organised-images-display22:09
kspearfeedback welcome22:09
gabrielhurleysweet. I'll take a look today./22:09
jpichNice22:09
cody-somervilleDavid pinged me last week and I've started this week helping him with the file-upload-redux related blueprints - specifically on the django side of things. I have some questions re: implementation if there's time in the meeting.22:09
gabrielhurleyoooh, I like the mockup22:09
gabrielhurleycody-somerville: sure. we'll do that at the end22:10
cody-somervillekspear: nice!22:10
kspearthanks22:10
gabrielhurleyI know all the quantum blueprints are on track, so I'm not worried there.22:10
gabrielhurleyjpich, vkmc, mrunge: any updates you'd like to share or shall I ask again next week?22:11
*** sarob has quit IRC22:11
cody-somervilleI noticed that the admin user does not have access to the quantum related views.22:11
jpichI will start on the blueprint next week, so no update so far22:11
cody-somervilleIs that intentional?22:11
vkmcCurrently doing some research about the bp, nothing relevant yet, I feel I'd have something more concrete next week22:11
*** AlanClark has joined #openstack-meeting22:12
vkmcI have concerns about some bugs I'm working on22:12
gabrielhurleycody-somerville: I believe the goal is to expand some of those capabilities in G3, though it's still a work in progress. They've got a huge amount of feature-work to get in and can only do so much per cycle.22:12
gabrielhurleyvkmc: no problem. I'm gonna open things up for general questions in a minute if you want to ask about specific issues.22:12
cody-somervillegabrielhurley: It's just weird that you can't really access the work that is done because they require additional permissions that the admin user by default in devstack does not have.22:13
vkmcgabrielhurley, Sure22:13
gabrielhurleycody-somerville: oh, I didn't realize that... could you file that as a bug against horizon + quantum + devstack?22:13
gabrielhurleyit's probably a devstack fix, but we should all track it22:13
cody-somervilleSure thing.22:13
* gabrielhurley admits he doesn't generally have quantum set up in devstack and doesn't notice these things immediately.22:14
jpichI can see the networks and subnets panels in my devstack, didn't realise there was more22:14
cody-somervillemaybe it only grants the permissions if quantum is setup to automatically have the views hidden22:14
cody-somervillejpich: I can't see the networks and subnets panels in my devstack22:14
gabrielhurleycody-somerville: are you sure quantum is in your keystone service catalog?22:15
gabrielhurleythat's what triggers hiding/showing them22:15
cody-somervilleand manually accessing the urls gives me a permission denied error22:15
gabrielhurleyhorizon looks for a service called "network"22:15
cody-somervillegabrielhurley: I'll have to take a look.22:15
gabrielhurleyif that's not present you'll get the behavior you describe22:15
jpichI did have to add this to my settings - http://wiki.openstack.org/Horizon#Quantum_Configuration_.28optional.29 - perhaps devstack should add it if quantum is enabled22:15
*** otherwiseguy has quit IRC22:16
gabrielhurleyjpich: that... just shouldn't be true. but yeah, we need a ticket to track this.22:16
*** otherwiseguy has joined #openstack-meeting22:16
gabrielhurleyI keep finding new places where Horizon settings are misdocumented22:16
gabrielhurley::sigh::22:16
gabrielhurleyI think we've moved into the next topic though22:17
gabrielhurley#topic open discussion22:17
*** openstack changes topic to "open discussion (Meeting topic: horizon)"22:17
jpichgabrielhurley: I probably added them at the same time I enabled quantum and didn't notice if they weren't needed. Ah well22:17
gabrielhurleyjpich: probably so22:17
gabrielhurleycody-somerville: I'd check your service catalog in keystone first. that's the most likely culprit.22:17
gabrielhurleyso, cody-somerville I think you asked first about having Django questions. vkmc you can go next...22:18
jpichgabrielhurley: Are those settings still needed for Folsom only?22:18
cody-somervilleAgreed. In any regard, I think it would be helpful if those views returned something other than 401 in this scenario to avoid confusion.22:18
gabrielhurleyjpich: they were true in... Diablo? Essex removed Quantum, and Folsom re-added it without all that extra settings nonsense.22:18
gabrielhurleycody-somerville: yep22:19
cody-somervilleOk. So image-upload spec specifically says this:22:19
cody-somerville"Strong preference goes to a solution that does not involve proxying the file through the Horizon server (since allowing arbitrary upload of potentially very large files is dangerous)."22:19
jpichgabrielhurley: Huh! I need to re-run a few tests on how I enabled the Quantum panels everywhere, thank you22:19
cody-somervilleFrom what I understand so far, davidlenwell's plan is for the file to be uploaded to the Horizon server and than sent to whereever. I'm wondering if we want this or if we should do something like jquery iframe transport plugin so that we upload the files directly to glance, swift, or whatever.22:20
cody-somervilleOR if we need to support both22:20
gabrielhurleycody-somerville: that's still my preference. uploading a multi-GB image through apache/nginx/whatever, storing that in /tmp or some other upload directory, then sending that to Glance/Swift via another API call is really not happy.22:20
gabrielhurleycody-somerville: the latter (transport directly to glance/swift) would be AMAZING22:20
gabrielhurley'cuz DOS'ing a dashboard install via filling up the disk is trivial if you allow GB-sized uploads22:21
notmynamegabrielhurley: cody-somerville: swift supports that feature today (direct from browser upload)22:22
gabrielhurleyyeah, I know swift does, not sure about Glance (if it's not backed to swift)22:22
notmynamesorry for the drive-by comment. I don't really know the context, except that "swift" was highlighted in my IRC client :-)22:23
gabrielhurleycody-somerville: you might want to coordinate with notmyname and bcwaldon on what possibilities are available for direct transfers from the browser22:23
gabrielhurleyanother idea off the top of my head: if direct upload to glance/swift isn't possible, I'd also wonder if we could do some sort of chunked/streaming transfer so that the data is proxied through Horizon but only in small segments.22:23
*** lcheng has joined #openstack-meeting22:23
gabrielhurleythings to think about.22:23
cody-somervillegabrielhurley: we can do that too22:23
cody-somervilleI just want to clarify what OUR requirements are22:23
gabrielhurleycool. I think you've got it now.22:23
gabrielhurleyI've got a hard stop at 2:30 today (sorry), and I'd like to let vkmc ask her question.22:24
cody-somervilleIf we can do the direct upload, that is indeed cool but I know that some installations of OpenStack don't have glance publicly available so do we need to support proxying too?22:24
gabrielhurleyanything we don't have time for, feel free to email me and I'll try to respond promptly22:24
davidlenwellcody-somerville: I'm fine with your jquery iframe transport plugin idea for the most part22:24
*** maoy has quit IRC22:24
cody-somervilleie. which do we want to target for this milestone? I personally think proxying (especially if we store and than async upload) has a lot of risk22:24
gabrielhurleycody-somerville: not a hard requirement. For Grizzly we can document what the requirements are for that feature to work22:24
gabrielhurleyif thta means a public glance endpoint that's fine22:25
vkmcThanks gabrielhurley, it's not too important, but I'd love to get some suggestions for this two bugs I'm working on https://bugs.launchpad.net/horizon/+bug/1055217 and https://bugs.launchpad.net/horizon/+bug/110083022:25
uvirtbotLaunchpad bug 1055217 in horizon "Instance deletion confirmation dialog should show instance name" [Wishlist,In progress]22:25
gabrielhurleyshowing the instance name can probably be done by just looking at the "name" column for the row the action was triggered from.22:26
gabrielhurleywhat's the question on the second one (visual heirarchy)?22:26
gabrielhurleyI thought that one was just about making the heading levels, etc. consistent.22:27
jpichThe questions is a comment on the review - https://review.openstack.org/#/c/20226/22:27
vkmcYeah, I considered that, but the main problem with it is that not all the tables follow the same ordering22:27
*** yaguang has quit IRC22:27
*** roaet is now known as roaet-away22:28
vkmcHere I uploaded possible solutions for both https://review.openstack.org/#/c/20234/ - https://review.openstack.org/#/c/20226/22:28
*** reed has quit IRC22:29
*** mrunge has quit IRC22:29
gabrielhurleygotcha. I'll have to take a look at the review.22:29
*** markvoelker1 has quit IRC22:30
gabrielhurleyI have to run though. next meeting is calling (this one in person).22:30
gabrielhurleyI will look at those this afternoon though22:30
gabrielhurleythanks everyone!22:30
vkmcThanks :)22:30
gabrielhurley#endmeeting22:30
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:30
openstackMeeting ended Tue Jan 22 22:30:29 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-01-22-22.03.html22:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-01-22-22.03.txt22:30
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-01-22-22.03.log.html22:30
cody-somervilleWhens the next Horizon meeting?22:30
jpichcody-somerville: every week at this time22:30
vkmcNext Tuesday22:30
cody-somervillecool22:30
*** radez is now known as radez_g0n322:31
*** flaper87 has quit IRC22:32
*** AlanClark has quit IRC22:34
*** redthrux has left #openstack-meeting22:35
*** jhenner has quit IRC22:36
*** yaguang has joined #openstack-meeting22:38
*** sdake has quit IRC22:39
*** woodspa has quit IRC22:41
*** reed has joined #openstack-meeting22:42
*** agentle_ has joined #openstack-meeting22:47
*** dwcramer has quit IRC22:49
*** annegentle has quit IRC22:49
*** agentle_ is now known as annegentle22:49
*** jpich has quit IRC22:49
*** eharney has joined #openstack-meeting22:52
*** brich1 has left #openstack-meeting22:52
*** MarkA3 has joined #openstack-meeting22:55
*** john5223 has quit IRC22:56
*** danwent has quit IRC22:57
*** FallenPegasus has quit IRC22:58
*** yaguang has quit IRC22:58
*** markvoelker has joined #openstack-meeting23:00
*** olaph has left #openstack-meeting23:01
*** jcmartin has quit IRC23:05
*** mtreinish has quit IRC23:07
*** koolhead17 has quit IRC23:07
*** markvoelker has quit IRC23:08
*** jcmartin has joined #openstack-meeting23:10
*** cp16net is now known as cp16net|away23:11
*** topol has quit IRC23:11
*** Gordonz has quit IRC23:11
*** cp16net|away is now known as cp16net23:13
*** yaguang has joined #openstack-meeting23:14
*** markmcclain has quit IRC23:14
*** fnaval has quit IRC23:15
*** galthaus has quit IRC23:15
*** markmcclain has joined #openstack-meeting23:16
*** danwent has joined #openstack-meeting23:16
*** ryanpetr_ has joined #openstack-meeting23:18
*** cloudchimp has quit IRC23:20
*** annegentle has quit IRC23:20
*** vkmc has quit IRC23:21
*** ryanpetrello has quit IRC23:21
*** kspear has left #openstack-meeting23:24
*** reed has quit IRC23:27
*** danwent has quit IRC23:30
*** jdbarry has left #openstack-meeting23:31
*** dolphm_ has quit IRC23:32
*** ryanpetr_ has quit IRC23:32
*** blamar has quit IRC23:33
*** cp16net is now known as cp16net|away23:35
*** cdub_ has quit IRC23:41
*** rturk has joined #openstack-meeting23:44
*** rturk has left #openstack-meeting23:44
*** cp16net|away is now known as cp16net23:45
*** carlp is now known as carlp-away23:46
*** kaganos has quit IRC23:50
*** dosaboy has quit IRC23:57
*** nati_ueno has joined #openstack-meeting23:58
*** garyTh has quit IRC23:59

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