Opennebula:what ' snewin5.4 Chinese version

Source: Internet
Author: User
Keywords Opennebula full network support full storage management Opennebula Chinese version
Tags access added analysis api based change cloud community

Opennebula:what ' snewin5.4 Chinese version.

Opennebula 5.4 (this version, named Medusa, the ogre in Ancient Greek mythology) is the third version of the Opennebula 5 series. As we maintain a high level of attention to the needs of the community, we also devote a great deal of effort to enhancing the key functional points described in the 5.2 continuity plan.

Typically, almost every Opennebula component is focused on usability and functionality enhancements, and reduces API changes to a minimal rate to avoid interfering with other components of the ecosystem. One of the important points of focus is that we have enhanced the integration of vcenter, including storage and network management. At the same time, a number of new components have been added to enhance the Opennebula experience.

We made a big fix on vcenter integration. Our team decided to unify and standardize the vcenter integration and the level of support for KVM. This means:

1. Full storage management. Non-persistent mirrors are supported in addition to temporary disks (volatile workloads). Currently, Opennebula can perform all disk and storage references. It also supports linked cloning and application markets.

2. Full network support. You can now create standard port groups and distributed port groups based on vcenter within Opennebula, or even directly create Vswitche (virtual switches). You can assign Vlanid to the port groups created by Opennebula.

3. Improve monitoring efficiency. Speed, there are two orders of magnitude of ascension.

4, the ability to import enhanced. The restrictions on importing resources are lifted and VNC for wild VMS can be activated automatically.

5, disk size reset. When a virtual machine is deployed, the selection of virtual machines and template catalogs ... and other changes are as follows:

We have added a new resource, virtual unit (VM groups), to achieve strong correlation and repulsion between VM-VM and Vm-host. A virtual machine is a series of related virtual machines whose deployment constraints can be based on association and exclusion policies. A virtual group is defined as a series of roles. A role is defined as the type or category of a virtual machine, we can increase the expression of VM Group to define the role affinity between virtual machines, or between virtual machines and hosts. This ensures that a newly created virtual machine is dynamically added to the associated or excluded policy from boot up, and that other virtual machines can be added after VM group creation. as follows:

What's more, opennebula5.4 brings a native consistency algorithm that enables a Opennebula front-end to achieve a highly reliable deployment without relying on third-party components. This distributed consistency protocol provides disaster tolerance (FT) and state consistency capabilities for Opennebula services. The construction of a consistency algorithm revolves around two concepts, the System State <--> database datasheet, and the log <-->sql query results, which are applied to all the databases that the Opennebula service will use. In order to maintain a consistent view of the system services, modifications of the system state are performed through a specific node. The Opennebula service cluster elects a node as the leader node. The leader node periodically sends a heartbeat to the other node (from the node) to maintain its leadership position. When a leader node sends a heartbeat failure, the voter node will initiate a request to become a candidate node and start a new round of elections. This feature, combined with floating IP and the correct sunstone configuration, gives Opennebulacloud robustness. This distributed System State function is also used to implement Opennebula multi-domain deployments. The MySQL cluster is no longer needed for both ft and ha, so administrators can ignore MySQL redundancy replication.

In the 5.4 release, there are many improvements, such as the virtual machine lifecycle, flexible resource licensing, such as disk thermal expansion. Increased support for Ceph, enhanced disk I/O feedback, sunstone It cost analysis, flexible IPV6 definition, application market began to support HTTP proxies, Opennebula database cleaning tools, resource group isolation, multiple Sunstone function enhancements (VNC, Password dialogs, confirmation dialogs, better vcenter support, persistent tagging, usability enhancements, network promotion, user input in Oneflow, and many more new features that enhance your cloud experience. As in the previous release, the team spared no effort to fix bugs and improve common availability in order to meet the reliability requirements of the cloud-tube platform.

This version of Opennebula is named after the Medusa Nebula (Medusa Nebula, also known as the Jellyfish Nebula), a massive planetary nebula located on the edge of Gemini and the constellation of puppies. The nebula, also known as Abel 21 or Sharpe 2-274, was first discovered in 1955 by astronomer George O. Abel of the University of California, Los Angeles, which he labeled as an old planetary nebula. The nebula, like a braided layer of luminous filaments, is the origin of its name, much like the ancient Greek mythology of Medusa's snake hair.

The Opennebula 5.4 Medusa version is considered a stable release that can be upgraded in a production environment.

The following list allows you to view the key features of Opennebula 5.4 (adetailed list of changes can is found here):)

