Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

To test Smartfacts in your infrastructure, you can perform an internal PoC installation. These pages describe the procedure to perform such an internal PoC installation.

Restrictions of a PoC deployment

To simplify the installation process, the following restrictions apply to a PoC installation:

  • The installation will be performed on a single-node Kubernetes cluster using k3s.

  • Smartfacts will not connect to any identity provider. In the PoC you will work with dummy usershat are provisioned in advance.

  • Smartfacts will not send emails to users.

All other functionality will be usable as in a later production deployment.

General steps

For installing as Smartfacts PoC instance perform the following steps.

  1. Prepare your infrastructure

  2. Get access to container and chart registry

  3. Install Smartfacts

Prepare your infrastructure

Create the appropriate Hardware

Provide a server with the following specifications:

  • CPU:

    • minimum: 6 Cores

    • x64 / AMD64 processor - ARM based servers will not work

  • RAM: minimum 32 GB

  • Hard disk: SSD, minimum 150 GB

Create the DNS entries for Smartfacts Server and Subdomains

Set up DNS entries for the following FQDNs

  • <Server-FQDN>

  • smartfacts.<Server-FQDN>

  • camp.<Server-FQDN>

  • identity.<Server-FQDN>

  • oslc.<Server-FQDN>

  • genoslc.<Server-FQDN>

Create an X.509 Certificate

Create the certificates according to the instructions on Creating and testing the Certificates for Smartfacts.

Get credentials and Smartfacts license

Please contact cops@mid.de. We will send you credentials for accessing our container & chart registry and a PoC license.

Install Smartfacts

We recommend that your server can directly acces our container and chart repository. In this case follow the instructions for a Deployment on Kubernetes with Internet Connection.

If your server does not have internet acces, follow the instracionts for a Deployment on Kubernetes without Internet Connection.

  • No labels