update(indy): ansible playbooks and roles to use the new standalone helm charts #2557
Assignees
Labels
indy
Related to the Hyperledger Indy Platform
Comments
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 4, 2024
This commit introduces support for deploying a decentralized ledger technology (DLT) network using Ansible automation. The changes include: - 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: 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 endorsers - Updated the Reset Ansible code to delete each node's key from the vault, along with the organization policy and Authentication engine - Added an individual role to clean all the network-supported local files (JSON files) - 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. fixes hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 5, 2024
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. fixes hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 5, 2024
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. fixes hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 6, 2024
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. fixes hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 6, 2024
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. fixes hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 6, 2024
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. fixes hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 10, 2024
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 hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 11, 2024
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 hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 11, 2024
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 hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
saurabhkumarkardam
added a commit
to saurabhkumarkardam/S-bevel
that referenced
this issue
Jun 11, 2024
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 hyperledger#2557 Signed-off-by: saurabhkumarkardam <saurabh.kumar.kardam@accenture.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
As a developer I want to cleanup, update and test ansible playbooks and roles so that the Hyperledger Indy network can be deployed using the new standalone helm charts
Acceptance Criteria
The text was updated successfully, but these errors were encountered: