You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/source/guides/besu/add-new-member-org.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ This guide explains how to add a new validator node to an existing organization
27
27
28
28
1.**Update network.yaml file**
29
29
30
-
Refer [this guide](../networkyaml-besu.md) for details on editing the configuration file.
30
+
Make sure that the genesis file is provided in base64 encoding. Also, if you are adding node to the same cluster as of another node, make sure that you add the ambassador ports of the existing node present in the cluster to the network.yaml
31
31
32
32
The `network.yaml` file should contain the specific `network.organization` details along with the enode information, genesis file in base64 encoding and tessera transaction manager details
Copy file name to clipboardExpand all lines: docs/source/guides/besu/add-new-validator-node.md
+19-2
Original file line number
Diff line number
Diff line change
@@ -17,8 +17,25 @@ This guide explains how to add a new validator node to an existing organization
17
17
18
18
To add a new node in Besu, an existing besu network should be running, enode information of all existing nodes present in the network should be available, genesis file should be available in base64 encoding and the information of transaction manager nodes and existing validator nodes should be available. The new node account should be unlocked prior adding the new node to the existing besu network.
19
19
20
-
---
21
-
**NOTE**: Addition of a new validator node has been tested on an existing network which is created by Bevel. Networks created using other methods may be suitable but this has not been tested by Bevel team.
20
+
The `network.yaml` file should contain the specific `network.organization` details along with the tessera transaction manager node details and existing validator and member node details.
21
+
22
+
---
23
+
**NOTE**: Make sure that the genesis file is provided in base64 encoding. Also, if you are adding node to the same cluster as of another node, make sure that you add the ambassador ports of the existing node present in the cluster to the network.yaml
24
+
25
+
---
26
+
For reference, sample `network-besu-new-validatornode.yaml` file [here](https://github.com/hyperledger/bevel/blob/main/platforms/hyperledger-besu/configuration/samples/network-besu-new-validatornode.yaml)
Copy file name to clipboardExpand all lines: docs/source/guides/besu/add-new-validator-org.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Refer [this guide](../networkyaml-besu.md) for details on editing the configurat
27
27
The `network.yaml` file should contain the specific `network.organization` details along with the transaction manager node details and existing validator and member node details.
28
28
29
29
---
30
-
**NOTE**: Make sure that the genesis flie is provided in base64 encoding. Also, if you are adding node to the same cluster as of another node, make sure that you add the ambassador ports of the existing node present in the cluster to the network.yaml
30
+
**NOTE**: Make sure that the genesis file is provided in base64 encoding. Also, if you are adding node to the same cluster as of another node, make sure that you add the ambassador ports of the existing node present in the cluster to the network.yaml
31
31
32
32
---
33
33
For reference, sample `network-besu-new-validatororg.yaml` file [here](https://github.com/hyperledger/bevel/blob/main/platforms/hyperledger-besu/configuration/samples/network-besu-new-validatororg.yaml)
Copy file name to clipboardExpand all lines: docs/source/guides/networkyaml-besu.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Although, the file itself has comments for each key-value, here is a more detail
39
39
The sections in the sample configuration file are
40
40
<aname="type"></a>
41
41
type
42
-
: `type` defines the platform choice like corda/fabric/indy/quorum/besu, here in the example its**besu**.
42
+
: `type` defines the platform choice like corda/fabric/indy/quorum/besu, here in the example it's**besu**.
43
43
44
44
<aname="version"></a>
45
45
version
@@ -55,7 +55,7 @@ permissioning
55
55
56
56
<aname="env"></a>
57
57
env
58
-
: `env` section contains the environment type and additional (other than 443) Ambassador port configuration. Vaule for proxy field under this section can be 'ambassador' as 'haproxy' has not been implemented for Besu.
58
+
: `env` section contains the environment type and additional (other than 443) Ambassador port configuration. Value for proxy field under this section can be 'ambassador' as 'haproxy' has not been implemented for Besu.
59
59
60
60
The snippet of the `env` section with example value is below
61
61
@@ -70,7 +70,7 @@ The fields under `env` section are
70
70
| type | Environment type. Can be like dev/test/prod.|
71
71
| proxy | Choice of the Cluster Ingress controller. Currently supports 'ambassador' only as 'haproxy' has not been implemented for Hyperledger Besu |
72
72
| ambassadorPorts | Any additional Ambassador ports can be given here. This is only valid if `proxy: ambassador`. These ports are enabled per cluster, so if you have multiple clusters you do not need so many ports to be opened on Ambassador. Our sample uses a single cluster, so we have to open 4 ports for each Node. These ports are again specified in the `organization` section. |
73
-
| loadBalancerSourceRanges | (Optional) Restrict inbound access to a single or list of IP adresses for the public Ambassador ports to enhance Bevel network security. This is only valid if `proxy: ambassador`. |
73
+
| loadBalancerSourceRanges | (Optional) Restrict inbound access to a single or list of IP addresses for the public Ambassador ports to enhance Bevel network security. This is only valid if `proxy: ambassador`. |
74
74
| retry_count | Retry count for the checks. Use a high number if your cluster is slow. |
75
75
|external_dns | If the cluster has the external DNS service, this has to be set `enabled` so that the hosted zone is automatically updated. |
76
76
| namespace | (Optional) K8s Namespace on which proxy will be installed. Default value is `default`|
@@ -206,7 +206,7 @@ The fields under `peer` service are
206
206
| tm_nodeport.ambassador | The tm port when exposed on ambassador service. |
207
207
| tm_clientport.port | Client Port used by Transaction manager `tessera`. This is the port where Besu nodes connect to their respective transaction manager. |
208
208
209
-
The peer in an organization with type as `member` can be used to deploy the smarcontracts with additional field `peer.smart_contract`. The snapshot of peers service with example values is below
209
+
The peer in an organization with type as `member` can be used to deploy the smartcontracts with additional field `peer.smart_contract`. The snapshot of peers service with example values is below
210
210
```yaml
211
211
peers:
212
212
- peer:
@@ -246,7 +246,7 @@ The additional fields under `peer` service are
246
246
| smart_contract.contract_path | Path of the smart contract folder relative to deployjs_path |
247
247
| smart_contract.iterations | Number of Iteration of executions for which the gas and the code is optimised |
248
248
| smart_contract.entrypoint | Main entrypoint solidity file of the smart contract |
249
-
| smart_contract.private_for | Comma seperated string of `tessera` Public keys for the `privateFor` |
249
+
| smart_contract.private_for | Comma separated string of `tessera` Public keys for the `privateFor` |
250
250
251
251
Each organization with type as `validator` will have a validator service. The snippet of validator service with example values is below
| attribute | key value pair for the different attributes supported in Fabric, details about the attribues are [here](https://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control)|
276
+
| attribute | key value pair for the different attributes supported in Fabric, details about the attributes are [here](https://hyperledger-fabric-ca.readthedocs.io/en/latest/users-guide.html#attribute-based-access-control)|
277
277
278
278
279
279
The services field for each organization under `organizations` section of Fabric contains list of `services` which could be ca/orderers/consensus/peers based on if the type of organization.
@@ -341,7 +341,7 @@ The chaincodes section contains the list of chaincode for the peer, the fields u
341
341
| image | Mandatory for external_chaincode, the container from docker registry applicable for this chaincode. For private registry, ensure password is passed in `network.docker` section |
342
342
| crypto_mount_path | Required only when `tls: true`, the path where the crypto materials will be stored |
343
343
344
-
The organization with orderer type will have concensus service. The snapshot of consensus service with example values is below
344
+
The organization with orderer type will have consensus service. The snapshot of consensus service with example values is below
Copy file name to clipboardExpand all lines: docs/source/guides/networkyaml-quorum.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ The sections in the sample configuration file are
41
41
42
42
<aname="type"></a>
43
43
type
44
-
: `type` defines the platform choice like corda/fabric/indy/quorum, here in the example its**quorum**.
44
+
: `type` defines the platform choice like corda/fabric/indy/quorum, here in the example it's**quorum**.
45
45
46
46
<aname="version"></a>
47
47
version
@@ -53,7 +53,7 @@ version
53
53
54
54
<aname="env"></a>
55
55
env
56
-
: `env` section contains the environment type and additional (other than 443) Ambassador port configuration. Vaule for proxy field under this section can be 'ambassador' or 'haproxy'
56
+
: `env` section contains the environment type and additional (other than 443) Ambassador port configuration. Value for proxy field under this section can be 'ambassador' or 'haproxy'
57
57
58
58
The snippet of the `env` section with example value is below
59
59
@@ -68,7 +68,7 @@ The fields under `env` section are
68
68
| type | Environment type. Can be like dev/test/prod.|
69
69
| proxy | Choice of the Cluster Ingress controller. Currently supports 'ambassador' only as 'haproxy' has not been implemented for Quorum |
70
70
| ambassadorPorts | Any additional Ambassador ports can be given here. This is only valid if `proxy: ambassador`. These ports are enabled per cluster, so if you have multiple clusters you do not need so many ports to be opened on Ambassador. Our sample uses a single cluster, so we have to open 4 ports for each Node. These ports are again specified in the `organization` section. |
71
-
| loadBalancerSourceRanges | Restrict inbound access to a single or list of IP adresses for the public Ambassador ports to enhance Bevel network security. This is only valid if `proxy: ambassador`. |
71
+
| loadBalancerSourceRanges | Restrict inbound access to a single or list of IP addresses for the public Ambassador ports to enhance Bevel network security. This is only valid if `proxy: ambassador`. |
72
72
| retry_count | Retry count for the checks. Use a high number if your cluster is slow. |
73
73
|external_dns | If the cluster has the external DNS service, this has to be set `enabled` so that the hosted zone is automatically updated. |
74
74
@@ -136,7 +136,7 @@ Each `organization` under the `organizations` section has the following fields.
136
136
| k8s | Kubernetes cluster deployment variables.|
137
137
| vault | Contains Hashicorp Vault server address and root-token in the example |
138
138
| gitops | Git Repo details which will be used by GitOps/Flux. |
139
-
| services | Contains list of services which could ca/peer/orderers/concensus based on the type of organization |
139
+
| services | Contains list of services which could ca/peer/orderers/consensus based on the type of organization |
140
140
141
141
For the `aws``vault` and `k8s` field the snippet with sample values is below
0 commit comments