OpenNebula Conf 2016 is getting closer and we would like to keep sharing with you the companies/projects that are sponsoring this year’s conference. Now it is time for OPEN-V, as part of our Gold Sponsors.


If you want to participate in OpenNebulaConf and meet OPEN-V and other OpenNebula users, remember that you are still in time for getting a good price deal for tickets. Also, if your company is interested in sponsoring OpenNebulaConf 2016 there are still slots.

About Open-V

OPEN-V’s Flagship product StackMAX is a unified intelligent cloud platform managing the Cloud landscape from a single point, smartly connecting infrastructure, data, applications and business processes. StackMAX is engineered to deliver “everything as a service,” enabling enterprises to consume core business services on demand and respond / innovate faster, at unprecedented scale.

Thanks to OpenNebula project and community which has enabled OPEN-V to focus on Cloud innovation and not worry about core IAAS and orchestration services. The simple and straight forward architecture of OpenNebula with extensive documentation has enabled OPEN-V to deliver StackMAX with rock solid reliability and powerful orchestrator services towards our Global customers across varied Industries.

OPEN-V delivers StackMAX along with optional module – ContainerMAX which mainly focuses on difficulties surrounding image building, orchestration of containers, logging and monitoring them.

Screen Shot 2016-06-08 at 2.43.01 PM



Date and Time: Mon, October 24, 2016 2:00 PM – 5:00 PM

OpenNebula Barcelona User Group is a gathering of our users in Barcelona area to share best practices, discuss technical questions, network, and learn from each other and enjoy. Direct Link

Taking advantage of the Opennebula conference in Barcelona, its user group in collaboration with the Opennebula project and CSUC organizes a free open cloud session to introduce the project, share new local developments and use cases with the community and any people interested in Open Cloud topics (Free Registration).

Agenda: (Free Registration -> Register here and reserve your seat)

14:00 Welcome/Bienvenida/Benvinguda
14:05 Opennebula Project: Open Cloud in essence – Dr. Ruben Santiago Montero (Chief Technical Officer & Co-Founder)
14:30 Cloud Bursting and VMware: New Opennebula VCLOUD driver  – Jordi Guijarro (Cloud & Security Manager – CSUC)
14:50 Barcelona Users Group
15:00 ACB League use case – Joaquin Villanueva (Director of Media Technology)
15:20 UPC Research Lab (RDLAB) use case – Gabriel Verdejo (IT Manager)
15:40 University of Valencia use case – Israel Ribot (System Administrator)
16:00 Coffee & Networking
16:30 EOF

Free Registration -> Register here and reserve your seat

ONEBCN Team in collaboration with CSUC

OpenNebula Conf 2016 is getting closer and we would like to keep sharing with you the companies/projects that are sponsoring this year’s conference. Now it is time for Todoencloud, as part of our Silver Sponsors.

If you want to participate in OpenNebula Conf and meet Todoencloud and other OpenNebula users, remember that today is the deadline for getting a good price deal for tickets. Also, if your company is interested in sponsoring OpenNebulaConf 2016 there are still slots.

About Todoencloud

In Todoencloud, we think that the Cloud should be democratized and made simple in its day to day operation, where the language that is spoken should be the language relevant to the business and not the resources on which it is grounded. For this, we translate all our know-how and expertise as Cloud and system architects to the IT customer departments to build the resources with a particular focus on the group of its business’ applications in a specific Cloud environment or with Cloud several providers. Our cloud is Open, Isolated and Secure, thanks to OpenNebula console and its powerful and amazing functionalities

Screen Shot 2016-06-08 at 2.43.01 PM

OpenNebula Conf 2016 is getting closer and we would like to keep sharing with you the companies/projects that are sponsoring this year’s conference. Now it is time for LINBIT, as part of our Platinum Sponsors.

If you want to participate in OpenNebula Conf and meet LINBIT and other OpenNebula users, remember that you are still in time for getting a good price deal for tickets. Also, if your company is interested in sponsoring OpenNebulaConf 2016 there are still slots.


LINBIT is the leading Linux based storage replication provider. They work with industry leaders from the storage and network sectors, designing next generation critical infrastructures. Major cloud solutions providers, data center operators, OEM and ISV integrators and commercial enterprises employ LINBIT’s open source software DRBD to ensure High Availability and Disaster Recovery replication. LINBIT is privately-held and headquartered in Vienna, Austria and Portland, OR.

