WIP: Launch 3-component deployment using docker-compose.yml #1300
Conversation
riconnon
force-pushed
the
experiment/rconnon/components
branch
from
edb6275
to
45e35bf
Compare
|
I think it would be good to maintain the single-container model for fnserver if possible, even if internally the container was running three processes - it keeps the black box simple and consistent for the user. |
|
it should be possible to do this all in a single process, too, there's some... factoring issues... to solve. |
| - fnserver | ||
| - api | ||
| - lb | ||
| - runner | ||
| volumes: | ||
| - ./examples/grafana/prometheus.yml:/etc/prometheus/prometheus.yml | ||
| fnserver-ui: |
There was a problem hiding this comment.
let's exclude the UI component, because it doesn't work =(
| lb: | ||
| restart: always | ||
| depends_on: | ||
| - db |
There was a problem hiding this comment.
should also depend on api node.
| build: . | ||
| networks: | ||
| - fn-network | ||
| build: |
There was a problem hiding this comment.
Network attribute was necessary to let functions be within the Fn network, and the idea was to have a flat network where each component has a binding.
|
As for testing, i'm getting |
|
Let's do the following, I'd rather get rid of compose file and use OSS helm charts. @riconnon thoughts? |
I thought I'd experiment with launching a 3-component deployment as a local environment using docker-compose
Interested to know what people think.