Cloud-native global file system with multi-site support using push classes
A technique for data sharing among multiple filers that share a volume in a private or public cloud object store is implemented. In this approach, a mechanism is provided to enable a local filer to determine whether other filers that are sharing the volume have a consistent view of new data being written to the cloud object store by the local filer. The begins by associating together a collection of one or more files in a “push class.” On demand, a push operation for the push class is initiated on the local filer. Preferably, the push is managed according to one or more push criteria associated with the push class. Typically, the push operation pushes file data and metadata associated with the one or more files of the push class in respective phases, with the file data being pushed to the cloud during a first phase and the metadata associated with that file data being pushed during a second phase that follows the first phase. After the push operation completes, a determination is made whether the new version of the file is available at one or more other filers that share the volume.
1. Apparatus associated with a private or public cloud object store in which a volume is being shared among filers across a number of sites, comprising:
computer hardware; and
an application programming interface (API) configured as software executed in the computer hardware, the API responsive to receipt from a first function call from a source filer to issue to one or more target filers a second function call, the apparatus being distinct from the source filer and the one or more target filers, the first function call configured to push from the source filer to each of the one or more target filers a payload, wherein the payload comprises a set of one or more files that satisfy a user-defined criteria of interest, the payload configured to be pushed from the source filer to the one or more target filers distinct from any point-in-time snapshot on the volume, the second function call configured to determine whether a push of the payload has arrived at a particular target filer.
2. The apparatus as described in claim 1 wherein the API is further configured to provide a notification indicating that the payload has arrived at a particular target filer in a consistent manner.
3. The apparatus as described in claim 1 wherein the first function call has an associated timeout.
4. The apparatus as described in claim 1 wherein the second function call has an associated timeout.
5. The apparatus as described in claim 1 wherein the user-defined criteria of interest being defined by one of: a directory pattern to follow, and a temporal constraint.
6. The apparatus as described in claim 1 wherein at least one target filer is located remote from the source filer.
7. The apparatus as described in claim 1 wherein the API is configured in a web-accessible management console.
8. The apparatus as described in claim 1 wherein the snapshot is performed on-demand.
9. The apparatus as described in claim 1 wherein the user-defined criteria of interest are a push class.
10. The apparatus as described in claim 1 wherein file data and metadata associated with the one or more files of the push class are pushed from the source filer in respective phases, with the file data being pushed to the cloud during a first phase and the metadata associated with that file data being pushed during a second phase that follows the first phase.