Skip to content

Commit 3483b16

Browse files
committed
updating with inputs from the PM team
1 parent de2b08c commit 3483b16

File tree

1 file changed

+25
-4
lines changed

1 file changed

+25
-4
lines changed

articles/blockchain/templates/hyperledger-fabric-consortium-azure-kubernetes-service.md

Lines changed: 25 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -113,11 +113,11 @@ The deployment usually takes 10-12 minutes, might vary depending on the size and
113113
To build the blockchain consortium post deploying the ordering service and peer nodes, you need to carry out the below steps in sequence. Azure HLF script (azhlf), which helps you with setting up the consortium, creating channel, and chaincode operations.
114114

115115
> [!NOTE]
116-
> Azure HLF (azhlf) script provided is to help with demo/DevTest scenarios only. Channel and consortium created by this script has basic HLF policies to simplify demo/DevTest scenario. For production setup, we recommend updating channel/consortium HLF policies in line with your organization compliance needs using the native HLF APIs.
116+
> There is an update in the script, this update is to provide more functionality with Azure HLF script. If you want to refer to the old script, [see here](https://github.com/Azure/Hyperledger-Fabric-on-Azure-Kubernetes-Service/blob/master/consortiumScripts/README.md). This script is compatible with Hyperledger Fabric on Azure Kubernetes Service template version 2.0.0 and above. To check the version of the deployment, follow the steps in [Troubleshoot](#troubleshoot).
117117
118+
> [!NOTE]
119+
> Azure HLF (azhlf) script provided is to help with demo/DevTest scenarios only. Channel and consortium created by this script has basic HLF policies to simplify demo/DevTest scenario. For production setup, we recommend updating channel/consortium HLF policies in line with your organization compliance needs using the native HLF APIs.
118120
119-
>[!NOTE]
120-
> There is an update in the script and this update is to provide more functionlaity with Azure HLF script. If you want to refer to the old script, [see here](https://github.com/Azure/Hyperledger-Fabric-on-Azure-Kubernetes-Service/blob/master/consortiumScripts/README.md).
121121

122122
All the commands to run the Azure HLF script can be executed through Azure Bash Command Line. Interface (CLI). You can login into Azure shell web version through  ![Hyperledger Fabric on Azure Kubernetes Service Template](./media/hyperledger-fabric-consortium-azure-kubernetes-service/arrow.png) option at the top-right corner of the Azure portal. On the command prompt, type bash and enter to switch to bash CLI.
123123

@@ -126,7 +126,6 @@ See [Azure shell](https://docs.microsoft.com/azure/cloud-shell/overview) for mor
126126
![Hyperledger Fabric on Azure Kubernetes Service Template](./media/hyperledger-fabric-consortium-azure-kubernetes-service/hyperledger-powershell.png)
127127

128128

129-
130129
The following image shows the step-by-step process to build consortium between an orderer organization and peer organization. Detailed commands to execute these steps are captured in the following sections.
131130

132131
![Hyperledger Fabric on Azure Kubernetes Service Template](./media/hyperledger-fabric-consortium-azure-kubernetes-service/process-to-build-consortium-flow-chart.png)
@@ -392,3 +391,25 @@ Execute below command to query chaincode:
392391
./azhlf chaincode query -o $ORGNAME -u $USER_IDENTITY -n $CC_NAME -c $CHANNEL_NAME -f <queryFunction> -a <queryFuncArgs>
393392
```
394393
Pass query function name and space separated list of arguments in `<queryFunction>` and `<queryFuncArgs>` respectively. Again, taking chaincode_example02.go chaincode as reference, to query value of “a” in the world state set `<queryFunction>` to `query` and `<queryArgs>` to “a”.
394+
395+
## Troubleshoot
396+
397+
**To verify the running template version**
398+
399+
Run the below commands to find the version of your template deployment.
400+
401+
Set below environment variables as per the resource group where template has been deployed.
402+
403+
```bash
404+
405+
SWITCH_TO_AKS_CLUSTER() { az aks get-credentials --resource-group $1 --name $2 --subscription $3; }
406+
AKS_CLUSTER_SUBSCRIPTION=<AKSClusterSubscriptionID>
407+
AKS_CLUSTER_RESOURCE_GROUP=<AKSClusterResourceGroup>
408+
AKS_CLUSTER_NAME=<AKSClusterName>
409+
```
410+
Run below command to print the template version
411+
```bash
412+
SWITCH_TO_AKS_CLUSTER $AKS_CLUSTER_RESOURCE_GROUP $AKS_CLUSTER_NAME $AKS_CLUSTER_SUBSCRIPTION
413+
kubectl describe pod fabric-tools -n tools | grep "Image:" | cut -d ":" -f 3
414+
415+
```

0 commit comments

Comments
 (0)