Friday, 2016-05-27

kota_morning00:04
kota_tdasilva: the discussion place for pyeclib/liberasurecode issues moved to somewhere (lanunchpad) too?00:06
kota_tdasilva: for them, we have sitll a bunch of open issues like here, https://bitbucket.org/kmgreen2/pyeclib/issues?status=new&status=open00:06
*** bill_az_ has quit IRC00:17
*** lyrrad has quit IRC00:17
*** Jeffrey4l has joined #openstack-swift00:17
*** itlinux has joined #openstack-swift00:18
*** arch-nemesis has quit IRC00:21
*** Vinsh has quit IRC00:24
*** bill_az_ has joined #openstack-swift00:26
*** klamath has quit IRC00:26
*** klamath has joined #openstack-swift00:26
*** klamath has quit IRC00:27
*** klamath has joined #openstack-swift00:28
*** Suyi has quit IRC00:37
*** kei_yama has quit IRC00:53
*** kei_yama has joined #openstack-swift00:53
*** itlinux has quit IRC00:57
*** itlinux has joined #openstack-swift00:58
*** gyee has quit IRC01:03
*** itlinux has quit IRC01:03
openstackgerritTim Burke proposed openstack/swift: Buffer DiskfileWriter writes  https://review.openstack.org/9113301:09
claygkota_: i'm with you bro - where do I file issues against openstack/pyeclib now?  the new 1.2.1 release is broken w/o a liberasure release :D01:09
*** asettle has joined #openstack-swift01:10
kota_Hi clayg, I'm not sure where we should discuss the issue. Probably bitbucket's issue list is still working for tsg- and Kevin.01:14
*** esker has joined #openstack-swift01:15
claygwell if we're going to be maintaining them in openstack/ namespace we should probably have issues there?  maybe luanchpad projects?01:15
clayghttps://launchpad.net/pyeclib !!01:15
kota_looks like tdasilva has been working to create https://launchpad.net/pyeclib01:15
kota_clayg: bro!01:15
kota_I found liberasurecode version, https://launchpad.net/liberasurecode01:16
kota_too01:16
*** asettle has quit IRC01:17
claygopenstack is magic01:18
claygtdasilva: https://bugs.launchpad.net/pyeclib/+bug/158622001:18
openstackLaunchpad bug 1586220 in PyECLib "ImportError: /usr/lib/python2.7/dist-packages/pyeclib_c.so: undefined symbol: liberasurecode_backend_available" [Undecided,New]01:18
kota_either is fine to me becuase I can get subscription from bitbucket too. But for others working on openstack, launchpad is probably good place to discuss issues.01:18
kota_clayg: nice01:19
*** esker has quit IRC01:19
claygkota_: if you have any issues you're *actively* tracking upstream it'd be good I think to get the migrated over to launchpad (manually?) you can reference the bitbucket issue - but the plan is that openstack/ is the new home and we'll maintain those libraries via gerrit01:20
claygwhich is great!01:20
kota_yeah01:22
*** diogogmt has quit IRC01:25
*** mingyu has joined #openstack-swift01:34
*** bill_az_ has quit IRC01:36
*** mingyu has quit IRC01:38
*** kei_yama has quit IRC01:42
*** kei_yama has joined #openstack-swift01:42
*** esker has joined #openstack-swift01:51
*** janonymous_ has quit IRC01:53
*** esker has quit IRC01:55
*** itlinux has joined #openstack-swift01:59
*** itlinux has quit IRC02:04
*** mingyu has joined #openstack-swift02:16
*** nadeem has joined #openstack-swift02:19
*** vint_bra has joined #openstack-swift02:23
*** openstackgerrit has quit IRC02:36
*** openstackgerrit has joined #openstack-swift02:43
*** arch-nemesis has joined #openstack-swift02:54
*** openstackgerrit has quit IRC02:56
*** nadeem has quit IRC02:58
*** jamielennox is now known as jamielennox|away03:01
-openstackstatus- NOTICE: Gerrit is going offline briefly to check possible filesystem corruption03:02
*** ChanServ changes topic to "Gerrit is going offline briefly to check possible filesystem corruption"03:02
*** sams-gleb has joined #openstack-swift03:07
*** sams-gleb has quit IRC03:12
mattoliveraunotmyname, clayg: grrr, sqlite OFFSET turns out not to be the greatest. Not on really large containers anyway. But think I've found a solution that's super quick, just maybe not always pick the best. I decided to blog it (I know haven't touched my blog in 3 years) so others don't have to find out the hard way like me: http://oliver.net.au/?p=26703:19
*** openstackgerrit has joined #openstack-swift03:19
*** dmorita has quit IRC03:19
*** sheel has joined #openstack-swift03:19
*** dmorita has joined #openstack-swift03:22
*** ChanServ changes topic to "Let's talk! We're nice | Review Dashboard: https://goo.gl/mtEv1C | Logs: http://eavesdrop.openstack.org/irclogs/%23openstack-swift/ | Meetings: https://wiki.openstack.org/wiki/Meetings/Swift | Community Dashboard: http://not.mn/swift/swift_community_dashboard.html"03:22
-openstackstatus- NOTICE: after a quick check, gerrit and its filesystem have been brought back online and should be working again03:22
*** mvk_ has joined #openstack-swift03:32
openstackgerritJanie Richling proposed openstack/swift: crypto - Don't use 'meta' for crypto-meta dict  https://review.openstack.org/32193703:33
notmynamemattoliverau: interesting. nice update03:35
*** mkrcmari__ has quit IRC03:36
mattoliverauignore my bad english.. or should I say Australian.03:36
notmynameI've long ago stopped thinking it was "English" ;-)03:37
*** dmorita has quit IRC03:37
*** dmorita has joined #openstack-swift03:38
mattoliveraunotmyname: :P03:40
mattoliveraualso izip_longest makes the code sample _so_ much shorter.03:40
mattoliveraudamn fancy iterators that make life easier :P03:41
* mattoliverau goes to find lunch03:41
claygmattoliverau: yeah it has to *acctually* order all of them to find whos in that posistion - interesting03:41
*** dmorita has quit IRC03:41
mattoliverauso I could use the OFFSET on smaller containers to get it "right" and the fuzzy apporach on large.. or just do the latter for everything.03:42
mattoliveraubut let me run the code on the large container again and find the next bottleneck first :P03:43
*** links has joined #openstack-swift03:46
claygnever to two different things if the one thing works03:49
claygmattoliverau: i doesn't make any sense tho - there has to be a way to just ask the damn index what it has in it's middle?04:00
claygthis was great btw - sqlite is so great - https://www.sqlite.org/queryplanner.html04:02
*** klrmn has quit IRC04:04
*** nadeem has joined #openstack-swift04:09
mattoliverauclayg: maybe with a patch, but the index is a linked list (as far as I could determine) so I don't think it can jump to the middle. Tho am happy to be wrong cause it'll make my life easier. Maybe I need to look at the codes :)04:18
claygmattoliverau: wait... can you do listings on the container?  like marker queries and stuff - or the whole thing is just hozed?04:20
clayglike i was sorta thinking the problem had to be in the sorter - it's trying to get the entire 700M rows in order before thinking about the limit part04:22
mattoliverauWell it's running of rusty metal, so it seems hozed to me. Me thinks the split may still take a while. /me needs to play with SSDs next.04:22
clayghrmm..04:22
clayggl04:22
mattoliverauI tried without sorting, IE no order by name04:23
*** psachin has joined #openstack-swift04:24
mattoliverauclayg: on sqllite I can LIMIT so should be able to container listing. it's more the OFFSET 350M is kinda slow :)04:26
*** adu has joined #openstack-swift04:37
mahaticjrichli: are you around?04:39
jrichlimahatic: yes, for a few minutes more.  what's up?04:40
*** arch-nemesis has quit IRC04:41
mahaticjrichli: just had a query on trello card. but i think figured (left a comment): https://trello.com/c/v5xkmidJ/111-use-derived-iv-for-container-listing-etag-encryption-i-e-same-as-object-sysmeta-value04:41
mahaticI think I figured*04:41
*** dmorita has joined #openstack-swift04:42
*** vint_bra has quit IRC04:43
jrichlimahatic: I think the card is to change the iv used for all etag encryption to always be the one used for the container listing.  currently, we use a random iv for the 'regular' object etag.04:44
jrichliis that what you are thinking too?04:44
*** itlinux has joined #openstack-swift04:45
mahaticjrichli: it's the other way round i suppose. the object etag currently uses derived iv and container listing etag uses a random iv. Now we want container listing etag to use derived iv as well04:45
*** ChubYann has quit IRC04:46
jrichlimahatic: yes, right.  that's what I meant ;-)04:46
*** dmorita has quit IRC04:46
jrichliI think it's my bed time now!04:46
mahaticheh. yeah ;)04:47
jrichlimahatic: have a good day04:48
mahaticjrichli: thanks, good night!04:48
*** itlinux has quit IRC04:48
*** SkyRocknRoll has joined #openstack-swift04:51
*** ppai has joined #openstack-swift04:57
*** janonymous has joined #openstack-swift05:00
*** arch-nemesis has joined #openstack-swift05:03
*** arch-nemesis has quit IRC05:08
*** sams-gleb has joined #openstack-swift05:09
*** zaitcev has quit IRC05:12
*** sams-gleb has quit IRC05:13
*** klamath_ has joined #openstack-swift05:18
*** klamath has quit IRC05:18
*** adu has quit IRC05:20
*** arch-nemesis has joined #openstack-swift05:21
*** itlinux has joined #openstack-swift05:29
*** geaaru has joined #openstack-swift05:58
*** dmorita has joined #openstack-swift06:02
openstackgerritMahati Chamarthy proposed openstack/swift: crypto: use derived iv for container listing etag  https://review.openstack.org/32197006:03
*** rcernin has joined #openstack-swift06:04
*** dmorita has quit IRC06:07
mahaticacoles_: I combined this card: https://trello.com/c/v5xkmidJ/111-use-derived-iv-for-container-listing-etag-encryption-i-e-same-as-object-sysmeta-value and https://trello.com/c/F7J1xcE0/108-include-path-iv-base-in-crypto-meta-for-listing-etag in patch 32197006:09
patchbotmahatic: https://review.openstack.org/#/c/321970/ - swift (feature/crypto) - crypto: use derived iv for container listing etag06:09
mahatichope it's okay06:09
*** rcernin has quit IRC06:15
*** rcernin has joined #openstack-swift06:20
*** daemontool has joined #openstack-swift06:44
*** hseipp has joined #openstack-swift06:50
*** itlinux has quit IRC06:51
*** sams-gleb has joined #openstack-swift06:56
*** hseipp has quit IRC06:56
*** nadeem has quit IRC07:04
*** tdasilva has quit IRC07:07
*** nadeem has joined #openstack-swift07:10
-openstackstatus- NOTICE: zuul required a restart due to network outages. If your change is not listed on http://status.openstack.org/zuul/ and is missing results, please issue a 'recheck'.07:14
*** nadeem has quit IRC07:22
*** alex_osso has joined #openstack-swift07:25
*** tdasilva has joined #openstack-swift07:27
*** ChanServ sets mode: +v tdasilva07:27
*** daemontool has quit IRC07:32
*** tesseract has joined #openstack-swift07:36
*** mmcardle has joined #openstack-swift08:04
*** mmcardle1 has joined #openstack-swift08:09
*** mmcardle has quit IRC08:11
*** jordanP has joined #openstack-swift08:13
*** asettle has joined #openstack-swift08:25
*** asettle has quit IRC08:26
*** joeljwright has joined #openstack-swift08:31
*** ChanServ sets mode: +v joeljwright08:31
*** sycoder has joined #openstack-swift08:37
*** sanchitmalhotra has quit IRC08:38
openstackgerritMahati Chamarthy proposed openstack/swift: crypto: use derived iv for container listing etag  https://review.openstack.org/32197008:42
*** dmorita has joined #openstack-swift08:42
*** acoles_ is now known as acoles08:43
*** dmk0202 has joined #openstack-swift08:46
*** dmorita has quit IRC08:47
sycoderhi...I am having an 503 error in my swift installation, does anyone have some advice on what could be the reasons/solution ?08:48
*** mingyu has quit IRC08:50
*** ouchkernel has quit IRC09:02
*** ouchkernel has joined #openstack-swift09:06
*** jmccarthy has joined #openstack-swift09:12
*** jmccarthy has quit IRC09:15
*** daemontool has joined #openstack-swift09:18
*** jmccarthy has joined #openstack-swift09:20
*** sycoder has quit IRC09:39
*** SkyRocknRoll has quit IRC09:40
*** permalac has joined #openstack-swift09:54
*** permalac has quit IRC09:54
*** permalac has joined #openstack-swift09:54
*** permalac has quit IRC09:55
*** permalac has joined #openstack-swift09:55
*** SkyRocknRoll has joined #openstack-swift09:56
*** ouchkernel has quit IRC10:38
*** openstackgerrit has quit IRC10:47
*** openstackgerrit has joined #openstack-swift10:48
*** bzurawski has joined #openstack-swift10:49
openstackgerritAlistair Coles proposed openstack/swift: crypto - remove default root secret  https://review.openstack.org/31820811:26
openstackgerritAlistair Coles proposed openstack/swift: crypto - Don't use 'meta' for crypto-meta dict  https://review.openstack.org/32193711:38
*** sams-gleb has quit IRC11:39
*** openstackgerrit has quit IRC11:47
*** openstackgerrit has joined #openstack-swift11:48
*** daemontool has quit IRC11:51
*** daemontool has joined #openstack-swift11:51
*** daemontool has quit IRC12:08
*** daemontool has joined #openstack-swift12:08
*** mmcardle1 has quit IRC12:09
*** sams-gleb has joined #openstack-swift12:12
*** daemontool has quit IRC12:18
*** daemontool has joined #openstack-swift12:18
*** dmellado is now known as dmellado|lunch12:20
*** dmellado|lunch is now known as dmellado12:20
*** itlinux has joined #openstack-swift12:22
*** mkrcmari__ has joined #openstack-swift12:23
*** mvk_ has quit IRC12:26
*** klamath has joined #openstack-swift12:28
*** klamath_ has quit IRC12:28
*** mkrcmari__ has quit IRC12:30
*** mkrcmari__ has joined #openstack-swift12:30
*** daemontool has quit IRC12:31
*** daemontool has joined #openstack-swift12:32
*** mkrcmari__ has quit IRC12:40
*** daemontool has quit IRC12:42
*** daemontool has joined #openstack-swift12:42
*** dmorita has joined #openstack-swift12:44
*** itlinux has quit IRC12:45
*** itlinux has joined #openstack-swift12:47
*** openstackgerrit has quit IRC12:48
*** dmorita has quit IRC12:48
*** openstackgerrit has joined #openstack-swift12:49
*** ppai has quit IRC12:49
*** klamath has quit IRC12:53
*** klamath has joined #openstack-swift12:53
*** mmcardle has joined #openstack-swift12:58
*** MikeG451 has joined #openstack-swift13:00
*** kei_yama has quit IRC13:06
*** mkrcmari__ has joined #openstack-swift13:08
*** diogogmt has joined #openstack-swift13:12
*** StraubTW has joined #openstack-swift13:13
*** asettle has joined #openstack-swift13:27
*** diogogmt has quit IRC13:28
*** itlinux has quit IRC13:33
*** asettle has quit IRC13:42
*** daemontool has quit IRC13:48
*** daemontool has joined #openstack-swift13:49
openstackgerritMerged openstack/swift: crypto - Don't use 'meta' for crypto-meta dict  https://review.openstack.org/32193713:50
*** diogogmt has joined #openstack-swift13:56
*** daemontool has quit IRC14:03
*** daemontool has joined #openstack-swift14:04
*** openstackgerrit has quit IRC14:18
*** openstackgerrit has joined #openstack-swift14:19
joeljwrighti14:20
joeljwright(sorry, dropped something on my keyboard)14:21
*** alex_osso has left #openstack-swift14:28
*** dmk0202 has quit IRC14:35
*** alex____3 has joined #openstack-swift14:37
openstackgerritAlistair Coles proposed openstack/swift: crypto - stop using key id to derive GET path keys  https://review.openstack.org/31814814:41
*** Lickitysplitted has joined #openstack-swift14:43
*** Lickitysplitted_ has quit IRC14:43
openstackgerritAlistair Coles proposed openstack/swift: crypto - stop using key id to derive GET path keys  https://review.openstack.org/31814814:45
*** alex____3 is now known as alex_osso14:47
acolesjoeljwright: o14:57
*** SkyRocknRoll has quit IRC15:00
*** jistr is now known as jistr|call15:01
claygtdasilva: good morning - looks like you go tmy back on the liberasurecode?!15:10
claygacoles: u15:11
*** sams-gleb has quit IRC15:11
*** tesseract has quit IRC15:11
acolesclayg: LOL. very good15:11
claygacoles: were you thinking more like "p"?15:12
claygwasn't quite sure where we were going15:12
acolesclayg: "i-o, i-o, it's off to work we go"15:13
tdasilvaclayg: yep, sorry about the issue15:13
acolesclayg: actually i was thinking i-o-u-a  - what comes next?15:14
claygBEER!15:15
claygtdasilva: not your fault - we'll get good at all of this eventually tho ;)15:16
*** Jeffrey4l has quit IRC15:16
joeljwrightacoles: :D15:16
tdasilvaclayg: yep...need to come up with a good strategy I guess. I'm wondering if we need to time or at least make sure new pyeclib releases work with liberasurecode releases that have already been packaged by ubuntu, rh?15:18
tdasilvaclayg: or do we just make sure that it works with the latest liberasurecode release15:19
claygtdasilva: I think that one is the good enough15:19
claygtdasilva: we can't control what's packaged - we just need to make sure that good versions are available15:19
claygtdasilva: I'm not super stoked about the failure mode - I think maybe soe different flags int he Makefile would have prevented me from being able to build with the older liberasure-devel package - that would have hinted to me something was busted15:21
tdasilvaclayg: yeah, my mistake is that when I built it yesterday, I built it again liberasurecode master, so I didn't see anything15:23
claygtdasilva: simple thing maybe just always cut liberasure first (since it has no depends) and pyeclib second?15:23
claygtdasilva: yeah I didn't notice either way because it was just a warning :\15:23
tdasilvaclayg: yeah, that's what I was thinking, or at least make sure to build pyeclib against the latest libEC release15:23
*** rcernin has quit IRC15:24
tdasilvaand not master :P15:24
claygtdasilva: well we'll have to build it against master in development?15:24
claygi'm sure we can figure it out next time - just tag a liberasurecode release - it'll be fine :P15:24
tdasilvaclayg: but for swift, I don't think we can up the release in requirements.txt until liberasurecode packages are available15:25
*** jistr|call is now known as jistr15:25
claygtdasilva: right15:25
tdasilvaclayg: yeah, in dev for sure, but I mean to tag a release, you want to make sure the release works with whatever is available in libEC15:25
claygtdasilva: so there's a case maybe that pyeclib should be able to be updated and support different libEC versions?  :\15:25
tdasilvaclayg: I don't follow...15:26
claygtdasilva: yeah if that's possible I think that'd be good15:26
*** mingyu has joined #openstack-swift15:26
claygtdasilva: well you can pip install pyeclib 1.2.1 but it might not work with the libEC .so's you have installed from packages?15:26
tdasilvacorrect! it doesn't15:27
tdasilva:)15:27
claygtdasilva: I think the fact that pyeclib compiles with those warnings about missing symbols could be fixed - then at least trying to pip install would fail?15:27
notmynamegood morning15:28
notmynameabout to go get on the bus, but catching up on the pyeclib/liberasurecode stuff15:28
tdasilvaclayg: I see, yes, would need to look into that...sounds like a new bug report :)15:28
notmynametdasilva: did tagging the pyeclib release automatically push something to pypi?15:29
*** links has quit IRC15:29
notmynameseems like we could take advantage of the -infra setup to test master branches together and against latest stable too. I mean, that kind of thing has been set up for a lot of the projects already15:31
notmynameok, time for me to walk to the bus stop15:34
tdasilvanotmyname: it did not push into pypi, but that was an error, which I already tracked down with help from -infra15:36
*** mingyu has quit IRC15:36
tdasilvanotmyname: agree on setting up tests to test different branches15:37
*** mingyu has joined #openstack-swift15:37
*** mingyu has quit IRC15:37
tdasilvanotmyname: will fix the pypi issue in a bit15:38
tdasilva*will attempt15:38
*** jordanP has quit IRC15:43
*** admin6 has quit IRC15:45
*** pgbridge has joined #openstack-swift15:47
*** zaitcev has joined #openstack-swift15:48
*** ChanServ sets mode: +v zaitcev15:48
*** bzurawski has quit IRC15:52
*** itlinux has joined #openstack-swift15:52
timburkemattoliverau: the index *must* be more than just a linked-list, otherwise things like marker queries would suck. i'm *sure* there's a tree involved; just not one that can easily spit out the Nth element. i could totally see a doubly-linked list being used when iterating through the index, though15:58
timburkemattoliverau: nice solution, though; the unicode conversions made me a little nervous, but i think utf-8 should be well ordered like that, unlike some other encodings (hi windows-1252!)15:59
*** lakshmiS has joined #openstack-swift15:59
timburkeclayg: on "there has to be a way to just ask the damn index what it has in it's middle?" - that's actually rather non-trivial. an order-statistic tree could do it, but that's an extra layer of complexity16:01
*** mkrcmari__ has quit IRC16:04
*** psachin has quit IRC16:04
*** itlinux has quit IRC16:06
acolesnotmyname: IIRC you prompted this change, does it seem an appropriate approach to you? https://review.openstack.org/#/c/318208/6/swift/common/middleware/keymaster.py16:08
patchbotacoles: patch 318208 - swift (feature/crypto) - crypto - remove default root secret16:08
claygtimburke: well the exact middle might require counting - but if it is a tree they have to do *something* about balancing right?  or left?  or maybe left, right, right...16:11
*** sams-gleb has joined #openstack-swift16:11
*** silor has joined #openstack-swift16:12
tdasilvammm...when I try a git review on liberasurecode it tries to submit a lot of old commits, not just my most recent one...any clues?16:12
claygmattoliverau: I think the fuzzy middle has a good shot of getting things wrong if the extreams are outliers :\16:12
claygmattoliverau: plus I was starting to think the middle might not even be that interesting if you're considering "object_count" the middle (because of expired/deleted rows)16:12
claygmattoliverau: what about "select name from objects where deleted in (1, 0) order by name offset 400000" MMMMMMMnnnnNNNNEEEhexTTT16:13
clarkbtdasilva: if you rebased and all those commits changed or if you are pushing to a different branch that can happen16:13
*** joeljwright has quit IRC16:15
*** sams-gleb has quit IRC16:15
openstackgerritThiago da Silva proposed openstack/liberasurecode: Release 1.2.0  https://review.openstack.org/32225716:18
tdasilvaclarkb: thanks!16:18
tdasilvaclayg: so my plan is to merge that and tag that commit to cut the release, which means master HEAD, are you ok with that?16:19
notmynamegood morning again16:19
claygtdasilva: yeah that's great!16:20
*** dmorita has joined #openstack-swift16:21
notmynameacoles: yeah, that seems like much better message16:21
acolesnotmyname: k. I'll take that as a +1 then ;)16:22
openstackgerritThiago da Silva proposed openstack/liberasurecode: Release 1.2.0  https://review.openstack.org/32225716:22
notmynameacoles: and later we can figure out something about "you didn't change it from a default"?16:22
acolesnotmyname: actually I think the plan is to not have a default when we propose to master, we only have it there now so that we can have encryption in the pipeline for gate functional tests on the feature branch16:23
notmynameeven better :-)16:24
acolesnotmyname: so you MUST set a value and it MUST be base64 encoded 32 bytes or more16:24
notmynameyeah, that sounds great16:25
acolesmaybe we someone can figure out a check for sufficient entropy16:25
acolesnotmyname: we could put an example of how to generate a key in doc (openssl rand -base64 32) - IDK if that is too prescriptive??16:26
notmynamewe probably should, as long as it's vetted by some crypto person :-)16:27
notmynameprobably with some words around it like "make sure /dev/random has entropy" or something16:27
acolesk, will do. we already have some words in there from a crypto expert about high entropy.16:28
notmynameI saw something at LCA this year that's a tiny USB device designed specifically to product 1MB/sec of high quality random noise. basically, plug it in, and /dev/random is immediately good to go16:28
acolesnotmyname: was it called "line manager" :P16:29
notmyname:-)16:30
notmynamespeaking of management, this was an interesting read this morning http://randsinrepose.com/archives/bored-people-quit/16:31
notmynameah, here it is http://altusmetrum.org/ChaosKey/. produces 12Mb/s of random bits16:35
notmynamefully open hardware and software (including firmware)16:35
*** geaaru_ has joined #openstack-swift16:39
*** mingyu has joined #openstack-swift16:39
*** geaaru has quit IRC16:39
*** asettle has joined #openstack-swift16:44
acolesnotmyname: I just updated priority reviews with a list of 6 remaining patches that would ideally merge on feature/crypto before we move to feature/crypto-review. There are a few others that imho could just follow-on on crypto-review or in case of doc carry across for continued review.16:45
*** mmcardle has quit IRC16:45
notmynamegreat, thanks16:45
*** nadeem has joined #openstack-swift16:46
*** nadeem has quit IRC16:46
acolesI'd like to start preparing the short chain of patches for crypto-review, so could you request that branch from infra? no rush - I am out on Monday anyway.16:46
*** geaaru__ has joined #openstack-swift16:47
notmynameme too (out on monday)16:47
*** can8dnSix has joined #openstack-swift16:47
*** geaaru_ has quit IRC16:47
*** asettle has quit IRC16:50
*** nadeem has joined #openstack-swift16:52
acolesmahatic: jrichli timburke tdasilva - see few lines above re updated priority reviews for crypto - we should focus on finishing those patches in order to move to crypto-review16:52
tdasilvaacoles: ack16:53
*** klrmn has joined #openstack-swift16:56
*** asettle has joined #openstack-swift16:59
*** asettle has quit IRC17:02
*** gyee has joined #openstack-swift17:05
*** SkyRocknRoll has joined #openstack-swift17:07
openstackgerritAlistair Coles proposed openstack/swift: crypto - add overview doc (WIP)  https://review.openstack.org/31209617:17
*** gyee has quit IRC17:18
*** gyee has joined #openstack-swift17:20
*** acoles is now known as acoles_17:27
*** tqtran has joined #openstack-swift17:27
openstackgerritThiago da Silva proposed openstack/liberasurecode: Release 1.2.0  https://review.openstack.org/32225717:39
*** links has joined #openstack-swift17:49
openstackgerritThiago da Silva proposed openstack/liberasurecode: Release 1.2.0  https://review.openstack.org/32225718:04
openstackgerritMerged openstack/liberasurecode: Release 1.2.0  https://review.openstack.org/32225718:10
*** links has quit IRC18:10
tdasilvacrap, something went wrong...one sec18:13
*** nadeem has quit IRC18:14
openstackgerritThiago da Silva proposed openstack/liberasurecode: Add NEWS and README back  https://review.openstack.org/32229318:27
tdasilvatimburke: ^^^ :/18:27
* timburke sighs18:29
timurtdasilva: clayg sorry I've been MIA around the packaging stuff. I agree with Clay that at the very least pyeclib should break the build on undefined symbols. I'm juggling a few balls in the air at the moment, but I'd like to add a patch to fix that (unless someone beats me to it). The other thing that would be nice to add is a version check for the features with an ifdef (checking the version from18:29
*** ChubYann has joined #openstack-swift18:29
timurerasurecode_version.h). That'd be second patch I'd add... hopefully soon18:29
timuroh, hey, I can also +2 tdasilva's patch :D18:29
tdasilvatimur: yes you can :D18:29
openstackgerritMerged openstack/liberasurecode: Add NEWS and README back  https://review.openstack.org/32229318:30
*** thumpba has joined #openstack-swift18:40
zaitcevThe RPM philosophy is to control dependencies with Requires: in the spec. So in theory if I write the spec right, liberasurecode always builds without error and in a repeatable fashion.18:44
notmynametdasilva: I was out of the office yesterday. ping me if you need something with pyeclib or liberasurecode18:44
*** silor has quit IRC19:00
*** MikeG451 has quit IRC19:02
tdasilvanotmyname: I just tagged a new libEC release. One of the next things I'd like to figure out is what to do with issues in bitbucket. Not sure if there's an automated way to migrate them to launchpad, so need to look into that19:03
notmynametdasilva: how many are we talking about?19:04
tdasilvapyeclib alone has 14, which doesn't sound like a lot, but there's a ton of conversation within each of them19:04
tdasilvaas people are trying to figure out problems19:04
notmynamehmmm19:04
tdasilvae.g: https://bitbucket.org/kmgreen2/pyeclib/issues/80/decode-segfault-with-certain-corrupted19:05
notmynamelet me think about it. I think we should have some plan there, but it's not something that is a blocker for starting to use it19:05
*** mmcardle has joined #openstack-swift19:08
*** mingyu has quit IRC19:08
*** itlinux has joined #openstack-swift19:09
tdasilvanotmyname: agreed19:16
tdasilvatdasilva: another item is getting the gate jobs running19:16
*** mmcardle has quit IRC19:18
*** daemontool has quit IRC19:18
*** itlinux has quit IRC19:22
*** mingyu has joined #openstack-swift19:30
*** thumpba_ has joined #openstack-swift19:33
*** thumpba has quit IRC19:35
*** openstack has joined #openstack-swift21:44
claygmaybe squashing could make a guess at left or right - solve the issue if the far left gets small after rows expire... but there's some hope it might just all eventually expire21:44
claygstill going to be hard to co-ordinate piviot points :\21:45
notmynameif the initial shard method is "take X rows from the top, repeat", then we could do a binary method on the smaller ones. but I'm not sure the top/prefix method wouldn't end up with the same result21:45
claygnotmyname: if we can get by with only one thing that works I think that's best :)21:45
notmynameoh yeah. coordinating the pivots21:45
notmynameyeah. one thing >>> two things21:46
*** dmorita has joined #openstack-swift21:46
claygeven in the quorm situation you have the issues with handoffs and over replication - but as long as you have a consistent reconciliation maybe it'll all work out eventually21:46
*** esker has quit IRC21:47
claygI'd love it if we could figure out some consistent naming such that even if two split brains come up with a different row to split on they still start populating the same named shard - then those guys can work out row reconciliation on mostly independently if needed21:48
*** thumpba has quit IRC21:48
claygno good ideas at the moment tho :'(21:49

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