openATTIC 2.0.16 beta has been released

We're happy to announce the availability of openATTIC version 2.0.16!

Following our mantra "release early, release often", we have published a release four weeks after the release of 2.0.15. One of the highlights in this version is the migration support for openATTIC instances still running on Django 1.6!

Moreover, the openATTIC REST API does now report all installed packages as well as the currently installed openATTIC version. Most other changes are bug fixes and improvements of openATTIC. We have also continued working on supporting Ubuntu 16.04 LTS "Xenial Xerus".

You can install openATTIC on Xenial by following these steps.

We highly recommend using the nightly packages, in order to ensure that fixes of currently known bugs are already included.

# wget -q -O - | apt-key add -

# cat > /etc/apt/sources.list.d/openattic.list << EOF
deb xenial main
deb-src xenial main
deb nightly main
deb-src nightly main

# apt-get update
# apt-get install openattic
# systemctl enable lvm2-lvmetad.socket
# systemctl start lvm2-lvmetad.socket

Known issues:

  • Its not possible to create any share on top of a volume (OP-1697)
  • targetcli cannot be installed next to openATTIC (OP-1694)
  • Its not possible to create a new host with iSCSI iqn or FC wwn (OP-1696)
  • You have to run oaconfig install twice - otherwise oacli key is missing (OP-1695)
  • Ubuntu Xenial: XML-RPCD: No JSON object could be decoded (OP-1671)
  • oaconfig install requires lvm2 systemd services (OP-1685)
  • Internal Server on /api/pools cause of ZFS error (OP-1662)

This release also provides some extensions to our Ceph integration on the backend side. For example, we have continued working on our DeepSea integration.

Also, we can now migrate existing openATTIC databases on Ubuntu Xenial and SUSE which are still based on Django 1.6. Which means you don't have to delete and recreate your database when you upgrade to newer Django versions.

To download and install openATTIC, please follow the installation instructions in the documentation.

Please note that 2.0.16 is still a beta version. As usual, handle with care and make sure to create backups of your data!

We would like to thank everyone who contributed to this release.

Your feedback, ideas and bug reports are very welcome. If you would like to get in touch with us, consider joining our openATTIC Users Google Group, visit our #openattic channel on or leave comments below this blog post.

See the list below for a more detailed change log and further references. The OP codes in brackets refer to individual Jira issues that provide additional details on each item. You can review these on our public Jira instance.

Changelog for 2.0.16:

  • Backend: The REST API 'host' resource returns the openATTIC version (in version.txt) if the host is an openATTIC host (OP-553)
  • Backend: The REST API 'host' resource returns the installed Django apps if the host is an openATTIC host (OP-1023)
  • Backend: Removed ID parameter from volume update view (OP-1473)
  • Backend: Salt minions keys can now be accepted via our REST API (OP-1601)
  • Backend: Reverted NAGIOS_PLUGIN_DIR on SUSE back to /usr/lib/nagios/plugins
  • Backend: The backend does no longer print the whole traceback into the logfile if the XML file of an RRD file is not found (OP-1632)
  • Backend: Django migration files aren't checked by Flake8 anymore (OP-1638)
  • Backend: Added reading and writing of the policy.cfg of DeepSea REST API (OP-1617)
  • Backend: The is_oa_host database field is set to True for oA hosts by 'oaconfig add-host' (OP-1665)
  • Backend: Added database migrations for Django 1.6 (OP-1649)
  • Backend: Fixed Bug on Ubuntu Trusty preventing deletion of iSCSI targets (OP-722)
  • Backend: Fixed issue breaking the WebUI on Xenial (OP-1689)
  • WebUI: Tabs will be selected as expected (OP-1082)
  • Packaging: The python-configobj dependency is moved to the openattic-base package (OP-1666)
  • Packaging: Added missing dependency openattic-module-cron in openattic-module-lvm (OP-1664)


Comments powered by Disqus