Abstract: A method of evaluating a low voltage (LV) battery system includes collecting parameters of the LV battery system, determining a health of the LV battery system based on one or more health indicators of a plurality of health indicators, and based on determining that the battery system is in an unhealthy condition, identifying a cause of the unhealthy condition based on selection of a set of health indicators. Determining the health includes identifying an enabling condition related to charging or discharging of the LV battery system, selecting a set of health indicators from the plurality of health indicators based on the identified enabling condition, estimating a value of each of the set of health indicators, and determining whether the LV battery system is in a healthy condition or the unhealthy condition based on the collected parameters and the value of each of the set of health indicators.

Abstract: Described herein is a graphics processor comprising a memory interface and a graphics processing cluster coupled with the memory interface. The graphics processing cluster includes a plurality of processing resources. A processing resource of the plurality of processing resources includes a source crossbar communicatively coupled with a register file, the source crossbar to reorder data elements of a source operand and a format conversion pipeline to convert a plurality of input data elements specified by the source operand from a first format of a plurality of datatype formats to a second format of the plurality of datatype formats, the plurality of datatype formats including integer and floating-point formats.

Abstract: Described herein is a graphics processor comprising a memory interface and a graphics processing cluster coupled with the memory interface. The graphics processing cluster includes a multi-lane parallel floating-point unit and a multi-lane parallel integer unit. The multi-lane parallel integer unit includes an integer pipeline including a plurality of parallel integer logic units configured to perform integer compute operations on a plurality of input data elements and a format conversion pipeline including a plurality of parallel format conversion units configured to convert a plurality of input data elements from a first one of a plurality of datatype formats to a second one of the plurality of datatype formats, the plurality of datatype formats including integer and floating-point formats.

Abstract: Methods, systems, and devices for data management are described. A cloud data backup and recovery system may include a destination system and a source system. The destination system may be operable to provide backup and recovery services for the source system. The destination system may communicate a set of push/pull notifications with the source system. Each push/pull notifications may indicate an event is being performed in the source system. The destination system may determine an event is being performed in the source system based on transmitting a push notification or receiving a pull notification, where the push or pull notification may include metadata associated with the event. The destination system may retrieve, from the source system, data that is modified by the event based on the metadata. The destination system may synchronize a database of the destination system based on the data retrieved from the source system.

Abstract: Methods, systems, and devices for data management are described. A cloud data backup and recovery system may include a destination system and a source system. The destination system may be operable to provide backup and recovery services for the source system. The destination system may communicate a set of push/pull notifications with the source system. Each push/pull notifications may indicate an event is being performed in the source system. The destination system may determine an event is being performed in the source system based on transmitting a push notification or receiving a pull notification, where the push or pull notification may include metadata associated with the event. The destination system may retrieve, from the source system, data that is modified by the event based on the metadata. The destination system may synchronize a database of the destination system based on the data retrieved from the source system.

Abstract: Methods, systems, and devices for data management are described. A cloud data backup and recovery system may include a destination system and a source system. The destination system may be operable to provide backup and recovery services for the source system. The destination system may communicate a set of push/pull notifications with the source system. Each push/pull notifications may indicate an event is being performed in the source system. The destination system may determine an event is being performed in the source system based on transmitting a push notification or receiving a pull notification, where the push or pull notification may include metadata associated with the event. The destination system may retrieve, from the source system, data that is modified by the event based on the metadata. The destination system may synchronize a database of the destination system based on the data retrieved from the source system.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may provide backup services for multiple tenants. The DMS may receive a request to provide a first user of the DMS with audit information associated with an entity of the DMS. The DMS may identify context information for a log-in session associated with the request. The context information may include an identifier (ID) of a tenant associated with the request. The DMS may identify, based on the ID of the tenant, authorization information associated with the tenant. The authorization information may indicate that the tenant has access to a set of entities within a hierarchy associated with the DMS. The DMS may determine whether to output the requested audit information to the first user based on a hierarchical relationship, within the hierarchy, between the tenant and the entity.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may implement multi-tenancy role based access control (RBAC). In accordance with the multi-tenancy based RBAC, tenant organizations of a DMS may be assigned permissions (i.e., privileges) for a given data management cluster and/or computing objects within a data management cluster. Customized user roles (RBAC roles) may also be created for a given tenant. For example, a role may be defined based on a corresponding set of permissions (e.g., permissions associated with computing objects, data management clusters, or data sources associated with the tenant). A user within a tenant may be assigned a user role, which may be a customized role, and the effective permissions for the user may be based on which permissions of the user's assigned role are also within the scope of the tenant's permissions.

