Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define a Usage Unit Dimension #181

Closed
3 tasks
amitw-g opened this issue Sep 25, 2023 · 0 comments
Closed
3 tasks

Define a Usage Unit Dimension #181

amitw-g opened this issue Sep 25, 2023 · 0 comments
Assignees

Comments

@amitw-g
Copy link
Contributor

amitw-g commented Sep 25, 2023

Type

Type of issue (e.g. Dimension, Metric, Attribute, Documentation etc.)
Dimension
Normalized? Yes

Description

Define the Usage Unit dimension, this unit will apply to Usage Quantity dimension. Note the name of the columns is not finalized

Definition of done

  • Rationalize vendor-neutral, cross-cloud naming
  • Complete spec template and include naming (code name, display name), constraints, guidelines, compatibility with major providers etc.
    ** If Normalized Dimension **
  • Include principles and governance criteria for maintaining this dimension

** If Normalized Dimension **
Work for generating the normalized list of supported values is tracked in a separate issue. Mappings between normalized values and vendor specified values need to be explored as a part of this work. However, these mappings are not included in the spec documentation. Separate tasks will be created for making these mappings available to practitioners outside of the FOCUS repository.

@SumairaaNazir SumairaaNazir self-assigned this Sep 26, 2023
amitw-g added a commit that referenced this issue Sep 28, 2023
Spec change for Usage Unit: A unit of measurement for consumption or usage of resources or services
amitw-g pushed a commit that referenced this issue Oct 4, 2023
…recommended unit set (#188)

This commit adds more specific language to the recommended unit set and
guidance on capitalization. The commit also gets a bit more precise on
*exactly* what we mean by "you MUST if possible" for units in the
recommended set.
udam-f2 pushed a commit that referenced this issue Nov 13, 2023
Spec change for Usage Unit: A unit of measurement for consumption or usage of resources or services
udam-f2 pushed a commit that referenced this issue Nov 13, 2023
…recommended unit set (#188)

This commit adds more specific language to the recommended unit set and
guidance on capitalization. The commit also gets a bit more precise on
*exactly* what we mean by "you MUST if possible" for units in the
recommended set.
udam-f2 added a commit that referenced this issue Nov 13, 2023
Spec change for Usage Unit: A unit of measurement for consumption or
usage of resources or services

---------

Co-authored-by: Tim O'Brien <[email protected]>
Co-authored-by: Udam Dewaraja <[email protected]>
Co-authored-by: Michael Flanakin <[email protected]>
Co-authored-by: Joshua Kwan <[email protected]>
Co-authored-by: Shawn Alpay <[email protected]>
Co-authored-by: Irena Jurica <[email protected]>
@udam-f2 udam-f2 closed this as completed Jan 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants