Alongside the OpenNebula 5.8 Beta 2 release, we are also publishing the 5.7.80 beta contextualization packages for the guest operating systems running in the virtual machines. Follow the download pages with the detailed release notes for Linux (and FreeBSD) and Windows. Packages are compatible with OpenNebula versions between 4.6 and 5.8 Beta 2.

You should use these packages if you want to try the very new features of OpenNebula 5.8 Beta. Namely, the LXD hypervisor or multiple managed IP addresses on a single vNIC. Naturally, there are also small fixes and improvements for the users of current stable OpenNebula versions.

With this beta version, we are excited to announce initial support for the FreeBSD guests! It’s now possible to run the FreeBSD virtual machines in the OpenNebula cloud and configure the network, SSH keys, user password, run custom start scripts, or report back via OneGate based on the provided contextualization parameters – most of the things you are used to from the supported Linux distributions. Moreover, we tried to reuse as much as possible from the current Linux contextualization code base. FreeBSD specific contextualization scripts are limited only to the network configuration. The rest of the scripts were adapted to play nicely in both worlds.

For a quick start, we are providing beta KVM images on our Marketplace for FreeBSD 11.2 and FreeBSD 12.0 with preinstalled beta contextualization packages. You can easily import these appliances into your OpenNebula and give it a try.

Please open a GitHub issue to report your bugs or feature requests!

 

ONE Service Appliances in the Marketplace

A short time ago we made a quick introduction to one of our recent efforts in OpenNebula – ONE service appliances. In particular, the CMS platform WordPress. It was just a short announcement in the forum to let you know that we started to expand the OpenNebula’s Marketplace. If you missed this news, you can take a quick look here: Release of WordPress 5.0 appliance

This new endeavor is not just about a preinstalled software package where every new installation/instantiation requires configuration – either by hand or via ansible/saltstack/chef/puppet or another automation tool of your choice. That would be too easy (for us) and not of much use for you. Eventually you may do some reconfiguration anyway to meet your needs, but we tried to make the appliance deployment as automated and straightforward for you as possible. For example, some appliances support username, password and email (where it makes sense) as a contextualization – you can deploy multiple of these appliances at once and each with its own credentials. But we don’t stop there. Even if you decide to not provide any contextualization at all, the appliance will still not have any passwords or sensitive security information baked inside the image. Every time you instantiate a ONE service appliance, it will first configure itself and generate a new set of credentials, tokens and similar, as needed.

For more general information about ONE service appliances, visit the documentation.

The aforementioned announcement serves as a sneak peak and we promised to give you more info about it and more appliances to play with. Let us first take a deeper look at the WordPress appliance. After that we will cover another new appliance – GitLab, the popular CI/CD platform for developers!

WordPress – Let’s write some blog!

We will now create yet another blog. All the necessary steps are in the documentation so you just need to follow the Quick Start first, but don’t leave the contextualization parameters empty. Instead, fill up the bootstrapping variables and save your time by avoiding the need to go through the setup wizard.

Bootstrapped WordPress:

Running WordPress

 

GitLab – It’s time to develop!

GitLab is definitively one of the most popular CI/CD tools these days and we are happy to include it in our marketplace. Again, all the necessary steps are described in the documentation – follow the Quick Start and before you instantiate, fill up the bootstrapping variables. If you fail to do so, GitLab will greet you with the prompt for password setup.

Bootstrapped GitLab:

GitLab login screen

 

This concludes our introduction to the first batch of ONE service appliances. Stay tuned for the next addition!

Do you have a tip for some other great service? Let us know what you think in the comment section!

As part of OpenNebula v.5.8 “Edge”, we have designed a new method for self-provisioning virtual networks. OpenNebula already has two ways for creating virtual networks:

  • Just create it from scratch.
  • Reserve a slice of an existing virtual network.

Typically the virtual networks are created by the cloud administrators and the end user just makes reservations from those virtual networks. However, this method does not allow the end user to make changes at a logic level like changes to IP ranges, the DNS server, etc.

Now, with the new virtual network template, an end user will be able to do just that. The cloud administrator will be able to create a virtual network template with all the required physical attributes, like the driver (VN_MAD), the bridge, the VLAN_ID (it can be set to be automatically generated), etc. and can still use the restricted attributes to manage the end users’ control. Yet in the end, the end user will be able to create a virtual network by means of the template.

For example, the administrator could create a virtual network like this:

cat template.txt
  NAME="vn_template"
  VN_MAD=bridge
  BRIDGE=virbr0
  AUTOMATIC_VLAN_ID=yes
$ onevntemplate create template.txt
  ID: 3
