Recent Discussions
Ask Us Everything about Object Storage
💬 Get ready for our February 2026 edition of Ask Us Everything, this Friday, February 20th at 9 AM Pacific. This month is all about Object Storage. If you have a burning question, feel free to ask it here early and we'll add it to the list to answer tomorrow. Or if we can't get it answered live, our Pure Storage experts can follow up here. Karthik Srinivasan, Flashman​ & dpoorman​ ​ are the experts answering your questions during the conversation and here on the community. See you this Friday! (Oh, and if you haven't registered yet, there's still time!) Or, check out this self-serve resource: Object Storage Webinar EDIT: Thanks for joining in! If you have additional burning questions and comments, leave them in the comments below for the team!General Availability of Purity//FB 4.5.6
We are excited to announce the general availability of Purity//FB 4.5.6 Purity 4.5.6 Release Highlights Introducing Purity//FB 4.5.6, designed to simplify managing a fleet of systems, optimize geographically distributed workflows, and expand the environments that can deploy FlashBlade. Key highlights include: Fusion for FlashBlade: Support for FlashBlade is available now on Pure Fusion, enabling FlashBlade to create, or join a fleet of arrays, simplifying deployments, scaling, and management of data across both FlashArrays and FlashBlades. Pure Fusion now also delivers a single consistent interface for deploying file and object workloads. Rapid Replicas: The remote fetching and caching capability enables file data to be distributed efficiently and allows collaborative development across multiple Data centers, remote sites or, increasingly, workloads in the cloud. QoS ceiling for File System: Purity//FB adds support for creating custom QoS policies defining ceiling limits for IOPS and bandwidth per filesystem. Storage administrators can leverage QoS ceiling to ensure predictable performance and mitigate resource contention. Legal Hold support for File System: Allows users to apply legal hold on files, folders and sub-folders. Once applied the file/folder can’t be deleted by the user until the legal hold is removed. This capability supports compliance for enterprises in regulated industries by providing mandatory legal hold capabilities for files and folders. 18.6TB QLC DFM Support for S100: provides lower entry-point (130TB raw) for customers to experience the power and goodness of FlashBlade//S and also provides heterogeneous expansion capability on //S100 systems with 18.6TB and 37.5TB DFMs. FlashBlade//S500 with NVIDIA DGX SuperPOD: Purity//FB 4.5.6 introduces the integration of FlashBlade with NVIDIA DGX SuperPOD to provide a high-performance, scalable solution for AI and other high-performance computing applications. Object Secure Token Service: Secure Token Services helps FlashBlade to integrate with Single Sign ON (SSO) architectures (Federated Identity models). It simplifies management of user and group access to FlashBlade resources like buckets and objects. Increased Object Account and Bucket Scale: Scalability in FlashBlade Object storage is enhanced with the latest release. FlashBlade will be able to support up to 30K replication relations and up to 5K remote credentials while setting up replication. Object Active-Active Replication: Beginning with Purity//FB 4.5.6, Active-Active Replication between multi-site writable buckets is now Generally Available. No qualification document or approval for setting up replication is needed. However, active-active replication of classic buckets still requires PM approval. Please contact your Pure Storage Representative for assessment and approval for classic buckets. We recommend using multi-site writable buckets for all scenarios including single site deployments. Capacity Consolidation on FB//S & FB//E: provides support for upgrading smaller capacity DFMs to larger capacity DFMs in FlashBlade//S and FlashBlade//E systems. TLS Policy and Ciphers: TLS Policy allows customers to create and maintain custom TLS policies & Ciphers for FlashBlade network interfaces. TLS policy helps centralize management and controls for all inbound network traffic. The policy helps narrow down attack surface and vulnerability exploitation for transports over the network. Updates to Zero Move Tiering (ZMT): FlashBlade//ZMT system adds support for 1,2,3 and 4 DFM per blade configs in 1S:1E offering. New SKUs offer low starting capacity points for Hot storage class and large Cold archival storage. This indirectly improves TCO for customers with predictable performance and cost efficiency. ABE Support for File System: Access-based Enumeration (ABE) allows administrators to hide objects (files and folders) from users who don’t have permissions (Read or List) on a network shared folder in order to access them. MMC Support for File System: Administrators can now go into Microsoft Management Console (MMC) to list open inaccessible files and choose to close them. The full list of new features and enhancements can be found in the Purity//FB 4.5.6 Release Notes.
Flashblade & Ansible collection
Hello community, We are facing some issues with our FlashBlade when provisioning policies with Ansible. We have updated all the components (py-pure-client and the collection), and we are failing on a simple policy deployment. - name: Test purestorage.flashblade.purefb_policy: name: "filesystem_export_policy" enabled: True policy_type: "nfs" at: True client: "mynfsexport.flashblade.local" secure: True security: "sys" permission: "rw" access: "no-squash" fb_url: "{{ fb_host }}" api_token: "{{ fb_api_token }}" The complete stack trace is : The full traceback is: Traceback (most recent call last): File "/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py", line 107, in <module> _ansiballz_main() File "/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py", line 99, in _ansiballz_main invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS) File "/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py", line 47, in invoke_module runpy.run_module(mod_name='ansible_collections.purestorage.flashblade.plugins.modules.purefb_policy', init_globals=dict(_module_fqn='ansible_collections.purestorage.flashblade.plugins.modules.purefb_policy', _modlib_path=modlib_path), File "<frozen runpy>", line 226, in run_module File "<frozen runpy>", line 98, in _run_module_code File "<frozen runpy>", line 88, in _run_code File "/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py", line 4233, in <module> File "/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py", line 4008, in main File "/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py", line 2392, in update_nfs_policy AttributeError: 'ErrorResponse' object has no attribute 'items' fatal: [localhost]: FAILED! => { "changed": false, "module_stderr": "Traceback (most recent call last):\n File \"/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py\", line 107, in <module>\n _ansiballz_main()\n File \"/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py\", line 99, in _ansiballz_main\n invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n File \"/home/user/.ansible/tmp/ansible-tmp-1778656887.1852276-3067455-48057529014464/AnsiballZ_purefb_policy.py\", line 47, in invoke_module\n runpy.run_module(mod_name='ansible_collections.purestorage.flashblade.plugins.modules.purefb_policy', init_globals=dict(_module_fqn='ansible_collections.purestorage.flashblade.plugins.modules.purefb_policy', _modlib_path=modlib_path),\n File \"<frozen runpy>\", line 226, in run_module\n File \"<frozen runpy>\", line 98, in _run_module_code\n File \"<frozen runpy>\", line 88, in _run_code\n File \"/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py\", line 4233, in <module>\n File \"/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py\", line 4008, in main\n File \"/opt/tmp/tmp/ansible_purestorage.flashblade.purefb_policy_payload_xaietsz7/ansible_purestorage.flashblade.purefb_policy_payload.zip/ansible_collections/purestorage/flashblade/plugins/modules/purefb_policy.py\", line 2392, in update_nfs_policy\nAttributeError: 'ErrorResponse' object has no attribute 'items'\n", "module_stdout": "", "msg": "MODULE FAILURE: No start of json char found\nSee stdout/stderr for the exact error", "rc": 1 } If the policy is already set, the playbook runs perfectly fine. The problem occurs when a new policy is injected. However, we have to install the collection from GitHub. It seems that the artifact built and installed by Ansible Galaxy is not correct. Some commits are not propagated. For example, with the FlashBlade collection 1.24 (installed from Galaxy), we have: >>> from pypureclient.flashblade import ( ... PolicyRuleObjectAccessCondition, ... PolicyRuleObjectAccessPost, ... PolicyRuleObjectAccess, ... NfsExportPolicy, ... NfsExportPolicyRule, ... Policy, ... PolicyPatch, ... PolicyRule, ... SmbSharePolicyRule, ... SmbSharePolicy, ... SmbClientPolicyRule, ... SmbClientPolicy, ... ObjectStoreAccessPolicyPost, ... NetworkAccessPolicy, ... NetworkAccessPolicyRule, ... WormDataPolicy, ... ) Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/home/user/conda/envs/ansible/lib/python3.12/site-packages/pypureclient/flashblade/__init__.py", line 40, in __getattr__ raise ImportError(f'module {__package__} has no attribute {name}') ImportError: module pypureclient.flashblade has no attribute PolicyPatch We have compared the archive from GitHub and there are many differences with the upstream collection code. To help, find my my env package : Package Version ----------------- ----------- annotated-types 0.7.0 ansible-core 2.18.5 bcrypt 5.0.0 certifi 2026.4.22 cffi 2.0.0 cryptography 44.0.0 dnspython 2.8.0 invoke 3.0.3 Jinja2 3.1.4 MarkupSafe 2.1.1 packaging 24.1 paramiko 5.0.0 pip 24.2 py-pure-client 1.88.0 pycparser 2.22 pydantic 2.13.4 pydantic_core 2.46.4 PyJWT 2.12.1 PyNaCl 1.6.2 python-dateutil 2.9.0.post0 PyYAML 6.0.2 resolvelib 1.0.1 setuptools 75.8.2 six 1.17.0 typing_extensions 4.15.0 typing-inspection 0.4.2 urllib3 2.7.0 wheel 0.45.0 And our flashblades are running the Purity//FB 4.6.9. If anyone has a lead to help us get our Ansible back up and running, I thank them in advance. We appreciate your help. MatthAnnouncing the General Availability of Purity//FB 4.7.10 LLR
We are happy to announce the general availability of 4.7.10, the first Long-Life Release (LLR) of the 4.6/4.7 line, providing long-term maintenance of the 4.6 feature set with consistency in capabilities, user experience, and interoperability. For more detailed information about bug fixes and security updates included in each release, see the release notes. Highlights The 4.7 LLR adds many new features and improvements for customers upgrading from the 4.5 LLR: AI and high-performance workload acceleration Major gains for AI, HPC, and other demanding unstructured workloads through higher-performance platform options, increased bandwidth, better read/write concurrency, and S3 over RDMA, provide customers faster time to results, better GPU utilization, and more value from large-scale file and object environments. Lower cost at scale with smarter data placement and efficiency Zero Move Tiering for file and object, larger supported system scale, tenant-level performance controls, and DeepReduce for FlashBlade//E help customers scale capacity more efficiently, improve workload density, and reduce total cost of ownership without adding operational complexity. Stronger security and compliance Important security capabilities including NFS over TLS, mutual TLS, FIDO2 and authentication policy support for SSH, object auditing, and proactive Purity patching, helping customers protect data in flight, strengthen access controls, simplify compliance, and respond faster to risk. Multi-tenancy and service delivery Realms, management access policies, secure multi-tenancy for object, local users and groups, and Fusion workload and preset enhancements give customers stronger isolation, simpler delegated administration, and more consistent service delivery across shared environments and dark sites. Improved observability, resilience, and operations On-box observability, richer protocol and connection statistics, Rapid Replica enhancements, larger-scale file data protection, and hardware-based availability improvements make it easier for customers to troubleshoot faster, protect more data at scale, and run mission-critical environments with greater confidence. This release is supported on the following FlashBlade Platforms: FB//S100, FB//S200 (R1, R2), FB//S500 (R1, R2), FB//ZMT, FB//E, FB//EXA Release recommendations Customers looking for long-term maintenance of the complete 4.6 feature set are encouraged to upgrade to the 4.7 LLR. Customers looking for the latest features as soon as they are available should upgrade to the 4.8 FR. Check out our AI Copilot intelligent assistant for deeper insights into release content and recommendations. EOL schedule The 4.6/4.7 release line is planned to reach End-of-Life (EOL) in April 2029. Links and References Purity//FB 4.7 Release Notes Everpure Product Lifecycle and Support Policies Overview Purity//FB Release and End-of-Life Schedule Purity//FB Release Guidelines FlashBlade Hardware and End-of-Support FlashBlade Capacity and Feature Limits Pure1 Manage AI Copilot
Announcing the General Availability of Purity//FB 4.5.14
We are happy to announce the general availability of 4.5.14, the fifteenth release of the 4.5 Long-Life Release (LLR) line! This LLR line provides long-term maintenance of the complete feature set introduced earlier in the 4.5 release line. For more detailed information about bug fixes and security updates included in each release, see the release notes. UPGRADE RECOMMENDATIONS AND EOL SCHEDULE Customers who are looking for long-term maintenance of the complete 4.5 feature set are encouraged to upgrade to this latest 4.5 LLR. Customers who are looking for continued delivery of all the newest capabilities as soon as they are available should upgrade to the 4.6 Feature Release line. Note, both 3.3 and 4.1 are bridgehead releases, which means any older FlashBlade systems will need to upgrade to 3.3 and then 4.1 before upgrading to 4.5. The 4.5 LLR line will remain active through Q2 2028 before reaching End-of-Life (EOL). HARDWARE SUPPORT This release is supported on the following FlashBladePlatforms: first generation FlashBlade, FB//S100, FB//S200 (R1), FB//S500 (R1), and FB//E. LINKS AND REFERENCES Purity//FB 4.5 Release Notes Purity//FB Release and End-of-Life Schedule Purity//FB Release Guidelines FlashBlade Hardware and End-of-Support FlashBlade Capacity and Feature Limits On Box Diagnostic landing page
