Puppet Integration Adapter

Kovair Puppet Adapter integrates the Puppet tool with Omnibus and other best of breed ALM tools to fully manage the automation of the deployment process across the delivery pipeline.

Kovair provides an ESB platform called the Kovair Omnibus. Using Omnibus platform and Kovair Puppet adapter, you can hook the Puppet tool to Kovair Omnibus, which will expose all related entity deployment details directly from the target server where the Puppet tool deploys the built codes to the other tool environments. This helps different tool users, connected to Kovair Omnibus, in the creation of cross tool reports and metrics for monitoring build, jobs, test runs, and deployment, altogether.

Kovair Omnibus uses point and click configuration to create seamless deployment using Jenkins Job and Puppet cookbook. Kovair adapter for Puppet provides easy execution of knife in command line to interact with Puppet Server.

Features & Benefits

  • Puppet integration provides deployment solution for Kovair DevOps solution
  • Synchronizes Puppet tool with Kovair application.
  • Point and Click configuration method guided by Kovair interactive UI.
  • Easy monitoring of deployment related entities directly exposed from the target server.
  • Customized event-based action service flow.
  • End-to-end traceability from a consolidated view.
  • Creation of Reports, Metrics, Continuous Monitoring, Consolidated View, etc.

Key Highlights of Kovair Puppet Adapter

Kovair Puppet Adapter, when integrated with Omnibus platform offers the following benefits:

Direct Fetching of Deployment Related Artifacts

The adapter enables the tool to expose deployment related artifacts directly from the target server into Kovair application.

Point and Click Configuration Method

Kovair Puppet adapter can integrate Puppet with Omnibus platform thus enabling integration with other ALM tools. Kovair’s integration uses a uniform Point and Click Configuration method guided by Kovair interactive UI to facilitate capturing of vital statistical data from puppet for reporting. 

End-to-End Traceability and Streamlined Reports

Users can use the data fetched via Kovair Puppet Adapter for end-to-end traceability, consolidated view, custom reports creation, and metrics.

Entities Exposed Entity Fields Entity Mapping Type Events Collected Actions Supported
  • Puppet Master
  • Groups
  • Nodes
  • Report
  • Job
  • Entity Objects
  • Single Line Text
  • One to Many
  • Many to One (Puppet Master)
  • Many to Many (Groups)\
  • Many to One (Puppet Master)
  • Supports both ‘Add’ and ‘Edit’
  • Supports both ‘Add’ and ‘Edit’

Puppet Adapter Integration Use Case

To understand the integration scenario with Puppet, let us take the example of an organization where teams use various ALM tools:

Puppet Adapter Integration Use Case
  • Requirement engineers: using Kovair for managing releases, sprints, user stories, etc. in the Agile project.
  • Developers: using Eclipse IDE for coding, SonarQube for performing static code analysis, GitHub as source code repository.
  • Build managers: using Jenkins for build purposes.
  • QA team: using Selenium for automated testing.
  • Step 1: Once the requirements are added as backlogs, the Requirement Engineer will prioritize the backlogs, associate it to the sprint, and approve it.
  • Step 2: On sprint approval, the Developers will get a notification of the backlogs that have been to the sprint.
  • Step 3: The requirements that are residing in the Kovair application are exposed to the developers using Eclipse IDE. This is possible with the help of Kovair Omnibus plugin specific to Eclipse IDE.
  • Step 4: The Developers check out the source code project from GitHub and then make necessary modifications on the code file in order to implement the backlog and then save it.
  • Step 5: Next, the Developer performs static code analysis on the code project using SonarQube.

  • Step 6: Based on the analytical result, the code project is checked into GitHub. While checking in, the ID of the backlog is provided in the Comments, which is then automatically configured in the backend of Kovair Application, through a business rule. This helps to establish a relationship between the backlog and the GitHub Commit.
  • Step 7: Once the code file is checked in; Kovair one-stop DevOps solution comes to play.
  • Step 8: The pipeline in Jenkins is automatically triggered. It performs three jobs—“Build” using Jenkins, “Deployment” using Puppet, and “Automated Test” executions using Selenium.
  • Step 9: Finally, in Kovair, we get to view the traceability of the artifacts and the relationships that are fetched from various other tools. 
  • Step 10: Apart from the traceability report, we can also fetch specific data from each of the tools in real time and create several metrics and dashboards. These metrics and dashboards are essential for monitoring purposes by higher executives. For example, the deployment manager can get a full-fledged traceability of all the artifacts in a consolidated manner along with its relationships fetched from Puppet to Kovair.

Note: The adapter as developed and offered by Kovair follows the subject tool’s standard specifications. Any deviations from the Tool’s typical use pattern may not have been anticipated in our off-the-shelf product. For any customization or special configuration needs, please contact Kovair Sales – sales@kovair.com