openATTIC 3.7.0 has been released
We're happy to announce version 3.7.0 of openATTIC!
Version 3.7.0 is the first bugfix release of the 3.7 stable branch, containing fixes for multiple issues that were mainly reported by users.
There has been an issue with self-signed certificates in combination with the RGW proxy which is now configurable. We also improved the openATTIC user experience and adapted some of our frontend tests in order to make them more stable.
As mentioned in our last blog post our team was working on a Spanish translation. We are very proud to have the translation included in this release. Thank you Gustavo for your contribution.
Another highlight of the release is then newly added RBD snapshot management. openATTIC is now capable to create, clone, rollback, protect/unprotect and delete RBD snapshots. In addition it is also possible to copy RBD images now. Furthermore the "pool edit" feature received a slight update: we implemented the option to set the "EC overwrite" flag when editing erasure coded pools.
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 irc.freenode.net 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 version 3.7.0
Added
Changed
Fixed
- WebUI: added support for enabling EC overwrite on existing pools (OP-3158)
- WebUI: fixed typo in RBD creation form (OP-3148)
- WebUI: Ignore unused operations on the CRUSH Map Editor (OP-3154)
- WebUI: "Last Change" column not displayed in Pools table (OP-3162)
- WebUI: 404 not found when increasing number of rows displayed in a table (OP-3163)
- WebUI/QA: Fixed timing issue with scrub e2e tests (OP-3152)
- Backend: RGW proxy can't handle self-signed SSL certificates (OP-3161)
- Backend: REST API didn't respond in time (OP-3164)
Comments
Comments powered by Disqus