Hybrid Development and Test USE CASE

Transcription

1 Hybrid Development and Test USE CASE

2 CliQr Use Case: Hybrid Development and Test Page 2 Hybrid Development and Test Unlike the production phase, with its typically steady workload, development and test cycles tend to be bursty by nature. Because of this, it is typical in large organizations to match the burstiness of those dev/test workloads with the elasticity that public cloud provides while running a predictable production version of the application on a private cloud. But how do you ensure that applications are deployed the same way across diverse cloud environments so that the dev/test work is a valid replica of production? Any Application Dev/Test Production PUBLIC cloud PRIVATE cloud Using CliQr CloudCenter, companies can choose low-cost and elastic public cloud environments for various stages of development and then deploy for production in their private cloud by following a fully automated, policy-based workflow. Development and test workloads must be able to mimic the production environment, but replicating that environment can be prohibitively expensive. CliQr minimizes configuration and release management costs for dev/test environments while ensuring that provisioned infrastructure for dev/test is an exact replica of production, thus improving quality and accelerating the application lifecycle. And there s enough governance inside CloudCenter to enforce policies that dictate what workloads run where based on their stage in the software development lifecycle.

3 CliQr Use Case: Hybrid Development and Test Page 3 Foundations for Hybrid Development and Test Success CloudCenter provides the tools for an IT department to import user groups from an existing LDAP server and govern cloud usage with sophisticated role-based access controls. With CloudCenter s benchmarking feature, the best execution venues for development, test, and production workloads can be discovered and optimized for price, performance, or a combination of the two. Cloud-agnostic Application Profiles, which describe the infrastructure needs of each application, can be versioned and made upgradeable to support the long life of an application. With these capabilities as a foundation, IT can manage a hybrid environment where development and test run on one cloud and production on another. Managing Hybrid Development and Test CliQr enables IT departments to centrally define dev/test environments that span private cloud, public cloud, or both, simplifying application lifecycle management across diverse, hybrid cloud environments. IT can enforce environment use policies by optionally mandating workflow approval before an application is promoted from one environment to another, so the dev/test environment stays on public clouds while the production environment goes on the internal private cloud. Adding a New Deployment Environment

4 CliQr Use Case: Hybrid Development and Test Page 4 Teams can now focus on building and testing scalable applications, without the need to depend on IT resources to provision infrastructure components and maintain annoyingly incompatible images on various clouds. With CliQr, IT can give developers the access they need to deploy applications, spin up VMs in any cloud, and subsequently promote the application to the production environment without any cloud-specific scripting. This portability along with governance around user roles provides IT with flexibility and control over the entire lifecycle. But, how can CloudCenter achieve the kind of portability required to run different phases of a software lifecycle on different clouds? The Key to Portability CliQr Application Profiles CliQr achieves this level of flexibility and ease of use with Application Profiles. CliQr Application Profiles describe the configuration and release requirements for an application across different phases of the deployment lifecycle in a cloud-agnostic way. Engineering managers use CliQr Application Profiles to describe the infrastructure needs of an application in one place, and they can reuse them to deploy the application to different environments throughout its lifecycle. Administrators can set up dev/test on public clouds to leverage their low-cost elasticity, and then use the same Application Profile to deploy to production on a private cloud. CliQr s Application Profiles start with one of several templates, which organizations can use to create genre-specific Application Profiles. The core Application Profile templates include: N-Tier Supports applications that are made up of multiple tiers (database, back-end cache, message queue, application cluster, load balancer, front-end cache, and other applications), where each tier may be provisioned on a different node or node cluster. Examples include Web applications built in Java, PHP, Ruby on Rails, as well as enterprise applications including Oracle EBS and SAP ECC. Cluster Computing Supports applications that require a cluster with shared storage to complete execution. The application process is launched on a single node with a list of all cluster nodes. Examples include Message-Passing Interface (MPI)-based High-Performance Computing (HPC) applications. Batch Processing Supports single-node applications in which multiple independent application jobs are placed on a queue for servicing by an elastic cluster. Examples include gene sequencing, batch document processing, regressions, simulations, or video transcoding applications. Parallel Computing Supports single-node applications in which multiple independent

5 CliQr Use Case: Hybrid Development and Test application runs are launched in parallel on multiple nodes. Examples include gene sequencing and various types of complex simulations. Cloud-enabled Thick Client Supports desktop applications that have a user interface. The desktop application launches in a cloud so that browsers can access the application s user interface from any device, such as a tablet or smartphone. Local devices can then upload or download application data to the application in the cloud. Examples include design and graphics rendering (e.g., Blender), modeling user interfaces, or layout editors for semiconductors. Multi-Step Workflow It s possible to combine any of the above profiles into any multi-step workflow to describe simple or complex applications and application workflows. From there, it s straightforward to extend any of the Application Profiles by plugging in custom scripts, calling third-party orchestrators, and using existing images or various services. The CliQr CloudSmart Orchestrator (CSO) runs on each cloud and encapsulates its best practices. At deployment time, the Application Profile is interpreted by the CSO and provisioned based on the strengths of the specific target cloud. CSOs are available for most on-premise environments as well as public and private clouds, which makes deploying dev/test on one cloud while targeting production for another, consistent and simple. Find out how CliQr can streamline and simplify your hybrid dev/test needs at CliQr Technologies Scott Blvd, Suite 220, Santa Clara, CA [email protected] CliQr Technologies. All rights reserved. CliQr, the CliQr logo, and CliQr CloudCenter are trademarks of CliQr Technologies in the United States. All other trademarks and company names are the property of their respective owners. UC-HDT-1214