search

hyperledger-bevel / bevel

An automation framework for rapidly and consistently deploying production-ready DLT platforms
https://hyperledger-bevel.readthedocs.io/en/latest/
Apache License 2.0
347 stars 720 forks source link

Privacy flags are missing from besu charts. #903

Closed lakshyakumar closed 4 years ago

lakshyakumar commented 4 years ago

Describe the bug Beus binary is invoked without the --privacy flags, in the Besu node_orion chart. The flags --privacy-enabled=true --privacy-url=<json-rpc url> --privacy-public-key-file=<orion nodekey.pub file path> should be added to the command. The network should be tested after adding the privacy flags. The chart should be checked for additional missing flags if exists.

Additional context https://github.com/PegaSysEng/besu-kubernetes/blob/master/helm/ibft2-with-privacy/besu/templates/node2privacy-statefulset.yaml

lakshyakumar commented 4 years ago

able to deploy the sample smartcontract on besu network without tls after adding the missing flags to the chart.

describe transaction for supplychain deployment blockinfo
lakshyakumar commented 4 years ago

While trying to deploy the contract on besu network with orion tls on getting the error.

ErrorCommunicatingWithEnclave

The code is able to connect to the JSON-RPC port of the node and create the eth_account using the web3.js library.

lakshyakumar commented 4 years ago

The communication with enclave can be setup once the besu nodes are also communicating and setup using the tls. So the next story can be setting up tls for besu. https://besu.hyperledger.org/en/stable/Concepts/TLS/