Abstract: Methods, systems, and devices for data management are described. A data management system may configure backup and recovery resources for tenant of the data management system. The data management system may receive an indication to create a set of subtenants within the resources configured for the tenant. The data management system may assign a first subset of resources configured for the tenant, and the first subset may be different from a second subset configured for a second subtenant. The data management system may activate a first backup procedure for the first subtenant. The first backup procedure may be configured to backup a first data source associated with the first subtenant of the tenant using the first subset of the set of backup and recovery resources, and the first backup procedure may be separate from a second backup procedure for a second data source associated with the second subtenant.

Abstract: Methods, systems, and devices for data management are described. A multi-tenancy data management system (DMS) may include multiple computing objects organized as a hierarchy of computing objects. The DMS may receive a request for report data associated with a first set of computing objects of the DMS. The DMS may identify context information for a log-in session associated with the request. The context information may include a tenant identifier (ID) for a tenant associated with the request. The DMS may apply a filter to the first set of computing objects. The filter may be based on a second set of computing objects to which the tenant has access within the hierarchy of computing objects. The DMS may output the report data for at least one computing object of the first set based on the at least one computing object being included in the second set of computing objects.

Abstract: Methods, systems, and devices for data management are described. A data management system may receive an indication to create a set of subtenants of a tenant. A first set of user profiles are associated with the tenant and a second set of user profiles are associated with a parent tenant of the tenant. The system may assign a first subset of the first set of user profiles to a first subtenant and assign a second subset to a second subtenant. The first subset and the second subset exclude user profiles from the second set of user profiles that are non-overlapping with the first set of user profiles. The system may update metadata corresponding to the first set of user profiles and the second set of user profiles such that the first subset has access to the first subtenant for and the second subset has access to the second subtenant.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may implement multi-tenancy role based access control (RBAC). A DMS that provides backup and recovery to multiple tenants may assign a data management cluster to a tenant organization, or specific resources from a data management cluster to a tenant, allowing multiple tenants to share a single data management cluster. The assignment of resources of the data management cluster respects the hierarchical relationship among computing objects, for example, assigning a top-level resource to a tenant implicitly assigns the descendent resources that descend from that top-level resource to the tenant.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may receive a request to assign a first computing object in a first object hierarchy of the DMS to a first tenant of the DMS. The DMS may check the first object hierarchy to identify other computing objects having a hierarchical relationship with the first computing object. The other objects may be above or below the first computing object within the first object hierarchy. The DMS may determine whether at least one of the other computing objects in the first object hierarchy is assigned to a second tenant of the DMS. The DMS may output, in response to the request, an indication that the first computing object is unavailable for assignment to the first tenant if at least one of the other computing objects in the first object hierarchy is assigned to the second tenant.

Abstract: Methods, systems, and devices for data management are described. A data management system (DMS) may receive a federated login request from a user associated with one or more tenants of the DMS. The DMS may direct the federated login request to a centralized management service. The DMS may receive a security assertion markup language (SAML) assertion that indicates an identity of the user, a set of object-level permissions assigned to the user, and an identifier of a first tenant associated with the user. The DMS may identify one or more computing objects in a cluster of storage nodes that correspond to the first tenant based on the identifier from the SAML assertion. The DMS may determine that the user is authorized to perform a set of actions on the one or more computing objects based on the set of object-level permissions indicated by the SAML assertion.

Abstract: Methods, systems, and devices for data management are described. Data management clusters may be configured to store metadata associated with providing data protection for a set of computing objects. A data management cluster may be triggered to export respective metadata to a cloud environment, where the respective metadata may be associated with providing data protection for one or more of the computing objects. Based on the export operation being triggered, the respective metadata may be downloaded from the cloud environment and written to a database that is configured to store a version of the metadata associated with providing the data protection for the set of computing objects. An interface for managing the operation of the data management clusters may be provided, where a content of the interface may reflect the version of the metadata stored at the database.