Self-service operation for bare-metal servers

US11716407B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11716407-B2
Application numberUS-202117379891-A
CountryUS
Kind codeB2
Filing dateJul 19, 2021
Priority dateJan 29, 2019
Publication dateAug 1, 2023
Grant dateAug 1, 2023

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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

Opening claim text (preview).

What is claimed is: 1. A system comprising a non-transitory memory having instructions stored thereon, and a processor configured to read the instructions 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; generate a ticket in a ticketing system for repair of the bare-metal server, wherein the ticket identifies the at least one component; 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 at the scheduled uptime. 2. 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. 3. The system of claim 2 , wherein the at least one bare-metal server is prohibited from generating new instances of applications, performing restarts, and updating when in the reduced operation state. 4. The system of claim 2 , 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. 5. 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. 6. 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. 7. 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; generating a ticket in a ticketing system for repair of the bare-metal server, wherein the ticket identifies the at least one component, 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 at the scheduled uptime. 8. The method of claim 7 , 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. 9. The method of claim 8 , wherein the at least one bare-metal server is prohibited from generating new instances of applications, performing restarts, and updating when in the reduced operation state. 10. The method of claim 8 , 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. 11. The method of claim 7 , 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. 12. The method of claim 7 , 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. 13. 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; generating a ticket in a ticketing system for repair of the bare-metal server, wherein the ticket identifies the at least one component; 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 at the scheduled uptime. 14. The non-transitory computer readable medium of claim 13 , 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. 15. The non-transitory computer readable medium of claim 14 , wherein the at least one bare-metal server is prohibited from generating new instances of applications, performing restarts, and updating when in the reduced operation state. 16. The non-transitory computer readable medium of claim 14 , 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. 17. The non-transitory computer readable medium of claim 13 , 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

Inventors

Classifications

  • H04L67/60Primary

    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/62Primary

    Establishing a time schedule for servicing the requests · CPC title

  • Cellulose sulfate · CPC title

  • from organic cellulose esters or ethers, e.g. cellulose acetate · CPC title

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

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11716407B2 cover?
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 clie…
Who is the assignee on this patent?
Walmart Apollo Llc
What technology area does this patent fall under?
Primary CPC classification H04L67/60. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 01 2023 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 7 related publications on this page (citations in our corpus or others sharing the same primary CPC).