Server-client glidein submission


Users submitting jobs to their local Institutional Pool can expand their resources by overflowing their jobs to the Global Pool via CMS Connect. This mean user jobs will start running on the local pool and idle jobs still waiting to run will communicate with CMS Connect so that they can be matched with available CMS resources in the Global Pool. In order to do this, the user needs to:

  • Before starting, make sure your system administrator has properly configured condor to allow authentication between the local Institutional Pool and Global Pool resources (see the admin guide).
  • Run a server on the Institutional submit host to communicate with CMS Connect.
    • You will need an open port for this (default port is: 11001, but you can choose any available). Ask your administrator if you don't know any of this.
  • Login to and run the client. This will read the jobs from the server.

Also, the Institutional pool needs to be properly configured (see the ) so that authentication works properly.

The server-client tool

We will use pyglideins in order to run both the server and the client. This is a pyhon-based open source glidein implementation developed by Icecube [1].

The server side

On your Institutional submit host, download the pyglidein repository:

$ wget
$ unzip

Then, you need to run the client on a specific port, constraint also the server to only send information about your own jobs.

$ cd pyglidein-master
[pyglidein-master]$ ./ -p 50000 -u <your_username>

To verify the chosen port is open, you can login into CMS Connect and run nmap to that specific port. The State alternatives are:

  • Open:  This means the server port is opened and listening. 
  • Closed: The server is not running
  • Filtered: The server port is behind a firewall

[]$ nmap -Pn -p 50000
Starting Nmap 5.51 ( ) at 2016-09-15 09:47 CDT
Nmap scan report for (
Host is up (0.012s latency).
50000/tcp open  ibm-db2
Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds

The client side

Follow the same steps to download the pyglidein tool on and run it as followed:

[pyglidein-master]$ ./ --conf=you_config

There are different configuration examples in the github repository. Use this example as a guide and contact the support team for further help.




Please, using the following e-mail for any questions: