Balsam is an interface to a batch system's local scheduler. The each scheduler is abstracted such that Balsam remains scheduler independent.
ARGO is a workflow manager. ARGO can submit jobs to any system on which Balsam is running.
Both ARGO and Balsam are implemented in Python as django apps. This was done because django provides some services by default that are needed such as database handling and web interfaces for monitoring job statuses. django version 1.6 has been used and Python 2.6.6 (with GCC 4.4.7 20120313 (Red Hat 4.4.7-3)).
The communication layer is handled using RabbitMQ and pika. RabbitMQ is a message queue system. Message queues were an easy alternative to writing a custom TCP/IP interface. This requires installing and running a RabbitMQ server. RabbitMQ 3.3.1 is used with Erlang R16B02.
The data transport is handled using GridFTP. This requires installing and running a GridFTP server. Globus version 5.2.0 is used.
{{hpc:argobalsamdiagram.png?600 | Diagram of the ARGO - Balsam interactions. }} ===== Job Submission ===== Jobs are submitted to ARGO via a RabbitMQ message queue. The messages use the python json serialization format. An example submission is:
from site_settings.mira_settings import *
-
INSTALLED_APPS = (
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'south',
'balsam_core',
'argo_core',
)
- If you are using MySQL:
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'your_table_name_goes_here',
'USER': 'your_login',
'PASSWORD': 'your_password',
'HOST': '127.0.0.1',
'PORT': '',
'CONN_MAX_AGE': 2000000,
}
}
- Setup your database:
- For Older Django using South (pre-1.7):
- python manage.py syncdb
- Create the first migration python manage.py schemamigration balsam_core --initial
- Apply the first migration python manage.py migrate balsam_core --fake
- Create the first migration python manage.py schemamigration argo_core --initial
- Apply the first migration python manage.py migrate argo_core --fake
- For newer Django (1.7,1.8):
- python manage.py syncdb
- For Django (1.9+):
- python manage.py migrate --fake-initial
===== Git Tag Notes =====
Git Browser
5.0
* updated to MySQL database
* create filter website
* Added ''group_identifier'' to ArgoDbEntry so that jobs can be grouped together and searched for easier.
4.1
* updated vesta balsam delays to 5 min
* making all settings files consistent.
* added code to deal with jobs after a crash, and added print statements
* added restart try of subprocesses in the service loop
* updated vesta settings
* Updated Balsam code to support tukey submit script with manual mpirun call. Mira handles the mpirun call for the user whereas tukey does not.
* added tukey balsam site to argo settings
* updated argo settings to reflect new install directory balsam_production
4.0
* adding condor command files which should have already been added. Fixed bugs with adding alpgen data to finished emails.
* adding logger.exception in the proper places. Fixed small bugs and added JobHold error
* Adding files for the condor scheduler changes to include dagman jobs and condor job files.
* Many updates to accomodate a Condor Scheduler ability to accept condor job files and condor dagman job files. Also includes updates to include more information on emails upon completion.
* fixing missing str() conversion
* fixed error messages where integers needed to be converted to strings
* updating only specific db fields instead of full object
3.2
* re-added JobStatusReceiver
3.1
* adding QueueMessage class to argo
* merging old and new?
* adding longer wait times to balsam on ascinode settings, and an error checking to the job status receiver.
3.0
* major change to ARGO so that each transition takes place in a subprocess and does not block argo from processing other jobs in parallel
* added error catching for job id mismatch