Pure Storage, Inc.

Symantec Corporation

Taher Vohra

Naveen Neelakantam

Luis Pablo Pabón

Xiaohui Wang

John Colgrove

Ronald S Karr

Marco Sanvido

Mark L McAuliffe

Andrew Kleinerman

Ethan L Miller

Neil A Vachharajani

Boris Feigin

Benjamin Scholbrock

Svitlana Tumanova

Robert H Lee

Virendra Prakashaiah

Anne Cesa Klein

Richard A Hankins

Matthew Paul Fay

Abhay Kumar Singh

Patrick East

Andrew R Bernat

Par Botes

Ivan Jibaja

Patrick D Lee

Lawrence Mertes

Srikant Sharma

Matthew Conover

Gopal Sharma

Michael Tyler Richardson

Prakash Darji

Dharmesh Shah

Robert Warren Perry

Andrew Sillifant

Arun Rokade

Geeta Gharpure

Frank Tuzzolino

Grizel Lopez

Sameer Majahan

Kelvie Wong

Utilizing a non-repeating identifier to encrypt data, including: receiving a request to write data to a storage device; selecting a segment-offset pair where the data will be stored, where the selected segment-offset pair is unique to every other segment-offset pair utilized during the lifetime of the storage device; and encrypting the data in dependence upon an identifier of the segment-offset pair.

Encrypting data using non-repeating identifiers

An illustrative method includes determining, by a monitoring system based on an attribute model of a dataset stored within a storage system, that one or more data items in the dataset are noncompliant with a compliance ruleset, wherein one or more data attributes of a data item in the dataset includes one or more of a data type of the data item, an encryption information of the data item, an accessibility of the data item, a retention policy of the data item, or an operation log configuration associated with the data item; determining, by the monitoring system based on the one or more data items being noncompliant with the compliance ruleset, a compliance level of the dataset with the compliance ruleset; and performing, by the monitoring system based on the compliance level of the dataset satisfying a compliance level threshold, an operation with respect to the dataset.

Attribute model-based compliance monitoring of data stored in a storage system

Self-tuning clusters for resilient microservices, including: receiving, by a services orchestrator within a cloud-computing environment and from a plurality of cloud computing instances, respective latency measurements corresponding to respective control plane operations directed to a shared resource of the plurality of cloud computing instances; determining, based on a current timeout value and on the respective latency measurements from the plurality of cloud computing instances, an updated timeout value for the shared resource; and providing, to each of the plurality of cloud computing instances, the updated timeout value for the shared resource.

Orchestrating self-tuning for cloud storage

Systems and methods for orchestrating coordinated snapshots across distinct storage environments are disclosed. The methods include steps for determining, for storage systems storing portions of a dataset, that a local checkpoint at a storage system of the storage systems meets dependency requirements for a coordinated checkpoint of the dataset relative to another local checkpoint at another storage system of the storage systems while storage operations are being applied to the dataset, and based on the determination, orchestrating the coordinated checkpoint.

Orchestrating coordinated snapshots across distinct storage environments

A storage system, associated with a container system, may be configured to perform a method that includes: providing, by a storage system, storage services to a container system; determining, by the storage system and based on the providing the storage services to the container system, a potential security threat; and performing, by the storage system, a remedial action based on the potential security threat.

Storage system based threat detection and remediation for containers

An illustrative method includes receiving, by a container storage interface (CSI) filter driver executing on a node of a cluster managed by a container orchestrator, a request to deploy a containerized application; selecting, by the CSI filter driver based on one or more attributes of the containerized application, a storage system from a plurality of storage systems attached to a plurality of clusters managed by the container orchestrator; and transmitting, by the CSI filter driver, a command to a CSI driver executing on a node of a cluster to which the storage system is attached, the cluster included in the plurality of clusters, the command configured to direct the CSI driver to provision a volume on the storage system for use with the containerized application.

Container storage interface filter driver-based determination of optimal storage system to provide storage for a containerized application deployment

