Self-service operation for bare-metal servers

Patent metadata

Field	Value
Publication number	US-2021355241-A1
Application number	US-202117379891-A
Country	US
Kind code	A1
Filing date	Jul 19, 2021
Priority date	Jan 29, 2019
Publication date	Nov 18, 2021
Grant date	—

Abstract

A system and method of automated downtime scheduling and control is disclosed. A failure of at least one component of at least one bare-metal server associated with a client is detected and a first notification is transmitted to a client system associated with the client. The notification includes a request to schedule downtime. A response including a selected downtime is received from the client system and the at least one bare-metal server is transitioned to an offline state at the selected downtime. A ticket is generated in a ticketing system for repair of the bare-metal server. The ticket identifies the at least one component.

First claim

What is claimed is:

1 . A system comprising a computing device configured to:
detect a failure of at least one component of at least one bare-metal server associated with a client; transmit a first notification to a client system associated with the client, wherein the notification includes a request configured to solicit a scheduled downtime that includes a time and date when the at least one bare-metal server can be taken offline; receive a response from the client system, the response including the scheduled downtime; transition the at least one bare-metal server to an offline state at the scheduled downtime; and generate a ticket in a ticketing system for repair of the bare-metal server, wherein the ticket identifies the at least one component.

2 . The system of claim 1 , wherein the computing device is further configured to:
generate a second notification to the client system, wherein the second notification includes a request configured to solicit a scheduled uptime, wherein the scheduled uptime includes a time and date when the at least one bare-metal server can be brought online; receive a second response from the client system, the second response including the scheduled uptime; and transition the at least one bare-metal server from the offline state to an online state.

3 . The system of claim 1 , wherein the processor is configured to transition the at least one bare-metal server to a reduced operation state before transitioning the at least one bare-metal server to the offline state.

4 . The system of claim 3 , wherein the at least bare metal server is prohibited from generating new instances of applications, performing restarts, and updating when in the reduced operation state.

5 . The system of claim 3 , wherein the first notification includes information regarding the types of operations that are restricted in the at least one bare-metal server when the at least one bare-metal server is operating in the reduced operation state.

6 . The system of claim 1 , wherein the request configured to solicit a scheduled downtime includes an initial time after which the at least one bare-metal server can be taken offline.

7 . The system of claim 1 , wherein the request configured to solicit a scheduled downtime includes a bounded time window during which the at least one bare-metal server can be taken offline.

8 . A method comprising:
detecting a failure of at least one component of at least one bare-metal server associated with a client; transmitting a first notification to a client system associated with the client, wherein the notification includes a request configured to solicit a time and date when the bare-metal server can be taken offline; receiving a response from the client system, the response including a selected downtime; transitioning the at least one bare-metal server to an offline state at the selected downtime; and generating a ticket in a ticketing system for repair of the bare-metal server, wherein the ticket identifies the at least one component.

9 . The method of claim 8 , further comprising:
generating a second notification to the client system, wherein the second notification includes a request configured to solicit a scheduled uptime, wherein the scheduled uptime includes a time and date when the at least one bare-metal server can be brought online; receiving a second response from the client system, the second response including the scheduled uptime; and transitioning the at least one bare-metal server from the offline state to an online state.

10 . The method of claim 8 , comprising transitioning the at least one bare-metal server to a reduced operation state before transitioning the at least one bare-metal server to the offline state.

11 . The method of claim 10 , wherein the at least bare metal server is prohibited from generating new instances of applications, performing restarts, and updating when in the reduced operation state.

12 . The method of claim 10 , wherein the first notification includes information regarding the types of operations that are restricted in the at least one bare-metal server when the at least one bare-metal server is operating in the reduced operation state.

13 . The method of claim 8 , wherein the request configured to solicit a scheduled downtime includes an initial time after which the at least one bare-metal server can be taken offline.

14 . The method of claim 8 , wherein the request configured to solicit a scheduled downtime includes a bounded time window during which the at least one bare-metal server can be taken offline.

15 . A non-transitory computer readable medium having instructions stored thereon, the instructions, when executed by a processor, cause the processor to perform operations comprising:
detecting a failure of at least one component of at least one bare-metal server associated with a client; transmitting a first notification to a client system associated with the client, wherein the notification includes a request configured to solicit a time and date when the bare-metal server can be taken offline; receiving a response from the client system, the response including a selected downtime; transitioning the at least one bare-metal server to an offline state at the selected downtime; and generating a ticket in a ticketing system for repair of the bare-metal server, wherein the ticket identifies the at least one component.

16 . The non-transitory computer readable medium of claim 15 , wherein the operations further comprise:
generating a second notification to the client system, wherein the second notification includes a request configured to solicit a scheduled uptime, wherein the scheduled uptime includes a time and date when the at least one bare-metal server can be brought online; receiving a second response from the client system, the second response including the scheduled uptime; and transitioning the at least one bare-metal server from the offline state to an online state.

17 . The non-transitory computer readable medium of claim 15 , wherein the operations further comprise transitioning the at least one bare-metal server to a reduced operation state before transitioning the at least one bare-metal server to the offline state.

18 . The non-transitory computer readable medium of claim 17 , wherein the at least bare metal server is prohibited from generating new instances of applications, performing restarts, and updating when in the reduced operation state.

19 . The non-transitory computer readable medium of claim 17 , wherein the first notification includes information regarding the types of operations that are restricted in the at least one bare-metal server when the at least one bare-metal server is operating in the reduced operation state.

20 . The non-transitory computer readable medium of claim 15 , wherein the request configured to solicit a scheduled downtime includes an initial time after which the at least one bare-metal server can be taken offline.

Assignees

• Walmart Apollo Llc

Inventors

• Bothello Gerald
• Roy Surajit
• Phalke Shriniwas
• Singh Sumeet
• Kumar Biswal

Classifications

• H04L67/60

  Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) · CPC title

• H04L67/62 Primary

  Establishing a time schedule for servicing the requests · CPC title

• H04L67/01

  Protocols · CPC title

• H04L41/5074

  Handling of user complaints or trouble tickets · CPC title

• G06F11/0709

  in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title