Hybird Cloud Six Lacks

1 - Heterogeneity and lack of standard

The main obstacle to the success of hybrid cloud is the lack of standardization. "A hybrid cloud impose structural choices for the internal IF and limiting vis-à-vis public clouds supported," says Yves Pellemans, technical director of APX. To make seamless hybrid cloud, it must adopt the same technology throughout, even among providers of public clouds.

"Theoretically, OpenStack is expected to make the hybrid heterogeneous environment but it is not yet a promise," said Marc Gourlan in charge of business development of cloud computing at BU CSC.

One solution is to ignore the layers of virtualization and features provisioning to settle for hybridization at the application level. "We then deploy the same application, both public and private side, maintaining the same levels of versions and patches," says Yves Pellemans.

2 - Heavy technological and application constraints

Enemy of the hybrid cloud, latency slows trade between remote application components. "In France, it is not a problem if you put the price by using the fiber and optimizing flows," Yves Pellemans advance. But this has a cost and technical lock becomes economical.

Another way to circumvent the obstacle: Rethinking the application architecture or accept limitations. "Applications should not need access to a database shared by the private cloud and public cloud data" provides an example Julien Contal.

You can also simply move virtual machines (VMs) between private cloud and public cloud. "But it is never transparent, particularly in terms of IP addressing. In addition, these VM running applications whose data exchange will risk always ask latency issues, "retorted Julien Contal.

Another technological constraint: identity management and authorization also becomes complex hybrid environment.

3 - A weight often existing heavy

"To make the hybrid cloud, you must first convert the information private cloud system," asserts Yves Pellemans. Swathes of SI then be incompatible with the notion of private cloud. Especially since it must be able to reproduce in the public cloud. However, there is little clouds deals mainframe world or proprietary Unix. "In addition, there are licensing issues, some publishers do not allow deployment in the cloud," says Julien Contal.

This weight is existing as virtually prohibits changing applications to a hybrid cloud PaaS category."It will be limited to new applications. They are based on a specific development or a software package, we will ensure they are PaaS "compatible explains Julien Contal.

In this context, the software will decline their offers in several forms, SaaS and PaaS package in addition to the version on-premise . What is even often the case.

4 - Cost control: the hybrid cloud is not a panacea

The public cloud is supposed to offer better visibility of costs, which vary according to the needs.It allows you to choose in each case, the private or public mode. But it can also be a source of slippage. "When data between private and public clouds are synchronized, for example in the context of a PRA, services must run continuously on the public cloud and data volumes can be significant, which creates a risk of explosion costs, "says Julien Contal.

Especially since many public cloud offerings are priced bandwidth. This problem then joined the network architecture and application, which should restrict trade between distant clouds.

5 - The sometimes prohibitive regulatory and security constraints

Regulatory and security constraints often prevent data out of the private cloud. Never mind: the hybrid cloud is rightly to choose the best option based on these constraints. Except that the use cases most often cited by firms is the PRA, which by definition target the most critical applications."Now, a PRA in hybrid mode imposes a continuous output of critical data to duplicate in the public cloud, "says Julien Contal.

6 - A slow change in attitudes and organization

The company itself, DSI head, is perhaps the first brake hybrid cloud. "This is a big change for the functional and technical teams, which should agree on what can be provisioned in the public cloud services rather than resources thinking." Says Yves Pellemans.

You should also add a social dimension. Door wide open to the public cloud, hybrid cloud is synonymous effect of outsourcing part of the ISD.

Hybrid Cloud inconsistent with the culture of the department?

According to a Gartner study , by the end of 2017, nearly half of the companies have implemented hybrid cloud deployments . Analysts believe that the hybrid cloud (where some resources are managed internally and by other external providers) is the point where the private cloud was there three years.

However, if most companies today use one form or another private cloud computing, Gartner notes that a number of obstacles impede more rapid adoption of these solutions. According to Thomas Bittman, vice president of Gartner, agility is the main problem.

To Mr. Bittman, that agility is the key driver of private cloud computing, IT departments need to understand how their current level of services it can really make a difference. They should ask themselves, "What new services would be useful if they were provided so agile, and they must work closely with their clients to answer these questions," he says.

According to him, companies that have already started their private cloud projects often neglect issues related to the technologies themselves. This is partly due to the immaturity of some of the technologies on which the private cloud based, and partly by the fact that many companies realize a significant customization work is necessary to obtain satisfactory products from scratch.

Adapt the technical expertise to automated operation 

But, according to Gartner, the transformations required to use these technologies are even more difficult to implement. "Cloud services business processes require both rapid and tailored services provided," said Thomas Bittman.

"Computer literacy focuses on the technical expertise that is deeply rooted within IT departments do not fit a model of self-service operation, fully automatic, requiring based on teamwork approach oriented services. "

In other words, culture existing within the IT departments drives them to seek technical solutions to what they see as technical problems, whereas in today's world, it is non-technical solutions that are usually necessary.

"Too often, the private cloud projects begin with the choice of technology, but it is not the technology itself that will solve problems related to the processing teams and processes," says Bittman. Gartner proposes a radical solution: if there is no question of eliminating block IT departments must at least find different approaches that can improve the way they work.

Transform teams and processes 

"It is best to start by focusing on an approach to achieve the necessary transformation," says Bittman. "In many cases, this involves creating a separate organization, separate from traditional IT processes (at least during the incubation phase of these projects), and focus primarily on a simple project that everyone agrees with the IT department and its clients. "

According to Gartner, progress in private cloud are extremely variable, the majority of small-scale deployments starting with a limited scope and functionality. "However, as these private cloud solutions will grow, the resulting cloud infrastructures are likely based on the technologies chosen for pilot projects," analysts said.