AppMarket 2.0 RC (1.9.85)

The OpenNebula team is pleased to announce the release candidate of AppMarket 2.0.


In addition to the features included in the previous beta release, this version features a new simplified import dialog and fixes minor bugs reported by the community. Also, AppMarket Worker has been extended to support other OVF versions.


This new version can be downloaded from the OpenNebula download page and information on how to install and use it is available in Github.


AppMarket 2.0 Beta (1.9.80)

February 3rd, 2014. The OpenNebula team is pleased to announce a beta release of AppMarket 2.0. This release includes important features that are a direct result of feedback from production deployments.

This release extends the AppMarket functionality by adding a new set of features that enables the management and processing of OVA files. A new component AppMarket Worker is introduced, which handles the OVA package treatment (download, unpack, OVF parsing) and image format conversion. This release also features a new API and a new AppMarket interface via Sunstone.

What’s New in AppMarket 2.0 Beta

In the following list you can check the highlights of AppMarket 2.0 Beta:


  • Multi-image Appliances: AppMarket Appliances can now have multiple disks, which creates new possibilities to upload and register more complex and feature complete Appliances.
  • Sunstone Import: users will be able to import registered Appliances to OpenNebula via Sunstone by using pre-filled Image and Template creation forms.
  • Sunstone Views: two new Sunstone views: an AppMarket *admin* view, that allows full control of the AppMarket, and a *user* view, that allows end users to import registered appliances.

AppMarket Worker

A new horizontally-scalable component that subscribes to the AppMarket and executes jobs. It enhances the AppMarket functionality by adding:

  • OVA processing: If a URL to an OVA package is supplied, the AppMarket will be able completely process it and integrate it to its repository. This involves: downloading and unpacking of the OVA package, parsing of the OVF file and creating a corresponding OpenNebula template.
  • Format conversion: appliances registered in a specific format, can be converted to a new format.
  • Extensibility: All the operations described above are implemented within the framework of an extensible driver engine, which allows further customization and integration by the administrators.

These new features will be only available interacting with AppMarket from an OpenNebula 4.6 deployment. If you want to test them before OpenNebula 4.6 is released, you can use the master branch of OpenNebula.


The new features introduced in the AppMarket 2.0 were funded by Produban in the context of the Fund a Feature Program.


OpenNebula 4.4: Enhanced Amazon EC2 API Implementation

This is the fourth entry in a blog post series explaining how to make the most out of your OpenNebula 4.4 cloud. In previous posts we explained the new multiple datastore system with storage load balancing, the enhanced cloud bursting to Amazon features and the multiple groups functionality.

In OpenNebula 4.4 we have enhanced the Amazon EC2 API implementation exposed by the econe-server. Note that this functionality is different from the cloud bursting scenario explained in the post released days ago. The econe-server is a component on top of the OpenNebula core that translates Amazon EC2 API calls into OpenNebula actions, therefore a user will be able to interact with an OpenNebula cloud using any of the available EC2 clients or tools.

We have improved the econe-server in several ways. Now instance types are based on OpenNebula templates instead of files. You can create different base templates from Sunstone or the CLI and then make them available as instance types for users interacting with OpenNebula through the EC2 interface. These templates will be merged with the information provided by the user (i.e: AMI, user data, keypairs…) when a new instance is created. This allows us to use restricted attributes inside the templates or set permissions like any other OpenNebula resource. For more information on how to create these base templates see this guide.

$ cat /tmp/m1.small
NAME = "m1.small"
EC2_INSTANCE_TYPE = "m1.small"
CPU = 1
MEMORY = 1700
$ ontemplate create /tmp/m1.small
$ ontemplate chgrp m1.small users
$ ontemplate chmod m1.small 640

The describe functions have also been improved , for example you can query any of the resource pools providing a list of IDs, and now the describe-instances response includes instances that have been terminated recently. Thanks to Mark Gergely from MTA SZTAKI LPDS for this contribution!

The EBS support has been extended adding support for snapshotting. Now volumes can be created from a given snapshot, and snapshots can be created from running instances with an attached volume. We have also included support for resource tagging. Currently tags are supported for instances, amis, volumes and snapshots.

