Development/Playground Environment

hyperledger-labs / business-partner-agent

The Business Partner Agent is a SSI wallet and controller based on aries cloud agent python.

https://labs.hyperledger.org/business-partner-agent/

Apache License 2.0

56 stars 49 forks source link

Development/Playground Environment #45

Open domwoe opened 4 years ago

domwoe commented 4 years ago

As a (test) user and as a developer I want to have a local environment with 3 instances of the business partner agent.

A bank as issuer
A supplier that can request a verified bank account from the bank
A customer to send a presentation of the verified bank account to or that can request a verified bank account

Bank and Customer agents should get prepopulated with a suitable organizational profile

Issues / Things to think about

Do we need to start a local instance of the von network as well?
- If we don't, we need to create new seeds for each deployment. Otherwise agents from different deployments would overwrite themselves.

matgnt commented 4 years ago

Needs #60

domwoe commented 4 years ago

Can we learn something from the demo scripts of https://github.com/OpenMined/PyAriesFL ?

They are following the approach of the VON Team.

frank-bee commented 4 years ago

@domwoe looks nice this demo of the PyAriesFL project. I like especially how the describe the demo scenario with the overview image and so on, very straight and clear. Some remarks:

they use docker instead of docker-compose, which is what we use.
they do not need ingress & frontends? This is probably the most critical point for demos ( how to handle DNS, how do avoid NGROK,...)

My option you anyway know: let's go cloud native --> K8s

frank-bee commented 4 years ago

BTW, installing k8s locally is meanwhile very straight forward: https://ubuntu.com/tutorials/install-a-local-kubernetes-with-microk8s#2-deploying-microk8s

There isn't much of a difference compared to a docker-compose setup I'd say. And if comes with advantages , e.g.

monitoring , logging,... can easily be setup with third party tools ( helm charts ) or plugins https://ubuntu.com/tutorials/install-a-local-kubernetes-with-microk8s#3-enable-addons
setup is near to production
separation of components can be done with helm ( database, monitoring tools, maybe aries, ...)
handing of secrets and configuration is a first class citizen in K8s
technology is growing fast ...

The only downsides with a k8s setup I see:

Some developers are still unfamiliar with k8s
Development setup with debugging and so on is not straight forwards (https://www.telepresence.io/ seems to be a nice tool here)

domwoe commented 4 years ago

Removed the docker-compose in AC in issue. This needs probably split up further as @etschelp noted. There are different requirements for (test) users and developers.