November 2015 Summaries

In November 2015, Michael Richardson discussed a significant shift in Azure's resource management from Azure Service Management (ASM) to Azure Resource Manager (ARM), highlighting the implications for Octopus Deploy, which at the time interacted only with ASM. To support ARM, proposals included adding a new Azure Service Principal account type requiring Azure Active Directory authentication, and introducing a "Deploy Azure Resource Group" step for provisioning resources using JSON templates, which could dynamically adjust parameters based on various conditions. The proposed changes aimed to streamline the deployment process, allowing for validation against ARM to ensure JSON template correctness before deployment. Additionally, Richardson mentioned considerations about integrating templates from a Git repository and the gradual phasing out of Service Management API development by Microsoft, which underscored the growing importance of adapting to ARM for future Azure deployments.

Octopus Deploy has introduced IPv6 support in version 3.1.7, simplifying the process of configuring Tentacle deployments using the IPv6 protocol. Previously, setting up IPv6 required manual configuration, but now both Octopus Deploy Server and Tentacles operate in a dual-mode, listening to both IPv4 and IPv6 addresses simultaneously on the same port, thanks to the .Net 4.5 sockets update. This advancement alleviates concerns about running out of IPv4 addresses and allows for seamless integration by using Fully Qualified Domain Names (FQDNs) to resolve addresses, with the networking stack automatically determining the protocol to use. Users can specify IPv6 addresses directly in configurations or rely on DNS to handle protocol selection. The system is designed to fall back to IPv4 if necessary, ensuring broad compatibility, and users can choose to bind Tentacles exclusively to IPv4 if desired. The update is part of Octopus Deploy's ongoing efforts to modernize and improve infrastructure capabilities.