$ onevntemplate show 3
   TEMPLATE 3 INFORMATION
   ID             : 3
   NAME           : vn_template
   USER           : oneadmin
   GROUP          : oneadmin
   LOCK           : None
   REGISTER TIME  : 11/29 14:12:01

   PERMISSIONS                                                 
   OWNER          : um-
   GROUP          : ---
   OTHER          : ---

   TEMPLATE CONTENTS
   AUTOMATIC_VLAN_ID="yes"
   BRIDGE="virbr0"
   VN_MAD="bridge"

And make it available for all end users:

$ onevntemplate chmod 3 604
$ onevntemplate show 3
   …
   PERMISSIONS                                                        
   OWNER          : um-
   GROUP          : ---
   OTHER          : u--
   …

Once the virtual network template is created and ready to use, the end user will be able to create customized virtual networks.

During the instantiation the user can create a new address range:

You can go to the “Virtual Networks” section and check that the virtual network is already there:

 

Test out this new feature – it’s available now in our v.5.8 beta version – and let us know if you have any suggestions!

We are very excited to announce that the eighth edition of our OpenNebula Conference will be held in Barcelona, Spain on October 21-22, 2019.

Plan ahead, and make some space on your calendars, as Barcelona is beautiful in October, and our OpenNebulaConf is an annual event worth attending. This is an entirely educational and networking event, with the focus of sharing keen insight on OpenNebula and the evolving technology landscape, creating conversation around innovations and user experiences, and providing a platform for valuable knowledge sharing! It also includes Hands-on training sessions!

Join us in Barcelona for a great event!  Whether you are exploring the market for a private cloud solution, or you are already an avid user of OpenNebula, this conference offers plenty for you.

And if you’d like the opportunity for your organization to connect with our active User Community – help us sponsor the event!! Check out the details.

We hope to see you in Barcelona!

Version 5.8 will bring cloud capabilities to the Edge

As you will have seen in our recent post, we have released a beta version of the upcoming “v.5.8 Edge”, where in addition to extending and enhancing some of the recent functionalities of “v.5.6 Blue Flash”, we are bringing to the market a collection of new capabilities that are focused on extending cloud computing to the Edge.  The ever-growing discussion around “connected data” and “IoT” is transforming the computing and infrastructure needs of organisations. The conversation is shifting away from centralised cloud infrastructure, and refocusing toward bringing the computing power closer to the users, with a concerted effort to reduce latency. The Clouds are quickly drifting to the Edge.

Historically, with OpenNebula, we have continued to remain at the forefront of cloud computing offerings, with a close eye on the needs of the User Community, while evolving along with the rapidly developing technology.  Now with v.5.8, OpenNebula will be taking a huge step toward moving to the forefront, and bringing remarkable value that will stand out from the rest.

As referenced earlier in our beta-release announcement, v.5.8 Edge will be “something to behold”!  Allow me to remind you why:

  • You will see complete, native support for LXD containers – allowing for the same capabilities as running on VM’s, but without the overhead that comes with running a separate kernel and simulating all the hardware.  You now have more options for your infrastructure.
  • Without having to change the nature of your workload, you will be able to quickly expand your cloud and build remote clusters using bare metal providers.  This feature is key in being able to build Distributed Data Centers along the edge of your expanding cloud.
  • As you build your edge environments, where hosts may be diverse, with different network configurations, the OpenNebula Scheduler will now allow for Automatic NIC selection.
  • v.5.8 Edge will offer broad Scalability Improvements – across pool management, monitoring, and the GUI – to ensure that orchestrating your edge cloud remains simple and effective.

Keep an eye out for updates surrounding the v.5.8 release, as well as, upcoming posts delving into more detail about some of its new capabilities.  And we urge you to get your hands on the beta-version to kick the tires! Let us know what you think!

 

OpenNebula v.5.8 is close…

We are launching a “Call for Translations” as we prepare the release of OpenNebula v.5.8.  Any help that you can provide in helping to translate for our Sunstone GUI would be of enormous value – and it is very easy to do!

You can translate “one string at a time”.

Existing translations can be updated and new translations submitted through our project site at Transifex:

https://www.transifex.com/opennebula/one/

The “Call for Translations” will end on January 28, 2019.  And translated languages reaching a good level of completion will be included in the official v.5.8 release.

We appreciate your collaboration!!

Closing out 2018…and welcoming in 2019!!

2018 has been another exciting year for OpenNebula. It has brought continued developments and advancements in the OpenNebula product capabilities. At the same time, we’ve seen a fervor and a steady commitment by the User Community which continues to bring unmatched value. At OpenNebula Systems, we have our sights set on continued improvement for 2019, and we are excited about several promising, emerging developments. But again, one of the key dynamics of the project is that we wouldn’t be able to grow without you.

For that reason, one of the recent developments in the community has been our request for your participation in our 2018 User Survey.  This is a simple vehicle to allow us to learn about the use cases, platforms, and overarching technical needs of the OpenNebula User Community.  We look to remain in synch with your needs, and to develop alongside with you. Fill it out, and share your thoughts!

