Deployment Environments and Requirements

Deployment Planning

To help plan the deployment of Itential's software to your organization's environment, use the following to help define some of the conditions and requirements for building IAP before executing a full deployment. This is not an exhaustive list of questions, but some of the details to consider to support a smooth experience.

• Will you be deploying IAP in a clustered topology or in stand-alone topology?
• Will you be configuring the VMs manually or using Ansible?
• Do your labs have access to a proxy server that can provide Internet access?
• Do your production servers have access to a proxy server that can provide Internet access?
• Does your organization have internal NPM, yum, and Python registries accessible to labs and production servers?

Physical Servers vs Virtual Machines

The IAP platform and all of its components support both physical servers and virtual machines. Virtual machines (VM) are recommended because they are less expensive and easier to manage as a solution. Moreover, performance appears to be comparable, assuming the VM hardware specifications ("specs") are guaranteed and not shared with other virtual machines.

Performance Limit for Custom Applications

Performance testing shows that increasing the pronghorn.json file size affects IAP performance linearly and causes a processing delay. For pronghorn.json within custom applications, IAP can support up to 4000 methods if the system is running on the recommended Production ENV as defined in the IAP Server section. Workloads above that limit will cause degradation of service.

Production

For production environments, all IAP components should be installed on their own individual servers to properly support high availability (HA).

Lab and Development

For non-production environments the specs may be lowered to provide lower cost options. However, keep in mind that depending on usage, these specs will need to be adjusted. For highly active developer environments with a great number of custom applications, increased CPU, memory, and disk space will be required.

IAP Server

Required IAP production server components are listed below.

The hardware specifications listed above assume an IAP Server with a few custom applications. In situations where a number of custom applications are heavily utilized, or additional IAP backup storage is needed, the CPU, RAM, and disk space allocations will need to be increased.

MongoDB Server

MongoDB server resources required by IAP in a production environment are listed below.

Redis Shared-Token Server

Redis server resources required by IAP in a production environment using multiple IAP servers and shared-tokens are listed below.

RabbitMQ Server

These are the RabbitMQ server resources required by IAP in a production environment.

Alternative Lab and Development Environments

As an alternative solution a single larger VM may be used to run all of the IAP platform components. A lab environment may include MongoDB, Redis, RabbitMQ, and IAP on a single server.