Bridging Ansible Galaxy Roles for Infrastructure Configuration Management with ARA
Ansible is a simple DevOps IT automation engine for cloud provisioning, infrastructure configuration management, application deployment, and other IT needs. Ansible infrastructure configuration management can be driven by continuous deployment.
Using Ansible and DeployHub Together
Ansible is written in the Python programming language, but knowledge of Python is not necessary. As with DeployHub, Ansible is agentless, meaning that installation is not required to run on each target endpoint. DeployHub integrates Ansible Galaxy roles into your application release management logic. Ansible Galaxy roles allow you to develop a deployment workflow that incorporates infrastructure configuration management as part of the software deployment. Check out a demo at https://youtu.be/0MvavR7MStU
Bridging DevOps with Infrastructure Configuration Management and Release Automation
Adding the Ansible Galaxy Roles bridges both release automation and infrastructure Configuration management, thus creating an excellent DevOps solution. When an application is first deployed to servers, many steps must be completed such as standing up a WebSphere Server, starting and stopping server processes, and updating low level configurations. After that process is completed, the War or Jar file can then be installed in the newly configured server. DeployHub now allows you to define a software deployment workflow that can include Ansible Galaxy Roles as ‘procedures’ or ‘components.’ By centralizing both the Server Infrastructure configuration with the application configuration, driven by continuous deployment, all steps are managed in a single complete process, minimizing errors, and coordinating both development and operational activities.
DeployHub has incorporated the Galaxy Roles in two ways. First, reusable components, such as a Websphere install, have been added. This allows anyone to easily re-use the component without doing any extra scripting, coding, or configuration. Secondly, DeployHub allows you to use the Galaxy Roles as functions and procedures. Functions and procedures can be called as part of a standard software deployment workflow. The ability to reuse these types of standard procedures minimizes one-off scripting to deliver more consistent and reproducible software deployments.
DeployHub’s Key Features
- Blueprint your application’s logical view
- Publish and Catalog Microservices
- Version Microservice Configurations
- Release and Track Microservices
- Manage Database Deployments
- Continuous Deployment Blogs
- Understanding a Microservice Pipeline
- Microservice Continuous Integration – Where’s the Build?
- Working with Helm for your Microservices Releases
- Kubernetes Pipeline Challenges
- Managing Embedded Configurations
- Questions and Answers on managing a K8s Pipeline
- Running Safe Blue / Green Deployments
- The DeployHub Jenkins Plug-in
- Setting Up the Jenkins Plug-in
- The DeployHub CircleCI Orb
- Creating a Continuous Feedback Loop
- Release Agents – the Enemy of Continuous Deployments
- DeployHubs Release Architecture
- Why we need Application Packages for CD
- Agentless Deployments with DeployHub’s Engine
- Version Jumps and Tracking
- Blogs on Microservice Configuration Management