The migration of objects stored in the existing Swift-based Object protocol will depend on whether they're stored as traditional Swift objects or as regular files (Unified File and Object mode). As you may have seen, the objects uploaded to Object protocol will end up on disk in one of two naming formats:
Traditional Swift (hashed path): 8406/605/835811b46b065bf86d4b58601e0f5605/1709142045.35693.data Unified File and Object (regular path): AUTH_12345/buildlogs/2024/jan/20240123.log Objects which are stored in a storage policy defined as Unfiied File and Object mode are stored as regular files and directories. Since they are regular files, the directory which represents the container can be configured as a bucket in the DAS/CES S3 environment. Objects which are stored in the traditional Swift format will need to be downloaded out of Swift and saved as regular files using a cloud migration tool (such as rclone). Once the objects have been downloaded into files, the resulting directory can be set as a bucket in DAS/CES S3. Keep in mind that the DAS/CES S3 interface is S3 only. Applications which use the Swift protocol will need to be converted to use the S3 protocol. -Brian =================================== Brian Nelson IBM Spectrum Scale [email protected] _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at gpfsug.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
