Upcoming Cloud TechDays in Chicago, Boston and Paris

Besides our annual OpenNebula Conference, we are organizing Cloud Technology Day events in multiple cities globally in the next two months.

The OpenNebula TechDays are full day events to learn about OpenNebula with a hands-on cloud installation and operation workshop, and presentations from community members and users that will focus on:

  • Sharing cloud use cases and deployment experiences
  • Introducing new integrations and ecosystem developments
  • Describing other related cloud open-source projects and tools

The first OpenNebula Cloud Tech Day will be held on the 24th of June in Chicago, IL, at the Illinois Institute of Technology and with the collaboration of FermiLab.

IIT_Logo_stack_186_blkfermilab

 

The second OpenNebula Cloud Tech Day will be held on the 29th of June in Cambridge, MA, at the Microsoft New England R&D Center, organized by the HPC & GPU Supercomputing Group of Boston and sponsored by Microway.

microsoft_logo

microway_logo

 

The third OpenNebula Cloud Tech Day will be held on the 8th of July in Paris, France, organized by IPPON Hosting.

logo_ippon_hosting_HD

 

If you want to actively participate in any of these events, share your experience with OpenNebula or describe other related cloud open-source projects and tools, send us your talk proposal at events@opennebula.org.

The number of seats is limited to ensure there is plenty of opportunity for everyone to interact. We encourage everyone to register as early as possible.

For more information on past events, please visit the Cloud Technology Days page

We hope to see you there! and a big thanks to the organizers of these events.

Please send us an email at events@opennebula.org if you are interested in hosting a TechDays event.

We look forward to your answers

ungleich to Sponsor OpenNebulaConf 2015

The third ever OpenNebula International Conference is getting closer and we are proud to announce the first Gold Sponsor for the event, ungleich GmbH.

ungleich_logo_opennebula_-

ungleich, meaning not equal (≠) in German, is the number one Linux infrastructure company in Switzerland, specializing in design, implementation and maintenance of Linux infrastructures. The highly skilled, multidiscipline team at ungleich provide the services of a local System-Administrator, but more efficiently and with higher availability.

OpenNebula is used by ungleich to provide high availability (HA) hosting in Germany and Switzerland. The ungleich HA hosting uses a variety of Open Source Software like Django, cdist or GlusterFS ; OpenNebula plays a central role for offering hosting.
As you may already know OpenNebula Conf will be held in Barcelona from the 20th to the 22nd of October 2015. Visit the ungleich booth to learn how OpenNebula is used in hosting and in customers projects. Find out how small to large scale hosting infrastructures are configured with the configuration management system “cdist”, the Swiss made Configuration management system.

If you want to participate in OpenNebula Conf and meet ungleich 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 2015 there are still slots.

promo_banner

OpenNebula Has a New Base in the U.S.

We are pleased to announce that OpenNebula Systems, the company behind the OpenNebula Project and vOneCloud, has established a new subsidiary to oversee all business operations and to support the OpenNebula community in the U.S. The new subsidiary in Cambridge Mass. will serve as a training, consulting and support facility for the quickly growing number of OpenNebula and vOneCloud users in the area.

This is great news for our open-source Project because this new company will help support the community, spread its word, and strengthen its user base in the U.S. We are organizing Cloud Technology Day events in Boston and Chicago at the end of June.

Contact us if you would like to help us organize a Cloud TechDay.

More details in the Today’s Press Release by OpenNebula Systems.

Unity Builds its Federated Cloud with OpenNebula

Unity Technologies is shaping a booming global games market. The Unity engine is far and away the dominant global game development software. More games are made with Unity than with any other game technology! And guess what? Unity uses OpenNebula to run their IaaS infrastructure to support their development services, among other things.

Unity Technologies contacted OpenNebula Systems, the company behind OpenNebula, due to its expert knowledge of OpenNebula, to jointly design and deploy Unity cloud infrastructure, dubbed uCloud. OpenNebula Systems offers this service through the Jumpstart packages, on their Basic and Advanced modalities, based on the different Open Cloud Reference Architecture corresponding types.

