Friday, 2015-03-13

*** vinsh has joined #openstack-swift00:00
*** annegentle has quit IRC00:02
*** vinsh has quit IRC00:04
*** zhill has quit IRC00:06
*** thumpba has quit IRC00:08
*** kota_ has joined #openstack-swift00:14
*** reed has joined #openstack-swift00:14
*** dmorita has joined #openstack-swift00:15
*** kota_ has quit IRC00:28
*** ho has joined #openstack-swift00:33
homorning00:35
mattoliverauho: morning00:54
peluseyo00:56
*** annegentle has joined #openstack-swift00:58
homattoliverau: morning! thanks.00:58
*** annegentle has quit IRC01:03
notmynamepeluse: back online if you need anything01:34
openstackgerritpaul luse proposed openstack/swift: Erasure Code Reconstructor  https://review.openstack.org/13187201:41
openstackgerritpaul luse proposed openstack/swift: Multiple fragment Archive Index Support  https://review.openstack.org/15963701:41
openstackgerritpaul luse proposed openstack/swift: Prefer policy to policy_index  https://review.openstack.org/16369001:41
pelusenotmyname, I'm good... off for some grub here shortly01:46
pelusethanks though01:46
openstackgerritMerged openstack/swift: fsync() on directories  https://review.openstack.org/12692301:55
*** tsg has quit IRC01:57
*** annegentle has joined #openstack-swift01:59
*** annegentle has quit IRC02:04
*** jrichli has joined #openstack-swift02:16
*** annegentle has joined #openstack-swift02:19
*** annegentle has quit IRC02:25
*** annegentle has joined #openstack-swift02:26
*** reed has quit IRC02:33
openstackgerritpaul luse proposed openstack/swift: Prefer policy to policy_index  https://review.openstack.org/16369002:33
*** haomaiwang has joined #openstack-swift02:38
*** devlaps has quit IRC02:43
*** annegentle has quit IRC02:46
*** tsg has joined #openstack-swift03:22
*** gyee has quit IRC03:23
*** earthrocker has joined #openstack-swift03:43
*** earthrocker has quit IRC03:43
*** ppai has joined #openstack-swift03:43
*** zaitcev has quit IRC03:58
*** delattec has quit IRC04:14
*** cdelatte has quit IRC04:14
*** cdelatte has joined #openstack-swift04:15
*** delattec has joined #openstack-swift04:21
*** cdelatte has quit IRC04:21
*** delatte has joined #openstack-swift04:21
*** ahonda has quit IRC04:24
*** jrichli has quit IRC05:03
hoos1: Please use this for your double-check of recon. http://paste.openstack.org/show/192018/05:30
*** delattec has quit IRC05:36
*** delatte has quit IRC05:36
*** cdelatte has joined #openstack-swift05:37
*** delattec has joined #openstack-swift05:37
*** SkyRocknRoll has joined #openstack-swift05:40
openstackgerritOpenStack Proposal Bot proposed openstack/swift: Imported Translations from Transifex  https://review.openstack.org/16408606:12
*** nshaikh has joined #openstack-swift06:55
*** bkopilov has quit IRC07:08
mattoliverauNight all, have a great weekend07:16
*** bkopilov has joined #openstack-swift07:28
*** donagh has quit IRC07:31
*** jamielennox has quit IRC07:31
*** bkopilov has quit IRC07:32
*** jamielennox has joined #openstack-swift07:34
*** donagh has joined #openstack-swift07:34
*** donagh has quit IRC07:39
*** jamielennox has quit IRC07:39
*** mmcardle has joined #openstack-swift07:43
*** donagh has joined #openstack-swift07:53
*** jamielennox|away has joined #openstack-swift07:55
*** jamielennox|away is now known as jamielennox07:55
*** chlong has quit IRC08:09
*** sc has joined #openstack-swift08:12
*** jistr has joined #openstack-swift08:12
*** openstackgerrit has quit IRC08:21
*** openstackgerrit has joined #openstack-swift08:22
*** rledisez has joined #openstack-swift08:22
openstackgerritTushar Gohad proposed openstack/swift: Bump eventlet version to 0.16.1  https://review.openstack.org/16410808:38
*** kei_yama has quit IRC08:44
*** jistr has quit IRC08:46
*** jistr has joined #openstack-swift09:04
*** jordanP has joined #openstack-swift09:16
openstackgerritLorcan Browne proposed openstack/swift: Add swift-recon feature to track swift-drive-audit error count  https://review.openstack.org/16388909:17
*** NM has joined #openstack-swift09:43
*** NM has quit IRC09:45
*** bkopilov has joined #openstack-swift09:49
openstackgerritPrashanth Pai proposed openstack/swift: Make object creation more atomic in Linux  https://review.openstack.org/16224309:54
*** bkopilov has quit IRC09:55
*** sluo_wfh has quit IRC10:08
*** nellysmitt has joined #openstack-swift10:17
*** delattec has quit IRC10:24
*** cdelatte has quit IRC10:24
*** aix has joined #openstack-swift10:44
*** jamielennox has quit IRC10:55
*** dmorita has quit IRC10:55
*** donagh has quit IRC11:01
*** erlon has joined #openstack-swift11:01
*** jamielennox|away has joined #openstack-swift11:02
*** jamielennox|away is now known as jamielennox11:02
*** donagh has joined #openstack-swift11:08
*** vinsh has joined #openstack-swift11:12
*** jamielennox has quit IRC11:14
*** jamielennox|away has joined #openstack-swift11:24
*** cdelatte has joined #openstack-swift11:24
*** jamielennox|away is now known as jamielennox11:24
*** vinsh has quit IRC11:32
*** haomaiwang has quit IRC11:37
*** ho has quit IRC11:46
*** bkopilov has joined #openstack-swift11:53
*** NM has joined #openstack-swift11:57
*** vinsh has joined #openstack-swift12:17
*** geaaru has joined #openstack-swift12:19
*** SkyRocknRoll has quit IRC12:20
*** bkopilov has quit IRC12:20
*** vinsh has quit IRC12:22
*** chlong has joined #openstack-swift12:24
*** cca has joined #openstack-swift12:36
*** vinsh has joined #openstack-swift12:37
*** cca has left #openstack-swift12:37
*** cca has joined #openstack-swift12:37
*** cca has quit IRC12:47
*** jkugel has joined #openstack-swift13:01
cschwedehmm, looks like a few patches on the ec branch need an update to reflect the change in 1.0.1 of pyeclib (missing ECPyECLibException)?13:15
cschwedenevermind, patches only need to be rebased, it’s done in 719483a81f83391ee8471ea3dc50ffce933cfc2713:25
openstackgerritChristian Schwede proposed openstack/swift: Bump PyECLib version to >= 1.0.1  https://review.openstack.org/16417213:28
openstackgerritpaul luse proposed openstack/swift: Multiple fragment Archive Index Support  https://review.openstack.org/15963713:35
pelusecschwede, was just looking at your comment on policy names being empty....13:37
cschwedepeluse: yeah, should probably never happen, but i’m wondering if a logging message would be appropriate. just in case. wdyt?13:40
*** ppai has quit IRC13:41
pelusecschwede, last time I checked we didn't allow empty strings when we parsed swift.conf but unless I'm seeing things (or not) I guess we do13:41
peluseif that made any sense :)13:42
cschwedehmm, or it’s only this function that allows empty strings, but never gets an empty string as arg. which is fine then (if the error is already raised earlier)13:42
peluseyeah, OK maybe the check is still there.  Look in the constructor for class StoragePolicy(object)13:43
cschwedei’m currently reviewing patch 159637, looks like there is some interesting stuff that could be used outside EC as well13:44
patchbotcschwede: https://review.openstack.org/#/c/159637/13:44
pelusecschwede, yeah, that's a key one for EC though and the focus of a lot of attention right now (I'm in San Fran today)13:45
openstackgerritpaul luse proposed openstack/swift: Erasure Code Reconstructor  https://review.openstack.org/13187213:46
cschwedepeluse: ah nice! you should talk to elon musk to get a direct hyperloop connection to SF ;)13:46
peluseI don't think that's available until Q3 this year :)13:47
*** mikehn_ has quit IRC13:48
*** mikehn has joined #openstack-swift13:49
*** bkopilov has joined #openstack-swift14:21
openstackgerritpaul luse proposed openstack/swift: Rename RUGGEDIZE to SSYNC  https://review.openstack.org/16419414:23
eikkeI was wondering: how are Swift developer meetups announced?14:28
*** doxavore has joined #openstack-swift14:29
*** wer has joined #openstack-swift14:32
*** CrackerJackMack has quit IRC14:33
*** panbalag has joined #openstack-swift14:33
doxavoreclayg: thanks for the help yesterday - i still must not understand the zero_byte_files_per_second setting in our use case, but taking it from the default down to 20/sec has taken I/O util down from 75% to 50%. (previously going with files_per_second=20, MB/sec=5 took it from 100% to 75%)14:35
doxavoreif the kernel supports it, is anyone aware of a reason you would _not_ want to use spice=yes in swift-2.2.2?14:36
*** CrackerJackMack has joined #openstack-swift14:38
*** jrichli has joined #openstack-swift14:40
tdasilvaeikke: typically notmyname announces it on irc meetings14:40
eikketdasilva: ok. should start attending those as well14:41
*** silor has joined #openstack-swift14:47
tdasilvaeikke: https://wiki.openstack.org/wiki/Meetings/Swift contains the meeting agenda14:47
*** thumpba has joined #openstack-swift14:53
*** thumpba has quit IRC14:53
eikketdasilva: thanks. might not be able to make it next week though, @ customer14:54
*** thumpba has joined #openstack-swift14:55
*** doxavore has quit IRC14:55
*** thumpba_ has joined #openstack-swift15:02
*** lcurtis has joined #openstack-swift15:04
*** thumpba has quit IRC15:05
*** erlon has quit IRC15:11
*** nellysmitt has quit IRC15:12
*** silor has quit IRC15:13
*** erlon has joined #openstack-swift15:29
*** tsg has quit IRC15:30
*** nshaikh has left #openstack-swift15:32
*** jrichli has quit IRC15:32
*** david-lyle_afk is now known as david-lyle15:33
*** mmcardle has left #openstack-swift15:35
notmynamegood morning15:38
tdasilvanotmyname: hello15:39
*** reed has joined #openstack-swift15:40
notmynameeikke: the mid-cycle/hackthon/whatevers? ya, I intentionally don't publicize them super widely (they're intended as a small, focused dev time), but I do my best to make them known to the contributor community. so ya, they are mentioned in the meetings and in here15:41
*** jrichli has joined #openstack-swift15:41
*** mahatic has joined #openstack-swift15:42
*** logan2 has joined #openstack-swift15:54
*** takotuesday has joined #openstack-swift15:55
takotuesdayHey guys, what do you think about using a swift container as a storage device for static html files for a heroku application? for static html files?15:57
notmynameI think that's a great idea15:57
takotuesdaycool15:58
openstackgerritpaul luse proposed openstack/swift: Rename RUGGEDIZE to SSYNC  https://review.openstack.org/16419415:59
takotuesdayso far Ive gotten my heroku app (it generates static html files and then hosts them) to generate the html and write to my swift container15:59
takotuesdaythe interesting thing about swift containers is there isnt really a directory structure15:59
takotuesdayso when I route to the static files I have to figure out a way to access just the string16:00
notmynametakotuesday: http://docs.openstack.org/developer/swift/middleware.html#staticweb16:00
takotuesdaynotmyname: thanks!16:01
openstackgerritThiago da Silva proposed openstack/swift: versioned writes middleware  https://review.openstack.org/13434716:03
takotuesdaynotmyname: do you think this works with multiple index files?16:04
notmynametakotuesday: what do you mean?16:04
notmynameoh, IIRC if you have a path that ends in a /, staticweb will look for the configured index page16:05
takotuesdayahh ok16:05
takotuesdayyeah so my app generates web content for each user which is globally accessible. Im using swift to maintain persistent storage for these sites. So user A could have a generated site, and user B could as well. These both need to be accessible from my app by all users16:06
notmynametakotuesday: sounds like a basic "global read" permission16:12
eikkenotmyname: thanks16:12
eikkeI should start working on the 'community interaction' part of my role :P16:12
notmynameeikke: :-)16:14
m_hanhi! newbie question - if i have an object stored in my swift-cluster,which is a media file, how can i play it on my VLC ?16:19
openstackgerritpaul luse proposed openstack/swift: Multiple fragment Archive Index Support  https://review.openstack.org/15963716:23
notmynamem_han: if VLC does html5 media (ie pseudo streaming with range requests), then I'd expect it to work out of the box with no problem16:24
openstackgerritpaul luse proposed openstack/swift: Multiple fragment Archive Index Support  https://review.openstack.org/15963716:33
*** panbalag has quit IRC16:40
*** panbalag has joined #openstack-swift16:41
openstackgerritpaul luse proposed openstack/swift: Diskfile decides if durable is written based on policy  https://review.openstack.org/16271716:43
openstackgerritpaul luse proposed openstack/swift: Erasure Code Reconstructor  https://review.openstack.org/13187216:50
*** takotuesday has quit IRC17:00
*** rledisez has quit IRC17:14
*** jordanP has quit IRC17:18
*** tsg_ has joined #openstack-swift17:19
notmynametdasilva: got a few minutes? I wanted to talk about you middleware/refactor patches17:20
tdasilvasure17:20
notmynamepeluse is here in the office with torgomatic and clayg yesterday and today. we've been talking about ec stuff, and your refactors came up17:22
tdasilvanotmyname: not sure that's a good thing or bad :P17:22
notmynametdasilva: https://review.openstack.org/#/c/134347/ and https://review.openstack.org/#/c/156825/ and (maybe) https://review.openstack.org/#/c/159610/217:22
notmynametdasilva: so in general and if possible, getting that stuff landed soon to help with the EC code in the proxy server would be good. in part, just to help with the EC merge to master17:23
notmynameso, what's the status on those, what do you thinks necessary to get them landed? just waiting on reviews? or is there other stuff too?17:25
*** delattec has joined #openstack-swift17:25
tdasilvanotmyname: so for obj. versioning. I think it's just a matter of reviews...clayg has been very helpful, but so far the only one to comment17:26
*** zhill has joined #openstack-swift17:26
tdasilvaI have to answer some comments he left there, but I think overall it is ready...17:26
notmynameok17:27
tdasilvareed: 156825 - while talking to clayg, I think we agreed to limit the scope of that one17:27
tdasilvas/reed/re:17:27
reeduhm17:28
reedah :)17:28
notmynamereed: get in theose swift code reviews, reed! ;-)17:28
tdasilvalol, soory reed17:28
*** cdelatte has quit IRC17:28
tdasilvacan't type!17:28
reedaye, captain notmyname17:28
notmynamelol17:28
tdasilvaanyway...I hope we can make good progress on that too17:29
tdasilvathen the last one, it's about defining the scope, maybe we can just limit to the PUT verb or go refactor the other verbs too17:30
*** erlon has quit IRC17:31
*** jistr has quit IRC17:31
*** m_han has quit IRC17:31
tdasilvanotmyname: was that helpful? :\17:32
*** bkopilov has quit IRC17:34
*** bkopilov has joined #openstack-swift17:35
*** rdaly2 has joined #openstack-swift17:39
*** doxavore has joined #openstack-swift17:40
*** bkopilov has quit IRC17:43
*** bkopilov has joined #openstack-swift17:44
openstackgerritThiago da Silva proposed openstack/swift: versioned writes middleware  https://review.openstack.org/13434717:48
*** bkopilov has quit IRC17:50
*** bkopilov has joined #openstack-swift17:51
*** bkopilov has quit IRC17:58
*** bkopilov has joined #openstack-swift17:59
*** doxavore has quit IRC18:00
openstackgerritDavid Goetz proposed openstack/swift: make swift-init skip things if config does not have section  https://review.openstack.org/16428518:05
openstackgerritDavid Goetz proposed openstack/swift: make swift-init skip things if config does not have section  https://review.openstack.org/16428518:10
notmynamedfg: fun with pep8? ;-)18:10
*** straycat is now known as sadcat_18:11
dfgnotmyname: ya- forgot to run it. its been a while i guess...18:11
notmynametdasilva: ya, limiting to PUT is definitely a possibility too18:13
notmynametdasilva: and some of that maybe we could proposed to feature/ec (since it also touches a lot of the PUT path) so that we spread out the merge conflicts (ie land it on feature/ec and get it in master when feature/ec lands in master)18:14
openstackgerritClay Gerrard proposed openstack/swift: wip: ec probe test  https://review.openstack.org/16429118:15
tdasilvanotmyname: yes! I was about to say that for the last patch is where it makes the most sense to try to merge as much of the effort with whatever is going on in the EC branch18:15
claygpeluse: https://review.openstack.org/16429118:15
claygfix the required replica count shiz and then try to make fill in the comments to rmtree on some datadirs18:16
notmynametdasilva: ya, so getting it proposed to feature/ec instead of on master would be great18:16
*** delatte has joined #openstack-swift18:16
claygdfg was into pep8 before they were popular, now that everyone is using it; gerrit probably hasn't heard of the tools dfg uses now18:19
*** delattec has quit IRC18:20
*** fandi has joined #openstack-swift18:20
*** fandi has quit IRC18:21
*** bsdkurt has quit IRC18:22
*** bkopilov has quit IRC18:25
*** bkopilov has joined #openstack-swift18:25
openstackgerritDavid Goetz proposed openstack/swift: make swift-init skip things if config does not have section  https://review.openstack.org/16428518:32
*** bkopilov has quit IRC18:32
dfgok- now there's a unit test for it too.18:32
*** bkopilov has joined #openstack-swift18:32
dfgand i ran pep8. even though i'm way too cool for that18:32
notmyname:-)18:34
tdasilvanotmyname: to get patch 159610 proposed to feature/ec branch we would need 134347 and 156825 to land on master first, no?18:37
patchbottdasilva: https://review.openstack.org/#/c/159610/18:37
notmynamewhoa! thanks patchbot18:38
* notmyname didn't remember that it did that18:38
notmynametdasilva: what about getting https://review.openstack.org/#/c/156825 on feature/ec18:39
tdasilvanotmyname: mmm..guess we could try that18:41
openstackgerritpaul luse proposed openstack/swift: wip: ec probe test  https://review.openstack.org/16429118:51
claygcschwede: I don't think an empty *base* string is really invalid18:54
claygcschwede: we use that get_policy_string and split_policy_string to convert a base (say "tmp", or "async" or "objects")18:54
claygto a stirn like "tmp-3", "async" (for Policy-0) or "objects-1"18:55
claygso if you give get_policy_string and empty base get_policy_string('', Policy-1) - it will return (correctly?) '-1' meaning I added the trailer for Policy-1 to ''18:55
claygthen if you split_policy_string('-1') - you get back '', Policy-118:56
claygso it seems reasonable for the inverse of get_policy_string('', Policy-0) == '' and split_policy_string('') == '', Policy-018:57
*** zaitcev has joined #openstack-swift18:57
*** ChanServ sets mode: +v zaitcev18:57
*** jordanP has joined #openstack-swift19:03
*** jordanP has quit IRC19:03
*** vinsh has quit IRC19:11
*** vinsh has joined #openstack-swift19:12
*** geaaru has quit IRC19:14
*** vinsh has quit IRC19:16
*** bsdkurt has joined #openstack-swift19:16
*** zul has quit IRC19:19
*** vinsh has joined #openstack-swift19:29
notmynamepeluse: torgomatic: clayg: jrichli is looking in to getting the functests to run against a specific storage policy19:31
notmynameFYI19:31
*** thumpba has joined #openstack-swift19:36
notmynamezaitcev: I think you wrote a guest blog post, cause it sounds exactly like what you'd say http://www.vitavonni.de/blog/201503/2015031201-the-sad-state-of-sysadmin-in-the-age-of-containers.html19:38
openstackgerritpaul luse proposed openstack/swift: wip: ec probe test  https://review.openstack.org/16429119:38
zaitcevnotmyname: you sound omnious19:38
*** thumpba_ has quit IRC19:40
*** thumpba has quit IRC19:41
zaitcevnotmyname: I'm sorry to sound like luddite, but downloading random shit at build time is a problem. Even if you pull from a trusted source like pypi and check SSL.19:45
*** bkopilov has quit IRC19:45
*** bkopilov has joined #openstack-swift19:48
*** zhill has quit IRC19:54
openstackgerritClay Gerrard proposed openstack/swift: wip: ec probe test  https://review.openstack.org/16429119:59
claygzaitcev: curl http://random.org/install | bash wfm19:59
notmynamezaitcev: oh, I completely agree. I wasn't complaining. I jsut think you'd really sympathize with what was there20:00
*** vinsh has quit IRC20:01
*** bkopilov has quit IRC20:02
*** bkopilov has joined #openstack-swift20:04
*** zhill has joined #openstack-swift20:07
*** panbalag has quit IRC20:16
openstackgerritMerged openstack/swift: Prefer policy to policy_index  https://review.openstack.org/16369020:16
*** delatte has quit IRC20:20
openstackgerritClay Gerrard proposed openstack/swift: wip: ec probe test  https://review.openstack.org/16429120:22
*** rdaly2 has quit IRC20:32
dfgnotmyname: you around?20:52
notmynamedfg: yo20:53
notmynamedfg: what's up?20:53
dfgso- i'm trying to decide something wanted your opinion. you think anybody would ever want container metadata that would be added to every object request20:53
dfglike you'd set x-container-meta-public-hello:there on the container and then every GET to an object in the container would have a response header of Hello:there on it20:54
dfgit sounds lame right? nobody would want that. just use object metadata20:55
notmynamewouldn't it be easier to add once to a container instead of to the millions of objects in the container (including all the existing ones there)?20:56
notmynamedfg: do you have a customer asking for it or some other new feature that would use it?20:56
dfga well ya. and a more useful case would be x-container-meta-public-cache-control: public, whatevrer20:56
dfglike for static web public containers20:57
notmynameya, cache control headers would be interesting, especially when plumbing through different caching stuff (cdns, varnish, etc)20:57
notmynameso you're wanting to keep it on a per-object basis?20:58
dfgi basicly need to write something that does this and keep going back and forth about special casing it and adding into swift.20:58
dfgthe thing is if I special case it and then somebody later goes and adds it to swift it'll be pretty ugly20:58
notmynameright. or when the next thing needs to be added for every object in a container20:59
dfglike if you wanted to use swift, public containers as an origin for a CDN it would be nice to do x-container-meta-public-cache-control: public, max-age:900 or whatever and then every origin gets a automatic ttl set for the cdn.21:02
dfgi feel like somebody eventually will want this.21:02
notmynameright. that seems like an awesome feature21:03
dfgbut you could just tell everbody to just set cache-control: public, ... on every object21:04
notmynameI haven't heard from anyone needing that (container meta applied to every object), but it also sounds like a relatively minor addition21:04
dfgya... i'm just trying to decide what to do.21:05
notmynamedfg: I think it's a great feature for swift. if...21:11
notmynamedfg: if you start it like the allowed_headers in the object server. I think the hard part is what to do when the object server already has some metadata. so eg you don't want to override the content-type or date headers based on the container metadata21:11
notmynameso if there were a config list of "these are the headers you can set", maybe that makes it safer21:12
notmynameI don't know21:12
notmynamewhat do you do when you have a cache control header set on the object? use that I'd guess. but are there some headers I can't override? or maybe only some that I can?21:13
dfgya- thats why i kinda just want to special case it. you start getting these ugly edge cases and the solution is worse than the problem21:14
notmynameya21:14
dfgi mena write a custom middleware21:14
notmynamedfg: your example had -public-. would you only want it for public data? or maybe have x-container-response-meta-foo: bar (and later x-container-request-meta-foo)21:15
notmynamethen configure only what's allowed to be set21:15
notmynamean example of the x-container-request-meta might be auto-adding an expiry time (maybe x-delete-after: 86400) for every object added to the container21:17
notmynameand the example for x-container-response-meta is your's with the cache control headers21:17
dfgoh- now you're just going crazy21:17
notmynameheh. that's the one I've heard of here. not the response headers21:17
dfgi've heard of people wanting that too21:18
dfghmph. i don't want to wade into all that though.21:18
notmynameso it seems like your cache control header idea could be pretty close to the other one too. so add the response header one. and let someone else do the request one later21:18
notmynamemake it simple. wouldn't be too much to wade through. config variable to set the explicit values that are allowed. keeps the surface space small21:19
claygtorgomatic: peluse: notmyname: patch 16320921:24
patchbotclayg: https://review.openstack.org/#/c/163209/21:24
*** patchbot has quit IRC21:25
*** patchbot has joined #openstack-swift21:25
dfg notmyname: alright- i'll play around with it for a bit and see how well it works. sounds like an ok solution. thx.21:25
notmynamedfg: no. thank you. I think it sounds pretty cool21:25
pelusepatch 16411221:51
patchbotpeluse: https://review.openstack.org/#/c/164112/21:51
openstackgerritClay Gerrard proposed openstack/swift: Rename RUGGEDIZE to SSYNC  https://review.openstack.org/16419421:52
notmynamewow, there's a lot to get done for EC in the next 2 weeks!21:56
*** echevemaster has joined #openstack-swift22:00
*** NM has quit IRC22:10
*** jkugel has quit IRC22:12
*** jrichli_ has joined #openstack-swift22:14
*** jrichli has quit IRC22:18
*** mahatic has quit IRC22:20
*** mahatic has joined #openstack-swift22:21
*** zhill has quit IRC22:21
notmynametsg_: still around?22:24
tsg_notmyname: yep22:24
notmynametsg_: can you help jrichli_? she's getting her saio for ec set up and having an issue with getting pyeclib installed22:25
tsg_notmyname: sure let talk to her22:25
jrichli_I got an error when I tried to pip install:22:25
jrichli_Error: liberasurecode-1.0.5 install failed :  Record file /tmp/pip-oHkCsm-record/install-record.txt not found22:25
openstackgerritJohn Dickinson proposed openstack/python-swiftclient: Reduce memory usage for download/delete and add --no-shuffle option to st_download  https://review.openstack.org/13033922:26
tsg_jrichli_: for starters, can you paste your pip install command line22:26
jrichli_pip install pyeclib22:27
swifterdarrelltsg_: I'm about to package pyeclib... anything I should know?22:27
tsg_swifterdarrell: package as a deb?22:27
swifterdarrelltsg_: mostly interested in where to get the appropriate code (pypi?)22:27
swifterdarrelltsg_: deb & rpm22:28
tsg_swifterdarrell: zigo is working on updating the debian package and I have written to zaitcev about rpm22:28
swifterdarrelltsg_: (for our product--the actual packaging process is quite wacky, but I've got a handle on that)22:28
swifterdarrelltsg_: I just need the (right) source; but an existing deb or rpm package always speeds things up22:28
zaitcevtsg_: Looks like I missed it, unless it was just now.22:28
tsg_zaitcev: it was last night I believe22:29
tsg_let me forward you again22:29
swifterdarrelltsg_: is the latest on PyPi good?22:29
swifterdarrelltsg_: (which appears to be "1.0.4"?)22:29
tsg_swifterdarrell: that's a special version (with other packages integrated)22:30
swifterdarrelltsg_: also appears to be super-fresh: 2015-03-1322:30
tsg_let me point you in the right direction, one moment22:30
swifterdarrelltsg_: k22:30
tsg_swifterdarrell: yes, I pushed an update last night with some error reporting changes22:30
tsg_swifterdarrell: pyeclib tag "v1.0.5m" off of https://bitbucket.org/kmgreen2/pyeclib22:32
tsg_swifterdarrell: liberasurecode has been packaged already for Debian/Ubuntu22:32
tsg_http://packages.ubuntu.com/search?suite=trusty-backports&searchon=names&keywords=liberasurecode22:32
tsg_swifterdarrell: zigo asked last night and I have sent him the new tags .. so he may already be in the middle of packaging the latest pyeclib and liberasurecode22:33
tsg_perhaps I should add you to that thread22:33
tsg_zaitcev: email sent to 'Pete Zaitcev' <zaitcev@redhat.com>, subject line: "PyECLib/liberasurecode releases"22:34
swifterdarrelltsg_: cool, I got the 1.0.5m code tarball successfully; and that liberasurecode link should give me a leg up packaging that as well22:35
tsg_yes22:35
tsg_swifterdarrell: there is already a pyeclib debian version as well, in the process of being accepted into Ubuntu - you might be able to use those control files for pyeclib22:36
tsg_https://packages.debian.org/unstable/main/python-pyeclib22:37
swifterdarrelltsg_: sweet!22:37
tsg_swifterdarrell: you will need these 2 packages for Jerasure EC backend - http://packages.ubuntu.com/search?keywords=jerasure&searchon=names&suite=trusty-backports&section=all22:38
tsg_(libjerasure2, libgf-complete1)22:39
tsg_those two have been backported to trusty and are fairly up to date22:39
tsg_so you should be able to use those debs as-is22:40
openstackgerritJohn Dickinson proposed openstack/swift: List valid EC types in error  https://review.openstack.org/14231122:40
tsg_jrichli_: try removing "/tmp/pip-*" and retry the "pip install" perhaps?22:43
jrichli_i'll try it22:43
jrichli_there was nothing to remove: I ran again, and same error22:45
notmynamejrichli_: what os?22:47
notmynameI just upgraded it on my saio with no problem (`pip install -U pyeclib`)22:47
jrichli_Ubuntu 14.04.1 LTS22:47
jrichli_i will try that22:48
zigotsg_: Indeed, I'll work on this very soon.22:49
jrichli_same thing.22:49
jrichli_I had tried running python setup.py install before22:49
jrichli_and had got this:22:49
*** cdelatte has joined #openstack-swift22:49
jrichli_src/c/pyeclib_c/pyeclib_c.c:32:25: fatal error: erasurecode.h: No such file or directory22:49
jrichli_ #include <erasurecode.h>22:49
*** delattec has joined #openstack-swift22:49
jrichli_that was using this:22:50
jrichli_Downloading https://pypi.python.org/packages/source/P/PyECLib/PyECLib-22:50
jrichli_1.0.4.tar.gz#md5=9886dd9a4b3d66fa40a642945fd7007722:50
tsg_jrichli_: I assume you have not installed liberasurecode or other deps before, correct?22:52
tsg_zigo: many thanks! :)22:52
jrichli_nothing for EC until today, that is right22:52
zigotsg_: Is there a chance that SSE is detected and use at runtime only?22:53
zigotsg_: Because I had to disable it, unfortunately... :(22:53
tsg_zigo: that's possible with ISA-L :)22:53
zigoWhat's ISA-L ?22:53
tsg_zigo: we'll recommend folks to build Jerasure/gf-complete locally if they need performance22:53
tsg_zigo: https://01.org/intel%C2%AE-storage-acceleration-library-open-source-version22:53
*** delattec has quit IRC22:53
*** cdelatte has quit IRC22:53
tsg_zigo: storage SIMD primitives library22:54
tsg_zigo: open source version supports Erasure Coding - something that can use a Debian package for sure22:54
zigotsg_: Did you bump sonames?22:55
tsg_zigo: https://bitbucket.org/tsg-/liberasurecode/commits/4e1290ea61e5dba3e782155f426e4e492664d52522:56
zigoI'll have to rename liberasurecode0 into liberasurecode1, which is annoying (it's going to have to go through the NEW queue...).22:56
tsg_zigo: ack, but that's what we get by going to the stable(r) 1.x series :(22:58
zigotsg_: SONAME has nothing to do with moving from beta to stable.22:59
zigoYou'd bump it if there's an ABI breakage.22:59
zigoAnd eventually, we'll make a transition so that the lib and its dependencies are moving at once from SID to Testing.23:00
tsg_zigo: I get the point .. what is your suggestion on SONAME?  keep it at 0 for now, I can make that change if you feel necessary but that might break stuff for folks that are already using liberasurecode.so.1?23:02
tsg_s/keep it at 0 for now/keep it at 0 for now?/23:03
zigotsg_: If there's already some users for .1, then yes, it's too late.23:03
zaitcevtsg_: thanks, I got the message. Indeed, I only packaged jerasure and gf-complete. Haven't touched PyECLib yet.23:03
tsg_zigo: mainly folks that pulled off of pypi in the last few days only, though23:03
zigotsg_: In the future, just keep in mind that the SONAME has nothing to do with the version number of your software.23:03
zigotsg_: Look at MySQL for example...23:04
zigoWe're at libmysqlclient18 for version 5.5 of mysql.23:04
tsg_zigo: agreed - I read your comment differently to start with, but I do see the point23:04
tsg_zigo: acknowledged23:04
eikkedo you aim for full EC support in Kilo?23:05
zigotsg_: Oh, and one more thing, SONAME bumps are a major pain to deal with in Debian, if there's many reverse dependencies.23:05
zigoGot to coordinate the transition with the release team, etc.23:05
tsg_zigo: since most folks are using pypi version which has liberasurecode integrated for now, I can change liberasurecode to use the old SONAME23:05
tsg_zigo: I am glad you brought this up .. we sure don't want to add to the pain :)23:06
zigotsg_: For me, this has very little consequences, since liberasurecode was never in Testing.23:06
zigotsg_: So, no transition, etc.23:06
zigo(thanks to the freeze of Jessie, and the fact it wasn't there, somehow...)23:07
notmynameeikke: the current plan is that kilo will have an EC beta. we'll begin the merge to master is about 2 weeks, based on what's done between now and then23:07
zigotsg_: Just to give you an example. I also maintain miniupnp in Debian. I had to fix 4 or 5 software because of some API change (including bitcoin, warzone2000, and some other which I don't remember).23:08
zigoJust because upstream decided to break stuff...23:08
zigoIt took about 2 or 3 months to do s.23:08
tsg_zigo: :)  that sucks - feel your pain!23:08
notmynameeikke: we expect that nearly all functionality will be in there, but there will be room to improve (filling in the final gaps)23:09
tsg_zigo: in the current situation, are you suggesting to move ahead with liberasurecode1?23:09
zigoThe process is: upload the new lib to experimental. Try to build all reverse dependencies to see if something breaks. File bugs for the breakage, preferably with patches if possible. Then upload to Sid, raise the bugs severity from important to serious, wait a few days, then do NMU (Non-maintainer-upload) if the maintainer of the package doesn't do his homework...23:10
zigotsg_: In the current situation, don't do anything, I don't care.23:10
zigoI'm just warning you for the future, in order to avoid pain... :)23:10
tsg_zigo: gotcha :)23:10
mattoliverauWow, you all talk a lot, its Saturday here and thought I'd read some scroll back... Wow.. I guess it is a Friday for y'all. :p23:11
tsg_zigo: and I did learn a lot for sure going just through the pain of getting the stuff into Ubuntu :)23:11
tsg_zigo: points taken on SONAMEs and ABI compatibility23:11
tsg_zigo: thank you for doing the heavy lifting here!23:11
notmynamemattoliverau: tons of stuff going on. IT'S SO EXCITING!!!23:12
mattoliveraunotmyname: now I feel like I'm missing out :(23:12
tsg_jrichli_, assume you've already attempted "sudo pip install pyeclib"?23:13
mattoliverautdasilva: I'll take a look at your patches Monday my time (Sunday yours)23:13
notmynamemattoliverau: if you feel that way, download some EC patches and get to reviewing!! (also, fixing merge conflicts between the versioned writes middleware and the ec branch would be helpful)23:13
zigotsg_: Well, thanks to you guys for doing the erasurecode stuff, which is a great feature!23:14
tsg_zigo: thanks! :)23:14
jrichli_tsg_ oh geez, I can't believe I didn't run as sudo.  That was it!  I would have expected a permission denied error instead23:15
tsg_jrichli_, I am so relieved! ;)23:15
jrichli_thanks so much!23:15
tsg_jrichli_, it has been a pain to keep pypi, jenkins and co happy23:15
tsg_jrichli_, thought we ran into something new! and that we might need a new tag :)23:15
notmynamejrichli_: lol23:15
tsg_jrichli_, glad it worked23:15
mattoliveraunotmyname: maybe I will... Tho the wife may kill me for working on weekends :p23:16
jrichli_me too!23:16
jrichli_^^ re: glad it worked, not that my wife may kill me :-)23:16
eikkenotmyname: interesting, thanks23:17
*** tsg_ has quit IRC23:19
notmynameeikke: are you in france or the bay area? I thought you were in france, but if so you're on IRC pretty late on a friday... :-)23:20
eikkenotmyname: now in France. Just got back home from an Internations party (though its only 00:21)23:21
notmyname"only"23:21
mattoliverauLol23:21
mattoliverauThanks jrichli_23:22
eikkemy days are mostly 9AM-2AM23:22
*** lcurtis has quit IRC23:27
zigoliberasurecode 1.0.5 and pyeclib 1.0.5m uploaded to Sid. :P23:28
*** david-lyle is now known as david-lyle_afk23:29
*** jrichli_ has quit IRC23:29
eikkewhat kind of EC is used? plain RS?23:32
*** keving has joined #openstack-swift23:32
notmynameeikke: it's quite extensible.23:32
notmynameand keving just joined23:32
notmynameeikke: keving is the EC expert23:32
kevingwhats up?23:33
notmynamekeving: eikke was just asking which ec algos are supported in pyeclib/liberasurecode23:33
eikkekeving: just asked which kind of EC is being used23:33
kevingreed-solomon mostly23:33
eikkeplain RS or something different23:33
eikkeright23:33
kevingwhat do you mean by "plain"?23:33
kevingthe underlying libraries use pretty sophisticated optimizations23:34
eikkesurue23:34
kevingthere is also a class for XOR-based codes available23:34
eikkeI meant,using the general idea of RS, or another form of EC23:34
kevingboth23:35
kevingi assume most people will just use RS23:35
eikkei see23:35
* eikke has done quite some EC research in the past23:35
notmynameeikke: keving maintains jerasure these days23:35
eikkemostly non-RS (though cant talk too much about that, not even in current job, because of things)23:35
notmynameeikke: also note that pyeclib (or liberasurecode) have a pretty small interface that allows for any other EC library to be used. (details left to the reader?)23:36
kevingsure.  so, the XOR-based codes are based on a paper i co-authored in 201023:36
kevingeikke: if you have something, we could make a backend in liberasurecode23:36
kevingeikke: i assume you are talking about some form of regenerative code?23:37
eikkekeving: rateless codes, yes23:37
kevingoh rateless23:37
kevingfor storage?23:37
eikkenow I should STFU :)23:38
kevingok23:38
keving(i am also doing a little work in rateless codes)23:38
eikkekeving: you at intel?23:38
kevingBox23:38
eikkeoh, ok23:38
kevingi would like to add regenerative codes to liberasurecodce, but the current API does not fit rateless codes23:39
notmynamekeving: typey, typey23:39
kevinghaha23:40
* eikke doesnt get that joke?23:40
kevingeikke: gotta run to another meeting.  feel free to drop my an email (kmgreen2@gmail.com) if you wanna talk more23:40
notmynameeikke: something I picked up from some australians. basically, "get to typing!"23:41
eikkekeving: would love to, but Im afraid I better don't due to corporate BS (<- which doesnt refer to my current employer, because of the very same corporate BS I can't touch any of the EC stuff there either)23:42
kevingeikke: heh.  i get it.  in any case, the offer is still on the table.23:42
kevingnotmyname: let me know if there are any other issues on the library side of things.  AFAIK, tushar and the packaging folks have things worked out.23:43
mattoliveraubloody Australians23:43
eikkewill remember (and dlook into the libs you've been working on with quite some interest soon)23:43
kevingeikke: cool.23:44
notmynamekeving: ok. will do. and tsg has been doing great tracking down the packaging stuff. Ithink we're good for know23:44
kevingnotmyname: good to hear!23:44
kevingok, gtg23:44
notmynamekeving: thanks for stopping by23:44
kevingnotmyname: sure.  i should do it more often ;)23:44
*** keving has left #openstack-swift23:45
notmynameyes you should :-)23:45
*** mahatic has quit IRC23:46
notmynameclayg: torgomatic: how can I help you this weekend?23:49

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