Map your microservices to their consumers, tools, version history, and the teams that support them to achieve a DevOps breakthrough.
Improve Incident Response
Is your support team prepared for microservices? Don’t let them get paged about a microservice they know nothing about.
It’s our job to keep everyone in the loop. DeployHub’s unified Microservice Catalog uncovers the data your support teams need to maintain quick incident response. It gives them a single location to locate the service owners, what was last deployed, and the comparisons and inventory reports needed for them to quickly respond to an issue.
Easily Find and Share Common Services
DeployHub makes it easy for teams to collaborate around microservices.
Give your teams an easy way to discover microservices across your organization. Writing the same service over and over is costly and creates microservice sprawl. DeployHub organizes services so your development teams can share, find, consume, and test services based on ‘solution spaces’ using a Domains Driven Design.
Safely Ship Microservices with DB Updates
Are you ‘flying blind’ when you push microservice updates out to your end users?
Know before you go. DeployHub gives you an early warning system showing the blast radius of your update across all your Kubernetes clusters before you deploy.
Microservice Versioning - Indispensable Clarity
Track and compare changes over time.
To succeed in a cloud native architecture, you need to know what has changed across your Kubernetes clusters from day to day. DeployHub’s built-in version control engine tracks changes between any two versions of your clusters, products or microservices. This is similar to comparing coding updates, but instead we compare all of the details of a container image including where it is running, who uses it, and how it was configured.
Add Automated Configuration Management to Your CD Pipeline
Are you spending time manually tracking changes?
Add DeployHub to your CI/CD Pipeline to automatically track your service changes and their impact. DeployHub is triggered when a new version of your container image has been registered. It grabs the container digest and tag, creates a new version of your service and new versions of all consuming applications. This is your new release candidate captured by your CD Pipeline. When your pipeline deployment step executes, DeployHub is called to initiate the push and captures success/fail results and inventory.
Integrations to Evolve Your DevOps Pipeline
DeployHub includes pre-defined integrations with some of your most common DevOps tools from Jenkins and Helm to Slack and Salesforce. In addition, you can create ‘custom actions’ to extend DeployHub any way you need. Learn More
- Jira, Bugzilla and GitHub Issues
Helm Custom Deployment Actions
Helm can be called to replace the DeployHub default processing engine for performing container deployments. When DeployHub executes the release process, it will call the Helm Chart you have defined as your Custom Action at the Component level. DeployHub includes the version of the Helm chart as part of its overall configuration data. In addition, DeployHub can track Key Value pairs and generate override files for each Environment to which you are deploying.
Jenkins as an Orchestrator
The Jenkins integration uses the a DeployHub Jenkins Groovy Library to perform the following steps :
- Continuous Configuration Management: The process of automatically versioning Components, like microservices, with their consuming Applications.
- Moves: Allows Jenkins to tell DeployHub to push a new update from one state to the next.
- Deploy: Allows Jenkins to tell DeployHub when the deployment needs to be executed.
- Approvals: Tracks an Approval, with audit, between Jenkins and DeployHub Pro (not supported in DeployHub Team).
Configuration Management for Testing
DeployHub integrates with CircleCI to support continuous configuration management and continuous deployments built into your CircleCI pipeline. In particular, DeployHub integrates with CircleCI to enrich the CI/CD pipeline around microservices, tracking which applications need to be retested due to a common microservice update.
Critical to the process is the ability to perform versioning and tracking of microservices across clusters and teams and mapping them to ‘logical’ Applications. DeployHub’s CircleCI Orb includes the ability to perform automated version and dependency management of microservices tracking application and microservice relationships, their versions and their deployment meta data.
Tracking Change Request and Issues
DeployHub integrates with Jira, Bugzilla and GitHub issues to track your change request at 3 levels: Component (microservice), Application and Release (collection of Applications). You define Jira, Bugzilla or GitHub through an object called a ‘data source.’ Once defined, you can pull change request from your issue system and assign them at any level for tracking. When change request are managed in this way, you have a continuous feedback loop showing when the issue was opened and when the customer received the fix.
HipChat as a Notifier
DeployHub allows you to send notifications using Notifiers via HipChat Groups, Topics, or Room features. Notifications are defined to Components and Applications and inform the recipient(s) of the Component or Applications deployment’s success or failure.
GitHub as a Binary Repository
You can configure DeployHub to call out to a Git Repo to pull deployable artifacts (binaries, scripts, etc.) as part of your deployment. The process will check out your deployable artifacts based on commit, branch or tag specified.
Slack as a Notifier
Slack can be integrated with DeployHub using Notifiers. Notifiers can be called to report on success or fail status of deployments.
Tracking and Deploying Salesforce APEX Classes
If you are developing your Applications using SaleForce, this integration will allow you to support SalesForce deployments. By creating this Custom Action you can replace the DeployHub standard deployment processing engine and instead use a process designed specific to Salesforce including the mapping of DeployHub Environments to different SalesForce regions such as testing, pre-production, production, where the class and package files can be deployed.
DeployHub and Playbooks
DeployHub supports the ability to run any Ansible Playbook you create. It does this using pre-defined DeployHub Procedures that you can use to create a DeployHub Action of your choosing. Once created, the Action can call any Ansible Playbook. The most common use is for performing deployments, but you can also use the Action to execute Pre Actions or Post Actions to the deployment.
Using Cloud Foundry to Deploy
DeployHub interacts with Cloud Foundry by using the command line process (cf) to connect to the Cloud Foundry Endpoint. To deploy a new Application (or to make changes to an existing Application) DeployHub uses the “cf push” command to upload the Application to the Cloud Foundry Endpoint.
DeployHub Environments are the same as Cloud Foundry “spaces”. Since DeployHub is an agentless solution, it can deploy to Cloud Foundry by executing the cf command automatically as part of the deployment process. It can extract your DeployHub Application code from any Repository and push the changes up to the Cloud Foundry Endpoint. It can then track which version of the Application is installed in which Cloud Foundry space.
Deploying and managing DataPower with DeployHub.
DeployHub can deploy DataPower the same as it deploys to any Endpoint types, such as docker containers, physical servers, virtual servers, cloud servers, routers, and Gateways. A DataPower multi-channel Gateway provides access, security, and control to a range of mobile devices, web applications, and APIs.
DeployHub can be used to install, configure, and reconfigure DataPower gateways quickly and easily. Due to its agentless architecture, configuration changes to the Data Power gateway can be deployed as standard. DeployHub has built-in Actions that allow zip files to be read, converted to base-64 and embedded into an out-going SOAP message which can then be posted to the Data Power Gateway.
LDAP or Active Directory to manage Logins
DeployHub allows you to use LDAP or Active Directory to manage your User logins. The integration creates an LDAP Data Source to access an LDAP database and use the information stored to gain access to DeployHub. It also populates the Users General tab with Real Name and Email, which it gets from the LDAP database. When you define a User, you associate the LDAP authentication method. At login, DeployHub checks the User’s authentication method to determine if LDAP or Active Directory should be used.