We are reviewing Octopus as a potential solution to automate our deployment between multiple data centers in different countries. The most interesting concept to us will be to test out the Process of a Project in testing environments before we take it to live environments. Assuming there will naturally be network segregation between the data centers, what would be a recommended architecture? We could think of a few different ways but would appreciate your help to better understand their pro and cons:
Create 1 RavenDB in each location and match an Octopus Deployment server on it. But our understanding is that there is no way for us to export/import Process of Projects without wiping the variables that will be managed locally in this case.
Use a single RavenDB, manage all environment variables from all data centers in it. Stand up 1 Octopus Deployment server in each data center that all share this remote RavenDB. We have yet to find documentation suggesting that this is an Octopus supported architecture.
Use a single RavenDB and a singleton Oct Deployment server. But we are worried about the network/internet across continents becoming a dependency during deployment window.
My apology if this is already documented somewhere. Your advice is truly appreciated.