Skip to content

mohana-intain/baf

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
README.md
README.md
 
 

Repository files navigation

BLOCKCHAIN AUTOMATION FRAMEWORK

CORDA DEPLOYMENT IN AMAZON WEB SERVICE - ELASTIC KUBERNETES SERVICE CLUSTER

A. STEPS TO SET UP AWS EKS CLUSTER

**TO INSTALL AWS CLI EXECUTE THE FOLLOWING COMMANDS

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install

**TO CONFIGURE AWS CLI

Run  aws configure. Paste ACCESS KEY AND SECRET KEY PROVIDED.

**TO INSTALL TERRAFORM

curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo apt-key add -
sudo apt-add-repository "deb [arch=amd64] https://apt.releases.hashicorp.com $(lsb_release -cs) main"
sudo apt-get update && sudo apt-get install terraform

**TO CREATE EKS CLUSTER USING TERRAFORM EKS

git clone git@github.com:sivaramkannan/blockchain-platform.git
cd blockchain-platform/cloudplatform/aws
gedit aws_credentials.  //  Place ACCESS KEY AND SECRET KEY PROVIDED.
terraform init
terraform state replace-provider "registry.terraform.io/-/aws" "hashicorp/aws"
terraform apply

/The above command creates a Elastic Kubernetes Cluster in AWS with 3 Nodes. In order to increase the number of nodes donot change in the eks.tf . Change in the AWS EKS UI after the Cluster is created./

terraform destroy     //  Destroys the cluster.

/*How to change the nodes in UI.

Services -> Containers -> Elastic Kubernetes Services ->Under ”Amazon EKS” Clusters ->Under “Cluster name” -> Configuration -> Compute -> Node Groups -> Under “Group name” -> Edit (in top right corner) -> Enter the total nodes in Maximum and Desired Size -> Save Changs (Bottom Right Corner) */

**TO CHECK WHETHER THE CLUSTER IS CREATED

 aws eks list-clusters

**TO UPDATE THE KUBERNETES CONFIGURATION FILE

 aws eks --region <cluster_region> update-kubeconfig --name <cluster_name>
 kubectl config view

**TO VIEW ALL PODS IN THE CLUSTER

 kubectl get pods --all-namespaces

B. CREATE A NGINX SERVER

**CREATE A FILE nginx.yaml AND PASTE THE BELOW CONTENTS

    apiVersion: apps/v1
    kind: Deployment
    metadata:
     name: nginx-deployment
    spec:
     replicas: 1
     selector:
         matchLabels:
           app: node-nginx-app
     template:
       metadata:
         labels:
           app: node-nginx-app 
       spec:     
         volumes:
         - name: nginx
           persistentVolumeClaim:
             claimName: nginx-pvc
         containers:
         - name: node-nginx-app
           image: nginx
           imagePullPolicy: Always
           volumeMounts:
           - mountPath: /mnt
             name: nginx

**TO DEPLOY THE SERVER, EXECUTE THE BELOW COMMANDS

  kubectl create deployment nginx --image=nginx
  kubectl get pods --all-namespaces
  kubectl exec -it <nginx pod name> -- /bin/bash

C. SETTING UP VAULT SERVER

**AFTER LOGGING INTO CONSOLE CHOOSE Services → Compute → EC2 → Launch Instance → Launch Instance 

**SELECT ami-0a91cd140a1fc148a / ami-0dd9f0e7df0f0a138 / ami-0d2751e39abf67ea8 / ami-0ebc8f6f580a04647

**TYPE:  t2.micro

**ADD RULE :
  ingress {
     from_port = 8200        
     to_port = 8200
     protocol = "tcp"
     cidr_blocks = ["0.0.0.0/0"]
     }

  ingress {
     from_port = 8200
     to_port = 8200
     protocol = "tcp"
     ipv6_cidr_blocks = ["::/0"]
  }

**SELECT YOUR EXISTING PAIR OR CREATE A NEW KEY PAIR

**LAUNCH Instance

**CLICK How to connect to your Linux Instance
CHOOSE SSH  Or go to the instance dashboard and click connect
Copy the command paste in terminal
Check whether key-pair.pem file exists in the directory before you execute the command

**AFTER LOGGING INTO THE INSTANCE DO THE FOLLOWING

    https://www.digitalocean.com/community/tutorials/how-to-install-and-use-docker-on-ubuntu-18-04 
    Follow the link to install docker
    which docker
    cd into directory
    sudo chmod -R 777 docker*
**DO THE FOLLOWING
  1. Create a file /etc/systemd/system/vault-docker.service cd /etc/systemd/system nano vault-docker.service
  2. Copy paste the below content there

