Abstract: Disclosed herein are system, method, and computer program product embodiments for multi-cluster distribution. In some embodiments, a server on a primary computing cluster receives an update to an object stored on the primary computing cluster and to be implemented by a secondary computing cluster. Furthermore, the server receives a request to distribute the object to the secondary computing cluster. The server further retrieves the object based on an object identifier or an identifier of the secondary computing cluster. Moreover, the server identifies the secondary computing cluster based on the object identifier or the identifier of the secondary computing cluster. The server then distributes the object to the secondary computing cluster via a persistent connection.

Abstract: A storage appliance arranges snapshot data and snapshot metadata into different structures, and arranges the snapshot metadata to facilitate efficient snapshot manipulation, which may be for snapshot management or snapshot restore. The storage appliance receives snapshots according to a forever incremental configuration and arranges snapshot metadata into different types of records. The storage appliance stores these records in key-value stores maintained for each defined data collection (e.g., volume). The storage appliance arranges the snapshot metadata into records for inode information, records for directory information, and records that map source descriptors of data blocks to snapshot file descriptors. The storage appliance uses a locally generated snapshot identifier as a key prefix for the records to conform to a sort constrain of the key-value store, which allows the efficiency of the key-value store to be leveraged.

Abstract: A storage appliance arranges snapshot data and snapshot metadata into different structures, and arranges the snapshot metadata to facilitate efficient snapshot manipulation, which may be for snapshot management or snapshot restore. The storage appliance receives snapshots according to a forever incremental configuration and arranges snapshot metadata into different types of records. The storage appliance stores these records in key-value stores maintained for each defined data collection (e.g., volume). The storage appliance arranges the snapshot metadata into records for inode information, records for directory information, and records that map source descriptors of data blocks to snapshot file descriptors. The storage appliance uses a locally generated snapshot identifier as a key prefix for the records to conform to a sort constrain of the key-value store, which allows the efficiency of the key-value store to be leveraged.

Abstract: Disclosed herein are system, method, and computer program product embodiments for multi-cluster boot-strapping. In some embodiments, a server residing on a primary computing cluster receives a first request to establish a temporary connection between the primary computing cluster and a secondary computing cluster. The server establishes the temporary connection between the primary computing cluster and the secondary computing cluster using the first set of credentials. Furthermore, the server receives a second request to establish a persistent connection between the primary computing cluster and the secondary computing cluster. The server establishes the persistent connection by transmitting a third request comprising the configuration settings to the secondary computing cluster thereby causing the secondary computing cluster to generate a second set of credentials corresponding to the primary computing cluster. The server receives and stores the second set of credentials.

Abstract: Disclosed herein are system, method, and computer program product embodiments for role-based access control in multi-tenancy environments using cloud-native objects. An embodiment operates by executing an application in a cluster. The embodiment creates roles corresponding to a user or group of users. The embodiment defines a set of permissions for the roles. The embodiment binds the roles to native objects in a cloud orchestrator based on the set of permissions for the roles. The embodiment receives a first request from a user to log in. The embodiment transmits a request to authenticate the user. The embodiment receives a list of a set of permissions for the user. The embodiment causes a display of system assets on a user interface of a client device based on the list of the set of permissions for the user.

Abstract: Disclosed herein are system, method, and computer program product embodiments for multi-cluster distribution. In some embodiments, a server on a primary computing cluster receives an update to an object stored on the primary computing cluster and to be implemented by a secondary computing cluster. Furthermore, the server receives a request to distribute the object to the secondary computing cluster. The server further retrieves the object based on an object identifier or an identifier of the secondary computing cluster. Moreover, the server identifies the secondary computing cluster based on the object identifier or the identifier of the secondary computing cluster. The server then distributes the object to the secondary computing cluster via a persistent connection.

Abstract: Disclosed herein are system, method, and computer program product embodiments for multi-cluster access. In some embodiments, the server receives a first request to bind one or more cluster roles associated with a user to each of one or more secondary computing clusters. The server binds the user's credentials with the one or more cluster roles corresponding to each of one or more secondary computing clusters. Furthermore, the server receives a second request for providing the user access to the primary computing cluster. Moreover, the server receives a third request from the user interface intended for at least one secondary computing cluster. The server forwards the third request to the at least one secondary computing cluster while impersonating at least one cluster role of the one or more cluster roles corresponding to the at least one secondary computing cluster.

