Skip to content

Release Notes

Jump to bottom
Jan Poctavek edited this page Jul 24, 2021 · 104 revisions

4.x

  • Last release: 2021-07-24
  • Codename: Bratislava

Changelogs

4.5

  • Platform: 20210711T112647Z (upstream/release-20210701)
  • Release: 2021-07-24

This release has received backported bhyve support from upcoming major version v5.0 plus other interesting new features.

Release highlights:

  • BHYVE support
  • Live BHYVE disk resize without VM reboot
  • Restore snapshot into other VM - very handy way how to convert KVM into BHYVE
  • Support for zone transfers to external DNS slaves

Quick upgrade steps: create a snapshot of admin VMs (recommended), upgrade of management server, upgrade of nodes software, upgrade the node SmartOS platform. See also Upgrading Guide.

If you're upgrading from v4.0 and older, you need to upgrade platform on the first compute node and reboot before main upgrade:

  • On the node that hosts dns01 appliance run esdc-git-update v4.4 && esdc-platform-upgrade v4.5 && init 6

4.4

  • Platform: 20201111T142959Z (upstream/release-20201105)
  • Release: 2020-11-16

This release fixes the security bug in SmartOS and brings some minor platform bugfixes and GUI improvements. See changelog for full list.

4.3

  • Platform: 20200715T230801Z (upstream/release-20200715)
  • Release: 2020-08-29