The DRBD Software Defined Storage solution, comprised of the DRBD9 Linux kernel driver and the DRBD Manage provisioning software, can be used as image storage for OpenNebula. This makes OpenNebula’s philosophy of Infrastructure As A Service extend to another important aspect: high availability.

Screen Shot 2016-06-08 at 2.43.01 PM

OpenNebula Conf 2016 is getting closer and we would like to keep sharing with you the companies/projects that are sponsoring this year’s conference. Now it is time for Terradue, as part of our Silver Sponsors.

If you want to participate in OpenNebula Conf and meet Terradue and other OpenNebula users, remember that you are still in time for getting a good price deal for tickets. Also, if your company is interested in sponsoring OpenNebulaConf 2016 there are still slots.

About Terradue

 Terradue was founded in 2006 as a European Space Agency (ESA) spin-off. Our mission is to innovate data integration and analysis Cloud services for Earth Sciences. Today, user communities working on Terradue Cloud Platform contribute to research ecosystems where public and private sectors jointly develop skills for the new digital, computational science. Our flagship solution for massive processing of Earth Observation data is orchestrated using OpenNebula. Terradue’s Private Cloud is also using OpenNebula for its very effective, customizable cloud technology. As an open source project, OpenNebula offers a strong vehicle to contribute enhancements, and build dedicated solutions for our customers. Terradue is an OpenNebula Partner since 2013, from which we appreciate direct interactions with support, well-established branding rules, a joint vision to develop OpenNebula markets, and good visibility on the OpenNebula roadmap. At the OpenNebula Conference 2016, we will also present our future endeavours in building Digital Marketplaces, allowing user communities to cross-fertilize cloud-enabled tools and data repositories for Earth Sciences.

Screen Shot 2016-06-08 at 2.43.01 PM

Screen Shot 2016-06-08 at 2.43.01 PM

As you may already know, this year OpenNebulaConf is taking place in Barcelona again, on October 24-26.  If you are willing to attend and can save now the date you can take advantage of a 40% discount in your Conf tickets until mid July.

Guided by your feedback from previous editions, we have changed the traditional format of our conference this year and have included more community sessions to learn and network. We have just published a preliminary agenda with the main sessions.


There will be three pre-conference tutorials in the afternoon of October 24th:

  • OpenNebula Introductory Tutorial
  • OpenNebula Advanced Tutorial
  • Invited Tutorials (to be announced)


During the conference, we will have four keynotes. In a few days we will announce our impressive line-up of keynote speakers.

Community Sessions => CALL FOR SPEAKERS!

The Conference includes several community sessions:

OpenNebula User Workshops with presentations by community members describing aspects related to their use of OpenNebula:

  • Research projects
  • User experiences
  • Case studies
  • Best practices
  • Any other topics that you feel are relevant to users, administrators, and architects

Hands-on Workshops with presentations by community members related to storage, hypervisors, networking, federation and security with OpenNebula:

  • Deployment scenarios
  • Integration
  • Tuning & debugging
  • Best practices
  • Any other topics that you feel are relevant to developers and integrators

The Call for Speakers is open until June 24th, 2016. Speakers will receive a 50% discount in their registration to the conference.

If you want to get an idea of the past OpenNebulaConf sessions, including talks from companies such as CentOS, Runtastic, Puppet Labs, Cloudweavers, RedHat, Produban, Unity, Deutsche Post, please check our Youtube channel or download the presentations from our SlideShare account.

The agenda also includes new sessions to Meet the Experts, aimed at providing an informal atmosphere where delegates can interact with experts who will give their undivided attention for knowledge, insight and networking.

Sponsorship Opportunities => CALL FOR SPONSORS!

You can learn about the different sponsorship opportunities at the Conference web page. Current sponsors of the OpenNebulaConf 2016 include StorPool as Platinum Sponsor, NodeWeaver as Gold Sponsor and Terradue as Silver Sponsor.

And last, but not least, do not forget the main reason that allows these conferences to exist! Check out our evening events in prime locations of Barcelona, the city that never sleeps.

Next week, on the 13th of May 2016, will host a new edition of an OpenNebula Cloud TechDay.