Abstract: A packet forwarding network may include spine and leaf switches that forward network traffic between end hosts. The packet forwarding network may be implemented on multiple network racks in a rack-based system. A controller may control the underlying spine and leaf switches to form on-premise virtual private cloud (VPC) resources. In particular, the controller may form enterprise VPC (EVPC) tenants, each having a virtual router that performs routing between different segments within the corresponding EVPC tenant. The different segments may separately include web, application, and database servers, as end hosts. The controller may form a system VPC tenant having a virtual system router that performs routing between different EVPC tenants. A segment in an internal VPC tenant formed by the controller and/or an external VPC tenant formed by the controller may provide external network access for one or more of the EVPC tenants.

Abstract: A packet forwarding network may include spine and leaf switches that forward network traffic between end hosts. The packet forwarding network may be implemented on multiple network racks in a rack-based system. A controller may control the underlying spine and leaf switches to form on-premise virtual private cloud (VPC) resources. In particular, the controller may form enterprise VPC (EVPC) tenants, each having a virtual router that performs routing between different segments within the corresponding EVPC tenant. The different segments may separately include web, application, and database servers, as end hosts. The controller may form a system VPC tenant having a virtual system router that performs routing between different EVPC tenants. A segment in an internal VPC tenant formed by the controller and/or an external VPC tenant formed by the controller may provide external network access for one or more of the EVPC tenants.

Abstract: A storage appliance arranges snapshot data and snapshot metadata into different structures, and arranges the snapshot metadata to facilitate efficient snapshot manipulation, which may be for snapshot management or snapshot restore. The storage appliance receives snapshots according to a forever incremental configuration and arranges snapshot metadata into different types of records. The storage appliance stores these records in key-value stores maintained for each defined data collection (e.g., volume). The storage appliance arranges the snapshot metadata into records for inode information, records for directory information, and records that map source descriptors of data blocks to snapshot file descriptors. The storage appliance uses a locally generated snapshot identifier as a key prefix for the records to conform to a sort constrain of the key-value store, which allows the efficiency of the key-value store to be leveraged.

Abstract: A storage appliance arranges snapshot data and snapshot metadata into different structures, and arranges the snapshot metadata to facilitate efficient snapshot manipulation, which may be for snapshot management or snapshot restore. The storage appliance receives snapshots according to a forever incremental configuration and arranges snapshot metadata into different types of records. The storage appliance stores these records in key-value stores maintained for each defined data collection (e.g., volume). The storage appliance arranges the snapshot metadata into records for inode information, records for directory information, and records that map source descriptors of data blocks to snapshot file descriptors. The storage appliance uses a locally generated snapshot identifier as a key prefix for the records to conform to a sort constrain of the key-value store, which allows the efficiency of the key-value store to be leveraged.

Abstract: Various embodiments are generally directed an apparatus and method for receiving a recovery point objective for a workload, the recovery point objective comprising an amount of time in which information for the workload will be lost if a failure occurs, and determining a service level objective for a replication transfer based on the recovery point objective, the replication transfer to replicate information on a destination node to maintain the recovery point objective. Various embodiments include dynamically controlling one or more resources to replicate the information on the destination node based on the service level objective and communicating information for the replication transfer from the source node to the destination node.

Abstract: A storage appliance arranges snapshot data and snapshot metadata into different structures, and arranges the snapshot metadata to facilitate efficient snapshot manipulation, which may be for snapshot management or snapshot restore. The storage appliance receives snapshots according to a forever incremental configuration and arranges snapshot metadata into different types of records. The storage appliance stores these records in key-value stores maintained for each defined data collection (e.g., volume). The storage appliance arranges the snapshot metadata into records for inode information, records for directory information, and records that map source descriptors of data blocks to snapshot file descriptors. The storage appliance uses a locally generated snapshot identifier as a key prefix for the records to conform to a sort constrain of the key-value store, which allows the efficiency of the key-value store to be leveraged.

Abstract: A remote data storage system for providing one or more mobile devices with a remote data store. The system may include a cloud platform with a storage management application and a data store. A mobile storage application may operate on a mobile device to enable the mobile device to interact with the storage management application. The storage management application may condition data for exchange between the mobile device and the data store. The conditioning of data may include the replacement of duplicate data subsets with references to equivalent data subsets. Other embodiments are described and claimed.

Abstract: Various embodiments are generally directed an apparatus and method for receiving a recovery point objective for a workload, the recovery point objective comprising an amount of time in which information for the workload will be lost if a failure occurs, and determining a service level objective for a replication transfer based on the recovery point objective, the replication transfer to replicate information on a destination node to maintain the recovery point objective. Various embodiments include dynamically controlling one or more resources to replicate the information on the destination node based on the service level objective and communicating information for the replication transfer from the source node to the destination node.