SKU Properties & Providers alignment

[jpradocueva]

Description

This issue was created to assign the following action item: TF2-#xxx: Michael, Zack, Rupa: Lead the discussion on SKU properties and ensure alignment across providers.

Proposed approach

Describe the approach that your group is proposing

Github issue or Reference

If the topic is related to a particular work item, reference the Github issue. If its a specification-wide topic, indicate that.

Context

Add any context that may help the community think through this and provide useful feedback

[AWS-ZachErdman]

https://docs.google.com/document/d/1zPEUZ5L5wf9YAJ63ymW3tyrOFx-krJBB6sf1bHU_oOs/edit

Need input from other providers to get their first class columns that differentiate between different SKUs and different SKU Price IDs

[jpradocueva]

Action Items agreed on TF-2, July 17 call:

• [x] TF2-#495 Zach: To draft a more detailed request for use cases involving SKU details and raise the question during the Members meeting.
• SKU Details from Providers
• [ ] TF2-#495 Rob: To engage a practitioner group for input on use cases and queries involving SKU details.

Action Items from Maintainers call on Jul 22:

• [x] Maintainers-#495: Zach to gather example data and collaborate with Karl and Shawn. Present findings and proposed attributes in the next TF2 meeting.
• Folder folder #495 SKU Properties & Providers Alignment

Action Items, TF-2 call on July 24.

• [ ] Map Provider-Specific Columns to Standardized SKU Details: Team members need to map the SKU details and price details specific to each cloud service provider (e.g., AWS, Azure, GCP) to the standardized format. This involves identifying and aligning common attributes such as usage type, operation, and instance type across providers.
• [ ] Define Common Attributes: The team needs to define and refine the attributes like usage type, operation, and instance type, ensuring clarity and consistency across providers. This includes developing clear definitions and criteria for these attributes.
• [ ] Draft SQL Queries: Team members, potentially led by Shawn or other technical leads, should draft SQL queries to demonstrate how the newly defined and standardized columns can be used in practice. This will help validate the usefulness of the proposed standardization and support further discussions on the inclusion of these attributes as first-class columns.
• [ ] Gather and Analyze Data Samples: The team should gather sample data from different providers and analyze it to see how the standardized attributes fit and whether any additional adjustments are needed. This includes working with CSP representatives to understand the specific data structures and attributes provided by each cloud provider.

Action Items from TF-2 call on July 31st.

• [ ] TF2-#495 Zach to update the supporting document with a breakdown of the proposed columns and their definitions, reflecting the discussion's outcome.
• [ ] TF2-#495 Team members to review the supporting document and provide feedback on the proposed columns and definitions.

Action Items from Maintainers meeting on Aug 5th call:

• [ ] [TF1-#495 ] Zach will schedule a meeting with key members, including Michael and Tim, to finalize the proposal and review shared attributes analysis. He will announce the meeting in the Slack channel.
• [ ] [TF1-#495 ] Zach will develop a proposal for explicit columns based on shared SKU attributes and present it in the upcoming Task Force 2 meeting.
• [ ] [TF1-#495 ] Zach will update relevant documents with the rationale behind the proposed columns and the identified shared attributes.

Action Items from TF-2 meeting on Aug 14th:

• [ ] [TF2-#495-#516 ] Tim and Karl to provide samples from GCP to illustrate how the new column will be used. This is part of the alignment of the SKU properties across providers.
• [ ] [TF2-#495-#516 ] The group to finalize the PR for the new column by next week to ensure timely approval.
• [ ] [TF2-#495-#516 ] Zach to draft a short narrative explaining the use case and goals of the new column, align it with the current PR, avoid specific provider terminology.
• [ ] [TF2-#495-#516 ] Zach to incorporate into PR #516 the following concepts discussed and agreed by the group:
  1. Flexible Definition for the New Column:
     • The team agreed to adopt a flexible approach to defining the new usage type column. The definition would accommodate differences in how each cloud provider (AWS, Azure, GCP) defines and measures SKUs. The focus will be on describing the function of the SKU without being overly prescriptive.
  2. Incorporation of Provider-Specific Values:
     • It was acknowledged that the new column would likely contain provider-specific values, and the group agreed to embrace the inherent differences across providers. The goal is to allow these slightly disparate concepts to coexist within a single column, recognizing that this will not be a perfectly normalized field across all providers.
  3. Exclusion of Size and Tier for Now:
     • The group discussed the possibility of future columns such as size and tier, which could be introduced in later releases. For now, the decision was made not to include these elements in the new column being defined in PR #516.
  4. Narrative and Supporting Content:
     • Zach was tasked with drafting a narrative that would clearly define the use case and goals for the new column. This narrative should avoid specific provider terminology and instead focus on a more abstract description that applies across all cloud providers.
  5. Timeline and PR Update:
     • The team agreed that the updates and narrative provided by Zach would be incorporated into PR #516. The aim is to finalize the PR by the following week, ensuring that it reflects the group’s consensus and is ready for Task Force (TF) approval.
     • The PR would then be presented to the broader group for final approval, with the understanding that there is limited time remaining before the release deadline.

[AWS-ZachErdman]

https://github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/pull/516