This TechDay will feature a 4-hour hands-on tutorial in which you will learn how to install and configure an OpenNebula Cloud from scratch. The presentations in the afternoon will be focused in Ceph. We want you to learn as much as possible about Ceph best-practices and how to use it with your OpenNenbula Cloud.

The agenda for the afternoon is:

  • Object scale out with Eternus CD10000 by Walter Graf and Frits de Kok from Fujitsu.
    Introduction to object storage, Ceph concepts and internals and how Fujitsu managed to overcome administrative challenges involved in running a Ceph cluster.
    Fujitsu and BIT will be giving a demo of Fujitsu CD10000 and OpenNebula.
  • Building the Dutch National Archive with Ceph by Wido den Hollander, Part of the Ceph Board.
    The Dutch National Archive has chosen Ceph to store their data on in Groningen, The Netherlands. Together with ODC Noord I’ve built the 8PB Ceph cluster running in a IPv6-only network. This talk will go in-depth in the design decisions made when building this cluster.
  • The OpenNebula Ceph Drivers by Jaime Melis from OpenNebula Systems.
    Overview of the Ceph Drivers. Configuration attributes, peculiarities. Everything you should know about before deploying your OpenNebula + Ceph cloud.
  • BIT’s experiences playing with Ceph and OpenNebula by Stefan Kooman from
    BIT has been running a Ceph test cluster for some time and will talk about their experiences so far. A live demo is planned where we will test Ceph’s ability to recover from failure.

Join this TechDay to learn about OpenNebula, the Cloud, Ceph and benefit from the expertise of the speakers!






More information
Register for this Event

Executive Summary

This is the third survey of OpenNebula deployments since September 2012. The results of this voluntary survey were answered online between December 3, 2015 and December 11, 2015. While previous surveys were open for several months, responses in this survey were collected only over a period of one week because its goal is to have a snapshot on the architectural components of existing OpenNebula clouds in order to improve support for the most demanded infrastructure platforms and configurations.

Although several hundreds of organizations took part of the survey, we have only included in the analysis the 190 respondents that are using OpenNebula 4.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. Since the foundation of the open-source project in November 2007, OpenNebula has been downloaded more than 360,000 times from the project site (280,000 times since our first survey in September 2012 and 160,000 times since our latest survey in August 2014), not including other software repositories or third-party distributions.

Regarding the use of OpenNebula, the Survey shows 43% of overall deployments are in Industry and 13% in Research Centers. Most of organizations (80%) are in Europe, Russia or North America and use OpenNebula to build private clouds (93%). When asked about the type of workload, 73% said that they use OpenNebula for running production workloads.

Regarding the size of the clouds, 80% of deployments have fewer than 100 nodes and 10% of deployments have more 500 physical nodes. 51% of deployments consist of more than one OpenNebula zone and 5% run more than 10 zones. Among the advanced components offered by OpenNebula, High Availability at 73% is the most widely used, in correspondence with the predominant production usage of OpenNebula.

Regarding the building blocks of the cloud, KVM at 79% and VMware vCenter at 37% are the dominant virtualization platforms, and CentOS at 44% and Ubuntu at 40% are the most widely used linux distributions for OpenNebula clouds. The preferred choices for the storage back-ends are shared FS and Ceph at 60% and 40% respectively. Regarding networking, most of the deployments, 45%, use the Standard Linux Bridge for network configuration, 35% use 802.1Q, and 33% use Open vSwitch. 44% of deployments use the hybrid cloud functionality offered by OpenNebula. Amazon EC2 at 30% and Microsoft Azure at 16% are the most widely used public clouds.

In comparison to previous survey findings in 2014, there have been some changes:

  • OpenNebula shows its increasing maturity, with 73% of deployments in production compared to 62% reported in our previous survey.
  • Growth in North America has accelerated, now representing 30% of responses, up from 20%.
  • KVM provides the majority of OpenNebula support, growing from 48% to 79%.
  • There is a high rate of adoption in VMware environments from 28% to 37%.
  • Ubuntu grows from 36% to 40% and Debian falls from 33% to 22% as operating systems to build the cloud.
  • The use of the EC2 cloud API decreases from 25% to 10%.
  • The use of Ceph has grown considerably from 17% to 40%.
  • The use of LVM as storage solution decreases from 22% to 12%.

