Abstract: A centralized Internet of Things (IoT) manager of an IoT system is configured generate and deploy a data pipeline application to an edge system. The centralized IoT manager is configured to receive a request for a data category and identification of a data transformation function, identify a data source of the IoT system belonging to the data category, and identify an edge system of the IoT system associated with the data source. The centralized IoT manger is further configured to generate a containerized data pipeline application based on a configuration of the edge system that is configured apply the data transformation function to input data to provide transformed data, and provide the containerized data pipeline application to the edge system.

Abstract: An example Internet of Things (IoT) sensor application hosted on a mobile device is configured to add the mobile device as a data sensor or source in the IoT system. The IoT sensor application is configured to provide an interface between an input or output component of the mobile device and a data pipeline or application and/or to cloud data storage associated with an IoT system. The IoT sensor application is configured to connect to an edge device of the IoT system and search for a data source identifier associated with the type of data source component, and corresponding application(s) and/or data pipeline(s) to which the data source is connected. Once connected, the IoT sensor application provides captured data to or receives processed or playback data from the data source.

Abstract: A scalable Internet of Things (IoT) system may include multiple instances of an IoT manager, each instance respectively configured to connect to a respective edge system of multiple edge systems, The IoT system may further include a containerized system configured to allow any instance of the IoT manager to deploy data pipelines to any edge system of the multiple edge systems in delta communications. Any instance of the IoT manager may send a change message to any edge system via a publish/subscribe notification method. In some examples, a centralized IoT manager may form a secure communication with an edge system, synchronize an object model with an edge object model for the edge system, and maintain the edge system using delta change communications. The IoT system may facilitate any instance of the IoT manager to subscribe a communication channel with an associated edge system for receiving update notification.

Abstract: A centralized Internet of Things (IoT) manager of an IoT system is configured generate and deploy a data pipeline application to an edge system. The centralized IoT manager is configured to receive a request for a data category and identification of a data transformation function, identify a data source of the IoT system belonging to the data category, and identify an edge system of the IoT system associated with the data source. The centralized IoT manger is further configured to generate a containerized data pipeline application based on a configuration of the edge system that is configured apply the data transformation function to input data to provide transformed data, and provide the containerized data pipeline application to the edge system.

Abstract: A method of managing servers of a distributed computer system by using an intent-based CLI (command line interface) executing by one or more processors of a remote computing device, the servers hosting a virtual cluster comprising one or more virtual machines. The method includes receiving, by a first server of the servers, a connection-request from the intent-based CLI to establish an encrypted connection between the first server and the remote computing device. The method includes authenticating the connection-request and establishing, in response to authenticating the connection-request, a first encrypted communication channel between the first server and the remote computing device. The method includes receiving, via the first encrypted communication channel, an operation-request for a list of intent-based operations supported by the first server.

Abstract: Disclosed is an approach for implementing disaster recovery for virtual machines. Consistency groups are implemented for virtual machines, where the consistency group link together two or more VMs. The consistency group includes any set of VMs which need to be managed on a consistent basis in the event of a disaster recovery scenario.

Abstract: An illustrative embodiment disclosed herein is a host device including a plurality of virtual machines and a controller virtual machine configured to compute a plurality of central processing unit (CPU) usages corresponding to the plurality of virtual machines. The controller virtual machine is further configured to compute a total usage as a sum of the plurality of CPU usages and to flag one or more outlier virtual machines of the plurality of virtual machines responsive to one or more exceeding CPU usages of the one or more outlier virtual machines being greater than a threshold usage. The controller virtual machine is further configured to assign weights to the one or more outlier virtual machines and to select, for virtual machine migration, a first outlier virtual machine of the one or more outlier virtual machines responsive to the total usage being greater than a target usage.

Abstract: A system and method include migrating virtual machines (VMs) between compute only (CO) and hyper converged (HC) nodes. The method includes identifying, by a management processor of a virtual computing system, a plurality of virtual machines hosted on compute only (CO) nodes in the virtual computing system. The management processor then identifies hyper converged (HC) nodes having virtual disks hosting data for the plurality of virtual machines hosted on CO nodes. When a virtual machine (VM) in the plurality of virtual machines is migrating, the management processor biases the VM to migrate to a first HC node hosting a virtual disk assigned to host data for the VM.

Abstract: An illustrative embodiment disclosed herein is an apparatus including a processor having programmed instructions that identify a bucket identifier corresponding to a bucket. The bucket identifier includes a prefix. The processor has programmed instructions that determine that the prefix matches a predetermined prefix, assign an expiry duration to the bucket, and, after the expiry duration, delete the bucket identifier.

Abstract: Examples of a distributed message service include a virtualized file system including a virtual disk configured to store messages for a message topic, and a broker logically allocated to the message topic. The broker is configured to cause a message directed to the message topic provided from a publisher to be stored at the virtual disk, and to route the message to a subscriber of the message topic that is registered with the broker. The distributed message service further includes an operating system configured to manage the virtualized file system and includes a message service configured to manage logical allocation of the broker and manage allocation of the virtual disk to the message topic.

