iov-one / devnet-operations Goto Github PK

First deployment environment is dancenet but it should be easy to deploy it for all envs

• Database must be accessible by block-metrics
• Database must be accessible by quick-block-explorer

Notes:

• Ideally kustomize should handle this task easily.
• Call with Dave regarding this task is on the shared drive in Internal Communications > Meeting Notes > Back-end > 20191217 Devops discussion with Orkun

Please use bnsd v0.21.3 and tendermint v0.31.11.

depends on #44

First deployment environment is dancenet but it should be easy to deploy it for all envs.

My initial idea was to have both bns and bcp nets adjusted via kustomize from the same base manifests.

I've discussed this with @alpe and we came to a decision that it has to be 2 separate dirs, but @ethanfrey brought it up again and after some consideration I think it makes sense to use the same base manifests, because both apps are exactly the same, except for genesis and executable names, which are easily overridable via an overlay.

It seems easier to add a pvc to traefik and let it handle certificate renewals instead of manually doing it.

Depends on #45

First deployment environment is dancenet but it should be easy to deploy it for all envs

We are paying too much for our clusters. We don't need such powerful machines as n1-standard-4. Please migrate the nodes in dancenet to n1-standard-2 and record how you did it. The migration should not incur any downtime.

Commit 5314fb8 will increase the faucet credit amount. Please apply it to the cluster.

This is to cater for maintenance overlap between networks, when we have several different versions deployed at the same time.

Deploy wallet-demo v0.13.0 with this config (https://github.com/iov-one/wallet-demo/blob/master/config/production.json) to wallet.zebranet.iov.one

As requested by @webmaster128

Depends on #46