Abstract: Some examples relate to performing application-defined object logging through a file system journal. In an example, a file system may determine during execution of an operation for an application whether a callback function is specified for the operation. In response to the determination, file system may invoke the callback function. File system may receive an object defined by the application. File system may link a copy of the object with a file system transaction associated with the operation in a journal of file system. File system may determine whether file system transaction is committed. In response to the determination, file system may write a copy of the object from the journal to an event log file. File system may allow the application to determine whether file system transaction is committed by enabling access to the event log file.

Abstract: In one example, a request for storage of an extended attribute (EA) of a file system object is received. A storage location for the EA is determined from a plurality of storage locations, based on one or more characteristics of the EA, the plurality of storage locations including an inode, a first storage file accessible by a first B+ tree, and a second storage file accessible by a second B+ tree. The EA is accordingly stored in the determined storage location.

Abstract: In example implementations, a computing node is provided. The computing node includes a containerized application, a local storage partition, and a controller. A portion of the local storage partition is associated with portions of other local storage partitions to form a global cache. The controller executes the containerized application, receive an indication from a second computing node that the containerized application is being migrated, transfers data associated with the containerized application to the second computing node via the global cache.

Abstract: Some examples relate to performing application-defined object logging through a file system journal. In an example, a file system may determine during execution of an operation for an application whether a callback function is specified for the operation. In response to the determination, file system may invoke the callback function. File system may receive an object defined by the application. File system may link a copy of the object with a file system transaction associated with the operation in a journal of file system. File system may determine whether file system transaction is committed. In response to the determination, file system may write a copy of the object from the journal to an event log file. File system may allow the application to determine whether file system transaction is committed by enabling access to the event log file.

Abstract: In one example, a request for storage of an extended attribute (EA) of a file system object is received. A storage location for the EA is determined from a plurality of storage locations, based on one or more characteristics of the EA, the plurality of storage locations including an inode, a first storage file accessible by a first B+ tree, and a second storage file accessible by a second B+ tree. The EA is accordingly stored in the determined storage location.