48 lines
2.2 KiB
Markdown
48 lines
2.2 KiB
Markdown
---
|
||
title: "Public Cloud Learning Sessions - Ollie Workflow and The Demand Process"
|
||
type: source
|
||
tags: [Workflow, Demand-Process, Agile, DevOps]
|
||
date: 2024-04-16
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Cloud & DevOps/Public-Cloud-Learning-Sessions/06_CI_CD_GitOps/public-cloud-learning-sessions-ollie-workflow-and-the-demand-process-20240416-16.md]]
|
||
|
||
## Summary
|
||
- 核心主题：Oli 工作流流程，用于超大规模云服务商的支出审批、需求管理和请求处理
|
||
- 问题域：IT 服务管理、需求管理、云资源审批流程
|
||
- 方法/机制：ITIL 框架下的三阶段审批流程（可行性验证→技术验证→预算验证）
|
||
- 结论/价值：通过标准化工作流实现云资源请求的透明化管理，确保预算控制和资源合理分配
|
||
|
||
## Key Claims
|
||
- MUI 或 Shannon 的书面审批是任何超大规模云服务商支出的强制要求
|
||
- Oli 工作流正在过渡到 FinOps 团队，由 Tom Bice 负责管理
|
||
- 请求缺失理由说明将导致即时拒绝
|
||
- 机器应执行机器能做的事，实现自动化处理
|
||
|
||
## Key Quotes
|
||
> "The current mandate requires written approval from MUI or Shannon for any hyperscaler spend, regardless of the amount." — 审批要求
|
||
> "If justification details are not provided, requests are subject to immediate rejection." — 拒绝机制
|
||
> "Machines should do what machines can do, enabling an automated fulfillment process." — 自动化目标
|
||
|
||
## Key Concepts
|
||
- [[Demand Management]]：需求管理，平衡请求与可用容量
|
||
- [[ITIL Framework]]：ITIL 框架将业务流程分为服务战略、设计、转换、运营和改进五个阶段
|
||
- [[Workflow Process]]：审批流程是请求处理的第一阶段
|
||
- [[Service Catalog]]：服务目录，云产品和服务的标准化清单
|
||
|
||
## Key Entities
|
||
- [[MUI]]：审批决策者之一
|
||
- [[Shannon]]：审批决策者之一
|
||
- [[Tom Bice]]：FinOps 团队负责人
|
||
- [[FinOps Team]]：负责 Oli 工作流管理的团队
|
||
- [[FPNA Team]]：负责预算可用性验证的团队
|
||
|
||
## Connections
|
||
- [[Demand Management]] ← depends_on ← [[ITIL Framework]]
|
||
- [[Workflow Process]] ← part_of ← [[ITIL Framework]]
|
||
- [[Service Catalog]] ← enables ← [[Demand Management]]
|
||
- [[FinOps Team]] ← manages ← [[Workflow Process]]
|
||
|
||
## Contradictions
|
||
- 无 |