Skip to content

Commit f774c52

Browse files
Merge pull request #616 from oracle-devrel/FinOps-add
finops add
2 parents e3d0899 + 9533b96 commit f774c52

File tree

2 files changed

+92
-0
lines changed

2 files changed

+92
-0
lines changed
Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# FinOps
2+
3+
**FinOps** is a cloud financial management practice that supports organizations to optimize their cloud spending by providing a dedicated framework to achieve maximum business value by helping engineering, finance & business teams to collaborate on data-driven spending decision
4+
5+
6+
**The FinOps Framework** describes
7+
1. The Principles that drive FinOps practices
8+
2. The Personas that FinOps must support as stakeholders
9+
3. The best practices and process models that allow us to accomplish this
10+
4. The Domains of activity we will have to perform in our FinOps practice
11+
12+
# Principles
13+
14+
- Teams need to collaborate
15+
- Everyone takes ownership of their cloud usage
16+
- A centralized team enables FinOps
17+
- Reports should be accessible and timely
18+
- Decisions are driven by the business value of the cloud
19+
- Take advantage of the variable cost model of the cloud
20+
21+
# FinOps Phases
22+
23+
**Inform**: Gain visibility into your cloud usage;
24+
**Optimize**: Reduce overconsumption by making optimal decisions based on data;
25+
**Operate**: Create a culture for cost optimization.
26+
27+
# Useful Links
28+
29+
[State of FinOps](https://data.finops.org/)
30+
31+
32+
Attribution
33+
[FinOps Principles](https://www.finops.org/framework/principles/) by [FinOps Foundation](https://finops.org/about/)
34+
35+
36+
37+
# License
38+
39+
Copyright (c) 2023 Oracle and/or its affiliates.
40+
41+
Licensed under the Universal Permissive License (UPL), Version 1.0.
42+
43+
See [LICENSE](https://github.com/oracle-devrel/technology-engineering/blob/main/LICENSE)for more details.
44+
Reviewed: 20/11/2023
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
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

Comments
 (0)