Abstract: The technology described herein is directed towards fault injection to cloud provider resources, through a system that facilitates selection of specific resources in availability zone(s)/region(s). Example resources include VMs (virtual machines), VM clusters, tagged resource grouping and/or managed services. Based on (e.g., user) input data, the system injects faults to specified resources through cloud provider interfaces. The input data can specify availability zone(s), fault injection start time and duration. The input data can also specify fixed mode (fail specified resources together) or chaos mode (randomly inject failures for each resource individually). Failure type can be specified, e.g., graceful (e.g., clean shutdown) or non-graceful (e.g., a non-clean, hard fault). Based on the input, the system injects fault(s) using the modes selected to the specified resource(s) in the selected availability zone(s) for the duration entered.

Abstract: The technology described herein is directed towards automatic virtual subnet delegation. An automated process scans the subnets of a virtual network and builds a tree of the IP space, including allocated and unused space designations. User-defined parameters and organization policy data are used to determine the number of IP addresses needed for an application or the like. By traversing the tree of existing IP space, the technology described herein finds and places a new subnet, such as to ensure a high utilization of the overall IP space or based on an alternative type-of-fit criterion. When the virtual subnet space is created in the cloud, a public cloud-specific subnet identifier is returned to the user to utilize in deploying the application. Another use of the technology described herein is to track and optimize IP space allocation for existing virtual networks in the public cloud, including to identify underutilized and/or improperly-sized subnets.

Abstract: The technology described herein is directed towards automatic virtual subnet delegation. An automated process scans the subnets of a virtual network and builds a tree of the IP space, including allocated and unused space designations. User-defined parameters and organization policy data are used to determine the number of IP addresses needed for an application or the like. By traversing the tree of existing IP space, the technology described herein finds and places a new subnet, such as to ensure a high utilization of the overall IP space or based on an alternative type-of-fit criterion. When the virtual subnet space is created in the cloud, a public cloud-specific subnet identifier is returned to the user to utilize in deploying the application. Another use of the technology described herein is to track and optimize IP space allocation for existing virtual networks in the public cloud, including to identify underutilized and/or improperly-sized subnets.

Abstract: The technology described herein is directed towards fault injection to cloud provider resources, through a system that facilitates selection of specific resources in availability zone(s)/region(s). Example resources include VMs (virtual machines), VM clusters, tagged resource grouping and/or managed services. Based on (e.g., user) input data, the system injects faults to specified resources through cloud provider interfaces. The input data can specify availability zone(s), fault injection start time and duration. The input data can also specify fixed mode (fail specified resources together) or chaos mode (randomly inject failures for each resource individually). Failure type can be specified, e.g., graceful (e.g., clean shutdown) or non-graceful (e.g., a non-clean, hard fault). Based on the input, the system injects fault(s) using the modes selected to the specified resource(s) in the selected availability zone(s) for the duration entered.

Abstract: A passive state storage controller monitors a plurality of active state storage controllers to determine when a failure of at least one of the active state storage controllers occurs. Based on a determination of a failure, the passive state storage controller remaps storage devices to the passive state storage controller from the failed storage controller. The passive state storage controller may also remap network interfaces. The passive state storage controller retrieves a transaction log of the failed storage controller from a transaction log database, and replays transactions in the retrieved transaction log. The passive state storage controller switches to operating in an active state.

Abstract: A passive state storage controller monitors a plurality of active state storage controllers to determine when a failure of at least one of the active state storage controllers occurs. Based on a determination of a failure, the passive state storage controller remaps storage devices to the passive state storage controller from the failed storage controller. The passive state storage controller may also remap network interfaces. The passive state storage controller retrieves a transaction log of the failed storage controller from a transaction log database, and replays transactions in the retrieved transaction log. The passive state storage controller switches to operating in an active state.

Abstract: A method, non-transitory computer readable medium, and apparatus that monitors with a passive storage controller a plurality of active storage controllers. A determination is made with the passive storage controller when a failure of one of the active storage controllers has occurred based on the monitoring. Storage device(s) previously assigned to the one of the active storage controllers are remapped to the passive storage controller. A transaction log associated with the one of the active storage controllers is retrieved with the passive storage controller from a transaction log database. Transaction(s) in the transaction log are replayed with the passive storage controller, when the failure of the one of the active storage controllers is determined to have occurred.

Abstract: A method, non-transitory computer readable medium and host device that monitors an active virtual storage controller. A determination of when a failure of the active virtual storage controller has occurred is made based on the monitoring. When the failure of the active virtual storage controller is determined to have occurred, one or more storage devices previously assigned to the active virtual storage controller are remapped to a passive virtual storage controller and one or more transactions in a transaction log are replayed.

Abstract: According to a novel mechanism, each processing device (e.g., a central processing unit (CPU) in a multi-processor system) is assigned to process a single execution thread for a task and the execution thread is processed across various layers of the multi-processor system (such as a network layer and application layer) without being divided into separate threads. Advantageously, upon initialization of the multi-processor system, network context data structures are created equal to the number of processing devices in the system. As used herein, a network context is a logical entity to which zero or more connections are bound during their lifetime. Rather than sharing data structures among execution threads, a multi-processor system allocates memory resources per each network context during initialization of the system. As a result, an execution thread processing a task queued to a particular network context accesses memory resources allocated for that network context only.

Abstract: A flow manager may receive packet flow rules from one or more network services and may generate a unified rule set according to the received packet flow rules. A flow manager may additionally split the unified rule set into subsets for enforcement by one or more flow enforcement devices and may install the rule subsets onto the flow enforcement devices. When splitting the unified rule set into subsets, a flow manager may analyze a network topology connecting the flow enforcement devices. A flow manager may also receive additional packet flow rules, integrate them into the unified rule set, update the rule subsets according to the additional rules, and install the updated subsets onto the flow enforcement devices.

Abstract: A flow manager may receive prioritized packet flow rules from multiple prioritized network services where each flow rule may comprise a packet filter and a prioritized action list. The priority for the flow rules from each network service may be expressed as either longest prefix or ordered precedence. The flow manager may generate a unified rule set according to the received packet flow rules by identifying conflict between pairs of rules and resolving the identified conflicts according the priority relationship two rules of each pair. When resolving conflicts between rules, the flow manager may append the action list of one rule to the action list of another rule, and may also create a new rule by combining the packet filters and actions lists of the conflicting rules.

Abstract: A flow manager may receive prioritized packet flow rules from one or more network services where each rule may include a packet filter and prioritized actions. Each action of a packet flow rule may be either terminating or non-terminating. A flow manager may generate a unified rule set according to the received packet flow rules and may additionally validate the unified rule set to identity errors. When validating the unified rule set, a flow manager may compare the unified rule set against one or more defined policies. Alternatively, a flow manager may apply the unified rule set to either captured or manually specified simulated network packets. A flow manager may also identity extraneous rules or actions. Further, a flow manager may present the unified rule set for manual verification and may receive input identifying errors and specifying modification to correct the errors.