8a7650c13a
* Problem: `ValidatorElection` and `MigrationElection` need to inherit from a common `Election` class Solution: Factored the common logic out of `ValidatorElection` and moved it to `Election` parent class * Problem: Adding base58 as a requirement seems to break the build... Solution: Reverting the changes * Problem: Responding to a suggestion for improved method naming Solution: Refactored `get_result_by_election_id` to `get_election_result_by_id` * Problem: No need to store different types of elections in their own tables Solution: Remove `DB_TABLE` property from `Election` class * Revert "Problem: No need to store different types of elections in their own tables" This reverts commit db45374d3c690429d18a25bcc319f8056c016500. * Problem: Missed a method in `Bigchain` class when updating the naming for an election method Solution: Finished the refactoring * Problem: Need a table to store data for all elections Solution: Created the `elections` table with secondary_index `election_id` * Problem: `Election` class needs to be updated to store concluded elections in the `elections` table Solution: Updated the class to use the new table * Problem: `UpsertValidatorVote` can be generalized to just be `Vote` Solution: Renamed, refactored and moved the `Vote` class to tie in with the more general `Election` base class * Problem: Error in docstring return signature Solution: Fixed the docstring * Problem: Hardcoded reference to the `VOTE_TYPE` in `Election` base class Solution: Pointed the reference to the class variable * Problem: Schema still refers to `ValidatorElectionVote` instead of `Vote` Solution: Renamed `TX_SCHEMA_VALIDATOR_ELECTION_VOTE` as `TX_SCHEMA_VOTE` * Problem: `Election` class variable `ELECTION_TYPE` is overly specific Solution: Renamed `ELECTION_TYPE` to `OPERATION` * Problem: Command line options for `upsert-validator` can be generalized to manage any type of election Solution: Refactored the CLI to manage generalized elections * Problem: Default for `show_election` not implemented for `Election` class Solution: Create a default method that work if all fields in the 'asset[data]' can be displayed without additional formatting * Problem: Multiple small issues with style etc. Solution: Addressed comments from PR * Problem: `Election` class variable to `VOTE_TYPE` unnecessary Solution: Removed the variable and hardcoded everything to use the `Vote` class * Problem: Minor style issues with PR Solution: Addressing comments * Problem: Changes to format for validator keys broke some tests Solution: Aligned the tests to reflect the changed key format * Problem: `election show` command displaying the base56 public key Solution: Cast any public key to base64 * Problem: `election_parser` help message still refers to upsert-validator Solution: Updated the help message
7.5 KiB
Command Line Interface (CLI)
The command-line command to interact with BigchainDB Server is bigchaindb.
bigchaindb --help
Show help for the bigchaindb command. bigchaindb -h does the same thing.
bigchaindb --version
Show the version number. bigchaindb -v does the same thing.
bigchaindb configure
Generate a local configuration file (which can be used to set some or all BigchainDB node configuration settings). It will ask you for the values of some configuration settings. If you press Enter for a value, it will use the default value.
At this point, only one database backend is supported: localmongodb.
If you use the -c command-line option, it will generate the file at the specified path:
bigchaindb -c path/to/new_config.json configure localmongodb
If you don't use the -c command-line option, the file will be written to $HOME/.bigchaindb (the default location where BigchainDB looks for a config file, if one isn't specified).
If you use the -y command-line option, then there won't be any interactive prompts: it will use the default values for all the configuration settings.
bigchaindb -y configure localmongodb
bigchaindb show-config
Show the values of the BigchainDB node configuration settings.
bigchaindb init
Create a backend database (local MongoDB), all database tables/collections, various backend database indexes, and the genesis block.
bigchaindb drop
Drop (erase) the backend database (the local MongoDB database used by this node).
You will be prompted to make sure.
If you want to force-drop the database (i.e. skipping the yes/no prompt), then use bigchaindb -y drop
bigchaindb start
Start BigchainDB. It always begins by trying a bigchaindb init first. See the documentation for bigchaindb init.
The database initialization step is optional and can be skipped by passing the --no-init flag, i.e. bigchaindb start --no-init.
Options
The log level for the console can be set via the option --log-level or its
abbreviation -l. Example:
$ bigchaindb --log-level INFO start
The allowed levels are DEBUG, INFO, WARNING, ERROR, and CRITICAL.
For an explanation regarding these levels please consult the
Logging Levels
section of Python's documentation.
For a more fine-grained control over the logging configuration you can use the configuration file as documented under Configuration Settings.
bigchaindb election
Manage elections to manage the BigChainDB network. The specifics of the election process are defined in BEP-18, please refer it for more details.
Election management is broken into several subcommands. Below is the command line syntax for each,
election new
Create a new election which proposes a change to your BigChainDB network.
There are multiple types of election, which each take different parameters. Below is a short description of each type of election, as well as their command line syntax and the return value.
election new upsert-validator
Create an election to add/update/remove a validator from the validator set.
$ bigchaindb election new upsert-validator E_PUBKEY E_POWER E_NODE_ID --private-key PATH_TO_YOUR_PRIVATE_KEY
[SUCCESS] Submitted proposal with id: <election_id>
E_PUBKEY: Public key of the node to be added/updated/removed.E_POWER: The new power for theE_PUBKEY. NOTE, if power is set to0thenE_PUBKEYwill be removed from the validator set when the election concludes.E_NODE_ID: Node id ofE_PUBKEY. The node operator ofE_PUBKEYcan generate the node id viatendermint show_node_id.--private-key: The path to Tendermint's private key which can be generally found at/home/user/.tendermint/config/priv_validator.json. For example, to add a new validator, provide the public key and node id for some node not already in the validator set, along with whatever voting power you'd like them to have. To remove an existing validator, provide their public key and node id, and setE_POWERto0. Please note that the private key provided here is of the node which is generating this election i.e.
NOTE: A change to the validator set can only be proposed by one of the exisitng validators.
Example usage,
$ bigchaindb election new upsert-validator HHG0IQRybpT6nJMIWWFWhMczCLHt6xcm7eP52GnGuPY= 1 fb7140f03a4ffad899fabbbf655b97e0321add66 --private-key /home/user/.tendermint/config/priv_validator.json
[SUCCESS] Submitted proposal with id: 04a067582cf03eba2b53b82e4adb5ece424474cbd4f7183780855a93ac5e3caa
If the command succeeds, it will create an election and return an election_id. A successful execution of the above command doesn't imply that the validator set will be immediately updated but rather it means the proposal has been succcessfully accepted by the network. Once the election_id has been generated the node operator should share this election_id with other validators in the network and urge them to approve the proposal. Note that the node operator should themsleves also approve the proposal.
NOTE: The election proposal consists of vote tokens allocated to each current validator as per their voting power. Validators then cast their votes to approve the change to the validator set by spending their vote tokens.
election approve
Approve an election by voting for it. The proposal generated by executing bigchaindb election new ... can be approved by the validators using this command. The validator who is approving the proposal will spend all their votes i.e. if the validator has a network power of 10 then they will cast 10 votes for the proposal.
Below is the command line syntax and the return value,
$ bigchaindb election approve <election_id> --private-key PATH_TO_YOUR_PRIVATE_KEY
[SUCCESS] Your vote has been submitted
election_idis the transaction id of the election the approval should be given for.--private-keyshould be the path to Tendermint's private key which can be generally found at/home/user/.tendermint/config/priv_validator.json.
Example usage,
$ bigchaindb election approve 04a067582cf03eba2b53b82e4adb5ece424474cbd4f7183780855a93ac5e3caa --private-key /home/user/.tendermint/config/priv_validator.json
[SUCCESS] Your vote has been submitted
If the command succeeds a message will be returned stating that the vote was submitted successfully. Once a proposal has been approved by sufficent validators (more than 2/3 of the total voting power) then the proposed change is applied to the network. For example, consider a network wherein the total power is 90 then the proposed changed is applied only after 60 (2/3 * 90) have been received.
election show
Retrieves information about an election initiated by election new.
Below is the command line syntax and the return value,
$ bigchaindb election show ELECTION_ID
<election_data>
status=<status>
The election data is the same set of arguments used in the election new command that originally triggered the election. status takes three possible values, ongoing, if the election has not yet reached a 2/3 majority, concluded, if the election reached the 2/3 majority needed to pass, or inconclusive, if the validator set changed while the election was in process, rendering it undecidable.