Using PCF Ops Manager to Deploy Hyperledger Fabric

Transcription

1 Using PCF Ops Manager to Deploy Hyperledger Fabric By VMware Introduction Pivotal Cloud Foundry Operations Manager (PCF Ops Manager for short) is a graphical interface used to configure and deploy various service components. Many PCF components are imported into Ops Manager as Tile. The web-based graphical interface displays products, tiles and configuration settings and diagnostic reports. The Andes Tile imported into PCF Ops Manager can deploy a Hyperledger Fabric cluster in Kubernetes. It can use an existing Kubernetes cluster, or create a Kubernetes cluster in Pivotal Container Service (PKS) Tile. PKS is a commercially supported release of the open source project Kubo, PKS has two important capabilities for Pivotal customers: a simple way to deploy and operate enterprise-grade Kubernetes, and a seamless mechanism for migrating container-based workloads to run on VMware vsphere or other cloud platform. Installation Prerequisites: 1. Install PCF Ops Manager 2.0.x or above. 2. Install PKS Tile 1.0.x or above. 3. Create a Kubernetes cluster 1.8.x or above and an NFS server. Note: You only need to do either #2 or #3. Andes Tile requires a Kubernetes cluster which can be created in PKS Tile by Andes Tile automatically or created by the end users manually in other place outside of Ops Manager. Deploy Andes Tile together with PKS Tile 1. Install PKS Tile Visit Ops Manager Web UI and login as user admin. Import PKS Tile, then click 'Pivotal Container Service' in the 'Installation Dashboard', then config each section under 'Settings' tab, until all sections show green icon. 1) Assign AZs and Networks

2 Figure 1 2) PKS API Figure 2

3 3) Plan 1 Figure 3 4) Plan 2

4 Figure 4 5) Kubernetes Cloud Provider Here we connects to vsphere as an example. If the Ops Manager is deployed on vsphere vcenter, use the same vcenter connection here.

5 Figure 5

6 6) UAA Figure 6 Go back to Installation Dashboard, click 'Apply Changes' in the 'Installation Dashboard' to deploy PKS Tile. It shows 'Changes Applied' when deployment completes successfully. 2. Create a user in PKS SSH to Ops Manager VM as user ubuntu. Follow PKS doc to create a uaa user for PKS. Install uaac: $ sudo gem install cf-uaac Add PKS UAA IP and FQDN mapping in /etc/hosts, for example: $ echo uaa.pks.local sudo tee -a /etc/hosts Target your UAA Server: $ uaac target Authenticate with UAA Server with the 'Uaa Admin Secret' in the 'Credentials' tab of Pivotal Container Service Tile: $ uaac token client get admin -s THE-UAA-ADMIN-SECRET Create a user in PKS: $ uaac user add pks -- s pks@example.com -p password

7 Assign admin role to the user to manage Kubernetes clusters: $ uaac member add pks.clusters.admin pks 3. Create a K8s cluster in PKS Note: This step is not needed if PKS or higher version is installed. 1) Set env variables. $ export CLUSTER_NAME=<Any Cluster Name> # e.g. mycluster $ export PKS_API_ENDPOINT=<UAA_FQDN> # The UAA URL configured in PKS Tile, e.g. uaa.pks.local $ export PKS_API_USERNAME=pks $ export PKS_API_PASSWORD=password $ export K8S_MASTER_EXTERNAL_FQDN=<Any FQDN which can be resolved to the K8S MASTER IP> # Usually it's the FQDN of load balancer for K8s masters, e.g. "mycluster.k8s.pks.local" $ export K8S_WORKERS_NUM=2 2) Download PKS CLI $ wget -q -O pks $ chmod +x pks $ sudo mv pks /usr/local/bin/pks 3) Login PKS. $ pks login -k -a $PKS_API_ENDPOINT -u $PKS_API_USERNAME -p $PKS_API_PASSWORD 4) Create k8s cluster using PKS CLI. $ pks create-cluster $CLUSTER_NAME --external-hostname $K8S_MASTER_EXTERNAL_FQDN --plan small --num-nodes $K8S_WORKERS_NUM 5) Generate kube config file which is used by kubectl. $ pks get-credentials $CLUSTER_NAME 6) Configure BOSH CLI environment. Get Bosh Commandline credentials via om CLI. Assume is the Ops Manager IP: $ om -t u admin -p 'Admin!23' -k curl -s --path /api/v0/deployed/director/credentials/bosh_commandline_credentials jq -r '.credential' Copy BOSH_CA_CERT file from Ops Manager VM to local box: $ scp ubuntu@ :/var/tempest/workspaces/default/root_ca_certificate /tmp/

