We have released a new, “refreshed” version of the OpenNebula Marketplace, with a cleaner, more efficient look-and-feel.  Pre-set filters are available for quick searches, while you can also search by keyword, as well. What’s even better is that the Marketplace will adapt to any device which you use – whether on a phone, a tablet, or a computer.

There are a lot of important components available to you on the Marketplace. And now it will be that much easier for you to explore and use.


We are sending out a huge thanks to CSUC for hosting the OpenNebula TechDay in Barcelona this past Wednesday.  It is always exciting to meet up with folks in the community, willing to share their insights and innovations, to talk about their specific use cases, and to inquire about how we can create better, more efficient solutions.  Huawei was there, as well, able to share some insight into some of the innovations they are making in ICT Infrastructure, while also sponsoring the event.  Many thanks!

We had a great agenda lined up. You can check out the presentations here:

Keep your sights squared on upcoming OpenNebula TechDays.

Raúl Sánchez from Rancher Labs.

The curious crown getting their questions answered.

Who we are

ARGO-ICT delivers managed IT services and solutions based on open technologies. Ranging from managing a single application to a fully featured private (on-premises) cloud environment.

We focus on delivering a solution that demands the least time possible of the engineers managing it, but also provides clear and traceable logs if something goes wrong and the freedom to make it fit if it doesn’t.

OpenNebula enabled us to deliver these solutions and had a lot more features we could only wish for.

Why we use OpenNebula

The environments of our customers differ a lot. From self-servicing customers to managed customers with environments consisting of virtual machines, kubernetes clusters to complete private cloud deployments. We needed a solution to support it all.

And that is exactly what OpenNebula provides in one functional package, without the need to integrate tens of components with a lot of custom work and bug fixing.

The web interface delivers our self-servicing customers an easy to use portal where they can manage their own environment. OpenNebula’s chargeback feature enabled us to make usage based billing easier than ever.

For managing customer’s environments, it provides us with all the CLI tools, API’s and drivers needed to have the freedom to approach the environment as we like and integrate smoothly.

How we use OpenNebula

We focus on automation and simplicity. To achieve this we use Ansible for configuration management. From the OpenNebula cloud environment itself to our customer environments running on it, we use Ansible to ensure the environment is according to our and our customers needs. We therefore make happily use of the OpenNebula Ansible module.

Maximizing availability using High-Availability setups for our instances was no pain at all to setup using the clearly defined Hooks in OpenNebula. Depending on the state of an instance or host, we can trigger an action. If a compute node all of a sudden goes down, all the instances are migrated to an operational compute node in a matter of seconds.

In order to provide real High-Availability a good storage solution is one of the key parts to prevent data lost and ensure the instance can always reach its own data. Our datastores use Ceph as RBD storage for all of our instances. OpenNebula made it easier then ever to setup using their Ceph RBD drivers, which just works like a charm.

To make things even simpler, we started using the OpenNebula docker-machine driver to enable our container orchestration platform, Rancher, to provision it’s own environments within OpenNebula. This enables us to provide fully operational kubernetes clusters in minutes, with just a few keyboard strokes or an API call.

Never forget the community

Exactly this, the possibility to write a blogpost, perfectly reflects the welcoming community behind the project. But also the rich, easy to follow documentation (with some basic background knowledge), helps a lot during the process.

In summary

OpenNebula is definitely our choice for a cloud management platform, because it is one complete package which contains everything you need without integrating or extensively modifying modules. Thanks to it’s easy to use API’s, Drivers and Hooks, we have a highly available platform that integrates nicely with our configuration management and container orchestration management systems. Almost out of the box.

Launching a distributed gaming cloud across 17 global locations in just 25 minutes, for little more than pocket change!

While most of today’s organizations are taking advantage of the long list of benefits offered by cloud computing, the growth of data-intensive workloads and the benefits of lower latency highlight the need to move beyond a simplistic “centralized cloud” approach. As businesses and applications serve global, mobile audiences the benefits of distributed infrastructure are becoming apparent to an expanding list of use cases.  

One clear example is gaming and entertainment.  

