add Nomadic's and BCD tezos indexers #166
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Both indexers are able to index a private chain. BCD indexer needs private images with env variables to set the hostname for elastic/db/rabbitmq. Next release of BCD hub will have them, until then it is necessary to build your own containers: baking-bad/bcdhub#554 The indexer need to be activated in values.yaml and does not run by default. The default values.yaml has an explanation in comments.
My immediate need is to deploy an archive node; I need 300Gi of storage.
│ The files belonging to this database system will be owned by user "postgres". │ This user must also own the server process. │ The database cluster will be initialized with locale "en_US.utf8". │ The default database encoding has accordingly been set to "UTF8". │ The default text search configuration will be set to "english". │ Data page checksums are disabled. │ initdb: error: directory "/var/lib/postgresql/data" exists but is not empty │ It contains a lost+found directory, perhaps due to it being a mount point. │ Using a mount point directly as the data directory is not recommended. │ Create a subdirectory under the mount point. │ stream closed
harryttd
reviewed
Apr 5, 2021
harryttd
reviewed
Apr 5, 2021
harryttd
reviewed
Apr 5, 2021
harryttd
reviewed
Apr 5, 2021
There is no version 3.5.2 of containers.
harryttd
reviewed
Apr 9, 2021
charts/tezos/templates/static.yaml
Outdated
| selector: | ||
| app: tezos-baking-node | ||
| app: tezos-node |
There was a problem hiding this comment.
what happens if there is only a baker in the cluster and no reg nodes?
chain-init needs to look for a baker, not a reg node. Hmmmm, well chain-init is a job and as of now every pod has all of the keys imported on it (for sk's this should change). So it would likely still activate the chain even if there is only a single reg node.
Shouldn't a baker be a more reliable source for RPC?
We should be able to select multiple apps if desired.
There was a problem hiding this comment.
Just tried on latest commit 02a4bb3 on branch indexer_new, and in minikube. It breaks bec job can't find the activation key.
>>>>1: http://tezos-node-rpc:8732/chains/main/blocks/genesis/protocols
<<<<1: 200 OK
{ "protocol": "PtYuensgYBb3G3x1hLLbCmcav8ue8Kyd2khADcL5LsT5R1hcXex",
"next_protocol": "PtYuensgYBb3G3x1hLLbCmcav8ue8Kyd2khADcL5LsT5R1hcXex" }
Error:
Erroneous command line argument 9 (tqtezos_baker_0).
no secret_key alias named tqtezos_baker_0
cannot read file (Unix.Unix_error(Unix.ENOENT, "open", "tqtezos_baker_0"))
Error while parsing URI: SK_URI needs a scheme
There is currently no headless service for them.
Indexer + Baker/Node and Services updates
harryttd
reviewed
Apr 19, 2021
| storage: "300Gi" | ||
| --- | ||
| apiVersion: v1 | ||
| kind: ConfigMap |
Bcd indexer updates
Templatize storageClassName for bcd indexer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Both indexers are able to index a private chain.
BCD indexer needs private images with env variables to set the hostname for elastic/db/rabbitmq. Next release of BCD hub will have them, until then it is necessary to build your own containers:baking-bad/bcdhub#554The indexer need to be activated in values.yaml and does not run by default. The default values.yaml has an explanation in comments.