Addressing the disconnect across Development and Operations teams in any given IT department today, means we recognize that these two teams fundamentally have different perspectives on change and the speed in which it is introduced.
Development teams work hand-in-hand with the line of business to rapidly deliver on change requests raised, that way they can meet and adapt to the ever-changing business landscape. Operations teams on the other hand, work on ensuring tight controls on change requests to minimize poor performance, outages and security vulnerabilities. As you can see, diametrically opposed objectives.
Now, while both teams are right and true in their charter, this ebb-and-flow in change management across the teams has unfortunately resulted in “Relations between Development and Operations generally viewed as poor, with some even characterized as toxic”*. This lack of operational efficiencies is not business sustainable.
This is the business challenge that HP’s Continuous Delivery Automation (CDA) was built to address. Particularly, helping businesses address the DevOps divide for better real time collaboration, through the use of HP innovation in Flexible Application Modeling. This is accomplished by providing a model-driven approach to DevOps collaboration. This approach is used for automation of application development and monitoring, to meet the concerns of Development and Operations teams.
Innovation through HP Flexible Application Modeling
Bridging the gap between development and operations environments calls for a defined pipeline of release stages and application candidates. This means moving regularly from planning to development and from release to operations. With transparency between Development and Operations teams, and clarity towards both scope and frequency these groups should increase communication and deliver results faster.
HP Continuous Delivery Automation addresses this pipeline through a dynamic set of model-driven data and actions. CDA leverages HP’s flexible application modeling technology to represent required artifacts and relationships to define how composite applications are delivered to a dynamic set of target environments. Artifacts are centrally stored (and versioned) into a definitive software library, that is then used to orchestrate key operations modeled—from platform provisioning to application deployment. The goal is to unify development and operations functions while eliminating critical disconnects that are found in traditional processes.
Understanding HP Flexible Application Modeling
When you create models with components of infrastructure/platform/application, HP’s flexible application modeling provides a paradigm shift toward modular and reusable application deployment. This is a marked difference from the typical script/workflow approach which requires a new independent script/workflow for changes made to a given component. This is notwithstanding the cascading set of changes that extends the different set of application scripts that uses this same revised component. This traditional approach presents exponential complexity. HP’s flexible application modeling technology does not.
By using a layer-based model, where each layer is independently designed, HP flexible application modeling allows the reuse of an existing configuration while constructing the application deployment through a building block approach of modular construction. At the same time, HP flexible application modeling facilitates application deployment portability, for the deployment of this same application model on different platform topologies.
This form of additive complexity can be illustrated in the following example :
An IT department has a collection of 500 applications today. Assume that these applications uses four different operating systems, four different databases, four different middleware and four different application servers. With the use of HP’s flexible application modeling technology, this becomes 4+4+4+4 = 16 data models to be configured and mapped to the 500 applications in store. In a traditional approach, this would mean managing 44 = 256 scripts/workflows to each of the application - clearly a Herculean effort when it comes to change management.
HP Flexible Application Modeling simplifies the design and modeling of an application and its infrastructure through a building-block approach, with components in infrastructure/platform/application. To create an application design, simply connect the appropriate building blocks together. Modify the blocks along the application lifecycle as needed; without having to modify the application code as it moves from test to stage and to production. This expedites application design and enables users to leverage best practices across multiple models.
HP Flexible Application Modeling brings value to DevOps
This approach facilitates the dynamic reuse of artifacts because it provides flexibility and portability for applications across platforms, all to meet day-to-day changing business delivery requirements.
Improved time-to-delivery (TTD) of application ecosystems and a reduction in costs, errors, rework and risks through model-drive automation
Improved collaboration with DevOps by centralizing information on setup, operations and monitoring across a release pipeline
Reduced vendor lock-in by separating the model that defined the delivery artifacts from the tools that operate on the model necessary to realize the automation.
The solution was developed with real customer needs and demands in mind, and it continues to bridge the gap between development and operations. Read the attached business whitepaper which discusses how the disconnects between development and operations functions is impacting your organization today. Learn how you can adopt a set of software delivery practices that improves collaboration between application development, testing, infrastructure and operations teams by going to www.hp.com/go/cda .