Release highlights:

  • With this release you can deploy OPNSense VM to serve as a router from admin to external network
  • Image size for the first compute node has increased from 4GB to 6GB (the image for other compute nodes is still 2GB)
  • From now on, installer generates /usbkey/answers.json file so you can do unattended installation more easily (just update passwords (because they were not written) and copy it to private/answers.json on next installation USB key.
  • Bugfix for platform kvm-clock clocksource
  • Redesign of embedded PowerDNS infrastructure, recursion is enabled only for networks defined in Danube Cloud.
  • Changed default value of MON_ZABBIX_TEMPLATES_VM_RESTRICT: now it is allowed by default to apply any Zabbix monitoring template to a VM from Danube Cloud GUI/API.

4.2

  • Platform: 20191019T085327Z (upstream/release-20191010)
  • Release: 2019-11-03

From now on, Danube Cloud supports hybrid UEFI/BIOS boot. You can boot both ways using the same USB image. Fresh disk installs of v4.2 and later also support hybrid boot.

4.1

  • Platform: 20190422T104439Z (upstream/release-20190328)
  • Release: 2019-05-22

The Danube Cloud Team is pleased to announce the release of Danube Cloud version 4.

The biggest change is that all features from the Enterprise edition were merged into this Community edition. We value the power of open source and this was the final step towards it. We still offer support for both editions to help you to get the most out of Danube Cloud and to help you in unexpected situations.

One of these enterprise features is VM replication which enables continuously, incrementally and consistently replicate VM disks onto other compute nodes, allowing an instant one-click VM restore on the other compute node in case of a failure of the original compute node.

The next big enterprise version feature is High availability of the management GUI/API. The helper scripts ha-prepare and ha-deploy will walk you through the steps of deploying additional VMs mgmt02 and mgmt03 and an ansible-based playbook will cluster them together by a corosync/pacemaker stack. Please note that this is not an install-and-forget feature. It is important to know at least something about managing pacemaker clusters so you know what to do in case of a failure. Paid support can be very helpful here.

Live migration code has also received improvements. SmartOS has implemented better VM system clock handling and therefore you can use default OS configuration inside VMs during migrations (before this release, we have recommended to use HPET clock source instead of TSC).

Interesting change is also increased number of possible vNICs for VMs from 6 to 16.

For a full list of smaller changes and fixes, please see the Changelog.

Quick upgrade steps: create a snapshot of admin VMs (recommended), upgrade of management server, upgrade of nodes software, upgrade the node SmartOS platform, (optional) upgrade OS in mgmt VMs (yum update / pkgin full-upgrade). See also Upgrading Guide.

Upgrading note 1: You need a working internet connection from nodes and management VMs for upgrade to succeed.

Upgrading note 2: Although, it is not directly related to the Danube Cloud upgrade, you should know it because Danube Cloud CentOS images use the cloud-init. New version of the cloud-init package (v18.2) changes behavior in setting a hostname. Now it tries to set an OS hostname even if the hostname is not present in the VM metadata settings. Consequently, after you upgrade the OS in a VM and reboot, you might end up with a hostname set to VM's UUID string. To avoid it, please go to VM settings and create a metadata key hostname with the desired value. Starting with Danube Cloud 4.0, this metadata entry is added automatically for all newly created VMs.

3.0

  • Codename: Vienna
  • Platform: 20180318T095138Z (upstream/release-20180315)
  • 3.0.0 platform: 20180318T095138Z (upstream/release-20180315) released on: 2018-05-07
  • 3.0.0-rc5 platform: 20180318T095138Z (upstream/release-20180315) released on: 2018-04-16
  • 3.0.0-rc4 platform: 20180318T095138Z (upstream/release-20180315) released on: 2018-03-21
  • 3.0.0-rc3 platform: 20180218T102008Z (upstream/release-20180215) released on: 2018-02-25
  • 3.0.0-rc2 platform: 20180218T102008Z (upstream/release-20180215) released on: 2018-02-19 - This and previous releases were shipped with a broken PowerDNS integration within Danube Cloud (affects only new installations)
  • 3.0.0-rc1 platform: 20180105T193033Z [upstream/release-20180104) released on: 2018-02-07
  • 3.0.0-beta3 platform: 20180105T193033Z (upstream/release-20180104) released on: 2018-01-23
  • 3.0.0-beta2 platform: 20180105T193033Z (upstream/release-20180104) released on: 2018-01-22
  • 3.0.0-beta1 platform: 20180105T193033Z (upstream/release-20180104) released on: 2018-01-16

NOTE: When upgrading from 2.x, the software update must be performed manually; first on the management server and then on all compute nodes. On compute nodes, first, upgrade the software (using esdc-git-update) and only after that you can upgrade the platform.

NOTE: This version relates to a new platform version. The platform image should be also updated. It is required when you plan to use: KVM live migration, network overlays or want protection against the Meltdown attack.

NOTE: The 3.x compute node cannot be connected into a Danube Cloud installation with a 2.x management virtual server. The management server has to be updated first.

The Danube Cloud Team is pleased to announce the release of Danube Cloud version 3.0.

The new major version of Danube Cloud includes plenty of new features. The most interesting one will be definitely the introduction of Live Migration for KVM virtual machines. The Live Migration capability in Danube Cloud does not depend on shared storage. The decision to implement this feature was mostly based on wishes and needs of our users. This feature should be considered experimental for now.

Another important feature inspired by requirements of our customers are Network Overlays and VXLANs. With this feature integrated into Danube Cloud it is much easier to interconnect compute nodes residing in various datacenters. It is now possible to control compute nodes in other physical locations connected via internet (without the need of a L2 connection). Virtual machines in different datacenters can see each other as if they were connected locally into the same local private switch.

Version 3.0 also adds another major feature: Zabbix Alert Management. Who should receive alerts for which servers can be now configured via Danube Cloud. Listing of current and historical monitoring alerts is available from the Danube Cloud web management console.

Besides many features and bug fixes, the official User Guide got also some interesting updates. Most notably there is now a Disaster Recovery HOWTO and a new Upgrading Guide.

The 3.0 release includes a new system menu intended for Danube Cloud operators and the software update functionality was completely re-implemented. Therefore the upgrade from 2.x should be performed manually.

Download

Changelogs

2.6

  • Codename: Tuttlingen
  • Platform: 20170624T192838Z (upstream/release-20170622)
  • 2.6.7 released on: 2017-11-06
  • 2.6.6 released on: 2017-10-17
  • 2.6.5 released on: 2017-10-04
  • 2.6.4 released on: 2017-09-11
  • 2.6.3 released on: 2017-08-21
  • 2.6.2 released on: 2017-08-09
  • 2.6.1 released on: 2017-08-07
  • 2.6.0 released on: 2017-07-21 - This version introduced a serious bug #219 -> please update to 2.6.1 or later

The 2.6 release includes an updated SmartOS platform image, which has many new features: new installer (NTP server option, admin vlan ID, configuration of other NIC tags), new PXE network boot/install options and updated pkgsrc release (2016Q4). Our changes to the SmartOS platform were refactored in a way that should allow us to merge upstream releases more easily.

The Danube Cloud web management portal received new interesting features such as: comparative VM graphs per compute node (CPU, memory, disk), customizable shutdown timeout for KVM guests, user editable notes of VMs and nodes (with markdown support), ability to disable reservation of replicated VM resources, as well as experimental support for Linux zones.

The monitoring (Zabbix) synchronization code was completely refactored for potential future support of another monitoring backends. The Zabbix backend now synchronizes users and user groups from the Danube Cloud management to the Zabbix server, which is a necessary precondition for future integration of alerting configuration.

NOTE: After updating the mgmt software (es set /system/update) all compute nodes must be updated to the 2.6.x version (es set /system/node/<hostname>/update).

Download

Changelogs

2.5

  • Codename: Donaueschingen
  • Platform: 20161207T144343Z
  • 2.5.3 released on: 2017-05-16
  • 2.5.2 released on: 2017-04-11
  • 2.5.1 released on: 2017-03-07
  • 2.5.0 released on: 2017-03-03

This release adds compute node monitoring graphs into the API and GUI. CPU, Memory & swap, storage and network graphs are available per each compute node and can be used to determine usage and performance problems on physical servers. There are also several smaller bug fixes and features, including support for Windows 2016. The 2.5.2 minor release fixes many small bugs mostly related to monitoring and graphs. The 2.5.3 release has added support for restoring service VMs, which is important for a complete disaster recovery of a Danube Cloud installation (assuming that all VMs are backed up).

Download

Changelogs

2.4

  • Codename: Schwarzwald
  • Platform: 20161207T144343Z
  • 2.4.0 released on: 2017-02-22

This is the first release, which was fully developed as an open source project.
The most visible changes are improvements of the UX in the GUI (UI elements are used consistently across the web interface). Furthermore, API now supports SmartOS' nics.*.allowed_ips feature. And of course, we released lots of small features and fixes - see changelogs for details.

Download

Changelogs

2.3

  • Codename: Erigones SDDC -> Danube Cloud
  • Platform: 20161111T125226Z
  • 2.3.3 released on: 2017-02-04
  • 2.3.2 released on: 2016-12-17
  • 2.3.1 released on: 2016-12-15
  • 2.3.0 released on: 2016-11-17

Initial open source release.

Download

Changelogs

Homepage | User Guide | API Reference | Wiki

Clone this wiki locally