Responses to review comments from @krish7919 on #1526

This commit is contained in:
Troy McConaghy 2017-06-09 14:32:39 +02:00
parent e1082af385
commit 945ed81038
3 changed files with 16 additions and 9 deletions

View File

@ -1,5 +1,5 @@
How to Configure Your BigchainDB Node How to Configure a BigchainDB Node
===================================== ==================================
This page outlines the steps to set a bunch of configuration settings This page outlines the steps to set a bunch of configuration settings
in your BigchainDB node. in your BigchainDB node.
@ -23,6 +23,12 @@ That file already contains many comments to help you
understand each data value, but we make some additional understand each data value, but we make some additional
remarks on some of the values below. remarks on some of the values below.
Note: None of the data values in ``config-map.yaml`` need
to be base64-encoded. (This is unlike ``secret.yaml``,
where all data values must be base64-encoded.
This is true of all Kubernetes ConfigMaps and Secrets.)
vars vars
~~~~ ~~~~
@ -53,12 +59,12 @@ of all *other* nodes in your BigchainDB cluster
* If you're deploying the first node in the cluster, * If you're deploying the first node in the cluster,
the value should be ``""`` (an empty string). the value should be ``""`` (an empty string).
* If you're deploying the second node in the cluster, * If you're deploying the second node in the cluster,
the value should be one public key inside double quotes the value should be one public key inside double quotes.
(*not* base64-encoded). For example, For example,
``"EPQk5i5yYpoUwGVM8VKZRjM8CYxB6j8Lu8i8SG7kGGce"`` ``"EPQk5i5yYpoUwGVM8VKZRjM8CYxB6j8Lu8i8SG7kGGce"``
* If there are two or more other nodes already in the cluster, * If there are two or more other nodes already in the cluster,
the value should be a colon-separated list of public keys the value should be a colon-separated list of public keys
inside double quotes (with no base64 encoding anywhere). inside double quotes.
For example, For example,
``"DPjpKbmbPYPKVAuf6VSkqGCf5jzrEh69Ldef6TrLwsEQ:EPQk5i5yYpoUwGVM8VKZRjM8CYxB6j8Lu8i8SG7kGGce"`` ``"DPjpKbmbPYPKVAuf6VSkqGCf5jzrEh69Ldef6TrLwsEQ:EPQk5i5yYpoUwGVM8VKZRjM8CYxB6j8Lu8i8SG7kGGce"``

View File

@ -101,7 +101,7 @@ That means you can visit the dashboard in your web browser at
Step 3: Configure Your BigchainDB Node Step 3: Configure Your BigchainDB Node
-------------------------------------- --------------------------------------
See the page titled :ref:`How to Configure Your BigchainDB Node`. See the page titled :ref:`How to Configure a BigchainDB Node`.
Step 4: Start the NGINX Service Step 4: Start the NGINX Service

View File

@ -1,3 +1,5 @@
## Note: data values do NOT have to be base64-encoded in this file.
## vars is common environment variables for this BigchaindB node ## vars is common environment variables for this BigchaindB node
apiVersion: v1 apiVersion: v1
kind: ConfigMap kind: ConfigMap
@ -31,8 +33,7 @@ metadata:
name: bdb-keyring name: bdb-keyring
namespace: default namespace: default
data: data:
# Colon-separated list of all *other* nodes' BigchainDB public keys # Colon-separated list of all *other* nodes' BigchainDB public keys.
# with no base64 encoding anywhere
bdb-keyring: "<':' separated list of public keys>" bdb-keyring: "<':' separated list of public keys>"
--- ---
apiVersion: v1 apiVersion: v1
@ -41,6 +42,6 @@ metadata:
name: bdb-public-key name: bdb-public-key
namespace: default namespace: default
data: data:
# BigchainDB public key of *this* node, not base64-encoded. # BigchainDB public key of *this* node.
# Example: "EPQk5i5yYpoUwGVM8VKZRjM8CYxB6j8Lu8i8SG7kGGce" # Example: "EPQk5i5yYpoUwGVM8VKZRjM8CYxB6j8Lu8i8SG7kGGce"
bdb-public-key: "<public key>" bdb-public-key: "<public key>"