Ansible Galaxy Roles integrated into Release Management
Bridging Ansible Galaxy Roles for Infrastructure Configuration Management with Release Management
OpenMake Release Engineer 7.6 inclues the ability to integrate Ansible Galaxy roles into your application release management logic. This feature allows you to develop a deployment workflow that incorporates infrastructure configuration management as part of the software deployment. Check out a sneak peak at https://youtu.be/0MvavR7MStU
Adding the Ansible Galaxy roles bridges both release management and Infrastructure Configuration management. 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. Release Engineer 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, all steps are managed in a single complete process, minimizing errors and coordinating both development and operational activities.
Ansible Galaxy Roles
Release Engineer 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, Release Engineer 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 and delivers more consistent and reproducible software deployments.