The basic principle that Unity applies to their infrastructure is the KISS approach, which is very much aligned with the OpenNebula design principle.

The Requirements

Unity Technologies offers its services globally, and as such required to deploy a cloud across three different data centers to serve EMEA, US and ASIA Unity users. The data centers were to be based on SoftLayer bare metal servers, and the users of the Cloud were expected to be able to access resources across these different data centers.

Regarding networking, a certain degree of federation was expected, particularly the ability to interconnect virtual machines from different data centers in different virtual networks. Unity Technologies suggested the use of network gateways to manage this interconnections, so the challenge was to integrate them in the OpenNebula workflow.

Other requirements were the use of Active Directory to authenticate users, and also to have a complete isolation between groups of users (that is, the workloads of one group of users should not affect the others), as well as hybrid access to public cloud providers, in particular SoftLayer and Amazon EC2, to be able to cloud burst Virtual Machine to them in case the allocated bare metal in SoftLayer cannot cope with the fluctuating demands.

The Design

OpenNebula Systems and Unity got to work right away, to deliver the best possible OpenNebula cloud design taking into account the requirements. Take a look at the picture to get a glimpse of the final design of uCloud.

unity

The use of Ceph was a no brainer, Unity used Ceph internally and OpenNebula Systems agreed right away since this cloud is expected to grow to a medium to large scale. This is aligned with the OpenNebula Advanced Reference Architecture, intended for clouds of this magnitude. Also, Ubuntu was preferred by Unity sysadmins, and given OpenNebula full support for it; the decision was arrived to easily enough as well.

Using OpenNebula federation capabilities solved right away the need to federate at the authentication level the different datacenters. The SoftLayer dedicated link low latency allowed the several instances of OpenNebula (one per data center) to communicate quickly enough to keep them synchronized and provide a top-notch user experience.

The need of serving different groups of people, with different needs in terms of physical and virtual resources, was also solved using the powerful OpenNebula provisioning model, by assigning physical resources to Virtual Data Centers, and providing access to them via Groups of users, to which virtual resources can be assigned.

Networking was trickier. The limitations of using only traffic encapsulated within VLANs imposed the use of VXLAN, which OpenNebula fully supports. Special integrations were made into OpenNebula to operate the Gateways as soon as a new virtual network is created; so new routes are created dynamically enabling the interconnection of different data centers virtual networks on demand. The OpenNebula flexible architecture proved that it is a great asset to solve complex designs.

Cgroups was the technology picked up for workload isolation, so VMs from one groups of users cannot eat up all the CPU resources if they are needed by another VMs. For memory, not allowing for over commitment was the decision.

The Result

uCloud is a state of the art cloud, with authentication and network federation, prepared to scale to support thousands and even millions of users as Unity Technology requires. Unity Technologies can arguably be given the credit of making the right call, contacting OpenNebula Systems, the creators of the technology, to push it to its limits to create a cloud infrastructure ahead of its time.

“We engaged OpenNebula Systems to verify our design thoughts and to speed up the deployment phase of our uCloud project.”, said Karsten Nielsen, IT Manager at Unity Technologies. “OpenNebula Systems is very professional and executed within the tight death-line the project was under. I am very pleased with the process and the result of the project.”


Karsten Nielsen will give a keynote about the uCloud infrastructure and OpenNebula at OpenNebulaConf2015 (Barcelona, October 20-22 2015). Register asap and save with very early Bird discount!.

Create a context ready VyOS Image for OpenNebula

Today I’m writing about the steps I’ve followed when creating a KVM VyOS image for OpenNebula that accepts some contextualization variables.

I hope this post helps users to extend the contextualization support and create your own VyOS appliances and share them in the marketplace, e.g why don’t you try to follow these steps to create an image for Xen and VMWare?

The first part of the post will help you to create a KVM image using Sunstone, the second part explains how we can add contextualization to our VyOS image.

Let’s begin!


First part – Creating a VyOS KVM image

