Mounting dynamic endpoints
A client application is provided with a view of a subset of objects within an object store. A REST protocol, REST interface, or API may be used to access the objects. A coupling server may include a filter and a generator. The generator may automatically generate object metadata for newly created files that matches a filter. A client application may mount a drive on a computer based on metadata objects, such as providing a filter on object metadata to view files a user wants to access; or editing, reading, and updating object metadata as a file.
1. A method of accessing from a client application on a client computer a subset of objects from cloud object storage, said method comprising:
a. receiving, at the client computer, a tag input by a human end user;
b. mounting a drive on the client computer via a mount command from the client application which includes a filter specifying the tag;
c. receiving, at a coupling server on a computer via a file protocol, a file access CREATE request from a file system interface of the client application that specifies a file name to write, wherein the tag is stored on the coupling server;
d. generating for a created file, by the coupling server, a new object and new object metadata that matches the tag, said new object and new object metadata being stored in the cloud object storage;
e. returning, by the coupling server, to the client application the file name for the created file allowing the client application to read from or write to the new object in cloud object storage; and
f. providing to the client application a view of the subset of objects within the cloud object storage, wherein the subset of objects in the cloud object storage have associated object metadata matching the tag of the filter that is included in the mount command from the client application; wherein the client application can access the subset of objects within the cloud object storage.
2. A method as recited in claim 1 wherein objects in the cloud object storage are accessed via a REST interface.
3. A method as recited in claim 1 , wherein objects in the cloud object storage are accessed via an API.
4. A method as recited in claim 1 wherein the tag is not communicated to the cloud object storage.
5. A method of accessing from a client application on a client computer a subset of objects from cloud object storage, said method comprising:
receiving, at the client computer, a tag input by a human end user;
mounting a drive on the client computer via a mount command from the client application which includes a filter specifying the tag;
receiving, at a coupling server on a computer via a file protocol, a file access LIST request from a file system interface of the client application that specifies a file specification including list metadata, wherein the tag is stored on the coupling server;
generating, by the coupling server, an object specification from the file specification that includes the tag and the list metadata;
querying, by the coupling server, a search index of the cloud object storage for a list of objects whose metadata matches the object specification;
generating, by the coupling server, a list of file names corresponding to said list of objects;
returning, by the coupling server, to the client application the list of file names; and
providing to the client application a view of the subset of objects within the cloud object storage, wherein the subset of objects in the cloud object storage have associated object metadata matching the tag of the filter that is included in the mount command from the client application; wherein the client application can access the subset of objects within the cloud object storage.
6. A method as recited in claim 5 wherein the tag is not communicated to the cloud object storage.
7. A method of accessing from a client application on a client computer a subset of objects from cloud object storage, said method comprising:
receiving, at the client computer, a tag input by a human end user;
mounting a drive on the client computer via a mount command from the client application which includes a filter specifying the tag;
receiving, at a coupling server on a computer via a file protocol, a file access METADATA EXPOSURE request from a file system interface of the client application that specifies a file name having a predefined label for a requested file, wherein the tag is stored on the coupling server;
creating, by the coupling server, an object specification from the file name of the requested file;
retrieving, by the coupling server, an object and its metadata corresponding to the object specification;
determining, by the coupling server, that the metadata of the object matches the tag;
returning, by the coupling server, to the client application a file handle for a pseudo file that includes the metadata; and
providing to the client application a view of the subset of objects within the cloud object storage, wherein the subset of objects in the cloud object storage have associated object metadata matching the tag of the filter that is included in the mount command from the client application; wherein the client application can access the subset of objects within the cloud object storage.
8. A method as recited in claim 7 wherein the tag is not communicated to the cloud object storage.