Closed knikolla closed 2 months ago
@joachimweyl @Milstein @larsks @naved001 would appreciate your feedback on this.
I am generally in favor of the idea of machine-readable policy (and change control for policy decisions), so I am all for this idea!
I don't know enough about our billing model to comment on the specific example representation you've shown here. I would probably start with a higher level description of the information we want to represent and a description of how it would be consumed, and then use that to inform the design of an appropriate representation.
I also like the idea. Let me know when you need the rates and I can provide them.
Added a temporary estimate of 5, please feel free to change it if it is an inaccurate estimate.
@knikolla why should we have the start and end dates for rates in the manifest itself? Wouldn't the fact that it's checked into git help us track when the rates are changed?
I'd imagine that we create monthly releases from the rate repo and use that for producing a report, so if we wanted to regenerate an old report we can use the appropriate release from the rate repo. Thoughts?
@naved001 Using the day of merge to git makes it hard to plan rate changes in the future as the change can't be merged until the day it becomes effective.
Repo avalable at https://github.com/cci-moc/nerc-rates
Motivation
I propose the creation of a repository
nerc-project/rates
to store the above missing information.A possible representation of that information may be (using YAML):