Skip to content

Releases: praiskup/resalloc

Release v3.4

19 Feb 07:20
Compare
Choose a tag to compare
  • New features:

    • The 'resalloc-maint' command got a new sub-command 'foreach-resource'
      that can be used for programatic way of executing commands for each
      running resource.
  • Bugfixes:

    • We fixed a bug in calculation of "preallocated" resources; previously
      released resources were counted as free-to-use by anyone - thus also
      pre-allocated. But these are not useable by anyone, and shouldn't be
      taken as preallocated.

    • We re-added the "host" config option, which is just for backward
      compatibility. Users still should use 'hostname' preferably.

Release v3.3

25 Jun 11:51
Compare
Choose a tag to compare
  • Bugfixes:

    • Large stdout output from cmd_new command is properly trimmed, without
      traceback and leftover always-STARTING instance.

    • Better (fixed) logging from AllocWorker.

Release v3.2

02 Jun 05:02
Compare
Choose a tag to compare

New in 3.2:

  • Enhancements:

    • Configurable command cmd_release to be run before we mark the
      resource as reusable again.

    • After server restart, schedule all inconsistent resources to be
      terminated. (mitigates issue#41)

    • Systemd serrver service is restarted upon failure (just in case).

Release v3.1

02 Jun 05:01
Compare
Choose a tag to compare

New in 3.1:

  • Enhancements:

    • Resource Watcher thread doesn't directly terminate resources, but only
      checks periodically for liveness. The termination task is given to
      Manager thread to avoid races.

    • The Watcher thread has a new environment variable
      RESALLOC_RESOURCE_DATA with base64 encoded output from 'cmd_new'.

Release v3.0

17 May 10:07
Compare
Choose a tag to compare
  • New features:

    • Resource "re-using" mechanism was added. Resources are newly put to
      sandboxes (per ticket sandbox flag), and when the resource is released
      from ticket the resource can be assigned to other (subsequent) ticket
      with the same sandbox flag.

    • Python API; The resalloc.client.Connection constructor now accepts
      'request_survives_server_restart'. When set to True (default False),
      each XML request network failure is ignored and the request is retried
      till it succeeds. This allows administrator to do resalloc server
      maintenance, restart it and clients survive without noticing.

Release 2.6

02 Aug 06:48
Compare
Choose a tag to compare

Don't assign resources to closed tickets.

v2.5

13 Jun 04:50
Compare
Choose a tag to compare
  • don't mangle os.environ in threads

Fix inter-thread problems with resource termination

11 Jun 09:37
Compare
Choose a tag to compare
  • using thread local data where appropriate
  • simplified/enhanced testsuite
  • shorted critical sections while working with sql transactions

provide resalloc-server.1 man page

10 May 10:51
Compare
Choose a tag to compare
logrotate also hooks/ directory

This requires custom scripting to merge the small files into one
log file, which is actually rotated.

Fix release tarball to contain argparse-manpage

09 May 09:04
Compare
Choose a tag to compare
Bump version to v2.2

Basically because I created a bad release before.