Thursday, 2014-04-17

*** joeljwright has joined #openstack-swift00:03
*** joeljwright has quit IRC00:09
*** shakamunyi has joined #openstack-swift00:20
*** kevinc_ has quit IRC00:21
*** shakamunyi has quit IRC00:21
*** shakamunyi has joined #openstack-swift00:21
*** mmcardle has joined #openstack-swift00:25
*** shakamunyi has quit IRC00:25
*** shakamunyi has joined #openstack-swift00:26
*** tdasilva has left #openstack-swift00:27
*** shakamunyi has quit IRC00:29
*** mmcardle has quit IRC00:30
*** zackf has quit IRC00:31
*** matsuhashi has joined #openstack-swift00:31
openstackgerritA change was merged to openstack/swift: Super small code cleanup in Updater  https://review.openstack.org/8742400:37
*** shri has quit IRC00:44
*** mlipchuk has joined #openstack-swift00:48
*** mwstorer has quit IRC00:59
*** joeljwright has joined #openstack-swift01:05
*** joeljwright has quit IRC01:09
*** mtreinish has quit IRC01:22
*** mtreinish_ has joined #openstack-swift01:22
*** mtreinish_ is now known as mtreinish01:22
*** mmcardle has joined #openstack-swift01:26
*** mmcardle has quit IRC01:31
*** nosnos has joined #openstack-swift01:33
*** saschpe has quit IRC01:37
*** saschpe has joined #openstack-swift01:40
*** joeljwright has joined #openstack-swift02:06
*** joeljwright has quit IRC02:10
*** fifieldt has joined #openstack-swift02:17
*** mmcardle has joined #openstack-swift02:27
*** zhiyan_ is now known as zhiyan02:29
*** mmcardle has quit IRC02:32
openstackgerritA change was merged to openstack/swift: Fix testcase test_print_db_info_metadata()  https://review.openstack.org/8739402:35
*** lnxnut_ has joined #openstack-swift02:51
*** Longgeek_ has joined #openstack-swift02:51
*** lnxnut has quit IRC02:53
*** Longgeek_ has quit IRC02:57
peluse_portante:  saw your note on the in process patch, will look at it some more tomorrow, thanks!03:03
*** joeljwright has joined #openstack-swift03:07
*** Longgeek_ has joined #openstack-swift03:07
*** joeljwright has quit IRC03:12
openstackgerritTakashi Kajinami proposed a change to openstack/swift: Make container PUT and DELETE to allow asynchronous updating to account  https://review.openstack.org/8788203:13
*** matsuhashi has quit IRC03:14
*** gyee has quit IRC03:23
*** nosnos has quit IRC03:27
*** mmcardle has joined #openstack-swift03:28
*** lnxnut_ has quit IRC03:33
portantepeluse_: great03:33
*** mmcardle has quit IRC03:34
portanteI have some comments about 87101 but wanted to try something out first03:34
*** bach has joined #openstack-swift03:39
*** Longgeek_ has quit IRC03:39
*** zhiyan is now known as zhiyan_03:41
*** bach has quit IRC03:48
*** Longgeek_ has joined #openstack-swift03:49
*** bach has joined #openstack-swift03:53
*** Anju has joined #openstack-swift03:56
*** bach_ has joined #openstack-swift03:59
*** bach has quit IRC04:03
*** bach_ has quit IRC04:03
*** bach has joined #openstack-swift04:03
*** zackf has joined #openstack-swift04:05
*** zackf has quit IRC04:06
*** gvernik has joined #openstack-swift04:07
*** praveenkumar has joined #openstack-swift04:07
*** joeljwright has joined #openstack-swift04:08
*** zaitcev has quit IRC04:10
*** joeljwright has quit IRC04:12
*** gvernik has quit IRC04:14
*** d89 has joined #openstack-swift04:14
*** matsuhashi has joined #openstack-swift04:20
*** nosnos has joined #openstack-swift04:23
*** mmcardle has joined #openstack-swift04:30
*** mmcardle has quit IRC04:34
*** chandan_kumar has joined #openstack-swift04:35
*** chandan_kumar has quit IRC05:03
*** chandan_kumar has joined #openstack-swift05:03
*** mmcardle has joined #openstack-swift05:09
*** joeljwright has joined #openstack-swift05:09
*** mmcardle has quit IRC05:13
*** joeljwright has quit IRC05:14
*** mmcardle has joined #openstack-swift05:15
*** mmcardle1 has joined #openstack-swift05:17
*** mmcardle has quit IRC05:17
*** mmcardle1 has quit IRC05:21
*** baojg has joined #openstack-swift05:23
*** baojg has quit IRC05:23
*** mlipchuk has quit IRC05:24
*** baojg has joined #openstack-swift05:24
*** Longgeek_ has quit IRC05:38
*** zhiyan_ is now known as zhiyan05:41
*** baojg_ has joined #openstack-swift05:54
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8671405:54
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8672005:54
openstackgerritClay Gerrard proposed a change to openstack/swift: Expose container info on deleted containers.  https://review.openstack.org/8670805:54
*** Longgeek_ has joined #openstack-swift05:56
*** baojg has quit IRC05:56
*** baojg_ has quit IRC05:57
*** cheri has joined #openstack-swift05:58
*** baojg has joined #openstack-swift05:58
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/8814406:00
*** Longgeek_ has quit IRC06:00
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects in object-updater  https://review.openstack.org/8814506:00
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects in container-replicator  https://review.openstack.org/8814606:00
openstackgerritClay Gerrard proposed a change to openstack/swift: Add object-reconciler daemon  https://review.openstack.org/8590806:00
openstackgerritClay Gerrard proposed a change to openstack/swift: Container Confict on obj update with wrong Storage-Policy-Index  https://review.openstack.org/7973106:00
*** RockKuo_ has joined #openstack-swift06:07
*** RockKuo_Office has joined #openstack-swift06:07
openstackgerritClay Gerrard proposed a change to openstack/swift: Convert POLICIES to list for random.choice  https://review.openstack.org/8815006:08
openstackgerritClay Gerrard proposed a change to openstack/swift: add write_fake_ring to test.unit  https://review.openstack.org/8815106:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend interface on InternalClient  https://review.openstack.org/8815206:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects in object-updater  https://review.openstack.org/8814506:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8671406:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/8814406:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects in container-replicator  https://review.openstack.org/8814606:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Add object-reconciler daemon  https://review.openstack.org/8590806:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Container Confict on obj update with wrong Storage-Policy-Index  https://review.openstack.org/7973106:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8672006:08
openstackgerritClay Gerrard proposed a change to openstack/swift: Expose container info on deleted containers.  https://review.openstack.org/8670806:08
*** baojg has quit IRC06:09
*** baojg has joined #openstack-swift06:09
*** joeljwright has joined #openstack-swift06:10
*** baojg has quit IRC06:11
*** baojg has joined #openstack-swift06:11
*** joeljwright has quit IRC06:14
*** praveenkumar has quit IRC06:15
*** nacim has joined #openstack-swift06:20
openstackgerritA change was merged to openstack/python-swiftclient: Makes use of requests.Session  https://review.openstack.org/7444406:27
*** baojg has quit IRC06:29
*** baojg has joined #openstack-swift06:30
*** cheri has quit IRC06:33
*** praveenkumar has joined #openstack-swift06:33
*** baojg_ has joined #openstack-swift06:39
*** baojg has quit IRC06:42
*** bach has quit IRC06:54
*** joeljwright has joined #openstack-swift06:56
*** nacim has quit IRC07:05
*** ekarlso has quit IRC07:12
*** mattoliverau has joined #openstack-swift07:15
*** hurricanerix has quit IRC07:16
*** dfg has quit IRC07:17
*** dfg has joined #openstack-swift07:17
*** hurricanerix has joined #openstack-swift07:17
*** haomaiw__ has quit IRC07:26
*** haomaiwa_ has joined #openstack-swift07:27
openstackgerritMadhuri Kumari proposed a change to openstack/swift: Bypass committing pending records from .pending file  https://review.openstack.org/8535107:29
*** haomai___ has joined #openstack-swift07:30
*** joeljwright1 has joined #openstack-swift07:31
*** joeljwright1 has quit IRC07:32
*** joeljwright1 has joined #openstack-swift07:32
*** haomaiwa_ has quit IRC07:33
*** joeljwright has quit IRC07:33
*** Longgeek_ has joined #openstack-swift07:41
*** Longgeek_ has quit IRC07:42
*** Longgeek_ has joined #openstack-swift07:43
*** Longgee__ has joined #openstack-swift07:45
*** Longgeek_ has quit IRC07:48
openstackgerritYuan Zhou proposed a change to openstack/swift: Fix delete versioning objects when previous is expired  https://review.openstack.org/8820407:56
openstackgerritYuan Zhou proposed a change to openstack/swift: Fix delete versioning objects when previous is expired  https://review.openstack.org/8820407:59
*** RockKuo_Office has quit IRC08:00
*** _bluev has joined #openstack-swift08:01
_bluevmorninb08:02
_bluevmorning...08:02
*** nacim has joined #openstack-swift08:07
*** haomai___ has quit IRC08:16
*** haomaiwang has joined #openstack-swift08:17
*** ashish_ has joined #openstack-swift08:20
*** mmcardle has joined #openstack-swift08:21
*** foexle has joined #openstack-swift08:24
foexlenotmyname: thx for your hint yesterday. It was helpful :)08:29
*** ashish_ has quit IRC08:32
*** RockKuo_Office has joined #openstack-swift08:39
*** baojg_ has quit IRC08:40
*** fbo_away is now known as fbo08:40
*** baojg has joined #openstack-swift08:40
*** ashish_ has joined #openstack-swift08:44
*** nacim has quit IRC08:48
*** mkollaro has joined #openstack-swift08:52
*** nacim has joined #openstack-swift09:06
*** chandan_kumar has quit IRC09:08
*** ashish_ has quit IRC09:09
*** Longgee__ has quit IRC09:20
*** ashish_ has joined #openstack-swift09:21
*** zhiyan is now known as zhiyan_09:50
*** zhiyan_ is now known as zhiyan09:52
*** zhiyan is now known as zhiyan_09:54
*** baojg_ has joined #openstack-swift10:12
*** madhuri has joined #openstack-swift10:12
*** baojg has quit IRC10:16
*** mlipchuk has joined #openstack-swift10:37
*** mkollaro has quit IRC10:37
*** lnxnut has joined #openstack-swift10:44
*** mkollaro has joined #openstack-swift10:54
*** baojg_ has quit IRC11:01
*** mkollaro has quit IRC11:04
*** RockKuo_Office has quit IRC11:07
*** mlipchuk has quit IRC11:35
*** mlipchuk has joined #openstack-swift11:35
*** praveenkumar has quit IRC11:40
*** mmcardle has quit IRC11:41
*** mmcardle has joined #openstack-swift11:41
*** mlipchuk has quit IRC11:42
*** praveenkumar has joined #openstack-swift11:44
*** ashish_ has quit IRC11:53
*** marcusvrn has joined #openstack-swift12:05
*** Trixboxer has joined #openstack-swift12:16
*** mkollaro has joined #openstack-swift12:33
*** yuanz has quit IRC12:37
*** _bluev has left #openstack-swift12:37
*** zhiyan_ is now known as zhiyan12:38
*** d89 has quit IRC12:39
openstackgerritJulien Danjou proposed a change to openstack/swift: obj/server: add support for If-Match  https://review.openstack.org/8800212:49
*** nosnos has quit IRC12:56
openstackgerritpaul luse proposed a change to openstack/swift: Quick fix to Storage Policy Support for List Endpoints  https://review.openstack.org/8807912:58
*** matsuhashi has quit IRC13:06
*** minnear has quit IRC13:16
*** minnear has joined #openstack-swift13:16
*** matsuhashi has joined #openstack-swift13:17
*** bach has joined #openstack-swift13:20
*** baojg has joined #openstack-swift13:27
*** chandan_kumar has joined #openstack-swift13:36
*** bach has quit IRC13:46
*** bach has joined #openstack-swift14:05
*** changbl has quit IRC14:07
*** bach_ has joined #openstack-swift14:12
*** bach has quit IRC14:14
*** bach_ has quit IRC14:28
*** bach has joined #openstack-swift14:29
*** matsuhashi has quit IRC14:30
*** lpabon has joined #openstack-swift14:30
*** chandan_kumar has quit IRC14:31
*** baojg has quit IRC14:32
*** baojg has joined #openstack-swift14:33
*** bach has quit IRC14:37
*** tanee is now known as tanee-away14:42
*** tanee-away is now known as tanee14:42
*** zematynnad has joined #openstack-swift14:43
*** tanee is now known as tanee-away14:45
*** praveenkumar has quit IRC14:46
*** tanee-away is now known as tanee14:49
*** baojg has quit IRC14:50
*** baojg has joined #openstack-swift14:51
*** baojg has quit IRC14:55
*** chandan_kumar has joined #openstack-swift14:57
*** foexle has quit IRC14:59
notmynamegood morning15:06
zematynnadanybody know if keystone integration was working for swift in grizzly?15:08
notmynamezematynnad: are you seeing a particular error?15:09
*** tanee is now known as tanee-away15:09
zematynnadjust not able to get it to work yet and not sure about the correct values that are supposed to go in proxy-server.conf15:09
zematynnadso was just wondering if others had it working in grizzly at some point15:10
creihtzematynnad: it is how devstack is configured and tested, so I would expect it to work15:14
zematynnadI see15:14
*** kevinc_ has joined #openstack-swift15:16
notmynamezematynnad: yes, keystone has always "worked" for swift, in all versions (with varying degrees of performance)15:16
chmouelzematynnad: yes should work on grizzly and should not be too much different for configuration than the current ones15:16
zematynnadok, I will take a look at devstack for a more concrete example of integrating the two then15:17
zematynnadthamks notmyname. creiht and chmouel15:17
notmynameit's openstack release day!15:21
notmynamepeluse_: around?15:22
peluse_notmyname:  yup15:22
notmynamepeluse_: I'm merging master into ec and getting one unit test failure: https://gist.github.com/notmyname/5743cce010dac01a5e1915:22
peluse_Cool, I'll take a look15:23
notmynamecreiht: portante: chmouel: all 3 of you volunteered to be the oslo liason. shall I pick one of you or do one of you want it more?15:23
creihtlol15:24
*** Anju_ has joined #openstack-swift15:24
notmynamecreiht: actually, I think you'd do a great job at it. you've got a great feel for appropriate library design and dependencies15:26
creihtyeah I'm fine with that15:26
peluse_notmyname:  have to call into a meeting so will be jsut a few but on first look I agree with the assertion that 2 in fact does not equal 3 :)15:26
creihtnot sure the oslo people will be happy about it :)15:26
notmynamepeluse_: :-)15:26
*** chandan_kumar has quit IRC15:27
chmoueleither way i don't mind :)15:27
chmouelimport random;['portante', 'chmouel', 'creith'][random.randrange(0, 2)] ?15:27
creihtlol15:27
creihtrandom.choice(['portante', 'chmouel', 'creiht'])15:27
creiht:)15:27
*** chandan_kumar has joined #openstack-swift15:28
notmynameimport random; print random.choice(['portante', 'chmouel', 'creith'])15:28
notmynameheh. creiht beat me to it :-)15:28
notmynameof course, I don't know who "creith" is15:28
*** bach has joined #openstack-swift15:29
chmouelheh15:29
chmouelwe should decide who own the c namespace :)15:29
peluse_notmyname:  did you have like a zillion conflicts to manually resolve?15:34
notmynamecreiht: how does this work? https://gist.github.com/notmyname/27f434fb9b94f438f7cf where are the passed end parameters coming from in that test case?15:34
notmynamepeluse_: nope. simple ones at then end of account and object tests that check for log formats, and one about the constraints given in /info. that's it (except for this failure)15:35
notmynamecreiht: this is in test_internal_client.py15:36
notmynameI don't see any setUp methods anywhere15:36
peluse_hmm, can you shoot me a note detailing the steps you took, I must be doing something wrong but want to have the same base as obviously so I can fix it15:36
notmynamepeluse_: ok15:37
notmynameFYI, all, if you want to run for the openstack TC, today is the last day to nominate yourself15:37
creihtnotmyname: Most of that mock stuff is magic to me15:38
notmynamecreiht: :-)15:38
notmynamepeluse_: do you get 3 conflicts?15:38
creihtnotmyname: heh, I'm tired of not getting voted in :/15:39
creihtthey don't want anyone that doesn't tote the party line anyways15:39
creihtnotmyname: ok with your previous question, patching like that basically lets you call anything to it and it just returns15:41
creihtthen look lower where it checks with request.assert_called_With15:41
*** chandan_kumar has quit IRC15:42
creihtto check to make sure it got called with the right params15:42
peluse_notmyname:  I got many dozens... made a local branch tracking feature/ec and did git rebase -i remotes/origin/master and picked all15:42
notmynamepeluse_: ah. I got the latest origin/feature/ec and then did `git merge master`. there are only 3 conflicts there15:43
peluse_OK, I'll try that way15:43
creihtyeah everything is set at the beginning of the method15:43
creihtthe patched versions are sent as the parameters (request and urlopen)15:43
notmynamecreiht: is the stack of decorators sent as params...ah ok15:44
creihtyeah I'm not really fond of how it works15:44
creihtbut it works I guess15:44
creihtheh15:44
notmynamethat makes sense to me then (agreed that it's weird)15:44
creihtI still have to go reread the mock docs every time that I use it15:44
*** mwstorer has joined #openstack-swift15:46
*** _80386sx has joined #openstack-swift15:48
*** tanee-away is now known as tanee15:49
*** baojg has joined #openstack-swift15:50
*** tanee is now known as tanee-away15:53
openstackgerritJulien Danjou proposed a change to openstack/swift: obj: allow to use ETags with If-{None-,}Match  https://review.openstack.org/8834615:54
chmouelthat patch is a bit like inception by jd https://review.openstack.org/#/c/86016/915:56
creihtlol15:56
*** gyee has joined #openstack-swift15:56
creihtchmouel: hey can you tell julien that we probably shouldn't support if-none-match with etags yet15:57
creihtas there are some hairy edge cases15:57
*** zematynnad has left #openstack-swift15:57
chmoueli'll ping him to come over15:57
notmynamecreiht: well get out your yak shaving shears ;-)15:58
creihtheh15:58
creihtand I'm not sure the use for if_match on put?15:58
*** zhiyan is now known as zhiyan_15:59
portantecreiht: right behind in on the oslo work! :)15:59
notmynamecreiht: it might make sense, in a general sense, if the etag weren't the md5 sum of the data. (eg etag == some internal id of the data that doesn't mean it's unique). maybe? that may violate teh spec in other ways...16:00
creihtnotmyname: well I'm thinking specifically for swift16:00
notmynamecreiht: of course :-)16:00
*** jd__ has joined #openstack-swift16:01
jd__long time no see #openstack-swift16:01
jd__hi everyone16:01
notmynamecreiht: did I ever tell you about the guy I interviewed who, for the first 30-45 minutes, told me how swift was getting RFC2616 wrong, and he knew this because he'd read over the rfc twice?16:01
notmynamejd__: welcome, stranger :-)16:02
creihtnotmyname: heh16:02
notmynameTechniques on How to Not Interview, 10116:02
creihtI don't think anyone gets rfc2616 right :)16:02
*** chandan_kumar has joined #openstack-swift16:02
notmynametrue :-)16:03
*** tanee-away is now known as tanee16:03
*** tanee is now known as tanee-away16:03
*** bach_ has joined #openstack-swift16:03
notmynameportante: so I'm not sure I understood what you said to creiht about oslo liason. how passionate about it are you?16:04
notmynamejd__: we have some concern about etag + if-non-match edge cases (re your patch)16:04
jd__hehe, yeah you probably know better than me16:05
openstackgerritChmouel Boudjnah proposed a change to openstack/python-swiftclient: Only encode metadata for user customed headers  https://review.openstack.org/8835116:05
openstackgerritChmouel Boudjnah proposed a change to openstack/python-swiftclient: Use quote/unquote from six module for py3  https://review.openstack.org/8728716:05
openstackgerritChmouel Boudjnah proposed a change to openstack/python-swiftclient: Remove validate_headers  https://review.openstack.org/8777216:05
openstackgerritChmouel Boudjnah proposed a change to openstack/python-swiftclient: Fix test_raw_upload test  https://review.openstack.org/8778416:05
creihtjd__: howdy :)16:05
jd__that's mainly just a try to start discussing if that's possible, and if so to help moving this forward since I'd love to have that feature16:05
notmynamejd__: creiht had looked into it. IIRC the hard parts are dealing with the eventual consistency nature of things16:05
* jd__ nods16:05
creihtjd__: howdy :)16:06
jd__I've used GETorHEAD thinking it would use the quorum thingy to handle that for me, but I don't know if that's good enough16:06
openstackgerritChmouel Boudjnah proposed a change to openstack/python-swiftclient: Only encode metadata for user customed headers  https://review.openstack.org/8835116:06
jd__creiht: hey!16:06
*** bach has quit IRC16:06
chmoueloh damn rebase16:06
creihtyeah that will not work, because it is just going to choose one at random16:07
creihtand we would really like to have something like this work without having to do a lot of extra head requests16:07
*** changbl has joined #openstack-swift16:07
creihtI was really close to having it work in the current direction I was going16:08
jd__ah :)16:08
creihtwhat is missing is a reasonable way to update an object that already exists16:08
jd__did you send a patch already? I'd love to help if I can16:08
creihtjd__: I backed the work out when I submitted the if_none_match: * patch16:09
portantenotmyname: I was confused by your email, as I thought you sent the email after the IRC meeting where creiht volunteered, so I answered thinking that perhaps something transpired after the meeting where creiht did not want to do it16:09
creihtjd__: will you be at the summit?16:09
creihtIt is kinda difficult to discuss over irc :)16:09
jd__yes I will16:09
notmynameportante: ah, ok. I actually didn't see creiht volunteered during the meeting. conference wifi cut out in the middle of the meeting and that's what I lost16:10
creihtahh16:10
portanteah16:10
portantethat makes sense now16:10
jd__creiht: well if you can make this work _before_ the summit that'd be even better though :D16:10
creihthaha16:10
creihtyeah that isn't likely16:10
notmynameportante: creiht: so that makes a lot of sense then. if creiht volunteered at the meeting, then that's completely ok with me :-)16:10
creihtthe biggest issue is handling the eventual consistency issues16:10
creihtlike for example, if you PUT v1 and goes on nodes a,b,c16:11
creihtyout PUT v2 and there are failures so it goes on nodes c,d,e16:12
peluse_notmyname:  OK, off my call now.  Yup, 3 conflicts, will take a look at that failuire now16:12
notmynamepeluse_: I've been trying some printf debugging, but still haven't found anything16:13
notmynameyet16:13
creihtif someone does an if-none-match with a v1 etag16:14
creihta and b have the right etag, so don't need the data16:14
creihtc gets overwritten with the uploaded file (with a different timestamp)16:15
*** bach_ has quit IRC16:15
creihtnow if c fails, the v2 in d and e would eventually replicate over16:15
creihtso what it really needed was something like the linux touch command, that would just update the timestamp of a,b16:16
creihtthen things would work reasonably well16:16
jd__sounds too easy to be true :)16:16
creihthehe16:16
creihtyeah so turns out that isn't that easy :)16:17
creihtright now that's handled by default via POST as COPY16:17
creihtso if you do that to a 5GB object, you don't want to wait for the object to copy just to update the ts16:17
*** foexle has joined #openstack-swift16:17
creihtthere are some other oddities16:17
jd__hm, can't we add something like a TOUCH method to the object server?16:18
creihtwell the problem is how to make the change in an atomic way16:18
jd__err right16:18
creihtand at this point, my memory is getting a little fuzzy as to all of the issues with that16:19
creihtI would have to poke at the code again16:19
*** bach has joined #openstack-swift16:20
creihtwe started trying to figure out how to just make the .meta post work right16:21
*** tanee-away is now known as tanee16:21
creihtso we wouldn't have to do post a copy16:21
creihtbut we ran into the same problems we had before16:21
creihtif only content-type wasn't in the container listing :/16:22
notmynamecreiht: can't send an update to the container servers for the metadata? seems like it would be the same container update semantics as an object PUT, just without the body16:23
notmynamecreiht: I'm not doubting at all, just curious about the problems you ran in to16:23
creihtyeah we talked about that but I forgot what the issue ended up being with that16:23
creihthehe16:23
creihtwhen you start digging in the weeds, it is hard to keep all the details16:24
notmynamepeluse_: hmm...it seems that the test case is patching Request to return URLError, not raise it. ...still learning16:25
notmynameI'm not sure yet why this works in master16:25
notmyname(or does it?)16:25
notmynamehmm... cschwede is in git blame for it. make him fix it ;-)16:26
*** bach_ has joined #openstack-swift16:26
cschwedei broke something? let me know :)16:26
creihtjd__: so the easy(ish) answer is, if we can figure out how to get fast POST to work with content-type updates, that would likely lead to being able to support etag if-none-match16:26
notmynamecschwede: I'm working on merging master into the ec branch. but a unit test for internal_client is failing. I'm not sure why yet16:27
cschwedenotmyname: which one?16:27
peluse_notmyname:  not failing for me....16:28
notmynamecschwede: swift@saio:~/swift/test/unit/common$ nosetests -svv test_internal_client.py:TestSimpleClient.test_get_with_retries16:28
notmynamepeluse_: ah, interesting16:28
*** bach has quit IRC16:28
cschwedenotmyname: checking16:28
peluse_notmyname:  want to push your complete branch up and I can compare to mine?16:29
notmynamepeluse_: cschwede: interesting. it's also failing on master for me. /whatsgoingon16:29
*** gyee has quit IRC16:29
peluse_notmyname:  maybe that test doesn't liky you :)16:30
notmynamemaybe a dependency thing. old version of mock. wasn't there something about that recently?16:30
notmynamepeluse_: what version of mock do you have?16:30
cschwedenotmyname: mhh, it’s failing for me on master as well16:31
creihtnotmyname: heh... tests on master run for me16:32
notmynamecreiht: what version of mock do you havE?16:32
creiht1.0.116:34
cschwedenotmyname: if i run .unittests, it also works for me (and if the test would always fail, we should see it on the gate too?)16:34
cschwedemaybe it’s related to nosetest?16:35
cschwedeerr, no makes no sense, .unittest also calls nosetest16:35
notmynamemock 0.8.0 (what's in swift's test-requirements) fails. mock 1.0.1 passes16:35
cschwedenosetests test/unit/common/test_internal_client.py:TestSimpleClient works16:35
peluse_notmyname:  mother mocker16:35
cschwedenosetests test/unit/common/test_internal_client.py:TestSimpleClient.test_get_with_retries doesn’T work16:35
notmynamecschwede: same16:36
notmynamecschwede: wait, with 0.8.0?16:36
peluse_hey, how do I check my mock ver?16:36
cschwedenotmyname: mock 1.0.1 for me16:36
notmynamepython -c 'import mock; print mock.__version__'16:37
notmynamecschwede: confirmed that it still breaks with 0.8.016:37
cschwedepeluse_: python -c "import mock; print mock.__version__"16:37
cschwedetoo slow16:37
peluse_yup 1.0.1 for me too16:37
notmynamein 1.0.0 alph 2 of mock: Any exceptions in an iterable side_effect will be raised instead of returned16:37
notmynamewhich is the problem16:38
notmynameso 0.8.0 can't work16:38
peluse_mockin' A16:38
cschwedeyep, 0.8.0 fails for me too16:38
openstackgerritJohn Dickinson proposed a change to openstack/swift: merged master into ec  https://review.openstack.org/8835916:39
notmynamepeluse_: ^^16:39
*** tanee is now known as tanee-away16:39
notmynamethe change in https://review.openstack.org/#/c/88359/1/test/unit/proxy/test_server.py makes me happy :-)16:39
cschwedenotmyname: so how do we continue on this issue with mock 0.8?16:40
notmynamethanks acoles :-)16:40
*** bach_ has quit IRC16:40
notmynamecschwede: patch test-requirements16:40
notmynamewhile >-1.0.0 would probably work, >=1.0.1 is probably fine16:41
notmynamemeh, the global-requirements have ">=1.0", so we should do that16:41
peluse_notmyname:  identical to mine, check!16:42
*** tanee-away is now known as tanee16:42
cschwedenotmyname: ok, uploading16:42
notmynamecschwede: hang on16:42
cschwedenotmyname: ok16:42
*** tanee is now known as tanee-away16:42
*** tanee-away is now known as tanee16:42
notmynamecschwede: please add a reference in your commit message to http://www.voidspace.org.uk/python/mock/changelog.html#version-1-0-0-alpha-216:43
notmynamecschwede: other than that, thanks!16:43
*** tanee is now known as tanee-away16:43
notmynamecschwede: or specifically to "Any exceptions in an iterable side_effect will be raised instead of returned"16:43
*** tanee-away is now known as tanee16:43
cschwedenotmyname: ok16:43
*** tanee is now known as tanee-away16:43
*** changbl has quit IRC16:44
*** tanee-away is now known as tanee16:44
notmynamepeluse_: ack. merging16:45
*** tanee is now known as tanee-away16:45
*** tanee-away is now known as tanee16:46
notmynameubuntu release and openstack release all in the same day. what an exciting time to be alive!16:47
creihtlol16:47
*** mmcardle has quit IRC16:47
*** tanee is now known as tanee-away16:48
*** tanee-away is now known as tanee16:48
creihtI wonder how long before we have images for the new lts16:48
creihttime to rebuild my saio :)16:48
notmynamecreiht: at rax or for a vm? (for a vm: http://releases.ubuntu.com/trusty/)16:48
creihtfor rax16:49
notmynamehmm..only 22 seeds for the 64-bit server torrent16:50
notmynameoh, there it goes16:50
notmyname329 peers16:50
notmynamevery nice to download at about 4MB/s. already done16:52
creihthttp://www.ubuntu.com/16:54
creihtUbuntu 14.04 LTS, with OpenStack.16:54
creihtthat's kinda interesting16:54
openstackgerritChristian Schwede proposed a change to openstack/swift: Fix test-requirements.txt  https://review.openstack.org/8836316:55
notmynamecschwede: thanks!16:56
cschwedeyou’re welcome!16:56
cschwedenotmyname: and i learned another thing today: also test with the lowest version in (test-)requirements.txt to ensure nothing breaks16:57
cschwedenotmyname: so happy me :)16:57
notmynamecschwede: chmouel: do you have a tl;dr for py3 in swiftclient? with the icehouse release, I was looking at when we should cut another release there16:58
notmynamelooks like there are a few things other than py3 changes that have landed, but the majority are for py316:58
notmynameI'd prefer to have full py3 support rather than "here's a release with new dependencies for something that doesn't work yet"16:59
openstackgerritpaul luse proposed a change to openstack/swift: Bring Object Auditor Coverage To 99%  https://review.openstack.org/8710116:59
Alex_Gaynornotmyname: As far as I can tell, we're like three patches away from having passing tests.16:59
cschwedenotmyname: yes, that would be nice. is there any specific date you have in mind?16:59
notmynameAlex_Gaynor: ah, cool16:59
Alex_Gaynornotmyname: https://review.openstack.org/#/c/87772/ https://review.openstack.org/#/c/87784/ https://review.openstack.org/#/c/87287/ are the most important ones, if you want to do a review :-)17:00
notmynamecschwede: no particular date for swiftclient. if there's stuff that's useful and releasable, then let's release. if not, no need to release17:00
notmynameAlex_Gaynor: thanks17:00
*** shri has joined #openstack-swift17:04
notmynamecreiht: py34 in 14.04: https://news.ycombinator.com/item?id=760459617:04
*** mmcardle has joined #openstack-swift17:05
*** nacim has quit IRC17:09
*** mmcardle has quit IRC17:09
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects in object-updater  https://review.openstack.org/8814517:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Keep status_changed_at up-to-date with status changes.  https://review.openstack.org/8671417:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend direct_client  https://review.openstack.org/8814417:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Enqueue misplaced objects in container-replicator  https://review.openstack.org/8814617:12
openstackgerritClay Gerrard proposed a change to openstack/swift: add write_fake_ring to test.unit  https://review.openstack.org/8815117:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Add object-reconciler daemon  https://review.openstack.org/8590817:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Container Confict on obj update with wrong Storage-Policy-Index  https://review.openstack.org/7973117:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Extend interface on InternalClient  https://review.openstack.org/8815217:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Merge container storage_policy_index values.  https://review.openstack.org/8672017:12
openstackgerritClay Gerrard proposed a change to openstack/swift: Expose container info on deleted containers.  https://review.openstack.org/8670817:12
claygoh sorry, just fixing up some missing imports from my rebase dance yesterday17:12
peluse_phew17:19
*** chandan_kumar has quit IRC17:19
peluse_clayg:  saw the word when its a good time to start looking at these (and in what order)17:19
notmynamepeluse_: google+?17:20
notmynameoh! you finally got it working17:20
peluse_notmyname:  with my ASU account - not sure what Intel has against google+ but my intel.com email won't work there17:25
notmynameheh. maybe google is using AMD or something ;-)17:26
peluse_hah!17:26
peluse_something tells my its the IT security "police"17:27
*** CrackerJackMack has quit IRC17:27
*** foexle has quit IRC17:30
claygpeluse_: the start of the change is some bullshit test fix for some times when I tried to pretend POLICIES is a list17:31
claygpeluse_: after that just follow the "neededby" links17:32
claygpeluse_: https://review.openstack.org/#/c/88150/17:32
claygI think everything up to Merge container storage_policy_index values should be done17:32
*** mlipchuk has joined #openstack-swift17:35
peluse_clayg:  so its ready to start looking at now?17:36
claygyeah i'm done with those for awhile17:36
peluse_claygy:  cool, I'll get some lunch and a few beers and start looking :)17:37
notmynameprerequisites for reviewing all code ;-)17:38
*** CrackerJackMack has joined #openstack-swift17:47
*** devananda has joined #openstack-swift17:47
devanandahi ya'll - we're looking to add swift tempurl support in Ironic17:48
notmynamedevananda: cool!17:48
devanandaand i'm wondering if anyone would have a little time to review the proposal / code17:48
notmynamedevananda: got a link?17:48
devanandanotmyname: https://blueprints.launchpad.net/ironic/+spec/swift-temp-urls17:48
*** fbo is now known as fbo_away17:48
notmynamedevananda: not a lot of detail there. do you have some specific questions about it?17:49
notmynamedevananda: that is, yes, it describes how tempurls work :-)17:49
devanandaheh17:50
devanandamostly whether it looks like we're using them sanely17:50
devanandaduplicating code or using libs where approrpiate17:50
devanandaetc17:50
devananda*that* we want to use tempurls is clear. it's more a question of: is this the right way to use them17:50
notmynameis the "conductor" a glance thing or something in ironic?17:51
devanandaironic-conductor is the service that performs mgmt tasks on bare metal nodes17:51
notmynameok, so the conductor sends a signed URL referencing the swift cluster to the workers on the bare metal nodes?17:51
devanandayep17:52
devanandathat worker (ironic-python-agent) then downloads the image and writes it to disk17:52
notmynamesounds like a great use case17:52
devanandawhereas today, we're passing a keystone auth token17:52
notmynamethere's a couple of things to think about17:52
notmyname(which is why you're here, I think)17:52
notmynameglance? hot content. per user keys.(making a list so I don't forget one)17:53
*** ChanServ sets mode: +v dfg17:54
notmynamedevananda: I don't know enough about glance to know if ironic needs to go through glance to get images or not. it sounds like you don't want that in your use case, but I don't know if it's required in the architecture17:54
notmynamedevananda: ie does glance provide the pass-through for the images, or does glance simply tell the client where to go get stuff?17:55
*** changbl has joined #openstack-swift17:56
devanandanotmyname: so that's an aspect of this I do not fully undersatnd, but, there's a doc string that seems to cover it here17:56
devanandahttps://review.openstack.org/#/c/81391/13/ironic/common/glance_service/v2/image_service.py17:56
devanandanotmyname: and i'm hoping you know more about that than I :)17:57
notmynamenope :-)17:57
devanandaheh17:57
notmynamedevananda: does glance hand bakc the image or a URL to the image?17:57
notmynamehmm...maybe that doesn't matter17:58
devanandain the existing PXE driver, we aer passed a glance image id from Nova, and then actually fetch it from glance17:58
devanandathis is architecturally different17:58
notmynamedevananda: either way, glance is the one generating the tempurl, not ironic17:58
notmynameright?17:58
devanandano17:58
notmynameok17:58
devanandadirect_url = image_info['properties']['direct_url']17:59
notmynameok17:59
devananda... return ('http://{host}/{url}?temp_url_sig={sig}&temp_url_expires='17:59
notmynameok17:59
devanandaso irnoic is taking the glance direct_url, if present, and creating a swift tempurl from it17:59
notmynameglance returns the template, not the actual url?17:59
*** bach has joined #openstack-swift18:00
devanandathere's a bunch of url parsing in that file that seems to be related to the structure of a swift tempurl18:00
devanandaso i think glance is returning a "direct url" but not a tempurl18:00
notmynameis glance filling in the value of {sig}?18:00
devanandalemme pull josh in18:01
chmouelnotmyname: with the last patches i have sent tests pass under py318:01
notmynamechmouel: yay18:01
*** piyush has joined #openstack-swift18:01
*** zaitcev has joined #openstack-swift18:01
*** ChanServ sets mode: +v zaitcev18:01
chmouelnotmyname: when we get those merged we will maybe talk about having the gates running the py3 unitttests18:01
*** JayF has joined #openstack-swift18:01
notmynamechmouel: IIRC it already does, just non-voting right?18:02
*** bach has quit IRC18:02
chmouelnotmyname: that's correct,18:02
*** jroll has joined #openstack-swift18:02
*** JoshNang has joined #openstack-swift18:02
notmynameok. agreed that flippingthe voting switch is good18:02
chmouelfyi: the patches is listed here https://wiki.openstack.org/wiki/Python3/SprintPycon2014#Synchronize_work_on_OpenStack_components18:02
devanandaJoshNang: hi! so in reading through https://review.openstack.org/#/c/81391/13/ironic/common/glance_service/v2/image_service.py I dont actually see anything communicating with swift. should I ?18:03
chmoueland that's the last one of the series https://review.openstack.org/#/c/88351/ which has the py3 unittests passing18:03
JoshNangdevananda: from my understanding of how swift temp urls work, you don't need to contact swift. you have an object that exists, a set of methods, and a shared secret. you use the shared secret to sign a constructed URL with a TTL, and when swift gets a call to that URL, it compares the given signed URL with its shared secret and either allows or 401s the request18:04
notmynameJoshNang: devananda and I are talking about tempurl support in ironic, and glance is mentioned in the ironic design proposal18:04
notmynameJoshNang: devananda: correct18:04
devanandaJoshNang: ah, cool.18:05
notmynameJoshNang: does glance generate the tempurl signature or does ironic?18:05
JoshNangnotmyname: awesome. i'd love feedback on it.18:05
JoshNangironic generates the tempurl as it stands18:05
notmynameJoshNang: devananda: and then ironic requests glance to fetch that tempurl?18:06
JoshNangsort of. it's passed to an agent running elsewhere and then fetched directly from swift.18:06
JoshNangit gets the original image info from glance before hitting the temp url function18:07
notmynameJoshNang: devananda: here's how I would imagine things working:18:07
JoshNangand uses the direct_url in that image info to construct it18:07
jrollJoshNang: well, ironic fetches the tempurl itself, and passes that to the agent18:07
notmyname1) Ironic gets a list of images from glance for the current user18:07
notmyname2) ironic gets, from glance, the tempurl to directly access the image18:08
notmyname3) ironic passes that tempurl to the workers18:08
notmyname4) the workers each directly download the image from swift18:08
notmyname(steps one and two should be combined)18:08
notmynameJoshNang: devananda: does that make sense?18:08
jroll(I'm wrong about that, ignore me) :)18:08
devanandanotmyname: i'd replace (1) with: ironic gets the image metadata from nova for the specific image the user is requesting18:09
JoshNangnotmyname: totally.18:09
*** joeljwright1 has quit IRC18:09
JoshNang^ +118:09
devanandanotmyname: re: 2, it sounds like you are suggesting that ironic not generate the swift tempurls, but leverage glance for that?18:09
JoshNangand as a follow up re: 2, is that currently supported in glance?18:10
notmynamedevananda: yes, but that's also based on my idea of what I think glance is. not necessarily what glance actually does18:10
devanandaheh18:10
notmynameand I don't know what's in metadata that nova has about the image, or why nova does that (again, my understanding of what I think glance is/does)18:10
devanandasounds like we need to ask the glance folks if they provide an API to get swift tempurls18:11
notmynamemy understanding of glance is that it tracks metadata about system images. an indexer of sorts18:11
notmynamedevananda: ok18:11
notmynamedevananda: as to the other things I was thinking of (glad I made a list), I think you--or glance, whoever is generating it--should support per-user keys, not per-system keys.18:12
devanandanotmyname: as an aside, is there any reason why ironic should not generate swift tempurls?18:12
devanandanotmyname: oh, good point, except ironic does not today support users -- one needs to be a cloud admin to talk to the API at all18:13
notmynamedevananda: I have no idea about "should", but ironic certainly "could" generate tempurls (it's all done locally based on a shared secret)18:13
devanandanotmyname: we dont currently track "user" or "project"18:13
notmynamedevananda: ok. then don't build a schema today that locks you in :-). tempurls are per-account (swift account, not user identity), and therefore there are N of them in a given swift cluster18:14
devanandain part because of the security ramifications of allocating a physical machine, that was used by user A, to user B, without being able to guarantee a firmware level wipe18:15
notmynamedevananda: JoshNang: also, FWIW, tempurls actually support 2 secrets to allow for key rotation with no interruption. while not necessary in your first implementation, it's something you can take advantage of18:15
devanandanotmyname: good to know18:15
JoshNangnotmyname: definitely something i've got in mind before going to production with anything :)18:15
*** haomaiwang has quit IRC18:15
*** haomaiwang has joined #openstack-swift18:16
notmynamedevananda: so in this case, the source swift account is a "system-level" account? ie write access would only be granted to a cluster admin18:17
devanandanotmyname: correct18:17
notmynamedevananda: there are 2 reasons to use tempurls. 1) to give time-limited read access without needing to pass credentials around and 2) to avoid auth requests on every ironic worker when fetching the image18:18
devananda(1) is our main reason here, IMO18:18
notmynameok18:18
devanandapassing a full "system level" keystone token over DHCP or TFTP is really not ideal18:19
JoshNangheh18:19
notmyname:-)18:19
notmynamedevananda: so it seems like you have some research to do on how the ironic/glance interaction will work18:19
devanandaJoshNang: can you follow up with the glance team on ^ ?18:20
devanandaJoshNang: aside from that, eerything else is sounding good to me18:20
JoshNangdevananda: certainly. if i can just get it from glance without having to do it myself and mess with direct_url, i'd be quite happy :)18:20
notmynamedevananda: cool. let me shatter those happy feelings with the last thing on my list: hot content :-)18:20
devanandayay! what's that :)18:20
notmynamedevananda: if you are storing and accessing one image, it's going to be stored in swift on 3 spindles (assuming 3 replicas and a <5GB image). therefore, accessing it from 1000 ironic workers all at once could pretty easily saturate those spindles' IO18:22
notmynamenot to mention the network18:22
devanandanotmyname: swift does not use the FS cache, correct?18:22
notmynamedevananda: swift can be configured to use it. but caching large objects probably isn't a good idea, nor too effective in practice18:23
devanandanotmyname: as far as network IO, there is some work (or at least discussion of work) for doing multicast streaming from glance18:23
notmynamethat's cool18:23
notmynamedevananda: there are a couple of things that can be done in a production system to help mitigate this issue. in increasing order of difficulty, here are 4 ideas18:24
notmyname1) don't ask for the image all at once. use some splay function18:24
devanandanotmyname: and I would like the same mode of authentication to be applicable to both, that is, using a tempurl, rather than passing a whole keystone token18:24
notmyname2) use a cache layer like varnish18:24
devanandaJoshNang: so if glance can continue to act as the front-end for the tempurl, that would seem to be beneficial when multicast starts being implemented18:25
notmyname3) deploy different copies of the image and request different ones18:25
devananda3) yuck. hard for deplyers to keep track of that18:26
*** mariusv has joined #openstack-swift18:26
notmyname3a) write a "rand-ifest" feature that works like the current manifests but instead chooses a random one in the manifest18:26
devananda2) seems straight forward and easy to me18:26
notmyname4) write a "seed a torrent" feature in swift18:26
devananda4) yes! JoshNang you guys want to do that, right? ;)18:27
JoshNangdevananda: notmyname 4) yes!18:27
notmynamedevananda: JoshNang: awesome! when can I expect to see the swift patches from you? ;-)18:27
notmynamedevananda: 3a solves the "deployer yuk" part of different copies, but not the issue of storing many copies of the same data and using the extra space (but FWIW, space storage normally isn't the concern with storing a library of common images)18:28
JoshNang:) i'm not sure how we were planning on implementing yet, but i'd love to upstream it when we do (rather than just implementing it as a feature of the agent, for example)18:28
notmynameJoshNang: there are some people here who have looked at it, but AFAIK haven't yet solved it18:29
devanandaJoshNang: rather than the agent fetch-then-seed, if swift provides the seed, the agent ought to be somewhat simpler18:29
devananda*agent code for this ought ...18:29
JoshNangdevananda: agreed. and i like that.18:30
notmynameJoshNang: devananda: but for the realistic solution, it may be adequate to add docs that say "if you are using more than XX nodes, put a cache layer in front of swift for the hot content"18:30
JoshNangnotmyname: definitely18:30
devananda++18:30
devanandaJoshNang: fwiw, that is a drawback of the agent approach. the PXE driver definitely uses the FS local cache on teh conductors to mitigate that18:31
notmynamedevananda: JoshNang: I'd love to see torrent support in swift, but it's a tricky problem, from what I hear. or at least it adds a lot of complexity18:31
notmynameit's in my "someday" bucket of stuff for swift18:31
JayFdevananda: sometimes it's easy to forget that not everyone gets a pre-scaled awesome swift cluster to use :)18:31
zaitcevtorrent (4) is not going to work, because torrent only works when peers particiapte, but in our cases as soon as workers download the images they are going either to move on or to modify the images or discard the images.18:31
JoshNangnotmyname: i'll do some digging into it either after lunch or next week18:32
devanandazaitcev: not true with the agent that is being added to ironic18:32
zaitcevThe randifest (3) is intriguing in its cleverness, but not helping network choke at proxy18:32
JayFfwiw; also, the torrent based approach adds more credence to the desire to have long running agents. They can keep seeding while waiting to be provisioned :)18:32
JoshNangwell, in our case, the workers won't in all cases go directly into booting. they may sit around seeding for some amount of time18:32
devanandazaitcev: it can be long-lived and continue seeding18:32
notmynameJayF: :-) I like your ideas and wish to subscribe to your newsletter18:32
devanandaJayF: yep. this may be the best argument for long-lived agents taht i've seen yet :)18:33
devanandaJayF: adding some logic to ConductorManager to guage how many agents to pre-warm // keep seeding is going to be interesting....18:33
notmynamedevananda: FYI, we (swiftstack) had a customer with this exact problem and the solution was to store multiple copies of the image in swift18:33
notmynameie with different names18:34
devanandanotmyname: sure. but i dont think that's a general solution eg. for folks using this to install their cloud18:34
devananda(ie tripleo)18:34
devananda(3a) would be fine18:34
notmynamedevananda: right. just color commentary and background on a near-term solution18:34
notmynamedevananda: 3a would actually be pretty easy to write18:35
notmynamedevananda: JoshNang: questions answered? anything else?18:36
JoshNangthat works for me! i'll dive into bittorrent when i get a chance and talk to the glance guys after lunch. thanks for your input!!18:37
*** gyee has joined #openstack-swift18:37
*** piyush has left #openstack-swift18:37
notmynameglad to help18:38
* notmyname steps away from the computer for a bit18:38
*** chandan_kumar has joined #openstack-swift18:43
devanandanotmyname: thanks much!18:43
* devananda steps away as well18:43
*** kevinc_ has quit IRC18:49
*** bach has joined #openstack-swift18:50
*** bach has quit IRC18:55
*** pberis has joined #openstack-swift19:00
*** bach has joined #openstack-swift19:08
*** baojg has quit IRC19:27
*** baojg has joined #openstack-swift19:27
*** baojg has quit IRC19:32
*** annegentle has quit IRC19:33
openstackgerritA change was merged to openstack/swift: Fix test-requirements.txt  https://review.openstack.org/8836319:38
*** kevinc_ has joined #openstack-swift19:39
notmynamehmm...so with that test-requirement change, I guess that's pretty strong evidence that the gate isn't actually using swift's specified dependencies19:42
notmynamewell, no, never mind. the gate would have simply installed mock, got the latest one, and used it.19:42
creihtnotmyname: well obviously the gate needs to start testing every combination of every version of library supported ;)19:43
notmynameand interesting set of tests, then, would be to run against the earliest specified version and the lated allowed version19:43
*** bach_ has joined #openstack-swift19:45
*** zhiyan_ is now known as zhiyan19:46
*** bach_ has quit IRC19:47
*** bach_ has joined #openstack-swift19:48
*** bach has quit IRC19:50
*** bach_ has quit IRC19:54
*** bach has joined #openstack-swift19:55
*** ashish_ has joined #openstack-swift19:55
*** annegentle has joined #openstack-swift20:04
shrihi...20:12
shriIs there a list of talks that'll be part of the design summit next month?20:12
swillsso i finally got back to looking at swift, and running the tests on my zfs install...20:17
swillsi'm using 1.13.0... tests are still running, cause my box is slow, but so far only a few errors.20:17
*** chandan_kumar has quit IRC20:22
swillsRan 233 tests in 1088.017s20:29
swillsFAILED (SKIP=2, errors=16)20:29
*** kevinc_ has quit IRC20:31
swillsbox was too busy it seems, some of the failures were just timesouts, rerunning...20:34
*** ashish_ has quit IRC20:42
swillshmm, still some issues20:42
*** occupant has joined #openstack-swift20:42
swillshttp://meatwad.mouf.net/~swills/swift_tests.txt20:42
swillscreiht: ideas on these test failures?20:42
*** bach has quit IRC20:47
*** nacim has joined #openstack-swift20:50
*** kevinc_ has joined #openstack-swift20:51
*** Anju_ has quit IRC20:51
*** lpabon has quit IRC20:52
openstackgerritPete Zaitcev proposed a change to openstack/swift: Plumb insecure flag to functests  https://review.openstack.org/8843821:05
*** fifieldt has quit IRC21:09
zaitcevswills: The only way I know to get to the bottom is to add print(resp.body) in places where these 503 happen. That ought to save the tracebacks. Assuming the failures are repeatable, of course.21:12
swillszaitcev: ok, thanks. i'm thinking they are simply timeouts because things are slow. i am running 6 jails on one box so...21:16
swillsthat is, all the swift instances are on the same box21:16
swillsi did get some tracebacks in logs tho21:17
swillsi can show them if you want21:17
zaitcevswills: Overloaded nodes aren't not going to work, because Swift uses 10s timeouts in backends. Going that low is necessary to switch to a working backend if some nodes go down before client times out, and some clients do 30s.21:18
swillsoh, i'm getting some things timeing out >10 sec...21:18
swillshttp://paste.mouf.net/pastes/nuhhemerjto74v0l8fuirj8j21:18
swillsso perhaps all my nodes are timing out21:19
*** mlipchuk has quit IRC21:20
*** fifieldt has joined #openstack-swift21:21
*** changbl has quit IRC21:21
*** kevinc_ has quit IRC21:24
*** ashish_ has joined #openstack-swift21:29
*** rukawz has joined #openstack-swift21:31
rukawzhi, I just used put_object method from python-swiftclient and I wanted to know what is the best way to retrieve the URI of the object I just created21:32
*** nacim has quit IRC21:33
*** mkollaro1 has joined #openstack-swift21:33
*** mkollaro has quit IRC21:33
*** bach has joined #openstack-swift21:34
rukawzput_object just returns a ETag, I was wondering if I could get the URI used to PUT in the headers21:34
Alex_Gaynorrukawz: it's {account name}/{container name}/{object name} I don't think there's a particular API to retrieve this though21:34
*** ashish_ has quit IRC21:34
rukawzok21:35
rukawzthank you, so I'll have to build myself the URI, is the storage_url available in service endpoints ?21:36
chmouelhas anyone plugged serf into swift for managing ring management push? (serf: http://www.serfdom.io/)21:39
*** mkollaro has joined #openstack-swift21:39
*** erlon has quit IRC21:39
*** mkollaro1 has quit IRC21:39
creihtswills: you would have to look at the logs to see why they returned a 50321:43
creihtoh looks like you already got that sorted out21:44
*** bach has quit IRC21:44
*** pberis has quit IRC21:45
*** kevinc_ has joined #openstack-swift21:46
*** bach has joined #openstack-swift21:48
*** bach_ has joined #openstack-swift21:49
*** marcusvrn has quit IRC21:50
*** bach_ has quit IRC21:51
*** bach has quit IRC21:53
*** bach has joined #openstack-swift21:55
*** foexle has joined #openstack-swift21:56
*** _80386sx has quit IRC21:58
*** mariusv has quit IRC21:58
*** sungju has joined #openstack-swift21:59
*** mariusv has joined #openstack-swift21:59
*** mariusv has quit IRC21:59
*** mariusv has joined #openstack-swift21:59
*** kevinc_ has quit IRC22:01
*** bach has quit IRC22:03
*** bach has joined #openstack-swift22:04
*** rukawz has left #openstack-swift22:04
*** kevinc_ has joined #openstack-swift22:04
zaitcevportante: I was looking everywhere for that sample config22:09
*** bach has quit IRC22:10
openstackgerritPete Zaitcev proposed a change to openstack/swift: Plumb insecure flag to functests  https://review.openstack.org/8843822:14
*** zhiyan is now known as zhiyan_22:29
*** sungju has quit IRC22:48
swillscreiht: yeah, i guess the issue is just that my box is too slow, not that anything is not working?22:53
notmynamechmouel: that looks pretty cool. I haven't used it, but it looks useful22:58
*** mkollaro has quit IRC22:59
*** Trixboxer has quit IRC23:07

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