It cost's me some nerves and time to figure out how to create a vagrant image from a libvirt kvm vm and how to modify an existing one. Thanks to pl_rock from stackexchange for the awesome start.

• First of all you have to install a new vm as usual. I've installed a new vm with Ubuntu 16.04 LTS. I'm not sure if it's really neccessary but set the root password to "vagrant", just to be sure.
• Connect to your VM via ssh or terminal and do the following steps.

Read more…

It is our great pleasure to announce Version 3.6.1 of openATTIC.

3.6.1 is a bugfix release for the 3.6 stable branch, containing fixes for multiple issues that were reported by users.

In addition to that, it contains several usability enhancements and security improvements.

Behind the scenes, we continued with converting the WebUI code into Angular components in preparation for moving to Angular 2 in the near future.

Note that this release depends on a DeepSea version 0.8.2 or higher, as one improvement to the iSCSI target management (OP-2926) required making changes to both openATTIC and DeepSea.

Read more…

We're happy to announce that our demo is up and running again.

The demo will be reinstalled every day at midnight. The login credentials are openattic/openattic. With the next release we'll include the demo mode which allows us to show this information at the top of the demo.

So please take the chance to visit demo.openattic.org

Last week SALTCONF17 took place at Salt Lake City and I was one of the attendees of this great event which included 2 days of pre-conference training and 2 days of conference.

Salt Palace Convention Center was the chosen place for this conference that included 60 keynotes and breakout sessions with dozens of SaltStack use cases presented by SaltStack users and in-depth tech talks from the SaltStack developers and experts.

The SaltStack Certified Engineer exam was available to attendees that took the pre-conference training (learn more about the SSCE certification and exam here).

Read more…

We're happy to announce version 3.6.0 of openATTIC.

Given the fact that openATTIC 3.5.3 was only a bug fix release this 3.6.0 release includes all the improvements and changes since 3.5.2. We cleaned up and removed a lot of unnecessary things and also made some usability improvements to the UI.

The most visible change in openATTIC 3.6.0 is the unification of Grafana and our "old" widgets into one single dashboard page.

We now have one unified dashboard and you don't have to switch between the "old" and the new Grafana dashboard. We included the functionality of the old status widget into our default dashboard. If your cluster is in an error or warning state, this will be shown at the top of your dashboard including the failure message from the 'ceph health' command.

Read more…

We are happy to announce version 3.5.3 of openATTIC.

3.5.3 is a small bugfix release mainly containing fixes for upgrade bugs from openATTIC 2.0.

This release also features fixes regarding deletion of RGW users with existing buckets and the health widget in the classic dashboard widget.

Read more…

I'm very glad to announce that we have our automatic nightly master tarball and package build functional again.

I've you're interested in the latest code we're currently working on, just checkout our nightly master build. The package and tarball will be updated every hour if there has been a commit since the last build.

Link to: Source Link to: Package Link to: Installation Guide

Due to some planned maintenance work in SUSE's data center, a number of services will not be available from Friday, Oct. 13th, 16:00 UTC until Monday, Oct. 16th, 12:00 UTC.

In particular, the following services related to the openATTIC project will not be available:

• JIRA
• Confluence
• Downloads
• Downloads from SUSE's Build Service

The openATTIC web site and blog as well as the documentation will not be affected by this.

Recently, I was responsible for the release of openATTIC 3.5.1 and found myself in the position of being the so called "Release Captain". In the following blog post I'm going to explain the release process and the meaning of the openATTIC Release Captain.

We release a new version of openATTIC every few weeks. To keep the quality of the released version as high as possible and to make sure that the user doesn’t run into obvious issues, the release process needs to be well structured and repeatable.

Read more…

We are proud to announce Version 3.5.2 of openATTIC.

Today, we broke our regular release cycle, with a good reason. After we published version 3.5.1, we found a hand full of bugs that, from our point of view, could frustrate the user while managing their cluster with openATTIC.

For example, in this version we prevent the user from deleting buckets that are referenced/used by NFS etc.

Furthermore, due to changes in the latest Ceph version, it wasn't possible to create erasure code profiles anymore. This issue has been fixed in this release as well.

Some other minor changes and UI improvements made it also into this release, see the CHANGELOG for further details.

Read more…