Base Command Manager / Bright Cluster Manager Release Notes

Release notes for Bright 8.2-21

== General ==

- New Features

* Support for kubernetes v1.16
* Support for SLES12sp5

- Fixed Issues

* cm-openssl: added functionality to support RHEL 8.2

== cmdaemon ==

- New Features

* Compress large fields in the DB

- Fixed Issues

* Add cmsh filemode display format and use the filemask for the file in generic role configurations
* Reinitialize gpu sampler after DCGM is connected
* Always use the primary head node as the first one in the LSF_MASTER_LIST

== cm-kubernetes-setup ==

- Improvements

* Added additional ingress to expose kubernetes dashboard via path based ingress on new installations

== ml ==

- New Features

* Extended support for CUDA 10.2 with cm-xgboost-py37-cuda10.2-gcc package
* Extended support for CUDA 10.2 with cm-theano-py37-cuda10.2-gcc package
* Extended support for CUDA 10.2 with cm-tensorflow-py37-cuda10.2-gcc package
* Extended support for CUDA 10.2 with cm-open3d-py37-cuda10.2-gcc package
* Extended support for CUDA 10.2 with cm-mxnet-py37-cuda10.2-gcc package
* Extended support for CUDA 10.2 with cm-horovod-*-py37-cuda10.2-gcc packages
* Extended support for CUDA 10.2 with cm-gpytorch-py37-cuda10.2-gcc package
* Extended support for CUDA 10.2 with cm-fastai-py37-cuda10.2-gcc package
* Extended support for CUDA 10.2 with cm-dynet-py37-cuda10.2-gcc package
* Extended support for CUDA 10.2 with cm-chainer-py37-cuda10.2-gcc package
* Updated cm-xgboost-* packages to v1.1.1
* Updated cm-tensorflow-* packages to v2.2.0

- Improvements

* Deprecated -py36- variants of Machine Learning packages. Customers are encouraged to switch to -py37- packages to benefit more frequent updates. Uninstallation of old -py36- packages is not strictly necessary, since they can coexist with -py37- packages.
* Introduced cm-open3d-* packages (v0.10.0)
* Introduced cm-horovod-tensorflow2-* packages (v0.19.4)

== pythoncm ==

- Fixed Issues

* Make sure HA is decided before updating the active head node host, which otherwise can interfere in some cases with cmha-setup