[chore] release 1.1 merge #2596
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
**Primary Changes** 1. Fixed deployment add-orderer-organization.yaml playbook for fabric 2.2.2 2. Added support for deploying add-orderer-organization.yaml playbook for Fabric 2.5.4 3- Added deletion of genesis file in platforms/hyperledger-fabric/configuration/roles/delete/genesis role. **Modifications** platforms/hyperledger-fabric/configuration/roles/create/cli platforms/hyperledger-fabric/configuration/add-orderer-organization.yaml platforms/hyperledger-fabric/configuration/cleanup.yaml platforms/hyperledger-fabric/configuration/deploy-network.yaml platforms/hyperledger-fabric/configuration/roles/create/configtx platforms/hyperledger-fabric/configuration/roles/create/genesis platforms/hyperledger-fabric/configuration/roles/create/new_organization/orderer_org platforms/hyperledger-fabric/configuration/roles/create/new_organization/orderer_org platforms/hyperledger-fabric/configuration/roles/create/orderers platforms/hyperledger-fabric/configuration/roles/delete/genesis platforms/hyperledger-fabric/configuration/roles/delete/vault_secrets fixes #2453 Signed-off-by: mgCepeda <marina.gomez.cepeda@accenture.com>
changes: updated quorum-add-new-org.md fixes:2483 Signed-off-by: saikumarbommakanti <sai.kumar.bommakanti@accenture.com>
) Changes: Introduced a new GitHub Workflow enabling the deployment of Hyperledger Bevel's CORDA DLT Platform to an EKS Cluster. Introduced a new directory at path: platforms/r3-corda/configuration/samples/workflow, containing two new sample network configuration files: network-proxy-corda: Supports deployment with Ingress controller. network-no-proxy-corda: Supports deployment without an Ingress controller, specifically designed for deployment on Minikube. Additional Changes: Allowing to choose between the 'deploy' and 'reset' actions when manually triggering it through the GitHub Actions UI. fixes #2416 Signed-off-by: sailajakommineni <sailaja.kommineni@accenture.com> Co-authored-by: Suvajit Sarkar <55580532+suvajit-sarkar@users.noreply.github.com>
**Primary Changes** 1. Updated Fabric config file 2. Fixed authpath harcode in tpl files fixes #2465 Signed-off-by: mgCepeda <marina.gomez.cepeda@accenture.com>
…ides tab (#2503) changes: updated operations: add-new-member-org.md add-new-validator-node.md add-new-validator-org.md setup-cactus-connector.md setup-onchain-permissioning.md Configurations: networkyaml-besu.md fixes:2483 Signed-off-by: saikumarbommakanti <sai.kumar.bommakanti@accenture.com> Co-authored-by: Suvajit Sarkar <55580532+suvajit-sarkar@users.noreply.github.com>
Signed-off-by: Roy,Sownak <sownak.roy@accenture.com>
changes: Configurations: networkyaml-quorum.md fixes:2465 Signed-off-by: saikumarbommakanti <sai.kumar.bommakanti@accenture.com>
**Primary Changes** 1.Updated operations corda docs 2.Removed cenm console in corda operations fixes #2483 Signed-off-by: sailajakommineni <sailaja.kommineni@accenture.com>
Signed-off-by: saikumarbommakanti <sai.kumar.bommakanti@accenture.com>
**Primary Changes** 1. The roles related to channel have been removed from the site.yaml file. 2. The create/configtx, create/channel_artifacts and create/genesis" roles aren't executed by version 2.5.4. 3. Channel creation can be done afterwards by running the add-new-channel.yaml playbook. Signed-off-by: mgCepeda <marina.gomez.cepeda@accenture.com>
…node Changes: Introduced new helm chart named besu-propose-validator at path platforms/hyperledger-besu/charts/. This chart utilizes the qbft_proposeValidatorVote method to facilitate the addition or removal of nodes from the validator set based on majority votes. fixes #2508 Signed-off-by: saikumarbommakanti <sai.kumar.bommakanti@accenture.com>
This commit enhances the deployment process for the Quorum Distributed Ledger Technology (DLT) network by exclusively leveraging Helm charts. Four new Helm charts have been introduced to streamline the deployment process: 1. quorum-genesis: Initializes the network with specific requirements. 2. quorum-node: Starts the network and allows adding new nodes. 3. quorum-tessera-node: Facilitates privacy by enabling transaction encryption using Tessera. 4. quorum-tlscert-gen: Enables secure access to the node via HTTPS. Each chart comes with a README to help users customize the network. These changes make deploying and managing the Quorum DLT network smoother with Helm. Other Improvements: - Added error handling to ensure clean uninstallation of the besu-genesis and besu-tlscert-gen charts. - Updated the README's API Call section. fixes #2484 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
…de (#2516) Changes: - Introduced new helm chart named `quorum-propose-validator` at path `platforms/quorum/charts/`. - This chart utilizes the `istanbul_propose` method to facilitate the addition or removal of nodes from the validator set based on majority votes. fixes #2508 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
This reverts commit 0b004fa.
Revert "[quorum] introduce helm chart deployment capability"
This commit enhances the deployment process for the Quorum Distributed Ledger Technology (DLT) network by exclusively leveraging Helm charts. Four new Helm charts have been introduced to streamline the deployment process: 1. quorum-genesis: Initializes the network with specific requirements. 2. quorum-node: Starts the network and allows adding new nodes. 3. quorum-tessera-node: Facilitates privacy by enabling transaction encryption using Tessera. 4. quorum-tlscert-gen: Enables secure access to the node via HTTPS. Each chart comes with a README to help users customize the network. These changes make deploying and managing the Quorum DLT network smoother with Helm. Other Improvements: - Added error handling to ensure clean uninstallation of the besu-genesis and besu-tlscert-gen charts. - Updated the README's API Call section. fixes #2484 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
* [corda] Ansible automation with new helm charts * Update network_service.tpl --------- Signed-off-by: Roy,Sownak <sownak.roy@accenture.com>
Signed-off-by: suvajit-sarkar <suvajit.sarkar@accenture.com>
Signed-off-by: saikumarbommakanti <sai.kumar.bommakanti@accenture.com>
Signed-off-by: Roy,Sownak <sownak.roy@accenture.com>
Signed-off-by: Aditya Joshi <adityaprakashjoshi1@gmail.com>
Signed-off-by: Roy,Sownak <sownak.roy@accenture.com>
Signed-off-by: Aditya Joshi <adityaprakashjoshi1@gmail.com>
(fabric): syntax fix for annotations
…2529) **Primary Changes** 1. This PR includes changes to deploy fabric 2.5.4 without a channel using helm charts. 2. Version 2.2.2 is pending 3. Deploy with Ansible pending **Changes in charts** platforms/hyperledger-fabric/charts/fabric-ca-server platforms/hyperledger-fabric/charts/fabric-cacerts-gen platforms/hyperledger-fabric/charts/fabric-catools platforms/hyperledger-fabric/charts/fabric-cli platforms/hyperledger-fabric/charts/fabric-orderernode platforms/hyperledger-fabric/charts/fabric-peernode fixes #2484 Signed-off-by: mgCepeda <marina.gomez.cepeda@accenture.com>
Signed-off-by: Roy,Sownak <sownak.roy@accenture.com>
This pull request introduces enhanced functionality to deploy the Substrate platform using Helm charts. Several improvements have been made to streamline the process and increase readability: 1. Substrate-genesis: - The substrate-genesis Helm chart now dynamically generates keys and updates the genesis.json file accordingly. - Eliminates the need for the substrate-key-chart Helm chart, achieving the same functionality within the substrate-genesis chart. - Once the entire Substrate codebase is updated, substrate-key-mgmt can be safely removed. 2. Substrate-node: - The substrate-node chart handles node deployment, simplifying the overall process. - Improved readability and maintainability by removing the repetetive code and containers such as node-secrets, retrieve-chain-spec, inject-keys, and query-services. - Their functionalities have been incorporated into the main container responsible for starting the node. 3. dscp-ipfs-node - Updated for deployment via Helm. 4. A README.md has been added at the path ./platform/substrate/charts/ to provide guidance for deploying the Substrate platform via Helm. These enhancements aim to streamline Substrate deployment via Helm, making the process more efficient and the codebase easier to manage. fixes #2484 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
[substrate] platform deployment via Helm
[fabric] Create channel using just helm
…iles to charts (#2562) Signed-off-by: alvaropicazo <alvaro.picazo.haase@accenture.com>
* [fabric] Helm chart updates Signed-off-by: sownak <sownak.roy@accenture.com>
Signed-off-by: sownak <sownak.roy@accenture.com>
Signed-off-by: sownak <sownak.roy@accenture.com>
Signed-off-by: sownak <sownak.roy@accenture.com>
[fabric] Genesis update and add new channel
This commit introduces support for deploying a decentralized ledger technology (DLT) network using Ansible automation. The changes include: 1. Updated the Ansible codebase to support network deployment in respect of the standalone Helm chart. 2. The following Ansible roles have been introduced to appropriately deploy the network: - 1. Generate keys for each node of each organization. - 2. Fetch generated keys in JSON format to deploy genesis with known nodes only. - 3. Utilize keys stored in the JSON file to configure the genesis with known nodes and then install the genesis block. - 4. A secondary genesis setup is also included to support deployment in multiple namespaces for a multi-organization Indy network. - 5. Deploy stewards for all organizations. - 6. Deploy the endorser. 3. Updated the Reset Ansible code to delete each node's key from the vault, along with the organization policy and Authentication engine. 4. Added an individual role to clean all the network-supported local files (JSON files). 5. Updated the sample network configuration file to provide information on which networks can be deployed using this file and how to customize the network by following the network rules specified in the file itself. This PR will allow users to set an Indy network with support of the following rules: 1. Exactly 1 trustee is required per organization. 2. Up to 1 endorser is allowed per organization. 3. At least 4 stewards are required collectively across the entire Indy network. fixes #2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
This PR updates our project to use Flux version 2.3.0. The following changes have been implemented: - The Flux version has been upgraded from 0.41.2 to 2.3.0. - Updated all HelmRelease templates (tpls) to utilize the v2 API instead of v2beta1. fixes #quick-fix Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
[indy] enable platform deployment via ansible server
[shared] support flux latest version 2.3.0
Signed-off-by: sownak <sownak.roy@accenture.com>
[fabric] Operator readme updates
**Primary Changes** 1.Deploy fabric 2.5.4 without channel using ansible. 2.Deploy fabric 2.2.2 without channel using ansible. 3.Update cleanup.yaml fixes #2556 Signed-off-by: mgCepeda <marina.gomez.cepeda@accenture.com>
[fabric] Update ansible playbooks and roles
This commit introduces support for deploying a decentralized ledger technology (DLT) network using Ansible automation. Updated the Ansible codebase to support network deployment in respect of the standalone Helm chart The following Ansible roles have been introduced to appropriately deploy the network of one organization only: 1. initlize the organization 2. setup cenm 3. setup notary 4. setup networkmap updated the sample network configuration file to provide information on which networks can be deployed using this file fixes #2548 Signed-off-by: saikumarbommakanti <sai.kumar.bommakanti@accenture.com>
**Primary Changes** 1.Deploy fabric 2.5.4 with channel using ansible. 2.Deploy fabric 2.2.2 with channel using ansible. fixes #2576 Signed-off-by: mgCepeda <marina.gomez.cepeda@accenture.com>
Signed-off-by: mgCepeda <marina.gomez.cepeda@accenture.com>
chore: merged changes from main to develop
Signed-off-by: sownak.roy <sownak.roy@amag2d2w93xrv.home>
sownak
requested review from
suvajit-sarkar,
jagpreetsinghsasan,
arsulegai,
weihong-ou and
adityajoshi12
as code owners
suvajit-sarkar
approved these changes
Jul 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.