Reece Walsh on 06 Dec, 2017 05:38 AM
Thank you for getting in touch!
Deployment targets within Octopus refer to instances within a Tentacle agent.
You could have a single Tentacle agent installed on a machine for instance, and then have multiple instances setup which acts as 'deployment targets'
To answer your questions more specifically, two tentacles on one machine would mean two deployment targets as they would each identify with a unique thumbprint that Octopus will use to identify the target.
One Tentacle with multiple tenants still acts as a single deployment target, again as it still only identifies with a single instance/thumbprint.
From a licensing perspective if you had five machines with one Tentacle installed on each catering to four tenants you would be utilizing five deployment targets.
When adding a deployment target within Octopus you are able to select the following options;
Listening Tentacle (Connect to a machine via a Tentacle in Listening Mode, Listening Mode has the Tentacle Agent await instruction from the Server, having the firewall exceptions in place on the target machine)
Polling Tentacle (Connect to a machine via a Tentacle in Polling Mode, Polling Mode has the Tentacle Agent actively query the server via a firewall exception on the Server itself for instruction and is the most resource heavy option)
SSH Connection (Connect to a machine via Secure Shell (SSH))
Offline Package Drop (Configure a location to drop Offline Deployment Packages, Typically, we would only recommend this as an option in scenarios where installing Tentacle is not feasible from a security policy or compliance control perspective. The only other workaround would be to install Tentacle on the specified machines)
Cloud Region (A convenient way to model multiple geographic regions, though these do not count towards the target limit)
I hope this answers your query and provides some additional information.
If you have any further queries please let me know :)