On the whole, OpenNebula continues to be loved by its users for its flexibility, 82%, simplicity, 80%, and openness, 72%. These results are aligned with our our mission — to become the simplest cloud enabling platform — and our purpose — to bring simplicity to the private and hybrid enterprise cloud. OpenNebula exists to help companies build simple, cost-effective, reliable, open enterprise clouds on existing IT infrastructure.

We would like to thank all respondents that took part in the survey!

A. About the Organization

43% of respondents indicated that they work for industry, while 13% work for research centers. These are similar to previous survey results.


Type of Organization


50% of deployments are in Europe and Russia. This means a small reduction compared with previous survey data where the number of deployments in Europe and Russia was 54%. The number of deployments in North America grows from 20% to 30%. 80% of respondents are located in Europe, Russia, and North America.


Geographic Region


65% of organizations are small companies with fewer than 500 employees, and only 7% has more than 10,000 employees.


Number of Employees in the Organization

B. About the Type of Cloud

93% of respondents are running a private cloud for internal operations, while 34% are running a public cloud to offer utility services. Compared with previous survey data in 2014, the number of public clouds decreases from 40% and the number of private deployments increases from 84%.


Type of Cloud (people may select more one checkbox)


73% of respondents are running non-critical environments or peripheral installations for running testing or development applications, while 73% are using the cloud for running production workloads. We see that OpenNebula is increasingly mature, with more deployments moving into production stage as compared with prior surveys data, from 42% in 2012 and 62% in 2014.


Type of Workload (people may select more one checkbox)


The number of users in most of the clouds, 70%, is fewer than 100. Many of these deployments use OpenNebula as virtual data center infrastructure manager and not as a cloud provisioning platform. Similar results were collected in previous edition of the survey.


Number of Users

C. About the Cloud Architecture

56% of OpenNebula deployments have more than 10 nodes, and 10% of the deployments have more than 500 physical nodes. Similar results were collected in the previous edition of the survey.


Number of Nodes


51% of deployments are federated environments consisting of more than one OpenNebula zone, and 5% are running more than 10 zones.This means a slight increase, from 44%, in the number of federated environments compared to previous survey.


Number of Zones


KVM at 79% and vCenter at 37% are the most widely used virtualization platforms. Next one is Xen at 12%. VMware ESX drivers are used by only 4% of deployments, most of VMware users have migrated from ESX to vCenter drivers, which brings many benefits. The number of KVM users has grown considerably from 48% to 79% and the number of VMware users has grown from 28% to 37%, compared to previous survey in 2014 (vCenter support was introduced just after the previous survey). Other hypervisors include those not part of the main OpenNebula distribution that are supported through community plugins.


Hypervisor (people may select more one checkbox)


Shared file system at 60% and Ceph at 40% are the most widely used storage solutions in open environments. The use of Ceph has grown considerably from 17% in 2014. FS LVM, Block LVM and GlusterFS are used by 17%, 12% and 12% of organizations respectively. VMware FS at 40% is used in VMware-based deployments, mainly through vCenter.


Storage Configuration (people may select more one checkbox)


Most of deployments, 45%, use the Standard Linux Bridge for network configuration; 35% use 802.1Q; 33% use Open vSwitch; and 13% use VXLAN. VMware networking at 40% is used in VMware-based deployments, mainly through vCenter. These are similar to previous survey results.


Network Configuration (people may select more one checkbox)


Regarding authentication, most of organizations, 73%, use the built-in user/password system, while SSH and LDAP/AD, with 50% and 36% respectively, are the more popular external authentication systems. Similar results to previous edition of the survey.


Authentication Configuration (people may select more one checkbox)


CentOS at 44% and Ubuntu at 40% are the most widely used linux distributions for building OpenNebula clouds. CentOS slightly falls from 46% and Ubuntu grows from 36%. Debian decreases from 33% to 22% of the deployments.


Operating System (people may select more one checkbox)


Among the advanced features offered by OpenNebula, High Availability, with 73%, is the most widely used. DC federation and Flow multi-VM are the next features with 55% and 45% respectively. The use of the EC2 cloud API drops from 25% to 10%.


Advanced Components (people may select more one checkbox)


In this survey edition we added a new question about the use of hybrid cloud drivers. 44% of deployments use the hybrid cloud functionality offered by OpenNebula. Amazon EC2 at 30% and Microsoft Azure at 16% are the most widely used public clouds.