The growth of immersive and interactive gaming and media experiences are pushing the threshold on many levels. Just ask any twelve year-old Fortnite player, and you’ll learn all about the importance of latency and jitter – and how frustrating it is when these experiences don’t translate the way they want. The same story is being repeated across a huge range of industries and verticals, from industrial IoT and office productivity, to mobility, store automation, live entertainment or even real-time, AI-powered diagnosis of medical data.

While some of these problems are due to congestion or “last mile” issues, we’re mainly running into a simple physics problem: the speed of light!  Moving compute closer to the user dramatically changes the equation for what is possible. Enter, edge computing!

OpenNebula at the Edge

While OpenNebula has consistently provided a simple and stable platform for managing private cloud infrastructures, whether on-premises, hosted, federated, or hybrid, the new OpenNebula version 5.8 “Edge” is flexing its muscles by bringing key capabilities to create and manage highly distributed cloud infrastructures.

The ability to distribute workloads used to be the domain of only the largest websites and applications.  However, more and more organizations are looking to respond to their global users, and the public cloud has helped to lower the barrier to doing this rapidly and affordable.

But what if you’re not solely a public cloud user?  Most enterprises have diverse infrastructure, including private and hybrid clouds.  As such, being able to expand private clouds to distributed dedicated infrastructure – for instance to address the ever-growing need for low latency – is of increasing value to our users.

With our latest release, OpenNebula provides the ability to expand a cloud by instantiating hosts and clusters using bare metal resources from providers like Packet or even Amazon Web Services (AWS now offers a line of bare metal compute instances).  With a single command, users can deploy and configure new clusters using these bare metal providers in locations around the world.

Moreover, OpenNebula provides the ability to grow or reduce the size of one’s cloud infrastructure based on the active demands of the system.

A Real World Example: Gaming

To showcase OpenNebula’s capabilities, what we are going to review here is the use case of a gaming company releasing their new video game to a global audience. As they establish their OpenNebula private cloud, this (fictional) gaming company is very aware of key requirements for their platform.

  1. The broad majority of video gaming now happens on mobile devices or devices connected over WiFi. Hence, user experience will correlate very closely to response time and latency between the cloud resources and the users’ consoles. So being able to deploy their gaming services as close as possible is key.
  2. In order to meet fluctuating demands, they will need to manage their distributed private cloud environment with speed and flexibility. This means being able to dynamically grow or shrink one’s cloud infrastructure according to real time needs, creating new cloud resources where needed and scaling these resources according to dynamic user demands.  
  3. Finally, the platform needs to be highly scalable – being able to manage large-scale, highly distributed cloud infrastructures. The infrastructure cannot be limited to a single host location, but rather have the flexibility to scale in size, across multiple locations across the globe.

In this particular case, you’ll see how OpenNebula works with bare metal from Packet to provide the perfect building blocks for this use case, both at launch time and beyond.

Edge Cloud Infrastructure

Packet is a bare metal resource provider with the focus of bringing the experience of the cloud to physical infrastructure, regardless of what it is and where it resides.

The five year old company, which is backed by names just as Softbank, Dell Technologies and Samsung, manage tens of thousands of physical servers, built by a dozen different manufacturers, across three architectures and over 20 global facilities, and support 15+ official operating systems.  An important thing to note for this example is that a large percentage of Packet’s users deploy with their Custom iPXE feature, which allows each customer to bring their own OS image.

With its focus on bare metal, fast provisioning, and distributed locations Packet is a consummate platform for building out the Edge.

For this experiment, we are using the following infrastructure, provided by Packet:

Name Location Type
AMS1 Amsterdam, Netherlands c2.medium.x86
BOS2 Boston, MA USA c2.medium.x86
DFW1 Dallas, TX USA c2.medium.x86
DFW2 Dallas, TX USA x1.small.x86
EWR1 Parsippany, NJ USA c2.medium.x86
FRA2 Frankfurt, Germany c2.medium.x86
HKG1 Hong Kong, China x1.small.x86
IAD1 Ashburn, VA USA x1.small.x86
LAX1 Los Angeles, CA USA x1.small.x86
MRS1 Marseille, France x1.small.x86
NRT1 Tokyo, Japan x1.small.x86
ORD2 Chicago, IL USA c2.medium.x86
ORD3 Niles, IL USA c2.medium.x86
SIN1 Singapore x1.small.x86
SJC1 Sunnyvale, CA USA x1.small.x86
SYD1 Sydney, Australia x1.small.x86
YYZ1 Toronto, ON, Canada x1.small.x86

