Tuesday, 2013-02-05

*** dwcramer has joined #openstack-meeting00:00
*** tongli has joined #openstack-meeting00:02
*** stevebaker has quit IRC00:08
*** stevebaker has joined #openstack-meeting00:08
*** fnaval has joined #openstack-meeting00:09
*** SumitNaiksatam has quit IRC00:09
*** khaido1 is now known as zaro00:11
*** same5336 has joined #openstack-meeting00:11
*** dolphm has joined #openstack-meeting00:16
*** same5336 has quit IRC00:17
*** same5336 has joined #openstack-meeting00:18
*** ewindisch has quit IRC00:19
*** stevebaker has quit IRC00:20
*** rkukura has left #openstack-meeting00:21
*** tongli has quit IRC00:22
*** afazekas has quit IRC00:23
*** stevebaker has joined #openstack-meeting00:24
*** notmyname has quit IRC00:27
*** notmyname has joined #openstack-meeting00:27
*** annegentle has joined #openstack-meeting00:27
*** markwash has quit IRC00:34
*** lloydde has quit IRC00:42
*** annegentle has quit IRC00:45
*** annegentle has joined #openstack-meeting00:48
*** mdomsch has quit IRC00:48
*** lbragstad has joined #openstack-meeting00:50
*** annegentle has quit IRC00:59
*** nati_ueno has quit IRC01:02
*** sleepsonthefloor has quit IRC01:03
*** hemna is now known as hemnafk01:08
*** ewindisch has joined #openstack-meeting01:17
*** vkmc has quit IRC01:19
*** bdpayne has quit IRC01:19
*** ewindisch has quit IRC01:20
*** ewindisch has joined #openstack-meeting01:26
*** xiao_ has joined #openstack-meeting01:31
*** colinmcnamara has quit IRC01:34
*** colinmcnamara has joined #openstack-meeting01:34
*** colinmcnamara has quit IRC01:39
*** ewindisch has quit IRC01:40
*** dripton_ has joined #openstack-meeting01:44
*** noslzzp has joined #openstack-meeting01:46
*** dripton has quit IRC01:47
*** bdpayne has joined #openstack-meeting01:51
*** ryanpetrello has joined #openstack-meeting01:53
*** markmcclain has quit IRC01:54
*** ayoung has quit IRC01:55
*** bdpayne has quit IRC02:02
*** anniec_ has quit IRC02:03
*** anniec has joined #openstack-meeting02:10
*** ryanpetrello has quit IRC02:13
*** sarob has quit IRC02:15
*** ryanpetrello has joined #openstack-meeting02:21
*** markvan has joined #openstack-meeting02:26
*** vipul is now known as vipul|away02:31
*** vipul|away is now known as vipul02:31
*** emagana_ has quit IRC02:36
*** topol has joined #openstack-meeting02:37
*** cp16net is now known as cp16net|away02:37
*** adjohn has quit IRC02:38
*** Mandell has quit IRC02:40
*** ewindisch has joined #openstack-meeting02:44
*** dolphm has quit IRC02:44
*** dolphm has joined #openstack-meeting02:55
*** garyk has quit IRC02:58
*** markmcclain has joined #openstack-meeting03:02
*** markvan has quit IRC03:02
*** cp16net|away is now known as cp16net03:03
*** anniec has quit IRC03:04
*** cp16net is now known as cp16net|away03:04
*** cp16net|away is now known as cp16net03:04
*** otherwiseguy has joined #openstack-meeting03:08
*** adjohn has joined #openstack-meeting03:09
*** novas0x2a|laptop has quit IRC03:10
*** garyk has joined #openstack-meeting03:12
*** bencherian has quit IRC03:15
*** adjohn has quit IRC03:19
*** danwent has quit IRC03:19
*** metral has joined #openstack-meeting03:20
*** ryanpetrello has quit IRC03:27
*** maurosr has quit IRC03:40
*** DuncanT1 has joined #openstack-meeting03:49
*** DuncanT has quit IRC03:53
*** christophk has quit IRC03:53
*** garyk has quit IRC03:58
*** noslzzp has quit IRC04:00
*** bdpayne has joined #openstack-meeting04:11
*** bdpayne has quit IRC04:15
*** christophk has joined #openstack-meeting04:23
*** koolhead17 has joined #openstack-meeting04:31
*** markvan has joined #openstack-meeting04:34
*** markvan has quit IRC04:35
*** dolphm has quit IRC04:38
*** adjohn has joined #openstack-meeting04:40
*** lloydde has joined #openstack-meeting04:42
*** cp16net is now known as cp16net|away04:43
*** adjohn has quit IRC04:44
*** danwent has joined #openstack-meeting04:57
*** cp16net|away is now known as cp16net05:02
*** otherwiseguy has quit IRC05:03
*** bdpayne has joined #openstack-meeting05:19
*** markmcclain has quit IRC05:31
*** adjohn has joined #openstack-meeting05:34
*** troytoman-away has quit IRC05:37
*** cp16net is now known as cp16net|away05:37
*** Mandell has joined #openstack-meeting05:38
*** lloydde has quit IRC05:38
*** cyclicflux has joined #openstack-meeting05:41
*** Guest25954 has joined #openstack-meeting05:41
*** cyclicflux_ has joined #openstack-meeting05:42
*** cp16net|away is now known as cp16net05:43
*** cyclicflux_ is now known as CyclicFlux05:45
*** topol has quit IRC05:48
*** troytoman-away has joined #openstack-meeting05:49
*** stevebaker has quit IRC05:59
*** topol has joined #openstack-meeting06:00
*** topol has quit IRC06:07
*** martine has quit IRC06:14
*** jjm3lp has quit IRC06:20
*** bdpayne has quit IRC06:21
*** metral has quit IRC06:29
*** garyk has joined #openstack-meeting06:35
*** same5336_ has joined #openstack-meeting06:45
*** same5336 has quit IRC06:49
*** same5336_ is now known as same533606:49
*** lloydde has joined #openstack-meeting06:49
*** lloydde has quit IRC06:53
*** gongysh_ has quit IRC06:56
*** emagana has joined #openstack-meeting06:57
*** davidh_ has quit IRC06:59
*** CyclicFlux has quit IRC07:03
*** zigo has joined #openstack-meeting07:08
*** zigo_ has quit IRC07:08
*** same5336 has quit IRC07:10
*** same5336 has joined #openstack-meeting07:10
*** emagana has quit IRC07:13
*** alrs has quit IRC07:14
*** afazekas has joined #openstack-meeting07:14
*** alrs has joined #openstack-meeting07:15
*** mrunge has joined #openstack-meeting07:17
*** danwent has quit IRC07:20
*** psedlak has quit IRC07:28
*** emagana has joined #openstack-meeting07:29
*** cody-somerville has quit IRC07:38
*** zigo has quit IRC07:55
*** spn has quit IRC07:56
*** flaper87 has joined #openstack-meeting07:57
*** zigo has joined #openstack-meeting07:58
*** rafaduran has joined #openstack-meeting07:59
*** spn has joined #openstack-meeting07:59
*** psedlak has joined #openstack-meeting08:02
*** emagana has quit IRC08:11
*** ketan985 has joined #openstack-meeting08:15
*** ketan985 has quit IRC08:17
*** koolhead17 has quit IRC08:35
*** Mandell has quit IRC08:37
*** emagana has joined #openstack-meeting08:37
*** cody-somerville has joined #openstack-meeting08:37
*** cody-somerville has joined #openstack-meeting08:37
*** emagana has quit IRC08:44
*** koolhead17 has joined #openstack-meeting08:48
*** EmilienM has joined #openstack-meeting08:54
*** afazekas has quit IRC08:59
*** jamespage has joined #openstack-meeting09:04
*** jamespage has left #openstack-meeting09:06
*** emagana has joined #openstack-meeting09:11
*** emagana has quit IRC09:21
*** alrs has quit IRC09:24
*** alrs has joined #openstack-meeting09:24
*** davidha has joined #openstack-meeting09:26
*** darraghb has joined #openstack-meeting09:28
*** stevebaker has joined #openstack-meeting09:34
*** mrunge has quit IRC09:36
*** mrunge has joined #openstack-meeting09:40
*** emagana has joined #openstack-meeting09:47
*** mordred has quit IRC09:52
*** jesusaurus has quit IRC09:52
*** mordred has joined #openstack-meeting09:53
*** mestery_ has joined #openstack-meeting09:53
*** jesusaurus has joined #openstack-meeting09:53
*** mestery has quit IRC09:54
*** adjohn has quit IRC09:54
*** emagana has quit IRC09:57
*** jaypipes has quit IRC09:58
*** corrigac has joined #openstack-meeting10:04
*** zul has quit IRC10:05
*** colemanc has quit IRC10:05
*** jaypipes has joined #openstack-meeting10:12
*** derekh has joined #openstack-meeting10:13
*** zul has joined #openstack-meeting10:18
*** emagana has joined #openstack-meeting10:23
*** EmilienM has quit IRC10:25
*** zigo has quit IRC10:26
*** zigo has joined #openstack-meeting10:27
*** emagana has quit IRC10:34
*** koolhead17 has quit IRC10:34
*** vkmc has joined #openstack-meeting10:38
*** adjohn has joined #openstack-meeting10:43
*** koolhead17 has joined #openstack-meeting10:47
*** alexpilotti has joined #openstack-meeting10:48
*** psedlak has quit IRC10:48
*** psedlak has joined #openstack-meeting10:48
*** psedlak has quit IRC10:50
*** psedlak has joined #openstack-meeting10:50
*** psedlak has quit IRC10:51
*** adjohn has quit IRC10:51
*** maurosr has joined #openstack-meeting10:52
*** psedlak has joined #openstack-meeting10:52
*** zigo has quit IRC11:00
*** zigo has joined #openstack-meeting11:00
*** psedlak has quit IRC11:10
*** psedlak has joined #openstack-meeting11:11
*** psedlak_ has joined #openstack-meeting11:27
*** psedlak_ has quit IRC11:32
*** psedlak_ has joined #openstack-meeting11:32
*** afazekas has joined #openstack-meeting11:34
*** dosaboy has quit IRC11:42
*** adjohn has joined #openstack-meeting11:45
*** adjohn has quit IRC11:50
*** dosaboy has joined #openstack-meeting11:51
*** anilkb has joined #openstack-meeting12:03
*** zigo has quit IRC12:11
*** zigo has joined #openstack-meeting12:11
*** anilkb has quit IRC12:16
*** dosaboy has quit IRC12:17
*** emagana has joined #openstack-meeting12:18
*** dosaboy has joined #openstack-meeting12:18
*** emagana has quit IRC12:27
*** annegentle has joined #openstack-meeting12:38
*** markvoelker has joined #openstack-meeting12:43
*** dhellmann has joined #openstack-meeting12:51
*** vkmc has quit IRC12:52
*** annegentle has quit IRC13:01
*** dwcramer has quit IRC13:12
*** adjohn has joined #openstack-meeting13:16
*** martine has joined #openstack-meeting13:20
*** adjohn has quit IRC13:21
*** koolhead17 is now known as koolhead17|afk13:23
*** otherwiseguy has joined #openstack-meeting13:24
*** topol has joined #openstack-meeting13:25
*** psedlak has quit IRC13:27
*** psedlak_ has quit IRC13:27
*** psedlak has joined #openstack-meeting13:28
*** anniec has joined #openstack-meeting13:33
*** dosaboy has quit IRC13:35
*** anniec has quit IRC13:36
*** anniec has joined #openstack-meeting13:36
*** ryanpetrello has joined #openstack-meeting13:42
*** topol has quit IRC13:43
*** anteaya has joined #openstack-meeting13:44
*** dosaboy has joined #openstack-meeting13:51
*** gongysh_ has joined #openstack-meeting13:53
*** gongysh_ has quit IRC13:58
*** dosaboy has quit IRC14:00
*** dosaboy has joined #openstack-meeting14:02
*** joesavak has joined #openstack-meeting14:03
*** dosaboy has quit IRC14:03
*** dosaboy has joined #openstack-meeting14:04
*** dprince has joined #openstack-meeting14:07
*** noslzzp has joined #openstack-meeting14:09
*** emagana has joined #openstack-meeting14:11
*** sandywalsh has joined #openstack-meeting14:12
*** cody-somerville has quit IRC14:14
*** dosaboy has quit IRC14:15
*** sandywalsh_ has joined #openstack-meeting14:16
*** sandywalsh has quit IRC14:17
*** emagana has quit IRC14:24
*** fnaval has quit IRC14:24
*** zigo has quit IRC14:25
*** zigo has joined #openstack-meeting14:25
*** woodspa has joined #openstack-meeting14:27
*** dosaboy has joined #openstack-meeting14:28
*** eharney has joined #openstack-meeting14:28
*** eharney has joined #openstack-meeting14:28
*** cody-somerville has joined #openstack-meeting14:28
*** markmcclain has joined #openstack-meeting14:33
*** dripton_ is now known as dripton14:39
*** mrodden has joined #openstack-meeting14:39
*** adjohn has joined #openstack-meeting14:47
*** galthaus has joined #openstack-meeting14:47
*** emagana has joined #openstack-meeting14:49
*** primeministerp has joined #openstack-meeting14:52
*** adjohn has quit IRC14:52
*** fnaval has joined #openstack-meeting14:58
*** dwcramer has joined #openstack-meeting14:59
*** emagana has quit IRC15:00
*** mtreinish has joined #openstack-meeting15:01
*** same5336_ has joined #openstack-meeting15:04
*** same5336 has quit IRC15:06
*** same5336_ is now known as same533615:06
*** iben has joined #openstack-meeting15:06
*** dolphm has joined #openstack-meeting15:07
*** esker has joined #openstack-meeting15:08
*** markvan has joined #openstack-meeting15:10
*** diogogmt has joined #openstack-meeting15:10
*** topol has joined #openstack-meeting15:16
*** woodspa has quit IRC15:17
*** adjohn has joined #openstack-meeting15:18
*** adjohn has quit IRC15:22
*** dhellmann is now known as dhellmann-afk15:24
*** noslzzp has quit IRC15:24
*** lbragstad has quit IRC15:27
*** woodspa has joined #openstack-meeting15:27
*** emagana has joined #openstack-meeting15:27
*** mestery_ is now known as mestery15:27
*** mattray has joined #openstack-meeting15:31
*** emagana has quit IRC15:31
*** annegentle has joined #openstack-meeting15:33
*** john5223 has joined #openstack-meeting15:34
*** patrocinio has joined #openstack-meeting15:35
*** zigo_ has joined #openstack-meeting15:36
*** ayoung has joined #openstack-meeting15:36
*** zigo has quit IRC15:37
*** psedlak has quit IRC15:43
*** psedlak has joined #openstack-meeting15:44
*** haleyb has left #openstack-meeting15:46
*** metral has joined #openstack-meeting15:46
*** dhellmann-afk is now known as dhellmann15:46
*** lbragstad has joined #openstack-meeting15:47
*** dprince has quit IRC15:48
*** adjohn has joined #openstack-meeting15:49
*** dprince has joined #openstack-meeting15:49
*** luis_fdez has joined #openstack-meeting15:53
*** adjohn has quit IRC15:53
*** Daviey has quit IRC15:54
primeministerp#startmeeting hyper-v15:57
openstackMeeting started Tue Feb  5 15:57:13 2013 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:57
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:57
*** openstack changes topic to " (Meeting topic: hyper-v)"15:57
openstackThe meeting name has been set to 'hyper_v'15:57
primeministerphi everyone15:57
alexpilottihi guys15:57
primeministerpalexpilotti: pedro's not going to make it15:57
primeministerpalexpilotti: although I think we'll be quick today15:57
alexpilottidarn, I had to ask him a few questions15:57
primeministerpalexpilotti: take them up via email pls15:58
primeministerpalexpilotti: he's in meetings15:58
alexpilottivolumes are not getting live migrated15:58
primeministerpalexpilotti o15:58
primeministerpthat's not good15:58
alexpilottiyep. I'm doing it now for clod migration15:58
primeministerpalexpilotti: file a bug15:58
alexpilottiso if he gives me confirmation I can add the to live mifration as well15:59
primeministerpo15:59
primeministerpeven better15:59
primeministerpok reach out via email then15:59
primeministerpplease15:59
primeministerpI wanted to discuss the work on the windows cloudinit bits15:59
alexpilottiso, no problem, I just need to know what his plans were in the "old" Folsom times :-)15:59
alexpilottisure16:00
primeministerpas well as the stuff we did yesterday16:00
primeministerpif you think it's ok16:00
primeministerpfor others to try16:00
*** same5336 has quit IRC16:01
*** same5336 has joined #openstack-meeting16:01
primeministerpalexpilotti: care to discuss the new cloudinit bits?16:01
alexpilottisure16:01
alexpilottiso what we have now is:16:02
alexpilottisupport for all the WIndows OS currently supported by MS:16:02
primeministerp+116:02
alexpilotti2003, 2003 R2, 2008, 2008 R2, 201216:02
*** s3u has joined #openstack-meeting16:02
alexpilottiboth x86 and x6416:02
*** patrocinio has left #openstack-meeting16:03
alexpilottiand also the workstation OSs for VDIs: vista, 7 and 816:03
*** iben-mobile has joined #openstack-meeting16:03
ibennice!16:03
alexpilottiI have to admit that we didn't bother to test on Vista :-D16:03
ibenno one cares about vista16:03
alexpilottibut it has the same kernel as 200816:03
alexpilottithat's my point as well ;-)16:04
ibeni don't know of any companies using vista16:04
primeministerpalexpilotti: did you complete the rest of the cloudinit integration of the unattend.xml?16:04
primeministerp.. and sysprep etc16:04
alexpilottiI have to add cloud init16:04
primeministerpalexpilotti: are you going to use a rapper to dl it16:04
alexpilottito recap that feature, as iben might be interested16:04
primeministerpalexpilotti: i.e. you can always do it in multiple post exec scripts16:04
primeministerpo yes16:05
primeministerpiben: so alexpilotti and I did some work on a unattend16:05
alexpilottiwe put together an unattended.xml to create a KVM Windows image16:05
alexpilottiwith "no hands"16:05
ibenok16:05
primeministerp*nod*16:05
primeministerpit could be used to create any image16:06
alexpilottithis is due to the need to select Virtio drivers during setup, adding drivers for network later etc16:06
primeministerpit just also slipstreams the drivers in16:06
*** iben-mobile has quit IRC16:06
*** iben-mobile has joined #openstack-meeting16:06
alexpilottiI wanted a solution to simplify it as much as possible16:06
*** Daviey has joined #openstack-meeting16:06
alexpilottias unfortunately we cannot provide Windows Glance images for doenload16:06
alexpilottidu to licensing16:06
alexpilotti*due16:06
primeministerpbut we can provide really easy ways to build them16:06
primeministerp;)16:06
ibenyes - the documentation will be key16:07
alexpilottiyep :-)16:07
ibenI can help with that16:07
primeministerpiben: perfect16:07
alexpilotticool16:07
alexpilottiok, the next feature in cloudinit is the set password16:07
primeministerpalexpilotti: i also merged the kvm drivers into my pxe bits16:07
primeministerpalexpilotti: fwiw16:07
alexpilottithere's a new feature in Grizzly16:08
alexpilottito set the password in Windows and get it from nova client16:08
*** bdpayne has joined #openstack-meeting16:08
alexpilottiit is encrypted w the SSH public key beloging to the keypair assigned to the VM16:09
alexpilottiand is decrypted with the corresponding private key16:09
alexpilottiso now, to get a VM password the user needs simply to do a:16:09
alexpilottinova get-password vm1 ./ssh/id_rsa16:09
alexpilotti(for example)16:09
alexpilottiit's a pefectly secure way of handling the password issue16:10
primeministerpnice16:10
alexpilottiWindows cloud-init does the main work16:10
alexpilotti1) getting the SSH key from teh metadata16:11
alexpilotti2) extracting the RSA key (we don't have openssh on Windows)16:11
alexpilotti3) generating a random password16:11
*** cp16net is now known as cp16net|away16:11
alexpilotti4) encrypting16:11
alexpilotti5) posting the encrypted data to the metadata service16:12
alexpilotti6) creating / updating the user with the given password16:12
alexpilottiat this point any client can get the password, by simply providing the private key16:12
primeministerpalexpilotti: great job16:13
ibenalexpilotti: what user id is being set with this process?  Is it just one or can many users be setup using this method?16:13
primeministerpalexpilotti: local admin correct?16:13
alexpilottione user, the user name is set in the cloud-init configuration16:13
ibenand does the user need to exist in the initial image or can users be created?16:13
alexpilottilet me fetch you a snapshot16:13
primeministerpeven better16:13
alexpilottiiben: no, the servcei checks if the user exists and creates it as needed16:14
ibenokay16:14
ibenthanks!16:14
ibenplease cover this in the release notes as I'm sure we will get asked this many times...16:14
alexpilottialso, the user is added to a set of local groups provided in the configuration16:14
alexpilottitipically "administrators"16:14
ibenexcellent16:14
ibenmost enterprises have changed away from the defaults16:15
alexpilottiiben: second snapshot here: http://www.cloudbase.it/cloud-init-for-windows-instances/16:15
primeministerpiben: have you tried alessandro's installers?16:15
primeministerpyet16:15
ibenso local admin would not be "administrator"16:15
alexpilottiiben: you can set "administrators" if you prefer16:15
ibenprimeministerp: we are usign them in our lab16:15
primeministerpiben: great16:15
alexpilottifor security reasons, as you said companies prefer to avoid it16:16
*** dprince has quit IRC16:16
primeministerpiben: how is that going16:16
ibenso far so good - we are verifying the configuration of the various OS support16:16
ibenoriginally w2k3 was not working16:16
*** noslzzp has joined #openstack-meeting16:16
ibenbut I think we moved past that - right alexpilotti?16:16
alexpilottiiben: tep, I wrote Chris about it16:16
primeministerpiben: and hyper-v?16:17
ibenalexpilotti has been a great resource - kudos!!!16:17
alexpilottiiben: do you know if he managed to test it?16:17
ibenso far all this is on Ubuntu KVM16:17
alexpilottiiben: tx! :-)16:17
ibenand Essex16:17
primeministerpiben: gotcha16:17
ibenwe will be moving to folsom eventually16:17
ibenand we have yet to discuss licenses16:17
*** danwent has joined #openstack-meeting16:17
ibenthat may impact out hypervisor choice16:18
alexpilottiprimeministerp: we keep on getting requests for Essex, we might think about supporting it16:18
primeministerpalexpilotti: we can't16:18
primeministerpfrom a hyper-v perspective16:18
primeministerpw/ the main codebase16:18
alexpilottiiben: Hyper-V is free :-)16:18
primeministerpalexpilotti: kind of16:18
alexpilottiprimeministerp: only for Cloud-init16:18
primeministerpalexpilotti: only for not running windows16:18
ibenwell - if a company owns many MS windows licenses16:18
ibenthey can license the hyper-v16:18
primeministerpalexpilotti: o gotcha16:18
ibenand save on the guest VM license cost16:18
primeministerpalexpilotti: then definatley16:18
ibenother wise16:19
primeministerpalexpilotti: we should support essex w/ the cloudinit bits16:19
alexpilottiiben: what we, do is using SPLA licenses16:19
ibenwe can use a free hypervisor16:19
ibenand then we need to license each guest vm instance16:19
alexpilottiiben: we use Windows Server SPLA licenses16:19
alexpilottidatacenter edition16:19
primeministerpiben: only windows guests16:19
ibenokay - we will look into this16:19
alexpilottithey retail around 70 USD / month / socket16:19
alexpilottiunlimited virtualization rights16:20
primeministerpalexpilotti: but that's licensed on datacenter16:20
alexpilottiso with 2 sockets and ca 50-70 VMs per host16:20
primeministerpalexpilotti: not at the vm layer16:20
alexpilottithat's the point16:20
primeministerpalexpilotti: i.e. you're using windows server vs hyper-v server16:20
alexpilottiyou end up paying 1-2 USD / month per guest :-)16:20
primeministerpalexpilotti: datacenter16:20
*** Gordonz has joined #openstack-meeting16:21
alexpilottiit's independent from the host (Hypervisor) OS16:21
alexpilottiso you can use Hyper-V / KVM / ESXi / Xen etc16:21
alexpilottithe same license includes also the host license16:22
primeministerpalexpilotti: and you're sure that's cheaper than licensing the spla datacenter/core w/ hyper-v16:22
ibenthis brings up a new topic to put on our agenda for discussion later on - I'd like to propose a talk for the portland summit in april about the work I'm doing with you guys.16:22
*** noslzzp has quit IRC16:22
primeministerpalexpilotti: honestly I have  no idea16:22
alexpilottiyou don't license hyper-v!16:22
primeministerpalexpilotti: i know you don''t16:22
ibeni will research all this stuff and present the "official" story16:22
primeministerpalexpilotti: but you license the windows server core it need s to run on16:22
*** hemna has joined #openstack-meeting16:23
primeministerpi.e. for unlimited guests16:23
ibenif you work for Microsoft then you probably don't worry too much about licensing16:23
alexpilottiwhy do you need to license a windows erver core??16:23
primeministerpiben: and I work on open source16:23
primeministerpiben: so i care even less16:23
primeministerp;)16:23
alexpilottilol16:23
primeministerplicensing16:23
primeministerper about licensing16:23
ibenand same thing goes for a lot of the really big enterprises with thousands of licenses and a KPL server16:23
primeministerpyes16:23
alexpilottiwhat about moving this topic to the hyper-V channel after the meeting? :-)16:23
primeministerpthat's the problem16:23
primeministerpthat's infe16:24
primeministerper fine16:24
primeministerp#topic resize16:24
*** openstack changes topic to "resize (Meeting topic: hyper-v)"16:24
ibenwhen we bring servers or workstations on line they get licenses from the active directory domain automatically and it's someone elses issue to make sure we're in compliance16:24
primeministerpiben: that's how most places seem to work16:24
primeministerp;)16:24
primeministerpalexpilotti: move onto resize16:25
primeministerpalexpilotti: did we agree that vhdx is for I16:25
*** colinmcnamara has joined #openstack-meeting16:25
alexpilottiprimeministerp: sure, here we go16:26
alexpilottiso resize is going on very well, I should be able to finish it in 2-3 days16:26
alexpilottiI had most of the code from the Folsom times16:27
primeministerpalexpilotti: yes I remember16:27
alexpilottiI'm thinking about fitting even the "rescue" feature in G16:27
alexpilottiif we finish everything16:27
primeministerpalexpilotti: and vhdx, is that for I16:27
alexpilottibut before that I'd like to squeeze in NVGRE on Quantum16:28
primeministerpi would like to see that16:28
primeministerpas well16:28
alexpilottiyes, VHDX requires WMI V2, which is scheduled for I16:28
primeministerpok perfect want to make sure I account for that in our list16:28
alexpilottithanks to the huge refactoring we did last week, it's now way easier to do it16:28
alexpilottibut not in 2 weeks ;-)16:28
primeministerp*nod*16:28
ibenso for us noobs - what is "I"16:29
primeministerpthe release after H16:29
ibenwow - that's far out16:29
alexpilottisorry guys!16:29
primeministerpiben: i actually meant h16:29
primeministerpnot i16:29
alexpilottiI meant "H"16:29
alexpilottiall that stuff is for Havana16:29
primeministerpalexpilotti: yes16:30
primeministerpalexpilotti: my slip too16:30
primeministerpalexpilotti: it's the damn fiscal cycle16:30
primeministerpalexpilotti: throws me off16:30
alexpilottiwe are too used to think 1 version ahead :-)16:30
primeministerpok16:30
primeministerp#ci progress16:30
ibenthat's good - there's no mention of "I" anywhere here.. http://wiki.openstack.org/ReleaseNaming16:31
primeministerp#topic ci progress16:31
*** openstack changes topic to "ci progress (Meeting topic: hyper-v)"16:31
alexpilottiociuhandu: is having some amazing progress on CI16:31
primeministerpiben: thats why we call it i16:31
primeministerpalexpilotti: good, we needed to catch up16:31
alexpilottiI saw a full puppetized controller running here today ;-)16:31
primeministerpociuhandu: did you finish the network controller bits?16:31
ociuhanduprimeministerp: the controller is working with all the bits16:31
*** noslzzp has joined #openstack-meeting16:32
primeministerpociuhandu: network and compute?16:32
ociuhandunot the config, i went back to the main controller to fix the keystone ssl issues16:32
primeministerpociuhandu: so we still have ssl issues16:32
ociuhanduno, it's fixed16:32
primeministerpo16:32
primeministerpyou fixed it?16:32
primeministerpgreat16:32
ociuhanduprimeministerp: the "main controller" is deploying fine16:32
*** anniec has quit IRC16:32
primeministerpI'll run one out of pxe today16:32
ociuhanduwith all configs16:33
ociuhanduprimeministerp: the only bit left is the enter required during the pxe on LVM16:33
primeministerpociuhandu: there isn't one16:33
primeministerpociuhandu: ;)16:33
primeministerpociuhandu: we might have to rebuild the preseed clean16:33
ociuhanduthere is, i deployed 3-4 ubuntu machines in the last 2 days and it's the same16:33
*** iben-mobile has quit IRC16:34
primeministerpociuhandu: I'll check it, but I have no prompts16:34
*** iben-mobile has joined #openstack-meeting16:34
ociuhanduprimeministerp: did you check the order in the preseed? i think i sent you some info16:34
primeministerpociuhandu: is the disk dropping out?16:34
ociuhanduprimeministerp: they were saying that the default order is not right (for the options in the preseed)16:35
ociuhanduprimeministerp: no, it just does not take the confirmation to write the LVM config16:35
primeministerpociuhandu: let's talk after and I'l lcheck16:35
primeministerpociuhandu: like i said16:35
primeministerpociuhandu: we might just need puppet to rebuild that file16:35
ociuhanduprimeministerp: sure16:35
primeministerpociuhandu: but I have no prompts on preseeds16:35
primeministerpduring lvm creatoin16:35
primeministerpwhen I run it16:35
*** otherwiseguy has quit IRC16:35
ociuhanduprimeministerp: network controller is deploying, installing from git the quantum but the config is not finished templating16:36
primeministerpociuhandu: ok good16:36
primeministerpociuhandu: on my side16:36
primeministerpociuhandu: i have the windows iso's automounting16:36
ociuhanduprimeministerp: once we also have the windows bits we can also test the compute, as the puppet part ofr that should be done already16:36
primeministerphowever we still have to put it onto the system manually16:36
primeministerpociuhandu: yes16:37
ociuhanduprimeministerp: great16:37
primeministerpociuhandu: that's my goal16:37
primeministerpociuhandu: I ended up using a defines16:37
primeministerpociuhandu: bc we need to know the iso name16:37
primeministerpociuhandu: I'm going to generate all the scripts for launching the unatted.xml install from there16:38
primeministerpociuhandu: also for time sake I may skip the part we discussed the other day16:38
primeministerpociuhandu: as I have to still tweak the startnet.cmd16:38
ociuhanduprimeministerp: i think i also got the direction for identifying the machines from puppet through puppetdb16:39
primeministerpociuhandu: good16:39
primeministerpociuhandu: let's touch base after this16:39
ociuhanduprimeministerp: e.g. getting the ips of all machines having a certain module deployed16:39
ociuhanduprimeministerp: sure16:39
primeministerp#general discussion16:39
primeministerpgah16:39
primeministerp#topic general discussion16:40
*** openstack changes topic to "general discussion (Meeting topic: hyper-v)"16:40
primeministerpso anyone have anything else to dadd16:40
primeministerper add16:40
primeministerpo16:40
primeministerpbtw luis_fdez thanks helping w/ testing the cloudinit bits16:40
*** bencherian has joined #openstack-meeting16:40
ibenI'd like to propose a talk for the portland summit in april about the work I'm doing with you guys.16:40
luis_fdezprimeministerp: :)16:40
ibenis anyone else here planning any talks?16:41
primeministerpiben: we were going to have talk16:41
ibenwant to make sure we don't overlap16:41
primeministerpre: the new features16:41
ibenand there is some strategic direction16:41
primeministerpand work that was done16:41
alexpilottiiben: when do you plan to move to Folsom?16:41
primeministerpalso I know alessandro was going to have an additional discussion on cloud init16:41
ibenso - I am an advisor helping many companies with cloud technology16:41
ibenone of my larger customers is using essex now16:42
*** hanrahat has joined #openstack-meeting16:42
ibenwhen folsom is released (is it production yet?) they will start setting up new clusters with it16:42
primeministerpiben: folsom was already released16:43
ibeni don't think there's a clean upgrade path to take 2000 Ubuntu servers in production with 10,000 virtual machines and just upgrade it16:43
ibenI'm not sure on that though16:43
primeministerpI would agree16:43
primeministerpthere might be some challenge16:43
*** jaypipes has quit IRC16:43
ibenso as new racks come on line we can setup this new code16:44
ibenbut there is the large legacy installation to account for16:44
*** dhellmann has quit IRC16:44
primeministerpiben: gotcha16:44
ibenYahoo is also setting up a 20,000 redhat based openstack - pretty sure they will use folsom16:44
*** otherwiseguy has joined #openstack-meeting16:44
ibenand they will want to run windows vms on there too16:44
primeministerpiben: which specific part do you want to speak about at the conference?16:45
ibenthe challanges of getting traditional corp workloads onto openstack16:45
primeministerpiben: perfect16:45
ibennetworking16:45
ibenlicensing16:45
ibencloudbaseinit16:45
ibensort of an overview with pointers16:46
ibenfrom the trenches with a been there done that perspective16:46
primeministerpiben: sure16:46
primeministerpiben: sounds good16:46
ibenspecifically enterprise focused16:47
ibena lot of openstack work is targeted towards devops - which is fine16:47
ibenbut we sometimes leave out the bread and butter of the enterprise apps16:47
alexpilottiiben, primeministerp: would you like to setup a meeting on Skype on those 3 topics?16:48
ibeni didn't even know it was possible until we started talking here with you guys16:48
primeministerpalexpilotti: that's a great ide16:48
primeministerper idea16:48
alexpilotti(networking, licenseing cloudbase-init)16:48
ibenso it's great news and we need to help spread the word!16:48
*** jaypipes has joined #openstack-meeting16:48
primeministerpiben: sounds good16:48
primeministerpiben: let's schedule a skype to discuss more16:48
hanrahatprimeministerp: please include me in that meeting16:48
ibenexcellent!16:48
primeministerphanrahat: sure thing16:49
*** adjohn has joined #openstack-meeting16:49
ibenswitching to skype16:49
*** adjohn has quit IRC16:49
primeministerpiben: would you mind starting that thread w/ your avilability16:49
primeministerpok16:50
primeministerpanything else?16:50
ibennot at all16:50
primeministerpluis_fdez: anything to add?16:50
luis_fdeznothing primeministerp, by CERN side I've been working on image creation and specific cern stuff...16:50
ibenhave you had good success to create images?16:51
ibenluis_fdez16:51
primeministerpok guys i'm closing the meeting16:51
ibenok16:51
primeministerpluis_fdez: iben #openstack-hyper-v?16:51
primeministerp#endmeeting16:51
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:51
openstackMeeting ended Tue Feb  5 16:51:51 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
luis_fdeziben: yep, we're managing to create them throug Oz and some custom scripts to connect to glance16:51
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-02-05-15.57.html16:51
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-02-05-15.57.txt16:51
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-02-05-15.57.log.html16:51
*** iben-mobile has quit IRC16:52
*** iben-mobile has joined #openstack-meeting16:52
luis_fdezprimeministerp, iben sorry but I have to go... tomorrow I'll join openstack-hyper-v16:52
ibenokay16:52
ibenbye16:52
*** dhellmann has joined #openstack-meeting16:53
*** luis_fdez has quit IRC16:53
alexpilottibye!16:53
ociuhandubye!16:54
*** garyk has quit IRC16:54
*** glenc has joined #openstack-meeting16:59
*** anniec has joined #openstack-meeting16:59
*** gyee has joined #openstack-meeting17:00
*** glenc_ has quit IRC17:01
*** noslzzp has quit IRC17:03
*** s3u has quit IRC17:04
*** anniec has quit IRC17:07
*** anniec_ has joined #openstack-meeting17:07
*** rafaduran has left #openstack-meeting17:08
*** gyee has quit IRC17:11
*** koolhead17|afk is now known as koolhead1717:13
*** gyee has joined #openstack-meeting17:17
*** adjohn has joined #openstack-meeting17:20
*** markwash has joined #openstack-meeting17:25
*** adjohn has quit IRC17:25
*** iben-mobile has quit IRC17:27
*** iben-mobile has joined #openstack-meeting17:27
*** iben-mobile has quit IRC17:29
*** iben-mobile has joined #openstack-meeting17:30
*** zul has quit IRC17:32
*** lloydde has joined #openstack-meeting17:36
*** mrodden1 has joined #openstack-meeting17:38
*** zul has joined #openstack-meeting17:38
*** mrodden1 has quit IRC17:39
*** zul has quit IRC17:39
*** bencherian has quit IRC17:39
*** metral_ has joined #openstack-meeting17:40
*** zul has joined #openstack-meeting17:40
*** mrodden has quit IRC17:40
*** metral has quit IRC17:44
*** metral_ is now known as metral17:44
*** derekh has quit IRC17:47
*** kwss has joined #openstack-meeting17:51
*** adjohn has joined #openstack-meeting17:51
*** dwaite has joined #openstack-meeting17:53
*** mrodden has joined #openstack-meeting17:54
*** bencherian has joined #openstack-meeting17:54
*** adjohn has quit IRC17:55
*** sleepsonthefloor has joined #openstack-meeting17:56
*** metral has quit IRC17:58
ayoungKey, Key, Key!17:59
ayoungKEYSTONE!17:59
topolHi17:59
*** andreaf has quit IRC17:59
*** brich has joined #openstack-meeting17:59
joesavakhiya17:59
*** henrynash has joined #openstack-meeting17:59
dolphmo/18:00
gyee\o18:00
*** heckj has joined #openstack-meeting18:00
henrynashhi18:00
dolphmheckj was here last week, right?18:00
henrynashyep18:00
heckjmorning!18:00
topolI believe he was18:00
heckj#startmeeting keystone18:00
openstackMeeting started Tue Feb  5 18:00:48 2013 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
dolphmyay!18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: keystone)"18:00
henrynashand is!18:00
openstackThe meeting name has been set to 'keystone'18:00
*** adjohn has joined #openstack-meeting18:00
*** nati_ueno has joined #openstack-meeting18:00
heckjWhassup dolph?18:00
dolphmheckj: not much, belatd welcome back18:01
dolphmbelated*18:01
heckjheh - closer to surface now - it's not dark anymore :-)18:01
joesavakbleated?18:01
heckjdolphm: missed out on last week's keystone meeting18:01
*** anniec_ has quit IRC18:01
ayoung#link http://wiki.openstack.org/Meetings/KeystoneMeeting18:02
heckjOkay - looking over the agenda18:02
ayoungI see we haven;t updated since last week18:02
heckjBTW: I've got to keep things short on my side today - will get heavily distracted in about 30 minutes as I'm trying to run two meetings at once18:02
*** dwchadwick has joined #openstack-meeting18:03
heckj#topic Hot, Burning Issues of Love?18:03
*** openstack changes topic to "Hot, Burning Issues of Love? (Meeting topic: keystone)"18:03
*** anniec has joined #openstack-meeting18:03
topolI have friends who play online poker and play 10 tables simultaneously. You can handle 2 meetings18:03
ayoungtopol, they play with their money, not with mine18:03
heckjanything in the frying pan this week?18:03
heckjcritical reviews pending, etc?18:03
ayounggyee's work on V3 Token is probably most critical18:04
*** stevemar has joined #openstack-meeting18:04
henrynashheckj: so we need the auth review done18:04
henrynashayoung: +118:04
gyeeyou guys OK with the spec now?18:04
henrynashgyee: you saw my comment on the unstopped token bit…..18:04
ayounghenrynash, can you link18:04
gyeehenrynash, I am still uncomfortable with the concept of private namespace18:05
joesavak+1 gyee18:05
gyeestill get wrap my head around on how does it work in conjunction with public namespaces?18:05
heckjdolphm: I think most of the holdout last week was related to commentary related to multifactor and token structures, which I think mostly got resolved with a general agreement to leave it open and assert extra keys should be ignored. This jive with you?18:05
gyeestill can't18:05
henrynashhttps://review.openstack.org/#/c/20524/15/openstack-identity-api/src/markdown/identity-api-v3.md18:05
dolphmseeing the impact of private namespaces on openstackclient makes me sad18:05
ayoungheckj, it jives with me18:06
henrynashdolphm: ?18:06
stevemarme too18:06
gyeeI think we need more impact on the private namespace18:06
gyeeimpact study18:06
ayoungcan private namespaces be implemented later, or do they need to be designed in up front>18:06
ayoung?18:06
gyeeI still think we either going to have namspace for all or nothing18:06
henrynashgyee: I guess my concerns is we had this debate, approved the blueprint18:07
dolphmheckj: sure18:07
gyeeI am OK with namespace, just not *private* namespace18:07
dolphmtbh, when i +2'd the spec, i didn't expect it to merge so fast -- i was just happy with the way it was written... i probably should have +1'd18:07
henrynashgyee: there is very little code change that that would cause…..but of course it would be a hard on/off18:07
dolphmif it's a feature we can't fully deliver in the next 10 days, we need to cut it from the spec, and put it back for v3.118:08
*** sarob has joined #openstack-meeting18:08
heckjgyee or henrynash: can one of you summarize how namespace is impacting the spec and the choice that needs to be made there?18:08
henrynashdolphm:: we can definitely deliver it18:08
*** markmcclain has quit IRC18:08
*** sarob has joined #openstack-meeting18:08
henrynashheckj:  There are two spec changes:18:08
*** nachi has joined #openstack-meeting18:08
*** nachi_ has joined #openstack-meeting18:08
gyeeI am half way there with the auth impl18:09
henrynash1) Specifiy domain in auth when usernaem is specified18:09
*** dprince has joined #openstack-meeting18:09
gyeetooks 2 days, at this way, I should have a wip review in the next 2 days :)18:09
*** bencherian has quit IRC18:09
dolphmdiscussion on impact to openstackclient: https://review.openstack.org/#/c/20854/4/openstackclient/identity/v3/credential.py18:09
henrynash…as well as domain alongside for project scope/default  to ensure these are unique….all in auth or scoping18:10
*** nachi_ has joined #openstack-meeting18:11
henrynashdolphm: do you think there is an issue there  in terms of adding the filtering?18:11
gyeethe idea that we have to retrieve the user's domain in order to figure out the namespace is not very performance friendly18:11
*** dwchadwick has quit IRC18:12
dolphmhenrynash: adding ?domain_id= to GET /users and GET /projects?18:12
henrynashdolphm: yes18:12
dolphmhenrynash: not at all18:12
henrynashgyee: sure. but we do this how often?18:13
*** dwchadwick has joined #openstack-meeting18:13
gyeehenrynash, can you update the doc on how does private domain work in conjunction with public domain?18:14
henrynashgyee: you mean 'default' domain?18:14
gyeenot just default18:14
*** Mandell has joined #openstack-meeting18:15
henrynashgyee: not quite with you….what do you mean by public domain?  Any domain, not private?18:15
gyeesay I have user jdoe in default/public domain, and I want to create a user jdoe in a private domain XYZ18:15
*** lcheng has joined #openstack-meeting18:15
joesavakso, private domain = private namespace, allows usernames to be unique for that domain instead system wide. If not used, then users get a default (public) domain and domain isn't required for authN?18:15
gyeehow does that work?18:15
henrynashjoesavak: yes18:16
gyeeand how does it impact other OS services?18:16
joesavaki like the flexibility18:16
dolphmgyee: dashboard is the (only?) impact i'm aware of -- users in a privately namespaced domain can't login18:16
henrynashgyee: so the only real potential is swift, and looking at the with auth code, there might actually be no changes (still being checked - if there are they are minor)18:17
henrynashswift containers seem fine18:17
henrynashswift ACL has legacy code that checks tenantID as well as useranme, so that *might* can no changes….18:17
joesavakdashboard will need to do something like <domainid>.horizon.com and send in domain id with the user/pass for authN if configured in the OS deployment18:17
henrynashjoesavak: yes18:18
dwchadwickcan anyone give the rationale for why user names and project names can be locally defined in a domain but role names cannot be. Seems illogical to me18:18
*** otherwiseguy has quit IRC18:18
*** Haneef has joined #openstack-meeting18:18
henrynashdwchadwick: it is a artefact that today the role names are shared identifiers between all services and keystone18:19
dolphmdwchadwick: we need to have domain-specific policy first18:19
ayoungdwchadwick, as of now, policy is specificied at a service level,  so private roles would be meaningless18:19
*** vipul is now known as vipul|away18:19
joesavakwe need policies tied to explicit capabilities to enable private roles.18:20
*** davidha has quit IRC18:20
dwchadwickbut if you have service wide policy, how can that work with domain specific user names and not with domain specific role names18:20
heckjgyee: reading through this, there's some impact on other services for a private domain concept with V3 auth impl (not suprising), and the argument against so far that I've caught is that it's not performant, and we'll need to be clear about expectations for interop when using and not using domains. Does that summarize your concerns?18:21
henrynashgyee: I understand the desire to have  a hard switch on namespace….but since there wold be very little code change that this saves, I think the flexibility we get from the current spec, outweighs any gain18:21
dolphmdwchadwick: policy files have no concern for user names18:21
gyeeheckj, that sounds right18:21
heckjdwchadwick: let's keep this to one topic at a time please - fine to bring that up later, but let's sort out the current spec disagreement18:21
ayoungpolicy does not care about user names.  Policy as it is currently makes decisions based on roles and tenants.18:21
henrynashheck, gyee: I'm not sure about the performant bit…this is for auth when we need to do the look up, not  each token check?18:22
gyeelater when we give it a full go on namespace, then what's the advantage of private domain?18:22
dolphmhenrynash: it's the client-side code impact that seems much larger18:22
dwchadwickbut tenants (now projects) can be domain specific18:22
ayoungcan someone please define (or link to a definition of) a private namespace?18:23
gyeeproblem with private domain, is that from now on, given a name, I have to do a looking on the domain18:23
gyeelookup18:23
heckjjoesavak relayed this earlier, which I thought covered it: so, private domain = private namespace, allows usernames to be unique for that domain instead system wide. If not used, then users get a default (public) domain and domain isn't required for authN?18:23
henrynashayoung: so the spec is probably the best: https://review.openstack.org/#/c/18805/18:23
dolphmayoung: you approved the review lol18:23
dwchadwickunless the domain name is always provided, or in its absence you can assume default18:23
dwchadwickthen all names can be local to the domain18:24
henrynashheckj: yep, it's really that simple":  names are private to that domain or they are not18:24
*** bencherian has joined #openstack-meeting18:24
ayoungdolphm, yeah, but I think that it might mean differently from I origianlly interpreted it18:24
gyeeits not just default domain18:24
gyeesay if I have 3 public domains and 1 private domain18:25
ayoung#link https://docs.google.com/document/d/1c6Tvr_zRMOP2mJCQN9lrfJjxGaXAExXiFlwMDvmXbl4/edit18:25
gyeename is globally unique across all the public domains18:25
henrynashgyee: so today, names are global across all domains18:25
gyeethis is confusing just to describe it18:25
*** dprince has quit IRC18:25
dolphmi'm lost on how the default domain has any impact on public/private namespacing?18:26
dwchadwickIts not confusing if you get a nice description written up somewhere18:26
gyeedolphm, for a given name, I don't know if its globally unique till I lookup its domain18:26
henrynashgyee: that stays true expect for and names that are in a domain that was created with the "private" flag set….in which cases those names are in their own private name sapce18:26
joesavakthink of public domain as a single default domain (only one can exist) and it is basically the absence of a private domain18:26
henrynashgyee: well, that's how it is today!18:26
ayoungOK...so a "private" namespace is a namespace.  THe private does not imply privacy concerns, but rather a way to divide uniqueness between two realms, so usernames and tenant names can be reused, correct?18:27
dolphm1) user names share a single namespace across all publicly namespaced domains, 2) project names share a single namespace across all publicly namespaced domains, 3) user names have their own namespace within a privately namespaced domain, 4) project names have their own namespace within a privately namespaced domain18:27
heckjhenrynash, gyee: I'm missing the distinction between public and private domains - hven't seen an identifier to assert which it is. I've been under the impression that if there *is* a domain at all, it's a "private" domain in the curren conversation. Is there a disinction there I'm missing18:27
dolphmayoung: yes18:27
dwchadwickwhen you create a domain there is a public/private flag18:28
dolphmayoung: meaning that a username or project name without a domain for context *may* be ambiguous, but you're forced to check for it in the public namespace because you don't know which private namespace to look in18:28
heckjdwchadwick: ah, thank you - missed that.18:28
henrynashheckj: on domain create, you can specify pivate_user_names and/or private_project _names true/false18:28
henrynashheckj: default is false - i.e the current situation18:28
dwchadwickand you should also be able to specify public/private role names as well ;-)18:29
*** mrmartin has joined #openstack-meeting18:29
henrynashdwchadwick: another battle, not this one :-)18:29
Haneef Can't we simply make names scoped to domain?18:29
heckjheh, just can't keep a good academic down, can you18:29
stevemardwchadwick: i agree18:29
*** cp16net|away is now known as cp16net18:30
dwchadwickits all part of the same battle. Having a clean model that is consistent and understandable rather than adhoc18:30
gyeewhat battle? :)18:30
gyeesee how confusing this thing is?18:30
dwchadwickthe battle over the v3 API ;-)18:30
dolphmdwchadwick: unfortunately we don't start with a blank slate for every release18:30
*** vkmc has joined #openstack-meeting18:31
gyeewe either going to have namspace or we don't, much easier to understand18:31
joesavakhaneef - i think the way henrynash did it allows for an easier transition from v2 to v3. As discussed earlier there are ripple effects when domainId is required for authN in addition to user/pass. If v3 impl provided an easy way to transition from user-unique across all domains to user-unique to a domain it will help adoption18:31
heckjhenrynash, gyee - frankly, the distinction seems needlessly complex and simply a means of enabling a break in the uniqeness rules that we currently are living under. I think (maybe this is what gyee was arguing) that we would be better making usernames specific/unique to domains from the very start - revising what we're doing today18:31
dwchadwickbut adding more spaghetti to the plate makes it more difficult to untangle in the long run18:31
gyeeheckj, amen brother!18:31
gyeeI am NOT against namespace, I am against *private* namespace18:32
heckjso as a compromise here, let me suggest the following:18:32
dwchadwickgyee - what is the difference?18:32
heckjwe change our asserting that user names need to be globally unique, and instead only enforce uniqueness to a domain18:32
heckjwe remove the concept of public vs. priviate domains altogether18:32
dwchadwickall namespaces are private until make global18:32
ayoungdwchadwick, yes18:33
Haneefheckj , totally agree. Don't need to write so many pages in document to explain private/public  domain in docs. Simply make it domain scope18:33
ayoungI agree "all namespaces are private until make global"18:33
*** anniec has quit IRC18:33
ayoungbut...you should be able to run that backwards18:33
heckjwe make additional implementation notes in the spec asserting that there is a concept of a default domain, and if a domain isn't specified in auth, that auth is assume to go against the default domain18:33
dolphmayoung: "backwards"?18:33
ayoungit should be possible to split a global namespace into multiple private ones down the road18:33
ayoungif the pool is globally unique to start18:33
dolphmheckj: you can't make a private namespace public -- there will be collisions with the existing public namespace18:34
joesavakdefault domain will help v3 adoption18:34
ayoungyou should be able to split that into multiple pools of names where the  names start to overlap18:34
*** arunkant has joined #openstack-meeting18:34
ayoungthere should be a default domain.  THat is the domain for all users.  THe problem is on how to split it up after wards18:34
ayoungif you l;ook at the DNS syustem, they are split on dots18:34
ayoungldap splits on the whole cn=<value>, comma18:35
*** darraghb has quit IRC18:35
ayoungand so if some people are doing username with email addresses, and you start splitting on domain name, now people that were in the same domain are split into different18:35
ayoungayoung@redhat.com would be partitioned into a different domain than admiyo@yahoo.com, even though they are both MY email addresses.  This is the process we need to keep in mind18:36
henrynashheckj:  so I am am absolutely fine with this approach…and indeed I started there! The thing we are really saying is that the use of domains will really be for enterprises that want to have their own namespace and won't accept restrictions of clashing with others18:36
ayoungSo...we start with Folsom18:36
dwchadwickthe concept is simple. You take your own private name and prefix or suffix with your name (i.e. name of parent) to turn it into a global name18:36
ayoungand the V2 API.  And we specify how things will grow into the V3 API18:36
Haneefto support v2, can't we create a predefined v2 domain and move all the users to it.18:36
joesavakHaneef, +118:36
henrynashwe have the v2 thing coverered18:36
gyeeheckj, I am fine with your proposal18:36
gyeehave namespace applicable to all18:37
*** reed has joined #openstack-meeting18:37
ayoungLets call it DOM0 just to confuse the Xen guys!18:37
dolphmHaneef: we already did that18:37
henrynashwhen you upgrade from F->G, all users and projects end up in the default domain and v2 and v3 clients will find them fine18:37
joesavaksweet18:37
*** vipul|away is now known as vipul18:37
HaneefSo we don't even need to worry about default domain, for v2 users, it is v2 domain, and v3 , they are going to create a new domain or use existing one18:38
ayoungdwchadwick, "the concept is simple. You take your own private name and prefix or suffix with your name (i.e. name of parent) to turn it into a global name"  that leads to things liike Kerberos tickets:  ayoung@example.com@EXAMPLE.COM18:38
ayoungBNotice the double @ incase I didn't make it clear enough18:38
psedlakwith current proposal - user in private namespace will never be able to access diferent domains/project meanwhile user in global name space can get this acces and that could be problem in just private namespaces (possible name-clash) - right?18:39
gyeeayoung, that looks like my email@EMAIL18:39
dwchadwickyes exactly. As the world grows and domains merge then you need to add another level to the name18:39
henrynashhaneef: better than that, domain is optional in v3, so if the cloud provider want to run in "folsom" mode, the just never specify a domain on any entity and it all ends up in one big default domain with folsom semantcis18:39
ayoungSince we have not ruled out any characters in usernames, we can't specify a means to concatinate  username and domain in a singled string.18:39
gyeeayoung, email is unique across the world18:40
dwchadwickI suggested you make it a config parameter that each OpenStack installation can decide18:40
ayounghenrynash, so, is there fundamentally and difference between saying "we have multiple domains" and "we have multiple namespaces?"18:40
dwchadwickIn this way you cater for Chinese, Korean, Japanese etc18:40
dolphmayoung: +1 to straight up concatenation is impossible18:41
ayounggyee, yes, but we are not currently splitting domains on email addresses.  If we do that,. we end up with one domain per unique email address in the system....sub optimal18:41
henrynashayoung: if we take the approach suggest here, then no every domain is its own namespace18:41
ayounghenrynash, and I think that is the right approach18:41
ayoungso lets drop the term "private" from discussing namespaces.  What we should say is something like this:18:42
ayoung1.  IN folsom, there is one domain and one namespace18:42
ayoung2  Grizzly there will, by default, also be one domain and one namespace18:42
ayoung3.  If you want to enable an additional domain, you can do so18:42
ayoung4.  this domain will have a separate namespace from the existing domain.18:43
*** iben-mobile has quit IRC18:43
*** iben-mobile has joined #openstack-meeting18:43
henrynashayoung: +118:43
dwchadwick4. But you have to specify the domain name always18:43
ayoungI think this maps to how people will want to use it.18:43
topolayoung +118:43
*** andreaf has joined #openstack-meeting18:43
ayoungdwchadwick, there's the rub, as the bard said18:43
gyeeayoung, +118:43
ayoungso that should be up to the deployment to decide18:43
*** anniec has joined #openstack-meeting18:43
ayoungif you have multiple namespaces,  you can chose either:18:43
ayoung1.  if they leave off the domain ID, they get the default or18:44
ayoung2. if you leave off the domain id you get an error18:44
ayoungWe have gone with 118:44
henrynashayoung: …they get the domain the token is scoped to….18:44
ayoungas it allows the V2 api to work unchanged18:44
ayounghenrynash, right18:44
ayoungbut you have to start the process somewhere18:44
ayoungso if I just pass in userid and password to get a token, and not domain ID, we are saying that is checked against the default domain to keep V2 working18:45
gyeeI like that18:45
dwchadwickno 4. But you have to specify the domain name always when you want to use the non-default domain18:45
henrynashayoung: v2 client yes18:46
ayoungBut, for V3,  we can specify that the domain Id is always passed, or we can specify it is up to the deployment whether it is required or not18:46
joesavakup to deployment, please18:46
ayoungdwchadwick, yes, you  have to specify the domain name always when you want to use the non-default domain.18:46
dwchadwickthat works18:46
ayounggyee, henrynash do you guys feel like we have a workable solution?18:47
dwchadwickSo this issue is not up to the deployment18:47
gyeeayoung, sounds good to me!18:47
ayoungdwchadwick, the deployment gets to say whether default domains are in effect, or whether you always have to specify18:47
henrynashgyee: The key is that this is a hard: every domain has its own namespace18:47
dwchadwickayoung  yes18:47
henrynashI'm fine with that…the rest is details we can work through outside this meeting18:47
ayoungdwchadwick, said another way, the deployment controls the rule "what to do if domain ID is missing"18:48
ayoungschweet18:48
dwchadwickayoung : no, the deployment cannot control that18:48
gyeehenrynash, hard to implement or hard to understand? :)18:48
henrynashgyee: hard as in fixed!18:48
dwchadwickIt cannot say domain name is missing and it is private namespace18:48
ayoungdwchadwick, I thought we agreed to stop using the word private18:49
ayoungbut yes, I am not saying that18:49
dwchadwickas recipient then wont know what name it is meant to be18:49
ayoungit can say18:49
ayoungif no domain id, use a default domain of "EXAMPLE_COM"18:49
dwchadwickagreed18:49
ayoungor it can say18:49
ayoungif no domain id, raise an exception18:49
dwchadwickbut it cannot same if domain is missing, guess which domain it is18:49
ayoungdwchadwick, true....although we are specifying that in certain cases, a missing domain ID would mean "carry over the domain id used in a previous transaction with this same user"18:51
henrynashheck, young: Ok, sign me up to update the api spec to reflect this18:51
ayoungso it has to be specified at some point in the chain.18:51
ayoung#action henrynash updates spec to reflect current design of domain namespacing18:51
gyeecan you guys approve the current token API spec first?18:52
topolgyee: whats the review url18:52
henrynashgyee: valid point18:52
dwaiteI'm still a little unclear on domains and namespaces18:52
gyeehttps://review.openstack.org/#/c/20524/18:52
topolgyee: you earned a +1 from me today18:53
gyeetopol, thanks18:53
henrynashgyee: you'll need to change the wordings to remove private namespaces etc.18:53
ayounggyee you have your approval https://review.openstack.org/#/c/20524/18:53
gyeegrasseyass amigo!18:53
*** dprince has joined #openstack-meeting18:53
henrynashgyee: however, it won't change what you pass, just the text description18:53
dwaiteis a domain a namespace?18:53
ayoungheh, I already hit approve.  Should I stop that?18:54
gyeedwaite, yes18:54
henrynashdwaite: it is now18:54
dwaiteok18:54
dwaiteyay18:54
gyeehenrynash, you can do the wording update after the merge18:54
henrynashgyee: +218:54
gyeew00t!18:54
dolphmayoung: did you review the final result or just hit approve?18:54
*** galthaus_ has joined #openstack-meeting18:55
*** enikanorov has quit IRC18:55
ayoungdolphm, hit approve. there were +2s from two core18:55
ayoungI can stop it18:55
dolphmayoung: please read hugely impactful changes before you sign off on them :(18:55
gyeewhat's the holdup?18:56
heckjreading back really quick - I very much want a fixed suggested solution for waht happens when no domain is specified.18:56
*** davidha has joined #openstack-meeting18:56
heckjayoung - good with your proposal entirely18:56
heckjbut it can't be deployment specific, or we'll fuck interoperability18:56
heckjI'm fine with someone choosing to do it another way, but we need (as OpenStack) to have an opinion on the solution and publish it to allow for interop18:57
ayoungdolphm, sorry...I just saw that there was the requisite number.  We can continue to update the spec, though....I think that it is ok for this to be its own commit18:57
*** Haneef has quit IRC18:57
ayoungnot a bad idea to break big reviews down into smaller ones, as we have seen18:57
gyeeright, and henrynash is going to change the wording on namespace18:57
stevemar+118:57
*** galthaus has quit IRC18:57
*** galthaus_ is now known as galthaus18:57
ayoungwow, that merged fast18:57
dolphmdocs have very little build process18:58
gyeehenrynash, she's all yours :)18:58
dolphm / gating18:58
henrynashgyee: I"ll treat her gently...18:58
*** brich has left #openstack-meeting18:58
ayoungdolphm, actually, now that I look at it, I had read that earlier.18:58
ayoungI was fine by it.  It can always be clearer, but I think we are on the right track18:59
heckjWell, there goes that meeting.18:59
*** dwchadwick has quit IRC19:00
ayoungdolphm, since I assume heckj is split-brained right now, you want to move on to the next topic, or just call it here19:00
*** olaph has joined #openstack-meeting19:00
henrynashheckj: hey, but agreed stuff!19:00
ayoungheckj, ah.  we done?19:00
heckjwe're out of time, so we'll need to wrap for today19:00
heckj#endmeeting19:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:00
openstackMeeting ended Tue Feb  5 19:00:44 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-02-05-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-05-18.00.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-05-18.00.log.html19:00
clarkbTime for openstack infra19:01
fungiyup19:01
pleia2o/19:01
clarkbwho do we have? olaph fungi pleia2 zaro ttx annegentle ryan_lane?19:01
*** kwss has quit IRC19:01
olaphohai19:01
*** stevemar has left #openstack-meeting19:01
clarkb#startmeeting infra19:01
openstackMeeting started Tue Feb  5 19:01:50 2013 UTC.  The chair is clarkb. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
*** psedlak has quit IRC19:01
fungiold business?19:02
clarkbon the agenda for today: CLA, wiki, logs, reviewday, jenkins plugins, and whatever else we want to talk about19:02
fungisounds goof19:02
fungigood too19:02
clarkb#topic CLA19:03
*** openstack changes topic to "CLA (Meeting topic: infra)"19:03
clarkbfungi: how are things in redoing the CLA land?19:03
fungino news is good news. also known as "i've been busy with other things"19:03
fungiwe're on track19:03
fungitoddmorey and i keep missing each other to exchange the new key, but other than that good19:04
clarkbthe dummy endpoint for CLA checking landed on review-dev correct?19:04
fungia few weeks back, yeah19:04
*** heckj has quit IRC19:04
*** dwaite has left #openstack-meeting19:04
clarkbother than exchanging a key is there any other work we should keep on our radar?19:04
*** ociuhandu has quit IRC19:05
fungiannegentle posted a follow-up to the ml, but nobody seems to have piped up past that19:05
fungithe actual cut-over will be happening on the 24th of this month, so keep that in mind i guess19:05
fungii'll remind everybody to get some reviews done on the pending wip patches when we get closer19:05
clarkbok sounds good to me19:06
fungithey'll likely need a rebase between now and then anyway19:06
clarkbI will do my best to write changes that conflict with yours :)19:06
fungianyway, unless there are questions, we can move on to the next topic19:06
clarkbnone from me.19:06
fungithough i think we skipped the action items from last week19:06
funginot that it probably matters much since most of that's on the agenda anyway19:07
fungigiven that we never revised teh agenda ;)19:07
clarkb#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-01-29-19.01.html <- last weeks notes19:07
clarkbI am going to skip the wiki for now because I don't think ryan_lane is here yet19:08
fungik19:08
clarkb#topic quantal slaves19:08
*** openstack changes topic to "quantal slaves (Meeting topic: infra)"19:08
fungii've got four up and running. our automation for launching new slaves has been fixed to accommodate quantal19:08
*** afazekas has quit IRC19:08
fungiover the weekend i tested the master branch unit tests for all core and incubated projects on quantal slaves and they're fine19:09
clarkbI think the tripleo folks have volunteered to guinea pig for us19:09
fungii need to update jclouds to be capable of adding extra quantals19:09
fungibut we can press forward before that as long as we don't switch too many projects over19:09
clarkbfungi: did you want to go ahead and propose changes that migrate projects one by one to quantal? (or in groups smaller than doing all at once)19:09
fungii assume we want buy-in from the core devs on each project, right?19:10
clarkbyeah I would have them +1 the change (or get the PTL to)19:10
fungiso probably separate changes, that way they don't block progress if some projects are slow reviewing19:10
fungii can batch the server and client projects together19:11
fungias pairs19:11
clarkb++19:11
fungii'll add jclouds first though, so that we can be lazy about adding persistent slaves if needed19:11
clarkbsounds good to me19:12
*** dprince has quit IRC19:12
*** dprince has joined #openstack-meeting19:12
clarkbany questions about quantal slaves?19:12
clarkb#topic Jenkins Build Logs19:13
*** openstack changes topic to "Jenkins Build Logs (Meeting topic: infra)"19:13
fungialso known as how to lose a monday19:13
pleia2heh :)19:13
clarkbyesterday (Monday) static.o.o which hosts the logs.o.o vhost decided it would run out of disk space19:13
fungi#link http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=309&rra_id=all19:14
clarkbthis caused the gate to effectively grind to a halt as Jenkins could not copy build logs to the log server and zuul interpreted these failures as job failures19:14
clarkbfungi managed to run the compression job aggressively to keep things semi sane but compressing things and cleaning up old unneeded cruft wasn't helping much19:15
fungi#link https://bugs.launchpad.net/openstack-ci/+bug/111539119:15
uvirtbotLaunchpad bug 1115391 in openstack-ci "Root filesystem full on static.openstack.org" [High,In progress]19:15
*** diogogmt has quit IRC19:16
clarkbafter looking at the problem more closely we realized that the tempest full runs were producing 42MB syslog which was being duplicated by screen logs (all uncompressed). That plus the other logs we were capturing put each devstack tempest full run at near 100MB of log data19:16
clarkbjenkins was not compressing this data before copying it and each change runs 2 to 3 of these jobs. tl;dr it didn't take many jenkins jobs to eat up gigs of data before things got compressed19:17
fungiand we normally only compress on static.o.o every 4 hours19:17
fungithe monday rush overran that rapidly19:18
*** iben has quit IRC19:18
clarkbthe temporary solution is we are no longer copying the openstack service screen logs as syslog duplicates that data, and we are compressing the files before jenkins copies them to the log server19:18
*** awataszko has joined #openstack-meeting19:18
clarkbvishy pointed out that syslog truncates messages so I have written a change to increase the MaxMessageSize in rsyslog on our slaves19:19
clarkb#link https://review.openstack.org/#/c/21233/19:19
clarkbthis should keep things reasonable while we sort out a long term solution to this problem19:20
*** cp16net is now known as cp16net|away19:20
*** nachi_ has quit IRC19:20
clarkblong term options include: growing the disk space on static.o.o, storing all logs in swift, rotating logs more aggressively (there are many ways of doing this), and I am sure we can come up with many more19:20
clarkb#action clarkb start discussion on long term log archival options when jeblair gets back19:21
fungiin the meantime we've got about 4gb free right now19:21
fungiwe may need to come up with something we can purge between now and next week, depending19:22
clarkband if the gate queue ever quiets down we may just go ahead and grow that disk19:22
fungimy only concern there is that it comes with a bigger vm all around, and we can't as easily scale back19:22
fungibut it definitely is an easy way out19:23
pleia2well, growing it a little now could give some breathing room (certainly isn't a long term solution)19:23
pleia24G doesn't seem like a lot right now19:23
clarkbyeah, and we are trying to move more items to static.o.o so I don't think making it a bigger server is a bad idea in general19:23
fungii'll buy that19:23
funginext step up is 4g ram and 160g disk19:23
fungiright now it's at 2 and 8019:24
clarkbanything else on logs?19:24
clarkb#topic reviewday19:25
*** openstack changes topic to "reviewday (Meeting topic: infra)"19:25
*** nachi has quit IRC19:25
pleia2so, last week I cleaned up the code so now it passes pep8 and pyflakes tests19:25
*** cp16net|away is now known as cp16net19:26
pleia2also made it so it can take a command line argument to specify the output directory19:26
pleia2puppetizing is now in progress19:26
pleia2planning on putting this on static.o.o at the moment (it's small and doesn't really grow)19:26
*** otherwiseguy has joined #openstack-meeting19:26
pleia2that's all I've got19:27
clarkbpleia2: are there outstanding changes that need review?19:27
*** dosaboy has quit IRC19:27
clarkbI have been particularly bad keeping up with the review queue lately (will try to fix that today)19:27
pleia2clarkb: I checked in a change, but it's more for sharing with fungi at the moment to fill in the missing pieces (not ready for proper review)19:28
clarkbok19:28
fungithough i saw pabelanger had some suggestions on it already, so you'll want to have a look at those19:28
pleia2yeah, most of those are known, but it is helpful19:28
fungiand i'll start going over it after the meeting, before dinnertime19:28
pleia2much appreciated19:28
clarkbcool19:28
clarkb#topic Jenkins Plugins19:29
*** openstack changes topic to "Jenkins Plugins (Meeting topic: infra)"19:29
zaroi need some of my java stuff reviewed if anyone wants to do it.19:29
*** hanrahat has quit IRC19:29
clarkb#link https://review.openstack.org/#/q/project:openstack-infra/gearman-plugin,n,z19:29
*** ijw1 is now known as ijw19:29
fungizaro is a.k.a. khaido i guess. i miss nick changes sometimes19:29
clarkbtrying to get the number of outstanding changes down to a reasonable number to simplify git management19:29
clarkbfungi: yes19:29
*** mrmartin has quit IRC19:30
zarosorry didn't inform about nick change. but it's true19:30
clarkbzaro demoed gearman running jobs across multiple jenkins masters for me. it is pretty awesome19:30
funginice!19:31
fungiscalability, here we come19:31
zaroi've been holding off further changes until reviews come back.19:31
*** sarob has quit IRC19:31
zaroworking on documenting it and further tests.19:31
clarkbzaro has also started a gearman puppet module. so there is an assortment of related items around the gearman plugin that are ready for review19:31
*** sarob has joined #openstack-meeting19:31
fungii'll try to take a closer look in the next couple of days. i've also been very slack on reviews of late19:32
clarkbme too.19:32
clarkbI skimmed jeblair's LCA talk and he mentioned the ZMQ plugin there. And implied it would be available through the normal openstack-infra channels. So I will try getting that into gerrit sometime in the near future too19:33
fungijeblair's already releasing your future work. awesome19:33
zarohave a link to his talk?19:33
pleia2zaro: http://mirror.linux.org.au/linux.conf.au/2013/mp4/OpenStack_Zuul.mp419:34
clarkbthe plugin is running on jenkins and jenkins-dev and is still spewing events so I think it is working now19:34
*** arunkant has quit IRC19:34
pleia2zaro: watched last night, it's great :)19:34
fungiand that gets us a step closer to logstash indexing of job logs, right?19:34
clarkbfungi: yes, it makes the notification of "hey logs are available" very simple19:35
zaropleia2: got a link to talk?19:35
*** diogogmt has joined #openstack-meeting19:35
pleia2zaro: the mp4 link above19:35
zaropleia2: opps.  thanks.19:35
clarkbfungi: jeblair was suggesting zuul may use it too19:36
fungioh, i can see where that would be helpful, yes19:36
clarkbstill no ryan_lane but I think we should move onto talking about the wiki move19:36
* annegentle is here19:36
clarkb#topic wiki19:36
*** openstack changes topic to "wiki (Meeting topic: infra)"19:36
clarkbolaph: how are things?19:37
*** gyee has quit IRC19:37
olaphthe underlying skin on wiki-staging.o.o is different from the one I was using, but I've ported over all the style changes required for 'v1'19:37
*** sarob has quit IRC19:37
*** sarob_ has joined #openstack-meeting19:37
clarkbhttps://wiki-staging.openstack.org is not returning bytes to me. is that expected?19:38
olaphhttps://wiki-staging.openstack.org/wiki/Main_Page19:38
fungii got a cert from it, but yeah, no content19:38
*** novas0x2a|laptop has joined #openstack-meeting19:39
clarkbooh shiny19:39
clarkbwe should probably make apache forward you to /wiki/Main_Page when you hit /19:39
olaphI would assume that would resolve correctly when they go live...  :)19:39
fungitiming out getting a response after the handshake19:39
clarkbah19:39
pleia2nice19:39
clarkbannegentle: olaph I know jeblair requested we move the migration up a day19:40
annegentlelooking good19:40
clarkbI was hoping ryan_lane would be here to chime in on that19:40
pleia2he works next door to where I live, shall I go knock? :)19:41
clarkbpleia2: I won't stop you, but I don't think it is necessary :)19:41
clarkbannegentle: how do you feel about that?19:41
annegentleno problem from me, either day works19:41
ttxclarkb: o/19:42
clarkbI think both fungi and I are available on the 17th if we want to stick wit hthe original day that everyone agreed to19:42
fungiyeah, i'm cool either way19:42
clarkbttx: heelo19:42
ttxolaph: nice work on the theme19:42
clarkbok sounds like either day works for most people. if we can get a hold of ryan today and he is ok with the 16th then I think we should move it19:42
clarkbttx: ^ that work with you?19:42
ttxI'll be in jetlag mode but yes, works for me19:43
fungiif we do that, i guess we also need to follow up to the original announcement on the ml19:43
clarkbfungi: yes we will need to send an update19:43
annegentleyeah makes sense, I'll send an update as needed19:43
clarkbis anyone aware of any additional outstanding items? I believe image upload works and the template looks good19:44
clarkbI guess not19:45
clarkb#action clarkb to find out if ryan_lane is ok with migrating the wiki on Feb 16 instead of Feb 17.19:45
clarkb#topic open discussion19:45
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:46
annegentle#action annegentle to send update to mailing list if moved to Feb 1619:46
ttxclarkb: was wondering if we could do something to get python-swiftclient 1.3.0 to Pypi19:46
ttxbeen chasing mordred about it to not avail19:47
clarkbttx: that was the tag that didn't push properly because the jenkins job was off?19:47
ttxthat was the tag that didn't push properly because a script was missing19:47
clarkbyes, we can manually push that to pypi19:47
mordredoh, sorry19:48
clarkbmordred: did you want to do that?19:48
* ttx blames mordred for not doing it earlier19:48
mordredclarkb: I can, unless someone beats me to it19:48
mordredclarkb: I was going to re-trigger the job in jenkins to re-test it19:48
clarkb#action mordred to upload python-swiftclient 1.3.019:49
mordredrather than pushing the tag manually19:49
clarkb++ to retriggering jenkins job19:49
ttxmordred: while you're in acceptance mode, remember to push new versioning code to projects asap19:49
mordredttx: https://review.openstack.org/#/q/status:open+branch:master+topic:oslo-version,n,z19:49
ttxmordred: cool, thx19:49
fungimordred: any news on the rhel slave licensing situation?19:49
*** enikanorov has joined #openstack-meeting19:50
mordredfungi: I learned new things at LCA, but need to follow up on them19:50
fungiokay, awesome19:50
clarkbwe will probably want to follow http://people.canonical.com/~ubuntu-security/cve/2013/CVE-2013-0169.html19:52
uvirtbotclarkb: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0169)19:52
ttxmordred: also I'll probably start up summit.openstack.org on the same cloudserver instance as for past summits19:52
ttxmordred: couldn't push it to infra proper and now time is running very short19:52
mordredttx: ok19:52
ttxmordred: I kinda want to do it myself as an exercise19:52
ttxso I'll do that early in H.19:52
* ttx remembers saying that 6 months ago too.19:53
mordred:)19:53
clarkbwe could trap ttx in a bar in portland and make him do it then19:53
*** afazekas has joined #openstack-meeting19:53
clarkbanything else?19:54
clarkb#endmeeting19:54
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:54
openstackMeeting ended Tue Feb  5 19:54:30 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-05-19.01.html19:54
Daviey.19:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-05-19.01.txt19:54
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-05-19.01.log.html19:54
fungiDaviey: ?19:55
*** Mr_T has joined #openstack-meeting19:57
Davieyfungi: wassup?19:58
DavieyOh, the . was a typo. Sorry.19:58
fungiahh, didn't know if you had a last-minute question when we were closing out the meeting19:58
*** Hg_ has joined #openstack-meeting19:58
*** Hg__ has joined #openstack-meeting19:59
*** Hg_ has quit IRC19:59
*** gabrielhurley has joined #openstack-meeting19:59
ttxWho is around for the TC meeting ?19:59
*** markmc has joined #openstack-meeting19:59
gabrielhurley\o19:59
*** Hg_ has joined #openstack-meeting19:59
markmchey20:00
*** torgomatic has joined #openstack-meeting20:00
markwashttx: I'm standing in for bcwaldon, unless that's a subsequent meeting where I'm supposed to do that :-)20:00
* markmc in a meeting, so will be a little distracted ... sorry20:00
* ttx counts 3 so far, pinging others20:00
ttxmarkmc: I think you replace him for the next meeting20:00
markwashttx: gotcha20:00
* markwash lurks anyway20:01
danwento/20:01
notmynamehere20:01
ttxrussellb annegentle jgriffith heckj ?20:01
annegentleo/20:01
*** maurosr has quit IRC20:01
ttxvishy jaypipes mordred ?20:01
vishyo/20:01
mordredo/20:01
* ttx stopped counting20:02
ttx#startmeeting tc20:02
openstackMeeting started Tue Feb  5 20:02:11 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: tc)"20:02
openstackThe meeting name has been set to 'tc'20:02
ttxAgenda for today is:20:02
jaypipeso/20:02
ttx#link http://wiki.openstack.org/Governance/TechnicalCommittee20:02
ttx#topic Schedule for Spring 2013 PTL/TC elections20:02
*** openstack changes topic to "Schedule for Spring 2013 PTL/TC elections (Meeting topic: tc)"20:02
*** galthaus has quit IRC20:02
ttxOur charter actually defines the timing for elections, based on the date for the Summit20:02
ttxNow that we know the summit date, the timing is:20:03
*** galthaus has joined #openstack-meeting20:03
ttxMarch 1-7: Nominations for PTL20:03
ttxMarch 8-14: Vote for PTLMarch 8-14: Vote for PTL20:03
ttxoops20:03
ttxMarch 15-21: Nominations for direct seats20:03
ttxMarch 22-28: Vote for direct seats20:03
ttxThis is coming fast20:03
ttxWe need people that are not running for any position to organize those. I can't do that since I need to run for reelection myself.20:03
ttxannegentle, mordred: one of you interested in spearheading that effort ?20:03
markmcttx, do we run PTL elections for (still) incubating projects?20:03
markmcttx, or only do that when projects graduate?20:04
annegentlewow are we the only two eligible?20:04
ttxmarkmc: no, we have to decide if they graduate /before/ the elections20:04
*** rnirmal has joined #openstack-meeting20:04
annegentleor can other community members organize them20:04
*** vipul is now known as vipul|away20:04
ttxannegentle: you're the only two I /think/ won't run20:04
mordredmordred: I can do it if I can start working on it tomorrow20:04
ttxannegentle: oh, you can have election officials that are from elsewhere20:05
ttxjust kinda want someone from the TC to own the process and see it to completion20:05
annegentlemordred: awesome because I really can't20:05
markmcvuntz and jeblair help with the foundation elections, they might be interested?20:05
ttxmordred: we can hook jeblair in, can help with the election lists20:05
ttx#info mordred to set up elections20:06
ttxmordred: You can start with a copy of http://wiki.openstack.org/Governance/TCElectionsFall201220:06
ttxask me if you have questions20:06
ttxquestions on that ?20:06
mordredexcited20:06
markmcgood luck mordred20:07
* ttx is happy to offload some of his so exciting tasks to someone else :)20:07
*** galthaus has quit IRC20:07
ttxok, no questions I see20:07
ttxnext topic then20:08
ttx#topic Update on the "Future of Incubation / core" joint committee20:08
*** openstack changes topic to "Update on the "Future of Incubation / core" joint committee (Meeting topic: tc)"20:08
ttxSo... we needed to propose a way forward to projects currently in incubation, before it's too late to add them to the integrated release cycle for Havana20:08
ttx(we need to decide which projects are "integrated", and therefore have PTLs, before we start the PTL election process, i.e. before March 1st)20:08
ttxTo that effect we summarized the current position of the Incubation/Core joint committee and that was presented to the Board20:08
ttxMy understanding was that this being a TC process and no red flag being waved, we should go ahead with that process for the currently-incubated projects20:08
ttxmarkmc, mordred: comments ?20:09
markmcso, I summarised stuff here:20:09
markmchttp://lists.openstack.org/pipermail/openstack-tc/2013-January/000113.html20:09
markmcthe slightly messy thing is that the committee hasn't finished its work completely20:09
mordredttx: my only comment/concern is what markmc said20:09
markmcand we said the TC would go ahead based on the discussions to date20:09
markmcafter running it by the board20:09
ttxright, I expect the committee to continue working until May tbh20:09
markmcseeing as this shouldn't need approval by anyone but the TC20:09
markmcI presented to the board (as a TC rep) last week20:10
ttxThe idea would be to have in the remaining weeks of February a "end of cycle incubation graduation review" where we look into the state of the currently-incubated projects20:10
markmcbut seems like mordred understands what happened a little differently20:10
ttxand either accept them as part of the integrated release for havana, or ask them to continue maturing during the next cycle20:10
ttxDoes this fly for everyone, and if not what would be your alternate suggestion ?20:10
jgriffithworks for me20:11
annegentlemarkmc: did the board say "do what you have to?"20:11
Daviey(As long as these don't suddenly become mandatory (unlikely) for Grizzly, i am a happy bunny :)20:11
ttxnote that we can start the process based on our understanding, and stand corrected if needed20:11
mordredmarkmc: yeah, that sounds find. for some reason I thought ttx was suggesting we vote to ratify the work in progress state :)20:11
annegentlemarkmc: (Your list message just said something about red flags)20:11
markmcannegentle, there was some discussion about process, some support of the progress we made and no objections raised20:12
markmcannegentle, but there was no vote on anything20:12
ttxmordred: no, just want to tell the incubated project when they will be eaten and with what sauce20:12
markmcannegentle, and disclaimer: the official minutes would be the official "what the board said" record20:12
markmcannegentle, right, there were no red flags raised20:13
annegentlemarkmc: just looking for the big gotchas is all, sounds like there are none20:13
ttxOK, so everyone is fine with us looking into graduation in February, in time to meet PTL elections deadlines on March 1st ?20:13
markmcttx, mordred, would we e.g. do s/Core/Integrated/ in our charter before we consider Heat/Ceilometer?20:13
ttxmarkmc: yes that's my next question actually20:13
ttxThis new "integrated" concept triggers an interesting related question. As far as our "Charter" is concerned, we have two interpretation options:20:13
ttx1. Consider that what we technically called "core" is now renamed to "integrated" -- and grant all (current and future) integrated projects a seat on the TC20:13
ttx2. Consider that what is called "core" in the Charter still means "core" (although the joint committee did not define that term yet) -- and only grant "core" projects a seat on the TC20:13
ttxI much prefer interpretation 1 since otherwise we would basically give the BoD the right to choose which projects have guaranteed seats on the TC20:14
markmcpersonally, I had assumed (1)20:14
ttxbut since that touches our Charter I figured I should ask the committee first :)20:14
markmc(2) hadn't even occurred to me20:14
DavieySilly question .. There isn't intention to couple Ceilometer or Heat as a mandatory component in a deployment, rught?20:14
ttxDaviey: there is nothing mandatory.20:14
mordredDaviey: the only curently mandatory components are nova and swift20:14
mordredDaviey: and that's only if you want to use the trademark20:14
markmcthe problem with (2) is it involves the Foundation Board in the question of "who gets a seat on the TC"20:15
markmcwhich seems strange20:15
ttxmarkmc: yep20:15
mordredyep20:15
Davieysure, but i think most people would consider keystone & glance practically required20:15
markmcDaviey, nothing which is in the release currently would depend (even optionally) on Heat or Ceilometer20:15
notmynamettx: while I agree with the spirit of (1), I'd prefer to wait until the committee finishes before redifining things. and choosing (2) does put some pressure on people to come up with the right definitions :-)20:16
mordredDaviey: sure. it's just that if you want to talk about _required_ - the only thing you guys are required to implement to call your thing openstack is nova and swift as things are currently written20:16
ttxnotmyname: the problem is that I don't expect the committee to decide on that before the end of the month20:16
ttx*we can defer that decision until then20:16
mordredttx: related to what notmyname said...20:16
markmcif we don't decide on (1) vs (2) before PTL elections20:16
markmcit would mean the new PTLs wouldn't know whether they will sit on the TC20:17
annegentledoes heat or ceiliometer have stand-in PTLs now? We're not preventing their technical progress right?20:17
mordredwhat if we did (3) move forward as currently chartered, since it doesn't particularly conflict with the committee direction20:17
markmc(new PTLs, if any)20:17
Davieymordred: I'm talking on a pure technical basis.  I think markmc got what i was trying to convey, and confirmed my question perfectly.20:17
mordredDaviey: great20:17
ttxmarkmc: yeah, we kinda need to know before the election setup20:17
ttxotherwise it will get messy20:17
ttxbut we could decide that on Feb 28, I guess20:17
* ttx doesn't mind, he doesn't organize the elections this time around20:18
markmcI'm starting to think the committee should just wrap up the incubation side of things this week20:18
mordredmarkmc: I agree20:18
markmcso the TC can move on without this debate over process20:18
markmcbut ...20:18
mordredhow about this?20:18
markmcdoes that mean we need a joint TC/Board meeting?20:18
annegentlemarkmc: yes some time pressure there seems appropriate20:18
mordredhow about this week we see if we can get a motion out of the committee?20:19
markmcI'm sure we can20:19
mordredthat can be taken to the all-day-in-person board meeting on tuesday20:19
mordredif that goes well, then we don't hav ea bunch of things to tap dance around on our side20:19
markmcbut wasn't the idea the TC and Board would jointly discuss recommendations from the committee20:19
ttxmordred: I'm a bit concerned with the timing for the end of cycle graduation review20:19
mordredif it doesn't, then we make contingency plans20:19
ttxwe have three meetings left: Feb 12, Feb 19, Feb 26 to consider Ceilometer and Heat20:19
markmcmordred, one thing, though - what is proposed doesn't *need* board sign-off IMHO20:20
mordredmarkmc: I might have been, but I cannot imagine a situation where that's productive20:20
ttxthat's why we need a decision this week... but not necessarily today20:20
mordredmarkmc: not saying it needs sign-off20:20
markmcmordred, right, we just need to be careful about terminology here20:20
mordredmarkmc: but _something_ needs to be _something_ before we start changing our charter20:20
ttxOK, how about this...20:20
ttxWe schedule the graduation review for the meeting of next weeks of February20:21
*** sleepsonthefloor has quit IRC20:21
ttxWe try to get the committee to wrap up that first part of the process (incubation)20:21
ttxAnd hopefully next week we are all set /and/ don't lose a week in scheduling20:22
mordredI think that sounds great20:22
markmcso, next week ...20:22
ttxmy only concern here is that we should start that review asap20:22
ttxIt's a bit tight. Feb 12, mordred and markmc might be caught into the board meeting and I'm not sure where i'll be myself. Feb 26 I'm skiing and probably won't be around20:22
markmcboth the TC and board vote on the committee's motion ?20:22
ttx(though I can miss meetings alright :)20:23
markmcmaybe we have a vote now, that the TC is happy to not have a joint meeting with the board to discuss it20:23
markmcthat we're happy with how things have gone?20:23
markmcmeh20:23
mordredttx: feb 12 when the TC is supposed to meet might be an opportune time to join the meetings...20:23
ttxmordred: now I'm confused20:24
jgriffithttx: ditto20:24
markmche's suggesting the TC join the board meeting next week20:24
markmcat this time20:24
* ttx hates process in the way of progress, especially when 99% of people agree on the way forward20:24
markmcnot sure how we'd work the logistics for that20:24
markmcbut maybe there isn't a better opportunity20:24
markmcttx, agree massively, this feels like a tonne of busy work20:25
mordredI mena, we're going to be there anyway20:25
*** jsavak has joined #openstack-meeting20:25
mordred++20:25
mordredotoh, I _do_ think there is nothing stopping us from assessing heat/ceilometer over feb20:25
ttxi somehow doubt we'll have quorum on the phone/webex/whatever thing for other TC members20:25
ttxI'm physically present, I don't mind20:26
markmcmordred, there is - clarity on what graduation means20:26
mordredspeaking of - if the next two weeks are iffy because of conflicts, what difference in action related to heat/ceilometer are you suggesting?20:26
markmcwe can begin assessing for sure20:26
markmcgathering data20:26
mordredmarkmc: the only difference in what graduation means is whether their ptl gets a seat on the tC20:27
*** stevebaker has quit IRC20:27
*** primeministerp has quit IRC20:27
annegentleSo there's a need for a deadline for graduation assessment, that should coincide with the TC makeup of PTLs, right?20:27
annegentleCan we convince the board these deadlines need to be the same date?20:27
markmcmordred, currently, graduation means becoming core20:27
mordredwhich should not make a difference to our assessment, based on the conversatoins about not changing TC elections20:27
markmcmordred, it obviously doesn't mean that anymore20:27
markmcmordred, but does it mean the TC recommends the project for core?20:27
*** psedlak has joined #openstack-meeting20:27
markmcmordred, we have a consensus on what it means, but for some reason we're stalling on implementing that20:28
ttxI'd prefer to have the clear go-ahead on the process (which I thought we had) before we start it20:28
mordredok. I'm not making myself clear, and I'm sorry for that ... let me try again20:28
mordreda) we have consensus, but right now we have consensus on something that a committee discussed, which means that I don't think that we need to amend our charter this instant20:29
*** joesavak has quit IRC20:29
mordredb) the effective actual steps of action we will take in the next two weeks do not change whether we implement the committee's recommendations or not20:30
mordredso - I think we are free to move ahead as usual20:30
mordredand then push for reslution from the committee20:30
ttxworks for me20:30
mordredunless I'm just WAY off base20:30
*** dprince has quit IRC20:30
ttxmordred/markmc: do  you think we can have the TC meeting next week ?20:31
annegentleyeah I don't think the two items (graduation and TC makeup) HAVE to coincide20:31
markmcso long as we have the TC charter accurate before the discussion about ceilometer/heat graduation, fine20:31
mordredttx: tough to say - I haven't seen the schedule - but I'm game to try to do both meetings at once :)20:31
markmcttx, it'd be lunch time, we could probably join. mordred?20:31
mordredmarkmc: let's just tell jbryce that that's the way it has to be20:31
markmcso20:32
ttxannegentle: theydon't have to coincide, but one must finish before the other ;)20:32
markmcwhen does our discussion about ceilometer/heat graduation start?20:32
annegentlettx: dependencies20:32
ttxmarkmc: next week20:32
* markmc sighs20:32
markmcare we going to have that discussion with e.g.20:32
*** joesavak has joined #openstack-meeting20:32
markmc"should ceilometer be core?"20:32
markmcconfusing the whole thing again20:33
mordredmarkmc: does it matter?20:33
annegentlemordred: yes I think it does20:33
markmcyes, I think confusion will make the discussion difficult20:33
mordredhrm. weird. ok20:33
ttxmarkmc: ideally by then we should have the clear mandate to only discuss integration20:33
markmcmordred, "are we recommending ceilometer to the board for core inclusion?"20:33
mordredmarkmc: OH!20:33
mordredmarkmc: I understand something you said before now20:34
mordredok20:34
markmcok, between the committee and board20:34
markmclet's try and get this better wrapped up for next week20:34
mordredsorry, I let my viewpoint cloud my process-view20:34
markmcfor next week's TC meeting20:34
ttxSo let's proceed as if we'll get that20:34
jgriffith+120:34
mordredttx: ++20:34
jgriffithplease, let's move forward one way or another!20:35
ttxjgriffith: yay, action20:35
markmcjgriffith, that's the thing - we could vote on this right now :)20:35
markmcjgriffith, the TC can change its own charter20:35
markmcjgriffith, within the bounds of its mandate under the bylaws20:35
*** jsavak has quit IRC20:35
jgriffithmarkmc: I have no objection to that TBH20:35
ttxme neither20:35
ttxbut I think mordred had20:35
mordredI do20:35
* notmyname hasn't seen anything in the last 10 minutes (router issues)20:36
markmcmordred, what exactly is the objection?20:36
mordredchanging ourside of hte charter unilaterally20:36
markmcyou could hardly call the last weeks and weeks of discussion on "unilaterally"20:36
ttxnotmyname: you didn't miss anything useful. Just back on forth on the need to be extra careful on stuff everyone agrees about20:36
notmynamettx: k, thanks20:36
mordredmeans that we would be voting projects into a structure that we do not know that the board will finally accept20:36
markmcmordred, I object to the notion that we can't do it without board approval20:36
mordredI agree20:36
mordredwe can totally do it20:36
mordredI just don't think it gets us anywhere20:36
annegentleI'd rather not give incoming projects whiplash :)20:37
ttxnotmyname: http://eavesdrop.openstack.org/irclogs/%23openstack-meeting/%23openstack-meeting.2013-02-05.log20:37
jgriffithmordred: I understand but on the other hand I'd rather make progress20:37
jgriffithif we have to adjust after the fact so be-it20:37
markmcmordred, so, process-wise - you think the TC might change its charter and later find the board has objections and the TC would then need to change again?20:37
jgriffithThe other thing is maybe we can influence the board this way20:37
markmcmordred, seems pretty far fetched20:37
* jgriffith likes to drive the bus, not ride it20:38
markmcmordred, far fetched, given the level of discussion we've had to date openly, in the committee and with the board last week20:38
mordredmarkmc: sure. but you know what we didn't do last week? we didn't make a motion with the board?20:39
mordreds/?$//20:39
jgriffithmarkmc: mordred I guess my question is whether this seems to be controversial from the boards perspective anyway?20:39
* mordred is PURELY being a process wonk20:39
jgriffithhehe20:39
markmcmordred, me too :)20:39
ttxmordred: you're being a wrong process monk20:39
markmcmordred, I don't see that a board motion is required20:39
markmcmordred, what would they be approving?20:39
ttxon that matter, the TC is self-sufficient20:39
jgriffithttx: +120:40
markmcthis is important20:40
markmcwhen we want to change things we have a mandate to change20:40
mordredmarkmc: I don't know - what the hell is the point of the committee if there is not an official actual outcome?20:40
* ttx happens to have written that charter and large parts of the bylaws whee they touch the tC20:40
markmcwill we always stall while we wait for board approval?20:40
mordredON THIS, yes20:40
mordredthis is the only thing where the board and the TC overlap20:40
ttxI can tell that we can move without the BoD formal approval.20:40
markmcmordred, to jointly discuss stuff and bring motions back to the appropriate board/tc that need to vote on the changes recommended20:40
mordredthe only thing20:40
markmcmordred, I think the board would vote on the core side of the thing and the TC would vote on the incubation side of things20:41
ttxmordred: core inclusion yes. incubation no.20:41
markmchow about this?20:41
markmcme or ttx draft a TC motion for us to vote on next week20:42
markmcafter discussion on list20:42
mordredttx: but the only reason we're talking about this right now is that the question of whether we are going to recommend these for core inclusion is up for debate20:42
markmcwe'll discuss it with the committee on thursday20:42
markmcand the board next week20:42
mordredmarkmc: heh. actually, that's required, now you mention it :)20:42
markmcand give everyone an opportunity to say20:42
markmc"we don't think you're following the right process, you need board approval before you can do this"20:42
markmcor whatever they might say20:42
mordredmarkmc: maybe that's the thing that was tripping my weird meter20:42
mordredmarkmc: ++20:42
ttxmarkmc: that sounds like a great way to lose one of our 3 precious weeks. But why not20:42
mordredttx: you have no choice20:43
mordredthe rule is that a TC motion needs to be proposed a week before a vote20:43
mordredfor adequate mailing list discussion20:43
ttxmordred: there is the choice to act now and ask for forgiveness later20:43
jgriffithttx: a motto to live by :)20:43
markmcttx, I think he's right on the week-to-discuss-a-motion thing20:43
*** sdake_z has joined #openstack-meeting20:44
ttxmordred: I went back and forth on the need for a motion20:44
*** mikor has joined #openstack-meeting20:44
ttxbut with the propsoed motion being exactly what we were mlandated by the TC to push to the committee...20:44
annegentlettx: Do the incoming projects want to know the whole story or just if they graduate to "integrated?"20:44
ttxwe actually already voted on that20:44
annegentlewhole story=TC makeup20:44
ttxmordred: I'm fine with voting twice on the same thing if you feel that's necessary20:44
mordredI'm very fuzzy on many things on this - I'll be the first to admit that20:44
mordredttx: you want to change our charter without a specific motion and vote?20:45
ttxmordred: but then I'd say that the BoD tainted you20:45
markmcttx, that was before e.g. the choice of the Integrated name and that we'd s/Core/Integrated/ in the charter20:45
jgriffithI can't help but wonder what the point of this TC is if we can't make decisions like this without approval etc20:45
* markmc would prefer a motion20:45
ttxmordred: we don't change the charter20:45
mordredoh. we don't?20:45
ttxmordred: we update the incubation process20:45
mordredsee, this is why motions are helpful20:45
jgriffithhehe20:45
mordredthey make it clear what we're deciding20:45
markmcheh20:46
ttxthe only fuzzy points is that the charter uses the "core" word20:46
ttxas mentioned earlier20:46
markmcwe change the process without changing the charter, heh20:46
markmchadn't thought of that20:46
markmcthink I'd prefer to do both together20:46
ttxthe charter doesn't mention incubation.20:46
*** heckj has joined #openstack-meeting20:46
ttxAt all.20:46
mordredso, it's possible that you and I have been saying the same thing the whole time20:46
*** stevebaker has joined #openstack-meeting20:46
markmc(don't feel strongly against just changing the process now and charter next week, though)20:47
ttxmordred: we might need to update the charter this month to account for the "integrated" concept20:47
ttxbut that doesn't prevent us from looking into heat /ceilometer graduation20:47
*** beagles is now known as beagles_music_le20:47
mordredjust so I'm clear - the rush is because we might need to include the projects in the ptl election, right?20:48
ttxWell, and also in things like summit preparation but yes20:48
mordredk. just making sure20:48
* mordred will enjoy watching the second heat ptl election in two months20:48
ttxwe need to know which projects are in the next release cycle' before we start it, basically20:48
*** alexpilotti has quit IRC20:49
ttxmarkmc: you summarize, or should I ?20:49
markmcheh20:49
markmcgo for it20:49
ttxargh :)20:49
ttxok so:20:50
* markmc doesn't know how to summarize all that quickly20:50
ttx- we prepare a motion/whatever describing the process, and present it to incup, board and TC20:50
ttx- at the same time, we schedule the graduation review to start at next week meeting20:51
ttxso that we don't lose another week20:51
markmc(and to be clear, only the TC vote is an "approval" vote ... the others would be "expression of support" votes)20:51
ttxyes20:51
*** vipul|away is now known as vipul20:51
markmcsounds good to me20:51
ttxobjections ?20:52
annegentleand for the graduation review, are us TC members reviewing based on graduation to integrated or core or no graduation?20:52
* markmc assumes most everyone has gone asleep ... this is boring20:52
ttxannegentle: the motion will say "graduation to integrated", and hopefully should be all set by then*20:52
*** cp16net is now known as cp16net|away20:53
annegentlettx: sounds good20:53
*** iben-mobile has quit IRC20:53
ttxannegentle: if shit happens we revisit20:53
markmcttx, the left hands side of this: https://docs.google.com/drawings/d/1oLo1ETnRpNSgDj_m7p6o6tF7HHA2a-3XeKa-QLMBcRc/edit20:53
ttxif shit hits the fan, I'll blame mordred20:53
markmcI'll throw him into the harbour20:53
ttxmarkmc: yes20:53
mordredttx: you always do :)20:53
ttxor the harbor20:53
*** markmc has left #openstack-meeting20:53
*** markmc has joined #openstack-meeting20:54
ttx#action markmc/ttx to prepare a motion/whatever describing the process, and present it FYI to incup, board and for vote on TC20:54
ttx#action ttx to schedule, at the same time, graduation review to start at next week meeting20:54
ttxquestion: do you think we should call projects one at a time or all together ?20:55
markmca quick status update from both next week20:55
markmcmight be a good way to start20:55
mordred++20:55
markmc"why we think we're ready"20:55
ttxsounds good20:55
ttx#topic Discussion: OpenStack compatibility test suite20:56
*** openstack changes topic to "Discussion: OpenStack compatibility test suite (Meeting topic: tc)"20:56
ttxSince we have a few minutes left...20:56
ttxThe Foundation asked me to raise the topic of an openStack compatibility test suite to the TC20:56
heckjany more detail there?20:56
markmcoh dear20:56
markmcbecause that's not a rathole20:57
jgriffithhehe20:57
annegentlehee20:57
ttxA blackbox tool that can be used to assess support for the OpenStack API, and that could be used as part of the certification/labelling by the BoD20:57
ttxGood idea, bad idea ?20:57
jgriffithbad idea IMO20:57
mordredI think it's a great idea. I think it's hard20:57
mordredheh20:57
ttxAny hint how we could trigger more interest in the community around that ?20:57
jgriffithbut I would entertain a version of that20:57
danwenti think its valuable, if done right.20:57
ttxML posts, design summit session ?20:58
markmcreasonable idea, potential for disastrous implementation of said idea20:58
ttxIt's one of those "sounds like a good idea, but nobody will have time to spend on doing it20:58
jgriffithSo... are we going back to "The API is OpenStack"20:58
mordredI think it should be kind of like some other things ... if someone thinks it's a good idea, they can implement it and then point us at it20:58
mordredI don't think we're going back to that at all20:58
ttxmordred: problem is that the ones that think it's a good idea are not really technical20:58
jgriffithSo I've had similar ideas at a smaller scale20:58
jgriffithIE drivers for cinder20:59
mordredttx: I disagree with that20:59
markmcjgriffith, from discussions so far, I doubt API compliance would be enough - also needs to use the implementation released by us20:59
gabrielhurleyIf a third-party implementation can pass the same tests (exercise.sh and tempest) our code review gating goes through, that's compatible, right? ;-)20:59
ttxmordred: putting it differently, the ones who cared enough to ask me to raise that issue are not technical20:59
mordredttx: I know brian aker brings up how helpful it was for them to have an API complliance checking tool for memcached all the time20:59
jgriffithbut on an overall project level I'm not quite getting what this proposal means exactly20:59
mordredthing is - I think that's tempest20:59
mordredand if someone thinks it isn't tempest, they should add more features to tempest - it's already black-box21:00
jgriffithmordred: +121:00
mordredand we use it to validate our own cloud21:00
markmcthere's also the potential the board could invest and hire someone to implement it21:00
markmcwith our guidance21:00
mordreds/cloud/code/21:00
ttxgabrielhurley: I think they want to have the tool so that they can use it in rules, but they kinda want the tool available before discussing that :)21:00
markmcnot sure if that's what anyone is proposing21:00
mordredmarkmc: can we hire someone to add it to tempest?21:00
jgriffithbut but but....21:00
jgriffithhold on folks... for the benefit of us slower people21:00
ttxanyway, just throwing the idea out there, just think about it21:00
ttxas time is over21:00
jgriffithI'm not really sure what this even accomplishes?21:00
*** topol has quit IRC21:01
markmcstricter trademark rules21:01
jgriffithttx: sure... drop a chaos grenade and run21:01
markmcor a new trademark program21:01
mordredttx: seriously - can we clarify how what is being asked for is different from tempest?21:01
heckjjgriffith: stirring up the pot before another meeting, of coure21:01
markmci.e. "OpenStack Certified"21:01
jgriffithheckj: go figure :)21:01
*** maurosr has joined #openstack-meeting21:01
markmcwho knows21:01
markwashjgriffith: doing blackbox testing for drivers is a fantastic idea btw21:01
ttxmordred: let's talk when we meet21:01
heckjmordred: ttx please - they seem to be the same to me too21:01
jgriffithmarkmc: Yeah, I get that but I think a def of "openstack-cert" would be prudent first21:01
mordredheckj: ++21:01
jgriffithmarkwash: I have a dream :)21:01
mordredheckj: ttx and I will jump on them next week21:02
markmcjgriffith, I'd like a def of "core" before anything else :)21:02
markwashjgriffith: since I bet most companies really want to implement drivers and not wholesale replacements (though I wouldn't be surprised if I were wrong on that measure)21:02
jgriffithmarkwash: TRUE DAT!!!21:02
mordredspeaking of - any of your bay area folks, ttx, markmc and I will be in san fran on tuesday21:02
ttxok moving on to next meeting21:02
jgriffitherrr...mark21:02
jgriffithmarkmc!!!!21:02
ttx#endmeeting21:02
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:02
openstackMeeting ended Tue Feb  5 21:02:37 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-05-20.02.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-05-20.02.txt21:02
jgriffithstupid keyboard21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-05-20.02.log.html21:02
mordredmarkwash: several public clouds have already implemented wholesale replacements21:02
mordredmarkwash: rax and hp both don't use keystone21:02
markmcwell now, that was an exhausting meeting21:03
mordredmarkmc: ++21:03
markmctime for a nap21:03
ttx#startmeeting project21:03
openstackMeeting started Tue Feb  5 21:03:08 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
*** openstack changes topic to " (Meeting topic: project)"21:03
openstackThe meeting name has been set to 'project'21:03
markmcnoooo....21:03
markwashmordred: true. . but I consider that bad for them and us21:03
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:03
* ttx takes a few red pills21:03
* jgriffith is napping now21:03
mordredmarkwash: me too!21:03
ttxmarkmc, heckj, notmyname, markwash, jgriffith, vishy, gabrielhurley, danwent: let's do it21:03
jgriffithready!21:03
danwenthello21:03
ttx#topic General announcements21:03
*** openstack changes topic to "General announcements (Meeting topic: project)"21:03
gabrielhurleyoh, the rest of us get to talk now?21:03
markwasho|21:03
ttxI pushed a proposal for a limited StringFreeze for projects following the upcoming Grizzly feature freeze in Feb 1921:03
jgriffithgabrielhurley: don't count on it :)21:03
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-February/005303.html21:04
heckjo/21:04
ttxIf nobody complains I'll document it so that it can take effect at FeatureFreeze21:04
gabrielhurley+121:04
annegentlesounds good21:04
jgriffithworks for /me21:04
vishyO/21:04
* heckj nods21:04
ttxmarkmc, mordred, annegentle, davidkranz/jaypipes: Updates from Stable/CI/QA/Docs teams ?21:04
mordredo/21:04
mordreduhm, things got shaky yesterday, but clarkb and fungi fixed everything21:04
markmc2012.2.3 released last week, no regressions reported AFAIK21:04
mordredand I'm pushing through version updates to people21:04
davidkranzAny feedback about turning on the full gate?21:05
davidkranz  ^^^ tempest21:05
mordredmarkmc: I may need to add more more versoin patch to oslo21:05
* jgriffith is happy about it so far21:05
ttxmordred: was wondering how badly the new long tests will fuck the money time for feature reviews21:05
mordredmarkmc: I found yet-another use case when upgrading glanceclient21:05
markmcmordred, ok, what for?21:05
markmcmordred, ah, I see21:05
markmcmordred, thought you meant something for first oslo-config tagging21:05
mordredmarkmc: glanceclient uses oslo-version in glanceclient/__init__.py :)21:05
ttxmordred: do we have any idea of the impact on the number of commits per day, for example ?21:05
*** alexpilotti has joined #openstack-meeting21:06
mordredttx: we don't - it shouldn't matter, we have zuul21:06
mordredttx: yesterday's problem was log files blowing out disks21:06
ttxmordred: it shouldn't matter if we had no false negatives21:06
jgriffithttx: mordred It is going to be interesting when we hit the last week of the milestone21:06
*** bru has joined #openstack-meeting21:06
mordred++21:06
mordredto both jgriffith and ttx21:06
ttxunfortunately we don't live in that ideal world yet21:06
mordredwe never will21:07
ttxso it does matter21:07
annegentleI have a brief set of reminders.21:07
ttxannegentle: shoot21:07
annegentleWiki migration going to 2/16, monthly doc team meeting 2/12, about to send a copyright guidance note to the -dev ML, operator's book sprint 2/24.21:07
annegentlewhew21:07
ttxcool21:07
ttxok, anything else before we move to project-specific stuff ?21:08
ttx#topic Oslo status21:08
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:08
ttx#link https://launchpad.net/oslo/+milestone/grizzly-321:08
markmcoslo-config is ready to tag21:08
markmchope to move some/most projects to it next week21:09
ttxmarkmc: oh, thought that was done already (tag)21:09
markmccommon-db is pretty close now, I think - did a bunch of work on it21:09
markmccfg-filter-view is new and I've a patch up21:09
ttxthat answers my two questions, thanks21:09
ttxmarkmc: ETA to tag ?21:09
markmckeyring might not make it21:09
markmcI don't know what's stopping me, tbh :)21:09
ttxmarkmc: do it in meeting. That's how I roll21:10
markmcI haven't actually got a patch through gerrit for oslo-config yet21:10
ttxAnything else on the oslo topic ?21:10
markmcwould seem odd to tag before that21:10
markmcno, nothing else21:10
ttxthx!21:10
ttx#topic Keystone status21:10
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:10
*** markmc has quit IRC21:10
ttxheckj: o/21:10
ttx#link https://launchpad.net/keystone/+milestone/grizzly-321:10
heckjola21:11
ttxheckj/dolphm: Should 'default-domain' be considered completed now ?21:11
dolphmttx: the last piece is in review21:11
ttxdolphm: for some reason it's not linked. Ok21:12
heckjttx: will change to pending review21:12
ttxheckj/ayoung: How are 'replace-tenant-user-membership' and 'trusts' going on ?21:12
heckjayoung was still asserting we'd get them in21:12
ttxtime is running low and tests running longer21:13
ayoung'replace-tenant-user-membership'  is close21:13
ttxheckj: could you elaborate on why pluggable-identity-authentication-handlers is blocked ? Is it technical or resource block ?21:13
ayoungI'm down to about 6 unit test failuers21:13
ayoungfailures21:13
ttxayoung: good news21:13
*** cp16net|away is now known as cp16net21:13
ayoungtrying to get that closed out today...tomorrowish21:14
ttxayoung: would be great21:14
ttxheckj: ?21:15
ttxDidn't see a lot of help coming on https://review.openstack.org/#/c/20524/ -- does that jeopardize stop-ids-in-uris ?21:15
heckjwe unblocked the authn/authz pieces for gyee, and he has implementation in progress (pending final agreement on the spec) - expecting that to move forward fairly agressively now21:15
heckjttx: if you'll look now, it's been approved - sorted through that with this morning's keystone meeting21:16
ttxheckj: which one of those blueprints (if any) would you require a feature freeze exception for, if they don't make it in time ?21:16
heckjmost critical would be "Implement auth on Identity API v3" and "Token trusts", but I expect both to wing in under the deadline21:17
ttxok, good!21:17
ttxAnything more about Keystone ?21:17
heckjnot from me21:17
ttx#topic Swift status21:17
*** openstack changes topic to "Swift status (Meeting topic: project)"21:18
ttxnotmyname: o/21:18
notmynamehere (as long as IRC connections are cooperating)21:18
ttxStill can't find python-swiftclient 1.3.0 on PyPI21:18
notmynameI poked mordred with a sharp stick last week about it21:18
ttxBeen complaining about that to mordred, maybe you can take the other 12-h nagging shift :)21:18
mordredclarkb is aware of it now21:18
notmyname:-)21:18
*** bencherian has quit IRC21:18
ttx#link https://launchpad.net/swift/+milestone/1.8.021:18
mordredwhich means something might actually happen :)21:18
ttxDo you expect that one to be the Grizzly one, or do you rather imagine two releases until common release, or no idea yet ?21:19
notmynamethat will probably be grizzly, based on when the cutoff will be21:19
ttxok21:20
ttxAnything more on Swift ?21:20
notmynamethat will probably be grizzly, based on when the cutoff will be21:20
ttxlooks like the Network is not with you today, let's move on21:21
ttx#topic Glance status21:21
*** openstack changes topic to "Glance status (Meeting topic: project)"21:21
markwashhi hi21:21
notmynamenot from me. swift meeting tomorrow21:21
ttxmarkwash: o/21:21
ttx#link https://launchpad.net/glance/+milestone/grizzly-321:21
ttxSaw code being proposed for glance-api-v2-image-sharing, which is good21:22
ttxIs the review progressing well ?21:22
markwashit is, I have been in talks with iccha21:22
markwashvery good progress21:22
*** bencherian has joined #openstack-meeting21:22
markwashI expect it (and everything labeled Good Progress) to land in time21:22
ttxI see api-v2-property-protection is not started yet -- do you still think it can make it in master in less than two weeks ?21:22
markwashas an absurd optimist, yes21:22
markwashbut I've been in talks with bcwaldon about retargeting21:23
ttxI'd rather get one in rather than target 2 and get none21:23
ttxmarkwash: do you know if Brian got the answers he was looking for from other assignees ?21:23
markwashI know that he got some, but we are still looking for info on common image properties21:23
ttxok... The last thing I wanted to mention are the late blueprints: iscsi-backend-store and its dependency, importing-rootwarp21:24
markwashprobably mostly proposals, rather than info :-)21:24
rainyamarkwash, if you have specifics, let me know and i'll bug folks on this end :)21:24
ttxI think jgriffith makes a really nice point in the first review: more generally piggybacking on cinder sounds like a hell of a better solution than reimplementing block storage drivers in Glance21:24
*** psedlak_ has joined #openstack-meeting21:24
ttxAnd that would benefit from some design discussion, like say at the Design Summit21:24
markwashI agree with jgriffith, however. .21:24
markwashI think I need to feel like its doing some harm before I could argue that it shouldn't be included21:24
jgriffithmarkwash: ttx I'll yield but I think it would have made more sense to use cinder21:25
markwashthe way it looks to me, (apart from rootwrap which is fine) it is well contained21:25
ttxmarkwash: you could argue that adding rootwrap for Glance is a bit of a large hammer for a weird nail21:25
jgriffithmarkwash: ttx I also understand something is better than nothing, but I would definitely want to see it changed in H21:25
markwashttx: that may be21:26
*** psedlak_ has quit IRC21:26
ttxjgriffith: I feel like accepting that is liekly to make the right solution[tm] harder to implement21:26
*** psedlak_ has joined #openstack-meeting21:26
jgriffithttx: sadly, yes21:26
ttxsince we'll have to support upgarde scenarios etc21:26
markwashhmm, you guys are speaking my language21:26
*** psedlak_ has quit IRC21:26
jgriffithI can shift my priorities to try and have an alternative if folks agree with me on it21:26
ttxsounds like something that could live in a branch rather than in a release21:27
jgriffithttx: +121:27
jgriffithI hadn't thought of that21:27
ttxanyway, bcwaldon decides21:27
*** jsavak has joined #openstack-meeting21:27
markwashwell, good feedback. I'll take it to bcwaldon and discuss21:27
ttxAnything more on Glance ?21:27
markwashnot from me21:27
ttx#topic Quantum status21:27
*** openstack changes topic to "Quantum status (Meeting topic: project)"21:27
*** psedlak has quit IRC21:28
ttxdanwent: hi!21:28
danwenthi21:28
ttx#link https://launchpad.net/quantum/+milestone/grizzly-321:28
danwentyeah....21:28
*** psedlak has joined #openstack-meeting21:28
ttxNot so much progress in stuff under review, afaict21:28
danwentwell, the good news is that all of our 'high' items have code posted.21:28
danwentbut for the overall bulk, very little progres over the week.21:28
ttxCould you give us an update on how close we are to merging those ?21:28
danwentyes21:28
ttx(the high stuff)21:28
ttxdanwent: it's my understanding that you would require Feature freeze exceptions only for the 'High' priority stuff here, if it doesn't make it in time. Correct ?21:29
danwenthttps://blueprints.launchpad.net/quantum/+spec/quantum-v2-api-xml: very close.  just minor design discussions.21:29
danwentyes, that is correct.  anything that is not high will be booted next week if not in code review, and booted completely the next week if it does not merge.  no exceptions.21:29
danwenti fully expect the majority of medium items not to merge.21:29
*** psedlak has quit IRC21:30
*** psedlak has joined #openstack-meeting21:30
*** psedlak has quit IRC21:30
danwenthttps://blueprints.launchpad.net/quantum/+spec/quantum-security-groups-iptables-ovs .  quantum code review is basically done.  waiting on two nova issues.21:30
*** psedlak has joined #openstack-meeting21:30
danwentone is: https://bugs.launchpad.net/nova/+bug/105043321:30
uvirtbotLaunchpad bug 1050433 in nova "LibvirtBridgeDriver crashes when spawning an instance with NoopFirewallDriver" [High,In progress]21:30
*** joesavak has quit IRC21:30
danwentthe other is: https://bugs.launchpad.net/quantum/+bug/111291221:30
uvirtbotLaunchpad bug 1112912 in nova "get_firewall_required should use VIF parameter from quantum" [Undecided,Confirmed]21:30
*** sdake_z has quit IRC21:31
ttxvishy: ^21:31
*** sdake_z has joined #openstack-meeting21:31
danwenthttps://blueprints.launchpad.net/quantum/+spec/quantum-scheduler .  A lot of review progress on this.  I am confident about this, though the dev will be out for a chinese holiday next week, which puts some pressure on us (though he said he will continue to work on this through the holiday)21:31
*** psedlak has quit IRC21:32
danwentthe last two blueprints are the LBaaS stuff, the second of which was just posted for review yesterday21:32
danwenthttps://blueprints.launchpad.net/quantum/+spec/lbaas-agent-and-rpc21:32
*** sleepsonthefloor has joined #openstack-meeting21:32
ttxok21:32
danwenthttps://blueprints.launchpad.net/quantum/+spec/lbaas-haproxy-driver21:32
ttxShould https://blueprints.launchpad.net/quantum/+spec/nvp-port-security-extension be considered 'Implemented' ?21:32
*** psedlak has joined #openstack-meeting21:32
danwenti'm starting to get a bit nervous about the lbaas stuff, as the original code was a fair bit different than what the cores where expecting. But we talked through it on IRC yesterday, so I think we're heading in the right direction.  Definitely the one i'm most worried about though in terms of possibly needing a FFE.21:33
*** jchiles has joined #openstack-meeting21:33
ttxdanwent: it's relatively self-contained I suspect ?21:33
danwentttx: looks like that BP should be implemented. i'll confirm with the dev and change it.21:33
ttxShould I confirm the series goal for routed-service-insertion to "grizzly" ?21:34
ttx(it's 'proposed' right now)21:34
danwentttx: yes, lbass is essentially entirely self-contained, which is nice from an FFE perspective, if needed.21:34
*** psedlak has quit IRC21:34
danwentyes please21:34
ttxwilldo21:34
*** psedlak has joined #openstack-meeting21:34
danwentthat one a new one (hopefully the last)21:34
ttxAnything else on Quantum ?21:34
danwentone question for the community21:34
danwentwe are looking at how to version our python-quantumclient stuff.21:35
danwenti'd like it to be as inline with the rest of the community as possible.21:35
danwentwas wondering if there was a "standard" mechanism used by other projects.21:35
*** henrynash has quit IRC21:35
ttxdanwent: bcwaldon had a pretty strong feeling about that21:35
danwentok, i will loop him into the discussion with our sub-team lead for clientlib + CLI21:35
ttxok, moving on, answer on #openstack-dev to Dan's question on versioning21:36
ttx#topic Cinder status21:36
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:36
ttxjgriffith: hi!21:36
jgriffithhey there21:36
ttx#link https://launchpad.net/cinder/+milestone/grizzly-321:36
ttxEvery week I discover more blueprints in here :)21:36
ttxHow is volume-backups going ?21:36
jgriffith:)21:36
jgriffithGood21:36
jgriffithA few minor nits to fix up21:37
ttxHow about api-v1-v2-docs ?21:37
jgriffithThat's going well too...21:37
ttxDo you think you need to drop anything early to focus review efforts on the priority stuff... or you can trust cinder-core to prioritize properly ?21:37
jgriffithI'm fairly comfortable with what's left21:37
jgriffithBut I am worried about what the NFS folks are cookin up21:37
jgriffithI fear a 10K line patch dropping next wed from them21:38
ttxFYI you have 4 drivers + one other bp targeted to g3 which are not in the series goal: huawei-volume-driver, scality-volume-driver, coraid-volume-driver, glusterfs-support, volume-usage-metering21:38
ttxthis morning when I looked up there were only 3 :)21:38
jgriffithYeah, I'm not seeing good progress on those guys so I'm giving them til tomorrow then dumping21:38
*** kspear has joined #openstack-meeting21:38
ttxit's high season for surprising code drops21:38
jgriffithI need to catch up with eharney on the gluster patch21:39
ttxDo you see anything in there you'd request feature freeze exceptions for, if they would not make it by grizzly-3 ?21:39
jgriffithThe only one is my AZ/Aggregates BP21:39
jgriffiththe rest I personally think I can live without21:39
*** jpich has joined #openstack-meeting21:39
ttxjgriffith: which one is that ?21:39
ttxjgriffith: could you prioritize it at least to 'high' ?21:40
jgriffithwill do21:40
jgriffithTBH, I can call that a bug anyway if need be21:40
ttxAnything more in Cinder ?21:40
jgriffithNope looking ok21:40
ttx#topic Nova status21:40
*** openstack changes topic to "Nova status (Meeting topic: project)"21:40
ttxvishy: o/21:40
ttxrussellb is down, Flusdem got him21:41
ttx#link https://launchpad.net/nova/+milestone/grizzly-321:41
ttxdo we have vishy ?21:41
rainyaget down get funky21:41
*** psedlak has quit IRC21:41
ttxgabrielhurley: around ?21:41
gabrielhurleyhi21:42
ttx#topic Horizon status21:42
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:42
ttxlet's do horizon first21:42
ttx#link https://launchpad.net/horizon/+milestone/grizzly-321:42
gabrielhurleyon the blueprints:21:42
gabrielhurleyThe 7 in code review will likely all merge this week. The 3 in "good progress" I've got updates from the assignees and they should be up for review soon. The 2 that are "started" are both in good shape and I know where the authors are at but they're optional for the release; if they don't make it no harm is done. Lastly, I am worried about the two related to file/image uploads. Saw early code and progress, but haven't g21:42
gabrielhurleyOverall, anything I don't see code for by next week I'm going to untarget.21:42
*** stevebaker has quit IRC21:42
ttxgabrielhurley: Do you see anything in there you'd request feature freeze exceptions for, if they would not make it by grizzly-3 ?21:43
gabrielhurleythe image uplaod stuff would be the only one21:43
gabrielhurleyI'd really like to see that happen21:43
*** psedlak has joined #openstack-meeting21:43
gabrielhurleybut I need more info21:43
ttxhmm ok, would be really good to see progress on that then21:43
gabrielhurleyagreed21:43
ttxAnything more on Horizon ?21:43
gabrielhurleyI'm trying to follow up21:43
*** psedlak has quit IRC21:43
gabrielhurleynope, that's it for this week. thakns to everyone who got code up since last week!21:44
*** psedlak has joined #openstack-meeting21:44
*** psedlak has quit IRC21:44
ttx(the file upload stuff is a bit disruptive to land after g3, so it better be very close)21:44
vishysorry back21:44
*** noslzzp has joined #openstack-meeting21:44
ttx#topic Nova status21:44
*** openstack changes topic to "Nova status (Meeting topic: project)"21:44
gabrielhurleyduly noted21:44
ttxjust in time21:44
ttx#link https://launchpad.net/nova/+milestone/grizzly-321:44
ttxvishy: Should instance-actions be considered Implemented ?21:45
alaskinot yet21:45
alaskineeds an API extension which I'm finishing up now21:45
ttxLooking into the High-prio stuff now...21:45
*** patelna_ has joined #openstack-meeting21:45
ttxvishy: Are the db-* blueprints making good progress ?21:45
vishyno21:46
vishywell i don't think they will be "complete"21:46
ttxah. I see what you mean21:46
*** woodspa has quit IRC21:46
ttxGuess we'll just split them21:46
ttxthough db-archiving would be nice21:47
vishyyeah21:47
ttxthat's "completeable" I guess21:47
vishywe'll just have to see how it goes21:47
ttxIs no-db-compute still on track ?21:47
ttxi.e. all code proposed, just churning through reviews now ?21:47
vishyyes i think it is really close21:48
vishylike one review away21:48
ttxvishy: which one of those blueprints (if any) would you require a feature freeze exception for, if they don't make it in time ?21:48
ttxno-db-compute, db-archiving ?21:48
*** iben has joined #openstack-meeting21:49
vishyno none of the db ones21:49
vishyi would consider https://blueprints.launchpad.net/nova/+spec/nova-quantum-security-group-proxy21:49
vishyno-db-compute isn't at risk imo21:49
ttxok21:49
vishyi would also consider https://blueprints.launchpad.net/nova/+spec/improve-block-device-handling if it gets really close21:49
ttxmulti-boot-instance-naming still needs some assignee and love21:49
ttxor should we abadon it altogether at this point ?21:50
*** psedlak has joined #openstack-meeting21:51
vishyi think it is going to get abandoned for grizzly at this point21:51
vishysince no one wants to take it21:51
ttxok, will move it off if nobody takes it this week21:51
ttxor yo can beat me to it21:51
ttxYou also have your share of last-minute grizzly-3 suggestions: migrate-volume-block-migration, user-locale-api, encrypt-cinder-volumes, libvirt-aoe, pass-rxtx-factor-to-quantum21:51
ttxSome of those sound quite complex to me to be introduced from scratch at this point in the cycle21:51
* ttx would like an ideal world where all blueprints are submitted before the design summit21:52
vishyi'm going through those21:52
ttxand flying cars, too21:52
rustlebeei tried to start commenting on some of those, saying code better show up asap to have the slightest chance21:52
ttxrustlebee: you're alive ?21:53
rustlebeejust a little21:53
rainyai totes want flying cars21:53
ttxAny question on Nova ?21:53
*** psedlak has quit IRC21:53
*** psedlak has joined #openstack-meeting21:53
*** psedlak has quit IRC21:54
ttx#topic Incubated projects21:54
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:54
*** psedlak has joined #openstack-meeting21:54
ttxAny Heat/Ceilometer folk around ?21:54
sdake_zhi21:54
ttx#link https://launchpad.net/heat/+milestone/grizzly-321:54
ttxsdake: Do you plan to have a strict feature freeze at grizzly-3 ?21:54
sdake_znot much progress last week, 80% of the devs were at conferences21:55
*** same5336_ has joined #openstack-meeting21:55
sdake_zyes strict feature freeze21:55
ttxYou'll have to enforce it without my help, can't spread too much21:55
sdake_zwe may bounce blueprints if they dont make21:55
sdake_zif they dont make it21:55
ttxit's just a question of teaching core reviewers what's acceptable or not :)21:55
sdake_zheat is usable as is21:55
ttxHow are those resource-type-* blueprints progressing ?21:55
sdake_zyup i'll speak about it this week21:55
sdake_zwell we are blocked because we are having trouble with quantum21:56
ttxglad to see I'm not the only one21:56
sdake_zbut again devs out of town so only 1 day spent on unblocking so far21:56
ttxok21:56
sdake_zmain focus really for g3 is fixing bugs ;)21:56
ttxthat's all I had :)21:56
sdake_zwant heat to work well for features we have21:56
ttxnijaba: around ?21:56
*** iben has quit IRC21:56
*** psedlak has quit IRC21:57
*** psedlak has joined #openstack-meeting21:57
*** psedlak has quit IRC21:57
*** same5336 has quit IRC21:58
*** same5336_ is now known as same533621:58
ttxI guess not21:58
*** psedlak has joined #openstack-meeting21:58
*** psedlak has quit IRC21:58
*** psedlak has joined #openstack-meeting21:59
ttxnijaba: my only question was about feature freeze, if you planned to align it with the common one21:59
ttxthat will be for next week.21:59
ttx#endmeeting21:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:59
openstackMeeting ended Tue Feb  5 21:59:18 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-05-21.03.html21:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-05-21.03.txt21:59
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-05-21.03.log.html21:59
rainyawoohoo!21:59
ttxgabrielhurley: wow, I wouldn't have bet I'd finish in time this one21:59
heckjheh21:59
gabrielhurleyha21:59
ttxcan't wait until we have two more projects to fit in one hour21:59
ttxlooks like an experiment, how many projects does it need to trigger a RM burnout22:00
*** markvoelker has quit IRC22:00
rainyayou did great, ttx22:00
gabrielhurleyoooookay, horizon meeting time22:01
gabrielhurley#startmeeting horizon22:01
openstackMeeting started Tue Feb  5 22:01:12 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: horizon)"22:01
openstackThe meeting name has been set to 'horizon'22:01
*** flaper87 has quit IRC22:01
gabrielhurley#topic General status update22:01
*** openstack changes topic to "General status update (Meeting topic: horizon)"22:01
gabrielhurleyLots of code up for review at the moment22:01
gabrielhurleyI went through this morning and tried to make sure everything had feedback.22:02
gabrielhurleythere are several that need a second +2/approval22:02
gabrielhurleythe blueprints that have been posted are all looking good22:02
gabrielhurley#topic Blueprints and bugs22:02
*** openstack changes topic to "Blueprints and bugs (Meeting topic: horizon)"22:02
gabrielhurleyspeaking of blueprints22:02
mrungehi, just a short update, I also did my duty on reviews22:02
gabrielhurleyexcellent. thank you.22:02
mrungeso, we have several approved now22:02
*** same5336 has quit IRC22:02
gabrielhurleyyep, jenkins will churn away on them22:02
mrungeyupp22:03
*** same5336 has joined #openstack-meeting22:03
zykes-gabrielhurley: speaking of bps will the introspection land ?22:03
gabrielhurleyzykes-: no, that one got dropped out of Grizzly several weeks ago, sorry. It'll be an early-H feature22:03
zykes-awww :(22:04
gabrielhurleyyeah, I know. sadface.22:04
gabrielhurley;-)22:04
gabrielhurleyIn terms of remaining work to be done for Grizzly, we've got just over two weeks.22:05
gabrielhurleyThat means anyone who'd like to get their code in should get a review up by this time next week22:05
gabrielhurleyI know it's a big push to get to the end22:05
gabrielhurleybut the deadline's the deadline, and ttx doesn't like feature freeze exceptions. ;-)22:05
mrungeshould we do a combined test day or so?22:06
mrungejust to be sure, everything is tested then again?22:06
gabrielhurleyI generally go by the rule of "that's what the RC period is for"22:06
zykes-gabrielhurley: question also, is there support for the domain / project stuff and new quantum lbaas stuff ?22:06
gabrielhurleyzykes-: quantum LBaaS is in progress but not currently targeted. I will accept it if it's proposed in the near future. The quantum team is hard at work on it.22:07
*** martine has quit IRC22:07
gabrielhurleydomain management in keystone got hammered out too late for horizon to do much in adopting the v3 API, so that'll be H as well22:07
gabrielhurleyOverall, I'd like to see folks hammering on the blueprints for the next 1-2 weeks, and then we'll have time for a testing effort and bug bash in the RC phase. That's always the best time to polish.22:08
*** amotoki has joined #openstack-meeting22:08
zykes-that's kinda sad face that major features aren't landed in the UI22:09
gabrielhurleyzykes-: it's been that kind of dev cycle... horizon's a tricky project 'cuz our work is so dependent on other projects getting things nailed down in a reasonable timeframe.22:10
gabrielhurleyWe usually end up with a very busy final milestone because of it22:10
gabrielhurleyand only so much fits in22:10
gabrielhurleybut in a positive light, we've had a lot of new folks coming in during the last milestone and a half so that bodes very well for getting lots done in H! :-)22:11
amotokihi22:11
gabrielhurleyhi amotoki. how're things going in quantum-land?22:11
amotokiI just joined the channel. I am looking at the log.22:11
ttxgabrielhurley: yeah right, blame me :)22:11
gabrielhurleyttx: you're the best scapegoat22:12
gabrielhurleyamotoki: okay. no worries.22:12
gabrielhurleyis either davidlenwell or cody-somerville around?22:12
gabrielhurleyI'd really like to get an update on the file/image upload blueprints22:13
gabrielhurleyif not I'll follow up via email22:14
gabrielhurleycody-somerville was here a minute ago...22:14
cody-somervillei22:14
gabrielhurleyoh well. email it is.22:14
cody-somervilleer.22:14
cody-somervilleHey :)22:14
gabrielhurleyoh22:14
gabrielhurleyhi!22:14
cody-somervilleSo I need to sync up with David.22:14
cody-somervilleI've did the bit the allow one to upload an image like you can upload to swift through Horizon22:15
cody-somervillebut uploading multi-gig file that way isn't really realistic22:15
gabrielhurleyyeah22:15
gabrielhurleyit's certainly not ideal22:15
gabrielhurleybut it might be better to land it as such in G3 and document deployment considerations there22:15
gabrielhurleythen in H we can improve it22:16
*** heckj has quit IRC22:16
cody-somervilleOk. Was going to ask about that.22:16
cody-somervilleWas wondering if I should bother to implement some sort of streaming22:16
cody-somervilleor if we should get glance people to implement something similar to formpost that swift has22:16
gabrielhurleycan you do that in under two weeks? ;-)22:16
gabrielhurleyI was talking to brian waldon about that the other day22:16
cody-somervilleOne thing I noticed about formpost for swift is that the swift account has to have a temp key thingie set on it.22:16
gabrielhurleywe may see something of that nature in H22:16
gabrielhurleyI don't think we'd see it implemented in glance exactly like in swift (which has tons of legacy auth stuff going on), but it's not gonna be a grizzly feature22:17
gabrielhurleyand we could help shape the requirement/developemtn for that22:17
cody-somervilleIf we do the formpost bit for swift, is just creating a random temp url key on the swift account ok if there isn't one already? (I assume we can fetch the current key if there is one set).22:18
gabrielhurleyso yeah, I think as long as we thoroughly document the deployment considerations and security implications (and perhaps add a settings flag to enable/disable the direct upload form/modal) then merging it with a naive file upload is gonna be good enough for Grizzly22:18
gabrielhurleyfor swift that's fine as far as I know22:18
gabrielhurleycody-somerville: can you get a review up (even if it's still a little rough) by this time next week?22:19
gabrielhurleyI'd really rather not 11th-hour merge this one, ya know :-)22:19
cody-somervilleSure.  For the image-upload patch, the only thing remaining is some more tests plus UI consideration from David.22:20
gabrielhurleyawesome22:20
gabrielhurleythat's good news22:20
cody-somervilleI've only just added another input to the form for the file (and logic to handle only accepting one or the other). I assume we'll want to do something nicer looking with JS.22:20
gabrielhurleythat'd be ideal22:21
*** stevebaker has joined #openstack-meeting22:21
gabrielhurleyas noted, though, substance counts more right now. there's more time to polish afterward22:21
amotokigabrielhurley: about quantum we have 6 BPs now. summary is here: http://wiki.openstack.org/Network/Meetings#line-12722:21
*** psedlak has quit IRC22:22
cody-somervilleso this will implement image-upload but what exactly do we want to do for the file-upload-refux bp?22:22
cody-somerville*redux22:22
*** dwcramer has quit IRC22:22
gabrielhurleycody-somerville: I though part of davidlenwell's code was about a nice fancy upload widget. he showed me something back at the end of G2 that wasn't too far off...22:22
gabrielhurleyamotoki: I'm curious how the "network topology" blueprint is coming along? is that still gonna land in G3?22:23
gabrielhurleyI remember nachi's demo at the summit so I'm surprised it hasn't been proposed for review yet.22:24
amotokiI will ask nachi about its status.22:24
gabrielhurleythanks22:24
zykes-demo what ? :)22:24
cody-somervilleOk. Cool. So file-upload-redux is about the UI. Thought maybe there was work on the backend you wanted done for the spec.22:24
gabrielhurleyzykes-: it was a network topology visualization. cool stuff.22:24
mrungeoh, cool22:25
amotokigabrielhurley: perhaps he must be writng a unittests. i will ask him to update the status.22:25
gabrielhurleycody-somerville: the idea was simply to make a reusable UI widget so that file uploading was consistent across image upload, swift upload, etc. and have it be a good experience.22:25
gabrielhurleyamotoki: thanks. are there any of the other blueprints you are concerned about? it sounds like they're all going pretty well to me.22:26
amotokigabrielhurley: for other stuffs in quantum, quantum-lbaas has a steady progross and i am asking the status update to KC (from bigswitch)22:26
zykes-amotoki: is bsn involved in that stuff ?22:27
zykes-I thought it was some other oflks22:27
amotokizykes-: yes. they are woring on quantum-lbaas22:27
gabrielhurley#topic General discussion22:28
*** openstack changes topic to "General discussion (Meeting topic: horizon)"22:28
gabrielhurleyanything else people would like to cover? the blueprints were my main taopic.22:28
lchenggabriel: Does the rbac update to use the policy api going into G? :-)22:28
gabrielhurley*topic22:28
gabrielhurleylcheng: keystone still hasn't gotten the policy file rollup into the v3 API, so no.22:29
gabrielhurleythat is easily the most delayed feature I've ever dealt with22:29
gabrielhurleyI think it's been bumped out of three releases now22:29
gabrielhurleyE, F and G22:29
gabrielhurleybut given how far the v3 API came along in Grizzly I don't think it will escape from Havana22:30
*** jsavak has quit IRC22:30
lchengargh, I thought the policy api is already included in V3 API. Would be a nice feature to have.22:30
lchengThanks22:30
gabrielhurleypolicy API *for keystone* is included22:31
gabrielhurleybut we need the policy API for *all the projects*22:31
gabrielhurleythey didn't quite get there22:31
*** woodspa has joined #openstack-meeting22:31
*** woodspa has quit IRC22:31
lchenggot it.22:31
amotokigabrielhurley: about my quantum secgroup patch, some part (vm launching panel) may need to be splited and extended.22:32
*** woodspa has joined #openstack-meeting22:32
gabrielhurleyno problem22:32
amotokigabrielhurley: i have no concerns about others.22:32
lchengbtw,  I got the change-password bp. Would you like it to be included for G3?22:32
*** esker has quit IRC22:32
vkmcgabrielhurley, Before moving away from bp, I wanted to know your opinions about the tenant deletion blueprint https://blueprints.launchpad.net/horizon/+spec/tenant-deletion22:33
gabrielhurleylcheng: sure. put up a review22:33
lchengokay22:33
*** olaph has left #openstack-meeting22:33
*** olaph has joined #openstack-meeting22:33
gabrielhurleyvkmc: everything you've proposed for it sounds great. just the coding that remins, right? ;-)22:33
gabrielhurley*remains22:33
vkmcgabrielhurley, Yeah, but also I found that OpenStack allows to manage some resources that are available from the clients but not yet from Horizon (e.g. cloudpipes and agents in Nova, vips and members in Quantum). That is, that resources cannot be managed from the Dashboard. Should they be taken into account when deleting a tenant?22:34
gabrielhurleyI would say no for now, though it'd be good to make a note of that (probably comments in the code)22:34
gabrielhurleyI'd just be hesitant to start deleting anything from the dashboard that you can't *see* from the dashboard22:35
vkmcgabrielhurley, Fair enough22:35
vkmcgabrielhurley, I'd also appreciate some feedback regarding the UI http://imgur.com/a/I8zsu#022:35
vkmcgabrielhurley, I'm worried that it's too massive22:36
*** jchiles has quit IRC22:36
gabrielhurleylooks great but yeah, might be biting off more than you can chew for v122:36
gabrielhurleybut use your judgment on that part22:36
vkmcgabrielhurley, Great, I'll do that then22:37
*** markmcclain has joined #openstack-meeting22:37
gabrielhurleyexcellent22:37
gabrielhurleyanybody else?22:37
gabrielhurleygreat! good meeting everyone. keep up the hard work during the final stretch here. propose your code in gerrit, and I'll talk to you all same time next week!22:38
gabrielhurley#endmeeting22:38
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:38
openstackMeeting ended Tue Feb  5 22:38:16 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-05-22.01.html22:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-05-22.01.txt22:38
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-05-22.01.log.html22:38
*** olaph has left #openstack-meeting22:38
mrungethanks!22:38
jpichThanks everyone22:38
kspearcheers22:38
amotokihave a good day22:38
*** diogogmt has quit IRC22:38
*** dolphm has quit IRC22:38
vkmcThanks, good day!22:39
*** afazekas has quit IRC22:40
*** mrunge has quit IRC22:40
*** ewindisch has quit IRC22:40
*** kspear has quit IRC22:45
*** koolhead17 has quit IRC22:48
*** jpich has quit IRC22:48
*** gabrielhurley has quit IRC22:50
*** noslzzp has quit IRC22:51
*** gyee has joined #openstack-meeting22:53
*** otherwiseguy has quit IRC22:55
*** annegentle has quit IRC22:56
reedquestion from new developer: if one wants to run the full set of jenkins tests without sending a patch for review, where do they go?22:59
reedoops, wrong channel, sorry23:00
*** ryanpetrello has quit IRC23:04
*** john5223 has quit IRC23:05
*** rnirmal has quit IRC23:07
*** vipul is now known as vipul|away23:12
*** sarob_ has quit IRC23:14
*** dosaboy has joined #openstack-meeting23:17
*** gyee has quit IRC23:20
*** ewindisch has joined #openstack-meeting23:22
*** markvan has quit IRC23:24
*** sdake_z has quit IRC23:25
*** bru has quit IRC23:33
*** Gordonz has quit IRC23:34
*** ewindisch has quit IRC23:39
*** lbragstad has quit IRC23:40
*** mrodden has quit IRC23:40
*** ewindisch has joined #openstack-meeting23:41
*** fnaval has quit IRC23:46
*** mattray has quit IRC23:52
*** ewindisch has joined #openstack-meeting23:54
*** lloydde has quit IRC23:55
*** lloydde has joined #openstack-meeting23:58
*** lloydde has quit IRC23:59
*** tr3buchet has quit IRC23:59
*** lloydde has joined #openstack-meeting23:59

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