The OpenNebula Team is proud to announce a release candidate for the first stable release of vOneCloud 1.0, a CentOS Linux virtual appliance for vSphere that contains all required OpenNebula services optimized to work on existing VMware vCenter deployments. vOneCloud deploys an enterprise-ready OpenNebula cloud in just a few minutes.

vOneCloud extends vCenter with cloud features such as provisioning, elasticity and multi-tenancy; designed for companies that want to create a self-service cloud environment on top of their VMware infrastructure without having to abandon their investment in VMware and retool the entire stack. vOneCloud leverages advanced features such as vMotion, HA or DRS scheduling provided by the VMware vSphere product family.

This release candidate improves the previous beta version with several bug fixes and the following new features:


Relevant Links

The OpenNebula team is proud to announce a new maintenance release of OpenNebula 4.10 Fox Fur. This release (4.10.1) comes with several bug fixes found after the 4.10 release. These bug fixes covers different OpenNebula components, like for instance the command line interface, the Cloud View self service portal, OpenNebula Core and several drivers (Auth, Storage), OneFlow and more. Check the full list of bug fixes in the development portal.

OpenNebula 4.10.1 also comes with several new features related to the new vCenter integration that made its debut in 4.10:

If you haven’t had the chance so far to try OpenNebula 4.10, now is the time to download and install OpenNebula 4.10.1 Fox Fur. As as highlight, find below the newly introduced Sunstone gateway to manage commercial support tickets designed to boost productivity.

We are pleased pleased to announce a new maintenance release of AppMarket. Release 2.0.3 solves issues reported by the community and has been verified to work with OpenNebula 4.10.

This release is part of the AppMarket 2.0.x series, which extended the AppMarket functionality by adding a new set of features that enables the management and processing of OVA files. A new component AppMarket Worker was introduced, which handles the OVA package treatment (download, unpack, OVF parsing) and image format conversion. This release also featured a new API, a new simplified import dialog, a new AppMarket interface via Sunstone, and handles VMware and VirtualBox OVAs.

Please consider that, although AppMarket is widely used by the OpenNebula users, this software has not gone through the same rigorous testing process as the main OpenNebula distribution.

Read more about the AppMarket 2.0.x series.



List of issues solved in this release:

  • Feature: Add opennebula_version to the creation form
  • Feature: Add dev_prefix and driver to the creation form
  • Feature: Fill opennebula_template input in update form
  • Bug: Remove original appliance not the newly converted one
  • Bug: Display first level app attributes for hypervisor, os-arch and format in the Sunstone tables
  • Bug: Remove testing gems from Gemfile
  • Bug: Delete job is now parsing correctly the CONF file
  • Bug: Handle properly urls that contain error prone chars like [], etc…
  • Bug: Remove csrftoken from the job creation method
  • Bug: Mime-types gem latest version can’t be installed in ruby 1.8.7
  • Bug: Fix input layout when the import fails

Go ahead and read the Install AppMarket Guide.

This edition of the conference is just around the corner, happening next 2-4 December in Berlin. If you are interested in attending the conference, we entreat you to register swiftly, since only a few seats are left.

1. An Amazing Speaker Lineup and Agenda

This year’s edition of the international OpenNebula Conference is packed with an amazing agenda. If you want to learn about Cloud Computing in general, and OpenNebula in particular. If you are familiar with the software or even an active user or contributor to the project, willing to hear and learn how other members of the community bend OpenNebula for their infrastructure needs, this is the place to be!

Take a look at the highlights from the final agenda:

2. Hacking Workshop and Hands-on Tutorial of the Brand-new OpenNebula 4.10

Besides its amazing talks, there are multiple goodies packed with the OpenNebulaConf registration. Lightning talks, a hands-on tutorial, and meeting OpenNebula users and developers are some of the treats you are in for if you are attending the conference.

One of the major benefits is the possibility to attend an OpenNebula tutorial the day before of the conference. This 3-hour tutorial is included in the registration, so everyone is welcome to attend it. The tutorial is intended for devops and system administrators interested in deploying a private cloud solution, or the integration of OpenNebula with other platforms.

