Right on time before the holiday season, we're happy to announce a new beta release of openATTIC.
openATTIC logo wall painting!
For this release, we fixed several bugs and usability issues in the GUI and extended the RESTful API test cases as well as the WebUI tests. Furthermore, the openATTIC backend code and RESTful API have been extended with the functionality to grow unformatted DRBD connections.
From very early on (Feb 2011), openATTIC has been licensed under the GNU General Public License (GPLv2) and new releases were made publicly available for download.
However, contributing patches or submitting code for new features was somewhat of an ordeal, as it required filling out and submitting a "Contributor License Agreement". This was mandatory, as we wanted to maintain the option to relicense openATTIC under a different license.
Going forward, this is no longer a requirement. Instead, we have decided to adopt the "sign-off" procedure introduced by the Linux kernel.
Today i would like to show you, how you can easily create a Python script with openATTIC for automatic snapshot creation.
First of all we need a little Python script which can create snapshots for the specific openATTIC volume. This is really easy, because you can use the "API Recorder" within openATTIC. You just have to select an existing volume, click the record button (the little record symbol on the right topbar) and create a snapshot of that volume. Afterwards, you click the stop button (the record button switches into a stop button after you clicked it) and you will get a working Python script, containing the actual API calls.
On November 21st, the Linux User Group Vorarlberg organized the 17th LinuxDay in Dornbirn, Austria. It took place at the Höhere Technischen Lehranstalt (HTL) Dornbirn and attracted several hundred attendees from the so called "DACH" Region (Germany, Austria and Switzerland).
The schedule consisted of more than 20 separate lectures (presented in German), that were held in three parallel tracks.
As mentioned in the openATTIC 2.0.3 beta announcement before, we try to stick to our 5-6 weeks release plan - time to publish openATTIC 2.0.4 beta!
This release was the first one based on an improved development workflow. We're now using Mercurial branches to separate ongoing development work from the rest of the code base and implemented code reviews and pull requests via BitBucket to coordinate the ongoing development work. It took a bit to get used to this way of collaborating, but it helped us to avoid trampling on each other's work or destabilizing the code base by accident. In addition to that, the code reviews help us to better distribute and share the knowledge of the various openATTIC subsystems between the developers.
The OpenStack Foundation held their last biannual OpenStack Summit in Tokyo, Japan, from October 27-30, 2015. OpenStack Summits include keynotes, in-depth technical discussions, hands-on workshops, and the full presence of almost every key player in the OpenStack ecosystem.
I attended the summit together with three other colleagues from it-novum, from Tuesday till Friday. In this article, I'll try to summarize my impressions and share my notes and observations.
Some time ago, I attended the Kieler Linux Tage, to talk about managing storage on Linux using openATTIC.
The post processing took a while, but the video recording of my presentation titled "Flexibles Storage Management unter Linux mit openATTIC" (in German) is now available on YouTube (in 4K resolution!):
I hope you enjoy it! A big Thank You to LuiKast for the professional recording and post-processing.
The slide deck is also available on SlideShare:
I switched from Outlook to Thunderbird and after i configured my email within Thunderbird my whole subfolders were missing. After a little while i found a checkbox that fixes this problem.
Check: -> "Account Settings" -> "Server Settings" -> "Advanced" -> "Server supports folders that contain subfolders and messages"
Now you have to restart your thunderbird and voila :-).
We're happy to announce that openATTIC version 2.0.3 beta has now been released!
We're trying to stick to the core mantra of Open Source, by releasing early and often. We intend to establish a cadence of publishing a new release build roughly every 5-6 weeks. For the impatient, we also provide nightly builds that contain all changes that have been committed into the development branch and have passed the test suites.
One notable highlight in the 2.0.3 release is the inclusion of some additional Ceph support in the Web UI: it is now possible to review the CRUSH map and perform some basic editing of the Ceph cluster layout (replication rules, placements) this way. We're very eager on receiving feedback on this functionality, as it's currently still under development.
We've also made some progress in adding DRBD support to the openATTIC RESTful API - it's now possible to create and delete mirrored volumes. However, web UI support and a method to resize existing mirrored volumes is still in the works - we hope to deliver these missing pieces with the next release.
In addition to these new features, we fixed several bugs and usability issues. We also added numerous additional tests to the API and UI test suites.
Thanks to everyone who contributed to this release!
Page rendering speeds and security of a static web site or blog like ours can not be beaten by any CMS or blog software that is developed in some kind of scripting language using a database backend.
However, one downside is the lack of a feedback channel like a comment system. As we're very eager to receive your feedback, we've now added a comment system to this blog, powered by Disqus. You can either leave comments below any post, or visit the openATTIC channel on Discqus to join the conversation.
Another highlight worth mentioning: as already mentioned in a previous blog post, we've applied for an Open Source License for Atlassian Jira. They were kind enough to approve our request very quickly, so we now have a dedicated Jira instance for tracking the openATTIC development. We intend to enable self-registration, so that you will be able to create new issues or comment on existing ones once you've created an account and have logged in. Once this is in place, we'll disable the bug tracker on BitBucket, to avoid confusion. Any open issues will be migrated to Jira first, of course. We're very grateful for this generous offer from Atlassian. Thank you!
Any many thanks to Kai Wagner for setting up both the comment system and Jira in record time!