Skip to content
Products
Platform
Developer Tools
Portal

Installation and deployment guide

Last updated on

Credentials to access the system

Section titled “Credentials to access the system”

There are a number of different credentials for accessing the iCAS system after deployment.

Windows login

Section titled “Windows login”

To log in to the Windows server, the local user admin should be used. The associated password is generated randomly and displayed in the Terraform output.

iCAS iAdmin login

Section titled “iCAS iAdmin login”

The default credentials can be used to log in to the iCAS administration tool iAdmin. These can be changed afterwards.

Usernameuser
Passwordpassword
Pin0000

SMB access for business applications

Section titled “SMB access for business applications”

The credentials for the created SMB shares can be found in the log directory (default: C:\iCASDeployment).

Installation process

Section titled “Installation process”

Please do not carry out any manual configurations, changes or server restarts until the deployment process has been completed. This would lead to an uncontrolled interruption, leaving the system in an unusable state.

Once the deployment has been started, the iCAS Server is provided, installed and configured completely automatically. As soon as the Terraform output reports successful deployment, you can connect to the server via the web console in the STACKIT portal, for example. In the first step, the server is deployed and some downstream settings are made. The completion of this step is indicated by a message box in the web console.

The Windows login can then take place. The local user admin is used by default. The associated password is generated randomly and displayed in the Terraform output. After the Windows server is ready, the iCAS installation and configuration is started automatically in the background. This process is indicated by a README file on the desktop. As long as this file exists, the iCAS installation and configuration is not yet complete. No manual changes may be made to the system during this time. The current progress can be viewed in the log file mentioned in the README.

To complete the entire deployment, the server is restarted. The iCAS server can then be used. As soon as the server has been restarted, you can use the system.

Deployment

Section titled “Deployment”

  1. Open a command line prompt.

    For this example we assume a bash shell (e.g. git bash) and that all files (terraform.exe, .env, terraform files and deployment files from GitHub) are located in the same directory.
    If you are not using a bash shell, but another tool, the variables from the .env must be adjusted or set directly in the Terraform files.
    If you have named the .env file differently, replace the file accordingly hereinafter. Screenshot of a Git Bash terminal window opened at the path "/e/iCAS/Terraform". The output displays the results of the "ls" command, listing various configuration files including multiple numbered Terraform files from "00-provider.tf" to "07-icas.tf", a README.md file, an iCAS.env file, and the terraform.exe executable.

  2. Ensure that all values in the .env file are set. Screenshot of a Git Bash terminal window showing the output of the "cat iCAS.env" command. The file contains multiple environment variables defined via "export", including Terraform variable declarations for credential parameters like tenant ID, username, password, project ID, and service account keys, followed by VM infrastructure properties such as flavor, availability zone, storage options, and network range configurations.

  3. Ensure that all values in the iCAS configuration file 03-config_data are set. Screenshot of a Git Bash terminal window displaying the JSON configuration content of the "03-config_data" file using the "cat" command. The JSON structure includes nested objects for MailConfiguration, S3Configuration with predefined endpoint URL and variable keys, and an Applications block defining properties like share name, retention value, and compression for "Custom Autocommit" and "Custom ReadOnly" applications.

  4. Initialize the.env variables.

    Terminal window
    source.env

    Screenshot of a Git Bash terminal window showing the execution of the command "source iCAS.env" at the path "/e/iCAS/Terraform". The command completes successfully without returning any terminal output, returning directly to the command prompt.

  5. Initialize the environment (only required during the first execution).

    Terminal window
    terraform init

    Screenshot of a Git Bash terminal window showing the output of the "./terraform.exe init" command. The terminal logs the initialization of the backend and the successful download and installation of provider plugins for OpenStack, STACKIT, HashiCorp Random, and HashiCorp Template. It concludes with a green confirmation message stating "Terraform has been successfully initialized!".

  6. Plan the deployment (optional).

    Terminal window
    terraform plan

    Screenshot of a Git Bash terminal window showing the initial output of the "./terraform.exe plan" command. The log shows a data template file being read successfully, followed by an explanation of the plan symbols, noting that "plus" indicates a create action and "less than" indicates a data resource read action. Screenshot of a Git Bash terminal window displaying the summary of a "terraform plan" execution. The text specifies "Plan: 19 to add, 0 to change, 0 to destroy" and indicates a new output variable "+ windows_password = (known after apply)". A note at the bottom warns that the plan was not saved using the "-out" option.

  7. Run the deployment.

    Terminal window
    terraform apply

    Screenshot of a Git Bash terminal window showing the initial execution of the "./terraform.exe apply" command at the path "/e/iCAS/Terraform". The first output log line indicates that a data template file is being read. Check the displayed info and enter ‘yes’ to start the deployment.
    Screenshot of a Git Bash terminal window displaying the completed Terraform execution output block. Below the green heading "Outputs:", the generated "windows_password" value is displayed, though heavily blurred for credential security. Write down the Windows password for future use.

  8. Wait until the first deployment step is finished and displayed by a message box. Screenshot of a Windows message box popup. The title bar reads "Message from 1/22/2024 11 AM". The message text states "We have completed the access configuration, you can log in now." with an "OK" button at the bottom right ready to be clicked.

  9. Now it is possible to log in. The still running iCAS installation is displayed by a text file on the desktop. Close-up screenshot of a desktop file icon. The icon features a white document sheet symbol on a light blue background, with the text overlay reading "README - iCAS installation in progress".

  10. Wait until the server restarts automatically. This could take some time. After the restart and a log in the iCAS installation is finished.

Additional information

Section titled “Additional information”

If the iCAS VM is to be used productively, please contact the iTernity Sales Team to discuss the next steps.

If you have any questions or problems with the deployment, please contact STACKIT Support or iTernity Support, depending on the area of your request.
For requests regarding Terraform deployment and virtual infrastructure, please contact STACKIT.
For requests regarding the iCAS installation, please contact iTernity.