1. Introduction

This guide is intended for administrators planning to set up a Techila Virtual Server in their Techila Distributed Computing Engine (TDCE) environment. If you are unfamiliar with the terminology or theory on how the TDCE system functions refer to Introduction to Techila Distributed Computing Engine for details. Please note that paths and screen captures presented in this document may differ from your system.

The structure of this document is as follows:

Preparation contains a list of prerequisites that must be met before proceeding with the Techila Virtual Server installation.

Preparing the Installation Packages contains steps for preparing the installation packages containing the Techila Virtual Server installation files and the Techila License file. These files will be required later in the installation process. After performing the steps described in this Chapter, you should have access to all required files used in the installation.

Deploying the Techila Virtual Server contains all the necessary steps for configuring the Techila Virtual Server. The configuration involves deploying the virtual machine to VMware ESXi by using the vSphere Client. Instructions are also provided for installing the Open VM Tools package and for adjusting the time zone of the Techila Virtual Server. After performing the steps described in this Chapter, you should be able to log in to the Techila Web Interface.

Updating the Techila License contains instructions for uploading the Techila License file to the Techila Virtual Server. A valid Techila License is required to perform computations in the TDCE environment. After performing the steps described in this Chapter you can continue by adding Techila Workers and End-Users to the TDCE system.

Adding Techila Workers shortly introduces how to add Techila Workers to the TDCE system. More thorough instructions are provided in the document Techila Distributed Computing Engine Administration Guide and in the operating system specific Techila Worker installation guides.

Adding End-Users contains step-by-step instructions on how you can add your first End-User to the Techila system.

Creating a Test Project contains instructions on how you can create a test Project using the End-User Key created during the process described in Adding End-Users.

Creating Runtime Bundles introduces the concept of Runtime Bundles, which are used if you plan on using MATLAB, R, Python or Perl in your TDCE environment.

Appendix contains a collection of useful information such as login credentials to the Techila Web Interface, the location and password Master Administrator Keystore and the login credentials of the techila-admin user for the Techila Virtual Server.

2. Preparation

Before proceeding, please verify that you have:

  • Techila Virtual Server installation file

  • Techila License package

If you do not have Techila Virtual Server installation file, please download it from Techila Extranet and save the file to an easily accessible location.

If you do not have access to Techila Extranet, please contact Techila Technologies to request for Techila Extranet access.

If you do not have Techila License package, please contact Techila Technologies.

You will also need to have the following virtualization software product installed on the server you plan on using as the host for the Techila Virtual Server.

  • VMware ESXi

The procedures described in this document have been tested with VMware ESXi 5.0 Other versions of the VMware ESXi software may also be compatible, but full functionality is not guaranteed.

In addition, you will also need the following software for deploying and configuring the Techila Virtual Server.

  • VMware vSphere Client

2.1. Master Administrator Key Practices

Please refer to Techila Distributed Computing Engine Administration Guide for details about Master Administrator Key and related recommended practices.

3. Preparing the Installation Packages

This Chapter contains instructions on preparing the Techila Virtual Server installation file and Techila License package.

3.1. Preparing the Techila Virtual Server Installation Package

Locate the Techila Virtual Server installation file. In the figure below, a Techila Virtual Server installation file is located in C:\techilavm. This file will need to be stored in a location that can be accessed when using the vSphere Client to deploy the Techila Virtual Server to the ESXi environment.

image006
Figure 1. The Techila Virtual Server installation file. The file name also contains a timestamp, which contains information on when the package was created. This timestamp might be different in your package.

3.2. Extracting the Techila License Package

  1. Locate the Techila License package. In the figure below, a Techila License package is located in C:\Techilalicense.

    image007
    Figure 2. The Techila License is delivered as a ZIP file.
  2. Extract the Techila License package to a location that can be accessed when uploading the Techila License. After extraction, a Techila License file will be available as illustrated below. This file will be uploaded to the Techila Virtual Server later in the installation process.

    image008
    Figure 3. A Techila License file can be recognized from the .license suffix.

