Hi, Is there a way to use a password file for the Elasticsearch jobcomp plugin? Currently, our slurm.conf is readable by all users. If I put JobCompPass and JobCompUser in slurm.conf, anyone who looks will have our Elasticsearch credentials. Other workarounds would be fine, too. Thanks! -Aaron
Hi, JobComp[User|Pass] options don't currently apply to this plugin. As documented in guide[1], the only available options that apply are JobCompType, JobCompLoc and DebugFlags. Since long ago I have a list of nice things to enhance the functionality offered by the plugin. Unfortunately, absent someone willing to sponsor such changes, or a contributed patch providing expansions, SchedMD cannot say when/if this will ever be addressed. Some of the ideas that I have in mind include: 1. Let the user decide the index name and index type instead of forcing the current fixed names /slurm/jobcomp. 2. Use the json-c library instead of manually generating a JSON formatted string for each finished job. 3. Add support for https://www.elastic.co/products/x-pack X-Pack credentials and potentially take advantage of the already available JobComp[User|Pass]. 4. Parse the REST response by using the https://curl.haxx.se/libcurl/c/curl_easy_getinfo.html libcurl method. This will be a safer way to parse the different response parts (CURLINFO_RESPONSE_CODE, ...) than manually using strtok. 5. Move the libcurl C API setup to a common function under src/common. Potential new code using libcurl could take advantage of that (i.e. InfluxDB). 6. Add a new JobCompParams slurm.conf option to specify different params such as ESExpandHostlist (which indicates whether to store the node list in a contracted or expanded format) or ESIndex=[none|day|week|month|year] to append a different date to the index name at different frequencies. [1] https://slurm.schedmd.com/elasticsearch.html
