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
@@ -31,9 +28,18 @@ Hyperledger Bevel delivers an automation framework for rapidly and consistently
31
28
32
29

33
30
34
-
Hyperledger Bevel makes use of Ansible, Helm, and Kubernetes to deploy production DLT networks. Specifically, it makes use of Ansible for configuration of the network by DevOps Engineers. It then uses Helm charts as instructions for deploying the necessary components to Kubernetes. Kubernetes was chosen to allow for Hyperledger Bevel to deploy the DLT networks to any cloud that supports Kubernetes.
31
+
Hyperledger Bevel is an accelerator/tool that helps developers rapidly set up and deploy secure, scalable and production-ready DLT network(s) that also allows new organizations to be easily on-boarded on the network. Bevel facilitates a safe and secure way of deploying and operating different DLT platforms.
35
32
36
-
Hyperledger Bevel currently supports Corda, Hyperledger Fabric, Hyperledger Indy and Quorum. It is the intention to add support for Hyperledger Besu and Corda Enterprise in the near future. Other DLT platforms can easily be added.
33
+
It includes:
34
+
- Helm charts to deploy different DLT nodes and to generate the related crypto/identities.
35
+
- Helm charts for various operational features like adding new nodes, and deploying smart contracts.
36
+
- Helm charts to deploy Hyperledger Cacti connectors for Fabric, Quorum and Besu networks.
37
+
- Ansible playbooks and modular role definitions to automate the deployment of Helm charts.
38
+
- Ansible playbooks and roles to automated deployment of Hyperledger fabric using bevel-operator-fabric(Kubernetes operator for managing Hyperledger Fabric networks).
39
+
- Integrated CD using GitOps so that once the network is set up, all changes can be done via git PRs/merges.
40
+
- Configuration for Ambassador Edge Stack, HAProxy (for Hyperledger Fabric) and Isto Ingress (for Substrate) to act as Ingress Controller.
41
+
42
+
Hyperledger Bevel currently supports R3 Corda OS and Enterprise, Hyperledger Fabric, Hyperledger Indy, Hyperledger Besu, Quorum and Substrate. Other DLT platforms can easily be added.
37
43
38
44
### Getting Started
39
45
@@ -64,7 +70,7 @@ For Hyperledger Indy, we build Docker containers from our source code. A number
64
70

65
71
66
72
### Quorum
67
-
For Quorum, we use the official Docker containers provided by Quorum. A number of different Ansible scripts will allow you to either create a new network (across clouds) with choice of Consensus (between IBFT and RAFT) and a choice of Transaction Manager (between Tessera and Constellation).
73
+
For Quorum, we use the official Docker containers provided by Quorum. A number of different Ansible scripts will allow you to either create a new network (across clouds) with choice of Consensus (between IBFT and RAFT) and a transaction Manager.
68
74
69
75

70
76
@@ -85,10 +91,10 @@ Please review [contributing](./CONTRIBUTING.md) guidelines to get started.
85
91
If you are not using the provided Jenkins automation scripts, you can run the provisioning scripts within a docker runtime independent from your target Kubernetes cluster.
86
92
```
87
93
# Build provisioning image
88
-
docker build . -t hyperledgerlabs/baf-build
94
+
docker build . -t ghcr.io/hyperledger/bevel-build
89
95
90
96
# Run the provisioning scripts
91
-
docker run -it -v $(pwd):/home/bevel/ hyperledgerlabs/baf-build
97
+
docker run -it -v $(pwd):/home/bevel/ ghcr.io/hyperledger/bevel-build
92
98
```
93
99
94
100
## Initial Committers
@@ -99,28 +105,3 @@ docker run -it -v $(pwd):/home/bevel/ hyperledgerlabs/baf-build
0 commit comments