Most of the work on this version has been done under the hood to further improve performance and overall optimization of the core, as well as the front-end access layers, including S3, file system interfaces, and management tools.
The list of new features includes:
Service IDs: This is probably the most important improvement made to OpenIO SDS. Instead of mapping internal services to IP addresses, they will be mapped to an internal service directory that is always accessible to all nodes in the cluster. This feature will allow the software to support hybrid (on-premises + cloud) configurations, Docker containers, and Kubernetes in production.
OIO-FS V2: OIO-FS is a simple file system interface that maps a container to a file system so it can then be mounted on a Linux host. The FUSE-based file system connector has been improved, and this connector is now part of the standard subscription; all our customers will be able to take advantage of it without any additional cost. OIO-FS Enterprise will be available with the 18.10 release as an extra module for the standard subscription and will include the HA (High Availability) capability.
Improved S3 compliance: Work on S3 compliance is constant to ensure that the S3 API and all its extensions attain the best compliance and map internal features and APIs correctly to S3 and Swift. In this release a lot of work has been done to ensure that versioning and lifecycle management is consistent across different APIs and aligned with the expectations of our customers.
Container snapshots (beta): It is now possible to create a new container (bucket) starting from an existing one, pointing to the same data chunks as the original container. Operations performed on the new container do not affect the original data, but create new objects or data chunks for their updated parts. This feature will be very useful for backing up production buckets to cold storage.
Simplified deployment tools: Now based on Ansible, these tools include a pre-flight check procedure and all the necessary processes to make new nodes compliant with OpenIO SDS requirements. They make it possible to set up more cluster parameters during the initial deployment, which also results in a smoother, simpler process.