Tuesday, 2012-07-31

*** jakedahn_zz is now known as jakedahn00:06
*** nati_ueno has quit IRC00:06
*** dendrobates is now known as dendro-afk00:07
*** nati_ueno has joined #openstack-meeting00:08
*** Mandell has quit IRC00:13
*** rnirmal has quit IRC00:13
*** Transformer has joined #openstack-meeting00:15
*** Transformer has left #openstack-meeting00:16
*** s0mik has quit IRC00:18
*** dolphm has joined #openstack-meeting00:19
*** s0mik has joined #openstack-meeting00:21
*** dolphm has quit IRC00:23
*** s0mik has quit IRC00:23
*** dolphm has joined #openstack-meeting00:24
*** jakedahn is now known as jakedahn_zz00:25
*** danwent has quit IRC00:30
*** markmcclain has joined #openstack-meeting00:33
*** nati_ueno has left #openstack-meeting00:45
*** littleidea has quit IRC00:46
*** johnpur has left #openstack-meeting00:53
*** adjohn has quit IRC01:01
*** adjohn has joined #openstack-meeting01:05
*** novas0x2a|laptop has quit IRC01:05
*** jdurgin has quit IRC01:06
*** matwood has quit IRC01:08
*** markmcclain has quit IRC01:10
*** littleidea has joined #openstack-meeting01:14
*** ryanpetrello has joined #openstack-meeting01:14
*** ryanpetrello has quit IRC01:23
*** ryanpetrello has joined #openstack-meeting01:25
*** dolphm has quit IRC01:29
*** dolphm has joined #openstack-meeting01:37
*** dwcramer has joined #openstack-meeting01:41
*** os-beginner has joined #openstack-meeting01:42
*** os-beginner has quit IRC01:48
*** adjohn has quit IRC01:50
*** blamar has quit IRC01:51
*** anniec has quit IRC02:01
*** ryanpetrello has quit IRC02:04
*** matwood has joined #openstack-meeting02:05
*** maoy has quit IRC02:16
*** PotHix has quit IRC02:22
*** dolphm has quit IRC02:27
*** jakedahn_zz is now known as jakedahn02:27
*** gongys has joined #openstack-meeting02:30
*** gyee has quit IRC02:31
*** littleidea has quit IRC02:37
*** slim_ has joined #openstack-meeting02:49
*** slim_ has quit IRC02:55
*** matiu has joined #openstack-meeting02:57
*** matiu has joined #openstack-meeting02:57
*** rnirmal has joined #openstack-meeting03:02
*** matiu has quit IRC03:03
*** matiu has joined #openstack-meeting03:04
*** matiu has quit IRC03:07
*** matiu has joined #openstack-meeting03:07
*** matiu has joined #openstack-meeting03:07
*** jog0 has quit IRC03:16
*** matiu has quit IRC03:16
*** Mandell has joined #openstack-meeting03:16
*** matiu has joined #openstack-meeting03:18
*** matiu has joined #openstack-meeting03:18
*** dolphm has joined #openstack-meeting03:19
*** SumitNaiksatam has quit IRC03:26
*** blamar has joined #openstack-meeting03:28
*** SOURCE has joined #openstack-meeting03:50
*** SOURCE is now known as STICKY-DICKS03:54
STICKY-DICKSI'm Hairy03:54
STICKY-DICKSI'm Hairy03:54
STICKY-DICKSI'm Hairy03:54
STICKY-DICKSI'm Hairy03:54
STICKY-DICKSI'm Hairy03:54
STICKY-DICKSI'm Hairy03:54
STICKY-DICKSI'm Hairy03:54
STICKY-DICKSI'm Hairy03:54
STICKY-DICKSI'm Hairy03:55
STICKY-DICKSI'm Hairy03:55
STICKY-DICKSI'm Hairy03:55
STICKY-DICKSI'm Hairy03:55
STICKY-DICKSI'm Hairy03:55
STICKY-DICKSI'm Hairy03:55
STICKY-DICKSI'm Hairy03:55
STICKY-DICKSI'm Hairy03:55
*** STICKY-DICKS is now known as justin-bieber03:55
*** justin-bieber is now known as f03:55
*** f is now known as justin-bieber03:55
*** justin-bieber is now known as SHIKIS03:58
*** littleidea has joined #openstack-meeting04:08
*** dwcramer has quit IRC04:18
*** dolphm has quit IRC04:20
*** shang has quit IRC04:25
*** SHIKIS is now known as PigsSNIKER04:34
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:35
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
PigsSNIKERSNORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BITCHES04:36
*** shang has joined #openstack-meeting04:39
*** PigsSNIKER has quit IRC04:45
*** anniec has joined #openstack-meeting04:49
*** anniec_ has joined #openstack-meeting04:51
*** anniec has quit IRC04:55
*** anniec_ is now known as anniec04:55
*** maoy has joined #openstack-meeting04:59
*** dolphm_ has joined #openstack-meeting05:05
*** cp16net is now known as cp16net|away05:08
*** cp16net|away is now known as cp16net05:08
*** johnpostlethwait has joined #openstack-meeting05:10
*** gongys has quit IRC05:18
*** blamar has quit IRC05:21
*** dolphm_ has quit IRC05:44
*** mikal has quit IRC05:57
*** mikal has joined #openstack-meeting05:59
*** rnirmal has quit IRC06:03
*** littleidea has quit IRC06:07
*** GheRivero has joined #openstack-meeting06:10
*** danwent has joined #openstack-meeting06:32
*** salv-orlando has joined #openstack-meeting06:43
*** johnpostlethwait has quit IRC07:09
*** matwood has quit IRC07:13
*** salv-orlando has quit IRC07:13
*** milner has quit IRC07:13
*** blamar has joined #openstack-meeting07:27
*** milner has joined #openstack-meeting07:27
*** zhuadl has joined #openstack-meeting07:29
*** EmilienM has joined #openstack-meeting07:35
*** matiu has quit IRC07:38
*** salv-orlando has joined #openstack-meeting07:51
*** Mandell has quit IRC07:52
*** blamar has quit IRC07:58
*** salv-orlando has left #openstack-meeting08:00
*** zhuadl has quit IRC08:07
*** derekh has joined #openstack-meeting08:17
*** zhuadl has joined #openstack-meeting09:30
*** shang has quit IRC09:48
*** sandywalsh has joined #openstack-meeting09:52
*** sandywalsh has quit IRC09:52
*** shang has joined #openstack-meeting10:01
*** darraghb has joined #openstack-meeting10:30
*** zhuadl has quit IRC10:43
*** mikal has quit IRC11:01
*** mikal has joined #openstack-meeting11:03
*** maoy has quit IRC11:22
*** dolphm has joined #openstack-meeting11:30
*** rkukura has left #openstack-meeting12:08
*** markmcclain has joined #openstack-meeting12:26
*** goldfish has quit IRC12:29
*** markmcclain has quit IRC12:30
*** alexpilotti has joined #openstack-meeting12:33
*** darraghb has quit IRC12:36
*** darraghb has joined #openstack-meeting12:39
*** dprince has joined #openstack-meeting12:41
*** dprince has quit IRC12:55
*** mancdaz has joined #openstack-meeting12:57
*** zhuadl has joined #openstack-meeting13:11
*** dendro-afk is now known as dendrobates13:11
*** pnavarro has joined #openstack-meeting13:13
*** littleidea has joined #openstack-meeting13:25
*** markmcclain has joined #openstack-meeting13:30
*** dabo has joined #openstack-meeting13:31
*** hggdh has joined #openstack-meeting13:34
*** dprince has joined #openstack-meeting13:35
*** dendrobates is now known as dendro-afk13:35
*** ryanpetrello has joined #openstack-meeting13:42
*** littleidea has quit IRC13:42
*** littleidea has joined #openstack-meeting13:43
*** hggdh has quit IRC13:44
*** blamar has joined #openstack-meeting13:53
*** dolphm has quit IRC13:53
*** Mandell has joined #openstack-meeting14:01
*** blamar has quit IRC14:05
*** mattray has joined #openstack-meeting14:06
*** mdomsch has quit IRC14:13
*** hggdh has joined #openstack-meeting14:17
*** Mandell has quit IRC14:19
*** zhuadl has quit IRC14:20
*** jaypipes has quit IRC14:24
*** jaypipes has joined #openstack-meeting14:27
*** creiht has quit IRC14:29
*** markmcclain has quit IRC14:30
*** primeministerp has joined #openstack-meeting14:34
*** ociuhandu has joined #openstack-meeting14:36
*** danwent has quit IRC14:37
*** blamar has joined #openstack-meeting14:43
*** dolphm has joined #openstack-meeting14:51
*** jakedahn is now known as jakedahn_zz14:53
*** creiht has joined #openstack-meeting14:56
*** jakedahn_zz is now known as jakedahn14:59
primeministerpOpenstack/Hyper-V discussion to begin in a couple of minutes14:59
openstackMeeting started Tue Jul 31 15:00:07 2012 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** jakedahn is now known as jakedahn_zz15:00
primeministerp#topic Hyper-V15:00
*** openstack changes topic to "Hyper-V"15:00
primeministerpHowdy everyone15:00
primeministerpI sent out the topics for discussion to the list15:00
primeministerp•Status of the Mock Hyper-V Compute15:01
primeministerp•Move  from Essex to Folsom15:01
primeministerpoInstaller is for essex integration15:01
primeministerp•Hyper-V Testing Procedures15:01
primeministerpoDev stack for hyper-v testing15:01
primeministerpoChef for Windows automation15:01
primeministerpWe'll go through those now15:01
primeministerp#topic Hyper-V Moc driver15:02
*** openstack changes topic to "Hyper-V Moc driver"15:02
*** s0mik has joined #openstack-meeting15:02
primeministerpAlessandro and I have been working to put together a plan of attack15:02
primeministerpalexpilotti: care to add some input15:02
primeministerpIn a nutshell he is in the process of the implementing the wmi moc interface15:03
*** matiu has joined #openstack-meeting15:03
*** danwent has joined #openstack-meeting15:04
primeministerpalexpilotti: needs a minute15:05
primeministerpwe'll come back to this15:05
primeministerp#topic Upstream Code integration15:05
*** openstack changes topic to "Upstream Code integration"15:05
*** blamar has quit IRC15:06
*** blamar has joined #openstack-meeting15:06
primeministerpWork needs to begin to integrate the upstream code15:06
primeministerppnavarro: is this something you can begin looking at15:06
primeministerppnavarro: we know we have issues w/ the glance, python-novaclient15:07
* primeministerp looks up the other15:07
pnavarroprimeministerp: yes we have, some packages are not compatible with windows15:07
primeministerppnavarro: right15:07
primeministerpso wee need to flush those out15:07
alexpilottihi guys!15:07
primeministerpand have the code put in to exclude it15:08
primeministerpalexpilotti: great15:08
alexpilottipnavarro: hi!15:08
pnavarrohi alexpilotti15:08
primeministerppnavarro: i'll be able to flush this out once testing is underway15:08
primeministerppnavarro: and hopefully supply useful bits for bugs15:09
primeministerppnavarro: can you expand on what you know?15:09
*** s0mik has quit IRC15:09
primeministerpno hitesh today15:10
primeministerpso I guess what needs to happen is people need to manually install the bits15:11
primeministerpto see exactly these incompatibilites exist15:11
alexpilottipnavarro: do you have a list of the packages that were incompatible in your setup?15:11
primeministerpand then notify the people upstream15:11
primeministerpalexpilotti: i Have that15:11
primeministerpalexpilotti: at least some of it15:11
alexpilottipnavarro: I'd like to cross check as well so we can file up the relevant bugs15:11
primeministerpone sec15:11
pnavarrofrom glance, xattr and pysendfile are incompatible15:12
primeministerpthis is whyat i have15:12
primeministerpglance 2012.215:12
*** rnirmal has joined #openstack-meeting15:12
*** blamar has quit IRC15:12
primeministerpanyjson 0.3.2+15:13
*** blamar has joined #openstack-meeting15:13
alexpilottipnavarro: pysendfile and xattr are dependencies of another package I guess. Glance itself?15:13
pnavarroalexpilotti: yes, they are dependencies introduced in glance Folsom15:13
primeministerppnavarro: then we need to file an upstream bug asap15:14
primeministerppnavarro: do you have enough data to file a bug15:14
pnavarroprimeministerp: but, it can be considered as a bug?15:14
primeministerppnavarro: well we need to make someone aware15:14
primeministerppnavarro: or we need to fix it15:14
primeministerppnavarro: do we need to include new deps15:15
pnavarroprimeministerp: what it's clear, they need to be considering windows when introducing new deps15:16
primeministerppnavarro: correct15:16
primeministerpjaypipes: ping15:16
jaypipesprimeministerp: pon15:16
pnavarroprimeministerp: if filing a bug it's the way... why not...15:17
alexpilottipnavarro: I'm going to do a full folsom setup so that we can compare the results15:17
primeministerpjaypipes: is filing a bug the best way to get windows considered when creating deps15:17
primeministerper introducing deps15:17
primeministerpfor example15:17
alexpilottipnavarro: xattr afaik is a Linux specific package15:17
primeministerpglance now requires xattr15:17
alexpilottipnavarro: *nix non linux15:17
primeministerpwhich is a *nix only package15:17
primeministerpand breaks hyper-v integration15:18
jaypipesprimeministerp: glance does NOT require xattr. I specifiically removed the xattr requirement so that the image cache could work on windows.'15:18
primeministerpo sorry15:18
alexpilottipnavarro: if that's the case, we have to get it out of Glance, starting w a temporary patch workaround15:18
primeministerpjaypipes: something is requiring xattr15:18
primeministerpjaypipes: is that in the current versions?15:18
primeministerpjaypipes: maybe we haven't tried w/ the newer stuff since then15:19
pnavarrojaypipes: i found it in pip-requires in F2 tar.gz15:19
jaypipesprimeministerp: well, I'm positive xattr is not needed :) perhaps this is a packaging thing? maybe xattr has been left in the packaging deps by accident.15:19
jaypipesprimeministerp: you could certainly file a bug to remove it from pip-requires (and put it in test-requires)15:19
primeministerppnavarro: can you add your data to a new bug re: ^^^^15:20
jaypipesprimeministerp: best to file a bug, sure, and assign it to me.15:20
primeministerpjaypipes: thanks!!15:20
jaypipesprimeministerp: I'll move it from pip-requires to test-requires, but I'll bring mtaylor in to ensure it's not listed in any package deps.15:20
pnavarrojaypipes: and what about pysendfile, it's used?15:20
jaypipespnavarro: not a requirement, same as xattr..15:21
jaypipespnavarro: it's used if available, ignored if not.15:21
alexpilottipnavarro: were you using the installer for setting up the environment?15:21
primeministerppnavarro: can you cc me on the bug as well15:22
pnavarroprimeministerp: ok !15:22
primeministerppnavarro: perfect15:22
primeministerppnavarro: thx15:22
*** dwcramer has joined #openstack-meeting15:22
primeministerpjaypipes: ok15:22
pnavarroalexpilotti: That happened when jordan installer version was installing Folsom versions of glance15:23
alexpilottijaypipes: what version of Glance should we use for Folsom?15:23
jaypipesalexpilotti: Folsom :)15:24
mtaylorjaypipes, primeministerp: I am not the right person for removing it from pacakge deps15:24
alexpilottijaypipes: lol15:24
mtaylorbut I support the moving of it to test-requires15:24
jaypipesmtaylor: zul?15:24
mtaylorjaypipes: yah15:24
jaypipesmtaylor: gotcha. will do.15:24
mtaylorjaypipes: and whoever does stuff for redhat15:24
primeministerpayoung: ping15:25
ayounghey primeministerp15:25
zulmtaylor: hmm?15:25
primeministerpjaypipes: we need someone from rh in the discussion for removing it from package deps?15:25
ayoungprimeministerp, is this a nova thing?  markmc is your man15:25
primeministerpayoung: thx15:26
primeministerpmtaylor: is zul the person to talk to re: the package deps?15:26
jaypipesprimeministerp: yeah, but I'll take care of that if you assign me the bug15:26
primeministerpjaypipes: perfect15:26
primeministerpwe'll move on15:27
primeministerplet's note bug to be filed, assigned to jaypipes15:27
primeministerp#topic hyper-v moc interface15:27
*** openstack changes topic to "hyper-v moc interface"15:27
*** dtroyer has quit IRC15:28
pnavarrojaypipes: what's your launchpad ID ?15:28
primeministerppnavarro: should be jaypipes15:28
primeministerpi believe15:28
primeministerppnavarro: if you paste the link to the bug I can add it to the meeting notes15:29
primeministerpjaypipes: launchpad id for pnavarro15:29
primeministerpto add you to the bug15:29
uvirtbotLaunchpad bug 1031396 in glance "xattr and pysendfile dependencies broke Hyper-V integration" [Undecided,New]15:29
primeministerp#link https://bugs.launchpad.net/glance/+bug/103139615:30
*** ayoung has quit IRC15:30
primeministerp#topic hyper-v/chef15:30
*** openstack changes topic to "hyper-v/chef"15:30
primeministerpok let's dicuss work to automate the provisioning and prep for a hyper-v compute node15:30
primeministerpI have implemented the chef infrastructure in my lab and began the process of gathering15:31
primeministerpall the windows chef recipes we can use as a base for our hyper-v efforts and ci integration15:31
*** s0mik has joined #openstack-meeting15:31
primeministerpmattray: is from opscode and he has offered to help us in this process15:32
*** gyee has joined #openstack-meeting15:32
*** ryanpetrello has quit IRC15:32
mattrayok, let me level set real quick15:33
primeministerpmattray: yes15:33
primeministerpmattray: please do15:33
pnavarrojaypipes: I couldn't change the assignee of the bug to you15:33
primeministerpmattray: i was thinking from a guidence perspective15:33
mattrayopscode.com/openstack describes the Chef for OpenStack project and links to the ML and IRC channel15:33
mattraywe have a WIP for deploying openstack with chef based on Rackspace's cookbooks15:33
*** heckj has joined #openstack-meeting15:33
primeministerpmattray: are those specific to essex?15:34
mattraylots of folks are working on it, the key is that it's very modular and Chef already has good support for Windows15:34
mattraycurrently, Folsom work probably starts next week15:34
primeministerpmattray: exactly i'm using the existing cookbooks as a base15:34
primeministerpmattray: execelent, our work is specifically for configuring a hyper-v node to work w/ our openstack compute driver15:34
mattraythere is a nova/compute recipe that I plan on pulling all the kvm support out and into another cookbook15:35
primeministerpmattray: interesting15:35
mattrayonce that supports pluggable back-ends, hyper-v will be a reasonable backend15:35
mattray(initially it will be lxc and kvm)15:35
mattrayjust following the same patterns15:35
primeministerpmattray: execelent15:35
mattrayyou also need glance-client right?15:35
mattrayand keystone-client?15:36
primeministerpmattray: no15:36
*** ayoung has joined #openstack-meeting15:36
primeministerpmattray: we only install nova15:36
alexpilottimattray: no, we don't15:36
pnavarromattray: opscode openstack cookbooks are the same that crowbar ones?15:37
mattraypnavarro: no15:37
mattraypnavarro: forked off awhile back by Rackspace15:37
mattrayDell is coming back to these eventually15:37
alexpilottipnavarro: I just did a pip install glance on a clean VM15:37
primeministerpmattray: then we should coordinate15:37
alexpilottipnavarro: I can confirm that I had the same error you had15:37
mattrayprimeministerp: definitely.15:38
alexpilottipnavarro: there's an xattr dependency15:38
pnavarroalexpilotti: thanks to confirm !15:38
primeministerpmattray: so when i add our building out of nova-compute15:38
jaypipespnavarro: I'll assign myself...15:38
pnavarrojaypipes: ok, thanks !15:38
alexpilottijaypipes: I did pip install glance, I confirm the xattr dep15:38
primeministerpmattray: i can hopefull use some of the upstream bits as well15:39
primeministerpmattray: specific to nova15:39
alexpilottijaypipes: for Folsom, should we get Glance from its github's active branch?15:39
alexpilottijaypipes: or can we relay on pip?15:39
jaypipespnavarro: done15:39
*** s0mik has quit IRC15:39
jaypipesalexpilotti: uhm... the client or the server?15:40
mattrayprimeministerp: sure. The loose plan is that sometime next week we'll start coordinating on folsom deployments and source builds. This will lend itself well to hyper-v support15:40
alexpilottijaypipes: client, running on hyper-v's nova-compute nodes15:40
jaypipesalexpilotti: from PIP.15:40
primeministerpmattray: are you expecting to have a nova chef deployment be agnostic15:40
alexpilottijaypipes: ok, we need a quick workaround to get rid of xattr15:41
primeministerpi just have a nova recipe and it is already platform independent15:41
jaypipesalexpilotti: yup, onit.15:41
alexpilottijaypipes: tx!15:41
*** dendro-afk is now known as dendrobates15:42
mattrayprimeministerp: I think we can work to accommodate deploying on Windows, either by attributing-out anything platform specific or with a separate recipe15:42
primeministerpmattray: ok then15:42
primeministerpmattray: i was going to build a seperate recipe15:42
mattrayprimeministerp: there will be a lot of recipes, we'll just have to have good documentation and roles to accomodate that15:42
primeministerpmattray: i'll continue on that path15:42
primeministerpmattray: hopefully I can reuse a lot of what's there and transliate it to windows15:43
primeministerpmattray: when you typicall deploy15:43
primeministerpmattray: are you doing it from package or source?15:43
primeministerpmattray: or both15:43
mattrayprimeministerp: currently packages. We're working on a strategy for source15:43
*** anniec has quit IRC15:43
primeministerpmattray: and for python deps, pip or also packages?15:44
mattrayall the above15:44
mattrayyou show up with the code, we'll find a way to accomodate15:44
primeministerpmattray: perfect15:44
primeministerpmattray: i'm going to need help running it15:44
mattrayas long as other stuff doesn't get broken, we'll kick to fit15:44
primeministerpmattray: at least from a understanding how to push to all nodes15:44
mattrayyeah, #openstack-chef is where we gather15:44
primeministerpmattray: ok i'll hop in there15:45
mattrayand I'm usually online, and #chef is full of 400+ helpful people15:45
primeministerpmattray: perfect15:45
primeministerpon that note15:45
primeministerplet's quickly go through the bits that need to be set for windows15:45
primeministerp1. disable all fw's15:46
primeministerp2. enable iscsi target svs15:46
primeministerp3. set ntp15:46
primeministerp4. set diskpart std policy15:46
alexpilottijaypipes: by looking at the install log, I notice that it has also "greenlet" as a dep15:46
primeministerp5. live migration enablement15:46
primeministerp6. enable powershell15:46
alexpilottijaypipes: building green let fails, I'm adding a comment to the bug15:46
primeministerppnavarro: anything else to add to that list15:47
pnavarroprimeministerp: it's ok for me15:47
primeministerp7. enable hyper-v role if server is not hyper-v server15:47
primeministerp8. configure bridge interfaces15:47
primeministerpthose are the specific for hyper-v15:48
alexpilottipnavarro: I noticed that compiling green let fails not (or not yet) xattr15:48
primeministerpfor nova, we have the following15:48
alexpilottipnavarro: *greenlet15:48
primeministerpthat needs to be addressed by chef15:48
primeministerp1. installation of python15:48
*** cp16net is now known as cp16net|away15:48
primeministerp2. pip install of python deps15:48
primeministerp3. install hv code from src15:49
primeministerp1 install python15:49
mattray1 & 2 sound like we need to update the python cookbook for windows support15:49
mattray#3 will probably use the git resource15:49
primeministerp2 run installation from the openstack hyper-v installer15:49
primeministerpmattray: i have one15:49
*** maoy has joined #openstack-meeting15:49
primeministerpmattray: that i found15:49
primeministerpmattray: i was planning on updating it today15:49
mattrayprimeministerp: cool15:50
primeministerpmattray: we use 2.7.x15:50
mattrayfeel free to follow up with me directly and I'll help get your patches upstreamed quickly15:50
primeministerpmattray: if i'm going send it upstream and I have to sign the contrib, it could take time15:51
primeministerpi'll have to get that into lcs15:51
mattrayyeah, we need to get on that ASAP15:51
primeministerper lca15:51
primeministerpmattray: do you have the link15:51
mattrayprimeministerp: wiki.opscode.com/display/chef/How+to+Contribute15:51
primeministerpmattray: how different is it than the openstack agreement15:52
mattrayit's the Apache CLA15:52
mattrays/Apache Foundation/Opscode, Inc./15:52
mattrayit got through VMware, Dell & HP so it's not impossible ;)15:53
primeministerpmattray: ok then, I'll start that process today15:53
primeministerpwe'll I guess we can use that as a base15:54
primeministerpI'll send out a email to the list as soon as my starting point is online15:54
primeministerpmattray: i'll send that to lca today15:54
mattrayok, I'll be sure to follow up on the posts outlining how we'll be collaborating15:54
primeministerpok let's see what's left to discuss15:55
primeministerp#topic Status of Hyper-V ci Infrastructure15:56
*** openstack changes topic to "Status of Hyper-V ci Infrastructure"15:56
primeministerpgood news15:56
primeministerpI have been given an asa and have configured it to support the circuit i am waiting to be pulled to my rack15:57
*** cp16net|away is now known as cp16net15:57
primeministerponce that is done i will have control of the network infrastructure and can begin building out the pxe infrastructure to support the deployment of the hyper-v nodes15:57
primeministerpadditionally i have provisioned vpn access throught the asa15:58
primeministerpfor individuals to debug15:58
pnavarroprimeministerp: that's great !15:58
primeministerpadditional work will need to be done to get a centralized auth infrasturcutre and other long term bits15:58
primeministerpas a start15:58
primeministerpwe have some something secured15:58
primeministerpto use15:58
primeministerponce I have this in place I will also be able to complete tie into gerrit, as I currenlty have no outbound ssh15:59
primeministerpanything anyone else want to add?15:59
*** dolphm has quit IRC16:00
*** dolphm has joined #openstack-meeting16:01
primeministerpif that it i'm ending the meeting16:02
primeministerpthanks everyone16:02
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"16:02
openstackMeeting ended Tue Jul 31 16:02:10 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-15.00.html16:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-15.00.txt16:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-15.00.log.html16:02
*** GheRivero_ has joined #openstack-meeting16:05
*** dolphm has quit IRC16:05
alexpilottijaypipes: green let dep gets solved by installing manually the win32 version before installing glance. At this point I hit the error on xattr, so it's consistent with pnavarro's envirnoment16:11
*** bencherian has joined #openstack-meeting16:17
*** markvoelker has joined #openstack-meeting16:27
*** Gordonz has joined #openstack-meeting16:32
*** _0x44 has quit IRC16:32
*** _0x44 has joined #openstack-meeting16:33
*** mattray has quit IRC16:34
*** kindaopsdevy has joined #openstack-meeting16:37
alexpilottiayoung: ping16:38
ayoungalexpilotti, whats up16:38
alexpilottiayoung: any suggestion in creating a fedora controller w the latest Folsom bits?16:38
*** mattray has joined #openstack-meeting16:39
ayoungalexpilotti, devstack works16:39
ayoungjust use FORCE=yes16:39
alexpilottiayoung: ok16:39
alexpilottiayoung: about this: http://fedoraproject.org/wiki/Features/OpenStack_Folsom16:39
alexpilottiayoung: do you know when the first packages will be available?16:40
ayoungalexpilotti, there are RPMs.  they will trail by a couple days, though16:40
ayoungalexpilotti, http://fedoraproject.org/wiki/Getting_started_with_OpenStack_on_Fedora_1716:40
jaypipesalexpilotti: greenlet doesn't have any relationship with xattr, AFAIK?16:41
alexpilottiayoung: great tx, but aren't the Fedora 17 packages Essex related?16:41
ayoungalexpilotti, hm...we have Folsom packages too.16:41
alexpilottijaypipes: nope, is just another Glance dep that fails to compile16:41
jaypipesalexpilotti: oh...16:42
alexpilottiayoung: ok, I still have to deploy a Fedora based controller, so sorry for the trivial questions16:42
alexpilottiayoung: Folsom packages are in a specific repository?16:42
ayoungalexpilotti, not a problem.  WHat do you mean by Controller?16:42
*** Mandell has joined #openstack-meeting16:42
*** kindaopsdevy has quit IRC16:43
*** kindaopsdevy has joined #openstack-meeting16:43
alexpilottiayoung: a VM containing all the OpenStack roles except compute16:43
ayoungalexpilotti, OK.  is this for testing?  Because Devstack is the easiest way to get that running16:44
ayoungBut if you want RPMS...let me ask16:44
*** jakedahn_zz is now known as jakedahn16:44
alexpilottiayoung: for development. I want to see if there are issues16:44
alexpilottiayoung: while I'll use for sure Devstack for general development16:45
*** markmcclain has joined #openstack-meeting16:45
*** Mandell has quit IRC16:48
ayoungalexpilotti, Rawhide (F18) only fro Folsom.  you should ask questions like these in #openstack-dev, BTW16:48
*** Mandell has joined #openstack-meeting16:48
*** ryanpetrello has joined #openstack-meeting16:48
*** johnpur has joined #openstack-meeting16:49
alexpilottiayoung: I read that F18 as introducing Folsom support. I'll post on the dev list, tx!!16:49
ayoungalexpilotti, yeah,  that would be about right.  I am going to try to spin up a F18 VM and see what happens..16:50
alexpilottiayoung: great, in case I'd also like to sign up for some early testing of Folsom on F18 :-)16:53
ayoungalexpilotti, let me first figure out how to get an F18 VM.  In the past, I've done upgrades from earlier versions of Fedora16:54
*** Mandell_ has joined #openstack-meeting16:54
ayoungalexpilotti, but please joim #openstack-dev...this room will be needed for meetings shortly16:54
alexpilottiayoung: already did it tx16:55
*** derekh has quit IRC16:57
*** Mandell has quit IRC16:58
*** jdurgin has joined #openstack-meeting17:11
*** anniec has joined #openstack-meeting17:13
*** kindaopsdevy has quit IRC17:20
*** s0mik has joined #openstack-meeting17:22
*** jog0 has joined #openstack-meeting17:22
*** kindaopsdevy has joined #openstack-meeting17:25
*** kindaopsdevy_ has joined #openstack-meeting17:25
*** bcwaldon has joined #openstack-meeting17:26
*** troytoman-away is now known as troytoman17:26
*** s0mik has quit IRC17:27
*** kindaopsdevy has quit IRC17:29
*** kindaopsdevy_ is now known as kindaopsdevy17:29
*** darraghb has quit IRC17:31
*** rafaduran has joined #openstack-meeting17:42
*** PotHix has joined #openstack-meeting17:43
*** oubiwann has joined #openstack-meeting17:47
*** Shrews has joined #openstack-meeting17:48
*** lcheng has joined #openstack-meeting17:52
ayoungWho is here for Keystone?17:57
ayoungheckj ?17:59
openstackMeeting started Tue Jul 31 18:00:51 2012 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
heckjOkay - let's get this ball rolling18:01
ayoung#topic domains18:01
heckjayoung was gracious enough to get us an agenda set up18:02
*** timchan has joined #openstack-meeting18:02
*** dolphm has joined #openstack-meeting18:02
* ayoung has to leave at about 1:45..so in a bit of a hurry18:02
heckjayoung: what's the domain topic?18:02
ayoungheckj, OK,  so Domains is gyee's bailywick.  I figured we should sort out what we are doing with them18:02
ayoungMy take is:  get them in in a minimal format18:03
ayoungno groups18:03
ayoungand first we need an agreement of what is acceptable/expected18:03
heckjayound: adding as extension to V2 API, or dependent on V3 API?18:03
gyeenot sure if anyone have a chance to look at my draft review18:03
ayounggyee, have you changed it recently?18:03
heckjI've glanced over it, but not read in depth18:04
*** dolphm_ has joined #openstack-meeting18:04
gyeewhy change it, its perfect :)18:04
ayoung#link http://etherpad.openstack.org/keystone-domains18:04
ayounggyee, since we are not doing a formal V3 for Folsom anyway, are you OK with doing it as an extension?18:05
heckjadding domains as an extension to V2 API isn't an issue, but changing the token format and output would be a significant API change - which I believe is needed to make it useful to external services18:05
ayoungWe can migrate Extension to V3 in Grizzly18:05
*** jlr has joined #openstack-meeting18:05
gyeeas of know, the code is parked in contrib18:05
gyeeso are we OK with the current impl?18:06
ayoungOIK,  so my understanding is that each user and tenant is owned by exactly one domain18:06
gyeeI heard rejection city the last go around18:06
ayounggyee, I heard arguing over details,  but I think that we were close to consensus18:06
liemmnFYI...  Guang's implementation would support the single-home user RBAC model, i.e., a user may have only one home domain.18:07
heckjIt's unclear that users need to be fully segmented as well - using the policy engine, we can get the same enforcement18:07
*** devananda has joined #openstack-meeting18:07
ayoungheckj, I see this as more "the eggs Policy usese to make omlettes"18:08
gyeeif we have the domain_id in the users, we can easily implement isolation18:08
ayoungyou have to put a user "somewhere"18:08
heckjand with the V2 API, the "admin" has uber-rights over everything18:08
ayoungonce we put them there, they stay there18:08
gyeeheckj, with my impl, domain admin can control their own domain18:08
gyeedomain admin is a role18:09
heckjYep - not asserting what your code does, asserting what current code and V2 API expectations are18:09
gyeemeaning user from one domain can have the domain admin role in multiple domains18:09
gyeewe are not doing anything outside the realm of RBAC18:10
ayoungheckj, is the question "a mechanism that is  domain specific" versus  "a mechanism based on the policy impl?"18:10
ayoungIE,  we can implement the domain spec using the policy code?18:11
heckj(in V3) I think we have everything we need to enforce the domain admin needs even down to users using policy18:12
heckjMy primary concern with gyee's current extension/V2 work is that I don't think we can meaningfully make this a V2 API extension18:12
heckjIf we start changing responses to the API, we'll get a lot18:12
heckjof pushback that the API needs to be revised/revisioned18:13
heckj(recent conversations related to changing the API and what that means to versioning)18:13
ayoungheckj, agreed that we are too late to do modifications of V2 APIs18:13
liemmnI think that domain is a core concept and should be part of the core, rather than an extension...  It is messier as an extension.18:13
ayoungliemmn, yes,  but not until V318:13
heckjliemmn: I'm totally with you - and I think it needs to flow all the way out ot all services (nova, glance, etc)18:13
liemmnhence, voting for v318:13
liemmn(as core)18:13
heckjI really appreciate gyee's work, but I think we'd be better getting identity wrapper and moved in a V3 API and get started with impl there18:14
gyeeI am OK with V318:14
gyeebut we have to have user isolation18:14
gyeewhich means domain_id in users18:14
ayounggyee, so long as it is an attribute, and not in the URL that should not break anything18:15
ayoungI think that meets the letter of the law WRT  dkranz's policy doc18:15
gyeedomain_id is an attribute of user, just like tenant18:15
*** pnavarro has quit IRC18:16
ayounggyee, so do you have enough to get a new impl out for review?18:16
gyeekeep in mind that having domain_id in user does not prevent user from *assigning* to tenants18:16
heckjgyee: I'm asserting that you can and do have domain isoliation of users with a reasonable use of policy.json. I don't think it's critical to enforce it in the data model as well18:16
liemmnWith domain model + domain_id on user, I think we can implement the user isolation as described in the KeystoneRoles doc ("single-home user" option)18:17
gyee^^^ what he said18:17
uvirtbotgyee: Error: "^^" is not a valid command.18:17
ayoungheckj, so to add a new domain, we would need to update policy.json ?18:18
gyeeI am ready to rock n roll if you guys are cool with it18:18
heckjayoung: not at all - just add a role & rule in policy.json that to add a user, reset a user, etc you need to be the domain admin for relevant tenants18:19
*** dolphm_ has quit IRC18:19
ayoungheckj, I think that domain_id would be default to null for most deployments, but be in the data model to be used in "multi domain deployments"18:19
*** dolphm has quit IRC18:19
*** nati_ueno has joined #openstack-meeting18:20
heckjIf the implementation you have completey segregates tenants and users are in tenants, you can use the default_tenant_id to determine the appropriate domain to use to verify for password resets and such18:20
ayoungheckj, but tenants can't be nested, and thus we don't have an organizational mechanism for tenants/18:20
heckjayoung: if it's null, then it can't be mandatory. If it's optional, then what's the difference between it and using the domain assocaited with the default tenant?18:21
heckjayoung: in this first cut, they can't be nested - but I think we all agree that we want to enable that in a future round18:21
gyeeheckj, have default_tenant_id as domain_id, we are essentially overloading the meaning of default tenant18:21
gyeenot very flexible18:21
gyeeand confusing18:21
liemmnheckj, I provided an argument against using default tenant for linking domain in the KeystoneRoles document.18:21
heckjgyee: I absolutely do not want to overload a value18:21
jlrdefault tenant is for scoping the token.  domainId is for isolating the user18:22
heckjI'm happy using them as a chain to look up relevant data, but the meaning of an attribute has to be crisp and clear18:22
gyeeso what's the problem with having domain_id and default_tenant_id as separate attributes?18:22
gyeethat's very clear18:22
*** danwent has quit IRC18:22
liemmnI think that is overloading the usage of default tenancy.  If I understand correctly, default tenancy is used for the purpose of authentication if a tenant is not specified.  A default tenant is also optional.  A user's "home domain" is not.  A user (except for a super-admin) must always have a "home domain."  So, I decided to introduce the concept of "home domain" for better separation of concern and enforcement of immutability.  To18:23
liemmnanswer your question:18:23
liemmn1) "can a user have a default tenant but a null home domain?" -> No, a user (except the super-admin) always has a home domain.18:23
liemmn2) "can a user's default tenant not belong to the user's in the user's home domain?" -> Yes, in the given proposal, user's default tenancy and home domain are 2 separate concerns.  For example, I have a guest tenancy in domain B and a home domain A.  However, whenever I log on, I always want to log onto the guest tenancy I have in domain B.  Therefore, I will set my default tenancy to guest tenancy in domain B.18:23
heckjgyee: that is clear - are you OK with asserting that domain_id is optional and can be null?18:23
gyeeI am OK with it being "null"18:23
heckjgyee: and thereby being also optional?18:23
gyeedeployment does not use domain doesn't need to set a domain_id18:23
ayoungheckj, I would state that for all domain_id = null we assume the default domain.18:23
ayoungAs opposed to any chained lookup18:24
gyeesounds good18:24
jlrit is an all or nothing thing... if it is used in a deployment, it is a mandatory field18:24
liemmnMaybe we can create a configuration to specify if the deployment is a "domain-aware" deployment (similar to PKI, for example)... If it is so, we will need to enforce non-null domainId when creating a user.18:24
heckjayoung: inconsistency is going to bite us there18:24
liemmnIt's a deployment option.18:24
gyeeI am OK with that18:25
heckjliemmn: and you're arguing to encode deployment options in the data model, which I'm not OK with18:25
ayoungheckj, you mean there is the potential for an inconsistnacy between the domain of the user (null) and the domain of the default tenant?18:25
liemmndata model is always there.18:25
heckjayoung: yes18:25
ayoungheckj, I would say that is an acceptable setup in some cases18:25
liemmnenforcement of non-null domainId is there... For a domain-aware install, a user without a domain does not make sense.18:25
ayoungsay a migration scenario18:25
heckjI'm ok with adding a domain_id attribute to the user *if* we assert it can be Null, and therefore is an optional attribute based on backend driver18:26
ayoungwhere a domain was not used in the past18:26
gyeehackj, +118:26
gyeeheckj, my bad18:26
ayoungheckj, I can buy that18:26
heckjnow I can't type18:26
liemmngyee spreaded the can't type bug18:26
ayoungOK.  gyee can you write up what we agreed on here in a couple short sentances and we';; # action them?18:27
gyeeits my middle finger18:27
gyeeayoung, you got it18:27
ayoungheckj, OK to move on to PKI?18:28
liemmnayoung, for migration from a non-domain deployment to a domain-aware one, we will need to lob all those users into some sort of default domain...18:28
ayoungliemmn, exactly18:28
heckjliemmn: +118:29
ayoungso there might be a point where a default tenant is part of a domain, but the user isn't or some other weirdness18:29
heckjayoung: yep18:29
heckj#topic PKI18:29
*** openstack changes topic to "PKI"18:29
ayoungfirst up is location of the cached certs18:29
ayoungit came to my attention that sticking them in /tmp is a no-no18:29
ayoungthere is a potential elevation of privs:  say a user on the Keystone system gets to /tmp/keystone-blah  ahead of time18:30
ayoungand sticks in their own cert18:30
ayoungthen they can authenticate using a bogus token18:30
ayoungSo the question is what should the default be?18:31
heckjayoung: any way we can make that a configurable option?18:31
ayoungheckj, it is already18:31
heckjayoung: ah, we're just talking about sensible default then18:31
ayoungthe question is what should the default be,18:31
heckjproposal: /var/lib/keystone18:31
ayoungI think /var/cache is slightly more correct18:31
ayoungbut then the issue is the user name18:32
gyeewhat's the issue with user name?18:32
ayounggyee, OK  possible race condition18:32
ayoungassume that there are two services running as the same user,  say nova18:32
ayoungand both get a request at the same time18:32
ayoungone fetches the certs, and starts writing18:33
ayoungthe other tests for existence of the files, which succeeds, and attempts to validate18:33
heckjayoung: I'm ok with /var/cache - sounds like you've got to deal with the async race regardless of directory18:33
ayoungvalidation will fail since they only have say, half a cert18:33
ayoungheckj, so, will /var/cache be acceptable across the distros?18:33
ayoungThere is nothing in there right now18:34
*** Gordonz has quit IRC18:34
heckjayoung: as far as I know, yeah - I'd poke a quick question at adamg or zul in #openstack-packaging if you want an ubuntu check18:34
ayoungwe'll have to modify any install process to make a writable subdir in there18:34
*** Gordonz has joined #openstack-meeting18:34
ayoungand I am not sure the correct general mechanism to do that18:35
ayoungso lets take that as a #action?18:35
liemmnayoung, you can use a touch file to specify that a cert has been written completely.18:35
ayoungliemmn, yep18:35
*** torgomatic has left #openstack-meeting18:35
heckjayoung: sounds reasonable18:35
ayoungliemmn, maybe even the cert fingerprint....18:36
gyeewe use fingerprint for out-of-band validation as well18:36
ayoung#action use the cert fingerprint as a touch file to indicate download has completed18:37
ayoungheckj, can I get ops to post?18:37
*** reed has joined #openstack-meeting18:37
heckjayoung: I'm being dense. "ops to post"?18:37
ayoungor, better yet,  you repost my #actions,  that way I get spellcheck :)18:37
heckj#action ayoung to18:38
heckj#action ayoung to use the cert fingerprint as a touch file to indicate download has completed18:38
heckjyou're going to hate this18:38
ayoung#action check with adamg or zul in #openstack-packaging about use of /var/cache for certificates18:38
heckj#action: ayoung to touch base with Zul/AdamG (or IRC #openstack-packaging or mailing list in general) to check on suitability of /var/cache/**/ directory creation on install18:39
ayoungheckj, you are wrong.  I love this18:39
heckjmore on PKI?18:39
ayoungOK...let me come back to acceptance criteria...18:39
ayoungtwo quick matters18:39
heckj#action: add domain_id as optional attribute to V3 API model on users18:39
ayoungone,  I've been told that the enable/disable for pki config options are poorly named18:40
ayoungthey don't like my double negatives18:40
ayoungso I am thinking:  token_format = PKI | uuid18:40
gyeeheckj, is the /v3 path implemented, where am I going to park the domain code?18:41
ayoungwith uuid being the equivalent of the current default18:41
ayounggyee, do you mean in the future?18:41
gyeenear future18:41
ayoungI would assume it would have to be part of the identity provider18:41
heckjgyee: It's be under the identity provider for a V3 api route18:42
gyeeoh ok18:42
ayoungOK, I have to disappear18:43
*** gabrielhurley has joined #openstack-meeting18:43
heckjayoung: ciao18:43
ayoungI'll start an etherpad for Summit sessions.18:43
ayoungWe can argue there and get it down to areasonable number18:44
ayoungunless there is a better suggestion?18:44
ayoungOK...I'm gone.  I'll beat you guys up over the rest of the Agenda items in #openstack-dev18:45
heckjOther topics/issues?18:46
gyeev3 api18:48
gyee(DELETE) /users/{user_id}/roles/{role_id} ==> delete_role_from_user18:48
gyeeif I assign the same role to multiple tenants, which role is the above deleting?18:48
gyeeall of them?18:48
liemmnunless the tenantId is part of the payload somewhere18:49
liemmnbut, that's not very restful18:49
gyeeright, same for domain roles as well18:49
heckjgyee: good question18:50
liemmnAlso... we need an update API for credentials (my feedback on draft#3)18:50
*** johnpostlethwait has joined #openstack-meeting18:50
liemmnso, to allow update to an access key, for example (enable/disable)18:51
gyeespeaking of access key, we are ready to start on the tempURL impl18:52
*** nati_ueno has quit IRC18:52
*** novas0x2a|laptop has joined #openstack-meeting18:52
*** nati_ueno has joined #openstack-meeting18:52
*** novas0x2a|laptop has quit IRC18:52
liemmnI've got to run... Later, heckj18:53
heckjgyee: I believe so18:53
*** danwent has joined #openstack-meeting18:53
heckjliemmn: I'll hit a draft update this week/weekend if nothing else18:53
gyeethen how do we remove just a tenant-role association?18:54
gyeeor domain-role association18:54
*** novas0x2a|laptop has joined #openstack-meeting18:55
heckjgyee: we should totally be able to do that - I need to re-read that section to see what the hell I was thinking18:55
gyeeoh ok :)18:56
heckjyeah - very distracted right now18:56
heckjIm going to wrap this up18:56
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"18:56
openstackMeeting ended Tue Jul 31 18:56:45 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-18.00.html18:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-18.00.txt18:56
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-18.00.log.html18:56
*** jlr has quit IRC18:57
*** ociuhandu has quit IRC18:59
mtaylorheckj: wait, what? you ... finished early/on-time?18:59
* heckj smacks mtaylor19:00
gabrielhurleyheckj, mtaylor: I can feel the love19:00
mtaylorgabrielhurley: we want to keep you amused19:00
openstackMeeting started Tue Jul 31 19:00:53 2012 UTC.  The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
mtayloranybody interested in CI?19:01
mtaylor#topic horizon19:01
*** openstack changes topic to "horizon"19:01
ShrewsCuddling Iquanas?19:01
mtaylorwhat is an Iquana?19:01
*** timchan has quit IRC19:01
Shrewssame as an Iguana, but more exotic19:01
* mtaylor forward-proposes the openstack I relase to be named Iquana, invoking the bcwaldon rule19:02
mtaylorok. so - gabrielhurley did you get a chance to read the email I sent this morning?19:02
gabrielhurleymtaylor: I did19:02
gabrielhurleyandI was thinking similarly about using selenium tests to ensure some of that stuff19:02
mtaylorgabrielhurley: excellent. that means less typing now19:02
gabrielhurleyit is a bit of a catch-22 though, where we need to test against the future changes but also against the current pip-requires lists...19:03
mtaylorit is. I think the key is to make sure that changes don't go in that _can't_ work with released libs19:04
mtaylorif the client libs start ganking with existing apis too much it'll screw all the other projects too anyway19:04
gabrielhurleyyeah, it just happened to be that we (Horizon) hit it first19:05
gabrielhurleyit's definitely not a horizon-only problem19:05
mtaylorand then, if someone is adding a new api call/feature to a client lib that you desperately need in horizon ...19:05
mtaylorthey need to cut a release19:05
gabrielhurleyBrian Waldon is pushing a new glanceclient release today19:05
mtaylordo you think there would be any value in running selenium tests against the devstack install too?19:05
jeblairgabrielhurley: he already did it, and it's on pypi!  0.2.019:05
gabrielhurleyjeblair: nice19:05
*** GheRivero_ has quit IRC19:05
gabrielhurleymtaylor: definitely value in that19:05
mtaylorgabrielhurley: k. I'll put that on the list of things for clarkb to think about19:06
jeblairmtaylor: one further question for clarkb to think about -- can it be incorporated into tempest, or does that make no sense.19:06
mtaylorthat is19:07
mtaylorclarkb: this is what happens when you go to lunch instead of this meeting - you get assigned things19:07
mtaylorgabrielhurley: cool. so I think we're set for now, until we think of something else19:07
gabrielhurleysounds good. we'll give it a try and revise as needed19:08
mtaylor#topic PTL's + client lib releases19:09
*** openstack changes topic to "PTL's + client lib releases"19:09
mtaylorjeblair: so - bcwaldon made a releaes because I explicitly added him to the acls for that project a few weeks ago, which is obviously the wrong way to do things19:09
*** novas0x2a|laptop has quit IRC19:10
mtaylorI believe the ML decision was to add $project-drivers to python-${projet}client  with tagging acls, yeah?19:10
*** novas0x2a|laptop has joined #openstack-meeting19:10
mtaylorso I think we can get that done - BUT - it brings up a thought...19:10
jeblairmtaylor: that makes sense to me19:11
mtaylorshould we manage the project ACL files int eh config branches with puppet?19:11
*** kindaopsdevy has quit IRC19:11
jeblairmtaylor: neat idea.19:11
mtaylorjeblair: I was thinking about it when I was making the "create a project" additions19:11
mtaylorsince the acls part is the most annoying part19:11
* mtaylor assigns clarkb to think about that when he gets back19:12
mtaylor#action clarkb manage project acls with puppet19:12
mtaylor#actoin clarkb think about running selenium against devstack19:12
mtaylor#action clarkb think about running selenium against devstack19:13
mtaylor#action clarkb think about running selenium in tempest19:13
mtaylorrecorded those19:13
mtaylor#topic renaming client libs19:13
*** openstack changes topic to "renaming client libs"19:13
mtaylornotmyname: you aroud?19:14
mtaylorzul: how about you?19:14
zularound? not really19:14
zulill lurk continue without me19:15
jeblairso the gist was that automated packaging scripts have problems with "python-fooclient" because they want to call the result "python-python-fooclient"19:15
notmynamemtaylor: here19:15
jeblairwhich isn't a problem for, say, ubuntu, who just pick the right name, but for individuals making their own .debs19:15
mtayloralso, we do already have a pile of extra logic in stuff to deal with the fact that some of our projects are named differently than their main module19:16
jeblairand i guess we should distinguish between the git repo name, and the setup.py name -- it's the setup.py name that the deb build scripts pick up, so that's what's being wanted to change.19:16
mtayloryes. it is not necessary that we change the git repo name - although I kinda think that if we change the one we should consider changing the other too19:17
notmynameIMO, the git repo name makes sense19:17
mtaylorhowever, this would affect the tarball name that we produce, which might affect ubuntu a little19:17
*** jgriffith has joined #openstack-meeting19:18
mtaylorand we should consider whether or not it should affect the launchpad project name19:18
jeblairright, so that brings up the question "why are they named python-fooclient?" is it because we might have an openstack/java-fooclient project someday?  if so, yeah, we might want to leave it as-is.19:18
mtayloryes. I believe that was the reason19:18
jeblairso, if we consider just changing the setup.py name, what breaks?19:18
mtayloralso, we'll need to make new pypi entries19:18
jeblair(but leaving the git repo name alone)19:18
mtaylorif all we change is the setup.py name19:18
gabrielhurleyif you change the setup.py name the names on PyPI will get screwed19:19
mtayloryeah - it'll be a whole new pypi thing19:19
gabrielhurleyyou'll need to update all the pip-requires in all the projects with the new names as well19:19
mtayloralthough that could be done in a rolling fashion19:19
gabrielhurleyI don't object to that, btw. just sayin' it's the case19:19
jeblairmtaylor: do tarball names come from that?19:19
jeblairso that would affect distros19:20
*** rnirmal has quit IRC19:20
mtayloryup - although we've pre f3, so I think it's maybe still ok?19:20
mtaylorttx: ?19:20
mtaylornotmyname: any sense of whether the other python-*client people have interest in following suit?19:21
jeblairmtaylor: i'm sure we'd have a whole bunch of puppet config files that would need changing, but that's probably not a huge deal.19:21
notmynameno idea. I got the request from people building python-swiftclient packages19:21
sorenI'm apparently missing some context.19:22
sorenWhat are we renaming from and to?19:22
mtaylorsoren: the suggestion is to make setup(name='python-swiftclient' be setup(name='swiftclient'19:23
mtaylorsoren: and, of course, if we think about that, we'd like to think about doing that across the board19:23
sorenAnd what's the motivation? Did I miss a mailinglist discussion?19:23
mtaylorbut leaving the git repo named the same19:23
mtaylormotivation is - apparently there are packaging tools for python which pull the python name from setup.py and pre-pend python- to it19:24
notmynamepackage building tools take the internal name (python-fooclient) and turn it into python-python-fooclient19:24
mtaylorso those are making python-python-swiftclient packages19:24
notmynamewhich implies that clients of the module are a python-python-swiftclient-client19:24
jeblairi'm sure those can change, but it does also seem weird that these are in pypi as "python-swiftclient" because it's obviously python.19:25
jeblairso it's certainly worth considering19:25
*** kindaopsdevy has joined #openstack-meeting19:25
sorenThere are hundreds of projects named python-* on pypi.19:25
sorenHow do they manage?19:25
jeblairthere are tens of thousands that aren't.  :)19:26
mtaylorthere are 58 things openstack depends on19:26
sorenjeblair: That's got to be the worst argument ever fo.19:26
sorenjeblair: For anything :)19:26
mtaylor3 of them that are not our projects are prefixed with python-19:26
mtaylorso I'd say that the general trend seems to be non-python prefixing for pypi modules19:27
mtaylorwith the one really odd-one out being MySQL-python which installs MySQLdb - but Andy is weird anyway19:27
jeblairsoren: i won't get into a meta-argument with you, i will just note that it was a rebuttal to your rebuttal to my _actual_ point that the name is redundant.19:27
sorenjeblair: It's not redundant. It's the python blahclient (as opposed to the java blahclient or haskell blahclient etc).19:28
sorenjeblair: How's it redundant?19:28
* mtaylor abstractly wants to be a meta-observer19:28
mtaylorsoren: it's redundant on pypi19:28
mtaylorsoren: it makes sense for the ubuntu package to be named python-${pypi-package-name}19:29
sorenI don't think that should dictate naming.19:29
*** s0mik has joined #openstack-meeting19:29
mtaylorI'm not saying that it should19:29
sorenSo what are you saying?19:29
*** sandywalsh has joined #openstack-meeting19:29
mtaylorpurely that, for the name whose main purpose is tarball naming and pypi project, python- isn't essential19:30
sorenI think it is. For tarball naming.19:30
mtaylorbecause we're likely, as a project, to produce ${foo}-novaclient where foo!=python ?19:31
sorenHaving the t at the end for client also isn't essential. In fact, it's redundant, because "clien" isn't a real world, and the context should reveal its true purpose.19:31
jeblairthat is a good point; the tarball exists in a similar context to the git repo, so its name having python- makes sense.19:31
*** markmcclain has quit IRC19:31
sorenmtaylor: Absolutely.19:31
sorenmtaylor: I'm surprised we don't already.19:31
jeblairto be clear, soren's point about tarball naming was a good point.  not "clein".  :)19:31
mtaylorwe make python libs becuase we're a python based projects19:31
mtaylorjava and ruby libs are silly19:31
mtaylorbecause ruby people should be using fog19:32
mtaylorand java people should be using jclouds19:32
mtaylorand even when they aren't19:32
mtaylorthe java project is named after openstack19:32
mtaylorand not after each project19:32
notmynamemtaylor: actually because the API isn't a language, it's HTTP. we simply provide wrappers for a particular language19:32
mtaylornotmyname: indeed. and we do that _purely_ because our projects need to be able to talk to each other19:32
mtaylorand then we use those libraries as the basis for command line clients ... but it isn't part of a larger decision to try to make openstack-project generated client libraries for all languages19:33
*** rnirmal has joined #openstack-meeting19:34
notmynamethis seems to be way off track. current proposal is to internally drop the language prefix and externally (the repo and maybe the tarball) to have the prefix? and what issue does that cause19:34
mtaylorbut - that's just my opinion, of course19:34
sorenmtaylor: Even if *we* don't create them, there's a great big world out there whose namespace we're sharing.19:34
mtaylorthe tarball name is generated from the name19:34
sorenIf someone wants to build php-glanceclient, more power to them.19:34
mtaylorsoren: no. I disagree. the only place it would matter is our tarballs ftp server19:34
mtaylorI cannot be responsible for a theoretical global namespace of tarballs19:34
mtaylorsoren: sure. and they can call it python-glanceclient for all I care19:35
mtaylornotmyname: so the reason we're ratholing19:35
mtaylornotmyname: is python setup.py sdist19:35
sorenmtaylor: Well, that's just silly. We pick the names fo things to avoid collisions with others.19:35
sorenHeck, half this discussion has been about other people's namespace!19:35
sorenPyPi and Ubuntu, to be exact.19:35
mtaylornotmyname: which bases its tarball name on what's in setup.py(name=19:35
notmynameya. like stdeb makes it python-<name from setup.py>19:36
sorenmtaylor: So don't give me the "we don't care about other people's namespace".19:36
mtaylorsoren: "we don't care about it for tarballs" - because there is no shared tarball namespace we need to care about19:37
mtaylorwe upload to a shared thing called pypi, and we kinda talk to the ubuntu people19:37
mtaylorbut I belive we are wandering19:37
mtaylorinto a meta argument again19:37
mtaylormore to the point - tarball name, setup(name= and pypi name are tied together19:37
mtaylorso, unless we want to get weird, changing one changes all three19:38
*** markmcclain has joined #openstack-meeting19:38
mtaylornotmyname: can we touch base with bcwaldon and jk0? I know I'm arguing against soren here, but that's probably just because it's fun - there is potentially a valid concern in there19:39
*** gabrielhurley has quit IRC19:39
jeblairmtaylor: perhaps we should take this to the ML?19:39
mtaylorand I doubt we're going to come to conclusion here right now19:40
mtaylorI think we know which things would change and where the issues might be19:40
notmynamemtaylor: ya, sure. like I said earlier, this certainly isn't an issue that's important enough to be different about. it's mostly an "awkwardness in naming" issue19:40
notmynamemtaylor: jeblair: thanks for talking through it19:40
*** littleidea_ has joined #openstack-meeting19:40
jeblairindeed, this has been useful to explore the issue, and i think it's worth finding out what others think19:41
*** markmcclain has quit IRC19:42
*** markmcclain has joined #openstack-meeting19:42
mtaylorok. so those were talky19:42
ttxmtaylor: what's the question ?19:42
mtaylor#topic statuses of stuff19:42
*** openstack changes topic to "statuses of stuff"19:42
mtaylorttx: we'll bring it back on ML or over in normal chanel19:42
*** littleidea has quit IRC19:42
*** littleidea_ is now known as littleidea19:43
*** dtroyer has joined #openstack-meeting19:43
mtaylora few quick status things:19:43
*** markmcclain1 has joined #openstack-meeting19:43
mtaylorI got a bunch of puppet module re-org done (yay) and we have some code in from Ryan_Lane to get our new wiki up and going19:43
mtaylorclarkb got selenium tests going against horizon19:44
mtaylorjeblair: did you accomplish anything worthwhile last week?19:44
jeblairzuul should be testing/merging changes in an optimal order now19:44
jeblairif that looks like it's working...19:44
jeblairi'll switch the CI repos to cherry-pick so we can dogfood that idea before proposing we change the rest of the projects19:45
jeblairand i finally have tests for zuul, so we can make changes to it without the _extremely_ laborious process of clicking around in jenkins and gerrit19:45
*** markmcclain has quit IRC19:46
mtayloranybody got anything else?19:47
devanandapatches for devstack and devtack-gate to support testing openvz have been proposed19:48
devanandajust waiting for reviews/etc now19:48
mtaylorif anybody around here has devstack review status, checking those out would be god19:48
Shrewsdevananda: is RS ready to push once those changes are in? i know daniel has already merged in my patches19:49
devanandaoh, and i did a pretty big re-org from something jaypipes pointed out (the openvz glance image gets handled just like the other images now)19:49
*** mnewby has joined #openstack-meeting19:49
devanandaShrews: whether or not they think they are, no, they're not19:49
devanandait fails several tests right now, most notably volume and snapshots19:49
Shrewsdevananda: ah, right19:49
devanandabut it's testing them, heh ;)19:50
*** reed has quit IRC19:50
*** thingee has joined #openstack-meeting19:50
Shrewswell, we might need to fix that ourselves19:50
devanandai think it won't be too hard, at least the volume stuff seemed *almost* there when I read it19:51
*** liemmn has quit IRC19:53
*** mcaway has joined #openstack-meeting19:54
jeblairmtaylor: endmeeting?19:55
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"19:55
openstackMeeting ended Tue Jul 31 19:55:20 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-19.00.html19:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-19.00.txt19:55
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-19.00.log.html19:55
*** mnewby has quit IRC19:55
*** patelna has joined #openstack-meeting19:57
ttxmtaylor: staying around for PPb to defend the supporting project list ?19:57
*** dolphm has joined #openstack-meeting19:58
*** mnewby has joined #openstack-meeting19:59
*** anotherjesse_zz is now known as anotherjesse20:01
bcwaldonttx: mtaylor is on a call, he says20:01
ttxChair chair20:02
ttxany other PPB member ?20:02
bcwaldonanotherjesse is around20:03
bcwaldonvishy is too20:03
ttxanotherjesse, danwent, devcamca-, jaypipes, johnpur... ?20:03
jaypipesttrifonov: o/20:04
jaypipesttx: o/20:04
*** dolphm has quit IRC20:04
ttxThat's 820:04
* ttx checks if that means quorum20:05
ttxlooks like it does, anyone volunteering to chair ?20:05
bcwaldonI nominate ttx20:06
ttxnothing like chairing two meeting in a row20:06
openstackMeeting started Tue Jul 31 20:06:29 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:06
bcwaldonttx: we know you can do it!20:06
ttxTwo topics on http://wiki.openstack.org/Governance/PPB20:06
*** Shrews has left #openstack-meeting20:06
ttx#topic API stability20:06
*** openstack changes topic to "API stability"20:06
ttxanyone up to defend this one ?20:07
mcawayso, it should be pretty straightforward20:07
ttxYour nick now sounds like some express takeaway at McDo.20:07
*** mcaway is now known as markmc20:07
markmcidea is that the project should make its stance on API stability a bit more clear20:07
markmcwith a "this is very important to OpenStack" statement20:08
*** ewanmellor has joined #openstack-meeting20:08
jaypipesmarkmc: ++20:08
markmcand, second, that the PPB should encourage folks to help out with a set of API guidelines20:08
markmcthe two links are20:08
ttxmarkmc: so this is our "yes we care" moment ?20:08
markmcttx, pretty much20:09
* markmc shrugs20:09
markmcthe guidelines thing will help a lot of we can flesh them out20:09
ttxok, any questions before we formally express whether we care about APi stability or not ?20:09
markmclooks like we had a nod to this before:20:09
vishyI support guidelines, although they clearly need some more editing20:09
markmc"Each successive implementation of the APIs should always be backwards-compatible;"20:10
markmcvishy, they certainly do20:10
vishyfor example, I don't think adding post parameters to an api without versioning is acceptable20:10
vishy(putting them in an extension is fine by me though)20:10
markmcah, there's a question20:11
markmcdo extensions fall under this?20:11
*** mnewby has quit IRC20:11
markmcI had presumed yes20:11
bcwaldonextensions should be thought of a mini-apis20:11
anotherjesseI think the "example" section is a great way of exploring the api space…20:11
markmcbcwaldon, with same or lesser API stability expectations?20:11
bcwaldonmarkmc: 'each successive implementation...' needs to be better defined20:11
bcwaldonmarkmc: same expectations20:11
markmcbcwaldon, that's an old proposal - just point it out for completeness20:12
bcwaldonmarkmc: versioned independently20:12
heckjanotherjesse: +120:12
vishymarkmc: extensions should be able to add things to requests and response, but I don' tthink they need any other requirements above that20:12
bcwaldonmarkmc: kk20:12
jaypipesvishy: what about adding a limit=XXX&marker=XXX post params? that would need API minor version increment, not major version increment, right?20:12
ttxThe proposal still needs work, at this point we are just saying whether we care20:12
bcwaldonwe absolutely care20:12
vishyjaypipes: sure although we haven't minor versioned any apis yet20:12
vishyjaypipes: so why not do it with an extension?20:12
bcwaldonfor me, its just been an understanding that we all care20:12
ttxand if our care extends to extensions20:13
markmcyeah, right now it's a question of whether the PPB agrees with the stance here:20:13
bcwaldonI guess we need to explicitly say what we care about?20:13
bcwaldonmarkmc: yes, lets vote20:13
ttxI think yes on both accounts is pretty much a given, but the proposals authors would like affirmative vote20:13
*** Ravikumar_hp has joined #openstack-meeting20:13
* ttx tries to remember how voting works20:13
markmcwell, not me actually :)20:13
jaypipesvishy: is the time when an extension is merged back into core something that is written down somewhere?20:13
* markmc always happy with rough consensus20:13
markmcwhich I figure we had anyway20:13
bcwaldonthats fine, nobody has said no20:14
ttx#startvote Agreement on proposed API Stability Statement: yes, no20:14
bcwaldonvoting just makes it obvious and records it in notes20:14
bcwaldon#vote yes20:14
jaypipes#vote yes20:14
vishy#vote yes20:14
johnpur#vote yes20:14
danwent#vote yes20:14
ttxwait the thing didn't work20:14
anotherjesse#vote yes20:14
Ravikumar_hp#vote yes20:14
patelna#vote yes20:14
anotherjesse#vote petunia20:14
notmynamettx: gotta have the "?"20:14
ttx#startvote Agreement on proposed API Stability Statement ? yes, no20:15
openstackBegin voting on: Agreement on proposed API Stability Statement ? Valid vote options are yes, no.20:15
openstackVote using '#vote OPTION'. Only your last vote counts.20:15
vishy#vote yes20:15
*** lloydde has joined #openstack-meeting20:15
bcwaldon#vote yes20:15
jaypipes#vote yes20:15
johnpur#vote yes20:15
ttxstart again, only PPB members vote please20:15
ttx#vote yes20:15
danwent#vote yes20:15
ttxnotmyname, anotherjesse ?20:16
anotherjesse#vote yes20:17
heckj#vote yes20:17
ttxclosing in 30 seconds20:17
notmyname#vote yes20:18
nati_ueno#vote yes20:18
openstackVoted on "Agreement on proposed API Stability Statement ?" Results are20:18
openstackyes (10): anotherjesse, bcwaldon, ttx, notmyname, vishy, heckj, jaypipes, johnpur, danwent, nati_ueno20:18
jaypipeswow, contentious.20:18
ttxnati_ueno: only PPB members vote, sorry :)20:18
* markmc moves to /Approved20:18
ttxmarkmc: anything more on that subject ?20:18
bcwaldonmarkmc: I would love to work with you on api goals when the time comes20:19
markmcttx, everyone help with the guidelines! :)20:19
markmcbcwaldon, cool20:19
ttx#topic Supporting projects20:19
*** openstack changes topic to "Supporting projects"20:19
ttx#link http://wiki.openstack.org/Governance/Proposed/SupportingProjectDefinition20:19
ttxSo this is a try to align our current structure with the proposed future TC structure20:20
ttxBasically we have a number of projects that are considered "OpenStack" with contributors that are relevant technical contributors that should be allowed to vote in TC elections20:20
ttxSo we need to assert that this category of project exist, and put a number of them in that category20:21
annegentle I'd like to voice a concern about leaving openstack-chef and the TryStack project off that list20:21
*** EmilienM has left #openstack-meeting20:21
ttxGives those project contributors the right to vote in directly-elected TC seats election20:21
annegentleThose two projects help increase adoption and support documentation efforts by providing real environments.20:21
annegentleThey're also great bridge projects to operators and cloud users.20:21
ttxOn the other hand, puts that project under the TC authority20:21
ttxso it's a bit of a two-edged sword20:22
ttxSo first, do we agree about the category ?20:22
ttxi.e. Proposal 1 in http://wiki.openstack.org/Governance/Proposed/SupportingProjectDefinition20:22
ttxQuestions on that part ?20:22
ttxannegentle: let's discuss which projects are and aren't considered in that category when we'll discuss Proposal 220:23
annegentlettx: got it20:23
anotherjessettx: can you give examples in part 1 (in the doc?)20:23
anotherjesseerr, nevermind20:23
*** devcamca- is now known as devcamcar20:24
ttxready to vote on the first part ?20:24
ttx#startvote Creating a "supporting" project official category? yes, abstain, no20:24
openstackBegin voting on: Creating a "supporting" project official category? Valid vote options are yes, abstain, no.20:24
openstackVote using '#vote OPTION'. Only your last vote counts.20:24
* ttx is getting better at this startvote thing20:25
bcwaldon#vote yes20:25
johnpur#vote yes20:25
ttx#vote yes20:25
danwent#vote yes20:25
*** blamar_ has joined #openstack-meeting20:25
devcamcar#vote abstain20:25
*** kindaopsdevy has quit IRC20:26
bcwaldonttx: you might want to expand on what the requirements are to be a supporting project20:26
vishy#vote yes20:26
bcwaldonttx: i.e. what you are expected to do20:26
ttxbcwaldon: You inherit allthe duties of other openstack official projects, but maybe I could expand on that20:27
*** blamar has quit IRC20:27
*** blamar_ is now known as blamar20:27
bcwaldonsure, or maybe I should just read more20:27
anotherjesse#vote yes20:27
*** dprince has quit IRC20:28
ttxbcwaldon: there are a few pieces out there that assume the supporting projects already exist ;)20:28
ttxvote closes in 30 sec20:28
heckj#vote abstain20:28
notmyname#vote no20:28
openstackVoted on "Creating a "supporting" project official category?" Results are20:29
openstackyes (6): anotherjesse, bcwaldon, ttx, vishy, johnpur, danwent20:29
openstackabstain (2): devcamcar, heckj20:29
openstackno (1): notmyname20:29
notmynamenot because it those projects aren't important. but because I don't think it makes them important enough20:29
ttxnotmyname: as in... less important than core projects because they don't get an aassigned seat on the TC ?20:29
johnpurnotmyname: what is your alternative?20:29
vishyI would be curious to know how many people contribute to these projects that don't also contribute to an official project20:30
vishymy thought is that it is close to 020:30
heckjvishy: docs might be an example of a difference, but that's the only one that comes to mind20:31
notmynamejohnpur: for example, gating + CI + docs together as "one" project with a lead that gets a seat on the PPB/TC20:31
ttxnotmyname: why not 3 seats then ?20:31
*** kindaopsdevy has joined #openstack-meeting20:32
notmynameI don't know. why not? :-)20:32
ttxyou know my position on this.. you can't weigh a project against another, the only way to do it fairly is to have all seats elected in the same way, with proportional rep20:32
ttxbut that ship has sailed20:32
ttxok, looking into proposal 220:32
*** mnewby has joined #openstack-meeting20:32
ttxwhich of those projects should actually be considered a supporting project20:33
ttxthe first on the list are no-brainers in my opinion20:33
ttxAnyone objects to the "Official documentation" list of projects ?20:33
bcwaldonttx: you've got my approval on the rest of the proposal20:33
annegentleto me, the official documentation list looks correct20:34
ttxThe only ones I had doubts with are pbr and git-review20:35
annegentlesorry, I have to catch a ride back to Austin, but basically I am advocating Supporting project definition that include deployers20:35
bcwaldonttx: both totally necessary20:35
ttxThe rest is pretty much openstack and openstack-centric20:35
ttxannegentle: we can discuss further additions another time anyway20:36
bcwaldonttx: I think putting something in openstack*/* should mean it is some sort of offical openstack project20:36
annegentlegreat, thanks all20:36
ttxannegentle: i'll discuss it with you20:36
ttxbcwaldon: indeed, the idea would be to remove the ones that are abusively under openstack*/* and should not be considered ours20:37
*** Ravikumar_hp has quit IRC20:37
ttxthen we can use review.openstack.org/openstack*/* as "the" list20:37
*** Ravikumar_hp has joined #openstack-meeting20:37
bcwaldonttx: ok, so I could see git-review moving under the stackforge banner20:37
ttxand generate active contributors directly from gerrit20:37
bcwaldonttx: and pbr could really exist outside of openstack20:37
ttxmtaylor: wanna step up and defend those ?20:37
bcwaldonttx: we should let mtaylor/jeblair argue those points20:37
*** jk0 has joined #openstack-meeting20:37
ttxeveryone agrees on the rest of the list ?20:38
ttx(from openstack/compute-api to openstack-dev/openstack-nose)20:38
bcwaldonseems so20:39
ttxwanna make an argument about wht pbr and git-review should be IN ?20:39
mtaylorsame reason as openstack-nose, honestly20:40
mtaylorthey were written for openstack and are kinda central to what we do20:40
ttxmtaylor: openstack-nose has a smarter name :P20:40
mtaylorthe fact that they were written to be friendly and non-openstack _specific_ is beside the point20:40
bcwaldonmtaylor: so I made the opposite decision for warlock20:40
mtaylorhowever, if people want them to move, I don't think it will hurt anything20:40
bcwaldonmtaylor: which I wrote for openstack, but it has nothing to do with the domain20:40
*** dwcramer has quit IRC20:41
mtaylorI could see git-review moving to openstack-dev rather than openstack-ci - or honestly just somewhere else20:41
mtaylorI'm not wedded to it being in openstack-ci20:42
bcwaldonmtaylor: is git-review specific to openstack? Isn't it more of a way to interact with a stackforge cite?20:42
mtaylorwith a gerrit20:42
ttxSo... no objection to doc and core infra categories, still a bit of discussion around openstack-nose, pbr and git-review20:42
bcwaldonsure, even just a gerrit20:42
mtaylorit was originally written as a re-write of a shell script we had in our repos20:42
mtaylorwhich is why it's in our system20:42
mtaylorsame with pbr - which is actually mostly just code from openstack-common20:42
*** gabrielhurley has joined #openstack-meeting20:42
mtaylorpackaged up to be easier to work with20:42
mtaylorboth have some openstack assumptions in them (pbr more-so than git-review)20:43
bcwaldonmtaylor: right, one thing I don't want to do is to prevent other open source projects from consuming our stuff20:43
mtaylorpbr could just as easily be called openstack-setup or something :)20:43
bcwaldonmtaylor: and not have to care about openstack20:43
ttxI propose we vote to add the first two categories and let the discussion continue some other day about the others.20:43
bcwaldonttx: sure20:43
mtayloryeah - we can offline pbr and git-review discussion just fine20:43
*** kindaopsdevy_ has joined #openstack-meeting20:43
* mtaylor does noth ave the passionate feelings on this topic - it's a grey area honestly20:43
johnpurttx: +120:44
ttx#startvote Add Official doc and Core Infrastructure projects lists to the "supporting" category? yes, abstain, no20:44
openstackBegin voting on: Add Official doc and Core Infrastructure projects lists to the "supporting" category? Valid vote options are yes, abstain, no.20:44
openstackVote using '#vote OPTION'. Only your last vote counts.20:44
ttxI think that roughly covers 100% of contributors anyway20:44
bcwaldon#vote yes20:44
johnpur#vote yes20:44
ttx#vote yes20:44
ttxso we can use them to get the right list of people voting20:44
vishy#vote yes20:44
ttxin the elections next month20:44
anotherjesse#vote yes20:44
heckj#vote yes20:44
devcamcar#vote yes20:44
danwent#vote yes20:45
*** johnpostlethwait has quit IRC20:45
ttx30 seconds more20:45
notmyname#vote abstain20:45
*** johnpostlethwait has joined #openstack-meeting20:45
openstackVoted on "Add Official doc and Core Infrastructure projects lists to the "supporting" category?" Results are20:46
openstackyes (8): anotherjesse, bcwaldon, ttx, vishy, heckj, johnpur, danwent, devcamcar20:46
openstackabstain (1): notmyname20:46
*** kindaopsdevy has quit IRC20:46
*** kindaopsdevy_ is now known as kindaopsdevy20:46
ttxok, I think we are done... 14 minute recess before next meeting ?20:46
bcwaldonthanks, ttx20:46
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"20:47
openstackMeeting ended Tue Jul 31 20:47:09 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:47
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-20.06.html20:47
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-20.06.txt20:47
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-20.06.log.html20:47
*** kindaopsdevy has quit IRC20:48
*** ewanmellor has quit IRC20:48
*** kindaopsdevy has joined #openstack-meeting20:49
*** jk0 has left #openstack-meeting20:50
*** dolphm has joined #openstack-meeting20:51
*** johnpostlethwait has quit IRC20:54
*** johnpostlethwait has joined #openstack-meeting20:54
*** markmcclain1 has quit IRC20:58
ttxback on stage21:01
ttxmarkmc, heckj, notmyname, bcwaldon, jgriffith, vishy, devcamcar, danwent: [still] around ?21:01
gabrielhurleyttx: I'll be your devcamcar for today.21:01
ttxgabrielhurley: awesome21:02
ttxlet's start and bcwaldon/vishy/jgriffith will catch up21:02
openstackMeeting started Tue Jul 31 21:02:53 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:03
*** jerdfelt has joined #openstack-meeting21:03
ttx#info Two weeks left for Folsom features! Propose code now or it will wait for Grizzly.21:03
ttx#topic Actions from previous meeting21:03
*** openstack changes topic to "Actions from previous meeting"21:03
ttx* notmyname to retroactively create some blueprints to cover 1.6.0 main features: DONE21:03
ttx* vishy to defer trusted messaging and user configurable rbac to Grizzly: DONE21:03
ttx* gabrielhurley/devcamcar to clarify droppage of ext-roles due to lack of RBAC support21:04
ttxgabrielhurley: Now marked "Slow progress", so it's still relevant ?21:04
gabrielhurleyttx: it is still relevant, yes21:04
ttxbut unlikely.21:04
gabrielhurleyttx: it's a stretch goal, but we're working on it21:04
ttxgabrielhurley: ok, thx21:04
gabrielhurleyttx: it's actually not hard for horizon, it's just dependent on keystone21:04
ttx* ttx to confirm green light to nova and keystone 2012.1.221:04
ttx...let's discuss that in the next topic.21:04
bcwaldonttx: here21:05
ttxgabrielhurley: anything specific you are waiting on in Keystone ?21:05
gabrielhurleyttx: like you said, we can discuss that during the keystone topic ;-)21:05
ttxWell, I was actually speaking of 2012.1.2, but let's do that yes21:06
*** anotherjesse is now known as anotherjesse_zz21:06
ttx#topic 2012.1.2 stable release21:06
*** openstack changes topic to "2012.1.2 stable release"21:06
ttxmarkmc: So we are now aiming for August 9 for 2012.1.2 ?21:06
markmcttx, yes, pushing out by a week because of a fix in the pipeline21:07
ttxDoes that mean there is still room for more last-minute fix backports in Keystone/Nova ?21:07
markmcttx, still looking good, had a nice bunch of nova fixes21:07
ttxor you'd rather not ?21:07
markmchappy to take some more, looks like there's some in the queue for keystone21:07
heckjmarkmc: yeah, apevec has been busy there21:07
markmchaven't re-checked horizon and glance since last week21:07
ttxsounds good. Anything more on that topic ?21:08
markmcnot from me21:08
*** mnewby has quit IRC21:08
ttx#topic Keystone status21:09
*** openstack changes topic to "Keystone status"21:09
ttxheckj: o/21:09
ttx#link https://launchpad.net/keystone/+milestone/folsom-321:09
heckj(refresh if you haven't recently)21:09
ttxheckj: Not much visible progress since last week ?21:09
* ttx refreshes21:09
heckjPKI getting landed and bugs on it21:09
heckjSome no-progress elements removed from F3 milestone goals21:09
ttxVERY recently :)21:10
heckjthat's why I suggested you refresh. Wanted to be more like bcwaldon21:10
ttxHe's alreday tainting you, I see21:10
ttxLooks good now21:11
ttxheckj: Quick priority sanity-check: Can you confirm you're fine with deferring to Grizzly all those features if they are not merged in by August 14 ?21:11
heckjttx: I really wanted to get more done, but yeah - I'd prefer stability and consistency over last-minute change to just shove something in the door21:11
ttxright, obviously all the "High" are very much wanted21:12
heckjstill hoping to have parts of the V3 API stubbed out and "draft" or "beta" available for F321:12
ttxheckj: anything else ?21:12
heckjnot from me - question time21:13
ttxgabrielhurley: what is it you're depending on in Keystone ?21:13
gabrielhurleyttx: perhaps heckj can comment on his thinking about the policy consolidation and CRUD in keystone (which is the main dependency for horizon's RBAC blueprint)21:13
ttxgabrielhurley: perhaps he can.21:13
gabrielhurley(he and I have spoken about it, but probably best to share...)21:13
heckjThere's a slow-progress blueprint about consolidating all the various policy.json files and suggesting a best-practice/small-deployment setup for those and assocaited roles.21:13
heckjThat's really the key piece there - just getting some intended consistency to deployments21:14
heckjthere's also some V3 API around letting keystone host those policy files,21:14
gabrielhurleyif there's consistency and we an API to query the policy, then horizon has trivial work to do to support it in the UI21:14
*** markmc is now known as mcaway21:14
heckjbut that's after we get a basic around the roles across projects, etc.21:14
ttxgabrielhurley: you'd need document-deployment-suggestions-policy complete ASAP to be unblocked ?21:15
heckjthat's the gist of it all - horizon's UI would require the V3 Policy crud API and conventions around how to read those files21:15
uvirtbotgabrielhurley: Error: "^^that" is not a valid command.21:16
* heckj loves the uvirtbot21:16
gabrielhurleyif it all falls through we haven't lost much... we're just still stuck with the two roles (admin and member)21:16
ttxheckj: do you think it would be reasonable for Horizon to use a part of the V3 API ?21:16
*** markvoelker has quit IRC21:17
heckjthat portion, yes - it's totally new and independent of the other API elements21:17
ttxOK. Other questions about Keystone ?21:17
gabrielhurleyttx heckj: since I thoroughly vetted the v3 API I'm pretty comfortable with using it, particularly that bit. we can adjust over time if necessary.21:17
ttx#topic Swift status21:18
*** openstack changes topic to "Swift status"21:18
ttx#link https://launchpad.net/swift/+milestone/1.6.021:18
ttxnotmyname: hey21:18
ttx1.6.0 still being QA'ed ?21:18
ttxnotmyname: more fixes coming up, or just more time to complete the QA round ?21:19
notmynamethere was a slow start to getting them tested, and a couple of issues came up. so both :-)21:20
ttxnotmyname: OK. just push the Final=True thing onto milestone-proposed when you're fine with it21:20
notmynameI will21:20
ttxIt will be our secret signal21:20
notmynamedon't tell21:20
*** maoy has quit IRC21:20
ttxnotmyname: ideally the bugs we are waiting on should be visible on the milestone page (targeted to 1.6.0)21:21
ttxso that everyone knows what we are blocking on21:21
ttxnotmyname: anything else ?21:21
notmynamethe page is up to date. the most recent was actually a regression. it broke old functionality (the bug would be "everything is the same as it was")21:21
ttxAck. Questions on Swift ?21:22
notmynamethere are no known blockers right now. simply waiting for QA to be done21:22
ttx#topic Glance status21:23
*** openstack changes topic to "Glance status"21:23
ttxbcwaldon: o/21:23
ttx#link https://launchpad.net/glance/+milestone/folsom-321:23
* ttx refreshes21:23
ttxGood progress overall, still a bit worried about essential stuff...21:24
bcwaldonyou don't trust me!?21:24
ttxbcwaldon: When worried I go from being a weekly PITA to being a daily PITA :P21:24
ttxLet's see where we stand...21:24
ttx* https://blueprints.launchpad.net/glance/+spec/api-v2-store-access21:24
*** s0mik has quit IRC21:24
ttxStill not started ? But short enough ?21:24
bcwaldonI have someone who will do it over the next week21:25
bcwaldonif its not done, I'm gonna do it21:25
bcwaldonthats how a lot of things get done21:25
bcwaldonmarkwash has been super helpful in the v2 implementation21:26
ttxif not done next week, that will just leave you with the weekend to do it :)21:26
bcwaldonand he's wrapping up his remaining blueprints as we speak21:26
*** ohnoimdead has joined #openstack-meeting21:26
bcwaldonttx: thats enough time, I just have other things to do right now21:26
ttxSo api-v2-links is close to completion once part 1 is merged ?21:26
bcwaldonttx: I think the review up now is all that needs to be done21:27
ttxOK, so that leaves us with https://blueprints.launchpad.net/glance/+spec/separate-client21:27
ttxBlocked on https://blueprints.launchpad.net/nova/+spec/integrate-python-glanceclient and https://blueprints.launchpad.net/python-glanceclient/+spec/glance-client-parity21:27
bcwaldonyep, I have code for integrate-python-glanceclient21:27
bcwaldongot that working last night21:27
ttxvishy: OK to raise priority of integrate-python-glanceclient to "Essential" to match ?21:27
bcwaldonand glance-client parity has one thing left - porting ssl code from legacy client21:28
bcwaldonwhich someone else could do!21:28
*** heckj has quit IRC21:29
ttx#help Volunteer needed to port ssl code from legacy client in glance-client-parity21:29
ttxNeeded for some Folsom-essential stuff ^21:30
ttxbcwaldon: About https://blueprints.launchpad.net/glance/+spec/api-v2-property-protection -- is that part of the API v2 stuff ? Should that be Essential ?21:30
bcwaldonsounds like someone who cares about using glanceclient over ssl could step up21:30
bcwaldonttx: we might get a really dumb version of that implemented, but it might get bumped to grizzly21:31
ttx(it's also a good occasion to focus on something that is important for the release success, rather than some pet itch)21:31
ttxbcwaldon: so it's not an integral part of API v2 ?21:31
bcwaldonttx: no, its a nice-to-have21:31
bcwaldonttx: its something that will make the v2 api more powerful, but its a behind-the-scenes feature21:32
bcwaldonits not built into the spec21:32
ttxbcwaldon: last question, apart from the already-marked-Essential stuff, you're fine with deferring to Grizzly anything not merged by Aug 14 ?21:32
bcwaldonttx: I want to make sure dprince's tenant-specific storage stuff gets in21:32
ttxjust checking we are not forgetting some essential stuff.21:32
bcwaldonttx: he has code in review already21:33
bcwaldonttx: I hope to get those in shortly21:33
ttxbcwaldon: should we set that to Essential to reflect that you'd not release folsom without it ?21:33
*** s0mik has joined #openstack-meeting21:33
bcwaldonttx: yes21:34
ttxbcwaldon: will do. Anything else ?21:34
*** ryanpetrello has quit IRC21:34
bcwaldonttx: I'll go over it again but nothing to bring up now21:34
ttxQuestions on Glance ?21:34
ttx#topic Quantum status21:35
*** openstack changes topic to "Quantum status"21:35
ttxdanwent: yo21:35
ttx#link https://launchpad.net/quantum/+milestone/folsom-321:35
ttxGood progress on High/Essential stuff... let's see the Essential ones in more detail21:35
ttx* https://blueprints.launchpad.net/quantum/+spec/provider-networks21:35
ttxOne more small part still needed, right ?21:35
danwentbeen promised a review by monday21:35
danwentyes, patch 3 of 421:36
danwentor rather, 4 of 421:36
danwent3 of 4 are in21:36
ttx* https://blueprints.launchpad.net/quantum/+spec/quantum-v2-public-networks21:36
ttxCode proposed at https://review.openstack.org/#/c/9845/, could benefit from some reviewing activity ?21:36
*** s0mik has quit IRC21:36
danwentits actually been through a decent amount of review, given that salvatore puts together good code to start with21:37
danwentbut one of the two core devs reviewing the patch is now on vacation, so we need to find another one21:37
ttx* https://blueprints.launchpad.net/quantum/+spec/quantum-l3-fwd-nat21:37
ttxStatus on that ?21:37
danwentfinally making good progress on that.21:37
*** s0mik has joined #openstack-meeting21:37
danwenthave committed to a review by monday21:37
ttxYou mentioned splitting that one in two, did you abandon the idea ?21:37
danwentam hoping to have a WIP done sooner than that.21:37
danwentI'm actually going to do the bulk of it myself, but slice a few pieces off.21:38
danwentnati_ueno also will be helping21:38
ttxok, looks like we should be mostly set in a week21:38
ttx(for the essential stuff)21:38
*** s0mik has quit IRC21:38
ttxDo you agree to un-folsom3-target the (unassigned) expose-dhcp-server-ip and api-rate-limiting ?21:39
danwentyeah, essential and high should all be in for review by tuesday21:39
ttxWill still be in folsom map but out of F3 since nobody is signed up yet for them21:39
danwentexpose-dhcp-server-ip is trivial, and i'm going to try and hand it to someone21:39
danwentvery small patch21:39
danwentrate-limiting will be bumped21:39
danwenti'm also planning on moving anything in slow progress out as well21:39
*** heckj has joined #openstack-meeting21:39
ttxSame priority-sanity-check, apart from the stuff marked Essential, you're fine with deferring to Grizzly anything that doesn't make it to master by Aug 14 ?21:39
danwentfeature-wise, yes21:40
ttxdanwent: Anything else ?21:40
ttxQuestions on Quantum ?21:40
danwenti'm a bit worried we may have an 'oh crap' of something possible in nova network that we didn't handle in quantum, but i've done my best to cover the core use cases.21:40
danwentbtw, multi-host stuff probably won't make it unless someone steps up.21:41
ttxdanwent: we could cover them as bugs/exceptions if they are not too intrusive21:41
danwentttx: ok.21:41
ttx#topic Cinder status21:41
*** openstack changes topic to "Cinder status"21:42
ttxjgriffith: around ?21:42
ttxHmm, let's do Nova first21:42
ttx#topic Nova status21:42
*** openstack changes topic to "Nova status"21:42
*** hggdh has quit IRC21:42
ttxvishy: hey21:42
ttx#link https://launchpad.net/nova/+milestone/folsom-321:42
ttxLet's see progress on essential stuff:21:43
ttx* https://blueprints.launchpad.net/nova/+spec/general-host-aggregates (jog0)21:43
ttxStill waiting to get step 2/5 merged ?21:43
jog0ttx: needs code review21:43
ttx#help Review needed on https://review.openstack.org/#/c/10256/21:44
ttxjog0: How complex are the remaining steps ?21:44
*** patelna has quit IRC21:45
ttxvishy: please mention that review during your meeting if it's not covered by then, looks like the one most likely to spillover21:45
jog0ttx: fairly easy, besides moving AZs to aggregates internally21:46
ttx* https://blueprints.launchpad.net/nova/+spec/integrate-python-glanceclient21:46
ttxWe mentioned this earlier when we discussed Glance...21:46
ttxbcwaldon has working code, should be proposed soon21:47
bcwaldonttx: code is up, just getting testing to work21:47
*** patelna has joined #openstack-meeting21:47
vishyi will21:48
ttxAlso wanted to look into a few "High" ones:21:48
ttx* https://blueprints.launchpad.net/nova/+spec/extract-nova-volumes21:48
ttxvishy: how is this one looking ?21:48
vishyttx: the nova side is done barring potential export code in nova-manage21:48
vishyjgriffith is looking at that now21:48
ttx* https://blueprints.launchpad.net/nova/+spec/no-db-messaging21:48
ttxLots of changes were merged for this... any indication of how much more there will be ?21:49
ttx(are the last 4 proposed the last ones ?)21:49
vishyttx: down to a few21:50
ttxMinor cleanups now, those two blueprints look completed to me, please confirm:21:50
ttx* https://blueprints.launchpad.net/nova/+spec/update-flavor-key-value21:50
ttx* https://blueprints.launchpad.net/nova/+spec/xenstore-metadata21:50
vishyttx: russelb just found a couple more spots in the scheduler he needs to fix21:50
ttx(no need to look at them now, just set to Implemented after meeting if appropriate)21:51
ttxAnd this one looks like it could be targeted to F3:21:51
ttx* https://blueprints.launchpad.net/nova/+spec/xenapi-live-block-migration21:51
vishyyes should be targeted21:51
ttxvishy: Same question as the other projects, apart from Essential stuff, you're fine with deferring to Grizzly anything that doesn't make it by Aug 14 ?21:51
ttxvishy: Anything else ?21:51
vishywe are going to check those key blueprints in the thursday meeting21:51
*** arosen has quit IRC21:51
vishyI will let you know next week if there is anything that comes up there as a blocker21:52
ttxsounds good21:52
ttxQuestions on Nova ?21:52
ttx#topic Horizon status21:53
*** openstack changes topic to "Horizon status"21:53
ttxgabrielhurley: hey21:53
gabrielhurleyttx: hi21:53
ttx#link https://launchpad.net/horizon/+milestone/folsom-321:53
gabrielhurleynot as much progress since last week as I'd have liked, but not time to cut things quite yet21:53
ttxWe clarified ext-roles earlier...21:53
ttxhad a question for https://blueprints.launchpad.net/horizon/+spec/swiftclient -- is that blocked on Swift 1.6.0 release ? Or just work in the pipe ?21:53
gabrielhurleyjust work in the pipe21:54
ttxFinally about https://blueprints.launchpad.net/horizon/+spec/readd-quantum-support21:54
ttxThis looks pretty high-prio... how is that going ?21:54
gabrielhurleygoing well. Akihiro and company have been pushing new revisions of the code regularly and it's definitely gonna land.21:54
ttxFinally same question than for the others... you're fine with deferring all those features if they are not merged in by August 14 ?21:55
*** EdB has joined #openstack-meeting21:55
gabrielhurleyall the ones that aren't started yet are fine to defer if they don't land21:55
gabrielhurleythe ones that are started I'd be sad about21:55
gabrielhurleybut still not blockers21:55
ttxgabrielhurley: anything else you wanted to mention ?21:55
*** EdB has quit IRC21:56
*** rnirmal has quit IRC21:56
gabrielhurleyI think I got my mentioning done earlier. ;-)21:56
*** patelna has quit IRC21:56
ttxQuestions for Horizon ?21:56
ttx#topic Cinder status try 221:56
*** openstack changes topic to "Cinder status try 2"21:56
ttxjgriffith: howdy!21:56
jgriffithhowdy :)21:56
ttx#link https://launchpad.net/cinder/+milestone/folsom-321:56
ttx* https://blueprints.launchpad.net/cinder/+spec/migrate-nova-volumes-to-cinder21:57
ttxAny progress on that ?21:57
jgriffithlittle, as Vishy mentioned that's my next list item21:57
*** dolphm has quit IRC21:57
jgriffithI plan to have a first pass thrown out tomorrow afternoon hopefully21:57
ttxWas wondering if you'd consider it's OK to release Cinder/Folsom if this is not completed.21:57
jgriffithI don't think it will come to that21:57
ttxi.e. shouldn't it be "essential" rather than "high"21:57
jgriffithgiven the tone of the ML responses I think it's essential21:58
jgriffithJust my opinoin21:58
jgriffithI'm happy to change it, but I'll have it for F321:58
ttxjgriffith: that's the spirit :)21:58
ttxWill mark it essential21:58
*** patelna has joined #openstack-meeting21:58
ttx* https://blueprints.launchpad.net/cinder/+spec/cinder-notifications21:58
* jgriffith has sucker on his forehead21:58
ttxAny news from cp16net ?21:59
jgriffithttx: Yea, he said he's going to finish it21:59
jgriffithttx: The only question is when21:59
ttxSo it's started, low priority ?21:59
jgriffithttx: He did say in the next week or so (that was last week)21:59
jgriffithttx: yes, started low pri21:59
ttxjgriffith: Anything else ?21:59
jgriffithttx: The only thing that keeps me hanging on to it is that it's in nova now22:00
ttxQuestions on Cinder ?22:00
jgriffithUmmm.... lots but nothing anybody cares about likely22:00
ttx#topic Other Team reports22:00
*** openstack changes topic to "Other Team reports"22:00
ttxAny other team lead with a status report ?22:00
ttx#topic Open discussion22:01
*** openstack changes topic to "Open discussion"22:01
ttxAnything else, anyone ?22:01
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"22:02
openstackMeeting ended Tue Jul 31 22:02:17 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-21.02.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-21.02.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-07-31-21.02.log.html22:02
ttxJust below the one hour mark22:03
ttxStarted 21:02:53, Ended 22:02:1722:03
*** thingee has left #openstack-meeting22:03
*** kindaopsdevy has left #openstack-meeting22:03
*** patelna has quit IRC22:05
*** littleidea has quit IRC22:07
*** littleidea has joined #openstack-meeting22:07
*** arosen has joined #openstack-meeting22:10
*** EdB has joined #openstack-meeting22:12
*** EdB has left #openstack-meeting22:13
*** gabrielhurley has quit IRC22:14
*** jerdfelt has left #openstack-meeting22:14
*** heckj has quit IRC22:24
*** Gordonz has quit IRC22:25
*** littleidea_ has joined #openstack-meeting22:25
*** lcheng has quit IRC22:25
*** littleidea has quit IRC22:25
*** littleidea_ is now known as littleidea22:25
*** lloydde has quit IRC22:28
*** lloydde has joined #openstack-meeting22:28
*** mnewby has joined #openstack-meeting22:40
*** ttrifonov is now known as ttrifonov_zZzz22:43
*** mattray has quit IRC22:46
*** mnewby has quit IRC22:47
*** ecarlin has joined #openstack-meeting22:50
*** danwent has quit IRC22:52
*** alexpilotti has quit IRC22:53
*** blamar_ has joined #openstack-meeting22:53
*** rafaduran has quit IRC22:57
*** blamar has quit IRC22:57
*** blamar_ is now known as blamar22:57
*** dendrobates is now known as dendro-afk22:59
*** blamar has quit IRC23:01
*** matiu has quit IRC23:03
*** dwcramer has joined #openstack-meeting23:04
*** kindaopsdevy has joined #openstack-meeting23:06
*** dolphm has joined #openstack-meeting23:08
*** mnewby has joined #openstack-meeting23:10
*** kindaopsdevy has quit IRC23:10
*** kindaops_ has joined #openstack-meeting23:10
*** kindaops_ has quit IRC23:11
*** kindaopsdevy has joined #openstack-meeting23:11
*** dolphm has quit IRC23:12
*** lloydde has quit IRC23:14
*** ohnoimdead has quit IRC23:15
*** dwcramer has quit IRC23:16
*** Ravikumar_hp has quit IRC23:20
*** dwcramer has joined #openstack-meeting23:30
*** gyee has quit IRC23:41
*** mnewby has quit IRC23:42
*** mnewby has joined #openstack-meeting23:47
*** jakedahn is now known as jakedahn_zz23:47
*** lzyeval has joined #openstack-meeting23:49
*** dmd17 has joined #openstack-meeting23:54
*** johnpur has quit IRC23:54
*** johnpur has joined #openstack-meeting23:54
*** mikal has quit IRC23:56
*** mikal has joined #openstack-meeting23:58
*** johnpur has quit IRC23:58
*** johnpur has joined #openstack-meeting23:59

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