compute: allow "instance" label name to be set (behind a flag) #266
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #262.
What
Allow
instance
label name to be set via new-compute.instance-label
flag.Why
See #262 for the rationale and discussion.
How
for each compute
Collector
, create newcollectorMetrics
typecontaining compute metrics (moved from global var), to let each
Collector
own an allocated instance obtained vianewCollectorMetrics(instanceLabel)
changing metrics from global var to dynamically allocated object is
needed for:
instanceLabel
spot={true,false}
labelthere's a new
config.CommonConfig
type, currently only having asingle field
ComputeInstanceLabel
, which is passed down fromcmd/
to each instantiated Provider, then to each compute Collector
Testing
Adapted testing with a couple
ComputeInstanceLabel="node"
changes,although it should be improved to test changes to the label name.
--
Signed-off-by: JuanJo Ciarlante [email protected]