Non-disruptively moving a storage fleet control plane, including deploying, on an edge device, one or more agents that are managed by a control plane residing in a cloud computing environment; mediating one or more API requests, generated by the control plane, directed to the one or more agents on the edge device; and migrating, in response to a first condition, the control plane to the edge device.

Non-disruptively moving a storage fleet control plane

An illustrative method includes receiving, by a container storage interface (CSI) filter driver, a request provided by a source for a CSI driver associated with a storage system to perform a control plane operation with respect to the storage system, wherein the CSI filter driver and the CSI filter execute on a node of a cluster managed by a container orchestrator, and wherein the storage system is configured to store data associated with one or more containerized applications executing on the node; performing, by the CSI filter driver in response to receiving the request, an access control operation with respect the request; and allowing, by the CSI filter driver, the CSI driver to perform the control plane operation when the access control operation determines that the source is authorized to initiate the control plane operation.

Container storage interface filter driver-based security for a storage system

A storage system, associated with a container system, may be configured to perform a method that includes: providing, by the storage system to a container operating within a container system, one or more storage services; determining, by the storage system, an interruption to the one or more storage services; and providing, based on the interruption and from the storage system to a container orchestrator for the container system, an alert associated with the container.

Storage system based monitoring and remediation for containers

An illustrative method may include passing, by a container storage interface (CSI) filter driver, requests received by way of a node agent to a CSI driver associated with a storage system, the requests comprising requests for the CSI driver to perform control plane operations with respect to the storage system, wherein the node agent, the CSI filter driver, and the CSI filter all execute on a node of a cluster managed by a container orchestrator, and wherein the storage system is configured to store data associated with one or more containerized applications executing on the node; identifying, by the CSI filter driver based on the requests, attributes associated with the control plane operations; determining, by the CSI filter driver based on the attributes, a usage profile associated with the storage system; and performing, by the CSI filter driver based on the usage profile, an optimization operation.

Container storage interface filter driver-based optimization of a storage system

An illustrative method includes a storage-aware serverless function management system determining a status of a serverless system that implements one or more serverless functions configured to access one or more components of a storage system, determining a utilization of the storage system, and requesting that the storage system adjust storage of data in the storage system based on the status of the serverless system and the utilization of the storage system.

Storage optimization for serverless functions

A storage management system may receive a request for data storage having a set of functions. The storage management system may distinguish, with respect to a storage resource from a pool of storage resources, native functions of the set of functions that are natively supported by the storage resource and non-native functions of the set of functions that are not natively supported by the storage resource. In response to the request, the storage management system may then provide a data storage entity having the set of functions. For example, the data storage entity may be implemented by the storage resource and may be configured to provide the native functions using native functionality of the storage resource and to provide the non-native functions using data path functions. Corresponding systems and methods and computer program products are also disclosed.

Data path functions for data storage

Replicating multiple storage systems utilizing coordinated snapshots, including identifying a replica dataset stored across two or more target storage systems, wherein the replica dataset is a replication target for a source dataset stored across two or more source storage systems; identifying two or more local replicated checkpoints that are replicated from the two or more source storage systems to the two or more target storage systems, wherein two or more local source checkpoints for the two or more local replicated checkpoints are associated with a coordinated source checkpoint for the source dataset; and determining, based on the two or more local replicated checkpoints, a coordinated target checkpoint for the replica dataset.

Replicating multiple storage systems utilizing coordinated snapshots

A container recovery using volumes comprising container images may be performed by a method comprising: determining, by a recovery process and based on node data, to recover a container operating on a first node onto a second node, where a container image is associated with the container; determining, by the recovery process and based on the container image, volume data indicative of a volume comprising the container image; and initiating, by the recovery process and based on the volume data, recovery of the container from the first node onto the second node.

Container recovery using volumes comprising container images

An example method includes detecting a request to store a software build instance within a storage system prior to the software build instance being uploaded to a software registry and initiating, based on the request and while the software build instance is stored within storage system, a scanning operation with respect to the software build instance, the scanning operation configured to check for one or more anomalies associated with the software build instance.

Growing community of inventors

Sunnyvale, CA, United States of America

Taher Vohra