OneOps Manages OneOps
We have two separate instances of OneOps named prod and admin. They are in different regions, managing each other.
We did this by creating a seed environment from our qa env.
- The seed env created our first env: admin.
- Then we took a snapshot of the database in the seed env and shutdown the env.
- The admin env then created a prod env and restored the snapshot from the seed.
- When prod came up it had all the data to manage admin. This enabled prod and admin to manage each other.