{'fraction_non_alphanumeric': 0.03842940685045948, 'fraction_numerical': 0.003341687552213868, 'mean_word_length': 5.475675675675675, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Resource Adjustment and Intervention Scheduling in the Availability-Aware Cloud

Server instances, also known as virtual machines (VMs), with various computing and storage capabilities (i.e. different combinations of CPU, memory, storage, and networking), are commonly offered by cloud computing service providers such as Amazon Web Services (AWS), Google, Microsoft, Rackspace, and SalesForce. The clients, ranging from individuals and small institutions to large companies, can rent and pay only for a set of VMs that are actually needed as a usagebased (pay-as-you-go) posted pricing model. This model alleviates the clients’ concerns about the risks of capacity under-utilization and demand non-fulfillment associated with in-house facilities. These VMs are mapped onto physical servers within cloud. Such datacenters are known to be susceptible to different types of failures from frequent small-scale failures (such as disk failures) to less frequent but more catastrophic failures (such as power distribution unit failures) (Dean 2009). Failures at the physical infrastructure level inevitably render the mapped VMs unavailable due to loss of connectivity, software bugs, human errors, etc.