159 node information

[andy-shi88]

Description

Open endpoint to fetch node information such as cpu, ram, and storage usages.

Breakdown

• Open get node information bidirectional stream endpoint handler
• Create simple authentication method
• Open proxy endpoint and initiate minimal postman.collection
• Move every interceptor from /common/util to common/interceptor
• Authenticate user using authorization header (which is a hex string representation of signed data [requestType+timestamp] *will explain more in wiki later)

Reference Issue

Close #159

Step to Test (optional)

• go test ./...
• run the server
• run client script in GetNodeHardware/client.go
  http proxy : POSTMAN
• run server
• import the postman collection, adjust your environment host value to match the port in your resource/config.toml:apiHTTPPort

note:

• some part of the code can't be mocked (the gopsutil library usage), sorry bout that.

[andy-shi88]

The only thing is whether we need to add this endpoint as stream or normal rpc endpoint, if it's stream then every request in the stream, they'll need to generate the Auth object.

[sukrawidhyawan]

no need to use blocker package?

[andy-shi88]

yes, will do

[capt4ce]

How do we treat the functionality when the owner of a node is changed? do we need to restart the node? @andy-shi88

[andy-shi88]

How do we treat the functionality when the owner of a node is changed? do we need to restart the node? @andy-shi88

true right now we'll need to restart the whole application, since it only read the owner from config file in the start up. This should follow however the claim node transaction type work. I'll add some todo comment for this.

[andy-shi88]

WIP: moving auth checking to interceptor as suggested by @astaphobia

[andy-shi88]

ready for re-review