Versions Compared

Old Version 7

changes.mady.by.user Nirav Patel

Saved on

compared with

New Version Current

changes.mady.by.user Nirav Patel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Containerization allows EmpowerID to be deployed in three primary ways:

  1. The EmpowerID SaaS option alleviates all infrastructure concerns, allowing you to focus on solving business needs with EmpowerID on day one. EmpowerID SaaS runs on a fully redundant Microsoft Azure infrastructure in the region of your choice, with all aspects of management and monitoring handled by our infrastructure team. EmpowerID SaaS deployments are appropriately sized to balance your organization’s demanding SLAs with costs and scaled as and when needed. Additional service options are available for SaaS customers to offload all EmpowerID management tasks, including configuration management, converting their SaaS EmpowerID into a fully managed service. All managed service offerings can be phased out as a customer develops their own internally trained support staff.

  2. Organizations can self-host EmpowerID in their own private Microsoft Azure tenant. Our team can provide any level of support, ranging from consulting to assist your engineers in designing your infrastructure to offering a full-managed service to run and manage your EmpowerID installation. Support for other public cloud platforms such as Amazon Web Services (AWS) is in beta now.

  3. An on-premise installation of EmpowerID allows an organization to manage Cloud and on-premise systems but run EmpowerID from their own data centers. If these organizations run Kubernetes clusters today to host other services, then running EmpowerID containers on-premises is easily accomplished.

...

Organizations that want to install EmpowerID using modern architectures can leverage containerization to lessen the footprint associated with a full on-premise or cloud-hosted installation. To facilitate this, EmpowerID provides OCI-compliant images of the product, allowing a fully functional instance of EmpowerID to be easily deployed as a standalone lab on a single desktop or as an orchestrated enterprise-ready environment using Kubernetes or other modern container orchestrators.

...

To run EmpowerID images, the following requirements must be met:

Container orchestrator / cluster with Windows node support

Container Orchestrator

Any existing modern OCI-compliant orchestrator with support for Windows nodes and workloads

-or- Docker Swarm, to be replaced with a low-footprint Kubernetes distribution when ready


Windows Node Requirements

  • Windows Server 1809 (LTSC)

  • 8 Cores

  • 64gb mem

  • 250gb drive

Linux Node Requirements (May vary depending on optional components chosen)

  • Kubernetes standards

Ancillary Requirements

  • Log aggregation capabilities within cluster (for diagnostics and support)

  • Cluster monitoring

  • Git Repo (for customization management)

SQL Requirements (typically not containerized)


Processor


8 processor cores required, more recommended based on usage scenario.


Memory



64 GB required, more recommended based on usage scenario.

Disk

  • Fast SSD-Based Disks

  • Separate Drive for OS

  • Separate Drive for Application

Note

Each SQL server should follow Microsoft’s best practice design, utilizing different disk spindles for OS, Logs, Data, and backups. At a minimum, EmpowerID needs the log drive and data drive to have the below available space. Depending on the number of objects in your environment, disk space needs may be significantly higher.

  • Log Drive: 200 GB. This is to accommodate large transaction log growth in the event of extended processes.

  • Data Drive: 200 GB. We anticipate the database will be 5-10 GB on initial creation. The growth rate will depend on actual use and transaction level.

Provided by EmpowerID

The following are components provided by EmpowerID for deployment needs:

...