Base Command Manager / Bright Cluster Manager Release Notes
Release notes for Bright 8.1-4
== General ==
- New Features
* Adv. config. option BasicSysInfoCollector, when set to 1 will reduce the amount of collected sysinfo data, improving performance on large clusters
* Support for batched power operations
* New jobs power metrics for accounting & reporting
- Improvements
* Reduce default IPMI power timeout from 30m to 5m
* Speed up generation of new admin / portal / ... certificate during request-license
* Allow just booted nodes to retrieve entity configuration from their provisioning node. GlobalConfig = { "InitialEntityFromProvisioningNode=1" }
* Improved performance of cmdaemon http server
* Support for custom sorting of jobs and parent jobs in the user portal, specified using adv. config. flags
- Fixed Issues
* ldap ca.pem not written on passive head node
* Added support for HP iLO on Ubuntu nodes
* An issue with the permissions for /usr/local/share/swig
== cmdaemon ==
- New Features
* Added an option for external default values for global config
- Improvements
* Prevent Etcd from starting without having member certificates
* Improved SSL error reporting
- Fixed Issues
* Possible cmdaemon crash when changing the image for many nodes several times in rapid succession
* CMD_SCRIPTTIMEOUT env. variable not set for the power scripts
* Frozen Slurm configuration still updated by cmdaemon
* Creating a lot of open and idle https connections could cause cmdaemon to stop accepting new connections
* New adv. config. options to control (un)drain during burn
* Queues taking a long time to appear in monitoring tree
* In some cases, drain action executed after the job prolog was completed (thus jobs could still run)
* cmdaemon crash when using numeric usernames in Kubernetes certificates
* In some cases, failed certificate creation could lead to cmdaemon crash
* An issue with pam_bright module not working on Ubuntu
== node-installer ==
- New Features
* Added ability to prevent the node installer from writing ifcfg files (by setting the interface->revision field to "no-ifcfg")
- Fixed Issues
* An issue with using network interface priorities when configuring static routes
* Added support to node-installer scripts to be able to boot a node over Omni-Path
== Bright View ==
- New Features
* Ability to send cluster statistics, to help improve Bright Cluster Manager
* Added About page
- Fixed Issues
* An issue with sending feedback
* Device state tooltips
== cmsh ==
- New Features
* New cmsh "device status" option --overview, to create an overview of the devices
- Fixed Issues
* An issue with --raw option to latestmetricdata
* cmsh device list --rack crash if racks are not configured
* An issue with selecting the user for the cmsh ssh command when using custom profiles
== cod ==
- Improvements
* cod-aws: changed the default VMtypes from m3.medium to t2.medium. The former is no longer being reported by AWS apis as available.
== monitoring ==
- New Features
* Monitoring sampler for lnstat
* Added API call to return all known monitoring resources / types
* Added an option to monitoring tool to export all data to CSV
* Added small tool to calculate monitoring storage size: cm-bright-monitoring-usage.py
- Improvements
* Job metric initialization optimizations
* Improved autocompletion for dumpmonitoringdata command in jobs mode of cmsh
- Fixed Issues
* An issue with monitoringdrop --filtered removing too much for the base partition
* An issue with the perpetual JSON sampler support for multiline data
* Perpetual data producer AUTO format not detecting JSON format
* Improved check if a mount point is docker related, to prevent it from being monitored
* In some cases, job information does not correctly handle the time zones
* getMonitoringMeasurablesForEntity for invalid entity returns error 400, instead of []
* An issue with Prometheus queries on measurables with parameters
* Switch uptime mertric not marked as cumulative
* In some cases, crash in sample now
* An issue with sample now of cumulative metrics returning the raw data instead of the derivative
== wlm-setup ==
- Improvements
* wlm-setup now asks for a confirmation when setting up an already configured workload manager