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 and Release Engineer

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.


TRagan

Ms. Ragan has had extensive experience in the development and implementation of DevOps for large organizations. She began her consulting career in 1989 on Wall Street specializing in build, testing and release management for the distributed platform. It was during her consulting experiences that Ms. Ragan recognized the lack of standardized development procedures on open systems that were common on the mainframe. In the years leading to the creation of OpenMake Software she worked with development teams in implementing a community driven standardized build and deploy process that enabled frequent builds and releases, automated around version control. Her knowledge and experience contributed to the creation of OpenMake Meister, the first commercial Build Automation solution. Ms. Ragan served on the Eclipse Foundation Board of Directors as an Add-in Provider Representative for 5 years. She has been published on numerous occasions and regularly speaks at conferences including CA World where she presented for 15 consecutive years. She holds a BS Degree in Business Administration, Computer Technology from California State University, Pomona.

0 thoughts on “Release Engineer 7.6 with Ansible Galaxy Roles”

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts

DevOps

Moving from Ant to Meister – No conversion required

Ant to Meister conversion is not required Don’t believe that an Ant to Meister conversion is needed to move to Meister Build services Our competitors would like you to believe that an Ant to Meister Read more...

DevOps

Release Packaging for Release Management

Release Packaging to Improve Software Deployments Release Packaging a requirement for Release Management Release packaging for release management is done in a graphical method with Release Engineer.  Other solutions uses a hard-coded manifest file that Read more...

DevOps

.Net Solutions with complex dependencies

.Net Solutions with Complexity .Net Solution builds can get complicated with multiple solution files We often get customers who have multiple .Net Solutions for creating a single application.   While Microsoft may advise against the practice, Read more...