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.

Sign up for GitHub

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

Jump to bottom

Refactor source to separate CHAIN deployments using LXD Projects. #25

Closed
farscapian opened this issue Apr 3, 2019 · 1 comment
Closed

Refactor source to separate CHAIN deployments using LXD Projects. #25

farscapian opened this issue Apr 3, 2019 · 1 comment
Assignees
@farscapian
Labels
enhancement New feature or request
Milestone
v0.0.1

Comments

@farscapian
Copy link
Collaborator

BCM should have the ability to deploy mainnet, testnet, and regtest environments natively. However, since these are technical separate trust networks, we should therefore avoid any overlap in running containers. That is, any component running on Testnet SHOULD be confined to data center workloads related to testnet.

LXD Projects provides a mechanism to perform this. Each chain will be classified under a distinct LXD project. CLI options will be created to get the current chain (get-chain) and set the chain (set-chain), which result in BCM scripts deploying to a different 'project'/CHAIN.
@farscapian farscapian self-assigned this Apr 3, 2019
@farscapian farscapian added the enhancement New feature or request label Apr 3, 2019
@farscapian farscapian added this to the v0.0.1 milestone Apr 3, 2019
@farscapian
Copy link
Collaborator Author

All issues are now going to be tracked directly in the codebase using # TODO stanzas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@farscapian farscapian

Labels
enhancement New feature or request
Projects
None yet
Milestone
v0.0.1
Development

No branches or pull requests
1 participant
@farscapian