This is easy for most of the users, however I think it’s always good to show these steps to newcomers. These are only my recommendations, they’re not mandatory, I’m just letting you know what works for me.

  1. First, download the latest stable image for virtual 64 bits (or 32 bits) from VyOS adding the ISO as a virtio CDROM image (vd prefix).
  2. Let’s create a 2GB Hard Disk image. I use a persistent, empty, datablock to create a VirtIO HDD. Once the HDD is created, remember to change the TYPE from DATABLOCK to OS.VyOS_HDD
  3. Once we have an ISO image and a HDD it’s time to create a template. In my case I add a network interface so I can later configure VyOS using SSH. Using the wizard these are the most important parts I configure:
    • General -> Memory. We’ll need at least 256 MB RAM (512 MB recommended).
    • General -> Hypervisor. KVM in my example :-D
    • Graphics -> VNC.
    • Network. When creating a NIC I use the advanced options and select virtio for the NIC Model.
    • OS Booting. Arch -> x86_64
    • OS Booting 1st Boot -> CDROM. It’s quite important to ensure the VM will boot the CD first unless you want a “AMD64 – No bootable device error” error.
    • OS Booting 2nd Boot -> HD
  4. After our template is ready let’s instantiate it!. If everything works fine we’ll have access to the console using VNC.VyOS_VNC
  5. Vyos default username and password are both vyos. Once we’re in, we can install VyOS in our HDD image using the following command:
    install image
  6. The installation wizard will ask some questions:
    • VyOS image to a local hard drive. Would you like to continue? (Yes/No) [Yes]:
    • Partition (Auto/Parted/Skip) [Auto]:
      I found the following drivers on your system:
      vda 2097MB
      vdb 247MB
      Install the image on? [vda]:
    • This will destroy all data on /dev/vda.

      Continue? (Yes/No) [No]: Yes

    • How big of a root partition should I create? (1000MB – 2097MB) [2097]MB:

      Creating filesystem on /dev/vda1: OK

    • What would you like to name this image? [1.1.5]
    • I found the following configuration files:…
      Which one should I copy to vda? [/config/config.boot]:
    • Enter password for user ‘vyos':
    • Which drive should GRUB modify the boot partition on? [vda]:
  7. Once the system is installed we can run the poweroff command:
    poweroff
  8. The HDD is ready so we only have to update our template removing the CDROM and selecting HD as the 1st Boot device in the OS Booting tab. Then we can instantiate the VyOS template again.
  9. In the second part I’ll use SSH to run some commands so I first enable a NIC and start the SSH service using the following VyOS commands. In my example I’m using the 192.168.4.11 IP address.
    config
    set interfaces ethernet eth0 address 192.168.4.11/24
    commit
    set service ssh
    commit
  10. Now we have a VyOS image with SSH and we’re ready to start with part two.

Second part – Adding the contextualization script

VyOS is a fork of the Vyatta Community Edition. Vyatta’s forum was full of useful information and it helped me to find answers to “where should I start to add contextualization?”. Unfortunately, when Brocade acquired Vyatta, the forum dissapeared, so I don’t know really who should receive credit for the info I gathered… I only can say thanks to Vyatta’s community and wishing the best for the new VyOS community.

All right. Let’s try to explain the magic.

If we add to VyOS a script called vyatta-postconfig-bootup.script, VyOS will run any command in that script, once VyOS is ready and the configuration has been loaded. In this script we try to mount the OpenNebula’s CDROM containing the context.sh script which will load the contextualization environment variables (please see the official OpenNebula’s documentation) to get a deeper understanding of contextualization. In any case, VyOS will launch the vyatta-vmcontext.sh bash script afterwards.

The vyatta-vmcontext.sh (it can be renamed, of course) uses the vyatta-cfg-cmd-wrapper command to encapsulate VyOS commands that will alter the configuration. The wrapper commands must be declared between a begin, a commit and, of course, an end. Using one of the OpenNebula’s contextualization scripts as a template, I’ve added VyOS command that will be executed if some context variables are ready (e.g the IP and MASK…). I think this script it’s quite easy to follow but don’t hesitate to send your doubts and feedback to add a FAQ to this post.

