search

keep-network / local-setup

Allow to easily set up tBTC and Keep locally for development and test purposes.
MIT License
8 stars 16 forks source link

Kubernetes deployment for large-scale network tests #41

Open lukasz-zimnoch opened 4 years ago

lukasz-zimnoch commented 4 years ago

This pull request introduce a config generator that allows producing an arbitrary number of accounts for the local Ethereum network along with their corresponding keep-core and keep-ecdsa config files. This feature is useful for large-scale network tests because there is no need to create multiple accounts and config files manually. Apart from that, a new version of the e2e test cron job was prepared for the keep-dev environment and auxiliary non-generated k8s configs were created for Ethereum and Bitcoin local networks.

Shadowfiend commented 4 years ago

Let's stick to the structure Sloan has across repos here if we can:

infrastructure/
  kube/ # deployment/system type
    local/ # environment
      <resource-name>-<index-when-applicable>-<resource-type>.yaml # .yaml as extension

e.g. see https://github.com/keep-network/keep-core/tree/master/infrastructure/kube/keep-dev

Ultimately I want us to also be thinking about how we can put the resource definitions in the repos, and leave only the orchestration in this repo---but that can come much later.

EDIT: I finished reading the description and wanted to flag that the environment in this case is keep-dev, not local, but if we were setting up sibling configurations for a local deployment it would be local :grimacing:

lukasz-zimnoch commented 4 years ago

Let's stick to the structure Sloan has across repos here if we can:

infrastructure/
  kube/ # deployment/system type
    local/ # environment
      <resource-name>-<index-when-applicable>-<resource-type>.yaml # .yaml as extension

e.g. see https://github.com/keep-network/keep-core/tree/master/infrastructure/kube/keep-dev

Ultimately I want us to also be thinking about how we can put the resource definitions in the repos, and leave only the orchestration in this repo---but that can come much later.

EDIT: I finished reading the description and wanted to flag that the environment in this case is keep-dev, not local, but if we were setting up sibling configurations for a local deployment it would be local 😬

Sure, I'll adjust the code at the end.