Concept of a gateway server so I only have to open one firewall hole per datacenter
Concept of a gateway server so I only have to open one firewall hole per datacenter I want to deploy to. The gateway would listen say on port 10935 for an OD server that is aware of the tentacles in the gateways private network. The gateway would then receive the project and related files and pass them on to the tentacle if it was coming from the OD server. The gateway would receive status from the tentacle and report back to the OD server.
Tim
shared this idea
Octopus 3.4 shipped a little while ago and includes support for setting up a proxy server that is used by Octopus when connecting to Tentacles. You could use this to set up a proxy server in the data center, and only allow Octopus to connect to it, and from there to access the Tentacles. Here’s the documentation showing how this feature works: http://docs.octopusdeploy.com/display/OD/Proxy+Support
-
Peter Mourfield
commented
This would really help me out. Right now I have to deploy to Y number of datacenters with Z number of servers. It is not realistic for me to put a tentacle on each server in a datacenter because this would result in a package being uploaded Y * Z times, slowing the process and consuming a lot of bandwidth. A gateway or 'octo-proxy' ;) could help with this problem.
One solution I have considered would be to host a nuget feed in each datacenter that the server uploads release packages to as a part of a deploy. Next, each tentacle in the datacenter is configured to pull release packages from their local nuget feed. Right now I have to host a single tentacle in each datacenter then use powershell to deploy to each server. Not ideal.