Abstract: A database system associated with a plurality of source databases in a virtual computing system includes a dashboard having a main menu for providing a plurality of control functions and a body that dynamically changes based upon the plurality of control functions that are selected. The dashboard includes a homepage for displaying a plurality of cells in the body, including a first cell for displaying a list of the plurality of source databases. The main menu includes a first control function, the selection of which triggers a database provisioning service by presenting options to either create a new source database or register an existing database within the body and a second control function, the selection of which triggers a copy data management service by presenting an option to create a new cloned database.

Abstract: Techniques for performing compression operations on persistently-stored data blocks during read/write commands. A method embodiment performs in-line data compression operations over data blocks referenced by a caller. The in-line data compression operations are performed during execution of a storage input-output (I/O) command, between the event of receipt of the storage I/O command and the event of returning status of the storage I/O command. The storage I/O operation is associated with at least one data group comprising one or more data blocks that are identified by the caller. Upon receipt of the storage I/O command, one or more compression rules are applied to the data blocks to determine one or more compression parameters, which compression parameters are used to form specific compression operations that are performed over at least a portion of the data group. The status pertaining to the execution of the storage I/O operation is returned to the caller.

Abstract: An illustrative embodiment disclosed herein is an apparatus including a processor having programmed instructions to determine a frequency rate for tracking changed data of a virtual machine (VM), track the changed data at the determined frequency rate, receive a request to generate a recovery point associated with a specified time, and, responsive to receiving the request to generate the recovery point associated with the specified time, generate the recovery point.

Abstract: Systems and methods for optimizing virtual migration includes determining a migration plan which includes migrating at least a virtual machine (VM) from a first origin node to a first candidate destination node over a network, determining a network migration cost for the migration plan, which includes determining a first relative network usage indicative of an amount of network traffic communicated over the network between the VM and each of one or more associated file storages when the VM is located on the first candidate destination node, and selecting to execute the migration plan based on the network migration cost.

Abstract: Systems and method for expanding a cluster with nodes before an upgrade so that the cluster can handle a failover event during an upgrade and still continue operating. The system and method includes receiving, at a processor, a signal indicating a cluster is about to commence an upgrade; computing, by the processor, a first number of nodes; adding, by the processor, the first number of nodes from a network to the cluster before the upgrade is performed on the cluster; receiving, at the processor, a signal indicating the cluster finished the upgrade; and removing a second number of nodes that is no greater than the first number of nodes from the cluster after the processor receives the signal indicating the upgrade is complete.

Abstract: Systems for low-latency data access in distributed computing systems. A method embodiment commences upon generating a first storage area in local storage of a first computing node. Access to the first storage area is provided through the first computing node. A second storage area is generated wherein the second storage area comprises a first set of metadata that comprises local storage device locations of at least some of the local storage areas of the first storage area. A set of physical access locations of the second storage area is stored to a database that manages updates to the second set of metadata pertaining to the second storage area. Accesses to the first storage area are accomplished by querying the database retrieve a location of the second set of metadata, and then accessing the first storage area through one or more additional levels of metadata that are node-wise collocated.

Abstract: Examples described herein provide for hardware interface services in virtualized systems. The hardware interface services may receive a vendor-agnostic command to control a particular hardware component. The particular hardware component may be identified, for example, by its location (e.g., physical and/or logical location or other identification) in the virtualized system. The hardware interface services described herein may identify a hardware component type (e.g., vendor, serial number, model number, etc.) based on the location provided. The hardware interface services may translate the vendor-agnostic command to a command specific for the identified hardware component.

Abstract: Examples described herein may provide local key managers on computing nodes of distributed computing systems. The local key managers may protect secrets (e.g. cryptographic keys) in the distributed system such that risk of compromise is reduced or eliminated. In some examples, secure processors, such as trusted platform modules (TPMs), may be incorporated in computing nodes of distributed computing systems described herein. The secure processor may aid in securely protect cryptographic keys in the event of disk or node theft, for example.

Abstract: In one embodiment, a system for managing a virtualization environment comprises a plurality of host machines, one or more virtual disks comprising a plurality of storage devices, a virtualized file server (VFS) comprising a plurality of file server virtual machines (FSVMs), wherein each of the FSVMs is running on one of the host machines and conducts I/O transactions with the one or more virtual disks, and a virtualized file server backup system configured to back up data stored in a VFS located a cluster of host machines to an object store, and retrieve the backed-up data as needed to restore the data in the VFS. The object store may be located in a public cloud. The object store may include a low-cost storage medium within the cluster. An FSVM of the VFS may provide an object store interface to low-cost storage media.

Abstract: Systems and methods for managing access to storage devices in a distributed data storage environment. Embodiments operate to manage communications between a client computing device and storage target devices in a distributed storage system. The distributed storage system comprises one or more computing nodes and at least one storage target device. A client computing device interfaced with the distributed storage system uses an IP address to access a leader virtualized controller. Upon receipt of a storage access protocol message by the leader virtualized controller elected from a set of virtualized controllers, a redirect message comprising a second IP address that identifies a second virtualized controller is sent to the client computing device. The client computing device connects to the second virtualized controller. Messages are sent between the client computing device and the second virtualized controller, which in turn accesses the storage target device to carry out storage I/O protocol messaging.