4. Deploying the Techila Virtual Server

  1. Launch the VMware vSphere Client. The login window will be displayed prompting for the host IP address and login credentials.

    image009
    Figure 4. The VMware vSphere Client login screen.
  2. Enter your ESXi host address and your login credentials. Click the Login button to login.

    image010
    Figure 5. Entering ESXi host network address and login credentials. In this example, the connection would be established to IP address 10.50.1.42 as the user root.
  3. After logging in, click File and click on the Deploy OVF Template…​ menu item.

    image011
    Figure 6. Choosing the Deploy OVF Template menu item.
  4. After clicking on the menu item, the Deploy OVF Template window will be displayed. Click the Browse button.

    image012
    Figure 7. The initial view before any OVF templates have been selected.
  5. After clicking the Browse button a file dialog window will be displayed. Navigate to the directory where you extracted the files in the Techila Virtual Server package. Select the file Techila Virtual Server installation file (.ova suffix) and click the Open button.

    image013
    Figure 8. Selecting the TechilaVM.ova file.
  6. The view will switch back to the Deploy OVF Template window and the location of the .ova file you chose should now be visible in the text field as shown below. Click the Next button to continue.

    image014
    Figure 9. The path of the ova file should be visible
  7. A window containing OVF template details will be displayed. Click Next to continue.

    image015
    Figure 10. The OVF Template Details window.
  8. A window prompting for the name of the virtual machine will be displayed. If you wish to modify the name of the virtual machine, replace the default name with a name of your choosing. Click Next to continue.

    image016
    Figure 11. Specifying the name of the Techila Virtual Server.
  9. A window prompting for format of the virtual disks will be displayed, depending on your host system specifications either choose thin or thick provisioning. After you have selected the format, click Next to continue.

    image017
    Figure 12. Choosing the disk format type.
  10. A windows prompting for network mapping will be displayed. Choose which network you want to use and click Next to continue.

    network
    Figure 13. Choosing the network.
  11. A window containing the deployment settings will be displayed. Click Finish to deploy the Techila Virtual Server.

    image018
    Figure 14. The Techila Virtual Server deployment settings.
  12. A deployment progress indicator will be displayed. Depending on the network bandwidth in your environment, the deployment process can take several minutes.

    image019
    Figure 15. Deployment progress indicator.
  13. After the deployment process has been completed, a message will be displayed indicating a successful deployment. Click Close.

    image020
    Figure 16. Notification of a successful Techila Virtual Server deployment
  14. Return to the VMware vSphere Client. Click the Edit Settings icon to check the settings of the Techila Virtual Server and modify values according to your requirements.

    image021
    Figure 17. Edit the settings of the virtual machine.

    Typical settings that might need modifications are:

    • Number of CPU cores

    • Amount of RAM

    • Size of the data hard disk (hard disk 2)

      image022
      Figure 18. Modify the virtual machine properties according to your specifications.

      Note! Modifying the size of the data hard disk (Hard disk 2) must be done before you power on the Techila Virtual Server for the first time. System hard disk (Hard disk 1) size cannot be changed. See Modifying the Size of the Data Hard Disk for information on how to modify the data hard disk size before powering on the Techila Virtual Server

      The number of CPU cores and amount of RAM can also be modified after starting the Techila Virtual Server.

      After modifying the settings, click the OK button and close the configuration window.

  15. After configuring the virtual machine properties, you can power on the Techila Virtual Server. Select the virtual machine and click the Power on button located in the Summary tab to start it.

    image023
    Figure 19. Powering on the Techila Virtual Server.
  16. After powering on the virtual machine, open the right-click menu for the Techila Virtual Server and select Open Console from the menu.

    image024
    Figure 20. The Open Console menu item can be used to display the console of the Techila Virtual Server.
  17. The console for the Techila Virtual Server will be displayed, which will contain information on the startup process. The startup process will take several minutes.

    After the startup process has completed, the Techila Virtual Server will be operational. A login prompt will also be displayed, which can be used to login to the Techila Virtual Server.

  18. Log in by using the login credentials shown below:

    Login: techila-admin
    Password: eizolee0

    Note! By default, SSH connections will be allowed from all IP addresses unless the Techila Server has been isolated to a separate network.

    Note! Software fail2ban is installed on the Techila Server. This software will ban IP address after six failed attempts. Ban is 600 seconds.

    image025
    Figure 21. After logging in, important information on the Techila Virtual Server will be displayed.

    Note! It is strongly recommended that you change the password used to login to the Techila Virtual Server before proceeding. The password can be changed with the passwd command.

    The vSphere Client should display the IP-address of the Techila Virtual Server under the General category. Note! The displayed IP-address will be needed later when adding Techila Workers to the Techila Distributed Computing Engine (TDCE) environment and when configuring the techila_settings.ini file to connect to the Techila Server.

    image026
    Figure 22. The IP address of the Techila Server will be visible in the Summary tab. In this example the IP Address of the Techila Server is 10.50.1.187.

    The Techila Virtual Server is now operational.

  19. Optional If you wish to adjust the Techila Server time, please use the command shown below to select an appropriate time-zone.

    sudo dpkg-reconfigure tzdata
  20. Optional If you wish to change the configured Debian mirror site used for operating system updates, please follow instructions described on the following web site:

  21. Optional If you wish to change the Techila Server firewall configuration to only allow connections from a specific IP address range, please follow instructions in Configuring the Techila Server Firewall Note! It is recommended that the firewall is configured to only allow SSH connections from IP addresses used by Techila Administrators

  22. Log out from the Techila Virtual Server by using the command shown below:

    exit

