Abstract: Some embodiments provide a system and method associated with a determination of an upgrade path for an application service associated with a container-orchestration system (e.g., a KUBERNETES® container-orchestration system). A container-orchestration system server may trigger, by an operator object deployed as a controller for the application service, an upgrade process. In response to the trigger, the container-orchestration system server may access a dictionary type data structure containing a plurality of tuples associated with the application service (and the dictionary type data structure may be uncoupled from the application service). The container-orchestration system server may then automatically execute a search algorithm on the plurality of tuples to determine the upgrade path from a source version to a target version for the application service. According to some embodiments, the application service may then be automatically upgraded in accordance with the determined upgrade path.

Abstract: Some embodiments provide a system and method associated with improving resilience for a non-high availability service provided by a multi-node cluster (e.g., a bosh-based database service). A processor of a node in the cluster may determine that a lifecycle event has occurred (e.g., an initial deployment, failover, or deployment update). Responsive to the lifecycle event, the processor may store information about a role of a master node and timestamp information (e.g., on persistent storage). The processor may subsequently determine that a cluster deployment crash has occurred for the service. Timestamp information associated with multiple nodes may then be compared to establish one of the nodes as the master node. For example, the most recent timestamp may be used to establish the master node.

Abstract: Some embodiments provide a system and method associated with a determination of an upgrade path for an application service associated with a container-orchestration system (e.g., a KUBERNETES® container-orchestration system). A container-orchestration system server may trigger, by an operator object deployed as a controller for the application service, an upgrade process. In response to the trigger, the container-orchestration system server may access a dictionary type data structure containing a plurality of tuples associated with the application service (and the dictionary type data structure may be uncoupled from the application service). The container-orchestration system server may then automatically execute a search algorithm on the plurality of tuples to determine the upgrade path from a source version to a target version for the application service. According to some embodiments, the application service may then be automatically upgraded in accordance with the determined upgrade path.

Abstract: Some embodiments provide a system and method associated with improving resilience for a non-high availability service provided by a multi-node cluster (e.g., a bosh-based database service). A processor of a node in the cluster may determine that a lifecycle event has occurred (e.g., an initial deployment, failover, or deployment update). Responsive to the lifecycle event, the processor may store information about a role of a master node and timestamp information (e.g., on persistent storage). The processor may subsequently determine that a cluster deployment crash has occurred for the service. Timestamp information associated with multiple nodes may then be compared to establish one of the nodes as the master node. For example, the most recent timestamp may be used to establish the master node.

Abstract: A first cloud computing provider may execute a virtual machine, and an automated migration platform may access the first provider data center using a secure shell with key-based access by providing a public encryption key. The automated migration platform may use a data duplicator command to stream block level copies of the virtual machine (and the stream of block level copies may be compressed before being stored at a storage location). Resource requirements, including a volume size, of the virtual machine may be automatically determined and used to create a new empty volume at a second cloud computing provider. The compressed stream of block level copies from the storage location may be extracted into the new empty volume. A new virtual machine may then be spawned at the second cloud computing provider having the new volume as a root volume. The new virtual machine may then be started.

Abstract: A first cloud computing provider may execute a virtual machine, and an automated migration platform may access the first provider data center using a secure shell with key-based access by providing a public encryption key. The automated migration platform may use a data duplicator command to stream block level copies of the virtual machine (and the stream of block level copies may be compressed before being stored at a storage location). Resource requirements, including a volume size, of the virtual machine may be automatically determined and used to create a new empty volume at a second cloud computing provider. The compressed stream of block level copies from the storage location may be extracted into the new empty volume. A new virtual machine may then be spawned at the second cloud computing provider having the new volume as a root volume. The new virtual machine may then be started.