HashiCorp and Quali work together to help organizations rapidly scale, maintain, and secure their cloud initiatives, and manage business-critical applications.
Combining the power of HashiCorp’s Infrastructure-as-Code (IaC) product, Terraform, with Quali Torque and CloudShell helps teams bring the application to the center of the operation to develop, test, and deploy with a self-service focus on any cloud, on-prem data center or physical bare metal server.
While HashiCorp is cloud agnostic, Quali is infrastructure agnostic thus creating a powerful partnership to give organizations the keys to manage or migrate any application and any layer.
Quali helps bring business and mission critical applications to the forefront of an organization’s migration roadmap. This partnership is not a one-size-fits-all solution as many organizations require the need for VPC and hybrid data centers. By using both HashiCorp and Quali, organizations can efficiently execute cloud deploys or DevOps strategies.
Terraform CLI: Torque integrates with Terraform CLI as a trusted Infrastructure as Code (IaC) tool and allows users to use .tf modules to execute dev/test environments inside the Torque UI.
Learn more at HashiCorp.com
Many organizations trust Terraform to deploy and provision infrastructure resources to a single cloud and manage the infrastructure state. When organizations combine Quali Torque with Terraform, the application is brought to the center of the DevOps lifecycle.
Organizations at any stage of their cloud migration journey are now able to prioritize any and all applications to modernize or migrate drastically improve time to market and user experience.
HashiCorp’s “Immutable Infrastructure” empowers the cloud, but in situations where organizations look to migrate applications to the cloud, host applications on-prem or through service providers, it can put decision makers in a challenging predicament. This is where Quali thrives.
All organization have existing investments and tooling roadmaps with various automation and orchestration products in their environments.
One of these challenges starts with investments made on do-it-yourself tools to piece the ecosystem puzzle together and create a clean workspace for developers to modernize or migrate applications. Quali embraces the notion that open communities empower the DevOps ecosystem.
Quali does not look to rip and replace existing investments as we all know it is a difficult to have conversations asking teams to completely change their automation and orchestration posture.
Quali’s Torque and CloudShell fit between development teams and Infrastructure Ops in a flexible manner to optimize existing investments and offer efficiency removing the unknowns of Shadow IT.
Our open and flexible frameworks are driven by Quali’s blueprints with a rich repository of REST API allowing for integration and automation across the full lifecycle of an application. This openness allows DevOps teams to create and replicate dev/test sandboxes that spin up and teardown any environment on-demand based on their existing ecosystem of tools.
As it relates to Terraform CLI, users can create blueprints in Quali that include Terraform files. a simple example of a Quali application blueprint (including a .tf file) that enables the operations team to manage all the surrounding integration points and Vault secrets then expose Terraform templates on the application itself.
When a sandbox is spinning up in the blueprint inside of Torque’s UI, Quali creates a VPC, application load balancer, application instances, and target groups.
The Quali server opens different ports, creating the routing table, internet gateway, hosting zone, etc. via your required cloud/on-prem resources according to your organization’s value stream best-practices.
We take on the responsibility and provide this service, which is unique to Torque.
This is where Terraform steps in. Torque supports all module sources that are available in Terraform.
Review the official documentation here.
We recommend DevOps teams keep the Terraform module in GitHub or another source control repository and reference that in your source definition.
Quali Torque and CloudShell use blueprint YAMLs to define a set of applications and their dependencies, providing a way to define the required infrastructure and application parameters.
Users are able to use service YAML files with reference to .tf modules applying them directly inside of the Torque UI with a simple toggle inside of the blueprint.
Quali’s blueprints provide guardrails and governance across all development teams. At scale, this is where Terraform and Quali can provide a seamless experience for developers.
Quali defines applications in development at the logical level of the service provisioning process all the way down to the policy automation workflow that must occur in the provisioning of an environment.
This enables Immutable application stacks not just the infrastructure.
As teams grow and applications teams require on-demand access to dev/test environments, the Quali and Terraform relationship meets the demand head on.
While Terraform meets some of these needs to code and automate stages of the infrastructure, the effort to manage workflows in complex environments becomes cumbersome to manage, especially in situations where technical debts lock dev teams into legacy tools and hybrid infrastructure. Quali Torque’s blueprints alleviate these complexities by creating a self-service catalog of repeatable environments.
Combining the power of Quali’s immutable applications stack with Terraform turns 200 lines of code commands into 30 resulting in a clean application release from commit to pipeline to health check to production.
Store Application Reuse in Blueprints
Modelling applications through blueprints is the only way to turn applications into re-usable elements throughout the development and release pipeline. Quali integrations with popular repositories, CI/CD, Artifact repositories, automation, and other ecosystem tools to keep the latest versions and images stored and accessible.
Multi-cloud, Multi-environment Focus
Quali helps teams abstract applications to move workloads between environments and cloud providers. If applications and infrastructure are abstracted and defined separately, developers must start from scratch once the application moves into the new environment.
The Path to Breaking Silos
The vision of Dev, Sec, and Ops all dealing with the same language (code) is wonderful. But bringing everyone to the same code pool is not always easy. Applications and infrastructure are not the same thing, even though we can code both. Mixing them makes them unnecessarily hard to build and troubleshoot. It forces us to deal with fuzzy boundaries when it comes to responsibility for this code. Basing automation on a model that organizes the world in a way the different stakeholders can understand it can help overcome this barrier.
Connect Infrastructure to Business Needs
Quali does not understate the importance of infrastructure as the infrastructure is the foundation of everything. Infrastructure-as-Code is extremely powerful, but in order to make application development and release faster, Quali combines the needs of the business by bringing automation, visualization and actionable actions to eliminate Shadow IT.