)]}'
{"id":"openstack%2Fliberasurecode~424353","triplet_id":"openstack%2Fliberasurecode~master~I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0","project":"openstack/liberasurecode","branch":"master","topic":"phazrio_libphazr","hashtags":[],"change_id":"I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0","subject":"Add Phazr.IO libphazr backend to liberasurecode","status":"MERGED","created":"2017-01-23 22:13:10.000000000","updated":"2017-03-01 04:03:42.000000000","submitted":"2017-03-01 02:21:14.000000000","submitter":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"total_comment_count":65,"unresolved_comment_count":0,"has_review_started":true,"meta_rev_id":"33a81e72ba2a73ab561e808f7c83e3bf1371ca0d","_number":424353,"virtual_id_number":424353,"owner":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"actions":{},"labels":{"Verified":{"approved":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"all":[{"value":0,"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},{"value":2,"date":"2017-03-01 02:21:14.000000000","post_submit":true,"_account_id":3,"name":"Jenkins","username":"jenkins"},{"value":0,"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},{"value":0,"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},{"value":0,"date":"2017-03-01 04:03:42.000000000","post_submit":true,"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"}],"values":{"-2":"Fails","-1":"Doesn\u0027t seem to work"," 0":"No score","+1":"Works for me","+2":"Verified"},"description":"","default_value":0,"optional":true},"Code-Review":{"approved":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"all":[{"value":2,"date":"2017-03-01 02:06:10.000000000","permitted_voting_range":{"min":2,"max":2},"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},{"value":0,"_account_id":3,"name":"Jenkins","username":"jenkins"},{"value":0,"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},{"value":2,"date":"2017-02-28 21:55:44.000000000","permitted_voting_range":{"min":2,"max":2},"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},{"value":0,"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"}],"values":{"-2":"Do not merge","-1":"This patch needs further work before it can be merged"," 0":"No score","+1":"Looks good to me, but someone else must approve","+2":"Looks good to me (core reviewer)"},"description":"","default_value":0,"optional":true},"Workflow":{"approved":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"all":[{"value":1,"date":"2017-03-01 02:06:10.000000000","permitted_voting_range":{"min":1,"max":1},"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},{"value":0,"_account_id":3,"name":"Jenkins","username":"jenkins"},{"value":0,"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},{"value":0,"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},{"value":0,"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"}],"values":{"-1":"Work in progress"," 0":"Ready for reviews","+1":"Approved"},"description":"","default_value":0,"optional":true}},"removable_reviewers":[],"reviewers":{"REVIEWER":[{"_account_id":3,"name":"Jenkins","username":"jenkins"},{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"}]},"pending_reviewers":{},"reviewer_updates":[{"updated":"2017-01-23 22:13:19.000000000","updated_by":{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},"reviewer":{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},"state":"REVIEWER"},{"updated":"2017-02-28 21:55:44.000000000","updated_by":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"reviewer":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"state":"REVIEWER"},{"updated":"2017-03-01 02:06:10.000000000","updated_by":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"reviewer":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"state":"REVIEWER"},{"updated":"2017-03-01 02:21:14.000000000","updated_by":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"reviewer":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"state":"REVIEWER"}],"messages":[{"id":"4ab5f1e5ab724223c4b457cfebe975f2e81b5b1f","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-01-23 22:13:10.000000000","message":"Uploaded patch set 1.","accounts_in_message":[],"_revision_number":1},{"id":"d338995e8989c67e38fc13ce972b88b5ee3f9c27","author":{"_account_id":10068,"name":"Welcome, new contributor!","username":"welcome-message"},"date":"2017-01-23 22:13:19.000000000","message":"Patch Set 1:\n\nThank you for your first contribution to OpenStack.\n\n    Your patch will now be tested automatically by OpenStack testing frameworks\n    and once the automatic tests pass, it will be reviewed by other friendly\n    developers. They will give you feedback and may require you to refine it.\n\n    People seldom get their patch approved on the first try, so don\u0027t be\n    concerned if requested to make corrections. Feel free to modify your patch\n    and resubmit a new change-set.\n\n    Patches usually take 3 to 7 days to be reviewed so be patient and be\n    available on IRC to ask and answer questions about your work. Also it\n    takes generally at least a couple of weeks for cores to get around to\n    reviewing code. The more you participate in the community the more\n    rewarding it is for you. You may also notice that the more you get to know\n    people and get to be known, the faster your patches will be reviewed and\n    eventually approved. Get to know others and become known by doing code\n    reviews: anybody can do it, and it\u0027s a great way to learn the code base.\n\n    Thanks again for supporting OpenStack, we look forward to working with you.\n\n    IRC: https://wiki.openstack.org/wiki/IRC\n    Workflow: http://docs.openstack.org/infra/manual/developers.html\n    Commit Messages: https://wiki.openstack.org/wiki/GitCommitMessages","accounts_in_message":[],"_revision_number":1},{"id":"41a130981a7cb0961b0155c2f6c4d18bda130926","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-01-23 22:18:40.000000000","message":"Patch Set 1: Verified+1\n\nBuild succeeded (check pipeline).\n\n- gate-liberasurecode-unit http://logs.openstack.org/53/424353/1/check/gate-liberasurecode-unit/cffb379/ : SUCCESS in 5m 05s","accounts_in_message":[],"_revision_number":1},{"id":"63ea1135ed4c4d4bca15142d4dfc70db1ac9633a","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-01-23 22:26:27.000000000","message":"Uploaded patch set 2: Commit message was updated.","accounts_in_message":[],"_revision_number":2},{"id":"26676c1589d4a2069e2055c4b8a5db9ed637c2b6","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-01-23 22:28:24.000000000","message":"Uploaded patch set 3: Commit message was updated.","accounts_in_message":[],"_revision_number":3},{"id":"ad0309c567e0a83b3f9378a232d323dce76f74eb","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-01-23 22:34:49.000000000","message":"Patch Set 3: Verified+1\n\nBuild succeeded (check pipeline).\n\n- gate-liberasurecode-unit http://logs.openstack.org/53/424353/3/check/gate-liberasurecode-unit/b8ba1aa/ : SUCCESS in 4m 58s","accounts_in_message":[],"_revision_number":3},{"id":"4885c0a2115fce64a22ee5d43171e1e390c19d4b","author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"date":"2017-01-23 23:26:20.000000000","message":"Patch Set 3:\n\n(5 comments)\n\nSome initial thoughts after a quick glance.","accounts_in_message":[],"_revision_number":3},{"id":"5cdcf36ab4f1f7c98eda9411502aafdf748d1396","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-01-24 00:42:36.000000000","message":"Patch Set 3:\n\nTim, thanks for the great input! \n\n\u003e (5 comments)\n \u003e \n \u003e Some initial thoughts after a quick glance.\n\n \u003e https://review.openstack.org/#/c/424353/3/include/erasurecode/erasurecode.h\n \u003e File include/erasurecode/erasurecode.h:\n\n \u003e Line 77:     int p;                  /* libphazr backend internal metadata */\n \u003e Does this mean deployers/consumers will need to recompile pyeclib against latest liberasurecode even if they\u0027re not planning to use libphazr? (We would probably recommend   that anyway; I just want to better understand the process.)\n\n \u003e Judging by https://github.com/openstack/pyeclib/blob/master/src/c/pyeclib_c/pyeclib_c.h#L36 I\u0027m guessing yes?\n\nIf a consumer is not planning to use libphazr, they don\u0027t need to recompile pyeclib, a default value p will be used in backend implementation, so it can be omitted.\n \n \u003e Should we start eating into the \"reserved for future expansion\" space? Otherwise, we\u0027ve changed the offset to the checksum type... FWIW, I see that we\u0027ve done that sort of thing before in https://github.com/openstack/liberasurecode/commit/dbbc02d and https://github.com/openstack/liberasurecode/commit/e30f788 (though I\u0027m not sure we did the right thing for .hd in that second one...)\n\n \u003e Or maybe we could/should (ab)use the .hd arg?\n\n \u003e We can probably use the .hd arg and get rid of .p to minimize code change.  \n\n \u003e https://review.openstack.org/#/c/424353/3/include/erasurecode/erasurecode_preprocessing.h\n \u003e File include/erasurecode/erasurecode_preprocessing.h:\n\n \u003e Line 60:         char **orig_payload, uint64_t *payload_len);\n \u003e This makes me wonder if we should have been passing the ec_backend_t instance to all of these from the get-go :-/\n\n \u003e Or maybe I\u0027m mistaken, and there\u0027s a bigger difference between libphazr_fragments_to_string and fragments_to_string than I imagine?\n\nThere is an offset position in data ptr needed to be accounted for in libphazr, but if we pass ec_backend_t instance to fragments_to_string, we can do it with if/else for that.\n\n \u003e https://review.openstack.org/#/c/424353/3/src/erasurecode.c\n \u003e File src/erasurecode.c:\n\n \u003e Line 603: ＆\n \u003e FULLWIDTH AMPERSAND, fancy!\n\n \u003e (I don\u0027t know that anyone actually cares; I just noticed that it renders differently in Gerrit :-) \n\nWe will normalize it with regular \u0026.\n \n \u003e https://review.openstack.org/#/c/424353/3/src/erasurecode_helpers.c\n \u003e File src/erasurecode_helpers.c:\n\n \u003e Line 204:         ceill((double) data_len / alignment_multiple) * alignment_multiple;\n \u003e Maybe worth an if/else?\n\nYes, we can make the change\n\n \u003e https://review.openstack.org/#/c/424353/3/test/liberasurecode_test.c\n \u003e File test/liberasurecode_test.c:\n\n \u003e Line 244: };\n \u003e Should these have .p set?\n\nA default value 1 will be used if .p is not set.","accounts_in_message":[],"_revision_number":3},{"id":"ec557f2c0216a076eaddc1de455c36cd1fa7dd00","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-01-24 01:12:55.000000000","message":"Uploaded patch set 4.","accounts_in_message":[],"_revision_number":4},{"id":"04c3bcf46803e81e9b0bb955a705b0c6ad169aaa","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-01-24 01:14:06.000000000","message":"Patch Set 4: Verified-1\n\nBuild failed (check pipeline).  For information on how to proceed, see http://docs.openstack.org/infra/manual/developers.html#automated-testing\n\n- gate-liberasurecode-unit http://logs.openstack.org/53/424353/4/check/gate-liberasurecode-unit/816d101/ : FAILURE in 28s","accounts_in_message":[],"_revision_number":4},{"id":"2ce13212307eb65b21d6be077d04cc39b6577a6a","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-01-24 01:23:57.000000000","message":"Uploaded patch set 5.","accounts_in_message":[],"_revision_number":5},{"id":"48fc69d68a92813f43fe2a73d304d281365796b4","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-01-24 01:32:04.000000000","message":"Patch Set 5: Verified+1\n\nBuild succeeded (check pipeline).\n\n- gate-liberasurecode-unit http://logs.openstack.org/53/424353/5/check/gate-liberasurecode-unit/436e832/ : SUCCESS in 5m 28s","accounts_in_message":[],"_revision_number":5},{"id":"a21c0c44e3171d1ec6182ce052af67405f49383f","author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"date":"2017-01-31 08:16:30.000000000","message":"Patch Set 5: Code-Review-1\n\n(10 comments)\n\nAt first, it\u0027s great to hear a new contributor is interested in adding a new backend to liberasurecode. Welcome! and Thanks!\n\n\nHowever, probably I didn\u0027t get about backend completely but it looks it requires to bite some of our common routines (e.g. preprocessing, helpers) via if branches.\n\nI added a few comments on that but not sure and need your help to understand *what change required* on your backend.\n\ne.g. memory allocation order? memory size?\n\nThe original design for liberasurecode is providing common erasurecode api for the backends and *abstracts common functions* like allocate the necessary memory and free them after it works so that I\u0027d reduce *backend uniqueness* as possible from there.\n\nIf we requires some pre/post processing for specific backend, maybe making a hook point somehwere may be a better solution... but anyway, I\u0027d know what\u0027s required to suggest something at first.\n\nThanks!","accounts_in_message":[],"_revision_number":5},{"id":"b4444d9fe087f351223325847a8077a72685b399","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-01-31 19:12:28.000000000","message":"Patch Set 5:\n\n(9 comments)\n\n\u003e (10 comments)\n \u003e \n \u003e At first, it\u0027s great to hear a new contributor is interested in\n \u003e adding a new backend to liberasurecode. Welcome! and Thanks!\n \u003e \n \u003e \n \u003e However, probably I didn\u0027t get about backend completely but it\n \u003e looks it requires to bite some of our common routines (e.g.\n \u003e preprocessing, helpers) via if branches.\n \u003e \n \u003e I added a few comments on that but not sure and need your help to\n \u003e understand *what change required* on your backend.\n \u003e \n \u003e e.g. memory allocation order? memory size?\n \u003e \n \u003e The original design for liberasurecode is providing common\n \u003e erasurecode api for the backends and *abstracts common functions*\n \u003e like allocate the necessary memory and free them after it works so\n \u003e that I\u0027d reduce *backend uniqueness* as possible from there.\n \u003e \n \u003e If we requires some pre/post processing for specific backend, maybe\n \u003e making a hook point somehwere may be a better solution... but\n \u003e anyway, I\u0027d know what\u0027s required to suggest something at first.\n \u003e \n \u003e Thanks!\n\nThank you Kota for your input!  We\u0027ll make your suggested changes.  However, we do need your help with 72 before resubmitting the updates.  Lastly, regarding memory allocation order, memory size.  It has to do with our encoding algorithm to address privacy.  It\u0027s very difficult to explain without going into the details.  Maybe we can take it offline if necessary.  Thanks for understanding!","accounts_in_message":[],"_revision_number":5},{"id":"699b362c061494c4a11c1fd1e5ef8c910377c478","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-01-31 19:27:55.000000000","message":"Patch Set 5:\n\n(2 comments)\n\nCouple more clarifications on Line 72 and 301.  Thanks Kota!","accounts_in_message":[],"_revision_number":5},{"id":"538d1065a5bd610f11df515672b36f08d95e9925","author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"date":"2017-02-01 09:24:28.000000000","message":"Patch Set 5:\n\n(1 comment)\n\nQuick response, sorry not much time to catch up all of your comments.\n\nHope it to help you. Thanks!","accounts_in_message":[],"_revision_number":5},{"id":"8b3986d84e6c54a11a10c251845397dfa2ad5f87","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-02-01 22:17:25.000000000","message":"Patch Set 5:\n\n(1 comment)\n\n\u003e (1 comment)\n \u003e \n \u003e Quick response, sorry not much time to catch up all of your\n \u003e comments.\n \u003e \n \u003e Hope it to help you. Thanks!\n\nThanks Kota for your suggestions/help!  Please see our response.  In addition, we\u0027ll need a day or so to come up with a proposed solution on how to handle a dynamic metadata_size.","accounts_in_message":[],"_revision_number":5},{"id":"a7b094ebd15ea1d909d2beaf4d5b577de8aa71e1","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-02-07 23:46:18.000000000","message":"Uploaded patch set 6.","accounts_in_message":[],"_revision_number":6},{"id":"6f6ed57ad3aebf6e83bb4d1a28f8d120cbfc92cc","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-02-07 23:49:51.000000000","message":"Patch Set 6: Verified+1\n\nBuild succeeded (check pipeline).\n\n- gate-liberasurecode-unit http://logs.openstack.org/53/424353/6/check/gate-liberasurecode-unit/8619035/ : SUCCESS in 3m 10s","accounts_in_message":[],"_revision_number":6},{"id":"9ccc09b51931250691369c506a74813207ea2e33","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-02-07 23:51:07.000000000","message":"Patch Set 5:\n\n(1 comment)\n\nKota, please see proposed changes.","accounts_in_message":[],"_revision_number":5},{"id":"63fb25cb015c6c351ae5ea4e5c604f17c9e80c80","author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"date":"2017-02-20 20:28:01.000000000","message":"Patch Set 6: Code-Review+1\n\n(4 comments)\n\nI think this is going to really good progress so far. I had some implementations to get this more clean [1]. Please make sure that, I think it could make this less code changes :D\n\n1: https://review.openstack.org/436174","accounts_in_message":[],"_revision_number":6},{"id":"dd89108ab87c0afc1b8e82f59f13f20dc0d1c3c3","author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"date":"2017-02-20 20:29:08.000000000","message":"Patch Set 6:\n\nEr, I still need to check if our third party works as well with dynamic metadata size :P (Not yet, will do in the next week)","accounts_in_message":[],"_revision_number":6},{"id":"d8d5ecb74e89ca3d81965b6316ec26dda99d354f","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-02-22 20:30:09.000000000","message":"Uploaded patch set 7.","accounts_in_message":[],"_revision_number":7},{"id":"2ebf1be64fefa60cbb16e6ff03e9945f9b492007","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-02-22 20:43:25.000000000","message":"Patch Set 7: Verified+1\n\nBuild succeeded (check pipeline).\n\n- gate-liberasurecode-unit http://logs.openstack.org/53/424353/7/check/gate-liberasurecode-unit/6ca5ae1/ : SUCCESS in 7m 20s","accounts_in_message":[],"_revision_number":7},{"id":"06d313fd2e3293efb358d8158b9c0f163b6cafd4","author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"date":"2017-02-24 08:10:26.000000000","message":"Patch Set 7:\n\n(11 comments)","accounts_in_message":[],"_revision_number":7},{"id":"27e1792a1a1be4e32e9fe645b5b73fb25993330b","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-02-24 22:14:14.000000000","message":"Patch Set 7:\n\n(7 comments)\n\n\u003e (11 comments)","accounts_in_message":[],"_revision_number":7},{"id":"5be4c955c3beb00ca027dd4684e1caaa8d6c1b0b","author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"date":"2017-02-27 04:16:45.000000000","message":"Patch Set 7: Code-Review-1\n\n(7 comments)\n\nNice vision Tim. I added small thoughts for you and for Jim.\nMy remaining concern to block from the merge is only at [1]. Others can be in follow up or another patch.\n\nAnd I confirmed current patch set with our backend works well, though I\u0027ve been looking at some valgrind failures with my backend but it looks not to be related to this because I can get that with the master, my laziness... :/\n\n1: https://review.openstack.org/#/c/424353/7/src/backends/phazrio/libphazr.c@272","accounts_in_message":[],"_revision_number":7},{"id":"0137d235934f2cf574c6e2453eb6ac8e6864182c","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-02-27 19:12:19.000000000","message":"Patch Set 7:\n\n(3 comments)\n\nWe\u0027ll submit the changes tomorrow.","accounts_in_message":[],"_revision_number":7},{"id":"ccb327e91390f1fee7ecd4a79c6067fde0397883","author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"date":"2017-02-27 19:57:10.000000000","message":"Patch Set 7:\n\n(3 comments)","accounts_in_message":[],"_revision_number":7},{"id":"0078543fe98a88535751f62a102c7ba630f039be","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-02-28 19:19:35.000000000","message":"Uploaded patch set 8.","accounts_in_message":[],"_revision_number":8},{"id":"89bf87f2a2bce7bcb4a990ef566d5cc6a3a06097","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-02-28 20:22:50.000000000","message":"Patch Set 8: Verified+1\n\nBuild succeeded (check pipeline).\n\n- gate-liberasurecode-unit http://logs.openstack.org/53/424353/8/check/gate-liberasurecode-unit/730db15/ : SUCCESS in 9m 00s","accounts_in_message":[],"_revision_number":8},{"id":"a8bc151fa8bbe109006d15984193a4381423c8c1","author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"date":"2017-02-28 21:55:44.000000000","message":"Patch Set 8: Code-Review+2\n\nI had a vague concern about freeing NULL pointers, but I guess that isn\u0027t really a concern anymore? http://stackoverflow.com/a/2360462 seems to indicate it isn\u0027t, and if you can\u0027t trust strangers on the internet, who *can* you trust?\n\nChange seems to make sense. You might want to rebase against current master and re-run test locally, since Kota fixed the valgrind check in https://review.openstack.org/#/c/434162/ to actually catch memory leaks. At this point, though, I\u0027m fairly certain that any such leak would have to be in libphazr itself, though, so I think we\u0027re good?","accounts_in_message":[],"_revision_number":8},{"id":"56e77674bf8b132ef547f8f341414cd61bec62fd","author":{"_account_id":4608,"name":"Kota Tsuyuzaki","email":"bloodeagle40234@gmail.com","username":"tsuyuzaki-kota"},"date":"2017-03-01 02:06:10.000000000","message":"Patch Set 8: Code-Review+2 Workflow+1\n\n(1 comment)\n\nThe code looks reasonable and I confirmed my backend also works.\n\nWith rebasing to the master, this still works well with no new memory leaks found so that +2 +A for this. Welcome Phazr.IO to liberasurecode world!","accounts_in_message":[],"_revision_number":8},{"id":"220b71640ce359ed0fac7d0050e3c877467dc0bf","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-03-01 02:06:20.000000000","message":"Patch Set 8: -Verified\n\nStarting gate jobs.\nhttp://status.openstack.org/zuul/","accounts_in_message":[],"_revision_number":8},{"id":"e9a5b47ba6fd76ef1460316e7fc506c7b60d4ce8","date":"2017-03-01 02:21:14.000000000","message":"Change has been successfully merged into the git repository by Jenkins","accounts_in_message":[],"_revision_number":8},{"id":"7714bb7bed81c0abd6a168cfd656d785382a1efd","author":{"_account_id":3,"name":"Jenkins","username":"jenkins"},"date":"2017-03-01 02:21:14.000000000","message":"Patch Set 8: Verified+2\n\nBuild succeeded (gate pipeline).\n\n- gate-liberasurecode-unit http://logs.openstack.org/53/424353/8/gate/gate-liberasurecode-unit/d9de69f/ : SUCCESS in 10m 18s","accounts_in_message":[],"_revision_number":8},{"id":"e0dc7e3a895e23609ebd7442dad2c965784199bd","author":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"date":"2017-03-01 04:03:42.000000000","message":"Patch Set 8:\n\nThank you so much Tim and Kota for all your hard work and great input!!!","accounts_in_message":[],"_revision_number":8}],"current_revision_number":8,"current_revision":"06e50ea86b6de729fa5dbc23ef41af87b19e636a","revisions":{"60112d84c3443fd5767f94b67df4b1e0edae84a0":{"kind":"REWORK","_number":1,"created":"2017-01-23 22:13:10.000000000","uploader":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"ref":"refs/changes/53/424353/1","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/liberasurecode","ref":"refs/changes/53/424353/1","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/1 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/1 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/1 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/1"}}},"commit":{"parents":[{"commit":"0794b31c623e4cede76d66be730719d24debcca9","subject":"Merge \"1.4.0 release\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/0794b31c623e4cede76d66be730719d24debcca9"}]}],"author":{"name":"Jim Cheung","email":"jim.cheung@phazr.io","date":"2017-01-23 21:55:24.000000000","tz":-480},"committer":{"name":"jimcheung","email":"jim.cheung@phazr.io","date":"2017-01-23 22:12:52.000000000","tz":-480},"subject":"Add Phazr.IO libphazr backend to liberasurecode","message":"Add Phazr.IO libphazr backend to liberasurecode\n\nChange-Id: I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/60112d84c3443fd5767f94b67df4b1e0edae84a0"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/60112d84c3443fd5767f94b67df4b1e0edae84a0"}]},"branch":"refs/heads/master"},"4c244e0dc1f98c009e5b64904f8c8b59dc014f33":{"kind":"NO_CODE_CHANGE","_number":2,"created":"2017-01-23 22:26:27.000000000","uploader":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"ref":"refs/changes/53/424353/2","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/liberasurecode","ref":"refs/changes/53/424353/2","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/2 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/2 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/2 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/2"}}},"commit":{"parents":[{"commit":"0794b31c623e4cede76d66be730719d24debcca9","subject":"Merge \"1.4.0 release\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/0794b31c623e4cede76d66be730719d24debcca9"}]}],"author":{"name":"Jim Cheung","email":"jim.cheung@phazr.io","date":"2017-01-23 21:55:24.000000000","tz":-480},"committer":{"name":"jimcheung","email":"jim.cheung@phazr.io","date":"2017-01-23 22:24:01.000000000","tz":-480},"subject":"Add Phazr.IO libphazr backend to liberasurecode","message":"Add Phazr.IO libphazr backend to liberasurecode\n\nCurrently, there are several implementations of erasure codes that are available within OpenStack Swift.  Most, if not all, of which are based on the Reed Solomon coding algorithm.\n\nPhazr.IO’s Erasure Coding technology uses a patented algorithm which are significantly more efficient and improves the speed of coding, decoding and reconstruction.  In addition, Phazr.IO Erasure Code use a non-systematic algorithm which provides data protection at rest and in transport without the need to use encryption.\n\nPlease contact support@phazr.io for more info on our technology.\n\nChange-Id: I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/4c244e0dc1f98c009e5b64904f8c8b59dc014f33"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/4c244e0dc1f98c009e5b64904f8c8b59dc014f33"}]},"branch":"refs/heads/master"},"7c338bd4c9524f449c1af9d4f55b08ad96e05c09":{"kind":"NO_CODE_CHANGE","_number":3,"created":"2017-01-23 22:28:24.000000000","uploader":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"ref":"refs/changes/53/424353/3","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/liberasurecode","ref":"refs/changes/53/424353/3","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/3 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/3 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/3 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/3"}}},"commit":{"parents":[{"commit":"0794b31c623e4cede76d66be730719d24debcca9","subject":"Merge \"1.4.0 release\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/0794b31c623e4cede76d66be730719d24debcca9"}]}],"author":{"name":"Jim Cheung","email":"jim.cheung@phazr.io","date":"2017-01-23 21:55:24.000000000","tz":-480},"committer":{"name":"jimcheung","email":"jim.cheung@phazr.io","date":"2017-01-23 22:26:49.000000000","tz":-480},"subject":"Add Phazr.IO libphazr backend to liberasurecode","message":"Add Phazr.IO libphazr backend to liberasurecode\n\nCurrently, there are several implementations of erasure codes that are\navailable within OpenStack Swift.  Most, if not all, of which are based\non the Reed Solomon coding algorithm.\n\nPhazr.IO’s Erasure Coding technology uses a patented algorithm which are\nsignificantly more efficient and improves the speed of coding, decoding\nand reconstruction.  In addition, Phazr.IO Erasure Code use a non-systematic\nalgorithm which provides data protection at rest and in transport without\nthe need to use encryption.\n\nPlease contact support@phazr.io for more info on our technology.\n\nChange-Id: I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/7c338bd4c9524f449c1af9d4f55b08ad96e05c09"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/7c338bd4c9524f449c1af9d4f55b08ad96e05c09"}]},"branch":"refs/heads/master"},"baa4532d50eb6a74bfe32c8e8573dac83893dfd7":{"kind":"REWORK","_number":4,"created":"2017-01-24 01:12:55.000000000","uploader":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"ref":"refs/changes/53/424353/4","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/liberasurecode","ref":"refs/changes/53/424353/4","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/4 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/4 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/4 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/4"}}},"commit":{"parents":[{"commit":"0794b31c623e4cede76d66be730719d24debcca9","subject":"Merge \"1.4.0 release\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/0794b31c623e4cede76d66be730719d24debcca9"}]}],"author":{"name":"Jim Cheung","email":"jim.cheung@phazr.io","date":"2017-01-23 21:55:24.000000000","tz":-480},"committer":{"name":"jimcheung","email":"jim.cheung@phazr.io","date":"2017-01-24 01:09:19.000000000","tz":-480},"subject":"Add Phazr.IO libphazr backend to liberasurecode","message":"Add Phazr.IO libphazr backend to liberasurecode\n\nCurrently, there are several implementations of erasure codes that are\navailable within OpenStack Swift.  Most, if not all, of which are based\non the Reed Solomon coding algorithm.\n\nPhazr.IO’s Erasure Coding technology uses a patented algorithm which are\nsignificantly more efficient and improves the speed of coding, decoding\nand reconstruction.  In addition, Phazr.IO Erasure Code use a non-systematic\nalgorithm which provides data protection at rest and in transport without\nthe need to use encryption.\n\nPlease contact support@phazr.io for more info on our technology.\n\nChange-Id: I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/baa4532d50eb6a74bfe32c8e8573dac83893dfd7"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/baa4532d50eb6a74bfe32c8e8573dac83893dfd7"}]},"branch":"refs/heads/master"},"f5d81d73a3644edd0db801784ea7d1b94d2fe294":{"kind":"REWORK","_number":5,"created":"2017-01-24 01:23:57.000000000","uploader":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"ref":"refs/changes/53/424353/5","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/liberasurecode","ref":"refs/changes/53/424353/5","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/5 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/5 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/5 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/5"}}},"commit":{"parents":[{"commit":"0794b31c623e4cede76d66be730719d24debcca9","subject":"Merge \"1.4.0 release\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/0794b31c623e4cede76d66be730719d24debcca9"}]}],"author":{"name":"Jim Cheung","email":"jim.cheung@phazr.io","date":"2017-01-23 21:55:24.000000000","tz":-480},"committer":{"name":"jimcheung","email":"jim.cheung@phazr.io","date":"2017-01-24 01:23:36.000000000","tz":-480},"subject":"Add Phazr.IO libphazr backend to liberasurecode","message":"Add Phazr.IO libphazr backend to liberasurecode\n\nCurrently, there are several implementations of erasure codes that are\navailable within OpenStack Swift.  Most, if not all, of which are based\non the Reed Solomon coding algorithm.\n\nPhazr.IO’s Erasure Coding technology uses a patented algorithm which are\nsignificantly more efficient and improves the speed of coding, decoding\nand reconstruction.  In addition, Phazr.IO Erasure Code use a non-systematic\nalgorithm which provides data protection at rest and in transport without\nthe need to use encryption.\n\nPlease contact support@phazr.io for more info on our technology.\n\nChange-Id: I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/f5d81d73a3644edd0db801784ea7d1b94d2fe294"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/f5d81d73a3644edd0db801784ea7d1b94d2fe294"}]},"branch":"refs/heads/master"},"ba4e66a6e4008c1ba1cdce971f22f4d4b4c51fcc":{"kind":"REWORK","_number":6,"created":"2017-02-07 23:46:18.000000000","uploader":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"ref":"refs/changes/53/424353/6","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/liberasurecode","ref":"refs/changes/53/424353/6","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/6 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/6 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/6 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/6"}}},"commit":{"parents":[{"commit":"0794b31c623e4cede76d66be730719d24debcca9","subject":"Merge \"1.4.0 release\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/0794b31c623e4cede76d66be730719d24debcca9"}]}],"author":{"name":"Jim Cheung","email":"jim.cheung@phazr.io","date":"2017-01-23 21:55:24.000000000","tz":-480},"committer":{"name":"jimcheung","email":"jim.cheung@phazr.io","date":"2017-02-07 23:27:33.000000000","tz":-480},"subject":"Add Phazr.IO libphazr backend to liberasurecode","message":"Add Phazr.IO libphazr backend to liberasurecode\n\nCurrently, there are several implementations of erasure codes that are\navailable within OpenStack Swift.  Most, if not all, of which are based\non the Reed Solomon coding algorithm.\n\nPhazr.IO’s Erasure Coding technology uses a patented algorithm which are\nsignificantly more efficient and improves the speed of coding, decoding\nand reconstruction.  In addition, Phazr.IO Erasure Code use a non-systematic\nalgorithm which provides data protection at rest and in transport without\nthe need to use encryption.\n\nPlease contact support@phazr.io for more info on our technology.\n\nChange-Id: I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/ba4e66a6e4008c1ba1cdce971f22f4d4b4c51fcc"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/ba4e66a6e4008c1ba1cdce971f22f4d4b4c51fcc"}]},"branch":"refs/heads/master"},"91cdc6238807f25d804e435231c49f0de770249e":{"kind":"REWORK","_number":7,"created":"2017-02-22 20:30:09.000000000","uploader":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"ref":"refs/changes/53/424353/7","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/liberasurecode","ref":"refs/changes/53/424353/7","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/7 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/7 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/7 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/7"}}},"commit":{"parents":[{"commit":"0794b31c623e4cede76d66be730719d24debcca9","subject":"Merge \"1.4.0 release\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/0794b31c623e4cede76d66be730719d24debcca9"}]}],"author":{"name":"Jim Cheung","email":"jim.cheung@phazr.io","date":"2017-01-23 21:55:24.000000000","tz":-480},"committer":{"name":"jimcheung","email":"jim.cheung@phazr.io","date":"2017-02-22 20:06:06.000000000","tz":-480},"subject":"Add Phazr.IO libphazr backend to liberasurecode","message":"Add Phazr.IO libphazr backend to liberasurecode\n\nCurrently, there are several implementations of erasure codes that are\navailable within OpenStack Swift.  Most, if not all, of which are based\non the Reed Solomon coding algorithm.\n\nPhazr.IO’s Erasure Coding technology uses a patented algorithm which are\nsignificantly more efficient and improves the speed of coding, decoding\nand reconstruction.  In addition, Phazr.IO Erasure Code use a non-systematic\nalgorithm which provides data protection at rest and in transport without\nthe need to use encryption.\n\nPlease contact support@phazr.io for more info on our technology.\n\nChange-Id: I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/91cdc6238807f25d804e435231c49f0de770249e"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/91cdc6238807f25d804e435231c49f0de770249e"}]},"branch":"refs/heads/master"},"06e50ea86b6de729fa5dbc23ef41af87b19e636a":{"kind":"REWORK","_number":8,"created":"2017-02-28 19:19:35.000000000","uploader":{"_account_id":24559,"name":"Jim Cheung","email":"jim.cheung@phazr.io","username":"jimcheung"},"ref":"refs/changes/53/424353/8","fetch":{"anonymous http":{"url":"https://review.opendev.org/openstack/liberasurecode","ref":"refs/changes/53/424353/8","commands":{"Checkout":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/8 \u0026\u0026 git checkout FETCH_HEAD","Cherry Pick":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/8 \u0026\u0026 git cherry-pick FETCH_HEAD","Format Patch":"git fetch https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/8 \u0026\u0026 git format-patch -1 --stdout FETCH_HEAD","Pull":"git pull https://review.opendev.org/openstack/liberasurecode refs/changes/53/424353/8"}}},"commit":{"parents":[{"commit":"0794b31c623e4cede76d66be730719d24debcca9","subject":"Merge \"1.4.0 release\"","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/0794b31c623e4cede76d66be730719d24debcca9"}]}],"author":{"name":"Jim Cheung","email":"jim.cheung@phazr.io","date":"2017-01-23 21:55:24.000000000","tz":-480},"committer":{"name":"jimcheung","email":"jim.cheung@phazr.io","date":"2017-02-28 19:14:11.000000000","tz":-480},"subject":"Add Phazr.IO libphazr backend to liberasurecode","message":"Add Phazr.IO libphazr backend to liberasurecode\n\nCurrently, there are several implementations of erasure codes that are\navailable within OpenStack Swift.  Most, if not all, of which are based\non the Reed Solomon coding algorithm.\n\nPhazr.IO’s Erasure Coding technology uses a patented algorithm which are\nsignificantly more efficient and improves the speed of coding, decoding\nand reconstruction.  In addition, Phazr.IO Erasure Code use a non-systematic\nalgorithm which provides data protection at rest and in transport without\nthe need to use encryption.\n\nPlease contact support@phazr.io for more info on our technology.\n\nChange-Id: I4e40d02a8951e38409ad3c604c5dd6f050fa7ea0\n","web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/06e50ea86b6de729fa5dbc23ef41af87b19e636a"}],"resolve_conflicts_web_links":[{"name":"gitea","tooltip":"Open in GitWeb","url":"https://opendev.org/openstack/liberasurecode/commit/06e50ea86b6de729fa5dbc23ef41af87b19e636a"}]},"branch":"refs/heads/master"}},"requirements":[],"submit_records":[],"submit_requirements":[]}