Vendor non-specific computer server software system

• US 10,652,362 B1
• Filed: 06/28/2018
• Issued: 05/12/2020
• Est. Priority Date: 06/28/2018
• Status: Active Grant

• Current Assignee: State Farm Mutual Automobile Insurance Company (State Farm)
• Original Assignee: State Farm Mutual Automobile Insurance Company (State Farm)
• Inventors: Kudari, Elia, Callighan, Shaun, Eberle, Daniel Ray, Carlson, Michael Dale, Trovillion, Gary D.
• Primary Examiner(s): Springer, James E
• Application Number:
  US16/022,015
• Time in Patent Office: 684 Days
• Field of Search: 709220
• CPC Class Codes: H04L 41/0253 using browsers or web-pages for accessing management information
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0883 Semiautomatic configuration, e.g. proposals from system
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/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

Abstract

A computer server software system implemented on a computing device comprises a bare metal automation interface, a request processor, a scheduler, a vendor non-specific bare metal interface, and an orchestration engine. The bare metal automation interface is configured to receive requests for configuration of one or more of a plurality of servers. The request processor is configured to receive the requests from the bare metal automation interface and to forward the requests. The scheduler is configured to receive instructions from a runtime environment in which the computer server software system operates and forward the instructions. The vendor non-specific bare metal interface is configured to interface with a plurality of vendor-specific server interfaces, wherein each vendor-specific server interface communicates with a server from the specific vendor. The orchestration engine is configured to execute a workflow for the requests from the request processor and for the instructions from the scheduler.

Claims

1. A computer server software system implemented on a computing device, the system comprising:

a bare metal automation interface configured to receive requests for configuration of one or more of a plurality of servers from a plurality of different vendors;

a request processor configured to receive the requests from the bare metal automation interface and forward the requests;

a scheduler configured to receive instructions from a runtime environment in which the computer server software system operates and forward the instructions;

a vendor non-specific bare metal interface configured to interface with a plurality of vendor-specific server interfaces, each vendor-specific server interface communicating with a server of the plurality of servers from a specific vendor of the plurality of different vendors; and

an orchestration engine configured to execute a workflow for the requests from the request processor and for the instructions from the scheduler to configure the server from the specific vendor.

2. The computer server software system of claim 1, further comprising an alert and notification generator configured to notify users of a status of a request or to alert system administrators if an error occurs.

3. The computer server software system of claim 1, further comprising an authentication and authorization interface configured to forward a user'"'"'s credentials to a lightweight directory access protocol device or an active directory device.

4. The computer server software system of claim 1, further comprising a persistence storage interface configured to forward data regarding the servers to a bare metal asset information database.

5. The computer server software system of claim 1, further comprising a GIT interface configured to forward a user'"'"'s credentials to a GIT system.

6. The computer server software system of claim 1, wherein the bare metal automation interface is further configured to receive data from a user including a user'"'"'s name, a password, and/or tokens.

7. The computer server software system of claim 1, wherein the scheduler is further configured to forward the instructions to the orchestration engine.

8. The computer server software system of claim 1, wherein the vendor non-specific bare metal interface is further configured to receive vendor-non-specific commands intended for a server and to transmit corresponding vendor-specific commands to the vendor-specific server interface for the server.

9. The computer server software system of claim 1, wherein the bare metal automation interface is configured to receive requests from a user using a web browser.

10. The computer server software system of claim 1, wherein the bare metal automation interface is configured to receive requests from other systems using a representational state transfer and simple object access protocol interface.

11. A computer server software system implemented on a computing device, the system comprising:

a bare metal automation interface configured to receive requests for configuration of one or more of a plurality of servers from a plurality of different vendors, the requests being received from a user using a web browser, and other systems using a representational state transfer and simple object access protocol interface;

a request processor configured to receive the requests from the bare metal automation interface and forward the requests;

a scheduler configured to receive instructions from a runtime environment in which the computer server software system operates and forward the instructions;

a vendor non-specific bare metal interface configured to interface with a plurality of vendor-specific server interfaces, each vendor-specific server interface communicating with a server of the plurality of servers from a specific vendor of the plurality of different vendors, and to receive vendor-non-specific commands intended for a server and to transmit corresponding vendor-specific commands to the vendor-specific server interface for the server; and

an orchestration engine configured to execute a workflow for the requests from the request processor and for the instructions from the scheduler to configure the server from the specific vendor.

12. The computer server software system of claim 11, further comprising an alert and notification generator configured to notify users of a status of a request or to alert system administrators if an error occurs.

13. The computer server software system of claim 11, further comprising an authentication and authorization interface configured to forward a user'"'"'s credentials to a lightweight directory access protocol device or an active directory device.

14. The computer server software system of claim 11, further comprising a persistence storage interface configured to forward data regarding the servers to a bare metal asset information database.

15. The computer server software system of claim 11, further comprising a GIT interface configured to forward a user'"'"'s credentials to a GIT system.

16. The computer server software system of claim 11, wherein the bare metal automation interface is further configured to receive data from a user including a user'"'"'s name, a password, and/or tokens.

17. The computer server software system of claim 11, wherein the scheduler is further configured to forward the instructions to the orchestration engine.

18. A computer server software system implemented on a computing device, the system comprising:

a bare metal automation interface configured to receive requests for configuration of one or more of a plurality of servers from a plurality of different vendors;

a request processor configured to receive the requests from the bare metal automation interface and forward the requests;

a scheduler configured to receive instructions from a runtime environment in which the computer server software system operates and forward the instructions;

an alert and notification generator configured to notify users of a status of a request or to alert system administrators if an error occurs;

an authentication and authorization interface configured to forward a user'"'"'s credentials to a lightweight directory access protocol device or an active directory device;

a persistence storage interface configured to forward data regarding the servers to a bare metal asset information database;

a GIT interface configured to forward a user'"'"'s credentials to a GIT system;

a vendor non-specific bare metal interface configured to interface with a plurality of vendor-specific server interfaces, each vendor-specific server interface communicating with a server of the plurality of servers from a specific vendor of the plurality of different vendors; and

an orchestration engine configured to execute a workflow for the requests from the request processor and for the instructions from the scheduler to configure the server from the specific vendor.

19. The computer server software system of claim 18, wherein the vendor non-specific bare metal interface is further configured to receive vendor-non-specific commands intended for a server and to transmit corresponding vendor-specific commands to the vendor-specific server interface for the server.

20. The computer server software system of claim 18, wherein the bare metal automation interface is configured to receive requests from a user using a web browser and receive requests from other systems using a representational state transfer and simple object access protocol interface.