Skip to content

Commit 7eba1e1

Browse files
update readme
Signed-off-by: suvajit-sarkar <[email protected]>
1 parent da17321 commit 7eba1e1

File tree

3 files changed

+15
-34
lines changed

3 files changed

+15
-34
lines changed

README.md

+14-33
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,4 @@
11
# Hyperledger Bevel [![join the chat][chat-image]][chat-url]
2-
<!-- ALL-CONTRIBUTORS-BADGE:START - Do not remove or modify this section -->
3-
[![All Contributors](https://img.shields.io/badge/all_contributors-6-orange.svg?style=flat-square)](#contributors-)
4-
<!-- ALL-CONTRIBUTORS-BADGE:END -->
52

63
[chat-url]: https://discord.gg/hyperledger
74
[chat-image]: https://img.shields.io/discord/905194001349627914?logo=Hyperledger&style=plastic.svg
@@ -31,9 +28,18 @@ Hyperledger Bevel delivers an automation framework for rapidly and consistently
3128

3229
![What is Hyperledger Bevel?](./docs/images/hyperledger-bevel-overview.png "What is Hyperledger Bevel?")
3330

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.
3532

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.
3743

3844
### Getting Started
3945

@@ -64,7 +70,7 @@ For Hyperledger Indy, we build Docker containers from our source code. A number
6470
![Hyperledger Bevel - Indy](./docs/images/hyperledger-bevel-indy.png "Hyperledger Bevel for Hyperledger Indy")
6571

6672
### 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.
6874

6975
![Hyperledger Bevel - Quorum](./docs/images/hyperledger-bevel-quorum.png "Hyperledger Bevel for Quorum")
7076

@@ -85,10 +91,10 @@ Please review [contributing](./CONTRIBUTING.md) guidelines to get started.
8591
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.
8692
```
8793
# Build provisioning image
88-
docker build . -t hyperledgerlabs/baf-build
94+
docker build . -t ghcr.io/hyperledger/bevel-build
8995
9096
# 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
9298
```
9399

94100
## Initial Committers
@@ -99,28 +105,3 @@ docker run -it -v $(pwd):/home/bevel/ hyperledgerlabs/baf-build
99105

100106
## Sponsor
101107
Mark Wagner (Github: [n1zyz](https://github.com/n1zyz), email: [[email protected]](mailto:[email protected])) - TSC Member
102-
103-
## Contributors ✨
104-
105-
Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/docs/en/emoji-key)):
106-
107-
<!-- ALL-CONTRIBUTORS-LIST:START - Do not remove or modify this section -->
108-
<!-- prettier-ignore-start -->
109-
<!-- markdownlint-disable -->
110-
<table>
111-
<tr>
112-
<td align="center"><a href="https://github.com/alvaropicazo"><img src="https://avatars.githubusercontent.com/u/76157062?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Alvaro Picazo</b></sub></a><br /><a href="#maintenance-alvaropicazo" title="Maintenance">🚧</a></td>
113-
<td align="center"><a href="https://github.com/suvajit-sarkar"><img src="https://avatars.githubusercontent.com/u/55580532?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Suvajit Sarkar</b></sub></a><br /><a href="https://github.com/hyperledger/bevel/commits?author=suvajit-sarkar" title="Code">💻</a> <a href="https://github.com/hyperledger/bevel/commits?author=suvajit-sarkar" title="Documentation">📖</a></td>
114-
<td align="center"><a href="https://github.com/deepakkumardbd"><img src="https://avatars.githubusercontent.com/u/57094817?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Deepak Kumar</b></sub></a><br /><a href="https://github.com/hyperledger/bevel/commits?author=deepakkumardbd" title="Code">💻</a></td>
115-
<td align="center"><a href="https://github.com/jagpreetsinghsasan"><img src="https://avatars.githubusercontent.com/u/56861721?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Jagpreet Singh Sasan</b></sub></a><br /><a href="https://github.com/hyperledger/bevel/commits?author=jagpreetsinghsasan" title="Code">💻</a> <a href="#maintenance-jagpreetsinghsasan" title="Maintenance">🚧</a></td>
116-
<td align="center"><a href="https://github.com/angelaalagbe"><img src="https://avatars.githubusercontent.com/u/54588164?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Angela.Alagbe</b></sub></a><br /><a href="https://github.com/hyperledger/bevel/commits?author=angelaalagbe" title="Documentation">📖</a> <a href="#content-angelaalagbe" title="Content">🖋</a></td>
117-
<td align="center"><a href="https://github.com/mgCepeda"><img src="https://avatars.githubusercontent.com/u/83813093?v=4?s=100" width="100px;" alt=""/><br /><sub><b>Marina Gómez Cepeda</b></sub></a><br /><a href="https://github.com/hyperledger/bevel/commits?author=mgCepeda" title="Code">💻</a></td>
118-
</tr>
119-
</table>
120-
121-
<!-- markdownlint-restore -->
122-
<!-- prettier-ignore-end -->
123-
124-
<!-- ALL-CONTRIBUTORS-LIST:END -->
125-
126-
This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!
28.3 KB
Loading

platforms/hyperledger-besu/charts/besu-cacti-connector/Chart.yaml

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
apiVersion: v2
2-
name: besu_connector
2+
name: besu-cacti-connector
33
description: "Hyperledger Besu: Deploys Cactus Besu Connector"
44
type: application
55
version: '0.15.0'

0 commit comments

Comments
 (0)