Hands on.

  1. We’ll need two bash scripts that I’ve uploaded to my Github account. You can clone the repo:
    git clone https://github.com/n40lab/vyos-onecontext.git
    cd vyos-onecontext
  2. Now we’ll scp the files to our VyOS VM using the vyos username and the vyos password (unless you’ve changed it during the installation). My VyOS router is listening on the 192.168.4.14 address.
    scp vyatta-vmcontext.sh vyos@192.168.4.14:/tmp/
    scp vyatta-postconfig-bootup.script vyos@192.168.4.14:/tmp/
  3. Using SSH and sudo we’ll move the scripts to the right directories:VyOS_SSH
    ssh vyos@192.168.4.14
    sudo mv /tmp/vyatta-postconfig-bootup.script /opt/vyatta/etc/config/scripts/vyatta-postconfig-bootup.script
    sudo mv /tmp/vyatta-vmcontext.sh /opt/vyatta/sbin/
  4. In order to use the contextualization, we must first remove SSH service and the ethernet address and any changes we’ve made to VyOS config:
    delete service ssh
    delete interfaces ethernet eth0
  5. We can edit the file /boot/grub/grub.cfg (sudo vi /boot/grub/grub.cfg) and delete the following lines:
    serial --unit=0 --speed=9600
    terminal_output --append serial
    echo -n Press ESC to enter the Grub menu...
    if sleep --verbose --interruptible 5 ; then
    terminal_input console serial
    fi
    
    menuentry "VyOS 1.1.5 linux (Serial console)" {
    linux /boot/1.1.5/vmlinuz boot=live quiet vyatta-union=/boot/1.1.5 console=tty0 console=ttyS0,9600
    initrd /boot/1.1.5/initrd.img
    }
    
    menuentry "VyOS 1.1.5 linux (USB console)" {
    linux /boot/1.1.5/vmlinuz boot=live quiet vyatta-union=/boot/1.1.5 console=tty0 console=ttyUSB0,9600
    initrd /boot/1.1.5/initrd.img
    }
    
    menuentry "Lost password change 1.1.5 (Serial console)" {
    linux /boot/1.1.5/vmlinuz boot=live quiet vyatta-union=/boot/1.1.5 selinux=0 console=tty0 console=ttyS0,9600 init=/opt/vyatta/sbin/standalone_root_pw_reset
    initrd /boot/1.1.5/initrd.img
    }
    
    menuentry "Lost password change 1.1.5 (USB console)" {
    linux /boot/1.1.5/vmlinuz boot=live quiet vyatta-union=/boot/1.1.5 selinux=0 console=tty0 console=ttyUSB0,9600 init=/opt/vyatta/sbin/standalone_root_pw_reset
    initrd /boot/1.1.5/initrd.img
    }

    Removing the console, will help us to avoid the following error-> INIT: Id “TO” respawing too fast: disabled for 5 minutes. Thanks to this post!

  6. Unless we’ve added a KVM serial port we can delete the console:
    delete system console
  7. Finally we can delete the bash history, commit and save the changes:
    > /home/vyos/.bash_history
    commit
    save
    exit
    reboot

Please remember: Once you reboot your image, the contextualization script will try to autoconfigure your VyOS router, however no changes are saved unless you explicitly use the save command. If you use the save command you should stop using the contextualization scripts to avoid clashes between your saved configuration and the one from context… so execute:

sudo cat /dev/null > /opt/vyatta/etc/config/scripts/vyatta-postconfig-bootup.script

Phew!. It’s been a long post and it’s hard to include all the information without boring you. I hope you have understood how you can use some scripts to add context to your own VyOS image. Soon I’ll post here some more information about VyOS but in the while you can start improving your VyOS images.

Cheers!

OpenNebula Newsletter – April 2015

This Newsletter contains the most worthy developments and events of the OpenNebula project and the community during this last month, and the plans for the upcoming months.

Technology