Please continue by Updating the Techila License.

5. Updating the Techila License

This Chapter contains instructions on how to update the license of your Techila Virtual Server. If you do not have access to a Techila License, please contact Techila Technologies. Information on updating the Techila License can also be found in Techila Distributed Computing Engine Administration Guide.

Note! Certain Techila License types require access to Internet based Techila License Server TCP port 80 (HTTP). The license server address will be delivered together with the license file. If no connection can be established, the Techila Server will stop assigning new Jobs to Techila Workers after a certain time period (24 hours). Techila License files that require a connection have the following XML element:

<statsurl>...</statsurl>
  1. Launch your web browser and connect to the Techila Web Interface by entering the network address of the Techila Server in the address bar of the web browser as shown below. The notation <TechilaServerNetworkAddress> should be replaced with the IP address/hostname of the Techila Server that is visible in the summary tab of the vSphere Client.

    https://<TechilaServerNetworkAddress>
  2. Depending on your web browser settings, you may receive a security warning. You can ignore this security warning and continue connecting to the Techila Web Interface

  3. The Techila Web Interface will prompt you for user credentials. Enter the following login credentials to access the Techila Web Interface with administrative access:

    Login: admin
    Password: adminpass

  4. Click the LOGIN button to log in.

    image027
    Figure 23. The Techila Web Interface Login page.
  5. After logging in, your browser will be redirected to the Status Page as illustrated below. Notice that the "Registered to" field contains the value "Unknown" indicating no Techila License is available.

    image028
    Figure 24. View when no Techila Licenses have been uploaded.
  6. Navigate to the "Uploads" page by clicking Admin → Uploads. Click the Browse.. button to open a file dialog window that can be used to select the Techila License file.

    image029
    Figure 25. Opening the file dialog window that can be used to select the Techila License file.
  7. Using the file dialog window, select the Techila License file. This file should be located in the directory you extracted the Techila License package to in Extracting the Techila License Package. After selecting the file, click the Open button.

    image030
    Figure 26. Selecting the Techila License file.
  8. The Techila License file you selected will now be visible in the text field as illustrated below. Click the UPLOAD button to upload the Techila License to the Techila Server.

    image031
    Figure 27. Clicking the UPLOAD button will transfer the Techila License to the Techila Server.
  9. After the upload process is completed, the Techila License will be listed in the Upload Directory table. Tick the checkbox (under the APPROVE button) and click the APPROVE button to approve the License.

    image032
    Figure 28. Tick the checkbox and approve the Techila License by clicking the APPROVE button.
  10. Click the Status page. The Status page will display the Techila License information in the Server Registration Info table as shown below.

    image033
    Figure 29. After uploading the Techila License, the new license information will be visible in the Server Registration Info table on the Status page

Congratulations, your Techila Virtual Server is now ready for use! Please continue by Adding Techila Workers.

6. Adding Techila Workers

Before End-Users can run computational Projects in the Techila Distributed Computing Engine (TDCE) environment, Techila Workers will need to be added to the TDCE environment, and their status needs to be set to "trusted".

