Friday, 2011-10-14

*** anotherjesse has quit IRC00:02
*** vladimir3p_ has quit IRC00:05
*** patelna has quit IRC00:12
*** fyang has joined #openstack-dev00:27
*** rkukura has joined #openstack-dev00:42
*** dtroyer has quit IRC00:55
*** fyang has quit IRC01:34
*** adjohn has quit IRC01:39
*** zykes- has joined #openstack-dev01:39
*** jdurgin has quit IRC01:50
openstackgerritYogeshwar Srikrishnan proposed a change to openstack/keystone: Fixing issue 854425.ie chaning token table name to tokens. Fixing issue 863667.Changes to support updation of user/tenant name as well using api calls. Fixing LDAP backend to have id independent of name.Fixing getuser call to also return name.  https://review.openstack.org/88402:03
KiallSomeone doesnt get the whole 1 review = 1 change idea :)02:08
*** rkukura has left #openstack-dev02:18
*** neogenix has joined #openstack-dev02:29
*** neogenix has left #openstack-dev02:31
openstackgerritJohn Tran proposed a change to openstack/nova: bug 817872  https://review.openstack.org/86202:35
uvirtbotLaunchpad bug 817872 in nova "Delete security group that contains instances should not be allowed" [Medium,Confirmed] https://launchpad.net/bugs/81787202:35
*** rkukura has joined #openstack-dev02:42
*** nati2 has joined #openstack-dev02:56
*** KiwiMartin has joined #openstack-dev02:56
*** KiwiMartin has quit IRC03:01
*** rkukura has quit IRC03:01
*** anotherjesse has joined #openstack-dev03:06
*** anotherjesse has quit IRC03:07
*** martine has joined #openstack-dev03:10
openstackgerritBrian Waldon proposed a change to openstack/nova: Convert instancetype.flavorid to string  https://review.openstack.org/85903:39
*** novas0x2a|laptop has quit IRC03:46
*** zul has quit IRC03:58
*** zul has joined #openstack-dev03:59
*** zul has quit IRC04:04
*** nati2 has quit IRC04:04
*** zul has joined #openstack-dev04:05
*** zedas has quit IRC04:05
*** blakeyeager has quit IRC04:08
*** jakedahn has joined #openstack-dev04:15
*** misheska has joined #openstack-dev04:21
*** blakeyeager has joined #openstack-dev04:21
*** blakeyeager has quit IRC04:28
*** novas0x2a|laptop has joined #openstack-dev04:28
*** tsuzuki_ has joined #openstack-dev04:44
*** jakedahn has quit IRC04:53
*** Vek has quit IRC05:00
*** martine has quit IRC05:09
*** nati2 has joined #openstack-dev05:10
*** zul has quit IRC05:13
*** martine has joined #openstack-dev05:13
*** zul has joined #openstack-dev05:13
*** nati2 has quit IRC05:16
*** novas0x2a|laptop has quit IRC05:24
*** jakedahn has joined #openstack-dev05:28
*** reed has quit IRC05:36
*** zul has quit IRC05:43
*** zul has joined #openstack-dev05:44
*** unabonger has joined #openstack-dev05:51
*** nati2 has joined #openstack-dev05:56
*** zaitcev has quit IRC06:09
*** martine has quit IRC06:09
*** unabonger is now known as backburner06:13
*** Vek has joined #openstack-dev06:55
*** nati2 has quit IRC07:29
*** reidrac has joined #openstack-dev08:15
*** pyhole has quit IRC08:55
*** darraghb has joined #openstack-dev09:07
*** rbasak has joined #openstack-dev09:29
*** tryggvil_ has joined #openstack-dev10:14
*** tsuzuki_ has quit IRC10:33
*** hugokuo has quit IRC10:41
*** rods has joined #openstack-dev10:46
*** mancdaz has quit IRC10:59
*** mancdaz has joined #openstack-dev11:00
*** lorin1 has joined #openstack-dev11:37
*** markmc has quit IRC11:52
*** rkukura has joined #openstack-dev12:04
*** Oneiroi has joined #openstack-dev12:23
*** Oneiroi has joined #openstack-dev12:25
*** med_out is now known as medberry12:51
*** dtroyer has joined #openstack-dev12:58
*** dtroyer has quit IRC13:02
*** xtor_ has joined #openstack-dev13:14
*** extor has quit IRC13:14
*** xtor_ has quit IRC13:16
*** extor has joined #openstack-dev13:16
*** misheska has joined #openstack-dev13:19
*** misheska has quit IRC13:19
*** markmc has joined #openstack-dev13:28
*** Oneiroi has quit IRC13:30
*** misheska has joined #openstack-dev13:36
*** kbringard has joined #openstack-dev13:57
*** martine has joined #openstack-dev13:58
openstackgerritChuck Short proposed a change to openstack/nova: Fix pep8 errors  https://review.openstack.org/88514:00
openstackgerritChuck Short proposed a change to openstack/nova: Display LXC container console when using euca-get-console.  https://review.openstack.org/72814:00
*** fyang has joined #openstack-dev14:01
*** wwkeyboard has joined #openstack-dev14:08
*** rnorwood has joined #openstack-dev14:09
*** dubsquared has joined #openstack-dev14:14
openstackgerritJames E. Blair proposed a change to openstack-ci/git-review: Add --setup command for a pro-active repo setup.  https://review.openstack.org/87114:20
openstackgerritA change was merged to openstack-ci/git-review: Add --setup command for a pro-active repo setup.  https://review.openstack.org/87114:21
openstackgerritVerification of a change to openstack-ci/git-review failed: Replace git fetch with git remote update.  https://review.openstack.org/87514:21
openstackgerritAlex Meade proposed a change to openstack/nova: Redirects requests to /v#.# to /v#.#/ Added an APIMapper to catch routemaps when the url is '' because routes.Mapper returns an error if this is the case but we want a redirect Fixes bug 865585 Related to Routes issue: https://bitbucket.org/bbangert/route  https://review.openstack.org/88614:22
uvirtbotLaunchpad bug 865585 in nova "/v1.1 returns a 500, /v1.1/ gives desired respons" [Undecided,In progress] https://launchpad.net/bugs/86558514:22
openstackgerritAlex Meade proposed a change to openstack/nova: Redirects requests to /v#.# to /v#.#/ Added an APIMapper to catch routemaps when the url is '' because routes.Mapper returns an error if this is the case but we want a redirect Fixes bug 865585 Related to Routes issue: https://bitbucket.org/bbangert/route  https://review.openstack.org/88614:23
openstackgerritAlex Meade proposed a change to openstack/nova: Redirects requests to /v#.# to /v#.#/  https://review.openstack.org/88614:24
openstackgerritJames E. Blair proposed a change to openstack-ci/git-review: Replace git fetch with git remote update.  https://review.openstack.org/87514:25
openstackgerritA change was merged to openstack-ci/git-review: Replace git fetch with git remote update.  https://review.openstack.org/87514:25
openstackgerritJames E. Blair proposed a change to openstack-ci/git-review: fixed problem downloading changes  https://review.openstack.org/88714:25
openstackgerritChuck Short proposed a change to openstack/nova: Allow user to decide whether or not to inject ssh keys into the image. Fixes LP: 833499  https://review.openstack.org/88814:39
openstackgerritA change was merged to openstack/keystone: Fixing issue 854425.ie chaning token table name to tokens. Fixing issue 863667.Changes to support updation of user/tenant name as well using api calls. Fixing LDAP backend to have id independent of name.Fixing getuser call to also return name.  https://review.openstack.org/88414:46
*** reed has joined #openstack-dev14:47
*** rnorwood has quit IRC14:48
*** dragondm has joined #openstack-dev14:50
lorin1Does Gerrit let you view an entire file in the web interface, or can you only see the parts that have changed?14:50
*** code_franco has joined #openstack-dev14:51
*** adjohn has joined #openstack-dev14:51
wwkeyboardlorin1: In the side-by-side view you can change the context to "whole file"14:55
*** pyhole has joined #openstack-dev14:55
*** martine has quit IRC14:56
wwkeyboardDoes anyone with core access to openstack-integration-tests have time to do some reviewing this morning? https://review.openstack.org/#q,status:open+project:openstack/openstack-integration-tests,n,z14:56
lorin1wwkeyboard: thanks, I hadn't notice that drop-down before.14:57
westmaasjeblair: howdy sir, you mentioned you were going to make a new core group for openstack-integration-tests, did that happen?  And who is in the group?  thanks!14:59
openstackgerritCarlos Marin proposed a change to openstack/keystone: First commit for Secret Question and Answer Extension: RAX-KSQA  https://review.openstack.org/86115:00
jeblairwestmass: hi!  that's in progress now actually.  I created the group a while ago, it's synced to gerrit, and i'm currently updating gerrit to give that group +2 access.15:00
westmaasjeblair: cool.  just the same group as nova core?15:00
jeblairwestmaas: i only added jaypipes so far.  is there a consensus on who sholud be in it?15:01
westmaasnope :)15:01
*** markmc has quit IRC15:02
jeblairokay, i'll nudge him to add some folks next time i see him online, or send email.15:02
*** rnorwood has joined #openstack-dev15:05
*** xtoddx has left #openstack-dev15:06
*** reidrac has quit IRC15:12
*** cp16net has joined #openstack-dev15:14
openstackgerritA change was merged to openstack-ci/git-review: fixed problem downloading changes  https://review.openstack.org/88715:16
kbringardhey guys, a couple quick ?'s (sorry, I couldn't find it elsewhere)15:17
kbringardwhen is the maintenance release of diablo being targeted?15:17
kbringardand do we know if https://bugs.launchpad.net/nova/+bug/855660 is in it?15:17
uvirtbotLaunchpad bug 855660 in nova "DescribeInstances fails sporadically" [Undecided,Fix committed]15:17
wwkeyboardjeblair: In the meantime how do we go about getting branches merged into the openstack-integration-tests?15:18
kbringardit doesn't look like it's in diablo-backport :-/15:23
*** throughnothing has left #openstack-dev15:25
jeblairwwkeyboard: i'd prefer to wait for jay to approve or nominate others15:26
jeblairkbringard: does this thread help? https://lists.launchpad.net/openstack/msg04748.html15:27
kbringardjeblair: probably, let me read it :-)15:27
kbringardthanks15:27
*** xtoddx has joined #openstack-dev15:27
*** martine has joined #openstack-dev15:29
*** misheska has quit IRC15:34
*** misheska has joined #openstack-dev15:35
*** vladimir3p has joined #openstack-dev15:35
kbringardone last question, I don't see anything in here about packages being built… are there plans for that or will I need to apply patches manually?15:36
*** misheska has quit IRC15:36
jeblairkbringard: openstack may not15:37
jeblairack15:37
kbringardbleh, stuff like, euca-describe-instances failing 50% of the time in a "released" version doesn't seem like a good thing15:38
jeblairkbringard: openstack may not produce a release based on the backported fixes, and separately, we're going to stop producing packages as a product.  instead the proposals are for the distros to handle packaging, and the maintenance branches are to facilitate distros patching their released versions to provide stable release updates15:38
kbringardah, makes sense15:39
jeblairkbringard: https://lists.launchpad.net/openstack/msg04789.html15:39
jeblairmore info about packaging ^15:39
kbringardman, I need to be better about reading the mailing list mail, heh15:39
kbringardsorry I suck15:39
jeblairwwkeyboard: based on the wed meeting, it looks like westmaas and dwalleck should be in qa-core15:42
jeblairwestmaas: ping15:42
*** Oneiroi has joined #openstack-dev15:43
*** Oneiroi has joined #openstack-dev15:43
lorin1Anybody else having trouble getting to paste.openstack.org?15:43
jeblairmtaylor: ^15:43
*** markmc has joined #openstack-dev15:44
mtaylorooh. that's no good15:46
*** rnirmal has joined #openstack-dev15:46
westmaasjeblair: back15:48
jeblairwestmaas: wwkeyboard was asking about getting some patches merged to openstack-integration-tests.  based on the transcript of the meeting on wed, i added you to qa-core, so you can +2 reviews in gerrit now.15:51
mtaylorlorin1: fixed15:51
lorin1mtaylor: thx15:52
*** darraghb has quit IRC15:54
*** martine_ has joined #openstack-dev15:55
*** lorin1 has quit IRC15:59
*** adjohn has quit IRC16:03
openstackgerritA change was merged to openstack/swift: Fix documentation example.  https://review.openstack.org/82016:04
*** medberry is now known as med_out16:07
openstackgerritA change was merged to openstack/swift: Query only specific zone via swift-recon  https://review.openstack.org/70216:13
openstackgerritCarlos Marin proposed a change to openstack/keystone: First commit for Secret Question and Answer Extension: RAX-KSQA  https://review.openstack.org/86116:20
openstackgerritA change was merged to openstack/swift: Adding what acc/cont/obj into the ratelimit error messages  https://review.openstack.org/83816:22
*** lts has joined #openstack-dev16:26
*** Oneiroi has quit IRC16:37
*** Oneiroi has joined #openstack-dev16:37
*** Oneiroi has joined #openstack-dev16:37
*** jdurgin has joined #openstack-dev16:45
*** Oneiroi has quit IRC16:47
openstackgerritA change was merged to openstack/keystone: First commit for Secret Question and Answer Extension: RAX-KSQA  https://review.openstack.org/86116:55
*** lorin1 has joined #openstack-dev16:56
*** cp16net_ has joined #openstack-dev17:01
*** cp16net has quit IRC17:04
*** cp16net_ is now known as cp16net17:04
openstackgerritVish Ishaya proposed a change to openstack/nova: Makes snapshots work for amis. Fixes bug 873156  https://review.openstack.org/88917:07
uvirtbotLaunchpad bug 873156 in nova "Unhandled exception during 'nova image-create' caused by wrong destination format in qemu-img create" [Medium,New] https://launchpad.net/bugs/87315617:07
*** rbasak has quit IRC17:11
*** corrigac has quit IRC17:13
*** jdg has joined #openstack-dev17:23
openstackgerritJames E. Blair proposed a change to openstack-ci/git-review: Check .gitreview file in repo for location of gerrit.  https://review.openstack.org/89017:24
*** adjohn has joined #openstack-dev17:27
openstackgerritVish Ishaya proposed a change to openstack/nova: Makes snapshots work for amis. Fixes bug 873156  https://review.openstack.org/88917:30
uvirtbotLaunchpad bug 873156 in nova "Unhandled exception during 'nova image-create' caused by wrong destination format in qemu-img create" [Medium,New] https://launchpad.net/bugs/87315617:30
*** jhtran has joined #openstack-dev17:31
westmaasjeblair: cool thanks17:35
jhtran<comstud> i'm actually re-working that whole thing right now again17:36
jhtran<jhtran> oh snap17:36
jhtran<jhtran> nice!17:36
jhtran<comstud> it's related to some other work being done to separate network stuff out17:36
jhtran<comstud> but17:36
jhtran<comstud> this stuff doesn't perform like it needs to17:36
jhtran<jhtran> u think for my env i can get around it for now by just re-adding the prior lazy load relationship to fixed_ips?17:36
jhtran<comstud> so I'm restoring some of the old code for now17:36
jhtran<comstud> i thought I caught all of the cases where instance['fixed_ips'] was referenced17:36
jhtran<comstud> did I miss one?17:36
jhtran<comstud> Soon... instance['fixed_ips'] will be restored17:36
jhtran<comstud> with the work I'm doing now17:36
jhtran<jhtran> ok cool.  thanks17:36
jhtran<jhtran> i'll just hold off then and wait17:36
jhtran<jhtran> thanks again for your time17:36
jhtran<comstud> yeah.. it'll be added back to the joins when getting instances17:36
jhtranoh shit17:36
jhtranmy bad17:36
jhtranignore the above everyone17:36
kbringardignored :-)17:37
comstudhaha17:37
kbringardgood thing you weren't talking smack ;-)17:39
comstudtrue17:39
kbringardthat's what I call coding in the opc17:40
kbringardopen17:40
openstackgerritA change was merged to openstack/nova: Added vcpu_weight to models.  https://review.openstack.org/87417:41
*** vladimir3p has quit IRC17:41
openstackjenkinsProject nova-docs build #1,492: SUCCESS in 4 min 51 sec: https://jenkins.openstack.org/job/nova-docs/1492/17:50
openstackjenkinsJosh Kearney: Added vcpu_weight to models.17:50
openstackgerritVerification of a change to openstack/nova failed: Adds the ability to automatically issue a hard reboot to instances that have been stuck in a 'rebooting' state for longer than a specified window.  https://review.openstack.org/87217:51
*** vladimir3p has joined #openstack-dev17:55
vladimir3pvishy: ping17:55
*** cdub has quit IRC17:58
*** dtroyer has joined #openstack-dev18:03
*** bcwaldon has joined #openstack-dev18:03
openstackgerritA change was merged to openstack-ci/git-review: Check .gitreview file in repo for location of gerrit.  https://review.openstack.org/89018:04
*** cp16net has quit IRC18:04
*** cp16net has joined #openstack-dev18:05
*** dtroyer has quit IRC18:05
*** donaldngo_hp has joined #openstack-dev18:06
*** novas0x2a|laptop has joined #openstack-dev18:07
openstackgerritChuck Short proposed a change to openstack/nova: Check to see LXC container can actually run properly on a host before starting. Fixes LP: 83351  https://review.openstack.org/89118:07
*** dak has joined #openstack-dev18:12
openstackgerritBrian Waldon proposed a change to openstack/nova: Refactoring nova.tests.api.openstack.test_images  https://review.openstack.org/89218:23
openstackgerritBrian Waldon proposed a change to openstack/nova: Remove OSAPI v1.0  https://review.openstack.org/84018:23
*** martine has quit IRC18:25
*** martine has joined #openstack-dev18:25
openstackgerritBrian Waldon proposed a change to openstack/nova: Refactoring nova.tests.api.openstack.test_images  https://review.openstack.org/89218:26
*** zaitcev has joined #openstack-dev18:30
*** rnirmal_ has joined #openstack-dev18:32
*** dragondm has quit IRC18:32
*** martine has quit IRC18:34
*** code_franco_ has joined #openstack-dev18:34
*** rnirmal has quit IRC18:34
*** rnirmal_ is now known as rnirmal18:34
*** code_franco_ has quit IRC18:34
*** code_franco has quit IRC18:36
*** openstackjenkins has quit IRC18:37
*** openstackjenkins has joined #openstack-dev18:38
openstackgerritJosh Kearney proposed a change to openstack/nova: Adds the ability to automatically issue a hard reboot to instances that have been stuck in a 'rebooting' state for longer than a specified window.  https://review.openstack.org/87218:48
*** kbringard has quit IRC18:49
*** nati2 has joined #openstack-dev18:50
openstackgerritA change was merged to openstack/nova: Xenapi driver can now generate swap from instance_type  https://review.openstack.org/83018:54
*** kbringard has joined #openstack-dev18:56
openstackjenkinsProject nova-docs build #1,493: SUCCESS in 5 min 10 sec: https://jenkins.openstack.org/job/nova-docs/1493/19:01
openstackjenkinsRick Harris: Xenapi driver can now generate swap from instance_type19:01
openstackgerritA change was merged to openstack/nova: Adds the ability to automatically issue a hard reboot to instances that have been stuck in a 'rebooting' state for longer than a specified window.  https://review.openstack.org/87219:04
*** jdurgin has quit IRC19:04
*** jdurgin has joined #openstack-dev19:04
*** dragondm has joined #openstack-dev19:07
openstackgerritA change was merged to openstack/swift: make drive audit regexes detect 4-letter drives  https://review.openstack.org/75519:09
openstackgerritBrian Waldon proposed a change to openstack/nova: Refactoring nova.tests.api.openstack.test_images  https://review.openstack.org/89219:13
*** tryggvil_ has quit IRC19:16
openstackgerritA change was merged to openstack/nova: Ensure non-default FLAGS.logfile_mode is properly converted to an octet.  https://review.openstack.org/75819:19
*** mdomsch has joined #openstack-dev19:23
openstackjenkinsProject nova-docs build #1,494: SUCCESS in 4 min 46 sec: https://jenkins.openstack.org/job/nova-docs/1494/19:24
openstackjenkinsJosh Kearney: Adds the ability to automatically issue a hard reboot to instances that have been stuck in a 'rebooting' state for longer than a specified window.19:24
openstackgerritA change was merged to openstack/nova: Use latest version of SQLAlchemy  https://review.openstack.org/70819:30
openstackjenkinsProject nova-docs build #1,495: SUCCESS in 4 min 56 sec: https://jenkins.openstack.org/job/nova-docs/1495/19:31
openstackjenkinsadamg: Ensure non-default FLAGS.logfile_mode is properly converted to an octet.19:31
*** rnirmal has quit IRC19:34
*** rnirmal has joined #openstack-dev19:34
*** adjohn has quit IRC19:34
openstackgerritBrian Waldon proposed a change to openstack/openstack-chef: Remove OSAPI v1.0 from Nova's api-pate.ini  https://review.openstack.org/89319:37
openstackgerritBrian Waldon proposed a change to openstack/openstack-chef: Remove OSAPI v1.0 from Nova's api-pate.ini  https://review.openstack.org/89319:38
*** code_franco has joined #openstack-dev19:38
*** Vek has quit IRC19:39
openstackgerritBrian Waldon proposed a change to openstack/openstack-chef: Remove OSAPI v1.0 from Nova's api-pate.ini  https://review.openstack.org/89319:42
openstackjenkinsProject nova-docs build #1,496: SUCCESS in 4 min 50 sec: https://jenkins.openstack.org/job/nova-docs/1496/19:43
openstackjenkinsMark McLoughlin: Use latest version of SQLAlchemy19:43
*** adjohn has joined #openstack-dev19:45
*** lts has quit IRC20:11
*** med_out is now known as medbrry20:14
*** medbrry is now known as medberry20:14
*** rkukura has quit IRC20:23
openstackgerritA change to openstack/nova has been rejected: Fix pep8 errors  https://review.openstack.org/88520:25
*** rkukura has joined #openstack-dev20:25
*** kbringard has quit IRC20:29
*** kbringard has joined #openstack-dev20:30
*** nhubbard has joined #openstack-dev20:37
kbringardso, to make sure I'm understanding this correctly, there are no plans to release new PPA versions of the diablo branch to fix some of those issues discovered after the release, right?20:53
*** rkukura has quit IRC20:53
kbringardnew stable/milestone packages, I mean20:53
kbringardand if so, is there a recommended path to get those patches onto a system that is running packages from the PPA milestone repo?20:55
kbringardI'm trying to get this documented, since I have a feeling people are going to start asking20:55
*** toluene has joined #openstack-dev20:57
*** rkukura has joined #openstack-dev20:58
*** bcwaldon has quit IRC20:58
rmkmtaylor: Don't suppose there are diablo keystone packages available yet?20:59
rmkkbringard: Actually doing a build of the stable branch now heh.21:00
mtaylorrmk: crap. sorry, no - I've been buried in a few other things. still on my list21:00
kbringardrmk: you mean for the launchpad ppas? or an internal build?21:00
rmkcool np21:00
rmkkbringard: Internal since there isn't an official stable build yet21:00
rmkBut I'll gladly publish, nothing special about the build21:01
*** lorin1 has quit IRC21:01
kbringardah, right, yes… so does that mean there are plans for a new stable? I guess that's what I'm confused about21:01
rmkhttp://wiki.openstack.org/StableBranch21:01
rmkSounds like it based on that21:01
kbringardgoing forward it sounds like we don't want to build packages anymore21:01
kbringardbut just provide source and backported patches for the vendors to slipstream in upstream21:02
*** nhubbard is now known as nhubbard_away21:02
kbringardthen everyone will just get their packages from Fedora/Ubuntu/Whomever21:02
rmkThat's a bit scary21:02
kbringardthat's what I thought, but either way, I'm just trying to understand the plan… I don't entirely get it from the stable build wiki page :-)21:02
kbringardhttps://lists.launchpad.net/openstack/msg04748.html21:04
kbringarderr, wait21:05
kbringardhttps://lists.launchpad.net/openstack/msg04789.html21:05
kbringardspecifically:21:05
kbringard- We will not be uploading nova/swift/glance/keystone to PPAs.21:05
kbringard- We will still maintain a PPA with backport packages of depends for dev21:05
kbringardpurposes (things like libvirt) This will be a new PPA though, as there21:05
kbringardis really no point in having separate PPAs for each project any more.21:05
*** Oneiroi has joined #openstack-dev21:06
*** toluene has quit IRC21:09
notmynamekbringard: mtaylor: w r t a single PPA for dependencies--this needs to be addressed carefully. although we do have some common dependencies across projects, they, at times, have been dependent on different versions. for example, recently glance started using a newer version of webob that broke something in swift. we resolved it (by going to yet a newer version), but these sorts of things require good communication21:10
*** martine_ has quit IRC21:11
mtaylornotmyname: agree re: communication21:14
mtaylornotmyname: I think the main intent of that PPA is for developers for backports and not for deployments - so hopefully breakage there will cause someone to notice - OR, if it doesn't, we should figure out tests to put in to place to catch that stuff.21:15
mtaylornotmyname: but YES to making sure that we pay decent attention to the depend issues cross project21:15
rmkHow many people actually pushed for removing auto generated packages?21:15
rmkThe PPAs have been super helpful.21:15
rmkWere there actual users representing the group proposing their elimination, or just developers?21:16
openstackgerritJosh Kearney proposed a change to openstack/nova: Cancel any clean_reboot tasks before issuing the hard_reboot.  https://review.openstack.org/89421:16
rmkIt's just going to make it that much harder to get up and running.  As it stands now, add a few PPAs, few apt commands and you can run whichever version of OS you need.21:17
notmynamermk: we (swift deployers at rackspace) don't care because we don't use them at all. so why spend effort on something people don't use? the "we don't care" also means we don't care if they stay either21:17
notmynamewe maintain our own set of packages21:18
rmknotmyname: Your own packages because you use a different distro internally, or other reasons?21:19
kbringardI would argue that, assuming we do decide to get rid of the PPAs, we should still use them for the backports of diablo21:19
kbringardand use essex as a transitin21:19
kbringardtransition21:19
kbringardbecause conventional wisdom for diablo has been "Install from the milestone PPA repo"21:19
kbringardso you're going to have a lot of installs using that repo21:19
rmkI think the conclusion to eliminate packages was drawn by developers who stated they weren't using them, with users not being present to represent usage at the ODS.21:19
kbringardand if the required backport fixes never make it to those people, we're going to have a lot of pissed off users21:20
notmynamemtaylor: however, the dependencies are important. webob for example isn't updated in LTS so we have our own newer version of the code. similarly if we submit patches to a dependency, I'd hate to have to wait for ubuntu to include them before we can fix a bug or add a feature in an openstack project. repos for dependencies are important for deployments21:20
notmynamermk: other reasons. we use ubuntu internally for deployment. the openstack packages have gotten better, but they started out not meeting our needs at all. so we made our own (since we have a product to maintain)21:21
*** cp16net has quit IRC21:22
mtaylornotmyname: yeah - it's a tricky thing ... because once we start publishing package backport ppas, then we need to also maintain those for security fixes and what not ... and we wind up becomming like a mini distribution21:23
mtaylorrmk: ^^21:24
notmynamemtaylor: what I've always said we are anyway ;-)21:24
mtaylornotmyname: perhaps so :)21:24
openstackgerritAaron Lee proposed a change to openstack/openstack-integration-tests: Adding generic run_tests.sh  https://review.openstack.org/87021:24
kbringard'cause I can tell you, I'm running diablo from the milestone release, and 2 things in particular are a pain, one the source groups not working and 2 is the lazy load errors every other time I run euca-describe-instances21:24
kbringardbut the lazy load thing is like, 650 lines spread across like 12 files… that's a pain in the butt to try to monkeypatch21:25
villepnow thats fuckd.21:25
kbringardI'm not suggesting we maintain backport PPAs long term, necessarily, but I think we should at least do a maintenance release for diablo that fies some of the major pain points21:26
notmynamemtaylor: one other thing to keep in mind is that nova and swift are different. for example, the "stable branch" conversations may apply to nova, but they don't seem to fit for swift. the "Stable branch" in swift is master. if you ned an older version, pull it from the tag. but master is always stable (or it doesn't get merged)21:26
mtaylornotmyname: indeed.21:27
kbringardfies == fixed21:27
kbringarddammit, fixes21:27
kbringardtyping is hard21:27
mtaylorkbringard: I believe the intent is to maintain a backport branch at the moment - no consensus has been reached on how releases should come out of that from the project21:27
*** yogirackspace has joined #openstack-dev21:28
mtaylorkbringard: although the _distros_ certainly want to maintain it because once they ship something with diablo in it they kind of have to support that21:28
villepI noticed that there were roles defined for nova in: http://bazaar.launchpad.net/~nova-core/nova/github/view/head:/nova/api/ec2/__init__.py#L26321:28
mtaylorit's a weird little intersection here21:28
kbringardmtaylor: yea, I saw the mailing list stuff about it, my concern is that there isn't really wide spread support from the distros, even fro diablo21:28
villepany clues when swift roles are in ?21:28
kbringardand I know from helping people in #openstack all day that a good lot of people have diablo installed form the milestone PPA repo21:28
kbringardsince that was the conventional "how to install diablo" wisdom at the time21:29
notmynamekbringard: true, but that may be quite a selection bias because that's pretty much been the only way to get packages...21:29
mtaylorkbringard: agree... and I think that's actually one of the reasons to move to not making the packages ... I think us providing those packages implies that we're going to maintain and continue to update them in some way21:29
annegentleoh but it's such a pain point right now... so. very. painful. I can't tell people how to install Diablo successfully.21:30
mtaylorand apparently, (which was news to me) there was never really any project intent to continue to apply patches to and support the diablo release after it was released, other than via the distros21:30
notmynameannegentle: what is "diablo"? nova? swift? all of it?21:30
kbringardright, I'm not arguing that we should maintain packages long term, I just think that if we don't do at least some transition21:30
vladimir3pmtaylor: sorry guys for my ignorance prior to that, but are there any scripts for auto-package generation for ubuntu?21:30
kbringardand I'm talking specifically about nova21:30
rmkThe problem with relying on distro packages is that they're not going to be updated nearly often enough.21:30
kbringardwe're going to have a lot of people who are like "I can't even describe my instances reliably, this isn't stable software"21:31
annegentlenotmyname: I have a swift/keystone q on twitter for example21:31
mtaylorvladimir3p: not 100% what you mean? we have packaging branches, and can use those to generate packages21:31
annegentlenotmyname: so yes I mean all of it21:31
rmkI like that I can use whichever version of Ubuntu I want (for the most part), and get Diablo installed just by pointing at the PPAs.21:31
rmkIf you rely on the distros, you're going to get Ubuntu release = Diablo release.21:31
vladimir3pmtaylor: yep, that is what we need. Just never done it before for nova21:31
rmkAnd that's the end of that.21:31
rmkSo, one would need Ubuntu 11.10 to get Diablo.21:31
kbringardthis ^^ is my concern about diablo21:32
mtaylorrmk: yes. the problem is, maintaining that packaging and the backports meant we were working at cross-purposes from the ubuntu devs21:32
kbringardwith essex perhaps there will be wider adoption21:32
rmkAnd that's only true because 11.10 came out after Diablo.21:32
rmkWhat happens if Essex comes out in May?21:32
mtaylorbecause they were trying to make oneiric packages, many of the things of which broke packages for previous versions of ubuntu21:32
kbringardbut I would argue that there are very few people who are using the Ubuntu packages for Diablo21:32
rmkusers wait until October for Essex to make it into Ubuntu?21:32
mtaylorrmk: our release dates are tied to ubuntu release dates21:32
rmkI see21:33
mtaylorrmk: so we will always release before final freeze of the upcoming ubuntu21:33
kbringardyea, soren works on an ongoing basis to coordinate the openstack release with the ubuntu release21:33
kbringardat least that's been my understanding21:33
notmynamewhich doesn't address people using rhel :-)21:33
rmkmtaylor: That's cool then.  I suppose my only concern then would be the lack of the latest OS available for the latest LTS.21:33
mtaylorso, although I agree with rmk and kbringard in theory (I was one of the ones suggesting that we ensure backport packages exist for prior versions of ubuntu)21:34
kbringardanyway, my only point here, is that there are enough very visible issues with the current diablo milestone PPA packages, that we should do at least one more21:34
rmkmtaylor: I really like what you guys are doing right now.21:34
rmkmtaylor: I actually thought you guys were ahead of other projects in this regard.21:34
mtaylorwell - it got REALLY painful with the debian extremeley-poorly-managed-transition to dh_python221:34
kbringardone more PPA release that incorporates those issues21:34
mtaylordon't even get me started on the complete shit-show they made of that21:34
rmkYes, the stable PPA should reflect a stable release branch which is always being updated.21:35
rmkThat's the only piece missing in my opinion right now.21:35
rmkWhich is what kbringard has been saying.21:35
mtaylorbut that made is exceptionally difficult to have a single set of packaging that built on oneiric/sid as well as the versions that came before21:35
*** Vek has joined #openstack-dev21:35
mtaylorand yes - I personally agree...21:35
kbringardif we're going to get rid of the PPA's, then it is what it is, but we should probably not do it with the broken version of diablo sitting on there21:35
rmkI think you guys are going to hear more "Openstack is hard to install" comments if the PPAs go away.21:36
mtaylorfrom a project perspective, long-term maintenance has been the real sticking point21:36
rmkYou already get a lot of that and it's insanely easy using the PPAs.21:36
mtaylor:)21:36
mtaylorfair21:36
rmkMaybe reduce the overhead by choosing fewer distros to backport.21:37
kbringardthis is the last time I'll say it, I promise :-) but my only beef at the moment is that the version of diablo that most people seem to be installing, is the milestone ppa, which is currently fairly broken, so I think it would be in our best interests to at least do one more push of packages there that incorporate the backports fixes21:39
rmkkbringard: I agree with you 100%.21:39
rmkI'm having to hand-apply patches to Diablo as well right now, specifically for live block migration which doesn't work "out of the box".21:39
kbringardafter that if we want to get rid of the PPAs, then lets do it, but we can't tell people in the openstack docs that the way to install is to use the milestone ppas, and then be like "Yea, sorry, those are fucked, but we stopped supporting it"21:40
kbringardgood luck!21:40
kbringardthe diablo openstack docs, I should say21:40
notmynamekbringard: +121:41
rmkI mentioned this earlier but I think the negative responses to eliminating the PPAs weren't represented accurately at the design summit.21:41
rmkYou mainly had developers there.21:41
rmkIf the next release is going to be about the users, which is the theme I've been hearing, I think the last thing you want to do is take away a convenience service which already exists.21:42
openstackgerritKevin L. Mitchell proposed a change to openstack/nova: Add XML templates.  https://review.openstack.org/81821:42
annegentlekbringard: yes.21:43
rmkEnhancing it to include builds out of a "stable" branch for each project, pleased in the stable PPA would be the cherry on top for me.21:43
annegentlermk: also yes.21:43
rmkThat's the only thing missing.21:43
rmkplaced*21:43
annegentlemtaylor: will it help for me to try to plead this case on the ML?21:44
rmkAnyway, that's my two cents.  I'll reply to the thread if there's still time to change this decision.21:44
notmynamermk: does this meet your needs (imagine the same for nova if you need that): http://crashsite.github.com/swift_debian/21:44
notmynamermk: ^ has all of the dependencies and also a separate (stable!) repo for past versions21:44
notmynamermk: that's the repo we deploy from at rax for swift (cloud files)21:45
rmknotmyname: Yes that's great.  Basically I don't care where the repos are, as long as they exist for each project which satisfy all the deps.21:45
mtaylorannegentle: well, it would be great if you or rmk would say something on the ml21:45
rmkIf there's one for swift, another for nova, etc, not on launchpad, doesn't matter as long as the location is documented somewhere.21:45
rmkmtaylor: Will do.21:45
annegentlenotmyname: yes, I can doc packages that are known to work21:45
mtaylorso - the problem is for the other things that there is nobody currently tasked with maintaining packaging produced by the project21:46
mtaylorI'm CERTAINLY not saying it's a bad idea to make them - I've been championing them for a while now21:46
notmynamemtaylor: isn't that #43 on your list of stuff to do? ;-)21:46
rmkThere's a lack of consistency in that regard across packages.  In fact, I think that spans across the release process too.21:46
rmkerr projects not packages21:46
mtaylorbut with no policy for post-release updates for maintenance, it's a bit of a nightmare21:46
mtaylorI mean, I can cut trunk packages just fine21:47
mtaylorbut what happens post diablo release?21:47
rmkYeah that's a huge, huge issue.21:47
mtaylorwho owns the package contents? who fixes the bugs in them?21:47
rmkThough honestly it's worthwhile to tackle this within the OS project.21:47
mtaylorwith distro-generated packages, at least the distros are on the hook for fixing your bugs21:47
mtaylorit IS worthwhile21:47
notmynamemtaylor: rmk: since nobody on the openstack side is maintaining packages, we will continue to maintain the crashsite ones for swift21:47
mtaylorit's just that no one has stepped up and said they want to do it21:47
mtaylornotmyname: great!21:47
notmynamemtaylor: I definitely think someone should do it for openstack :-)   (although I expect pretty much every major deployer to maintain their own deploy repos)21:48
notmynamewhere major == large scale21:48
mtaylornotmyname: see - that's just the problem21:48
mtaylorthe people who are actually using this stuff at scale are maintaining their own repos (understandably)21:49
openstackgerritA change was merged to openstack/nova: Cancel any clean_reboot tasks before issuing the hard_reboot.  https://review.openstack.org/89421:49
mtaylorso we're not really getting that feedback into the project produced packages21:49
rmkmtaylor: You know a lot of that has to do with the lack of an updated stable package.21:49
*** adjohn has quit IRC21:49
rmkI have to cut my own packages too now because I need several patches just to fix critical issues in Diablo.21:49
rmkGranted having the packaging bzr makes this easy.21:50
*** rkukura has left #openstack-dev21:50
mtaylormy original discussions on packaging at ODS were on trying to make it easier for major deployers to contribute to the main packaging with the intent that perhaps we could produce packages that a major deployer wanted to install from21:50
mtaylorbut as we got in to it, it seemes as if we were trying to solve a problem for a use case that was never going to happen ... that is, none of the major deployers were going to use them, ever21:50
mtaylorwhich means we're producing packages which are clearly not good21:50
rmkMaybe not, but users do/are.21:51
notmynamemtaylor: but major deployers are more likely to have their own internal stuff too. at rax we also have a rackswift repo that includes proprietary auth and billing stuff21:51
mtaylornotmyname: there's a difference though - if you were making packages directly using upstream packaging source and just cutting them in to a repo, that would be one thing21:51
rmkIf automated trunk packages weren't being produced leading up to Diablo, I wouldn't have been testing Diablo actively.21:51
mtaylorbecause then the best way to fix a packaging issue would be to get the commit into packaging trunk21:51
mtaylor(which is what I was trying to get rolled out for essex for openstack)21:52
*** rnorwood has quit IRC21:52
mtaylorI'm happy to revisit the idea ... but I honestly need some sort of buy in from someone that having those packages is a goal, and that we want them to meet some set of criteria21:53
notmynamemtaylor: I think that smaller scale deployers will still use whatever package repo we provide (and I think rmk agrees)21:53
kbringardI personally don't mind installing from source to track trunk, but I can tell you, I help a shitton of people in #openstack and the reason I'm able to is because I was able to track trunk on a daily basis, so I knew most of what needed to be changed migrsting from cactus to diablo21:53
mtaylorwhich means, much as notmyname (and I) contend - that we are making a micro-distribution - and therefore have to figure out how to support ourselves as one21:53
rmkyep21:53
notmynamemtaylor: project autonomy! ;-)21:53
kbringardso there is definitely utility in tracking trunk21:54
mtaylornotmyname: no. that's the exact OPPOSITE of what we need here :)21:54
mtaylornotmyname: you providing swift packages is great and all - but how exactly do we determine that those work with nova/glance/keystone for a diablo thing? also, your project just releases again in 2 weeks... how does that work with ongoing maintenance?21:54
notmynamemtaylor: well, I certainly don't want to get into that debate again (at least now) ;-)21:54
mtaylornotmyname: aw...21:54
mtaylornotmyname: but we skipped it totally at the conference! :)21:55
notmynamewe've got a long plane ride to brazil :-)21:55
mtayloryes we do21:55
mtayloralthough I don't think we're on the same plane...21:55
mtaylorunless you are taking a terrible route21:55
notmynamelol21:55
mtaylorwe DO, on the other hand, have many hours of drinking in brazil ahead of us21:56
*** rkukura has joined #openstack-dev21:56
openstackjenkinsProject nova-docs build #1,497: SUCCESS in 5 min 2 sec: https://jenkins.openstack.org/job/nova-docs/1497/21:56
*** rnirmal has quit IRC21:56
openstackjenkinsJosh Kearney: Cancel any clean_reboot tasks before issuing the hard_reboot.21:56
kbringarddrinking debates are the best debates21:57
mtaylorhell yes21:57
notmynamewe determine that the releases work together 2 ways: 1) talk about it 2) the guarantee that each 6-month release works with the other projects (or else you wouldn't be a core project)21:57
mtaylortotally.21:57
mtaylorI'm talking about stable release updates21:57
mtaylorif we release this 6 month thing called diablo ... and then there are bugfixes which need to be applied - let's call them security fixes21:57
mtaylorhow does that thing called diablo get managed21:58
notmynamebut honestly, I have it easier on the swift side because we are required to be stable and backwards compatible all the time. nova/keystone/etc are in more of a state of flux and will be changing contracts more rapidly21:58
mtaylor++21:59
mtaylorthis is an easier problem when things aren't quite in as much rapid flux21:59
notmynameindeed. which lets me get up on my ivory tower and look down on everyone ;-)22:00
kbringardisn't that what the backports branch is all about? managing the patches for upstream distros to put in their packages?22:00
notmyname(that was totally kidding, if it wasn't clear)22:00
kbringardand again, I'm not advocating that we do this long term, I just think we need to make sure the diablo milestone packages are less bjorked22:01
kbringardeven if it's just one more push22:01
notmynamekbringard: agreed. broken packages are much worse than no packages at all22:01
notmyname(but on that note I'm mostly a spectator. I don't have much skin in the game for nova)22:01
kbringardyea, and for me, nova is the main show22:03
kbringardand I think for the majority of people22:03
notmynameI think you're right ;-)22:03
kbringardso anyway, sorry to stir up that hornet's nest22:03
kbringardlol, I was just trying to get clarification on what the plan was22:04
notmynamemtaylor: so there is noone on the openstack side who's job it is is to manage the packages for the projects?22:04
mtaylornotmyname: me.22:04
notmynamemtaylor: do you have minions?22:04
mtaylornotmyname: except that the unanswered policy stuff I mentioned is the main blocker22:04
*** dragondm has quit IRC22:05
mtaylornotmyname: i.e. - I can make packages - the big question is "what content goes in to them" ... this is especially tricky if the project itself is not producing post-release updates22:05
notmynameindeed22:05
mtaylornotmyname: but ... I'm working on gathering some minions22:05
kbringardmtaylor: yes, that is where what I'm proposing (more more package push) hits a bump22:05
kbringardmore more == one more22:06
notmynamemedberry: and so the "what content goes in to them" question leads to the stable branch discussions, right?22:06
notmynamemtaylor: ^22:06
mtaylornotmyname: yes. and we got _somewhere_ on those at least22:06
mtaylorin that we now have stable branches and teams tasked with maintaining them22:07
mtaylorturning the contents of those into releases is still without a person at the help22:07
mtaylorhelm22:07
notmynamefor everything but swift?22:07
mtaylornope. swift too22:07
notmynameah?22:07
notmynamewho?22:07
mtaylorthe stable branches are owned by the distros and deployers22:07
medberrynotmyname, nod.22:08
mtaylorso that any patches they're putting in to their distro releases have a place to land so that they can be sharead by others22:08
notmynameoh ok. so eg someone at canonical for ubuntu22:08
mtayloryup22:08
notmynamemedberry: sorry. autocomplete fail on my part :-)22:08
medberryyup22:08
mtaylorsomeone at piston, and at nebula, and at rax and at hp and redhat22:08
mtaylorat least, that's the list of stakeholders for those branches off the top of my head22:08
notmynamemtaylor: who at rax for swift? (If feel like I should know this person)22:09
notmynameah ok22:09
mtaylornotmyname: it's not a person at rax per-project at the moment22:09
mtaylornotmyname: at least, it's not specifically set up that way - I imagine given how swift is organized, someone from your group would likely want to be involved22:09
notmynames/want to/should/ :-)22:10
mtaylornotmyname: for nova, I think someone from westmaas's or pvo's group is the person we'd be thinking of, ish.22:10
mtaylornotmyname: s,s/want to/should/,s/should/want to/,22:10
notmynamemtaylor: heh. I'm not trying to build fiefdoms. just figuring that the swift devs should be involved in maintaining swift :-)22:13
mtaylornotmyname: god no - I completely agree22:13
mtaylornotmyname: it's more of a "hey, we're gonna set up stuff for folks to maintain this stuff ... now somebody should probably maintain this stuff"22:14
notmynameI do think we (swift) can and should do a better job, long term, of supporting some older versions of swift. currently our team isn't really set up to do this, but it is something we should acknowledge22:14
mtaylor++22:15
mtaylorand I think that's actually across the board22:15
mtaylornobody is really set up to support older versions of stuff22:15
mtayloryou're in a decent place beacause most of the time just upgrading to the latest swift is unlikely to completely hose you22:16
notmynameit's an advantage, but "just upgrade to a newer version" is rarely helpful advice to other deployers22:16
notmynameI can be pretty sure it won't break anything, but the other guys will have their own policies and red tape to go through22:17
mtaylor++22:18
* notmyname wonders about auto-upgrades in the project...nah, so many people would hunt me with pitchforks22:18
* mtaylor is always amused that people are fine upgrading from 1.0-1 to 1.0-2 but not from 1.0 to 1.1 ... even though the debian maintainers could have added god-knows-what sort of patches in -222:18
kbringardnotmyname: use sparkle!22:18
kbringard:-p22:18
notmynameperfect!22:19
kbringardmtaylor: I agree 100%22:19
mtaylorjesus. is that another one of those hippy web 2.0 ruby bullshits?22:19
mtayloryup22:19
kbringardit's even more entertaining trying to explain debian patches to a PCI auditor22:19
mtaylorsoftware updates for hipster-coder-macs22:19
* mtaylor pukes on everyone22:20
mtaylorkbringard: I'll bet!22:20
kbringardwhen your entire external scan is red because the "version" is from like 10 years ago22:20
kbringardeven though every security patch has been slipstreamed in22:20
* kbringard shakes his fist in the air22:21
* mtaylor loved the redhat kernel versions from rhel422:21
kbringardanyway, good discussion guys… so what are we going to do about it? :-p22:22
mtaylorthat were labeled 2.422:22
mtaylorexcept that they had backported most of 2.6 in22:22
mtaylorbut that way it didn't count as a new kernel version22:22
kbringardoh, that's terrible22:22
mtaylorkbringard: I'll send a follow up email to the list ... let me see what kind of resources for supporting something I can come up with22:22
mtayloralong with some concrete suggestions22:22
kbringardfor PCI I had to search for every single vulnerability ID on the debian security site and reference it22:23
mtaylorand then maybe notmyname and I can bum-rush the ppb when they aren't looking22:23
kbringardhehe22:23
kbringardif you're in austin I'll send my boss down22:23
kbringardhe's good at bum rushin'22:23
mtaylorit's all virtual - I'm in New York ... but I'll take the help anyway22:23
kbringardhehe, yea, I'm in Colorado22:24
kbringardeither way, well, the only concrete thing I think is essential is that we do at least one more diablo milestone PPA push with packages that incorporate fixes for some of the high profile things we've seen in the diablo release22:24
kbringardso there you have it22:25
kbringard:-)22:25
kbringardthanks for taking the time to talk about it22:25
kbringardI need to call it a day, have a good one guys22:25
*** kbringard has quit IRC22:26
*** dubsquared has quit IRC22:26
*** wwkeyboard has left #openstack-dev22:28
*** code_franco has quit IRC22:31
*** misheska has joined #openstack-dev22:33
openstackgerritYogeshwar Srikrishnan proposed a change to openstack/keystone: Fixing issue #843226.  https://review.openstack.org/89522:35
openstackgerritYogeshwar Srikrishnan proposed a change to openstack/keystone: Fixing issue #843226. Changes to throw appropriate faults during token validation. Fixing issue  #854929. Changing incorect 'text/json' references to 'application/json'.  https://review.openstack.org/89622:35
*** yogirackspace has left #openstack-dev22:41
*** rkukura has quit IRC22:49
*** medberry is now known as med_out22:50
*** jdg has quit IRC23:03
*** jhtran has quit IRC23:04
*** fyang has quit IRC23:18

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