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 they are stored on the file system.
- CES Swift Object protocol feature is not supported from IBM Storage Scale 5.2.0 onwards.
- IBM Storage Scale 5.1.8 is the last release that has CES Swift Object protocol.
- IBM Storage Scale 5.2.0 will tolerate the update of a CES
node from IBM Storage Scale 5.1.8.
- Tolerate means:
- The CES node will be updated to 5.2.0.
- Swift Object support will not be updated as part of the 5.2.0 update.
- You may continue to use the version of Swift Object protocol that was provided in IBM Storage Scale 5.1.8 on the CES 5.2.0 node.
- IBM will provide usage and known defect support for the version of Swift Object that was provided in IBM Storage Scale 5.1.8 until you migrate to a supported object solution that IBM Storage Scale provides.
- Tolerate means:
- Please contact IBM for further details and migration planning.
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.
-
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
It is assumed that the object is configured over the /ibm/gpfs0 file system
with the default object 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.