Abstract: A method for dynamically adjusting a number of virtual machines for a workload, includes: receiving a probability indicator for each of a plurality of N sequential stages, where N is a natural number greater than 1, of a likelihood that a virtual machine assigned to a workload will be evicted during the N sequential stages; predicting a target number of virtual machines to configure in a current stage for a subsequent stage from among the plurality of N sequential stages based on the probability indicator, a target capacity for the workload, and a current price for maintaining a virtual machine; and configuring a number of virtual machines for the workload during the current stage based on the target number to be loaded for the workload for the subsequent stage.

Abstract: Systems and methods are provided for scheduling a virtual machine (VM) to host a workload in a cloud system. In particular, the disclosed technology schedules an evicted VM for redeploying an interruptible workload. The scheduling is based on capacity prediction and inference data associated with a type of the evicted VM. Capacity signal predictor generates training data for training a machine learning model using capacity signal history data of the cloud system. The machine-learning model, once trained, predicts capacity including a rate of evictions for the types of the evicted VM. The predicted data is based on at least the current status of available computing resources. Upon receiving a notice associated with a workload interruption, the intelligent scheduler prioritizes the evicted VM for scheduling and determines whether to defer redeploying the evicted VM based on the rate of eviction for the type of the evicted VM.

Abstract: To obtain one or more recommendations for the migration of a database to a cloud computing system, information about performance of the database operating under a workload may be obtained. A first machine learning model (e.g., a neural network-based autoencoder) may be used to generate a compressed representation of characteristics of the database operating under the workload. The compressed representation may then be provided as input to a second machine learning model (e.g., a neural network-based classifier), which outputs a recommendation regarding a characteristic (e.g., size, configuration, level of service) of the cloud database to which the database should be migrated. This type of recommendation may be made prior to migration, thereby making it easier to properly estimate the cost of running the cloud database and plan the migration accordingly.

Abstract: Aspects of the present disclosure relate to incident routing in a cloud environment. In an example, cloud provider teams utilize a scout framework to build a team-specific scout based on that team's expertise. In examples, an incident is detected and a description is sent to each team-specific scout. Each team-specific scout uses the incident description and the scout specifications provided by the team to identify, access, and process monitoring data from cloud components relevant to the incident. Each team-specific scout utilizes one or more machine learning models to evaluate the monitoring data and generate an incident-classification prediction about whether the team is responsible for resolving the incident. In examples, a scout master receives predictions from each of the team-specific scouts and compares the predictions to determine to which team an incident should be routed.

Abstract: To obtain one or more recommendations for the migration of a database to a cloud computing system, information about performance of the database operating under a workload may be obtained. A first machine learning model (e.g., a neural network-based autoencoder) may be used to generate a compressed representation of characteristics of the database operating under the workload. The compressed representation may then be provided as input to a second machine learning model (e.g., a neural network-based classifier), which outputs a recommendation regarding a characteristic (e.g., size, configuration, level of service) of the cloud database to which the database should be migrated. This type of recommendation may be made prior to migration, thereby making it easier to properly estimate the cost of running the cloud database and plan the migration accordingly.