runtime: support unix domain socket

[daixiang0]

Signed-off-by: Long long0dai@foxmail.com

Description

Support unix domain socket.

Issue reference

Please reference the issue this PR will close: #2864

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Unit tests passing
• End-to-end tests passing
• Extended the documentation / Created issue in the Describe the use of unix sockets, the CLI commands and usage example.md docs#1730
• Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
• Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

[daixiang0]

after build:

1. run with hello-world example in quick-start
daprd --app-id nodeapp --app-protocol http --components-path /root/.dapr/components --metrics-port 39497 --dapr-http-max-request-size -1 --app-port 3000 --placement-host-address localhost:50005 --config /root/.dapr/config.yaml --enable-domain-socket
2. test
   curl --unix-socket /tmp/nodeapp-http.socket http://unix/v1.0/state/statestore/order

[yaron2]

I'm really happy to see this PR landing. Notice tests are failing.

[codecov]

Codecov Report

Merging #3529 (90c855a) into master (a30488d) will decrease coverage by 0.14%.
The diff coverage is 9.09%.

@@            Coverage Diff             @@
##           master    #3529      +/-   ##
==========================================
- Coverage   60.51%   60.37%   -0.15%     
==========================================
  Files          97       97              
  Lines        8760     8784      +24     
==========================================
+ Hits         5301     5303       +2     
- Misses       3070     3092      +22     
  Partials      389      389              

Impacted Files	Coverage Δ
pkg/channel/http/http_channel.go	67.02% <ø> (ø)
pkg/grpc/server.go	17.60% <0.00%> (-1.21%)	⬇️
pkg/http/config.go	0.00% <0.00%> (ø)
pkg/http/server.go	55.20% <0.00%> (-1.79%)	⬇️
pkg/runtime/cli.go	4.41% <0.00%> (-0.04%)	⬇️
pkg/runtime/runtime.go	53.82% <0.00%> (-0.47%)	⬇️
pkg/grpc/config.go	100.00% <100.00%> (ø)
pkg/runtime/config.go	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1f9adee...90c855a. Read the comment docs.

[daixiang0]

@yaron2 @artursouza not sure is it necessary for all e2e tests, so no e2e tests for now, please review codes first, thanks.

[artursouza]

LGTM overall. This would need changes in the CLI, docs and SDKs too.

[daixiang0]

@artursouza I think CLI changes need to wait this merged if there is any e2e based on daprd, docs changes as well, SDK is the last step while I do not familiar with other languages, I will create issues to track it.

[daixiang0]

sorry for force push since flaky tests, if there is a better way to re-run tests, please tell me, thanks.

[greenie-msft]

@artursouza, should this be included in the 1.4 milestone?

[artursouza]

@artursouza, should this be included in the 1.4 milestone?

I prefer to add community contributions to the milestone when they get merged.

[artursouza]

Please, create tracking issues in CLI and SDKs.

[artursouza]

@yaron2 @greenie-msft @orizohar For this feature to be announced, we would need to have support in at least CLI and one SDK.

[yaron2]

@yaron2 @greenie-msft @orizohar For this feature to be announced, we would need to have support in at least CLI and one SDK.

Ok, but why? For example, cant users directly call via the socket if using their own gRPC client?

[artursouza]

@yaron2 @greenie-msft @orizohar For this feature to be announced, we would need to have support in at least CLI and one SDK.

Ok, but why? For example, cant users directly call via the socket if using their own gRPC client?

Yes, but we should make it a first class feature with flags from CLI and config in the SDKs. Otherwise, people might not use it.

[yaron2]

@yaron2 @greenie-msft @orizohar For this feature to be announced, we would need to have support in at least CLI and one SDK.

Ok, but why? For example, cant users directly call via the socket if using their own gRPC client?

Yes, but we should make it a first class feature with flags from CLI and config in the SDKs. Otherwise, people might not use it.

Ok, just making sure there isn't some special config that needs to be done for this, and that regular gRPC/HTTP clients can use this.