The Top Private Cloud Project Mistakes You Need to Avoid
When it comes to your private cloud project it's easy to make mistakes that in hindsight look obvious, but can be hard to predict if you lack experience with cloud infrastructures.
For many organizations, moving IT infrastructure and applications into private clouds is entering into uncharted territory. When it comes to your private cloud project it's easy to make mistakes that in hindsight look obvious, but can be hard to predict if you lack experience with cloud infrastructures.
Recommended Reading: Private Cloud Project: Top Considerations You Need to Know.
First, What is a Private Cloud?
A private cloud is basically a cloud computing platform that is implemented within the corporate firewall, under the control of the IT department. It is designed to offer the same features and benefits of public cloud systems -- but removes a number of security concerns inherent to the cloud computing model.
Companies initiate private cloud projects to enable their IT infrastructure to become more capable of quickly adapting to continually evolving business needs and requirements.
Top 3 Private Cloud Project Mistakes
1. Don't believe that every cloud that claims to be private actually is
Just because "private" is the term you're using does't mean you can slack off when it comes to setting up access controls and safeguarding the privacy of corporate data.
"Surprisingly, some 'private' clouds really aren't so private. For example, the private cloud might mingle data from multiple customers in a single instance, though the cloud itself is not publicly accessible," said Mike Carpenter, Vice President of Service Assurance at TOA Technologies, a provider of mobile workforce management solutions.
Additionally, the best cloud services plan for and provide capabilities that not only ensure every user has a truly private cloud, but also make sure that the customer controls his or her own data. In a truly private cloud, customers are in control of creating their user accounts. The customer controls the data, and the customer controls access to the only application that can open it.
2. Don't think that de-provisioning VMs is easy
Just because you can de-provision a VM and free it up for something else in theory, doesn’t mean you’ll be able to do so in practice.
"How can you put a bullet in a virtual machine without knowing who owns it?" asked Paul Martin, Systems Engineering Lead, EMEA, for Embotics, a private cloud management provider. "Most IT administrators don’t know who owns it and will end up erring on the side of caution, which causes other problems."
Without the proper tools in place to identify zombies and VMs that have had no log-in, or have not been powered on for a certain number of days -- and to identify the owners of those orphaned VMs, IT pros won’t risk getting rid of them. It’s too big of a political risk.
3. Using a private cloud model to roll-out public cloud services
Concur Technologies, a provider of travel and expense reporting solutions, had virtualized nearly 80 percent of its internal IT infrastructure and had moved many internal applications into private clouds. However, their customer-facing travel and expense reporting SaaS solution ran up against a major problem, one that is easy to overlook if your cloud focus is directed inward: the fact that heavy-duty enterprise apps don’t always perform well over the public Internet.
Moreover, in a transaction-based environment, end users have little patience for slow performance. If transaction times lag, customers move on to someone else.
To tackle these problem, Concur brought in ExtraHop, a provider of application performance monitoring and management solutions.