github.com/NVIDIA/aistore@v1.3.23-0.20240517131212-7df6609be51d/docs/_posts/2024-03-30-ais-on-nfs.md (about)

     1  ---
     2  layout: post
     3  title:  "AIS on NFS"
     4  date:   March 30, 2024
     5  author: Alex Aizman
     6  categories: aistore nfs
     7  ---
     8  
     9  > This is an excerpt from an article that I posted at storagetarget.com. The full text can be found at:
    10  
    11  * [https://storagetarget.com/2024/03/30/ais-on-nfs](https://storagetarget.com/2024/03/30/ais-on-nfs)
    12  
    13  -------------------------------------------------------
    14  
    15  <...>
    16  
    17  AIStore will now aggregate not only disks (or, not just disks) but also directories. Any file directories – assuming, of course, they are not nested. Any number of regular file directories that, ostensibly, may not even have underlying block devices.
    18  
    19  Here’s what has happened:
    20  
    21  ![Upcoming](/assets/mountpaths/mpl-transition.png)
    22  
    23  On the left and the right: an AIS cluster sandwiched between two interfaces often referred to as frontend and backend. Cluster provides the former (which inevitably entails [S3](/docs/s3compat.md) but not only), and utilizes the latter to perform fast-tiering function across vendors and solutions.
    24  
    25  ## TL;DR
    26  
    27  Long story short, the upcoming v3.23 removes the requirement that every aistore mountpath is a separate filesystem (“FS” above) that owns a block device. In the past, this block device would have to present itself at a node’s startup and wouldn’t be permitted to be used by (or shared with) any other mountpath.
    28  
    29  Not anymore, though. Planned for late April or May 2024, the release will introduce a separate indirection called “mountpath label.”