Bevel Release 1.1.0

[suvajit-sarkar]

What's new in Bevel

• Platform's with new standalone helm charts, allowing network deployment using just helm commands.
• Network deployment with proxy or without proxy (single cluster dev/poc setup)
• Network deployment with Hashicorp Vault or without Vault with Kubernetes secrets

New Features

• HL Fabric
  • Network deployment without channel creation
  • Support for custom labels in services and deployments

Deprecation

• No active support for older versions of Bevel (below v1.0.0)
• Support on Kubernetes below v1.23
• No support for Fabric < 2.2.x

Known issues

• Corda Enterprise deployment using firewall support disabled

Major Bug Fixes

• policy_type variable undefined policy_type variable undefined #2473
• Incorrect storage class name Incorrect storage class name #2513
• RLPx Handshake Error in Quorum Validator Nodes RLPx Handshake Error in Quorum Validator Nodes #2563

Improvements

• All Platform helm charts refactored
• Hahsicorp Vault paths made flat for easier usage/readability for all platforms

Documentation

• Update the readme's, setup guide and version information for the DLT platforms
• Update operations guide

What's Changed

• [fabric] Support add-orderer-organization.yaml playbook by @mgCepeda in [fabric] Support add-orderer-organization.yaml playbook #2493
• docs(quorum): operations section under guides tab by @saikumarbommakanti in docs(quorum): operations section under guides tab #2498
• update(docs): fabric configuration and ops sections by @mgCepeda in update(docs): fabric configuration and ops sections #2500
• feat(r3corda): enable DLT deployment via GitHub Workflow & Action. by @sailajakommineni in feat(r3corda): enable DLT deployment via GitHub Workflow & Action. #2499
• update(docs): Substrate configuration file. by @mgCepeda in update(docs): Substrate configuration file. #2502
• docs(Hyperleder-besu): operations and configurations section under guides tab by @saikumarbommakanti in docs(Hyperleder-besu): operations and configurations section under guides tab #2503
• [corda] New charts as per release 1.0.0 by @sownak in [corda] New charts as per release 1.0.0 #2505
• docs(quorum): configuration section under guides tab by @saikumarbommakanti in docs(quorum): configuration section under guides tab #2504
• docs(r3corda): operations section under guide's tab by @sailajakommineni in docs(r3corda): operations section under guide's tab #2506
• update(docs): Indy configuration and ops sections by @mgCepeda in update(docs): Indy configuration and ops sections #2507
• chore: Updated kubeconfig configuration in storage class helm chart by @sownak in chore: Updated kubeconfig configuration in storage class helm chart #2511
• feat(fabric): Fabric deployment without channel by @mgCepeda in feat(fabric): Fabric deployment without channel #2515
• feat(besu): implement proposevalidatorvote method to add or rem… by @saikumarbommakanti in feat(besu): implement proposevalidatorvote method to add or rem… #2517
• [quorum] introduce helm chart deployment capability by @saurabhkumarkardam in [quorum] introduce helm chart deployment capability #2512
• [quorum] implement istanbul_propose method to add or remove a node by @saurabhkumarkardam in [quorum] implement istanbul_propose method to add or remove a node #2516
• Revert "[quorum] introduce helm chart deployment capability" by @suvajit-sarkar in Revert "[quorum] introduce helm chart deployment capability" #2519
• [quorum] introduce helm chart deployment capability by @saurabhkumarkardam in [quorum] introduce helm chart deployment capability #2520
• [corda] Ansible automation with new helm charts by @sownak in [corda] Ansible automation with new helm charts #2521
• doc: update roadmap by @suvajit-sarkar in doc: update roadmap #2522
• feat(besu): updated image versions for quorum engineering, besu-node and mysql by @saikumarbommakanti in feat(besu): updated image versions for quorum engineering, besu-node and mysql #2524
• [chore] Update flux and redis versions by @sownak in [chore] Update flux and redis versions #2526
• (fabric): added support for labels in fabric network by @adityajoshi12 in (fabric): added support for labels in fabric network #2528
• [r3-corda] Cordapps download with secrets by @sownak in [r3-corda] Cordapps download with secrets #2530
• (fabric): syntax fix for annotations by @adityajoshi12 in (fabric): syntax fix for annotations #2532
• [fabric] Introduce helm chart deployment capability for version 2.5 by @mgCepeda in [fabric] Introduce helm chart deployment capability for version 2.5 #2529
• [indy] Upgrade to 1.12.6 and support for Kubernetes 1.28+ by @sownak in [indy] Upgrade to 1.12.6 and support for Kubernetes 1.28+ #2531
• [substrate] platform deployment via Helm by @saurabhkumarkardam in [substrate] platform deployment via Helm #2541
• [fabric] Create configtx and genesis files using just helm by @mgCepeda in [fabric] Create configtx and genesis files using just helm #2543
• feat(r3-corda-ent) base network deployment using just helm charts by @suvajit-sarkar in feat(r3-corda-ent) base network deployment using just helm charts #2542
• [fabric] Catools should be dependency of orderer/peer by @mgCepeda in [fabric] Catools should be dependency of orderer/peer #2552
• [substrate] update helm charts readmes by @saurabhkumarkardam in [substrate] update helm charts readmes #2553
• feat(substrate): enable deployment with proxy and vault via helm by @saikumarbommakanti in feat(substrate): enable deployment with proxy and vault via helm #2554
• [indy] Use only helm to deploy Indy network by @sownak in [indy] Use only helm to deploy Indy network #2555
• feat(r3-corda-ent): helm only deployment using proxy and vault by @suvajit-sarkar in feat(r3-corda-ent): helm only deployment using proxy and vault #2559
• [substrate] enable platform deployment via ansible server by @saurabhkumarkardam in [substrate] enable platform deployment via ansible server #2561
• [fabric] Create channel using just helm by @mgCepeda in [fabric] Create channel using just helm #2560
• update(besu,quorum): adapt besu & quorum ansible tasks and template files to charts by @alvaropicazo in update(besu,quorum): adapt besu & quorum ansible tasks and template files to charts #2562
• [fabric] Helm chart updates by @sownak in [fabric] Helm chart updates #2571
• [fabric] Fix Chart versions and add-cli via helm chart by @sownak in [fabric] Fix Chart versions and add-cli via helm chart #2573
• [fabric] Update add cli and add peer docs by @sownak in [fabric] Update add cli and add peer docs #2575
• [fabric] Genesis update and add new channel by @sownak in [fabric] Genesis update and add new channel #2577
• [indy] enable platform deployment via ansible server by @saurabhkumarkardam in [indy] enable platform deployment via ansible server #2574
• [shared] support flux latest version 2.3.0 by @saurabhkumarkardam in [shared] support flux latest version 2.3.0 #2579
• [fabric] Operator readme updates by @sownak in [fabric] Operator readme updates #2580
• [fabric] Update ansible playbooks and roles by @mgCepeda in [fabric] Update ansible playbooks and roles #2570
• [r3-corda-ent] enable platform deployment via ansible-server by @saikumarbommakanti in [r3-corda-ent] enable platform deployment via ansible-server #2582
• [fabric] Update ansible playbooks for create a channel by @mgCepeda in [fabric] Update ansible playbooks for create a channel #2589
• shared: hot fix by @mgCepeda in shared: hot fix #2592
• chore: merged changes from main to develop by @suvajit-sarkar in chore: merged changes from main to develop #2593
• [docs] Updated for latest release by @sownak in [docs] Updated for latest release #2595
• [chore] release 1.1 merge by @sownak in [chore] release 1.1 merge #2596

