The version 8.1 is now supported in addition to 8.0.1. Clients can start upgrading to the latest version.
Gurobi Instant Cloud now supports machines in three Microsoft Azure regions: US East, US West 2 and EU West. You can choose between the following machine types:
You can now choose between the following machine types:
The previous generation of c4 and r3 machines have been upgraded to c5 and r4 machines. Instant Cloud pools and preferences have already been changed so that you will benefit from the new machines immediately.
With the v8 engine, all the communications between the clients and the Gurobi Instant Cloud are using the HTTPS protocol. This means that your communications are secured and encrypted using standard internet protocols. In addition, Gurobi servers enforce the latest encryption policies (TLS v1.2 and above only). For better security, the dedicated machines started by Instant Cloud on your behalf cannot be accessed directly, and all communications must transit through a secured and highly-available region router acting as a reverse proxy. This also facilitates the integration with clients as only the standard HTTPS protocol and standard port 443 need to be open if a firewall is in place.
For customers who have used versions v6.x and v7.x, the new v8 engine will simplify their network integration, as there is no need to open ports 61000 to 65000 anymore. Also, please note that the pool fixed IP feature of v6.x and v7.x engines is not available for v8 as we have replaced the protocols by internet standards.
The v8 engine now provides visibility into the jobs running on the machines. The Instant Cloud Manager has a new menu option to list the jobs currently running or queued on all active machines and pools. The list also contains recently ended jobs with a status:
Note that when a machine is terminated, the job executed on this machine will disappear from this list. If you need to keep visibility on all executed jobs, see the Job History feature below.
It is also possible to select jobs and abort them.
From the active job list, the detailed job dashboard can de displayed. The job dashboard provides different views about a given job in order to let an optimization expert monitor the job execution:
While the active job list provides a view of jobs currently queued, running or recently ended, the job history provides a persistent list of ended jobs. The new job history menu option lets you browse and filter these jobs. The engine log can also be downloaded. When using this feature, the job metadata and the engine logs are stored on the Instant Cloud secured servers for a maximum of 90 days. This feature can be disabled on selected pools or machines in the options panel.
It is now possible to scale up or down your pools using the Instant Cloud Manager or the REST API. A pool defines a number of compute servers that is actually the minimum number of servers. So when a client starts a pool, the pool will be ready when this number of servers is ready. Then, you can scale up by requesting additional servers to be added to the pool. When servers are added, they automatically join the cluster of compute servers of the pool and start processing new jobs or jobs already queued in existing servers.
The pool will scale down automatically by using the existing idle shutdown parameter. This means that any server being idle for this time limit will be terminated, up to completely terminate the pool. The pool can also be explicitly scaled down by reducing the number of servers. In this case, if a machine must be stopped but it is already running a job, it will be moved into a draining mode where new jobs will not be processed while running ones will be processed normally. When these jobs have completed, the machine will be automatically terminated.
For better monitoring, the pool view displays the number of machines that are starting, stopping and the ones that are ready.
The machines are now reporting the current CPU and memory usage. These metrics are displayed in the machine view.
A parameter has been added to specify the duration limit after which the job will auto-terminate when there is no command sent to the server. This is useful to avoid using resources when some clients may leave their connections open (for example in an interactive python shell) while not being active. Clients can set this timeout using the CSIDLETIMEOUT parameter or using the IDLETIMEOUT property in the license file. The default value is 30 minutes. The pool or machine option can be used to set a larger timeout globally that will override the client default.
The REST API has several new endpoints to support the monitoring of active jobs, the access to job history and the management of pool scaling. See the REST API reference documentation for more details.
In order to provide better support on heavily used regions, we have decided to focus our resources on 5 regions:
As a consequence, we are discontinuing the support of 3 regions and if you had pools using these regions, they will be automatically moved to the nearest one as follows:
As we are now supporting the new v8 engine, we have removed the support of v6.0 and v6.5 in Instant Cloud. Our policy is to support the last two major versions, namely v8 and v7.x. If you had pools and preferences using these versions, they will be automatically upgraded to v7.0.
The new v7.5 engine can now be selected in the dropdown menu of the engine versions of your pools and machines. Note that the version of the client and the machines or pools must match. If you had existing pools, they will still use the current version. When you are ready to use the v7.5, you will need to manually update the version of your pools to match the client so that you can upgrade at your own pace.