8 Set Bosh env variables: $ export BOSH_CLIENT=ops_manager $ export BOSH_CLIENT_SECRET="xxxxx" # Get from last steps $ export BOSH_CA_CERT=/tmp/root_ca_certificate # the path of local certificate file $ export BOSH_ENVIRONMENT= # The Bosh Directory VM IP 7) Start rpcbind service on all k8s worker nodes. This step is required due to a bug of PKS Tile It will be fixed in PKS Tile future releases. $ bosh ssh worker -d `bosh deployments --column Name grep service-instance tail -1` "sudo service rpcbind restart" 4. Install Andes Tile Import Andes Tile in the 'Installation Dashboard', and then click "Andes Blockchain Service", then config each section under 'Settings' tab, until all sections show green icon. 1) Assign AZs and Networks 2) Hyperledger Fabric Figure 7 Users can set Organization Number and Peer Number in this panel.

9 Figure 8 3) Kubernetes Choose "Create or reuse Kubernetes Cluster in PKS". Then config the connection to PKS Server and the name of Kubernetes cluster to be created or used.

10 Figure 9 Back to Installation Dashboard, click 'Apply Changes' in the 'Installation Dashboard' to deploy Andes Tile. It shows 'Changes Applied' when deployment completes successfully.

11 Deploy Andes Tile without PKS Tile Note: PKS Tile is not required in this approach, but you need to setup an NFS server which allows read/write access from all IPs and set owner of the export directory to 'nobody:nogroup'. Please follow '4. Install Andes Tile' to config Andes Tile. The only difference is that choosing "Use existing Kubernetes cluster" in 'Kubernetes' panel. X509 Client Certificate/Key authentication and Username/Password authentication are supported for connecting to the existing Kubernetes cluster. You must provide either 'Client Certificate/Key' or 'Username/Password', but not both. 1) Username/Password Enter 'Kubernetes Username' and ''Kubernetes Password'

12 Figure 10

13 2) X509 Client Certificate/Key Enter 'Kubernetes Client Certificate' and 'Kubernetes Client Key'. Figure 11

14 Back to Installation Dashboard, click 'Apply Changes' in the 'Installation Dashboard' to deploy Andes Tile. It shows 'Changes Applied' when deployment completes successfully. Use Hyperledger Fabric Cluster created by Andes Tile 1. Visit Hyperledger Fabric Explorer and Kubernetes Dashboard Get Kubernetes Dashboard URL and Hyperledger Fabric Explorer URL from Andes Tile. 1) Click "Installation Dashboard -> Andes Blockchain Service -> Status". Record the IP. Figure 12 2) Visit the IP in the Web Browser to view the Andes Blockchain Service Portal. Figure 13 3) Click "Hyperledger Fabric Explorer" to view Hyperledger Fabric Explorer.

15 Figure 14 4) Click "Kubernetes Dashboard" to view Kubernetes Dashboard. You must import Kubernetes config file or enter token to sign in.

16 Figure Run Hyperledger Fabric Chaincode Copy the kube config file of your Kubernetes cluster to any machine and download kubectl CLI. 1) Show all Hyperledger Fabric pods in the Kubernetes cluster. $ kubectl get pods --all-namespaces Figure 16

17 2) Launch the bash shell of the Fabric CLI pod. $ kubectl exec -it cli-856fbbc8fd-hnpcq --namespace=org1-f-1 bash Figure 17 3) Run Chaincode in the Fabric CLI pod. For example: Install Chaincode: $ peer chaincode install -n mycc -v 1.0 -p github.com/hyperledger/fabric/peer/resources/chaincodes/chaincode_example02 Instantiate Chaincode: $ peer chaincode instantiate -o orderer0.ordererorg-f-1:7050 -C defaultchannel -n mycc -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P "OR ('Org1MSP.member','Org2MSP.member')" Invoke Chaincode: $ peer chaincode invoke -o orderer0.ordererorg-f-1:7050 -C defaultchannel -n mycc -c '{"Args":["invoke","a","b","10"]}' Query Chaincode: $ peer chaincode query -C defaultchannel -n mycc -c '{"Args":["query","a"]}'