[Unit]

Description=Vault Docker Application Service Requires=docker.service After=docker.service

[Service]

ExecStart=/usr/bin/docker run --rm -v /opt/vault/store:/vault/file -p 8200:8200 --cap-add=IPC_LOCK -e 'VAULT_LOCAL_CONFIG={"backend": {"file": {"path": "/vault/file"}}, "default_lease_ttl": "168h", "max_lease_ttl": "720h", "listener": {"tcp": {"address": "0.0.0.0:8200", "tls_disable": true}}}' vault server Restart=always RestartSec=90 StartLimitInterval=400 StartLimitBurst=3

[Install]

WantedBy=multi-user.target

  1. sudo systemctl enable vault-docker.service

  2. sudo systemctl start vault-docker.service

    **EXECUTE THE COMMAND TO VIEW THE IP dig +short myip.opendns.com @resolver1.opendns.com

    **GO TO THE LINUX TERMINAL [Use the Above IP to export]

     export VAULT_ADDR='http://DNS_Name:8200' //DROPLET IP
 vault operator init -key-shares=1 -key-threshold=1
 vault login root-token
 export VAULT_TOKEN="<Your Vault root token>"
 vault operator unseal
 vault secrets enable -version=1 -path=secret kv
 vault status
 vault secrets list

D. SETTING UP BAF DLT NETWORK

**MAKE A LOCAL PROJECT FOLDER

**INSIDE THE PROJECT FOLDER GIT CLONE THE BLOCKCHAIN AUTOMATION FRAMEWORK REPOSITORY FROM HYPERLEDGER LABS OR YOUR OWN VERSION OF THE CLONED REPO.

git clone git@github.com:sivaramkannan/baf-intain-fork.git

**CREATE A NEW BRANCH OUT OF THE CLONED REPO.

IF DOING FOR THE FIRST TIME  :    git checkout -b corda-test v0.7.0.0

OR ELSE                      :    git push -d origin corda-test
			  git checkout -b corda-test v0.7.0.0

CHECK USING                 :    git branch

**CHANGE DIRECTORY TO BAF-INTAIN-FORK

**CREATE A NEW DIRECTORY CALLED build

**INSIDE THE build DIRECTORY , YOU HAVE TO PLACE 4 FILES. network.yaml gitops (private key) gitops.pub (public key) kuberenetes-configuration-file(.yaml) JAR DIRECTORY (JAR FILES)

**COPY THE FILE FROM /blockchain-automation-framework/platforms/r3-corda/configuration/samples/network-cordav2.yaml AND PLACE IT IN BUILD DIRECTORY AND RENAME IT AS * network.yaml

**CHANGE CORDA VERSION TO 4.4 IN network.yaml

**UPDATE THE FOLLOWING

CHANGE THE network_services:SECTION

UNDER THE ORGANISATIONS SECTION, CHANGE 
external_url_suffix: test.corda.emulya.com

UPDATE THE CLOUD PROVIDER, k8s , VAULT SECTION, GITOPS

**MAKE A EMPTY FOLDER AS CORDA-TEST

cd blockchain-automation-framework/platforms/r3-corda/releases
mkdir corda-test

**MAKE THE FOLLOWING CHANGES

CHANGE THE PRESENT WORKING DIRECTORY TO

blockchain-automation-framework/platforms/r3-corda/configuration/roles/create/storageclass/tasks/main.yaml

	IN THE TASK **CREATE** REPLACE THE CLOUD PROVIDER AS YOUR CLOUD PROVIDER.     Eg.  { cloud_provider }storageclass REPLACED AS awsstorageclass

SEARCH IN baf-intain-fork/platforms/r3-corda/ FOR k8s_raw AND CHANGE k8s_raw TO community.kubernetes.k8s

**COMMIT THE CHANGES

git commit -a
git remote -v
git status
git push origin corda-test

**TO RUN THE PROVISIONING SCRIPTS

docker run -it -v $(pwd):/home/blockchain-automation-framework/ hyperledgerlabs/baf-build

**TO RUN THE NETWORK

ansible-playbook platforms/shared/configuration/site.yaml -e "@./build/network.yaml"  -e 'ansible_python_interpreter=/usr/bin/python3'

**TO RESET THE NETWORK

bash reset.sh

**TO DEPLOY CORDAPP

ansible-playbook platforms/r3-corda/configuration/deploy-cordapps.yaml -e "@./build/network.yaml" -e "source_dir='/home/blockchain-automation-framework/build/jar'" -e 'ansible_python_interpreter=/usr/bin/python3'

About

No description, website, or topics provided.

Resources

Readme
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

No packages published