1.10. Adding Resources to Your MedeA Installation
Contents
download: | pdf |
---|
1.10.1. Introduction
Previous sections guide you to create a working system on your computer: the MedeA graphical user interface (GUI), the JobServer, and the TaskServer are all installed and working together. This is perfect for learning to use the interface and run your first calculations.
Adding resources to your MedeA installations can be accomplished in many different ways, and there are plenty of solutions. The following sections cover most cases:
- Adding another GUI
- Linking another JobServer
- Adding more TaskServers
The clear separation into three tiers allows for adding or changing components without impact to ongoing calculations.
Note
Before reading further, ensure you have read the following sections on installing and configuring MedeA, the JobServer, and the TaskServer:
1.10.2. Adding Another GUI

To add a second GUI on a laptop/desktop to access an existing JobServer, perform a custom installation without installing the JobServer and TaskServer.
GUI | JobServer | TaskServer |
Install: MedeA GUI and databases | ||
Save new license: C:\MD\ (Windows) or ~/MD/ (Linux) | ||
Connect to JobServer: Edit MedeA Preferences | Name IP-address |
There is no need to install JobServer and TaskServer unless you would like to run calculations directly on the new computer. You will need to get a license for the new machine.
If you have changed MedeA preferences, you can copy the MedeA environment settings file,
MedeA.settings
from your home directory, abbreviated as ~, to the home directory on the new machine.
On Windows 10, this is normally C:\Users\<Username>.
On Linux, the command cd or cd ~ take you into your home directory.
1.10.3. Installing Another JobServer

Adding another JobServer involves all three tiers as the JobServer is the central piece of the MedeA installation. The JobServer talks to the graphical GUI and the TaskServers. The installation process is split into two parts, first to add and test another JobServer without interrupting the running JobServer. The next section will deal with replacing an existing JobServer.
Warning
Do not connect two or more JobServers to the same TaskServer. This should be a temporary solution for testing purposes as this can result in files being overwritten and corrupted.
GUI | JobServer | TaskServer |
Install: JobServer | ||
Add new JobServer to Preferences | Name IP-Address | |
Create Queues | ||
Attach TaskServer | Name IP-Address |
During the custom installation select only JobServer and perform configuration as a service. Create queues and attach TaskServers as described in section JobServer Administration and Configuration. On the MedeA GUI, add the new JobServer via File >> Preferences >> Job Servers.

1.10.4. Replacing the JobServer
When planning to replace an existing JobServer, the previous procedure creates a new JobServer, but it leaves the need to transfer the existing results to the new JobServer to have all computed results in one central place.
GUI | JobServer | TaskServer |
Install: JobServer | ||
Add new JobServer to Preferences | Name IP-Address | |
Create Queues | ||
Attach TaskServers | Name IP-Address | |
Import jobs: Maintenance | ||
Delete old JobServer in Preferences | Name IP-Address |
During the custom installation on the new machine, only install JobServer as a service. Duplicate your existing JobServer by creating the same Queues and attach the existing TaskServers. You can rename and change settings based on the experience gained in the meantime. You can use the MDmaintenance program to import the Jobs to the new JobServer, provided the Job directory is accessible to both machines, for example, by sharing the directory on the local network. After testing and transferring you can remove the entry of the old JobServer from File >> Preferences >> Job Servers The Job directory still contains all the calculated results - delete only after verifying that the import worked exactly as planned.
1.10.5. Adding More TaskServers

GUI | JobServer | TaskServer |
Install TaskServer | ||
Add TaskServer | Name IP-address | |
Attach to JobServer queue | ||
Adapt job scheduler integration script template<scheduler>.tcl |
First, install only the TaskServer component on the new compute node and record its IP address. Then from the JobServer, open the MDMaintenance program. From click Manage MD Services, then add a Queue name and User and click Add TaskServer and Queue. If feeding into an external job scheduler, adapt the respective scheduler integration script. Finally, add the TaskServer to the list of TaskServers known to the JobServer and attach to selected Queues.
download: | pdf |
---|