File path in unified file and object access
One of the key advantages of unified file and object access is the placement and naming of objects when stored on the file system.
Unified file and object access stores objects following the same path hierarchy as the object's URL. In contrast, the default object implementation stores the object following the mapping given by the ring, and its final file path cannot be determined by the user easily. For example, an object with the following URL is stored by the two systems as follows:
Example object URL: https://swift.example.com/v1/acct/cont/obj
Path in default object implementation: /ibm/gpfs0/object_fileset/o/z1device108/objects/7551/125/75fc66179f12dc513580a239e92c3125/75fc66179f12dc513580a239e92c3125.data
Path in unified file and object access: /ibm/gpfs0/obj_sofpolicy1/s69931509221z1device1/AUTH_763476384728498323747/cont/obj
In this example, it is assumed that the object is configured over the /ibm/gpfs0 file system with the default object located on the object_fileset fileset and the unified file and object access data is located under the obj_sofpolicy1 fileset. s69931509221z1device1 is auto-generated based on the swift ring parameters and AUTH_763476384728498323747 is auto-generated based on the account ID from keystone.