Wednesday, 2014-09-10

*** aswadr has joined #openstack-swift00:10
*** tkay has quit IRC00:13
*** kyles_ne has joined #openstack-swift00:16
*** kyles_ne has quit IRC00:17
*** gyee is now known as zuul00:18
*** zuul is now known as gyee00:18
*** dmorita has joined #openstack-swift00:29
*** yuan has joined #openstack-swift00:33
*** shri has quit IRC00:51
*** gyee has quit IRC00:55
*** dabbler has joined #openstack-swift01:04
*** IgnacioCorderi has quit IRC01:04
dabblerhello people.. I am a noob at swift..01:04
*** mwstorer has quit IRC01:05
dabblerwe are writing a library that uses curl commands to upload segmented objects to swift..01:05
dabbleris there a way to track the progress01:05
dabblerof upload..01:05
*** echevemaster has quit IRC01:06
dabblerI have seen this https://bugs.launchpad.net/python-swiftclient/+bug/1231509 but that does seem to be appropriate for what we would want..01:07
dabbler*does not01:10
openstackgerritA change was merged to openstack/swift: Too many if clauses in the _clean_incoming_headers and the _clean_outgoing_headers routines of the tempurl module  https://review.openstack.org/11978201:18
*** thurloat has quit IRC01:23
zaitcevIf you use _curl commands_, then this question hardly has anything to do with swift. You just need to use curl's progress counter or -# for progress bar. If you want a summary, then your master script could do something like counting the segments.01:27
openstackgerritMatthew Oliver proposed a change to openstack/swift: Treat 404s as 204 on object delete in proxy  https://review.openstack.org/11412001:27
zaitcevBut I have a feeling that I do not understand what the difficulty is here.01:27
*** kota_ has joined #openstack-swift01:32
*** cpen has quit IRC01:32
*** dmsimard_away is now known as dmsimard01:33
*** zaitcev has quit IRC01:34
dabbler@zaitcev the upload job is kicked off and some other routines/jobs are invoked and the upload job continues in the background..01:34
dabbleris there a way to get query the object storage and get the amt of bytes copied?01:35
dabblerI can get the total container bytes from the manifest (if it is written before assembly of chunks) but that would be contentious if two or more objects are being written to the same container01:36
*** dmsimard is now known as dmsimard_away01:39
*** thurloat has joined #openstack-swift01:42
*** kota_ has quit IRC01:44
*** IgnacioCorderi has joined #openstack-swift01:46
*** rmcall has quit IRC01:47
*** mattoliverau has quit IRC01:49
*** mattoliverau has joined #openstack-swift01:50
openstackgerritMatthew Oliver proposed a change to openstack/swift: Treat 404s as 204 on object delete in proxy  https://review.openstack.org/11412001:53
*** nosnos has joined #openstack-swift01:54
*** IgnacioCorderi has quit IRC01:55
*** fifieldt_ is now known as fifieldt02:03
*** haomaiw__ has quit IRC02:14
*** haomaiwang has joined #openstack-swift02:15
*** NM has joined #openstack-swift02:19
*** NM has quit IRC02:29
*** haomaiwang has quit IRC02:30
*** haomaiw__ has joined #openstack-swift02:30
*** haomaiwa_ has joined #openstack-swift02:35
*** haomaiwa_ has quit IRC02:35
*** haomaiw__ has quit IRC02:36
*** haomaiwang has joined #openstack-swift02:36
*** NM has joined #openstack-swift02:37
*** haomai___ has joined #openstack-swift02:42
*** dabbler has quit IRC02:42
*** NM has quit IRC02:43
*** haomaiwang has quit IRC02:45
*** dabbler has joined #openstack-swift03:07
*** IgnacioCorderi has joined #openstack-swift03:11
*** IgnacioCorderi has quit IRC03:14
*** judd7 has quit IRC03:15
*** dabbler has left #openstack-swift03:28
*** haomai___ has quit IRC03:35
*** haomaiwang has joined #openstack-swift03:35
*** haomaiw__ has joined #openstack-swift03:47
*** haomaiwang has quit IRC03:50
*** ppai has joined #openstack-swift04:27
notmynameI just reread over http://www.hds.com/assets/pdf/distributed-object-store-principles-of-operation.pdf. Such a great overview of object storage04:30
*** rmcall has joined #openstack-swift04:31
*** IgnacioCorderi has joined #openstack-swift04:36
*** IgnacioCorderi has quit IRC04:40
*** mahatic has quit IRC05:19
*** Yorkfly has quit IRC05:19
mattoliverauI'll add it to my reading list then :)05:20
notmynamemattoliverau: that paper is more than 4 years old, but still is a fantastic description of challenges and principles of distributed object storage05:39
mattoliveraunotmyname: more background is always useful :) Now no more procrastinating and go to bed :P05:41
notmynameheh. I'm looking over some reporter's questions about file vs object storage trying to come up with both correct but succinct answers05:42
*** Anju has joined #openstack-swift05:45
*** k4n0 has joined #openstack-swift05:45
*** nshaikh has joined #openstack-swift05:45
*** kopparam has joined #openstack-swift06:00
*** kopparam has quit IRC06:00
*** kopparam has joined #openstack-swift06:01
*** kopparam has quit IRC06:06
*** kopparam has joined #openstack-swift06:09
*** bkopilov has quit IRC06:14
*** bkopilov has joined #openstack-swift06:15
*** bkopilov_wfh has joined #openstack-swift06:15
*** gius has joined #openstack-swift06:34
*** Anju has quit IRC06:37
*** IgnacioCorderi has joined #openstack-swift06:37
*** bkopilov has joined #openstack-swift06:38
giusacoles: Hi! Are you there?06:44
*** rmcall has quit IRC06:45
*** gius has left #openstack-swift06:46
*** pino has joined #openstack-swift06:47
*** AnjuT has joined #openstack-swift06:51
pinoDear all, Alice and Bob are two users of the same tenant (called TENANT). I would like that each of them see only the Container that she/he will create. How can I do it?06:51
pinoI know that it is necessary to use the headers X-Container-Read and X-Container-Write, but I don't know how to use these headers.06:53
pinoIn other words, what is the cURL command should I use?06:54
*** AnjuT has quit IRC06:58
*** k4n0 has quit IRC07:07
mattoliverauk, I'm calling it a night, see you all on the morrow.07:11
notmynamemattoliverau: you're not allowed to call it a night before me! ;-)07:19
*** k4n0 has joined #openstack-swift07:21
mattoliverau notmyname: You still up!07:22
notmyname:-)07:22
notmynamethis isn't good for the 7:30 phone call I have tomorrow morning07:22
notmynamebut on the other hand, I think this has been a pretty productive evening07:22
*** geaaru has joined #openstack-swift07:22
mattoliverauLol that's good.. Tho if we have a grumpy tired ptl tomorrow we'll know why :p07:23
mattoliverauI'm taking my parents out for dinner (its 530pm, so the stereotype of early dinners for oldies is universal) :p07:25
openstackgerritChristian Schwede proposed a change to openstack/swift: Fix Keystone middleware example in the docs  https://review.openstack.org/12032707:26
*** IgnacioCorderi has quit IRC07:27
openstackgerritOpenStack Proposal Bot proposed a change to openstack/swift: Updated from global requirements  https://review.openstack.org/8873607:32
*** vr1 has joined #openstack-swift07:34
*** bvandenh has joined #openstack-swift07:57
openstackgerritLin Yang proposed a change to openstack/swift: Remove unnecessary comma  https://review.openstack.org/12033708:15
*** vr1 has quit IRC08:24
*** vr1 has joined #openstack-swift08:25
*** vr2 has joined #openstack-swift08:54
*** vr1 has quit IRC08:54
*** pino has quit IRC08:59
*** nosnos has quit IRC09:41
*** nosnos has joined #openstack-swift09:42
*** aix has quit IRC09:47
*** nosnos has quit IRC09:47
*** mahatic has joined #openstack-swift09:54
*** vr2 has quit IRC09:55
*** vr1 has joined #openstack-swift09:55
*** fbo has joined #openstack-swift09:56
*** bvandenh has quit IRC10:07
*** aix has joined #openstack-swift10:21
*** mkollaro has joined #openstack-swift10:24
*** homegrown has joined #openstack-swift10:29
*** haomaiw__ has quit IRC10:34
*** 18VAAWTEG has joined #openstack-swift10:34
*** NM has joined #openstack-swift10:35
*** NM has quit IRC10:37
*** kopparam has quit IRC10:40
*** kopparam has joined #openstack-swift10:40
*** pino has joined #openstack-swift10:41
*** 18VAAWTEG has quit IRC10:53
*** haomaiwang has joined #openstack-swift10:53
*** bvandenh has joined #openstack-swift10:58
*** miqui has quit IRC11:00
*** dmorita has quit IRC11:00
*** mahatic has quit IRC11:04
*** Manifesto has quit IRC11:05
*** ppai has quit IRC11:05
*** mahatic has joined #openstack-swift11:06
*** jamiehannaford has joined #openstack-swift11:17
*** ppai has joined #openstack-swift11:19
*** anticw has quit IRC11:31
*** dmsimard_away is now known as dmsimard11:32
*** Manifesto has joined #openstack-swift11:32
*** Manifesto has quit IRC11:35
*** ekarlso- has quit IRC11:37
*** ekarlso- has joined #openstack-swift11:37
*** kopparam has quit IRC11:39
*** kopparam has joined #openstack-swift11:40
*** kopparam has quit IRC11:44
*** mahatic has quit IRC11:47
*** marcusvrn has joined #openstack-swift11:53
*** mahatic has joined #openstack-swift12:03
*** vr1 has quit IRC12:04
*** vr1 has joined #openstack-swift12:04
pinoDear all. I have a tenant (CONCEPT) with three users named "orch","user1","user2". Only user "orch" has an operator_roles in the proxy-server.conf. I would like that  "user1" and "user2" can create own container and thyy can only read a specific container created by "orch". Is it possible?12:08
pino*they12:08
pinoI rewrite in a better fashion:  I have a tenant (CONCEPT) with three users named "orch","user1","user2". Only user "orch" has an operator_roles in the proxy-server.conf.12:10
pinoI would like that  "user1" and "user2" can create/read own container and they can only read a specific container created by "orch". Is it possible?12:10
*** kopparam has joined #openstack-swift12:10
*** kopparam has quit IRC12:17
*** anticw has joined #openstack-swift12:20
acolespino: assuming you are using keystone auth, only a user with an operator_role can create a container.12:22
acolesso in your example only orch can create containers.12:22
acolesorch can grant read access to a specific container to other users using X-Container-Read header12:23
*** miqui has joined #openstack-swift12:29
pinoacoles: I am using Keystone12:30
pinoSo, I suppose that if "user1" and "user2" have operator_role, they can read and write all the Containers into the Account12:31
acolespino: yes12:34
pinoWell. In this scenario can "orch" restrict the access to own Container? I would like that "user1" and "user2" can only read a specific container created by "orch"12:37
*** tab_ has joined #openstack-swift12:38
acolespino: if user1 and user2 do NOT have operator_role on tenant, then orch can create container c1 and c2, and give read access for c1 to user1, and read access to c2 to user2.12:40
acolespino: orch can always read c1 and c2. is that what you would like to achieve?12:40
pinoacoles: I would like that  "user1" and "user2" can create/read own container and they can only read a specific container created by "orch".12:41
pinoSo, I think that the scenario I would achive is impossible12:42
acolespino: I don't think that is possible - is user1 is able to create a container then user1 must have operator_role and therefore can read any container.12:45
acolesfor non operator_role users the access control list can only grant read or write access to objects.12:46
acoless/is user1/if user1/12:46
*** nshaikh has quit IRC12:55
*** aix has quit IRC13:02
*** aix has joined #openstack-swift13:04
pinoacoles: Thank you very much!13:08
*** ppai has quit IRC13:09
*** tdasilva has joined #openstack-swift13:09
*** NM has joined #openstack-swift13:11
*** kopparam has joined #openstack-swift13:13
*** kopparam has quit IRC13:17
*** Trixboxer has joined #openstack-swift13:39
openstackgerritAlistair Coles proposed a change to openstack/swift: Add description option to policy config  https://review.openstack.org/12042413:55
acolesnotmyname: ^^ i'm not sure about the max length limit - there is no max length for a policy name13:56
*** kopparam has joined #openstack-swift13:57
*** zaitcev has joined #openstack-swift14:05
*** ChanServ sets mode: +v zaitcev14:05
*** judd7 has joined #openstack-swift14:11
*** achhabr has joined #openstack-swift14:17
notmynamegood morning14:17
notmynameacoles: good point. commented in gerrit14:17
*** sandywalsh has quit IRC14:18
*** dabbler has joined #openstack-swift14:20
*** Manifesto has joined #openstack-swift14:40
*** pino has quit IRC14:42
acolesnotmyname: thx, yup it could be a lot bigger, lets see what anyone else thinks. i haven't yet thought of a similar case.14:42
*** mahatic has quit IRC14:42
*** kopparam has quit IRC14:43
*** kopparam has joined #openstack-swift14:44
*** kopparam has quit IRC14:48
*** annegentle has joined #openstack-swift14:52
*** rmcall has joined #openstack-swift14:59
*** annegentle has quit IRC15:03
*** dabbler has quit IRC15:08
*** morganfainberg is now known as morgan15:12
*** morgan is now known as Morgan15:13
*** Morgan is now known as morgan15:15
*** aix has quit IRC15:17
*** judd7 has quit IRC15:18
*** judd7 has joined #openstack-swift15:20
*** jasondotstar has joined #openstack-swift15:22
*** mwstorer has joined #openstack-swift15:26
*** aix has joined #openstack-swift15:30
*** gyee has joined #openstack-swift15:32
*** k4n0 has quit IRC15:34
*** pberis has quit IRC15:46
*** kenhui has joined #openstack-swift16:04
*** mahatic has joined #openstack-swift16:06
*** kyles_ne has joined #openstack-swift16:06
*** bvandenh has quit IRC16:09
*** jamiehannaford has quit IRC16:15
notmynameI was just told today, via the public mailing list, that there is now a deadline for python-*client releases of September 1816:22
notmynameso it would seem that I'll need to tag a release at or right before then16:22
*** vr1 has quit IRC16:41
zaitcevyay16:45
notmynamemattoliverau: looks like fungi just started a new ML thread about resurrecting the auto-abandon bot in gerrit. subject is "[openstack-dev] [all] Bringing back auto-abandon (was: Review metrics - what do we want to measure?)"16:46
*** rmcall has quit IRC16:48
*** mkollaro has quit IRC16:49
*** tkay has joined #openstack-swift16:50
*** rmcall has joined #openstack-swift16:50
*** kenhui has quit IRC16:53
*** kenhui has joined #openstack-swift16:54
*** rmcall has quit IRC16:56
*** rmcall has joined #openstack-swift16:57
*** aix has quit IRC16:58
*** echevemaster has joined #openstack-swift17:07
*** Manifesto has quit IRC17:13
notmynameso I think this is pretty cool. you can now sign up for an unlimited 45-day free trial of swiftstack. so like the vagrant-swift-all-in-one is a great way to easily get started with a dev environment, the swiftstack trial is an easy way to get started with a real deployment17:18
*** rmcall has quit IRC17:18
notmynameI know it's kinda weird to talk about a company's product in here, so apologies if you find that in bad taste17:19
*** rmcall has joined #openstack-swift17:20
*** mahatic has quit IRC17:24
*** mahatic has joined #openstack-swift17:29
TrixboxerHi, what can be the reason of17:39
TrixboxerGET /v1/AUTH_77443a36-22ed-473b-a0bd-053afdddbc25?format=json HTTP/1.1 - HTTP/1.1 200 OK17:39
TrixboxerGET /v1/AUTH_77443a36-22ed-473b-a0bd-053afdddbc25?format=xml HTTP/1.1 - HTTP/1.1 403 Forbidden17:39
*** mahatic has quit IRC17:46
*** mahatic has joined #openstack-swift17:51
zaitcevTrixboxer: nothing obvious comes to mind. Try json again, in case account was deleted.17:53
Trixboxersurprisingly after updating the client software it works :(17:54
TrixboxerGET /v1/AUTH_77443a36-22ed-473b-a0bd-053afdddbc25?format=xml HTTP/1.1 - HTTP/1.1 200 OK17:54
Trixboxerthe account stood same and no changes to swift17:54
portanteare you sure you have all the memcached configurations the same across all proxy nodes?17:57
*** gordc has joined #openstack-swift17:57
portanteTrixboxer: ^17:57
gordcjust curious but did something change with how swift handles 'set log_level' in middleware filters?17:57
Trixboxerportante: yes17:58
notmynamegordc: not that I'm aware17:58
gordcnotmyname: hmm... ok i'll dig into it... for some reason it seems like it's displaying ceilometer logs in swift again.17:58
*** rmcall has quit IRC17:59
*** rmcall has joined #openstack-swift18:01
notmynameTrixboxer: downgrading to recreate the error, then eg doing a tcpdump to see what's actually getting sent to swift could be useful in tracking it down18:01
Trixboxeraah difficult :(18:02
*** kyles_ne has quit IRC18:02
*** dabbler has joined #openstack-swift18:04
*** IgnacioCorderi has joined #openstack-swift18:05
notmynameTrixboxer: what client is it?18:05
*** dabbler has quit IRC18:05
*** IgnacioCorderi has quit IRC18:06
*** geaaru has quit IRC18:07
Trixboxernotmyname: cloudberry18:13
notmynamereminder that there is a swift team meeting in about 45 minutes https://wiki.openstack.org/wiki/Meetings/Swift18:13
notmynameTrixboxer: ah. not one that I have to do any local tests with18:13
notmynameTrixboxer: so far, it would seem that the ?format=xml request in the older version of cloudberry wasn't doing what you expected. that's why I suggested looking at what it was actually sending on the wire18:14
notmynameTrixboxer: alternatively, downgrade cloudberry and ensure that it still breaks and that you can successfully do ?format=xml with a different client (eg curl). then you pretty much know that the issue must be in the client18:15
notmynameTrixboxer: or you can use the new version of cloudberry that works and not worry about bugs in the old version anymore :-)18:16
Trixboxer:-)18:16
Trixboxernew version is good18:16
*** morgan is now known as morganfainberg18:23
*** morganfainberg is now known as morgan18:24
*** kyles_ne has joined #openstack-swift18:37
*** cutforth has joined #openstack-swift18:44
*** gvernik has joined #openstack-swift18:47
*** kota_ has joined #openstack-swift18:56
*** gordc has left #openstack-swift18:57
*** thurloat has quit IRC18:58
notmynamemeeting time in #openstack-meeting18:59
*** rmcall has quit IRC18:59
zaitcevhttp://www.theregister.co.uk/2014/08/26/seagates_eight_terabyte_spinner/ -- might we know someone other than Clover who tests these ^_^19:00
*** mjseger has joined #openstack-swift19:03
*** mjseger has quit IRC19:05
*** thurloat has joined #openstack-swift19:06
openstackgerritDoug Hellmann proposed a change to openstack/swift-specs: Add RSS feed  https://review.openstack.org/12054419:15
openstackgerritDoug Hellmann proposed a change to openstack/swift-specs: Remove templates from toctrees  https://review.openstack.org/12054519:15
openstackgerritDoug Hellmann proposed a change to openstack/swift-specs: Use the current date for the copyright statement  https://review.openstack.org/12054619:15
*** kenhui1 has joined #openstack-swift19:16
*** kenhui has quit IRC19:18
*** DisneyRicky has quit IRC19:19
*** DisneyRicky has joined #openstack-swift19:21
TaiSHiThis might sound stupid, but is there any way to mount a swift container as a filesystem?19:23
TaiSHi(I mean, to access it as a fs)19:24
tdasilvaTaiSHi: take a look at this project: https://github.com/swiftonfile/swiftonfile, it might help you...19:25
notmynamethat's not mounting swift as a filesystem :-)19:25
torgomaticTaiSHi: there's also some swift fuse filesystem thing out there somewhere19:26
TaiSHiYeah I found cloudfuse19:26
notmynameTaiSHi: but natively in swift, no19:26
*** AnjuT has joined #openstack-swift19:26
TaiSHiJust wanted a more professional opinion :P19:26
TaiSHiBecause the client wont modify the entire application just yet19:27
tdasilvacorrect, swiftonfile is not for mounting swift as a filesystem, but depending on what you are trying to achieve, it could help...19:29
TaiSHiWell currently the app works under nginx+php and access the files on disk19:29
TaiSHiI know nginx can access files directly from swift, but php cant, that aside, the application will try to write uploaded files on disk19:30
*** echevemaster has quit IRC19:30
TaiSHiPerhaps I didn't choose my weapon wisely19:32
notmynamedfg: swifterdarrell19:38
*** rmcall has joined #openstack-swift19:43
*** kota_ has quit IRC19:45
*** gvernik has quit IRC19:45
mattoliverauYay, back to bed, be back in a few hours.19:48
TaiSHiI'm sad, I was convinced that swift was my holy grial :P19:48
*** ZBhatti has joined #openstack-swift19:48
*** cutforth has quit IRC19:49
notmynameTaiSHi: I was just about to get started on that cook_me_breakfast middleware19:50
TaiSHinotmyname, interestingly enough, we don't cook our breakfast here :P19:51
notmynameTaiSHi: yet again, swift let's you down ;-)19:51
notmynames/'//19:51
TaiSHiI might be missing some joke due to language barrier19:52
TaiSHiSo I'll just sob and laugh at the same time19:52
notmynamelol19:52
TaiSHicloudfuse is not stable enough I think19:52
*** aswadr has quit IRC19:53
notmynameTaiSHi: in all seriousness, I'm a pretty big believer in the right tool for the job. and that you don't want one tool to do everything for you.19:53
TaiSHiI agree with you19:53
*** infotection has quit IRC19:53
TaiSHiBut I didn't see (or didn't want to see) that Swift, even if great at its job, wont do me no good since I can't update the entire app to work with it19:54
TaiSHiMeh, I was even watching videos to understand how node failure was handled19:54
notmynameTaiSHi: yes, I agree with you. that is a big barrier to entry for existing apps. there are thins like cloudfuse, and there are also some commercial gateways that do what you want (disclosure: my employer sells one)19:56
TaiSHiThe app isn't big enough (translation: my client is a cheap bastard) to buy a commercial solution19:57
TaiSHiI'm a bit scared of cloudfuse, also it's limited to 10k files in some dirs19:57
notmynamebut it is big enough to take advantage of swift's distributed storage and scaling facilities?19:58
notmynameI think the cloudfuse limit comes from the fact that the first page of results on a listing in swift (eg a container listing to show what objects are in it) is by default limited to 10000 items19:58
TaiSHiheh, I admit I might be overkilling it...19:58
TaiSHiCurrently 286552 files in the web's folder19:59
TaiSHi(that's just the main site)19:59
*** akshya11235 has joined #openstack-swift20:00
akshya11235Hi All, I want to run benchmarking on swift single node setup. Has anyone tried it before with COSbench?20:01
TaiSHiAlso, I'm prisoner of how the site is coded, it pretty much works as a wordpress (a big bad wordpress)20:01
notmynameakshya11235: oh. you're asking in every channel :-)20:02
akshya11235no jus the swift and the openstack channel. sometimes people are in different IRC :)20:02
*** infotection has joined #openstack-swift20:02
notmynameakshya11235: and -101 ;-)20:02
notmynameakshya11235: no worries20:03
notmynameTaiSHi: so maybe the first thing to do it look at similar things that you can do with wordpress. eg take all the media files and recreate a swift URL for them. but of course if you can't write a wordpress-style pluging or do any coding updates at all, then you're going to be hard-pressed20:03
notmynameakshya11235: yea, cosbench is built by the intel folks, so they've run it a lot. do you have specific questions about it?20:04
TaiSHinotmyname, that's the issue, the app hits on a PHP file to process images (even though I cache them after to reduce load)20:04
TaiSHiYes, perhaps the app itself could hit the swift proxy to retrieve the image and do whatever it does with it. I might check with the coder20:05
openstackgerritDoug Hellmann proposed a change to openstack/swift-specs: Use the current date for the copyright statement  https://review.openstack.org/12054620:06
openstackgerritDoug Hellmann proposed a change to openstack/swift-specs: Remove templates from toctrees  https://review.openstack.org/12054520:06
openstackgerritDoug Hellmann proposed a change to openstack/swift-specs: Add RSS feed  https://review.openstack.org/12054420:06
AnjuTnotmyname : a question  Hope I am not disturbing you :)20:07
TaiSHinotmyname, actually, it might be possible to reuse current app... it's all scrambled in my head20:08
goodeswhat is the current state of EC - can we just check out the branch in install/test it - or are there other libraries that need to be installed?20:08
torgomaticgoodes: well, if you check out the branch, you'll have to write the remaining 90% of the code, and then it'll work for you20:09
torgomaticoh right... ":)"20:09
goodessorry, I'm only qualified to write 20% that has 80% of the functionality20:10
torgomaticmore seriously, it's under active development, and isn't feature-complete yet20:11
torgomaticor even close, really20:11
torgomaticthere's pending patches for stuff, but what's on feature/ec isn't ready for use20:11
goodesso, pre-alpha?20:11
notmynamegoodes: sure, if you want a name for it :-)20:11
goodescontext was - is it worth checking out to play with to learn more, or is it too soon?20:12
notmynamegoodes: too soon to use, but not too soon to get involved in the development of it :-)20:12
goodesI hear you20:12
goodesif that will be the focus of the hackathon and then I'll start preping now20:13
*** annegentle has joined #openstack-swift20:13
*** akshya11235 has quit IRC20:14
goodeshow will the dependency on external EC libs be resolved - will they be wrapped in python packages or installed as system libraries?20:15
torgomaticgoodes: pyeclib is a python wrapper for one or two underlying C libraries, and that's what we're using20:16
mahatictorgomatic, Regarding the document patch, if in real deployments, someone chooses to use UUID, then what does the ring use?20:19
goodesI'm just finishing a project so I will dive in early next week. Is it all contained in the EC branch or are there any external dependencies (such as pyeclib)?20:19
torgomaticmahatic: the ring contains mount points; if the device in the ring is XYZ, then the filesystem in question is mounted at /srv/node/XYZ20:20
torgomaticit's easier for humans if that mount point matches the UUID or label, but it's not a technical requirement20:21
notmynamegoodes: the external stuff is pretty much settled AFAIK in pyeclib. the remaining work is inside of swift. look at the bottom of the priority reviews page (link in topic) for the EC project tracking stuff20:21
torgomaticgoodes: just pyeclib + feature/ec branch, IIRC... also the transitive dependencies of pyeclib if you really want to get into it20:21
goodesnotmyname: torgomatic: thanks - I'll try a quick install tomorrow :-)20:24
mahatictorgomatic, okay20:24
*** akshya11235 has joined #openstack-swift20:27
*** ZBhatti has quit IRC20:28
akshya11235I was trying to run the COSbench on SAIO. Had 2 Hypervisors, 1 had the SAIO VM and other was runing the COSbench20:29
*** ZBhatti has joined #openstack-swift20:29
akshya11235the install and benchmarking process itslef are fine20:29
akshya11235but I am getting a super low ops per second. and they max out pretty fast at ~250 ops per sec20:29
notmynameakshya11235: on a SAIO I'm not surprised20:30
akshya11235Is there some limitation of SAIO i m overlooking? or something like missing the caching of objects?20:30
notmynameakshya11235: the SAIO runs 4 of each storage node to simulate a cluster. and if you also have more than one worker process, well, it adds upquickly20:31
notmynameakshya11235: and then you get to the fact that if you're using loopback, all SAIO processes are sharing the same storage media (ie IO bus).20:31
notmynameakshya11235: all that means this: wow, I'm impressed you got 250 ops/sec on a SAIO!20:31
akshya11235notmyname: I see. would it make any difference with a separate partition for all the storage nodes?20:32
TaiSHiseparate disk ^20:33
akshya11235I understand that having a separate disk would definitely have an improvement20:33
akshya11235Just wanted to know if it was tried before and people were seeing something similar20:34
akshya11235becuase for the swift saio VM , i cranked up the vcpus it had and the Ram20:34
notmynameyeah, but you're still using the same physical resources20:37
*** kenhui1 has quit IRC20:39
*** zacksh has quit IRC20:40
*** zacksh has joined #openstack-swift20:41
akshya11235hmm20:52
akshya11235well thats true20:52
akshya11235the resource is still the same20:52
akshya11235everything gets stuck on the harddrive20:52
akshya11235so here to increase performace I will need separate storage nodes20:53
TaiSHi^20:53
notmynameakshya11235: yeah, pretty much20:54
notmynameakshya11235: but that's actually swift's design: scale out by adding servers or drives. and since it's a modular system you can add more where you need it20:54
AnjuTnotmyname: can I handle the RSEP body in swift client20:55
notmynameAnjuT: I'm not sure what you mean20:55
TaiSHinotmyname, I'm seriously considering cloudfuse but I'm scared :P20:56
notmynameTaiSHi: not sure how I can help you with that :-)20:56
TaiSHiread that some people maxed the IO (due to cloudfuse storing in tmp)20:56
TaiSHiI should actually stop being a whiny little girl and test it in production20:57
notmynamelol20:57
notmynameand on that note...20:57
torgomaticI love the name "FUSE". It's like... stuff's on fire, might explode soon, but go ahead and put your data in it20:57
notmynameI've got to drive to a meeting, so I'll be offline for the rest of the day.20:57
notmynamegood luck!20:58
AnjuTnotmyname:  when I am listing containers using --limit and --prefix ..I am getting an extra output of RESP Body in limit20:58
AnjuTnotmyname: ohh okk20:58
TaiSHinotmyname, If I'm not here tomorrow, erhm, well, maybe I ran to colombia20:59
TaiSHitorgomatic, *grin*20:59
*** annegentle has quit IRC21:06
tdasilvatorgomatic: thanks for the +2 on 11599521:10
torgomatictdasilva: sure thing21:10
*** miqui has quit IRC21:12
*** mahatic has quit IRC21:13
*** IgnacioCorderi has joined #openstack-swift21:17
*** AnjuT has quit IRC21:19
*** annegentle has joined #openstack-swift21:29
*** annegentle has quit IRC21:35
*** kyles_ne has quit IRC21:47
*** kyles_ne has joined #openstack-swift21:47
*** kyles_ne has quit IRC21:47
*** kyles_ne has joined #openstack-swift21:52
*** akshya11235 has quit IRC22:08
*** IgnacioCorderi has quit IRC22:10
*** NM has quit IRC22:14
*** dmsimard is now known as dmsimard_away22:20
*** IgnacioCorderi has joined #openstack-swift22:23
*** morgan is now known as morganfainberg22:27
mattoliverauMorning22:31
*** Trixboxer has quit IRC22:31
*** ZBhatti has quit IRC22:35
*** NM has joined #openstack-swift22:51
*** NM has left #openstack-swift22:52
*** achhabr has quit IRC22:58
openstackgerritOpenStack Proposal Bot proposed a change to openstack/python-swiftclient: Updated from global requirements  https://review.openstack.org/8925023:09
*** echevemaster has joined #openstack-swift23:55

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