Friday, 2015-08-21

*** hezhiqiang has joined #openstack-swift00:18
*** kevinc___ has quit IRC00:18
*** hezhiqiang has quit IRC00:24
*** NM has quit IRC00:44
*** lyrrad has quit IRC00:51
*** ccavanna has joined #openstack-swift00:54
*** haigang has joined #openstack-swift01:00
*** ccavanna_ has joined #openstack-swift01:00
*** ccavanna has quit IRC01:01
*** bapalm has quit IRC01:12
*** bapalm has joined #openstack-swift01:14
*** bapalm has quit IRC01:21
*** wbhuber_ has joined #openstack-swift01:33
*** bapalm has joined #openstack-swift01:33
*** bapalm has quit IRC01:38
*** jkugel has joined #openstack-swift01:44
*** bapalm has joined #openstack-swift01:44
*** bapalm has quit IRC01:51
*** haomaiwang has joined #openstack-swift01:55
*** bapalm has joined #openstack-swift01:56
*** bapalm has quit IRC02:03
*** hezhiqiang has joined #openstack-swift02:05
*** haomaiwang has quit IRC02:09
*** haomaiwa_ has joined #openstack-swift02:10
*** bapalm has joined #openstack-swift02:10
*** bapalm has quit IRC02:15
*** jrichli has joined #openstack-swift02:15
*** jkugel has left #openstack-swift02:16
*** bapalm has joined #openstack-swift02:23
*** bapalm has quit IRC02:30
*** bapalm has joined #openstack-swift02:33
*** wbhuber_ has quit IRC02:34
*** bapalm has quit IRC02:40
*** bapalm has joined #openstack-swift02:42
*** haomaiwa_ has quit IRC02:47
openstackgerritPradeep Kumar Singh proposed openstack/swift: Emit warning log in object replicator  https://review.openstack.org/18506102:47
*** haomaiwang has joined #openstack-swift02:47
notmynamegood evening02:49
*** david__ has quit IRC02:51
*** bapalm has quit IRC02:52
*** bapalm has joined #openstack-swift02:55
*** haomaiwang has quit IRC02:58
*** haomaiwang has joined #openstack-swift02:58
*** haomaiwang has quit IRC03:01
*** haomaiwa_ has joined #openstack-swift03:01
*** baojg has joined #openstack-swift03:01
*** bapalm has quit IRC03:04
*** gyee has quit IRC03:09
*** bapalm has joined #openstack-swift03:10
*** baojg has quit IRC03:18
jrichlinotmyname: good evening.  looks like you and Joe had some fun at IDF!03:21
notmyname:-)03:21
notmynamethey were giving away these, and I picked one up https://en.wikipedia.org/wiki/Intel_Galileo03:22
*** sanchitmalhotra has joined #openstack-swift03:23
*** baojg has joined #openstack-swift03:24
jrichlisounds neat.  any specific plans for it yet?03:24
notmynamenope03:25
notmynamefor the time being it will probably sit next to my second raspberry pi (unused)03:25
jrichlilol.  :-)  too busy with 'real' work i guess03:26
notmynameyeah, I'd probably have to stop doing swift stuff on nights and weekends ;-)03:26
jrichlii hear ya!03:26
*** sanchitmalhotra1 has joined #openstack-swift03:31
*** sanchitmalhotra has quit IRC03:33
*** baojg has quit IRC03:47
*** baojg has joined #openstack-swift03:48
*** ppai has joined #openstack-swift03:51
hoping kota_, dmorita i would like to know miyahara-san's irc name.03:58
*** breitz has quit IRC04:10
*** haigang has quit IRC04:27
zaitcevho: I'd poke km and ask...04:30
*** jrichli has quit IRC04:39
*** bapalm has quit IRC04:39
*** bapalm has joined #openstack-swift04:41
*** bapalm has quit IRC04:46
*** bapalm has joined #openstack-swift04:47
*** bapalm has quit IRC04:54
*** baojg has quit IRC04:55
*** NM has joined #openstack-swift04:55
*** bapalm has joined #openstack-swift04:56
*** bapalm has quit IRC05:03
*** bapalm has joined #openstack-swift05:07
*** bapalm has quit IRC05:16
*** bapalm has joined #openstack-swift05:20
*** kairo has quit IRC05:22
*** NM has quit IRC05:23
*** kairo has joined #openstack-swift05:25
*** bapalm has quit IRC05:34
*** bapalm has joined #openstack-swift05:35
*** bapalm has quit IRC05:44
hozaitcev: thanks! do you have any response?05:55
zaitcevho: I didn't ask. I thought you would.05:55
*** bapalm has joined #openstack-swift05:56
hozaitcev: oh, i see. i tried it in japanse, now waiting...06:00
*** zaitcev has quit IRC06:01
*** baojg has joined #openstack-swift06:03
*** baojg has quit IRC06:09
*** bapalm has quit IRC06:15
*** bapalm has joined #openstack-swift06:16
*** bapalm has quit IRC06:20
hokazuhiro around?06:44
*** joeljwright has joined #openstack-swift06:52
*** ChanServ sets mode: +v joeljwright06:52
*** hrou has quit IRC07:00
*** mahatic has joined #openstack-swift07:07
*** baojg has joined #openstack-swift07:08
*** baojg has quit IRC07:08
*** rledisez has joined #openstack-swift07:08
*** geaaru has joined #openstack-swift07:46
*** haomaiwa_ has quit IRC07:49
*** haomaiwang has joined #openstack-swift07:49
*** haomaiwang has quit IRC08:01
*** haomaiwang has joined #openstack-swift08:02
*** joeljwright has quit IRC08:02
*** vinsh has quit IRC08:03
*** jordanP has joined #openstack-swift08:04
*** onovy has quit IRC08:08
*** hezhiqiang has quit IRC08:25
*** jistr has joined #openstack-swift08:30
*** wbhuber_ has joined #openstack-swift08:30
*** wbhuber_ has quit IRC08:34
*** sayali has joined #openstack-swift08:47
*** ho has quit IRC09:00
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-swift09:02
*** sayali has quit IRC09:04
*** sayali has joined #openstack-swift09:08
*** jodah has quit IRC09:10
*** jith_ has joined #openstack-swift09:11
jith_hi all.. is it mandatory to create swiftOperator role.. what is the use of it?09:12
*** aix has joined #openstack-swift09:19
*** baojg has joined #openstack-swift09:27
*** baojg has quit IRC09:27
*** onovy has joined #openstack-swift09:37
*** km has quit IRC09:49
*** haomaiwang has quit IRC10:01
*** izadorozhna has left #openstack-swift10:01
*** haomaiwa_ has joined #openstack-swift10:02
openstackgerritKazuhiro MIYAHARA proposed openstack/swift: Fix dispersion-reports error message  https://review.openstack.org/21369710:05
janonymousjith_ : I think no, Roles could be any name, if used with keystone the entry must be present in its roles on server side also. swiftoperator is just for specification of swift role10:06
jith_janonymous: thanks.. i am using with keystone only...   for swift user i will create the role as admin... may be for ther users like demo i have to assign swiftoperator?? is it like so?10:08
*** aix has quit IRC10:10
*** kei_yama has quit IRC10:16
*** madhuri_ has joined #openstack-swift10:19
* madhuri_ slaps janonymous around a bit with a large fishbot10:19
*** aix has joined #openstack-swift10:22
janonymousjith : yes you can assign swiftoperator role or simply use admin and change that in config of proxy.10:22
janonymousmadhuri_ : Hahaa yes Irc is changed and has some new features :)10:23
madhuri_M sorry was just trying around.. Haha  :)10:25
*** madhuri_ has left #openstack-swift10:25
janonymousOkay.. :)10:26
*** mahatic has quit IRC10:28
jith_janonymous: is it possible for demo user to access swift if he is not admin10:30
*** sanchitmalhotra has joined #openstack-swift10:44
*** sanchitmalhotra1 has quit IRC10:47
*** haigang has joined #openstack-swift10:52
janonymousNo. it has to have admin rights or reseller rights.10:54
janonymousOr the swiftoperator might be configured with admin rights as well for it.10:55
*** haomaiwa_ has quit IRC11:01
*** haomaiwang has joined #openstack-swift11:02
*** mahatic has joined #openstack-swift11:10
*** sanchitmalhotra has quit IRC11:24
jith_janonymous: thanks11:24
jith_but i didnt get fully.. any documentation for this?11:25
jith_default one is swiftoperator?11:25
*** joeljwright has joined #openstack-swift11:28
*** ChanServ sets mode: +v joeljwright11:28
janonymousI think _member is default11:28
janonymousKeystone docs might be helpful for this.11:29
janonymousyou could add multiple roles in proxy.conf also11:29
janonymoushttp://docs.openstack.org/havana/install-guide/install/apt/content/ch_keystone.html11:31
*** SkyRocknRoll has joined #openstack-swift11:37
*** haomaiwang has quit IRC11:42
*** sayali has quit IRC11:44
*** sayali has joined #openstack-swift11:45
*** nadeem has joined #openstack-swift11:48
*** nadeem has quit IRC11:49
*** kairo has quit IRC12:12
*** kairo has joined #openstack-swift12:12
*** ahale has quit IRC12:12
*** petertr7_away is now known as petertr712:12
*** ahale has joined #openstack-swift12:12
kairomorning.12:14
*** alejandrito has joined #openstack-swift12:20
*** vinsh has joined #openstack-swift12:26
*** nakagawamsa has quit IRC12:31
*** abhirc has joined #openstack-swift12:44
*** SkyRocknRoll has quit IRC12:49
*** sayali has quit IRC12:51
*** joeljwright has quit IRC12:57
*** chlong has joined #openstack-swift12:58
*** wbhuber_ has joined #openstack-swift12:58
*** NM has joined #openstack-swift12:59
*** dustins has joined #openstack-swift13:02
*** chlong has quit IRC13:07
*** haigang has quit IRC13:10
*** chlong has joined #openstack-swift13:11
*** peluse_ is now known as peluse13:11
*** ChanServ sets mode: +v peluse13:12
*** vinsh has quit IRC13:12
*** chlong has quit IRC13:15
*** petertr7 is now known as petertr7_away13:21
*** hrou has joined #openstack-swift13:21
*** ppai has quit IRC13:24
*** wbhuber has quit IRC13:25
*** wbhuber_ is now known as wbhuber13:25
*** jkugel has joined #openstack-swift13:25
*** chlong has joined #openstack-swift13:29
*** jrichli has joined #openstack-swift13:33
*** vinsh has joined #openstack-swift13:34
*** vinsh has quit IRC13:35
*** vinsh_ has joined #openstack-swift13:35
*** haigang has joined #openstack-swift13:38
*** ccavanna_ has quit IRC13:39
*** abhirc has quit IRC13:50
*** lcurtis has joined #openstack-swift14:06
*** ccavanna has joined #openstack-swift14:12
*** petertr7_away is now known as petertr714:15
*** dbarman has joined #openstack-swift14:16
*** jlhinson has joined #openstack-swift14:17
*** haigang has quit IRC14:21
*** haomaiwang has joined #openstack-swift14:26
openstackgerritStuart McLaren proposed openstack/python-swiftclient: Add minimal working service token support.  https://review.openstack.org/18264014:31
*** mahatic_ has joined #openstack-swift14:42
*** mahatic has quit IRC14:42
*** zul has quit IRC14:44
*** zul has joined #openstack-swift14:46
*** minwoob has joined #openstack-swift14:58
*** haomaiwang has quit IRC15:01
*** petertr7 is now known as petertr7_away15:02
*** haomaiwang has joined #openstack-swift15:02
*** nadeem has joined #openstack-swift15:04
*** nadeem has quit IRC15:05
*** nadeem has joined #openstack-swift15:05
*** pgbridge has quit IRC15:08
*** haigang has joined #openstack-swift15:18
*** nadeem has quit IRC15:18
*** bapalm has joined #openstack-swift15:21
*** nadeem has joined #openstack-swift15:26
*** nadeem has quit IRC15:26
*** nadeem has joined #openstack-swift15:27
*** petertr7_away is now known as petertr715:28
*** zul has quit IRC15:37
notmynamegood morning15:38
ccavannatorgomatic: Hi. Thanks for the UT code.15:46
ccavannatorgomatic: Can I ask you a question about one function in the change?15:46
*** gyee has joined #openstack-swift15:46
notmynameccavanna: don't ask to ask. just ask :-)15:46
notmyname(also, torgomatic normally isn't around for another hour or so)15:47
ccavannanotmyname: oh, I thought he was up. I'll wait then. Thanks.15:47
ccavannanotmyname: and good morning !15:47
*** jordanP has quit IRC15:47
notmynameit's ok to go ahead and ask. he'll see it when he gets on line, and it may also be answered by someone else who is online now15:47
ccavannaGreat.15:48
ccavannaI got this diff with code changes for UTs from Sam. https://gist.github.com/smerritt/953023d09b0ee1247af315:49
ccavannaIn this method: assertUpdateStats, the first line is sorting the statistics values.15:50
ccavannaI'm not sure why.15:50
ccavannaProbably for the comparison at the end, as long as we pass all the expected values in order.15:52
*** haigang has quit IRC15:55
*** abhirc has joined #openstack-swift15:55
torgomaticccavanna: that's because it doesn't matter what order the updates are in. The ordering of the packets containing object.GET.blahblah and object.policy.2.GET.blahblah is completely irrelevant, so I didn't want the test asserting one came before the other16:00
*** haomaiwang has quit IRC16:01
ccavannatorgomatic: thanks and thanks for the code. I wasn't really sure how you wanted the UTs. Are those changes commited?16:02
albertomdo i have to create an account.builder and container builder for each policy ?16:02
ccavannatorogomatic: or do you want me to check them in with my change?16:02
*** haomaiwang has joined #openstack-swift16:02
torgomaticccavanna: nope; I sent a diff for you to evaluate and take what you liked from it, but that's all I did16:02
ccavannatorgomatic: thank you, it was very helpful.16:03
torgomaticccavanna: you're welcome16:03
*** jistr has quit IRC16:05
torgomaticalbertom: nope, just object rings16:07
*** petertr7 is now known as petertr7_away16:07
*** chsc has joined #openstack-swift16:09
*** zul has joined #openstack-swift16:15
*** rledisez has quit IRC16:25
*** lyrrad has joined #openstack-swift16:25
*** NM has quit IRC16:37
*** arringtp_ has joined #openstack-swift16:56
openstackgerritStuart McLaren proposed openstack/python-swiftclient: Add minimal working service token support.  https://review.openstack.org/18264016:57
*** zul has quit IRC16:59
*** NM has joined #openstack-swift17:00
*** haomaiwang has quit IRC17:01
*** haomaiwa_ has joined #openstack-swift17:02
*** abhirc has quit IRC17:06
openstackgerritDoug Hellmann proposed openstack/python-swiftclient: Update .gitreview for stable/juno  https://review.openstack.org/21571617:16
notmynamepeluse: https://www.youtube.com/watch?v=MnTEpvK7LAE17:17
openstackgerritTim Burke proposed openstack/swift: Add the ability to specify ranges for SLO segments  https://review.openstack.org/21172617:22
*** zul has joined #openstack-swift17:24
*** albertom has quit IRC17:26
notmynamemy thoughts on the hackathon last week https://swiftstack.com/blog/2015/08/21/openstack-swift-hackathon-august2015/17:28
*** albertom has joined #openstack-swift17:29
wbhubernotmyname: reading....17:30
*** abhirc has joined #openstack-swift17:30
wbhuberit looks good.  covered the most pressing topics.  things that can be done pre tokyo and post tokyo.  thx for writing it up.17:33
haypopeluse: hi. any news from tsg for the pyeclib 1.0.8 release?17:36
openstackgerritAlistair Coles proposed openstack/swift: Enable object server to return non-durable data  https://review.openstack.org/21527617:37
hrounotmyname, great summary, thanks for that ! Will share with folks here in the lab, we had written up a summary (better described as an amalgamation of notes) but this is much more concise.17:37
acolespeluse: FYI - still WIP but making progress: patch 21527617:38
patchbotacoles: https://review.openstack.org/#/c/215276/17:38
*** NM has left #openstack-swift17:40
*** janonymous_ has joined #openstack-swift17:41
*** acoles is now known as acoles_17:42
minwoobDoes anyone know of a way off the top of their head, a method to get the path of a fragment with its etag?17:45
hayponotmyname: hi. by the way, can you tell me how i can make progress on my "fix tox -e py34" patch? https://review.openstack.org/#/c/199034/ -- thanks17:45
haypothis patch got a +2 from Pete Zaitcev17:46
openstackgerritCarlos Cavanna proposed openstack/swift: Improving statistics sent to Graphite.  https://review.openstack.org/20265717:46
jrichlinotmyname: great summary!17:48
*** aix has quit IRC17:49
*** geaaru has quit IRC17:56
*** delattec has quit IRC17:58
*** cdelatte has quit IRC17:58
*** zhill has joined #openstack-swift18:00
*** haomaiwa_ has quit IRC18:01
*** mahatic_ has quit IRC18:01
*** haomaiwang has joined #openstack-swift18:02
*** petertr7_away is now known as petertr718:12
openstackgerritCarlos Cavanna proposed openstack/swift: New troubleshooting case in documentation.  https://review.openstack.org/21574418:16
*** albertom has quit IRC18:18
*** dbarman has quit IRC18:19
*** pgbridge has joined #openstack-swift18:22
*** albertom has joined #openstack-swift18:23
*** albertom has quit IRC18:39
*** albertom has joined #openstack-swift18:45
claygheyoh!18:45
*** bwall is now known as deez_nutz18:46
*** deez_nutz is now known as bwall18:46
*** bwall is now known as obama18:47
*** obama is now known as bwall18:48
*** abhirc has quit IRC18:55
*** janonymous_ has quit IRC18:56
minwoobclayg: Are you aware of a method that directly retrieves the fragment's path from its etag?18:58
minwoob(Similar to how you can get the metadata from the fragment body).18:58
claygminwoob: the fragments *path* like /account/container/body ?18:59
clayger... /a/c/o18:59
claygI don't know why i typed body18:59
minwoobRight.18:59
claygminwoob: no, the etag is from the body - that kind of information is all metadata-ish19:00
minwoobNot sure if that will work with shutil.move() but it would get us closer.19:00
minwoobI see.19:00
claygoh you mean like /srv/node/sdb/part/suffix/hash/frag#1.data ?19:00
*** haomaiwang has quit IRC19:01
claygi mean - not that you could get that from the etag :P19:01
*** haomaiwang has joined #openstack-swift19:02
clayghow did you get the etag w/o knowning something else about it - just having the etag is like a weird starting point - it's like a macgyver setup - except even macgyver would be like "wtf am I going to do with an etag?  is there anything else in here?"19:02
minwoobHmm19:02
claygheh19:02
minwoobFrom direct_get(objectpart, object node)19:02
*** haypo has quit IRC19:02
minwoobobject part, object node which in turn was returned by the ring.19:03
claygthat's in some probetest some where right?  it may have even been moved to common or some shiz - i think those tests have some attributes set on them in setup like "self.account, self.container_name, self.object_name" or something19:03
minwoobYeah, exactly.19:03
claygyeah go look at what direct_get does - it must have some state that i can pull from19:03
minwoobI'm pretty sure just etag but it may be returning more than just that.19:05
minwoob(I'm looking at test_reconstructor_revert.py btw).19:05
claygminwoob: ok, yeah that method might just be throwing out TMI - you can get the frag index from the the headers - but it's probably determistic - if you know the acc/cont/o and the node you should be able to figure out the fragment index and the path on disk19:05
minwoob(under tests/probe).19:05
minwoobI see.19:06
claygminwoob: i'm not sure why but it seems move of the new probetests don't reall go all the way down to disk19:09
claygtest_object_failures has some wonky junk19:10
claygI think it might be better to try something with DiskFileManager.yeild_hashes(device, part) - maybe?19:11
claygminwoob: maybe look at how swift-get-nodes works (it'd be good to know ayway) - it might be possible to split up cli.info.print_ring_locations into utils.get_ring_locations and cli.info.display_ring_locations19:15
claygget_ring_locations might return a list of dicts, but instead of *just* the node/device keys (e.g. 'ip', 'port', 'device', etc.) it would also have like 'hash', 'suffix', 'part', 'storage_dir', 'path', 'handoff' (boolean), 'policy'19:17
claygminwoob: or you can just crib what's its doing and roll your own19:17
minwoobclayg: I see. Once it's been -- artificially -- moved to a primary node though, will the reconstructor be able to pick up on the artificially moved fragment?19:21
minwoobBy artificially, I mean by using a utility such as shutil.move() rather than a ring rebalance.19:22
minwoobFrom what I see, shutil.move() is not being used anywhere else in the code.19:23
minwoobThat's what I was planning to go forward with.19:23
claygminwoob: yeah we're definately off in crazy town - you're going to do great tho19:23
claygminwoob: the reconstructor is going to deal with whatever he finds in the directory - it doesn't really know how it got there - so for that part shutil.move is going to be fine19:24
claygminwoob: there's some chance (if the reconstructor has already run) that it won't find anything in that directory tho because it doesn't know to go looking for it19:24
claygif it seems like at some point some background process isn't noticing that you changed something out from underneath it you may have to call invalidate_hash (or just rm hashes.pkl)19:25
claygor maybe just fork lift the whole part - that'd probably be better than surgery19:26
clayglike fail a couple of primaries, then lift the parts off the handoffs - but drop them on the wrong nodes (swapped) - the scenario we're acctually trying to cover for is a node that took a handoff suddenly becoming a primary and finding he's holding the wrong frag19:27
pelusenotmyname, cool thanks19:27
claygso moving handoff frags onto the wrong primary seems like a pretty good proxy I think?19:27
claygpeluse: !!!19:27
pelusemr clayg!19:28
clayghow was the big presentation conference thingy?!19:28
claygpeluse: did you sell a bunch of cpus?19:28
pelusegreat prese O think, weak attendance :(19:28
pelusewe had a crappy timeslot, most of the tech sessions were very light on the last day just before lunch.  oh well19:28
peluseclayg, so hey I'm spending most of today getting the cluster ready for next week's fun.  I saw your etag buckets comments/updates - are you pushing more stuff or want me to run with what's up there this weekend (try to address thingss) or what are ya thinkin'?19:29
claygpeluse: yes - next week is key19:30
minwoobclayg: I like the idea of moving the part around, rather than the fragment -- can only have one fragment per object, on a part, anyway.19:30
claygpeluse: you should work on getting ready for that19:31
claygpeluse: but we neede etag buckets!19:31
clayghrm...19:31
claygminwoob: well - heh - unless your a primary :D19:31
*** andrey-mp has joined #openstack-swift19:34
peluseclayg, OK so keep me posted on etag buckets.  for now I'll use master for the test cluster19:34
claygpeluse: i guess I'm thinking the bucket response and spawn extra requests is exactly the right thing to do - so it's all tactical now19:34
*** tsg has joined #openstack-swift19:35
claygpeluse: I thinking handling mixed 206/416 in ranged responses is about the same as handling mixed etags and they should both work the same19:35
claygpeluse: I think we should probably group by timestamp instead of etag19:35
peluseclayg, ahhh....19:35
claygpeluse: I think there could be more failures to come out of additional testing19:35
minwoobRight.19:35
peluseclayg, ain't that the truth always?19:36
claygpeluse: I think acoles made a comment about spawning as many extra requests as needed to service the difference of min-gets and max-bucket was spot on - and I snuck that in my follow up19:36
clayg... so ...19:37
claygwell that's it really19:37
claygi don't know what to do now except keep working on it19:37
peluseclayg, cool19:37
peluseclayg, thanks19:37
andrey-mpHi, Who is responsible for swift3 plugin? I sent quiestions to mailing list and to all people from swift3-core... but no answer...19:38
claygi have some bandwidth today - might be able to move it forward - i could start squashing stuff over your change; or doing more diffs and/or dependent patches - i think there's other core's around - we might could try to merge something today if that would be helpful?19:38
claygandrey-mp: try timburke or kota_ (where is kota_ ?)19:38
peluseclayg, yes that would be HUGE19:38
claygctennis: are you guys going to be able to deploy master next week?19:39
notmynameandrey-mp: I'm not exactly sure what your proposed change means19:39
ctennisclayg: he plan is to just put git master on the machines and point the existing directories to them19:39
andrey-mpnotmyname: I can describe it :)19:40
notmynameandrey-mp: what does it mean to "...add to swift3 project pipeline tempest job."19:40
andrey-mpswift3 doesn't have any functional tests in gating19:40
andrey-mpi propose to add tempest job to swift3 gating to check functionality in real cloud19:41
claygandrey-mp: do other ec2 compatibility api shims *gate* changes to openstack?19:41
claygor you want to gate changes to swift3?  against some tempest functional tests?19:42
andrey-mpclayg: i don't fully understand your phrase... but i try to answer - ec2 has three functional gate jobs19:42
andrey-mpi want to gate changes with swift3 against some tempest tests. yes :)19:43
andrey-mptempest.thirdparty.boto - these tests have s3 requests19:44
claygyeah ok - kota would probably be down for that - sounds reasonable to me <- timburke19:44
claygandrey-mp: do they pass currently for you when you run them localy on your setup?19:44
timburkeandrey-mp: do we already know that current swift3 has sufficient compatibility with the S3 api to pass? i know there are still some blind spots...19:44
andrey-mpclayg: yes. We have gate job for ec2 that enables swift3 plugin and runs tempest and our ec2 functional tests.19:45
andrey-mptimburke: all tests that we have are passed against cloud with swift3 enabled19:46
*** bkopilov has quit IRC19:47
timburkeandrey-mp: then, yeah, i'm all for it! i know we were talking about doing something similar for the swift gate at the hackathon. (non-voting, though; swift3 shouldn't dictate what can land in swift)19:47
*** bkopilov has joined #openstack-swift19:47
claygnotmyname: ^ sounds good to me, does andrey-mp have to do anything special to work with infra to get the non-voting job setup?19:47
*** alejandrito has quit IRC19:48
claygtimburke: but if the tests are reliable and provide useful failures it'd be cool to have them gate changes to swift3 (start non-voting obviously)19:48
andrey-mpyeah, I'll do it :) I made same job (non-voting) for our ec2 project - so it will be simple19:48
notmynamewhat is the "ec2 project" you're talking about?19:48
timburkeclayg: *nod*19:49
andrey-mpthis is - https://github.com/stackforge/ec2-api19:49
claygis it holiday in Japan?  I'm guessing either kota didn't see the message or he's OOO19:49
notmynameandrey-mp: and are you wanting to add these checks to swift3 or to swift?19:49
andrey-mpis a standalone ec2 api to openstack19:49
andrey-mpnotmyname: swift319:49
claygnotmyname: he said swift319:49
notmynameclayg: it's saturday in japan. also 4:50 am19:49
claygnotmyname: ah!19:49
claygandrey-mp: the thing about "no one responded" with a global community is - you need to give it a couple three business days :P19:51
claygIRC is great tho, good call jumping in here :D19:51
andrey-mpclayg: ok :) I'm worrying because my previous mail to mailing list has no response too, but I sent it four days ago :)19:52
claygandrey-mp: heh, fair enough - swift3+keystone it probably like a subgroup of a subgroup - good for you!19:56
claygandrey-mp: is this like a s3 http server that just writes stright to a filesystem -> https://github.com/stackforge/ec2-api/blob/master/ec2api/s3/s3server.py19:57
andrey-mpclayg: yes. this is improved copy-paste from nova. nova team deprecated ec2/s3 in nova project19:59
andrey-mpclayg: but this implementation mostly for testing not for real cloud. also it doesn't have authentication at all20:00
*** haomaiwang has quit IRC20:01
*** 7JTAAIXB0 has joined #openstack-swift20:02
claygi keep laughing at "real cloud" - like ... idk, i'm not a meteorologist :)20:05
*** petertr7 is now known as petertr7_away20:05
minwooblol20:05
andrey-mp:)20:06
claygyay Friday!20:07
andrey-mpI dislike a bit unit tests because it works with ephemeral layers and I call it fake cloud :)20:07
claygeven better!  :)20:08
andrey-mpso, something like this - https://review.openstack.org/#/c/215766/20:13
claygandrey-mp: I honstly have no idea ^ notmyname timburke20:14
*** marcusvrn_ has quit IRC20:15
albertomhi20:17
notmynamehi20:17
albertomhow can i create a container with policy-1 ?20:17
albertomswift -V3 post containername     <==== this creates a container with the default policy20:18
claygalbertom: -H 'x-container-policy: <policy-name-from-/info>'20:18
clayg^ works with curl or swift20:18
albertomswift: error: no such option: -H20:19
claygwhoa - `sudo pip install --upgrade python-swiftclient` maybe?20:20
albertomswift 2.3.120:20
albertomI have that one20:20
claygalbertom: mine says python-swiftclient 2.4.1.dev2120:21
clayg  --header <header>     Set request headers. This option may be repeated.20:21
clayg                        Example -H "content-type:text/plain"20:21
claygalbertom: oh is that the version of *swift* or python-swiftclient?  you did `swift --version`20:21
notmynameit's swift client20:21
albertomI did swift --version20:21
albertomon ubuntu20:21
notmynamealbertom: it hink you put the -H in the wrong place20:22
albertomalso, it would be nice if horizon could let me choose the policy20:22
*** tsg has quit IRC20:24
albertomoh right20:25
albertom-H after post20:25
notmynameyeah. just confirmed locally20:25
*** bkopilov has quit IRC20:27
albertomswift -V3 post -H 'X-Storage-Policy: silver' silver20:27
albertomyeah that works20:28
albertomthanks!20:28
albertomdo youy know if there is a patch already in horizon ?20:28
andrey-mpthanks all!20:28
*** tsg has joined #openstack-swift20:30
notmynamealbertom: nope. I don't know20:34
*** albertom has quit IRC20:34
*** bkopilov has joined #openstack-swift20:35
*** andrey-mp has quit IRC20:35
*** bkopilov has quit IRC20:41
*** albertom has joined #openstack-swift20:41
*** tsg has quit IRC20:49
*** bkopilov has joined #openstack-swift20:53
*** jrichli has quit IRC20:55
*** 7JTAAIXB0 has quit IRC21:01
*** lyrrad_ has joined #openstack-swift21:01
*** haomaiwang has joined #openstack-swift21:01
*** lyrrad has quit IRC21:03
*** lyrrad_ is now known as lyrrad21:03
*** pberis has joined #openstack-swift21:10
*** dustins has quit IRC21:17
*** jlhinson has quit IRC21:18
openstackgerritMatt Riedemann proposed openstack/python-swiftclient: Update from global requirements  https://review.openstack.org/21578621:22
peluseclayg, you still there?21:26
notmynamepeluse: he's not been at his desk in a while21:42
pelusenotmyname, OK thanks.  Have a cont reconciler question that's no big deal - can wait21:45
*** abhirc has joined #openstack-swift21:45
*** ccavanna has quit IRC21:48
*** ccavanna has joined #openstack-swift21:48
*** zaitcev has joined #openstack-swift21:50
*** ChanServ sets mode: +v zaitcev21:50
*** ccavanna_ has joined #openstack-swift21:50
*** ccavanna has quit IRC21:50
*** sungju has joined #openstack-swift21:53
*** sungju has quit IRC21:53
*** hrou has quit IRC21:54
*** ccavanna_ has quit IRC21:54
*** zhill has quit IRC21:56
*** haomaiwang has quit IRC22:01
*** haomaiwang has joined #openstack-swift22:02
*** pberis has quit IRC22:03
*** tsg has joined #openstack-swift22:05
*** chsc has quit IRC22:13
*** jkugel has left #openstack-swift22:14
*** minwoob has quit IRC22:30
*** tsg has quit IRC22:46
*** alejandrito has joined #openstack-swift22:46
*** lyrrad has quit IRC22:49
*** lyrrad has joined #openstack-swift22:51
mattoliverauBack in Oz \o/22:53
notmynameyay22:53
*** haomaiwang has quit IRC23:01
*** haomaiwang has joined #openstack-swift23:02
claygpeluse: nope23:04
*** zhill has joined #openstack-swift23:08
*** abhirc has quit IRC23:12
*** tsg has joined #openstack-swift23:13
peluse:)23:16
peluseoutta here... later23:16
*** abhirc has joined #openstack-swift23:24
*** lcurtis has quit IRC23:24
*** nadeem has quit IRC23:37
openstackgerritTony Breeds proposed openstack/python-swiftclient: Update *requirements.txt from global-requirements  https://review.openstack.org/21583723:37
*** tsg has quit IRC23:39
timburketdasilva: so i've been playing around with the idea of having delete markers in the versions (rather than versioned) container. how would we distinguish between PUT -> DELETE-with-marker (ie, original and marker in versions, nothing in versioned) and PUT -> DELETE-with-marker -> PUT (original and marker in versions, updated copy in versioned)?23:45
timburkewe now need to know two things at once: is there an object in the versioned container? and is the version that i'm trying to restore a delete marker? we can get either one fairly easily (HEAD the object in the versioned container or peek at the COPY headers), but i think both at once will be hard.23:45
timburkeif we HEAD before trying to do any COPYs, that info may be stale by the time we get a successful COPY. notmyname suggested If-(None-)Match: *, but those are no good; for a COPY, If-None-Match: * applies to the source (as well as the dest?), while If-Match: * isn't respected on PUTs (so it's meaningless for COPYs).23:45
timburkeeven if they worked, though, we'd be left needing to make two requests in some cases, which opens this up to race conditions even worse than it already is23:45
*** chlong has quit IRC23:52

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