June 2022 Summaries

Bob Walker shares insights and recommendations on creating runbooks using Octopus Deploy, focusing on a specific case of backing up SQL Server databases to a NAS. He emphasizes the importance of understanding the problem, defining requirements, and considering factors like use cases, workflow, permissions, and notifications before starting. Walker details his experience with Octopus Deploy, highlighting challenges such as the system's initial limitations in database backup processes and how to overcome them by using configuration options like JSON. The runbook he designed aims for simplicity and efficiency, running automatically across all environments with necessary approvals and notifications to maintain security and performance. He advises grouping generic runbooks into specific projects, setting appropriate retention policies for logs, and emphasizes collaboration between developers and operations during the runbook design phase for more robust and supportable processes.

The blog post by Sarah Lean discusses the integration of Azure Bicep files with GitHub and Octopus Deploy for automating infrastructure deployments using source control and GitHub Actions. It highlights the benefits of using source control for Infrastructure as Code (IaC), such as providing a single source of truth, enabling collaboration, and tracking changes. The process involves storing Bicep files in GitHub, using GitHub Actions to automate their transfer to an Octopus Deploy instance, and setting up a GitHub Actions workflow to zip the files and push them to Octopus. The workflow relies on creating secrets for connection details to Octopus, and the steps include checking out code, installing the Octopus CLI, and executing commands to pack and push the Bicep files. The article concludes by emphasizing the streamlined deployment process and encourages feedback from readers.

Microsoft introduced Bicep in late 2020 as a Domain-Specific Language (DSL) designed to simplify the deployment of Azure resources, offering a modular and reusable approach that is popular within the IT community. As of version 0.3, Bicep is fully supported for production use, and this article provides a comprehensive guide on creating and deploying Bicep templates using Octopus Runbooks. The guide assumes familiarity with Azure Resource Manager (ARM) templates and walks through the process of setting up an Azure App Service Plan and a Linux Web App using Bicep, detailing parameter declaration, resource configuration, and deployment steps. To automate deployment, the Bicep template is packaged into a ZIP file and uploaded to Octopus Deploy, where users define deployment variables and employ Azure CLI scripts to execute the deployment process. The article encourages further exploration of Bicep modules for complex deployments and offers community support for users seeking assistance.

In an interview with Shipra Mahindra, a Senior Product Manager at Octopus Deploy, she discusses her career path, which began as a software engineer and evolved through roles like Scrum Master and Product Owner, eventually leading her to pursue an MBA to enhance her decision-making skills. Her passion for solving complex, customer-centric problems led her to product management, where she enjoys bringing clarity to ambiguity and collaborating with teams to deliver customer-pleasing solutions. As a Senior Product Manager for Configuration as Code, her role involves a dynamic routine of customer interactions, market research, and ideation with design and development teams to enhance product value. She emphasizes the importance of prioritization based on customer feedback and market trends, aiming for a 60% feature adoption rate, and evaluates success by aligning outcomes with set goals. Despite the challenges, she finds satisfaction in the role and expresses no desire to switch jobs, though she would consider a design role if necessary, given its similarity to product management.

The ServiceNow integration for Octopus, available as an early access preview, streamlines change management for DevOps teams by automating the creation and approval processes of change requests, reducing system downtime risks associated with unapproved deployments. By linking Octopus deployments to approved ServiceNow change requests, the integration ensures compliance with company policies and regulatory requirements, while offering a full audit log of deployments for enhanced control. This integration minimizes manual interventions, allowing for automated approval processes, and provides the flexibility to reuse change requests across multiple projects and environments. Set up is simplified with minimal configuration required in ServiceNow, and users can create or use existing change requests, with deployments proceeding only after necessary approvals are in place. The integration aims to alleviate the challenges of manual change management, inviting users to participate in the early access program and contribute feedback for further enhancements.