For those that already master OpenNebula, we are organizing a Hacking session that is meant for people that already has OpenNebula deployed and knows how to use it. You can catch up with OpenNebula developers and have conversations that are a bit hard to have in the mailing list. It is also a great place to meet other people that may be doing similar things or have already sorted out some of the problems you may have.

3. Social Event

Right on the riverside, in a beautiful part of Berlin, you can find the old dairy farm with its historic atmosphere. You can experience the most beautiful and varied shades of nature, associated with the four seasons with them.

Last year’s conference was an absolute success, with fruity presentations of long time users of OpenNebula, and with various use cases that, we can confess, largely surprised the OpenNebula team for their artfulness. It is always a pleasure to see how people are using OpenNebula.

See you in Berlin!

Recently we decided to deploy a private cloud to replace our RHEV setup. The reasoning behind this will be covered in an other blog post, but the main reason was the higher level of automation we could achieve with Opennebula compared to RHEV. In this post I would like to talk about how we used Ansible to help us with the setup of Opennebula and what we are going to do in the near future.

Why Ansible? Well, we were already using Ansible to perform repeatable deployments in our test environments to save us some valuable time compared to “manual” setups. This way we can test new code or deploy complete test environments faster.

So when we decided to deploy Opennebula we started writing ansible playbooks from the first start because we wanted to test several setups until we had a configuration that we found performant enough and was configured the way we wanted. This allowed us to rebuild the complete setup from scratch (using Cobbler for physical deployments) and have a fresh setup 30min later. This included a fully configured setup with Opennebula Management Node, Hypervisors(kvm) and everything we needed to further configure our Gluster storage backend.

One of the advantages of Ansible is that it is not just a configuration management tool but can do orchestration to. Opennebula for example uses SSH to communicate to all the hypervisor nodes. So during the deployment of a hypervisor node we use the delegate_to module to fetch the earlier generated ssh keys and deploy them on the hypervisor. Pretty convenient..

We currently have quite complete playbooks that use a combination of 3 roles. They do need some testing and when we feel they can be used by other people too, we’ll put them on the Ansible Galaxy.

  • one_core : configures the base for both KVM nodes and the sunstone service
  • one_sunstone : configures the Sunstone UI service
  • one_kvmnode : configures the hypervisor

Until now we haven’t used Ansible to keep our config in sync or to do updates, but it’s something we have in the pipeline and should be quite trivial using the current Ansible playbooks.

Another thing we’ll start working on are modules to support Opennebula. We already had a look at the possibilities Opennebula provides and should be quite trivial to build using its API.

We are very pleased with both projects as they aim to keep things simple which is important to us since we are a very small team and have to move forward at a rather fast pace.

The playbooks can be found on github

Yes, time flies, and it is now time to celebrate the 7th anniversary of In the post we wrote last year to celebrate our sixth anniversary we described the progress of the project in terms of its community, adoption and innovation. We are really proud to confirm that those figures are growing at the same rate.

This year we would like to focus on our commitment to the open cloud. We think it is important to clearly state what “open”, “simple”, “scalable”, and “flexible” mean for us. Mostly because, as you well know, terms like “open-” and “open-source” are used by many vendors as a marketing tool to lock you into their own version or distribution of a hyped open-source software. Well, I think you know what we mean.

  • Openness means you can run production-ready software that is fully open-source without proprietary extensions that lock you in. Yes, this means that OpenNebula does not need enterprise extensions. Yes, OpenNebula is not a limited version of an enterprise software… There is one and only one OpenNebula distribution, and it is truly open-source, Apache licensed, and enterprise-ready. There is no fragmentation.  As recently stated by one of our users:

“Other open-source cloud management platforms do not work out of the box, you need to go through a vendor – they are open source but vendor-based and brings proprietary components”

  • Simplicity means that you do not need an army of administrators to build and maintain your cloud. OpenNebula is a product and not a toolkit of components that you have to integrate to build something functional. Moreover your cloud will run for years with little maintain. As recently stated by one of our users:

