Vendor non-specific computer server software system

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.

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.