Pure is announcing the add-on of file services to its Purity direction software. At a high level, they are adding SMB and NFS protocols and a file system to their storage arrays. This means that with Pure Storage, you can now run the storage services needed, block or file, to friction match the requirements of your workload.
Let’s dive into the details of these additions to the Pure FlashArray™ family.
The engineering science for the FlashArray™ File Services product comes from the 2019 acquisition of the Swedish company Compuverde. Central parts of the Compuverde technology stack have now been integrated into Pure Purity.
The Purity operating system traditionally provided the means for storage admins to manage block protocols, volumes, information reduction, and RAID-HA. The Compuverde technologies (file protocols and file systems) were integrated into the stack, and the goodness from both technologies was applied across the surround. This means the SMB and NFS services volition do good from data reduction and RAID/HA services.
Some of the features of this integrated approach are:
via SMB and NFS information to provide the aforementioned file information in the same assortment.
Directory snapshots, directory-level metrics
provided past the File System
Global dedupe and compression
for file and block via the existing Purity information reduction and RAID-HA layers.
Access is integrated
into the Purity GUI, CLI, and REST APIs. And then existing Purity concepts like snapshots and deduplication are extended to the file system, and new concepts like managed directories and export policies are added.
Additionally, if yous currently use Pure Storage in your surroundings, in that location won’t be a large learning curve. File services will show up in however you access Purity.
Finally, every bit per usual with Pure Storage, in that location is no actress license and no extra charge for this new feature, you but need to upgrade to the new version of Purity. In that location will be restrictions on which arrays tin host the new file services and file system, as it takes sufficient CPUs and memory to host them. Exist certain to verify your array capabilities, as the smaller arrays will not be bulky enough to run file services or to run file services and cake at the same fourth dimension.
Here are some of the nuts of the NFS file organization beingness offered. The root is always a managed directory, just other managed directories tin can exist created under the root. Purity vi.0 will support up to 500 managed directories per array.
NAS clients volition but run into another directory, although the client won’t have the permissions to remove the managed directory. A managed directory looks similar any normal directory. It will exist visible in the UI, enabling storage admins to manage and monitor space, as well equally apply policies (e.g. export managed directories, take snapshots).
In the diagram higher up, there are 4 managed directories:
users. The directories under
(alan, jon, naveen) are non managed. Infinite can exist managed and monitored on the managed directories. Yet, on the individual subdirectories, such as the ones under the
managed directory, management of the individual subdirectories volition be an aggregate of the
managed directory, as will any policies applied.
It is important to recollect about how you’ll want to organize your file organization. Information technology isn’t possible to convert an ordinary directory into a managed directory. And one time the users start to populate those directories or use them in product, information technology could be difficult and disruptive to make changes. For case, if I wanted the ability to manage, monitor, and apply policies to alan, I’d need to program to go far a managed directory from the beginning.
I now tin run cake and file services from the same Pure FlashArray™. Crawly! Just what are the business organization reasons that drive an organisation to want to await for that option?
Using flash arrays for full general-purpose file share and home directories seem to exist direct-forward use cases. But are there specific workloads or applications where having ane storage arrangement would satisfy multiple architectural requirements?
VDI is one such use case. VDI systems crave stable and reliable operations of block storage. Simply user habitation directories, or where all the users do their piece of work, is usually some sort of file system. How cool would it be to have both storage platforms on the aforementioned system? Surely there are management and low latency benefits that could be realized.
Any type of workload that is primarily a block-based application but has some file system requirements could be a skilful fit. An interesting use instance could be an application like SAP that requires block storage, but then having the log files on a file system, but all the same in the same array.
Information technology makes good sense to have an array with the ability to perform block-based and file-based storage. What volition be interesting going forward is if File Services will be offered throughout the portfolio, peculiarly in Pure Storage’due south cloud offerings.
Additionally, while there are employ cases similar VDI that seem like a slam dunk for this type of architecture, will the add-on of file services unlock some of the newer applications that are yet to be written for the Edge and IoT devices?
It will be neat to run across how this is used by developers in the future.