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

document for production deployment of Vault engine #340

Open
sichen1234 opened this issue Nov 3, 2021 · 3 comments
Open

document for production deployment of Vault engine #340

sichen1234 opened this issue Nov 3, 2021 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation fabric mentorship-cactus

Comments

@sichen1234
Copy link
Contributor

Please provide documentation on how to set up and deploy Vault engine in a production setting.

For example, should there be a separate Vault engine for each Fabric node?

Are there deployment scripts or documentation available?

@sichen1234 sichen1234 added mentorship-cactus documentation Improvements or additions to documentation fabric labels Nov 3, 2021
@Zzocker
Copy link
Member

Zzocker commented Nov 3, 2021

@sichen1234 I had already add a documentation for this, here : https://github.com/hyperledger-labs/blockchain-carbon-accounting/tree/main/utility-emissions-channel/minikube-setup

It uses mini-kube for the deployment of vault server in Kubernetes.

@sichen1234
Copy link
Contributor Author

@udosson What do you think about this? Should we do it this way for our emissions network?

@udosson
Copy link
Member

udosson commented Nov 8, 2021

The documentation looks good to me. We could do this for our emissions network. This could however require starting the network from scratch. @Zzocker what steps do you think should we follow to switch our cloud deployment from "native" fabric to the vault enhanced version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation fabric mentorship-cactus
Projects
None yet
Development

No branches or pull requests

3 participants