Capacity Reservation Proposal for ID & Status

[gparker-at-sf]

Proposal based on Action Items, TF-3, Aug 16:

[TF3-#397] George will draft a PR for the new “ID” and “Status” columns related to ODCRs.
[TF3-#397] to consult AWS for further guidance on the feasibility of providing a CR ID in the billing data.

[jpradocueva]

Action Items, Maintainers, Aug 19:

• [Maintainers-#509-#523] Chris and Zach will refine the PR to reflect the decisions made and prepare for final approval.

[jpradocueva]

Action Items from Member's call on Aug 22:

• [Members- #523 ] George, @gparker-at-sf : Continue with the discussion of naming conventions and finalize PR Capacity Reservation Proposal for ID & Status #523 in the TF3 meeting.

[jpradocueva]

Action Items from TF-3 call on Aug 23rd:

• [TF-3-#523 ] Zach, @AWS-ZachErdman : To update the PR based on the feedback, ensuring the language reflects the decisions made about when the ID and status must or should be provided.
• [TF-3-#523 ] Chris - (@cnharris10), Alex - (@ahullah), Zach - (@AWS-ZachErdman), and Irena - (@ijurica): To review the updated PR and provide final comments or approvals.

[jpradocueva]

Action Items from Maintainers' call on Aug 26:

• [Maintainers-#523] Zach - @AWS-ZachErdman : To complete reorganizing normative statements in PR Capacity Reservation Proposal for ID & Status #523.

[ijurica]

There is no entry for Capacity Reservation in the Glossary.

According to FinOps terminology:

Capacity Reservation

Capacity Reservations allow you to secure compute capacity for resource instances in a particular region or zone. By utilizing Capacity Reservations, you can proactively address the potential challenge of acquiring capacity in situations where there might be capacity limitations. If you have specific capacity demands and operate mission-critical workloads that necessitate reliable and predictable capacity levels, it is advised that you create a Capacity Reservation. This ensures uninterrupted access to CSP instances, precisely when you require them. Capacity Reservations are available through on-demand Capacity Reservations (ODCRs) or through specific Commitment Discount types available from your CSP.

[jpradocueva]

Action Items from the TF-3 call on Friday, Sep 30:

• [TF3-#523] George: To update the PR by adding "Capacity Reservation" to the glossary and revising the requirements to avoid circular references and improve clarity.
• [TF3-#523] Irina: To review and approve the final changes made to the PR.

[udam-f2]

Seems good to go once comments are addressed.

This definitely needs some supporting content added to capture why we're dancing around the need for the capacity reservation id being SHOULD and other important topics we discussed (e.g. should this be in generic columns, related resources etc.).

Because of the FOCUS recommendation to use forks (which is unfortunate and an unnecessary complication for no gain), can't suggest this directly - so adding here:
FYI @jpradocueva

Please add to columns.mdpp (in alphabetical order):

!INCLUDE "capacityreservationid.md",1
!INCLUDE "capacityreservationstatus.md",1

[jpradocueva]

Action Items from Maintainers' call on Sep 2nd:

• [Maintainers-#523] George, @gparker-at-sf will update the PR by adding “Capacity Reservation” to the glossary and Irena to review and approve the PR and revisit the suggestions during the consistency review.
• [Maintainers-#523] Irena, @ijurica : To review and approve the final changes made to the PR.

[jpradocueva]

Approved by the Members group on Sep 5.