Note! In the latest version of the Techila Virtual Server, the Techila Worker Key will be automatically trusted by the Techila Server. If you are using an older version of the Techila Virtual Server, the status of the Techila Worker Key needs to be set to "trusted" by using the Techila Web Interface (Admin ( Keys ( Worker Keys). If you wish to disable automatic trusting, please see instructions in Configuring a Static IP Address for the Techila Server.

Please see Techila Distributed Computing Engine Administration Guide for more detailed instructions on how to install a Techila Worker

Installation instructions for installing the Techila Worker software on different operating systems can be found in the following documents:

Please continue by Adding End-Users.

7. Adding End-Users

The following procedure describes how you can add your first End-User to the Techila Distributed Computing Engine (TDCE) environment.

Note! The steps described in this Chapter use Java applications included in the Techila SDK.

Please ensure that you have Java installed on your computer. Java Platform, Standard Edition 6 (or newer) Java Development Kit (JDK) or Java Runtime Environment (JRE) are supported.

When Java is installed and available from the command line, Java version can be verified with the following command. Please note that executing the command requires that the Java installation path is listed in the PATH environment variable.

java -version
java
Figure 30. Verifying the Java version from the command line.

The process of adding your first End-User to the Techila Distributed Computing Engine system is divided in to the following steps:

7.1. Downloading the Techila SDK

  1. Log in to the Techila Extranet located at:

  2. Click on the End-User Downloads menu item on the right side of the page

  3. Click on the Latest Techila SDK Download link

    image034
    Figure 31. The Techila SDK can be downloaded from the End-User Downloads section in the Techila Extranet
  4. Download the Techila SDK by clicking the Agree and Download button located below the EULA.

    image035
    Figure 32. Clicking the highlighted button will download the Techila SDK.
  5. After clicking on the link, a file download dialog box will be displayed. Choose Save File and click OK to save the file to your computer.

    image036
    Figure 33. Save the TechilaSDK.zip file to your computer.
  6. After the download has finished, extract the TechilaSDK.zip file to your computer.

    image037
    Figure 34. Extracting the TechilaSDK.zip file.
  7. Extracting the zip-file will create a directory named techila which has several subfolders as shown below.

    image038
    Figure 35. Contents of the techila directory.

7.2. Configuring the Techila SDK For Administrator Usage

The next steps will describe how you can download the Administrator Key from the Techila Virtual Server by using a SFTP file transfer program such as FileZilla, Putty pstfp or sftp. The screenshots shown in the following steps are from FileZilla software. (http://filezilla-project.org/)

  1. Launch your SFTP program.

    image039
    Figure 36. The FileZilla main interface.
  2. Enter the connection details that will be used to connect to the Techila Virtual Server.

    Connection setting Example Value Notes

    Host

    sftp://<Techila Server Network Address>

    The IP address of the Techila Server is visible in the Summary tab of the vSphere Client.

    Username

    techila-admin

    -

    Password

    eizolee0

    If you have changed the password for techila-admin user, use the new password.

    Port

    22

    -

    Local site

    <full path>\techila

    Set the path to point to the techila directory, which was created when extracting the TechilaSDK.zip file.

  1. Establish a SFTP connection to your Techila Virtual Server.

    The screenshot below illustrates how to use FileZilla to establish the SFTP connection

    cliimage008
    Figure 37. Establishing an sftp connection to the Techila Server
  2. After establishing connection, navigate to directory /home/techila-admin/userkeys and download the file subadmin1.jks to your computer.

    cliimage009
    Figure 38. Downloading the keystore file.
  3. After downloading the subadmin1.jks file, make a mental note where the file is on located on your computer. This information will be needed in the following steps.

    In the example below, the path of the file is:

    C:\TechilaKeys\subadmin1.jks
    cliimage010
    Figure 39. Check the location of the keystore file and make a mental note of the location.
  4. Navigate to your Techila SDK directory and rename techila_settings.ini.template file to techila_settings.ini.

  5. Open the techila_settings.ini file using a text editor.

  6. Replace the value of the keystore parameter with the path of your subadmin1.jks file. In this example, the path is:

    C:\TechilaKeys\subadmin1.jks

    The configured value is illustrated below.

    cliimage011
    Figure 40. Configuring the location of the keystore file in the techila_settings.ini file.
  7. In the techila_settings.ini file, replace the value of the hostname parameter with the network address of your Techila Virtual Server.

    In the example below, the IP address has been used. This is the same IP address that was used when establishing the SFTP connection to the Techila Virtual Server.

    cliimage012
    Figure 41. Configuring the network address of the Techila Server in the techila_settings.ini file.
  8. Save the changes you made to the techila_settings.ini file and close the text editor. The configuration is now complete.

7.3. Testing the Techila SDK configuration

This Chapter contains instructions how to test the Techila CLI administrator commands.

  1. Launch a command prompt and change your current working directory to techila/lib in the Techila SDK.

    In the example below, the path to the directory is:

    C:\techila\lib
    cliimage016
    Figure 42. Command Prompt window after navigating to techila/lib in the Techila SDK.
  2. Execute the following command in the command prompt to test network connectivity to the Techila Server.

    java -jar techila.jar testsession
  3. When prompted, enter the following keystore password:

    adminpass

    After entering the password, you should get the output illustrated in the screenshot below.

  4. If the network connection test fails, please check that your firewall has been configured to allow network connections from your computer to the Techila Server TCP port 25001.

    cliimage017
    Figure 43. View after a successful network connection test.
  5. Note! By default, the keystore password will be prompted each time you execute a Techila CLI command. If you do not want to be prompted for a password, please use one of the following options:

    Option 1 (recommended)

    1. Create a session to the Techila Server with Techila CLI init command. This command will prompt for the keystore password.

    2. Execute an arbitrary number of Techila CLI administrator commands. You will not be prompted for your keystore password.

    3. Remove the session with Techila CLI unload command.

    Option 2 (not recommended)

    Specify your keystore password in the techila_settings.ini file using the password parameter. After defining the password, you will not be prompted for your keystore password when executing Techila CLI commands.

    In the following steps, Option 1 will be used to create a session with the Techila Server.

  6. Create a session to the Techila Server with the init command using the syntax shown below:

    java -jar techila.jar init

    This is illustrated in the screenshot below:

    cliimage018
    Figure 44. Creating a session.
  7. When prompted, enter the following keystore password:

    adminpass

  8. This step will test that the Techila Account has the admin checkbox ticked in the Techila Web Interface.

    Execute the following Techila CLI administrator command to get a list of Techila Accounts:

    java -jar techila.jar admin listusers

    After executing the command, a list of Techila Accounts should be displayed as illustrated in the screenshot below. Please note that the list generated in your Techila environment might be different than the one illustrated here.

    cliimage019
    Figure 45. List of Techila Accounts returned by the listusers command.
  9. This step will test that the subadmin1.jks keystore file contains an administrator key and that you are using the correct password to access the administrator key.

    Note! The test will be done by using the adduser command, which will create a Techila Account and a keystore containing an End-User Key. Techila Accounts cannot be easily removed due to accounting mechanics. This means that if you execute the example command shown below, a Techila Account with login exampleuser will be created. This will not cause any problems to the operation of the Techila Server, but means that you cannot create another Techila Account with the same login value (exampleuser).

    Execute the following example command to create the End-User`s keystore file and Techila Account.

    Note! Modify the path defined in adminkeystore parameter to match the location of your subadmin1.jks file.

    java -jar techila.jar admin adduser adminkeystore=C:\AWSDeployment\subadmin1.jks adminpass=adminpass userkeystore=C:\techila\exampleuser.jks userpass=userpass123 validity=730 login=exampleuser username="Example User"

    Executing the command should generate similar output as illustrated in the screenshot below:

    cliimage020
    Figure 46. Output generated after executing the adduser command.
  10. The new Techila Account will now be visible when getting the list of Techila Accounts with command:

    java -jar techila.jar admin listusers
    cliimage021
    Figure 47. The new Techila Account will be visible when executing the listusers command.

    The Techila Administrator CLI has now been tested successfully. You are now able to execute any Techila CLI administrator command.

  11. Execute the unload command to remove the session:

    java -jar techila.jar unload

    This is illustrated in the screenshot below:

    cliimage022
    Figure 48. Remove the session with the unload command.

7.4. Adding an End-User using the Techila CLI

This Chapter contains instructions for adding a new End-User using the Techila Administrator CLI adduser command.

  1. Launch a command prompt/terminal and navigate to <full path>\techila\lib in the Techila SDK.

    adminimage035
    Figure 49. A command prompt window.
  2. Create a new End-User with the Techila Admin CLI adduser command. The general syntax of the command is shown below. Optional parameters are enclosed in square brackets [].

    java -jar techila.jar admin  adduser [adminkeystore=<keystore>] [index=<indexfile>] [adminalias=<alias>] [adminpass=<password>] [userkeystore=<keystore.jks>] [useralias=<useralias>] login=<login> username="<user name>" [dn=<DN>] userpass=<userpass> [group="<worker group>"] [validity=<validity period>] [keyonly=<true|false>]

    Default values of the optional parameter are shown below:

    Parameter Default Value Description

    adminkeystore

    /home/techila-admin/admin/admin.jks

    Location of the keystore that contains the admin key

    index

    <path of admin.jks>/index.xml

    By default, the index.xml will be read from the same directory as defined in adminkeystore

    adminalias

    admin

    The alias of the admin key in the admin keystore

    adminpass

    adminpass

    The password of the admin keystore file

    userkeystore

    <userlogin>.jks

    The name of the End-User Keystore that will be created. By default, the name same as defined in the parameter userlogin

    useralias

    <userlogin>

    The alias of the End-User Key that will be created. By default, the alias will be same as defined in the parameter userlogin

    dn

    CN=<username> <system clock timestamp in milliseconds>

    The distinguished name of the End-User Key. By default, value will be set based on the username parameter and the system clock timestamp

    group

    All Workers

    Techila Worker Groups that will be assigned to the End-User. By default, the All Workers Techila Worker Group will be assigned.

    validity

    365

    The validity of the End-User Key. By default the validity period is 365 days.

    An example syntax for the adduser command is shown below.

    java -jar techila.jar admin adduser adminkeystore=C:\techila\subadmin1.jks adminalias=admin adminpass=adminpass userkeystore=C:\techila\johndoe.jks userpass=userpass123 useralias=johndoe validity=365 login=johndoe username="John Doe" group="Example Worker Group" keyonly=false

    The parameters used in the example command are explained below.

    The first three parameters (adminkeystore, adminalias, adminpass) in the example are used to define which Administrator Key is accessed. The syntax used accesses the Administrator Key in the C:\techila\subadmin1.jks keystore file. This keystore contains the alias admin and the password used to access the keystore is adminpass.

    The following four parameters (userkeystore, useralias, userpass, validity) in the example define the properties of the End-User Key that will be created. The syntax used will create a keystore file in C:\techila\johndoe.jks. The alias of this keystore will be set to johndoe and the keystore will be protected with the password userpass123.

    The remaining parameters used in the example define the properties of the Techila Web Interface account that will be created for the End-User. The syntax used will create a Techila Web Interface account with the login johndoe (login parameter) and password userpass123 (userpass parameter). Name John Doe (username parameter) will be displayed when the user is logged in the Techila Web Interface. The Techila Worker Group named Example Worker Group (group parameter) will be automatically assigned to the End-User. The validity period of the End-User Key will be 365, which means 365 days. The value of the keyonly parameter is false, meaning both the End-User Key and Techila Web Interface account will be created.

  3. After executing the command, you will be prompted for the End-User Keystore password. Note! This is the password of the End-User Key that is assigned to your administrative Techila Web Interface account, not the End-User password specified in the command above.

    Enter the password and click OK to continue.

    adminimage037
    Figure 50. Entering the keystore password.
  4. After you have entered the keystore password, the End-User Key and Techila Web Interface account will be created. After the command has been executed, the view should resemble the one shown below.

    adminimage038
    Figure 51. View after executing the adduser command.

The End-User Key is now ready for use and can be used for creating computational Projects. Please note that in order for End-User to be able to create computational Projects, you will need to give the End-User the following information and files:

  • The keystore containing the End-User Key. The location and name of the file were defined in Step 2 with parameter userkeystore.

  • The password of the keystore. This is the password that was specified in Step 2 with parameter userpass.

  • The network address of the Techila Server

  • The port of the Techila Server (default 25001)

8. Creating a Test Project

This Chapter contains a walkthrough how you can create a simple test Project for testing purposes by using the End-User Key created in Adding End-Users.

Note! In order for the test Project to be completed successfully, at least one Techila Worker with a Microsoft Windows or Linux operating system must be available. At least one Techila Worker also must be in the Running state. The statuses of active Techila Workers can be viewed in the Techila Web Interface in the Workers ( All Workers page. The screenshot below illustrates a valid test environment.

image062
Figure 52. Techila Workers with the Running status are highlighted with green.
  1. Navigate to the techila directory and verify that the keystore containing the End-User Key is located in the directory. If you chose to name your keystore differently or stored the file in a different location, you will need to modify instructions.

    image063
    Figure 53. In this example, the End-User Key is stored in a keystore file named demouser.jks. Your keystore might have a different name.
  2. Open the file techila_settings.ini using a text editor. Modify the value of the keystore parameter to contain the path and keystore filename.

    keystore={inidir}\demouser.jks

    The notation {inidir} used here is a macro and points to the directory that contains the file techila_settings.ini, which means it can also be used to specify the location of the keystore file. More information on macros (notations in curly {} brackets) can be found in the beginning of the techila_settings.ini file and in the document Getting Started.

    Note! If you named the keystore differently or stored the keystore file in a different location, you will need to specify the value for the keystore parameter accordingly.

  3. Save changes and close the text editor.

  4. Launch a command prompt/terminal and navigate to the following directory.

    <full path>\techila\examples\CLI\Tutorial\1_distribution
  5. Create the test Project using command:

    java -jar ../../../../lib/techila.jar read < commands
    image064
    Figure 54. The test Project can be created by running one of the Techila Command Line Interface examples. More information on the example material under the CLI folder can be found in the document Techila Distributed Computing Engine with Command Line Interface.
  6. After executing the command, a graphical password dialog will be displayed. Enter the keystore password you specified when adding the End-User in Adding End-Users and click the OK button.

    image065
    Figure 55. The graphical password dialog.
  7. After entering the password, the test Project will be created. Information on the Project will be displayed in the command prompt and should resemble the one shown below.

    image066
    Figure 56. Information on the Project will be displayed in the command prompt. The test Project is computationally very light, which means that the Project will be completed in a very short amount of time.

    Congratulations! You have successfully completed a computational Project in the Techila Distributed Computing Engine environment.

9. Creating Runtime Bundles

Language-specific Runtime Bundles (a subset of Library Bundles) are required to perform computations on Techila Workers with different programming languages. Runtime Bundles will be required if End-Users in your Techila Distributed Computing Engine environment use the following programming languages:

  • MATLAB

  • Perl

  • R

  • Python

Information on how to create Runtime Bundles can be found in the document Bundle Guide.

10. Appendix

10.1. Techila Web Interface Login Credentials

The login credentials for the Techila Web Interface are shown below:

Techila Web Interface

Login

admin

Password

adminpass

Note! It is strongly recommended that you change the default password as soon as possible.

10.2. Master Administrator Keystore Information

Information on the Master Administrator keystore is shown below:

Master Administrator keystore

Location of the Master Administrator keystore

/home/techila-admin/admin/admin.jks

Master Administrator Key alias

admin

Master Administrator Key password

adminpass

Note! It is strongly recommended that you change the default password as soon as possible.

10.3. End-User Keystore Information

Information on the End-User keystore is shown below:

End-User keystore

Location of the End-User keystore

/home/techila-admin/userkeys/subadmin1.jks

End-User Key alias

admin

End-User Key password

adminpass

Note! It is strongly recommended that you change the default password as soon as possible.

10.4. User techila-admin Login Credentials

The login credentials for the user techila-admin user on the Techila Virtual Server are shown below:

Techila Virtual Server

Login

techila-admin

Password

eizolee0

Note! It is strongly recommended that you change the default password as soon as possible.

10.5. Configuring a Static IP Address for the Techila Server

By default, the Techila Server is configured to obtain the IP address from the DHCP server. This Chapter contains instructions on how to configure a static IP address for the Techila Server.

Procedure

  1. Log in to the Techila Server as techila-admin

  2. Open file /etc/network/interfaces with a text editor (as root via sudo) e.g. by using command:

    sudo nano /etc/network/interfaces

  3. If needed, remove the lines containing the dhcp configuration and replace with the following parameters:

    iface eth0 inet static
      address <IP address of the Techila Server>
      netmask <netmask value>
      broadcast <broadcast address>
      network <network address>
      gateway <gateway address>

    Below is an example static IP address configuration for eth0.

    iface eth0 inet static
      address 10.50.1.3
      netmask 255.255.255.0
      broadcast 10.50.1.255
      network 10.50.1.0
      gateway 10.50.1.4

    More information on configuring the network address of a Debian operating system can be found from the following address:

  4. Save changes and exit the editor.

  5. Reboot the Techila Server with command:

    sudo reboot

10.6. Disabling the Automatic Trusting of Techila Worker Keys

The following procedure describes how you can disable the automatic trusting of Techila Worker Keys.

  1. Log in as an administrator to the Techila Web Interface

  2. Click Admin

  3. Click Advanced

  4. Click Config

  5. Scroll down the page and locate the table titled Techila Server Security X509DB

  6. Uncheck the checkbox on following line Workers: Trust Keys Automatically

  7. Click the Submit button

10.7. Modifying the Size of the Data Hard Disk

This Chapter contains instructions on how to modify the size of the data hard disk before powering on the Techila Virtual Server.

Note! The procedures described in this Chapter cannot be applied if you have already started the Techila Virtual Server.

  1. Select the Techila Virtual Server and click the Edit Settings button.

    image067
    Figure 57. Open the virtual machine properties window by clicking the Edit Settings button.
  2. Select "Hard disk 2" and delete it by clicking the Remove button.

    image068
    Figure 58. Select "Hard disk 2" and click the Remove button.
  3. Mark files to be removed from the disk in the Removal Options section. Click the Add…​ button to add a new hard disk.

    image069
    Figure 59. Mark the old hard disk file to be removed and click the Add…​ button to add a new data hard disk.
  4. A new "Add Hardware" window will be displayed that can be used to add the new data hard disk. Select Hard Disk as the device type and click Next.

    image070
    Figure 60. Selecting the Device Type.
  5. Select Create a new virtual disk and click Next.

    image071
    Figure 61. Specifying that a new hard disk should be created.
  6. Specify the size of the new hard disk and other properties. Click Next to continue.

    image072
    Figure 62. Specify the properties of the new data hard disk. In this example, the size has been set to 24 GB and Disk Provisioning has been set to "Thin".
  7. In the Advanced Options view, ensure that the Virtual Device Node is set to SCSI (0:1). Click Next to continue.

    image073
    Figure 63. Ensure that the Virtual Device Node field matches the one illustrated here.
  8. Create the hard disk by clicking the Finish button. The view will change back to the virtual machine properties view and should resemble the one shown below. Click OK to close the virtual machine properties view.

    image074
    Figure 64. After adding the new hard disk, click OK to close the virtual machine properties view.

10.8. Configuring the Techila Server Firewall

The Techila Server firewall configuration is located in the following directory:

  • /etc/firewall/

This directory contains the following firewall configuration files:

  • config_allow_port20001

  • config_allow_port20002

  • config_allow_port25001

  • config_allow_port443

  • config_allow_port80

  • config_allow_snmp

  • config_allow_ssh

Each of these files contains the allowed IP address range definition in CIDR format for the port specified in the file name. Please see below table for a description of the files.

File Default Allowed IP Address Range (CIDR) Description

config_allow_port20001

0/0

Defines IP range from where Signal Channel connections can be established from. Connections are established by Techila Techila Workers

config_allow_port20002

0/0

Defines IP range from where Data Channel connections can be established from. Connections are established by Techila Workers

config_allow_port25001

0/0

Defines IP range from where Management Channel connection can be established from. Connections established by End-Users via Techila SDK.

config_allow_port443

0/0

Defines IP range from where Techila Web Interface can be accessed from. Connections established by End-Users and Administrators via web browser using https protocol.

config_allow_port80

No external connections allowed.

Defines IP range from where http requests can be performed. Port not used in the current Techila Virtual Server.

config_allow_snmp

No external connections allowed.

Defines IP range from where SNMP connections can be established from using UDP port 161. Default only allows connections from localhost.

config_allow_ssh

0/0

Defines IP range from where SSH connections can be established from using TCP port 22. Connections established by Techila Administrators.

After modifying the firewall configuration files described above, the changes will need to be applied by executing the firewall configuration update script. The location of the firewall configuration script is:

  • /etc/firewall/iptables-firewall.sh

Note! When executing the configuration update script, your current working directory must be set to /etc/firewall

The example procedure in this Chapter illustrates how the Techila Server firewall can be configured to only allow SSH connections from a specific IP address range.

The procedure is similar for all port configurations, only the file names will be different. Please replace the filenames to match the firewall configuration you are modifying.

  1. Establish a SSH connection to the Techila Server. When prompted for login credentials, use login credentials described in User techila-admin Login Credentials.

  2. Change your current working directory to directory /etc/firewall.

    cd /etc/firewall
  3. Open the file config_allow_ssh with a text editor using sudo.

    sudo nano config_allow_ssh
  4. When prompted for the techila-admin password, enter the password defined in User techila-admin Login Credentials.

  5. Replace the line 0/0 with the IP address CIDR range of your choosing. In the example below, the IP range has been changed to 10.50.1.0/24.

    image075
    Figure 65. Specifying the IP address range using CIDR format.
  6. Save the changes that you made to the file and exit the text editor.

  7. Update the changes to the firewall by executing the script iptables-ssh.sh using the command shown below:

    sudo ./iptables-ssh.sh
  8. After executing the command, information about the new IP address range should be displayed as shown below.

    image076
    Figure 66. After executing the configuration update script, the new allowed IP address range will be displayed.