The Octopus 2022 Q2 release introduces a range of enhancements aimed at supporting cloud-native deployments and modernizing CI/CD pipelines, particularly for teams using a mix of modern and legacy technologies. Key features include improved support for deploying containerized applications to Amazon ECS and Kubernetes, enhanced serverless capabilities for AWS, and the introduction of cloud target discovery. The release also focuses on Config as Code usability improvements, faster deployments with improved caching for Octopus Cloud, and customer-driven updates such as customizable Project and Space icons and improved security administration. Additionally, the release integrates ServiceNow Change Management to streamline change request processes, and supports OAuth 2.1 Authorization Code Flow with PKCE for improved security. These updates aim to facilitate a smooth transition to modern infrastructure while maintaining existing systems, offering flexibility and ease of use in managing complex deployment scenarios.

Octopus Workflow Builder is a tool designed to simplify the setup of modern continuous delivery workflows by providing a streamlined process for deploying applications to cloud platforms such as EKS, ECS, and AWS Lambdas. Users can select their desired platform, input their Octopus cloud instance and AWS credentials, and authorize the creation of a GitHub repository that includes sample web applications, Terraform configuration files, and GitHub Actions workflows. These resources populate the Octopus instance with necessary deployment projects, environments, and security scanning setups, offering an opinionated CI/CD workflow for real cloud-based applications. This tool aims to reduce the complexity and time required for setup, giving users complete control over customization while seeking feedback to improve its functionality.

In a detailed exploration of backup procedures, the text underscores the importance of not only creating and storing data backups but also verifying them through a robust, automated process. It highlights common oversights in backup strategies, particularly the lack of a verification process to ensure that the right data in the correct format is being backed up. The suggested approach involves treating backups as versioned artifacts, similar to software deployments, and automating the restoration process in a disposable environment using tools like Docker. This method allows DevOps teams to routinely rehearse backup restorations, ensuring that recovery processes are well-practiced and reliable, thus minimizing uncertainties during actual data loss scenarios. The text also presents a practical runbook example that demonstrates how to generate, store, and verify database backups using automation tools, thereby integrating backup verification into the regular backup lifecycle.

AWS Lambda is a serverless Function as a Service (FaaS) that offers scalable, cost-effective deployment solutions by allowing resources to scale to zero when not in use. This post guides users through deploying a simple Lambda using AWS CloudFormation, including setting up essential resources like log groups and IAM roles for monitoring purposes. It extends to a more intricate example where a Lambda is deployed within a Virtual Private Cloud (VPC) that incorporates both private and public subnets, enabling Lambda to interact with resources like databases and EC2 instances. The deployment involves configuring network access through security groups, demonstrating how to manage network traffic and resource interactions within a VPC. The article emphasizes the simplicity of deploying basic Lambdas and the flexibility of configuring more complex deployments requiring VPC access, providing readers with practical insights into AWS infrastructure setup.

Amazon Relational Database Service (RDS) offers a managed, scalable, and highly available database platform that supports several popular database providers such as MySQL, MariaDB, Oracle, Postgres, and SQL Server. The article explains how to deploy an RDS instance using a CloudFormation template, which includes creating a new Virtual Private Cloud (VPC) with two private subnets and configuring various resources such as security groups and a subnet group to support the RDS instance. The security group setup allows network access to the RDS instance, ensuring that resources within the VPC can communicate with it while maintaining security by not allowing public IP addresses for serverless Aurora clusters. This setup is part of a broader series discussing CloudFormation templates and VPCs, providing insights into the deployment of a serverless Aurora RDS instance with ready-to-attach security groups for additional resource access.

Operations Runbooks in Octopus enhance DevOps by facilitating management and maintenance tasks outside of traditional deployment processes, allowing for a more comprehensive approach to infrastructure management. This capability is particularly valuable in Kubernetes environments, where linting tools like DigitalOcean's Clusterlint can be integrated to automate best practice checks and provide feedback loops for continuous improvement. By running these checks as part of an automated workflow via runbooks, users can schedule regular diagnostics without impacting active deployments, thus reducing errors and improving cluster management. Runbooks also support robust reporting mechanisms, enabling the sharing of lint results through various communication channels, and can be scaled to a production-ready solution with features like security, logging, auditing, and scheduling. The introduction of runbooks in Octopus represents a significant shift in automating and simplifying the complexities associated with Kubernetes management, providing a foundation for scalable and repeatable infrastructure operations.