“It is easy to bring existing sysadmins to handle OpenNebula since it is just standard components that is used”

  • Flexibility means that you can easily build a cloud to fit into your data center and policies. Because no two data centers are the same, we do not think there’s a one-size-fits-all in the cloud, and we do not try to impose requirements on data center infrastructure. We try to make cloud an evolution by leveraging existing IT infrastructure, protecting your investments, and avoiding vendor lock-in. As recently stated by one of our users:

“OpenNebula captured my interest for several technical reasons besides the fact that it is truly open. It’s architecture is very elegant; it has C++ bones, ruby muscles and bash tendons. It’s extensible and understandable”

  • Scalability means that you can easily grow the size of each zone and the number of zones. Some of our main users have reported infrastructures with tens of zones distributed worldwide that have executed several hundreds of thousands of virtual machines. As recently stated by one of our users:

“Very simple to use, implement and deploy, but yet, you guys make it very scalable and reliable”

Fully embedded in our commitment to the open-source world, we are immersed in a disruptive move, building a bridge between the proprietary virtualization field dominated by VMware and the open source cloud arena. We are doing so with an integration between OpenNebula and vCenter, easy to use and to deploy, bringing cloud features on top of production virtualized infrastructures. VMware users can take a step toward liberating their stack from vendor lock-in. Being OpenNebula a platform independent software, they can gradually migrate to open virtualization platforms.

Looking back, it is inspiring the distance that we have come together. And that is nothing compared to what is planned for the future. We look forward to meeting you in a few days in Berlin in our second OpenNebula Conference, we have a lot to celebrate.

Thanks to all of you and happy anniversary!

On behalf of the OpenNebula Project

Tim Verhoeven, lead architect for a Business Intelligence and Analytics SaaS cloud platform at Deloitte Consultin, will give a keynote entitled “Practical experiences with OpenNebula for cloudifying a SaaS” in the upcoming OpenNebulaConf 2014 to be held in Berlin on the 2-4 of December.

Tim will speak about how his team manages a SaaS platform for Business Intelligence and Analytics applications using a diverse set of middleware (mostly IBM). However the original setup of this platform was not done using a cloud architecture. In this talk they describe the reasons for selecting OpenNebula. The architecture of the new setup. The process of migrating to that new setup and the lessons they learned during that process and in the daily operation of the platform. And finally this talk will also cover their vision for the next step which is to move towards a hybrid cloud setup.

Tim currently works for Deloitte Consulting in Belgium as the lead architect for a Business Intelligence and Analytics SaaS cloud platform. Tim Verhoeven is been involved in IT Infrastructure for more then 10 years and in these years gathered experience with Linux, networking, servers, storage and the tools and processes to deploy, manage and monitor these infrastructures.
Do not miss this talk, register now, only a few seats are left!

This case study assumes you want to build a private cloud on top of an existing virtualized datacenter composed of ten hosts (servers) running vSphere and managed by one vCenter instance. It is understood that you do not want to abandon your investment in VMware by retooling the entire stack. You want to continue managing your infrastructure with already familiar and powerful VMware tools, such as vSphere and vCenter Operations Manager. Your goal is to create a self-service cloud environment on top of your vSphere infrastructure to provide your users with a simple cloud interface featuring elasticity, multi-tenancy and self-service provisioning.

This post compares the pricing of two different approaches to build this cloud environment, the deployment of vOneCloud (an open-source replacement for vCloud based on OpenNebula) on your existing vSphere/vCenter environment versus the adoption of VMware vCloud Suite:

  • The latest version of the vCloud Suite (5.8) brings all the components needed to build and manage a vSphere-based private cloud. The three product editions, Standard, Advanced and Enterprise, include vSphere Enterprise Plus and vCloud Director. According to VMware’s official price list, the average cost (including license and support) per server (2 processors) and year (license cost prorated in three years) of vCloud Standard is €4,883.41 and € 5,243.13 for basic and production support level respectively.
  • vOneCloud requires vSphere (Standard edition is enough) and vCenter Standard. According to VMware’s official price list, the average cost (including license and support) per server (2 processors) and year (license cost prorated in three years) of vSphere Standard is €1,087.35 and €1,177.27 for basic and production support level respectively. If we add the cost of vCenter Standard (we consider a cloud consisting of 10 servers), the overall cost per server and year is €1,331.52 and €1,439.44 for basic and production support level respectively. vOneCloud is free, open-source software, and the cost of an enterprise support subscription (we consider a cloud consisting of 10 servers) per server and year is between €200 and €600 for basic and premium support.

