Bug fix for updater parsing

[nick-enoent]

Addresses bug when "updaters" is omitted from "peers" dictionary in top level "aggregators" dictionary.
Fixes bug that occurs when "producers" regular expression is not defined in the "updaters" dictionary.
Updaters now correctly only add the parent dictionary's producers when "produers" is not defined in the updaters dictionary.
Updated producer balancing when multiple aggregators share producers in the YAML configuration.
Updated ldmsd_yaml_parser man page

[emdonat]

Is the intention for an updaters stanza of:

aggregators:
- daemons: "admin[1-1]-agg"
  peers:
  - daemons: "compute[1-30]"
    endpoints: "compute[1-30]-ib0"
    reconnect: 20s
    type: active
    updaters:
      - mode: pull
        interval: "1.0s"
        offset: "10ms"
        sets:
          - regex: ".*"
            field: inst

to result in configuration lines like:

updtr_prdcr_add name=updtr_0 regex=compute1-ib0
updtr_prdcr_add name=updtr_0 regex=compute2-ib0
updtr_prdcr_add name=updtr_0 regex=compute3-ib0
...
updtr_prdcr_add name=updtr_0 regex=compute29-ib0
updtr_prdcr_add name=updtr_0 regex=compute30-ib0   

Just want to confirm that this is expected. I am adding no producers: entry under aggregators: peers: updaters:.

[nick-enoent]

Is the intention for an updaters stanza of:

aggregators:
- daemons: "admin[1-1]-agg"
  peers:
  - daemons: "compute[1-30]"
    endpoints: "compute[1-30]-ib0"
    reconnect: 20s
    type: active
    updaters:
      - mode: pull
        interval: "1.0s"
        offset: "10ms"
        sets:
          - regex: ".*"
            field: inst

to result in configuration lines like:

updtr_prdcr_add name=updtr_0 regex=compute1-ib0
updtr_prdcr_add name=updtr_0 regex=compute2-ib0
updtr_prdcr_add name=updtr_0 regex=compute3-ib0
...
updtr_prdcr_add name=updtr_0 regex=compute29-ib0
updtr_prdcr_add name=updtr_0 regex=compute30-ib0   

Just want to confirm that this is expected. I am adding no producers: entry under aggregators: peers: updaters:.

Hey @emdonat, this is the intended behavior. Otherwise we'd have to reverse engineer a regular expression from the list of producer names.

[emdonat]

Is the intention for an updaters stanza of:

aggregators:
- daemons: "admin[1-1]-agg"
  peers:
  - daemons: "compute[1-30]"
    endpoints: "compute[1-30]-ib0"
    reconnect: 20s
    type: active
    updaters:
      - mode: pull
        interval: "1.0s"
        offset: "10ms"
        sets:
          - regex: ".*"
            field: inst

to result in configuration lines like:

updtr_prdcr_add name=updtr_0 regex=compute1-ib0
updtr_prdcr_add name=updtr_0 regex=compute2-ib0
updtr_prdcr_add name=updtr_0 regex=compute3-ib0
...
updtr_prdcr_add name=updtr_0 regex=compute29-ib0
updtr_prdcr_add name=updtr_0 regex=compute30-ib0   

Just want to confirm that this is expected. I am adding no producers: entry under aggregators: peers: updaters:.

Hey @emdonat, this is the intended behavior. Otherwise we'd have to reverse engineer a regular expression from the list of producer names.

Just to confirm - each updtr_prdcr_add on the same name=updtr_0 appends rather than overwrites the prior? I just want to make sure that the end result isn't that the only regex is the final one processed e.g. compute30-ib0.

[tom95858]

@emdonat, match_add appends to a list of match expressions. They. are all evaluated to determine if there is a match. You can view this list in the ldmsd_controller using the updtr_match_list command.

[nick-enoent]

Just to confirm - each updtr_prdcr_add on the same name=updtr_0 appends rather than overwrites the prior? I just want to make sure that the end result isn't that the only regex is the final one processed e.g. compute30-ib0.

Yes, that's correct. Subsequent updtr_prdcr_add calls do not overwrite previous calls

[emdonat]

@emdonat, match_add appends to a list of match expressions. They. are all evaluated to determine if there is a match. You can view this list in the ldmsd_controller using the updtr_match_list command.

This is prdcr_add in this case.

[emdonat]

Thanks. I think that this actually helps with some functionality that was hoped for when demoing this yesterday. Forging our own limiting regex was going to be a frustrating ordeal and error prone.

[nick-enoent]

Added a missing newline when using a string for configuration commands in the top level daemons dictionary