Changelog for
libelasto_file1-0.9.3-1.3.x86_64.rpm :
* Tue Sep 25 2018 ddissAATTsuse.com- Update to Elasto 0.9.3 + detect and set MIME content-type for uploads and copies + drop tcmu-runner backend
* Sun Feb 18 2018 ddissAATTsuse.com- Update to Elasto 0.9.2 + deprecate and disable (by default) tcmu SCSI backstore + the public API has been discontinued by tcmu-runner upstream + fix Azure tests when running with Access Key instead of PS + work towards custom host support, for Ceph rgw, etc.
* Sun Jul 09 2017 ddissAATTsuse.com- Update to Elasto 0.9.1 + add --developer option for test and debug utils + use new HMAC_CTX API with openssl >= 1.1.0 + handle zero length I/Os immediately
* Thu Apr 13 2017 ddissAATTsuse.com- Update to Elasto 0.9.0 + rename client binary elasto_cli -> elasto + perform SSL certificate hostname validation + pipeline multi-part put requests + add command prompt usage hints + bump to latest version of linenoise + use us-west1 as default AWS S3 location + rework connection redirect to reuse ev_base + add new client stat command
* Tue Dec 06 2016 ddissAATTsuse.com- Update to Elasto 0.8.2 + install elasto_tcmu configuration helper + add elasto_tcmu (and config helper) man page
* Mon Nov 28 2016 ddissAATTsuse.com- Update to Elasto 0.8.1 + experimental LIO / TCM-user SCSI target backend + requires tcmu-runner and kernel with CONFIG_TCM_USER2 + support Azure Shared Key signatures + required for premium storage account I/O + fix starky elasto_cli python test suite + build against latest libevent 2.1 release
* Sat Aug 06 2016 ddissAATTsuse.com- Fix Fedora 24 and CentOS 7 builds
* Sat Aug 06 2016 ddissAATTsuse.com- Update to Elasto 0.7.3 + fix non-sparse uploads + fix Azure multi-block uploads for blobs with long names + allow for .. and . client path components - in preparation for \'cd\' support with relative paths + improve path validation and corresponding unit tests
* Sat Apr 02 2016 ddissAATTsuse.com- Add libelasto_file1 Requires for devel package
* Mon Mar 28 2016 ddissAATTsuse.com- Update to Elasto 0.7.2 + Add created/existed elasto_fopen() returns + Add elasto_file library pkg-config
* Thu Mar 24 2016 ddissAATTsuse.com- Use OBS tar_scm to pull down the source tarball from the git repo
* Thu Mar 24 2016 ddissAATTsuse.com- Package manpage on recent SUSE and Fedora distros only + Others don\'t have aciidoc, just ship text file instead
* Mon Mar 14 2016 ddissAATTsuse.com- Update to Elasto 0.7.1 + Support space-efficiient uploads and downloads + Only upload/download allocated ranges in sparse files + Update to upstream linenoise version 1.0 + Improve docs + Use asciidoc instead of docbook + Azure Blob/File Service get range operation support
* Sun Oct 18 2015 ddissAATTsuse.com- Update to Elasto 0.7.0 + Azure File Service Copy File support + Azure storage account access key credentials + Remove suboptimal reconnect-per-request dispatch behaviour
* Sun Jul 05 2015 ddissAATTsuse.com- Update to Elasto 0.6.1 + Improve req function parameter validation + Convert libfile mk/rmdir helpers to use elasto_fopen() + Move libfile connection handling into the per provider modules, allowing for future removal of silly per-op reconnect logic + Add Azure File Service libfile tests
* Sat May 23 2015 ddissAATTsuse.com- Update to Elasto 0.6.0 + Use libevent HTTP(S) client instead of libcurl + Support the Azure File Service + Extend libelasto_file + Improve unit test coverage- Remove unused and broken Debian build files
* Sun Dec 07 2014 ddissAATTsuse.com- Update to Elasto 0.4.1 + Add get and set file properties support + Add file property manipulation tests + Add file creation and IO tests + Fix Put File Range URL + Add mandatory length header to create file requests
* Mon Dec 01 2014 ddissAATTsuse.com- Update to Elasto 0.4.0 + Support PublishSettings v2 schema + Make headers C++ compatible. + Issue#4 + Fix crash parsing new publishsettings + Issue#5 + Improve Azure File Service support + File and directory request handling + Test suite
* Tue Oct 21 2014 ddissAATTsuse.com- Update to Elasto 0.3.2 + Fix security vulnerability that could expose Azure SSL certs to other users with access to the same directory as the publish settings file. + Use a safe/restricted temporary directory for this purpose. + Add support for Azure file service share creation.