Speaking of developments…

Among the various version releases this year, we released version 5.6 “Blue Flash” with a huge set of improvements both at the core level, as well as for vCenter integration. And from there, we have jumped right into focused development on the upcoming version 5.8.  In it, we have been working on many different features – a long-awaited support for LXD containers, being one of them.

2018 has seen a certain dedicated focus on the emerging developments surrounding Edge Computing, and while we have been working closely with customers and partners, learning the details of evolving use cases, we have also made developments around integrations with OpenNebula along “the edge”.  Earlier this year, we released an initial prototype of “oneProvision”, allowing users to provision and deploy bare-metal resources directly within an OpenNebula cluster.  Upcoming development of oneProvision will include being able to deploy not only one host, but a cluster of hosts.  At the same time, we partnered with Packet to demonstrate our continued focus in bringing capabilities to the edge.

Recent releases of new capabilities like miniONE and VirtualNetwork Scheduler, and the Image Converter to/from VMDK and QCOW2 all demonstrate our driven effort to making OpenNebula the easiest-to-use platform out there.

The “Calendar of Events”

In 2018, we held several OpenNebula TechDay events throughout Europe – in Sofia hosted by StorPool, in Barcelona hosted by CSUC, and in Frankfurt hosted by LINBIT – and in the US – in Santa Clara, CA hosted by Hitachi Vantara and in Cambridge, MA hosted by OpenNebula Systems.  We also held our OpenNebulaConf in Amsterdam.  We thank our sponsors and hosts for collaborating to put these events together.

Events schedule in 2019

The lineup for OpenNebula TechDays for this coming year will tentatively be in the following locations, with dates and details to be determined:

  • Frankfurt
  • Barcelona
  • Vienna
  • Sofia
  • Boston

And plan to attend our 2019 OpenNebulaConf in Barcelona on October 21-22, 2019.

Great support from the Community

Lastly, as we continuously try to make clear, the OpenNebula project would not have the vitality nor the reach it has if it weren’t for our dedicated User Community.  We’ve seen a continued growth of OpenNebula Champions.  Throughout the year, users have taken the time to publish tutorials like these from Pandora FMSVirtuozzo 7, and CSUC.  Our OpenNebula Blog has been used by many from the Community to publish share insight and experiences. This year, we also created our Partner Ecosystem, another instrument to show and share integrations between ONE and other great technologies.

This has been an exciting year for OpenNebula! We give you our utmost thanks, and we look forward to our collaboration going into 2019!!

Stay Connected!

Our newsletter contains the highlights of the OpenNebula project and its Community throughout the month.

Technology

Several important items and functionalities have been worked on or released this month, which are definitely worth mentioning:

  • We released the powerful, yet simple tool called “miniONE“.  With miniOne, you can now stand up a complete OpenNebula environment on a single host with just one command.  And it takes no longer than a few minutes.  Check out the detailed miniONE blog post.
  • We have released a new appliance onto the OpenNebula Marketplace with a pre-installed WordPress 5.0 service.  Take a look at the quick walk-through on the forum post and check it out!
  • We have been firmly focused on our testing and validation of the LXD container support, along with vCenter driver updates, and we are getting very close to releasing a beta version for OpenNebula 5.8.  Keep your eyes peeled!

Community

As the holiday season approaches, and we coast into the new year, we give a big thanks to the User Community for your continued support and enthusiasm in pushing OpenNebula forward, and for sharing your experiences and insight.

Outreach

And as we look toward the new year, we have been working fervently on the OpenNebula plan for 2019:

  • We sent out our 2018 User Survey with the hopes of getting useful insight into your needs and suggested areas of focus. Your feedback is extremely valuable, so we urge you to fill it out, if you haven’t already.  (It takes 5 minutes, max).
  • We will soon be wrapping up our OpenNebula TechDay schedule for 2019. We sent out a Call for Hosts, and are working on finalizing our schedule.  There’s still time to submit your request to host a TechDay of your own.

We wish you all a wonderful holiday season, and look forward to ringing in the new year together!

Best wishes, and Stay Connected!

This post is about a simple tool called miniONE, which allows you to easily install OpenNebula on a single host from the freshly deployed system to the ready-to-use OpenNebula installation just by a single command.

Let’s say that you just want to check out how OpenNebula looks like when starting evaluation or you want to see if something particular is done in v5.6. This might be the case when you can use miniONE.

So, just get it:

$ wget https://github.com/OpenNebula/minione/raw/v5.6.0/minione

and run it:

$ sudo bash minione

At first, there needs to be some checks done. You can see all of them by running with –verbose.

$ sudo bash minione --verbose

