[abacus] Accommodating for plans in a resource config


Benjamin Cheng
 

Abacus will want to support plans in its resource config (as mentioned in issue #153 https://github.com/cloudfoundry-incubator/cf-abacus/issues/153)

Starting with a basic approach, there would be a plans property(an array) added to the top-level of a resource config. The current metrics and measures properties would be moved under that plans property. This will allow them to be scoped to a plan. Despite moving metrics and measures under plans, there will be a need of a common sets of measures/metrics for plans to fall back on. This comes into play in the report for example when summary/charge functions are running on aggregated usage across all plans.

In terms of the common section, there's of a choice of leaving measures/metrics on the top level as the common/default or putting those under a different property name.

I think there's a couple of things to consider here:
-Defaulting for a plan to the common section if there is no formula defined. This may require the plan to point to the common section or logic that would automatically default to the common section (and subsequently the absolute resource config defaults that are already in place).
-If there's no plan id passed(for example some of the charge/summary calls), they would need to go this common section.

Thoughts/Concerns/Suggestions?

Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.