Ahmed Muawia Khan 9be68c972d Problem: standardize docker-compose workflows (#2130)
- Standardize docker-compose workflow
- Change docker-compose version to 2.1
  - why one might ask? because compose version
    3.0 does not support depends on and inherits
    like we want to and is more aimed towards migration to using
    `docker stack`, for our current strategy `2.1` is a better choice.
- change `bdb` service `bigchaindb` service
  - why? Introduced a new proxy service `bdb` which is just a dummy
    `busybox` image.
    - why? because this ensure via healthcheck of bigchaindb that BigchainDB
      has started properly and makes a `curl` to ensure HTTP API server is up
      and running.
      - why? Because we have had scenarios where BigchainDB is not started
        via docker compose and user has to check out the logs to find out what
        the problem might be. This ensure that bigchaindb is up and running.
- Does this change deployment workflow? No.
  - The only thing change is that if you want to run commands inside a bigchaindb
    container e.g. `pytest` now you have to run the following command:
    `docker-compose run --rm --no-deps bigchaindb pytest -v --cov=bigchaindb`
     as opposed to `docker-compose run --rm --no-deps bdb pytest -v --cov=bigchaindb`
- Remove env variable `BIGCHAINDB_START_TENDERMINT`
- Remove TENDERMINT_INTEGRATION.rst and move to the new docs
- Change mdb -> mongodb because the other services were named with
  full name.
- Add example to run specific tests or from a file
- Update config.toml for tendermint to use `bigchaindb` as proxy app
  instead of `bdb`
- Remove `network` directory because it is deprecated
- Add comment about why PYTHONBUFFERED is used
2018-03-21 12:42:43 +01:00

4.5 KiB

Vanshdeep's Notes on Running a Local Dev Node

The following doc describes how to run a local node for developing BigchainDB Tendermint version.

There are two crucial dependencies required to start a local node:

  • MongoDB
  • Tendermint

and of course you also need to install BigchainDB Sever from the local code you just developed.

Installing MongoDB

MongoDB can be easily installed, just refer their installation documentation for your distro. We know MongoDB 3.4 works with BigchainDB. MongoDB 3.6 might work, or it might not. You could try it. After the installation of MongoDB is complete, run MongoDB using sudo mongod --replSet=bigchain-rs

Installing Tendermint

Installing Tendermint Using Docker

Tendermint can be run directly using the docker image. Refer here for more details.

Installing Tendermint from Source

  • Before we can begin installing Tendermint one should ensure that the Golang is installed on system and $GOPATH should be set in the .bashrc or .zshrc. An example setup is shown below

$ echo $GOPATH
/home/user/Documents/go
$ go -h
Go is a tool for managing Go source code.

Usage:

	go command [arguments]

The commands are:

	build       compile packages and dependencies
	clean       remove object files

...

  • We can drop GOPATH in PATH so that installed Golang packages are directly available in the shell. To do that add the following to your .bashrc
export PATH=${PATH}:${GOPATH}/bin
  • Now we can install Glide which is vendor package manger for Golang,
$ go get github.com/Masterminds/glide

...
...

$ glide -h
NAME:
   glide - Vendor Package Management for your Go projects.

   Each project should have a 'glide.yaml' file in the project directory. Files
   look something like this:

...
  • Now we install Tendermint from source,
$ mkdir -p $GOPATH/src/github.com/tendermint && cd $_
$ git clone https://github.com/tendermint/tendermint
...
$ cd tendermint && glide install
$ go install ./cmd/tendermint
  • If the above commands were executed successfully then Tendermint is installed at $GOPATH/bin. To ensure Tendermint's installed fine execute the following command,
$ tendermint -h
Tendermint Core (BFT Consensus) in Go

Usage:
  tendermint [command]

Available Commands:
  gen_validator               Generate new validator keypair
  help                        Help about any command
  init                        Initialize Tendermint
...

Running Tendermint

  • We can initialize and run tendermint as follows,
$ tendermint init
...

$ tendermint node --consensus.create_empty_blocks=false

The argument --consensus.create_empty_blocks=false specifies that Tendermint should not commit empty blocks.

  • To reset all the data stored in Tendermint execute the following command,
$ tendermint unsafe_reset_all

Installing BigchainDB

To install BigchainDB from source (for dev), clone the repo and execute the following command, (it is better that you create a virtual env for this)

$ git clone https://github.com/bigchaindb/bigchaindb.git
...
$ git checkout tendermint
$ pip install -e .[dev]  #  or  pip install -e '.[dev]'  # for zsh

Running tests

To execute tests when developing a feature or fixing a bug one could use the following command,

$ pytest -v --database-backend=localmongodb

NOTE: MongoDB and Tendermint should be running as discussed above.

One could mark a specific test and execute the same by appending -m my_mark to the above command.

Although the above should prove sufficient in most cases but in case tests are failing on Travis CI then the following command can be used to possibly replicate the failure locally,

$ docker-compose run --rm --no-deps bdb pytest -v --cov=bigchaindb

NOTE: before executing the above command the user must ensure that they reset the Tendermint container by executing tendermint usafe_reset_all command in the Tendermint container.

Closing Notes

How to check bigchaindb upsert-validator:

  • Clean bigchaindb (bigchaindb drop, bigchaindb init) and execute bigchaindb upsert-validator B0E42D2589A455EAD339A035D6CE1C8C3E25863F268120AA0162AD7D003A4014 10
  • Start Tendermint
  • tendermint init
  • tendermint unsafe_reset_all
  • tendermint node --consensus.create_empty_blocks=false
  • Start BigchainDB with bichaindb start
  • Execute curl http://localhost:46657/validators