Abstract: Executing functions in serverless platforms leveraging metadata is disclosed. Embodiments of the invention related to using metadata when placing and/or executing functions. The metadata includes request metadata, container or function metadata, node metadata, and/or data metadata. The metadata allows a function to be placed and executed in a manner that accounts for user intent, container requirements, node resources, and data location. Functions can be placed across different serverless platforms. Once the metadata is evaluated and a location is selected, a function is placed and executed at the selected location.

Abstract: One example method includes receiving a data event notification, retrieving data to which the data event notification pertains, analyzing the data, based on the analyzing, generating metadata pertaining to the data, and transmitting the metadata to a repository. These operations may be performed automatically in response to receipt of the data event notification. The data event notification may likewise be generated automatically in response to implementation of the data event, which may be any of a data create, read, update, or delete, operation.

Abstract: One example method includes data orchestration. Data sets are available to users in an online marketplace. Based on requests for data sets, other data sets may be recommended. The recommended data sets are moved or copied to recommended locations. This ensures that the data sets are available to the user more quickly if subsequently requested.

Abstract: One example method includes, at a computer system that is an element of a network, intercepting stream elements of a stream associated with the computer system, selecting one or more of the stream elements, analyzing the selected stream elements, and based on the analyzing, emitting the selected stream elements to an external, query-able, storage entity that is external to the computer system. The metadata emitted to the storage entity may further include metadata that was natively generated at the computer system.

Abstract: One example method includes receiving, by an administrator from a user computer system, a query identifying content the user wants to access, and the administrator and user computer system are elements of a system that includes a group of networked user computer systems, parsing, by the administrator, the query to identify metadata included in the query, identifying, by the administrator, any content of a datastore that matches the metadata, packaging, by the administrator, the datastore content into a virtual filesystem, and exposing, by the administrator, the virtual filesystem to one of the user computer systems.

Abstract: One example method includes declaring a management requirement for a collection of data, defining metadata that embodies the requirement, associating the management requirement with the collection of data, and performing a filesystem operation, with respect to the collection of data, based on the metadata. The declaring and defining operations may be performed by an administrator operating in a centralized datastore that includes a metadata repository, and the defined metadata may be stored in the metadata repository.

Abstract: One example method includes extracting content metadata from data, storing the content metadata in a data catalogue, receiving at the data catalogue, from a user, a request to access the data, transmitting, by the data catalogue to a security service provider, an access request that includes the extracted content metadata and metadata relating to the access request, accessing, by the security service provider, identity metadata concerning an identity of the user, and a data access policy, and transmitting, by the security service provider to the data catalogue, a decision as to whether or not access can be granted to the data, and the decision is based on the data access policy, the identity metadata, and the metadata in the access request.

Abstract: One example method includes selecting items to be repatriated from a cloud site to an on-premises site, and the items include a workload and a data set accessed by the workload, transmitting a repatriation request from the on-premises site to the cloud site, and the repatriation request identifies the selected items, receiving, by the on-premises site from the cloud site, a compressed data set which includes the data set in compressed form, receiving, by the on-premises site from the cloud site, a compressed workload which includes the workload in compressed form, and the compressed workload and the compressed data set have been compressed with a compression algorithm automatically selected based on content, and/or context, of data in the data set, decompressing, at the on-premises site, the compressed data set and the compressed workload, and deploying the decompressed data set and the decompressed workload locally at the on-premises site.

Abstract: One example method includes receiving stream data batches at a client node. The client node determines if the stream data batches are compressible. For the compressible stream data batches, a request is sent to a server node for an on-demand stream compression service, the request including an indicator of a stream data type for the compressible data batches. The on-demand stream compression service is deployed and launched at the client node. The on-demand stream compression service includes a compressor pool of compressors that are able to compress the stream data type of the compressible stream data batches. A compressor of the compressor pool is selected and used to compress the compressible stream data batches. The compressed stream data batches are sent to the server node.

Abstract: One example method includes receiving, by a graph proxy, an event from an event generator, and the event includes information about an IO and information about data affected by the IO, comparing, by the graph proxy, the data to a schema, when the data is determined by the graph proxy to map to the schema, identifying, by the graph proxy, a rule that is associated with the event, and the rule specifies performance of an action when a condition is met, and when the condition is met, performing, by the graph proxy, the action, and the action is performed with respect to a graph.

Abstract: A compression system is disclosed. A compression service removes compression responsibilities from an application. The compression system can deploy virtual network engines to locations near the applications. The virtual network engines compress the data using a compressor selected from multiple compressors. The compressed data can then be transmitted, decompressed, and delivered to the destination.

Abstract: One example method includes file specific compression selection. Compression metrics are generated for a chunk of a file. Using a set of training data, the compression metrics are corrected using a correction factor to determine estimated file compression metrics. A compressor is then selected to compress the file based on at least the estimated file compression metrics.

Abstract: One example method includes identifying an IO event comprising an IO made by a customer against a service hosted at an XaaS platform, and the IO event is associated with IO event metadata generated by the service, associating the IO event metadata with a billable customer operation, analyzing the IO event metadata and, based on the analyzing, associating the IO event with the customer, and generating a customer bill based on the associating of the IO event metadata with the billable customer operation, and based on the associating of the IO event with the customer.

Abstract: One example method includes file specific compression selection. Compression metrics are generated for a chunk of a file using a reference compressor. Compression metrics for other compressors are determined from the metrics of the reference compressor. A compressor is then selected to compress the file.

Abstract: One example method includes injecting processing into sessions including IO sessions. Events in a file system are intercepted and processed. During processing, policies may be applied to the events. Some of the policies are triggered such that external actions or processing is applied to the event. Once the actions have been performed, the event may be processed by the file system.

Abstract: One example method includes integrating user space applications with kernel space events including primitives. The events are intercepted in kernel space and processed in user space. The events can be stored in a session cache that allows a holistic view of behavior to be determined with regard to resources of the computing system. The events in the session cache can be correlated to user or process behavior by provided a time-based view of the events.

Abstract: One example method includes data orchestration. Data sets are available to users in an online marketplace. Based on requests for data sets, other data sets may be recommended. The recommended data sets are moved or copied to recommended locations. This ensures that the data sets are available to the user more quickly if subsequently requested.

Abstract: One example method includes file specific compression selection. Compression metrics are generated for a chunk of a file using a reference compressor. Compression metrics for other compressors are determined from the metrics of the reference compressor. A compressor is then selected to compress the file.

Abstract: One example method includes receiving a request from a user to access data stored in a filesystem, in response to the request, retrieving metadata of the data and metadata of the user, validating the metadata of the data and the metadata of the user against a data access rule, and granting the user access to the data upon successful validation of the metadata of the data and the metadata of the user.

Abstract: One example method includes monitoring a data access pattern, registering a data access request directed to data, comparing metadata associated with the data access request to a rule, based on a result of the comparing, sending a trigger to a graph service, and using information in the trigger to generate a visual representation of the data access request, wherein the visual representation indicates an extent to which the data access request is considered to constitute a potential threat to the data.