An important milestone was reached this month with the publication of the Open Cloud Reference Architecture for Basic and Advanced cloud deployments. This Reference Architecture has been created from the collective information and experiences from hundreds of users and cloud client engagements. Besides main logical components and interrelationships, the document describes software products, configurations, and requirements of infrastructure platforms recommended for a smooth OpenNebula installation.

A maintenance release for Cotton Candy,4.12.1, was released this month by the OpenNebula Team. This release comes with several bug fixes found after the 4.12 release. These bug fixes covers different OpenNebula components, like for instance the scheduler, the Cloud View self service portal, Sunstone web interface, OpenNebula Core and several drivers (VM, Auth, Network). Besides the bug fixes mentioned above, 4.12.1 includes several improvements, like the ability to have VNC capabilities imported from vCenter VMs, a logrotate script for OpenNebula logs and, specially, the scheduler has been revisited to cope with large XML files. Now OpenNebula instances are able to manage even more VMs!

Also April saw the release of a new stable version of vOneCloud, the open replacement of vCloud to cloudify vSphere infrastructures. vOneCloud 1.4 comes with outstanding new features for vCenter resource management, like for instance the inclusion of Showback capabilities. The VDC model has been revisited to enable resource sharing easily among different groups, as well as the interfaces, in order to smooth the workflow of importing vCenter resources. The main highlight though is the addition of multi-vm management capabilities, enabling the management of services, including the ability to set up elasticity rules to automatically increase or decrease the number of nodes composing a service. vOneCloud is zero intrusive, try it out with without the need to commit to it!

Community

Technical posts are definitely our sort of thing. And if they come as detailed and rounded as this amazing piece showing how to install OpenNebula on HA with Ceph and IPoIB in CentOS, the better. Check it out for a awesome script laying out all the steps needed to reproduce this setup. Another example is this excellent post about securing noVNC connections for Sunstone, with detailed explanation on how to create your own CA for VNC connections.

In depth analysis of the OpenNebula technology by third parties is a great way to promote OpenNebula, giving users leeway to choose among the IaaS technology that better fit their needs. This blog post by OlinData is a great example.

Our community is always giving back, and that is the spirit of open source. For instance, people sharing his work to make other people’s life easier, is a great example of the health of OpenNebula community. This new addon enabling the integration of OpenNebula and StorPool broads the integration capabilities of OpenNebula. Also important this example of a nodejs boilerplate to interact with OpenNebula. Thanks!

As you may know, OpenNebula is participating in the BEACON project, flagship European project in federated cloud networking. You can check the profile of OpenNebula Systems in the project blog.

We run on feedback. Seriously, it is never enough. If you are doing an OpenNebula deployment we want to hear from you! As they say, through thick and thin. Have you just installed a Windows 10 VM using OpenNebula?. We want to hear from you!

Outreach

The upcoming third edition of the OpenNebulaConf will be held in Barcelona this October 2015.You are still in time for getting a good price deal for tickets. Also, your company may be interested in the sponsorship opportunities for OpenNebulaConf 2015.

We have two Cloud Technology Days planned for US, in Chicago and Boston, for the end of June. We will publish the details in a few days. If there is anyone interested to host a TechDay in the east coast (in particular, we are looking for hosts in New York), drop us a line.

During the following months, members of the OpenNebula team will be speaking in the following events:

If you are interested in receiving OpenNebula training, check the schedule for 2015 public classes at OpenNebula Headquarters. Please contact us if your would like to request training near you.

Remember that you can see slides and resources from past events in our Events page. We have also created a Slideshare account where you can see the slides from some of our recent presentations.

OpenNebula Cloud TechDay, Boston, MA USA, June 29

The first OpenNebula Cloud Tech Day of the Northeast USA tour will be held in Cambridge, MA, at the Microsoft New England R&D Center, organized by the HPC & GPU Supercomputing Group of Boston and sponsored by Microway,

microsoft_logo

 

microway_logo

 

 

 

The event will start on the 29th of June at 9:00 with a hands-on cloud installation and operation workshop, and will continue with presentations from OpenNebula community members and users, and related open-source projects. The page of the TechDay contains all the details about the event.

