Thursday, 2014-04-10

*** _bluev has quit IRC00:14
*** RockKuo has joined #openstack-swift00:17
pelusebobf: let me (or anyone here) know if you need some help - great to see someone trying to kick the tires00:23
*** matsuhashi has joined #openstack-swift00:26
*** shri has quit IRC00:40
*** mlanner has quit IRC00:50
*** piousbox has quit IRC00:51
*** mlanner has joined #openstack-swift00:51
zackmdavisls00:51
*** dmorita has joined #openstack-swift00:59
*** saschpe has quit IRC01:04
*** saschpe has joined #openstack-swift01:06
*** bobf has quit IRC01:13
*** corrigac has joined #openstack-swift01:18
*** SpamapS_ has joined #openstack-swift01:21
*** taras___ has joined #openstack-swift01:21
*** StevenK_ has joined #openstack-swift01:21
*** alpha_ori has quit IRC01:22
*** SpamapS has quit IRC01:22
*** taras_ has quit IRC01:22
*** cschwede has quit IRC01:22
*** alpha_ori_ has joined #openstack-swift01:22
*** StevenK has quit IRC01:22
*** alpha_ori_ is now known as alpha_ori01:23
*** mordred has quit IRC01:23
*** bsdkurt has quit IRC01:23
*** akscram has quit IRC01:23
*** ccorrigan has quit IRC01:23
*** wkelly has quit IRC01:23
*** amandap has quit IRC01:23
*** sileht has quit IRC01:24
*** amandap_ has joined #openstack-swift01:24
*** wklely has joined #openstack-swift01:24
*** mordred has joined #openstack-swift01:24
*** StevenK_ is now known as StevenK01:24
*** cschwede has joined #openstack-swift01:24
*** bsdkurt has joined #openstack-swift01:24
*** sileht has joined #openstack-swift01:24
*** akscram has joined #openstack-swift01:25
*** _bluev has joined #openstack-swift01:25
*** _bluev has quit IRC01:29
*** gadb has joined #openstack-swift01:30
*** csd has quit IRC01:39
*** sudorandom has quit IRC01:46
*** nosnos has joined #openstack-swift01:48
*** sudorandom has joined #openstack-swift01:48
*** bill_az_ has quit IRC01:54
*** saschpe has quit IRC02:00
*** saschpe has joined #openstack-swift02:03
*** changbl has joined #openstack-swift02:07
*** Gue______ has joined #openstack-swift02:11
*** lollipop has joined #openstack-swift02:11
lollipopI have created an image from glance with swift successfuly, how I can list the image file from swift client?02:13
lollipop"swift list" can list other files but the image file02:13
*** byeager has joined #openstack-swift02:21
openstackgerritYuan Zhou proposed a change to openstack/swift: Update swift-container-info to be storage policy aware  https://review.openstack.org/8630402:39
*** byeager has quit IRC02:49
*** zaitcev has quit IRC03:00
*** Gue______ has quit IRC03:04
*** praveenkumar has joined #openstack-swift03:07
*** praveenkumar has quit IRC03:10
*** praveenkumar has joined #openstack-swift03:11
*** zackf has joined #openstack-swift03:17
*** zaitcev has joined #openstack-swift03:19
*** ChanServ sets mode: +v zaitcev03:19
*** zackf has quit IRC03:20
*** matsuhashi has quit IRC03:22
*** zackf has joined #openstack-swift03:24
*** zackf has quit IRC03:30
*** matsuhashi has joined #openstack-swift03:32
*** mmcardle has joined #openstack-swift03:39
*** haomaiwang has joined #openstack-swift03:46
*** mmcardle has quit IRC03:49
*** haomaiw__ has quit IRC03:49
*** wklely is now known as wkelly03:59
*** nosnos has quit IRC04:09
*** ppai has joined #openstack-swift04:11
*** chandan_kumar_ has joined #openstack-swift04:14
*** cheri has joined #openstack-swift04:21
*** chandan_kumar_ has quit IRC04:21
*** zhiyan_ is now known as zhiyan04:22
*** cheri has quit IRC04:31
*** ppai has quit IRC04:34
*** chandan_kumar_ has joined #openstack-swift04:35
*** cheri has joined #openstack-swift04:43
*** gyee has quit IRC04:47
*** nosnos has joined #openstack-swift04:47
*** ppai has joined #openstack-swift04:51
*** bill_az has joined #openstack-swift04:52
*** mmcardle has joined #openstack-swift04:53
*** mmcardle has quit IRC05:03
*** ppai has quit IRC05:21
*** Longgeek_ has joined #openstack-swift05:23
*** Longgeek_ has quit IRC05:24
*** haomaiwang has quit IRC05:28
*** chandan_kumar_ has quit IRC05:31
*** bill_az has quit IRC05:33
*** cheri has quit IRC05:40
*** haomaiwa_ has joined #openstack-swift05:50
*** cheri has joined #openstack-swift05:53
*** ppai has joined #openstack-swift05:54
*** zaitcev has quit IRC06:10
*** Longgeek_ has joined #openstack-swift06:15
*** Longgeek_ has quit IRC06:15
*** SpamapS_ is now known as SpamapS06:20
*** SpamapS has joined #openstack-swift06:20
*** psharma has joined #openstack-swift06:23
openstackgerritA change was merged to openstack/swift: Update swift-container-info to be storage policy aware  https://review.openstack.org/8630406:25
*** scohen has joined #openstack-swift06:36
*** chandan_kumar has joined #openstack-swift06:38
*** scohen has quit IRC06:38
*** scohen has joined #openstack-swift06:40
*** nshaikh has joined #openstack-swift07:14
*** mmcardle has joined #openstack-swift07:19
*** zigo has quit IRC07:29
hugokuoAnyone ever user cname_lookup middleware ?  Where is the proper position to insert the middleware in the pipline ?07:30
lollipopcan we run "swift list" with local auth, without keystone?07:46
lollipopI mean to check the swift status passing by keystone auth07:47
*** _bluev has joined #openstack-swift07:49
*** _bluev has left #openstack-swift07:50
*** ashish_ has joined #openstack-swift07:50
ashish_-+07:50
*** jamie_h has joined #openstack-swift07:56
ashish_I have a swift all in one installation on a single node.I am using a loopback device to create 4 nodes,I am running short of disk space.Could anyone tell me how to increse the storage capacity of my nodes.08:11
*** ashish_ has quit IRC08:11
*** ashish_ has joined #openstack-swift08:12
ashish_I have a swift all in one installation on a single node.I am using a loopback device to create 4 nodes,I am running short of disk space.Could anyone tell me how to increse the storage capacity of my nodes.08:12
ashish_Plese help.08:12
*** tanee-away is now known as tanee08:13
*** tanee is now known as tanee-away08:14
*** tanee-away is now known as tanee08:14
*** tanee has quit IRC08:14
*** tanee-away has joined #openstack-swift08:15
*** tanee-away is now known as tanee08:16
mmcardledoes any one know what change the following refers to - "Prevent static large objects from containing other static large objects" in https://github.com/openstack/swift/blob/master/CHANGELOG#L43208:17
*** haomaiwa_ has quit IRC08:18
*** haomaiwang has joined #openstack-swift08:19
*** matsuhashi has quit IRC08:21
*** haomaiw__ has joined #openstack-swift08:21
*** matsuhashi has joined #openstack-swift08:21
*** zigo has joined #openstack-swift08:23
*** haomaiwang has quit IRC08:24
*** matsuhashi has quit IRC08:25
*** cheri has quit IRC08:25
*** cheri has joined #openstack-swift08:26
*** d89 has joined #openstack-swift08:35
*** matsuhashi has joined #openstack-swift08:37
*** mmcardle has quit IRC08:38
*** mmcardle has joined #openstack-swift08:41
*** lollipop has quit IRC08:47
*** mmcardle has quit IRC09:05
*** mmcardle has joined #openstack-swift09:06
*** ashish_ has quit IRC09:06
*** gadb has quit IRC09:20
*** matsuhashi has quit IRC09:30
*** foexle has joined #openstack-swift09:31
*** matsuhashi has joined #openstack-swift09:34
*** zhiyan is now known as zhiyan_09:39
openstackgerritChristian Schwede proposed a change to openstack/swift: RADOS (CEPH) DiskFile Backend  https://review.openstack.org/6021509:42
*** mkollaro has joined #openstack-swift09:51
*** Longgeek_ has joined #openstack-swift09:58
*** mmcardle has quit IRC09:59
*** mmcardle has joined #openstack-swift10:02
*** Longgeek_ has quit IRC10:02
openstackgerritAlistair Coles proposed a change to openstack/swift: Restrict keystone cross-tenant ACLs to IDs  https://review.openstack.org/8643010:11
*** matsuhashi has quit IRC10:20
*** Longgeek_ has joined #openstack-swift10:22
*** mmcardle has quit IRC10:24
*** matsuhashi has joined #openstack-swift10:25
*** d89 has quit IRC10:27
*** mmcardle has joined #openstack-swift10:28
*** Longgeek_ has quit IRC10:35
*** d89 has joined #openstack-swift10:36
*** zhiyan_ is now known as zhiyan10:41
*** mmcardle has quit IRC10:41
*** mmcardle has joined #openstack-swift10:54
*** nosnos has quit IRC10:59
*** lpabon has joined #openstack-swift10:59
*** nosnos has joined #openstack-swift10:59
*** lpabon has quit IRC10:59
*** cheri has quit IRC11:01
*** mmcardle has quit IRC11:02
*** nosnos has quit IRC11:03
*** mmcardle has joined #openstack-swift11:04
*** ppai has quit IRC11:04
*** Trixboxer has joined #openstack-swift11:06
*** matsuhashi has quit IRC11:14
*** acoles is now known as acoles_away11:15
*** RockKuo has quit IRC11:15
*** mmcardle has quit IRC11:17
*** cheri has joined #openstack-swift11:18
*** mmcardle has joined #openstack-swift11:19
*** ppai has joined #openstack-swift11:21
*** matsuhashi has joined #openstack-swift11:22
*** zanc has joined #openstack-swift11:24
*** mkerrin has quit IRC11:25
*** mmcardle has quit IRC11:29
*** matsuhashi has quit IRC11:31
*** mkerrin has joined #openstack-swift11:32
*** matsuhas_ has joined #openstack-swift11:33
*** dmorita has quit IRC11:35
*** bill_az has joined #openstack-swift11:40
*** peterbus_ has quit IRC11:53
*** praveenkumar has quit IRC11:54
*** peterbusque has joined #openstack-swift11:54
*** matsuhas_ has quit IRC11:57
*** mkollaro has quit IRC12:01
*** mkollaro1 has joined #openstack-swift12:01
*** nshaikh has quit IRC12:03
*** JuanManuelOlle has joined #openstack-swift12:07
*** mmcardle has joined #openstack-swift12:09
*** cheri has quit IRC12:10
*** jamie_h has quit IRC12:13
*** mmcardle has quit IRC12:20
*** praveenkumar has joined #openstack-swift12:30
*** ppai has quit IRC12:33
*** mkollaro has joined #openstack-swift12:36
*** jamie_h has joined #openstack-swift12:37
*** mkollaro1 has quit IRC12:39
*** joeljwright has joined #openstack-swift12:47
joeljwrightIn order to resolve the check-grenade-dsvm test fail with the patch here https://review.openstack.org/#/c/85453/ it seems I need to propose a change to openstack/requirements to be included in the stable/havana branch, but it's not clear to me how I should go about this12:53
joeljwrightcan someone help me out with the procedure to propose a change to a stable branch...12:54
*** nacim has joined #openstack-swift12:56
*** judd7 has joined #openstack-swift12:57
openstackgerritChristian Schwede proposed a change to openstack/swift: RADOS (CEPH) DiskFile Backend  https://review.openstack.org/6021512:59
*** tdasilva has joined #openstack-swift13:05
*** nshaikh has joined #openstack-swift13:12
*** JuanManuelOlle has quit IRC13:18
*** nacim has quit IRC13:20
openstackgerritYuan Zhou proposed a change to openstack/swift: Clean up swift-object-info/swift-get-nodes bin files  https://review.openstack.org/8659313:29
*** saschpe has quit IRC13:32
*** saschpe has joined #openstack-swift13:37
*** judd7_ has joined #openstack-swift13:43
*** judd7 has quit IRC13:45
*** saju_m has joined #openstack-swift13:50
*** zackf has joined #openstack-swift13:55
*** corrigac has quit IRC14:02
*** G________ has joined #openstack-swift14:02
*** praveenkumar has quit IRC14:05
*** corrigac1 has joined #openstack-swift14:05
*** joeljwright has quit IRC14:06
openstackgerritA change was merged to openstack/python-swiftclient: Python 3: fix tests on HTTP headers  https://review.openstack.org/8471114:08
*** mmcardle has joined #openstack-swift14:10
*** psharma has quit IRC14:15
*** praveenkumar has joined #openstack-swift14:32
*** G________ has quit IRC14:32
*** chandan_kumar has quit IRC14:47
*** nshaikh has quit IRC14:49
*** mmcardle has quit IRC14:50
*** mmcardle has joined #openstack-swift14:51
*** tanee is now known as tanee-away14:58
*** Guest_ has joined #openstack-swift15:00
*** saju_m has quit IRC15:05
*** tanee-away is now known as tanee15:05
*** piyush1 has joined #openstack-swift15:05
*** foexle has quit IRC15:12
*** IRTermite|away has joined #openstack-swift15:12
*** saschpe has quit IRC15:14
*** saschpe has joined #openstack-swift15:23
*** amandap_ is now known as amandap15:27
*** _bluev has joined #openstack-swift15:33
*** mwstorer has joined #openstack-swift15:35
openstackgerritDonagh McCabe proposed a change to openstack/swift: Restrict keystone cross-tenant ACLs to IDs  https://review.openstack.org/8643015:39
notmynamegood morning world15:40
*** cheri has joined #openstack-swift15:42
*** mkollaro1 has joined #openstack-swift15:43
*** mkollaro has quit IRC15:43
*** IRTermite|away has quit IRC15:44
creihttorgomatic: ping15:44
creihthttps://bugs.launchpad.net/swift/+bug/130602715:44
creihtnotmyname: -^15:45
notmynamecreiht: ack15:45
creihtnotmyname: not really sure what to do about that15:47
creihtwas hoping torgomatic would have some insight, if he isn't out15:47
notmynamecreiht: ya. IIRC that patch was written because the devstack stuff was bombing on some manifests testing15:48
notmynameI don't remember exactly what the testing was. maybe not manifests15:48
notmynamecreiht: in about 10 minutes I'm going to start a 2 hour run of meetings, so I won't be here in IRC15:50
notmynamecreiht: is this somethign you are looking more at? in your opinion is this a release issue or just an FYI?15:50
*** mkollaro1 has quit IRC15:50
* notmyname is assuming a release issue15:50
creihthehe15:50
creihtI dunno15:50
creihtnotmyname: I just started looking at it this morning15:51
notmynameok. thanks. let me know what you find15:51
creihtafter pandemicsyn started noticing it in our dev cluster15:51
claygcreiht: the traceback on shutdown is the only problem - logging comes back up and starts working cleanly?15:53
creihtI'll check15:54
creihtthought might be a bit15:55
creihtIs it time to just stop supporting 2.6? :)15:55
notmynamewe kinda did that a while back, tacitly. but with the "well, if it breaks 2.6 RAX will let us know and we'll fix it"15:57
creihtheh15:57
claygick, we still have the py2.6 unittets!15:57
claygi don't really maintain my lucid saio anymore :\15:58
*** russellb has quit IRC15:59
*** russellb has joined #openstack-swift15:59
creihtso doing a little experimentation it looks like everything still works16:01
*** scohen has quit IRC16:02
creihtjust spews a lot of traceback info into the error logs16:02
creihtwhich is annoying16:02
creihtnot sure if you want it to be a release blocker16:02
*** redbo has quit IRC16:03
peluseclayg:  did we decide we *did* want to update SAOI for SP support (and just have the same davies on both rings)?  I think its a good idea16:03
peluseSAIO...16:03
*** redbo has joined #openstack-swift16:03
*** ChanServ sets mode: +v redbo16:03
creihtthere was another issue that we were having related to logs16:04
creihtI need to see if this was related, and will ask pandemicsyn when he gets in16:04
claygpeluse: do you need me to send you a new keyboard?16:05
clayg:P16:05
pelusebobf:  sorry I missed your chat earlier... I'll be in and out today.  Wrt your question though, remakerings has not yet been udpated to support multiple policies (this my question to clayg).  You'd have to manually edit swift.conf and either manually run the same commands in remakerings (with -index after object) or just copy/rename the ring file that's created for you as the 2nd ring16:06
claygcreiht: yeah definately annoying, please do update if pandemicsyn thinks there maybe be other issues than the traceback...16:06
peluseclayg:  I actually got one!  Now I have to get used to it :)16:06
clayglol!16:06
*** mkollaro has joined #openstack-swift16:08
claygpeluse: I think the storage_policies development guide should include instructions for modifying an existing saio to have storage policies setup, and the saio_development guide should link to that at the end, or maybe next to the remakerings and somewhere around the ref to swift.conf16:08
peluseclayg:  or we could have 2 files built in SAIO that could be copied over to make it SP (swift.conf and remakerings) along with the instructions16:08
peluseclayg:  or both really (instructions for modifying and making it easy to setup the first time)16:09
creihtclayg: so the thing that is kind of annoying is that the container-updater spams that every pass16:09
* peluse will be back in a few...16:10
claygcreiht: oh that's weird...16:10
claygcreiht: i wonder why?16:10
creihtdunno16:12
creihtjust finding this out myself :)16:12
creihtI'm out for a bit, but will check back in later16:12
creihtbtw, in our dev cluster, I see that error constantly running over and over again in the logs16:13
creihtfor container-updater16:13
creihtlikely because we don't have a huge number of containers in it16:13
creihtheh16:14
creihtjobs.log on one server is 1MB, jobs.error is 3G :)16:15
*** cheri has quit IRC16:16
*** ashish_ has joined #openstack-swift16:17
mmcardledoes any one know what change the following refers to - "Prevent static large objects from containing other static large objects" in https://github.com/openstack/swift/blob/master/CHANGELOG#L432 16:28
*** gyee has joined #openstack-swift16:34
*** piousbox has joined #openstack-swift16:42
*** corrigac1 has left #openstack-swift16:42
*** fbo is now known as fbo_away16:46
*** saju_m has joined #openstack-swift16:48
claygcreiht: I'm not really having any luck reproing16:48
claygI mean I think just overriding close to catch and ignore the KeyError would fix it...16:49
claygcreiht: i'm on python2.6.9 tho :\16:50
*** tanee is now known as tanee-away16:51
*** ashish_ has quit IRC16:56
*** ashish_ has joined #openstack-swift16:57
*** ashish__ has joined #openstack-swift16:58
*** lpabon has joined #openstack-swift17:07
openstackgerritClay Gerrard proposed a change to openstack/swift: Supress traceback in exitfunc on old versions of Python  https://review.openstack.org/8665417:08
claygcreiht: still trying to duplicate, bringing up a lucid box17:09
*** csd has joined #openstack-swift17:17
ashish__ I have a swift all in one installation on a single node.I am using a loopback device to create 4 nodes,I am running short of disk space.Could anyone tell me how to increase the storage capacity of my nodes.17:17
ctennisadd more disks?17:19
ashish__ctennis is there a way I can increase the space in the existing nodes.17:21
ctennisare you doing a loopback device on top of a file in a filesystem?  I guess I don't understand how your device structure is setup.17:22
ashish__ctennis I'm using a loopback device on top of the srv directory in ubuntu.17:23
ctennisright but a loopback device is connected to a file in the filesystem17:24
ctennishow did you create the device?17:24
*** zaitcev has joined #openstack-swift17:25
*** ChanServ sets mode: +v zaitcev17:25
ashish__This is how I did it. http://paste.openstack.org/show/75489/17:26
notmynameashish__: just to make sure I understand this..you aren't using this as a production system right?17:27
ashish__notmyname no I am using the swift all in one installation on a single node.Just for testing purpose17:28
notmynameashish__: then in that case, delete the current loopback devices, change the "1GB" value in line 4 of your paste, and start over17:29
ashish__notmyname but doing so makes me lose all my data.Doesnt it?17:29
*** _bluev has quit IRC17:30
notmynameyes. but you just said it's for testing purposes. if you've got data on there you can't lose, then it's not for testing purposes17:30
zaitcevportante: I'm sorry, but I'm not a fan of confusing "automation" when I am trying to pinpoint problems, which is what testing is for. If I set the variable, I want it to run functests. If I don't set the variable, I want it to do what it did before. And your patch blows that. I hope I am not asking for too much.17:33
ashish__notmyname got it.How can I add a new node to the existing loopback device17:33
notmynameashish__: you mean adding a new loopback device?17:34
openstackgerritDonagh McCabe proposed a change to openstack/swift: Restrict keystone cross-tenant ACLs to IDs  https://review.openstack.org/8643017:34
*** d89 has quit IRC17:35
ashish__notmyname yes I want to add a new loopback device and integrate it with swift17:35
notmynameashish__: and just to be explicit, your setup is ok for swift dev work, but it isn't really a good POC to simulate a prod deployment, nor is it a good prod deployment at all17:35
notmynameashish__: wouldn't that simply be changing the loop constraints in your pastebin? eg change 4 to 5 or 6?17:36
ashish__notmyname I did not get your point.17:36
*** mmcardle has quit IRC17:37
notmynameashish__: I'm not sure what you are trying to do. what are you hoping to gain by adding another loopback device? what is the problem you are solving?17:38
ctennisashish__ add another loopback device like you have in another spot, or use truncate to extend the current one and use xfs to extend the mount size17:39
ashish__notmyname my current loopback device is running short of space.So is there a solution17:40
ashish__ctennis Thanks.But would that add more space to my existing nodes17:40
ctennisyou need to use the ring builder to leverage the new space17:40
ashish__ctennis could you tell me how its actually done17:41
ctennishttp://docs.openstack.org/developer/swift/admin_guide.html17:41
ctennismostly the same way you did it the first time17:41
ashish__ctennis thanks But I still did not get what needs to done.17:46
zaitcevashish_: once you have the device added and mounted under /src/node, do the "swift-ring-builder add" like you did before only with the new device.17:49
*** mkollaro has quit IRC17:50
*** piyush1 has quit IRC17:53
ashish__zaitcev i am following the http://docs.openstack.org/developer/swift/development_saio.html tutorial but in this tut there's no mention of swift ring builder.Thanks17:54
zaitcevGood grief. That's a sudden blowback for those who thought that doc/saio/bin was a good idea. The users have NO CLUE what they fuck they are doing anymore.17:57
ctennisashish__: it's happening in the remakerings script17:58
ctennislook in there, it will have the steps17:58
zaitcevcommit ba5fe5f39e18fe8e1483a3b5851f044fe3358d0b17:58
zaitcevAuthor: Peter Portante <peter.portante@redhat.com>17:58
ashish__ctennis Thanks17:59
zaitcev"Many of the large files are included in the tree and the script now leverages a checked out swift tree to provide those files so that users don't have to cut/paste text from the document. The contents of those files are still included in the document for reference."17:59
zaitcevBut they are not included17:59
clayglol @ zaitcev18:02
ashish__zaitcev. Thanks got ur point.So in case I want to increase the capacity of the existing loopback device Would this work http://paste.openstack.org/show/75492/18:03
zaitcevashish_: NO18:03
zaitcevoriginal remakerings only contains commands for stock loopbacks18:03
ashish__zaitcev.Could you tell me how could that be done.18:03
zaitcevjust edit the script, it should be obvious once you're in it18:04
ctennisashish__: I think your best bet is to just start over, and make a bigger loopback to begin with18:05
ashish__ctennis actually I wanted to learn how to scale up swift.18:07
zaitcevit can't be that hard. vi ~/bin/remakerings18:08
ashish__zaitcev thanks what do I need to do after this18:10
claygso i added a localrc option to make vagrant-swift-all-in-one's loopback partition size configurable... but I guess that's not really what ashish__ needs...18:13
*** Guest_ has joined #openstack-swift18:14
*** ashish_ has quit IRC18:20
*** ashish__ has quit IRC18:20
*** ashish_ has joined #openstack-swift18:22
*** ashish_ has quit IRC18:22
*** ashish_ has joined #openstack-swift18:23
*** zul has quit IRC18:25
portantezaitcev: what files are not included?18:25
creihtclayg: hey just got back sorry, any luck reproducing?18:26
zaitcevportante: the one we're not supposed to copy-paste anymore18:26
zaitcevportante: in ashish's case it's remakerings18:26
*** zackf1 has joined #openstack-swift18:26
*** zackf has quit IRC18:26
claygcreiht: still trying to get my swift intalled on lucid - I'm sort of not trying that hard, but I occasionally flip over to that window and punch a few buttons18:27
creihthaha18:27
zaitcevAs I see the problem here, ashish_ managed to install SAIO without ever running swift-ring-builder or understanding what it does. As a result, he's completely powerless when he needs to add one device to the cluster.18:27
claygcreiht: it's like impossible to install swift on lucid now right?  You have to hold your tounge really funny and make some sort of child sacrifice to the gods or reasonable python packages or something?18:28
creihtlol18:28
zaitcevportante: So, your commit vastly improved convenience of quick-setup of SAIO, but made it less of an education tool, evidently...18:28
creihtclayg: that's only true if you try installing it with pbr ;P18:28
portantezaitcev: remakerings appears in my tree18:29
*** mkollaro has joined #openstack-swift18:29
zaitcevportante: oh. You meant that they're included into tree, not into development_saio.rst18:30
portantethey are in both18:30
*** zackf1 has quit IRC18:30
*** zackf has joined #openstack-swift18:30
claygportante: no, not the bin scripts i don't think18:30
portantewe use the doc include feature last I checked18:30
portanteclayg: hmmm18:30
claygthe didn't get the inline ref feature18:30
ashish_zaitcev I have run the swift-ring-builder before and do know what it does.But am still not getting how to add a device.Please help.i am still a third year student.Learnin Days.18:30
zaitcevgrep -l swift-ring-builder hail/swift-tip/doc/source/*.rst18:31
*** jergerber has joined #openstack-swift18:31
zaitcevokay, perhaps it's an isolated case18:32
claygzaitcev: don't the multi node docs hav something on this or the admin docs or somewhere?18:33
zaitcevclayg: multi has everything18:33
ashish_zaitcev could you please tell me what should I do now.18:33
claygashish_: read this http://docs.openstack.org/developer/swift/admin_guide.html18:35
zaitcevashish_: look at http://docs.openstack.org/developer/swift/howto_installmultinode.html, hopefuly it helps. It has swift-ring-builder xxx add18:35
zaitcevoh yeah, clayg is right, that one is even better18:35
zaitcevportante: so, what do you think about the snippet of code I posted to 66108?18:36
zaitcevportante: if that one is accepptable to you, it would be fine to me too18:36
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8668018:36
ashish_clayg zaitcev thanks for your help.and thanks for being so patient.18:37
zaitcevportante: my test.conf has no constraints, and why would it?18:37
openstackgerritPeter Portante proposed a change to openstack/swift: Add includes of referenced SAIO bin scripts  https://review.openstack.org/8668118:37
portantezaitcev: let me look18:37
*** zul has joined #openstack-swift18:39
*** ashish_ has quit IRC18:40
creihtclayg: yeah so puting a try/except around the close code fixes the issue18:40
*** piyush1 has joined #openstack-swift18:40
claygcreiht: oh good?18:40
creihtyeah dunno? :)18:40
creihtit "fixes" the symptom18:40
creihtbut not sure if it is really the right thing to do18:40
claygi don't think it's acctually a leak18:41
claygthe fact that it happens in close makes me think that gc is just beating the exit handler to it18:41
creihtyeah18:41
claygyeah I think it's a bug in python 2.6.518:41
*** piyush2 has joined #openstack-swift18:42
creihtheh18:42
claygthe 2.6.9 and 2.7 close fucntions do a if "thing" in _handlers: del _handlers["thing"]18:42
claygmy lucid install just does the del18:42
portantezaitcev: I am not sure that is any more correct, but if you'd like, switching the behavior of the existing functional tests to key off of /info first would probably clear this all up18:44
*** piyush1 has quit IRC18:44
zaitcevportante: Do you mean fetching constraints from /info? But why is it so critical anyway?18:45
portanteand I don't think auth_host is enough18:45
creihtclayg: oh just noticed your patch18:45
zaitcevplease tell me more18:45
gholtnotmyname: wth is swift/__init__.py only copyright HP?18:45
*** Guest_ has quit IRC18:45
portanteI was trying not to change the behavior18:45
portantecurrently, tests are skipped if the proper constraints are not provided18:45
claygcreiht: yay finall got it duped!18:46
portanteso instead of skipping them, we run the in-process18:46
redboI'm gonna go put copyrights on all the empty __init__.py files.18:46
portantebut the code today does not gracefully handle a test.conf that does not have auth_host, does it?18:46
*** gyee has quit IRC18:46
zaitcevBut you did change. Look, I have a computer. This laptop. In the master, I run ./.functests, they test my server. In your patch tree, I run ./.functests, they force in-process. It's totally changed!18:46
creihtclayg: when I was playing around, I only needed to add a try/except in the close method of LoggingHandlerWeakRef18:46
notmynamegholt: that happened when an HP employee (ie mordred) replaced the entire contents with the pbr stuff18:46
redboor maybe I'll find any files I modified and add a copyright me.18:47
zaitcevportante: currently the tests are not skipped if constraints are not provided... Well some of them are, but only a small number.18:47
claygcreiht: oh that sounds better!18:47
creiht:)18:47
portantezaitcev: okay, I'll see what I can do18:48
creihtI was just about to submit a patch, and saw you had already thrown something up there18:48
zaitcevportante: but for sure, pulling from /info sounds good, as it will reduce the skipped number even further18:48
gholtnotmyname: Well, aside from the long argued sillyness over copyright notices, I was trying to figure out what to put on this file I'm working in that still has OpenStack Foundation, which I understand is not desirable.18:48
portantezaitcev, creiht: can we get the eventlet change in at least?18:49
creihtnotmyname: can we just remove the copyright declarations at the top of each file?18:49
gholtI figured I'd grab whatever was in swift/__init__.py -- but...18:49
zaitcevportante: sure18:49
creihtportante: what eventlet change?18:49
creihtsorry been a bit distracted with the logging stuff18:49
portantecreiht: the change to swift from eventlet to gevent18:49
portante;)18:50
portantejust kidding18:50
creihtlol18:50
gholtI'll just myself18:50
portantethe change to remove threading and use eventlet in its place18:50
portanteI'll just ... myself?18:50
redboinsert your own verb18:50
gholtHeheh18:50
creihtportante: ahh, yes I'll take a look again when I get back on the regularly scheduled review train18:50
portanteall, so you all want gevent, then?18:50
zaitcevportante: BTW, could you +2 https://review.openstack.org/85909? You reviewed the unified patch once, way before Luis and DATADIR, and it did not change since, so should be 20 seconds +2 for you, right?18:50
claygcreiht: i abandoned mine can you kick something up?  I have an env to test it now18:50
creihtclayg: sure18:51
portantezaitcev: I think I was looking at that midstream when I got pulled off, will get back to it18:51
zaitcevI thought the proper meme was "I accidentially the whole Internet".18:51
claygportante: zaitcev: did in process merge yet?18:53
zaitcevcreiht: "the eventlet" is this https://review.openstack.org/85782 together with chunks() moved into scope. Peter just never gives up18:53
creihtzaitcev: lol18:53
zaitcevclayg: no, no. I was just arguing with portante about it a few minutes ago18:53
zaitcevclayg: there was also some forgotten code in there so it also got -1 on that grounds18:54
claygzaitcev: well bummer18:54
portanteclayg, just doin what I am told18:54
portanteclayg: can you review the threading->eventlet change on which it depends?18:55
zaitcevyeah, baby steps18:55
zaitcevI am suitably ashamed about bikeshedding one little def chunks() while quickly agreeing to the whole eventlet thing, even including the use_hub(), which I find cargo-culted and unnecessary.18:56
*** zhiyan is now known as zhiyan_18:56
pelusegholt: you there?18:57
zaitcevredbo explained how it got into servers. Surely the same logic does not apply to tests. And if you want super reliablity, just use use_hub('selects').18:57
zaitcevoh well18:58
gholtpeluse: Yes, but having trouble keeping up with this channel, so be sure to gholt: prefix stuff for me like you are. :)18:58
claygportante: oh yeah i noticed the depends when I was looking at it last night but forgot to go back to it18:58
*** mkollaro has quit IRC18:58
portanteclayg: thanks18:59
redboI'd like to try switching back to epoll in servers and do a big test, maybe it was some wonky kernel we were using at the time or something.  Maybe I'll trick creiht into doing that, he likes that kind of stuff.18:59
portanteredbo: I'd be game to test it here as well18:59
pelusegholt:  so I have a small request.  patch to add policy support to container sync.  Could you take a gander for 4 things (1) general review, pretty small change (2) Jenkins fails but all of my tests pass and logically, based on my understanding, they should and the third thing I'll hold off on for now :)19:00
pelusegholt: https://review.openstack.org/#/c/86469/19:00
portantecould we get a patch that makes it easily configurable?19:00
zaitcevwe probably could but please don't19:00
pelusegholt:  3 things not 4, man I just can't win w/typing anymore19:00
zaitcevwe're swimming in options as we are19:00
portantezaitcev: we need an option so that it is easy to switch a cluster of machines without pushing new code out19:01
openstackgerritChuck Thier proposed a change to openstack/swift: Fix logging issue when services stop on py26  https://review.openstack.org/8668419:01
portanteif we don't add one, I'll create a branch with one so that we can make this easily deployable19:01
gholtpeluse: Hah, sure thing. I'll put it on my "to do".19:01
creihtclayg: -^19:01
claygsays the guy that wants to make the entire implementation configurable?  I think adding an option it totally reasonable - the best choice probably depends on the platform...19:01
zaitcevportante: well, you have a point...19:01
redboportante: this is the error that happens when it gets in a bad state.  https://github.com/eventlet/eventlet/blob/master/eventlet/hubs/hub.py#L11919:01
portantereallly?19:02
pelusegholt:  thanks!  Will see if I can't digest more of the tests in the meantime19:02
portanteI just ran into that in in-process functional tests19:02
*** jamie_h has quit IRC19:03
portanteI thought that was due to threading, where one thread was running the hub, but a greenlet object got handed to another thread19:03
portantetrampoline away a ... pooh!19:03
portantepoof!19:03
portantesorry19:03
portantedidn't mean to mess up the channel, sorry, cleaning it now quickly19:03
openstackgerritChuck Thier proposed a change to openstack/swift: Fix logging issue when services stop on py26  https://review.openstack.org/8668419:03
* portante does anybody have any clorox?19:03
zaitcevnuke it from orbit. it's the only way to make sure.19:03
creihtI can never seem to submit a patch correctly the first time :/19:04
zaitcevlemme guess - forgot pep819:04
redboyeah, it's supposed to catch two greenthreads trying to simultaneously read or write a socket19:04
creihtzaitcev: heh, somehow added some extra spaces19:04
*** zackf has quit IRC19:05
*** zackf1 has joined #openstack-swift19:05
portanteredbo: so should we have some kind of ssbench scenario set we can hammer on?19:05
portanteor were you just going to run it on a node in some staging environment at rax?19:06
portantewe are building a 3 proxy, 9 storage node cluster here in a lab, and have a simple 3 node swift cluster immediately available19:06
*** Trixboxer has quit IRC19:07
redboI'll probably run some sort of benchmark against it19:07
claygcreiht: can you trick redbo or gholt into merging the logging fix - it works fine19:07
creihtclayg: thanks for taking a look19:08
zaitcevlogging sounds vaguely familiar19:08
redbowell as long as you promise it works19:08
zaitcevgo go gadget https://review.openstack.org/#/q/status:open+project:openstack/swift,n,z19:08
zaitcevwait, what referent = self()19:09
zaitcevyou're taking self and invoking __call__() here? right?19:10
creihtzaitcev: that was already there, so don't ask me :)19:10
zaitcevI need to read how weak refs work, then19:10
zaitcevoh that redbo ninjaed me19:11
creihtyeah I'm not entirely sure, but I think some of that stuff torgomatic just pulled from the py27 tree19:11
creihtnotmyname: it might be worth considering adding https://review.openstack.org/#/c/86684/ to icehouse19:12
notmynameya, I was just about to ask about that19:13
notmynamewhat's the consensus?19:13
notmynamecreiht: clayg: portante: zaitcev: redbo: backport that py26 issue or not?19:13
creihtI'm on the fence19:13
creihtthough leaning slightly on the side of backport19:14
zaitcevnotmyname: I think yes19:14
notmynamecreiht: same here19:14
redboI think it makes it unusable on 2.6.19:14
creihtanyone running a cluster on py26 will see a lot of stack traces in their logs19:14
zaitcevwhat, really? It looked completely safe, which is why +219:14
redbothe problem, not the solution :)19:15
creihtzaitcev: sorry, the above is true without the patch19:15
portantenotmyname: backport, it is just ugly when it starting filling logs19:15
portantenotmyname: which is any RHEL base system, and/or I think CentOS, right?19:16
notmynameportante: right. which is why I'm leaning to the backport19:16
zaitcevRHEL 619:16
zaitcev7 is 2.7 I think19:16
notmynamezaitcev: right19:17
claygit works on 2.6.9 - but not 2.6.5 best I can tell...19:17
claygmaybe you could get ubuntu to backport the fix to python 2.6.5's logging?19:18
claygso is icehouse like out out or just in RC?19:18
creihtI thought we have until Thurs for final cut19:19
notmynameright. we can do another RC19:19
notmynameI'll start turning the wheels on that19:19
*** chandan_kumar has joined #openstack-swift19:19
creihtnotmyname: cool19:19
creihtlol... I was just reminded that today is Thursday :)19:20
*** davidhadas has joined #openstack-swift19:20
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Support to Container Sync  https://review.openstack.org/8646919:23
pelusegholt:  ^ might see why the Jenkins tests were failed but would still appeciate a review and then have a test question after that.  Not super urgent though, thanks19:25
openstackgerritClay Gerrard proposed a change to openstack/swift: Add includes of referenced SAIO bin scripts  https://review.openstack.org/8668119:27
claygportante: ^ the rendering on those literalincludes was messed up cause of :: - i also added test.conf just cause19:32
notmyname"OpenSSL Software Foundation, which funds crypto for most of the Web, set 3-day fundraising record this week: $841.70"19:32
portanteclayg: cool, so that means I can +2 my own patch now, huh? ;)19:34
claygman that's stupid - what good is it for my to have python2.6 installed if the version I have fixes all the bugs in lucid's python that I acctually wanna avoid19:34
claygportante: fuck that it's just docs - we'll both +2 it and make zaitcev merge it since he was whining about it ;)19:34
* clayg hugs zaitcev 19:34
*** krtaylor has quit IRC19:36
zaitcevclayg: at least let me run python setup.py build_sphinx, I want to see what .literalinclude daoes19:37
claygvagrant-swift-all-in-one has a super hot autodoc script that's pretty great for hacking/reviewing doc changes...19:38
claygit watches file changes; builds sphix; uploads them to swift19:38
claygso you just point your web browser at swift and hack away refreshing every so often...19:38
claygs/at swift/at your saio, autodoc spits out a link/19:39
*** csd has quit IRC19:40
zaitcevoh... I used file:///q/zaitcev/hail/swift-tip/doc/build/html/development_saio.html as a peasant I am19:41
notmynamebackport patch https://review.openstack.org/#/c/86689/19:43
*** wayneeseguin has left #openstack-swift19:50
*** mwstorer has quit IRC19:57
openstackgerritgholt proposed a change to openstack/swift: TempURL: Fixed bug with \r or \n in disposition.  https://review.openstack.org/8669119:58
*** krtaylor has joined #openstack-swift20:03
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Support to Container Sync  https://review.openstack.org/8646920:03
clayggholt: lol @ copyright attribution on that change20:10
gholtSsshh. ;)20:11
creihtclayg: I told him he should run his script on all of the files :)20:12
claygi was *hoping* he scripted it!20:12
creihtgholt: you should claim the copyright of the copyright block since you wrote it20:12
claygsince i'm not in the list I'm not going to explicitly complain that I don't want copyright any files, but i wonder if some of those folks would (assuming you didn't already get their explicit permission)20:14
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Documentation  https://review.openstack.org/8582420:17
*** saju_m has quit IRC20:28
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Documentation  https://review.openstack.org/8582420:29
*** saju_m has joined #openstack-swift20:29
*** gyee has joined #openstack-swift20:29
*** ashish_ has joined #openstack-swift20:36
clayggholt: might be nice to open a bug for documenting this "invalid HTTP Content-Disposition header" behavior for weary swift users in the the future that may bump into the problem on older swift deployments...20:41
gholtAh, yeah20:42
gholtAs far as what to do with it, not 100% sure either. urllib quote I think is wrong because it'd make stuff name %xx on people's machines... maybe. I don't actually /know/. :/20:42
claygi would sorta imagine most browsers would figure that one out, somebody should test it :D20:44
*** ashish_ has quit IRC20:44
gholtHey, I'm cool with underscores. :P20:47
claygnice20:48
clayggholt: apparently so is torgomatic!20:48
gholtHeheh20:48
creihtisn't torgomatic supposed to be doing something else other than looking at code? :)20:48
openstackgerritgholt proposed a change to openstack/swift: TempURL: Fixed bug with \r or \n in disposition.  https://review.openstack.org/8669120:49
notmynamefrom old irc channel logs, "copyright notices are up to personal/project discretion. i think projects benefit from adding and maintaining them, but that's just my opinion"20:49
notmynamefrom http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2014-04-03.log20:50
gholtThat's not too old20:50
portantefruit fly years?20:50
creihtnotmyname: so I guess he sets official openstack copyright procedure? :)20:51
creihtI personally think we should just remove them all20:52
notmynamecreiht: oh, so you set official openstack copyright procedure now? ;-)20:52
creihtno20:52
creihtjust expressing my opinion20:53
gholtYeah, I'm not sure who to trust, somebody named fungi or somebody named creiht. :P20:53
creihtlol20:53
notmynamethe only "official" thing I've ever found is https://wiki.openstack.org/wiki/Documentation/Copyright20:54
notmynamewhich doesn't say much20:54
creihtyeah it has always been ambiguous20:55
notmynameI'm pretty sure just having the individual authors listed out is wrong, though :-)20:55
openstackgerritClay Gerrard proposed a change to openstack/swift: Expose container info on deleted containers.  https://review.openstack.org/8670820:55
notmynameI'd be fine with removing them too20:56
creihtnotmyname: I think we need to comission a 2 year study from the board and call it defcopyright21:00
notmynamecreiht: and our deliverable will be the process by which we can determine what the right copyright policy is?21:01
*** csd has joined #openstack-swift21:01
creihtnotmyname: well I'm sure first we would have to define what required sections of code must maintain a copyright21:04
gholtclayg: Finally got the testing done. Url quoting won't work. Well, I mean it'd "work" but you end up with %xx named files downloaded.21:07
openstackgerritPeter Portante proposed a change to openstack/swift: Load constraints from cluster info dictionary  https://review.openstack.org/8671021:08
openstackgerritSamuel Merritt proposed a change to openstack/swift: Check swift.conf MD5 with recon  https://review.openstack.org/8611421:08
*** piyush2 has left #openstack-swift21:08
gholtclayg: http://stackoverflow.com/questions/93551/how-to-encode-the-filename-parameter-of-content-disposition-header-in-http21:10
gholt:)21:10
portantezaitcev, acoles: ^^^21:10
portantefunctional tests no longer rely on direct constraints, only use cluster info of target swift instance for functional tests21:10
portantetorgomatic: ^^^21:10
portantethis is not tied to the in-process stuff21:11
gholtclayg: So mostly we just need to at least return valid html, which it wasn't. Past that, whatever goes for the moment.21:11
gholtclayg: torgomatic: I can always use quote(name, safe='/ +-blah')21:18
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8671421:19
*** peterbusque has quit IRC21:23
*** peterbusque has joined #openstack-swift21:23
*** chandan_kumar has quit IRC21:23
*** peterbusque has quit IRC21:25
torgomaticgholt: yeah, I don't actually have that strong an opinion on quote vs. underscores; either one is way better than invalid HTTP headers21:33
torgomaticquote seems *slightly* better, but... meh21:33
clayggholt: that's weird, when I linked that so post in my inline comment my reading seemed to indicate quote was the way to go - which browser was too dumb to figure out thos %XX in the filename - do you bother to test the filename*=UTF-8'' thing?21:37
*** Guest____ has joined #openstack-swift21:38
gholtsafari, I didn't do the random punctuation thing, no21:38
gholtI'm cool with quote with extra safe chars, seems reasonable21:38
gholtJust figure I'll wait until Monday to commit that in case a strong other opinion comes up.21:39
creihtI think gerrit just likes to troll me21:40
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8672021:44
tdasilvapeluse: I just did a quick pass of your storage policy doc patch and noticed that there's a TODO for adding info to the SAIO instructions. I was wondering if that wouldn't complicate the saio deployment even more. For some reason I see SP as a more advanced feature and SAIO as a way for people new to swift just get started with it...what do you think?21:45
notmynametdasilva: while the SAIO may be used as a "getting started" thing, that's not the intent. the SAIO is for contributors doing dev work21:46
*** krtaylor has quit IRC21:46
tdasilvanotmyname: I see and in part I agree with you, but then I wonder if it would make sense to then create sections as "here's what you need to do" to just try it out and here's the complete instructions to setup a dev. environment...21:48
notmynametdasilva: yes. I think the bare minimum to get a distributed storage system up and running starts to look close to the SAIO, therefore nobody has bothered making a second, seprate doc21:49
zaitcevportante: so, the master cannot func-test my Grizzly cluster anymore, is that how it is?21:50
zaitcevon n/m21:52
zaitcevcurl -v -k https://rhev-a24c-01.mpc.lab.eng.bos.redhat.com/info21:53
claygzaitcev: well just cause info is there doesn't mean all of the constraints are listed... but if you're running and old deployment you can always checkout the functests that go with that version yeah?21:57
zaitcevclayg: I figure I probably could22:01
claygheh22:01
claygnotmyname: so i was wrong, the overhead of keeping changes I need for the reconciler uptodate against feature/ec and pre-storage-policies is going to be too high22:02
notmynameclayg: bah22:02
notmynameclayg: I'm fine with keeping the wiki page updated22:02
notmynameclayg: it's not a scalable solution, but we're only talking about a few contributors and patches for a short about of time22:03
claygnotmyname: I think it's going to end up being better just getting stuff merged to ec and then pull them out to master after that22:03
claygI think the pre-storage-policy topic is a good idea - I think it's just better for changes that are already on master22:04
notmynamechanges already on masteR?22:04
claygyeah changes that are already on feature/ec and could be pulled onto mater - sorry22:04
notmynameok, that makes sense. that's what we talked about (or at least I understood)22:05
claygpart of the problem is it's easier to cherry pick a diff against master over to ec than the other way around22:05
claygnotmyname: well i've been running into a lot of stuff working on the reconciler, but I end up with patches like this that just suck to maintain -> https://review.openstack.org/#/c/86714/22:06
claygit's a mirror of a depdendency chain that's purposed to master - such a chore when I need to go back and fix the tip of the chain on master and then redo the cherry picks to feature/ec so I can rebase the replicator and reconciler changes - ick22:07
notmynamemakes sense22:08
notmynameclayg: so this seems like no change other than the lack of same topic across patches22:09
*** yuanz has joined #openstack-swift22:09
claygnotmyname: well... no I don't think we loose the topic name across patches - that was easy22:10
notmynameclayg: ah, ok22:10
claygnotmyname: i'm just not going to be doing anymore for stuff that I want on feature/ec22:11
notmyname...22:11
notmynameI'm having  hard time following. phone call?22:12
*** yuan has quit IRC22:12
claygso like instead of feature/ec -> mirror-pre-storage-policy-change -> reconciler, it's gunna be feature/ec -> some-change-we'll-eventually-have-to-dig-out-of-feature/ec -> reconciler22:12
claygnah, i gotta sign off for a bit - baseball time - we can talk about it tomorrow22:15
notmynameok22:15
*** saju_m has quit IRC22:20
gholtpeluse: That container sync policy stuff seems reasonable to me. I'm not sure how much I should read into a lot of that just yet. But seems totally fine.22:27
pelusegholt:  thanks.  still trying to figure out the Jenkis failure but a few more shotgun type things to try first.  I can't think of any reason why you can't/shouldn't be able to sync containers with different policies, can you? (not realted to the failure BTW)22:36
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Support to Container Sync  https://review.openstack.org/8646922:38
*** zackf1 has quit IRC22:41
notmynamethis coming sunday (right before the red hat summit), there is going to be a hackathon on a few different storage projects, including swift22:49
notmynameany ideas on good topics for people to tackle?22:50
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Documentation  https://review.openstack.org/8582423:06
*** jergerber has quit IRC23:29
*** yuan has joined #openstack-swift23:44
*** yuanz has quit IRC23:46
*** Guest____ has quit IRC23:47
zaitcevMake them run down the bug list at Launchpad23:47

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