|
| 1 | +# How OCI Can Support FinOps Discipline |
| 2 | + |
| 3 | +In Cloud, the ability to spin up infrastructure by the simple push of a button has shifted costs from a fixed model to a variable model, |
| 4 | +increasing the distance from Engineerig and Finance teams. At the same time, this increases the chance for resources to be deployed and under-utilized, |
| 5 | +or to be under-utilized under particular circumstances. |
| 6 | +OCI provides tools and constructs to ensure FinOps discipline can be applied: |
| 7 | + |
| 8 | +**Organizations**: allows a parent-child relationship between various tenancies |
| 9 | + |
| 10 | +**Tenancies**: provide strong isolation among workloads |
| 11 | + |
| 12 | +**Compartments**: allow resources to be organized |
| 13 | + |
| 14 | +**Resources**: all OCI artifacts that can be deployed |
| 15 | + |
| 16 | +**Tags**: add metadata information to resources to apply governance policies and break down cost reporting |
| 17 | + |
| 18 | +**Budgets**: thresholds that can be set on cost per billing cycle that OCI will evaluate every hour to send an alert in case the value for the budget is crossed or closed. Budgets can be targeted toward subscriptions, child tenancies, compartments, and tags. The integration with the Event service can be used to trigger automation such as the creation of Quotas. |
| 19 | + |
| 20 | +**Quotas**: limits are set by Admins on compartments to prevent overspending. |
| 21 | + |
| 22 | + |
| 23 | + |
| 24 | +Cost reporting tools in OCI are aware of resource hierarchy and tags. |
| 25 | +Understanding your organization's reporting needs is the first step that needs to be |
| 26 | +taken into account when planning for a costing structure. |
| 27 | + |
| 28 | +OCI provides powerful tools to support FinOps discipline. |
| 29 | + |
| 30 | + |
| 31 | + |
| 32 | +1. **Cost Analysis** to visualize consumption over time. Group-by and filtering dimensions are available to customers. Queries can be saved for reuse. Data can be extracted as CSV and PDF. Future cost prediction is estimated based on current usage patterns. Reports can run at a specific time and deliver the content to an object storage. |
| 33 | + |
| 34 | +2. **Custom Cost Reports** show usage hourly per resources. Combined reports can be generated for all tenancies in an organization, viewed in Oracle Analytics Cloud, and queried in Autonomous DB when transferred. This move can be automated. |
| 35 | + |
| 36 | +3. Reporting needs across multiple cloud providers can be met by **3rd Party tools** such as Flexera, CloudHealth, and Cloudvane. |
| 37 | + |
| 38 | +4. **Cloud Advisor** enables cost-saving opportunities with resource-specific recommendations and customizable profiles. These recommendations can be immediately implemented via the 'fix-it' flow, without navigating to the specific resource. |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | + |
| 46 | +# Useful Links |
| 47 | + |
| 48 | +[FinOps best practices for Oracle Cloud Infrastructure](https://www.youtube.com/watch?v=0ia5wMwrAuI) |
0 commit comments