If you want to actively participate in this event, share your experience with OpenNebula or describe other related cloud open-source projects and tools, send us your talk proposal at events@opennebula.org.

The number of seats is limited to ensure there is plenty of opportunity for everyone to interact. We encourage everyone to register as early as possible.

If you want to organize an OpenNebula TechDay in another city during our Northeast USA tour this is your chance! If you are interested or want to have more information please send an email to contact@opennebula.org.

We hope to see you there! and a big thanks to the HPC & GPU Supercomputing Group of Boston for making OpenNebula Tech Day possible.

OpenNebula – Securing Sunstone’s NoVNC connections with Secure Websocket and your own Certificate Authority

When dealing with NoVNC connections, I’ve faced some problems as a newbie, so today I’m sharing with you this post that may help you.

If you’re already using SSL to secure Sunstone’s access you could get an error when opening a VNC window: VNC Connection in progress”It’s quite possible that your browser is silently blocking the VNC connection using websockets. Reason? You’re using an https connection with Sunstone, but you’re trying to open an uncrypted websocket connection.

VNC_Connection_In_Progress

This is solved easily, just edit the following lines in the # UI Settings section in your /etc/one/sunstone-server.conf configuration file:

:vnc_proxy_support_wss: yes
:vnc_proxy_cert: /etc/one/certs/one-tornasol.crt
:vnc_proxy_key: /etc/one/certs/one-tornasol.key

We’ve just activated the secure websockets (wss) options and tell Sunstone where to find the SSL certificate and the key (if it’s not already included in the cert). Now, just restart your Sunstone server.

 

There’s another issue with VNC and SSL when using self-signed certificates. When running your own lab or using a development environment maybe you don’t have an SSL certificate signed by a real CA and you opt to use self-signed certificates which are quick and free to use… but this has some drawbacks

Trying to protect you from security threats, your Internet browser could have problems with secure websockets and self-signed certificates and messages like “VNC Disconnect timeout” and VNC Server disconnected (code: 1006)” could show.

VNC_Disconnected

In my labs I just use the openssl command (available in CentOS/Redhat and Debian/Ubuntu in the openssl package) to generate my own Certificate Authority certificate and sign the SSL certificates.

First we’ll create the /etc/one/certs directory in my Frontend and set the right owner:

mkdir -p /etc/one/certs
chown -R oneadmin:oneadmin /etc/one/certs

We’ll generate an RSA key with 2048 bits for the CA:

openssl genrsa -out /etc/one/certs/oneCA.key 2048

Now, we’ll produce the CA certificate using the key we’ve just created, and we’ll have to answer some questions to identify our CA (e.g my CA will be named ArtemIT Labs CA). Note that this CA certificate will be valid for 3650 days, 10 years!…

openssl req -x509 -new -nodes -key /etc/one/certs/oneCA.key -days 3650 -out /etc/one/certs/oneCA.pem

