Audience is enterprise senior management for data center operations, intended to highlight different elements of the Nutanix product suite. Ghost-written for Nutanix, through Dipti Parmar who runs an agency for technical content in India.
URL: https://www.nutanix.com/theforecastbynutanix/technology/unify-hybrid-multicloud-environment-into-single-operational-model
URL: https://www.nutanix.com/theforecastbynutanix/technology/unify-hybrid-multicloud-environment-into-single-operational-model
HED: Get That Single View of Your Operations
DEK: How to unify a Hybrid and Multi-Cloud Environment into a Single Operational Model
Complex environments create complex problems, but there are well-designed solutions for those willing to journey into them.
Today, over 81% of organizations are working with two or more public cloud service providers to support their activities. This multi-operational model comes with overhead in costs and time and is no longer strictly necessary. It’s time to move into the model dubbed the Single Operational Model for hybrid and multi-cloud environments, the ‘single pane of glass’.
Enterprises should invest time and money now into finding the right middleware solution for both hybrid- and multi-cloud.
— David Linthicum, GigaOm
Growth in cloud-based IT has spawned mature Cloud Management Platforms (CMPs) that wrestle the on-premise, hybrid and multi-cloud environments into submission. CMPs expedite the ability to connect multiple environments to provide that single operational view. They can provide self-service provisioning, deep analytics, layered and rules-based governance and compliance, faster incident recovery times and more to simplify operations across all business units within an enterprise.
The question is not if an organization should make use of a good CMP, but how to get there? Many already have the resources needed to take advantage of a CMP but are looking for a definitive map to that destination. Listed here are several components and considerations to take to reach that single operational model.
The Enterprise Cloud Strategy: If there isn’t one, get a defined, documented strategy. If there is, it’s time to review, update and put it to use. The Cloud Strategyprovides the path, the size and the scope, pointing everyone in the same direction. Using references from recognized sources minimizes disagreement on meaning and purpose, expediting the discussion.
Here is where the inventory of applications, data, services and residencies are accumulated. The information is collected and refined, allowing the organization to move forward quickly and with confidence in their decisions. Companies with no time for guesswork know the Cloud Strategy is a requirement.
Costs: This goes beyond contract costs for the current Cloud configurations and is more reflection of true TCO. The need is to understand the management andoperational costs, the actual man-hours required to maintain each of the different environments. This is where a primary business case for a ‘single pane of glass’ view of all operating environments is found.
This is not a guarantee that all will be strictly cost savings. There are outlays and there will be shifting of costs. The introduction of a single operational model will likely change processes and procedures in multiple areas which will require resources. It may necessitate reassigning existing personnel or acquiring new skills to take full advantage of the product. It may also show that more than one product is required to meet all needs.
Financial considerations must be understood to allow the most prudent decisions to be made. However, they should not be used so rigidly as to limit the ability for the organization to reap the benefits of a single operational model.
Requirements: The true TCO is now visible and speaks to the need for a single operational model. With the ’what’ and the ‘why’ in hand, identify the requirements specific to the enterprise. Prioritizing and documenting the needs, wants and future enhancements allows the conversations and decision to proceed. This can include regulatory, geographic, goal-supporting and financial needs. Every organization is unique, and their CMP should fit their business.
Use case topics for a Cloud Management Platform (CMP) to consider:
Any organization’s list will also include other items specific to their configuration. The requirements facilitate the short list of potential providers but should be as complete as possible. Ranking within each category helps to identify the ‘must have’ items should those determinations be required.
All providers have support, but some are more proficient than others. Be specific when sharing expectations and how the organization generally works. If someone on-site is required throughout the implementation, make it clear from the beginning. These should be included in the requirements rather than after a provider has been selected.
Providers: It will be tempting to purchase and install the monitoring product from the largest Cloud provider with an existing relationship or the one that seems to have lots of features at a reasonable price. Here is a call to exercise caution. Only by matching the needs of the enterprise to the proposed product will the best fit for the organization be identified.
Pitfalls can include purchasing services that may not be fully utilized, accepting services that appear to cover most of the requirements but may leave some unacceptable gaps, and products that can’t be integrated — especially common with some on-premise, legacy applications. This last case could present a need for a second product or provider. There may not be a perfect answer to every scenario but knowing the exceptions up front is critical to success.
There are a number of CMPs out there able to integrate on-premise, hybrid and multi-cloud environments, each with their own services. Finding the one that best suits a given enterprise will depend on the requirements. Being mindful the goal to simplify the operational model will require looking at several providers very closely.
Having very direct conversations with the short-list of final provider candidates specifically about implementation and product support prior to final selection is advised. Often, this helps make the final decision more clearly visible.
Implementation: Once a choice has been made, there is product implementation, the unavoidable disruption that must be managed. A phased approach is common practice. The internal team will partner closely with the provider’s team to define timelines and resources required for the migration.
Some environments will migrate in quickly and rather seamlessly. Others may take a bit more work or custom integrations. It is important to in the phased approach to allow learning, adjusting and normalizing to happen along the way.
Normalization: The post-implementation/normalization period will contain growth and present adjustments throughout the organization. Learning the big features and small nuances takes time.
Rules are often initially over-tooled. They require review and adjustment, fine-tuning them until they manage enough without limiting too much.
Some CMPs include Ai and Machine Learning capabilities in their products. As these are integrated into the organization’s analytics new patterns and opportunities will emerge.
Go. This selection and migration will take time so it is best to start. Hybrid and multi-cloud are no longer synonymous with complexity. It’s time for organizations to claim the simplicity promised by the cloud with a single pane of glass operational model.
DEK: How to unify a Hybrid and Multi-Cloud Environment into a Single Operational Model
Complex environments create complex problems, but there are well-designed solutions for those willing to journey into them.
Today, over 81% of organizations are working with two or more public cloud service providers to support their activities. This multi-operational model comes with overhead in costs and time and is no longer strictly necessary. It’s time to move into the model dubbed the Single Operational Model for hybrid and multi-cloud environments, the ‘single pane of glass’.
Enterprises should invest time and money now into finding the right middleware solution for both hybrid- and multi-cloud.
— David Linthicum, GigaOm
Growth in cloud-based IT has spawned mature Cloud Management Platforms (CMPs) that wrestle the on-premise, hybrid and multi-cloud environments into submission. CMPs expedite the ability to connect multiple environments to provide that single operational view. They can provide self-service provisioning, deep analytics, layered and rules-based governance and compliance, faster incident recovery times and more to simplify operations across all business units within an enterprise.
The question is not if an organization should make use of a good CMP, but how to get there? Many already have the resources needed to take advantage of a CMP but are looking for a definitive map to that destination. Listed here are several components and considerations to take to reach that single operational model.
The Enterprise Cloud Strategy: If there isn’t one, get a defined, documented strategy. If there is, it’s time to review, update and put it to use. The Cloud Strategyprovides the path, the size and the scope, pointing everyone in the same direction. Using references from recognized sources minimizes disagreement on meaning and purpose, expediting the discussion.
Here is where the inventory of applications, data, services and residencies are accumulated. The information is collected and refined, allowing the organization to move forward quickly and with confidence in their decisions. Companies with no time for guesswork know the Cloud Strategy is a requirement.
Costs: This goes beyond contract costs for the current Cloud configurations and is more reflection of true TCO. The need is to understand the management andoperational costs, the actual man-hours required to maintain each of the different environments. This is where a primary business case for a ‘single pane of glass’ view of all operating environments is found.
This is not a guarantee that all will be strictly cost savings. There are outlays and there will be shifting of costs. The introduction of a single operational model will likely change processes and procedures in multiple areas which will require resources. It may necessitate reassigning existing personnel or acquiring new skills to take full advantage of the product. It may also show that more than one product is required to meet all needs.
Financial considerations must be understood to allow the most prudent decisions to be made. However, they should not be used so rigidly as to limit the ability for the organization to reap the benefits of a single operational model.
Requirements: The true TCO is now visible and speaks to the need for a single operational model. With the ’what’ and the ‘why’ in hand, identify the requirements specific to the enterprise. Prioritizing and documenting the needs, wants and future enhancements allows the conversations and decision to proceed. This can include regulatory, geographic, goal-supporting and financial needs. Every organization is unique, and their CMP should fit their business.
Use case topics for a Cloud Management Platform (CMP) to consider:
- Financial Management and Resource Optimization
- Security, Compliance and Governance
- Provisioning and Lifecycle Management
- Operations and Incident Reporting
- Analytics and Machine Learning
- Third-Party Integration of Apps and Services
Any organization’s list will also include other items specific to their configuration. The requirements facilitate the short list of potential providers but should be as complete as possible. Ranking within each category helps to identify the ‘must have’ items should those determinations be required.
All providers have support, but some are more proficient than others. Be specific when sharing expectations and how the organization generally works. If someone on-site is required throughout the implementation, make it clear from the beginning. These should be included in the requirements rather than after a provider has been selected.
Providers: It will be tempting to purchase and install the monitoring product from the largest Cloud provider with an existing relationship or the one that seems to have lots of features at a reasonable price. Here is a call to exercise caution. Only by matching the needs of the enterprise to the proposed product will the best fit for the organization be identified.
Pitfalls can include purchasing services that may not be fully utilized, accepting services that appear to cover most of the requirements but may leave some unacceptable gaps, and products that can’t be integrated — especially common with some on-premise, legacy applications. This last case could present a need for a second product or provider. There may not be a perfect answer to every scenario but knowing the exceptions up front is critical to success.
There are a number of CMPs out there able to integrate on-premise, hybrid and multi-cloud environments, each with their own services. Finding the one that best suits a given enterprise will depend on the requirements. Being mindful the goal to simplify the operational model will require looking at several providers very closely.
Having very direct conversations with the short-list of final provider candidates specifically about implementation and product support prior to final selection is advised. Often, this helps make the final decision more clearly visible.
Implementation: Once a choice has been made, there is product implementation, the unavoidable disruption that must be managed. A phased approach is common practice. The internal team will partner closely with the provider’s team to define timelines and resources required for the migration.
Some environments will migrate in quickly and rather seamlessly. Others may take a bit more work or custom integrations. It is important to in the phased approach to allow learning, adjusting and normalizing to happen along the way.
Normalization: The post-implementation/normalization period will contain growth and present adjustments throughout the organization. Learning the big features and small nuances takes time.
Rules are often initially over-tooled. They require review and adjustment, fine-tuning them until they manage enough without limiting too much.
Some CMPs include Ai and Machine Learning capabilities in their products. As these are integrated into the organization’s analytics new patterns and opportunities will emerge.
Go. This selection and migration will take time so it is best to start. Hybrid and multi-cloud are no longer synonymous with complexity. It’s time for organizations to claim the simplicity promised by the cloud with a single pane of glass operational model.
