We initially tested Octopus Deploy on a local server (not production quality), using the trial license (5 projects, 10 target servers). Everything went well, we’ve bought in to this technology. We purchased a full license and this is now on a new “production quality” server. I am working to migrate these projects from the local server to the new server.
FYI: for us, Production Quality Server means one that has sufficient redundant infrastructure support to run 24x7, along with typically higher CPU/RAM/Disk resources and with frequent backups to protect data. The local “development” server simply doesn’t meet this level.
The complication is that three of the five projects are actively being worked and pushing packages several times a day. The other two are quite right now and thus ideal to migrate as we will be able to test/exercise once on the new server. We wish to keep using the existing server for this deployment cycle for those active projects.
The backup from the original server is dependent on the master key. When we import to the new server using this master key, I am reading that we can continue to use this master key and thus the tentacles will continue to use the same thumbprint.
I know the new server already has its own “master key”.
- How do we tell this new server to use the old master key?
- Is that something that happens during the import?
We use listening tentacles.
- Will these tentacles get confused if the old servers is still in use while starting the new server?