Managed Cloud Service Maintenance Windows
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing public cloud offerings lack the ability to meet the stringent availability, compliance, and maintenance requirements of sensitive industry verticals such as telecommunications, healthcare, and financial services, while providing the benefits of cloud scalability and pay-as-you-go models.
Innovation Solution
A managed cloud offering that includes a service maintenance system, which classifies services by criticality and schedules maintenance windows accordingly. The system denies maintenance requests when maintenance windows are closed and allows requests when they are open, ensuring high availability and compliance with regulatory requirements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If maintenance is performed on critical services, then service updates and improvements can be applied, but service availability and reliability deteriorate during maintenance windows
Solution Approach 1:
The system performs maintenance actions in advance during predetermined maintenance windows before they impact critical services. By scheduling maintenance ahead of time and executing it during designated periods when services are expected to be less critical or can be temporarily paused, the system applies updates without causing unexpected service outages, thus resolving the contradiction between performing maintenance and maintaining availability
Solution Approach 2:
The system implements periodic maintenance windows at predetermined intervals during which maintenance activities are permitted. This periodic structure allows the system to rotate through maintenance and operation phases, ensuring that critical services receive updates while maintaining overall availability through structured timing, thereby balancing maintenance capability with service reliability
2Adaptability or versatility
If multiple maintenance windows are created for different criticality classifications, then maintenance scheduling flexibility improves, but system complexity increases
Solution Approach 1:
The system applies different maintenance window policies to different services based on their criticality classifications. Critical services have restricted maintenance windows with stricter constraints, while non-critical services have more flexible scheduling. This localized differentiation allows the system to optimize maintenance scheduling for each service type without requiring complete redesign of the entire maintenance management system, thus improving flexibility while controlling complexity
Solution Approach 2:
The maintenance window management system is segmented into distinct categories based on service criticality (critical, semi-critical, non-critical). Each segment has its own maintenance window rules and scheduling policies, which simplifies the overall management by breaking down the complex task of managing all services uniformly into manageable segments with standardized handling procedures for each category
3Reliability
If maintenance requests are denied when windows are closed, then service availability is maintained, but maintenance productivity and system updates are delayed
Solution Approach 1:
The system continuously monitors the status of maintenance windows and service criticality levels, providing feedback to determine whether maintenance requests should be approved or denied. This feedback mechanism ensures that maintenance is allowed when it will not impact service availability and denied when it would cause disruptions, thereby maintaining both service reliability and maintenance productivity through dynamic, informed decision-making
Solution Approach 2:
The maintenance window system dynamically adjusts its state based on real-time conditions such as service criticality changes and current maintenance status. Maintenance windows can be opened, closed, or extended based on the current state of services and infrastructure, allowing the system to adapt maintenance scheduling to actual conditions rather than following a rigid schedule, thus balancing availability requirements with maintenance needs
Data Source
AI summary
A method includes obtaining, for each service of a plurality of services of a public cloud environment, a criticality classification. Each criticality classification includes one of a critical classification, a semi-critical classification, or a non-critical classification. The method includes obtaining a maintenance schedule for the public cloud environment. The maintenance schedule includes a plurality of maintenance windows and each maintenance window of the plurality of maintenance windows is associated with a respective criticality classification. The method includes receiving a maintenance request requesting maintenance of one of the plurality of services. The method also includes determining that each maintenance window associated with the respective criticality classification of the one of the plurality of services is currently closed. In response to determining that each maintenance window associated with the respective criticality classification of the one of the plurality of services is currently closed, the method includes denying the maintenance request.