![]() Roles are essentially dynamic labels you can assign to servers. You can then assign the new tentacle to an environment and a role. Once the tentacle is installed, you can attempt to discover the machine from your Octopus server interface. Octopus and Tentacle both have a public/private key pair, that they use to establish the HTTPS connection (one is the TLS server and presents a server certificate, the other is a TLS client and presents a client certificate).īack to the registration. Regardless of whether Tentacle is in listening mode or polling mode, all communication between the Tentacle and Octopus is performed over HTTPS. The Octopus documentation site mentions how communication between Octopus and the tentacles actually works ( link). If not, then your network team may have to reconfigure some security measures or create a new network configuration where all the tentacles have a way to communicate with the Octopus server. You should know in advance how your servers are currently communicating with one another within your organization beforehand so you can determine if there is even a path that the Octopus server can communicate with the tentacles. It’s meant to show that the Octopus server does not need one specific single port for tentacles to register to! Keep in mind this example drastically understates all the complexities between networks. For smaller organizations with less to manage, I imagine it’s not such a big deal. So what’s this mean for you? I had gone so far as to ask on the support forums just how ports worked in Octopus.įor large companies with numerous network restrictions, this is a huge feature. At first, I didn’t understand how this worked. One of the biggest features in Octopus isn’t given enough credit: the ability to have tentacles on different ports than the server itself. The recent project I had at a large client had numerous network configurations world-wide multiple zones and intricate port restrictions between said zones. Hit that button and your screen should appear similar to this: Once you’ve copied the thumbprint (from the Octopus server) to the listening tentacle, you should see another install button. If not, you may receive an error message when you try to register the tentacle. Make sure the port number is opened on your Windows Server firewall only on the tentacle itself and that the server itself can access the Octopus server. In that setup you’ll notice that a port was required as part of the installation. After the tentacle installation, there’s a setup wizard. Keep in mind firewall ports on the Octopus server do not have to match the tentacles and vice versa, they just need to have an open path to one another. The network path and firewall ports will simply make registering easier. Keep the thumbprints handy when registering the tentacles and server to each other.Make sure the firewall ports to be used on your server and tentacle are open.Make sure you have a clear network path to the server from the tentacle.When beginning your first Octopus Deploy installation, there are three things to keep in mind: Now to the good stuff registering tentacles with Octopus. If you have no preference, go with listening. I’ve never tried polling, nor do I see any need to at this point. Installation note: While installing the tentacle, they’ll recommend using a listening mode (push) rather than polling mode (pull) system of communication. The tentacle instructions are readily available on the same site as well: Rather than reiterate the obvious, I’ll just focus in on the registering of tentacles and server. In fact, the folks at Octopus Deploy already have a nice video on how to install the server here: I’ll address the packages in another article and skip dealing with installing both components as it’s very straightforward. There are essentially four aspects of installation and configuration: installing the Octopus server, the Octopus agent (or tentacle), registering both components with each other and storing your packages. ![]() TL DR I’m diving into registering tentacles and servers as that’s the most challenging part in an Octopus Deploy installation if you’re unfamiliar with the terrain. I’ll address some possible issues that may crop up and how to avoid them. I’m not going into great detail how to install the server and tentacles as it’s pretty simple and there are documents direct from Octopus Deploy’s documentation site on how to do so. Updating Octopus Deploy is a slightly different story, but I’ll address that in another article. Installing Octopus Deploy is a fairly trivial task.
0 Comments
Leave a Reply. |