Tenant-controlled cloud updates
US-2018136960-A1 · May 17, 2018 · US
US11095749B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11095749-B2 |
| Application number | US-201916260986-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 29, 2019 |
| Priority date | Jan 29, 2019 |
| Publication date | Aug 17, 2021 |
| Grant date | Aug 17, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
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.
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 time and date when the bare-metal server can be taken offline; receive a response from the client system, the response including a selected downtime that indicates a time period during which the at least one bare-metal server can be taken offline; transition the at least one bare-metal server to an offline state at the selected downtime; generate a ticket in a ticketing system for repair of the bare-metal server, wherein the ticket identifies the at least one component; and generate a second notification to the client system including the request to schedule downtime when the response from the client system is not received within a predetermined time period, wherein the predetermined time period corresponds to a preset hardware scan process. 2. The system of claim 1 , wherein the processor: receives an update to the ticket indicating maintenance of the bare-metal server has been completed; and generates a third notification to the client system including a request to schedule uptime. 3. The system of claim 2 , wherein the processor: transitions the at least one bare-metal server to an online state; and implements at least one predetermined service on the bare-metal server. 4. The system of claim 3 , wherein the at least one predetermined service includes a virtual machine. 5. The system of claim 3 , wherein the processor generates a fourth notification to the client system including an indication that the at least one predetermined service is available. 6. The system of claim 1 , wherein the processor, upon detecting the failure of at least one component of the at least one bare-metal server: disables one or more functions of the bare-metal server. 7. A non-transitory computer readable medium having instructions stored thereon, wherein the instructions, when executed by a processor cause a device 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_that indicates a time period during which the at least one bare-metal server can be taken offline; 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; and generating a second notification to the client system including the request to schedule downtime when the response from the client system is not received within a predetermined time period, wherein the predetermined time period corresponds to a preset hardware scan process. 8. The non-transitory computer readable medium of claim 7 , wherein the instructions further cause the device to perform operations comprising: receiving an update to the ticket indicating maintenance of the bare-metal server has been completed; and generating a third notification to the client system including a request to schedule uptime. 9. The non-transitory computer readable medium of claim 8 , wherein the instructions further cause the device to perform operations comprising: transitioning the at least one bare-metal server to an online state; and implementing at least one predetermined service on the bare-metal server. 10. The non-transitory computer readable medium of claim 9 , wherein the at least one predetermined service includes a virtual machine. 11. The non-transitory computer readable medium of claim 9 , wherein the instructions further cause the device to perform operations comprising generating a fourth notification to the client system including an indication that the at least one predetermined service is available. 12. The non-transitory computer readable medium of claim 7 , wherein the instructions further cause the device to perform operations comprising: disable one or more functions of the bare-metal server prior to transmitting the first notification to the client system. 13. 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 that indicates a time period during which the at least one bare-metal server can be taken offline; 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; and generating a second notification to the client system including the request to schedule downtime when the response from the client system is not received within a predetermined time period, wherein the predetermined time period corresponds to a preset hardware scan process. 14. The method of claim 13 , comprising: receiving an update to the ticket indicating maintenance of the bare-metal server has been completed; and generating a third notification to the client system including a request to schedule uptime. 15. The method of claim 14 , comprising: transitioning the at least one bare-metal server to an online state; and implementing at least one predetermined service on the bare-metal server. 16. The method of claim 15 , wherein the at least one predetermined service includes a virtual machine. 17. The method of claim 15 , comprising generating a fourth notification to the client system including an indication that the at least one predetermined service is available. 18. The method of claim 13 , comprising disabling one or more functions of the bare-metal server prior to transmitting the first notification to the client system.
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
Establishing a time schedule for servicing the requests · CPC title
Protocols · CPC title
Handling of user complaints or trouble tickets · CPC title
in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.