Opennebula Core:

New ha mode: does not rely on third parties, providing native HA capability (based on raft consistency algorithm) for Opennebula components, including Sunstone.

Simplified multi-domain deployments, based on the new Opennebula distributed System State functionality, no longer requires the installation and maintenance of MySQL's redundant databases.

VM Advanced access Control Policy (ACL), which can now be redefined for each VM operation's access level (admin, manage, use).

Improves traceability of VM operations, and the virtual machine history feature logs associated data from virtual machine operations

VM Group: Defining the relevance and repulsion of a series of virtual machines

Database Maintenance tool, which supports cleaning historical data, and can implement bad data and dirty data update through ONEDB command.


Enhance disk Management, such as online thermal expansion of virtual machine disks, as well as I/O feedback and monitoring.

Enhance CEPH integration capabilities By default Ceph snapshots are a flat structure (optionally as other storage backend), and it is also easier to specify different authentication methods when deploying multiple clusters now. Finally, we added a new option "Trim/discard" (Trim/Discard)

Better IPV6 support, including definitions of security groups and NON-SLAAC IP V6 address segments. (NON-SLAAC: Non-traditional stateless address auto assignment).

Improved network-specific settings: These settings may overwrite multiple default options when creating a link to the virtualization layer, including Mac spoofing, ARP cache poisoning, and the interface MTU or STP, among others.

Mixed cloud: Amazon EC2

Enhanced EC2 monitoring and virtual machine Lifecycle management: Better handling of cloudwatch data points to avoid errors caused by long-term network problems.

Better EC2 Resource Description information, the information used to access the EC2 domain is now stored on the corresponding Opennebula host, including EC2 certificates, resource constraints, and EC2 domain names;


Association/Exclusion: VM-VM, Vm-role, Vm-host Association and exclusion strategies used by VM Group resources;

Virtual machine Priority: When Pending/reschedule state, static virtual machine priority policy can change the default distribution virtual queue order (first in first out)


Perfect customization: More tags for action-constrained usage, and enhanced logo customization capabilities;

Persistent Resource Label: If no resources are labeled, this label will not expire

Enhanced mirroring Upload control: Supports process feedback and retransmission capabilities.

Better group isolation: Allows direct change of primary and secondary groups from the group management interface; When group switches, only the group resources currently in use are displayed so that the project can be easily worked on.

Extends user input, adding new types, such as Boolean types and the ability to define order.

Fixed multiple language keyboard support in VNC

Improve the cost analysis. Friendlier dialog box for defining and evaluating virtual machine template Cost Analysis

A large number of practical enhancement points:

More Secure Password Change dialog box

VNC dialog box supports ESC button action

Improve the Resource Overload dialog box

More virtual machine templates, instance dialogs, and tab virtual machine logos appear

Resource release action, add confirmation dialog when reclaiming disk or erasing a virtual machine

Cloud view to differentiate between your own virtual machines and group-owned virtual machines


A notable milestone for this release is that vcenter is no longer a public cloud, but rather a mature hypervisor to manage. The monitoring and import process has been greatly optimized and time efficiency has increased by two orders of magnitude.

Improve virtual machine and template management. Where there is, Mount CDROM to a VM without driver, automatically add VNC capability when importing Wilds VM, save virtual machine as a template, link clone capability (with original mirror as parent mirror, incremental part form chain dependency), support create mirror and network for imported virtual machine templates and directory deployment features ( Represents virtual machine disks and network adapters.

Network creation Support: The virtual network definition has a new network pattern, standard, different port groups, and virtual switches can be created directly in Opennebula, and when a port group is created, you can specify the MTU, the VLAN ID, and the port number.

Storage Management improvements (datastore, image, and Disk Management), support for non-persistent mirroring and temporary hard drives (originally supported only in KVM), clustered datastore can be clearly distinguished when importing, support disk resize, save disk, and disk statistics monitoring.

vcenter defaults, some default values for vcenter properties, such as Nic mode, can be specified in a new configuration file.

Unlock command limits, such as the Vcenter cluster instance and the name of the Datastore, which can now support spaces.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.