Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tezos-proto-cruncher chart #532

Merged
merged 9 commits into from
Jan 26, 2023
Merged

tezos-proto-cruncher chart #532

merged 9 commits into from
Jan 26, 2023

Conversation

nicolasochem
Copy link
Collaborator

This chart deploys a daemonset in your cluster. the daemonset runs a parallel search for a vanity protocol hash.

It takes s3 bucket credentials. Protocol is downloaded from bucket then results are written to the bucket.

It does not terminate: it keeps running until the cluster is torn down.

This chart deploys a daemonset in your cluster. the daemonset runs a
parallel search for a vanity protocol hash.

It takes s3 bucket credentials. Protocol is downloaded from bucket then
results are written to the bucket.

It does not terminate: it keeps running until the cluster is torn down.
@harryttd
Copy link
Collaborator

Suggestion: explain how to uninstall the chart in the medium article when it isn't needed anymore

@nicolasochem nicolasochem merged commit 47fd4a4 into master Jan 26, 2023
@nicolasochem nicolasochem deleted the tezos-proto-cruncher branch January 26, 2023 23:24
Sachito18 added a commit to smart-chain-fr/tezos-k8s that referenced this pull request Jan 27, 2023
* Exit config-init script on error (oxheadalpha#531)

* Exit config-init script on error

* Update chart tests

* Set fitness to 1 instead of -1 at activation (oxheadalpha#534)

A bug was uncovered during mumbai activation, where nodes were unable to
activate and were crashing.

The [fix](https://gitlab.com/tezos/tezos/-/merge_requests/7462/diffs)
broke dailynet because it is no longer possible to activate with a
fitness of -1 (which is how we have been activating chains since the
beginning of tezos-k8s).

Replacing this value to 1 fixes the issue for dailynet and also does not
appear to be causing any issue with v15.1.

* tezos-proto-cruncher chart (oxheadalpha#532)

* tezos-proto-cruncher chart

This chart deploys a daemonset in your cluster. the daemonset runs a
parallel search for a vanity protocol hash.

It takes s3 bucket credentials. Protocol is downloaded from bucket then
results are written to the bucket.

It does not terminate: it keeps running until the cluster is torn down.

* better variable names

* Update charts/tezos-proto-cruncher/scripts/proto-downloader.py

Co-authored-by: Aryeh Harris <harryttd@users.noreply.github.com>

* address review comments

* lint python scripts with black

* catch exception when s3 upload fails

* fix manual method

* fix manual method, better way per Aryeh

* fail fast when env vars not set in proto downloader

Co-authored-by: Aryeh Harris <harryttd@users.noreply.github.com>

Co-authored-by: Aryeh Harris <harryttd@users.noreply.github.com>
Co-authored-by: Nicolas Ochem <nicolas.ochem@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants