Abstract: A technique improves implementation of an index for an operations log (oplog) that coalesces random write operations directed to a virtual disk (vdisk) stored on an extent store. The oplog temporarily caches data associated with the random write operations (i.e., write data) as well as metadata describing the write data. The metadata includes descriptors to the write data stored on virtual address regions, i.e., offset ranges, of the vdisk and are used to identify the offset ranges of write data for the vdisk that are cached in the oplog. To facilitate fast lookup operations of the offset ranges when determining whether write data is cached in the oplog, an oplog index provides a state of the latest data for offset ranges of the vdisk. The technique improves implementation of the oplog index by storing the oplog index in storage class memory, such as persistent memory, to obviate failure and subsequent recovery of the oplog index.

Abstract: A system for package management includes an interface and a processor. The interface is to receive an indication to install a package. The processor is to determine a configured package using a set local configuration properties and using the package and to launch, using a metascheduler, a set of subschedulers to install a plurality of applications of the configured package.

Abstract: Methods, systems, and computer program products for high-performance multi-node computing. Upon receiving a request to move a computing process from a first computing node to a second computing node, an agent responds to the request by: copying contents of one or more pages of the computing process from the first computing node to the second computing node, identifying page recency metadata corresponding to the one or more pages of the computing process, and copying all or portions of the identified page recency metadata to the second computing node. When the CPU of the second computing node accesses pages of the moved computing process, the operating system of the second computing node observes page recency metadata that had been copied from the first node and stored at the second computing node. The computing process might comprise a virtual machine, a guest operating system, or an executable container.

Abstract: Methods, systems, and computer program products for high availability computing systems. A computer processor executes a sequence of instructions to execute, on a first node of a computing platform, a first instance of a computing process that is configured to use a first graphics processing unit (GPU) in a first GPU configuration. Responsive to detection of a loss of functionality that affects the first node, an agent automatically determines that a second instance of the computing process can execute on a second node. The determination is made by (1) determining that the second instance of the computing process can execute using a second GPU in a second GPU configuration on the second node, (2) mapping the first GPU configuration into one or more alternate second GPU configurations, and (3) configuring the second instance of the computing process to use the second GPU in one of the alternate second GPU configurations.

Abstract: A dynamically-managed microservices platform. The microservices platform is configured to selectively accept admission of microservices and to selectively throttle microservices based on a continually-trained machine learning model. The system is configured to implement multiple microservice lifecycle strategies, where individual ones of the multiple microservice lifecycle strategies use a prediction model having long-term and short term demand predictions. One or another of the multiple microservice lifecycle strategies are invoked at different times under different conditions. Under a first set of conditions, a prediction model is used to select a first strategy to admit or throttle a microservice based upon long-term or short-term demand predictions. Under a second set of conditions, the prediction model is used to select a different strategy to admit or throttle a microservice.

Abstract: Methods, systems and computer program products for hibernating a computing cluster. An information lifecycle manager facility (ILM) is invoked to carry out movement of data from the hypervisor of a node of a computing cluster to a different storage location. Multiple nodes of the computing cluster can be hibernated until the entire computing cluster has been hibernated. The ILM observes a replication factor of the computing cluster to suppress saving multiple copies of data. A hibernation object comprising state information of a node is stored in a network-accessible storage location. The hibernation object is accessed in response to an instruction to initiate restoration of all or parts of the computing cluster. The hibernation object can be stored using first cloud computing storage infrastructure and later, can be restored to a different cloud computing infrastructure. Upon restoration, the hibernated cluster has the same state as of the time of hibernation.

Abstract: Various embodiments set forth techniques for taking a snapshot of virtual memory of a virtual machine. One technique includes allocating, in a persistent memory, one or more blocks associated with a virtual memory; detecting a write request associated with a first portion of the virtual memory; in response to detecting the write request associated with the first portion, prioritizing the first portion; based on the prioritizing, copying the first portion into the one or more blocks in the persistent memory ahead of a second portion of the virtual memory; and after copying the first portion: applying the write request to the first portion; and copying the second portion into the one or more blocks in the persistent memory.

Abstract: A multi-cluster configuration of a database management system in a virtual computing system includes a server that defines a first policy for a source database on a first cluster of a plurality of clusters. Each of the plurality of clusters is registered with the server and the first policy defines capture of snapshots and/or transactional logs from the source database on the first cluster. The server defines a second policy for the source database to replicate at least some of the snapshots and/or transactional logs from the first cluster to a second cluster of the plurality of clusters, captures a first snapshot and/or a first transactional log from the source database in accordance with the first policy, and replicates the first snapshot and/or the first transactional log to the second cluster in accordance with the second policy.

Abstract: A patching operation on an availability group cluster having a plurality of nodes is disclosed. The patching operation is performed in a plurality of iterations, each including determining a current state of each of the plurality of nodes, selecting a next node based on the current state, and patching the next node. A secondary replica node is selected as the next node before the a primary replica node. Each secondary replica node is patched in accordance with a first priority, upon patching each of the secondary replica node, a failover target node for patching the primary replica node is selected, the failover target node is selected based on a second priority, and according to the second priority, a healthy synchronous secondary replica node of the plurality of nodes is selected as the failover target node before an unhealthy synchronous secondary replica node of the plurality of nodes.

Abstract: In one embodiment, a system for managing communication connections in a virtualization environment includes a plurality of host machines implementing a virtualization environment, wherein each of the host machines includes a hypervisor, at least one user virtual machine (user VM), and a distributed file server that includes file server virtual machines (FSVMs) and associated local storage devices. Each FSVM and associated local storage device are local to a corresponding one of the host machines, and the FSVMs conduct I/O transactions with their associated local storage devices based on I/O requests received from the user VMs. Each of the user VMs on each host machine sends each of its representative I/O requests to an FSVM that is selected by one or more of the FSVMs for each I/O request based on a lookup table that maps a storage item referenced by the I/O request to the selected one of the FSVMs.

Abstract: In one embodiment, a system for managing a virtualization environment includes a set of host machines, each of which includes a hypervisor, virtual machines, and a virtual machine controller, and a data migration system configured to identify one or more existing storage items stored at one or more existing File Server Virtual Machines (FSVMs) of an existing virtualized file server (VFS). For each of the existing storage items, the data migration system is configured to identify a new FSVMs of a new VFS based on the existing FSVM, send a representation of the storage item from the existing FSVM to the new FSVM, such that representations of storage items are sent between different pairs of FSVMs in parallel, and store a new storage item at the new FSVM, such that the new storage item is based on the representation of the existing storage item received by the new FSVM.

Abstract: Various embodiments set forth techniques for maintaining replicas of a data set. The techniques include storing, by a first node, a first replica of the data set on the first node; storing, by a second node, a second replica of the data set on the second node; and performing, by the first node and based on first metadata associated with the first replica, a first data management activity on the first replica that changes a first format of the first replica so that the first format of the first replica is different from a second format of the second replica.

Abstract: A technique efficiently migrates a live virtual disk (vdisk) across storage containers of a cluster having a plurality of nodes deployed in a virtualization environment. Each node is embodied as a physical computer with hardware resources, such as processor, memory, network and storage resources, that are virtualized to provide support for one or more user virtual machines (UVM) executing on the node. The storage resources include storage devices embodied as a storage pool that is logically segmented into the storage containers configured to store one or more vdisks. The storage containers include a source container having associated storage policies and a destination container having different (new) storage policies.

Abstract: One embodiment of the present invention facilitates address resolution protocol (ARP) resolution in an extended subnet. A gateway of a first segment of the extended subnet can determine that a layer-2 address corresponding to a layer-3 destination address of a packet is locally unavailable. The gateway can then determine whether a respective egress interface of an ARP request for the layer-3 destination address is associated with a layer-2 subnet extension from the first segment to a second segment of the extended subnet. The extension can provide a common layer-2 broadcast domain comprising the first and second segments with a same default gateway layer-3 address. If the egress interface is associated with the extension, the gateway can insert a layer-3 address of a first endpoint associated with the extension as a source protocol address in the ARP request. The gateway can send the modified ARP request via the egress interface.

Abstract: Examples described herein include virtualized file servers which may include cloned instances of the virtualized file server. Cloning a virtualized the server may allow for testing of new and/or revised features, disaster recovery plans, or other configurations while maintaining availability of the parent (e.g., source) virtualized file server.

Abstract: A technique provides efficient data failover by creation and deployment of a protection policy that ensures maintenance of frequent common snapshots between sites of a multi-site data replication environment. A global constraint optimizer executes on a node of a cluster to create the protection policy for deployment among other nodes of clusters at the sites. Constraints such as protection rules (PRs) specifying, e.g., an amount of tolerable data loss are applied to a category of data designated for failover from a primary site over a network to a plurality of (secondary and tertiary) sites typically located at geographically separated distances. The optimizer processes the PRs to compute parameters such as frequency of snapshot generation and replication among the sites, as well as retention of the latest common snapshot maintained at each site to create a recovery point and configuration of the protection policy that reduces network traffic for efficient use of the network among the sites.

Abstract: A platform-as-a-service infrastructure and application lifecycle manager is configured to implement a common services model to deploy selected services from a common set of services to service domains hosted on multiple different cloud platforms by abstracting dependence on availability of various additional supporting services, such as services that are platform-specific. The platform-as-a-service infrastructure and application lifecycle manager may also manage a lifecycle of available services, such as managing upgrades and/or patches to services.

Abstract: In one embodiment, a system for managing a virtualization environment includes a set of host machines, each of which includes a hypervisor, virtual machines, and a virtual machine controller, and a virtualized file server backup system configured to identify backup data, wherein the backup data comprises data stored on the virtual disks and VFS configuration information, and the first data is identified in accordance with a backup policy, send the backup data to one or more remote sites for storage, and, in response to detection of changes in the backup data, send the changes to the remote sites in accordance with a replication policy. The backup data may be identified based on a protection domain associated with the backup policy. The data stored on the VFS may include one or more storage objects. The storage objects may include shares, groups of shares, files, or directories.

Abstract: Examples of systems described herein include a virtualized file servers. Examples of virtualized file servers described herein may support disaster recovery of the virtualized file server. Accordingly, examples of virtualized file servers may support metadata fixing procedures to update metadata in a recovery setting. Examples of virtualized file servers may support hypervisor-agnostic disaster recovery.

Abstract: Methods, systems and computer program products for intra-footprint computing cluster bring-up within a virtual private cloud. A network connection is established between an initiating module and a virtual private cloud (VPC). An initiating module allocates resources of the virtual private cloud including a plurality of nodes that correspond to members of a to-be-configured computing cluster. A cluster management module having coded therein an intended computing cluster configuration is configured into at least one of the plurality of nodes. The members of the to-be-configured computing cluster interoperate from within the VPC to accomplish a set of computing cluster bring-up operations that configure the plurality of members into the intended computing cluster configuration. Execution of bring-up instructions of the management module serve to allocate networking IP addresses of the virtual private cloud.