Hybrid Cloud (people may select more one checkbox)

D. Why OpenNebula

One more year, simplicity, flexibility, and openness continue being the main reasons for choosing OpenNebula.


Why OpenNebula (people may select more than one checkbox)

In Cloud Management Platforms users typically deploy their VMs out of pre-defined templates that can specify a fixed amount of memory. Users may be able to customize the size of their VMs but they tend to overestimate the memory required for their applications. As an example, three 4 GB VMs with applications actually using 1 GB of RAM fit in a 12 GB node, but there is no more room left for additional VMs. Adjusting their memory to 1 GB VMs enables to deploy additional VMs on that node, as shown in the next figure.


CloudVAMP is an open-source development that manages these situations for all the nodes in an OpenNebula Cloud deployment based on the KVM hypervisor. CloudVAMP monitors the memory usage of Virtual Machines (VMs) and dynamically changes the memory allocated to VMs by stealing the unused free memory from VMs. Then CloudVAMP enables OpenNebula to use that stolen memory, thus being able to increase the VM-per-node ratio. To prevent memory overload in the physical hosts, live migration is applied in order to accommodate the increasing memory demand by VMs across the OpenNebula Cloud.

Some Technical Details

CloudVAMP consists of three components:

  • Cloud Vertical Elasticity Manager (CVEM). An agent that analyzes the amount of memory actually needed by the VMs and dynamically updates the memory allocated to each of them, according to a set of customizable rules.
  • The Memory Reporter (MR). An agent that runs in the VMs and reports to the OpenNebula monitoring system the free, used memory and usage of the swap space, by the applications in the VM.
  • The Memory Oversubscription Granter (MOG). A system that informs OpenNebula about the amount of memory that can be oversubscribed from the hosts, to be taken into account by the OpenNebula scheduler.

CloudVAMP integrates with OpenNebula in several ways. The MR can be staged in the VMs using the contextualization mechanisms provided by OpenNebula or it can be pre-installed in the Virtual Machine Images. It contacts OneGate to report the memory usage in the VMs. The CVEM is installed as a daemon in the front-end node of the OpenNebula Cloud. Finally, the MOG is implemented as a new Information Manager in OpenNebula. The interaction with KVM is performed by means of LibVirt. Therefore, no modifications in the OpenNebula worker nodes are required. The interaction with the components is shown in the following figure:


Benefits of Using CloudVAMP

Deploying CloudVAMP in an OpenNebula Cloud enables to seamlessly allow OpenNebula to deploy more VMs per physical host, thus achieving increased server density. The memory usage of VMs is monitored in order to satisfy increased memory demands by the applications running in the VMs. The usage of live migration to redistribute the VMs without downtime is employed if necessary, without any user or sysadmin intervention. This enables an increased usage of the hardware platform that supports an OpenNebula Cloud.

In particular, at the GRyCAP research group we have integrated CloudVAMP in order to accommodate a larger number of incoming jobs from the ES-NGI (the Spanish National Grid Initiative) that are executed on a virtual elastic cluster deployed and managed by EC3 (Elastic Cloud Computing Cluster). The virtual cluster, deployed on top of our OpenNebula Cloud, is horizontally scaled whenever incoming jobs are received (i.e., deploying additional Worker Nodes (WNs)) and vertically scaled (i.e., adjusting the allocated memory to the VMs) in order to let OpenNebula deploy additional WNs in the same host, if necessary. Further details of this case study are available in CloudVAMP’s reference publication.


CloudVAMP has been developed by the GRyCAP research group at the Universitat Politècnica de València. It is available under the Apache 2.0 license at GitHub.

There is further information in CloudVAMP’s web page and in the corresponding publication:

Germán Moltó, Miguel Caballer, and Carlos de Alfonso. 2016. “Automatic Memory-Based Vertical Elasticity and Oversubscription on Cloud Platforms.” Future Generation Computer Systems 56: 1–10.

Contributions, feedback and issues are very much welcome.

ONEDock is a set of extensions for OpenNebula to use Docker containers as first-class entities, just as if they were lightweight Virtual Machines (VM). For that, Docker is configured to act as an hypervisor so that it behaves just as KVM or other hypervisors do in the context of OpenNebula.