If you want to test any of these new features you can download the OpenNebula 4.4 beta2. The econe client is not maintained anymore, but  you can use any of the available client tools or libraries such as euca2ools, ElasticFox to interact with the econe-server.

Your feedback is more than welcome.

Back from ISC Cloud’13

Last week, we participated in the 2013 edition of ISC Cloud. The event addressed currently popular topics such as High Performance Computing (HPC) as a service, industrial and scientific application software in the Cloud, new software licence models, security in the Cloud, computing power and data protection.

The event started with a very successful hands on tutorial on “Building your Cloud for HPC, here and now, in 3 hours!”. During the tutorial, the attendees were able to deploy, manage and operate a 2-nodes OpenNebula cloud in their own laptops.

We have uploaded all the material of the tutorial, for all of those who couldn’t be there. You can find the VirtualBox images used in the tutorial and the slides here:

During the afternoon Ignacio M. Llorente described the most demanded features for building HPC and science clouds and illustrated how OpenNebula effectively addresses these challenges of cloud usage, scheduling, security, networking and storage. If you missed this talk you can find it here:

See you next time!

OpenNebulaApps 4.0 Beta Is Out for Testing

This is the official announcement of OpenNebulaApps 4.0 Beta, a suite of tools for users and administrators of OpenNebula clouds to simplify and optimize multi-tiered application management. This new OpenNebulaApps release is fully integrated with the new OpenNebula 4.0, including tabs for the new Sunstone views.

Download the OpenNebula package
Configuring and using OpenNebula Apps

We look forward to your feedback,

A Preview of the Brand New Sunstone in OpenNebula 4.0

Following the series of posts about the new OpenNebula 4.0 features, now it’s time to take a peek at the brand new Sunstone. OpenNebula 4.0 Sunstone has some beautiful new looks, but it’s not only about the external appearance  there has also been a major boost for the user experience by redefining the users workflow.

In this post we will show a few snapshots of some new Sunstone key features. The new wizard screen eases the task of creating and updating Virtual Machines. There’s also new functionality to update very easily existing resources using the extended info panel.

  • Easily edit your existing resources using the extended info panel.

  • When creating a new Virtual Machine template,  you will be able to filter and select your images with a single click.

  • Select where you want your Virtual Machine to run on.

  • Automatically add contextualization metadata to your Virtual Machines.

OpenNebula 4.0 will be available for testing, really soon. Until then, we will keep you updated with the new features in posts like this. You can also check the posts released last week about the Ceph integration and the new scheduling feature.

Stay tuned!

OpenNebula Public Cloud updated to 3.4

The OpenNebula Cloud offers a virtual computing environment accessible through two different remote cloud interfaces, OCCI and EC2, and  two different web interfaces,  Sunstone for cloud administrators and the new SelfService for cloud consumers. These mechanisms access the same infrastructure, i.e. resources created by any of the mentioned methods will be instantly available on the others. For instance, you can create a VM with the OCCI interface, monitor it with the EC2 interface, and shut it down using the OpenNebula Sunstone web interface.

This Cloud has been migrated to the last OpenNebula version, 3.4. If you have an account you can still use your old username and password. If not, request a new account and check out the new OpenNebula 3.4 features. These interfaces will show you the regular user view of the Cloud, but you will not be able to manage system resources such as ACLs, groups nor users; nor infrastructure resources such as hosts, clusters and datastores, since that will be delegated to the oneadmin group.

Operations upon this cloud will result on virtual networks and machines resource creations, but no real action whatsoever will be performed. This means that there will be the illusion that a VM is created, but in fact it won’t be running anywhere.

x509 Authentication in OpenNebula Sunstone

A new Howto on enabling x509 certificates authentication with Sunstone has been included in the OpenNebula wiki

This guide shows how to enable and use x.509 certificates for authentication in OpenNebula Sunstone. In this configuration, the authentication is delegated to Apache, or any SSL capable HTTP Proxy. If the certificate is valid, the server encrypts those credentials and sends the token to OpenNebula.