The underlying cloud is running OpenNebula v.5.8 “Edge”, and is instantiated on a Packet host in its Parsippany, NJ (USA) location.

This cloud then deploys and configures the host clusters, using the new OpenNebula provisioning feature, at the remaining locations. Each provision run produces a new ready-to-use dedicated OpenNebula cluster with its datastores, virtual networks and hosts.

The OpenNebula front-end host in the Parsippany was prepared using the miniONE tool, which automates the OpenNebula single-node evaluation installation, completing in just 4 minutes. For the host, we took the CentOS 7 operating system and c2.medium.x86 (https://www.packet.com/cloud/servers/c2-medium-epyc/) hardware configuration.

Hardware and Game Selection

Host clusters deployed on the locations world-wide are of 2 hardware configurations (x1.small.x86 and c2.medium.x86) with the Ubuntu 18.04 LTS operating system and KVM hypervisor. Hosts are running the OpenNebula managed KVM virtual machines with the Debian 9 guest operating system and gaming server service for the online FPS game “Wolfenstein: Enemy Territory”.

We chose this service for its maturity and simplicity. The real game which is used to demonstrate the functionality is “Enemy Territory: Legacy”. It’s an open source project that provides a compatible client (and server) for the game “Wolfenstein: Enemy Territory”.  And as we walk through the details of this assumed “product launch”, we have direct insight into the latencies of all the servers, which we will review below.

A key feature for the successful experiment is having the gaming server services reachable from the public Internet for everyone. The OpenNebula installation was configured to manage the ad-hoc public IP ranges provided by Packet and assign them to the virtual machines over the standard OpenNebula IP management interfaces. Virtual machines can now have all their services exposed to the public transparently.

Experiment Execution

Watch the step-by-step video of the use case execution (7:28)

Each provision run prepares a cluster in one location in several phases.

  • Phase 1:  The new physical hosts are allocated and deployed on the Packet, getting the clean installation of the chosen operating system.
  • Phase 2:  The OpenNebula provision feature installs and configures the hosts to be able to run the KVM hypervisor.
  • Phase 3:  New hosts are added into the OpenNebula as hypervisor hosts and the OpenNebula front-end transfers own drivers and proceed with the monitoring.
  • Phase 4:  We are ready and starting the virtual machines.
  • Phase 5:  The gaming server service is automatically installed right on a boot.

The precise installation steps are passed to each VM over the OpenNebula specific metadata (contextualization). At the end, there is a fully working game server automatically included on the list of all the other public game servers world-wide.

Hosts and gaming service VMs were started from the base OS images and configured dynamically from scratch. No images with pre-installed or pre-configured services were used. As each provision execution prepares only a cluster in a single location, several independent provisions against different locations were started in parallel.

The following table shows the actual timing of each phase for various locations:

Name Location
Phase 1
Deploy host
Phase 2
KVM host
Phase 3
by ONE
Phase 4
Start VM
Phase 5
game svc
AMS1 462 163 98 23 82 831
BOS2 444 87 11 23 105 673
DFW1 309 129 44 15 78 579
DFW2 427 125 44 22 86 707
EWR1 548 77 3 8 109 748
FRA2 346 168 97 21 84 719
HKG1 351 352 375 376 146 1504
IAD1 305 93 12 32 80 525
LAX1 342 172 77 17 96 707
MRS1 329 194 104 24 75 729
NRT1 350 328 241 46 138 1105
ORD2 452 103 24 7 89 678
ORD3 438 103 25 36 85 691
SIN1 329 424 320 58 108 1242
SJC1 341 177 89 19 117 746
SYD1 345 462 342 60 171 1383
YYZ1 308 102 16 9 82 520

One can see that the quickest of all deployments was the Toronto (YYZ1), taking 520 seconds (just over 8 minutes) in total. The longest was in Hong Kong (HKG1), taking 1504 seconds (just over 25 minutes).

Times to deploy a host on Packet are quite consistent, with low variance. When we configure the hosts as a KVM hypervisor, the latency between front-end and host, or performance of the nearest OS packages mirrors in the locality is taken into account. Time to monitor the host by OpenNebula is only affected by the remote host latency and network throughput.

The same applies for the virtual machine start, as the base VM image (320 MiB) must initially be transferred from the front-end to each hypervisor host. For the distant hosts to the front-end, the image transfer times can be pretty long (for example 171 seconds to Sydney, SYD1). During the game service bootstrap, we depend mainly on the performance of the nearest OS packages mirror.

Below is a screenshot of the deployed and configured servers hosting the Enemy Territory video game. If you pay attention to the “PING” metric, you’ll notice the latency measured from the client from where we orchestrated this exercise (Brno, Czech Republic) to the various nodes.  Understandably, the host location with the shortest latency was Frankfurt, Germany (FRA2) with 18ms. Compare that to a latency from Czech Republic to Sydney, Australia and you’ll see a latency of 331ms (almost 20x longer).

The ideal situation would be to stand up resources as close to the user base as possible.  So users in relative proximity to the nodes will experience latencies below 10ms.

So, with this OpenNebula distributed cloud infrastructure using core and edge bare metal resources by Packet, players of Enemy Territory will be directed to the node with the shortest latency, providing optimal performance. And the infrastructure admin will have the flexibility to flex resources in each cluster in accordance with the active traffic.  

And from the standpoint of clearing out the entire cloud architecture – the simultaneous execution of the host deletions took no more than 49 seconds.

What does a platform like this cost?

Packet has an innovative business model and a strong foothold that at the forefront of the rapidly developing technology ecosystem. It is worthwhile digging deeper into Packet’s offerings. The hourly rate for the resources hosting our Enemy Territory video game distributed cloud cost no more than $11.40/hour!

The conclusion is clear

OpenNebula v.5.8 Edge takes a fresh approach to creating a private distributed cloud by not only broadening support for lightweight LXD containers, but as we have seen here, by integrating support for simple cloud deployment on bare metal resources from providers like Packet. An administrator having the ability to create and manage a distributed private cloud with nodes in 17 locations around the world, deploy and configure them with a few clicks of a button, and to subsequently be able to flex those configurations on the fly – all within 25 minutes and for under $12 / hour – that sounds like a perfect building block for platforms of today, and tomorrow.

Executive Summary

We’d like to thank all of you who shared your perspective on OpenNebula as part of our 2018 Architecture Survey. This is the fourth architectural survey of OpenNebula since 2012, and the results were collected during the period of December 4, 2018 through January 11, 2019. Your participation here is fundamental to our strategic focus to best provide features and support that align with the infrastructures platforms and configurations demanded by you.

We have only included in the analysis the respondents that are using OpenNebula 5.x (latest series) and who we deem reliable because they have provided identification details that allow us to verify the answers of the survey. This is important given that our main aim is to have accurate and useful information about OpenNebula deployments. This survey is not a market survey and does not express all OpenNebula deployments worldwide.

The data provided helps to shed light on how OpenNebula is being used by the community, as well as providing some indicators of where to aim for the future. In comparing to our previous survey taken in 2015, there are some other notable findings:

  • The types of workloads handled by OpenNebula is evolving, with a growing proportion (85%) of them being run in a Production environment, while also having others running in Dev/Test (73%) and in a Proof of Concept mode (29%). OpenNebula shows its increasing maturity, compared with 73% of deployments in production reported in our previous survey.
  • A few other indicators of its developing stability are both the Number of Users supported by OpenNebula clouds, as well as the Number of Nodes.  For each of these metrics, there has been steady growth across the board.
    • The growth in user count for OpenNebula clouds has progressively increased with now close to 20% servicing more than 1,000 users.  Smaller OpenNebula clouds, of 100 users or less, now constitute 45%, which is down from 70% in 2015.
    • And “node count” has seen steady growth as well, with 77% of cloud environments having more than 10 nodes, (up from 56% in 2015). Similarly, we see that 29% of cloud environments have more than 100 nodes, where in 2015 that figure was 20%.
  • Usage of OpenNebula in Commercial and Industrial enterprises continues to grow.  Its employment in organizations across various industries shows a growing distribution with increasing usage in IT, Telecommunications and Internet, and Hosting and MSP’s, and Media and Gaming sectors – mounting to 75% of total usage.  And while still an important sector of OpenNebula usage, Academia and Research constitutes a smaller percentage of the overall – now 14%, down from 25% in our last survey.
  • Hybrid cloud usage continues to grow, with an increasing percentage of OpenNebula integration with AWS (39%), as well as with Microsoft Azure (22%).
  • With the advent of Configuration Management and Remote Execution tools, we see that a hefty segment of OpenNebula users (73%) are taking advantage of these to introduce automation to their environments.
  • A growing usage of CentOS as an Operating System has reached 50% across our survey participants, while usage of both Ubuntu and Debian have remained fairly steady at 42% and 22% respectively.

And OpenNebula continues in its aim to be the simplest and most flexible open source solution for private cloud and data center virtualization management.  Our user community rates it highly because of its Simplicity (83%), its Openness (69%) and Flexibility (56%), as well as its Vendor-neutrality (52%).

Thank you again for participating in our survey! Below you can review the detailed results.

A.  About the Organization

This year we broke out the demographics across multiple categories, with “Information Technology”, “Cloud Hosting and MSP’s”, and “Telco and Internet” companies assuming large portions of the demographics – but those added together with “Media and Gaming” and “Web, SaaS, and eCommerce” total up to a growing 75% of Industrial/Commercial users. 14% of users work in Science, R&D, and Academia, while just under 11% work for Government and Non-Profits.

Type of Organization


Usage by larger companies has steadily grown over time, now reaching 20% of companies with 5,000 employees or more, compared to 13% from our last survey.  While smaller companies – (of 500 employees or less) – continue to be avid users of OpenNebula, that demographic constitutes a smaller base of 58%, compared to 64% from our last survey.


Size of Organization (# of employees)


48% of deployments are located in Europe or in Russia, a slight shift downward from 50% in our last survey. We also see a small tick upward in growth within North America to 33% from 30%. These two geographic regions continue to lead the usage of OpenNebula by a large margin.

Geographic Region


B. About Cloud Usage

The usage of OpenNebula for Production workloads has seen steady growth to 85%, from 73% in 2015. Its use for Development and Testing has remained firm at 73%, while there is significant Proof of Concept work being done, as well (19%).

Type of Workload (allows for multiple selections)


It is logical that the “On-premise private cloud” remains the most common type of cloud being built with OpenNebula, with 78% of respondents confirming it being part of their cloud infrastructure.  However, again the widening types of clouds being created is evident with 54% of users venturing into “Hybrid private clouds”, 55% creating “Federated private clouds”, and 17% and 26% creating “Hosted private clouds” and “Distributed private clouds”, respectively.  Even 8% are beginning to venture in creating “Edge private clouds”. With the imminent release of v.5.8 Edge, it will be interesting to see how that last figure grows.

Type of Cloud Architecture (allows for multiple selections)


And from a use case perspective, 71% of organizations use OpenNebula for “Data Center Virtualization management”, and 48% use it to establish “Public Clouds, VPS and MSPs”.  39% of users take advantage of OpenNebula to create cloud environments on top of their VMware infrastructure, and 37% are laying the groundwork for Enterprise clouds.

Type of Use Case (allows for multiple selections)


Since 2015, the number of users in most OpenNebula clouds has seen significant growth.  Clouds with more than 1,000 users have reached 19% from 8%, while the smaller ones of 100 users or less now constitute 45%, from 70% in 2015.

Number of Users


Another new question we introduced this year had to do with understanding with which other Cloud providers users interact.  Amazon Web Services (AWS) is, by far, the most common at 61%, with Microsoft Azure following at 35%.

Interaction with Other Cloud providers (allows for multiple selections)


C. About Cloud Configuration

59% of OpenNebula environments are “federated”, meaning that they have more than a single zone, and 9% are running more than 10 different zones.  This is up from 51% and 5%, respectively, from the last time we collected data.

Number of Zones (OpenNebula instances)


Node count – another metric in measuring cloud size – has steadily increased, as well.  77% of cloud environments have more than 10 nodes, which is a significant increase from 2015 when this measure was 56%.  And currently 29% of cloud environments have more than 100 nodes, where in 2015 that figure was 20%.

Number of Nodes


KVM hypervisors remain the most commonly used hypervisors in OpenNebula environments. Yet, usage with VMware hypervisor continues to be a very solid use-case. The percentage of KVM users has stayed fairly steady, at 75% compared to 73% previously.  And usage with VMware hypervisors has increased slightly, at 39% compared to 37%.

Hypervisor usage (allows for multiple selections)


56% of users have implemented some form of a “hybrid cloud” in their environment. And the most popular Public cloud providers used in tandem with OpenNebula are Amazon Web Services (AWS) at 39% and Microsoft Azure at 22%.  These two were most popular in our last survey, as well, but have increased slightly, where they were 30% and 16% respectively.

Public Clouds used for Hybrid (allows for multiple selections)


Shared datastores at 53% and Ceph at 40% remain the most widely used storage solutions in open environments – while Shared datastore usage dropping slightly from 60%, Ceph has remained the same at 40%. VMware FS at 38% is used in VMware-based deployments, mainly through vCenter, and dropped slightly from 40%.

Storage configurations (allows for multiple selections)


The most common network configuration is still the Standard Bridged network configuration (40%). 802.1Q VLAN (31%) and Open vSwitch (25%) remain widely-used choices as well, while there has been some movement to VXLAN and OpenSwitch VXLAN with 14% and 10% respectively.  And for VMware deployments, we see a steady usage of VMware networking (37%), primarily used through vCenter.

Networking configurations (allows for multiple selections)


Authentication practices, while shifting slightly to using external authentication systems, have remained fairly static.  The majority of deployments use the built-in User/Password authentication (68%), and LDAP, and Active Directory have gained slightly more traction since the last survey with 22%, and 21% usage respectively. SSH, while widely used (42%) has seen a slight drop from 50%.

Authentication configurations (allows for multiple selections)


CentOS and Ubuntu are still the most popular Linux distributions for creating OpenNebula clouds with usage at 48% and 41% respectively, which is a slight upward movement from 44% and 40%.  Debian has remained steady at 22% usage.

Operating Systems (allows for multiple selections)


A new question was introduced to understand what types of configuration management systems are employed to take advantage of automation.  The most common platform is Ansible, with 50% usage. Puppet is another popularly used tool, at 29%. There are a few other tools used with some regularity, like Chef (8%) and SaltStack (6%). And 27% of respondents state that they do not use any configuration management system at all.

Configuration Management (allows for multiple selections)


Similar to the types of configuration management systems, we asked which tools are used to deploy OpenNebula, and the same set of tools lined up in a similar fashion. Ansible is the most-commonly used with 40% usage, and Puppet is used by 21%.  Tools like Chef (5%) and SaltStack (4%) have a small user base, while 41% of respondents state that they do not use any deployment tools.

Deployment tools (allows for multiple selections)


Another question asked inquired about Container or PaaS tools being used to manage applications.  While a large part of the respondents (48%) state that they are not yet using these types of tools, for those that are using these types of tools, the most commonly used is Kubernetes with 25% usage. Docker Swarm (14%) and OpenShift (10%) follow in popularity, while 9% of respondents state they are building their own solutions.

Container / PaaS for Application Management (allows for multiple selections)


When asking about which Advanced Components are used or planning to be used, a large selection of components were confirmed.  The most commonly selected was “High Availability” at 65%. Other popular components are “Application Containerization” (47%), “Data Center Federation” (43%), and “OneFlow” (42%).  A few others are listed, while 14% state that they are not using or interested in using any advanced components, just yet.

Advanced Components (allows for multiple selections)


From a provisioning interface perspective, a large majority of OpenNebula users are taking advantage of the Sunstone interface (82% of users). The CLI and API both have a fairly extensive usage across the community with 41% and 39% respectively, and the Cloud View (Self-Service portal) has 27% of usage.

Provisioning Interfaces (allows for multiple selections)


We inquired about which OpenNebula API’s are being used or planned to be used in the near future, and curiously, a very large constituent (45%) has shown interest in being able to soon utilize Python bindings when v.5.8 is released. Of other API’s currently available at the time of the survey, use or intended use of Ruby bindings is common with 26%, while JAVA and Go bindings follow with 16% and 13% respectively.  29% of users state no current interest in using OpenNebula API’s.

OpenNebula API’s (allows for multiple selections)


And lastly, as seems to be the case for many years running, “Stability”, “Flexibility”, and “Openness” continue to be the top reasons why users choose OpenNebula.

Why OpenNebula? (allows for multiple selections)


Thank you again!

Stay connected!


Packet has announced its Edge Alliance Program, in which OpenNebula is one of the Initial Program participants.  This collaboration has been picking up steam over the past year, as focus is taking shape on Edge computing, and both platforms see a natural synergy to provide innovative solutions.  OpenNebula is just minutes away from its new version release of 5.8 “Edge”, which among other edge-focused capabilities, like providing native support for lightweight LXD containers and Automatic NIC selection, offers the ability to use bare metal providers (like Packet) to build remote clusters and to easily create Disaggregated Data Center environments along the Edge.

Packet’s Edge Alliance Program is a bold step toward encouraging innovation and providing “free access to edge computing building blocks”.  The newly announced availability of two edge sites in Chicago (IL), and a site separately deployed near Gillette Stadium in Foxborough (MA) is just the beginning of their goal to launch 15 separate site locations in 2019. With the perfect timing of OpenNebula’s 5.8 Edge release, it will become second-nature to provision Packet bare-metal resources within your cloud.

Check out more details about Packet’s Edge Alliance Program, and get engaged!

And read here for more details on OpenNebula’s partnership with Packet.

OpenNebula-based Edge Platform to be presented in 2019 Mobile World Congress

With OpenNebula as a core component, CORD (Central Office Re-architectured as a Data Center) will be featured in Telefónica’s Edge Computing demos at the Mobile World Congress in Barcelona, Spain from February 25-28. Stop by Telefonica’s booth (Hall 3, Stand 3K31) to see the new generation of Central Offices that are fully IPv6 compliant and allow for the deployment of programmable services rather than the traditional black box solutions provided by proprietary solutions.

Telefónica’s CORD prototype aims to meet low-latency demands of the emerging Internet of Things ecosystem and to virtualize the access network and give third-party IoT application developers and content providers cloud-computing capabilities at the network edge.

You can find more details surrounding the solution in this Open CORD blog.
Below are some video presentations given by Telefónica on how OpenNebula forms a key element of their innovative solution:

v.5.8 Release Candidate is available!

OpenNebula v.5.8 “Edge” is just about ready!  The Release Candidate is now available for download, which includes several bug fixes.

A huge thanks goes out to the User Community, as several of the bug fixes were found and brought to our attention by you!

For the latest details about what you can expect from v.5.8 Edge, read about it below:

Relevant Links

Beta version 2 is ready!

You will have seen our communication a few weeks ago announcing the exciting release of OpenNebula v.5.8 “Edge” – Beta version, which has been available for download.  It was a first look at the exciting new capabilities on which we have been working with a focused attention on providing edge computing capabilities in OpenNebula, as well as bringing broad enhancements recommended by our User Community.

Now, we are excited to announce the release of our Beta Version 2.  We got some great feedback from the Community over the past few weeks. While we have addressed some code fixes, we also introduced a few additional features:

  • We have added a new option for searching and filtering VM’s.
  • From a vCenter perspective, the ability to migrate datastores and clusters is now operational.
  • And you can see below the template for LXD containers!!

Once again, here’s a reminder that this is a beta release.  Its aim is for testers and developers to try the new features, and to send more feedback for the final release. Also note that being a beta, there is no migration path from the previous stable version (5.6.1) nor a migration path to the final stable version (5.8.0). A list of open issues can be found in the GitHub development portal.

Relevant Links


Call for Translations – extended until February 4, 2019!

We are tying up the last details for the OpenNebula 5.8 “Edge” version release.  However, before we do so, we need some help with some final translations for the Sunstone GUI portal.  Whatever help you can provide would be great!  Remember, you can translate one string at a time.

The following languages are included in current version 5.6, and the highlighted  ones require additional translations in order to be included for version 5.8:

* Catalan
* Danish
* German
* Greek
* Japanese
* Lithuanian
* Persian
* Polish
Portuguese (Brazil)
* Portuguese (Portugal)

We’ll close the Call for Translations on Monday, Feb. 4.  Thank you for this one last push!