-
My Hard specs highlights:
Intel(R) Core Duo CPU E8500 @ 3.16GHz RAM: 8Gb
-
My Soft specs highlights:
Kernel version 4.15.10-300.fc27.x86_64 (Fedora 27) Docker version 1.13.1 docker-compose version 1.17.1
- Go to some directory, such as "/home/user", using any of these commands (all are the same):
cd
cd ~
cd /home/user- Use sudo or execute as root, to avoid user rights issues:
sudo git clone https://github.com/carmelopz/sawtooth-supply-chain
cd sawtooth-supply-chain
sudo docker-compose up- Wait until the output stops and/or in a new terminal use this to verify that the 10 containers are up:
sudo docker ps- Then, we can see the example FishNet supply chain application running. Using any browser on the host:
- As seen below, I have developed a python program to get access to the database tier, using a new container:
- Go to this subdirectory of /sawtooth-supply-chain
cd dbtier- We build the image from the Dockerfile which also imports the needed libraries in requirements.txt:
sudo docker build -t dbtier .- Then, we run the image as a container. Thanks to the --net=host command, the container can connects with the other containers and be available at the host at the same time, without port conflicts.
sudo docker run --net=host dbtier- We can see the agents record in browser running in the host:
A last note: I have tried also this week to prepare a docker yml compose files adding some replicas of the containers, to show how the queries are balanced between them.
Nevertheless, the docker compose yml file of the supply-chain app is in version 2.1, which does not support the "replicas" command and beside this, we have to decide between using the swarm option in docker versus converting the docker-compose.yml to kubernetes, which I think is clearly winning the orchestration topic race versus docker swarm.
I have also tried the open-source converter Kompose:
https://github.com/kubernetes/kompose
In order to translate the sawtooth supply chain yml compose file to kubernetes, but it is not working out of the box. So both docker swarm and kubernetes will need me some extra time to test this sawtooth application.
More details below. Thank you so much for reading this.
--- ooOoo ---
This is a distributed application to help you trace the provenance and other contextual information of any asset. It can be used as-is or customized for different use cases. This distributed application runs on top of Hyperledger Sawtooth, an enterprise blockchain. To learn more about Hyperledger Sawtooth please see its sawtooth-core repo or its published docs.
Running alongside the core components from Hyperledger Sawtooth, Supply Chain includes a number of elements customizing the blockchain and user interaction with it:
- a transaction processor which handles Supply Chain transaction logic
- a server which provides an HTTP/JSON API for Supply Chain actions
- a ledger sync which syncs blockchain data to a local database
- the AssetTrack example client for tracking generic assets
- the FishNet example client for tracking fish from catch to table
- a shell container with the dependencies to run any commands and scripts
This project utilizes Docker to simplify
dependencies and deployment. After cloning this repo, follow the instructions
specific to your OS to install and run whatever components are required to use
docker and docker-compose from your command line. This is only dependency
required to run Supply Chain components.
Once Docker is installed and you've cloned this repo, navigate to the root project directory and run:
docker-compose upThis will take awhile the first time it runs, but when complete will be running all required components in separate containers. Many of the components will be available through HTTP endpoints, including:
- The Supply Chain REST API will be at http://localhost:8020
- AssetTrack will be at http://localhost:8021
- FishNet will be at http://localhost:8022
- RethinkDB's admin panel will be available at http://localhost:8023
- Sawtooth's blockchain REST API will be available at http://localhost:8024
In bash you can shutdown these components with the key combination: ctrl-C.
You can shutdown and remove the containers (destroying their data), with the
command:
docker-compose downRunning docker-compose up, will automatically run all scripts necessary to
use all Supply Chain components. However if you want to run any additional
scripts, such as scripts to automatically update sample blockchain data, a shell
container is provided with all necessary dependencies installed. To enter the
shell, simply open a terminal window and run:
docker exec -it supply-shell bashOnce inside the shell, you might try running the one of the update scripts to see live updates populate in an example web app. First navigate to the server directory:
cd server/Then run one of the two provided npm scripts:
npm run update-sample-assets
npm run update-sample-fishYou can customize how many updates are submitted per minute with the RATE
environment variable (default 6), and use LIMIT to stop the updates after a
certain number are submitted (default 25):
RATE=3 LIMIT=10 npm run update-sample-assetsIf you just want to exit the shell, you can simply run:
exitWhile the Server runs out of the box with sensible defaults, there are a number of secrets and API keys which will not be secure unless set explicitly. While this is fine for demo purposes, any actual deployment set the following properties:
- JWT_SECRET: can be any random string
- PRIVATE_KEY: must be 64 random hexadecimal characters
- MAPS_API_KEY: provided by Google Maps
These properties can be set one of two ways, through an environment variable,
or (preferably) by creating a file named config.json file in the server/
directory. A file named config.json.example is provided which should provide
a template to follow.
The default Docker containers use the volumes command to link directly to the
source code on your host machine. As a result any changes you make will
immediately be reflected in Supply Chain components without having to rebuild
them. However, typically you will have to restart a component before it can
take advantage of any changes. Rather than restarting every container, you can
restart a single component from separate terminal using the container name. For
example:
docker restart supply-serverThe available container names include:
- supply-shell
- supply-processor
- supply-server
- supply-asset-client
- supply-fish-client
- supply-rethink
- supply-validator
- supply-settings-tp
- supply-rest-api
Files in the protos/ directory are used to generate classes for other
components. This is done automatically on up, but if you make changes to
these files and wish to rebuild the generated files immediately, you can do so
from within the Supply Chain Shell:
docker exec -it supply-shell bashOnce in the shell, you can generate the necessary Python classes simply by running:
protogenFor the example clients, in addition to rebuilding them on Protobuf changes, any changes to their source code will require their static files be rebuilt. However, their containers do not typically need to be restarted in order to reflect changes, just rebuild the static files and refresh your browser (the browser cache may have to be emptied):
cd asset_client/
npm run buildcd fish_client/
npm run buildThe latest documentation for Sawtooth Supply Chain is available within this repo in the docs subdirectory.
Hyperledger Sawtooth software is licensed under the Apache License Version 2.0 software license.
Hyperledger Sawtooth Supply Chain documentation in the docs subdirectory is licensed under a Creative Commons Attribution 4.0 International License. You may obtain a copy of the license at: http://creativecommons.org/licenses/by/4.0/.
