Installing Octopus Deploy
Adventures in automated deployment
February 26, 2014Now that I have two VMs setup inside of azure it is time to install Octopus Deploy to begin my attempt at automated deployment. I am going to show the basic steps I went through to see if I can figure things out without reading my documentation (for now).
Install The Server
License and download
The first thing have to do is get a trial license to octopus so I can install the server. This license was obtained on the website here . When you submit the form you can download the server install here .
Run the installer
I like installers like this, no configuration, just a simple install location!
Getting Started
Now that we have it installed let's see what we need to do next to get things running. Here are the screens I captured during the server install process.
Welcome
License
Simply paste in the license you received via email into the text area.
Storage
I changed the value to D:\Octopus
not really sure why I did this but felt like a good idea.
Web Portal
I left the default settings for the web portal since I have nothing else installed on this fresh azure vm.
Authentication
Since I have only two simple vms azure I decided to go with the username/password authentication. When we install this on the production server we will probably leverage active directory.
Install
The one thing I thought was interesting is the ability to view the install script which means you must be able to install this via command line which is cool.
Manager
After you have it all installed you are presented with a manager window for the Octopus Server.
Now that we have this installed let's see how we install a tentacle.
Install A Tentacle
Download tentacle software
If you go back to the download page, download, and install the tentacle. Once again no configuration during setup, nice!
Screens captured during the tentacle setup.
Welcome
Storage
I let these values as the defaults for now and will need to do a bit more research on what these values mean for a production install.
Communication
This is the one setting I decided to research to understand the difference between listening or polling. The documentation and install recommends listening as it is less cpu intensive. Next screen asks for the thumbprint value which can be obtained from the octopus server, so back to the server we go.
Add Environment on Octopus Server
Since this is a fresh install I was able to click on Environment and create an Octopus environment.
Add Machine to Environment
Once I had an environment setup now I need to add a machine to that environment. This step also displays the thumbprint value mentioned in the tentacle install.
Back to Tentacle Configuration
With the newly obtained thumbprint value I pasted the value into the tentacle configuration.
Install
Now we are able to install the tentacle configuration.
Manager
After the configuration is applied we are displayed a similar manager screen for the tentacle.
Back to Server
Now that the tentacle is configured I clicked on "Discover" to connect the Server to the Tentacle. I did run into an error the first time because my fresh VM didn't have the port opened up for the communication from the server to the tentacle. To fix simply open up Windows Firewall and allow communication over the port you configured
Configured
It now looks like we have an Octopus Server and one tentacle configured. This wasn't hard at all.
Conclusion
So far installation was painless and very straight foreword. This is the first step for my goal of automated deployment. Next up let's see what this thing can do, but for now I will consider this a win for tonight!
Cover image credit: http://facebook.com/RodrigoMoraesPhotography