Once your cluster has successfully deployed, perform the following steps to deploy the asset management demonstration app. This app repeatedly assigns an asset "Picasso" from one owner to another. For more information about this app as well as its source code, see the Fabric repository.

Run Using AMP Effector

  • Go to http://10.10.10.100:8081/ in your browser (the Cloudsoft AMP Console)
  • Click on the "Applications" tab
  • Hover over the ">" under "Hyperledger Fabric Application" (or your custom name)
  • Click "Expand All"
  • Click "CLI Node"
  • Click the "Effectors" tab
  • Click "Invoke" next to "Run Demo Application"

Run Manually

Step 1: SSH into CLI Node

  • Go to http://10.10.10.100:8081/ in your browser (the Cloudsoft AMP Console)
  • Click on the "Applications" tab
  • Hover over the ">" under "Hyperledger Fabric Application" (or your custom name)
  • Click "Expand All"
  • Click "CLI Node"
  • Click the "Sensors" tab
  • Copy the host.sshAddress value
  • Open up your terminal and run command: ssh <ssh-address-here>

Note 1: You may need to supply an SSH key or a username / password depending on your deployment location's configuration.

Note 2: If host.sshAddress ends with a port (e.g. :22), remove the colon and the port from the SSH command.

Note 3: If you deployed to local Vagrant VMs, you can SSH into any of these VMs by running this command instead: vagrant ssh byon<number here>. The name of the VM is based on the last digit of the IP address. For example, if the CLI node's IP is 10.10.10.102 then the command would be: vagrant ssh byon2.

Step 2: Build and Run the Asset Management App

From the same terminal window from the previous step, execute the following commands:

sudo docker exec -it cli bash
cd $APP_HOME
go build
./app

This enters the CLI container, builds the app, and executes the app. When the app runs, the output should clearly indicate the transfer of ownership of "Picasso" ultimately ending with "Dave" as the owner.

Appendix

AWS EC2 instances

If deploying to AWS You should use an up-to-date CentOS AMI. The "CentOS 7 (x86_64) with Updates HVM" images (link) are a good choice. The following is a sample catalogue blueprint for the us-east-1 version of this AMI:

brooklyn.catalog:
  id:       aws-virginia-centos7
  name:     AWS Virginia CentOS 7
  itemType: location
  item:
    type: jclouds:aws-ec2
    brooklyn.config:
      identity:   <YOUR IDENTITY>
      credential: <YOUR CREDENTIAL>
      region:     us-east-1
      imageId:    us-east-1/ami-6d1c2007
      minRam:     2000
      loginUser:  centos
      installDevUrandom: true
      allocatePTY: true

For any questions or comments, please contact via: hlf-success@cloudsoft.io

Or add us on our Slack Channel: https://slack.cloudsoft.io/