Configuration fixes for mobymask-v2 stack for multiple deployments #318

2023-04-12T10:03:22Z

prathamesh0 commented

2023-04-12 10:03:22 +00:00

(Migrated from github.com)

Part of https://github.com/cerc-io/stack-orchestrator/issues/264

Even though the existing mobymask-v2 stack works as expected locally (singular deployment of the watcher and apps), we need few things described below in order to seamlessly deploy multiple instances with relay nodes in a federation:

Configurable announce domain for the relay node as it can vary across different servers
Configurable relay peers list for the relay node (for federated setup)
Peer ids for relay and peer nodes in mobymask-v2 watcher generated when required (instead of using hardcoded ones) and stored in a mounted volume for further usage

Part of https://github.com/cerc-io/stack-orchestrator/issues/264 Even though the existing `mobymask-v2` stack works as expected locally (singular deployment of the watcher and apps), we need few things described below in order to seamlessly deploy multiple instances with relay nodes in a federation: - Configurable announce domain for the relay node as it can vary across different servers - Configurable relay peers list for the relay node (for federated setup) - Peer ids for relay and peer nodes in mobymask-v2 watcher generated when required (instead of using hardcoded ones) and stored in a mounted volume for further usage

Sign in to join this conversation.

No reviewers

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/stack-orchestrator#318