Once you are logged in, you can use gurobi_cl to submit a job:
> gurobi_cl ResultFile=solution.sol stein9.mps Using license file /opt/gurobi950/manager.lic Set parameter CSManager to value "http://server1:61080" Set parameter LogFile to value "gurobi.log" Compute Server job ID: 1e9c304c-a5f2-4573-affa-ab924d992f7e Capacity available on 'server1:61000' - connecting... Established HTTP unencrypted connectionGurobi Optimizer version 9.5.2 build v9.5.2rc0 (linux64)
Copyright (c) 2022, Gurobi Optimization, LLC
Gurobi Compute Server Worker version 9.5.2 build v9).5.2rc0 (linux64)
Thread count: 4 physical cores, 8 logical processors, using up to 8 threads ... Optimal solution found (tolerance 1.00e-04) Best objective 5.000000000000e+00, best bound 5.000000000000e+00, gap 0.0000% Compute Server communication statistics: Sent: 0.002 MBytes in 9 msgs and 0.01s (0.26 MB/s) Received: 0.007 MBytes in 26 msgs and 0.09s (0.08 MB/s)
The initial log output indicates that a Compute Server job was created, that the Compute Server cluster had capacity available to run that job, and that an unencrypted HTTP connection was established with a server in that cluster. The log concludes with statistics about the communication performed between the client machine and the Compute Server. Note that the result file solution.sol is also retrieved.
This is an interactive optimization task because the connection with the job must be kept alive and the progress messages are displayed in real time. Also, stopping or killing the command terminates the job.