Managed LASR Deployments Orchestration

[mattgeddes]

This is a (very) high level issue to group together tasks involved in orchestration for a production-ready, managed deployment of LASR. Part of which exists already, some functionality is planned and some requirements are likely still unknown. As we scale past a single, shared and hand-curated node, it becomes more and more critical that we're able to manage all of the nodes and environments through orchestration to keep the deployments consistent and to reduce the overhead in managing them in the field.

A secondary use case also exists. As we look to onboard partners as node operators, having some reusable orchestration will allow them to quickly stand up nodes in their environment and join the network.

Here are the subtasks representing specific chunks of functionality:

• Orchestration of LASR container repo #115
• Orchestration of LASR base image(s) pull #116
• Orchestration of LASR private TLS CA #117
• Orchestration of IPFS instance on separate node #118
• Create orchestration to deploy/maintain single MongoDB instance #125
• Update orchestration to support MongoDB scale-out #126
• Make Prometheus Exporter labels consistent across the board #129

Issues #125 and #126 are linked both to this issue, as well as #119 .