This case study reveals savings of more than €3,000 a year per server using vOneCloud over vSphere/vCenter to build the cloud. The saving is much higher if you are using servers with more than 2 processors or building a cloud with more than 10 servers, given that vCloud licensing/support costs are per processor while vOneCloud support costs are per vCenter instance for unlimited number of processors and servers. For example, in infrastructures with 4-CPU servers, savings would be more than €6,000 per server and year. In a private cloud consisting of 10 servers, the saving would be between €30,000 and €60,000 a year.

vCloud defenders will argue that vCloud suite incorporates more features than vOneCloud on top of vSphere/vCenter. However the same arguments could be used in favor of vOneCloud, which offers features for hybrid cloud or federation that are not offered by the vCloud suite (your would require vRealize). In any case, the right cloud tool depends on your specific needs, our experience is that vOneCloud exceeds the cloud management requirements of most users.

The main advantage of vOneCloud is the strategic path to openness as you move beyond virtualization toward a private cloud. Adopting vOneCloud, you take a step toward liberating your stack from vendor lock-in. Being platform independent software, you can gradually migrate to other virtualization platforms. vOneCloud can leverage your existing VMware infrastructure, protecting IT investments, and at the same time avoid future vendor lock-in, strengthening the negotiating position of your company.

Why not give it a try?. The vOneCloud appliance does not interfere in existing vSphere configurations, procedures and workflows. This means that you can try it and if you decide not to adopt it, you can just delete it.

Update: This post was updated on November 8th 2017 to include the new pricing plans for vOneCloud enterprise support. The new support subscription prices are per vCenter instance for unlimited number of servers.

David Lutterkort, Principal Engineer at Puppet Labs, will give a keynote entitled “Puppet and OpenNebula” in the upcoming OpenNebulaConf 2014 to be held in Berlin on the 2-4 of December.

This talk will show how Puppet can be used by adminsitrators to manage OpenNebula hosts, and by users to manage their infrastructure as well as how to use Puppet during image builds. Many facets of using an IaaS cloud like OpenNebula can be greatly simplified by using a configuration management tool such as Puppet. This includes the management of hosts as well as the management of cloud resources such as virtual machines and networks. Of course, Puppet can also play an important role in the management of the actual workload of virtual machine instances. Besides using it in the traditional, purely agent-based way, it is also possible to use Puppet during the building of machine images. This serves two purposes: firstly, it speeds up the initial Puppet run when an instance is launched off that image, sometimes quite dramatically. Secondly, it supports operating immutable infrastructure without losing Puppet’s benefits to organize and simplify the description of the entire infrastructure.

David is a principal engineer at Puppet Labs and the technical lead for Puppet Labs’ development of Razor. Before joining Puppet Labs, David worked at Red Hat on a variety of management tools and served as the maintainer of Apache Deltacloud. He was one of the earliest contributors to Puppet, and is the main author of the Augeas configuration management tool.

Do not miss this talk, register now, only a few seats are left!

As you may know, the lineup and agenda for the second OpenNebula Conference (due this 2-4 December in Berlin) are already closed. These high quality contents ensure that the conference is the perfect place to learn about Cloud Computing, and to understand how industry leaders of different sectors are using OpenNebula in their datacenters.

There is however still a chance to contribute to the conference. The lightning talks are 5 minute plenary presentations focusing on one key point. This can be a new project, product, feature, integration, experience, use case, collaboration invitation, quick tip, or demonstration. This session is an opportunity for ideas to get the attention they deserve. Remember the rules:

  • Five minutes and only five minutes
  • Three slides and only three slides
  • Focus on only one key point: use case, experience, new feature, demo…

We have two 30-minute sessions for lightning talks and there are still slots available, so now is the time to register and send us your proposal!