These instructions are to run a basic IBM blockchain network on IBM's container service. It will bring up the following components:
- Fabric-CA (with 3 CAs - 1 for orderer org and 2 for peer orgs)
- Orderer (SOLO)
- 2 Fabric-Peer (for org1)
- 2 Fabric-Peer (for org2)
- Fabric tool to create channel
- Fabric utils (Our home brewed image to assist the crypto and config artifact generation)
It also creates services to expose the components.
- Make it easy for a developer to set up a basic hyperledger fabric network on IBM Cloud.
- Keep it to basic hyperledger fabric network.
- WE DO NOT SUPPORT THIS OFFERING. Support is only provided through the IBM Container Service; IBM Blockchain does not have a support offering for this.
Yes, this can run on minikube. But, running on CS gives you a cloud hosted network. You can point your solution to HSBN once you are ready and have a HSBN.
https://kubernetes.io/docs/tasks/kubectl/install/
http://clis.ng.bluemix.net/ui/home.html
bx plugin repo-add bluemix https://plugins.ng.bluemix.net
bx plugin install container-service -r bluemix
bx cs cluster-create --name blockchain
You will have to login to Bluemix for the above to work:
# Point to Bluemix
bx api api.ng.bluemix.net
# Login to Bluemix
bx login
Command:
bx cs clusters
The response will be similar to the following:
Name ID State Created Workers
blockchain 7fb45431d9a54d2293bae421988b0080 deploying 2017-05-09T14:55:09+0000 0
Wait for the State to change from deploying to normal. Note that this might take about 15-30 minutes. If it takes more than 30 minutes, there is some issue on the container service.
A ready cluster should give the following response:
$ bx cs clusters
Listing clusters...
OK
Name ID State Created Workers
blockchain 0783c15e421749a59e2f5b7efdd351d1 normal 2017-05-09T16:13:11+0000 1
If you want to inspect on the status of the workers: Command:
# bx cs workers <cluster-name>
# Example
bx cs workers blockchain
The expected response is as follows:
$ bx cs workers blockchain
Listing cluster workers...
OK
ID Public IP Private IP Machine Type State Status
kube-dal10-pa0783c15e421749a59e2f5b7efdd351d1-w1 169.48.140.48 10.176.190.176 free normal Ready
Command:
#bx cs cluster-config <cluster-name>
bx cs cluster-config blockchain
Expected output:
Downloading cluster config for blockchain
OK
The configuration for blockchain was downloaded successfully. Export environment variables to start using Kubernetes.
export KUBECONFIG=/home/mrshah/.bluemix/plugins/container-service/clusters/blockchain/kube-config-prod-dal10-blockchain.yml
Use the export command above to point your kubectl cli to the cluster.
Following instructions will setup the blockchain network and create appropriate channel on IBM Container Service.
Note: You might see some errors Error from server (NotFound): error when stopping. Ignore those errors, as those occur when the cleanup is trying to delete pods which are not created.
To perform the setup, please run
setup_all.sh
To delete all deployments, please run
delete_all.sh
# To get the logs of a component, use -f to follow the logs
kubectl logs $(kubectl get pods | grep <component> | awk '{print $1}')
# Example
kubectl logs $(kubectl get pods | grep org1peer1 | awk '{print $1}')
# To get into a running container
kubectl exec -ti $(kubectl get pods | grep <component> | awk '{print $1}') bash
# Example
kubectl exec -ti $(kubectl get pods | grep ordererca | awk '{print $1}') bash