October 2014 Summaries

Paul Stovell, founder and CEO of Octopus Deploy, announces the integration of the Octopus Deploy Tentacle agent as an extension for Azure VMs, as revealed by Scott Guthrie. This extension simplifies the deployment of ASP.NET web applications, Windows Services, and other applications by automating the configuration of IIS, the installation of services, and necessary configuration changes. Previously, Tentacle could be installed manually or via scripts, but the new extension offers a user-friendly interface utilizing an open-source PowerShell DSC resource. The integration addresses a popular request on Azure UserVoice and enhances the deployment and configuration process on Azure VMs by providing a seamless way to deploy applications, addressing the limitations of a standard Azure VM setup that only includes an operating system, remote desktop, and PowerShell remoting connection. For users interested in leveraging the extension, additional documentation is available, including instructions for command-line installation via PowerShell.

In 2014, Microsoft announced a partnership with Docker to integrate Docker's open-source container technology into Windows Server, allowing developers to create distributed, container-based applications compatible with various programming languages, including .NET. This integration is set to offer significant benefits, such as improved application isolation and resource efficiency compared to traditional virtual machines. The article explores potential deployment strategies using Docker with Octopus Deploy, a deployment automation tool, highlighting different approaches like treating Docker as an infrastructure concern, building new images per deployment, or creating images per release to maintain consistency across environments. While Docker simplifies application packaging and deployment, Octopus continues to provide orchestration capabilities for managing complex deployment processes. The discussion also addresses the potential impact of Docker on Azure cloud service projects and the evolving ecosystem of Windows Server with Docker support.

A newly identified security vulnerability known as POODLE primarily affects connections using SSL 3.0, which can be avoided by disabling the protocol in both clients and servers. In the context of Octopus Deploy, a tool for managing software deployments, the risk is mitigated by specifically using TLS 1.0 for secure communication between the Octopus server and Tentacle deployment agents, bypassing SSL 3.0 entirely. This approach has been in place since the release of an open-source project called Halibut in 2013, which laid the foundation for Octopus's communication stack. However, the Octopus web portal, running on IIS and HTTP.sys, could potentially be vulnerable if exposed over HTTPS unless SSL 3.0 is disabled via registry changes or Group Policy, as recommended by Microsoft.

Henrik Andersson's blog post from October 2014 details the process of deploying an ASP.NET MVC application to Azure Web Apps using Octopus Deploy 3.0, which at the time had recently added support for Azure Web Apps. Due to the absence of out-of-the-box functionality for deploying Azure Web Sites directly from Octopus, a step template involving a PowerShell script and Web Deploy is utilized. The post guides readers through setting up a demo ASP.NET MVC application in Visual Studio 2013, creating a NuGet package with OctoPack, and modifying project files to automate package generation. It further explains setting up an Azure Web Site, importing a Web Deploy step template into Octopus, and configuring project variables and deployment processes. The blog post concludes with instructions on creating and deploying a release to Azure, as well as updating and redeploying the application with modifications.

Octopus Deploy offers a versatile software deployment solution, notably supporting scripting within the deployment process, which enables extensive flexibility. A recent enhancement to the Octopus Deploy Library is the Microsoft Software Installer (MSI) Step template, designed to facilitate the installation, repair, or removal of MSI files on systems. This template necessitates Windows Installer 3.0 on the target machine and supports only quiet installations, running with the norestart flag. For effective deployment, MSI installers must be packaged inside an Octopus Deploy NuGet package, which can be created using the octo.exe pack command. The process involves importing the step template into the local Octopus Deploy instance and configuring it with the necessary MSI path, installer actions, and properties, after which the deployment can proceed seamlessly.