The holiday season accentuates the need for IT agility and flexibility, especially within the retail, hospitality and travel industries.
However, this need is equally as important for any business that experiences variable demand or events that require a rapid rollout of new services.
With some basic planning, you can automate the process of secure app and infrastructure provisioning and delivery. This blog post is a quick guide on how you can build a continuous deployment (CD) pipeline process with IBM Cloud Pak for Watson AIOps and how to implement all the IT processes for secure delivery with just a few clicks (without IT involvement).
Traditionally, developers would be required to use service portals like ServiceNow to request virtual machines (VMs) and storage to deploy applications. Today, IT teams are automating this process with Infrastructure as Code and auto-scaling automation in response to these pressures to help accelerate continuous deployment of critical apps and services. This also ensures reliability in the whole stack — from applications to infrastructure. In doing so, businesses can leverage the same workflows used to ensure security and audit requirements, while accelerating the deployment of code and removing risk.
Combining Infrastructure Automation (IA) with an OpenShift GitOps tool based on Argo continuous deployment (CD), users have complete control of both the application and infrastructure stacks, enabling a rapid response to changes during the holiday season.
How this works in action
Assume an OpenShift cluster, where both GitOps and IBM Cloud Pak® for Watson AIOps are deployed. The Infrastructure Automation Operator is activated and ArgoCD is set up.
Infrastructure Automation exposes REST APIs, which can be called from any external tool to invoke Terraform– and Ansible-based services, providing a seamless connection from an ArgoCD application.
Bring ArgoCD and Infrastructure Automation together to rapidly provision applications and infrastructure, achieving the speed and agility needed for a quality service delivery:
The Infrastructure Automation service is treated entirely as code that can be checked into Git, and it is part of the Git repo used by ArgoCD for deployment. It includes securing the required ServiceNow approvals, provisioning a new Kubernetes cluster and VMs, configuring VM databases via Ansible and updating the CMDB in ServiceNow:
When the ArgoCD application syncs the desired state with the Git repo, the system will deploy all the components, which causes resources to be created. This is the Infrastructure Automation service represented as a Kubernetes resource:
This is the view of those same services in the Infrastructure Automation UI:
Here is the completed deployment of all the required components in the Infrastructure Automation service:
Infrastructure Automation provides an enterprise Terraform capability that integrates with Red Hat Ansible Tower for configuration management. It also includes a comprehensive day 2 management and operations toolset based on the open-source ManageIQ.
Infrastructure Automation drives complex service deployments from GitOps using APIs from Argo CD applications, while preserving the ability to do self-service deployments or integrating with other portals.
It also allows seamless integration with existing IT processes and tools like ServiceNow or CMBDs that aren’t directly integrated with the Kubernetes control plane.
IBM Cloud Pak for Watson AIOps capabilities are designed to support and enhance a broad range of IT practices, including DevOps, SRE and service management. Its outcome focus includes anomaly detection, event correlation and root cause analysis to improve monitoring, service management, cloud charge-backs and automation tasks.