Full Changelog: v1.0.1...v1.1.0

---

This discussion was created from the release Bevel Release 1.1.0.

[michaelkhalsa]

Hi,

Creating a fabric network Single org, 2 peers, 3 orderer, raft using bevel 1.1
Used an external vault (on separate ec2 instance)

Using MacOs (apple silicon) for controller, deployed to an eks cluster.
Ran playbook in sudo, included overrides to set os_aarch and bin directory in cmd.
Added a --kubeconfig location to flux bootstrap which seems to be necessary for flux on apple silicon.
Changed role/check/setup 'Wait for certs to be created in vault'
to use a command instead of shell (so would find vault)
Copied the most recent binaries (was, helm, vault, kubectl, flux) to bevel/bin, so that playbooks would not try to install outdated (and unworkable) versions). Copied over kubectl config, etc., to build.

Ran to completion successfully. Peers up and listening (according to logs), cli installed, orderers running, crypto materials all in vault, genesis block saved to vault and appears correct, everything pushed to the correct GitHub directory for flux.

PLAY RECAP **************************************************************************************************
localhost : ok=227 changed=65 unreachable=0 failed=0 skipped=232 rescued=0 ignored=0

Yet, according to logs, only the system chaincode was installed, i.e., not my chaincode (verified correct GitHub path and permissions). Running peer cli commands, it appears that no 'AllChannel' was created (as specified in network.yaml), nor peers joined to it. I went over network.yaml carefully.

There was also no join-channels job in eks cluster (assume there should be)?

I can run /api/v1/cainfo on the ca server endpoint (when exposed outside cluster) to verify it is live.

Looking through Ansible scripts, I do not see anywhere where the channel is actually created, peers joined, and chaincode installed. These are in the deploy-operator-network script, but not the network-deploy.yaml file.

Is this intentional? Am I missing something?

Also odd, in the terminal, after completing deploy-network yaml, it then went on to the deploy-operator-network yaml playbook, despite network.env.type not being 'operator' in platform.yaml file. All the tasks were skipped for that anyway. I am looking to see if there is somewhere this variable was changed midstream by one of the scripts.

Thanks for any help, suggestions, or comments.

[abhayprasadnovartis]

Hi,

Using the No proxy & No Vault option trying to create a fabric network by following the commands in below link
https://github.com/hyperledger-bevel/bevel/tree/main/platforms/hyperledger-fabric/charts#without-proxy-or-vault

Getting below error at # Join peer to channel and make it an anchorpeer
How do i rectify this error?
useradmin@100:~/hyperLedgerBevel/bevel/platforms/hyperledger-fabric/charts$ helm install peer0-allchannel ./fabric-channel-join --namespace supplychain-net --set global.vault.type=kubernetes
Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condition

Request for the help in this regard