yoshiyuki.kanno

@Argentum88 Sorry for the late reply. Originally @yosukehara project lead should answer your question but he seems busy so I'd like to answer instead of him. Now he and other...

> @yosukehara @mocchira could you tell when you plan to return to the development of LeoFS? @wulfgar93 The situation I've been in is almost same as @yosukehara. I'm not sure...

One possible solution would returning the error with more detail like the number of write accepted. As for write after error, depending on the use case, when 1 accepted, a...

@Kirsun25 If I understand your question correctly, there are no mechanisms for **auto-duplicating a file to third alive storage** (I think this is the feature called **Hinted Hand Off**) on...

IMO sounds good. So if we go with this proposal, how to handle|manage ip and subnet masks is the point. (now we have no persistent ip related information at all....

@yosukehara if the purpose is to make it easy to use leofs then would a all-in-one image with getting all of the components up at startup and leo_gateway port opened...

@yosukehara got it. Replacing ``` make -j4 ``` with ``` make -j"$(nproc)" ``` would be good as it automatically scale with # of cores a builder have. any others LGTM.

+1 looks reasonable to me.

@windkit yes generalizing parallelism into framework is the best if possible but ironically getting parallelism right(pull the maximum performance) may be difficult on high level languages with built-in GC|Concurrency support...

As part of the article get deprecated, for which we should reference 4.3 Specifying SSL Options on ["Using SSL for Erlang Distribution"](http://erlang.org/doc/apps/ssl/ssl_distribution.html) instead.