### Checks & detection
Checking distribution and version [CentOS 7] OK
Checking cpu virtualization capabilities OK
Check free disk space OK
Using local interface [ens3] OK
Checking directories from previous installation OK
Checking user from previous installation OK
Checking sshd service is running OK
Checking bridge-utils are installed SKIP will try to install
Checking minionebr interface is not present OK
Check given VN 172.16.100.0/24 is not routed OK
Checking SELinux OK
Checking for present ssh key SKIP
Generating ssh keypair in /root/.ssh/id_rsa OK
Checking presence of the market app: "CentOS 7 - KVM" OK

Mainly you need to run it on a supported system — Centos 7 and recently Ubuntus so far. Then, you need CPU capable to perform virtualization, some free space to allocate the images and virtual machines itself, etc.

It may happen that you hit some non critical check to fail

### Checks & detection
Checking directories from previous installation FAILED

But you might try to force it using -f.

$ sudo bash minione -f

### Checks & detection
Checking directories from previous installation IGNORED will be deleted

Once you get through that, you may start the installation.

### Main deployment steps:
Purge previous installation
Configure bridge minionebr with IP 172.16.100.1/24
Enable NAT over ens3
Using ssh public key /root/.ssh/id_rsa.pub
Install OpenNebula version 5.6

Do you agree? [yes/no]:

### Installation
Install bridge-utils OK
Creating bridge interface minionebr OK
Restarting network OK
Enabling ipv4 forward OK
Configuring nat using iptables OK
Saving iptables changes OK
Installing DNSMasq OK
Starting DNSMasq OK
Configuring repositories OK
Installing epel OK
Installing OpenNebula packages OK
Installing ruby gems OK
Installing OpenNebula node packages OK

### Configuration
Switching onegate endpoint in oned.conf OK
Switching scheduler interval to 10sec OK
Setting initial password for current user and oneadmin OK
Starting opennebula services OK
Checking OpenNebula is working OK
Disabling ssh from virtual network OK
Adding localhost ssh key to known_hosts OK
Testing ssh connection to localhost OK
Add ssh key to oneadmin user OK
Updating datastores, TM_MAD=qcow2, SHARED=yes OK
Creating host OK
Creating virtual network OK
Exporting [CentOS 7 – KVM] from marketplace to local datastore OK
Updating template OK

What is happening? Apart from the installation itself, which simply adds the repositories and installs the OpenNebula packages, some configuration changes must be done. Above all, the networking needs be prepared to somehow allow you to connect to the virtual machines later.

For that purpose the bridge interface is created with dedicated network segment and NAT is configured on the installing host. Also, DNS server (DNSMasq) is started for the virtual machines.

miniONE comes with default parameter values for most cases. See them all in the Help:

$ bash minione --help
-h --help                           List of supported arguments
--version [5.6]                     Specify OpenNebula version
-f --force                          Skip non-fatal validation errors
                                    (e.g., traces of existing inst.)
-v --verbose                        Be verbose
--yes                               Don't ask
--password [random generated]       Initial password for oneadmin
--ssh-pubkey [~/.ssh/id_rsa.pub]    User ssh public key
--bridge-interface [minionebr]      Bridge interface for private networking
--nat-interface [first net device]  Interface to configure for NAT
--vnet-address [172.16.100.0]       Virtual Network address
--vnet-netmask [255.255.255.0]      Virtual Network netmask
--vnet-gateway [172.16.100.1]       Virtual Network gateway (i.e. bridge IP)
--vnet-ar-ip-start [172.16.100.1]   Virtual Network AR start IP
--vnet-ar-ip-count [100]            Virtual Network AR size
--marketapp-name [CentOS 7 - KVM]   Name of Marketplace appliance to import
--vm-password [opennebula]          Root password for virtual machine 

Before the installation finishes, it also bootstraps the OpenNebula to be ready to use. At first it enables KVM hypervisor on localhost and downloads one appliance from the market place. So, once that is complete, you may easily login using the printed credentials:

### Report
OpenNebula 5.6 was installed
Sunstone (the webui) is runninng on:
  http://192.168.100.101:9869/
Use following to login:
  user: oneadmin
  password: o6ARsMAdGe

And that’s it! It won’t take us to Mars, but it might be handy, nonetheless.

It’s been a few weeks now since the 2018 OpenNebula Conference in Amsterdam.  It was great to see so many members of the User Community, enthusiastic to learn and share insights around OpenNebula and the current technology landscape.  We give a huge thanks to the great lineup of speakers who presented, as well as to the sponsoring organizations that helped to make the conference a success!

Here are the materials from the conference, available for you to review at your leisure:

Take some time to review the material, think about how it may help with your environment or your proposed solution, and reach back out to the community if you have questions or suggestions. We’d love your feedback!

Additionally, you will have seen our recent 2019 OpenNebula TechDay “Call for Hosts”.
Think about hosting one of your own!

Stay connected!