You are about to be asked to enter information that will be incorporated into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.
----
Country Name (2 letter code) [XX]:ES
State or Province Name (full name) []:Valladolid
Locality Name (eg, city) [Default City]:Valladolid
Organization Name (eg, company) [Default Company Ltd]:ArtemIT Labs
Organizational Unit Name (eg, section) []:
Common Name (eg, your name or your server's hostname) []:ArtemIT Labs CA
Email Address []:

Now, we already have a CA certificate and a key to sign SSL certificates. Time to generate the SSL certificate for WSS connections.

First, we’ll create the key for the Frontend, then we’ll generate the certificate answering some questions. In this example my Frontend server is called tornasol.artemit.local and I’ve set no challenge password for the certificate.

openssl genrsa -out /etc/one/certs/one-tornasol.key 2048


openssl req -new -key /etc/one/certs/one-tornasol.key -days 3650 -out /etc/one/certs/one-tornasol.csr

You are about to be asked to enter information that will be incorporated into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank

For some fields there will be a default value,

If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [XX]:ES
State or Province Name (full name) []:Valladolid
Locality Name (eg, city) [Default City]:Valladolid
Organization Name (eg, company) [Default Company Ltd]:ArtemIT Labs
Organizational Unit Name (eg, section) []:
Common Name (eg, your name or your server's hostname) []:tornasol.artemit.local
Email Address []:
Please enter the following 'extra' attributes to be sent with your certificate request
A challenge password []:
An optional company name []:

If everything is fine you’ll have the certs and keys under /etc/one/certs.

Now we’ll copy the oneCA.pem file to the computers where I’ll use my browser to open the Sunstone GUI.

In Firefox we’ll import the oneCA.pem (the CA certificate file) using Preferences -> Advanced -> Certificates -> Authorities tab checking all the options as shown in this image. If using Chrome under Linux it’s the same process when importing your CA cert.

trust_ca_firefox

If using IE or Chrome under Windows, change the extension from pem to crt, double-click the certificate and add the Certificate to the Trusted Root Certification Authorities storage. Some warnings will show, just accept them.

Once we trust our CA certificate, you can open your encrypted NoVNC windows.

Captura de pantalla de 2015-04-25 15:06:08

Free, quick and secure for your lab environment, but remember don’t do this in a production environment! 

Cheers!

vOneCloud 1.4 Released! Cloudify vSphere Infrastructures

We want you to know that OpenNebula Systems have just announced the availability of vOneCloud version, 1.4.

Several exciting features have been introduced in vOneCloud 1.4. The appliance that helps you turn your vSphere infrastructure into a private cloud generates daily reports that can be consulted by every user to check their resource consumption, with associated costs defined by the Cloud Administrator. The Virtual Datacenter provisioning model has been revisited to enable resource sharing easily among different groups, as well as to simplify configuration. The interfaces has also been improved to smooth the workflow of importing vCenter resources via the vOneCloud web interface, Sunstone. But probably most importantly, vOneCloud 1.4 add multi-vm management capabilities, enabling the management of sets of interconnected VMs (services), including the ability to set up elasticity rules to automatically increase or decrease the number of nodes composing a service, according to easily programmed rules that take into account the service demands.

Improvements were also in place for Control Panel, a web interface that eases the configuration of vOneCloud services and enables one click smooth upgrades to newer versions, introducing features to aid in the troubleshooting of the appliance.

The above features and components add to the already present ability to expose a multi-tenant cloud-like provisioning layer through the use of virtual datacenters, self-service portal, or hybrid cloud computing to connect in-house vCenter infrastructures with public clouds. vOneCloud seamlessly integrates with running vCenter virtualized infrastructures, leveraging advanced features such as vMotion, HA or DRS scheduling provided by the VMware vSphere product family.

vOneCloud is zero intrusive, try it out with without the need to commit to it. If you happen to don’t like it  just remove the appliance!

Relevant Links

 

New Open Cloud Reference Architecture

We are excited to announce the release of the first version of the Open Cloud Reference Architecture. The OpenNebula Reference Architecture is a blueprint to guide IT architects, consultants, administrators and field practitioners in the design and deployment of public and private clouds fully based on open-source platforms and technologies. This Reference Architecture has been created from the collective information and experiences from hundreds of users and cloud client engagements. Besides main logical components and interrelationships, this reference documents software products, configurations, and requirements of infrastructure platforms recommended for a smooth OpenNebula installation. Three optional functionalities complete the architecture: high availability, cloud bursting for workload outsourcing, and federation of geographically dispersed data centers.

The document describes the reference architecture for Basic (small to medium-scale) and Advanced (medium to large-scale) OpenNebula Clouds and provides recommended software for main architectural components, and the rationale behind the recommendations. Each section also provides information about other open-source infrastructure platforms tested and certified by OpenNebula to work in enterprise environments. To complement these certified components, the OpenNebula add-on catalog can be browsed for other options supported by the community and partners. Moreover, there are other components in the open cloud ecosystem that are not part of the reference architecture, but are nonetheless important to consider at the time of designing a cloud, like for example Configuration Management and Automation Tools for configuring cloud infrastructure and manage large number of devices.

You can download a copy from the Jumpstart Packages page at the OpenNebula Systems web site.

Thank you!