IP Library › Granted Patent US 11,249,742
Granted Patent B1
US 11,249,742 · App. 17/033,193 · Granted Feb 15, 2022

Systems and methods for zero-touch infrastructure build automation

Inventor: Neel K. Paudel (Plain City, OH)
Assignee: JPMORGAN CHASE BANK, N.A.
G06F8/63G06F16/2445
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,249,742
App. No.
17/033,193
Granted
Feb 15, 2022
Kind
B1
Abstract

Systems and methods for zero-touch infrastructure build automation are disclosed. A method may include: receiving an input file including a hardware requirement and an installation type; validating hardware requirements for the server installation on a target host; calling a build API to create a plurality of active directory accounts and to assign required roles; creating a service account, a system account, and a user account; validating and approving the service account, the system account, and the user account, and creating a configuration file; downloading a build automation packet on the target host based; provisioning a database instance to the target host; downloading and extracting server and binary tools from a source location to the target host; initiating server unattended installation on the target host; installing client connectivity and configuration tools on the target host; and installing organization-specific tools on the target host.

Claims (45)

1. A method for zero-touch infrastructure build automation of a server on a target host, comprising:

in an information processing apparatus comprising at least one computer processor:

receiving an input file for a server build comprising a payload file including a hardware requirement and an installation type;

validating hardware requirements for the server installation on a target host based on hardware requirements;

calling a build API (Application Programming Interface) to create a plurality of active directory accounts and to assign required roles to perform the server build and for running services;

creating a service account, a system account, and a user account;

validating and approving the service account, the system account, and the user account, and creating a configuration file;

downloading a build automation packet on the target host based on the input file;

provisioning a database instance to the target host;

downloading and extracting server and binary tools from a source location to the target host;

initiating server unattended installation on the target host using the configuration file and a template that is based on the installation type;

installing client connectivity and configuration tools on the target host; and

installing organization-specific tools on the target host.

2. The method of claim 1 , wherein the installation type is one of a standalone server installation, prepared failover cluster server installation, and a complete failover cluster server installation.

3. The method of claim 1 , wherein the hardware requirements comprise a memory requirement, a storage requirement, and a CPU (Central Processing Unit) requirement.

4. The method of claim 1 , further comprising:

creating a non-human account for the server build; and

adding the non-human account to an admin group at an operating system level.

5. The method of claim 1 , wherein the configuration file is generated based on a file generation task value in the input file and a template for the installation type.

6. The method of claim 1 , wherein the server tools comprise SQL (Structured Query Language) server tools.

7. The method of claim 1 , wherein the organization-specific tools comprise security tools.

8. The method of claim 1 , wherein the server is installed on a plurality of target hosts.

9. A system for zero-touch infrastructure build automation of a server on a target host, comprising:

a production file server comprising a computer processor and executing a build automation program;

an application server that provides an input file comprising a payload file including a hardware requirement and an installation type for a server build; and

a target host;

wherein:

the build automation program receives an input file for a server build comprising a payload file including a hardware requirement and an installation type;

the build automation program validates hardware requirements for the server installation on a target host based on hardware requirements;

the build automation program calls a build API to create a plurality of active directory accounts and to assign required roles to perform the server build and for running services;

the build automation program creates service account, a system account, and a user account;

the build automation program validates and approves the service account, the system account, and the user account, and creating a configuration file;

the build automation program downloads a build automation packet on the target host based on the input file;

the build automation program provisions a database instance to the target host;

the build automation program downloads and extracts server and binary tools from a source location to the target host;

the build automation program initiates server unattended installation on the target host using the configuration file and a template that is based on the installation type;

the build automation program installs client connectivity and configuration tools on the target host; and

the build automation program installs organization-specific tools on the target host.

10. The system of claim 9 , wherein the installation type is one of a standalone server installation, prepared failover cluster server installation, and a complete failover cluster server installation.

11. The system of claim 9 , wherein the hardware requirements comprise a memory requirement, a storage requirement, and a CPU requirement.

12. The system of claim 9 , wherein the build automation program creates a non-human account for the server build and adds the non-human account to an admin group at an operating system level.

13. The system of claim 9 , wherein the configuration file is generated based on a file generation task value in the input file and a template for the installation type.

14. The system of claim 9 , wherein the server tools comprise SQL server tools.

15. The system of claim 9 , wherein the organization-specific tools comprise security tools.

16. The system of claim 9 , wherein the server is installed on a plurality of target hosts.

Cited By (1)
US 12,675,449