The underlying idea is that when OpenNebula is asked for a VM, a Docker container will be deployed instead. In the context of OpenNebula, it is managed as if it was a VM, and the user will be able to use IP addresses to access to the container.

Docker Machine and similar projects deploy VMs in different Cloud Management Plattforms (e.g. OpenNebula, OpenStack) or commercial providers (like Amazon EC2), installing Docker on them. Afterwards, it is possible to deploy and manage Docker containers inside them, using the Docker client tools that communicate directly with the Docker services deployed inside the aforementioned VMs.

Instead, ONEDock takes a different approach by deploying Docker containers on top of bare-metal nodes, thus considering the containers as first-class citizens in OpenNebula. This allows to seamlessly integrate the benefits of Docker containers (quick deployment, limited overhead, availability of Docker images, etc.) in a Cloud Management Platform such as OpenNebula. On the other side, it provides new features for containers that are usually reserved for VMs (e.g. enhanced IP addressing, attachment of block devices, etc.).

ONEDock tries to adapt Docker semantics to the OpenNebula context. The workflow for a whole use-case is the following:

  1. An image is registered in a datastore of type ‘onedock’, by using the oneimage command.
  2. ONEDock will download the image from Docker Hub.
  3. A VM that uses an image registered in the ‘onedock’ datastore is requested.
  4. When the VM is scheduled, ONEDock will actually create a Docker container instead of the VM, and the container will be daemonized (e.g. kept alive).
  5. If the container has been connected to a network, it is possible to be accessed (e.g. using ssh or http).

The most prominent feature of ONEDock is that it does not introduce any API changes, therefore it does not modify the way of interacting with OpenNebula: It is possible to use the ONE CLI (i.e. oneimage, onevm, onetemplate), OpenNebula Sunstone, XML-RPC, etc. and keep the usual lifecycle for the VMs.

Technical details

ONEDock provides 4 components that need to be integrated into the OpenNebula deployment:

  • ONEDock Datastore, that enables to create a datastore that contains Docker images. It is self-managed in the sense that images are created as references that are automatically downloaded from Docker Hub.
  • ONEDock Transfer Manager, that stages the docker images that are in a Docker datastore into the virtualization hosts.
  • ONEDock Monitoring Driver, that monitors the virtualization hosts in the context of the Docker hypervisor.
  • ONEDock Virtual Machine Manager, that carries out the tasks related to the lifecycle of the Docker containers as if they were VMs.

These components have to be installed in the proper folders of a ONE frontend (i.e. /var/lib/remotes/) and activated in the oned.conf file. Therefore, no source code modifications of OpenNebula are required.

Once this has been done, it is possible to create datastores of type ‘onedock’ and virtualization hosts that use ‘onedock’ as the virtual machine manager.

The ONEDock datastore

In order to deploy a Docker container, a Docker image is required. When you run a container, Docker automatically retrieves the image from the Docker Hub repository.

To avoid that all virtualization hosts access Docker Hub, and as kind of cache, ONEDock supports a private registry installed in the OpenNebula front-end. Then, the references to the Docker images will point to the private Docker registry. ONEDock supports Docker registry v2.0.

The network in ONEDock

Docker containers are conceived to run applications, and so, it is common to find that ports are redirected to public ports in the machine that hosts the Docker container. ONEDock enhances this behaviour in order to expose all the ports of the container as it would happen in a VM. Therefore, you can run different services in different ports without the need of exposing them explicitly. The container will have an IP address where all the ports are available.

Testing ONEDock

ONEDock can be evaluated in a sandbox before deploying it in your on-premises Cloud. Easy as 1, 2, 3:

  1. Install Vagrant
  2. Spin up the vagrant VM, which will be automatically configured with ONE, ONEDock, the docker registry and all the needed components.
  3. Start creating Docker containers with the common ONE commands (i.e. onevm create, etc.)


  1. Install LXC
  2. Create a testing container (using a self contained cli-utility that installs ONE, ONEDock, the docker registry and all the needed components).
  3. Start using ONE by issuing the common ONE commands (i.e. onevm create, etc.)

Getting ONEDock

ONEDock has been developed in the framework of the INDIGO-DataCloud ( project under the Apache 2.0 license. You can get it from the public repository

ONEDock is accepting contributions. You are invited to interact with us in the GitHub repository, by asking questions or opening new issues.