2023-08-14 13:35:32 +02:00
|
|
|
# `cc-backend` version 1.2.0
|
2023-06-15 09:55:24 +02:00
|
|
|
|
2023-07-03 11:49:05 +02:00
|
|
|
Supports job archive version 1 and database version 6.
|
2023-06-15 09:55:24 +02:00
|
|
|
|
2023-07-20 08:33:42 +02:00
|
|
|
This is a minor release of `cc-backend`, the API backend and frontend
|
2023-06-15 09:55:24 +02:00
|
|
|
implementation of ClusterCockpit.
|
|
|
|
|
2023-08-14 13:35:32 +02:00
|
|
|
** Breaking changes **
|
|
|
|
|
|
|
|
The LDAP configuration option user_filter was changed and now should not include
|
|
|
|
the wildcard. Example:
|
|
|
|
* Old: `"user_filter": "(&(objectclass=posixAccount)(uid=*))"`
|
|
|
|
* New: `"user_filter": "&(objectclass=posixAccount)"`
|
2023-06-15 09:55:24 +02:00
|
|
|
|
|
|
|
The aggregate job statistic core hours is now computed using the job table
|
2023-06-16 14:31:09 +02:00
|
|
|
column `num_hwthreads`. In a future release this column will be renamed to
|
2023-06-15 09:55:24 +02:00
|
|
|
`num_cores`. For correct display of core hours `num_hwthreads` must be correctly
|
|
|
|
filled on job start. If your existing jobs do not provide the correct value in
|
|
|
|
this column then you can set this with one SQL INSERT statement. This only applies
|
|
|
|
if you have exclusive jobs, only. Please be aware that we treat this column as
|
|
|
|
it is the number of cores. In case you have SMT enabled and `num_hwthreads`
|
|
|
|
is not the number of cores the core hours will be too high by a factor!
|
|
|
|
|
2023-06-27 09:41:06 +02:00
|
|
|
** NOTE **
|
|
|
|
If you are using the sqlite3 backend the `PRAGMA` option `foreign_keys` must be
|
|
|
|
explicitly set to ON. If using the sqlite3 console it is per default set to
|
|
|
|
OFF! On every console session you must set:
|
|
|
|
```
|
|
|
|
sqlite> PRAGMA foreign_keys = ON;
|
|
|
|
|
|
|
|
```
|
|
|
|
Otherwise if you delete jobs the jobtag relation table will not be updated accordingly!
|