Community General Hybrid Clouds Interoperability OpenSource

New OpenNebula VCLOUD driver: Building Hybrid Clouds with VMware cloud providers

Based in its definition, the “Hybrid Cloud Computing” is a model which combines the use of multiple Cloud services across different deployment models, including combining the use of services of public cloud services private cloud outside or inside organization / institution.
Most companies and organizations have not been born in the “cloud”, a situation that often causes the cloud resources are to be connected to traditional systems or applications with some criticality and are usually located in their own premises. This type of architecture is the most common where the keys to their success pass take into account aspects such as integration capabilities, hyper-converged management, etc.
Cloud bursting is always welcome!
Today we are one_vcloudsharing exciting news about the expansion of the number of public clouds supported by OpenNebula to build hybrid cloud deployments. As a result of the collaboration between OpenNebula and CSUC, a new addon to support VCLOUD providers has been added to OpenNebula catalogue.
“With this addon, real hybrid architectures can use OpenNebula’s rich set of infrastructure management tools to manage cloud deployments across VCLOUD private, public and hosted cloud platforms.”
The driver is developed for Opennebula 5.x and VCLOUD 5.5 version and is released today to be available for testing. The integration has been carried out using the ruby_vcloud_sdk, which interacts with the vCloud Director API, enabling a complete control of the lifecycle of Virtual Machines in a transparent way within an OpenNebula cloud. Thanks to these new addon, private resources can be easily supplemented with resources from external providers to meet fluctuating demands.


This addon gives Opennebula the posibility to manage resources in VMware vCloud infraestructures. It includes virtualization and monitoring drivers.
This driver is based on vCenter Driver and uses a modified version of ruby_vcloud_sdk.
Alt text


This addon has the following capabilities:

  • Deploy, stop, shutdown, reboot, save, suspend, resume and delete VM’s in the Virtual Data Centers hosted in vCloud.
  • Create, delete and revert snapshots of VM’s.
  • Change RAM and CPU values of VM.
  • It’s able to hot-attach and detach NICs to VM’s.
  • Automatized customization of the VMs instanciated.
  • Obtain monitoring information from the VDC, Datastore and VM’s.
  • In this development version we manage vApps with one VMs inside (A VM in OpenNebula equals a vApp with one VM in vCloud).
  • Each Virtual Data Center (VDC) in vCloud is managed as a Host in OpenNebula.
  • Import networks, hosts, templates and datastores hosted in vCloud using onevcloud script.
Need more information? You are welcome to use the OpenNebula community instruments to ask around (for instance, the forums tool is a good place to pose your questions) or reserve a seat to see details inside the next Open Cloud Free session in Barcelona (24/10 14:00h)
As always, we value your feedback and contributions to this new feature!
Barcelona UserGroup Team –

General Social

Traditional On-Premise vs Cloud Computing:

The Cloud computing business motivation is that the resources solutions on demand promise greater flexibility, dynamic, timely and green solution than traditional on-premise computing.

Therefore, we must bear in mind that migrate certain parts or all of a classic on-premise IT to Cloud can provide scalability, can reduce the costs of physical growth, reduce costs and reduce energy use .

On-premise computing needs an initial capital investment, maintenance and the costs of future updates. In contrast Cloud does not need an important initial cost so it has a lower initial investment because Cloud offer elasticity and pay-as-you go cost model.

It is interesting to find which solution is better. But it is more interesting the utilization into both solutions together to keep the best features of each .

In the paper there is an interesting analysis of cost and performance between “Traditional On-Premise” with Cloud Computing classifying the various types of costs CapEX (CAPitalEXpenditures) and OpEX (OPerationalEXpenditures) depending on the attribute to be analyzed ( Infrastructure, Business, Physical Resources, Network, Performance, Energy, budget, etc.). In short we can discuss that in Cloud Computing there are more OpEx and in the traditional on-premise there are more CapEx.

Nowadays generally on-premise infrastructure run with low utilization, sometimes it goes down up to 5 to 10 percent of average utilization. Data centers that utilize Cloud technologies are more efficient than traditional data centers. Energy is usually lost through server under utilization, because most of the time these servers are just in idle mode. But in a Cloud environment the system is managed to run at the highest efficiency. In addition, data center planning allows better power utilization. In traditional data centers, they can have cooling problems and you can run out of space for more servers. There is also a consortium of Cloud providers, who assure that its members optimize their data centers to minimize power consumption.

On-premise solution can be better, whenever if we have a constant full utilization of the IT infrastructure. This often happens in large companies that offers constant services around the world. For example, in their start Facebook was using Amazon services but finally due to their large increase in business, Facebook built his own data center, adapted to their business needs.

Cloud solutions are highly recommended in most areas. But an important factor to consider is that network latency influences negatively in the response time of the Cloud solutions. Traditional On-Premise Computing usually have better network latency and therefore the response time gives better results for the solution.

And also a lot of companies prefer to use on-premise infrastructure for its data privacy and protection. In this project, however, we do not focus on Cloud security.

In conclusion, it is necessary to analyze the CapEx/OpEx balance and the consumption depending on each own case. As we have said, what we study is the energy consumption and in the next chapter, we would like to show our structure solution of hybrid architectures and how they are a solution to reduce energy consumption, without losing too much performance.

Paper: Predicting the Energy, Cost and Performance of Cloud Computing

By Cloud Admin