Cisco Server Provisioner 6.6 User's Guide ("Chuck Berry")

Architecture and Components

Hide Navigation Pane

Architecture and Components

Previous topic Next topic No expanding text in this topic  

Architecture and Components

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function Mail us feedback on this topic!  

 

Interface Layer:

oBrowser-based graphical user interface (PHP) for:

Creation of system-specific (“MAC-Specific”) provisioning role templates that define an operating system and optionally application installation and configuration

Assignment of provisioning role templates, networking configuration and business rules to individual systems

Creation of MAC-Specific imaging roles and business rules

Creation of system-independent (“MAC-Independent”) provisioning roles and client-side, pre-boot, manual OS selection screen

Application Programming Interface with GUI-based “teaching mode”

Scripts (perl) for:

oOS media uploading

oDriver integration

oProvisioner PXE Server configuration

Services Layer (Java):

oWeb server

oLow-level services (tftp, ftp, binl, bootp, etc.) intercept PXE (Preboot eXecution Environment) requests sent by the client system or virtual machine to the Provisioner PXE Server and initiate action based on the business rules set by the IT user using the graphical user interface, or by external applications using the Application Programming Interface (API)

Database (PostgreSQL) Layer:

oStores relevant information for each system’s provisioning and imaging roles

File System Layer:

oOS Media and drivers

oControl/Configuration Files

oLog files

oImaging files