Cloud computing Vision: Crossing the mixed cloud model gap

Cloud computing often creates many problems, and companies don't know where to start. The discussion between the public cloud and the private cloud goes on and on, deciding which cloud service architecture to adopt, or even arguing over who is the driver of the cloud-the personal business unit or the IT department. Regardless of how the architecture, enterprises need to consider in the process of approaching the cloud is to use "from the outside (Òoutsideó in)" or "from the inward (Inside Out)" method.

From an outward-interior cloud model

Business scope (LOB) Planners consider the cloud as "externally based" models, and they want cloud computing to make it a more strategic operational component. These "extroverted" clouds see the need to buy capital equipment and software, support a data center, and internal it activities, along with potential cost problems and apparent agility impediments.

These planners want to visualize all it software as a service (SaaS), able to quickly appoint and deallocate applications to respond to business needs. This "external" cloud planning vision begins when you want cloud computing to look at end users.

The cloud model from inside to outside

On the other hand, many enterprises use the cloud as an "introverted" approach, as an alternative platform for running applications, or as an extension of the data center. This vision underscores the need for fixed public cloud services to match their current datacenter technology architecture, allowing applications to run seamlessly when data center overload or failure occurs.

"Introverted" vision thinkers consider cloud services, whether infrastructure, service (IaaS) or platform-service (PaaS), depending on whether there is a single local domain software platform or whether it supports multiple operating systems and middleware. This vision of cloud computing starts with what the enterprise has and how it develops.

Comprehensive cloud Computing

The cloud project includes collaboration between it and LOB planners, which is more effective than it and LOB separate cloud projects.

The key to a successful cloud deployment is to combine the two, the internal and external teams. One way to keep these two teams in harmony is to make their business applications look like SaaS. This is done largely by customizing the end-user view by dragging data from the available APIs to its graphical user interface (GUI). In most cases, this process is not dominated by the cloud, but it is important to ensure that the tools used to complete the APIs that have access to cloud hosting are available.

All SaaS applications operate through the API, and if a business hosts its application to the cloud, these applications must be able to work with the Cloud APIs. Cloud service providers can provide guidance on how these cloud application APIs are accessed, and cloud application integration tools can assist in the successful completion of this task.

Resource-level flexibility is another concept that can bridge these two approaches to cloud computing. Building a pool of resilient application resources, including local servers and public cloud services, will be key to a federated "inside" and "outside" cloud model. The challenge is to seamlessly integrate internal IT resources and shipping resources, a method that managers can use to build private clouds or extend existing virtualization tools.

Constructing cloud model of hybrid cloud Bridge

Some companies implement cloud strategies, including the functionality of public and private clouds. Some popular cloud platforms, including OpenStack, Cloudstack, Eucalyptus, and Hadoop, allow businesses to mix and match public and private cloud resources.

For these mashup cloud choices, it is important to carry out small-scale testing, and the interaction of resources between any specific public cloud and private cloud must be made clear in the service level agreement or in the contracts of all cloud service providers.

In addition, many businesses build hybrid clouds, benefiting from public and private clouds. However, to build a hybrid cloud, IT departments must first ensure that they build a private cloud with the right functionality.

In doing so, it is important that no private cloud software can create a resource pool; Infrastructure as a service (IaaS) and platform as a service (PaaS) can provide resources on demand, and for end users, there is no difference in functionality in virtualized data centers. To bridge the private cloud and public cloud, find tools to provide server load and functionality, as well as tools that are compatible with virtualized software that is already in use.

At the network level, creating a flexible hybrid cloud means that the selected network tools can be virtualized in the same way as virtualized servers and storage. Virtual Networks (VLANs) and virtual private cloud networks (VPNs) may be the best framework for creating this flexible cloud, but connecting public cloud resources to VPNs requires specific support, usually from network vendors and public cloud providers.

(Responsible editor: The good of the Legacy)